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.
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
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
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
Public bug reported:
Binary package hint: nautilus
nautilus won't start in ubuntu 8.04 after installing updates on May 30th
(installed version of nautilus package: 1:2.22.3-0ubuntu2)
[EMAIL PROTECTED]:~$ nautilus
seahorse nautilus module initialized
Initializing nautilus-share extension
**
** Ee
