Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
SLiM doesn't start
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Mrhnhrm
n00b
n00b


Joined: 29 Jun 2008
Posts: 39
Location: Krasnoyarsk city, Russian Federation

PostPosted: Mon Dec 21, 2009 4:24 am    Post subject: SLiM doesn't start Reply with quote

I've tried installing SLiM, but it doesn't want to start - all I get is a boring black screen on VT7. I can switch to other VTs, however. And I know that X starts alright by startx command. Here's slim.log:
Code:
/usr/bin/xauth:  creating new authority file /var/run/slim.auth


X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.31.01-std131-amd64 x86_64
Current Operating System: Linux tux 2.6.31-zen9exp1 #1 ZEN SMP PREEMPT Fri Dec 18 00:18:20 KRAT 2009 x86_64
Build Date: 17 December 2009  03:02:58PM
 
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 21 10:19:19 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "freetype" (module does not exist, 0)
(EE) Failed to load module "dri2" (module does not exist, 0)
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
No protocol specified

slim: waiting for X server to begin accepting connections.
No protocol specified
..
No protocol specified
..
No protocol specified
..
No protocol specified
..

(edit) *** and the same two lines repeat a hunderd more times *** (/edit)

No protocol specified
..
No protocol specified
..
Giving up.
slim: unable to connect to X server

slim: waiting for X server to shut down



I'd be very thankful for some input on this issue.
_________________
If there isn't an explanation of a problem described above, well... computers just hate me.
Registered Linux user # 523263
Back to top
View user's profile Send private message
Nerevar
l33t
l33t


Joined: 31 May 2008
Posts: 712

PostPosted: Mon Dec 21, 2009 8:15 am    Post subject: Reply with quote

Apparently, there are multiple ways to fix it...
http://forums.gentoo.org/viewtopic-t-803474.html
Back to top
View user's profile Send private message
Mrhnhrm
n00b
n00b


Joined: 29 Jun 2008
Posts: 39
Location: Krasnoyarsk city, Russian Federation

PostPosted: Tue Dec 22, 2009 6:41 am    Post subject: Reply with quote

Um.. maybe I was a little unclear with problem formulation. I think that the thread you're referencing is dealing with the situation when SLIM is somewhat misconfigured, but manages to start at least, which is not exactly my case. For me SLIM doesn't even reach the point where it should ask for a login/password. I've tried playing around with settings described in that thread, however, but it still doesn't help, and I keep staring at a boring black screen when xdm service is started.

Another interesting fact that I've discovered is that SLIM stops loading before it gets the chance to ask for a login/password only if xdm service is started at boot time (runlevel default). But if I skip xdm at boot time and attempt to run xdm later from command line, SLIM starts successfully. Strange, eh?
_________________
If there isn't an explanation of a problem described above, well... computers just hate me.
Registered Linux user # 523263
Back to top
View user's profile Send private message
Nerevar
l33t
l33t


Joined: 31 May 2008
Posts: 712

PostPosted: Tue Dec 22, 2009 1:10 pm    Post subject: Reply with quote

Mrhnhrm wrote:
Another interesting fact that I've discovered is that SLIM stops loading before it gets the chance to ask for a login/password only if xdm service is started at boot time (runlevel default). But if I skip xdm at boot time and attempt to run xdm later from command line, SLIM starts successfully. Strange, eh?

Maybe a required kernel module is getting loaded too late? Take a look at your full /var/log/Xorg.0.log.
Back to top
View user's profile Send private message
dasPaul
n00b
n00b


Joined: 14 Feb 2012
Posts: 49
Location: VirgoSC/LocalGroup/MilkyWay/Solarsystem/Earth/Europe/Germany/Saxony/Dresden

PostPosted: Wed Jan 23, 2013 7:47 pm    Post subject: Re: SLiM doesn't start Reply with quote

Mrhnhrm wrote:
I've tried installing SLiM, but it doesn't want to start - all I get is a boring black screen on VT7. I can switch to other VTs, however. And I know that X starts alright by startx command. ......


