https://bugs.kde.org/show_bug.cgi?id=494579
Bug ID: 494579
Summary: 6.2.0 causes Shift+Alt (but not Alt+Shift) to trigger
Meta modifier-only shortcut
Classification: Plasma
Product: plasmashell
Version: 6.2.0
Platform:
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #26 from RedBearAK ---
(In reply to Nate Graham from comment #25)
> Looks like it ended up backported after all, in
> https://invent.kde.org/plasma/kwin/-/commit/
> 6943fab2c1c46eb15e0018ae3419c0d43eb3c8d7! So that explains it.
O
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #24 from RedBearAK ---
(In reply to Nate Graham from comment #22)
> Fixed by David Edmundson with
> https://invent.kde.org/plasma/kwin/-/commit/
> 6943fab2c1c46eb15e0018ae3419c0d43eb3c8d7 in Plasma 6.2.0.
Hey, I'm a little
https://bugs.kde.org/show_bug.cgi?id=457913
RedBearAK changed:
What|Removed |Added
Version|6.0.4 |6.1.3
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=457913
RedBearAK changed:
What|Removed |Added
CC||redb...@redbearnet.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #23 from RedBearAK ---
(In reply to Nate Graham from comment #22)
> Fixed by David Edmundson with
> https://invent.kde.org/plasma/kwin/-/commit/
> 6943fab2c1c46eb15e0018ae3419c0d43eb3c8d7 in Plasma 6.2.0.
Thanks for taking th
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #19 from RedBearAK ---
(In reply to David Redondo from comment #18)
> I cant reprdouce this on master. I suspect its fixed by
> https://invent.kde.org/frameworks/kguiaddons/-/commit/
> 0420025cc0d706856076bb71143c04f857871ac2 and/o
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #17 from RedBearAK ---
Something has changed after a Tumbleweed update, even though none of the
Plasma/Qt version info in "About" has changed.
It used to be Plasmashell using about 17% CPU, with kwin_wayland using abou
https://bugs.kde.org/show_bug.cgi?id=454413
--- Comment #3 from RedBearAK ---
(In reply to David Edmundson from comment #2)
> I can confirm this is how it behaves, I also don't see it as a bad thing,
> the user has caused an explicit action to switch from switch between all
> windo
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #16 from RedBearAK ---
Bad news. Or a clue?
I was able to replicate this issue for the first time on a Fedora 40 system.
Fully updated as of today, Plasma 6.1.2, Frameworks 6.3.0, Qt 6.7.2, kernel
6.6.39 (LTS).
Interestingly, it is a
https://bugs.kde.org/show_bug.cgi?id=454413
RedBearAK changed:
What|Removed |Added
Version|unspecified |6.1.2
--- Comment #1 from RedBearAK ---
This is
https://bugs.kde.org/show_bug.cgi?id=490325
--- Comment #1 from RedBearAK ---
The thing about the "Delete" button was wrong, it still shows up after typing
something, even in the restricted-width dialog while using a large font.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=490325
Bug ID: 490325
Summary: krunner dialog stuck at fixed width after Frameworks
6.4.0 update, regardless of font size
Classification: Plasma
Product: krunner
Version: 6.1.2
Platf
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #15 from RedBearAK ---
(In reply to postix from comment #14)
> I cannot reproduce it on openSUSE TW with KDE Plasma 6.1.2 Wayland with the
> Gnome Text Editor 46.3
I did a `zypper dup` to be sure I'm up to date. Still able t
https://bugs.kde.org/show_bug.cgi?id=430082
RedBearAK changed:
What|Removed |Added
CC||redb...@redbearnet.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #13 from RedBearAK ---
It should come as no surprise that after Tumbleweed updated to Plasma 6.1.2, I
can still replicate the symptoms of this. Elevated CPU usage upon de-selecting
any amount of selected text, then the Plasmashell core dump
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #12 from RedBearAK ---
I did a system update on Tumbleweed and rebooted, then happened to log into the
X11 session and noticed I couldn't replicate the high CPU usage bug or the
Plasmashell core dump.
But I did have a remarkably diff
https://bugs.kde.org/show_bug.cgi?id=489644
RedBearAK changed:
What|Removed |Added
Summary|Selecting, and then |Un-selecting text in GNOME
|un
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #11 from RedBearAK ---
I found another GTK text editor app that causes both the high CPU usage upon
selecting and then un-selecting some text, and also the Plasmashell core dump
after quitting the app.
Apostrophe, a Markdown editor. The
https://bugs.kde.org/show_bug.cgi?id=489644
RedBearAK changed:
What|Removed |Added
Summary|Typing, selecting, and |Selecting, and then
|deleting
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #10 from RedBearAK ---
I should have realized this since it's about the clipboard being empty, but
there's no necessity of deleting any text to start the cycle of high CPU usage.
That was sort of a red herring in my initial descr
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #9 from RedBearAK ---
Another minor nuance: If I make a text selection to temporarily stop the high
CPU usage, and only then quit the app, the RPM version does not seem to trigger
the Plasmashell core dump.
I've only done it a few
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #8 from RedBearAK ---
Was able to get the core dump dialog to show up again after running the RPM
version from the terminal and doing the usual stuff, then quitting the app.
It's apparently only the desktop entry that was overwritten
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #7 from RedBearAK ---
(Had a "mid-air collision" with your comment when I tried submit this a minute
ago.)
Slightly nuanced addition. I'm having a hard time going back to the RPM version
to check this because for some rea
https://bugs.kde.org/show_bug.cgi?id=489644
--- Comment #5 from RedBearAK ---
(In reply to Nate Graham from comment #4)
> A flame graph shows that it's in clipboard code, first
> KSystemClipboard::changed, then SystemClipboard::checkClipData, then
> SystemClipboard::receivedEmptyC
https://bugs.kde.org/show_bug.cgi?id=489644
RedBearAK changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=489644
Bug ID: 489644
Summary: Plasmashell and kwin_wayland high CPU, plasmashell
core dump, triggered with GNOME Text Editor
Classification: Plasma
Product: plasmashell
Version: 6.1.1
https://bugs.kde.org/show_bug.cgi?id=489536
Bug ID: 489536
Summary: Window placement setting not noticed by "Highlight
Changed Settings" option
Classification: Applications
Product: systemsettings
Version: 6.1.1
Platfor
https://bugs.kde.org/show_bug.cgi?id=487922
--- Comment #4 from RedBearAK ---
And just before I posted that appears to have been marked as a duplicate of
this bug report:
https://bugs.kde.org/show_bug.cgi?id=484992
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487922
RedBearAK changed:
What|Removed |Added
CC||redb...@redbearnet.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=489382
RedBearAK changed:
What|Removed |Added
CC||redb...@redbearnet.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=482350
--- Comment #2 from RedBearAK ---
(In reply to Nate Graham from comment #1)
> This is an issue in `im-chooser` itself; please report it to the developers.
This is my best guess as to where the appropriate place would be. But after
searching the web
https://bugs.kde.org/show_bug.cgi?id=482350
Bug ID: 482350
Summary: im-chooser libimchooseui-WARNING DBus Error No such
method 'logout'
Classification: I don't know
Product: kde
Version: unspecified
Platform: Fedora RPM
https://bugs.kde.org/show_bug.cgi?id=435170
RedBearAK changed:
What|Removed |Added
Version|5.21.3 |6.0.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=412655
RedBearAK changed:
What|Removed |Added
Resolution|UNMAINTAINED|---
Version|5.16.5
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #13 from RedBearAK ---
(In reply to Natalie Clarius from comment #12)
> Re. ยง2: I was not talking about activation and the tab-grave transition
> issue, but raising and the singling out a window issue. If I understood you
> corre
https://bugs.kde.org/show_bug.cgi?id=454413
Bug ID: 454413
Summary: Transition from Alt+Tab to Alt+Grave without releasing
Alt unexpectedly switches windows
Product: kwin
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #11 from RedBearAK ---
(In reply to Natalie Clarius from comment #10)
> The transition from Tab to Grave already activating the window before
> releasing Alt is an issue on its own though, so I suggest you file a
> separate b
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #9 from RedBearAK ---
(In reply to Natalie Clarius from comment #8)
> > But as soon as you press Grave while still holding Alt after doing Alt+Tab,
> > the Grave key press triggers the app switch event
>
> What'
https://bugs.kde.org/show_bug.cgi?id=412655
RedBearAK changed:
What|Removed |Added
CC||redb...@redbearnet.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #7 from RedBearAK ---
(In reply to Natalie Clarius from comment #6)
> It should be noted that the KWin script acts on any window activation event,
> i.e. not only when task switching with Alt+Tab, but also with the task
> manag
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #5 from RedBearAK ---
The Kwin script from Natalie is working great after compensating for some
interference with panel items.
Windows of a single application are kept together and brought forward when
clicking on any window of the app
https://bugs.kde.org/show_bug.cgi?id=433566
--- Comment #6 from RedBearAK ---
(In reply to Alexander Lohnau from comment #5)
> I think this is a good idea.
>
> How would you like the results to be presented? Like when you are searching
> for "Apperance" do you want to
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #3 from RedBearAK ---
There is another desktop environment that has the ability to have both "Switch
windows" and "Switch applications" active at the same time on different
keyboard shortcuts.
It is possible that som
https://bugs.kde.org/show_bug.cgi?id=435738
--- Comment #5 from RedBearAK ---
(In reply to Konrad Materka from comment #4)
> Both IconName and IconPixmap are empty.
>
> Maybe the problem is that Albert set's the icon in a weird way?
> https://github.com/albertlauncher/albert
https://bugs.kde.org/show_bug.cgi?id=435738
--- Comment #2 from RedBearAK ---
(In reply to Konrad Materka from comment #1)
> Can you provide a link to the application?
The Albert GitHub thread that led to me asking for assistance on narrowing down
the cause of this issue:
https://github.
https://bugs.kde.org/show_bug.cgi?id=435738
RedBearAK changed:
What|Removed |Added
Summary|Tray icon fails to display |Tray icon for Albert
|in Albert
https://bugs.kde.org/show_bug.cgi?id=435738
Bug ID: 435738
Summary: Tray icon fails to display in Albert
Product: frameworks-plasma
Version: 5.81.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severi
https://bugs.kde.org/show_bug.cgi?id=435170
--- Comment #2 from RedBearAK ---
(In reply to Nate Graham from comment #1)
> Coming from the Mac world, I also find this style of switching to be
> intuitive and pleasant, and would appreciate seeing it as an option. It
> mostly only makes s
https://bugs.kde.org/show_bug.cgi?id=435170
Bug ID: 435170
Summary: REQUEST: Application-centric task switching like
macOS/GNOME
Product: kwin
Version: 5.21.3
Platform: Other
OS: Linux
Status: RE
https://bugs.kde.org/show_bug.cgi?id=435043
--- Comment #6 from RedBearAK ---
(In reply to Nate Graham from comment #5)
> That issue has already been fixed by giving the button text in the next
> version of Plasma (5.22).
Oh, that's good news. I am eagerly awaiting 5.22.x for other
https://bugs.kde.org/show_bug.cgi?id=435043
--- Comment #4 from RedBearAK ---
(In reply to Nate Graham from comment #3)
> Yup that's correct.
Thanks.
I guess I'll make a separate (short) report on Discover to get some attention
on the no-label cancel button that disappears w
https://bugs.kde.org/show_bug.cgi?id=435043
--- Comment #2 from RedBearAK ---
(In reply to Nate Graham from comment #1)
> Interesting point of view. I can see what you mean.
Thank you for saying so.
Usually what people say right off the bat is, "Geez, you could have made that a
lot
53 matches
Mail list logo
