so, well, today I also upgraded my good ols eeepc701 to r14 (from 3.5.13), not without some trouble (had to issue aptitude dist-upgrade several times), but finally, ran through and most things seem to work. unfortunately, kdepowersave stopped working. whien started from the cli, I get this:
kpowersave --force-acpi-check kpowersave: WARNING: Acquire org.freedesktop.Policy.Power interface failed with error: Connection ":1.13" is not allowed to own the service "org.freedesktop.Policy.Power" due to security policies in the configuration file kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: ERROR: Can't connect to HAL kpowersave: ERROR: Could not connect to HAL kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: ERROR: This machine does not support ACPI, APM, PMU, CPUFreq, Suspend2Disk nor Suspend2RAM. Please close KPowersave now. ERROR: Communication problem with kpowersave, it probably crashed.
so, seems to be related to hal. anyone got an idea how to fix this (OS is debian wheezy).
Werner
From: werner@hoernerfranzracing.de To: trinity-users@lists.pearsoncomputing.net Date: Mon, 22 Dec 2014 14:54:51 +0100 Subject: [trinity-users] kdepowersave
so, well, today I also upgraded my good ols eeepc701 to r14 (from 3.5.13), not without some trouble (had to issue aptitude dist-upgrade several times), but finally, ran through and most things seem to work. unfortunately, kdepowersave stopped working. whien started from the cli, I get this:
kpowersave --force-acpi-check kpowersave: WARNING: Acquire org.freedesktop.Policy.Power interface failed with error: Connection ":1.13" is not allowed to own the service "org.freedesktop.Policy.Power" due to security policies in the configuration file kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: ERROR: Can't connect to HAL kpowersave: ERROR: Could not connect to HAL kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: WARNING: HAL is not ready. We will try later... kpowersave: ERROR: This machine does not support ACPI, APM, PMU, CPUFreq, Suspend2Disk nor Suspend2RAM. Please close KPowersave now. ERROR: Communication problem with kpowersave, it probably crashed.
so, seems to be related to hal. anyone got an idea how to fix this (OS is debian wheezy).
Werner
Hi,
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore. It might be easier for you to find the package in Synaptic, depending on how you are comfortable with apt-get or aptitude. Then it should work!
-Alexandre
Am Montag, 22. Dezember 2014, 10:40:22 schrieb Alexandre:
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore.
well, of course I tried that :) but there is no tdepowersave whatsoever, only kpowersave-trinity
Werner
From: werner@hoernerfranzracing.de To: trinity-users@lists.pearsoncomputing.net Date: Mon, 22 Dec 2014 16:51:44 +0100 Subject: Re: [trinity-users] kdepowersave
Am Montag, 22. Dezember 2014, 10:40:22 schrieb Alexandre:
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore.
well, of course I tried that :) but there is no tdepowersave whatsoever, only kpowersave-trinity
Werner
Then it could be good to check the following:
1. Has the apt source list file been in-line with the new release? (Please compare it with the one in the Debian install page on this website.
2. Do you have Synaptic installed? In Synaptic, for me on Ubuntu (for test only, PCLinuxOS is better), the package has the tdepowersave-trinity name. It is easier to search package in Synaptic.
Hope it helps! -Alexandre
Am Montag, 22. Dezember 2014, 11:03:13 schrieb Alexandre:
Then it could be good to check the following:
- Has the apt source list file been in-line with the new release? (Please
compare it with the one in the Debian install page on this website.
yes, I followed the instructions on the trinity website for debian wheezy
- Do you have Synaptic installed?
no.
In Synaptic, for me on Ubuntu (for test only, PCLinuxOS is better), the package has the tdepowersave-trinity name. It is easier to search package in Synaptic.
I always search with apt-cache or aptitude. I suppose these would find the same things as synaptic, no ?
Werner
Am Montag, 22. Dezember 2014, 16:51:44 schrieb Werner Joss:
Am Montag, 22. Dezember 2014, 10:40:22 schrieb Alexandre:
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore.
well, of course I tried that :) but there is no tdepowersave whatsoever, only kpowersave-trinity
additional note: kpowersave does work if I start /usr/sbin/hald before manually. will now try to figure out why hald is no more started automatically after the dist-upgrade.
Werner
From: werner@hoernerfranzracing.de To: trinity-users@lists.pearsoncomputing.net Date: Mon, 22 Dec 2014 17:07:10 +0100 Subject: Re: [trinity-users] kdepowersave
Am Montag, 22. Dezember 2014, 16:51:44 schrieb Werner Joss:
Am Montag, 22. Dezember 2014, 10:40:22 schrieb Alexandre:
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore.
well, of course I tried that :) but there is no tdepowersave whatsoever, only kpowersave-trinity
additional note: kpowersave does work if I start /usr/sbin/hald before manually. will now try to figure out why hald is no more started automatically after the dist-upgrade.
Werner
Looks like the flaky Debian package management is doing you trouble. kpowersave requiring HAL should not be there anymore, and should be replaced by tdepowersave-trinity, which does not require HAL; HAL is of no use for R14...
-Alexandre
On Mon, 22 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 16:51:44 schrieb Werner Joss:
Am Montag, 22. Dezember 2014, 10:40:22 schrieb Alexandre:
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore.
well, of course I tried that :) but there is no tdepowersave whatsoever, only kpowersave-trinity
additional note: kpowersave does work if I start /usr/sbin/hald before manually. will now try to figure out why hald is no more started automatically after the dist-upgrade.
Werner
I am keen on your results. I have had this problem for months now.
F.
On Mon, 22 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 16:51:44 schrieb Werner Joss:
Am Montag, 22. Dezember 2014, 10:40:22 schrieb Alexandre:
If I were you, I would look for replacing the kpowersave package with something named tdepowersave, which doesn't need HAL anymore.
well, of course I tried that :) but there is no tdepowersave whatsoever, only kpowersave-trinity
additional note: kpowersave does work if I start /usr/sbin/hald before manually. will now try to figure out why hald is no more started automatically after the dist-upgrade.
Werner
I am keen on your results. I have had this problem for months now.
F.
-- Felmon Davis
A person with one watch knows what time it is; a person with two watches is never sure. Proverb
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
-ALexandre
Am Montag, 22. Dezember 2014, 11:21:26 schrieb Alexandre:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
well, problem solved :) it turned out that - my /etc/apt/sources.list.d/trinity.list file (which kept the entries for trinity) had vanished during my initial several 'dist-upgrades' (forced by errors) - once fixed, aptitude found tdepowersave, which would uninstall/replace kpowersave upon installation
after next reboot, tdepowersave starts automatically and works as expected. thanks for your help.
Werner
On Mon, 22 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 11:21:26 schrieb Alexandre:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
well, problem solved :) it turned out that
- my /etc/apt/sources.list.d/trinity.list file (which kept the entries for
trinity) had vanished during my initial several 'dist-upgrades' (forced by errors)
- once fixed, aptitude found tdepowersave, which would uninstall/replace
kpowersave upon installation
after next reboot, tdepowersave starts automatically and works as expected. thanks for your help.
glad you got yours figured out. not so lucky here.
trying to install the new release practically killed my system. I wrestled it back to near health though there are still issues, including the kpowersave issue. I didn't have tdepowersave in apt-cache.
I took the hard-drive out and put in a new virgin one, did a new install but for carrying over home. that has the tdepowersave app but it is misbehaving: it shuts down the system no matter what I put in the configuration menu. (or maybe something else does...?)
guess this is an advance since the other version either didn't have a config menu or only had one after manually loading hald. even then I wasn't sure it was doing anything.
the new ssd card is cool though. makes a difference I hadn't noticed on my netbook, the laptop has more and faster cpus.
F.
Am Montag, 22. Dezember 2014, 15:58:33 schrieb Felmon Davis:
On Mon, 22 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 11:21:26 schrieb Alexandre:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
well, problem solved :) it turned out that
- my /etc/apt/sources.list.d/trinity.list file (which kept the entries for
trinity) had vanished during my initial several 'dist-upgrades' (forced by errors)
- once fixed, aptitude found tdepowersave, which would uninstall/replace
kpowersave upon installation
after next reboot, tdepowersave starts automatically and works as expected. thanks for your help.
glad you got yours figured out. not so lucky here.
trying to install the new release practically killed my system. I wrestled it back to near health though there are still issues, including the kpowersave issue. I didn't have tdepowersave in apt-cache.
that was here only with vanished sources.list entrys for trinity.
I took the hard-drive out and put in a new virgin one, did a new install but for carrying over home. that has the tdepowersave app but it is misbehaving: it shuts down the system no matter what I put in the configuration menu. (or maybe something else does...?)
I suppose, it must be something else.
guess this is an advance since the other version either didn't have a config menu or only had one after manually loading hald. even then I wasn't sure it was doing anything.
does it at least show the battery status ? (it should, of course).
Werner
On Tue, 23 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 15:58:33 schrieb Felmon Davis:
On Mon, 22 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 11:21:26 schrieb Alexandre:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
well, problem solved :) it turned out that
- my /etc/apt/sources.list.d/trinity.list file (which kept the entries for
trinity) had vanished during my initial several 'dist-upgrades' (forced by errors)
- once fixed, aptitude found tdepowersave, which would uninstall/replace
kpowersave upon installation
after next reboot, tdepowersave starts automatically and works as expected. thanks for your help.
glad you got yours figured out. not so lucky here.
trying to install the new release practically killed my system. I wrestled it back to near health though there are still issues, including the kpowersave issue. I didn't have tdepowersave in apt-cache.
that was here only with vanished sources.list entrys for trinity.
not sure what you mean by 'vanished'. in the end though I'm supposing something was wrong with the sources.list I used. maybe I'll hook up that hard-drive and have another look.
I'm a bit spoiled by the pleasant speed of the ssd card on this laptop so I doubt I'll put the old hard-drive back into actual use.
(got to research the 'trim' issues.)
I took the hard-drive out and put in a new virgin one, did a new install but for carrying over home. that has the tdepowersave app but it is misbehaving: it shuts down the system no matter what I put in the configuration menu. (or maybe something else does...?)
I suppose, it must be something else.
slowly I think so too and in fact I'm suspecting I made an error somewhere.
guess this is an advance since the other version either didn't have a config menu or only had one after manually loading hald. even then I wasn't sure it was doing anything.
does it at least show the battery status ? (it should, of course). Werner
I'll tell you when I boot up that drive again.
Mike Bird downthread gave some intriguing advice; I'll prob try that too.
F.
On Tuesday 23 of December 2014 09:51:55 Felmon Davis wrote:
On Tue, 23 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 15:58:33 schrieb Felmon Davis:
On Mon, 22 Dec 2014, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 11:21:26 schrieb Alexandre:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
well, problem solved :) it turned out that
- my /etc/apt/sources.list.d/trinity.list file (which kept the entries
for trinity) had vanished during my initial several 'dist-upgrades' (forced by errors)
- once fixed, aptitude found tdepowersave, which would
uninstall/replace kpowersave upon installation
after next reboot, tdepowersave starts automatically and works as expected. thanks for your help.
glad you got yours figured out. not so lucky here.
trying to install the new release practically killed my system. I wrestled it back to near health though there are still issues, including the kpowersave issue. I didn't have tdepowersave in apt-cache.
that was here only with vanished sources.list entrys for trinity.
not sure what you mean by 'vanished'. in the end though I'm supposing something was wrong with the sources.list I used. maybe I'll hook up that hard-drive and have another look.
I'm a bit spoiled by the pleasant speed of the ssd card on this laptop so I doubt I'll put the old hard-drive back into actual use.
(got to research the 'trim' issues.)
I took the hard-drive out and put in a new virgin one, did a new install but for carrying over home. that has the tdepowersave app but it is misbehaving: it shuts down the system no matter what I put in the configuration menu. (or maybe something else does...?)
I suppose, it must be something else.
slowly I think so too and in fact I'm suspecting I made an error somewhere.
guess this is an advance since the other version either didn't have a config menu or only had one after manually loading hald. even then I wasn't sure it was doing anything.
does it at least show the battery status ? (it should, of course). Werner
I'll tell you when I boot up that drive again.
Mike Bird downthread gave some intriguing advice; I'll prob try that too.
F.
Regarding losses apt sources I have one idea - previously was one package trinity-keyring, which contained both GPG key and APT sources list. Now are two separate packages trinity-keyring and trinity-apt-archive. If your apt sources previously came from package trinity-keyring, after upgrade this package apt sources list would disappear.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/23/2014 01:37 AM, Werner Joss wrote:
Am Montag, 22. Dezember 2014, 11:21:26 schrieb Alexandre:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
well, problem solved :) it turned out that - my /etc/apt/sources.list.d/trinity.list file (which kept the entries for trinity) had vanished during my initial several 'dist-upgrades' (forced by errors) - once fixed, aptitude found tdepowersave, which would uninstall/replace kpowersave upon installation
after next reboot, tdepowersave starts automatically and works as expected. thanks for your help.
Werner
Just as a note to all, R14.0.0 on Linux does not require HAL. If you still have HAL installed after the upgrade, this could indicate that something went wrong. Cheers Michele
Am Dienstag, 23. Dezember 2014 schrieb Michele Calgaro:
Just as a note to all, R14.0.0 on Linux does not require HAL. If you still have HAL installed after the upgrade, this could indicate that something went wrong. Cheers Michele
On wheezy, too? "dpkg -l|grep hal" says:
ii hal 0.5.14-8 amd64 Hardware Abstraction Layer ii hal-info 20091130-1 all Hardware Abstraction Layer - fdi ii hal-trinity 4:0-0debian2 all Trinity HAL metapackage ii libhal-storage 0.5.14-8 amd64 Hardware Abstraction Layer - shar ii libhal1 0.5.14-8 amd64 Hardware Abstraction Layer - shar
Nik
Am Dienstag, 23. Dezember 2014, 09:18:56 schrieb Dr. Nikolaus Klepp:
Am Dienstag, 23. Dezember 2014 schrieb Michele Calgaro:
Just as a note to all, R14.0.0 on Linux does not require HAL. If you still have HAL installed after the upgrade, this could indicate that something went wrong. Cheers
Michele
On wheezy, too? "dpkg -l|grep hal" says:
ii hal 0.5.14-8 amd64 Hardware Abstraction Layer ii hal-info 20091130-1 all Hardware Abstraction Layer - fdi ii hal-trinity 4:0-0debian2 all Trinity HAL metapackage ii libhal-storage 0.5.14-8 amd64 Hardware Abstraction Layer - shar ii libhal1 0.5.14-8 amd64 Hardware Abstraction Layer -
same here.
Werner
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2014/12/23 05:27 PM, Werner Joss wrote:
Am Dienstag, 23. Dezember 2014, 09:18:56 schrieb Dr. Nikolaus Klepp:
Am Dienstag, 23. Dezember 2014 schrieb Michele Calgaro:
Just as a note to all, R14.0.0 on Linux does not require HAL. If you still have HAL installed after the upgrade, this could indicate that something went wrong. Cheers
Michele
On wheezy, too? "dpkg -l|grep hal" says:
ii hal 0.5.14-8 amd64 Hardware Abstraction Layer ii hal-info 20091130-1 all Hardware Abstraction Layer - fdi ii hal-trinity 4:0-0debian2 all Trinity HAL metapackage ii libhal-storage 0.5.14-8 amd64 Hardware Abstraction Layer - shar ii libhal1 0.5.14-8 amd64 Hardware Abstraction Layer -
same here.
Werner
Yes, on Wheezy too. R14.0.0 in Linux relies on tdehwlib and does not required HAL. I just completed an upgrade in Wheezy from 3.5.13.2 to R14.0.0 and no HAL is not installed. There were a few left-over configuration files as in:
~# dpkg -l |grep hal | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend rc hal 0.5.14-8 amd64 Hardware Abstraction Layer rc libhal-storage1 0.5.14-8 amd64 Hardware Abstraction Layer - shared library for storage devices rc libhal1 0.5.14-8 amd64 Hardware Abstraction Layer - shared library
but a simple clean up with aptitude got rid of it. You should be able to get rid of HAL without major problems, unless you are using other programs that specifically require it.
Cheers Michele
On Tue December 23 2014 00:18:56 Dr. Nikolaus Klepp wrote:
On wheezy, too? "dpkg -l|grep hal" says:
ii hal 0.5.14-8 amd64 Hardware Abstraction Layer ii hal-info 20091130-1 all Hardware Abstraction Layer - fdi ii hal-trinity 4:0-0debian2 all Trinity HAL metapackage ii libhal-storage 0.5.14-8 amd64 Hardware Abstraction Layer - shar ii libhal1 0.5.14-8 amd64 Hardware Abstraction Layer - shar
You can do "apt-get install tdepowersave-trinity". After that you can do "dpkg --dry-run --purge hal hal-info libhal-storage1 libhal1" and if it looks OK repeat without the "--dry-run".
--Mike
I had the problem on a new install. It weas a fresh wheezy + TDE14 install.
On synaptics at least some "informations" are problematic. Actually, three packages are (more or less available):
I first looked for kpowersave (that's what I am used to) and found two pakackages:
- kpowersave-trinity, requiring HAL (it is sitll there, it installs but does not work: I get a greyed out icon in the system tray). Trying to start it complained about HAL not being installed
- kpowersave-nohal-trinity, indicated as a dummy package. When I tried to install it colored red and said it depended on a package (I think now it was tdepowersave, but I am not sure) that was not to be installed.
After reading the list I removed the non-working kpowersave and apt-get installed tdepowersave and that works perfectly.
I don't know if the two kpowersave are necessary, but most "old" users being used to them they actually work as a trap :)
Thierry
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 12/24/2014 04:59 PM, Thierry de Coulon wrote:
I had the problem on a new install. It weas a fresh wheezy + TDE14 install.
On synaptics at least some "informations" are problematic. Actually, three packages are (more or less available):
I first looked for kpowersave (that's what I am used to) and found two pakackages:
- kpowersave-trinity, requiring HAL (it is sitll there, it installs but does not work: I get a greyed out icon in
the system tray). Trying to start it complained about HAL not being installed
- kpowersave-nohal-trinity, indicated as a dummy package. When I tried to install it colored red and said it
depended on a package (I think now it was tdepowersave, but I am not sure) that was not to be installed.
After reading the list I removed the non-working kpowersave and apt-get installed tdepowersave and that works perfectly.
I don't know if the two kpowersave are necessary, but most "old" users being used to them they actually work as a trap :)
Thierry
Hi Thierry, kpowersave has been replaced in Linux by tdepowersave. In Wheezy it is still available, but in Jessie it will no longer be there, since HAL is not available anymore and so kpowersave does not build in Jessie at all.
Cheers Michele
On Wednesday 24 December 2014 9:20:28 pm you wrote:
On 12/24/2014 04:59 PM, Thierry de Coulon wrote:
I had the problem on a new install. It weas a fresh wheezy + TDE14 install.
On synaptics at least some "informations" are problematic. Actually, three packages are (more or less available):
I first looked for kpowersave (that's what I am used to) and found two pakackages:
- kpowersave-trinity, requiring HAL (it is sitll there, it installs but
does not work: I get a greyed out icon in the system tray). Trying to start it complained about HAL not being installed
- kpowersave-nohal-trinity, indicated as a dummy package. When I tried to
install it colored red and said it depended on a package (I think now it was tdepowersave, but I am not sure) that was not to be installed.
After reading the list I removed the non-working kpowersave and apt-get installed tdepowersave and that works perfectly.
I don't know if the two kpowersave are necessary, but most "old" users being used to them they actually work as a trap :)
Thierry
Hi Thierry, kpowersave has been replaced in Linux by tdepowersave. In Wheezy it is still available, but in Jessie it will no longer be there, since HAL is not available anymore and so kpowersave does not build in Jessie at all.
Cheers Michele
?? Jessie & R14
I have tdepowersave-trinity here, only one kdepowersave package...the 'dummy' package.
On Monday 22 December 2014 16:21:26 Alexandre wrote:
Can you post a screenshot of you searching for the keyword powersave in Synaptic. It is very very unlikely that it is not there.
Alexandre -
Your preference for GUI is to be respected, but so is the preference of many of us for the CLI. In the days when I administered computers with Synaptic installed I have solved may a Synaptic snarl-up by switching to aptitude at the CLI.
Aptitude search is every bit as reliable as any searching on Synaptic, I would feel more so. tdepowersave wasn't there because of a sources.list problem. Not because Synaptic is somehow magic and apt and aptitude are rubbish.
Lisi