MX-23 beta 1 feedback thread

Message
Author
User avatar
dolphin_oracle
Developer
Posts: 22277
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 beta 1 feedback thread

#131 Post by dolphin_oracle »

siamhie wrote: Tue May 30, 2023 3:13 pm
dolphin_oracle wrote: Tue May 30, 2023 3:00 pm its a user service, like pipewire. which also isn't in your list @siamhie
@dolphin_oracle pipewire shows at the bottom. Is that what you were referring to?

Code: Select all

siamhie@mxflux23:~
$ systemctl status
● mxflux23
    State: degraded
    Units: 399 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 1 units
    Since: Tue 2023-05-30 05:09:26 PDT; 7h ago
  systemd: 1:252.6-1mx23+1
  Tainted: local-hwclock
   CGroup: /
           ├─init.scope
           │ └─1 /lib/systemd/systemd
           ├─system.slice
           │ ├─ModemManager.service
           │ │ └─1115 /usr/sbin/ModemManager
           │ ├─accounts-daemon.service
           │ │ └─1064 /usr/libexec/accounts-daemon
           │ ├─acpi-fakekey.service
           │ │ └─1065 /usr/sbin/acpi_fakekeyd -f
           │ ├─acpid.service
           │ │ └─1066 /usr/sbin/acpid
           │ ├─avahi-daemon.service
           │ │ ├─1070 "avahi-daemon: running [mxflux23.local]"
           │ │ └─1074 "avahi-daemon: chroot helper"
           │ ├─bluetooth.service
           │ │ └─1072 /usr/libexec/bluetooth/bluetoothd
           │ ├─cron.service
           │ │ └─1073 /usr/sbin/cron -f
           │ ├─cups-browsed.service
           │ │ └─1400 /usr/sbin/cups-browsed
           │ ├─dbus.service
           │ │ ├─1075 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
           │ │ └─2180 /usr/libexec/corectrl/corectrl_helper
           │ ├─emby-server.service
           │ │ └─1401 /opt/emby-server/system/EmbyServer -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-se>
           │ ├─haveged.service
           │ │ └─1042 /usr/sbin/haveged --Foreground --verbose=1
           │ ├─lightdm.service
           │ │ ├─1414 /usr/sbin/lightdm
           │ │ └─1437 /usr/lib/xorg/Xorg -dpi "\$DPI" :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
           │ ├─network-manager.service
           │ │ └─1176 /usr/sbin/NetworkManager
           │ ├─nfs-blkmap.service
           │ │ └─1060 /usr/sbin/blkmapd
           │ ├─nfs-idmapd.service
           │ │ └─1062 /usr/sbin/rpc.idmapd
           │ ├─nfs-mountd.service
           │ │ └─1411 /usr/sbin/rpc.mountd
           │ ├─nfsdcld.service
           │ │ └─1063 /usr/sbin/nfsdcld
           │ ├─ntpsec.service
           │ │ └─2007 /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
           │ ├─polkit.service
           │ │ └─1083 /usr/lib/polkit-1/polkitd --no-debug
           │ ├─rpc-statd.service
           │ │ └─1412 /sbin/rpc.statd
           │ ├─rpcbind.service
           │ │ └─1053 /sbin/rpcbind -f -w
           │ ├─rsyslog.service
           │ │ └─1087 /usr/sbin/rsyslogd -n -iNONE
           │ ├─smartmontools.service
           │ │ └─1088 /usr/sbin/smartd -n
           │ ├─system-getty.slice
           │ │ └─getty@tty1.service
           │ │   └─1448 /sbin/agetty -o "-p -- \\u" --noclear - linux
           │ ├─systemd-journald.service
           │ │ └─512 /lib/systemd/systemd-journald
           │ ├─systemd-logind.service
           │ │ └─1090 /lib/systemd/systemd-logind
           │ ├─systemd-udevd.service
           │ │ └─udev
           │ │   └─531 /lib/systemd/systemd-udevd
           │ ├─udisks2.service
           │ │ └─1091 /usr/libexec/udisks2/udisksd
           │ ├─unattended-upgrades.service
           │ │ └─1410 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
           │ └─wpa_supplicant.service
           │   └─1117 /sbin/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev"
           └─user.slice
             └─user-1000.slice
               ├─session-1.scope
               │ ├─1650 lightdm --session-child 13 16
               │ ├─1679 fluxbox
               │ ├─1716 /usr/bin/dbus-launch --exit-with-session --sh-syntax
               │ ├─1717 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
               │ ├─1770 /usr/bin/ssh-agent /usr/bin/startfluxbox
               │ ├─1789 compton
               │ ├─1796 tint2 -c /home/siamhie/.config/tint2/tint2rc
               │ ├─1797 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
               │ ├─1801 nm-applet
               │ ├─1822 /usr/libexec/gvfsd
               │ ├─1827 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
               │ ├─1996 xfce4-clipman
               │ ├─1997 /usr/libexec/at-spi-bus-launcher --launch-immediately
               │ ├─2004 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=>
               │ ├─2017 /usr/libexec/xdg-desktop-portal
               │ ├─2022 /usr/libexec/xdg-document-portal
               │ ├─2026 /usr/libexec/xdg-permission-store
               │ ├─2032 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
               │ ├─2038 /usr/libexec/xdg-desktop-portal-gtk
               │ ├─2052 /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
               │ ├─2054 corectrl
               │ ├─2063 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
               │ ├─2065 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
               │ ├─2302 /usr/libexec/at-spi2-registryd --use-gnome-session
               │ ├─2363 /usr/bin/python3 /usr/lib/apt-notifier/modules/apt-notifier.py
               │ ├─2477 /bin/bash /tmp/conky-manager2-siamhie/16854737871749932149.sh
               │ ├─2478 conky -c /home/siamhie/.conky/R8/r8
               │ ├─2535 /usr/libexec/gvfsd-metadata
               │ ├─2558 xfce4-terminal
               │ ├─2580 bash
               │ ├─2641 systemctl status
               │ └─2642 pager
               └─user@1000.service
                 ├─app.slice
                 │ └─gnome-keyring-daemon.service
                 │   └─2069 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
                 ├─init.scope
                 │ ├─1659 /lib/systemd/systemd --user
                 │ └─1660 "(sd-pam)"
                 └─session.slice
                   ├─pipewire-pulse.service
                   │ └─1677 /usr/bin/pipewire-pulse
                   └─pipewire.service
                     └─1675 /usr/bin/pipewire
