MX-23 beta 2 feedback thread

Message
Author
User avatar
gRegNfo
Posts: 35
Joined: Sat Jun 10, 2023 6:30 am

Re: MX-23 beta 2 feedback thread

#231 Post by gRegNfo »

It's not a big thing, but apt sources.list mention in the description BULLSEYE although the deb URL is correctly pointing to Bookworm. Just that.
ASUS Laptop N56VB 1080p
i7-3630QM 2.40GHz Ivy Bridge
16GB DDR3 1600 MHz
2TB HW/SSD RAID-0 SATA3
Intel HD4000 IVB GT2
NVIDIA GK107M GeForce GT-740M 2GB VRAM
Intel Centrino WiFi-N 2230
Qualcomm Atheros AR8161 Gigabit
Intel 7 C210/C216/HM76 Express Chipset

andy
Posts: 99
Joined: Tue Oct 26, 2021 1:08 pm

Re: MX-23 beta 2 feedback thread

#232 Post by andy »

keos wrote: Thu Jun 22, 2023 3:22 pm @j2mcgreg

I can not understand, I guess it is a very difficult issue, if you mean the new version ... because the one I have is ventoy-1.0.63 which is the same one I made mx-21 with. Any way thank for trying to help.
Hi @keos,
current Ventoy version is 1.0.91.
https://www.ventoy.net/en/doc_news.html
Every ISO of particular distribution version can be slightly different and therefore some older Ventoy versions might not recognize it correctly, and did not apply particular treatment to boot it correctly.
This is your issue. Even the current Ventoy does not know, how to boot correctly particular MX 23 version. (yes, it is indeed different from MX 21 in this regard).
So, if you want to boot MX 23 with Ventoy, you must:
1. Login to github to your github account, to make visible download of special files to you. (If you do not have account there, you can make it for free)
2. Locate file, download it.
3. Apply it to your existing Ventoy USB. It must be *current* *latest* version, 1.0.91.
The exact procedure is described in the post mentioned by others.

Regards,
Andy

User avatar
keos
Posts: 1394
Joined: Sat Mar 04, 2017 12:00 pm

Re: MX-23 beta 2 feedback thread

#233 Post by keos »

Thanks.
Acer Aspire A315-58
Intel Core i7-1165G7
Iris Xe Graphics
MX-23.2-Xfce4 - 4.18.2

*Matthew 5:11

User avatar
mklym
Posts: 111
Joined: Fri May 03, 2019 11:54 am

Re: MX-23 beta 2 feedback thread

#234 Post by mklym »

I am not sure if this should go in this thread or not. If not, please move to proper section. Thanks.

Code: Select all

