[krita] [Bug 466203] New: [Android] Crash upon launch
https://bugs.kde.org/show_bug.cgi?id=466203 Bug ID: 466203 Summary: [Android] Crash upon launch Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 156575 --> https://bugs.kde.org/attachment.cgi?id=156575&action=edit logcat SUMMARY Nightly commit 3aeb18b37e2a619448972ae4d0e481200349c51f Crashes on Android 13 shortly after splash appears STEPS TO REPRODUCE 1. Install nightly 2. Launch OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466203] [Android] Crash upon launch
https://bugs.kde.org/show_bug.cgi?id=466203 --- Comment #1 from Parker Reed --- Created attachment 156576 --> https://bugs.kde.org/attachment.cgi?id=156576&action=edit Tombstone Tombstone from the crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466203] [Android] Crash upon launch
https://bugs.kde.org/show_bug.cgi?id=466203 --- Comment #2 from Parker Reed --- Created attachment 156577 --> https://bugs.kde.org/attachment.cgi?id=156577&action=edit Extra Tombstone PB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488813] New: Shake cursor inoperable with animation speed set to instant
https://bugs.kde.org/show_bug.cgi?id=488813 Bug ID: 488813 Summary: Shake cursor inoperable with animation speed set to instant Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY With animation speed set to instant, shake cursor does not work. STEPS TO REPRODUCE 1. Set animations to instant 2. Enable Shake Cursor under accessibility 3. Try to shake cursor OBSERVED RESULT Cursor stays the same size EXPECTED RESULT Cursor to inflate when shaken SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488813] Shake cursor inoperable with animation speed set to instant
https://bugs.kde.org/show_bug.cgi?id=488813 --- Comment #1 from Parker Reed --- Subsequently the cursor size changing is entirely dependent on animation speed. If you have it set really low, it takes a long time to inflate and deflate. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 428921] New: error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’
https://bugs.kde.org/show_bug.cgi?id=428921 Bug ID: 428921 Summary: error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’ Product: frameworks-kwayland Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: mgraess...@kde.org Reporter: parker.l.r...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 133191 --> https://bugs.kde.org/attachment.cgi?id=133191&action=edit Build log Fails to build on latest master Arch Linux gcc 10.2.0-3 STEPS TO REPRODUCE 1. Clone kwayland-server from git 2. Build OBSERVED RESULT Errors out at a missing member EXPECTED RESULT Build successful Log attached -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 428921] error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’
https://bugs.kde.org/show_bug.cgi?id=428921 --- Comment #2 from Parker Reed --- plasma-framework-git r15640.8b7b4f74c-1 https://invent.kde.org/frameworks/plasma-framework/-/commit/8b7b4f74c6bdfd51fe9247fec28e71c377004045 Only does it if I leave the default cmake BUILD_TESTS enabled. Disabling tests lets it compile successfully. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 428921] error: ‘class KWayland::Client::DataOffer’ has no member named ‘accept’
https://bugs.kde.org/show_bug.cgi?id=428921 Parker Reed changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Parker Reed --- This appears to be working now. Built fine on the same install with the default options. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #13 from Parker Reed --- Since this didn't make it due to X11 freeze, will this be available for X11 in the hotfix after release? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #15 from Parker Reed --- Running into this on plasma-framework 5.61 With the default applications URL handler set to "in an application based on the contents of the URL" it takes 1:16 to open http://google.com with kde-open5 Attached log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 --- Comment #16 from Parker Reed --- Created attachment 122495 --> https://bugs.kde.org/attachment.cgi?id=122495&action=edit kde-open5 strace with timestamps -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 --- Comment #17 from Parker Reed --- Created attachment 122496 --> https://bugs.kde.org/attachment.cgi?id=122496&action=edit Malformed kioslaverc Figured out the culprit. My ~/.config/kioslaverc had some old malformed proxy entries. Nuking the rc and running without properly opens URL based on mimetype instantly. Uploading the bad kioslaverc as an example -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475574] [Wayland] Unable to bind keys with keycodes above 255
https://bugs.kde.org/show_bug.cgi?id=475574 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #1 from Parker Reed --- Seeing same thing here with Chromecast remote. Half of the buttons are way above 255 and won't map in KWin. Event: time 1706641635.753398, -- SYN_REPORT Event: time 1706641641.873435, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0089 Event: time 1706641641.873435, type 1 (EV_KEY), code 377 (KEY_TV), value 1 Event: time 1706641641.873435, -- SYN_REPORT Event: time 1706641642.013353, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0089 Event: time 1706641642.013353, type 1 (EV_KEY), code 377 (KEY_TV), value 0 Event: time 1706641642.013353, -- SYN_REPORT Event: time 1706641643.873390, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0078 Event: time 1706641643.873390, type 1 (EV_KEY), code 589 (?), value 1 Event: time 1706641643.873390, -- SYN_REPORT Event: time 1706641643.973367, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0078 Event: time 1706641643.973367, type 1 (EV_KEY), code 589 (?), value 0 Event: time 1706641643.973367, -- SYN_REPORT Event: time 1706641644.453419, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0077 Event: time 1706641644.453419, type 1 (EV_KEY), code 588 (?), value 1 Event: time 1706641644.453419, -- SYN_REPORT Event: time 1706641644.533424, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0077 Event: time 1706641644.533424, type 1 (EV_KEY), code 588 (?), value 0 Event: time 1706641644.533424, -- SYN_REPORT Event: time 1706641645.313474, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041 Event: time 1706641645.313474, type 1 (EV_KEY), code 353 (KEY_SELECT), value 1 Event: time 1706641645.313474, -- SYN_REPORT Event: time 1706641645.453442, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041 Event: time 1706641645.453442, type 1 (EV_KEY), code 353 (KEY_SELECT), value 0 Event: time 1706641645.453442, -- SYN_REPORT -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475574] [Wayland] Unable to bind keys with keycodes above 255
https://bugs.kde.org/show_bug.cgi?id=475574 --- Comment #4 from Parker Reed --- These keys are defined in evdev and I can use them perfectly remapping them to other keys so this shouldn't be an issue. https://github.com/philipl/evdevremapkeys/commit/e5f251720c470f047549b59acff16ef701e28120 devices: - input_name: 'Chromecast Remote' output_name: remap-kbd remappings: KEY_SELECT: - KEY_ENTER 588: - KEY_PHONE KEY_SCREENLOCK: - KEY_POWER KEY_TV: - KEY_LEFTALT - KEY_F4 589: - KEY_MEDIA KEY_BACK: - KEY_BACKSPACE KEY_HOMEPAGE: - KEY_LEFTMETA -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] New: [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 Bug ID: 470531 Summary: [Android] SDLAudioManager crash Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- SUMMARY Latest nightly crashing on Android 13 STEPS TO REPRODUCE 1. Install update 2. Application crash upon launch OBSERVED RESULT Applications crashes EXPECTED RESULT Application no crashes SOFTWARE/OS VERSIONS Android 13 Samsung Tab S8+ ADDITIONAL INFORMATION 06-01 12:54:03.216 9738 9738 E org.krita.next: - class 'Lorg/libsdl/app/SDLAudioManager;' cl=0x12c77468 - 06-01 12:54:03.216 9738 9738 E org.krita.next: objectSize=228 (224 from super) 06-01 12:54:03.216 9738 9738 E org.krita.next: access=0x.0001 06-01 12:54:03.216 9738 9738 E org.krita.next: super='java.lang.Class' (cl=0x0) 06-01 12:54:03.216 9738 9738 E org.krita.next: vtable (0 entries, 11 in super): 06-01 12:54:03.216 9738 9738 E org.krita.next: direct methods (4 entries): 06-01 12:54:03.216 9738 9738 E org.krita.next: 0: void org.libsdl.app.SDLAudioManager.() 06-01 12:54:03.216 9738 9738 E org.krita.next: 1: void org.libsdl.app.SDLAudioManager.addAudioDevice(boolean, int) 06-01 12:54:03.216 9738 9738 E org.krita.next: 2: int org.libsdl.app.SDLAudioManager.nativeSetupJNI() 06-01 12:54:03.216 9738 9738 E org.krita.next: 3: void org.libsdl.app.SDLAudioManager.removeAudioDevice(boolean, int) 06-01 12:54:03.216 9738 9738 E org.krita.next: static fields (1 entries): 06-01 12:54:03.216 9738 9738 E org.krita.next: 0: org.libsdl.app.SDLAudioManager$1 org.libsdl.app.SDLAudioManager.mAudioDeviceCallback 06-01 12:54:03.216 9738 9738 E org.krita.next: Failed to register native method org.libsdl.app.SDLAudioManager.nativePermissionResult(IZ)V in base.apk 06-01 12:54:03.216 9738 9738 E SDL : Failed to register methods of org/libsdl/app/SDLAudioManager -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 --- Comment #1 from Parker Reed --- Likely related to the commit adding audio for animations bfc5402d8798cf37c5941633fbfdad3a960dfb57 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 Parker Reed changed: What|Removed |Added Latest Commit||2ceec081587284d7d5eae5d5039 ||4084a111a21ff -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] New: [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 Bug ID: 470761 Summary: [Android] Crash upon opening canvas Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 159525 --> https://bugs.kde.org/attachment.cgi?id=159525&action=edit WindowManager lines from logcat SUMMARY Application crashes any time the canvas is brought up (new file or opening existing) STEPS TO REPRODUCE 1. Load Krita Nightly 2. New file 3. Create OBSERVED RESULT Application crashes upon creating canvas EXPECTED RESULT Canvas to be created SOFTWARE/OS VERSIONS Samsung Tab S8+ Android 13 ADDITIONAL INFORMATION Log attached -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 Parker Reed changed: What|Removed |Added Latest Commit||e7bf1f0d299c4f7c6529438059d ||14e7a99907066 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #2 from Parker Reed --- (In reply to Halla Rempt from comment #1) > Sharaf, the android maintainer, is having exams, so this'll take some time. > The attached log doesn't show anything happening inside Krita, though. After taking another look I was able to get better logcat output and found the tombstone that was created. Attaching files -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #3 from Parker Reed --- Created attachment 159545 --> https://bugs.kde.org/attachment.cgi?id=159545&action=edit logcat of application dump -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #4 from Parker Reed --- Created attachment 159546 --> https://bugs.kde.org/attachment.cgi?id=159546&action=edit tombstone -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #5 from Parker Reed --- Created attachment 159547 --> https://bugs.kde.org/attachment.cgi?id=159547&action=edit tombstone pb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470761] [Android] Crash upon opening canvas
https://bugs.kde.org/show_bug.cgi?id=470761 --- Comment #7 from Parker Reed --- Look like this was fixed as of the past handful of commits! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451591] New: [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 Bug ID: 451591 Summary: [kwin/display configuration] Multiple monitors with same name cause unintentional behavior Product: kwin Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 147533 --> https://bugs.kde.org/attachment.cgi?id=147533&action=edit Screenshot of fixed result 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 *** When using more than one display with the same EDID name and multiple different rotations, display configuration will apply your changes but instantly think a change was made so there are TWO apply steps. Due to a hardware issue, sometimes my displays reconnect and the portrait rotation from the right monitor is applied to the left making the left upside down. I have to go in each time and reapply the rotation, apply twice, and then close out. Confirmed on two different AMD GPU systems with the same monitor layout (One HDMI and two Displayport) My fix was to create a specific EDID for each of the portrait monitors with their own name. Image attached showing the result of the fix. STEPS TO REPRODUCE 1. Have three monitors 2. Arrange in one landscape, one portrait, and one reverse portrait 3. Rotation applied incorrectly to one of the portrait montiors OBSERVED RESULT On display reconnect/resume, the wrong rotation is applied to one of the portrait monitors due to the naming of the display being the same between all. EXPECTED RESULT Displays to be treated separately (possibly by serial/unique identifier based on connection name) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3+kde+r134-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451591] [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 --- Comment #1 from Parker Reed --- Forgot to mention session type X11. I think the connector based layout is working but there's possibly a bug with two of the same name in portrait rotation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451591] [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 --- Comment #2 from Parker Reed --- Thanks to a wonderful contributor over on Reddit, finally realized what exposed this issue. My custom EDID setup was already in place when this started. The DisplayPort dock that I have will not drive to monitors at the full refresh rate. So I already had a custom EDID with a single mode single refresh rate set for both of those. Guess which two those were, both portrait. I used a basic EDID generator for the mode and refresh rate which doesn't set a serial number. On top of that I used the same file for both of them in the kernel command line, so to the system they were essentially the same monitor with an nulled out serial. My "solution" of creating to EDID with different names worked because Plasma then have something to differentiate them by even with a blank serial. Wayland with the same EDID works as it already names them as "unknown " programmatically. For the X11 issue at hand, I get that it was my EDID with the same nulled serial causing the issue. I know those get used a lot so probably not the first to run into it. Will be interesting to see if there's anything that can be done there. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486127] New: Unable to drag scrollbar with mouse
https://bugs.kde.org/show_bug.cgi?id=486127 Bug ID: 486127 Summary: Unable to drag scrollbar with mouse Classification: Applications Product: NeoChat Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: parker.l.r...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Scrollbar handle pops to the left when scrolling, seemingly so you can drag it. As soon as you mouse over it, it collapses to the right making it impossible to drag. STEPS TO REPRODUCE 1. Go to any chat list 2. Try dragging the scrollbar OBSERVED RESULT Handle avoids the mouse making it impossible to drag EXPECTED RESULT Being able to drag the scrollbar handle SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 484200] New: Segfault when closing child color picker dialog with no parents
https://bugs.kde.org/show_bug.cgi?id=484200 Bug ID: 484200 Summary: Segfault when closing child color picker dialog with no parents Classification: Applications Product: konsole Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- Created attachment 167584 --> https://bugs.kde.org/attachment.cgi?id=167584&action=edit backtrace SUMMARY Editing any of the current profile's colors, closing the parent windows, and then closing the color picker causes a crash STEPS TO REPRODUCE 1. Edit Current Profile 2. Appearance 3. Edit 4. Click a color 5. Close Edit Color Scheme and Edit Profile via the titlebar (Window buttons are properly blocked) 6. Close the child Color Picker dialog OBSERVED RESULT Konsole crashes EXPECTED RESULT Color Picker closing (or the Edit Color Scheme/Edit Profile titlebar exit buttons being blocked if the Color Picker is open) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Attached backtrace -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 484200] Segfault when closing child color picker dialog with no parents
https://bugs.kde.org/show_bug.cgi?id=484200 --- Comment #2 from Parker Reed --- The steps as I posted them should replicate it. When you go into the edit color scheme dialog and click on any of the colors like foreground or background and leave that resulting color picker dialog open and close the schemes and profile, proceeding to close the color picker will crash the entire application. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] New: Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 Bug ID: 484492 Summary: Plasma Wayland fails to initialize Display Stream Compression Classification: Plasma Product: kwin Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: parker.l.r...@gmail.com Target Milestone: --- SUMMARY Hardware: Steam Deck/ROG Ally Dock : Dell WD-19S Monitors: 3 Lenovo Q27q-10 1440p 75 Hz With all three monitors connected (MST and Display Stream Compression) Plasma X11 can output to all three at their native 1440p 75 Hz. When running Plasma Wayland, it's either * 2 1440 75 Hz and the third monitor never initializes video (Does however show up to KScreen) * 1 1440 75 Hz and 2 1080 60 Hz (As if Display Stream Compression wasn't even working to begin with) I have confirmed on Gnome Wayland Mutter that all three monitors do work at their native resolution for Wayland. STEPS TO REPRODUCE 1. Plug in monitors 2. Go to Display Settings 3. Try to configure all three at native reosolution OBSERVED RESULT Acts like DSC isn't available and either 2 work or 3 work at reduced resolution. EXPECTED RESULT All three to work at native resolution (As they do in Gnome) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 24.0.2 Qt Version: 6.6.2 ADDITIONAL INFORMATION Dmesg from ROG Ally https://gist.github.com/parkerlreed/10da3f1ff55340c5b1f317948ee8f7ac Journalctl (kernel + plasma) from Steam Deck https://gist.github.com/parkerlreed/0b153848d2513d0ad7d8d8696aeffe2f amdgpu thread https://gitlab.freedesktop.org/drm/amd/-/issues/3278 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 --- Comment #1 from Parker Reed --- Additional note: Inoperability with Wayland was present on 5.27 as well going back quite a ways. So this isn't new to Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 --- Comment #2 from Parker Reed --- Just tried enabling 2 1440 75 and 1 1080 60 and got this on kernel messages [ 717.144654] amdgpu :09:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:264 [ 717.351967] [drm] Send DSC enable to synaptics Waiting for the monitor and it's just slow enough to be past the timeout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484492] Plasma Wayland fails to initialize Display Stream Compression
https://bugs.kde.org/show_bug.cgi?id=484492 --- Comment #4 from Parker Reed --- Oh my. Thank you! Is there an existing bug triage for this I can follow? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 451591] [kwin/display configuration] Multiple monitors with same name cause unintentional behavior
https://bugs.kde.org/show_bug.cgi?id=451591 --- Comment #7 from Parker Reed --- I have been on 5.26 with the same setup without any modified EDID and it appears to be working as expected. I believe I changed the bottom option in display settings to remember it per monitor setup if that helps. I was on 5.23 shortly before this (Steam Deck) and I was experiencing the same rotation issue on the left hand monitor. After Steam Deck Main branch updated to 5.26, smooth sailing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 Parker Reed changed: What|Removed |Added CC||parker.l.r...@gmail.com --- Comment #3 from Parker Reed --- Found a workaround: open any KDE file dialog (I used Ctrl O in Chrome) and sort the entries there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #1 from Parker Reed --- Seemingly all the Framework laptops have their battery labeled as BAT1 which is where I noticed this (Framework 16) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #3 from Parker Reed --- Checked with a few friends and it looks like even with BAT1 they are only seeing the "Battery" label So this might be a bug that was introduced in the testing Plasma updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] New: Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 Bug ID: 492480 Summary: Battery monitor labels only battery as Battery 2 Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: parker.l.r...@gmail.com CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: 1.0 Created attachment 173188 --> https://bugs.kde.org/attachment.cgi?id=173188&action=edit Screenshot SUMMARY Tray applet shows single battery at /sys/class/power_supply/BAT1 as "Battery 2" STEPS TO REPRODUCE 1. Have a single battery available to the system labeled as BAT1 OBSERVED RESULT Label shows "Battery 2" EXPECTED RESULT Only show "Battery" if BAT1 is the only one available. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.8.0 Kernel Version: 6.10.6-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #2 from Parker Reed --- So this may be a recent kernel change to avoid using BAT0. All of my machines on 6.10 are BAT1 and show "Battery 2" in the applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492480] Battery monitor labels only battery as Battery 2
https://bugs.kde.org/show_bug.cgi?id=492480 --- Comment #5 from Parker Reed --- I only show one battery but it is labeled as BAT1, hence getting the "Battery 2" label ACAD BAT1 ucsi-source-psy-USBC000:001 ucsi-source-psy-USBC000:002 ucsi-source-psy-USBC000:003 ucsi-source-psy-USBC000:004 All of my AMD machines show as BAT1 -- You are receiving this mail because: You are watching all bug changes.
