FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Kubuntu User

 
 
LinkBack Thread Tools
 
Old 08-16-2008, 02:08 PM
"D. R. Evans"
 
Default HELP! Urgent! Unable to log in

Trying to log in, instead of seeing my nice shiny KDE desktop after
the login screen, I just get a blue screen and then after a while I
get the following:

----

There was an error setting up inter-process communication for KDE. The
message returned by the system was:

Could not read network connection list /home/n7dr/.DCOPserver_homebrew_0

Please check that the "dcopserver" program is running.

____

HELP! I have no idea what to do :-(

Doc

PS I also have no idea what I did that could have caused this.

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 08-16-2008, 02:20 PM
"D. R. Evans"
 
Default HELP! Urgent! Unable to log in

D. R. Evans said the following at 08/16/2008 08:08 AM :
> Trying to log in, instead of seeing my nice shiny KDE desktop after
> the login screen, I just get a blue screen and then after a while I
> get the following:

Fixed! I deleted the /tmp/kde-n7dr directory and now everything seems fine.

Not obvious, though, is it? I think that the problem was that there was a
lock file present (startkdeinitlock; goodness knows why it was there) in
/tmp/kde-n7dr. It would have been a lot easier if the error message had
explained that.

Doc

--
Web: http://www.sff.net/people/N7DR

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 08-16-2008, 02:30 PM
"Willy K. Hamra"
 
Default HELP! Urgent! Unable to log in

D. R. Evans wrote:
> D. R. Evans said the following at 08/16/2008 08:08 AM :
>> Trying to log in, instead of seeing my nice shiny KDE desktop after
>> the login screen, I just get a blue screen and then after a while I
>> get the following:
>
> Fixed! I deleted the /tmp/kde-n7dr directory and now everything seems fine.
>
> Not obvious, though, is it? I think that the problem was that there was a
> lock file present (startkdeinitlock; goodness knows why it was there) in
> /tmp/kde-n7dr. It would have been a lot easier if the error message had
> explained that.
>
> Doc
>
weird stuff like this can happen, a corrupt .bashrc once prevented me
from logging in graphically, and on another PC i was removing tons of
GUI programs to transform it to a server, one package refused to get
removed properly and caused me problems with APT because a file that
needs to be deleted wasn't there (already deleted), i had to touch a
file with the same path and name for it to work!
glad you solved the problem, at least you got pointed to the right
directory, and not told in the windoze way "an error happened somewhere
dangerous i can't tell you where since you're a noob, call our non
supportive staff on our sky-high priced phone number" :-P

--
Willy K. Hamra
Manager of Hamra Information Systems
Co. Manager of Zeina Computer & Billy Net
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 08-16-2008, 05:15 PM
Art Alexion
 
Default HELP! Urgent! Unable to log in

On Saturday 16 August 2008 10:08:12 D. R. Evans wrote:
> Trying to log in, instead of seeing my nice shiny KDE desktop after
> the login screen, I just get a blue screen and then after a while I
> get the following:
>
> ----
>
> There was an error setting up inter-process communication for KDE. The
> message returned by the system was:
>
> Could not read network connection list /home/n7dr/.DCOPserver_homebrew_0
>
> Please check that the "dcopserver" program is running.
>
> ____
>
> HELP! I have no idea what to do :-(
>
> Doc
>
> PS I also have no idea what I did that could have caused this.

I find the best way to diagnose problems like this is to go to another console
(Shift+Ctrl+F3), log in and run 'cat .xsession-errors' to see what the
culprit is. The .xsession-errors file is usually more helpful than the gui
popups.

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 

Thread Tools




All times are GMT. The time now is 07:11 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org