Package: plasma-workspace / 4:5.14.5.1-1

Metadata

Package Version Patches format
plasma-workspace 4:5.14.5.1-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
disable_incompatible_tests | (download)

kioslave/desktop/tests/CMakeLists.txt | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 disable_incompatible_tests

===================================================================

add_sddm_debian_breeze.patch | (download)

CMakeLists.txt | 14 14 + 0 - 0 !
sddm-theme-debian/metadata.desktop | 17 17 + 0 - 0 !
sddm-theme-debian/theme.conf | 4 4 + 0 - 0 !
3 files changed, 35 insertions(+)

 add sddm's debian-breeze theme

Breeze with Debian's default background

replace fds.patch | (download)

ksplash/ksplashqml/main.cpp | 20 13 + 7 - 0 !
1 file changed, 13 insertions(+), 7 deletions(-)

 not close stdin,stdout,stderr, and redirects stdin,stdout,stderr

This fix a bug in ksplashqml. An upstream commit
https://cgit.kde.org/plasma-workspace.git/commit/?id=56d2c15b9acb9c4b57398b281685807c3191f622
has caused this problem.

 x-session-manag,133,kdetest /usr/bin/x-session-manager
   +-(ksplashqml,232)
   +-ssh-agent,191 /usr/bin/im-launch x-session-manager
   +-uim-toolbar,220
   |   +-{llvmpipe-0},235
   |   +-{llvmpipe-1},236
   |   +-{llvmpipe-2},237
   |   `-{llvmpipe-3},238
   `-uim-xim,219
 ksplashqml,233,kdetest Breeze --pid
   +-mozc_server,239
   |   +-{IPCServer},244
   |   +-{QueueTimer},240
   |   +-{QueueTimer},243
   |   `-{WatchDog},242
   +-uim-candwin-qt5,245 -v
   |   +-{QDBusConnection},249
   |   `-{QXcbEventReader},248
   |-{QDBusConnection},255
   |-{QQmlThread},254
   |-{QXcbEventReader},234
   |-{llvmpipe-0},250
   |-{llvmpipe-1},251
   |-{llvmpipe-2},252
   `-{llvmpipe-3},253
 
 # strace -f -p 133
 strace: Process 133 attached
 read(3, ^Cstrace: Process 133 detached
  <detached ...>
 
 It looks like the parent process (133), x-session-manager (startkde
 script), is waiting for the stdout of the ksplashqml process (232),
 but which is now defunct. Its child process(es) may be writing to the
 same fd.
 
 # ls -l /proc/133/fd/3
 lr-x