Bill, it is possible that what I suggested you to do don't work.
At least Debian poster seems to say it does not work that way for him to find
corrupted .desktop files.
I am speaking to developers here.
I WAS WRONG.
I have deliberately broken my
/usr/share/applications/screensavers/flipscreen3d.desktop file by removing the
[desktop] line.
Then:
[EMAIL PROTECTED]:~$ sudo update-desktop-database
Could not parse file
'/usr/share/applications/screensavers/flipscreen3d.desktop': Key file does not
start with a group
File '/usr/share/applications/totem.desktop' contains invalid MIME type '-e'
that is missing a slash
[EMAIL PROTECTED]:~$
So Hardy SEEMS (I am slowly becoming more prudent) to not be affected.
I tried to compare Gutsy and Hardy and they seems the same to me.
After:
mime_types = g_key_file_get_string_list (keyfile,
g_key_file_get_start_group (keyfile),
"MimeType", NULL, &load_error);
Code does:
g_key_file_free (keyfile);
if (load_error != NULL)
{
g_propagate_error (error, load_error);
return;
}
I have a new ... *hypothesis*
I now believe that this code is right.
But that there was an assert in the Glib for the g_key_file_get_start_group in
Gutsy that have been removed in Hardy.
So that now g_propagate_error do work (and was not going up to there in Gutsy
because of the hypothetical assert).
--
update-desktop-database segfault
https://bugs.launchpad.net/bugs/59392
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
