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 452456 - crash in Text Editor: tried to open index.html...
crash in Text Editor: tried to open index.html...
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-06-30 04:49 UTC by baykelper
Modified: 2007-06-30 15:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description baykelper 2007-06-30 04:49:43 UTC 
Version: 2.15.9

What were you doing when the application crashed?
tried to open index.html file from CD,  initally wouldn't open as html, so I tried opening by right clicking and choosing text-editor (gedit)


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.2962.fc6 #1 SMP Tue Jun 19 18:24:12 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 61087744 vsize: 0 resident: 61087744 share: 0 rss: 32587776 rss_rlim: 0
CPU usage: start_time: 1183178748 rtime: 0 utime: 31 stime: 0 cutime:25 cstime: 0 timeout: 6 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 -1208681728 (LWP 9065)]
(no debugging symbols found)
0x00f50402 in __kernel_vsyscall ()

+ Trace 144777

Thread 1 (Thread -1208681728 (LWP 9065))

  • #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 g_utf8_validate
    from /lib/libglib-2.0.so.0
  • #5 gedit_convert_from_utf8
  • #6 gedit_convert_to_utf8
  • #7 gedit_document_new
  • #8 gedit_document_new
  • #9 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** (eggcups:2984): WARNING **: IPP request failed with status 1030
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
** (nautilus:2976): WARNING **: No description found for mime type "x-special/socket" (file is "mapping-gtbradley"), please tell the gnome-vfs mailing list.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3f specified for 0x1234b3f ().
closing
closing
gnome-mount 0.5
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
** (bug-buddy:9067): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Bruno Boaventura 2007-06-30 15:03:41 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 ***