this post was submitted on 11 Sep 2024
16 points (83.3% liked)

Linux

7936 readers
7 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
MigratingtoLemmy@lemmy.world
16
Why does VirtualBox keep launching on boot? (lemmy.ca)
submitted 1 month ago* (last edited 1 month ago) by cygnus@lemmy.ca to c/linux@lemmy.world
16 comments fedilink hide all child comments
 

Sorry if this kind of question isn't allowed here, but I'm at my wit's end. VB randomly started launching on startup about 2 weeks ago (on EndeavourOS) and I can't figure out why. There's no shortcut in ~/config/autostart, it isn't in the KDE startup apps list, and I can't find anything virtualbox-related with systemctl either. There's also no setting in the VB app itself. WTF?

you are viewing a single comment's thread
view the rest of the comments
[–] JTskulk@lemmy.world 3 points 1 month ago (1 children)

Try to exclude it from being restored on KDE startup. There could be something running in the background that keeps getting saved and restored. Go to System Settings, System, Desktop Session, put virtualbox in the ignored applications list. You can also just choose "Start with an empty session" and then relog to see if that stops it from coming back, then you'll know if this is causing your problem or not. Good luck!

[–] cygnus@lemmy.ca 3 points 1 month ago (1 children)

I was feeling good about this one, but that didn't work either.

[–] JTskulk@lemmy.world 1 points 1 month ago (1 children)

Bummer! What's its parent process? Maybe that will hint at something.

[–] cygnus@lemmy.ca 1 points 4 weeks ago (1 children)

I'm not sure what you mean by this, sorry! My Linux expertise is limited once I get below surface level.

[–] JTskulk@lemmy.world 2 points 3 weeks ago

Well hey, welcome to the Linux club :)

Unlike Windows, in Linux every process has a parent except for PID (Process ID) 1, which is the init system. You can run a command like ps auxf and you'll get a tree of all your processes and you can hopefully see what spawned VirtualBox.