Skip to content
  • 0 Votes
    3 Posts

    @ambershark Thanks for the input. I was afraid the window manager changes might be the issue. We are using KDE as our window manager. I have limited control on what I am allowed to change unfortunately. For now, I will likely move forward with work around. Since the applications dialogues now appear in the task bar, there is little downside to minimizing them. The issue was they would simply get "lost" when they were minimized. I was able to remove the maximize button by setting fixed size restraints on the dialogues. I will update the post if I ever figure out how to get the KDE settings and the Qt Window Flags to play nicely together. I have been investigating the kwindecorations settings, but had no luck yet.

  • 0 Votes
    2 Posts


    IIRC, that's part of the GNOME Human Interface Guidelines so there's no much you can do from a Qt point of view.

  • 1 Votes
    1 Posts
    No one has replied
  • 0 Votes
    4 Posts

    Yes use another distro than rhel v6.7 :)

  • 0 Votes
    1 Posts
    No one has replied
  • 0 Votes
    5 Posts

    Well ... someone in a corporate environment here [1] really suffering from this bug after upgrading to openSUSE Leap 42.1 which ships with Plasma 5. Considering openSUSE Leap and SUSE Linux Enterprise Server are now so tightly coupled in development I suspect this bug will start to affect more and more users.

    I would like to add that sometimes it's not just an extra warning, but actually blocks the UI.

    Running strace on kwrite opening a file from a NFSv4 drive results in the following messages:

    open("/NFSv4mount/home/user/.config/kwriterc.lock", O_WRONLY|O_CREAT|O_EXCL|O_CLOEXEC, 0644) = 9
    fcntl(9, F_SETFD, FD_CLOEXEC) = 0
    flock(9, LOCK_EX|LOCK_NB) = 0
    fcntl(9, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1 EAGAIN (Resource temporarily unavailable)
    write(2, "setNativeLocks failed: Resource "..., 56setNativeLocks failed: Resource temporarily unavailable
    ) = 56
    write(9, "24895\nkwrite\nPC-123456\n", 23) = 23
    open("/NFSv4mount/home/user/.config/kwriterc.lock", O_RDONLY|O_CLOEXEC) = 12
    fcntl(12, F_SETFD, FD_CLOEXEC) = 0
    fstat(12, {st_mode=S_IFREG|0644, st_size=23, ...}) = 0
    fstat(12, {st_mode=S_IFREG|0644, st_size=23, ...}) = 0
    read(12, "29337\nkwrite\nPC-123456\n", 16384) = 23
    read(12, "", 16361) = 0
    close(12) = 0
    uname({sysname="Linux", nodename="PC-123456", ...}) = 0
    kill(29337, SIG_0) = -1 ESRCH (No such process)
    open("/NFSv4mount/home/user/.config/kwriterc.lock", O_WRONLY|O_CLOEXEC) = 12
    fcntl(12, F_SETFD, FD_CLOEXEC) = 0
    flock(12, LOCK_EX|LOCK_NB) = 0
    fcntl(12, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1 EAGAIN (Resource temporarily unavailable)
    close(12) = 0
    close(9) = 0
    unlink("/NFSv4mount/home/user/.config/kwriterc.lock") = 0
    nanosleep({6, 400000000}, 0x7ffd3a249730) = 0

    (the nanosleep timer just increases, meanwhile the kwrite window stays "blank" (actually whatever the background of the window was when it was started)).

    If I intervene and remove this file kwrite immediately returns and shows the file. And in subsequent starts the file opens immediately.

    Perhaps a workaround would be to move my .config directory back to local disk and place a symlink in my home folder to this on disk location.

    Relevant bug report:

    My corporate environment, for those interested:
    [1] Using sssd.conf: services = nss, pam, autofs
    Using ldap to login, automount to mount a NFSv4 Kerberized mount.