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#43640 - [plasma-workspace] graphics stack crashing
Attached to Project:
Arch Linux
Opened by Anders Lund (andersl) - Saturday, 31 January 2015, 10:03 GMT
Last edited by Felix Yan (felixonmars) - Tuesday, 03 March 2015, 14:22 GMT
Opened by Anders Lund (andersl) - Saturday, 31 January 2015, 10:03 GMT
Last edited by Felix Yan (felixonmars) - Tuesday, 03 March 2015, 14:22 GMT
|
DetailsDescription: After updating plasma-workspace, my desktop became very unstable, the graphics stack would crash and window and activity scitching became impossible. Downgrading to -1 fixed the problem.
Additional info: * package version(s) plasma-workspace 5.2.0-3 * config and/or log files etc. I use a acer V3-111 laptop with intel chips and graphics Steps to reproduce: start and try to cycle trough the alt-tab window switcher a few times. |
This task depends upon
Closed by Felix Yan (felixonmars)
Tuesday, 03 March 2015, 14:22 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed with 5.2.1.
Tuesday, 03 March 2015, 14:22 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed with 5.2.1.
Comment by Andrea Scarpino (BaSh) -
Saturday, 31 January 2015, 10:30 GMT
- Field changed: Summary (graphics stack crashing with plasma-workspace 5.2.0-3 → [plasma-workspace] graphics stack crashing)
- Field changed: Status (Unconfirmed → Assigned)
- Field changed: Category (Packages: Extra → Upstream Bugs)
- Task assigned to Andrea Scarpino (BaSh)
Please report upstream.
Comment by Anders Lund (andersl) -
Saturday, 31 January 2015, 10:39 GMT
The problem is with the changes between archlinux packages, the upstream package have not changed. I do not know what you changed in the packaging between -1 and -3 versions.
Comment by Felix Yan (felixonmars) -
Tuesday, 03 March 2015, 14:17 GMT
Do you still have this issue with 5.2.1-2?
Comment by Anders Lund (andersl) -
Tuesday, 03 March 2015, 14:19 GMT
No, this have gone with 5.2.1. See my comments here: https://forum.kde.org/viewtopic.php?f=289&t=125040&p=330560#p330560