Announcement

Collapse
No announcement yet.

SystemD/Udev Multi-Seat Support For X.Org

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SystemD/Udev Multi-Seat Support For X.Org

    Phoronix: SystemD/Udev Multi-Seat Support For X.Org

    Lennart Poettering has published patches this Sunday to provide support for udev/systemd multi-seat input device hot-plugging support for the X.Org Server...

    http://www.phoronix.com/vr.php?view=OTY4MA

  • #2
    Yay! Breaking shit for no good reason. That's what open source development is all about now.

    Comment


    • #3
      @yogi_berra: Break what and how? I only see something getting added.

      Comment


      • #4
        Multiseat rocks! The single coolest, most amazing thing I've ever made Linux do.

        Comment


        • #5
          Multi-seat is awesome, go multi-seat!

          Comment


          • #6
            If I understand correctly, this will FINALLY fix the problem with disappearing peripherals when using multiseat.

            For those who do not use multiseat, the problem is that the new InputClass method of adding peripherals is incompatible with multiseat setups. So is hotplugging, which makes ALL X servers listen to ALL peripherals at the same time, breaking multiseat. You have to use InputDevice and explicitly disable hotplugging in order for multiseat to work. If you unplug the mouse or keyboard, your X session becomes deaf, and only a logout will fix it.

            So if you accidentally lose the connection to one of your mice or keyboards (this happens quite often when there is some fluctuation on the USB bus, such as when plugging in a USB stick or a camera), you must log out. This happens at least once a day with my cheap mouse, and once a week for one of the three other peripherals.

            So this is great news, which should fix MAJOR breakage.

            Comment


            • #7
              This is so awesome.

              Comment


              • #8
                Originally posted by phoronix View Post
                Phoronix: SystemD/Udev Multi-Seat Support For X.Org
                This is awesome but as pointed out many times before here, it is called "systemd" and not "SystemD" although Phoronix gets this consistently wrong. Check the prominent note on the frontpage

                http://www.freedesktop.org/wiki/Software/systemd/

                Comment


                • #9
                  Good news.
                  Halton Huo couldn't make his multiseat patches land GDM master branch. I hope Lennart will be more lucky to make multiseat "official" part of Linux desktop.

                  Comment


                  • #10
                    Originally posted by mudig View Post
                    I only see something getting added.
                    No, you see a working system getting replaced with something that is in development and unnecessary for most use cases, unless you are willing to argue that web servers and render nodes need to be instant on devices, of course.

                    Comment


                    • #11
                      Originally posted by yogi_berra View Post
                      No, you see a working system getting replaced with something that is in development and unnecessary for most use cases, unless you are willing to argue that web servers and render nodes need to be instant on devices, of course.
                      Hmm, sounds like every software/program out there that intends to replace some other software/program. Oh, you meant unstable/untested. Well, I'm sure they'll test it before pushing it on the masses; it is Xorg we're talking about, after all.

                      (...you shouldn't be using bleeding-edge Xorg releases in a production environment anyway)

                      Comment


                      • #12
                        Originally posted by yogi_berra View Post
                        No, you see a working system getting replaced with something that is in development and unnecessary for most use cases, unless you are willing to argue that web servers and render nodes need to be instant on devices, of course.
                        This fixes a LONG standing bug preventing multiple users from using the computer at the same time. For a multi-user system like Unix, this is rather important.

                        Why are you running X on servers and render nodes anyway?

                        Comment


                        • #13
                          Originally posted by pingufunkybeat View Post
                          If I understand correctly, this will FINALLY fix the problem with disappearing peripherals when using multiseat.

                          For those who do not use multiseat, the problem is that the new InputClass method of adding peripherals is incompatible with multiseat setups. So is hotplugging, which makes ALL X servers listen to ALL peripherals at the same time, breaking multiseat. You have to use InputDevice and explicitly disable hotplugging in order for multiseat to work. If you unplug the mouse or keyboard, your X session becomes deaf, and only a logout will fix it.

                          So if you accidentally lose the connection to one of your mice or keyboards (this happens quite often when there is some fluctuation on the USB bus, such as when plugging in a USB stick or a camera), you must log out. This happens at least once a day with my cheap mouse, and once a week for one of the three other peripherals.

                          So this is great news, which should fix MAJOR breakage.
                          While this patchset is definitely really useful, you can still use InputClasses to have working multiseat setups with hotplug. Instead of an InputDevice section with hotplug disabled, just change it to an InputClass section which matches the exact same device your InputDevice would use. Job done.

                          I first implemented multiseat for Ubuntu in 2004, and I believe it still works just as well to this day. This just improves it.

                          Comment


                          • #14
                            Originally posted by daniels View Post
                            While this patchset is definitely really useful, you can still use InputClasses to have working multiseat setups with hotplug. Instead of an InputDevice section with hotplug disabled, just change it to an InputClass section which matches the exact same device your InputDevice would use. Job done.
                            Obviously you know X better than I do, but are you sure?

                            I know that you can define an InputClass to be specific enough to match a particular input device. The problem was that I could not find an option which ties an InputClass to a particular seat.

                            Specifically, ServerLayout can refer to a specific InputDevice, but not to a specific InputClass, or at least I haven't found a way to do it, which is why I gave up. I've just checked with "man xorg.conf" with xserver 1.10.3

                            If you can tell me how it's supposed to work, I'd be really really happy!

                            Comment


                            • #15
                              Originally posted by pingufunkybeat View Post
                              Multiseat rocks! The single coolest, most amazing thing I've ever made Linux do.
                              Hey, this really sounds very cool. I haven't followed multiseat development at all, and after reading some bits here and there I'm left with some practical questions:

                              - Do I need a videocard per seat?
                              - Is it easy to get running? Like, is this already in a state where I install something through my package manager and be done?
                              - What happens to 3D acceleration in a multiseat configuration?

                              We are two at home, both adicted to the internets (so we spend a lot of time in front of our respective computers). Right now we have a Vista desktop plus two laptops (Vista + linux), and I'm thinking in getting myself another desktop. Would you say it makes sense to set up a multiseat linux system on the existing desktop instead of going for another one? I'm thinking that it'd have to run Windows on a virtual machine and handle whatever it is I may be doing in linux. Would this push things too much for a rather basic dual core CPU? Also, I imagine the wiring of peripherals may get a bit messy if I wanted the systems to be in different rooms...

                              Comment

                              Working...
                              X