Bug 1465431

Summary: plasmashell crash
Product: [Fedora] Fedora Reporter: Frédéric <ufospoke>
Component: kde-print-managerAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 25CC: jgrulich, jreznik, me, rdieter, than
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:31:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
gdb /usr/bin/plasmashell backtrace none

Description Frédéric 2017-06-27 12:22:46 UTC
Description of problem:

When I login from ssdm on Plasma KDE, I can see quickly my desktop background and then plasmashell crashes and I get only a black screen. The mouse works, Alt+F2 works to launch applications, Ctrl+Alt+Suppr works to log off.

Version-Release number of selected component (if applicable):
5.9.5 (but I tried 5.10.2 from Ed Greshko and got the same issue.

How reproducible:
always

Steps to Reproduce:
1. log in

Actual results:
black screen

Expected results:
normal desktop + menu bar

Additional info:

With a newly created user, I get the same problem.

Here is the content of .xsession-errors after the crash:
xset:  bad font path element (#2), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
startkde: Starting up...

vmware-user: could not open /proc/fs/vmblock/dev
Already running
abrt-applet: Impossible d'afficher la notification :
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Notifications was not provided b>
abrt-applet: Impossible d'afficher la notification :
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Notifications was not provided b>
...
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit

setenforce 0 did not help.

And this is what I see if I boot in level 3 and run startx from the terminal:

xauth: file /home/fred/.serverauth.1393 does not exist

X.Org X Server 1.19.3
Release Date: 2017-03-15
...
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
  xset: bad font path element (#2), possible causes are:
    Directory does not exist or has wrong permissions
      Directory missing fonts.dir
        Incorrect font server address or syntax
          startkde: Starting up...
            dbus-update-activation-environment: warning: error sending
to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.freedesktop.systemd1 exited with status 1
vmware-user: could not open /proc
.KCrash: Attempting to start /usr/bin/kdeinit5 from
kdeinitsock_file=/run/user/1000/kdeinit5__0
Warning: conncect() failed: : No such file or directory
KCrash: Attempting to start /usr/bin/kdeinit5 directly
KCrash: Applicatino 'kdeinit5' crashing...
kdeinit5: Communication error with launcher. Exiting!
.KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
(II) Server terminated successfully (0). Closing log file.
Warning: connect() failed: : Connection refused
KCrash: Attempting to start /usr/libexec/drkonqi directly

When I start from F25 KDE live DVD, I have no issue.

Comment 1 Frédéric 2017-06-28 14:49:31 UTC
Created attachment 1292666 [details]
gdb /usr/bin/plasmashell backtrace

Comment 2 Frédéric 2017-06-28 14:50:20 UTC
dnf remove kde-print-manager-libs solved the issue.

Comment 3 Fedora End Of Life 2017-11-16 18:58:14 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:31:36 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.