I honestly don't understand why wireplumber doesn't start on fluxbox/systemd. unless there is something that happens on the full DEs (kde, xfce) that doesn't happen when starting fluxbox. off the top of my head I don't know what that would be. In my tests, even going just to a console, the audio services all started under systemd at login.

previously the pipewire-start script was force-loading wireplumber in all cases. I guess it can still do that, but under KDE and Xfce it was killing an existing running service and starting a new one.

will investigate some more.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Developer
Posts: 22277
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 beta 1 feedback thread

#132 Post by dolphin_oracle »

@siamhie is dbus-user-session installed on the fluxbox iso?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
siamhie
Global Moderator
Posts: 3368
Joined: Fri Aug 20, 2021 5:45 pm

Re: MX-23 beta 1 feedback thread

#133 Post by siamhie »

dolphin_oracle wrote: Tue May 30, 2023 3:27 pm
I honestly don't understand why wireplumber doesn't start on fluxbox/systemd. unless there is something that happens on the full DEs (kde, xfce) that doesn't happen when starting fluxbox. off the top of my head I don't know what that would be. In my tests, even going just to a console, the audio services all started under systemd at login.

previously the pipewire-start script was force-loading wireplumber in all cases. I guess it can still do that, but under KDE and Xfce it was killing an existing running service and starting a new one.

will investigate some more.

@dolphin_oracle Would it just be easier to have wireplumber placed in fluxbox's startup script. That way the other desktops (XFCE, KDE) won't get affected? I wonder if other fluxbox testers are experiencing this.

Code: Select all

#start pipewire before volumeicon so unmute works
#wireplumber &
pipewire-start
sleep 2
volumeicon -c volumeicon-fluxbox & 

Maybe it might be my onboard sound. MSI B550-A Pro motherboard. Just thinking out loud.

