Bug 408792 – crash in Iagno:

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 408792 - crash in Iagno:


Summary:	crash in Iagno:


Status:	RESOLVED DUPLICATE of bug 364936

Product:	gnome-games-superseded
Classification:	Deprecated
Component:	iagno
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Games maintainers
QA Contact:	GNOME Games maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-17 02:28 UTC by zuvirie
Modified:	2007-02-17 10:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description zuvirie 2007-02-17 02:28:02 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 31084544 vsize: 0 resident: 31084544 share: 0 rss: 12419072 rss_rlim: 0
CPU usage: start_time: 1171679245 rtime: 0 utime: 34 stime: 0 cutime:31 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/games/iagno'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225038160 (LWP 4700)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 111405

Thread 1 (Thread -1225038160 (LWP 4700))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 __assert_fail
from /lib/tls/i686/cmov/libc.so.6
#8 avahi_client_free
from /usr/lib/libavahi-client.so.3
#9 ??
#10 ??
#0 __kernel_vsyscall

Comment 1 Damien Durand 2007-02-17 10:15:56 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 364936 ***