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 392884 - crash in Dia Diagram Editor: Starting it!
crash in Dia Diagram Editor: Starting it!
Status: RESOLVED INCOMPLETE
Product: dia
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-04 21:05 UTC by Vladimir Lushnikov
Modified: 2007-02-13 20:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Vladimir Lushnikov 2007-01-04 21:05:12 UTC
Version: @VERSION@

What were you doing when the application crashed?
Starting it!


Distribution: Gentoo Base System version 1.12.8
Gnome Release: 2.16.2 2007-01-02 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 44007424 vsize: 0 resident: 44007424 share: 0 rss: 31825920 rss_rlim: 0
CPU usage: start_time: 1167944687 rtime: 0 utime: 65 stime: 0 cutime:59 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

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 -1226528576 (LWP 21995)]
0xb7ef9410 in ?? ()

Thread 1 (Thread -1226528576 (LWP 21995))

  • #0 ??
  • #1 ??
  • #2 ??
  • #0 ??

Comment 1 Hans Breuer 2007-01-05 17:44:24 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Bruno Boaventura 2007-02-13 20:33:06 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!