[plasmashell] [Bug 484590] [feature/bug] Wayland Notification not placed on active/primary screen
https://bugs.kde.org/show_bug.cgi?id=484590 --- Comment #2 from kolorafa --- I have(In reply to Nate Graham from comment #1) > Notifications appear next to the Notifications widget, one of which is in > the system tray. So notifications will always appear on the screen with that > widget on it. > > The ability to manually choose its screen (not just its position on that > screen) hasn't been implemented yet, per Bug 446961 which it looks like > you've already found. Marking as a duplicate of it, since the current > behavior you're seeing is intentional. > > *** This bug has been marked as a duplicate of bug 446961 *** I have the widget (and tray icons) on all 3 monitors, and I want that to stay this way. But thanks to your answer I think I found a "workaround", as I can leave the tray icons there, but I can disable only the notification widget in icon settings, only leaving the notification icon on one screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489096] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=489096 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489096] New: plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=489096 Bug ID: 489096 Summary: plasmashell crash Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: kde_...@dlk.pl Target Milestone: 1.0 Application: plasmashell (6.1.0) Qt Version: 6.7.1 Frameworks Version: 6.3.0 Operating System: Linux 6.9.5-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.0 [CoredumpBackend] -- Information about the crash: Was just closing flatpak app com.github.vikdevelop.timer. And the plasmashell froze and then restarted. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 SystemClipboard::checkClipData (this=0x61e8e0517e20, mode=QClipboard::Selection) at /usr/src/debug/plasma-workspace/plasma-workspace-6.1.0/klipper/systemclipboard.cpp:157 #6 0x7dbce8ba17e7 in QtPrivate::QSlotObjectBase::call (this=, r=, a=, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #7 doActivate (sender=, signal_index=, argv=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4086 #8 0x7dbce898db01 in KSystemClipboard::changed (this=, _t1=) at /usr/src/debug/kguiaddons/build/src/KF6GuiAddons_autogen/include/moc_ksystemclipboard.cpp:142 #9 0x7dbce8ba17e7 in QtPrivate::QSlotObjectBase::call (this=, r=, a=, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489096] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=489096 --- Comment #1 from kolorafa --- Created attachment 170904 --> https://bugs.kde.org/attachment.cgi?id=170904&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488879] Application: kwin_wayland (kwin_wayland), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=488879 --- Comment #4 from kolorafa --- (In reply to Zamundaaa from comment #3) > The information you provided isn't useful, because the binary and debug > information is for 6.1 and the running instance was 6.0. We need a proper > backtrace, without it this is not actionable. That was the whole point of this PR, to make is useful in the future if this happen again (and I can guess that it will). Because the crash handler UI that showed was useless in this case, as it did downloaded debugging symboles but looks like wrong ones. What can be done to make it useful? Some manual work can be done to get more data from that crash or to prepare for the next one? Or maybe something could be done to improve the crash UI to help with similar crashes after update in the future? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488879] Application: kwin_wayland (kwin_wayland), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=488879 --- Comment #2 from kolorafa --- It most likely related to the OS Update, but if so, it should tell the user that "reboot advices or it might crash", but better ... fix that it will not crash, or even if it crashes it would not take down everything with it ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488879] Application: kwin_wayland (kwin_wayland), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=488879 --- Comment #1 from kolorafa --- Blocking sending request because "Data from crash report are not helpful" is also ... just bad, unless the signal that it did crash was reported somewhere, but I doubt as that would say data is leaked without user knowledge. Why? Because the desktop could crash for a lot of people and non would be wiser... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488879] Application: kwin_wayland (kwin_wayland), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=488879 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488879] New: Application: kwin_wayland (kwin_wayland), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=488879 Bug ID: 488879 Summary: Application: kwin_wayland (kwin_wayland), signal: Segmentation fault Classification: Plasma Product: kwin Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- Created attachment 170739 --> https://bugs.kde.org/attachment.cgi?id=170739&action=edit saved crash report SUMMARY STEPS TO REPRODUCE 1. Use the desktop as normal for few days 24h/d 2. (maybe?) do an update to newer version 3. Use the desktop as normal for some time OBSERVED RESULT Crash - killing all my ongoing work ! EXPECTED RESULT Even if Crashed - it should not crash any other app! SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.5 (updated to 6.1 without reboot) KDE Frameworks Version: ?? Qt Version: ?? ADDITIONAL INFORMATION the submit bug was not working even after clicking to "fetch diagnostic symbols", that only proves that once again kwin_wayland is not production ready... (kwin_x11 did actually recover just fine without losing a session ...) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484590] New: [feature/bug] Wayland Notification not placed on active/primary screen
https://bugs.kde.org/show_bug.cgi?id=484590 Bug ID: 484590 Summary: [feature/bug] Wayland Notification not placed on active/primary screen Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: kde_...@dlk.pl CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY Wayland: Can't change on which screen desktop notifications show up in multi-screen environment. Currently they are showing only on most right screen (which is TV behind). If I remember correctly previously/on X11 they appear on active screen (where the mouse/active window), currently they always show on most right screen for me. STEPS TO REPRODUCE 1. Execute `notify-send "test"` OBSERVED RESULT Notification showing on a most right screen (in my case it's a TV behind me dedicated for watching media). EXPECTED RESULT Notification showing on active screen (where the mouse pointer/active window is?) or primary / selected in settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.2 Qt Version: 6.6.2 Platform: Wayland ADDITIONAL INFORMATION I see I can change the position on the screen of the notification so I can set it to be centered, but not the screen so it will still be centered on most right screen for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme
https://bugs.kde.org/show_bug.cgi?id=482645 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470375] New: Setting modal showing old konsole scroll history size on reopen.
https://bugs.kde.org/show_bug.cgi?id=470375 Bug ID: 470375 Summary: Setting modal showing old konsole scroll history size on reopen. Classification: Applications Product: konsole Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- SUMMARY Can't change konsole scroll history size without switching to unlimited/disabled first. STEPS TO REPRODUCE 1. Open the history size setting. 2. Change the value in any way (scroll/number/arrows) 3. Optionally - Change the radio button but select it back to the same position as initially 4. Save changes (clicking [ OK ] ) OBSERVED RESULT The actual history size is changed, but when you re-open the setting modal the old value is visible. The only way to force setting modal show a different value would be to switch to unlimited/disabled press [OK] and then switch to limit with a value. It looks like the setting modal window is remembering the old value. EXPECTED RESULT Get the correct/effective value on reopen. SOFTWARE/OS VERSIONS Linux: 6.3.4-arch1-1 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Recording: https://nextcloud.dlk.pl/s/T7xgcA6ZdHwjmRK -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442684] New: Dolphin keeps freezing on (slow) remote sshfs (and local) filesystem
https://bugs.kde.org/show_bug.cgi?id=442684 Bug ID: 442684 Summary: Dolphin keeps freezing on (slow) remote sshfs (and local) filesystem Product: dolphin Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kde_...@dlk.pl CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. connect to remote fs (sshfs host: folder) 2. open folder in dolphin with preview enabled and tree view (to increase the effect) 3. open dolphin, and experience 20s interface freeze on every action once doplhin interacts with remote fs OBSERVED RESULT Looks like loading (thumbnails?) keeps freezing whole dolphin It's very bad experience to wait sometimes over 20s to go back to different directory or trying to select files to do something with them. EXPECTED RESULT never freeze interface, and just load thumbnails and file details slowly SOFTWARE/OS VERSIONS Linux/KDE Plasma: plasmashell 5.22.5 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I know that doing async task is hard and prone to problems, but it's very bad experience. Same behavior happen if I have hard drive in sleep state, and I open dolphin. Dolphin doesn't even show for the whole thime hard drive spinup (i hear it very clearly as It's external usb drive and it takes at least 7s) and it doesn't matter if I want to use it, as long as It's mounted and shown in dolphin, doplhin trying to get drive usage and that is waking up hard drive. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438929] New: kwin_wayland crashes when window is resized for too long
https://bugs.kde.org/show_bug.cgi?id=438929 Bug ID: 438929 Summary: kwin_wayland crashes when window is resized for too long Product: kwin Version: 5.22.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: egl Assignee: kwin-bugs-n...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- SUMMARY Crash when window is resized Reproducible STEPS TO REPRODUCE 1. Login 2. Run (autostart) "rambox" (as it's most buggy app I have, even on X) 3. Resize it (I'm using META+right mouse button) 4. Crash after few seconds of constantly resizing OBSERVED RESULT Crash ``` cze 19 23:39:44 kolorafa-newarch audit[3537]: ANOM_ABEND auid=1000 uid=1000 gid=100 ses=2 pid=3537 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 cze 19 23:39:44 kolorafa-newarch kernel: kwin_wayland[3537]: segfault at 318 ip 7fb0800d472f sp 7fff8f99bf60 error 4 in libEGL_nvidia.so.465.31[7fb080056000+de000] cze 19 23:39:44 kolorafa-newarch kernel: Code: 02 00 00 31 db eb 93 0f 1f 40 00 41 56 41 55 49 89 d5 41 54 55 31 d2 53 49 89 fc 48 89 f3 be 01 00 00 00 45 89 c6 48 83 ec 20 <48> 8b af 18 03 00 00 48 89 4c 24 08 48 89 ef e8 1d 8a 03 00 84 c0 cze 19 23:39:44 kolorafa-newarch kernel: audit: type=1701 audit(1624138784.797:458): auid=1000 uid=1000 gid=100 ses=2 pid=3537 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 cze 19 23:39:44 kolorafa-newarch systemd[1]: Starting Start containers: sonarr plex nzbget emby... cze 19 23:39:44 kolorafa-newarch audit: BPF prog-id=67 op=LOAD cze 19 23:39:44 kolorafa-newarch audit: BPF prog-id=68 op=LOAD cze 19 23:39:44 kolorafa-newarch audit: BPF prog-id=69 op=LOAD cze 19 23:39:44 kolorafa-newarch systemd[1]: Started Process Core Dump (PID 6633/UID 0). (...) cze 19 23:39:45 kolorafa-newarch systemd-coredump[6635]: [🡕] Process 3537 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 3537: #0 0x7fb0800d472f n/a (libEGL_nvidia.so.0 + 0x7e72f) #1 0x7fb0800d70a2 n/a (libEGL_nvidia.so.0 + 0x810a2) #2 0x7fb0800d3f4a n/a (libEGL_nvidia.so.0 + 0x7df4a) #3 0x7fb0800d6f58 n/a (libEGL_nvidia.so.0 + 0x80f58) #4 0x7fb0800a03d6 n/a (libEGL_nvidia.so.0 + 0x4a3d6) #5 0x7fb082142db0 n/a (KWinWaylandDrmBackend.so + 0x3cdb0) #6 0x7fb0891063bb n/a (libQt5Core.so.5 + 0x2f03bb) #7 0x7fb089af66be _ZN14KWaylandServer28EglStreamControllerInterface22streamConsumerAttachedEPNS_16SurfaceInterfaceEPvP8wl_array (libKWaylandServer.so.5 + 0x786be) #8 0x7fb089b0eb71 n/a (libKWaylandServer.so.5 + 0x90b71) #9 0x7fb085fcfacd n/a (libffi.so.7 + 0x6acd) #10 0x7fb085fcf03a n/a (libffi.so.7 + 0x603a) #11 0x7fb0870f8124 n/a (libwayland-server.so.0 + 0xd124) #12 0x7fb0870f357c n/a (libwayland-server.so.0 + 0x857c) #13 0x7fb0870f607a wl_event_loop_dispatch (libwayland-server.so.0 + 0xb07a) #14 0x7fb089b0cf67 _ZN14KWaylandServer7Display14dispatchEventsEv (libKWaylandServer.so.5 + 0x8ef67) #15 0x7fb0891063bb n/a (libQt5Core.so.5 + 0x2f03bb) #16 0x7fb089109880 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2f3880) #17 0x7fb08910a08d _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2f408d) #18 0x7fb089f40d62 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15ad62) #19 0x7fb0890cf00a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b900a) #20 0x7fb089124f74 _ZN27QEventDispatcher
[plasmashell] [Bug 418616] plasmashell crash after arch update
https://bugs.kde.org/show_bug.cgi?id=418616 --- Comment #1 from kolorafa --- * Problem resolved by removing from .config/kdeglobals [QtQuickRendererSettings] SceneGraphBackend=software ( somehow skipped the "removing" part :) ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418616] New: plasmashell crash after arch update
https://bugs.kde.org/show_bug.cgi?id=418616 Bug ID: 418616 Summary: plasmashell crash after arch update Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.2) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8-arch1-1 x86_64 Windowing system: X11 Distribution: Antergos Linux -- Information about the crash: - What I was doing when the application crashed: updating arch linux - Problem resolved by from .config/kdeglobals [QtQuickRendererSettings] SceneGraphBackend=software The crash can be reproduced every time. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f780e312840 (LWP 27066))] Thread 8 (Thread 0x7f77a7fff700 (LWP 27075)): #0 0x7f78126174fc in read () at /usr/lib/libc.so.6 #1 0x7f7810e6b8c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7810ebb001 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f7810ebc748 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f7810ebc871 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f7812bd40ec in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7812b7a57c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f781299ee62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f781299ffd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7811ddf46f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f78126263d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f77ac9fd700 (LWP 27074)): #0 0x7f7811de5cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f78127b6ea1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:865 #2 std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f77efecc00d in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at /usr/lib/libQt5WebKit.so.5 #4 0x7f77f0703f28 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7f77f0705901 in () at /usr/lib/libQt5WebKit.so.5 #6 0x7f77efece71a in () at /usr/lib/libQt5WebKit.so.5 #7 0x7f77efef17bb in () at /usr/lib/libQt5WebKit.so.5 #8 0x7f7811ddf46f in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f78126263d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f77ad1fe700 (LWP 27073)): #0 0x7f78126174fc in read () at /usr/lib/libc.so.6 #1 0x7f7810e6b8c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7810ebb001 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f7810ebc748 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f7810ebc871 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f7812bd40ec in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7812b7a57c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f781299ee62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f781299ffd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7811ddf46f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f78126263d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f77ad9ff700 (LWP 27072)): #0 0x7f781261babf in poll () at /usr/lib/libc.so.6 #1 0x7f7810ebc7a0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7810ebc871 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f7812bd40ec in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7812b7a57c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f781299ee62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f781299ffd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7f7811ddf46f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f78126263d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f77eec83700 (LWP 27071)): #0 0x7f7811de5cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f78127b6ea1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:865 #2 std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f77f14fb5bb in () at /usr/lib/libQt5WebKit.so.5 #4 0x7f77f
[ksmserver] [Bug 376346] Can't restart OS from menu.
https://bugs.kde.org/show_bug.cgi?id=376346 --- Comment #4 from kolorafa --- Currently it only happening after I do a Arch system update, as there is a version mix between running apps/libs and the newly installed. And I don't remember the circumstance about that report from then, sorry. But it would be nice to have a better fallback on shutdown/reboot buttons in menu if confirmation prompt would fail to start because of mix after os update, arch users mostly know how to start "reboot" manually, (but then the session (window placement, etc) is not saved as far as i noticed) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413087] New: lockscreen broken when mediacontrols active
https://bugs.kde.org/show_bug.cgi?id=413087 Bug ID: 413087 Summary: lockscreen broken when mediacontrols active Product: plasmashell Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Lock/logout applet Assignee: plasma-b...@kde.org Reporter: kde_...@dlk.pl Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Start a media player that works with the latest breaking changes in mpros (audacious) - play music or have i in pause 2. wait for screen to lock or just META+L to lock OBSERVED RESULT only background is showing, while moving mouse or clicking buttons nothing happens, and showing in log every few seconds: kernel: kscreenlocker_g[8010]: segfault at 7ffe586a6fd0 ip 7f7eff625558 sp 7ffe586a6fa0 error 6 in libQt5Gui.so.5.13.1[7f7eff2b4000+414000] kernel: Code: e5 40 e9 6b ff ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55 41 54 55 53 48 89 fb 48 81 ec c8 38 00 00 48 8b 6f 10 <48> 89 74 24 30 64 48 8b 04 25 28 > kernel: audit: type=1701 audit(1571316489.797:178): auid=1000 uid=1000 gid=100 ses=3 pid=8010 comm="kscreenlocker_g" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1 If I stop the playback or close the player (so the media icon disapear from tray) then it works (as media controls doesn't show on lock screen). EXPECTED RESULT show gui to login :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (old Antergos) KDE Plasma Version: 5.17.0 KDE Frameworks Version: Qt Version: 5.13.1 kde4-config -v Qt: 4.8.7 KDE Development Platform: 4.14.38 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405820] window placement behaviour is broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=405820 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl --- Comment #7 from kolorafa --- @Damian I got exactly the same behavior but on xorg, enabling "Active screen follows mouse" on Focus tab did fix it for me. (overall, <3 plasma) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385834] when FAST SCROLLING on audio volume plasmoid to change volume-->plasmoid gets confused
https://bugs.kde.org/show_bug.cgi?id=385834 --- Comment #3 from kolorafa --- I found a clue, i discovered for example that the scroll also goes crazy when scrolling pages in Okular, but only if there are some floating windows like showing a sound volume level in the middle of the screen. as soon as it disappears the scroll goes back to being ok - no back-scrolling behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385834] when FAST SCROLLING on audio volume plasmoid to change volume-->plasmoid gets confused
https://bugs.kde.org/show_bug.cgi?id=385834 --- Comment #2 from kolorafa --- I got this behavior today, as yesterday i did os upgrade, but jumped few versions because of waiting for some needed app to be updated latest OS libs. OS: Arch plasmashell 5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385834] when FAST SCROLLING on audio volume plasmoid to change volume-->plasmoid gets confused
https://bugs.kde.org/show_bug.cgi?id=385834 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl --- Comment #1 from kolorafa --- same here on mouse, I need to scroll very slow. If scrolling fast it randomly jumps but if doing it constantly if scrolling up the volume overall goes down, and scrolling down volume goes up ... how can i help debug it? mouse wheel fine (checked on xev) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #11 from kolorafa --- plasmashell 5.13.1 Funny behaviour as it refreshes around other windows :) https://youtu.be/bTASAx0jbpU (on NVIDIA graphic / nvidia driver) On Intel/mesa - OS still not up-to-date because of missing a way to run a outdated necessary app with newest libraries, so probably one more week until it gets sorted out ready to update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #10 from kolorafa --- just experienced this bug on 5.12.5 and running default without tripple buffering - with one window of firefox -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #9 from kolorafa --- Workstation (laptop) with mesa (nvidia disabled): On the system with mesa i did run export KWIN_TRIPLE_BUFFER=1; kstart kwin_x11 --replace and as for now no artefacts I didn't reset theme/compositor on MESA (laptop) as it's my workstation that I could not affort to get a downtime for last few weeks, next week i will upgrade also my laptop and will try there too, but until new plasma doesn't have a fix i assume it will be exactly the same Workstation with nvidia only: i did also use tripple for short period, no errors noticed, today upgraded nvidia station to plasmashell 5.12.5 and running without tripple buffering, time will tell I saw the simple way to leave a PC working with Audacious (with "winamp" skin) for a few days, audacious continuously scroll the track name from left to right forcing refresh/render that triggers the bug, other app show the same problem but at longer time (as they refresh less frequently) Also maybe it happens when i have workstation locked, hard to tell. - AKA: tripple bufforing somehow helps MESA: not done anything NVIDIA: no change on theme/compositor reset -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #7 from kolorafa --- defaulting composition and using default theme didn't help, until i missed something: (now testing the triple bufforing on kwin) == Version === KWin version: 5.12.4 Qt Version: 5.10.1 Qt compile version: 5.10.1 XCB compile version: 1.13 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11906000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans [GOOG],10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 8 focusPolicyIsReasonable: true borderSnapZone: 15 windowSnapZone: 15 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 27 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 27 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 12 commandAll2: 12 commandAll3: 14 keyCmdAllModKey: 16777250 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: false Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 3 Screen 0: - Name: DVI-D-0 Geometry: 1280,0,1920x1080 Scale: 1 Refresh Rate: 60 Screen 1: - Name: DVI-I-0 Geometry: 0,0,1280x1024 Scale: 1 Refresh Rate: 75.0247 Screen 2: - Name: DP-1 Geometry: 3200,0,1920x1080 Scale: 1 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL version string: 4.6.0 NVIDIA 390.48 OpenGL platform interface: GLX OpenGL shading language version string: 4.60 NVIDIA Driver: NVIDIA Driver version: 390.48 GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 X server version: 1.19.6 Linux kernel version: 4.16.5 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_dialogparent kwin4_effect_login kwin4_effect_fade kwin4_effect_frozenapp kwin4_effect_morphingpopups kwin4_effect_translucency kwin4_effect_logout kwin4_effect_maximize kwin4_effect_windowaperture slidingpopups wobblywindows slide screenshot minimizeanimation flipswitch desktopgrid coverswitch colorpicker sheet presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_dialogparent: kwin4_effect_login: kwin4_effect_fade: kwin4_effect_frozenapp: kwin4_effect_morphingpopups: kwin4_effect_translucency: kwin4_effect_logout: kwin4_effect_maximize: kwin4_effect_windowape
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #5 from kolorafa --- It was set to 1year, by that time i would probably repaste more/new but ok :) Version === KWin version: 5.12.4 Qt Version: 5.10.1 Qt compile version: 5.10.1 XCB compile version: 1.13 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11906000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.kwin.aurorae Theme: __aurorae__svg__seven-black Blur: 1 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans [GOOG],10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 8 focusPolicyIsReasonable: true borderSnapZone: 15 windowSnapZone: 15 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 27 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 27 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 12 commandAll2: 12 commandAll3: 14 keyCmdAllModKey: 16777250 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 2 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: false Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 3 Screen 0: - Name: DVI-D-0 Geometry: 1280,0,1920x1080 Scale: 1 Refresh Rate: 60 Screen 1: - Name: DVI-I-0 Geometry: 0,0,1280x1024 Scale: 1 Refresh Rate: 60.0197 Screen 2: - Name: DP-1 Geometry: 3200,0,1920x1080 Scale: 1 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 390.48 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 390.48 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.19.6 Linux kernel version: 4.15.14 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: yes Loaded Effects: --- zoom kwin4_effect_dialogparent kwin4_effect_login kwin4_effect_fade kwin4_effect_frozenapp kwin4_effect_morphingpopups kwin4_effect_translucency kwin4_effect_logout kwin4_effect_maximize kwin4_effect_windowaperture slidingpopups wobblywindows slide screenshot minimizeanimation flipswitch desktopgrid coverswitch colorpicker sheet presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_dialogparent: kwin4_effect_login: kwin4_effect_fade: kwin4_effect_frozenapp: kwin4_effect_morphingpopups: kwin4_effect_translucency: kwin4_effect_logout: kwin4_effect_maximize: kwin4_effect_windowaperture: slidingpopups: fadeInTime: 150
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #3 from kolorafa --- Intel: https://pastebin.com/5wdV9hdw Nvidia: https://pastebin.com/vMmJJNGt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 --- Comment #1 from kolorafa --- Maybe related to: https://bugs.kde.org/show_bug.cgi?id=335330 I will try: export KWIN_TRIPLE_BUFFER=1 and report back if i see flickering (normally it takes few days to start flickering). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393300] New: heavy refreshed windows stops rendering and/or flicker after a time
https://bugs.kde.org/show_bug.cgi?id=393300 Bug ID: 393300 Summary: heavy refreshed windows stops rendering and/or flicker after a time Product: kwin Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- https://youtu.be/eBWM7MeuLEk https://youtu.be/XIAno8r5UTs What helps is to close/reopen window or restart kwin what doesn't help (only temporary refreshes the content): - minimizing - resizing - doing some action on some elements that trigger refresh Drivers: MESA & NVIDIA prop. OS: Arch up-to-date Timeframe: it happens for at least as long as I use Plasma (maybe a year now), on every PC I have (All Arch Plasma). Rendering backend: OpenGL 3.1 Custom settings: Enabled some desktop effects like Fade, Wobbly Windows (also, Wobbly Windows randomly show flickering artefacts in places animation took place but no longer is taking place as long as you hold the window), plasmashell (as it constantly refresh time in seconds). When does it show .. after few days while running a window with high refresh rate like Audacious (with constantly moving text in window), or older pavcontrol (as there sound level bar), or chrome. Less often (or at least i didn't saw this problem) on windows with less refresh rate like terminal, dolphin. Kernel: 4.15.14 Example of Intel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 5600 (Broadwell GT2) (0x1612) Version: 17.3.7 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5600 (Broadwell GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.7 OpenGL core profile shading language version string: 4.50 Example of NVIDIA: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 390.48 OpenGL core profile shading language version string: 4.60 NVIDIA -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390676] unpredictable desktop settings
https://bugs.kde.org/show_bug.cgi?id=390676 --- Comment #10 from kolorafa --- KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 27 and type 'Read', disabling... QSocketNotifier: Invalid socket 55 and type 'Read', disabling... QSocketNotifier: Invalid socket 62 and type 'Read', disabling... KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Pułapka debuggera/breakpoint (zrzut pamięci) plasmashell Debugger trap/breakpoing(memory dump) plasmashell almost every time plasmashell dies if I switch between "Desktop" and "Folder view" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390674] plasmashell freeze as long as you have gnome-disks running after doing a sudo from it
https://bugs.kde.org/show_bug.cgi?id=390674 --- Comment #10 from kolorafa --- same here: $ qdbus org.kde.plasmashell / /DataEngine /DataEngine/applicationjobs /DataEngine/applicationjobs/JobWatcher STUCK AT THIS LINE UNTIL I CLOSED DISKS /FileUndoManager /MainApplication /PlasmaShell /Unity /klipper /org /org/freedesktop /org/freedesktop/Notifications /org/kde /org/kde/osdService /org/kde/plasmashell sudo gdb attach $(pidof plasmashell) -ex cont ctrl+c > thread apply all bt https://pastebin.com/dQmY7DqT btw, my trace is a mess, because I did try to install newest plasmashell from AUR to try "fix" for https://bugs.kde.org/show_bug.cgi?id=390676 but i didn't finish with success. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390676] unpredictable desktop settings
https://bugs.kde.org/show_bug.cgi?id=390676 --- Comment #6 from kolorafa --- If needed i can redo the video in english. For now you could download the current from youtube and expand video to multiple screen to better see what is going on. (Or you could use my favorite trick: 1. click fullscreen on youtube 2. ALT+F3 > more > disable fullscreen (the video will stay fullscreen but behave as window) 3. ALT+F3 > more > move to left screen 4. ALT+F3 > more > change size / resize over multiple screens (or you can use META+Mouse for 3-4)) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390676] unpredictable desktop settings
https://bugs.kde.org/show_bug.cgi?id=390676 --- Comment #5 from kolorafa --- Like you see on video: 1. All 3 screens set to desktop view, icons (x, desktop, x) - ok 2. screen 2 switched to home (desktop, home, desktop) icons (desktop, x, x) - error 3. screen 1 switched to home (home, home, desktop) icons (x, x, x) - error 4. screen 3 switched to home (home, home, home) icons (x, home, x) - ok 5. screen 2 switched to desktop (home, desktop, home) icons (x, desktop, x) - error 6. and 7. switch screen 3 to desktop and home - no change 8. screen 2 to desktop (desktop, desktop, home) icons (desktop, x, x) - error ... ok - like in the theory x - no icons Ok, it might require a reboot to correctly handle the change, or maybe need to close Settings after every change, but my personal question would be: How can i show the same icons on all screens like in plasmashell 5.11.5? (Or how to show the same directory on all screen). Also if we going into setting what is on primary, secondary and so on, then there should be a single place where you select: Primary: X Secondary: Y Third: Z For example the current view but in tabs for screen order. ... and then if you disconnect primary, then the next screen will get the primary, so then you do it like that: Primary: Desktop Secondary: nothing Third: Nothing then you get always icons on primary and for example me, i can set Primary: Desktop Secondary: Desktop Third: Desktop and i will have the 5.11 way :) The way settings are currently in 5.12 when you select "show desktop icons" and see nothing is wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390676] unpredictable desktop settings
https://bugs.kde.org/show_bug.cgi?id=390676 --- Comment #3 from kolorafa --- Created attachment 110869 --> https://bugs.kde.org/attachment.cgi?id=110869&action=edit screen layout from video Hi András The primary was the middle one (the one with the icons at first). Second should be the left one, but i don't know how to tell. (the left screen have a "panel padding" becase the physical screen top and bottom is broken, but still usable) plasmashell 5.11.5 - the same icons on every screen (i like it that way) plasmashell 5.12.X - icons only on first/primary (until you have something else on that screen) Is it a bug? Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390676] New: unpredictable desktop settings
https://bugs.kde.org/show_bug.cgi?id=390676 Bug ID: 390676 Summary: unpredictable desktop settings Product: dolphin Version: 17.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- I assume that Dolphin handles desktop icons (or they use the same engine/lib), please point me in the right direction if I'm wrong. Setting 3 screens to "show desktop icons". Expected result: show the same icons on every screen (like in 17.10) Current result: it shows desktop icons only on one (random?) screen Bad workaround: set to show files from ~/Desktop (it show them but doesn't resolve .desktop files so it's showing names with .desktop) also it works only on (random?) second screen https://youtu.be/U4yKDNcvk3g As show in video, I opened desktop setting for every screen and tried various combinations, and the result is crazy. For example if desktop icons is set to every screen only probably first/primary screen gets icons, if i switch primary to something else the second screen gets icons. It might be the "desired" by developer but at least not by me. But i think it's a bug as other settings also work "unpredictable" as for example i set it to show place - select home directory, and it only show it sometimes depending on other screen settings. If the desktop behavior was "expected" please fix/revert it back to the way it was, if someone want to have different icons on every screen then he could set them to different directories or add third option to "show only on primary". plasmashell: 5.12.1 kernel: 4.15.3-2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390674] New: plasmashell freeze as long as you have gnome-disks running after doing a sudo from it
https://bugs.kde.org/show_bug.cgi?id=390674 Bug ID: 390674 Summary: plasmashell freeze as long as you have gnome-disks running after doing a sudo from it Product: plasmashell Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: 1.0 After getting the sudo prompt the plasmashell freezes until i close gnome-disks https://youtu.be/036pSziFekM I forgot to run dolphin in english for the video. I can redo if that would help. Example: Iso file > open with > writting images to disk > gnome-disks select disk > proceed > sudo prompt > plasmafreze and stays until gnome-disks running Other apps and stuff working without problems. Plasmashells recovers and handles all queued events after unfreeze. kernel: 4.15.3-2-ARCH plasmashell: 5.12.1 This error exists for some time, I remember to hit it also in previous versions (i think 5.10 or earlier) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389542] Everything crashes when reaching 100% physical memory while having a lot of free swap.
https://bugs.kde.org/show_bug.cgi?id=389542 --- Comment #3 from kolorafa --- Found (probably) the cause of crashes -> zswap. After disabling zswap (that was enabled on both my pc) the crashes stopped. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389542] Everything crashes when reaching 100% physical memory while having a lot of free swap.
https://bugs.kde.org/show_bug.cgi?id=389542 kolorafa changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |INVALID --- Comment #2 from kolorafa --- Thanks, true, going to change makepkg settings to include debug and recompile from "sources" (pkgbuild) those apps that i see crashing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389542] Everything crashes when reaching 100% physical memory while having a lot of free swap.
https://bugs.kde.org/show_bug.cgi?id=389542 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389542] New: Everything crashes when reaching 100% physical memory while having a lot of free swap.
https://bugs.kde.org/show_bug.cgi?id=389542 Bug ID: 389542 Summary: Everything crashes when reaching 100% physical memory while having a lot of free swap. Product: kwin Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- Application: kwin_x11 (5.11.5) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.14.15-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Opening a lof ot browser tab (especially google spreadsheet), factorio, minecraft to fillup my 16GB of memory. As soon i reach 100% of physical apps starts to crash even when having free swap. (8gb of swap, 20gb - no difference, still everything crashes when physical full) min_free_kbytes set to 875840 - but i don't see much difference Anyone have a clue what could be checked? there is no OOM in the journal or dmesg, but i suspect that OS is refusing memory access and it crashes them that would explain the randomness of what crashes. Stacktrace suggest the same? (I would be greatfull if someone read stacktrace and put some suggestion based on it). OS: Arch - up to date plasmashell: 5.11.5 kernel; 4.14.15-1-ARCH The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1c446cd840 (LWP 1095))] Thread 6 (Thread 0x7f1c03deb700 (LWP 6851)): #0 0x7f1c3cf933bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1c4140a00c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c3c15d9ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1c3c15de54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1c41408b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f1c3cf8d08c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1c4407ce7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1c03251700 (LWP 1535)): #0 0x7f1c3cf933bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1c4055df77 in () at /usr/lib/libQt5Script.so.5 #2 0x7f1c4055dfb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f1c3cf8d08c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f1c4407ce7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1c20dc4700 (LWP 1512)): #0 0x7f1c44072a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1c4164d6f3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c4164ee8f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1c415f3d0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1c4140378e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1c3ba5fa19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f1c41408b2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f1c3cf8d08c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1c4407ce7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1c22005700 (LWP 1391)): #0 0x7f1c44072a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1c4164d6f3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c4164ee8f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1c415f3d0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1c4140378e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1c3ba5fa19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f1c41408b2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f1c3cf8d08c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1c4407ce7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1c28916700 (LWP 1245)): #0 0x7f1c44072a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1c4164d6f3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c4164ee8f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1c415f3d0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1c4140378e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1c3abd3416 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f1c41408b2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f1c3cf8d08c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1c4407ce7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1c446cd840 (LWP 1095)): [KCrash Handler] #5 0x7f1bfc00 in () #6 0x7f1c404a3b99 in () at /usr/lib/libQt5Script.so.5 #7 0x7f1c408472b8 in __bss_start ()
[kactivitymanagerd] [Bug 389128] When full physical memory - Process (kactivitymanage) of user 1000 dumped core.
https://bugs.kde.org/show_bug.cgi?id=389128 kolorafa changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from kolorafa --- Short version: Thanks for the tip, going over Xorg to fail a bug report. Long version: Yes, I'm using nvidia proprietary drivers. I was misleaded because the failure doesn't produce any dmesg or journal log. The real culprit was xorg, i did do next test and this time the screen just freezed, i did log into pc using ssh and found this: [178630.668] (EE) [178630.668] (EE) Backtrace: [178630.692] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x55adf3472169] [178630.693] (EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x50) [0x7fceae3d0dff] [178630.694] (EE) 2: /usr/lib/libc.so.6 (_int_malloc+0xb99) [0x7fceae088ef9] [178630.694] (EE) 3: /usr/lib/libc.so.6 (_int_realloc+0x145) [0x7fceae089ab5] [178630.695] (EE) 4: /usr/lib/libc.so.6 (realloc+0x2eb) [0x7fceae08acdb] [178630.695] (EE) 5: /usr/lib/xorg-server/Xorg (ReadRequestFromClient+0x40c) [0x55adf3470efc] [178630.695] (EE) 6: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x305) [0x55adf330c235] [178630.695] (EE) 7: /usr/lib/xorg-server/Xorg (InitFonts+0x420) [0x55adf33102c0] [178630.695] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xea) [0x7fceae028f4a] [178630.695] (EE) 9: /usr/lib/xorg-server/Xorg (_start+0x2a) [0x55adf32f9f2a] [178630.695] (EE) [178630.695] (EE) Segmentation fault at address 0x0 [178630.695] (EE) Fatal server error: [178630.695] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 854.815] (EE) [ 854.815] (EE) Backtrace: [ 854.817] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x558984987169] [ 854.817] (EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x50) [0x7f3a94714dff] [ 854.821] (EE) 2: ? (?+0x50) [0xffcb001a] [ 854.821] (EE) [ 854.821] (EE) Segmentation fault at address 0xffcaffca [ 854.821] (EE) Fatal server error: [ 854.821] (EE) Caught signal 11 (Segmentation fault). Server aborting -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389128] New: When full physical memory - Process (kactivitymanage) of user 1000 dumped core.
https://bugs.kde.org/show_bug.cgi?id=389128 Bug ID: 389128 Summary: When full physical memory - Process (kactivitymanage) of user 1000 dumped core. Product: kactivitymanagerd Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 109949 --> https://bugs.kde.org/attachment.cgi?id=109949&action=edit journalctl It happens every time i reach 100% of my physical ram, the swap is like between 0%-0,5%, there is no OOM in the log, but kactivitymanager crashes and I'm getting logged out. Especially strange as I have 16GB of ram. Nvidia GTX 960, i7-5930K, kernel 4.14.13-1-ARCH, Arch Linux It might be something related to my swap not getting filled much, on one test "on 100%" the heavy-memory-test-app did crash rather than kactivitymanager, but most of the time i'm greeted with black screen and logging screen with the log about kactivitymanagerd coredump.long (I could get more ram ;) but still ... 16GB :/) -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 389121] New: Uncaught TypeError: tagName.toLowerCase is not a function
https://bugs.kde.org/show_bug.cgi?id=389121 Bug ID: 389121 Summary: Uncaught TypeError: tagName.toLowerCase is not a function Product: plasma-browser-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: kde_...@dlk.pl Target Milestone: --- Created attachment 109943 --> https://bugs.kde.org/attachment.cgi?id=109943&action=edit code snippet Control panel (probably buggy) breaks when plasma-browser-integration is enabled. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl --- Comment #2 from kolorafa --- Same here, i did put a vault on dropbox and just wanted to open it on second pc and i don't see any option, and by trying creating vault from scratch it crashed/window disapeared at finish. But for now you need to copy the plasmavaultrc or mount manually (depending on encryption type): cryfs /path/to/encrypted/dir /path/to/mount encfs /path/to/encrypted/dir /path/to/mount -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384236] New: plasmashell crash (and restart)
https://bugs.kde.org/show_bug.cgi?id=384236 Bug ID: 384236 Summary: plasmashell crash (and restart) Product: plasmashell Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.6-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Moving window, probably window jumped from one screen to second and back. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4739216c80 (LWP 2421))] Thread 27 (Thread 0x7f45f2ffd700 (LWP 11069)): #0 0x7f47320781ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4732eac5ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f46731fc3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f46732012b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #26 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #27 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #28 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #29 0x7f46731feb6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #30 0x7f4732eab15b in () at /usr/lib/libQt5Core.so.5 #31 0x7f4732072049 in start_thread () at /usr/lib/libpthread.so.0 #32 0x7f47327bef0f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f45f37fe700 (LWP 11068)): #0 0x7f47320781ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4732eac5ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f46731fc3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f46732012b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f4673201312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f46731fb913 in ThreadWeaver::Weaver::applyForWork(Threa
[plasmashell] [Bug 382496] New: Plasma crash&restart after closing "Event Calendar" widget settings.
https://bugs.kde.org/show_bug.cgi?id=382496 Bug ID: 382496 Summary: Plasma crash&restart after closing "Event Calendar" widget settings. Product: plasmashell Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.11.9-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Open "Event calendar" widget settings, change something, save, and close by hitting OK. After closing window plasma crashes/restarts every time. Plasma on Arch (Antergos), not tested on a clean install. https://youtu.be/T4kJeksgZUY -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa728e6dd80 (LWP 918))] Thread 26 (Thread 0x7fa5bbbff700 (LWP 5892)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fa5de7fd700 (LWP 4899)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fa5df7fe700 (LWP 4680)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fa5d700 (LWP 4679)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fa5f0de9700 (LWP 4592)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fa5f2def700 (LWP 4586)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fa6020fc700 (LWP 3405)): #0 0x7fa721d7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa722bb15ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fa72696bae8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fa72696bf4a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa722bb015b in () at /usr/lib/libQt5Core.so.5 #5 0x7fa721d77049 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa7224c3f0f
[konsole] [Bug 188528] konsole's history adds spaces to end of lines when copying text
https://bugs.kde.org/show_bug.cgi?id=188528 --- Comment #164 from kolorafa --- I just struggling with the same problem, Konsole is adding extra spaces where there is non to begin with. It's just annoying that i copy/paste text from one file to another on server using Konsole and i need to remove spaces. Selecting "Cut spaces on end" didn't help -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 188528] konsole's history adds spaces to end of lines when copying text
https://bugs.kde.org/show_bug.cgi?id=188528 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379191] New: PlasmaShell disapeared and reappeared after few seconds - only once
https://bugs.kde.org/show_bug.cgi?id=379191 Bug ID: 379191 Summary: PlasmaShell disapeared and reappeared after few seconds - only once Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_...@dlk.pl CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: just plainly switching to next song by shortcut, but i don't think thats related, it was first crash, -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f780cefe800 (LWP 1322))] Thread 27 (Thread 0x7f76f1896700 (LWP 30011)): #0 0x7f78013f2e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f78013acc99 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f78013ad6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f78013ad8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7806eee06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7806e9789a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7806cb9a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7806cbe6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f7805b732e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f78065d154f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f36d75f7700 (LWP 8962)): #0 0x7f78065c767d in poll () at /usr/lib/libc.so.6 #1 0x7f77fb1bbee1 in () at /usr/lib/libpulse.so.0 #2 0x7f77fb1ad6f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f77fb1add8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f77fb1ade40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f77fb1bbe29 in () at /usr/lib/libpulse.so.0 #6 0x7f77fab4bfe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7f7805b732e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f78065d154f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f76f0a77700 (LWP 8961)): #0 0x7f7806eed4ed in () at /usr/lib/libQt5Core.so.5 #1 0x7f78013acc8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f78013ad6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f78013ad8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7806eee06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7806e9789a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7806cb9a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7809df1025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f7806cbe6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7805b732e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f78065d154f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f76f27fc700 (LWP 4670)): #0 0x7f7805b79756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7806cbf58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f77545d61d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f77545da9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f77545daa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f77545d5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f77545daa32 in
[ksmserver] [Bug 378551] New: ksmserver - high memory usage - 1,9GB for ksmserver
https://bugs.kde.org/show_bug.cgi?id=378551 Bug ID: 378551 Summary: ksmserver - high memory usage - 1,9GB for ksmserver Product: ksmserver Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- 1,891GB for ksmserver. Overall it's not a problem, and i will update this box in few days, but I'm curious about what could be the cause of this. Maybe it's related that i use caffeine manually set to disable screen lockdown. This pc for some time now only shows and records camera feeds from home, it has 12G of ram as it was my previous workstation, but totally wasting it :D The problem doesn't occure on my new workstation with plasma 5.9.4, but maybe someone have a few teories why could be the reason :) Keep up the great work! GiB RAM : 40,3/11,738 GiB Swap: 0,0/0,000 PID UŻYTK. PR NIWIRTREZ %CPU %PAM CZAS+ S KOMENDA 1056 kolorafa 20 0 2614,2m 1,891g 0,0 16,1 4:44.34 S ksmserver 1068 kolorafa 20 0 0,255t 522,0m 3,3 4,3 558:09.90 R plasmashell 1178 kolorafa 20 0 3044,1m 220,3m 0,0 1,8 13:03.16 S dropbox 407 root 20 0 1849,8m 169,6m 59,6 1,4 5265:45 S xeoma 25151 kolorafa 20 0 279,3m 157,1m 0,0 1,3 24:34.39 S synergyc 1063 kolorafa 20 0 3208,9m 151,6m 7,9 1,3 586:43.72 R kwin_x11 24201 kolorafa 20 0 622,4m 150,1m 47,0 1,2 4044:14 S xeoma -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 376346] Can't restart OS from menu.
https://bugs.kde.org/show_bug.cgi?id=376346 --- Comment #1 from kolorafa --- In the log i see: lut 11 12:55:43 kolorafa-newarch ksmserver[920]: ksmserver: Client "./ts3client_linux_amd64" ( 1016b1b019a1af00014866762820009200020 ) canceled shutdown. But after third time, even when i shutdown this app, it still doesn't restart. It did continue the reboot after manually shutting down all apps, but it didn't show info about apps that prevents reboot... :( -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 376346] New: Can't restart OS from menu.
https://bugs.kde.org/show_bug.cgi?id=376346 Bug ID: 376346 Summary: Can't restart OS from menu. Product: ksmserver Version: 5.9.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ui Assignee: l.lu...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- Created attachment 103977 --> https://bugs.kde.org/attachment.cgi?id=103977&action=edit journal Can't normally restart OS, need to type "reboot" from console 75% times (if you have apps running). After clicking "reboot" from menu, you see the countdown, you click reboot and ... nothing. Second time after clicking "reboot", you see the countdown, you click reboot and ... nothing. Third and every time from now, you click "reboot" and see nothing. the only thing that shows in any logs that i know is: lut 11 13:01:26 kolorafa-newarch ksmserver[920]: ksmserver: Shutdown called with confirm -1 type 1 and mode -1 But nothing happens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376235] Different width (shrinked) with grouping without popups
https://bugs.kde.org/show_bug.cgi?id=376235 --- Comment #4 from kolorafa --- Created attachment 103924 --> https://bugs.kde.org/attachment.cgi?id=103924&action=edit width fix. Somehow it is exactly oposite, for me if i have one chrome open first, terminal second, and then i will open second chrome, i want chrome to get after the first chrome so in between chrome and terminal. You probably will say than you can order Alphabetically, then no, because if I open NEW window, it often gets before the previous one. (example, i have "Terminal <9>" and i will open next one then "Terminal <10>" gets before 9... I don't like (even hate) this popup groups, but i ... LOVE the grouping, so whenever i open new X it will be placed behind X on the task list. And if I do it like on "bad width" screenshot, i get the ability to REORDER the gorups, still having them to group togheter, Yes, i know, it's like f... W10. The problem is i HATE W10 but i like their grouping behavior. And i love Linux & Plasma it's f... awesome! So for anyone else that want to have the same size here is the patch. Simple comment-out line "return preferredMinWidth();" in function preferredMaxWidth() in file /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/code/layout.js -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376235] Different width (shrinked) with grouping without popups
https://bugs.kde.org/show_bug.cgi?id=376235 --- Comment #2 from kolorafa --- Created attachment 103920 --> https://bugs.kde.org/attachment.cgi?id=103920&action=edit Good width -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376235] Different width (shrinked) with grouping without popups
https://bugs.kde.org/show_bug.cgi?id=376235 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl --- Comment #1 from kolorafa --- Created attachment 103919 --> https://bugs.kde.org/attachment.cgi?id=103919&action=edit Bad width (to short) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376235] New: Different width (shrinked) with grouping without popups
https://bugs.kde.org/show_bug.cgi?id=376235 Bug ID: 376235 Summary: Different width (shrinked) with grouping without popups Product: plasmashell Version: 5.9.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: 1.0 When you select to "Grouping By Program Name" but do not select "Open groups in popups" then the tile is somehow shorter even when there is a lof of space empty. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376234] New: Window preview on hover + Middle click (close) = all window transparent
https://bugs.kde.org/show_bug.cgi?id=376234 Bug ID: 376234 Summary: Window preview on hover + Middle click (close) = all window transparent Product: plasmashell Version: 5.9.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kde_...@dlk.pl CC: plasma-b...@kde.org Target Milestone: 1.0 When you set your Task manager to highlight window on hover and then middle click to close that window it will get stuck with all windows transparent until you hover your mouse once more. So using hover to highlight and middle to close is pain. The same behavior on 5.8.5-5.9.1. Easiest way to test it is to middle click (close) last window on task list. It would be nice to fix this :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process
https://bugs.kde.org/show_bug.cgi?id=371889 kolorafa changed: What|Removed |Added CC||kde_...@dlk.pl --- Comment #19 from kolorafa --- USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND kolorafa 27275 15.5 37.8 282921676 6176060 ? Sl sty03 1879:08 \_ /usr/bin/plasmashell --shut-up I have the exact same thing (100% cpu when tray icon change/blinks). If you have any blinking icon in systray over a time it uses more and more cpu and after few hours it is like 100% cpu for every icon switch. And aditionally after 23 days of system uptime with blinking icons i opened huge page in crome, normally only chrome would freeze for some time because of cpu, but the whole plasma did freeze and started to behave crazy ... I opened the shell and saw 100% MEM (16G) and swap (4G) I did kill chrome and now i see that plasmashell still uses 6GB of ram (RSS). If that would help i could try some profiling because on my 8G laptop that i use the same way i need to reboot my box just to get plasmashell use less memory after 24h. -- You are receiving this mail because: You are watching all bug changes.
kde-bugs-dist@kde.org
https://bugs.kde.org/show_bug.cgi?id=373637 Bug ID: 373637 Summary: seg fault&restart Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kde_...@dlk.pl Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.36-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: right after login - starting desktop in the morning - Unusual behavior I noticed: slow to load - have fast cpu but slow spinning disk and network, cpu, memory and directory list widget on desktop -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbfd1da1840 (LWP 1167))] Thread 6 (Thread 0x7fbf9f7fe700 (LWP 1455)): #0 0x7fbfcaa8510f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbfcdddbac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fbfcdddbb09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fbfcaa7f454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fbfd17f17df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fbfa5e2f700 (LWP 1267)): [KCrash Handler] #6 0x7fbfcedd92d2 in () at /usr/lib/libQt5Core.so.5 #7 0x7fbfced76856 in QLockFile::tryLock(int) () at /usr/lib/libQt5Core.so.5 #8 0x7fbfd0b7f2d9 in () at /usr/lib/libKF5ConfigCore.so.5 #9 0x7fbfd0b632b0 in KConfig::sync() () at /usr/lib/libKF5ConfigCore.so.5 #10 0x7fbfb4ec2df5 in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #11 0x7fbfcee719ce in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7fbfcee7e6d8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7fbfcee72473 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7fbfcfb25e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7fbfcfb2d581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7fbfcee45de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7fbfcee996ae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #18 0x7fbfcee97618 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7fbfcee4423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7fbfcec670f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #21 0x7fbfcec6bd78 in () at /usr/lib/libQt5Core.so.5 #22 0x7fbfcaa7f454 in start_thread () at /usr/lib/libpthread.so.0 #23 0x7fbfd17f17df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fbfa7b09700 (LWP 1218)): #0 0x7fbfd17e8551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fbfcee95ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fbfcee973b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fbfcee4423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fbfcec670f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fbfc97dd2d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fbfcec6bd78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fbfcaa7f454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fbfd17f17df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fbfb58e3700 (LWP 1187)): #0 0x7fbfd17e8551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fbfcee95ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fbfcee973b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fbfcee4423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fbfcec670f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fbfc89a7e55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fbfcec6bd78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fbfcaa7f454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fbfd17f17df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fbfb784b700 (LWP 1183)): #0 0x7fbfd17e848d in poll () at /usr/lib/libc.so.6 #1 0x7fbfd09288e0 in () at /usr/lib/libxcb.so.1 #2 0x7fbfd092a679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fbfb82f7449 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fbfcec6bd78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fbfcaa7f454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fbfd17f17df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fbfd1da1840 (LWP 1167)):
