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 611276 - dia: python warning when exporting a png from a dia file using png-libart
dia: python warning when exporting a png from a dia file using png-libart
Status: RESOLVED OBSOLETE
Product: dia
Classification: Other
Component: exports
0.97.x
Other Linux
: Normal minor
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-27 12:28 UTC by Roland Stigge
Modified: 2019-03-20 11:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example dia file (2.30 KB, application/x-dia-diagram)
2010-02-27 12:28 UTC, Roland Stigge
Details

Description Roland Stigge 2010-02-27 12:28:42 UTC
Created attachment 154825 [details]
Example dia file

Hi,

I'm attaching an example dia file that with:

$ unset DISPLAY
$ dia -t png-libart --export=ldap-is-a-tree.png ldap-is-a-tree.dia

results in:

========================================================================
/usr/lib/pymodules/python2.5/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
ldap-is-a-tree.dia --> ldap-is-a-tree.png
========================================================================

The result looks fine, though.

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538309

I can't reproduce the segfault just by unsetting DISPLAY but get the above warning.

Thanks for considering.

bye,
  Roland
Comment 1 Hans Breuer 2010-07-29 20:13:08 UTC
The crash is probably a duplicate of bug #603004, the warning should be harmless.
Comment 2 GNOME Infrastructure Team 2019-03-20 11:48:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dia/issues/278.