Bug 456111 - KDE Connect segmentation fault (v21.12.3)
Summary: KDE Connect segmentation fault (v21.12.3)
Status: RESOLVED DUPLICATE of bug 449276
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-29 04:05 UTC by aplatypus
Modified: 2022-06-29 12:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Back trace from Crash Reporting Assistant (3.01 KB, text/plain)
2022-06-29 04:05 UTC, aplatypus 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description aplatypus 2022-06-29 04:05:17 UTC 
Created attachment 150242 [details]
Back trace from Crash Reporting Assistant

SUMMARY

Application: kdeconnectd (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-40-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
Start/restart KDE Connect or after reboot or login.

The crash can be reproduced every time.


STEPS TO REPRODUCE
1. Start KDE connect
2. 
3. 

OBSERVED RESULT

* Crash reporter window -- Which incidentally doesn't work.  
* I imagine you are not getting many reports of this because something seems to be missing in the crash reporting assistant.
EXPECTED RESULT


SOFTWARE/OS VERSIONS

Linux/Ubuntu:  22.04 / Light DM / Cinnamon desktop

 $ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04 LTS
Release:	22.04
Codename:	jammy


ADDITIONAL INFORMATION

* This happened last night and then it just keeps happening
* Sometimes not right away today it has been very consistient
* I have a new phone so may be there are too many devices now?
   - This morning was connecting 5 mobiles, tablets and a laptop
Comment 1 Nicolas Fella 2022-06-29 12:35:50 UTC 

*** This bug has been marked as a duplicate of bug 449276 ***