[Powerdevil] [Bug 486506] Firefox (Flatpak) does not inhibit power management when playing videos
https://bugs.kde.org/show_bug.cgi?id=486506 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de --- Comment #7 from Jan Rathmann --- I get the same behaviour with the flatpaked version of SameBoy (screen goes black while playing with Gamepad despite SameBoy is listed as "blocking screen locking and suspend" in systray). However, if I watch videos with Freetube (also Flatpak), suspend inhibition works correct (screen stays on). My setup: * Kubuntu 24.04 * self-build Plasma 6.0.90, Frameworks 6.4.0 and Qt 6.7.2 * Wayland session -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486768] [git master] - Open app in Icon Only Task manager use more space than closed app.
https://bugs.kde.org/show_bug.cgi?id=486768 Jan Rathmann changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486768] [git master] - Open app in Icon Only Task manager use more space than closed app.
https://bugs.kde.org/show_bug.cgi?id=486768 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 --- Comment #10 from Jan Rathmann --- (In reply to Rune from comment #9) > This is sadly not fixed. The keyboard navigation does not work after > searching, only after just opening the application dashboard. Strange, the keyboard navigation does still work for me after typing search text. (I run a kdesrc-build from git master.) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485155] Konsole and Konsole KPart crash when using shortcuts with Ctrl
https://bugs.kde.org/show_bug.cgi?id=485155
Jan Rathmann changed:
What|Removed |Added
CC||jan.rathm...@gmx.de
--- Comment #8 from Jan Rathmann ---
In case this is helpful, the following steps always trigger the crash for me:
* Open Konsole
* type in the name of a directory that exists in your working dir
*
hit Shift+Ctrl once
*
hit Shift+Ctrl twice
-> Konsole crashes.
ADDITIONAL INFORMATION
Konsole build from master on 2024-04-07.
Plasma also build from master the same day.
Distro: Kubuntu 23.10
BACKTRACE
Application: Konsole (konsole), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[New LWP 54114]
[New LWP 54116]
[New LWP 54148]
[New LWP 54149]
[New LWP 54141]
[New LWP 54115]
[New LWP 54118]
[New LWP 54117]
[New LWP 54139]
[New LWP 54140]
[New LWP 54119]
[New LWP 54120]
[New LWP 54121]
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.ubuntu.com>
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/home/jan/kde/usr/bin/konsole'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
[Current thread is 1 (Thread 0x785546792a00 (LWP 54114))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x785546792a00 (LWP 54114))]
Thread 13 (Thread 0x785523fff6c0 (LWP 54121)):
#0 0x78554c6940f6 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5e7e04659188) at
./nptl/futex-internal.c:57
#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0,
clockid=0, expected=0, futex_word=0x5e7e04659188) at ./nptl/futex-internal.c:87
#2 __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x5e7e04659188, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
./nptl/futex-internal.c:139
#3 0x78554c696a7e in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x5e7e04659138, cond=0x5e7e04659160) at ./nptl/pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x5e7e04659160, mutex=0x5e7e04659138) at
./nptl/pthread_cond_wait.c:627
#5 0x78553d71ed2d in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6 0x78553d6cf1bb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7 0x78553d71ec5b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8 0x78554c697b5a in start_thread (arg=) at
./nptl/pthread_create.c:444
#9 0x78554c7285fc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 12 (Thread 0x785528dff6c0 (LWP 54120)):
#0 0x78554c6940f6 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5e7e04658fe4) at
./nptl/futex-internal.c:57
#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0,
clockid=0, expected=0, futex_word=0x5e7e04658fe4) at ./nptl/futex-internal.c:87
#2 __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x5e7e04658fe4, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
./nptl/futex-internal.c:139
#3 0x78554c696a7e in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x5e7e04658f90, cond=0x5e7e04658fb8) at ./nptl/pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x5e7e04658fb8, mutex=0x5e7e04658f90) at
./nptl/pthread_cond_wait.c:627
#5 0x78553d71ed2d in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6 0x78553d6cf1bb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7 0x78553d71ec5b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8 0x78554c697b5a in start_thread (arg=) at
./nptl/pthread_create.c:444
#9 0x78554c7285fc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 11 (Thread 0x78553cdfe6c0 (LWP 54119)):
#0 0x78554c6940f6 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5e7e046cda90) at
./nptl/futex-internal.c:57
#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0,
clockid=0, expected=0, futex_word=0x5e7e046cda90) at ./nptl/futex-internal.c:87
#2 __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x5e7e046cda90, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
./nptl/futex-internal.c:139
#3 0x78554c696a7e in __pthread_cond_wait_common (abstime=0x
[plasmashell] [Bug 483773] Panel doesn't autohide if Application Dashboard is invoked via Meta key
https://bugs.kde.org/show_bug.cgi?id=483773 Jan Rathmann changed: What|Removed |Added Blocks||478797 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=478797 [Bug 478797] Metabug: issues with Panel in "Auto-Hide" or "Dodge Windows" modes inappropriately un-hiding in various circumstances -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478797] Metabug: issues with Panel in "Auto-Hide" or "Dodge Windows" modes inappropriately un-hiding in various circumstances
https://bugs.kde.org/show_bug.cgi?id=478797 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de Depends on||483773 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=483773 [Bug 483773] Panel doesn't autohide if Application Dashboard is invoked via Meta key -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483773] New: Panel doesn't autohide if Application Dashboard is invoked via Meta key
https://bugs.kde.org/show_bug.cgi?id=483773 Bug ID: 483773 Summary: Panel doesn't autohide if Application Dashboard is invoked via Meta key Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY If Application Dashboard is used as the app launcher on a panel that is set to auto hide, the panel stays visible if the Application Dashboard is invoked via Meta key (instead of mouse click). STEPS TO REPRODUCE 1. In a fresh session, right click on Kicker icon, "Show alternatives", select Application Dashboard. 2. Right click on panel, "Enter edit mode", set visibility to auto hide. 3. Press Meta key to open the Dashboard. 4. Click on an app icon (e.g. Dolphin). OBSERVED RESULT Panel stays visible and doesn't auto hide anymore. Hovering over the panel with the cursor doesn't change that. EXPECTED RESULT Panel stays hidden until hovered with the cursor. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION * Reproduced with Neon Unstable installation and with OpenSuse Krypton live image. * Happens both on Wayland and X11. * Happens both with floating and non-floating panel. * Does _not_ happen if Application Dashboard is launches via mouse. * On Plasma 6.0 stable this happens sometimes too, but I have found no way to reliably reproduce it there. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard does not open an Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 401863] baloo creates multiple entries for files residing on multi-device btrfs file systems
https://bugs.kde.org/show_bug.cgi?id=401863 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457746] Deleted audio file not removed from index as expected
https://bugs.kde.org/show_bug.cgi?id=457746 Jan Rathmann changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jan.rathm...@gmx.de Status|REPORTED|RESOLVED --- Comment #7 from Jan Rathmann --- *** This bug has been marked as a duplicate of bug 353874 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 353874] Baloo does not remove deleted files from index
https://bugs.kde.org/show_bug.cgi?id=353874 Jan Rathmann changed: What|Removed |Added CC||zalimann...@mail.ru --- Comment #34 from Jan Rathmann --- *** Bug 457746 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 429006] Deleted files are not removed from the index
https://bugs.kde.org/show_bug.cgi?id=429006 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from Jan Rathmann --- *** This bug has been marked as a duplicate of bug 353874 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 353874] Baloo does not remove deleted files from index
https://bugs.kde.org/show_bug.cgi?id=353874 Jan Rathmann changed: What|Removed |Added CC||francogpellegr...@gmail.com --- Comment #33 from Jan Rathmann --- *** Bug 429006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481800] Disabling floating panel leaves empty space at the bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=481800 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Audex] [Bug 481757] New: Slowdown of extraction process due to fetching subchannel infos
https://bugs.kde.org/show_bug.cgi?id=481757
Bug ID: 481757
Summary: Slowdown of extraction process due to fetching
subchannel infos
Classification: Applications
Product: Audex
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: c...@carlschwan.eu
Reporter: jan.rathm...@gmx.de
Target Milestone: ---
SUMMARY
The following commit makes Audex reading subchannel infos at start (or end?) of
every audio track ("Fetching extra information from disc...") during
extraction, causing the process to stall for ~20-30 seconds per track:
https://invent.kde.org/multimedia/audex/-/commit/f3da7ab976b241e5784a9c4861828578dd80c8c5
* Add MCN and ISRC placeholders
* Some code consistency fixes
* Show more device capabilities on device widget
STEPS TO REPRODUCE
1. Start audio extraction (I have paranoia mode enabled.)
2. Watch messages of extraction process in its window.
OBSERVED RESULT
At change between tracks, there is the message "Fetching extra information from
disc...", the process stalls for ~20-30 sec. while CD drive is making busy
sounds.
EXPECTED RESULT
For me the previous behaviour (direct continuation of the extraction process
between tracks without the subchannel info fetching) is more desireable.
I'm not sure if those subchannel infos that Audex fetches have any purpose at
all for my use case (converting audio discs to track-by-track flac files). If
the subchannel infos are not related to the integrity/quality of the actual
audio data, a setting to enable/disable fetching subchannel infos would be
really useful for me!
ADDITIONAL INFORMATION
My drive (information from Audex Device Settings:)
Vendor: HL-DT-ST (imprint says "LG")
Model: DVDRAM GH24NS95
Revision: RN00
Tested with kdesrc builds of Audex and Plasma 6.0 on Ubuntu 23.10.
--
You are receiving this mail because:
You are watching all bug changes.
[Audex] [Bug 481754] New: Commit 4cc41059cfa9fe6660597a054014ee172ca36397 significantly slows down extraction process
https://bugs.kde.org/show_bug.cgi?id=481754 Bug ID: 481754 Summary: Commit 4cc41059cfa9fe6660597a054014ee172ca36397 significantly slows down extraction process Classification: Applications Product: Audex Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: General Assignee: c...@carlschwan.eu Reporter: jan.rathm...@gmx.de Target Milestone: --- SUMMARY The following commit makes audio extraction twice as slow for me as before: https://invent.kde.org/multimedia/audex/-/commit/4cc41059cfa9fe6660597a054014ee172ca36397 * Remove mutex from CDIO class * Add tooltip to write MCN/ISRC checkbox * Respect drive capabilities in CDIO * Apply better error handling in ripping process * Apply some minor code changes in CDDA model STEPS TO REPRODUCE 1. Enable "Device settings -> Full paranoia mode", disable "Skip reading errors" 2. Start ripping. OBSERVED RESULT Ripping of my example CD takes ~28 min. (play time: ~ 77 min.) EXPECTED RESULT Ripping of my example CD would take ~14 min. as before (with same paranoia settings). ADDITIONAL INFOMARTION: My drive (information from Audex Device Settings:) Vendor: HL-DT-ST (imprint says "LG") Model: DVDRAM GH24NS95 Revision: RN00 Tested with kdesrc builds of Audex and Plasma 6.0 on Ubuntu 23.10. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480982] Dolphin icon color stopped respect accent color (in Taskbar)
https://bugs.kde.org/show_bug.cgi?id=480982 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480012] crashing after searching in keyboard->shortcuts
https://bugs.kde.org/show_bug.cgi?id=480012 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 --- Comment #1 from Jan Rathmann --- Created attachment 165564 --> https://bugs.kde.org/attachment.cgi?id=165564=edit Workaround that makes launching apps via Enter key work again Was debugging this for some hours during the last weeks, but still it isn't clear to me was exactly causes this bug or what would work to fix it. It seems it might be related to some change between Qt5 and Qt6, or some change to applets behaviour between P5 and P6. I would need a lot more experience in QML and Plasma applet development to make any progress on this, I guess. Anyway, I found a workaround to make at least launching apps via Enter key work again. I have attached the respecting patch, but I'm really unsure if this is the way it should be implemented (that's why I didn't make a merge request). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370964] "Auto-Hide" mode does not work when using "Switch desktop on edge > Always enabled" setting
https://bugs.kde.org/show_bug.cgi?id=370964 Jan Rathmann changed: What|Removed |Added Version|5.7.5 |5.92.0 CC||jan.rathm...@gmx.de Keywords||qt6 --- Comment #12 from Jan Rathmann --- In Plasma 6.0 it is a bit better in that regard that an additional step is neccessary to trigger the problem: STEPS TO REPRODUCE 1. In a fresh session (with one panel at bottom), start Systemsettings. 2. Go to "Window Management -> Virtual Desktops", change number of rows to 2 and then add a second virtual desktop to the second row. 3. Go to "Mouse & Touchpad -> Screen Edges" and set "Switch desktop on edges" to "Only when moving windows " 4. Right click on panel, "Enter edit mode", set panel visibility to auto-hide. 5. Auto-hide now seems to work as expected at first glance. 6. Move a non-maximized window so that it's border touches the bottom screen edge. ACTUAL RESULT The panel stays hidden and cannot be revealed by hovering the bottom screen edge with the cursor. A workaround to reveal it again is to press the Meta key to open the Application menu. EXPECTED RESULT The panel can still be simply revealed by mouse cursor. ADDITIONAL INFORMATION * With only 1 row of (at least 2) virtual desktops, it can be triggered in a similar way when the panel is on the right screen side. * Seems to independent of Wayland/X11. * Reproduced with self-build Plasma 6.0 and on Neon Unstable with current updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478923] On Wayland, floating panel becomes non-responsive after moving it to a screen edge that causes it to de-float after Edit Mode is exited, until it is touched by a window to m
https://bugs.kde.org/show_bug.cgi?id=478923 --- Comment #7 from Jan Rathmann --- With todays build (and also in my Neon VM with todays updates) I now can reproduce it again – both Nate's steps from #5 and mine from the bug description lead to a non-responsive panel. I can also confirm that the panel becomes responsive again when it is touched with a window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478923] On Wayland, floating panel becomes non-responsive after moving it to a screen edge that causes it to de-float after Edit Mode is exited, until it is touched by a window to m
https://bugs.kde.org/show_bug.cgi?id=478923 --- Comment #6 from Jan Rathmann --- (In reply to Nate Graham from comment #5) > I just found a 100% reliable way to reproduce this issue: > Weird, I can't reproduce it anywhere when replicating your steps (with updates/build from today)... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478923] Floating panel becomes non-responsive after moving it to top or bottom on Wayland
https://bugs.kde.org/show_bug.cgi?id=478923 Jan Rathmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Jan Rathmann --- With latest updates on Neon/openSuse and with an updated build of Plasma 6.0, I can't reproduce the panel freezing anymore, too – it seems it has been getting fixed silently :-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477431] Slightly jumpy scrolling when scrolling through sidebar by slowly dragging the scroll handle
https://bugs.kde.org/show_bug.cgi?id=477431 Jan Rathmann changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from Jan Rathmann --- (In reply to Nate Graham from comment #6) > Cannot reproduce anymore with either 200% or 225% scale. Some patches went > in to better pixel-align things, so I suspect they fixed it! Strange, can still reproduce it – in a VM (Neon Unstable) and on bare HW (self-build Plasma 6.0). Changing scale to 200% doesn't make a difference for me (my default is 100%). Using a different mouse doesn't change anything either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478923] Floating panel becomes non-responsive after moving it to top or bottom on Wayland
https://bugs.kde.org/show_bug.cgi?id=478923 --- Comment #2 from Jan Rathmann --- Created attachment 164827 --> https://bugs.kde.org/attachment.cgi?id=164827=edit Screen recording of the reproduction steps (In reply to Nate Graham from comment #1) > Cannot reproduce myself with those steps. Reminds me of Bug 469016, though. > I have an Intel GPU; what GPU are you using? > > And could you attach a screen recording of it happening so I know I'm > testing properly? > > Also would be good to check if it still happens in Plasma 6 RC1. My GPU vendor is AMD (AMD Ryzen 5700G APU). But I can also reproduce on a Gnome Boxes VM with no HW acceleration. I have just updated my Neon Unstable VM to see if anything has changed - it unfortunately hasn't. Here is a screen recording of the reproduction steps. Notice how the panel doesn't react neither to hovering nor clicking before running 'plasmashell --replace'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479429] Plasmashell crashes when panel contains a widget that has a second PlasmoidItem outside of main.qml
https://bugs.kde.org/show_bug.cgi?id=479429 --- Comment #1 from Jan Rathmann --- Created attachment 164688 --> https://bugs.kde.org/attachment.cgi?id=164688=edit Crashmoid: Minimal test case widget to trigger the crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479429] New: Plasmashell crashes when panel contains a widget that has a second PlasmoidItem outside of main.qml
https://bugs.kde.org/show_bug.cgi?id=479429 Bug ID: 479429 Summary: Plasmashell crashes when panel contains a widget that has a second PlasmoidItem outside of main.qml Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: 1.0 Application: plasmashell (5.91.90) Qt Version: 6.6.1 Frameworks Version: 5.248.0 Operating System: Linux 6.2.0-39-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.91.90 [CoredumpBackend] -- Information about the crash: STEPS TO REPRODUCE 1. Copy minimal test case widget "Crashmoid" (attached) to ~/.local/share/plasma/plasmoids 2. Right-click on panel, Add widget, and add it. 3. Likely nothing particular will happen so far. 4. Log out, and log in again. OBSERVED RESULTS Plasmashell will crash repeatedly and is unable to start. It will start again if the widgets dir under ~/.local/share/plasma/plasmoids gets removed. ADDITIONAL INFORMATION It seems that this crash is caused by the definition of a second PlasmoidItem in a different QML file than main.qml. This can happen if someone (like me ;-) ) misinterprets the Plasma 6 Porting Guide in that way that every QML of a widget _must_ contain a PlasmoidItem at top. Could be reproduced on: * Plasma 6 and Qt 6.6.2 build with kdesrc on Kubuntu 23.10 * Two Neon unstable installations (one in a VM, one bare HW). * openSuse Krypton live image in a VM * Qt 6.6.1 and Qt 6.6.2 The attached backtrace is from Neon Unstable. The crash can be reproduced every time. -- Backtrace: Application: plasmashell (plasmashell), signal: Aborted [New LWP 4043] [New LWP 4069] [New LWP 4064] [New LWP 4063] [New LWP 4073] [New LWP 4072] [New LWP 4061] [New LWP 4083] [New LWP 4084] [New LWP 4099] [New LWP 4070] [New LWP 4183] [New LWP 4182] [New LWP 4190] [New LWP 4192] [New LWP 4372] [New LWP 4193] [New LWP 4242] [New LWP 4194] [New LWP 4363] [New LWP 4370] [New LWP 4191] [New LWP 4364] [New LWP 4375] [New LWP 4376] [New LWP 4377] [New LWP 4371] [New LWP 4373] [New LWP 4365] [New LWP 4374] This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/: Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140520492640960) at ./nptl/pthread_kill.c:44 [Current thread is 1 (Thread 0x7fcd7a0c2ac0 (LWP 4043))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x7fcd7a0c2ac0 (LWP 4043))] Thread 30 (Thread 0x7fccf13fc640 (LWP 4374)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fccf13fb970, op=137, expected=0, futex_word=0x559102103b84) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x7fccf13fb970, clockid=560, expected=0, futex_word=0x559102103b84) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x559102103b84, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7fccf13fb970, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7fcd7e093e9b in __pthread_cond_wait_common (abstime=0x7fccf13fb970, clockid=1, mutex=0x559102103b30, cond=0x559102103b58) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x559102103b58, mutex=0x559102103b30, abstime=0x7fccf13fb970) at ./nptl/pthread_cond_wait.c:652 #5 0x7fcd7eb646f7 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (deadline=..., this=0x559102103b30) at ./src/corelib/thread/qwaitcondition_unix.cpp:93 #6 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x559102103b30) at ./src/corelib/thread/qwaitcondition_unix.cpp:101 #7 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x559101d85958, deadline=...) at ./src/corelib/thread/qwaitcondition_unix.cpp:181 #8 0x7fcd7eb5fcb9 in QThreadPoolThread::run() (this=0x5591021039f0) at ./src/corelib/thread/qthreadpool.cpp:114 #9 0x7fcd7eb5f6ed in operator() (__closure=) at ./src/corelib/thread/qthread_unix.cpp:324 #10 (anonymous namespace)::terminate_on_exception > (t=) at ./src/corelib/thread/qthread_unix.cpp:260 #11 QThreadPrivate::start(void*) (arg=0x5591021039f0) at ./src/corelib/thread/qthread_unix.cpp:283 #12 0x7fcd7e094ac3 in start_thread (arg=) at
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478923] New: Floating panel becomes non-responsive after moving it to top or bottom on Wayland
https://bugs.kde.org/show_bug.cgi?id=478923 Bug ID: 478923 Summary: Floating panel becomes non-responsive after moving it to top or bottom on Wayland Classification: Plasma Product: plasmashell Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6, wayland Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY A floating panel will become completely unresponsive if it is moved to the top (or bottom) in the Wayland session. STEPS TO REPRODUCE 1. Start Wayland session. 2. Have a floating panel (like the default one). 3. Right-click, "Enter edit mode..." 4. Set position to top. 5. Exit edit mode. OBSERVED RESULT The panel doesn't respond to clicks or mouse hover anymore. The only reliable way to make it usable again seems to be 'plasmashell --replace'. EXPECTED RESULT The panel stays a friendly thing that you can interact with :) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.91 KDE Frameworks Version: 5.248 Qt Version: 6.6.1 ADDITIONAL INFORMATION * X11 session seems not affected. * Moving the panel from top to bottom has the same effect (becoming unresponsive). * Moving the panel to left or right seems _not_ to be affected. * If the panel is solid (non-floating), the unresponsiveness doesn't seem to happen. * Reproduced on Neon Unstable and in a VM with openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] New: Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Bug ID: 478620 Summary: Mouse navigation with numpad doesn't work under Wayland Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6, wayland Severity: normal Priority: NOR Component: kcm_accessibility Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- SUMMARY Using the numpad to move the mouse cursor currently doesn't work in the Wayland session. STEPS TO REPRODUCE 1. Start P6 Wayland session 2. Go to Systemsettings -> Accessibility -> Mouse Navigation 3. Check "Use number pad to move cursor" 4. Try to move the cursor with the numpad OBSERVED RESULT Nothing happens when pressing numpad keys to move the cursor. EXPECTED RESULT Cursor should move when pressing numpad keys. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 ADDITIONAL INFORMATION Reproduced with Neon Unstable installation and openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478473] New: Panel configuration popup can easily be covered by other configuration popups and vanishes just by moving cursor
https://bugs.kde.org/show_bug.cgi?id=478473 Bug ID: 478473 Summary: Panel configuration popup can easily be covered by other configuration popups and vanishes just by moving cursor Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 164136 --> https://bugs.kde.org/attachment.cgi?id=164136=edit Screen recording showing the panel popup behaviour SUMMARY When right-clicking, "Enter edit mode", the Panel configuration popup can be very prone to be inaccessible due to being covered by configuration popups of widgets on that panel, e.g. task manager widget. Furthermore, in this state of being covered, the Panel config popup will vanish when just moving the cursor. This is easy to trigger especially when the panel is in auto-hide or dodge mode. (See attached screen recording) STEPS TO REPRODUCE 1. Right click on the large empty space of the default panel, "Enter edit mode..." (Wayland session) 2. Panel configuration popup appears 3. When your panel is set to "always visible", move the cursor over the panel. (When your panel is set to "auto hide" or "dodge windows" this is likely not necessary.) OBSERVED RESULT A big Task manager configuration popup covers the Panel config popup. * If you now move the cursor a bit, the Panel config popup will vanish completely after ~1-3 seconds. * If you then right-click on the panel again, "Leave edit mode", the edit mode will not be left, but instead the Panel config popup re-appears again! (To leave edit mode, click close button on the top-screen "Edit mode popup".) * If you actually want to access the Panel config popup when covered with another popup, left-clicking on one of the visible (=not covered) parts of the Panel config popup makes it stay at the top. But you need to fast (or at least not to slow) to do that click, otherwise the popup will vanish like described above! EXPECTED RESULT * The Panel configuration popup doesn't get covered by other popups. * It does not vanish just by moving the cursor. * Right-clicking on the panel, "Leave edit mode" will actually leave the edit mode. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 ADDITIONAL INFORMATION * The description above is based on the behaviour on Wayland. On X11 it is very similar, with the only(?) difference being that the Task manager config popup is much smaller and thus it is easier to see/reach the partly covered Panel config popup (what makes the bug a bit less obvious). * Reproduced on Neon Unstable installation and a VM with openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 478472] New: When searching, result is cluttered by empty categories
https://bugs.kde.org/show_bug.cgi?id=478472 Bug ID: 478472 Summary: When searching, result is cluttered by empty categories Classification: Plasma Product: kdeplasma-addons Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- Created attachment 164135 --> https://bugs.kde.org/attachment.cgi?id=164135=edit Screen recording of the steps to reproduce SUMMARY When searching in the Application Dashboard, the search result shows all possible categories even though they don't contain any search result. What makes this especially problematic is that actual search results can get "hidden" by the empty categories and can only be seen by scrolling down. (see attached screen recording) STEPS TO REPRODUCE 1. Open Application Dashboard 2. Type something like Kate or Konsole to search OBSERVED RESULT Beside search results, lots of empty categories are shown. One maybe needs to scroll to down to see all actual ssearch results. EXPECTED RESULT Only search results are shown (that's the case in the P5 version of the Dashboard). SOFTWARE/OS VERSIONS KDE Plasma Version: 5.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 ADDITIONAL INFORMATION Reproduced on up-to-date Neon Unstable installation and a VM with openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478432] New: Panel in dodge mode covers the "Edit mode popup" when placed at top
https://bugs.kde.org/show_bug.cgi?id=478432 Bug ID: 478432 Summary: Panel in dodge mode covers the "Edit mode popup" when placed at top Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 164108 --> https://bugs.kde.org/attachment.cgi?id=164108=edit Screen recording of the steps to reproduce SUMMARY If the panel is in dodge mode and placed at the top of the screen, it covers the "Edit mode popup" when in edit mode. (see attached screen recording) STEPS TO REPRODUCE 1. Right click on default panel, "Enter edit mode.." 2. Set panel visibility to dodge mode 3. Set panel position to top OBSERVED RESULT The "Edit mode popup" is now almost fully covered by the panel and cannot be accessed anymore. (To leave edit mode, you can right click on desktop, "Leave edit mode".) EXPECTED RESULT The "Edit mode popup" is still visible and can be accessed to e.g. leave the edit mode. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 ADDITIONAL INFORMATION Independent of Wayland/X11. Reproduced on up-to-date Neon Unstable installation and in a VM with openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477998] New: Glitches on tooltip animations for systray and task list items when hovering with mouse
https://bugs.kde.org/show_bug.cgi?id=477998 Bug ID: 477998 Summary: Glitches on tooltip animations for systray and task list items when hovering with mouse Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 163821 --> https://bugs.kde.org/attachment.cgi?id=163821=edit Screen recording of animation glitches SUMMARY When moving with the mouse over the systray entries in the panel (or task list entries), the tooltip animations look a bit distorted/glitchy (see screen recording). STEPS TO REPRODUCE 1. On a panel with systray and/or task list, move over the items with the mouse. OBSERVED RESULT Animations of the appearing/disappearing toolstips look glitchy (see screen recording). EXPECTED RESULT Animations look elegant and clean. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.90 KDE Frameworks Version: 5.246 Qt Version: 6.6.1 ADDITIONAL INFORMATION * Reproduced on Neon Unstable installation and openSuse Krypton live image. * Independent of running under Wayland/X11 * Didn't see those glitches on my Plasma 5 system. * Relevant HW of my sytem: AMD Ryzen 7 5700G with integrated graphics (without additional graphics HW). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477431] Animation glitches when scrolling through category list with grabbed scrollbar
https://bugs.kde.org/show_bug.cgi?id=477431 --- Comment #3 from Jan Rathmann --- Created attachment 163536 --> https://bugs.kde.org/attachment.cgi?id=163536=edit Video of the glitches Ok, added a screencast showing the glitches. I forgot to mention, this is something new in Plasma 6 (the animation looks fine in Plasma 5). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477431] Animation glitches when scrolling through category list with grabbed scrollbar
https://bugs.kde.org/show_bug.cgi?id=477431 --- Comment #1 from Jan Rathmann --- Seems independent of running Wayland or X11. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477431] New: Animation glitches when scrolling through category list with grabbed scrollbar
https://bugs.kde.org/show_bug.cgi?id=477431 Bug ID: 477431 Summary: Animation glitches when scrolling through category list with grabbed scrollbar Classification: Applications Product: systemsettings Version: 5.27.80 Platform: Neon OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- STEPS TO REPRODUCE 1. Open Systemsettings. 2. Grab the scrollbar of the category list with your mouse (keep left button pressed). 3. Move slowly up or down. OBSERVED RESULT The category items "jump" up and down a tiny bit while scrolling, which looks a bit glitchy. EXPECTED RESULT No glitches during scrolling. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.81 KDE Frameworks Version: 5.245 Qt Version: 6.6.0 ADDITIONAL INFORMATION Best visible when running on real HW, but I see it also in a VM. Tested under Neon Unstable and openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] New: Plasma 6 Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 Bug ID: 477348 Summary: Plasma 6 Application Dashboard: Can't select items via keyboard after searching Classification: Plasma Product: kdeplasma-addons Version: 5.27.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- SUMMARY In the Plasma 6 version of the Application Dashboard, it's impossible to select or change between items after entering a search term. STEPS TO REPRODUCE 1. Open Dashboard. 2. Enter some letters as a search term. 3. Try to select an item by pressing Arrow-down or Tab. OBSERVED RESULT Keyboard focus stays in the search field. No item gets selected. When pressing Arrow-down, nothing happens. When pressing Tab, the search term is expanded by a tab character. (Pressing Enter adds a line-break, which also looks funny ;-) ) EXPECTED RESULT Pressing Arrow-down should navigate you downwards through the items, pressing Tab should navigate you through the first items of each section. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.81 KDE Frameworks Version: 5.245 Qt Version: 6.6.0 ADDITIONAL INFORMATION * Independent of Wayland/X11. * Reproduced in Neon Unstable installation and VM with openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477087] Application Dashboard widget not available
https://bugs.kde.org/show_bug.cgi?id=477087 --- Comment #2 from Jan Rathmann --- Ok, I finally found the reason: The package plasma-widgets-addons isn't installed by default on Neon Unstable. If I install it manually, I get the Application Dashboard. Should this be changed? Neon User apparently has that package installed by default. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477087] Application Dashboard widget not available
https://bugs.kde.org/show_bug.cgi?id=477087 --- Comment #1 from Jan Rathmann --- Did a cross-check: On openSuse Krypton live image with Plasma 6 the Application Dashboard is there and works. So I suspect that its absence in Neon may be due to some packaging issue. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477087] Application Dashboard widget not available
https://bugs.kde.org/show_bug.cgi?id=477087 Jan Rathmann changed: What|Removed |Added Summary|Application Dashboard |Application Dashboard |widget not avaiable |widget not available -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477087] New: Application Dashboard widget not avaiable
https://bugs.kde.org/show_bug.cgi?id=477087 Bug ID: 477087 Summary: Application Dashboard widget not avaiable Classification: KDE Neon Product: neon Version: unspecified Platform: Neon URL: https://invent.kde.org/plasma/plasma-desktop/-/merge_r equests/1704#note_809178 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: jan.rathm...@gmx.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY The Application Dashboard widget is currently not avaiable in Neon Unstable with P6. STEPS TO REPRODUCE 1. Start Neon Unstable live image. 2a. Right-click on Application launcher icon on panel, select "Show alternatives..." OR 2b. Right-click on panel, "Add widget..." OBSERVED RESULT No entry for Application Dashboard. EXPECTED RESULT I can find and select the Application Dashboard. However the following files belonging to the A.D. still exist (like in Plasma 5): /usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/DashboardRepresentation.qml /usr/share/plasma/plasmoids/org.kde.plasma.kickerdash/metadata.json SOFTWARE/OS VERSIONS Neon Unstable 20231113-1400 ADDITIONAL INFORMATION Not a recent regression (reproducible since > 1 month). Further information in URL above. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755
https://bugs.kde.org/show_bug.cgi?id=103788 --- Comment #30 from Jan Rathmann --- Here's a Qt bug report, but it's only for X11: https://bugreports.qt.io/browse/QTBUG-8 (It doesn't work on Wayland either. Haven't found a report for Wayland in the Qt bug tracker.) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755
https://bugs.kde.org/show_bug.cgi?id=103788 --- Comment #29 from Jan Rathmann --- (In reply to Nate Graham from comment #28) > Can someone explain in plain English what exactly is being requested here? > I'm not understanding what needs to be done to support it, because it isn't > clear to me what the feature is. Thanks! The feature is to be able to insert arbitrary unicode characters in text fields (or a text editor) by pressing Ctrl+Shift+u and then the hexadecimal number of the unicode character. Example: Ctrl+Shift+u + 1F600 will give you the emoji . You can test it in Firefox or other GTK-based applications. More details on https://en.wikipedia.org/wiki/Unicode_input (Note: The article claims that it is supported by Qt applications on Linux, what doesn't seem to be correct) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755
https://bugs.kde.org/show_bug.cgi?id=103788 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- --- Comment #26 from Jan Rathmann --- Reopening. Verified that entering unicode chars (in Kate) still doesn't work currently on Kubunu 23.10 (Plasma 5.27.8) and Neon Unstable (Plasma 6). If it is not on Qt's side to implement this (as Christoph tells in #22), which component would be correct to assign this bug? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755
https://bugs.kde.org/show_bug.cgi?id=103788 Jan Rathmann changed: What|Removed |Added CC||ekotekbi...@gmail.com --- Comment #25 from Jan Rathmann --- *** Bug 443543 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443543] Unicode/XCompose input characters doesn't work
https://bugs.kde.org/show_bug.cgi?id=443543 Jan Rathmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||jan.rathm...@gmx.de --- Comment #1 from Jan Rathmann --- *** This bug has been marked as a duplicate of bug 103788 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461741] Panel in "Auto-hide" mode inappropriately un-hides after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=461741 Jan Rathmann changed: What|Removed |Added CC|jan.rathm...@gmx.de | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474699] New: Wayland: Panel needs a mouse hover to auto hide again after suspend
https://bugs.kde.org/show_bug.cgi?id=474699 Bug ID: 474699 Summary: Wayland: Panel needs a mouse hover to auto hide again after suspend Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Flags: X11- SUMMARY On Wayland, if I set the panel to auto hide, it is shown after resuming from suspend until I hover it with the mouse cursor for one time. STEPS TO REPRODUCE 1. Start a Wayland session. 2. Set panel to auto hide. (Panel is hidden.) 3. Suspend system. 4. Resume. 5. If lock screen is enabled, enter password. OBSERVED RESULT Panel is shown allthough it is set to auto hide. Needs one mouse hover to resume auto hiding. EXPECTED RESULT Panel is hidden when set to auto hide, as in X11 session. SOFTWARE/OS VERSIONS OS/Kernel: Neon Unstable 6.2.0-32-generic KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240 Qt Version: 6.6.0 ADDITIONAL INFORMATION Tested with fresh user account on Neon Unstable with Plasma 6, and on Kubuntu 23.04 with Plasma 5.27.8 Commented first on #461741, was adviced to fill a new bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461741] Panel in "Auto-hide" mode inappropriately un-hides after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=461741 Jan Rathmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=474699 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460840] KWin doesn't respect sub-pixel rendering setting for window titles
https://bugs.kde.org/show_bug.cgi?id=460840 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468923] New: Changing default font is not remembered after restart
https://bugs.kde.org/show_bug.cgi?id=468923 Bug ID: 468923 Summary: Changing default font is not remembered after restart Classification: Applications Product: Arianna Version: 1.0.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: c...@carlschwan.eu Reporter: jan.rathm...@gmx.de Target Milestone: --- STEPS TO REPRODUCE 1. Open Arianna 2. In Settings, change default font to something else than 'serif' 3. Load a book to see that it is now rendered with the selected font 4. Close Arianna 5. Load a book again. OBSERVED RESULT Book is rendered with the default font (serif). In Settings, the default font was set back to 'serif'. EXPECTED RESULT The default font selected in Settings before should still be there after restarting Arianna. SOFTWARE/OS VERSIONS Arianna 1.01 Flatpak version from Flathub Kubuntu 23.04 (Plasma 5.27.4, Frameworks 5.104, Qt 5.15.8) ADDITIONAL INFORMATION Verified that I can reproduce the bug in a clean environment (booting Kubuntu 23.04 live image). Kind regards, Jan -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467426] Often wrong window preview shown on hover
https://bugs.kde.org/show_bug.cgi?id=467426 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407020] When the default font size for epub is changed, links are at the wrong positions
https://bugs.kde.org/show_bug.cgi?id=407020 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de --- Comment #5 from Jan Rathmann --- It seems that this bug happens every time the font+size configuration in the Epub backend is set to anything deviating from the global default font+size configuration of Plasma desktop. E.g.: Plasma Systemsettings -> Appearance -> Fonts: "Noto Sans 10" -> links in epub files work correctly only for "Noto Sans 10" Plasma Systemsettings -> Appearance -> Fonts: "Bitstream Charter 11" -> links in epub files work correctly only for "Bitstream Charter 11" Tested with Neon user live image (okular-extra-backends needs to be installed). -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 464698] Sometimes the scrollbar doesn't move when clicking and dragging it
https://bugs.kde.org/show_bug.cgi?id=464698 --- Comment #7 from Jan Rathmann --- Forgot to mention, I'm using NeoChat as Flatpak from Flathub, in case that matters. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 464698] Sometimes the scrollbar doesn't move when clicking and dragging it
https://bugs.kde.org/show_bug.cgi?id=464698 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Jan Rathmann --- I'm also seeing this behavious, sometimes the scrollbar works, sometimes it doesn't. If it doesn't work, it usually helps to temporarily switch to another room and then switch back to the original one. Wondered if this might be Wayland specific but I see that the original report is from X11.. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447636] Android 11: scoped storage does not allow to share the root of the filesystem
https://bugs.kde.org/show_bug.cgi?id=447636 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447636] Android 11: scoped storage does not allow to share the root of the filesystem
https://bugs.kde.org/show_bug.cgi?id=447636 Jan Rathmann changed: What|Removed |Added CC||l12c-account_for_kde@l12c.e ||u --- Comment #7 from Jan Rathmann --- *** Bug 447774 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447774] File system expose cannot expose certain folders on Android 11
https://bugs.kde.org/show_bug.cgi?id=447774 Jan Rathmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||jan.rathm...@gmx.de --- Comment #8 from Jan Rathmann --- *** This bug has been marked as a duplicate of bug 447636 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465164] Wayland: Invisible cursor in Libreoffice with kf5 when inserting geometric shapes etc.
https://bugs.kde.org/show_bug.cgi?id=465164 Jan Rathmann changed: What|Removed |Added Resolution|NOT A BUG |UPSTREAM --- Comment #3 from Jan Rathmann --- Has been fixed upstream. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465851] Images look slightly blurry with zoom level < 100%
https://bugs.kde.org/show_bug.cgi?id=465851 --- Comment #3 from Jan Rathmann --- Created attachment 156312 --> https://bugs.kde.org/attachment.cgi?id=156312=edit Example of sharper rendering in patched Gwenview, view at 100% -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465851] Images look slightly blurry with zoom level < 100%
https://bugs.kde.org/show_bug.cgi?id=465851 --- Comment #2 from Jan Rathmann --- Created attachment 156311 --> https://bugs.kde.org/attachment.cgi?id=156311=edit Example of sharper rendering in Firefox, view at 100% -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465851] Images look slightly blurry with zoom level < 100%
https://bugs.kde.org/show_bug.cgi?id=465851 --- Comment #1 from Jan Rathmann --- Created attachment 156310 --> https://bugs.kde.org/attachment.cgi?id=156310=edit Example of blurry rendering in Gwenview, view at 100% -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465851] New: Images look slightly blurry with zoom level < 100%
https://bugs.kde.org/show_bug.cgi?id=465851 Bug ID: 465851 Summary: Images look slightly blurry with zoom level < 100% Classification: Applications Product: gwenview Version: 20.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- Created attachment 156309 --> https://bugs.kde.org/attachment.cgi?id=156309=edit Patch to make Gwenview render images more sharply SUMMARY Some images (photos) look slightly blurry when they are displayed with a zoom level < 100% (this is the default if I simply open an image file that has a higher resolution than my screen). STEPS TO REPRODUCE 1. Open a photo in Gwenview with small, fine-grained details. OBSERVED RESULT Photo looks slightly blurry. (see attached screenshot, view at 100%) EXPECTED RESULT Photo looks "sharp". (see attached screenshot of the same image displayed by Firefox, view at 100%) ADDITIONAL INFORMATION I discovered this problem by developing RAW files in darktable, wondering why the image looks sharp in darktable but a bit blurry in Gwenview. I compared the rendering of Gwenview with: * Firefox * digiKam * Eye of Gnome On all of them it looks "good/sharp". I get a sharp rendering in Gwenview by replacing Qt::SmoothTransformation with Qt::FastTransformation in one function, see attached patch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465164] Wayland: Invisible cursor in Libreoffice with kf5 when inserting geometric shapes etc.
https://bugs.kde.org/show_bug.cgi?id=465164 Jan Rathmann changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 || -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465164] Wayland: Invisible cursor in Libreoffice with kf5 when inserting geometric shapes etc.
https://bugs.kde.org/show_bug.cgi?id=465164 --- Comment #2 from Jan Rathmann --- (In reply to Vlad Zahorodnii from comment #1) > Based on my debugging, it appears like libreoffice tries to set an empty > bitmap cursor (and it also hits a buggy code path in qtwayland, but it's > unrelated in this case). Please report this issue to libreoffice developers, > it looks like a client side bug. Ok, done: https://bugs.documentfoundation.org/show_bug.cgi?id=15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465164] New: Wayland: Invisible cursor in Libreoffice with kf5 when inserting geometric shapes etc.
https://bugs.kde.org/show_bug.cgi?id=465164 Bug ID: 465164 Summary: Wayland: Invisible cursor in Libreoffice with kf5 when inserting geometric shapes etc. Classification: Plasma Product: kwin Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- SUMMARY I'm not sure whether this is a bug in KDE or Libreoffice. On wayland when running Libreoffice with kf5 backend under Plasma 5.26.90, the mouse cursor in the main pane of the LO window becomes invisible when performing certain "drawing" operations, like inserting a rectangle or a text field. This bug was present to that extend in previous Plasma versions that the cursor has a wrong icon (something else like the usual cross hair), but stays visible. The invisibility seems to be an additional regression in Plasma 5.26.90. STEPS TO REPRODUCE 1. Boot into Plasma 5.26.90, Wayland session. 2. Run Libreoffice with kf5 support. (I discovered it while using LO Draw, but e.g. LO Writer is also affected) 3. Try to insert a rectangle or some other shape, or a text field. OBSERVED RESULT After clicking the button of the thing you want to insert, the cursor becomes invisible while being in the "main pane" of the LO window. EXPECTED RESULT When working correctly, the cursor stays visible and morphs into a cross hair icon to indicate one can now draw something. ADDITIONAL INFORMATION I can reproduce this on VirtualBox and real HW. It does not happen on X11, and when running LO on Wayland with the generic backend: SAL_USE_VCLPLUGIN=gen libreoffice I can reproduce it on: (with pristine user accounts) * Kubuntu 22.10 + 5.27 beta PPA * Neon unstable up-to-date installation * neon-unstable-20230122-1118.iso live image (on real HW and Virtualbox) (Unfortunately current neon unstable live image doesn't boot for me). I can only partly reproduce it (cursor visible, but wrong, see above) on: * Kubuntu 22.10 live image * Neon user live image Kind regards, Jan -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461741] Panel raises and doesn't hide after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=461741 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Jan Rathmann --- While I cannot reproduce this bug in the context of just locking the screen, I see something very similar after waking up from suspend: My autohiding panel appears and stays raised until I hover it for one time with the mouse (doesn't seem to matter if screen locking is active or not) . I can reproduce this with pristine user accounts under: * Kubuntu 22.10 + Plasma 5.27 Beta, Wayland * Neon unstable, Wayland To test it, it is sufficient to enable auto-hide on KDE's default bottom panel, suspend the machine, and wake it up again. It does not happen under X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 267277] configurable delay for autohide/show of panels
https://bugs.kde.org/show_bug.cgi?id=267277 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464687] New: Wayland: Hamburger menu pops up again when trying to select a category
https://bugs.kde.org/show_bug.cgi?id=464687
Bug ID: 464687
Summary: Wayland: Hamburger menu pops up again when trying to
select a category
Classification: Applications
Product: systemsettings
Version: 5.26.90
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: jan.rathm...@gmx.de
Target Milestone: ---
Created attachment 155526
--> https://bugs.kde.org/attachment.cgi?id=155526=edit
Screencast demonstration of the bug
SUMMARY
On Wayland, there is a weird bug when the hamburger menu is openend and
dismissed without clicking on any of its items.
STEPS TO REPRODUCE
1. Open Systemsettings
2. Click on the hamburger menu
3. Click on a place on the side bar, the menu disappears
4. Click on a category (Apppearance, etc.) on the side bar
OBSERVED RESULT
Category doesn't open, instead the hamburger menu appears again.
Repeatingy clicking on the category again just toggles the hamburger menu on
and off.
It can be completely dismissed by either clicking on one of its items ("About
KDE" etc.) or by clicking somewhere on the "main pane" of the systemsettings
window (not the side bar).
(Screencast attached.)
This doesn't seem to happen under X11.
EXPECTED RESULT
The content of the clicked category should be displayed.
Reproducable on Kubuntu 22.10 + Plasma Beta PPA (real HW) and on Neon unstable
live image (Virtualbox).
Kind regards, Jan
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 463024] Plasma doesn't respect Sub-pixel rendering for system tray and desktop
https://bugs.kde.org/show_bug.cgi?id=463024 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de --- Comment #22 from Jan Rathmann --- I did two tests by booting the live images of current Neon user and Kubuntu 22.10. - Neon live-image: (Plasma 5.26.5, Frameworks 5.101, Qt 5.15.8) Can reproduce the bug. By default, sub-pixel rendering is turned off in the font settings. But nevertheless I can see in a screenshot that sub-pixel rendering is used in the text of the clock applet in the systray! For text in Kickoff and KDE apps (tested Systemsettings, Dophin, Window decoration), everything seems to be correct (no sub-pixel rendering). However, Firefox (GTK) uses sub-pixel rendering in its UI texts! - Kubuntu 22.10: (Plasma 5.25.5, Frameworks 5.98, Qt 5.15.6) Bug in the Plasma panel is not there. By default, sub-pixel rendering is turned on. If I turn it off in the font settings (and restart Plasma session), even the clock applet text is correctly rendered without sub-pixel rendering. For anything else, results are the same as within Neon: KDE apps correct, Firefox (GTK) "wrong". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449027] Crash when clicking on application dashboard icon on panel
https://bugs.kde.org/show_bug.cgi?id=449027 --- Comment #8 from Jan Rathmann --- Fortunately I haven't seen this bug for a really long time, so it seems that something happened that fixed it :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426928] Position of widgets on a panel is sometimes not saved during sessions
https://bugs.kde.org/show_bug.cgi?id=426928 Jan Rathmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Jan Rathmann --- Ok, if I add a spacer it will move the clock widget to the right panel edge as desired. If that's by design the way it should work, then I can't reproduce the bug anymore for now - the panel configuration stays the same as it should after log out/log in :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426928] Position of widgets on a panel is sometimes not saved during sessions
https://bugs.kde.org/show_bug.cgi?id=426928 --- Comment #6 from Jan Rathmann --- Created attachment 154426 --> https://bugs.kde.org/attachment.cgi?id=154426=edit Recording of new panel with clock widget, failing to move it to the right @veggero Here is a video where I create a new empty panel, add a clock widget and fail to move it to right panel side. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426928] Position of widgets on a panel is sometimes not saved during sessions
https://bugs.kde.org/show_bug.cgi?id=426928 --- Comment #4 from Jan Rathmann --- (In reply to veggero from comment #3) > There has been some fixes about this since the last message. May I ask you > if you can still reproduce the bug? Ok, I tried again, but for now I'm not able to get past step 5 of my reproduction instructions in the opening post. When I have added a clock widget, it always gets added to the very left side of the panel, and I haven't found a way anymore to move it to the right! Even setting the panel alignment from left to right doesn't change anything. So basically, it seems like I can't reproduce the bug because of another bug. Tested on: * Neon stable live image (Virtualbox) * Neon unstable live image (Virtualbox) * Kubuntu 22.10 + Backports PPA on real HW -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 450169] Apps sometimes don't start by mouse click on Wayland
https://bugs.kde.org/show_bug.cgi?id=450169 Jan Rathmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jan Rathmann --- Since I haven't seen this bug for a long time, I assume it somehow got fixed during this year :) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460723] Thumbnails for RAW files are shown allthough they shouldn't
https://bugs.kde.org/show_bug.cgi?id=460723 --- Comment #1 from Jan Rathmann --- Hypothesis after investigating a bit (I hope it's not totally wrong): * Recently, the camera RAW images plugin has been added to KImageFormats (source: changelog of frameworks 5.99): https://invent.kde.org/frameworks/kimageformats/-/commit/eefb8146d360879e85c5136401303a99d7b0c845#1a471716951fdc5029dbe12eb74a4bbfa952c59c * The "imagethumbnail" preview type in Dolphin seems to feel responsible for _every_ image mimetype ( "image/*" ), see: https://invent.kde.org/network/kio-extras/-/blob/master/thumbnail/imagethumbnail.json So in combination with the camera RAW images plugin in place, checking the "Images (GIF, PNG, BMP, ...) " entry in preview settings now implicitly also covers RAW files even though one may have explicitly deselected the "raw image" entry. Not only raw files are affected: There is e.g. a separate entry for JPEG images in the preview settings. If I deselect it, thumbnails for JPG files are displayed nevertheless when "Images (GIF, PNG, BMP, ...) " is selected. So it effectivly does nothing unless one disables previews for all images. == Idea == Perhaps it would be good solution, if the imagethumbnail preview type would only apply to all image files _not_ covered by separate preview types (BMP, PNG, PCX etc; _not_ JPEG or RAW files)? == (Horrible) workaround == Deleting the file /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/kimg_raw.so will stop new RAW thumbnails being generated (to remove the existing ones, purging ~/.cache/thumbnails should help). -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460723] New: Thumbnails for RAW files are shown allthough they shouldn't
https://bugs.kde.org/show_bug.cgi?id=460723
Bug ID: 460723
Summary: Thumbnails for RAW files are shown allthough they
shouldn't
Classification: Frameworks and Libraries
Product: kio-extras
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Thumbnails and previews
Assignee: plasma-b...@kde.org
Reporter: jan.rathm...@gmx.de
Target Milestone: ---
SUMMARY
In Dolphin and file dialog, thumbnails are generated and displayed for various
RAW files (.RW2, .ARW, .DNG) allthough I don't want this and have explicitly
unchecked this option in Dolphins preview settings ("RAW files").
This started happening after upgrading to Kubuntu 22.10 with enabled backports
PPA (Plasma 5.26.1, Frameworks 5.99).
If I also deselect "Images (GIF, PNG, BMP, ...) as a preview type, this stops
displaying thumbnails for RAW files, but also for a lot of other image file
types where I actually want to see the thumbnails.
Kind regards, Jan
SOFTWARE/OS VERSIONS
Kubuntu 22.10 + Backports-PPA
KDE Plasma Version: 5.26.1
KDE Frameworks Version: 5.99
Qt Version: 5.15.5
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Broken corners on pop-ups, dialogs, applets, and tooltips
https://bugs.kde.org/show_bug.cgi?id=438644 --- Comment #49 from Jan Rathmann --- I can confirm that the Plasma update to 5.26.1 fixes the bug for me on my dark panels :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 --- Comment #8 from Jan Rathmann --- Update: I recently got a new PC and I don't see the bug there anymore, without changing anything on the installed OS. For graphics now I use the integrated GPU of the Ryzen 7 5700G that also uses the amdgpu driver, same as before. So this bug may be a special problem related to my old graphics card, an Asus Radeon R7 240. For other people still affected, I can present you a really ugly workaround that nevertheless worked for me: * Create a systemd service roughly like this (Don't know if all of those environment variables are actually necessary. Don't forget to insert your actual user name/computer name etc.): [Unit] Description=Workaround to fix flickering after suspend under Wayland After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target [Service] ExecStart=/path/to/kwin-suspend-fix-flicker.sh User=YOUR_USER_NAME Environment=DISPLAY=:1 Environment=DESKTOP_SESSION="plasmawayland" Environment=DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/YOUR_NUMERICAL_USERID/bus" Environment=SESSION_MANAGER="local/YOUR_COMPUTER_NAME:@/tmp/.ICE-unix/1467,unix/YOUR_COMPUTER_NAME:/tmp/.ICE-unix/1467" Environment=XDG_RUNTIME_DIR="/run/user/YOUR_NUMERICAL_USERID" Environment=DESKTOP_SESSION="plasmawayland" declare -x DISPLAY=":1" Environment=XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" Environment=XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session2" Environment=XDG_SESSION_TYPE="wayland" [Install] WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target * Then create a script kwin-suspend-fix-flicker.sh : #!/bin/bash qdbus org.kde.KWin /component/kwin org.kde.kglobalaccel.Component.invokeShortcut "MinimizeAll" sleep 0.5 qdbus org.kde.KWin /component/kwin org.kde.kglobalaccel.Component.invokeShortcut "MinimizeAll" This will run the Kwin effect "Minimize all" to stop the flickering, and the run the same effect a second time to restore the original positions of all windows. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459967] New: Dolphin crashed after copying file
https://bugs.kde.org/show_bug.cgi?id=459967 Bug ID: 459967 Summary: Dolphin crashed after copying file Classification: Applications Product: dolphin Version: 22.04.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jan.rathm...@gmx.de CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.3) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-48-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Happened immediately after I copied a file per drag and drop in split view from one pane to another (small text file). Could not reproduce on a second attempt to copy the same file (same as before with split view + dnd). The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 QSharedDataPointer::~QSharedDataPointer (this=0x557ceac5b690, __in_chrg=) at /usr/include/c++/11/bits/atomic_base.h:385 #5 KFileItem::~KFileItem (this=0x557ceac5b690, __in_chrg=) at ./src/core/kfileitem.cpp:605 #6 0x7f0fe30a6471 in QList::node_destruct (n=0x557ceac5b690, this=0x557ceabc4a60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:479 #7 QList::erase (it=..., this=0x557ceabc4a60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:566 #8 KCoreDirListerCache::reinsert (this=this@entry=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, item=..., oldUrl=...) at ./src/core/kcoredirlister_p.h:289 #9 0x7f0fe3095eae in KCoreDirListerCache::processPendingUpdates (this=this@entry=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at ./src/core/kcoredirlister.cpp:2018 #10 0x7f0fe3096ec0 in KCoreDirListerCache::slotResult (this=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, j=) at ./src/core/kcoredirlister.cpp:1338 #11 0x7f0fe1623793 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5b26bb20, r=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, this=0x557ceaea81e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x557ceaba2340, signal_index=6, argv=0x7ffc5b26bb20) at kernel/qobject.cpp:3886 #13 0x7f0fe161caa7 in QMetaObject::activate (sender=sender@entry=0x557ceaba2340, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc5b26bb20) at kernel/qobject.cpp:3946 #14 0x7f0fe2835f00 in KJob::result (this=this@entry=0x557ceaba2340, _t1=, _t1@entry=0x557ceaba2340, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #15 0x7f0fe283bdab in KJob::finishJob (this=0x557ceaba2340, emitResult=) at ./src/lib/jobs/kjob.cpp:98 #16 0x7f0fe283be5d in KJob::kill (this=0x557ceaba2340, verbosity=verbosity@entry=KJob::EmitResult) at ./src/lib/jobs/kjob.cpp:118 #17 0x7f0fe308a60a in KCoreDirListerCache::stopListJob (this=this@entry=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, url=..., silent=silent@entry=true) at ./src/core/kcoredirlister.cpp:441 #18 0x7f0fe308debe in KCoreDirListerCache::stopListingUrl (this=this@entry=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=, lister@entry=0x557cea6ebec0, _u=..., silent=silent@entry=true) at ./src/core/kcoredirlister.cpp:407 #19 0x7f0fe308e080 in KCoreDirListerCache::stop (this=this@entry=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=lister@entry=0x557cea6ebec0, silent=silent@entry=true) at ./src/core/kcoredirlister.cpp:378 #20 0x7f0fe309b8d2 in KCoreDirListerCache::listDir (this=0x7f0fe3118560 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=, dirUrl=..., _keep=, _reload=) at ./src/core/kcoredirlister.cpp:116 #21 0x7f0fe3604112 in KFileItemModel::refreshDirectory (this=0x557cea6869d0, url=...) at ./src/kitemviews/kfileitemmodel.cpp:132 #22 0x557ce8a53585 in FoldersPanel::loadTree (this=0x557cea38eb00, url=..., navigationBehaviour=) at ./src/panels/folders/folderspanel.cpp:342 #23 0x557ce8a4bb39 in FoldersPanel::urlChanged (this=0x557cea38eb00) at ./src/panels/folders/folderspanel.cpp:109 #24 0x557ce8a4ba06 in Panel::setUrl (this=0x557cea38eb00, url=...) at ./src/panels/panel.cpp:54 #25 0x7f0fe1623793 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5b26c090, r=0x557cea38eb00, this=0x557cea38fe00) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #26 doActivate (sender=0x557cea0568d0, signal_index=11, argv=0x7ffc5b26c090) at
[frameworks-kio] [Bug 448114] kioslave5 crashes when searching in Dolphin
https://bugs.kde.org/show_bug.cgi?id=448114 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 --- Comment #5 from Jan Rathmann --- Javier, is your card also supported by the amdgpu driver? (You can check by running 'lspci -k' and see if there is a line that says something like "Kernel modules: radeon, amdgpu") If yes, it could be helpful if you try it out and see if you can confirm the behaviour that I'm getting when using amdgpu (flickering when lock screen is disabled). Have you tested if everything works fine when you use Plasma X11 session instead? This would also be interesting to know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 --- Comment #3 from Jan Rathmann --- Created attachment 149348 --> https://bugs.kde.org/attachment.cgi?id=149348=edit Output of lshw in english Sorry, the output of lshw I first posted was in german, attaching an english version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447705] Flickering in Wayland session (most often when returning from standby)
https://bugs.kde.org/show_bug.cgi?id=447705 --- Comment #32 from Jan Rathmann --- I have posted a follow-up report: https://bugs.kde.org/show_bug.cgi?id=454639 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 --- Comment #2 from Jan Rathmann --- Created attachment 149347 --> https://bugs.kde.org/attachment.cgi?id=149347=edit radeon driver: Corrupted screen after suspend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 --- Comment #1 from Jan Rathmann --- Created attachment 149346 --> https://bugs.kde.org/attachment.cgi?id=149346=edit Output of lshw -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] New: amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 Bug ID: 454639 Summary: amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled Product: kwin Version: 5.24.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- Flags: Wayland+ Created attachment 149345 --> https://bugs.kde.org/attachment.cgi?id=149345=edit Video showing the flickering This is a follow-up report to https://bugs.kde.org/show_bug.cgi?id=447705 Steps how I experience the bug: * Use Plasma Wayland session, screenlocking disabled, GPU driver set to amdgpu (see below) * Do Suspend-to-RAM. * Resume. Result: Sometimes heavy flickering of the whole screen, it goes away if I click on UI elements (see attached video). Happens always?: No. At the first resumes after boot chances are good that everythings's fine. But when flickering has happend one time, it seems it will also flicker on all subsequent resumes (until rebooting). (I rarely see a similar flickering in Firefox at Firefox startup or when a new browser tab loads [usually only a small square part of the window is affected, it goes away almost immediately <1 second. Not sure if it is related.].) Additional notes: Kubuntu 22.04 + Backports-PPA Plasma 5.24.5 Frameworks: 5.94.0 Qt: 5.15.3 Kernel: 5.15.0-33-generic == My system == Board: Gigabyte P35-DS3 CPU: Intel Core2Quad Q9550 Graphics card: Asus Radeon R7 240 Note that my graphics card can work with two different drivers: The default driver is radeon but amdgpu also works by manually enabling it by adding the following boot optionts to the linux command line in Grub: radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 For at least a year(?) I solely used amdgpu on my system (the initial reason was something like amdgpu worked slightly better than radeon at one minor aspect, but I don't remember exactly anymore). Using amdgpu was so ubiquitous for me that I didn't even remember it when writing the original bug report. For debugging purpose I tested how suspend/resume behaves with radeon driver in use (both on Wayland and X11), and it is different: Resume from suspend under Wayland: * amdgpu: flickers sometimes, as described above. * radeon: no flickering, but even worse: graphics output completely distorted and corrupted (see attached video). Sometimes temporarily switching between different TTYs (Ctrl+Alt+F1-7) restores the desktop, when it does not it effectively crashes the whole session. Resume from suspend under X11: * Everything fine, no flicker (amdgpu), no corruption (radeon) I also tested (under Wayland) what happens if the lock screen is enabled after suspend: * amdgpu: Everythings fine now, couldn't reproduce the flickering anymore * radeon: corrupted screen, as described above Sorry it took so long to report this follow-up report, it took some time to investigate and test all those different subtly different surrounding conditions. Kind regards, Jan -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 453460] New: Gwenview crashes randomly when rotating images
https://bugs.kde.org/show_bug.cgi?id=453460 Bug ID: 453460 Summary: Gwenview crashes randomly when rotating images Product: gwenview Version: 22.04.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- Application: gwenview (22.04.0) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.15.0-27-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: This happened two times when I browsed a large collections of images (all PNG files) and I rotated/cropped some of them. The crashes happened when I pressed Ctrl+R to rotate, and I also had unsaved changes (mostly rotating) from other images which got lost after the crash. When I made the next attempt to rotate the same image, it didn't crash. I'm not sure whether this is a duplicate of the following bug: https://bugs.kde.org/show_bug.cgi?id=439697 The crash does not seem to be reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:131 #5 0x7fd1f2e855c2 in memcpy (__len=, __src=0x7fd192462d28, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:29 #6 QImage::copy (this=0x55892585f980, r=...) at image/qimage.cpp:1239 #7 0x7fd1f450c78a in Gwenview::RasterImageItem::paint (this=0x5589256d4f40, painter=0x7ffc6a7212e0) at ./lib/documentview/rasterimageitem.cpp:106 #8 0x7fd1f38f97b3 in QGraphicsScenePrivate::draw (this=this@entry=0x55892415ef90, item=item@entry=0x5589256d4f40, painter=painter@entry=0x7ffc6a7212e0, viewTransform=viewTransform@entry=0x0, transformPtr=, exposedRegion=exposedRegion@entry=0x558924323890, widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:4981 #9 0x7fd1f38fa773 in QGraphicsScenePrivate::drawSubtreeRecursive (this=this@entry=0x55892415ef90, item=0x5589256d4f40, painter=painter@entry=0x7ffc6a7212e0, viewTransform=viewTransform@entry=0x0, exposedRegion=exposedRegion@entry=0x558924323890, widget=, widget@entry=0x558924328880, parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873 #10 0x7fd1f38f990b in QGraphicsScenePrivate::draw (this=this@entry=0x55892415ef90, item=item@entry=0x55892468fde0, painter=painter@entry=0x7ffc6a7212e0, viewTransform=viewTransform@entry=0x0, transformPtr=, exposedRegion=exposedRegion@entry=0x558924323890, widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:5013 #11 0x7fd1f38fa773 in QGraphicsScenePrivate::drawSubtreeRecursive (this=this@entry=0x55892415ef90, item=0x55892468fde0, painter=painter@entry=0x7ffc6a7212e0, viewTransform=viewTransform@entry=0x0, exposedRegion=exposedRegion@entry=0x558924323890, widget=, widget@entry=0x558924328880, parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873 #12 0x7fd1f38f990b in QGraphicsScenePrivate::draw (this=0x55892415ef90, item=, painter=0x7ffc6a7212e0, viewTransform=0x0, transformPtr=, exposedRegion=0x558924323890, widget=, opacity=, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:5013 #13 0x7fd1f38bc3f1 in QGraphicsItemEffectSourcePrivate::draw (this=0x558925a22430, painter=0x7ffc6a7212e0) at graphicsview/qgraphicsitem.cpp:11328 #14 0x7fd1f3966f4a in QGraphicsEffectSource::draw (this=0x5589256dc970, painter=0x7ffc6a7212e0) at effects/qgraphicseffect_p.h:90 #15 0x7fd1f38fa567 in QGraphicsScenePrivate::drawSubtreeRecursive (this=this@entry=0x55892415ef90, item=0x55892469ce10, painter=painter@entry=0x7ffc6a7212e0, viewTransform=viewTransform@entry=0x0, exposedRegion=exposedRegion@entry=0x558924323890, widget=, widget@entry=0x558924328880, parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4867 #16 0x7fd1f38fadf2 in QGraphicsScenePrivate::drawItems (this=this@entry=0x55892415ef90, painter=painter@entry=0x7ffc6a7212e0, viewTransform=viewTransform@entry=0x0, exposedRegion=exposedRegion@entry=0x558924323890, widget=0x558924328880) at graphicsview/qgraphicsscene.cpp:4735 #17 0x7fd1f391fc3f in QGraphicsView::paintEvent (this=, event=) at ../../include/QtWidgets/../../src/widgets/graphicsview/qgraphicsscene.h:307 #18 0x7fd1f35f04ee in QWidget::event (this=this@entry=0x558924323390, event=event@entry=0x7ffc6a7216a0) at kernel/qwidget.cpp:9033 #19 0x7fd1f369e422 in QFrame::event (this=0x558924323390, e=0x7ffc6a7216a0) at
[kwin] [Bug 447705] Flickering in Wayland session (most often when returning from standby)
https://bugs.kde.org/show_bug.cgi?id=447705 --- Comment #29 from Jan Rathmann --- (In reply to Aleix Pol from comment #28) > There was an in-between version of the MR that wasn't working well, but it > was addressed. Ah, thanks for the explanation. I'll see if I can still reproduce it on one of the branches containing the final version of the fix - it may take some time before I can a definitive answer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447705] Flickering in Wayland session (most often when returning from standby)
https://bugs.kde.org/show_bug.cgi?id=447705 --- Comment #27 from Jan Rathmann --- I feel a bit confused that the bug is now marked as 'Fixed', after I wrote yesterday in #24 that the changes from the merge request don't fix the bug for me. Am I missing something, or was my comment somehow unclear? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447705] Flickering in Wayland session (most often when returning from standby)
https://bugs.kde.org/show_bug.cgi?id=447705 --- Comment #24 from Jan Rathmann --- (In reply to Aleix Pol from comment #20) > Submitted this fix, maybe someone can confirm it addresses the issue as well? > https://invent.kde.org/plasma/kwin/-/merge_requests/2188 Sorry, took a while to test the patch, had to figure out how to build patched Kwin on my test installation of Neon Unstable. Unfortunately, the patch from the merge request doesn't fix the bug for me - still flickering after resume sometimes. Maybe it's relevant to mention that I don't have screen locking enabled (no password prompt on resume). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447705] Flickering in Wayland session (most often when returning from standby)
https://bugs.kde.org/show_bug.cgi?id=447705 --- Comment #22 from Jan Rathmann --- (In reply to Aleix Pol from comment #20) > Submitted this fix, maybe someone can confirm it addresses the issue as well? > https://invent.kde.org/plasma/kwin/-/merge_requests/2188 The first patch from this morning seems to make no difference for me (flickering is still there). I can try to make a build with the additional changes tomorrow or so. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450637] Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed
https://bugs.kde.org/show_bug.cgi?id=450637 Jan Rathmann changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8019 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450637] Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed
https://bugs.kde.org/show_bug.cgi?id=450637 --- Comment #5 from Jan Rathmann --- Sorry, I first overlooked the linked upstream report. But this might be a different bug than the one I reported here anyway: * it references only to behaviour of button popups, not of menus * LO 7.2 contains a temporary fix for the button popups thing, and I can confirm that this fix works for me on LO 7.2 on Kubuntu 22.10, but only for the exact use case with the button popups! While my bug here with menus opening as separate windows shows up also on LO 7.2 (independently whether this fix is included or not). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450637] Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed
https://bugs.kde.org/show_bug.cgi?id=450637 --- Comment #4 from Jan Rathmann --- (In reply to David Edmundson from comment #3) > Not a kwin bug. Ok, does that implicate it is a bug in LibreOffice? The thing is, I can't reproduce it with LibreOffice on Gnome Wayland session (just tested with two up-to-date (K)Ubuntu Jammy test installations). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449027] Crash when clicking on application dashboard icon on panel
https://bugs.kde.org/show_bug.cgi?id=449027 --- Comment #4 from Jan Rathmann --- Update: This kind of crash has continued to appear from time to time recently, triggered by the same action (clicking on dashboard icon) and with similar backtraces. I'm not that experienced in reading backtraces, but could it indicate that there is some problem/bug with glib (not KDE related)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450637] New: Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed
https://bugs.kde.org/show_bug.cgi?id=450637 Bug ID: 450637 Summary: Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed Product: kwin Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- STEPS TO REPRODUCE 1. Start a Plasma Wayland session 1. Open e.g. LibreOffice Writer 2. Open or switch to any other window (-> LibreOffice window loses focus) 3. Inside the unfocussed LO window, click on a menu (File, Edit, etc.) OBSERVED RESULT The menu appears in the centre of the screen and has a window decoration. EXPECTED RESULT It should appear as a menu, not as a window on its own. I can reproduce this when running a Kubuntu 22.04 daily-live image in VirtualBox (and log in to a Wayland session manually). SOFTWARE/OS VERSIONS Kubuntu 21.10+Backports/22.04 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426720] broken colors (gamma?) when saving images
https://bugs.kde.org/show_bug.cgi?id=426720 --- Comment #9 from Jan Rathmann --- Created attachment 146991 --> https://bugs.kde.org/attachment.cgi?id=146991=edit Screenshot of Plasma 5.3. wallpaper opened in Gwenview -- You are receiving this mail because: You are watching all bug changes.
