[Bug 195180] Re: user-mountable (nfs) filesystems are not showing up in Computer view of nautilus
Peter, what does that have to do with GVFS not reporting NFS mounts to Nautilus? Please file a separate bug for your unrelated issue. -- user-mountable (nfs) filesystems are not showing up in Computer view of nautilus https://bugs.launchpad.net/bugs/195180 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
affects /distros/ubuntu/softbeep -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
affects /distros/ubuntu/softbeep -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
I don't know how to reassign a bug to a new package, so someone else will have to do it for me. -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] UGH
I figured out what was different on the to machines, and boy is it lame. On the non-working machine, I had added /usr/lib/softbeep/libsoftbeep.so to /etc/ld.so.preload. Apparently, this package is not as clever as it should be at differentiating between beeps and non-beeps. -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
Ok, here's my workaround. This results in output identical to the output of the non-patched gconf on you working system. It probably just masks the real problem, though. So what changed to cause local_schema->long_desc to be defined but point to an empty string? Who knows? The schema files are the same on the working and non-working system. All the packages that are installed on both systems are at the same version (except ssh, which I patched to include sftp logging). ** Attachment added: "Workaround: don't write if local_schema->long_desc is an empty string" http://librarian.launchpad.net/5323666/patch-gconf2-empty-long_desc-fputs-failure.diff -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
Ok... the line that causes gconftool to bail out is a call to fputs on
line 4030 of markup-tree.c (in the function write_local_schema_info).
Here's the surrounding chunk of code:
if (write_descs && local_schema->long_desc)
{
if (fprintf (f, "%s", whitespace2) < 0)
goto out;
s = g_markup_escape_text (local_schema->long_desc, -1);
if (fputs (s, f) < 0)
{
g_free (s);
goto out;
}
g_free (s);
if (fputs ("\n", f) < 0)
goto out;
}
What's happening is that local_schema->long_desc is an empty string, and fputs
apparently returns EOF if you pass it an empty string.
So now the question becomes what changed that caused this code to get
run even if long_desc is an empty string?
--
update-schemas: Error writing file
"/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
https://launchpad.net/bugs/74699
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
The error message is generated by the gconf source file backends/markup- tree.c in the save_tree_with_locale function on line 4480. That code assumes that if there was an error, (i.e. write_failed is true) it was caused by something that sets errno. However, there are plenty of ways for an error to occur that don't result in errno getting set. The write_entry function (called by save_tree_with_locale) calls a lot of fprintf and fputs, and if any of those fail, it returns a negative value (which causes save_tree_with_locale to set write_failed to true. Unless I'm mistaken, fprintf and fputs don't set errno. (Or at least the manpage doesn't mention setting errno.) So the "Inappropriate ioctl for device" error is totally bogus. Incidentally, the "" element is written on line 4025 (in write_local_schema_info, which is called by write_entry). Maybe that fprintf is returning a negative value? Or, maybe the next thing (printing the long_desc itself, with fputs) is failing? I'm planning to add some debugging statements around there when I have some time. But right now, time for lunch. -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
More experimentation: I again copied my /var/lib/gconf directory from my other (non-broken) Edgy box, and am doing some experiments with that. One test is to unregister and then register a single schema. I did this with evince-thumbnailer-djvu.schemas: # With virgin gconf dir from spider, unregister single schema: [EMAIL PROTECTED]:~# gconf-schemas --unregister evince-thumbnailer-djvu.schemas # So far so good, now register that schema again: [EMAIL PROTECTED]:~# gconf-schemas --register evince-thumbnailer-djvu.schemas Failed to write "/var/lib/gconf/defaults/%gconf-tree.xml": Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists Error syncing config data: Failed to write some configuration data to disk At this point, %gconf-tree.xml.new DOES exist, and consists of the first 30,839 lines of %gconf-tree.xml. The last identical line is: In %gconf-tree.xml, this is immediately followed by: but in %gconf-tree.xml.new, we get this: evince-thumbnailer -s %s %u %o And that's the end of the file. There isn't even a closing newline. Digging deeper, I found out the exact command that gconf-schemas was running, and executed it manually: # With virgin gconf dir from spider, uninstall single schema: [EMAIL PROTECTED]:~# HOME=/tmp/gconf--3PMME GCONF_CONFIG_SOURCE=xml:readwrite:/var/lib/gconf/defaults gconftool-2 --makefile-uninstall-rule /usr/share/gconf/schemas/evince-thumbnailer-djvu.schemas Resolved address "xml:readwrite:/var/lib/gconf/defaults" to a writable configuration source at position 0 Attached schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' to key `/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' Uninstalled schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' from locale `C' Attached schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' to key `/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' Uninstalled schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' from locale `C' # So far so good, now install that schema again: [EMAIL PROTECTED]:~# HOME=/tmp/gconf--3PMME GCONF_CONFIG_SOURCE=xml:readwrite:/var/lib/gconf/defaults gconftool-2 --makefile-install-rule /usr/share/gconf/schemas/evince-thumbnailer-djvu.schemas Resolved address "xml:readwrite:/var/lib/gconf/defaults" to a writable configuration source at position 0 Attached schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' to key `/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' Installed schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' for locale `C' Attached schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' to key `/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' Installed schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' for locale `C' Failed to write "/var/lib/gconf/defaults/%gconf-tree.xml": Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": Inappropriate ioctl for device Error syncing config data: Failed to write some configuration data to disk This does exactly the same thing to the contents of /var/lib/gconf/defaults, but interestingly, the error message is different! When running gconf-schemas, the error was "File exists", but when running gconftool-2 directly, the error is "Inappropriate ioctl for device". So I redo the above test under strace (starting from the virgin gconf directory of course): # With virgin gconf dir from spider, uninstall single schema: [EMAIL PROTECTED]:~# HOME=/tmp/gconf--3PMME GCONF_CONFIG_SOURCE=xml:readwrite:/var/lib/gconf/defaults gconftool-2 --makefile-uninstall-rule /usr/share/gconf/schemas/evince-thumbnailer-djvu.schemas Resolved address "xml:readwrite:/var/lib/gconf/defaults" to a writable configuration source at position 0 Attached schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' to key `/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' Uninstalled schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/enable' from locale `C' Attached schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' to key `/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' Uninstalled schema `/schemas/desktop/gnome/thumbnailers/[EMAIL PROTECTED]/command' from locale `C' # So far so good, now install that schema again: [EMAIL PROTECTED]:~# HOME=/tmp/gconf--3PMME GCONF_CONFIG_SOURCE=xml:readwrite:/var/lib/gconf/defaults strace -o strace.out -e write=3 -e abbrev=none gconftool-2 --makefile-i
[Bug 74699] Re: update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
I remembered what initially caused the problem on my original installation. The first time I saw the error was after downgrading totem (and totem-gstreamer) from 1.4.3-0ubuntu1 to 1.4.1-0ubuntu4. I did this because the totem browser plugin wasn't available for 1.4.3-0ubuntu1. Re-upgrading totem and totem-gstreamer didn't fix it. Likewise, reversing the evince upgrade that caused it on this installation doesn't fix it either. -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 74699] update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists
Public bug reported: Binary package hint: gconf2 This is a problem in Edgy, as upgraded from Dapper. I did not see it in Dapper. A long time ago, during the installation of some package that uses gconf, the configuration phase of the installation failed with the following error: Failed to write "/var/lib/gconf/defaults/%gconf-tree.xml": Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists I forget which package originally triggered the error, I just started noticing it during upgrades at some point. Since then, every package that uses gconf (and tries to install a schema) fails to configure with that same error. Investigating, I found no evidence of a %gconf-tree.xml.new file. I tried all sorts of things, including starting from an empty %gconf-tree.xml file and manually installing all the schemas. Nothing worked, so I put the /var/lib/gconf directory back the way I found it. I have another similarly-configured Edgy box that was also upgraded from Dapper that does not exhibit this problem. I installed all the same gconf-using packages on that box, and then copied the entire /var/lib/gconf directory from the working box to the broken box. No dice. In desperation, I reinstalled the system -- this time, a clean Edgy install. I didn't reformat the hard drive, but I moved everything out of the way and then directed the installer to use the existing filesystem. After this, packages that wanted to install gconf schemas worked fine -- UNTIL TODAY. I upgraded evince from 0.6.1-0ubuntu1.1 to 0.6.1-0ubuntu1.2 today, and during the configuration phase, I got the same error! Re-configuriung (with dpkg --configure --pending) doesn't help, and again there's no %gconf-tree.xml.new file in /var/lib/gconf. The line in evince.postinst that triggers the bug is: gconf-schemas --register evince-thumbnailer-djvu.schemas evince-thumbnai ler-dvi.schemas evince-thumbnailer.schemas evince.schemas This is a fairly disruptive bug for some packages, since they can't install their gconf schemas at all, and any configuration that happens after gconf-schemas is called doesn't happen. ** Affects: gconf2 (Ubuntu) Importance: Undecided Status: Unconfirmed -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
