[Solved] logout

[zvacet]

It seams that logout doesn´t work.For me any way.If I try to logout I get black screen and there is no way to login again.I have to reboot.  

[richdb]

place your bugs over here: http://www.bugs.pardus-anka.org/index.php?project=4&do=index&switch=1

[zvacet]

Done. 

[Anglo]

It seams that logout doesn´t work.For me any way.If I try to logout I get black screen and there is no way to login again.I have to reboot. 

Try using terminal , type " telinit 1" then  " halt "

[zvacet]

Code:

telinit 1

It look this command log me out ( again black screen) so I have no chance to even type

Code:

halt

[Anglo]

Code:

telinit 1

It look this command log me out ( again black screen) so I have no chance to even type

Code:

halt

hmm

[Lisa]

Hi zvacet,

Are you seeing any errors, segfaults in /var/log/syslog when this happens? 
Looks like flyspray bug site has no way to include a log from system as text file attachment.  These can give helpful clues.

[zvacet]

I found out that i can login after logout.It is not real solution but...On black screen i see cursor and when I move it to certain position it change shape and then I know I can type there.That is a way I login after logout.Login screen is missing. Here is syslog if any one want to read it.

[Lisa]

zvacet. This sounds familiar to what you are experiencing.  You could try the solution by zorael and edit the /etc/X11/kdm/kdmrc.

First make a backup of file /etc/X11/kdm/kdmrc and save it somewhere in case it does not work.

Open krunner (ALT + F2) enter
kdesu kate /etc/X11/kdm/kdmrc
enter root password
Then in editor, add to section:

Code:

[X-:*-Core]
AllowNullPasswd=true
AllowShutdown=All
NoPassEnable=false
NoPassUsers=
ServerArgsLocal=-nolisten tcp
ServerCmd=/usr/bin/X

TerminateServer=true

save.

Probably better error logs would be kdm or xsession since it is a display problem.  Looking further into it to see if I can find some similar problem that has been solved (read somewhere it could have to do with hibernation or screensaver).  If it works, post it to the bug report. 

[zvacet]

Tnx Lisa! That was it.Now it is working thanks to you. 
I think I should close or remove bug report.

[Lisa]

wow!  That's is good that it worked! 
I'd keep the bug report open as this editing of the file is only a fix and still needs to be addressed by the folks at Pardus-Anka team.  It is probably an upstream bug that affects Intel chips, but they need to know about it and hopefully fix it in future releases.

Ugh, we had an ice storm so I was slow in responding to you.  All melted now and power is back on. 

[zvacet]

You really think that I should keep bug open?Because I close it thinking this is solution for my ( and other people) problem.

[Lisa]

Hi zvacet, sorry to get to you so late.
Of course, you can do as you think best. 
You did what I would do, as adding 'solved' to this thread.  But if it were me, the official bug report should stay open and include how you temporarily fixed problem by describing how you edited a file.  I call it a 'fix' and not solved.  Solved is when you don't have to edit or change a file, but instead and update from the developers or a new release solves the problem without you having to edit a file.  That way the problem is solved for anyone that has your similar hardware, too.
See you at the pisilinux forum 
Lisa Marie