¡Hola!
Adding the upower maintainers to the loop.
El 2015-03-28 a las 22:51 +0100, Andreas Stempfhuber escribió:
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
Hi,
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
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
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
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
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
Control: tag -1 unreproducible
Control: tag -1 normal
If changing the kernel helps then it's probably not a bug in kde-workspace-
bin. In any case, I can't reproduce this in jessie.
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer
Hi Andreas,
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.
Unfortunately, old data isn't useful -- yes, I did read the entire bug report
and the links
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
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
Package: kde-workspace-bin
Version: 4:4.11.13-2
Followup-For: Bug #769155
Dear Maintainer,
Confirming this bug with version 4.11.13-2.
I tested booting with linux-image-3.2.0-4-amd64 (3.2.65-1+deb7u1) and the
laptop has gone to hibernate when passing the critical level, so I think is
related
Package: kde-workspace-bin
Version: 4:4.11.13-1
Severity: normal
Dear Maintainer,
I'm following jessie and this is a feature which was working.
System settings - Power Management - Advanced Settings - Battery levels
- Battery is at low level at 30% , Battery is at critical level at 17%,
- When
12 matches
Mail list logo
