I resolved the issue I was having. I had to enable the Updates/testing parrot repo to satisfy dependcies held back packages/ broken packages to get the right linux-headers package. Which was a simple and quick fix. I didn’t immediately jump to this solution, however, as I have come to realize I wasn’t so much looking for the solution, but was hell bent on finding the cause of the issue(looking for something to blame)
My thoughts on this is that this is an issue i’d normally attribute to user error and carelessness or improper package maintenance(n00bs!) I’d expect to see someone adding or removing repos unnecessarily and getting their packages out of sorts, however,I had not changed or altered any repos recently nor have I deviated from recommended best practices when it comes to package maintenance (update, parrot-upgrade, ect)
Considering these inconsistencies I’m unable to determine the root cause of the issue with much confidence. The timing and sequence of events suggests it was the kernel update that was the cause, but as I already stated, normally I’d attribute something like this to user error (i.e. finger-fucking the repos without knowing what is being done and what the outcome will be.)
I’m not a rocket scientist, or brain surgeon, I never got the job as a g33k on the g33k squad. Matter of fact I’m a heavy equipment operator on a good day but more often than not I’m just another cog in the wheel. I’ve worked construction for 15 years. All that is to say, I’m no "professional’’ in the realm of IT. I’m working on getting a few certifications and maybe changing careers, but it’s all been out of passion and pleasure up to this point, and I will be eternally grateful to have found something I enjoy as much as I do the ethical hacking, open source, linux, tech, community (ParrotOS, the real gold here, the MVP, in its own right is an amazing experience and the most worthy project and collaboration I’ve had the pleasure to watch evolve and grow. I have the greatest respect for the Parrot team, they have filled the void that windows or any other linux distro could not. Efficient, practical, useful, seamless in my setup/ life. It’s not limited to one use case such as kali is. It just makes sense for me, right now.
Back to topic. I’m prone to mistakes and human error as much as anyone, probably more so. But I would consider myself very capable and technologically inclined by nature. I had no problem teaching myself linux, ethical hacking/penetration testing methodologies and tools, how to code, building and compiling a custom kernel, ect. I know I hadn’t messed about my repos and cannot for the life of me pinpoint anything I’ve done that would cause this issue, but given the nature of the issue I’m not marking it off the list of possibilities
Has anyone else had the same issue/error as discussed in the original post? Or does it come to reason that I may have done something to trigger the problem? I’ll continue to look through some logs that may reveal some clues but unless I missed something, I know when it came to be and what was happening when it did.
The lack of confirmations I believe is already speaking for itself… Back to the drawing board
