https://bugs.kde.org/show_bug.cgi?id=485534
Parker Reed changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=485534
Parker Reed changed:
What|Removed |Added
CC||parker.l.r...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #23 from Parker Reed ---
I was mistaken in my first assumption of it being powermanagementengine
Turns out what handles this for the powerdevil applet is
components/batterycontrol/batteriesnamesmonitor_p.cpp
Working through some debug
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #22 from Parker Reed ---
Created attachment 173818
--> https://bugs.kde.org/attachment.cgi?id=173818&action=edit
powerdevil
If I kill and restart org_kde_powerdevil it shows up correctly
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #21 from Parker Reed ---
Created attachment 173817
--> https://bugs.kde.org/attachment.cgi?id=173817&action=edit
plasmawindowed
If I run org.kde.plasma.battery with plasmawindowed within the same session it
shows the correct &
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #20 from Parker Reed ---
I recompiled upower to return nothing on creating the DisplayDevice node. Had
no affect on Plasma. Still reporting "Battery 2"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #19 from Parker Reed ---
Is DisplayDevice not monitor in UPower's world? Now I'm not so sure if that's
what's tripping the counter.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #18 from Parker Reed ---
Same on the Ally
[parker@rogally ~]$ upower -i /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated: Wed 18 Sep 2024 02:48:00 AM EDT (27 seconds ago)
has history
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #17 from Parker Reed ---
I figured it out finally.
DisplayDevice has battery stats but no vendor info.
This increments unnamedBattery by 1. The real battery comes along and trips it
over to 2.
[parker@parker-framework powerdevil]$ upower
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #16 from Parker Reed ---
Created attachment 173815
--> https://bugs.kde.org/attachment.cgi?id=173815&action=edit
upower
I'm hitting this condition without having more than one battery
https://invent.kde.org/plasma/plas
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #15 from Parker Reed ---
Even stranger, I just booted the Ally on 6.10.10 and it's showing BAT0, but the
applet still says battery 2.
I could have sworn this was reading BAT1 earlier. There's a second fake PS
controller battery,
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #14 from Parker Reed ---
Okay, so just realized I do have more AMD hardware.
Steam Deck is also BAT1 but 5.27 but power widget correctly labels it as
"Battery".
Ally, FW 16, T495 all on 6.1/6.2 are BAT1 and have the "Batter
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #13 from Parker Reed ---
I'm seeing a bunch of mentions of this being handled with quirks in the kernel
https://github.com/torvalds/linux/commit/c986a7024916c92a775fc8d853fba3cae1d5fde4
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #12 from Parker Reed ---
I guess this doesn't rule out a kernel bug or configuration issue. The only
commonality between my devices is using Arch Linux.
Recently switched to Linux Zen on the framework and its BAT1 as well.
I'll
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #10 from Parker Reed ---
The behavior is seemingly entirely dependent on whether your
/sys/class/power_supply folder has a BAT0 or BAT1.
None of my devices have any capabilities for multiple batteries, but they are
all labeled as BAT1
https://bugs.kde.org/show_bug.cgi?id=492480
--- Comment #8 from Parker Reed ---
(In reply to Nate Graham from comment #7)
> So you're only seeing this on Framework hardware? Or elsewhere too?
I am seeing this on all of my AMD hardware currently, so Framework 16 and a
T495.
Using up
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-U
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 ma
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.
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.
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
Stat
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
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
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: REPOR
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.
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
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.
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
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
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
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/e5f251720c470f047549b59acff16ef701e
https://bugs.kde.org/show_bug.cgi?id=475574
Parker Reed changed:
What|Removed |Added
CC||parker.l.r...@gmail.com
--- Comment #1 from
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.
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.
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.
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.
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.
Afte
https://bugs.kde.org/show_bug.cgi?id=470761
Parker Reed changed:
What|Removed |Added
Latest Commit||e7bf1f0d299c4f7c6529438059d
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:
https://bugs.kde.org/show_bug.cgi?id=470531
Parker Reed changed:
What|Removed |Added
Latest Commit||2ceec081587284d7d5eae5d5039
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.
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: And
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.
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.
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
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
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
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:
Yo
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
https://bugs.kde.org/show_bug.cgi?id=428921
Parker Reed changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
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
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
O
https://bugs.kde.org/show_bug.cgi?id=384066
Parker Reed changed:
What|Removed |Added
CC||parker.l.r...@gmail.com
--- Comment #13 from
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
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.
https://bugs.kde.org/show_bug.cgi?id=364662
Parker Reed changed:
What|Removed |Added
CC||parker.l.r...@gmail.com
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=399430
Parker Reed changed:
What|Removed |Added
CC||parker.l.r...@gmail.com
--- Comment #3 from
57 matches
Mail list logo
