https://bugs.kde.org/show_bug.cgi?id=500041
--- Comment #11 from David Warner ---
Unfortunately a fresh install of KDE Plasma 6.3.4 (Fedora 42) hasn't improved
this behaviour on my machine - my monitors are all still capped at 30%
brightness when using the software controls (incidentally
https://bugs.kde.org/show_bug.cgi?id=500041
--- Comment #2 from David Warner ---
I should mention tbat my monitors are all Dell S2721QS models, in case it's
relevant. Also, I should emphasise that this is a regression from Plasma 6.2.
> If I then change the monitors OSD brightness to 1
https://bugs.kde.org/show_bug.cgi?id=500041
Bug ID: 500041
Summary: Monitor brightness limited to 30%
Classification: Plasma
Product: plasmashell
Version: 6.3.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #18 from David Warner ---
(In reply to Jakob Petsovits from comment #17)
> (In reply to David Warner from comment #16)
> > This might be an edge case not worth worrying about, but yesterday I had a
> > brief power outage
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #19 from David Warner ---
(In reply to David Warner from comment #18)
> (In reply to Jakob Petsovits from comment #17)
> > (In reply to David Warner from comment #16)
> > > This might be an edge case not worth worrying ab
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #16 from David Warner ---
This might be an edge case not worth worrying about, but yesterday I had a
brief power outage and my monitors were all set to 30% when I turned my PC back
on - I guess the previous state isn't retained in
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #12 from David Warner ---
This is better for me now in Plasma 6.2 on a fresh Fedora 41 install (which I
think shipped with Plasma 6.2.1 - currently 6.2.4). The screen is dimmed when
the lock screen appears after a period of inactivity, but
https://bugs.kde.org/show_bug.cgi?id=479891
David Warner changed:
What|Removed |Added
CC||david.p.war...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=460344
David Warner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=443937
David Warner changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=476566
--- Comment #4 from David Warner ---
Confirmed fixed in Plasma 6.1 - thank you!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476543
David Warner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=488098
David Warner changed:
What|Removed |Added
CC||david.p.war...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #6 from David Warner ---
Sorry, ignore all the above - it just happened on the DisplayPort monitors,
too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #5 from David Warner ---
In case it's helpful: in my 2x DisplayPort, 1x HDMI setup, the issue seems to
be occurring only on the monitor connected by HDMI - the other 2 monitors are
correctly set at 100% brightness after resuming
https://bugs.kde.org/show_bug.cgi?id=482278
--- Comment #3 from David Warner ---
(In reply to Jakob Petsovits from comment #2)
> Hi, could you confirm if this is still an issue with Plasma 6.0.1 or higher?
> The original 6.0.0 release was missing this commit:
> https://invent.kde.o
https://bugs.kde.org/show_bug.cgi?id=482278
David Warner changed:
What|Removed |Added
CC||david.p.war...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482064
--- Comment #14 from David Warner ---
Happy to confirm this is fixed for me in 6.0.1 with the above commit.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482064
David Warner changed:
What|Removed |Added
CC||david.p.war...@gmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=476566
--- Comment #2 from David Warner ---
(In reply to Akseli Lahtinen from comment #1)
> Can confirm this issue, the coordinates are offset. It also seems that the
> Wine application is not scaled at all, text wise.
Thanks for confirming.
Wine h
https://bugs.kde.org/show_bug.cgi?id=476566
David Warner changed:
What|Removed |Added
Platform|Other |Fedora RPMs
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=476566
Bug ID: 476566
Summary: Wine drag & drop coordinates off with Wayland
fractional scaling
Classification: Plasma
Product: kwin
Version: 5.27.9
Platform: Other
O
https://bugs.kde.org/show_bug.cgi?id=433284
David Warner changed:
What|Removed |Added
CC||david.p.war...@gmail.com
--- Comment #16 from
https://bugs.kde.org/show_bug.cgi?id=476543
David Warner changed:
What|Removed |Added
Keywords||wayland
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=476543
Bug ID: 476543
Summary: Wrong display sizes when Wayland fractional scaling
enabled
Classification: Applications
Product: krdc
Version: 23.08.1
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=433205
David Warner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=453534
--- Comment #13 from David Warner ---
I'm not seeing this on a fresh Fedora 38 install with KCalc 23.04.0 (Plasma
5.27.4, KDE Frameworks 5.105.0, Qt 5.15.9, X11), though I'm sure it was still
happening on my previous Fedora 37 install wit
https://bugs.kde.org/show_bug.cgi?id=461032
--- Comment #12 from David Warner ---
@San Does your package manager let you downgrade KWin to 5.26.1? In Fedora I
ran `dnf install kwin-5.26.1-1.fc36.x86_64` and things seemed to work.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=460344
David Warner changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=460344
David Warner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=461032
--- Comment #7 from David Warner ---
(In reply to kevinfocke1 from comment #6)
> (In reply to David Warner from comment #5)
> > Thanks for the quick fix. Will this be in 5.26.3 or is there a chance it
> > will be pushed sooner?
>
>
https://bugs.kde.org/show_bug.cgi?id=388985
--- Comment #8 from David Warner ---
Sadly no, I'm sorry I didnt think to save it.
David
Sent from my T-Mobile 4G LTE Device
Original message From: Alvin Wong
Date: 1/15/18 8:42 AM (GMT-05:00) To: blen...@gmail.com Subject: [
https://bugs.kde.org/show_bug.cgi?id=388985
--- Comment #6 from David Warner ---
Greetings once more Alvin,
I report success! Deleting the AppData and rc files in my AppData\Local then
reloading the 4.0 Beta 1 (Decided to skip the nightly build) worked well!!! 😊
Very Happy,
David W.
Sent
https://bugs.kde.org/show_bug.cgi?id=388985
--- Comment #5 from David Warner ---
No, it did not work and I tried both the exe and the portable zip
Sent from Mail for Windows 10
From: Alvin Wong
Sent: Monday, January 15, 2018 8:21 AM
To: blen...@gmail.com
Subject: [krita] [Bug 388985] Pen
https://bugs.kde.org/show_bug.cgi?id=388985
--- Comment #4 from David Warner ---
BTW also deleting the rc files that reside in AppData as well
Sent from Mail for Windows 10
From: David Warner
Sent: Monday, January 15, 2018 8:17 AM
To: bug-cont...@kde.org
Subject: RE: [krita] [Bug 388985] Pen
https://bugs.kde.org/show_bug.cgi?id=388985
--- Comment #2 from David Warner ---
I did Alvin, I even restarted my SP4 a number of times between settings. I
eventually reinstalled 3.3.3 and all was well again. I am in the process of
uninstalling Krita and deleting my User\AppData for Krita. I
https://bugs.kde.org/show_bug.cgi?id=388985
Bug ID: 388985
Summary: Pen Pressure not detected on Surface Pro 4 in Krita
4.0 Beta
Product: krita
Version: 4.0.0-beta.1
Platform: Other
OS: MS Windows
37 matches
Mail list logo
