Bug 414377 - Freeze or graphical glitches after app throws "gtk-warning: infinite surface size not supported" in Konsole
Summary: Freeze or graphical glitches after app throws "gtk-warning: infinite surface ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.17.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-21 19:14 UTC by postix
Modified: 2020-02-07 13:02 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Video of the graphical glitches of Konsole due to the gtk issue. 1/2 (1.11 MB, video/mp4)
2019-11-24 11:33 UTC, postix
Details
Video of the graphical glitches of Konsole due to the gtk issue. 2/2 (2.06 MB, video/mp4)
2019-11-24 11:34 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2019-11-21 19:14:55 UTC
SUMMARY

The GTK/Vala app Dino let the whole plasmashell freeze when it is started in Konsole.
This does not happen if it is started outside of Konsole.
In order to recover, Dino has to be killed in another TTY.

I will try to get a backtrace of the stack later.

STEPS TO REPRODUCE
1. git clone https://github.com/dino/dino (f9c69a204ebd7ecabd022f6f6e9a7131a1ecadae)
2. Compile Dino
3. Execute "dino" in Konsole

OBSERVED RESULT

Dino throws gtk-errors:

(dino:14997): Gdk-WARNING **: 20:03:22.102: Native Windows wider or taller than 32767 pixels are not supported

(dino:14997): Gdk-WARNING **: 20:03:22.108: Native Windows wider or taller than 32767 pixels are not supported

(dino:14997): Gtk-WARNING **: 20:03:22.387: infinite surface size not supported

(dino:14997): Gtk-WARNING **: 20:03:22.389: infinite surface size not supported

(dino:14997): Gtk-WARNING **: 20:03:22.390: infinite surface size not supported

...

and the whole Plasmashell freezes.

EXPECTED RESULT

Dino starts without causing issues obviously.



SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2
Kernel Version: 5.3.11-1-MANJARO

ADDITIONAL INFORMATION

Scaling 1.5
Comment 1 postix 2019-11-24 11:33:18 UTC
Created attachment 124093 [details]
Video of the graphical glitches of Konsole due to the gtk issue. 1/2

Dino is started and gtk starts throwing gtk warnings in an infinite loop. There of course those horizontal line artifacts but additional the rendered Konsole image is not refreshed correctly as it can seen at the mouse trail.
Comment 2 postix 2019-11-24 11:34:00 UTC
Created attachment 124094 [details]
Video of the graphical glitches of Konsole due to the gtk issue. 2/2

Here the whole can be still dragged but earlier renderings are not cleared.
Comment 3 postix 2019-11-24 12:12:10 UTC
If try to run Dino in Konsole under Wayland, I get the following error only:

(dino:15020): Gdk-CRITICAL **: 13:07:28.826: ../gtk/gdk/wayland/gdkdisplay-wayland.c:1399: Unable to create Cairo image surface: invalid value (typically too big) for the size of the input (surface, pattern, etc.)


and then Dino crashes with a SIGSEGV.
Comment 4 postix 2019-12-03 13:44:33 UTC
Maybe this is more an issue of KWin actually as it is about painting the desktop.
Comment 5 postix 2019-12-03 13:46:43 UTC
It does no longer freeze the whole plasmashell, but still gives those graphical glitches, which can be seen in the attached videos.
Comment 6 Patrick Silva 2020-02-07 11:57:10 UTC
At least Dino 0.1.0-3 from Arch repos works fine.
I can't reproduce any issue described here with it.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Comment 7 Vlad Zahorodnii 2020-02-07 12:40:29 UTC
(In reply to Postix from comment #5)
> It does no longer freeze the whole plasmashell, but still gives those
> graphical glitches, which can be seen in the attached videos.
Are you talking the horizontal line artifacts?
Comment 8 Vlad Zahorodnii 2020-02-07 12:40:50 UTC
*Are you talking about ...
Comment 9 postix 2020-02-07 13:02:08 UTC
Sorry, I forgot to update this issue. The bug seems to be magically gone. :)