Summary: | [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5 | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kded | Reporter: | nekonexus |
Component: | general | Assignee: | David Faure <faure> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | 3502075663, davecollier1948, kdelibs-bugs, plasma-bugs, ryuichi.ya220, thegalacticvoid |
Priority: | NOR | Keywords: | drkonqi, needs_verification, usability |
Version: | 5.93.0 | Flags: | nekonexus:
Usability+
|
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
URL: | https://git.harting.dev/ALHP/ALHP.GO | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | DrKonqi Backtrace Info and Kernel Info |
Description
nekonexus
2022-04-17 05:36:47 UTC
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. |