jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()

I cannot replicate this. The timeout for this is set to 86400 seconds (an entire day), and the timeout works for me.

Can anyone please describe exactly how you got this crash? Any recipe for reproducing?

Wish I could - this was an automated bug report - all I did was reboot the machine after switching to closed-source Nvidia drivers through the restricted drivers applet.

All I can tell you is that the process hung at 100% so I ended it and rebooted the machine - the driver apparently installed correctly but I got a couple of bugchecks after a reboot.

wizard10000 [2008-10-13 9:08 -0000]:
> Wish I could - this was an automated bug report - all I did was reboot
> the machine after switching to closed-source Nvidia drivers through the
> restricted drivers applet.

Ah, and when did you get the crash report? After closing the hardware
driver panel, or after restarting the computer?

That's already a valuable data point. So far I assumed the timeout
would happen during driver installation (as the traceback suggests).

> All I can tell you is that the process hung at 100% so I ended it and
> rebooted the machine

which process exactly? jockey-gtk or jockey-backend?

Do other reporters have similar experience? Does it crash *during*
driver installation for you, or at some later point?

Thanks, Martin

I have no idea how to replicate the problem, but what I can tell you is:
The recommended NVidia driver could not be installed, the hang occurred a
couple of times;
The NVidea driver version 96 could be installed after installing the NVidia
version 71;
But neither version could be activated, the machine had a [fail] proc on
NVidia on restart; and could only start on low level graphics otherwise it
would hang;

I believe that the drivers were not compatible? It's a NVidia G4 card.

On Mon, Oct 13, 2008 at 4:44 PM, Martin Pitt <email address hidden> wrote:

> I cannot replicate this. The timeout for this is set to 86400 seconds
> (an entire day), and the timeout works for me.
>
> Can anyone please describe exactly how you got this crash? Any recipe
> for reproducing?
>
> ** Changed in: jockey (Ubuntu)
> Status: In Progress => Incomplete
>
> --
> jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> https://bugs.launchpad.net/bugs/273600
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

The crash report happened after closing the Hardware Driver Panel, was
hanging on 0% and being non-responsive. jockey-gtk - Did not install, the
driver it was hanging on driver installation.

Verified connection and all processes - system monitor - no activity other
than system-monitor and firefox.

On Mon, Oct 13, 2008 at 5:45 PM, Martin Pitt <email address hidden> wrote:

> wizard10000 [2008-10-13 9:08 -0000]:
> > Wish I could - this was an automated bug report - all I did was reboot
> > the machine after switching to closed-source Nvidia drivers through the
> > restricted drivers applet.
>
> Ah, and when did you get the crash report? After closing the hardware
> driver panel, or after restarting the computer?
>
> That's already a valuable data point. So far I assumed the timeout
> would happen during driver installation (as the traceback suggests).
>
> > All I can tell you is that the process hung at 100% so I ended it and
> > rebooted the machine
>
> which process exactly? jockey-gtk or jockey-backend?
>
> Do other reporters have similar experience? Does it crash *during*
> driver installation for you, or at some later point?
>
> Thanks, Martin
>
> --
> jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> https://bugs.launchpad.net/bugs/273600
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Martin Pitt wrote:

>Ah, and when did you get the crash report? After closing the hardware
>driver panel, or after restarting the computer?

After the reboot.

>which process exactly? jockey-gtk or jockey-backend?

jockey-gtk

>Do other reporters have similar experience? Does it crash *during*
>driver installation for you, or at some later point?

One other piece of information - well, two. First, this machine is a myth backend and mythfilldatabase also crashed at some point and wanted to send a bug report on the same reboot - so did compiz.real.

Second, it just occurred to me that I had set vm.swappiness to 10 right before the upgrade to Intrepid - might not be a good idea on this machine. I removed the entry from sysctl.conf and will keep an eye on the machine.

i had this same problem.

i was changing to the old 173 version of the driver but the download was stalled at 0% so i tried to cancel the download but nothing happened. Then i tried to close the window. nothing happens. the after a while this crash.

forgot:
intrepid ibex updated this morning. on 64 bit.
if theres anything else you need please let me know

Fresh up-to-date intrepid.

Went to install the restricted ati driver, and after an eternity at 0%, this pops up, and the window closes.

