MX-23 beta 2 feedback thread

[Melber]

MX-23beta2 Fluxbox updated!

I like the new MXFB-tour, but I'm a little bit skeptical about its new fully transparent icon with the fully transparent description in the Polish localization...


https://imgur.com/S4rtV3F.png



Moderator: image changed to link, please read the forum rules

.desktop file needs correcting
- Translation is empty for several languages, incliding pl
- remove .svg from icon name

[davemx]

Not a problem. @davemx: the only question for this thread is whether the default conky that MX delivers with MX-23 works on your machine. Otherwise please start a separate thread of your own--and state right at the beginning that you have modified the original.

+1 Thank you @Jerry3904

@davemx Start a new thread chornicalling your conky issues your seeing with you\re modified code.

It's great fun being piled on! Not. Especially by people who did not read my posts properly.

If you read my posts, you would see that after my amended version of Geeky-Tower didn't work properly, I created a temporary user, and loaded the ORIGINAL UNMODIFIED Geeky-Tower conky, as supplied with MX23ß2, and exactly the same thing happened. I suspected that maybe I needed to install a package or something. So, have you made the graph black since version 21 when it was white?

[Jerry3904]

First of all: we were just trying to help in response to this first post of yours:

Anyway, in conky, MX-GeekyTowerLogo doesn't fully work because ${downspeedgraph and ${upspeedgraph don't work. They just return an empty box. However, ${downspeedf and ${upspeedf do work. Does it need some sort of driver to be installed, or is it just not compatible with certain updates?

Second: "I" didn't change anything but something may have happened during the complex migration development to MX-23. You can easily just change it to any color you like with MX Conky (details in its Help file).

[Wallon]

Hello Everyone,

Today I bought a very good Samsung "Champagne Silver" 128GB - 400MB/s USB key to install MX Fluxbox 23 in the fr_BE language.

My day had started well but... it's not ending well. I have to stay calm because Eadwine Rose is keeping an eye on the forum.

I created the Live USB stick with Rufus as always. My stick is recognised straight away. I chose the language fr_BE and the time zone "Brussels". I run the md5 check and all the files are OK. My Belgian Azerty keyboard is recognised. It's different from the Azerty keyboard for France and that's a good thing.

I discover a Live key that mixes English and [fr] translations. I don't see many things translated into [fr_BE].

Three icons at the top of the screen don't work (Videos - Software - Install MX).

On the left of the screen, I have a dock with 3 icons. The tooltips are in English for;
1) MX Tools
2) Help
3) Settings Manager

If I click on the "Settings Manager" icon, the new window is all in English.
It's discouraging to translate...

If I click on the desktop, I get a half-English / half-French menu (see screenshot). It's really Pfffooouuuuu.

As the "Install MX" icon doesn't work and I couldn't find an option in the menu to launch the installation, I wasn't able to install MX FluxBox on my new Samsung USB key.

Honestly, what's going on?

Wallon

[Eadwine Rose]

The easiest thing to check.. did the download's check out (md5sum etc)? Did the stick's check turn out ok?

[Jerry3904]

Sounds like a complete gachis.

