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 373606 - crash in GTetrinet: gestartet
crash in GTetrinet: gestartet
Status: RESOLVED DUPLICATE of bug 361961
Product: gtetrinet
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gtetrinet Hackers
Gtetrinet Hackers
Depends on:
Blocks:
 
 
Reported: 2006-11-10 23:38 UTC by basti.ruehl
Modified: 2006-11-12 01:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description basti.ruehl 2006-11-10 23:38:12 UTC 
What were you doing when the application crashed?
gestartet


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

Memory status: size: 19103744 vsize: 0 resident: 19103744 share: 0 rss: 6889472 rss_rlim: 0
CPU usage: start_time: 1163201871 rtime: 0 utime: 8 stime: 0 cutime:7 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

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

(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 -1225348928 (LWP 13334)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 85217

Thread 1 (Thread -1225348928 (LWP 13334))

  • #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 gnome_config_assemble_vector
    from /usr/lib/libgnome-2.so.0
  • #5 gnome_config_has_section_
    from /usr/lib/libgnome-2.so.0
  • #6 gnome_config_clean_file_
    from /usr/lib/libgnome-2.so.0
  • #7 gnome_config_get_string_with_default_
    from /usr/lib/libgnome-2.so.0
  • #8 ??
  • #9 _IO_stdin_used
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-11-12 01:57:36 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 361961 ***