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 481328 - crash in Dia Diagram Editor: Saving to a dia file in ...
crash in Dia Diagram Editor: Saving to a dia file in ...
Status: RESOLVED DUPLICATE of bug 131210
Product: dia
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-28 15:05 UTC by Johannes Buchner
Modified: 2007-09-28 18:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Johannes Buchner 2007-09-28 15:05:39 UTC 
Version: @VERSION@

What were you doing when the application crashed?
Saving to a dia file in a path with non-ascii characters. 


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.2 2007-08-30 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22 #2 SMP Thu Aug 2 21:12:47 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Tangoish-Industrial
Icon Theme: gartoon

Memory status: size: 213397504 vsize: 213397504 resident: 62320640 share: 23904256 rss: 62320640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190991116 rtime: 2195 utime: 2001 stime: 194 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/dia'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47555269937280 (LWP 4010)]
0x000000317aa0dad5 in waitpid () from /lib/libpthread.so.0

+ Trace 166201

Thread 1 (Thread 47555269937280 (LWP 4010))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strchr
    from /lib/libc.so.6
  • #4 strrchr
    from /lib/libc.so.6
  • #5 diagram_set_filename
  • #6 ??
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 ??
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (11 sec old) ---------------------
	at com.aelitis.net.upnp.impl.UPnPImpl.performSOAPRequest(UPnPImpl.java:588)
	at com.aelitis.net.upnp.impl.services.UPnPActionInvocationImpl.invoke(UPnPActionInvocationImpl.java:98)
	... 13 more
GTK Accessibility Module initialized
Bonobo accessibility support initialized
(dia:4010): Gtk-WARNING **: Unable to locate theme engine in module_path: "tangoish",
sys:1: PangoWarning: Invalid UTF-8 string passed to pango_layout_set_text()
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
(bug-buddy:4761): Gtk-WARNING **: Unable to locate theme engine in module_path: "tangoish",
--------------------------------------------------
Comment 1 Johannes Buchner 2007-09-28 17:11:40 UTC 
Dia is probably innocent ... see Bug 481358
Comment 2 Lars Clausen 2007-09-28 18:45:56 UTC 
We've had a bug like that in prior versions, but the latest version certainly has it licked, and this bug report is not from the latest version (0.96.1).

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