Version-Release number of selected component: plasma-workspace-drkonqi-5.7.3-2.fc26 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 1719 --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 2314 kernel: 4.8.0-0.rc0.git3.1.fc26.x86_64 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1680 #3 QMessageLogger::fatal at global/qlogging.cpp:793 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:592 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:186 #6 QXcbIntegrationPlugin::create at qxcbmain.cpp:56 #7 QPlatformIntegrationFactory::create at kernel/qplatformintegrationfactory.cpp:71 #8 init_platform at kernel/qguiapplication.cpp:1094 #9 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1263 #10 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1280 #11 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:787 Potential duplicate: bug 1351165
Created attachment 1187656 [details] File: backtrace
Created attachment 1187657 [details] File: cgroup
Created attachment 1187658 [details] File: core_backtrace
Created attachment 1187659 [details] File: dso_list
Created attachment 1187660 [details] File: environ
Created attachment 1187661 [details] File: limits
Created attachment 1187662 [details] File: maps
Created attachment 1187663 [details] File: mountinfo
Created attachment 1187664 [details] File: namespaces
Created attachment 1187665 [details] File: open_fds
Created attachment 1187666 [details] File: proc_pid_status
Created attachment 1187667 [details] File: var_log_messages
Similar problem has been detected: I'm sorry, but I'm not 100% sure as to the order of events... I was working on my other computer when I noticed the screen saver about to start. I hit the arrow key to stop that and went back to working on the other computer for a while. I came back to my computer here and went to unlock it. Not paying any attention, I typed in my password and hit enter. I didn't notice that it would start a new session or something (since I'd hit the arrow key a few minutes prior trying to stop the auto screen lock). Here's where I'm not 100% about... either: 1) Well, the new session didn't load all the way or maybe I was too inpatient, but I let it go for about 20 seconds and the kde loading login progress bar was stuck at abour 40% loaded. I contol + alt + f3 and that got me to a new session. I control + alt + f1 and that brought me back to the unlock screen for my user. I unlocked it, but I then had this issue with the application crashing. or 2) My new session attempt did load and then I saw it was a new session. I then did the control alt f3, control alt f1 to get back to the unlock screen for my previous session. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :1 --appname kwin_x11 --apppath /usr/bin --signal 11 --pid 20243 --appversion 5.7.4 --programname KWin --bugaddress submit.org --startupid 0 crash_function: qt_message_fatal executable: /usr/libexec/drkonqi global_pid: 20307 kernel: 4.8.0-0.rc3.git2.1.fc26.x86_64 package: plasma-workspace-drkonqi-5.7.4-1.fc26 pkg_vendor: Fedora Project reason: drkonqi killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
*** Bug 1471909 has been marked as a duplicate of this bug. ***
Similar problem has been detected: login after poweron/off reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/krunner crash_function: qt_message_fatal executable: /usr/bin/krunner journald_cursor: s=47ecbea39ead43c8b3958e9cb12c6a8f;i=11698b;b=39248daad4594e85bf2002aa8326e5a5;m=baf8bb0a8;t=5549058f67f89;x=c04f7efa26b10432 kernel: 4.11.9-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: krunner killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: login after poweroff/on reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/drkonqi -platform xcb -display :3 --appname krunner --apppath /usr/bin --signal 11 --pid 12161 --appversion 5.10.1 --programname krunner --bugaddress submit.org --startupid 0 --restarted crash_function: qt_message_fatal executable: /usr/libexec/drkonqi journald_cursor: s=47ecbea39ead43c8b3958e9cb12c6a8f;i=116993;b=39248daad4594e85bf2002aa8326e5a5;m=baf917cda;t=5549058fc4bbb;x=dc10bd6ef486061d kernel: 4.11.9-300.fc26.x86_64 package: plasma-workspace-drkonqi-5.10.1-1.fc26 reason: drkonqi killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1001
xauth issue, from var_log_messages: Aug 04 15:44:33 laptop drkonqi[2314]: QXcbConnection: Could not connect to display :0
*** Bug 1479005 has been marked as a duplicate of this bug. ***
Similar problem has been detected: logout in a vnc session reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/ksmserver-logout-greeter --shutdown-allowed --mode logout --mode-fd 35 crash_function: qt_message_fatal executable: /usr/libexec/ksmserver-logout-greeter journald_cursor: s=928a62ee230c4476b647df572000d001;i=2e34c;b=0e501ae2a1f640e5831cb869083d2633;m=6af7e2b7ec;t=556871dcd59d1;x=baaab16449aa6573 kernel: 4.11.11-300.fc26.x86_64 package: plasma-workspace-5.10.4-1.fc26 reason: ksmserver-logout-greeter killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: May be switching like: {Plasma} -> {SDDM} -> {LxQT}. All via UI. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/kuiserver5 crash_function: qt_message_fatal executable: /usr/bin/kuiserver5 journald_cursor: s=2274a2e59f8446c3b4f200fbaef6799f;i=20b2;b=37b58c5f614c4b46a818bf2d49a093fe;m=6c517d01;t=5558c62d003ad;x=24f03b7f0d630cd8 kernel: 4.11.8-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: kuiserver5 killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
from backtrace: #3 QMessageLogger::fatal (this=this@entry=0x7ffec5585ac0, msg=msg@entry=0x7ffba639a9e8 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:793 likely related to bug #1370222
*** Bug 1494078 has been marked as a duplicate of this bug. ***
*** Bug 1495010 has been marked as a duplicate of this bug. ***
*** Bug 1497529 has been marked as a duplicate of this bug. ***
*** Bug 1499209 has been marked as a duplicate of this bug. ***
This should be fixed by an update that fixes the linked bug #1370222 https://bodhi.fedoraproject.org/updates/FEDORA-2017-d119cd8c3f
*** Bug 1511315 has been marked as a duplicate of this bug. ***