You are not logged in.
I am most times getting a blank screen on startup. I cant see the cursor or anything, but I can see that the desktop enviroment loads.
They way I get it to start up, is to start it up in failsafe mode with out the graphical interface and then restart. I have no idea why that works.
Last edited by bobhund (2017-02-15 15:31:46)
Offline
Does this problem also happen if you load up a "live" ISO image or does it only happen in your BunsenLabs system?
What is your graphics hardware?
lspci -knn | grep -iA2 'vga\|3d'
When you reboot successfully after the problem occurs, have a look in /var/log/Xorg.0.log.old for any errors.
The systemd journal can also be used to investigate this, guide here:
Offline
It only happens on my bunselsystem, not on the bunsel on a stick.
when I run the code I get
~$ lspci -knn | grep -iA2 'vga\|3d'
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)
Subsystem: Dell Latitude D630 [1028:01f9]
Kernel driver in use: i915
Xorg.0.log.old seems to be empty
Let me read the article about the systemd journal
Offline
that was a bit weird, when I run journalctl I get the response
No journal files were found.
Offline
^ Either run `journalctl` as root or add your user to the "systemd-journal" group:
sudo gpasswd -a $USER systemd-journal
You may also need to enable persistence by editing the file at /etc/systemd/journald.conf (as root!) and un-commenting and changing this line:
Storage=persistent
Once you have debugged this problem, remember to reset (or remove) that line and delete the directory:
sudo rm -rf /var/log/journal
If this is not done, large journal files may delay startup significantly.
Offline
HoaS, is there any reason why the Live ISO doesn't have journaling set up and ready to go by default, with the persistence line and everything already set up? It seems to be a point that whenever we give advice to people to use the journalctl command, it's not already configured, which to me...someone running systemd, really should have (sort of ignores one of the huge benefist of the systemd suite)
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
^ We ship with the stock Debian configuration.
I did configure a persistent journal on my jessie system and forgot about it until a few weeks later when I received a user complaint about excessive boot times -- it was taking 45 seconds to process the journal files (normal boot time is ~25 seconds) with *nothing* showing in `systemd-analyze`, I had to comb through the journal itself and note the timestamps on each entry to spot the cause of the delay
Offline
I got journalctl to work but there are litterally thousands of lines. Am I looking for anything in particularly?
Offline
Upload the entire thing to http://paste.debian.net/ and post the URL here and I will have a quick look.
The guide that I linked to in my first post details the various filters that can be applied with the `journalctl` command.
Offline
Hi All, I must admit I punted on this one over the chritsmas, and just left my box in a corne. I got it out the other day and after an apt-get upgrade, it seems to have fixed itself.
Now I just need to label it solved. Which I for some reason can not find out how to do.
Offline
Edit your first post and add Solved to the subject field.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Online