[opensuse-kde] Tumbleweed : drkonqui crash each time kde plasma5 is started SEGV
Everytime I start my computer, I've an event for drkonqui in coredump I'm using autologin qt-kt:~ # coredumpctl gdb 1024 PID: 1024 (drkonqi) UID: 1502 (bruno) GID: 1500 (ioda) Signal: 6 (ABRT) Timestamp: Sun 2016-07-17 11:01:25 CEST (5h 46min ago) Command Line: /usr/lib64/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 3054 --startupid 0 -- restarted Executable: /usr/lib64/libexec/drkonqi Control Group: /user.slice/user-1502.slice/session-1.scope Unit: session-1.scope Slice: user-1502.slice Session: 1 Owner UID: 1502 (bruno) Boot ID: a24e755e12b84261a49ff60422e4d104 Machine ID: 5796a69412fbda1c055a261856a26e81 Hostname: qt-kt.labaroche.ioda.net Coredump: /var/lib/systemd/coredump/core.drkonqi. 1502.a24e755e12b84261a49ff60422e4d104.1024.1468746085000000.xz Message: Process 1024 (drkonqi) of user 1502 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://bugs.opensuse.org/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib64/libexec/drkonqi...Reading symbols from /usr/ lib/debug/usr/lib64/libexec/drkonqi.debug...done. done. [New LWP 1024] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib64/libexec/drkonqi -platform xcb -display :0 -- appname kdeinit5 --kdein'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f31b1195975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007f31b1195975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 #1 0x00007f31b1196d8a in __GI_abort () at abort.c:78 #2 0x00007f31b1925331 in QMessageLogger::fatal(char const*, ...) const (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1648 #3 0x00007f31b1925331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffcd36cf170, msg=msg@entry=0x7f31a6d14a10 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:790 #4 0x00007f31a6c8a007 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (this= 0x22486b0, nativeInterface=0x22485b0, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:585 #5 0x00007f31a6c8cede in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (this=<optimized out>, parameters=..., argc=@0x7ffcd36cf7bc: 13, argv=0x7ffcd36cfa28) at qxcbintegration.cpp:179 #6 0x00007f31a6f8e4fd in QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (this=<optimized out>, system=..., parameters=..., argc=@0x7ffcd36cf7bc: 13, argv=0x7ffcd36cfa28) at qxcbmain.cpp:50 #7 0x00007f31b2057d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (argv=0x7ffcd36cfa28, argc=@0x7ffcd36cf7bc: 13, parameters=..., key=..., loader=<optimized out>) at kernel/qplatformintegrationfactory.cpp:56 #8 0x00007f31b2057d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (platform=..., paramList=..., argc=@0x7ffcd36cf7bc: 13, argv=argv@entry=0x7ffcd36cfa28, platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:73 #9 0x00007f31b2066365 in QGuiApplicationPrivate::createPlatformIntegration() (argv=<optimized out>, argc=@0x7ffcd36cf7bc: 13, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1058 #10 0x00007f31b2066365 in QGuiApplicationPrivate::createPlatformIntegration() (this=0x222e620) at kernel/qguiapplication.cpp:1227 #11 0x00007f31b206715d in QGuiApplicationPrivate::createEventDispatcher() (this=<optimized out>) at kernel/qguiapplication.cpp:1244 #12 0x00007f31b1b1bd5f in QCoreApplicationPrivate::init() (this=this@entry=0x222e620) at kernel/qcoreapplication.cpp:814 #13 0x00007f31b2068adf in QGuiApplicationPrivate::init() (this=this@entry=0x222e620) at kernel/qguiapplication.cpp:1267 #14 0x00007f31b285e329 in QApplicationPrivate::init() (this=0x222e620) at kernel/qapplication.cpp:578 #15 0x000000000041db89 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.7.0/drkonqi/ main.cpp:60 (gdb) This kind of crash exist since months, and I would like to improve my start speed, so limiting SEGV on boot and coredump collection would be a first step. I've reported that some months ago, https://bugs.kde.org/show_bug.cgi?id=363676 Am I alone to experiment this kind of crash ? If not could you add your backtrace to the bug, so its status will move to confirmed. To check just run coredumpctl --no-pager to see the list of those your system could have cought. Thanks for your attention. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 17. Juli 2016, 16:54:25 schrieb Bruno Friedmann:
Am I alone to experiment this kind of crash ?
Apparently yes. At least it's not a general issue. Your problem seems to be this though:
#3 0x00007f31b1925331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffcd36cf170, msg=msg@entry=0x7f31a6d14a10 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:790
I.e. "Could not connect to display". The only thing that might cause this that I can think of right now is that the hostname changes during login. Try to disable "Use DHCP to change hostname" (or whatever it's called) in YaST, if you are using a NetworkManager user connection it is only connected (and may change the hostname) when you actually login. Other than that: you don't explicitly set the $DISPLAY environment variable anywhere, do you? A user on the openSUSE mailinglist recently had the problem that he couldn't login and an "export DISPLAY=:3.0" in ~/.bashrc was the cause. http://lists.opensuse.org/opensuse/2016-07/msg00296.html Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On lundi, 18 juillet 2016 11.52:14 h CEST Wolfgang Bauer wrote:
Am Sonntag, 17. Juli 2016, 16:54:25 schrieb Bruno Friedmann:
Am I alone to experiment this kind of crash ?
Apparently yes. At least it's not a general issue.
Your problem seems to be this though:
#3 0x00007f31b1925331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffcd36cf170, msg=msg@entry=0x7f31a6d14a10 "QXcbConnection: Could not connect to display %s")
at global/qlogging.cpp:790
I.e. "Could not connect to display".
The only thing that might cause this that I can think of right now is that the hostname changes during login. Try to disable "Use DHCP to change hostname" (or whatever it's called) in YaST, if you are using a NetworkManager user connection it is only connected (and may change the hostname) when you actually login. Ok I'm using NetworkManager but system wide configuration for wired connection.
In Yast there's no change my hostname checkbox activated, and plus my workstation always get the same ip and name (dhcp reservation)
Other than that: you don't explicitly set the $DISPLAY environment variable anywhere, do you? A user on the openSUSE mailinglist recently had the problem that he couldn't login and an "export DISPLAY=:3.0" in ~/.bashrc was the cause. http://lists.opensuse.org/opensuse/2016-07/msg00296.html
I've checked again all my .XXX env files, and none of them export DISPLAY. and Display is setup as expected XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 DISPLAY=:0 I didn't find anything that can explain the crash in journald there's just too much error (every time the screen suspend and or wake up) Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kuiserver[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2736, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kuiserver[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2737, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kwalletd5[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2736, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kwalletd5[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2737, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kpasswdserver[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2288, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kpasswdserver[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2289, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kglobalaccel[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 6502, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.kglobalaccel[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 6503, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.KScreen[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 3447, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:00 qt-kt.labaroche.ioda.net org.kde.KScreen[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 3448, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:01 qt-kt.labaroche.ioda.net org.kde.kglobalaccel[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 6510, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:01 qt-kt.labaroche.ioda.net org.kde.kpasswdserver[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2297, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:01 qt-kt.labaroche.ioda.net org.kde.kwalletd5[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2744, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:01 qt-kt.labaroche.ioda.net org.kde.kuiserver[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 2744, resource id: 0, major code: 140 (Unknown), minor code: 20 Jul 17 18:58:01 qt-kt.labaroche.ioda.net org.kde.KScreen[2213]: QXcbConnection: XCB error: 148 (Unknown), sequence: 3455, resource id: 0, major code: 140 (Unknown), minor code: 20 Thanks a lot Wolfgang for your inputs, I know now that I'm affected by a non common problem. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Well, I have no idea currently what could be the reason then, sorry. For further clarification: is the Plasma session useable afterwards? Can you start new applications? Just a wild guess: Maybe it's something that gets started by the session management (that crashes). Try to set "Start with a clean session" in "Configure Desktop"->"Startup and Shutdown"->"Session Management", and see if it "cures" the problem. But maybe store away ~/.config/ksmserverrc first, so we can find out what it was if that's really the problem... PS: In case it wasn't obvious yet, your other mail about kdeinit crashing has the same cause. And this drkonqi that's crashing is actually only started because of the kdeinit crash (which it captures), as can be seen from the command line from your coredumpctl output. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On mardi, 19 juillet 2016 00.02:55 h CEST Wolfgang Bauer wrote:
Well, I have no idea currently what could be the reason then, sorry.
For further clarification: is the Plasma session useable afterwards? Can you start new applications?
Just a wild guess: Maybe it's something that gets started by the session management (that crashes). Try to set "Start with a clean session" in "Configure Desktop"->"Startup and Shutdown"->"Session Management", and see if it "cures" the problem.
But maybe store away ~/.config/ksmserverrc first, so we can find out what it was if that's really the problem...
PS: In case it wasn't obvious yet, your other mail about kdeinit crashing has the same cause. And this drkonqi that's crashing is actually only started because of the kdeinit crash (which it captures), as can be seen from the command line from your coredumpctl output.
Kind Regards, Wolfgang
Starting with new session still give some segv on startup but this time
kactivitymanage
coredumpctl gdb 2177
PID: 2177 (kactivitymanage)
UID: 1502 (bruno)
GID: 1500 (ioda)
Signal: 11 (SEGV)
Timestamp: Sat 2016-07-23 16:24:39 CEST (17min ago)
Command Line: /usr/bin/kactivitymanagerd start-daemon
Executable: /usr/bin/kactivitymanagerd
Control Group: /user.slice/user-1502.slice/session-5.scope
Unit: session-5.scope
Slice: user-1502.slice
Session: 5
Owner UID: 1502 (bruno)
Boot ID: c9ae14047fcc4ad0919b8fee56afa3ac
Machine ID: 5796a69412fbda1c055a261856a26e81
Hostname: qt-kt.labaroche.ioda.net
Coredump: /var/lib/systemd/coredump/core.kactivitymanage.
1502.c9ae14047fcc4ad0919b8fee56afa3ac.2177.1469283879000000.xz
Message: Process 2177 (kactivitymanage) of user 1502 dumped core.
GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://bugs.opensuse.org/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kactivitymanagerd...Reading symbols from /usr/
lib/debug/usr/bin/kactivitymanagerd.debug...done.
done.
warning: core file may not match specified executable file.
[New LWP 2177]
[New LWP 2187]
[New LWP 10380]
[New LWP 2185]
[New LWP 2186]
[New LWP 2188]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/kactivitymanagerd start-daemon'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fafd93ab3d1 in QSqlDatabase::close (this=this@entry=0x2140b38) at
kernel/qsqldatabase.cpp:871
871 kernel/qsqldatabase.cpp: No such file or directory.
[Current thread is 1 (Thread 0x7faff62078c0 (LWP 2177))]
(gdb) bt
#0 0x00007fafd93ab3d1 in QSqlDatabase::close() (this=this@entry=0x2140b38) at
kernel/qsqldatabase.cpp:871
#1 0x00007fafd93ada49 in QSqlDatabase::~QSqlDatabase() (this=0x2140b38,
__in_chrg=<optimized out>) at kernel/qsqldatabase.cpp:799
#2 0x00007fafd93b073d in QHash
Am Samstag, 23. Juli 2016, 16:44:41 schrieb Bruno Friedmann:
Starting with new session still give some segv on startup but this time kactivitymanage
coredumpctl gdb 2177 PID: 2177 (kactivitymanage) ... #0 0x00007fafd93ab3d1 in QSqlDatabase::close() (this=this@entry=0x2140b38) at kernel/qsqldatabase.cpp:871 #1 0x00007fafd93ada49 in QSqlDatabase::~QSqlDatabase() (this=0x2140b38, __in_chrg=<optimized out>) at kernel/qsqldatabase.cpp:799 ... Any throughs ?
That's not a crash on startup, but rather a crash on exit. It is a known problem (in Qt5), but it is completely harmless. See https://bugs.kde.org/show_bug.cgi?id=348194. And your original problem is gone now? Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On samedi, 23 juillet 2016 17.43:09 h CEST Wolfgang Bauer wrote:
Am Samstag, 23. Juli 2016, 16:44:41 schrieb Bruno Friedmann:
Starting with new session still give some segv on startup but this time kactivitymanage
coredumpctl gdb 2177
PID: 2177 (kactivitymanage)
... #0 0x00007fafd93ab3d1 in QSqlDatabase::close() (this=this@entry=0x2140b38) at kernel/qsqldatabase.cpp:871 #1 0x00007fafd93ada49 in QSqlDatabase::~QSqlDatabase() (this=0x2140b38, __in_chrg=<optimized out>) at kernel/qsqldatabase.cpp:799 ... Any throughs ?
That's not a crash on startup, but rather a crash on exit. It is a known problem (in Qt5), but it is completely harmless. See https://bugs.kde.org/show_bug.cgi?id=348194.
And your original problem is gone now?
Kind Regards, Wolfgang So after a bit of testing and stop and start computer: If the restore session is off then there no drkonqui nor kdeinit5 segv But this is not what I need (I'm too lazy to reopen konsole and my 10 tabs each time).
Stangely the kactivimanage crash occur on login here, not logout. But again this only appear when session restore is off ;-) Now I've deeply inspected when I start and shutdown the computer and kdeinit5 crash appear in fact on shutdown. Mon 2016-07-25 18:37:00 CEST 12578 1502 1500 6 * /usr/lib64/libexec/ drkonqi Mon 2016-07-25 18:37:00 CEST 12580 1502 1500 6 * /usr/bin/kdeinit5 504284 Jul 25 18:37 core.klauncher. 1502.4e21b207345947ba81fc0da48a860731.12580.1469464619000000.xz coredumpctl gdb 12580 PID: 12580 (klauncher) UID: 1502 (bruno) GID: 1500 (ioda) Signal: 6 (ABRT) Timestamp: Mon 2016-07-25 18:36:59 CEST (2h 19min ago) Command Line: klauncher [kdeinit5] --fd= Executable: /usr/bin/kdeinit5 Control Group: /user.slice/user-1502.slice/session-1.scope Unit: session-1.scope Slice: user-1502.slice Session: 1 Owner UID: 1502 (bruno) Boot ID: 4e21b207345947ba81fc0da48a860731 Machine ID: 5796a69412fbda1c055a261856a26e81 Hostname: qt-kt.labaroche.ioda.net Coredump: /var/lib/systemd/coredump/core.klauncher. 1502.4e21b207345947ba81fc0da48a860731.12580.1469464619000000.xz Message: Process 12580 (klauncher) of user 1502 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://bugs.opensuse.org/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/kdeinit5...Reading symbols from /usr/lib/debug/ usr/bin/kdeinit5.debug...done. done. warning: core file may not match specified executable file. [New LWP 12580] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `klauncher [kdeinit'. Program terminated with signal SIGABRT, Aborted. #0 0x00007ff4afa1b975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ff4afa1b975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 #1 0x00007ff4afa1cd8a in __GI_abort () at abort.c:78 #2 0x00007ff4afe23331 in QMessageLogger::fatal(char const*, ...) const (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1648 #3 0x00007ff4afe23331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffc357ff430, msg=msg@entry=0x7ff49fa0ea10 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:790 #4 0x00007ff49f984007 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (this= 0x2113ef0, nativeInterface=0x2113df0, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:585 #5 0x00007ff49f986ede in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (this=<optimized out>, parameters=..., argc=@0x7ffc357ffa3c: 2, argv=0x20f3760) at qxcbintegration.cpp:179 #6 0x00007ff49fc434fd in QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (this=<optimized out>, system=..., parameters=..., argc=@0x7ffc357ffa3c: 2, argv=0x20f3760) at qxcbmain.cpp:50 #7 0x00007ff4b0555d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (argv=0x20f3760, argc=@0x7ffc357ffa3c: 2, parameters=..., key=..., loader=<optimized out>) at kernel/qplatformintegrationfactory.cpp:56 #8 0x00007ff4b0555d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (platform=..., paramList=..., argc=@0x7ffc357ffa3c: 2, argv=argv@entry=0x20f3760, platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:73 #9 0x00007ff4b0564365 in QGuiApplicationPrivate::createPlatformIntegration() (argv=<optimized out>, argc=@0x7ffc357ffa3c: 2, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1058 #10 0x00007ff4b0564365 in QGuiApplicationPrivate::createPlatformIntegration() (this=0x20ff390) at kernel/qguiapplication.cpp:1227 #11 0x00007ff4b056515d in QGuiApplicationPrivate::createEventDispatcher() (this=<optimized out>) at kernel/qguiapplication.cpp:1244 #12 0x00007ff4b0019d5f in QCoreApplicationPrivate::init() (this=this@entry=0x20ff390) at kernel/qcoreapplication.cpp:814 #13 0x00007ff4b0566adf in QGuiApplicationPrivate::init() (this=0x20ff390) at kernel/qguiapplication.cpp:1267 #14 0x00007ff4b05678f4 in QGuiApplication::QGuiApplication(int&, char**, int) (this=0x7ffc357ffa70, argc=@0x7ffc357ffa3c: 2, argv=0x20f3760, flags=329217) at kernel/qguiapplication.cpp:573 #15 0x00007ff49fe54b7a in kdemain(int, char**) (argc=<optimized out>, argv=0x20f3760) at /usr/src/debug/kinit-5.24.0/src/klauncher/ klauncher_main.cpp:162 #16 0x000000000040886d in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) (argc=argc@entry=2, _name=_name@entry=0x40b247 "klauncher", args=<optimized out>, args@entry=0x7ffc357ffec0 "--fd=8", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b293 "0") at /usr/src/debug/kinit-5.24.0/src/kdeinit/kinit.cpp:759 #17 0x0000000000409687 in start_klauncher() () at /usr/src/debug/kinit-5.24.0/ src/kdeinit/kinit.cpp:1047 #18 0x0000000000405bb5 in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/kinit-5.24.0/src/kdeinit/kinit.cpp:1809 (gdb) #0 0x00007ff4afa1b975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 #1 0x00007ff4afa1cd8a in __GI_abort () at abort.c:78 #2 0x00007ff4afe23331 in QMessageLogger::fatal(char const*, ...) const (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1648 #3 0x00007ff4afe23331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffc357ff430, msg=msg@entry=0x7ff49fa0ea10 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:790 #4 0x00007ff49f984007 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (this=0x2113ef0, nativeInterface=0x2113df0, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:585 #5 0x00007ff49f986ede in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (this=<optimized out>, parameters=..., argc=@0x7ffc357ffa3c: 2, argv=0x20f3760) at qxcbintegration.cpp:179 #6 0x00007ff49fc434fd in QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (this=<optimized out>, system=..., parameters=..., argc=@0x7ffc357ffa3c: 2, argv=0x20f3760) at qxcbmain.cpp:50 #7 0x00007ff4b0555d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (argv=0x20f3760, argc=@0x7ffc357ffa3c: 2, parameters=..., key=..., loader=<optimized out>) at kernel/qplatformintegrationfactory.cpp:56 #8 0x00007ff4b0555d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (platform=..., paramList=..., argc=@0x7ffc357ffa3c: 2, argv=argv@entry=0x20f3760, platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:73 #9 0x00007ff4b0564365 in QGuiApplicationPrivate::createPlatformIntegration() (argv=<optimized out>, argc=@0x7ffc357ffa3c: 2, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1058 #10 0x00007ff4b0564365 in QGuiApplicationPrivate::createPlatformIntegration() (this=0x20ff390) at kernel/qguiapplication.cpp:1227 #11 0x00007ff4b056515d in QGuiApplicationPrivate::createEventDispatcher() (this=<optimized out>) at kernel/qguiapplication.cpp:1244 #12 0x00007ff4b0019d5f in QCoreApplicationPrivate::init() (this=this@entry=0x20ff390) at kernel/qcoreapplication.cpp:814 #13 0x00007ff4b0566adf in QGuiApplicationPrivate::init() (this=0x20ff390) at kernel/qguiapplication.cpp:1267 #14 0x00007ff4b05678f4 in QGuiApplication::QGuiApplication(int&, char**, int) (this=0x7ffc357ffa70, argc=@0x7ffc357ffa3c: 2, argv=0x20f3760, flags=329217) at kernel/qguiapplication.cpp:573 #15 0x00007ff49fe54b7a in kdemain(int, char**) (argc=<optimized out>, argv=0x20f3760) at /usr/src/debug/kinit-5.24.0/src/klauncher/ klauncher_main.cpp:162 #16 0x000000000040886d in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) (argc=argc@entry=2, _name=_name@entry=0x40b247 "klauncher", args=<optimized out>, args@entry=0x7ffc357ffec0 "--fd=8", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b293 "0") at /usr/src/debug/kinit-5.24.0/src/kdeinit/kinit.cpp:759 #17 0x0000000000409687 in start_klauncher() () at /usr/src/debug/kinit-5.24.0/ src/kdeinit/kinit.cpp:1047 #18 0x0000000000405bb5 in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/kinit-5.24.0/src/kdeinit/kinit.cpp:1809 Seems that for the moment I have to live with one or another segv :-)) Annoying to need to empty so regularly /var/lib/systemd/ Shall I report all that stuff upstream ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 25. Juli 2016, 21:01:15 schrieb Bruno Friedmann:
So after a bit of testing and stop and start computer: If the restore session is off then there no drkonqui nor kdeinit5 segv But this is not what I need (I'm too lazy to reopen konsole and my 10 tabs each time).
Ok, that seems to indicate that it is indeed something that's being restarted by session management. So, can you please try to rename ~/.config/ksmserverrc and enable session management? If that helps, please post the file, maybe something obvious is in there. In any case, you should be able to use session management again without disturbance.
Stangely the kactivimanage crash occur on login here, not logout. But again this only appear when session restore is off ;-)
I don't completely follow you here. How exactly are you infering that this occurs on login? How/where do you see the crash? If you run "coredumpctl", it may show you the crash at logout too. It's stored. The crash dump you posted is definitely a crash when kactivitiymanagerd quits. And you still didn't tell what actual problems you experience...
Now I've deeply inspected when I start and shutdown the computer and kdeinit5 crash appear in fact on shutdown.
If things are crashing, it may be worth to report them upstream, though you already did, didn't you? (I haven't really compared the backtraces right now) But at least you should mention that the crashes occur in fact on shutdown. OTOH, that's much less to worry about, except as you say that they are filling up your /var/lib/systemd/. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On lundi, 25 juillet 2016 22.19:54 h CEST Wolfgang Bauer wrote:
Am Montag, 25. Juli 2016, 21:01:15 schrieb Bruno Friedmann:
So after a bit of testing and stop and start computer: If the restore session is off then there no drkonqui nor kdeinit5 segv But this is not what I need (I'm too lazy to reopen konsole and my 10 tabs each time).
Ok, that seems to indicate that it is indeed something that's being restarted by session management.
So, can you please try to rename ~/.config/ksmserverrc and enable session management?
here's the file attached below
If that helps, please post the file, maybe something obvious is in there. In any case, you should be able to use session management again without disturbance.
Stangely the kactivimanage crash occur on login here, not logout. But again this only appear when session restore is off ;-)
I don't completely follow you here. How exactly are you infering that this occurs on login? How/where do you see the crash?
If you run "coredumpctl", it may show you the crash at logout too. It's stored. The crash dump you posted is definitely a crash when kactivitiymanagerd quits.
That's the part where we «disagree» :-) the timestamps of the crash are really when I login (autologin to be more precise)
And you still didn't tell what actual problems you experience... The problem is that 2 or more coredumpctl beside taking place slowdown the overall boot process. And there's no good reason to let segv program on a computer. The rest of the plasma5 session, seems to work correctly.
Now I've deeply inspected when I start and shutdown the computer and kdeinit5 crash appear in fact on shutdown.
If things are crashing, it may be worth to report them upstream, though you already did, didn't you? (I haven't really compared the backtraces right now) But at least you should mention that the crashes occur in fact on shutdown.
No I've not yet report it upstream, because I would like to make a as precise as possible report, against the right component.
OTOH, that's much less to worry about, except as you say that they are filling up your /var/lib/systemd/.
Kind Regards, Wolfgang
Well, I would prefer to not have the 2965 lines of report since 5 feb :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot
Am Dienstag, 26. Juli 2016, 09:02:03 schrieb Bruno Friedmann:
So, can you please try to rename ~/.config/ksmserverrc and enable session management?
here's the file attached below
Ok, so the automatically started applications are: program1=kwin_x11 program2=/ioda/home/bruno/.dropbox-dist/dropbox-lnx.x86_64-6.4.14/dropbox program3=pulseaudio program4=/usr/bin/konsole program5=/usr/bin/korgac program6=/usr/bin/kwalletmanager program7=/usr/bin/dolphin As the crash apparently doesn't appear when you disable session management, I strongly suspect one of those is crashing on login. Do those applications get started fine, i.e. are all of them running after login? If one is not, it's likely the culprit. One thing I find a bit strange here is that pulseaudio is in the list. There should be no need to start it via session management, and the restartCommand is empty anyway (that *may* even be what causes the crash I suppose...). Try to add "pulseaudio" to the list of excluded applications in "Configure Desktop"->"Startup & Shutdown"->Session Management, maybe it helps. (or, if you prefer, you can also try to disable pulseaudio completely in YaST) If not, to verify that the crash is indeed caused by the ksmserverrc content, try to remove/rename the file after you logout, before you login, and check whether the crash is gone or still there.
If you run "coredumpctl", it may show you the crash at logout too. It's stored. The crash dump you posted is definitely a crash when kactivitiymanagerd quits.
That's the part where we «disagree» :-) the timestamps of the crash are really when I login (autologin to be more precise)
You mean the kactivitymanagerd crash? But it is crashing on exit, have a look at the backtrace, the crash happens when the database is closed. Maybe it doesn't quit immediately on logout, but only later after a while... In any case, that crash with that backtrace you posted is a known problem (in Qt5), so no need to report it. A workaround has been added to kactivitymanagerd a while ago, but it turned out to not work (and has been removed again since).
Now I've deeply inspected when I start and shutdown the computer and kdeinit5 crash appear in fact on shutdown.
If things are crashing, it may be worth to report them upstream, though you already did, didn't you? (I haven't really compared the backtraces right now) But at least you should mention that the crashes occur in fact on shutdown.
No I've not yet report it upstream, because I would like to make a as precise as possible report, against the right component.
You did mention a bug report you filed months ago in your opening mail. And I noticed that you filed a second one too, about a kdeinit crash. This last crash shows exactly the same symptom, namely "Cannot open display". Considering this, I don't really think that this one happens on logout/shutdown, I have to say. I don't think anything would launch kdeinit after the display is closed on shutdown. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (2)
-
Bruno Friedmann -
Wolfgang Bauer