However, going into synaptic reports that all the fglrx packages are installed now.

Reopening the jockey gui also reports that they are enabled, but that a restart is required (this is normal, as I haven't yet restarted).

My apport crash data is at bug #284002

I would consider marking this as confirmed.

I had the same problem as eapache.

Same problem here

Same problem here. I was trying to activate nvidia close-source driver version 177. When I clicked "Activate", it tried to download the driver, but this error appeared.

and here too - downloaded the daily iso of the 17th Oct, did all the updates, rebooted, then started the activation of the nvidia driver, went to kitchen to do stuff and came back to a crashed jockey...

just an addition to my last statement - I rebooted and upon logging back in found the nvidia drivers had been installed. Confirmed both by starting the Hardware drivers tool, as well as by the screen position (nvidia always sets the screen 4 or 5 mm to the left)

Mine failed on installation of ATI/AMD drivers on a vanilla new install, reason unknown for sure, directly after failure of Jockey I recieved report that libamdxvba1 did not install properly. May be tied to that???

This happened to me after activating the nvidia driver v177. The driver appears to be active. No reboot required. I'm using the LiveCD v8.10.

This happened while using firefox, getting the drivers (automagically so) and having 2 Appearance windows open at the same time (yes, that might possibly have been a stupid thing to do).

Thanks for all the good work. ***blows won't ever come near my pc again.

I finally discovered one bug: if driver installation lasts longer than 10 minutes, the backend times out, and the GUI crashes with "org.freedesktop.DBus.Error.ServiceUnknown: The name :1.398 was not provided by any .service files". That's a real problem, however, it's not exactly the same crash that was reported here. That might be because the crash you reported is yet another problem, or just because of the slightly braindead way I used to test this.

I fixed the issue mentioned above in trunk (r503). However, I now know what happened: Whenever the backend crashes, with e. g. SIGSEGV or SIGABRT, it simply goes away without throwing a proper exception to the GUI, and the GUI then just times out. That doesn't happen with Python exceptions in the backend, they are propagated properly.

So I'm a bit lost how to fix this, since none of the reports contain an actual reason why the backend crashed.

I alleviated this by intercepting the crash and presenting an error dialog which asks to file a bug. Usually apport should catch the backend crash, so that should happen automatically on Ubuntu.

Yes the problem was like this, after a long time that system was trying to
install the driver, (without any progress) the application crashes... But
this occurs only on Live CD, after installed I think that its install
properly.

Thanks!

2008/11/12 Martin Pitt <email address hidden>

> I finally discovered one bug: if driver installation lasts longer than
> 10 minutes, the backend times out, and the GUI crashes with
> "org.freedesktop.DBus.Error.ServiceUnknown: The name :1.398 was not
> provided by any .service files". That's a real problem, however, it's
> not exactly the same crash that was reported here. That might be because
> the crash you reported is yet another problem, or just because of the
> slightly braindead way I used to test this.
>
> --
> jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> https://bugs.launchpad.net/bugs/273600
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "jockey" source package in Ubuntu: In Progress
>
> Bug description:
> 810 with latest updates
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/jockey-gtk
> InterpreterPath: /usr/bin/python2.5
> NonfreeKernelModules: nvidia
> Package: jockey-gtk 0.5~alpha1-0ubuntu2
> PackageArchitecture: all
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_IN
> SHELL=/bin/bash
> PythonArgs: ['/usr/bin/jockey-gtk']
> SourcePackage: jockey
> Title: jockey-gtk crashed with DBusException in
> dbus_sync_call_signal_wrapper()
> Uname: Linux 2.6.27-4-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev
> plugdev root sambashare scanner tape users video
>

--
Gabriel B. Casella(c)(R)

Nay, the problem persists. I installed amd64 variant of Ubuntu 8.10 today
and couldn't start the NVIDIA driver thru System --> Administration -->
Hardware Drivers at all. At earlier installation (regular Ubuntu 8.10 Live
CD) I could achieve that albeit with some struggle (Jokey behaved
strangely). Now when I try to start NVIDIA driver ver. 177 Jokey simply
hangs with 'Downloading...' window at 0%, and doesn't do anything...

I uninstalled Jockey and am downloading the driver directly thru Software
update...

On Wed, Nov 12, 2008 at 21:40, gbc921 <email address hidden> wrote:

> Yes the problem was like this, after a long time that system was trying to
> install the driver, (without any progress) the application crashes... But
> this occurs only on Live CD, after installed I think that its install
> properly.
>
> Thanks!
>
>
> 2008/11/12 Martin Pitt <email address hidden>
>
> > I finally discovered one bug: if driver installation lasts longer than
> > 10 minutes, the backend times out, and the GUI crashes with
> > "org.freedesktop.DBus.Error.ServiceUnknown: The name :1.398 was not
> > provided by any .service files". That's a real problem, however, it's
> > not exactly the same crash that was reported here. That might be because
> > the crash you reported is yet another problem, or just because of the
> > slightly braindead way I used to test this.
> >
> > --
> > jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> > https://bugs.launchpad.net/bugs/273600
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in "jockey" source package in Ubuntu: In Progress
> >
> > Bug description:
> > 810 with latest updates
> >
> > ProblemType: Crash
> > Architecture: i386
> > DistroRelease: Ubuntu 8.10
> > ExecutablePath: /usr/bin/jockey-gtk
> > InterpreterPath: /usr/bin/python2.5
> > NonfreeKernelModules: nvidia
> > Package: jockey-gtk 0.5~alpha1-0ubuntu2
> > PackageArchitecture: all
> > ProcAttrCurrent: unconfined
> > ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> > ProcEnviron:
> >
> >
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> > LANG=en_IN
> > SHELL=/bin/bash
> > PythonArgs: ['/usr/bin/jockey-gtk']
> > SourcePackage: jockey
> > Title: jockey-gtk crashed with DBusException in
> > dbus_sync_call_signal_wrapper()
> > Uname: Linux 2.6.27-4-generic i686
> > UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev
> > plugdev root sambashare scanner tape users video
> >
>
>
> --
> Gabriel B. Casella(c)(R)
>
> --
> jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> https://bugs.launchpad.net/bugs/273600
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in "jockey" source package in Ubuntu: Fix Committed
>
> Bug description:
> 810 with latest updates
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/jockey-gtk
> InterpreterPath: /usr/bin/python2.5
> NonfreeKernelModules: nvidia
> Package: jockey-gtk 0.5~alpha1-0ubuntu2
> PackageArchitecture: all
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python ...

Yes!!!
On Ubuntu 8.10 AMD64 happen the same thing! At least on live cd...
But if you install the NVIDIA driver, by NVIDIA site, after install on the
Hardware Drivers it doesn't appears that is in use the driver (which is the
same version by the graphical way or the terminal way). And all works fine
with this driver.

