[F25] only black screen with KDE Plasma session

[Frédéric Bron]

Hi,

Since this morning, after loging in on a Plasma KDE session, I can
first see the desktop then only a black screen with only the mouse
available, nothing else.
Ctrl+Alt+Suppr, brings the log out screen so I can log out.
I can also switch to a text terminal with Ctrl+Alt+F2. That's all.

On the fedora users mailing list, we identified that it is due to
plasmashell crash.
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

[Frédéric Bron]

>  KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
>  KCrash: Application 'plasmashell' crashing...
>  KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit 
some additional information: my version of plasma-desktop is 5.9.5
revision 1.fc25

I am still in the dark :(

[Oron Peled]

On Friday, 23 June 2017 16:52:32 IDT Frédéric Bron wrote:
>  Hi,
>  
>  Since this morning, after loging in on a Plasma KDE session, I can
>  first see the desktop then only a black screen with only the mouse
>  available, nothing else.
>  Ctrl+Alt+Suppr, brings the log out screen so I can log out.
>  I can also switch to a text terminal with Ctrl+Alt+F2. That's all. 
Workaround (did it many times when plasmashell crashed in the past):
 * You can use Alt+F2 to open krunner dialog (normally tiny at the top).
 * Than type "plasmashell" + Enter and it should run.
 * Even if it crash again, you should be able to use the same method
   for running konsole and have further debugging lead.

>  On the fedora users mailing list, we identified that it is due to
>  plasmashell crash.
>  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
>  _______________________________________________
>  kde mailing list -- kde(a)lists.fedoraproject.org
>  To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org 
-- 
Oron Peled                                 Voice: [phone]

"In theory, it's practical. In practice - it's only a theory".

[Frédéric Bron]

> > Since this morning, after loging in on a Plasma KDE session, I
> can
> > first see the desktop then only a black screen with only the mouse
> > available, nothing else.
>
>  Workaround (did it many times when plasmashell crashed in the past):
>   * You can use Alt+F2 to open krunner dialog (normally tiny at the top).
>   * Than type "plasmashell" + Enter and it should run.
>   * Even if it crash again, you should be able to use the same method
>     for running konsole and have further debugging lead. 
Oh, that's great! It works, yes, very well.
If I launch plasmashell in konsole, below is what I get. Could that
give a clue to what happens?

Many thanks,

Frédéric

$ plasmashell
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
org.kde.kcoreaddons: Expected JSON property
"X-Plasma-ContainmentCategories" to be a string list. Treating it as a
list with a single entry: "panel" org.kde.plasma.desktop.appmenubar
org.kde.kcoreaddons: Expected JSON property
"X-Plasma-ContainmentCategories" to be a string list. Treating it as a
list with a single entry: "panel" org.kde.plasma.desktop.emptyPanel
org.kde.kcoreaddons: Expected JSON property
"X-Plasma-ContainmentCategories" to be a string list. Treating it as a
list with a single entry: "panel" org.kde.plasma.desktop.defaultPanel
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
No metadata file in the package, expected it at: "/home/fred/Images/"
No metadata file in the package, expected it at: "/home/fred/Images/"
No metadata file in the package, expected it at: "/home/fred/Images/"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:252:21:
QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/BarMonitor.qml:47:
TypeError: Cannot read property 'length' of undefined
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/BarMonitor.qml:49:20:
Unable to assign [undefined] to QColor
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst
using setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:353:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:352:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:351:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:350:
TypeError: Cannot read property 'padding' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/BarMonitor.qml:49:20:
Unable to assign [undefined] to QColor
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried
("/home/fred/.local/share",
"/usr/share/kde-settings/kde-profile/default/share",
"/usr/local/share", "/usr/share")
Trying to use rootObject before initialization is completed, whilst
using setInitializationDelayed. Forcing completion
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:350:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:351:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:352:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:353:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:353:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:352:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:351:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:350:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:350:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:351:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:352:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:353:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:350:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:351:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:352:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:353:
TypeError: Cannot read property 'padding' of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError:
Cannot read property of null
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 17 and type 'Read', disabling...

[Ed Greshko]

On 06/24/17 17:53, Frédéric Bron wrote:
> >> Since this morning, after loging in on a Plasma KDE session,
> I can
> >> first see the desktop then only a black screen with only the mouse
> >> available, nothing else.
> > Workaround (did it many times when plasmashell crashed in the past):
> >  * You can use Alt+F2 to open krunner dialog (normally tiny at the top).
> >  * Than type "plasmashell" + Enter and it should run.
> >  * Even if it crash again, you should be able to use the same method
> >    for running konsole and have further debugging lead.
>  Oh, that's great! It works, yes, very well.
>  If I launch plasmashell in konsole, below is what I get. Could that
>  give a clue to what happens? 

I'm not able to comment on the output you are seeing.  But, I do have one other
question.  Can you, or have you, tried to boot from a Live image, either from DVD or
USB device?

FWIW, I did do what was suggested after killing plasmashell with a -9 and got the
output.  Some parts are similar, others not.  Nothing jumps out at me as a clue. 
Also the system I'm running has a pre-release version of KDE on it....so it may add
more confusion than not.



-- 
Fedora Users List - The place to go to speculate endlessly

[Frédéric Bron]

>  I'm not able to comment on the output you are seeing.  But, I do
> have one other
>  question.  Can you, or have you, tried to boot from a Live image, either from DVD or
>  USB device? 
I did but not recently. One time, I suspected a SSD issue so I wanted
to run fsck.

Frédéric

[Ed Greshko]

On 06/24/17 19:10, Frédéric Bron wrote:
> > I'm not able to comment on the output you are seeing.  But, I
> do have one other
> > question.  Can you, or have you, tried to boot from a Live image, either from DVD or
> > USB device?
>  I did but not recently. One time, I suspected a SSD issue so I wanted
>  to run fsck.
>  
Assuming the fsck ran without error, it would be good to know if the Live image runs
just to rule out a HW problem which may have happened overnight.  :-)


-- 
Fedora Users List - The place to go to speculate endlessly

[Frédéric Bron]

>  Assuming the fsck ran without error, 
yes, that was the case

>  it would be good to know if the Live image runs
>  just to rule out a HW problem which may have happened overnight.  :-) 
F25 KDE live works nicely.

Cheers,

Frédéric

[Frédéric Bron]

>  
Hi, I still have a black screen, any idea where to look at?
Thanks,
Frédéric

[Ed Greshko]

On 06/27/17 17:08, Frédéric Bron wrote:
>  Hi, I still have a black screen, any idea where to look at?
>  Thanks, 

Well.....   I don't have a particular suggestion as to finding the culprit.  But I do
have a suggestion which surely won't make things any worse.

I've been running plasma 5.10.2 for sometime on a laptop that I use mainly for
testing and it runs quite well.  I have the _copr_mkyral-kf5-unstable.repo and
_copr_mkyral-plasma-unstable.repo installed/enabled from
https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=mkyral.

You could try enabling those repos and updating to 5.10.2 and see if thing improve.  
You could always go back to "normal" with a "distro-sync".

-- 
Fedora Users List - The place to go to speculate endlessly

[Frédéric Bron]

>  I've been running plasma 5.10.2 for sometime on a laptop that I
> use mainly for
>  testing and it runs quite well.  I have the _copr_mkyral-kf5-unstable.repo and
>  _copr_mkyral-plasma-unstable.repo installed/enabled from
>  https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=mkyral.
>
>  You could try enabling those repos and updating to 5.10.2 and see if thing improve.
Thanks for the idea but I get the same issue with your versions! it
just takes more time to logout with Ctrl+Alt+Suppr.

I am hopeless. For now, I use LXDE but it does not work as well as KDE
(before). For example, I have no default pdf viewer installed, no
sound volume icon...

