Discussion:
[plasmashell] [Bug 401808] New: kde fails to actualize a desktop at startup
Add Reply
George R. Goffe
2018-12-05 23:43:22 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

Bug ID: 401808
Summary: kde fails to actualize a desktop at startup
Product: plasmashell
Version: master
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: ***@davidedmundson.co.uk
Reporter: ***@yahoo.com
CC: plasma-***@kde.org
Target Milestone: 1.0

Created attachment 116704
--> https://bugs.kde.org/attachment.cgi?id=116704&action=edit
uncompressed flat file from /var/log

SUMMARY

startx with .xinitrc containing startkde fails to show a desktop.

I have NO idea where this bug really belongs because KDE appears to be stuck
somewhere in it's initialization processing.

This is a Fedora 30 x86_64 distribution.
kde-workspace-common-4.11.22-23.fc29.noarch is as close as I can come to where
the problem possibly exists.

Are there other files you need to see?

STEPS TO REPRODUCE
1. startx
2.
3.

OBSERVED RESULT

Splash screen appears with a small circle chasing itself. Finally this ends and
a blank screen appears. The mouse works and displays a cursor-pointer but
NOTHING else appears.

Is there a hidden trick to get kde to show more of what it's doing? What
processes should be running when kde is behaving "normally"? Is there a log
other than Xorg.0.log? /var/log/messages shows nothing.

EXPECTED RESULT

a fully operational kde desktop

SOFTWARE/OS VERSIONS
Windows:
MacOS:
Linux/KDE Plasma: kf5-plasma-5.52.0-2.fc30.x86_64
(available in About System)
KDE Plasma Version:
KDE Frameworks Version: kf5-frameworkintegration-5.52.0-1.fc30.x86_64
Qt Version: qt5-qtenginio-1.6.2-19.fc30.x86_64

ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-12-05 23:51:36 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

--- Comment #1 from David Edmundson <***@davidedmundson.co.uk> ---
What about with a display manager?
--
You are receiving this mail because:
You are watching all bug changes.
George R. Goffe
2018-12-06 01:36:20 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

--- Comment #2 from George R. Goffe <***@yahoo.com> ---
David,

I'm not sure what you mean by "Display Manager". Can you elucidate please? My
knowledge of KDE doesn't go much deeper than having .xinitrc contain "startkde"
and my issuing a startx command. I have done some minor configuration changes
with the "systems manager" tool... Most of these changes are what I would call
tweaks.

George...
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-12-06 01:52:10 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

David Edmundson <***@davidedmundson.co.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO

--- Comment #3 from David Edmundson <***@davidedmundson.co.uk> ---
Something like SDDM / LightDM.

Use outside of that is possible, but a failure there typically indicates end
user setup problems rather than an upstream bug.

If you have an issue whilst using a display manager please reopen.
SDDM will store it's logs of the session in
~/.local/share/sddm/xorg-session.log please attach that if you still have
issues.
--
You are receiving this mail because:
You are watching all bug changes.
George R. Goffe
2018-12-06 09:14:32 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

--- Comment #4 from George R. Goffe <***@yahoo.com> ---
David,

The default display manager worked...

I went back to trying to startkde and gave up in disgust... left it with a
working mouse pointer and an otherwise black screen.

Came back about an hour later and kde was now displaying a desktop. I noticed
some tweaks that I missed earlier and attempted to correct them. System
settings had other ideas though. "Global Shortcut daemon" was not running.
Several other items seemed to put system settings in a loop.

Clearly there seems to be some kde components that are not running. I've
included the output of the ps command... if you could identify what's missing
and how to start them or troubleshoot them.

Thanks for your help,

George...
--
You are receiving this mail because:
You are watching all bug changes.
George R. Goffe
2018-12-06 09:15:15 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

--- Comment #5 from George R. Goffe <***@yahoo.com> ---
Created attachment 116709
--> https://bugs.kde.org/attachment.cgi?id=116709&action=edit
uncompressed flat file containing output from the ps command.
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-12-06 11:54:05 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401808

David Edmundson <***@davidedmundson.co.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |NOT A BUG

--- Comment #6 from David Edmundson <***@davidedmundson.co.uk> ---
I had a look, couldn't seen anything major.

I suggest comparing envs of the display manager session, that's the main thing
they're responsible for setting up correctly.

Anything else is outside the scope of our bug tracker, sorry.
--
You are receiving this mail because:
You are watching all bug changes.
Loading...