[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
> should it fail how can I get the log when my system completely locks up and dies? My understanding of the bug is that it occurs when the NVIDIA driver tries to bring up the DisplayPort link on certain DisplayPort monitors. You should be able to drive the system in text mode with a failing driver, to capture the log. One way to do that would be to add "systemd.unit=multi-user.target" to the kernel command line. (When the bootloader menu comes up, edit the boot options and add this argument to the line that starts with 'linux'.) If you happen to have another system on the same network you can even try SSHing into the system that reproduces the problem, then start the graphical session manually with `sudo systemctl isolate graphical`, and if the crash doesn't take down the SSH session, you ought to be able to generate the log file while the problem is occurring. (Log files taken while a bug is actively being reproduced tend to be the most useful.) Depending on the exact nature of the crash, you may even be able to SSH into a system which has already crashed, without having to go to the effort of starting it in text mode first. > In that eventuality I've only been able to recover by booting an older kernel with the older drivers. Will that not invalidate the log content on restart? It may, or may not. nvidia-bug-report.sh attempts to capture logs from the previous boot, if they have been retained. If you do find that you are unable to capture a log file using a driver version which reproduces the problem, just make sure to note that you captured the log file after rebooting to a known good driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Hello, NVIDIA employee here. Can those who are still experiencing problems please provide the following information? * NVIDIA driver version installed * NVIDIA GPU model * Exact model of affected monitor An nvidia-bug-report.log will capture the driver version and GPU model, along with some other useful information, though possibly not the monitor model since the system may be crashing before the EDID can be read. You can generate an nvidia-bug-report.log file by running `nvidia- bug-report.sh` as root. This will create a new file named nvidia-bug- report.log.gz in your current directory. As for the fix being absent from the release notes, that was an accidental omission. The fix should be present in 460.91.03 and later, as well as all publicly released 470 drivers. Unfortunately, the fix did not make it into 465 before support for the 465 series was discontinued. We will want to collect the relevant information for anybody still experiencing problems with DP monitors so that any remaining issues can be addressed as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930937] Re: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop
Tested in a clean focal chroot. The dependency resolution works as expected, allowing the package to be installed without pulling in all of GNOME, but only if the "universe" repository component is enabled. If I have only "main" enabled, then dependency resolution fails with the following: # apt install screen-resolution-extra Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: screen-resolution-extra : Depends: policykit-1-gnome but it is not installable or gnome-shell but it is not going to be installed or polkit-1-auth-agent E: Unable to correct problems, you have held broken packages. I'm not sure if there's a reason apt doesn't just fall back to selecting gnome-shell when policykit-1-gnome isn't available, due to being in a disabled repository. Perhaps this might be expected behavior, but since there is a change in behavior compared to how the dependencies were previously set up, I'm not sure if the change is appropriate for an SRU. At least for default desktop installations, I imagine the difference wouldn't be noticeable, since gnome-shell would already be installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930937] [NEW] Default dependency resolution in Focal pulls in full GNOME Desktop
Public bug reported: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome- shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia- settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. ** Affects: screen-resolution-extra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: Default dependency resolution in Focal pulls in full GNOME Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905591] Re: no brightness control in {455, 460} after update from 450
The workaround suggests that there's an interaction between the NVIDIA
driver and another kernel module at play here. Presumably, adding the
NVIDIA kernel modules to the initrd causes them to be loaded before the
other module. Maybe video.ko, which registers its own brightness
handler?
The modeswitch glitch should probably be tracked as a separate issue.
Can somebody who is experiencing this glitch provide an example video?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905591] Re: no brightness control after update from 450 to 455
Can somebody with an affected system please try with one of the recently released 460.xx drivers? There were some brightness regressions that were resolved in the 460 series that may be related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905591 Title: no brightness control after update from 450 to 455 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854985] [NEW] pm-utils overrides runtime power management mode for audio devices
Public bug reported: In newer Ubuntu 18.04 HWE kernels, it is possible for GPU HDA controllers to be dynamically runtime-suspended if the HDA's power/control mode is set to "auto". However, pm-utils explicitly sets this to "on" when resuming, which prevents runtime power management of these devices from working as intended. ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854985 Title: pm-utils overrides runtime power management mode for audio devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1854985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831945] Re: HDMI/DP audio: ELD not updated on hotplug event
Sorry, I didn't notice that this bug had expired, or that it was waiting on log files. I don't have the system that I originally reproduced the issue on set up any more, but it should be easily reproducible. I'll set up another system to reproduce and generate the requested log files, but in the meantime, I'm setting this to "Confirmed" anyway since this is really just a straightforward request to backport a change that fixes a kernel regression. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831945 Title: HDMI/DP audio: ELD not updated on hotplug event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824282] Re: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU
Would it be possible to change the "intel" profile to no longer alias the nvidia.ko and nvidia-uvm.ko modules to "off"? The blacklisting can remain, and would prevent the modules from being loaded automatically in response to the device being present, but wouldn't prevent them from being explicitly loaded if desired. Since I imagine the reason for preventing the modules from loading is to allow the NVIDIA GPU to be turned off via ACPI, would it be possible to attempt unloading the modules before attempting to shut off the GPU? If they fail to unload, it's presumably because they're in use, so shutting off the GPU doesn't make sense, anyway. Going the other way, it could also be useful to add a udev rule or some other trigger to turn the GPU back on if it's off and somebody tries to load nvidia.ko. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824282 Title: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1824282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828084] Re: Kernel modules generated incorrectly when system is localized to a non-English language
amd64 counts as x86 for the purposes of supported architectures in Linux, and x86 does have the C version of recordmcount. Comment #3 includes a list of architectures that lack the C version of recordmcount. Of those architectures, ppc64le is the only one that is supported by the NVIDIA driver (the test case described in the reproduction steps). I did try to create a reproduction case independent of the NVIDIA driver, but was unsuccessful, as simpler kernel modules failed to cause a panic, and I hadn't isolated what specific behavior of the NVIDIA driver is problematic when recordmcount fails to run. One troubleshooting technique you can use to verify whether recordmcount.pl is working when localization options are set is to instrument the Kbuild makefiles to record a checksum of the object file recordmcount is run against before running recordmcount and again after it has run. If recordmcount fails to run the checksums will be the same. Note that this is only useful on architectures which use recordmcount.pl rather than the C version, as the C version has no dependency on parsing the output of objdump. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828084 Title: Kernel modules generated incorrectly when system is localized to a non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831945] Re: HDMI/DP audio: ELD not updated on hotplug event
** Patch added: "Patch generated from the upstream commit that fixes this issue" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+attachment/5269215/+files/hda.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831945 Title: HDMI/DP audio: ELD not updated on hotplug event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831945] [NEW] HDMI/DP audio: ELD not updated on hotplug event
Public bug reported: When using HDMI or Displayport audio, the EDID-like Data (ELD) fails to update properly when hotplugging or hot-unplugging displays. This in turn prevents tools like the GNOME sound settings control panel from accurately presenting the system's current audio capabilities. How reproducible: Hot plug and hot unplug an audio-capable display and observe the state of the ELDs, either by directly reading the ELD files in /proc/asound/card*/eld* or by examining the available audio output devices in the GNOME sound settings control panel. Steps to Reproduce: 1. Log into a desktop session with no audio-capable displays plugged in 2. Plug in an audio-capable display 3. Open the GNOME sound settings control panel Actual results: The audio-capable display is not selectable as an output device. Expected results: The audio-capable display should be selectable as an output device. Additional info: This bug has been fixed upstream with commit 37a3a98ef601f89100e3bb657fb0e190b857028c. Applying this change alone to the bionic 4.18 HWE kernel is sufficient to allow the expected behavior to occur. It is likely to be sufficient to fix the same bug, assuming it exists, in Cosmic, but neither the presence of the bug nor the sufficiency of the patch were tested. The bug is likely not present in Disco, but this was not tested. This behavior was observed on a system with an NVIDIA GPU running the NVIDIA proprietary driver. The particular NVIDIA GPU on the system is not currently compatible with Nouveau. It is possible and likely that this problem is also reproducible on other systems which do have GPUs that are compatible with Nouveau, and even on systems with HDMI or Displayport connectors being driven by non-NVIDIA GPUs. When the ELD fails to update in response to a hotplug event, an update can be forced by accessing the underlying ALSA codec directly. For example, playing an audio stream directly via ALSA or even just reading from the /proc/asound/cardX/codec#Y file will cause the ELD to become updated. This is of course unnecessary if the patch which fixes the issue is applied, but it does offer a somewhat simple workaround for affected users until the patch can be backported. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831945 Title: HDMI/DP audio: ELD not updated on hotplug event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830975] [NEW] Old style NVIDIA package installs configuration snippet to an unusual location
Public bug reported: The old-style NVIDIA package (used prior to Bionic) installs an X configuration snippet to: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm- outputclass.conf The purpose of this configuration snippet is to configure DRM OutputClass-based driver matching so that the NVIDIA driver can be loaded without needing to explicitly configure it. Due to its location, however, it ends up not being read by the X server. This isn't a problem in distros before Bionic, since up until Artful, the X server was patched to add "nvidia" to the X server's own auto- detected driver list, so the OutputClass-based matching was redundant. However, if a system running Bionic or newer has an NVIDIA driver package from Artful or earlier installed, the location of this file is problematic, as the NVIDIA driver can no longer be autoconfigured from either the X server's internal driver list nor the OutputClass-based matching. Normally, a user wouldn't end up with an old-style driver package on a newer distro, but one possible scenario which could lead to this condition is if an NVIDIA driver package is installed via an external repository (for example, the NVIDIA CUDA repositories) on an Ubuntu version that uses the older packaging format, then the system is upgraded to a newer version that uses the newer packaging format. Third party repositories are disabled as part of the do-release-upgrade process, and the NVIDIA driver package does not get updated. The packages continue to function, but the placement of the nvidia-drm- outputclass.conf file prevents X from selecting the NVIDIA X driver without explicit configuration. I have confirmed that moving this file one level up, so that its parent directory is /usr/share/X11/xorg.conf.d allows the OutputClass-based matching to function as expected. ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830975 Title: Old style NVIDIA package installs configuration snippet to an unusual location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1830975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828084] Re: Kernel modules generated incorrectly when system is localized to a non-English language
Yes, that's the one. The kbuild maintainer modified the commit message to add a maintainer Signed-off-by line. I would say that any kernel versions that are shipped for actively maintained versions of Ubuntu that support hardware platforms that don't use the C version of recordmcount: for file in arch/*/Kconfig; do if ! grep '^[[:space:]]*select HAVE_C_RECORDMCOUNT $file > /dev/null; then echo $file | cut -f2 -d/; fi; done alpha arc c6x h8300 hexagon ia64 m68k microblaze nds32 nios2 openrisc parisc powerpc riscv s390 sh um unicore32 xtensa This particular problem was observed on powerpc, specifically, ppc64le. Of course, it's up to the Canonical kernel maintainers to decide which kernels could best benefit from a backport; I just wanted to bring the issue and fix to Canonical's attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828084 Title: Kernel modules generated incorrectly when system is localized to a non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828084] [NEW] Kernel modules generated incorrectly when system is localized to a non-English language
Public bug reported: When LANG is set to a non-English language with the relevant language pack installed, Kbuild's recordmcount.pl script fails to function correctly when building out-of-tree kernel modules on architectures that do not use the C version of recordmcount (e.g. ppc64le). This can result in invalid kernel modules being built. This was due to the non-C version of recordmcount relying on parsing the output of objdump(1), which can be localized. This is now fixed in the linux-kbuild tree with the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux- kbuild.git/commit/?h=kbuild=7b6954a982e7f60af38b835db52a06afc6e4b84c This commit is not in the torvalds/linux.git tree yet, but it would be good to backport the change to the Ubuntu kernel, particularly the linux-headers packages that are used for building out-of-tree kernel modules. Steps to Reproduce: 1. Set LANG to a language other than English (e.g. ja_JP.UTF-8) 2. Make sure that the correct language pack is installed and that localization is working; for example, run a command expected to print an error message, like `cp` with no additional arguments. 3. Install the NVIDIA GPU driver Actual results: The kernel panics when loading the nvidia-modeset kernel module. Expected results: The driver should install and load normally. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828084 Title: Kernel modules generated incorrectly when system is localized to a non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
I'm confused about the above message. This bug never affected the kernel in Bionic AFAIK. Or is this referring to the HWE kernel for Bionic from Cosmic for 18.04.2? In that case, why isn't this change already included in the HWE kernel as it was imported from Cosmic, rather than needing to be brought in through -proposed first? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
Yes, I do see the expected behavior now with signed modules, both when the signing key is enrolled in the MOK (module loads, no verification error) and when it is not enrolled in the MOK (module fails to load due to verification error.) However, the behavior is not quite what I expect when a module is unsigned. The module fails to load, which is expected, but there is no error message in dmesg indicating a missing key, which can make it tricky to determine why the module failed to load, since the failure message printed by modprobe/insmod is simply "Operation not permitted". (It seems the ENOKEY failure is not getting propagated to the user-facing tool.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
Just to confirm, this is with the 4.18.0-12-generic x86_64 kernel from cosmic-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
Cool, glad you were able to track down the problems. Sorry if my report that module signature verification was disabled and couldn't be re- enabled was misleading. That's what I thought was happening; I didn't think to imagine that the enforcement of the "valid signature required" policy wasn't taking place at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204919/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204913/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly
apport information ** Tags added: apport-collected cosmic ** Description changed: On a system with Ubuntu 18.10, with secure boot enabled, and a key enrolled in the MOK database, I am observing the following peculiar behaviors: * Signature verification appears to be disabled, and cannot be enabled again. It appeared to be enabled previously, as loading of unsigned modules was failing, and `mokutil --enable-validation` runs without incident; however, upon the next boot when attempting to confirm the change, MokManager prints an error message "Unable to delete Secure Boot state" after completing the password challenge. * As a result of signature verification being disabled, modules signed with untrusted keys taint the kernel instead of failing to load outright. * Regardless of signature verification being enabled or not, it seems that the key enrolled in the MOK is not being used for validating kernel module signatures. Modules signed with the key still fail the signature verification test and taint the kernel, even though the key is visible in the output of `mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows that it's enrolled. Also, a message acknowledging the key appears in dmesg: Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring * Also, somewhat strangely, in this state with module signature verification not being enforced, attempting to load a completely unsigned kernel module suceeds, and doesn't even log a kernel message about a missing/invalid signature, or taint the kernel. Apport report attached, which includes dmesg log showing the kernel acknowledging the key enrolled in the MOK database, and a signature verification failure and subsequent successful loading of a module signed with that key: [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring ... [6.628452] nvidia: module verification failed: signature and/or required key missing - tainting kernel ... [6.637252] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [6.637507] nvidia :01:00.0: enabling device (0006 -> 0007) [6.637620] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [6.737216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 410.66 Wed Oct 10 12:01:53 CDT 2018 (using threaded interrupts) - This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into - Ubuntu 18.04, signatures made with the same key are recognized as valid. - Hence, I suspect that something changed in the Ubuntu 18.10 kernel which - is causing signature verification to function in an unexpected way. + This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into Ubuntu 18.04, signatures made with the same key are recognized as valid. Hence, I suspect that something changed in the Ubuntu 18.10 kernel which is causing signature verification to function in an unexpected way. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: danix 1729 F pulseaudio + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-10-23 (0 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + NonfreeKernelModules: nvidia_uvm nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.modeset=0 + ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-10-generic N/A + linux-backports-modules-4.18.0-10-generic N/A + linux-firmware 1.175 + Tags: cosmic + Uname: Linux 4.18.0-10-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: False + dmi.bios.date: 03/20/2018 + dmi.bios.vendor: HP + dmi.bios.version: P70 Ver. 01.18 + dmi.board.name: 8270 + dmi.board.vendor: HP + dmi.board.version: KBC Version 46.67 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP70Ver.01.18:bd03/20/2018:svnHP:pn:pvr:rvnHP:rn8270:rvrKBCVersion46.67:cvnHP:ct10:cvr: + dmi.product.family: 103C_5336AN HP ZBook + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204908/+files/AlsaInfo.txt -- You received this bug notification because you are a member of
[Bug 1798863] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204914/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204910/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204917/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204920/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204916/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204911/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204915/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204918/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204912/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1798863/+attachment/5204909/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798863 Title: 18.10 kernel does not appear to validate kernel module signatures correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798863] [NEW] 18.10 kernel does not appear to validate kernel module signatures correctly
Public bug reported: On a system with Ubuntu 18.10, with secure boot enabled, and a key enrolled in the MOK database, I am observing the following peculiar behaviors: * Signature verification appears to be disabled, and cannot be enabled again. It appeared to be enabled previously, as loading of unsigned modules was failing, and `mokutil --enable-validation` runs without incident; however, upon the next boot when attempting to confirm the change, MokManager prints an error message "Unable to delete Secure Boot state" after completing the password challenge. * As a result of signature verification being disabled, modules signed with untrusted keys taint the kernel instead of failing to load outright. * Regardless of signature verification being enabled or not, it seems that the key enrolled in the MOK is not being used for validating kernel module signatures. Modules signed with the key still fail the signature verification test and taint the kernel, even though the key is visible in the output of `mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows that it's enrolled. Also, a message acknowledging the key appears in dmesg: Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring * Also, somewhat strangely, in this state with module signature verification not being enforced, attempting to load a completely unsigned kernel module suceeds, and doesn't even log a kernel message about a missing/invalid signature, or taint the kernel. Apport report attached, which includes dmesg log showing the kernel acknowledging the key enrolled in the MOK database, and a signature verification failure and subsequent successful loading of a module signed with that key: [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring ... [6.628452] nvidia: module verification failed: signature and/or required key missing - tainting kernel ... [6.637252] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [6.637507] nvidia :01:00.0: enabling device (0006 -> 0007) [6.637620] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [6.737216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 410.66 Wed Oct 10 12:01:53 CDT 2018 (using threaded interrupts) This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into Ubuntu 18.04, signatures made with the same key are recognized as valid. Hence, I suspect that something changed in the Ubuntu 18.10 kernel which is causing signature verification to function in an unexpected way. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "apport data from affected system" https://bugs.launchpad.net/bugs/1798863/+attachment/5203120/+files/apport.linux-image-4.18.0-10-generic.c_cz4acm.apport ** Description changed: On a system with Ubuntu 18.10, with secure boot enabled, and a key enrolled in the MOK database, I am observing the following peculiar behaviors: * Signature verification appears to be disabled, and cannot be enabled again. It appeared to be enabled previously, as loading of unsigned modules was failing, and `mokutil --enable-validation` runs without incident; however, upon the next boot when attempting to confirm the change, MokManager prints an error message "Unable to delete Secure Boot state" after completing the password challenge. * As a result of signature verification being disabled, modules signed with untrusted keys taint the kernel instead of failing to load outright. * Regardless of signature verification being enabled or not, it seems that the key enrolled in the MOK is not being used for validating kernel module signatures. Modules signed with the key still fail the signature verification test and taint the kernel, even though the key is visible in the output of `mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows that it's enrolled. Also, a message acknowledging the key appears in dmesg: Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring * Also, somewhat strangely, in this state with module signature verification not being enforced, attempting to load a completely unsigned kernel module suceeds, and doesn't even log a kernel message about a missing/invalid signature, or taint the kernel. Apport report attached, which includes dmesg log showing the kernel acknowledging the key enrolled in the MOK database, and a signature verification failure and subsequent successful loading of a module signed with that key: - [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key:
[Bug 1760704] [NEW] ld has a hard time finding development symlinks in the versioned directories
Public bug reported: The packages install the driver libraries, including symlinks intended for the dynamic linker, to versioned directories (e.g. /usr/lib/nvidia-390). The dynamic loader is configured to search these directories via /etc/ld.so.conf.d; however, this configuration doesn't affect the dynamic linker, which won't find the NVIDIA driver libraries unless the appropriate -L flag is set. For example, it would be nice to be able to link an application that uses libnvcuvid.so without having to set e.g. -L/usr/lib/nvidia-390 on the command line, since doing so would require finding out the right driver version number to set in the -L parameter. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760704 Title: ld has a hard time finding development symlinks in the versioned directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1760704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
It's unlikely to be due a change in the NVIDIA driver, since we (NVIDIA) have not yet identified a root cause for the touchpad freeze. As this problem is highly sporadic, and can take several hours in some cases to reproduce, if it reproduces at all, we should probably wait for more confirmations that it is no longer reproducible in Utopic before concluding that it has indeed been fixed there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and garbled after resume from suspend
@Alberto:
Here's a patch that adds calls into pm_vt_switch_{required,unregister}()
to the NVIDIA driver. It resolves the corruption issue on my test
system. This change will be included with the next release of the 331
series drivers.
** Patch added: NVIDIA driver patch for pm_vt_switch_required()
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1210077/+attachment/4015678/+files/pm_vt_switch_required.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210077
Title:
Screen freeze and garbled after resume from suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1210077/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and garbled after resume from suspend
Moving this bug from nvidia-prime to nvidia-graphics-drivers-331, since the fix goes in the NVIDIA driver, and not nvidia-prime. FWIW, the attached patch has been formatted for use with the NVIDIA .run installer's --apply-patch option, but it should be usable for DKMS, since DKMS uses patchlevel -p1. The patch includes a conftest so that the calls to the new pm_vt_switch_*() functions will only be compiled if the kernel actually provides them, so you don't need to worry about PATCH_MATCH, and can just apply the patch unconditionally. ** Package changed: nvidia-prime (Ubuntu) = nvidia-graphics-drivers-331 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and garbled after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and garbled after resume from suspend
It looks like this is a consequence of recent changes in the kernel that allow the system to optionally skip VT switches on suspend and resume: 24576d2 drm/i915: enable VT switchless resume v3 3cf2667 fb: add support for drivers not needing VT switch at suspend/resume time f43f627 PM: make VT switching to the suspend console optional v3 The kernel will not skip VT switches if no drivers register their VT switch requirements through pm_vt_switch_required(); however, if any drivers do so, and all of them indicate that VT switches are not required, they will be skipped. In the PRIME case, this is exactly what happens: the Intel driver registers itself as not needing VT switches, and the NVIDIA driver does not register its VT switch requirements one way or the other (the NVIDIA driver *does* need a VT switch on suspend/resume), so the kernel skips the VT switch, resulting in corruption when attempting to restore the NVIDIA X screen. The NVIDIA driver can be updated to pm_vt_switch_required() (I verified with a quick spot check that doing so restores the desired behavior: more testing will be needed before this change can be made officially); in the meantime, it is possible to work around this issue by adding 'no_console_suspend' to the kernel command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and garbled after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and garbled after resume from suspend
@Alberto: that's essentially the change which I tested successfully on a laptop I have which reproduces the issue, but some of my colleagues have suggested calling into pm_vt_switch_*() elsewhere in the driver. I would prefer if you could wait for an official patch and/or driver update, which we'll make available after the change has been properly reviewed and tested at NVIDIA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and garbled after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1210077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282796] [NEW] prime-xconfig can write an invalid BusID string
Public bug reported: The BusID string created by prime-xconfig could be incorrect in any of the following cases: a) Any numeric component of the bus ID is greater than 9: prime-xconfig will write a hexadecimal value, but X will parse it as decimal. b) The system has more than one PCI domain: `lspci -n` will show the PCI domain, which is normally hidden on systems with a single PCI domain. This breaks the formatting assumptions made by nv_get_id() about which fields are in which position. Besides the potential correctness issues, the generated BusID string is missing the following recommended (but optional) information: a) Bus type. According to xorg.conf(5) this should be PCI: b) PCI domain: omission of this field could lead to problems on systems with multiple PCI domains A patch against nvidia-prime 0.5.5 from Trusty is attached. The version on github seems to be behind that version by quite a bit. ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Patch added: prime-xconfig: format the BusID string correctly https://bugs.launchpad.net/bugs/1282796/+attachment/3988958/+files/0001-prime-xconfig-format-the-BusID-string-correctly.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282796 Title: prime-xconfig can write an invalid BusID string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282796] Re: prime-xconfig can write an invalid BusID string
Note that X can parse hexadecimal values in the BusID string if they're prepended with 0x, since xf86ParsePciBusString() uses atoi(3) to parse each field; however, the comment at the top of xf86ParsePciBusString() explicitly states that a decimal value is expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282796 Title: prime-xconfig can write an invalid BusID string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Hi Alberto, One of our GL driver engineers looked into this a bit, and it actually seems to be a linker regression that is exposed when linking an application against the Mesa libGL, and then running it against the NVIDIA one. He is gathering some more information before filing a bug, but in the mean time, please find attached a test case demonstrating the linker bug, which doesn't involve either the Mesa libGL or the NVIDIA one. See the README in the tarball for details. When bisecting binutils in an attempt to identify the regression, our engineer found that commit commit b64fb44af4f416fbbbda3de03fcfff61d80c841c (Also track weak references) actually introduced a link time error when attempting to link the test executable: ld: /tmp/cc3K1rHK.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' ld: note: 'pthread_create@@GLIBC_2.2.5' is defined in DSO //lib/x86_64-linux-gnu/libpthread.so.0 so try adding it to the linker command line That ld error no longer occurs after commit 879707c642925947e156b7ae2169b89f844532cd (Exclude weak refs when considering whether an --as-needed library is needed); however, the bug described here (assertion from ld.so) does. We believe that this Debian bug may be related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529 ** Bug watch added: Debian Bug tracker #728529 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248642 Title: dynamic library inconsistencies with OpenGL/C++ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1248642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Hi Alberto, One of our GL driver engineers looked into this a bit, and it actually seems to be a linker regression that is exposed when linking an application against the Mesa libGL, and then running it against the NVIDIA one. He is gathering some more information before filing a bug, but in the mean time, please find attached a test case demonstrating the linker bug, which doesn't involve either the Mesa libGL or the NVIDIA one. See the README in the tarball for details. When bisecting binutils in an attempt to identify the regression, our engineer found that commit commit b64fb44af4f416fbbbda3de03fcfff61d80c841c (Also track weak references) actually introduced a link time error when attempting to link the test executable: ld: /tmp/cc3K1rHK.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' ld: note: 'pthread_create@@GLIBC_2.2.5' is defined in DSO //lib/x86_64-linux-gnu/libpthread.so.0 so try adding it to the linker command line That ld error no longer occurs after commit 879707c642925947e156b7ae2169b89f844532cd (Exclude weak refs when considering whether an --as-needed library is needed); however, the bug described here (assertion from ld.so) does. We believe that this Debian bug may be related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728529 ** Attachment added: repro app https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1248642/+attachment/3948803/+files/pthread_bug_pure_c.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248642 Title: dynamic library inconsistencies with OpenGL/C++ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1248642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Apologies for the duplicated post: I neglected to include the attachment the first time around, and when I attempted to add it later, it resulted in the text of my previous update being posted again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248642 Title: dynamic library inconsistencies with OpenGL/C++ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1248642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241745] Re: [regression] Changing the screen brightness does not work anymore in 319.xx
The problem described in this bug is due to a confirmed regression in the NVIDIA driver. If you are seeing a similar symptom on Intel, that should probably be tracked in a separate bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241745 Title: [regression] Changing the screen brightness does not work anymore in 319.xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241745] Re: [regression] Changing the screen brightness does not work anymore in 319.xx
Not to my knowledge: that changelog entry refers to adding an additional interface via the NV-CONTROL API to the existing backlight functionality. The problem is that the existing backlight functionality is now broken on some laptops, so it doesn't make a difference whether it's exposed through a new API or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241745 Title: [regression] Changing the screen brightness does not work anymore in 319.xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
Sorry, I don't have any ideas. I don't think we've seen anything like this either; we'd probably need a machine that uses the same touchpad or touchpad driver. If the Nouveau driver also supports the RandR 1.4 provider source capability, it might be an interesting experiment to configure PRIME with Nouveau - modesetting to see if it's a generic interaction between the touchpad driver and RandR 1.4. Alternatively, it might be useful to attempt configuring an X screen on the Intel GPU using the modesetting driver and no offloading, to see if it's a general interaction between the touchpad driver and the modesetting X driver. That should be a lot easier to set up. Or... another possibility would be to try configuring the offloading with the Intel driver as the provider output instead of the modesetting driver. I can't remember the specific problems we ended up having with the Intel driver that led us to recommend the modesetting driver in the README instead, but if the Intel driver works as an output for you, and the problem is due to an interaction between the modesetting and touchpad drivers, then this may be a way to avoid the problem. These are all just wild guesses though; I don't have any good ideas as to why this might be happening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241745] Re: [regression] Changing the screen brightness does not work anymore in 319.xx
Sorry, at the moment we don't have an ETA for a fix. It's not likely to be fixed in the immediate future. I've added a note to the bug report on the NVIDIA bug tracker as a reminder to update this Launchpad thread when we have a fix in hand. The only workaround I'm currently aware of is to use an older driver, but older drivers may not be compatible with newer X servers and kernels. The 304.xx series is maintained as a legacy branch, so it would be compatible with newer kernel / X server versions, and unless your hardware is especially new, there's a good chance that a 304.xx driver will work for you. The recently released 304.116 driver, for example, is compatible with Xorg up to 1.14 and Linux up to 3.12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241745 Title: [regression] Changing the screen brightness does not work anymore in 319.xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and gabled after resume from suspend
It's not explicitly stated anywhere in this bug report, but due to the bug being assigned to nvidia-prime and the attached bug reports apparently coming from systems with PRIME configured, can it be assumed that this bug happens specifically on systems with RandR 1.4 display offloading configured? Does anybody have images of the corruption? I'm assuming the corruption is observed with the default Unity desktop. Does it also occur with non-composited desktops? (e.g. unity-2d, xfce4 default config) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and gabled after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1210077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241745] Re: [regression] Changing the screen brightness does not work anymore in 319.xx
It looks like we're tracking a similar bug report about broken brightness controls on HP EliteBook 8560w in the 319 and later drivers in the NVIDIA internal bug tracker. That bug tracker is not visible to the public, but in case you want to check with NVIDIA support on the status of the bug, the bug number is 1372953. The root cause of this issue has not yet been investigated, so there's nothing to report at the moment, other than that we are indeed able to reproduce this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241745 Title: [regression] Changing the screen brightness does not work anymore in 319.xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1241745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929384] Re: nvidia drivers broken by the recent libc update on i386 arch
The next 295 driver version will contain a fix for this issue. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Triaged = Fix Committed ** Changed in: nvidia-graphics-drivers (Ubuntu) Assignee: Alberto Milone (albertomilone) = Daniel Dadap (ddadap) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929384 Title: nvidia drivers broken by the recent libc update on i386 arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111039] Re: xtightvncviewer scrolling doesn't work
** Changed in: tightvnc (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/111039 Title: xtightvncviewer scrolling doesn't work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111039] Re: xtightvncviewer scrolling doesn't work
Actually, this isn't a bug. The old-skool Xaw scrollbars need to be right-clicked to scroll left or up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/111039 Title: xtightvncviewer scrolling doesn't work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[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 Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 refresh rates
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519538] [NEW] System freeze when logging into GNOME on fresh Lucid install
Public bug reported: This is happening on Toshiba Tecra M5 and Tecra M10 laptops. Started with a fresh install of Karmic, which works normally. Did an upgrade to Lucid. Upon booting into Lucid, the gdm login screen displays. On the M5, this screen has scrambled video, which clears up if I switch to a vt (control-alt-f#) and back. On the M10, it displays normally. When I try to log into the system, the cursor disappears and the system becomes completely unresponsive. Both laptops have NVIDIA discrete graphics. This happens with both the nv and the vesa drivers. It also happens regardless of what session is selected. (GNOME, Failsafe GNOME, xterm.) ** Affects: ubuntu Importance: Undecided Status: New -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
