After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 737441 - Cannot save anymore file changes (error in misc.py)
Cannot save anymore file changes (error in misc.py)
Status: RESOLVED DUPLICATE of bug 737350
Product: meld
Classification: Other
Component: filediff
3.11.x
Other Linux
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2014-09-26 14:59 UTC by valere.monseur
Modified: 2014-09-29 21:03 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
traceback (2.92 KB, application/octet-stream)
2014-09-26 15:05 UTC, valere.monseur 		Details

Description valere.monseur 2014-09-26 14:59:27 UTC 
When making some changes in a file diff, I try to save (or save as) and no save is performed. There is a traceback displayed listing the problem (see attachment).
Comment 1 valere.monseur 2014-09-26 15:01:05 UTC 
(Quick & dirty) workaround I've applied at this time is changing the code in misc.py and commenting these 2 lines:

d.props.image.set_alignment(0.5, 0)
d.props.image.set_padding(12, 12)

At least, I'm allowed to save the changes.
Not sure what's the impact of not having these 2 lines (seems to be only UI related -> looks ok temporarily).
Comment 2 valere.monseur 2014-09-26 15:05:41 UTC 
Created attachment 287169 [details]
traceback
Comment 3 Kai Willadsen 2014-09-26 19:49:50 UTC 
What version of Meld are you running, and what are your versions of GTK+ and PyGObject?
Comment 4 valere.monseur 2014-09-27 06:07:13 UTC 
meld 3.11.4
gtk+ 3.12.2
pygobject 3.12.2 (called python2-gobject in archlinux)
Comment 5 Kai Willadsen 2014-09-29 21:03:24 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 737350 ***