jockey-backend crashed with MemoryError in run_dbus_service()

[damormino]

Upon logging in after restart, this message appears: Sorry, the program "jockey-gtk" closed unexpectedly

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
.var.log.jockey.log:

Architecture: amd64
Date: Mon Aug 22 21:06:40 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InterpreterPath: /usr/bin/python2.7
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=0be36b9e-45e2-4861-aa9d-b82f7cf42452 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log']
SourcePackage: jockey
Title: jockey-backend crashed with MemoryError in run_dbus_service()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: NM10
dmi.board.vendor: ZOTAC
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/21/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnZOTAC:rnNM10:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ingo Gerth (igerth)]

This bug happens on my machine every time I open Ubiquity from a live session. Bug #833295 occurs right after this. This is reproducible.

[Steph (64bit-us)]

I get this crash along with "jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.124 was not provided by any .service files" crash

This crash has begun after the latest updates (today) in Gnome when clicking "Additional Drivers" in System Settings. (That screen never does come up).

[florin (florin-arjocu)]

I don't really know what triggers this bug, but along with other 3-4 visible bugs this one is always present on my virtualbox machine. I just upgraded the distribution, so this system is up-to-date.

[crtm (carlosrtm)]

crash after the last update

[Maarten Kossen (mpkossen)]

This happens at more moments than when clicking 'Additional Drivers'. I just got it while unlocking my screen and I've seen it happen once what looked like "a random moment".

[ralph (ralph-shoemaker)]

I found the solution. I loaded Mint 11, then loaded kernel 3 and Gnome 3
separately.

On Wed, Aug 24, 2011 at 11:31 PM, Maarten Kossen <
<email address hidden>> wrote:

> This happens at more moments than when clicking 'Additional Drivers'. I
> just got it while unlocking my screen and I've seen it happen once what
> looked like "a random moment".
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (831447).
> https://bugs.launchpad.net/bugs/831754
>
> Title:
> jockey-backend crashed with MemoryError in run_dbus_service()
>
> Status in Jockey driver manager:
> New
> Status in “jockey” package in Ubuntu:
> In Progress
>
> Bug description:
> Upon logging in after restart, this message appears: Sorry, the
> program "jockey-gtk" closed unexpectedly
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.10
> Package: jockey-common 0.9.4-0ubuntu2
> ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3
> Uname: Linux 3.0.0-9-generic x86_64
> .var.log.jockey.log:
>
> Architecture: amd64
> Date: Mon Aug 22 21:06:40 2011
> ExecutablePath: /usr/share/jockey/jockey-backend
> InterpreterPath: /usr/bin/python2.7
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l
> /var/log/jockey.log
> ProcEnviron:
>
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic
> root=UUID=0be36b9e-45e2-4861-aa9d-b82f7cf42452 ro quiet splash vt.handoff=7
> PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l',
> '/var/log/jockey.log']
> SourcePackage: jockey
> Title: jockey-backend crashed with MemoryError in run_dbus_service()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> dmi.bios.date: 03/21/2011
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 080016
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: NM10
> dmi.board.vendor: ZOTAC
> dmi.chassis.asset.tag: To Be Filled By O.E.M.
> dmi.chassis.type: 3
> dmi.chassis.vendor: To Be Filled By O.E.M.
> dmi.chassis.version: To Be Filled By O.E.M.
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/21/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnZOTAC:rnNM10:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
> dmi.product.name: To Be Filled By O.E.M.
> dmi.product.version: To Be Filled By O.E.M.
> dmi.sys.vendor: To Be Filled By O.E.M.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/jockey/+bug/831754/+subscriptions
>

[David Baucum (maxolasersquad)]

I also received this crash when trying to open "Additional Drivers"

[col reilly (lupinehorror)]

crash happened just when loading desktop...no other action taken to cause it on my part.

[col reilly (lupinehorror)]

just got it under the ubuntu desktop as well as the xubuntu desktop

[Erick Brunzell (lbsolost)]

Just got this error with the initial boot of the Lubuntu i386-20110825 daily image. It just popped up as soon as the desktop appeared w/o having launched any apps.

[Glenn Chugg (glennlchugg)]

Crash occurred just after desktop completed loading.

[Takács Arnold (tarnoldj)]

I get this error after installing from Ubuntu i386-20110826 daily alternative image. When this occurs after it has booted to the desktop, the Jockey indicator also fails to start, so it's not showing up at all. I tried to run jockey-text for instance, and its output is inside the following attachment.

[[e-mail] (sgage)]

I get the same symptom as Steph above (though my system is 32-bit).

"jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.124 was not provided by any .service files"

[Barry Drake (b-drake)]

Agai - trying to open 'additional drivers' - no other clues.

[Barry Drake (b-drake)]

This time, it occurred just after opening Nautilus. Can't find any consistency, except that it is repeatable when trying to open 'additional drivers'.

[jerrylamos (jerrylamos)]

Today's daily build 26 August live

Just booted and waited, a couple minutes later this bug appeared.

