Windows look broken when enlarged

Hi everybody!

I need some help.

Some windows when maximized or enlarged glitch out. like that

The window top bar and area clipping vanishes when the menu I click on a different menu entry.

I am using X11 since I need Discord which sadly crashes on Wayland at start.

What kind of terminal output to provide for diagnostics. Here’s my inxi -G

Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel
  Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.2 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915
    resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 22.1.3

And inxi -S and inxi -M

System:
  Host: fedora Kernel: 5.18.9-200.fc36.x86_64 arch: x86_64 bits: 64
    Desktop: GNOME v: 42.3.1 Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Laptop System: Dell product: Latitude E5470 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0VHKV0 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.30.3 date: 03/28/2022

Can it be a GTK4 bug?

Still having that issue, any help would be appreciated.

As I have been experiencing that issue, it looks like it is connected to the load time from BTRFS partition with @ and @home subvolumes.

Is there a way to make the load time from BTRFS faster?

It looks like you’re running Xorg. I’m curious if you don’t see this go away if you switch back to Wayland, since Wayland is better at preventing tearing.

There is no tearing with Wayland indeed @vwbusguy Strangely for me, Disord crashes immediately on Wayland, so I need to run it. Also my experience with screen sharing software has been, that it doesn’t yet support Wayland for their own reasons.

Any ideas how to remove screen tearing on X11?

wayland is the future so you should bug report to discord about this.
even in the next release xorg will be removed from the default packages
https://fedoraproject.org/wiki/Releases/37/ChangeSet#Changes/LegacyXorgDriverRemoval
1.18

@frankjunior How do I exactly bug report? How where to search for the place to do that. It might be a general intelligence thing, but sadly I am not a developer

The bug reporting program in Fedora is unable to extract the error. Have reported some things I found through there.

Thank you for replying and helping with the advice. I have been cataloguing my attempts to understand and solve that issue for quite a long time. At least It has been on my mind.

i think it will help you
https://support.discord.com/hc/en-us/articles/360046057772-How-do-I-submit-a-bug-
else you can always tweet them about the issue or ask them about bug report.

Thank you for being proactive.

I’ll make use of that link. Thank you.

It’s curious that I didn’t have any window tearing on Debian 11 stable (Gnome 3.38) on Xorg.

Needed to share to share the screen - most apps which do that don’t support Wayland. Zoom flat out doesn’t let share the screen - just tells you to change to Xorg.

watch for sure newer gnome 42 is just released so we can expect some small bugs but as i have told you wayland is the future and more secure you can search for and more advance and simple code base unlike xorg. so as we are transitioning to wayland so it is safe to use all apps in wayland to be safe and secure. hence i have suggested that and it can be reported to fedora or gnome about it but it will waste time for devs as xorg is depreciating sooner or later.
havnt tested yet on other distros with gnome 42 but it seems like a gnome bug.
if you want to report it to gnone it can be done on gitlab.

Just bunch of my messaging apps (almost all) crashed on launch on Wayland. I guess, it means a- Paperwork!!

That’s odd. It works great for me with Wayland. I believe I’m using the rpm packaged version instead of the flatpak, if that matters.

I’m using flatpak for slack and zoom with Wayland and those notes generally work for me as well.

Maybe I should try to find RPMs. Not sure if all of them have.

Where did you get the discord RPM?

Discord client is available in RPMFusion (you’ll need to enable both free and non-free repos).

1 Like

Interesting. We have reduced it to flatpak issue. All my com-apps are flatpaks.

1 Like

Verified! RPM Discord works on Wayland.

1 Like

nope that is not the case i use matrix and signal on my wayland system i never see a crash. there must be some issue in your system. i will check this apps download from flathub and try crash or not.

Here you are!

System:
  Kernel: 5.18.13-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-27.fc36 Desktop: GNOME v: 42.3.1
    Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Laptop System: Dell product: Latitude E5470 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0VHKV0 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.31.3 date: 06/07/2022