System:    Kernel: 5.16.0-5mx-amd64 [5.16.14-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.16.0-5mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower April 9  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Matsushita product: CF-30FCS85AM v: 002 serial: <filter> 
           Mobo: Matsushita model: CF30-2 v: 001 serial: <filter> BIOS: Phoenix v: 2.00L14 
           date: 05/23/2008 
CPU:       Info: Dual Core model: Intel Core2 Duo L7500 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: B (11) microcode: BA cache: L2: 4 MiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6384 
           Speed: 1481 MHz min/max: 800/1601 MHz boost: enabled Core speeds (MHz): 1: 1481 2: 1069 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Matsushita driver: i915 
           v: kernel bus-ID: 00:02.0 chip-ID: 8086:2a02 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: loaded: intel 
           display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 339x271mm (13.3x10.7") 
           s-diag: 434mm (17.1") 
           Monitor-1: VGA1 res: 1280x1024 hz: 60 dpi: 96 size: 338x270mm (13.3x10.6") 
           diag: 433mm (17") 
           OpenGL: renderer: Mesa Intel 965GM (CL) v: 2.1 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: Intel 82801H HD Audio vendor: Matsushita driver: snd_hda_intel v: kernel 
           bus-ID: 00:1b.0 chip-ID: 8086:284b class-ID: 0403 
           Sound Server-1: ALSA v: k5.16.0-5mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network driver: iwl4965 
           v: in-tree: modules: wl port: 1100 bus-ID: 0b:00.0 chip-ID: 8086:4229 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Marvell 88E8055 PCI-E Gigabit Ethernet vendor: Matsushita driver: sky2 
           v: 1.30 port: 4000 bus-ID: 0d:00.0 chip-ID: 11ab:4363 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Alps UGTZ4 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-2:3 
           chip-ID: 044e:3001 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: 
           hardware: no software: no address: <filter> 
           Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park 
           link-mode: slave accept 
Drives:    Local Storage: total: 232.89 GiB used: 144.74 GiB (62.1%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB 
           block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s type: SSD serial: <filter> 
           rev: 2B6Q scheme: MBR 
Partition: ID-1: / raw-size: 228.13 GiB size: 223.49 GiB (97.97%) used: 144.74 GiB (64.8%) 
           fs: ext4 dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 4.75 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda2 maj-min: 8:2 
Sensors:   System Temperatures: cpu: 50.0 C mobo: 46.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2012 lib: 977 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/charm.list 
           1: deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.it.ubc.ca/mxlinux/mx/repo/ bullseye main non-free
           2: deb http://mirror.it.ubc.ca/mxlinux/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/softmaker.list 
           1: deb [signed-by=/etc/apt/keyrings/softmaker.gpg] https://shop.softmaker.com/repo/apt stable non-free
Info:      Processes: 200 Uptime: 26m wakeups: 2 Memory: 3.83 GiB used: 1.76 GiB (46.0%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)
I am trying to upgrade from 21.3 to MX23. I am following the instructions found here:
https://mxlinux.org/wiki/system/upgradi ... nstalling/

All is good until I run the following command as root in terminal:

Code: Select all

$ find /etc/apt -name “*.list” -exec sudo sed -i ‘s/bullseye/bookworm/g’ {} +
This is the error I get:

Code: Select all

$ grep -qF ‘non-free-firmware’ /etc/apt/sources.list.d/debian.list || sudo sed -i ‘s/non-free/non-free non-free-firmware/g’ /etc/apt/sources.list.d/debian.list
sed: -e expression #1, char 1: unknown command: `�'
The next step is to run

Code: Select all

sudo apt update; sudo apt full-upgrade
This is the result:

Code: Select all

$ sudo apt update; sudo apt full-upgrade
Hit:1 http://deb.debian.org/debian bullseye-updates InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease                                              
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease                       
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease                                      
Get:5 https://repo.charm.sh/apt * InRelease                                                        
Hit:6 https://shop.softmaker.com/repo/apt stable InRelease                                         
Hit:7 http://mirror.it.ubc.ca/mxlinux/mx/repo bullseye InRelease
Fetched 6,615 B in 5s (1,221 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
How do I get rid of the sed error so I can finish the upgrade?

Looking forward to the final release of MX23. I have three units to deploy and a half dozen personal units to upgrade.
Thanks to all involved for all the work on MX.
CF-29LTQ, CF-30FCS, CF-31SBM, CF-52GUN, CF-53AAG, HP Z420

Life's Journey is not to arrive safely at the grave in a well preserved body, but rather to skid in sideways totally worn-out shouting 'Woo Hoo! What a ride!'

User avatar
fehlix
Developer
Posts: 12625
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-23 beta 2 feedback thread

#235 Post by fehlix »

mklym wrote: Thu Jun 22, 2023 4:17 pm I am trying to upgrade from 21.3 to MX23. I am following the instructions found here:
https://mxlinux.org/wiki/system/upgradi ... nstalling/

All is good until I run the following command as root in terminal:

Code: Select all

$ find /etc/apt -name “*.list” -exec sudo sed -i ‘s/bullseye/bookworm/g’ {} +
This is the error I get:

Code: Select all

$ grep -qF ‘non-free-firmware’ /etc/apt/sources.list.d/debian.list || sudo sed -i ‘s/non-free/non-free non-free-firmware/g’ /etc/apt/sources.list.d/debian.list
sed: -e expression #1, char 1: unknown command: `�'
On the web-page, the single quotes and double-quotes are displayed wrongly (or better have been
replaced by the used web-software.
And if you just copy paste the command those quotings chars will result in such an error,
b/c they have been replaced wrongly by the web-site rendering software (I think wordpress )

So you need edit first the copied command and replace all single quotes and double quotes properly:
e.g. this commnad is wrong:

Code: Select all

find /etc/apt -name “*.list” -exec sudo sed -i ‘s/bullseye/bookworm/g’ {} +
replace all and with normal double quotes "
and all singel quotes and with normal single quotes '
so it looks like this:

Code: Select all

find /etc/apt -name "*.list" -exec sudo sed -i 's/bullseye/bookworm/g' {} +
the same for the other command.
wrong:

Code: Select all

grep -qF ‘non-free-firmware’ /etc/apt/sources.list.d/debian.list || sudo sed -i ‘s/non-free/non-free non-free-firmware/g’ /etc/apt/sources.list.d/debian.list
corrected:

Code: Select all

grep -qF 'non-free-firmware' /etc/apt/sources.list.d/debian.list || sudo sed -i 's/non-free/non-free non-free-firmware/g' /etc/apt/sources.list.d/debian.list
@Adrian suggest to use codebox for these commands to avoid those quot-char issue.
Maybe @peregrine could help to add those codeboxes,
on this page https://mxlinux.org/wiki/system/upgradi ... nstalling/
something similare was done on the Signature verifcation web-page
https://mxlinux.org/wiki/system/signed-iso-files/,
where codeboxes have been added by @peregrine

User avatar
mklym
Posts: 111
Joined: Fri May 03, 2019 11:54 am

Re: MX-23 beta 2 feedback thread

#236 Post by mklym »

Well, I can not see any difference on my screen between the lines I posted and the lines you posted, but I did copy/paste your lines into the terminal and it is in the process of downloading and installing 1700+ updates. :D I will post back with results when it finishes. Thank you fehlix.
CF-29LTQ, CF-30FCS, CF-31SBM, CF-52GUN, CF-53AAG, HP Z420

Life's Journey is not to arrive safely at the grave in a well preserved body, but rather to skid in sideways totally worn-out shouting 'Woo Hoo! What a ride!'

User avatar
fehlix
Developer
Posts: 12625
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-23 beta 2 feedback thread

#237 Post by fehlix »

mklym wrote: Thu Jun 22, 2023 4:53 pm Well, I can not see any difference on my screen between the lines I posted and the lines you posted, but I did copy/paste your lines into the terminal and it is in the process of downloading and installing 1700+ updates. :D I will post back with results when it finishes. Thank you fehlix.
I made the quoting chars above a bit bigger, so you see the difference.
that those quote chars are different:
Double: and "
Singel: and '
And yes it's not easily to see on the commnad line, but you got error b/c those are different chars not allowed for
quoting on bash command line.

User avatar
mklym
Posts: 111
Joined: Fri May 03, 2019 11:54 am

Re: MX-23 beta 2 feedback thread

#238 Post by mklym »

Okay, now I see the difference. It makes sense to me now. The upgrade has started unpacking the files.
CF-29LTQ, CF-30FCS, CF-31SBM, CF-52GUN, CF-53AAG, HP Z420

Life's Journey is not to arrive safely at the grave in a well preserved body, but rather to skid in sideways totally worn-out shouting 'Woo Hoo! What a ride!'

User avatar
gRegNfo
Posts: 35
Joined: Sat Jun 10, 2023 6:30 am

Re: MX-23 beta 2 feedback thread

#239 Post by gRegNfo »

APT
apt-notifier

I have a problem with apt notifier (MX Updater), it's broken and I can't realize if I messed up or not.

Code: Select all

$ apt-notifier

$ Gtk-Message: 22:04:00.608: Failed to load module "gail"

** (python3:3609): WARNING **: 22:04:00.615: (../atk-adaptor/bridge.c:1105):atk_bridge_adaptor_init: runtime check failed: (root)
I reinstalled python3 and dependencies, atk, apt, that I found in the repo and I can't figure it out.
Updates still work on synaptic ... but somehow I think I've broken something maybe not a bug.
ASUS Laptop N56VB 1080p
i7-3630QM 2.40GHz Ivy Bridge
16GB DDR3 1600 MHz
2TB HW/SSD RAID-0 SATA3
Intel HD4000 IVB GT2
NVIDIA GK107M GeForce GT-740M 2GB VRAM
Intel Centrino WiFi-N 2230
Qualcomm Atheros AR8161 Gigabit
Intel 7 C210/C216/HM76 Express Chipset

User avatar
fehlix
Developer
Posts: 12625
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-23 beta 2 feedback thread

#240 Post by fehlix »

gRegNfo wrote: Thu Jun 22, 2023 5:16 pm APT
apt-notifier

I have a problem with apt notifier (MX Updater), it's broken and I can't realize if I messed up or not.

Code: Select all

$ apt-notifier

$ Gtk-Message: 22:04:00.608: Failed to load module "gail"

** (python3:3609): WARNING **: 22:04:00.615: (../atk-adaptor/bridge.c:1105):atk_bridge_adaptor_init: runtime check failed: (root)
I reinstalled python3 and dependencies, atk, apt, that I found in the repo and I can't figure it out.
Updates still work on synaptic ... but somehow I think I've broken something maybe not a bug.
Not sure what the indication might be that apt-notifier is broken. Does it not work anymore?
The message you got, is based on a missing module used by accessibility library:
Would

Code: Select all

sudo apt install libgail-common
help?

Locked

Return to “General”