LMDE causing same-old APT problems
When I just tried upgrading my Linux Mint Debian installation, I again ran into that dreaded bug that causes APT to hang without consuming any CPU. I seriously am going to switch to Fedora if this bug with APT isn't going to be ironed out anytime soon.
|
It'll never be "fixed" if that is the extent of it's description.
Evo2. |
What happens is this: On the part where APT starts "Unpacking" the .deb files, nothing happens. It just echoes "Unpacking" and then stops. On top of that, when I am looking at my CPU indicator light, it would be flashing if the CPU or RAM was being consumed. Instead, nothing. It almost looks like an infinite loop is causing the problem.
|
Hi,
Quote:
You could try running the following to try to understand exactly what it is hanging on. Code:
ps aux | grep -E 'apt|dpkg' Code:
strace apt-get install foo Quote:
Cheers, Evo2. |
Trying to run strace returns this:
Code:
The program 'strace' is currently not installed. To run 'strace' please ask your administrator to install the package 'strace' Code:
configure: error: cannot run /bin/bash buildlib/config.sub |
I also know that the version of APT in LMDE is 0.8.0, while the version in Ubuntu Maverick is 0.8.3, which isn't causing as many problems. So, I will install Ubuntu 10.10 until LMDE or Debian (considering LMDE uses Debian repos) uses 0.8.3 and then switch back again.
|
I'm running both Debian stable (apt version 0.7.20.2+lenny2) and Debian unstable (apt version 0.8.4) and have no problems like the one you describe. Seems like compete overkill to install a different distribution instead of trying to understand and fix the problem (or perhaps filing a bug report), but each to their own I guess.
Cheers, Evo2. |
Yes, but LMDE uses 0.8.0 as I said, and it draws from Debian Testing, not Unstable. And it's 0.8.0 that caused this bug in an old version of Maverick Meerkat (Alpha 3). I also think it to be Acer Aspire One-specific.
|
Haven't seen anyone with this issue on forums.debian.net or on the Mint LMDE forum.
Never ran into it here and my install is over 6 yrs old, with apt-get update && apt-get dist-upgrade ran daily.(Fingers crossed, it will be 7 yrs in Feb 2011) Is the problem you are having listed on either launchpad or on the Debian BTS? Keep in mind that Ubuntu changes things so a bug on Ubuntu doesn't mean a bug on Debian and same for the other way around. Only thing similar is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442189 or this http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252758 but it is from an old old version of apt. |
All times are GMT -5. The time now is 03:56 PM. |