after sync I get this error at boot:

[!!!!!!] Failed to start up manager.
[11.179840] systemd[1]: Freezing execution.

Most of the times restarting solves the problem and I can login succesfully, but today it needed 5 tries.

    Fanmion Did you perform the steps under "Severe lagginess loading applications in GNOME" in the known issues in the top thread?

      I updated all my computers this morning (Budgie, Plasma), all went smooth.

      Thank you very much to the team !

      • [deleted]

      Fanmion Do you mean the file picker?

        [deleted] I think so. Like Nautilus doesn't want to communicate with anyone. I can't upload any file into my cloud.

        Fanmion Step by step instructions for reproducing the issue (preferably with pictures if you're having trouble describing what you mean) would be very useful for us to help troubleshoot your issue. It seems like your issue is very uncommon/rare since nobody else seems to fully understand what you're talking about.

          • [deleted]

          • Edited

          ReillyBrogan To me it seems like an issue with desktop portals. Was there a change regarding them recently?

            [deleted] We added xdg-desktop-portal-gnome to GNOME installs, but using the dbus-broker fix above resolves the only known issue with it. That's why we're asking for reproduction steps as it appears to be a new issue and Fanmion already did the dbus-broker steps.

            alexxtasi I really want logs from someone experiencing this issue.

            From a boot where you experienced the issue and were able to bypass it by hitting CTRL+D please run the following:

            sudo journalctl -b0 > initrd-issue.log

            And then upload that the pastebin/hastebin and post the link here.

              nolan UNIT >
              proc-sys-fs-binfmt_misc.automount >
              sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backlig>
              sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d1.device >
              sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d10-1\x2d10:1.0-bluetooth-hci0.d>
              sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d5-1\x2d5.2-1\x2d5.2.3-1\x2d5.2.>
              sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d5-1\x2d5.2-1\x2d5.2.4-1\x2d5.2.>
              sys-devices-pci0000:00-0000:00:1d.1-0000:04:00.0-net-wlp4s0.device >
              sys-devices-pci0000:00-0000:00:1d.4-0000:07:00.0-nvme-nvme0-nvme0n1-nvme0n1p1>
              sys-devices-pci0000:00-0000:00:1d.4-0000:07:00.0-nvme-nvme0-nvme0n1-nvme0n1p2>
              sys-devices-pci0000:00-0000:00:1d.4-0000:07:00.0-nvme-nvme0-nvme0n1-nvme0n1p3>
              sys-devices-pci0000:00-0000:00:1d.4-0000:07:00.0-nvme-nvme0-nvme0n1.device >
              sys-devices-pci0000:00-0000:00:1f.3-sound-card0-controlC0.device >
              sys-devices-pci0000:00-0000:00:1f.6-net-enp0s31f6.device >
              sys-devices-platform-serial8250-tty-ttyS0.device >
              sys-devices-platform-serial8250-tty-ttyS1.device >
              sys-devices-platform-serial8250-tty-ttyS2.device >
              sys-devices-platform-serial8250-tty-ttyS3.device >
              sys-devices-platform-thinkpad_acpi-leds-tpacpi::kbd_backlight.device >
              sys-devices-virtual-block-ram0.device >
              sys-devices-virtual-block-ram1.device >
              sys-devices-virtual-block-ram10.device >
              sys-devices-virtual-block-ram11.device

              ReillyBrogan I would like to show you pictures if I can upload some xD. When I'm o getsol.us and want to download the new ISO, so I'm clicking on the download button and nothing happens. BUT: somehow Gnome Web works as usual, but I don't want to use Gnome Web.

                Staudey Just wanted to show an indicator that most people are happy with leaving X11, replacing mate with xfce. With time and additional support those numbers will increase. And this distrowatch survey shows it. So people are generally more optimistic and I'm one of them. Gnome on wayland is a standard way today.

                  WhiteWolf Generally yes! But Wayland is not ready for Gaming/Streaming. Wayland does not have Capture API, so high quality Twitch Streams are not possible. Wayland has still issues recognizing mouse clicking during a game. Forced V-Sync of Wayland makes playing League of Legends not enjoyable coz of high input lag. So I hope solus doesn't ditch X11 soonly.

                    alexxtasi Show me the output of cat /etc/fstab, sudo mount, and sudo blkid. It looks like your boot error is likely that some of the partitions you have listed in your /etc/fstab are failing to mount properly.

                      DirtyAngel I don't know what you mean by that. Solus having a weekly sync thread is a new thing that we've implemented and I'm just trying to get people used to using it. As I previously stated, the issue you reported is a known issue and the solution is in the OP of this thread. You can also just wait for the next sync where it'll be fixed automatically upon updating.

                      Fanmion Wayland is plenty ready for gaming. I game on it most nights.

                      Fanmion But Wayland is not ready for Gaming/Streaming

                      A capture API is out of scope for Wayland. This API is provided by PipeWire and exposed by XDG-Desktop-Portals to whatever app needs the stream. If the app you're trying to use does not support this then it's not the fault of Wayland, it's the lacking support in the app you're trying to use. OBS has full support for this for example.

                      Fanmion Forced V-Sync of Wayland makes playing League of Legends not enjoyable coz of high input lag

                      Tearing support in Wayland is in progress and support is being merged into the various components. Expect it sooner than later. Also, this isn't an actual issue if you are using a VRR capable monitor as they wait for the completed frame anyway. It's also really only noticeable at 60fps and below, the impact is only ever 1 frame so if you're on 120hz+ it becomes imperceptible.

                      Fanmion Wayland has still issues recognizing mouse clicking during a game

                      Wayland is a protocol. There is no Wayland "server" so it's inaccurate to say that Wayland has issues recognizing mouse clicks. What you mean is that either your compositor (Mutter (GNOME)/kwin (Plasma)/wlroots (Sway, others)) or Xwayland (most likely) has this issue. You should research around, it's probably a known issue and we could potentially get the fix if we were linked to a bug report.

                      Sebastian The reality of Solus is that Solus is by and large developed by people who want to improve their own experience. Those individuals largely listen to other people working on developing Solus. If you really want a voice in how Solus develops the correct way is to learn packaging so you can start improving Solus.