[Bug 252094] Re: MASTER: Poor graphics performance on Intel
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 older chipsets. So my guess is that people would still be highly unsatisfied with the driver quality, the only difference would be that the bug reports would be against an old version and would no longer useful. But, have you considered supplying a package with an older version of xserver that could run the i810 driver? Please note that I am not suggesting that Ubuntu rollback its xserver, just that it supply something like a xserver-xorg-legacy package that could replace the default xserver with an older version (one that supported i810) for users with older intel chipsets. Perhaps a little installation magic could pick the legacy driver depending on the detected hardware. I know that this is an ugly solution, and I recognize that simply fixing the bugs in the -intel driver is a more elegant approach. But, it has been over a year since Ubuntu stopped working properly on these chipsets. The most recent driver has rendered my system (and many others) completely and utterly unusable. And in all likelihood it will take many many more months before the regressions introduced by the -intel driver start to be pared down You asked for patience, but I think that the community has already been very patient. I think the most important thing at this point is to get things working again. And, ugly as it may be, this would restore basic functionality to many of the above users instantaneously (I just installed xserver 1.4.2, and my system has never worked better). In your post, you suggested that releasing an older version would inhibit our ability to work with upstream to gain real fixes to the problem In fact, I would argue that releasing a legacy driver would only allow for a more sane release plan. Reading the notes by Keith Packard that you have cited above, it seems that Xorg is essentially treating -intel as a beta. Beta software is fine for early adopters who are willing to track down bugs and take the time to file intelligent bug reports, but it is counterproductive to distribute beta software at large. It does not produce more information, it simply infuriates individuals that have become unwilling beta-testers (see some of the above comments) and produces a large number of uninformed bug reports (see some of the duplicates). I think the best way to get to a working driver is to relieve some of the presure from the Xorg team by pushing out a legacy driver that gets normal users working systems, and then let the early adopters slowly work through the bugs in the -intel driver. In your post, you also mentioned that releasing an outdated version is the wrong thing to do. Well, it certainly doesn't feel right. And if everything was as it should, every version would improve upon the previous and releasing old versions would never be necessary. But alas, this does not seem to be the case. I think the right thing to do at this point is to get things working again. -- MASTER: Poor graphics performance on Intel https://bugs.launchpad.net/bugs/252094 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365883] [NEW] jockey hangs indefinitely
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 restarted jockey-backend with the debug flag, and restarted jockey-gtk. I'll attach the output of both. The jockey-backend process hangs after printing the Installing package: nvidia-glx-180 after which I interrupted the process. The jockey-gtk process outputs nothing until jockey-backend is interrupted, after which it prints the attached. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365883] Re: jockey hangs indefinitely
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365883] Re: jockey hangs indefinitely
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365883] Re: jockey doesn't display progress or allow cancel
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365883] Re: jockey doesn't display progress or allow cancel
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 hanging, the current behavior is still something less than ideal. As is, it appears that the progress bar is only updated with file-level granularity. For something like the nvidia drivers where most of the download is in a single file, this is not so useful. Anyone without a broadband connection is going to see the progress bar sit at 0% for around 15 minutes. I suspect most people will assume it is stalled. If jockey-gtk is using python-apt then it should be possible to display the progress within each file download. Also, as I mentioned in the original post, during the download clicking cancel does nothing. I'm not sure if the download would be cancelled after the first file was downloaded, but clicking cancel should really cause immediate termination of the installation. I've updated the bug description to reflect the new information. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 284550] Re: backlight brightness oscillates
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 brightness oscillates https://bugs.launchpad.net/bugs/284550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 284550] Re: backlight brightness oscillates
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 -- backlight brightness oscillates https://bugs.launchpad.net/bugs/284550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249039] Re: GDM error on shutdown/restart
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 you receive the error message or a crash depends on the precise timing of the logout/shutdown. Neon Knight has also reported that his system will crash upon logout, but I am uncertain as to the exact behavior observed by others who have made comments. Maybe your hardware results in logout that manages to consistently avoid a crash, or maybe my hardware is particularly prone to the crash code path. It might be a different bug, but at this point the error message and the behavior at least seem consistent with this one. -- GDM error on shutdown/restart https://bugs.launchpad.net/bugs/249039 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249039] Re: GDM error on shutdown/restart
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 (logging out) to crash with a fairly high frequency, perhaps the importance should be upgraded to High. -- GDM error on shutdown/restart https://bugs.launchpad.net/bugs/249039 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
