Huh? According to that error message, modesetting.upper() returned
'MODE_DiSABLED'. with lowercase 'i'. No idea how this is possible.
Anyway, try to remove the file settings.json in the folder
~/.mypaint/. Also, MyPaint is no fun with pressure disabled. Try
enabling it again in the preferences
GTK2 did not support tablet hotplugging, which I suspect may be the
cause of this problem. Please try to reproduce with MyPaint git, which
uses GTK3, which should support this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's wrongly detecting your mouse as a tablet.
Go to the preferences, and set Mode to Disabled. This will disable
graphic tablets (pressure sensitivity) in general, and thus also prevent
from accidentally putting your mouse into screen mode (which is what
screws up GTK).
The problem should
To narrow the problem down, you could check if xidump also shows the
increase in sinsitivity (so you know whether it comes from MyPaint/GTK
or from Xorg/Kernel), see here for some ideas what to check:
http://wiki.mypaint.info/Development/Debugging_Tablet_Issues
That said, relative mode has always
MyPaint bugreport: https://gna.org/bugs/?18188 (Status: Wont Fix)
** Bug watch added: gna.org #18188
http://gna.org/bugs/?18188
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835387
Title:
Hover
The message stands for out of memory while trying to save the file.
MyPaint was trying to create a 3824 x 11072 (127MB) pixbuf, which would
be the size of your image. If your image should have been much smaller,
you probably made some accidental faint strokes while zoomed out. Check
whether your
Yes we assume 50% pressure but you can change that in the preferences
(modify the pressure curve, so it outputs something else at 50% input).
--
Drawing with non-pressure capable devices
https://bugs.launchpad.net/bugs/544704
You received this bug notification because you are a member of Ubuntu
Xev does not call XkbSetDetectableAutoRepeat(), thus it cannot be used
to test whether XkbSetDetectableAutoRepeat() does get rid of the extra
key up events or not.
--
problem with key repeat, extra key up events
https://bugs.launchpad.net/bugs/403339
You received this bug notification because
You cannot reproduce this bug with xev. The output you describe is a
little bit strange, but correct behaviour. The program has to
explicitely change the behaviour through an API call.
--
problem with key repeat, extra key up events
https://bugs.launchpad.net/bugs/403339
You received this bug
This is the xorg bugreport:
https://bugs.freedesktop.org/show_bug.cgi?id=22515
** Bug watch added: freedesktop.org Bugzilla #22515
https://bugs.freedesktop.org/show_bug.cgi?id=22515
--
problem with key repeat, extra key up events
https://bugs.launchpad.net/bugs/403339
You received this bug
10 matches
Mail list logo
