[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.
[plasma-systemmonitor] [Bug 482257] When I click on Processes or any other tab
https://bugs.kde.org/show_bug.cgi?id=482257 Jan changed: What|Removed |Added CC||mrzyglodja...@gmail.com -- 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.
[kwin] [Bug 454231] 3-fingers touchpad gesture (to navigate between virtual desktops) should follow touchpad scrolling direction preference
https://bugs.kde.org/show_bug.cgi?id=454231 Frans-Jan v. Steenbeek changed: What|Removed |Added Version|5.24.90 |6.0.4 --- Comment #13 from Frans-Jan v. Steenbeek --- Same on Plasma 6.0.4. as well. Should we update the version tag of this bug now that we're on the next Megarelease? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454231] 3-fingers touchpad gesture (to navigate between virtual desktops) should follow touchpad scrolling direction preference
https://bugs.kde.org/show_bug.cgi?id=454231 Frans-Jan v. Steenbeek changed: What|Removed |Added CC||frans-...@van-steenbeek.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #17 from Jan van Bekkum --- When I open Digikam 8.3.0 from the taskbar on my 3440 x 1440 display and then drag it to the 3840 x 2160 display then the fonts are still too small. If I open it from the taskbar on my 3840 x 2160 display they are correct. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 485681] Keyboard is not working
https://bugs.kde.org/show_bug.cgi?id=485681 Gerrit Jan changed: What|Removed |Added CC||gj.elder...@quicknet.nl --- Comment #2 from Gerrit Jan --- I have the same problem. When I try to close krdc the screen freezes. Operating System: openSUSE Tumbleweed 20240417 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-1-default (64-bit) -- 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
[frameworks-kglobalaccel] [Bug 484884] New: Overriden default shortcuts stop working after relogin
https://bugs.kde.org/show_bug.cgi?id=484884
Bug ID: 484884
Summary: Overriden default shortcuts stop working after relogin
Classification: Frameworks and Libraries
Product: frameworks-kglobalaccel
Version: 6.0.0
Platform: NixOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: kde-b...@keksgesicht.net
Target Milestone: ---
Created attachment 168034
--> https://bugs.kde.org/attachment.cgi?id=168034=edit
my current kglobalshortcutsrc config file
SUMMARY
When overriding default shortcuts in other options or applications it only
applies to the current session. When login out und in again (and parsing
kglobalshortcutsrc) these shortcuts stop working do nothing. Not even their
default binding. Every other shortcut (which did not trigger a reassign
warning) works normally.
STEPS TO REPRODUCE
1. Set "Meta+R" or "Meta+Shift+S" for any other application or option than
default and Apply (Shortcuts in System Settings)
2. Logout and Login (alternative reboot)
3. Try again one of the shortcuts set in step 1
OBSERVED RESULT
Shortcut has no function at all
EXPECTED RESULT
Shortcuts work are persistent and consistent over reboots and relogins.
SOFTWARE/OS VERSIONS
Operating System: NixOS 24.05
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.2 (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
I recognized that are changes between Plasma5 and Plasma6 in how custom
application shortcuts are saved in kglobalshortcutsrc.
Also I get these Messages in the journal on login. They are part
plasma-kwin_wayland.service unit:
Apr 01 11:41:59 cookieclicker kwin_wayland[23270]:
kf.globalaccel.kglobalacceld: Shortcut found twice in kglobalshortcutsrc.
QKeySequence("Meta+R")
Apr 01 11:41:59 cookieclicker kwin_wayland[23270]:
kf.globalaccel.kglobalacceld: Shortcut found twice in kglobalshortcutsrc.
QKeySequence("Meta+Shift+S")
Also testing some other shortcuts like "Meta+E" and they show the same broken
behaviour. Surprisingly when applying "Meta+." to something else it is
mentioned as a duplicate in the journal, but the Emoji Selector is still
opened.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 484724] New: no font scaling for time with seconds on vertical panels
https://bugs.kde.org/show_bug.cgi?id=484724 Bug ID: 484724 Summary: no font scaling for time with seconds on vertical panels Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: NixOS OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: kde-b...@keksgesicht.net Target Milestone: 1.0 Created attachment 167923 --> https://bugs.kde.org/attachment.cgi?id=167923=edit time text draws outside of vertical panel When using an vertical (floating) panel and setting seconds to show always, the text is larger than the panel it self and does not get resized to the panels real width. SUMMARY Too large text on vertical panels with seconds STEPS TO REPRODUCE 1. use an vertical panel (left or right screen edge) 2. set seconds to show always in Digital Clock widget OBSERVED RESULT oversized text EXPECTED RESULT font scales to panel width SOFTWARE/OS VERSIONS Operating System: NixOS 24.05 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Graphics Platform: Wayland ADDITIONAL INFORMATION - selecting on the "Text display" setting auto selects "Noto 10" and this looks right - weekdays also render correct without setting the font size manually -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426519] Invalid state
https://bugs.kde.org/show_bug.cgi?id=426519 Jan changed: What|Removed |Added CC||jan_cec...@verizon.net --- Comment #25 from Jan --- Created attachment 167890 --> https://bugs.kde.org/attachment.cgi?id=167890=edit Entire column disappeared instead of just spades -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 484639] Fallback to Breeze ignored by KIconLoader because of wrong global initialization order
https://bugs.kde.org/show_bug.cgi?id=484639 Jan Pavlicek changed: What|Removed |Added CC||jan.pavli...@centrum.cz -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 481402] question mark icons shown in systray when oxygen icon theme
https://bugs.kde.org/show_bug.cgi?id=481402 Jan Pavlicek changed: What|Removed |Added CC||jan.pavli...@centrum.cz -- You are receiving this mail because: You are watching all bug changes.
[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.
[plasmashell] [Bug 483617] kicker: segfault when built with clang
https://bugs.kde.org/show_bug.cgi?id=483617 Jan-Niklas Glückert changed: What|Removed |Added Attachment #167222|0 |1 is obsolete|| --- Comment #4 from Jan-Niklas Glückert --- Created attachment 167236 --> https://bugs.kde.org/attachment.cgi?id=167236=edit Better backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483617] kicker: segfault when built with clang
https://bugs.kde.org/show_bug.cgi?id=483617 --- Comment #3 from Jan-Niklas Glückert --- Yes. This is inlining related, I can't reproduce without LTO. Are you suggesting a compiler bug? Meanwhile I've been able to get a better backtrace - though I think the ASAN report already shows that this is probably from a bad object. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483617] kicker: segfault when built with clang
https://bugs.kde.org/show_bug.cgi?id=483617 --- Comment #1 from Jan-Niklas Glückert --- Created attachment 167223 --> https://bugs.kde.org/attachment.cgi?id=167223=edit ASAN output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483617] New: kicker: segfault when built with clang
https://bugs.kde.org/show_bug.cgi?id=483617 Bug ID: 483617 Summary: kicker: segfault when built with clang Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: jannik.glueck...@gmail.com Target Milestone: 1.0 Created attachment 167222 --> https://bugs.kde.org/attachment.cgi?id=167222=edit Backtrace SUMMARY When built with clang, plasmashell-6.0.2 crashes immediately in kicker (wayland session). I managed to get a (probably) useful ASAN run, though I haven't been able to get a symbolized coredump for some reason. Building with gcc did not exhibit this issue. I did not try to reproduce with gcc ASAN or with older clang versions yet, but on first glance it looks like an out of bounds read? Backtrace and ASAN output are in attachments. SOFTWARE/OS VERSIONS Gentoo Linux Plasma 6.0.2 Qt 6.6.2 Clang 18.0.0 libstdc++ 13.2.1 CFLAGS: -O3 -flto=thin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451270] Media hotkeys don't do anything until plasmashell is restarted once
https://bugs.kde.org/show_bug.cgi?id=451270 --- Comment #13 from Jan Klos --- It seems that plasma6 has indeed resolved this for me (or a switch from xorg to wayland, but I doubt it). Prev & next & play/pause keys seem to work perfectly all the time for me. Never had any issue with volume keys. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 428922] Back Button should go back in history
https://bugs.kde.org/show_bug.cgi?id=428922 Jan Hajer changed: What|Removed |Added CC||j...@hajer.com --- Comment #3 from Jan Hajer --- I do not remember when this regression was introduced but I can confirm that is persists in version 23.08.3. -- 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.
[partitionmanager] [Bug 481586] New: KDE partition manager seemingly creates invalin fat32 partition
https://bugs.kde.org/show_bug.cgi?id=481586 Bug ID: 481586 Summary: KDE partition manager seemingly creates invalin fat32 partition Classification: Applications Product: partitionmanager Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: javai...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Attach USB stick to PC/laptop 2. Use KDE partition manager to create new fat32 partition to the device 3. Try copying one/some large files (>2.5GB) to the newly formatted partition OBSERVED RESULT Creating partition was seemingly successful, but copying files to newly formatted partition jammed for the first file. EXPECTED RESULT Files were successfully copied to the device. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20240218 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION USB stick was successfully formatted on windows 10 machine & files copied to the device -- 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.
[Discover] [Bug 480525] Custom backend for DNF5
https://bugs.kde.org/show_bug.cgi?id=480525 --- Comment #5 from Jan Kolarik --- (In reply to Nate Graham from comment #4) > Thanks for the info. > > I've long suspected that we'd see this kind of thing from distros to work > around the limitations of PackageKit. It's a bit of a shame IMO, since > PackageKit itself already needs custom backends for package management > systems, so that work already has to be dome somewhere. And conceptually it > seems like it would be best if the library itself were improved to support > any use cases not yet covered. There are benefits to supporting PackageKit > that go beyond Discover: we use it in other places too, for example to > prompt the user to download needed Samba packages in the file sharing setup > wizard, or to download Konsole if they open Dolphin's terminal panel without > Konsole being installed. Not supporting PackageKit means those features will > stop working in your distro. For the immutable distros this is > understandable since the concept of traditional package management doesn't > really apply there, but for a non-immutable distro, it's supportable in > principle. > > Still, it is what it is. As a path forward, I suggest doing what the Kinoite > and SteamOS folks did: write your own custom backend for Discover and submit > it to KDE for inclusion. Given your knowledge of how DNF5 works, I think you > or your team (or an adjacent one?) represent the ideal folks to do the work! Thank you too for sharing the background. I will discuss it with the team. One more point to note is that, for now, PackageKit with the current dnf and the new dnf5 can coexist on the same system, at least on Fedora Linux. While not ideal due to differences in package states metadata formats stored at separate locations, resulting in inefficient storage usage, this is generally not noticeable for the typical GUI user. Additionally, the backing RPM DB remains the only shared source of information about installed packages. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 480525] [RFE] Support for dnf5 backend
https://bugs.kde.org/show_bug.cgi?id=480525 --- Comment #3 from Jan Kolarik --- (In reply to Nate Graham from comment #2) > Thanks for reaching out. Does this mean that you don't plan to support > PackageKit with DNF 5 at all? And that therefore it will need its own new > backend, not unlike the rpm-ostree backend? Yes, the situation is that PackageKit has been in maintenance mode for some time now, and there are no plans to add new features or backends like DNF5. Therefore, a specific backend or plugin for the dnf5daemon integration will be necessary. -- 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.
[plasma-systemmonitor] [Bug 480865] New: Crash when switching tab
https://bugs.kde.org/show_bug.cgi?id=480865 Bug ID: 480865 Summary: Crash when switching tab Classification: Applications Product: plasma-systemmonitor Version: 5.27.8 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mrzyglodja...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-15-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: The crash happens when switching to "Applications" or "Processes" tab. The overview is working. The crash can be reproduced every time. -- Backtrace: Application: Monitor systemowy (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7fbdf784f38b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fbdf784f3fd in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fbdf79dd0e6 in QAccessibleQuickItem::role() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fbdf8975ca9 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7fbdf8978ab8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7fbdf897a301 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7fbdf785d317 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fbdf7865dfd in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7fbdf7866311 in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7fbdec31ac49 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #15 0x7fbdf6e01f6f in QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*, QQmlTableInstanceModel::DestructionMode) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #16 0x7fbdf6e29661 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #17 0x7fbdf6e01979 in QQmlTableInstanceModel::drainReusableItemsPool(int) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #18 0x7fbdf7952e90 in QQuickTableView::geometryChanged(QRectF const&, QRectF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7fbdf785beac in QQuickItem::setSize(QSizeF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7fbdf6f0c779 in QQuickControlPrivate::resizeContent() () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #21 0x7fbdf6f09223 in QQuickControlPrivate::setRightPadding(double, bool) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #22 0x7fbdfe6f4e2b in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7fbdfe6f5dc6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7fbdfe6f3734 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7fbdfe6d059f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7fbdfcf05a6c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fbdfe6776a6 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7fbdfe6f4e01 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7fbdfe6f5dc6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7fbdfe6f3734 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #31 0x7fbdfe6d059f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #32 0x7fbdfcf05a6c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fbdf785d368 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #35 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #36 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #37 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #38 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #39 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #40 0x7fbdf785d295 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #41
[gwenview] [Bug 476995] The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995 --- Comment #5 from Jan K --- So far I failed to comprehend the relations of PlaceTreeModel, SortedDirModel, KFilePlacesModel, etc., but it turns out that dumb hacking the 'canFetchMore' to always return true makes gwenview usable again - one can browse the directory tree, and it's again in sync with the main view. By no means this solves the issue, for it renders all directories as having subdirectories. (Upon expanding an empty directory, nothing happens apart from displaying 'v' in place of '>' on to the left of the directory name.) I regard this to be a **very** dirty workaround for time being. === --- a/lib/placetreemodel.cpp2024-02-04 15:26:58.085270323 +0100 --- b/lib/placetreemodel.cpp2024-02-04 15:26:58.085270323 +0100 @@ -273,8 +273,8 @@ // Special case to avoid calling openUrl on all places at startup return true; } -const QModelIndex dirIndex = d->dirIndexForNode(node, parent); -return node.model->canFetchMore(dirIndex); +// const QModelIndex dirIndex = d->dirIndexForNode(node, parent); +return true; // node.model->canFetchMore(dirIndex); } void PlaceTreeModel::fetchMore(const QModelIndex ) === -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 480547] New: Cannot connect to remote servers from .ssh/config/ that don't use a resolvable hostname as an identifier
https://bugs.kde.org/show_bug.cgi?id=480547 Bug ID: 480547 Summary: Cannot connect to remote servers from .ssh/config/ that don't use a resolvable hostname as an identifier Classification: Applications Product: krusader Version: 2.7.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: net-connection Assignee: krusader-bugs-n...@kde.org Reporter: j...@delinquent.de CC: krusader-bugs-n...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. have an external host defined in .ssh/config/ 2. use sftp://the_hostname/some/path/ OBSERVED RESULT Error: Internal Error Please send a full bug report at https://kde.bugs.org Could not set host EXPECTED RESULT SFTP connection is established. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It definitely worked before upgrading to 22.04. The definition in .ssh/config is like Host the_hostname User someuser HostName 123.456.654.321 Port 22 It works on local servers but fails on external ones. `ssh the_hostname` works just fine. Affected are hosts with underscores and those without. It works if I set the entry name to something DNS-resolvable. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 480525] New: [RFE] Support for dnf5 backend
https://bugs.kde.org/show_bug.cgi?id=480525 Bug ID: 480525 Summary: [RFE] Support for dnf5 backend Classification: Applications Product: Discover Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jkola...@redhat.com CC: aleix...@kde.org Target Milestone: --- Hello, I am reaching out on behalf of the DNF package manager team to initiate contact and gather an overview of the current state and plans for Plasma Discover regarding support for the dnf5 backend. Specifically, we are talking about the utilization of the dnf5daemon component, which serves as the replacement for PackageKit in the dnf5 package manager for managing RPM packages through various GUI frontends using the D-Bus API. Another reason is the Fedora system-wide change proposal aiming to replace DNF with DNF5 as the default package manager for Fedora 41 (details here: https://fedoraproject.org/w/index.php?title=Changes/ReplaceDnfWithDnf5). As of now, we are aware of two related projects with some ongoing work: - GNOME Software Center: https://gitlab.gnome.org/mcrha/gnome-software/-/tree/wip/dnf5daemon/plugins/dnf5?ref_type=heads - DNF dragora: https://github.com/manatools/dnfdragora/blob/50f1162df883138f1b8b24a49f2182341c49c36a/dnfdragora/dnfd_client.py I am available to offer guidance in implementing the new backend. Best regards, Jan DNF5 upstream: https://github.com/rpm-software-management/dnf5 -- 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.
[gwenview] [Bug 476995] The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995
Jan K changed:
What|Removed |Added
CC||jprofeso...@o2.pl
--- Comment #4 from Jan K ---
I have the same problem, also on Gentoo with its current stable versions of
qt5/plasma/kde frameworks etc.
It seems that the `Gwenview::PlaceTreeModel` from lib/placetreemodel.cpp
malfunctions. The file has not been changed for two years, so my guess is that
recent changes in KFilePlacesModel (KIO) broke gwenview.
As far as my debugger claims, `Gwenview::PlaceTreeModel::canFetchMore` always
returns `false` when I try to expand a folder.
So far I flinched from further debugging once I saw I'd have to rebuild qt &
KDE libs with debugging symbols. I might dig into it with some pointers…
Also, I can't tell if this is related or not, but it seems that in vicinity of
the class responsible for the folders tab a test case fails.
When I try `make test` I get:
===
make test
Running tests...
Test project /tmp/gwenview/build
(…)
Start 5: placetreemodeltest
5/14 Test #5: placetreemodeltest ...***Failed1.16 sec```
* Start testing of PlaceTreeModelTest *
Config: Using QtTest library 5.15.11, Qt 5.15.11 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 13.2.1 20230826), gentoo 2.14
PASS : PlaceTreeModelTest::initTestCase()
QWARN : PlaceTreeModelTest::testListPlaces() kf.kio.core: Malformed JSON
protocol file for protocol: "trash" , number of the ExtraNames fields should
match the number of ExtraTypes fields
QWARN : PlaceTreeModelTest::testListPlaces() kf.kio.core: Malformed JSON
protocol file for protocol: "trash" , number of the ExtraNames fields should
match the number of ExtraTypes fields
FAIL! : PlaceTreeModelTest::testListPlaces() Compared values are not the same
Actual (model.rowCount()): 11
Expected (8) : 8
Loc: [/tmp/gwenview/tests/auto/placetreemodeltest.cpp(127)]
QWARN : PlaceTreeModelTest::testListUrl1() kf.jobwidgets: Cannot register a
job with KUiServerV2JobTracker without QGuiApplication::desktopFileName
QWARN : PlaceTreeModelTest::testListUrl1() kf.kio.core: Malformed JSON
protocol file for protocol: "trash" , number of the ExtraNames fields should
match the number of ExtraTypes fields
QWARN : PlaceTreeModelTest::testListUrl1() org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/qoi"
QWARN : PlaceTreeModelTest::testListUrl1() org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mng"
QWARN : PlaceTreeModelTest::testListUrl1() org.kde.kdegraphics.gwenview.lib:
Unresolved raw mime type "image/x-samsung-srw"
PASS : PlaceTreeModelTest::testListUrl1()
PASS : PlaceTreeModelTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 1066ms
* Finished testing of PlaceTreeModelTest *
This might be a red herring, but it still raises my eyebrows that '/' is being
added twice, for once I added a loop to print the model, I got:
for(int i = 0 ; i < 11; ++i)
qDebug("URL for index %d is: %s", i, model.urlForIndex(model.index(i,
0)).path().toLocal8Bit().data());
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 0 is:
/tmp/placetreemodeltest-vstthm/url1
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 1 is:
/tmp/placetreemodeltest-vstthm/url2
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 2 is: /home/jasiu
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 3 is:
/home/jasiu/Desktop
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 4 is:
/home/jasiu/Documents
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 5 is:
/home/jasiu/Downloads
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 6 is:
/home/jasiu/Pictures
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 7 is: /
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 8 is: /
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 9 is: /files
QDEBUG : PlaceTreeModelTest::testListPlaces() URL for index 10 is: /locations
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #15 from Jan van Bekkum --- I have two displays in my Windows 10 system, a 3840 x 2160 display with scale setting 150% and a 3440 x 1440 display with scale setting 100%. On both displays the scale is smaller for digiKam 8.3.0 than for any other program, including digiKam 8.2.0. Both displays are connected to a Gigabyte GeForce RTX 3070 GAMING OC 8 GB V2 LHR. I don't see a difference after setting Variable: QT_SCALE_FACTOR to value: 1.5. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #12 from Jan van Bekkum --- @Gilles - It is a reaction to this reply from Mike: "Qt6 now always uses HiDPI scaling, this can no longer be deactivated. You have to adjust the fonts in the digiKam settings accordingly." in this conversation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #11 from Jan van Bekkum --- Created attachment 165097 --> https://bugs.kde.org/attachment.cgi?id=165097=edit Environment variables I don't think I have a Qt environment variable set. My Environment Variables are attached. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #8 from Jan van Bekkum --- Force software OpenGL does not make a difference, scaling factor is 150%, dimensions are 3840 x 2160. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #6 from Jan van Bekkum --- Created attachment 165091 --> https://bugs.kde.org/attachment.cgi?id=165091=edit Screenshot of a different program on the same display I can change the font of the icons in digiKam, but not the size of the toolbars and the top bar. The fonts of digiKam 8.3.0 are smaller than the fonts of 8.2.0. Version 8.2.0 was good. I understand from Microsoft feedback that this may ne an app issue. https://support.microsoft.com/en-us/topic/windows-scaling-issues-for-high-dpi-devices-508483cd-7c59-0d08-12b0-960b99aa347d. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 Jan van Bekkum changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Assignee|digikam-bugs-n...@kde.org |jan.vanbek...@gmail.com --- Comment #5 from Jan van Bekkum --- Created attachment 165090 --> https://bugs.kde.org/attachment.cgi?id=165090=edit Screenshot of digiKam on an UHD display -- 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.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #3 from Jan van Bekkum --- I got two other problems that I didn't have in 8.2.0. Therefore I went back to the released version: - The font size on one of my monitors (3840 x 2160) is much smaller than in 8.2.0; - After I rescanned one of my drives and added a tag to all found video footage I had extra copies (_v1, sometimes even _v2, _v3) of most of the files. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #2 from Jan van Bekkum --- This worked! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] New: Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 Bug ID: 479511 Summary: Crash when filling in name of scanned face Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jan.vanbek...@gmail.com Target Milestone: --- Created attachment 164730 --> https://bugs.kde.org/attachment.cgi?id=164730=edit Image causing crash SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open image containing a face 2. Scan for faces 3. Start filling in name OBSERVED RESULT Crash after some delay EXPECTED RESULT Dropdown list with matching names SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This happened with different images. Attached is one of the images. -- 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
[akregator] [Bug 445351] Akregator always wants to recover the session on boot
https://bugs.kde.org/show_bug.cgi?id=445351 Jan Wesselink changed: What|Removed |Added Platform|Arch Linux |Debian stable Version|5.18.3 |5.22.3 CC||wessel...@gmail.com --- Comment #6 from Jan Wesselink --- Same thing here while using wayland on desktop HP prodesk 400 g5. Akregator opens screen to restore last session, is wasnt shutdown properly it says. When starting with x11 it doenst give any problems. akregator 5.22.3 (22.12.3) debian 12 stable KDE -- You are receiving this mail because: You are watching all bug changes.
[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.
[plasma-pa] [Bug 478834] New: Possibility to give an application exclusively audio output
https://bugs.kde.org/show_bug.cgi?id=478834 Bug ID: 478834 Summary: Possibility to give an application exclusively audio output Classification: Plasma Product: plasma-pa Version: 5.27.9 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: fus...@fusselkater.org CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com Target Milestone: --- It would be nice to have a simple way to give an application exclusively rights to play audio. For example with a button in the applications view of the volume control. The problem is, that if you play music in a public event, you don't want to have any sounds played except for the single application you are using for playing music. The workaround I use for this case is to set some dummy output device as default output and only set the application to the real audio output. This works fine, so this feature is just a nice-to-have. -- 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.
[korganizer] [Bug 412722] KOrganizer does not show some events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 Jan Bundesmann changed: What|Removed |Added CC||k...@knofafo.de --- Comment #16 from Jan Bundesmann --- This might be the same bug that's bothering me: https://bugs.kde.org/show_bug.cgi?id=421916 -- 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.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #21 from Jan Klos --- (In reply to Lynn from comment #20) > Most likely what is happening is that by removing/adding the media player > widget you are changing which application the MPRIS passes the media keys > to. Absolutely not. the case (at least not what I am experiencing). The media keys stop working after some time REGARDLESS whether there are other media-type applications registering. > There are many bug reports for this issue in regards to MPRIS on other > bugtrackers. It isn't really a KDE issue, so this bug isn't something that > can be fixed by KDE developers. I only have this issue in KDE Plasma, which is my main environment. Never experienced it in Gnome, although I admittedly use them much less often. -- 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.
[kontact] [Bug 471414] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=471414 Jan Iversen changed: What|Removed |Added CC||jan.iver...@mailbox.org -- 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.
[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548 --- Comment #7 from Jan Palus --- Confirmed the fix works fine. Thanks! -- 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.
[plasma-nm] [Bug 469398] Network/VPN password dialog is no longer focused when it appears
https://bugs.kde.org/show_bug.cgi?id=469398 Jan Molnar changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #12 from Jan Molnar --- It truly is a duplicate of bug 465751 which describes only a single issue instance. Thank you. *** This bug has been marked as a duplicate of bug 465751 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465751] [5.27 Regression] Password prompt for VPN connection does not have password field in focus by default
https://bugs.kde.org/show_bug.cgi?id=465751 Jan Molnar changed: What|Removed |Added CC||jan.mol...@gmail.com --- Comment #8 from Jan Molnar --- *** Bug 469398 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 469398] Network/VPN password dialog is no longer focused when it appears
https://bugs.kde.org/show_bug.cgi?id=469398 --- Comment #9 from Jan Molnar --- The issue seems to be gone. Probably after update to 5.27.9. Could anyone confirm it please? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548
--- Comment #3 from Jan Palus ---
I've done some debugging and possibly found the culprit.
The assertion di->rodata_size == a_shdr.sh_size failed because left hand side
was 8 while the other was 3. However in readelf output for both stripped binary
and debuginfo file I see rodata size as 3. So assumed right hand side must be
correct. So I've checked why valgrind thinks it's 8 for debuginfo file and
found this:
2482 if (0 == VG_(strncmp)(name, ".rodata", 7)) {
2483 if ((inrx||inrw1) && !di->rodata_present) { /* first .rodata* */
2484 di->rodata_svma = svma;
2485 di->rodata_avma = svma;
2486 di->rodata_size = size;
2487 di->rodata_debug_svma = svma;
2488 } else if ((inrx||inrw1) && di->rodata_present) { /* not first
.rodata* */
2489 Addr tmp = VG_ROUNDUP(di->rodata_size + di->rodata_svma,
alyn);
2490 if (svma == tmp) { /* adjacent to previous .rodata* */
2491di->rodata_size = size + tmp - di->rodata_svma;
2492 } else {
2493BAD(".rodata"); /* is OK, but we cannot handle multiple
.rodata* */
2494 }
2495 }
https://sourceware.org/git/?p=valgrind.git;a=blob;f=coregrind/m_debuginfo/readelf.c;h=fb64ed9769d28e7f64762c8a34ebab8e353bc21f;hb=HEAD#l2482
It extends rodata_size with size of adjacent sections with name starting with
".rodata".
Both debuginfo and stripped binary have adjacent .rodata and .rodata.cst4
sections with size 3 and 4 respectively which I believe after aligning make 8:
[Nr] Name TypeAddress OffSize ES Flg
Lk Inf Al
[12] .rodata PROGBITS0020059c 00059c 03 00 A
0 0 1
[13] .rodata.cst4 PROGBITS002005a0 0005a0 04 04 AM
0 0 4
I would assume same logic for accumulating size is not reflected here:
https://sourceware.org/git/?p=valgrind.git;a=blob;f=coregrind/m_debuginfo/readelf.c;h=fb64ed9769d28e7f64762c8a34ebab8e353bc21f;hb=HEAD#l3362
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 476548] New: valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548
Bug ID: 476548
Summary: valgrind 3.22.0 fails on assertion when loading
debuginfo file produced by mold
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: jpalus+...@fastmail.com
Target Milestone: ---
SUMMARY
After valgrind upgrade to 3.22.0 it started failing with:
valgrind: m_debuginfo/readelf.c:3394 (vgModuleLocal_read_elf_debug): Assertion
'di->rodata_size == a_shdr.sh_size' failed.
when loading debuginfo file produced with mold 2.3.1. Binaries linked with
bfd/lld work fine.
valgrind 3.21.0 works fine.
Also raised in mold under https://github.com/rui314/mold/issues/1139 as it's
not clear who is to blame.
STEPS TO REPRODUCE
1. Build sample c++ binary with debug symbols and link with mold:
g++ -x c++ -g2 -fuse-ld=mold -o test - <
int main() {
std::cout << "hello world" << std::endl;
}
EOF
2. Create debuginfo file:
eu-strip -f test.di test
3. Run valgrind against binary:
valgrind -v ./test
OBSERVED RESULT
valgrind fails:
...
--413198-- Considering /home/users/builder/test.di ..
--413198-- .. CRC is valid
valgrind: m_debuginfo/readelf.c:3394 (vgModuleLocal_read_elf_debug): Assertion
'di->rodata_size == a_shdr.sh_size' failed.
...
EXPECTED RESULT
valgrind works fine
--
You are receiving this mail because:
You are watching all bug changes.
[Tokodon] [Bug 474182] Crash when closing program in ~QQuickAnimatedImage()
https://bugs.kde.org/show_bug.cgi?id=474182 Jan changed: What|Removed |Added CC||jan.iver...@mailbox.org -- 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.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #41 from Jan van Bekkum --- Ik realized that we should have done the reread after I sent my last comment. It now works! Sorry for the confusion. After all it was a configuration error, not a bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #39 from Jan van Bekkum --- We have enabled read and write sidecar on computer C, but the we still don't see tags and labels. Do I understand correctly that the bug that you reported yesterday has to be resolved first. You probably discovered already from the logs that computer A and B have English as system language and computer C (and also D as reported earlier in this chain) use Dutch. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #38 from Jan van Bekkum --- Thanks for your quick response and sorry for not setting up computer C correctly. It was a fresh install and I left all defaults in place. Any reason why sidecar reading and writing is not enabled by default? -- 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.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #34 from Jan van Bekkum --- Video files are too large for an attachment. I uploaded them to WeTransfer. This is the link: https://we.tl/t-gK6yPCoTUQ. The tags and labels of both are not visible on computer C. -- You are receiving this mail because: You are watching all bug changes.
