Find the answer to your Linux question:
Results 1 to 8 of 8
Today I received that god forsaken message "you have 350 mB left" from kali; in my infinite wisdom, I decided to run Code: sudo apt-get autoremove to remove ~250 mB... ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2014
    Posts
    2

    Question cannot use apt-get anymore


    Today I received that god forsaken message "you have 350 mB left" from kali; in my infinite wisdom, I decided to run
    Code:
    sudo apt-get autoremove
    to remove ~250 mB... Unfortunately I was using gnome... My compute decided it was high time to make my life hell, and uninstalled gnome and network-manager . I proceeded to spend the next several hours attempting to dig up a linux live cd. After it FINALLY loaded, I decided to chroot into my kali system and attempt to install gnome again. Unfortunately, when I booted up into Kali, it lacked wifi access but at least had the GUI. So, I started up the CD drive again and booted into ubuntu... Upon entering I chrooted into Kali again, but, when I attempted to install network-manager, I was presented by a daunting message... To understand why this message occurred you must know that earlier today, again in my most infinite of wisdom, decided, due to the EXTREME differences between Iceweasel and firefox such as I have no idea, to uninstall iceweasel and install the ubuntu version of firefox in my debian system. This daunting error message complained about iceweasel and firefox contradicting each other, as one stated my system was Ubuntu, and the other stated it was Debian (which I thought were extremely related to each other). I, in due time (2 hrs) fixed this problem by uninstalling firefox using dpkg among other things... After this, I decided to, again my my most infinite wisdom, reinstall gnome. Unfortunately I have been presented with the same error over and over again. Below is the error message when I now run
    Code:
    sudo apt-get install gnome
    :
    Code:
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    gnome is already the newest version.
    0 upgraded, 0 newly installed, 0 to remove and 116 not upgraded.
    5 not fully installed or removed.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue [Y/n]? y
    Can not write log, openpty() failed (/dev/pts not mounted?)
    Setting up gdm3 (3.4.1-8) ...
    dpkg: error processing gdm3 (--configure):
     subprocess installed post-installation script returned error exit status 1
    Setting up network-manager (0.9.4.0-10) ...
    [....] Reloading system message bus config...Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
    invoke-rc.d: initscript dbus, action "force-reload" failed.
    insserv: warning: script 'S70netglub-master' missing LSB tags and overrides
    insserv: script vboxdrv: service vboxdrv already provided!
    insserv: warning: script 'netglub-master' missing LSB tags and overrides
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Max recursions depth 99 reached
    insserv: There is a loop at service rmnologin if started
    insserv: There is a loop between service rmnologin and mountkernfs if started
    insserv:  loop involving service mountkernfs at depth 1
    insserv: exiting now without changing boot order!
    update-rc.d: error: insserv rejected the script header
    dpkg: error processing network-manager (--configure):
     subprocess installed post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of network-manager-gnome:
     network-manager-gnome depends on network-manager (>= 0.9.4); however:
      Package network-manager is not configured yet.
    
    dpkg: error processing network-manager-gnome (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of gnome-core:
     gnome-core depends on gdm3 (>= 3.4); however:
      Package gdm3 is not configured yet.
    
    dpkg: error processing gnome-core (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of gnome:
     gnome depends on gnome-core (= 1:3.4+7+deb7u1); however:
      Package gnome-core is not configured yet.
     gnome depends on network-manager-gnome (>= 0.9.4); however:
      Package network-manager-gnome is not configured yet.
    
    dpkg: error processing gnome (--configure):
     dependency problems - leaving unconfigured
    Errors were encountered while processing:
     gdm3
     network-manager
     network-manager-gnome
     gnome-core
     gnome
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Unfortunately, when I Google "netglub-master depends on rmnologin", no results came up.

    thanks in advance!
    TL;DR Version:
    I keep on getting the following error when I attempt to use apt-get:
    Code:
    insserv: Starting netglub-master depends on rmnologin and therefore on system facility `$all' which can not be true!
    Last edited by nicbit; 03-22-2014 at 01:33 AM.

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,533
    Sounds like an Oh Sh!t moment to me! I've done similar things in the past (and recently at that), and had to backup my critical data and re-install the OS and all of my critical applications, then restore my data to get going again. This may be such a case unless someone lurking here knows of a recovery tool for Debian/Ubuntu distributions.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Mar 2014
    Posts
    2
    is it just me, or is the O MY GOD I DELETED MY PHD THESIS moments far too frequent in these small(er) distros

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,533
    Well, if your thesis is still on disc, then you can boot a live cd/dvd/usb drive and recover it. I remember when my wife was in graduate school in the mid-1970's. We were both volunteers on the county rescue squad and were at the site of a tornado strike. We assessed the situation and checked the apartments that were affected by the storm (roofs torn off, cars up-ended in the swimming pool, etc) - no serious injuries thankfully, although I was a trained EMT and ERT and had my medical kit with us. We found one family in the top floor of one of the apartments without a roof, standing in their living room with the rain pouring down, and papers strewn everywhere. The man of the family was a graduate student and was getting ready to defend his thesis, but the storm basically sucked it, and all of his research, out into oblivion! In those days, most such work was on hard-copy... Needless to say, we could definitely feel his pain!

    That was DEFINITELY in the Sh!it Happens category!
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  5. #5
    drl
    drl is offline
    Linux Engineer drl's Avatar
    Join Date
    Apr 2006
    Location
    Saint Paul, MN, USA / CentOS, Debian, Slackware, {Free, Open, Net}BSD, Solaris
    Posts
    1,286
    Hi, nicbit.

    Welcome to the forum.

    I cannot tell whether you are using Kali, Ubuntu, or Debian. However, I can tell you that mixing binaries in repositories from different systems almost always results in tragedy. This even includes mixing Debian Stable, Testing, and Sid. There is some safety in compiling source, but it can take more time, effort, and knowledge.

    For some posts on this topic do a search with mix ubuntu debian repository site:forums.debian.net and read a few posts.

    If I cannot find a desired package in repositories, I either go without, or install to a local directory someplace in HOME, but never replacing applications and libraries from repositories. There are far too many possibilitites for gross version mis-matches, and many for more subtle differences.

    I am usually successful at avoiding crashes -- see below for some systems that I run.

    If it were me, I'd save what I could, re-install, and perhaps look at the Debian wiki for how to install Firefox in place of Iceweasel.

    However, if you are going to experiment like this, using virtual machines, and creating snapshots is a good way of being able to recover from many disasters. However, nothing beats a real backup for peace of mind, saving one's valuable time, etc.

    Good luck ... cheers, drl
    Code:
    # Uptimes for available machines 2014.03.22:
    up  80 days   6 users: aptosid 2013.1 (Hesperides, Debian jessie/sid) 
    up 103 days   5 users: CentOS 6.4 (Final) 
    up 103 days   1 users: Debian 5.0 (lenny, vm-server) 
    up 103 days   2 users: Debian 6.0 (squeeze, backups) 
    up 103 days   6 users: Debian 7.2 (wheezy, vm-server-ng) 
    up 104 days  31 users: Debian 5.0.8 (lenny, workstation) 
    up  25 days   2 users: Debian 7.4 (wheezy, workstation-vm) 
    up  87 days   6 users: Debian (jessie) 
    up  97 days  12 users: Fedora 19 KDE (Schrödinger’s Cat) 
    up  75 days   2 users: OpenBSD, 5.3, amd64 
    up  97 days   5 users: openSUSE 12.3 (Dartmouth) 
    up  40 days   6 users: Slackware 14.0 
    up 101 days   2 users: Solaris 10 10/08 s10x_u6wos_07b X86 
    up  97 days   7 users: Ubuntu 12.04.3 LTS (Precise Pangolin)
    Welcome - get the most out of the forum by reading forum basics and guidelines: click here.
    90% of questions can be answered by using man pages, Quick Search, Advanced Search, Google search, Wikipedia.
    We look forward to helping you with the challenge of the other 10%.
    ( Mn, 2.6.n, AMD-64 3000+, ASUS A8V Deluxe, 1 GB, SATA + IDE, Matrox G400 AGP )

  6. #6
    Just Joined! fenario's Avatar
    Join Date
    Mar 2009
    Location
    Rylstone NSW Australia
    Posts
    36
    Hi nicbit

    Sometimes you can waste far too much time fixing complex faults. Fortunately with Linux we don't need key codes for installation and it's free too (unlike windows). So it makes sense to save what you can ( perhaps also a complete copy of the hidden ~/.thunderbird folder, if that is your mail-program, which you can re-introduce) and re-install the whole system. It'll be squeeky clean and you'll have more space again. I had a grand stuff up and needed to re-install. On the previous OS I tried so many different things; even had an android simulation. That filled up my partition too much. So I was glad to start again. I keep a "tweak diary", so any time I need to re-install I can do these changes on the new installation.

    The point is to know when to give up; and that could be a decision with your infinite wisdom behind it.

  7. #7
    Linux Engineer TNFrank's Avatar
    Join Date
    Jul 2013
    Location
    Crossville, TN. USA
    Posts
    827
    I did an apt-get autoremove once just to clean up anything that was orphaned on my system and it started eating the entire install,LOL. Ended up re-installing the Distro which is no big deal since I don't store anything on my install that's not also on a USB flash drive.
    Yep, sometimes ol' apt-get can really get ya'.

  8. #8
    Just Joined! fenario's Avatar
    Join Date
    Mar 2009
    Location
    Rylstone NSW Australia
    Posts
    36
    Quote Originally Posted by TNFrank View Post
    I did an apt-get autoremove once just to clean up anything that was orphaned on my system and it started eating the entire install,LOL. Ended up re-installing the Distro which is no big deal since I don't store anything on my install that's not also on a USB flash drive.
    Yep, sometimes ol' apt-get can really get ya'.
    Exactly. This is what I mean. TNFrank acted from his wisdom too.
    On another note; the command: sudo apt-get clean
    will remove files that had been downloaded into /var/cache/apt/archives
    If you want to clean out all the orphaned files that are not needed any longer
    it might be better to use Synaptic > Installed (auto removable)
    and right click on each file > Mark for Complete Removal
    and see what other files it wants to get rid of.
    The same goes for installing files. Keep a keen eye on: To be removed !
    It can even happen on updating if one has unstable repositories, Debian repositories for an Ubuntu OS or pre-release updates
    And one can easily overlook the "To be removed" column if there are a lot of updates. It happened to me too.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •