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 PROTECTED]> 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. > -- 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
