KDE not showing any window borders in 18.03

[arianvp]

Issue description

I just updated to 18.03 and KDE is broken. I can't close or resize windows anymore as window decorations are not displayed

Steps to reproduce

Upgrade to 18.03

Technical details

I can't as I can't open a browser on the machine

[arianvp]

Sorry for the terse description but I can't open a web browser on the machine. Or at least. I can't make the window focus..

[arianvp]

[jasoncarr0]

Can't reproduce. It may be due to the configuration in your home directory. If you move that out (~/.kde, and a number of files in ~/.config), does the issue persist? Are there any other details about your computer?

[bkchr]

Try to execute kwin_x11 --replace and see if that crashes.

[bkchr]

Yeah, @arianvp should try that. If for you everything works, I did not expect anything else ;)

[arianvp]

When I'm home I'll investigate further :)

…

On Sat, Apr 14, 2018, 09:17 Bastian Köcher ***@***.***> wrote: Yeah, @arianvp <https://github.com/arianvp> should try that. If for you everything works, I did not expect anything else ;) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#38870 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAmWo5JwwFNeiHFzfd8WrWjuqYLkaal4ks5toaKmgaJpZM4TSekx> .

[lheckemann]

Possible dup of #38752

[chreekat]

After running 18.03 for a day, this suddenly started happening for me, as well. I rolled back to 17.09 and rebuild 18.03 just to be certain, and it still happens. I'll try the step bkchr mentioned above.

[chreekat]

$ nix-info
system: "x86_64-linux", multi-user?: yes, version: nix-env (Nix) 1.11.16, channels(root): "nixos-18.03.132083.06c576b0525", channels(b): "unstable-18.09pre135256.6c064e6b1f3", nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

EDIT: That info is from the rolled-back 17.09. Let me rerun from 18.03.

[chreekat]

This does look like a dupe of #38752, though I'm not sure how that helps me :)

[chreekat]

nix-info from the broken 18.03:

• system: "x86_64-linux"
• host os: Linux 4.14.35, NixOS, 18.03.132083.06c576b0525 (Impala)
• multi-user?: yes
• sandbox: no
• version: nix-env (Nix) 2.0
• channels(root): "nixos-18.03.132083.06c576b0525"
• channels(b): "unstable-18.09pre135256.6c064e6b1f3"
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Maybe it's time to switch away from KDE.

[bkchr]

@chreekat did it fix your installation to delete the config folder?

[chreekat]

I will try that and let you know. On Apr 22, 2018 15:36, "Bastian Köcher" <notifications@github.com> wrote: @chreekat <https://github.com/chreekat> did it fix your installation to delete the config folder? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#38870 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAg3qg7P1kXZrDcEhwcIsWxj8XNA6Myzks5trNu4gaJpZM4TSekx> .

[chreekat]

@bkchr I removed everything I could find (~/.kde and anything vaguely kde or plasma in ~/.config), and it didn't help. journalctl still says:

Apr 23 09:12:52 fuzzbomb kernel: kwin_x11[1364]: segfault at 4 ip 00007f414ff1ca98 sp 00007ffd5e041820 error 4 in libxkbcommon.so.0.0.0[7f414ff00000+3e000]

[bkchr]

@chreekat which GPU are you using?

I found a similar bug report for gnome: https://bugzilla.redhat.com/show_bug.cgi?id=1462507
Do you also use wayland?

[chreekat]

I am using X11. I have some integrated graphics, probably Intel. NixOS doesn't seem to have lspci, and I'm not sure what else to use to look up the info. lshw doesn't give anything useful.

Ah, the GNOME 'about' pages says, "Intel® Haswell Mobile".

[lheckemann]

NixOS doesn't seem to have lspci

nix-shell -p pciutils --run lspci or nix-env -f '<nixpkgs>' -iA pciutils then try again.

[chreekat]

Thanks,

00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)

I said "seems to not have" because I got no prompt to install a particular package, as I sometimes do with missing utilities, and I am not sure how to map particular utilities to particular packages. Except for grepping the sources, I suppose, which I could have done...

[jasoncarr0]

I'm now getting the issue, with the same error as chreekat (kwin_x11[1364]: segfault at 4 ip 00007f414ff1ca98 sp 00007ffd5e041820 error 4 in libxkbcommon.so.0.0.0[7f414ff00000+3e000]). Similarly affecting old generations. Have cleared out ~/.config, ~/.kde /var, /tmp
Have attempted to clear out most qt-using packages from user environment. Currently the only version from 5.10.1 is the phonon backend using 5.6 on my most recent generation

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)

[jasoncarr0]

My error was likely related to qt versions. Fixed by removing version of spectacle which was more recent than expected for the release I was on (spectacle was version 18.04 from unstable, expected version was 17.12 or earlier). The segfault was coming in from a plugin inside qtbase.

So this might be related as there may be other errors with qt versions, as mentioned in the other issue.

[sopvop]

Got same problem when I installed qt5 app (telegram client) from nixpkgs-unstable. It got fixed once I removed it from user profile.

[sopvop]

EDIT: Disregard that. It was Qt version conflict.

[stale]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.

[FliegendeWurst]

Considering the lack of recent comments, this issue was probably fixed a while ago.