[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |ASSIGNED --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreen/-/merge_requests/199 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #7 from Luca Bacci --- Observing the member output object for destruction was done as part of https://invent.kde.org/plasma/kscreen/-/commit/071282f545, which sends to https://phabricator.kde.org/D9414 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #6 from Luca Bacci --- Thanks for the report, Bucior! Seems to be a different issue according to the stacktrace, most probably in KScreen. The stacktrace is very useful! :) KScreen::Osd keeps a reference to a LibKScreen::Output. When Osd instances are destroyed, their references to LibKScreen::Output instances are dropped, and that can cause their immediate destruction. Osd also subscribes as an observeer for its member LibKScreen::Output's destruction: https://invent.kde.org/plasma/kscreen/-/blob/v5.27.2/osd/osd.cpp#L33. The handler method is Osd::hideOsd() is executed, but at that time Osd is already in the process of being destructed... As for fixes, we may ::disconnect() in Osd's destructor. However I don't get why Osd observes its member object for destruction if it keeps a reference to it? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #4 from Bucior --- Created attachment 157154 --> https://bugs.kde.org/attachment.cgi?id=157154=edit kscreen crash I also had this crash, just switching monitors, previous i was using tv more i will try to reproduce once more -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #3 from Luca Bacci --- This seems to be an issue in the dconf GSettingsBackend. I have opened an issue at https://gitlab.gnome.org/GNOME/dconf/-/issues/79 for now, but will investigate more! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #2 from Luca Bacci --- Yeah, may be. I'm gonna take a look at this! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 Nate Graham changed: What|Removed |Added CC||luca.ba...@outlook.com, ||n...@kde.org Component|common |general Assignee|kscreen-bugs-n...@kde.org |unassigned-b...@kde.org Product|KScreen |kde Version|5.27.2 |unspecified Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- I genuinely cannot tell which KDED module is crashing based on the backtrace. I see a lot of glib and GObject function calls though... Luca, do you think it could be the GTK settings daemon? -- You are receiving this mail because: You are watching all bug changes.
