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
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 PROTECTED] wrote:
This bug was fixed in the package jockey - 0.5~beta3-0ubuntu8
---
jockey (0.5~beta3-0ubuntu8)
Happened to me while downloading the ATI FGLRX driver with Live CD.
--
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.
--
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
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).
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
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.
** Changed in: jockey (Ubuntu)
Importance: High = Medium
Status: In Progress = Fix Committed
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 PROTECTED]
I finally
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
** Changed in: jockey (Ubuntu)
Status: Incomplete = In Progress
--
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.
--
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.
--
jockey-gtk crashed with
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.
--
jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
https://bugs.launchpad.net/bugs/273600
You received this bug notification
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???
--
jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
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.
--
jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
https://bugs.launchpad.net/bugs/273600
You received
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...
--
jockey-gtk crashed with DBusException in dbus_sync_call_signal_wrapper()
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)
--
jockey-gtk crashed with
Same problem here
--
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
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
I had the same problem as eapache.
--
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
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.
--
jockey-gtk crashed with DBusException in
forgot:
intrepid ibex updated this morning. on 64 bit.
if theres anything else you need please let me know
--
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
** Visibility changed to: Public
--
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
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
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
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
wizard1 [2008-10-13 9:08 -]:
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
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
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
28 matches
Mail list logo
