[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 macr...@gmail.com changed: What|Removed |Added CC||macr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #3 from macr...@gmail.com --- Created attachment 157923 --> https://bugs.kde.org/attachment.cgi?id=157923&action=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.8 I find that I can very reliably induce this crash by simply leaving my system unattended for long enough to cause the screens to turn off. I did recently decide to temporarily disable system locking, so that may have something to do with it, but I cannot be entirely sure that this is related as I have noticed problems whether or not I have my screen locked, provided that I have had my screens turn off. Furthermore, if I do not restart my system and allow the crash to occur once more it results in all open programs being closed and I am forced to kill and relaunch plasmashell to get my desktop functional once more. Another odd thing I have noticed is that I no longer have any notification that I have experienced a crash and the KDE Crash Handler no longer registers that a crash has occurred after the first crash has taken place. -- Backtrace (Reduced): #4 std::default_delete::operator() (__ptr=0x110, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff9a93a3d8) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff9a93a3d8) at /usr/include/c++/12/bits/vector.tcc:181 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468404] New: Akonadi Server Crashes When Screen Goes Inactive
https://bugs.kde.org/show_bug.cgi?id=468404 Bug ID: 468404 Summary: Akonadi Server Crashes When Screen Goes Inactive Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: macr...@gmail.com Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.9-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Every time my screens go into sleep mode Akonadi Server crashes. All I have to do is let my system sit for a while and when I come back Akonadi server will have crashed and taken all running programs with it. I suspect that one of my monitors may have a bad capacitor which causes the screen to turn off when entering low power mode, causing the system to detect the screen as being disconnected, which, in turn, causes the display configuration to change and, consequently, reactivates the monitor, turning it back on. It is only possible to submit a bug report after the first crash, as it appears as though not every service properly reloads after the Akonadi Server crash. I previously attempted to file a bug report but it appears as though DrKonqi appended it to an unrelated bug so I am attempting to do so again, this time referencing a bug that appears to be similar to what I am experiencing. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::default_delete::operator() (__ptr=0x110, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7ffe1596a6d8) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7ffe1596a6d8) at /usr/include/c++/12/bits/vector.tcc:181 #9 std::vector >, std::allocator > > >::erase (__position=..., this=0x7ffe1596a6d8) at /usr/include/c++/12/bits/stl_vector.h:1530 #10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=0x7ffe1596a650) at /usr/src/debug/kf5-akonadi-server-22.12.3-1.fc37.x86_64/src/server/akonadi.cpp:234 #11 0x7f14044c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f140449d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f14044a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7f14044eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7f140265fc7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7f14026b6118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7f140265cf00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7f14044ee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7f140449bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f14044a4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #21 0x555dcc8a4058 in AkApplicationBase::exec (this=0x7ffe1596a620) at /usr/src/debug/kf5-akonadi-server-22.12.3-1.fc37.x86_64/src/shared/akapplication.cpp:107 #22 main (argc=, argv=) at /usr/src/debug/kf5-akonadi-server-22.12.3-1.fc37.x86_64/src/server/main.cpp:65 [Inferior 1 (process 10666) detached] The reporter indicates this bug may be a duplicate of or related to bug 467883. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 450217] (SEGV) Crash in Akonadi::Server::AkonadiServer::connectionDisconnected
https://bugs.kde.org/show_bug.cgi?id=450217 macr...@gmail.com changed: What|Removed |Added CC||macr...@gmail.com --- Comment #22 from macr...@gmail.com --- *** Bug 468404 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468404] Akonadi Server Crashes When Screen Goes Inactive
https://bugs.kde.org/show_bug.cgi?id=468404 macr...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from macr...@gmail.com --- It appears as though this is a duplicate of bug 450217 https://bugs.kde.org/show_bug.cgi?id=450217 *** This bug has been marked as a duplicate of bug 450217 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457742] Plasmashell crashes when unlocking
https://bugs.kde.org/show_bug.cgi?id=457742 --- Comment #2 from macr...@gmail.com --- (In reply to Nate Graham from comment #1) > FWIW the "unlock button doesn't work" issue is very likely Bug 456210. Much obliged, I will look into that thread and see if I can contribute anything of value. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458204] New: Plasmashell occasionally crashes upon unlocking if my screens go to sleep before I return
https://bugs.kde.org/show_bug.cgi?id=458204 Bug ID: 458204 Summary: Plasmashell occasionally crashes upon unlocking if my screens go to sleep before I return Product: plasmashell Version: 5.25.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: macr...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.18.18-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: After a previous update I had been having plasmashell crash every time I unlocked my system if my screens turned off. This seems to have been largely resolved, but I do still occasionally get plasmashell crashes upon unlocking my system. A previous bug report I submitted, https://bugs.kde.org/show_bug.cgi?id=457742, suggests that some of the crashing I was experiencing may have been related to having one of my screens rotated, but I figured I would submit another report as the contents of the crash handler report appeared to differ in some ways from the one I had submitted previously. It may be of interest that, while I still do see the unlock button at times, it now works correctly when clicked ever time and I no longer have to power off and on one of my monitors to unlock my system. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #5 0x7f36d70bfcb3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #6 0x7f36d706f9c6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7f36d70597f4 in __GI_abort () at abort.c:79 #8 0x7f36d730ae40 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*) (file=file@entry=0x558fdcef88f8 "/usr/include/c++/12/bits/stl_algo.h", line=line@entry=3623, function=function@entry=0x558fdcef88a0 "constexpr const _Tp& std::clamp(const _Tp&, const _Tp&, const _Tp&) [with _Tp = int]", condition=condition@entry=0x558fdcef8693 "!(__hi < __lo)") at ../../../../../libstdc++-v3/src/c++11/debug.cc:60 #9 0x558fdceb440f in std::clamp(int const&, int const&, int const&) (__val=, __lo=, __hi=) at /usr/include/c++/12/bits/stl_algo.h:3621 #10 std::clamp(int const&, int const&, int const&) (__hi=: , __lo=: , __val=@0x558fe0ae0c74: 976) at /usr/include/c++/12/bits/stl_algo.h:3621 #11 PanelView::resizePanel() (this=this@entry=0x558fe0ae0c30) at /usr/src/debug/plasma-workspace-5.25.4-1.fc36.x86_64/shell/panelview.cpp:629 #12 0x558fdceb9c8f in PanelView::restore() (this=0x558fe0ae0c30) at /usr/src/debug/plasma-workspace-5.25.4-1.fc36.x86_64/shell/panelview.cpp:692 #13 0x7f36d77428c6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd1f5ea0e0, r=, this=0x558fe2c262e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x7f36c0080080, signal_index=3, argv=0x7ffd1f5ea0e0) at kernel/qobject.cpp:3886 #15 0x7f36d773d8a7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7f36c0080080, m=m@entry=0x7f36d8003ae0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd1f5ea0e0) at kernel/qobject.cpp:3946 #16 0x7f36d7eef776 in QScreen::geometryChanged(QRect const&) (this=this@entry=0x7f36c0080080, _t1=...) at .moc/moc_qscreen.cpp:372 #17 0x7f36d7b75f7c in QScreenPrivate::emitGeometryChangeSignals(bool, bool) (this=0x558fe9b4ffb0, geometryChanged=geometryChanged@entry=true, availableGeometryChanged=availableGeometryChanged@entry=true) at kernel/qscreen.cpp:98 #18 0x7f36d7b4ffce in QGuiApplicationPrivate::processScreenGeometryChange(QWindowSystemInterfacePrivate::ScreenGeometryEvent*) (e=) at ../../include/QtGui/../../src/gui/kernel/qscreen.h:69 #19 QGuiApplicationPrivate::processScreenGeometryChange(QWindowSystemInterfacePrivate::ScreenGeometryEvent*) (e=) at kernel/qguiapplication.cpp:3148 #20 0x7f36d7b2dfbc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #21 0x7f36c55eee4e in xcbSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at qxcbeventdispatcher.cpp:105 #22 0x7f36d5a95faf in g_main_dispatch (context=0x7f36c0005010) at ../glib/gmain.c:3417 #23 g_main_context_dispatch (context=0x7f36c0005010) at ../glib/gmain.c:4135 #24 0x7f36d5aeb2c8 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f36c0005010, block=block@entry=1, dispatch=dispatch
[plasmashell] [Bug 457742] New: Plasmashell crashes when unlocking
https://bugs.kde.org/show_bug.cgi?id=457742 Bug ID: 457742 Summary: Plasmashell crashes when unlocking Product: plasmashell Version: 5.25.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: macr...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.16-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Currently I have 4 monitors connected to my system, 3 at my desk and one located a distance away. They are set up such that when my right-most monitor is turned on, the three on my desk are enabled while the remote monitor is disabled and vice-versa. I am currently using X11 rather than Wayland despite using Fedora36 as any attempts to use wayland result in a much worse crash. To reproduce the crash all I need to do is lock the computer and leave it for long enough for the screens to go into sleep mode. Upon attempting to log in I will rarely be able to log in successfully, but more often than not I am presented with a button that says " unlock" but does nothing when pressed. To get logged in I then need to manually turn off the right-most screen and then turn it on again, which allows me to attempt to log in again on a different monitor, however this time it will let me in. Whether or not I log in on the first time I will see a notification from drkonqi that plasmashell has crashed, but the vast majority of the time drkonqi closes itself before I can save any information and fails to save any reference of the crash. It appears as though drkonqi closing coincides with plasmashell relaunching, but with this most recent crash drkonqi did not close. If I attempt to use wayland the system becomes unstable and I must switch to a terminal session and forcefully close any running programs on the session that has frozen before rebooting the system. All of my monitors are from different manufactureres, with my desk screens being manufactured by Dell, acer, and samsug, in order, left to right, while my leftmost screen is rotated 90 degrees to the left. The screens also have different resolutions, from left to right being 1080, 1440, and 2160. I am currently using an AMD Radeon VII as a GPU and have the 3 desktop monitors connected via display port. I attempted to ensure that all relevant debug symbols were installed when generating the trace, but still received a warning that some were missing, but I would be happy to provide any other information if necessary. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f66a80e8bd3 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () at /usr/lib64/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so #5 0x7f66d6a258c6 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #6 0x7f66d683c155 in QFutureWatcherBase::event(QEvent*) () at /lib64/libQt5Core.so.5 #7 0x7f66d76b2d22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7f66d69f2228 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #9 0x7f66d69f5594 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #10 0x7f66d6a43467 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #11 0x7f66d4d7bfaf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #12 0x7f66d4dd12c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #13 0x7f66d4d79940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #14 0x7f66d6a42f5a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #15 0x7f66d69f0c7a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #16 0x7f66d69f8d42 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #17 0x5588a795b165 in main () [Inferior 1 (process 371019) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
