LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-07-2019, 03:43 PM   #1
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Rep: Reputation: Disabled
Desktop with plasma don't work.


Hello everyone! I did a clean installation of Slackware Current and the plasma of the repository of AlienBOB, so far so good, but, when I start the graphical interface and after logging with my user the desktop is not loaded, just a black screen with the cursor mouse button. I have already consulted many materials from here, excluding .conf, .kde, etc files, but the system still does not work.

Thanks any help!
 
Old 03-07-2019, 05:23 PM   #2
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 445

Rep: Reputation: 146Reputation: 146
Hello esauf, welcome to the LQ Slackware forum.

Did you run 'xwmconfig' after install Plasma?

Code:
NOTE:
If you had installed KDE 4 as your default desktop previously, the removal
of KDE 4 packages will break the symbolic link '/etc/X11/xinit/xinitrc'.
An attempt to run 'startx' in a console will fail with a black screen.
After installing Plasma 5 for the first time, you need to run 'xwmconfig'
and select 'xinitrc.plasma' as your desktop session.
source- instructions to install Plasma 5
http://bear.alienbase.nl/mirrors/ali.../latest/README

Hope this helps.

ps- one problem I had with Plasma was with Nouveau driver,
it froze the desktop (mouse and keyboard) consistently.
Solution was installing the Nvidia proprietary driver.

Last edited by Paulo2; 03-07-2019 at 05:24 PM.
 
Old 03-07-2019, 07:34 PM   #3
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Paulo2 View Post
Hello esauf, welcome to the LQ Slackware forum.

Did you run 'xwmconfig' after install Plasma?

Code:
NOTE:
If you had installed KDE 4 as your default desktop previously, the removal
of KDE 4 packages will break the symbolic link '/etc/X11/xinit/xinitrc'.
An attempt to run 'startx' in a console will fail with a black screen.
After installing Plasma 5 for the first time, you need to run 'xwmconfig'
and select 'xinitrc.plasma' as your desktop session.
source- instructions to install Plasma 5
http://bear.alienbase.nl/mirrors/ali.../latest/README

Hope this helps.

ps- one problem I had with Plasma was with Nouveau driver,
it froze the desktop (mouse and keyboard) consistently.
Solution was installing the Nvidia proprietary driver.


Thanks for the reply Paul. Come on, yes I run `xwmconfig`. Lets why the plasma sddm works and I can log in normally. Right now I am responding by the system, but without the working desktop. As I performed a clean install, I dont have the KDE 4 on my PC. And I followed all instructions from the Alien link.

I dont know how to help, but trying to start with startx shows an error when opening kdeinit5.

Thank you!
Any idea?
 
Old 03-07-2019, 07:39 PM   #4
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Thanks for the reply Paul. Come on, yes I run `xwmconfig`. Lets why the plasma sddm works and I can log in normally. Right now I am responding by the system, but without the working area working. As I performed a clean install, I dont have KDE 4 on my PC. And I followed all instructions from the Alien link.

I dont know how to help, but trying to start with startx shows an error when opening kdeinit5.

Thank you!
Any idea?
 
Old 03-07-2019, 08:03 PM   #5
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,456

Rep: Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086
Try Ctrl-Alt-F1 after trying to log in and see if there are any errors printed to the console.

Last edited by montagdude; 03-07-2019 at 08:06 PM.
 
Old 03-07-2019, 08:30 PM   #6
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Code:
 Could not connect to d-bus server: org.freedesktop.Dbus.Error.Noserver: Failed to connect to socket /TMP/dbus-pgspEAuLtT: Connection refused 
Startkde: Shutting down...
QStandardPaths: XDG_RUNTIME_DIR no set, defaulting to '/tmp/runtime-johnf'
kdeinit5_wrapper: Warning: connect (/tmp/runtime-johnf/kdeinit5_1) failed: No such file or directory
Error: Can not contact kdeinit5!
xprop: unable to open display ' :1
 
Old 03-07-2019, 08:45 PM   #7
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,456

Rep: Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086
Well, that's definitely the problem, but unfortunately I don't know what's causing it. Is that all the messages that are printed? Also, you said you did a clean install without KDE 4. Is there anything else you left out?
 
Old 03-07-2019, 08:59 PM   #8
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by montagdude View Post
Well, that's definitely the problem, but unfortunately I don't know what's causing it. Is that all the messages that are printed? Also, you said you did a clean install without KDE 4. Is there anything else you left out?
No, I just dont install KDE 4, KDEI, XFCE and GAMES. But, right from the start the plasma worked well, but after a reboot the problem arose. Here is the complete output of the error:

Code:
bluedevil: ObexManager operational changed true
bluedevil: ObexAgent registered
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 819, resource id: 33554440, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11984, resource id: 8388626, major code: 2 (ChangeWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11989, resource id: 8388658, major code: 18 (ChangeProperty), minor code: 0
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-johnf'
kdeinit5: Got EXEC_NEW '/usr/lib64/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch '/usr/lib64/qt5/plugins/kf5/kio/file.so'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-johnf'
(II) AIGLX: Suspending AIGLX clients for VT switch
^Cxinit: connection to X server lost

waiting for X server to shut down The X11 connection broke: I/O error (code 1)
Hangup
GOT SIGHUP
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke (error 1). Did the X11 server die?
kdeinit5: Fatal IO error: client killed
The X11 connection broke (error 1). Did the X11 server die?
kdeinit5: sending SIGHUP to children.
The X11 connection broke (error 1). Did the X11 server die?
XIO:  fatal IO error 0 (Success) on X server ":1"
      after 94 requests (94 known processed) with 0 events remaining.
klauncher: Exiting on signal 1
kdeinit5: sending SIGTERM to children.
kdeinit5: Exit.
(II) Server terminated successfully (0). Closing log file.
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-pgspEAuLtT: Connection refused
startkde: Shutting down...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-johnf'
kdeinit5_wrapper: Warning: connect(/tmp/runtime-johnf/kdeinit5__1) failed: : No such file or directory
Error: Can not contact kdeinit5!
xprop:  unable to open display ':1'
xprop:  unable to open display ':1'
startkde: Done.
^C
xinit: unexpected signal 2
 
Old 03-07-2019, 09:11 PM   #9
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,456

Rep: Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086Reputation: 1086
Based on that output, I'm not sure what the problem is. Maybe someone else can tell. Or there may be other useful information in /var/log/Xorg.0.log, ~/.xsession-errors, or /var/log/sddm.log.
 
Old 03-07-2019, 09:37 PM   #10
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Guys, it dont make sense to me. With this problem I was thinking about what I had installed previously, and I removed the fish package (that friendly user), and after restarting the plasma just worked!
I do not know if I'm glad or more curious than might have happened when installing a simple package.
I'll continue to investigate, thank you all!
 
Old 03-08-2019, 08:53 AM   #11
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 445

Rep: Reputation: 146Reputation: 146
The fish shell? (if not please ignore)

I can't reproduce here. Slackware -current up to date with fish installed from ponce's SBo-git.
I can login with sddm and the Plasma desktop loads.
 
Old 03-08-2019, 11:58 AM   #12
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Paulo2 View Post
The fish shell? (if not please ignore)
s.


Yes, this package. But in the logs of the plasma or even of the X they did not refer at all to the SHELL FISH. I am uploading a VM to test this. Thanks!
 
Old 03-08-2019, 06:59 PM   #13
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Guys, after simulating the same environment where I had encountered the error on the plasma boot, actually after installing the '' fish '' package and setting it as standard shell the problem happened in VM too!
It really was the cause of the plasma break, but I still dont understand the reason for this failure. In the fish installation instructions it only informs you that this package might
Quote:
conflict with the /usr/games/fish
binary from the y/bsdgames package,
but dont break the boot of the desktop on its behalf.
Anyway thanks for your help!
 
Old 03-08-2019, 07:43 PM   #14
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 445

Rep: Reputation: 146Reputation: 146
Do you mean change the default shell in /etc/passwd?

I think this is strange because at some point the fish game from bsd-games
changed the name to 'go-fish'.

Code:
Sun Feb 17 23:44:53 UTC 2019
y/bsd-games-2.17-x86_64-1.txz:  Upgraded.
+--------------------------+
Thu Apr 19 01:04:06 UTC 2018
y/bsd-games-2.13-x86_64-13.txz:  Rebuilt.
+--------------------------+
Maybe the problem is set fish as default shell then.



edit-
I can reproduce now, with fish as default shell in /etc/passwd
the Plasma desktop doesn't load after graphical login and splash screen.

edit2-
It happens with init 3 too,
plasma desktop doesn't load after splash screen.

Last edited by Paulo2; 03-08-2019 at 08:13 PM. Reason: s/in some/at some/ and add info
 
Old 03-08-2019, 08:06 PM   #15
esauf
LQ Newbie
 
Registered: Mar 2019
Location: Anywere
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Paulo2 View Post
Do you mean change the default shell in /etc/passwd?

I think this is strange because at some point the fish game from bsd-games
changed the name to 'go-fish'.

Code:
Sun Feb 17 23:44:53 UTC 2019
y/bsd-games-2.17-x86_64-1.txz:  Upgraded.
+--------------------------+
Thu Apr 19 01:04:06 UTC 2018
y/bsd-games-2.13-x86_64-13.txz:  Rebuilt.
+--------------------------+
Maybe the problem is set fish as default shell then.



edit-
I can reproduce now, with fish as default shell in /etc/passwd
the Plasma desktop doesn't load after graphical login and splash screen.
Strange not? I even thought I was crazy. Well, I have not seen anything yet in the logs that could help pinpoint the cause, but it's a good thing to work on. Thanks Paul!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: KDE Plasma 5.7.4 Desktop Environment Is Out with Plasma Desktop and KWin Fixes LXer Syndicated Linux News 0 08-24-2016 01:13 AM
LXer: Plasma 5.6 Makes KDE Plasma Desktop Environment More Powerful, Beautiful And Useful? LXer Syndicated Linux News 0 05-12-2016 12:24 PM
LXer: KDE Plasma 5.6.4 Desktop Environment Launches with Plasma Discover Improvements LXer Syndicated Linux News 0 05-10-2016 07:15 PM
[SOLVED] Please tell me how to tell KDE to run plasma-desktop instead of plasma-netbook Kenny_Strawn Linux - Software 7 07-19-2010 07:32 PM
kde4 on karmic: plasma-desktop doesn't start by itself after removing plasma-netbook eantoranz Linux - Software 8 10-10-2009 09:57 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration