Linux mint hangs after "Started*AppArmor*initializaion"
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 hangs after "Started*AppArmor*initializaion"
Linux mint hangs after "Started*AppArmor*initializaion".
Running on a Lenovo R500 Thinkpad, 64bit, 2GB mem. with Linux Mint with MATE 19.3 on a USB stick. Not seeing any errors as it boots up. It gets to that point "starting AppArmor" and then hangs (booting in recovery mode). It will boot on another Lenovo L412 Thinkpad, 64bit, 4GB memory. The R500 has Linux Mint Mate 19.3 installed on the HDD (but currently getting a grub error - reason I'm trying to boot from USB stick). The L412 has Windows 10 Pro installed on the HDD. I should add, I can't get to the Recovery menu.
I asked the above question about the hang after apparmor started and have not seen anything. Is there anyone out there that knows how to fix the problem?
Secondly, your post isn't the easiest to read - when a post is difficult to understand, a lot of people just skip past it, so try re-phrasing it and being more structured.
As for the issue itself, you say the same thing works on another machine, so what is the next step that occurs there, that the hanging machine doesn't reach?
Also, how much do you care about solving this specific issue, versus finding another way to solve your Grub problem? (Can you just try another distro and/or USB drive?)
Linux mint hangs after "Started*AppArmor*initializaion"
As I stated, I have Linux Mint on a USB stick (32GB). It will boot on a Lenovo L412 but not on a Lenovo R500, where it hangs after the "starting Apparmor" message. In addition, to hanging in a normal boot, it also hangs there in trying to get to "recovery mode" - you know recovery mode where you can do a "Clean", "DPKG", "FSCK", etc.
The only piece of data that could be confusing was just saying "Recovery mode". The intent was recovery mode could not be reached either on the system where it hangs on the Apparmor.
If I had just posted it hangs on "starting apparmor", I would have been questioned, what system I am running, what ios the H/W, etc., etc., including was it cloudy that day or was the sun shining, how many siblings do I have, etc. Not trying to be a smart@$$, but the relatively few questions have posted in the past amount to just that and even after reposting all the requested information, never got an answer. One reason why I don't post an occasional problem on these boards as I either get BS replies back or a lot of "why are you doing what you are doing" or other nonsensical replies. I see too much of that on a lot of these boards, which is why I can see newbies saying "screwit, I'll stick to Windows.
So, do you have a solution? If so, it would be appreciated. Thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.