--Which version of MX-23 did you download? alpha 1/2, beta 1/2?
--All the desktop icons didn't work?! I have never seen that in testing and don't understand how that could happen.
--That All Apps script may not be localized (I'll check), but no one has ever pointed that out. The rest of the Root Menu should be.
--The Settings Manager is just picking up applications from /usr/share/applications so if the desktop files are localized I would expect it to show correctly. Some desktop files may only be localized to fr--but I don't know if that would make a difference to what you see.

[davemx]

First of all: we were just trying to help in response to this first post of yours:

Anyway, in conky, MX-GeekyTowerLogo doesn't fully work because ${downspeedgraph and ${upspeedgraph don't work. They just return an empty box. However, ${downspeedf and ${upspeedf do work. Does it need some sort of driver to be installed, or is it just not compatible with certain updates?

Second: "I" didn't change anything but something may have happened during the complex migration development to MX-23. You can easily just change it to any color you like with MX Conky (details in its Help file).

Sadly, in English we have only one word for You, whether singular or plural. I meant that a few people (you plural) chimed in telling me to start a new thread, despite the fact that I had clarified that I had tested the conky script as supplied by MX as a temporary user.

Anyway, I went into my MX21-Xfce, and added the Geeky-Tower conky from MX23, unamended, with a white graph, and it worked perfectly. I then rebooted to MX23-beta and the self-same conky had the same problem, and ${downspeedgraph and ${upspeedgraph did not work. To be honest, even if it was black rather than white I could have seen it as it is over a grey area of desktop. I have no idea why this should be, and I reckon that if/when I install the new version, it will probably start working when I install another package! Anyway I have a more serious problem, which I will make another post for in this thread.

[siamhie]

So, have you made the graph black since version 21 when it was white?

@davemx Nothing has changed.

mx21.3 fluxbox

Code: Select all

${color2}ETHERNET (${addr ${template4}}) ${hr 2}${color}
   Down: ${downspeedf ${template4}}kB/s ${alignr}Up: ${upspeedf ${template4}}kB/s
   ${downspeedgraph ${template4} 30,120 000000 000000} ${alignr}${upspeedgraph ${template4} 30,120 000000 000000}${else}\
${if_up ${template5}}${color2}
ETHERNET (${addr ${template5}}) ${hr 2}${color}
   Down: ${downspeedf ${template5}}kB/s ${alignr}Up: ${upspeedf ${template5}}kB/s
   ${downspeedgraph ${template5} 30,120 000000 000000} ${alignr}${upspeedgraph ${template5} 30,120 000000 000000}${endif}${endif}\
${if_up ${template6}}${color2}
WIRELESS (${addr ${template6}}) [${wireless_link_qual_perc ${template6}}%] ${hr 2}${color}
   Down: ${downspeedf ${template6}}kB/s ${alignr}Up: ${upspeedf ${template6}}kB/s
   ${downspeedgraph ${template6} 30,120 000000 000000} $alignr${upspeedgraph ${template6} 30,120 000000 000000}${else}
${if_up ${template7}}${color2}
WIRELESS (${addr ${template7}}) [${wireless_link_qual_perc ${template7}}%] ${hr 2}${color}
   Down: ${downspeedf ${template7}}kB/s ${alignr}Up: ${upspeedf ${template7}}kB/s
   ${downspeedgraph ${template7} 30,120 000000 000000} $alignr${upspeedgraph ${template7} 30,120 000000 000000}${endif}${endif}

mx21.3 xfce june snapshot

Code: Select all

${color2}ETHERNET (${addr ${template4}}) ${hr 2}${color}
   Down: ${downspeedf ${template4}}kB/s ${alignr}Up: ${upspeedf ${template4}}kB/s
   ${downspeedgraph ${template4} 30,120 000000 000000} ${alignr}${upspeedgraph ${template4} 30,120 000000 000000}${else}\
${if_up ${template5}}${color2}
ETHERNET (${addr ${template5}}) ${hr 2}${color}
   Down: ${downspeedf ${template5}}kB/s ${alignr}Up: ${upspeedf ${template5}}kB/s
   ${downspeedgraph ${template5} 30,120 000000 000000} ${alignr}${upspeedgraph ${template5} 30,120 000000 000000}${endif}${endif}\
${if_up ${template6}}${color2}
WIRELESS (${addr ${template6}}) [${wireless_link_qual_perc ${template6}}%] ${hr 2}${color}
   Down: ${downspeedf ${template6}}kB/s ${alignr}Up: ${upspeedf ${template6}}kB/s
   ${downspeedgraph ${template6} 30,120 000000 000000} $alignr${upspeedgraph ${template6} 30,120 000000 000000}${else}
${if_up ${template7}}${color2}
WIRELESS (${addr ${template7}}) [${wireless_link_qual_perc ${template7}}%] ${hr 2}${color}
   Down: ${downspeedf ${template7}}kB/s ${alignr}Up: ${upspeedf ${template7}}kB/s
   ${downspeedgraph ${template7} 30,120 000000 000000} $alignr${upspeedgraph ${template7} 30,120 000000 000000}${endif}${endif}

mx23 fluxbox beta2

Code: Select all

${color2}ETHERNET (${addr ${template4}}) ${hr 2}${color}
   Down: ${downspeedf ${template4}}kB/s ${alignr}Up: ${upspeedf ${template4}}kB/s
   ${downspeedgraph ${template4} 30,120 000000 000000} ${alignr}${upspeedgraph ${template4} 30,120 000000 000000}${else}\
${if_up ${template5}}${color2}
ETHERNET (${addr ${template5}}) ${hr 2}${color}
   Down: ${downspeedf ${template5}}kB/s ${alignr}Up: ${upspeedf ${template5}}kB/s
   ${downspeedgraph ${template5} 30,120 000000 000000} ${alignr}${upspeedgraph ${template5} 30,120 000000 000000}${endif}${endif}\
${if_up ${template6}}${color2}
WIRELESS (${addr ${template6}}) [${wireless_link_qual_perc ${template6}}%] ${hr 2}${color}
   Down: ${downspeedf ${template6}}kB/s ${alignr}Up: ${upspeedf ${template6}}kB/s
   ${downspeedgraph ${template6} 30,120 000000 000000} $alignr${upspeedgraph ${template6} 30,120 000000 000000}${else}
${if_up ${template7}}${color2}
WIRELESS (${addr ${template7}}) [${wireless_link_qual_perc ${template7}}%] ${hr 2}${color}
   Down: ${downspeedf ${template7}}kB/s ${alignr}Up: ${upspeedf ${template7}}kB/s
   ${downspeedgraph ${template7} 30,120 000000 000000} $alignr${upspeedgraph ${template7} 30,120 000000 000000}${endif}${endif}

All graph colors are black by default (000000 000000). Start a new thread (maybe title it geekytowerLogo or something) so that we can further help you.

[davemx]

This is probably an idiosyncratic problem, but I have orage dependent on vdirsyncer which is in turn dependent on a legacy link to my Google account, which breaks their new OAuth rules. As I had already set up this link, I just had to change it to "testing" and it still works! For this I need legacy vdirsyncer version 18 and requests-oauthlib. I do keep searching on the net trying to work out how to set it all up under the new rules, but I can't find anything that makes sense. If anyone can point me in the right direction, I would have a go at it.

Sadly, something in the new version blocks me from adding legacy vdirsyncer via "pip3 install", and the version in MX/Debian repos is 19. Is there a way that I can over-ride the block and install the versions I need?

[Wallon]

Dear Jerry,

Here's the inxi from my Live USB stick regarding MX Fluxbox 23

Kind regards,
Wallon

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: lang=fr_BE
    tz=Europe/Brussels quiet splasht nosplash
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0
    Distro: MX-23_fluxbox_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: MSI model: H170M PRO-VDH (MS-7982) v: 1.0 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 2.F0 date: 06/27/2018
CPU:
  Info: model: Intel Core i5-6400 bits: 64 type: MCP arch: Skylake-S gen: core 6 level: v3
    note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
    microcode: 0xC6
  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: 2700 min/max: 800/3300 scaling: driver: intel_pstate governor: powersave
    cores: 1: 2700 2: 2700 3: 2700 4: 2700 bogomips: 21599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Micro-Star MSI driver: nouveau v: kernel
    non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm
    built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: DP-1,HDMI-A-1 empty: DP-2,DP-3,DVI-I-1 bus-ID: 01:00.0 chip-ID: 10de:1401
    class-ID: 0300 temp: 45.0 C
  Device-2: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-6:3
    chip-ID: 046d:082d class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: nouveau gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
    s-diag: 1055mm (41.54")
  Monitor-1: DP-1 pos: primary,left model: AOC 2590G5 serial: <filter> built: 2021 res: 1920x1080
    hz: 60 dpi: 90 gamma: 1.2 size: 544x303mm (21.42x11.93") diag: 623mm (24.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: right model: MD20830 serial: <filter> built: 2016
    res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NV126 direct-render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 1-6:3 bus-ID: 00:1f.3 chip-ID: 046d:082d
    chip-ID: 8086:a170 class-ID: 0102 class-ID: 0403 serial: <filter>
  Device-2: NVIDIA GM206 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
    chip-ID: 10de:0fba class-ID: 0403
  Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo
  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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 1.69 GiB (0.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SUV400S37240G size: 223.57 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: D6SD scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM003-1SB102 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC43 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: SD9SN8W256G size: 232.89 GiB
    block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 1012 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-4: /dev/sdd maj-min: 8:48 type: USB model: USB DISK 2.0 size: 29.83 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: DL07 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc1
    maj-min: 8:33
Sensors:
  System Temperatures: cpu: 34.0 C pch: 47.0 C mobo: N/A gpu: nouveau temp: 45.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0
Repos:
  Packages: pm: dpkg pkgs: 1802 libs: 881 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free
  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://mirror.tiguinet.net/mx/packages/mx/repo/ bookworm main non-free
Info:
  Processes: 200 Uptime: 1m wakeups: 1 Memory: 15.57 GiB used: 860 MiB (5.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)