[Ubuntu-x-swat] [Bug 1839555] Re: X server backports for PRIME render offloading
Is there any plan to add this functionality to the 18.04 HWE stack? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1839555 Title: X server backports for PRIME render offloading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1839555/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1839555] [NEW] X server backports for PRIME render offloading
Public bug reported:
Configuring PRIME render offloading requires changes to the X server
which have been accepted upstream but are not yet present in any
release. These changes do not break the driver ABI and should be safe to
backport to existing X servers shipped in distributions like Ubuntu.
The required commits are:
* 7f962c70b6d9c346477f23f6c15211e749110078 - xsync: Add resource inside of
SyncCreate, export SyncCreate
* 37a36a6b5b887d5c5a17a6931ceba8ad5d1bb6d5 - GLX: Add a per-client vendor
mapping
* 8b67ec7cc6fda243480a5a8ca118b66242f3eb2c- GLX: Use the sending client for
looking up XID's
* 56c0a71fdd94a008e5d746261f70a713c4767f93 - GLX: Add a function to change a
clients vendor list
* b4231d69028adc8123801a7552b40a15ea928d1b - GLX: Set
GlxServerExports::{major,minor}Version
These commits must be backported to an X.org X server of at least
version 1.20, as this is the first version with support for server-side
GLVND.
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1839555
Title:
X server backports for PRIME render offloading
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1839555/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1104209] [NEW] Pointer can't cross screens on multiple X screen configuration
Public bug reported: This bug is well described on the freedesktop.org bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54654 In short, the cursor can't move beyond one screen when a server is running multiple X screens. The bug has been fixed upstream; the fix should be applied to all Ubuntu releases using a 1.13 X server. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Patch added: Patch from Peter Hutterer https://bugs.launchpad.net/bugs/1104209/+attachment/3498460/+files/0001-dix-fix-zaphod-screen-scrossing-54654.patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1104209 Title: Pointer can't cross screens on multiple X screen configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1104209/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1057093] Re: Installing nvidia-current should blacklist gfxpayload
Hi Steve, While the NVIDIA driver often happens to work with consoles other than the standard VGA text mode console without any user-visible symptoms, any console configuration besides VGA text mode is not supported by the driver, and use of any alternative consoles is directly linked, in many cases, to stability problems and graphical corruption. Here are some recent examples of issues users have encountered as a result of using framebuffer consoles with the NVIDIA driver; these symptoms were observed with a framebuffer console present, and absent when using a VGA text mode console on the same system: - Complete graphics freeze in some situations - recoverable by restarting X. - Inability to restore console after suspend/resume. - Scribbling of data from the console on top of the X screen driven by the primary GPU. Users shouldn't be exposed to such issues in the name of graphical boot splashes. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1057093 Title: Installing nvidia-current should blacklist gfxpayload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1057093/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1057093] [NEW] Installing nvidia-current should blacklist gfxpayload
Public bug reported: The NVIDIA driver does not interact well with consoles other than plain VGA text consoles, such as vesafb. NVIDIA recommends that users run VGA text consoles in conjunction with the NVIDIA driver. Many distributions, such as Ubuntu, enable a framebuffer console by default. It appears that Ubuntu has a mechanism (via update-grub- gfxpayload) to blacklist the framebuffer console for specific hardware. It appears that the nvidia-current package includes a gfxpayload rules file, which includes a (commented out) example rule to blacklist the framebuffer console for all NVIDIA devices. I confirmed that after installing the nvidia-current package and rebooting, the system was using a vesafb framebuffer console. I edited /usr/share/nvidia-current/nvidia-current.grub-gfxpayload and uncommented the example rule, ran update-grub-gfxpayload, rebooted, and confirmed that the system was using a VGA text console. This rule should be enabled by default as part of installing the nvidia- current package. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1057093 Title: Installing nvidia-current should blacklist gfxpayload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1057093/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1037896] Re: Starting Firefox kills xserver immediately
The current release 304 drivers should work fine with 1.13. I'll check this out on my Quantal machine. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1037896 Title: Starting Firefox kills xserver immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037896/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1037896] Re: Starting Firefox kills xserver immediately
There was a change in the layout of an X server data structure, which caused the NVIDIA OpenGL driver to call into invalid function pointers: http://lists.x.org/archives/xorg-devel/2012-August/033307.html This should be fixed in the next 304 release after 304.37. Thanks for reporting this. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1037896 Title: Starting Firefox kills xserver immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037896/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
@tye3ow: In that case, you are probably experiencing a different issue, as we have identified a specific problem that was introduced between the 290 and 295 series of drivers that we believe is responsible for many of the reports here. The next 304 release (the fix is not in 304.32) will contain a fix for the above described problem. This driver should be released very soon. If you continue to experience problems after upgrading to the next 304 release when it's available, please file a separate bug instead of continuing to update this bug. When you file that bug, please try to provide as much detailed information about the problem as possible. (See my comment #144 here.) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
@joelm, thanks for providing that. You provided three backtraces. You included a snippet from dmesg with backtrace 1: can you confirm that you didn't see the same info from the kernel when you captured backtraces 2 and 3? Also, when did you generate that nvidia-bug-report.log file? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
At an above linked forum thread, they were able to reproduce this bug on a quadro fx4600. They are hoping to fix it this month, but I'd guess it will be next month. The thread is now password protected. Sorry if there is any confusion, but the issue I believe you are referring to, which we do have an internal reproduction of, is not known to necessarily be the same issue as what people are describing here. We believe that some people on this thread might be affected by this issue, but as I said earlier, the reports on this thread conflict with each other on many levels, and at this time, I find it hard to believe that everybody reporting here is actually experiencing exactly the same problem. This is why, despite the seemingly similar reports here, it is important that as much detail about the specific problem each person is experiencing be provided. I should note that the reproduction we have in house of the issue that we believe may be related to some of the reports here is on a single system so far: attempts to reproduce the problem on other systems so far have failed; we do not yet understand what is specific to this system that allows it to reproduce the issue while others do not. The person who eventually reproduced the issue internally went through dozens of systems before finding the one that finally reproduced it. Also, the issue we have reproduced internally has specific reproduction steps. The reports here lack good reproduction steps. For reference, the specific reproduction steps given are: Repro steps (A): 1. Open Firefox and play video from the link http://www.adobe.com/devnet/flash/articles/vidtemplate-engage-with-flash.html 2. Make it full screen 3. Just keep moving the mouse cursor over the video; after some time, the X server will crash. Repro steps (B): 1. Open 4 to 5 seperate Firefox windows and play youtube HD videos 2. Make sure to view with large player (no need to make it fullscreen) 3. After some time (say for 3 to 5min), we can observe an X server crash. This is reproducible regardless of whether or not VDPAU is used. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
@natew: NVIDIA does not have access to the nvnews.net forum at this time, either. I was not directly involved in the attempts to reproduce the issue described above, but as reported by the person who did reproduce this issue, we did try several systems with chips that are similar to the GeForce 285m, without success. I see that you're the original reporter of this bug on launchpad, and you have posted a backtrace from gdb captured during the crash. Thanks for that, but to make the backtrace more readable, do you think you could capture another one with debugging symbols installed for the X server, and with the DSO load base of nvidia_drv.so within X captured? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
@natew: I gave some basic guidance on how to get debug symbols for X installed, and how to determine nvidia_drv.so's DSO load base in comment #144 here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers/+bug/973096/comments/144 Specifically, see (3a) and (3c). Let me know if you need any additional clarification beyond what's described there. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
Hi everybody, Like I said earlier, I've personally been using Precise with Unity on one of my main test machines since the alpha stage, and haven't seen any X crashes that weren't due to bugs that have since been fixed, and I certainly haven't seen random, frequent X crashes like what seems to be described here. That machine has its drivers and GPUs swapped frequently, and for as long as I have been using Precise, I have always used 295 or later drivers on it. (Compiz does seem to crash frequently, but it always recovers, without disturbing any of the applications or windows I have open.) In addition to my own personal experience, which is obviously a tiny sample, the driver goes through extensive automated and manual testing on many different hardware configurations, and on a variety of distributions, including Ubuntu 12.04. We haven't seen any issues that cause X to crash sporadically, as seems to be described here. With that in mind, we're obviously missing something important that's required to reproduce this bug (if it is even just a single bug: it's hard to tell, since the symptom is fairly generic). If we can collect as much detail as possible from everybody who is affected, that would help us understand what is happening better. The more information you provide, the better our chances for reproducing the issue at NVIDIA. Please provide as many of the following as possible: 1) An nvidia-bug-report.log file, generated immediately after a crash. This can be generated by running the script `nvidia-bug-report.log.sh`, which is included as part of the driver install. The script requires superuser privileges to collect system information, so you should run it with sudo. The script will save a file called nvidia-bug-report.log.gz to your current working directory. 2) A detailed description of what you were doing at the time of the crash. 3) If you are familiar with using gdb, stack traces from the crashing server, with X debug symbols installed, would be very helpful. If you're not familiar with gdb, but want to try to provide a stack trace anyway, you can try following these steps: a) Install X debug symbols (sudo apt-get install xserver-xorg-core-dbg) b) Start your desktop session, as normal c) For good measure, capture the DSO load base of the NVIDIA driver, in case it shows up in the stack trace of the crashing server. (grep nvidia_drv.so /proc/`pidof X`/maps) - you may need to do this as root. Stash this information away, and if nvidia_drv.so shows up in your backtrace when you get one, submit it along with everything else. d) Log into your system *FROM ANOTHER MACHINE* and attach a debugger to the already running X server (gdb Xorg `pidof X`): it's important that you do this from another machine over ssh, because after the debugger is attached, X will be frozen until you continue. If you start the debugger from a VT on the same machine, when X crashes later, it will be frozen, and you probably won't be able to switch to your VT running the debugger e) After the debugger is attached, type continue (or just c) at the gdb prompt and hit enter f) Use your system, leaving the debugger attached the whole time. If X crashes, the debugger will stop. Go to your machine running the debugger, and type backtrace (or just bt) and hit enter to get a backtrace at the time of your crash. If the backtrace is long, you may have to hit enter a few more times to see the rest of it. Copy and paste this backtrace, and submit it along with the nvidia-bug-report.log. It does sound like some boards are affected, and some are not, though the boards reported so far don't have a whole lot in common with each other. We will do our best to match the configurations reported here, in hopes of reproducing this crash. Thanks in advance for your help. In the meantime, for those who are affected, it does sound like unity-2d is more stable, so perhaps you can switch to unity-2d as a temporary workaround while waiting for this issue to be resolved. Alberto, has anybody at Canonical been able to reproduce this? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 973096] Re: Nvidia driver causes xorg crash
Hi Alberto, There seem to be a lot of reports here, and it's hard to tell whether they're all related. We are currently investigating reports of a regression with very recent versions of Flash where the X server can crash when playing videos, which it sounds like many of the users here are reporting, but there are many other reports here which sound completely unrelated to Flash, including the post from the original reporter. The root cause of the Flash regression is not yet known, but in the meantime, we have found that it's possible to work around this particular issue by disabling Flash's use of VDPAU for hardware acceleration of video playback. It sounds like a lot of people here are experiencing general stability problems with Unity and the NVIDIA driver, and using other desktop sessions, older drivers, or different GPU hardware/drivers avoids these issues. I haven't personally seen issues like this on any of my machines running Unity on Precise, nor am I aware of any reports like this coming from our internal testing on various distributions, including Ubuntu. I understand that the reports are of crashes which are random and sporadic in nature, but any efforts to isolate specific workflows or actions that seem to trigger the crashes or at least make it more likely that X or the desktop session will crash so that these problems can be reproduced on demand will make it much easier to investigate what is happening. If there appear to be multiple problems that share similar symptoms (Nvidia driver causes xorg crash can describe a multitude of issues), they should preferably be separated out into distinct bug reports. (It also seems like at least some people on this bug report are reporting issues with non-NVIDIA drivers and/or hardware: these reports, at least, definitely don't belong in an Nvidia driver causes xorg crash report.) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 982485] Re: nvidia 295.40 breaks unity 3d
Are the other affected users also running GeForce 6200 or similar boards? As an experiment, try reverting the security patch here: ftp://download.nvidia.com/XFree86/patches/security/CVE-2012-0946/ You should be able to do this without reinstalling the whole driver by manually reverting the patch in /usr/src/nvidia-current-295.40 and then rebuilding just the kernel module using DKMS. (May want to have X stopped / module unloaded while doing this.) GeForce 6xxx series isn't susceptible to the vulnerability. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2012-0946 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: nvidia 295.40 breaks unity 3d To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 982485] Re: nvidia 295.40 breaks unity 3d
Effenberg, I think you're experiencing a different set of problems than the original reporters, who have a regression in 295.40 compared to 295.33. What's your display configuration? If you have multiple large displays, or multiple displays with different resolutions, it is sometimes necessary to stay in the maximum performance state at all times. Is your GPU still unable to clock down if you use a single display, possibly at a lower resolution? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/982485 Title: nvidia 295.40 breaks unity 3d To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982485/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 959842] Re: root escalation via /dev/nvidia0
Okay, will they need any information from NVIDIA to populate the database entry, or will they do their own research? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/959842 Title: root escalation via /dev/nvidia0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/959842/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 931967] Re: Corrupted graphics after the login until the unity launcher appears
If it's true that similar issues show up in Nouveau, and on AMD boards (radeon? fglrx?), then it probably makes the most sense to track down the regression better first. There's still a chance that there could be bugs in all of the affected drivers that are causing this, but it would be great if we could begin investigating with some more solid information about the problem first. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/931967 Title: Corrupted graphics after the login until the unity launcher appears To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/931967/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 877682] Re: [Latitude E6510 / Thinkpad W510/T510] External Video inoperative with nVidia current
The 295 driver package will contain the control panel fix. However, the original problem reported in this bug does not sound like the control panel bug. It's not clear to me if the other comments on this bug are actually reporting the same issue reported in this bug, or the control panel issue as described in the linked forum posts. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/877682 Title: [Latitude E6510 / Thinkpad W510/T510] External Video inoperative with nVidia current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/877682/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 877682] Re: [Latitude E6510 / Thinkpad W510/T510] External Video inoperative with nVidia current
I don't think it's related. I don't see any reports of X crashing here,
just inability to use external displays. Furthermore, the bug referenced
in that changelog entry was introduced in the 295 timeframe and this bug
is reported in 280.
The issue described here also doesn't seem to exactly match the issue
described on the ubuntuforums.org and forums.nvidia.com links: here it
sounds like neither external display is working, and on the forum posts
it sounds like the control panel is freezing when enabling two external
monitors simultaneously.
The latter is a known bug in the control panel which was fixed in the
290 timeframe. The former sounds like a distinct issue to me, but maybe
I've misunderstood the report. It would be good to clarify with the
original reporter.
For the control panel bug, you don't want to do a full driver update for
that bug, you can just patch the control panel:
--- a/src/gtk+-2.x/ctkdisplayconfig-utils.c
+++ b/src/gtk+-2.x/ctkdisplayconfig-utils.c
@@ -,8 +,8 @@
if (!screen-displays) {
screen-displays = display;
} else {
-nvDisplayPtr last = screen-displays;
-while (last) {
+nvDisplayPtr last;
+for (last = screen-displays; last; last = last-next_in_screen) {
if (!last-next_in_screen) {
last-next_in_screen = display;
break;
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/877682
Title:
[Latitude E6510 / Thinkpad W510/T510] External Video inoperative with
nVidia current
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/877682/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 933212] Re: FBO-using applications unresponsive for a long time after modeswitch
What driver version is this reported on? There is a known bug in the driver that resulted in momentary hangs during modeswitch for some FBO applications. It was fixed in the 295 timeframe. The first public driver with the fix was the 295.17 beta. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/933212 Title: FBO-using applications unresponsive for a long time after modeswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/933212/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 753144] Re: focused, or maximized windows blank
Hello all, Thanks for reporting this bug. Since it seems to be quite active on launchpad and users are writing in to linux-bugs about it, I just wanted to mention that NVIDIA is aware of the issue. We've been tracking it for a while under NVIDIA internal bug number 822418. It does appear to be specific to older cards in low video memory situations; for integrated GPUs you can allocate more memory to work around the problem, but for discrete GPUs this isn't a possibility. We do not currently have an estimated time for delivery of a fix. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/753144 Title: focused, or maximized windows blank To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/753144/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 650539] Re: Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil, Stellarium, skype, VLC crashes Xserver
Just set the DISPLAY variable to your third display's X screen. Example, if your third display is screen :0.1: DISPLAY=:0.1 xterm -- Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil, Stellarium, skype, VLC crashes Xserver https://bugs.launchpad.net/bugs/650539 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 650539] Re: Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil, Stellarium, skype, VLC crashes Xserver
TwinView is only supported when two displays are used on one GPU. -- Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil, Stellarium, skype, VLC crashes Xserver https://bugs.launchpad.net/bugs/650539 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
The 260.19.04 driver doesn't have this fix yet. It will be a later version that does. -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 613458] Re: After upgrading to latest kernel i get a black screen and cant do anything except ctrl+alt+delete to reboot
The 256.xx driver should work fine with kernel 2.6.35. I just upgraded my Maverick test machine to 2.6.35-14 and I'm not having any problems with the NVIDIA driver. The logs attached to this bug all appear to have been generated with 2.6.35-11. I'm assuming that the system was rebooted into the older kernel to generate them. Can the system be sshed into when the problem occurs? If an nvidia-bug- report.log can be generated (`sudo nvidia-bug-report.sh`) when the actual failure is occurring, then it might help us figure out what's happening. (If it helps, you might want to configure your system not to start X by default when booting: edit /etc/init/gdm.conf and comment out the start on conditions. When you reboot you should be presented with a text login prompt. This will allow you to, e.g., determine the IP address so that you can ssh in from another system before starting X. You can then start X with `sudo start gdm` when you're ready, and if the ssh session is still responsive, generate an nvidia-bug-report.log.) -- After upgrading to latest kernel i get a black screen and cant do anything except ctrl+alt+delete to reboot https://bugs.launchpad.net/bugs/613458 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 481599] Re: When using NVIDIA driver wrong resolutions are picked causing *out of range* error from monitors OSD and cannot display analog signal from VGA output to TV because of
The NVIDIA driver builds its list of available modes from several sources. The most important of these are the display's EDID, and the X server's list of VESA standard modes. The ModeValidation NoXServerModes option removes the X server provided modes from this pool. It seems that in this case, one or more of the VESA standard modes provided in the X server was incompatible with the particular display hardware being used. We do try to eliminate potentially incompatible modes from the server's list by checking them against the pixel clock and display dimensions in the EDID, but it's possible to have an incompatible mode pass these tests once in a while. It would be useful to know exactly which modes are failing, and to have a little bit more information about what is happening during the mode validation process. Setting Option ModeDebug true in the Screen section of xorg.conf will print detailed mode validation information in the log. -- When using NVIDIA driver wrong resolutions are picked causing *out of range* error from monitors OSD and cannot display analog signal from VGA output to TV because of refresh rates https://bugs.launchpad.net/bugs/481599 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 578517] [NEW] Hang after pressing enter in VT that X was started from when using startx
Public bug reported: Binary package hint: xorg Steps to reproduce: 1. stop gdm 2. Run startx from a VT 3. Once the desktop is up, open a few windows. 4. Switch back to the VT that you ran startx on 5. Hit enter 6. Switch back to the VT that X is running on With the nouveau and vesa drivers, what we see is that all windows are now blank and filled with white, and the GNOME menu and shortcut icons in the top panel are missing. Other items in the panel appear to be unaffected and are responsive to input. With the NVIDIA binary driver, all we see is a black screen with a cursor. Not too many will be starting desktop sessions with startx, let alone switching to the VT they started X from and hitting enter, but this still probably deserves some investigation. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Mon May 10 21:34:53 2010 DkmsStatus: Error: [Errno 2] No such file or directory GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory LiveMediaBuild: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MachineType: OEM OEM ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 11/14/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 132-BL-E758 dmi.board.vendor: EVGA dmi.board.version: Tylersburg dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/14/2008:svnOEM:pnOEM:pvrOEM:rvnEVGA:rn132-BL-E758:rvrTylersburg:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Hang after pressing enter in VT that X was started from when using startx https://bugs.launchpad.net/bugs/578517 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 578517] Re: Hang after pressing enter in VT that X was started from when using startx
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/48237562/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/48237563/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48237564/Dependencies.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/48237565/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/48237566/GdmLog1.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/48237567/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/48237568/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/48237569/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/48237570/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/48237571/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/48237572/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/48237573/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/48237574/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/48237575/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/48237576/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/48237577/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/48237578/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/48237579/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/48237580/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/48237581/xkbcomp.txt -- Hang after pressing enter in VT that X was started from when using startx https://bugs.launchpad.net/bugs/578517 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 563100] Re: Mouse movement corrupted with Xinerama enabled
The recent NVIDIA driver release does not fix this problem. This is a problem with the X server. The problem exists upstream and affects a number of other Linux distributions as well, so it's not specific to Ubuntu. -- Mouse movement corrupted with Xinerama enabled https://bugs.launchpad.net/bugs/563100 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 563100] Re: Mouse movement corrupted with Xinerama enabled
The recent NVIDIA driver release does not fix this problem. This is a problem with the X server. The problem exists upstream and affects a number of other Linux distributions as well, so it's not specific to Ubuntu. -- Mouse movement corrupted with Xinerama enabled https://bugs.launchpad.net/bugs/563100 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 573557] Re: nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
Thanks for all the reports. We have tracked this down to a problem with the kernel's VGA arbiter trying to move VGA ownership to a GPU that hasn't POSTed. We're working with the developers of the VGA arbiter to get this fixed in the kernel. In the meantime, we have a patch which works around the issue by preventing the VGA arbiter from moving VGA ownership away from the default device. It is attached as NVIDIA_kernel-195.36.24-682377.diff. You can apply the patch by downloading the latest installer from http://www.nvidia.com/object/linux-display-ia32-195.36.24.html (32-bit) or http://www.nvidia.com/object/linux-display-amd64-195.36.24.html (64-bit) and running the installer with the --apply-patch /path/to/patch.diff option. This will create a patched installer with a name ending in -custom.run, which will install a driver with this workaround. If you're not comfortable with applying the patch yourself, or with working out the conflicts between the driver as installed by the NVIDIA installer and the driver as installed by Jockey (the restricted drivers manager) then please wait until an updated package is available through Jockey. ** Patch added: NVIDIA_kernel-195.36.24-682377.diff - patch with workaround for VGA arbiter multi-GPU bug http://launchpadlibrarian.net/47710249/NVIDIA_kernel-195.36.24-682377.diff -- nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system https://bugs.launchpad.net/bugs/573557 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 548362] Re: nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
Thanks for all the reports. We have tracked this down to a problem with the kernel's VGA arbiter trying to move VGA ownership to a GPU that hasn't POSTed. We're working with the developers of the VGA arbiter to get this fixed in the kernel. In the meantime, we have a patch which works around the issue by preventing the VGA arbiter from moving VGA ownership away from the default device. It is attached as NVIDIA_kernel-195.36.24-682377.diff. You can apply the patch by downloading the latest installer from http://www.nvidia.com/object/linux-display-ia32-195.36.24.html (32-bit) or http://www.nvidia.com/object/linux-display-amd64-195.36.24.html (64-bit) and running the installer with the --apply-patch /path/to/patch.diff option. This will create a patched installer with a name ending in -custom.run, which will install a driver with this workaround. If you're not comfortable with applying the patch yourself, or with working out the conflicts between the driver as installed by the NVIDIA installer and the driver as installed by Jockey (the restricted drivers manager) then please wait until an updated package is available through Jockey. ** Patch added: NVIDIA_kernel-195.36.24-682377.diff - patch with workaround for VGA arbiter multi-GPU bug http://launchpadlibrarian.net/47710284/NVIDIA_kernel-195.36.24-682377.diff -- nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system https://bugs.launchpad.net/bugs/548362 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532436] Re: nvidia driver sometime does not load at boot
This sounds like it might the same as this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563624 Could the affected people please try increasing the GDM timeout (GdmXserverTimeout in /usr/share/gdm/defaults.conf) to see if it alleviates the issue? ** Bug watch added: Debian Bug tracker #563624 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563624 -- nvidia driver sometime does not load at boot https://bugs.launchpad.net/bugs/532436 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532436] Re: nvidia driver sometime does not load at boot
Hmm, I'll fire up my Ubuntu Lucid system and see if the setting for GDM timeout has moved somewhere else. It might be in another file, or in gconf, or who knows where... -- nvidia driver sometime does not load at boot https://bugs.launchpad.net/bugs/532436 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532436] Re: nvidia driver sometime does not load at boot
Hi Mike, you're right; I can't seem to figure out where the GDM configuration went... Try creating a simple custom.conf file at /usr/share/gdm/custom.conf containing the following two lines: [daemon] GdmXserverTimeout=60 If this doesn't work, it will tell us that either: 1) Your problem is not the GDM timeout issue 2) The version of GDM distributed with Lucid ignores custom.conf 3) Both of the above -- nvidia driver sometime does not load at boot https://bugs.launchpad.net/bugs/532436 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 563100] Re: Mouse movement corrupted with Xinerama enabled
This is a known bug in Xorg 1.7. https://bugs.freedesktop.org/show_bug.cgi?id=24986 We did investigate this about a month ago, until we discovered that it was a bug in X. At the time, it did reproduce in Debian unstable, though the bug report here suggests that it currently does not. The freedesktop.org bug report lists an available patch, so it's possible that Debian unstable has applied this patch or their own. It's also possible that the server layout that the original poster tested with in Debian unstable is different: this bug only reproduces when screens with a higher ID are placed to the left of screens with a lower one. ** Bug watch added: freedesktop.org Bugzilla #24986 http://bugs.freedesktop.org/show_bug.cgi?id=24986 -- Mouse movement corrupted with Xinerama enabled https://bugs.launchpad.net/bugs/563100 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532436] Re: nvidia driver sometime does not load at boot
I haven't seen this happen during any of my recent testing with Lucid. If it is a timing issue, it might be easiest to pursue a repro on the same hardware. I'll try to get access to one of these notebook systems (Dell Studio XPS 1340) for testing. In the meantime, if anybody else is experiencing this on other systems, it would be helpful to know about those systems as well. -- nvidia driver sometime does not load at boot https://bugs.launchpad.net/bugs/532436 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 522328] Re: [Test xpr-008] Lucid upgrade broke when upgrading from manually installed nvidia proprietary drivers
Is the nvidia kernel module being rebuilt after the upgrade? It's expected not to work after upgrading the kernel, if it's not rebuilt for the new kernel. -- [Test xpr-008] Lucid upgrade broke when upgrading from manually installed nvidia proprietary drivers https://bugs.launchpad.net/bugs/522328 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 519538] Re: System freeze when logging into GNOME on fresh Lucid install
This no longer happens for me after an aptitude update; aptitude upgrade a few days ago. Please close this bug. Thanks, Daniel -- System freeze when logging into GNOME on fresh Lucid install https://bugs.launchpad.net/bugs/519538 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
