jockey-backend crashed with MemoryError in run_dbus_service()

Bug #832622 reported by Pit(er) Ralon
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Don' know exactly why the crash report is starting. after updating system i logged in ubunt, and it works! for the first time, and it looks good. so i go with mouse courser to the screen icon on the right corner above into the systemsettings and then crash report is starting.

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

Architecture: amd64
Date: Wed Aug 24 11:09:33 2011
ExecutablePath: /usr/share/jockey/jockey-backend
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110701)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard SG3-140CH
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=d7a7136d-23a7-4f56-84c0-df927bb4a59f 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: Upgraded to oneiric on 2011-08-24 (0 days ago)
UserGroups:

dmi.bios.date: 04/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.01
dmi.board.name: 2AAF
dmi.board.vendor: FOXCONN
dmi.board.version: 1.00
dmi.chassis.asset.tag: CZC0228K3V
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.01:bd04/23/2010:svnHewlett-Packard:pnSG3-140CH:pvr:rvnFOXCONN:rn2AAF:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: SG3-140CH
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Pit(er) Ralon (pitralon) wrote :
visibility: private → public
Changed in jockey (Ubuntu):
status: New → Confirmed
Revision history for this message
nochka85 (nochka85) wrote :

Got the same bug at every session start... And I'm not able to open the window for the proprietary drivers at all.

Note : I use a 64bits system

Revision history for this message
nochka85 (nochka85) wrote :

By the way, this is what I have when running 'jockey-gtk' in a terminal :

$ jockey-gtk
ERROR:dbus.proxies:Introspect error on :1.72:/DeviceDriver: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 415, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 465, in run
    self.ui_show_main()
  File "/usr/bin/jockey-gtk", line 94, in ui_show_main
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 271, in update_tree_model
    for h_id in self.get_displayed_handlers():
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 816, in get_displayed_handlers
    return self.backend().available(self.argv_options.mode)
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 127, in backend
    self._check_repositories()
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 839, in _check_repositories
    if self._dbus_iface.has_repositories():
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.72 was not provided by any .service files

Revision history for this message
crtm (carlosrtm) wrote :

after last upgrade, crash

Revision history for this message
Adnane Belmadiaf (daker) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #831754, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.