I run into exactly the same problem. Slim seems to start with with a black screen. I change to vt1 to see whats going on and slim.log tells same "no protocol specified....giving up".

# cat /etc/slim.conf
Code:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path        /bin:/usr/bin:/usr/local/bin
default_xserver     /usr/bin/X
xserver_arguments   -nolisten tcp -br -deferglyphs 16

# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/xauth

# Xauth file for server
authfile           /var/run/slim.auth


# Activate numlock when slim starts. Valid values: on|off
numlock             on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/bash -login ~/.xinitrc %session
#login_cmd           exec /bin/bash -login /usr/share/slim/Xsession %session

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd      some command
# sessionstop_cmd       some command
sessionstart_cmd        /usr/bin/sessreg -a -l :0.0 %user
sessionstop_cmd         /usr/bin/sessreg -d -l :0.0 %user

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
daemon  yes

# Available sessions:
# The current chosen session name replaces %session in the login_cmd
# above, so your login command can handle different sessions.
# If no session is chosen (via F1), %session will be an empty string.
# see the xinitrc.sample file shipped with slim sources
#sessions            xfce4,icewm,wmaker,blackbox
# Alternatively, read available sessions from a directory:
sessiondir           /etc/X11/Sessions

# Executed when pressing F11 (requires media-gfx/imagemagick for import)
# Alternative is media-gfx/scrot. See Gentoo bug 252241 for more info.
screenshot_cmd      import -window root /slim.png
#screenshot_cmd      scrot /root/slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host

# Session message. Prepended to the session name when pressing F1
# session_msg         Session:

# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user        simone

# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password      no

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          no


# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme       default

# Lock file, /etc/init.d/xdm expects slim.pid
lockfile            /var/run/slim.pid

# Log file
logfile             /var/log/slim.log


#cat .xinitrc
Code:
exec enlightenment_start


# cat /var/log/slim.log
Code:
/usr/bin/xauth:  file /var/run/slim.auth does not exist


slim: waiting for X server to begin accepting connections
X.Org X Server 1.13.1
Release Date: 2012-12-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.7.3-gentoo i686 Gentoo
Current Operating System: Linux c1 3.7.3-gentoo #2 SMP Wed Jan 23 14:41:09 CET 2013 i686
Kernel command line: ntp syslog x44 rootsize=1500m usbhid.mousepoll=2 sqi=l32b17 vga=792 rootp=/dev/sdb1
Build Date: 23 January 2013  12:12:02PM
 
Current version of pixman: 0.28.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 23 19:24:14 2013
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
.
No protocol specified
..
No protocol specified
..
No protocol specified
..
No protocol specified
..

..Giving up.
slim: unable to connect to X server

slim: waiting for X server to shut downServer terminated successfully (0). Closing log file.


EDIT:

After that xdm is in status "crashed". Stoping and starting xdm results in an working slim :? .
Back to top
View user's profile Send private message
dasPaul
n00b
n00b


Joined: 14 Feb 2012
Posts: 49
Location: VirgoSC/LocalGroup/MilkyWay/Solarsystem/Earth/Europe/Germany/Saxony/Dresden

PostPosted: Thu Jan 24, 2013 10:53 am    Post subject: Reply with quote

the oddness continues, after I gave up slim and installed lightdm. Same problem here. On boot xdm tries to start but failed (status crashed).

error in /var/log/lightdm/x-0-greeter.log

Code:

No protocol specified

(lightdm-gtk-greeter:3804): Gtk-WARNING **: cannot open display: :0


Restarting /etc/init.d/xdm results in an fully functional lightdm.
Back to top
View user's profile Send private message
dasPaul
n00b
n00b


Joined: 14 Feb 2012
Posts: 49
Location: VirgoSC/LocalGroup/MilkyWay/Solarsystem/Earth/Europe/Germany/Saxony/Dresden

PostPosted: Fri Jan 25, 2013 3:12 pm    Post subject: Reply with quote

problem solved by:
cleaning out garbage initscripts, removing xorg.conf, reemerged world. I still dont know what exactly caused the error.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum