NixOS / nixpkgs

Nix Packages collection & NixOS
MIT License
17.01k stars 13.36k forks source link

[20.03] KSystemLog crashes when launched from menu #80711

Open ghost opened 4 years ago

ghost commented 4 years ago

Describe the bug

When launching KSystemLog on plasma5, it crashes if launched from menu. It works well when launched from terminal session.

To Reproduce Steps to reproduce the behavior:

  1. Install plasma5 and KSystemLog
  2. Launch KSystemLog

Expected behavior

The program should open.

Additional context

Launching a journalctl -f while launching it shows the following line :

févr. 21 11:25:51 ely-lenovo xsession[1187]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10385, resource id: 50331816, major code: 18 (ChangeProperty), minor code: 0

Metadata

Maintainer information:

@ttuegel @worldofpeace

ttuegel commented 4 years ago

The line you see in journalctl is harmless, but I haven't had a chance to investigate the crash yet.

ghost commented 4 years ago

@ttuegel : I have done some digging, and it seems adding a X-KDE-SubstituteUID=false to the desktop file resolves the issue. On Arch Linux setups, ksystemlog asks for a privilege escalation, this might be why there is a suid on the desktop file.

stale[bot] commented 3 years ago

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.

ttuegel commented 3 years ago

@Elyhaka Do you know what mechanism it uses to ask for privilege escalation? Polkit? kdesu?

ghost commented 3 years ago

I have no idea, sorry. Gonna check on a friend's ArchLinux setup.

stale[bot] commented 3 years ago

I marked this as stale due to inactivity. → More info

mourogurt commented 1 week ago

The bug is still present on plasma6 desktops.