[konsole] [Bug 477330] New: New F10 behaviour collides with htop quit button
https://bugs.kde.org/show_bug.cgi?id=477330 Bug ID: 477330 Summary: New F10 behaviour collides with htop quit button Classification: Applications Product: konsole Version: 24.01.75 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- SUMMARY The new F10 behaviour to focus the toolbar clashes with the quit button in the popular terminal process monitor, htop. When attempting to quit via F10, nothing happens, and the main menu "toolbar" is focused instead. This program has used F10 as its quit button for as long as I can remember, and is still widely used today. While I do like this new behaviour, wouldn't it be a good idea to add a workaround for this application, or something more universal for all TUI applications that might use F10? Or maybe move the main menu focus to CTRL+F10, and the present windows effect to Meta+F10? SOFTWARE/OS VERSIONS Linux: 6.6.1 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Konsole version: 24.01.75 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 477161] New: Cannot change month when using "Basic month grid"
https://bugs.kde.org/show_bug.cgi?id=477161 Bug ID: 477161 Summary: Cannot change month when using "Basic month grid" Classification: Applications Product: Merkuro Version: 23.08.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: td21rz...@mozmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 163252 --> https://bugs.kde.org/attachment.cgi?id=163252=edit Merkuro Calendar with the two month view settings SUMMARY When using "Basic month grid" in the "Month view settings", I cannot change months back or forth. Only when "Swipeable month grid" is selected can I change the currently visible month. STEPS TO REPRODUCE 1. Set Merkuro Calendar to "Basic month grid" in the settings 2. Close the settings 3. Try to change months with the arrow buttons OBSERVED RESULT The month name in the top left changes, however the actual calendar does not. EXPECTED RESULT To see the desired month. SOFTWARE/OS VERSIONS Linux: 6.6.1 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Also observed in Plasma 5.27.9 and with Frameworks 5.112, as well as Merkuro 24.01.75 Not sure how to generate useful information for this bug.. Would highly appreciate any advice in this regard =) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477024] Cannot click applications in the Application Dashboard's alphabetical list
https://bugs.kde.org/show_bug.cgi?id=477024 --- Comment #2 from Aurora Robb Kristiansen --- Also happens in the X11 session -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477024] Cannot click applications in the Application Dashboard's alphabetical list
https://bugs.kde.org/show_bug.cgi?id=477024 --- Comment #1 from Aurora Robb Kristiansen --- Created attachment 163172 --> https://bugs.kde.org/attachment.cgi?id=163172=edit Video showing what happens in the Application Dashboard -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477024] New: Cannot click applications in the Application Dashboard's alphabetical list
https://bugs.kde.org/show_bug.cgi?id=477024 Bug ID: 477024 Summary: Cannot click applications in the Application Dashboard's alphabetical list Classification: Plasma Product: kdeplasma-addons Version: 5.27.80 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- SUMMARY When using the Application Dashboard menu, as my application starter, I cannot click any applications that appear in the alphabetical list. Hovering over them and clicking them acts as if I clicked an empty space on the dashboard, and closes it. When switching to any of the categories instead, it works as expected. STEPS TO REPRODUCE 1. Set Application Dashboard as your application launcher. 2. Try to click on any application in the alphabetical list. OBSERVED RESULT The application does not start and the Application Dashboard closes. EXPECTED RESULT The application clicked on opens. SOFTWARE/OS VERSIONS Linux: 6.6.1 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Does not affect other menus, such as Application Launcher. Does not affect Plasma 5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476889] Konsole claims the desktop doesn't support transparency
https://bugs.kde.org/show_bug.cgi?id=476889 Aurora Robb Kristiansen changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476889] Konsole claims the desktop doesn't support transparency
https://bugs.kde.org/show_bug.cgi?id=476889 Aurora Robb Kristiansen changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #2 from Aurora Robb Kristiansen --- Wait, sorry, no.. Reopening this, I genuinely thought I had logged back into the Wayland session but something felt off, and sure enough I was still in the X11 session; I must have chosen Wayland from one dropdown in SDDM, but signed in via SDDM appearing on one of my three other connected monitors and head-mounted display. (Unrelated, but it's because of something weird that happened to SDDM after installing Plasma 6 Alpha, it's trying to display SDDM on my VR headset, which overlaps its output on my main monitor, so there's two partially overlapping SDDMs on the main monitor...) Sorry for the spam, I must have been really confused. It is indeed a Wayland issue in my case here. It works on Plasma 6 X11, not Plasma 6 Wayland. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476889] Konsole claims the desktop doesn't support transparency
https://bugs.kde.org/show_bug.cgi?id=476889 Aurora Robb Kristiansen changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Aurora Robb Kristiansen --- Switching to X11, opening Konsole (and confirming transparency works there, then back to Wayland, solved this issue.. Odd! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476889] New: Konsole claims the desktop doesn't support transparency
https://bugs.kde.org/show_bug.cgi?id=476889 Bug ID: 476889 Summary: Konsole claims the desktop doesn't support transparency Classification: Applications Product: konsole Version: 24.01.75 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- Created attachment 163084 --> https://bugs.kde.org/attachment.cgi?id=163084=edit Konsole's terminal output when browsing its spawned windows. SUMMARY In Konsole, when using a colour scheme with transparency enabled, the transparency effect does not work, and the settings menu claims: "This color scheme uses a transparent background which does not appear to be supported on your desktop" This message is seen repeated several times when switching between dialogs spawned by Konsole (settings window, profile editing window, etc.) kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 Will test again on X11 after submitting this. STEPS TO REPRODUCE 1. Begin a Plasma 6 Wayland session 2. Enable transparency in Konsole 3. Apply the theme OBSERVED RESULT The terminal background is opaque. EXPECTED RESULT A transparent background in the terminal emulator. SOFTWARE/OS VERSIONS Linux: 6.6.1 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION This happens on both of my machines, one with an AMD RX 6700 XT, and the other with Vega 8 integrated graphics. Both also use an AMD Ryzen 7 7700X and Ryzen 5 5600H respectively. I don't know if it's relevant, but my current Mesa version is 23.2.1 The Plasma 6 packages are binaries provided by Arch Linux. The issue persists with a new, clean profile, and a new konsolerc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #51 from Aurora Robb Kristiansen --- Didn't have time to check X11, but I just updated on my laptop and rebooted, can still observe on 5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 473618] Merkuro Calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=473618 Aurora Robb Kristiansen changed: What|Removed |Added Version|unspecified |23.08.0 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 473618] Merkuro Calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=473618 --- Comment #2 from Aurora Robb Kristiansen --- Just updated to the official 24.08 release in the Arch Linux repository, and it still segfaults when launching it, in both Wayland and X11, Norwegian or English locale doesn't matter. Merkuro Contacts and Mail works. When trying to start Merkuro Calendar from a terminal, this is the output: merkuro-calendar qrc:/BasicMonthListView.qml:22:5: Required property startDate was not initialized qrc:/MainDrawerToggleButton.qml:25: TypeError: Cannot read property 'collapsed' of undefined qrc:/MainDrawerToggleButton.qml:14: TypeError: Cannot read property 'collapsed' of undefined qrc:/MainDrawerToggleButton.qml:11: TypeError: Cannot read property 'mainDrawer' of undefined 30 -- exe=/usr/bin/merkuro-calendar 17 -- platform=wayland 25 -- appname=merkuro-calendar 17 -- apppath=/usr/bin 10 -- signal=11 9 -- pid=5205 19 -- appversion=23.08.0 29 -- programname=Merkuro Calendar 31 -- bugaddress=sub...@bugs.kde.org KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = merkuro-calendar path = /usr/bin pid = 5205 KCrash: Arguments: /usr/bin/merkuro-calendar KCrash: Attempting to start /usr/lib/drkonqi kf5idletime_wayland: This plugin does not support polling idle time [1]+ Stopped merkuro-calendar -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 473618] Merkuro Calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=473618 --- Comment #1 from Aurora Robb Kristiansen --- Created attachment 161122 --> https://bugs.kde.org/attachment.cgi?id=161122=edit Another backtrace that seems to have more information. Uploading this backtrace just in case it's more informative than the first one, I generated this one manually using GDB. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473618] New: Merkuro Calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=473618
Bug ID: 473618
Summary: Merkuro Calendar crashes on startup
Classification: I don't know
Product: kde
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: td21rz...@mozmail.com
Target Milestone: ---
Application: merkuro-calendar (23.07.80)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.11-zen2-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Using the new Merkuro Calendar rebranding, the application crashes every time I
launch the application.
Downgrading to Kalendar 23.04 makes it work again.
Merkuro Calendar was downloaded from the Arch Linux KDE-Unstable repo.
The crash can be reproduced every time.
-- Backtrace:
Application: Merkuro Calendar (merkuro-calendar), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fbb5922f76d in
QQuickItemPrivate::removeItemChangeListener(QQuickItemChangeListener*,
QFlags) (this=0xf89e2ef07c6b7709,
listener=0x55a5ba3ced68, types=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:3928
#7 0x7fbb5694676c in
QQuickScrollBarAttachedPrivate::setFlickable(QQuickFlickable*)
(this=this@entry=0x55a5ba3ced10, item=item@entry=0x0) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickscrollbar.cpp:766
#8 0x7fbb56946a13 in QQuickScrollBarAttached::~QQuickScrollBarAttached()
(this=0x55a5ba3cecf0, this=) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickscrollbar.cpp:1017
#9 0x7fbb56946a3e in QQuickScrollBarAttached::~QQuickScrollBarAttached()
(this=0x55a5ba3cecf0, this=) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickscrollbar.cpp:1018
#10 0x7fbb570c73bd in QObjectPrivate::deleteChildren()
(this=this@entry=0x55a5ba39c8f0) at kernel/qobject.cpp:2137
#11 0x7fbb570c7b39 in QObject::~QObject() (this=,
this=) at kernel/qobject.cpp:1115
#12 0x7fbb1c1721a3 in QQuickScrollView::~QQuickScrollView()
(this=0x55a5ba3cd5f0, this=) at
../../../include/QtQuickTemplates2/5.15.10/QtQuickTemplates2/private/../../../../../../qtquickcontrols2/src/quicktemplates2/qquickscrollview_p.h:58
#13 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55a5ba3cd5f0, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#14 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55a5ba3cd5f0, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#15 0x7fbb570c73bd in QObjectPrivate::deleteChildren()
(this=this@entry=0x55a5ba34dc60) at kernel/qobject.cpp:2137
#16 0x7fbb570c7b39 in QObject::~QObject() (this=,
this=) at kernel/qobject.cpp:1115
#17 0x7fbb593b86a0 in QQuickImplicitSizeItem::~QQuickImplicitSizeItem()
(this=0x55a5ba34dba0, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickimplicitsizeitem_p.h:60
#18 QQuickLoader::~QQuickLoader() (this=0x55a5ba34dba0, this=)
at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickloader.cpp:317
#19 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55a5ba34dba0, this=) at
../../include/QtQml/../../../qtdeclarative/src/qml/qml/qqmlprivate.h:144
#20 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55a5ba34dba0, this=) at
../../include/QtQml/../../../qtdeclarative/src/qml/qml/qqmlprivate.h:144
#21 0x7fbb570c73bd in QObjectPrivate::deleteChildren()
(this=this@entry=0x55a5ba322610) at kernel/qobject.cpp:2137
#22 0x7fbb570c7b39 in QObject::~QObject() (this=,
this=) at kernel/qobject.cpp:1115
#23 0x7fbb1c17432b in QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55a5ba31ee80, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#24 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55a5ba31ee80,
this=) at /usr/include/qt/QtQml/qqmlprivate.h:144
#25 0x7fbb570c3f9e in QObject::event(QEvent*) (this=0x55a5ba31ee80,
e=0x55a5ba4401e0) at kernel/qobject.cpp:1334
#26 0x7fbb57d7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55a5ba31ee80, e=0x55a5ba4401e0) at
kernel/qapplication.cpp:3640
#27 0x7fbb5709c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55a5ba31ee80, event=0x55a5ba4401e0) at
kernel/qcoreapplication.cpp:1064
#28 0x7fbb570a165b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55a5b9acfe50) at
kernel/qcoreapplication.cpp:1821
#29 0x7fbb570e76d8 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55a5b9aed060) at kernel/qeventdispatcher_glib.cpp:277
#30 0x7fbb54d0fa31 in g_main_dispatch (context=0x7fbb34000ee0) at
../glib/glib/gmain.c:3460
#31
[plasmashell] [Bug 470533] Feature request: Click & drag on panel to move maximised window that touches it
https://bugs.kde.org/show_bug.cgi?id=470533 Aurora Robb Kristiansen changed: What|Removed |Added CC||td21rz...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470533] New: Feature request: Click & drag on panel to move maximised window that touches it
https://bugs.kde.org/show_bug.cgi?id=470533 Bug ID: 470533 Summary: Feature request: Click & drag on panel to move maximised window that touches it Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: td21rz...@mozmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Summary: I would like to be able to left-click and drag on empty spaces in a panel, to move a maximised window that might be touching it. This is similar to how you can simultaneously un-maximise and move a window in the Unity desktop. See the following video for an example: https://i.imgur.com/OLw8Xll.mp4 How it can be implemented: Perhaps a panel could check if a maximised window is touching it, and if it is the active window, clicking and dragging anywhere on that panels' empty space will un-maximise and move the window. This feature should be off by default, but can appear as a toggle next to the "Floating Panel" toggle, when editing a panel using "Edit Mode". Why Plasma benefits from this feature: When a window is maximised and the user wants to move it, it is common to just left-click and hold the titlebar, then move the cursor to move it somewhere. Using KDE Plasma, many people prefer to use a slim top panel, paired with an auto-hiding panel somewhere that contains application shortcuts and icons for open applications. This isn't the case if one has configured Plasma to automatically hide titlebars when a window is maximised, to make the most out of the vertical screen real estate. It then requires clicking the "Restore" button using the window controls, or dragging another "grab-able" part of a window. If one chooses to keep titlebars on windows with a "Unity-like" top-panel regardless, it still requires more precise clicking. So with that in mind, this feature will help muscle memory a lot for anyone using aforementioned configuration, as well as being a quick alternative to moving windows with Meta+Left Click & Drag. While it might be easy to just suggest "Well, if you want GNOME or Unity functionality, you might as well use those", but there are many KDE Plasma users of whom myself included, simply prefer the KDE ecosystem, a Qt desktop experience, both and/or more reasons to not switch away from KDE Plasma. Thanks for reading! SOFTWARE/OS VERSIONS Linux: 6.3.4 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Notes: I believe this might have been a Latte dock feature at some point, but it doesn't work with the current version of Latte built from source and I believe it can benefit more users if it's implemented in the main Plasma panels. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Remember visibility status of Annotations toolbar in Rectangular Region mode across application launches
https://bugs.kde.org/show_bug.cgi?id=468788 --- Comment #8 from Aurora Robb Kristiansen --- That would be ideal, and is what this bug report was originally about, so I still believe at least a command line option to hide it for power users makes a lot of sense. I hate to sound demanding, and on a FOSS project no less, but still. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Remember visibility status of Annotations toolbar in Rectangular Region mode across application launches
https://bugs.kde.org/show_bug.cgi?id=468788 --- Comment #6 from Aurora Robb Kristiansen --- Makes sense, Nate. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Option to disable the new Spectacle toolbar (annotation tools)
https://bugs.kde.org/show_bug.cgi?id=468788 --- Comment #4 from Aurora Robb Kristiansen --- If I do that, the toolbar still appears on the next Spectacle run, with annotation tools visible as well. The button also doesn't remove the bar itself, which is somewhat annoying. I tried disabling the annotation tools, then taking a picture to test this. The first time I ran the rectangle region shortcut with CTRL+SHIFT+3, then I ran the Spectacle GUI itself through the application launcher shortcut. Both times I turned off annotation tools before taking the rectangle screenshot, and it still appears on new Spectacle launches afterwards. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] Option to disable the new Spectacle toolbar (annotation tools)
https://bugs.kde.org/show_bug.cgi?id=468788 --- Comment #2 from Aurora Robb Kristiansen --- That would probably solve it for most of us, since my shortcut just runs "spectacle -(arguments)" -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468788] New: Option to disable the new Spectacle toolbar (annotation tools)
https://bugs.kde.org/show_bug.cgi?id=468788 Bug ID: 468788 Summary: Option to disable the new Spectacle toolbar (annotation tools) Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: td21rz...@mozmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When I use Spectacle, I wish to use it with as little fluff as absolutely possible. I have one shortcut set to rectangle capture mode, that then copies my rectangle to the clipboard, and that's it. Though definitely useful for many, I personally don't have any need for editing features and would much rather prefer they don't pop up. I will add they're a nice feature to have by default, though, so I'm not proposing they be disabled by default. SOFTWARE/OS VERSIONS Linux: 6.2.12 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467662] New: Option to close Emoji Selector after copying an emoji
https://bugs.kde.org/show_bug.cgi?id=467662 Bug ID: 467662 Summary: Option to close Emoji Selector after copying an emoji Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: 1.0 SUMMARY An option to close the Emoji Selector after picking a single emoji would be very helpful. ADDITIONAL INFORMATION Could also make it so that holding CTRL (or other user definable button) does not close the Emoji Selector, even if such an option is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #21 from Aurora Robb Kristiansen --- I found a fix.. I feel very silly now. My klipperrc had this line in it: Version=5.26.90 I changed that to read Version=5.27.0, and now the issue is gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #18 from Aurora Robb Kristiansen --- > (In reply to Fushan Wen from comment #16) > This looks like your system is mixing old and new libraries. Ok, finally had time to try this in Neon (both X11 and Wayland session) and as expected based on your comment, the problem is on my end. I'll need to figure out why both my Arch computers are having this issue. Nevertheless, I appreciate that you lended me your time. I hope it's ok that I leave the status of the bug up to you, as I'm not sure how you'd rather close it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #17 from Aurora Robb Kristiansen --- I haven't gotten time to try a fresh Plasma live environment yet, but while using 5.26.90 I noticed that the same bug happens on my laptop which also runs Arch. Still happens on 5.27 there too. (In reply to Fushan Wen from comment #16) > This looks like your system is mixing old and new libraries. That's super odd, I'm trying to figure out how I might go about fixing that because I've checked and all my libraries are up to date (Plasma, Frameworks, Qt.) Furthermore I only have official repositories enabled. I know this isn't an advice forum, but would you happen to have any idea what I can try to prevent it from doing that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 Aurora Robb Kristiansen changed: What|Removed |Added Attachment #156162|0 |1 is obsolete|| --- Comment #14 from Aurora Robb Kristiansen --- Created attachment 156262 --> https://bugs.kde.org/attachment.cgi?id=156262=edit More comprehensive backtrace for plasmashell (In reply to Fushan Wen from comment #12) > Are you sure you are using plasma-workspace from Arch testing repo? Just double-checked, yes I am. (In reply to David Redondo from comment #13) > Can you provide a backtrace with symbols for libQT5Core? Thanks! Still new to generating backtraces, now I've learned about another thing to look out for. Uploaded a new backtrace with as many missing symbols as I could. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used
https://bugs.kde.org/show_bug.cgi?id=465010 Aurora Robb Kristiansen changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #11 from Aurora Robb Kristiansen --- Created attachment 156247 --> https://bugs.kde.org/attachment.cgi?id=156247=edit plasmashell terminal output I'm planning to reproduce this in a clean Plasma live environment sometime this week, whenever I can catch a breather, but I did try to see if the crash correlates with copying things, and it really does seem like that's what's going on. Shortly after I make a Spectacle screenshot (rectangle, copy to clipboard) this bug occurs. I grabbed the terminal output and attached it, hopefully it has something helpful in it. (The "kpipewire_logging" lines came from hovering my cursor over open applications on my task manager.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #9 from Aurora Robb Kristiansen --- Still getting this bug in 5.27 (downloaded from Arch Linux's testing repo), is there anything else I can do to pinpoint the issue better? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used
https://bugs.kde.org/show_bug.cgi?id=465010 --- Comment #7 from Aurora Robb Kristiansen --- Cannot reproduce in Plasma 5.27 (now works as expected), can anyone else confirm that this is fixed now? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #3 from Aurora Robb Kristiansen --- Scratch that, it's doing it again but I can still interact with my panel so it hadn't fully crashed yet (it just did while I was writing this). High CPU temperature, and saw about 11% CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 --- Comment #2 from Aurora Robb Kristiansen --- Addendum: It could be that I perceived plasmashell as not crashed because I could see the panel, but upon further inspection it looks like plasmashell crashes, THEN my CPU temperature rises while usage exceeds 25% (checked via htop.) This leaves a panel on my screen that I can't interact with, which I perceived as "still running, but my CPU is thinking really hard about something." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 Aurora Robb Kristiansen changed: What|Removed |Added CC||td21rz...@mozmail.com --- Comment #1 from Aurora Robb Kristiansen --- Created attachment 156162 --> https://bugs.kde.org/attachment.cgi?id=156162=edit Backtrace for plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] New: Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 Bug ID: 465603 Summary: Plasmashell stresses CPU then crashes Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: 1.0 SUMMARY During normal usage (playing a game, writing documents, etc.) my Ryzen 7 7700X temperature spikes to its maximum for a while until the "plasmashell" process eventually crashes. Subsequent starts of plasmashell, either when it respawns on its own or using "kstart5 plasmashell" if it doesn't, makes it exhibit the same behaviour eventually. CPU usage remains at approximately 25% when plasmashell causes the CPU to work a sweat. When plasmashell crashes, CPU temperature returns to normal. This has only happened with the package "plasma-desktop 5.26.90-2" from the KDE-Unstable repository on Arch Linux. Unable to test with X11 at the moment, and would appreciate if someone with similar hardware would be able to do so. STEPS TO REPRODUCE 1. Install plasma-desktop 5.26.90-2 on Arch Linux 2. Keep using the computer like you normally would OBSERVED RESULT The plasmashell process causes the CPU to work really hard (but not with high usage!) and eventually crashes. EXPECTED RESULT plasmashell does my bidding without causing high CPU temperatures or crashing SOFTWARE/OS VERSIONS Linux: 6.1.9 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Upload backtrace after posting this. In the backtrace, I start plasmashell via gdb and play a game until it crashes, in which I save the log and quit gdb. Have tried running minimal amounts of applications and waiting, then seen the crash happen regardless. Not sure what sort of config files would help here, so please let me know and I'll upload them ASAP. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433059] "Active/Inactive Titlebar" colors are visible and editable but confusingly unused when Header colors are present
https://bugs.kde.org/show_bug.cgi?id=433059 Aurora Robb Kristiansen changed: What|Removed |Added CC||td21rz...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used
https://bugs.kde.org/show_bug.cgi?id=465010 --- Comment #3 from Aurora Robb Kristiansen --- Created attachment 155916 --> https://bugs.kde.org/attachment.cgi?id=155916=edit My spectaclerc -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used
https://bugs.kde.org/show_bug.cgi?id=465010 --- Comment #2 from Aurora Robb Kristiansen --- Created attachment 155915 --> https://bugs.kde.org/attachment.cgi?id=155915=edit Spectacle config and error message about clipboard not containing image -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465010] Auto copy to clipboard does not work if rectangle is used
https://bugs.kde.org/show_bug.cgi?id=465010 Aurora Robb Kristiansen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||td21rz...@mozmail.com --- Comment #1 from Aurora Robb Kristiansen --- Can confirm I've been having this problem on Plasma Wayland 5.27 Beta (5.26.90). When I use Spectacle, I use it as a rectangle capture tool and copy directly to clipboard, because I always paste images where I want them immedaitely which is usually to instant messaging apps. I never save to file, so this is rather inconvenient. Attaching my spectaclerc after this comment and a screenshot. My config is also visible in that screenshot. I've configured Spectacle to not take a screenshot automatically, not save file to folder, to copy image to clipboard and accept on click-and-release. I tried: 1) Executing "spectacle -rbnci" in a terminal then taking a screenshot 2) Capturing a rectangular region via the shortcut as defined in Plasma Settings 3) Opening Spectacle's GUI and taking a new rectangular screenshot through that None of these methods copies the image to the clipboard like I've told it to do. Can confirm that all other capture methods DO copy to clipboard successfully. Plasma Wayland 5.26.90 Frameworks 5.102.0 Qt 5.15.8 Linux 6.1.9 AMDGPU driver (Mesa 22.3.4) if that matters. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461498] Disabled Middle Click Pasting makes text selection in some GTK apps impossible on Wayland
https://bugs.kde.org/show_bug.cgi?id=461498 Aurora Robb Kristiansen changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||td21rz...@mozmail.com Ever confirmed|0 |1 --- Comment #5 from Aurora Robb Kristiansen --- Has been happening to me in all GTK apps ever since Plasma 5.25.90 but I was never really sure why. Turned middle-click paste back on, lo and behold, now I can mark text in GTK text entry fields again. Tested with Pinta and DeaDBeeF on Plasma 5.26.3. This does not affect Firefox, however I'm not quite sure if Firefox is GTK or Qt, or either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460733] New: Hardware cursor colour is wrong
https://bugs.kde.org/show_bug.cgi?id=460733 Bug ID: 460733 Summary: Hardware cursor colour is wrong Classification: Plasma Product: kwin Version: 5.26.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- SUMMARY When using the default hardware cursor rendering, the cursor's colour is wrong. Almost as if the contrast is too low. It happens with any cursor theme, in both X11 and Wayland sessions. I have had this bug ever since I clean installed Arch Linux about half a month ago, but was never really certain what it is that caused it or if it was even a KDE bug. I experienced it with both the Nvidia proprietary graphics driver (GTX 1060) and now the AMDGPU open source driver (RX 6700 XT), but can't for the life of me reproduce this bug on my laptop (RX Vega 7 integrated graphics, AMDGPU there too). The software cursor has correct colours. STEPS TO REPRODUCE 1. Install the KDE Plasma desktop 2. Log in to the X11 or Wayland session 3. Check the cursor colour OBSERVED RESULT The cursor colour is off, exhibiting low contrast in my case. EXPECTED RESULT The cursor colour replicates what is shown in the previews. SOFTWARE/OS VERSIONS KDE Plasma: 5.26.1 KDE Frameworks Version: 5.99. Qt Version: 5.15.6 Linux: 6.0.2 ADDITIONAL INFORMATION Video: https://youtu.be/Qx2mz_p2VRQ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460686] Maximized Qt applications' close buttons don't extend to corner completely
https://bugs.kde.org/show_bug.cgi?id=460686 Aurora Robb Kristiansen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||td21rz...@mozmail.com --- Comment #1 from Aurora Robb Kristiansen --- This has been happening to me a lot as well, I'm using Plasma Wayland with Breeze Light (from the Breeze Twilight global global theme), same button locations, same graphics card manufacturer. KDE Plasma 5.26.1 KDE Frameworks 5.99 Qt 5.15.6 Linux 6.0.2 Video: https://www.youtube.com/watch?v=5lbshX0gklQ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460175] System does not respect middle click paste toggle
https://bugs.kde.org/show_bug.cgi?id=460175 Aurora Robb Kristiansen changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Aurora Robb Kristiansen --- You're right, the feature works as it should in today's release. Much appreciated! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460175] System does not respect middle click paste toggle
https://bugs.kde.org/show_bug.cgi?id=460175 --- Comment #2 from Aurora Robb Kristiansen --- (In reply to Nate Graham from comment #1) > I believe this has been fixed in the final release. Can you test again with > the final 5.26 release which is coming out tomorrow? Thanks! Sure! I'll put it on my to-do, thanks for the heads up. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460175] New: System does not respect middle click paste toggle
https://bugs.kde.org/show_bug.cgi?id=460175 Bug ID: 460175 Summary: System does not respect middle click paste toggle Classification: Applications Product: systemsettings Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: td21rz...@mozmail.com Target Milestone: --- SUMMARY In the Wayland session, I disabled middle click pasting as found in "System Settings" -> "Workspace Behaviour" -> "General Behaviour", there is a toggle for the middle click paste function. When I toggle it off, apply and reboot my computer, the middle mouse button still pastes. STEPS TO REPRODUCE 1. Turn off "Middle Click: Paste selected text" in System Settings 2. Apply (and possibly reboot) 3. Copy some text and middle click in a text entry field OBSERVED RESULT The copied text is pasted into the text entry field even if there is no text highlighted. EXPECTED RESULT Nothing should happen SOFTWARE/OS VERSIONS Linux: 6.0 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I am using Plasma Wayland, and a Corsair Scimitar Pro mouse with the CKB-Next software loaded. However, uninstalling this software did not fix this issue. Possibly relevant? https://bugs.kde.org/show_bug.cgi?id=441668 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 459850] New: Trigger notification on login if calendar event occurred while logged out
https://bugs.kde.org/show_bug.cgi?id=459850 Bug ID: 459850 Summary: Trigger notification on login if calendar event occurred while logged out Classification: Applications Product: kalendar Version: 22.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: td21rz...@mozmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY If a calendar event occurs while the computer is off, or the user is logged off, trigger a notification when the user signs in. Could be a check that happens on sign-in, and optional for anyone worried about performance or just rather wouldn't want this. When I put birthdays on my calendar, I set them to happen all day on those days, and remind me "On event start", i.e. 00:00 I try to be asleep by that time, so my computer is naturally turned off :) Therefore it'd be nice to be reminded as soon as I get to work in the morning on my computer. Of course, this could benefit more use cases than just birthdays. STEPS TO REPRODUCE 1. Make an event in Kalendar 2. Set it to notify you on event start 3. Log out before midnight, and log back in after OBSERVED RESULT There is no visual reminder that the event started while the user was signed out. EXPECTED RESULT A system tray notification that something happened while signed out. SOFTWARE/OS VERSIONS Linux: Arch Linux, Kernel 5.19.11 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #7 from Aurora Robb Kristiansen --- (In reply to Nate Graham from comment #6) > are there any apps across which it does work? Yes, seemingly everything, be it XWayland or Wayland native software. Just tested and it works in Konversation, Discord (XWayland), Konsole. Tutanota, Signal and Telegram also all work, those are running as Wayland apps. Oh actually while writing this comment I just noticed, that it works in Firefox Wayland when copying page contents, it's the URL I can't copy, which is odd... Copying any text on this page shows up on my clipboard manager, copying the URL from the URL bar (in Firefox Wayland of course) just doesn't get sent to Klipper. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #5 from Aurora Robb Kristiansen --- Should add that whatever I copy in Firefox stays within Firefox, as if it has its own sandboxed clipboard. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 Aurora Robb Kristiansen changed: What|Removed |Added CC||mopylr...@mozmail.com --- Comment #4 from Aurora Robb Kristiansen --- In the Wayland session, I am experiencing that copying text and links in Firefox Wayland do NOT appear on my Klipper clipboard, however when running Firefox under xwayland, it works like normal and anything I copy appears on my clipboard. Been experiencing this since before 5.25 released, but was unsure whether that was a Firefox bug or not and didn't get around to looking into it. Does that essentially confirm this bug? Leaving it at reported just in case I'm wrong.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459301] Firefox / Discord use a cross-fade animation when changing browser tabs
https://bugs.kde.org/show_bug.cgi?id=459301 --- Comment #12 from Aurora Robb Kristiansen --- (In reply to Vlad Zahorodnii from comment #7) > Do you have any window rules? Yes, quite a lot, however none of them are for Firefox. Discord's window rule only changes its titlebar colour, as do many of the others. Nice work by the way!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized xwayland apps leave some pixels on the right border
https://bugs.kde.org/show_bug.cgi?id=459373 Aurora Robb Kristiansen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||mopylr...@mozmail.com --- Comment #1 from Aurora Robb Kristiansen --- This happens to me as well on my HiDPI laptop, it is very noticeable in Blender (with xwayland) as it leaves a 2 pixel gap between the right side and along the bottom of the window, when it is maximized. It is also noticeable in VLC. In Blender, most of the app looks very crisp and nice thanks to using its own scaling, but near the right side and bottom, elements are slightly blurry. I wonder if it's because of this gap? SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-zen1-1-zen Graphics Platform: Wayland Laptop: Lenovo IdeaPad 5 Pro 16ACH6 Processor and Graphics: AMD Ryzen 5 5600H with Vega 7 graphics Product Name: 82L5 System Version: ThinkPad X1 Yoga Gen 6 Screen resolution: 2560x1600 PPI: 188.68 Scaling in Plasma settings: 150% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459301] Firefox / Discord use a cross-fade animation when changing browser tabs
https://bugs.kde.org/show_bug.cgi?id=459301 --- Comment #4 from Aurora Robb Kristiansen --- Hi everyone, thank you for your responses. I just sat down to follow the steps you gave me, but for some unfortunate reason I cannot reproduce this issue anymore.. I'm unsure why it won't work now, I did try rebooting my machine when I experienced it, and it did persist after a reboot yesterday. After turning my PC on today it just works. Nevertheless, I'm supplying the requested information, and I'll leave the bug status up to you in case you want to investigate this more, or just close it now. (In reply to Marco Martin from comment #2) > can you try to go in system settings -> desktop effects and uncheck > "Maximize" to see if still happen? I tried turning it off and back on, but it works as intended now in any case. (In reply to Vlad Zahorodnii from comment #1) > How weird, I don't think we put any code to cross-fade between tabs in FF. > Can you post the output of `qdbus org.kde.KWin /KWin supportInformation`? Uploaded it here for you: https://invent.kde.org/-/snippets/2352 (In reply to David Edmundson from comment #3) > send us the snippet of changes when you switch tabs I tried generating some info from changing one tab to another using CTRL+TAB, hopefully there's not too much unnecessary info with it. https://invent.kde.org/-/snippets/2353 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459301] New: Firefox / Discord use a cross-fade animation when changing browser tabs
https://bugs.kde.org/show_bug.cgi?id=459301
Bug ID: 459301
Summary: Firefox / Discord use a cross-fade animation when
changing browser tabs
Classification: Unclassified
Product: kwin
Version: 5.25.90
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: mopylr...@mozmail.com
Target Milestone: ---
Quick preface; I'm not sure if this is a bug, and if it isn't I apologise.
However I'm choosing to report it anyway, as it is unexpected behaviour that
I'm not entirely sure if I like. The effect is nice and it works in some apps,
but for web browsing it's rather in the way of things :)
SUMMARY
When changing tabs in Firefox, the transition between tabs use a cross-fade
animation, like seen in other KDE apps such as Dolphin and the KDE Plasma
System Settings app. Discord (Chromium) is also affected.
I was not able to observe this in other apps, even other Chromium-based apps
such as Signal and Authy.
I confirmed that this is an animation controlled by Kwin/Plasma as the
animation speed setting affects the fade speed.
STEPS TO REPRODUCE
1. Make sure Plasma has animation speed set to anything but instant.
2. Launch Firefox (or possibly other web-browser based apps such as Discord.)
3. Open multiple tabs if you can.
4. Switch tabs or navigate to different views within the app.
OBSERVED RESULT
Switching between tabs/application views use a cross-fading animation.
Video: https://www.youtube.com/watch?v=3_w3sXy_ewA
EXPECTED RESULT
Instant, non-animated transitions between browser tabs, like in Plasma 5.25.5
and older.
SOFTWARE/OS VERSIONS
Linux: Arch Linux, kernel 5.19 ("Linux Zen" kernel)
KDE Plasma Version: Plasma 5.25.90
KDE Frameworks Version: 5.98
Qt Version: 5.15.6
ADDITIONAL INFORMATION
Observed on Plasma Wayland, and thus putting this in the wayland-generic
component; please move it if that is wrong. I'm not sure which component
specifically handles these animations.
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 428028] OSD not positioned ideally on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=428028 Aurora Robb Kristiansen changed: What|Removed |Added CC||mopylr...@mozmail.com --- Comment #2 from Aurora Robb Kristiansen --- I agree, the OSD being all over the place is a bit confusing. As someone with three screens, I wish I could have an option to make the OSD appear on my primary screen ONLY. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #8 from Aurora Robb Kristiansen --- Good catch! Can't believe I didn't think to include my task manager settings.. I had to double check now that you mentioned it, but with all default settings (except for tooltip window thumbnails, as per step 1), it still exhibits this same behaviour. But thank you, I'll make sure to include my settings in future reports. On the other hand I have a lot changes in my Plasma System Settings, but I'm unsure if any of them could affect the bug and which ones I should share here, without dumping thousands of lines of unrelated settings here. I uploaded my "plasma-org.kde.plasma.desktop-appletsrc" file, just in case. Lemme know if I can share are any other files or settings that might affect this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #7 from Aurora Robb Kristiansen --- Created attachment 148074 --> https://bugs.kde.org/attachment.cgi?id=148074=edit My Plasma panel settings These are the settings for my Plasma panel, just in case they're needed. I couldn't see any settings in it that I personally think might be related to the bug, but you never know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #5 from Aurora Robb Kristiansen --- This is on my desktop by the way, not sure if it matters, but as mentioned the same issue occurs on my laptops in the Wayland session. In the video the bug is reproduced in the X11 session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #4 from Aurora Robb Kristiansen --- Hi Nate, thank you very much for attempting to reproduce the issue. I have created a short video and uploaded it to YouTube. You can see it here: https://youtu.be/ljuXR-2lLpA Here's a rundown of what I do in it: 0:02 - First I open another Dolphin window to create a grouped icon. 0:08 - Then I hover over Firefox, to view that window's preview. 0:12 - When I then press Meta + 1 (Dolphin's position), it shows the last previewed window. In this case, Firefox. 0:25 - By previewing Dolphin and removing the cursor from the preview, it can show Dolphin's windows correctly, but only because that was the last preview. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #2 from Aurora Robb Kristiansen --- I just performed another test on this, and found out that the task manager simply attempts to create a preview window where there last was one. This means that, if you hover your mouse over a different application on the task manager and let the tooltip window thumbnail appear, pressing Meta+(Number) on a grouped task will re-spawn the window thumbnail you just created with your mouse. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 Aurora Robb Kristiansen changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #1 from Aurora Robb Kristiansen --- A personal example that hopefully helps make this report more clear: I have two PDFs opened with Okular, on the fifth spot on my icons only task manager. To the left of it I have the DeaDBeeF music player pinned, but it is not running. When I press Meta+5, Plasma only presents an empty preview window above DeaDBeeF, with the text being DeaDBeeF's last state (Song title etc.) before I closed it long ago. Doesn't matter if Okular is pinned or not, it has the same behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 Aurora Robb Kristiansen changed: What|Removed |Added Version|5.24.4 |5.24.3 CC||mopylr...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] New: Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 Bug ID: 452187 Summary: Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: mopylr...@mozmail.com Target Milestone: 1.0 SUMMARY (Example: Meta+5 to open the fifth entry on the icons only task manager) When using the behaviour setting "Shows tooltip window thumbnails", and then pressing a Meta+(Number) shortcut on a grouped entry on the task manager, it instead only highlights an adjacent entry, without opening it. STEPS TO REPRODUCE 1. Configure your Icons Only Task Manager's Behaviour settings to "Shows tooltip window thumbnails" 2. Open multiple instances of a task 3. Pin or open more tasks, doesn't matter if they're single or grouped 4. Use a grouped task's respective Meta+(Number) shortcut OBSERVED RESULT Plasma highlights a nearby task without opening it EXPECTED RESULT Plasma cycles through the grouped tasks' windows on each button press SOFTWARE/OS VERSIONS Linux: Void Linux 64-bit, Kernel 5.16.18_1 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 HARDWARE Processor: Intel Pentium N3540 Graphics: Intel HD Graphics (Mesa DRI)s ADDITIONAL INFORMATION Single tasks (not grouped) behave as intended. Happens in both the X11 and Wayland sessions. Also tested on my Arch Linux desktop system in an X11 session, using the proprietary Nvidia graphics driver and same KDE/Qt software versions as above. At the time of writing I cannot supply a video recording due to the poor hardware I am using, but will attempt to supply one during the coming week. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451744] Implement toggle for "Sticky corners", preventing mouse cursor moving between monitors in corners
https://bugs.kde.org/show_bug.cgi?id=451744 Aurora Robb Kristiansen changed: What|Removed |Added CC||mopylr...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451854] Visual corruption using background contrast with Wayland
https://bugs.kde.org/show_bug.cgi?id=451854 --- Comment #4 from Aurora Robb Kristiansen --- Oh also, moving this to kwin/wayland-generic as I think it's more of a kwin issue. No worries tho, I'm always unsure of these categories myself. I had to check with the kde-bugs channel to make sure this change was ok, in fact -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451854] Visual corruption using background contrast with Wayland
https://bugs.kde.org/show_bug.cgi?id=451854 Aurora Robb Kristiansen changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Aurora Robb Kristiansen --- Just came here to report the same thing, so I can confirm this does indeed happen in the Plasma Wayland session, using Nvidia's proprietary driver. Currently on version 510.54, but I've observed this on older driver versions (with support for the GBM backend). It only happens with the "Background Contrast" effect on, "Blur" does not affect it at all. In the X11 session, it works perfectly. A bit of info about my environment: SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Linux Kernel 5.16.16-zen1-1-zen KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION CPU: Ryzen 5 2600 GPU: Nvidia GTX 1060 6GB Nvidia Driver 510.54 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451854] Visual corruption using background contrast with Wayland
https://bugs.kde.org/show_bug.cgi?id=451854 Aurora Robb Kristiansen changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Target Milestone|1.0 |--- Component|Panel |wayland-generic Product|plasmashell |kwin CC||mopylr...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451744] Implement toggle for "Sticky corners", preventing mouse cursor moving between monitors in corners
https://bugs.kde.org/show_bug.cgi?id=451744 --- Comment #2 from Aurora Robb Kristiansen --- (In reply to ratijas from comment #1) >Moving to KWin. Not sure about the component, but it's definitely closer. Thanks a lot! >it has this nice feature of _sometimes_ magically stopping the cursor from >moving to the other screen. Often it triggers unpredictably or when not needed >at all, but that's just a matter of heuristics which can and should be >improved. Glad I'm not alone I agree, it can and should definitely be improved upon and not carbon copied. I found that Windows stops your cursor completely in corners about... 2-ish percent of the screen up and downwards depending on the corner location. I think this is perfect, but it should be configurable. It also stops your mouse on **any** edge if you're dragging a window; UNLESS your cursor is traveling at a certain speed. This can be a blessing and a curse.. Again, also how it can be improved upon. I like the function, but wish I could tune the velocity threshold when I do have no option but to use Windows. Others will definitely want to disable it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 451744] New: Implement toggle for "Sticky corners", preventing mouse cursor moving between monitors in corners
https://bugs.kde.org/show_bug.cgi?id=451744
Bug ID: 451744
Summary: Implement toggle for "Sticky corners", preventing
mouse cursor moving between monitors in corners
Product: frameworks-plasma
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: libplasma
Assignee: plasma-b...@kde.org
Reporter: mopylr...@mozmail.com
CC: m...@ratijas.tk, notm...@gmail.com
Target Milestone: ---
Created attachment 147636
--> https://bugs.kde.org/attachment.cgi?id=147636=edit
An example image showing a mouse cursor moving into a corner, and its
trajectory sliding onto the adjacent monitor. An example of a 25px threshold is
also drawn on top
SUMMARY
To aid with button interactions in monitor corners, the four corners of a
monitor should (optionally) stop quick mouse movements towards corners from
moving onto the adjacent monitor.
HOW THIS IS USEFUL TO USERS
An example for a user with the close button in the top left of an application:
They quickly move their cursor to the top left, to close a maximized
application. However due to the quick movement, the cursor slides onto the
left-adjacent monitor.
Plasma stopping the mouse cursor from doing this in corners would be a great
quality-of-life improvement for users with many monitors, who tend to maximize
applications on several monitors. This is only an example, there are more
benefits to this.
Another use case I can imagine this is extremely helpful for, is to aid hot
corner usage for window tiling.
Let me use a final, personal example: I have a hotkey bound to Spectacle
rectangle selection, to copy a screenshot to clipboard quickly. Sometimes I
want to capture screenshots beginning in a screen edge, with these "sticky"
corners, worrying about capturing pieces of adjacent monitors (or manually
editing these tiny details) is no longer needed.
It would also be nice if this could have a configurable threshold. Let's say by
default, on a 1080p monitor, it stops your mouse cursor if it tries to move to
the other screen 20~25 pixels within the top or bottom of the screen. A slider
can let users define this threshold themselves.
The feature is most likely best for power users. So at your own discretion,
would best be implemented as an optional feature, disabled by default to avoid
confusion for existing Plasma users if anything.
STEPS TO REPRODUCE
1. With a multi-monitor setup, move the mouse cursor all the way down or up
into a corner that has another monitor next to it
2. Move the mouse cursor towards the other monitor
OBSERVED RESULT
The mouse cursor moves freely to the other monitor with no resistance
EXPECTED RESULT
Plasma should ideally stops the mouse cursor from moving onto the other monitor
SOFTWARE/OS VERSIONS
Linux: Linux 5.16 ("Zen")
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
An implementation of this feature can be observed in action with Windows 8 or
newer.
In case my explanation is not clear, I have attached an image which should
hopefully clarify.
Apologies if this is the wrong category to post this wish in. Thank you for
reading!
--
You are receiving this mail because:
You are watching all bug changes.
