[Discover] [Bug 485007] Discover random crash
https://bugs.kde.org/show_bug.cgi?id=485007 Derek Enz changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Derek Enz --- This bug is no longer reproducible. Discover seems stable. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485007] Discover random crash
https://bugs.kde.org/show_bug.cgi?id=485007 --- Comment #3 from Derek Enz --- Since the last Fedora KDE update, Discover now seems stable. Cannot reproduce the issue. Thanks Derek Enz On Fri, May 3, 2024 at 5:24 AM Harald Sitter wrote: > https://bugs.kde.org/show_bug.cgi?id=485007 > > Harald Sitter changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > CC||sit...@kde.org > Status|REPORTED|NEEDSINFO > > --- Comment #2 from Harald Sitter --- > Random is the correct word there :) > > Is this still reproducible? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468955] Triangular mouse filtering does not work at all in RTL (Right-to-Left) mode
https://bugs.kde.org/show_bug.cgi?id=468955 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com --- Comment #2 from Derek Christ --- The issue can also be reproduced when the option "New tasks appear: To the right" is enabled, even without an RTL language. A vertical panel layout is also affected. I might be able to look into this. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485007] Discover random crash
https://bugs.kde.org/show_bug.cgi?id=485007 --- Comment #1 from Derek Enz --- kf.newstuff.core: The file could not be parsed. kf.newstuff.core: The file could not be parsed. org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false adding empty sources model QStandardItemModel(0x55db0e4df760) qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" QObject::startTimer: Timers cannot have negative intervals qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:330:5: QML OverlaySheet: Binding loop detected for property "implicitHeight" qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene. invalid kns backend! "/usr/share/knsrcfiles/systemmonitor-faces.knsrc" because: "Backend System monitor Sensor Display Styles took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "systemmonitor-faces.knsrc" invalid kns backend! "/usr/share/knsrcfiles/systemmonitor-presets.knsrc" because: "Backend System monitor Sensor Presets took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "systemmonitor-presets.knsrc" org.kde.plasma.libdiscover: last stream isn't over yet Filters() ResourcesProxyModel(0x55db0e76d6c0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e68e010, name = "Games"),) ResourcesProxyModel(0x55db0dff5fc0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e682190, name = "Developer Tools"),) ResourcesProxyModel(0x55db0f1f3410) invalid kns backend! "/usr/share/knsrcfiles/aurorae.knsrc" because: "Backend Aurorae Window Decorations took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "aurorae.knsrc" org.kde.plasma.libdiscover: last stream isn't over yet Filters() ResourcesProxyModel(0x55db0e76d6c0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e68e010, name = "Games"),) ResourcesProxyModel(0x55db0dff5fc0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e682190, name = "Developer Tools"),) ResourcesProxyModel(0x55db0f1f3410) invalid kns backend! "/usr/share/knsrcfiles/kwineffect.knsrc" because: "Backend Desktop Effects took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "kwineffect.knsrc" org.kde.plasma.libdiscover: last stream isn't over yet Filters() ResourcesProxyModel(0x55db0e76d6c0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e68e010, name = "Games"),) ResourcesProxyModel(0x55db0dff5fc0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e682190, name = "Developer Tools"),) ResourcesProxyModel(0x55db0f1f3410) invalid kns backend! "/usr/share/knsrcfiles/kwinscripts.knsrc" because: "Backend Window Manager Scripts took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "kwinscripts.knsrc" org.kde.plasma.libdiscover: last stream isn't over yet Filters() ResourcesProxyModel(0x55db0e76d6c0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e68e010, name = "Games"),) ResourcesProxyModel(0x55db0dff5fc0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e682190, name = "Developer Tools"),) ResourcesProxyModel(0x55db0f1f3410) invalid kns backend! "/usr/share/knsrcfiles/kwinswitcher.knsrc" because: "Backend Window Manager Switching Layouts took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "kwinswitcher.knsrc" org.kde.plasma.libdiscover: last stream isn't over yet Filters() ResourcesProxyModel(0x55db0e76d6c0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e68e010, name = "Games"),) ResourcesProxyModel(0x55db0dff5fc0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e682190, name = "Developer Tools"),) ResourcesProxyModel(0x55db0f1f3410) invalid kns backend! "/usr/share/knsrcfiles/window-decorations.knsrc" because: "Backend Window Decorations took too long to initialize" org.kde.plasma.libdiscover: Discarding invalid backend "window-decorations.knsrc" org.kde.plasma.libdiscover: last stream isn't over yet Filters() ResourcesProxyModel(0x55db0e76d6c0) org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55db0e68e010, name = "Games"),) ResourcesProxyMo
[Discover] [Bug 485007] New: Discover random crash
https://bugs.kde.org/show_bug.cgi?id=485007 Bug ID: 485007 Summary: Discover random crash Classification: Applications Product: Discover Version: 6.0.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: derek...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (6.0.3) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.8.2-300.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 40 (KDE Plasma Prerelease)" DrKonqi: 6.0.3 [CoredumpBackend] -- Information about the crash: Discover will just crash. It happens when searching for apps or after running an update. Sometimes after logging into my machine without even using Discover, I'll get a message saying it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault This GDB supports auto-downloading debuginfo from the following URLs: <https://debuginfod.fedoraproject.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. [New LWP 23814] [New LWP 23816] [New LWP 23819] [New LWP 23818] [New LWP 23815] [New LWP 23821] [New LWP 23817] [New LWP 23822] [New LWP 23820] [New LWP 23823] [New LWP 23876] [New LWP 23834] [New LWP 23874] [New LWP 23835] [New LWP 23845] [New LWP 23906] [New LWP 23832] [New LWP 23864] [New LWP 23846] [New LWP 23844] [New LWP 23831] [New LWP 23830] [New LWP 23907] [New LWP 23842] [New LWP 23877] [New LWP 23833] [New LWP 23884] [New LWP 23879] [New LWP 23878] [New LWP 23875] [New LWP 23885] [New LWP 23880] [New LWP 23843] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/plasma-discover'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f27880ab144 in __pthread_kill_implementation () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f2783c80b00 (LWP 23814))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x7f2783c80b00 (LWP 23814))] Thread 33 (Thread 0x7f273a0006c0 (LWP 23843)): #0 0x7f278812918d in syscall () from /lib64/libc.so.6 #1 0x7f27878d183d in g_cond_wait () from /lib64/libglib-2.0.so.0 #2 0x7f278783e58b in g_async_queue_pop_intern_unlocked () from /lib64/libglib-2.0.so.0 #3 0x7f27878a4a93 in g_thread_pool_spawn_thread () from /lib64/libglib-2.0.so.0 #4 0x7f27878a38a3 in g_thread_proxy () from /lib64/libglib-2.0.so.0 #5 0x7f27880a91b7 in start_thread () from /lib64/libc.so.6 #6 0x7f278812b39c in clone3 () from /lib64/libc.so.6 Thread 32 (Thread 0x7f26ff4006c0 (LWP 23880)): #0 0x7f27880a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7f27880a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f276d09d6ed in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f276d07b34b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f276d09d61c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f27880a91b7 in start_thread () from /lib64/libc.so.6 #6 0x7f278812b39c in clone3 () from /lib64/libc.so.6 Thread 31 (Thread 0x7f26f3e006c0 (LWP 23885)): #0 0x7f27880a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7f27880a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f276d09d6ed in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f276d07b34b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f276d09d61c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f27880a91b7 in start_thread () from /lib64/libc.so.6 #6 0x7f278812b39c in clone3 () from /lib64/libc.so.6 Thread 30 (Thread 0x7f27166006c0 (LWP 23875)): #0 0x7f27880a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7f27880a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f276d09d6ed in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f276d07b34b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f276d09d61c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f27880a91b7 in start_thread () from /lib64/libc.so.6 #6 0x7f278812b39c in clone3 () from /lib64/libc.so.6 Thread 29 (Thread 0x7f2704e006c0 (LWP 23878)): #0 0x7f27880a5919 in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7f27880a82e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f276d09d6ed in cnd_wait () from /usr/li
[kde] [Bug 485005] New: Bottom Taskbar stays to the left after resizing and selecting centered.
https://bugs.kde.org/show_bug.cgi?id=485005 Bug ID: 485005 Summary: Bottom Taskbar stays to the left after resizing and selecting centered. Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: derek...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Bottom Taskbar stays to the left after resizing and selecting centered. If I log out and back in the task bar then moves to the desired location. STEPS TO REPRODUCE 1. Right click on taskbar and select edit mode. 2. Select width and resize. 3. Select alignment and select centered. OBSERVED RESULT I can resize but when centered is selected the task bar stays to the left. I have to logout and log back in for the taskbar to move to the center position. EXPECTED RESULT After resizing the task bar and selecting centered, the taskbar should automatically move to the center. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #114 from Derek --- Nvidia 550.67 update today seems to have fixed a lot of the issues I was experiencing, only been about 30 minutes but everything that would lock the display up before seems to be going smooth. Fingers are crossed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481984] Flickering menus on the web.
https://bugs.kde.org/show_bug.cgi?id=481984 --- Comment #3 from Derek --- (In reply to Nate Graham from comment #2) > Does it happen in Firefox? No. The scrollbar also flickers in sync with the flickering of the menu's and the menu will flicker when moving the mouse or scrolling after closing it like old frames are displaying. link to video of the flickering. https://streamable.com/znwdze Other symptoms in chromium browsers is hovering the chrome menu in the top right, the three dot menu, it will display the highlighted entry on hover but that lags and jumps all around. When the mouse enters the window everything on the page flickers and even as I type this right now everything flickers in the top menu and when I erase text it will delete and then flicker back into view for a second after it was deleted. It just seems like a general lag in chromium and it bogs everything else down. Only does this in Wayland as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481984] New: Flickering menus on the web.
https://bugs.kde.org/show_bug.cgi?id=481984 Bug ID: 481984 Summary: Flickering menus on the web. Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dcostr...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When you open menu's on websites, Youtube for example and hover the dropdown notification menu it starts a flickering/blinking. Not sure if it's a mouse tracking type of problem or something with plasma as it started happening after upgrading to plasma 6. STEPS TO REPRODUCE 1. Open chromium based browser and navigate to Youtube 2. Open the notification dropdown and hover the mouse around in the menu and let it sit there a minute OBSERVED RESULT Dropdown menu's flicker SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen Threadripper PRO 5945WX 12-Cores Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA T1000 8GB/PCIe/SSE2 Manufacturer: LENOVO Product Name: 30E000MEUS System Version: ThinkStation P620 -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 405022] KFind does not offer DELETE in right-click menu - only 'Move to Wastebin'
https://bugs.kde.org/show_bug.cgi?id=405022 Derek changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #5 from Derek --- Dolphin in more recent times offers 'delete' via Shift+Del (or holding Shift while in the context menu of a file changes 'move to wastebin' to 'delete'). Rather than the workaround, i think it would be nice if Kfind had consistent operation with Dolphin. This is obviously a nice to have, it's not a bug and with Plasma 6 the focus right now this will be a low priority in the scheme of things. But i don't think it should be closed. It seems a very sensible thing to do, when time is available for someone to do it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 --- Comment #9 from Derek Graham --- I installed the Unstable Neon and same thing on there -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 --- Comment #8 from Derek Graham --- PID: 65235 (kwin_wayland) UID: 1000 (dgraham) GID: 1001 (dgraham) Signal: 11 (SEGV) Timestamp: Thu 2023-12-21 22:23:43 CST (1h 48min ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :0 --xwayland-xauthority /run/user/1000/xauth_DAFtxC --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (dgraham) Boot ID: c0e7b59540204a49a096d559db1ee3eb Machine ID: 1aa718c232084f139d062a89c4e98d0e Hostname: Mulder Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.c0e7b59540204a49a096d559db1ee3eb.65235.170321902300.zst (present) Size on Disk: 7.9M Message: Process 65235 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 65235: #0 0x7f22ede1d16c n/a (libKF6ConfigCore.so.6 + 0x2c16c) #1 0x7f22ede51e39 n/a (libKF6ConfigCore.so.6 + 0x60e39) #2 0x7f22ede4948e _ZN19KCoreConfigSkeletonD2Ev (libKF6ConfigCore.so.6 + 0x5848e) #3 0x7f22e5d5fc08 n/a (oxygen6.so + 0xc6c08) #4 0x7f22ec05ecc6 n/a (libc.so.6 + 0x40cc6) #5 0x7f22ec05ee10 exit (libc.so.6 + 0x40e10) #6 0x7f22ec045cd7 n/a (libc.so.6 + 0x27cd7) #7 0x7f22ec045d8a __libc_start_main (libc.so.6 + 0x27d8a) #8 0x5621272317a5 n/a (kwin_wayland + 0x5c7a5) Stack trace of thread 65264: #0 0x7f22ec12c73d syscall (libc.so.6 + 0x10e73d) #1 0x7f22ec7a629a _ZN14QMetaCallEventD2Ev (libQt6Core.so.6 + 0x1a629a) #2 0x7f22ec7a62bd _ZN14QMetaCallEventD0Ev (libQt6Core.so.6 + 0x1a62bd) #3 0x7f22ec762e05 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x162e05) #4 0x7f22ec99ead4 n/a (libQt6Core.so.6 + 0x39ead4) #5 0x7f22eafb9f69 n/a (libglib-2.0.so.0 + 0x59f69) #6 0x7f22eb018367 n/a (libglib-2.0.so.0 + 0xb8367) #7 0x7f22eafb8162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #8 0x7f22ec99d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #9 0x7f22ec76cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #10 0x7f22ec84a13f _ZN7QThread4execEv (libQt6Core.so.6 + 0x24a13f) #11 0x7f22ed48995f n/a (libQt6DBus.so.6 + 0x2f95f) #12 0x7f22ec8c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #13 0x7f22ec0aa9eb n/a (libc.so.6 + 0x8c9eb) #14 0x7f22ec12e7cc n/a (libc.so.6 + 0x1107cc) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 --- Comment #6 from Derek Graham --- Hopefully that helps -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 --- Comment #5 from Derek Graham --- PID: 65384 (kded6) UID: 1000 (dgraham) GID: 1001 (dgraham) Signal: 11 (SEGV) Timestamp: Thu 2023-12-21 22:23:42 CST (1h 34min ago) Command Line: /usr/bin/kded6 Executable: /usr/bin/kded6 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kded6.service Unit: user@1000.service User Unit: plasma-kded6.service Slice: user-1000.slice Owner UID: 1000 (dgraham) Boot ID: c0e7b59540204a49a096d559db1ee3eb Machine ID: 1aa718c232084f139d062a89c4e98d0e Hostname: Mulder Storage: /var/lib/systemd/coredump/core.kded6.1000.c0e7b59540204a49a096d559db1ee3eb.65384.170321902200.zst (present) Size on Disk: 4.2M Message: Process 65384 (kded6) of user 1000 dumped core. Stack trace of thread 65384: #0 0x7f7b0d959a49 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x5a49) #1 0x7f7b0ba5c710 n/a (libc.so.6 + 0x3e710) #2 0x7f7b0d17116c n/a (libKF6ConfigCore.so.6 + 0x2c16c) #3 0x7f7b0d1a5e39 n/a (libKF6ConfigCore.so.6 + 0x60e39) #4 0x7f7b0d19d48e _ZN19KCoreConfigSkeletonD2Ev (libKF6ConfigCore.so.6 + 0x5848e) #5 0x7f7aff74fc08 n/a (oxygen6.so + 0xc6c08) #6 0x7f7b0ba5ecc6 n/a (libc.so.6 + 0x40cc6) #7 0x7f7b0ba5ee10 exit (libc.so.6 + 0x40e10) #8 0x7f7b0ba45cd7 n/a (libc.so.6 + 0x27cd7) #9 0x7f7b0ba45d8a __libc_start_main (libc.so.6 + 0x27d8a) #10 0x560f4ee2f765 n/a (kded6 + 0x7765) Stack trace of thread 65392: #0 0x7f7b0bb20f6f __poll (libc.so.6 + 0x102f6f) #1 0x7f7b0b8ea2b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x7f7b0b88a162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x7f7b0c39d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #4 0x7f7b0c16cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #5 0x7f7b0c24a13f _ZN7QThread4execEv (libQt6Core.so.6 + 0x24a13f) #6 0x7f7b0cfcc95f n/a (libQt6DBus.so.6 + 0x2f95f) #7 0x7f7b0c2c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #8 0x7f7b0baaa9eb n/a (libc.so.6 + 0x8c9eb) #9 0x7f7b0bb2e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 65448: #0 0x7f7b0bb2c73d syscall (libc.so.6 + 0x10e73d) #1 0x7f7b0b8e52f7 g_cond_wait (libglib-2.0.so.0 + 0xb32f7) #2 0x7f7b0b8571b4 n/a (libglib-2.0.so.0 + 0x251b4) #3 0x7f7b0b8bfa8e n/a (libglib-2.0.so.0 + 0x8da8e) #4 0x7f7b0b8bda05 n/a (libglib-2.0.so.0 + 0x8ba05) #5 0x7f7b0baaa9eb n/a (libc.so.6 + 0x8c9eb) #6 0x7f7b0bb2e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 65450: #0 0x7f7b0bb20f6f __poll (libc.so.6 + 0x102f6f) #1 0x7f7b0b8ea2b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x7f7b0b88cb97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97) #3 0x7f7b052a319c n/a (libgio-2.0.so.0 + 0x11219c) #4 0x7f7b0b8bda05 n/a (libglib-2.0.so.0 + 0x8ba05) #5 0x7f7b0baaa9eb n/a (libc.so.6 + 0x8c9eb) #6 0x7f7b0bb2e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 65449: #0 0x7f7b0bb20f6f __poll (libc.so.6 + 0x102f6f) #1 0x7f7b0b8ea2b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x7f7b0b88a162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x7f7b0b88a1b2 n/a (libglib-2.0.so.0 + 0x581b2) #4 0x7f7b0b8bda05 n/a (libglib-2.0.so.0 + 0x8ba05) #5 0x7f7b0baaa9eb n/a (libc.so.6 + 0x8c9eb) #6 0x7f7b0bb2e7cc n/a (libc.so.6 + 0x1107cc) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 --- Comment #4 from Derek Graham --- PID: 2951 (baloo_file) UID: 1000 (dgraham) GID: 1001 (dgraham) Signal: 6 (ABRT) Timestamp: Thu 2023-12-21 22:31:53 CST (1h 26min ago) Command Line: /usr/lib/kf6/baloo_file Executable: /usr/lib/kf6/baloo_file Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service Unit: user@1000.service User Unit: kde-baloo.service Slice: user-1000.slice Owner UID: 1000 (dgraham) Boot ID: c07b0aa1b2ef40d4b344cd006bcd202c Machine ID: 1aa718c232084f139d062a89c4e98d0e Hostname: Mulder Storage: /var/lib/systemd/coredump/core.baloo_file.1000.c07b0aa1b2ef40d4b344cd006bcd202c.2951.170321951300.zst (present) Size on Disk: 1.2M Message: Process 2951 (baloo_file) of user 1000 dumped core. Stack trace of thread 4242: #0 0x7f73ac0ac83c n/a (libc.so.6 + 0x8e83c) #1 0x7f73ac05c668 raise (libc.so.6 + 0x3e668) #2 0x7f73acf978a0 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x58a0) #3 0x7f73ac05c710 n/a (libc.so.6 + 0x3e710) #4 0x7f73ac0ac83c n/a (libc.so.6 + 0x8e83c) #5 0x7f73ac05c668 raise (libc.so.6 + 0x3e668) #6 0x7f73ac0444b8 abort (libc.so.6 + 0x264b8) #7 0x7f73ac6b3924 n/a (libQt6Core.so.6 + 0xb3924) #8 0x7f73ac6b4135 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0xb4135) #9 0x7f73ac6b2770 _Z9qt_assertPKcS0_i (libQt6Core.so.6 + 0xb2770) #10 0x561967168e8f n/a (baloo_file + 0x10e8f) #11 0x7f73ac8cfcf5 n/a (libQt6Core.so.6 + 0x2cfcf5) #12 0x7f73ac8c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #13 0x7f73ac0aa9eb n/a (libc.so.6 + 0x8c9eb) #14 0x7f73ac12e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 2957: #0 0x7f73ac120f6f __poll (libc.so.6 + 0x102f6f) #1 0x7f73aaf6c2b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x7f73aaf0c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x7f73ac99d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #4 0x7f73ac76cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #5 0x7f73ac84a13f _ZN7QThread4execEv (libQt6Core.so.6 + 0x24a13f) #6 0x7f73acca995f n/a (libQt6DBus.so.6 + 0x2f95f) #7 0x7f73ac8c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #8 0x7f73ac0aa9eb n/a (libc.so.6 + 0x8c9eb) #9 0x7f73ac12e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 2951: #0 0x7f73ac12206f write (libc.so.6 + 0x10406f) #1 0x7f73aaf5beab n/a (libglib-2.0.so.0 + 0xa7eab) #2 0x7f73ac761b65 _ZN16QCoreApplication9postEventEP7QObjectP6QEventi (libQt6Core.so.6 + 0x161b65) #3 0x7f73ac7b3a5a n/a (libQt6Core.so.6 + 0x1b3a5a) #4 0x7f73ac7b9fc1 n/a (libQt6Core.so.6 + 0x1b9fc1) #5 0x7f73acc9ee53 n/a (libQt6DBus.so.6 + 0x24e53) #6 0x7f73acca4dca n/a (libQt6DBus.so.6 + 0x2adca) #7 0x7f73ac7ba03c n/a (libQt6Core.so.6 + 0x1ba03c) #8 0x561967173323 n/a (baloo_file + 0x1b323) #9 0x7f73ac7a5447 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1a5447) #10 0x7f73ac7629fc _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x1629fc) #11 0x7f73ac762dfb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x162dfb) #12 0x7f73ac99ead4 n/a (libQt6Core.so.6 + 0x39ead4) #13 0x7f73aaf0df69 n/a (libglib-2.0.so.0 + 0x59f69) #14 0x7f73aaf6c367 n/a (libglib-2.0.so.0 + 0xb8367) #15 0x7f73aaf0c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #16 0x7f73ac99d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #17 0x7f73ac76cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #18 0x7f73ac765518 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x165518) #19 0x56196716b5f3 n/a (baloo_file + 0x135f3) #20 0x7f73ac045cd0 n/a (libc.so.6 + 0x27cd0) #21 0x7f73ac045d8a __libc_start_main (libc.so.6 + 0x27d8a) #22 0x56196716b745 n
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 --- Comment #3 from Derek Graham --- PID: 65235 (kwin_wayland) UID: 1000 (dgraham) GID: 1001 (dgraham) Signal: 11 (SEGV) Timestamp: Thu 2023-12-21 22:23:43 CST (1h 31min ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :0 --xwayland-xauthority /run/user/1000/xauth_DAFtxC --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (dgraham) Boot ID: c0e7b59540204a49a096d559db1ee3eb Machine ID: 1aa718c232084f139d062a89c4e98d0e Hostname: Mulder Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.c0e7b59540204a49a096d559db1ee3eb.65235.170321902300.zst (inaccessible) Message: Process 65235 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 65235: #0 0x7f22ede1d16c n/a (libKF6ConfigCore.so.6 + 0x2c16c) #1 0x7f22ede51e39 n/a (libKF6ConfigCore.so.6 + 0x60e39) #2 0x7f22ede4948e _ZN19KCoreConfigSkeletonD2Ev (libKF6ConfigCore.so.6 + 0x5848e) #3 0x7f22e5d5fc08 n/a (oxygen6.so + 0xc6c08) #4 0x7f22ec05ecc6 n/a (libc.so.6 + 0x40cc6) #5 0x7f22ec05ee10 exit (libc.so.6 + 0x40e10) #6 0x7f22ec045cd7 n/a (libc.so.6 + 0x27cd7) #7 0x7f22ec045d8a __libc_start_main (libc.so.6 + 0x27d8a) #8 0x5621272317a5 n/a (kwin_wayland + 0x5c7a5) Stack trace of thread 65264: #0 0x7f22ec12c73d syscall (libc.so.6 + 0x10e73d) #1 0x7f22ec7a629a _ZN14QMetaCallEventD2Ev (libQt6Core.so.6 + 0x1a629a) #2 0x7f22ec7a62bd _ZN14QMetaCallEventD0Ev (libQt6Core.so.6 + 0x1a62bd) #3 0x7f22ec762e05 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x162e05) #4 0x7f22ec99ead4 n/a (libQt6Core.so.6 + 0x39ead4) #5 0x7f22eafb9f69 n/a (libglib-2.0.so.0 + 0x59f69) #6 0x7f22eb018367 n/a (libglib-2.0.so.0 + 0xb8367) #7 0x7f22eafb8162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #8 0x7f22ec99d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #9 0x7f22ec76cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #10 0x7f22ec84a13f _ZN7QThread4execEv (libQt6Core.so.6 + 0x24a13f) #11 0x7f22ed48995f n/a (libQt6DBus.so.6 + 0x2f95f) #12 0x7f22ec8c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #13 0x7f22ec0aa9eb n/a (libc.so.6 + 0x8c9eb) #14 0x7f22ec12e7cc n/a (libc.so.6 + 0x1107cc) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank
https://bugs.kde.org/show_bug.cgi?id=478865 Derek Graham changed: What|Removed |Added CC||derekagraha...@icloud.com --- Comment #1 from Derek Graham --- Created attachment 164355 --> https://bugs.kde.org/attachment.cgi?id=164355=edit Photo of Issue Adding a photo of what I see -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] New: Multiple Screen with one display being blank
https://bugs.kde.org/show_bug.cgi?id=478865 Bug ID: 478865 Summary: Multiple Screen with one display being blank Classification: Plasma Product: kwin Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: derekagraha...@icloud.com Target Milestone: --- Created attachment 164354 --> https://bugs.kde.org/attachment.cgi?id=164354=edit Journal Log 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 *** https://pastebin.com/Ra6EDYQM https://pastebin.com/ek3TZQUP STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT One Screen displays correctly other is completely black EXPECTED RESULT Both Screens work, it works fine with x11. Just not with Wayland. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Garuda Linux 6.6.7-zen1-1-zen(64 bit) (available in About System) KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Intel Internal Built in Video HD 2500 AMD Radeon RX 550 9.415] (II) LoadModule: "intel" [ 9.416] (WW) Warning, couldn't open module intel [ 9.416] (EE) Failed to load module "intel" (module does not exist, 0) [ 9.416] (II) LoadModule: "amdgpu" [ 9.416] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so [ 9.447] (II) Module amdgpu: vendor="X.Org Foundation" [ 9.447]compiled for 1.21.1.7, module version = 23.0.0 [ 9.447]Module class: X.Org Video Driver [ 9.447]ABI class: X.Org Video Driver, version 25.2 [ 9.447] (II) LoadModule: "ati" [ 9.447] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [ 9.448] (II) Module ati: vendor="X.Org Foundation" [ 9.448]compiled for 1.21.1.8, module version = 22.0.0 [ 9.448]Module class: X.Org Video Driver [ 9.448]ABI class: X.Org Video Driver, version 25.2 [ 9.467] (II) LoadModule: "modesetting" [ 9.467] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 9.469] (II) Module modesetting: vendor="X.Org Foundation" [ 9.469]compiled for 1.21.1.10, module version = 1.21.1 [ 9.469]Module class: X.Org Video Driver [ 9.469]ABI class: X.Org Video Driver, version 25.2 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 457091] GPX thumbnails/previews do not work any more
https://bugs.kde.org/show_bug.cgi?id=457091 Derek Christ changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Derek Christ --- On both of my machines the feature just started to work again without changing anything. So I guess some code change fixed this bug. Closing. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 475201] New: Encrypted EXT4 USB HDD partitions created by KDE Partition Manager are read-only.
https://bugs.kde.org/show_bug.cgi?id=475201 Bug ID: 475201 Summary: Encrypted EXT4 USB HDD partitions created by KDE Partition Manager are read-only. Classification: Applications Product: partitionmanager Version: 23.04.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: linux.9v...@simplelogin.co Target Milestone: --- SUMMARY KDE Partition Manager creates encrypted EXT4 USB HDD partitions that are read only as the user - requires sudo to be able to write. STEPS TO REPRODUCE 1. Insert USB HDD (do not mount) 2. Open KDE Partition Manager 3. Identify HDD, delete existing partitions (and if desired, partition table). 4. Create new partition (and table if removed), select EXT4 w/LUKS encryption. 6. Provide password. 7. Selecting either "everybody" or "root" doesn't make a difference for this issue (i tried both). 8. Finalise partition creation. 9. Mount HDD, input password. 10. HDD mounts in /run/media/[user]/[label] 11. Try to create/copy a file using Dolphin or Terminal as user. OBSERVED RESULT - As the user - read access works, write access = permission denied in terminal. In Dolphin, the 'new' or 'paste' option is greyed out or not present. - Using sudo, i could write files via the terminal. EXPECTED RESULT Should be able to copy files or create files as user. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Nobara 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I performed the relevant procedure in gnome-disk-utility with the same hardware, and it worked as expected. I could write files to the HDD after i mount and input the password. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 --- Comment #10 from Derek --- (In reply to Nate Graham from comment #9) > Thanks, then this is Bug 469016. > > *** This bug has been marked as a duplicate of bug 469016 *** I had small window previews disabled when I filed the bug but I have switched back to Wayland since seeing your comment and so far so good. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472008] New: Controlling monitor brightness over ddcutil sometimes unreliable
https://bugs.kde.org/show_bug.cgi?id=472008 Bug ID: 472008 Summary: Controlling monitor brightness over ddcutil sometimes unreliable Classification: Plasma Product: Powerdevil Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Controlling the brightness of the monitor using ddcutil generally works but is wonky sometimes. (Due to the nature of ddcutil) it takes a short time until the monitor has adjusted the brightness (like half a second). Therefore, for example changing the brightness by scrolling on the brightness applet feels choppy as it seems it does a blocking wait until the monitor reported the changed brightness value. Also, when the monitor is dimmed to a lower brightness value and is powered off by Plasma because of no user input , it sometimes fails to reset to the previous brightness setting when waking up the monitor again. It just stays at the lowest brightness setting. STEPS TO REPRODUCE 1. Change brightness by scrolling on the brightness control bar icon/applet 2. It feels very choppy OBSERVED RESULT It feels very choppy EXPECTED RESULT The brightness target value should be overwritten immediately, with the actual monitor brightness following at a later point in time (when the ddcutil communication succeeded) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.4.1-arch2-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Derek changed: What|Removed |Added CC||dcostr...@gmail.com --- Comment #19 from Derek --- This would be extremely helpful, would like to see this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 --- Comment #4 from Derek --- (In reply to Marcelo Bossoni from comment #3) > For me just hovering the mouse back and forth through items cause it to stop > updating. Yes I started getting random screen freezes, which logging out and back in solves and still odd freezing or extreme lag caused by some kind of task manager event like right clicking icon, moving icon, hovering. It seems to be random because I went almost a day and a half without any noticeable problems and then it just seems to happen at random. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 --- Comment #2 from Derek --- Recent updates over last 2 days may have resolved the problem. I haven't noticed any freezing when rearranging or unpinning yet. Will keep using and seeing if any particular scenario triggers it. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Derek Otto changed: What|Removed |Added CC||dereko...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] New: Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 Bug ID: 466580 Summary: Panel freezes when rearranging or unpinning on icons only task manager widget Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcostr...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY I have Nvidia GPU + Wayland and the panel will freeze anytime I unpin or rearrange the icons in the task manager. I can still right click on the panel and enter edit mode which adjusting the height by 1 pixel resolves whatever makes it freeze. So my workaround is just 1px up 1 px down real quick. Sometimes if I drag the icon to the exact location it will be when placed it works fine. STEPS TO REPRODUCE 1. Rearrange or unpin icon on task manager 2. 3. OBSERVED RESULT Panel freezes EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #258 from Derek --- Same issue. Everything was working and somewhere I along the way I was trying to switch back to nouveau drivers it didnt boot because I didnt realize nvidia driver installed blacklisting. either way I reverted back to the nvidia and for somereason now had mirroring happening and took me a minute to realize the monitors where stacked on top of each other in the Settings -> Display and Monitor settings window and I dragged the monitor off the other one and made them side by side and when I did that's when the black monitor happened. If i orient the monitor to vertical or upside down it displays normally but when I switch back to normal orientation it turns black. very strange. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Derek changed: What|Removed |Added CC||dcostr...@gmail.com --- Comment #257 from Derek --- Same issue. Everything was working and somewhere I along the way I was trying to switch back to nouveau drivers it didnt boot because I didnt realize nvidia driver installed blacklisting. either way I reverted back to the nvidia and for somereason now had mirroring happening and took me a minute to realize the monitors where stacked on top of each other in the Settings -> Display and Monitor settings window and I dragged the monitor off the other one and made them side by side and when I did that's when the black monitor happened. If i orient the monitor to vertical or upside down it displays normally but when I switch back to normal orientation it turns black. very strange. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466001] New: Visual glitches at the border of the panel since 5.27
https://bugs.kde.org/show_bug.cgi?id=466001 Bug ID: 466001 Summary: Visual glitches at the border of the panel since 5.27 Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 156436 --> https://bugs.kde.org/attachment.cgi?id=156436=edit Visual glitch SUMMARY There are some visual glitches in the border of the panel. The glitch is more than 1px thick. Observed in Wayland with fractional scaling enabled to 175%. Introduced with 5.27 STEPS TO REPRODUCE 1. Use Wayland and fractional scaling 2. Observe visual glitches SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-zen1-1-zen (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464953] Cannot open places view by pressing return while places button is highlighted
https://bugs.kde.org/show_bug.cgi?id=464953 Derek Christ changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Derek Christ --- I'm sorry, one is supposed to hit space, not return... I was distracted by the warning in the console. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464953] New: Cannot open places view by pressing return while places button is highlighted
https://bugs.kde.org/show_bug.cgi?id=464953 Bug ID: 464953 Summary: Cannot open places view by pressing return while places button is highlighted Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 155739 --> https://bugs.kde.org/attachment.cgi?id=155739=edit Places highlighted SUMMARY When hitting tab until the "places" button is highlighted, you cannot open the places view by pressing return. STEPS TO REPRODUCE 1. Tab until "places" is highlighted 2. Hit return 3. Nothing happens OBSERVED RESULT Nothing EXPECTED RESULT Places view should be opened SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-MANJARO (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION When hitting return, this is printed in the console: file:///home/derek/KDE/usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Header.qml:192: TypeError: Cannot read property 'action' of null -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 443406] ScrollView is draggable with a mouse
https://bugs.kde.org/show_bug.cgi?id=443406 Derek Christ changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from Derek Christ --- Can reproduce, lets reopen. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451965] Submenu misplacement since new outer margins of hightlight in menus
https://bugs.kde.org/show_bug.cgi?id=451965 --- Comment #3 from Derek Christ --- Other GUI interfaces do not seem to have a clear answer to this question either (Firefox, Windows, MacOS, ...) and most tend to place the submenu directly at the end of the highlight. So both possibilities may be valid. Perhaps the goal of the bug report should be to make it consistent in Plasma, based on the style that is more accepted among the community. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #18 from Derek Christ --- Created attachment 155000 --> https://bugs.kde.org/attachment.cgi?id=155000=edit Different scalings I tested with a fresh master build and then with the patch applied. Unfortunately it looks like problem persists in all cases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Mouse hover selection in search result persists across kickoff openings
https://bugs.kde.org/show_bug.cgi?id=454349 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com --- Comment #36 from Derek Christ --- Weird, can only reproduce on Wayland. On X this does not happen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462753] New: BTRFS deduplication is not considered in size calculation when duplicating files/directories
https://bugs.kde.org/show_bug.cgi?id=462753 Bug ID: 462753 Summary: BTRFS deduplication is not considered in size calculation when duplicating files/directories Classification: Frameworks and Libraries Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: christ.de...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When there is not much space left on the disk, KIO will not try to duplicate (Ctrl+D) files or directories that would take up more space than is left. On BTRFS, however, due to the deduplication, this operation will not take up any space at all. Therefore KIO falsely aborts a duplicate operation that should be possible. STEPS TO REPRODUCE 1. Fill up disk 2. Find a file that is bigger than the space left on disk 3. Try to duplicate it (Ctrl+D) OBSERVED RESULT Is not duplicated EXPECTED RESULT Should be duplicated SOFTWARE/OS VERSIONS Is not duplicated ADDITIONAL INFORMATION Operating System: openSUSE Tumbleweed 20221206 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438950] Triangle menu idle-hover reset doesn't work in kickoff
https://bugs.kde.org/show_bug.cgi?id=438950 --- Comment #25 from Derek Christ --- (In reply to Nate Graham from comment #24) > Sounds good, let's do that. Done with 462271 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462271] New: Sometimes the category the mouse is hovering over is not selected
https://bugs.kde.org/show_bug.cgi?id=462271 Bug ID: 462271 Summary: Sometimes the category the mouse is hovering over is not selected Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 154047 --> https://bugs.kde.org/attachment.cgi?id=154047=edit Category not selected SUMMARY Sometimes, the category the mouse is currently hovering over is not selected, even after the short timeout period of the triangular mouse filter. This mostly happens when moving the mouse diagonally to the upper left direction. This bug is caused by the triangular mouse filter that wrongfully filters a hover event and consequently does not re-select the category after the timeout period as the conditions for the filtering were actually not given. STEPS TO REPRODUCE 1. Open kickoff 2. Move mouse diagonally to the upper left over a category OBSERVED RESULT Category is not selected, even after the timeout EXPECTED RESULT Category should be selected. Also, there should not be a timeout, as the conditions for the triangular filtering are not matched. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.8-1-MANJARO (64-bit) ADDITIONAL INFORMATION This is the continuation of a very similar but slightly different bug 438950. More information of why this bug happens can be found in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2100 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438950] Triangle menu idle-hover reset doesn't work in kickoff
https://bugs.kde.org/show_bug.cgi?id=438950 --- Comment #23 from Derek Christ --- (In reply to Nate Graham from comment #22) > > This happens mostly when you make a fast jerky movement diagonally to the > > upper left. > > That seems like a different issue; moving to top left should not trigger the > triangle menu logic in the first place, and categories should be highlighted > on hover. This works for me FWIW. You're technically correct. We would then need to create a new bug report for this other issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadows have artifacts on HiDPI
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #9 from Derek Christ --- Created attachment 153950 --> https://bugs.kde.org/attachment.cgi?id=153950=edit HiDPI 200% scaling Wayland -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadows have artifacts on HiDPI
https://bugs.kde.org/show_bug.cgi?id=462005 Derek Christ changed: What|Removed |Added Attachment #153948|0 |1 is obsolete|| --- Comment #8 from Derek Christ --- Created attachment 153949 --> https://bugs.kde.org/attachment.cgi?id=153949=edit HiDPI 175% scaling Wayland -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadows have artifacts on HiDPI
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #7 from Derek Christ --- Created attachment 153948 --> https://bugs.kde.org/attachment.cgi?id=153948=edit HiDPI 175% scaling Wayland >From what I can tell, with 200% scaling, the artifact is less significant but can still be observed. Looking at the border of a window from the inside to the outside, it first gets brighter, then darker and finally brighter again. Added some screenshots. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadows have artifacts on HiDPI
https://bugs.kde.org/show_bug.cgi?id=462005 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #5 from Derek Christ --- Can confirm, I have a HiDPI monitor with 175% scaling on Wayland and the outline doesn't look right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438950] Triangle menu idle-hover reset doesn't work in kickoff
https://bugs.kde.org/show_bug.cgi?id=438950 --- Comment #21 from Derek Christ --- (In reply to Nate Graham from comment #20) > Weird, I can't. When I move my cursor diagonally to trigger the triangle > filter to not switch categories, it indeed does not switch categories. But > then when the cursor steps for a moment, it switches to whatever category > the cursor is over. > > Are you not seeing that? Yes, in general the timeout of the mouse filter works. But sometimes it happens that a selection is not made, although the timer should have expired. This happens mostly when you make a fast jerky movement diagonally to the upper left. I have described why this happens in more detail in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2100. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438950] Triangle menu idle-hover reset doesn't work in kickoff
https://bugs.kde.org/show_bug.cgi?id=438950 --- Comment #19 from Derek Christ --- (In reply to Nate Graham from comment #18) > That fix was reverted, but I can't reproduce the issue anymore in current > git master, so maybe something else fixed it. Can anyone else confirm? I can still reproduce the bug on latest master. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445403] [feature] Clone navigation history when creating new tab
https://bugs.kde.org/show_bug.cgi?id=445403 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com --- Comment #2 from Derek Christ --- This would also make much sense when middle clicking the forward/backward button (or refresh button, see 458954) in the toolbar. Most web browsers implement it that way, that the navigation history is cloned. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458954] New: Duplicate same tab by middle clicking on refresh button
https://bugs.kde.org/show_bug.cgi?id=458954 Bug ID: 458954 Summary: Duplicate same tab by middle clicking on refresh button Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: christ.de...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY It would be a nice addition to be able to duplicate the current Dolphin tab by middle clicking the refresh button. This already works on many browsers (Firefox, ...) and is a useful feature. STEPS TO REPRODUCE 1. Add refresh button to toolbar if not present 2. Middle click it OBSERVED RESULT Nothing happens EXPECTED RESULT Open the same tab in a new tab. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 Kernel Version: 5.15.60-1-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 452074] Deleting files to trash with kio very slow | trash-cli and rm work correctly
https://bugs.kde.org/show_bug.cgi?id=452074 Derek Christ changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||christ.de...@gmail.com --- Comment #8 from Derek Christ --- I experience the same issue with BTRFS. I want to add, that I'm also using LUKS disk encryption, but I'm not sure if this is related at all. Moving files to trash take several seconds for me, sometimes even longer. When using XFCE's file manager Thunar test wise, the deletion process finishes almost immediately. The trash folder is in the same BTRFS subvolume as the deleted files. Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.59-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453090] Can't connect to a Windows samba share with samba-libs 4.16
https://bugs.kde.org/show_bug.cgi?id=453090 derek-shnosh changed: What|Removed |Added CC||derek.d.smi...@gmail.com --- Comment #10 from derek-shnosh --- Commenting to advise this bit me with samba-libs 4.15.9. ``` Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-43-generic (64-bit) Samba version: 4.15.9 ``` -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 457120] New: Reminder Daemon crashing when Dismissing after startup
https://bugs.kde.org/show_bug.cgi?id=457120 Bug ID: 457120 Summary: Reminder Daemon crashing when Dismissing after startup Product: kalendar Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: dereko...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.3) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.96.0 Operating System: Linux 5.18.14_custom x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: This has been a consistent issue when first loggin into my desktop session. Reminders for previous events pop-up and when I Dismiss the first one, the KDE Reminder daemon crashes. Reminders still seem to work afterwards, but the first Dismiss seems to cause a crash. The crash can be reproduced every time. -- Backtrace: Application: Reminders (kalendarac), signal: Segmentation fault [KCrash Handler] #4 0x7b3b28f943b3 in _dbus_header_get_byte_order () at /usr/lib64/libdbus-1.so.3 #5 0x7b3b28f945b9 in () at /usr/lib64/libdbus-1.so.3 #6 0x7b3b28f8f135 in dbus_connection_send_with_reply () at /usr/lib64/libdbus-1.so.3 #7 0x7b3b2ab54fcd in () at /usr/lib64/libQt5DBus.so.5 #8 0x7b3b2a8b9bae in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #9 0x7b3b2a88f157 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7b3b2a891f17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #11 0x7b3b2a8e3603 in () at /usr/lib64/libQt5Core.so.5 #12 0x7b3b26cc55fb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #13 0x7b3b26cc5868 in () at /usr/lib64/libglib-2.0.so.0 #14 0x7b3b26cc590f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #15 0x7b3b2a8e2cd4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #16 0x7b3b2a88dd0b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7b3b2a6ae39e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #18 0x7b3b2ab48447 in () at /usr/lib64/libQt5DBus.so.5 #19 0x7b3b2a6af3eb in () at /usr/lib64/libQt5Core.so.5 #20 0x7b3b295aae45 in start_thread () at /lib64/libpthread.so.0 #21 0x7b3b2a18f4af in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7b3b246ae640 (LWP 4612) "QXcbEventQueue"): #1 0x7b3b290adcc2 in () at /usr/lib64/libxcb.so.1 #2 0x7b3b290afd4a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7b3b247d34c0 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7b3b2a6af3eb in () at /usr/lib64/libQt5Core.so.5 #5 0x7b3b295aae45 in start_thread () at /lib64/libpthread.so.0 #6 0x7b3b2a18f4af in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7b3b249465c0 (LWP 4591) "kalendarac"): #1 0x7b3b2963b050 in () at /usr/lib64/libKF5Crash.so.5 #2 0x7b3b2963ba46 in KCrash::defaultCrashHandler(int) () at /usr/lib64/libKF5Crash.so.5 #3 0x7b3b2a0bf8d0 in () at /lib64/libc.so.6 #4 0x7b3b2a8e5b88 in () at /usr/lib64/libQt5Core.so.5 #5 0x7b3b2a73eb7d in QString::toUtf8_helper(QString const&) () at /usr/lib64/libQt5Core.so.5 #6 0x7b3b2bb2a39f in KConfigBase::isGroupImmutable(QString const&) const () at /usr/lib64/libKF5ConfigCore.so.5 #7 0x7b3b2bb312d8 in KConfigGroup::KConfigGroup(KConfigBase*, QString const&) () at /usr/lib64/libKF5ConfigCore.so.5 #8 0x0040a3e2 in () #9 0x0040a6da in () #10 0x7b3b2a8c344d in () at /usr/lib64/libQt5Core.so.5 #11 0x7b3b2c583437 in KNotification::close() () at /usr/lib64/libKF5Notifications.so.5 #12 0x7b3b2a8c344d in () at /usr/lib64/libQt5Core.so.5 #13 0x7b3b2c57e68f in KNotificationPlugin::finished(KNotification*) () at /usr/lib64/libKF5Notifications.so.5 #14 0x7b3b2c59bde4 in () at /usr/lib64/libKF5Notifications.so.5 #15 0x7b3b2a8c344d in () at /usr/lib64/libQt5Core.so.5 #16 0x7b3b2c5a90cf in () at /usr/lib64/libKF5Notifications.so.5 #17 0x7b3b2c5a977b in () at /usr/lib64/libKF5Notifications.so.5 #18 0x7b3b2ab53deb in () at /usr/lib64/libQt5DBus.so.5 #19 0x7b3b2a8b9bae in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7b3b2a88f18a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #21 0x7b3b2a891f17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #22 0x7b3b2a8e3603 in () at /usr/lib64/libQt5Core.so.5 #23 0x7b3b26cc55fb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #24 0x7b3b26cc5868 in () at /usr/lib64/libglib-2.0.so.0 #25
[marble] [Bug 457091] New: GPX thumbnails/previews do not work any more
https://bugs.kde.org/show_bug.cgi?id=457091 Bug ID: 457091 Summary: GPX thumbnails/previews do not work any more Product: marble Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: christ.de...@gmail.com Target Milestone: --- SUMMARY The thumbnail/preview function of GPX files in Dolphin does not work any more. The generic file icon will be displayed instead. There may be a bug in the thumbnailer of Marble. STEPS TO REPRODUCE 1. Make sure to have Marble installed. 2. Enable the preview of GPX files in Dolphin's settings. 3. Try to open a preview of a GPX file by pressing F11. OBSERVED RESULT Generic file icon. EXPECTED RESULT Preview of the GPX file. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION The GPX files I tested with can be opened by Marble itself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438950] Triangle menu idle-hover reset doesn't work in kicker
https://bugs.kde.org/show_bug.cgi?id=438950 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455227] New: Password field in lock screen is not cleared after failed login attempt
https://bugs.kde.org/show_bug.cgi?id=455227 Bug ID: 455227 Summary: Password field in lock screen is not cleared after failed login attempt Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com CC: visual-des...@kde.org Target Milestone: 1.0 SUMMARY Since https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1754/ the password field in the lock screen does not get cleared after a failed login attempt. STEPS TO REPRODUCE 1. Lock screen (Ctrl+L) 2. Enter false password OBSERVED RESULT False password not cleared EXPECTED RESULT Cleared text field -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453828] New: Undo operation possible in lock-screen password field (Ctrl-Z)
https://bugs.kde.org/show_bug.cgi?id=453828 Bug ID: 453828 Summary: Undo operation possible in lock-screen password field (Ctrl-Z) Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com CC: visual-des...@kde.org Target Milestone: 1.0 SUMMARY It's possible to do Ctrl-Z and restore the previous written text in the password entry field. Consider the scenario where a user partly enters the password but then decides to something else and not unlock the screen. The user then clears the password field thinking the password cannot be restored by some other person. Some other person can now hit Ctrl-Z and restore the password and make it visible by clicking on the eye symbol. STEPS TO REPRODUCE 1. Type something in the lock screen password field 2. Delete it 3. Hit Ctrl-Z OBSERVED RESULT Password restored EXPECTED RESULT Ctrl-Z should not be possible SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.6-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453107] New: Some applications open a separate window and then it switches back to the icon.
https://bugs.kde.org/show_bug.cgi?id=453107 Bug ID: 453107 Summary: Some applications open a separate window and then it switches back to the icon. Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dcostr...@gmail.com Target Milestone: --- Created attachment 148421 --> https://bugs.kde.org/attachment.cgi?id=148421=edit separate window opening when icon clicked instead of expanding SUMMARY Some applications open a separate window and then it switches back to the icon. There are times when the windows stays separated from the launcher even though open seperate is disabled. I have noticed this with chromium and chromium based browsers more notably Brave. Other apps periodically have this happen as well. In screenshot i took I just clicked on Brave icon to left but for a few seconds it will open a separate window all the way to the right instead of expanding the icon in place. Sometimes it doesn't go back to the Brave icon and then the Brave icon on the left always opens new windows instead of expanding icon. STEPS TO REPRODUCE 1. Open app 2. It opens separate launcher SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 452579] Printing on an ipp printer that requires authentication does not ask for a password and consequently does not print
https://bugs.kde.org/show_bug.cgi?id=452579 --- Comment #2 from Derek Christ --- (In reply to Harald Sitter from comment #1) > How to get an ipp printer that requires authentication? In my case it's my university that requires authentication for the public printers. I'm not an CUPS expert but maybe it's possible to set up a remote CUPS instance that requires authentication? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 452579] New: Printing on an ipp printer that requires authentication does not ask for a password and consequently does not print
https://bugs.kde.org/show_bug.cgi?id=452579 Bug ID: 452579 Summary: Printing on an ipp printer that requires authentication does not ask for a password and consequently does not print Product: print-manager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: christ.de...@gmail.com Target Milestone: --- SUMMARY Printing on an ipp printer that requires authentication does not ask for a password and consequently does not print. The only way I found it to work is to set it up using the full ipp:// url like so: ipp://user:p...@server.com. Note that this leaks on the password in clear text into the system log, as pointed out in bug 441948. When the printer is set up without providing the password in the url, printing does not work. STEPS TO REPRODUCE 1. Add an ipp printer that requires authentication 2. Print a document 3. You will not be asked for authentication OBSERVED RESULT The document will not be printed EXPECTED RESULT The user should get asked for the username and password. Also the system should ask if the password should be saved into KWallet. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.16.14-1-MANJARO (64-bit) ADDITIONAL INFORMATION I tested the same thing on Linux Mint (with Cinnamon) and over there I get asked for a password when printing. Also on Gnome it should work too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396397] Second drag-and-drop inside a Folder View Widget compresses each item during the drag
https://bugs.kde.org/show_bug.cgi?id=396397 Derek Christ changed: What|Removed |Added CC||i...@marguerite.su --- Comment #5 from Derek Christ --- *** Bug 451948 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451948] [foldermodel]selection changed from rectangle to square when dragging a file with multi-line filename for the second time
https://bugs.kde.org/show_bug.cgi?id=451948 Derek Christ changed: What|Removed |Added Status|REPORTED|RESOLVED CC||christ.de...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Derek Christ --- *** This bug has been marked as a duplicate of bug 396397 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451965] Submenu misplacement since new outer margins of hightlight in menus
https://bugs.kde.org/show_bug.cgi?id=451965 --- Comment #1 from Derek Christ --- Created attachment 147773 --> https://bugs.kde.org/attachment.cgi?id=147773=edit Context menu in system-monitor -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451965] New: Submenu misplacement since new outer margins of hightlight in menus
https://bugs.kde.org/show_bug.cgi?id=451965 Bug ID: 451965 Summary: Submenu misplacement since new outer margins of hightlight in menus Product: Breeze Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com Target Milestone: --- Created attachment 147772 --> https://bugs.kde.org/attachment.cgi?id=147772=edit Context menu on desktop SUMMARY Submenus in menus get horizontally misplaced since the addition of the new outer margins of hightlight in menus. The submenu is placed at the edge of the highlight instead of the menu itself which looks weird. I attached a screenshot that shows the misplacement of the submenu. The Breeze Style for QQC2 is not affected by this bug as far as I can tell. I also attached a screenshot from the system-monitor where the submenu gets correctly aligned to the main menu and not the highlight. STEPS TO REPRODUCE 1. Run the git master version of Plasma 2. Right click on the desktop and hover over an item that opens a submenu OBSERVED RESULT Submenu is aligned to the highlight EXPECTED RESULT Submenu is aligned to the main menu SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.16.14-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450076] Right click in the left column of kickoff, the hovering highlight in the right column disappears.
https://bugs.kde.org/show_bug.cgi?id=450076 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com --- Comment #7 from Derek Christ --- I noticed a likely related issue: When searching for a keyword in kickoff and right-clicking into the list while the cursor is fastly moving, the hightlight disappears and no context menu appears, leaving the kickoff launcher in a seemingly freezed state. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 425257] Changing the color scheme while ksysguard is open messes with the displayed graphs
https://bugs.kde.org/show_bug.cgi?id=425257 Derek Christ changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Derek Christ --- Closing this, as since the launch of the new system monitor this is irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428109] Fitts' Law broken for non-taskmanager panel applets
https://bugs.kde.org/show_bug.cgi?id=428109 --- Comment #33 from Derek Christ --- (In reply to Nate Graham from comment #32) > For anyone who can reproduce this, can you answer the following questions: > 1. What side of the screen is your panel located on? > 2. On which screen edge is Fitts' Law broken for? > 2. What is your screen resolution? > 3. What is your scaling factor? > 4. Are you running Plasma on X11 with PLASMA_USE_QT_SCALING=1? > 4a. If so, does the problem go away if you unset that and restart > plasmashell? > 5. Does it reproduce on Wayland too, or just X11? > > Thanks in advance. :) 1. Bottom 2. Bottom is broken, the left side works 2. 3840x2160 3. 2x 4. Yes 4a. At first yes, but the panel is smaller when the variable is not set. After resizing to the previous visual size the problem persists but this time also for the left screen edge. 5. In Wayland everything works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449543] New: Dragging multiple items onto the desktop in the bottom right corner makes the view scrollable
https://bugs.kde.org/show_bug.cgi?id=449543 Bug ID: 449543 Summary: Dragging multiple items onto the desktop in the bottom right corner makes the view scrollable Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Since https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/836 it's multiple items that get dragged onto the desktop will get properly placed at the cursor position. A result of this, however, is that dragging multiple items onto the desktop in the bottom right corner makes the view scrollable because some items get placed outside of the visible space. This might almost never be the intend of the user. STEPS TO REPRODUCE 1. Drop at least two files from Dolphin over to the desktop 2. Drop it in the bottom right corner 3. Scrollbar appears OBSERVED RESULT Scrollbar appears, item gets placed outside of the view EXPECTED RESULT Maybe the dropped items should shift backwards so that none gets dropped outside of the view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407888] Items remain with a different "strong" highlight color after drag-and-dropping them
https://bugs.kde.org/show_bug.cgi?id=407888 Derek Christ changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||christ.de...@gmail.com --- Comment #1 from Derek Christ --- This bug should be resolved with my merge request https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/708 in 5.24. In 5.23 I still could reproduce the bug, in 5.24 not anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428109] Fitts' Law broken for non-taskmanager panel applets
https://bugs.kde.org/show_bug.cgi?id=428109 --- Comment #31 from Derek Christ --- I'll add my infos from Bug 446880 too: Can reproduce the bug with scaling set to 2x (4k resolution) on X11. The bug does not occur with 1x scaling. Also, the Wayland session is not affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447509] New: Rubber band selection sometimes does not clear up when selected file is deleted.
https://bugs.kde.org/show_bug.cgi?id=447509 Bug ID: 447509 Summary: Rubber band selection sometimes does not clear up when selected file is deleted. Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 144858 --> https://bugs.kde.org/attachment.cgi?id=144858=edit Rubber band bug SUMMARY Sometimes, when a rubber band selection is made over an item, it will not clear up when the item was deleted. The selection just stays even when the left mouse button is no longer being held down. This happens somewhat irregularly and I wasn't able to figure out under which circumstances this bug appears and when not. STEPS TO REPRODUCE 1. Make a rubber band selection containing one item 2. Delete the item with the delete key 3. The selection is still there when releasing the left mouse button OBSERVED RESULT Selection stays EXPECTED RESULT Selection should vanish SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211223 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-1-default (64-bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 447066] New: Ark doesn't compress dir to 7z, and sometimes crashes Dolphin.
https://bugs.kde.org/show_bug.cgi?id=447066 Bug ID: 447066 Summary: Ark doesn't compress dir to 7z, and sometimes crashes Dolphin. Product: ark Version: 21.12.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: derek@eide.cloud CC: aa...@kde.org, rthoms...@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. Within Dolphin, elect to compress with 7zip via right-click. 2. Accept defaults (no changes to compression or name or anything). 3. Compression begins, but doesn't finish. Progress keeps going... Using ZIP works fine. OBSERVED RESULT - Ark seems to run forever - progress indicator doesn't finish. - Resultant 7zip file SEEMS ok, but i don't trust it. - Ark didn't crash, but Dolphin did when i clicked 'stop' in the notification area. I don't think this was every time, but it happened several times. I submitted a bug and saved the file (below). - When i had two instances of Dolphin open, the 2nd instance would open a tab in the directory i'm working in (odd!) - Notification area error box showed: Dolphin Compressing 26 files (Failed) Application closed unexpectedly. EXPECTED RESULT Compression to show as finished. SOFTWARE/OS VERSIONS Application: dolphin (21.12.0) Qt Version: 5.15.2 Frameworks Version: 5.89.0 Operating System: Linux 5.15.7-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: See above. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7ff6f028e5c1 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7ff6f14aa38d in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/libKF5CoreAddons.so.5 #6 0x7ff6f14ab87c in KJob::finishJob(bool) () from /usr/lib/libKF5CoreAddons.so.5 #7 0x7ff6f028e7cb in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7ff6d027f9e3 in Kerfuffle::ReadOnlyArchiveInterface::finished(bool) () from /usr/lib/libkerfuffle.so.21 #9 0x7ff6f028e7cb in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7ff6f01c0719 in QProcess::finished(int, QProcess::ExitStatus) () from /usr/lib/libQt5Core.so.5 #11 0x7ff6f01c6226 in ?? () from /usr/lib/libQt5Core.so.5 #12 0x7ff6f01c635e in ?? () from /usr/lib/libQt5Core.so.5 #13 0x7ff6f028e800 in ?? () from /usr/lib/libQt5Core.so.5 #14 0x7ff6f0291c90 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #15 0x7ff6f029249d in QSocketNotifier::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7ff6f0d2ed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7ff6f025741a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x7ff6f02b0c5e in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7ff6edd8952c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x7ff6e7b9 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x7ff6edd86c11 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0x7ff6f02b0046 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7ff6f0255d8c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #24 0x7ff6f025e2f4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #25 0x558a9041d54e in ?? () #26 0x7ff6efbe3b25 in __libc_start_main () from /usr/lib/libc.so.6 #27 0x558a9041d93e in ?? () [Inferior 1 (process 20252) detached] Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446880] [X11] Clickable area of applets do not expand to the screen edges when 2x global scaling is activated
https://bugs.kde.org/show_bug.cgi?id=446880 --- Comment #2 from Derek Christ --- (In reply to Nate Graham from comment #1) > Is it broken for the Task Manager too, or only for all other applets? Or > does it affect every panel applet? > > See Bug 428109. The task manager is the only applet that is not affected, as far as I can tell. I also noticed that this bug only appears when the height of the applet is bigger than a certain amount. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446880] New: [X11] Clickable area of applets do not expand to the screen edges when 2x global scaling is activated
https://bugs.kde.org/show_bug.cgi?id=446880 Bug ID: 446880 Summary: [X11] Clickable area of applets do not expand to the screen edges when 2x global scaling is activated Product: plasmashell Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: christ.de...@gmail.com Target Milestone: 1.0 SUMMARY In X11, when using global scaling (I tested with 2x), it is no longer possible to click applets in the panel that are right on the edge of the screen by moving the cursor in the edge of the screen. For example the kickoff menu cannot be opened by moving the cursor to the bottom left of the screen and the "Show desktop" / "Minimize all windows" applet cannot be triggered by moving the cursor in the bottom right corner. You have to exactly click the button. This issue does not occur when the global scaling is disabled, and I also cannot confirm this bug on Wayland. STEPS TO REPRODUCE 1. Set global scaling to 2x on X11 2. Log out, back in 3. Move cursor to the bottom left corner or bottom right corner and try to trigger an applet OBSERVED RESULT Nothing happens EXPECTED RESULT Menus should open / applets should trigger SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211208 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405377] Handle new Linux kernel feature: Restartable Sequences ("rseq")
https://bugs.kde.org/show_bug.cgi?id=405377 --- Comment #4 from Derek Bruening --- Updated link for the stale wiki page from the first comment above detailing the run-twice solution DynamoRIO has been using successfully for years now: https://dynamorio.org/page_rseq.html -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445442] New: Holding F2 while creating a selection freezes the rubber band
https://bugs.kde.org/show_bug.cgi?id=445442 Bug ID: 445442 Summary: Holding F2 while creating a selection freezes the rubber band Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: christ.de...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143519 --> https://bugs.kde.org/attachment.cgi?id=143519=edit Video of the issue SUMMARY Holding F2 while creating a selection freezes the rubber band. Please see my attached video. STEPS TO REPRODUCE 1. Hold F2 2. Make a selection with the mouse 3. The rubber band will freeze in place Operating System: openSUSE Tumbleweed 2020 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445441] New: Dropping multiple files on the desktop only positions one file at the mouse position
https://bugs.kde.org/show_bug.cgi?id=445441 Bug ID: 445441 Summary: Dropping multiple files on the desktop only positions one file at the mouse position Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When dropping multiple files onto the desktop, only one will be actually dropped at the mouse position. The other items will just fill up at the top left corner. STEPS TO REPRODUCE 1. Drag multiple files from Dolphin onto the desktop 2. See that only one item will be at the mouse position EXPECTED RESULT All files dropped at mouse position. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 2020 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443512] Unable to create a folder on desktop via F10 keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=443512 --- Comment #7 from Derek Christ --- (In reply to David Edmundson from comment #6) > Please try to get rid of > `QApplication::instance()->installEventFilter(this);` > > It will be causing a sizable amount of overhead for every interaction. Sadly this is needed to fix bug 425997. What do you think about removing the filter as soon as the context menu closes? So that it is only installed on QAppliaction when the menu is actually open. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443512] Unable to create a folder on desktop via F10 keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=443512 --- Comment #5 from Derek Christ --- > Derek, would you be able to take a look? Thanks! Sorry, I must have missed this. Will have a look -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443406] New: Left settings bar flickable in config dialogs
https://bugs.kde.org/show_bug.cgi?id=443406 Bug ID: 443406 Summary: Left settings bar flickable in config dialogs Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: christ.de...@gmail.com Target Milestone: Not decided Created attachment 142213 --> https://bugs.kde.org/attachment.cgi?id=142213=edit Example SUMMARY It's possible to drag the items that are displayed in the left bar in every config dialog (Kirigami only) when dragging on text. STEPS TO REPRODUCE 1. Open a Kirigami config dialog (for example the settings of the kickoff menu) 2. Click and drag exactly on text in the left settings bar OBSERVED RESULT Is flickable EXPECTED RESULT Should not be flickable SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211001 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm sorry if this isn't the correct place to put this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442765] Can't delete file on desktop from contestual menu (right mouse button + click "Elimina")
https://bugs.kde.org/show_bug.cgi?id=442765 --- Comment #4 from Derek Christ --- I cannot really reproduce (at least on latest Git master and Neon Testing Live image) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442765] Can't delete file on desktop from contestual menu (right mouse button + click "Elimina")
https://bugs.kde.org/show_bug.cgi?id=442765 --- Comment #2 from Derek Christ --- This sounds very like BUG 442485 (the removeaction wasn't properly initialized unless the user presses shift at least once). Any chance the fix didn't made it into the beta? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442587] New: [Wayland] Launch feedback does not work when staring an app using the kickoff launcher
https://bugs.kde.org/show_bug.cgi?id=442587 Bug ID: 442587 Summary: [Wayland] Launch feedback does not work when staring an app using the kickoff launcher Product: plasmashell Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Since Bug 402903 is now resolved, we finally have launch feedback when opening an application on Wayland. However, the launch feedback does not work when an app is launched using the kickoff launcher. Launching from the desktop or from any other application (KRunner) works fine. STEPS TO REPRODUCE 1. Open Kickoff launcher 2. Launch an application 3. No launch feedback OBSERVED RESULT No launch feedback EXPECTED RESULT Launch feedback SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210914 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This does not only affect Kickoff launcher, but also every other menu I tested. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442485] Delete key to move desktop file to trash does not work after restarting plasmashell, showing the desktop, and selecting a file
https://bugs.kde.org/show_bug.cgi?id=442485 Derek Christ changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/64 ||14da73867a39f4ce5cfade20d01 ||d918496f2d9 --- Comment #3 from Derek Christ --- Git commit 6414da73867a39f4ce5cfade20d01d918496f2d9 by Derek Christ. Committed on 15/09/2021 at 17:55. Pushed by ngraham into branch 'master'. Fix a bug regarding the remove action in the folder plugin Fix a bug that caused not being able to remove files from the desktop using the delete key when no context menu was opened since the start of the plasmashell. M +3-0containments/desktop/plugins/folder/foldermodel.cpp M +0-2containments/desktop/plugins/folder/removeaction.cpp https://invent.kde.org/plasma/plasma-desktop/commit/6414da73867a39f4ce5cfade20d01d918496f2d9 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442469] New: Running a external tool on saving.
https://bugs.kde.org/show_bug.cgi?id=442469 Bug ID: 442469 Summary: Running a external tool on saving. Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: christ.de...@gmail.com Target Milestone: --- SUMMARY It would be a nice convenience to be able to run a external tool every time the user saves the current file. For example by saving the file a code formatter tool could run and format all changes. STEPS TO REPRODUCE 1. Setup a external tool to run on save 2. Every time the user saves, the tool runs OBSERVED RESULT Not yet possible, to my understanding. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210913 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It's possible to do something similar with hacks. Just assign Ctrl+S on the external tool and config the tool that it will save the current file before running. But this is not a very nice solution to the problem. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442468] New: Running a formatter as external tool prevents usage of Ctrl+Z
https://bugs.kde.org/show_bug.cgi?id=442468 Bug ID: 442468 Summary: Running a formatter as external tool prevents usage of Ctrl+Z Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: christ.de...@gmail.com Target Milestone: --- SUMMARY Running a formatter as an external tool has the ability to save the current file, apply the tool, and reloading it afterwards. For formatting this works great but the reloading of the file wipes the Ctrl+Z buffer and its no longer possible to revert stuff that happened before the formatting. STEPS TO REPRODUCE 1. Make some changes to a file 2. Run the clang-format formatter tool on the whole file 3. Reverting changes before the formatting with Ctrl+Z is no longer possible. OBSERVED RESULT Ctrl+Z does nothing, because the file was reloaded. EXPECTED RESULT It should still be possible to revert old changes. Other code editors I know of just revert the whole formatting when the user presses Ctrl+Z right after formatting. All other changes before that are also revertable. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210913 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438930] Visual glitch in context menu when the shift modifier key is pressed
https://bugs.kde.org/show_bug.cgi?id=438930 Derek Christ changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/f8 ||30ceeaf012a9f87b7c0b2b2bb9b ||095de107da4 Status|ASSIGNED|RESOLVED Version Fixed In||5.22 Resolution|--- |FIXED --- Comment #3 from Derek Christ --- Git commit f830ceeaf012a9f87b7c0b2b2bb9b095de107da4 by Derek Christ. Committed on 09/09/2021 at 19:01. Pushed by davidedmundson into branch 'master'. Introduce RemoveAction for context menu The RemoveAction can either represent the delete action or the move to trash action, depending on the shift modifier state. This inplace swapping instead of adding and removing both actions fixes a visual glitch that could be noticed by pressing and releasing the shift key multiple times. FIXED-IN: 5.22 M +1-0containments/desktop/plugins/folder/CMakeLists.txt M +28 -46 containments/desktop/plugins/folder/foldermodel.cpp M +0-2containments/desktop/plugins/folder/foldermodel.h A +99 -0containments/desktop/plugins/folder/removeaction.cpp [License: GPL(v2.0+)] A +49 -0containments/desktop/plugins/folder/removeaction.h [License: GPL(v2.0+)] https://invent.kde.org/plasma/plasma-desktop/commit/f830ceeaf012a9f87b7c0b2b2bb9b095de107da4 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 440466] New: Dark Mode for Kid3 on MacOS
https://bugs.kde.org/show_bug.cgi?id=440466 Bug ID: 440466 Summary: Dark Mode for Kid3 on MacOS Product: kid3 Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: johndoeiscom...@yahoo.com Target Milestone: --- SUMMARY Kid3 is needing a dark mode for MacOS. When I'm editing songs at night, my eyes hurts from the light mode when all of my other applications are in dark mode, I think this would be a nice addition. SOFTWARE/OS VERSIONS macOS: 10.15.7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 417894] Blurry Plasma Components Buttons when position is fractional
https://bugs.kde.org/show_bug.cgi?id=417894 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 432130] high-res/non-integer scrolling clashes BAD with font hinting/icons
https://bugs.kde.org/show_bug.cgi?id=432130 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com --- Comment #2 from Derek Christ --- Created attachment 140191 --> https://bugs.kde.org/attachment.cgi?id=140191=edit The outline and icon of an element look weird. This may also be the cause why the applet for the hidden systray elements is so blurry even without any scrolling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432270] Transition of focus from search box to search results list eats a down arrow keystroke unintuitively
https://bugs.kde.org/show_bug.cgi?id=432270 Derek Christ changed: What|Removed |Added CC||christ.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439395] New: Conflicting shortcuts on fresh install
https://bugs.kde.org/show_bug.cgi?id=439395 Bug ID: 439395 Summary: Conflicting shortcuts on fresh install Product: digikam Version: 7.2.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: christ.de...@gmail.com Target Milestone: --- Created attachment 139797 --> https://bugs.kde.org/attachment.cgi?id=139797=edit Conflicting shortcuts SUMMARY There are conflicting shortcuts for "Open Command Bar" and "Add Images" on a fresh install of digiKam (on openSUSE Tumbleweed). Please see my screenshot. STEPS TO REPRODUCE 1. Install digiKam (on openSUSE Tumbleweed) 2. Open digiKam OBSERVED RESULT Conflict EXPECTED RESULT No conflict SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210629 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I could reproduce this on two separate fresh installations of Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439066] New: Add ability to scroll through PDF-preview
https://bugs.kde.org/show_bug.cgi?id=439066 Bug ID: 439066 Summary: Add ability to scroll through PDF-preview Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: christ.de...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY It would be nice if the PDF preview that is already displayed by Dolphin in the information panel would be scrollable. Either by providing a scrollbar or by two buttons that add the ability to browse though the pages of the document. STEPS TO REPRODUCE 1. Select a PDF document 2. See that the first page of the document is shown in the preview OBSERVED RESULT Only the first page is show. EXPECTED RESULT Scrollbar / or buttons that add the ability to browse the preview ADDITIONAL INFORMATION (I have to say this) Windows has such a feature. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438930] New: Visual glitch in context menu when the shift modifier key is pressed
https://bugs.kde.org/show_bug.cgi?id=438930 Bug ID: 438930 Summary: Visual glitch in context menu when the shift modifier key is pressed Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139527 --> https://bugs.kde.org/attachment.cgi?id=139527=edit Glitch SUMMARY When the shift modifier key is pressed while a context menu of a file or folder is open, a visual glitch appears at the bottom of the context menu. Please see my picture. STEPS TO REPRODUCE 1. Go to desktop 2. Right click on a file 3. Press and release shift OBSERVED RESULT Visual glitch EXPECTED RESULT No glitch SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210616 KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have found this bug while working on Bug 425997. I will probably fix this bug myself soon. I think the glitch appears because the eventfilter of the context menu swaps the "move to trash" action with the delete action instead of changing it in place. I think doing it like Dolphin and switching the action in place will resolve this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 437007] New: Compositions will not work on Video2 or above at the end of a clip
https://bugs.kde.org/show_bug.cgi?id=437007 Bug ID: 437007 Summary: Compositions will not work on Video2 or above at the end of a clip Product: kdenlive Version: 21.04.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: dereknea...@protonmail.com Target Milestone: --- Created attachment 138377 --> https://bugs.kde.org/attachment.cgi?id=138377=edit Screenshot of the way to create the clip that doesn't work SUMMARY Compositions will not work on Video2 or above when added to the end of a clip. STEPS TO REPRODUCE 1. Make a title clip in Video2 or higher 2. Add a composition (i.e. wipe, dissolve) to the end of the title clip OBSERVED RESULT Playback or render the video and the composition will not work EXPECTED RESULT Composition will work properly as it does in Video1. SOFTWARE/OS VERSIONS Linux Mint 19.3 ADDITIONAL INFORMATION This feature used to work properly in all video tracks and now it only works in Video1. This started halfway through working on a project and is not resolved if I start a new project from scratch. If I load an old project prior to this issue, it will work fine. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 434927] When audio plays, the volume slider button goes under the volume bar
https://bugs.kde.org/show_bug.cgi?id=434927 --- Comment #5 from Derek Christ --- Please see this short clip. It illustrates the connection to the mic mute button: https://imgur.com/zRktZPd -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 434927] When audio plays, the volume slider button goes under the volume bar
https://bugs.kde.org/show_bug.cgi?id=434927 --- Comment #3 from Derek Christ --- I noticed, that this is more likely to happen when the Mic is muted as in my pictures. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 434927] New: When audio plays, the volume slider button goes under the volume bar
https://bugs.kde.org/show_bug.cgi?id=434927 Bug ID: 434927 Summary: When audio plays, the volume slider button goes under the volume bar Product: plasma-pa Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: christ.de...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 137052 --> https://bugs.kde.org/attachment.cgi?id=137052=edit Plasmoid SUMMARY When audio plays, the volume plasmoid shows a small visualizer showing the current volume level. However, when this is the case, the button of the slider goes under the volume bar. (Please see my pictures) STEPS TO REPRODUCE 1. Play audio 2. Open audio plasmoid 3. See that the slider button is below the slider. OBSERVED RESULT The button should be all the way on the top. EXPECTED RESULT The button is under the slider. Operating System: openSUSE Tumbleweed 20210321 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-default -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 423333] Wishlist: any-event mouse tracking support (1003 mode)
https://bugs.kde.org/show_bug.cgi?id=42 Derek Christ changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||christ.de...@gmail.com --- Comment #2 from Derek Christ --- *** This bug has been marked as a duplicate of bug 391967 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391967] Konsole doesn't report mouse moves in ESC[?1003h mode
https://bugs.kde.org/show_bug.cgi?id=391967 Derek Christ changed: What|Removed |Added CC||kevin.lamo...@gmail.com --- Comment #1 from Derek Christ --- *** Bug 42 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
