Summary: | plasmashell crashes in QQmlPropertyCacheCreator on startup after boot | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | chiflutz |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | agurenko, bsnapcaps, cxfighter11, gloriouseggroll, kde.o9i1z, nate, nicolas.fella, nicolas.van.dyck |
Priority: | NOR | Keywords: | drkonqi, qt6 |
Version: | 6.0.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Flatpak | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
chiflutz
2024-03-14 17:33:02 UTC
*** Bug 484030 has been marked as a duplicate of this bug. *** *** Bug 483834 has been marked as a duplicate of this bug. *** *** Bug 483590 has been marked as a duplicate of this bug. *** I've worked around this by purging the plasmashell cache and selecting the Wayland session again in SDDM. It seems that this only occurs for the X11 session. I was able to reproduce the issue. It appears at least from testing on Nobara that plasma-x11 session only wants to load if a single display is connected. Any more than one and either plasma hangs at a black screen or boots out back to sddm login screen Please note that I was using Wayland, not x11 when the issue happened. All that I did was change the theme back to default Breeze Dark from a custom theme. I noticed an immediate issue with it not fully transitioning the theme, and upon reboot to try to fix it, I got the black screen (with ability to use terminal) regardless of Wayland or x11. Also, I only have one monitor, so I'm not sure if this is exactly the same issue as when someone has two monitors and gets a black screen. The backtraces here point to an issue with the QML disk cache, so it makes sense that clearing the cache fixes it. Any issues specific to X11 or Wayland or a particular display setup are most likely unrelated bugs *** Bug 483280 has been marked as a duplicate of this bug. *** (In reply to Nicolas Fella from comment #7) > The backtraces here point to an issue with the QML disk cache, so it makes > sense that clearing the cache fixes it. > > Any issues specific to X11 or Wayland or a particular display setup are most > likely unrelated bugs wrt that it might be worth retesting then as there was a recent rebuild for qml as of a yesterday (6.0.2-2 packages in nobara) (In reply to Tom Crider from comment #9) > > wrt that it might be worth retesting then as there was a recent rebuild for > qml as of a yesterday (6.0.2-2 packages in nobara) After the update, when switching sessions, there's a minor abrtapplet crash (x3), but nothing impacting plasmashell. I can't reproduce the original state of the cache anymore, didn't think to back it up, but I don't suppose it's important enough to dig through. The abrtapplet notification does not pop up if the login reuses the previous session, instead of switching. It's also not possible to report it from the notification window (no button), so if you missed the popup, you have to reproduce it in order to report it via drkonqi. Also after this update, SDDM does not follow the KDE Display Configuration, so if you're expecting to log in on your primary display, it will seem "locked up" - input doesn't display and mouse navigation is impeded by the fact that the cursor is on display 2 instead of 0, with no apparent common margin. This is only a problem if display 2 is a) HDMI and b) currently turned off. I'm aware that my setup is in the very low percentile of users (2x DP displays, 1x HDMI, all with different resolutions and refresh rates, on an nvidia GPU), so from where I'm standing, the KDE 6 release on Nobara 39 has been a fantastic success. Thank you for all your work! -- Including inxi output in case it's relevant: Graphics: Device-1: NVIDIA GA102 [GeForce RTX 3080] driver: nvidia v: 550.54.14 Display: server: X.Org v: 1.20.14 with: Xwayland v: 21.1.99 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia,nvidia-nvswitch resolution: 1: 2560x1440~144Hz 2: 1920x1080~60Hz 3: 3840x2160 API: EGL v: 1.5 drivers: nvidia,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14 renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 API: Vulkan v: 1.3.270 drivers: nvidia,llvmpipe surfaces: xcb,xlib Audio: Device-1: NVIDIA GA102 High Definition Audio driver: snd_hda_intel Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel API: ALSA v: k6.7.6-201.fsync.fc39.x86_64 status: kernel-api Info: Memory: total: 64 GiB available: 62.7 GiB used: 2.95 GiB (4.7%) Processes: 521 Uptime: 5h 49m Shell: Sudo inxi: 3.3.33 *** This bug has been marked as a duplicate of bug 418148 *** |