Battery:
  ID-1: BAT0 charge: 37.6 Wh (100.0%) condition: 37.6/57.1 Wh (65.8%)
    volts: 8.3 min: 7.6 model: Panasonic DELL 79VRK6A status: full
CPU:
  Info: dual core model: Intel Core i5-6300U bits: 64 type: MT MCP
    arch: Skylake rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 2943 high: 3001 min/max: 400/3000 cores: 1: 2904
    2: 2965 3: 2902 4: 3001 bogomips: 19999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell driver: i915
    v: kernel arch: Gen9 bus-ID: 00:02.0
  Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-2:2
  Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 22.1.4
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.18.13-200.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel bus-ID: 01:00.0
  IF: wlp1s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-8:5
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0
Drives:
  Local Storage: total: 238.47 GiB used: 42.37 GiB (17.8%)
  ID-1: /dev/sda vendor: Intel model: SSDSCKKF256H6 SATA 256GB
    size: 238.47 GiB
Partition:
  ID-1: / size: 236.89 GiB used: 42.13 GiB (17.8%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 973.4 MiB used: 204.7 MiB (21.0%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 598.8 MiB used: 45.7 MiB (7.6%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 236.89 GiB used: 42.13 GiB (17.8%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 58.0 C pch: 48.5 C mobo: 41.0 C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 269 Uptime: 3h 29m Memory: 15.42 GiB used: 3.87 GiB (25.1%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.1.1 Packages: 12
  note: see --pkg Shell: fish v: 3.5.0 inxi: 3.3.19

tried with discord does not crash in my system running wayland.downloaded from flathub

Is there any info I can paste to find the bug.

I guess the error for signal was SIGSERV

EDIT:

Ran all flatpak messaging apps I have in terminal - outputs:

**Whatsapp**
> flatpak run com.github.eneshecan.WhatsAppForLinux
logger: socket /dev/log: No such file or directory
marko@fedora ~ [SIGABRT]

**Caprine**
> flatpak run com.sindresorhus.Caprine
marko@fedora ~ [SIGSEGV]

**Element**
> flatpak run im.riot.Riot
/home/marko/.var/app/im.riot.Riot/config/Element exists: yes
/home/marko/.var/app/im.riot.Riot/config/Riot exists: no
LaunchProcess: failed to execvp:
xdg-settings
[3:0725/215627.910171:ERROR:ozone_platform_x11.cc(248)] Missing X server or $DISPLAY
[3:0725/215627.910266:ERROR:env.cc(226)] The platform failed to initialize.  Exiting.
/app/bin/element: line 10:     3 Segmentation fault      (core dumped) env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"
marko@fedora ~ [SIGSEGV]

**Jitsi Meet**
flatpak run org.jitsi.jitsi-meet
LaunchProcess: failed to execvp:
xdg-settings
[3:0725/215703.240394:ERROR:ozone_platform_x11.cc(248)] Missing X server or $DISPLAY
[3:0725/215703.240444:ERROR:env.cc(226)] The platform failed to initialize.  Exiting.
/app/bin/jitsi-meet-run: line 2:     3 Segmentation fault      (core dumped) zypak-wrapper /app/bin/jitsi-meet/jitsi-meet "$@"
marko@fedora ~ [SIGSEGV]

**Signal Desktop**
flatpak run org.signal.Signal
Debug: Will run signal with the following arguments: 
Debug: Additionally, user gave: 
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /app/Signal/resources/app.asar/config
NODE_CONFIG {}
ALLOW_CONFIG_MUTATIONS undefined
HOSTNAME undefined
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
SIGNAL_ENABLE_HTTP undefined
userData: /home/marko/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[2:0725/215715.266958:ERROR:ozone_platform_x11.cc(248)] Missing X server or $DISPLAY
[2:0725/215715.267055:ERROR:env.cc(226)] The platform failed to initialize.  Exiting.
marko@fedora ~ [SIGSEGV]