https://bugs.kde.org/show_bug.cgi?id=465596
--- Comment #4 from qlum ---
Created attachment 156357
--> https://bugs.kde.org/attachment.cgi?id=156357&action=edit
Screenshot of desktop and panels at work
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465596
qlum changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=465596
--- Comment #6 from qlum ---
Just a few sidenotes:
The Panels and Desktops Management window shows old desktop backgrounds, but
does seem to update them upon editing.
I have not yet updated my setup at home to the stable version of 5.27 and will
do so
https://bugs.kde.org/show_bug.cgi?id=465596
--- Comment #8 from qlum ---
(In reply to Marco Martin from comment #7)
> did it only did that after the upgrade, or even if you put them back in the
> proper place they keep being moved after every reboot?
Only after the upgrade, subsequent r
https://bugs.kde.org/show_bug.cgi?id=429385
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #1 from qlum ---
I would
: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: qlum...@gmail.com
Target Milestone: ---
SUMMARY
The way edge barriers between screens work right now, are rather
https://bugs.kde.org/show_bug.cgi?id=489136
--- Comment #3 from qlum ---
Created attachment 170947
--> https://bugs.kde.org/attachment.cgi?id=170947&action=edit
Diagonal movement
Okay, so it is intentional behavior, for me personally that means I will not
use this feature, but that&#x
https://bugs.kde.org/show_bug.cgi?id=489136
--- Comment #4 from qlum ---
Small adition to my previous comment, I was using a Edge barrier of 10px when
showcasing the diagonal movement.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489136
--- Comment #6 from qlum ---
(In reply to Nate Graham from comment #5)
> All of this is intentional, yeah; it's designed to make slow movements
> easier to constrain to one screen so you can reach UI elements touching a
> screen edg
Linux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: qlum...@gmail.com
Target Milestone: ---
Created attachment 166707
--> ht
https://bugs.kde.org/show_bug.cgi?id=482339
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #13 from qlum ---
I am
https://bugs.kde.org/show_bug.cgi?id=482339
--- Comment #14 from qlum ---
I suspect that this issue is simply that the task manager does not get updated
whenever it moves to a different screen.
In that case from stand-by it may just have been on no screen at all and still
referencing that after
https://bugs.kde.org/show_bug.cgi?id=422401
--- Comment #12 from qlum ---
(In reply to etoven from comment #10)
> I want to talk about how your F keys goes to 24. Forget about the bug. 😲
in my case I can just rebind the keys in software, so added fn+Fkeys to f13-24.
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=478936
--- Comment #22 from qlum ---
Testing it again on plasma 6.0.1 and qt 6.7 I can confirm that I can bind the
calculator key again.
However, I do need to manually set the binding again, as the old binding will
remain non-functional.
--
You are
https://bugs.kde.org/show_bug.cgi?id=422401
--- Comment #15 from qlum ---
(In reply to Dashon from comment #13)
> I believe the issue that I'm having is related to this one, where I have a
> key on my keyboard that has a picture of a calculator on it. I believe it
> was sendi
https://bugs.kde.org/show_bug.cgi?id=482859
--- Comment #4 from qlum ---
I just want to add that this is indeed fixed for my use with Plasma 6.0.2.
--
You are receiving this mail because:
You are watching all bug changes.
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: qlum...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
Target Milestone
https://bugs.kde.org/show_bug.cgi?id=481927
--- Comment #3 from qlum ---
Great to know it's being worked on.
as for keeping the old behavior as a toggle, wouldn't that be worse from a
maintainability perspective?
Wouldn't adding a simple lock / fold-unfold that simply moves all
https://bugs.kde.org/show_bug.cgi?id=429992
--- Comment #1 from qlum ---
Another issue, to indicate that it may be more widespread: my second and third
monitor (Gigabyte G27Q) disconnect / reconnect when in standby but do stay
connected while turned off, this also causes flickering / config
Status: REPORTED
Severity: normal
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: qlum...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
My center monitor (Asus VG27AQ) has the
https://bugs.kde.org/show_bug.cgi?id=351175
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #15 from qlum ---
I
https://bugs.kde.org/show_bug.cgi?id=351175
qlum changed:
What|Removed |Added
Version Fixed In||org,
||k
https://bugs.kde.org/show_bug.cgi?id=414059
--- Comment #3 from qlum ---
Created attachment 126725
--> https://bugs.kde.org/attachment.cgi?id=126725&action=edit
Distorded image on bootup
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414059
--- Comment #4 from qlum ---
At random intervals I get this type of distortion on one or more of my center 3
screens.
The screen is divided into bands of around 60px high.
Divided equally over the content of all 5 monitors. What should be displayed
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm
Assignee: kscreen-bugs-n...@kde.org
Reporter: qlum...@gmail.com
Target Milestone: ---
Created attachment 123857
--> https://bugs.kde.org/attachment.cgi?id=123857&
https://bugs.kde.org/show_bug.cgi?id=414059
qlum changed:
What|Removed |Added
Version|5.17.2 |5.17.3
--- Comment #2 from qlum ---
Now updated to
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Panel
Assignee: plasma-b...@kde.org
Reporter: qlum...@gmail.com
CC: niccolo.venera...@gmail.com
Target Milestone: 1.0
https://bugs.kde.org/show_bug.cgi?id=478898
--- Comment #1 from qlum ---
I can also reproduce this issue on a different system using intel integrated
graphics.
My main system uses a 7900xt + the igp of my 7800x3d (amd)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422401
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #1 from qlum ---
Can
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_khotkeys
Assignee: plasma-b...@kde.org
Reporter: qlum...@gmail.com
CC: k...@michael-jansen.biz
Target Milestone: ---
When trying to use a previously made
https://bugs.kde.org/show_bug.cgi?id=478866
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=478990
--- Comment #1 from qlum ---
Created attachment 164437
--> https://bugs.kde.org/attachment.cgi?id=164437&action=edit
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
--
You are receiving this mail because:
: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: qlum...@gmail.com
Target Milestone: 1.0
Application
: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: kscreen-bugs-n...@kde.org
Reporter: qlum...@gmail.com
Target Milestone: ---
SUMMARY
Whenever a disabled screen
https://bugs.kde.org/show_bug.cgi?id=478990
--- Comment #2 from qlum ---
I will add that the display that has been disconnected / reconnected does not
have to be the one in portrait itself.
It seems the crash also happens upon connecting a display while having at least
one display in portrait
https://bugs.kde.org/show_bug.cgi?id=477674
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #3 from qlum ---
Created
https://bugs.kde.org/show_bug.cgi?id=477674
--- Comment #4 from qlum ---
Just for reference I am using the following setup:
Distro: Arch Linux
Plasma Version: 5.91.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479071
--- Comment #2 from qlum ---
I can reproduce this bug on one machine but not on a different one.
Both running Arch Linux
Both running qt6.7
Both running plasma 6 beta 2.
Looking at the differences between my systems:
The one that has the issue is a
https://bugs.kde.org/show_bug.cgi?id=478898
--- Comment #3 from qlum ---
Created attachment 164477
--> https://bugs.kde.org/attachment.cgi?id=164477&action=edit
Screenshot of visual corruption:
Forgot to add the screenshot.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=478994
--- Comment #2 from qlum ---
Please note the issue on KDE's side is not the monitor's behavior which is odd
and probably rare.
The update of the layout will not cause huge issues, but panels do get redrawn
which is visible, and it can make r
https://bugs.kde.org/show_bug.cgi?id=478994
--- Comment #5 from qlum ---
Created attachment 164822
--> https://bugs.kde.org/attachment.cgi?id=164822&action=edit
output of drm_info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478994
--- Comment #6 from qlum ---
Created attachment 164823
--> https://bugs.kde.org/attachment.cgi?id=164823&action=edit
KWin log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478994
qlum changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=478990
--- Comment #11 from qlum ---
The Issue I was having seems to at least been fixed in RC1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478898
--- Comment #9 from qlum ---
Seems to be resolved on RC1 on my systems.
--
You are receiving this mail because:
You are watching all bug changes.
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: alexander.loh...@gmx.de
Reporter: qlum...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
Specifically on Wayland
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: qlum...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
https://bugs.kde.org/show_bug.cgi?id=455913
--- Comment #24 from qlum ---
Just for reference, I personally no longer use Nvidia hardware since early this
year but other people seem to be more than capable of handling it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449429
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #6 from qlum ---
Created
https://bugs.kde.org/show_bug.cgi?id=449906
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #8 from qlum ---
Might
https://bugs.kde.org/show_bug.cgi?id=489136
--- Comment #9 from qlum ---
(In reply to Nate Graham from comment #7)
> Ah, if it's just about diagonals, that may be a legit issue if you've got
> your screens configured so that they really are diagonal to each other. Can
> you
https://bugs.kde.org/show_bug.cgi?id=469119
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #6 from qlum ---
Same
https://bugs.kde.org/show_bug.cgi?id=399282
--- Comment #7 from qlum ---
I can no longer reproduce the issue, even forgot I opened it.
I can't exactly pinpoint when it resolved itself, but I am no longer having
this issue.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=429177
qlum changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=427069
qlum changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=430781
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #2 from qlum ---
>F
https://bugs.kde.org/show_bug.cgi?id=435013
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #2 from qlum ---
could
https://bugs.kde.org/show_bug.cgi?id=442684
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--- Comment #2 from qlum ---
Similar
Severity: normal
Priority: NOR
Component: Panel
Assignee: plasma-b...@kde.org
Reporter: qlum...@gmail.com
Target Milestone: 1.0
SUMMARY
Right now, whenever a display is not connected, there is no way in GUI to
manage panels that are on it.
This can be an issue
https://bugs.kde.org/show_bug.cgi?id=447044
--- Comment #2 from qlum ---
(In reply to Nate Graham from comment #1)
> Can you help me understand why you need or want to configure panels that
> aren't visible? By definition, if they aren't visible, you won't be able to
>
https://bugs.kde.org/show_bug.cgi?id=447044
--- Comment #3 from qlum ---
Sidenote, I have kscreen 2 turned off as a service on my home system. The
reason being that 3 of my 4 monitors behave a bit wacky with it enabled, as
posted in: 429992, this does not seem to prevent panels from interacting
https://bugs.kde.org/show_bug.cgi?id=414059
qlum changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Multi-screen support
Assignee: plasma-b...@kde.org
Reporter: qlum...@gmail.com
CC: aleix...@kde.org, notm...@gmail.com
Target Milestone: 1.0
https://bugs.kde.org/show_bug.cgi?id=465596
--- Comment #2 from qlum ---
(In reply to Nate Graham from comment #1)
> When you say, "Use a panel on multiple monitors" you mean that each screen
> has its own panel, right?
>
> This happened after you upgraded but it didn
https://bugs.kde.org/show_bug.cgi?id=429992
qlum changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=399282
--- Comment #2 from qlum ---
Sadly I can still reproduce the issue. Sorry for the late response it happens
on my machine at work and didn't have an opportunity to verify earlier. It does
however seem pretty hard to reproduce at times.
Another
Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: qlum...@gmail.com
Target Milestone: ---
SUMMARY
Random system freeze when capturing area
STEPS TO REPRODUCE
1. Set capture mo
https://bugs.kde.org/show_bug.cgi?id=399282
qlum changed:
What|Removed |Added
CC||qlum...@gmail.com
--
You are receiving this mail
68 matches
Mail list logo
