Bug 415970

Summary:	Ringing a computer crashes KDE Connect Daemon on their side
Product:	[Applications] kdeconnect	Reporter:	The Feren OS Dev <ferenosdev>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cwo.kde
Priority:	NOR
Version First Reported In:	1.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description The Feren OS Dev 2020-01-07 17:30:40 UTC

SUMMARY
If you try to "Ring my phone" a paired computer from another computer it'll instantly crash KDE Connect Daemon on their side.

STEPS TO REPRODUCE
1. Pair up a computer with KDE Connect through another computer
2. Go into the Plasmoid, the device menu for that computer and select "Ring my phone"
3. KDE Connect Daemon instantly crashes on the other computer's end

OBSERVED RESULT
KDE Connect Daemon will crash on the computer being "rang"

EXPECTED RESULT
Either that it'd be impossible to give your other computer an identity crisis by "ringing a phone" at it or it'd have some sort of comedic response similar to pinging a computer.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Feren OS (KDE neon 5.17.4)
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
The computer you ring with thinks the other computer is a phone as per the menu item for ringing that other computer.

Comment 1 cwo 2024-08-03 19:33:51 UTC

Thanks for the bug report. I can no longer reproduce this crash. I assume it was fixed sometime in the last couple of years.

If you can still reproduce this crash, can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

Comment 2 Bug Janitor Service 2024-08-19 03:47:23 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2024-09-03 03:47:26 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.