[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#818519: libqt5core5a: KDE apps randomly switch to unmapped state (hidden)



Package: libqt5core5a
Version: 5.5.1+dfsg-16
Severity: important

Dear Maintainer,

After last upgrade from sid a week ago, several KDE apps randomly switch to "Unmapped" state,  becoming invisible even in the task bar.
I can see they are unmapped via xwininfo, the only way to recover i found is with xdotool (or killing them by command line).

Ex.
$ xdotool search --pid `pidof kate`
119538548
119539507
119540209

$ xwininfo -id 119538548 | grep 'Map State'
Map State: IsUnMapped

$ xdotool windowmap --sync 119538548

Note they are not moved to another virtual desktop or activity. I have only 1 activity and 1 virtual desktop, spanning over two screens.
The issues seems to raise when the system get locked for inactivity but i was not able to confirm that every time.
Also I experience that mostly with Kate and Konsole as they are the KDE5 apps i uses more often but i suppose others KDE5 apps would be affected too.
The others always-open app i use is Firefox which seems unaffected (that's why i am guessing the issue is linked to KDE5 only).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (870, 'unstable'), (850, 'testing'), (825, 'experimental'), (800, 'stable'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5core5a depends on:
ii  libc6         2.22-3
ii  libgcc1       1:5.3.1-11
ii  libglib2.0-0  2.46.2-3
ii  libicu55      55.1-7
ii  libpcre16-3   2:8.38-3
ii  libstdc++6    5.3.1-11
ii  zlib1g        1:1.2.8.dfsg-2+b1

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.5.1-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.24-2

-- no debconf information


Reply to: