Re: lxqt crashing (Was: NetBSD 10 packages)

[Jason Bacon <jtocino%gmx.com@localhost>]

On 10/5/23 05:55, David Brownlee wrote:

> > Reverting to the nb3 package fixes the lxqt-panel crashes on my NetBSD
> > 10 VM, but that just takes me back to the old hanging issue and failure
> > to activate consolekit errors.
> >
> > It's progress, though...
>
> When I tested the netbsd-9 packages on netbsd-10 I shut down all other
> daemons (dbus, avahidaemon etc), and lxqt started without issue. I
> left them shut down when I switched back to netbsd-10 packages and
> tested lxqt-panel-1.3.0nb3, and again it started without delay or
> issue. One data point only, but a suggestive one...
>
> David

I can reproduce this on my NetBSD 10 VM.

What's interesting is that lxqt launches its own dbus child process
whether or not a dbus service is already running.  On NetBSD 10, this
appears to cause a conflict, while on NetBSD 9 is does not.

NetBSD 9 with dbus enabled in /etc/rc.conf and no login session running:

791 ?     Is   0:00.00 /usr/pkg/bin/dbus-daemon --system --fork

NetBSD 9 with lxqt running:

 169 ?     S    0:00.02 dbus-launch --exit-with-session startlxqt
 791 ?     Ss   0:00.06 /usr/pkg/bin/dbus-daemon --system --fork
 869 ?     Is   0:00.02 ck-launch-session dbus-launch
--exit-with-session start
 982 ?     Ss   0:00.05 /usr/pkg/bin/dbus-daemon --syslog --fork
--print-pid 9

NetBSD 10 with dbus enabled in /etc/rc.conf and no login session running:

26053 ?     Ss   0:00.00 /usr/pkg/bin/dbus-daemon --system --fork

NetBSD 10 with lxqt running:

 1789 ?     Z    0:00.00 (dbus-daemon)
 3506 ?     Ss   0:00.00 /usr/pkg/bin/dbus-daemon --syslog --fork
--print-pid 7
26053 ?     Ss   0:00.00 /usr/pkg/bin/dbus-daemon --system --fork
27431 ?     S    0:00.00 dbus-launch --sh-syntax --exit-with-session

If I stop the dbus service launched from /etc/rc.conf on NetBSD 10, the
LXQT session seems to work fine.

So the question now is why do multiple dbus processes play nice together
on NetBSD 9 but not on NetBSD 10?  Is it directly due to OS differences,
or perhaps some configure script behaving differently on NetBSD 10?

I'm leaning toward not enabling dbus in rc.conf when LXQT is chosen in
desktop-installer.  I don't think dbus serves any purpose when there is
no login session running, but please chime in if I'm wrong about this.
Since LXQT starts its own dbus process anyway, the system service is at
best useless, and at worst buggers the login session.