Bug 358813 - kdeinit5 crash after logout
Summary: kdeinit5 crash after logout
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kinit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-31 09:19 UTC by Alexander Miroshnichenko
Modified: 2018-12-02 03:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
abrt crash log (80.71 KB, text/x-log)
2016-01-31 09:20 UTC, Alexander Miroshnichenko
Details
klauncher [kdeinit5] crash log update 2 (88.43 KB, text/x-log)
2016-05-15 11:47 UTC, Alexander Miroshnichenko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Miroshnichenko 2016-01-31 09:19:44 UTC
KDE plasma 5.5.4
KDE Frameworks 5.18
Qt 5.5.1

Reproducible: Always

Steps to Reproduce:
1. Login to Plasma 5 
2. Logout
3.


Expected Results:  
No crashes
Comment 1 Alexander Miroshnichenko 2016-01-31 09:20:58 UTC
Created attachment 96937 [details]
abrt crash log
Comment 2 David Faure 2016-05-01 09:01:14 UTC
:#3  QMessageLogger::fatal (this=this@entry=0x3f285166ca0, msg=msg@entry=0x3ed3e43c818 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:781
:#4  0x000003ed3e3ad860 in QXcbConnection::QXcbConnection (this=0x10e2afea90, nativeInterface=0x10e2af51a0, canGrabServer=<optimized out>, defaultVisualId=4294967295, displayName=0x0) at qxcbconnection.cpp:511
:#5  0x000003ed3e3b1ffa in QXcbIntegration::QXcbIntegration (this=<optimized out>,
:#6  0x000003ed4f6293de in QXcbIntegrationPlugin::create (this=<optimized out>, system=..., parameters=..., argc=@0x3f28516715c: 2, argv=0x10e2ae2e20) at qxcbmain.cpp:50
:#7  0x000003ed4e641365 in loadIntegration (argv=0x10e2ae2e20, argc=@0x3f28516715c: 2, 
:#9  0x000003ed4e6507c5 in init_platform (argv=0x10e2ae2e20, argc=@0x3f28516715c: 2, 
:#10 QGuiApplicationPrivate::createPlatformIntegration (this=0x10e2af4bc0) at
:#11 0x000003ed4e6517f5 in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1193
:#12 0x000003ed4e317f64 in QCoreApplication::init (this=this@entry=0x3f285167190) at 
:#13 0x000003ed4e3180a9 in QCoreApplication::QCoreApplication (this=0x3f285167190, p=...) at kernel/qcoreapplication.cpp:689
:#14 0x000003ed4e653a24 in QGuiApplication::QGuiApplication (this=0x3f285167190, 
:#15 0x000003ed3e4cedfd in kdemain (argc=2, argv=0x10e2ae2e20) at /usr/src/debug/kde-frameworks/kinit-5.18.0/kinit-5.18.0/src/klauncher/klauncher_main.cpp:162
:#16 0x00000010e07caa5f in launch (argc=2, _name=0x10e07cd97c "klauncher", args=
:#17 0x00000010e07cba88 in start_klauncher () at /usr/src/debug/kde-frameworks/kinit-5.18.0/kinit-5.18.0/src/kdeinit/kinit.cpp:1035
:#18 0x00000010e07c78c0 in main (argc=1, argv=<optimized out>) at /usr/src/debug/kde-frameworks/kinit-5.18.0/kinit-5.18.0/src/kdeinit/kinit.cpp:1794

That is extremely peculiar... why is klauncher still only starting, at the time of logout.... or maybe this crash dialog was open the whole time?

Does this still happen?
Comment 3 Alexander Miroshnichenko 2016-05-09 11:15:37 UTC
crash dialog was open whole time and new dialog was created while every logout.

I had updated to:
KDE plasma 5.6.3 
KDE Frameworks 5.21 
Qt 5.6.0

Currently I does not see crash any more.
Comment 4 David Faure 2016-05-11 07:23:21 UTC
Seems fixed then, please reopen if it happens again.
Comment 5 Alexander Miroshnichenko 2016-05-15 11:43:53 UTC
It happens again
Comment 6 Alexander Miroshnichenko 2016-05-15 11:47:25 UTC
Created attachment 98987 [details]
klauncher [kdeinit5] crash log update 2

klauncher [kdeinit5] crash log

kde-frameworks-5.21.0
kde plasma 5.6.4
qt-5.6.0
Comment 7 Alexander Miroshnichenko 2016-05-15 11:50:09 UTC
At this time klauncher [kdeinit5] crashes at login time.
Comment 8 David Faure 2016-05-21 08:57:08 UTC
:#3  QMessageLogger::fatal (this=this@entry=0x7ffe86010420, msg=msg@entry=0x7f24a7f28b78 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:784
:#4  0x00007f24a7e94c40 in QXcbConnection::QXcbConnection (this=0x5573eb5194a0, nativeInterface=0x5573eb50fc90, canGrabServer=<optimized out>, defaultVisualId=4294967295, displayName=0x0) 

This says that you don't have the variable $DISPLAY set.
Just to be sure -- is this on X11? You have X running, right?
I have no idea why your setup doesn't set $DISPLAY, but that's definitely a setup bug.
Comment 9 Alexander Miroshnichenko 2016-05-21 20:26:01 UTC
(In reply to David Faure from comment #8)
> This says that you don't have the variable $DISPLAY set.
> Just to be sure -- is this on X11? You have X running, right?
X11. You are right.

> I have no idea why your setup doesn't set $DISPLAY, but that's definitely a
> setup bug.
I start Plasma session from sddm. I don't know why and how the variable $DISPLAY does not exists at the starting session.
Comment 10 David Faure 2016-05-21 21:22:44 UTC
Can you confirm my hypothesis by doing echo $DISPLAY in an xterm?
Comment 11 Alexander Miroshnichenko 2016-05-22 20:52:53 UTC
$ echo $DISPLAY
:0
Comment 12 Andrew Crouthamel 2018-11-01 13:50:04 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Bug Janitor Service 2018-11-16 11:38:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2018-12-02 03:44:59 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!