Bug#777268: mplayer2 compiled w/o dvdnav support
This bug can be closed. The original "mplayer" is back in testing/sid, making "mplayer2" obsolete. The "mplayer" package comes with proper dvdnav support, as expected. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776874: systemd: system auto-resumes when pcspkr module is loaded
well, because systemd is responsible for suspending the system, afaik, so if that's not working properly, I figured it would be best addressed here. If that's wrong, then what package should I file this bug report against instead? linux-image-amd64, which provides the pcspkr module? Thanks much! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777268: mplayer2 compiled w/o dvdnav support
Subject: mplayer2 compiled w/o dvdnav support Package: mplayer2 Version: 2.0-728-g2c378c7-4+b1 Severity: normal Dear Maintainer, starting mplayer with dvdnav:// results in a "No stream found to handle url dvdnav://" error, although libdvdnav4 is installed. According to the build logs, mplayer2 was compiled w/o dvdnav support: Checking for DVD support (libdvdnav) ... no Can this be corrected? It would be nice to not have to switch over to the DMO package... Thanks! -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (700, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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) Versions of packages mplayer2 depends on: ii liba52-0.7.4 0.7.4-17 ii libasound21.0.28-1 ii libass5 0.10.2-3 ii libavcodec56 6:11.2-1 ii libavformat56 6:11.2-1 ii libavresample26:11.2-1 ii libavutil54 6:11.2-1 ii libbluray11:0.6.2-1 ii libbs2b0 3.1.0+dfsg-2.1 ii libc6 2.19-13 ii libcaca0 0.99.beta19-2 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libdca0 0.0.5-7 ii libdirectfb-1.2-9 1.2.10.0-5.1 ii libdv41.0.0-6 ii libdvdread4 5.0.0-1 ii libenca0 1.16-1 ii libfaad2 2.7-8 ii libgif4 4.1.6-11 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-11 ii liblcms2-22.6-3+b3 ii liblircclient00.9.0~pre1-1.2 ii libmad0 0.15.1b-8 ii libmpg123-0 1.20.1-2 ii libogg0 1.3.2-1 ii libpng12-01.2.50-2+b2 ii libpostproc52 6:0.git20120821-4 ii libpulse0 5.0-13 ii libquvi7 0.4.1-3 ii libsdl1.2debian 1.2.15-10+b1 ii libsmbclient 2:4.1.13+dfsg-2 ii libspeex1 1.2~rc1.2-1 ii libswscale3 6:11.2-1 ii libtheora01.1.1+dfsg.1-6 ii libtinfo5 5.9+20140913-1+b1 ii libvdpau1 0.8-3 ii libvorbis0a 1.3.4-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxinerama1 2:1.1.3-1+b1 ii libxss1 1:1.2.2-1 ii libxv12:1.0.10-1+b1 ii libxvidcore4 2:1.3.3-1 ii libxxf86vm1 1:1.1.3-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 mplayer2 recommends no packages. mplayer2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#867509: deborphan lists manually installed package as orphaned
Package: deborphan Version: 1.7.28.8-0.3+b1 Severity: normal Dear Maintainer, I have manually installed 'libdbus-glib-1-dev' on my buster system because I need this library to compile other software from git. The package was manully installed, not as a dependency, and is correctly not listed as an auto-install: brainslug@bender:~$ aptitude search libdbus-glib-1-dev i libdbus-glib-1-dev Therefore I do not think that deborphan should list this package as orphaned, but it does: brainslug@bender:~$ deborphan libdbus-glib-1-dev:amd64 My first guess was that this might be because no other package directly depends on this librarary but this logic does not hold true as I have tons of other packages installed that that are not a requirement for any other package either but since they were manually installed and not an auto-install get properly ignored by deborphan. One example is the 'units' package. It is not identified as orphaned, despite not being a requirement for any other package: root@bender:/# aptitude remove units The following packages will be REMOVED: units 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 511 kB will be freed. (Reading database ... 221203 files and directories currently installed.) Removing units (2.14-1) ... Processing triggers for install-info (6.4.0.dfsg.1-1) ... Processing triggers for menu (2.1.47+b1) ... Processing triggers for man-db (2.7.6.1-2) ... Do '-dev' libraries get treated differently in deborphan's logic? And if this is not a bug but some sort of weird "feature", is there a way to tell deborphan to ignore this particular package? Thanks! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages deborphan depends on: ii libc6 2.24-12 Versions of packages deborphan recommends: ii apt 1.4.6 ii dialog1.3-20160828-2 ii gettext-base 0.19.8.1-2 deborphan suggests no packages. -- no debconf information
Bug#634073: Svn launches kwallet
It's two years later now, but subversion 1.9.2 on Debian/stretch still launches stupid kwallet. +1 on setting "password-stores=" to an empty string by default. Cheers!
Bug#815862: rsyslog re-spawns immediately when stopped
Package: rsyslog Version: 8.16.0-1 Severity: important Dear Maintainer, it appears that I am not able to shut down rsyslog via systemctl or init script. It auto-respawns immediately. This is a huge problem b/c everytime I plug in a USB 3.0 device my system crashes and syslog / kern.log fill up my disks very quickly even after I remove the device. Here is what I do: root@localhost:~# ps faux | grep rsyslogd ... root 3144 0.0 0.0 258296 3020 ?Ssl 00:41 0:00 /usr/sbin/rsyslogd -n root@localhost:~# /etc/init.d/rsyslog stop [] Stopping rsyslog (via systemctl): rsyslog.serviceWarning: Stopping rsyslog.service, but it can still be activated by: syslog.socket . ok root@localhost:~# ps faux | grep rsyslogd ... root 25326 0.0 0.0 258296 3020 ?Ssl 00:41 0:00 /usr/sbin/rsyslogd -n The PID of rsyslogd has changed, so the process appears to have gotten killed originally but my logfiles keep getting flooded thanks to the auto-spawned process. The only way for me to "stop" logfile flooding is: mv /usr/sbin/rsyslog /tmp /etc/init.d/rsyslog stop mv /tmp/rsyslog /usr/sbin This is not good. My /etc/rsyslog.conf is the original file provided by the .deb package and there is nothing in /etc/rsyslog.d/ When trying to stop rsyslogd via init script, I see this in /var/log/syslog: Feb 25 00:51:38 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="3595" x-info="http://www.rsyslog.com";] exiting on signal 15. Feb 25 00:51:38 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="3681" x-info="http://www.rsyslog.com";] start Feb 25 00:51:38 localhost systemd[1]: Stopping System Logging Service... Feb 25 00:51:38 localhost systemd[1]: Stopped System Logging Service. Feb 25 00:51:38 localhost systemd[1]: Starting System Logging Service... Feb 25 00:51:38 localhost systemd[1]: Started System Logging Service. Not sure why I get duplicate entries for stops and starts. Any help would be much appreciated. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (800, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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) Versions of packages rsyslog depends on: ii init-system-helpers 1.28 ii libc62.21-9 ii libestr0 0.1.10-1 ii libjson-c2 0.11-4 ii liblogging-stdlog0 1.0.5-2 ii liblognorm2 1.1.2-1.1 ii libsystemd0 228-6 ii libuuid1 2.27.1-3 ii lsb-base 9.20160110 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages rsyslog recommends: ii logrotate 3.8.7-2 Versions of packages rsyslog suggests: pn rsyslog-doc pn rsyslog-gnutls pn rsyslog-gssapi pn rsyslog-mongodb pn rsyslog-mysql | rsyslog-pgsql pn rsyslog-relp -- no debconf information
Bug#886405: bumblebee-nvidia: optirun/primus seems to work, but no display output
Package: bumblebee-nvidia Version: 3.2.1-17 Severity: normal Dear Maintainer, I am trying to get optirun/primusrun to work on a Dell Precision M4800 laptop which has Optimus capabilities and the following hardware: brainslug@m4800:~$ lspci ... 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) ... 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev ff) I've installed bumblebee-nvidia and primus packages 3.2.1-17, running kernel 4.14.0-2-amd64, no multi-arch, Debian testing. No external displays connected, only internal laptop display used. optirun/primusrun seems to work for some programs, like darktable & bash, but for most programs I don't get any display output, examples include firefox, glxgears, glxinfo. According to syslog the Nvidia card gets activated and I can see that /proc/acpi/bbswitch changes from "OFF" to "ON" during a primusrun/optirun attempt. I just don't see the program output. Some debug info below - if this bug report should be filed against another package, please let me know. Any help would be much appreciated. Initial state: brainslug@m4800:~$ cat /proc/acpi/bbswitch :01:00.0 OFF then brainslug@m4800:~$ optirun -v glxinfo [ 552.198375] [INFO]Response: Yes. X is active. [ 552.198392] [INFO]Running application using primus. ^C[ 605.131876] [WARN]Received Interrupt signal. while running, this in other shell: brainslug@m4800:~$ cat /proc/acpi/bbswitch :01:00.0 ON Then after the command is terminated via Ctrl-C: brainslug@m4800:~$ cat /proc/acpi/bbswitch :01:00.0 OFF from syslog: Jan 6 02:09:17 m4800 kernel: [ 550.267976] bbswitch: enabling discrete graphics Jan 6 02:09:18 m4800 kernel: [ 551.049385] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none Jan 6 02:09:18 m4800 kernel: [ 551.049448] nvidia-nvlink: Nvlink Core is being initialized, major device number 243 Jan 6 02:09:18 m4800 kernel: [ 551.049456] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 375.82 Wed Jul 19 21:16:49 PDT 2017 (using threaded \ interrupts) Jan 6 02:09:19 m4800 acpid: client connected from 3275[0:999] Jan 6 02:09:19 m4800 acpid: 1 client rule loaded Jan 6 02:09:19 m4800 kernel: [ 551.788227] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.82 Wed Jul 19 20:3\ 5:11 PDT 2017 Jan 6 02:09:19 m4800 bumblebeed[992]: [ 552.198276] [WARN][XORG] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/Type1". Jan 6 02:09:19 m4800 bumblebeed[992]: [ 552.198293] [WARN][XORG] (WW) NVIDIA(0): Unable to get display device for DPI computation. Jan 6 02:09:19 m4800 bumblebeed[992]: [ 552.198301] [ERROR][XORG] (EE) PreInit returned 2 for "" Jan 6 02:10:12 m4800 kernel: [ 605.250609] nvidia-modeset: Unloading Jan 6 02:10:12 m4800 acpid: client 3275[0:999] has disconnected Jan 6 02:10:12 m4800 kernel: [ 605.283041] nvidia-nvlink: Unregistered the Nvlink Core, major device number 243 Jan 6 02:10:12 m4800 kernel: [ 605.316555] bbswitch: disabling discrete graphics Jan 6 02:10:12 m4800 kernel: [ 605.334899] pci :01:00.0: Refused to change power state, currently in D0 I've also tried to specify the display explicitly, like so: brainslug@m4800:~$ optirun -v -d :0 -b primus glxinfo but the results are the same -- no glxinfo output. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bumblebee-nvidia depends on: ii bumblebee 3.2.1-17 ii glx-alternative-nvidia 0.8.0 ii nvidia-kernel-dkms 375.82-7 bumblebee-nvidia recommends no packages. bumblebee-nvidia suggests no packages. -- no debconf information
Bug#837194: systemd --user: service action not triggered
Package: systemd Version: 231-4 Severity: normal Dear Maintainer, I have a business laptop for which I do not have root access. The system is configured to suspend when I press the power key. Now I am trying to configure systemd on a user level to lock my screen before the system suspends. I have a working service file in ~/.config/systemd/user/i3lock.service, like so: [Unit] Description=i3lock Before=sleep.target [Service] Type=forking Environment=DISPLAY=:0 ExecStart=/usr/bin/i3lock -c 00 [Install] WantedBy=sleep.target I can enable the service via the --user option: brainslug@flexo:~$ systemctl --user enable i3lock Created symlink /home/brainslug/.config/systemd/user/sleep.target.wants/i3lock.service → /home/brainslug/.config/systemd/user/i3lock.service. I can start the service via brainslug@flexo:~$ systemctl --user start i3lock which immediately locks my screen, so I would think the service file itself is correct and working. However, when suspending the laptop this does not seem to trigger my service file and my screen remains unlocked on resume. When I check on the service status, this is what I get: brainslug@flexo:~$ systemctl --user status i3lock ● i3lock.service - i3lock Loaded: loaded (/home/brainslug/.config/systemd/user/i3lock.service; enabled; vendor preset: enabled) Active: inactive (dead) FWIW, I am using lightdm and window maker. Thanks! -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (800, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (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) Versions of packages systemd depends on: ii adduser 3.115 ii libacl1 2.2.52-3 ii libapparmor12.10.95-4 ii libaudit1 1:2.6.6-1 ii libblkid1 2.28.1-1 ii libc6 2.23-5 ii libcap2 1:2.25-1 ii libcap2-bin 1:2.25-1 ii libcryptsetup4 2:1.7.0-2 ii libgcrypt20 1.7.3-1 ii libgpg-error0 1.24-1 ii libidn111.33-1 ii libkmod222-1.1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.28.1-1 ii libpam0g1.1.8-3.3 ii libseccomp2 2.3.1-2 ii libselinux1 2.5-3 ii libsystemd0 231-4 ii mount 2.28.1-1 ii util-linux 2.28.1-1 Versions of packages systemd recommends: ii dbus1.10.10-1 ii libpam-systemd 231-4 Versions of packages systemd suggests: ii policykit-10.105-16 pn systemd-container pn systemd-ui Versions of packages systemd is related to: ii udev 231-4 -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandlePowerKey=suspend HandleSuspendKey=hibernate HandleHibernateKey=hibernate HandleLidSwitch=ignore HandleLidSwitchDocked=ignore -- no debconf information
Bug#837357: meld requires gnome-user-guide
Package: meld Version: 3.16.2-1 Severity: minor Dear Maintainer, meld automatically installs gnome-user-guide as a dependency. This is completely unnecessary and gnome-user-guide can be manually removed afterwards without breaking anything. Instead of listing gnome-user-guide as a dependency, meld should only recommend gnome-user-guide. Thank you. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (800, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 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) Versions of packages meld depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1 ii gir1.2-gtksource-3.0 3.21.5-2 ii libcanberra-gtk3-module 0.30-3 ii libgtk-3-0 3.21.5-3 ii libgtksourceview-3.0-1 3.21.5-2 ii patch2.7.5-1 ii python-gi3.21.91-2 ii python-gi-cairo 3.21.91-2 pn python:any Versions of packages meld recommends: ii yelp 3.20.1-1 meld suggests no packages. -- no debconf information
Bug#837357: meld requires gnome-user-guide
o.k., so this is weird I agree that meld does not list gnome-user-guide as a dependency. gome-user-guide gets auto-installed because meld seems to required yelp - even though it is not listed in its dependencies either: root@uw1:~# aptitude install meld The following NEW packages will be installed: gnome-user-guide{a} meld yelp{a} yelp-xsl{a} 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/13.4 MB of archives. After unpacking 55.1 MB will be used. Do you want to continue? [Y/n/?] After I install meld, I can safely remove yelp, yepl-xsl and gnome-user-guide again and meld keeps working as expected, so why does yelp get installed in the first place? This problem is reproducible on all three of my Debian machines, including a fresh install. Installation of meld pulls in yelp. FWIW, I don't seem to have any pending or broken packages installed that could be blamed for the yelp installation: root@uw1:~# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. and root@flexo:~# aptitude search ~b root@flexo:~# Any idea why meld pulls in yelp? Thanks!
Bug#837357: meld requires gnome-user-guide
never mind, looks like meld recommends yelp. Thanks for the help. Please close this one.
Bug#789125: initramfs-tools: update-initramfs fails w/ random luks key for swap
Package: initramfs-tools Version: 0.120 Severity: normal Dear Maintainer, since the migration to systemd, key scripts in /etc/crypttab are no longer supported (bug #618862). To work around this problem I tried replacing the keyscript for my swap partition with a random key. But this fails when trying to update the initramfs: /etc/crypttab: sda4_crypt /dev/sda4 /dev/urandom cipher=aes-xts-plain64,size=256,swap sda5_crypt UUID=2fa9feb8-b096-41f7-bf17-41399ccc8004 none luks,discard root@laptop:/etc# update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 cryptsetup: WARNING: target sda4_crypt has a random key, skipped The swap partition does not get created on boot. If this is not a bug but expected behavior, then what is the proper way now to create a randomly encrypted swap partition? Thanks! - B -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 4.8M Jun 17 22:42 /boot/initrd.img-3.16.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=a9fb75bb-960d-47dd-8e94-d5863b059810 ro quiet intel_pstate=disable acpi_backlight=vendor -- resume RESUME=/dev/mapper/sda4_crypt -- /proc/filesystems ext3 ext2 ext4 fuseblk vfat -- lsmod Module Size Used by cpuid 12663 0 ccm17577 3 usb_storage56215 0 hid_generic12393 0 snd_usb_audio 135354 3 snd_usbmidi_lib23388 1 snd_usb_audio snd_rawmidi26806 1 snd_usbmidi_lib snd_seq_device 13132 1 snd_rawmidi hid_logitech_dj17192 0 usbhid 44460 0 pci_stub 12429 1 vboxpci23077 0 vboxnetadp 25443 0 vboxnetflt 23324 0 vboxdrv 340226 3 vboxnetadp,vboxnetflt,vboxpci ip6table_filter12540 1 ip6_tables 26025 1 ip6table_filter xt_recent 17246 1 iptable_nat12646 0 nf_nat_ipv412912 1 iptable_nat xt_comment 12427 20 ipt_REJECT 12465 4 xt_addrtype12557 5 xt_mark12453 1 iptable_mangle 12536 1 xt_tcpudp 12527 51 xt_CT 12842 22 iptable_raw12524 1 xt_multiport 12518 4 nf_conntrack_ipv4 18448 45 nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 xt_conntrack 12681 22 ipt_ULOG 12819 0 xt_NFLOG 12462 0 nfnetlink_log 17201 1 xt_NFLOG xt_LOG 17171 12 nf_nat_tftp12422 0 nf_nat_snmp_basic 16904 0 nf_conntrack_snmp 12443 3 nf_nat_snmp_basic nf_nat_sip 17053 0 nf_nat_pptp12562 0 nf_nat_proto_gre 12517 1 nf_nat_pptp nf_nat_irc 12454 0 nf_nat_h32316935 0 nf_nat_ftp 12460 0 nf_nat_amanda 12424 0 ts_kmp 12535 5 nf_conntrack_amanda12437 3 nf_nat_amanda nf_nat 18241 10 nf_nat_ftp,nf_nat_irc,nf_nat_sip,nf_nat_amanda,nf_nat_proto_gre,nf_nat_h323,nf_nat_ipv4,nf_nat_pptp,nf_nat_tftp,iptable_nat nf_conntrack_sane 12428 2 nf_conntrack_tftp 12433 3 nf_nat_tftp nf_conntrack_sip 26053 3 nf_nat_sip nf_conntrack_proto_udplite12931 0 nf_conntrack_proto_sctp17268 0 nf_conntrack_pptp 12619 3 nf_nat_pptp nf_conntrack_proto_gre13024 1 nf_conntrack_pptp nf_conntrack_netlink35433 0 nfnetlink 12989 2 nfnetlink_log,nf_conntrack_netlink nf_conntrack_netbios_ns12445 2 nf_conntrack_broadcast12365 2 nf_conntrack_netbios_ns,nf_conntrack_snmp nf_conntrack_irc 12427 3 nf_nat_irc nf_conntrack_h323 58618 5 nf_nat_h323 nf_conntrack_ftp 16783 3 nf_nat_ftp nf_conntrack 87424 29 nf_nat_ftp,nf_nat_irc,nf_nat_sip,nf_nat_amanda,xt_CT,nf_nat_snmp_basic,nf_conntrack_netbios_ns,nf_conntrack_proto_gre,nf_conntrack_proto_\ udplite,nf_nat,nf_nat_h323,nf_nat_ipv4,nf_nat_pptp,nf_nat_tftp,xt_conntrack,nf_conntrack_amanda,nf_conntrack_proto_sctp,nf_conntrack_netlink,nf_conntrack_broadcast,nf_con\ ntrack_ftp,nf_conntrack_irc,nf_conntrack_sip,iptable_nat,nf_conntrack_h323,nf_conntrack_ipv4,nf_conntrack_pptp,nf_conntrack_sane,nf_conntrack_snmp,nf_conntrack_tftp deflate12551 0 ctr12927 3 nfsd 263032 2 twofish_generic16569 0 twofish_avx_x86_64 46079 0 twofish_x86_64_3way25483 1 twofish_avx_x86_64 auth_rpcgss51211 1 nfsd twofish_x86_64 12541 2 twofish_avx_x86_64,twofish_x86_64_3way oid_registry 12419 1 auth_rpcgss twofish_common 20585 4 twofish_generic,twofish_avx_x86_64,twofish_x86_64_3way,twofish_x86_64 nfs_acl12511 1 nfsd camellia_generic 29025 0 nfs 188136 0 camellia_aesni_avx225843 0 camellia_aesni_avx_x86_6425925 1 camellia_aesni_avx2 camellia_x86_6450481 2 camel
Bug#789125: initramfs-tools: update-initramfs fails w/ random luks key for swap
Some more info: The problem seems to be the "_" in the swap's crypto device name. If I replace "sda4_crypt" with something that does not contain an underscore, this works, for example: sda4crypt /dev/sda4 /dev/urandom cipher=aes-xts-plain64,size=256,swap sda5_crypt UUID=2fa9feb8-b096-41f7-bf17-41399ccc8004 none luks,discard root@laptop:/etc# update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 root@laptop:/etc# However, underscore is not a problem on any of my non-swap devices, like the root partition sda5_crypt. Only for the swap partition. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#618862: systemd: ignores keyscript in crypttab
Hi, I'm also affected by this problem. Very simple setup, encrypted root and swap via decrypt_derived so I can suspend to disk: /etc/crypttab: sda5_crypt UUID=2fa9feb8-b096-41f7-bf17-41399ccc8004 none luks sda4_crypt UUID=6d3382e4-58fc-4f10-9346-276bbc127e78 sda5_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived In /var/log/syslog: Mar 11 20:37:38 hercules systemd-cryptsetup[544]: Encountered unknown /etc/crypttab option 'keyscript=/lib/cryptsetup/scripts/decrypt_derived', ignoring. Any progress on this? I would think this needs to be fixed before jessie can be released, otherwise a lot of systems out there will break? Thanks & Cheers! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#853927: debian-installer: Hang in os-prober in "dmsetup create -r osprober-linux-sda1"
Hi, I tried installing RC2 (netboot) on my ASUS TP200SA yesterday and ran into a similar issue, os-prober hang during the install-grub phase. The thing here is that I'm neither using LVM nor any crypto, just the plain eMMC with a couple of partitions (see below). I could successfully finish the installation by manually killing the os-prober processes (there were multiple running) and then trying the GRUB re-install again via the install menu. The second time it worked. After I finished the installation I decided to try again, restarted a fresh installation and same thing - os-prober would hang on the first attempt but finish without any issues after killing and re-trying. Not sure if this any useful info but I thought I'd mention it b/c I don't see any reports for plain, non-encrypted, non-LVM disks showing this issue. But maybe it's a completely different problem? FWIW: root@flexo:~# fdisk -l Disk /dev/mmcblk0: 29.1 GiB, 31268536320 bytes, 61071360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 32DFD951-1036-41D1-A0A0-FA02557229F3 Device Start End Sectors Size Type /dev/mmcblk0p12048 4095 20481M BIOS boot /dev/mmcblk0p24096 395263 391168 191M EFI System /dev/mmcblk0p3 395264 5277695 4882432 2.3G Linux swap /dev/mmcblk0p4 5277696 5570559 292864 143M Linux filesystem /dev/mmcblk0p5 5570560 61069311 55498752 26.5G Linux filesystem Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk1: 59.8 GiB, 64223182848 bytes, 125435904 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Let me know if I can provide any other information. Cheers!
Bug#853927: debian-installer: Hang in os-prober in "dmsetup create -r osprober-linux-sda1"
Hi, right after replying to the bug report I decided to re-install, just for the fun of it. This obviously deleted the install logs, sorry. But this time I did not have the microSD card in my internal card reader like I usually do (/dev/mmcblk1 from my fdisk output) and the installation finished without os-prober getting stuck. So my guess is that the SD card may have been the culprit even though it does not contain any OS, just a plain ext4 file system (no partition table) that has some mp4 files on it. If you want me to I could re-install once again, with the SD card inserted, and check the logs. Let me know if that would be of any use. Cheers!
Bug#844505: patch seems to work!
Hi, I applied the patch from #15 and it seems to have fixed the segfault issues for me on stretch. Thanks Elias for fixing this. Cheers!
Bug#752266: systemd: laptop powers down on resume when suspended via power/suspend button
Package: systemd Version: 204-8 Severity: important I'm running jessie on a Dell M4800 laptop. I modified /etc/systemd/logind.conf to suspend when either the power or suspend key is pressed. This part is working, but when I try to wake the system up (via power button or by opening the lid), the system immediately initiates the power-off sequence and goes down. When triggering the suspend from the command line via "systemctl suspend" instead of pressing any of the assigned keys, the laptop resumes without issues. I tried with the laptop in the docking station and in "standalone" mode on battery and there is no difference in behavior. Thanks! -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libc62.19-1 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.4-1 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.2 ii udev 204-8 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandlePowerKey=suspend HandleSuspendKey=suspend HandleHibernateKey=hibernate HandleLidSwitch=ignore -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752266: systemd: laptop powers down on resume when suspended via power/suspend button
Hi Michael, thanks for the quick reply. Indeed, the acpi-support-base package was installed and after removing it the system seems to be behaving normally, i.e. it properly resumes when suspended via power button. Thanks! I don't know much (yet) about systemd, just switched over a few days ago, but now I'm wondering if it makes sense to uninstall all the acpi stuff - is all of acpi's functionality now being handled by systemd, or is there a good reason to keep acpi(d) installed on my system? And related to this question, what about laptop-mode-tools? Is there any good debian documentation of systemd that answers some of the basic questions for users? Thanks much for your help! -B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752266: systemd: laptop powers down on resume when suspended via power/suspend button
Hi Michael, thanks for your explanations and the link to documentation. Mostly I'm interested in finding out what functionality systemd is taking over from other packages. For instance, until the last system update, all my power management was handled exclusively by xfce4-power-manager. A nice convenient way that had all the settings in one place. xfce4-power-manager stopped working all of a sudden, because now systemd and logind are apparently dealing with power events instead. It just gets a bit muddy to figure out what service or program is now actually responsible for what on my system. There seems to be a lot of redundancy in functionality across many packages and subsystem (as expected for such a major migration), and I'm having a bit of a hard time staying on top of how to configure certain parts of my system now. I'll follow the link you provided and try to find some answers there. Again, thanks for your help. - B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756240: nvidia-settings: nvidia-settings removed when upgrading to nvidia-driver 340.24-2 and xserver 1.16
Package: nvidia-settings Version: N/A Severity: wishlist Hi, now that the nvidia-driver package is upgraded to work with xserver 1.16 (thanks!), is there any chance to get nvidia-settings back into sid/unstable? Muchas Gracias, - B -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756240: nvidia-settings: nvidia-settings removed when upgrading to nvidia-driver 340.24-2 and xserver 1.16
Hi Vincent, that's great, thank you very much for the links, and also for all your work on the nvidia packages! - B > I already built and uploaded it a week or so ago; it's currently > sitting in the NEW queue awaiting ftpmaster approval [1]. You can find > the actual packaging files by checking out [2] (which you can use to > build your own set of packages in the meantime), or fetch the > source+binaries I uploaded to ftpmaster that I'm hosting on my own > website temporarily [3]. > > Regards, > Vincent > > [1] https://ftp-master.debian.org/new/nvidia-settings_340.24-1.html > [2] svn://anonscm.debian.org/pkg-nvidia/packages/nvidia-graphics-drivers/trunk > [3] http://www.vcheng.org/nvidia-settings/ > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744343: icedtea-netx: policyeditor does not start, looks for wrong java version
Package: icedtea-netx Version: 1.5-1 Severity: important Launching policyeditor fails with the following error message: /usr/bin/policyeditor: line 102: /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java: No such file or directory Only java-7-openjdk installed, $$ aptitude search ~i | grep jdk i default-jdk - Standard Java or Java compatible Developme i openjdk-7-jdk - OpenJDK Development Kit (JDK) i A openjdk-7-jre - OpenJDK Java runtime, using Hotspot JIT i A openjdk-7-jre-headless - OpenJDK Java runtime, using Hotspot JIT (h but icedtea-netx apparently creates an incomplete java-6-openjdk directory that it is trying to use: $$ dpkg -S /us/lib/jvm/java-6-openjdk-amd64/ icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/man/man1/itweb-settings.1.gz icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/man/man1/javaws.1.gz icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/man/man1 icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/man/man1 icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/man/man1/itweb-settings.gz icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/javaws icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/man icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/bin icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/man/man1/javaws.1.gz icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/itweb-settings icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/man icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64 icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/bin/javaws icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/bin icedtea-netx:amd64: /usr/lib/jvm/java-6-openjdk-amd64/jre -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (690, 'unstable'), (680, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.5-1 ii openjdk-7-jre7u51-2.4.6-1 icedtea-netx recommends no packages. icedtea-netx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org