Your message dated Fri, 8 Sep 2017 10:28:35 +0200 with message-id <[email protected]> and subject line Re: Bug#728843: nvidia-driver: Changing sound on keyboard or launching remmina crashes X has caused the Debian Bug report #728843, regarding nvidia-driver: Changing sound on keyboard or launching remmina crashes X to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 728843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728843 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nvidia-driver Version: 319.60-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Updates to packages in Jessie * What exactly did you do (or not do) that was effective (or ineffective)? Initially, result was X would not start, providing blinking cursor. Purged all packages returned from dpkg --list | grep -i "nividia" Changed xorg.conf to vesa to confirm X worked Deployed various nvidia packages from jessie, unstable and sid repositories Some success achieved with 3.19.60-2 nvidia-vdpau-driver and 304xx varieties, however symptoms persist where changing volume from keyboard, launching remmina, and other context switches cause x windows to crash and a log to denote: (II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision [ 891.660] (II) NVIDIA(GPU-0): stereo. * What was the outcome of this action? Once again, purged all nvidia packages, found and deployed nvidia's 331.13 package, noting that building the dkms seems to fail due to some inability for the source to properly harvest the cc variable, experienced exact same symptoms. * What outcome did you expect instead? An easy way to revert the packages in apt would probably be helpful for this kind of situation. Probably more conversation with linux kernel team and nvidia to shield the user community from the politics. Maybe more reverse engineering and middle fingers should be raised up. Thanks for all you do -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (901, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nvidia-driver depends on: ii libc6 2.17-93 pn libgl1-nvidia-glx <none> pn libnvidia-ml1 <none> pn nvidia-alternative <none> pn nvidia-installer-cleanup <none> pn nvidia-kernel-dkms | nvidia-kernel-319.60 <none> pn nvidia-support <none> pn nvidia-vdpau-driver <none> pn xserver-xorg-video-nvidia <none> Versions of packages nvidia-driver recommends: pn libgl1-nvidia-glx-i386 <none> pn nvidia-settings <none> Versions of packages nvidia-driver suggests: pn nvidia-kernel-dkms | nvidia-kernel-source <none>
--- End Message ---
--- Begin Message ---On Sat, 09 Nov 2013 20:56:46 +0100 Andreas Beckmann <[email protected]> wrote: > Running reportbug on a different system does not collect information > from your setup ... that could have helped debugging. > (Hint: run 'reportbug -N 728843' on the failing machine) > > Anyway, 319.72 is on its way to unstable and 331.20 is in experimental. > Besides trying these versions, please report this directly to NVIDIA - > that is nothing we can do to fixed the closed source driver. > See the README.Debian in the nvidia-driver package for more pointers. Closing due to lack of further information. Andreas
--- End Message ---
