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 437749 - crash in Computer: clicked on a directory i...
crash in Computer: clicked on a directory i...
Status: RESOLVED DUPLICATE of bug 349551
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-11 19:50 UTC by Gavin Flower
Modified: 2007-05-12 01:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Gavin Flower 2007-05-11 19:50:23 UTC
Version: 2.16.2

What were you doing when the application crashed?
clicked on a directory in a newly opened directory window (nautilus)


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.2948.fc6 #1 SMP Fri Apr 27 19:18:54 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 573739008 vsize: 573739008 resident: 35454976 share: 15736832 rss: 35454976 rss_rlim: 0
CPU usage: start_time: 1178650733 rtime: 7227 utime: 6015 stime: 1212 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496441296 (LWP 19868)]
0x0000003fb3c0d96f in __libc_waitpid (pid=22420, stat_loc=0x7fff8de9d6fc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 1 (Thread 46912496441296 (LWP 19868))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 gtk_ui_manager_remove_ui
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 nautilus_ui_unmerge_ui
    at nautilus-ui-utilities.c line 38
  • #5 real_update_menus
    at fm-directory-view.c line 4637
  • #6 fm_directory_view_update_menus
    at fm-directory-view.c line 9360
  • #7 update_menus_timeout_callback
    at fm-directory-view.c line 2928
  • #8 g_timeout_dispatch
    at gmain.c line 3422
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #10 g_main_context_iterate
    at gmain.c line 2677
  • #11 IA__g_main_loop_run
    at gmain.c line 2881
  • #12 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 main
    at nautilus-main.c line 389
  • #14 __libc_start_main
    at libc-start.c line 231
  • #15 _start
0x0000003fb3c0d96f	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);


----------- .xsession-errors (313764 sec old) ---------------------
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 8368973 error_code 1 request_code 0 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 8368976 error_code 1 request_code 0 minor_code 0)
  (Note t
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-05-12 01:24:23 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 349551 ***