Hi, since I yesterday upgraded 2 TW installs with KDE to latest TW snapshots, both 20210212 as well as 20210215, and since then Skype (latest version from its own repo) seems to be running in background well, i.e. it notifies me about new message and so on, but the window doesn't render at all, it contains basically background, so it's not usable at all. I wonder if this could be related to possible sandboxing issue mentioned by Dominique at Tuesday, but I have 64bit systems, and I have libqt5-qtwebengine 5.15.2-6.1 from tw-update. Any idea what could be wrong?
On Thu, Feb 18, 2021 at 10:54 AM Vojtěch Zeisek vojtech.zeisek@opensuse.org wrote:
Hi, since I yesterday upgraded 2 TW installs with KDE to latest TW snapshots, both 20210212 as well as 20210215, and since then Skype (latest version from its own repo) seems to be running in background well, i.e. it notifies me about new message and so on, but the window doesn't render at all, it contains basically background, so it's not usable at all. I wonder if this could be related to possible sandboxing issue mentioned by Dominique at Tuesday, but I have 64bit systems, and I have libqt5-qtwebengine 5.15.2-6.1 from tw-update. Any idea what could be wrong?
It renders and works fine for me. Maybe you can try to disable KDE's compositor to see what happens...
Dne čtvrtek 18. února 2021 14:09:19 CET jste napsal(a):
On Thu, Feb 18, 2021 at 10:54 AM Vojtěch Zeisek wrote:
Hi, since I yesterday upgraded 2 TW installs with KDE to latest TW snapshots, both 20210212 as well as 20210215, and since then Skype (latest version from its own repo) seems to be running in background well, i.e. it notifies me about new message and so on, but the window doesn't render at all, it contains basically background, so it's not usable at all. I wonder if this could be related to possible sandboxing issue mentioned by Dominique at Tuesday, but I have 64bit systems, and I have libqt5-qtwebengine 5.15.2-6.1 from tw-update. Any idea what could be wrong?
It renders and works fine for me. Maybe you can try to disable KDE's compositor to see what happens...
Hmmm... Compositor doesn't seem to be responsible here... It keeps behaving same, I haven't figured out what could be causing it... :-(
-
Stratos Zolotas -
Vojtěch Zeisek