Hi,
After updating the packages on my manjaro install I am unable to get to the login manager, and also doesn’t appear to start X successfully (when I get to a tty and type startx) - I don’t receive any errors in the Xorg log but just what appears to be some innocuous warnings. I receive a failure to start Light Display Manager in the statup std out. FYI: I also turned X back into root mode to see if it would help but to no avail. Any hints would be much appreciated as i’m running out of rabbit holes.
inxi:
System:
Kernel: 5.15.85-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=4a3fd543-61d8-4c50-a534-04644cbb00f4 rw quiet
resume=UUID=ced76fbf-892d-409c-9590-3e1ab5ce780c
Console: tty 3 DM: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: VC66 serial: N/A UEFI: ASUSTeK (Licensed
from AMI) v: 0407 date: 05/25/2017
CPU:
Info: model: Intel Core i5-7400 socket: LGA1151 bits: 64 type: MCP
arch: Kaby Lake gen: core 7 level: v3 note: check built: 2018
process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0xF0
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/3500 base/boost: 3000/8300 scaling:
driver: intel_pstate governor: powersave volts: 0.9 V ext-clock: 100 MHz
cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 24008
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
Type: retbleed mitigation: IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: DP-1
empty: HDMI-A-1,HDMI-A-2,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:5912
class-ID: 0300
Display: server: X.org v: 1.21.1.6 with: Xwayland v: 22.1.7 driver: X:
loaded: modesetting unloaded: fbdev alternate: vesa dri: iris gpu: i915
tty: 240x67
Monitor-1: DP-1 model: Acer B286HK serial: <filter> built: 2014
res: 3840x2160 dpi: 157 gamma: 1.2 size: 621x341mm (24.45x13.43")
diag: 708mm (27.9") ratio: 16:9 modes: max: 3840x2160 min: 720x400
API: OpenGL Message: GL data unavailable in console and glxinfo missing.
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
class-ID: 0403
Sound API: ALSA v: k5.15.85-1-MANJARO running: yes
Sound Server-1: JACK v: 1.9.21 running: no
Sound Server-2: PulseAudio v: 16.1 running: no
Sound Server-3: PipeWire v: 0.3.63 running: no
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: down mac: <filter>
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24f3 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
bus-ID: 1-8:3 chip-ID: 8087:0a2b class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
Local Storage: total: 4.09 TiB used: 1.83 TiB (44.6%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate model: BUP BK
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: N/A
serial: <filter> rev: 0108 scheme: GPT
Partition:
ID-1: / raw-size: 456.66 GiB size: 448.43 GiB (98.20%) used: 44.09 GiB (9.8%)
fs: ext4 block-size: 4096 B dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 42.2 MiB (14.1%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 159 Uptime: 4m wakeups: 0 Memory: 7.64 GiB used: 1.23 GiB (16.1%)
Init: systemd v: 252 default: graphical tool: systemctl Compilers:
gcc: 12.2.0 clang: 14.0.6 Packages: 1558 pm: pacman pkgs: 1551 libs: 465
tools: pamac pm: flatpak pkgs: 0 pm: snap pkgs: 7 Shell: Bash (sudo)
v: 5.1.16 running-in: tty 3 inxi: 3.3.24
Will provide Xorg log and journalctl logs.
Thanks!
The display Manager (Lightdm) crashed.
Maybe your update was incomplete?
Try running it again (from a TTY)
sudo pacman -Syu
to start your xfce session from TTY , use startxfce4
instead of startx
sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syyu
reports: nothing to do.
startxfce4
has the same result as startx
Any other suggestions?
What is the result?
I can’t glean it from what is here at the moment.
… not as root - as your normal user …
/usr/bin/startxfce4: Starting X server
X.Org X Server 1.21.1.6
X Protocol Version 11, Revision 0
Current Operating System: Linux charvey-media 5.15.85-1-MANJARO #1 SMP PREEMPT Wed Dec 21 21:15:06 UTC 2022 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64 root=UUID=4a3fd543-61d8-4c50-a534-04644cbb00f4 rw quiet resume=UUID=ced76fbf-892d-409c-9590-3e1ab5ce780c
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 6 14:29:26 2023
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Environment variable $XAUTHORITY not set, ignoring.
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
So, it switches to a non tty output and then right back with the log above.
Xorg log: Xorg log - Pastebin.com
since the display manager crashes
and you don’t know why
you could eliminate it altogether (for the time being)
disable it (for now, to take it out of the picture)
systemctl disable lightdm.service
reboot - you’ll land on a TTY
log in (as normal user) and try: startxfce4
something has to leave a trace …
It’ll likely be the same outcome - but: who knows?
Well, you guessed it - same outcome.
startxfce4
has the same result and journalctl -p 3 -xb
has the same stack coming from xfce4-session
.
Not sure how to take this further.
Me neither - I’ll need some time to think and tinker
perhaps I can come up with something
… you have not altered the Display manager configuration?
Or run a different than the standard greeter?
No AUR package replaced the originals?
you have not altered the Display manager configuration?
I did set up auto login but dropped that to no avail. And based on your last suggestion DM is out of the picture.
Or run a different than the standard greeter?
I did modify the greeter script to start syngergy but have removed that also, and appears to be a probem starting Xorg opposed to DM.
No AUR package replaced the originals?
Not that I know of. Prior to the upgrade I did install jellyfin from AUR but that should not have touched any of the components we’re talking about.
Is it worth forcing a re-install of xfce? If so, how would one do so?
No.
Won’t do anything towards the display manager issue.
Won’t affect anything inside your $HOME … which might (just might) be also an issue.
No.
Interestingly if I run Xorg
then I do receive some errors but I don’t know if it is legal to call Xorg
directly without some set up / configs set. These are the errors:
[ 1099.429] (II) LoadModule: "fbdev"
[ 1099.429] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 1099.429] (II) Module fbdev: vendor="X.Org Foundation"
[ 1099.429] compiled for 1.21.1.1, module version = 0.5.0
[ 1099.429] Module class: X.Org Video Driver
[ 1099.429] ABI class: X.Org Video Driver, version 25.2
[ 1099.429] (II) LoadModule: "vesa"
[ 1099.429] (WW) Warning, couldn't open module vesa
[ 1099.429] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 1099.429] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 1099.429] (II) FBDEV: driver for framebuffer: fbdev
[ 1099.429] (EE)
Fatal server error:
[ 1099.429] (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
[ 1099.429] (EE)
[ 1099.429] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1099.429] (EE) Please also check the log file at "/home/hraja/.local/share/xorg/Xorg.0.log" for additional information.
[ 1099.429] (EE)
[ 1099.429] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
[ 1099.429] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
[ 1099.491] (EE) Server terminated with error (1). Closing log file.
Entire Xorg log: Xorg - Pastebin.com
Are you sure that you left the file in a sane state?
as it was before you did that?
double check that!
same here!
but:
startxfce4 does not work either - but it should
It sure does for me
so none of the above even matters at the moment
[ 1099.429] (EE) Failed to load module "vesa" (module does not exist, 0)
this is the first (EE) aka error that occurs
something about the vesa graphics driver
I only have a Manjaro VM here to test
It does not have or use this driver.
mhwd -li
might shed some light ?
Worth noting that I only see that error if I run Xorg
directly, i.e. not via startx*.
> 0000:00:02.0 (0300:8086:5912) Display controller Intel Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
installed:
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
I have never (in 22 yers) started X that way - it just isn’t right
so let’s not pursue that path any further
It didn’t feel right but that puts us back to having no errors other than the core dump:
Jan 06 15:26:03 charvey-media kernel: x86/cpu: SGX disabled by BIOS.
Jan 06 15:26:04 charvey-media kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jan 06 15:26:04 charvey-media kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Jan 06 15:26:04 charvey-media systemd-udevd[270]: event5: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
Jan 06 15:26:05 charvey-media kernel: snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]
Jan 06 15:26:06 charvey-media bluetoothd[702]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jan 06 15:26:06 charvey-media bluetoothd[702]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jan 06 15:26:06 charvey-media bluetoothd[702]: src/plugin.c:plugin_init() Failed to init bap plugin
Jan 06 15:26:12 charvey-media nmbd[903]: [2023/01/06 15:26:12.950994, 0] ../../source3/nmbd/nmbd.c:901(main)
Jan 06 15:26:12 charvey-media nmbd[903]: nmbd version 4.17.4 started.
Jan 06 15:26:12 charvey-media nmbd[903]: Copyright Andrew Tridgell and the Samba Team 1992-2022
Jan 06 15:26:12 charvey-media nmbd[903]: [2023/01/06 15:26:12.953714, 0] ../../source3/param/loadparm.c:4126(lp_load_ex)
Jan 06 15:26:12 charvey-media nmbd[903]: lp_load_ex: Max protocol NT1 is less than min protocol SMB2_02.
Jan 06 15:26:12 charvey-media nmbd[903]: [2023/01/06 15:26:12.954280, 0] ../../lib/util/become_daemon.c:150(daemon_status)
Jan 06 15:26:12 charvey-media nmbd[903]: daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
Jan 06 15:26:12 charvey-media nmbd[903]: [2023/01/06 15:26:12.954530, 0] ../../source3/nmbd/nmbd_subnetdb.c:252(create_subnets)
Jan 06 15:26:12 charvey-media nmbd[903]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Jan 06 15:26:49 charvey-media systemd-coredump[1290]: Process 1251 (xfce4-session) of user 1000 dumped core.
Stack trace of thread 1251:
#0 0x00007f4b3954d048 g_log_structured_array (libglib-2.0.so.0 + 0x5d048)
#1 0x00007f4b3954d683 g_log_default_handler (libglib-2.0.so.0 + 0x5d683)
#2 0x00007f4b3954e8b5 g_logv (libglib-2.0.so.0 + 0x5e8b5)
#3 0x00007f4b3954eb64 g_log (libglib-2.0.so.0 + 0x5eb64)
#4 0x00007f4b39550797 g_log_set_writer_func (libglib-2.0.so.0 + 0x60797)
#5 0x00007f4b39f61a52 n/a (libgtk-3.so.0 + 0x3d2a52)
#6 0x00007f4b39d6bed3 n/a (libgtk-3.so.0 + 0x1dced3)
#7 0x00007f4b39643210 g_closure_invoke (libgobject-2.0.so.0 + 0x14210)
#8 0x00007f4b39670ea8 n/a (libgobject-2.0.so.0 + 0x41ea8)
#9 0x00007f4b39660f75 g_signal_emit_valist (libgobject-2.0.so.0 + 0x31f75)
#10 0x00007f4b39661204 g_signal_emit (libgobject-2.0.so.0 + 0x32204)
#11 0x00007f4b3964dfc6 n/a (libgobject-2.0.so.0 + 0x1efc6)
#12 0x00007f4b39654671 g_object_notify (libgobject-2.0.so.0 + 0x25671)
#13 0x00007f4b39ac28bc n/a (libgdk-3.so.0 + 0x338bc)
#14 0x00007f4b3966111c g_signal_emit_valist (libgobject-2.0.so.0 + 0x3211c)
#15 0x00007f4b39661424 g_signal_emit_by_name (libgobject-2.0.so.0 + 0x32424)
#16 0x00007f4b39b154af n/a (libgdk-3.so.0 + 0x864af)
#17 0x00007f4b39ac2c46 gdk_display_manager_open_display (libgdk-3.so.0 + 0x33c46)
#18 0x00007f4b39d70d50 gtk_init_with_args (libgtk-3.so.0 + 0x1e1d50)
#19 0x0000556b32aa90c0 main (xfce4-session + 0x120c0)
#20 0x00007f4b3932c290 n/a (libc.so.6 + 0x23290)
#21 0x00007f4b3932c34a __libc_start_main (libc.so.6 + 0x2334a)
#22 0x0000556b32aa93c5 _start (xfce4-session + 0x123c5)
Stack trace of thread 1264:
#0 0x00007f4b3938c4b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007f4b3938ecd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007f4b3415650e n/a (iris_dri.so + 0x10c50e)
#3 0x00007f4b3410689c n/a (iris_dri.so + 0xbc89c)
#4 0x00007f4b3415643c n/a (iris_dri.so + 0x10c43c)
#5 0x00007f4b3938f8fd n/a (libc.so.6 + 0x868fd)
#6 0x00007f4b39411a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1267:
#0 0x00007f4b394040bf __poll (libc.so.6 + 0xfb0bf)
#1 0x00007f4b3959cbef n/a (libglib-2.0.so.0 + 0xacbef)
#2 0x00007f4b39544ddf g_main_loop_run (libglib-2.0.so.0 + 0x54ddf)
#3 0x00007f4b3979aadc n/a (libgio-2.0.so.0 + 0x10aadc)
#4 0x00007f4b39572e05 n/a (libglib-2.0.so.0 + 0x82e05)
#5 0x00007f4b3938f8fd n/a (libc.so.6 + 0x868fd)
#6 0x00007f4b39411a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1266:
#0 0x00007f4b394040bf __poll (libc.so.6 + 0xfb0bf)
#1 0x00007f4b3959cbef n/a (libglib-2.0.so.0 + 0xacbef)
#2 0x00007f4b39544132 g_main_context_iteration (libglib-2.0.so.0 + 0x54132)
#3 0x00007f4b39544182 n/a (libglib-2.0.so.0 + 0x54182)
#4 0x00007f4b39572e05 n/a (libglib-2.0.so.0 + 0x82e05)
#5 0x00007f4b3938f8fd n/a (libc.so.6 + 0x868fd)
#6 0x00007f4b39411a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1263:
#0 0x00007f4b3938c4b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007f4b3938ecd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007f4b3415650e n/a (iris_dri.so + 0x10c50e)
#3 0x00007f4b3410689c n/a (iris_dri.so + 0xbc89c)
#4 0x00007f4b3415643c n/a (iris_dri.so + 0x10c43c)
#5 0x00007f4b3938f8fd n/a (libc.so.6 + 0x868fd)
#6 0x00007f4b39411a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1265:
#0 0x00007f4b3938c4b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007f4b3938ecd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007f4b3415650e n/a (iris_dri.so + 0x10c50e)
#3 0x00007f4b3410689c n/a (iris_dri.so + 0xbc89c)
#4 0x00007f4b3415643c n/a (iris_dri.so + 0x10c43c)
#5 0x00007f4b3938f8fd n/a (libc.so.6 + 0x868fd)
#6 0x00007f4b39411a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1262:
#0 0x00007f4b3938c4b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007f4b3938ecd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007f4b3415650e n/a (iris_dri.so + 0x10c50e)
#3 0x00007f4b3410689c n/a (iris_dri.so + 0xbc89c)
#4 0x00007f4b3415643c n/a (iris_dri.so + 0x10c43c)
#5 0x00007f4b3938f8fd n/a (libc.so.6 + 0x868fd)
#6 0x00007f4b39411a60 n/a (libc.so.6 + 0x108a60)
ELF object binary architecture: AMD x86-64
░░ Subject: Process 1251 (xfce4-session) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 1251 (xfce4-session) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Jan 06 15:27:01 charvey-media nmbd[903]: [2023/01/06 15:27:01.033411, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Jan 06 15:27:01 charvey-media nmbd[903]: *****
Jan 06 15:27:01 charvey-media nmbd[903]:
Jan 06 15:27:01 charvey-media nmbd[903]: Samba name server CHARVEY-MEDIA is now a local master browser for workgroup WORKGROUP on subnet 192.168.4.101
Jan 06 15:27:01 charvey-media nmbd[903]:
Jan 06 15:27:01 charvey-media nmbd[903]: *****
Jan 06 15:30:13 charvey-media systemd-coredump[1754]: Process 1737 (xfce4-session) of user 1000 dumped core.
Stack trace of thread 1737:
#0 0x00007face76c1048 g_log_structured_array (libglib-2.0.so.0 + 0x5d048)
#1 0x00007face76c1683 g_log_default_handler (libglib-2.0.so.0 + 0x5d683)
#2 0x00007face76c28b5 g_logv (libglib-2.0.so.0 + 0x5e8b5)
#3 0x00007face76c2b64 g_log (libglib-2.0.so.0 + 0x5eb64)
#4 0x00007face76c4797 g_log_set_writer_func (libglib-2.0.so.0 + 0x60797)
#5 0x00007face80d5a52 n/a (libgtk-3.so.0 + 0x3d2a52)
#6 0x00007face7edfed3 n/a (libgtk-3.so.0 + 0x1dced3)
#7 0x00007face77b7210 g_closure_invoke (libgobject-2.0.so.0 + 0x14210)
#8 0x00007face77e4ea8 n/a (libgobject-2.0.so.0 + 0x41ea8)
#9 0x00007face77d4f75 g_signal_emit_valist (libgobject-2.0.so.0 + 0x31f75)
#10 0x00007face77d5204 g_signal_emit (libgobject-2.0.so.0 + 0x32204)
#11 0x00007face77c1fc6 n/a (libgobject-2.0.so.0 + 0x1efc6)
#12 0x00007face77c8671 g_object_notify (libgobject-2.0.so.0 + 0x25671)
#13 0x00007face7c368bc n/a (libgdk-3.so.0 + 0x338bc)
#14 0x00007face77d511c g_signal_emit_valist (libgobject-2.0.so.0 + 0x3211c)
#15 0x00007face77d5424 g_signal_emit_by_name (libgobject-2.0.so.0 + 0x32424)
#16 0x00007face7c894af n/a (libgdk-3.so.0 + 0x864af)
#17 0x00007face7c36c46 gdk_display_manager_open_display (libgdk-3.so.0 + 0x33c46)
#18 0x00007face7ee4d50 gtk_init_with_args (libgtk-3.so.0 + 0x1e1d50)
#19 0x00005628305990c0 main (xfce4-session + 0x120c0)
#20 0x00007face74a0290 n/a (libc.so.6 + 0x23290)
#21 0x00007face74a034a __libc_start_main (libc.so.6 + 0x2334a)
#22 0x00005628305993c5 _start (xfce4-session + 0x123c5)
Stack trace of thread 1749:
#0 0x00007face75004b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007face7502cd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007face22ca50e n/a (iris_dri.so + 0x10c50e)
#3 0x00007face227a89c n/a (iris_dri.so + 0xbc89c)
#4 0x00007face22ca43c n/a (iris_dri.so + 0x10c43c)
#5 0x00007face75038fd n/a (libc.so.6 + 0x868fd)
#6 0x00007face7585a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1751:
#0 0x00007face75780bf __poll (libc.so.6 + 0xfb0bf)
#1 0x00007face7710bef n/a (libglib-2.0.so.0 + 0xacbef)
#2 0x00007face76b8132 g_main_context_iteration (libglib-2.0.so.0 + 0x54132)
#3 0x00007face76b8182 n/a (libglib-2.0.so.0 + 0x54182)
#4 0x00007face76e6e05 n/a (libglib-2.0.so.0 + 0x82e05)
#5 0x00007face75038fd n/a (libc.so.6 + 0x868fd)
#6 0x00007face7585a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1748:
#0 0x00007face75004b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007face7502cd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007face22ca50e n/a (iris_dri.so + 0x10c50e)
#3 0x00007face227a89c n/a (iris_dri.so + 0xbc89c)
#4 0x00007face22ca43c n/a (iris_dri.so + 0x10c43c)
#5 0x00007face75038fd n/a (libc.so.6 + 0x868fd)
#6 0x00007face7585a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1747:
#0 0x00007face75004b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007face7502cd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007face22ca50e n/a (iris_dri.so + 0x10c50e)
#3 0x00007face227a89c n/a (iris_dri.so + 0xbc89c)
#4 0x00007face22ca43c n/a (iris_dri.so + 0x10c43c)
#5 0x00007face75038fd n/a (libc.so.6 + 0x868fd)
#6 0x00007face7585a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1750:
#0 0x00007face75004b6 n/a (libc.so.6 + 0x834b6)
#1 0x00007face7502cd0 pthread_cond_wait (libc.so.6 + 0x85cd0)
#2 0x00007face22ca50e n/a (iris_dri.so + 0x10c50e)
#3 0x00007face227a89c n/a (iris_dri.so + 0xbc89c)
#4 0x00007face22ca43c n/a (iris_dri.so + 0x10c43c)
#5 0x00007face75038fd n/a (libc.so.6 + 0x868fd)
#6 0x00007face7585a60 n/a (libc.so.6 + 0x108a60)
Stack trace of thread 1752:
#0 0x00007face75780bf __poll (libc.so.6 + 0xfb0bf)
#1 0x00007face7710bef n/a (libglib-2.0.so.0 + 0xacbef)
#2 0x00007face76b8ddf g_main_loop_run (libglib-2.0.so.0 + 0x54ddf)
#3 0x00007face790eadc n/a (libgio-2.0.so.0 + 0x10aadc)
#4 0x00007face76e6e05 n/a (libglib-2.0.so.0 + 0x82e05)
#5 0x00007face75038fd n/a (libc.so.6 + 0x868fd)
#6 0x00007face7585a60 n/a (libc.so.6 + 0x108a60)
ELF object binary architecture: AMD x86-64
░░ Subject: Process 1737 (xfce4-session) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 1737 (xfce4-session) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
at this point - still unlikely to help but yes - as well as xorg
I can’t come up with anything - if everything is current, the coredump should not happen