[SOLVED] An application has unexpectedly disappeared.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Linux mint 17.2
I have been trying (& eventually succeeding) to install WordPress. Initially I installed LAMP but then uninstalled it & installed XAMPP.
Today I came to use QGIS, one of my key applications & it has disappeared - from my panel and the Apps menu.
I suspect that the command I used
Code:
for pkg in `dpkg -l *apache* *mysql* phpmyadmin | grep ^ii | awk '{ print $2 }'`; do sudo apt-get -y purge --auto-remove $pkg; done;
2017-03-14 11:51:43 status installed qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 remove qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1 <none>
2017-03-14 11:51:43 status half-configured qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 status half-installed qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 status config-files qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 status config-files qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 status config-files qgis-plugin-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 status not-installed qgis-plugin-grass:amd64 <none>
2017-03-14 11:51:43 status installed qgis-provider-grass:amd64 2.14.3+dfsg-2~trusty1
2017-03-14 11:51:43 remove qgis-provider-grass:amd64 2.14.3+dfsg-2~trusty1 <none>
Is that evidence that it has been uninstalled? Is there a way of reversing this, as reinstallation of the whole QGIS suite of tools so they all talk to each other, is a royal pain.
Thanks
Last edited by mogmog; 03-15-2017 at 07:18 AM.
Reason: clarity
I should add that I would advise against running such scripts in the future unless you know exactly what they are going to do. The person who wrote that script should have taken into consideration that additional installed packages might have "apache" and "mysql" somewhere in their names.
A good way of checking what an apt-related command will do is to run it in simulate mode by placing the -s option before the commands e.g. apt-get -sy purge --auto-remove $pkg in the command above.
Check your apt log out at /var/log/apt/history.log
Please paste the portion of the log that resulted from the command that you issued.
Thanks - I searched for auto-remove: all the entries are together, so I presume this is the section you mean?
Oddly, I see a Kexi entry, but this still works (at the level I use it). And no QGIS/GRASS/SAGA entries.
Thanks. We're working off the assumption that it was the effects of the command that you ran that purged a package or packages it shouldn't have, and it is that which has rendered QGIS inoperable. Of course that assumption could be wrong.
There are two ways you could approach this. Firstly you could reinstall QGIS, which should pull in any dependencies it requires. Your personal config in home will remain the same but any system config may not, so you may have to reconfigure QGIS. However, it is worth considering that one of more of the packages purged by the original command may still affect the system otherwise in the future due to their lack of presence.
Alternatively you could reinstall every package that was removed by the command. However this could well conflict with XAMPP, so you may have to uninstall XAMPP before you do that. In effect you would be, by examining the APT history log and selecting commands associated with the LAMP stack, rolling back to the situation you were in before. Then, once you have reached that situation, you would see what LAMP components you have installed, remove with care what you don't need, and then install XAMPP. It should be noted that you may well however be able to install XAMPP over LAMP with no problems - I don't know, but a web search should help you out on that.
The third option is to roll back your system to the backup that you took of it before you ran the initial command. That's of course if you are making backups of your system.
Just a quick further thought. Have a look at your APT history log to see if you can find out exactly which packages and dependencies were installed when you initially installed LAMP. That will allow you to determine which packages were subsequently purged which shouldn't have been.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
