You are not logged in.

#1 2014-09-21 08:19:14

b4nst0n
Member
Registered: 2013-08-08
Posts: 50

[SOLVED]Slim+XFCE4 boot takes terrible long time.

it used to work great.
But from the day I don't remember it take terrible long time for booting xfce4.
Here is the log of boot.

9月 21 16:03:48 x230 slim[363]: (xfdesktop:418): libxfce4ui-WARNING **: ICE I/O Error
9月 21 16:03:48 x230 slim[363]: (xfdesktop:418): libxfce4ui-WARNING **: Disconnected from session manager.

Maybe that is the reason?
I don't know what that mean. sad
Or any other message you need, please tell me.

thanks for all reply. ;D

Last edited by b4nst0n (2014-09-22 11:01:11)

Offline

#2 2014-09-21 17:27:26

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: [SOLVED]Slim+XFCE4 boot takes terrible long time.

try disabling slim and try to startx manually from command line. does that take a long time as well or does this only happen with slim?

Offline

#3 2014-09-22 05:58:52

b4nst0n
Member
Registered: 2013-08-08
Posts: 50

Re: [SOLVED]Slim+XFCE4 boot takes terrible long time.

ooo wrote:

try disabling slim and try to startx manually from command line. does that take a long time as well or does this only happen with slim?

I've try gdm, it also take a long time.
And next I mount /var/log to tmpfs, then it boot very quickly.
I think that is something wrong with journal, but I don't know it exactly. Whatever, it "SOLVED" :>(

Offline

#4 2014-09-22 09:01:01

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: [SOLVED]Slim+XFCE4 boot takes terrible long time.

In that case your issue is probably caused by systemd journal getting too big and fragmented.

You could just remove everything in /var/log/journal and reboot to clear the logs (althought there could be more elegant way to do that),
and I recommend setting size limit for journal to prevent it from growing too big in the future.

Offline

#5 2014-09-22 11:00:44

b4nst0n
Member
Registered: 2013-08-08
Posts: 50

Re: [SOLVED]Slim+XFCE4 boot takes terrible long time.

ooo wrote:

In that case your issue is probably caused by systemd journal getting too big and fragmented.

You could just remove everything in /var/log/journal and reboot to clear the logs (althought there could be more elegant way to do that),
and I recommend setting size limit for journal to prevent it from growing too big in the future.

Thanks for your reply smile
I will try later, and whatever, let's marked this topic SOLVED.

Offline

Board footer

Powered by FluxBB