Bug 130111 - KDE does not start
Summary: KDE does not start
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-17 08:55 UTC by Doncho Gunchev
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-17 11:11:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
startx's output (2.40 KB, text/plain)
2004-08-17 08:57 UTC, Doncho Gunchev
no flags Details

Description Doncho Gunchev 2004-08-17 08:55:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040809

Description of problem:
    With kdebase-3.3.0-0.1.rc2 'switchdesk kde; startx' fails.

Version-Release number of selected component (if applicable):
kdebase-3.3.0-0.1.rc2

How reproducible:
Always

Steps to Reproduce:
1. Install FC3t1 and update kdebase to 3.3.0-0.1.rc2
2. login in text console
3. switchdesk kde; startx
    

Actual Results:  KSMServer: Error listening for connections: Cannot
establish any listening sockets
KSMServer: Aborting.
startkde: Shutting down...


Expected Results:  normal start

Additional info:  I'll attach startx's output (startx 2>&1 | tee
startx-kde.log)

Comment 1 Doncho Gunchev 2004-08-17 08:57:33 UTC
Created attachment 102782 [details]
startx's output

generated with startx 2>&1 | tee startx-kde.log

Comment 2 Than Ngo 2004-08-17 10:19:28 UTC
i have installed kde 3.3.0rc2 on my local machine. It works fine here.

could you please check whether you have updated kde 3.3.0 rc2 packages
in rawhide.

You should try to start KDE with a new user. Does it still appear?



Comment 3 Doncho Gunchev 2004-08-17 11:11:24 UTC
    I 'yum update'-d my system fully this morning. Starting with new
user works - configuration problem. I'll have to setup my KDE again
:(. Sorry, I shuld have tryed this first - it happend before. Closing.


Note You need to log in before you can comment on or make changes to this bug.