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 404405 - crash in Text Editor: I was in a gedit File Sa...
crash in Text Editor: I was in a gedit File Sa...
Status: RESOLVED DUPLICATE of bug 375496
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-04 21:16 UTC by TerryByrne1963
Modified: 2007-02-05 16:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description TerryByrne1963 2007-02-04 21:16:59 UTC
Version: 2.15.9

What were you doing when the application crashed?
I was in a gedit File Save dialog box. From within the dialog box I attempted to move one of the folders displayed in the dialog box by selecting the folder then hitting Ctrl-x on the keyboard to 'cut' the folder, intending then to use Ctrl-v to 'paste' the folder and its contents elsewhere. 


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 84705280 vsize: 0 resident: 84705280 share: 0 rss: 27095040 rss_rlim: 0
CPU usage: start_time: 1170623036 rtime: 0 utime: 213 stime: 0 cutime:199 cstime: 0 timeout: 14 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 -1208128960 (LWP 6078)]
(no debugging symbols found)
0x00707402 in __kernel_vsyscall ()

Thread 1 (Thread -1208128960 (LWP 6078))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 gtk_file_info_render_icon
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_file_chooser_button_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #8 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #9 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #10 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Error: Duplicate name found: replacing MatchId 66695 with 84535
Error: Duplicate name found: replacing MatchId 66695 with 84536
Error: Duplicate name found: replacing MatchId 66695 with 84537
Error: Duplicate name found: replacing MatchId 66695 with 84538
Error: Duplicate name found: replacing MatchId 66695 with 84539
Error: Duplicate name found: replacing MatchId 66695 with 84541
Error: Duplicate name found: replacing MatchId 66695 with 84543
Error: Duplicate name found: replacing MatchId 66695 with 84544
Error: Duplicate name found: replacing MatchId 66695 with 84545
Error: Duplicate name found: replacing MatchId 66695 with 84546
Error: Duplicate name found: replacing MatchId 66695 with 84547
Error: Duplicate name found: replacing MatchId 66695 with 84548
Error: Duplicate name found: replacing MatchId 66695 with 84549
** (bug-buddy:6128): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 palfrey 2007-02-05 16:44:25 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 375496 ***