2008/11/13 Kom-Si <email address hidden>

> Nay, the problem persists. I installed amd64 variant of Ubuntu 8.10 today
> and couldn't start the NVIDIA driver thru System --> Administration -->
> Hardware Drivers at all. At earlier installation (regular Ubuntu 8.10 Live
> CD) I could achieve that albeit with some struggle (Jokey behaved
> strangely). Now when I try to start NVIDIA driver ver. 177 Jokey simply
> hangs with 'Downloading...' window at 0%, and doesn't do anything...
>
> I uninstalled Jockey and am downloading the driver directly thru Software
> update...
>
> On Wed, Nov 12, 2008 at 21:40, gbc921 <email address hidden> wrote:
>
> > Yes the problem was like this, after a long time that system was trying
> to
> > install the driver, (without any progress) the application crashes... But
> > this occurs only on Live CD, after installed I think that its install
> > properly.
> >
> > Thanks!
> >
> >
> > 2008/11/12 Martin Pitt <email address hidden>
> >
> > > I finally discovered one bug: if driver installation lasts longer than
> > > 10 minutes, the backend times out, and the GUI crashes with
> > > "org.freedesktop.DBus.Error.ServiceUnknown: The name :1.398 was not
> > > provided by any .service files". That's a real problem, however, it's
> > > not exactly the same crash that was reported here. That might be
> because
> > > the crash you reported is yet another problem, or just because of the
> > > slightly braindead way I used to test this.
> > >
> > > --
> > > jockey-gtk crashed with DBusException in
> dbus_sync_call_signal_wrapper()
> > > https://bugs.launchpad.net/bugs/273600
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > >
> > > Status in "jockey" source package in Ubuntu: In Progress
> > >
> > > Bug description:
> > > 810 with latest updates
> > >
> > > ProblemType: Crash
> > > Architecture: i386
> > > DistroRelease: Ubuntu 8.10
> > > ExecutablePath: /usr/bin/jockey-gtk
> > > InterpreterPath: /usr/bin/python2.5
> > > NonfreeKernelModules: nvidia
> > > Package: jockey-gtk 0.5~alpha1-0ubuntu2
> > > PackageArchitecture: all
> > > ProcAttrCurrent: unconfined
> > > ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> > > ProcEnviron:
> > >
> > >
> >
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> > > LANG=en_IN
> > > SHELL=/bin/bash
> > > PythonArgs: ['/usr/bin/jockey-gtk']
> > > SourcePackage: jockey
> > > Title: jockey-gtk crashed with DBusException in
> > > dbus_sync_call_signal_wrapper()
> > > Uname: Linux 2.6.27-4-generic i686
> > > UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev
> > > plugdev root sambashare scanner tape users video
> > >
> >
> >
> > --
> > Gabriel B. Casella(c)(R)
> >
> > --
> > jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> > https://bugs.launchpad.net/bugs/273600...

