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 436025 - crash in Iagno: i AM NOT SHERE
crash in Iagno: i AM NOT SHERE
Status: RESOLVED DUPLICATE of bug 364936
Product: gnome-games-superseded
Classification: Deprecated
Component: iagno
unspecified
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-05 03:33 UTC by joyachan
Modified: 2007-05-06 18:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description joyachan 2007-05-05 03:33:13 UTC 
What were you doing when the application crashed?
i AM NOT SHERE 


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

Memory status: size: 35008512 vsize: 0 resident: 35008512 share: 0 rss: 12431360 rss_rlim: 0
CPU usage: start_time: 1178335900 rtime: 0 utime: 272 stime: 0 cutime:254 cstime: 0 timeout: 18 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 -1224890704 (LWP 10048)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 132485

Thread 1 (Thread -1224890704 (LWP 10048))

  • #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


Pedro Villavicencio





          2007-05-06 18:01:42 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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