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 458354 - crash in Text Editor: trying to view the photo...
crash in Text Editor: trying to view the photo...
Status: RESOLVED DUPLICATE of bug 354046
Product: gedit
Classification: Applications
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-19 17:03 UTC by redcatsharlequin
Modified: 2007-07-20 16:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description redcatsharlequin 2007-07-19 17:03:04 UTC 
Version: 2.15.9

What were you doing when the application crashed?
trying to view the photos taken with my Chocolate phone.


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.20-1.2944.fc6 #1 SMP Tue Apr 10 17:46:00 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 1115025408 vsize: 1115025408 resident: 24072192 share: 13209600 rss: 24072192 rss_rlim: -1
CPU usage: start_time: 1184864681 rtime: 26 utime: 20 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 46912496412416 (LWP 28664)]
(no debugging symbols found)
0x00000035d940d935 in waitpid () from /lib64/libpthread.so.0

+ Trace 149139

Thread 1 (Thread 46912496412416 (LWP 28664))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_utf8_validate
    from /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 /lib64/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #10 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
report junk?? Fun Art Tools with Kid Pix(R) SmartDownload for only $15
(evolution:27802): e-data-server-DEBUG: Loading categories from "/home/sasha/.evolution/categories.xml"
(evolution:27802): e-data-server-DEBUG: Loaded 29 categories
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 (Save as JP)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1405675 (my_pix); these messages lack timestamps and therefore suck.
** (bug-buddy:28666): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 palfrey 2007-07-20 16:37:09 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 ***