[opensuse] Strange acpid behavior in 12.3
Hi all, I'm a beginner in the openSUSE world. I recently installed openSUSE 12.3 in my two laptops, Thinkpad X200 tablet and HP Probook 6470b. I had no problems with the first laptop. But after I boot the Probook the acpi daemon doesn't detect battery changes nor closing the lid (I saw it running acpi_listen). Then I suspend the laptop using the Fn proper key, and, after I resume, the daemon seems work as I would expect on boot (battery status is reported right and I can suspend closing the lid). Anybody had the same problem? Tsao -- Francisco J. Tsao Santín http://tsao.enelparaiso.org 1024D/71CF4D62 42 F1 53 35 EF 98 98 8A FC 6C 56 B3 4C A7 7D FB
El 04/05/13 16:07, tsao@members.fsf.org escribió:
Hi all,
I'm a beginner in the openSUSE world. I recently installed openSUSE 12.3 in my two laptops, Thinkpad X200 tablet and HP Probook 6470b. I had no problems with the first laptop. But after I boot the Probook the acpi daemon doesn't detect battery changes nor closing the lid (I saw it running acpi_listen). Then I suspend the laptop using the Fn proper key, and, after I resume, the daemon seems work as I would expect on boot (battery status is reported right and I can suspend closing the lid).
Anybody had the same problem?
acpid will conflict with systemd-logind you have to use one of them, you have either to uninstall acpid or read logind.conf manual page to disable logind handling of HandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=, HandleLidSwitch= Many applications and desktop environments (KDE , X, GNOME, E17, not sure about others) no longer talk to acpid at all so you best bet is to use logind. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 4 May 2013, Cristian Rodríguez wrote:
either to uninstall acpid or read logind.conf manual page to disable logind handling of HandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=, HandleLidSwitch=
Many applications and desktop environments (KDE , X, GNOME, E17, not sure about others) no longer talk to acpid at all so you best bet is to use logind.
Ok, thanks. I was not aware of this conflict (I only used Debian until now, so I'm beginning to learn systemd ;-)). -- Francisco J. Tsao Santín http://tsao.enelparaiso.org 1024D/71CF4D62 42 F1 53 35 EF 98 98 8A FC 6C 56 B3 4C A7 7D FB
Cristian Rodr�������������������������������� wrote:
El 04/05/13 16:07, tsao@members.fsf.org escribi�: acpid will conflict with systemd-logind you have to use one of them, you have either to uninstall acpid or read logind.conf manual page to disable logind handling of HandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=, HandleLidSwitch=
Many applications and desktop environments (KDE , X, GNOME, E17, not sure about others) no longer talk to acpid at all so you best bet is to use logind.
There's a logind? That's separate from systemd? It seems odd that systemd would be considered a replacement for sysV's init if it didn't give login prompts to the configured terminals, I mean how would you login on a system with systemd that has init removed? If logind is required, why package them separately? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Cristian Rodríguez -
Francisco J. Tsao Santin -
Linda Walsh -
tsao＠members.fsf.org