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#51783 - kscreen_backend broken in testing
Attached to Project:
Arch Linux
Opened by Hyacinthe Cartiaux (hcartiaux) - Thursday, 10 November 2016, 16:26 GMT
Last edited by Antonio Rojas (arojas) - Friday, 11 November 2016, 12:11 GMT
Opened by Hyacinthe Cartiaux (hcartiaux) - Thursday, 10 November 2016, 16:26 GMT
Last edited by Antonio Rojas (arojas) - Friday, 11 November 2016, 12:11 GMT
|
DetailsDescription:
This bug is probably already known, but I think libkscreen/kscreen_backend is broken in testing, causing KDE to fail at start-up with a cascade of strack traces in the logs. Additional info: * kscreen 5.8.3-1 * up-to-date testing environment (maybe related to the recent systemd update from 232-1 to 232-2) I attach the logs extract to this bug. Steps to reproduce: * Update your system using the *-testing repositories * Try to boot and start kde (I use sddm with autologin) Rebuilding libkscreen with pacman -Sb solved the problem. |
This task depends upon
Closed by Antonio Rojas (arojas)
Friday, 11 November 2016, 12:11 GMT
Reason for closing: Works for me
Friday, 11 November 2016, 12:11 GMT
Reason for closing: Works for me
bootlogs
I don't use any unofficial qt/kf packages.
I can't reproduce this issue on my system anymore, even if I reinstall the official libkscreen package.
I will add more details if it happens again, we can probably close this issue for the moment...