Cheers
I´ve been having this issue for some time but now its getting worse.
The thing is, when shutdown my system it takes ages to shut down. The splash screen shows and stays for at least 1 minute.
I don’t know what the reason is, i googled it a few times but didnt find any equal problem/solution.
Anyone have a clue?
Thanks…
You will be more likely to get help, if you tell us something about how you are shutting down the system.
To illustrate, here is how I shutdown:
I use KDE 4.10.5.
To shutdown, I right-click on the desktop, and select “leave”. And then, in the next menu, I select “shutdown”.
So, now, how do you shutdown?
Well, acpid could cause something like that. If you have that installed, try to uninstall it.
But this should be fixed up to now.
Try to press ESC when the splash screen is there to switch to text messages.
At which point does it hang? What comes next when it continues?
Edit:
Also see here for how to debug this: Debugging
As the others have indicated, we need more information.
check your /var/logs to see if there is anything there. Also when shutting down, hit the Esc key and watch the text. Look for things that Failed or where it hangs for a bit.
As Johnny5 would say “input, input, need more input”
Sorry for the lack of info, but i do the shutdown like that.
For the “acpid”, it wasn’t installed, but i installed it and the system shuts down faster now :sarcastic:.
Doing ESC in the splash screen, its not showing any other message than confirming that the splash screen started and the system hanged after that.
In the logs i didnt know what to search for. There are a couple of ones named “messages”, faillog, boot.log etc.
I tried to open some of them with kwrite “kdesu kwrite” but it didn’t open…
They are usually too big to fit into memory so a normal editor will not work try the less command to look at them
On 2013-08-18 23:46, gogalthorp wrote:
>
> They are usually too big to fit into memory so a normal editor will not
> work try the less command to look at them
And they are owned by root.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I think they are still user readable just can’t save any changes. But the main reason is their possible size. Editors tend to do all things in memory so if the file won’t fit in memory you can not load it into an editor. utilities like less/more/etc just load what they currently are going to display so keep very little in memory
On 2013-08-19 20:46, gogalthorp wrote:
>
> I think they are still user readable just can’t save any changes. But
> the main reason is their possible size. Editors tend to do all things in
> memory so if the file won’t fit in memory you can not load it into an
> editor. utilities like less/more/etc just load what they currently are
> going to display so keep very little in memory
cer@Telcontar:~> l /var/log/messages
-rw-r----- 1 root root 3498350 Aug 19 20:53 /var/log/messages
cer@Telcontar:~>
That’s not user readable 
Ah, joe opens a 1,6G text file just fine - just tried
Slowly, but it works. It creates a huge copy in /tmp.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)