Bug 1098911 - qt apps over ssh -X will show empty, not responding window
Summary: qt apps over ssh -X will show empty, not responding window
Status: RESOLVED DUPLICATE of bug 1097227
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Factory
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-23 13:15 UTC by simon becherer
Modified: 2018-06-23 13:53 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description simon becherer 2018-06-23 13:15:49 UTC
Overview:
ssh from tumbleweed to tumbleweed starting a qt application like yast2 or dolphin or konsole will result in a empty not responding window.

Steps to Reproduce:
with only one tumbleweed system:

myself@mysystem:~> ssh -X mysystem
Have a lo of fun...
myself@mysystem:~> dolphin
Trying to convert empty KLocalizedString to QString.
qt.accessibility.core: Cannot create accessible child interface for object:  PlacesView(0x55953285cb10)  index:  12
(empty not responding window)


Actual Results:
not respoding, empty dolphin window


Expected Results:
the application window should open and qt-applictation (dolphin) should work.


Build Date & Hardware:
x86-64, kde/plasma/x11:
tumbleweed version tested: 20180618 and 20180620 (actual version)


Additional Builds and Platforms: 
Doesn't Occur on tumbleweed version 20180530


Additional Information:
reproduced from different users see:

https://lists.opensuse.org/opensuse/2018-06/msg01000.html
https://lists.opensuse.org/opensuse-factory/2018-06/msg00078.html

MAYBE this here is related:
1. https://bugreports.qt.io/browse/QTBUG-68449
2. https://cgit.freedesktop.org/xorg/xserver/commit/?
id=3c4cead499f10dabac20ab87728746ec41dae799


simoN
Comment 1 Wolfgang Bauer 2018-06-23 13:53:28 UTC
A fix is in Factory already and should be available with the next snapshot.

*** This bug has been marked as a duplicate of bug 1097227 ***