[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #96 from Sebastian E. --- Is there a follow-up issue for the underlying cause, i.e. the deleted windows that shouldn't exist in the first place? Those which are presumably caused by any of the window open/close animations? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #75 from Sebastian E. --- Thanks, vm, for keeping digging and figuring this out! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #65 from Sebastian E. --- Unfortunately, that bug will probably be resolved as duplicate of https://youtrack.jetbrains.com/issue/JBR-6921, which is already resolved as third-party problem. I reproduced the issue using the method demonstrated by Vm in his video above. It works well, but took more clicks for me. I also tried two other applications instead of IntelliJ: a Java Swing app and a Compose Desktop app, both using the default JRE and and Jetbrains' JRE (found in ~/.jbr/). It didn't happen with them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #48 from Sebastian E. --- And "xev -root", at least on X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #47 from Sebastian E. --- The output of "xwininfo -root -all" could be useful. But you need to check it for personal information, it contains Window titles. By the way, there's an issue at the Jetbrains issue tracker, too: https://youtrack.jetbrains.com/issue/JBR-6921 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483162] Sometimes wrong window stacking stacking orders with NVIDIA and AMD GPUs
https://bugs.kde.org/show_bug.cgi?id=483162 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] regression: dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450268] Magic Lamp / Slide effects duration speed should always be controlled by global option
https://bugs.kde.org/show_bug.cgi?id=450268 --- Comment #11 from Sebastian E. --- (In reply to guimarcalsilva from comment #10) > The right thing to do here is to fix the speed factor of the animation in > the code so it has the same speed as all other animations. If it's too slow > compared to everything else, then that's the problem. Leaving it up to users > to fix problems is not good for anyone. Anyway, the default animation speed > for that specific effect is another bug and should be discussed in bug > 455450 , not here. There is no objectively correct speed factor. It's subjective and thus must be a configurable value. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450268] Magic Lamp / Slide effects duration speed should always be controlled by global option
https://bugs.kde.org/show_bug.cgi?id=450268 --- Comment #9 from Sebastian E. --- (In reply to guimarcalsilva from comment #8) > If there's a problem with the animation itself, then that should be fixed > instead of leaving it up to the user to work around the issue by manually > speeding up individual animations or manually choosing the easing curves. > Mind you easing curves don't usually change the amount of time it takes for > an effect to complete, only the speed of movement within a certain > timeframe, so changing it wouldn't have any effect on the amount of time it > takes for windows to appear after the animation starts. The problem with the slide animation itself is that it's too slow. Sure, I could increase the global animation speed, but then all other animations would be too fast. Of course, that's just my opinion. How to fix that? Hmm... how about providing an option to control the speed of the slide animation independently from all other animations? Oh, it already existed, but was removed, because it was inconsistent? Well, then how about providing that option for every animation? That would make everyone happy, and emphasize KDE's selling point of being an un-opinionated, customizable, powerful desktop environment, instead of undermining it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450268] Magic Lamp / Slide effects duration speed should always be controlled by global option
https://bugs.kde.org/show_bug.cgi?id=450268 --- Comment #7 from Sebastian E. --- Premik said that the last pixels take too long to scroll. That's the effect of easing, not a bug. The animation slows down towards the end. Windows that overflow to another screen are indeed invisible on that screen during sliding, which is a bug. The defaults Premik is talking about are obviously the easing mode and the duration of animations relative to each other. Now the slide animation takes a hardcoded factor x as long as some other animation. Before, you could at least change the speed of the slide and magic lamp independent of the speed of other effects. Now, the ratio is hardcoded. That's clearly a regression, and yet another step from a sophisticated, un-opinionated DE to a dumbed-down, opinionated DE. Users should be able to override the easing mode and duration of each animation individually. @Premik: The configuration dialog of the slide effect used to have an option for the animation duration, which was removed from the latest release. Maybe you once changed it and forgot about it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450268] Magic Lamp / Slide effects duration speed should always be controlled by global option
https://bugs.kde.org/show_bug.cgi?id=450268 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net --- Comment #3 from Sebastian E. --- I guess the reason for those independent duration settings was that the magic lamp and slide animations interrupt workflow. The overall animation speed might be nice, but maybe you don't want to wait a second for the desktop to switch or a window to be restored. At least I don't want to, so I now had to set global animation speed to almost instant, because the choices available for the desktop switching animation also lack "none". Huge improvement! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 452782] Temperature sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=452782 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443723] "Display geometry when moving or resizing" does not work under wayland
https://bugs.kde.org/show_bug.cgi?id=443723 --- Comment #8 from Sebastian E. --- Yet another feature dropped. :/ I skimmed through the scripting documentation (https://develop.kde.org/docs/extend/plasma/scripting/api/), and need some hints. How can I register a listener for window events like resize/move, and how can I create a tip, which would be a top level window without decoration, I guess? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449842] New: Snap helper no longer displays window geometry
https://bugs.kde.org/show_bug.cgi?id=449842 Bug ID: 449842 Summary: Snap helper no longer displays window geometry Product: kwin Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: kde-b...@foobarlibre.net Target Milestone: --- After upgrading to 5.24, when moving or resizing a window with Snap Helper enabled, the usual labels with window position and size are not displayed. STEPS TO REPRODUCE 1. Enable snap helper and move or resize a window. OBSERVED RESULT No window geometry displayed. EXPECTED RESULT Window geometry should be displayed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #26 from Sebastian E. --- KSysGuard and KDE System Monitor are system utilities, and as such should first and foremost display system information as it is. Any processing that helps to better dig through and display that information is a nice-to-have option, but should only be that - an option. * This is not macOS running exclusively on a limited, well-known set of Apple hardware. Any attempt to properly clean up a raw list of sensors is futile. * There's the kernel, lm_sensors, and systemd-sensorsd suddenly popping up wouldn't surprise me. That's the layer were cleanup should happen. Doing it at the application layer is conceptually wrong (but of course still a nice-to-have option, especially when the layers below leave something to be desired). * There's a reason why people choose a particular OS and desktop environment. And sometimes that choice changes when beginners become experts. Don't look to macOS or Windows as if the grass was greener there, just because it's more polished. KDE is the side with the greenest grass. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #19 from Sebastian E. --- What about k10temp? I have a Pie Chart System Monitor Sensor in my bottom panel which used to display Tctl, until it unfortunately stopped working after an update. I left it there, hoping it would work again after another update, occasionally checking its settings. Now there's temperature for each core, but not for all cores (i.e. the CPU package temperature). I can add temperature for "[Group] CPU", which looks really fancy, but I already got an RGB keyboard, so I don't really need that. Will there be an option to just get a simple reading of the current CPU temperature again? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #16 from Sebastian E. --- (In reply to Felipe Kinoshita from comment #15) > Sure, also why you don't make this change, seems like you have been studying > this code a lot recently, just create a merge request and I can take a loot > at it. I've already read parts of the "Get involved" guide, and successfully installed kdesrc-build and built/run Dolphin. But I still need to figure out more stuff, like setting up CLion, code style, git-pulling the latest changes, properly run it on my existing system, testing, Gitlab account, how to make a merge request, etc... If I've had enough time, I would have done it myself. But yeah, I'll probably contribute in the future. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277
--- Comment #14 from Sebastian E. ---
@Felipe Kinoshita
Could you please revert or fix your commit that broke it?
https://invent.kde.org/plasma/plasma-workspace/-/commit/6befb657dd9fd811160e0369913d769cfff7f02d
Your commit reintroduced a change that has been reverted before:
https://invent.kde.org/plasma/plasma-workspace/-/commit/885c4abe7b5343caa7407c4b441b2cfcd78828c3
Fixing that warning along with the change did not really help, it just crashes
differently.
Alternatively replace
if (screen == nullptr) {
return;
}
with
if (screen == nullptr) screen = QGuiApplication::screens()[0]
Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #12 from Sebastian E. --- Wondering why it crashes in PopupProxy::parent(), and not in KlipperPopup::rebuild()... Calling methods on null objects may work until "this" is actually accessed, which doesn't happen before PopupProxy::parent() or QObject::parent(). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #11 from Sebastian E. --- Alignment at bottom is not sufficient to reproduce the issue. There also must be no screen at the top left of the virtual geometry. https://invent.kde.org/plasma/plasma-workspace/-/blob/9d2051b0ec2d4857a61d17d9d3f766614c0f42d7/klipper/klipperpopup.cpp So, the constructor gets the window info of a QMenu that's just been initialized and then calls QGuiApplication::screenAt to query the screen at its center. I don't know what's the initial size of a QMenu, but I assume the coordinates of its center are not much more than (50, 50). So because there is no screen in our case, the constructor returns early, leaving m_popupProxy uninitialized. Because m_dirty is initially true, rebuild() will be called on the aboutToShow signal, where m_popupProxy is dereferenced while being null. Boom. Aside from that, the intent of the code seems to be to determine the maximum width and height of the popup. Uhm, well, the code could as well just take a random screen from QGuiApplication::screens(). The correct thing to do would be to iterate QGuiApplication::screens() and collect the minimum width and height. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #4 from Sebastian E. --- Also, my secondary left display is smaller than my primary right display and aligned to the bottom. When I align the left screen to the top, it works, too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #3 from Sebastian E. --- Probably only happens with multiple displays. Workaround: * Disable secondary display (or all except one). * Invoke shortcut. Plasma will crash once, but then it will work. Just restarting Plasma would probably do the job, too. * Re-enable other displays. * Will work until reboot (or probably until Plasma is restarted). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 Sebastian E. changed: What|Removed |Added CC||kde-b...@foobarlibre.net --- Comment #2 from Sebastian E. --- I have the same issue. Plasma crashes every time I use the Clipboard popup shortcut. Application: plasmashell (5.22.0) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-arch1-1 x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: "Arch Linux" Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f79e727b752 in () at /usr/lib/qt/plugins/plasma/dataengine/plasma_engine_clipboard.so #5 0x7f79e7279d2b in () at /usr/lib/qt/plugins/plasma/dataengine/plasma_engine_clipboard.so #6 0x7f79e727a033 in () at /usr/lib/qt/plugins/plasma/dataengine/plasma_engine_clipboard.so #7 0x7f79e725f523 in () at /usr/lib/qt/plugins/plasma/dataengine/plasma_engine_clipboard.so #8 0x7f7a2174e3bb in () at /usr/lib/libQt5Core.so.5 #9 0x7f7a223c7203 in QAction::triggered(bool) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f7a223c9f18 in QAction::activate(QAction::ActionEvent) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f7a234356ea in () at /usr/lib/libKF5GlobalAccel.so.5 #12 0x7f7a2174e3bb in () at /usr/lib/libQt5Core.so.5 #13 0x7f7a2343ffa5 in () at /usr/lib/libKF5GlobalAccel.so.5 #14 0x7f7a234401c3 in () at /usr/lib/libKF5GlobalAccel.so.5 #15 0x7f7a220b9300 in () at /usr/lib/libQt5DBus.so.5 #16 0x7f7a2174415f in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7f7a223cdd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f7a2171700a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f7a2171a109 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #20 0x7f7a21770604 in () at /usr/lib/libQt5Core.so.5 #21 0x7f7a1fa3802c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #22 0x7f7a1fa8bb59 in () at /usr/lib/libglib-2.0.so.0 #23 0x7f7a1fa35781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #24 0x7f7a2176fc36 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7f7a2171597c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7f7a2171dee4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #27 0x5654bd2dd20f in () #28 0x7f7a210a1b25 in __libc_start_main () at /usr/lib/libc.so.6 #29 0x5654bd2dd34e in () [Inferior 1 (process 1498) detached] -- You are receiving this mail because: You are watching all bug changes.
