Bug 1265592 - plasma starts only when bash is the login shell
plasma starts only when bash is the login shell
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kf5-kinit (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Daniel Vrátil
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-23 06:19 EDT by fferdasy067ab
Modified: 2015-11-01 20:39 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-23 07:19:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description fferdasy067ab 2015-09-23 06:19:38 EDT
Description of problem:
Instead of my plasma desktop only  a black screen appears with a free movable
mouse pointer.

When I change my login shell from tcsh to bash everthing works
and my normal desktop appears.

I suppose that some scripts need bash to work.

Version-Release number of selected component (if applicable):
I updated on  Mon Sep 21 23:51:27 2015 the last time 
the kf5

How reproducible:


Steps to Reproduce:
1.Login shell tcsh
2. startkde
3.

Actual results:
  a black screen appears with a free movable
mouse pointer.
The startup works normal.

Expected results:
my normal desktop appears after startup

Additional info:

In my .xsession-error 
I read that $DISPLAY is not set, I thought that 
probably plasma starts in my tcsh but need bash. 

from my .xsession-error

sudo: Sie müssen ein TTY haben, um sudo zu verwenden 
startkde: Starting up...
>>> kdeinit5: Aborting. $DISPLAY is not set.  <<<<<
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory
Qt: Session management error: networkIdsList argument is NULL
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.6'
"\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
"\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Comment 1 Kevin Kofler 2015-09-23 07:19:26 EDT
This has nothing to do with the login shell. You cannot run "startkde" on its own, you have to run "startx startkde" to start KDE Plasma from the command line.

Note You need to log in before you can comment on or make changes to this bug.