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 700116 - Nautilus crashes during owner change, when accessed as user
Nautilus crashes during owner change, when accessed as user
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Crashers
3.8.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-11 09:34 UTC by contact
Modified: 2021-06-18 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description contact 2013-05-11 09:34:44 UTC
Hi,

I am using ArchLinux, 3.8.11 kernel, gnome 3.8.1

When I try to run nautilus as user and set the permission on a file, it crashes (after setting the correct permission). I tried all solutions suggested in Archlinux forums. Nothing has worked for my problem. 

I tried to have a look at the coredump, but didn't get a clue how to look for info in that. i dumped the systemd coredump to another file.

How to reproduce:
1. sudo nautilus
2. get the properties of a file and then permission tab.
3. set the owner as one user and then set it back to original user.

Error:
[root@gpdarch ~]# nautilus /home/gpdas/

(nautilus:1135): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed

(nautilus:1135): Gtk-CRITICAL **: gtk_spinner_start: assertion `GTK_IS_SPINNER (spinner)' failed

(nautilus:1135): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
**
ERROR:nautilus-properties-window.c:1837:schedule_owner_change_timeout: assertion failed: (NAUTILUS_IS_FILE (file))
Aborted (core dumped)

I tried all below, but none of this has helped.
1. run sudo nautilus
2. gksu nautilus
3. after export DISPLAY=:0.0
4. logged in as root from gdm and tried files directly and from terminal.
5. installed gnome-polkit
6. confirmed in freshly installed arch linux and gnome3.8.
Comment 1 António Fernandes 2013-05-11 09:58:31 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? You can produce a stack trace from the coredump file using gdb. Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 contact 2013-05-11 15:23:47 UTC
The trace is below. Thanks in advance.


# gdb nautilus
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/nautilus...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/nautilus 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffea69c700 (LWP 16967)]

(nautilus:16961): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
[New Thread 0x7fffe3fff700 (LWP 16968)]
[New Thread 0x7fffe35f2700 (LWP 16969)]
[New Thread 0x7fffd8b44700 (LWP 16970)]
[New Thread 0x7fffce29f700 (LWP 16971)]
[New Thread 0x7fffcda9e700 (LWP 16972)]
[Thread 0x7fffcda9e700 (LWP 16972) exited]
[Thread 0x7fffce29f700 (LWP 16971) exited]
[New Thread 0x7fffce29f700 (LWP 16975)]
[New Thread 0x7fffcda9e700 (LWP 16976)]
[Thread 0x7fffcda9e700 (LWP 16976) exited]
[Thread 0x7fffe3fff700 (LWP 16968) exited]
[New Thread 0x7fffe3fff700 (LWP 16977)]
[Thread 0x7fffce29f700 (LWP 16975) exited]

(nautilus:16961): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed

(nautilus:16961): Gtk-CRITICAL **: gtk_spinner_start: assertion `GTK_IS_SPINNER (spinner)' failed

(nautilus:16961): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
**
ERROR:nautilus-properties-window.c:1837:schedule_owner_change_timeout: assertion failed: (NAUTILUS_IS_FILE (file))

Program received signal SIGABRT, Aborted.
0x00007ffff424f1c9 in raise () from /usr/lib/libc.so.6
(gdb) thread apply all bt


Comment 3 António Fernandes 2013-05-11 15:45:25 UTC
Thanks. 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 https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces for more information on how to do so on Arch Linux. The debug packages for glib, gtk+ and nautilus are likely to be enough.
Comment 4 contact 2013-05-11 18:37:42 UTC
Thanks for quick response. Here is the new trace. i installed debug version of glibc glib2 nautilus gtk3. I assume now there are no bissing bits. 


Thread 1 (Thread 0x7ffff7fa6900 (LWP 6712))

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #1 __GI_abort
    at abort.c line 90
  • #2 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #3 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #4 schedule_owner_change_timeout
    at nautilus-properties-window.c line 1837
  • #5 g_timeout_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_iterate.isra.22
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #9 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #10 main
    at nautilus-main.c line 104

Comment 5 António Fernandes 2013-05-11 20:46:05 UTC
Yes, it looks good now, thank you.
Comment 6 André Klapper 2021-06-18 15:15:41 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.