Re: KDE Plasma menu crashes on text input

On Mon Dec 30, 2024 at 02:43:30PM +0000, Klemens Nanni wrote:
> 12.06.2024 18:50, Klemens Nanni пишет:
> > Today's snap and kde-plasma-extras-6.0.5p0 starts on a T14 gen3 Intel,
> > I can click through the menu in the bottom left corner, but typing to
> > search/filter applications immediately crashes the menu, the background
> > becomes black/white again, X11 keeps running though.
> >
> > First time starting KDE Plasma on this installation, i.e. no ~/.config/
> > or other files from previous attempts:
> >
> > ~/.config/kwinrc contains this as per package readme:
> > [Compositing]
> > Enabled=false
> >
> > ~/.xsession is this as per package readme:
> > #!/bin/sh
> > export XDG_RUNTIME_DIR=/tmp/run/$(id -u)
> > if [ ! -d $XDG_RUNTIME_DIR ]; then
> > mkdir -m 700 -p $XDG_RUNTIME_DIR
> > fi
> > export DESKTOP_SESSION=plasma
> > export QT_FORCE_STDERR_LOGGING=1
> > export QT_LOGGING_RULES="*=true"
> > export XDG_CURRENT_DESKTOP=KDE
> > /usr/local/bin/startplasma-x11 > ~/.startplasma-x11.log 2>&1
>
> Tried yesterday again with a fresh user profile, but nothing changed;
> plasmashell crashes when typing text in menu:
>
> #0 g_log_structured_array (log_level=<optimized out>, fields=<optimized out>, n_fields=<optimized out>) at ../glib-2.82.4/glib/gmessages.c:1867
> #1 0x000005799b41f155 in g_log_default_handler (log_domain=<optimized out>, log_level=17, message=<optimized out>, unused_data=<optimized out>) at ../glib-2.82.4/glib/gmessages.c:3412
> #2 0x000005799b41ecc2 in g_logv (log_domain=0x5799b35c96c "GLib", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=<optimized out>) at ../glib-2.82.4/glib/gmessages.c:1246
> #3 0x000005799b41e825 in g_log (log_domain=0xffffffff00000011 <error: Cannot access memory at address 0xffffffff00000011>, log_level=0, format=0x57949c98e40 "") at ../glib-2.82.4/glib/gmessages.c:1315
> #4 0x000005799b4793b2 in g_wakeup_new () at ../glib-2.82.4/glib/gwakeup.c:162
> #5 0x000005799b4112c0 in g_main_context_new_with_flags (flags=G_MAIN_CONTEXT_FLAGS_NONE) at ../glib-2.82.4/glib/gmain.c:663
> #6 0x00000579a575bfd4 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate(_GMainContext*) () from /usr/local/lib/libQt6Core.so.5.0
> #7 0x00000579a575c258 in QEventDispatcherGlib::QEventDispatcherGlib(QObject*) () from /usr/local/lib/libQt6Core.so.5.0
> #8 0x00000579a56697bb in QThreadPrivate::createEventDispatcher(QThreadData*) () from /usr/local/lib/libQt6Core.so.5.0
> #9 0x00000579a55c96df in QThreadData::createEventDispatcher() () from /usr/local/lib/libQt6Core.so.5.0
> #10 0x00000579a5669968 in QThreadPrivate::start(void*) () from /usr/local/lib/libQt6Core.so.5.0
> #11 0x00000579b770a162 in _rthread_start (v=0x0) at /usr/src/lib/librthread/rthread.c:96
> #12 0x00000579114ad9fa in __tfork_thread () at /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:87
>
>
> Logs are flooded:
> $ du -h .startplasma-x11.log
> 3.9G .startplasma-x11.log
> $ wc -l .startplasma-x11.log
> 40444457 .startplasma-x11.log
>
> One line looks relevant:
> (process:951): GLib-ERROR **: 03:52:26.152: Creating pipes for GWakeup: Too many open files
>
> The system/user runs with
> $ sysctl -n kern.maxfiles ; ulimit -n
> 8192
> 512
>
> I did not find anything wrt. increasing limits in package docs/readmes.
>

Could you try it with the "maxpower" ridiculous open profile, to verify
it's a limits issue, please?

/etc/login.conf.d/maxpower
maxpower:\
:datasize=infinity:\
:datasize-max=infinity:\
:datasize-cur=infinity:\
:maxproc=infinity:\
:maxproc-max=infinity:\
:maxproc-cur=infinity:\
:openfiles=infinity:\
:openfiles-max=infinity:\
:openfiles-cur=infinity:\
:stacksize-cur=8M:\
:tc=default: