[systemsettings] [Bug 486722] Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 --- Comment #9 from Aleksey Kladov --- Is there any workaround here? For the past few weeks, my daily routine now includes "go to settings and remove dolphin", as Meta+E conflicts with one of my personal shortcut :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486722] Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 --- Comment #7 from Aleksey Kladov --- >Does the same issue appear if you try with a new user? Yes, it does reproduce for a fresh user. I also use the same nixos config on two different machines, and they both have the issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486722] Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 --- Comment #6 from Aleksey Kladov --- > presume you're clicking on the trashcan icon No, I uncheck the checkbox. See the new screenshots for the repro >I cannot reproduce. Which distribution are you using? NixOS, with this config specifically https://github.com/matklad/config/blob/30c657cfbb59b9f0266a38ff78535d39b726172e/flake.nix -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486722] Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 --- Comment #5 from Aleksey Kladov --- Created attachment 169306 --> https://bugs.kde.org/attachment.cgi?id=169306=edit repro step 3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486722] Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 --- Comment #4 from Aleksey Kladov --- Created attachment 169305 --> https://bugs.kde.org/attachment.cgi?id=169305=edit repro setp 2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486722] Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 --- Comment #3 from Aleksey Kladov --- Created attachment 169304 --> https://bugs.kde.org/attachment.cgi?id=169304=edit repro step 1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486722] New: Can't remove Meta+E shortcut for dolphin
https://bugs.kde.org/show_bug.cgi?id=486722 Bug ID: 486722 Summary: Can't remove Meta+E shortcut for dolphin Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aleksey.kla...@gmail.com Target Milestone: --- Created attachment 169267 --> https://bugs.kde.org/attachment.cgi?id=169267=edit screenshot If I remove Meta+E global shortcut for dolphin in settings, then, after reboot, it is back, and there are two dolphins present in the settings. ``` λ plasmashell -v plasmashell 6.0.4 ``` -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 484864] New: drkonqi-coredump-pickup.service breaks logging out during pre-start
https://bugs.kde.org/show_bug.cgi?id=484864 Bug ID: 484864 Summary: drkonqi-coredump-pickup.service breaks logging out during pre-start Classification: Applications Product: drkonqi Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hxk...@gmail.com Target Milestone: --- Created attachment 168012 --> https://bugs.kde.org/attachment.cgi?id=168012=edit System log immediately after trying to log out SUMMARY drkonqi-coredump-pickup.service has a line 'ExecStartPre=/usr/bin/sleep 60'. Trying to log out while that sleep command is running will fail to log out and leave the system in the semi-broken state. STEPS TO REPRODUCE 1. Try to log out during 60 seconds after logging in OBSERVED RESULT Logging out fails, can't log out/shutdown/reboot/etc from plasma anymore, probably something else EXPECTED RESULT Logging out works SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION See attached log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483929] There is no smooth scrolling to the value of 6.
https://bugs.kde.org/show_bug.cgi?id=483929 Aleksey Samoilov changed: What|Removed |Added CC||samoilov@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483128] vertical floating panel bleeds into adjacent monitor when window maximized.
https://bugs.kde.org/show_bug.cgi?id=483128 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #3 from Aleksey Zagorodnikov --- Created attachment 166905 --> https://bugs.kde.org/attachment.cgi?id=166905=edit Horizontal panel bleeds on second monitor Hi, I assume there is the same problem with my panels' arrangement. Maximized or not - it doesn't matter. Floating or fixed too. If I have a vertical panel on the left, then the horizontal panel on top or bottom will shift to another monitor. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470549] Error while communicating with the global shortcuts service
https://bugs.kde.org/show_bug.cgi?id=470549 Aleksey Randay changed: What|Removed |Added CC||fffggg5...@gmail.com --- Comment #8 from Aleksey Randay --- Hi there. The problem is in ~/.config/kglobalshortcutsrc. More precisely, most likely wine (I assume) added a shortcut to the code, and after deleting wine, it did not delete the shortcut, which is why the plasma-kglobalaccel.service service broke(Or the user simply incorrectly added opening the application via shortcut, which is why everything broke). This service complains about invalid path "/component/_windows_sample_application_desktop" and invalid path "/component/wine_Programs_windows_sample_application_desktop", so you need to open ~/.config/kglobalshortcutsrc and delete any lines associated with _windows_sample_application_desktop and wine_Programs_windows_sample_application_desktop. It's also worth checking ~/.local/share/applications. Good luck -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478278] The overview effect is applied to the session management window
https://bugs.kde.org/show_bug.cgi?id=478278 --- Comment #1 from Aleksey Samoilov --- Created attachment 164020 --> https://bugs.kde.org/attachment.cgi?id=164020=edit record of issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478278] New: The overview effect is applied to the session management window
https://bugs.kde.org/show_bug.cgi?id=478278 Bug ID: 478278 Summary: The overview effect is applied to the session management window Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: samoilov@gmail.com Target Milestone: 1.0 SUMMARY *** After clicking on the button to exit the session and activating the overview mode (for example, through the active corner), the session management menu turns into a regular window and goes into overview mode (see attached video) *** STEPS TO REPRODUCE 1. Click on logout/reboot/shutdown button from kickoff menu to call session management menu 2. Activate overview effect (using top left active corner or Meta+W) OBSERVED RESULT Session management menu goes to overview mode as a regular window EXPECTED RESULT If session management menu is active, any effects (e.g. overview effect) should be inhibited SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Unstable (available in About System) KDE Plasma Version: 5.27.90 KDE Frameworks Version: 5.245 Qt Version: 6.6.0 ADDITIONAL INFORMATION Also affected Plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469275] Non-removable volumes shown as removable volumes
https://bugs.kde.org/show_bug.cgi?id=469275 --- Comment #5 from Aleksey Kontsevich --- Yes, I bought new MB, bug started after that, so https://bugzilla.kernel.org/show_bug.cgi?id=111651#c3 helped: >Disabling the hotplug functionality in the bios make the drives appears as non >removable anymore -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469275] Non-removable volumes shown as removable volumes
https://bugs.kde.org/show_bug.cgi?id=469275 --- Comment #3 from Aleksey Kontsevich --- Created attachment 160452 --> https://bugs.kde.org/attachment.cgi?id=160452=edit udisksctl.log udisksctl dump attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469275] Non-removable volumes shown as removable volumes
https://bugs.kde.org/show_bug.cgi?id=469275 Aleksey Kontsevich changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Aleksey Kontsevich --- Any chance to fix this?! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470134] New: Emoji Selector could be useful for selecting latex symbols
https://bugs.kde.org/show_bug.cgi?id=470134 Bug ID: 470134 Summary: Emoji Selector could be useful for selecting latex symbols Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: aleksey.kla...@gmail.com Target Milestone: 1.0 In addition to emojies, I often want to copy-paste math symbols (\cap, \cup, \infty, etc). Emoji Selector would be a perfect UI for me to do that. To not clutter the emoji list itself, latex symbols can be suggested only when the query string starts with `\`. I think I can use `kcharselect` for a similar purpose, but this solution has the following shortcomings: - i'd need separate shortcuts for "launch emojier" and "launch kcharselect", although I think about both as "I want some unicode symbol" - kcharselect UI is clunky - kcharselect doesn't actually support latex aliases I guess this wish can be split into two: - extend emojier into general "pick unicode symbols by names" functionality - add latex aliases for math symbols -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469868] Dolphin does not restore its state on KDe start
https://bugs.kde.org/show_bug.cgi?id=469868 --- Comment #2 from Aleksey Kontsevich --- *** This bug has been marked as a duplicate of bug 470050 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470050] Dolphin does not restore folders when opened through session restore
https://bugs.kde.org/show_bug.cgi?id=470050 --- Comment #3 from Aleksey Kontsevich --- *** Bug 469868 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470050] Dolphin does not restore folders when opened through session restore
https://bugs.kde.org/show_bug.cgi?id=470050 Aleksey Kontsevich changed: What|Removed |Added CC||akontsev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 --- Comment #26 from Aleksey Kontsevich --- (In reply to Eduardo from comment #25) > (In reply to Bug Janitor Service from comment #23) > > A possibly relevant merge request was started @ > > https://invent.kde.org/system/dolphin/-/merge_requests/549 > > Thank you, this looks good. > At least dolphin now remembers closed tabs from last time. I have not tested > session restore, but I will only do it when I actually can log out and back > in. Very good! When it will be available in openSUSE Tumbleweed? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469868] New: Dolphin does not restore its state on KDe start
https://bugs.kde.org/show_bug.cgi?id=469868 Bug ID: 469868 Summary: Dolphin does not restore its state on KDe start Classification: Applications Product: dolphin Version: 23.04.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: akontsev...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin does not restore its state on KDe start (session recovery) OBSERVED RESULT I had 3 Dolphin windows with many tabs, they always restored on KDe start for years. Now I have 3 windows with 1 tab in each with HOME dir in them. "Show on startup" settings is set to the state from last time - has no effect at all now! When bug was 1st observed "Show on startup" was dropped to HOME dir for some reason - so assume 2 bugs are here. EXPECTED RESULT Many windows with many tabs with same paths on KDe start. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230515 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-2-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469275] New: Disks & Devices applet always shows all the partitions
https://bugs.kde.org/show_bug.cgi?id=469275 Bug ID: 469275 Summary: Disks & Devices applet always shows all the partitions Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: akontsev...@gmail.com Target Milestone: 1.0 SUMMARY Disks & Devices applet always shows all the available partitions for me if I select "Show only removable media". If I select "Show non-removable media" - it shows nothing. "Show all" - shows all like in the 1st variant. Systemsettings app shows external devices correctly - only removable media. OBSERVED RESULT Disks & Devices applet shows all disks including removable media (USB), SSD and HDD EXPECTED RESULT Disks & Devices applet should show only removable media (USB). SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230501 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 468440] Global Application shortcuts are slower than they could be
https://bugs.kde.org/show_bug.cgi?id=468440 --- Comment #2 from Aleksey Kladov --- >could help here since it cuts out an intermediate helper process Aha, I think this helper process would explain 100% of the slowness I observe. On my system, spawning any plasma-related processes is very slow: ``` $ t kstart -h real 339.00ms cpu 171.86ms (127.87ms user + 43.99ms sys) rss 94.29mb ``` I fixed that dowstream (https://github.com/NixOS/nixpkgs/issues/225871), so I think it's fair to say that there's no "global shortcuts are slow" bug in plasma after all. Still, getting rid of an intermediate process feels like a good idea regardless! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468846] Konsole crashes when external monitor (with connected keyboard and mouse) goes to sleep mode
https://bugs.kde.org/show_bug.cgi?id=468846 --- Comment #3 from Aleksey Maximov --- still crashing... no ideas why and how to fix it. Message: Process 3344 (konsole) of user 1000 dumped core. Stack trace of thread 3344: #0 0x7ffa9a32f0a8 _ZNK15QPlatformScreen6screenEv (libQt5Gui.so.5 + 0x12f0a8) #1 0x7ffa98057c51 _ZN15QtWaylandClient14QWaylandWindow20handleScreensChangedEv (libQt5WaylandClient.so.5 + 0x81c51) #2 0x7ffa99ebea71 n/a (libQt5Core.so.5 + 0x2bea71) #3 0x7ffa953b04f6 n/a (libffi.so.8 + 0x74f6) #4 0x7ffa953acf5e n/a (libffi.so.8 + 0x3f5e) #5 0x7ffa953afb73 ffi_call (libffi.so.8 + 0x6b73) #6 0x7ffa9873e645 n/a (libwayland-client.so.0 + 0x7645) #7 0x7ffa9873ee73 n/a (libwayland-client.so.0 + 0x7e73) #8 0x7ffa9873f13c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x813c) #9 0x7ffa98048c06 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x72c06) #10 0x7ffa99ebec20 n/a (libQt5Core.so.5 + 0x2bec20) #11 0x7ffa99ed8ca7 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8ca7) #12 0x7ffa99e866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #13 0x7ffa99e91219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #14 0x55d36253db65 _Z13fillAboutDataR10KAboutData (/usr/bin/konsole (deleted) + 0x5b65) #15 0x7ffa99f76e90 n/a (libQt5Core.so.5 + 0x376e90) ELF object binary architecture: AMD x86-64 lines 1986-2054/2054 (END) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468846] Konsole crashes when external monitor (with connected keyboard and mouse) goes to sleep mode
https://bugs.kde.org/show_bug.cgi?id=468846 --- Comment #2 from Aleksey Maximov --- recompiled package pkgname=qt5-wayland pkgver=5.15.9+kde+r55 _commit=c4c3fc69250c01cb35aaae5ea1ea2bcc8236dff0 with export CFLAGS="-O0 -ggdb -DDEBUG" export CXXFLAGS="-O0 -ggdb -DDEBUG" no more bugs and crashes... ;-| so, extra/qt5-wayland 5.15.8+kde+r63-1 really have bugs. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468846] Konsole crashes when external monitor (with connected keyboard and mouse) goes to sleep mode
https://bugs.kde.org/show_bug.cgi?id=468846 --- Comment #1 from Aleksey Maximov --- recompiled Konsole , 1 min timer to Screen Energy Saving (on AC) got trace. [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/konsole'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0023 in ?? () [Current thread is 1 (Thread 0x7f744dc06400 (LWP 162639))] (gdb) bt #0 0x0023 in ?? () #1 0x7f745105722a in QtWaylandClient::QWaylandWindow::handleScreensChanged() () from /usr/lib/libQt5WaylandClient.so.5 #2 0x7f7452ebea71 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f744e3c64f6 in ?? () from /usr/lib/libffi.so.8 #4 0x7f744e3c2f5e in ?? () from /usr/lib/libffi.so.8 #5 0x7f744e3c5b73 in ffi_call () from /usr/lib/libffi.so.8 #6 0x7f7451754645 in ?? () from /usr/lib/libwayland-client.so.0 #7 0x7f7451754e73 in ?? () from /usr/lib/libwayland-client.so.0 #8 0x7f745175513c in wl_display_dispatch_queue_pending () from /usr/lib/libwayland-client.so.0 #9 0x7f7451048bf6 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib/libQt5WaylandClient.so.5 #10 0x7f7452eb1bb0 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #11 0x7f7453b78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7f7452e8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7f7452e8ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #14 0x7f7452ed4e88 in ?? () from /usr/lib/libQt5Core.so.5 #15 0x7f745123f53b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x7f745129c219 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0x7f745123e1a2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0x7f7452ed8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #19 0x7f7452e866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #20 0x7f7452e91219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #21 0x557af0634af1 in main (argc=1, argv=0x7ffe98025338) at /home/amaxcz/src/xx1/konsole/repos/extra-x86_64/src/konsole-22.12.3/src/main.cpp:252 (gdb) i r rax0x557af2d3be50 93986548334160 rbx0x557af2331570 93986537805168 rcx0x0 0 rdx0x0 0 rsi0x7ffe98024640 140731448706624 rdi0x557af2a28540 93986545108288 rbp0x557af2a28540 0x557af2a28540 rsp0x7ffe98024688 0x7ffe98024688 r8 0x0 0 r9 0x1 1 r100x7f74400047f8 140137266694136 r110x293 659 r120x7f745103cdd0 140137552137680 r130x557af2331580 93986537805184 r140x0 0 r150x557af22cf020 93986537402400 rip0x230x23 eflags 0x10293 [ CF AF SF IF RF ] cs 0x3351 ss 0x2b43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468846] New: Konsole crashes when external monitor (with connected keyboard and mouse) goes to sleep mode
https://bugs.kde.org/show_bug.cgi?id=468846 Bug ID: 468846 Summary: Konsole crashes when external monitor (with connected keyboard and mouse) goes to sleep mode Classification: Applications Product: konsole Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ama...@gmail.com Target Milestone: --- SUMMARY *** Message: Process 103623 (konsole) of user 1000 dumped core. Stack trace of thread 103623: #0 0x7ff62a12f0a8 _ZNK15QPlatformScreen6screenEv (libQt5Gui.so.5 + 0x12f0a8) #1 0x7ff627eb60f1 _ZN15QtWaylandClient14QWaylandWindow20handleScreensChangedEv (libQt5WaylandClient.so.5 + 0x810f1) #2 0x7ff629cbea71 n/a (libQt5Core.so.5 + 0x2bea71) #3 0x7ff6251f84f6 n/a (libffi.so.8 + 0x74f6) #4 0x7ff6251f4f5e n/a (libffi.so.8 + 0x3f5e) #5 0x7ff6251f7b73 ffi_call (libffi.so.8 + 0x6b73) #6 0x7ff62853c645 n/a (libwayland-client.so.0 + 0x7645) #7 0x7ff62853ce73 n/a (libwayland-client.so.0 + 0x7e73) #8 0x7ff62853d13c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x813c) #9 0x7ff627ea7bf6 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x72bf6) #10 0x7ff629cbec20 n/a (libQt5Core.so.5 + 0x2bec20) #11 0x7ff629cd8ca7 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8ca7) #12 0x7ff629c866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #13 0x7ff629c91219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #14 0x556502212b65 n/a (konsole + 0x5b65) #15 0x7ff62943c790 n/a (libc.so.6 + 0x23790) #16 0x7ff62943c84a __libc_start_main (libc.so.6 + 0x2384a) #17 0x556502213425 n/a (konsole + 0x6425) Stack trace of thread 103625: #0 0x7ff62949b766 n/a (libc.so.6 + 0x82766) #1 0x7ff62949df90 pthread_cond_wait (libc.so.6 + 0x84f90) #2 0x7ff629aeb7c4 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xeb7c4) #3 0x7ff627ea7cc4 n/a (libQt5WaylandClient.so.5 + 0x72cc4) #4 0x7ff629ae432a n/a (libQt5Core.so.5 + 0xe432a) #5 0x7ff62949ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x7ff629520d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 103626: #0 0x7ff6295139df __poll (libc.so.6 + 0xfa9df) #1 0x7ff627ea7d1d n/a (libQt5WaylandClient.so.5 + 0x72d1d) #2 0x7ff629ae432a n/a (libQt5Core.so.5 + 0xe432a) #3 0x7ff62949ebb5 n/a (libc.so.6 + 0x85bb5) #4 0x7ff629520d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 103627: #0 0x7ff62949b766 n/a (libc.so.6 + 0x82766) #1 0x7ff62949df90 pthread_cond_wait (libc.so.6 + 0x84f90) #2 0x7ff61a0c254c n/a (iris_dri.so + 0xc254c) #3 0x7ff61a10b96c n/a (iris_dri.so + 0x10b96c) #4 0x7ff62949ebb5 n/a (libc.so.6 + 0x85bb5) #5 0x7ff629520d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 103629: #0 0x7ff62949b766 n/a (libc.so.6 + 0x82766) #1 0x7ff62949df90 pthread_cond_wait (libc.so.6 + 0x84f90) #2 0x7ff61a0c254c n/a (iris_dri.so + 0xc254c) #3 0x7ff61a10b96c n/a (iris_dri.so + 0x10b96c) #4 0x7ff62949ebb5 n/a (libc.so.6 + 0x85bb5) #5 0x7ff629520d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 103630: #0 0x7ff62949b766 n/a (libc.so.6 + 0x82766) #1 0x7ff62949df90 pthread_cond_wait (libc.so.6 + 0x84f90) #2 0x7ff61a0c254c n/a (iris_dri.so + 0xc254c) #3 0x7ff61a10b96c n/a (iris_dri.so + 0x10b96c) #4 0x7ff62949ebb5 n/a (libc.so.6 + 0x85bb5) #5 0x7ff629520d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 103624: #0 0x7ff6295139df __poll (libc.so.6 + 0xfa9df) #1 0x7ff62816c17f n/a (libglib-2.0.so.0 + 0xb717f) #2 0x7ff62810e1a2 g_main_context_iteration (libglib-2.0.so.0 + 0x591a2) #3 0x7ff629cd8c6c
[ksmserver] [Bug 468704] Session menu stops working after using nested Wayland compositor
https://bugs.kde.org/show_bug.cgi?id=468704 --- Comment #1 from Aleksey Samoilov --- This is messages after launching nested Sway: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) 00:00:00.054 [wlr] [types/wlr_drm_lease_v1.c:705] No DRM backend supplied, failed to create wlr_drm_lease_v1_manager 00:00:00.072 [wlr] [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use 2023-04-20 10:56:47 - [main.c:293] Found config * for output WL-1 ((null)) 00:00:00.026 [swaybar/tray/host.c:24] Registering Status Notifier Item ':1.43/StatusNotifierItem' 00:00:00.026 [swaybar/tray/host.c:24] Registering Status Notifier Item ':1.61/StatusNotifierItem' -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 468704] New: Session menu stops working after using nested Wayland compositor
https://bugs.kde.org/show_bug.cgi?id=468704 Bug ID: 468704 Summary: Session menu stops working after using nested Wayland compositor Classification: Plasma Product: ksmserver Version: 5.27.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: samoilov@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** After launch Sway as a nested Wayland compositor in Plasma Wayland session, I can no longer use session menu. Nor "Logout', nor "Reboot", doesn't work. For example, I press the "Shutdown" button - and nothing happens. Same result if running Sway in Plasma X11 session. *** STEPS TO REPRODUCE 1. Check that session menu (logiut, reboot, etc) is work; 2. Run Sway with 'sway -c /etc/sway/config' command; 3. Close Sway and try to logout or reboot system with session menu OBSERVED RESULT Session menu doesn't work EXPECTED RESULT Session menu should appear as usual (fullscreen menu with options to logout, reboot, shutdown, etc) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian Bookworm (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #13 from Aleksey Kladov --- Also confirm that with * NixOS [patch](https://github.com/NixOS/nixpkgs/pull/225881) applied * emojier [patch](https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1469) applied * and using task manager shortcut, rather than M+. plasma-emojier finally feels snappy enough for me! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #12 from Aleksey Kladov --- > If you run `plasma-emojier` in a terminal window, is it significantly faster > to launch, or about the same? > It’s slow either way, and other global shortcuts are pretty snappy Spoke too soon @nate! After testing this patch, I found out that global shortcuts are also slow (global _application_ shortcut adds an extra 100ms delay in comparison to launching taskbar entry with the same shortcut). See https://bugs.kde.org/show_bug.cgi?id=468440 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468440] New: Global Application shortcuts are slower than they could be
https://bugs.kde.org/show_bug.cgi?id=468440 Bug ID: 468440 Summary: Global Application shortcuts are slower than they could be Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aleksey.kla...@gmail.com Target Milestone: --- SUMMARY Global Application shortcuts (like `M+.` for emojier) add about 100ms delay in comparison to pinning the app in taskbar and using `Win+number` shortcut. That is, launching emojier with `M+.` is noticeably slower for me than pinning it and launching a new instance via `Win+1` STEPS TO REPRODUCE The delay is visible with a nacked eye, especially if you compare two kinds of shortcuts (xclock is a guinea pig). But I also confirmd that with time measurments using these two scripts click.sh logs current time and uses ydotool to send `F4` shortcut ``` #!/bin/sh date +%s.%N >> "/home/matklad/tmp/log.txt" ydotool key 62:1 62:0 ``` clock.sh logs current time ``` #!/bin/sh date +%s.%N >> "/home/matklad/tmp/log.txt" echo "\n" >> "/home/matklad/tmp/log.txt" ``` If I bind F4 to global script shorcturt ``` [clock.sh.desktop] _k_friendly_name=clock.sh _launch=F4,none,/home/matklad/tmp/clock.sh ``` the result looks like this ``` 1681339791.367891270 1681339791.488687436 \n 1681339792.845658459 1681339792.964949291 \n 1681339793.893609292 1681339794.015043447 ``` That's about 120ms of delay between click.sh and clock.sh If I find F4 to task manager ``` activate task manager entry 1 ``` the result looks like this ``` 1681340227.988185176 1681340228.001887438 \n 1681340229.466190483 1681340229.482717773 \n 1681340230.419816890 1681340230.437328642 ``` about 20ms of delay, 100ms faster than the global shortcut SOFTWARE/OS VERSIONS Operating System: NixOS 23.05 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Related issue: https://bugs.kde.org/show_bug.cgi?id=468328 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #7 from Aleksey Kladov --- Taking a further look here, it seems like the slowness was the result of three independent causes: * NiXOS quadratic QT_PLUGIN_PATH manipulation (I've eliminated it by constructing the right path myself) * _Something_ in nvidia driver taking a lot of time to great a GL Context (eliminated that by switching to Intel) * Residual slowness in emojier itself With the first two issues fixed, the perf is improved to the point where it is not outright noticeable sluggish, but still doesn't quite feel instant. Though, at this point it is probably good enough. If anyone wants to poke at it, here's a profile: https://share.firefox.dev/3UqtTKC -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #6 from Aleksey Kladov --- https://discourse.nixos.org/t/plasma-emojier-is-very-slow/27160 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #5 from Aleksey Kladov --- Got symbols: https://share.firefox.dev/401bncW It's pretty curious... Looks like the blame is actually on the NixOS wrapper script, which doesn't look at all reasonable: https://gist.github.com/matklad/a32bd2fc34bdb7edd37947d8d4619b35 I'll ask on nixos discourse what's up with that: * either NixOS is doing something stupid there, * or perhaps there's something lacking with plasma's dynamic linking/search path, which forces Nix to do a poorly perfoming work-aroud -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #4 from Aleksey Kladov --- Here's a firefox profile for `perf record` https://share.firefox.dev/3ZQGasY There's no symbols, but there's something taking 500ms there -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468328] Emoji Selector should be faster to launch
https://bugs.kde.org/show_bug.cgi?id=468328 --- Comment #2 from Aleksey Kladov --- It’s slow either way, and other global shortcuts are pretty snappy -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468328] New: Emoji Selector takes half a second to start
https://bugs.kde.org/show_bug.cgi?id=468328 Bug ID: 468328 Summary: Emoji Selector takes half a second to start Classification: I don't know Product: kde Version: unspecified Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aleksey.kla...@gmail.com Target Milestone: --- Emoji picker (`M-.`, `plasma-emojier`) is slow to start. It takes roughly 500ms between clicking the shortcut/starting the command in terminal, and the GUI window appearing. This is a very noticeable, flow-breaking delay. This is on a rather powerful desktop (i7-12700H, 1920x1080 display) ``` λ plasma-emojier --version plasma.emojier 5.27.4 fish: Job 1, 'plasma-emojier --version' terminated by signal SIGSEGV (Address boundary error) ``` (sefault on version doesn't bother me :0) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup
https://bugs.kde.org/show_bug.cgi?id=466236 Aleksey Kontsevich changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #22 from Aleksey Kontsevich --- (In reply to Fushan Wen from comment #21) > If you clear the clipboard history, will the bug still exist? Cleared, copied some. With 1 record - no. Will check further when have more records. Why does not switch to OpenGL, how to switch? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #20 from Aleksey Kontsevich --- (In reply to Fabian Vogt from comment #19) > I see that plasmashell still uses the software renderer, so the switch to > OpenGL did not work. Another bug? > However, it looks like in both backtraces it's busy in clipboard history > code. In plasma_error_2.txt, it's saving a copied image to disk. What was changed in 5.27 that causes it?! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup
https://bugs.kde.org/show_bug.cgi?id=466236 Aleksey Kontsevich changed: What|Removed |Added Summary|With NVIDIA GPU,|With NVIDIA GPU, |plasmashell crashes in |plasmashell crashes in |QSGSoftwareRenderableNode:: |QSGSoftwareRenderableNode:: |update() when filtering in |update() when filtering in |the Klipper history popup |the Klipper history popup |with Cyrillic keyboard | |layout applied | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #18 from Aleksey Kontsevich --- (In reply to Aleksey Kontsevich from comment #17) > Right after the 1st crash (freeze), 2nd one happened accidentally (did > nothing at that time: browsing in chrome based browser). See Attachment > #157160 [details]. 3rd crash just happened then auto-restarted - so was unable to catch the stack trace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 Aleksey Kontsevich changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #17 from Aleksey Kontsevich --- Right after the 1st crash (freeze), 2nd one happened accidentally (did nothing at that time: browsing in chrome based browser). See Attachment #157160. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #16 from Aleksey Kontsevich --- Created attachment 157160 --> https://bugs.kde.org/attachment.cgi?id=157160=edit plasma_error_2.txt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #15 from Aleksey Kontsevich --- (In reply to Fabian Vogt from comment #13) > If it's frozen (or crashed but somehow hangs instead of restarting), you can > run > > gdb -ex "thread apply all bt" -ex "kill" -ex "q" -p $(pidof plasmashell) That was tricky: Klipper filtering freezes plasma hardly - several CPU completely loaded, no keyboard response, so forced to do this in virtual terminal switching by Ctrl-Alt-F1 and redirect output to a file - see attachment below. See Attachment #157159. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #14 from Aleksey Kontsevich --- Created attachment 157159 --> https://bugs.kde.org/attachment.cgi?id=157159=edit plasma_error.txt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #12 from Aleksey Kontsevich --- > > No, after the crash "kcmshell5 kcm_qtquicksettings" appeared for me so I > > tried any variants: Program, OpenGL, Automatic - all crashes. > > Please switch to OpenGL, when it crashes again attach a backtrace. Already switched, but problem is crash sender UI never appears, while it crashes or freezes all the time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #8 from Aleksey Zagorodnikov --- Before 5.27 it wasn't happening, noticed it right after update. During tests, I've realized that firefox and chrome somehow related to this behavior. When I close their windows - mouse seems to hover smoothly. But instantly laggy after running the browser again. Disabling hover previews doesn't instantly solve the issue, it needs to restart plasmashell, otherwise, it is laggy even without previews. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #6 from Aleksey Zagorodnikov --- Noticed in journal kwin_wayland[1819]: kwin_screencast: Dropping a screencast frame because the compositor is slow And it seems disabling "Show small windows previews when hovering over Tasks" option in Task Manager settings solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #5 from Aleksey Zagorodnikov --- Got the same issue, but it does not consistently reproduce, at least several minutes it works okay after boot, or after plasmashell --replace. I've noticed that video in Firefox stutters too when hovering over the task manager. I enable FPS counter inside firefox and it drops from 120/60 to <30fps when this happens. It reproduces on built-in display and on an external monitor too. My hardware: Operating System: Manjaro Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 38,9 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO Product Name: 21DJ System Version: ThinkBook 15 G4 IAP -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #4 from Aleksey Zagorodnikov --- Created attachment 157080 --> https://bugs.kde.org/attachment.cgi?id=157080=edit firefox drops fps -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #10 from Aleksey Kontsevich --- (In reply to Fabian Vogt from comment #9) > Apparently you use the QML software renderer. That should not be the case, > did you configure that explicitly in kcmshell kcm_qtquicksettings? No, after the crash "kcmshell5 kcm_qtquicksettings" appeared for me so I tried any variants: Program, OpenGL, Automatic - all crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #28 from Aleksey Kontsevich --- (In reply to Fabian Vogt from comment #27) > This bug report is specific to 32bit x86. If you see something on x86_64, > that's a different bug. > > Please do not reopen this bug. Ah sorry, not mine, mine is: https://bugs.kde.org/show_bug.cgi?id=466236 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Aleksey Kontsevich changed: What|Removed |Added Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #26 from Aleksey Kontsevich --- (In reply to Jiri Slaby from comment #25) > (In reply to Jiri Slaby from comment #23) > > Maybe we should continue in downstream (openSUSE miscompilation) or upstream > > (qt bug). > > Resolved downstream by dropping non-sse2 builds of qt libraries (which are > apparently broken), see the downstream bug. > https://bugzilla.suse.com/show_bug.cgi?id=1208188 They said it is a different bug! https://bugzilla.suse.com/show_bug.cgi?id=1208188#c12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 Aleksey Kontsevich changed: What|Removed |Added Version|5.27.0 |5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #8 from Aleksey Kontsevich --- (In reply to Aleksey Kontsevich from comment #0) > Most often this happens when press Klipper hotkey - to show records at mouse > position, type something - to filter records - crash/freeze. Of course it also crashes very often accidentally without any reason as well. Please fix. Same crashes are in 5.27.1 version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #7 from Aleksey Kontsevich --- Crashes also with Latin keyboard, also when browsing in chrome based browser, etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] Plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 Aleksey Kontsevich changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #4) > Just tried that and it didn't happen to me. > > The backtrace indicates that it's deep in graphics code. What kind of GPU do > you have? > inxi -SGa System: Host: Aleksey Kernel: 6.1.12-1-default arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.12-1-default root=UUID=24fbaf81-79f0-4b37-b08e-b1d709ed97e7 splash=silent resume=/dev/disk/by-uuid/a58af199-9a71-4f77-9547-30a7871438e8 mitigations=auto quiet security=apparmor nosimplefb=1 Desktop: KDE Plasma v: 5.27.0 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Tumbleweed 20230221 Graphics: Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: ASUSTeK driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 520.xx+ status: current (as of 2022-10) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 2 speed: 5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:2507 class-ID: 0300 Device-2: Logitech C920 PRO HD Webcam type: USB driver: snd-usb-audio,uvcvideo bus-ID: 5-2:3 chip-ID: 046d:08e5 class-ID: 0102 Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 compositor: kwin_x11 driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa alternate: nouveau,nv gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 192 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95") Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Samsung serial: 16780800 built: 2021 res: 3840x2160 dpi: 103 gamma: 1.2 size: 950x540mm (37.4x21.26") diag: 1093mm (43") ratio: 16:9 modes: max: 3840x2160 min: 640x480 API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2 direct render: Yes >And have you forced Plasma or KWin to use a non-default rendering mode? Tried OpenGl or Automatic - what else? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] Plasmashell constantly crashing and freezing
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #1 from Aleksey Kontsevich --- Created attachment 156600 --> https://bugs.kde.org/attachment.cgi?id=156600=edit plasmashell-20230222-115656.kcrash Backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #18 from Aleksey Kontsevich --- Ha, appeared drkonqi created the bug reports already: - https://bugs.kde.org/show_bug.cgi?id=465962 - https://bugs.kde.org/show_bug.cgi?id=466236 The latter with debug symbols. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465962] Plasmashell freezes and crashes
https://bugs.kde.org/show_bug.cgi?id=465962 Aleksey Kontsevich changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately the backtrace is incomplete and > missing debug symbols for the following lines that we need to figure out > exactly what's going wrong: > > > #5 0x7f7a37effbd7 in ?? () from > > /usr/lib64/qt5/plugins/plasma/applets/org.kde.plasma.private.systemtray.so > > #6 0x7f7a37effe39 in ?? () from > > /usr/lib64/qt5/plugins/plasma/applets/org.kde.plasma.private.systemtray.so > > Could you please install debug symbols for Plasma, reproduce the crash, and > attach a new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Thanks again! This one with debug symbols: https://bugs.kde.org/show_bug.cgi?id=466236 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] New: Plasmashell constantly crashing and freezing
https://bugs.kde.org/show_bug.cgi?id=466236 Bug ID: 466236 Summary: Plasmashell constantly crashing and freezing Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: akontsev...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.0) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: Most often this happens when press Klipper hotkey - to show records at mouse position, type something - to filter records - crash/freeze. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f0220c4a9bc in QSGSoftwareRenderableNode::update (this=this@entry=0x7f0198035330) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenode.cpp:187 #5 0x7f0220c4b247 in QSGSoftwareRenderableNode::setTransform (this=this@entry=0x7f0198035330, transform=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenode.cpp:368 #6 0x7f0220c4f824 in QSGSoftwareRenderableNodeUpdater::updateRenderableNode (this=0x7f020c01e250, type=, node=0x7f0198029280) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenodeupdater_p.h:131 #7 0x7f0220c09175 in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:519 #8 0x7f0220c091db in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:528 #9 0x7f0220c0919b in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:502 #10 0x7f0220c0919b in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:502 #11 0x7f0220c0921b in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:495 #12 0x7f0220c0919b in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:502 #13 0x7f0220c0919b in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:502 #14 0x7f0220c0919b in QSGNodeVisitorEx::visitChildren (this=0x7f020c01e250, node=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:502 #15 0x7f0220c0919b in QSGNodeVisitorEx::visitChildren (this=this@entry=0x7f020c01e250, node=node@entry=0x7f019805c3b0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/qsgadaptationlayer.cpp:502 #16 0x7f0220c4d707 in QSGSoftwareRenderableNodeUpdater::updateNodes (this=0x7f020c01e250, node=, node@entry=0x7f019805c3b0, isNodeRemoved=isNodeRemoved@entry=false) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenodeupdater.cpp:277 #17 0x7f0220c3f5f0 in QSGAbstractSoftwareRenderer::nodeAdded (this=this@entry=0x7f0198005620, node=node@entry=0x7f019805c3b0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgabstractsoftwarerenderer.cpp:261 #18 0x7f0220c40ee5 in QSGAbstractSoftwareRenderer::nodeChanged (this=0x7f0198005620, node=0x7f019805c3b0, state=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgabstractsoftwarerenderer.cpp:102 #19 0x7f0220c97fd2 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x5649cbe06620) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/items/qquickwindow.cpp:521 #20 0x7f0220c562bd in QSGSoftwareRenderThread::sync (this=this@entry=0x7f01a6186890, inExpose=inExpose@entry=true) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/scenegraph/adaptations/software/qsgsoftwarethreadedrenderloop.cpp:437 #21 0x7f0220c56d92 in
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #17 from Aleksey Kontsevich --- However found condition when it always crashes/freezes: press Klipper hotkey - to show records at mouse position, switch to cyrillic, type something - to filter records - crash/freeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #16 from Aleksey Kontsevich --- Tried gdb however it does not allow to catch these freezes - only crashes, no crash yet however. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #15 from Aleksey Kontsevich --- > coredumpctl No coredumps found. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #13 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #12) > I already told you what you need to do, I already told You that I can't! >Aleksey: get a backtrace and submit HOW???!!! Crash reporter does not appear! > there is no indication that your issue is the same as this one. There are a lot of indications the issues is the same: - Same OS - openSUSE Tumbleweed - same kernel version - same plasma version - same symptoms - same time it appeared - same OS upgrade in Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #11 from Aleksey Kontsevich --- Now it freezes all the time!!! Every minute!!! 100% CPU load - killing and restart does not help!!! Do something! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #10 from Aleksey Kontsevich --- (In reply to Aleksey Kontsevich from comment #9) > (In reply to Nate Graham from comment #8) > > If you can reproduce it, please get a backtrace and file a new bug report. > > After cache cleaning it sometimes crashes but now it restarts immediately > after the crash so it is less annoying. However crash reporter does not > appear now, so I can't report the stack. Crashes again, workaround helped temporarily. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #9 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #8) > If you can reproduce it, please get a backtrace and file a new bug report. After cache cleaning it sometimes crashes but now it restarts immediately after the crash so it is less annoying. However crash reporter does not appear now, so I can't report the stack. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #7 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #6) > Please file a new bug report for that, as there's no way to know it's the > same issue without a backtrace of the crash. Same OS, same kernel, same plasma version, same symptoms, same time! What else?! I reported the bug but kde crash reporter had not uploaded it for some reason - also buggy! ;) I did kill plasmashell, then deleted ~/.cache, then restarted plasmashell - no freezes observed since then. Will check more tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Aleksey Kontsevich changed: What|Removed |Added CC||akontsev...@gmail.com --- Comment #5 from Aleksey Kontsevich --- I have the same bug after recent openSUSE Tubleweed upgrades: Plasmashell constantly freezes (100% CPU) and crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465962] New: Plasmashell freezes and crashes
https://bugs.kde.org/show_bug.cgi?id=465962 Bug ID: 465962 Summary: Plasmashell freezes and crashes Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: akontsev...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.0) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: https://forums.opensuse.org/t/plasmashell-freezes/164477 Same as here: https://bugs.kde.org/show_bug.cgi?id=465872 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f7a4388f47c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f7a4383ce16 in raise () from /lib64/libc.so.6 #6 0x7f7a4382589c in abort () from /lib64/libc.so.6 #7 0x7f7a43aacbf7 in ?? () from /lib64/libstdc++.so.6 #8 0x7f7a43abc23c in ?? () from /lib64/libstdc++.so.6 #9 0x7f7a43abc2a7 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x7f7a43eba437 in qTerminate() () from /lib64/libQt5Core.so.5 #11 0x7f7a43ebbe84 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f7a4388d615 in start_thread () from /lib64/libc.so.6 #13 0x7f7a43913c60 in clone3 () from /lib64/libc.so.6 Thread 10 (Thread 0x7f79ecd8e6c0 (LWP 29143) "QSGSoftwareRend"): #1 0x7f7a4388c960 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f7a43efb74b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #3 0x7f7a45e55ff1 in ?? () from /lib64/libQt5Quick.so.5 #4 0x7f7a45e57281 in ?? () from /lib64/libQt5Quick.so.5 #5 0x7f7a43ef5e3d in ?? () from /lib64/libQt5Core.so.5 #6 0x7f7a4388d615 in start_thread () from /lib64/libc.so.6 #7 0x7f7a43913c60 in clone3 () from /lib64/libc.so.6 Thread 9 (Thread 0x7f79fc8546c0 (LWP 29085) "plasmashell"): #1 0x7f7a41fe3b4f in ?? () from /lib64/libusbmuxd-2.0.so.6 #2 0x7f7a41fe47e3 in ?? () from /lib64/libusbmuxd-2.0.so.6 #3 0x7f7a4388d615 in start_thread () from /lib64/libc.so.6 #4 0x7f7a43913c60 in clone3 () from /lib64/libc.so.6 Thread 8 (Thread 0x7f79fd0556c0 (LWP 29084) "KCupsConnection"): #1 0x7f7a42c27dbe in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f7a42c27edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f7a44133c2e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f7a440dac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f7a43ef4c47 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f7a18777f07 in KCupsConnection::run() () from /lib64/libkcupslib.so #7 0x7f7a43ef5e3d in ?? () from /lib64/libQt5Core.so.5 #8 0x7f7a4388d615 in start_thread () from /lib64/libc.so.6 #9 0x7f7a43913c60 in clone3 () from /lib64/libc.so.6 Thread 7 (Thread 0x7f79fd8566c0 (LWP 29083) "QQuickXmlQueryE"): #1 0x7f7a42c7754f in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f7a42c278a6 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f7a42c27d68 in ?? () from /lib64/libglib-2.0.so.0 #4 0x7f7a42c27edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f7a44133c2e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f7a440dac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f7a43ef4c47 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f7a20dbd895 in ?? () from /usr/lib64/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #9 0x7f7a43ef5e3d in ?? () from /lib64/libQt5Core.so.5 #10 0x7f7a4388d615 in start_thread () from /lib64/libc.so.6 #11 0x7f7a43913c60 in clone3 () from /lib64/libc.so.6 Thread 6 (Thread 0x7f7a20d636c0 (LWP 29066) "QSGSoftwareRend"): #1 0x7f7a4388c960 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f7a43efb74b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #3 0x7f7a45e55ff1 in ?? () from /lib64/libQt5Quick.so.5 #4 0x7f7a45e57281 in ?? () from /lib64/libQt5Quick.so.5 #5 0x7f7a43ef5e3d in ?? () from /lib64/libQt5Core.so.5 #6 0x7f7a4388d615 in start_thread () from /lib64/libc.so.6 #7 0x7f7a43913c60 in clone3 () from /lib64/libc.so.6 Thread 5 (Thread 0x7f7a227b66c0 (LWP 29061) "QQuickPixmapRea"): #1 0x7f7a42c27dbe in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f7a42c27edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f7a44133c2e in
[kmail2] [Bug 393531] Fail to connect to Exchange server
https://bugs.kde.org/show_bug.cgi?id=393531 Aleksey Kontsevich changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Aleksey Kontsevich --- That was many years ago, do not use this soft any more. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 394317] Applications crash on reboot
https://bugs.kde.org/show_bug.cgi?id=394317 Aleksey Kontsevich changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Aleksey Kontsevich --- Not repro any more. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 458175] New: Support demangling Rust symbols
https://bugs.kde.org/show_bug.cgi?id=458175 Bug ID: 458175 Summary: Support demangling Rust symbols Product: Heaptrack Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: m...@milianw.de Reporter: aleksey.kla...@gmail.com Target Milestone: --- Heaptrack mostly works out of the box with Rust and is very helpful. However, there's one snag -- it doesn't demangle Rust symbols automatically. It would be great if it did this though! There's a C library which implements Rust demangling here: https://github.com/LykenSol/rust-demangle.c And https://github.com/rui314/mold/issues/371 might contain some more useful context. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 --- Comment #48 from Aleksey Kontsevich --- (In reply to David de Cos from comment #47) > I have this only in Wayland and only with Telegram. I use the binary > downloaded from their web page: > https://telegram.org/dl/desktop/linux (not Flatpak or Snap) It happens with X11 as well mostly when we have many apps started on session restore. Sometimes happens with KeePassXC, KShutdown, etc. Recent time very rarely however. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382793] QuiteRss news notification hangs plasmashell
https://bugs.kde.org/show_bug.cgi?id=382793 --- Comment #11 from Aleksey Kontsevich --- (In reply to Nate Graham from comment #10) > A lot has changed since this bug was filed. Is it still reproducible for you > in Plasma 5.25 (the latest LTS version) or 5.25 (the latest version, period)? QuiteRSS stopped to work for me: they do not update it for new Qt/Plasma. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455638] New: Captured bouncing launch icon of itself
https://bugs.kde.org/show_bug.cgi?id=455638 Bug ID: 455638 Summary: Captured bouncing launch icon of itself Product: Spectacle Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: xglo...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 149942 --> https://bugs.kde.org/attachment.cgi?id=149942=edit bouncing icon SUMMARY After recent update Plasma 5.25 spectacle starts capturing the self icon. STEPS TO REPRODUCE 1. Update manjaro unstable 2. Capture fullscreen or rectangular OBSERVED RESULT There is a Spectacle icon on a screenshot EXPECTED RESULT No Spectacle icon on a screenshot as it was before. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.5-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 2.40GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445893] KDE Plasma segfaults in Plasma::WindowTextureProvider::~WindowTextureProvider()
https://bugs.kde.org/show_bug.cgi?id=445893 --- Comment #13 from Aleksey Midenkov --- Please change the priority to critical. This is very annoying bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445893] KDE Plasma segfaults in Plasma::WindowTextureProvider::~WindowTextureProvider()
https://bugs.kde.org/show_bug.cgi?id=445893 Aleksey Midenkov changed: What|Removed |Added CC||midenok+kdeb...@gmail.com --- Comment #12 from Aleksey Midenkov --- Always crashes after awake from sleep. Package: plasma-workspace Version: 4:5.24.4-0ubuntu1 Package: libqt5quick5 Version: 5.15.3+dfsg-1 [KCrash Handler] #4 0x7f64366aeb10 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f64366aeb8a in QSGAreaAllocator::deallocate(QRect const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f64366b5353 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f64366b54a1 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f64366b54bd in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f6427f4e3d1 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so #10 0x7f6436700012 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f64366f996f in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f64366fbe49 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f6434b03ca1 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f6434677b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #15 0x7f6434709a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452446] After recent KDE upgrade I can't switch keyboard layout by Meta key
https://bugs.kde.org/show_bug.cgi?id=452446 --- Comment #3 from Aleksey Kontsevich --- Sorry, false alert -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452446] After recent KDE upgrade I can't switch keyboard layout by Meta key
https://bugs.kde.org/show_bug.cgi?id=452446 Aleksey Kontsevich changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452446] After recent KDE upgrade I can't switch keyboard layout by Meta key
https://bugs.kde.org/show_bug.cgi?id=452446 --- Comment #2 from Aleksey Kontsevich --- Also Ctrl-Shift does not to select text - this is terrible! Guys, what are You doing???!!! You're killing KDE! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452446] After recent KDE upgrade I can't switch keyboard layout by Meta key
https://bugs.kde.org/show_bug.cgi?id=452446 --- Comment #1 from Aleksey Kontsevich --- *Before recent KDE upgrade I was able to switch keyboard layout by Meta key, now I can't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452446] New: After recent KDE upgrade I can't switch keyboard layout by Meta key
https://bugs.kde.org/show_bug.cgi?id=452446 Bug ID: 452446 Summary: After recent KDE upgrade I can't switch keyboard layout by Meta key Product: kwin Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: akontsev...@gmail.com Target Milestone: --- Before recent KDE upgrade I can't switch keyboard layout by Meta key any more. Layout settings was simplified and there are no X11 options any more to choose Meta (win key) as layouts switch. That is terrible: KDE become worse and worse everyday and goes in terrible GNOME direction by removing useful and used to features in every release: - locale settings https://bugs.kde.org/show_bug.cgi?id=394698 - removed 3D cube - etc etc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449251] New: Global Menu Applet incorrectly handle multiple activities and show menu items from another app.
https://bugs.kde.org/show_bug.cgi?id=449251 Bug ID: 449251 Summary: Global Menu Applet incorrectly handle multiple activities and show menu items from another app. Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: xglo...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 145989 --> https://bugs.kde.org/attachment.cgi?id=145989=edit reproduced on chrome as well SUMMARY In some cases Global Menu Applet still show menu items from previously focused app, when current focused app hasn't global menu. STEPS TO REPRODUCE 1. Place on panel Global Menu Applet 2. Switch to second activity 3. Open for example Dolphin 4. On a 1st activity open for example maximized Firefox, and sure that is in focus. 5. Open Dolphin in 1st activity 6. Close Dolphin in 1st activity OBSERVED RESULT After closed Dolphin focus brings back to Firefox, but global menu applet still show menu from Dolphin from another activity. EXPECTED RESULT Global Menu Applet should be empty as Firefox not expose menu. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449160] Wrong sticky window behavior when moving in multi-monitor setup on Wayland
https://bugs.kde.org/show_bug.cgi?id=449160 --- Comment #3 from Aleksey Zagorodnikov --- Nope, only reproduces when grab title. And found that this bug can be reproduced only if window title was below the threshold. If title initially above threshold it can moved smoothly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449160] Wrong sticky window behavior when moving in multi-monitor setup on Wayland
https://bugs.kde.org/show_bug.cgi?id=449160 --- Comment #1 from Aleksey Zagorodnikov --- Created attachment 145925 --> https://bugs.kde.org/attachment.cgi?id=145925=edit arrangement of monitors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449160] New: Wrong sticky window behavior when moving in multi-monitor setup on Wayland
https://bugs.kde.org/show_bug.cgi?id=449160 Bug ID: 449160 Summary: Wrong sticky window behavior when moving in multi-monitor setup on Wayland Product: kwin Version: git master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: xglo...@gmail.com Target Milestone: --- Created attachment 145924 --> https://bugs.kde.org/attachment.cgi?id=145924=edit video demonstration SUMMARY My main monitor with 1440 vertical resolution and second monitor with 1024 on vertical. Second monitor placed in right-hand of primary monitor and centered on vertical. So second monitor has position +2560+208. On second monitor there is a plasma panel on top. When I move window on primary monitor by vertical axis from bottom to top it sticks/snap/hangs around +208+24 position and can move further only after mouse pass +208 position. Despite some weird recording artifacts I show it on this video https://youtu.be/SZSH1JiTtFg STEPS TO REPRODUCE 1. Setup second monitor on side of primary and offset it by vertical. 2. Place plasma panel on top of second monitor 3. Drag window on main monitor from bottom to top OBSERVED RESULT Window snaps at some point on main monitor, right when pass height where placed panel on second monitor. It also snaps when moved from top to bottom. EXPECTED RESULT Window should be moved smoothly from bottom to top and top to bottom on this monitor. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449099] Hot-plugging Primary Monitor not handled correctly for XWayland
https://bugs.kde.org/show_bug.cgi?id=449099 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449099] New: Hot-plugging Primary Monitor not handled correctly for XWayland
https://bugs.kde.org/show_bug.cgi?id=449099 Bug ID: 449099 Summary: Hot-plugging Primary Monitor not handled correctly for XWayland Product: kwin Version: git-stable-Plasma/5.24 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: xglo...@gmail.com Target Milestone: --- SUMMARY If I unplug and plug again primary monitor it was incorrectly showed in xrandr' output as not primary, and Xwayland apps starts on wrong monitor. STEPS TO REPRODUCE 1. Login in wayland session 2. Run xrandr 3. Unplug Primary monitor 4. Plug Primary monitor again 5. Run xrandr again and compare output OBSERVED RESULT Xrandr output in 5th step: XWAYLAND1 connected primary 1280x1024+2560+208 (normal left inverted right x axis y axis) 380mm x 300mm XWAYLAND2 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm EXPECTED RESULT Xrandr output in 5th step should be the same as in 2nd step: XWAYLAND0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm XWAYLAND1 connected 1280x1024+2560+208 (normal left inverted right x axis y axis) 380mm x 300mm SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION My primary 2560*1440 monitor is connected via DP, and secondary 1280*1024 monitor connected via HDMI and placed on right-hand side. After login in logs: kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564ced0892c0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(0,0 1280x1024), scale=1) kwin_xwl: Setting primary KWin::DrmOutput(0x564ced0892c0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) 33 After unplug monitor: kwin_wayland_drm: Removing output KWin::DrmOutput(0x564ced0892c0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) kwin_xwl: Setting primary KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(2560,208 1280x1024), scale=1) 35 kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(2560,208 1280x1024), scale=1) After plug monitor again: kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cedebd5e0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(0,0 1280x1024), scale=1) kwin_xwl: Setting primary KWin::DrmOutput(0x564cedebd5e0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) 35 Aside from this issue I've also experiencing #371717 after reconnect primary monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #33 from Aleksey Zagorodnikov --- Hi folks, I don't know is it make sense for investigation, but for my curiosity I was tried to research it myself. I've using desktop Intel UHD630 with two monitors, primary on DP and secondary on HDMI. And on my setup I need often to effectively unplug-plug DP monitor via KVM switch, while HDMI connected permanently, so I experiencing this kind of bugs a lot during work. Maybe this bug related to "Primary Monitor" feature? If I remove Q_EMIT primaryOutputChanged(primary); in Platform::setPrimaryOutput I can switch monitor back and forth and plasmashell doesn't loose containment on secondary monitor. I've spot another strange behavior with Primary Monitor feature and commented this https://invent.kde.org/plasma/kwin/-/commit/f91ae3e97584767d273479c4013a43e279d77f40#note_383499 but not really sure is it related or not. PS: A bit off-topic, but can we introduce settings for ignoring hot-plug events from monitors? I actually can use wayland only after removing updateOutputs from DrmBackend::handleUdevEvent, otherwise after switching KVM back and forth some windows on desktop changes their positions, a bit annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448963] Panel disappears after turning monitors off/on
https://bugs.kde.org/show_bug.cgi?id=448963 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #2 from Aleksey Zagorodnikov --- In my case not only panel is gone, but background goes black and right click on it not work anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 --- Comment #38 from Aleksey Kontsevich --- (In reply to Linus Dierheimer from comment #37) > However it is often missing, and only shows up after i manually start an app > with an app indicator. After that it works fine Same for me: after app restart icon is shown. > Is this the same bug / root cause? Seems so. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447481] Can't mount USB drive
https://bugs.kde.org/show_bug.cgi?id=447481 --- Comment #2 from Aleksey Kontsevich --- Seems solved after recent updates. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 --- Comment #5 from Aleksey Zagorodnikov --- I'm so sorry, didn't realized that fix is not released yet in 5.23.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #4 from Aleksey Zagorodnikov --- Hi, I've recently switched to wayland and now experiencing this problem. It is marked as resolved, but in my case it is definitely here. I'm using dual monitor setup if it matter. Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.13-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447481] New: Can't mount USB drive
https://bugs.kde.org/show_bug.cgi?id=447481 Bug ID: 447481 Summary: Can't mount USB drive Product: dolphin Version: 21.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: akontsev...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Can't mount USB drive in Tumbleweed KDE while it is successfully mounts on my Kubuntu 20.04 Laptop. Dolphin prints error: > Error mounting /dev/sdd1 at /run/media/user/TRANSCEND: > The function 'bd_fs_mount' called, but not implemented! Problem is fully described here: https://forums.opensuse.org/showthread.php/563878-Can-t-mount-USB-drive -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 --- Comment #35 from Aleksey Kontsevich --- Applications are: - KeepassXC (Qt) - KShutdown (KDE) So they follow SNI, happens very often. -- You are receiving this mail because: You are watching all bug changes.
