[systemdgenie] [Bug 462616] systemdgenia blocks under spam mesages about systemPropertiesChanged: "org.freedesktop.systemd1.xxxx"

2023-10-09 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=462616 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com --- Comment #1 from Alex

[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue

2022-08-11 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=445240 --- Comment #5 from Alex Folland --- No, I didn't see any change in visibility from the TTY. The source of these logs is from redirecting the output to a file, and there was no output that wasn't redirected, as I saw no text output, but the file

[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue

2022-08-10 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=445240 --- Comment #3 from Alex Folland --- OK, I've tried both of those commands. Here are the logs from them. from `XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland --exit-with-session=konsole` ``` kf.service.services: The desktop entry file "

[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue

2022-08-09 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=445240 --- Comment #1 from Alex Folland --- I've tried again and the logging is different now for the same login issue. It's still not quite good enough to understand exactly why Plasma can't reach the desktop, but here's an update of what's logged

[plasmashell] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

2022-04-02 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=417282 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com -- You are receiving

[plasmashell] [Bug 440397] KDE crashes on launch with Wayland and NVidia

2022-01-19 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=440397 --- Comment #6 from Alex Folland --- I've just reread my previous command and realized that it has the second command which I used entered incorrectly, so I'd like to correct myself. What I used which did not work was this: XDG_SESSION_TYPE=wayland

[kwin] [Bug 440397] KDE crashes on launch with Wayland and NVidia

2022-01-19 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=440397 --- Comment #4 from Alex Folland --- I have this issue on my machine. I tried the command in Vlad Zahorodnii's comment: XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland --exit-with-session=konsole This command above kind of works, showing

[kwin] [Bug 440397] KDE crashes on launch with Wayland and NVidia

2021-11-15 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=440397 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com -- You are receiving

[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue

2021-11-09 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=445240 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com -- You are receiving

[kwin] [Bug 445240] New: Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue

2021-11-09 Thread Alex Folland
https://bugs.kde.org/show_bug.cgi?id=445240 Bug ID: 445240 Summary: Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue Product: kwin