You are not logged in.
- Topics: Active | Unanswered
#1 2014-04-06 08:01:33
- wolfdogg
- Member
- From: Portland, OR, USA
- Registered: 2011-05-21
- Posts: 545
kde fried after update, wierd red x's on screen. [solved]
I updated the other night and on first reboot kde came up all fried. the login in prompt comes up fine, then once i log in, the log in screen shows it loading fine. once the desktop loads it loads very funky. all i see on the desktop when it is loaded is a blank screen, and about 10 huge red x icons that looks like a close button just atleast 4-8 times the size, tiled across the top left, then another several on the top right. this is the ONLY thing on the screen. Some of the x buttons to click down, when i click them, some of them dont, but nothing happens... not sure what i was expecting...
any ideas? i dont really want to lose my customizations, is this a known issue? fingers/crossed...
EDIT:
i did find this post after searching for broken KDE https://bbs.archlinux.org/viewtopic.php?id=159227, didnt have that kind of luck searching for KDE broken RED x's not sure why. i think ill check my freespace on that box.
Last edited by wolfdogg (2014-06-25 05:22:30)
Offline
#2 2014-04-06 08:12:11
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: kde fried after update, wierd red x's on screen. [solved]
What is in your logs/journal?
Offline
#3 2014-04-06 18:34:08
- hermi
- Member
- Registered: 2012-06-01
- Posts: 16
Re: kde fried after update, wierd red x's on screen. [solved]
Hallo all!
I have the same Problem.
Where can I find the right logs for information?
Best regards,
hermi
Edit:
I fixed it for me. It seems that my root-partition was full. After I deleted some of the packages in /var/cache/pacman/pkg/ I could log in again. Maybe this is of help.
Last edited by hermi (2014-04-06 19:08:30)
Offline
#4 2014-06-25 05:22:18
- wolfdogg
- Member
- From: Portland, OR, USA
- Registered: 2011-05-21
- Posts: 545
Re: kde fried after update, wierd red x's on screen. [solved]
sorry for not getting back on this sooner. the problem was due to a full partition, no free space. i cleared up some space, and was finally able to successfully boot it.
Offline