Frédéric

[Ed Greshko]

On 06/27/17 19:24, Frédéric Bron wrote:
> > I've been running plasma 5.10.2 for sometime on a laptop that
> I use mainly for
> > testing and it runs quite well.  I have the _copr_mkyral-kf5-unstable.repo and
> > _copr_mkyral-plasma-unstable.repo installed/enabled from
> > https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=mkyral.
> >
> > You could try enabling those repos and updating to 5.10.2 and see if thing improve.
>  Thanks for the idea but I get the same issue with your versions! it
>  just takes more time to logout with Ctrl+Alt+Suppr.
>
>  I am hopeless. For now, I use LXDE but it does not work as well as KDE
>  (before). For example, I have no default pdf viewer installed, no
>  sound volume icon...
>  
Oh, well....  Worth a try.  Doesn't sound as if even an upgrade to F26 Beta
would be
successful.

Time to file a bugzilla?   Maybe you'll get some troubleshooting avenue that way.


-- 
Fedora Users List - The place to go to speculate endlessly

[Frédéric Bron]

>  Oh, well....  Worth a try.  Doesn't sound as if even an upgrade
> to F26 Beta would be
>  successful.
>  Time to file a bugzilla?   Maybe you'll get some troubleshooting avenue that way.
yep, I'll do that, thanks for your support Ed.
Regards,

Frédéric

[Frédéric Bron]

> > Time to file a bugzilla?   Maybe you'll get some
> troubleshooting avenue that way.
>  yep, I'll do that, thanks for your support Ed. 
https://bugzilla.redhat.com/show_bug.cgi?id=1465431

[Felix Miata]

Frédéric Bron composed on 2017-06-27 14:25 (UTC+0200):
.
>  https://bugzilla.redhat.com/show_bug.cgi?id=1465431 
.
Have you already done a distro-sync, or tried uninstalling sddm before trying
startx? KDM still works in all F25 & F26 64 bit installations here. Elsewhere
more than once I've seem Plasma trouble solved by eliminating sddm from the system.

Have you already tried uninstalling the nouveau driver? Xorg should fall back to
using the integral modeset driver automatically unless your NV gfxcard is too
old or too new.

If nothing else has helped as yet, provide hardware information:

