bugMyPaint - Bugs: bug #20687, old config dir ~/.mypaint causes...

Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #20687: old config dir ~/.mypaint causes incomprehensible errors

Submitted by:  Cedric sodhi <manday>
Submitted on:  Sat Mar 30 21:29:08 2013  
Severity: 3 - NormalPriority: 5 - Normal
Status: Works For MePrivacy: Public
Assigned to: NoneOpen/Closed: Closed
Release: git masterPlanned Release: None
Operating System: 

Tue Jun 24 21:21:18 2014, comment #5:

This bug tracker will shortly be moving to Github. As part of this process, we are reviewing old bug reports on gna.org.

This bug was marked as "Ready for Test" or "Works for Me" some time ago, but was still classified as Open and no feedback has been submitted since then. I am therefore assuming that the problem has been fixed to everyone's satisfaction (or was't reproducible by anybody else).

If you believe that this bug still affects the most recent git master of MyPaint (and thus the next release), please feel free to open a new issue on
Github about it. Our new issue trackers are:


Andrew Chadwick <achadwick>
Project Administrator
Thu Apr 4 15:27:26 2013, comment #4:

This is probably something other than Cairo support given the error relates to treeview models - perhaps your recompile fixed that too - but it would be tricky to nail down, I think. Closing WORKSFORME given that the problem has gone away with a more complete GObject-system/Python build.

Andrew Chadwick <achadwick>
Project Administrator
Mon Apr 1 13:23:32 2013, comment #3:

After I corrected the PyGObject build to be compiled against cairo, as described in #20688, the error does no longer occur.

Cedric sodhi <manday>
Mon Apr 1 08:20:37 2013, comment #2:

Gentoo Linux, git master. I still have the offending config dir, I attached it as a tar'ed file (it's a .mypaint directory, so you probably won't see it without ls -a after extracting). I'll bisect as soon as I can.

Cedric sodhi <manday>
Sun Mar 31 22:02:28 2013, comment #1:

Cool error. Zero's certainly in the range mentioned...

What operating system and version are you using, please?

Unfortunately I can't reproduce this one out unless I know what was in your old config and user data files. Did you change any settings or do anything which might provoke a bug with the display of the layer visibility state on startup?

If you have backups and know git well, please use bisect to identify the troublesome commit. I don't think it's to do with the migration to XDG config dirs.

Andrew Chadwick <achadwick>
Project Administrator
Sat Mar 30 21:29:08 2013, original submission:

Only after I deleted the old ~/.mypaint, mypaint would start. Before that, it would give me strange errors like

Traceback (most recent call last):
File "/home/manday/local/share/mypaint/gui/layerswindow.py", line 353, in layer_visible_datafunc
layer = model.get_value(tree_iter, 0)
File "/usr/lib64/python2.7/site-packages/gi/types.py", line 43, in function
return info.invoke(*args, **kwargs)
ValueError: 0 not in range -2147483648 to 2147483647

Cedric sodhi <manday>


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by achadwick (Posted a comment)
  • -unavailable- added by manday (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Error: not logged in



    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue Jun 24 21:21:18 2014achadwickOpen/ClosedOpen=>Closed
    Thu Apr 4 15:27:26 2013achadwickStatusNeed Info=>Works For Me
    Sun Mar 31 22:02:28 2013achadwickSeverity4 - Important=>3 - Normal
      StatusNone=>Need Info
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup