Not after the partial upgrade I did yesterday. Hopefully in a few days when
Beta 1 comes out it will be fixed.
On Aug 28, 2011 4:56 AM, "Extender" <email address hidden> wrote:
> So, there is no way to start jockey in Oneiric?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (835619).
> https://bugs.launchpad.net/bugs/657829
>
> Title:
> jockey-gtk crashed with DBusException in call_blocking()
>
> Status in “jockey” package in Ubuntu:
> Confirmed
>
> Bug description:
> Just clicked on "Additional Drivers" in System Menu, running from Live CD
(which was verified after burning).
> v 10.10
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: jockey-gtk 0.5.10-0ubuntu5
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic i686
> Architecture: i386
> CurrentDmesg: [ 73.536039] eth0: no IPv6 routers present
> Date: Sun Oct 10 18:09:48 2010
> ExecutablePath: /usr/bin/jockey-gtk
> InterpreterPath: /usr/bin/python2.6
> LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
> PackageArchitecture: all
> ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
> ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> PythonArgs: ['/usr/bin/jockey-gtk']
> SourcePackage: jockey
> Title: jockey-gtk crashed with DBusException in call_blocking()
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> dmi.bios.date: 01/28/2005
> dmi.bios.vendor: Intel Corp.
> dmi.bios.version: EV91510A.86A.0401.2005.0128.0809
> dmi.board.name: D915GAG
> dmi.board.vendor: Intel Corporation
> dmi.board.version: AAC64123-304
> dmi.chassis.type: 2
> dmi.modalias:
dmi:bvnIntelCorp.:bvrEV91510A.86A.0401.2005.0128.0809:bd01/28/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GAG:rvrAAC64123-304:cvn:ct2:cvr:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/657829/+subscriptions
Not after the partial upgrade I did yesterday. Hopefully in a few days when /bugs.launchpad .net/bugs/ 657829 ature: Ubuntu 2.6.35- 22.33-generic 2.6.35.4 ture: all preseed/ hostname. seed boot=casper /casper/ initrd. lz quiet splash -- maybe-ubiquity bin/jockey- gtk'] 86A.0401. 2005.0128. 0809 p.:bvrEV91510A. 86A.0401. 2005.0128. 0809:bd01/ 28/2005: svn:pn: pvr:rvnIntelCor poration: rnD915GAG: rvrAAC64123- 304:cvn: ct2:cvr: /bugs.launchpad .net/ubuntu/ +source/ jockey/ +bug/657829/ +subscriptions
Beta 1 comes out it will be fixed.
On Aug 28, 2011 4:56 AM, "Extender" <email address hidden> wrote:
> So, there is no way to start jockey in Oneiric?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (835619).
> https:/
>
> Title:
> jockey-gtk crashed with DBusException in call_blocking()
>
> Status in “jockey” package in Ubuntu:
> Confirmed
>
> Bug description:
> Just clicked on "Additional Drivers" in System Menu, running from Live CD
(which was verified after burning).
> v 10.10
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: jockey-gtk 0.5.10-0ubuntu5
> ProcVersionSign
> Uname: Linux 2.6.35-22-generic i686
> Architecture: i386
> CurrentDmesg: [ 73.536039] eth0: no IPv6 routers present
> Date: Sun Oct 10 18:09:48 2010
> ExecutablePath: /usr/bin/jockey-gtk
> InterpreterPath: /usr/bin/python2.6
> LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
> PackageArchitec
> ProcCmdLine: file=/cdrom/
initrd=
> ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> PythonArgs: ['/usr/
> SourcePackage: jockey
> Title: jockey-gtk crashed with DBusException in call_blocking()
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> dmi.bios.date: 01/28/2005
> dmi.bios.vendor: Intel Corp.
> dmi.bios.version: EV91510A.
> dmi.board.name: D915GAG
> dmi.board.vendor: Intel Corporation
> dmi.board.version: AAC64123-304
> dmi.chassis.type: 2
> dmi.modalias:
dmi:bvnIntelCor
>
> To manage notifications about this bug go to:
>
https:/