Open bernd-wechner opened 6 months ago
As stated above, it's a 24/7 box with rare restarts, but executed one recently, noted xreader is working now, and so took an env snapshot and compared it with diff -y
to get:
env: xreader not working env: xreader working
SHELL=/bin/bash SHELL=/bin/bash
SESSION_MANAGER=local/<redacted>:@/tmp/.ICE-unix/1849,unix/<r | SESSION_MANAGER=local/<redacted>:@/tmp/.ICE-unix/1870,unix/<r
QT_ACCESSIBILITY=1 QT_ACCESSIBILITY=1
COLORTERM=truecolor COLORTERM=truecolor
XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
GNOME_DESKTOP_SESSION_ID=this-is-deprecated GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GTK_IM_MODULE=ibus GTK_IM_MODULE=ibus
LANGUAGE=en_AU:en LANGUAGE=en_AU:en
LC_ADDRESS=en_AU.UTF-8 LC_ADDRESS=en_AU.UTF-8
LC_NAME=en_AU.UTF-8 LC_NAME=en_AU.UTF-8
> CINNAMON_VERSION=6.0.4
XMODIFIERS=@im=ibus XMODIFIERS=@im=ibus
DESKTOP_SESSION=cinnamon DESKTOP_SESSION=cinnamon
LC_MONETARY=en_AU.UTF-8 LC_MONETARY=en_AU.UTF-8
GTK_MODULES=gail:atk-bridge GTK_MODULES=gail:atk-bridge
> XDG_SEAT=seat0
PWD=/home/<redacted> PWD=/home/<redacted>
LOGNAME=<redacted> LOGNAME=<redacted>
XDG_SESSION_DESKTOP=cinnamon XDG_SESSION_DESKTOP=cinnamon
QT_QPA_PLATFORMTHEME=qt5ct QT_QPA_PLATFORMTHEME=qt5ct
XDG_SESSION_TYPE=x11 XDG_SESSION_TYPE=x11
CHROME_CONFIG_HOME=/media/Data/Web/Chrome CHROME_CONFIG_HOME=/media/Data/Web/Chrome
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1 GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
SYSTEMD_EXEC_PID=22838 <
XAUTHORITY=/home/<redacted>/.Xauthority XAUTHORITY=/home/<redacted>/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/<redacted> XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/<redacted>
GDM_LANG=en_AU GDM_LANG=en_AU
HOME=/home/<redacted> HOME=/home/<redacted>
IM_CONFIG_PHASE=1 <
LC_PAPER=en_AU.UTF-8 LC_PAPER=en_AU.UTF-8
LANG=en_AU.UTF-8 LANG=en_AU.UTF-8
XDG_CURRENT_DESKTOP=X-Cinnamon XDG_CURRENT_DESKTOP=X-Cinnamon
VTE_VERSION=6800 VTE_VERSION=6800
KDEDIR=/home/<redacted>/kde KDEDIR=/home/<redacted>/kde
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/0b701d8c_0c6 | GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/b47123f5_e64
CLUTTER_IM_MODULE=ibus CLUTTER_IM_MODULE=ibus
XDG_SESSION_CLASS=user XDG_SESSION_CLASS=user
TERM=xterm-256color TERM=xterm-256color
LC_IDENTIFICATION=en_AU.UTF-8 LC_IDENTIFICATION=en_AU.UTF-8
USER=<redacted> USER=<redacted>
GNOME_TERMINAL_SERVICE=:1.151 | GNOME_TERMINAL_SERVICE=:1.128
DISPLAY=:0 DISPLAY=:0
SHLVL=0 SHLVL=0
LC_TELEPHONE=en_AU.UTF-8 LC_TELEPHONE=en_AU.UTF-8
QT_IM_MODULE=ibus QT_IM_MODULE=ibus
LC_MEASUREMENT=en_AU.UTF-8 LC_MEASUREMENT=en_AU.UTF-8
> XDG_VTNR=7
> XDG_SESSION_ID=c1
PAPERSIZE=a4 PAPERSIZE=a4
XDG_RUNTIME_DIR=/run/user/1000 XDG_RUNTIME_DIR=/run/user/1000
LC_TIME=en_AU.UTF-8 LC_TIME=en_AU.UTF-8
KDEDIRS=/home/<redacted>/kde KDEDIRS=/home/<redacted>/kde
LC_COLLATE=C LC_COLLATE=C
GTK3_MODULES=xapp-gtk3-module GTK3_MODULES=xapp-gtk3-module
XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/<red XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/<red
PATH=/home/<redacted>/kde/bin:/home/<redacted>/bin:/home/<red PATH=/home/<redacted>/kde/bin:/home/<redacted>/bin:/home/<red
GDMSESSION=cinnamon GDMSESSION=cinnamon
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
LC_NUMERIC=en_AU.UTF-8 LC_NUMERIC=en_AU.UTF-8
_=/usr/bin/env _=/usr/bin/env
In case that helps.
I'm getting the same problem on 21.3. Although I prefer xreader, it was easier to remove it and use evince instead.
Distribution
Mint 21.3
Package version
4.0.2
Frequency
Always
Bug description
Steps to reproduce
Start xreader
Expected behavior
Not a segmentation fault ;-)
Additional information
I have a gut feel this will come good with reboot. In short, I have recollection of it happening before and finding that. I'm on 24/7 box though and rebooting is not a simple thing, so not tried it this time yet. In part because it's not a relevant qualifier of bug status (it's a bug regardless) but might point to a cause (put it in the camp of configs). So if it's helpful an amateurishly redacted env: