[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 Nicolas Fella changed: What|Removed |Added Resolution|WORKSFORME |--- CC||nicolas.fe...@gmx.de Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 Nicolas Fella changed: What|Removed |Added CC||alexmatee...@yahoo.com --- Comment #12 from Nicolas Fella --- *** Bug 453931 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #11 from torokat...@gmail.com --- I should also add, that since a couple releases ago, Fedora, the distro I use, comes with dbus-broker instead of the "original" dbus-daemon. This may or may not matter. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #10 from torokat...@gmail.com --- I'm on Plasma 5.22.4 now. While this issue feels like it happens somewhat less often nowadays, I still get a couple weird behaviors related to (I think) the D-Bus connection: - Sometimes the icon of KTorrent doesn't appear in the System Tray applet when I open it - Sometimes the icon appears, but the Minimize and Quit options are missing from its context menu - Sometimes none of the options in the context menu of any application in the System Tray (let it be KTorrent, Discord, Discover, etc.) work, or do anything, when clicked - Sometimes Firefox stops being able to show native desktop notifications, and switches to its own popup windows instead - Plasma still just crashes from time to time, for no apparent reason whatsoever, during normal use (actually I don't know if this has anything to do with D-Bus, but it's possible) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from David Edmundson --- This code subtly changed in 5.22, lets reopen if we see it then -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #8 from torokat...@gmail.com --- Created attachment 138870 --> https://bugs.kde.org/attachment.cgi?id=138870=edit New crash information added by DrKonqi plasmashell (5.21.5) using Qt 5.15.2 - What I was doing when the application crashed: I clicked on the "Konsole" launcher icon on the panel. (And the tooltip for it was open, not sure if this matters). -- Backtrace (Reduced): #7 0x7f0174da0010 in _dbus_warn_return_if_fail () at /lib64/libdbus-1.so.3 #8 0x7f01768d2d79 in q_dbus_pending_call_block (pending=) at /usr/src/debug/qt5-qtbase-5.15.2-15.fc34.x86_64/src/dbus/qdbus_symbols_p.h:450 #9 QDBusConnectionPrivate::getNameOwnerNoCache(QString const&) (this=this@entry=0x7f0154003a00, serviceName=...) at qdbusintegrator.cpp:2563 #10 0x7f01768d4d6b in QDBusConnectionPrivate::addSignalHook(QString const&, QDBusConnectionPrivate::SignalHook const&) (this=0x7f0154003a00, key=, hook=...) at qdbusintegrator.cpp:2298 #11 0x7f01768d63d5 in QtPrivate::FunctorCall, QtPrivate::List, bool, bool (QDBusConnectionPrivate::*)(QString const&, QDBusConnectionPrivate::SignalHook const&)>::call(bool (QDBusConnectionPrivate::*)(QString const&, QDBusConnectionPrivate::SignalHook const&), QDBusConnectionPrivate*, void**) (arg=, o=, f=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:152 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #7 from torokat...@gmail.com --- And immediately after, when I tried to restart Firefox, just by clicked on its launcher icon on the panel. And right after that, I triggered https://bugs.kde.org/show_bug.cgi?id=436866 when I tried to unmute the sound (for some reason, when I restart plasmashell, it always mutes the system). I really, _really_ want to use KDE on Wayland, but honestly, it's still quite hostile to me... :/ -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #6 from torokat...@gmail.com --- Now I got this crash upon receiving a message in an IM webapp, because Firefox tried to show a notification about it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #5 from torokat...@gmail.com --- I'm also getting D-Bus-related plasmashell crashes when simply clicking on an application launcher icon. This is the interesting part of plasmashell's console output while crashing when launching VLC (so it also contains some vlc output): VLC media player 3.0.13 Vetinari (revision 3.0.12.1-158-g6977abc430) kf.kio.gui: Failed to register new cgroup: "app-vlc-1520a4d6277f4b9e9b0e870b0add08ee.scope" "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" [5565cc2b19d0] main interface error: no suitable interface module [5565cc19bc80] main libvlc error: interface "svpcontrol,none" initialization failed [5565cc19bc80] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [5565cc23d310] main playlist: playlist is empty kdeinit5: Shutting down running client. klauncher: Exiting on signal 15 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: Shutting down running client. klauncher: Exiting on signal 15 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kf.kio.core: couldn't create slave: "Cannot talk to klauncher: Not connected to D-Bus server" dbus[106622]: arguments to dbus_pending_call_block() were incorrect, assertion "pending != NULL" failed in file ../../dbus/dbus-pending-call.c line 765. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace KCrash: Attempting to start /usr/bin/plasmashell KCrash: Application 'plasmashell' crashing... kf.plasma.quick: Applet preload policy set to 1 qt.gui.icc: fromIccProfile: failed minimal tag size sanity -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #4 from David Edmundson --- *** Bug 436640 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 --- Comment #3 from torokat...@gmail.com --- Also cross-referencing: https://bugs.kde.org/show_bug.cgi?id=425607 and: https://bugreports.qt.io/browse/QTBUG-44836?jql=description%20~%20%22getNameOwnerNoCache*%22 In the hope that these might help... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 torokat...@gmail.com changed: What|Removed |Added CC||torokat...@gmail.com --- Comment #2 from torokat...@gmail.com --- Created attachment 138169 --> https://bugs.kde.org/attachment.cgi?id=138169=edit stack trace of a plasmashell crash I got a few crashes with stack traces almost identical to this one. But for me, the plasmashell program crashed, not systemmonitor. Also, my system was nowhere near a low-memory thrashing situation. See the attachment for the stack traces. I trimmed out a whole lot of threads that were just waiting for a futex, or in a poll syscall, and looked uninteresting. Seeing that it affects multiple components, could this be a Qt bug? Operating System: Fedora 34 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.17-300.fc34.x86_64 OS Type: 64-bit Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435999] Crash due to incorrect dbus call
https://bugs.kde.org/show_bug.cgi?id=435999 Nate Graham changed: What|Removed |Added Summary|Crash with backtrace|Crash due to incorrect dbus ||call CC||n...@kde.org --- Comment #1 from Nate Graham --- #9 0x7fd03e9942d0 in _dbus_warn_check_failed (format=0x7fd03e9a1c50 "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-internals.c:281 #10 0x7fd03fa81f69 in q_dbus_pending_call_block (pending=) at qdbus_symbols_p.h:450 -- You are receiving this mail because: You are watching all bug changes.
