[plasmashell] [Bug 500494] Since Plasma 6.4, notification appears like normal window of xfce4 at the center of desktop
https://bugs.kde.org/show_bug.cgi?id=500494 Piotr Mierzwinski changed: What|Removed |Added Keywords||wayland CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 500493] New: KRunner doesn’t respond to shortcuts
https://bugs.kde.org/show_bug.cgi?id=500493 Bug ID: 500493 Summary: KRunner doesn’t respond to shortcuts Classification: Plasma Product: krunner Version: 6.3.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrija.urosevi...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY At the boot any default and custom shortcuts for the KRunner work as intended, but the first time I call the KRunner using the shortcut and dismiss it wit escape key, it won’t be able to show the search bar again until I terminate the session(reboot or log out). STEPS TO REPRODUCE 1. run the krunner 2. close it without typing anything inside the search bar 3. run the krunner again - it does not respond OBSERVED RESULT EXPECTED RESULT KRunner should popup even after I dismiss it, like it did in the previous versions of Plasma. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700KF Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080 ADDITIONAL INFORMATION KRunner version is 6.11.0-1 and I am using Wayland. When running krunner in terminal: ➜ ~ krunner QThreadStorage: Thread 0x5e62419ab030 exited after QThreadStorage 4 destroyed QThreadStorage: Thread 0x5e62419ab030 exited after QThreadStorage 3 destroyed ➜ ~ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 500445] digiKam "You have insufficient privileges on database. Following privileges are not assigned to you: CREATE TABLE" after cataloging 300k images and simply restarting digiKam
https://bugs.kde.org/show_bug.cgi?id=500445 --- Comment #11 from David --- F'ing Western Digial and their NAS. So close. I thought I had the "Easy Button". I'll open a case with them and find out if it's possible to expand. Or, I need to find a good docker-compose entry for MariaDB and run it on my swarm (swarm of 2). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500451] Locker turns a fingerprint scanner on before system suspend
https://bugs.kde.org/show_bug.cgi?id=500451 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 481808 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 500499] New: Dolphin ignores XDG_USER_DIRS infrastructure?
https://bugs.kde.org/show_bug.cgi?id=500499 Bug ID: 500499 Summary: Dolphin ignores XDG_USER_DIRS infrastructure? Classification: Applications Product: dolphin Version: 24.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: incan...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Per the Arch Wiki- "xdg-user-dirs is a tool to help manage 'well known' user directories like the desktop folder and the music folder. It also handles localization (i.e. translation) of the filenames." At startup Dolphin shows the users Home, plus the Desktop, Documents, Downloads etc. directories. These latter "well known" directories are precisely the ones xdg-user-dirs is designed to manage. I plan to point all my users "well known" directories to a separate filesystem (partition) separate from the main OS partition. However, having set up the test config in ~/.config/user-dirs.dirs in my own account, I find that Dolphin ignores the folders configured there. STEPS TO REPRODUCE 1. Change the configuration of the XDG_USER_DIRS, either by directly editing ~/.config/user-dirs.dirs, or using the KDE configuration "Locations" tool 2.Start Dolphin. 3.The "well known" dirs in the "Places" sidebar ignore the XDG configuration and instead show the unmodified defaults (e.g. ~/Documents, ~/Videos etc.) OBSERVED RESULT Dolphin ignores the customisation of well known user directories EXPECTED RESULT The Dolphin Places sidebar should be automatically synchronised with the "Locations" settings, which are reflected in ~/.config/user-dirs.dirs SOFTWARE/OS VERSIONS Operating System: KDE neon 6.2 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.11.0-17-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #72 from Marcelo Vanzin --- Not keyboard, but sometimes when the screen layout changes it seems like the mouse doesn't work properly; trying to click on menus and menu items doesn't work properly. Moving the window to a different screen and back seems to fix it. The `kwin --replace` trick doesn't always fix that. So I'm tempted to say different problem... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 500202] Spectacle: Window Under Cursor, with a delay, sometimes fails to present a cross-hair (cursor) – no shot, the Spectacle window does not reappear
https://bugs.kde.org/show_bug.cgi?id=500202 Graham Perrin changed: What|Removed |Added Summary|Spectacle: Window Under |Spectacle: Window Under |Cursor, with a delay, |Cursor, with a delay, |sometimes fails to present |sometimes fails to present |a cursor (the Spectacle |a cross-hair (cursor) – no |window does not reappear) |shot, the Spectacle window ||does not reappear -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 495692] Unable to take screenshots of a window with a context menu in "Window under cursor" mode
https://bugs.kde.org/show_bug.cgi?id=495692 Graham Perrin changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=500202 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500505] Power icon not working
https://bugs.kde.org/show_bug.cgi?id=500505 --- Comment #1 from 권순호 --- Created attachment 178672 --> https://bugs.kde.org/attachment.cgi?id=178672&action=edit When the option is turned off, the icon is displayed normally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499612] Screen freezes briefly when starting Element
https://bugs.kde.org/show_bug.cgi?id=499612 --- Comment #3 from Jakob Petsovits --- Created attachment 178674 --> https://bugs.kde.org/attachment.cgi?id=178674&action=edit Stuttering kwin_wayland trace 2 (5700 Hz sample rate, no initial screen activity) Here's a similar profile, except recorded with -F 5700, which is the maximum it lets me do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499612] Screen freezes briefly when starting Element
https://bugs.kde.org/show_bug.cgi?id=499612 --- Comment #4 from Jakob Petsovits --- Created attachment 178675 --> https://bugs.kde.org/attachment.cgi?id=178675&action=edit Stuttering kwin_wayland trace 3 (5700 Hz sample rate, always moving mouse pointer) For this one, I thought wouldn't it be nice if I kept moving the mouse all throughout so the pause is clearly visible? So this profile is perhaps the clearest insight. Toward the end there are brief input breaks prior to stopping my perf invocation, but the big pause at the beginning is extremely visible and with just the same stacktrace. I could probably take another profile that shows system-wide loads, but this is what I've got right now, it looks actionable enough to act on. Let me know if you need anything else in particular. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493797] screen freezes due to kwin stuck in infinite loop (wayland & x11)
https://bugs.kde.org/show_bug.cgi?id=493797 Marco Rebhan changed: What|Removed |Added CC||m...@dblsaiko.net -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 495692] Unable to take screenshots of a window with a context menu in "Window under cursor" mode
https://bugs.kde.org/show_bug.cgi?id=495692 Graham Perrin changed: What|Removed |Added CC||grahamper...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499927] plasmashell crashed sometimes in QSharedPointer::deref when clicking on the Networks icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=499927 Bug Janitor Service changed: What|Removed |Added Sentry Crash||https://crash-reports.kde.o Report||rg/organizations/kde/issues ||/122628/events/7a7e88098205 ||4ed18e3d035ae30129f4/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #122 from Nate Graham --- Is anyone who was experiencing this in the past unable to reproduce the issue with Plasma 6.3.1 now? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499927] plasmashell crashed sometimes in QSharedPointer::deref when clicking on the Networks icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=499927
--- Comment #5 from Matt Fagnani ---
Created attachment 178676
--> https://bugs.kde.org/attachment.cgi?id=178676&action=edit
plasmashell 6.3.1 trace
I was using Plasma 6.3.1 on Wayland in a Fedora Rawhide live image on bare
metal. I clicked on the Networks icon in the system tray repeatedly.
plasmashell crashed in QSharedPointer::deref with a
trace like I reported here.
Thread 1 (Thread 0x7fef7b8c4d80 (LWP 2816)):
[KCrash Handler]
#4 QSharedPointer::deref (this=0x10) at
/usr/include/qt6/QtCore/qsharedpointer_impl.h:471
#5 QSharedPointer::~QSharedPointer (this=, this=) at
/usr/include/qt6/QtCore/qsharedpointer_impl.h:284
#6 std::destroy_at > (__location=0x10)
at /usr/include/c++/15/bits/stl_construct.h:88
#7 std::_Destroy > (__pointer=0x10) at
/usr/include/c++/15/bits/stl_construct.h:163
#8 std::_Destroy*> (__first=0x10,
__last=0x7ffcdb3a7b310) at /usr/include/c++/15/bits/stl_construct.h:211
#9 std::destroy*> (__first=, __last=0x7ffcdb3a7b310) at /usr/include/c++/15/bits/stl_construct.h:288
#10 QtPrivate::QGenericArrayOps
>::destroyAll (this=0x7ffcdb3a7a40) at
/usr/include/qt6/QtCore/qarraydataops.h:377
#11 QArrayDataPointer
>::~QArrayDataPointer (this=, this=) at
/usr/include/qt6/QtCore/qarraydatapointer.h:109
#12 QArrayDataPointer
>::~QArrayDataPointer (this=, this=) at
/usr/include/qt6/QtCore/qarraydatapointer.h:106
#13 0x7feebc78ced7 in QList
>::~QList (this=, this=) at
/usr/include/qt6/QtCore/qlist.h:83
#14 Handler::requestScanInternal (frame_ptr=0x55ebfbb27b30) at
/usr/src/debug/plasma-nm-6.3.1-1.fc43.x86_64/libs/handler.cpp:674
#15 0x7feebc7999e1 in std::__n4861::coroutine_handle::resume
(this=) at /usr/include/c++/15/coroutine:142
#16
QCoro::detail::QCoroDBusPendingReply::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}::operator()(QDBusPendingCallWatcher*)
(__closure=, watcher=0x55ebfbe7b820) at
/usr/include/qcoro6/qcoro/qcorodbuspendingreply.h:43
#17 QtPrivate::FunctorCall,
QtPrivate::List, void,
QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}>::call(QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}&,
void**)::{lambda()#1}::operator()() const (__closure=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:141
#18 QtPrivate::FunctorCallBase::call_internal,
QtPrivate::List, void,
QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}>::call(QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}&,
void**)::{lambda()#1}>(void**,
QtPrivate::FunctorCall,
QtPrivate::List, void,
QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}>::call(QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}&,
void**)::{lambda()#1}&&) (args=, fn=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:65
#19 QtPrivate::FunctorCall,
QtPrivate::List, void,
QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}>::call(QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}&,
void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:140
#20
QtPrivate::FunctorCallable::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1},
QDBusPendingCallWatcher*>::call,
void>(QCoro::detail::QCoroDBusPendingReply<>::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1}&,
void*, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:362
#21
QtPrivate::QCallableObject::WaitForFinishedOperation::await_suspend(std::__n4861::coroutine_handle)::{lambda(auto:1*)#1},
QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:572
#22 0x7fef7a8c5efa in QtPrivate::QSlotObjectBase::call
(this=0x55ebfcd3dcc0, r=0x55ebfbe7b820, a=0x7ffcdb3a7bf0) at
/usr/src/debug/qt6-qtbase-6.8.2-3.fc43.x86_64/src/corelib/kernel/qobjectdefs_impl.h:486
#23 doActivate (sender=0x55ebfbe7b820, signal_index=3,
argv=argv@entry=0x7ffcdb3a7bf0) at
/usr/src/debug/qt6-qtbase-6.8.2-3.fc43.x86_64/src/corelib/kernel/qobject.cpp:4115
#24 0x7fef7a8bc8a9 in QMetaObject::activate (sender=,
m=m@entry=0x7fef7aed2f00, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffcdb3a7bf0) at
/usr/src/debug/qt6-qtbase-6.8.2-3.fc43.x86_64/src/corelib/kernel/qobject.cpp:4175
#25 0x7fef7ae83471 in QDBusPendingCallWatcher::finished (this=, _t1=) at
/usr/sr
[kstars] [Bug 500506] New: GPhoto on MacOS: Camera open error (-4): Error loading a library
https://bugs.kde.org/show_bug.cgi?id=500506 Bug ID: 500506 Summary: GPhoto on MacOS: Camera open error (-4): Error loading a library Classification: Applications Product: kstars Version: 3.7.5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bast...@blankenburg.net Target Milestone: --- Created attachment 178677 --> https://bugs.kde.org/attachment.cgi?id=178677&action=edit KStars/Ekos verbose log for INDI and CCD SUMMARY STEPS TO REPRODUCE 1. Ensure that ptpcamerad isn't running and mounting cameras. 2. Connect Olympus E-M5 II to computer running KStars. 3. Configure local INDI server with GPhoto CCD driver. 4. Try to start INDI server and connect. OBSERVED RESULT Camera doesn't connect, INDI log shows ``` 2025-02-21T05:31:10: [ERROR] Can not open camera: Power OK? If camera is auto-mounted as external disk storage, please unmount it and disable auto-mount. 2025-02-21T05:31:10: [ERROR] Camera open error (-4): Error loading a library ``` EXPECTED RESULT Camera connects fine. SOFTWARE/OS VERSIONS macOS: Sonoma 14.7.1 ADDITIONAL INFORMATION I've enabled verbose logging for Ekos -> INDI and Drivers -> CCD, and attached the log file here. In my old KStars version (3.6.8), I could connect my Olympus E-M5 II just fine (using a script which periodically kills ptpcamerad every 0.1 seconds to prevent it from mounting the camera, and which I also ran for the new versin). The old Kstars used libindi 2.0.5, while the new one uses 2.1.2. I also saw the same issue with the IndiStarter app: an old version that came with libindi 2.0.2 worked fine, but the new one which bundles 2.1.2 does not, showing the same error. So I think it's a libindi issue with was introduced somewhere between 2.0.5 and 2.1.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500494] Since Plasma 6.4, notification appears like normal window of xfce4 at the center of desktop
https://bugs.kde.org/show_bug.cgi?id=500494 cwo changed: What|Removed |Added CC||cwo@posteo.net Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from cwo --- Thank you for the bug report! Can you please attach a screenshot that shows such a notification? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500492] Widgets are blank (no content) after a reboot, or sleep/wake cycle
https://bugs.kde.org/show_bug.cgi?id=500492 --- Comment #4 from incan...@gmail.com --- Created attachment 178665 --> https://bugs.kde.org/attachment.cgi?id=178665&action=edit Widgets back after a couple of logouts? I did a couple of rapid logout/login cycles to investigate another bug (login styles not sticking) only to realise the missing widgets were now back again! I will try to investigate further to see if this is repeatable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500495] New: Applying screen layout (desktop configuration) and desktop backgrounds to the login screen (SDDM) does not take effect
https://bugs.kde.org/show_bug.cgi?id=500495 Bug ID: 500495 Summary: Applying screen layout (desktop configuration) and desktop backgrounds to the login screen (SDDM) does not take effect Classification: Plasma Product: plasmashell Version: 6.3.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: incan...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY I am logged in as a user with membership of the sudo and admin groups My machine has 3 monitors in a "PLP (portrait-landscape-portrait) configuration, so screen config is important for the machine to be usable However changes to the SDDM desktop config and style do not "stick". After logout the login display uses the default background wallpaper and screen config, leaving 2 out of 3 monitors with displays rotated by 90 degrees STEPS TO REPRODUCE 1. Set a custom Display Configuration and "Desktop and Wallpaper" 2. Open the "Login Screen (SDDM)" system setting 3. Select "Apply Plasma Settings" OBSERVED RESULT One of the default desktop themes, with no customisation of the screen config (i.e. screen position and rotation) is applied EXPECTED RESULT On this config page, there are selection icons for a couple of default configurations (Breeze and Maya), plus an "Apply" button at the bottom of the page. I would expect selecting one of the default themes and hitting "Apply" would set SDDM to use that theme. The fact tat the default themes don't handle things liek screen rotation is annoying, but not surprising. However, given that the "Apply" button exists to apply a selected theme, my expectation was that the "Apply Plasma Settings" button was clearly there for a different purpose, otherwise it would be redundant. What I expected it to do was apply MY CURRENT PLASMA SETTINGS (theme colours, wallpapers, AND screen configuration) to SDDM, so that having spent the time to set up a "sane" desktop config on my account, I could easily apply it the login environment. (Note, if the user needs to authenticate as sudo to alter the config of SDDM, there should be a popup asking for authentication like other admin changes) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.2 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500498] New: Screen content displayed before lock screen when waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=500498 Bug ID: 500498 Summary: Screen content displayed before lock screen when waking up from sleep Classification: I don't know Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kbtr.buffer...@passinbox.com Target Milestone: --- SUMMARY Waking up from sleep, the lock screen takes a second to show up and in the moment, it glitches showing the actual unlocked screen. It's enough time for whoever wakes up the computer to read a good deal of information before the lock screen appears, which turns this into a privacy problem. This is always reproduceable and it does not matter how long you wait between sleeping and waking up, which could rule out the lock delay. And still, if the lock delay was what was happening here, the lock screen wouldn't show up asking for a password anyway. It happens both under X11 and Wayland. Showing the desktop longer on X11 and on Wayland just for a fraction of a second, but still showing it. STEPS TO REPRODUCE 1. Put the computer to sleep (either by clicking the sleep button, or closing the laptop lid, it doesn't matter). 2. Wait a bit, to ensure the computer fully goes to sleep. I wait for my laptop power led to start blinking, you can also go away for a few hours, it makes no difference. 3. Wake the computer up, by pressing any key or opening the laptop lid. OBSERVED RESULT - The laptop wakes up. - The "contents" of the screen are visible for a moment. - The lock screen covers everything and I'm required to type my password. EXPECTED RESULT - The laptop wakes up. - Either: - The lock screen shows up right away, without allowing for any glitching. - If the lock screen takes a moment to show up, the screen should be blank. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 408233] ark cannot drag and drop files to arbitrary apps (e.g. mpv, pcmanfm-qt) due to lack of XDS support
https://bugs.kde.org/show_bug.cgi?id=408233 --- Comment #11 from Neal Gompa --- The issues in comment 8 are partly why GNOME now integrates archive management in Nautilus itself. But they also have the advantage of gvfs having stable paths for the FUSE stuff (we don't have that in KIO). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 500066] Dolphin freezes when trying to open right click context menu on HDD while having selected many files
https://bugs.kde.org/show_bug.cgi?id=500066 TraceyC changed: What|Removed |Added Resolution|--- |BACKTRACE CC||kde...@tlcnet.info Status|REPORTED|NEEDSINFO --- Comment #1 from TraceyC --- Thanks for the bug report. Can you please attach a backtrace of the freeze using the `coredumpctl` command-line program, as detailed in: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 499509] Icons for hidden folders are smaller than non-hidden ones
https://bugs.kde.org/show_bug.cgi?id=499509 --- Comment #11 from TraceyC --- In Bug 500078 this is also affecting folder icons in Details view. It is also linked to having previews enabled. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 500078] Dolphin does not show folder icons correctly since Plasma 6.3 - most hidden and linked folder are small
https://bugs.kde.org/show_bug.cgi?id=500078 TraceyC changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||kde...@tlcnet.info --- Comment #1 from TraceyC --- Thanks for the bug report. This looks to be the same as bug 499509 (which also affects Icon View). Please follow that report for updates. *** This bug has been marked as a duplicate of bug 499509 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 500265] half screen view hides location bar initially
https://bugs.kde.org/show_bug.cgi?id=500265 TraceyC changed: What|Removed |Added CC||kde...@tlcnet.info Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from TraceyC --- I'm not able to reproduce this with Dolphin 24.12.2 or built from git-master - Set Dolphin to Compact mode - Use Meta+Left (or right) to make it take up half the screen I also used quick tiling, and tiling to the top / bottom Can you try creating a new user and seeing if it happens with that user as well? If it does, please let us also know: Linux/KDE Plasma: KDE Plasma Version: - the full version (like 6.2.5) KDE Frameworks Version: Qt Version: Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 499509] Icons for hidden folders are smaller than non-hidden ones
https://bugs.kde.org/show_bug.cgi?id=499509 TraceyC changed: What|Removed |Added CC||deadinside...@gmail.com --- Comment #12 from TraceyC --- *** Bug 500160 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500500] New: kwin does not use PreciseTimers in renderloop.
https://bugs.kde.org/show_bug.cgi?id=500500 Bug ID: 500500 Summary: kwin does not use PreciseTimers in renderloop. Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: dimitromanola...@gmail.com Target Milestone: --- Created attachment 178667 --> https://bugs.kde.org/attachment.cgi?id=178667&action=edit patch to switch timer types When the renderloop timer is contrsucted no default timer type is set, so the default CoarseTimer is used. CoarseTimer can have a +/- 20% timing offset, which is definetely not ideal for a renderloop. Suggest using PreciseTimers for this and other timer critical timers in KWin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500452] Touch Scrolling No Longer Working in Plasma 6.3.1
https://bugs.kde.org/show_bug.cgi?id=500452 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||qydwhotm...@gmail.com Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500454] Using zoom on a trackpad is too aggressive
https://bugs.kde.org/show_bug.cgi?id=500454 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 476047 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 500467] Apps can appear above Spectacle's rectangular region view if they launch after Spectacle does
https://bugs.kde.org/show_bug.cgi?id=500467 Nate Graham changed: What|Removed |Added Severity|normal |minor CC||n...@kde.org Summary|Apps appear above spectacle |Apps can appear above |and can be interacted with |Spectacle's rectangular ||region view if they launch ||after Spectacle does Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Nate Graham --- Can reproduce. Unsure how much we can do to prevent this, though. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 500506] GPhoto on MacOS: Camera open error (-4): Error loading a library
https://bugs.kde.org/show_bug.cgi?id=500506 --- Comment #1 from Bastian --- I've just tried IndiStarter release 2.4.1 which comes with libindi 2.0.7, which also shows the " Camera open error (-4): Error loading a library" problem. So that might indicate that the issue was introduced between libindi 2.0.5 and 2.0.7. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 500432] Extra language option at the top labeled "C", does nothing
https://bugs.kde.org/show_bug.cgi?id=500432 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500309] Some apps don't recognize drawing tablet inputs after upgrading to Plasma 6.3.0
https://bugs.kde.org/show_bug.cgi?id=500309 Nate Graham changed: What|Removed |Added CC||n...@kde.org Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 500506] GPhoto on MacOS: Camera open error (-4): Error loading a library
https://bugs.kde.org/show_bug.cgi?id=500506 --- Comment #2 from Bastian --- Sorry my previous comment was wrong, I didn't realise that I had a running indiserver 2.1.2 instance; 2.0.7 actually works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500441] Having autolock and suspend at the same time breaks lockscreen (can't be unlocked)
https://bugs.kde.org/show_bug.cgi?id=500441 Nate Graham changed: What|Removed |Added Component|general |Screen locking CC||n...@kde.org Severity|critical|grave --- Comment #8 from Nate Graham --- It looks like the lock screen has fallen back to software rendering. This often implies a GPU reset or crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500439] improvement: allow keyboard shortcuts for clipper-icons (action/qrcode/edit/delete)
https://bugs.kde.org/show_bug.cgi?id=500439 Nate Graham changed: What|Removed |Added Severity|normal |wishlist CC||n...@kde.org Version|git-stable-Plasma/6.3 |6.3.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500463] KDE on Parch 6.3.1 Icons and text panel (app taskbar) suddenly started putting up long lasting popups on hover the obscures the currently focussed gadget (it is visually mod
https://bugs.kde.org/show_bug.cgi?id=500463 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED Version|git-stable-Plasma/6.3 |6.3.1 --- Comment #2 from Nate Graham --- I'm afraid this was an intentional change for the Task Manager. If you want to go back to the way things were before, you can disable *all* panel widget tooltips in System Settings > General Behavior > uncheck "Show informational tooltips on hover". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500339] Lockscreen unable to unlock, no reaction when entering password
https://bugs.kde.org/show_bug.cgi?id=500339 --- Comment #12 from Nate Graham --- Are you able to take a phone screenshot of what the lock screen looks like when this has happened? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 500364] bold font
https://bugs.kde.org/show_bug.cgi?id=500364 --- Comment #6 from passy...@gmail.com --- Yes, Source Code Pro has Bold. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500329] Logitech Marble FX Trackball Paste Button not configurable under Wayland
https://bugs.kde.org/show_bug.cgi?id=500329 --- Comment #6 from Jens Westemeier --- My trackball appears in System Settings. Going to "Configure Extra Buttons -> Add Binding" I can press the small button, intended to perform the Paste operation. But how to assign the Paste operation in the second step? I pressed both left&right big buttons, which currently provide the Paste operation, but that does not work. It seems that at that stage only keyboard shortcuts are allowed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482624] Navigating between runner columns with arrow left/right keys is unreliable
https://bugs.kde.org/show_bug.cgi?id=482624 cwo changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #14 from cwo --- (In reply to hernan1342 from comment #11) > Curiously enough, once the keys stop working, the right key works when go to > the "configure application launcher" button after going into the search > field (but can't go back with the left, only go down from there) This bug report is about Application Menu (also called kicker). It's not about Application Launcher (also called kickoff). Kicker does not have a "configure application launcher" button, there's no button to the right of the search field at all, and the search field is at the bottom. You're talking about a different program. Please file a new bug report for this against plasmashell / Application Launcher (Kickoff) Widget. FWIW, I can't reproduce that one either with the steps you gave (except that I clicked the widget otiginally instead of using Meta, as I have the Meta key bound to Kicker at the moment to test some changes I'm making). I can freely move around with the arrow keys in Kickoff as well. So when you file the new bug please be specific about your system and configurations and the steps needed to cause the issue. Trying it in a new user account to see if maybe something is misconfigured in your user account is also a good idea to help us narrow things down. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500330] [plasma-nm] Disconnection but available network icon uses /Devices rather than from /places folder.
https://bugs.kde.org/show_bug.cgi?id=500330 --- Comment #9 from Erwin Iosef --- In panels folder, from 32x32 to 42x42/devices and one network-wired-symbolic.svg in status folder, yes. I think the network-wired image should be picked at panels, rather than devices folder since the icons at the sidemenu for the applets have their roots in the panel. It's not a big deal for Breeze since they all use the same icons regardless of folders anyway. Or the status folder if you feel as if the available networks in the sidemenu are a matter of status rather than available devices. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 499674] Compiling breeze-icons-6.9 exhausts memory on 32-bit hosts
https://bugs.kde.org/show_bug.cgi?id=499674 --- Comment #2 from Dave Flogeras --- Do you think it is worth raising with GCC folks? In my view, at the end of the day, it's compiling ~100M of bytes not C code. This may be overly naive, but I'm not sure why it would consume so much RAM when there's nothing to optimize here. I did try make -j1, with -O0 to no avail here (my Gentoo system default is -O2). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500258] When using DSC, 4K 144Hz screen does not display content after being turned off and back on again until switching VTs
https://bugs.kde.org/show_bug.cgi?id=500258 Justin Slay changed: What|Removed |Added CC||justin.s...@gmail.com --- Comment #2 from Justin Slay --- I have had this issue for a while now (~1 year). Disabling DSC did not resolve the issue for me. Not only, I have been running at 4k@120hz the entire time the issue has presented itself. This is on a single monitor PG48UQ setup. When the monitor comes back on, I will hear the device connected sound, then disconnected sound shortly thereafter. This repeats indefinitely until I switch virtual terminals and back. I can also repro this just by unplugging the HDMI cable from the GPU, and plugging it back in. I have had this issue since at least KDE 6.0, maybe even before it, but I can't remember exactly. Also having issues with SDDM crashing on the NVidia 570 driver, but I believe this is unrelated as it has only just started with the new driver. This just exacerbates the issue because when I would usually switch virtual desktops and back to get a picture/signal back, it now crashes SDDM and I lose my session. Using GDM, this particular issue does not occur. Arch/KDE 6.3 13900K with NVidia 4090 570.86.16 DKMS with kernel 6.13.2/6.13.3. Interestingly enough, KDE "About this system" shows that both my GPUs are my 4090, when that is incorrect. GPU 1 should be the i915 integrated graphics from the Intel chip, even though it is unused and no device plugged into the motherboard outputs. Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900K Memory: 62.6 GiB of RAM Graphics Processor 1: NVIDIA GeForce RTX 4090/PCIe/SSE2 Graphics Processor 2: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z790 AORUS MASTER System Version: -CF $ inxi -G Graphics: Device-1: Intel Raptor Lake-S GT1 [UHD Graphics 770] driver: i915 v: kernel Device-2: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 570.86.16 Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5 compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris gpu: nvidia,nvidia-nvswitch resolution: 3840x2160~120Hz API: EGL v: 1.5 drivers: iris,nvidia platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 570.86.16 renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2 API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib,wayland Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494483] When encrypted external drive is auto-mounted, Disks & Devices applet doesn't recognize that it is mounted, and still offers option to mount it
https://bugs.kde.org/show_bug.cgi?id=494483 Łukasz Konieczny changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Version|6.2.0 |6.3.1 --- Comment #8 from Łukasz Konieczny --- This bug reappeared in Plasma 6.3.1. I'm reopening the bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 500399] opening files from the command line opens new session
https://bugs.kde.org/show_bug.cgi?id=500399 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Cannot reproduce in the almost latest KDevelop master (version 6.2.250370). When a single KDevelop session is open, the files opened from the command line are added to it. When multiple KDevelop sessions are open, the "Pick a Session" dialog allows to choose in which session to open the files. KDevelop 5 is no longer supported. I guess something is wrong with the interprocess communication to the running KDevelop instance(s) on your system. When you run kdevelop from the command line without any arguments, is the existing KDevelop window activated or a new one opened? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 494627] Parent window fades out and re-appears according to window placement mode first time Properties window opened with Qt 6.8.0
https://bugs.kde.org/show_bug.cgi?id=494627 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #27 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/911 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 498211] Between files, inconsistent size of overlay emblem (like link icon) on thumbnailed icons
https://bugs.kde.org/show_bug.cgi?id=498211 --- Comment #32 from Gauthier --- Created attachment 178628 --> https://bugs.kde.org/attachment.cgi?id=178628&action=edit Nextloud icons Dolphin 24.12.1 (In reply to Méven from comment #31) > That's not the same thing as the bug here. > Please don't pollute bug report with unrelated things. Thanks. Sorry for my ignorance, it seemed related since the changes are a direct consequence of what's been discussed here (and this bug report was pointed to from the Nextcloud forum on this issue). Happy to report it elsewhere if here isn't the place. I'm using my spare time to report bugs and do my bits to improve KDE, but as all human, I make mistake. > That's new expected behavior, it depends on the zoom level. Ok, I saw that changing the zoom brings the folder and tick together but it only looks normal at huge zoom levels. Frankly it still looks like a regression compared to 24.12.1 (see screenshot of how it was before). -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 500419] KDevelop error
https://bugs.kde.org/show_bug.cgi?id=500419 Igor Kushnir changed: What|Removed |Added Version|unspecified |5.7.230805 Assignee|kdevelop-bugs-n...@kde.org |m...@svenbrauch.de Product|kdevelop|kdev-python CC||igor...@gmail.com Component|general |Language support -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 495986] Right Click on desktop in Edit Mode says "Enter Edit Mode" instead of "Exit Edit Mode"
https://bugs.kde.org/show_bug.cgi?id=495986 --- Comment #6 from Filip --- Created attachment 178629 --> https://bugs.kde.org/attachment.cgi?id=178629&action=edit plasma 6.3.1 showcase I uploaded a video. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 500401] plasma-kded6.service will not be restarted when crashed unless user restart it manually or re-login
https://bugs.kde.org/show_bug.cgi?id=500401 BryanLiang changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from BryanLiang --- I decide to close the issue as RESOLVED FIXED as the patch has been merged. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500451] New: Locker turns of fingerprint scanner before suspend
https://bugs.kde.org/show_bug.cgi?id=500451 Bug ID: 500451 Summary: Locker turns of fingerprint scanner before suspend Classification: Plasma Product: plasmashell Version: 6.3.0 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Screen locking Assignee: plasma-b...@kde.org Reporter: iamgr...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. I am using this device: https://www.key-id.com/fido2-key-with-windows-hello/ 2. I have installed pam-u2f: https://github.com/Yubico/pam-u2f.git 3. I configured locking in /etc/pam.d/fingerprint as: > auth sufficient pam_u2f.so authfile=/etc/u2f_keys userverification=1 cue OBSERVED RESULT When I close the lid of my MSI Raider GE77HX 12UGS to suspend the system, the LED on the fingerprint reader turns on and stays on until I open the lid again to resume the system. If I remove the device and plug it back in while the system is suspended, the LED does not turn on. However, after opening the lid, the lock screen becomes unresponsive, and I need to unlock the system from TTY. EXPECTED RESULT Before KDE 6.3, the LED was only enabled after opening the lid, and everything worked flawlessly. This looks like a regression. SOFTWARE/OS VERSIONS Operating System: Ubuntu 24.10 (Oracular Oriole) KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.11.0-1010-lowlatency (64-bit) Graphics Platform: Wayland Processors: 24 × 12th Gen Intel® Core™ i7-12800HX Memory: 31.1 ГиБ of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Ti Laptop GPU ADDITIONAL INFORMATION Probably regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500451] Locker turns a fingerprint scanner on before system suspend
https://bugs.kde.org/show_bug.cgi?id=500451 Grief changed: What|Removed |Added Summary|Locker turns fingerprint|Locker turns a fingerprint |scanner ON before suspend |scanner on before system ||suspend -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500451] Locker turns fingerprint scanner ON before suspend
https://bugs.kde.org/show_bug.cgi?id=500451 Grief changed: What|Removed |Added Summary|Locker turns of fingerprint |Locker turns fingerprint |scanner before suspend |scanner ON before suspend -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500452] New: Touch Scrolling No Longer Working in Plasma 6.3.1
https://bugs.kde.org/show_bug.cgi?id=500452 Bug ID: 500452 Summary: Touch Scrolling No Longer Working in Plasma 6.3.1 Classification: Plasma Product: plasmashell Version: 6.3.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) widget Assignee: plasma-b...@kde.org Reporter: dashonww...@whybother.me CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY I'm pretty sure it was working in 6.3.0. Currently using a touch screen device to try and scroll through apps using the application launcher initiates a drag instead. Also can't interact with the scrollbar once you have tried to scroll with touch, so it may fail to be used as a workaround. STEPS TO REPRODUCE 1. Update to 6.3.1 2. Using touchscreen tap the application launcher. 3. Go to all apps or any category that has a long enough list of applications to show the scroll bar. 4. Try to scroll with the touchscreen. OBSERVED RESULT It initiates a drag instead. EXPECTED RESULT Should initiate a scroll like it used to. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C95 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500452] Touch Scrolling No Longer Working in Plasma 6.3.1
https://bugs.kde.org/show_bug.cgi?id=500452 Dashon changed: What|Removed |Added CC||dashonww...@whybother.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 498280] Compositor latency causes input lag
https://bugs.kde.org/show_bug.cgi?id=498280 Rolf Schröder changed: What|Removed |Added CC||rolf.schroeder@limbus-medte ||c.com --- Comment #5 from Rolf Schröder --- I believe I have the same issue. I am running the following system: ``` Operating System: NixOS 24.11 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.6.76 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 8840U w/ Radeon 780M Graphics Memory: 61.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21MCCTO1WW System Version: ThinkPad T14 Gen 5 ``` The machine is completely new so I initially thought this was a hardware problem. I check Windows 11, tty1 as well as Ubuntu Live (24.04, X11) and none of the them could reproduce the lag. Since it works fine on tt1 (i.e. I do not feel any lag while typing), I presume it's KDE/Wayland related and no hardware issue. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 454776] Wishlist: let one control the file index start value and increment
https://bugs.kde.org/show_bug.cgi?id=454776 --- Comment #1 from Sergio --- Would like to advocate again for this enhancement. Yes, it is true that skanpage lets you reorder the pages before saving. Still manually reordering the pages when they can be 20 or more is cumbersome. There is also another usage scenario: You have pages that tend to stick together, so every now and then the scanner ADF pulls in two pages at once and you miss a page. If you realize that after you have saved the pages, you need scan the missing pages and then to manually rename all the files to have them in order. But had you picked 10 as the index increment, you would be able to rename just the missing pages to have the files in the correct order. Again, yes, skanpage lets you reorder the pages, but working with the indexes is faster if you have a lot of pages. ADDITIONAL INFORMATION As an alternative to being able to configure the indexes on save, even better would be to be able to configure the page numbers while scanning. In this way the thumbnails would immediately get in order. Eg., on the side of the scan button I can enter the first page and the page increment. I need to scan duplex and I have a simplex scanner. I set the start page to 1 and the increment to 2 and then I press scan the odd sides. Then I set the start page to the last even page and the increment to -2 and I scan the even pages, in the thumbnails the pages end up in the correct order. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500439] improvement: allow keyboard shortcuts for clipper-icons (action/qrcode/edit/delete)
https://bugs.kde.org/show_bug.cgi?id=500439 --- Comment #3 from slartibar...@gmail.com --- yes, arrow keys work. But, the shortcuts with Alt- work only for invoke action (alt-i), qr-code (alt-q) and delete (alt-r) And yes, they do work in popup (meta-v) and in system-tray. But: Edit is not reachable by shortcut (i tried all letters as shown in the hover-menu but wasn't succesful. I'm using english/us as language), neither in systray nor popup. The problem with arrow-keys is, that you need to select the icon and then press space(!) to invoke the action. Return just closes the popup created by Meta-V. (Not very intuitive, don't you think? :-) So, i would be happy if the (auto-generated shortcut with alt-) also works for 'edit'. Let's shift the focus of this bug-report then to make edit reachable similar to qr/remove/action by shortcut. Maybe it could help, if the hover-menu would indicate the active letter with an underline , similar to the visual guide in application-menus? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500439] improvement: allow keyboard shortcuts for clipper-icons (action/qrcode/edit/delete)
https://bugs.kde.org/show_bug.cgi?id=500439 --- Comment #4 from slartibar...@gmail.com --- sorry... not hover-menu. I was referring to the information-popup that you get when hovering with the mouse over the icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500441] Having autolock and suspend at the same time breaks lockscreen (can't be unlocked)
https://bugs.kde.org/show_bug.cgi?id=500441 cwo changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||cwo@posteo.net Status|REPORTED|NEEDSINFO --- Comment #1 from cwo --- I can't reproduce this using the steps outlined on master - the lock screen allows unlocking without issues. Does the same thing happen if you manually put the computer to sleep (using e.g. the "Sleep" button in the Application Launcher)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500450] New: Weird resizing issues in some OpenGL apps in Plasma 6.3.0
https://bugs.kde.org/show_bug.cgi?id=500450 Bug ID: 500450 Summary: Weird resizing issues in some OpenGL apps in Plasma 6.3.0 Classification: Plasma Product: kwin Version: 6.3.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: eduard.moldova...@outlook.com Target Milestone: --- Created attachment 178627 --> https://bugs.kde.org/attachment.cgi?id=178627&action=edit glxgears resizing bug SUMMARY I have a strange behavior in glxgears and an app i made using SkiaSharp, which internally uses OpenGL. When I resize the window, the content covers it really slow instead of instantly. Since this isssue is also present in glxgears, I assume it’s not my code at fault, since this only started to happen after I upgraded to Plasma 6.3.0. Also, the app runs fine on Windows 11. STEPS TO REPRODUCE 1. Use Plasma 6.3.0 2. Launch glxgears from the terminal 3. Resize the window slowly or rapidly and see how it is redrawn OBSERVED RESULT The contents update really slowly and the drawing falls behind in pace compared to the resizing. It looks as if the surface can't keep up the pace of redrawing with the resizing. EXPECTED RESULT The contents update normally, (almost) instantly following the window's size, like the other apps SOFTWARE/OS VERSION Linux/KDE Plasma: Fedora KDE 41 (Wayland), Kernel version 6.12.13-200 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION I also attached a videos with glxgears being resized, to better observe the behavior -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 498280] Compositor latency causes input lag
https://bugs.kde.org/show_bug.cgi?id=498280 --- Comment #6 from Rolf Schröder --- I could not find any obvious (error) messages related to amdgpu but `sudo cat /sys/kernel/debug/dri//amdgpu_gpu_recover` seems to have helped here, too. I have GPU_ID 1 and 128 (i.e. two subfolders in .../dri) and only `cat` the first one. After a couple of minutes of playing around with the system, my impression is that get lag is gone. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500146] Suggestion to add a convenient customizable timer for screen lock
https://bugs.kde.org/show_bug.cgi?id=500146 cwo changed: What|Removed |Added CC||cwo@posteo.net --- Comment #2 from cwo --- (In reply to Nate Graham from comment #1) > Is there any reason to expect you would remember the new thing you're > proposing, though? Wouldn't it run into the same problem if you needing to > remember to use it? I think the idea is the following: Situation: Time to get away from the computer for a bit, but need some long-running task to continue in the mean time. Current solution: Manually set inhibit. Come back later, computer is still on. Continue working, hopefully remembering to turn the manual block off again. Proposed solution: Manually set "inhitbit for 90 minutes". Come back later, computer is still on (if it's earlier than 90 minutes), or sleeping (if it's later). Resume as needed, no further invention is necessary. In other words, in one case you need to remember two things (setting the block and removing it), while in the other you only need to remember one. And the first one is typically easy to remember, as it's something the user actually wants to do, whereas the other is cleanup after the user has to after what they want to do is complete. It's much easier to remember putting the original on the photocopier if you want to make a copy than remembering to take it with you when you have the copy you wanted. This could be implemented with a timer combo box next to the "Manually Block" button in the applet, similar to the one we have in kcm_powerdevil for choosing the waiting time before sleeping etc. Like [Manually block] [For 90 minutes |v] [Manually block] [until unblocked |v] Seems reasonable to me, and easy enough to understand. (Wording for the indeterminate length case could be tweaked). Though if the user is regularly compiling large projects it probably makes sense to integrate the building with kde-inhibit so it automatically happens, but this is not something we can do for the user, they have to set it up for themselves. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 500431] F-droid - hash error
https://bugs.kde.org/show_bug.cgi?id=500431 --- Comment #2 from roel --- Hallo Bart, I added the KDE release repo to f-droid. I installed also Elisa and this one installed OK. I will add the testing repo, maybe it will work there. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 500453] New: Skanpage keeps proposing to save as PDF even if default format is configured to PNG
https://bugs.kde.org/show_bug.cgi?id=500453 Bug ID: 500453 Summary: Skanpage keeps proposing to save as PDF even if default format is configured to PNG Classification: Applications Product: Skanpage Version: 24.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: sergio.calleg...@gmail.com Target Milestone: --- SUMMARY I have skanpage configured to use png as the default format. Still, if I scan some pages and I try to save them one by one, clicking the 3 dots to the side of the thumbnail, from the second page, the save dialog is pre-configured to pdf. STEPS TO REPRODUCE 1. Configure skanpage to use png as its default format 2. Scan multiple pages 3. Go to first page thumbnail, click on the 3 dots, save image 4. Do the same with the second, third, etc. images OBSERVED RESULT >From the second page, skanpage proposes pdf as the save format EXPECTED RESULT Skanpage should respect the default save format. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.12-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4750HQ CPU @ 2.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Pro Graphics P5200 Manufacturer: Notebook Product Name: W740SU ADDITIONAL INFORMATION Similar issue is marked as fixed in bug 489111, but it is not for the sequence above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500443] Crash when playing with some elements of the plasma shell
https://bugs.kde.org/show_bug.cgi?id=500443 --- Comment #5 from Steve Cossette --- I checked in the PCRE package in fedora, there has been actually no update in a very long time, with 0 bugs reported right now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500443] Crash when playing with some elements of the plasma shell
https://bugs.kde.org/show_bug.cgi?id=500443 Neal Gompa changed: What|Removed |Added CC||ngomp...@gmail.com --- Comment #6 from Neal Gompa --- PCRE2 is still on 10.44 in F42, but was updated to 10.45 two weeks ago in Rawhide: https://src.fedoraproject.org/rpms/pcre2/commits/rawhide -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 500384] Closing System monitor logs error messages to the journal: Helper process terminated abnormally: "The process doesn't have permission to open the capture source"
https://bugs.kde.org/show_bug.cgi?id=500384 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libksysguard/-/merge_requests/397 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499833] Bottom panel of plasma 6.3 appears nicely at startup now but top one still doesn't
https://bugs.kde.org/show_bug.cgi?id=499833 cwo changed: What|Removed |Added Resolution|DUPLICATE |FIXED CC||cwo@posteo.net --- Comment #8 from cwo --- (In reply to PK from comment #7) > If only directly after the startup of Plasma the sensitive zone of the panel > had the same width as the panel! > I could live very well with that! Wait and see if the resolution to bug 499914 fixes this - there seems to be an issue with flexible-width panels not updating their size in response to changes right now. I don't know if this is the case, but the fix should likely be in 6.3.2 and we can revisit the issue after that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500454] New: Using zoom on a trackpad is too aggressive
https://bugs.kde.org/show_bug.cgi?id=500454 Bug ID: 500454 Summary: Using zoom on a trackpad is too aggressive Classification: Plasma Product: plasmashell Version: 6.3.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: antti.s...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Demonstrative video: https://youtu.be/seWvwn6RS60 If I use a trackpad on my a Thinkpad T470s laptop to zoom, it is way too aggressive. In the demonstrative video I try to use as minimal movements as possible at first and the screen almost instantly jerks to full zoom. STEPS TO REPRODUCE 1. Use a Super+Shift+Trackpad to zoom OBSERVED RESULT The zoom speed is way too aggressive EXPECTED RESULT The zoom speed should be so that from top to bottom of the trackpad should be full zoom SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.9.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500390] When certain apps are open, the application launcher shifts to the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=500390 cwo changed: What|Removed |Added CC||cwo@posteo.net --- Comment #10 from cwo --- It seems to me that "items change their position as applications are opened or closed" is the defining characteristic of center-aligned fit-to-content panels (with widgets that change width like a task manager). If there's no apps open or pinned, the menu is going to be in the middle of the screen, and if I have 20 open it'll be way toward the corner. If the user does not want that, they should use a mode that does not do that (such as having task manager/panel left-aligned). The current behavior does not seem optimal though in that it has such a clear mode switch. I think it would make sense to have the popup (in narrow panel mode) centered on the center of the panel, rather than the center of the kickoff item (as long as there is enough space, of course. That way we would get the popup gradually shifting toward the screen edge as the number of task manager entries (/panel width) increases. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 500147] Dolphin crashed on closing somwhere around KFilePlacesItem::~KFilePlacesItem KBookmark::~KBookmark
https://bugs.kde.org/show_bug.cgi?id=500147 Akseli Lahtinen changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Akseli Lahtinen --- Thanks, I will add some bookmarks myself and see if I can get the crash happen too. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 492396] Calender module modifies folder colors for etesync resources
https://bugs.kde.org/show_bug.cgi?id=492396 --- Comment #39 from Akseli Lahtinen --- Sadly I do not know what might be causing the bug, since I can't repro it anymore at all after the changes I mentioned here previously.. :( It may be because i have caldav, not etesync? However keep us posted. It really is annoying bug. > In Korganizer settings, you can also change the calendar colors. I wonder if > changing them from there has any effect? I vaguely remember trying to fix > them from Korganizer side when I first encountered this issue. Did you try this by the way? Maybe you have to set them to something in korganizer, to make sure the colors are updated in right place. Otherwise the field where the colors are expected to be might be still empty and then akonadi(?) downloads the colors. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 500370] The file sent from Android to Mac is displayed successfully, but the Mac does not receive it
https://bugs.kde.org/show_bug.cgi?id=500370 --- Comment #2 from X404 --- Image only has the Mac m processor, there is no problem with the Mac with Intel processor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500199] Incorrect behavior of the menu bar in GTK 3 applications
https://bugs.kde.org/show_bug.cgi?id=500199 manru...@gmail.com changed: What|Removed |Added CC||manru...@gmail.com --- Comment #18 from manru...@gmail.com --- Bug is still here. First seen on plasma 6.3. On 6.2.5 (and 6.2.4) all works fine. My specs: KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 499913] kwin_wayland uses 100% CPU when I drag window to top edge multiple times and freezes desktop
https://bugs.kde.org/show_bug.cgi?id=499913 --- Comment #19 from antonio --- I think it would be useful to also include a thread in the program that monitors CPU usage and kills the process in case of excessive and prolonged CPU usage (for example over 95% CPU for more than 10 consecutive seconds), because killing this process restarts Plasma without affecting any open windows on the screen and can be a solution to prevent the server freeze in case of undetected bugs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500442] Application menu panel widget hangs
https://bugs.kde.org/show_bug.cgi?id=500442 cwo changed: What|Removed |Added CC||cwo@posteo.net Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from cwo --- I can't reproduce this, flicking through the sumbenus for a minute or so and no notable slowdowns. Can you try reproducing the issue with "journalctl --follow" open in a terminal to see if there are any relevant error messages being printed at the same time the issue happens? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 499720] Refresh album view WITHOUT re-scanning thumbnails.
https://bugs.kde.org/show_bug.cgi?id=499720 --- Comment #14 from * --- One more issue with this: I can't make my preferred assignment to work. Shortcuts work as intended when F5 and Ctrl + F5 are set the default way, but if I try to set them to work other way round in keyboard shortcut configuration, the setting is not applied and shortcuts still work like default. I would like to set F5 for new image scan only without searching thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500032] The "Legacy X11 App Support" setting does not work correctly with a different keyboard layout!
https://bugs.kde.org/show_bug.cgi?id=500032 idk changed: What|Removed |Added CC||justamail12...@gmail.com --- Comment #5 from idk --- hi! I was able to reproduce the bug too. the bug only appears on a layout other than English (in my case, Russian) my system: Operating System: EndeavourOS KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Xeon® CPU E5-2640 v3 @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 470 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 495767] Firefox (Flatpak) randomly fails to launch. "journalctl -f" shows multiple compositor errors.
https://bugs.kde.org/show_bug.cgi?id=495767 Fernando M. Muniz changed: What|Removed |Added URL||https://bugzilla.mozilla.or ||g/show_bug.cgi?id=1940341 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500032] The "Legacy X11 App Support" setting does not work correctly with a different keyboard layout!
https://bugs.kde.org/show_bug.cgi?id=500032 Жора Змейкин changed: What|Removed |Added Version|6.2.5 |6.3.1 OS|Other |Linux Platform|Other |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468910] crashes on startup after nested timeline insert. Cannot save nor reuse files
https://bugs.kde.org/show_bug.cgi?id=468910 --- Comment #8 from rlacr...@insa-toulouse.fr --- (In reply to emohr from comment #7) > @rlacroix > Do you have used the official Kdenlive flatpak from flathub > https://flathub.org/apps/org.kde.kdenlive? If not please install Kdenlive > from flathub and try again. I used it at the time. I don't have the file that caused the issue anymore though :/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473078] Cannot render Timeline Preview when it reaches a title
https://bugs.kde.org/show_bug.cgi?id=473078 --- Comment #5 from rlacr...@insa-toulouse.fr --- (In reply to emohr from comment #4) > @rlacroix Do you have used the official OBS flatpak from flathub > https://flathub.org/apps/com.obsproject.Studio ? If not please install OBS > from flathub and try again. > > It could be that you have installed the flatpak from Fedora which might have > issues generate correct MKV files. The project did not contain any recorded clips, neither from OBS nor anything else it was just a title -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500444] Plasmashell crashed after hovering task bar icon with multiple windows
https://bugs.kde.org/show_bug.cgi?id=500444 cwo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||cwo@posteo.net --- Comment #2 from cwo --- Thank you for the bug report! This issue is already being tracked; marking as a duplicate. *** This bug has been marked as a duplicate of bug 491699 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463047] Flatpak version doesn't behave correctly on GNOME Wayland
https://bugs.kde.org/show_bug.cgi?id=463047 Julius Künzel changed: What|Removed |Added CC||julius.kuen...@kde.org --- Comment #9 from Julius Künzel --- The context is that Fedora packages it's own Flatpaks and prioritizes them higher than Flathub. See https://gitlab.com/fedora/sigs/flatpak/fedora-flatpaks#39 and https://pagure.io/fedora-workstation/issue/463 However the bug you describe seems to be indeed on our side. XDG_CURRENT_DESKTOP=kde has been added several years ago, see https://github.com/flathub/org.kde.kdenlive/issues/53 I am pretty sure that we should just remove it now from the Flatpak manifest. I will keep this report closed as I opened https://github.com/flathub/org.kde.kdenlive/pull/514 In a few minutes a test package should show up in this pull request. It would be nice if you could test it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 498211] Between files, inconsistent size of overlay emblem (like link icon) on thumbnailed icons
https://bugs.kde.org/show_bug.cgi?id=498211 --- Comment #31 from Méven --- (In reply to Gauthier from comment #30) > Created attachment 178618 [details] > Nextcloud folder - Dolphin from Git > > I install dolphin from Git, and while there is a clear improvement which > makes it usable again, it's still looking odd. The green tick icon on > Nextcloud folder are way outside to the left of the folder icon itself which > wasn't the case before and which make all folders look unnecessary wide. See > screenshot. That's new expected behavior, it depends on the zoom level. That's not the same thing as the bug here. Please don't pollute bug report with unrelated things. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500443] Crash when playing with some elements of the plasma shell
https://bugs.kde.org/show_bug.cgi?id=500443
cwo changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED|NEEDSINFO
--- Comment #4 from cwo ---
Offending line in mnemonicattached.cpp:
m_mnemonicLabel.replace(QRegularExpression(QLatin1String("\\&([^\\&])")),
QStringLiteral("\\1"));
It fails on JIT-compiling the regular expression while preparing to do the
replace. I don't think there's anything here that could cause a crash from our
end, it's just a fixed regular expression (and the line hasn't changed since
2023). It goes to Qt, which calls PCRE2, which crashes.
Can you check whether there is an issue with PCRE in Fedora 42 Prerelease? That
would also explain why all of them crash.
--
You are receiving this mail because:
You are watching all bug changes.
[kweather] [Bug 500449] New: kweather-plasma-applet not compatible with plasma 6.
https://bugs.kde.org/show_bug.cgi?id=500449 Bug ID: 500449 Summary: kweather-plasma-applet not compatible with plasma 6. Classification: Applications Product: kweather Version: 24.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: edpi...@free.fr CC: espi...@gmail.com Target Milestone: --- My distro just upgraded to plasma 6.3.1 I wanted to try kweather-plasma-applet but it displays: This widget was written for an unknown version of plasma. It is incompatible with version 6 of plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499825] Allow user to use colorful icons in System Tray same as it is allowed for Kickoff (Bug 457077)
https://bugs.kde.org/show_bug.cgi?id=499825 --- Comment #31 from Konrad Materka --- Will this work? :) > find /usr/share/icons/ -iname *-symbolic.* -delete Probably you will need to refresh some caches etc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494664] While muted at 1% volume or higher, the system doesn't use the muted icon.
https://bugs.kde.org/show_bug.cgi?id=494664 Fernando M. Muniz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=496272 --- Comment #10 from Fernando M. Muniz --- 1- Have the speaker set to 0% volume 2- Have the headphone set to 100% volume but mute it with Fn+F1 (or press the speaker icon on the widget) 3- Connect and disconnect the headphone. Result: Only 0% volume is treated as a mute by the OSD. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491699] Occasional crash in QQmlDelegateModelItem::destroyObject() when clicking on task manager icons
https://bugs.kde.org/show_bug.cgi?id=491699 cwo changed: What|Removed |Added CC||victor_su...@hotmail.com --- Comment #2 from cwo --- *** Bug 500444 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 455888] The default shortcut (Ctrl+w) for the overview effect does not close the overview when the keyboard layout is non-Latin
https://bugs.kde.org/show_bug.cgi?id=455888 Spyros Angelis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 448237] 5.90 breaks installing KNS items with dependencies
https://bugs.kde.org/show_bug.cgi?id=448237 Sirsendu Dutta changed: What|Removed |Added Ever confirmed|1 |0 Status|RESOLVED|REPORTED CC||sdutta...@gmail.com Resolution|FIXED |--- --- Comment #15 from Sirsendu Dutta --- this bug is appearing again in KDE Plasma 6.1.5 (Wayland) : Kubuntu oracular 24.10 Way to reproduce the bug is exactly as described before. i am not sure it is due to my system or kde plasma itself. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 455756] Cannot upload files that contain Greek characters in their file name from any chromium based browser
https://bugs.kde.org/show_bug.cgi?id=455756 Spyros Angelis changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453637] Chinese name patterns in kra and bundles are displayed incorrectly.
https://bugs.kde.org/show_bug.cgi?id=453637 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/e29cf8b ||578c177a7090e9301c2cf0e7a87 ||1d5ba7 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Dmitry Kazakov --- Git commit e29cf8b578c177a7090e9301c2cf0e7a871d5ba7 by Dmitry Kazakov, on behalf of Nicholas LaPointe. Committed on 20/02/2025 at 08:34. Pushed by dkazakov into branch 'master'. Treat pattern name as UTF-8 when loading a .pat resource GIMP pattern names are stored as null-terminated UTF-8 strings, but we were loading them as Latin-1. References: (UTF-8) https://developer.gimp.org/core/standards/pat/ (Null-termination) https://gitlab.gnome.org/GNOME/gimp/-/blob/127cd67118727ef9086c829e66b7894c72c2ef98/app/core/gimppattern-header.h#L42 M +1-1libs/pigment/resources/KoPattern.cpp https://invent.kde.org/graphics/krita/-/commit/e29cf8b578c177a7090e9301c2cf0e7a871d5ba7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500450] Weird resizing issues in some OpenGL apps in Plasma 6.3.0
https://bugs.kde.org/show_bug.cgi?id=500450 eduard.moldova...@outlook.com changed: What|Removed |Added CC||eduard.moldovan04@outlook.c ||om -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453637] Chinese name patterns in kra and bundles are displayed incorrectly.
https://bugs.kde.org/show_bug.cgi?id=453637 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/-/commit/e29cf8b |hics/krita/-/commit/343b590 |578c177a7090e9301c2cf0e7a87 |224f9067ef436b9c543fe08944d |1d5ba7 |a9582b --- Comment #3 from Dmitry Kazakov --- Git commit 343b590224f9067ef436b9c543fe08944da9582b by Dmitry Kazakov. Committed on 20/02/2025 at 08:37. Pushed by dkazakov into branch 'krita/5.2'. Treat pattern name as UTF-8 when loading a .pat resource GIMP pattern names are stored as null-terminated UTF-8 strings, but we were loading them as Latin-1. References: (UTF-8) https://developer.gimp.org/core/standards/pat/ (Null-termination) https://gitlab.gnome.org/GNOME/gimp/-/blob/127cd67118727ef9086c829e66b7894c72c2ef98/app/core/gimppattern-header.h#L42 (cherry picked from commit e29cf8b578c177a7090e9301c2cf0e7a871d5ba7) Co-authored-by: Nicholas LaPointe M +1-1libs/pigment/resources/KoPattern.cpp https://invent.kde.org/graphics/krita/-/commit/343b590224f9067ef436b9c543fe08944da9582b -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 496272] Request: Create two visually distinct mute icons
https://bugs.kde.org/show_bug.cgi?id=496272 Fernando M. Muniz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=494664 -- You are receiving this mail because: You are watching all bug changes.
