You are not logged in.
Hi,
When I try to run nautilus as user and set the permission on a file, it crashes (after setting the correct permission). My problem sounds very similar to https://bbs.archlinux.org/viewtopic.php?id=162090 , but I do not have any problem starting nautilus. I tried all solutions suggested there. Nothing has worked for my problem. I am using GNOME3.8. I know I can do it on terminal, but if this is reproducable for others it can be an upstream bug. ![]()
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
Offline
Offline
thanks sistematico, but that didn't work.
tried that for both user and root. No changes. still crashes in changing the owner back. user -> root -> user. in fact the root -> user change causes the crash, the other one works perfectly.
removing ~/.local it worked for changing default applications, if the user (root) is the owner of the file. otherwise it crashes with the same error.
there is a message in a dialog, but it goes away in a fraction of second. i could just say it said something about the ownership.
Last edited by gpdas (2013-05-04 10:19:47)
Offline
I can confirm this happens in fresh install as well, ie fresh arch install and direct gnome 3.8 install.
Offline
reported upstream https://bugzilla.gnome.org/show_bug.cgi?id=700116
Offline