Bug#769155: kde-workspace-bin: laptop does not go to sleep when critical battery level is reached
Hi, I tested with a third notebook (an old Compal CL51) upgraded from Wheezy to Jessie. The issue is the same and also the workaround is the same. The workaround is to enable the upower service with "systemctl enable upower" so that upower is started prior to PowerDevil. I'll change the severity back to grave as I installed Jessie now on three notebooks and can reproduce the issue with every installation. Regards Andi -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201503282251.22443.reportbug2...@afulinux.de
Bug#769155: kde-workspace-bin: laptop does not go to sleep when critical battery level is reached
Hi, Am Dienstag, 10. März 2015 schrieb Ronoaldo José de Lana Pereira: > I can confirm that starting upower before the KDE session makes everything > work as expected. As a workaround, I am currently using the /etc/rc.local > script to start upower with systemctl, as Andreas pointed out: > > 1) Make the /etc/rc.local script executable with: sudo chmod +x > /etc/rc.local > 2) Edit the file and add this line before the "exit 0" one: systemctl start > upower thanks for your feedback. Another way to workaround the issue is to enable the upower service with: systemctl enable upower Upower is then started automatically during boot. > I walked trough the kde-workspace-bin debian source, and seems like > PowerDevil launches the upower service via DBus if it is not running, but I > was unable to find out why the thread that monitors the battery level > change don't work properly in some cases. It looks like some hardware > specific information from the battery may cause be the issue, i.e., when > upower starts from PowerDevil, it may not work as expected and the thread > don't start properly. The weirdiest thing is that the battery icon *does* > work, i.e., it shows the proper level; only the low/critical actions aren't > triggered. > > I do agree, however, that the issue seems to be hardware specific, since it > don't happen with most users, but it should be put in a wiki/errata so > people can actually find the workaround for it. I tested another notebook, Dell Latitude E6330 and the issue is exactly the same. Also the workaround is the same. Since there are several years between the release dates of the two tested notebooks, it does not look like a hardware specific issue to me. Or the affected hardware base is really large. I'll tend to change the severity back to grave as I don't think that Jessie should be released with a non-working power management in KDE, but waiting for your feedback first. Stuart, as you could not reproduce the issue, please can you provide more details on when upower is started on your setup? Thanks Andreas
Bug#769155: kde-workspace-bin: laptop does not go to sleep when critical battery level is reached
Hi Stuart, I got a bit closer, when I start upower (using "systemctl start upower") before I login on KDM then everything works! Unfortunately I'm not such familiar with systemd yet, how is it supposed to work, when should /usr/lib/upower/upowerd get started? Thanks Andreas -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201503080251.14381.reportbug2...@afulinux.de
Bug#769155: kde-workspace-bin: laptop does not go to sleep when critical battery level is reached
Hi Stuart, I can reproduce the issue with an up to date Jessie. 1st scenario (not working): I boot the notebook with battery power, I login on KDM and when the KDE desktop is ready I wait till the warning (11%) and critical (10%) thresholds are reached but nothing happens, no messages and no suspend. "upower -d" output after login: Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: So 08 Mär 2015 01:32:27 CET (16 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Panasonic model:DELL JD6066 serial: 1135 power supply: yes updated: So 08 Mär 2015 01:32:29 CET (14 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: low energy: 4,2513 Wh energy-empty:0 Wh energy-full: 26,8509 Wh energy-full-design: 56,61 Wh energy-rate: 19,0476 W voltage: 11,2 V time to empty: 13,4 minutes percentage: 15% capacity:47,4314% technology: lithium-ion icon-name: 'battery-low-symbolic' History (charge): 1425774747 15,000 charging 1425774698 0,000 unknown History (rate): 1425774749 19,048 discharging 1425774747 26,784 charging 1425774698 0,000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Do 01 Jan 1970 01:00:00 CET (1425774763 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: low energy: 4,2513 Wh energy-full: 26,8509 Wh energy-rate: 19,0476 W time to empty: 13,4 minutes percentage: 15% icon-name: 'battery-low-symbolic' Daemon: daemon-version: 0.99.1 on-battery: yes lid-is-closed: no lid-is-present: yes critical-action: HybridSleep "upower -d" at 7% battery which is 3% below the critical threshold: Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: So 08 Mär 2015 01:32:27 CET (341 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Panasonic model:DELL JD6066 serial: 1135 power supply: yes updated: So 08 Mär 2015 01:37:59 CET (9 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: critical energy: 1,9647 Wh energy-empty:0 Wh energy-full: 26,8509 Wh energy-full-design: 56,61 Wh energy-rate: 24,864 W voltage: 10,608 V time to empty: 4,7 minutes percentage: 7% capacity:47,4314% technology: lithium-ion icon-name: 'battery-caution-symbolic' History (charge): 1425775079 7,000 discharging 1425775019 8,000 discharging 1425774989 9,000 discharging History (rate): 1425775079 24,864 discharging 1425775049 25,563 discharging 1425775019 25,397 discharging 1425774989 27,506 discharging Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Do 01 Jan 1970 01:00:00 CET (1425775088 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: critical energy: 1,9647 Wh energy-full: 26,8509 Wh energy-rate: 24,864 W time to empty: 4,7 minutes percentage: 7% icon-name: 'battery-caution-symbolic' Daemon: daemon-version: 0.99.1 on-battery: yes lid-is-closed: no lid-is-present: yes critical-action: HybridSleep 2nd scenario (not working): I boot the notebook with AC power, I login on KDM and when the KDE desktop is ready I disconnect the AC adaptor. I wait till the warning and critical thresholds are reached but nothing happens, no messages and no suspend. 3rd scenario (working): I boot the notebook with AC power. When o
Bug#769155: kde-workspace-bin: laptop does not go to sleep when critical battery level is reached
Stuart, I CAN reproduce it with a fresh install and others can reproduce it as well. Just in this bug report you find 3 people with the same issue. On the provided link you find even more. Booting Kubuntu on the exactly same hardware works without issues. So this is a bug in Debian Jessie. As upower is providing proper power details (see the attachment on Giorgos initial e-mail) I don't think that this is a general kernel bug. Anyway, if it's helpfull to try the Wheezy kernel on Jessie I can try it, but that's not fixing the issue. This IS a grave bug as a notebook relies on the power management capability of the chosen desktop environment to avoid data loss and file system corruption when battery runs empty. If the case is with a different package (I could think about libsolid4) it should be properly reassigned. What additional details can I provide for further troubleshooting? Thanks Andreas -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201503071446.29380.reportbug2...@afulinux.de
Bug#769155: kde-workspace-bin: PowerDevil is ignoring battery thresholds
Package: kde-workspace-bin Version: 4:4.11.13-2 Followup-For: Bug #769155 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I have installed Jessie with the RC1 i386 installer from the first CD on a Dell Latitude D620 notebook. It's a standard installation, nothing special. I just selected KDE instead of GNOME as desktop environment. To troubleshoot the issue I verified that suspend to disk, suspend to RAM and shutdown are generally working. To get a better understanding of the issue I enabled all notification messages within PowerDevil. PowerDevil is able to correctly display the battery level. When a power supply is connected or disconnected the icon changes accordingly and the corresponding notifications are shown. But battery warning and battery critical thresholds are not working at all. The configured thresholds are ignored, notifications are not shown, battery critical action (suspend to disk, suspend to RAM or shutdown) is not performed. Notebook looses power when battery runs empty. While searching for a solution I also found other users with this issue: https://lists.debian.org/debian-kde/2014/12/msg00025.html While troubleshooting I found out that when I boot with no battery installed and install the battery *after* KDE is started then PowerDevil is working as expected. A notebook relies on the power management capability of the chosen desktop environment to avoid data loss and file system corruption when battery runs empty. Thanks Andreas -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-workspace-bin depends on: ii iso-codes 3.57-1 ii kde-runtime 4:4.14.2-2 ii kde-style-oxygen 4:4.11.13-2 ii kde-workspace-data4:4.11.13-2 ii kde-workspace-kgreet-plugins 4:4.11.13-2 ii kscreen 1.0.2.1-1 ii libc6 2.19-13 ii libcln6 1.3.4-1 ii libdbusmenu-qt2 0.9.2-1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libice6 2:1.0.9-1+b1 ii libjpeg62-turbo 1:1.3.1-11 ii libkactivities6 4:4.13.3-1 ii libkcmutils4 4:4.14.2-5 ii libkdeclarative5 4:4.14.2-5 ii libkdecore5 4:4.14.2-5 ii libkdesu5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkfile4 4:4.14.2-5 ii libkidletime4 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libknewstuff3-4 4:4.14.2-5 ii libknotifyconfig4 4:4.14.2-5 ii libkparts44:4.14.2-5 ii libkpty4 4:4.14.2-5 ii libkscreensaver5 4:4.11.13-2 ii libkworkspace4abi24:4.11.13-2 ii libnepomukcore4 4:4.14.0-1+b2 ii libpam0g 1.1.8-3.1 ii libphonon44:4.8.0-4 ii libplasma34:4.14.2-5 ii libplasmagenericshell44:4.11.13-2 ii libpng12-01.2.50-2+b2 ii libprocesscore4abi1 4:4.11.13-2 ii libprocessui4a4:4.11.13-2 ii libqalculate5 0.9.7-9 ii libqimageblitz4 1:0.0.6-4 ii libqjson0 0.8.1-3 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libsm62:1.2.2-1+b1 ii libsolid4 4:4.14.2-5 ii libsoprano4 2.9.4+dfsg-1.1 ii libstdc++64.9.1-19 ii libstreamanalyzer00.7.8-1.2+b2 ii libudev1 215-11 ii libusb-0.1-4 2:0.1.12-25 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxft2 2.3.2-1 ii libxi62:1.7.4-1+b2 ii libxinerama1 2:1.1.3-1+b1 ii libxkbfile1 1:1.0.8-1 ii libxrandr22:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxtst6 2:1.2.2-1+b1 ii phonon
Bug#518511: krfb: crash (SIGABRT) after disconnect
I tried it on another PC with an identical setup but krfb does not crash. Only difference I can see is that this PC is using a single core CPU. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages krfb depends on: ii kdelibs4c2a 4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for ii libc62.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1.1 GCC support library ii libjpeg626b-14 The Independent JPEG Group's JPEG ii libqt3-mt3:3.3.8b-5+b1 Qt GUI Library (Threaded runtime ii libslp1 1.2.1-7.5 OpenSLP libraries ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-2 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime krfb recommends no packages. Versions of packages krfb suggests: ii khelpcente 4:4.0.0.really.3.5.9.dfsg.1-6 help center for KDE -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#518511: krfb: crash (SIGABRT) after disconnect
Subject: krfb: crash (SIGABRT) after disconnect Followup-For: Bug #518511 Package: krfb Version: 4:3.5.10-2 Hello, this issue is also replicable on Debian Lenny. The crash happens about 5 seconds after disconnecting the session. It happens on every disconnect. It also happens by aborting the password prompt, without entering a valid password. If the problem happens then it's no longer possible to connect to the PC using VNC which means that this is also a Denial of Service issue. It would be good to get it fixed in Lenny. Thanks, Andreas .xsession-errors output: QFile::open: No file name specified QFile::open: No file name specified *** glibc detected *** krfb: double free or corruption (!prev): 0x095912b0 *** === Backtrace: = /lib/i686/cmov/libc.so.6[0xb7696624] /lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7698826] /usr/lib/libX11.so.6[0xb755d229] krfb[0x805694d] krfb[0x8057a7d] krfb[0x8059277] krfb[0x805efa0] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb763e455] krfb(_ZNK7QDialog15minimumSizeHintEv+0xdd)[0x80553b1] === Memory map: 08048000-0808b000 r-xp 08:01 1140872/usr/bin/krfb 0808b000-0808e000 rw-p 00042000 08:01 1140872/usr/bin/krfb 0808e000-080a rw-p 0808e000 00:00 0 093fb000-095dc000 rw-p 093fb000 00:00 0 [heap] b3ec5000-b3ec6000 ---p b3ec5000 00:00 0 b3ec6000-b46c6000 rw-p b3ec6000 00:00 0 b46c6000-b46c7000 ---p b46c6000 00:00 0 b46c7000-b4ec7000 rw-p b46c7000 00:00 0 b4ec7000-b4ec8000 ---p b4ec7000 00:00 0 b4ec8000-b5d83000 rw-p b4ec8000 00:00 0 b630-b632c000 rw-p b630 00:00 0 b632c000-b640 ---p b632c000 00:00 0 b643e000-b6448000 r-xp 08:01 819951 /lib/i686/cmov/libnss_files-2.7.so b6448000-b644a000 rw-p 9000 08:01 819951 /lib/i686/cmov/libnss_files-2.7.so b644a000-b6451000 r-xp 08:01 819949 /lib/i686/cmov/libnss_compat-2.7.so b6451000-b6453000 rw-p 6000 08:01 819949 /lib/i686/cmov/libnss_compat-2.7.so b6478000-b6485000 r--p 08:01 597971 /usr/share/fonts/truetype/ttf-bitstream-vera/VeraMono.ttf b6485000-b64aa000 r--p 08:01 353031 /usr/share/locale/de/LC_MESSAGES/kio.mo b64aa000-b64b1000 r--s 08:01 212584 /usr/lib/gconv/gconv-modules.cache b64b1000-b64d r--p 08:01 435182 /usr/share/locale/de/LC_MESSAGES/libc.mo b64d-b650 r-xp 08:01 213946 /usr/lib/liblcms.so.1.0.16 b650-b6502000 rw-p 0002f000 08:01 213946 /usr/lib/liblcms.so.1.0.16 b6502000-b6504000 rw-p b6502000 00:00 0 b6504000-b6572000 r-xp 08:01 215696 /usr/lib/libmng.so.1.1.0.9 b6572000-b6575000 rw-p 0006e000 08:01 215696 /usr/lib/libmng.so.1.1.0.9 b658-b6589000 r-xp 08:01 819953 /lib/i686/cmov/libnss_nis-2.7.so b6589000-b658b000 rw-p 8000 08:01 819953 /lib/i686/cmov/libnss_nis-2.7.so b658b000-b659a000 r--p 08:01 597966 /usr/share/fonts/truetype/ttf-bitstream-vera/VeraBd.ttf b659a000-b659e000 r-xp 08:01 616688 /usr/lib/qt3/plugins/imageformats/libqmng.so b659e000-b659f000 rw-p 3000 08:01 616688 /usr/lib/qt3/plugins/imageformats/libqmng.so b659f000-b65b r--p 08:01 597974 /usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf b65b-b65ce000 r-xp 08:01 861773 /usr/lib/kde3/plugins/styles/plastik.so b65ce000-b65cf000 rw-p 0001e000 08:01 861773 /usr/lib/kde3/plugins/styles/plastik.so b65cf000-b65d3000 r--p 08:01 351822 /usr/share/locale/de/LC_MESSAGES/krfb.mo b65d3000-b6602000 r--p 08:01 352974 /usr/share/locale/de/LC_MESSAGES/kdelibs.mo b6602000-b6608000 r--s 08:01 425416 /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86.cache-2 b6608000-b6609000 r--s 08:01 425275 /var/cache/fontconfig/e3fa16a14183b06aa45b3e009278fd14-x86.cache-2 b6609000-b660d000 r--s 08:01 425305 /var/cache/fontconfig/926e794c3d5e5dffcaf2fa83ef8d36c2-x86.cache-2 b660d000-b661 r--s 08:01 425266 /var/cache/fontconfig/6eb3985aa4124903f6ff08ba781cd364-x86.cache-2 b661-b6617000 r--s 08:01 425258 /var/cache/fontconfig/6d41288fd70b0be22e8c3a91e032eec0-x86.cache-2 b6617000-b661a000 r--s 08:01 425264 /var/cache/fontconfig/de156ccd2eddbdc19d37a45b8b2aac9c-x86.cache-2 b661a000-b661b000 r--s 08:01 425401 /var/cache/fontconfig/9451a55048e8dbe8633e64d34165fdf2-x86.cache-2 b661b000-b661c000 r--s 08:01 425283 /var/cache/fontconfig/4794a0821666d79190d59a36cb4f44b5-x86.cache-2 b661c000-b663e000 r--s 08:01 425279 /var/cache/fontconfig/365b55f210c0a22e9a19e35191240f32-x86.cache-2 b663e000-b664 r--s 08:01 425280 /var/cache/fontconfig/0dad82dbaa6c15cf0806f139d62298a3-x86.cache-2 b664-b6642000 r--s 08:01 425273 /var/cache/fontconfig/de9486f0b47a4d768a594cb4198cb1c6-x86.cache-2 b6642000-b6649000 r--s 08:01 425287 /var/cache/fontconfig/d52a8644073d54c13679302ca1180695-x86.cache-2 b6649000-b664e000 r--s 08:01 425399 /var/cache/fontconfig/105b9c7e6f0a4f82d8c9b6e39c52c6f9-x86.cache-2 b664e000-b667d000 r--s 000