Happened to me while downloading the ATI FGLRX driver with Live CD.

This bug was fixed in the package jockey - 0.5~beta3-0ubuntu8

---------------
jockey (0.5~beta3-0ubuntu8) jaunty; urgency=low

  * Merge bug fixes from trunk:
    - Replace enabled/disabled icons with more decent variant, thanks Kenneth
      Wimer! (LP: #290239)
    - backend.py: Rewrite timeout behaviour for more robustness; do not time
      out right after a long method call.
    - Intercept crashes of the backend (which manifest as D-BUS NoReply
      error), present an error message, and restart backend. (LP: #273600)
    - jockey-gtk: Fix crash if nothing is selected in the tree view after an
      operation. (LP: #283887)
    - fglrx.py: Unconfigured driver defaults to ati, which already provides
      compositing. (LP: #285879)
  * jockey/oslib.py, install_package(): Use --force-confnew to fix hang/crash
    on "EOF on stdin at conffile prompt", since the jockey backend does not
    have any terminal or interactivity. This fixes fglrx install failure when
    the upstream installer was previously used. This still keeps .dpkg-old
    configuration backups, and using a tool like Jockey should "make it work".
    (LP: #283765)
  * data/handlers/b43.py: Add missing OSLib import. (LP: #295530)

 -- Martin Pitt <email address hidden> Mon, 24 Nov 2008 20:31:53 +0100

The error is now resolved, after updating to latest patch the error has been
resolved. Great work!

On Tue, Nov 25, 2008 at 4:50 AM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> This bug was fixed in the package jockey - 0.5~beta3-0ubuntu8
>
> ---------------
> jockey (0.5~beta3-0ubuntu8) jaunty; urgency=low
>
> * Merge bug fixes from trunk:
> - Replace enabled/disabled icons with more decent variant, thanks
> Kenneth
> Wimer! (LP: #290239)
> - backend.py: Rewrite timeout behaviour for more robustness; do not time
> out right after a long method call.
> - Intercept crashes of the backend (which manifest as D-BUS NoReply
> error), present an error message, and restart backend. (LP: #273600)
> - jockey-gtk: Fix crash if nothing is selected in the tree view after an
> operation. (LP: #283887)
> - fglrx.py: Unconfigured driver defaults to ati, which already provides
> compositing. (LP: #285879)
> * jockey/oslib.py, install_package(): Use --force-confnew to fix
> hang/crash
> on "EOF on stdin at conffile prompt", since the jockey backend does not
> have any terminal or interactivity. This fixes fglrx install failure
> when
> the upstream installer was previously used. This still keeps .dpkg-old
> configuration backups, and using a tool like Jockey should "make it
> work".
> (LP: #283765)
> * data/handlers/b43.py: Add missing OSLib import. (LP: #295530)
>
> -- Martin Pitt <email address hidden> Mon, 24 Nov 2008 20:31:53
> +0100
>
> ** Changed in: jockey (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
> https://bugs.launchpad.net/bugs/273600
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>