Bug 262401 - DCOPserver doesn't works
Summary: DCOPserver doesn't works
Status: RESOLVED DUPLICATE of bug 177480
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: KDE (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-09 08:43 UTC by Perret Florian
Modified: 2007-05-27 19:54 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
hosts (690 bytes, text/ascii)
2007-04-17 11:21 UTC, Perret Florian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Perret Florian 2007-04-09 08:43:30 UTC
Sometimes I cannot log at all. I have to wait about 30 minutes to
make SUSE to start again. My computer is unusable all this time ! 

With GNOME this bug makes a loop to the log screen. 
And with KDE I have this message : 

"could not read network list /home/flo/.DCOPserver_linux-rh1lh_0
Check if DCOPserver works"
Comment 1 Dirk Mueller 2007-04-16 14:52:23 UTC
is your network working? how is it set up? is your hostname listed in /etc/hosts?
Comment 2 Perret Florian 2007-04-17 11:20:37 UTC
Usually network works (both LAN and wifi).But when I have this bug, I can't log at all so I cannot see if network works.

I have two network card :
- LAN has a specific setup (IP, DNS...)
- wifi works with dhcp,
Comment 3 Perret Florian 2007-04-17 11:21:58 UTC
Created attachment 131707 [details]
hosts
Comment 4 Lubos Lunak 2007-05-18 12:46:17 UTC
You should be still able to switch to text mode and log in there, or switch the login type to failsafe and log that way.
When the problem occurs, log in and check
- if all relevant partitions have enough free space
- if network works
- if "ping localhost", "ping linux-kdj3.site" and "ping linux-kdj3" work
- what does running "hostname" do
Comment 5 Perret Florian 2007-05-27 19:54:50 UTC

*** This bug has been marked as a duplicate of bug 177480 ***