[systemsettings] [Bug 478936] Unable to bind / use the calculator key in plasma 6 on Wayland
https://bugs.kde.org/show_bug.cgi?id=478936 Richard Knausenberger changed: What|Removed |Added CC||liem...@gmail.com --- Comment #23 from Richard Knausenberger --- (In reply to qlum from comment #22) > Testing it again on plasma 6.0.1 and qt 6.7 I can confirm that I can bind > the calculator key again. > However, I do need to manually set the binding again, as the old binding > will remain non-functional. Plasma 6.0.1, Qt 6.7.7-1 on openSUSE Tumbleweed/X11 here, still doesn't work for the calculator key of my Ducky One keyboard. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476639] New: Doesn't start on Wayland on Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=476639 Bug ID: 476639 Summary: Doesn't start on Wayland on Ubuntu 22.04 Classification: Applications Product: Spectacle Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: liem...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** When I try to open Spectacle on Wayland on Ubuntu 22.04 (64 bit), Gnome 42.9 it doesn't open. Error message: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files" Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files" Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files" Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files" Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files" Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files" Error calling KWin DBus interface: "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.KWin was not provided by any .service files" QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.122' Segentation fault *** STEPS TO REPRODUCE 1. Use Ubuntu 22.04 2. Login with Wayland 3. Try to open Spectacle OBSERVED RESULT Spectacle doesn't open EXPECTED RESULT Spectacle works on Xorg, but not on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463158] Closes application launcher menu automatically when e.g. mounting drive
https://bugs.kde.org/show_bug.cgi?id=463158 --- Comment #2 from Richard Knausenberger --- (In reply to Patrick Silva from comment #1) > Right-click on the applet. There is an option to not open automatically > after mounting a device. No no, the auto open on mount is great (and I don't want to disable it completely). It just should auto close "higher priority" applets like the application launcher menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463158] New: Closes application launcher menu automatically when e.g. mounting drive
https://bugs.kde.org/show_bug.cgi?id=463158 Bug ID: 463158 Summary: Closes application launcher menu automatically when e.g. mounting drive Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: liem...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 154649 --> https://bugs.kde.org/attachment.cgi?id=154649=edit Video SUMMARY When you plug in e.g. an external drive, the notification applet on the panel automatically opens and shows the list of mounted drives. While this is great, there is a minor but annoying issue with it: When I plug in my backup drive, open the application launcher menu and start typing (to open my backup application), the opening notification applet mounted drive list automatically closes my application launcher menu. There is a delay between plugging an external drive in and when it actually gets mounted (and the applet opens the drive list). In this time I can open the application menu and start typing - but usually I am too slow, so it closes automatically while I'm still typing. This is quite annoying, since the - currently in use - application launcher menu should have priority. I made a short video about it (in the attachments). The video start immediately after i plugged in my external drive. Maybe some kind of a priority system for applets could fix this? STEPS TO REPRODUCE 1. plug in a drive 2. open the application menu OBSERVED RESULT The application menu gets closed automatically and the notification applets drive list opens. EXPECTED RESULT The application menu should stay open, the notification applets drive list shouldn't open automatically. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463058] New: Better grid for desktop applets
https://bugs.kde.org/show_bug.cgi?id=463058 Bug ID: 463058 Summary: Better grid for desktop applets Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: liem...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY *** After setting applets on a desktop multiple times I can say the current resizing system is not very convenient. I had troubles making multiple applets the same size and aligning them. I think a better grid system that lets you snap to other applets when resizing would fix this. *** STEPS TO REPRODUCE 1. Add an applet to the desktop and resize it 2. Add another applet to the desktop 3. Try to resize it, so it fits the size of the other one perfectly SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462550] Sometimes single random digits disappear with AMD GPU
https://bugs.kde.org/show_bug.cgi?id=462550 Richard Knausenberger changed: What|Removed |Added CC||liem...@gmail.com --- Comment #2 from Richard Knausenberger --- Plasma 5.26.4, Nvidia, bug is still there. Switching to another font (e.g. Open Sans instead of the default Noto Sans) fixes it for me. As far as I remember it only happened to the digital clock applet on my second screen desktop, never happened to the one in the panel of my main screen. Could also be because I show the date on my main screen one, but not on the desktop applet on my second screen. But I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 463033] New: Nvidia stopped working after recent driver update
https://bugs.kde.org/show_bug.cgi?id=463033
Bug ID: 463033
Summary: Nvidia stopped working after recent driver update
Classification: Plasma
Product: plasma-systemmonitor
Version: 5.26.4
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: liem...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
SUMMARY
***
Utilization, VRAM, temperature, etc. worked with my Nvidia gpu before, but
since a recent driver update (I'm now on 525.60.11, but it broke 2 or 3 updates
before) it's no longer working. It still detects my Nvidia gpu (GPU1), but it
shows 0% utilization, 0°C temperature, 0 MB VRAM, etc.
The desktop applet ("system monitor") is affected, too (same behavior there).
Nvidia X Server Settings and the nvidia-smi still show the utilization, vram
usage, temperature, etc. correctly. Other applications (like Unigine Valley
benchmark) still show the correct values.
***
STEPS TO REPRODUCE
1. Update nvidia driver
2. try to show utilization/vram/temperature with Systemmonitor application or
desktop applet
OBSERVED RESULT
Shows 0%, 0°C, 0MB, etc.
EXPECTED RESULT
Shows the real values (e.g. 90%, 71°C, 2000MB)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
ADDITIONAL INFORMATION
Tested with multiple gpus (GTX 1080, RTX 3070)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 456309] Nvidia driver updates breaks logout greeter temporarily
https://bugs.kde.org/show_bug.cgi?id=456309 --- Comment #3 from Richard Knausenberger --- Finally I got a Nvidia update what caused this issue again. When I click on the report bug button, the KDE bug reporter tries to open a window but it immediately crashes. Can I get the logs from somewhere else? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456309] Nvidia driver updates breaks logout greeter temporarily
https://bugs.kde.org/show_bug.cgi?id=456309 --- Comment #2 from Richard Knausenberger --- (In reply to Nate Graham from comment #1) > Normally I'd tell you that you have to reboot after updating your NVIDIA > drivers, but it seems like this is preventing you from doing just that! How > perverse. > > Can you attach a backtrace of the crash? Sure! I will as soon as the next Nvidia update get's released. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456309] New: Nvidia driver updates breaks logout greeter temporarily
https://bugs.kde.org/show_bug.cgi?id=456309 Bug ID: 456309 Summary: Nvidia driver updates breaks logout greeter temporarily Product: plasmashell Version: 5.25.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: liem...@gmail.com Target Milestone: 1.0 SUMMARY *** When I update my Nvidia drivers (via apt/zypper/etc) the logout greeter crashes. To reboot, I have to use the terminal. After the reboot everything works again. It's just after an update of the Nvidia driver. It always happened to me after every Nvidia driver update, on Kubuntu 18.04, Kubuntu 20.04 and now on openSUSE Tumbleweed. *** STEPS TO REPRODUCE 1. Update your Nvidia drivers 2. Try to reboot/shutdown/logout/... OBSERVED RESULT The logout greeter crashes. EXPECTED RESULT The logout greeter works as normal. SOFTWARE/OS VERSIONS Happened to all Nvidia updates on all Linux distros with KDE Plasma I used so far. ADDITIONAL INFORMATION Never happened without a Nvidia driver update. Never happened with other desktop environments (like Cinnamon). Found this old closed bug report https://bugs.kde.org/show_bug.cgi?id=364593 with a similar issue. Might be relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456122] New: Buggy applets on desktop after suspend returned
https://bugs.kde.org/show_bug.cgi?id=456122 Bug ID: 456122 Summary: Buggy applets on desktop after suspend returned Product: plasmashell Version: 5.25.1 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: liem...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 150257 --> https://bugs.kde.org/attachment.cgi?id=150257=edit Screenshot. Applets shoud neither by transparent, nor have this grey effect behind them. SUMMARY *** With Plasma 5.25 the buggy applets after suspend returned (see screenshots below). I haven't seen it for a long time, with the update to Plasma 5.25 they returned. If you logout and login again it's fixed. Replacing Plasmashell (plasmashell --replace) doesn't work. *** STEPS TO REPRODUCE 1. Update to Plasma 5.25 2. Add applets to the desktop 3. Suspend and resume from suspend OBSERVED RESULT Applets don't display correctly EXPECTED RESULT Applets are displayed as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (64 Bit) KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Nvidia GTX 1080 GPU (Nvidia 515.48.07 drivers), X, not Wayland -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 454870] New: Icon request: 3D objects (obj, gltf, stl, etc)
https://bugs.kde.org/show_bug.cgi?id=454870 Bug ID: 454870 Summary: Icon request: 3D objects (obj, gltf, stl, etc) Product: Breeze Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: liem...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 149476 --> https://bugs.kde.org/attachment.cgi?id=149476=edit Screenshot of current icons I noticed 3D object files (like obj and gltf) don't have an icon. That's sad, since 3D files are a common file type. It would be great if we could have a 3D-files icon. (Not a preview - even if this would be even better - but at least an icon, not just the default one. Maybe a 3D cube or something.) The screenshot was taken on Plasma 5.24.5 on openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426078] New: transparent controlpanel and menus after standy
https://bugs.kde.org/show_bug.cgi?id=426078 Bug ID: 426078 Summary: transparent controlpanel and menus after standy Product: kwin Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: liem...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 5.4.0-42-generic x86_64 Distribution: Ubuntu 18.04.5 LTS -- Information about the crash: - Unusual behavior I noticed: After waking up from standby the control panels and menus are transparent sometimes. I can fix this by loging out and in again. I use the standard Kubuntu Breeze theme and I disabled transparency in the Plasma settings. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f20abe51cc0 (LWP 9189))] Thread 8 (Thread 0x7f1fdce30700 (LWP 27982)): #0 0x7f20a481e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f208c019330) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f20a481e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f208c0192e0, cond=0x7f208c019308) at pthread_cond_wait.c:502 #2 0x7f20a481e9f3 in __pthread_cond_wait (cond=0x7f208c019308, mutex=0x7f208c0192e0) at pthread_cond_wait.c:655 #3 0x7f20a898d5ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f20a39f26a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f20a39f2b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f20a898c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f20a48186db in start_thread (arg=0x7f1fdce30700) at pthread_create.c:463 #8 0x7f20ab7cba3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f2073fff700 (LWP 27981)): #0 0x7f20ab7bedf6 in __GI_ppoll (fds=0x7f206c0058e8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f20a8bbf561 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f20a8bc0c7e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f20a8b6890a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f20a898723a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f20a33046f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f20a898c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f20a48186db in start_thread (arg=0x7f2073fff700) at pthread_create.c:463 #8 0x7f20ab7cba3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f208a168700 (LWP 25874)): #0 0x7f20a481e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558df8061f04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f20a481e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558df8061eb0, cond=0x558df8061ed8) at pthread_cond_wait.c:502 #2 0x7f20a481e9f3 in __pthread_cond_wait (cond=0x558df8061ed8, mutex=0x558df8061eb0) at pthread_cond_wait.c:655 #3 0x7f20a898d5ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f20a39f26a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f20a39f2b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f20a898c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f20a48186db in start_thread (arg=0x7f208a168700) at pthread_create.c:463 #8 0x7f20ab7cba3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f207b7ff700 (LWP 11444)): #0 0x7f20ab7bedf6 in __GI_ppoll (fds=0x558df7db24f8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f20a8bbf561 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f20a8bc0c7e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f20a8b6890a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f20a898723a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f20a898c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f20a48186db in start_thread (arg=0x7f207b7ff700) at pthread_create.c:463 #7 0x7f20ab7cba3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f207282a700 (LWP 9363)): #0 0x7f20a481e9f3 in futex_wait_cancelable (private=,
[dolphin] [Bug 414063] New: Autoscroll after renaming file
https://bugs.kde.org/show_bug.cgi?id=414063 Bug ID: 414063 Summary: Autoscroll after renaming file Product: dolphin Version: 19.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: liem...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- When I rename a file with Dolphin, it automatically scrolls to the currently renamed file. This is annoying if you want to rename several screenshot in one big folder (called screenshot1, screenshot2, etc.) and you have to scroll back to the others every time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406767] New: kwin segmentation fault
https://bugs.kde.org/show_bug.cgi?id=406767 Bug ID: 406767 Summary: kwin segmentation fault Product: kwin Version: 5.12.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: liem...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.7) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.15.0-47-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Sometimes when I wake my computer up from standby the desktop gets black. I have to run the command "plasmashell", then the KDE desktop works again The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8a6a0e9cc0 (LWP 4045))] Thread 8 (Thread 0x7f8a3dfc8700 (LWP 9145)): [KCrash Handler] #6 0x7f8a37289020 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #7 0x7f8a371766aa in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #8 0x7f8a3717e413 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #9 0x7f8a371eb453 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #10 0x7f8a371eb619 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #11 0x7f8a371ede06 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #12 0x7f8a371ee4fe in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #13 0x7f8a37183ba3 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #14 0x7f8a36da5b4b in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 #15 0x7f8a61c49f88 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f8a61c4f85e in QSGBatchRenderer::Renderer::render() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f8a61c402a0 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f8a61c4075b in QSGRenderer::renderScene(unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f8a61c7aaf0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f8a61cd8b68 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7f8a61c83bbc in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7f8a61c88ac8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7f8a66c2217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f8a62aae6db in start_thread (arg=0x7f8a3dfc8700) at pthread_create.c:463 #25 0x7f8a69a6188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f8a4ce2e700 (LWP 9141)): #0 0x7f8a69a54cf6 in __GI_ppoll (fds=0x7f8a4401a778, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f8a66e55671 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8a66e56d8e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f8a66dfea1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8a66c1d23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8a6159a6f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f8a66c2217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8a62aae6db in start_thread (arg=0x7f8a4ce2e700) at pthread_create.c:463 #8 0x7f8a69a6188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f8a36393700 (LWP 6044)): #0 0x7f8a69a54cf6 in __GI_ppoll (fds=0x7f8a2c001298, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f8a66e55671 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8a66e56d8e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f8a66dfea1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8a66c1d23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8a66c2217d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8a62aae6db in start_thread (arg=0x7f8a36393700) at pthread_create.c:463 #7 0x7f8a69a6188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f8a35b92700 (LWP 4226)): #0 0x7f8a62ab49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f8a66056fb8) at
[plasmashell] [Bug 400971] Widget font sometimes disappears after suspend
https://bugs.kde.org/show_bug.cgi?id=400971 Richard Knausenberger changed: What|Removed |Added CC||liem...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400971] New: Widget font sometimes disappears after suspend
https://bugs.kde.org/show_bug.cgi?id=400971 Bug ID: 400971 Summary: Widget font sometimes disappears after suspend Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: liem...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 After suspending, sometimes the fonts of the desktop widgets disappears. So there is still the widget, but without any font. The clock in the panel has the same problem, but much rarer. I am using Kubuntu 18.04 with Plasma 5.12, but I had the same problem in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380267] New: Dolphin - Icon for each file
https://bugs.kde.org/show_bug.cgi?id=380267 Bug ID: 380267 Summary: Dolphin - Icon for each file Product: dolphin Version: 17.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: richard.knausenber...@gmail.com Target Milestone: --- Hello, The only missing thing in Dolphin is that you can't set an icon for each audio/video/... file. You can only change every .mp3 file icon for example. I would like to change the icon of each file itself (like in Nautilus oder Nemo). It would be great if you add that in Dolphin. Thanks a lot Richard Knausenberger -- You are receiving this mail because: You are watching all bug changes.
