Skip to content

Instantly share code, notes, and snippets.

Created November 4, 2014 10:39
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save anonymous/248fc2618d89d6532019 to your computer and use it in GitHub Desktop.
Save anonymous/248fc2618d89d6532019 to your computer and use it in GitHub Desktop.
$ sudo apt-get purge gconf2&&sudo apt-get install gconf2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
gconf2*
0 upgraded, 0 newly installed, 1 to remove and 12 not upgraded.
3 not fully installed or removed.
After this operation, 258kB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 49907 files and directories currently installed.)
Removing gconf2 ...
Purging configuration files for gconf2 ...
Processing triggers for man-db ...
Setting up shared-mime-info (0.71-1ubuntu2) ...
Segmentation fault
dpkg: error processing shared-mime-info (--configure):
subprocess installed post-installation script returned error exit status 139
dpkg: dependency problems prevent configuration of libgtk2-perl:
libgtk2-perl depends on shared-mime-info; however:
Package shared-mime-info is not configured yet.
dpkg: error processing libgtk2-perl (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of libgnome2-canvas-perl:
libgnome2-canvas-perl depends on libgtk2-perl (>= 1.040); however:
Package libgtk2-perl is not configured yet.
dpkg: error processing libgnome2-canvas-perl (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
shared-mime-info
libgtk2-perl
libgnome2-canvas-perl
E: Sub-process /usr/bin/dpkg returned an error code (1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment