This forum has been archived. All content is frozen. Please use KDE Discuss instead.

kdeinit5 fails constantly

Tags: None
(comma "," separated)
sphinks
Registered Member
Posts
2
Karma
0

kdeinit5 fails constantly

Tue Aug 27, 2019 12:55 pm
I'm using Fedora 29 + KDE 5.14.5 + KDE Framework 5.59.0 + QT 5.11.3. For last couple days I'm getting lot of kdeinit5 crashes. I have no idea what is causing that crashes, there is no specific action that leads to fail. In logs I get such info:

Code: Select all
localhost.localdomain plasmashell[2011]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_372(0x557f6d64dc00, parent=0x557f688f>
aug 27 15:43:35 localhost.localdomain plasmashell[2011]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:>
aug 27 15:43:35 localhost.localdomain systemd-coredump[5172]: Process 3301 (file.so) of user 1000 dumped core.
                                                                 
                                                                 Stack trace of thread 3301:
                                                                 #0  0x00007f8e509828b5 _ZN6QMutex4lockEv (libQt5Core.so.5)
                                                                 #1  0x00007f8e50b76186 _ZN10QTextCodec14codecForLocaleEv (libQt5Core.so.5)
                                                                 #2  0x00007f8e50a00569 _ZN7QString20fromLocal8Bit_helperEPKci (libQt5Core.so.5)
                                                                 #3  0x00007f8e50ad67b8 _ZN14QStandardPaths16writableLocationENS_16StandardLocationE (libQt5Co>
                                                                 #4  0x00007f8e51c35881 n/a (libKF5Crash.so.5)
                                                                 #5  0x00007f8e51c36362 n/a (libKF5Crash.so.5)
                                                                 #6  0x00007f8e51c36815 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5)
                                                                 #7  0x00007f8e50406600 .annobin_sigaction.c (libc.so.6)
aug 27 15:43:35 localhost.localdomain systemd-coredump[5173]: Process 3991 (file.so) of user 1000 dumped core.
                                                                 
                                                                 Stack trace of thread 3991:
                                                                 #0  0x00007f8e509828b5 _ZN6QMutex4lockEv (libQt5Core.so.5)
                                                                 #1  0x00007f8e50b76186 _ZN10QTextCodec14codecForLocaleEv (libQt5Core.so.5)
                                                                 #2  0x00007f8e50a00569 _ZN7QString20fromLocal8Bit_helperEPKci (libQt5Core.so.5)
                                                                 #3  0x00007f8e50ad67b8 _ZN14QStandardPaths16writableLocationENS_16StandardLocationE (libQt5Co>
                                                                 #4  0x00007f8e51c35881 n/a (libKF5Crash.so.5)
                                                                 #5  0x00007f8e51c36362 n/a (libKF5Crash.so.5)
                                                                 #6  0x00007f8e51c36815 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5)
                                                                 #7  0x00007f8e50406600 .annobin_sigaction.c (libc.so.6)
aug 27 15:43:35 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cor>
aug 27 15:43:35 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cor>
aug 27 15:43:36 localhost.localdomain kwin_x11[1996]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 42177, resource id: 123731979, major cod>
aug 27 15:43:37 localhost.localdomain abrt-server[5210]: Deleting problem directory ccpp-2019-08-27-15:43:35.946209-3301 (dup of ccpp-2019-08-26-17:08:51.2832>
aug 27 15:43:37 localhost.localdomain abrt-server[5210]: Lock file '.lock' is locked by process 2388
aug 27 15:43:38 localhost.localdomain abrt-notification[5253]: Process 4388 (kdeinit5) crashed in QMutex::lock()()
aug 27 15:43:40 localhost.localdomain abrt-server[5211]: Deleting problem directory ccpp-2019-08-27-15:43:35.962232-3991 (dup of ccpp-2019-08-26-17:08:51.2832>
aug 27 15:43:40 localhost.localdomain abrt-notification[5298]: Process 4388 (kdeinit5) crashed in QMutex::lock()()


Can anybody point me to a problem that is causing all that crashes?
airdrik
Registered Member
Posts
1854
Karma
5
OS

Re: kdeinit5 fails constantly

Tue Aug 27, 2019 6:18 pm
sphinks wrote:I'm using Fedora 29 + KDE 5.14.5 + KDE Framework 5.59.0 + QT 5.11.3. For last couple days I'm getting lot of kdeinit5 crashes. I have no idea what is causing that crashes, there is no specific action that leads to fail. In logs I get such info:

Code: Select all
...
aug 27 15:43:37 localhost.localdomain abrt-server[5210]: Lock file '.lock' is locked by process 2388
...


Can anybody point me to a problem that is causing all that crashes?


Looks like a process with id 2388 (possibly another instance of kdeinit5?) has an open lock which the new process is trying to acquire. You'll probably need to terminate that other process before trying to run the new process.


airdrik, proud to be a member of KDE forums since 2008-Dec.
sphinks
Registered Member
Posts
2
Karma
0

Re: kdeinit5 fails constantly

Wed Aug 28, 2019 9:44 am
I have no idea how do I start new process, moreover it does not fixed even after reboot.
airdrik
Registered Member
Posts
1854
Karma
5
OS

Re: kdeinit5 fails constantly

Fri Aug 30, 2019 7:01 pm
Starting a new process is just running the command. What are you running that's crashing and giving these errors (or do they just happen from something in the background)?

In the crash output, does it consistently complain about locking as in that line that I noted in my last post? If so is the process ID always the same, especially after reboots?
An option for attempting to resolve that problem would be to kill the process with that id (though you should be cautious about doing so as killing processes you aren't familiar with could lead to trouble, including ending your session). To do that, pull up the process monitor using Ctrl+Exc, search for the process ID, right-click on it and select End Process. Assuming that the trouble process is another "kdeinit5" process, killing it should be fine.


airdrik, proud to be a member of KDE forums since 2008-Dec.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]