Code: Select all

Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 14:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.1.0-9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

User avatar
siamhie
Global Moderator
Posts: 3368
Joined: Fri Aug 20, 2021 5:45 pm

Re: MX-23 beta 1 feedback thread

#134 Post by siamhie »

dolphin_oracle wrote: Tue May 30, 2023 3:43 pm @siamhie is dbus-user-session installed on the fluxbox iso?

@dolphin_oracle How would I check that? I did flash the ISO with MX Live USB Maker.
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

User avatar
dolphin_oracle
Developer
Posts: 22277
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 beta 1 feedback thread

#135 Post by dolphin_oracle »

siamhie wrote: Tue May 30, 2023 3:53 pm
dolphin_oracle wrote: Tue May 30, 2023 3:43 pm @siamhie is dbus-user-session installed on the fluxbox iso?

@dolphin_oracle How would I check that? I did flash the ISO with MX Live USB Maker.

Code: Select all

apt-policy dbus-user-session
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Developer
Posts: 22277
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 beta 1 feedback thread

#136 Post by dolphin_oracle »

siamhie wrote: Tue May 30, 2023 3:50 pm
dolphin_oracle wrote: Tue May 30, 2023 3:27 pm
I honestly don't understand why wireplumber doesn't start on fluxbox/systemd. unless there is something that happens on the full DEs (kde, xfce) that doesn't happen when starting fluxbox. off the top of my head I don't know what that would be. In my tests, even going just to a console, the audio services all started under systemd at login.

previously the pipewire-start script was force-loading wireplumber in all cases. I guess it can still do that, but under KDE and Xfce it was killing an existing running service and starting a new one.

will investigate some more.

@dolphin_oracle Would it just be easier to have wireplumber placed in fluxbox's startup script. That way the other desktops (XFCE, KDE) won't get affected? I wonder if other fluxbox testers are experiencing this.

Code: Select all

#start pipewire before volumeicon so unmute works
#wireplumber &
pipewire-start
sleep 2
volumeicon -c volumeicon-fluxbox & 

Maybe it might be my onboard sound. MSI B550-A Pro motherboard. Just thinking out loud.

Code: Select all

Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 14:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.1.0-9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
since the pipewire-start script starts up wireplumber, no, that would put two entries in effect when booting with sysVinit.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
entropyfoe
Posts: 615
Joined: Thu Apr 19, 2007 11:42 am

Re: MX-23 beta 1 feedback thread

#137 Post by entropyfoe »

Wow, just wow. This is a great win for the dev team, the beta is wonderful.

I downloaded the iso (XFCE 64 bit) , md5 was good, burned to a 4G stick with the MX live USB creator under MX 21.

Booted fine, the internet and sound worked live, so time to hit the install button to my testing partition, grub to root. Installed fine, I remembered to enable the existing swap. I like that start animation of the MX logo, looks good.
Did an immediate synaptic upgrades, 63 of them. I then installed my favorite applications, got all but two, not showstoppers, this adds 154 packages with all the dependencies.

Missing for me is jerry - a non essential chess program as scid can do most of that
Missing is fsearch, that is a great tool, it will probably get packaged in due time. :happy:
Nice touch stock fish goes from version 12 to 15. That is about +130 Elo points ! : :cool:

Installed the NVIDIA driver with the MX tool, worked flawlessly, getting the 470.182.03-1.

Rebooted, into MX 21 to update-grub, and when I boot the new MX 23 is in the grub menu, I select it and all is working.

During the boot I see rrand is not reliable in this platform. Not an MX problem, but the error message is way shorter than in MX 21 ! :happy:

Nice touch, the 6.1 kernel. [edit] that is a LTS kernel. :happy:

Then I start with my list of tweaks

Code: Select all

