Bryce,
Thanks for the update, very informative. You mentioned in your post
several reasons for not reverting to an older, more stable version of
the -intel driver. And I agree that this would probably be counter-
productive, in my experience the -intel driver has never really been
stable on
Public bug reported:
I'm running 64-bit Jaunty, fully-patched. I just tried to install the
nvidia driver (v. 180) after a fresh install, and the downloading and
installing box hangs indefinitely at 0% progress. Clicking the cancel
button does nothing. So I ran killall jockey-backend, then
** Attachment added: jockey-backend.log
http://launchpadlibrarian.net/25913683/jockey-backend.log
--
jockey hangs indefinitely
https://bugs.launchpad.net/bugs/365883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: jockey-gtk.log
http://launchpadlibrarian.net/25913685/jockey-gtk.log
--
jockey hangs indefinitely
https://bugs.launchpad.net/bugs/365883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Summary changed:
- jockey hangs indefinitely
+ jockey doesn't display progress or allow cancel
--
jockey doesn't display progress or allow cancel
https://bugs.launchpad.net/bugs/365883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I took another look at this and it appears that jockey wasn't really hanging,
the ubuntu repositories were throttled and the downloads were progressing at a
glacial pace (as observed by checking the file sizes in
/var/cache/apt/archives/partial). While that is much better than simply
The bug from the above comment has been identified as a duplicate of bug
566095 in the upstream bug database
(http://bugzilla.gnome.org/show_bug.cgi?id=566095). This bug was fixed
in version 2.24.4 of gnome-power-manager. I have tested 2.24.4 and can
confirm it fixes the problem.
--
backlight
This bug seems to have fallen through the cracks. The original reporter
provided all of the requested information, but the bug still has not
been marked as confirmed.
I've been having the same problem and so I filed a bug on the upstream
bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=571807
Dimitrios, alas I am running hardy. From the above, it appears that
intrepid uses 2.20.8 and has the fix while hardy uses 2.20.7 and retains
the bug. But if I am mistaken, please correct me. As for the crashes,
the bug appears to result from a race condition in the cleanup, so I
expect whether
I am also regularly encountering this bug, and wanted to second Neon
Knight's point. Most of the time it simply causes a warning in the
system logs, but occasionally (~5% of the time) it causes the entire
graphical interface to hang indefinitely. Given that it causes a very
common behavior
10 matches
Mail list logo
