SERIOUS PROBLEM !!! With Antix and / or MX Package Manager !!!
by LinWinux from LinuxQuestions.org on (#56NEQ)
I consider this thread to be really important because of the following hidden problem. It's not anything that requires an individual user resolution, but rather some action by the developers of Antix and/or MX linux distribution.
A few day ago I installed an MX 19 snapshot which was created from an updated/upgraded MX 18 system. It was created from an older generic Asus laptop with 4 GB of RAM and a 7200 rpm 500 GB SATA drive. Older 1,83 ghz. intel CPU with intel HD grahics. I do believe that the hardware used is irrelevant though. Newly refurbished hard disk with no other operating system. Clean installation ...
The installed snapshot which installed without a problem, had a few packages that I wanted to remove as there were similar other duplicates installed as well. Utilizing MX Tools, followed by going to the MX Package Manager, from where I opened the second Tab at the top for stable repository, I searched for some applications and began removing these one by one. Right now I don't remember specifically which app generated the problem, but the ones which I uninstalled were:
shutter
swell-foop
gthumb
simple-scan
supertuxkart
cheese
kshisen
kpat
There were some other apps which were removed as well, but I'm pretty certain that the problem began with one of the above during removal. As you already know, when you first initiate a removal, you'll receive a summary message in the window telling you the app about to be removed and the amount of free space this will result in. Usually that's anywhere from less than 1 MB up to 200+ MB for some of the more massive applications.
Anyway, for the removal of one of the programs the message for disk space to be freed resulted in 670 MB or thereabout. My first thought was, "Wow, that's an awful lot of space for such a small programm" ... followed by thinking "What the heck, what do I know about additional packages that are tied to this one, let's just do it and see what happens"
Well, by the time that the 3rd or 4th line ticked by, I noticed things being removed that I knew for a fact had nothing to do with that particular application. Instead of panicking and since this was a fairly new build anyway, I decided to keep on watching, to see what else would get removed.
Most of the XFCE files remained untouched, but a huge portion, I'd say about 50 to 65 percent of all of the MX Tools packages were removed, including of course the initial app which I wanted to remove in the first place and which had absolutely nothing to do with anything MX-Tools related. So somewhere for whatever reason, there's a serious problem with the Package Manager or rather, the removal of apps by means of the Package Manager.
On a side note: I also noticed that anytime that Ksnip or Swell-Foop is open on another one of my machines, some applications are no longer accessible. The system itself is fine, but some applications simply do not respond at all when clicking on them. But as soon as I close either of those two when I'm done, everything else goes back to normal. It's not a big deal, just a weird glitch of sorts that I thought I'd mention since both of those apps were also used in the described issue above.
A few day ago I installed an MX 19 snapshot which was created from an updated/upgraded MX 18 system. It was created from an older generic Asus laptop with 4 GB of RAM and a 7200 rpm 500 GB SATA drive. Older 1,83 ghz. intel CPU with intel HD grahics. I do believe that the hardware used is irrelevant though. Newly refurbished hard disk with no other operating system. Clean installation ...
The installed snapshot which installed without a problem, had a few packages that I wanted to remove as there were similar other duplicates installed as well. Utilizing MX Tools, followed by going to the MX Package Manager, from where I opened the second Tab at the top for stable repository, I searched for some applications and began removing these one by one. Right now I don't remember specifically which app generated the problem, but the ones which I uninstalled were:
shutter
swell-foop
gthumb
simple-scan
supertuxkart
cheese
kshisen
kpat
There were some other apps which were removed as well, but I'm pretty certain that the problem began with one of the above during removal. As you already know, when you first initiate a removal, you'll receive a summary message in the window telling you the app about to be removed and the amount of free space this will result in. Usually that's anywhere from less than 1 MB up to 200+ MB for some of the more massive applications.
Anyway, for the removal of one of the programs the message for disk space to be freed resulted in 670 MB or thereabout. My first thought was, "Wow, that's an awful lot of space for such a small programm" ... followed by thinking "What the heck, what do I know about additional packages that are tied to this one, let's just do it and see what happens"
Well, by the time that the 3rd or 4th line ticked by, I noticed things being removed that I knew for a fact had nothing to do with that particular application. Instead of panicking and since this was a fairly new build anyway, I decided to keep on watching, to see what else would get removed.
Most of the XFCE files remained untouched, but a huge portion, I'd say about 50 to 65 percent of all of the MX Tools packages were removed, including of course the initial app which I wanted to remove in the first place and which had absolutely nothing to do with anything MX-Tools related. So somewhere for whatever reason, there's a serious problem with the Package Manager or rather, the removal of apps by means of the Package Manager.
On a side note: I also noticed that anytime that Ksnip or Swell-Foop is open on another one of my machines, some applications are no longer accessible. The system itself is fine, but some applications simply do not respond at all when clicking on them. But as soon as I close either of those two when I'm done, everything else goes back to normal. It's not a big deal, just a weird glitch of sorts that I thought I'd mention since both of those apps were also used in the described issue above.