Hi All,

I am looking at starting a project and was wondering if there was a way to make it so a controller type changed boot conditions. I want to move to linux for my home entertainment and would like to have a ps5 controller boot Lutris and a different controller boot into something like KDE plasma.

Is this a possibility or nonsense?

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    15 days ago

    I think the bigger hurdle here is that you need to do some legwork and research, else you would not be here asking this question 😉

    It’s possible but then I’d ask why? What’s the purpose of booting a different DE based on the controller type?

    • Victor@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 days ago

      My guess is that they want only the necessary software to run when gaming, which KDE is not. But I’ll let OP speak for themselves.

    • Squizzy@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      14 days ago

      I’m unsure of what the first part means, is this not looking for advice? I am new to linux and know I can have steam open on start up to big picture mode and I want the machine to also be easily accessible for other members of the family to launch apps like plex.

      At the moment they press the ps5 controller to boot to ps5 or the tv remote to boot to apps. Seeing as how these will now be merged to a single machine I want to make a user friendly differentiation.

  • superfes@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    15 days ago

    Certainly seems like you could make a udev rule to do something along these lines, I know you can execute specific commands /w udev, whether or not you can enable or disable a system service or whatever, I dunno, guess you could always execute a custom start script before WM that decides which WM to start

  • Bluefruit@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    15 days ago

    I think you’d be better off just having a controller hook up and that triggers a bash script to start steam in big picture mode or lutris.

    You probably could do something like this if you really wanted to but this would be clunky. If you’re always turning off the machine after you’re done using it, maybe it’d be OK but IMO, it would make more sense to just use KDE plasma and script something to get the functionality that you want.

    You wouldn’t have to worry about booting things up or shutting them down if you wanna switch between gaming and whatever else, you could easily make changes to it, and it’d likely be less complicated.

    Hell even a shortcut that opens it through a button combo or something would work for this. Pair controller, hit a key on your keyboard, boom, steam opens. That can be done through KDE natively through the shortcuts settings. Very easy to setup and something I use a lot.

  • glitching@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days ago

    “rebooting” is not a thing ova here. yeah, you can accomplish that but that’s not what you want. utilising something like InputRemapper + e.g. Plasma shortcuts, you can launch a big-picture UI, like steam or plama-bigscreen when it’s ready or somesuch, when you press a key combo on the controller or mouse or keyboard or any combination thereof.

    • Squizzy@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      14 days ago

      Yeah I suppose rebooting is the incorrect path or word. I am looking to closely mirror the current setup of smart tv, console, streaming box etc. all on one machine.

      The keyboard is unlikely to be used by anyone other than me, I am to do some research on an appropriate tv style remote to select apps and use within apps.