X-chm + uninstall causes mime-type problems

Bug #78592 reported by Jacob Hannan
2
Affects Status Importance Assigned to Milestone
desktop-file-utils (Debian)
Fix Released
Unknown
desktop-file-utils (Ubuntu)
Fix Released
Medium
Ralph Janke

Bug Description

Binary package hint: gnochm

I have had gnochm installed on my edgy system for a while now without confronting any problems. The latter arrived when I installed x-chm as well. At this point, I can't recall if/what error I got at first, but I proceeded to try to uninstall gnochm and get the following:

jacob@localhost:~$ sudo aptitude remove gnochm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages will be REMOVED:
  gnochm
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 717kB will be freed.
Writing extended state information... Done
(Reading database ... 95889 files and directories currently installed.)
Removing gnochm ...
***
* Updating MIME database in /usr/share/mime...
Wrote 481 strings at 20 - 27f8
Wrote aliases at 27f8 - 29ac
Wrote parents at 29ac - 337c
Wrote literal globs at 337c - 33e0
Wrote suffix globs at 33e0 - 6768
Wrote full globs at 6768 - 678c
Wrote magic at 678c - be18
Wrote namespace list at be18 - be28
***

(update-desktop-database:13792): GLib-CRITICAL **: g_key_file_get_string_list: assertion `group_name != NULL' failed
Segmentation fault (core dumped)
dpkg: error processing gnochm (--remove):
 subprocess post-removal script returned error exit status 139
Errors were encountered while processing:
 gnochm
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
jacob@localhost:~$

I now get this whether I have x-chm installed or not.

Revision history for this message
Jacob Hannan (hannanjf) wrote : Solved; unrealted to gnochm

Turns out that this problem is the result of a corrupted .desktop file, as described here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396439

As pointed out in the bug report, there is no easy way of finding out which of the files is corrupted. I was able to do so by looking at the /usr/share/applications directory and subdirectories with nautilus. I noticed one of the screensaver .desktop files wasn't using the "binary" icon that all the others were, so I backed it up, moved it, and re-ran aptitude. This time, I had no errors. In order to recreate an uncorrupted .desktop file, I ran:

Code:

sudo aptitude reinstall gnome-screensaver screensaver-default-images xscreensaver-data xscreensaver-gl

... and refreshed nautilus. And there it was, with the proper icon.

I am not sure if the icon thing is a generalizable means of detecting corrupted .desktop files, or not, however.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thanks for submitting this problem and helping to make Ubuntu better.

I have tested to remove gnochm without and with xchm installed. Both times it works without any error. I have done this on hardy BETA.

I therefore believe this problem has been fixed and would like to close this report. Is this ok? Or do you want to test it on hardy?

Thanks.

Changed in gnochm:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
Ralph Janke (txwikinger) wrote :

This was fixed in version 0.14-2 and was integrated into ubuntu with 0.15-1 in hardy.

Changed in gnochm:
importance: Undecided → Low
status: Incomplete → Confirmed
Changed in desktop-file-utils:
status: Confirmed → Fix Released
importance: Low → Medium
Changed in desktop-file-utils:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.