[Bug 305415] Using on-screen keyboard makes the system freeze

2012-08-21 Thread Maurice de la Ferté
https://bugs.kde.org/show_bug.cgi?id=305415 --- Comment #8 from Maurice de la Ferté maurice.fe...@basyskom.com --- Could you try a 'rm -rf path of mounted archos rootfs' before executing the 'tar' deploying command? Maybe your system is affected by some artefacts of an older installation. I'm

[Bug 305415] Using on-screen keyboard makes the system freeze

2012-08-21 Thread jean.cayron
https://bugs.kde.org/show_bug.cgi?id=305415 --- Comment #7 from jean.cay...@gmail.com --- Created attachment 73341 -- https://bugs.kde.org/attachment.cgi?id=73341action=edit My kwinactiverc [Compositing] AnimationSpeed=3 Backend=XRender DisableChecks=true Enabled=true GLDirect=true

Re: qml screenlocker, again

2012-08-21 Thread Marco Martin
On Monday 20 August 2012, Martin Gräßlin wrote: the only big issue (and is indeed, quite big) is that is possible to kill the window with ctrl+alt+esc key combo. any idea how to solve this? nasty, that should not be. Solution is to grab the keyboard, but that should actually be done by

Re: Re: qml screenlocker, again

2012-08-21 Thread Martin Gräßlin
On Tuesday 21 August 2012 13:43:56 Marco Martin wrote: Three issues come to my mind: * log-in with locked screen (needs adjustment in startkde) hmm, any reason in particular this would be needed or wanted? * it's a feature currently present * it allows to not stop at KDM - very useful for

Re: qml screenlocker, again

2012-08-21 Thread Marco Martin
On Tuesday 21 August 2012, Alex Fiestas wrote: On Tuesday 21 August 2012 17:51:55 Martin Gräßlin wrote: should still work, IIRC I adjusted it. Personally I would like to have it as the default, but it's too slow in loading. Then we should try to improve this somehow (Maybe in randa?) I'd

Re: Re: qml screenlocker, again

2012-08-21 Thread Martin Gräßlin
On Tuesday 21 August 2012 19:20:08 Marco Martin wrote: On Tuesday 21 August 2012, Martin Gräßlin wrote: i think the timeout is still (partly) governed by the screensaver timeout, so without that kcm wouldn't make much sense, should be uniquely powermanagement governed timeouts?