Announcement

Collapse
No announcement yet.

Anyone attempt Wayland yet?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Anyone attempt Wayland yet?

    Curious about it. I've been lightly watching the progress to Wayland. I understand and frankly agree with Canonical's decision to default to Xorg for 18.04 but supposedly you can install a Wayland compositor and all it's dependencies and log into a Wayland session. This is not working (yet) with the Kubuntu Beaver release.

    I guess I haven't figured out the magic sauce to getting Wayland to show in SDDM.

    Please Read Me

    #2
    Plasma/Wayland Showstoppers : https://community.kde.org/Plasma/Wayland_Showstoppers
    Before you edit, BACKUP !

    Why there are dead links ?
    1. Thread: Please explain how to access old kubuntu forum posts
    2. Thread: Lost Information

    Comment


      #3
      Hmmm, have to try later:

      This site can’t be reached

      community.kde.org took too long to respond.
      Try:


      ERR_CONNECTION_TIMED_OUT

      Please Read Me

      Comment


        #4
        Originally posted by oshunluvr View Post
        I guess I haven't figured out the magic sauce to getting Wayland to show in SDDM.
        Package plasma-workspace-wayland should give you a wayland session in sddm?
        On #kubuntu-devel & #kubuntu on libera.chat - IRC Nick: RikMills - Launchpad ID: click

        Comment


          #5
          Originally posted by acheron View Post
          Package plasma-workspace-wayland should give you a wayland session in sddm?
          Thanks. That makes it show up in SDDM, but not able to log in yet. Rebooting the VM and trying again.

          Please Read Me

          Comment


            #6
            SDDM error log:

            Code:
            2/6/18 3:53 PM    sddm-helper    pam_kwallet(sddm:auth): (null): pam_sm_authenticate
            2/6/18 3:53 PM    sddm-helper    pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
            2/6/18 3:53 PM    sddm-helper    pam_kwallet(sddm:setcred): pam_kwallet: pam_sm_setcred
            2/6/18 3:53 PM    sddm-helper    pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
            2/6/18 3:53 PM    sddm-helper    pam_unix(sddm:session): session opened for user stuart by (uid=0)
            2/6/18 3:53 PM    systemd    Created slice User Slice of stuart.
            2/6/18 3:53 PM    systemd-logind    New session 8 of user stuart.
            2/6/18 3:53 PM    systemd    Started Session 8 of user stuart.
            2/6/18 3:53 PM    systemd    Starting User Manager for UID 1000...
            2/6/18 3:53 PM    systemd    pam_unix(systemd-user:session): session opened for user stuart by (uid=0)
            2/6/18 3:53 PM    systemd    Reached target Paths.
            2/6/18 3:53 PM    systemd    Reached target Sockets.
            2/6/18 3:53 PM    systemd    Reached target Timers.
            2/6/18 3:53 PM    systemd    Reached target Basic System.
            2/6/18 3:53 PM    systemd    Reached target Default.
            2/6/18 3:53 PM    systemd    Startup finished in 18ms.
            2/6/18 3:53 PM    systemd    Started User Manager for UID 1000.
            2/6/18 3:53 PM    sddm-helper    pam_kwallet(sddm:session): pam_kwallet: pam_sm_open_session
            2/6/18 3:53 PM    sddm-helper    pam_kwallet(sddm:session): pam_kwallet: final socket path: /run/user/1000/kwallet.socket
            2/6/18 3:53 PM    sddm-helper    pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
            2/6/18 3:53 PM    sddm-helper    pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
            2/6/18 3:53 PM    sddm-helper    Starting: "/usr/share/sddm/scripts/wayland-session dbus-launch --exit-with-session /usr/bin/startplasmacompositor"
            2/6/18 3:53 PM    dbus-daemon    [session uid=1000 pid=1730] AppArmor D-Bus mediation is enabled
            2/6/18 3:53 PM    sddm-helper    pam_unix(sddm-greeter:session): session closed for user sddm
            2/6/18 3:53 PM    dbus-daemon    [session uid=1000 pid=1730] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=1000 pid=1751 comm="dbus-update-activation-environment --systemd --all" label="unconfined")
            2/6/18 3:53 PM    dbus-daemon    [session uid=1000 pid=1730] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
            2/6/18 3:53 PM    sddm-helper    pam_unix(sddm:session): session closed for user stuart
            2/6/18 3:53 PM    sddm-helper    pam_kwallet(sddm:session): pam_kwallet: pam_sm_close_session
            2/6/18 3:53 PM    sddm-helper    pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
            2/6/18 3:53 PM    sddm-helper    pam_kwallet(sddm:setcred): pam_kwallet: pam_sm_setcred
            2/6/18 3:53 PM    sddm-helper    pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
            2/6/18 3:53 PM    sddm-helper    pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
            2/6/18 3:53 PM    systemd    Started Session 10 of user sddm.
            2/6/18 3:53 PM    systemd-logind    New session 10 of user sddm.
            2/6/18 3:53 PM    sddm-greeter    High-DPI autoscaling Not Enabled
            2/6/18 3:53 PM    sddm-greeter    Loading file:///usr/share/sddm/themes/breeze/Main.qml...
            2/6/18 3:53 PM    sddm-greeter    QObject: Cannot create children for a parent that is in a different thread.
            (Parent is SDDM::GreeterApp(0x7ffd41bc9c70), parent's thread is QThread(0x55a3298391b0), current thread is QThread(0x55a329962640)
            2/6/18 3:53 PM    sddm-greeter    QObject: Cannot create children for a parent that is in a different thread.
            (Parent is SDDM::GreeterApp(0x7ffd41bc9c70), parent's thread is QThread(0x55a3298391b0), current thread is QThread(0x55a329962640)
            2/6/18 3:53 PM    sddm-greeter    QObject: Cannot create children for a parent that is in a different thread.
            (Parent is SDDM::GreeterApp(0x7ffd41bc9c70), parent's thread is QThread(0x55a3298391b0), current thread is QThread(0x55a329962640)
            2/6/18 3:53 PM    sddm-greeter    QObject: Cannot create children for a parent that is in a different thread.
            (Parent is SDDM::GreeterApp(0x7ffd41bc9c70), parent's thread is QThread(0x55a3298391b0), current thread is QThread(0x55a329962640)
            2/6/18 3:53 PM    sddm-greeter    QObject::installEventFilter(): Cannot filter events for objects in a different thread.
            2/6/18 3:53 PM    sddm-greeter    QObject: Cannot create children for a parent that is in a different thread.
            (Parent is SDDM::GreeterApp(0x7ffd41bc9c70), parent's thread is QThread(0x55a3298391b0), current thread is QThread(0x55a329962640)
            2/6/18 3:53 PM    dbus-daemon    [session uid=119 pid=1774] AppArmor D-Bus mediation is enabled
            2/6/18 3:53 PM    sddm-greeter    QObject: Cannot create children for a parent that is in a different thread.
            (Parent is SDDM::GreeterApp(0x7ffd41bc9c70), parent's thread is QThread(0x55a3298391b0), current thread is QThread(0x55a329962640)
            2/6/18 3:53 PM    sddm-greeter    QObject::installEventFilter(): Cannot filter events for objects in a different thread.
            2/6/18 3:53 PM    sddm-greeter    Cannot watch QRC-like path ":/icons/hicolor/index.theme"
            2/6/18 3:53 PM    sddm-greeter    file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
            2/6/18 3:53 PM    systemd-logind    Removed session 7.
            2/6/18 3:54 PM    systemd    Starting Cleanup of Temporary Directories...
            2/6/18 3:54 PM    systemd-tmpfiles    [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
            2/6/18 3:54 PM    systemd    Started Cleanup of Temporary Directories.

            Please Read Me

            Comment


              #7
              Installed a few more packages (there doesn't seem to be any depends at all) and I'm on Wayland.

              It's real jumpy video-wise in the VM and doesn't scale to the window, etc. Reddish boxes popping around the screen and menus flash on and off when interacting with it.

              I'll be interesting to do this on a bare metal install after April.

              Please Read Me

              Comment


                #8
                Running Debian sid, and living slightly in dread of the Wayland transition ...

                Comment


                  #9
                  wood...ummm yeah...no big deal smoke

                  Comment


                    #10
                    ya I just tried it on Kubuntu-17.10 and no joy ,,,,,at first just a Kubuntu logo ,,,,,,had to ctrl+alt+sysrq+s,u,b to reboot as no F key would give a TTY ,,,,then I "apt searched wayland" and installed every package that seemed pertinent,,,,reboot ,,,,just black screen

                    VINNY
                    i7 4core HT 8MB L3 2.9GHz
                    16GB RAM
                    Nvidia GTX 860M 4GB RAM 1152 cuda cores

                    Comment


                      #11
                      black screen...hmmmm

                      woodhmmsmoke

                      Comment


                        #12
                        Originally posted by vinnywright View Post
                        ya I just tried it on Kubuntu-17.10 and no joy ,,,,,at first just a Kubuntu logo ,,,,,,had to ctrl+alt+sysrq+s,u,b to reboot as no F key would give a TTY ,,,,then I "apt searched wayland" and installed every package that seemed pertinent,,,,reboot ,,,,just black screen

                        VINNY
                        Yea I don't think I would try a Wayland session right now on anything other than Neon Dev Edition + either Intel or AMD with opensource drivers. And still, even then, it's still early times.
                        ​"Keep it between the ditches"
                        K*Digest Blog
                        K*Digest on Twitter

                        Comment


                          #13
                          Originally posted by dequire View Post
                          Yea I don't think I would try a Wayland session right now on anything other than Neon Dev Edition + either Intel or AMD with opensource drivers. And still, even then, it's still early times.
                          OK I'll try that ,,,,,on Neon-/dev/stable that is ,but my 17.10 is as far up in plasma as the neon ,,,,,,but how knows .

                          VINNY
                          i7 4core HT 8MB L3 2.9GHz
                          16GB RAM
                          Nvidia GTX 860M 4GB RAM 1152 cuda cores

                          Comment


                            #14
                            Wow! So many negatives. Tell me again the logic for moving to Wayland.
                            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                            – John F. Kennedy, February 26, 1962.

                            Comment


                              #15
                              Originally posted by oshunluvr View Post
                              ...I guess I haven't figured out the magic sauce to getting Wayland to show in SDDM.
                              It does show up in Debian. You may need a .desktop file to convince SDDM to offer the option - I've had to do that to get stuff to show up in SDDM once or twice.

                              I'm not on a Linux box so I can't tell you where the .desktop files go, but they're somewhere in /usr IIRC.
                              we see things not as they are, but as we are.
                              -- anais nin

                              Comment

                              Working...
                              X