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 411483 - crash in Text Editor: initngの設定ミスだと思います
crash in Text Editor: initngの設定ミスだと思います
Status: RESOLVED DUPLICATE of bug 360792
Product: gedit
Classification: Applications
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-24 06:14 UTC by linenanasi
Modified: 2007-02-24 15:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description linenanasi 2007-02-24 06:14:53 UTC 
Version: 2.15.9

What were you doing when the application crashed?
initngの設定ミスだと思います


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 92856320 vsize: 0 resident: 92856320 share: 0 rss: 23023616 rss_rlim: 0
CPU usage: start_time: 1172295159 rtime: 0 utime: 142 stime: 0 cutime:129 cstime: 0 timeout: 13 it_real_value: 0 frequency: 0

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

(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 -1209050560 (LWP 2973)]
(no debugging symbols found)
0x006ee402 in __kernel_vsyscall ()

+ Trace 113434

Thread 1 (Thread -1209050560 (LWP 2973))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 bacon_message_connection_new
  • #6 _gedit_app_get_window_in_workspace
  • #7 _start
  • #0 __kernel_vsyscall 






Comment 1


Paolo Borelli





          2007-02-24 15:58:49 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 360792 ***