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 412553 - crash in gedit: Again... your great app...
crash in gedit: Again... your great app...
Status: RESOLVED DUPLICATE of bug 354046
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-27 07:24 UTC by borko.boyanov
Modified: 2007-02-27 11:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description borko.boyanov 2007-02-27 07:24:15 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Again... 
your great application FAILED to produce results: 
QUITING normaly after it sees that the Data it has been fed (they are like animals you know) is a B4D 0xf00d ... And this data here was an .exe...

What if this combines with a BUG in Wine api and 'produce' some 'usefull' stuff there? hm? trash my linux because of a Windows creature?
sese?


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 460337152 vsize: 460337152 resident: 10596352 share: 16216064 rss: 26812416 rss_rlim: 445296640
CPU usage: start_time: 1172560872 rtime: 51 utime: 44 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/gedit'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47886812633872 (LWP 4696)]
(no debugging symbols found)
0x00002b8d83118c25 in waitpid () from /lib64/libpthread.so.0

+ Trace 114262

Thread 1 (Thread 47886812633872 (LWP 4696))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_utf8_validate
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #4 gedit_convert_from_utf8
  • #5 gedit_convert_to_utf8
  • #6 gedit_document_new
  • #7 gedit_document_new
  • #8 g_source_get_current_time
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #10 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #12 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #13 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Susana





          2007-02-27 11:15:27 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 354046 ***