1. Enable my data disk in the disk manager
2. Change my wall paper
3. Fire up synaptic and load about 30 programs (adds to maybe 160 packages with all dependencies) Such as audacity, k3b, ksnip, bleachbit, ripperx, handbrake, scid, stockfish, eboard, espeak....I really should automate this with aptik !
4. Run synaptic to get all updates
5.Widen the panel, change the clock so it shows seconds
6. Install the NVidia driver with the MX Package Installer
7. Switch conky to the modified antiX conky
8. Set up a desktop short cut to the data drive
9. Run bleachbit to clear all the post install stuff out
10. Reboot and test stability after all the up dates
11. Configure Firefox, set home page to duckduckgo, set downloads to go to a folder on the data drive, import bookmarks, add noscript
12. Disable sudo -MX Tweak > Other tab > radial button at the bottom labeled accordingly
13. In power management set so no log-in is required from suspend
All went well except after a reboot the desktop wall paper came back as the stock instead of the one I had installed, I have seen this on other new installs a few time, I will repeat and investigate.

But this will be a daily driver for me for at least a few days with further testing and work loads.

Code: Select all

System:
  Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64
    root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_beta1_x64 Libretto May 28  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 5204 date: 07/29/2019
CPU:
  Info: model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0
    microcode: 0x8701013
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2151 high: 2208 min/max: 2200/4409 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1985 2: 2208 3: 1863 4: 2200 5: 2196 6: 2195
    7: 2200 8: 2200 9: 2176 10: 2196 11: 2200 12: 2200 bogomips: 91028
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: always-on, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI driver: nvidia v: 470.182.03
    non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2 code: GF119/GK208
    process: TSMC 28nm built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 09:00.0
    chip-ID: 10de:128b class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
    gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.04x11.26")
    diag: 584mm (22.99") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.182.03 renderer: NVIDIA GeForce GT 710/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 09:00.1 chip-ID: 10de:0e0f class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.1.0-9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.25 TiB used: 566.55 GiB (44.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 2B2QEXM7 temp: 36.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5B0Q
    scheme: MBR
Partition:
  ID-1: / raw-size: 88.35 GiB size: 86.41 GiB (97.80%) used: 8.15 GiB (9.4%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32.23 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
  System Temperatures: cpu: 48.0 C mobo: 32.0 C gpu: nvidia temp: 49 C
  Fan Speeds (RPM): cpu: 602 case-1: 0 case-2: 941 case-3: 888 gpu: nvidia fan: 50%
  Power: 12v: 12.16 5v: N/A 3.3v: N/A vbat: N/A
Repos:
  Packages: pm: dpkg pkgs: 2301 libs: 1234 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 283 Uptime: 26m wakeups: 2 Memory: 31.26 GiB used: 2.2 GiB (7.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Last edited by entropyfoe on Tue May 30, 2023 8:39 pm, edited 2 times in total.
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound

User avatar
dolphin_oracle
Developer
Posts: 22277
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 beta 1 feedback thread

#138 Post by dolphin_oracle »

@siamhie probably is almost certainly the missing dbus-user-session.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Jerry3904
Administrator
Posts: 23223
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-23 beta 1 feedback thread

#139 Post by Jerry3904 »

dolphin_oracle wrote: Tue May 30, 2023 4:35 pm @siamhie probably is almost certainly the missing dbus-user-session.
Is that something you take care of or should I inform @m_pav about that?
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
Melber
Developer
Posts: 1311
Joined: Tue Mar 23, 2021 4:19 pm

Re: MX-23 beta 1 feedback thread

#140 Post by Melber »

Jerry3904 wrote: Tue May 30, 2023 3:23 pm I'm still fooling around from time to time with that autohide dock problem, which annoys me. I used dockmaker to match the background and border to the color of the sand on the bottom of the screen. There is still a blue line around the dock itself:
...
@Melber is that from you? If yes, I wonder if that might be causing these sporadic problems.
I don't think the border is the issue, but the fluxbox style may be.
The border around the dock is set in the MX-comfort fluxbox style. I tried a copy without the border and it behaved the same way.

From my testing the following fluxbox styles work with dock autohide and any dock placement
bloe
bora_blue
bora_black
bora_green
carp
debian-dark
green-tea
ostrich
zimek_bisque
zimek_darkblue
zimek_green
All other styles (including the MX-comfort styles) only show a hidden dock with the placement is set to RightTop, RightCenter or RightBottom.
With any other placement the hidden dock refuses to slide out.

Had a quick scan over the various fluxbox style theme.cfg files but no difference between working and not-working themes jumped out at me.

Locked

Return to “General”