jockey-gtk crashed with AttributeError: 'tuple' object has no attribute 'getSections'

[John Kozyrakis]

this appears when running jockey-gtk, ubuntu hardy beta with latest updates as of today.

$ jockey-gtk
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 300, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 266, in run
    self.ui_init()
  File "/usr/bin/jockey-gtk", line 93, in ui_init
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 240, in update_tree_model
    is_enabled = handler.enabled()
  File "/usr/share/jockey/handlers/nvidia.py", line 50, in enabled
    devices = self.xorg_conf.getSections('device')
AttributeError: 'tuple' object has no attribute 'getSections'

The gpu is nvidia geforce fx 5200.

[Inkwina (phsi)]

I have the exact same problem

[Nicolai (nicojorg)]

same for me

[Thorsten (ungesaeuertesbrot)]

the api in guidance-backends, namely in /usr/share/python-support/guidance-backends/xorgconfig.py seems to have changed. This causes self.xorg_conf to be a tuple of XorgConfig and bool rather than a simple XorgConfig.

Changing line 60 in /usr/lib/python2.5/site-packages/jockey/xorg_driver.py from
                self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)
to
                self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)[0]

fixes the problem. I'm not sure what one could use the boolean value in the tuple for since it looks like an XorgConfig instance is created anyways or an Exception raised. And in anyy case xorg_driver.py simply fills in None if there was an exception. Anyway it might still be bad style to simply ignore that bool. Yet it seems to work. diff -Nurp is attatched.

[Jeff Strunk (jstrunk-math)]

This problem exists with versions 0.3.3-0ubuntu6 and 0.3.3-0ubuntu7.

I get the same exception in a different file though:

Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 300, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 266, in run
    self.ui_init()
  File "/usr/bin/jockey-gtk", line 93, in ui_init
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 240, in update_tree_model
    is_enabled = handler.enabled()
  File "/usr/lib/python2.5/site-packages/jockey/xorg_driver.py", line 77, in enabled
    devices = self.xorg_conf.getSections('device')
AttributeError: 'tuple' object has no attribute 'getSections'

This occurs in a system with an ATI Radeon HD 2400 XT. It does not occur on my ATI Rage 128 Pro Ultra TF or my Intel 82Q35 Express systems.

[Jeff Strunk (jstrunk-math)]

Throsten's patch fixes my problem.

Thank you.

[Chafnan (chafnan)]

I had the same issue.

Throsten's patch fixes it for me.

Thanks

[peter b (b1pete)]

subject: bug #215171
message from: Thorsten Shoel

*** This bug is a duplicate of bug 215027 ***
    https://bugs.launchpad.net/bugs/215027

** This bug has been marked a duplicate of bug 215027*** This bug is a duplicate of bug 215027 ***
    https://bugs.launchpad.net/bugs/215027

made the change suggested above; still no success when system-->admin-->hardware drivers called; no display. bug notification still pops up as before (when bug reported).

thank you,
peter b

[peter b (b1pete)]

ran also

sudo jockey-gtk

Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 300, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 266, in run
    self.ui_init()
  File "/usr/bin/jockey-gtk", line 93, in ui_init
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 240, in update_tree_model
    is_enabled = handler.enabled()
  File "/usr/lib/python2.5/site-packages/jockey/xorg_driver.py", line 77, in enabled
    devices = self.xorg_conf.getSections('device')
AttributeError: 'tuple' object has no attribute 'getSections'

and crash report again pops up.

thank you
peter b

[peter b (b1pete)]

video adapter ati x1300

[tavella (tony-avella)]

The fix worked for me. Ubuntu Hardy x86_64 Nvidia 7400.

[Kai Stempfle (kai-stempfle)]

Supplied patch worked for me, too.

nVIDIA GeForce 8600 GTS

# uname -a
Linux Wingthor 2.6.24-15-generic #1 SMP Tue Apr 8 00:33:51 UTC 2008 i686 GNU/Linux

[lolzlolz (lolzlolz)]

fixed for me as well
on a x86_64
nvidia 8600gt
thanks

[BC7333 (brian-abtrafco)]

Could someone point me to the directions how to apply the patch? Sorry linux newbie here.

[peter b (b1pete)]

latest packages installed, file rechecked, reboot twice --> everything OK, working.

thank you

[jesmago (jesmago)]

it also works for me.
Thank you!

[Anmar Oueja (anmar)]

I can confirm that this also works for me.

[Matija Polajnar (matija-polajnar)]

I can also confirm the existence of this bug and that the posted patch fixes the problem.

[John S. Gruber (jsjgruber)]

Nice work, Thorsten. The fix worked for me for installing a proprietary driver.

Removing a driver still gave me a similar problem with a UI traceback below the tuple problem. Using your research I found another call of readConfig later in the code and made the same change you made above. Then I was able to go back and forth.

Here's the total change:

--- xorg_driver.py 2008-04-08 21:06:25.000000000 -0400
+++ xorg_driver.py.new 2008-04-10 16:36:07.000000000 -0400
@@ -57,7 +57,7 @@

         if os.path.exists(OSLib.inst.xorg_conf_path):
             try:
- self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)
+ self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)[0]
             except (IOError, xorgconfig.ParseException, AttributeError):
                 self.xorg_conf = None
         else:
@@ -156,7 +156,7 @@
         elif os.path.exists(oldconf):
             open(OSLib.inst.xorg_conf_path, 'w').write(open(oldconf).read())
             os.unlink(oldconf)
