[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 Folland  ---
I see the same behavior, with the GUI not updating properly, and staying frozen
(noninteractive).  Here's my terminal output.

```
[alex@alex-pc ~]$ systemdgenie
/home/alex/.themes/Matcha-dark-azul-buju/gtk-2.0/panel.rc:8: error: unexpected
keyword 'bg', expected string constant
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
Detected systemd 0
Refreshing system units...
Refreshing user units...
Refreshing session list...
Refreshing timer list...
Refreshing config files list...
Entering application loop
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
UserJobNew:  248168 "/org/freedesktop/systemd1/job/248168"
"easyeffects.service"
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
UserJobRemoved:  248168 "/org/freedesktop/systemd1/job/248168"
"easyeffects.service" "done"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Manager"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Manager"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
UserJobNew:  248188 "/org/freedesktop/systemd1/job/248188"
"easyeffects.service"
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
UserJobRemoved:  248188 "/org/freedesktop/systemd1/job/248188"
"easyeffects.service" "done"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Manager"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Service"
Refreshing user units...
Refreshing timer list...
userPropertiesChanged: "org.freedesktop.systemd1.Unit"
Refreshing user units...
Killed
[ble: exit 137]
[alex@alex-pc ~]$
```

I am posting this because almost a year has passed since the original report
and this issue makes the software unable to be used on my system.

-- 
You are receiving this mail because:
You are watching all bug changes.

[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 was populated.  I
think you've hit the nail on the head about what this issue ticket is for: the
fact that the logging output from kwin is not helpful enough to determine the
issue.  It shouldn't simply exit without saying exactly what happened. 
Instead, it should show some kind of helpful error message explaining exactly
what's wrong, or better yet, simply work instead, since other graphical
programs work with no issue.  I can even run RetroArch directly, for example,
with no X11 or Wayland server previously running, so kwin doesn't have a good
excuse to not simply render to my screens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[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
"/usr/share/applications/kcm_krunnersettings.desktop" has Type= "Application"
but no Exec line
kf.service.sycoca: Invalid Service : 
"/usr/share/applications/kcm_krunnersettings.desktop"
kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
kf.service.sycoca: Invalid Service :  "/usr/share/applications/qemu.desktop"
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192
comm="startplasma-wayland --exit-with-session=konsole")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service
name='org.freedesktop.systemd1' requested by ':1.3' (uid=1000 pid=2172221
comm="/usr/bin/kwin_wayland_wrapper --xwayland")
dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
kdeinit5: preparing to launch '/usr/lib/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 2172230, result = 0

(kwin_wayland:217): Gtk-WARNING **: 18:13:45.725: cannot open display: 

(kwin_wayland:2172233): Gtk-WARNING **: 18:13:45.810: cannot open display: 

(kwin_wayland:2172234): Gtk-WARNING **: 18:13:45.887: cannot open display: 

(kwin_wayland:2172235): Gtk-WARNING **: 18:13:45.964: cannot open display: 

(kwin_wayland:2172236): Gtk-WARNING **: 18:13:46.039: cannot open display: 

(kwin_wayland:2172237): Gtk-WARNING **: 18:13:46.116: cannot open display: 

(kwin_wayland:2172240): Gtk-WARNING **: 18:13:46.200: cannot open display: 

(kwin_wayland:2172241): Gtk-WARNING **: 18:13:46.281: canno

[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 in
`~/.local/share/sddm/wayland-session.log`.

```
kf.service.services: The desktop entry file
"/usr/share/applications/kcm_krunnersettings.desktop" has Type= "Application"
but no Exec line
kf.service.sycoca: Invalid Service : 
"/usr/share/applications/kcm_krunnersettings.desktop"
kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
kf.service.sycoca: Invalid Service :  "/usr/share/applications/qemu.desktop"
/usr/bin/xrdb: Can't open display ''
QPixmap: QGuiApplication must be created before calling defaultDepth().
QPixmap: QGuiApplication must be created before calling defaultDepth().
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
```

By the way, I'm not sure if Markdown works here.  It tends to work pretty much
everywhere else on the internet these days, so I'm trying it despite the
preview not rendering it correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[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 this mail because:
You are watching all bug changes.

[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 dbus-run-session startplasma-wayland
--exit-with-session=konsole

-- 
You are receiving this mail because:
You are watching all bug changes.

[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 a black desktop with no panels and a
tiny konsole window on the secondary display with a wrong monitor layout, so I
had to move the cursor off the right side of my right (primary) monitor to get
the konsole window from my left monitor.  That, at least, started a graphical
program which let me move my mouse around.

However, the following command, with "kwin_wayland" substituted by
"startplasma-wayland" has the following output and doesn't start any graphical
program.

command:

XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland
--exit-with-session=konsole

output (stderr):

dbus-daemon[679081]: [session uid=1000 pid=679081] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=679082
comm="startplasma-wayland --exit-with-session=konsole ")
dbus-daemon[679081]: [session uid=1000 pid=679081] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[679081]: [session uid=1000 pid=679081] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=679082
comm="startplasma-wayland --exit-with-session=konsole ")
dbus-daemon[679081]: [session uid=1000 pid=679081] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[679081]: [session uid=1000 pid=679081] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=679082
comm="startplasma-wayland --exit-with-session=konsole ")
dbus-daemon[679081]: [session uid=1000 pid=679081] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon[679081]: [session uid=1000 pid=679081] Activating service
name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=679082
comm="startplasma-wayland --exit-with-session=konsole ")
dbus-daemon[679081]: [session uid=1000 pid=679081] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1

(kwin_wayland:679094): Gtk-WARNING **: 11:59:03.550: cannot open display: 

(kwin_wayland:679095): Gtk-WARNING **: 11:59:03.635: cannot open display: 

(kwin_wayland:679096): Gtk-WARNING **: 11:59:03.725: cannot open display: 

(kwin_wayland:679097): Gtk-WARNING **: 11:59:03.815: cannot open display: 

(kwin_wayland:679098): Gtk-WARNING **: 11:59:03.908: cannot open display: 

(kwin_wayland:679099): Gtk-WARNING **: 11:59:03.996: cannot open display: 

(kwin_wayland:679100): Gtk-WARNING **: 11:59:04.087: cannot open display: 

(kwin_wayland:679102): Gtk-WARNING **: 11:59:04.184: cannot open display: 

(kwin_wayland:679103): Gtk-WARNING **: 11:59:04.270: cannot open display: 

(kwin_wayland:679104): Gtk-WARNING **: 11:59:04.365: cannot open display: 

(kwin_wayland:679105): Gtk-WARNING **: 11:59:04.460: cannot open display: 
startplasmacompositor: Shutting down...
startplasmacompositor: Done.

-- 
You are receiving this mail because:
You are watching all bug changes.

[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 this mail because:
You are watching all bug changes.

[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 this mail because:
You are watching all bug changes.

[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
   Version: 5.23.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lexlex...@gmail.com
  Target Milestone: ---

Created attachment 143390
  --> https://bugs.kde.org/attachment.cgi?id=143390=edit
wayland session log

***Please understand that this issue report is about logging only, not the
failure to start the session.***

STEPS TO REPRODUCE

1. Have the issue where the session named "Plasma (Wayland)" fails to start
from SDDM, in such a way that trying to start it from the SDDM login menu
navigates to a black screen, stays there for a few seconds, then navigates back
to the SDDM login menu.
2. Verify that the contents of your ~/.local/share/sddm/wayland-session.log
file are the following, or any with "cannot open display:" with nothing
following that text, like so:

---

(kwin_wayland:1939): Gtk-WARNING **: 16:11:52.831: cannot open display: 

(kwin_wayland:1944): Gtk-WARNING **: 16:11:52.903: cannot open display: 

(kwin_wayland:1945): Gtk-WARNING **: 16:11:52.975: cannot open display: 

(kwin_wayland:1946): Gtk-WARNING **: 16:11:53.036: cannot open display: 

(kwin_wayland:1948): Gtk-WARNING **: 16:11:53.094: cannot open display: 

(kwin_wayland:1949): Gtk-WARNING **: 16:11:53.151: cannot open display: 

(kwin_wayland:1951): Gtk-WARNING **: 16:11:53.206: cannot open display: 

(kwin_wayland:1952): Gtk-WARNING **: 16:11:53.262: cannot open display: 

(kwin_wayland:1953): Gtk-WARNING **: 16:11:53.318: cannot open display: 

(kwin_wayland:1954): Gtk-WARNING **: 16:11:53.373: cannot open display: 

(kwin_wayland:1955): Gtk-WARNING **: 16:11:53.428: cannot open display: 
startplasmacompositor: Shutting down...
startplasmacompositor: Done.

---

3. Spend as much time as it takes to search online for a way to work around the
issue.

OBSERVED BEHAVIOR

The log entries here that are like "Gtk-WARNING **: 16:11:52.831: cannot open
display: " with nothing after them are not informative enough to figure out
what the problem is, and there's no error message explaining why the session
could not start, from either kwin_wayland or startplasmacompositor.  The log
file itself is attached to this ticket.

EXPECTED BEHAVIOR

Session log entries for sessions which fail to start are expected to explain
clearly what is causing them to fail to start.

SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: Linux 5.15
KDE Plasma Version: KDE Plasma 5.23.3
KDE Frameworks Version: 5.23.3
Qt Version: 5.15.2 and 6.2.1

ADDITIONAL INFORMATION

Remember, this issue report is not about the failure to start.  That can be
tackled in another ticket.

This is about the log entries on session start failure not being useful enough
to determine the cause of the session start failure.  They should always say
exactly what's wrong, and improving the logging to the point where it says
exactly what's wrong if the session fails to start is the only goal of this
ticket.

-- 
You are receiving this mail because:
You are watching all bug changes.