MX 25 Beta 1 Feedback thread

[Jerry3904]

I tried that but perhaps placed the flag in first position. Will look again,, thanks.

No change, but thanks. Maybe @dolphin_oracle has a solution?

[IoannisTsoulos]

Also, the brave browser does not work any more after switching to wayland

I see no issues here, can you elaborate? Is it not starting? What does it say if you type in konsole: brave-browser?
Can you provide QSI, did you install nvidia driver?

Here is the output for the brave-browser command:
brave-browser
[5048:5048:0925/180114.379524:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[5048:5048:0925/180114.379858:ERROR:components/os_crypt/sync/kwallet_dbus.cc:113] Error contacting kwalletd6 (isEnabled)
[5048:5048:0925/180114.380134:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[5048:5048:0925/180114.380143:ERROR:components/os_crypt/sync/kwallet_dbus.cc:82] Error contacting klauncher to start kwalletd6
[5048:5048:0925/180114.577934:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[5048:5048:0925/180114.577960:ERROR:components/os_crypt/sync/kwallet_dbus.cc:408] Error contacting kwalletd6 (close)
[5048:5048:0925/180114.793421:ERROR:components/dbus/xdg/request.cc:169] Request ended (non-user cancelled).

The application starts, but I can not open any url. It seems to not responding. The application works fine in X11 environment

[Adrian]

It works here (I do see similar messages in terminal) so not sure what is going on, I guess use Xorg if that works for you, I don't think I can test and figure out the issue if I cannot replicate.

[Melber]

I asked that during the development phase, thanks for bringing it up again. If it makes no difference with the other wallpapers I would like to see it enabled. Reading man nitrogen, it seems like this change to ~/.config/nitrogen/nitrogen.cfg might work:

Code: Select all

[geometry]
posx=366
posy=132
sizex=1110
sizey=923

[nitrogen]
view=icon
set-scaled=true
recurse=true
sort=rtime
icon_caps=false
dirs=/usr/share/backgrounds;/home/jb/.fluxbox/backgrounds;

No, that appears to have no effect. Maybe we need to use the flag somewhere else?

Code: Select all

--set-scaled

I think you need to start nitrogen with the options in the startup file?

Code: Select all

nitrogen --restore --set-scaled

I tried that but perhaps placed the flag in first position. Will look again,, thanks.

No change, but thanks. Maybe @dolphin_oracle has a solution?

@Jerry3904 @chrispop99

startup file currently has this

Code: Select all

#restore from saved background if exists and nitrogen installed
if [ -x "/usr/bin/nitrogen" ]; then
    if [ -e "$HOME/.config/nitrogen/bg-saved.cfg" ]; then
        (sleep 1; nitrogen --restore & )
    else
        # set default background
        (sleep 1; nitrogen --set-auto /usr/share/backgrounds/default25.png)
    fi
fi

Think it should be changed to this

Code: Select all

#restore from saved background if exists and nitrogen installed
if [ -x "/usr/bin/nitrogen" ]; then
    if [ -e "$HOME/.config/nitrogen/bg-saved.cfg" ]; then
        (sleep 1; nitrogen --restore & )
    else
        # set default background
        (sleep 1; nitrogen --set-scaled /usr/share/backgrounds/default25.png)
    fi
fi

nitrogen first creates a bg-saved.cfg when you change the wallpaper.

+++

[dolphin_oracle]

I tried that but perhaps placed the flag in first position. Will look again,, thanks.

No change, but thanks. Maybe @dolphin_oracle has a solution?

yes.

in the .fluxbox/startup file change this:

Code: Select all

#get last background selected
#~/.fehbg
#restore from saved background if exists and nitrogen installed
if [ -x "/usr/bin/nitrogen" ]; then
    if [ -e "$HOME/.config/nitrogen/bg-saved.cfg" ]; then
        (sleep 1; nitrogen --restore & )
    else
        # set default background
        (sleep 1; nitrogen --set-auto /usr/share/backgrounds/default25.png)
    fi
fi

to this

Code: Select all

#get last background selected
#restore from saved background if exists and nitrogen installed
if [ -x "/usr/bin/nitrogen" ]; then
    if [ -e "$HOME/.config/nitrogen/bg-saved.cfg" ]; then
        (sleep 1; nitrogen --restore & )
    else
        # set default background
        (sleep 1; nitrogen --set-scaled /usr/share/backgrounds/default25.png)
    fi
fi

the way that works, --set-scaled is only explicitly used for the default background, and even then only if the bg-saved.cfg folder does not exist. the config file will take over from there when bg-saved.cfg exists.

[IoannisTsoulos]

It works here (I do see similar messages in terminal) so not sure what is going on, I guess use Xorg if that works for you, I don't think I can test and figure out the issue if I cannot replicate.

I have some strange issues in X11. The mouse clicks may times seem to be ignored by the system and the smplayer has some lags to play videos

[kmathern]

.
.
.
Here are my boot options
BOOT_IMAGE=/boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=121a82e6-02c9-4580-9ff4-f4e1ec71dbd2 ro quiet splash nvidia-drm.modeset=1

I see an additional nvidia related boot option mentioned here https://wiki.debian.org/NvidiaGraphicsD ... odesetting

Code: Select all

nvidia-drm.fbdev=1

[Jerry3904]

Thanks--just finishing mx-fluxbox changes so will test and push later.

[Jerry3904]

Before I send mx-fluxbox up, I received a message that we have not enabled spice-vdagent in fluxbox. I made no such decision so I need to ask: is its absence commission (intentional) or omission (accidental)? If the latter, can I just paste in the stanza in 23.6 startup again?

Code: Select all

# start spice-vdagent in KVM/Qemu 
if [ -x /usr/bin/spice-vdagent ]; then
   pidof -q spice-vdagentd && /usr/bin/spice-vdagent
fi

Thanks.

----------
Oh, and can picom be made available for MX-23 -- wrote only mx-25 in the Wiki article. picom is installed and active by default in 23.6

[fehlix]

Before I send mx-fluxbox up, I received a message that we have not enabled spice-vdagent in fluxbox. I made no such decision so I need to ask: is its absence commission (intentional) or omission (accidental)? If the latter, can I just paste in the stanza in 23.6 startup again?

Code: Select all

# start spice-vdagent in KVM/Qemu 
if [ -x /usr/bin/spice-vdagent ]; then
   pidof -q spice-vdagentd && /usr/bin/spice-vdagent
fi

Thanks.

maybe delay 5 sec, check daemon is running and agent is not running to avoid running twice, into background.
e.g. with:

Code: Select all

# start spice-vdagent in KVM/Qemu 
if [ -x /usr/bin/spice-vdagent ]; then
   (sleep 5 && pidof -q  spice-vdagentd && ! pidof -q  spice-vdagent &&  /usr/bin/spice-vdagent)&
fi