kdeconnectd crashed with SIGABRT in QMessageLogger::fatal()

Bug #1912266 reported by Stefan Löffler
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
kdeconnect (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On a fairly regular basis (although seemingly randomly), my Wayland/GnomeShell session hangs for a few seconds, then crashes and puts me back on the login screen. When I log back in, I am greeted with the attached crash report about kdeconnectd.
It seems to me the problem occurs more frequently when attaching/removing an external monitor and/or after waking the laptop from hibernation, but that could also be my subjective (mis)interpretation.

It is quite obvious that any unsaved data will be lost when the desktop session dies. In addition, data can be corrupted if the problem occurs while saving - especially if the computer is rebooted manually while the system is hanging (before reverting to the login screen).

I'm using Ubuntu 20.10, kdeconnect 20.08.2-0ubuntu1

Revision history for this message
Stefan Löffler (st.loeffler) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kdeconnect (Ubuntu):
status: New → Confirmed
Revision history for this message
Togo28 (togo28) wrote :

Upgraded and got the crash

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.