| Summary: | plasmashell segmentation fault | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Florian Wolfsjäger <florian> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | 5.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=341497 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
qdbus org.kde.KWin /KWin supportInformation
lshw -c video modinfo i915 |
||
|
Description
Florian Wolfsjäger
2015-08-13 13:10:31 UTC
I'm sorry but this backtrace lacks debug symbols, so it's impossible to say where and why it crashed, which is a requirement for fixing it. It's not so easy to get debug symbols in Arch, I had to recompile some packages to get at least that much. Almost every time when I'd like to get to the unlock screen (SDDM) kdeinit5 (package kinit) crashes, which can then only be resolved by killing the SDDM process. Sometimes some other processes, like plasma, crash as well. It's really annoying, if you can tell me how to get some proper debug information, I'd gladly provide you with those ;) I bet everyones every arms that the QXcbScreen is 0x0. run "kcmshell5 kded" and stop & disable the kscreen daemon. In case this is because your display turns off and kscreen unregisters it, that should prevent the crashes. Thanks for the tip, the kscreen daemon's deactivated now, I'll let you know if this "solves" my problem. (In reply to Thomas Lübking from comment #3) > I bet everyones every arms that the QXcbScreen is 0x0. > > run "kcmshell5 kded" and stop & disable the kscreen daemon. In case this is > because your display turns off and kscreen unregisters it, that should > prevent the crashes. Thanks a lot, my problem's solved, it no longer crashes and I get to the lock screen! I do have some other issues though were I weren't able to add debug symbols yet. It's about some screen flickering, issues with the plasma 5 taskbar, etc. Since I don't have any useful debug output I can't create a proper error message though, so may I contact anyone directly to get some hints on how to figure those out? Screen flicker may have various causes. Relevant information are - only with enabled compositor? - limited to some area (thr taskbar) or across the entire screen - used graphics hardware/drivers and in case of "compositing only issue", the output of qdbus org.kde.KWin /KWin supportInformation *** This bug has been marked as a duplicate of bug 341497 *** Created attachment 94037 [details]
qdbus org.kde.KWin /KWin supportInformation
Created attachment 94038 [details]
lshw -c video
Created attachment 94039 [details]
modinfo i915
(In reply to Thomas Lübking from comment #6) > Screen flicker may have various causes. > > Relevant information are > - only with enabled compositor? > - limited to some area (thr taskbar) or across the entire screen > - used graphics hardware/drivers and in case of "compositing only issue", > the output of > qdbus org.kde.KWin /KWin supportInformation > > *** This bug has been marked as a duplicate of bug 341497 *** It's hard to describe, some of the shell output that's printed before the display manager is started is shimmering / flickering through. It's only visible on dark backgrounds and happens on 2 areas across the entire screens. Though sometimes isn't there at all, I haven't figured out the cause yet. I can try starting with the compositor disabled, if I disable it afterwards using Alt+Shift+F12 it has no effect. Graphics hardware/info and qdbus /KWin supportInformation is attached ... I should probably create a new bug, if so, could you please tell me the product to select? > if I disable it afterwards using Alt+Shift+F12 it has no effect. iow not the compositor but the panel (an opengl context as well) flickers. Check uxa acceleration first https://wiki.archlinux.org/index.php/Intel_graphics#SNA_issues (In reply to Thomas Lübking from comment #11) > > if I disable it afterwards using Alt+Shift+F12 it has no effect. > iow not the compositor but the panel (an opengl context as well) flickers. > > Check uxa acceleration first > https://wiki.archlinux.org/index.php/Intel_graphics#SNA_issues I've already tried switching from UXA to SNA like that, sadly it doesn't help. (In reply to Florian Wolfsjäger from comment #12) > (In reply to Thomas Lübking from comment #11) > > > if I disable it afterwards using Alt+Shift+F12 it has no effect. > > iow not the compositor but the panel (an opengl context as well) flickers. > > > > Check uxa acceleration first > > https://wiki.archlinux.org/index.php/Intel_graphics#SNA_issues > > I've already tried switching from UXA to SNA like that, sadly it doesn't > help. The other way around, to UXA, sorry. |