Jerry

[Boris Tosovic (boris-tosovic)]

Same like comment before from jerrylamos. I zsynced build from 2-3 weeks ago.

[Niels Kristian Bech Jensen (nkbjensen)]

Same for me booting with the 20110826.1 Desktop CD on a Fujitsu-Siemens Amilo La1703. The crash occured right after the desktop appeared (no key pressed or anything).

[Kevin (blackhawkover-gmail)]

Got the same crash after clicking "additional drivers"

[Rainer Rohde (rainer-rohde)]

Crashed on me today right after login...

[Jonathan Almeida (jonalmeida)]

I get this error when installing the daily build (27th August) on virtualbox.

[Rainer Rohde (rainer-rohde)]

Also happens when opening the Ubuntu One client ...

[jerrylamos (jerrylamos)]

Brand new daily build live 27 August boot, wait a few seconds, up pops the error.

3.33 mHz Compaq ati radeon xpress 200. I've got full apport report but assume it is similar to the entries above.

Jerry

[Jeeks (tanjeekhiumssg)]

Same here. Filed a bug report. Using Nouveau Drivers.

[AO (aofrl10n)]

On Oneiric x64 daily live install 27/08/2011, jockey-gtk just doesn't work when looking for a driver, the backend goes right after.

[crtm (carlosrtm)]

after update -a few min.- then chrash

[Xavier Bassery (xaba)]

As a temporary workaround is to use the --no-dbus option.
  gksu "jockey-gtk --no-dbus"
works here.

[Maarten Kossen (mpkossen)]

The workaround from #28 doesn't work for me. I get a while list of other errors:

WARNING:root:Could not open DriverDB cache /var/cache/jockey/driverdb-OpenPrintingDriverDB.cache: [Errno 2] No such file or directory: '/var/cache/jockey/driverdb-OpenPrintingDriverDB.cache'
WARNING:root:modinfo for module nvidia_96 failed: ERROR: modinfo: could not find module nvidia_96

WARNING:root:modinfo for module nvidia_current failed: ERROR: modinfo: could not find module nvidia_current

WARNING:root:modinfo for module nvidia_173 failed: ERROR: modinfo: could not find module nvidia_173

WARNING:root:modinfo for module nvidia_current failed: ERROR: modinfo: could not find module nvidia_current

WARNING:root:modinfo for module nvidia_173 failed: ERROR: modinfo: could not find module nvidia_173

WARNING:root:modinfo for module nvidia_96 failed: ERROR: modinfo: could not find module nvidia_96

WARNING:root:modinfo for module vmxnet failed: ERROR: modinfo: could not find module vmxnet

WARNING:root:modinfo for module fglrx failed: ERROR: modinfo: could not find module fglrx

WARNING:root:modinfo for module fglrx failed: ERROR: modinfo: could not find module fglrx

WARNING:root:modinfo for module wl failed: ERROR: modinfo: could not find module wl

WARNING:root:modinfo for module ath_pci failed: ERROR: modinfo: could not find module ath_pci

Traceback (most recent call last):
  File "/usr/bin/jockey-text", line 128, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 467, in run
    self.backend().shutdown()
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 113, in backend
    self._dbus_iface = Backend()
  File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 146, in __init__
    self.detect()
  File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 175, in detect
    self._detect_handlers()
  File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 773, in _detect_handlers
    hardware=self.hardware):
  File "/usr/lib/python2.7/dist-packages/jockey/detection.py", line 1001, in get_handlers
    available_handlers.update(get_db_handlers(backend, db, hardware, mode))
  File "/usr/lib/python2.7/dist-packages/jockey/detection.py", line 1029, in get_db_handlers
    h = _driverid_to_handler(did, backend, mode)
  File "/usr/lib/python2.7/dist-packages/jockey/detection.py", line 739, in _driverid_to_handler
    (not h.package or not did['package'] or h.package == did['package']):
  File "/usr/lib/python2.7/dist-packages/jockey/detection.py", line 134, in __getitem__
    return self.properties.__getitem__(key)
KeyError: 'package'

[Xavier Bassery (xaba)]

@Marteen,
it looks like you have tried to run jockey as a normal user.
I had to use gksu like I have written, in order for jockey-gtk to work (once).

That said, the second time I tried to run jockey (after having installed a restricted driver), it didn't work.
The traceback is attached.

[Xavier Bassery (xaba)]

@Marteen,
my mistake, you actually got the same Traceback as the one I got the second time.
It looks like this is another bug.
It could trigger when there are no more restricted driver to install .
Do you actually have any "restricted" hardware in your system, or have you previously installed all possible candidates (using jockey, or apt, ...)?

[Xavier Bassery (xaba)]

Thanks Marteen for having reported the new bug in
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/836714

[Maarten Kossen (mpkossen)]

Xavier: thanks for your suggestion. Running it directly after booting got rid of the initial message (about the DriverDB), but the rest is the same, unfortunately. Let's hope for a fix soon.