Atip wrote:Contrary of what I said yesterday /dev/audio copied from Slint-32
does not survive a reboot or halt. I just tried it 4 times. /dev/audio*
is absent after a reboot or halt..
I have posted about this issue on the orca-list mailing list and received this answer
. As, yes, saytime is an oldie (last release is ten years old) it probably expects to land in a system configured for OSS. So, look at the comments in /etc/rc.d/rc.alsa-oss if you still want to use it or (maybe easier) try to find a modern replacement. I don't think that be a Slint specific issue. In any case check that /etc/rc.d/rc.pulseaudio be non executable as you don't need a speaking desktop.
Further: I have set inittab to runlevel 3. After login I type "startx"
and up comes my default desktop fluxbox.
If I set inittab to runlevel 4 and reboot I get now an ugly looking login
window, not the previous nice blue Slint, I enter my PW login and up comes
blackbox. This new login window does not give any choice for any other desktop.
/etc/X11/xinit/@xinitrc points to xinitrc.fluxbox.
I replaced lxdm by lightdm by default as display manager recently because it can speak.
1) You can get back lxdm, just commenting out the lines that start lightdm in /etc/rc.d/rc.4
2) The login window of lightdm does allow choosing the desktop session, there is an icon for than on the top right of the screen.
3) You can theme lightdm runnning as root lightdm-gtk-greeter-settings
4) Yes, in RC2 the selection of the desktop session in lightdm is wrong if you use xwmconfig. This has been fixed now. To get the fixes do this:
a) If not already done edit /etc/slapt-get/slapt-getrc replacing in the slint source slint-14.2 with slint-testing
b) run as root:
Code: Select all
dotnew or dotnew-gtk
After that lightdm should honor the settings that you will make using xwmconfig as regular user.
To set the desktop session in lightdm (but only in lightdm, that's its limitation), I have also added a small script called session-chooser
. Run it as regular user.
The recent changes and their rationale are as usual in the ChangeLog
, after 09 November 2017.