https://bugs.kde.org/show_bug.cgi?id=414553

--- Comment #3 from naroyce <nroycea+...@gmail.com> ---
I now have 223 entries in coredumpctl for this issue... just from today alone.
Interesting that uptime is also showing 12 days again.

For what it's worth, I'm also seeing:
*****
Dec 10 15:56:43 computerName kdeinit5[2972391]: This application failed to
start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.

                                          Available platform plugins are:
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc,
wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
...
Nov 28 11:25:45 computerName systemd-coredump[226677]: Process 226672
(kglobalaccel5) of user 1000 dumped core.

                                                 Stack trace of thread 226672:
                                                 #0  0x00007de1f9de3f25 raise
(libc.so.6)
                                                 #1  0x00007de1f9dcd897 abort
(libc.so.6)
                                                 #2  0x00007de1fa1e28f4
_ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
                                                 #3  0x00007de1fa7804e5
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5)
                                                 #4  0x00007de1fa780d81
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5)
                                                 #5  0x00007de1fa3f24e5
_ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5)
                                                 #6  0x00007de1fa782b30
_ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5)
                                                 #7  0x00007de1fa783b48
_ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5)
                                                 #8  0x00005b99122c108f n/a
(kglobalaccel5)
                                                 #9  0x00007de1f9dcf153
__libc_start_main (libc.so.6)
                                                 #10 0x00005b99122c13fe n/a
(kglobalaccel5)
-- Subject: Process 226672 (kglobalaccel5) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 226672 (kglobalaccel5) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Nov 28 11:25:38 computerName kdeinit5[1250]: The X11 connection broke: I/O
error (code 1)
Nov 28 11:25:38 computerName kdeinit5[1250]: QDBusAbstractAdaptor: Cannot relay
signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported:
KDEDModule*
...
Nov 28 11:25:38 computerName sddm[960]: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{426bda34-0b77-4c6d-a6bc-84fd07730e26} -background none -noreset
-displayfd 18 -seat seat0 vt1
*****

I'm currently looking to see if I can re-establish X11 (even though I'd think
it was running considering I'm typing this on the system).

I've no idea if this any way relates to when I turn on/off my receiver which I
have HDMI going to, as well as DVI going to my monitor (don't ask, screwy
monitor doesn't play nice with HDMI).

I also noticed a kernel trace log containing "i915" nearby.
I'll build a newer kernel (5.3.7->5.4.1 I think), reboot, keep an eye out for
that error and report it if needed.

In any case, exceptions are being thrown and not caught and nicely notifying
the user.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to