When I run 'startx' in a console fails with a black screen
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I run 'startx' in a console fails with a black screen
I've have alienbob's ktown installed for a number of weeks on current.
Struggled with slackpkg and slackpkg+ for a number of weeks. I think I've got over that learning curve as everything been working nicely for a week or two including the updates on 23May2018.
Today updated all updates from and including 25May2108.
Now when I boot into the system everything is fine until I start 'startx' when all I get is a black screen.
I've dropped my inittab back to 3 so I can get to the command line at boot. I'm using grub.
I've followed the instructions from alienbob
Quote:
After installing Plasma 5 for the first time, you need to run 'xwmconfig'
and select 'xinitrc.plasma' as your desktop session.
Just in case that got messed up.
I've also run 'xwmconfig' and select 'xinitrc.xfce' as my desktop session. Same result I get a black screen immediately after 'startx'
Any suggestions? I'm running slack current in virtualbox.
Now there's a thought. I'll try running the virtualbox addons stuff as there's been a few kernal upgrades in what I've done this morning.
Rebuilt the packages virtualbox-addons and virtualbox-kernel-addons and installed same. Everything seemed to start ok except the mouse in virtualbox wouldn't move.
Rebuilt the packages again, don't ask why, now I'm almost back to square 1. For a normal start the login manager starts, so I enter the credentials then get the black screen.
Log file attached.
I'm going to continue looking down the virtualbox route for the problem.
Alex
Last edited by aikempshall; 06-03-2018 at 05:51 AM.
Reason: Forgot the attachment
Now I can get startx to start everytime. Not sure how I managed this. Either it was
moving from 4.2.8 to 4.2.10 for the virtualbox addons
rebuilding initrd again, even though I'd already done that.
or more likely I've got a better feel for what's happening. See below.
My session works now with some features. Which are -
start a session and log on to get to the desktop
click the Maximise button, on the title bar, I get the black screen
click the restore button, on the title bar, I get the log on screen so I have to log on again
start a session and log on to get to the desktop
gradually increase the size of the window, when it reaches about two thirds of the available screen, I get a black screen
slightly reduce the size of the screen, I get the log on screen back again so I have to log on again
I've now reverted back to kernel 4.14.43 which was the one that last worked correctly. Same problem.
It might be that there is an issue with one or more packages I installed this morning which were from and including 25May2018. At the moment I've got no idea how I can test the theory.
I have a backup from 21May2018 which might have helped but looking at the mirrors the packages from 23May2018 that have subsequently been recompiled have gone.
EDIT: I wrote my reply before noticing that you had the same result with Xfce, so I wrote troubleshooting steps that were specific to KDE. Anyway, this doesn't apply, but here are some things to look into if the problem is specific to KDE:
1. Are you using the "ls" colors from trapd00r/LS_COLORS? Last I checked, that caused this issue.
2. Are you using the FISH shell? FISH doesn't automatically source the files in /etc/profile.d, and you need them to get KDE 5 running.
3. Are the right files in /etc/profile being loaded? /etc/profile.d/kde.sh in particular, is necessary.
First suggestion: in /etc/acpi/acpi_handler.sh, change "init 0" to "init 3". This lets you use the power button to drop to runlevel 3. Then, instead of using "startx" to launch the GUI, use "init 4" (as root). The GUI can crash, or fail to launch, to your heart's content; all you need is a tap on the power button to fall back to the console. You could even set the default runlevel in /etc/inittab to 4; again, tap the power button to escape a failed GUI launch.
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
#GRUB_GFXMODE=1024x768x32
# Font used on the graphical terminal:
#GRUB_FONT=/usr/share/grub/dejavusansmono.pf2
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
Would you be willing to bisect the issue with git between those two versions? Its tedious, but not really that hard. It would also help to make sure it hasn't been fixed in the git master first.
Would you be willing to bisect the issue with git between those two versions? Its tedious, but not really that hard. It would also help to make sure it hasn't been fixed in the git master first.
Yes I could give it a go. Am familiar with bisecting libreoffice for regressions, but that's a stand alone program. So will need some advice on how I can integrate the mesa git code into my system.
What video driver are you using? I adapted a script from Pat's script in current to build from the mesa git master a few years ago. The problem is that its specific to nouveau and if you are using amd or intel you will need to alter it a little bit (You can see Pat's script from reference). You may also need to build libdrm from the master if configure fails and you can specify a specific commit with the environment variable 'COMMIT'.
For example.
Code:
COMMIT=3e27b37 ./mesa.SlackBuild
The slow and easy way to do this is to bisect mesa in a clone and then feed the commits it wants you to test to the slackbuild, use upgradepkg and then test.
With the information I've got I should have both good and bad starting points. So what I shall do is make a clone of the mesa repository, start the git bisect process then
for each bisect create a tar file by using a hacked version of Pat's get-mesa.sh, so as I don't loose the git stuff
run Pat's SlackBuild against the file created in the previous step
upgrade the package ensuring reinstall flag is set
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.