Announcement

Collapse
No announcement yet.

X.Org Server 1.20.11 Released Due To New Security Advisory

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

  • #11
    Originally posted by scottishduck View Post

    As I understand it, XWayland wouldn’t need the xorg-x11-dev-amdgpu driver as wayland uses the kernel driver and not the xorg one.
    Thanks for the response. I did some digging and you are correct. Unfortunately SDDM has a hard requirement for the xorg-x11-server. I hope that is some thing they intend to correct before the final release of 34. It would be odd to have a release whose main feature is to remove X but then force you to take it anyway over the greeter which is going to send you to Wayland. I'm sticking with the idea that the best way to update X is to remove it.

    Comment


    • #12
      I love the x11 or wayland articles....popcorn and reading the comment section

      Comment


      • #13
        Dead.. when both KDE/GNOME compositors *both* can't turn on my DisplayPort on this laptop... Wayland is not ready, still. I can't switch to it at all.

        Code:
        [ 126.282206] amdgpu 0000:01:00.0: amdgpu: SRBM_SOFT_RESET=0x00100040
        [ 126.449983] [drm] Got external EDID base block and 2 extensions from "edid/Samsung-LC27G7xT.edid.bin" for connector "DP-2"
        I'm not sure it's the Wayland compositors for KDE/GNOME or if its amdgpu.ko thats broken but this works fine in X...

        If nobody is going to release 1.21, maybe it's time someone took the reins of this, if its documented how the releases are made. I would if I had time...
        Last edited by spstarr; 13 April 2021, 04:28 PM.

        Comment


        • #14
          Originally posted by spstarr View Post
          If nobody is going to release 1.21, maybe it's time someone took the reins of this, if its documented how the releases are made. I would if I had time...
          https://lists.x.org/archives/xorg-de...ay/058174.html

          Comment


          • #15
            Originally posted by spstarr View Post
            Dead.. when both KDE/GNOME compositors *both* can't turn on my DisplayPort on this laptop... Wayland is not ready, still. I can't switch to it at all.

            Code:
            [ 126.282206] amdgpu 0000:01:00.0: amdgpu: SRBM_SOFT_RESET=0x00100040
            [ 126.449983] [drm] Got external EDID base block and 2 extensions from "edid/Samsung-LC27G7xT.edid.bin" for connector "DP-2"
            I'm not sure it's the Wayland compositors for KDE/GNOME or if its amdgpu.ko thats broken but this works fine in X...

            If nobody is going to release 1.21, maybe it's time someone took the reins of this, if its documented how the releases are made. I would if I had time...
            Maybe--just maybe--reporting a bug and giving feedback on your bug is easier than maintaining Xorg by yourself.

            Comment


            • #16
              Originally posted by MadeUpName View Post

              Thanks for the response. I did some digging and you are correct. Unfortunately SDDM has a hard requirement for the xorg-x11-server. I hope that is some thing they intend to correct before the final release of 34. It would be odd to have a release whose main feature is to remove X but then force you to take it anyway over the greeter which is going to send you to Wayland. I'm sticking with the idea that the best way to update X is to remove it.
              running gnome 40 myself, gdm is the same too. which i find odd as gdm uses wayland by default on everything except nvidia.

              Comment


              • #17
                Originally posted by CochainComplex View Post
                I love the x11 or wayland articles....popcorn and reading the comment section
                tsk! that's nothing, nowadays everybody accepted the end of X11.
                the real interesting comments comes when the article is about systemd or btrfs

                Comment


                • #18
                  Originally posted by spstarr View Post
                  Dead.. when both KDE/GNOME compositors *both* can't turn on my DisplayPort on this laptop... Wayland is not ready, still. I can't switch to it at all.

                  Code:
                  [ 126.282206] amdgpu 0000:01:00.0: amdgpu: SRBM_SOFT_RESET=0x00100040
                  [ 126.449983] [drm] Got external EDID base block and 2 extensions from "edid/Samsung-LC27G7xT.edid.bin" for connector "DP-2"
                  Wayland is a protocol between clients(programs you open) and the compositor. It has nothing to do with your Samsung display having as broken edid, in fact it has nothing to do with Displays at all, drm/dri/kms do that. KDE and Gnome parse the edid info in a similar way and it is more to specification then the way Xorg parses it, and that is likely the reason why Xorg accepts your display.

                  Comment


                  • #19
                    Originally posted by cynic View Post

                    tsk! that's nothing, nowadays everybody accepted the end of X11.
                    No, I know someone who does not. In his eyes, Xorg is way better because reasons. And Arcan is way better too. And then he send me a issue on the wayland repo where someone has the following scenario:
                    * He starts client via the terminal
                    * He suspends the client (technically freezing the process)
                    * The compositor at some point has a timeout and closes the connection to the client

                    Then he told me "Imagine if you have a bitcoin wallet and it fetches gigabytes of data from the harddisk and your compositor kills it" and I did die internally from reading that.

                    People, if your program stalls main() for a large amount of time to fetch data from the harddrive, you do something massively wrong and should not be anywhere near to a computer.

                    Comment


                    • #20
                      Originally posted by Alexmitter View Post

                      No, I know someone who does not. In his eyes, Xorg is way better because reasons. And Arcan is way better too. And then he send me a issue on the wayland repo where someone has the following scenario:
                      * He starts client via the terminal
                      * He suspends the client (technically freezing the process)
                      * The compositor at some point has a timeout and closes the connection to the client

                      Then he told me "Imagine if you have a bitcoin wallet and it fetches gigabytes of data from the harddisk and your compositor kills it" and I did die internally from reading that.

                      People, if your program stalls main() for a large amount of time to fetch data from the harddrive, you do something massively wrong and should not be anywhere near to a computer.
                      It is not a matter or large or small amount of data. I have a GUI program which reads a file, and it can not continue until it is fully read. It can be 10 bytes, it can be megabyte. Files can be on a local or on remote network server. Program does not know. I have a wired connection. If I accidentally trip on the wire and unplug the network, my process is stalled until i reattach it. When I do, it continues undisturbed. Just what I want. My program is stuck in fread() until it succeeds or fails. Now call me stupid, but this is how practically all programs work.

                      Program can be swapped out from RAM to disk, and until it is read back in, it can not continue. It may run slower, but it will work.

                      Comment

                      Working...
                      X