Bug#851218: systemd[1]: Failed deactivating swap
Package: base Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? It is simply that I occasionally see these errors on shutting down: systemd[1]: Failed deactivating swap /dev/disk/by-partuuid/d261f2f3-01. systemd[1]: Failed deactivating swap /dev/sdc1. systemd[1]: Failed deactivating swap /dev/disk/by-path/pci-:00:1f.2-ata-2-part1. systemd[1]: Failed deactivating swap /dev/disk/by-uuid/b318e60d-0c9e-42ed-8b70-6a7bb1d3edd3. systemd[1]: Failed deactivating swap /dev/disk/by-id/ata-WDC_WD800JD-75MSA3_WD-WMAM9PD77921-part1. Nothing seems to go wrong, but it is mildly annoying to see red ERROR messages on shutdown. Also, it does not happen every time. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#848927: mount: bad option.
Package: gparted Version: 0.25.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? gparted fails completely with the message: "mount: bad option. Note that mmoving a mount " I noticed the identical bug searching with Google, but didn't see that bug in the list that reportbug offered me. One of the bug reports said that it was due to 'udisks2' and it was supposed to be fixed, but it is not. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gparted depends on: ii libatkmm-1.6-1v5 2.24.2-2 ii libc6 2.24-8 ii libgcc1 1:6.2.1-5 ii libglib2.0-0 2.50.2-2 ii libglibmm-2.4-1v5 2.50.0-1 ii libgtk2.0-0 2.24.31-1 ii libgtkmm-2.4-1v5 1:2.24.5-1 ii libpangomm-1.4-1v52.40.1-3 ii libparted-fs-resize0 3.2-16+b1 ii libparted23.2-16+b1 ii libsigc++-2.0-0v5 2.10.0-1 ii libstdc++66.2.1-5 ii libuuid1 2.29-1 gparted recommends no packages. Versions of packages gparted suggests: pn dmraid ii dmsetup2:1.02.136-1 pn dosfstools pn gpart pn jfsutils pn kpartx pn mtools pn ntfs-3g pn reiser4progs pn reiserfsprogs pn xfsprogs ii yelp 3.22.0-1 -- no debconf information
Bug#803667: upgrade-reports: No Xorg: "no screens found(EE)"
I fixed it by installing 'nvidea-xconfig' but although my video worked, my mouse was dead. Googling I found I had to add: Section "ServerFlags" Option "AllowEmptyInput" "False" Option "AutoAddDevices" "False" EndSection to 'xorg.conf', and it all seems fine. So it seems there's some issue with nouveau, and it would be polite if 'nvidea-xconfig' refrained from killing the mouse. Other than that, I don't care which video driver is used, so long as the damned thing works.
Bug#803667: upgrade-reports: No Xorg: "no screens found(EE)"
On 11/08/2015 12:51 PM, Julien Cristau wrote: On Sun, Nov 1, 2015 at 08:01:47 -0800, Ray Andrews wrote: (running a backup) with the failed upgrade, the first sign of trouble is the message: "failed to set drm version". Please provide the relevant logs. Cheers, Julien Attached, Julien, thanks. [ 560.360] X.Org X Server 1.17.2 Release Date: 2015-06-16 [ 560.364] X Protocol Version 11, Revision 0 [ 560.365] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 560.366] Current Operating System: Linux HP-w5--5-Debian1 4.1.0-2-686-pae #1 SMP Debian 4.1.6-1 (2015-08-23) i686 [ 560.366] Kernel command line: auto BOOT_IMAGE=w5:D1:4.1.0-2 root=LABEL=w5--5-Debian1 [ 560.369] Build Date: 08 October 2015 10:05:01AM [ 560.370] xorg-server 2:1.17.2-3 (http://www.debian.org/support) [ 560.372] Current version of pixman: 0.33.2 [ 560.374]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 560.374] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 560.380] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 25 15:47:57 2015 [ 560.381] (==) Using config file: "/etc/X11/xorg.conf" [ 560.382] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 560.383] (==) ServerLayout "Layout" [ 560.383] (**) |-->Screen "Screen0" (0) [ 560.383] (**) | |-->Monitor "Monitor0" [ 560.383] (**) | |-->Device "Device0" [ 560.383] (**) |-->Screen "Screen1" (1) [ 560.383] (**) | |-->Monitor "Monitor1" [ 560.383] (**) | |-->Device "Device1" [ 560.383] (**) |-->Screen "Screen2" (2) [ 560.383] (**) | |-->Monitor "Monitor2" [ 560.384] (**) | |-->Device "Device2" [ 560.384] (==) Automatically adding devices [ 560.384] (==) Automatically enabling devices [ 560.384] (==) Automatically adding GPU devices [ 560.384] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 560.384]Entry deleted from font path. [ 560.384] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 560.384] (==) ModulePath set to "/usr/lib/xorg/modules" [ 560.384] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 560.384] (II) Loader magic: 0x8035c700 [ 560.384] (II) Module ABI versions: [ 560.384]X.Org ANSI C Emulation: 0.4 [ 560.384]X.Org Video Driver: 19.0 [ 560.384]X.Org XInput driver : 21.0 [ 560.384]X.Org Server Extension : 9.0 [ 560.389] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31 [ 560.390] (II) xfree86: Adding drm device (/dev/dri/card0) [ 560.391] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0 [ 560.393] (--) PCI:*(0:1:0:0) 10de:104a:19da:6222 rev 161, Mem @ 0xeb00/16777216, 0xe000/134217728, 0xe800/33554432, I/O @ 0x1000/128, BIOS @ 0x/524288 [ 560.393] (II) LoadModule: "glx" [ 560.393] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 560.395] (II) Module glx: vendor="X.Org Foundation" [ 560.395]compiled for 1.17.2, module version = 1.0.0 [ 560.395]ABI class: X.Org Server Extension, version 9.0 [ 560.395] (==) AIGLX enabled [ 560.395] (II) LoadModule: "nouveau" [ 560.395] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [ 560.396] (II) Module nouveau: vendor="X.Org Foundation" [ 560.396]compiled for 1.17.1, module version = 1.0.11 [ 560.396]Module class: X.Org Video Driver [ 560.396]ABI class: X.Org Video Driver, version 19.0 [ 560.396] (II) LoadModule: "vesa" [ 560.396] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 560.396] (II) Module vesa: vendor="X.Org Foundation" [ 560.396]compiled for 1.17.1, module version = 2.3.3 [ 560.396]Module class: X.Org Video Driver [ 560.396]ABI class: X.Org Video Driver, version 19.0 [ 560.396] (II) NOUVEAU driver Date: Thu Aug 28 03:57:48 2014 +0200 [ 560.396] (II) NOUVEAU driver for NVIDIA chipset families : [ 560.396]RIVA TNT(NV04) [ 560.396]RIVA TNT2 (NV05) [ 560.396]GeForce 256 (NV10) [ 560.396]GeForce 2 (NV11, NV15) [ 560.396]GeForce 4MX (NV17, NV18) [ 560.396]GeForce 3 (NV20) [ 560.396]GeForce 4Ti (NV25, NV28) [ 560.397]GeForce
Bug#803667: upgrade-reports: No Xorg: "no screens found(EE)"
On 11/06/2015 11:56 PM, Niels Thykier wrote: Thanks for giving this some time Neils, it would be a shame if I had to stop using Debian due to this bug. Hi Ray, Are you using the setuid version of X11 or the new non-setuid version? And in the latter case, do you have libpam-systemd installed? Yes, and reinstalled with no change. Possibly related information: xorg-server (2:1.17.3-1) unstable; urgency=medium The Xorg server is no longer setuid root by default. This change reduces the risk of privilege escalation due to X server bugs, but has some side effects: * it relies on logind and libpam-systemd * it relies on a kernel video driver (so the userspace component doesn't touch the hardware directly) * it needs X to run on the virtual console (VT) it was started from * it changes the location for storing the Xorg log from /var/log/ to ~/.local/share/xorg/ On systems where those are not available, the new xserver-xorg-legacy package is needed to allow X to run with elevated privileges. See the Xwrapper.config(5) manual page for configuration details. -- Julien Cristau Tue, 27 Oct 2015 22:54:11 Everything there reinstalled too, but no joy. I wonder if I can move away from 'legacy' entirely?
Bug#803667: upgrade-reports: No Xorg: "no screens found(EE)"
Package: upgrade-reports Severity: important Dear Maintainer, -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) I track 'testing' and upgrade every few days, almost always without any issues. However a couple of weeks ago the upgrade caused my Xorg to fail with the above message. Looking at Xorg.0.log, comparing a good version (running a backup) with the failed upgrade, the first sign of trouble is the message: "failed to set drm version". lspci reports my card: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) I use the nouveau driver. I have an Xorg.conf, but it works fine prior to the upgrade. Removing Xorg.conf made no difference (I need it to get my dual monitors working). I tried reinstalling every package that has 'drm' in its name with no change. If it is relevant, recent efforts at upgrades on the broken install (I have expected that this bug would fix itself after a few subsequent upgrades) report something to the effect that the signature of the upgrade has not been updated--or something like that.
