[kde] [Bug 485008] Upgrade failure
https://bugs.kde.org/show_bug.cgi?id=485008 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 --- Comment #27 from Jason Playne --- (In reply to Lars Veldscholte from comment #26) > Same issue here. I didn't have this issue on Plasma 5.27 (I was already > using Wayland back then). > > Straight after booting, it always works fine, but after using Plasma for a > while and starting up a game, the mouse doesn't work anymore. I've also > noticed that sometimes it spontaneously starts working fine again after > trying some things (alt-tabbing, clicking, mashing some buttons) but I've > not been able to narrow it down to some specific trigger. > > The issue still exists on Plasma 6.02 / Qt 6.6.2. I can concur that a reboot does indeed allow me to play the game, i wonder if sleep/resume is the thing that breaks it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 469468] Unable to open repo's
https://bugs.kde.org/show_bug.cgi?id=469468 --- Comment #2 from Jason Playne --- (In reply to Hamed Masafi from comment #1) > Could you please test with new version? > Now I don't think there is such a problem. > Please test with the latest version and let me know the result Hi Hamed, So sorry for not doing this sooner (I only just found it in my inbox) I found that the snap version was unable to open my existing repos the flatpak version was able to. So it's going to be a snap packaging issue. How I tested: * I still had Kommit installed via snap (v1.0.2) and opened it up and attempted to open my repo, nothing * I performed the following actions from the dialog ```ATTENTION sudo snap connect kommit:gpg-keys :gpg-keys sudo snap connect kommit:ssh-keys :ssh-keys if you wish to use your pre-existing keys``` * Opened a git repo - noithing Installed Kommit via Flatpak and it just worked. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 475426] New: Stamps are rendered sideways
https://bugs.kde.org/show_bug.cgi?id=475426 Bug ID: 475426 Summary: Stamps are rendered sideways Classification: Applications Product: okular Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Created attachment 162186 --> https://bugs.kde.org/attachment.cgi?id=162186&action=edit screen recording of a stamp being placed (mouse down) and then rotated after release SUMMARY When adding a stamp to my PDF, it appears sideways on the PDF after adding it. Unfortunately this document has lots of PII as it is for building plans - I was wanting to use a stamp sign "sign" it. PDFs generated by Firefox (printing a page) did not exhibit this behaviour. One lead might be that the problem PDF has a page rotation of 270 degrees whereas the Firefox one does not. PDF DETAILS PdfInfo for the PDF (A3, Landscape) that exhibits the problem: Producer:iLovePDF ModDate: Tue Oct 10 13:34:36 2023 AWST Custom Metadata: no Metadata Stream: no Tagged: no UserProperties: no Suspects:no Form:none JavaScript: no Pages: 3 Encrypted: no Page size: 842 x 1191 pts (A3) Page rot:270 File size: 1241154 bytes Optimized: no PDF version: 1.7 --- PDF Info for a Firefox Print to PDF (A3, Landscape) that does not exhibit the problem Creator: Mozilla Firefox 118.0.1 Producer:cairo 1.17.4 (https://cairographics.org) CreationDate:Tue Oct 10 21:09:20 2023 AWST Custom Metadata: no Metadata Stream: no Tagged: no UserProperties: no Suspects:no Form:none JavaScript: no Pages: 2 Encrypted: no Page size: 1191 x 842 pts (A3) Page rot:0 File size: 55240 bytes Optimized: no PDF version: 1.5 --- STEPS TO REPRODUCE 1. Find a PDF that exhibits the problem (hopefully one without lots of PII) 2. Select a Stamp 3. Left Mouse Down and observe the stamp in the correct orientation 4. Release left mouse button and see the stamp rotated OBSERVED RESULT While mouse button down, see stamp in correct orientation on mouse button release see image rotated 90 degrees Counter Clockwise (or 270 degrees clockwise) EXPECTED RESULT Stamp is in correct orientation SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.6-060506-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 469468] New: Unable to open repo's
https://bugs.kde.org/show_bug.cgi?id=469468 Bug ID: 469468 Summary: Unable to open repo's Classification: Applications Product: kommit Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: hamed.mas...@gmail.com Reporter: ja...@jasonplayne.com CC: mon...@kde.org Target Milestone: --- SUMMARY Unable to open a code repo. Note: I was able to use view a repo on Friday (3 days ago) on a different computer Ok, STEPS TO REPRODUCE 1. Install commit v 0.4.0 from snap 2. attempt to open a repo, either from the File -> Open menu or "File -> Recent Repositories" menu OBSERVED RESULT no error (either dialog or on the stderr/stdout output), but also no display of my repo EXPECTED RESULT A view of the repo SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466923] XWayland crash on wake with DP monitor that takes 6 seconds to turn on
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #10 from Jason Playne --- (In reply to Nate Graham from comment #9) > There's no set threshold, but the longer it takes to turn back on, the > higher the chance that it will trigger a re-layout of stuff which runs a lot > of code and could be the cause of this crash. That's why I was asking. it's about 6 seconds from sleep to monitor on showing SDDM - if that helps -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #8 from Jason Playne --- (In reply to Nate Graham from comment #7) > Thanks. We're still missing a lot of debug symbols but it seems like it's > crashing when screens change? Do you have multiple screens, and are any of > them slow to turn on/reconnect? Are any of them using a DisplayPort cable? I have a single monitor (AOC 34" 3440x1440 doing 144hz) plugged in via Display Port. I personally wouldn't call it "A long time", <6 seconds for the whole system to resume and screen to turn on I would guess - but what's the threshold there? how many seconds? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #6 from Jason Playne --- with xwayland-dbgsym installed I get this warning: Section `.reg-xstate/42875' in core file too small. #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139852397381824) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f31ec7788c0 (LWP 42875))] (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139852397381824) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139852397381824) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139852397381824, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f31ecc42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f31ecc287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x564cd6182080 in OsAbort () at ../os/utils.c:1353 #6 0x564cd618db2f in AbortServer () at ../os/log.c:879 #7 FatalError (f=0x564cd61e1020 "Caught signal %d (%s). Server aborting\n") at ../os/log.c:1017 #8 0x564cd6180274 in OsSigHandler (unused=, sip=0x7fff9ce043f0, signo=11) at ../os/osinit.c:156 #9 OsSigHandler (signo=11, sip=0x7fff9ce043f0, unused=) at ../os/osinit.c:110 #10 #11 xwl_screen_destroy_drm_lease_device (xwl_screen=0x564cd8d5b380, wp_drm_lease_device_v1=0x564cd8d80d00) at ../hw/xwayland/xwayland-drm-lease.c:430 #12 0x7f31ece6ee2e in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #13 0x7f31ece6b493 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #14 0x7f31ed3e0b20 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #15 0x7f31ed3e12c3 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #16 0x7f31ed3e14bc in wl_display_dispatch_queue_pending () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #17 0x564cd60594bb in xwl_read_events (xwl_screen=0x564cd805a550) at ../hw/xwayland/xwayland-screen.c:482 #18 xwl_read_events (xwl_screen=0x564cd805a550) at ../hw/xwayland/xwayland-screen.c:469 #19 0x564cd6181841 in ospoll_wait (ospoll=0x564cd8056210, timeout=) at ../os/ospoll.c:657 #20 0x564cd60c1cb0 in WaitForSomething (are_ready=0) at ../os/WaitFor.c:208 #21 Dispatch () at ../dix/dispatch.c:492 #22 0x564cd604fc63 in dix_main (envp=, argv=, argc=) at ../dix/main.c:271 #23 main (argc=, argv=, envp=) at ../dix/stubmain.c:34 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #5 from Jason Playne --- seems to be a lot of question marks there, how do I tell which debug libs I need to install? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #4 from Jason Playne --- Sure warning: Section `.reg-xstate/264915' in core file too small. #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139954276735168) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f49a4f318c0 (LWP 264915))] (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139954276735168) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139954276735168) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139954276735168, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f49a5442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f49a54287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x55bd2cded080 in ?? () #6 0x55bd2cdf8b2f in ?? () #7 0x55bd2cdeb274 in ?? () #8 #9 0x55bd2ccbf389 in ?? () #10 0x7f49a53fae2e in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #11 0x7f49a53f7493 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #12 0x7f49a5b99b20 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #13 0x7f49a5b9a2c3 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #14 0x7f49a5b9a4bc in wl_display_dispatch_queue_pending () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #15 0x55bd2ccc44bb in ?? () #16 0x55bd2cdec841 in ?? () #17 0x55bd2cd2ccb0 in ?? () #18 0x55bd2ccbac63 in ?? () #19 0x7f49a5429d90 in __libc_start_call_main (main=main@entry=0x55bd2ccb9420, argc=argc@entry=13, argv=argv@entry=0x7ffc5a458b48) at ../sysdeps/nptl/libc_start_call_main.h:58 #20 0x7f49a5429e40 in __libc_start_main_impl (main=0x55bd2ccb9420, argc=13, argv=0x7ffc5a458b48, init=, fini=, rtld_fini=, stack_end=0x7ffc5a458b38) at ../csu/libc-start.c:392 #21 0x55bd2ccbc495 in ?? () -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #2 from Jason Playne --- xwayland installed version is 2:22.1.1-1ubuntu0.5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #1 from Jason Playne --- The first entry in systemd's coredump list for /usr/bin/Xwayland is from Fri 2022-12-09 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] New: XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 Bug ID: 466923 Summary: XWayland Crash on Wake 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: ja...@jasonplayne.com Target Milestone: --- Created attachment 157029 --> https://bugs.kde.org/attachment.cgi?id=157029&action=edit The the back traces in systemd after resume SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Log into a wayland session 2. open an xwayland app (for example, discord) 3. push system to sleep 4. wake system OBSERVED RESULT No XWayland apps are running EXPECTED RESULT The software I started before putting the machine to sleep is there when I wake it up SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION this happens every time i put the computer to sleep and wake it again. It has been happening for a while now (sometime during the 5.26 release cycle) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 --- Comment #74 from Jason Playne --- I too believe that the upgrade to KDE Neon 22.04 has resolved this issue (just did a log out/in and it worked as expected) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460917] New: Enter key does not work on second login
https://bugs.kde.org/show_bug.cgi?id=460917 Bug ID: 460917 Summary: Enter key does not work on second login 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: ja...@jasonplayne.com Target Milestone: --- SUMMARY *** If you logout and then attempt to login, the enter key does not submit the login request (you have to click the button) *** (sorry, not sure how to file this bug correctly) STEPS TO REPRODUCE 1. from SDDM login with your user/password 2. Log Out from your session 3. Enter your password and push the "enter" key. OBSERVED RESULT One does not simply login a second time using the enter key EXPECTED RESULT You should be logged in SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.3-060003-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 --- Comment #10 from Jason Playne --- Adding in some notes (to see if my usage patterns jive with yours) I have 3 virtual desktops. When I primarily use just one of them (#3) the issue does not manifest When I am regularly switching between each the problem manifests (but not on change) On each desktop I have #1 Java XWayland (jetbrains ide) + Opera Web Browser (Wayland) #2 Vivaldi (Wayland) and Teams (X11, Electron) #3 Discord (X11) and Firefox (X11) I am wondering if this might be a Chromium/Wayland caused thing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #12 from Jason Playne --- (In reply to space9301 from comment #9) > (In reply to Jason Playne from comment #1) > > it appears this segfault didn't create a core dump? > > > > $ coredumpctl > > No coredumps found. > > Do you have core dumps enabled? If coredumpctl still returns the same > result, they might be disabled. > Places to check: https://wiki.archlinux.org/title/Core_dump, > https://linux-audit.com/understand-and-configure-core-dumps-work-on-linux/ > - sysctl kernel.core_pattern > - /usr/lib/sysctl.d/50-coredump.conf > - ulimit -c Thank you for the help, I did install coredumpctl after the first crashes, and one of of the subsequent ones did produce something. Thank you for making me look again! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #11 from Jason Playne --- oh and following the documentation I get a slightly more rich output jason@jason-desktop:~ $ coredumpctl gdb /usr/bin/plasmashell PID: 248057 (plasmashell) UID: 1000 (jason) GID: 1000 (jason) Signal: 6 (ABRT) Timestamp: Sat 2022-10-15 11:20:36 AWST (2 days ago) Command Line: plasmashell --replace Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/session-171.scope Unit: session-171.scope Slice: user-1000.slice Session: 171 Owner UID: 1000 (jason) Boot ID: 9123c4115a9743108f1f78feb5e71e19 Machine ID: 0b8920f9b79a4d7aa86de3faed35fe2d Hostname: jason-desktop Storage: /var/lib/systemd/coredump/core.plasmashell.1000.9123c4115a9743108f1f78feb5e71e19.248057.1665804036.lz4 Message: Process 248057 (plasmashell) of user 1000 dumped core. Stack trace of thread 248057: #0 0x7fb5b8a6f00b __GI_raise (libc.so.6 + 0x4300b) #1 0x7fb5b8a4e859 __GI_abort (libc.so.6 + 0x22859) #2 0x7fb5b8e92bd9 qt_message_fatal (libQt5Core.so.5 + 0x92bd9) #3 0x7fb5b9539d9b init_platform (libQt5Gui.so.5 + 0x139d9b) #4 0x7fb5b953a218 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13a218) #5 0x7fb5b90bbb06 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bbb06) #6 0x7fb5b953d333 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13d333) #7 0x7fb5b9f741bd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1741bd) #8 0x55b198773a0d main (plasmashell + 0x28a0d) #9 0x7fb5b8a50083 __libc_start_main (libc.so.6 + 0x24083) #10 0x55b19877491e _start (plasmashell + 0x2991e) Stack trace of thread 248058: #0 0x7fb5b8b3e99f __GI___poll (libc.so.6 + 0x11299f) #1 0x7fb5b754336e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7fb5b75434a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7fb5b910fb82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #4 0x7fb5b90b3b3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #5 0x7fb5b8ecd342 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcd342) #6 0x7fb5b9c9ef4b n/a (libQt5DBus.so.5 + 0x18f4b) #7 0x7fb5b8ece543 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xce543) #8 0x7fb5bb185609 start_thread (libpthread.so.0 + 0x8609) #9 0x7fb5b8b4b133 __clone (libc.so.6 + 0x11f133) GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/plasmashell... Reading symbols from /usr/lib/debug/.build-id/22/87b8620679417738a0acf1dba04885bb86a4bb.debug... [New LWP 248057] [New LWP 248058] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `plasmashell --replace'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. [Current thread is 1 (Thread 0x7fb5b4f572c0 (LWP 248057))] (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7fb5b8a4e859 in __GI_abort () at abort.c:79 #2 0x7fb5b8e92bd9 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #3 QMessageLogger::fatal (this=this@entry=0x7ffecbcb36f0, msg=msg@entry=0x7fb5b99f9a05 "%s") at global/qlogging.cpp:893 #4 0x7fb5b9539d9b in init_platform (argv=, argc=@0x7ffecbcb395c: 2, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:209 #5 QGuiApplicationPriv
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #10 from Jason Playne --- i have managed to find a coredump PID: 248057 (plasmashell) UID: 1000 (jason) GID: 1000 (jason) Signal: 6 (ABRT) Timestamp: Sat 2022-10-15 11:20:36 AWST (2 days ago) Command Line: plasmashell --replace Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/session-171.scope Unit: session-171.scope Slice: user-1000.slice Session: 171 Owner UID: 1000 (jason) Boot ID: 9123c4115a9743108f1f78feb5e71e19 Machine ID: 0b8920f9b79a4d7aa86de3faed35fe2d Hostname: jason-desktop Storage: /var/lib/systemd/coredump/core.plasmashell.1000.9123c4115a9743108f1f78feb5e71e19.248057.1665804036.lz4 Message: Process 248057 (plasmashell) of user 1000 dumped core. Stack trace of thread 248057: #0 0x7fb5b8a6f00b __GI_raise (libc.so.6 + 0x4300b) #1 0x7fb5b8a4e859 __GI_abort (libc.so.6 + 0x22859) #2 0x7fb5b8e92bd9 qt_message_fatal (libQt5Core.so.5 + 0x92bd9) #3 0x7fb5b9539d9b init_platform (libQt5Gui.so.5 + 0x139d9b) #4 0x7fb5b953a218 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13a218) #5 0x7fb5b90bbb06 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bbb06) #6 0x7fb5b953d333 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13d333) #7 0x7fb5b9f741bd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1741bd) #8 0x55b198773a0d main (plasmashell + 0x28a0d) #9 0x7fb5b8a50083 __libc_start_main (libc.so.6 + 0x24083) #10 0x55b19877491e _start (plasmashell + 0x2991e) Stack trace of thread 248058: #0 0x7fb5b8b3e99f __GI___poll (libc.so.6 + 0x11299f) #1 0x7fb5b754336e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7fb5b75434a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7fb5b910fb82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #4 0x7fb5b90b3b3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #5 0x7fb5b8ecd342 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcd342) #6 0x7fb5b9c9ef4b n/a (libQt5DBus.so.5 + 0x18f4b) #7 0x7fb5b8ece543 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xce543) #8 0x7fb5bb185609 start_thread (libpthread.so.0 + 0x8609) #9 0x7fb5b8b4b133 __clone (libc.so.6 + 0x11f133) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 --- Comment #8 from Jason Playne --- (In reply to space9301 from comment #7) > (In reply to Jason Playne from comment #6) > > *** Bug 460336 has been marked as a duplicate of this bug. *** > > I'm not sure this is a duplicate. For me, my programs remained open -- only > plasmashell crashed. They were only lost when I killed kwin_wayland. There > were no segfaults in either kwin_wayland or plasmashell. > > To reproduce the black screen with movable cursor: > - killall plasmashell(the screen is now black, as the desktop background > is handled by plasmashell, but all the programs are open. In the original > bug, plasmashell failed to relaunch) > - ps $(pgrep kwin_wayland) > PID TTY STAT TIME COMMAND > 220965 ?Ssl0:00 /usr/bin/kwin_wayland_wrapper --xwayland > 237394 ?Sl 0:02 /usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayland-fd 9 > - killall kwin_wayland(the screen is black, and all the programs are > gone, but I can still move my cursor and launch a terminal with ctrl-alt-t) > - ps $(pgrep kwin_wayland) > PID TTY STAT TIME COMMAND > 220965 ?Ssl0:00 /usr/bin/kwin_wayland_wrapper --xwayland > 238586 ?Sl 0:02 /usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayland-fd 9 > (kwin_wayland has automatically been restarted. Killing kwin_wayland_wrapper > gets me to the login screen) > - kstart plasmashell (I can now use my session again) > > Sorry if the original bug description was misleading. "Output of journalctl > /usr/bin/kwin_wayland, including crashes" should have been "including > crashes of plasmashell". Your description describes what I am seeing (better than I am able to put into words) The segfault's and back traces I have seen I am thinking are incidental. I believe what I see is what you are describing. I suddenly get a back screen with a movable cursor, kwin_wayland is still running - lots of complains from the apps about losing their connection to the wayland server. I *think* the apps are still alive - I work around the problem with restarting sddm (the big hammer approach) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 --- Comment #6 from Jason Playne --- *** Bug 460336 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 Jason Playne changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #8 from Jason Playne --- *** This bug has been marked as a duplicate of bug 460513 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected
https://bugs.kde.org/show_bug.cgi?id=460336 Jason Playne changed: What|Removed |Added Summary|kwin_wayland segfault at 10 |kwin_wayland lockup / black |ip 7f220cb74ade sp |screen / clients |7ffcd7b23090 error 4 in |disconnected |libc-2.31.so[7f220caff000+1 | |78000] | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460513] Plasmashell crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=460513 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com --- Comment #3 from Jason Playne --- quick question - when kwin_wayland crashes, does it just leave you with a black screen + movable cursor? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #7 from Jason Playne --- also, any help on how to get info out of a hung process would be nice -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 Jason Playne changed: What|Removed |Added Platform|Other |Neon Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 Jason Playne changed: What|Removed |Added Resolution|BACKTRACE |FIXED --- Comment #6 from Jason Playne --- Unsure if this is related - it appears in the systemd logs around the time of the sddm restart (which is around 20 minutes after the "crash"?) Oct 13 16:24:06 jason-desktop systemd-coredump[94616]: Process 94612 (xdg-desktop-por) of user 117 dumped core. Stack trace of thread 94612: #0 0x7f96af46f00b __GI_raise (libc.so.6 + 0x4300b) #1 0x7f96af44e859 __GI_abort (libc.so.6 + 0x22859) #2 0x7f96af892bd9 qt_message_fatal (libQt5Core.so.5 + 0x92bd9) #3 0x7f96b0739d9b init_platform (libQt5Gui.so.5 + 0x139d9b) #4 0x7f96b073a218 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13a218) #5 0x7f96afabbb06 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2bbb06) #6 0x7f96b073d333 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13d333) #7 0x7f96b15741bd _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1741bd) #8 0x55ffc4a71f55 n/a (xdg-desktop-portal-kde + 0x26f55) #9 0x7f96af450083 __libc_start_main (libc.so.6 + 0x24083) #10 0x55ffc4a7229e n/a (xdg-desktop-portal-kde + 0x2729e) Stack trace of thread 94613: #0 0x7f96af53e99f __GI___poll (libc.so.6 + 0x11299f) #1 0x7f96addd736e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f96addd74a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f96afb0fb82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #4 0x7f96afab3b3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #5 0x7f96af8cd342 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcd342) #6 0x7f96b057af4b n/a (libQt5DBus.so.5 + 0x18f4b) #7 0x7f96af8ce543 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xce543) #8 0x7f96b137f609 start_thread (libpthread.so.0 + 0x8609) #9 0x7f96af54b133 __clone (libc.so.6 + 0x11f133) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #5 from Jason Playne --- Created attachment 152762 --> https://bugs.kde.org/attachment.cgi?id=152762&action=edit output of gdb Output of using the command from https://community.kde.org/KWin/Debugging#Debug_KWin_with_GDB sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file kwin_wayland.gdb" -ex "set logging on" -ex "continue" -ex "thread apply all backtrace" -ex "quit" note: This was run a few minutes *after* the sudden black screen with movable mouse cursor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #4 from Jason Playne --- (In reply to Vlad Zahorodnii from comment #3) > We can't do anything about this bug report without a backtrace or > reproducible steps to reproduce the crash. I understand, I am trying to figure out how to do it. It's just happened a 3rd time, the kwin_wayland process is still there this time -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #2 from Jason Playne --- Created attachment 152759 --> https://bugs.kde.org/attachment.cgi?id=152759&action=edit sddm wayland-session.log This is the second crash in kwin_wayland Before restarting sddm I saved the ssdm wayland-session.log and have attached it here for you. You can see PhpStorm complaining about some stuff (\Traversable, \Doctrine* stuff) and what happens when it goes bang -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 --- Comment #1 from Jason Playne --- it appears this segfault didn't create a core dump? $ coredumpctl No coredumps found. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460336] New: kwin_wayland segfault at 10 ip 00007f220cb74ade sp 00007ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000]
https://bugs.kde.org/show_bug.cgi?id=460336 Bug ID: 460336 Summary: kwin_wayland segfault at 10 ip 7f220cb74ade sp 7ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000] Classification: Plasma Product: kwin Version: git-stable-Plasma/5.26 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Just had a segfault crash in kwin_wayland in 5.26 I was working away (Typing PhpStorm) when the screen went black and I had a movable cursor STEPS TO REPRODUCE 1. ? 2. ? 3. ? OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-060001-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION The only useful thing I could find is in dmesg [16504.265944] kwin_wayland[43937]: segfault at 10 ip 7f220cb74ade sp 7ffcd7b23090 error 4 in libc-2.31.so[7f220caff000+178000] [16504.265956] Code: 00 41 be 02 00 00 00 b8 80 00 00 00 41 bd 20 00 00 00 48 01 d8 4c 8b 40 08 48 8d 48 f0 4c 39 c1 0f 84 6e 03 00 00 49 8b 50 18 <4c> 39 42 10 0f 85 50 0a 00 00 4c 8d 0d 91 50 15 00 4b 83 4c 28 08 I was not prompted by a crash reporting tool after logging back in (recovery was restarting sddm and logging back in) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #34 from Jason Playne --- Created attachment 152258 --> https://bugs.kde.org/attachment.cgi?id=152258&action=edit start menu and notificate, with patch -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com --- Comment #33 from Jason Playne --- (In reply to Malte S. Stretz from comment #30) > I tried the patch and it doesn't seem to fix the issue for me. The error > might be on my side of course. > > The steps I took are (on Neon): > ``` > mkdir bug-459188 > cd bug-459188 > > apt-get source libkf5waylandclient5 > > sudo true && sudo apt-get --assume-no build-dep libkf5waylandclient5 > 2>/dev/null | grep '^ ' | tr ' ' '\n' | grep -v '^$' > build-dep.txt > sudo apt-get build-dep libkf5waylandclient5 > > pushd kwayland-5.98.0 > curl -L https://invent.kde.org/frameworks/kwayland/-/merge_requests/75.diff > | patch -p1 > dch -l +hotfix 'Fix KDE bug 459188' > dpkg-buildpackage -rfakeroot -uc -b > popd > > sudo dpkg -i > libkf5waylandclient5_5.98.0-0xneon+20.04+focal+release+build55+hotfix1_amd64. > deb kwayland-data_5.98.0-0xneon+20.04+focal+release+build55+hotfix1_all.deb > sudo apt remove $( ``` Following your instructions I too built the package. For me the problem persists as well. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 453522] Requires frameworks 5.94 but CMake doesn't indicate this
https://bugs.kde.org/show_bug.cgi?id=453522 --- Comment #4 from Jason Playne --- (In reply to Nate Graham from comment #2) > Sounds like you got this from the KDE nightly Flatpak repo or built it > yourself. Because the error makes sense: > > > QQmlComponent: Component is not ready > > file:///usr/lib/qml/org/kde/kirigami.2/PageRow.qml:878: Error: Error while > > loading page: qrc:/ui/MapPage.qml:110 Kirigami.LoadingPlaceholder is not a > > type > > That component was introduced quite recently, and it's not even in any > released software yet. It'll be released in Frameworks 5.94, which will be > out in a few days. So you would need to build your own runtime with > Frameworks 5.94 in it. > > In the meantime, we should bump the frameworks dependency version for > Filelight to 5.94 to make this clear Yes, that's correct. Nightly build from KDE flatpak repo. Thanks for looking into this bug! -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 453522] Filelight Flatpak does not search/scan when buttons clicked
https://bugs.kde.org/show_bug.cgi?id=453522 --- Comment #1 from Jason Playne --- Note, in the output the error lines (like below) appear on mouse click on the buttons QQmlComponent: Component is not ready file:///usr/lib/qml/org/kde/kirigami.2/PageRow.qml:878: Error: Error while loading page: qrc:/ui/MapPage.qml:110 Kirigami.LoadingPlaceholder is not a type -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 453522] Filelight Flatpak does not search/scan when buttons clicked
https://bugs.kde.org/show_bug.cgi?id=453522 Jason Playne changed: What|Removed |Added Platform|Other |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 453522] Filelight Flatpak does not search/scan when buttons clicked
https://bugs.kde.org/show_bug.cgi?id=453522 Jason Playne changed: What|Removed |Added Summary|Filelight Flatpak does not |Filelight Flatpak does not |search |search/scan when buttons ||clicked -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 453522] New: Filelight Flatpak does not search
https://bugs.kde.org/show_bug.cgi?id=453522
Bug ID: 453522
Summary: Filelight Flatpak does not search
Product: filelight
Version: 22.04.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: martin.sandsm...@kde.org
Reporter: ja...@jasonplayne.com
Target Milestone: ---
SUMMARY
I have the Filelight flatpak installed (v22.07.70 reported by the app). When I
click on any of the scan buttons on the home page, nothing happens.
Below is the info of the installed version from flatpak
```
$ flatpak info org.kde.filelight
Filelight - Filelight creates an interactive map of concentric segmented-rings
that helps visualize disk usage on your computer
ID: org.kde.filelight
Ref: app/org.kde.filelight/x86_64/master
Arch: x86_64
Branch: master
Version: 22.04.0
License: GPL-2.0+
Origin: kdeapps
Collection:
Installation: system
Installed: 544.8 kB
Runtime: org.kde.Platform/x86_64/5.15-21.08
Sdk: org.kde.Sdk/x86_64/5.15-21.08
Commit: c00f1b763ac9f0cb6ecf42165481d9b8027187b12cd319aae80c33b10bf638ad
Parent: a5eda1ab018e9deedb14cc133626abdf6566717d3972e7cfa720a874e719f298
Subject: Built on Wed Apr 27 21:47:10 CEST 2022
Date: 2022-04-27 19:47:30 +
```
STEPS TO REPRODUCE
1. Install filelight from flatpak
2. flatpak run -v org.kde.filelight
3. Click on the home page icons
OBSERVED RESULT
nothing happens
EXPECTED RESULT
Filelight scans my machine
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.24 (user edition)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Flatpak 1.12.4
ADDITIONAL INFORMATION
```
$ flatpak run -v org.kde.filelight
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/jason/.local/share/flatpak
F: Opening user flatpak installation at path /home/jason/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Skipping parental controls check for app/org.kde.filelight/x86_64/master
since parental controls are disabled globally
F: Opening user flatpak installation at path /home/jason/.local/share/flatpak
F:
/home/jason/.local/share/flatpak/runtime/org.kde.Platform/x86_64/5.15-21.08/00b47d52c670191fc9b6255750dab766fc3065db2be0c37ae9d3863aa2298d0f/files/lib32
does not exist
F: Cleaning up unused container id 2857023847
F: Cleaning up per-app-ID state for org.kde.filelight
F: Allocated instance id 3694568507
F: Add defaults in dir /org/kde/filelight/
F: Add locks in dir /org/kde/filelight/
F: Disallowing network access
F: Allowing host-fs access
F: Allowing wayland access
F: Allowing x11 access
F: Running 'bwrap --args 43 xdg-dbus-proxy --args=45'
F: Running 'bwrap --args 43 filelight'
libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (No such file
or directory)
qrc:/ui/main.qml:174:5: QML Connections: Implicitly defined onFoo properties in
Connections are deprecated. Use this syntax instead: function
onFoo() { ... }
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:32:15: QML
MenuItem: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:14:1:
QML ToolBarPageHeader: Binding loop detected for property "implicitWidth"
file:///usr/lib/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:270:5: QML
Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5: QML
Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 afte
[plasmashell] [Bug 449812] New: Plasma locked up after screen blank
https://bugs.kde.org/show_bug.cgi?id=449812 Bug ID: 449812 Summary: Plasma locked up after screen blank Product: plasmashell Version: 5.24.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ja...@jasonplayne.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.24.0) Qt Version: 5.15.3 Frameworks Version: 5.90.0 Operating System: Linux 5.16.7-051607-generic x86_64 Windowing System: Wayland Distribution: KDE neon User - 5.24 DrKonqi: 5.24.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I upgraded to the latest 5.24.0 release and walked away from my PC for 30-40 minutes - enough time for the power management to turn my monitor off. I came back to my computer and started using it and noticed the time was wrong,. I right with date/time taskbar applet and chose adjust date/time - i noticed the time was correct in there. I ran ntpdate-debian on the cli, the applet did not update its time shown. Launched applications did not appear on the task bar (spotify in my case) In a terminal I ran plasmashell --replace & back to a working task bar / time applet The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 3895] [New LWP 44763] [New LWP 44764] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7efcd45cfaff in __GI___poll (fds=0x7fff4f618af8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7efcd07244c0 (LWP 3879))] Thread 4 (Thread 0x7efc4d96b700 (LWP 44764)): #0 0x7efcd45cfaff in __GI___poll (fds=0x56024055b820, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efcd2e6b36e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efcd2e6b6f3 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efc58128f8a in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7efcd2e94ad1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efcd4440609 in start_thread (arg=) at pthread_create.c:477 #6 0x7efcd45dc293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7efc58ace700 (LWP 44763)): #0 __GI___libc_read (nbytes=16, buf=0x7efc58acdb20, fd=32) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=32, buf=0x7efc58acdb20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7efcd2eb3b2f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efcd2e6aebe in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efcd2e6b312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efcd2e6b4a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7efcd2e6b4f1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7efcd2e94ad1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7efcd4440609 in start_thread (arg=) at pthread_create.c:477 #9 0x7efcd45dc293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7efccebce700 (LWP 3895)): #0 0x7efcd45cfaff in __GI___poll (fds=0x7efcb8004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efcd2e6b36e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efcd2e6b4a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efcd4b9da0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7efcb8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7efcd4b41c9b in QEventLoop::exec(QFlags) (this=this@entry=0x7efccebcdbb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7efcd495b362 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7efcd54d2f4b in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7efcd495c543 in QThreadPrivate::start(void*) (arg=0x7efcd5556d80) at thread/qthread_unix.cpp:331 #8 0x7efcd4440609 in start_thread (arg=) at pthread_create.c:477 #9 0x7efcd45dc293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7efcd07244c0 (LWP 3879)): [KCrash Handler] #4 0x7efcd6d73fe1 in wl_map_insert_at (map=, flags=flags@entry=1, i=335, data=data@entry=0x0) at ../src/wayland-util.c:247 #5 0x7efcd6d6fe85 in proxy_destroy (proxy=0x56023f35d750) at ../src/wayland-client.c:503 #6 wl_proxy_destroy (proxy=0x56023f35d750) at ../src/wayland-client.c:534 #7 0x7efcd6e33e75 in QScopedPointerDeleter::cleanup(KWayland::Client::Buffer::Privat
[Discover] [Bug 444353] Discover crashes after attempting to get list of updates
https://bugs.kde.org/show_bug.cgi?id=444353 Jason Playne changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Jason Playne --- *** This bug has been marked as a duplicate of bug 444354 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444354] Discover crashes after attempting to load updates
https://bugs.kde.org/show_bug.cgi?id=444354 --- Comment #2 from Jason Playne --- *** Bug 444353 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444354] Discover crashes after attempting to load updates
https://bugs.kde.org/show_bug.cgi?id=444354 --- Comment #1 from Jason Playne --- Before I was able to get DrKonqi to generate back traces I also created https://bugs.kde.org/show_bug.cgi?id=444353 with more information -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444354] New: Discover crashes after attempting to load updates
https://bugs.kde.org/show_bug.cgi?id=444354 Bug ID: 444354 Summary: Discover crashes after attempting to load updates Product: Discover Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Updates (offline) Assignee: lei...@leinir.dk Reporter: ja...@jasonplayne.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover-update (5.23.1) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.14.14-051414-generic x86_64 Windowing System: Wayland Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.1 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: When opening discover, it automatically fetches updates (launched from cli, systray notifier or launched from kickoff) and then crashes The crash can be reproduced every time. -- Backtrace: Application: Discover Update (plasma-discover-update), signal: Segmentation fault [New LWP 40171] [New LWP 40172] [New LWP 40174] [New LWP 40177] [New LWP 40178] [New LWP 40193] [New LWP 40218] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f68e4304aff in __GI___poll (fds=0x7fffd1eeb7f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f68deceab80 (LWP 40170))] Thread 8 (Thread 0x7f689f7fe700 (LWP 40218)): #0 0x7f68e4304aff in __GI___poll (fds=0x5594338919c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f68e2d3f36e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f68e2d3f4a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f68d5c8299d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7f68e2d68ad1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f68e3719609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f68e4311293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f6891ccd700 (LWP 40193)): #0 __GI___libc_read (nbytes=16, buf=0x7f6891ccc810, fd=96) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=96, buf=0x7f6891ccc810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f68e2d87b2f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f68e2d3eebe in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f68e2d3f312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f68e2d3f4a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f68e48d45eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6874000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f68e487887b in QEventLoop::exec(QFlags) (this=this@entry=0x7f6891ccca20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f68e4692292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f68e469342c in QThreadPrivate::start(void*) (arg=0x5594336b2590) at thread/qthread_unix.cpp:329 #10 0x7f68e3719609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f68e4311293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f689ccc2700 (LWP 40178)): #0 __GI___libc_read (nbytes=16, buf=0x7f689ccc1810, fd=39) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=39, buf=0x7f689ccc1810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f68e2d87b2f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f68e2d3eebe in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f68e2d3f312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f68e2d3f4a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f68e48d45eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f688c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f68e487887b in QEventLoop::exec(QFlags) (this=this@entry=0x7f689ccc1a20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f68e4692292 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f68e469342c in QThreadPrivate::start(void*) (arg=0x5594335babc0) at thread/qthread_unix.cpp:329 #10 0x7f68e3719609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f68e4311293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f689700 (LWP 40177)): #0 0x7f68e4304aff in __GI___poll (fds=0x7f6898003da0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f68e
[Discover] [Bug 444353] New: Discover crashes after attempting to get list of updates
https://bugs.kde.org/show_bug.cgi?id=444353 Bug ID: 444353 Summary: Discover crashes after attempting to get list of updates Product: Discover Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ja...@jasonplayne.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover crashes after attempting to get list of updates STEPS TO REPRODUCE 1. Start Discover 2. 3. Watch it crash OBSERVED RESULT $ plasma-discover kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling. do not add a source twice QSharedPointer(0x564d9c1456d0) 0x564d9c47fad0 adding empty sources model QStandardItemModel(0x564d9c535330) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" kf.newstuff.core: Could not find category "Xfce Icon Theme" KNS error in "Icon Themes" : KNSCore::ConfigFileError "All categories are missing" QVariant(Invalid) invalid kns backend! "/etc/xdg/cgcicon.knsrc" because: "Invalid Icon Themes backend, contact your distributor." org.kde.plasma.libdiscover: Discarding invalid backend "cgcicon.knsrc" kns error "/etc/xdg/cgcicon.knsrc" "Invalid Icon Themes backend, contact your distributor." org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" took really long to fetch FlatpakBackend(0x564d9bec8f80) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 39619 KCrash: Arguments: /usr/bin/plasma-discover KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSocketNotifier: Invalid socket 103 and type 'Read', disabling... QSocketNotifier: Invalid socket 104 and type 'Read', disabling... [2]+ Stopped plasma-discover jason@jason-desktop:~ $ Unable to find file for pid 39619 expected at "kcrash-metadata/39619.ini" QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... EXPECTED RESULT Discover opens and does not crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (latest/up to date) (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION [ 7339.688721] plasma-discover[38470]: segfault at 59 ip 7f61018c2358 sp 7ffc0fbab340 error 4 in flatpak-backend.so[7f61018b7000+26000] [ 7339.688728] Code: ff ff ff 0f 1f 80 00 00 00 00 48 8b 44 24 08 48 8b 68 70 48 03 6d 10 eb 0d 66 0f 1f 84 00 00 00 00 00 48 83 c5 10 48 8b 45 00 <48> 3b 58 18 75 f2 48 8b 78 10 48 85 ff 0f 84 95 00 00 00 e8 a0 7d -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438264] New: Setting Screen Edge Action Crashes System Settings under Wayland
https://bugs.kde.org/show_bug.cgi?id=438264 Bug ID: 438264 Summary: Setting Screen Edge Action Crashes System Settings under Wayland Product: systemsettings Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Application: systemsettings5 (5.22.0) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.12.8-051208-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.22.0 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: 1. Log in with a Wayland Session. 2. Navigate to "Workspace Behaviour" and then "Screen Edges" 3. Set the action on the top left point (i was switching between No Action and one. 4. a) Watch the app crash. - or (and this was after a few attempts) watch the task bar flash between opaque and translucent Note: The setting is changed when you repeat the steps above. The more I tried to replicate, the more stable the settings app became Things that might be in effect * I have a dual monitor setup: Monitor 2 - Left - 2560x1440, Monitor 1 - right - 1920x180 * Existing (i.e. not brand new) Plasma/Kde app settings (not a new login) The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 22638] [New LWP 22639] [New LWP 22640] [New LWP 22641] [New LWP 22642] [New LWP 22643] [New LWP 22644] [New LWP 22645] [New LWP 22646] [New LWP 22647] [New LWP 22648] [New LWP 22649] [New LWP 22650] [New LWP 22651] [New LWP 22652] [New LWP 22653] [New LWP 22654] [New LWP 22655] [New LWP 22656] [New LWP 22657] [New LWP 22658] [New LWP 22659] [New LWP 22660] [New LWP 22661] [New LWP 22663] [New LWP 22664] [New LWP 22666] [New LWP 22667] [New LWP 22668] [New LWP 22670] [New LWP 22671] [New LWP 22672] [New LWP 22673] [New LWP 22678] [New LWP 22681] [New LWP 22685] [New LWP 22687] [New LWP 22689] [New LWP 22691] [New LWP 22693] [New LWP 22695] [New LWP 22697] [New LWP 22699] [New LWP 22701] [New LWP 22704] [New LWP 22729] [New LWP 22730] [New LWP 22732] [New LWP 22733] [New LWP 22734] [New LWP 22736] [New LWP 22737] [New LWP 22738] [New LWP 22739] [New LWP 22741] [New LWP 22791] [New LWP 22797] [New LWP 22799] [New LWP 22813] [New LWP 22817] [New LWP 22837] [New LWP 22841] [New LWP 22843] [New LWP 22931] [New LWP 22935] [New LWP 22939] [New LWP 22942] [New LWP 22967] [New LWP 22969] [New LWP 22971] [New LWP 22974] [New LWP 22976] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f725a446aff in __GI___poll (fds=0x7fff322c0068, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f7255e618c0 (LWP 22636))] Thread 73 (Thread 0x7f70b4bb9700 (LWP 22976)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561622ee35f4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561622ee35a0, cond=0x561622ee35c8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561622ee35c8, mutex=0x561622ee35a0) at pthread_cond_wait.c:647 #3 0x7f724dc0e60b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f724dc0e20b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f7258e48609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f725a453293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 72 (Thread 0x7f70b57fa700 (LWP 22974)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561622d3b3a0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561622d3b350, cond=0x561622d3b378) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561622d3b378, mutex=0x561622d3b350) at pthread_cond_wait.c:647 #3 0x7f724dc0e60b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f724dc0e20b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f7258e48609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f725a453293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 71 (Thread 0x7f709f7bf700 (LWP 22971)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56162312e330) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56162312e2e0, cond=0x56162312e308) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56162312e308, mutex=0x56162312e2e0) at pthread_cond_wait.c:647 #3 0x7f724dc0e60b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f724dc0e20b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.s
[kpat] [Bug 426200] Under wayland kpatience crashes on window resize
https://bugs.kde.org/show_bug.cgi?id=426200 --- Comment #13 from Jason Playne --- As an aside, when I captured the first strace in konsole, I went to select the whole text - and konsole crashed. - not sure if related or not -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] Under wayland kpatience crashes on window resize
https://bugs.kde.org/show_bug.cgi?id=426200 --- Comment #12 from Jason Playne --- Created attachment 131819 --> https://bugs.kde.org/attachment.cgi?id=131819&action=edit strace of kpat crashing -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] Under wayland kpatience crashes on window resize
https://bugs.kde.org/show_bug.cgi?id=426200 --- Comment #11 from Jason Playne --- For me it still crashes. Using neons current build, the flathub version and the kdeapps (flatpak) version all crash. the time it takes to crash seems variable. sometimes it is nearly instant, others takes a while. I get feeling that the larger the screen the more likely the crash (I have a 2k monitor, I feel that when the window is larger the crash comes quicker). When I get the crash, I also get an artefact on the screen, it's ~50% opaque copy of the window that is not selectable. For me, to reproduce it this time. * open kpat (any source, either cli or launcher) * grab a corner and resize (really shake the mouse around) * * profit! I grabbed an strace of the neon version too -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] Under wayland kpatience crashes on window resize
https://bugs.kde.org/show_bug.cgi?id=426200 Jason Playne changed: What|Removed |Added Summary|Under wayland kpatience |Under wayland kpatience |crashes on window |crashes on window resize |resize/launch | -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] Under wayland kpatience crashes on window resize/launch
https://bugs.kde.org/show_bug.cgi?id=426200 --- Comment #3 from Jason Playne --- For Reference, This is the output doing the same sort of thing under an X11 plasma5 session $ kpat kf.coreaddons: "2552-1318-background" is too large to be cached. kf.coreaddons: "2560-1322-background" is too large to be cached. kf.coreaddons: Unable to free up memory for "1925-819-background" (but it did not crash) -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] Under wayland kpatience crashes on window resize/launch
https://bugs.kde.org/show_bug.cgi?id=426200 --- Comment #2 from Jason Playne --- Hi Albert, To trigger this error, I run kpat from the CLI resize the window. $ kpat kf.coreaddons: "2552-1318-background" is too large to be cached. kf.coreaddons: "2552-1308-background" is too large to be cached. kf.coreaddons: "2552-1212-background" is too large to be cached. The Wayland connection broke. Did the Wayland compositor die? KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kpat path = /usr/games pid = 690340 KCrash: Arguments: /usr/games/kpat KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped kpat The gap in the second one is when I was resizing the window to make it crash $ kpat kf.coreaddons: "2552-1318-background" is too large to be cached. kf.coreaddons: "2552-1308-background" is too large to be cached. kf.coreaddons: Unable to free up memory for "2552-1134-background" The Wayland connection broke. Did the Wayland compositor die? KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kpat path = /usr/games pid = 690992 KCrash: Arguments: /usr/games/kpat KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] New: Under wayland kpatience crashes on window resize/launch
https://bugs.kde.org/show_bug.cgi?id=426200 Bug ID: 426200 Summary: Under wayland kpatience crashes on window resize/launch Product: kpat Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: ja...@jasonplayne.com CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (20.08.1) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.6-050806-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I was wanting to play, so I launch the app and when to move the window I tried a few times and it is some variant of: launch app, double click title or resize window that causes the app to crash - Unusual behavior I noticed: after crash there is a 50% translucent ghost of kpatience covering my desktop. The crash can be reproduced every time. -- Backtrace: Application: KPatience (kpat), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f0bd10d9859 in __GI_abort () at abort.c:79 #6 0x7f0bd1665b69 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=, msg=) at global/qlogging.cpp:893 #8 0x7f0bcc70a8b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7f0bcc71b0de in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #10 0x7f0bd18b3550 in doActivate (sender=0x557027e0c1b0, signal_index=3, argv=0x7ffef3f49cb0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #11 0x7f0bd18adaf7 in QMetaObject::activate (sender=sender@entry=0x557027e0c1b0, m=m@entry=0x7f0bd1b59ba0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffef3f49cb0) at kernel/qobject.cpp:3930 #12 0x7f0bd18b6d95 in QSocketNotifier::activated (this=this@entry=0x557027e0c1b0, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141 #13 0x7f0bd18b70f1 in QSocketNotifier::event (this=0x557027e0c1b0, e=0x7ffef3f49f70) at kernel/qsocketnotifier.cpp:266 #14 0x7f0bd2462cc3 in QApplicationPrivate::notify_helper (this=this@entry=0x557027d900f0, receiver=receiver@entry=0x557027e0c1b0, e=e@entry=0x7ffef3f49f70) at kernel/qapplication.cpp:3685 #15 0x7f0bd246bf40 in QApplication::notify (this=0x7ffef3f4a2f0, receiver=0x557027e0c1b0, e=0x7ffef3f49f70) at kernel/qapplication.cpp:3431 #16 0x7f0bd187d78a in QCoreApplication::notifyInternal2 (receiver=0x557027e0c1b0, event=0x7ffef3f49f70) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #17 0x7f0bd18d6de5 in socketNotifierSourceDispatch (source=0x557027dc34d0) at kernel/qeventdispatcher_glib.cpp:107 #18 0x7f0bcf41bfbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f0bcf41c240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f0bcf41c2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f0bd18d61e2 in QEventDispatcherGlib::processEvents (this=0x557027e0be80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f0bd187c24b in QEventLoop::exec (this=this@entry=0x7ffef3f4a180, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #23 0x7f0bd1884296 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #24 0x557026bf1d11 in ?? () #25 0x7f0bd10db0b3 in __libc_start_main (main=0x557026bf0010, argc=3, argv=0x7ffef3f4a468, init=, fini=, rtld_fini=, stack_end=0x7ffef3f4a458) at ../csu/libc-start.c:308 #26 0x557026bf29ce in ?? () [Inferior 1 (process 508358) detached] Possible duplicates by query: bug 424911, bug 423951, bug 423222, bug 423132, bug 422433. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421047] New: Wayland - Crash on Wallpaper settings (or mesa upgrade)
https://bugs.kde.org/show_bug.cgi?id=421047 Bug ID: 421047 Summary: Wayland - Crash on Wallpaper settings (or mesa upgrade) Product: plasmashell Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ja...@jasonplayne.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.6.7-050607-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: While I was waiting for discover to upload to the mesa 20.1 RC1 release I was fiddling with my wallpaper settings. I have a dual monitor setup (2x1080p) with 1 hdmi and one DP->DVI monitor - Unusual behavior I noticed: The screen flickered (like it was attempting to recover?) and then crashed the desktop session crashed with only my apps left open. The wallpaper settings page is no longer around. - Custom settings of the application: I am using a PPA deb http://ppa.launchpad.net/ernstp/mesarc/ubuntu bionic main for mesa stable releases -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd8964c800 (LWP 9293))] Thread 59 (Thread 0x7fdc377fe700 (LWP 24712)): #0 0x7fdd7fdb19f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55aae6c744f4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fdd7fdb19f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55aae6c744a0, cond=0x55aae6c744c8) at pthread_cond_wait.c:502 #2 0x7fdd7fdb19f3 in __pthread_cond_wait (cond=0x55aae6c744c8, mutex=0x55aae6c744a0) at pthread_cond_wait.c:655 #3 0x7fdd8312ee5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55aae6c744a0) at thread/qwaitcondition_unix.cpp:146 #4 0x7fdd8312ee5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55aae50bb630, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fdd8312efd9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55aae50bb638, mutex=mutex@entry=0x55aae50bb630, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fdd87231233 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55aae50bb628) at scenegraph/qsgthreadedrenderloop.cpp:255 #7 0x7fdd87231233 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55aae50bb590) at scenegraph/qsgthreadedrenderloop.cpp:905 #8 0x7fdd87231691 in QSGRenderThread::run() (this=0x55aae50bb590) at scenegraph/qsgthreadedrenderloop.cpp:1000 #9 0x7fdd831288ac in QThreadPrivate::start(void*) (arg=0x55aae50bb590) at thread/qthread_unix.cpp:342 #10 0x7fdd7fdab6db in start_thread (arg=0x7fdc377fe700) at pthread_create.c:463 #11 0x7fdd82a1d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 58 (Thread 0x7fdc37fff700 (LWP 24711)): #0 0x7fdd7fdb19f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55aae7019e88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fdd7fdb19f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55aae7019e38, cond=0x55aae7019e60) at pthread_cond_wait.c:502 #2 0x7fdd7fdb19f3 in __pthread_cond_wait (cond=0x55aae7019e60, mutex=0x55aae7019e38) at pthread_cond_wait.c:655 #3 0x7fdd6916e57b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x in () Thread 57 (Thread 0x7fdc4b365700 (LWP 24710)): #0 0x7fdd7fdb19f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55aae6f8f1ec) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fdd7fdb19f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55aae6f8f198, cond=0x55aae6f8f1c0) at pthread_cond_wait.c:502 #2 0x7fdd7fdb19f3 in __pthread_cond_wait (cond=0x55aae6f8f1c0, mutex=0x55aae6f8f198) at pthread_cond_wait.c:655 #3 0x7fdd6916e57b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x in () Thread 56 (Thread 0x7fdc494ff700 (LWP 24703)): #0 0x7fdd82a0c0b4 in __GI___libc_read (fd=58, buf=0x7fdc494feb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fdd7cb662b0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdd7cb210b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdd7cb21570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdd7cb216dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdd8337744b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fdc300160f0, flags=...) at kernel/
[plasmashell] [Bug 413166] Plasma crash on after logging in
https://bugs.kde.org/show_bug.cgi?id=413166 Jason Playne changed: What|Removed |Added Platform|unspecified |Neon Packages --- Comment #1 from Jason Playne --- rebooted and everything works as intended -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413166] New: Plasma crash on after logging in
https://bugs.kde.org/show_bug.cgi?id=413166 Bug ID: 413166 Summary: Plasma crash on after logging in Product: plasmashell Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ja...@jasonplayne.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-050307-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I had just started my PC (cold boot) like I have done a couple of times now. Discord, Steam, Firefox all running by default The Taskbar is not present (I think that is what has failed) will reboot and try again -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f524f3f3800 (LWP 9023))] Thread 25 (Thread 0x7f52017fa700 (LWP 9993)): #0 0x7f52461779f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556912c31500) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52461779f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x556912c314b0, cond=0x556912c314d8) at pthread_cond_wait.c:502 #2 0x7f52461779f3 in __pthread_cond_wait (cond=0x556912c314d8, mutex=0x556912c314b0) at pthread_cond_wait.c:655 #3 0x7f5249246b0b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x556912c314b0) at thread/qwaitcondition_unix.cpp:146 #4 0x7f5249246b0b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x556912963ad0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5249246e19 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x556912963ad8, mutex=mutex@entry=0x556912963ad0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f524d265ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x556912963ac8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7f524d265ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x556912963a50) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f524d2662fa in QSGRenderThread::run() (this=0x556912963a50) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f524923fb72 in QThreadPrivate::start(void*) (arg=0x556912963a50) at thread/qthread_unix.cpp:360 #10 0x7f52461716db in start_thread (arg=0x7f52017fa700) at pthread_create.c:463 #11 0x7f5248b3c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f51b4539700 (LWP 9992)): #0 0x7f52461779f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55691408b93c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52461779f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55691408b8e8, cond=0x55691408b910) at pthread_cond_wait.c:502 #2 0x7f52461779f3 in __pthread_cond_wait (cond=0x55691408b910, mutex=0x55691408b8e8) at pthread_cond_wait.c:655 #3 0x7f52295bbccb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f52295bb8b7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f52461716db in start_thread (arg=0x7f51b4539700) at pthread_create.c:463 #6 0x7f5248b3c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f5201ffb700 (LWP 9304)): #0 0x7f52461779f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556912ffcd60) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52461779f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x556912ffcd10, cond=0x556912ffcd38) at pthread_cond_wait.c:502 #2 0x7f52461779f3 in __pthread_cond_wait (cond=0x556912ffcd38, mutex=0x556912ffcd10) at pthread_cond_wait.c:655 #3 0x7f52295bbccb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f52295bb8b7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f52461716db in start_thread (arg=0x7f5201ffb700) at pthread_create.c:463 #6 0x7f5248b3c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f52027fc700 (LWP 9303)): #0 0x7f52461779f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556912ffcd60) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52461779f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x556912ffcd10, cond=0x556912ffcd38) at pthread_cond_wait.c:502 #2 0x7f52461779f3 in __pthread_cond_wait (cond=0x556912ffcd38, mutex=0x556912ffcd10) at pthread_cond_wait.c:655 #3 0x7f52295bbccb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f52295bb8b7 in () at /usr/lib/x86_64-linux-gnu/dri/radeo
[kwin] [Bug 392820] wayland session crash back to sddm during load
https://bugs.kde.org/show_bug.cgi?id=392820 --- Comment #3 from Jason Playne --- The screenshot contains the text: *** Error in `/usr/bin/kwin_wayland': double free or corruption (!prev): 0x024e2ea0 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392820] wayland session crash back to sddm during load
https://bugs.kde.org/show_bug.cgi?id=392820 Jason Playne changed: What|Removed |Added Attachment #111879|0 |1 is obsolete|| --- Comment #2 from Jason Playne --- Created attachment 111881 --> https://bugs.kde.org/attachment.cgi?id=111881&action=edit screen shot of crash 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392820] wayland session crash back to sddm during load
https://bugs.kde.org/show_bug.cgi?id=392820 --- Comment #1 from Jason Playne --- Created attachment 111880 --> https://bugs.kde.org/attachment.cgi?id=111880&action=edit screen shot of crash 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392820] New: wayland session crash back to sddm during load
https://bugs.kde.org/show_bug.cgi?id=392820 Bug ID: 392820 Summary: wayland session crash back to sddm during load Product: kwin Version: 5.12.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Created attachment 111879 --> https://bugs.kde.org/attachment.cgi?id=111879&action=edit screen shot of crash 1 So, it seems that I may have a similar problem to others that have reported a crash in kwin_wayland. what I see is logging into a wayland session, the apps that were running last time starting to load and then crash back SDDM after about 10-15 seconds. What I do have is a couple of screenshots from seats 2 and 3 which seem to contain the crash information (I cannot find this info anywhere else (kern/syslog/journalctl/.xsession-errors), but I do confess in not knowing what other place to look for it). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389184] Crash on Upgrade in UpdateTransaction::isProgressing()
https://bugs.kde.org/show_bug.cgi?id=389184 --- Comment #2 from Jason Playne --- (In reply to Aleix Pol from comment #1) > The backtrace looks mangled. Is there any way for you to reproduce? > If you are on neon, how come it's 5.11.0 instead of the last stable one? There is a good chance this was an upgrade attempt from 5.11 to 5.12. I have since been unable to reproduce :( Each package upgrade since using discover has worked. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389184] New: Crash on Upgrade
https://bugs.kde.org/show_bug.cgi?id=389184 Bug ID: 389184 Summary: Crash on Upgrade Product: Discover Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Application: plasma-discover (5.11.0) Qt Version: 5.9.3 Frameworks Version: 5.42.0 Operating System: Linux 4.13.0-26-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: I double clicked the "you have updated" tray icon. I clicked update It looked as if the tool did the "apt update" process and was about to start the apt upgrade process. No dialog for "enter admin password" appeared before the crash -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f90e1d0c8c0 (LWP 30936))] Thread 16 (Thread 0x7f909a7fc700 (LWP 30958)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f90b723d3cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7f90b723d2e8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7f90d9d546ba in start_thread (arg=0x7f909a7fc700) at pthread_create.c:333 #4 0x7f90dd1ad41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f909affd700 (LWP 30955)): #0 0x7f90d7ecc8d3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f90d7ecd2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f90d7ecd49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9016cb in QEventDispatcherGlib::processEvents (this=0x7f908c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f90ddd79e2a in QEventLoop::exec (this=this@entry=0x7f909affcd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f90ddba28f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f90ddba7709 in QThreadPrivate::start (arg=0x47bd690) at thread/qthread_unix.cpp:368 #7 0x7f90d9d546ba in start_thread (arg=0x7f909affd700) at pthread_create.c:333 #8 0x7f90dd1ad41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f90a0ff4700 (LWP 30952)): #0 0x7f90d7f11a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f90d7ecc7f7 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f90d7ecd2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f90d7ecd49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9016cb in QEventDispatcherGlib::processEvents (this=0x7f90940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f90ddd79e2a in QEventLoop::exec (this=this@entry=0x7f90a0ff3d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f90ddba28f4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f90ddba7709 in QThreadPrivate::start (arg=0x28feac0) at thread/qthread_unix.cpp:368 #8 0x7f90d9d546ba in start_thread (arg=0x7f90a0ff4700) at pthread_create.c:333 #9 0x7f90dd1ad41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f90add8b700 (LWP 30951)): #0 0x7f90dd19d27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f90d7f106f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f90d7ecce74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f90d7ecd330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f90d7ecd49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9016cb in QEventDispatcherGlib::processEvents (this=0x7f909c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f90ddd79e2a in QEventLoop::exec (this=this@entry=0x7f90add8ad00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f90ddba28f4 in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f90ddba7709 in QThreadPrivate::start (arg=0x289e290) at thread/qthread_unix.cpp:368 #9 0x7f90d9d546ba in start_thread (arg=0x7f90add8b700) at pthread_create.c:333 #10 0x7f90dd1ad41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f90ae9de700 (LWP 30948)): #0 0x7f90dd19d27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f90d7f106f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f90d7ecce74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f90d7ecd330 in ?? () from /lib/x8
[plasmashell] [Bug 382532] plasmashell has a crash that removes window decorations on alt tab
https://bugs.kde.org/show_bug.cgi?id=382532 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382532] New: plasmashell has a crash that removes window decorations on alt tab
https://bugs.kde.org/show_bug.cgi?id=382532 Bug ID: 382532 Summary: plasmashell has a crash that removes window decorations on alt tab Product: plasmashell Version: 5.10.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: ja...@jasonplayne.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106753 --> https://bugs.kde.org/attachment.cgi?id=106753&action=edit crash log Application: plasmashell (5.10.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.0-041200-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: Alt Tab between windows. Once the crash occurs, I can no longer change which window is on top. Panel is responsive, can bring up the Application Launcher (start/k menu?) system tray icons are responsive I have experienced this crash several times in the last few days. I have Phpstorm (and the jetbrains toolbox), chrome, konsole, spotify and discord open when the crashes occur. The crash can be reproduced sometimes. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380371] Discover Search Crash
https://bugs.kde.org/show_bug.cgi?id=380371 Jason Playne changed: What|Removed |Added CC||ja...@jasonplayne.com --- Comment #2 from Jason Playne --- I have experienced a very similar problem. Searching for "calculator" causes a crash every time (some results are shown). -- You are receiving this mail because: You are watching all bug changes.
