|
Bugzilla – Full Text Bug Listing |
| Summary: | kdeconnect crashes after upgrading to Leap:15.6 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Dave Plater <davejplater> |
| Component: | KDE Applications | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | davejplater, lbeltrame |
| Version: | Leap 15.6 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
KDE crash trace back
Screenshot of kde when kdeconnect tries to connect |
||
gdb --args kdeconnect-cli -l Starting program: /usr/bin/kdeconnect-cli -l [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffee9ff6c0 (LWP 2440)] - Galaxy S6 edge: 4680ab46_f179_45e0_973e_505504e42637 (paired) - Hisense E7 Pro: 67fda1b4_f3df_4776_9b44_d6777649b924 (paired) - ArbuthnotL: _dcdbea85_4ff0_4c53_916b_a42713fa0dc2_ (paired) 3 devices found [Thread 0x7fffee9ff6c0 (LWP 2440) exited] [Inferior 1 (process 2437) exited normally] I'm writing this from a freshly updated tumbleweed and kdeconnect works 100% I share /home partition with Tumbleweed. It also worked with the previous snapshot: NAME="openSUSE Tumbleweed" # VERSION="20240429" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240429" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240429:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240429" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" Created attachment 875780 [details]
Screenshot of kde when kdeconnect tries to connect
I've checked the firewall
This might be a long shot... but can you disable all plugins for your phone (in the KDEConnect settings on your machine, not on the phone) and see whether it keeps on crashing? If it doesn't, re-enable them one by one until you can replicate the crash. (In reply to Luca Beltrame from comment #4) > This might be a long shot... but can you disable all plugins for your phone > (in the KDEConnect settings on your machine, not on the phone) and see > whether it keeps on crashing? > > If it doesn't, re-enable them one by one until you can replicate the crash. The culprit is system volume, needs to be enabled on pc and phone and it crashes every time. Everything else that I use such as file sharing, clipboard and remote input. I was most probably going to disable system volume because it stops the multimedia volume control from working on Leap:15.5. |
Created attachment 875777 [details] KDE crash trace back I already had kdeconnect running when my system was Leap:15.5 but after doing a zypper dup --allow-vendor change with only Main repository and dvd enabled, whenever my phone with kdeconnect installed tries to connect kdeconnect on my pc apparently crashes. I've installed updates and removed any packages that have lp155 then restored the unrestricted packages I had before it's still the same. I've tried gdb on kdeconnectd but when the unhappy face appears on the taskbar about eight times it simply says process exited normally. I'll attach the kde crash trace but I can't fathom anything from it. Surprisingly nobody else has filed a bug. to get the crash I open kdeconnect on my phone (same version as before) and it crashes continually.