You are not logged in.
Hello guys, anyone got the same problem? After my last update (KDE), my KDE is not working. After boot, I just receive many error messages from KDE, like:
1.
Details: Executable: krunner PID: 1469 Signal: Bus error (7) Date/time: 11-09-2013 08:45:10
When I click on close, I got another one:
2.
Details: Executable kmix PID: 1476 Signal: Bus error (7) Date/time....
When click on "Close", got another one...
3.
Details: Executable plasma-desktop PID: 1441 Signal: Bus error (7) Date/time...
And after close them all, I just see a black screen with nothing.
Already tried to remove ~/.kde4
Already checked dbus:
# systemctl list-units | grep dbus
dbus.service loaded active running
dbus.socket loaded active runnind
Any tip or guess?
Last edited by marcelokalib (2013-09-11 12:36:43)
Offline
It wasn't really a kde problem.
MY / fs was 100% full.
I did a simple pacman -Sc and my kde is working again.
Offline
Thx for the help, pacman -Sc did the job for me too! ![]()
Offline
you should look in /var/log for unneeded logfiles this can save much memory (my / partion is only 30GB big).
Linux odin 3.13.1-pf #1 SMP PREEMPT Wed Mar 5 21:47:28 CET 2014 x86_64 GNU/Linux
Offline
you should look in /var/log for unneeded logfiles this can save much memory (my / partion is only 30GB big).
What also helps to avoid wasting rootspace is setting the storage behaviour of journald-logs on `volatile` or `none`… Normally, nobody need tons of old boot-logs. ![]()
Offline
good idea.. just checked and saw log files with more than 3G.
Just cleaned more than 10G with just:
# cd /var/log
# cat /dev/null >everything.log
# cat /dev/null >kernel.log
# cat /dev/null >messages.log
;]
Last edited by marcelokalib (2013-09-11 13:28:21)
Offline
You should also take a look at /var/log/journal/.
Offline
You should also take a look at /var/log/journal/.
[root@tuxcaverna journal]# ls -lh
total 24K
drwxr-xr-x 2 root root 20K Set 11 08:51 3a28ee8b7c1f2e93b2abdcb7000007f7
Offline
cju wrote:You should also take a look at /var/log/journal/.
[root@tuxcaverna journal]# ls -lh
total 24K
drwxr-xr-x 2 root root 20K Set 11 08:51 3a28ee8b7c1f2e93b2abdcb7000007f7
That's a directory. ls only shows how much space the directory takes up, not its contents. Use du -sh to see how much space its contents take. Judging by the the output of ls, there are probably a lot of files in there. You should figure out why your system is generating a lot of logs. Deleting them won't solve the problem in the long run.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
marcelokalib wrote:cju wrote:You should also take a look at /var/log/journal/.
[root@tuxcaverna journal]# ls -lh
total 24K
drwxr-xr-x 2 root root 20K Set 11 08:51 3a28ee8b7c1f2e93b2abdcb7000007f7That's a directory. ls only shows how much space the directory takes up, not its contents. Use du -sh to see how much space its contents take. Judging by the the output of ls, there are probably a lot of files in there. You should figure out why your system is generating a lot of logs. Deleting them won't solve the problem in the long run.
Not really...
Here...
[kalib@tuxcaverna journal]$ ls -lh && ls -lh 3a28ee8b7c1f2e93b2abdcb7000007f7/ && du -h .
total 24K
drwxr-xr-x 2 root root 20K Set 11 08:51 3a28ee8b7c1f2e93b2abdcb7000007f7
total 7,4M
-rw-r----- 1 root systemd-journal 3,8M Set 11 14:01 system.journal
-rw-r-----+ 1 root systemd-journal 3,6M Set 6 08:45 user-1000.journal
7,4M ./3a28ee8b7c1f2e93b2abdcb7000007f7
7,4M .
Offline