KDE does not start

[Waldemar Villamayor-Venialbo]

Hello all,

I am using Fedora 17 KDE (specifically the computing science spin), I
have been running it for a while and never have major problems ;)
until this morning, since when KDE refuses to start. The system boots
normally to the login screen, I provides my username and password and
it seem that KDE will start, but the scren blink and return to the
login screen.

However, I get logged without any problem via console
(<CTRL><ALT><F2>) and have full access to the system. Does any one
know about this bug and how to solve it? Anything to cleanup from some
script file?

Any help would be apreciated.

Waldemar

[Joe Zeff]

On 09/24/2012 12:52 PM, Waldemar Villamayor-Venialbo wrote:
> However, I get logged without any problem via console
> (<CTRL><ALT><F2>) and have full access to the system. Does any one
> know about this bug and how to solve it? Anything to cleanup from some
> script file?

When your KDE login fails and you go to the console, what do you see in 
.xsession-errors that might be a clue?

Also, do you have any other DE such as Fluxbox, Xfce, LDXE or whatever 
that you might try?  If not, install it from the console and try it.  If 
one of them works it tells you that something in KDE itself is b0rk.

[Waldemar Villamayor-Venialbo]

Hello

OK, I reenabled my xsession-error, have to get it disabled because of
this bug (https://bugzilla.redhat.com/show_bug.cgi?id=495190),

I copy (by hand) the content to you, aparently the problem is the
display, but I have no made any change to it:

.xsession-errors
--------------------------------------
No protocol specified
xrdb: Resource temporarily unavailable
xrdb: Can't open display ':0'
<these three lines repeat twice>
No protocol specified
xmodmap: unable to open display ':0'
No protocol specified
<blank line>
(imsettings-check:1051): GLib-WARNING **:
(gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
<blank line>
(imsettings-check:1051): GLib-WARNING **:
(gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
No protocol specified
$DISPLAY is not set or canot connect to the X server.
-----------------------------------------

That's all.

I checked and the x server is running. And the logon screen shows normally.

Waldemar

[Mat Kovach]

Waldemar Villamayor-Venialbo  wrote:
> I am using Fedora 17 KDE (specifically the computing science spin), I
> have been running it for a while and never have major problems ;)
> until this morning, since when KDE refuses to start. The system boots
> normally to the login screen, I provides my username and password and
> it seem that KDE will start, but the scren blink and return to the
> login screen.
>
> However, I get logged without any problem via console
> (<CTRL><ALT><F2>) and have full access to the system. Does any one
> know about this bug and how to solve it? Anything to cleanup from some
> script file?
>
> Any help would be apreciated.

Error should be in $HOME/.xsession-errors, and just may point out 
the issue.

I would also create a new account and see if they account can log 
into KDE.

Also might take a look in your /tmp account. KDE creates a few files
and directories in there. Typically the name are like /tmp/kde-<username>
or such. One of those might have had their permissions/ownership change
for some reason. This could happen if you changed anything that 
might affect /etc/passwd (perhaps changing your UID or GID for some 
reason).

/mek

[Joe Zeff]

On 09/24/2012 01:46 PM, Waldemar Villamayor-Venialbo wrote:
> OK, I reenabled my xsession-error, have to get it disabled because of
> this bug (https://bugzilla.redhat.com/show_bug.cgi?id=495190),
>
> I copy (by hand) the content to you, aparently the problem is the
> display, but I have no made any change to it:

I see: you're getting hammered by a three-year-old bug that everybody 
agrees is a bug, but can't agree on who's responsibility it is, or how 
to solve it.  Ah, the glories of OSS and developers who spend their 
Copious Free Time working on it!

Next question: what graphics card do you use, and if it's nVidia, are 
you using noveau, the binary blob, or kmod/akmond-nvidia?  I ask because 
I use kmod/akmod and there was a kernel update yesterday, but the kmod 
wasn't there until today.  Back when I first got my card, but before I 
added akmod (I keep both because the first reboot is faster with the 
kmod.) I once rebooted into exactly that situation and ended up with a 
white screen, rather like what you're talking about.  In that case, all 
I did was reboot into the previous kernel and keep it there until the 
kmod was ready.

[Waldemar Villamayor-Venialbo]

Jeje,

It is an old nVidia 7600GS, I am using the noveau driver.

Ahh, that's another I already reboted with my old kernel but the
result is the same, I have kernels 3.3.xxxx and 3.5.xxx. Both works
fine, just KDE refuses to start.

2012/9/24 Joe Zeff :
> On 09/24/2012 01:46 PM, Waldemar Villamayor-Venialbo wrote:
> > OK, I reenabled my xsession-error, have to get it disabled because of
> > this bug (https://bugzilla.redhat.com/show_bug.cgi?id=495190),
> >
> > I copy (by hand) the content to you, aparently the problem is the
> > display, but I have no made any change to it:
>
> I see: you're getting hammered by a three-year-old bug that everybody agrees
> is a bug, but can't agree on who's responsibility it is, or how to solve it.
> Ah, the glories of OSS and developers who spend their Copious Free Time
> working on it!
>
> Next question: what graphics card do you use, and if it's nVidia, are you
> using noveau, the binary blob, or kmod/akmond-nvidia?  I ask because I use
> kmod/akmod and there was a kernel update yesterday, but the kmod wasn't
> there until today.  Back when I first got my card, but before I added akmod
> (I keep both because the first reboot is faster with the kmod.) I once
> rebooted into exactly that situation and ended up with a white screen,
> rather like what you're talking about.  In that case, all I did was reboot
> into the previous kernel and keep it there until the kmod was ready.
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Joe Zeff]

On 09/24/2012 02:19 PM, Waldemar Villamayor-Venialbo wrote:
> Jeje,
>
> It is an old nVidia 7600GS, I am using the noveau driver.
>
> Ahh, that's another I already reboted with my old kernel but the
> result is the same, I have kernels 3.3.xxxx and 3.5.xxx. Both works
> fine, just KDE refuses to start.

OK, good.  That's another blind alley we've closed off.

[SOLVED] KDE does not start

[Waldemar Villamayor-Venialbo]

Hello all,

Just for the record.

I googled "$DISPLAY is not set or canot connect to the X server" and
found these pages

http://forums.gentoo.org/viewtopic-t-852063.html
https://bbs.archlinux.org/viewtopic.php?pid=846216

they pointed me to

sudo rm -rfv /var/tmp/kdecache-<user>

the second page said that it "is enough!", but it wasn't in my case,
KDE still does not work.

Then I also proceed to

sudo rm -rfv /tmp/kdecache-<user>
sudo rm /tmp/.Xauthority* (just paranoid)

and reboot.

Some (or all) of those last commands solved the problem, now KDE
returned normally.

Thans Joe and Mat for the support.

Best regards.

Waldemar