| Summary: | [wayland] plasmashell crashes at startup | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | darkbasic |
| Component: | generic-wayland | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | bshah, edoantonioco, farkaslory, ict, mgraesslin, notmart, patrick.auernig, plasma-bugs-null, wawalkenhorst, xend54 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Session log
kstart5 plasmashell backtrace |
||
|
Description
darkbasic
2015-12-01 23:01:47 UTC
maybe it's trying to render on a surface not created yet? Do you have the abort message Qt prints? This is the only log I have: https://paste.lugons.org/show/9740/ I don't know where to find the QT abort message you are talking about. I forgot to say that if went so far it's because I disable OOM protection in kinit: https://aur.archlinux.org/cgit/aur.git/tree/001-disable-oom-protection.patch?h=kinit-nooom Otherwise all I get is just get a black window with a cursor. With latest git snapshot I get the "black screen with cursor" despite the kinit patch. (In reply to darkbasic from comment #4) > With latest git snapshot I get the "black screen with cursor" despite the > kinit patch. Same issue here. It's not the login manager since I've tried starting it with the command line. It has the nice breeze-themed cursor if that helps. *** Bug 355843 has been marked as a duplicate of this bug. *** It might be a "packaging" bug because I noticed the plasma ebuilds dropped the qt5-wayland dependency. I don't know if it's really necessary but the ebuilds no longer depend on it and someone on the arch forums stated it is mandatory: https://bbs.archlinux.org/viewtopic.php?pid=1584835#p1584835 *** Bug 360157 has been marked as a duplicate of this bug. *** I'm getting the same issue here, too. Running startplasmacompositor via .xinitrc results in a black screen with a Breeze-themed pointer. Pressing Alt-Space results in a delay and then krunner dropping down shakily from the top of the screen with distorted colours, so there seems to be something running... Running KF5 apps using '-platform wayland' from inside weston works perfectly. Plasma sessions via X11 work as expected. Weston/sway also run perfectly. I'm running Slackware current with a kdesrcbuild-built git master Plasma install (incl. kwayland and kwayland-integration), Qt 5.6.0, wayland/mesa/nouveau/drm git. I will attach my wayland session log. Created attachment 98149 [details]
Session log
(In reply to John Rowley from comment #9) > Running startplasmacompositor via .xinitrc Erm I hope you see the problem with trying to start wayland through *X*initrc. > I'm running Slackware current I'm sorry, but Slackware doesn't provide logind, which is a runtime requirement to start a Wayland session (Patches for other solutions welcome). I am running an ArchLinux box (I have logind) but plasmashell crashes. If I run the command: $kstart plasmashell Then I get: >kstart(...) main: Omitting both --window and --windowclass arguments is not recommended >KCrash: Attempting to start /usr/bin/plasmashell from kdeinit >sock_file=/run/user/1010/kdeinit5__0 >KCrash: Attempting to start /usr/lib/drkonqi from kdeinit >sock_file=/run/user/1010/kdeinit5__0 drkonqi does not start. For the command: $/usr/bin/plasmashell I get: >No metadata file in the package, expected it at: "/home/USERNAME/Desktop//metadata.desktop" 3x times, then >file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:80: TypeError: Cannot read property 'formFactor' of null And a bunch of line like that. Again KCrash ans sockfile and at the end: QsocketNotifier: Invalid socket 9 and type 'Read', disabling... (Sorry, the clipboard cannot paste its value to the browser.) As this issue is really old in terms of Wayland support I dare to set to unmaintained and assume that it is fixed by now. We have fixes all over the place - in Qt, KWin, KWayland, Plasma. It's quite likely that a ten month old crash is fixed now. Also I'm not able to test it anymore on the same machine, so I agree to close it. I did half an hour ago, after a full system refresh. I still have have crash. The spalsh screen shows up, then the ktorrent windows shows up, and that's all. Now at least I have a coredump. But it is 19mb. I cannot attach here. here is a link for the coredump: https://drive.google.com/open?id=0B5EdsRKfDCNqWloxVjFfLTNhS2c I would like to use wayland under KDE but in this state is useless. No panel, No menu for right button, nothing, just black screen. I would like to help (though I am not a developer) with anything that i can. But I do not know how to help. @Lorant: is this the same backtrace as the one in this bug report? Same issue, on manjaro, plasma 5.8, intel haswell. startplasmacompositor doesn't work either (black screen shows up) The coredump in comment 15 is a clean start and crash through sddm. As the ktorrent starts I can open a dolphin (it starts clean) and I can run commands though the konsole. If a run the command $kstart plasmashell kstart(7080) main: Omitting both --window and --windowclass arguments is not recommended then I can see my background image (that is an achievement) for several second. Then: KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__1 KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__1 I have coredump also for this: https://drive.google.com/file/d/0B5EdsRKfDCNqTWhCeXdIb2J5aHM/view?usp=sharing Please use "kstart5" instead of "kstart" when running KF5 applications. With $kstart5 plasmashell I got backtrace, attached here. Created attachment 101692 [details]
kstart5 plasmashell backtrace
(In reply to Lóránt Farkas from comment #21) > Created attachment 101692 [details] > kstart5 plasmashell backtrace That's a crash of kstart5 - please report a new bug for that one. |