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 353836 - [strchr nautilus_modul_initialize] using nautilus as regular user. right click on protected file to "open as administrator" - nautilus crashes
[strchr nautilus_modul_initialize] using nautilus as regular user. right clic...
Status: RESOLVED NOTGNOME
Product: nautilus
Classification: Core
Component: general
2.16.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 406666 408533 411161 414944 418976 420622 420645 425233 427746 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-01 12:46 UTC by lee
Modified: 2007-11-30 20:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description lee 2006-09-01 12:45:58 UTC
Distribution: Debian testing/unstable
Package: nautilus
Severity: Normal
Version: GNOME2.14.3 2.14.3
Gnome-Distributor: Debian
Synopsis: using nautilus as regular user. right click on protected file to "open as administrator" - nautilus crashes
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.14.3
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

using nautilus as regular user. right click on protected file to "open
as administrator" - nautilus crashes

Steps to reproduce the crash:
1. open nautilus as file manager as regular user 
2. right-click on protected file and choose "open as administrator"
3. instant crash

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225200896 (LWP 21328)]
[New Thread -1227138128 (LWP 21331)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225200896 (LWP 21328))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-gksu.so
  • #6 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 nautilus_menu_item_activate
    from /usr/lib/libnautilus-extension.so.1
  • #12 fm_directory_view_bump_zoom_level
  • #13 nautilus_file_is_directory
  • #14 nautilus_clipboard_monitor_emit_changed
  • #15 nautilus_directory_async_state_changed
  • #16 nautilus_directory_async_state_changed
  • #17 nautilus_undo_transaction_unregister_object
  • #18 nautilus_file_get_volume
  • #19 nautilus_file_get_volume
  • #20 POA_Nautilus_MetafileMonitor__init
  • #21 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 _gtk_action_emit_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #39 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #42 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #43 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #47 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #48 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #50 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 POA_Nautilus_MetafileMonitor__init
  • #52 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #53 ??
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-09-01 12:46 -------


Unknown version 2.14.3 in product nautilus.  Setting version to "2.14.x".

Comment 1 Christian Kirbach 2006-09-01 19:58:18 UTC
unique trace

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 lee 2006-09-04 14:51:01 UTC
hello

I am sorry - I downloaded nautilus-dbg and the problem has gone away. Files open perfectly.

I am not used to bug tracking systems so am not sure how or whether to close this correctly.

Apologies.

Lee
Comment 3 Christian Kirbach 2006-09-05 14:06:05 UTC
thank you for reporting back. perhaps the debugging package has a newer nautilus release that already has a fix integrated.

Closing this report. Feel free to reopen it any time you can reproduce the crash.
Comment 4 Christian Kirbach 2007-02-11 12:29:49 UTC
duplicates, reopeneing
Comment 5 Christian Kirbach 2007-02-11 12:29:58 UTC
*** Bug 406666 has been marked as a duplicate of this bug. ***
Comment 6 Christian Kirbach 2007-02-11 12:30:24 UTC
last dup is 2.16.1

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 7 Christian Kirbach 2007-02-16 22:11:27 UTC
*** Bug 408533 has been marked as a duplicate of this bug. ***
Comment 8 palfrey 2007-02-23 14:13:12 UTC
*** Bug 411161 has been marked as a duplicate of this bug. ***
Comment 9 Christian Kirbach 2007-03-05 20:17:38 UTC
*** Bug 414944 has been marked as a duplicate of this bug. ***
Comment 10 Christian Kirbach 2007-03-17 12:14:23 UTC
*** Bug 418976 has been marked as a duplicate of this bug. ***
Comment 11 Christian Kirbach 2007-03-21 19:07:53 UTC
*** Bug 420622 has been marked as a duplicate of this bug. ***
Comment 12 Christian Kirbach 2007-03-21 19:08:56 UTC
last duplicate has a trace with at leaset some symbols

  • #3 <signal handler called>
  • #4 strchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-gksu.so
  • #6 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 nautilus_menu_item_activate
    at nautilus-menu-item.c line 85
  • #12 extension_action_slow_mime_types_ready_callback
    at fm-directory-view.c line 4827
  • #13 file_list_file_ready_callback
    at nautilus-file.c line 5949
  • #14 ready_callback_call
    at nautilus-directory-async.c line 1237
  • #15 nautilus_directory_async_state_changed
    at nautilus-directory-async.c line 1849
  • #16 nautilus_directory_call_when_ready_internal
    at nautilus-directory-async.c line 1319
  • #17 vfs_file_call_when_ready
    at nautilus-vfs-file.c line 66
  • #18 nautilus_file_call_when_ready
    at nautilus-file.c line 5548
  • #19 nautilus_file_list_call_when_ready
    at nautilus-file.c line 5982
  • #20 extension_action_callback
    at fm-directory-view.c line 4843

Comment 13 Christian Kirbach 2007-03-21 19:34:08 UTC
*** Bug 420645 has been marked as a duplicate of this bug. ***
Comment 14 palfrey 2007-04-07 14:57:35 UTC
*** Bug 425233 has been marked as a duplicate of this bug. ***
Comment 15 palfrey 2007-04-09 14:02:18 UTC
*** Bug 427746 has been marked as a duplicate of this bug. ***
Comment 16 André Klapper 2007-11-30 20:05:14 UTC
crash in libnautilus-gksu, that's not GNOME.