Sync Updates for Week 30, 2023

Fanmion The most important thing you can provide me with is the log file I asked for.

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.

ReillyBrogan How can I get the log file?

Fanmion If you just opened a terminal and didn't cd somewhere then the file is in your home folder. Just open it like a normal file and paste it into pastebin.

ReillyBrogan Last time I used Wayland for screen capture has been a few months. Yes I used the Pipewire API and it stutters a lot so I ditched it. But I'm glad you explain it to me, so I can be sure my problems were never a Wayland problem, but components around Wayland. So I can say the infrastructure around Wayland is unusable for me yet? I don't really know why I can't click during a game.

ReillyBrogan Which file do you want? .profile?

Fanmion Run the following command sudo journalctl -b0 > issues.log. Remind me, what issue did you have? There's a 156 posts in this thread now and I may have gotten you confused with someone else I asked.

It would be incredibly helpful if someone experiencing the issue with swap partitions not mounting or the boot getting stuck at the rescue console could hop onto the Solus Matrix tomorrow between 4PM and 11PM UTC tomorrow for some debugging. I'm hoping to have this figured out before I do kernel builds tomorrow so the fix rolls out in the next sync (oh btw, the next sync is including kernel 6.4).

Fanmion

I'm not Reilly, but if you don't post the data he asked for, he likely can't help you.

I'm going to suggest that you are the best judge of whether anything you see in the log is "safe" enough for being posted in public. If in doubt, you can always view it in a text editor before posting it here.

Best of luck.

I will post it into our matrix server, because I can't upload files =(

Fanmion I will post it into our matrix server, because I can't upload files =(

You can open the file by navigating to your home folder with your file manager, open the file with a graphical text editor application like KWrite/Kate/Gedit etc., mark all the text, copy it to the system clipboard and then paste it here enclosed in triple backticks like this:

```
(paste the stuff you copied here)
```

Do you think you could do that?

EbonJaeger

Sorry nothing changed. installed from unstable * tpm2-tss 3.2.0-2-1-x86_64 is , rebooted twice, but no dice. Unicode input does not work.

Update: I believe I have fixed the swap issue and the boot issue in unstable. This fix will roll out for the next sync. However, if you want this working now you can edit /etc/systemd/system.conf and change:

#DefaultTimeoutStartSec=5s

To:

DefaultTimeoutStartSec=30s

And:

#DefaultDeviceTimeoutSec=5s

To:

DefaultDeviceTimeoutSec=30s

Note the removal of the # symbol. This should fix it immediately and things should work again on the next boot.

ReillyBrogan

• for cat /etc/fstab :
  https://pastebin.mozilla.org/aidGDaoX#L1

• for sudo mount :
  https://pastebin.mozilla.org/p4PVLBaf#L1

• for sudo blkid :
  https://pastebin.mozilla.org/d2wpgR0k#L1

alexxtasi Thanks, but I'm pretty sure I've already figured out the issue and it actually had nothing to do with the UUIDs and everything to do with the default timeouts having been set too low. This issue will be fixed in the sync today, or you can follow the instructions here

dassuan So I wonder if this touches the unicode input problem

No, the unicode input issue has already been figured out and is an issue in ibus. A fixed version of ibus will be rolling out in the sync shortly.