Bug#1072142: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#1072142: fixed in nvidia-graphics-drivers 535.161.08-3)
Thank you, I can confirm that installing libnvidia-egl-wayland1 fixes the issue in 535.161.08-2 and presumably earlier versions too.
Bug#1061323: RFP: rust-toml2json -- A very small CLI for converting TOML to JSON
Control: retitle -1 ITP: rust-toml2json -- A very small CLI for converting TOML to JSON Control: owner -1 ! Well I ended packaging this, it's waiting in debcargo-conf at https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/653 Best, Facundo On Thu, Feb 22, 2024 at 1:39 PM Jonas Smedegaard wrote: > Quoting Facundo Gaich (2024-02-22 17:12:22) > > I can work on packaging this if you're still interested, I'd need a > sponsor. > > > > I've already done some preliminary work on this, in particular I renamed > > the bin to "rust-toml2json" but maybe you've got a better idea? > > If the command-line tool does somewhat the same as the existing one, I > suggest to rename it with the deviating part as the end instead, so that > users TAB-completing would easier notice the alternative: > toml2json-rust. > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > * Sponsorship: https://ko-fi.com/drjones > > [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#1071551: linux-image-6.8.9-amd64: Meteorlake pinctrl driver needed for Cirrus speakers
Package: src:linux Version: 6.8.9-1 Severity: important X-Debbugs-Cc: mpearson-len...@squebb.ca Hi, Testing debian sid on an Asus Zenbook UX3405MA, I found that there was no sound from the speakers. After quite some testing I figured that the pinctrl_meteorlake kernel module is needed for them to work (as well as the Cirrus firmware files mentioned in #1031912). This bug is also related to #1070650. In the logs below the problem is evidenced by the line >[ 13.834438] pxa2xx-spi pxa2xx-spi.3: problem registering SPI controller Thanks, Facundo -- Package-specific info: ** Version: Linux version 6.8.9-amd64 (debian-ker...@lists.debian.org) (x86_64-linux-gnu-gcc-13 (Debian 13.2.0-25) 13.2.0, GNU ld (GNU Binutils for Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.8.9-1 (2024-05-15) ** Command line: BOOT_IMAGE=/vmlinuz-6.8.9-amd64 root=UUID=593b0a47-1cd0-41bf-86c0-ec538420f603 ro quiet ** Not tainted ** Kernel log: [ 13.812563] sof-audio-pci-intel-mtl :00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl [ 13.812564] sof-audio-pci-intel-mtl :00:1f.3: Topology file: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg [ 13.812679] sof-audio-pci-intel-mtl :00:1f.3: firmware: direct-loading firmware intel/sof-ipc4/mtl/sof-mtl.ri [ 13.813168] sof-audio-pci-intel-mtl :00:1f.3: Loaded firmware library: ADSPFW, version: 2.9.0.1 [ 13.834438] pxa2xx-spi pxa2xx-spi.3: problem registering SPI controller [ 13.918865] sof-audio-pci-intel-mtl :00:1f.3: Booted firmware version: 2.9.0.1 [ 13.935239] sof-audio-pci-intel-mtl :00:1f.3: firmware: direct-loading firmware intel/sof-ace-tplg/sof-hda-generic-2ch.tplg [ 13.935301] sof-audio-pci-intel-mtl :00:1f.3: Topology: ABI 3:29:0 Kernel ABI 3:23:0 [ 13.935627] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred [ 13.944293] iwlwifi :00:14.3: Not valid error log pointer 0x0027B0C0 for RT uCode [ 13.944331] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f [ 13.944339] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 13.944345] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x80 [ 13.944352] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 13.944758] iwlwifi :00:14.3: firmware: direct-loading firmware iwlwifi-ma-b0-gf-a0.pnvm [ 13.944865] iwlwifi :00:14.3: loaded PNVM version ce1a5094 [ 13.945450] iwlwifi :00:14.3: RFIm is deactivated, reason = 4 [ 13.957597] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 13.957602] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.957604] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 13.957605] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 13.957606] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 13.960395] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [ 14.024222] input: ELAN9008:00 04F3:4213 as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input23 [ 14.024336] input: ELAN9008:00 04F3:4213 UNKNOWN as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input24 [ 14.024395] input: ELAN9008:00 04F3:4213 UNKNOWN as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input25 [ 14.024453] input: ELAN9008:00 04F3:4213 Stylus as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input26 [ 14.024589] input: ELAN9008:00 04F3:4213 UNKNOWN as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input28 [ 14.024631] input: ELAN9008:00 04F3:4213 UNKNOWN as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input29 [ 14.024670] input: ELAN9008:00 04F3:4213 UNKNOWN as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN9008:00/0018:04F3:4213.0002/input/input30 [ 14.026839] iwlwifi :00:14.3: base HW address: 4c:03:4f:c1:da:90 [ 14.042812] iwlwifi :00:14.3 wlo1: renamed from wlan0 [ 14.136842] hid-multitouch 0018:04F3:4213.0002: input,hidraw1: I2C HID v1.00 Device [ELAN9008:00 04F3:4213] on i2c-ELAN9008:00 [ 14.142375] EXT4-fs (nvme0n1p6): mounted filesystem db35944d-2acc-4e1d-9fa1-f7cdc4fc3bca r/w with ordered data mode. Quota mode: none. [ 14.173743] pxa2xx-spi pxa2xx-spi.3: problem registering SPI controller [ 14.210864] audit: type=1400 audit(1716253357.569:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=1006 comm="apparmor_parser" [ 14.211001] audit: type=1400 audit(1716253357.569:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oosplash" pid=1003 comm="apparmor_parser" [ 14.211066] audit: type=1400 audit(1716253357.569:4):
Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common
Hi, Today I upgraded one of my unstable machines and saw several instances of something I believe is the same bug. The resolver seems to be failing to choose to upgrade certain dependencies. What's more, in the aptitude GUI I can see the rightmost "latest available version" column change on the fly when I select certain packages for upgrade. For example, I currently have libnm0 and libnm0:i386 installed at 1.46.0-1 and I can see the latest version is 1.46.0-2. If I go into the GUI and choose to "Install" libnm0, the latest version column for libnm0:i386 will change from 1.46.0-2 to 1.46.0-1. Choosing "Install" on libnm0:i386 will then effectively do a keep of libnm0 at 1.46.0-1. To fix this, I can either go into libnm0:i386 and explicitly choose the newest version or I can restart the GUI and then it will list and choose the latest version correctly when I do Install libnm0:i386. aptitude version: 0.8.13-6 Best, Facundo
Bug#1065479: RFA: gtk-gnutella -- The Most Efficient Gnutella Client
On Tue, 5 Mar 2024 09:42:59 +0100 Lucio Marinelli wrote: > Package: wnpp > Severity: normal > > I am part of gtk-gnutella developing team and would like to add again > the deb package to Debian since it has been removed and no longer part > of the distribution: https://tracker.debian.org/pkg/gtk-gnutella > > Gtk-gnutella has been recently updated to version 1.2.3, this is the > website: https://gtk-gnutella.sourceforge.io > > -- > Lucio Marinelli > > Hi Lucio, Maybe you'll want to retitle this to an RFP since the package no longer exists in Debian and add the relevant info [1] [1]: https://www.debian.org/devel/wnpp/
Bug#1061323: RFP: rust-toml2json -- A very small CLI for converting TOML to JSON
Hi, I can work on packaging this if you're still interested, I'd need a sponsor. I've already done some preliminary work on this, in particular I renamed the bin to "rust-toml2json" but maybe you've got a better idea? Best, Facundo
Bug#1062820: fwupd: Fails to start if libfwupd version isn't an exact match
Package: fwupd Version: 1.9.10-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, While trying to dodge Bug #1061731, apt-listbugs pinned my version of fwupd to 1.9.10-1 but libfwupd was still upgraded, resulting in the following failure to start the daemon: Failed to load daemon: failed to load engine: libfwupd version 1.9.12 does not match daemon 1.9.10 I can see that the source code of fwupd requires an exact match between the two [1], so probably the Depends relation should be changed to strict match. Thanks, Facundo [1]: https://github.com/fwupd/fwupd/blob/3bc3e17c298a317565989268779a68c8e897c895/src/fu-engine.c#L8076 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.13-amd64 (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd depends on: ii adduser3.137 ii libarchive13 3.7.2-1 ii libc6 2.37-15 ii libcbor0.100.10.2-1.1 ii libcurl3-gnutls8.6.0-1 ii libflashrom1 1.3.0-2.1+b1 ii libfwupd2 1.9.12-4 ii libglib2.0-0 2.78.3-2 ii libgnutls303.8.3-1 ii libgudev-1.0-0 238-3 ii libgusb2 0.4.8-1 ii libjcat1 0.2.0-2 ii libjson-glib-1.0-0 1.8.0-2 ii liblzma5 5.4.5-0.3 ii libmbim-glib4 1.30.0-1 ii libmbim-proxy 1.30.0-1 ii libmm-glib01.22.0-3 ii libpolkit-gobject-1-0 124-1 ii libprotobuf-c1 1.4.1-1+b1 ii libqmi-glib5 1.34.0-2 ii libqmi-proxy 1.34.0-2 ii libsqlite3-0 3.45.1-1 ii libsystemd0255.3-2 ii libtss2-esys-3.0.2-0 4.0.1-3 ii libxmlb2 0.3.14-2 ii shared-mime-info 2.4-1 ii zlib1g 1:1.3.dfsg-3+b1 Versions of packages fwupd recommends: ii bolt 0.9.6-2 ii dbus 1.14.10-4 pn fwupd-signed ii jq 1.7.1-2 ii python33.11.6-1 pn secureboot-db ii udisks22.10.1-5 Versions of packages fwupd suggests: pn gir1.2-fwupd-2.0 -- Configuration Files: /etc/fwupd/fwupd.conf [Errno 13] Permission denied: '/etc/fwupd/fwupd.conf' -- no debconf information
Bug#1033479: closed by Thomas Goirand (Re: Bug#1033479: minissdpd: Service fails to start on boot with "Error parsing address/mask...")
On Thu, Jun 1, 2023 at 11:54 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Hi, > > This is IMO a missconfiguration, not a bug. Closing accordingly. > > Cheers, > > Thomas Goirand (zigo) > Hi Thomas, Thanks, although, isn't it still a bug if it arrived at a misconfigured state without user interaction?
Bug#1033479: minissdpd: Service fails to start on boot with "Error parsing address/mask..."
Package: minissdpd Version: 1.6.0-1 Severity: important Dear Maintainer, The minissdpd service fails on boot with the following: minissdpd[834]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd-systemd-wrapper[834]: Error parsing address/mask (or interface name) : br-REDACTED minissdpd-systemd-wrapper[834]: can't parse "br-REDACTED" as a valid interface name minissdpd[834]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd[834]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address minissdpd-systemd-wrapper[834]: Error parsing address/mask (or interface name) : docker0 minissdpd-systemd-wrapper[834]: can't parse "docker0" as a valid interface name minissdpd-systemd-wrapper[834]: Error parsing address/mask (or interface name) : enp2s0 minissdpd-systemd-wrapper[834]: can't parse "enp2s0" as a valid interface name minissdpd[834]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd-systemd-wrapper[834]: Error parsing address/mask (or interface name) : vethREDACTED minissdpd-systemd-wrapper[834]: can't parse "vethREDACTED" as a valid interface name minissdpd[834]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd-systemd-wrapper[834]: Error parsing address/mask (or interface name) : vethREDACTED minissdpd-systemd-wrapper[834]: can't parse "vethREDACTED" as a valid interface name minissdpd-systemd-wrapper[834]: Usage: /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i [-i ] ... minissdpd-systemd-wrapper[834]:is an interface name such as eth0. minissdpd-systemd-wrapper[834]: By default, socket will be open as /var/run/minissdpd.sock minissdpd-systemd-wrapper[834]: and pid written to file /var/run/minissdpd.pid systemd[1]: minissdpd.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: minissdpd.service: Failed with result 'exit-code'. systemd[1]: Failed to start minissdpd.service - keep memory of all UPnP devices that announced themselves. If I try to start it manually after boot it succeeds: systemd[1]: Starting minissdpd.service - keep memory of all UPnP devices that announced themselves... minissdpd[3276]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd-systemd-wrapper[3276]: Error parsing address/mask (or interface name) : br-REDACTED minissdpd-systemd-wrapper[3276]: can't parse "br-REDACTED" as a valid interface name minissdpd[3276]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd-systemd-wrapper[3276]: Error parsing address/mask (or interface name) : vethREDACTED minissdpd-systemd-wrapper[3276]: can't parse "vethREDACTED" as a valid interface name minissdpd[3276]: ioctl(s, SIOCGIFFLAGS, ...): No such device minissdpd-systemd-wrapper[3276]: Error parsing address/mask (or interface name) : vethREDACTED minissdpd-systemd-wrapper[3276]: can't parse "vethREDACTED" as a valid interface name systemd[1]: Started minissdpd.service - keep memory of all UPnP devices that announced themselves. Note that it now worked for the docker0 and enp2s0 infterfaces, so apparently the error on boot is because it can't find a single correct interface. The bridge and veth interfaces are not configured anymore in my system, not sure how they were added to /etc/default/minissdpd -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minissdpd depends on: ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers1.65.2 ii libc6 2.36-8 ii libnfnetlink0 1.0.2-2 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-2 minissdpd recommends no packages. minissdpd suggests no packages. -- Configuration Files: /etc/default/minissdpd changed [not included] -- debconf information excluded
Bug#1012154: binfmt-support.service errors with "unable to close /proc/sys/fs/binfmt_misc/register: File exists"
Package: binfmt-support Version: 2.2.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, The binfmt-support service fails to start, with the following output: systemd[1]: Starting Enable support for additional executable binary formats... update-binfmts[536]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: File exists update-binfmts[536]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: File exists update-binfmts[536]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: File exists update-binfmts[536]: update-binfmts: exiting due to previous errors systemd[1]: binfmt-support.service: Main process exited, code=exited, status=2/INVALIDARGUMENT systemd[1]: binfmt-support.service: Failed with result 'exit-code'. systemd[1]: Failed to start Enable support for additional executable binary formats. Best, Facundo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages binfmt-support depends on: ii libc6 2.33-7 ii libpipeline1 1.5.6-1 ii lsb-base 11.2 binfmt-support recommends no packages. binfmt-support suggests no packages. -- no debconf information
Bug#959674: snapd: Removing snapd leaves broken AppArmor profiles
Package: snapd Version: 2.44.1-2 Severity: normal Dear Maintainer, * What led up to the situation? Install snapd package, then remove it. The following boot I get these errors: May 03 13:33:15 fgserv systemd[1]: Starting Load AppArmor profiles... May 03 13:33:15 fgserv apparmor.systemd[532]: Restarting AppArmor May 03 13:33:15 fgserv apparmor.systemd[532]: Reloading AppArmor profiles May 03 13:33:15 fgserv apparmor.systemd[562]: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' May 03 13:33:15 fgserv apparmor.systemd[612]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' May 03 13:33:15 fgserv apparmor.systemd[532]: Error: At least one profile failed to load May 03 13:33:15 fgserv systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE May 03 13:33:15 fgserv systemd[1]: apparmor.service: Failed with result 'exit-code'. May 03 13:33:15 fgserv systemd[1]: Failed to start Load AppArmor profiles. Purging the package fixes this. Regards Facundo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/6 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) LSM: AppArmor: enabled Versions of packages snapd depends on: ii adduser 3.118 ii apparmor 2.13.4-1+b1 ii ca-certificates 20190110 ii gnupg2.2.20-1 ii libapparmor1 2.13.4-1+b1 ii libc62.30-4 ii libcap2 1:2.33-1 ii libseccomp2 2.4.3-1+b1 ii libudev1 245.5-2 ii openssh-client 1:8.2p1-4 ii squashfs-tools 1:4.4-2 ii systemd 245.5-2 ii udev 245.5-2 Versions of packages snapd recommends: ii gnupg 2.2.20-1 Versions of packages snapd suggests: ii zenity 3.32.0-5
Bug#958494: linux-image-5.5.0-2-amd64: Amdgpu / drm: No video signal/blank screen on resume from suspend
Package: src:linux Version: 5.5.17-1 Severity: normal Tags: upstream,fixed-in-experimental Dear Maintainer, This is a tracking bug for kernel bug #206575 (https://bugzilla.kernel.org/show_bug.cgi?id=206575), which is fixed in experimental. The problem occurs when using AMD graphic cards and amdgpu driver, after doing a suspend-to-ram and resuming, the monitor/screen will stay blank or show no signal. This problem is fixed with the kernel in linux-image-5.6.0-trunk-amd64:5.6.4-1~exp1 Regards, Facundo -- Package-specific info: ** Version: Linux version 5.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-10)) #1 SMP Debian 5.5.17-1 (2020-04-15) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.5.0-2-amd64 root=UUID=ac43c144-ff3f-4c08-b24e-b9d76e3d66e2 ro loglevel=8 ** Not tainted ** Kernel log: [4.213896] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [4.215770] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input18 [4.217432] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a [4.242801] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input19 [4.244655] EDAC amd64: F15h detected (node 0). [4.244673] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input20 [4.248111] EDAC amd64: Node 0: DRAM ECC disabled. [4.248174] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input21 [4.252407] input: HDA ATI SB Line Out Front as /devices/pci:00/:00:14.2/sound/card0/input22 [4.254110] input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input23 [4.254247] input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input24 [4.254310] input: HDA ATI SB Line Out Side as /devices/pci:00/:00:14.2/sound/card0/input25 [4.254375] input: HDA ATI SB Front Headphone as /devices/pci:00/:00:14.2/sound/card0/input26 [4.258773] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [4.276583] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. [4.283634] systemd[1]: Condition check resulted in FUSE Control File System being skipped. [4.283712] systemd[1]: Condition check resulted in Kernel Configuration File System being skipped. [4.283785] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [4.283803] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [4.283834] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [4.283875] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [4.285483] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. [4.285603] systemd[1]: Condition check resulted in FUSE Control File System being skipped. [4.285678] systemd[1]: Condition check resulted in Kernel Configuration File System being skipped. [4.285747] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [4.285766] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [4.285794] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [4.285821] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [4.299166] EDAC amd64: F15h detected (node 0). [4.299200] EDAC amd64: Node 0: DRAM ECC disabled. [4.348820] EDAC amd64: F15h detected (node 0). [4.350210] EDAC amd64: Node 0: DRAM ECC disabled. [4.353475] systemd[1]: Started Journal Service. [4.364948] systemd-journald[372]: Received client request to flush runtime journal. [4.389300] EDAC amd64: F15h detected (node 0). [4.392728] EDAC amd64: Node 0: DRAM ECC disabled. [4.441325] EDAC amd64: F15h detected (node 0). [4.444675] EDAC amd64: Node 0: DRAM ECC disabled. [4.693311] EDAC amd64: F15h detected (node 0). [4.696690] EDAC amd64: Node 0: DRAM ECC disabled. [5.428318] random: crng init done [5.430722] random: 7 urandom warning(s) missed due to ratelimiting [ 17.615174] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 17.662418] audit: type=1400 audit(1587587166.554:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=558 comm="apparmor_parser" [ 17.664032] audit: type=1400 audit(1587587166.554:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=560 comm="apparmor_parser" [ 17.56] audit: type=1400 audit(1587587166.554:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=560 comm="apparmor_parser" [
Bug#902437:
Hi, This is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901883
Bug#843457: mysql-workbench: Dependency gdal-abi-2-1-1 no longer in repo
Source: mysql-workbench Severity: grave Justification: renders package unusable Dear Maintainer, mysql-workbench depends on virtual package gdal-abi-2-1-1, which isn't provided by any other package since libgdal20 is now providing gdal-abi-2-1-2, rendering this package uninstallable. Thanks Facundo -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 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)
Bug#796504: aptitude: package titles appear as garbage text in Resolve Dep. window
Package: aptitude Version: 0.7-1+b1 Severity: normal Dear Maintainer, When opening the Resolve Dependencies windows, a subset of the packages titles are shown as random bytes instead, which changes after each keystroke. Looking at the system info below, it seems aptitude is currently built against ncruses 5.9 while the latest version in unstable is 6.0, so maybe that's the root of the problem. -- Package-specific info: Terminal: xterm-256color $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.7 compiled at Aug 7 2015 19:34:17 Compiler: g++ 5.2.1 20150730 Compiled against: apt version 4.16.0 NCurses version 5.9 libsigc++ version: 2.4.1 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.0.20150810 cwidget version: 0.5.17 Apt version: 4.16.0 aptitude linkage: linux-vdso.so.1 (0x7ffd6bbbf000) libapt-pkg.so.4.16 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.16 (0x7f53414b) libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f534128) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f5341055000) libsigc-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7f5340e4f000) libcwidget.so.3 = /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7f5340b5) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f5340882000) libboost_iostreams.so.1.58.0 = /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x7f5340669000) libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7f5340267000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f5340049000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f533fcce000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f533f9cd000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f533f7b6000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f533f40d000) libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f533f20a000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f533f005000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f533edea000) libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f533ebda000) liblzma.so.5 = /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f533e9b6000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f533e7ae000) libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f533e5a8000) /lib64/ld-linux-x86-64.so.2 (0x562f68c61000) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 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 aptitude depends on: ii aptitude-common 0.7-1 ii libapt-pkg4.161.0.10.2 ii libboost-iostreams1.58.0 1.58.0+dfsg-3 ii libc6 2.19-19 ii libcwidget3v5 0.5.17-4 ii libgcc1 1:5.2.1-15 ii libncursesw5 6.0+20150810-1 ii libsigc++-2.0-0v5 2.4.1-2 ii libsqlite3-0 3.8.11.1-1 ii libstdc++65.2.1-15 ii libtinfo5 6.0+20150810-1 ii libxapian22v5 1.2.21-1.2 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.7-1 ii libparse-debianchangelog-perl 1.2.0-6 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: ii apt-xapian-index 0.47 pn debtags none ii tasksel 3.33 -- no debconf information
Bug#785579: wpa_supplicant: terminates as soon as dbus is disconnected, causing shutdown ordering issues
On Sun, May 17, 2015 at 8:40 PM Michael Biebl bi...@debian.org wrote: Hi ... This issue has come up before and will hopefully become moot in the future, once we have kdbus. See https://bugs.freedesktop.org/show_bug.cgi?id=89847 Thanks Michael for the info. In conclusion and based on the bug you posted a passable fix in the meantime would be to add After=dbus.service to wpa_supplicant.service.
Bug#785579: wpa_supplicant: terminates as soon as dbus is disconnected, causing shutdown ordering issues
Package: wpasupplicant Version: 2.3-2 Severity: normal File: /sbin/wpa_supplicant Dear Maintainer, While trying to debug issues related to systemd unmounting NFS shares way after the network has gone down, I ran into problems trying to stop services before wpa_supplicant initiated deauth. Even tying my service (autofs.service) to NetworkManager with After=NetworkManager.service didn't work, wireless would get disconnected before it could unmount over the net. This is because wpa_supplicant will shutdown when the dbus is disconnected, as seen in these logs: wpa_supplicant[919]: dbus: bus disconnected, terminating wpa_supplicant[919]: wlan0: Removing interface wlan0 wpa_supplicant[919]: wlan0: Request to deauthenticate - bssid=REDACTED pending_bssid=00:00:00:00:00:00 reason=3 state=COMPLETED wpa_supplicant[919]: TDLS: Tear down peers wpa_supplicant[919]: wpa_driver_nl80211_deauthenticate(addr=REDACTED reason_code=3) wpa_supplicant[919]: wlan0: Event DEAUTH (12) received wpa_supplicant[919]: wlan0: Deauthentication notification wpa_supplicant[919]: wlan0: * reason 3 (locally generated) wpa_supplicant[919]: Deauthentication frame IE(s) - hexdump(len=0): [NULL] wpa_supplicant[919]: wlan0: CTRL-EVENT-DISCONNECTED bssid=REDACTED reason=3 locally_generated=1 Since this relationship is not set in the systemd configuration, the only way to correctly shutdown services that require wireless connection is to set After=dbus.service in them. Of course, this is not evident in any way, and it can cause bugs such as #761909. I'm not sure what the solution would be in this case, I'm cc'ing the systemd maintainers since it seems to me they have tackled this kind of problems with wlan before. Thanks, Facundo -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.1 (SMP w/4 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 wpasupplicant depends on: ii adduser 3.113+nmu3 ii libc6 2.19-18 ii libdbus-1-3 1.8.18-1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libpcsclite1 1.8.13-1 ii libreadline6 6.3-8+b3 ii libssl1.0.0 1.0.2a-1 ii lsb-base 4.1+Debian13+nmu1 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl none pn wpaguinone -- 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#785563: autofs: systemctl reload autofs.service: /usr/bin/kill not found
Package: autofs Version: 5.1.1-1 Severity: normal Dear Maintainer, The autofs unit file /lib/systemd/system/autofs.service includes this line: ExecReload=/usr/bin/kill -HUP $MAINPID However /usr/bin/kill is not found in the system so doing systemctl reload autofs.service results in the following error in the journal: systemd[1904]: Failed at step EXEC spawning /usr/bin/kill: No such file or directory systemd[1]: autofs.service: control process exited, code=exited status=203 systemd[1]: Reload failed for Automounts filesystems on demand. I believe the solution is to change the ExecReload line to use /bin/kill. Thanks, Facundo Gaich -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.1 (SMP w/4 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 autofs depends on: ii init-system-helpers 1.23 ii libc62.19-18 ii libxml2 2.9.2+dfsg1-3 ii multiarch-support2.19-18 ii ucf 3.0030 Versions of packages autofs recommends: ii kmod20-1 ii nfs-common 1:1.2.8-9 autofs 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#748074: rpcbind has no systemd unit and tmp file files
Package: rpcbind Version: 0.2.1-6 Followup-For: Bug #748074 Dear Maintainer, I've run into another bug that seems to be a symptom of not having a unit file. I decided against reporting a new one since it seems you're close to fixing this one. Currently, the [Unit] section of the rpcbind.service file autogenerated by systemd-sysv-generator (using systemd 215-17) looks like this: [Unit] SourcePath=/etc/init.d/rpcbind Description=LSB: RPC portmapper replacement DefaultDependencies=no Before=sysinit.target shutdown.target After=network-online.target local-fs.target Wants=network-online.target Conflicts=shutdown.target This creates the following ordering cycle on my system: systemd[1]: Found ordering cycle on sysinit.target/stop systemd[1]: Found dependency on rpcbind.service/stop systemd[1]: Found dependency on network-online.target/stop systemd[1]: Found dependency on network.target/stop systemd[1]: Found dependency on wpa_supplicant.service/stop systemd[1]: Found dependency on basic.target/stop systemd[1]: Found dependency on sysinit.target/stop systemd[1]: Breaking ordering cycle by deleting job rpcbind.service/stop systemd[1]: Job rpcbind.service/stop deleted to break ordering cycle starting with sysinit.target/stop I've noticed that this error message only appears during shutdown but not during boot. I'm not sure why this is. I'm also not sure why sysinit.target is being added to Before. Anyways, from what I've seen the manual unit file elsewhere in this thread should prevent this cycle from appearing. Thanks, Facundo Gaich -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.1 (SMP w/4 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 rpcbind depends on: ii initscripts 2.88dsf-59.1 ii insserv 1.14.0-5 ii libc62.19-18 ii libtirpc10.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13+nmu1 rpcbind recommends no packages. rpcbind 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#782980: par2: Typo in man page: -b should have a n argument
Package: par2 Version: 0.6.11-1 Severity: minor Dear Maintainer, In the man page for par2, the line -b Set the Block-Count should read -bn Set the Block-Count -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-rc7 (SMP w/4 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 par2 depends on: ii libc6 2.19-17 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 par2 recommends no packages. par2 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#757419: xrandr: Shows DVI-0 as connected to a non-existant monitor
Package: x11-xserver-utils Version: 7.7+3 Severity: important Dear Maintainer, I have a dual monitor setup with my Radeon HD 5770: a 1920x1080 one connected through HDMI and a 1050x1680 one connected through DVI. I have them setup as primary and secondary respectively, and everything was working fine on 7.7+2. After I updated to 7.7+3, my desktop was still working as intended until I launched once again the Displays configuration tool of Gnome 3.12, at which point my configuration broke (my primary monitor lost signal and I had to do a full power cycle to get to Displays again and fix it). Trying to repair it, I discovered xrandr is now showing a 1024x768 monitor on my other DVI port (DVI-0) which has nothing connected to it: Screen 0: minimum 320 x 200, current 2970 x 1680, maximum 8192 x 8192 DisplayPort-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+235 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0870.0760.00 832x624 74.55 800x600 72.1975.0060.32 56.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.81 66.6760.0059.94 720x400 70.08 DVI-0 connected (normal left inverted right x axis y axis) 1024x768 60.00 800x600 60.32 56.25 848x480 60.00 640x480 59.94 DVI-1 connected 1050x1680+1920+0 left (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 59.95*+ 1600x1000 60.01 1280x1024 75.02 1440x900 59.90 1280x960 60.00 1152x864 75.00 1152x720 59.97 1024x768 75.08 60.00 832x624 74.55 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 I was able to turn off this unknown device through Displays. I am using the radeon driver, I'm not sure if it could be a bug in there, since xrandr --listproviders shows: Providers: number : 1 Provider 0: id: 0x59 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 0 name:radeon Thank you, Facundo -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 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 x11-xserver-utils depends on: ii cpp 4:4.9.1-1 ii libc62.19-7 ii libice6 2:1.0.9-1 ii libx11-6 2:1.6.2-2 ii libxaw7 2:1.0.12-2 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.2-1 ii libxi6 2:1.7.4-1 ii libxmu6 2:1.1.2-1 ii libxmuu1 2:1.1.2-1 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.4-1 ii libxxf86vm1 1:1.1.3-1 x11-xserver-utils recommends no packages. Versions of packages x11-xserver-utils suggests: pn cairo-5cnone pn nickle none ii xorg-docs-core 1:1.7-1 -- 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#696347: Duplicate
Hi, This is a duplicate of #683854http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683854 Regards, Facundo
Bug#683854: solr-jetty: Broken symlink to solr's webapp
Package: solr-jetty Version: 3.6.0+dfsg-1 Severity: important Dear Maintainer, With the default configuration of both solr and jetty, the former should be reachable at localhost:8080/solr. Upon installation, that URL returns a 404 error. The cause: the package installs the following *broken* symlink to /var/lib/jetty/webapps: solr - /usr/share/solr/webapp where it should be: solr - /usr/share/solr/web/ -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 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 solr-jetty depends on: ii jetty6.1.26-1 ii libjetty-extra-java 6.1.26-1 ii solr-common 3.6.0+dfsg-1 solr-jetty recommends no packages. solr-jetty 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#665004: Solved
Hi, Touchpad is working properly again here too. In fact, it even seems to be working better. Good work guys.
Bug#665004: xserver-xorg-input-synaptics: scrolling stopped working after upgrade 1.5.0 -- 1.5.99
Package: xserver-xorg-input-synaptics Version: 1.5.99.901-1 Followup-For: Bug #665004 Also affects my ASUS 1015PE. Two-finger-tapping and three-finger-tapping are still working though. Apparently, scrolling is now only working if you do a fast swipe, as opposed to the previous version behaviour where doing precision scrolling by moving the fingers a few milimiters worked. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Mar 14 00:57 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2056560 Mar 4 20:44 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] (rev 02) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-2-amd64 (Debian 3.2.12-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Tue Mar 20 18:36:37 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 33771 Apr 9 21:13 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [19.152] X.Org X Server 1.11.4 Release Date: 2012-01-27 [19.152] X Protocol Version 11, Revision 0 [19.153] Build Operating System: Linux 3.2.0-1-amd64 x86_64 Debian [19.153] Current Operating System: Linux fgnet 3.2.0-2-amd64 #1 SMP Tue Mar 20 18:36:37 UTC 2012 x86_64 [19.153] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=6c216d95-00c7-4643-82de-ace766ffcac2 ro quiet [19.153] Build Date: 04 March 2012 11:42:13PM [19.153] xorg-server 2:1.11.4-1 (Cyril Brulebois k...@debian.org) [19.153] Current version of pixman: 0.24.4 [19.153]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [19.153] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [19.153] (==) Log file: /var/log/Xorg.0.log, Time: Mon Apr 9 19:22:49 2012 [19.194] (==) Using system config directory /usr/share/X11/xorg.conf.d [19.214] (==) No Layout section. Using the first Screen section. [19.214] (==) No screen section available. Using defaults. [19.214] (**) |--Screen Default Screen Section (0) [19.214] (**) | |--Monitor default monitor [19.225] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [19.225] (==) Automatically adding devices [19.225] (==) Automatically enabling devices [19.265] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [19.265]Entry deleted from font path. [19.281] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [19.281]Entry deleted from font path. [19.281] (==) 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 [19.281] (==) ModulePath set to /usr/lib/xorg/modules [19.281] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [19.281] (II) Loader magic: 0x7fb39a862ae0 [19.281] (II) Module ABI versions: [19.281]X.Org ANSI C Emulation: 0.4 [19.281]X.Org Video Driver: 11.0 [19.281]X.Org XInput driver : 13.0 [19.281]X.Org Server Extension : 6.0 [19.283] (--) PCI:*(0:0:2:0) 8086:a011:1043:83ac rev 2, Mem @ 0xf7e0/524288, 0xd000/268435456, 0xf7d0/1048576, I/O @ 0xdc00/8 [19.283] (--) PCI: (0:0:2:1) 8086:a012:1043:83ac rev 2, Mem @ 0xf7e8/524288 [19.283] (II) Open ACPI successful (/var/run/acpid.socket) [19.283] (II) LoadModule: extmod [19.294] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [19.306] (II) Module extmod: vendor=X.Org Foundation [19.306]compiled for 1.11.4, module version = 1.0.0 [19.306]Module class: X.Org Server Extension [19.306]ABI class: X.Org Server Extension, version 6.0 [19.306] (II) Loading extension SELinux [19.306] (II) Loading extension MIT-SCREEN-SAVER [19.306] (II) Loading extension XFree86-VidModeExtension [19.306] (II) Loading extension XFree86-DGA [19.306] (II) Loading extension DPMS [19.306] (II) Loading
Bug#574678: init_acpi_acadapt() returned NOT_SUPPORTED.
This is a bug in libacpi's handling of /sys/class/power_supply, which was never fully implemented. Also note that libacpi was last updated in 2008. Options: * Fix libacpi, which wouldn't be THAT hard and would in turn make battery-stats functional again. But is such a wrapper necessary with the current sysfs interface? Which takes us to option 2... * Make battery-stats-collector gather the data directly from /sys/class/power_supply * Stop using battery-stats and go with alternatives Thoughts?
