[screen sharing] stride misalignment during rasterization on the receiver end

Bug report form

Describe your environment

Please specify the following:

• OS: Fedora Linux 40 (KDE Plasma)
• Jami version: 202405291734
• What build you are using: dnf repository from Fedora

Steps to reproduce

• I can reproduce the bug whenever I want it.

To do so,

1. Login to a Wayland session
2. Audio/Video Call another user
3. Start sharing screen

• Actual result: The Screen should be mirrored as is.
• Expected result: The screen ends up tearing as if the computer crashed.

Additional information

I can share my screen normally under a X11 Session. I tried my best to run it via XWayland. But no luck there.

---

It would be best to fix this as more DEs are going fully wayland. Finding the specific package to enable x11 was quite tedious when I was trying to do a serious call.

That looks like stride misalignment. Screen tearing is the term usually used to describe vertical synchronization issues. I will adjust the title and categorize the issue.

changed title from Screen sharing - Screen tears on the receiver end - Wayland to Screen sharing - stride misalignment during rasterization on the receiver end - Wayland

changed title from Screen sharing - stride misalignment during rasterization on the receiver end - Wayland to [screen sharing] stride misalignment during rasterization on the receiver end - Wayland

changed title from [screen sharing] stride misalignment during rasterization on the receiver end - Wayland to [screen sharing] stride misalignment during rasterization on the receiver end

added platformlinux severitymedium bug wayland labels

Are there any fixes to this because I am relying on Jami for important Communications on a day-to-day basis which requires Screen Sharing about 90% of the time.

I understand that this is a FOSS project but I really need this to be fixed. Cuz, I have been switching between Wayland and X11 multiples times a day because of this.

To be clear, is this a issue by Jami or Wayland ?

It could be a Jami issue. I'll check tomorrow and get back to you.

Thanks for the heads up. Awaiting for your reply.

There was in fact an issue that caused the stride value to sometimes be incorrect. I already wrote a fix for it; it's going to be included in the next release.

assigned to @ffauteux-chapleau

added sprintin progress label

added sprintdone label and removed sprintin progress label

closed