[kstars] [Bug 426899] kstars segmentation fault in doActivate when starting
https://bugs.kde.org/show_bug.cgi?id=426899 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Matt Fagnani --- (In reply to Jasem Mutlaq from comment #2) > Please check against KStars 3.6.1 and report back. This problem was related to compiling kstars and some other Qt programs with link-time optimization (LTO) enabled and was fixed as described at https://bugzilla.redhat.com/show_bug.cgi?id=1881915 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459837] kwin_wayland crashed when moving the cursor to the top-left corner of the screen when the splash screen was shown during login
https://bugs.kde.org/show_bug.cgi?id=459837 --- Comment #2 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #1) > Can you verify whether the crash is reproducible in 5.26? This problem didn't happen when I tried to reproduce it a few times with Plasma 5.25.90 when booting a Fedora Rawhide/38 KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20220927.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=2067704 on bare metal from a USB flash drive. Plasma 5.25.90 might not be affected or the problem might not have happened because of some difference between my Fedora 37 installation and the Fedora Rawhide live image. I'll comment again if I see this problem with the Plasma 5.26 branch. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459837] New: kwin_wayland crashed when moving the cursor to the top-left corner of the screen when the splash screen was shown during login
https://bugs.kde.org/show_bug.cgi?id=459837 Bug ID: 459837 Summary: kwin_wayland crashed when moving the cursor to the top-left corner of the screen when the splash screen was shown during login Classification: Plasma Product: kwin Version: 5.25.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- SUMMARY I logged into Plasma 5.25.5 on Wayland from sddm on Wayland in a Fedora 37 KDE Plasma installation. I moved the cursor to the top-left corner of the screen when the splash screen was shown during login. The top-left of the screen turned blue, and the splash screen became smaller with a blurred border around it. The screen went black, with only a text cursor _ shown. Plasma started after several seconds. coredumpctl gdb showed that kwin_wayland had crashed with a failed assertion in libepoxy Couldn't find current GLX or EGL context. as shown in frames #4 and 5 of the trace. Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7f43a3fa4980 (LWP 1414))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f43a2aa9d33 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7f43a2a59aa6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7f43a2a437fc in __GI_abort () at abort.c:79 #4 0x7f43a2a4371b in __assert_fail_base (fmt=0x7f43a2bb79c0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f43a476e750 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=0x7f43a476e841 "../src/dispatch_common.c", line=872, function=) at assert.c:92 #5 0x7f43a2a52656 in __GI___assert_fail (assertion=assertion@entry=0x7f43a476e750 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=file@entry=0x7f43a476e841 "../src/dispatch_common.c", line=line@entry=872, function=function@entry=0x7f43a476eca0 <__PRETTY_FUNCTION__.0.lto_priv.0> "epoxy_get_proc_address") at assert.c:101 #6 0x7f43a474a90f in epoxy_get_proc_address (name=0x7f43a4755059 "glDeleteFramebuffers") at ../src/dispatch_common.c:872 #7 0x7f43a46f899a in epoxy_glDeleteFramebuffers_resolver () at src/gl_generated_dispatch.c:81572 #8 epoxy_glDeleteFramebuffers_global_rewrite_ptr (n=1, framebuffers=0x7ffc934e90d0) at src/gl_generated_dispatch.c:49446 #9 0x55ff13f431b9 in operator() (__closure=0x55ff15ddf0d0) at /usr/src/debug/kwin-5.25.5-1.fc37.x86_64/src/effects/screentransform/screentransform.cpp:74 #10 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::ScreenTransformEffect::addScreen(KWin::EffectScreen*):: >::call (arg=, f=...) --Type for more, q to quit, c to continue without paging--c at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #11 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #12 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55ff15ddf0c0, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #13 0x7f43a3cdb9a6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc934e91b0, r=, this=0x55ff15ddf0c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x55ff15d80b00, signal_index=7, argv=0x7ffc934e91b0) at kernel/qobject.cpp:3919 #15 0x7f43a3cdb9a6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc934e9280, r=, this=0x55ff15d737a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate(QObject*, int, void**) (sender=0x55ff15157f70, signal_index=8, argv=0x7ffc934e9280) at kernel/qobject.cpp:3919 #17 0x7f43a3cd6927 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55ff15157f70, m=m@entry=0x7f43a531b720 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at kernel/qobject.cpp:3979 #18 0x7f43a4f85437 in KWin::Output::aboutToChange() (this=this@entry=0x55ff15157f70) at /usr/src/debug/kwin-5.25.5-1.fc37.x86_64/redhat-linux-build/src/kwin_autogen/EWIEGA46WW/moc_output.cpp:397 #19 0x7f438fbe3c95 in KWin::DrmOutput::applyQueuedChanges(KWin::OutputConfiguration const&) (config=..., this=0x55ff15157f70) at
[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 --- Comment #6 from Matt Fagnani --- The cursor appeared normally and selected the correct regions in GNOME Boxes QEMU/KVM VMs with 3D acceleration enabled using Fedora-KDE-Live-x86_64-Rawhide-20220806.n.0.iso https://koji.fedoraproject.org/koji/buildinfo?buildID=2042542 which had Plasma 5.25.4 and Mesa 22.1.5. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 456535] kontact crashed when closing
https://bugs.kde.org/show_bug.cgi?id=456535 --- Comment #1 from Matt Fagnani --- Created attachment 150510 --> https://bugs.kde.org/attachment.cgi?id=150510=edit valgrind log when running and closing kontact When I ran kontact in konsole, I got the following output all but the first line of which happened when closing it. Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls") kf.xmlgui: 0x31bb9170 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x31b6b048 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x31bdace0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x31ba27e8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x2ef98678 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x31b8a878 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x31b15598 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. kf.xmlgui: 0x31b532c8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. I ran valgrind --log-file=valgrind_kontact_1.txt kontact in a Fedora 36 KDE Plasma installation and closed it. The valgrind log showed use of uninitialized variables repeatedly such as the following. ==2302== Conditional jump or move depends on uninitialised value(s) ==2302==at 0x12BDC9F0: re2::SparseSetT::contains(int) const (sparse_set.h:227) ==2302==by 0x12BFCD19: UnknownInlinedFun (sparse_set.h:156) ==2302==by 0x12BFCD19: UnknownInlinedFun (sparse_set.h:133) ==2302==by 0x12BFCD19: UnknownInlinedFun (prog.cc:138) ==2302==by 0x12BFCD19: UnknownInlinedFun (prog.cc:136) ==2302==by 0x12BFCD19: re2::Prog::Optimize() (prog.cc:241) ==2302==by 0x12BE159B: re2::Compiler::Finish(re2::Regexp*) (compile.cc:1172) ==2302==by 0x12BE6898: re2::Compiler::Compile(re2::Regexp*, bool, long) (compile.cc:1156) ==2302==by 0x12C08E47: re2::RE2::Init(re2::StringPiece const&, re2::RE2::Options const&) (re2.cc:223) ==2302==by 0x12C099D3: re2::RE2::RE2(std::__cxx11::basic_string, std::allocator > const&) (re2.cc:118) ==2302==by 0x794DB2A: StringMismatch (gpu_control_list.cc:112) ==2302==by 0x794DB2A: gpu::(anonymous namespace)::StringMismatch(std::__cxx11::basic_string, std::allocator > const&, char const*) [clone .part.0] (gpu_control_list.cc:119) ==2302==by 0x794E2A5: StringMismatch (gpu_control_list.cc:316) ==2302==by 0x794E2A5: gpu::GpuControlList::GLStrings::Contains(gpu::GPUInfo const&) const (gpu_control_list.cc:316) ==2302==by 0x7950653: gpu::GpuControlList::Conditions::Contains(gpu::GpuControlList::OsType, std::__cxx11::basic_string, std::allocator > const&, gpu::GPUInfo const&) const (gpu_control_list.cc:521) ==2302==by 0x7950A75: gpu::GpuControlList::Entry::Contains(gpu::GpuControlList::OsType, std::__cxx11::basic_string, std::allocator > const&, gpu::GPUInfo const&) const (gpu_control_list.cc:536) ==2302==by 0x7951665: gpu::GpuControlList::MakeDecision(gpu::GpuControlList::OsType, std::__cxx11::basic_string, std::allocator > const&, gpu::GPUInfo const&, unsigned int) (gpu_control_list.cc:667) ==2302==by 0x796242C: gpu::ComputeGpuFeatureInfo(gpu::GPUInfo const&, gpu::GpuPreferences const&, base::CommandLine*, bool*) (gpu_util.cc:588) ==2302== ==2302== Use of uninitialised value of size 8 ==2302==at 0x12BDC9F2: re2::SparseSetT::contains(int) const (sparse_set.h:227) ==2302==by 0x12BFCD19: UnknownInlinedFun (sparse_set.h:156) ==2302==by 0x12BFCD19: UnknownInlinedFun (sparse_set.h:133) ==2302==by 0x12BFCD19: UnknownInlinedFun (prog.cc:138) ==2302==by 0x12BFCD19: UnknownInlinedFun (prog.cc:136) ==2302==by 0x12BFCD19: re2::Prog::Optimize() (prog.cc:241) ==2302==by 0x12BE159B: re2::Compiler::Finish(re2::Regexp*) (compile.cc:1172) ==2302==by 0x12BE6898: re2::Compiler::Compile(re2::Regexp*, bool, long) (compile.cc:1156) ==2302==by 0x12C08E47: re2::RE2::Init(re2::StringPiece const&, re2::RE2::Options const&) (re2.cc:223) ==2302==by 0x12C099D3: re2::RE2::RE2(std::__cxx11::basic_string, std::allocator > const&) (re2.cc:118) ==2302==by 0x794DB2A: StringMismatch (gpu_control_list.cc:112) ==2302==by 0x794DB2A: gpu::(anonymous namespace)::StringMismatch(std::__cxx11::basic_string, std::allocator > const&, char const*) [clone .part.0] (gpu_control_list.cc
[kontact] [Bug 456535] New: kontact crashed when closing
https://bugs.kde.org/show_bug.cgi?id=456535 Bug ID: 456535 Summary: kontact crashed when closing Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- Application: kontact (5.20.2 (22.04.2)) Qt Version: 5.15.4 Frameworks Version: 5.96.0 Operating System: Linux 5.19.0-0.rc5.20220708gite8a4e1c1bb69.44.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma Prerelease) DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: I booted a Fedora 36 KDE Plasma installation. I started Plasma 5.25.2 on Wayland. I started GNOME Boxes. I booted a Fedora Rawhide QEMU/KVM VM in GNOME Boxes with 3 GiB RAM, EFI enabled, and 3D acceleration enabled from the image Fedora-KDE-Live-x86_64-Rawhide-20220709.n.0.iso https://koji.fedoraproject.org/koji/buildinfo?buildID=1998908 I started kontact 22.04.2 from the Application Launcher menu. I selected Help > About Kontact, then OK. I closed kontact (by clicking x at the top right corner). Kontact segmentation faulted when closing. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f4163bb3d67 in KMail::UnityServiceManager::initListOfCollection (this=0x558063823f50) at /usr/src/debug/kmail-22.04.1-1.fc37.x86_64/src/unityservicemanager.cpp:106 #5 0x7f41edadb216 in QtPrivate::QSlotObjectBase::call (a=0x7ffef85cc320, r=, this=0x5580638247c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x558063815b30, signal_index=16, argv=0x7ffef85cc320) at kernel/qobject.cpp:3886 #7 0x7f41edad6247 in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=13, argv=argv@entry=0x7ffef85cc320) at kernel/qobject.cpp:3946 #8 0x7f41806df8de in Akonadi::Monitor::collectionAdded (this=, _t1=..., _t2=...) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/redhat-linux-build/src/core/KF5AkonadiCore_autogen/include/moc_monitor.cpp:955 #9 0x7f41806f1d57 in Akonadi::MonitorPrivate::emitToListeners (signal=, this=0x558063815b50) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/monitor_p.h:390 #10 Akonadi::MonitorPrivate::emitCollectionNotification (this=0x558063815b50, msg=..., col=..., par=..., dest=...) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/monitor_p.cpp:1115 #11 0x7f41806ee565 in Akonadi::MonitorPrivate::emitNotification (this=0x558063815b50, msg=...) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/monitor_p.cpp:520 #12 0x7f41806b2592 in Akonadi::ChangeRecorderPrivate::emitNotification (this=0x558063815b50, msg=...) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/changerecorder_p.cpp:216 #13 0x7f41806ecf35 in Akonadi::MonitorPrivate::flushPipeline (this=0x558063815b50) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/monitor_p.cpp:969 #14 0x7f41806ed8ed in Akonadi::MonitorPrivate::dataAvailable (this=0x558063815b50) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/monitor_p.cpp:978 #15 0x7f41edadb216 in QtPrivate::QSlotObjectBase::call (a=0x7ffef85cc600, r=, this=0x5580638073b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x558063815980, signal_index=3, argv=0x7ffef85cc600) at kernel/qobject.cpp:3886 #17 0x7f41edadb39f in doActivate (sender=0x7f41b000f520, signal_index=6, argv=0x7ffef85cc730) at kernel/qobject.cpp:3898 #18 0x7f41edad6247 in QMetaObject::activate (sender=sender@entry=0x7f41b000f520, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffef85cc730) at kernel/qobject.cpp:3946 #19 0x7f41eef88d29 in KJob::result (this=this@entry=0x7f41b000f520, _t1=, _t1@entry=0x7f41b000f520, _t2=...) at /usr/src/debug/kf5-kcoreaddons-5.96.0-1.fc37.x86_64/redhat-linux-build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #20 0x7f41eef8e34b in KJob::finishJob (this=0x7f41b000f520, emitResult=) at /usr/src/debug/kf5-kcoreaddons-5.96.0-1.fc37.x86_64/src/lib/jobs/kjob.cpp:98 #21 0x7f41eef8e3fe in KJob::kill (this=0x7f41b000f520, verbosity=verbosity@entry=KJob::EmitResult) at /usr/src/debug/kf5-kcoreaddons-5.96.0-1.fc37.x86_64/src/lib/jobs/kjob.cpp:118 #22 0x7f418070d0e1 in Akonadi::SessionPrivate::clear (this=0x5580637fa210, forceReconnect=forceReconnect@entry=false) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/session.cpp:440 #23 0x7f418070d246 in Akonadi::Session::~Session (this=, this=) at /usr/src/debug/kf5-akonadi-server-22.04.3-1.fc37.x86_64/src/core/session.cpp:396 #24
[kwin] [Bug 455630] kwin_wayland crashed in VMs using the llvmpipe graphics driver
https://bugs.kde.org/show_bug.cgi?id=455630 --- Comment #2 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #1) > > The problem might involve the llvmpipe driver. > > Indeed, this looks something something llvmpipy. > > The crash occurs when kwin calls glClear() over here > https://invent.kde.org/plasma/kwin/-/blob/ > 4699f8c0e2be8edce24133fb2678ef9f7a07cafa/src/plugins/screencast/ > windowscreencastsource.cpp Thanks. I reported this problem to Mesa at https://gitlab.freedesktop.org/mesa/mesa/-/issues/6710 and Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=2098535 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 --- Comment #1 from Matt Fagnani --- Created attachment 149984 --> https://bugs.kde.org/attachment.cgi?id=149984=edit A screenshot of the inverted cursor over the All Applications item but the Favorites item was highlighted in the Application Launcher menu The first line in my report should have started: The cursor in Plasma 5.25.0 was inverted so that it pointed down and to the left instead of up and to the left... I'm attaching a screenshot showing the inverted cursor over the All Applications item but the Favorites item being highlighted instead in the Application Launcher menu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455684] New: The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 Bug ID: 455684 Summary: The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled Product: kwin Version: 5.25.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- SUMMARY The cursor in Plasma 5.25.0 was inverted so that it pointed down and to the left instead of up and to the right in Fedora Rawhide/37 GNOME Boxes QEMU-KVM VMs using with 3D acceleration enabled using the virgl driver from mesa 22.1.2 and virtio gpu. The selected region was above the cursor by about 1-2 times the height of the cursor every time. In order to select and open the Application Launcher menu, the cursor had to be moved below the bottom-left of the screen. When trying to select menu items or other things in the Application Launcher menu, Firefox, Konsole, System Settings, kinfocenter, I needed to put the cursor about 1-2 cursor heights below the item to be selected. STEPS TO REPRODUCE 1. Boot a Fedora 36 KDE Plasma installation 2. Log in to Plasma on Wayland 3. install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes 4. Download Fedora-KDE-Live-x86_64-Rawhide-20220617.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=1986249 5. Start GNOME Boxes 6. Start a QEMU-KVM VM with Fedora-KDE-Live-x86_64-Rawhide-20220617.n.0.iso in GNOME Boxes with 3 GB RAM, 3D acceleration enabled, and EFI enabled 7. Move the cursor around in Plasma with the mouse. The cursor is inverted. 8. Try to select the Application Launcher menu button at the bottom-left of the screen normally. The cursor must be moved below the bottom-left of the screen to select Application Launcher menu button to open it. 9. Try to select the menu items or icons normally in the Application launcher menu. The cursor only selects the menu items or icons when it's 1-2 cursor heights below them. 9. Start Konsole 10. Try to select the menus in Konsole normally. The cursor only selects the menus when it's 1-2 cursor heights below them. OBSERVED RESULT The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled EXPECTED RESULT The cursor would appear normally and it would select things as usual. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide/37 (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION This problem didn't happen when using the same Fedora Rawhide KDE Plasma image on bare metal with the radeonsi mesa driver and amdgpu kernel driver with an integrated Radeon R5 GPU or in a GNOME Boxes QEMU-KVM VM with 3D acceleration disabled using the llvmpipe driver and virtio gpu. The problem might involve the virgl driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455630] New: kwin_wayland crashed in VMs using the llvmpipe graphics driver
https://bugs.kde.org/show_bug.cgi?id=455630 Bug ID: 455630 Summary: kwin_wayland crashed in VMs using the llvmpipe graphics driver Product: kwin Version: 5.25.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- SUMMARY kwin_wayland crashed at least 10 times in Fedora Rawhide/37 GNOME Boxes QEMU-KVM VMs using the llvmpipe graphics driver from mesa 22.1.2 and virtio gpu. The crashes sometimes happened when I was using Firefox, Konsole, Dolphin, and kwrite. Some crashes were when I right-clicked on text in Konsole, Firefox, and kwrite and tried to copy and paste it such as when trying the report this problem here. One crash happened when I right-clicked on a file in Dolphin and tried to copy and paste. Other crashes seemed random. The trace of the crashes seemed consistent. Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7feb9e9f9670 in ?? () [Current thread is 1 (Thread 0x7feb7a5fc640 (LWP 3064))] (gdb) thread apply all bt Thread 14 (Thread 0x7feb7adfd640 (LWP 3063)): #0 0x7feb9e9f9670 in ?? () #1 0x in ?? () Thread 13 (Thread 0x7feb59b78640 (LWP 3071)): #0 0x7feb9c71cf1f in poll () from /lib64/libc.so.6 #1 0x7feb9ab7421d in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7feb9ab1c930 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7feb9d8f88da in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7feb9d8a669a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7feb9d6e718a in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7feb9e74a469 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7feb9d6e8487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7feb9c6a8e9d in start_thread () from /lib64/libc.so.6 #9 0x7feb9c729680 in clone3 () from /lib64/libc.so.6 Thread 12 (Thread 0x7feb78df9640 (LWP 3067)): #0 0x7feb9c6a5a89 in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7feb9c6a8280 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7feb82cb83d3 in cnd_wait (mtx=0x56513e6c9690, cond=0x56513e6c96b8) at ../include/c11/threads_posix.h:155 #3 lp_cs_tpool_worker (data=data@entry=0x56513e6c9690) at ../src/gallium/drivers/llvmpipe/lp_cs_tpool.c:49 #4 0x7feb82cb834b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #5 0x7feb9c6a8e9d in start_thread () from /lib64/libc.so.6 #6 0x7feb9c729680 in clone3 () from /lib64/libc.so.6 Thread 11 (Thread 0x7feb79dfb640 (LWP 3065)): #0 0x7feb9c6a5a89 in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7feb9c6a8280 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7feb82cb83d3 in cnd_wait (mtx=0x56513e6c9690, cond=0x56513e6c96b8) at ../include/c11/threads_posix.h:155 #3 lp_cs_tpool_worker (data=data@entry=0x56513e6c9690) at ../src/gallium/drivers/llvmpipe/lp_cs_tpool.c:49 #4 0x7feb82cb834b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 --Type for more, q to quit, c to continue without paging--c #5 0x7feb9c6a8e9d in start_thread () from /lib64/libc.so.6 #6 0x7feb9c729680 in clone3 () from /lib64/libc.so.6 Thread 10 (Thread 0x7feb89538640 (LWP 3058)): #0 0x7feb9c71cf1f in poll () from /lib64/libc.so.6 #1 0x7feb9ab7421d in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7feb9ab1c930 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7feb9d8f88da in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7feb9d8a669a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7feb9d6e718a in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7feb9d6e8487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7feb9c6a8e9d in start_thread () from /lib64/libc.so.6 #8 0x7feb9c729680 in clone3 () from /lib64/libc.so.6 Thread 9 (Thread 0x7feb7bdff640 (LWP 3061)): #0 0x7feb9c6a7299 in pthread_barrier_wait@GLIBC_2.2.5 () from /lib64/libc.so.6 #1 0x7feb82cbb907 in util_barrier_wait (barrier=0x56513e6bfe60) at ../src/util/u_thread.h:298 #2 thread_function (init_data=init_data@entry=0x56513e6be7d8) at ../src/gallium/drivers/llvmpipe/lp_rast.c:1229 #3 0x7feb82cbae2b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7feb9c6a8e9d in start_thread () from /lib64/libc.so.6 #5 0x7feb9c729680 in clone3 () from /lib64/libc.so.6 Thread 8 (Thread 0x7feb9e25f980 (LWP 3039)): #0 0x7feb9c76fe04
[krfb] [Bug 451166] New: Starting krfb from konsole sometimes resulted in a crash of xdg-desktop-portal
https://bugs.kde.org/show_bug.cgi?id=451166 Bug ID: 451166 Summary: Starting krfb from konsole sometimes resulted in a crash of xdg-desktop-portal Product: krfb Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I started krfb 21.12.2 from konsole in Plasma 5.24.2 on Wayland in a Fedora 36 KDE Plasma installation. I noticed that krfb didn't appear after trying to start it from the Application Launcher menu. xdg-desktop-portal segmentation faulted in magazine_chain_pop_head at ../glib/gslice.c:579 in glib2-2.71.2-1.fc36.x86_64 sometimes when starting krfb with the following trace. Core was generated by `/usr/libexec/xdg-desktop-portal'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fe40a194f51 in magazine_chain_pop_head (magazine_chunks=) at ../glib/gslice.c:579 579 ChunkLink *chunk = (*magazine_chunks)->data; [Current thread is 1 (Thread 0x7fe3fb689640 (LWP 16331))] (gdb) bt #0 0x7fe40a194f51 in magazine_chain_pop_head (magazine_chunks=) at ../glib/gslice.c:579 #1 magazine_chain_prepare_fields (magazine_chunks=0x7fe3) at ../glib/gslice.c:661 #2 magazine_cache_push_magazine (ix=14, magazine_chunks=0x7fe3d0008110, count=5) at ../glib/gslice.c:735 #3 0x7fe40a1950f6 in private_thread_memory_cleanup (data=0x7fe3d8e0) at ../glib/gslice.c:821 #4 0x7fe409f89181 in __GI___nptl_deallocate_tsd () at nptl_deallocate_tsd.c:73 #5 __GI___nptl_deallocate_tsd () at nptl_deallocate_tsd.c:22 #6 0x7fe409f8be98 in start_thread (arg=) at pthread_create.c:453 #7 0x7fe40a0116d0 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 The journal from when one of the crashes happened follows. Mar 04 14:25:16 kwalletd5[1175]: Application ' "krfb" ' using kwallet without parent window! Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=fe80::::265c:5b24:c7aa:102b DST=ff02:::::::00fb LEN=164 TC=0 HOPLIMIT=255 FLOWLBL=52591 PROTO=UDP SPT=5353 DPT=5353 LEN=124 Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=192.168.2.10 DST=224.0.0.251 LEN=144 TOS=0x00 PREC=0x00 TTL=255 ID=19703 DF PROTO=UDP SPT=5353 DPT=5353 LEN=124 Mar 04 14:25:17 xdg-desktop-portal-kde[1676]: file:///usr/lib64/qt5/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:81:5: Unable to assign [undefined] to int Mar 04 14:25:17 xdg-desktop-portal-kde[1676]: file:///usr/lib64/qt5/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:80:5: Unable to assign [undefined] to int Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=fe80::::265c:5b24:c7aa:102b DST=ff02:::::::00fb LEN=164 TC=0 HOPLIMIT=255 FLOWLBL=52591 PROTO=UDP SPT=5353 DPT=5353 LEN=124 Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=192.168.2.10 DST=224.0.0.251 LEN=144 TOS=0x00 PREC=0x00 TTL=255 ID=19937 DF PROTO=UDP SPT=5353 DPT=5353 LEN=124 Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=fe80::::265c:5b24:c7aa:102b DST=ff02:::::::00fb LEN=164 TC=0 HOPLIMIT=255 FLOWLBL=52591 PROTO=UDP SPT=5353 DPT=5353 LEN=124 Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=192.168.2.10 DST=224.0.0.251 LEN=144 TOS=0x00 PREC=0x00 TTL=255 ID=19946 DF PROTO=UDP SPT=5353 DPT=5353 LEN=124 Mar 04 14:25:17 plasmashell[1329]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x555f7b44d5a0) Mar 04 14:25:17 plasmashell[1329]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x555f7b44d5a0) Mar 04 14:25:17 plasmashell[1329]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x555f7b44d5a0) Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=192.168.2.10 DST=224.0.0.251 LEN=233 TOS=0x00 PREC=0x00 TTL=255 ID=20065 DF PROTO=UDP SPT=5353 DPT=5353 LEN=213 Mar 04 14:25:17 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=fe80::::265c:5b24:c7aa:102b DST=ff02:::::::00fb LEN=237 TC=0 HOPLIMIT=255 FLOWLBL=52591 PROTO=UDP SPT=5353 DPT=5353 LEN=197 Mar 04 14:25:18 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=192.168.2.10 DST=224.0.0.251 LEN=233 TOS=0x00 PREC=0x00 TTL=255 ID=20230 DF PROTO=UDP SPT=5353 DPT=5353 LEN=213 Mar 04 14:25:18 kernel: "filter_IN_drop_DROP: "IN=enp1s0 OUT= MAC= SRC=fe80::::265c:5b24:c7aa:102b DST=ff02:::::::00fb LEN=237 TC=0 HOPLIMIT=255 FLOWLBL=52591 PROTO=UDP SPT=5353 DPT=5353 LEN=197 Mar 04 14:25:21 systemd[1]: systemd-localed.service: Deactivated successfully. Mar 04 14:25:21 audit[1]: SERVICE_STOP pid=1 uid=0
[plasmashell] [Bug 451065] New: Logging out of Plasma on Wayland sometimes resulted in a black screen and plasmashell, powerdevil, and xde-desktop-portal-kde aborts
https://bugs.kde.org/show_bug.cgi?id=451065 Bug ID: 451065 Summary: Logging out of Plasma on Wayland sometimes resulted in a black screen and plasmashell, powerdevil, and xde-desktop-portal-kde aborts Product: plasmashell Version: 5.24.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: 1.0 Created attachment 147251 --> https://bugs.kde.org/attachment.cgi?id=147251=edit journal for a boot where the black screen problem happened with the xdg-desktop-portal-kde crashes. SUMMARY Logging out of Plasma 5.24.2 on Wayland in a Fedora 36 KDE Plasma installation sometimes showed a black screen with a blinking underscore _ at the top left of the screen. This black screen problem happened about 20-30% of the time when logging out. plasmashell and powerdevil aborted usually 5 times each on some such logouts with errors that the Wayland connection had broken. xdg-desktop-portal-kde aborted multiple times on other logouts with the same errors. Traces of plasmashell and xdg-desktop-portal-kde crashes are the following. Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7efe10755f43 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7efe10705a36 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7efe106ef82f in __GI_abort () at abort.c:79 #4 0x7efe10bb4517 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #5 QMessageLogger::fatal (this=this@entry=0x7ffdf43de820, msg=msg@entry=0x7efe115ea407 "%s") at global/qlogging.cpp:893 #6 0x7efe111f60ef in init_platform (argv=, argc=, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254 #7 QGuiApplicationPrivate::createPlatformIntegration (this=0x55f08fd64ed0) at kernel/qguiapplication.cpp:1474 #8 0x7efe111f65c8 in QGuiApplicationPrivate::createEventDispatcher (this=) at kernel/qguiapplication.cpp:1491 #9 0x7efe10db2be1 in QCoreApplicationPrivate::init (this=this@entry=0x55f08fd64ed0) at kernel/qcoreapplication.cpp:835 #10 0x7efe111f8973 in QGuiApplicationPrivate::init (this=this@entry=0x55f08fd64ed0) at kernel/qguiapplication.cpp:1520 #11 0x7efe11a8672d in QApplicationPrivate::init (this=0x55f08fd64ed0) at kernel/qapplication.cpp:513 #12 0x55f08fb330a0 in main (argc=, argv=0x7ffdf43ded88) --Type for more, q to quit, c to continue without paging--c at /usr/src/debug/plasma-workspace-5.24.2-1.fc36.x86_64/shell/main.cpp:82 Core was generated by `/usr/libexec/xdg-desktop-portal-kde'. Missing separate debuginfos, use: dnf debuginfo-install xdg-desktop-portal-kde-5.24.2-1.fc36.x86_64 --Type for more, q to quit, c to continue without paging-- Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f028b20dea3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7f028b1bda16 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7f028b1a782f in __GI_abort () at abort.c:79 #4 0x7f028b66c517 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #5 QMessageLogger::fatal (this=this@entry=0x7ffd17e9bf70, msg=msg@entry=0x7f028c89a407 "%s") at global/qlogging.cpp:893 #6 0x7f028c4a60ef in init_platform (argv=, argc=, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254 #7 QGuiApplicationPrivate::createPlatformIntegration (this=0x56223197cb20) at kernel/qguiapplication.cpp:1474 #8 0x7f028c4a65c8 in QGuiApplicationPrivate::createEventDispatcher (this=) at kernel/qguiapplication.cpp:1491 #9 0x7f028b86abe1 in QCoreApplicationPrivate::init (this=this@entry=0x56223197cb20) at kernel/qcoreapplication.cpp:835 #10 0x7f028c4a8973 in QGuiApplicationPrivate::init (this=this@entry=0x56223197cb20) at kernel/qguiapplication.cpp:1520 #11 0x7f028d09672d in QApplicationPrivate::init
[plasmashell] [Bug 411662] plasmashell segmentation fault in QV4::CompiledData::CompilationUnit::destroy() after configuring the task manager to set the Show tooltips to off in Plasma 5.16.4 on Waylan
https://bugs.kde.org/show_bug.cgi?id=411662 --- Comment #6 from Matt Fagnani --- (In reply to Nate Graham from comment #3) > Can't reproduce with current git master. Can anyone who was affected check > again with at least Plasma 5.23? Git master or the Plasma 5.24 beta > (released tomorrow) would be even better. :) I set Show tooltips to off and on from Configure Task Manager several times in a Fedora 35 KDE Plasma installation with Plasma 5.23.5, KF 5.90.0, Qt 5.15.2. Plasmashell didn't crash. I didn't get emails for comments 3-4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422711] kwin_wayland segmentation fault in KWin::LibInput::Connection::applyScreenToDevice when logging in
https://bugs.kde.org/show_bug.cgi?id=422711 --- Comment #5 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #4) > That sounds like a different problem. Can you file a bug report? There were > some session related fixes in 5.24, so that issue might be already fixed. I reported what I described in comment 3 at https://bugs.kde.org/show_bug.cgi?id=449609 Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449609] New: Plasma on Wayland didn't start normally after a failed login attempt as another user to Plasma on X
https://bugs.kde.org/show_bug.cgi?id=449609 Bug ID: 449609 Summary: Plasma on Wayland didn't start normally after a failed login attempt as another user to Plasma on X Product: kwin Version: 5.23.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I tried to log in to Plasma on X with an incorrect password as one user from sddm, followed by logging in to Plasma on Wayland with the correct password as another user in a Fedora 35 KDE Plasma installation with Plasma 5.23.5, KF 5.90.0, Qt 5.15.2. The screen went black, and the Plasma splash screen didn't appear. Plasma didn't start normally. sddm reappeared. The failed Plasma startup happened 3/3 times I tried the above steps. STEPS TO REPRODUCE 1. Boot a Fedora 35 KDE Plasma installation updated to 2022-2-3 with the updates-testing repo enabled. The system has two normal users shown in sddm. 2. Try to log in to Plasma on X as the second user with an incorrect password from sddm 3. Log in to Plasma on Wayland as the first user with the correct password OBSERVED RESULT Plasma on Wayland didn't start normally after a failed login attempt as another user to Plasma on X EXPECTED RESULT Plasma on Wayland would start normally after a failed login attempt as another user to Plasma on X SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 + patches from KDE/Qt repos ADDITIONAL INFORMATION coredumpctl and journalctl didn't have kwin_wayland crashes as happened in my previous report with similar steps at https://bugs.kde.org/show_bug.cgi?id=422711 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422711] kwin_wayland segmentation fault in KWin::LibInput::Connection::applyScreenToDevice when logging in
https://bugs.kde.org/show_bug.cgi?id=422711 Matt Fagnani changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Matt Fagnani --- (In reply to David Redondo from comment #1) > Can you still reproduce I tried to reproduce this problem in a Fedora 35 KDE Plasma installation with Plasma 5.23.5, KF 5.90.0, Qt 5.15.2 by trying to log in to Plasma on X with an incorrect password as one user from sddm, followed by logging in to Plasma on Wayland with the correct password as another user. The screen went black, and the Plasma splash screen didn't appear. Plasma didn't start normally. sddm reappeared. coredumpctl and journalctl didn't have kwin_wayland crashes, though I'm unsure why Plasma didn't start. The failed Plasma startup happened 2/2 times I tried the above steps. I'm unsure if this is the same problem as I first reported. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409021] Segmentation faults of plasmashell in wl_proxy_set_queue in libwayland-client in Plasma on Wayland
https://bugs.kde.org/show_bug.cgi?id=409021 Matt Fagnani changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #16 from Matt Fagnani --- (In reply to Aleix Pol from comment #14) > Can you still reproduce this? A bunch of things have been fixed since. > > This could also be related, although it wouldn't be easy to backport since > RHI is involved. > https://codereview.qt-project.org/c/qt/qtwayland/+/371043 I haven't seen plasmashell crash with this trace in Plasma on Wayland in many months at least. I didn't see any crash when I repeatedly clicked to open and close the Application Menu at the lower-left of the screen many times today in Plasma 5.23.4 on Wayland with KF 5.90.0, Qt 5.15.2 in Fedora 35. I guess this problem was fixed at some point. I'll mark it as fixed. Feel free to reopen it if someone else sees this again. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444921] ksgrd_network_helper aborted when starting plasma-systemmonitor 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444921 --- Comment #4 from Matt Fagnani --- (In reply to Arjen Hiemstra from comment #1) > https://invent.kde.org/plasma/libksysguard/-/merge_requests/193 takes care > of the abort. That said, the abort shouldn't really happen in the first > place and only seems to happen because of a packaging bug. > `ksgrd_network_helper` needs `CAP_NET_RAW` to run, as it needs to capture > all the packets going over network devices. It seems Fedora's package > doesn't set that. That should be reported to Fedora somewhere. Arjen, I've quoted your comment in one on my report for Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=2020138#c1 Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444921] New: ksgrd_network_helper aborted when starting plasma-systemmonitor 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444921 Bug ID: 444921 Summary: ksgrd_network_helper aborted when starting plasma-systemmonitor 5.23.2 Product: plasma-systemmonitor Version: 5.23.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY ksgrd_network_helper aborted 6/6 times when starting plasma-systemmonitor in Plasma 5.23.2 on Wayland in a Fedora 35 KDE Plasma installation. The crashes happened right after plasma-systemmonitor started to the Overview screen. 5/6 of the ksgrd_network_helper crashes had traces which involved ConnectionMapping::~ConnectionMapping as follows Core was generated by `/usr/libexec/ksysguard/ksgrd_network_helper'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7fd5fed08fc0 (LWP 5117))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fd5fe8b38c3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fd5fe8666b6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7fd5fe8507d3 in __GI_abort () at abort.c:79 #4 0x7fd5feaf5a46 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #5 0x7fd5feb0129c in __cxxabiv1::__terminate (handler=) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48 #6 0x7fd5feb01307 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58 #7 0x55b5febb50fc in std::thread::~thread (this=, this=) at /usr/include/c++/11/bits/std_thread.h:152 #8 ConnectionMapping::~ConnectionMapping (this=, this=) at /usr/src/debug/libksysguard-5.23.2-1.fc35.x86_64/processcore/plugins/network/helper/ConnectionMapping.h:26 #9 __gnu_cxx::new_allocator::destroy (__p=, this=) at /usr/include/c++/11/ext/new_allocator.h:168 #10 std::allocator_traits >::destroy ( __p=, __a=...) at /usr/include/c++/11/bits/alloc_traits.h:531 #11 std::_Sp_counted_ptr_inplace, (__gnu_cxx::_Lock_policy)2>::_M_dispose (this=) at /usr/include/c++/11/bits/shared_ptr_base.h:528 --Type for more, q to quit, c to continue without paging--c #12 0x55b5febb5247 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release (this=0x55b5ff23a830) at /usr/include/c++/11/bits/shared_ptr_base.h:168 #13 0x55b5febb36fb in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count (this=, this=) at /usr/include/c++/11/bits/shared_ptr_base.h:702 #14 std::__shared_ptr::~__shared_ptr (this=, this=) at /usr/include/c++/11/bits/shared_ptr_base.h:1154 #15 std::shared_ptr::~shared_ptr (this=, this=) at /usr/include/c++/11/bits/shared_ptr.h:122 #16 main (argc=, argv=) at /usr/src/debug/libksysguard-5.23.2-1.fc35.x86_64/processcore/plugins/network/helper/main.cpp:94 The journal at the time of the crashes showed errors like: plasma-systemmonitor[2577]: org.kde.ksysguard.plugin.network: Helper process terminated abnormally! plasma-systemmonitor[2577]: org.kde.ksysguard.plugin.network: "The process doesn't have permission to open the capture source\nterminate called without an active exception\n" Nov 04 01:47:53 systemd[1106]: Started System Monitor - System Monitor. Nov 04 01:47:54 plasma-systemmonitor[2577]: kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling. Nov 04 01:47:54 systemd[1106]: Starting Track hardware statistics... Nov 04 01:47:54 NetworkManager[922]: [1636004874.4886] audit: op="statistics" interface="enp1s0" ifindex=2 args="500" pid=2589 uid=1000 result="success" Nov 04 01:47:54 NetworkManager[922]: [1636004874.5509] audit: op="statistics" interface="wlp2s0" ifindex=3 args="500" pid=2589 uid=1000 result="success" Nov 04 01:47:54 audit: BPF prog-id=49 op=LOAD Nov 04 01:47:54 audit: BPF prog-id=50 op=LOAD Nov 04 01:47:54 systemd[1]: Starting Hostname Service... Nov 04 01:47:54 systemd[1106]: Started Track hardware statistics. Nov 04 01:47:54 NetworkManager[922]: [1636004874.6293] audit: op="statistics" interface="wlp2s0" ifindex=3 args="500" pid=2589 uid=1000 result="success" Nov 04 01:47:54 systemd[1]: Started Hostname Service. Nov 04 01:47:54 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 04 01:47:55 plasma-systemmonitor[2577]:
[Discover] [Bug 439619] DiscoverNotifier occasionally crashed with a failed assertion related to flatpak then SIGTRAP in g_log_structured_array in glib after Plasma started
https://bugs.kde.org/show_bug.cgi?id=439619 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Matt Fagnani --- (In reply to Nate Graham from comment #4) > Have you seen it at all since then? Also would you be able to upgrade to > 5.22.5 and see if it still happens ever with that version? Or even better, > 5.23 (the beta, or the final release a week from now)? Some Flatpak fixes > have been made recently. These crashes just happened with Plasma 5.22.5 after an offline update which included Discover 5.23.0 and KF 5.87.0 from the updates-testing repo in a Fedora 35 KDE Plasma installation. The failed flatpak assertion happened first flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) drkonqi appeared. I tried to get a trace in drkonqi, then DiscoverNotifer crashed with SIGTRAP. I've seen these crashes a few times since my last report, but they only happened about 1-2% of logins to Plasma. I have the fedora, flathub, kdeapps flatpak remotes enabled. The problem might be with one of those remotes or how their metadata are being processed. Here's the journal from the time of the latest crashes. Oct 07 12:12:43 DiscoverNotifier[1473]: ** Oct 07 12:12:43 DiscoverNotifier[1473]: flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) Oct 07 12:12:43 DiscoverNotifier[1473]: Bail out! flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) Oct 07 12:12:44 DiscoverNotifier[1473]: KCrash: Attempting to start /usr/libexec/DiscoverNotifier Oct 07 12:12:44 DiscoverNotifier[1473]: KCrash: Application 'DiscoverNotifier' crashing... Oct 07 12:12:44 DiscoverNotifier[1473]: KCrash: Attempting to start /usr/libexec/drkonqi Oct 07 12:12:44 DiscoverNotifier[1473]: QSocketNotifier: Invalid socket 8 and type 'Read', disabling... Oct 07 12:12:44 DiscoverNotifier[1473]: QSocketNotifier: Invalid socket 6 and type 'Read', disabling... Oct 07 12:12:44 DiscoverNotifier[1473]: QSocketNotifier: Invalid socket 7 and type 'Read', disabling... Oct 07 12:12:44 DiscoverNotifier[1473]: QSocketNotifier: Invalid socket 9 and type 'Read', disabling... Oct 07 12:12:45 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 07 12:12:45 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 07 12:12:45 audit: BPF prog-id=45 op=UNLOAD Oct 07 12:12:45 audit: BPF prog-id=44 op=UNLOAD Oct 07 12:12:47 PackageKit[1496]: get-updates transaction /22256_ecddeadb from uid 1000 finished with success after 4824ms Oct 07 12:12:50 plasmashell[1270]: trying to show an empty dialog Oct 07 12:12:56 DiscoverNotifie[1473]: inotify read(): Bad file descriptor Oct 07 12:12:56 kernel: show_signal: 58 callbacks suppressed Oct 07 12:12:56 kernel: traps: gmain[1935] trap int3 ip:7f90cbfe9def sp:7f90b1b23790 error:0 in libglib-2.0.so.0.7000.0[7f90cbfab000+91000] Oct 07 12:12:56 audit[1473]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1473 comm="gmain" exe="/usr/libexec/DiscoverNotifier" sig=5 res=1 Oct 07 12:12:56 systemd[1]: Created slice Slice /system/systemd-coredump. Oct 07 12:12:56 audit: BPF prog-id=49 op=LOAD Oct 07 12:12:56 audit: BPF prog-id=50 op=LOAD Oct 07 12:12:56 audit: BPF prog-id=51 op=LOAD Oct 07 12:12:56 systemd[1]: Started Process Core Dump (PID 1992/UID 0). Oct 07 12:12:56 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-1992-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Oct 07 12:12:57 systemd-coredump[1994]: Process 1473 (DiscoverNotifie) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: a163a65077b549ecf47548415b039e8470b2b031 Found module libnss_resolve.so.2 with build-id: 4a47d35758f2657628a3657c1000a5958dac65b7 Found module libnss_sss.so.2 with build-id: f8ff93ecdf21e431b595f5ea823fe396d56da42d Found module libjavascriptcoregtk-4.0.so.18 with build-id: c15a43b6879f957cfd2f4bd8973ff16230934d93 Found module pacrunner_webkit.so with build-id: 8825df721dcf4c36ff066c450fa3a83d5c77ed24 Found module libproxy.so.1 with build-id: 7902906e4947
[kwin] [Bug 423602] kwin_wayland segmentation fault in std::__atomic_base::operator++ when using vlc
https://bugs.kde.org/show_bug.cgi?id=423602 Matt Fagnani changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #2) > Quite many things have changed in SeatInterface. Is this issue still actual? I haven't seen this type of crash in several months at least with Plasma 5.22.5 and earlier. I think the problem has been fixed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #3) > We've changed the handling of inert subsurfaces. Is this issue still actual? I haven't seen this type of crash in many months. I think it might've been fixed in Firefox. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442104] kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35
https://bugs.kde.org/show_bug.cgi?id=442104 --- Comment #2 from Matt Fagnani --- (In reply to Zamundaaa from comment #1) > Still happens with git master, too. The reason is that teardown of input > depends on the platform, which is deleted before input. > > Not sure how to best solve it yet, parenting the InputIntegration object to > the platform instead of the application causes a different segfault, AFACT > due to some annoying details about how C++ destructors work. I've seen this kwin_wayland crash happen about 10/15 times when logging out of Plasma using a mouse and 3/6 using a touchpad. The crash also happened with libinput-1.19.0-1.fc35. The problem might involve a race condition where the file descriptor fd had been closed or memory associated with the platform had been freed sometimes before being used by KWin::LibInput::Context::closeRestricted while Plasma was logging out. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442104] New: kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35
https://bugs.kde.org/show_bug.cgi?id=442104 Bug ID: 442104 Summary: kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35 Product: kwin Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma 5.22.5 on Wayland in a Fedora 35 KDE Plasma installation. The screen went black and then Plasma restarted. Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fe383646a95 in KWin::LibInput::Context::closeRestricted (this=0x558b8b8fb7a0, fd=33) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:146 Downloading source file /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp... 146 kwinApp()->platform()->session()->closeRestricted(fd); [Current thread is 1 (Thread 0x7fe36d78d640 (LWP 2255))] (gdb) bt #0 0x7fe383646a95 in KWin::LibInput::Context::closeRestricted(int) (this=0x558b8b8fb7a0, fd=33) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:146 #1 KWin::LibInput::Context::closeRestrictedCallBack(int, void*) (fd=33, user_data=0x558b8b8fb7a0) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:97 #2 0x7fe380e19101 in close_restricted (libinput=, libinput=0x558b8b8fb7c0, fd=) at ../src/libinput.c:2054 #3 evdev_device_suspend (device=device@entry=0x558b8b9b8bf0) at ../src/evdev.c:2871 #4 0x7fe380e22e76 in evdev_device_remove (device=0x558b8b9b8bf0) at ../src/evdev.c:2961 #5 0x7fe380e129e4 in evdev_device_dispatch (data=0x558b8b9b8bf0) at ../src/evdev.c:1144 #6 0x7fe380e0e667 in libinput_dispatch (libinput=0x558b8b8fb7c0) at ../src/libinput.c:2209 #7 0x7fe383646e7d in KWin::LibInput::Context::dispatch() (this=, this=) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:80 #8 KWin::LibInput::Connection::handleEvent() (this=0x558b8b966300) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/connection.cpp:231 #9 0x7fe381c573a9 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fe36d78c850, r=, this=0x7fe3640047b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x7fe3640046d0, signal_index=3, argv=0x7fe36d78c850) at kernel/qobject.cpp:3886 #11 0x7fe381c52327 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7fe3640046d0, m=m@entry=0x7fe381efc460 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fe36d78c850) at kernel/qobject.cpp:3946 #12 0x7fe381c59b4a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x7fe3640046d0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #13 0x7fe381c5a363 in QSocketNotifier::event(QEvent*) (this=0x7fe3640046d0, e=0x7fe36d78c950) at kernel/qsocketnotifier.cpp:302 #14 0x7fe3828b3443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7fe3640046d0, e=0x7fe36d78c950) at kernel/qapplication.cpp:3632 #15 0x7fe381c23798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7fe3640046d0, event=0x7fe36d78c950) at kernel/qcoreapplication.cpp:1064 #16 0x7fe381c755ff in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x7fe364004470) at kernel/qeventdispatcher_glib.cpp:107 #17 0x7fe37f2d233f in g_main_dispatch (context=0x7fe364000c20) at ../glib/gmain.c:3381 #18 g_main_context_dispatch (context=0x7fe364000c20) at ../glib/gmain.c:4099 #19 0x7fe37f327288 in g_main_context_iterate.constprop.0 (context=context@entry=0x7fe364000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175 #20 0x7fe37f2cf9e3 in g_main_context_iteration (context=0x7fe364000c20, may_block=1) at ../glib/gmain.c:4240 #21 0x7fe381c74b78 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe364000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7fe381c221a2 in QEventLoop::exec(QFlags) (this=this@entry=0x7fe36d78cbd0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7fe381a652aa in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7fe381a664a6 in QThreadPrivate::start(void*) (arg=0x558b8b9bc0d0) at thread/qthread_unix.cpp:329 #25 0x7fe3813caaaf in start_thread (arg=)
[dolphin] [Bug 439606] /tmp/startkdeinitlock may block dolphin for 30 seconds, if file owned by another user.
https://bugs.kde.org/show_bug.cgi?id=439606 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca --- Comment #3 from Matt Fagnani --- Thanks. This problem looks similar to that reported at https://bugs.kde.org/show_bug.cgi?id=434290 I noticed that /tmp/startkdeinitlock was present when the Plasma startup delay happened, but not otherwise. /tmp/startkdeinitlock was a text file containing 9014 kdeinit5_shutdown localhost.localdomain The kdeinit5_shutdown process was running when the problem happened, but it wasn't running when the problem wasn't happening. kdeinit5_shutdown and /tmp/startkdeinitlock seemed to be left over from the first Plasma session, and they might be blocking Plasma and other programs from starting normally. I tried removing /tmp/startkdeinitlock and stopping kdeinit5_shutdown, and the problem seemed to go away at least for starting Dolphin and loading the desktop icons during the same session. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 434290] After re-login, sometimes kdeinit5 takes 30 seconds to start
https://bugs.kde.org/show_bug.cgi?id=434290 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca --- Comment #10 from Matt Fagnani --- When I've logged out of Plasma 5.22.3 with KF 5.83.0 and Qt 5.15.2 and earlier on Wayland in a Fedora 34 KDE Plasma installation then logged in again, Plasma was delayed by 30 seconds when starting remaining on the splash screen for that long. The desktop icons took another 30 seconds to appear. Certain KDE programs such as Dolphin and Gwenview took 30 seconds to start. The file selection dialogs in Qt-based programs like VLC took 30 seconds to start. The most relevant messages in the journal when this delay happened were like kded5[9321]: kf.dbusaddons: 'kdeinit5' is taking more than 30 seconds to start. The journal when logging in to Plasma on Wayland was delayed after logging out as the same user is attached at https://bugzilla.redhat.com/show_bug.cgi?id=1985151 I first noticed this problem when logging out from Plasma on Wayland as one user then logging into Plasma on Wayland as a second user. This problem happened most of the time when doing so over the last few weeks at least. I had set KillUserProcesses=yes in /etc/systemd/logind.conf to stop the user session processes during that time. I changed that to #KillUserProcesses=yes in /etc/systemd/logind.conf. After that change, Plasma and other programs were delayed by 30 seconds when I logged out as one user and logged in again as the same user. These observations led me to think that some processes or files were left over after ending the first Plasma session which might be kdeinit5_shutdown and /tmp/startkdeinitlock as I describe below. A similar report about Dolphin taking 30 s to start noted that /tmp/startkdeinitlock was left after logging out as userA and logging in as userB at https://bugs.kde.org/show_bug.cgi?id=439606 I noticed that /tmp/startkdeinitlock was present when the Plasma startup delay happened, but not otherwise. /tmp/startkdeinitlock was a text file containing 9014 kdeinit5_shutdown localhost.localdomain The kdeinit5_shutdown process was running when the problem happened, but it wasn't running when the problem wasn't happening. kdeinit5_shutdown and /tmp/startkdeinitlock seemed to be left over from the first Plasma session, and they might be blocking Plasma and other programs from starting normally. I tried removing /tmp/startkdeinitlock and stopping kdeinit5_shutdown, and the problem seemed to go away at least for starting Dolphin and loading the desktop icons during the same session. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439619] DiscoverNotifier occasionally crashed with a failed assertion related to flatpak then SIGTRAP in g_log_structured_array in glib after Plasma started
https://bugs.kde.org/show_bug.cgi?id=439619 --- Comment #3 from Matt Fagnani --- (In reply to Aleix Pol from comment #2) > Can you reproduce? I don't think there's much we can do with this backtrace. Aleix, I reproduced the DiscoverNotifier crash with the failed assertion in flatpak 9 times (about 1-2 times a week), but the last crash was 2021-6-30. Since the crashes only happened in 1-2% of Plasma sessions, it might take a while to see if the problem is still reproducible unless I were to log in to Plasma like 100 times when there's new flathub or kdeapps metadata. The failed assertion flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) might have meant there was some problem with the flatpak metadata for the flathub or kdeapps remotes. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439619] DiscoverNotifier occasionally crashed with a failed assertion related to flatpak then SIGTRAP in g_log_structured_array in glib after Plasma started
https://bugs.kde.org/show_bug.cgi?id=439619 Matt Fagnani changed: What|Removed |Added Summary|DiscoverNotifier|DiscoverNotifier |occasionally crashed with |occasionally crashed with a |SIGTRAP in |failed assertion related to |g_log_structured_array in |flatpak then SIGTRAP in |glib after Plasma started |g_log_structured_array in ||glib after Plasma started --- Comment #1 from Matt Fagnani --- I forgot to mention that I think the failed assertion flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) is the reason for the first crash of DiscoverNotifier. The following DiscoverNotifier crash with SIGTRAP in g_log_structured_array likely happened when I tried to generate the trace in drkonqi by clicking the Advanced tab or button which led to the drkonqi crash. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439619] New: DiscoverNotifier occasionally crashed with SIGTRAP in g_log_structured_array in glib after Plasma started
https://bugs.kde.org/show_bug.cgi?id=439619
Bug ID: 439619
Summary: DiscoverNotifier occasionally crashed with SIGTRAP in
g_log_structured_array in glib after Plasma started
Product: Discover
Version: 5.21.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Notifier
Assignee: aleix...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
I've used a Fedora 34 KDE Plasma installation. Starting with Plasma 5.21.5 on
Wayland, DiscoverNotifier occasionally crashed with SIGTRAP in
g_log_structured_array in glib 2.68.2 about 30 s to 1 minute after login. Frame
1 of the crashing thread 1 had the error message "inotify read(): Bad file
descriptor"
Core was generated by `/usr/libexec/DiscoverNotifier'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0 g_log_structured_array (log_level=, fields=0x7fb94bffd7e0,
n_fields=4)
at ../glib/gmessages.c:556
556 G_BREAKPOINT ();
[Current thread is 1 (Thread 0x7fb94bfff640 (LWP 6231))]
(gdb) bt full
#0 g_log_structured_array (log_level=, fields=0x7fb94bffd7e0,
n_fields=4)
at ../glib/gmessages.c:556
__func__ = "g_log_structured_array"
#1 0x7fb96a4b5249 in g_log_default_handler
(log_domain=log_domain@entry=0x7fb9585976c4 "GLib-GIO",
log_level=log_level@entry=6, message=message@entry=0x7fb9440014a0 "inotify
read(): Bad file descriptor", unused_data=unused_data@entry=0x0)
at ../glib/gmessages.c:3236
fields =
{{key = 0x7fb96a5102e7 "GLIB_OLD_LOG_API", value = 0x7fb96a50e340,
length = -1}, {key = 0x7fb96a510228 "MESSAGE", value = 0x7fb9440014a0, length =
-1}, {key = 0x7fb96a51023b "PRIORITY", value = 0x7fb96a50a71d, length = -1},
{key = 0x7fb96a510295 "GLIB_DOMAIN", value = 0x7fb9585976c4, length = -1}}
n_fields =
#2 0x7fb96a4b661a in g_logv
(log_domain=0x7fb9585976c4 "GLib-GIO", log_level=G_LOG_LEVEL_ERROR,
format=, args=) at ../glib/gmessages.c:1382
domain = 0x0
data = 0x0
depth =
log_func = 0x7fb96a4b5190
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
--Type for more, q to quit, c to continue without paging--c
msg = 0x7fb9440014a0 "inotify read(): Bad file descriptor"
msg_alloc = 0x7fb9440014a0 "inotify read(): Bad file descriptor"
i = 2
#3 0x7fb96a4b6903 in g_log (log_domain=log_domain@entry=0x7fb9585976c4
"GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_ERROR,
format=format@entry=0x7fb9585cbd91 "inotify read(): %s") at
../glib/gmessages.c:1451
args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
0x7fb94bffda10, reg_save_area = 0x7fb94bffd950}}
#4 0x7fb95858c5b7 in ik_source_read_some_events
(iks=iks@entry=0x5566818859b0, buffer=buffer@entry=0x7fb94bffda80 "",
buffer_len=buffer_len@entry=4096) at ../gio/inotify/inotify-kernel.c:160
result =
errsv =
#5 0x7fb95858c71b in ik_source_read_all_the_events (buffer_len=4096,
length_out=, buffer=0x7fb94bffda80 "", iks=0x5566818859b0)
at ../gio/inotify/inotify-kernel.c:169
n_read =
stack_buffer = '\000' ...
buffer_len =
offset =
iks = 0x5566818859b0
user_callback = 0x7fb95858da60
interesting = 0
now = 2076854595
__func__ = "ik_source_dispatch"
#6 ik_source_dispatch (source=0x5566818859b0, func=0x7fb95858da60
, user_data=) at
../gio/inotify/inotify-kernel.c:253
stack_buffer = '\000' ...
buffer_len =
offset =
iks = 0x5566818859b0
user_callback = 0x7fb95858da60
interesting = 0
now = 2076854595
__func__ = "ik_source_dispatch"
#7 0x7fb96a4ae4cf in g_main_dispatch (context=0x55668185dc70) at
../glib/gmain.c:3337
dispatch = 0x7fb95858c6a0
prev_source = 0x0
begin_time_nsec = 2076854591611
was_in_call =
user_data = 0x0
callback = 0x7fb95858da60
cb_funcs = 0x7fb96a5913a0
cb_data = 0x556681877780
need_destroy =
source = 0x5566818859b0
current = 0x7fb944000c10
i = 0
#8 g_main_context_dispatch (context=0x55668185dc70) at ../glib/gmain.c:4055
#9 0x7fb96a5024e8 in g_main_context_iterate.constprop.0
(context=context@entry=0x55668185dc70, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131
max_priority = 2147483647
timeout = -1
some_ready = 1
nfds = 2
allocated_nfds = 2
fds =
begin_time_nsec = 2040086645207
#10 0x7fb96a4abc03 in g_main_context_iteration (context=0x55668185dc70,
may_block=may_block@entry=1) at ../glib/gmain.c:4196
retval =
#11 0x7fb96a4abc51 in glib_worker_main (data=) at
../glib/gmain.c:6089
[kate] [Bug 438895] There are two actions (Open Command Bar, ) that want to use the same shortcut (Ctrl+Alt+I) when starting Kate in Plasma 5.22.1
https://bugs.kde.org/show_bug.cgi?id=438895 --- Comment #1 from Matt Fagnani --- When I selected Settings > Configure keyboard shortcuts in Kate and entered Ctrl+Alt+I, Open Command Bar and view_commandbar_open were listed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438895] New: There are two actions (Open Command Bar, ) that want to use the same shortcut (Ctrl+Alt+I) when starting Kate in Plasma 5.22.1
https://bugs.kde.org/show_bug.cgi?id=438895 Bug ID: 438895 Summary: There are two actions (Open Command Bar, ) that want to use the same shortcut (Ctrl+Alt+I) when starting Kate in Plasma 5.22.1 Product: kate Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I opened Kate 21.04.1 from a desktop shortcut or the Application launcher menu in Plasma 5.22.1 on Wayland with KF 5.83.0 in a Fedora 34 KDE Plasma installation. An error popup titled Ambiguous Shortcuts appeared with the following message: There are two actions (Open Command Bar, ) that want to use the same shortcut (Ctrl+Alt+I). This is most probably a bug. Please report it in bugs.kde.org Kate had this error each of a few times I started it, and it started normally when I clicked OK. STEPS TO REPRODUCE 1. Boot a Fedora 34 KDE Plasma installation updated to 2021-6-18 with updates-testing enabled and kate installed 2. Log in to Plasma 5.22.1 on Wayland 3. Start Kate OBSERVED RESULT There are two actions (Open Command Bar, ) that want to use the same shortcut (Ctrl+Alt+I) when starting Kate in Plasma 5.22.1 EXPECTED RESULT Kate would start without the error message. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This error didn't appear when using Plasma 5.21.5 and earlier with KF 5.82.0 and earlier with the same Kate version. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429027] System Settings segmentation faulted in KCModuleProxyPrivate::loadModule()
https://bugs.kde.org/show_bug.cgi?id=429027 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429027] System Settings segmentation faulted in KCModuleProxyPrivate::loadModule()
https://bugs.kde.org/show_bug.cgi?id=429027 --- Comment #24 from Matt Fagnani --- Created attachment 138403 --> https://bugs.kde.org/attachment.cgi?id=138403=edit New crash information added by DrKonqi systemsettings5 (5.21.5) using Qt 5.15.2 - What I was doing when the application crashed: I tried to reproduce the System Settings crash in #429027 by selecting all the items from Startup and Shutdown down to Regional Settings in the sidebar menu on the left quickly so that sometimes the kcm screens didn't load before I selected the next one. I was using Plasma 5.21.5 on Wayland with KF 5.81.0 and Qt 5.15.2 in a Fedora 34 KDE Plasma installation. System Settings segmentation faulted in std::__atomic_base::store(QObjectPrivate::SignalVector*, std::memory_order) at /usr/include/c++/11/bits/atomic_base.h:811 in libstdc++-devel-11.1.1-1.fc34.x86_64. The first crash was in std::__atomic_base::load(std::memory_order), but the traces look similar otherwise. I remember this type of crash happening for me just these two times. -- Backtrace (Reduced): #4 std::__atomic_base::store(QObjectPrivate::SignalVector*, std::memory_order) (__m=std::memory_order_relaxed, __p=0x55ce07c03990, this=0x7f4330f8f888 ) at /usr/include/c++/11/bits/atomic_base.h:811 #5 std::atomic::store(QObjectPrivate::SignalVector*, std::memory_order) (__m=std::memory_order_relaxed, __p=0x55ce07c03990, this=0x7f4330f8f888 ) at /usr/include/c++/11/atomic:568 #6 QAtomicOps::storeRelaxed(std::atomic&, QObjectPrivate::SignalVector*) (newValue=0x55ce07c03990, _q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:269 #7 QBasicAtomicPointer::storeRelaxed(QObjectPrivate::SignalVector*) (newValue=0x55ce07c03990, this=0x7f4330f8f888 ) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:249 #8 QObjectPrivate::ConnectionData::resizeSignalVector(unsigned int) (this=this@entry=0x7f4330f8f880 , size=) at kernel/qobject_p.h:308 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 430325] kstars segmentation faulted in DetailDialog::createGeneralTab
https://bugs.kde.org/show_bug.cgi?id=430325 Matt Fagnani changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436215] New: System Monitor segmentation faulted in update_buffers when closing
https://bugs.kde.org/show_bug.cgi?id=436215 Bug ID: 436215 Summary: System Monitor segmentation faulted in update_buffers when closing Product: plasma-systemmonitor Version: 5.21.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.21.4) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.16-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.4 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I started System Monitor in Plasma 5.21.4 on Wayland in a Fedora 34 KDE Plasma installation. I selected History in the left menu. I closed System Monitor. System Monitor segmentation faulted in update_buffers at ../src/egl/drivers/dri2/platform_wayland.c:670 in mesa-libEGL-21.0.3-1.fc34.x86_64. I've only seen System Monitor crash once with this trace. plasmashell occasionally crashed in update_buffers with a similar trace as I reported at https://bugs.kde.org/show_bug.cgi?id=414411 The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f86fde58f9d in update_buffers (dri2_surf=dri2_surf@entry=0x7f86ac004d50) at ../src/egl/drivers/dri2/platform_wayland.c:670 #5 0x7f86fde593d8 in image_get_buffers (driDrawable=, format=, stamp=, loaderPrivate=0x7f86ac004d50, buffer_mask=, buffers=0x7f86c55deb60) at ../src/egl/drivers/dri2/platform_wayland.c:805 #6 0x7f86fc781786 in dri_image_drawable_get_buffers (statts_count=, statts=, images=, drawable=) at ../src/gallium/frontends/dri/dri2.c:282 #7 dri2_allocate_textures (ctx=0x5634e0279160, drawable=0x7f86ac0051a0, statts=0x7f86ac0058e8, statts_count=2) at ../src/gallium/frontends/dri/dri2.c:415 #8 0x7f86fc783044 in dri_st_framebuffer_validate (stctx=, stfbi=, statts=0x7f86ac0058e8, count=2, out=0x7f86c55ded10) at ../src/gallium/frontends/dri/dri_drawable.c:82 #9 0x7f86fc7df59c in st_framebuffer_validate (stfb=stfb@entry=0x7f86ac005410, st=st@entry=0x5634e0496ea0) at ../src/mesa/state_tracker/st_manager.c:223 #10 0x7f86fc7dfbc0 in st_manager_validate_framebuffers (st=st@entry=0x5634e0496ea0) at ../src/mesa/state_tracker/st_manager.c:1178 #11 0x7f86fc7ffe98 in st_validate_state (st=st@entry=0x5634e0496ea0, pipeline=pipeline@entry=ST_PIPELINE_CLEAR) at ../src/mesa/state_tracker/st_atom.c:203 #12 0x7f86fc804f69 in st_Clear (ctx=0x5634e044c970, mask=50) at ../src/mesa/state_tracker/st_cb_clear.c:442 #13 0x7f8705c9b768 in QSGBatchRenderer::Renderer::renderBatches (this=this@entry=0x7f86ac00c310) at scenegraph/coreapi/qsgbatchrenderer.cpp:4042 #14 0x7f8705c9bec2 in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:4363 #15 0x7f8705c887a4 in QSGRenderer::renderScene (bindable=..., this=0x7f86ac00c310) at scenegraph/coreapi/qsgrenderer.cpp:264 #16 QSGRenderer::renderScene (this=0x7f86ac00c310, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:220 #17 0x7f8705c88c43 in QSGRenderer::renderScene (this=, fboId=) at scenegraph/coreapi/qsgrenderer.cpp:212 #18 0x7f8705ce1915 in QSGDefaultRenderContext::renderNextFrame (this=0x5634dfceb2a0, renderer=0x7f86ac00c310, fboId=) at scenegraph/qsgdefaultrendercontext.cpp:228 #19 0x7f8705d3c4d9 in QQuickWindowPrivate::renderSceneGraph (this=0x5634dfb806c0, size=..., surfaceSize=...) at items/qquickwindow.cpp:617 #20 0x7f8705ced138 in QSGRenderThread::syncAndRender (this=0x5634e0278130, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:837 #21 0x7f8705cf186d in QSGRenderThread::run (this=0x5634e0278130) at scenegraph/qsgthreadedrenderloop.cpp:1043 #22 0x7f8717c63751 in QThreadPrivate::start (arg=0x5634e0278130) at thread/qthread_unix.cpp:329 #23 0x7f87175ce299 in start_thread (arg=0x7f86c55e0640) at pthread_create.c:473 #24 0x7f871788d6a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (LWP 7936 "plasma-s:gdrv0"): #1 0x7f87175daacf in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5634e04dff70, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7f87175d42b0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5634e04dff20, cond=0x5634e04dff48) at pthread_cond_wait.c:504 #3 __pthread_cond_wait (cond=0x5634e04dff48, mutex=0x5634e04dff20) at pthread_cond_wait.c:619 #4 0x7f86fc78a09b in cnd_wait (mtx=0x5634e04dff20,
[kstars] [Bug 430325] kstars segmentation faulted in DetailDialog::createGeneralTab
https://bugs.kde.org/show_bug.cgi?id=430325 --- Comment #7 from Matt Fagnani --- (In reply to Jasem Mutlaq from comment #4) > Cannot reproduce. Please try with more recent KStars (e.g. 3.5.2) KStars 3.4.3 is the most recent available version in Fedora 34 and rawhide as Bernie wrote. I installed the KStars 3.5.3 beta flatpak with the following based on https://community.kde.org/Guidelines_and_HOWTOs/Flatpak flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo flatpak remote-add --if-not-exists kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo flatpak install kstars flatpak run org.kde.kstars QWaylandShmBuffer: mmap failed (Invalid argument) was shown many times in Konsole as KStars started. The crash didn't happen when clicking on Pointing > Find Object, entering sagittarius in Filter by name, and selecting the Details button. The problem might've been fixed in 3.5.3 beta or earlier. The system is using Fedora 34 Plasma installation with Plasma 5.21.4, KF 5.80.0, Qt 5.15.2 with an integrated AMD Radeon R5 GPU using the radeonsi mesa 21.0.2 driver -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434403] Plasma on Wayland didn't start with a systemd error "user@1000.service: Failed to attach to cgroup /user.slice/user-1000.slice/user@1000.service: Device or resource busy" afte
https://bugs.kde.org/show_bug.cgi?id=434403 --- Comment #1 from Matt Fagnani --- I've continued to see this problem when I've logged out of Plasma 5.21.4 with KF 5.80.0 and logged in within about 40 seconds. If I logged in again after about 40-60 seconds, then Plasma started normally. When I rebooted or shut down from Plasma, a systemd message like "A stop job is running for User Manager for UID 1000" was shown for 40-60 seconds before the reboot or shutdown happened most of the time. I noticed in the KF 5.81.0 changelog for kded https://kde.org/announcements/frameworks/5/5.81.0/ the commit "make kded shut down cleanly during systemd session teardown" https://invent.kde.org/frameworks/kded/-/commit/96aa058b2b70bc19484e649b5bfcbb86d36336ff I changed /usr/lib/systemd/user/plasma-kded.service like in that commit by adding the line PartOf=graphical-session.target I logged in and out multiple times after that making that change, kded5 didn't abort during logout according to coredumpctl. Plasma started normally each time I logged in again within 10 seconds of logging out. That commit might be sufficient to avoid this problem. kwalletd5 still aborted when logging out, though kwalletd5 appears to just have a dbus-activated systemd service /usr/share/dbus-1/services/org.kde.kwalletd5.service and not a user session one like kded. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 434779] New: ksysguard segmentation faulted in QWidget::focusPolicy when closing
https://bugs.kde.org/show_bug.cgi?id=434779 Bug ID: 434779 Summary: ksysguard segmentation faulted in QWidget::focusPolicy when closing Product: ksysguard Version: 5.21.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.21.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.8-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.3 Distribution: Fedora 34 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: I opened ksysguard in Plasma 5.21.3 on Wayland in a Fedora 34 KDE Plasma installation. I sorted by the process name by clicking on the Name column header. I scrolled down through the processes. I closed ksysguard. ksysguard segmentation faulted in QWidget::focusPolicy at kernel/qwidget.cpp:7606 in qt5-qtbase-5.15.2-15.fc34.x86_64 when closing. This crash usually hasn't happened when closing ksysguard. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault [KCrash Handler] #4 0x7f8bea556918 in QWidget::focusPolicy (this=0x55ea13299900) at kernel/qwidget.cpp:7606 #5 0x7f8bea665022 in QLabelPrivate::needTextControl (this=0x55ea1302a980) at widgets/qlabel_p.h:99 #6 QLabel::setText (this=0x55ea12d3ebf0, text=...) at widgets/qlabel.cpp:344 #7 0x7f8beb453f2a in TopLevel::answerReceived (this=0x55ea12d1c340, id=, answerList=...) at /usr/src/debug/ksysguard-5.21.3-1.fc34.x86_64/gui/ksysguard.cpp:466 #8 0x7f8beb1a655e in KSGRD::SensorAgent::processAnswer (this=0x55ea130ceef0, buf=, buflen=) at /usr/src/debug/libksysguard-5.21.3.1-1.fc34.x86_64/ksgrd/SensorAgent.cpp:306 #9 0x7f8beb1aa520 in KSGRD::SensorShellAgent::msgRcvd (this=0x55ea130ceef0) at /usr/src/debug/libksysguard-5.21.3.1-1.fc34.x86_64/ksgrd/SensorShellAgent.cpp:93 #10 0x7f8be99374b0 in QtPrivate::QSlotObjectBase::call (a=0x7ffc54683100, r=, this=0x55ea13034d90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x55ea12fd73e0, signal_index=15, argv=0x7ffc54683100) at kernel/qobject.cpp:3886 #12 0x7f8be99319e7 in QMetaObject::activate (sender=, m=m@entry=0x7f8be9bca060 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffc54683100) at kernel/qobject.cpp:3946 #13 0x7f8be9898a31 in QProcess::readyReadStandardOutput (this=, _t1=...) at .moc/moc_qprocess.cpp:367 #14 0x7f8be989c42d in QProcessPrivate::tryReadFromChannel (this=0x55ea13037c70, channel=0x55ea13037d80) at io/qprocess.cpp:1073 #15 0x7f8be989c8f5 in QProcessPrivate::_q_canReadStandardError (this=) at io/qprocess.cpp:1092 #16 QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffc546832a0) at .moc/moc_qprocess.cpp:210 #17 0x7f8be99374fd in doActivate (sender=0x55ea13077d50, signal_index=3, argv=0x7ffc546832a0) at kernel/qobject.cpp:3898 #18 0x7f8be99319e7 in QMetaObject::activate (sender=sender@entry=0x55ea13077d50, m=m@entry=0x7f8be9bcc440 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc546832a0) at kernel/qobject.cpp:3946 #19 0x7f8be9939b3a in QSocketNotifier::activated (this=this@entry=0x55ea13077d50, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #20 0x7f8be993a2d4 in QSocketNotifier::event (this=0x55ea13077d50, e=) at kernel/qsocketnotifier.cpp:302 #21 0x7f8bea52de73 in QApplicationPrivate::notify_helper (this=, receiver=0x55ea13077d50, e=0x7ffc546833c0) at kernel/qapplication.cpp:3632 #22 0x7f8be9906f48 in QCoreApplication::notifyInternal2 (receiver=0x55ea13077d50, event=0x7ffc546833c0) at kernel/qcoreapplication.cpp:1063 #23 0x7f8be995417f in socketNotifierSourceDispatch (source=0x55ea12d416a0) at kernel/qeventdispatcher_glib.cpp:107 #24 0x7f8be04e5377 in g_main_dispatch (context=0x55ea12d3f620) at ../glib/gmain.c:3337 #25 g_main_context_dispatch (context=0x55ea12d3f620) at ../glib/gmain.c:4055 #26 0x7f8be05392c8 in g_main_context_iterate.constprop.0 (context=context@entry=0x55ea12d3f620, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #27 0x7f8be04e2ab3 in g_main_context_iteration (context=0x55ea12d3f620, may_block=1) at ../glib/gmain.c:4196 #28 0x7f8be99536f8 in QEventDispatcherGlib::processEvents (this=0x55ea12d41ca0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7f8be99059b2 in QEventLoop::exec (this=this@entry=0x7ffc54683630, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #30 0x7f8be990d544 in QCoreApplication::exec () at
[kwin] [Bug 434686] New: kwin_wayland aborted in egl_provider_resolver when the splash screen was shown
https://bugs.kde.org/show_bug.cgi?id=434686 Bug ID: 434686 Summary: kwin_wayland aborted in egl_provider_resolver when the splash screen was shown Product: kwin Version: 5.21.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I was logging into Plasma 5.21.3 on Wayland in a Fedora 34 KDE Plasma installation. The splash screen was shown. I moved the cursor to the top left of the screen, and the top left turned blue. kwin_wayland aborted in egl_provider_resolver at src/egl_generated_dispatch.c:3911 in libepoxy-1.5.5-2.fc34. The trace showed that kwin_wayland might've been destroying an EGL DMAbuf buffer in frames 3 to 8. Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 49return ret; [Current thread is 1 (Thread 0x7ffa879b8940 (LWP 5407))] (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #1 0x7ffa868a1950 in __GI_abort () at abort.c:100 #2 0x7ffa86e0bcb9 in egl_provider_resolver (name=name@entry=0x7ffa86e31b5c "eglDestroyImageKHR", providers=providers@entry=0x7ffa86e31704 , entrypoints=entrypoints@entry=0x7ffa86e316f8 ) at src/egl_generated_dispatch.c:3911 #3 0x7ffa86e0f55a in epoxy_eglDestroyImageKHR_resolver () at src/egl_generated_dispatch.c:4264 #4 epoxy_eglDestroyImageKHR_global_rewrite_ptr (dpy=0x55b7fbe3a490, image=0x55b7fca06680) at src/egl_generated_dispatch.c:5059 #5 0x7ffa73382be7 in KWin::EglDmabufBuffer::removeImages() (this=this@entry=0x55b7fca38d40) at /usr/src/debug/kwin-5.21.3-1.fc34.x86_64/platformsupport/scenes/opengl/egl_dmabuf.cpp:166 #6 0x7ffa73382d97 in KWin::EglDmabufBuffer::~EglDmabufBuffer() (this=0x55b7fca38d40, this=) at /usr/src/debug/kwin-5.21.3-1.fc34.x86_64/platformsupport/scenes/opengl/egl_dmabuf.cpp:150 #7 KWin::EglDmabufBuffer::~EglDmabufBuffer() (this=0x55b7fca38d40, this=) at /usr/src/debug/kwin-5.21.3-1.fc34.x86_64/platformsupport/scenes/opengl/egl_dmabuf.cpp:151 #8 0x7ffa8454f0cf in destroy_resource (element=0x55b7fca28d80, data=data@entry=0x0, flags=0) at ../src/wayland-server.c:724 #9 0x7ffa84550bb1 in wl_resource_destroy (resource=) at ../src/wayland-server.c:741 #10 0x7ffa81db9c04 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #11 0x7ffa81db9107 in ffi_call (cif=cif@entry=0x7ffc41d5cd00, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffc41d5cdd0) at ../src/x86/ffi64.c:525 #12 0x7ffa8454c670 in wl_closure_invoke --Type for more, q to quit, c to continue without paging--c (closure=closure@entry=0x55b7fcdf7cf0, target=, target@entry=0x55b7fca28d80, opcode=opcode@entry=0, data=, data@entry=0x55b7fc9f6320, flags=) at ../src/connection.c:1018 #13 0x7ffa845506e4 in wl_client_connection_data (fd=, mask=, data=0x55b7fc9f6320) at ../src/wayland-server.c:432 #14 0x7ffa8454f21a in wl_event_loop_dispatch (loop=0x55b7fbc19230, timeout=) at ../src/event-loop.c:1027 #15 0x7ffa86f59c6a in KWaylandServer::Display::dispatchEvents() (this=) at /usr/src/debug/kwayland-server-5.21.3-1.fc34.x86_64/src/server/display.cpp:107 #16 0x7ffa883b24b0 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc41d5d3f0, r=, this=0x55b7fbc0edd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate(QObject*, int, void**) (sender=0x55b7fc625520, signal_index=3, argv=0x7ffc41d5d3f0) at kernel/qobject.cpp:3886 #18 0x7ffa883ac9e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55b7fc625520, m=m@entry=0x7ffa88647440 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc41d5d3f0) at kernel/qobject.cpp:3946 #19 0x7ffa883b4b3a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x55b7fc625520, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #20 0x7ffa883b52d4 in QSocketNotifier::event(QEvent*) (this=0x55b7fc625520, e=) at kernel/qsocketnotifier.cpp:302 #21 0x7ffa87380e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b7fc625520, e=0x7ffc41d5d510) at kernel/qapplication.cpp:3632 #22 0x7ffa88381f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b7fc625520, event=0x7ffc41d5d510) at kernel/qcoreapplication.cpp:1063 #23 0x7ffa883cba6e in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x55b7fbbe7720) at kernel/qeventdispatcher_unix.cpp:304 #24 0x7ffa883cbde5 in
[plasmashell] [Bug 434403] New: Plasma on Wayland didn't start with a systemd error "user@1000.service: Failed to attach to cgroup /user.slice/user-1000.slice/user@1000.service: Device or resource bus
https://bugs.kde.org/show_bug.cgi?id=434403 Bug ID: 434403 Summary: Plasma on Wayland didn't start with a systemd error "user@1000.service: Failed to attach to cgroup /user.slice/user-1000.slice/user@1000.service: Device or resource busy" after logging out Product: plasmashell Version: 5.21.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I've logged out of Plasma 5.21.2 and earlier on Wayland in a Fedora 34 KDE Plasma installation, kded5, kwalletd5, drkonqi, and sometimes xdg-desktop-portal-kde have aborted with errors like "The Wayland connection broke. Did the Wayland compositor die?" likely because kwin stopped before they did. Mar 13 19:46:35 systemd[1124]: Created slice app-dbus\x2d:1.2\x2dorg.kde.LogoutPrompt.slice. Mar 13 19:46:35 systemd[1124]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service. Mar 13 19:46:35 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 13 19:46:35 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 13 19:46:35 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :406:376: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :407:130: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :408:130: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :408:393: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :409:130: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :410:129: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :411:129: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :412:129: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :413:129: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :413:379: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.svg: :413:631: Could not add child element to parent element because the types are incorrect. Mar 13 19:46:36 ksmserver-logout-greeter[8050]: file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserDelegate.qml:34: ReferenceError: model is not defined Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Mar 13 19:46:36 ksmserver-logout-greeter[8050]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Mar 13 19:46:37 systemd[1124]: Created slice app-dbus\x2d:1.2\x2dorg.kde.Shutdown.slice. Mar 13 19:46:37 systemd[1124]: Started dbus-:1.2-org.kde.Shutdown@0.service. Mar 13 19:46:37 systemd[1124]: plasma-xembedsniproxy.service: Deactivated successfully. Mar 13 19:46:37 systemd[1124]: Stopped target KDE Plasma Workspace. Mar 13 19:46:37 systemd[1124]: Stopped target KDE Plasma Workspace Core. Mar 13 19:46:37 systemd[1124]: plasma-ksmserver.service: Deactivated successfully. Mar 13 19:46:37 systemd[1124]: Stopped KDE Session Management Server. Mar 13 19:46:37 systemd[1124]: plasma-gmenudbusmenuproxy.service: Deactivated successfully. Mar 13 19:46:37 systemd[1124]: Stopped Proxies GTK DBus menus to a Plasma readable format. Mar 13 19:46:37 systemd[1124]: Stopped target Startup of XDG autostart applications. Mar 13 19:46:37 systemd[1124]: Stopping Geoclue Demo agent... Mar 13 19:46:37 systemd[1124]: Stopping Problem Reporting... Mar 13 19:46:37 systemd[1124]: Stopping Evolution Alarm Notify... Mar 13 19:46:37 systemd[1124]: Stopping Discover... Mar 13 19:46:37 systemd[1124]: Stopping Dolphin... Mar 13 19:46:37 systemd[1124]: Stopping KOrganizer Reminder Client... Mar 13 19:46:37 systemd[1124]: Stopping SELinux Troubleshooter... Mar 13 19:46:37 systemd[1124]: Stopping KActivityManager Activity manager Service... Mar 13 19:46:37 systemd[1124]: Stopping KDE Plasma Workspace... Mar 13 19:46:37 systemd[1124]: Stopping KDE PolicyKit
[plasma-systemmonitor] [Bug 434074] System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root
https://bugs.kde.org/show_bug.cgi?id=434074 --- Comment #1 from Matt Fagnani --- I ran gdb plasma-systemmonitor and terminated abrt-dump-journal-xorg as I described. The segmentation fault was shown in QWidget::effectiveWinId which was frame 1 in the original trace. The polkit and kauth functions in kf5-kauth-5.79.0-2.fc34 in frames 1 and 2 might indicate that the KDE PolicyKit agent was in the process of starting when the crash happened. (gdb) bt #0 QWidget::effectiveWinId() const (this=0x57385, this@entry=0x7fffa3f0) at kernel/qwidget.cpp:2462 #1 0x7fff92695931 in KAuth::Polkit1Backend::preAuthAction(QString const&, QWidget*) (this=, action=..., parent=0x7fffa3f0) at /usr/src/debug/kf5-kauth-5.79.0-2.fc34.x86_64/src/backends/polkit-1/Polkit1Backend.cpp:63 #2 0x74fe11cb in KAuth::ExecuteJob::Private::doExecuteAction() (this=0x583fc330) at /usr/src/debug/kf5-kauth-5.79.0-2.fc34.x86_64/src/kauthexecutejob.cpp:142 #3 0x768fc257 in QObject::event(QEvent*) (this=0x583fc260, e=0x583fc380) at kernel/qobject.cpp:1314 #4 0x773f0e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x583fc260, e=0x583fc380) at kernel/qapplication.cpp:3632 #5 0x768d4f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x583fc260, event=0x583fc380) at kernel/qcoreapplication.cpp:1063 #6 0x768d7c76 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55586d80) at kernel/qcoreapplication.cpp:1817 #7 0x76921c57 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x555b5350) at kernel/qeventdispatcher_glib.cpp:277 #8 0x7542c3d7 in g_main_dispatch (context=0x555c6ae0) at ../glib/gmain.c:3337 #9 g_main_context_dispatch (context=0x555c6ae0) at ../glib/gmain.c:4055 #10 0x75480518 in g_main_context_iterate.constprop.0 (context=context@entry=0x555c6ae0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #11 0x75429b13 in g_main_context_iteration (context=0x555c6ae0, may_block=1) at ../glib/gmain.c:4196 #12 0x769216f8 in QEventDispatcherGlib::processEvents(QFlags) --Type for more, q to quit, c to continue without paging--c (this=0x555b58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #13 0x768d39b2 in QEventLoop::exec(QFlags) (this=0x7fffa940, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #14 0x77975f7e in KJob::exec() (this=this@entry=0x583fc260) at /usr/include/qt5/QtCore/qflags.h:121 #15 0x7fff91f92e82 in KSysGuard::ProcessController::Private::runKAuthAction(QString const&, QVector const&, QMap const&) (this=this@entry=0x57385580, actionId=..., pids=..., options=...) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:269 #16 0x7fff91f932ad in KSysGuard::ProcessController::sendSignal(QVector const&, int) (this=0x7fffaac8, this@entry=0x57385b90, pids=..., signal=-21880, signal@entry=15) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:86 #17 0x7fff91f938d6 in KSysGuard::ProcessController::sendSignal(QList const&, int) (this=0x57385b90, pids=, signal=15) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:100 #18 0x7fff91f7e147 in KSysGuard::ProcessController::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x57385b90, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7fffad20) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/x86_64-redhat-linux-gnu/processcore/processcore_autogen/EWIEGA46WW/moc_process_controller.cpp:165 #19 0x7fff91f7e383 in KSysGuard::ProcessController::qt_metacall(QMetaObject::Call, int, void**) (this=0x57385b90, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffad20) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/x86_64-redhat-linux-gnu/processcore/processcore_autogen/EWIEGA46WW/moc_process_controller.cpp:282 #20 0x77e01b25 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=0x7fffafc0, type=QMetaObject::InvokeMetaMethod, index=, argv=) at qml/qqmlobjectorgadget.cpp:51 #21 0x77d081cb in CallMethod (callType=, callArgs=0x7fffadd0, engine=, argTypes=, argCount=, returnType=, index=, object=) at /usr/include/qt5/QtCore/qvarlengtharray.h:201 #22 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=..., data=..., engine=engine@entry=0x55670090, callArgs=callArgs@entry=0x7fffe210e598, callType=callType@entry=QMetaObject::InvokeMetaMethod) at jsruntime/qv4qobjectwrapper.cpp:1569 #23 0x77d0927b in CallOverloaded (callTy
[kwin] [Bug 434056] Menu items under the cursor usually aren't highlighted in Firefox 86.0-88.0a1 on Wayland
https://bugs.kde.org/show_bug.cgi?id=434056 --- Comment #3 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #1) > > Vlad Zahorodnii's comments on that report seemed to indicate that the > > underlying problem might involve kwin_wayland > > No, I just indicated that kwin might be doing something that other > compositors don't. It still looks like a Firefox bug, not a compositor bug. I didn't mean that your comments indicated that the underlying problem was in kwin_wayland. I just meant that you seemed to say the difference in the way that kwin_wayland handled the issue with the Wayland buffers could be involved in why it shows up in Plasma as opposed to other desktops. I haven't been able to reproduce this problem in GNOME 40 beta. Do you have ideas on how the issue could be addressed? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434115] Flickering of right-click popup menus with multiple simultaneously highlighted entries in Thunderbird on Wayland in Plasma
https://bugs.kde.org/show_bug.cgi?id=434115 --- Comment #1 from Matt Fagnani --- Created attachment 136468 --> https://bugs.kde.org/attachment.cgi?id=136468=edit Thunderbird Wayland debug log I ran MOZ_ENABLE_WAYLAND=1 WAYLAND_DEBUG=1 thunderbird & I right-clicked on an email and saw the flickering and multiple highlighted menu items a few times. The attached Wayland debug log showed some repeated lines around when the problem happened like the following. [1818472.163] wl_pointer@3.enter(1640, wl_surface@41, 599.00, 695.00) [1818472.234] -> wl_pointer@3.set_cursor(1640, wl_surface@14, 4, 4) [1818472.289] -> wl_surface@14.attach(wl_buffer@55, 0, 0) [1818472.331] -> wl_surface@14.set_buffer_scale(1) [1818472.356] -> wl_surface@14.damage(0, 0, 32, 32) [1818472.408] -> wl_surface@14.commit() [1818472.433] wl_pointer@3.frame() [1818619.844] wl_pointer@3.motion(684063, 597.00, 687.00) [1818619.934] wl_pointer@3.frame() [1818619.979] wl_pointer@3.motion(684069, 593.00, 677.00) [1818620.027] wl_pointer@3.frame() [1818620.042] wl_pointer@3.motion(684077, 590.00, 668.00) [1818620.058] wl_pointer@3.frame() [1818620.068] wl_pointer@3.motion(684085, 587.00, 659.00) [1818620.082] wl_pointer@3.frame() [1818620.091] wl_pointer@3.motion(684093, 584.00, 647.00) [1818620.105] wl_pointer@3.frame() [1818620.116] wl_pointer@3.motion(684101, 581.00, 633.00) [1818620.132] wl_pointer@3.frame() [1818620.141] wl_pointer@3.motion(684109, 575.00, 612.00) [1818620.178] wl_pointer@3.frame() [1818620.190] wl_pointer@3.motion(684117, 569.00, 595.00) [1818620.206] wl_pointer@3.frame() [1818620.215] wl_pointer@3.motion(684125, 559.00, 575.00) [1818620.229] wl_pointer@3.frame() [1818620.238] wl_pointer@3.motion(684133, 549.00, 555.00) [1818620.252] wl_pointer@3.frame() [1818620.277] wl_pointer@3.motion(684141, 541.00, 533.00) [1818620.291] wl_pointer@3.frame() [1818620.320] wl_pointer@3.motion(684149, 533.00, 509.00) [1818620.334] wl_pointer@3.frame() [1818620.348] wl_pointer@3.motion(684155, 525.00, 491.00) [1818620.363] wl_pointer@3.frame() [1818620.375] wl_pointer@3.motion(684163, 521.00, 471.00) [1818620.388] wl_pointer@3.frame() [1818620.396] wl_pointer@3.motion(684171, 518.00, 456.00) [1818620.410] wl_pointer@3.frame() [1818620.423] wl_pointer@3.motion(684179, 514.00, 440.00) [1818620.435] wl_pointer@3.frame() [1818620.445] wl_pointer@3.motion(684187, 509.00, 421.00) [1818620.459] wl_pointer@3.frame() [1818620.471] wl_pointer@3.motion(684195, 505.00, 402.00) [1818620.484] wl_pointer@3.frame() [1818620.495] wl_pointer@3.motion(684203, 501.00, 387.00) [1818620.508] wl_pointer@3.frame() [1818658.219] wl_buffer@66.release() [1818658.267] wl_callb...@79.done(1638) [1818658.290] wl_buffer@68.release() [1818658.320] -> wl_buffer@68.destroy() [1818663.311] -> wl_surface@49.attach(wl_buffer@66, 0, 0) [1818663.408] -> wl_surface@49.damage(0, 0, 2147483647, 2147483647) [1818663.447] -> wl_surface@49.commit() [1818663.460] -> wl_disp...@1.sync(new id wl_callback@79) [1818766.889] wl_display@1.delete_id(68) [1818766.937] wl_display@1.delete_id(79) The right-click menu problem happened a few times from around the lines above to the end. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434115] New: Flickering of right-click popup menus with multiple simultaneously highlighted entries in Thunderbird on Wayland in Plasma
https://bugs.kde.org/show_bug.cgi?id=434115 Bug ID: 434115 Summary: Flickering of right-click popup menus with multiple simultaneously highlighted entries in Thunderbird on Wayland in Plasma Product: kwin Version: 5.21.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY The menus shown when right-clicking on an email item in a list of emails in Thunderbird 78.8.0 and earlier on Wayland flickered and had multiple simultaneously highlighted items when moving the cursor up and down them in Plasma 5.21.2 and earlier in Fedora 34. This problem occurred in Thunderbird 78.8.0 on Wayland with OpenGL, WebRender, and in Safe mode with Basic compositing. Thunderbird on X hasn't had this problem with the same versions. The underlying issue might be in kwin_wayland. I haven't been able to reproduce this problem in Thunderbird 78.8.0 on Wayland in GNOME 40 beta on Wayland in Fedora 34. STEPS TO REPRODUCE 1. Boot a Fedora 34 KDE Plasma installation updated to 2021-3-7 with the updates-testing repo enabled 2. Log in to Plasma 5.21.2 on Wayland 3. Start Thunderbird on Wayland MOZ_ENABLE_WAYLAND=1 thunderbird 4. right-click on an email in a list of emails in a folder 5. move the cursor up and down the right-click menu 6. If the flickering didn't happen, repeat 4-5 until it does OBSERVED RESULT Flickering of right-click popup menus with multiple simultaneously highlighted entries in Thunderbird on Wayland in Plasma EXPECTED RESULT The right-click menus would appear normally without flickering, and only the menu item under the cursor would be highlighted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I reported the same problem of flickering and multiple highlighted items with right-click menus in Firefox Nighly 81.0a1 (2020-8-21) on Wayland in Plasma 5.19.4 in Fedora 33 at https://bugzilla.mozilla.org/show_bug.cgi?id=1660567 I haven't been seeing this problem in Firefox Nightly 86.0a1 (2021-1-15) - 88.0a1 (2021-3-6) and 86.0 on Wayland with WebRender enabled in Fedora 34 with Plasma 5.21.2 and earlier due to the menu items under the cursor not usually being highlighted as I reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1693472 Since Firefox and Thunderbird are based on the same rendering engine, the problems are likely related. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434074] New: System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root
https://bugs.kde.org/show_bug.cgi?id=434074 Bug ID: 434074 Summary: System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root Product: plasma-systemmonitor Version: 5.21.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY System Monitor 5.21.2 segmentation faulted in QWidget::internalWinId() at kernel/qwidget.h:222 in qt5-qtbase-5.15.2-13.fc34.x86_64 when terminating processes running as root. These crashes happened 4 of 4 times when running Plasma 5.21.2 on Wayland in a Fedora 34 KDE Plasma installation. I first noticed this crash after I stopped a backup with backintime and closed it. I saw rsync processes running as root still running in System Monitor, and I tried to terminate one rsync process. The second such crash happened when I tried to terminate the autostarted process /usr/bin/python3 -Es /usr/share/backintime/qt/serviceHelper.py from backintime. The trace below was from when I tried to terminate abrt-dump-journal-xorg which was running as root from the Processes screen by right clicking on abrt-dump-journal-xorg, selected Send Signal > Terminate, then End in the End Process box. The traces of the first 3 crashes looked the same. The crash happened before I guess that the KDE PolicyKit program would've appeared to prompt for a password. Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7fe64771e72b in QWidget::internalWinId() const (this=0x557486073) at kernel/qwidget.h:222 #5 QWidget::effectiveWinId() const (this=0x557486073, this@entry=0x7186b900) at kernel/qwidget.cpp:2462 #6 0x7fe5e1e24931 in KAuth::Polkit1Backend::preAuthAction(QString const&, QWidget*) (this=, action=..., parent=0x7186b900) at /usr/src/debug/kf5-kauth-5.79.0-2.fc34.x86_64/src/backends/polkit-1/Polkit1Backend.cpp:63 #7 0x7fe64528f1cb in KAuth::ExecuteJob::Private::doExecuteAction() (this=0x5574870113b0) at /usr/src/debug/kf5-kauth-5.79.0-2.fc34.x86_64/src/kauthexecutejob.cpp:142 #8 0x7fe646bf5257 in QObject::event(QEvent*) (this=0x557486963040, e=0x5574864ef780) at kernel/qobject.cpp:1314 #9 0x7fe6476f4e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x557486963040, e=0x5574864ef780) at kernel/qapplication.cpp:3632 #10 0x7fe646bcdf48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x557486963040, event=0x5574864ef780) at kernel/qcoreapplication.cpp:1063 #11 0x7fe646bd0c76 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55748437bd80) at kernel/qcoreapplication.cpp:1817 #12 0x7fe646c1ac57 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5574843aa350) at kernel/qeventdispatcher_glib.cpp:277 #13 0x7fe6456e43d7 in g_main_dispatch (context=0x5574843bbbd0) at ../glib/gmain.c:3337 #14 g_main_context_dispatch (context=0x5574843bbbd0) at ../glib/gmain.c:4055 #15 0x7fe645738518 in g_main_context_iterate.constprop.0 (context=context@entry=0x5574843bbbd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #16 0x7fe6456e1b13 in g_main_context_iteration (context=0x5574843bbbd0, may_block=1) at ../glib/gmain.c:4196 #17 0x7fe646c1a6f8 in QEventDispatcherGlib::processEvents(QFlags) (this=0x5574843aa810, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #18 0x7fe646bcc9b2 in QEventLoop::exec(QFlags) (this=0x7186be50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x7fe647c7ef7e in KJob::exec() (this=this@entry=0x557486963040) at /usr/include/qt5/QtCore/qflags.h:121 #20 0x7fe5e1982e82 in KSysGuard::ProcessController::Private::runKAuthAction(QString const&, QVector const&, QMap const&) (this=this@entry=0x557486073270, actionId=..., pids=..., options=...) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:269 #21 0x7fe5e19832ad in KSysGuard::ProcessController::sendSignal(QVector const&, int) (this=0x7186bfd8, this@entry=0x557486073880, pids=..., signal=-242827368, signal@entry=15) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:86 #22 0x7fe5e19838d6 in KSysGuard::ProcessController::sendSignal(QList const&, int) (this=0x557486073880, pids=, signal=15) at /usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:100 #23 0x7fe5e196e147 in KSysGuard::ProcessController::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x557486073880,
[kwin] [Bug 434056] New: Menu items under the cursor usually aren't highlighted in Firefox 86.0-88.0a1 on Wayland
https://bugs.kde.org/show_bug.cgi?id=434056 Bug ID: 434056 Summary: Menu items under the cursor usually aren't highlighted in Firefox 86.0-88.0a1 on Wayland Product: kwin Version: 5.21.2 Platform: Fedora RPMs URL: https://bugzilla.mozilla.org/show_bug.cgi?id=1693472 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Flags: Wayland+, X11- SUMMARY When I click on menus in the menu bar of Firefox Nightly 86.0a1 (2021-1-15) - 88.0a1 (2021-3-6) and 86.0 on Wayland with WebRender enabled in a Fedora 34 KDE Plasma installation with Plasma 5.21.2 and earlier, the menu items under the cursor usually aren't highlighted. Sometimes just the first item in the menu was highlighted. Occasionally multiple items in the menu were highlighted at the same time. The menus shown when right-clicking on a page are also affected by this issue. This problem started with 86.0a1 (2021-1-15). I ran the following to look for the commit involved MOZ_ENABLE_WAYLAND=1 mozregression --good 2021-1-13 --bad 2021-1-18 The end of the process showed 13:17.81 INFO: Narrowed integration regression window from [25680895, 8a9e98e5] (4 builds) to [376c2ff6, 8a9e98e5] (2 builds) (~1 steps left) 13:17.81 INFO: No more integration revisions, bisection finished. 13:17.81 INFO: Last good revision: 376c2ff62872fbf7cc25803f9cbdcd42f8c1fe6c 13:17.81 INFO: First bad revision: 8a9e98e50d031c7a72429a08aad7325f50e34d2e 13:17.81 INFO: Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=376c2ff62872fbf7cc25803f9cbdcd42f8c1fe6c=8a9e98e50d031c7a72429a08aad7325f50e34d2e The first bad revision was https://hg.mozilla.org/integration/autoland/rev/8a9e98e50d031c7a72429a08aad7325f50e34d2e Bug 1686703 [Wayland] Merge GetWaylandBufferWithSwitch()/GetWaylandBufferRecent() to GetWaylandBuffer(), r=jhorak Depends on D101746 Differential Revision: https://phabricator.services.mozilla.com/D101747 The problem doesn't affect 86.0a1-88.0a1 and 86.0 on X in Plasma on Wayland with the same Firefox settings and system versions. STEPS TO REPRODUCE 1. Boot a Fedora 34 KDE Plasma installation updated to 2021-3-6 with the updates-testing repo enabled 2. Log in to Plasma 5.21.2 on Wayland 3. Install firefox-wayland if it isn't already with sudo dnf install firefox-wayland 4 Start Firefox on Wayland with WebRender compositing enabled 5. Show the menu bar if it isn't already by right-clicking on the tab area and selecting Menu bar 5. Select the Bookmarks menu 6. Move the cursor up and down over the Bookmarks menu 7. Repeat 5-6 for other menus in the menu bar 8. Go to a site such as https://bugzilla.mozilla.org 9. Right-click somewhere on the page 10. Move the cursor up and down the right-click menu OBSERVED RESULT Menu items under the cursor usually aren't highlighted in Firefox 86.0-88.0a1 on Wayland EXPECTED RESULT Menu items under the cursor would be highlighted normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I reported this problem at https://bugzilla.mozilla.org/show_bug.cgi?id=1693472 Vlad Zahorodnii's comments on that report seemed to indicate that the underlying problem might involve kwin_wayland. I'm unsure if the problem is in Firefox or kwin_wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Matt Fagnani changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #10 from Matt Fagnani --- (In reply to Nate Graham from comment #9) > > #7 QMessageLogger::fatal (this=this@entry=0x7ffe06a40c50, > > msg=msg@entry=0x7fa6b48a11c0 "The Wayland connection experienced a fatal > > error: %s") at global/qlogging.cpp:893 > This means that kwin_wayland crashed. When it does so, it takes down apps > with it, and they die with this error message. So we will need to find out > why KWin crashed and debug that. If you still have a backtrace for it, can > you attach it? Thanks! > > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl kwin_wayland didn't crash at the times of the plasmashell crashes I reported here according to the journals I saved when they happened. I would've mentioned that kwin_wayland crashed if it had. The error was that an invalid argument was passed between plasmashell and kwin_wayland. I reproduced this plasmashell crash twice in Plasma 5.20.0 on Wayland with KF 5.79 and Qt 5.15.2 by repeatedly clicking to open and close the Application Launcher menu at the bottom left of the screen. The first such crash happened when I clicked several times in 1-2 seconds on the Application Launcher menu button. plasmashell crashed and went black. The window open at the time and the cursor remained responsive. drkonqi didn't appear and core dump wasn't saved probably because plasmashell didn't restart automatically. The journal at the time showed the following. Feb 24 11:06:31 plasmashell[1219]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Feb 24 11:06:31 plasmashell[1219]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Feb 24 11:06:31 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:31 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:31 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:32 plasmashell[1219]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Feb 24 11:06:32 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:32 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:32 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:32 plasmashell[1219]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Feb 24 11:06:32 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:32 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:32 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:33 plasmashell[1219]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Feb 24 11:06:33 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:33 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:33 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:33 plasmashell[1219]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Feb 24 11:06:33 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:33 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:33 plasmashell[1219]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_219(0x55df6f0792a0, name="popupWindow") Feb 24 11:06:34 plasmashell[1219]: KCrash: Application 'plasmashell' crashing... Feb
[rkward] [Bug 433398] New: RKWard segmentation faulted in QString::isEmpty when closing
https://bugs.kde.org/show_bug.cgi?id=433398 Bug ID: 433398 Summary: RKWard segmentation faulted in QString::isEmpty when closing Product: rkward Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I was using a Fedora 34 KDE Plasma installation with Plasma 5.21.0 on Wayland. I updated the system with sudo dnf upgrade. The update included R-4.0.4-1.fc34.x86_64 and rkward-0.7.2-2.fc34.x86_64. I rebooted and logged in to Plasma on Wayland. I started RKWard and selected Start with an empty workspace and OK. I closed RKWard by clicking the x button at the top right and selecting Discard in the box with Quitting RKWard: Do you want to save the workspace? RKWard segmentation faulted in QString::isEmpty at ../../include/QtCore/../../src/corelib/text/qstring.h:1078 in qt5-qtbase-5.15.2-13.fc34.x86_64 when closing. Core was generated by `/usr/libexec/rkward.rbackend --debug-level=3 --server-name=%2Ftmp%2FrkwardLHFpQ'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f39e74bcd3b in QString::isEmpty (this=) at ../../include/QtCore/../../src/corelib/text/qstring.h:1078 1078../../include/QtCore/../../src/corelib/text/qstring.h: No such file or directory. [Current thread is 1 (Thread 0x7f39b2f87640 (LWP 15055))] (gdb) bt #0 0x7f39e74bcd3b in QString::isEmpty (this=) at ../../include/QtCore/../../src/corelib/text/qstring.h:1078 #1 QIODevice::errorString (this=0x0) at io/qiodevice.cpp:2102 #2 0x5652fe39e2e6 in RKAbstractTransmitter::disconnected (this=0x7ffc50159bd0) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/rbackend/rktransmitter.cpp:270 #3 0x7f39e75874b0 in QtPrivate::QSlotObjectBase::call (a=0x7f39b2f85dd0, r=, this=0x7f39ac006560) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #4 doActivate (sender=0x7f39ac0051f0, signal_index=10, argv=0x7f39b2f85dd0) at kernel/qobject.cpp:3886 #5 0x7f39e75874fd in doActivate (sender=0x7f39ac0052d0, signal_index=11, argv=0x7f39b2f85ea0) at kernel/qobject.cpp:3898 #6 0x7f39e75819e7 in QMetaObject::activate (sender=sender@entry=0x7f39ac0052d0, m=m@entry=0x7f39e7a14d80 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #7 0x7f39e796edf7 in QAbstractSocket::disconnected (this=this@entry=0x7f39ac0052d0) at .moc/moc_qabstractsocket.cpp:404 #8 0x7f39e796f6c1 in QAbstractSocket::disconnectFromHost (this=0x7f39ac0052d0) at socket/qabstractsocket.cpp:2814 #9 0x5652fe3a1ceb in RKRBackendTransmitter::doExit (this=0x7ffc50159bd0) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/rbackend/rkbackendtransmitter.cpp:79 #10 0x7f39e757e257 in QObject::event (this=0x7ffc50159bd0, e=0x56530012be90) at kernel/qobject.cpp:1314 #11 0x7f39e7556f2b in doNotify (event=0x56530012be90, receiver=0x7ffc50159bd0) at kernel/qcoreapplication.cpp:1153 #12 QCoreApplication::notify (event=, receiver=, this=) --Type for more, q to quit, c to continue without paging--c at kernel/qcoreapplication.cpp:1139 #13 QCoreApplication::notifyInternal2 (receiver=0x7ffc50159bd0, event=0x56530012be90) at kernel/qcoreapplication.cpp:1063 #14 0x7f39e7559c76 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5652ff71d4e0) at kernel/qcoreapplication.cpp:1817 #15 0x7f39e75a3c57 in postEventSourceDispatch (s=s@entry=0x7f39ac004fe0) at kernel/qeventdispatcher_glib.cpp:277 #16 0x7f39e5ced0ff in g_main_dispatch (context=0x7f39ac000c20) at ../glib/gmain.c:3337 #17 g_main_context_dispatch (context=0x7f39ac000c20) at ../glib/gmain.c:4055 #18 0x7f39e5d40c98 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f39ac000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #19 0x7f39e5cea9f3 in g_main_context_iteration (context=0x7f39ac000c20, may_block=1) at ../glib/gmain.c:4196 #20 0x7f39e75a36f8 in QEventDispatcherGlib::processEvents (this=0x7f39ac000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f39e75559b2 in QEventLoop::exec (this=this@entry=0x7f39b2f862b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f39e73bd49a in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x7f39e73be751 in QThreadPrivate::start (arg=0x7ffc50159bd0) at thread/qthread_unix.cpp:329 #24 0x7f39e7a29269 in start_thread (arg=0x7f39b2f87640) at pthread_create.c:473 #25 0x7f39e6fe8663 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 RKWard 0.7.2 crashed in this way 7 of 7 times I've closed it. The first 5 core dumps
[systemsettings] [Bug 433192] New: System Settings on Wayland aborted when clearing history of activities with a failed dbus assertion
https://bugs.kde.org/show_bug.cgi?id=433192
Bug ID: 433192
Summary: System Settings on Wayland aborted when clearing
history of activities with a failed dbus assertion
Product: systemsettings
Version: 5.21.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_activities
Assignee: ivan.cu...@kde.org
Reporter: matthew.fagn...@utoronto.ca
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
I was using Plasma 5.21.0 on Wayland in a Fedora 34 KDE Plasma installation
with KF 5.79, Qt 5.15.2, Mesa 21.0.0-rc4. I started System Settings. I entered
activities in the search bar and selected Activities in the left bar. I
selected Privacy in the Activities screen. I had previously set Keep history: 1
month and Remember opened documents: Do not remember. I selected the Clear
History box and Forget Everything. System Settings aborted with a failed dbus
assertion 'arguments to dbus_message_new_method_call() were incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file
../../dbus/dbus-message.c line 1366.' as shown in the following journal output
at the time of the crash.
Feb 18 13:00:16 systemd[4038]: Started System Settings - System Settings.
Feb 18 13:00:17 systemsettings5[6689]: kf.coreaddons: Two plugins with the same
interface( QObject ) were registered. Use keywords to identify the plugins.
Feb 18 13:00:17 systemsettings5[6689]: kf.coreaddons: Two plugins with the same
interface( QObject ) were registered. Use keywords to identify the plugins.
Feb 18 13:00:17 systemsettings5[6689]: kf.coreaddons: Two plugins with the same
interface( QObject ) were registered. Use keywords to identify the plugins.
Feb 18 13:00:17 systemsettings5[6689]:
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:157:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
Feb 18 13:00:17 systemsettings5[6689]:
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:147:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
Feb 18 13:00:17 systemsettings5[6689]:
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
Feb 18 13:00:17 systemsettings5[6689]: qt.qpa.wayland: Wayland does not support
QWindow::requestActivate()
Feb 18 13:00:26 systemsettings5[6689]: QQmlEngine::setContextForObject():
Object already has a QQmlContext
Feb 18 13:00:26 systemsettings5[6689]: QQmlEngine::setContextForObject():
Object already has a QQmlContext
Feb 18 13:00:41 plasmashell[6689]: dbus[6689]: arguments to
dbus_message_new_method_call() were incorrect, assertion
"_dbus_check_is_valid_path (path)" failed in file ../../dbus/dbus-message.c
line 1366.
Feb 18 13:00:41 plasmashell[6689]: This is normally a bug in some application
using the D-Bus library.
Feb 18 13:00:41 plasmashell[6689]: D-Bus not built with -rdynamic so unable
to print a backtrace
Feb 18 13:00:41 plasmashell[6689]: KCrash: Application 'systemsettings5'
crashing...
Feb 18 13:00:41 plasmashell[6689]: KCrash: Attempting to start
/usr/libexec/drkonqi
The trace showed the failed dbus assertion in frame 7.
Application: System Settings (systemsettings5), signal: Aborted
[KCrash Handler]
#4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5 0x7fa382b2e8a4 in __GI_abort () at abort.c:79
#6 0x7fa380c50b16 in _dbus_abort () at ../../dbus/dbus-sysdeps.c:93
#7 0x7fa380c77010 in _dbus_warn_check_failed (format=0x7fa380c83b50
"arguments to %s() were incorrect, assertion \"%s\" failed in file %s line
%d.\nThis is normally a bug in some application using the D-Bus library.\n") at
../../dbus/dbus-internals.c:281
#8 0x7fa380c66ca2 in dbus_message_new_method_call
(destination=0x5602927bf178 "org.kde.ActivityManager", path=0x56029240b4f8
"/ActivityManager/Resources / Scoring", iface=0x56029240b0b8
"org.freedesktop.DBus.Introspectable", method=0x560292d8e948 "Introspect") at
../../dbus/dbus-message.c:1366
#9 0x7fa3820d3125 in q_dbus_message_new_method_call (method=0x560292d8e948
"Introspect", interface=0x56029240b0b8 "org.freedesktop.DBus.Introspectable",
path=, bus_name=) at
/usr/src/debug/qt5-qtbase-5.15.2-13.fc34.x86_64/src/dbus/qdbus_symbols_p.h:381
#10 QDBusMessagePrivate::toDBusMessage(QDBusMessage const&,
QFlags, QDBusError*) (message=...,
capabilities=..., error=error@entry=0x7ffedc1709e0) at qdbusmessage.cpp:139
#11 0x7fa3820cc76f in
QDBusConnectionPrivate::sendWithReplyAsync(QDBusMessage const&, QObject*, char
[rkward] [Bug 433040] New: RKWard aborted after installing recommended packages
https://bugs.kde.org/show_bug.cgi?id=433040 Bug ID: 433040 Summary: RKWard aborted after installing recommended packages Product: rkward Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I was using a Fedora 34 KDE Plasma installation with Plasma 5.21.0 on Wayland. I updated the system with sudo dnf upgrade. The update included R-4.0.4-1.fc34.x86_64 and rkward-0.7.2-2.fc34.x86_64. I rebooted and logged in to Plasma on Wayland. I started RKWard, and its wizard suggested that I install R2Html and rmarkdown. I installed those packages with their ~15 dependencies to /usr/lib64/R/library as root. The installation completed succesfully. I clicked Done in the installation window. RKWard aborted right after that. The functions at the top of the stack seem to indicate some sort of memory management error such as a bad allocation in frames 8-9. Some of those functions were from libstdc++-debuginfo-11.0.0-0.19.fc34 and qt5-qtbase-5.15.2-13.fc34. Application: RKWard (rkward), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fbe163768a4 in __GI_abort () at abort.c:79 #6 0x7fbe16709a86 in __gnu_cxx::__verbose_terminate_handler() () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x7fbe1671521c in __cxxabiv1::__terminate(void (*)()) (handler=) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x7fbe16715287 in std::terminate() () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x7fbe16715529 in __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) (obj=, tinfo=0x7fbe16877e78 , dest=0x7fbe167138b0 ) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:95 #10 0x7fbe169387b9 in qBadAlloc() () at global/qglobal.cpp:3338 #11 0x7fbe1693ae38 in QListData::detach_grow(int*, int) (this=, this@entry=0x55c08c1105b8, idx=, idx@entry=0x7ffe99d6557c, num=, num@entry=1) at tools/qlist.cpp:97 #12 0x55c08a3303f0 in QList::detach_helper_grow(int, int) (this=0x55c08c1105b8, i=, c=1) at /usr/include/qt5/QtCore/qlist.h:803 #13 0x55c08a36a071 in QList::append(RCommand* const&) (this=, t=@0x7ffe99d655c0: 0x55c08c369910) at /usr/include/qt5/QtCore/qlist.h:623 #14 0x55c08a437fbd in RCommandReceiver::addCommand(RCommand*) (command=, this=0x55c08c1105b0) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/rbackend/rcommandreceiver.cpp:48 #15 RCommand::addReceiver(RCommandReceiver*) (receiver=0x55c08c1105b0, this=0x55c08c369910) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/rbackend/rcommand.cpp:94 #16 RCommand::addReceiver(RCommandReceiver*) (this=0x55c08c369910, receiver=0x55c08c1105b0) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/rbackend/rcommand.cpp:86 #17 0x55c08a4381e1 in RCommand::RCommand(QString const&, int, QString const&, RCommandReceiver*, int) (this=0x55c08c369910, command=..., type=, rk_equiv=..., receiver=0x55c08c1105b0, flags=, this=, command=, type=, rk_equiv=, receiver=, flags=) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/rbackend/rcommand.cpp:61 #18 0x55c08a385c44 in LoadUnloadWidget::doLoadUnload() (this=0x55c08c110580) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/dialogs/rkloadlibsdialog.cpp:620 #19 0x55c08a3903c7 in LoadUnloadWidget::ok() (this=0x55c08c110580) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/dialogs/rkloadlibsdialog.cpp:577 #20 LoadUnloadWidget::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x55c08c110580, _id=, _a=, _c=) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/x86_64-redhat-linux-gnu/rkward/dialogs/dialogs_autogen/EWIEGA46WW/moc_rkloadlibsdialog.cpp:347 #21 0x7fbe16b374fd in doActivate(QObject*, int, void**) (sender=0x55c08c0df890, signal_index=8, argv=0x7ffe99d657a0) at kernel/qobject.cpp:3898 #22 0x7fbe16b319e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55c08c0df890, m=m@entry=0x7fbe17bef8e0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #23 0x7fbe178d3447 in QDialog::accepted() (this=this@entry=0x55c08c0df890) at .moc/moc_qdialog.cpp:236 #24 0x7fbe178d3898 in QDialogPrivate::finalize(int, int) (this=, resultCode=1, dialogCode=) at dialogs/qdialog.cpp:176 #25 0x55c08a380f55 in RKLoadLibsDialog::~RKLoadLibsDialog() (this=0x55c08c0df890, this=) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/dialogs/rkloadlibsdialog.cpp:86 #26 0x55c08a380fdd in RKLoadLibsDialog::~RKLoadLibsDialog() (this=0x55c08c0df890, this=) at /usr/src/debug/rkward-0.7.2-2.fc34.x86_64/rkward/dialogs/rkloadlibsdialog.cpp:88 #27 0x7fbe16b2deda in QObjectPrivate::deleteChildren()
[plasmashell] [Bug 432493] New: plasmashell on Wayland aborted when changing Global Theme to Fedora in System settings
https://bugs.kde.org/show_bug.cgi?id=432493 Bug ID: 432493 Summary: plasmashell on Wayland aborted when changing Global Theme to Fedora in System settings Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: 1.0 SUMMARY I was using Plasma 5.20.90 on Wayland in Fedora Rawhide/34. I started System Settings and selected Appearance > Global Theme. I switched the Global theme to Breeze and pressed Apply. I switched the Global theme to Fedora and pressed Apply. plasmashell aborted with the error message "The Wayland connection experienced a fatal error: Invalid argument" The screen went black. plasmashell didn't restart automatically. plasmashell aborted 4 of 5 times I changed the Global theme to Fedora in Plasma 5.20.90 on Wayland. The journal showed the following at the time of the last crash which had the same types of errors as the others. Feb 03 22:31:43 systemsettings5[5]: QDBusConnection: error: could not send signal to service "" path "//home/matt/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/matt/.kde/share/config/kdeglobals Feb 03 22:31:43 plasmashell[9277]: qt.svg: :406:376: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :407:130: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :408:130: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :408:393: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :409:130: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :410:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :411:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :412:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :413:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :413:379: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:43 plasmashell[9277]: qt.svg: :413:631: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 systemsettings5[5]: QDBusConnection: error: could not send signal to service "" path "//home/matt/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/matt/.kde/share/config/kdeglobals Feb 03 22:31:49 plasmashell[9277]: qt.svg: :406:376: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :407:130: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :408:130: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :408:393: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :409:130: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :410:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :411:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :412:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :413:129: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :413:379: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:49 plasmashell[9277]: qt.svg: :413:631: Could not add child element to parent element because the types are incorrect. Feb 03 22:31:58 systemsettings5[5]: QDBusConnection: error: could not send signal to service "" path "//home/matt/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/matt/.kde/share/config/kdeglobals Feb 03 22:31:58 plasmashell[9277]: wl_display@1: error 0: invalid object 390 Feb 03 22:31:58
[frameworks-kwayland] [Bug 408553] Segmentation faults and invalid reads/writes in powerdevil when logging out of Plasma 5.15.5 on Wayland in Fedora 30
https://bugs.kde.org/show_bug.cgi?id=408553 Matt Fagnani changed: What|Removed |Added Resolution|UPSTREAM|FIXED Latest Commit||https://phabricator.kde.org ||/D27538 Version Fixed In||5.68 --- Comment #7 from Matt Fagnani --- (In reply to Nate Graham from comment #6) > #6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, > msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland > compositor die?") at global/qlogging.cpp:893 > > This means that the compositor crashed. Due to a Qt issue, when this > happens, the app using it will crash too. KDE developers submitted a fix, > but sadly it was not merged. See > https://codereview.qt-project.org/c/qt/qtwayland/+/308984. > > Until we get better handling of this in Qt, the best we can do is debug why > the compositor crashed in the first place. So can you please get a backtrace > of the crash in kwin_wayland and then file a new bug report with it on kwin > | wayland-generic? Thanks! > > You may be able to use the `coredumpctl` utility to retrieve the backtrace. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Nate, I think that kwin_wayland stopped normally during logout before powerdevil segmentation faulted and then powerdevil tried to restart and drkonqi aborted, which led to the errors like The Wayland connection broke. Did the Wayland compositor die? I didn't mention any kwin_wayland crashes in my report. The first powerdevil segmentation faults were due to the use-after-free errors in wl_proxy_unref (wayland-client.c:229) in libwayland-client. I think those errors were fixed by Daniel Vrátil in kwayland 5.68 whose message mentioned invalid read/write use-after-free errors in wl_proxy_unref (wayland-client.c:230) also involving KWayland::Client::Registry::Private::globalSync in the commit https://phabricator.kde.org/R127:4ceb35672dfa3378776a926c452b9f83ffe2bc41 Registry: don't destroy the callback on globalsync Summary: Instead just unref it, because the wl_display_dispatch_queue_pending will try to destroy the callback afterwards as well, leading to invalid read/write. Fixes Valgrind warnings when running KScreen tests: ==460922== Invalid read of size 4 ==460922==at 0x5CE5B34: wl_proxy_unref (wayland-client.c:230) ==460922==by 0x5CE5C33: destroy_queued_closure (wayland-client.c:292) ==460922==by 0x5CE74AB: dispatch_queue (wayland-client.c:1591) ==460922==by 0x5CE74AB: wl_display_dispatch_queue_pending (wayland-client.c:1833) ==460922==by 0x4E0240D: KWayland::Client::EventQueue::dispatch() (src/frameworks/kwayland/src/client/event_queue.cpp:96) g==460922== Address 0x17233aac is 44 bytes inside a block of size 80 free'd ==460922==at 0x483B9F5: free (vg_replace_malloc.c:540) ==460922==by 0x4E15B60: destroy (src/frameworks/kwayland/src/client/wayland_pointer_p.h:63) ==460922==by 0x4E15B60: KWayland::Client::Registry::Private::globalSync(void*, wl_callback*, unsigned int) (src/frameworks/kwayland/src/client/registry.cpp:548) ... ==460922==by 0x5CE74AB: dispatch_queue (wayland-client.c:1591) ==460922==by 0x5CE74AB: wl_display_dispatch_queue_pending (wayland-client.c:1833) ==460922==by 0x4E0240D: KWayland::Client::EventQueue::dispatch() (src/frameworks/kwayland/src/client/event_queue.cpp:96) I haven't seen these powerdevil crashes or those involving similar invalid read/write errors in plasmashell, konsole, etc I mentioned in comment 5 since KF 5.68.0. The qtwayland fix you mentioned could resolve the aborts of KDE programs after kwin_wayland stopped when logging out. Alternatively, kwin_wayland could be made to wait until the other KDE programs have stopped before it is stopped maybe using the systemd integration. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086
Matt Fagnani changed:
What|Removed |Added
Version|5.20.3 |5.20.4
--- Comment #2 from Matt Fagnani ---
I've seen kwin_wayland crashes with this trace seven times with Plasma 5.20.3
and six times with 5.20.4. Each crash happened when using Firefox Nightly
84.0a1-86.0a1 on Wayland. All but one crash occurred while moving the cursor
over the bookmark folders. One crash happened on the bugs.kde.org Advanced
search page when I clicked on a popup box in the Custom Search area
https://bugs.kde.org/query.cgi?format=advanced
I've had WebRender compositing enabled in Firefox by going into about:config
and setting gfx.webrender.all=true, gfx.webrender.enabled=true. Having
WebRender enabled might be needed for this crash to happen. Robert Mader
commented "It just occurred to me that with Webrender enabled mesa will commit
our surface in dri2_wl_swap_buffers_with_damage which we call in
GLContextEGL::SwapBuffers(). So even if when using
moz_container_wayland_surface_lock there's still a chance that the surface will
get commited behind our back, potentially freeing it IIUC.
So maybe we have to extent our surface locking to GLContextEGL::SwapBuffers()
as well somehow.
"
https://bugzilla.mozilla.org/show_bug.cgi?id=1655282#c10
Robert wrote a patch to lock the surface in GLContextEGL::SwapBuffers
https://bugzilla.mozilla.org/show_bug.cgi?id=1680961
Checking that the pointer this or d isn't null in
KWaylandServer::SurfaceInterface::subSurface before surface_interface.cpp:792
might avoid the crash at least until the problem is fixed in Firefox.
QPointer< SubSurfaceInterface > SurfaceInterface::subSurface() const
{
return d->subSurface;
}
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 430325] kstars segmentation faulted in DetailDialog::createGeneralTab
https://bugs.kde.org/show_bug.cgi?id=430325 --- Comment #2 from Matt Fagnani --- Created attachment 134068 --> https://bugs.kde.org/attachment.cgi?id=134068=edit gdb output when run on kstars followed by the crash with the full trace -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 430325] kstars segmentation faulted in DetailDialog::createGeneralTab
https://bugs.kde.org/show_bug.cgi?id=430325 Matt Fagnani changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1907270 --- Comment #1 from Matt Fagnani --- Clicking on Pointing > Find Object, entering sagittarius in Filter by name, and selecting the Details button was all that was required for the crash to happen in further tries. When I ran kstars from konsole and under gdb, the following error was shown when the crash occurred. QWaylandShmBuffer: mmap failed (Invalid argument) Running kstars under gdb indicated that the pointer this in frame 0 pointed to an inaccessible address. (gdb) p this $1 = (DetailDialog * const) 0x58b4ecc0 (gdb) x this 0x58b4ecc0: 0x561463b8 (gdb) x 0x561463b8 0x561463b8: Cannot access memory at address 0x561463b8 I'm attaching the gdb output with the full trace. The pointer dso = 0x0 in frame 0 in DetailDialog::createGeneralTab in the full trace which might indicate a null pointer dereference happened at detaildialog.cpp:312 if (!dso->longname().isEmpty() && dso->longname() != dso->name()) Crashes with this trace happened with both of kstars-3.4.3-4.fc33 with LTO disabled due to the problem at https://bugzilla.redhat.com/show_bug.cgi?id=1881915 and kstars-3.4.3-5.fc33 with LTO enabled and -fPIC from koji. This problem isn't likely to be related to the LTO problem. The crash happened when I ran kstars on X in Plasma on Wayland with QT_QPA_PLATFORM=xcb kstars & so the problem probably isn't specific to Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 430325] New: kstars segmentation faulted in DetailDialog::createGeneralTab
https://bugs.kde.org/show_bug.cgi?id=430325 Bug ID: 430325 Summary: kstars segmentation faulted in DetailDialog::createGeneralTab Product: kstars Version: 3.4.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Application: kstars (3.4.3) Qt Version: 5.15.2 Frameworks Version: 5.75.0 Operating System: Linux 5.9.14-200.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I was using Plasma 5.20.4 on Wayland in Fedora 33. I started kstars 3.4.3 and clicked on Pointing > Find Object. I entered sagittarius in Filter by name then clicked OK. I moved the map around a bit. I clicked on Pointing > Find Object. I selected the Details button. kstars segmentation faulted in DetailDialog::createGeneralTab at /usr/src/debug/kstars-3.4.3-5.fc33.x86_64/kstars/dialogs/detaildialog.cpp:312 This crash happened 2/2 times. The crash can be reproduced every time. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault [KCrash Handler] #4 DetailDialog::createGeneralTab (this=0x563726e7c5e0) at /usr/src/debug/kstars-3.4.3-5.fc33.x86_64/kstars/dialogs/detaildialog.cpp:312 #5 0x5637216cc1fd in DetailDialog::DetailDialog (this=, o=, ut=..., geo=, parent=, this=, o=, ut=..., geo=, parent=) at /usr/src/debug/kstars-3.4.3-5.fc33.x86_64/kstars/dialogs/detaildialog.cpp:72 #6 0x5637218384f3 in FindDialog::slotDetails (this=) at /usr/src/debug/kstars-3.4.3-5.fc33.x86_64/kstars/dialogs/finddialog.cpp:504 #7 FindDialog::qt_static_metacall (_o=, _id=, _a=, _c=) at /usr/src/debug/kstars-3.4.3-5.fc33.x86_64/x86_64-redhat-linux-gnu/kstars/KStarsLib_autogen/2NRMJ5X7RK/moc_finddialog.cpp:170 #8 0x7f0a686a03c0 in doActivate (sender=0x563726c5dae0, signal_index=9, argv=0x7ffd076650d0) at kernel/qobject.cpp:3898 #9 0x7f0a6928c316 in QAbstractButton::clicked (this=this@entry=0x563726c5dae0, _t1=) at .moc/moc_qabstractbutton.cpp:308 #10 0x7f0a6928ccde in QAbstractButtonPrivate::emitClicked (this=this@entry=0x563725868a00) at widgets/qabstractbutton.cpp:415 #11 0x7f0a6928e673 in QAbstractButtonPrivate::click (this=this@entry=0x563725868a00) at widgets/qabstractbutton.cpp:408 #12 0x7f0a6928e855 in QAbstractButton::mouseReleaseEvent (this=0x563726c5dae0, e=0x7ffd07665690) at widgets/qabstractbutton.cpp:1044 #13 0x7f0a691ddb1e in QWidget::event (this=0x563726c5dae0, event=0x7ffd07665690) at kernel/qwidget.cpp:9019 #14 0x7f0a6919cec3 in QApplicationPrivate::notify_helper (this=, receiver=0x563726c5dae0, e=0x7ffd07665690) at kernel/qapplication.cpp:3632 #15 0x7f0a691a3eeb in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3076 #16 0x7f0a68670bd8 in QCoreApplication::notifyInternal2 (receiver=0x563726c5dae0, event=0x7ffd07665690) at kernel/qcoreapplication.cpp:1063 #17 0x7f0a691a2efa in QApplicationPrivate::sendMouseEvent (receiver=0x563726c5dae0, event=0x7ffd07665690, alienWidget=0x563726c5dae0, nativeWidget=0x56372659e2c0, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614 #18 0x7f0a691f6375 in QWidgetWindow::handleMouseEvent (this=0x563725864ed0, event=0x7ffd07665940) at kernel/qwidgetwindow.cpp:683 #19 0x7f0a691f96be in QWidgetWindow::event (this=0x563725864ed0, event=0x7ffd07665940) at kernel/qwidgetwindow.cpp:300 #20 0x7f0a6919cec3 in QApplicationPrivate::notify_helper (this=, receiver=0x563725864ed0, e=0x7ffd07665940) at kernel/qapplication.cpp:3632 #21 0x7f0a68670bd8 in QCoreApplication::notifyInternal2 (receiver=0x563725864ed0, event=0x7ffd07665940) at kernel/qcoreapplication.cpp:1063 #22 0x7f0a68b3f143 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at kernel/qguiapplication.cpp:2275 #23 0x7f0a68b208cc in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1169 #24 0x7f0a55f7de24 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #25 0x7f0a66b7a7ef in g_main_dispatch (context=0x5637232e9ed0) at ../glib/gmain.c:3325 #26 g_main_context_dispatch (context=0x5637232e9ed0) at ../glib/gmain.c:4043 #27 0x7f0a66bcc5d8 in g_main_context_iterate.constprop.0 (context=context@entry=0x5637232e9ed0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4119 #28 0x7f0a66b77bc3 in g_main_context_iteration (context=0x5637232e9ed0, may_block=1) at ../glib/gmain.c:4184 #29 0x7f0a686bd6f3 in QEventDispatcherGlib::processEvents (this=0x5637232cda50, flags=...) at
[kwin] [Bug 429395] New: kwin_wayland segmentation faults in spa_hook_remove in pipewire 0.3.16-1.fc33
https://bugs.kde.org/show_bug.cgi?id=429395 Bug ID: 429395 Summary: kwin_wayland segmentation faults in spa_hook_remove in pipewire 0.3.16-1.fc33 Product: kwin Version: 5.20.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I was using Plasma 5.20.3 on Wayland in a F33 KDE Plasma spin installation with kwin-wayland, plasma-workspace-wayland and their dependencies installed. I ran sudo dnf upgrade --refresh with updates-testing enabled. The update included pipewire-0.3.16-1.fc33, kernel-5.9.9-200.fc33 and other rpms. I rebooted. I logged in to Plasma 5.20.3 on Wayland. I was using Firefox Nightly 85.0a1 on Wayland for a few minutes. kwin_wayland segmentation faulted in spa_hook_remove at ../spa/include/spa/utils/hook.h:112 in pipewire 0.3.16-1.fc33 The crash appeared to happen when the pipewire stream was being destroyed starting with KWin::PipeWireStream::~PipeWireStream() in frame 3 --Type for more, q to quit, c to continue without paging-- Core was generated by `/usr/bin/kwin_wayland --xwayland --exit-with-session=/usr/libexec/startplasma-w'. Program terminated with signal SIGSEGV, Segmentation fault. #0 spa_hook_remove (hook=0x56227818) at ../spa/include/spa/utils/hook.h:112 112 hook->removed(hook); [Current thread is 1 (Thread 0x7f505f8c8e00 (LWP 3661))] (gdb) bt #0 spa_hook_remove (hook=0x56227818) at ../spa/include/spa/utils/hook.h:112 #1 spa_hook_list_clean (list=) at ../spa/include/spa/utils/hook.h:119 #2 pw_stream_destroy (stream=0x5620002159d0) at ../src/pipewire/stream.c:1315 #3 0x561ffe7ee8f1 in KWin::PipeWireStream::~PipeWireStream() (this=0x562277f0, this=) at /usr/src/debug/kwin-5.20.3-1.fc33.x86_64/screencast/pipewirestream.cpp:188 #4 0x561ffe7eea7a in KWin::WindowStream::~WindowStream() (this=0x562277f0, this=) at /usr/src/debug/kwin-5.20.3-1.fc33.x86_64/screencast/screencastmanager.cpp:40 #5 KWin::WindowStream::~WindowStream() (this=0x562277f0, this=) at /usr/src/debug/kwin-5.20.3-1.fc33.x86_64/screencast/screencastmanager.cpp:40 #6 0x7f505fb56256 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcca163730, r=0x562277f0, this=0x56287560) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x5629f000, signal_index=3, argv=0x7ffcca163730) at kernel/qobject.cpp:3886 #8 0x7f5060cab605 in KWaylandServer::ScreencastStreamV1InterfacePrivate::zkde_screencast_stream_unstable_v1_destroy_resource(QtWaylandServer::zkde_screencast_stream_unstable_v1::Resource*) (this=0x562000130ae0, resource=) at /usr/src/debug/kwayland-server-5.20.3-1.fc33.x86_64/src/server/screencast_v1_interface.cpp:31 #9 0x7f5060cf0584 in QtWaylandServer::zkde_screencast_stream_unstable_v1::destroy_func(wl_resource*) (client_resource=) at /usr/src/debug/kwayland-server-5.20.3-1.fc33.x86_64/x86_64-redhat-linux-gnu/src/server/qwayland-server-zkde-screencast-unstable-v1.cpp:326 #10 0x7f505df0197f in destroy_resource --Type for more, q to quit, c to continue without paging--c (element=0x562cc740, data=data@entry=0x7ffcca163824, flags=0) at src/wayland-server.c:724 #11 0x7f505df02013 in for_each_helper (entries=, entries=0x561542e0, data=0x7ffcca163824, func=0x7f505df018d0 ) at src/wayland-util.c:372 #12 wl_map_for_each (data=0x7ffcca163824, func=0x7f505df018d0 , map=0x561542e0) at src/wayland-util.c:385 #13 wl_client_destroy (client=client@entry=0x561542b0) at src/wayland-server.c:883 #14 0x7f505df0244b in destroy_client_with_error (reason=, client=) at src/wayland-server.c:319 #15 wl_client_connection_data (fd=, mask=, data=) at src/wayland-server.c:342 #16 0x7f505df01ac2 in wl_event_loop_dispatch (loop=0x561fff0e06e0, timeout=) at src/event-loop.c:1027 #17 0x7f5060c81f13 in KWaylandServer::Display::Private::dispatch() (this=) at /usr/src/debug/kwayland-server-5.20.3-1.fc33.x86_64/src/server/display.cpp:135 #18 0x7f505fb56256 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcca163d70, r=0x561fff102640, this=0x561fffac3280) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x561fffba6830, signal_index=3, argv=0x7ffcca163d70) at kernel/qobject.cpp:3886 #20 0x7f505fb59476 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x561fffba6830, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #21 0x7f505fb59be9 in QSocketNotifier::event(QEvent*) (this=0x561fffba6830, e=0x7ffcca163e90) at kernel/qsocketnotifier.cpp:302
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 --- Comment #1 from Matt Fagnani --- I've seen kwin_wayland crashes with this trace four times now. Each crash happened when using Firefox 84.0a1-85.0a1 on Wayland and moving the cursor over the bookmark folders. The folder shown at the time of the crash didn't contain another folder during two of the crashes, so the bookmark folder having another folder in it isn't a requirement for reproducing the crash. Another of the crashes had the contents of a bookmark folder within a folder frozen in a state of disappearing when Plasma crashed. Firefox on Wayland crashed many times when using the bookmarks folders during the last four months or so in Plasma 5.19.5 and earlier. Segmentation faults happened involving a null pointer dereference in wl_proxy_marshal_constructor at wayland-client.c:830 in libwayland-client-1.18.0-2.fc33.x86_64. The Wayland proxies of the surfaces of the bookmark folders might've been occasionally freed before being used. I reported the Firefox crashes at https://bugzilla.mozilla.org/show_bug.cgi?id=1655282 If the Wayland subsurface of the bookmark folders were sometimes freed before being used, this=0x0 in KWaylandServer::SurfaceInterface::subSurface in frame 1 might be how that would show up. I reported these crashes for Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=1897969 kwin_wayland core dump files were truncated for other crashes because their uncompressed sizes were above the 2 GB default limit of systemd-coredump https://bugs.kde.org/show_bug.cgi?id=416974 I changed /etc/systemd/coredump.conf many months ago to have the following values so the kwin_wayland core dumps wouldn't be truncated: ProcessSizeMax=3G ExternalSizeMax=3G -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429086] New: kwin_wayland segmentation faulted in QScopedPointer >::operator->() whe
https://bugs.kde.org/show_bug.cgi?id=429086 Bug ID: 429086 Summary: kwin_wayland segmentation faulted in QScopedPointer >::operator->() when using Firefox Product: kwin Version: 5.20.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Created attachment 133325 --> https://bugs.kde.org/attachment.cgi?id=133325=edit Full trace of all threads of kwin_wayland segmentation fault SUMMARY I was using Plasma 5.20.3 on Wayland in Fedora 33. I started Firefox Nightly 74.0a1 (2020-11-13) on Wayland. I clicked on Bookmarks in the menu bar and moved the cursor down over the bookmarks folders. The contents of one of the bookmarks folders didn't appear, but the contents of a folder within that folder appeared. Plasma froze for a few seconds. kwin_wayland segmentation faulted in QScopedPointer >::operator->() at /usr/include/qt5/QtCore/qscopedpointer.h:116 in qt5-qtbase-devel-0:5.15.1-7.fc33.x86_64. The pointer this=0x10 in frame 0 was likely invalid, which might be due to this=0x0 in KWaylandServer::SurfaceInterface::subSurface in frame 1. Core was generated by `/usr/bin/kwin_wayland --xwayland --exit-with-session=/usr/libexec/startplasma-w'. Program terminated with signal SIGSEGV, Segmentation fault. #0 QScopedPointer >::operator-> (this=0x10) at /usr/include/qt5/QtCore/qscopedpointer.h:116 116 T *operator->() const noexcept [Current thread is 1 (Thread 0x7fbde6c82e00 (LWP 1152))] (gdb) bt #0 QScopedPointer >::operator->() const (this=0x10) at /usr/include/qt5/QtCore/qscopedpointer.h:116 #1 KWaylandServer::SurfaceInterface::subSurface() const (this=0x0) at /usr/src/debug/kwayland-server-5.20.3-1.fc33.x86_64/src/server/surface_interface.cpp:792 #2 0x7fbde83ccfac in KWaylandServer::SubSurfaceInterface::Private::setMode(KWaylandServer::SubSurfaceInterface::Mode) (this=0x56071aaffb10, m=KWaylandServer::SubSurfaceInterface::Mode::Desynchronized) at /usr/src/debug/kwayland-server-5.20.3-1.fc33.x86_64/src/server/subcompositor_interface.cpp:275 #3 0x7fbde42dcb10 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #4 0x7fbde42dc0a3 in ffi_call (cif=cif@entry=0x7ffeb1593f70, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffeb1594040) at ../src/x86/ffi64.c:525 #5 0x7fbde5606fd5 in wl_closure_invoke (closure=closure@entry=0x56071ac12b70, target=, target@entry=0x56071ac70020, opcode=opcode@entry=5, data=, data@entry=0x56071abfdc60, flags=) at src/connection.c:1018 #6 0x7fbde560aecc in wl_client_connection_data (fd=, mask=, data=) at src/wayland-server.c:432 #7 0x7fbde5609ac2 in wl_event_loop_dispatch (loop=0x5607199cbb90, timeout=) at src/event-loop.c:1027 #8 0x7fbde8389f13 in KWaylandServer::Display::Private::dispatch() (this=) at /usr/src/debug/kwayland-server-5.20.3-1.fc33.x86_64/src/server/display.cpp:135 #9 0x7fbde725e256 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffeb1594650, r=0x5607199d71a0, this=0x56071a390d50) --Type for more, q to quit, c to continue without paging--c at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x56071a395430, signal_index=3, argv=0x7ffeb1594650) at kernel/qobject.cpp:3886 #11 0x7fbde7261476 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x56071a395430, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #12 0x7fbde7261be9 in QSocketNotifier::event(QEvent*) (this=0x56071a395430, e=0x7ffeb1594770) at kernel/qsocketnotifier.cpp:302 #13 0x7fbde7c2615f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x56071a395430, e=0x7ffeb1594770) at kernel/qapplication.cpp:3630 #14 0x7fbde722fbe8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x56071a395430, event=0x7ffeb1594770) at kernel/qcoreapplication.cpp:1063 #15 0x7fbde7277ece in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x56071999ab40) at kernel/qeventdispatcher_unix.cpp:304 #16 0x7fbde7278254 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:511 #17 0x7fbdd413c3ad in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib64/qt5/plugins/platforms/KWinQpaPlugin.so #18 0x7fbde722e64b in QEventLoop::exec(QFlags) (this=0x7ffeb15948e0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x7fbde7236010 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x56071912356e in main(int, char**) (argc=, argv=0x7ffeb1594b00) at
[systemsettings] [Bug 429027] New: System Settings segmentation faulted in std::__atomic_base::load when selecting Regional Settings
https://bugs.kde.org/show_bug.cgi?id=429027 Bug ID: 429027 Summary: System Settings segmentation faulted in std::__atomic_base::l oad when selecting Regional Settings Product: systemsettings Version: 5.20.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Application: systemsettings5 (5.20.2) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.8-200.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I was using Plasma 5.20.3 on Wayland in Fedora 33 with KF 5.75.0, Qt 5.15.1, Mesa 20.2.2 in Fedora 33. I started System Settings. I selected Startup and Shutdown > Login Screen (SDDM). I set the sddm background to Breeze because the default Breeze Fedora showed a white sddm background after logging out of Plasma. I selected various items on the menu on the left. System Settings segmentation faulted in std::__atomic_base::load when I selected Regional Settings. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f434d202264 in std::__atomic_base::load(std::memory_order) const (__m=, this=) at /usr/include/c++/10/bits/atomic_base.h:747 #5 std::atomic::load(std::memory_order) const (__m=, this=) at /usr/include/c++/10/atomic:523 #6 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #7 QBasicAtomicPointer::loadRelaxed() const (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #8 QObjectPrivate::ensureConnectionData() (this=) at kernel/qobject_p.h:371 #9 QObjectPrivate::addConnection(int, QObjectPrivate::Connection*) (this=0x0, signal=signal@entry=3, c=c@entry=0x55743c065190) at kernel/qobject.cpp:324 #10 0x7f434d204b3e in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) (sender=0x55743d481e40, signal_index=3, receiver=0x55743c17c8f0, slot=, slotObj=, type=, types=, senderMetaObject=) at kernel/qobject.h:132 #11 0x7f434d205005 in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) (sender=0x55743d481e40, signal=, receiver=0x55743c17c8f0, slot=0x0, slotObj=0x55743c796c90, type=Qt::AutoConnection, types=0x0, senderMetaObject=) at kernel/qobject.cpp:5001 #12 0x7f432438dd64 in QObject::connect > (type=Qt::AutoConnection, slot=..., context=0x55743c17c8f0, signal=(void (QmlComponentsPool::*)(class QmlComponentsPool * const)) 0x7f432437b170 , sender=0x55743d481e40) at /usr/include/qt5/QtCore/qobject.h:347 #13 ColumnView::classBegin() (this=0x55743c17c8f0) at /usr/src/debug/kf5-kirigami2-5.75.0-1.fc33.x86_64/src/columnview.cpp:1406 #14 0x7f434c2fbe6d in QQmlObjectCreator::createInstance(int, QObject*, bool) (this=0x7ffe1365fc30, index=38, parent=, isContextObject=) at qml/qqmlobjectcreator.cpp:1291 #15 0x7f434c2fe1fe in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) (this=this@entry=0x7ffe1365fc30, bindingProperty=bindingProperty@entry=0x7f42f40c93a8, binding=binding@entry=0x7f42b3b4abc8) at /usr/include/qt5/QtCore/qendian.h:288 #16 0x7f434c2fe7cf in QQmlObjectCreator::setupBindings(bool) (this=0x7ffe1365fc30, applyDeferredBindings=false) at qml/qqmlobjectcreator.cpp:798 #17 0x7f434c2fb57e in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) (this=this@entry=0x7ffe1365fc30, index=-1, index@entry=0, instance=0x0, bindingTarget=0x0, valueTypeProperty=valueTypeProperty@entry=0x0) at qml/qqmlobjectcreator.cpp:1555 #18 0x7f434c2fc0db in QQmlObjectCreator::createInstance(int, QObject*, bool) (this=0x7ffe1365fc30, index=0, parent=, isContextObject=) at qml/qqmlobjectcreator.cpp:1348 #19 0x7f434c2f73a0 in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) (this=0x7ffe1365fc30, subComponentIndex=, parent=0x0, interrupt=0x0, flags=) at qml/qqmlobjectcreator.cpp:204 #20 0x7f434c2fc5e6 in QQmlObjectCreator::createInstance(int, QObject*, bool) (this=0x7ffe13660460, index=2, parent=0x55743d559b40, isContextObject=) at qml/qqmlobjectcreator.cpp:1231 #21 0x7f434c2fe1fe in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) (this=this@entry=0x7ffe13660460, bindingProperty=bindingProperty@entry=0x7f42b40e8958, binding=binding@entry=0x7f42b389eb90) at /usr/include/qt5/QtCore/qendian.h:288 #22
[plasmashell] [Bug 409021] Segmentation faults of plasmashell in wl_proxy_set_queue in libwayland-client in Plasma on Wayland
https://bugs.kde.org/show_bug.cgi?id=409021 --- Comment #10 from Matt Fagnani --- Created attachment 133126 --> https://bugs.kde.org/attachment.cgi?id=133126=edit New crash information added by DrKonqi plasmashell (5.19.5) using Qt 5.15.1 - What I was doing when the application crashed: I was using Plasma 5.19.5 on Wayland in Fedora 33 with KF 5.75.0 and Qt 5.15.1. I'd set the desktop to use the Application Menu by right-clicking on the button at the bottom left of the screen, selecting Show Alternatives > Application Menu > Switch. I clicked to open the Application Menu several times. The screen went black and plasmashell restarted automatically. plasmashell segmentation faulted in wl_proxy_set_queue at src/wayland-client.c:2173 in libwayland-client-1.18.0-2.fc33.x86_64 due to a null pointer dereference where proxy=0x0. -- Backtrace (Reduced): #4 0x7f8d7de37ca5 in wl_proxy_set_queue (proxy=0x0, queue=0x562e195913a0) at src/wayland-client.c:2173 #5 0x7f8d6cc1df5d in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) (timeout=100, this=0x562e19591920) at qwaylandwindow.cpp:632 #6 QtWaylandClient::QWaylandWindow::waitForFrameSync(int) (this=0x562e19591920, timeout=100) at qwaylandwindow.cpp:625 #7 0x7f8d69f030aa in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) (this=0x562e1a3701a0, surface=0x562e19591930) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:492 #8 0x7f8d7ffca0fc in QSGRenderThread::syncAndRender(QImage*) (this=0x562e1a3ecfb0, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:870 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414116] Plasmashell aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=414116 --- Comment #4 from Matt Fagnani --- Created attachment 132580 --> https://bugs.kde.org/attachment.cgi?id=132580=edit New crash information added by DrKonqi plasmashell (5.19.5) using Qt 5.15.1 - What I was doing when the application crashed: I logged into Plasma 5.19.5 on Wayland in Fedora 33. I clicked on the Network Manager applet then on the connection. plasmashell stopped responding for about 10 seconds. plasmashell aborted with the error "The Wayland connection broke. Did the Wayland compositor die?" The journal showed the following errors at the time of the crash. Oct 20 05:44:23 plasmashell[1280]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem4/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:327: TypeError: Cannot read property 'width' of null Oct 20 05:44:23 plasmashell[1280]: The Wayland connection broke. Did the Wayland compositor die? The screen turned black. plasmashell reappeared. This crash has happened before, but it's infrequent. -- Backtrace (Reduced): #4 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7ff9e5ccb8a4 in __GI_abort () at abort.c:79 #6 0x7ff9e60f0b07 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal(char const*, ...) const (this=, msg=) at global/qlogging.cpp:893 #8 0x7ff9d4839d89 in QtWaylandClient::QWaylandDisplay::checkError() const (this=) at /usr/include/qt5/QtCore/qlogging.h:90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409021] Segmentation faults of plasmashell in wl_proxy_set_queue in libwayland-client in Plasma on Wayland
https://bugs.kde.org/show_bug.cgi?id=409021 --- Comment #9 from Matt Fagnani --- Created attachment 132017 --> https://bugs.kde.org/attachment.cgi?id=132017=edit New crash information added by DrKonqi plasmashell (5.19.5) using Qt 5.15.1 - What I was doing when the application crashed: I logged into Plasma 5.19.5 on Wayland in Fedora 33 with KF 5.73.0, Qt 5.15.1, Mesa 20.2.0. I clicked on the updates applet button in the System Tray. plasmashell crashed before the updates applet would have appeared. The screen went black. plasmashell restarted automatically. plasmashell had a segmentation fault in wl_proxy_set_queue at wayland-client.c:2173 in libwayland-client-1.18.0-2.fc33. The crash was likely due to a null pointer dereference since proxy=0x0 as in previous crashes I've reported here. -- Backtrace (Reduced): #4 0x7f1b52da3ca5 in wl_proxy_set_queue (proxy=0x0, queue=0x561f267c6780) at src/wayland-client.c:2173 #5 0x7f1b41a19f5d in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) (timeout=100, this=0x561f266066c0) at qwaylandwindow.cpp:632 #6 QtWaylandClient::QWaylandWindow::waitForFrameSync(int) (this=0x561f266066c0, timeout=100) at qwaylandwindow.cpp:625 #7 0x7f1b4000f0aa in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) (this=0x561f268c9700, surface=0x561f266066d0) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:492 #8 0x7f1b54df60fc in QSGRenderThread::syncAndRender(QImage*) (this=0x561f262a0ce0, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:870 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 426899] kstars segmentation fault in doActivate when starting
https://bugs.kde.org/show_bug.cgi?id=426899 Matt Fagnani changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1881915 --- Comment #1 from Matt Fagnani --- I ran valgrind --log-file=valgrind-kstars-1.txt kstars An invalid read at the address 0x8 and segmentation fault occurred in operator-> at qscopedpointer.h:118 in qt5-qtbase-5.15.1-1.fc33.x86_64. ==3954== Memcheck, a memory error detector ==3954== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==3954== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==3954== Command: kstars ==3954== Parent PID: 2717 ==3954== ==3954== Invalid read of size 8 ==3954==at 0x6C1CE5B: operator-> (qscopedpointer.h:118) ==3954==by 0x6C1CE5B: qGetPtrHelper > (qglobal.h:1135) ==3954==by 0x6C1CE5B: d_func (qobject.h:132) ==3954==by 0x6C1CE5B: get (qobject_p.h:339) ==3954==by 0x6C1CE5B: void doActivate(QObject*, int, void**) (qobject.cpp:3768) ==3954==by 0x64B5EE1: QGuiApplication::screenAdded(QScreen*) (moc_qguiapplication.cpp:389) ==3954==by 0x195CF697: QtWaylandClient::QWaylandDisplay::handleScreenInitialized(QtWaylandClient::QWaylandScreen*) (qwaylanddisplay.cpp:281) ==3954==by 0x195DC622: QtWaylandClient::QWaylandScreen::maybeInitialize() (qwaylandscreen.cpp:97) ==3954==by 0x485EB0F: ffi_call_unix64 (unix64.S:76) ==3954==by 0x485E0A2: ffi_call (ffi64.c:525) ==3954==by 0x1968F8FD: wl_closure_invoke.constprop.0 (connection.c:1018) ==3954==by 0x1968FFCA: dispatch_event.isra.0 (wayland-client.c:1445) ==3954==by 0x1969019B: UnknownInlinedFun (wayland-client.c:1591) ==3954==by 0x1969019B: wl_display_dispatch_queue_pending (wayland-client.c:1833) ==3954==by 0x195CFD84: QtWaylandClient::QWaylandDisplay::forceRoundTrip() (qwaylanddisplay.cpp:476) ==3954==by 0x195D7513: QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) (qwaylanddisplay.cpp:351) ==3954==by 0x195EA88E: QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) (qwayland-wayland.cpp:94) ==3954== Address 0x8 is not stack'd, malloc'd or (recently) free'd ==3954== ==3954== ==3954== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==3954== Access not within mapped region at address 0x8 ==3954==at 0x6C1CE5B: operator-> (qscopedpointer.h:118) ==3954==by 0x6C1CE5B: qGetPtrHelper > (qglobal.h:1135) ==3954==by 0x6C1CE5B: d_func (qobject.h:132) ==3954==by 0x6C1CE5B: get (qobject_p.h:339) ==3954==by 0x6C1CE5B: void doActivate(QObject*, int, void**) (qobject.cpp:3768) ==3954==by 0x64B5EE1: QGuiApplication::screenAdded(QScreen*) (moc_qguiapplication.cpp:389) ==3954==by 0x195CF697: QtWaylandClient::QWaylandDisplay::handleScreenInitialized(QtWaylandClient::QWaylandScreen*) (qwaylanddisplay.cpp:281) ==3954==by 0x195DC622: QtWaylandClient::QWaylandScreen::maybeInitialize() (qwaylandscreen.cpp:97) ==3954==by 0x485EB0F: ffi_call_unix64 (unix64.S:76) ==3954==by 0x485E0A2: ffi_call (ffi64.c:525) ==3954==by 0x1968F8FD: wl_closure_invoke.constprop.0 (connection.c:1018) ==3954==by 0x1968FFCA: dispatch_event.isra.0 (wayland-client.c:1445) ==3954==by 0x1969019B: UnknownInlinedFun (wayland-client.c:1591) ==3954==by 0x1969019B: wl_display_dispatch_queue_pending (wayland-client.c:1833) ==3954==by 0x195CFD84: QtWaylandClient::QWaylandDisplay::forceRoundTrip() (qwaylanddisplay.cpp:476) ==3954==by 0x195D7513: QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) (qwaylanddisplay.cpp:351) ==3954==by 0x195EA88E: QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) (qwayland-wayland.cpp:94) ==3954== If you believe this happened as a result of a stack ==3954== overflow in your program's main thread (unlikely but ==3954== possible), you can try to increase the size of the ==3954== main thread stack using the --main-stacksize= flag. ==3954== The main thread stack size used in this run was 8388608. ==3954== ==3954== HEAP SUMMARY: ==3954== in use at exit: 462,865 bytes in 8,031 blocks ==3954== total heap usage: 9,700 allocs, 1,669 frees, 826,505 bytes allocated ==3954== ==3954== LEAK SUMMARY: ==3954==definitely lost: 0 bytes in 0 blocks ==3954==indirectly lost: 0 bytes in 0 blocks ==3954== possibly lost: 160 bytes in 2 blocks ==3954==still reachable: 462,705 bytes in 8,029 blocks ==3954== suppressed: 0 bytes in 0 blocks ==3954== Rerun with --leak-check=full to see details of leaked memory ==3954== ==3954== For lists of detected and suppressed errors, rerun with: -s ==3954== ERROR SUMMARY: 1
[kstars] [Bug 426899] New: kstars segmentation fault in doActivate when starting
https://bugs.kde.org/show_bug.cgi?id=426899 Bug ID: 426899 Summary: kstars segmentation fault in doActivate when starting Product: kstars Version: 3.4.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I installed kstars-3.4.3-3.fc33.x86_64 in a Fedora 33 KDE Plasma spin installation running Plasma 5.19.5 on Wayland. kstars segmentation faulted in doActivate or QScopedPointer >::operator-> at kernel/qobject.cpp:3766 in qt5-qtbase-5.15.1-1.fc33.x86_64 when starting each of a few times. Core was generated by `/usr/bin/kstars'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fcf10ad4e5b in QScopedPointer >::operator-> (this=) at kernel/qobject.cpp:3766 3766void doActivate(QObject *sender, int signal_index, void **argv) (gdb) bt #0 0x7fcf10ad4e5b in QScopedPointer >::operator-> (this=) at kernel/qobject.cpp:3766 #1 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1135 #2 QObject::d_func (this=) at kernel/qobject.h:132 #3 QObjectPrivate::get (o=) at kernel/qobject_p.h:339 #4 doActivate (sender=0x0, signal_index=9, argv=0x7ffc77021ce0) at kernel/qobject.cpp:3768 #5 0x7fcf10f08ee2 in QGuiApplication::screenAdded (this=, _t1=) at .moc/moc_qguiapplication.cpp:389 #6 0x7fcefe390698 in QtWaylandClient::QWaylandDisplay::handleScreenInitialized (this= 0x5581ed409b60, screen=) at qwaylanddisplay.cpp:281 #7 0x7fcefe39d623 in QtWaylandClient::QWaylandScreen::maybeInitialize (this=0x5581ed401a20) at qwaylandscreen.cpp:97 #8 QtWaylandClient::QWaylandScreen::maybeInitialize (this=0x5581ed401a20) at qwaylandscreen.cpp:86 #9 0x7fcefe26bb10 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #10 0x7fcefe26b0a3 in ffi_call (cif=cif@entry=0x7ffc77021e80, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffc77021f50) at ../src/x86/ffi64.c:525 #11 0x7fcefe3138fe in wl_closure_invoke (closure=closure@entry=0x5581ed414590, target=, target@entry=0x5581ed4126b0, opcode=opcode@entry=2, data=, flags=) at src/connection.c:1018 #12 0x7fcefe313fcb in dispatch_event (display=display@entry=0x5581ed409d10, queue=, queue=) at src/wayland-client.c:1445 #13 0x7fcefe31419c in dispatch_queue (queue=0x5581ed409de0, display=0x5581ed409d10) at src/wayland-client.c:1591 --Type for more, q to quit, c to continue without paging--c #14 wl_display_dispatch_queue_pending (display=0x5581ed409d10, queue=0x5581ed409de0) at src/wayland-client.c:1833 #15 0x7fcefe390d85 in QtWaylandClient::QWaylandDisplay::forceRoundTrip (this=this@entry=0x5581ed409b60) at qwaylanddisplay.cpp:476 #16 0x7fcefe398514 in QtWaylandClient::QWaylandDisplay::registry_global (this=0x5581ed409b60, id=21, interface=..., version=2) at qwaylanddisplay.cpp:351 #17 0x7fcefe3ab88f in QtWayland::wl_registry::handle_global (data=0x5581ed409b70, object=, name=21, interface=0x5581ed4122d0 "zxdg_output_manager_v1", version=2) at /usr/include/qt5/QtCore/qstring.h:701 #18 0x7fcefe26bb10 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #19 0x7fcefe26b0a3 in ffi_call (cif=cif@entry=0x7ffc77022320, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffc770223f0) at ../src/x86/ffi64.c:525 #20 0x7fcefe3138fe in wl_closure_invoke (closure=closure@entry=0x5581ed4121f0, target=, target@entry=0x5581ed409e60, opcode=opcode@entry=0, data=, flags=) at src/connection.c:1018 #21 0x7fcefe313fcb in dispatch_event (display=display@entry=0x5581ed409d10, queue=, queue=) at src/wayland-client.c:1445 #22 0x7fcefe31419c in dispatch_queue (queue=0x5581ed409de0, display=0x5581ed409d10) at src/wayland-client.c:1591 #23 wl_display_dispatch_queue_pending (display=0x5581ed409d10, queue=0x5581ed409de0) at src/wayland-client.c:1833 #24 0x7fcefe390d85 in QtWaylandClient::QWaylandDisplay::forceRoundTrip (this=this@entry=0x5581ed409b60) at qwaylanddisplay.cpp:476 #25 0x7fcefe396c59 in QtWaylandClient::QWaylandDisplay::QWaylandDisplay (this=, waylandIntegration=, this=, waylandIntegration=) at qwaylanddisplay.cpp:162 #26 0x7fcefe38d8eb in QtWaylandClient::QWaylandIntegration::QWaylandIntegration (this=, this=) at qwaylandintegration.cpp:115 #27 0x7fcf12f0f3b7 in QtWaylandClient::QWaylandIntegrationPlugin::create (this=, system=..., paramList=...) at main.cpp:59 #28 0x7fcf10f01f4b in QPlatformIntegrationFactory::create (platform=..., paramList=..., argc=@0x7ffc77022a5c: 1, argv=, platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:51 #29 0x7fcf10f0c690 in init_platform (argv=, argc=@0x7ffc77022a5c: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1223 #30
[plasmashell] [Bug 409021] Segmentation faults of plasmashell in wl_proxy_set_queue in libwayland-client in Plasma on Wayland
https://bugs.kde.org/show_bug.cgi?id=409021 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 --- Comment #7 from Matt Fagnani --- Created attachment 131424 --> https://bugs.kde.org/attachment.cgi?id=131424=edit New crash information added by DrKonqi plasmashell (5.19.5) using Qt 5.14.2 - What I was doing when the application crashed: I was using Plasma 5.19.5 on Wayland in Fedora 33. I set desktop to use the Application Menu by right-clicking on the button at the bottom left of the screen, selecting Show Alternatives > Application Menu > Switch. I clicked to open the Application Menu. I right clicked on the Kate and Konsole icons at the left side of the Application menu 4 times. The Task Manager at the bottom of the screen disappeared, they background went black, and they reappeared automatically. plasmashell aborted with the message The Wayland connection experienced a fatal error: Invalid argument. The journal at the time of the crash had the following. Sep 04 20:40:10 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:10 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x55d9c76159f0) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x55d9c67f81a0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents Sep 04 20:40:11 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:11 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:11 plasmashell[7606]: The Wayland connection experienced a fatal error: Invalid argument Sep 04 20:40:12 plasmashell[8628]: kf.plasma.quick: Applet preload policy set to 1 Sep 04 20:40:12 plasmashell[8628]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) I've seen this crash at least 4 times when right-clicking repeatedly on the Kate and Kontact icons on the left of the Application menu. -- Backtrace (Reduced): #4 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f6ee512d8a4 in __GI_abort () at abort.c:79 #6 0x7f6ee554fa7f in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffc433e4ba0, msg=msg@entry=0x7f6ed3d05dc8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893 #8 0x7f6ed3c95640 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414411] plasmashell on Wayland segmentation fault in update_buffers in mesa-libEGL
https://bugs.kde.org/show_bug.cgi?id=414411
Matt Fagnani changed:
What|Removed |Added
Summary|plasmashell 5.17.3 on |plasmashell on Wayland
|Wayland segmentation fault |segmentation fault in
|in update_buffers at|update_buffers in
|../src/egl/drivers/dri2/pla |mesa-libEGL
|tform_wayland.c:633 in |
|mesa-libEGL-19.2.6-1.fc31.x |
|86_64 |
Version|5.17.3 |5.19.4
URL||https://bugzilla.redhat.com
||/show_bug.cgi?id=133
--- Comment #3 from Matt Fagnani ---
I was using Plasma 5.19.4 on Wayland in Fedora 33 with KF 5.73.0 and Qt 5.14.2.
I set the desktop to use the Application Menu by right-clicking on the button
at the bottom left of the screen, selecting Show Alternatives > Application
Menu > Switch. I quickly left-clicked to open the Application Menu many times.
The Task Manager bar at the bottom of the screen disappeared and reappeared
automatically. plasmashell segmentation faulted in thread 1 in update_buffers
at ../src/egl/drivers/dri2/platform_wayland.c:675 in
mesa-libEGL-20.1.5-1.fc33.x86_64.
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49
49return ret;
[Current thread is 1 (Thread 0x7ff43ebf5640 (LWP 8914))]
(gdb) bt
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49
#1
#2 0x7ff4c815026d in update_buffers
(dri2_surf=dri2_surf@entry=0x7ff428166b70)
at ../src/egl/drivers/dri2/platform_wayland.c:675
#3 0x7ff4c81507e8 in image_get_buffers (driDrawable=,
format=,
stamp=, loaderPrivate=0x7ff428166b70, buffer_mask=,
buffers=0x7ff43ebf3ba0) at ../src/egl/drivers/dri2/platform_wayland.c:810
#4 0x7ff4c2a46b11 in dri_image_drawable_get_buffers
(statts_count=,
statts=, images=, drawable=)
at ../src/gallium/state_trackers/dri/dri2.c:282
#5 dri2_allocate_textures (ctx=0x55cc55a25e20, drawable=0x7ff42816b200,
statts=0x7ff428163cd8,
statts_count=2) at ../src/gallium/state_trackers/dri/dri2.c:415
#6 0x7ff4c2a39ee4 in dri_st_framebuffer_validate (stctx=,
stfbi=,
statts=0x7ff428163cd8, count=2, out=0x7ff43ebf3d40)
at ../src/gallium/state_trackers/dri/dri_drawable.c:82
#7 0x7ff4c2a5609b in st_framebuffer_validate
(stfb=stfb@entry=0x7ff428163800,
st=st@entry=0x55cc56ce6510) at ../src/mesa/state_tracker/st_manager.c:223
#8 0x7ff4c2a57143 in st_manager_validate_framebuffers (st=0x55cc56ce6510)
at ../src/mesa/state_tracker/st_manager.c:1185
#9 0x7ff4c2a8e605 in st_validate_state (st=st@entry=0x55cc56ce6510,
pipeline=pipeline@entry=ST_PIPELINE_CLEAR) at
../src/mesa/state_tracker/st_atom.c:203
#10 0x7ff4c2a8f100 in st_Clear (ctx=0x55cc56cabe50, mask=50)
at ../src/mesa/state_tracker/st_cb_clear.c:442
#11 0x7ff4de231d6b in QSGBatchRenderer::Renderer::renderBatches
(this=this@entry=0x7ff4280079a0)
at
../../include/QtQuick/5.14.2/QtQuick/private/../../../../../src/quick/scenegraph/coreapi/qsgrend--Type
for more, q to quit, c to continue without paging--c
erer_p.h:131
#12 0x7ff4de2324d2 in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:4320
#13 0x7ff4de21bcd0 in QSGRenderer::renderScene (bindable=...,
this=0x7ff4280079a0) at scenegraph/coreapi/qsgrenderer.cpp:259
#14 QSGRenderer::renderScene (this=0x7ff4280079a0, bindable=...) at
scenegraph/coreapi/qsgrenderer.cpp:219
#15 0x7ff4de21c1a3 in QSGRenderer::renderScene (this=,
fboId=) at scenegraph/coreapi/qsgrenderer.cpp:211
#16 0x7ff4de26f8e1 in QSGDefaultRenderContext::renderNextFrame
(this=0x55cc55d1d880, renderer=0x7ff4280079a0, fboId=) at
scenegraph/qsgdefaultrendercontext.cpp:223
#17 0x7ff4de2c99a9 in QQuickWindowPrivate::renderSceneGraph
(this=0x55cc55d1ccf0, size=..., surfaceSize=...) at items/qquickwindow.cpp:541
#18 0x7ff4de27c7e3 in QSGRenderThread::syncAndRender (this=0x55cc56979f50,
grabImage=0x0) at /usr/include/qt5/QtGui/5.14.2/QtGui/private/qrhi_p.h:1230
#19 0x7ff4de283e0f in QSGRenderThread::run (this=0x55cc56979f50) at
scenegraph/qsgthreadedrenderloop.cpp:980
#20 0x7ff4dc7eb690 in QThreadPrivate::start (arg=0x55cc56979f50) at
thread/qthread_unix.cpp:342
#21 0x7ff4dbc4f3f9 in start_thread (arg=0x7ff43ebf5640) at
pthread_create.c:463
#22 0x7ff4dc46fb03 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
platform_wayland.c:675 corresponds to that in the crash I reported here before.
if (dri2_surf->base.Width != dri2_surf->wl_win->width ||
dri2_surf->base.Height != dri2_surf->wl_win->height) {
The poi
[plasmashell] [Bug 409021] Segmentation faults of plasmashell in wl_proxy_set_queue in libwayland-client in Plasma on Wayland
https://bugs.kde.org/show_bug.cgi?id=409021
Matt Fagnani changed:
What|Removed |Added
Version|5.15.5 |5.19.4
Summary|Segmentation faults of |Segmentation faults of
|plasmashell in |plasmashell in
|wl_proxy_set_queue at |wl_proxy_set_queue in
|wayland-client.c:2094 in|libwayland-client in Plasma
|libwayland-client in Plasma |on Wayland
|5.15.5 on Wayland with Qt |
|5.12.4 |
--- Comment #7 from Matt Fagnani ---
I was using Plasma 5.19.4 on Wayland in Fedora 33 with KF 5.73.0 and Qt 5.14.2.
I set the desktop to use the Application Menu by right-clicking on the button
at the bottom left of the screen, selecting Show Alternatives > Application
Menu > Switch. I quickly left-clicked to open the Application Menu many times.
The Task Manager bar at the bottom of the screen disappeared and reappeared
automatically. plasmashell segmentation faulted in wl_proxy_set_queue at
src/wayland-client.c:2173 in libwayland-client-1.18.0-2.fc33.x86_64.
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49
49return ret;
[Current thread is 1 (Thread 0x7ff5eabe6640 (LWP 8221))]
(gdb) bt
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49
#1
#2 0x7ff688034ca5 in wl_proxy_set_queue (proxy=0x0, queue=0x55f4dc0e5790)
at src/wayland-client.c:2173
#3 0x7ff676c85f8d in QtWaylandClient::QWaylandWindow::waitForFrameSync
(timeout=100,
this=0x55f4dc0ae900) at qwaylandwindow.cpp:637
#4 QtWaylandClient::QWaylandWindow::waitForFrameSync
(this=this@entry=0x55f4dc0ae900,
timeout=timeout@entry=100) at qwaylandwindow.cpp:630
#5 0x7ff6740181ea in QtWaylandClient::QWaylandGLContext::swapBuffers
(this=0x55f4dcaacb10,
surface=0x55f4dc0ae910)
at
../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:482
#6 0x7ff68a00d0c4 in QSGRenderThread::syncAndRender (this=0x55f4dc923380,
grabImage=0x0)
at scenegraph/qsgthreadedrenderloop.cpp:841
#7 0x7ff68a013e0f in QSGRenderThread::run (this=0x55f4dc923380)
at scenegraph/qsgthreadedrenderloop.cpp:980
#8 0x7ff68857b690 in QThreadPrivate::start (arg=0x55f4dc923380) at
thread/qthread_unix.cpp:342
#9 0x7ff6879df3f9 in start_thread (arg=0x7ff5eabe6640) at
pthread_create.c:463
#10 0x7ff6881ffb03 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
The pointer proxy=0x0 passed to wl_proxy_set_queue might've led to a null
pointer dereference like in the crash I reported here before.
(gdb) l src/wayland-client.c:2173
2168 * \memberof wl_proxy
2169 */
2170WL_EXPORT void
2171wl_proxy_set_queue(struct wl_proxy *proxy, struct wl_event_queue
*queue)
2172{
2173if (queue)
2174proxy->queue = queue;
2175else
2176proxy->queue = >display->default_queue;
2177}
The crashes might involve a race condition in which the Wayland proxy of the
Application menu was occasionally freed or corrupted before it was used.
The use-after-free errors I reported in comment 1 might still be happening and
leading to the crashes. plasmashell crashed when I've quickly left-clicked to
open the Application Menu many times in the last day with errors like The
Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 and a segmentation fault in
update_buffers in mesa-libEGL https://bugs.kde.org/show_bug.cgi?id=414411 Those
crashes might have been related to this one.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Matt Fagnani --- I installed plasma-wayland-protocols-1.1.1-1.fc33. I have seen other plasmashell crashes since then, but not with this specific error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 --- Comment #2 from Matt Fagnani --- (In reply to David Edmundson from comment #1) > Can you confirm your version of plasma-wayland-protocols please plasma-wayland-protocols isn't installed on my system. I'll install plasma-wayland-protocols-1.1.1-1.fc33 from https://koji.fedoraproject.org/koji/buildinfo?buildID=1571963 and see if that makes a difference. Should plasma-wayland-protocols be a dependency of another plasma package? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Matt Fagnani changed: What|Removed |Added Component|general |generic-crash Summary|plasmashell aborted a |plasmashell aborted shortly |shortly after logging in|after logging in with the |with the error The Wayland |error The Wayland |connection experienced a|connection experienced a |fatal error: Invalid|fatal error: Invalid |argument|argument Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] New: plasmashell aborted a shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Bug ID: 424879 Summary: plasmashell aborted a shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument Product: plasmashell Version: 5.19.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.4) Qt Version: 5.14.2 Frameworks Version: 5.72.0 Operating System: Linux 5.8.0-0.rc7.1.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: I logged into Plasma 5.19.4 on Wayland from sddm in Fedora Rawhide with KF 5.72.0, Qt 5.14.2. plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument according to the journal. Jul 31 17:03:00 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE_610_QML_613(0x55cc662a2b20) Jul 31 17:03:00 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE_610_QML_613(0x55cc662a2b20) Jul 31 17:03:00 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE_610_QML_613(0x55cc662a2b20) Jul 31 17:03:00 plasmashell[5493]: trying to show an empty dialog Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: org.kde.plasmaquick: Couldn't create KWindowShadow for ToolTipDialog(0x55cc6522bad0) Jul 31 17:03:04 plasmashell[5493]: The Wayland connection experienced a fatal error: Invalid argument Jul 31 17:03:05 plasmashell[5998]: org.kde.plasmaquick: Applet preload policy set to 1 - Unusual behavior I noticed: The background went black. plasmashell restarted automatically The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f1fb07d08a4 in __GI_abort () at abort.c:79 #6 0x7f1fb0bf3a7f in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffc97230990, msg=msg@entry=0x7f1f9f338dc8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893 #8 0x7f1f9f2c8640 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 #9 0x7f1f9f2c868e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55cc641e0470) at qwaylanddisplay.cpp:209 #10 0x7f1fb0debfb0 in doActivate (sender=0x55cc641f5100, signal_index=4, argv=0x7ffc97230a70, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #11 0x7f1fb0de67f8 in QMetaObject::activate (sender=sender@entry=0x55cc641f5100, m=m@entry=0x7f1fb10748a0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #12 0x7f1fb0db9af7 in QAbstractEventDispatcher::awake (this=this@entry=0x55cc641f5100) at .moc/moc_qabstracteventdispatcher.cpp:149 #13 0x7f1fb0e08bac in QEventDispatcherGlib::processEvents (this=0x55cc641f5100, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #14 0x7f1fb0dbb91b in QEventLoop::exec (this=this@entry=0x7ffc97230b90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #15 0x7f1fb0dc35a6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #16 0x55cc63509705 in main () [Inferior 1 (process 5493) detached] The reporter
[systemsettings] [Bug 424729] New: system settings aborted while scrolling through systemd units because its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=424729 Bug ID: 424729 Summary: system settings aborted while scrolling through systemd units because its Wayland connection broke Product: systemsettings Version: 5.19.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Application: systemsettings5 (5.19.3) Qt Version: 5.14.2 Frameworks Version: 5.72.0 Operating System: Linux 5.8.0-0.rc6.20200723gitd15be546031c.1.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: I was using Plasma 5.19.3 on Wayland in a Fedora Rawhide KDE Plasma spin installation with KF 5.72 and Qt 5.14.2. I opened System settings. I selected systemd at the bottom of the left menu. I scrolled up and down the systemd units for up to 15 seconds. System settings showed Not responding in its top bar, and its colours faded. System settings aborted with the error "The Wayland connection broke. Did the Wayland compositor die?" System settings aborted 3 out of 3 times I did the steps above. I've seen system settings, plasmashell, konsole, ksysguard and others abort with the same error. https://bugs.kde.org/show_bug.cgi?id=414118 https://bugs.kde.org/show_bug.cgi?id=414116 https://bugs.kde.org/show_bug.cgi?id=413058 https://bugs.kde.org/show_bug.cgi?id=413901 The problem is likely in qtwayland. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f4c5e7d78a4 in __GI_abort () at abort.c:79 #6 0x7f4c5ebfaa7f in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffeb9501340, msg=msg@entry=0x7f4c4cc79160 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x7f4c4cbfc8a9 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 #9 QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:191 #10 0x7f4c4cc0b09d in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) (this=0x5591daafe0a0, queue=0x5591dad40c20, condition=..., timeout=timeout@entry=100) at qwaylanddisplay.cpp:247 #11 0x7f4c4cc0fe2f in QtWaylandClient::QWaylandWindow::waitForFrameSync (this=0x5591dac6af60, timeout=100) at /usr/include/c++/10/new:175 #12 0x7f4c4ad9ac32 in QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x5591dbc6da70, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:482 #13 0x7f4c5f4bee8a in QPlatformBackingStore::composeAndFlush (this=this@entry=0x5591dad607f0, window=0x5591dac10b10, region=..., offset=..., textures=textures@entry=0x5591dc91c880, translucentBackground=translucentBackground@entry=false) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116 #14 0x7f4c5f80840b in QWidgetRepaintManager::flush (this=this@entry=0x5591dad60890, widget=0x5591dab4e0d0, region=..., widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1187 #15 0x7f4c5f80a48b in QWidgetRepaintManager::flush (this=this@entry=0x5591dad60890) at kernel/qwidgetrepaintmanager.cpp:1090 #16 0x7f4c5f80bfee in QWidgetRepaintManager::paintAndFlush (this=) at kernel/qwidgetrepaintmanager.cpp:1022 #17 0x7f4c5f83ca97 in QWidget::event (this=this@entry=0x5591dab4e0d0, event=event@entry=0x5591db4afa60) at kernel/qwidget.cpp:8978 #18 0x7f4c5f94b530 in QMainWindow::event (this=this@entry=0x5591dab4e0d0, event=event@entry=0x5591db4afa60) at widgets/qmainwindow.cpp:1341 #19 0x7f4c602c3ecd in KMainWindow::event (this=this@entry=0x5591dab4e0d0, ev=ev@entry=0x5591db4afa60) at /usr/src/debug/kf5-kxmlgui-5.72.0-1.fc33.x86_64/src/kmainwindow.cpp:885 #20 0x7f4c602f2c0d in KXmlGuiWindow::event (this=0x5591dab4e0d0, ev=0x5591db4afa60) at /usr/src/debug/kf5-kxmlgui-5.72.0-1.fc33.x86_64/src/kxmlguiwindow.cpp:121 #21 0x7f4c5f7fb063 in QApplicationPrivate::notify_helper (this=, receiver=0x5591dab4e0d0, e=0x5591db4afa60) at kernel/qapplication.cpp:3685 #22 0x7f4c5edc3fc0 in QCoreApplication::notifyInternal2 (receiver=0x5591dab4e0d0, event=0x5591db4afa60) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #23 0x7f4c5edc6c47 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5591daae4000) at kernel/qcoreapplication.cpp:1815 #24 0x7f4c5ee100a7 in postEventSourceDispatch (s=s@entry=0x5591dab233c0) at kernel/qeventdispatcher_glib.cpp:277 #25 0x7f4c5cb3beaf in
[plasmashell] [Bug 414116] Plasmashell aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=414116 --- Comment #3 from Matt Fagnani --- Created attachment 130090 --> https://bugs.kde.org/attachment.cgi?id=130090=edit New crash information added by DrKonqi plasmashell (5.19.3) using Qt 5.14.2 - What I was doing when the application crashed: I logged into Plasma 5.19.3 on Wayland in Fedora Rawhide with Qt 5.14.2, KF 5.72.0 from sddm. I've continued to see these plasmashell crashes where the Wayland connection broke occasionally when logging in and at other times like when using Firefox. The crashes happened particularly when there's been high I/O to the drive Fedora was on. Several KDE programs aborted each time I logged out of Plasma 5.19.3 and earlier on Wayland with the same error. Is there a setting that could increase something like a timeout duration for Qt programs before the Wayland connection is considered to be broken? - Unusual behavior I noticed: The background went black and automatically reappeared. -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f28fadfa8a4 in __GI_abort () at abort.c:79 #6 0x7f28fb21da7f in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffe676728f0, msg=msg@entry=0x7f28e997c160 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x7f28e98ff8a9 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423682] New: system settings segmentation fault in QtWaylandClient::QWaylandWindow::decoration when selecting activities and closing
https://bugs.kde.org/show_bug.cgi?id=423682
Bug ID: 423682
Summary: system settings segmentation fault in
QtWaylandClient::QWaylandWindow::decoration when
selecting activities and closing
Product: systemsettings
Version: 5.19.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
Application: systemsettings5 (5.19.2)
Qt Version: 5.14.2
Frameworks Version: 5.71.0
Operating System: Linux 5.8.0-0.rc3.1.fc33.x86_64 x86_64
Windowing system: Wayland
Distribution: Fedora 33 (KDE Plasma Prerelease)
-- Information about the crash:
- What I was doing when the application crashed:
I was using Plasma 5.19.2 on Wayland in a Fedora Rawhide KDE Plasma spin
installation with KF 5.71.0, Qt 5.14.2. I started System Settings on Wayland. I
selected Workspace Behavior > Activities. The left menus were black as I
reported at https://bugs.kde.org/show_bug.cgi?id=418291 The main part of System
Settings wasn't displaying normally. I closed System Settings. A segmentation
fault in System Settings happened in
QtWaylandClient::QWaylandWindow::decoration at qwaylandwindow.cpp:825. this=0x0
in QtWaylandClient::QWaylandWindow::decoration might indicate a null pointer
dereference as the reason for the segmentation fault. qwaylandwindow.cpp:825
returns mWindowDecoration in QtWaylandClient::QWaylandWindow::decoration
QWaylandAbstractDecoration *QWaylandWindow::decoration() const
{
return mWindowDecoration;
}
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
[KCrash Handler]
#4 QtWaylandClient::QWaylandWindow::decoration (this=0x0) at
qwaylandwindow.cpp:825
#5 0x7f31b8a01759 in
QtWaylandClient::QWaylandShmBackingStore::windowDecoration
(this=this@entry=0x5623ea6448c0) at qwaylandshmbackingstore.cpp:362
#6 0x7f31b8a021c6 in QtWaylandClient::QWaylandShmBackingStore::resize
(this=this@entry=0x5623ea6448c0, size=...) at qwaylandshmbackingstore.cpp:308
#7 0x7f31b8a02301 in QtWaylandClient::QWaylandShmBackingStore::ensureSize
(this=this@entry=0x5623ea6448c0) at qwaylandshmbackingstore.cpp:205
#8 0x7f31b8a0233d in QtWaylandClient::QWaylandShmBackingStore::beginPaint
(this=this@entry=0x5623ea6448c0, region=...) at qwaylandshmbackingstore.cpp:180
#9 0x7f31cb08ddad in QBackingStore::beginPaint (this=0x5623ea6bc0c0,
region=...) at
../../include/QtGui/5.14.2/QtGui/private/../../../../../src/gui/kernel/qhighdpiscaling_p.h:109
#10 0x7f31cb4f3e0e in QWidgetRepaintManager::paintAndFlush (this=) at kernel/qwidgetrepaintmanager.cpp:984
#11 0x7f31cb524a97 in QWidget::event (this=this@entry=0x5623ea4b5020,
event=event@entry=0x5623ec3b09d0) at kernel/qwidget.cpp:8978
#12 0x7f31cb633530 in QMainWindow::event (this=this@entry=0x5623ea4b5020,
event=event@entry=0x5623ec3b09d0) at widgets/qmainwindow.cpp:1341
#13 0x7f31cbfabf4d in KMainWindow::event (this=this@entry=0x5623ea4b5020,
ev=ev@entry=0x5623ec3b09d0) at
/usr/src/debug/kf5-kxmlgui-5.71.0-1.fc33.x86_64/src/kmainwindow.cpp:885
#14 0x7f31cbfdac3d in KXmlGuiWindow::event (this=0x5623ea4b5020,
ev=0x5623ec3b09d0) at
/usr/src/debug/kf5-kxmlgui-5.71.0-1.fc33.x86_64/src/kxmlguiwindow.cpp:121
#15 0x7f31cb4e3063 in QApplicationPrivate::notify_helper (this=, receiver=0x5623ea4b5020, e=0x5623ec3b09d0) at
kernel/qapplication.cpp:3685
#16 0x7f31caaabfc0 in QCoreApplication::notifyInternal2
(receiver=0x5623ea4b5020, event=0x5623ec3b09d0) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#17 0x7f31caaaec47 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5623ea44b000) at
kernel/qcoreapplication.cpp:1815
#18 0x7f31caaf80a7 in postEventSourceDispatch (s=s@entry=0x5623ea466630) at
kernel/qeventdispatcher_glib.cpp:277
#19 0x7f31c882beaf in g_main_dispatch (context=0x5623ea47aa30) at
../glib/gmain.c:3309
#20 g_main_context_dispatch (context=0x5623ea47aa30) at ../glib/gmain.c:3974
#21 0x7f31c882c238 in g_main_context_iterate
(context=context@entry=0x5623ea47aa30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4047
#22 0x7f31c882c303 in g_main_context_iteration (context=0x5623ea47aa30,
may_block=may_block@entry=1) at ../glib/gmain.c:4108
#23 0x7f31caaf7b73 in QEventDispatcherGlib::processEvents
(this=0x5623ea49d2f0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7f31c91b in QEventLoop::exec (this=this@entry=0x7fff34ad2850,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#25 0x7f31caab25a6 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#26 0x5623e98290cf in main (argc=, argv=0x7fff34ad2970) at
[kwin] [Bug 423602] kwin_wayland segmentation fault in std::__atomic_base::operator++ when using vlc
https://bugs.kde.org/show_bug.cgi?id=423602 --- Comment #1 from Matt Fagnani --- I've seen two more kwin_wayland segmentation faults when using Plasma 5.19.2, KF 5.71.0, Qt 5.14.2 while playing videos in vlc. The first such crash had the same trace as I reported here before. The second segmentation fault was in std::__atomic_base::load. Both traces involved QPointer::QPointer at /usr/include/qt5/QtCore/qpointer.h:62 operator() at /usr/src/debug/kwayland-server-5.19.2-1.fc33.x86_64/src/server/pointer_interface.cpp:241 When the mouse pointer is over the video in vlc without moving for a few seconds, the mouse pointer normally disappears. When the mouse is moved after the pointer disappeared, the mouse pointer reappeared. The problem might be related to this mouse pointer disappearing/appearing. Memory corruption might have led to invalid pointers involving the KWaylandServer::SurfaceInterface being passed to QPointer::QPointer. Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/libexec/st'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f97c432473e in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:741 warning: Source file is more recent than executable. 741 load(memory_order __m = memory_order_seq_cst) const noexcept [Current thread is 1 (Thread 0x7f97c473be00 (LWP 18029))] (gdb) thread apply all bt Thread 21 (Thread 0x7f9762a86680 (LWP 18109)): #0 0x7f97c3f2e31f in __GI___poll (fds=0x7f9754004630, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f97c1a6a1ce in g_main_context_poll (priority=, n_fds=1, fds=0x7f9754004630, timeout=, context=0x7f9754000c20) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f9754000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f97c1a6a303 in g_main_context_iteration (context=0x7f9754000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f97c44c5b73 in QEventDispatcherGlib::processEvents (this=0x7f9754000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f97c447891b in QEventLoop::exec (this=this@entry=0x7f9762a85be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f97c42e4427 in QThread::exec (this=this@entry=0x5601801df8b0) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f97c2fc77a9 in QQmlThreadPrivate::run (this=0x5601801df8b0) at qml/ftw/qqmlthread.cpp:155 #8 0x7f97c42e5690 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:342 #9 0x7f97c4f783f9 in start_thread (arg=0x7f9762a86680) at pthread_create.c:462 #10 0x7f97c3f393b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f974e346680 (LWP 22467)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x560180c037d0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560180c03780, cond=0x560180c037a8) at p--Type for more, q to quit, c to continue without paging--c thread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560180c037a8, mutex=0x560180c03780) at pthread_cond_wait.c:638 #3 0x7f97acac12ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f97acac0d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f97c4f783f9 in start_thread (arg=0x7f974e346680) at pthread_create.c:462 #6 0x7f97c3f393b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f9763fff680 (LWP 18105)): #0 0x7f97c3f2e31f in __GI___poll (fds=0x7f975c004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f97c1a6a1ce in g_main_context_poll (priority=, n_fds=1, fds=0x7f975c004e60, timeout=, context=0x7f975c000c20) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f975c000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f97c1a6a303 in g_main_context_iteration (context=0x7f975c000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f97c44c5b73 in QEventDispatcherGlib::processEvents (this=0x7f975c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f97c447891b in QEventLoop::exec (this=this@entry=0x7f9763ffebe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f97c42e4427 in QThread::exec (this=this@entry=0x560180073040) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f97c2fc77a9 in QQmlThreadPrivate::run (this=0x560180073040) at qml/ftw/qqmlthread.cpp:155 #8 0x7f97c42e5690 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:342 #9 0x7f97c4f783f9 in start_thread (arg=0x7f9763fff680) at pthread_create.c:462 #10 0x7f97c3f393b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64
[kwin] [Bug 423602] New: kwin_wayland segmentation fault in std::__atomic_base::operator++ when using vlc
https://bugs.kde.org/show_bug.cgi?id=423602 Bug ID: 423602 Summary: kwin_wayland segmentation fault in std::__atomic_base::operator++ when using vlc Product: kwin Version: 5.19.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY I was using Plasma 5.19.2 on Wayland in Fedora Rawhide with KF 5.71.0, Qt 5.14.2, Mesa 20.1.2. I started VLC 3.0.11 (from rpmfusion). I played an mp4 file for about 8 minutes. Plasma froze for a few minutes, and then sddm appeared. The systemd-coredump process for the kwin_wayland crash didn't complete correctly possibly due to timing out. I found the kwin_wayland core dump file in /var/lib/systemd/coredump/ kwin_wayland had a segmentation fault in thread 1 in std::__atomic_base::operator++ at /usr/include/c++/10/bits/atomic_base.h:325 due to an invalid pointer this=0x7000700070006 Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/libexec/st'. Program terminated with signal SIGSEGV, Segmentation fault. #0 std::__atomic_base::operator++ (this=0x7000700070006) at /usr/include/c++/10/bits/atomic_base.h:325 325 operator++() noexcept [Current thread is 1 (Thread 0x7fdd0dea1e00 (LWP 12932))] The trace involved kwayland-server-5.19.2-1.fc33. Functions related to the position of the pointer such as QPointer::QPointer in #5 were in parts of the trace. (gdb) thread apply all bt Thread 21 (Thread 0x7fdcf9802680 (LWP 12933)): #0 0x7fdd0d69231f in __GI___poll (fds=0x7fdcf40184a0, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdd0b1ce1ce in g_main_context_poll (priority=, n_fds=4, fds=0x7fdcf40184a0, timeout=, context=0x7fdcf4001ce0) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7fdcf4001ce0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7fdd0b1ce303 in g_main_context_iteration (context=0x7fdcf4001ce0, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7fdd0dc29b73 in QEventDispatcherGlib::processEvents (this=0x7fdcf4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7fdd0dbdc91b in QEventLoop::exec (this=this@entry=0x7fdcf9801bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7fdd0da48427 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7fdd0e65c51b in QDBusConnectionManager::run (this=0x7fdd0e6cb060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #8 0x7fdd0da49690 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:342 #9 0x7fdd0e6dc3f9 in start_thread (arg=0x7fdcf9802680) at pthread_create.c:462 #10 0x7fdd0d69d3b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fdce1a97680 (LWP 12942)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d6e53d8738) at ../sysdeps/nptl/futex-internal.h:183 --Type for more, q to quit, c to continue without paging--c #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d6e53d86e8, cond=0x55d6e53d8710) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d6e53d8710, mutex=0x55d6e53d86e8) at pthread_cond_wait.c:638 #3 0x7fdcf1c252ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fdcf1c24d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fdd0e6dc3f9 in start_thread (arg=0x7fdce1a97680) at pthread_create.c:462 #6 0x7fdd0d69d3b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fdc97fff680 (LWP 13004)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fdd0d473478) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fdd0d473428, cond=0x7fdd0d473450) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fdd0d473450, mutex=0x7fdd0d473428) at pthread_cond_wait.c:638 #3 0x7fdd0d37f01c in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #4 0x7fdd0d37f04f in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #5 0x7fdd0e6dc3f9 in start_thread (arg=0x7fdc97fff680) at pthread_create.c:462 #6 0x7fdd0d69d3b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fdcd1ffb680 (LWP 14500)): #0 0x7fdd0d69231f in __GI___poll (fds=0x7fdcb000f2d0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdd0b1ce1ce in g_main_context_poll (priority=, n_fds=1, fds=0x7fdcb000f2d0, timeout=, context=0x7fdcb000a3c0) at ../glib/gmain.c:4346 #2
[frameworks-kwayland] [Bug 416974] Plasma 5.17.90 crashed due to a kwin_wayland segmentation fault in QWeakPointer::QWeakPointer
https://bugs.kde.org/show_bug.cgi?id=416974
Matt Fagnani changed:
What|Removed |Added
Version|5.67.0 |5.71.0
--- Comment #2 from Matt Fagnani ---
I've continued to see kwin_wayland crashes occasionally with traces like those
I reported here up to and including Plasma 5.19.2 on Wayland, KF 5.71.0, Qt
5.14.2 in Fedora Rawhide particularly when using vlc in full screen mode or
Firefox. kwin_wayland crashed with the versions above while I was using
Thunderbird 68.9.0 on Wayland, and I opened the Preferences screen. Plasma
froze for a few minutes, and the systemd-coredump process timed out. The core
dump was present in /var/lib/systemd/coredump/. The segmentation fault was at
std::__atomic_base::operator++ at
/usr/include/c++/10/bits/atomic_base.h:325 likely due to an invalid pointer
this=0x51
QWeakPointer::QWeakPointer at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:587 was at #3 in the trace
instead of #0. The xp value looked abnormal in pos = {xp =
6.9286700983935495e-310, yp = 0} in #6 in operator() at
/usr/src/debug/kwayland-server-5.19.2-1.fc33.x86_64/src/server/pointer_interface.cpp:230
in kwayland-server-5.19.2-1.fc33 instead of kf5-kwayland as before. In the
first trace I reported here, frame #3 in
KWayland::Server::PointerInterfaceoperator() at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/pointer_interface.cpp:247
had similarly abnormal values pos = {xp = 6.941689537196333e-310, yp =
6.9531853373731582e-310}.
Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/libexec/st'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 std::__atomic_base::operator++ (this=0x51) at
/usr/include/c++/10/bits/atomic_base.h:325
325 operator++() noexcept
[Current thread is 1 (Thread 0x7f8baae0de00 (LWP 1209))]
(gdb) bt full
#0 std::__atomic_base::operator++ (this=0x51) at
/usr/include/c++/10/bits/atomic_base.h:325
No locals.
#1 QAtomicOps::ref (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:283
No locals.
#2 QBasicAtomicInteger::ref (this=0x51) at
/usr/include/qt5/QtCore/qbasicatomic.h:118
No locals.
#3 QWeakPointer::QWeakPointer (other=..., this=0x7327f080)
at /usr/include/qt5/QtCore/qsharedpointer_impl.h:587
No locals.
#4 QPointer::QPointer
(this=0x7327f080)
at /usr/include/qt5/QtCore/qpointer.h:53
No locals.
#5 KWaylandServer::SurfaceInterface::lockedPointer (this=)
at
/usr/src/debug/kwayland-server-5.19.2-1.fc33.x86_64/src/server/surface_interface.cpp:937
d =
#6 0x7f8bab719e7e in operator() (__closure=,
__closure=)
at
/usr/src/debug/kwayland-server-5.19.2-1.fc33.x86_64/src/server/pointer_interface.cpp:230
d = 0x55f224c44b40
pos = {xp = 6.9286700983935495e-310, yp = 0}
targetSurface =
this =
this =
d =
pos =
targetSurface =
--Type for more, q to quit, c to continue without paging--c
originSurface =
proxyRemoteFocused =
serial =
adjustedPos =
#7 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KWaylandServer::PointerInterface::PointerInterface(KWaylandServer::SeatInterface*,
wl_resource*):: >::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
No locals.
#8
QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
No locals.
#9
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
No locals.
#10 0x7f8baab7af76 in QtPrivate::QSlotObjectBase::call (a=0x7327f210,
r=0x55f224c392d0, this=0x55f224c40bf0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
No locals.
#11 doActivate (sender=0x55f2244569c0, signal_index=8,
argv=argv@entry=0x7327f210) at kernel/qobject.cpp:3870
obj = std::unique_ptr = {get() =
0x55f224c40bf0}
receiver = 0x55f224c392d0
td =
receiverInSameThread =
senderData = {previous = 0x0, receiver = 0x55f224c392d0, sender =
0x55f2244569c0, signal = 8}
c = 0x55f224541680
connections = {d = 0x55f224472ed0}
list =
inSenderThread = true
highestConnectionId = 73
signalVector = 0x55f224c99220
currentThreadId = 0x7f8baae0de00
sp =
signal_spy_set = 0x0
empty_argv = {0x0}
senderDeleted = false
#12 0x7f8baab757f8 in QMetaObject::activate
(sender=sender@entry=0x55f2244569c0, m=m@entry=0x7f8bab79d020
,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7327f210)
at kernel/qobject.cpp:3930
signal_index =
#13 0x7f8bab6e6fa9 in KWaylandServer::SeatInterface::pointerPosChanged
(this=this@e
[plasmashell] [Bug 423559] New: plasmashell segmentation fault in DeclarativeMimeData::DeclarativeMimeData when dragging and dropping a link from Firefox to Konsole
https://bugs.kde.org/show_bug.cgi?id=423559 Bug ID: 423559 Summary: plasmashell segmentation fault in DeclarativeMimeData::DeclarativeMimeData when dragging and dropping a link from Firefox to Konsole Product: plasmashell Version: 5.19.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.2) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.8.0-0.rc2.20200625git8be3a53e18e0.1.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: I was using a Fedora Rawhide KDE Plasma spin installation with Plasma 5.19.2, KF 5.71.0, Qt 5.14.2. I started Plasma on Wayland. I started Konsole 20.04.2 on Wayland. I opened Firefox Nightly 79.0a1 (2020-6-26) on Wayland. I went to youtube. I resized Firefox. I dragged and dropped a link from Firefox to Konsole. A plasmashell segmentation fault in DeclarativeMimeData::DeclarativeMimeData at /usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:55 in kf5-kdeclarative-5.71.0-1.fc33 happened. The link showed up correctly in Konsole. - Unusual behavior I noticed: The task manager bar disappeared from the bottom of the screen and reappeared. I tried the same procedure a few times, but the crash didn't happen again. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f716ef0fa63 in DeclarativeMimeData::DeclarativeMimeData (this=0x55e8b255ca10, copy=0x55e8b232f970) at /usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:55 #5 0x7f716ef0efb0 in DeclarativeDragDropEvent::mimeData (this=0x7ffea00cc8c0) at /usr/include/qt5/QtGui/qevent.h:656 #6 0x7f716ef09d35 in DeclarativeDragDropEvent::qt_static_metacall (_a=, _id=, _c=, _o=) at /usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/x86_64-redhat-linux-gnu/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:121 #7 DeclarativeDragDropEvent::qt_static_metacall (_o=, _c=, _id=, _a=) at /usr/src/debug/kf5-kdeclarative-5.71.0-1.fc33.x86_64/x86_64-redhat-linux-gnu/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:93 #8 0x7f71bf06e0b1 in QQmlPropertyData::readPropertyWithArgs (args=0x7ffea00caa10, target=0x7ffea00cc8c0, this=0x55e8b3052c28) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:274 #9 QQmlPropertyData::readProperty (property=0x7ffea00ca9f0, target=0x7ffea00cc8c0, this=0x55e8b3052c28) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:268 #10 loadProperty (v4=0x55e8b0f9c1f0, object=0x7ffea00cc8c0, property=...) at jsruntime/qv4qobjectwrapper.cpp:138 #11 0x7f71bf08c3c1 in QV4::Moth::VME::interpret (frame=0x7ffea00cac10, engine=0x55e8b0f9c1f0, code=0x7f715a6a94ba ":\004:\005\030\b\022>\030\v\246\006\b\001\v\030\b\006b\bL\005\246\a\006") at jsruntime/qv4vme_moth.cpp:638 #12 0x7f71bf0909c7 in QV4::Moth::VME::exec (frame=frame@entry=0x7ffea00cac10, engine=engine@entry=0x55e8b0f9c1f0) at jsruntime/qv4vme_moth.cpp:463 #13 0x7f71bf02d53d in QV4::Function::call (this=this@entry=0x55e8b19cb160, thisObject=, argv=argv@entry=0x7f71a9bc2508, argc=, context=) at jsruntime/qv4function.cpp:69 #14 0x7f71bf194955 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x55e8b19b12b0, callData=callData@entry=0x7f71a9bc24d8, isUndefined=isUndefined@entry=0x0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #15 0x7f71bf14bf5e in QQmlBoundSignalExpression::evaluate (this=, a=) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #16 0x7f71bf14c498 in QQmlBoundSignal_callback (e=0x55e8b19b6fd0, a=0x7ffea00cc890) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #17 0x7f71bf17a5bd in QQmlNotifier::emitNotify (endpoint=, a=0x7ffea00cc890) at qml/qqmlnotifier.cpp:104 #18 0x7f71bdb92ee2 in doActivate (sender=0x55e8b196de30, signal_index=30, argv=argv@entry=0x7ffea00cc890) at /usr/include/c++/10/bits/atomic_base.h:741 #19 0x7f71bdb8d7f8 in QMetaObject::activate (sender=sender@entry=0x55e8b196de30, m=m@entry=0x7f716ef17480 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffea00cc890) at kernel/qobject.cpp:3930 #20 0x7f716ef09663 in DeclarativeDropArea::dragEnter
[kwin] [Bug 422711] New: kwin_wayland segmentation fault in KWin::LibInput::Connection::applyScreenToDevice when logging in
https://bugs.kde.org/show_bug.cgi?id=422711
Bug ID: 422711
Summary: kwin_wayland segmentation fault in
KWin::LibInput::Connection::applyScreenToDevice when
logging in
Product: kwin
Version: 5.18.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
I booted the Fedora Rawhide KDE Plasma live spin
Fedora-KDE-Live-x86_64-Rawhide-20200603.n.0.iso which has Plasma 5.18.5, KF
5.70.0/1, Qt 5.14.2. I created a new user in System Settings with a password. I
installed kwin-wayland, plasma-workspace-wayland, and their dependencies. I
logged out of Plasma on X. I selected the user I created in sddm. I entered an
incorrect password and tried to login 3 times. The login was denied. I switched
the user to the liveuser and tried to log in to Plasma on Wayland. The screen
was briefly black then it went back to sddm. The next login to Plasma on
Wayland worked properly. coredumpctl showed that kwin_wayland had a
segmentation fault in KWin::LibInput::Connection::applyScreenToDevice at
/usr/src/debug/kwin-5.18.5-1.fc33.x86_64/libinput/../screens.h:220 which
occurred on the first login to Plasma on Wayland which didn't complete
properly. The full trace of all threads from coredumpctl was the following.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 KWin::LibInput::Connection::applyScreenToDevice
(this=this@entry=0x5635f74f4300, device=device@entry=0x5635f7605b60) at
/usr/src/debug/kwin-5.18.5-1.fc33.x86_64/libinput/../screens.h:220
220 return m_count;
[Current thread is 1 (Thread 0x7fc60d857e00 (LWP 10125))]
(gdb) thread apply all bt full
Thread 4 (Thread 0x7fc5f37fe680 (LWP 10128)):
#0 0x7fc60c941abf in poll () from /lib64/libc.so.6
No symbol table info available.
#1 0x7fc60a43dace in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#2 0x7fc60a43dc03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#3 0x7fc60cee1b73 in QEventDispatcherGlib::processEvents
(this=0x7fc5e4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
d = 0x7fc5e4000b80
canWait = true
savedFlags = {i = 0}
result =
#4 0x7fc60ce9491b in QEventLoop::exec (this=this@entry=0x7fc5f37fdc00,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
d = 0x7fc5e4003090
locker = {val = 94789782694168}
ref =
app =
#5 0x7fc60cd00427 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
d = 0x5635f75368c0
locker = {val = 94789782694168}
eventLoop = { = {_vptr.QObject = 0x7fc60d14d948 , static sta--Type for more, q to quit, c to continue
without paging--c
ticMetaObject = {d = {superdata = {direct = 0x0}, stringdata = 0x7fc60d0342e0
, data = 0x7fc60d0341c0 ,
static_metacall = 0x7fc60cec3350 , relatedMetaObjects = 0x0, extradata = 0x0}},
d_ptr = {d = 0x7fc5e4003090}, static staticQtMetaObject = {d = {superdata =
{direct = 0x0}, stringdata = 0x7fc60d037260 , data =
0x7fc60d034400 , static_metacall = 0x0, relatedMetaObjects =
0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = {direct =
0x7fc60d1452c0 }, stringdata = 0x7fc60d02e4e0
, data = 0x7fc60d02e480
, static_metacall = 0x7fc60ce94630
,
relatedMetaObjects = 0x0, extradata = 0x0}}}
returnCode =
#6 0x7fc60cd01690 in QThreadPrivate::start(void*) () at
thread/qthread_unix.cpp:342
currentThreadData = 0x5635f75370b0
current_thread_data_once = 2
current_thread_data_key = 3
(anonymous namespace)::destroy_current_thread_data_key_dtor_instance_ =
{}
#7 0x7fc60d994479 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#8 0x7fc60c94cb53 in clone () from /lib64/libc.so.6
No symbol table info available.
Thread 3 (Thread 0x7fc5f3fff680 (LWP 10127)):
#0 0x7fc60c941abf in poll () from /lib64/libc.so.6
No symbol table info available.
#1 0x7fc60a43dace in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#2 0x7fc60a43dc03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
No symbol table info available.
#3 0x7fc60cee1b73 in QEventDispatcherGlib::processEvents
(this=0x7fc5ec000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
d = 0x7fc5ec000b80
canWait = true
savedFlags = {i = 0}
result =
#4 0x7fc60ce9491b in QEventLoop::exec (this=this@entry=0x7fc5f3ffec00,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
d = 0x7fc5ec003890
locker
[plasmashell] [Bug 421170] New: plasmashell 5.18.5 on Wayland segmentation fault in QVector::indexOf
https://bugs.kde.org/show_bug.cgi?id=421170 Bug ID: 421170 Summary: plasmashell 5.18.5 on Wayland segmentation fault in QVector::indexOf Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.0-0.rc4.1.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: I booted a Fedora Rawhide KDE Plasma spin live image Fedora-KDE-Live-x86_64-Rawhide-20200505.n.0.iso. In Plasma System Settings, I shut off autologin, reduced the screen brightness, changed the compositor rendering backend to OpenGL 3.1, and shut off the lock screen. I logged out. I switched to a VT and ran sudo dnf upgrade --refresh -x kernel*. The update included Plasma 5.18.5 and KF 5.70.0. I installed kwin-wayland, plasma-workspace-wayland, xorg-x11-drv-amdgpu, and their dependencies. I logged out of the VT and switched to sddm. I logged into Plasma on Wayland. I added the firefox on wayland icon from the menu to the desktop. I sorted the icons into columns using the right-click menu on the desktop. plasmashell crashed with a segmentation fault in QVector::indexOf at /usr/include/qt5/QtCore/qvector.h:1008 in qt 5.14.2. I saw this crash twice before on the previous boot when clicking on a Thundebird on Wayland icon on the desktop in Plasma 5.18.5 on Wayland. I hadn't seen plasmashell crashes with this traces with Plasma 5.18.4.1 and KF 5.69.0 and earlier. - Unusual behavior I noticed: The desktop went black. plasmashell restarted automatically. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8ff0c49380 (LWP 4443))] Thread 34 (Thread 0x7f8f3aff7700 (LWP 4855)): #0 0x7f8feec99b02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fd623a12b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f8fd6239bfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f8feec93472 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8fef4a39d3 in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f8f3b7f8700 (LWP 4852)): #0 0x7f8feec99b02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fd623a12b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f8fd6239bfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f8feec93472 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8fef4a39d3 in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f8f70ff9700 (LWP 4833)): #0 0x7f8feec99b02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fd623a12b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f8fd6239bfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f8feec93472 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8fef4a39d3 in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f8f3bff9700 (LWP 4830)): #0 0x7f8feec99b02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fd623a12b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f8fd6239bfb in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f8feec93472 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8fef4a39d3 in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f8f48c21700 (LWP 4828)): #0 0x7f8feec99b02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fef82dd5b in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x561000533ae0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x56100055dda0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f8ff13840f2 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x56100055dd98) at scenegraph/qsgthreadedrenderloop.cpp:255 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x56100055dd00) at scenegraph/qsgthreadedrenderloop.cpp:905 #5 0x7f8ff1386639 in QSGRenderThread::run (this=0x56100055dd00) at scenegraph/qsgthreadedrenderloop.cpp:1000 #6 0x7f8fef828640 in QThreadPrivate::start (arg=0x56100055dd00) at thread/qthread_unix.cpp:342 #7 0x7f8feec93472 in start_thread () from /lib64/libpthread.so.0 #8 0x7f8fef4a39d3 in clone () from
[frameworks-kinit] [Bug 420262] kdeinit5 segmentation fault in XRenderHasDepths when using dolphin to open a firefox directory
https://bugs.kde.org/show_bug.cgi?id=420262 --- Comment #1 from Matt Fagnani --- Created attachment 127676 --> https://bugs.kde.org/attachment.cgi?id=127676=edit valgrind log when run on kdeinit5 and opening the firefox directory in dolphin Opening /usr/lib64/firefox from firefox-75.0-2.fc33.x86_64 in dolphin led to the same crash, so downloading Firefox Nightly 77.0a1 isn't necessary to reproduce it. I ran valgrind --log-file=valgrind-kdeinit5-dolphin-crash-2.txt /usr/bin/kdeinit5 and opened the Firefox Nightly directory in dolphin. Multiple SIGTERM and SIGALRM were sent to kdeinit5 according to the valgrind log. Several Conditional jump or move depends on uninitialised value(s) messages occurred. An invalid read happened in XAddExtension at InitExt.c:73 in libX11-1.6.9-3.fc32.x86_64. ==38773== Invalid read of size 8 ==38773==at 0x48ED597: XAddExtension (InitExt.c:73) ==38773==by 0x293D7E7C: _XftDisplayInfoGet.part.0 (xftdpy.c:91) ==38773==by 0x293DCA9D: XftFontInfoFill (xftfreetype.c:367) ==38773==by 0x293DD35F: XftFontOpenPattern (xftfreetype.c:1015) ==38773==by 0x289EB0E7: KFI::CFcEngine::queryFont() (FcEngine.cpp:1233) ==38773==by 0x289EB8B7: UnknownInlinedFun (FcEngine.cpp:1391) ==38773==by 0x289EB8B7: KFI::CFcEngine::getSizes() (FcEngine.cpp:1383) ==38773==by 0x289ECECF: KFI::CFcEngine::draw(QString const&, unsigned int, int, QColor const&, QColor const&, int, int, bool, QList const&, QList*) (FcEngine.cpp:876) ==38773==by 0x289DFA1B: KFI::CFontThumbnail::create(QString const&, int, int, QImage&) (FontThumbnail.cpp:114) ==38773==by 0x485126C: ThumbnailProtocol::createSubThumbnail(QImage&, QString const&, int, int) (thumbnail.cpp:727) ==38773==by 0x485158B: ThumbnailProtocol::drawSubThumbnail(QPainter&, QString const&, int, int, int, int, int) (thumbnail.cpp:759) ==38773==by 0x4851B99: ThumbnailProtocol::thumbForDirectory(QUrl const&) (thumbnail.cpp:562) ==38773==by 0x4852D37: ThumbnailProtocol::get(QUrl const&) (thumbnail.cpp:238) ==38773== Address 0x6574726f7078655f is not stack'd, malloc'd or (recently) free'd Functions like _XftDisplayInfoGet and lower in the stack showing the invalid read were in the crashing thread of kdeinit5. I'm attaching the valgrind log. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 420262] New: kdeinit5 segmentation fault in XRenderHasDepths when using dolphin to open a firefox directory
https://bugs.kde.org/show_bug.cgi?id=420262 Bug ID: 420262 Summary: kdeinit5 segmentation fault in XRenderHasDepths when using dolphin to open a firefox directory Product: frameworks-kinit Version: 5.68.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I was using Plasma 5.18.4.1 on Wayland in the Fedora Rawhide live image Fedora-KDE-Live-x86_64-Rawhide-20200414.n.0.iso which has KF 5.68.0, Qt 5.14.2. I downloaded Firefox Nightly 77.0a1 (2020-4-18). I extracted Firefox using ark 19.12.3. I opened dolphin 19.12.3 on Wayland, and I selected the firefox directory in dolphin. A segmentation fault in kdeinit5 in XRenderHasDepths at Xrender.c:126 in libXrender-0.9.10-11.fc32.x86_64 was shown by dr. konqi. The same crash was shown 4/4 times when I opened the firefox directory in dolphin. The trace has some functions involving thumbnails so some thumbnails in the firefox directory might be involved. Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcbb0939dc0 (LWP 30869))] Thread 14 (Thread 0x7fcb637fe700 (LWP 30882)): #0 0x7fcbb06bfb00 in QTimerInfoList::repairTimersIfNeeded() () from /lib64/libQt5Core.so.5 #1 0x7fcbb06bfb97 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #2 0x7fcbb06c129e in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #3 0x7fcbaee85002 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #4 0x7fcbaee85a1b in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #5 0x7fcbaee85c23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #6 0x7fcbb06c156b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fcbb067430b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #8 0x7fcbb04e03d7 in QThread::exec() () from /lib64/libQt5Core.so.5 #9 0x7fcb9f17c51b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #10 0x7fcbb04e1640 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #11 0x7fcbaf8d4472 in start_thread () from /lib64/libpthread.so.0 #12 0x7fcbb034c9b3 in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fcb63fff700 (LWP 30881)): #0 0x7fcbaf8dab02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcb9c04afcb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcb9c04aa9b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcbaf8d4472 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcbb034c9b3 in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fcb8cff9700 (LWP 30880)): #0 0x7fcbaf8dab02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcb9c04afcb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcb9c04aa9b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcbaf8d4472 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcbb034c9b3 in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fcb8d7fa700 (LWP 30879)): #0 0x7fcbaf8dab02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcb9c04afcb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcb9c04aa9b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcbaf8d4472 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcbb034c9b3 in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fcb8dffb700 (LWP 30878)): #0 0x7fcbaf8dab02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcb9c04afcb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcb9c04aa9b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcbaf8d4472 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcbb034c9b3 in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fcb8e7fc700 (LWP 30877)): #0 0x7fcbaf8dab02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcb9c04afcb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcb9c04aa9b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fcbaf8d4472 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcbb034c9b3 in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fcb8effd700 (LWP 30876)): #0 0x7fcbaf8dab02 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcb9c04afcb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fcb9c04aa9b in
[kwin] [Bug 409688] kwin_wayland aborted when shutting down involving invalid reads and writes, use of uninitialized variables etc.
https://bugs.kde.org/show_bug.cgi?id=409688 Matt Fagnani changed: What|Removed |Added Version|5.15.5 |5.18.3 --- Comment #2 from Matt Fagnani --- (In reply to Roman Gilg from comment #1) > Thanks for the awesome protocols! But your version of Plasma is super-old. > Would you be able to retry with current 5.18? > > I'm asking this because I'm currently looking into KScreenLocker. Roman, kwin_wayland aborted or segmentation faulted each time I've shutdown or rebooted with Plasma 5.18.3 and earlier, KF 5.67, Qt 5.13.2 in Fedora 32. Some examples from the journal are the following. Mar 16 07:32:01 audit[1249]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1249 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Mar 16 07:32:01 kernel: kwin_wayland[1249]: segfault at 564b57f98f80 ip 564b57f98f80 sp 7ffdf4350278 error 15 Mar 16 10:34:40 audit[1253]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1253 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=6 res=1 systemd-coredump doesn't try to save the coredumps during shutdown and reboots though. /usr/bin/startplasmacompositor doesn't seem to exist in Plasma 5.18.3. the kwin_wayland command line shows /usr/libexec/startplasma-waylandsession is used. /usr/libexec/startplasma-waylandsession is an ELF binary, so I guess I'd need to know the source file /usr/libexec/startplasma-waylandsession is created from, edit it to run kwin_wayland under valgrind, rebuild and update the rpms, then shutdown/reboot. I'll look into that and comment here if I can get it going. kwin_wayland also segmentation faulted when I've logged out of Plasma on Wayland, and the traces involved the mesa radeonsi driver as reported at https://bugs.kde.org/show_bug.cgi?id=416147 Those kwin_wayland logout crashes might be related to those when shutting down and rebooting. The commit Registry: don't destroy the callback on globalsync by Daniel Vrátil at https://cgit.kde.org/kwayland.git/commit/?id=4ceb35672dfa3378776a926c452b9f83ffe2bc41 looks like it should fix the invalid reads/writes in wl_proxy_unref in libwayland-client which I've seen with every KDE program I've run on Wayland under valgrind. The patch was added for kwayland 5.68.0. KF 5.68.0 hasn't been built yet for Fedora from what I can see. Thanks for checking out this problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418602] New: plasmashell aborted when logging in to Plasma on Wayland with the message "The Wayland connection experienced a fatal error: Protocol error"
https://bugs.kde.org/show_bug.cgi?id=418602 Bug ID: 418602 Summary: plasmashell aborted when logging in to Plasma on Wayland with the message "The Wayland connection experienced a fatal error: Protocol error" Product: plasmashell Version: 5.18.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: 1.0 SUMMARY I've seen plasmashell abort when logging into Plasma on Wayland in a Fedora 32 KDE Plasma spin installation. The plasmashell aborts have occurred about 12 times from Plasma 5.17.4 - 5.18.2. The screen was black except for the cursor which moved around normally. plasmashell didn't restart automatically. These plasmashell crashes have usually happened after a Plasma on Wayland session had crashed and sddm reappeared. The following plasmashell abort was with Plasma 5.18.2, KF 5.67.0, Qt 5.13.2 after a kwin_wayland segmentation fault of the type I reported at https://bugs.kde.org/show_bug.cgi?id=416974 Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50return ret; [Current thread is 1 (Thread 0x7f85a1aac580 (LWP 3242))] (gdb) thread apply all bt Thread 3 (Thread 0x7f858d69c700 (LWP 3636)): #0 0x7f859f9639cf in __GI___poll (fds=0x7f85800029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f859e57fa8d in g_main_context_poll (priority=, n_fds=1, fds=0x7f85800029e0, timeout=, context=0x7f858c30) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f858c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f859e57fbc3 in g_main_context_iteration (context=0x7f858c30, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f859fec1b75 in QEventDispatcherGlib::processEvents (this=0x7f858b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f859fe751db in QEventLoop::exec (this=this@entry=0x7f858d69bd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f859fcea6e7 in QThread::exec (this=this@entry=0x55cee4c18fc0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f85a1442d89 in QQmlThreadPrivate::run (this=0x55cee4c18fc0) at qml/ftw/qqmlthread.cpp:152 #8 0x7f859fceb9b6 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:360 #9 0x7f859f206432 in start_thread (arg=) at pthread_create.c:477 #10 0x7f859f96e833 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f858e934700 (LWP 3244)): #0 0x7f859f9639cf in __GI___poll (fds=0x7f85880029e0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f859e57fa8d in g_main_context_poll (priority=, n_fds=2, fds=0x7f85880029e0, t--Type for more, q to quit, c to continue without paging--c imeout=, context=0x7f8588000c30) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f8588000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f859e57fbc3 in g_main_context_iteration (context=0x7f8588000c30, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f859fec1b75 in QEventDispatcherGlib::processEvents (this=0x7f8588000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f859fe751db in QEventLoop::exec (this=this@entry=0x7f858e933d50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f859fcea6e7 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f85a0dc64da in QDBusConnectionManager::run (this=0x7f85a0e34060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f859fceb9b6 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:360 #9 0x7f859f206432 in start_thread (arg=) at pthread_create.c:477 #10 0x7f859f96e833 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f85a1aac580 (LWP 3242)): #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7f859f892895 in __GI_abort () at abort.c:79 #2 0x7f859fcb7a25 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1907 #3 QMessageLogger::fatal (this=this@entry=0x7fff06080940, msg=msg@entry=0x7f858ef47e70 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:888 #4 0x7f858eeb4c24 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:91 #5 0x7f858eeb4c7e in QtWaylandClient::QWaylandDisplay::flushRequests
[frameworks-kwayland] [Bug 416974] Plasma 5.17.90 crashed due to a kwin_wayland segmentation fault in QWeakPointer::QWeakPointer
https://bugs.kde.org/show_bug.cgi?id=416974 Matt Fagnani changed: What|Removed |Added CC||kwin-bugs-n...@kde.org Assignee|kwin-bugs-n...@kde.org |mgraess...@kde.org Version|5.17.90 |5.67.0 Platform|Other |Fedora RPMs Product|kwin|frameworks-kwayland Component|wayland-generic |server --- Comment #1 from Matt Fagnani --- I've continued seeing these kwin_wayland segmentation faults with Plasma 5.18.2, KF 5.67.0, Qt 5.13.2 in Fedora 32 when using firefox, vlc, and system settings. The crashes when using vlc were with vlc in full screen mode. I'm reassigning this report to frameworks-wayland because the trace involved kwayland where the invalid pointers started in KWayland::Server::SurfaceInterface::lockedPointer at /usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/surface_interface.cpp:937. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 418244] plasmashell segmentation fault in KScreen::GetConfigOperation::start when logging into Plasma 5.18.2 on Wayland
https://bugs.kde.org/show_bug.cgi?id=418244 Matt Fagnani changed: What|Removed |Added Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org Product|plasmashell |KScreen Version|master |git Target Milestone|1.0 |--- Component|generic-wayland |libkscreen --- Comment #3 from Matt Fagnani --- This crash was fixed in Fedora in libkscreen-qt5-5.18.2-2.fc32 https://koji.fedoraproject.org/koji/buildinfo?buildID=1472018 which added the commit https://cgit.kde.org/libkscreen.git/commit/?id=069bb65af0d0059391323f9ffd2edd9162d57588 That patch was added to the libkscreen 5.18 branch after the 5.18.2 tag was created https://cgit.kde.org/libkscreen.git/log/?h=Plasma/5.18 I'm reassigning this report to kscreen. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418291] New: Clicking on Activities in System Settings on Plasma on Wayland turned the left menus black
https://bugs.kde.org/show_bug.cgi?id=418291 Bug ID: 418291 Summary: Clicking on Activities in System Settings on Plasma on Wayland turned the left menus black Product: systemsettings Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_activities Assignee: ivan.cu...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: --- Created attachment 126479 --> https://bugs.kde.org/attachment.cgi?id=126479=edit System Settings with black left menus after clicking Activities SUMMARY I was using Plasma 5.18.2 on Wayland in a Fedora 32 KDE Plasma spin installation. I started System Settings. I selected Workspace Behaviour, and then I clicked on Activities. The two menus on the left side of System Settings became black. Clicking on the black part could still change the panel on the right to different ones, and the popups still appeared. The left menus remained black though after selecting a different screen. I'm attaching a picture of the screen with System Settings when the black menus appeared. STEPS TO REPRODUCE 1. Boot a Fedora 32 KDE Plasma spin installation fully updated to 2020-2-28 with kwin-wayland, plasma-workspace-wayland and their dependencies installed 2. Log in to Plasma 5.18.2 on Wayland 3. Start System Settings 4. Select Workspace Behaviour 5. Click on Activities OBSERVED RESULT Clicking on Activities in System Settings on Plasma turned the left menus black EXPECTED RESULT The menu would appear normally after clicking on Activities SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION These black menus didn't occur when I selected Activities in System Settings in Plasma 5.18.2 on X. The issue appears to be specific to Wayland. The problem was present in System Settings 5.18.1 and possibly in earlier versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418244] plasmashell segmentation fault in KScreen::GetConfigOperation::start when logging into Plasma 5.18.2 on Wayland
https://bugs.kde.org/show_bug.cgi?id=418244 --- Comment #2 from Matt Fagnani --- A patch in GetConfigOperation::start at getconfigoperation.cpp:174-176 to fix a null pointer dereference where the segmentation fault occurred was at https://cgit.kde.org/libkscreen.git/commit/?id=069bb65af0d0059391323f9ffd2edd9162d57588 https://phabricator.kde.org/D27625 The patch was listed in the 5.18.2 Changelog for libkscreen "Fix: handle when backend fails to load/initialize. Commit. Phabricator Code review D27625" https://kde.org/announcements/plasma-5.18.1-5.18.2-changelog.php The if block checking for null backend added by the commit doesn't appear in /usr/src/debug/libkscreen-qt5-5.18.2-1.fc32.x86_64/src/getconfigoperation.cpp at line 174. That patch might need to be added to fix these crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418244] plasmashell segmentation fault in KScreen::GetConfigOperation::start when logging into Plasma 5.18.2 on Wayland
https://bugs.kde.org/show_bug.cgi?id=418244 Matt Fagnani changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-wayland --- Comment #1 from Matt Fagnani --- I should've written that after the first such crash, the desktop icons were in four columns while they were normally in three columns. I've seen this crash 4/4 times when logging into Plasma 5.18.2 on Wayland. These plasmashell crashes might be related to the patch for the kded5 crashes when logging into Plasma 5.17.90 and later on Wayland at https://bugs.kde.org/show_bug.cgi?id=416566#c6 The kded5 crashing thread had functions with Config in their names in libkscreen-qt5 in frame #8 KScreen::WaylandConfig::applyConfig at /usr/src/debug/libkscreen-qt5-5.18.0-1.fc32.x86_64/backends/kwayland/waylandconfig.cpp:330 and #9 KScreen::SetConfigOperation::start() at /usr/src/debug/libkscreen-qt5-5.18.0-1.fc32.x86_64/src/setconfigoperation.cpp:129 https://bugs.kde.org/show_bug.cgi?id=416566#c2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418244] New: plasmashell segmentation fault in KScreen::GetConfigOperation::start when logging into Plasma 5.18.2 on Wayland
https://bugs.kde.org/show_bug.cgi?id=418244 Bug ID: 418244 Summary: plasmashell segmentation fault in KScreen::GetConfigOperation::start when logging into Plasma 5.18.2 on Wayland Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.2) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 5.6.0-0.rc3.git0.1.fc32.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 32 (Thirty Two) -- Information about the crash: - What I was doing when the application crashed: I updated to Plasma 5.18.2 in a Fedora 32 KDE Plasma spin installation with KF5 5.67, Qt 5.13.2, Mesa 20.0.0. I logged into Plasma on Wayland from sddm. A plasmashell segmentation fault in KScreen::GetConfigOperation::start happened at /usr/src/debug/libkscreen-qt5-5.18.2-1.fc32.x86_64/src/getconfigoperation.cpp:174. I haven't seen crashes with this trace with Plasma 5.18.1 and earlier. This crash happened 2/2 times when logging into Plasma 5.18.2. - Unusual behavior I noticed: The screen went black while logging in after the splash screen. plasmashell restarted automatically. After the first such crash, the desktop icons were in three columns while they were normally in two columns. The icons were normal after the second crash and plasmashell restart. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fc64a892580 (LWP 1425))] Thread 20 (Thread 0x7fc5f4e52700 (LWP 1867)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fc5f4e51cc0, clockid=, expected=0, futex_word=0x5617e0e0a130) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fc5f4e51cc0, clockid=, mutex=0x5617e0e0a0e0, cond=0x5617e0e0a108) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x5617e0e0a108, mutex=0x5617e0e0a0e0, abstime=0x7fc5f4e51cc0) at pthread_cond_wait.c:656 #3 0x7fc648f9f4d9 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (deadline=..., this=0x5617e0e0a0e0) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x5617e0e0a0e0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5617e0e09f70, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fc648f9f5fb in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5617e08884a0, mutex=0x5617e0e09f70, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fc648f9d5e3 in QThreadPoolThread::run() (this=0x5617e0888490) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #8 0x7fc648f999b6 in QThreadPrivate::start(void*) (arg=0x5617e0888490) at thread/qthread_unix.cpp:360 #9 0x7fc6484b4432 in start_thread (arg=) at pthread_create.c:477 #10 0x7fc648c1c833 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fc5db5e9700 (LWP 1851)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5617e0a82dd8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5617e0a82d88, cond=0x5617e0a82db0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5617e0a82db0, mutex=0x5617e0a82d88) at pthread_cond_wait.c:638 #3 0x7fc62f30a07b in cnd_wait (mtx=0x5617e0a82d88, cond=0x5617e0a82db0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x5617e0aa1180) at ../src/util/u_queue.c:275 #5 0x7fc62f309b5b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fc6484b4432 in start_thread (arg=) at pthread_create.c:477 #7 0x7fc648c1c833 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fc5f5a7a700 (LWP 1833)): #0 g_source_ref (source=) at ../glib/gmain.c:2166 #1 0x7fc64782b8c8 in g_source_iter_next (iter=iter@entry=0x7fc5f5a79b90, source=source@entry=0x7fc5f5a79b88) at ../glib/gmain.c:1046 #2 0x7fc64782ce8b in g_main_context_prepare (context=context@entry=0x7fc5d4000c30, priority=priority@entry=0x7fc5f5a79c10) at ../glib/gmain.c:3597 #3 0x7fc64782d96b in g_main_context_iterate (context=context@entry=0x7fc5d4000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4027 #4 0x7fc64782db73 in g_main_context_iteration (context=0x7fc5d4000c30, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #5 0x7fc64916fb93 in
[KScreen] [Bug 416566] kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 Matt Fagnani changed: What|Removed |Added Version|5.17.90 |5.18.0 --- Comment #5 from Matt Fagnani --- (In reply to Roman Gilg from comment #4) > Do you have a device with orientation sensor and the iio-sensor-proxy > package installed? No the hp laptop I've seen these crashes on doesn't have an orientation sensor. The iio-sensor-proxy package isn't installed. Thanks for looking into this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416566] kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 --- Comment #2 from Matt Fagnani --- Created attachment 125991 --> https://bugs.kde.org/attachment.cgi?id=125991=edit kded5 segmentation fault trace when logging into Plasma 5.18.0 on Wayland Roman, I've seen the kded5 crash one of two times when logging into Plasma 5.18.0 on Wayland. KWayland::Client::WaylandPointer::operator org_kde_kwin_outputmanagement* (this=) at /usr/src/debug/kf5-kwayland-5.67.0-1.fc32.x86_64/x86_64-redhat-linux-gnu/src/client/wayland-output-management-client-protocol.h:226 has been at the top of the crashing thread 1 since I updated to KF 5.67.0. I'll attach the trace of the crash which happened in a Fedora 32 KDE Plasma spin installation with Plasma 5.18.0, KF 5.67.0, and Qt 5.13.2. I saw this kded5 crash at least 32 times with Plasma 5.17.90 on Wayland which was about 30% of the times I logged in. kded5 has restarted normally after it has crashed when I've checked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414116] Plasmashell aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=414116 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416974] New: Plasma 5.17.90 crashed due to a kwin_wayland segmentation fault in QWeakPointer::QWeakPointer
https://bugs.kde.org/show_bug.cgi?id=416974
Bug ID: 416974
Summary: Plasma 5.17.90 crashed due to a kwin_wayland
segmentation fault in
QWeakPointer::QWeakPointer
Product: kwin
Version: 5.17.90
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
I was using Plasma 5.17.90 on Wayland in Fedora Rawhide with KF 5.66.0, Qt
5.13.2, Mesa 19.3.3. I started VLC 3.0.9 (from rpmfusion). I played a video and
paused it after a few minutes. Plasma froze for about 3 minutes, and then sddm
appeared. The systemd-coredump process for the kwin_wayland crash didn't
complete correctly possibly due to timing out. I found the kwin_wayland core
dump file in /var/lib/systemd/coredump/ kwin_wayland had a segmentation fault
in
QWeakPointer::QWeakPointer at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:589. The full trace of the
crashing thread 1 showed what looked like a invalid pointer d = 0x20 from
frames 0 to 2 in KWayland::Server::SurfaceInterface::lockedPointer at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/surface_interface.cpp:937.
The underlying problem might be in kwayland.
Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/libexec/st'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 QWeakPointer::QWeakPointer (other=..., this=0x7fff3257acb0)
at /usr/include/qt5/QtCore/qsharedpointer_impl.h:589
589 /usr/include/qt5/QtCore/qsharedpointer_impl.h: No such file or
directory.
[Current thread is 1 (Thread 0x7fc905ad7900 (LWP 1269))]
(gdb) bt full
#0 QWeakPointer::QWeakPointer(QWeakPointer const&)
(other=..., this=0x7fff3257acb0)
at /usr/include/qt5/QtCore/qsharedpointer_impl.h:589
d = 0x20
#1
QPointer::QPointer(QPointer
const&) (this=0x7fff3257acb0) at /usr/include/qt5/QtCore/qpointer.h:53
d = 0x20
#2 KWayland::Server::SurfaceInterface::lockedPointer() const (this=)
at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/surface_interface.cpp:937
d = 0x20
#3 0x7fc906938809 in
KWayland::Server::PointerInterfaceoperator()
(__closure=)
at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/pointer_interface.cpp:247
d = 0x5585256ff410
pos = {xp = 6.941689537196333e-310, yp = 6.9531853373731582e-310}
targetSurface =
#4 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KWayland::Server::PointerInterface::PointerInterface(KWayland::Server::SeatInterface*,
wl_resource*):: >::call
(arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#5
QtPrivate::Functor, 0>::call, void> (arg=, f=...)
at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#6
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=, r=,
a=, ret= for more, q to quit, c to
continue without paging--c
out>) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:439
#7 0x7fc905d74a60 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff3257ae30, r=0x5585255ffd80, this=0x5585256ef150) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
obj = {d = 0x5585256ef150}
receiver = 0x5585255ffd80
receiverInSameThread =
sw = {receiver = 0x5585255ffd80, previousSender = 0x0, currentSender =
{sender = 0x558524d49310, signal = 8, ref = 1}, switched = true}
c = 0x558525704a70
last = 0x5585256118d0
locker = {val = 140501365871928}
connectionLists = {connectionLists = 0x558524d49690}
list =
currentThreadId = 0x7fc905ad7900
signal_index = 8
empty_argv = {0x0}
#8 QMetaObject::activate(QObject*, int, int, void**) (sender=0x558524d49310,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3789
obj = {d = 0x5585256ef150}
receiver = 0x5585255ffd80
receiverInSameThread =
sw = {receiver = 0x5585255ffd80, previousSender = 0x0, currentSender =
{sender = 0x558524d49310, signal = 8, ref = 1}, switched = true}
c = 0x558525704a70
last = 0x5585256118d0
locker = {val = 140501365871928}
connectionLists = {connectionLists = 0x558524d49690}
list =
currentThreadId = 0x7fc905ad7900
signal_index = 8
empty_argv = {0x0}
#9 0x7fc906909899 in
KWayland::Server::SeatInterface::pointerPosChanged(QPointF const&)
(this=this@entry=0x558524d49310, _t1=...) at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/x86_64-redhat-linux-gnu/src/server/KF5WaylandServer_autogen/EWIEGA46WW/moc_seat_interface.cpp:451
_a = {0x0, 0x7fff3257ae90}
#10 0x7fc906941c02 in
[frameworks-kded] [Bug 416566] New: kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguration when logging into Plasma 5.17.90 on Wayland
https://bugs.kde.org/show_bug.cgi?id=416566 Bug ID: 416566 Summary: kded5 segmentation faults in KWayland::Client::OutputManagement::createConfiguratio n when logging into Plasma 5.17.90 on Wayland Product: frameworks-kded Version: 5.66.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: matthew.fagn...@utoronto.ca CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I logged into Plasma 5.17.90 on Wayland in Fedora Rawhide with KF5 5.66.0, Qt 5.13.2. Dr. Konqi immediately showed a segmentation fault in kded5 in KWayland::Client::OutputManagement::createConfiguration(QObject*) (this=0x0, parent=) at /usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/x86_64-redhat-linux-gnu/src/client/wayland-output-management-client-protocol.h:226. this=0x0 might indicate a problem with a null pointer. Application: kded5 (kded5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f1fa8b4d800 (LWP 1350))] Thread 5 (Thread 0x7f1f8e23f700 (LWP 1381)): #0 0x7f1fa7c269af in __GI___poll (fds=0x55d0cbdf2490, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1fa6df9e1e in g_main_context_poll (priority=, n_fds=1, fds=0x55d0cbdf2490, timeout=, context=0x55d0cbe13540) at ../glib/gmain.c:4309 #2 g_main_context_iterate (context=context@entry=0x55d0cbe13540, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4005 #3 0x7f1fa6df9f53 in g_main_context_iteration (context=0x55d0cbe13540, may_block=1) at ../glib/gmain.c:4071 #4 0x7f1f8e252abd in dconf_gdbus_worker_thread () at /usr/lib64/gio/modules/libdconfsettings.so #5 0x7f1fa6e23682 in g_thread_proxy (data=0x55d0cbdcfd40) at ../glib/gthread.c:805 #6 0x7f1fa7781482 in start_thread (arg=) at pthread_create.c:477 #7 0x7f1fa7c31583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f1f8700 (LWP 1372)): #0 __GI___libc_read (nbytes=16, buf=0x7f1f8fffecc0, fd=15) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=15, buf=buf@entry=0x7f1f8fffecc0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f1fa6e422cf in read (__nbytes=16, __buf=0x7f1f8fffecc0, __fd=) at /usr/include/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x55d0cbddac60) at ../glib/gwakeup.c:210 #4 0x7f1fa6df9967 in g_main_context_check (context=context@entry=0x55d0cbde00e0, max_priority=2147483647, fds=fds@entry=0x55d0cbde1f80, n_fds=n_fds@entry=1) at ../glib/gmain.c:3788 #5 0x7f1fa6df9dc2 in g_main_context_iterate (context=0x55d0cbde00e0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4007 #6 0x7f1fa6dfa1a3 in g_main_loop_run (loop=0x55d0cbde01d0) at ../glib/gmain.c:4204 #7 0x7f1f94f75b7a in gdbus_shared_thread_func (user_data=0x55d0cbde00b0) at ../gio/gdbusprivate.c:279 #8 0x7f1fa6e23682 in g_thread_proxy (data=0x55d0cbdcf4a0) at ../glib/gthread.c:805 #9 0x7f1fa7781482 in start_thread (arg=) at pthread_create.c:477 #10 0x7f1fa7c31583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1f949bf700 (LWP 1371)): #0 0x7f1fa7c269af in __GI___poll (fds=0x55d0cbdcd9e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1fa6df9e1e in g_main_context_poll (priority=, n_fds=1, fds=0x55d0cbdcd9e0, timeout=, context=0x55d0cbdcf2b0) at ../glib/gmain.c:4309 #2 g_main_context_iterate (context=context@entry=0x55d0cbdcf2b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4005 #3 0x7f1fa6df9f53 in g_main_context_iteration (context=0x55d0cbdcf2b0, may_block=may_block@entry=1) at ../glib/gmain.c:4071 #4 0x7f1fa6df9fa1 in glib_worker_main (data=) at ../glib/gmain.c:5959 #5 0x7f1fa6e23682 in g_thread_proxy (data=0x55d0cbdcf400) at ../glib/gthread.c:805 #6 0x7f1fa7781482 in start_thread (arg=) at pthread_create.c:477 #7 0x7f1fa7c31583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1f95a87700 (LWP 1364)): #0 0x7f1fa7c269af in __GI___poll (fds=0x7f1f900029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1fa6df9e1e in g_main_context_poll (priority=, n_fds=1, fds=0x7f1f900029e0, timeout=, context=0x7f1f9c30) at ../glib/gmain.c:4309 #2 g_main_context_iterate (context=context@entry=0x7f1f9c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4005 #3 0x7f1fa6df9f53 in g_main_context_iteration (context=0x7f1f9c30, may_block=may_block@entry=1) at ../glib/gmain.c:4071 #4 0x7f1fa81c58b3 in QEventDispatcherGlib::processEvents(QFlags)
[kate] [Bug 416315] New: Kate aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=416315 Bug ID: 416315 Summary: Kate aborted when its Wayland connection broke Product: kate Version: 19.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Application: kate (19.12.1) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.5.0-0.rc6.git0.1.fc32.x86_64 x86_64 Distribution: Fedora 32 (Rawhide) -- Information about the crash: - What I was doing when the application crashed: I was running Plasma 5.17.5 on Wayland in Fedora Rawhide with Qt 5.13.2, KF 5.66.0, Mesa 19.3.2. I opened Konsole 19.2.1. I opened a second tab. I ran coredumpctl gdb on a kwin_wayland crash which happened when logging out on the previous boot. I reported those type of kwin_wayland crashes at https://bugs.kde.org/show_bug.cgi?id=416147. The core dump file was 2.1 GB, and it took a few minutes for coredumpctl gdb to decompress and process the core dump. I ran bt in gdb to get a trace. Konsole stopped responding for about a minute with Not Responding in the title bar. Konsole's colours faded. Konsole disappeared. The trace in Dr. Konqi showed the error "The Wayland connection broke. Did the Wayland compositor die?" in frame 9 of the crashing thread 1. I've previously seen Konsole abort with that error as in my report at https://bugs.kde.org/show_bug.cgi?id=413058. I've also seen that error for plasmashell https://bugs.kde.org/show_bug.cgi?id=414116 ksysguard https://bugs.kde.org/show_bug.cgi?id=413901 system settings https://bugs.kde.org/show_bug.cgi?id=414118 I opened konsole again and ran coredumpctl gdb. I ran bt and thread apply all bt full. I opened Kate 19.12.1 and copied the coredumpctl gdb output to kate. I saved the output to a file. I pasted additional output to Kate and remove a line. I saved the file. Kate showed Not Responding in its title bar for a few seconds, and its colors faded. Kate aborted with the error "The Wayland connection broke. Did the Wayland compositor die?" in frame 9 of the crashing thread 1. The underlying problem might be in Qt particularly qtwayland. -- Backtrace: Application: Kate (kate), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fedf88b0c80 (LWP 3884))] Thread 12 (Thread 0x7fedbaffd700 (LWP 3895)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e00bb3380) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e00bb3330, cond=0x558e00bb3358) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e00bb3358, mutex=0x558e00bb3330) at pthread_cond_wait.c:638 #3 0x7fedde22ab0b in cnd_wait (mtx=0x558e00bb3330, cond=0x558e00bb3358) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x558e00bb4690) at ../src/util/u_queue.c:275 #5 0x7fedde22a71b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fedf60f5482 in start_thread (arg=) at pthread_create.c:477 #7 0x7fedf7215583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fedbb7fe700 (LWP 3894)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e00bb3380) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e00bb3330, cond=0x558e00bb3358) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e00bb3358, mutex=0x558e00bb3330) at pthread_cond_wait.c:638 #3 0x7fedde22ab0b in cnd_wait (mtx=0x558e00bb3330, cond=0x558e00bb3358) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x558e00bb4650) at ../src/util/u_queue.c:275 #5 0x7fedde22a71b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fedf60f5482 in start_thread (arg=) at pthread_create.c:477 #7 0x7fedf7215583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fedbbfff700 (LWP 3893)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e00bb2c78) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e00bb2c28, cond=0x558e00bb2c50) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e00bb2c50, mutex=0x558e00bb2c28) at pthread_cond_wait.c:638 #3 0x7fedde22ab0b in cnd_wait (mtx=0x558e00bb2c28, cond=0x558e00bb2c50) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x558e00bb1cb0) at ../src/util/u_queue.c:275 #5 0x7fedde22a71b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fedf60f5482 in start_thread (arg=) at
[konsole] [Bug 413058] Konsole aborted when Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=413058 Matt Fagnani changed: What|Removed |Added Version|19.08.0 |19.12.1 -- You are receiving this mail because: You are watching all bug changes.
