We will call this update Slackware 13.1 RC1, Now RC2
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That's the point. With RC1 you had better start 'scim' before any 'X' application that's why the reference to use autostart in KDE. How about trying to 'simply add the line "scim -d" to your ~/.xprofile file.
This gives you a Desktop Environment independent way of starting scim.' as stated for a XDM. Even if you don't use runlevel 4 this should make certain that 'scim' is independent of KDE.
I just want to generally advertise to anyone who uses DRBD as an LVM PV to not upgrade to -rc1 or 13.1 if it's released as is. Somewhere between DRBD and LVM is a serious data-corrupting bug and I'm currently working on trying to find the culprit.
Slackware 13.1 RC1 works great on my 2 laptop and 1 desktop pc. but i think i have some problem about Xsession in /etc/kde/kdm on my laptop. compared to xinitrc.kde, i think Xsession on kdm has missed ck-launch-session. i have to add it manualy so i can have consolekit registered session.
did it just happened on my slackware or somebody has similar problem? FYI i'm always doing slackware upgrade from slackware 13 to current (13.1 RC1), not clean install.
That's the point. With RC1 you had better start 'scim' before any 'X' application that's why the reference to use autostart in KDE. How about trying to 'simply add the line "scim -d" to your ~/.xprofile file.
This gives you a Desktop Environment independent way of starting scim.' as stated for a XDM. Even if you don't use runlevel 4 this should make certain that 'scim' is independent of KDE.
Thank you very much onebuck for your patience . SCIM now works with Firefox (no more screen freezing) if I use:
Quote:
simply add the line "scim -d" to your ~/.xprofile file.
But as mentioned in an earlier post, SCIM didn't work for me in Firefox when I used:
Quote:
In KDE, you can add a shell script to the ~/.kde/Autostart folder that runs the command "scim -d"
Maybe it would be good to only mention the .xprofile option in CHANGES_AND_HINTS.TXT
Look forward to another reliable and stable Slackware release.
Last year S13 was released on the day of my birthday (Thanks Pat for a great b-day present). This year it might be someone else's birthday. Whose birthday is still in May?
Last year S13 was released on the day of my birthday (Thanks Pat for a great b-day present). This year it might be someone else's birthday. Whose birthday is still in May?
Mine is tomorrow, the 20th!
Mind you I stuck with Debian Lenny for a while because it was released on Valentine's Day!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.