LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   How to revert slackware-current to 19.Sep.2013 ? (http://www.linuxquestions.org/questions/slackware-14/how-to-revert-slackware-current-to-19-sep-2013-a-4175480774/)

guanx 10-14-2013 05:38 PM

How to revert slackware-current to 19.Sep.2013 ?
 
I know the 20.Sep.2013 update broke KDE/Qt keyboard input but I no longer have the earlier snapshot. Is there a way to revert to the 19.Sep.2013 snapshot of slackware-current?

Thanks!

volkerdi 10-14-2013 05:57 PM

Could it be due to the xinput update? You could try downgrading to the previous version (which is in Slackware 14.0) to see if it makes a difference.

So far, no other reports of this issue have landed here.

Skaperen 10-15-2013 01:10 AM

You could try my ISO image from Sept 19:

http://slackware.slashusr.com/isos/s...t-20130919.iso
[md5: 0f2198940bbfdd14426f07adf4b28984]

There are others in that directory, too. I also have some even older ones archived I could upload if you really need it. And I have older packages from the distro archived (I use an incremental backup tool for mirroring) if you'd prefer to build your own ISO.

guanx 10-15-2013 04:37 AM

Thank you both! I've downgraded xinput and will report later to see if the problem is solved.

guanx 10-17-2013 07:17 AM

Thanks both again! Now I think this is a problem like "If I buy vanilla icecream the car won't start".

There is something wrong if I start scim automatically when KDE starts by putting scim into "$HOME/.kde/Autostart" as suggested by "/etc/profile.d/scim.sh". Even if I add a delay before the scim command the problem still shows up.

Now I have a fairly effective (though very ugly) workaround -- Do not start scim on KDE start up, but start KDE and then launch a GTK application such as Firefox, Pidgin or whatever. Then the GTK application will bring up scim. After that, all GTK and Qt / KDE applications work well.


All times are GMT -5. The time now is 07:47 AM.