Bug 569031 - Slim fails to load any window manager
Summary: Slim fails to load any window manager
Keywords:
Status: CLOSED DUPLICATE of bug 573284
Alias: None
Product: Fedora
Classification: Fedora
Component: slim
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lorenzo Villani
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-27 17:54 UTC by Gareth John
Modified: 2010-03-30 09:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-30 09:25:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gareth John 2010-02-27 17:54:44 UTC
Description of problem:
Slim fails to execute session logs say

(==) Using config file: "/etc/X11/xorg.conf"
SELinux: Disabled on system, not enabling in X server
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
/usr/bin/xauth:  creating new authority file /home/gljohn/.Xauthority
Required key missing in Desktop Entry: Type at /usr/bin/update_slim_wmlist line$
Can't open /etc/slim.conf.new for writing: Permission denied at /usr/bin/update$
slim: only root can run this program

slim: waiting for X server to shut down

/usr/bin/xauth:  error in locking authority file /var/run/slim/slim.auth


Version-Release number of selected component (if applicable):
Latest as of 27/02/2010

How reproducible:
Install slim,
Setup using /etc/sysconfig/desktop
telinit 3
telinit 5
logon with slim

Comment 1 Lorenzo Villani 2010-03-12 11:45:10 UTC
(In reply to comment #0)
> Version-Release number of selected component (if applicable):
> Latest as of 27/02/2010

Please report the exact version of the package.

Comment 2 Lorenzo Villani 2010-03-30 09:20:12 UTC
If your slim version is 1.3.1-11 this bug is probably related to #573284

Comment 3 Lorenzo Villani 2010-03-30 09:25:39 UTC
Closing as duplicated. Feel free to reopen it if it's a totally different issue.

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


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