Jose

Please, to summarise your system, post the O/P of:
 $ inxi -MSG

Is it worth looking in the system journal before these messages appear?

You cite libreoffice & mousepad, but say "this happend to other applications". Does this mean that the problem is widespread?

If you can find the Upgrade log, which is normally...
As root, look at:
 # ls -l /root/drakx/
for the files(s):
 /root/drakx/report.bug         [uncompressed]
 /root/drakx/report.bug.xz      [compressed]
but I am unsure if they apply to a Cauldron upgrade. If the dates correspond:

If only the compressed one (xz) is present, attach that to this bug.
If both are present with the same (upgrade) date, attach the compressed (xz) one.
If only the uncompressed file is present, or if both are present and the compressed (xz) file is older than uncompressed one, do:
 # xz /root/drakx/report.bug
which will create the corresponding compressed one - to attach to this bug.

CC: (none) => lewyssmith

(In reply to Lewis Smith from comment #1)
> Jose
> 
> Please, to summarise your system, post the O/P of:
>  $ inxi -MSG
> 
As is a VM I don't know if the information is useful but


inxi -MSG
System:
  Host: localhost Kernel: 6.6.87-desktop-1.mga10 arch: x86_64 bits: 64
  Desktop: LXDE v: 0.11.1 Distro: Mageia 10
Machine:
  Type: Kvm System: QEMU product: Standard PC (i440FX + PIIX, 1996)
    v: pc-i440fx-7.2 serial: <superuser required>
  Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.16.1-1.mga9
    date: 04/01/2014
Graphics:
  Device-1: Red Hat QXL paravirtual graphic card driver: qxl v: kernel
  Display: x11 server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 driver:
    X: loaded: modesetting unloaded: fbdev,vesa gpu: qxl
    resolution: 1360x690~60Hz
  API: OpenGL v: 4.5 vendor: mesa v: 25.0.4 renderer: llvmpipe (LLVM 19.1.3
    128 bits)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdpyinfo, xprop, xrandr

> Is it worth looking in the system journal before these messages appear?
> 
> You cite libreoffice & mousepad, but say "this happend to other
> applications". Does this mean that the problem is widespread?
> 
firefox not produce the message but gimp, filezilla, neochat, l3afpad does
Not have much time to test all the applications, even if are less than in
my real mageia 9 installation


> If you can find the Upgrade log, which is normally...
> As root, look at:
>  # ls -l /root/drakx/
> for the files(s):
>  /root/drakx/report.bug         [uncompressed]
>  /root/drakx/report.bug.xz      [compressed]
> but I am unsure if they apply to a Cauldron upgrade. If the dates correspond:
> 
drwx------ 2 root root    4096 ago  3  2024 drakx/
As I migrate by urpmi not recent information

I star to think is caused by lxdm with sddm not happen
I will be back to use lxdm to test, if not some update could have fixed this

Well lxdm is part of the equation, but enabling AT-SPDI-D-Bus bus at desktop start
is a workaround/solution

Leaving this with you for now, Jose. You are the best for chasing it.

A clarification please:
comment 0 says "The message goes away if I add before the application
NO_AT_BRIDGE=1" which is tedious;
and comment 4 says "enabling AT-SPDI-D-Bus bus at desktop start
is a workaround/solution" which looks simpler;

Do you need both? Or either?

Also, does the error message "dbind-WARNING **: 20:30:13.287: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Permiso denegado" have any negative effect on the application - like preventing it from starting? Or does the application continue anyway?

(In reply to Lewis Smith from comment #6)
> A clarification please:
> comment 0 says "The message goes away if I add before the application
> NO_AT_BRIDGE=1" which is tedious;
> and comment 4 says "enabling AT-SPDI-D-Bus bus at desktop start
> is a workaround/solution" which looks simpler;
> 
> Do you need both? Or either?
> 
> Also, does the error message "dbind-WARNING **: 20:30:13.287: Couldn't
> connect to accessibility bus: Failed to connect to socket
> /root/.cache/at-spi/bus_0: Permiso denegado" have any negative effect on the
> application - like preventing it from starting? Or does the application
> continue anyway?

Both things are true, the NO_AT_BRIDGE=1 is a solution I find in web searches
And Enable AT-SPDI-D-Bus bus at desktop start in the Lxde configuration tool is
what I find by testing

All the applications that produce the message starts, but I not test if exists some nasty effect , but quite sure is better to not have any potential issue.

Unsure where to push this. Is it a basesystem issue?
Assigning initially to NicolasS who seems to be the main packager for LXDE. But do please re-assign it to whoever you think is the best person; you are a better judge than me.

CC: lewyssmith => (none)
Assignee: bugsquad => nicolas.salguero

Not sure if related to make some test I remove lxde, and now I reinstall

I see this 

    39/61: mageia-lxde-config-Default
                                 ###################################################################################################
error al leer enlace /etc/xdg/lxsession/LXDE/desktop.conf: No existe el fichero o el directorio

Source RPM: lxdm,lxde-common,at-spi2-core => lxdm,lxde-common,at-spi2-core,mageia-lxde-config-0.6.4-10.mga9

This is still valid

Keywords: (none) => 10alpha1

Change keyword for flag status

Keywords: IN_ERRATA10 => (none)

Looks fixed now

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Flags: in_errata10+ => (none)