[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 --- Comment #11 from Ralf Jung --- Ah, in fact it seems it was already reported: https://bugreports.qt.io/browse/QTBUG-67579 https://bugreports.qt.io/browse/QTBUG-87778 It is labeled as fixed for Qt 5.15.12, I am on Qt 5.12.10. I see 5.15.12 is in Debian experimental so I hope I'll get the fix soon-ish. :D -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 --- Comment #10 from Ralf Jung --- Getting back to the issue of cursor.. "QT_QPA_PLATFORMTHEME=breeze qgit" also uses the wrong cursor theme. Is that a bug in Breeze or not? qt5ct does not provide any way to set a custom cursor, so I don't think this is a case of that theme being configured incorrectly. Literally every single Qt theme I tried uses the wrong cursors. It's clearly not just a KDE theme issue though so I'll report this with Qt directly. Also, setting QT_QPA_PLATFORM=xcb fixes the cursor. So this seems to be Wayland-related. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 --- Comment #9 from Ralf Jung --- > The way Qt works is that it expects for the environment it's run in to set a > QPT that tells it how to integrate Qt apps into that environment so they look > and feel correct. This is *how* Qt apps know how to look and feel native in > the environment they're run in. But if the environment doesn't bother to > provide a QPT, then the integration doesn't happen and Qt apps look and feel > junky. I doubt Microsoft and Apple are providing QPT so that can't be the full story. But also, Qt can't just declare that someone else must do some work. That's not how open-source works. > Clearly GNOME people do not have the interest, skill, and/or time to get it > done. That's fine; I can't blame them. So the task basically falls to distro > maintainers. No, I can't agree with that. Distro maintainers do integration, yes, by gluing together what exists and then testing that it all works together. It is not their task to *write entirely new UI themes* for a toolkit that unilaterally decided that it wants to out-source this work. If Qt wants to look and feel native wherever possible, that's great. But that should come *on top of* providing a good baseline that works everywhere that Qt hasn't yet gained native support for. I don't expect Qt applications in GNOME to be perfectly polished and integrated without help from the GNOME people. But I do expect them to meet a reasonable baseline, and it is Qt's responsibility to deliver that baseline. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 --- Comment #7 from Ralf Jung --- > I know there's some resistance to the concept of adopting a native > look-and-feel in some GNOME circles It is true that GNOME apps look not "native" on KDE desktops, as they just ignore the DE and do their own thing. And from a KDE perspective that's probably a bug in the GNOME apps. But honestly that's better than what happens with Qt/KDE apps. They don't look "native" on GNOME desktops either, and while GNOME apps have a very well-polished but "non-native" look in KDE, KDE apps just fall back to the standard "Fusion" Qt theme, which is not nearly as nice as Breeze or the GNOME look. It's not native either way. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 --- Comment #6 from Ralf Jung --- Thanks for getting back to this! I know dealing with user complaints can be tiring, and I appreciate the time you are taking. :) > That's the problem; qt5ct is a DIY QPT that gives you the user control over > everything a QPT can do. When using it, it becomes your responsibility to > configure it to your liking. But if you're looking for something that works > well out of the box, qt5ct is not the best choice. :) Without that env var (i.e., out of the box), it looks even worse, and the cursor is just as wrong. So qt5ct is not responsible for the cursor problem. > Probably this one: https://github.com/FedoraQt/QGnomePlatform "QGnomePlatform project is unmaintained a no longer actively developed." I have qt5-gtk-platformtheme installed. I have no idea if there's anything I am expected to do beyond installing it, but it doesn't seem to help. > I know there's some resistance to the concept of adopting a native > look-and-feel in some GNOME circles, but Qt is based around this concept, so > when a GNOME-focused distro fails to do the necessary setup, the end result > is that Qt apps look and feel terrible when run in GNOME. They may not like > it, but ensuring that a sane QPT is set by default is one of the basic > integration responsibilities of a distro. I'm not sure if I would call Debian a GNOME-focused distro. It's a "we have everything" distro, isn't it? The Qt package can't know which DE I am using. Obviously most KDE contributors use KDE as their DE so there's no reason why they would care about how their apps look like on GNOME, and I can't blame them for that, it's free software after all. But it is unfortunate that this means mixing the best parts of GNOME and KDE is a lot more work than it should be. If Qt aims to be "native" in every environment it is started in, I guess it would be a Qt bug (or at least feature request) if Qt apps don't look native on GNOME by default? It would certainly be a bug if Qt apps looked like this on Windows or macOS... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 --- Comment #4 from Ralf Jung --- Which package in the distro would you recommend should this be reported against? As you probably know, there is no way to just report an issue against "the distro", it needs to be e.g. the Qt package. FWIW, here are the relevant environment variables on my system: QT_ACCESSIBILITY=1 QT_QPA_PLATFORMTHEME=qt5ct QTWEBENGINE_DICTIONARIES_PATH=/usr/share/hunspell-bdic/ QT_QPA_PLATFORM=wayland QT_IM_MODULE=ibus I had to set some of them by hand as the default experience of Qt apps under Gnome is abysmal. This is in my ~/.profile: # make Qt apps look reasonable under Gnome if [ "$XDG_CURRENT_DESKTOP" == "GNOME" ]; then export QT_QPA_PLATFORMTHEME=qt5ct export QT_QPA_PLATFORM=wayland fi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 Ralf Jung changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ralf Jung --- QGit has the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Ralf Jung changed: What|Removed |Added CC|p...@ralfj.de | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480272] New: KDE applications use the wrong cursor theme in a Gnome desktop
https://bugs.kde.org/show_bug.cgi?id=480272 Bug ID: 480272 Summary: KDE applications use the wrong cursor theme in a Gnome desktop Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY Note: this is not a systemsettings bug. It affects all KDE applications. I just don't know in which category to put it. STEPS TO REPRODUCE 1. Install Gnome as well as one or two KDE applications (e.g. Dolphin, Gwenview) 2. Open a KDE application OBSERVED RESULT The cursor in the KDE application is different from, and a lot bigger than, the cursor used in every other application. EXPECTED RESULT KDE applications should follow the cursor theme of the current desktop environment. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks Version 5.107.0 Qt Version 5.15.10 (Would be great if there was an easy way to get this information. "About system" only works when using KDE as the desktop. I hope KDE applications are generally intended to work with other desktops as well, so this form should not assume that I am using KDE as my desktop.) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 479793] Ctrl-X does not cut all the files, some are missing
https://bugs.kde.org/show_bug.cgi?id=479793 --- Comment #2 from Ralf Jung --- To be clear, there is no data loss. Half the files get moved, half the files stay where they were. Not sure what you mean by "overwrite dialog" -- is that the one asking me what to do when one of the files already exists in the destination? No that dialog did not show; the files did not exist in the target. Note that I am using Dolphin in a Gnome session; not sure if that can potentially make a difference. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479793] New: Ctrl-X does not cut all the files, some are missing
https://bugs.kde.org/show_bug.cgi?id=479793 Bug ID: 479793 Summary: Ctrl-X does not cut all the files, some are missing Classification: Applications Product: dolphin Version: 23.08.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: p...@ralfj.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When I select multiple files and cut them (Ctrl-X), and then paste them somewhere else, some files are missing. Dolphin seems to only actually move about half the files (the first half), and the rest stays at the original location. This means it can take 4-5 attempts to actually move all the files I want to move, which is quite tedious. STEPS TO REPRODUCE 1. Select a bunch of files (5-50) 2. Ctrl-X 3. Navigate to another folder 4. Ctrl-V OBSERVED RESULT Only about half the files get moved EXPECTED RESULT All the files should get moved SOFTWARE/OS VERSIONS Linux/KDE Plasma: - (I use Gnome as my DE) KDE Frameworks Version 5.107.0 Qt Version 5.15.10 ADDITIONAL INFORMATION This used to work fine in the past but broken with a update a few months ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442321] Task manager sometimes opens new instance of an already-running app on left click when using wayland
https://bugs.kde.org/show_bug.cgi?id=442321 Ralf Jung changed: What|Removed |Added CC|p...@ralfj.de | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462280] kwin (wayland) completely freezes when plugging in external screen
https://bugs.kde.org/show_bug.cgi?id=462280 --- Comment #7 from Ralf Jung --- I've switched my setup and no longer use KDE, so I can't test this, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465377] Sometimes, drag'n'drop of entries in the task bar stops working
https://bugs.kde.org/show_bug.cgi?id=465377 --- Comment #6 from Ralf Jung --- I think in my case it was probably the stuck modifier key issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 415948] Session creation in Kate causes invalid desktop file to be placed in ~/.local/share/applications
https://bugs.kde.org/show_bug.cgi?id=415948 --- Comment #20 from Ralf Jung --- This is still a problem in Kate 22.12.3. It makes Kate very hard to use on non-KDE desktop environments that expect desktop files to match the spec. One doesn't even need to create a session. Just starting Kate when a session exists, and closing it again, will create the faulty desktop file. I would probably have to delete all my sessions to work around this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 415948] Session creation in Kate causes invalid desktop file to be placed in ~/.local/share/applications
https://bugs.kde.org/show_bug.cgi?id=415948 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465377] Sometimes, drag'n'drop of entries in the task bar stops working
https://bugs.kde.org/show_bug.cgi?id=465377 --- Comment #3 from Ralf Jung --- I'm currently on the beta, according to the system info screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465377] Sometimes, drag'n'drop of entries in the task bar stops working
https://bugs.kde.org/show_bug.cgi?id=465377 --- Comment #1 from Ralf Jung --- I wonder if this is the same underlying cause as https://bugs.kde.org/show_bug.cgi?id=442321 - is some modifier key getting stuck? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465377] New: Sometimes, drag'n'drop of entries in the task bar stops working
https://bugs.kde.org/show_bug.cgi?id=465377 Bug ID: 465377 Summary: Sometimes, drag'n'drop of entries in the task bar stops working Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de Target Milestone: 1.0 SUMMARY I have the task bar configured to "custom" sorting so that I can drag'n'drop the windows the way I like. However, sometimes that just stops working -- when I click and press and drag an entry in the taskbar, it no longer enters the usual drag'n'drop mode. I have no idea how to get plasma in that state. It probably has to do with switching back and forth between having an external screen connected, and no external screen. I only started seeing this the last few weeks, until around 5.26.0 this did not happen. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465118] New: Sometimes, clicking trying to bring a window to the front will instead open a new instance of that application
https://bugs.kde.org/show_bug.cgi?id=465118 Bug ID: 465118 Summary: Sometimes, clicking trying to bring a window to the front will instead open a new instance of that application Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de Target Milestone: 1.0 SUMMARY Sometimes plasma gets into a state where when I click on something in the task manager to bring an already running application to the front, it will instead spawn a new instance of that application. This will happen for all running applications -- it becomes impossible to switch to an already running application (except via alt-tab). Killing and re-starting Plasma fixes this. I've had this happen both immediately after login, and when the desktop geometry changes due to a screen being (un)plugged. This only started happening when I switched to Wayland -- but that came with a big system update so it's not clear which of those changes started this. STEPS TO REPRODUCE 1. With some applications (Firefox, Thunderbird, Konsole) running, click on one of their icons in the task manager OBSERVED RESULT A new instance of that application is being started. EXPECTED RESULT The existing window should be brought to the front. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432788] kwin freezes when sharing a minimized window
https://bugs.kde.org/show_bug.cgi?id=432788 Ralf Jung changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Ralf Jung --- I switched to wayland where screen sharing works very differently -- I just tried selecting a minimized window and it worked fine, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461156] On X11, kwin locks up with 100% CPU load when external screen gets plugged in
https://bugs.kde.org/show_bug.cgi?id=461156 --- Comment #4 from Ralf Jung --- I have switched to Wayland to avoid all these X11 issues, and am not able to reproduce this any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463655] Cannot select non-native screen resolution under Wayland
https://bugs.kde.org/show_bug.cgi?id=463655 Ralf Jung changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463734] Icons in left sidebar are too big with screen scaling
https://bugs.kde.org/show_bug.cgi?id=463734 --- Comment #9 from Ralf Jung --- Changing the setting works for me, thanks! :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463734] Icons in left sidebar are too big with screen scaling
https://bugs.kde.org/show_bug.cgi?id=463734 --- Comment #6 from Ralf Jung --- A few days ago, before the last update and before I used scaling, the icons on the left had the same size as the ones at the bottom. That is the default behavior I would expect. But I guess I got fooled by the fact that I did a system update and set up scaling basically at the same time. Is having a separate size for these sidebar icons a recent(-ish) change? I can confirm that they indeed scale with the display scaling. Thanks for pointing that out! So this is a different bug than I thought -- I would say it is rather strange that these icons have a different default size than all the others. I doubt I will not be the only one who will see these icons and assume that this must be a bug since they look out-of-place and this there is no clear reason for them to be that big. But this is definitely much more a matter of opinion than the display scaling issue I thought I was seeing. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463734] Icons in left sidebar are too big with screen scaling
https://bugs.kde.org/show_bug.cgi?id=463734 --- Comment #3 from Ralf Jung --- Also note that the icons are scaled twice as much as they should be (rather than being unscaled, which is what one would expect for such hard-coded pixel values). I don't know how that happens, but the icon size is currently set to 32 pixels and the actual size is around 64 pixels. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463734] Icons in left sidebar are too big with screen scaling
https://bugs.kde.org/show_bug.cgi?id=463734 Ralf Jung changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|NOT A BUG |--- --- Comment #2 from Ralf Jung --- I think it is a bug if an application does not properly handle scaling by default. Are you saying that each time I switch between a screen with 1x scaling and a screen with 2x scaling (i.e., several times a day, as I plug in external screens and unplug them again), I should also change the Kate settings? That's clearly not a proper solution. Just imagine having to adjust scaling by hand in every single application, that's clearly not how scaling is supposed to work. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463734] New: Icons in left sidebar are too big with screen scaling
https://bugs.kde.org/show_bug.cgi?id=463734 Bug ID: 463734 Summary: Icons in left sidebar are too big with screen scaling Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- Created attachment 154962 --> https://bugs.kde.org/attachment.cgi?id=154962=edit a screenshot demonstrating the problem SUMMARY Icons in the sidebar to the left are too big when screen scaling is enabled. See the attached screenshot for how it looks with a scaling factor of 2. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.0-6-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 463656] kioslave crashes on first login after boot
https://bugs.kde.org/show_bug.cgi?id=463656 Ralf Jung changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ralf Jung --- That would be #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x7f4406aa9d2f in __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 0x7f4406a5aef2 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f4407162be1 in KCrash::defaultCrashHandler (sig=11) at ./src/kcrash.cpp:633 #4 #5 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #6 0x7f4406aa9d2f in __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #7 0x7f4406a5aef2 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #8 #9 0x7f4406b1b0af in __GI___poll (fds=0x7f43fc0029e0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #10 0x7f4405c659ae in g_main_context_poll (priority=, n_fds=2, fds=0x7f43fc0029e0, timeout=, context=0x7f43fc000c30) at ../../../glib/gmain.c:4553 #11 g_main_context_iterate (context=context@entry=0x7f43fc000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4243 #12 0x7f4405c65acc in g_main_context_iteration (context=0x7f43fc000c30, may_block=1) at ../../../glib/gmain.c:4313 #13 0x7f4406f098b6 in QEventDispatcherGlib::processEvents (this=0x7f43fc000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x7f4406eb024b in QEventLoop::exec (this=this@entry=0x7f4401bfec10, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #15 0x7f4406ccab77 in QThread::exec (this=this@entry=0x7f440649bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #16 0x7f4406423487 in QDBusConnectionManager::run (this=0x7f440649bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ./src/dbus/qdbusconnection.cpp:179 #17 0x7f4406ccbd33 in QThreadPrivate::start (arg=0x7f440649bd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:331 #18 0x7f4406aa7fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #19 0x7f4406b2866c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463655] Cannot select non-native screen resolution under Wayland
https://bugs.kde.org/show_bug.cgi?id=463655 --- Comment #2 from Ralf Jung --- Created attachment 154951 --> https://bugs.kde.org/attachment.cgi?id=154951=edit kscreen-console bug Full output is attached. There's an "xrandr --verbose" section in there, which strikes me as odd in a wayland session -- but it *does* list a lot of alternative resolutions, including the one I want to use. KScreen (the UI) does not offer it though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463664] New: Launch feedback icon too big with screen scaling
https://bugs.kde.org/show_bug.cgi?id=463664 Bug ID: 463664 Summary: Launch feedback icon too big with screen scaling Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Configure "launch feedback" to "static" 2. Set screen scaling to 200% OBSERVED RESULT The launch icon is twice as big as it should be EXPECTED RESULT The icon should be scaled by the same amount as everything else, not double that amount SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.0-6-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION No idea which component of KDE is rendering those launch feedback icons (the things next to the cursor when an application starts) -- please move to the right product, if this is not the right one. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 463657] New: Applications are blurry after setting screen scaling (until next restart)
https://bugs.kde.org/show_bug.cgi?id=463657 Bug ID: 463657 Summary: Applications are blurry after setting screen scaling (until next restart) Classification: Plasma Product: KScreen Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY This is probably not a KScreen bug, but it affects all KDE applications so I am not sure where else to report it. I hope the devs know the right product/component for this. :) I also probably used the wrong keywords when searching since I assume this has already been reported? STEPS TO REPRODUCE 1. Have some KDE applications running 2. Change screen scaling to a different value OBSERVED RESULT The applications adjust their scaling in a way that is very blury, it's hard to even properly read text. After logging out and back in, everything is crisp. EXPECTED RESULT Things should scale properly and crisply immediately. Having to restart all my applications is a big disruption of the work I am trying to get done and should not be necessary. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.0-6-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 463656] New: kioslave crashes on first login after boot
https://bugs.kde.org/show_bug.cgi?id=463656 Bug ID: 463656 Summary: kioslave crashes on first login after boot Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.101.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: p...@ralfj.de CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY The first time I log in to a KDE session after boot, it takes a super long time to load (showing the loading screen with the spinning gear), and then greets me with a fully black screen and a crash dialog showing that kioslave crashed. After around 10 more seconds then Plasma begins to show. The KDE crash dialog is unable to produce any information about this crash; here is what cordumpctl shows: PID: 2548 (kioslave5) UID: 1000 (r) GID: 1000 (r) Signal: 11 (SEGV) Timestamp: Sat 2022-12-31 10:02:24 CET (2min 55s ago) Command Line: /lib/x86_64-linux-gnu/libexec/kf5/kioslave5 /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/desktop.so desktop "" local:/run/user/1000/plasmashellTIevMY.1.slave-socket Executable: /usr/lib/x86_64-linux-gnu/libexec/kf5/kioslave5 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (r) Boot ID: a98548db83a94712ae8d4d8abc92c92a Machine ID: b25d50fef3bc4281b370b693527f808e Hostname: r-thinktop Storage: /var/lib/systemd/coredump/core.kioslave5.1000.a98548db83a94712ae8d4d8abc92c92a.2548.167247734400.zst (present) Size on Disk: 570.8K Message: Process 2548 (kioslave5) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.4-1.amd64 Stack trace of thread 2552: #0 0x7f4406aa9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #1 0x7f4406a5aef2 __GI_raise (libc.so.6 + 0x3bef2) #2 0x7f4407162be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f4406a5af90 __restore_rt (libc.so.6 + 0x3bf90) #4 0x7f4406aa9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #5 0x7f4406a5aef2 __GI_raise (libc.so.6 + 0x3bef2) #6 0x7f4406a5af90 __restore_rt (libc.so.6 + 0x3bf90) #7 0x7f4406b1b0af __GI___poll (libc.so.6 + 0xfc0af) #8 0x7f4405c659ae n/a (libglib-2.0.so.0 + 0x549ae) #9 0x7f4405c65acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #10 0x7f4406f098b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3098b6) #11 0x7f4406eb024b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b024b) #12 0x7f4406ccab77 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcab77) #13 0x7f4406423487 n/a (libQt5DBus.so.5 + 0x17487) #14 0x7f4406ccbd33 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcbd33) #15 0x7f4406aa7fd4 start_thread (libc.so.6 + 0x88fd4) #16 0x7f4406b2866c __clone3 (libc.so.6 + 0x10966c) Stack trace of thread 2548: #0 0x7f4406b1b0af __GI___poll (libc.so.6 + 0xfc0af) #1 0x7f4407162160 n/a (libKF5Crash.so.5 + 0x5160) #2 0x7f4407162b67 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b67) #3 0x7f4406a5af90 __restore_rt (libc.so.6 + 0x3bf90) #4 0x7f440733aa29 _ZN3KIO9SlaveBase11setKillFlagEv (libKF5KIOCore.so.5 + 0x95a29) #5 0x7f440733aa4f n/a (libKF5KIOCore.so.5 + 0x95a4f) #6 0x7f4406a5af90 __restore_rt (libc.so.6 + 0x3bf90) #7 0x7f44072f6a9a n/a (libKF5KIOCore.so.5 + 0x51a9a) #8 0x7f44073b24fd n/a (libKF5KIOCore.so.5 + 0x10d4fd) #9 0x7f44073b2839 n/a (libKF5KIOCore.so.5 + 0x10d839) #10 0x7f4406a5d435 __run_exit_handlers (libc.so.6 + 0x3e435) #11 0x7f4406a5d5aa __GI_exit (libc.so.6 + 0x3e5aa) #12 0x7f4406a46191 __libc_start_call_main (libc.so.6 + 0x27191) #13 0x7f4406a46245 __libc_start_main_impl (libc.so.6 + 0x27245) #14 0x55a874a7f5e1 n/a (kioslave5 + 0x15e1) ELF object binary architecture: AMD x86-64 SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version:
[KScreen] [Bug 461168] On 16:9 4K screen, resolution 1920x1080 not offered under wayland
https://bugs.kde.org/show_bug.cgi?id=461168 --- Comment #6 from Ralf Jung --- Looks like unfortunately this bug is back, but in a worse form: https://bugs.kde.org/show_bug.cgi?id=463655 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463655] New: Cannot select non-native screen resolution under Wayland
https://bugs.kde.org/show_bug.cgi?id=463655 Bug ID: 463655 Summary: Cannot select non-native screen resolution under Wayland Classification: Plasma Product: kwin Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I just updated my KDE (Debian testing) and there is a major regression: I can no longer select 1920x1080 as resolution for my internal screen. In fact I can no longer select any resolution except for the native 4k resolution. This makes the system essentially unusable for me. Things still worked fine (under Wayland) before the update -- not entirely sure which version that was, I think 5.26.3? Basically https://bugs.kde.org/show_bug.cgi?id=461168 is back, but in much worse form since now only the native resolution is available. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.0-6-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462316] Black background after monitors were in standby
https://bugs.kde.org/show_bug.cgi?id=462316 Ralf Jung changed: What|Removed |Added CC||mlud...@logix.net.nz --- Comment #3 from Ralf Jung --- *** Bug 356225 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #417 from Ralf Jung --- *** This bug has been marked as a duplicate of bug 462316 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462280] kwin (wayland) completely freezes when plugging in external screen
https://bugs.kde.org/show_bug.cgi?id=462280 --- Comment #4 from Ralf Jung --- The machine is completely unresponsive at that point. Ctrl-Alt-Backspace does nothing. Ctrl-Alt-F1 (to 12) does nothing. I do not have a 2nd machine I could use to SSH into the laptop. Unless you have some other idea, I don't know how to get a backtrace here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462280] kwin (wayland) completely freezes when plugging in external screen
https://bugs.kde.org/show_bug.cgi?id=462280 Ralf Jung changed: What|Removed |Added Severity|normal |crash --- Comment #1 from Ralf Jung --- In fact this seems to be pretty much reproducible. It only doesn't happen when I go out of fullscreen before plugging in the external screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462280] New: kwin (wayland) completely freezes when plugging in external screen
https://bugs.kde.org/show_bug.cgi?id=462280 Bug ID: 462280 Summary: kwin (wayland) completely freezes when plugging in external screen Classification: Plasma Product: kwin Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I have a dual-GPU-laptop, where external screens are driven by the NVidia GPU. Sometimes when I plug in the external screen while watching a Youtube video full-screen (in Firefox), the entire system just freezes. The sound keeps playing, but the machine becomes entirely unresponsive to inputs. I cannot even switch to a virtual terminal, I have to use SysRq keys to hard-reboot the machine. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-4-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #71 from Ralf Jung --- Interestingly, restarting Plasma is enough to get the desktop back (and usually the panel, too). So it can't just be about the connector names, there seems to be some additional state confusion in plasma that gets resolved on a restart. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #69 from Ralf Jung --- When I just unplugged my external screen, plasma lost my *destop*. It is all black and there's not even a context menu. Is that the same bug or a different issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458156] Notification icon is tilted sometimes
https://bugs.kde.org/show_bug.cgi?id=458156 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de --- Comment #4 from Ralf Jung --- I've also seen this occasionally for at least a year now, both on Wayland and X11 sessions. Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-3-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461860] New: Windows end up on disabled screen
https://bugs.kde.org/show_bug.cgi?id=461860 Bug ID: 461860 Summary: Windows end up on disabled screen Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I use my laptop either with the internal screen, or with an external screen and the internal one disabled. When I switch from internal to external, windows regularly end up on the disabled screen and thus outside the visible area. STEPS TO REPRODUCE I am not entirely sure how to reproduce this, but I usually do something like this: 1. Work with the laptop on the internal screen only. 2. Suspend the laptop. 3. Connect an external screen. 4. Resume the laptop. It is already configured to switch to the external screen and disable the internal one. OBSERVED RESULT Some windows end up outside the visible area. When I activate them from the panel, the animation indicates they are to the right of the external screen. This is where I used to place my internal screen before I decided to disable it instead. EXPECTED RESULT Windows should always be forced into the visible area. In fact I don't quite understand why they are moved out to begin with -- something seems to move them all the way to the right. Maybe this is related to how I used to set up my external screen, where the internal screen was enabled and placed to the right of the external one, and the external one was primary. This is pure speculation though. Obviously since the internal screen is disabled, where it used to be placed when it was enabled should not have any effect, SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-3-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461780] New: Add option to restore tabs upon restart
https://bugs.kde.org/show_bug.cgi?id=461780 Bug ID: 461780 Summary: Add option to restore tabs upon restart Classification: Applications Product: konsole Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY It'd be nice to be able to restart the session or machine without losing the open tabs in Konsole. Most applications (e.g. Dolphin, Firefox) have that feature. In the past, X11 session management served this purpose, but with wayland that is not a thing any more, so it'd be great if Konsole implemented something like this itself. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 141267] wallet password dialog should stay in front
https://bugs.kde.org/show_bug.cgi?id=141267 --- Comment #23 from Ralf Jung --- I regularly have the situation where I don't even notice the wallet prompt opening, and then later I wonder why my wifi does not connect. So I would definitely prefer a full-session modal dialog. This is one of the things that IMO Gnome got right. (And generally, everything security-sensitive needs a full-session modal dialog to ensure that applications cannot fake a window that looks exactly the same. That's why these kinds of dialogs are typically full-session modal on other OSes, too.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461737] New: Cursor image turns to glitch after screen off/on
https://bugs.kde.org/show_bug.cgi?id=461737 Bug ID: 461737 Summary: Cursor image turns to glitch after screen off/on Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- Created attachment 153692 --> https://bugs.kde.org/attachment.cgi?id=153692=edit An image showing the problem (the white square on the right is the cursor) SUMMARY When the screensaver kicks in and then turns off again, the curser on the lockscreen turns into glitches. STEPS TO REPRODUCE 1. Leave the system sitting doing nothing until the screen is locked and turned off. I have "screen locking" configured to lock after 10min, and "energy saving" set to switch off the screen after 10min. 2. Some back to the machine and move the cursor. OBSERVED RESULT The cursor is a big glitchy mess, see screenshot -- it's the white square thing on the right. It stays like that even when moving the mouse. Once I enter my password and unlock, it goes back to normal. EXPECTED RESULT There should be a normal cursor. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION This laptop system has an Intel GPU and an NVidia GPU. The external screen that this happens on is attached to the NVidia GPU. The internal display is turned off. I am using the open-source nouveau drivers. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 141267] wallet password dialog should stay in front
https://bugs.kde.org/show_bug.cgi?id=141267 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de --- Comment #20 from Ralf Jung --- In Gnome, the keyring password dialog is integrated with the entire session: it is not a regular window, but a prompt that blacks out the rest of the screen. I like that since it means I cannot accidentally enter my password somewhere else if weird things happen with the focus. Maybe it'd make sense for KDE to also use that approach? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461698] New: Okular crashes when printing to printer that requires authentication
https://bugs.kde.org/show_bug.cgi?id=461698 Bug ID: 461698 Summary: Okular crashes when printing to printer that requires authentication Classification: Applications Product: okular Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY My employer has a Windows-based printer setup where printing requires me to provide username and password. I have set this up as a Samba printer in CUPS, and when I print from the Gnome Document Viewer, I get a password prompt as expected and things print just fine. However, Okular crashes. STEPS TO REPRODUCE 1. Print anything to a Sambda password-protected printer OBSERVED RESULT Okular just closes when I hit "print" or even just "properties". On the terminal I see 20 -- exe=/usr/bin/okular 17 -- platform=wayland 15 -- appname=okular 17 -- apppath=/usr/bin 10 -- signal=11 11 -- pid=195158 19 -- appversion=22.04.3 19 -- programname=Okular 31 -- bugaddress=sub...@bugs.kde.org 12 -- startupid=0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = okular path = /usr/bin pid = 195158 KCrash: Arguments: /usr/bin/okular 2022 -- Ho, Protzenko -- Aeneas: Rust Verification by Functional Translation.pdf The Wayland connection experienced a fatal error: Bad file descriptor EXPECTED RESULT It should print the document. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461672] New: On a folder symlink, "Link to" shows the name of the link, not where it points
https://bugs.kde.org/show_bug.cgi?id=461672 Bug ID: 461672 Summary: On a folder symlink, "Link to" shows the name of the link, not where it points Classification: Applications Product: dolphin Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: p...@ralfj.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY My `~/Downloads` is a symlink to `~/Desktop` (because some applications don't follow XDG and just always put their stuff in `~/Downloads`). However when I hover over it in Dolphin, it prints in the status bar: "Downloads (folder, link to file:///home/r/Downloads)" which is clearly wrong, it should say "link to file:///home/r/Desktop" SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de --- Comment #66 from Ralf Jung --- https://bugs.kde.org/show_bug.cgi?id=356225 has been marked as a duplicate of this. However that was about a panel not being shown properly on my internal laptop screen, which I don't think changes its identifier? The external screen got unplugged and replugged a few times, but the internal screen just stayed on all the time, and only the internal screen was present when there was no panel shown. So doesn't sound like an issue with ephemeral connector IDs to me? It also didn't reset to default. It just didn't have a panel, which obviously is a pretty bad user experience. Restarting plasma fixed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #415 from Ralf Jung --- To be clear it disappeared when *unplugging* the external screen. There was only the internal screen and no panel in sight anywhere. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 458714] Resolution changes are not properly restored
https://bugs.kde.org/show_bug.cgi?id=458714 --- Comment #2 from Ralf Jung --- I think I had that set? But anyway I am using Wayland now and couldn't reproduce the issue any more. (All I ran into is Plasma losing track of its panel, as usual... but that's another bug, probably https://bugs.kde.org/show_bug.cgi?id=356225 ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Ralf Jung changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #414 from Ralf Jung --- I just reproduced the problem as follows (in a Plasma Wayland session): - Connect an external screen. Configure laptop and external screen to 1600x900 resolution. (saving settings "only for this specific display arrangement) - Unplug external screen. Configure just the internal screen on its own to 2560x1440 resolution. - Now unplug and replug a few times. On the 2nd time, the panel disappeared and I had to kill and restart plasma to get it back. Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461168] On 16:9 4K screen, resolution 1920x1080 not offered under wayland
https://bugs.kde.org/show_bug.cgi?id=461168 --- Comment #5 from Ralf Jung --- Once it is packaged in Debian I can check that, yeah... -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461168] On 16:9 4K screen, resolution 1920x1080 not offered under wayland
https://bugs.kde.org/show_bug.cgi?id=461168 --- Comment #3 from Ralf Jung --- On IRC I was told that this should fix my problem: https://invent.kde.org/plasma/kwin/-/merge_requests/3138. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461172] External screen driven by separate NVIDIA GPU runs with only 30fps under wayland, compared to internal screen run with Intel iGPU
https://bugs.kde.org/show_bug.cgi?id=461172 --- Comment #1 from Ralf Jung --- According to what I was told on IRC, this is likely caused by the GPU-to-GPU copy being done on the CPU, since kwin doesn't have good fallback cases for when there is no perfect match of the buffers (or maybe I misunderstood what was said). I have now switched to the open-source nvidia driver, which fixed the problem. But ideally it should work with the closed-source driver as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461156] kwin locks up with 100% CPU load when external screen gets plugged in
https://bugs.kde.org/show_bug.cgi?id=461156 --- Comment #2 from Ralf Jung --- Yes this started after upgrading to Plasma 5.26.0 from some 5.25.x. I am now using the wayland session and experiencing various problems there -- will file / have filed those as separate bugreports. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461276] kwin_wayland crashes when connecting external screen
https://bugs.kde.org/show_bug.cgi?id=461276 --- Comment #1 from Ralf Jung --- I managed to get this backtrace out of 'coredumpctl debug', I hope it is helpful: #0 KWin::Output::capabilities() const (this=0x0) at ./src/core/output.cpp:159 #1 0x7f3ad15f86d6 in KWaylandServer::DpmsInterface::sendSupported() (this=0x7f3a940079f0) at ./src/wayland/dpms_interface.cpp:138 #2 0x7f3ad15f883d in KWaylandServer::DpmsInterface::DpmsInterface(KWaylandServer::OutputInterface*, wl_resource*) (this=0x7f3a940079f0, output=0x556d89f7dc70, resource=0x556d8a40c3c0) at ./src/wayland/dpms_interface.cpp:83 #3 0x7f3acc631f7a in () at /lib/x86_64-linux-gnu/libffi.so.8 #4 0x7f3acc63140e in () at /lib/x86_64-linux-gnu/libffi.so.8 #5 0x7f3acc631b0d in ffi_call () at /lib/x86_64-linux-gnu/libffi.so.8 #6 0x7f3ace32d981 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0 #7 0x7f3ace328bda in () at /lib/x86_64-linux-gnu/libwayland-server.so.0 #8 0x7f3ace32b89a in wl_event_loop_dispatch () at /lib/x86_64-linux-gnu/libwayland-server.so.0 #9 0x7f3ad15f6545 in KWaylandServer::Display::dispatchEvents() (this=) at ./src/wayland/display.cpp:114 #10 0x7f3acfae8caf in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd30e711f0, r=0x556d88d19e40, this=0x556d89049390) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate(QObject*, int, void**) (sender=0x556d8925e920, signal_index=3, argv=0x7ffd30e711f0) at kernel/qobject.cpp:3919 #12 0x7f3acfae1f4f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x556d8925e920, m=m@entry=0x7f3acfd4c1a0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd30e711f0) at kernel/qobject.cpp:3979 #13 0x7f3acfaebfef in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x556d8925e920, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #14 0x7f3acfaec7f5 in QSocketNotifier::event(QEvent*) (this=0x556d8925e920, e=) at kernel/qsocketnotifier.cpp:302 #15 0x7f3acf162f5e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x556d8925e920, e=0x7ffd30e712f0) at kernel/qapplication.cpp:3637 #16 0x7f3acfab1718 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x556d8925e920, event=0x7ffd30e712f0) at kernel/qcoreapplication.cpp:1064 #17 0x7f3acfb068f3 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x556d88cee610) at kernel/qeventdispatcher_unix.cpp:304 #18 0x7f3acfb06db7 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:511 #19 0x556d877d90cd in () #20 0x7f3acfab019b in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd30e71480, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #21 0x7f3acfab8306 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #22 0x556d876ea154 in () #23 0x7f3ace82920a in __libc_start_call_main (main=main@entry=0x556d876e8870, argc=argc@entry=14, argv=argv@entry=0x7ffd30e71958) at ../sysdeps/nptl/libc_start_call_main.h:58 #24 0x7f3ace8292bc in __libc_start_main_impl (main=0x556d876e8870, argc=14, argv=0x7ffd30e71958, init=, fini=, rtld_fini=, stack_end=0x7ffd30e71948) at ../csu/libc-start.c:389 #25 0x556d876ebb31 in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461276] New: kwin_wayland crashes when connecting external screen
https://bugs.kde.org/show_bug.cgi?id=461276 Bug ID: 461276 Summary: kwin_wayland crashes when connecting external screen Classification: Plasma Product: kwin Version: 5.26.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY When plugging in an external screen to the HDMI connector, kwin crashes or freezes about half the time, taking down the entire session. This HDMI connector is attached to the NVidia dGPU in my laptop; I am using the open-source nouveau drivers for that one. systemd-coredump shows a stacktrace in the logs but I am not sure how to get symbols for that one: Stack trace of thread 2093: #0 0x7f3ad13cbfd0 _ZNK4KWin6Output12capabilitiesEv (libkwin.so.5 + 0x1cbfd0) #1 0x7f3ad15f86d6 _ZN14KWaylandServer13DpmsInterface13sendSupportedEv (libkwin.so.5 + 0x3f86d6) #2 0x7f3ad15f883d _ZN14KWaylandServer13DpmsInterfaceC2EPNS_15OutputInterfaceEP11wl_resource (libkwin.so.5 + 0x3f883d) #3 0x7f3acc631f7a n/a (libffi.so.8 + 0x6f7a) #4 0x7f3acc63140e n/a (libffi.so.8 + 0x640e) #5 0x7f3acc631b0d ffi_call (libffi.so.8 + 0x6b0d) #6 0x7f3ace32d981 n/a (libwayland-server.so.0 + 0xd981) #7 0x7f3ace328bda n/a (libwayland-server.so.0 + 0x8bda) #8 0x7f3ace32b89a wl_event_loop_dispatch (libwayland-server.so.0 + 0xb89a) #9 0x7f3ad15f6545 _ZN14KWaylandServer7Display14dispatchEventsEv (libkwin.so.5 + 0x3f6545) #10 0x7f3acfae8caf _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2e8caf) #11 0x7f3acfaebfef _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2ebfef) #12 0x7f3acfaec7f5 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2ec7f5) #13 0x7f3acf162f5e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f5e) #14 0x7f3acfab1718 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1718) #15 0x7f3acfb068f3 _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 + 0x3068f3) #16 0x7f3acfb06db7 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x306db7) #17 0x556d877d90cd n/a (kwin_wayland + 0x1420cd) #18 0x7f3acfab019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #19 0x7f3acfab8306 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8306) #20 0x556d876ea154 n/a (kwin_wayland + 0x53154) #21 0x7f3ace82920a __libc_start_call_main (libc.so.6 + 0x2920a) #22 0x7f3ace8292bc __libc_start_main_impl (libc.so.6 + 0x292bc) #23 0x556d876ebb31 n/a (kwin_wayland + 0x54b31) SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455021] Tooltip with black window preview when I hover over a task on Wayland
https://bugs.kde.org/show_bug.cgi?id=455021 --- Comment #13 from Ralf Jung --- Ah yes that helps, thanks! It's not entirely smooth though... when the tooltip shows up, it first has no preview, and then after a short while (maybe 0.1-0.3s) the preview appears. It looks better on X11 where the preview appears immediately. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 449948] After kwin_wayland crashes and restarts or is manually restarted, Reboot, shutdown and logout do not work due to ksmserver relying on XWayland which also died and did not come
https://bugs.kde.org/show_bug.cgi?id=449948 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 461173] New: SSH_AUTH_SOCK is not always set in wayland sessions
https://bugs.kde.org/show_bug.cgi?id=461173 Bug ID: 461173 Summary: SSH_AUTH_SOCK is not always set in wayland sessions Classification: Plasma Product: ksmserver Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: p...@ralfj.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When using Konsole in a wayland KDE session and trying to do this with SSH, I encounter this error: "Could not open a connection to your authentication agent." Turns out that the SSH_AUTH_SOCK env var is not set. This used to be always set under X11, but under Wayland that does not always seem to work. I am pretty sure in a previous session I did have working SSH under Wayland, so maybe this is some non-deterministic condition related to the exact order in which services start when the session is brought up. I can see in "systemctl --user status ssh-agent.service" that the agent is running. In the logs I see the following Okt 29 21:41:20 r-thinktop agent-launch[19682]: dbus-update-activation-environment: setting SSH_AUTH_SOCK=/run/user/1000/openssh_agent Okt 29 21:41:20 r-thinktop agent-launch[19682]: dbus-update-activation-environment: setting SSH_AGENT_LAUNCHER=openssh Okt 29 21:41:20 r-thinktop agent-launch[19678]: SSH_AUTH_SOCK=/run/user/1000/openssh_agent; export SSH_AUTH_SOCK; so it seems that somehow those environment variables are supposed to make their way into the session proper, and that does not seem to (always) work. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461172] New: External screen runs with only 30fps under wayland
https://bugs.kde.org/show_bug.cgi?id=461172 Bug ID: 461172 Summary: External screen runs with only 30fps under wayland Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I am trying wayland for the first time on my system, and overall it works pretty well, despite my somewhat annoying multi-GPU setup involving an NVidia GPU. However, things running on the external screen are only running at 30fps: STEPS TO REPRODUCE 1. Run https://git.ralfj.de/gltest.git, or some other way or measuring FPS 2. Move the window between the internal screen of my laptop, and the external screen OBSERVED RESULT On the internal screen it runs with 60fps. On the external screen it runs with 30fps. EXPECTED RESULT It should run with 60fps on all screens. The lower framerate is even noticeable during normal desktop operation. When I start a video game on the external screen, it likewise only achieves 30fps. So I am fairly sure this is not caused by my little gltest program. On my laptop, the internal screen is connected to the Intel GPU, but the HDMI port with the external screen is connected to the NVidia GPU. I have the proprietary Nvidia drivers installed. Remarkably, the external screen just worked without any setup (nice!), but unfortunately there is this problem with the framerate. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461169] New: No window preview under wayland
https://bugs.kde.org/show_bug.cgi?id=461169 Bug ID: 461169 Summary: No window preview under wayland Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de Target Milestone: 1.0 SUMMARY When I start a Plasma wayland session, the task manager tooltips do not show window previews. There's just a big empty area where the preview would go. Previews work fine under X11, and in the alt-tab menu they work even under Wayland. STEPS TO REPRODUCE 1. Open some windows 2. Hover the window entires in the taskbar -- there is no preview OBSERVED RESULT See the attached screenshot. (It doesn't make a difference whether the window is minimized or not.) EXPECTED RESULT There should be a window preview. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461168] New: On 16:9 4K screen, resolution 1920x1080 not offered under wayland
https://bugs.kde.org/show_bug.cgi?id=461168 Bug ID: 461168 Summary: On 16:9 4K screen, resolution 1920x1080 not offered under wayland Classification: Plasma Product: KScreen Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY My laptop has a 4k screen with max resolution of 3840 x 2160. However I usually prefer to run it in full HD resolution, 1920 x 1080. When using an X11 session, kscreen offers to configure the screen with that resolution, but under Wayland it does not -- I can pick 1920 x 1200, or 2560 x 1440, but I cannot select 1920 x 1080. sy SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461156] New: kwin locks up with 100% CPU load when external screen gets plugged in
https://bugs.kde.org/show_bug.cgi?id=461156 Bug ID: 461156 Summary: kwin locks up with 100% CPU load when external screen gets plugged in Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY Each time I plug in my external screen, kwin just freezes up with 100% CPU load. I need to SIGKILL it from a tty (SIGTERM is being ignored), and then somehow get the desktop session to work again. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION This is just the last in a series of crash/freeze/hang bugs that kwin_x11 is suffering from recently. I am not sure if there is something odd about my system or if nobody is using KDE on X11 any more and hence those codepaths are just bitrotting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #8 from Ralf Jung --- This might be related -- today I once had Chromium start with an all-black window (similar to the black square that shows up in the corner right before everything goes down the drain), and then later qgit also started all-black, and since I started qgit from Konsole I saw this qt.qpa.xcb: xcb_shm_create_segment() failed for size 1726740 qt.qpa.xcb: xcb_shm_create_segment() failed for size 8762880 After that everything that wanted to open a new Window just failed. I have 32GB RAM and a lot of it is free. But looks like some resource somewhere gets exhausted and then (unsurprisingly) nothing knows how to deal with that and everything falls apart? Any idea what might cause that allocation to fail? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #7 from Ralf Jung --- This just happened again and I saw a lot of this on the terminal qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 32674, resource id: 98566529, major code: 15 (QueryTree), minor code: 0 kwin_core: XCB error: 152 (BadDamage), sequence: 33939, resource id: 16904766, major code: 143 (DAMAGE), minor code: 3 (Subtract) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59825, resource id: 98566594, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59837, resource id: 98566594, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59838, resource id: 98566594, major code: 18 (ChangeProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59839, resource id: 98566594, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59840, resource id: 98566594, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59841, resource id: 98566594, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59842, resource id: 98566594, major code: 7 (ReparentWindow), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59843, resource id: 98566594, major code: 6 (ChangeSaveSet), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59844, resource id: 98566594, major code: 2 (ChangeWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59845, resource id: 98566594, major code: 10 (UnmapWindow), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11133, resource id: 52428944, major code: 18 (ChangeProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11146, resource id: 52428945, major code: 18 (ChangeProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12989, resource id: 16923763, major code: 149 (Unknown), minor code: 4 kwin_core: XCB error: 136 (Unknown), sequence: 12991, resource id: 16923765, major code: 134 (SYNC), minor code: 17 (DestroyFence) qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12993, resource id: 16923763, major code: 149 (Unknown), minor code: 4 kwin_core: XCB error: 136 (Unknown), sequence: 12995, resource id: 16923766, major code: 134 (SYNC), minor code: 17 (DestroyFence) qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 15410, resource id: 16923935, major code: 149 (Unknown), minor code: 4 kwin_core: XCB error: 136 (Unknown), sequence: 15412, resource id: 16924074, major code: 134 (SYNC), minor code: 17 (DestroyFence) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17050, resource id: 127926442, major code: 15 (QueryTree), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 17081, resource id: 52428946, major code: 18 (ChangeProperty), minor code: 0 kwin_core: XCB error: 152 (BadDamage), sequence: 17139, resource id: 16923805, major code: 143 (DAMAGE), minor code: 3 (Subtract) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20364, resource id: 52428947, major code: 18 (ChangeProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20369, resource id: 52428948, major code: 18 (ChangeProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 22544, resource id: 16925067, major code: 149 (Unknown), minor code: 4 kwin_core: XCB error: 136 (Unknown), sequence: 22546, resource id: 16925069, major code: 134 (SYNC), minor code: 17 (DestroyFence) qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 22548, resource id: 16925067, major code: 149 (Unknown), minor code: 4 kwin_core: XCB error: 136 (Unknown), sequence: 22550, resource id: 16925070, major code: 134 (SYNC), minor code: 17 (DestroyFence) qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 22568, resource id: 16925067, major code: 149 (Unknown), minor code: 4 It seems like some particular client's behavior just really irritates kwin -- I am in a lng Zoom meeting today, which tends to open windows for notifications and things like that, and kwin dies about every hour. Which heavily impedes my ability to participate in the meeting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #6 from Ralf Jung --- I am pretty sure that error occurs after I hit Ctrl-Alt-Backspace. At that point of course the X server is gone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #4 from Ralf Jung --- I am now getting this at least once a day. I wonder what it special about my system that makes this not show up for others, but this is the kind of bug that might force me to use a different DE if I want to keep using my computer productively. If there is something that would help investigate the issue, please let me know. (Though so far it does not look like there is much interest in investigating critical crash issues in kwin...) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459539] New: kwin freeze after window opens while dragging another window
https://bugs.kde.org/show_bug.cgi?id=459539 Bug ID: 459539 Summary: kwin freeze after window opens while dragging another window Classification: Plasma Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I was dragging the main Zoom window to another screen when zoom also opened a notification window telling me about who is the host or something like that, when kwin froze entirely -- I could still move my cursor but no interaction with the system was possible. I had to 'killall -9' kwin to be able to use my system again. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.4 Kernel Version: 5.19.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #3 from Ralf Jung --- It's definitely a KWin problem. When this just happened again, I tried killing plasmashell (using a virtual tty), but the screen remained frozen. Killing kwin with s SIGTERM was just entirely ignored, kwin rept running. Killing kwin with a SIGKILL finally unlocked my session, and after restarting plasma things seem to be running again. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 458714] New: Resolution changes are not properly restored
https://bugs.kde.org/show_bug.cgi?id=458714 Bug ID: 458714 Summary: Resolution changes are not properly restored Product: KScreen Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I have an external screen that, when plugged in, I would like to exactly mirror my internal screen with a 720p resolution. But when it is unplugged, and I use only the internal screen, that should be 1080p. Somehow this does not work and it fails to switch the resolution of my internal screen -- though the exact same thing worked just fine until a week ago with a different screen. STEPS TO REPRODUCE 1. Set up internal screen to 1080p 2. Connect external screen, set both screens to 720p and move them to the same position in the screen configuration 3. Unplug external screen OBSERVED RESULT The internal screen remains at 720p EXPECTED RESULT The internal screen should switch to 1080p. If I switch it to 1080p by hand, then next time I plug in that external screen, *it* is still at 720p but the internal one remains at 1080p, which looks very wrong. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-4-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458708] Plasma lost the panel
https://bugs.kde.org/show_bug.cgi?id=458708 --- Comment #2 from Ralf Jung --- I can pretty much reproduce losing the panel by setting the external screen to be a "replica of" the internal one, and then unplugging. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458708] Plasma lost the panel
https://bugs.kde.org/show_bug.cgi?id=458708 --- Comment #1 from Ralf Jung --- Oh that is great, after some more unplugging and replugging, the old panel now sits at the middle of my laptop screen, with the external screen using a different resolution so it sits properly at the bottom there. Somehow it also doesn't remember to switch the resolution properly when I plug in that external screen (something that used to work fine with another external screen until a week ago)... but I guess that is a separate bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458708] New: Plasma lost the panel
https://bugs.kde.org/show_bug.cgi?id=458708 Bug ID: 458708 Summary: Plasma lost the panel Product: plasmashell Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY After unplugging an external screen, the plasma panel disappeared. Logging out and back in does not help. Looks like I need to re-configure my panel from scratch. STEPS TO REPRODUCE I don't know how to reproduce. All I did is connect an external screen, set it up to mirror the internal screen, set both to a lower resolution, and the unplug the external screen. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-4-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #2 from Ralf Jung --- It might be that the cause of the problem is actually plasma, not kwin -- or at least plasma seems to be tied in here. Sometimes when I see the strange artifact in the bottom right corner, I still manage to alt-tab to a terminal and do `killall plasmashell` -- and that prevents the death of my entire session that would usually follow. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Ralf Jung changed: What|Removed |Added Severity|normal |crash --- Comment #1 from Ralf Jung --- Actually turns out this can happen without vsocde being involved. It just happened while I was just using my webbrowser, not starting any new application. There was still a black square in the bottom right corner though. Maybe that is from a plasma notification? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Ralf Jung changed: What|Removed |Added Summary|kwin becomes unresponsive |kwin becomes unresponsive, |sometimes when starting |need to restart session |vscode | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] New: kwin becomes unresponsive sometimes when starting vscode
https://bugs.kde.org/show_bug.cgi?id=457847 Bug ID: 457847 Summary: kwin becomes unresponsive sometimes when starting vscode Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY I apologize in advance for the vague description. I don't know how to reproduce this issue and I don't know how to diagnose it, so I am down to describing symptoms in the hope that they are recognizable to the developers. It happened twice now in the span of 2 days so it is not just a one-off event. The symptoms are as follows: - I start visual studio code. - It doesn't start properly; the main windows remains mostly grey and the little notification boxes it shows in the bottom right corner are just black - I can keep do one alt-tab and interact with that window just fine - When I do another alt-tab the focus doesn't really go to that window any more - Now I am entirely stuck and nothing I do seems to have any effect. I even tried killing kwin from another terminal, no luck. I have to Ctrl-Alt-Backspace. I checked "journalctl" and found only this: Aug 13 12:54:26 r-thinktop systemd[1904]: Started Visual Studio Code. Aug 13 12:54:26 r-thinktop krunner[355566]: Warning: networking feature is disabled in Firejail configuration file Aug 13 12:54:26 r-thinktop krunner[355566]: Reading profile /etc/firejail/whitelist-common.inc Aug 13 12:54:26 r-thinktop krunner[355566]: Reading profile /etc/firejail/whitelist-common.local Aug 13 12:54:26 r-thinktop krunner[355566]: Parent pid 355566, child pid 355575 Aug 13 12:54:26 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 34689, resource id: 75497860, major code: 18 (ChangeProperty), minor code: 0 Aug 13 12:54:26 r-thinktop krunner[355582]: Child process initialized in 149.98 ms Aug 13 12:54:27 r-thinktop krunner[355614]: [39:0813/125427.287529:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. Aug 13 12:54:27 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 35169, resource id: 17481336, major code: 3 (GetWindowAttributes), minor code: 0 Aug 13 12:54:27 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 35170, resource id: 17481336, major code: 14 (GetGeometry), minor code: 0 Aug 13 12:54:27 r-thinktop krunner[355582]: [main 2022-08-13T16:54:27.406Z] update#setState idle Aug 13 12:54:29 r-thinktop krunner[355582]: [main 2022-08-13T16:54:29.010Z] Starting extension host with pid 124 (fork() took 11 ms). [...] Aug 13 13:00:23 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 1271, resource id: 17494157, major code: 149 (Unknown), minor code: 4 Aug 13 13:00:23 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 136 (Unknown), sequence: 1274, resource id: 17494158, major code: 148 (Unknown), minor code: 1 Aug 13 13:00:23 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 1276, resource id: 17494160, major code: 149 (Unknown), minor code: 4 Aug 13 13:00:23 r-thinktop kwin_x11[218611]: qt.qpa.xcb: QXcbConnection: XCB error: 136 (Unknown), sequence: 1277, resource id: 17494161, major code: 148 (Unknown), minor code: 1 Aug 13 13:01:02 r-thinktop kglobalaccel5[218644]: The X11 connection broke (error 1). Did the X11 server die? Aug 13 13:01:02 r-thinktop kded5[218605]: The X11 connection broke (error 1). Did the X11 server die? Aug 13 13:01:02 r-thinktop ksmserver[218599]: The X11 connection broke (error 1). Did the X11 server die? The "X11 connection broke" are from when I did Ctrl-Alt-Backspace. Before that kwin did show some "XCB error", no idea if those are significant / critical -- but I doubt it, I have similar messages in the log all the time. I am using Debian testing. This started when kwin-x11 got updated from 4:5.24.5-1+b1 to 4:5.25.4-2. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-3-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Manufacturer: LENOVO Product Name: 20ENCTO1WW System Version: ThinkPad P50 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 456253] New: "http://127.0.0.1:4000/" no longer recognized as a single link (including the port)
https://bugs.kde.org/show_bug.cgi?id=456253 Bug ID: 456253 Summary: "http://127.0.0.1:4000/; no longer recognized as a single link (including the port) Product: konsole Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: p...@ralfj.de Target Milestone: --- SUMMARY The string "http://127.0.0.1:4000/; no longer becomes a single clickable link in Konsole. Instead it thinks the link is for "http://127.0.0.1;. STEPS TO REPRODUCE 1. "echo http://127.0.0.1:4000/; 2. Right-click on the link, "Open Link" OBSERVED RESULT It opens "http://127.0.0.1; EXPECTED RESULT It should open "http://127.0.0.1:4000/;. This used to work a few months ago, so I think this is some recent regression. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446581] plasmashell and Firefox hang in QXcbClipboard::waitForClipboardEvent() when Firefox attempts to update the clipboard and show a notification at the same time
https://bugs.kde.org/show_bug.cgi?id=446581 --- Comment #7 from Ralf Jung --- > So perhaps plasmashell and Klipper should be rewritten to not block while > waiting for clipboard contents Blocking the main plasmashell thread sounds like a bad idea in general, since it always risks a freeze of the entire shell. I've experienced clipboard-related freezes in Plasma for around a decade now so it would be amazing to see this fixed at some point. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453562] Plasma freezes when saving an edited image
https://bugs.kde.org/show_bug.cgi?id=453562 --- Comment #7 from Ralf Jung --- Here's a main thread backtrace with some more debug symbols installed: (gdb) bt #0 0x7f0e019ef0fa in __futex_abstimed_wait_common64 (futex_word=futex_word@entry=0x5565f3675134, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7ffeb44b54e0, private=private@entry=0, cancel=cancel@entry=true) at ../sysdeps/nptl/futex-internal.c:74 #1 0x7f0e019ef15b in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5565f3675134, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7ffeb44b54e0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7f0e019e8f44 in __pthread_cond_wait_common (abstime=0x7ffeb44b54e0, clockid=1, mutex=0x5565f36750e0, cond=0x5565f3675108) at pthread_cond_wait.c:504 #3 __pthread_cond_timedwait (cond=0x5565f3675108, mutex=0x5565f36750e0, abstime=0x7ffeb44b54e0) at pthread_cond_wait.c:637 #4 0x7f0e020657a8 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (deadline=..., this=0x5565f36750e0) at thread/qwaitcondition_unix.cpp:136 #5 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x5565f36750e0) at thread/qwaitcondition_unix.cpp:144 #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5565f3658928, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7f0e020658a7 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5565f3658930, mutex=0x5565f3658928, time=) at thread/qwaitcondition_unix.cpp:209 #8 0x7f0dfcf7e673 in QXcbEventQueue::waitForNewEvents(unsigned long) (this=this@entry=0x5565f36588c0, time=163) at ./src/plugins/platforms/xcb/qxcbeventqueue.cpp:360 #9 0x7f0dfcf53a60 in QXcbClipboard::waitForClipboardEvent(unsigned int, int, bool) (this=this@entry=0x5565f36fc3b0, window=window@entry=41943085, type=type@entry=31, checkManager=checkManager@entry=false) at ./src/plugins/platforms/xcb/qxcbclipboard.cpp:809 #10 0x7f0dfcf54149 in QXcbClipboard::getSelection(unsigned int, unsigned int, unsigned int, unsigned int) (this=0x5565f36fc3b0, selection=1, target=380, property=385, time=286955112, time@entry=0) at ./src/plugins/platforms/xcb/qxcbclipboard.cpp:900 #11 0x7f0dfcf55b68 in QXcbClipboard::getDataInFormat(unsigned int, unsigned int) (fmtAtom=, modeAtom=, this=) at ./qxcbatom.h:249 #12 QXcbClipboardMime::formats_sys() const (this=0x5565f5cfd060) at ./src/plugins/platforms/xcb/qxcbclipboard.cpp:100 #13 0x7f0e0263f6bf in QInternalMimeData::formats() const (this=) at kernel/qinternalmimedata.cpp:98 #14 0x7f0d836505fd in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_clipboard.so #15 0x7f0e0227a133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffeb44b5900, r=0x5565f5b8e490, this=0x7f0df8006f20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate(QObject*, int, void**) (sender=0x7f0df8008750, signal_index=3, argv=0x7ffeb44b5900) at kernel/qobject.cpp:3886 #17 0x7f0e013157ee in KSystemClipboard::changed(QClipboard::Mode) () at /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5 #18 0x7f0e0227a133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffeb44b5a10, r=0x7f0df8008750, this=0x5565f5ba3fa0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x5565f3ea9ad0, signal_index=3, argv=0x7ffeb44b5a10) at kernel/qobject.cpp:3886 #20 0x7f0e022735ff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f0e02ba1c20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeb44b5a10) at kernel/qobject.cpp:3946 #21 0x7f0e02a8face in QClipboard::changed(QClipboard::Mode) (this=, _t1=) at .moc/moc_qclipboard.cpp:168 #22 0x7f0e0263016b in QClipboard::emitChanged(QClipboard::Mode) (this=, mode=) at kernel/qclipboard.cpp:608 #23 0x7f0e026121e3 in QPlatformClipboard::emitChanged(QClipboard::Mode) (this=, mode=) at kernel/qplatformclipboard.cpp:125 #24 0x7f0dfcf543a6 in QXcbClipboard::handleXFixesSelectionRequest(xcb_xfixes_selection_notify_event_t*) (this=, event=event@entry=0x7f0df801a460) at ./src/plugins/platforms/xcb/qxcbclipboard.cpp:679 #25 0x7f0dfcf57c74 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x5565f365c420, event=event@entry=0x7f0df801a460) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:685 #26 0x7f0dfcf59186 in QXcbConnection::processXcbEvents(QFlags) (this=0x5565f365c420, flags=...) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:1003 #27 0x7f0dfcf7f573 in xcbSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103 #28 0x7f0e001eff8b in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f0e001f0238 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0
[plasmashell] [Bug 453562] Plasma freezes when saving an edited image
https://bugs.kde.org/show_bug.cgi?id=453562 --- Comment #6 from Ralf Jung --- Created attachment 149516 --> https://bugs.kde.org/attachment.cgi?id=149516=edit 'thread apply all bt' when the freeze happens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453562] Plasma freezes when saving an edited image
https://bugs.kde.org/show_bug.cgi?id=453562 Ralf Jung changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #5 from Ralf Jung --- Okay I think I got a setup that reproduces the problem, and I *think* I captured the right backtrace -- I will add the 'thread apply all bt' as an attachment, but here's the main thread: Thread 1 (Thread 0x7f0dfd3f29c0 (LWP 814183) "plasmashell"): #0 0x7f0e019ef0fa in __futex_abstimed_wait_common64 (futex_word=futex_word@entry=0x5565f3675130, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7ffeb44b54e0, private=private@entry=0, cancel=cancel@entry=true) at ../sysdeps/nptl/futex-internal.c:74 #1 0x7f0e019ef15b in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5565f3675130, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7ffeb44b54e0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7f0e019e8f44 in __pthread_cond_wait_common (abstime=0x7ffeb44b54e0, clockid=1, mutex=0x5565f36750e0, cond=0x5565f3675108) at pthread_cond_wait.c:504 #3 __pthread_cond_timedwait (cond=0x5565f3675108, mutex=0x5565f36750e0, abstime=0x7ffeb44b54e0) at pthread_cond_wait.c:637 #4 0x7f0e020657a8 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (deadline=..., this=0x5565f36750e0) at thread/qwaitcondition_unix.cpp:136 --Type for more, q to quit, c to continue without paging-- #5 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x5565f36750e0) at thread/qwaitcondition_unix.cpp:144 #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5565f3658928, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7f0e020658a7 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5565f3658930, mutex=0x5565f3658928, time=) at thread/qwaitcondition_unix.cpp:209 #8 0x7f0dfcf7e673 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f0dfcf53a60 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7f0dfcf54149 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7f0dfcf55b68 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #12 0x7f0e0263f6bf in QInternalMimeData::formats() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f0d8365040b in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_clipboard.so #14 0x7f0e0227a133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffeb44b5900, r=0x5565f5b8e490, this=0x7f0df8006f20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate(QObject*, int, void**) (sender=0x7f0df8008750, signal_index=3, argv=0x7ffeb44b5900) at kernel/qobject.cpp:3886 #16 0x7f0e013157ee in KSystemClipboard::changed(QClipboard::Mode) () at /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5 #17 0x7f0e0227a133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffeb44b5a10, r=0x7f0df8008750, this=0x5565f5ba3fa0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate(QObject*, int, void**) (sender=0x5565f3ea9ad0, signal_index=3, argv=0x7ffeb44b5a10) at kernel/qobject.cpp:3886 #19 0x7f0e02a8face in QClipboard::changed(QClipboard::Mode) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x7f0dfcf57c74 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x7f0dfcf59186 in QXcbConnection::processXcbEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #22 0x7f0dfcf7f573 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #23 0x7f0e001eff8b in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f0e001f0238 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f0e001f02ef in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f0e0229b104 in QEventDispatcherGlib::processEvents(QFlags) (this=0x5565f3723830, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7f0e022424db in QEventLoop::exec(QFlags) (this=this@entry=0x7ffeb44b5cd0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #28 0x7f0e0224a7b0 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #29 0x5565f1ffa76a in () #30 0x7f0e01bc37fd in __libc_start_main (main=0x5565f1ff9910, argc=1, argv=0x7ffeb44b5f68, init=, fini=, rtld_fini=, stack_end=0x7ffeb44b5f58) at ../csu/libc-start.c:332 #31 0x5565f1ffa88a in () I am not surprised to see the clipboard show up there, the clipboard has caused freezes in Plasma for me for at least the last 10 years across four different laptops. -- You are receiving this mail because: You are watchi
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 --- Comment #27 from Ralf Jung --- I have just observed the crash with 5.24.5 (Debian testing): Application: KWin (kwin_x11), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fda6223a546 in __GI_abort () at abort.c:79 #6 0x7fda55f1831c in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7fda56b861d9 in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7fda560f88a9 in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #9 0x7fda64f03a04 in KWin::WindowThumbnailItem::updateOffscreenTexture() (this=0x56391648aaf0) at ./src/scripting/thumbnailitem.cpp:432 #10 0x7fda633d7133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc2d9820c0, r=0x56391648aaf0, this=0x563916374c80) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate(QObject*, int, void**) (sender=0x563915478b70, signal_index=3, argv=0x7ffc2d9820c0) at kernel/qobject.cpp:3886 #12 0x7fda633d05ff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x563915478b70, m=m@entry=0x7fda650b4c80 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #13 0x7fda64dd5810 in KWin::Scene::frameRendered() (this=this@entry=0x563915478b70) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_scene.cpp:155 #14 0x7fda64ed50cb in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) (this=this@entry=0x563915478b70, damage=..., repaint=..., updateRegion=updateRegion@entry=0x7ffc2d982260, validRegion=validRegion@entry=0x7ffc2d982268, renderLoop=renderLoop@entry=0x7fda58003230, projection=...) at ./src/scene.cpp:282 #15 0x7fda64fad6de in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (this=0x563915478b70, output=0x0, damage=..., toplevels=, renderLoop=0x7fda58003230) at ./src/scenes/opengl/scene_opengl.cpp:259 #16 0x7fda64e26e1e in KWin::Compositor::composite(KWin::RenderLoop*) (this=0x5639151df820, renderLoop=0x7fda58003230) at ./src/composite.cpp:633 #17 0x7fda64e274bb in KWin::X11Compositor::composite(KWin::RenderLoop*) (this=0x5639151df820, renderLoop=0x7fda58003230) at ./src/composite.cpp:844 #18 0x7fda633d7133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc2d982550, r=0x5639151df820, this=0x563915650580) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x7fda58003230, signal_index=5, argv=0x7ffc2d982550) at kernel/qobject.cpp:3886 #20 0x7fda633d05ff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fda650b4d00 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffc2d982550) at kernel/qobject.cpp:3946 #21 0x7fda64dda382 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) (this=, _t1=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206 #22 0x7fda64ec3573 in KWin::RenderLoopPrivate::dispatch() (this=0x563915281860) at ./src/renderloop.cpp:150 #23 0x7fda633d7133 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc2d982670, r=0x7fda58003230, this=0x563915287d90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate(QObject*, int, void**) (sender=0x563915281878, signal_index=3, argv=0x7ffc2d982670) at kernel/qobject.cpp:3886 #25 0x7fda633d05ff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fda6363a2e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc2d982670) at kernel/qobject.cpp:3946 #26 0x7fda633dafda in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #27 0x7fda633ccfff in QObject::event(QEvent*) (this=0x563915281878, e=0x7ffc2d9827f0) at kernel/qobject.cpp:1336 #28 0x7fda629776bf in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x563915281878, e=0x7ffc2d9827f0) at kernel/qapplication.cpp:3632 #29 0x7fda633a0aca in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x563915281878, event=0x7ffc2d9827f0) at kernel/qcoreapplication.cpp:1063 #30 0x7fda633f74ab in QTimerInfoList::activateTimers() (this=this@entry=0x563915010ce8) at kernel/qtimerinfo_unix.cpp:643 #31 0x7fda633f4c6c in QEventDispatcherUNIXPrivate::activateTimers() (this=this@entry=0x563915010c60) at kernel/qeventdispatcher_unix.cpp:249 #32 0x7fda633f59b7 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 #33 0x7fda5cd5e91e in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #34 0x7fda6339f4db in QEventLoop::exec(QFlags) (this=this@entry=0x7ffc2d982990, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/gl
[plasmashell] [Bug 453562] Plasma freezes when saving an edited image
https://bugs.kde.org/show_bug.cgi?id=453562 --- Comment #2 from Ralf Jung --- So how would that go, roughly? Does the following sound right? - attach gdb to plasmashell - trigger the freeze - quickly switch to the gdb console, Ctrl-C, catch a backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360262] Plasmashell and krunner stop responding after copying large text/images to clipboard on X11
https://bugs.kde.org/show_bug.cgi?id=360262 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453562] New: Plasma freezes when saving an edited image
https://bugs.kde.org/show_bug.cgi?id=453562 Bug ID: 453562 Summary: Plasma freezes when saving an edited image Product: plasmashell Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When I sort and edit images I took, I usually have them in a folder on my Desktop. I go over them in Gwenview, and open some of them in Gimp for editing. When I save the image in Gimp and then immediately click the taskbar entry for Gwenview, nothing happens -- Plasma is entirely locked up for a few seconds before it goes back to being responsive. Hitting Alt-Tab to switch back to Gwenview works immediately. STEPS TO REPRODUCE 1. Have a folder on your Desktop (not sure if that part is important) open in Dolphin, and open an image inside that folder with Gwenview. 2. From Gwenview, open Gimp. Edit the image a bit, and hit Ctrl-Shift-E to save it again. 3. Then immediately click on the Gwenview entry in the panel. OBSERVED RESULT Nothing happens for a few seconds -- not the usual hover effect when moving the mouse over the panel, and no window switching. Then after a bit, Gwenview is brought to the front. EXPECTED RESULT Plasma should be responsive as usual. Freezing the desktop shell for a few seconds is a bug. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452587] New: File renaming with newlines does not work very well
https://bugs.kde.org/show_bug.cgi?id=452587 Bug ID: 452587 Summary: File renaming with newlines does not work very well Product: dolphin Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: p...@ralfj.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I often copy-paste the title of a PDF document into the filename so that I can easily tell what the file contains. However, if the title does not fit on a single line in the document (which is most of the time), that inadvertently inserts a newline into the filename that I then have to remove. The Dolphin rename logic does not handle newlines very well (and over the last year, this got worse). STEPS TO REPRODUCE 1. Copy-paste some title with a newline into it into the filename 2. Try to rename the file in dolphin to remove the filename OBSERVED RESULT Only one of the multiple lines is ever actually shown while renaming, the other lines are cut off. Navigating the cursor around this multi-line filename does not work very well. The up/down arrow keys navigate to neighboring files, so to navigate the multiple lines in the filename one has to use just the left/right arrow keys. EXPECTED RESULT I am not sure what the best way to handle this would be. IMO it would make sense to just remove newlines when I Ctrl-V some text into the filename -- one basically never wants a newline in a filename anyway. Alternatively, maybe there is a way to make the file rename mode better support filenames with newlines. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-4-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications
https://bugs.kde.org/show_bug.cgi?id=451612 Ralf Jung changed: What|Removed |Added CC||p...@ralfj.de --- Comment #3 from Ralf Jung --- I am also seeing this with the Debian packages: Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-4-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 Application: KWin (kwin_x11), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fec33251546 in __GI_abort () at abort.c:79 #6 0x7fec2660331c in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7fec27270f79 in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7fec267e38a9 in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #9 0x7fec35f0fa34 in KWin::WindowThumbnailItem::updateOffscreenTexture() (this=0x563bfc044c80) at ./src/scripting/thumbnailitem.cpp:432 #10 0x7fec343ea1b3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcb2a4da30, r=0x563bfc044c80, this=0x563bfc17f070) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate(QObject*, int, void**) (sender=0x563bfb0bd960, signal_index=3, argv=0x7ffcb2a4da30) at kernel/qobject.cpp:3886 #12 0x7fec343e367f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x563bfb0bd960, m=m@entry=0x7fec360c0d20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #13 0x7fec35de1800 in KWin::Scene::frameRendered() (this=this@entry=0x563bfb0bd960) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_scene.cpp:155 #14 0x7fec35ee10fb in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) (this=this@entry=0x563bfb0bd960, damage=..., repaint=..., updateRegion=updateRegion@entry=0x7ffcb2a4dbd0, validRegion=validRegion@entry=0x7ffcb2a4dbd8, renderLoop=renderLoop@entry=0x563bfacef090, projection=...) at ./src/scene.cpp:282 #15 0x7fec35fb902e in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (this=0x563bfb0bd960, output=0x0, damage=..., toplevels=, renderLoop=0x563bfacef090) at ./src/scenes/opengl/scene_opengl.cpp:259 #16 0x7fec35e32e0e in KWin::Compositor::composite(KWin::RenderLoop*) (this=0x563bfaa40f60, renderLoop=0x563bfacef090) at ./src/composite.cpp:633 #17 0x7fec35e334ab in KWin::X11Compositor::composite(KWin::RenderLoop*) (this=0x563bfaa40f60, renderLoop=0x563bfacef090) at ./src/composite.cpp:844 #18 0x7fec343ea1b3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcb2a4dec0, r=0x563bfaa40f60, this=0x563bfaf15260) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x563bfacef090, signal_index=5, argv=0x7ffcb2a4dec0) at kernel/qobject.cpp:3886 #20 0x7fec343e367f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fec360c0da0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb2a4dec0) at kernel/qobject.cpp:3946 #21 0x7fec35de6372 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) (this=, _t1=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206 #22 0x7fec35ecf5a3 in KWin::RenderLoopPrivate::dispatch() (this=0x563bface4e10) at ./src/renderloop.cpp:150 #23 0x7fec343ea1b3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcb2a4dfe0, r=0x563bfacef090, this=0x563bfacf69b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #24 doActivate(QObject*, int, void**) (sender=0x563bface4e28, signal_index=3, argv=0x7ffcb2a4dfe0) at kernel/qobject.cpp:3886 #25 0x7fec343e367f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fec3464d2e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcb2a4dfe0) at kernel/qobject.cpp:3946 #26 0x7fec343ee05a in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #27 0x7fec343e007f in QObject::event(QEvent*) (this=0x563bface4e28, e=0x7ffcb2a4e160) at kernel/qobject.cpp:1336 #28 0x7fec3398b71f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x563bface4e28, e=0x7ffcb2a4e160) at kernel/qapplication.cpp:3632 #29 0x7fec343b3b4a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x563bface4e28, event=0x7ffcb2a4e160) at kernel/qcoreapplication.cpp:1063 #30 0x7fec3440a52b in QTimerInfoList::activateTimers() (this=this@entry=0x563bfaa74ea8) at kernel/qtimerinfo_unix.cpp:643 #3
[plasmashell] [Bug 451898] Notifications randomly switch to the left
https://bugs.kde.org/show_bug.cgi?id=451898 --- Comment #2 from Ralf Jung --- https://bugs.kde.org/show_bug.cgi?id=451811 has been marked as a duplicate, but I will note that I have seen wrong notification positions *only* after screen geometry changes, which seems different from the problem reported here. (But of course there could be a common cause.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451811] New: After screen unplug, notifications show in wrong place
https://bugs.kde.org/show_bug.cgi?id=451811 Bug ID: 451811 Summary: After screen unplug, notifications show in wrong place Product: plasmashell Version: 5.24.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: p...@ralfj.de CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 147679 --> https://bugs.kde.org/attachment.cgi?id=147679=edit A screenshot demonstrating the wrong position of the notification SUMMARY After a screen got unplugged while the machine is suspended, Plasma shows notifications in the wrong spot. STEPS TO REPRODUCE 1. Have an external screen connected, with the internal screen being set up "to the right of" the external one 2. Put machine to sleep, unplug external screen, resume machine 3. Make a notification happen OBSERVED RESULT The notification shows in the wrong spot, it partially clips outside of the visible area and overlaps with the toolbar. (See attached screenshot.) EXPECTED RESULT The notification should show where it usually does: in the bottom right corner, *above* the toolbar. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-4-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P530 ADDITIONAL INFORMATION This seems to be a zombie bug that came back: https://bugs.kde.org/show_bug.cgi?id=373379. This is a regression, the same sequence of actions worked with before the latest KDE/Plasma update (previous I was on 5.22 or 5.23). It's not just notifications, other things like KRunner also show in the wrong spot. Connecting and disconnecting another external screen while the machine runs fixes the problem. So it seems like a bug was introduced recently where Plasma fails to notice screen geometry changes in some situations related to system suspend/resume. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444949] When connecting external primary screen on the left, maximized windows do not move over [regression]
https://bugs.kde.org/show_bug.cgi?id=444949 --- Comment #4 from Ralf Jung --- I am now on plasma-desktop 4:5.24.3-1, kwin-x11 4:5.24.3-1 (Debian packages), and when I just plugged in my external screen the Windows still stayed on the laptop screen. So the bug still seems to be present in that version. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 --- Comment #9 from Ralf Jung --- In my case, kio seems to even lock itself out -- after unplugging and re-plugging my phone, kio-based applications are unable to access it. Also, kio will lock the MTP device even without me using any kio app -- if I want to use another app, I always have to kill the KIO daemon, even if I did not open the phone in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444949] When connecting external primary screen on the left, maximized windows do not move over [regression]
https://bugs.kde.org/show_bug.cgi?id=444949 --- Comment #2 from Ralf Jung --- I'm a bit wary of doing such experiments on my main production system. ;) Is there a live system one could use to test this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444952] Glitch in panel after restarting kwin
https://bugs.kde.org/show_bug.cgi?id=444952 Ralf Jung changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ralf Jung --- > You said you can reproduce this just by restarting KWin? Yes. KWin is sadly crashing fairly regularly since the update (fix is supposed to be in 5.23.1) and the glitches do appear each time that happens. > does it get fixed by restarting plasmashell (`plasmashell --replace`)? Yes, though my restart script looks slightly different: killall plasmashell sleep 0.2 plasmashell & -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353038] Drawing is stuttering
https://bugs.kde.org/show_bug.cgi?id=353038 --- Comment #13 from Ralf Jung --- I have not noticed issues with video playback in a while. Using my test application, I did get a rather stuttering 20fps -- but then after restarting KWin, it is up to 60fps. So it seems like in principle KWin can handle this properly, but sometimes it might get into a degraded state? Not sure how to reproduce this though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444952] Glitch in panel after restarting kwin
https://bugs.kde.org/show_bug.cgi?id=444952 Ralf Jung changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
