Looks like you removed the package database that apt creates from a package repository entry. All you need to do to get rid of a repository is to delete the config file for it out of the apt config at /etc/apt/sources.list.d/ or to remove the line from the config file at /etc/apt/sources.list. After you've done that, just run "apt-get update" and it will clean out all the repositories that don't exist anymore as well as update all the ones that still do. After that, symantic should start working again. Brian On 12/18/2013 02:53 PM, Michael Havens wrote: > oops.... what am I doing wrong? I remove the files: > > bmike1@PresarioLapTop1:~$ ls /var/lib/apt/lists/ |grep medibuntu > packages.medibuntu.org_dists_quantal_free_binary-i386_Packages > packages.medibuntu.org_dists_quantal_free_i18n_Translation-en > packages.medibuntu.org_dists_quantal_free_i18n_Translation-en%5fUS > packages.medibuntu.org_dists_quantal_non-free_binary-i386_Packages > packages.medibuntu.org_dists_quantal_non-free_i18n_Translation-en > packages.medibuntu.org_dists_quantal_non-free_i18n_Translation-en%5fUS > bmike1@PresarioLapTop1:~$ cd /var/lib/apt/lists/ > bmike1@PresarioLapTop1:/var/lib/apt/lists$ sudo rm -rf *medibuntu* > bmike1@PresarioLapTop1:/var/lib/apt/lists$ ls /var/lib/apt/lists/ |grep > medibuntu > bmike1@PresarioLapTop1:/var/lib/apt/lists$ sudo synaptic > > (synaptic:7475): GLib-GObject-CRITICAL **: g_object_set_data: assertion > `G_IS_OBJECT (object)' failed > > (synaptic:7475): GLib-GObject-WARNING **: invalid (NULL) pointer instance > > (synaptic:7475): GLib-GObject-CRITICAL **: g_signal_connect_data: > assertion `G_TYPE_CHECK_INSTANCE (instance)' failed > > and synaptic opens, then ubuntu's update manager is run to update the > system and it tells me: > > Failed to fetch http://packages.medibuntu.org/dists/quantal/Release.gpg > Something wicked happened resolving 'packages.medibuntu.org:http' (-5 > - No address associated with hostname) > Failed to fetch > http://packages.medibuntu.org/dists/quantal/free/binary-i386/Packages > Something wicked happened resolving 'packages.medibuntu.org:http' (-5 > - No address associated with hostname) > Failed to fetch > http://packages.medibuntu.org/dists/quantal/non-free/binary-i386/Packages Something > wicked happened resolving 'packages.medibuntu.org:http' (-5 - No address > associated with hostname) > Failed to fetch > http://packages.medibuntu.org/dists/quantal/free/i18n/Translation-en_US > Something wicked happened resolving 'packages.medibuntu.org:http' (-5 > - No address associated with hostname) > Failed to fetch > http://packages.medibuntu.org/dists/quantal/free/i18n/Translation-en > Something wicked happened resolving 'packages.medibuntu.org:http' (-5 > - No address associated with hostname) > Failed to fetch > http://packages.medibuntu.org/dists/quantal/non-free/i18n/Translation-en_US > Something wicked happened resolving 'packages.medibuntu.org:http' (-5 > - No address associated with hostname) > Failed to fetch > http://packages.medibuntu.org/dists/quantal/non-free/i18n/Translation-en > Something wicked happened resolving 'packages.medibuntu.org:http' (-5 > - No address associated with hostname) > Some index files failed to download. They have been ignored, or old ones > used instead. > > I then clicked update and now it says my system is up to date but when > 'refresh' is clicked I still get the medibuntu error? > > :-)~MIKE~(-: > > > On Wed, Dec 18, 2013 at 1:48 PM, Michael Havens > wrote: > > thanks > > :-)~MIKE~(-: > > > On Wed, Dec 18, 2013 at 1:34 PM, sean ritzler > > wrote: > > The medibuntu repo has been shut down. You'll want to remove any > mention of it from your list of repositories. > > On Wed, Dec 18, 2013 at 1:31 PM, Michael Havens > > wrote: > > I can't get my packaage managers to work. For instance: I > open synaptic and > > after it loads an info window appears that says: > > > > E: Encountered a section with no Package: header > > E: Problem with MergeList > > > /var/lib/apt/lists/packages.medibuntu.org_dists_quantal_free_i18n_Translation-en > > E: The package lists or status file could not be parsed or > opened. > > E: _cache->open() failed, please report. > > > > Please, how do I fix this? > > :-)~MIKE~(-: > > > > --------------------------------------------------- > > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > > > To subscribe, unsubscribe, or to change your mail settings: > > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > > > > > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss