Created attachment 148201 [details] DrKonqi Backtrace Info and Kernel Info SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** A DrKonqi crash dialog appeared claiming that kded5 crashed after my attempts to get my PS4 controller to stay consistently connected when it kept periodically disconnecting from the bluetooth applet at a 95% charge. STEPS TO REPRODUCE 1. Turn on the bluetooth applet if disabled 2. Connect a PS4 controller via bluetooth 3. Have Steam running with Playstation controller support enabled in the settings 4. Attempt to use the controller by holding the PS / "guide" button and moving the right stick around, using "R1" for mouse clicks (use it as though you intended to use the controller as a substitute for mouse) 5. After not too long, switching between open programs via the task manager and such, the controller disconnects itself from bluetooth without notification 6. Attempting this re-connect and perform this task several times prompted a DrKonqi kded5 crash dialog and set the bluetooth applet to disabled mode OBSERVED RESULT PS4 controller unexpectedly disconnects from the applet several times EXPECTED RESULT The PS4 controller should have stayed consistently connected SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION A x86-64-v3 repo is used: https://git.harting.dev/ALHP/ALHP.GO A custom kernel is used, though with the appropriate modules enabled: https://github.com/frogging-family/linux-tkg (I will attach the kernel config file and related customization file for the project) The kernel used is: "Linux 5.17.2-256-tkg-pds-llvm"
Hi on version 21 12 3 selected 4k, when Rendar is selected the system crashes and switches off the kdenlive prog works ok when mp3 selected
@Dave Excuse me, but can you not hi-jack my bug report for something completely unrelated? Make your own report, please.
Hi Sorry about the intrusion I was looking to report a bug found in kdenlive My mistake Regards DC Sent from Mail[1] for Windows *From: * bugzilla_noreply@kde.org[2] *Sent: *01 May 2022 02:29 *To: * davecollier1948@gmail.com[3] *Subject: *[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5 https://bugs.kde.org/show_bug.cgi?id=452691 nekonexus@protonmail.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Platform|unspecified |Archlinux Packages OS|Microsoft Windows |Linux --- Comment #2 from nekonexus@protonmail.ch --- @Dave Excuse me, but can you not hi-jack my bug report for something completely unrelated? Make your own report, please. -- You are receiving this mail because: You are on the CC list for the bug. 1. https://go.microsoft.com/fwlink/?LinkId=550986 2. mailto:bugzilla_noreply@kde.org 3. mailto:davecollier1948@gmail.com
ONCE AGAIN, make your own report; don't arbitrarily change the operating system and source information for something that OBVIOUSLY doesn't apply to Windows.
(In reply to nekonexus from comment #4) > ONCE AGAIN, make your own report; don't arbitrarily change the operating > system and source information for something that OBVIOUSLY doesn't apply to > Windows. I'm sorry. This is my first time using this site, and I have 0 clue how I got to this specific bug and how I was able to edit it in the first place
in bluedevil configure, the "Restore previous status" of "On login" doesn's work. when every time i login, no matter what the previous status was, the bluetooth is open.
You guys REALLY need to stop interfering with this page and file your issues elsewhere. Stop hijacking this report to change the topic to your own issues; that's not how a bug tracker works.
Isn't it because you've set multiple aliases like "crash" and "segfault"? Searching those words with the search bar directs you to this bug report.
> Isn't it because you've set multiple aliases like "crash" and "segfault"? > > Searching those words with the search bar directs you to this bug report. That isn't an excuse.
(In reply to nekonexus from comment #9) > > Isn't it because you've set multiple aliases like "crash" and "segfault"? > > > > Searching those words with the search bar directs you to this bug report. > > That isn't an excuse. It very much is because all of us are trying to do the right thing by searching for existing bug reports instead of starting new threads. You shouldn't berate people for making basic mistakes, especially when said mistakes are a result of this site's unintuitive design.