- self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)
+ self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)[0]
         else: # no backup, so mangle current config manually
             device = self.xorg_conf.getSections('device')[0]
             device.driver = self.alt_free_driver

[Daniel Morales (danielmorales)]

The patch to fix the problem works for me too. Thanks :)

[gjw (gjw)]

it works for me. thanks!

[BC7333 (brian-abtrafco)]

Nothing has worked for me here so far, updated, tried editing .py lines as above, uninstalled jockey, reinstalled..

brian@brian-laptop:~$ sudo jockey-gtk
[sudo] password for brian:
ERROR: could not open /proc/asound/cards: [Errno 2] No such file or directory: '/proc/asound/cards'
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 300, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 266, in run
    self.ui_init()
  File "/usr/bin/jockey-gtk", line 93, in ui_init
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 240, in update_tree_model
    is_enabled = handler.enabled()
  File "/usr/share/jockey/handlers/nvidia.py", line 50, in enabled
    devices = self.xorg_conf.getSections('device')
AttributeError: 'tuple' object has no attribute 'getSections'

brian@brian-laptop:~$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation NV31M [GeForce FX Go5600] (rev a1)
brian@brian-laptop:~$

jockey-gtk --list --debug 2>&1|tee /tmp/jockey-dbg.txt results attached.

[xtknight (xt-knight)]

John S. Gruber:

Thank you, it fixes the problem for me as well. I haven't thoroughly tested the operation of jockey though to be sure.

While we're at it, here's a debdiff. And anyone can try the new packages at my PPA: https://launchpad.net/~xt-knight/+archive

[John S. Gruber (jsjgruber)]

@BC7333

Did you change both lines in /usr/lib/python2.5/site-packages/jockey/xorg_driver.py when you made the changes or just the one suggested by Thorsten earlier? I don't know when you read the error report and did your test.

If you made them both you might try it again against the reinstalled jockey, adding a print line before line 50 in /usr/share/jockey/handlers/nvidia.py and after the two changes above to print a comment and self.xorg_conf

     I looked again and can't find any more places where that variable is incorrectly set, so it looks to my naive eye like that should do it.

As Thorsten pointed out above, this is about a software interface problem, not about your specific hardware. That might be why there are so many people reporting it.

[John S. Gruber (jsjgruber)]

I see that the diff I posted got changed by the launchpad software. It looks like embedded whitespace is deleted. The indentation is off
and indentation is all important in python programs.

Attached is the diff.

Let me try again, (gambling that initial whitespace will be respected by the posting process)

In line 60 of /usr/lib/python2.5/site-packages/jockey/xorg_driver.py (16 spaces start each line)

                self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)
->
                self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)[0]

and in line 159 of the same file (12 spaces start each line)

            self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)
->
            self.xorg_conf = xorgconfig.readConfig(OSLib.inst.xorg_conf_path)[0]

@xtknight: Thanks. Thorsten Schoel did the work. I just robotically copied Thorsten and then bumbled my posting.

[Junior (juniorperes)]

Throsten,

Thank you! Your modification fixed also my problem. By the way I believe this should be corrected by an update to all users because this can happens with newbie.

Best regards,
Adilson

[xtknight (xt-knight)]

OK then, updated debdiff crediting Thorsten. Thank you for bringing it to our attention though.

[xtknight (xt-knight)]

I believe this fix is eligible for a Freeze Exception.

First, the hardware driver dialog is broken for everyone (AFAIK), and this patch has only fixed it so far for several folks.
I don't know Python or the jockey architecture that well, so I don't know the impact of it. Maybe someone else can elaborate on this. It looks like a small fix to me. I doubt it makes anything worse.

[Michał Karnicki (karni)]

Thanks Thorsten Schoel, it solved my problem.

[cgoddard (chrismatic)]

Thorsten's patch worked for me. Unless anyone encountered any problems with this patch it seems like this should be applied in an update.

[samhassell (samhassell)]

Fixed for me too. This needs to be pushed next update.

[Andreas Schröder (mangkorn)]

Thanks Thorsten Schoel, it solved my problem, too

[klee1001 (k-merk)]

Throsten's patch fixes my problem.

Thank you.

[John Greenleaf-Maple (jandmgm)]

Another confirmation of Thorsten's patch fixing jockeky-gtk crash after upgrade. Thanks!

[g009 (g009)]

Thorstens fix worked for me to.
amd64 athlon
nvidia geforce4 32mb

[Martin Pitt (pitti)]

Those are all (even more) duplicates of bug 214914.

[keulieminogue (superkeule)]

Greate!!! it works

Thanx a lot

[chessepuff (paganjosh43130)]

the patch works great thank Thorstens

[coocoo (coocoo)]

OK, I'm a TOTAL noob to this, I only installed ubuntu hardy heron at 10pm last night. I have no idea how to apply this fix because opening the referenced file and trying to change the line doesn't work because I'm not the owner of the file.

Please help, I'm trying to rid myself of the Windows shackles and things like this make me wonder what I've let myself in for!

Simply put, what do I do to apply this fix?

[xtknight (xt-knight)]

This bug must have been fixed elsewhere because the -ubuntu7 version works again now.

[coocoo (coocoo)]

aye, works for me now too...

[Thorsten (ungesaeuertesbrot)]

See #214914. They reverted the change in guidance-backends that caused
the problem for jockey in the first place.

[thefuzz4 (jason-hamilton)]

Thank you this fix worked great.

[1+1=2 (dbzhang800)]

It works.Thanks!!