Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13014 - kde4 without hal
Attached to Project:
Arch Linux
Opened by CT (ctHx) - Wednesday, 28 January 2009, 03:04 GMT
Last edited by Pierre Schmitz (Pierre) - Tuesday, 24 February 2009, 19:33 GMT
Opened by CT (ctHx) - Wednesday, 28 January 2009, 03:04 GMT
Last edited by Pierre Schmitz (Pierre) - Tuesday, 24 February 2009, 19:33 GMT
DetailsDescription:
if dbus is not started i can't login (returning to kdm) if dbus is started i have first login failed(returning to kdm), second is ok with hal login is ok Additional info: * package version(s) kdebase-workspace-4.1.3-2,kdebase-workspace-4.2.0-2 * config and/or log files etc. Steps to reproduce: try to login kdm->kde without hal in rc.conf |
This task depends upon
Closed by Pierre Schmitz (Pierre)
Tuesday, 24 February 2009, 19:33 GMT
Reason for closing: Not a bug
Tuesday, 24 February 2009, 19:33 GMT
Reason for closing: Not a bug
with kde-workspace-4.1.3-1 works fine, i dont need start dbus or hal in rc.conf.
i dont need hal-features in kde (automount, hardware info plasmoids)
after updates i was surprised.
i think users should have choice, not all are using hal.
btw, howto switch off consolekit in kdebase-workspace?