SLiM starts late

I want to use SLiM on my Arch install, but it seems to start too late. The virtual console with the usual login screen shows up for a few seconds, and then SLiM turns on afterward. When I shut the computer off, it goes back to virtual console and sits there on the login screen rather than showing the output of the shutdown process (although it does shut down correctly). SLiM itself works, since I can log in normally with it, but what can I do to make it appear at the right time? I have it start unbackgrounded fairly early in my daemons array, and I don't think I can go any earlier (unless it's put before netcfg's menu, which causes trouble because I can't select a wireless connection on startup).
Also, are there any disadvantages of using SLiM, versus the regular login at the virtual console, that I should be aware of?

https://wiki.archlinux.org/index.php/Di … mon_method here is written that it slim should be your last position in daemons. Did you try that?

Similar Messages

Midi events start late

I have noticed that some tracks that have midi events (VST's: RealRPC / Native Instruments) start late the first time that I play the project after opening it. The second time the project plans fine. This also happens when I bounce the project - some midi tracks start late.
My setup:
Logic 9 Express
DAW: Mac Mini Server (i7 quad core 2GHz / 8 MB RAM)
thanks in advance!

I'm trying to do a similar thing - I'm no expert but here's a few ideas:
First you need a Transmitter not a Receiver (confusingly) - it takes signals from your keyboard and Transmits them to other receivers in your program.
So you have a Device, d, a Transmitter, t, and use MidiSystem.getSequencer() to get a Sequencer, s.
You also need a Receiver for the sequencer, r.
add the Transmitter to the Device: t = d.getTransmitter();
add the Receiver to the Sequencer r = s.getReceiver();
connect them together: t.setReceiver(r);
The class where you want to do stuff with incoming midi signals should implement interface ControllerEventListener, i.e. it has a method controlChange(shortMessage event) which will be called when the sequencer receives midi via receiver r. Then, provided the above code is inside this class, you can add the event listener to the sequencer by:
listenedSoFar = s.addControllerEventListener(this, listened)
where listened is int[], a list of the kinds of messages you want to deal with. Elements can be between 0-127. Class ShortMessage has constatnts for these like ShortMessage.NOTE_ON etc. listenedSoFar is a list of all the kinds of messages this event listener responds to. If this is the first/only addControllerEventListener then listenedSoFar should equal listened.
I'm not sure this is exactly right as i'm in the middle of writing my program. If you've already cracked the problem then any tips you have would be appreciated.
George

Change infopackage scheduling rom Start later in background to immediate

Hi all,
I am having the following issue,
How to make permanent changes to Infopackage which are included in process
My Infopackage is containing the following setting in Schedule Tab
1. Start later in background (Immediately)
This infopackage is included in one process chain.
I am changing the above setting to Start Data Load Immediately and saving it, but when I am opening that infopackage again the setting is going back to Start later in background (Immediately) .
Please let me know how can I change the setting Start later in background (Immediately) to start Data load Immediately perfectly .
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/infopackage-load-immediate-691990
Please suggest.
Raj.

Hey Raj,
Once you save the job as run in background it cannot be saved back to the run immediate. But that doesnt mean that your job aint set to immediate.
Infact within the scheduling tab itself you will notice many tabs
namely
Immediate
Date/Time
Afterjob
afterevent
at operation mode etc
Now observe when you have set it as immediate, as soon as you click on the immediate tab Under Date/time you would see a small faded check box with Immediate start checked. This says that the job would start immediately if you are not going to use the other options.
Bottom line Start date load immediately and start later in background with
immediate start checkbox faded gives the same effect unless u are having other specifications set.
If you click on start with either of the options its going to start immediately. So dont worry abt the radio button being activated for background.
Thanks
Raj

Alarm starts later than the time set!!

I am still puzzled!
I have a 5800 Xpress Music since almost a year now, regularly updating it to the latest softwares and all, everything was working well until I reached version 30 and then 31 of the updates, somehow, and for some reason a very weird problem started to happen to me! The alarm clock starts off in a later time than the one I set! For example, I set the alarm to 7:00 am, but it starts at 7:05 am! Actually it could start any time from 1-5 minutes later than the actual time set!
Moreover, the snooze! When I snooze the alarm that is already late, it wouldn't snooze for the period I already set! like, I have set the snooze time to be 6 minutes, but, when I press snooze, it would snooze for 10 or even 15 minutes instead!
It's really so weird, I tried to turn off automatic time update, I have even changed the SIM card, but nothing is working! it seems a bug in the new software because everything was fine before!
Please if anyone could help me don't hesitate!

Not only that but timed profiles don't expire at the right time either and scheduled backups don't happen.
Right now there is no solution. The firmware is buggy and that's all there is to it.
We have to wait for an update. The phone was only released about a year ago so there's hope yet that Nokia will release further updates.
Was this post helpful? If so, please click on the white "Kudos!" star below. Thank you!

Early start & lates start date

Hi experts,
I want to change the early start & latest start date which are in grey mode of maintenance order operation direcly instead of changing the order basic start date .How can I do it? please through some clues.thanks

Hi,
Can you please try this.
1. IW32, go to Operations tab, Select Operation 10 (assuming you only have one operation)
2. Click the "Dates" button from the buttons at teh bottom
3. On the Restrictions tab, StartPoitn, Select "Must Start On", then specify the Date you want to start the work on the right
4. Save the Work Order
Regards,
Joey

How do I get a song to start AND THEN have the video start later?

I have been pulling my hair out trying to have a song play to a black screen for a few seconds, and then have the video fade in. I've tried beat markers, but it looks like the very start of an audio clip IS a beat marker so the video clip always align to the start of the song. DO I need to add a blank title or black footage?

yes add black footage or any footage and dial back the colors to none.

ICal's day won't start later than 12noon

my work day starts at 5pm and ends around midnight - iCal only has options for midnight to noon (a twelve hour period) which eliminates anyone who's day starts after noon.
any help?

Hi,
I had the same problem, not only with ical but also with adress book. I checked my Library/Fonts folder and found three font suitcase files with the following name:
ÇcÇeÇoä®í‡ó¨
After dragging all three to trash and trying to empty it I could only remove 2 of them because obviously one was "still in use", it is the one mentioned above. So I put it back. Since then both ical and adress book work normal again and do no longer disappear.
I have no idea which application installed that funny font, I did install MS Office 2004. Otherwise I run an i-Mac G-4 under Leopard 10.5.1
Maybe some of you can fix the problem this way. Greetings from Switzerland, Alex

DVD Image FIle Starts Late When Played

Hi All, I am not sure if I am posting this in the proper forum, so pardon my ignorance. However I seem to have a strange problem. I have a DVD that I made of myself teaching to some clients. I wanted to duplicate that DVD so it could be distributed. Here is what I did:
1. Insert DVD into drive
2. Open Disk Utility
3. Select DVD (not drive, but actual DVD)
4. Select New Image
5. Select DVD/CD Master from Context Menu
6. Hit Save and then it creates a CDR file
Next I wanted to create a duplicate of the DVD (CDR file), so I did the follwing:
1. Inserted blank DVD
2. Opened Disk Utility
3. Selected the CDR file
4. Selected Burn
The DVD mounts when finished and actually plays fine... There is one problem however, and that is starts at about 1 minute into the recoding and not at the start. Anyone know why?
Thanks in advance,
Mike
Message was edited by: Michael710

Thank you for that information... However, it exhibited the same problem on a DELL Latitude laptop. When I inserted the DVD it started playing somewhere around the 1 minute mark.

Spool request starts later than job

Hello ,
a job started at 21:00. The first statement of the ABAP was a write-Statement (Write sy-uzeit)
The corresponding spool was generated at 23:00. The job stopped at 2:00
Can someone explain this? I have no idea
Thanks and best regards
Simone

Have you set the job class to "A" ? i.e. high priority?
Regards,
Sumit

Exchange online defrag starts later than I expect!

My Exchange 2007 database online defrag is a bit strange.<o:p></o:p>
Every evening it never completes so it picks up from where it left off the day
before, which is not a problem.<o:p></o:p>
I have changed the schedule so that its opportunity window is from 01:00 am to 8 am<o:p></o:p>
However it does not start until 5.30 am, and then finishes promptly at 8 am!<o:p></o:p>
Is there something I am missing? <o:p></o:p>
<o:p> </o:p>
Thanks everyone!<o:p></o:p>

Hi Kevin,
When exchange online defrag process starts, it will generate new event log entries that help you examine the progress of the scheduled. I recommend you refer to these logs to verify if the schedule have been delayed.
For more details about Online Defragmentation, please refer to the following articles:
Exchange 2007 Online Maintenance Database Scanning (Part 1)
Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported
officially by Microsoft.
Best regards,
Niko Cheng
TechNet Community Support

My macbook pro will not start late 2008 green light on charger cable indicate battery is fully charged

my macbook pro late 2008 will not start

Reinstalling Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

It starts late ,far late than google chrome and when i open a pdf i cant read them

slow like a turtle

See [[Firefox keeps opening many tabs or windows]]
You can have infinite tabs opening if you have selected Firefox as the application to handle a file if you get an ''Open with'' download window.
Firefox should not be selected as the application to handle a file and you have to remove the action that is associated with that file type.
You can delete [http://kb.mozillazine.org/mimeTypes.rdf mimeTypes.rdf] in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Profile Folder] to reset all actions or set that action in Tools > Options > Applications to 'Always Ask'.
See http://kb.mozillazine.org/File_types_and_download_actions ("File handling in Firefox 3 and SeaMonkey 2" and "Reset Download Actions")

SLiM only starts twice then exits to tty1

Hi... i've installed arch yesterday following this guide https://wiki.archlinux.org/index.php/Beginners'_Guide i
After that i started to set up a new desktop using openbox and slim.
Basically everything works fine... except that after exiting openbox 2 times slim won't start and i end at tty1.
systemctl status slim... after boot
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: active (running) since Di 2013-03-19 19:05:10 CET; 1min 10s ago
Main PID: 241 (slim)
CGroup: name=systemd:/system/slim.service
└─264 /usr/bin/X -nolisten tcp vt07 -auth /var/run/slim.auth
‣ 241 /usr/bin/slim -nodaemon
... after 1st "openbox logout"
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: active (running) since Di 2013-03-19 19:05:10 CET; 1min 50s ago
Main PID: 241 (slim)
CGroup: name=systemd:/system/slim.service
...after 2nt logout on tty1
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Di 2013-03-19 19:07:04 CET; 23s ago
Process: 241 ExecStart=/usr/bin/slim -nodaemon (code=exited, status=1/FAILURE)
/var/log/slim.log
slim: waiting for X server to begin accepting connections.
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
systemctl list-units
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys...t_misc.automount loaded active running Arbitrary Executable File Formats File System Automount Point
sys-devi...-sda-sda1.device loaded active plugged IC25N080ATMR04-0
sys-devi...-sda-sda2.device loaded active plugged IC25N080ATMR04-0
sys-devi...-sda-sda3.device loaded active plugged IC25N080ATMR04-0
sys-devi...-sda-sda4.device loaded active plugged IC25N080ATMR04-0
sys-devi...block-sda.device loaded active plugged IC25N080ATMR04-0
sys-devi...block-sr0.device loaded active plugged _NEC_DVD+_-RW_ND-6500A
sys-devi...und-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:02.7/sound/card0
sys-devi...et-enp0s4.device loaded active plugged /sys/devices/pci0000:00/0000:00:04.0/net/enp0s4
sys-devi...et-wlp2s0.device loaded active plugged /sys/devices/pci0000:00/0000:00:09.0/0000:02:00.0/net/wlp2s0
sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-subs...es-enp0s4.device loaded active plugged /sys/subsystem/net/devices/enp0s4
sys-subs...es-wlp2s0.device loaded active plugged /sys/subsystem/net/devices/wlp2s0
-.mount loaded active mounted /
boot.mount loaded active mounted /boot
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
home.mount loaded active mounted /home
proc-sys...infmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System
sys-kernel-config.mount loaded active mounted Configuration File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted Temporary Directory
systemd-...ord-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...ssword-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
net-auto-wireless.service loaded active running Provides automatic netcfg wireless connection
ntpd.service loaded active running Network Time Service
slim.service loaded failed failed SLiM Simple Login Manager
systemd-binfmt.service loaded active exited Set Up Additional Binary Formats
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...es-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-...sessions.service loaded active exited Permit User Sessions
systemd-...le-setup.service loaded active exited Setup Virtual Console
dbus.socket loaded active running D-Bus System Message Bus Socket
dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
lvmetad.socket loaded active listening LVM2 metadata daemon socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...d-control.socket loaded active listening udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
dev-sda2.swap loaded active active /dev/sda2
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-...iles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
/etc/slim.conf
# 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 vt07
# 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
# 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
# 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 (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
# sessions xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window 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
lockfile /var/run/lock/slim.lock
# Log file
logfile /var/log/slim.log
When i run "systemctl start slim" on tty1 slim starts again and after exiting openbox twice i'm back on tty1.
...But when i run "slim" on tty1 slim starts and i can exit openbox as often as i want.
Any ideas ?
Edit:
Running /usr/bin/slim from tty1 gives me this logfile.
/var/log/slim.log
slim: waiting for X server to begin accepting connections.
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
Somehow the second "slim: waiting for X server to shut down" does not happen when running "systemctl start slim"
Last edited by Synth (2013-03-19 19:39:10)

Ok, I was able to workaround parts of the bug:
I changed slim.conf and and set daemon = true (so slim runs as a daemon). Furthermore changed the slim.service file for systemd:
[Service]
Type = forking
PIDFile = /var/lock/slim.lock
ExecStart=/usr/bin/slim
Now I can log in and out as often as I want. Seems to work. However, nm-applet only shows up in odd numbers of logins:
1st login --> nm-applet is shown
2nd login --> nm-applet is not shown (but running --> htop)
3rd login --> nm-applet is shown
4th login --> nm-applet is not shown (but running --> htop)
...and so on...
I search the web, it seems to be a problem with dbus and the order how the services get started. Don't know if that is true...any ideas from anyone?

Starting Keyboard Driver with SLiM?

I use a Logitech G510 keyboard. When Arch starts up, the drivers for it to support the LCD and Macros starts as well. (from here)
If I log out to SLiM however, the drivers stop completely, rendiner the keyboard unusable to until I reseat it, at which point in time just the normal Arch keyboard drivers take over (no LCD support, etc, but keyboard is usable.)
What I'm wondering is if there is a way to get either the standard drivers (not sure what they are) or these G15 drivers to start when SLiM starts?

alphaniner wrote:How are the drivers loaded now? Do they require X to be running? Is there some reason they can't be loaded automatically with modules-load.d?
As far as I can tell when I looked at the website for the driver, it -seems- to be a X app running in the background. That could be the issue, its window would get terminated whenever he logged out and slim resumed, and could cause the driver to lock up. I can do some research on their page, there might be a module for it he can load.
Could you tell me exactly how you are loading the driver?
Last edited by Multimoon (2013-08-12 14:11:35)

[SOLVED] Slim not starting Openbox

Hi :)
I've run a search through this forum and all, and I can't seem to solve my problem...
I've installed Arch on VirtualBox (so that I can try it out) and I installed Slim and Openbox.
The problem is that when I log in, the screen flickers, and Slim comes back up, as if openbox wasn't executed at all
Any of you guys has this setup? (slim and ob)
If so, please tell me how you configured it...
Thanks in advance
Last edited by pedro-kun (2007-08-05 18:09:56)

Here it is:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin:/usr/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# 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
# 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
# Start in daemon mode. Valid values: yes | no
# Note that this can overridden by the command line
# option "-d"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
# sessions xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# 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 pedro
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
i got rid of the %session bit, and the sessions, because i'm gonna use only openbox. Either way, i don't think doing that has anything to do with the problem, because i think i tried it with the default slim.conf and it didn't work anyway.

SLiM starts late

Similar Messages

Maybe you are looking for