Magnus Vigerlöf <[EMAIL PROTECTED]> wrote:

> On Tuesday 10 April 2007 20:53, Olivier Lecarme wrote:
> [...]
> > I just remembered I had used before (when I had a 4x5 tablet) some tool
> > (probably wacomcpl) which inserted calls to xsetwacom into a start
> > script. And in fact, my ~/.xinitrc file contains these calls... but they
> > are all commented out! And this is the only place where xsetwacom is
> > mentioned in my initialisation scripts.
> 
> Yes, I see... But the file doesn't look as I expect a shell-script should 
> look 
> (they usually start with '#!<path-to-interpreter>')..

The tool that inserted the instructions put them in front of the
.xinitrc file, before the #! line.

> You might see some information in the log for the window-manager if these 
> commands for some reason does get executed.
> 
> > > If someone has been playing around on the account with an Intous 3 4x5
> > > tablet and used 'wacomcpl' it is fully possible that it has written
> > > commands to ~/.xinitrc that does the above, even if it seems that it
> > > should take one input device at a time and not one axis at a time.
> > > Anyway, could you check this to rule it out?
> >
> > Here is this .xinitrc file:
> >
> > # xsetwacom set stylus mode Absolute
> > # xsetwacom set eraser mode Absolute
> > # xsetwacom set stylus SpeedLevel 6
> > # xsetwacom set eraser SpeedLevel 6
> > # xsetwacom set stylus ClickForce 6
> > # xsetwacom set eraser ClickForce 6
> [...] lots skipped..
> 
> Wow :) Not that it *should* matter, but you might want to clean up this file.

It's done now.

> I also vaguely remember an earlier discussion on how to make these commands 
> resident in KDE/Gnome, and these commands *might* be in some other file as 
> well.. 'find . -type f | xargs grep xsetwacom' (may take time as it will go 
> through all the files from where you stand...)?
> 
> Another idea that you can try; Create a new user and log in into X, if there 
> are any commands that gets executed on your original account they shouldn't 
> be now (remember to reset X though)

I did it, and indeed this was OK for the new user. Thus I began
searching for a hidden initialisation file, and I found it indeed! It is
~/.wacom-config/startup.sh
What tool could have generated this stuff? Anyway, I removed the
offending file, and now all is OK.

Thanks a lot!

-- 


                        Olivier Lecarme

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Reply via email to