PC/laptop model
lspci -nnk | grep -A5 VGA (pasted here and bug)
Xorg.0.log (attached to bug)
journalctl -b _COMM=Xorg.bin (attached to bug)
if exists, /etc/X11/xorg.conf or /etc/X11/xorg.conf.d/*

See also: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[Frédéric Bron]

>  Have you already done a distro-sync 
just done, no change

>  or tried uninstalling sddm before trying
>  startx? KDM still works 
not yet, should I just do this?
$ dnf remove ssdm*
$ dnf install kdm

>  Have you already tried uninstalling the nouveau driver? 
should I do this?
$ dnf remove nouveau*

>  If nothing else has helped as yet, provide hardware information:
Here some first information:

laptop DELL XPS15 9550

$ lspci -nnk|grep -A5 VGA
0:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics
530 [8086:191b] (rev 06)
    Subsystem: Dell Device [1028:06e4]
    Kernel driver in use: i915
    Kernel modules: i915
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake
Processor Thermal Subsystem [8086:1903] (rev 07)
    Subsystem: Dell Device [1028:06e4]

[Felix Miata]

Frédéric Bron composed on 2017-06-28 09:36 (UTC+0200):

> > Have you already done a distro-sync 
.
>  just done, no change 
.
> > or tried uninstalling sddm before trying
> > startx? KDM still works 
.
>  not yet, should I just do this?
>  $ dnf remove ssdm*
>  $ dnf install kdm 
.
I would do only the first, then reboot, then try startx before proceeding to
install kdm. Given below, I don't believe sddm is your problem or that kdm would
help.
.
> > Have you already tried uninstalling the nouveau driver? 
.
>  should I do this?
>  $ dnf remove nouveau* 
.
That would be dnf remove xorg-x11-video-nouveau, but see below first.
.
> > If nothing else has helped as yet, provide hardware information:
.
>  Here some first information: 
.
>  laptop DELL XPS15 9550 
.
>  $ lspci -nnk|grep -A5 VGA
>  0:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics
>  530 [8086:191b] (rev 06)
>      Subsystem: Dell Device [1028:06e4]
>      Kernel driver in use: i915
>      Kernel modules: i915
>  00:04.0 Signal processing controller [1180]: Intel Corporation Skylake
>  Processor Thermal Subsystem [8086:1903] (rev 07)
>      Subsystem: Dell Device [1028:06e4] 
. 										
Your other thread indicated you have NVidia gfx, confirmed by looking at
http://laptoping.com/specs/product/dell-xps-15-9550/ (Skylake) so it looks like
you need to but have not utilized this doc:
https://fedoraproject.org/wiki/Bumblebee

That lspci -nnk | grep -A5 probably should have been -A12 or so. Try instead
'dnf install inxi; inxi -c0 -G'.

Plasmashell seems might be thinking both displays are currently connected and it
is trying to use the disconnected display, due to an inappropriate driver and/or
laptop firmware configuration, or defective firmware in need of update.

If it was here, first thing I would try is adding the following to
~/.config/kded5rc:

	[Module-kscreen]
	autoload=false

just to see if it stops the black. It's a troubleshooting option, not something
to keep permanently unless you plan to manually configure multiple displays
through a startup xrandr script or xorg.conf*.

Is linux-firmware installed?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[Frédéric Bron]

>  That lspci -nnk | grep -A5 probably should have been -A12 or so.
maybe you wanted to see the NVIDIA part:

00:02.0 VGA compatible controller [0300]: Intel Corporation HD
Graphics 530 [8086:191b] (rev 06)
    Subsystem: Dell Device [1028:06e4]
    Kernel driver in use: i915
    Kernel modules: i915
...
01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX
960M] [10de:139b] (rev a2)
    Subsystem: Dell Device [1028:06e4]
    Kernel driver in use: nouveau
    Kernel modules: nouveau

>  'dnf install inxi; inxi -c0 -G'. 
Graphics:  Card-1: Intel HD Graphics 530
           Card-2: NVIDIA GM107M [GeForce GTX 960M]
           Display Server: X.org 1.19.3 drivers:
modesetting,nouveau,intel (unloaded: fbdev,vesa)
           tty size: 120x80 Advanced Data: N/A for root

>  Plasmashell seems might be thinking both displays are currently
> connected and it
>  is trying to use the disconnected display, due to an inappropriate driver and/or
>  laptop firmware configuration, or defective firmware in need of update.
>
>  If it was here, first thing I would try is adding the following to
>  ~/.config/kded5rc:
>
>          [Module-kscreen]
>          autoload=false 
I did not have this file, so I created it with the content you show.
I rebooted, logged in, no more success.
I also removed sddm and had to run startx but I got the same black screen.

>  Is linux-firmware installed? 
yes
Version     : 20170605
Révision    : 74.git37857004.fc25

>  https://fedoraproject.org/wiki/Bumblebee 
You are right, I was not aware of that. Seems complicated. Do you
recommand that I do not use nouveau but prime instead, is that what I
should understand?

Frédéric

[Ed Greshko]

On 06/28/17 19:06, Frédéric Bron wrote:
>  maybe you wanted to see the NVIDIA part:
>
>  00:02.0 VGA compatible controller [0300]: Intel Corporation HD
>  Graphics 530 [8086:191b] (rev 06)
>      Subsystem: Dell Device [1028:06e4]
>      Kernel driver in use: i915
>      Kernel modules: i915
>  ...
>  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX
>  960M] [10de:139b] (rev a2)
>      Subsystem: Dell Device [1028:06e4]
>      Kernel driver in use: nouveau
>      Kernel modules: nouveau 

Just a couple of things....

First, it is probably a good idea to remind people that your system was running
perfectly fine one day and since turning it on the next day you've be plagued with
plasmashell crashes.  As you've noted in the user's list the only thing you know
changed on your system was google-chrome-stable, leptonica, and tbb being updated.

I don't know if this is possible, but can the Intel device be disabled in the BIOS as
a test?

-- 
Fedora Users List - The place to go to speculate endlessly

[Frédéric Bron]

>  I don't know if this is possible, but can the Intel device be
> disabled in the BIOS as
>  a test? 
you mean so that I use only the nvidia card?

Frédéric

[Ed Greshko]

On 06/28/17 19:55, Frédéric Bron wrote:
> > I don't know if this is possible, but can the Intel device be
> disabled in the BIOS as
> > a test?
>  you mean so that I use only the nvidia card?
>  
Yes, that is my meaning. 

Or, the other way around as well....use only the intel.

-- 
Fedora Users List - The place to go to speculate endlessly

[Adam Batkin]

On 06/27/2017 05:08 AM, Frédéric Bron wrote:
>  Hi, I still have a black screen, any idea where to look at? 
Have you tried creating a new user on the system and logging in there? 
If that works, it could be something to broken in your profile. Try 
finding the various KDE settings and cache directories and deleting them 
until it works.

-Adam Batkin

[Ed Greshko]

On 06/28/17 10:22, Adam Batkin wrote:
>  On 06/27/2017 05:08 AM, Frédéric Bron wrote:
> > Hi, I still have a black screen, any idea where to look at?
>
>  Have you tried creating a new user on the system and logging in there? If that
>  works, it could be something to broken in your profile. Try finding the various KDE
>  settings and cache directories and deleting them until it works. 
Yes, he did.  That appears in the user's list thread of the same subject.

https://lists.fedoraproject.org/archives/list/[e-mail].o...

:-(

-- 
Fedora Users List - The place to go to speculate endlessly

[Frédéric Bron]

>  Have you tried creating a new user on the system and logging in
> there? If
>  that works, it could be something to broken in your profile. Try finding the
>  various KDE settings and cache directories and deleting them until it works. 
Yes I did following Ed's suggestion.
Thanks,
Frédéric

[Felix Miata]

Frédéric Bron composed on 2017-06-28 06:25 (UTC+0200):
.
> > Have you tried creating a new user on the system and logging in
> there? If
> > that works, it could be something to broken in your profile. Try finding the
> > various KDE settings and cache directories and deleting them until it works. 
.
>  Yes I did following Ed's suggestion. . 
With what result?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[Frédéric Bron]

> >> Have you tried creating a new user on the system and logging
> in there? If
> >> that works, it could be something to broken in your profile. Try finding the
> >> various KDE settings and cache directories and deleting them until it works.
>  .
> > Yes I did following Ed's suggestion. .
>  With what result? 
sorry, same black screen with the new user!

[Felix Miata]

When you disconnect the external display, how exactly do you "disconnect"? What
brand and model is the external display? Disconnecting by powering down the
external display is not guaranteed to suffice with some models, such as one of
my Dells (21:9 U2913WM). Please try disconnecting the video cable from the
laptop if that is not what you have been doing.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[Frédéric Bron]

>  When you disconnect the external display, how exactly do you
> "disconnect"? 
I mean unplug the HDMI cable from the laptop.
And yes it is a DELL monitor

Frédéric

[Rex Dieter]

Frédéric Bron wrote:

>  Hi,
>  
>  Since this morning, after loging in on a Plasma KDE session, I can
>  first see the desktop then only a black screen with only the mouse
>  available, nothing else.
>  Ctrl+Alt+Suppr, brings the log out screen so I can log out.
>  I can also switch to a text terminal with Ctrl+Alt+F2. That's all.
>  
>  On the fedora users mailing list, we identified that it is due to
>  plasmashell crash. 
If none of the crash handlers catch this (like abrt or drkonqi), you can try 
running plasmashell under gdb to get a backtrace.  One way, use krunner 
(ALT-F2) to launch konsole, then run:

gdb /usr/bin/plasmashell

...

(gdb) run

... wait for crash...

(gdb) thread apply all backtrace

and post the result (ideally, you may need to install some -debuginfo to get 
a more useful backtrace).

-- Rex

[Frédéric Bron]

>  If none of the crash handlers catch this (like abrt or drkonqi), you
> can try
>  running plasmashell under gdb to get a backtrace.  One way, use krunner
>  (ALT-F2) to launch konsole, then run:
>
>  gdb /usr/bin/plasmashell 
Good idea. The log is attached.
Can you see something?

Frédéric

[Rex Dieter]

Frédéric Bron wrote:

> > If none of the crash handlers catch this (like abrt or drkonqi),
> you can
> > try
> > running plasmashell under gdb to get a backtrace.  One way, use krunner
> > (ALT-F2) to launch konsole, then run:
> >
> > gdb /usr/bin/plasmashell
>  
>  Good idea. The log is attached.
>  Can you see something? 
I think this thread, something to do with cups:

Thread 1 (Thread 0x7fffe42fb040 (LWP 10727)):
#0  0x00007fff28ce3d86 in JobModel::updateJob(int, KCupsJob const&) () at 
/lib64/libkcupslib.so
#1  0x00007fff28ce6137 in JobModel::getJobFinished() () at 
/lib64/libkcupslib.so
#2  0x00007fff28cec335 in JobModel::qt_static_metacall(QObject*, 
QMetaObject::Call, int, void**) [clone .part.7] () at /lib64/libkcupslib.so
#3  0x00007ffff1d727e9 in QObject::event(QEvent*) () at 
/lib64/libQt5Core.so.5
#4  0x00007ffff2616ecc in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) () at /lib64/libQt5Widgets.so.5
...

will need more -debuginfo to know more, at least:
dnf debuginfo-install kde-print-manager
(and try generating a backtrace again)


Now that we have a better idea what is crashing, one workaround to consider 
to get a working plasmashell...  temporarily remove print applet support by 
doing:
dnf remove kde-print-manager

-- Rex

[Frédéric Bron]

Hi,

Thanks for your help.

>  will need more -debuginfo to know more, at least:
>  dnf debuginfo-install kde-print-manager
>  (and try generating a backtrace again) 
please find the attached the new log

>  Now that we have a better idea what is crashing, one workaround to
> consider
>  to get a working plasmashell...  temporarily remove print applet support by
>  doing:
>  dnf remove kde-print-manager 
I will try that now. I guess I will not be able to print anymore?
I remember now that probably the day before I had the issue I had to
reinstall my printer because it was not found anymore...

Frédéric

[Luigi Toscano]

On Wednesday, 28 June 2017 16:21:24 CEST Frédéric Bron wrote:
>  Hi,
>  
>  Thanks for your help.
>  
>  > will need more -debuginfo to know more, at least:
>  > dnf debuginfo-install kde-print-manager
>  > (and try generating a backtrace again)
>  
>  please find the attached the new log 
Try to remove kde-print-manager-libs (which contains the offending library).

>  
>  > Now that we have a better idea what is crashing, one workaround to
>  > consider
>  > to get a working plasmashell...  temporarily remove print applet support
>  > by
>  > doing:
>  > dnf remove kde-print-manager
>  
>  I will try that now. I guess I will not be able to print anymore?
>  I remember now that probably the day before I had the issue I had to
>  reinstall my printer because it was not found anymore... 
No, it means that you could not use print-manager developed by KDE. Cups is 
still working independently. Still a bug.

-- 
Luigi

[Frédéric Bron]

>  Try to remove kde-print-manager-libs (which contains the offending
> library). 
Great, it works again!
What should I do now to have this corrected? Can I help?

And thanks a lot to all of you who helped :)

Frédéric