https://bugs.kde.org/show_bug.cgi?id=475077
--- Comment #44 from Blazer Silving ---
Hey, i'd like to note that the Merge Request at
https://invent.kde.org/plasma/kwin/-/merge_requests/5330 fully resolves this
for me, i've been using it in my personal Kwin build since I found the pa
https://bugs.kde.org/show_bug.cgi?id=482418
--- Comment #6 from Blazer Silving ---
Hello, based on the screenshot this issue may be as quick a fix as setting the
Rows count in System Settings -> Window Management -> Virtual Desktops. This of
course affects the pager where the top-right
https://bugs.kde.org/show_bug.cgi?id=455585
--- Comment #52 from Blazer Silving ---
It does sound like Paul's report is what we're experiencing. There are
seemingly two types of animation lag in Windowheap effects that are being
discussed in this report:
- Session starts, animation
https://bugs.kde.org/show_bug.cgi?id=455585
--- Comment #55 from Blazer Silving ---
(In reply to Nate Graham from comment #53)
> Animations in general being stuck at 60hz is something different — a broader
> issue than just the issue affecting WindowHeap-based effects. That needs its
>
https://bugs.kde.org/show_bug.cgi?id=466451
--- Comment #12 from Blazer Silving ---
Hey, for those still following, I have opened the upstream bug with Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=1919115
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455585
--- Comment #49 from Blazer Silving ---
With Plasma 6.1.4, the Windowheap slowness/stuttering has improved markedly in
X11 (likely due to the new triple buffering) and the effects seem to sync with
the monitor as close as it can.
I still encounter
https://bugs.kde.org/show_bug.cgi?id=466451
--- Comment #8 from Blazer Silving ---
(In reply to Stephen Gallagher from comment #7)
> The same issue is present when using Firefox with client-side decorations
> (which is the default on Fedora).
>
> I have no title bar (to save screen
https://bugs.kde.org/show_bug.cgi?id=466451
--- Comment #9 from Blazer Silving ---
It seems the upstream problem is actually twofold:
- Firefox does not detect tiled state in KDE. This means things like the left
tab spacer will always be visible, you can observe it disappear when maximized
and
https://bugs.kde.org/show_bug.cgi?id=488853
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475077
--- Comment #50 from Blazer Silving ---
I've opened a formal change request to spark discussion and move this along:
https://invent.kde.org/plasma/kwin/-/issues/240
Regression or enhancement request, it's still a problem and the solution
https://bugs.kde.org/show_bug.cgi?id=466451
--- Comment #11 from Blazer Silving ---
Yes, the Firefox top-most resizer issue is definitely upstream. I'm still
gathering information before submitting a report, but I'm not sure Firefox has
the ability to read the window hints that Kwin
https://bugs.kde.org/show_bug.cgi?id=492373
Bug ID: 492373
Summary: Desktop Bar overflows off-screen with large amount of
desktops
Classification: Plasma
Product: kwin
Version: 6.1.0
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=492373
--- Comment #1 from Blazer Silving ---
Created attachment 173096
--> https://bugs.kde.org/attachment.cgi?id=173096&action=edit
16 Desktops in KDE
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492373
--- Comment #2 from Blazer Silving ---
Created attachment 173097
--> https://bugs.kde.org/attachment.cgi?id=173097&action=edit
16 Desktops in MacOS
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492373
Blazer Silving changed:
What|Removed |Added
Attachment #173096|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=492373
Blazer Silving changed:
What|Removed |Added
Attachment #173097|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=492373
--- Comment #5 from Blazer Silving ---
Slight update after digging around a bit: the oversized bar IS scrollable with
a click+drag.
No real break, then!
It could be enhanced with UI arrows/cursor indicators to show the bar is able
to be grabbed, and
https://bugs.kde.org/show_bug.cgi?id=489353
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475077
--- Comment #52 from Blazer Silving ---
Thrilled to help, I only had to file paperwork for this one :) Glad we could
make it in before the release.
This *does* lead to a slight visual disconnect between the spatial hotkeys for
desktop navigation used
https://bugs.kde.org/show_bug.cgi?id=483979
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #2 from Blazer Silving ---
I'm surprised there aren't more reports on this, this is a heavy hitter for
usability. I work and play in virtual machines and VNC sessions very often,
isolated keyboard input is critical. I'm also
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #3 from Blazer Silving ---
Correction to last post, had too many tabs open.
https://invent.kde.org/plasma/kwin/-/merge_requests/23 addresses how Wayland at
the time added support, not X11.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=488828
--- Comment #8 from Blazer Silving ---
Some notes after modifying values and testing with kdesrc-build:
-- Sizing/Padding
Adjusting m_relativeMargin variables in expolayout.h works to help window
scaling. Less margins = larger window previews. The
https://bugs.kde.org/show_bug.cgi?id=488828
--- Comment #10 from Blazer Silving ---
Thanks for the bookkeeping, I've followed that ticket as well. Hate to be a
broken record, but I'm going to continue to strongly assert that a choice of
multiple layouts is the way to go here, and th
https://bugs.kde.org/show_bug.cgi?id=475077
--- Comment #48 from Blazer Silving ---
Quick suggestion, the ticket title "Show non-linear virtual desktop
arrangements again" is a bit misleading for what this thread actually covers,
hence all the duplicate tickets.
"Desktop Bar hi
https://bugs.kde.org/show_bug.cgi?id=488828
Blazer Silving changed:
What|Removed |Added
Summary|New WindowHeap layout has |Revisit multiple WindowHeap
https://bugs.kde.org/show_bug.cgi?id=490914
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #6 from Blazer Silving ---
Hello, are there any progress or ideas? I am also sticking to Plasma 6.0.5
primarily due to this bug.
The issue was not resolved by simply reverting commit
219499707e1f85d318bb23ce305de4f3cb0e0eb3 as speculated
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #8 from Blazer Silving ---
Thanks for the details, this portion of Plasma is all new to me. Kind of
interesting that the first result I read for "xcb record" recommends against
using it: https://stackoverflow.com/a/20825635. Ther
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #12 from Blazer Silving ---
Hello, i've built and tested the latest kdesrc-build pull of kglobalaccel, but
the issue persists.
Same behavior on default config, just a quick Meta/Super tap in a fresh profile
is enough to test. Ver
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #15 from Blazer Silving ---
> For this particular issue you are mentioning, do you know if it is a
> regression from 6.0?
> Maybe the virtual machine viewer is not correctly grabbing Super+Q and
> preventing events from propa
https://bugs.kde.org/show_bug.cgi?id=489113
--- Comment #18 from Blazer Silving ---
Good news, a clean build of kglobalacceld now reflects the change, something
must have been cached.
Multi-key shortcuts are indeed fixed. Using Barrier as a host in the build with
your patch, Meta+Q only
https://bugs.kde.org/show_bug.cgi?id=375943
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=495444
Bug ID: 495444
Summary: [Desktop Bar] Dropped windows "glide" offscreen
Classification: Plasma
Product: kwin
Version: 6.2.2
Platform: Arch Linux
OS: Linux
Status: REPO
https://bugs.kde.org/show_bug.cgi?id=495444
--- Comment #1 from Blazer Silving ---
Created attachment 175283
--> https://bugs.kde.org/attachment.cgi?id=175283&action=edit
Desktop bar behavior in 6.1.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495444
--- Comment #2 from Blazer Silving ---
Created attachment 175284
--> https://bugs.kde.org/attachment.cgi?id=175284&action=edit
Desktop bar behavior in 6.2.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495879
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=493708
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=496646
--- Comment #5 from Blazer Silving ---
https://invent.kde.org/plasma/kwin/-/commit/31c4b8ac555289309341b03bf813b4ac45d2e12d
This later patch defines heapRect to reference thumb.windowHeap, but still runs
it against "oldGlobalRect" and issu
https://bugs.kde.org/show_bug.cgi?id=493843
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=496646
Bug ID: 496646
Summary: [Desktop Grid] Regression in dropped window animations
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=496646
--- Comment #2 from Blazer Silving ---
Created attachment 176090
--> https://bugs.kde.org/attachment.cgi?id=176090&action=edit
Abnormal behavior of the desktop grid
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496646
--- Comment #1 from Blazer Silving ---
Created attachment 176089
--> https://bugs.kde.org/attachment.cgi?id=176089&action=edit
Normal behavior of the desktop grid
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496646
Blazer Silving changed:
What|Removed |Added
CC||n...@kde.org
https://bugs.kde.org/show_bug.cgi?id=493708
--- Comment #5 from Blazer Silving ---
I've tested the posted fix branch but it's not quite there yet. I've given
feedback in the MR:
https://invent.kde.org/plasma/kwin/-/merge_requests/6844#note_1082692
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=493708
--- Comment #3 from Blazer Silving ---
This also happens with a 2x2 Desktop Grid, if you drop the selection of windows
inbetween the Desktop tiles.
However! Individual windows will properly cancel the drop and move back to
their origin if dropped in
https://bugs.kde.org/show_bug.cgi?id=488828
--- Comment #11 from Blazer Silving ---
After spending this fall trying out different Kwin debugging setups and
environments, and taking time up and close with the Overview and Grid: I still
cannot get behind the new layout.
I set up an issue page
https://bugs.kde.org/show_bug.cgi?id=495444
--- Comment #6 from Blazer Silving ---
Confirmed fixed, thanks y'all!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496646
Blazer Silving changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=495444
Blazer Silving changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=485927
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=496646
Blazer Silving changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=496646
Blazer Silving changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=459226
--- Comment #11 from Blazer Silving ---
Created attachment 176269
--> https://bugs.kde.org/attachment.cgi?id=176269&action=edit
Desktop Grid behavior in 11/28 master
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459226
--- Comment #10 from Blazer Silving ---
This is still an issue in latest master (6.3), provided video clip
demonstrating this.
The clip demonstrates normal window drop behavior, and then attempts to perform
this drop action on the entire desktop&#
https://bugs.kde.org/show_bug.cgi?id=478132
--- Comment #4 from Blazer Silving ---
At this time there are several open issues with the Desktop Grid regarding
multiple monitors, we can consolidate a few:
The Animation feedback described here is being seen in BUG 459226, resolving it
may resolve
https://bugs.kde.org/show_bug.cgi?id=455897
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=493208
Blazer Silving changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=455585
--- Comment #59 from Blazer Silving ---
For everyone following this thread, there may be a fix in upstream qt6 found in
BUG 485927.
Thrilled if this is all it takes to fix this issue. So far, Overview+Grid are
butter smooth for me with no
https://bugs.kde.org/show_bug.cgi?id=485927
Blazer Silving changed:
What|Removed |Added
CC||kdebugs@paul.network
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=459771
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=478132
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=486613
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=459226
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=486202
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=486202
--- Comment #1 from Blazer Silving ---
Hey, i'm thinking this may be a duplicate of bug 459226.
Both describe the same issue, groups of windows dropped into a Desktop Grid
tile should not run their arrangement animation.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=486202
Blazer Silving changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=459226
Blazer Silving changed:
What|Removed |Added
CC||titouan-ca...@orange.fr
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=402857
--- Comment #24 from Blazer Silving ---
Is there an effort already in motion to work on this, beyond
https://invent.kde.org/plasma/kwin/-/issues/59?
Let's break it down and try to shake the dust off. From what I gather,
user-configurable tou
https://bugs.kde.org/show_bug.cgi?id=402857
--- Comment #28 from Blazer Silving ---
> These are the gestures and actions available in touchegg and seem to cover
> almost everything that someone could want from this feature.
Thanks for getting this list together. The last discussion thr
https://bugs.kde.org/show_bug.cgi?id=493208
--- Comment #5 from Blazer Silving ---
Thanks for testing! Didn't mean to close the issue without giving you a chance
to respond :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #16 from Blazer Silving ---
> I assume this is upstream with qt. Does anyone know who I have to contact in
> order to upstream this?
A case can be opened at https://bugreports.qt.io/projects/QTBUG/issues,
but..
This is
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #19 from Blazer Silving ---
(In reply to n.parkanyi from comment #17)
> (In reply to Blazer Silving from comment #16)
> > > It looks like these animations are all being driven by QUnifiedTimer
> >
> > I'
https://bugs.kde.org/show_bug.cgi?id=497149
Blazer Silving changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=497149
--- Comment #5 from Blazer Silving ---
Created attachment 176463
--> https://bugs.kde.org/attachment.cgi?id=176463&action=edit
1440p at 200% - Wayland (Correct)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497149
--- Comment #4 from Blazer Silving ---
Created attachment 176462
--> https://bugs.kde.org/attachment.cgi?id=176462&action=edit
1440p at 200% - X11 (Incorrect)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497149
Blazer Silving changed:
What|Removed |Added
Summary|[Desktop Bar] Desktop Bar |[Desktop Bar] Desktop Bar
https://bugs.kde.org/show_bug.cgi?id=497149
--- Comment #3 from Blazer Silving ---
(In reply to David Edmundson from comment #2)
> >2. Turn Global scaling up (200% or so) in the same KCM.
>
> That means it's X11. Can you confirm if on Wayland it works as expected.
>
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #21 from Blazer Silving ---
Kindly, can we get acknowledgement from someone KDE-side here? A knowledgable
dev could know Kwin's role in this timing value, or insight on how this could
be handled upstream in QT
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=488828
Blazer Silving changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=476161
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482418
Blazer Silving changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=482418
--- Comment #14 from Blazer Silving ---
I'm glad bringing back this feature was this simple! It's finished and ready.
Unfortunately, it didn't get picked up for testing in the upcoming 6.3 release,
and as a UI behavior change, it proba
https://bugs.kde.org/show_bug.cgi?id=482418
Blazer Silving changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482418
--- Comment #11 from Blazer Silving ---
Created attachment 176716
--> https://bugs.kde.org/attachment.cgi?id=176716&action=edit
Auto-tile 20 desktops to 5x4 grid
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482418
--- Comment #10 from Blazer Silving ---
Hey, thanks for providing this use case! I've been tinkering with an option to
ignore the pager and auto-tile Desktops in the Grid Effect, and only in the
Grid Effect. It's a very small change, uses
https://bugs.kde.org/show_bug.cgi?id=482418
--- Comment #12 from Blazer Silving ---
I've opened https://invent.kde.org/plasma/kwin/-/merge_requests/6922 to square
this feature off.
Encouraging anyone able and willing to build and test, thanks!
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=493843
--- Comment #4 from Blazer Silving ---
This ticket may be a duplicate of BUG 482418.
I've opened https://invent.kde.org/plasma/kwin/-/merge_requests/6922 to
re-introduce auto-tiling for that issue, it should address this one as well.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=497149
--- Comment #1 from Blazer Silving ---
I took a close look at the Plasma codebase (i.e. many varied searches across
kde-builder's tree), but could not find any instances where a previous desktop
element was corrected and made to follow global
https://bugs.kde.org/show_bug.cgi?id=497149
Bug ID: 497149
Summary: [Desktop Bar] Desktop Bar doesn't follow global
scaling (DPI)
Classification: Plasma
Product: kwin
Version: git master
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=402857
--- Comment #30 from Blazer Silving ---
I recently found an actively-developed Kwin script:
https://github.com/taj-ny/kwin-gestures.
Configuration takes a minute to fully set up, but I can confirm that it
overrides the default gestures in 6.2.5
https://bugs.kde.org/show_bug.cgi?id=375943
--- Comment #38 from Blazer Silving ---
(In reply to Dragan from comment #34)
> (In reply to Nate Graham from comment #33)
> > Looks like this is working as expected for me with Firefox 134 (only one
> > window in the Task Manager gets
https://bugs.kde.org/show_bug.cgi?id=501606
--- Comment #2 from Blazer Silving ---
> In editing mode, there are many hints that we are in editing path mode:
The icon at the beginning of the path (instead of >), the cursor, the '/'
visible, the I suspect this is mostly a tran
https://bugs.kde.org/show_bug.cgi?id=501649
Blazer Silving changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=501649
Blazer Silving changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=501606
--- Comment #3 from Blazer Silving ---
It's also worth noting the "sunken" state of the bar in all cases now. The bar
was formerly in the same plane as the header while in normal mode, and would
"sink" into edit mode (looked
https://bugs.kde.org/show_bug.cgi?id=475106
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=499989
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=501607
Bug ID: 501607
Summary: New URL/Location Bar breadcrumb navigation regressions
Classification: Frameworks and Libraries
Product: frameworks-kio
Version: 6.12.0
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=501606
Bug ID: 501606
Summary: New URL/Location Bar background does not indicate edit
state (too light/dark)
Classification: Frameworks and Libraries
Product: frameworks-kio
Version: 6.12.0
1 - 100 of 107 matches
Mail list logo
