Summary: | Plasmashell crashes in PanelView::relativeConfigRect() just after clicking over the option to show the panel configuration from the context menu | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Robert Pereira <robertjspereira> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | kdedev, nate, sj |
Priority: | NOR | Keywords: | drkonqi |
Version: | 6.1.3 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.2.0 | |
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/32532/ |
Description
Robert Pereira
2024-07-28 19:01:12 UTC
Does it happen in a Wayland session too? Or only X11? How many screens and panels do you have? Can you make it happen at all in a new clean user account? *** Bug 484530 has been marked as a duplicate of this bug. *** Got a duplicate report, moving out of NEEDSINFO status so it doesn't get auto-closed since it seems this is reproducible by at least one other person. As I mentioned in the duplicated ticket, I can reproduce this crash stabily by opening the configuration pannel after a screen disconnect & reconnect (I only have one screen). I tested this on 6.1.3 and git-master - Caused a notification to appear with an email, it was above the notification icon as expected (lower right on my systems) - Connected an external monitor, disconnected it and reconnected it - Caused another notification git-master: Notifications appear in the same spot after reconnecting the monitor. No crash. 6.1.3: Notifications appear in wrong spot - in the lower left corner rather than the lower right above the icon. No crash. It appears this might be resolved in git-master, but I'll leave this open so more knowledgeable folks can add information if necessary At Nate's advice, I'm closing this out as resolved in 6.2 since it is not reproducable in git-master This should be fixed on your system when Plasma is updated to 6.2. If the bug still happens for you in that version, feel free to reopen this bug report. |