Description of problem: slim: Could not create lock file: /var/run/slim/slim.lock Version-Release number of selected component (if applicable): 1.3.2-4.fc15 How reproducible: Steps to Reproduce: 1.yum install slim 2.add DISPLAYMANAGER=/usr/bin/slim-dynwm to /etc/sysconfig/desktop 3.restart Actual results: slim: Could not create lock file: /var/run/slim/slim.lock Expected results: Additional info: the same bug as https://bugzilla.redhat.com/show_bug.cgi?id=573284 (CLOSED) SELinux is disabled on my system
Same here. Although there are other issues with slim, this particular bug can be circumvented by changing '/var/run/slim' to '/var/run' in slim.conf. (Same must be done for slim.auth btw.)
slim-1.3.2-6.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/slim-1.3.2-6.fc15
Package slim-1.3.2-6.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing slim-1.3.2-6.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/slim-1.3.2-6.fc15 then log in and leave karma (feedback).
It does not start after a reboot, although I can start it through the command line (slim-dynwm) which was not possible before. [root@nostradamus ~]# yum list installed slim Loaded plugins: langpacks, presto, refresh-packagekit Installed Packages slim.x86_64 1.3.2-6.fc15 @updates-testing [root@nostradamus ~]# cat /etc/sysconfig/desktop PREFERRED=/usr/bin/startxfce4 DISPLAYMANAGER=/usr/bin/slim-dynwm
The /var/run issue disappeared so strictly speaking, this particular issue is solved. However, I too don't get slim start automatically (but from cmd, like Filipe said). Also, there are issues with the available sessions: slim will always start gnome-session and even alter slim.conf! (Should I file that separately?)
slim-1.3.2-6.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.