closing, that's not a nautilus bug but t he code being stricter about
incorrect configurations
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notifica
correct the new version doesn't ignore the configuration errors
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Isn't it possible that previous version of libeel tolerated such things
as value 0 instead of false in gconf, and the newest one does not? Then
the upgrade would only reveal an incorrect change in configuration.
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.
Re-upgraded libeel2-2 to 2.22.2 and disable trash icon as described in
thread, and nautilus works now too. I can't help but to wonder if the
libeel2-2 caused a problem or if reverting was a lucky (on my part)
unrelated work around, but after all it was an eel error reported in the
terminal, which w
I have been fighting this one for days too, what I eventually did was
revert libeel2-2 2.22.2 back to libeel2-2 2.22.1, and of course nautilus
would run, I thought I would mention the libeel2-2 because that update
may have caused the problem. I am going to go back up to the 2.22.2 and
see if changi
Setting trash_icon_name key to type string and a value of "Trash", and
checking the boolean trash_icon_visible has got it fixed for me.
As to Sebastien's comment that the bug came about through incorrect user
changes, I'd only add that, like Monika, I hadn't altered any of the
values. I upgraded f
those seem incorrect user changes, not sure that's worth complicating
the code and maybe introducing not bug to try to handle cases where
users set incorrect configuration
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug no
Was having this same problem on one machine, but not another.
In my case, the one having the trouble had the trash icon displayed and
apps/nautilus/desktop/trash_icon_name set to be an integer value of 0.
Unsetting the trash_icon_name key fixed the problem. I didn't try with
any other icons (I onl
Sebastien Bacher wrote:
> how do you change the preference? toggling the boolean value in gconf-
> editor has no reason to change the type and create an issue
>
>
I'm sorry --- I don't understand. From a terminal, I ran gconf-editor. I
found apps|nautilus|desktop and clicked the trash_icon_vis
ah, your screenshot show that the trash_icon_name is set to 0 which is
likely creating the issue, how did you change this one? does unsetting
this key fixes the issue?
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notifi
how do you change the preference? toggling the boolean value in gconf-
editor has no reason to change the type and create an issue
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ub
I'm not clear on how to do that. I did find that if I remove the
checkmark before trash_icon_visible, Nautilus runs, but, of course, I
have no trash icon. If I return the checkmark, nautilus stops. Could you
tell me please how I should go about implementing your suggestion? In
small words, please (
did you try unsetting the gconf value mentionned before using gconf-
editor?
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
As Monika reported, an entirely new user with administrative properties
can run nautilus correctly. The error is in some configuration of my
main account.
stew
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification
My backtrace attached
** Attachment added: "gdb-nautilus.txt"
http://launchpadlibrarian.net/14978978/gdb-nautilus.txt
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs
I've got the same problem. The error is:
[EMAIL PROTECTED]:/var/log$ nautilus
seahorse nautilus module initialized
Initializing nautilus-share extension
**
** Eel:ERROR:(eel-preferences.c:116):preferences_gconf_value_get_string:
assertion failed: (value->type == GCONF_VALUE_STRING)
Aborted
Runni
yes, it fixes the problem!
I didn't know how to change type - in "Modify" the type was visible, but
not possible to change - so I just hit "Clean key" and it changed to
boolean. I did the same to the next key volumes_visible, it also had
value 0 and it seemed to me it should be boolean. Now nautil
does changing it to a boolean value using gconf-editor fix the issue?
did you change this value before and how?
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is
the value I get is 0
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
could you run "gconftool-2 --get
/apps/nautilus/desktop/trash_icon_visible" and copy the value to a
comment?
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Ok, so I created a completely new user and run nautilus. It works.
Apparently it is configuration of my user. Can you give me any help with
restoring correct configuration? I didn't make any changes directly
before the crash so I have no idea what change is the problem & can't
undo it.
--
nautilu
This is my backtrace
** Attachment added: "backtrace"
http://launchpadlibrarian.net/14877312/gdb-nautilus.txt
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which
It seems I have a similar problem: http://pastebin.ubuntu.com/15980/.
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
what locale do you use? do you get the issue using a different user?
seems that your users as a wrong configuration value stored somewhere
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a memb
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned)
I encounter the same problem after the updates..
--
nautilus won't start unless with sudo because of eel:error
https://bugs.launchpad.net/bugs/236249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
26 matches
Mail list logo
