Page 1 of 1
MX-23 beta 2 feedback thread
Posted: Thu Jun 15, 2023 8:03 pm
by dolphin_oracle
This thread is for feedback and issue reports MX-23 beta 2, any flavor.
Be sure to include the quick-system-info with your report.
If posting nvidia-installer (ddm-mx) issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
By the way, the gui for quick-system-info now has a pretty nice log viewer function.
if posting about an application, please be specific on what application.
Original blog post here
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 15, 2023 9:27 pm
by entropyfoe
Posting from the beta2 right now. Downloaded, md5 is good, burn to 4 GIg stick using MX live creator under the beta1, and boots fine.
Posting from here. I will check the sound, and then hit install to my testing partion, grub to root.
Sound card selected with the MX Tools- sound card selector, it works...hit install.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 15, 2023 10:58 pm
by pbear
FYI, there's a typo in the blog link for download of the XFCE 64-bit iso. Says beta1 rather than beta2, generating an error at SourceForge. Can manually click through to the correct file name, but some users might not think to do that. By the way, you might add to Known Issues that the ISO won't at present boot from Ventoy, a problem hopefully to be fixed by future Ventoy update.
Edit: Ventoy has now been updated. The current version (1.0.93) boots the MX-23 beta2 without difficulty. Also still works with older versions (I tested 21.2.1, which was the ISO I had handy).
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 15, 2023 11:24 pm
by dolphin_oracle
pbear wrote: Thu Jun 15, 2023 10:58 pm
FYI, there's a typo in the blog link for download of the XFCE 64-bit iso. Says beta1 rather than beta2, generating an error at SourceForge. Can manually click through to the correct file name, but some users might not think to do that. By the way, you might add to Known Issues that the ISO won't at present boot from Ventoy, a problem hopefully to be fixed by future Ventoy update.
got it thanks
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 2:27 am
by peter_li
Congratulations to the MX Team for this BETA2. I have seen it at first available at Sourceforge, than the announcement on Distrowatch but still miss it when I read the News on
https://mxlinux.org/mx-linux-blog/ . Just installed and now writing on it. I dont found a torrent for the Xfce4 or the others, right?
So far it runs good. First time a non Arch Distro detected my Arch based Distro Installations correct so that they should be ready to boot with their multiple entrys in the initrd line:
Code: Select all
initrd /boot/intel-ucode.img /boot/initramfs-linux.img
. But what it does not correct detected: my SWAP partition, so I now have only the swapfile which I created during installation, my other Linux installations like Garuda Linux(also Arch based)(maybe cause it is on BTRFS) and openSUSE (they seem to have their special BTRFS partition layout).
Does somebody knew why grub.cfg sometimes states root=UUID... and sometimes root=/dev/sdbXX? There are cases where my internal sda is not shown and then sdb becomes to sda and the boot stops in a dash shell.
Is btrfs fully supported on MX Linux 23?
Will it be okay for small machines like mine to use Firefox or better use Brave or what would you suggest?
I would like to offer torrent download of MX-23 Linux from my small system, have only to check which ports to open or so. Any suggestions?
You want it, so you get it:
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Dell product: Latitude E6510 v: 0001 serial: <superuser required> Chassis:
type: 9 serial: <superuser required>
Mobo: Dell model: 02K3Y4 v: A01 serial: <superuser required> UEFI: Dell v: A17 date: 05/12/2017
Battery:
ID-1: BAT0 charge: 39.5 Wh (100.0%) condition: 39.5/62.2 Wh (63.6%) volts: 12.7 min: 11.1
model: Samsung SDI DELL H139109 type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Core i5 M 560 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 5 microcode: 0x7
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1434 high: 1463 min/max: 1199/2667 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1451 2: 1463 3: 1360 4: 1463 bogomips: 21280
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: eDP-1 empty: DP-1, DP-2, DP-3,
HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: intel
dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 mapped: eDP1 model: LG Display 0x024b built: 2010 res: 1366x768 hz: 60
dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell Latitude E6510
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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 82577LM Gigabit Network vendor: Dell Latitude E6510 driver: e1000e v: kernel
port: 7040 bus-ID: 00:19.0 chip-ID: 8086:10ea class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Broadcom BCM43224 802.11a/b/g/n vendor: Dell Wireless 1520 Half-size Mini PCIe Card
driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
chip-ID: 14e4:4353 class-ID: 0280
IF: wlan0 state: dormant mac: <filter>
Device-3: ZyXEL Dual-Band Wireless AC USB Adapter type: USB driver: rtl8812au bus-ID: 2-1.2:4
chip-ID: 0586:3426 class-ID: 0000 serial: <filter>
IF: wlan1 state: dormant mac: <filter>
Device-4: Dell F3607gw v2 Mobile Broadband Module type: USB driver: cdc_acm,cdc_ether,cdc_wdm
bus-ID: 2-1.6:6 chip-ID: 413c:8184 class-ID: 0202 serial: <filter>
IF: wwan0 state: down mac: <filter>
Bluetooth:
Device-1: Dell DW375 Bluetooth Module type: USB driver: btusb v: 0.8 bus-ID: 2-1.7:7
chip-ID: 413c:8187 class-ID: fe01 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 4 state: up address: <filter> bt-v: 2.0 lmp-v: 3.0
sub-v: 4203 hci-v: 3.0 rev: 205
Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 1.06 TiB used: 9.22 GiB (0.9%)
ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
SMART Message: Unable to run smartctl. Root privileges required.
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST9160314AS size: 149.05 GiB block-size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: DEM1
scheme: GPT
Partition:
ID-1: / raw-size: 48.83 GiB size: 47.76 GiB (97.81%) used: 9.17 GiB (19.2%) fs: ext4
dev: /dev/sda14 maj-min: 8:14
ID-2: /boot/efi raw-size: 315 MiB size: 196.9 MiB (62.50%) used: 59 MiB (30.0%) fs: vfat
dev: /dev/sdb4 maj-min: 8:20
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A sodimm: SODIMM C
Fan Speeds (RPM): cpu: 0
Repos:
Packages: pm: dpkg pkgs: 2066 libs: 1043 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/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://mirror.netzwerge.de/debian bookworm-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://mirror.netzwerge.de/debian bookworm main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 238 Uptime: 24m wakeups: 2 Memory: 3.69 GiB used: 1.69 GiB (45.7%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 3:32 am
by ceeslans
downloaded MX-Fluxbox-amd64 iso and installed it to a usb3
first impression: this beta2 is smooth and fast running. desktop is setting quickly, no traces of delays from sleeping/delayed startup items. very responsive to mouseclicks and keybinds.
Here are some initial findings
xsession-errors
---------
~/xsession-errors file keeps showing a number of errors/warnings, mostly related to pipewire (rtkit, libcamera etc) as well as xfce4-clipman issues.
No fluxbox errors were recorded in xsession-errors, nor logged to ~/.fluxbox/log.
Fluxbox only shows (harmless) warning about not being able to open fluxbox.cat: [Warning: Failed to open file (fluxbox.cat). For translation, using default messages.]
If you see that message, you can resolve it by executing following commands:
Code: Select all
cd /usr/share/fluxbox/nls
sudo ln -is en_US.UTF-8 $(locale | grep LANG | cut -d= -f2)
Also showing continuous 'Helpers.IconFetcher-WARNING' messages, about missing paths to 'font.png' and 'background.svg' icons. To solve this, suggest to edit following *.desktop files in /usr/share/applications:
Code: Select all
- mxfb-font.desktop : Icon=org.gnome.fontmanager
- mxfb-backgrounds.desktop : Icon=preferences-desktop-wallpaper
Icons will then display correctly in rofi/appfinder --> and warning messages are gone.
mxfb-font
---------
gtk 'subpixel' value is not written/saved to ~/.gtk-2.0 and ~/.config/gtk-3.0/settings.ini.
apparently the "gtk-xft-rgba= " line is failing in both files.
after manually adding the line in both files, then the chosen value is correctly written.
more to follow as it comes along.
QSI:
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: 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: Laptop System: Sony product: VPCF23P1E v: C609XFKA serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: Sony model: VAIO serial: <superuser required> BIOS: American Megatrends v: R2150V3
date: 07/22/2011
Battery:
ID-1: BAT0 charge: 38.9 Wh (100.0%) condition: 38.9/57.2 Wh (67.9%) volts: N/A min: 123.5
model: Sony Corp. type: Li-ion serial: N/A status: full
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M315/M235 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Core i7-2670QM bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled 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: 1260 high: 1985 min/max: 800/3100 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 798 2: 1455 3: 1450 4: 880 5: 902 6: 957 7: 1985 8: 1657
bogomips: 35120
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GF108M [GeForce GT 540M] vendor: Sony driver: nouveau v: kernel non-free:
series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm
built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: LVDS-1 empty: HDMI-A-1,VGA-1
bus-ID: 01:00.0 chip-ID: 10de:0df4 class-ID: 0300 temp: 49.0 C
Device-2: Ricoh USB2.0 Camera type: USB driver: uvcvideo bus-ID: 3-1.2:3 chip-ID: 05ca:18c0
class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: LVDS-1 model: Chi Mei Opto 0x1600 built: 2011 res: 1920x1080 hz: 60 dpi: 130
gamma: 1.2 size: 374x192mm (14.72x7.56") diag: 420mm (16.6") modes: max: 1920x1080 min: 640x350
API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NVC1 direct-render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Sony 6
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
Device-2: NVIDIA GF108 High Definition Audio vendor: Sony driver: snd_hda_intel v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0bea 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: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Foxconn Unex DHXA-225
driver: ath9k v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
chip-ID: 168c:0032 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Sony driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 9000 bus-ID: 05:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 252.42 GiB used: 5.66 GiB (2.2%)
ID-1: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: Ultra size: 14.32 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
SMART Message: Unable to run smartctl. Root privileges required.
ID-2: /dev/sdb maj-min: 8:16 vendor: Kingfast model: N/A size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Ultra size: 14.53 GiB block-size:
physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 10 GiB size: 9.75 GiB (97.45%) used: 5.53 GiB (56.8%) fs: ext4 dev: /dev/sda1
maj-min: 8:1
ID-2: /home raw-size: 3.32 GiB size: 3.19 GiB (96.20%) used: 125.7 MiB (3.8%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 1024 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
maj-min: 8:3
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A gpu: nouveau temp: 49.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 1804 libs: 883 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://nl.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 237 Uptime: 34m wakeups: 76 Memory: 5.77 GiB used: 1.34 GiB (23.2%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 3:42 am
by chrispop99
peter_li wrote: Fri Jun 16, 2023 2:27 am
I dont found a torrent for the Xfce4 or the others, right?
Torrents are only provided for Final versions.
Chris
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 3:47 am
by operadude
Quick (dumb?) Question about Installing:
I had previously installed Beta-1 on an old, legacy machine using Root, Home & Swap on 3 different partitions (with one "Logical" Partition). I want to wipe those partitions and re-install Beta-2.
However, since by default Beta-2 uses a Swapfile, can I install Beta-2 on just 1 partition on that old machine? With /Root/Home, and the Swapfile, on just 1 partition?
My question is: where does that Swapfile reside? I'm assuming it's NOT on a separate partition, right? Does it go in /Root/Home (automatically)?
I want to correctly set-up the partitions on that old (MBR) machine, and minimize the number of partitions (max=4). I know I can do as before, but I'd like to use the minimum number of partitions possible!
Can I get-away with installing Beta-2 on only 1 partition?
(And, I cannot do a "Whole Disk" install-- other stuff on that drive already)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 5:13 am
by Melber
ceeslans wrote: Fri Jun 16, 2023 3:32 am
mxfb-font
gtk 'subpixel' value is not written/saved to ~/.gtk-2.0 and ~/.config/gtk-3.0/settings.ini.
apparently the "gtk-xft-rgba= " line is failing in both files.
after manually adding the line in both files, then the chosen value is correctly written.
The subpixel selection option was removed for exactly this reason.
Seems like the mxfb-accessories package is yet to be updated with the latest version of mxfb-font.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 5:39 am
by i_ri
hello dolphin_oracle
mxfluxbox
XDG_ is empty.
Code: Select all
demo@mx1:~
$ echo $XDG_DESKTOP_DIR
demo@mx1:~
$ echo $(xdg-user-dir DESKTOP)
/home/demo/Desktop
demo@mx1:~
$
Code: Select all
Distro: MX-23_fluxbox_beta2_x64 Libretto June 15 2023
Desktop: Fluxbox v: 1.3.7
Host: mx1 Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64
CPU: dual core Intel Core i3 530 (-MT MCP-) speed/min/max: 1290/1200/2933 MHz
Up: 1d 6h 9m
Mem: 1804.3/7803.7 MiB (23.1%)
Procs: 202 Shell: Bash inxi: 3.3.26
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 5:52 am
by Jerry3904
Seems like the mxfb-accessories package is yet to be updated with the latest version of mxfb-font.
It sseems to have gotten stuck in the pipeline. The changelog shows that change was set to be packaged:
Code: Select all
mxfb-accessories (23.06.07) mx; urgency=medium
* Non-maintainer upload.
* Changed yad infotext to italics
* Removed "Sub-pixels" combobox
-- Jerry <jb@mx> Wed, 07 Jun 2023 20:55:51 -0400
I will push the latest change and we'll get it packaged. Sorry about that oversight.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:09 am
by Buck Fankers
I too am looking forward to see the answer.
operadude wrote: Fri Jun 16, 2023 3:47 am
My question is: where does that Swapfile reside? I'm assuming it's NOT on a separate partition, right? Does it go in /Root/Home (automatically)?
Quick follow up question and sorry for questions, since this is not feedback, but helps understanding the changes.
Is default swap file introduced for simplicity reasons, to be of help for us noobs
or is swap file now generally preferred way of setting up Linux system?
I'm asking this, since few years ago I learned, that at that time swap file was 'dirty', hacky way and not preferred way of setting up the system. Things changed since then, I'm sure, but can't hurt asking.
(edit, thanks moderator for help)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:38 am
by fehlix
pbear wrote: Thu Jun 15, 2023 10:58 pm
FYI, there's a typo in the blog link for download of the XFCE 64-bit iso. Says beta1 rather than beta2, generating an error at SourceForge. Can manually click through to the correct file name, but some users might not think to do that. By the way, you might add to Known Issues that the ISO won't at present boot from Ventoy, a problem hopefully to be fixed by future Ventoy update.
User can get latest pre-release Ventoy builds from
https://github.com/ventoy/Ventoy/actions,
which do work since MX related adjustments have been applied.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:47 am
by ceeslans
Jerry3904 wrote: Fri Jun 16, 2023 5:52 am
Seems like the mxfb-accessories package is yet to be updated with the latest version of mxfb-font.
>snip<
I will push the latest change and we'll get it packaged. Sorry about that oversight.
Great! Enough time for me then to duplicate this mxfb-font version and save it for later. I like its ability to set a sub-pixel order.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:56 am
by fehlix
peter_li wrote: Fri Jun 16, 2023 2:27 am
Does somebody knew why grub.cfg sometimes states root=UUID... and sometimes root=/dev/sdbXX? There are cases where my internal sda is not shown and then sdb becomes to sda and the boot stops in a dash shell.
update-grub generates grub menu entries in two flavours: If it detects a grub-installation on the other OS it uses information found within the grub.cfg file on the other OS. If there is no grub installed on the other OS, it would create generic menu entries with root=/dev/name entries. So you better always install GRUB, to get proper root=UUID=xxxx boot parameter.
peter_li wrote: Fri Jun 16, 2023 2:27 am
Is btrfs fully supported on MX Linux 23?
So fas as I see yes, including timeshift on btrfs.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:16 am
by ceeslans
There's a 'Application Finder' entry in the rightclick applications menu, as well as in rofi, which invokes 'xfce4-appfinder-mxfb.desktop' exec command.
But the actual xfce4-appfinder command isn't executed, since this application is not installed. Either point this .desktop file to rofi/appfinder - or remove it altogether?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:38 am
by jstdk
Thanks to everyone involved in building this great distro. I have been testing Libretto XFCE since beta 1, hereby my issues encountered.
Hardware:
Asus Vivobook Oled 3k 12th gen Intel
24 Ghz Ram
- Scaling issues. It happens frequently that I need to rescale on boot (Display->Scaling->0.5). The system sometimes (not always) forgets my settings during reboots/wakepups.
- Crashes when connecting to an external screen (HDMI). First the option is shown how to use the external screen (mirror, extension, etc). After choosing, the computer reboots
- MX Linux animation on startup and shutdown is extremely slow, it takes almost a minute to run (this was smooth in a VM, not sure why not on metal)
- The notification 'Do not show this message again', for example when a network is found, is ignored. The message keeps on showing up. I had to put the machine in Do not disturb mode
- Telegram Desktop Flatpak cannot be installed using the software installer (Error pulling from repo: GPG verification enabled, but no signatures found)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:40 am
by Jerry3904
Which version?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:44 am
by jstdk
Jerry3904 wrote: Fri Jun 16, 2023 7:40 am
Which version?
Beta 2 XFCE (updated my post)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 8:02 am
by Senpai
Hi:
Checking mx-tweak - Fluxbox tab, I see that the strings "108: Reset DefaultDock" and "116: Reset Fluxbox Menu", do not have space for translations.... Is it possible to increase the space for the text?
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 9:19 am
by peter_li
peter_li wrote: Fri Jun 16, 2023 2:27 am
But what it does not correct detected: my SWAP partition, so I now have only the swapfile which I created during installation,
I found out now:
Code: Select all
sudo blkid
...
/dev/sdb6: UUID="3c53b71b-9495-4e33-a35a-c634602cd40b" TYPE="swap" PARTUUID="ee946357-d891-4c07-b86e-4bc74850a1af"
This was not added to my /etc/fstab as I expected during the installation:
Code: Select all
# Pluggable devices are handled by uDev, they are not in fstab
UUID=93ec028b-5eac-4c2a-9429-3c0b8df5435f / ext4 noatime 1 1
UUID=7366-5199 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0
/swapfile swap swap defaults 0 0
So I added it now by hand:
Code: Select all
# Dedicated swap partition
UUID=3c53b71b-9495-4e33-a35a-c634602cd40b none swap defaults 0 0
which results to this:
Code: Select all
$ sudo swapon -a -v
swapon: /dev/sdb6: Signatur gefunden [Seitengröße=4096, Signatur=swap]
swapon: /dev/sdb6: Seitengröße=4096, Swapgröße=8469348352, Gerätegröße=8469348352
swapon /dev/sdb6
swapon: /swapfile: bereits aktiv -- wird ignoriert
$ swapon -s -v
Dateiname Typ Größe Benutzt Priorität
/swapfile file 2097148 0 -2
/dev/sdb6 partition 8270844 0 -3
which works now. But the system names it sdb where I think it should be sda.
Maybe this
page in the MX Wiki could be improved(cause mostly empty)?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 9:57 am
by Eadwine Rose
Glad to report that the nvidia driver installs fine on the machine here and things seem to be working ok. Currently in 21 but I wager no info is needed, as it is working. :)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:04 am
by andy
Hello
@dolphin_oracle,
Installer failed Phase 3 - Grub installation failed.
Installing on BTRFS with encryption, alongside Windows (EFI partition preserved, formerly there was MX23 alpha, on EXT4 w/o encr.).
Created BRTFS subvolumes @, @home in installer.
minstall.log attached.
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=/antiX/vmlinuz quiet splasht nosplash
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
serial: <superuser required> Chassis: type: 4 serial: <superuser required>
Mobo: Hewlett-Packard model: 339A serial: <superuser required> UEFI: Hewlett-Packard
v: K01 v03.08 date: 04/10/2019
CPU:
Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1845 high: 1885 min/max: 1600/3300 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1868 2: 1885 3: 1863 4: 1767 bogomips: 26338
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 model: Dell E2420H serial: <filter> built: 2020 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.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2500 (IVB GT1)
direct-render: Yes
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 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 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: ASUSTek UT220 Pro wireless/WT300 type: USB driver: hid-generic,usbhid bus-ID: 1-1.4:4
chip-ID: 0b05:185f class-ID: 0301
Drives:
Local Storage: total: 585.05 GiB used: 13.3 GiB (2.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2CW120A3 size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 400i scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB model: General size: 7.5 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 5.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 28.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 224 Uptime: 34m wakeups: 6 Memory: 7.63 GiB used: 2.99 GiB (39.1%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:05 am
by dolphin_oracle
peter_li wrote: Fri Jun 16, 2023 9:19 am
peter_li wrote: Fri Jun 16, 2023 2:27 am
But what it does not correct detected: my SWAP partition, so I now have only the swapfile which I created during installation,
I found out now:
Code: Select all
sudo blkid
...
/dev/sdb6: UUID="3c53b71b-9495-4e33-a35a-c634602cd40b" TYPE="swap" PARTUUID="ee946357-d891-4c07-b86e-4bc74850a1af"
This was not added to my /etc/fstab as I expected during the installation:
Code: Select all
# Pluggable devices are handled by uDev, they are not in fstab
UUID=93ec028b-5eac-4c2a-9429-3c0b8df5435f / ext4 noatime 1 1
UUID=7366-5199 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0
/swapfile swap swap defaults 0 0
So I added it now by hand:
Code: Select all
# Dedicated swap partition
UUID=3c53b71b-9495-4e33-a35a-c634602cd40b none swap defaults 0 0
which results to this:
Code: Select all
$ sudo swapon -a -v
swapon: /dev/sdb6: Signatur gefunden [Seitengröße=4096, Signatur=swap]
swapon: /dev/sdb6: Seitengröße=4096, Swapgröße=8469348352, Gerätegröße=8469348352
swapon /dev/sdb6
swapon: /swapfile: bereits aktiv -- wird ignoriert
$ swapon -s -v
Dateiname Typ Größe Benutzt Priorität
/swapfile file 2097148 0 -2
/dev/sdb6 partition 8270844 0 -3
which works now. But the system names it sdb where I think it should be sda.
Maybe this
page in the MX Wiki could be improved(cause mostly empty)?
so if I understand correctly you specified both a swap partition an a swapfile during installation, but only the swapfile was created/used?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:08 am
by dolphin_oracle
andy wrote: Fri Jun 16, 2023 10:04 am
Hello @dolphin_oracle,
Installer failed Phase 3 - Grub installation failed.
Installing on BTRFS with encryption, alongside Windows (EFI partition preserved, formerly there was MX23 alpha, on EXT4 w/o encr.).
Created BRTFS subvolumes @, @home in installer.
minstall.log attached.
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=/antiX/vmlinuz quiet splasht nosplash
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
serial: <superuser required> Chassis: type: 4 serial: <superuser required>
Mobo: Hewlett-Packard model: 339A serial: <superuser required> UEFI: Hewlett-Packard
v: K01 v03.08 date: 04/10/2019
CPU:
Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1845 high: 1885 min/max: 1600/3300 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1868 2: 1885 3: 1863 4: 1767 bogomips: 26338
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 model: Dell E2420H serial: <filter> built: 2020 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.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2500 (IVB GT1)
direct-render: Yes
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 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 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: ASUSTek UT220 Pro wireless/WT300 type: USB driver: hid-generic,usbhid bus-ID: 1-1.4:4
chip-ID: 0b05:185f class-ID: 0301
Drives:
Local Storage: total: 585.05 GiB used: 13.3 GiB (2.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2CW120A3 size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 400i scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB model: General size: 7.5 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 5.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 28.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 224 Uptime: 34m wakeups: 6 Memory: 7.63 GiB used: 2.99 GiB (39.1%) 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: UEFI
thank you for the log. gold star!
looks like we may need to set another parameter, one we haven't needed to before:
Code: Select all
G default: Exec #164: chroot /mnt/antiX grub-install --force-extra-removable --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=MX23 --recheck
2023-06-16 15:44:24.510 DBG default: SErr #164: "Installing for x86_64-efi platform.\ngrub-install: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file `/etc/default/grub'.\n"
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:17 am
by andy
I have repeated the installation process just with the change of filesystem to EXT4, encrypted, and Home on the root partition. All went well. I can attach the log, if needed, too. (Writing from another machine)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:30 am
by andy
One idea:
@dolphin_oracle,
may I ask for input box in installer on encryption page, where I can input parameters to override encryption? Like encryption algo, keysize, hash algo, etc...
It would be nice if it shows actual encryption parameters (commandline args), and initially disabled, to not allow users to mess with it. Beside it the checkbox "allow finetuning of encryption. Only for advanced users.", which will enable the inputbox, making it editable.
It would be awesome to have it like that. I am sure there will be users grateful for that. Not everybody uses AES, and/or SHA512.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:38 am
by pbear
Thanks. Will give that a try this evening (morning here, at the moment).
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:40 am
by dolphin_oracle
andy wrote: Fri Jun 16, 2023 10:30 am
One idea:
@dolphin_oracle,
may I ask for input box in installer on encryption page, where I can input parameters to override encryption? Like encryption algo, keysize, hash algo, etc...
It would be nice if it shows actual encryption parameters (commandline args), and initially disabled, to not allow users to mess with it. Beside it the checkbox "allow finetuning of encryption. Only for advanced users.", which will enable the inputbox, making it editable.
It would be awesome to have it like that. I am sure there will be users grateful for that. Not everybody uses AES, and/or SHA512.
we used to have that, but in looking at a lot of log files, I don't think anyone actually used it, so it was removed. Probably not high on the list to add back, but we will keep it in mind.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:41 am
by dolphin_oracle
andy wrote: Fri Jun 16, 2023 10:17 am
I have repeated the installation process just with the change of filesystem to EXT4, encrypted, and Home on the root partition. All went well. I can attach the log, if needed, too. (Writing from another machine)
that would be great for comparison.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:43 am
by pbear
operadude wrote: Fri Jun 16, 2023 3:47 am
My question is: where does that Swapfile reside? I'm assuming it's NOT on a separate partition, right? Does it go in /Root/Home (automatically)?
A swapfile can go anywhere, but the default is / (root), i.e, not in any of the folders/directories. The corresponding entry in fstab is simply /swapfile (which, indeed, is the full path).
Buck Fankers wrote: Fri Jun 16, 2023 6:09 am
... is swap file now generally preferred way of setting up Linux system?
Swap file and swap partition both work fine. The former is more convenient on a single-install system, as it can be resized easily. The latter has the efficiency on a multi-boot system that it can be shared.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:51 am
by andy
dolphin_oracle wrote: Fri Jun 16, 2023 10:40 am
andy wrote: Fri Jun 16, 2023 10:30 am
One idea:
@dolphin_oracle,
may I ask for input box in installer on encryption page, where I can input parameters to override encryption? Like encryption algo, keysize, hash algo, etc...
It would be nice if it shows actual encryption parameters (commandline args), and initially disabled, to not allow users to mess with it. Beside it the checkbox "allow finetuning of encryption. Only for advanced users.", which will enable the inputbox, making it editable.
It would be awesome to have it like that. I am sure there will be users grateful for that. Not everybody uses AES, and/or SHA512.
we used to have that, but in looking at a lot of log files, I don't think anyone actually used it, so it was removed. Probably not high on the list to add back, but we will keep it in mind.
These who have used it, were able to help themselves often, so did not post logs so frequently like newbies
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:54 am
by andy
dolphin_oracle wrote: Fri Jun 16, 2023 10:41 am
andy wrote: Fri Jun 16, 2023 10:17 am
I have repeated the installation process just with the change of filesystem to EXT4, encrypted, and Home on the root partition. All went well. I can attach the log, if needed, too. (Writing from another machine)
that would be great for comparison.
Here you are.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:04 am
by i_ri
Hello Melber
Themes with Music-names like sharp, flat, tremolo ?
Into each of 39[one recolour] Style files i put slit.border, slit.bevel values; that does take seventeen minutes. That is with one break; i am an easy boss. No more need of overlay for slit.border here.
hello dolphin_oracle
This sample mx-idesktool
Includes pushing an equivalent i.desktop Launcher into Desktop directory.
idesk
ditto
Thunar
sample
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:06 am
by siamhie
MX-23 fluxbox-b2
Are we going back to apt for updates? When applying updates this morning apt showed and not nala.
Code: Select all
# Alternative apt/apt-get command line package manager
# use_nala = true
# Example section below will be ignored
#
[Example]
# comment out the section header line above to make it active
#
# Use of alternative classic_some- and clasic_none icons:
classic_none = $HOME/.local/share/icons/apt-notifier-tickok_32.png
classic_some = $HOME/.local/share/icons/apt-notifier-reload_32.png
#
# Use alternative apt/apt-get command line package manager
use_nala = true
Can I set the notifier/update window back to 80x24 in size?
QSI
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
amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
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 System: Micro-Star product: MS-7C56 v: 2.0 serial: <superuser required>
Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required> UEFI: American
Megatrends LLC. v: A.B0 date: 08/11/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 3800X 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: 0x8701021
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2199 high: 2298 min/max: 2200/4559 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 2200 2: 2200 3: 2200 4: 2199 5: 2200 6: 2101
7: 2199 8: 2199 9: 2200 10: 2200 11: 2200 12: 2199 13: 2200 14: 2200 15: 2298 16: 2200
bogomips: 124806
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 0b:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 mapped: DisplayPort-0 model: HP X27q serial: <filter> built: 2021
res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
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: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel modules: wl pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 8.19 TiB used: 878.4 GiB (10.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital model: WDS500G1X0E-00AFY0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 613000WD temp: 38.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 102000WD temp: 35.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 465.26 GiB size: 456.89 GiB (98.20%) used: 8.12 GiB (1.8%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 572 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 65 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme1n1p1
maj-min: 259:1
Sensors:
System Temperatures: cpu: 34.2 C mobo: N/A gpu: amdgpu temp: 42.0 C mem: 44.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 741
Repos:
Packages: pm: dpkg pkgs: 2022 libs: 1039 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/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bullseye main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Info:
Processes: 333 Uptime: 9m wakeups: 2 Memory: 31.27 GiB used: 2.31 GiB (7.4%) Init: systemd v: 252
target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:07 am
by operadude
pbear wrote: Fri Jun 16, 2023 10:43 am
operadude wrote: Fri Jun 16, 2023 3:47 am
My question is: where does that Swapfile reside? I'm assuming it's NOT on a separate partition, right? Does it go in /Root/Home (automatically)?
A swapfile can go anywhere, but the default is / (root), i.e, not in any of the folders/directories. The corresponding entry in fstab is simply /swapfile (which, indeed, is the full path).
Buck Fankers wrote: Fri Jun 16, 2023 6:09 am
... is swap file now generally preferred way of setting up Linux system?
Swap file and swap partition both work fine. The former is more convenient on a single-install system, as it can be resized easily. The latter has the efficiency on a multi-boot system that it can be shared.
Thank you!
Very Helpful Info!
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:07 am
by entropyfoe
OK, I continued with the set-up and tweaking from last night.
That 3-D new logo looks good during the boot, I like how the back and leading edges are subtly out of focus, giving a nice 3D look, like it is something BIG.
All is running smoothly on this hard drive install. No problems so far, solid as beta1 as I reported earlier. A wonderful beta -AGAIN !
My list of post install tweaks is complete except for the final firefox 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 ! [b]Still need fsearch and warpinator, but these will come when the release settles.
4. Run synaptic to get all updates[/b]
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
14. MX Tweak-enable compton compositing, and select MX comfort theme with thick boarders
15. set swappiness =1
16. Set terminal opacity to 99
All on this:
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_beta2_x64 Libretto June 15 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: 2198 high: 2200 min/max: 2200/4409 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 2196 2: 2196 3: 2200 4: 2200 5: 2200 6: 2200
7: 2192 8: 2196 9: 2200 10: 2200 11: 2200 12: 2196 bogomips: 91030
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
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.8 GiB (44.2%)
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.34 GiB (9.7%) fs: ext4
dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
Kernel: swappiness: 1 (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: 47.0 C mobo: 32.0 C gpu: nvidia temp: 49 C
Fan Speeds (RPM): cpu: 0 case-1: 0 case-2: 927 case-3: 859 gpu: nvidia fan: 50%
Power: 12v: 12.16 5v: N/A 3.3v: N/A vbat: N/A
Repos:
Packages: pm: dpkg pkgs: 2323 libs: 1241 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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 297 Uptime: 22m wakeups: 1 Memory: 31.26 GiB used: 2.08 GiB (6.6%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:09 am
by Jerry3904
@siamhie Yes back to apt for default: we've had too many reports of lengthy hangups.
I don't know about changing the window size but it would be nice: it swamps my 1366x768 testing screen.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:19 am
by peter_li
dolphin_oracle wrote: Fri Jun 16, 2023 10:05 am
so if I understand correctly you specified both a swap partition an a swapfile during installation, but only the swapfile was created/used?
yes, the swap partition was like the EFI were shown in the partition window so I don't touch them. The efi were used, the swap not.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:25 am
by siamhie
Jerry3904 wrote: Fri Jun 16, 2023 11:09 am
@siamhie Yes back to apt for default: we've had too many reports of lengthy hangups.
I don't know about changing the window size but it would be nice: it swamps my 1366x768 testing screen.
Thanks
@Jerry3904. If I want to switch back to nala I can always uncomment out this line
Code: Select all
# Alternative apt/apt-get command line package manager
# use_nala = true <-------this one
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:43 am
by asqwerth
peter_li wrote: Fri Jun 16, 2023 11:19 am
dolphin_oracle wrote: Fri Jun 16, 2023 10:05 am
so if I understand correctly you specified both a swap partition an a swapfile during installation, but only the swapfile was created/used?
yes, the swap partition was like the EFI were shown in the partition window so I don't touch them. The efi were used, the swap not.
Even if swap partition is shown in the installer "spreadsheet", I believe you still have to select it to "use as swap" and then in the "format" column, choose "preserve" (ie, not to format) it. Otherwise it won't be recorded as a partition you chose to use, and thus won't show up in fstab.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 11:59 am
by dolphin_oracle
andy wrote: Fri Jun 16, 2023 10:04 am
Hello @dolphin_oracle,
Installer failed Phase 3 - Grub installation failed.
Installing on BTRFS with encryption, alongside Windows (EFI partition preserved, formerly there was MX23 alpha, on EXT4 w/o encr.).
Created BRTFS subvolumes @, @home in installer.
minstall.log attached.
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=/antiX/vmlinuz quiet splasht nosplash
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
serial: <superuser required> Chassis: type: 4 serial: <superuser required>
Mobo: Hewlett-Packard model: 339A serial: <superuser required> UEFI: Hewlett-Packard
v: K01 v03.08 date: 04/10/2019
CPU:
Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1845 high: 1885 min/max: 1600/3300 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1868 2: 1885 3: 1863 4: 1767 bogomips: 26338
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 model: Dell E2420H serial: <filter> built: 2020 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.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2500 (IVB GT1)
direct-render: Yes
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 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 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: ASUSTek UT220 Pro wireless/WT300 type: USB driver: hid-generic,usbhid bus-ID: 1-1.4:4
chip-ID: 0b05:185f class-ID: 0301
Drives:
Local Storage: total: 585.05 GiB used: 13.3 GiB (2.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2CW120A3 size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 400i scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB model: General size: 7.5 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 5.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 28.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 224 Uptime: 34m wakeups: 6 Memory: 7.63 GiB used: 2.99 GiB (39.1%) 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: UEFI
did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 12:04 pm
by andy
dolphin_oracle wrote: Fri Jun 16, 2023 11:59 am
andy wrote: Fri Jun 16, 2023 10:04 am
Hello @dolphin_oracle,
Installer failed Phase 3 - Grub installation failed.
Installing on BTRFS with encryption, alongside Windows (EFI partition preserved, formerly there was MX23 alpha, on EXT4 w/o encr.).
Created BRTFS subvolumes @, @home in installer.
minstall.log attached.
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=/antiX/vmlinuz quiet splasht nosplash
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
serial: <superuser required> Chassis: type: 4 serial: <superuser required>
Mobo: Hewlett-Packard model: 339A serial: <superuser required> UEFI: Hewlett-Packard
v: K01 v03.08 date: 04/10/2019
CPU:
Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1845 high: 1885 min/max: 1600/3300 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1868 2: 1885 3: 1863 4: 1767 bogomips: 26338
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 model: Dell E2420H serial: <filter> built: 2020 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.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2500 (IVB GT1)
direct-render: Yes
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 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 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: ASUSTek UT220 Pro wireless/WT300 type: USB driver: hid-generic,usbhid bus-ID: 1-1.4:4
chip-ID: 0b05:185f class-ID: 0301
Drives:
Local Storage: total: 585.05 GiB used: 13.3 GiB (2.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2CW120A3 size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 400i scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB model: General size: 7.5 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 5.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 28.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 224 Uptime: 34m wakeups: 6 Memory: 7.63 GiB used: 2.99 GiB (39.1%) 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: UEFI
did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.
In fact, now I am not sure about it. I was trying many things.
I will reinstall once more, albeit on a different machine. Will let you know in a while.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 12:29 pm
by peter_li
fehlix wrote: Fri Jun 16, 2023 6:56 am
peter_li wrote: Fri Jun 16, 2023 2:27 am
Does somebody knew why grub.cfg sometimes states root=UUID... and sometimes root=/dev/sdbXX? There are cases where my internal sda is not shown and then sdb becomes to sda and the boot stops in a dash shell.
update-grub generates grub menu entries in two flavours: If it detects a grub-installation on the other OS it uses information found within the grub.cfg file on the other OS. If there is no grub installed on the other OS, it would create generic menu entries with root=/dev/name entries. So you better always install GRUB, to get proper root=UUID=xxxx boot parameter.
@fehlix I think I wrote a answer before with the content that the os-prober on MX-23 does not detect my other Linux Distribution installations correctly. If they sit on BTRFS they will not detected. But I dont find my last post. So for showing you the difference I state the output from os-prober on Manjaro:
Code: Select all
/dev/sda4@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sda7:MX 21.3 Wildflower (21.3):MX:linux
/dev/sdb1:Trisquel GNU/Linux 11.0, Aramo (11.0):Trisquel:linux
/dev/sdb10:Ubuntu 23.04:Ubuntu:linux:btrfs:UUID=58a3a355-2870-487f-a190-0e281d56dc29:subvol=@
/dev/sdb11:Ubuntu 22.04.2 LTS (22.04):Ubuntu1:linux
/dev/sdb12:Void Linux:Void:linux
/dev/sdb13:NuTyX GNU/Linux (rolling):NuTyX:linux
/dev/sdb14:MX 23 Libretto (23):MX1:linux
/dev/sdb2:Ubuntu 23.04 (23.04):Ubuntu2:linux
/dev/sdb3:Debian GNU/Linux 12 (bookworm):Debian:linux
/dev/sdb4:EndeavourOS Linux (rolling):EndeavourOS:linux
/dev/sdb5:Artix Linux (rolling):Artix:linux
/dev/sdb6:Garuda Linux:Garuda:linux:btrfs:UUID=4eec2dc6-51e2-4d0a-9c57-13ffff02ca94:subvol=@
/dev/sdb7:Linux Mint 21.1:Linux:linux:btrfs:UUID=47649cc7-8995-4f70-9b19-19b192fff89c:subvol=@
/dev/sdb8:openSUSE Leap 15.5:openSUSE:linux:btrfs:UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706:subvol=@/.snapshots/1/snapshot
On MX the partitions sdb6 up to sdb10, all on btrfs, were not shown.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 12:40 pm
by fehlix
peter_li wrote: Fri Jun 16, 2023 12:29 pm
@fehlix I think I wrote a answer before with the content that the os-prober on MX-23 does not detect my other Linux Distribution installations correctly. If they sit on BTRFS they will not detected. But I dont find my last post. So for showing you the difference I state the output from os-prober on Manjaro:
That's correct, grub through it's use of os-prober won't be able to detect another install on btrfs,
esp, where /root sits on a /@ subvolume. I haven't tried an btrfs install where root is not on a subvolume
MX defaults to install root on /@, mainly b/c that's a timeshift requirement.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 1:09 pm
by fehlix
siamhie wrote: Fri Jun 16, 2023 11:06 am
Are we going back to apt for updates? When applying updates this morning apt showed and not nala.
We had two nala related reports like "nala hangs" and another one where the "nala hanger",
was actually not nala related but due to a 3min timeout of a not properly provided init-script of ntpsec.
The ntpsec timeout hanger has been fixed. But the other two, could not have been reproduced and so
we decided to go back to apt as default - until we can reproduce and potential help to fix nala, if possible.
User can always enable nala
within ~/.config/MX-Linux/apt-notifier.conf
and change this line
Code: Select all
# Alternative apt/apt-get command line package manager
# use_nala = true
to
Code: Select all
# Alternative apt/apt-get command line package manager
use_nala = true
siamhie wrote: Fri Jun 16, 2023 11:06 am
Can I set the notifier/update window back to 80x24 in size?
It's currently not adjustable, but defaults to terminal with of about 75%-80% of screen size.
I guess with people having now more bigger screen may be adding to a max terminal size.
80x25 can be definitely to small in size as user may have other repos with longer urls,
which would create quite some line-breaks with such a small terminal size.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 1:33 pm
by andy
dolphin_oracle wrote: Fri Jun 16, 2023 11:59 am
andy wrote: Fri Jun 16, 2023 10:04 am
...
did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.
Indeed, I did not. Why? From former experiences, knowing that installer has a good checking for improper setup (always had halted me, when encryption was enabled and I was trying to have boot on root partition), so I was experimenting, if it finally supports boot on root together with encryption.
So, installer let continue, with wrong (unsupported) setting.
(( Why, in the age of surveillance, when attacks on encryption are much easier, and funded by big entities, we still does not have working LUKS2 (which enables much safer PBKDF)?
What is holding smart programmers from making it working? ))
BUT:
Timeshift does not recognise BTRFS.
(its radio button is disabled)
Code: Select all
$ sudo btrfs subvolume list /
ID 256 gen 36 top level 5 path @
So, I double checked it (reinstalled once more), same result.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 2:01 pm
by siamhie
fehlix wrote: Fri Jun 16, 2023 1:09 pm
We had two nala related reports like "nala hangs" and another one where the "nala hanger",
was actually not nala related but due to a 3min timeout of a not properly provided init-script of ntpsec.
The ntpsec timeout hanger has been fixed. But the other two, could not have been reproduced and so
we decided to go back to apt as default - until we can reproduce and potential help to fix nala, if possible.
User can always enable nala
within ~/.config/MX-Linux/apt-notifier.conf
and change this line
Code: Select all
# Alternative apt/apt-get command line package manager
# use_nala = true
to
Code: Select all
# Alternative apt/apt-get command line package manager
use_nala = true
@fehlix I recall beta1 had both "use_nala = true" uncommented. Pretty easy to revert back to nala.
It's currently not adjustable, but defaults to terminal with of about 75%-80% of screen size.
I guess with people having now more bigger screen may be adding to a max terminal size.
80x25 can be definitely to small in size as user may have other repos with longer urls,
which would create quite some line-breaks with such a small terminal size.
That's a shame. It seems to take up a lot of real estate on my 1440 monitor and Jerry mentioned his monitor size of 1366x768 which I can only imagine would take up most of his screen.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 3:24 pm
by peter_li
fehlix wrote: Fri Jun 16, 2023 12:40 pm
peter_li wrote: Fri Jun 16, 2023 12:29 pm
@fehlix I think I wrote a answer before with the content that the os-prober on MX-23 does not detect my other Linux Distribution installations correctly. If they sit on BTRFS they will not detected. But I dont find my last post. So for showing you the difference I state the output from os-prober on Manjaro:
That's correct, grub through it's use of os-prober won't be able to detect another install on btrfs,
esp, where /root sits on a /@ subvolume. I haven't tried an btrfs install where root is not on a subvolume
MX defaults to install root on /@, mainly b/c that's a timeshift requirement.
Excuse me please when I ask again. So you mean the output of os-prober on MX Linux is the expected behavior and that what Manjaro and maybe others additionally do is extraordinary? So the solution for a multibooting environment, mainly for testing, is to stick at ext4 it seems?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 3:34 pm
by TerryL
OK, my initial effort was to run the beta-2 as a live USB - no problems noticed
Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely
What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.
Has anyone else had this problem?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 3:36 pm
by fehlix
peter_li wrote: Fri Jun 16, 2023 3:24 pm
fehlix wrote: Fri Jun 16, 2023 12:40 pm
peter_li wrote: Fri Jun 16, 2023 12:29 pm
@fehlix I think I wrote a answer before with the content that the os-prober on MX-23 does not detect my other Linux Distribution installations correctly. If they sit on BTRFS they will not detected. But I dont find my last post. So for showing you the difference I state the output from os-prober on Manjaro:
That's correct, grub through it's use of os-prober won't be able to detect another install on btrfs,
esp, where /root sits on a /@ subvolume. I haven't tried an btrfs install where root is not on a subvolume
MX defaults to install root on /@, mainly b/c that's a timeshift requirement.
Excuse me please when I ask again. So you mean the output of os-prober on MX Linux is the expected behavior and that what Manjaro and maybe others additionally do is extraordinary? So the solution for a multibooting environment, mainly for testing, is to stick at ext4 it seems?
As far as debian provided grub / os-prober goes, yes. Note: With Debian 12 bookworm, os-prober is kind of completely disabled. In MX-23 we re-enabeled os-prober to further support multi-boot with GRUB. But no attempt was made to enance grub/os-prober to detect os installs with btrfs and root-subvolumes.
User can still manually add other OS grub menu entries, e.g within /boot/grub/custom.cfg
+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 4:26 pm
by peter_li
fehlix wrote: Fri Jun 16, 2023 3:36 pm
peter_li wrote: Fri Jun 16, 2023 3:24 pm
fehlix wrote: Fri Jun 16, 2023 12:40 pm
That's correct, grub through it's use of os-prober won't be able to detect another install on btrfs,
esp, where /root sits on a /@ subvolume. I haven't tried an btrfs install where root is not on a subvolume
MX defaults to install root on /@, mainly b/c that's a timeshift requirement.
Excuse me please when I ask again. So you mean the output of os-prober on MX Linux is the expected behavior and that what Manjaro and maybe others additionally do is extraordinary? So the solution for a multibooting environment, mainly for testing, is to stick at ext4 it seems?
As far as debian provided grub / os-prober goes, yes. Note: With Debian 12 bookworm, os-prober is kind of completely disabled. In MX-23 we re-enabeled os-prober to further support multi-boot with GRUB. But no attempt was made to enance grub/os-prober to detect os installs with btrfs and root-subvolumes.
User can still manually add other OS grub menu entries, e.g within /boot/grub/custom.cfg
That would be the next question:
Shouldn't it be expected that Debian Bookworm with GRUB_DISABLE_OS_PROBER=false and MX Linux provide the same result?
Result on Debian:
Code: Select all
menuentry 'openSUSE Leap 15.5 (on /dev/sdb8)' --class opensuse --class gnu-linux --class gnu --class os $m>
insmod part_gpt
insmod btrfs
set root='hd1,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt8 --hint-efi=hd1,gpt8 --hint-baremeta>
else
search --no-floppy --fs-uuid --set=root 36f9708b-432f-4f9f-9dcd-6bb415e37706
fi
linux /boot/vmlinuz-5.14.21-150500.53-default root=UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 ${ext>
initrd /boot/initrd-5.14.21-150500.53-default
}
/etc/fstab on openSUSE:
Code: Select all
$ sudo cat /mnt/sdb8/etc/fstab
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 / btrfs defaults 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /var btrfs subvol=/@/var 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /usr/local btrfs subvol=/@/usr/local 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /tmp btrfs subvol=/@/tmp 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /srv btrfs subvol=/@/srv 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /root btrfs subvol=/@/root 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /opt btrfs subvol=/@/opt 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /home btrfs subvol=/@/home 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=9fc81fd9-6af1-4a50-9f3a-0d557a9cd476 swap swap defaults 0 0
UUID=7366-5199 /boot/efi vfat utf8 0 2
On MX not in result of os-prober.
I wonder how it comes to the difference?
+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.
That's fine especially cause one can install Grub2 and rEFInd as I read. But you will have to inform it about OS updates or added/deleted systems?
Would it there not be the better or equal behavior to hammer on the F12(at least on a DELL Latitude E6510) key at boot?
But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 5:16 pm
by Eadwine Rose
I am running into a Kodi issue. Installed the one from popular in MXPI. Seems a VLC one too, but haven't tried that yet.
Code: Select all
libva info: VA-API version 1.17.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Googled that, ran into this page:
https://bbs.archlinux.org/viewtopic.php?id=282638
Which basically says:
"seems to be caused by the recent update of libva to 2.17.0-1. Downgrading to libva 2.16.0-1 helped here."
Someone else says:
"===> So as a workaround define this environment variable (and everything works with libva 2.17.0-1, vlc included) :
Code: Select all
echo "setenv LIBVA_DRIVER_NAME nvidia" > /etc/profile.d/libva.csh
echo "export LIBVA_DRIVER_NAME=nvidia" > /etc/profile.d/libva.sh
"
Well, since this is a play installation anyway I up and did that environment variable, rebooted, waited for it to blow up, and nada, still the same results when I run vainfo.
Likely the right way there, not here. Ah well, would have been fun if I could have served up the solution as well
But we'll run with the info.
I figured I'd share it with you guys, since this kinda looks like it may pop up for more with nvidia cards and Kodi/VLC
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
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 1607 date: 06/17/2019
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball serial: <filter>
charge: 100% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 768 KiB
desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 1502 high: 1550 min/max: 1550/3200 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1545 2: 1533 3: 1533 4: 1534 5: 1550 6: 1451
7: 1550 8: 1535 9: 1530 10: 1544 11: 1512 12: 1442 13: 1472 14: 1425 15: 1448 16: 1433
bogomips: 102193
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
vendor: Hauppauge works driver: cx23885 v: 0.0.4 pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 07:00.0 chip-ID: 14f1:8880 class-ID: 0400
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 525.105.17
non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.0 chip-ID: 10de:1c82
class-ID: 0300
Device-3: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:3
chip-ID: 046d:09a4 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
gpu: cx23885,nvidia display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
s-diag: 1055mm (41.55")
Monitor-1: DVI-D-0 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
diag: 547mm (21.54") modes: N/A
Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 92
size: 531x299mm (20.91x11.77") diag: 609mm (23.99") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.105.17 renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
vendor: Hauppauge works driver: cx23885 bus-ID: 1-7:3 v: 0.0.4 pcie: chip-ID: 046d:09a4 gen: 1
class-ID: 0102 serial: <filter> speed: 2.5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 14f1:8880
class-ID: 0400
Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:0fb9 class-ID: 0403
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
Device-4: Logitech QuickCam E 3500 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: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-1:2
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 1-8:4 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 931.54 GiB used: 158.25 GiB (17.0%)
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: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 34.0 C scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
temp: 35.0 C scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
temp: 34.0 C scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
temp: 34.0 C scheme: GPT
Partition:
ID-1: / raw-size: 58.59 GiB size: 57.37 GiB (97.92%) used: 7.92 GiB (13.8%) fs: ext4
dev: /dev/sdb1 maj-min: 8:17
ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 26.5 MiB (5.3%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 166.48 GiB size: 162.81 GiB (97.79%) used: 274.7 MiB (0.2%) fs: ext4
dev: /dev/sdb3 maj-min: 8:19
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2
maj-min: 8:18
Sensors:
System Temperatures: cpu: 42.6 C mobo: 34.0 C gpu: nvidia temp: 42 C
Fan Speeds (RPM): cpu: 760 fan-2: 795 fan-3: 0 fan-4: 695 fan-6: 0 gpu: nvidia fan: 26%
Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.29
Repos:
Packages: pm: dpkg pkgs: 2206 libs: 1149 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://nl.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 347 Uptime: 8m wakeups: 3 Memory: 31.28 GiB used: 2.27 GiB (7.3%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 5:29 pm
by gRegNfo
Hi there,
Can I ask a simple question here?
How can I upgrade beta1 from beta2 iso without losing my home and setings?
I didnt want to reinstall from scratch and have to handle configs again.
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 5:54 pm
by fehlix
peter_li wrote: Fri Jun 16, 2023 4:26 pm
Shouldn't it be expected that Debian Bookworm with GRUB_DISABLE_OS_PROBER=false and MX Linux provide the same result?
Result on Debian:
Code: Select all
menuentry 'openSUSE Leap 15.5 (on /dev/sdb8)' --class opensuse --class gnu-linux --class gnu --class os $m>
insmod part_gpt
insmod btrfs
set root='hd1,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt8 --hint-efi=hd1,gpt8 --hint-baremeta>
else
search --no-floppy --fs-uuid --set=root 36f9708b-432f-4f9f-9dcd-6bb415e37706
fi
linux /boot/vmlinuz-5.14.21-150500.53-default root=UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 ${ext>
initrd /boot/initrd-5.14.21-150500.53-default
}
/etc/fstab on openSUSE:
Code: Select all
$ sudo cat /mnt/sdb8/etc/fstab
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 / btrfs defaults 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /var btrfs subvol=/@/var 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /usr/local btrfs subvol=/@/usr/local 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /tmp btrfs subvol=/@/tmp 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /srv btrfs subvol=/@/srv 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /root btrfs subvol=/@/root 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /opt btrfs subvol=/@/opt 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /home btrfs subvol=/@/home 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=9fc81fd9-6af1-4a50-9f3a-0d557a9cd476 swap swap defaults 0 0
UUID=7366-5199 /boot/efi vfat utf8 0 2
On MX not in result of os-prober.
I wonder how it comes to the difference?
That's correct, it should have also listed btrfs install with "/" on top-volume.
peter_li wrote: Fri Jun 16, 2023 4:26 pm
+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.
That's fine especially cause one can install Grub2 and rEFInd as I read. But you will have to inform it about OS updates or added/deleted systems?
Would it there not be the better or equal behavior to hammer on the F12(at least on a DELL Latitude E6510) key at boot?
I idea for inventing rEFInd was something like an easier efi-bootmanager. It can be set as default efi-loader and would list all found efi-loader, not only those which are listed with NVRAM(and may be invalid already).
peter_li wrote: Fri Jun 16, 2023 4:26 pm
But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.
That's Ubuntu and secure-boot related issue, as all those ubuntu-flavors use just one efi-loader entry.
That's actually similar what Debian is now doing, so if you have to install two debian installations, you would only find one EFI-loader. One way to solve it, use for every such install a separate ESP.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:14 pm
by dolphin_oracle
gRegNfo wrote: Fri Jun 16, 2023 5:29 pm
Hi there,
Can I ask a simple question here?
How can I upgrade beta1 from beta2 iso without losing my home and setings?
I didnt want to reinstall from scratch and have to handle configs again.
Thanks
just run your regular updates. I'm not changing the labels for updated systems from beta1 and beta2, but you are getting updates.
once we go final all beta and rc releases will see their version strings bumped.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:42 pm
by megaherz33
MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 6:57 pm
by Jerry3904
megaherz33 wrote: Fri Jun 16, 2023 6:42 pm
MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"
Install on what kind of a machine (Quick System Info)
Did you check the integrity of the download?
Did you run the USB check? Try reformating it
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:26 pm
by TerryL
TerryL wrote: Fri Jun 16, 2023 3:34 pm
OK, my initial effort was to run the beta-2 as a live USB - no problems noticed
Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely
What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.
Has anyone else had this problem?
Forgot to add - MX-23 beta-2 XFCE on a Lenovo X240
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:29 pm
by fehlix
megaherz33 wrote: Fri Jun 16, 2023 6:42 pm
MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"
Some more details would be good.
Have you made /selected "Check Integrity of the Live media"?
Also, we use the term "install" for installing MX Linux from a live Booted media
after boot.
The message "AntiX/linuxfs file could not be found" indicates
that the LiveBoot was not performed.
So suggest give more details, how you created the LiveBoot Media from the downloaded ISO.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:31 pm
by dolphin_oracle
TerryL wrote: Fri Jun 16, 2023 7:26 pm
TerryL wrote: Fri Jun 16, 2023 3:34 pm
OK, my initial effort was to run the beta-2 as a live USB - no problems noticed
Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely
What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.
Has anyone else had this problem?
Forgot to add - MX-23 beta-2 XFCE on a Lenovo X240
antix uses the same installer, so likely identical or near to. should be dropdowns for the various partitions discovered.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 7:37 pm
by BV206
I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except
en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.
Code: Select all
Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings: LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]
I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 8:08 pm
by fehlix
BV206 wrote: Fri Jun 16, 2023 7:37 pm
I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except
en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.
Code: Select all
Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings: LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]
I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.
what would this show:
and
and
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 8:10 pm
by dolphin_oracle
andy wrote: Fri Jun 16, 2023 1:33 pm
dolphin_oracle wrote: Fri Jun 16, 2023 11:59 am
andy wrote: Fri Jun 16, 2023 10:04 am
...
did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.
Indeed, I did not. Why? From former experiences, knowing that installer has a good checking for improper setup (always had halted me, when encryption was enabled and I was trying to have boot on root partition), so I was experimenting, if it finally supports boot on root together with encryption.
So, installer let continue, with wrong (unsupported) setting.
(( Why, in the age of surveillance, when attacks on encryption are much easier, and funded by big entities, we still does not have working LUKS2 (which enables much safer PBKDF)?
What is holding smart programmers from making it working? ))
BUT:
Timeshift does not recognise BTRFS.
(its radio button is disabled)
Code: Select all
$ sudo btrfs subvolume list /
ID 256 gen 36 top level 5 path @
So, I double checked it (reinstalled once more), same result.
ok we are looking into why the installer let you continue without a boot partition, thanks for the report.
I can confirm the timeshift report as well. apparently it doesn't like a btrfs format inside a luks container. works OK if the btrfs partition is not encrypted.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 9:20 pm
by peter_li
fehlix wrote: Fri Jun 16, 2023 5:54 pm
peter_li wrote: Fri Jun 16, 2023 4:26 pm
+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.
That's fine especially cause one can install Grub2 and rEFInd as I read. But you will have to inform it about OS updates or added/deleted systems?
Would it there not be the better or equal behavior to hammer on the F12(at least on a DELL Latitude E6510) key at boot?
I idea for inventing rEFInd was something like an easier efi-bootmanager. It can be set as default efi-loader and would list all found efi-loader, not only those which are listed with NVRAM(and may be invalid already).
I thought when I hammered F12 the computer shows me the content of the EFI-SYSTEM parttion direct but you mean its the content of the NVRAM which is on the computer board? So a installation need to write to both? Therefore more than only one EFI partition may exist as long as in the NVRAM is stated which to use?
fehlix wrote: Fri Jun 16, 2023 5:54 pm
peter_li wrote: Fri Jun 16, 2023 4:26 pm
But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.
fehlix wrote: Fri Jun 16, 2023 5:54 pm
That's Ubuntu and secure-boot related issue, as all those ubuntu-flavors use just one efi-loader entry.
That's actually similar what Debian is now doing, so if you have to install two debian installations, you would only find one EFI-loader. One way to solve it, use for every such install a separate ESP.
So you mean that more than one may be created maybe on the same disk? Is this supported now? As I read on this
page it seems not to be supported? So I would need three or more to access my three Ubuntu-flavors, okay?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:13 pm
by asqwerth
TerryL wrote: Fri Jun 16, 2023 7:26 pm
TerryL wrote: Fri Jun 16, 2023 3:34 pm
OK, my initial effort was to run the beta-2 as a live USB - no problems noticed
Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely
What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.
Has anyone else had this problem?
Forgot to add - MX-23 beta-2 XFCE on a Lenovo X240
While you can continue to upgrade beta1 to use it, some default configs were changed in beta 2, so you won't really be helpful in debugging beta 2 in this thread.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:19 pm
by asqwerth
@peter_li
From what I understand, normal grub in say, Arch, has os prober disabled but the user can edit /etc/default/grub to say no to disable os prober.
Apparently in Debian 12, in every update of grub package , they will redo the disabling of os prober so multi boot machines will not search for other distros or OSes again.
MX devs added their own script so that os prober will always be re-enabled. However that means that a user can't manually disable os prober from within that grub file. That instruction is ignored.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:29 pm
by pbear
FWIW, I prefer to use 40_custom rather than manually editing grub.cfg. Haven't tested btrfs in a couple years (don't use), but worked fine then. Be sure to use /@ on the configfile line if appropriate.
[Edited for clarity.]
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:33 pm
by pbear
TerryL wrote: Fri Jun 16, 2023 3:34 pm
The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.
Has anyone else had this problem?
FWIW, I installed XFCE beta2 to a similar multi-boot test box. Worked fine.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 16, 2023 10:42 pm
by Freja
jstdk wrote: Fri Jun 16, 2023 7:38 am
Thanks to everyone involved in building this great distro. I have been testing Libretto XFCE since beta 1, hereby my issues encountered.
Hardware:
Asus Vivobook Oled 3k 12th gen Intel
24 Ghz Ram
- Scaling issues. It happens frequently that I need to rescale on boot (Display->Scaling->0.5). The system sometimes (not always) forgets my settings during reboots/wakepups.
- Crashes when connecting to an external screen (HDMI). First the option is shown how to use the external screen (mirror, extension, etc). After choosing, the computer reboots
- MX Linux animation on startup and shutdown is extremely slow, it takes almost a minute to run (this was smooth in a VM, not sure why not on metal)
- The notification 'Do not show this message again', for example when a network is found, is ignored. The message keeps on showing up. I had to put the machine in Do not disturb mode
- Telegram Desktop Flatpak cannot be installed using the software installer (Error pulling from repo: GPG verification enabled, but no signatures found)
My MacBook Pro 2013 13inch still has same problem.
And, I saw that In the youtube MX-23-b2 review movie,
boot animation protruding to the screen (too big animation image).
Then, We need to fix boot animation.
I will made 60% shrink animation .png. I will send it to
@CharlesV tonight,
I want you to prepare a test machine and review the code. I'm sorry for increase your work.
If you don't have a test machine, you might want something my 2013 MacBook Pro,
or closer to the Asus Vivobook Oled 3k 12th gen Intel.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 12:14 am
by CharlesV
Freja wrote: Fri Jun 16, 2023 10:42 pm
jstdk wrote: Fri Jun 16, 2023 7:38 am
Thanks to everyone involved in building this great distro. I have been testing Libretto XFCE since beta 1, hereby my issues encountered.
Hardware:
Asus Vivobook Oled 3k 12th gen Intel
24 Ghz Ram
- Scaling issues. It happens frequently that I need to rescale on boot (Display->Scaling->0.5). The system sometimes (not always) forgets my settings during reboots/wakepups.
- Crashes when connecting to an external screen (HDMI). First the option is shown how to use the external screen (mirror, extension, etc). After choosing, the computer reboots
- MX Linux animation on startup and shutdown is extremely slow, it takes almost a minute to run (this was smooth in a VM, not sure why not on metal)
- The notification 'Do not show this message again', for example when a network is found, is ignored. The message keeps on showing up. I had to put the machine in Do not disturb mode
- Telegram Desktop Flatpak cannot be installed using the software installer (Error pulling from repo: GPG verification enabled, but no signatures found)
My MacBook Pro 2013 13inch still has same problem.
And, I saw that In the youtube MX-23-b2 review movie,
boot animation protruding to the screen (too big animation image).
Then, We need to fix boot animation.
I will made 60% shrink animation .png. I will send it to @CharlesV tonight,
I want you to prepare a test machine and review the code. I'm sorry for increase your work.
If you don't have a test machine, you might want something my 2013 MacBook Pro,
or closer to the Asus Vivobook Oled 3k 12th gen Intel.
Cool, thanks. I am closing in on the encrypted password dialog, and *almost* there. ( having to dodge around the image, so 60% may resolve that too. )
Also, going to attempt to dynamically shrink it all tomorrow,based upon user screen size.. not sure about that one, but .. worth a few cycles to try ;-p
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 3:03 am
by kobaian
MX-Fluxbox 23beta2 already installed and works fine, but some issues remain:
1. No icon for MXFB-Font and Tint2-Manager in the Appfinder.
2. No descriptions for Polish localization for MXFB-Tour and Configure-Top icons in the Appfinder.
3. In MXFB-Tour there is a chapter, how to use the XFCE-Appfinder but we've got now MXFB-Appfinder.
I've got also another questions:
4. Is it possible to localize the categories script for Appfinder, that all users would have categories tab in their own language?
5. Are there any plans to localize also the help tab?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 5:27 am
by fehlix
kobaian wrote: Sat Jun 17, 2023 3:03 am
MX-Fluxbox 23beta2 already installed and works fine, but some issues remain:
3. In MXFB-Tour there is a chapter, how to use the XFCE-Appfinder but we've got now MXFB-Appfinder.
MX-tour is currently re-worked and we will put those text shown onto transifex for translation.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 5:33 am
by megaherz33
fehlix wrote: Fri Jun 16, 2023 7:29 pm
megaherz33 wrote: Fri Jun 16, 2023 6:42 pm
MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"
Some more details would be good.
Have you made /selected "Check Integrity of the Live media"?
Also, we use the term "install" for installing MX Linux from a live Booted media
after boot.
The message "AntiX/linuxfs file could not be found" indicates
that the LiveBoot was not performed.
So suggest give more details, how you created the LiveBoot Media from the downloaded ISO.
HI,
Old PC.
Machine: G31TM-P21 (MSI)
CPU: Intel Core2 Duo E 6550
Graphics: Intel 82G33/G31
Monitor: Acer AL1619W
MX Linux 21.3 installs without problems.
The only problem is there is no screen resolution of the desired 1440x900
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 5:43 am
by andy
andy wrote: Fri Jun 16, 2023 1:33 pm
(( Why, in the age of surveillance, when attacks on encryption are much easier, and big adversaries have huge resources, we still does not have working LUKS2 (which enables much safer PBKDF)?
What is holding smart programmers from making it working? ))
edit: some rephrasing to better convey what I meant
Just to put more context for other folks:
It is vitally important to choose good password. It is clear from this information:
Dead simple and accessible password attack against LUKS, for EVERYONE!
https://blog.elcomsoft.com/2020/08/brea ... ncryption/
For curious some background around mechanics in LUKS:
https://crypto.stackexchange.com/questi ... master-key
G'day. LUKS stores multiple copies of the master key in what it terms key slots. Each key-slot contains an encrypted copy of the master key, and it can vary in its password-based KDF parameters (and even algorithms). The parameters and algorithms can sometimes be wildly different, giving rise to the circumstance where forcing one key-slot may be infeasible, while another is fundamentally weak. (Both will yield the master key.)
For LUKS1, the best option for the password-based KDF is PBKDF2. For LUKS2, an additional option exists to use Argon2, which gives you the potential to make it even harder to force a corresponding key-slot... but in all cases this will depend on the hardness parameters chosen, as well as the relative strength of the password. (In LUKS2 both options can exist in parallel.)
And if you have master key already extracted...
https://unix.stackexchange.com/question ... master-key
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 5:58 am
by Melber
kobaian wrote: Sat Jun 17, 2023 3:03 am
MX-Fluxbox 23beta2 already installed and works fine, but some issues remain:
1. No icon for MXFB-Font and Tint2-Manager in the Appfinder.
2. No descriptions for Polish localization for MXFB-Tour and Configure-Top icons in the Appfinder.
3. In MXFB-Tour there is a chapter, how to use the XFCE-Appfinder but we've got now MXFB-Appfinder.
I've got also another questions:
4. Is it possible to localize the categories script for Appfinder, that all users would have categories tab in their own language?
5. Are there any plans to localize also the help tab?
1. .desktop files need correction. Try following edits
/usr/share/applications/mxfb-font.desktop
/usr/share/applications/mxfb-tint2-manager.desktop
2. & 3. as fehlix said, we're still working on updating MXFB-Tour
4. & 5. Will look into it.
@Jerry3904 ?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 6:13 am
by ceeslans
@Melber @kobaian ... and while you're at it, perhaps also edit 'mxfb-backgrounds.desktop' to show its icon in rofi :
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 6:38 am
by Jerry3904
@kobaian 4: it should be possible one way or another, will ask @fehlix. Which file is that? 5. The help file itself ("Appfinder") contains already 10 DeepL translations, or did you mean something else?
@Melber I'll change those desktop files -- DONE
@ceeslans that one too -- DONE
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 8:32 am
by Melber
Jerry3904 wrote: Sat Jun 17, 2023 6:38 am
@kobaian 4: it should be possible one way or another, will ask @fehlix. Which file is that? 5. The help file itself ("Appfinder") contains already 10 DeepL translations, or did you mean something else?
I think kobaian means the text in the app tab itself, ie. Help and Settings.
Hopefully both "Categories" and "Help" tabs just a matter of adding gettext in the relevant scripts and creating po/mo files...
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 8:46 am
by BV206
fehlix wrote: Fri Jun 16, 2023 8:08 pm
BV206 wrote: Fri Jun 16, 2023 7:37 pm
I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except
en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.
Code: Select all
Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings: LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]
I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.
what would this show:
and
and
I fixed it before I read this reply.
I ran those yesterday but don't remember what was missing.
I do remember that /etc/default/locale only had
LANG=en_US.UTF-8 but it was commented out.
I also had the same thing happen on Debian 12. Both installed with US English as the default language but it couldn't find `en_GB' for some reason. I ran
sudo apt install --reinstall locales and then
sudo dpkg-reconfigure locales on both MX 23 and Debian 12 and it generated the en_US.UTF-8 locale with no errors and without commenting out anything in /etc/default/locale.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 9:32 am
by kobaian
Jerry3904 wrote: Sat Jun 17, 2023 6:38 am
@kobaian 4: it should be possible one way or another, will ask @fehlix. Which file is that? 5. The help file itself ("Appfinder") contains already 10 DeepL translations, or did you mean something else?
I mean /usr/bin/app-categories and /usr/share/rofi/rofi-help_appfinder - the bash scripts that run categories and help tab in the Appfinder. Now no matter which language is set, everyone will see the names of categories in English and for everyone will see "Appfinder" and "Settings" in English in the help-tab
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 9:34 am
by Jerry3904
Thanks.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 9:38 am
by peter_li
fehlix wrote: Fri Jun 16, 2023 5:54 pm
peter_li wrote: Fri Jun 16, 2023 4:26 pm
But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.
That's Ubuntu and secure-boot related issue, as all those ubuntu-flavors use just one efi-loader entry.
That's actually similar what Debian is now doing, so if you have to install two debian installations, you would only find one EFI-loader. One way to solve it, use for every such install a separate ESP.
@fehlix What's about MX Respins? Will they do not also overwrite the existing MX23 directory on EFI and NVRAM? Or can there be a better way?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 9:55 am
by siamhie
MX-23 fluxbox-beta2
Neofetch doesn't show DE or Packages information.
neofetch.jpg
From my neofetch config.conf file.
Code: Select all
info "OS" distro
info "WM" wm
info "Kernel" kernel
info "CPU" cpu
info "Memory" memory
info "GPU" gpu
info "Resolution" resolution
info "Packages" packages
info "DE" de
info "WM Theme" wm_theme
info "Theme" theme
info "Icons" icons
info "Terminal" term
info "Terminal Font" term_font
info "Disk" disk
Code: Select all
# Packages
# Show/Hide Package Manager names.
#
# Default: 'tiny'
# Values: 'on', 'tiny' 'off'
# Flag: --package_managers
#
# Example:
# on: '998 (pacman), 8 (flatpak), 4 (snap)'
# tiny: '908 (pacman, flatpak, snap)'
# off: '908'
package_managers="on"
# Desktop Environment
# Show Desktop Environment version
#
# Default: 'on'
# Values: 'on', 'off'
# Flag: --de_version
de_version="on"
I booted up the fluxbox-beta2 live ISO and DE shows but Packages doesn't. Tested it also with the MX-23 XFCE-beta2 live ISO with same results, DE shows but Packages doesn't.
QSI
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
amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
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 System: Micro-Star product: MS-7C56 v: 2.0 serial: <superuser required>
Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required> UEFI: American
Megatrends LLC. v: A.B0 date: 08/11/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 3800X 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: 0x8701021
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2200 min/max: 2200/4559 boost: enabled scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200
10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 bogomips: 124809
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 0b:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 mapped: DisplayPort-0 model: HP X27q serial: <filter> built: 2021
res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
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: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel modules: wl pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 8.19 TiB used: 879.79 GiB (10.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital model: WDS500G1X0E-00AFY0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 613000WD temp: 38.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 102000WD temp: 37.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 465.26 GiB size: 456.89 GiB (98.20%) used: 8.34 GiB (1.8%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 572 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 65 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme1n1p1
maj-min: 259:1
Sensors:
System Temperatures: cpu: 34.9 C mobo: N/A gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 783
Repos:
Packages: pm: dpkg pkgs: 2076 libs: 1058 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/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bullseye main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Info:
Processes: 335 Uptime: 25m wakeups: 2 Memory: 31.27 GiB used: 2.2 GiB (7.0%) Init: systemd v: 252
target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 11:08 am
by Jerry3904
Well you don't have a DE installed, right? But you do have a WM, which is correctly identified as Fluxbox. Don't know what "Packages" is supposed to show ()number?), but I don't even have it listed as a category.
Why isn't this a neofetch problem?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 12:42 pm
by Jerry3904
@keos This is the right place...and if you hope for a response provide the Quick System Info and the version you installed
---------------------------
Hello,
I don't know if this is the right forum.
Anyway, I install the latest beta version of mx-23, I update it.
Some problems ...
Chromium as browser, I always uninstall firefox. In chromium I install Startpage, the default is Duckduckgo, I don't like it, it's inferior in the quality of the searches -- once the browser was configured, duckduckgo disappeared and Odysee appeared as default browser. (?)
The internet connection says Eth0 (?)
Can't do anything on the system now, it has lost connection to the internet. I'm posting here from MX-21.
As it is a Beta I would like to know if this is normal due to the instability of the system.
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 12:45 pm
by siamhie
Jerry3904 wrote: Sat Jun 17, 2023 11:08 am
Well you don't have a DE installed, right? But you do have a WM, which is correctly identified as Fluxbox. Don't know what "Packages" is supposed to show ()number?), but I don't even have it listed as a category.
Why isn't this a neofetch problem?
@Jerry3904 I booted up several live ISO's with these results.
MX-23-Fluxbox-beta2-live-iso (DE listed just not Packages)
MX23-Fluxbox-beta2-live-iso.png
MX-21.3-XFCE-June_snapshot (DE listed just not Packages)
MX-21.3-XFCE-June_snapshot.png
Debian12-XFCE-live-iso (DE and Packages listed)
Debian12-XFCE-live-iso.png
I'm going to download MX-23-XFCE-beta2 live ISO and also boot my MX-21.3 fluxbox snapshot in the mean time to compare notes.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 12:57 pm
by j2mcgreg
@keos wrote:
Some problems ...
Chromium as browser, I always uninstall firefox. In chromium I install Startpage, the default is Duckduckgo, I don't like it, it's inferior in the quality of the searches -- once the browser was configured, duckduckgo disappeared and Odysee appeared as default browser. (?)
Click on the three vertical dots in the upper right hand corner, Scroll down to Settings, select Appearance and then insert your preference for your start page.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 1:08 pm
by keos
The iso: MX-23_beta2_x64.iso
The conection to internet is now possible (?)
Screenshot_2023-06-17_13-11-55.png
i did it, but this Odysee (Default) still over there(?)
Screenshot_2023-06-17_13-17-56.png
Code: Select all
keos@kaos:~
$ inxi -Fxxxrza
System:
Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64
root=UUID=600e4d5d-7c43-4bb6-8e4c-cbecb57df9ed 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_beta2_x64 Libretto June
15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: Dell product: Inspiron 3583 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Dell model: 0WHCP7 v: A00 serial: <superuser required> UEFI: Dell
v: 1.5.1 date: 05/30/2019
Battery:
ID-1: BAT0 charge: 39.9 Wh (100.0%) condition: 39.9/42.0 Wh (95.0%)
volts: 12.7 min: 11.4 model: SMP DELL VM73283 type: Li-poly serial: <filter>
status: full
CPU:
Info: model: Intel Core i5-8265U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check gen: core 8 level: v3 note: check
built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0xF6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled 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: 1387 high: 1800 min/max: 400/3900 scaling:
driver: intel_pstate governor: powersave cores: 1: 700 2: 700 3: 700 4: 1800
5: 1800 6: 1800 7: 1800 8: 1800 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
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: Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3ea0
class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 1-6:3 chip-ID: 0bda:5520 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver:
X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: AU Optronics 0x10ec built: 2017 res: 1366x768
hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (WHL
GT2) direct-render: Yes
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:9dc8 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: off with: 1: pipewire-pulse
status: off 2: wireplumber status: off tools: pw-cat,pw-cli,wpctl
Server-2: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 13.03 GiB (5.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: PC SN520 NVMe WDC 256GB size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
rev: 20200012 temp: 44.9 C scheme: GPT
Partition:
ID-1: / raw-size: 44.69 GiB size: 43.68 GiB (97.76%) used: 13.01 GiB (29.8%)
fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 1.43 GiB size: 1.43 GiB (99.80%)
used: 18.6 MiB (1.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 45.0 C pch: 42.0 C mobo: 37.0 C
Fan Speeds (RPM): cpu: 0
Repos:
Packages: pm: dpkg pkgs: 2353 libs: 1292
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
2: deb http://security.debian.org/debian-security/ bookworm-security non-free contrib main
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
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
Info:
Processes: 228 Uptime: 32m wakeups: 2 Memory: 7.63 GiB
used: 1.57 GiB (20.5%) Init: SysVinit v: 3.06 runlevel: 5 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 alt: 12 clang: 14.0.6 Shell: Bash
v: 5.2.15 running-in: xfce4-terminal inxi: 3.3.26
keos@kaos:~
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 1:19 pm
by richb
When applying Quick System Info, when the app appears just click on Copy For Forum and then paste into the post.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 1:50 pm
by keos
There is a video in inglish ... and at searching i got nothing:
Search found 0 matches: how to quick system information forum
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 1:59 pm
by j2mcgreg
@keos
Necesitamos el perfil completo de su computadora antes de que podamos continuar, por lo que debe publicar el resultado de la utilidad QSI. La utilidad Quick System Info (QSI) se encuentra en MX Tools y su salida se formatea automáticamente para su uso aquí en el foro. Ejecute la utilidad QSI, haga clic en "Copiar para foro" en la parte inferior y luego péguelo aquí en su hilo.
Reglas del Foro
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 2:04 pm
by keos
Gracias/Thanks!
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Dell product: Inspiron 3583 v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: Dell model: 0WHCP7 v: A00 serial: <superuser required> UEFI: Dell v: 1.5.1
date: 05/30/2019
Battery:
ID-1: BAT0 charge: 39.9 Wh (100.0%) condition: 39.9/42.0 Wh (95.0%) volts: 12.7 min: 11.4
model: SMP DELL VM73283 type: Li-poly serial: <filter> status: full
CPU:
Info: model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Comet/Whiskey Lake note: check
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0xF6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled 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: 1350 high: 1800 min/max: 400/3900 scaling: driver: intel_pstate
governor: powersave cores: 1: 1800 2: 1800 3: 900 4: 900 5: 1800 6: 1800 7: 900 8: 901
bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3
chip-ID: 0bda:5520 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: AU Optronics 0x10ec built: 2017 res: 1366x768 hz: 60 dpi: 101
gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
direct-render: Yes
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8
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: off with: 1: pipewire-pulse status: off 2: wireplumber
status: off tools: pw-cat,pw-cli,wpctl
Server-2: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 13.03 GiB (5.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520 NVMe WDC 256GB
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD
serial: <filter> rev: 20200012 temp: 44.9 C scheme: GPT
Partition:
ID-1: / raw-size: 44.69 GiB size: 43.68 GiB (97.76%) used: 13.02 GiB (29.8%) fs: ext4
dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 1.43 GiB size: 1.43 GiB (99.80%) used: 18.6 MiB (1.3%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 43.0 C pch: 41.0 C mobo: 37.0 C
Fan Speeds (RPM): cpu: 0
Repos:
Packages: pm: dpkg pkgs: 2353 libs: 1292 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
2: deb http://security.debian.org/debian-security/ bookworm-security non-free contrib main
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
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
Info:
Processes: 233 Uptime: 41m wakeups: 2 Memory: 7.63 GiB used: 1.5 GiB (19.7%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
clang: 14.0.6 Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 2:10 pm
by Eadwine Rose
You are on an English forum, please post in English, save for the designated subsections, thank you. :)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 2:26 pm
by siamhie
@Jerry3904 Seems the neofetch program is a customized version.
I removed neofetch from MXPI then purged it and removed the folder from ~./config and installed the version from Debian's bookworm ftp server (7.1.0-4)
Now it displays number of installed packages but with different information.
debians-neofetch.jpg
The version in our repo's has a different name (7.1.0+git20210726-0.2~mx21+1).
mx-neofetch.png
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 2:38 pm
by j2mcgreg
Eadwine Rose wrote: Sat Jun 17, 2023 2:10 pm
You are on an English forum, please post in English, save for the designated subsections, thank you. :)
I considered this to be a Catch 22 situation and went ahead. Shouldn't happen again.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 2:43 pm
by Eadwine Rose
Oh that was you. My brain was only half awake.
Thanks :)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 2:53 pm
by uncle mark
j2mcgreg wrote: Sat Jun 17, 2023 2:38 pm
Eadwine Rose wrote: Sat Jun 17, 2023 2:10 pm
You are on an English forum, please post in English, save for the designated subsections, thank you. :)
I considered this to be a Catch 22 situation and went ahead. Shouldn't happen again.
At least she didn't fish slap you.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 3:16 pm
by Buck Fankers
Feedback about Quick System Info:
WAU, great work, all those logs available in one place, perfect!
pbear wrote: Fri Jun 16, 2023 10:43 am
Buck Fankers wrote: Fri Jun 16, 2023 6:09 am
... is swap file now generally preferred way of setting up Linux system?
Swap file and swap partition both work fine. The former is more convenient on a single-install system, as it can be resized easily. The latter has the efficiency on a multi-boot system that it can be shared.
Thank you
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 7:07 pm
by FullScale4Me
pbear wrote: Thu Jun 15, 2023 10:58 pm
By the way, you might add to Known Issues that the ISO won't at present boot from Ventoy, a problem hopefully to be fixed by future Ventoy update.
Ventoy code upgrade to allow MX Linux 23 to boot
How to find
https://www.ventoy.net/en/doc_github_ci.html I had to poke into a few 'actions' to find one with download links.
Once downloaded and unarchived open terminal in folder of unzipped archive and run
Code: Select all
sudo sh Ventoy2Disk.sh -u /dev/sdX
where X is the target USB.
The -u switch is for upgrade...it doesn't touch the partition of ISOs. To install use the -i switch.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 8:03 pm
by CharlesV
HP Envy x360 2/23 - Just loaded Beta 2 on board and everything came up nicely, other than:
1) Sound still not playing in speakers (hasnt ever since I loaded MX on board - no matter what I have done)
2) Wireless networking REALLY slow
Havent had a chance to work with any of it yet, just started really looking at it.
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Convertible System: HP product: HP ENVY x360 2-in-1 Laptop 15-ew0xxx
v: Type1ProductConfigId serial: <superuser required> Chassis: type: 31
serial: <superuser required>
Mobo: HP model: 8A29 v: 22.10 serial: <superuser required> UEFI: Insyde v: F.14
date: 02/13/2023
Battery:
ID-1: BAT1 charge: 50.1 Wh (100.0%) condition: 50.1/51.0 Wh (98.3%) volts: 13.1 min: 11.6
model: Hewlett-Packard PABAS0241231 type: Li-ion serial: <filter> status: full
Device-1: hid-0018:04F3:406E.0001-battery model: ELAN2513:00 04F3:406E serial: N/A charge: N/A
status: N/A
CPU:
Info: model: 12th Gen Intel Core i7-1255U bits: 64 type: MST AMCP arch: Alder Lake level: v3
note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
microcode: 0x42A
Topology: cpus: 1x cores: 10 mt: 2 tpc: 2 st: 8 threads: 12 smt: enabled cache: L1: 928 KiB
desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB
desc: 1x12 MiB
Speed (MHz): avg: 2000 high: 2600 min/max: 400/4700:3500 scaling: driver: intel_pstate
governor: powersave cores: 1: 2600 2: 2600 3: 2600 4: 2600 5: 1199 6: 777 7: 511 8: 2600 9: 2600
10: 724 11: 2600 12: 2600 bogomips: 62668
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] vendor: Hewlett-Packard driver: i915
v: kernel arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: eDP-1 empty: DP-1,
DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46a8 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: AU Optronics 0xa08b built: 2019 res: 1920x1080 hz: 60 dpi: 142
gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (ADL GT2) direct-render: Yes
Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Hewlett-Packard
driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:51c8 class-ID: 0401
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 Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl bus-ID: 00:14.3
chip-ID: 8086:51f0 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-10:2 chip-ID: 8087:0033 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 476.94 GiB used: 10.87 GiB (2.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA model: N/A size: 476.94 GiB block-size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: HP01AN00
temp: 27.9 C scheme: GPT
Partition:
ID-1: / raw-size: 476.68 GiB size: 468.13 GiB (98.21%) used: 10.87 GiB (2.3%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0 fan-2: 0
Repos:
Packages: pm: dpkg pkgs: 2057 libs: 1041 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 306 Uptime: 6m wakeups: 7 Memory: 15.34 GiB used: 1.91 GiB (12.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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 8:14 pm
by siamhie
FullScale4Me wrote: Sat Jun 17, 2023 7:07 pm
pbear wrote: Thu Jun 15, 2023 10:58 pm
By the way, you might add to Known Issues that the ISO won't at present boot from Ventoy, a problem hopefully to be fixed by future Ventoy update.
Ventoy upgrade code upgrade to allow MX Linux 23 to boot
How to find
https://www.ventoy.net/en/doc_github_ci.html I had to poke into a few 'actions' to find one with download links.
Once downloaded and unarchived open terminal in folder of unzipped archive and run
Code: Select all
sudo sh Ventoy2Disk.sh -u /dev/sdX
where X is the target USB.
The -u switch is for upgrade...it doesn't touch the partition of ISOs.
@FullScale4Me I don't have an account to download the ventoy-linux file.
https://github.com/ventoy/Ventoy/action ... 4976511049
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 8:54 pm
by pbear
Thank you, that was the piece of the puzzle I was missing. If I've read that page before (likely enough), I had long since forgotten about it, so poking around on the
Actions page (
@fehlix's link) wasn't doing me any good. Notably, as
@siamhie mentions, one must have a GitHub account (I do) and have signed in (I hadn't) before the download links become available. FWIW, this
download link worked for me (though, again, only if logged into GitHub). Downloads a zip file; unzip to a tarball; extract; if using File Manager, right-click and select Open in Terminal. As you say, run
sudo sh Ventoy2Disk.sh -u /dev/sdx (where sdx is the device ID of the Ventoy drive).
And, yes, the patch works and I'm able to boot the beta2 ISOs from Ventoy.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 17, 2023 10:22 pm
by siamhie
pbear wrote: Sat Jun 17, 2023 8:54 pm
And, yes, the patch works and I'm able to boot the beta2 ISOs from Ventoy.
@pbear Working for me also.
@FullScale4Me sent me a link to download the update and now I have a working Ventoy 1.0.91 flash drive again.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 12:03 am
by i_ri
hello dolphin_oracle
on side and off side
mxfluxbox rootMenu >Out of sight >Toggle icons "[exec] (Toggle icons) { idesktoggle icons }"
strip command of trailing single "s", fehlix put it in the script;
officially the command is without s <idesktoggle icon>
If You could have what You wanted for a CursorOver: cursor, What would that be? a helicopter? a dolphin?
a kat? I think the man cursor looks a bit like a helicopter..
irilii
Consider. icon [ on | off ] to be icon [ PageA | PageB ]
Page off=PageB starts Blank.
Get two idesk menues.
Method two
Have idesk running, showing icons,
using mx-idesktool
Create an idesk icon name PageA with its command <idesktoggele icon> then run
<idesktoggle icon PageA.lnk>
The toggle switches the PageA.icon-send-to-other-page.
Method one
Have idesk running
Turn the icons off with
fluxbox rootmenu >Out of sight >Toggle icons
Now open mx-idesktool
fluxbox rootmenu >Appearance >Desktop icons
Create an icon its name PageA with its command <idesktoggle icon>
Quit mx-idesktool.
Now idesk is two pages.
The PageA icon is a signal of icons off.
PageB is now "off" stage with a PageA icon meaning launch "on."
Add icons two separate pages.
You can now menu toggle the two idesk presentations or you might
Click on the icon you just made, takes it to Page A, open mx-idesktool and Create an icon named PageB with its command <idesktoggle icon>
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 4:11 am
by peter_li
How to repair this broken pipe?
Code: Select all
Die folgenden Pakete werden aktualisiert (Upgrade):
rtl8821ce-dkms (5.5.2.1+git20221215-0.1~mx21+1 => 5.5.2.1+git20230504-0~mx23+1)
rtl8821cu-dkms (5.12.0+git20230215-1~mx21+1 => 5.12.0+git20230215-1~mx23+2)
2 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
...
depmod...
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Entpacken von rtl8821cu-dkms (5.12.0+git20230215-1~mx23+2) über (5.12.0+git20230215-1~mx21+1) ...
rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) wird eingerichtet ...
Loading new rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Deprecated feature: MODULES_CONF (/usr/src/rtl8821ce-5.5.2.1+git20230504/dkms.conf)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Done.
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
...
depmod...
rtl8821cu-dkms (5.12.0+git20230215-1~mx23+2) wird eingerichtet ...
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Building for 6.1.0-9-amd64
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
Done.
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
...
vollständige Aktualisierung abgeschlossen (oder wurde abgebrochen)
Dieses Terminalfenster kann nun geschlossen werden
But the dpkg.log looks normal?
Code: Select all
2023-06-18 09:31:29 startup archives unpack
2023-06-18 09:31:32 upgrade rtl8821ce-dkms:all 5.5.2.1+git20221215-0.1~mx21+1 5.5.2.1+git20230504-0~mx23+1
2023-06-18 09:31:32 status half-configured rtl8821ce-dkms:all 5.5.2.1+git20221215-0.1~mx21+1
2023-06-18 09:31:53 status unpacked rtl8821ce-dkms:all 5.5.2.1+git20221215-0.1~mx21+1
2023-06-18 09:31:53 status half-installed rtl8821ce-dkms:all 5.5.2.1+git20221215-0.1~mx21+1
2023-06-18 09:31:55 status unpacked rtl8821ce-dkms:all 5.5.2.1+git20230504-0~mx23+1
2023-06-18 09:31:55 upgrade rtl8821cu-dkms:all 5.12.0+git20230215-1~mx21+1 5.12.0+git20230215-1~mx23+2
2023-06-18 09:31:55 status half-configured rtl8821cu-dkms:all 5.12.0+git20230215-1~mx21+1
2023-06-18 09:31:58 status unpacked rtl8821cu-dkms:all 5.12.0+git20230215-1~mx21+1
2023-06-18 09:31:58 status half-installed rtl8821cu-dkms:all 5.12.0+git20230215-1~mx21+1
2023-06-18 09:32:00 status unpacked rtl8821cu-dkms:all 5.12.0+git20230215-1~mx23+2
2023-06-18 09:32:00 startup packages configure
2023-06-18 09:32:00 configure rtl8821ce-dkms:all 5.5.2.1+git20230504-0~mx23+1 <none>
2023-06-18 09:32:00 status unpacked rtl8821ce-dkms:all 5.5.2.1+git20230504-0~mx23+1
2023-06-18 09:32:00 status half-configured rtl8821ce-dkms:all 5.5.2.1+git20230504-0~mx23+1
2023-06-18 09:34:25 status installed rtl8821ce-dkms:all 5.5.2.1+git20230504-0~mx23+1
2023-06-18 09:34:25 configure rtl8821cu-dkms:all 5.12.0+git20230215-1~mx23+2 <none>
2023-06-18 09:34:25 status unpacked rtl8821cu-dkms:all 5.12.0+git20230215-1~mx23+2
2023-06-18 09:34:26 status half-configured rtl8821cu-dkms:all 5.12.0+git20230215-1~mx23+2
2023-06-18 09:40:32 status installed rtl8821cu-dkms:all 5.12.0+git20230215-1~mx23+2
Or could this be ignored?
The light of the notifier about updates still to handle was green and is now off.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 4:18 am
by Jamey
So far, so good!
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 slab_nomerge
init_on_alloc=1 init_on_free=1 page_alloc.shuffle=1 pti=on randomize_kstack_offset=on
vsyscall=none debugfs=off mitigations=auto,nosmt iommu=force iommu.strict=1 ipv6.disable=1
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 8 dm: SDDM Distro: MX-23_KDE_beta1_x64 Libretto
May 28 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Hewlett-Packard product: HP Z840 Workstation v: N/A
serial: <superuser required> Chassis: type: 6 serial: <superuser required>
Mobo: Hewlett-Packard model: 2129 v: 1.01 serial: <superuser required> UEFI: Hewlett-Packard
v: M60 v02.61 date: 03/23/2023
CPU:
Info: model: Intel Xeon E5-2690 v4 bits: 64 type: MCP SMP arch: Broadwell level: v3 note: check
built: 2015-18 process: Intel 14nm family: 6 model-id: 0x4F (79) stepping: 1 microcode: 0xB000040
Topology: cpus: 2x cores: 14 smt: disabled cache: L1: 2x 896 KiB (1.8 MiB) desc: d-14x32 KiB;
i-14x32 KiB L2: 2x 3.5 MiB (7 MiB) desc: 14x256 KiB L3: 2x 35 MiB (70 MiB) desc: 1x35 MiB
Speed (MHz): avg: 1467 high: 2600 min/max: 1200/2600 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1332 2: 1197 3: 1198 4: 1197 5: 1200 6: 1198 7: 1200 8: 1200 9: 1200
10: 1300 11: 1197 12: 1200 13: 1200 14: 1197 15: 2594 16: 1796 17: 2594 18: 1297 19: 1200
20: 2200 21: 1197 22: 1200 23: 1200 24: 2600 25: 1200 26: 1200 27: 2600 28: 1200
bogomips: 145293
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GM204GL [Quadro M5000] vendor: Hewlett-Packard driver: nvidia v: 525.105.17
non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm
built: 2014-19 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.0 chip-ID: 10de:13f0
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: kwin_x11 driver: X: loaded: nvidia
gpu: nvidia display-ID: :1 screens: 1
Screen-1: 0 s-res: 5120x1440 s-dpi: 107 s-size: 1216x342mm (47.87x13.46")
s-diag: 1263mm (49.73")
Monitor-1: DP-2 pos: primary,left res: 2560x1440 hz: 75 dpi: 109 size: 597x336mm (23.5x13.23")
diag: 685mm (26.97") modes: N/A
Monitor-2: DP-6 pos: right res: 2560x1440 hz: 60 dpi: 109 size: 596x335mm (23.46x13.19")
diag: 684mm (26.92") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.105.17 renderer: Quadro M5000/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel C610/X99 series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:8d20 class-ID: 0403
Device-2: NVIDIA GM204 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 10de:0fbb 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 Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: 5020
bus-ID: 00:19.0 chip-ID: 8086:15a0 class-ID: 0200
IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel I210 Gigabit Network vendor: Hewlett-Packard driver: igb v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 05:00.0 chip-ID: 8086:1533 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Device-1: zdata type: zfs status: ONLINE level: mirror-0 raw: size: 1.81 TiB free: 1.07 TiB
allocated: 758 GiB zfs-fs: size: 1.76 TiB free: 1.02 TiB
Components: Online:
1:
2:
Device-2: zvmstore type: zfs status: ONLINE level: linear raw: size: 1.55 TiB free: 953 GiB
allocated: 639 GiB zfs-fs: size: 1.51 TiB free: 903.07 GiB
Components: Online:
1:
Drives:
Local Storage: total: raw: 6.37 TiB usable: 9.63 TiB used: 1.38 TiB (14.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: <unknown> type: SSD serial: <filter> rev: 3B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HUS726020ALE614 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: <unknown> type: HDD rpm: 7200 serial: <filter>
rev: W907 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: HGST (Hitachi) model: HUS726040ALE614 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: <unknown> type: HDD rpm: 7200 serial: <filter>
rev: W907 scheme: GPT
Partition:
ID-1: / raw-size: 372.5 GiB size: 365.59 GiB (98.14%) used: 23.36 GiB (6.4%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 558.75 GiB size: 548.89 GiB (98.24%) used: 2.45 GiB (0.4%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 11 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 33.0 C mobo: N/A gpu: nvidia temp: 51 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 42%
Repos:
Packages: pm: dpkg pkgs: 2683 libs: 1496 tools: apt,apt-get,aptitude,nala 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 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bookworm main non-free
2: deb https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list
1: deb https://download.onlyoffice.com/repo/debian squeeze main
Info:
Processes: 686 Uptime: 1d 1h 47m wakeups: 1 Memory: 125.79 GiB used: 6.28 GiB (5.0%)
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: UEFI
Works:
- Updated all packages
- nvidia driver installer Installed correct nvidia 525 driver for quadro m5000
- nvidia driver installer also auto-installed the necessary cuda packages for nvenc (haven't seen any other distros include nvenc components)
- kdenlive and shotcut both utilize nvenc for gpu-based video rendering
- sound thru nvidia quadro hdmi works
- both network cards work fine
- mpt2sas driver works flawlessly with onboard LSI sata/sas raid controller working solid (experienced lockups under heavy load on freebsd)
- zfs modules load and can import/move/rename/scrub zfs mirrored pools and datasets
- gufw and ufw cli work fine
- enabled all hardening mitigations on kernel cli to see if anything breaks (can't break it yet)
What didn't work:
- couldn't wake up/resume from hibernate. confirmed same TPM bios settings as discussed with another user in beta1 thread so on me to fix
- kde-based ufw interface keeps showing "disconnected from backend" if I attempt to make a change
Nice work MX Team!
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 8:56 am
by Empty Handed
Is there any way to upgrade from 21 to 23?
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 9:47 am
by siamhie
Empty Handed wrote: Sun Jun 18, 2023 8:56 am
Is there any way to upgrade from 21 to 23?
@Empty Handed Read carefully.
Upgrading from MX-21 to MX-23 without reinstalling
https://mxlinux.org/wiki/system/upgradi ... nstalling/
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 9:59 am
by chrispop99
Fluxbox:
Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)
If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.
Chris
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 10:17 am
by Jerry3904
chrispop99 wrote: Sun Jun 18, 2023 9:59 am
Fluxbox:
Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)
If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.
Chris
@Adrian Also: it might be better to generalize as well by using xdg-open instead, and there are a couple of error messages;
Code: Select all
About to execute /usr/bin/featherpad /etc/custom-toolbox/mxfb-settings.list.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password:
QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000
Gtk-Message: 10:09:37.747: Failed to load module "gail"
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 10:21 am
by dolphin_oracle
chrispop99 wrote: Sun Jun 18, 2023 9:59 am
Fluxbox:
Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)
If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.
Chris
the edit button is still using su-to-root instead of pkexec. thanks.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 11:05 am
by fehlix
peter_li wrote: Sun Jun 18, 2023 4:11 am
How to repair this broken pipe?
Code: Select all
/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).
You can repair like this:
Code: Select all
sudo sed -i.orig '2497s/^/#/; 2497aif [[ $(stat -c %d%D /proc) == $(stat -c %d%D /) ]]; then' /sbin/dkms
and check with re-installing the same package
and send a bug-report with the potential fix to debian/upstream
Or
peter_li wrote: Sun Jun 18, 2023 4:11 am
Or could this be ignored?
You can ignore the message, and wait until someone else have fixed it.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 12:04 pm
by fehlix
Jerry3904 wrote: Sun Jun 18, 2023 10:17 am
chrispop99 wrote: Sun Jun 18, 2023 9:59 am
Fluxbox:
Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)
If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.
Chris
@Adrian Also: it might be better to generalize as well by using xdg-open instead, and there are a couple of error messages;
Code: Select all
About to execute /usr/bin/featherpad /etc/custom-toolbox/mxfb-settings.list.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password:
QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000
Gtk-Message: 10:09:37.747: Failed to load module "gail"
No need to open featherpad as root, b/c User get authentication popup-prompt when trying to save anyway.
@Adrian
The Failed to load module message indicates a missing package:
@m_pav
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 12:22 pm
by Jerry3904
@peter_li @fehlix That broken pipe caused totay's update to take up more than 30 mins and run the CPU at 100% on my little AAP 722 until I finally killed it. That is pretty much unacceptable in my book...
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 12:36 pm
by fehlix
BV206 wrote: Sat Jun 17, 2023 8:46 am
fehlix wrote: Fri Jun 16, 2023 8:08 pm
BV206 wrote: Fri Jun 16, 2023 7:37 pm
I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except
en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.
Code: Select all
Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings: LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]
I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.
what would this show:
and
and
I fixed it before I read this reply.
I ran those yesterday but don't remember what was missing.
I do remember that /etc/default/locale only had
LANG=en_US.UTF-8 but it was commented out.
I also had the same thing happen on Debian 12. Both installed with US English as the default language but it couldn't find `en_GB' for some reason. I ran
sudo apt install --reinstall locales and then
sudo dpkg-reconfigure locales on both MX 23 and Debian 12 and it generated the en_US.UTF-8 locale with no errors and without commenting out anything in /etc/default/locale.
Maybe you remember, how you "managed" to get this error. What settings have been selected when booted live
and when you run the installer. Anything changed like timezone and/or locale/language?
Also maybe mention what beta2 ISO you have installed, b/c we have some more than just one.
So anything like this would potential help first to reproduce and maybe also to fix the cause of the issue.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 12:38 pm
by fehlix
Jerry3904 wrote: Sun Jun 18, 2023 12:22 pm
@peter_li @fehlix That broken pipe caused totay's update to take up more than 30 mins and run the CPU at 100% on my little AAP 722 until I finally killed it. That is pretty much unacceptable in my book...
Maybe try the mentioned fix and re-install the *-dkms package involved. Also to proov (or not) the fix changed that not only the message is gone. Otherwise it maybe just the long dkms-build
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 12:50 pm
by fehlix
fehlix wrote: Sun Jun 18, 2023 12:38 pm
Jerry3904 wrote: Sun Jun 18, 2023 12:22 pm
@peter_li @fehlix That broken pipe caused totay's update to take up more than 30 mins and run the CPU at 100% on my little AAP 722 until I finally killed it. That is pretty much unacceptable in my book...
Maybe try the mentioned fix and re-install the *-dkms package involved. Also to proov (or not) the fix changed that not only the message is gone. Otherwise it maybe just the long dkms-build
It takes here about 1 minute to install /reinstall
Code: Select all
sudo bash -c 'time apt reinstall rtl8821ce-dkms'
real 0m59.740s
either with or without the mentioned fix (to get away with the broken pipe message)
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 1:01 pm
by Jerry3904
I meant unacceptable for MX, not just for me.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 1:20 pm
by richb
Whenever I see those updates to those rtl*** files I cringe. knowing that it will take an inordinate amount of time. I always wonder if the system has frozen but experience tells me it has not, Cringe worthy nonetheless.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 1:50 pm
by MXRobo
richb wrote: Sun Jun 18, 2023 1:20 pm
Whenever I see those updates to those rtl*** files I cringe. knowing that it will take an inordinate amount of time. I always wonder if the system has frozen but experience tells me it has not, Cringe worthy nonetheless.
Just a thought, an MX Cleanup project?
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 2:09 pm
by BV206
fehlix wrote: Sun Jun 18, 2023 12:36 pm
Maybe you remember, how you "managed" to get this error. What settings have been selected when booted live
and when you run the installer. Anything changed like timezone and/or locale/language?
Also maybe mention what beta2 ISO you have installed, b/c we have some more than just one.
So anything like this would potential help first to reproduce and maybe also to fix the cause of the issue.
This was the Xfce desktop. I didn't change anything on the live ISO before I installed it. I think the only thing I changed on the installer was US central time zone. Everything else was default US settings.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 3:29 pm
by fehlix
BV206 wrote: Sun Jun 18, 2023 2:09 pm
fehlix wrote: Sun Jun 18, 2023 12:36 pm
Maybe you remember, how you "managed" to get this error. What settings have been selected when booted live
and when you run the installer. Anything changed like timezone and/or locale/language?
Also maybe mention what beta2 ISO you have installed, b/c we have some more than just one.
So anything like this would potential help first to reproduce and maybe also to fix the cause of the issue.
This was the Xfce desktop. I didn't change anything on the live ISO before I installed it. I think the only thing I changed on the installer was US central time zone. Everything else was default US settings.
Thanks. Unfortunately, I cannot reproduce. Kept all defaults.
After install changed timezone to us-central and disabled all locale except en_US.UTF-8. And all is how it should be with no error messages.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 7:12 pm
by siamhie
@Jerry3904 Would it be possible to include cursors with MXFB-Look?
look.png
EDIT including
@Melber
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 8:27 pm
by BV206
fehlix wrote: Sun Jun 18, 2023 3:29 pm
Thanks. Unfortunately, I cannot reproduce. Kept all defaults.
After install changed timezone to us-central and disabled all locale except en_US.UTF-8. And all is how it should be with no error messages.
I will probably break something else and do a new VirtualBox installation. If it happens again I will post it here.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 9:10 pm
by Jerry3904
siamhie wrote: Sun Jun 18, 2023 7:12 pm
@Jerry3904 Would it be possible to include cursors with MXFB-Look?
look.png
That's definitely a question for [.mention]Melber[/mention]. It wouldn't happen though until after Final -- we're smack dab in the middle of feature freeze now.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 18, 2023 10:08 pm
by m_pav
@Melber Jerrys post above ^ with the formatting mention error.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:25 am
by i_ri
Code: Select all
++ Formatting: / (root) ++
Exec #49: mkfs.ext4 -F /dev/sdg1 -L rootMX23
SOut #49: "Creating filesystem with 7665664 4k blocks and 1916928 inodes\nFilesystem UUID: e9e2eccc-c7b0-4b0d-866e-daf9682ae8ba\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, \n\t4096000\n\nAllocating group tables: 0/234\b\b\b\b\b\b\b \b\b\b\b\b\b\bdone \nWriting inode tables: 0/234\b\b\b\b\b\b\b \b\b\b\b\b\b\bdone \nCreating journal (32768 blocks): done\nWriting superblocks and filesystem accounting information: 0/234\b\b\b\b\b\b\b \b\b\b\b\b\b\bdone\n\n"
SErr #49: "mke2fs 1.47.0 (5-Feb-2023)\n"
Exit #49: 0 QProcess::NormalExit QProcess::UnknownError
Exec #50: /sbin/tune2fs -c0 -C0 -i1m /dev/sdg1
SOut #50: "tune2fs 1.47.0 (5-Feb-2023)\nSetting maximal mount count to -1\nSetting current mount count to 0\nSetting interval between checks to 2592000 seconds\n"
Exit #50: 0 QProcess::NormalExit QProcess::UnknownError
++ Preparing subvolumes ++
MkPath(SUCCESS): "/mnt/btrfs-scratch"
Exec #51: mount -o subvolid=5,noatime /dev/sda1 /mnt/btrfs-scratch
SErr #51: "mount: /mnt/btrfs-scratch: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.\n dmesg(1) may have more information after failed mount system call.\n"
Exit #51: 32 QProcess::NormalExit QProcess::UnknownError
-- FAILED Phase 2 - Failed to prepare subvolumes. --
<< void MProcess::halt(bool) >>
<< void MInstall::cleanup(bool) >>
<< void MInstall::setupAutoMount(bool) >>
Bash #52: ps -e | grep 'udisksd'
SOut #52: " 7385 ? 00:00:32 udisksd\n"
Exit #52: 0 QProcess::NormalExit QProcess::UnknownError
Bash #53: grep -El '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d/*
Exit #53: 0 QProcess::NormalExit QProcess::UnknownError
Exec #54: rm -f /run/udev/rules.d/91-mx-udisks-inhibit.rules
Exit #54: 0 QProcess::NormalExit QProcess::UnknownError
Exec #55: udevadm control --reload
Exit #55: 0 QProcess::NormalExit QProcess::UnknownError
Exec #56: partprobe -s
SOut #56: "/dev/sda: msdos partitions 1\n/dev/sdb: msdos partitions 1 2\n/dev/sdg: msdos partitions 1\n"
Exit #56: 0 QProcess::NormalExit QProcess::UnknownError
Sleep #1: 1000ms
Sleep #1: exit 0
hello dolphin_oracle
minstall 23.6.04mx23
i can tell that it recognizes the --oem switch , because it is not switching windows toward the names input then it fails. The regular non --oem install is switching to the names window before the fail hits.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 1:26 am
by siamhie
Jerry3904 wrote: Sun Jun 18, 2023 9:10 pm
siamhie wrote: Sun Jun 18, 2023 7:12 pm
@Jerry3904 Would it be possible to include cursors with MXFB-Look?
look.png
That's definitely a question for [.mention]Melber[/mention]. It wouldn't happen though until after Final -- we're smack dab in the middle of feature freeze now.
OK
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 6:15 am
by keos
Yesterday I had difficulties changing in 'settings manager' > 'system keyboard' the configuration in order to be able to type the appropriate symbols of my language; no matter how much I restarted the system it would not enter/accept the changes, only after a total shutdown ...
But now, from this moment on, the network icon that should be on the panel xfce4 has disappeared (?).
*Note:
There had appeared on the panel some usa-little flags probably indicating the change / language, I removed them ... maybe along with them went the network icon. (?) -- If so, how could it be returned ...?.
Thanks
Screenshot_2023-06-19_06-18-57.png
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 6:51 am
by Melber
Jerry3904 wrote: Sun Jun 18, 2023 9:10 pm
siamhie wrote: Sun Jun 18, 2023 7:12 pm
@Jerry3904 Would it be possible to include cursors with MXFB-Look?
That's definitely a question for Melber. It wouldn't happen though until after Final -- we're smack dab in the middle of feature freeze now.
@siamhie I have been fiddling with mxfb-look to include gkrellm monitor and dock settings. Can look into adding cursors too...but, as Jerry said, it won't be happening before final release.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 7:22 am
by Jerry3904
@keos refresh with: Menu > MX Updater
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 7:43 am
by operadude
Been trying to get Beta-2, Xfce (64-bit) to work with VirtualBox.
Was spotty, but finally got it installed (32GB vdi, 16GB RAM).
Updates, partially, but with a number of errors: "HASH MISMATCH", "pipe broken", "can't get package" (or something to that effect).
I can't post to the Forum from VBox because Firefox keeps crashing.
Unfortunately, also having trouble with copying /var/log/mxpi(.install?) to Host machine, so I can't at this point relay relevant info from VBox environment.
Could use some suggestions about best way to set it up.
Anyway, here's my QSI (Host):
Code: Select all
System: Kernel: 5.10.0-23-amd64 [5.10.179-1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-23-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel, plank wm: xfwm 4.18.0 vt: 7
dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower October 20 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <filter>
Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <filter> UEFI: American Megatrends
v: F5 date: 04/24/2017
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake
family: 6 model-id: 9E (158) stepping: 9 microcode: F0 cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI
driver: radeon v: kernel alternate: amdgpu bus-ID: 01:00.0 chip-ID: 1002:6613
class-ID: 0300
Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: loaded: radeon
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 305 size: 160x90mm (6.3x3.5")
diag: 184mm (7.2")
OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.10.0-23-amd64 LLVM 11.0.1) v: 4.5 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 01:00.1
chip-ID: 1002:aab0 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-23-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: f000
bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives: Local Storage: total: 8.42 TiB used: 3.09 TiB (36.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 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: 1B2QEXE7 temp: 32.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3
scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G size: 111.79 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 61K1 scheme: MBR
ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: CC25 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: A750 scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD5000AADS-00S9B0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A
serial: <filter> rev: 0A01 scheme: GPT
ID-7: /dev/sdf maj-min: 8:80 type: USB vendor: Seagate model: Expansion Desk
size: 3.64 TiB block-size: physical: 4096 B logical: 4096 B type: N/A serial: <filter>
rev: 0739 scheme: MBR
ID-8: /dev/sdl maj-min: 8:176 type: USB model: Storage Device size: 7.5 GiB block-size:
physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-9: /dev/sdm maj-min: 8:192 type: USB model: Mass Storage Device size: 3.69 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-10: /dev/sdn maj-min: 8:208 type: USB model: Storage Device size: 7.4 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: N/A rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-11: /dev/sdo maj-min: 8:224 type: USB vendor: Sabrent model: SABRENT
size: 698.64 GiB block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter>
rev: 0104 scheme: MBR
Partition: ID-1: / raw-size: 20.49 GiB size: 20 GiB (97.61%) used: 12.36 GiB (61.8%) fs: ext4
dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm
ID-2: /boot raw-size: 512 MiB size: 487.2 MiB (95.16%) used: 107.9 MiB (22.2%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-3: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1.3 MiB (0.5%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /home raw-size: 40.02 GiB size: 39.1 GiB (97.69%) used: 8.6 GiB (22.0%) fs: ext4
dev: /dev/dm-1 maj-min: 253:1 mapped: 2.home.fsm
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 21.77 GiB used: 2 MiB (0.0%) priority: -2
dev: /dev/dm-3 maj-min: 253:3 mapped: swap
Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 41.0 C
Fan Speeds (RPM): N/A
Repos: Packages: note: see --pkg apt: 2995 lib: 1459 flatpak: 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 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/mx.list
1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
2: deb http://ftp.linux.org.tr/mx/repo/mx/repo/ bullseye main non-free
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info: Processes: 300 Uptime: 7h 59m wakeups: 3 Memory: 31.3 GiB used: 3.67 GiB (11.7%)
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: UEFI
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 8:54 am
by keos
@ Jerry3904
'mx-updater' is not displayed, i used 'synaptic', reload and apply ... reboot. ...
Now I have a horrendous panel looks like 'fluxbox', although it still saying: xfce4-panel 4.18.2
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 9:18 am
by siamhie
Melber wrote: Mon Jun 19, 2023 6:51 am
Jerry3904 wrote: Sun Jun 18, 2023 9:10 pm
siamhie wrote: Sun Jun 18, 2023 7:12 pm
@Jerry3904 Would it be possible to include cursors with MXFB-Look?
That's definitely a question for Melber. It wouldn't happen though until after Final -- we're smack dab in the middle of feature freeze now.
@siamhie I have been fiddling with mxfb-look to include gkrellm monitor and dock settings. Can look into adding cursors too...but, as Jerry said, it won't be happening before final release.
OK, thanks
@Melber.
One other item that I brought up in beta 1 was certain styles display a sub-menu with more than 34 items as one long entry.
@m_pav @Jerry3904 ?
If you edit that particular style and change the value for menu.bevelWidth: from 1 to 2 then the entries are set into 2 columns.
It would be easier if an entry was added to Overlay so that any style that has the value 1 gets set to 2 automatically.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 10:08 am
by Jerry3904
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:00 pm
by keos
@ Jerry3904
I went to the user manual to where the information about Xfce4 is, over there I found an alternative:
MX Tweak > Panel tab, click "Options" button under Docklike
It's not exactly like that but after a little struggle with the little window that opened ... I could 'apply' ... and in a few seconds the 'default panel' appeared -- I just lost the settings, a minor problem!.
Thanks.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:07 pm
by Gaer Boy
I'm having a problem with booting. It looks like something has gone awry with the install but I've repeated it with the same result. Live USB runs fine, install 64-bit XFCE to SSD, /dev/sdb6, labelled rootMX23, swap to /dev/sdc11. Grub not installed to EFI, updated later on MX-21.
Booting stops early with errors re files not found. Screen photo attached.
bootfail.jpg
One oddity I notice - at the fsck /dev/sda6 message, the
data-3-6 is the label on an empty partition on another disk. On another booting attempt it was
data-2-6, which is an empty partition on a 3rd disk. There seem to be a lot of error messages in the
minstall.log file.
minstall.log
For completeness, QSI.
Code: Select all
System: Kernel: 6.0.0-3.1mx-amd64 [6.0.7-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-3.1mx-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 November 22 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: Gigabyte product: B550I AORUS PRO AX v: N/A serial: <filter>
Mobo: Gigabyte model: B550I AORUS PRO AX v: x.x serial: <filter>
UEFI: American Megatrends v: F11 date: 12/31/2020
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 serial: <filter>
charge: 100% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M185 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Info: 6-Core model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 family: 19 (25) model-id: 50 (80) stepping: 0 microcode: A50000B cache:
L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 93425
Speed: 1700 MHz min/max: 1400/3900 MHz boost: enabled Core speeds (MHz): 1: 1700
2: 1400 3: 1400 4: 1400 5: 1560 6: 1700 7: 1400 8: 2648 9: 1698 10: 1400 11: 1400
12: 1400
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 status: Not affected
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, IBRS_FW, STIBP: always-on,
RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Cezanne vendor: Gigabyte driver: amdgpu v: kernel bus-ID: 07:00.0
chip-ID: 1002:1638 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver:
loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: HDMI-A-1 res: 1920x1080 hz: 60 dpi: 305 size: 160x90mm (6.3x3.5")
diag: 184mm (7.2")
OpenGL: renderer: AMD RENOIR (LLVM 14.0.5 DRM 3.48 6.0.0-3.1mx-amd64)
v: 4.6 Mesa 22.0.5 direct render: Yes
Audio: Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel
bus-ID: 07:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k6.0.0-3.1mx-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel port: f000
bus-ID: 05:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: f000 bus-ID: 06:00.0
chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-8:3
chip-ID: 8087:0029 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: 0:0 sco-mtu: 0:0 link-mode: slave accept
Drives: Local Storage: total: 2.05 TiB used: 254.52 GiB (12.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM005 HD103SJ size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: 00E5 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 1B6Q scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Toshiba model: HDWD110 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: A8J0 scheme: MBR
Partition: ID-1: / raw-size: 30 GiB size: 29.36 GiB (97.87%) used: 14.05 GiB (47.8%) fs: ext4
dev: /dev/sdb5 maj-min: 8:21
ID-2: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 941 KiB (0.9%) fs: vfat
dev: /dev/sdb1 maj-min: 8:17
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda11 maj-min: 8:11
Sensors: System Temperatures: cpu: 38.2 C mobo: 16.8 C gpu: amdgpu temp: 33.0 C
Fan Speeds (RPM): N/A
Repos: Packages: note: see --pkg apt: 2413 lib: 1255 flatpak: 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://free.hands.com/debian/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://free.hands.com/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/mx.list
1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb [arch=amd64] http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 326 Uptime: 11m wakeups: 5 Memory: 15.06 GiB used: 1.8 GiB (11.9%)
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: UEFI
Windows and samba shares
Posted: Mon Jun 19, 2023 12:26 pm
by bbfuller
I was interested to follow this topic:
viewtopic.php?t=75664
about Windows discovery of samba shares and the recommendation to install the "wsdd" package.
I've just done that on a 21.3 installation and in a 23-beta1.
The 21.3 installation came from the test repository and works as far as a cursory test is concerned.
sudo service wsdd status
reveals a running service with no further input required on my behalf.
On the 23-beta1 system after install the service status command results in
wsdd: unrecognized service
Is there something I am missing?
The wsdd file is in /usr/sbin on both machines
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:31 pm
by pbear
operadude wrote: Mon Jun 19, 2023 7:43 am
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:
Frankly, this sounds like a VBox issue, rather than a problem with the beta2 release. Many users (myself included) have had no difficulty installing beta2 in VBox. I do see the broken pipe errors mentioned upthread when updating the Realtek dkms modules ("/usr/bin/dkms: line 2497: echo: write error: broken pipe"), but the VM runs fine otherwise.
Code: Select all
$ inxi -SM
System:
Host: mx-beta2 Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 Desktop: Xfce
v: 4.18.1 Distro: MX-23_beta2_x64 Libretto June 15 2023
Machine:
Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2
serial: <superuser required>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required>
BIOS: innotek GmbH v: VirtualBox date: 12/01/2006
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:35 pm
by operadude
pbear wrote: Mon Jun 19, 2023 12:31 pm
operadude wrote: Mon Jun 19, 2023 7:43 am
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:
Frankly, this sounds like a VBox issue, rather than a problem with the beta2 release. Many users (myself included) have had no difficulty installing beta2 in VBox. I do see the broken pipe errors mentioned upthread when updating the Realtek dkms modules ("/usr/bin/dkms: line 2497: echo: write error: broken pipe"), but the VM runs fine otherwise.
Code: Select all
$ inxi -SM
System:
Host: mx-beta2 Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 Desktop: Xfce
v: 4.18.1 Distro: MX-23_beta2_x64 Libretto June 15 2023
Machine:
Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2
serial: <superuser required>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required>
BIOS: innotek GmbH v: VirtualBox date: 12/01/2006
OK, I really appreciate the feedback.
I'll just keep trying...
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:35 pm
by pbear
Gaer Boy wrote: Mon Jun 19, 2023 12:07 pm
Booting stops early with errors re files not found.
Perhaps you have done this already, but I would try running
fsck manually from a live session
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:38 pm
by fehlix
Gaer Boy wrote: Mon Jun 19, 2023 12:07 pm
I'm having a problem with booting. It looks like something has gone awry with the install but I've repeated it with the same result. Live USB runs fine, install 64-bit XFCE to SSD, /dev/sdb6, labelled rootMX23, swap to /dev/sdc11. Grub not installed to EFI, updated later on MX-21.
Installing without GRUB is possible, But you would get a GRUB menu entry generated on MX-21 with root=/dev/sdXY, where the device name is used which can be problemeatic, b/c when not using root=UUID=xxxx the device name may have changed next boot (b/c assigned differently by the kernel) and the grub menu may not work anymore. Suggest to always install GRUB, even if not used as primary boot menu.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:40 pm
by pbear
operadude wrote: Mon Jun 19, 2023 12:35 pm
I'll just keep trying...
What I would do in your shoes is wait for MX-23 to go final, then if the problem persists open a support thread on the topic.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:40 pm
by dolphin_oracle
You could install grub to the root partition and it won’t effect previously installed grub.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:43 pm
by fehlix
MX Fluxbox:
Latest installer upgrade took away minstall-pkexec ( in favour of recently introduced minstall-launcher)
which makes Installer icon on MX Fluxbox non-functional.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 12:51 pm
by operadude
pbear wrote: Mon Jun 19, 2023 12:40 pm
operadude wrote: Mon Jun 19, 2023 12:35 pm
I'll just keep trying...
What I would do in your shoes is wait for MX-23 to go final, then if the problem persists open a support thread on the topic.
Sounds good.
A bit weird, since I installed Windows (7 & 10) in VirtualBox, with Guest Additions, and Shared Folders between Guest & Host, working with no problems at all.
Anyway, will take your advice, and keep working at it...
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 1:11 pm
by nixon
Just wanted to report that I could successfully install (full disc) and use fluxbox 64 bit edition beta 2 on an old Dell Inspiron 9400 with disc encryption. Didn't notice any obvious problems. Even hibernate works (checked the box on installation) flawlessly. Great job MX Team. :)
Re: Windows and samba shares
Posted: Mon Jun 19, 2023 1:35 pm
by siamhie
bbfuller wrote: Mon Jun 19, 2023 12:26 pm
On the 23-beta1 system after install the service status command results in
@bbfuller This is the MX-23 beta 2 feedback thread. Install the beta 2 version and if you still have issues post your QSI along with it.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 1:49 pm
by dolphin_oracle
fehlix wrote: Mon Jun 19, 2023 12:43 pm
MX Fluxbox:
Latest installer upgrade took away minstall-pkexec ( in favour of recently introduced minstall-launcher)
which makes Installer icon on MX Fluxbox non-functional.
We can either put it back or change the gazelle.lnk file in the mx-fluxbox package.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 1:51 pm
by Jerry3904
I'll change the icon.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 2:30 pm
by operadude
Progress with VirtualBox:
Turned-off my VPN.
Now, got through install, with many errors (see below), but at least, it completed, and now the Updater Box is clear.
Main problem with VirtualBox (Beta2, Xfce, 64-bit) is that anything I try to install (simple screen recorder, gnome-games, redshift, etc.), the installer keeps trying to install rtl8821ce & rtl8821cu.
Here are some examples of the errors:
Code: Select all
/usr/sbin/dkms: write error: Broken pipe
E: sub-process /usr/bin/dpkg returned an error code (1)
Whenever I try to install anything in VirtualBox, it goes through, but also tries to install the rtl8821ce business, and I get errors for both: dkms & dpkg.
The programs DO INSTALL: I now have on VirtualBox all the programs mentioned above.
However, another, and bigger, issue is that Firefox crashes (in VirtualBox) after a very short while. I never have enough time to log-in to the Forum and post my QSI, let alone the issue I'm having.
If there's nothing here regarding Beta-2, I'll lay this to rest, and do as
@pbear suggested, and just wait for the final MX23 to come out.
My instance of MX23-Beta2 on VirtualBox seems that it should work: 32GB vdi, 16GB RAM, full 128MB for display, etc.
Anyway, maybe it's time to move on and keep testing on hardware.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 3:07 pm
by gRegNfo
dolphin_oracle wrote: Fri Jun 16, 2023 6:14 pm
gRegNfo wrote: Fri Jun 16, 2023 5:29 pm
Hi there,
Can I ask a simple question here?
How can I upgrade beta1 from beta2 iso without losing my home and setings?
I didnt want to reinstall from scratch and have to handle configs again.
Thanks
just run your regular updates. I'm not changing the labels for updated systems from beta1 and beta2, but you are getting updates.
once we go final all beta and rc releases will see their version strings bumped.
Well, I ended up installing beta2 from live media for a good surprise!
I started to backup the home folder, but during installation when I was to choose the partition I found an option "delete system files and keep home folder as btrfs"
Worked just fine!
I'm loving this MX+xfce it's my best Linux experience to date!
Keep on guys!
I'll update on my journey though installing discrete nvidia 740M and intel HD4000 and make them switchable.
It will be fun as newer kernels dont fully support it i guess?
We'll see!
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 6:23 pm
by CharlesV
Working on optimizing the MXLiveLogo startup/shutdown animation ... I just found that shutdown animation is no longer working in MX23 Beta.
I have verified this with several different themes:
gerson
greatest
glow
percentage
spinner
spinfinty
MXLiveLogo
and pretty much everything that has a "shutdown" screen ( havent checked them all, some dont.)
Trying now to find out the why, I suspect some different call that debian is making on shutdown, but at this point I can only say - "Its Broken"
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 8:31 pm
by m_pav
operadude wrote: Mon Jun 19, 2023 7:43 am
I can't post to the Forum from VBox because Firefox keeps crashing.
Unfortunately, also having trouble with copying /var/log/mxpi(.install?) to Host machine, so I can't at this point relay relevant info from VBox environment.
Could use some suggestions about best way to set it up.
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:
@operadude
Same thing I found during the builds, FF in VB is an absolute no-go and I haven't been able to find a work-around.
Set up a shared folder from your host to the virtual appliance. Machine Settings > Shared Folders > Add, set permissions and automount, provide a simple name. Keep all things the same for simplicity, we'll go with the name Host. On your daily driver, make a folder called Host and use this folder as the source, the Share name and the mount point in the VM
Boot the VM, create a new folder called Host, open a terminal and issue the command as below.
This is required for running Live, but for an installed VM, you only need the VirtualBox extensions installed in the virtual OS. Personally, I never install the extension pack, I just do as above. When you're all done, you can use this folder to transfer content between the host and the guest.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 9:11 pm
by Jerry3904
@dolphin_oracle I revised the gazelle icon and uploaded it.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 19, 2023 11:41 pm
by pbear
m_pav wrote: Mon Jun 19, 2023 8:31 pm
operadude wrote: Mon Jun 19, 2023 7:43 am
I can't post to the Forum from VBox because Firefox keeps crashing.
@operadude
Same thing I found during the builds, FF in VB is an absolute no-go and I haven't been able to find a work-around.
FWIW, I'm not having any difficulty with Firefox + beta2 + VBox. That's what I'm using to post this reply.
By the way, another (and to my mind simpler) way to port the VM's QSI to the host is copy-and-paste. Just tested and worked for me.
Finally, is there any reason
@operadude shouldn't solve his
Realtek module problem by uninstalling those packages?
As a quick test (using a snapshot), sudo apt remove rtl*-dkms seemed not to cause problems, but as I say, only a quick test.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 1:51 am
by i_ri
hello dolphin_oracle
Compare conky colors in fluxbox and in xfce.
green. red. black?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 2:30 am
by operadude
@m_pav : Thanks for your response!:
m_pav wrote: Mon Jun 19, 2023 8:31 pm
operadude wrote: Mon Jun 19, 2023 7:43 am
I can't post to the Forum from VBox because Firefox keeps crashing.
Unfortunately, also having trouble with copying /var/log/mxpi(.install?) to Host machine, so I can't at this point relay relevant info from VBox environment.
Could use some suggestions about best way to set it up.
I would really like to try Beta-2 on VirtualBox, so if anyone has suggestions:
@operadude
Same thing I found during the builds, FF in VB is an absolute no-go and I haven't been able to find a work-around.
Set up a shared folder from your host to the virtual appliance. Machine Settings > Shared Folders > Add, set permissions and automount, provide a simple name. Keep all things the same for simplicity, we'll go with the name Host. On your daily driver, make a folder called Host and use this folder as the source, the Share name and the mount point in the VM
Boot the VM, create a new folder called Host, open a terminal and issue the command as below.
This is required for running Live, but for an installed VM, you only need the VirtualBox extensions installed in the virtual OS. Personally, I never install the extension pack, I just do as above. When you're all done, you can use this folder to transfer content between the host and the guest.
I had set-up VB with a shared folder, as you outlined, but I left-out the VB hint (in dialog box):
I will try that, and really appreciate the hint!
@pbear: I was trying to use copy-paste for posting my QSI, but Firefox would crash before I could even get logged-in to the Forum! If No Firefox -> No Paste! Anyway...
I DO appreciate your suggestion:
Finally, is there any reason @operadude shouldn't solve his Realtek module problem by uninstalling those packages?
As a quick test (using a snapshot), sudo apt remove rtl*-dkms seemed not to cause problems, but as I say, only a quick test.
I will await the wisdom of my technological elders to approve that before doing so.
I do understand that I can take a snapshot of the current system in VB, and doing so before making any drastic changes (like: remove rtl*-dkms) is what you seem to be referring to. As I said, will await approval from my intellectual/technological elders
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 2:40 am
by pbear
operadude wrote: Tue Jun 20, 2023 2:30 am
@pbear: I was trying to use copy-paste for posting my QSI, but Firefox would crash before I could even get logged-in to the Forum! If No Firefox -> No Paste!
Open QSI in guest VM. Click button: Copy for Forum. Switch to host system. Open thread using Firefox (or other browser)
in the host system. Paste from clipboard.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 3:32 am
by Melber
Just for info
I found a bug in mxfb-look where conky isn't being reset correctly.
Think I see the small code change it needs, will check tonight.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 5:44 am
by operadude
pbear wrote: Tue Jun 20, 2023 2:40 am
operadude wrote: Tue Jun 20, 2023 2:30 am
@pbear: I was trying to use copy-paste for posting my QSI, but Firefox would crash before I could even get logged-in to the Forum! If No Firefox -> No Paste!
Open QSI in guest VM. Click button: Copy for Forum. Switch to host system. Open thread using Firefox (or other browser)
in the host system. Paste from clipboard.
Ahhh....So Simple!
Once you know what to do!
(Didn't think that I could switch back & forth just from the clipboard)
Will Try.
Thanks!
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 5:59 am
by operadude
Thanks
@pbear !
Here's my QSI from my VB instance:
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required>
Chassis: Oracle Corporation type: 1 serial: <superuser required>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> BIOS: innotek GmbH
v: VirtualBox date: 12/01/2006
CPU:
Info: model: Intel Core i3-7100 bits: 64 type: MCP arch: Kaby Lake gen: core 7 level: v2
built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9 microcode: N/A
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB desc: 2x256 KiB L3: 6 MiB desc: 2x3 MiB
Speed (MHz): avg: 3912 min/max: N/A cores: 1: 3912 2: 3912 bogomips: 15648
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: Virtual-1
empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, Virtual-8
bus-ID: 00:02.0 chip-ID: 15ad:0405 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: vmware
unloaded: fbdev,modesetting,vesa dri: vmwgfx gpu: vmwgfx display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1002 s-dpi: 96 s-size: 508x265mm (20.00x10.43") s-diag: 573mm (22.56")
Monitor-1: Virtual-1 mapped: Virtual1 res: 1920x1002 hz: 60 size: N/A modes: max: 1920x1002
min: 640x480
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: SVGA3D; build: RELEASE; LLVM; direct-render: Yes
Audio:
Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0
chip-ID: 8086:2415 class-ID: 0401
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 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 bus-ID: 00:03.0
chip-ID: 8086:100e class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A
modules: i2c_piix4 port: N/A bus-ID: 00:07.0 chip-ID: 8086:7113 class-ID: 0680
Drives:
Local Storage: total: 32 GiB used: 10.99 GiB (34.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK size: 32 GiB block-size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1.0 scheme: MBR
Partition:
ID-1: / raw-size: 31.99 GiB size: 31.32 GiB (97.89%) used: 10.99 GiB (35.1%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
Packages: pm: dpkg pkgs: 2086 libs: 1044 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://ftp.linux.org.tr/mx/repo/mx/repo/ bookworm main non-free
Info:
Processes: 198 Uptime: 0m wakeups: 31 Memory: 15.62 GiB used: 1.01 GiB (6.5%) 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)
Will try some of the other tweaks mentioned, as well as installing, & using FF...
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 6:04 am
by operadude
Just tried updating (1 package-- rtl8821cu). Here's the output:
Code: Select all
full upgrade
apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
rtl8821cu-dkms (5.12.0+git20230215-1~mx23+2 => 5.12.0+git20230215-1~mx23+3)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 12.0 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.linux.org.tr/mx/repo/mx/repo bookworm/main amd64 rtl8821cu-dkms all 5.12.0+git20230215-1~mx23+3 [12.0 MB]
Fetched 12.0 MB in 4s (2,708 kB/s)
(Reading database ... 287990 files and directories currently installed.)
Preparing to unpack .../rtl8821cu-dkms_5.12.0+git20230215-1~mx23+3_all.deb ...
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Unpacking rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) over (5.12.0+git20230215-1~mx23+2) ...
Setting up rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) ...
Removing old rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Deleting module rtl8821ce-5.5.2.1+git20230504 completely from the DKMS tree.
Loading new rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Deprecated feature: MODULES_CONF (/usr/src/rtl8821ce-5.5.2.1+git20230504/dkms.conf)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/build/make.log for more information.
dpkg: error processing package rtl8821ce-dkms (--configure):
installed rtl8821ce-dkms package post-installation script subprocess returned error exit status 10
Setting up rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) ...
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821cu/5.12.0/build/make.log for more information.
dpkg: error processing package rtl8821cu-dkms (--configure):
installed rtl8821cu-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
rtl8821ce-dkms
rtl8821cu-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
full upgrade complete (or was canceled)
this terminal window can now be closed
Press any key to close...
HTH
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 8:38 am
by operadude
@m_pav : Thanks for this:
Set up a shared folder from your host to the virtual appliance. Machine Settings > Shared Folders > Add, set permissions and automount, provide a simple name. Keep all things the same for simplicity, we'll go with the name Host. On your daily driver, make a folder called Host and use this folder as the source, the Share name and the mount point in the VM
Boot the VM, create a new folder called Host, open a terminal and issue the command as below.
Can confirm that VB using shared folder is working for MX23-BETA2(XFCE, x64). Here's a screenshot of my VB settings (right-hand side), with VB using a shared folder (lower middle portion), and the Host machine showing the 2 files in VB in Host's directory (upper left portion of the screenshot), called "VB_HOST":
2023-06-20 VirtualBox Shared_Folders Setup.jpg
Unfortunately, FF crashes every time, about 3 seconds in!
Any recommendations about using a different browser in the VM(VB)?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 8:44 am
by operadude
@m_pav :
Forgot to mention that I am just using the following, inside VB, from a Terminal, every VB session:
Code: Select all
$ sudo mount -t vboxsf VB_HOST ~/VB_HOST
I need to do this each session of the VB. It's not automatic. I guess that's what you meant:
This is required for running Live, but for an installed VM, you only need the VirtualBox extensions installed in the virtual OS. Personally, I never install the extension pack, I just do as above. When you're all done, you can use this folder to transfer content between the host and the guest.
Yeah, easy enough to just use the Terminal one-liner, and not even worry about the "extensions" (Guest Additions?).
Again, thanks for that. Working like a charm
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 8:44 am
by Jerry3904
Melber wrote: Tue Jun 20, 2023 3:32 am
Just for info
I found a bug in mxfb-look where conky isn't being reset correctly.
Think I see the small code change it needs, will check tonight.
In the same vein, I found that the MX-Comfort conky configs need some attention (e.g., battery not reporting)--will look tonight.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 9:56 am
by ceeslans
Yesterday I happened to see
siamhie's referral to a potential scenario to
upgrade MX21 to MX23.
Out of curiosity, I installed a latest snapshot of my MX21 system to a usb-3 drive (This actually is a skinny fluxbox install on a stripped-down MX21 setup, i.e with all xfce4-elements taken out) .
I then followed the instructions that @adrian provided in the wiki - just to see how this would work out.
During preparation, the command to write 'non-free-firmware' to the debian list failed, so I edited the list file manually.
Note that my 13y old laptop doesn't need the rtl8821* firmware, and as such the rtml8821*-dkms packages were already absent on my MX21 setup; as a result, I was spared from the potential dkms 'broken pipe' error.
The upgrade proces was smooth as silk, and finished without any real errors. It did take some time though, probably since I had over 2000 packages installed - and most likely the used usb drive didn't allow fast processing either.
I'm really happy with the endresult, I got a fully working MX23 setup, which hardly needed any adjustments. Had some problems with 'QSI-mx' throwing an error - and sofar I only needed to adjust a few exec paths to MX-tools in my fluxbox' rootmenu. Afterwards, I also installed the pipewire meta-package, which required some changes to be made to a few tint2-executor scripts. Surely, I will find some other small issues that would need adjustment, but overall the result is very satisfactory.
That said, I want to emphasize that this upgrade action may well be
unsuccesful on other installations. The only way to check this, would be to test it on a snapshot, installed on a separate drive. And please take @adrian's warning at heart: before doing system-wide changes
make a backup of your data and system.
About the wallpaper in the screenshot: I haven't a clue who portrayed Dolphin_Oracle so well... Oh well...
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 9:58 am
by Melber
Jerry3904 wrote: Tue Jun 20, 2023 8:44 am
In the same vein, I found that the MX-Comfort conky configs need some attention (e.g., battery not reporting)--will look tonight.
Presume you mean MX-Comfort-Sysinfo.
Perhaps it needs the BAT0 / BAT1 check that was added in the MX-Cowon conkys?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 10:13 am
by Jerry3904
Yup, and temp is not reporting either (running live, maybe sensors missing?).
There's a spacing problem somewhere as well, haven't looked closely yet.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 10:43 am
by operadude
@ceeslans Thanks for your recent post about upgrading to MX23:
viewtopic.php?p=730037#p730037
And, thanks
@Adrian for your article about MX21 -> MX23 upgrade:
https://mxlinux.org/wiki/system/upgradi ... nstalling/
Definitely will try it out on an MX21 system (old laptop) that doesn't have any data on it.
This reminds me that there's SO much more to learn, just in the MX Wiki alone
Another amazing source to review, before jumping into the Forum to find answers.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 11:21 am
by OlafD
xfce 64-bit
I installed MX on my macbook and took a snapshot after my custom setup and created a live boot stick from it using MX Live USB.
Here is the QSI of my host:
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Apple product: MacBookPro11,1 v: 1.0 serial: <superuser required> Chassis:
type: 10 v: Mac-189A3D4F975D5FFC serial: <superuser required>
Mobo: Apple model: Mac-189A3D4F975D5FFC v: MacBookPro11,1 serial: <superuser required>
UEFI: Apple v: 431.0.0.0.0 date: 02/22/2021
Battery:
ID-1: BAT0 charge: 57.8 Wh (100.2%) condition: 57.7/71.5 Wh (80.7%) volts: 12.4 min: 11.3
model: SMP bq20z451 type: Li-ion serial: N/A status: discharging cycles: 1005
CPU:
Info: model: Intel Core i5-4278U bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x45 (69) stepping: 1
microcode: 0x26
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1036 high: 1099 min/max: 800/3100 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1056 2: 1034 3: 958 4: 1099 bogomips: 20800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics vendor: Apple driver: i915 v: kernel
arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0a2e class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 445x278mm (17.52x10.94") s-diag: 525mm (20.66")
Monitor-1: eDP-1 model: Apple Color LCD built: 2013 res: 1680x1050 hz: 60 dpi: 149 gamma: 1.2
size: 286x179mm (11.26x7.05") diag: 337mm (13.3") ratio: 16:10 modes: 2560x1600
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Iris Graphics 5100 (HSW GT3)
direct-render: Yes
Audio:
Device-1: Intel Haswell-ULT HD Audio vendor: Apple driver: snd_hda_intel v: kernel
bus-ID: 00:03.0 chip-ID: 8086:0a0c class-ID: 0403
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:9c20 class-ID: 0403
Device-3: Broadcom 720p FaceTime HD Camera driver: N/A pcie: speed: Unknown lanes: 63 link-max:
gen: 6 speed: 64 GT/s bus-ID: 02:00.0 chip-ID: 14e4:1570 class-ID: 0480
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: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple driver: wl v: kernel
modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:43a0
class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Apple Bluetooth Host Controller type: USB driver: btusb v: 0.8 bus-ID: 1-3.3:6
chip-ID: 05ac:8289 class-ID: fe01
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 4196 hci-v: 4.0 rev: 2467
Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 113 GiB used: 29.25 GiB (25.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Apple model: SSD SD0128F size: 113 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 321 scheme: GPT
Partition:
ID-1: / raw-size: 37.55 GiB size: 36.67 GiB (97.64%) used: 29.25 GiB (79.8%) fs: ext4
dev: /dev/sda4 maj-min: 8:4
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2266 libs: 1154 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://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 231 Uptime: 2m wakeups: 3 Memory: 7.67 GiB used: 1.21 GiB (15.8%) 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: UEFI
On another PC I had an SSD that already had a btrfs partition. This SSD I have completely erased in live boot with gparted for now.
During the installation with "sudo minstall" I was always offered the manual setup of the drives, never the automatic. No matter what I selected, the installation aborted at about 11% (formatting /root or similar) and reported: No subvolumes could be created.
Here is my client system:
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
resume=UUID=<filter> resume_offset=16439296
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: ASRock model: B450M Pro4 R2.0 serial: <superuser required>
UEFI: American Megatrends v: P5.40 date: 03/01/2022
CPU:
Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80)
stepping: 0 microcode: 0xA50000C
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1559 high: 3464 min/max: 1400/4672 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 1416 6: 3464
7: 1400 8: 1400 9: 1400 10: 1400 11: 1400 12: 1576 13: 1400 14: 1700 15: 1400 16: 1400
bogomips: 121599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel
arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1 bus-ID: 07:00.0
chip-ID: 1002:1638 class-ID: 0300 temp: 33.0 C
Device-2: Logitech C920 HD Pro Webcam type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-2:3
chip-ID: 046d:0892 class-ID: 0102 serial: <filter>
Device-3: MacroSilicon usb video type: USB driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
bus-ID: 5-1:2 chip-ID: 534d:2109 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 4480x1643 s-dpi: 96 s-size: 1185x435mm (46.65x17.13") s-diag: 1262mm (49.7")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: bottom-r model: LG (GoldStar) E2242 serial: <filter>
built: 2012 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55")
diag: 547mm (21.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-2 mapped: HDMI-A-1 pos: primary,top-left model: BenQ EW3270ZL
serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 92 gamma: 1.2
size: 709x399mm (27.91x15.71") diag: 814mm (32") ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie:
bus-ID: 3-1:2 chip-ID: 0d8c:0166 gen: 3 speed: 8 GT/s class-ID: 0300 lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 07:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 07:00.6 chip-ID: 1022:15e3
class-ID: 0403
Device-3: C-Media USB PnP Sound Device type: USB driver: hid-generic,snd-usb-audio,usbhid
Device-4: Logitech C920 HD Pro Webcam type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-2:3
chip-ID: 046d:0892 class-ID: 0102 serial: <filter>
Device-5: MacroSilicon usb video type: USB driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
bus-ID: 5-1:2 chip-ID: 534d:2109 class-ID: 0300
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: ASRock driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.13 TiB used: 43.05 GiB (3.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QEXM7 temp: 30.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 04RL scheme: GPT
Partition:
ID-1: / raw-size: 111.33 GiB size: 109.02 GiB (97.93%) used: 43.05 GiB (39.5%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 36.72 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 39.1 C mobo: N/A gpu: amdgpu temp: 33.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2056 libs: 1041 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://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
Info:
Processes: 330 Uptime: 10m wakeups: 1 Memory: 30.72 GiB used: 2.21 GiB (7.2%) 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: UEFI
This phenomenon happened with xfce, as well as with KDE.
A reinstallation via the downloadable ISOs from you worked smoothly.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 12:51 pm
by fehlix
OlafD wrote: Tue Jun 20, 2023 11:21 am
On another PC I had an SSD that already had a btrfs partition. This SSD I have completely erased in live boot with gparted for now.
During the installation with "sudo minstall" I was always offered the manual setup of the drives, never the automatic. No matter what I selected, the installation aborted at about 11% (formatting /root or similar) and reported: No subvolumes could be created.
This phenomenon happened with xfce, as well as with KDE.
A reinstallation via the downloadable ISOs from you worked smoothly.
You may have update to latest version of mx-installer, where you missed to mention which version that would be.
The version released yesterday (?) appears to have subvolume-btrfs issue and a bug-fixed version is worked on
or already on the way to the repos.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 1:12 pm
by bridgesense
I have to say, I've hopped a lot of distros, but this is my first stint with Xfce. I've been on the beta now for two weeks, using the platform professionally (12+ hours a day). I have had no problems with this at all.
I did have to flip it over to systemd to work with some init pods, but overall, the presentation is impressive.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 1:18 pm
by Gerson
In the Touch Panel preferences for laptops, there is no option to disable when an external mouse is connected.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 1:56 pm
by OlafD
fehlix wrote: Tue Jun 20, 2023 12:51 pm
OlafD wrote: Tue Jun 20, 2023 11:21 am
On another PC I had an SSD that already had a btrfs partition. This SSD I have completely erased in live boot with gparted for now.
During the installation with "sudo minstall" I was always offered the manual setup of the drives, never the automatic. No matter what I selected, the installation aborted at about 11% (formatting /root or similar) and reported: No subvolumes could be created.
This phenomenon happened with xfce, as well as with KDE.
A reinstallation via the downloadable ISOs from you worked smoothly.
You may have update to latest version of mx-installer, where you missed to mention which version that would be.
The version released yesterday (?) appears to have subvolume-btrfs issue and a bug-fixed version is worked on
or already on the way to the repos.
OK, thanks.
Is it enough to make the Live-USB persistence and update it? Or must update the host system and make a new snapshot and USB?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 2:05 pm
by Gerson
Notification for night colour starts much earlier than scheduled.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 4:43 pm
by gRegNfo
OlafD wrote: Tue Jun 20, 2023 11:21 am
xfce 64-bit
I installed MX on my macbook and took a snapshot after my custom setup and created a live boot stick from it using MX Live USB.
On another PC I had an SSD that already had a btrfs partition. This SSD I have completely erased in live boot with gparted for now.
During the installation with "sudo minstall" I was always offered the manual setup of the drives, never the automatic. No matter what I selected, the installation aborted at about 11% (formatting /root or similar) and reported: No subvolumes could be created.
This phenomenon happened with xfce, as well as with KDE.
A reinstallation via the downloadable ISOs from you worked smoothly.
I also tried last night to use the beta2 snapshot feature and it didn't work with the same result during installation from iso/usb
I tried sudo, not using -E option, changing to root... no use.
"No subvolumes could be created." error at 11% formating partition (btrfs) on minstall gui.
I ended up copying the home folder and changing permissions to $user home folder, so it could boot using config files from last snapshot over a fresh beta2 installation.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 5:02 pm
by fehlix
OlafD wrote: Tue Jun 20, 2023 1:56 pm
fehlix wrote: Tue Jun 20, 2023 12:51 pm
OlafD wrote: Tue Jun 20, 2023 11:21 am
On another PC I had an SSD that already had a btrfs partition. This SSD I have completely erased in live boot with gparted for now.
During the installation with "sudo minstall" I was always offered the manual setup of the drives, never the automatic. No matter what I selected, the installation aborted at about 11% (formatting /root or similar) and reported: No subvolumes could be created.
This phenomenon happened with xfce, as well as with KDE.
A reinstallation via the downloadable ISOs from you worked smoothly.
You may have update to latest version of mx-installer, where you missed to mention which version that would be.
The version released yesterday (?) appears to have subvolume-btrfs issue and a bug-fixed version is worked on
or already on the way to the repos.
OK, thanks.
Is it enough to make the Live-USB persistence and update it? Or must update the host system and make a new snapshot and USB?
You would use the updated mx-installer within the running live system, regardless whether persistence is used or running read-only e.g from ISO. The installer takes what the live system is running to install onto target drive(s).
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 20, 2023 5:20 pm
by fehlix
gRegNfo wrote: Tue Jun 20, 2023 4:43 pm
OlafD wrote: Tue Jun 20, 2023 11:21 am
xfce 64-bit
I installed MX on my macbook and took a snapshot after my custom setup and created a live boot stick from it using MX Live USB.
On another PC I had an SSD that already had a btrfs partition. This SSD I have completely erased in live boot with gparted for now.
During the installation with "sudo minstall" I was always offered the manual setup of the drives, never the automatic. No matter what I selected, the installation aborted at about 11% (formatting /root or similar) and reported: No subvolumes could be created.
This phenomenon happened with xfce, as well as with KDE.
A reinstallation via the downloadable ISOs from you worked smoothly.
I also tried last night to use the beta2 snapshot feature and it didn't work with the same result during installation from iso/usb
I tried sudo, not using -E option, changing to root... no use.
"No subvolumes could be created." error at 11% formating partition (btrfs) on minstall gui.
I ended up copying the home folder and changing permissions to $user home folder, so it could boot using config files from last snapshot over a fresh beta2 installation.
The latest version 23.6.05mx23, which shsosuld be available by now on the repo's and potentially on the mirrored -repos, is suppost to have fixed the "cannot create subvolume" issue.
The recommended use on the terminal command line would be to start the installer
as normal user with
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 12:43 am
by OlafD
@fehlix
OK, thanks a lot
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 5:53 am
by i_ri
hello dolphin_oracle
Sample internet radio monitor conky /MX-Bridouz-strawberry/
.conky/MX-Bridouz-strawb/MX-bridouz_mod-arial-strawb
minimum_width = 220, minimum_height = 300,
maximum_width = 256,
a change from -clem., mediaplayer.py to strawberry sample
looking at radio strawberry; artist, title, coverAlbum.
Code: Select all
${font Arial:bold:size=10}${color ivory}MUSIC ${color 202F50}${hr 2}
##
##strawberry using mediaplayer.py script; orig ${font Open Sans:size=9}
${if_existing ./mediaplayer.py}${if_match "${execi 10 python3 ./mediaplayer.py strawberry -i}"=="yes"}
${color ivory}${font Open Sans:size=9}${execpi 4 python3 ./mediaplayer.py strawberry -tamr -w 45}
${color grey68}${font Open Sans:size=9}${execpi 4 python3 ./mediaplayer.py strawberry -lr -w 45}
${if_match "${execi 4 python3 ./mediaplayer.py strawberry -p}"=="Unknown"}\
Progress: ${alignr}Unknown
${else}
Progress:
${color 88999F}${execibar 4 python3 ./mediaplayer.py strawberry -p}${endif}
${execi 13 python3 ./mediaplayer.py strawberry -c /tmp/cover.jpg}
${image /tmp/cover.jpg -p 56,550 -s 76x75 -n}
${else}${color grey68}${font Open Sans:size=9}strawberry Not Running\
${endif}${endif}
$font${color ivory}
$conky_version
conky
(paste into /MX-TeejeeTech/Process Panel change minimum_width = 220, change y of image -p 56,394 .),
Paste direct into conky /MX-antiX17 looks like,
MX-bridouz_mod-arial-strawb.png
Process Panel-strawb.png
MX-antiX17-strawb.png
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 6:17 am
by kc1di
using KDE version. Can not get syanptics touchpad driver to work on this version. I prefer it to libinput as it allows touchpad to be disabled when mouse is plugged in. I can use touchpad indicator an do similar but prefer synaptics.
System;
Code: Select all
inxi -Fxxzr
System:
Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 dm: SDDM
Distro: MX-23_KDE_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux
12 (bookworm)
Machine:
Type: Laptop System: LENOVO product: 20BV000AUS v: ThinkPad T450
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20BV000AUS v: SDK0E50510 WIN
serial: <superuser required> UEFI-[Legacy]: LENOVO v: JBET71WW (1.35 )
date: 09/14/2018
Battery:
ID-1: BAT0 charge: 16.5 Wh (95.4%) condition: 17.3/23.2 Wh (74.4%)
volts: 12.2 min: 11.1 model: SANYO 45N1773 serial: <filter>
status: not charging
ID-2: BAT1 charge: 13.4 Wh (100.0%) condition: 13.4/23.2 Wh (57.8%)
volts: 12.4 min: 11.1 model: SANYO 45N1775 serial: <filter> status: full
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
Info: dual core model: Intel Core i5-5300U bits: 64 type: MT MCP
arch: Broadwell rev: 4 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 892 high: 907 min/max: 500/2900 cores: 1: 852 2: 903
3: 906 4: 907 bogomips: 18358
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel
arch: Gen-8 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:1616
Device-2: Bison Integrated Camera type: USB driver: uvcvideo bus-ID: 2-8:5
chip-ID: 5986:0366
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1482 res: 1600x900 dpi: 132
diag: 355mm (14")
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 5500 (BDW
GT2) direct-render: Yes
Audio:
Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel
v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0
API: ALSA v: k6.1.0-9-amd64 status: kernel-api
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
Network:
Device-1: Intel Ethernet I218-LM vendor: Lenovo driver: e1000e v: kernel
port: 3080 bus-ID: 00:19.0 chip-ID: 8086:15a2
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel pcie:
speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:095b
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 17.14 GiB (7.2%)
ID-1: /dev/sda vendor: LITE-ON model: LCH-256V2S size: 238.47 GiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 27.33 GiB used: 12 GiB (43.9%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 205.23 GiB used: 5.14 GiB (2.5%) fs: ext4 dev: /dev/sda6
Swap:
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 46.0 C pch: 45.5 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: pm: dpkg pkgs: 2503
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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
Processes: 207 Uptime: 9m Memory: 7.46 GiB used: 2.02 GiB (27.0%)
Init: SysVinit v: 3.06 runlevel: 5 default: graphical Compilers: gcc: 12
Shell: Bash v: 5.2.15 running-in: konsole inxi: 3.3.26
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 6:25 am
by Jerry3904
Not clear what you mean with not being able to get it to work, but dId you already try the toggle in MX Tweak > Other tab?
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 6:50 am
by kc1di
Hi Jerry,
Thanks for the reply. I simply mean the under system setting in KDE Hardware, Input devices, touchpad it will not give the option for disabling touchpad when mouse is plugged in.
Normally with some other distros if I install synaptics touchpad driver from repositories and reboot it then allow this function, but on Beta 2 it does not change anything and it's not offered.
I don't see anything on my install in tweaks that seems to do that either. I tried the setting use intel drivers but all that did was cause my screen to flash. In any event touchpad-indicator works.
But there should be a way to get synaptics working also. I understand this may be a KDE problem and no MX.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 7:35 am
by Jerry3904
Got it, thanks. No help from me for KDE, sorry, but others on the Forum know it well and may be able to help.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 9:58 am
by keos
trying to copy to the Ventoy:
1 the snapshot finished very fast ... (?)
2 when copy to the ventoy and openned the app to start with the system in ventoy:
Fatal Error:
Could not find file antiX/linufs
Edit:
Instead now I copy it to a USB and it comes out correctly, so the snapshot did its job well, the problem is when copying it to ventoy.
Failure to format EFI-Partition
Posted: Wed Jun 21, 2023 10:39 am
by Frankarnold
A very simple setup: Just one 64GB eMMC, regular install using the entire disk:
failed to format efi-partition, formatting stops at 11% or 12%
MX-21 ahs: tried N times, never worked, same result with custom install, WHEREAS:
all others did full install with no problem: Win10, Win11, Fedora37, Fedora38, Ubuntu Mint etc.
MX-23-2 beta installed - finally - on 3rd attempt.
Does this make any sense ?
-----------------------------------------------------------------------------------------------------------------------------------------
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: TREKSTOR product: Surfbook A13B v: N/A serial: <superuser required>
Mobo: TS_inet model: Geminilake_PN5_V01 serial: <superuser required> UEFI: American Megatrends
v: BIOS_V1.2.4 date: 07/23/2018
Battery:
ID-1: BAT0 charge: 33.2 Wh (94.9%) condition: 35.0/35.0 Wh (100.0%) volts: 7.6 min: N/A
model: GLK MRD Li-ion Battery type: Li-ion serial: <filter> status: discharging
CPU:
Info: model: Intel Pentium Silver N5000 bits: 64 type: MCP arch: Goldmont Plus level: v2
built: 2017 process: Intel 14nm family: 6 model-id: 0x7A (122) stepping: 1 microcode: 0x3E
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 224 KiB desc: d-4x24 KiB; i-4x32 KiB
L2: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 964 high: 1000 min/max: 800/2700 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1000 2: 1000 3: 900 4: 959 bogomips: 8755
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel GeminiLake [UHD Graphics 605] driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:3184 class-ID: 0300
Device-2: Alcor Micro USB 2.0 Web Camera type: USB driver: uvcvideo bus-ID: 1-7:5
chip-ID: 058f:5608 class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: Najing CEC Panda LC133LF4L01 built: 2015 res: 1920x1080 hz: 60 dpi: 166
gamma: 1.2 size: 294x165mm (11.57x6.5") diag: 337mm (13.3") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 605 (GLK 3) direct-render: Yes
Audio:
Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: Realtek
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_apl bus-ID: 00:0e.0
chip-ID: 8086:3198 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 Wireless 3165 driver: iwlwifi v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:3165 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
chip-ID: 8087:0a2a class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 1000 hci-v: 4.2 rev: 1000
Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 57.62 GiB used: 8.71 GiB (15.1%)
ID-1: /dev/mmcblk0 maj-min: 179:0 model: NCard size: 57.62 GiB block-size: physical: 512 B
logical: 512 B type: SSD serial: <filter> rev: 0x8 scheme: GPT
SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
ID-1: / raw-size: 57.36 GiB size: 56.16 GiB (97.91%) used: 8.71 GiB (15.5%) fs: ext4
dev: /dev/mmcblk0p2 maj-min: 179:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/mmcblk0p1 maj-min: 179:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2056 libs: 1041 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://ftp.halifax.rwth-aachen.de/mxlin ... s/mx/repo/ bookworm main non-free
Info:
Processes: 214 Uptime: 2m wakeups: 2 Memory: 3.66 GiB used: 1.02 GiB (27.8%) 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: UEFI
--------------------------------------------------------------------------------------------------------------------------------------------
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 11:06 am
by siamhie
keos wrote: Wed Jun 21, 2023 9:58 am
trying to copy to the Ventoy:
1 the snapshot finished very fast ... (?)
2 when copy to the ventoy and openned the app to start with the system in ventoy:
Fatal Error:
Could not find file antiX/linufs
Edit:
Instead now I copy it to a USB and it comes out correctly, so the snapshot did its job well, the problem is when copying it to ventoy.
@keos
You will need to download the ventoy-linux patch.
Once downloaded and unarchived open terminal in folder of unzipped archive and run
Code: Select all
sudo sh Ventoy2Disk.sh -u /dev/sdX
where X is the target USB.
The -u switch is for upgrade...it doesn't touch the partition of ISOs.
https://github.com/ventoy/Ventoy/action ... 4976511049 (account required)
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 11:33 am
by user-green
Dear Developers,
I think that the bug below may still be confirmed in Beta 2. The icon for the installed package of Firefox is concealed.
The window should be displayed as below:
Best regards
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 12:22 pm
by fehlix
user-green wrote: Wed Jun 21, 2023 11:33 am
Dear Developers,
I think that the bug below may still be confirmed in Beta 2. The icon for the installed package of Firefox is concealed.
You may want to give more details:
"MX Package Installer" latest version 23.6 displays here correctly:
with system locale in English:
mxpi_en.jpg
and also in Japanese:
mxpi_ja.jpg
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 12:37 pm
by megaherz33
Hi!
I tried to install MX Linux 23 on the main PC, the same "Critical error"
MX Linux 21.3 installs without problems.
P.S.I will wait for the update 21.3 to 23.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 1:16 pm
by siamhie
megaherz33 wrote: Wed Jun 21, 2023 12:37 pm
Hi!
I tried to install MX Linux 23 on the main PC, the same "Critical error"
MX Linux 21.3 installs without problems.
P.S.I will wait for the update 21.3 to 23.
@megaherz33 If you are trying to install using Ventoy, follow my steps I posted on the previous page.
viewtopic.php?p=730181#p730181
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 1:27 pm
by siamhie
fehlix wrote: Wed Jun 21, 2023 12:22 pm
user-green wrote: Wed Jun 21, 2023 11:33 am
Dear Developers,
I think that the bug below may still be confirmed in Beta 2. The icon for the installed package of Firefox is concealed.
You may want to give more details:
"MX Package Installer" latest version 23.6 displays here correctly:
with system locale in English:mxpi_en.jpg
and also in Japanese:mxpi_ja.jpg
@fehlix Same problem. I have xmms and librewolf installed but popular apps doesn't show it until I start typing in at least two characters into the search field. MXPI version 23.6
mxpi.png
mxpi2.png
mxpi3.png
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 1:30 pm
by megaherz33
siamhie wrote: Wed Jun 21, 2023 1:16 pm
megaherz33 wrote: Wed Jun 21, 2023 12:37 pm
Hi!
I tried to install MX Linux 23 on the main PC, the same "Critical error"
MX Linux 21.3 installs without problems.
P.S.I will wait for the update 21.3 to 23.
@megaherz33 If you are trying to install using Ventoy, follow my steps I posted on the previous page.
viewtopic.php?p=730181#p730181
I updated the flash drive using Ventoy-Linux. Same error.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 1:35 pm
by jasalt
iPhone USB network tethering seems to work only when booting using systemd.
Testing with fresh MX-23 Beta 2 installation and `libimobiledevice-utils` package installed. The `idevicepair pair` command doesn't initiate connection with USB connected iPhone (SE 2020) and simply returns "No device found." without any reaction on the phone.
USB network tethering and idevice*-commands are working after booting with systemd. When connecting USB cable the phone asks if the computer is to be trusted after which computer gets connected through it's mobile network as it does with stock Debian (or Mac).
File management on iOS / iDeviceMounter remains broken regardless of init system, but noted from other threads that it's a known issue.
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
resume=UUID=<filter> resume_offset=2368768
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: LENOVO product: 20L6S7PC00 v: ThinkPad T480 serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20L6S7PC00 v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO
v: N24ET72W (1.47 ) date: 01/03/2023
Battery:
ID-1: BAT0 charge: 16.6 Wh (79.4%) condition: 20.9/21.3 Wh (97.9%) volts: 12.4 min: 11.4
model: LGC 421 type: Li-poly serial: <filter> status: not charging cycles: 29
ID-2: BAT1 charge: 13.0 Wh (79.3%) condition: 16.4/23.9 Wh (68.3%) volts: 12.7 min: 11.4
model: LGC 01AV490 type: Li-poly serial: <filter> status: charging cycles: 528
CPU:
Info: model: Intel Core i5-8350U bits: 64 type: MT MCP arch: Coffee Lake gen: core 8 level: v3
note: check built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 0xA (10)
microcode: 0xF2
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled 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: 1625 high: 1900 min/max: 400/3600 scaling: driver: intel_pstate
governor: powersave cores: 1: 1900 2: 1900 3: 1900 4: 800 5: 1900 6: 800 7: 1900 8: 1900
bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300
Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:3
chip-ID: 13d3:56a6 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: InfoVision Optronics/Kunshan 0x057d built: 2017 res: 1920x1080 hz: 60
dpi: 158 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
direct-render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo ThinkPad T480 driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71
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 Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:2
chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 476.94 GiB used: 27.08 GiB (5.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN720 SDAQNTW-512G-1001
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 10190101 temp: 44.9 C scheme: GPT
Partition:
ID-1: / raw-size: 161.98 GiB size: 161.98 GiB (100.00%) used: 27.05 GiB (16.7%) fs: btrfs
dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 30.7 MiB (32.0%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 19.5 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 49.0 C pch: 44.0 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Info:
Processes: 285 Uptime: 0m wakeups: 6 Memory: 15.5 GiB used: 1.31 GiB (8.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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 1:40 pm
by megaherz33
I'll wait for the update to version 23.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 2:06 pm
by keos
@siamhie
I already have installed Ventoy into the system and i fallowed this instruction, in order to 'copy' the snaptshot file to ventoy:
After you’ve downloaded your favorite Linux operating system ISO(s), place them on the Ventoy USB device, and allow them to copy over. Copying should take no more than a few minutes.
When copying is finished, reboot the PC and keep the Ventoy USB plugged in. Then, load up the BIOS. Once you’ve loaded up your computer’s BIOS, find the boot options, and configure the system to boot from USB.
You will see a “Ventoy” menu. Ventoy will display all ISO files you’ve added to the system in this menu.
but it do not work
"... place them on the Ventoy USB device, and allow them to copy over ..."
and it did ... but after have copied it ... and reboot, (BIOS ...etc):
in the ventoy, is that the failure appears, the already copied system does not boot it.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 3:03 pm
by FullScale4Me
user-green wrote: Wed Jun 21, 2023 11:33 am
Dear Developers,
I think that the bug below may still be confirmed in Beta 2. The icon for the installed package of Firefox is concealed.
Best regards
With your mouse left hover over the | to left of the word Package.
The mouse cursor should change to <-->
Left-click and hold while pulling right.
Does the icon now appear?
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 3:10 pm
by FullScale4Me
siamhie wrote: Wed Jun 21, 2023 1:27 pm
fehlix wrote: Wed Jun 21, 2023 12:22 pm
user-green wrote: Wed Jun 21, 2023 11:33 am
Dear Developers,
I think that the bug below may still be confirmed in Beta 2. The icon for the installed package of Firefox is concealed.
You may want to give more details:
"MX Package Installer" latest version 23.6 displays here correctly:
with system locale in English:mxpi_en.jpg
and also in Japanese:mxpi_ja.jpg
@fehlix Same problem. I have xmms and librewolf installed but popular apps doesn't show it until I start typing in at least two characters into the search field. MXPI version 23.6
mxpi.png
mxpi2.png
mxpi3.png
With your mouse left hover over the | to left of the word Package.
The mouse cursor should change to <-->
Left-click and hold while pulling right.
Does the icon now appear?
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 5:18 pm
by andy
keos wrote: Wed Jun 21, 2023 2:06 pm
in the ventoy, is that the failure appears, the already copied system does not boot it.
The proposed solution solves exactly your problem - iso does not boot properly.
Login at ventoy github, download patch, apply patch to the ventoy usb, then the ISO will boot.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 5:20 pm
by siamhie
FullScale4Me wrote: Wed Jun 21, 2023 3:10 pm
siamhie wrote: Wed Jun 21, 2023 1:27 pm
fehlix wrote: Wed Jun 21, 2023 12:22 pm
You may want to give more details:
"MX Package Installer" latest version 23.6 displays here correctly:
with system locale in English:mxpi_en.jpg
and also in Japanese:mxpi_ja.jpg
@fehlix Same problem. I have xmms and librewolf installed but popular apps doesn't show it until I start typing in at least two characters into the search field. MXPI version 23.6
With your mouse left hover over the | to left of the word Package.
The mouse cursor should change to <-->
Left-click and hold while pulling right.
Does the icon now appear?
@FullScale4Me I can't get my mouse cursor to change to the <--> character but I am able to find that spot to grab.
Now I can see all installed packages under Popular Applications. I guess the Category field needs to be a bit longer in length.
k3b & Xfburn - weird issues...
Posted: Wed Jun 21, 2023 5:59 pm
by MintHawk
A weird issue came up today while trying to burn an audio CD.
The software I've been using for more than 15 years, k3b, was unable to burn a CD/DVD due to permission insufficiency with the burner.
It said I needed to go to k3b configuration and give permission to growisofs, etc.
I've never witnessed such an issue before. I looked it up, but whatever I tried didn't work. Eventually, I had to burn the project with Xfburn.
And then, the second issue came up:
It was a bunch of .mp3s and another of .flac files. The .flacs burned fine but the .mp3s sounded distorted, for some reason.
When it occurred to me that this was the case, I converted them to .flac and the burned result was fine.
Both these things happened on the PC running MX23 Beta in my parents' home.
I'm now trying the same thing on my desktop PC running the same MX.
Can anybody explain what happened?
P.S. I thought it was a software thing, so I posted it there, but the thread was locked.
k3b & Xfburn - weird issues...
Posted: Wed Jun 21, 2023 6:08 pm
by MintHawk
The same thing happens on my desktop PC.
As for Xfburn, the same thing again: the burned result coming from .mp3s is distorted, whereas the burned result that was .flacs is fine.
Edit: https://forum.xfce.org/viewtopic.php?id=13201
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 6:30 pm
by TTwrs
Is there any chance we'll see an MX-23_AHS beta? The non-AHS version will not run on some newer computers, so there is no way to take part in the trial.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 7:30 pm
by FullScale4Me
TTwrs wrote: Wed Jun 21, 2023 6:30 pm
Is there any chance we'll see an MX-23_AHS beta? The non-AHS version will not run on some newer computers, so there is no way to take part in the trial.
MX 23 currently has a 6.1.0-9 Debian LTS kernel. Try booting from a live USB.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 7:35 pm
by m_pav
@TTwrs, AHS versions are not usually built to after the full release has had a bit of time to settle. You can still contribute to an extent by using virtualisation and with your level of hardware, running a Type2 Hypervisor like VirtualBox would have next to no impact on your system resources.
If you're up for a challenge, you could "roll your own" AHS respin manually in the Hyprevisor, and snapshot it to get an ISO, but, it wouldn't be useful in our current testing.
k3b & Xfburn - weird issues...
Posted: Wed Jun 21, 2023 7:55 pm
by MintHawk
Back to the burning issue...
I installed Mint 21.2 Beta and after installing k3b (on the live USB), I successfully burned the project.
I'm thinking it's an issue with either XFCE or MX Beta, although I've seen it mentioned in other distros as well...
It's worth looking into, though, since k3b is probably one of the best pieces of open source software.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 8:00 pm
by Jerry3904
Does it work with the MX KDE beta 2?
k3b & Xfburn - weird issues...
Posted: Wed Jun 21, 2023 8:02 pm
by MintHawk
Not sure.
I'm gonna check it tomorrow.
What I can safely say, though, is that on Mint 21.2 Beta XFCE (same version as MX23) the burn process was completed successfully.
It seems to me that Ubuntu has nailed it with this one and that it might be a Debian thing...
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 21, 2023 8:54 pm
by user-green
You may want to give more details:
"MX Package Installer" latest version 23.6 displays here correctly:
with system locale in English:
mxpi_en.jpg
and also in Japanese:
mxpi_ja.jpg
fehlix,
Thank you for your posting. I confirmed it on default Xfce environment.
Perhaps I should not call it a bug, as it appears on MATE desktop when we add MATE simply from MX-Package-Installer.
Best reards
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=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=jp tz=Etc/UTC
Desktop: MATE v: 1.26.0 info: mate-panel wm: marco v: 1.26.1 vt: 7 dm: LightDM v: 1.26.0
Distro: MX-23_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: TOSHIBA product: dynabook B65/H v: PB65HNB41R7AD11
serial: <superuser required> Chassis: type: 10 v: Version 1.0 serial: <superuser required>
Mobo: TOSHIBA model: 50M PCBA 1 v: Version A0 serial: <superuser required> UEFI: TOSHIBA
v: Version 1.30 date: 01/23/2018
Battery:
ID-1: BAT1 charge: 25.5 Wh (63.1%) condition: 40.4/44.4 Wh (91.0%) volts: 14.8 min: 14.8
model: G71C000JM610 type: Li-ion serial: N/A status: charging
CPU:
Info: model: Intel Celeron 3865U bits: 64 type: MCP arch: Amber/Kaby Lake note: check level: v2
built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 9 microcode: 0x70
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB desc: 2x256 KiB L3: 2 MiB desc: 1x2 MiB
Speed (MHz): avg: 1800 min/max: 400/1800 scaling: driver: intel_pstate governor: powersave
cores: 1: 1800 2: 1800 bogomips: 7200
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel HD Graphics 610 vendor: Toshiba driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5906 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: marco v: 1.26.1 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x15db built: 2015 res: 1366x768 hz: 60 dpi: 101
gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 610 (KBL GT1)
direct-render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Toshiba driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 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 Ethernet I219-V vendor: Toshiba driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15d8 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-8:3
chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 480.52 GiB used: 2.01 GiB (0.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABF050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 6M
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Buffalo model: USB Flash Disk size: 14.76 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.00 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: 7.93 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda5
maj-min: 8:5
Sensors:
System Temperatures: cpu: 41.0 C pch: 37.5 C mobo: N/A
Fan Speeds (RPM): cpu: 3420
Repos:
Packages: pm: dpkg pkgs: 2101 libs: 1059 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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 191 Uptime: 24m wakeups: 2056 Memory: 7.68 GiB used: 2.05 GiB (26.7%) 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: UEFI
Re: k3b & Xfburn - weird issues...
Posted: Thu Jun 22, 2023 12:57 am
by Eadwine Rose
MintHawk wrote: Wed Jun 21, 2023 5:59 pm
P.S. I thought it was a software thing, so I posted it there, but the thread was locked.
As I explained: you are running the beta. The beta is not final yet, and as the announcement requested: feedback using the beta goes in the beta thread.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 1:01 am
by i_ri
hello everyone
hello @kc1di
/etc/X11/xorg.conf.d/30-touchpad-libinput.conf
trial a setting?
add SendEventsMode to libinput driver configure
sample
Code: Select all
Section "InputClass"
Identifier "touchpad"
Driver "libinput"
MatchIsTouchpad "on"
Option "Tapping" "on"
Option "TappingButtonMap" "lmr"
Option "AccelSpeed" "0.075"
Option "SendEventsMode" "disabled-on-external-mouse"
EndSection
k3b & Xfburn - weird issues...
Posted: Thu Jun 22, 2023 6:14 am
by MintHawk
Revisiting the burning issue with k3b and Xfburn:
On Mint XFCE 21.2 Beta, everything works fine. k3b works great, no errors, Xfburn burns .mp3s without the above-mentioned distortion and easyMP3gain can easily be installed via Snap instead of manually downloading the front-end here (as stated in another thread). Also, on the other PC which runs MX23 Beta, for some reason, easyMP3gain does not work, but on the PC I'm using right now it does...
I'm pretty sure things with k3b are gonna be OK on MX23 KDE Beta 2, but for the sake of the argument, I'll download it and check it out so the developers now where to focus.
Overall, each one uses their PC for their own personal reasons, with a set of specific tasks in mind they want to perform.
There are some who still burn CDs (for some crazy reason) and it seems I cannot do that right now on MX23 Beta. Thus, I'll have to uninstall MX23 Beta from the other PC
and install an Ubuntu derivative that does the job (probably Mint XFCE). However, I wouldn't like to uninstall MX23 from this PC, so I would appreciate it if a solution could be found concerning the issue with k3b. Alternatively, I'll have to go for another distro that can do that hassle free.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 6:20 am
by Jerry3904
Man, I haven't burned a CD in a million years but will take a look today.
Needs 153 new packages, lordy lordy.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 7:14 am
by Jerry3904
OK
--using hp elitebook 6930p with installed and updated
MX-23 a2
--installed k3b
--selected a folder of images to burn
--k3b had no trouble, burn completed and accurate
Code: Select all
started
(K3b::ActivePipe) successfully opened pipe.
(K3b::ActivePipe) writing from K3b::Process(0x55a56c0b42f0) to K3b::Process(0x55a56c156de8)
(mkisofs) "I: -input-charset not specified, using utf-8 (detected in locale settings)"
(mkisofs) "Using QUINTET000.PNG;1 for Pictures/Quintet.png (quintet.png)"
(growisofs) "Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'"
"Writing data"
(mkisofs) "Total translation table size: 0"
(mkisofs) "Total rockridge attributes bytes: 4333"
(mkisofs) "Total directory bytes: 10600"
(mkisofs) "Path table size(bytes): 42"
(mkisofs) "Max brk space used 0"
Read failed: "Unknown error"
Done: "write success" "read failed" (total bytes read/written: 125126656 / 125126656 )
"Flushing Cache"
"Closing Track"
"Closing Session"
"/dev/sr0"
received finished signal!
starting command: "(CommandEject)"
kf.notifications: Audio notification requested, but sound file from notifyrc file was not found, aborting audio notification
Resetting medium in "/dev/sr0"
I didn't try yet a downloaded b2--will later. Can you start in a terminal so we could see any error messages? (If you did that already I missed it)
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 7:16 am
by chrispop99
I can confirm that K3b fails to burn to CD, giving the error message:
Code: Select all
cdrecord has no permission to open the device.
Modify device settings in K3b to solve this problem.
I used some MP3 files, in data mode.
Chris
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 8:33 am
by Jerry3904
I wonder if the problems are specific to file type or size?
--I installed Xfce b2, updated and installed k3b
-- burned a folder with 10 images
--no errors, files written and accessible
k3b & Xfburn - weird issues...
Posted: Thu Jun 22, 2023 9:02 am
by MintHawk
@Jerry3904, I don't know what you did differently...Did you try burning music files?
@chrispop99, same issue.
And, after trying it on MX23 Beta2 KDE, the problem persists...
Are you sure it's not an MX issue...?
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 9:14 am
by keos
@siamhie
More informacion:
snapshot is able to copy the system, but ... is it able to be added into ventoy?
Screenshot_2023-06-22_08-42-11.png
Is it a problem of ventoy or of mx-23 beta?
Thanks
EDIT:
loading hardware specific modules
Scan usb.cd devices
look for boot file (s)
antiXlinuxfs
Fatal Error ....
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 9:26 am
by siamhie
keos wrote: Thu Jun 22, 2023 9:14 am
@siamhie
More informacion:
snapshot is able to copy the system, but ... is it able to be added into ventoy?
Screenshot_2023-06-22_08-42-11.png
Is it a problem of ventoy or of mx-23 beta?
Thanks
EDIT:
loading hardware specific modules
Scan usb.cd devices
look for boot file (s)
antiXlinuxfs
Fatal Error ....
@keos If you haven't applied the patch to your Ventoy flash drive it won't boot.
https://github.com/ventoy/Ventoy/action ... 4976511049
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 10:13 am
by Eadwine Rose
On k3b: Modify device settings in K3b to solve this problem.
is there a setting in k3b then??
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 10:20 am
by keos
@siamhie
Sorry, but i do not understand, mx-21 is already into my ventoy and it boot with not problem.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 10:33 am
by j2mcgreg
keos wrote: Thu Jun 22, 2023 10:20 am
@siamhie
Sorry, but i do not understand, mx-21 is already into my ventoy and it boot with not problem.
currently, there is a bug in Ventoy that prevents it from working with MX 23. There is a fix available, but the Ventoy developers have yet to include it in their build. The best advice for you is to use one of the other USB install drive creation tools for now.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 10:47 am
by siamhie
Weighing in on this k3b issue (from my end--MX23 fluxbox beta2).
Installed k3b and recommended packages. Launched k3b from terminal to monitor any errors.
Gabbed 5 mp3's from my hard drive and burned them to my cdr disc with no problems.
Audio CD plays in qmplay2.
Here's the terminal outputs.
Starting k3b
Code: Select all
╔═[siamhie@mxflux23]═[07:05 22/06/23]═════════════════════════════════════════════[~]
╚═> k3b
21 21
QUrl("file:///home/siamhie/")
QUrl("file:///home/siamhie") will be expanded.
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3blameencoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bexternalencoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3boggvorbisdecoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bsoxencoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3baudiometainforenamerplugin.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bwavedecoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bmpcdecoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3blibsndfiledecoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bffmpegdecoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3baudioprojectcddbplugin.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3boggvorbisencoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bmaddecoder.so"
Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/k3b_plugins/k3bflacdecoder.so"
(K3b::Device::Device) "/dev/sr0" : init()
(K3b::Device::Device) "/dev/sr0" feature: CD Mastering
(K3b::Device::Device) "/dev/sr0" feature: CD Track At Once
(K3b::Device::Device) "/dev/sr0" feature: CD-RW Media Write Support
(K3b::Device::Device) "/dev/sr0" feature: DVD Read (MMC5)
(K3b::Device::Device) "/dev/sr0" feature: DVD+R
(K3b::Device::Device) "/dev/sr0" feature: DVD+RW
(K3b::Device::Device) "/dev/sr0" feature: DVD+R Double Layer
(K3b::Device::Device) "/dev/sr0" feature: DVD-R/-RW Write
(K3b::Device::Device) "/dev/sr0" feature: Rigid Restricted Overwrite
(K3b::Device::Device) "/dev/sr0" feature: Layer Jump Recording
(K3b::Device::Device) "/dev/sr0" unknown profile: 2
(K3b::Device::Device) "/dev/sr0" : buffer.size(): 60
(K3b::Device::Device) "/dev/sr0" : checking for TAO
(K3b::Device::Device) "/dev/sr0" : checking for SAO
(K3b::Device::Device) "/dev/sr0" : checking for SAO_R96P
(K3b::Device::Device) "/dev/sr0" : checking for SAO_R96R
(K3b::Device::Device) "/dev/sr0" : checking for RAW_R16
(K3b::Device::Device) "/dev/sr0" : checking for RAW_R96P
(K3b::Device::Device) "/dev/sr0" : checking for RAW_R96R
(K3b::Device::Device) "/dev/sr0" : Number of supported write speeds via GET PERFORMANCE: 1
(K3b::Device::Device) "/dev/sr0" : 33240 KB/s
(K3b::Device::DeviceManager) setting current write speed of device "/dev/sr0" to 33240
no medium found
Devices:
------------------------------
Blockdevice: "/dev/sr0"
Vendor: "ASUS DVD"
Description: "RAM GHC1N"
Version: "AS00"
Write speed: 33240
Profiles: "DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW"
Read Cap: "DVD-ROM, DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+RW Dual Layer, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW"
Write Cap: "DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-R, CD-RW"
Writing modes: "SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump"
------------------------------
(K3b::Core) System problems:
- none -
(K3b::Core) System problems:
- none -
kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
Adding 5 mp3 files to project.
Code: Select all
(K3b::AudioDecoderFactory::createDecoder( "/media/Data/music/009 Sound System-Trinity.mp3" )
(K3bOggVorbisDecoder) not an Ogg-Vorbis file: "/media/Data/music/009 Sound System-Trinity.mp3"
(K3bWaveDecoder) "/media/Data/music/009 Sound System-Trinity.mp3" : not a RIFF file.
(K3bMpcWrapper) failed to initialize the Musepack decoder.
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3bMadDecoder) valid mpeg 1 layer 3 file with 2 channels and a samplerate of 44100
1
(K3b::AudioDoc) using K3bMadDecoder for decoding of "/media/Data/music/009 Sound System-Trinity.mp3"
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3bMadDecoder::countFrames)
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3bMadDecoder) length of track 600.189
(K3bMadDecoder::countFrames) end
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3b::AudioDoc::increaseDecoderUsage)
(K3b::AudioDoc::increaseDecoderUsage) finished
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af20c99680)
(K3b::AudioDoc::slotTrackChanged done
( K3b::AudioTrack(0x55af20c99680) , 0 )
(K3b::AudioDecoderFactory::createDecoder( "/media/Data/music/10 Ft. Ganja Plant-Chalwa.mp3" )
(K3bOggVorbisDecoder) not an Ogg-Vorbis file: "/media/Data/music/10 Ft. Ganja Plant-Chalwa.mp3"
(K3bWaveDecoder) "/media/Data/music/10 Ft. Ganja Plant-Chalwa.mp3" : not a RIFF file.
(K3bMpcWrapper) failed to initialize the Musepack decoder.
(K3bMad) skipping past ID3 tag to 159
(K3bMad) found first header at 159
(K3bMadDecoder) valid mpeg 1 layer 3 file with 2 channels and a samplerate of 44100
1
(K3b::AudioDoc) using K3bMadDecoder for decoding of "/media/Data/music/10 Ft. Ganja Plant-Chalwa.mp3"
(K3bMad) skipping past ID3 tag to 159
(K3bMad) found first header at 159
(K3bMadDecoder::countFrames)
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3bMadDecoder) length of track 277.603
(K3bMadDecoder::countFrames) end
(K3bMad) skipping past ID3 tag to 159
(K3bMad) found first header at 159
(K3b::AudioDoc::increaseDecoderUsage)
(K3b::AudioDoc::increaseDecoderUsage) finished
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af209e5a80)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioTrack::moveAfter( K3b::AudioTrack(0x55af20c99680) )
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af209e5a80)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioDecoderFactory::createDecoder( "/media/Data/music/4 Non Blondes-Whats Up.mp3" )
(K3bOggVorbisDecoder) not an Ogg-Vorbis file: "/media/Data/music/4 Non Blondes-Whats Up.mp3"
(K3bWaveDecoder) "/media/Data/music/4 Non Blondes-Whats Up.mp3" : not a RIFF file.
(K3bMpcWrapper) failed to initialize the Musepack decoder.
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3bMadDecoder) valid mpeg 1 layer 3 file with 2 channels and a samplerate of 44100
1
(K3b::AudioDoc) using K3bMadDecoder for decoding of "/media/Data/music/4 Non Blondes-Whats Up.mp3"
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3bMadDecoder::countFrames)
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3bMadDecoder) length of track 292.65
(K3bMadDecoder::countFrames) end
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3b::AudioDoc::increaseDecoderUsage)
(K3b::AudioDoc::increaseDecoderUsage) finished
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x7fee9800b080)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioTrack::moveAfter( K3b::AudioTrack(0x55af209e5a80) )
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x7fee9800b080)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioDecoderFactory::createDecoder( "/media/Data/music/Airbourne-Runnin' Wild.mp3" )
(K3bOggVorbisDecoder) not an Ogg-Vorbis file: "/media/Data/music/Airbourne-Runnin' Wild.mp3"
(K3bWaveDecoder) "/media/Data/music/Airbourne-Runnin' Wild.mp3" : not a RIFF file.
(K3bMpcWrapper) failed to initialize the Musepack decoder.
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3bMadDecoder) valid mpeg 1 layer 3 file with 2 channels and a samplerate of 48000
1
(K3b::AudioDoc) using K3bMadDecoder for decoding of "/media/Data/music/Airbourne-Runnin' Wild.mp3"
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3bMadDecoder::countFrames)
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3bMadDecoder) length of track 218.28
(K3bMadDecoder::countFrames) end
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3b::AudioDoc::increaseDecoderUsage)
(K3b::AudioDoc::increaseDecoderUsage) finished
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af207e6a50)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioTrack::moveAfter( K3b::AudioTrack(0x7fee9800b080) )
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af207e6a50)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioDecoderFactory::createDecoder( "/media/Data/music/Andrea Lindsay-Les yeux de Marie.mp3" )
(K3bOggVorbisDecoder) not an Ogg-Vorbis file: "/media/Data/music/Andrea Lindsay-Les yeux de Marie.mp3"
(K3bWaveDecoder) "/media/Data/music/Andrea Lindsay-Les yeux de Marie.mp3" : not a RIFF file.
(K3bMpcWrapper) failed to initialize the Musepack decoder.
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3bMadDecoder) valid mpeg 1 layer 3 file with 2 channels and a samplerate of 44100
1
(K3b::AudioDoc) using K3bMadDecoder for decoding of "/media/Data/music/Andrea Lindsay-Les yeux de Marie.mp3"
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3bMadDecoder::countFrames)
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3bMadDecoder) length of track 194.247
(K3bMadDecoder::countFrames) end
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3b::AudioDoc::increaseDecoderUsage)
(K3b::AudioDoc::increaseDecoderUsage) finished
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af2186deb0)
(K3b::AudioDoc::slotTrackChanged done
(K3b::AudioTrack::moveAfter( K3b::AudioTrack(0x55af207e6a50) )
(K3b::AudioDoc::slotTrackChanged K3b::AudioTrack(0x55af2186deb0)
(K3b::AudioDoc::slotTrackChanged done
found medium: ( "/dev/sr0" )
=====================================================
DiskInfo:
Mediatype: "CD-R"
Current Profile: "CD-R"
Disk state: empty
Empty: true
Rewritable: false
Appendable: false
Sessions: 0
Tracks: 0
Layers: 1
Capacity: "79:57:71" (LBA 359846 ) ( 736964608 Bytes)
Remaining size: "79:57:71" (LBA 359846 ) ( 736964608 Bytes)
Used Size: "00:00:00" (LBA 0 ) ( 0 Bytes)
=====================================================
(K3b::Device::Device) "/dev/sr0" : Number of supported write speeds via 2A: 4
(K3b::Device::Device) "/dev/sr0" : 8467 KB/s
(K3b::Device::Device) "/dev/sr0" : 7056 KB/s
(K3b::Device::Device) "/dev/sr0" : 5645 KB/s
(K3b::Device::Device) "/dev/sr0" : 2822 KB/s
"/org/freedesktop/UDisks2/block_devices/sr0"
Burning audio CD.
Code: Select all
QObject::connect: No such signal KLineEdit::lostFocus()
21 21
K3b::AudioBurnDialog(0x55af20c97830)
(K3b::Device::DeviceManager) request for empty device!
23 23
K3b::AudioBurnDialog(0x55af20c97830)
QLayout: Attempting to add QLayout "" to QFrame "", which already has a layout
kernel version: "6.1.0-9-amd64"
connecting
kernel version: "6.1.0-9-amd64"
"Preparing data"
"Determining maximum writing speed"
(K3b::AudioMaxSpeedJob) throughput: 66652 ( 1774560 / 25 )
(K3b::AudioMaxSpeedJob) throughput: 91208 ( 1774560 / 18 )
(K3b::AudioMaxSpeedJob) throughput: 82522 ( 1774560 / 20 )
(K3b::AudioMaxSpeedJob) throughput: 15853 ( 1769460 / 108 )
(K3b::AudioMaxSpeedJob) throughput: 78771 ( 1774560 / 21 )
(K3b::AudioMaxSpeedJob) max speed: 15853
K3bQProcess::QProcess(0x0)
"Writing"
"Waiting for media"
QLayout: Attempting to add QLayout "" to K3b::EmptyDiscWaiter "", which already has a layout
QLayout: Attempting to add QLayout "" to K3b::EmptyDiscWaiter "", which already has a layout
Waiting for medium "empty medium" "CD-R, CD-RW" ""
"/dev/sr0"
finishWaiting()
(K3b::Device::Device) "/dev/sr0" : Number of supported write speeds via 2A: 4
(K3b::Device::Device) "/dev/sr0" : 8467 KB/s
(K3b::Device::Device) "/dev/sr0" : 7056 KB/s
(K3b::Device::Device) "/dev/sr0" : 5645 KB/s
(K3b::Device::Device) "/dev/sr0" : 2822 KB/s
(K3b::AudioMaxSpeedJob) using speed factor: 48
***** "cdrecord" parameters:
"/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=48 -sao driveropts=burnfree textfile=/tmp/k3b.UUdwJd -useinfo -audio /home/siamhie/Videos/k3b_audio_0_01.inf /home/siamhie/Videos/k3b_audio_0_02.inf /home/siamhie/Videos/k3b_audio_0_03.inf /home/siamhie/Videos/k3b_audio_0_04.inf /home/siamhie/Videos/k3b_audio_0_05.inf"
"Preparing write process..."
"/dev/sr0"
started
QIODevice::seek (K3b::AudioTrackReader): The device is not open
(K3b::AudioDecoder) seek from "00:10:04" (+ 1152 ) to "00:00:00"
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3b::Process) found unfinished line: ' "Waiting for reader process to fill input buffer ... " '
(K3b::Process) last char: ' " " '
(K3b::Process) joined line: ' "Waiting for reader process to fill input buffer ... input buffer ready." '
"Writing Leadin"
"Writing pregap"
(K3b::CdrecordWriter) writing track 1 of 5 tracks.
"Writing track 1 of 5"
"Writing data"
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3b::AudioDecoder) track length: 105875280 ; decoded module data: 105868800 ; we need to pad 6480 bytes.
(K3b::AudioDecoder) padded 6480 bytes.
QIODevice::seek (K3b::AudioTrackReader): The device is not open
(K3b::AudioDecoder) seek from "00:10:04" (+ 1152 ) to "00:00:00"
(K3bMad) skipping past ID3 tag to 159
(K3bMad) found first header at 159
(K3b::CdrecordWriter) writing track 2 of 5 tracks.
"Writing track 2 of 5"
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3b::AudioDecoder) track length: 48970992 ; decoded module data: 48964608 ; we need to pad 6384 bytes.
(K3b::AudioDecoder) padded 6384 bytes.
QIODevice::seek (K3b::AudioTrackReader): The device is not open
(K3b::AudioDecoder) seek from "00:10:04" (+ 1152 ) to "00:00:00"
(K3bMad) skipping past ID3 tag to 144
(K3bMad) found first header at 144
(K3b::CdrecordWriter) writing track 3 of 5 tracks.
"Writing track 3 of 5"
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3b::AudioDecoder) track length: 51624048 ; decoded module data: 51618816 ; we need to pad 5232 bytes.
(K3b::AudioDecoder) padded 5232 bytes.
QIODevice::seek (K3b::AudioTrackReader): The device is not open
(K3b::AudioDecoder) seek from "00:10:02" (+ 756 ) to "00:00:00"
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3b::CdrecordWriter) writing track 4 of 5 tracks.
"Writing track 4 of 5"
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3b::AudioDecoder) track length: 38504592 ; decoded module data: 38500360 ; we need to pad 4232 bytes.
(K3b::AudioDecoder) padded 4232 bytes.
QIODevice::seek (K3b::AudioTrackReader): The device is not open
(K3b::AudioDecoder) seek from "00:10:04" (+ 1152 ) to "00:00:00"
(K3bMad) skipping past ID3 tag to 45
(K3bMad) found first header at 45
(K3b::CdrecordWriter) writing track 5 of 5 tracks.
"Writing track 5 of 5"
(K3bMad::fillStreamBuffer) MAD_BUFFER_GUARD
(K3b::AudioDecoder) track length: 34266288 ; decoded module data: 34260480 ; we need to pad 5808 bytes.
(K3b::AudioDecoder) padded 5808 bytes.
"Closing Session"
"Closing Session"
"/dev/sr0"
received finished signal!
starting command: "(CommandEject)"
kf.notifications: Audio notification requested, but sound file from notifyrc file was not found, aborting audio notification
kf.kio.widgets.kdirmodel: No node found for item that was just removed: QUrl("file:///home/siamhie/Videos/k3b_audio_0_03.inf")
Resetting medium in "/dev/sr0"
no medium found
finished command: "(CommandEject)"
"/org/freedesktop/UDisks2/block_devices/sr0"
no medium found
** (k3b:2992): WARNING **: 07:17:22.390: Invalid borders specified for theme pixmap:
/home/siamhie/.themes/Arc-Darkest-Nord-Frost/gtk-2.0/assets/frame.png,
borders don't fit within the image
(K3b::ProjectBurnDialog) job done. cleaning up.
K3b::InteractionDialog(0x55af20c97830)
k3b debug info (after burn session finished)
Code: Select all
Devices
-----------------------
ASUS DVD RAM GHC1N AS00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]
System
-----------------------
K3b Version: 22.12.3
KDE Version: 5.103.0
Qt Version: 5.15.8
Kernel: 6.1.0-9-amd64
Used versions
-----------------------
cdrecord: 1.1.11
cdrecord
-----------------------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.11
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Text len: 54
TOC Type: 0 = CD-DA
Driveropts: 'burnfree'
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'ASUS DVD'
Identification : 'RAM GHC1N '
Revision : 'AS00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 362208 = 353 KB
FIFO size : 12582912 = 12288 KB
Speed set to 8467 KB/s
pregap1: -1
Track 01: audio 100 MB (10:00.20) no preemp swab copy
Track 02: audio 46 MB (04:37.61) no preemp swab copy
Track 03: audio 49 MB (04:52.65) no preemp swab copy
Track 04: audio 36 MB (03:38.28) no preemp swab copy
Track 05: audio 32 MB (03:14.25) no preemp swab copy
Total size: 266 MB (26:23.00) = 118725 sectors
Lout start: 266 MB (26:25/00) = 118725 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11634 (97:26/66)
ATIP start of lead out: 359846 (79:59/71)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 241121
Starting to write CD/DVD at speed 48.0 in real SAO mode for single session.
Last chance to quit, starting real write in 2 seconds.
1 seconds.
0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
SAO startsec: -11634
Writing lead-in...
Lead-in write time: 15.550s
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01: 0 of 100 MB written.
Track 01: 1 of 100 MB written (fifo 100%) [buf 100%] 21.2x.
Track 01: 2 of 100 MB written (fifo 100%) [buf 100%] 21.8x.
Track 01: 3 of 100 MB written (fifo 100%) [buf 100%] 22.5x.
Track 01: 4 of 100 MB written (fifo 100%) [buf 100%] 21.8x.
Track 01: 5 of 100 MB written (fifo 100%) [buf 100%] 22.6x.
Track 01: 6 of 100 MB written (fifo 100%) [buf 100%] 21.9x.
Track 01: 7 of 100 MB written (fifo 100%) [buf 100%] 22.7x.
Track 01: 8 of 100 MB written (fifo 99%) [buf 100%] 22.0x.
Track 01: 9 of 100 MB written (fifo 100%) [buf 100%] 22.8x.
Track 01: 10 of 100 MB written (fifo 99%) [buf 100%] 22.1x.
Track 01: 11 of 100 MB written (fifo 99%) [buf 100%] 22.8x.
Track 01: 12 of 100 MB written (fifo 100%) [buf 100%] 22.2x.
Track 01: 13 of 100 MB written (fifo 100%) [buf 100%] 22.9x.
Track 01: 14 of 100 MB written (fifo 100%) [buf 100%] 22.3x.
Track 01: 15 of 100 MB written (fifo 100%) [buf 100%] 23.0x.
Track 01: 16 of 100 MB written (fifo 99%) [buf 100%] 22.3x.
Track 01: 17 of 100 MB written (fifo 100%) [buf 100%] 23.1x.
Track 01: 18 of 100 MB written (fifo 99%) [buf 100%] 22.4x.
Track 01: 19 of 100 MB written (fifo 100%) [buf 100%] 23.2x.
Track 01: 20 of 100 MB written (fifo 99%) [buf 99%] 8.6x.
Track 01: 21 of 100 MB written (fifo 100%) [buf 99%] 23.3x.
Track 01: 22 of 100 MB written (fifo 100%) [buf 100%] 22.6x.
Track 01: 23 of 100 MB written (fifo 100%) [buf 100%] 23.3x.
Track 01: 24 of 100 MB written (fifo 99%) [buf 100%] 22.7x.
Track 01: 25 of 100 MB written (fifo 100%) [buf 100%] 23.4x.
Track 01: 26 of 100 MB written (fifo 100%) [buf 99%] 22.7x.
Track 01: 27 of 100 MB written (fifo 100%) [buf 100%] 23.5x.
Track 01: 28 of 100 MB written (fifo 99%) [buf 100%] 22.8x.
Track 01: 29 of 100 MB written (fifo 100%) [buf 100%] 23.5x.
Track 01: 30 of 100 MB written (fifo 100%) [buf 100%] 22.9x.
Track 01: 31 of 100 MB written (fifo 100%) [buf 100%] 23.6x.
Track 01: 32 of 100 MB written (fifo 99%) [buf 100%] 23.0x.
Track 01: 33 of 100 MB written (fifo 100%) [buf 100%] 23.7x.
Track 01: 34 of 100 MB written (fifo 100%) [buf 100%] 23.0x.
Track 01: 35 of 100 MB written (fifo 100%) [buf 100%] 23.8x.
Track 01: 36 of 100 MB written (fifo 100%) [buf 99%] 23.1x.
Track 01: 37 of 100 MB written (fifo 100%) [buf 100%] 23.8x.
Track 01: 38 of 100 MB written (fifo 100%) [buf 100%] 23.2x.
Track 01: 39 of 100 MB written (fifo 100%) [buf 100%] 23.9x.
Track 01: 40 of 100 MB written (fifo 100%) [buf 100%] 23.2x.
Track 01: 41 of 100 MB written (fifo 100%) [buf 100%] 24.0x.
Track 01: 42 of 100 MB written (fifo 100%) [buf 100%] 23.3x.
Track 01: 43 of 100 MB written (fifo 100%) [buf 99%] 24.0x.
Track 01: 44 of 100 MB written (fifo 100%) [buf 100%] 24.8x.
Track 01: 45 of 100 MB written (fifo 100%) [buf 100%] 24.1x.
Track 01: 46 of 100 MB written (fifo 100%) [buf 99%] 24.9x.
Track 01: 47 of 100 MB written (fifo 100%) [buf 100%] 24.2x.
Track 01: 48 of 100 MB written (fifo 100%) [buf 100%] 25.0x.
Track 01: 49 of 100 MB written (fifo 100%) [buf 100%] 24.2x.
Track 01: 50 of 100 MB written (fifo 99%) [buf 99%] 25.0x.
Track 01: 51 of 100 MB written (fifo 100%) [buf 100%] 24.3x.
Track 01: 52 of 100 MB written (fifo 100%) [buf 100%] 25.1x.
Track 01: 53 of 100 MB written (fifo 100%) [buf 100%] 24.4x.
Track 01: 54 of 100 MB written (fifo 99%) [buf 100%] 25.2x.
Track 01: 55 of 100 MB written (fifo 100%) [buf 100%] 24.4x.
Track 01: 56 of 100 MB written (fifo 100%) [buf 99%] 25.2x.
Track 01: 57 of 100 MB written (fifo 99%) [buf 100%] 24.5x.
Track 01: 58 of 100 MB written (fifo 100%) [buf 100%] 25.3x.
Track 01: 59 of 100 MB written (fifo 99%) [buf 100%] 24.6x.
Track 01: 60 of 100 MB written (fifo 100%) [buf 100%] 25.4x.
Track 01: 61 of 100 MB written (fifo 100%) [buf 100%] 24.6x.
Track 01: 62 of 100 MB written (fifo 100%) [buf 100%] 25.4x.
Track 01: 63 of 100 MB written (fifo 100%) [buf 99%] 24.7x.
Track 01: 64 of 100 MB written (fifo 100%) [buf 100%] 25.6x.
Track 01: 65 of 100 MB written (fifo 100%) [buf 100%] 24.8x.
Track 01: 66 of 100 MB written (fifo 100%) [buf 100%] 25.6x.
Track 01: 67 of 100 MB written (fifo 100%) [buf 99%] 24.8x.
Track 01: 68 of 100 MB written (fifo 100%) [buf 100%] 25.6x.
Track 01: 69 of 100 MB written (fifo 100%) [buf 100%] 24.9x.
Track 01: 70 of 100 MB written (fifo 100%) [buf 100%] 25.7x.
Track 01: 71 of 100 MB written (fifo 100%) [buf 100%] 25.0x.
Track 01: 72 of 100 MB written (fifo 100%) [buf 100%] 25.8x.
Track 01: 73 of 100 MB written (fifo 100%) [buf 100%] 25.0x.
Track 01: 74 of 100 MB written (fifo 99%) [buf 100%] 25.8x.
Track 01: 75 of 100 MB written (fifo 100%) [buf 100%] 25.1x.
Track 01: 76 of 100 MB written (fifo 100%) [buf 100%] 25.9x.
Track 01: 77 of 100 MB written (fifo 100%) [buf 100%] 25.1x.
Track 01: 78 of 100 MB written (fifo 99%) [buf 100%] 26.0x.
Track 01: 79 of 100 MB written (fifo 100%) [buf 99%] 25.2x.
Track 01: 80 of 100 MB written (fifo 100%) [buf 100%] 26.0x.
Track 01: 81 of 100 MB written (fifo 99%) [buf 99%] 25.3x.
Track 01: 82 of 100 MB written (fifo 99%) [buf 100%] 26.1x.
Track 01: 83 of 100 MB written (fifo 99%) [buf 100%] 25.3x.
Track 01: 84 of 100 MB written (fifo 100%) [buf 100%] 26.1x.
Track 01: 85 of 100 MB written (fifo 100%) [buf 100%] 26.9x.
Track 01: 86 of 100 MB written (fifo 100%) [buf 100%] 26.2x.
Track 01: 87 of 100 MB written (fifo 100%) [buf 100%] 27.0x.
Track 01: 88 of 100 MB written (fifo 99%) [buf 100%] 26.2x.
Track 01: 89 of 100 MB written (fifo 99%) [buf 99%] 27.1x.
Track 01: 90 of 100 MB written (fifo 100%) [buf 100%] 26.3x.
Track 01: 91 of 100 MB written (fifo 100%) [buf 99%] 27.1x.
Track 01: 92 of 100 MB written (fifo 100%) [buf 99%] 26.3x.
Track 01: 93 of 100 MB written (fifo 100%) [buf 99%] 27.2x.
Track 01: 94 of 100 MB written (fifo 100%) [buf 100%] 26.4x.
Track 01: 95 of 100 MB written (fifo 99%) [buf 99%] 27.2x.
Track 01: 96 of 100 MB written (fifo 100%) [buf 100%] 26.5x.
Track 01: 97 of 100 MB written (fifo 100%) [buf 100%] 27.3x.
Track 01: 98 of 100 MB written (fifo 100%) [buf 100%] 26.5x.
Track 01: 99 of 100 MB written (fifo 100%) [buf 100%] 27.4x.
Track 01: 100 of 100 MB written (fifo 100%) [buf 99%] 26.5x.
Track 01: Total bytes read/written: 105875280/105875280 (45015 sectors).
Starting new track at sector: 45015
Track 02: 0 of 46 MB written.
Track 02: 1 of 46 MB written (fifo 100%) [buf 99%] 26.2x.
Track 02: 2 of 46 MB written (fifo 100%) [buf 100%] 27.0x.
Track 02: 3 of 46 MB written (fifo 100%) [buf 100%] 27.9x.
Track 02: 4 of 46 MB written (fifo 99%) [buf 100%] 27.0x.
Track 02: 5 of 46 MB written (fifo 100%) [buf 100%] 27.9x.
Track 02: 6 of 46 MB written (fifo 100%) [buf 99%] 27.0x.
Track 02: 7 of 46 MB written (fifo 100%) [buf 100%] 28.0x.
Track 02: 8 of 46 MB written (fifo 100%) [buf 100%] 27.2x.
Track 02: 9 of 46 MB written (fifo 100%) [buf 100%] 28.0x.
Track 02: 10 of 46 MB written (fifo 100%) [buf 99%] 27.2x.
Track 02: 11 of 46 MB written (fifo 100%) [buf 99%] 28.1x.
Track 02: 12 of 46 MB written (fifo 100%) [buf 99%] 27.2x.
Track 02: 13 of 46 MB written (fifo 100%) [buf 100%] 28.2x.
Track 02: 14 of 46 MB written (fifo 100%) [buf 100%] 27.3x.
Track 02: 15 of 46 MB written (fifo 100%) [buf 100%] 28.2x.
Track 02: 16 of 46 MB written (fifo 100%) [buf 100%] 27.3x.
Track 02: 17 of 46 MB written (fifo 100%) [buf 100%] 28.2x.
Track 02: 18 of 46 MB written (fifo 100%) [buf 99%] 27.4x.
Track 02: 19 of 46 MB written (fifo 99%) [buf 100%] 28.3x.
Track 02: 20 of 46 MB written (fifo 100%) [buf 100%] 27.5x.
Track 02: 21 of 46 MB written (fifo 99%) [buf 100%] 28.3x.
Track 02: 22 of 46 MB written (fifo 100%) [buf 100%] 27.5x.
Track 02: 23 of 46 MB written (fifo 99%) [buf 99%] 28.3x.
Track 02: 24 of 46 MB written (fifo 100%) [buf 100%] 27.6x.
Track 02: 25 of 46 MB written (fifo 99%) [buf 100%] 28.5x.
Track 02: 26 of 46 MB written (fifo 100%) [buf 99%] 27.6x.
Track 02: 27 of 46 MB written (fifo 99%) [buf 98%] 28.5x.
Track 02: 28 of 46 MB written (fifo 100%) [buf 99%] 27.7x.
Track 02: 29 of 46 MB written (fifo 99%) [buf 100%] 28.5x.
Track 02: 30 of 46 MB written (fifo 100%) [buf 100%] 27.7x.
Track 02: 31 of 46 MB written (fifo 99%) [buf 99%] 28.6x.
Track 02: 32 of 46 MB written (fifo 100%) [buf 100%] 27.8x.
Track 02: 33 of 46 MB written (fifo 99%) [buf 100%] 28.6x.
Track 02: 34 of 46 MB written (fifo 100%) [buf 99%] 27.8x.
Track 02: 35 of 46 MB written (fifo 99%) [buf 100%] 28.8x.
Track 02: 36 of 46 MB written (fifo 100%) [buf 100%] 27.9x.
Track 02: 37 of 46 MB written (fifo 99%) [buf 99%] 28.7x.
Track 02: 38 of 46 MB written (fifo 99%) [buf 100%] 27.9x.
Track 02: 39 of 46 MB written (fifo 99%) [buf 100%] 28.8x.
Track 02: 40 of 46 MB written (fifo 99%) [buf 99%] 9.6x.
Track 02: 41 of 46 MB written (fifo 99%) [buf 99%] 28.9x.
Track 02: 42 of 46 MB written (fifo 100%) [buf 99%] 28.0x.
Track 02: 43 of 46 MB written (fifo 100%) [buf 99%] 28.8x.
Track 02: 44 of 46 MB written (fifo 100%) [buf 99%] 29.8x.
Track 02: 45 of 46 MB written (fifo 100%) [buf 99%] 28.9x.
Track 02: 46 of 46 MB written (fifo 99%) [buf 100%] 29.8x.
Track 02: Total bytes read/written: 48970992/48970992 (20821 sectors).
Starting new track at sector: 65836
Track 03: 0 of 49 MB written.
Track 03: 1 of 49 MB written (fifo 100%) [buf 99%] 28.3x.
Track 03: 2 of 49 MB written (fifo 99%) [buf 99%] 29.1x.
Track 03: 3 of 49 MB written (fifo 99%) [buf 100%] 30.1x.
Track 03: 4 of 49 MB written (fifo 99%) [buf 99%] 29.1x.
Track 03: 5 of 49 MB written (fifo 99%) [buf 100%] 30.1x.
Track 03: 6 of 49 MB written (fifo 100%) [buf 99%] 29.1x.
Track 03: 7 of 49 MB written (fifo 100%) [buf 99%] 30.2x.
Track 03: 8 of 49 MB written (fifo 100%) [buf 99%] 29.2x.
Track 03: 9 of 49 MB written (fifo 100%) [buf 100%] 30.2x.
Track 03: 10 of 49 MB written (fifo 99%) [buf 100%] 29.2x.
Track 03: 11 of 49 MB written (fifo 100%) [buf 99%] 30.2x.
Track 03: 12 of 49 MB written (fifo 100%) [buf 99%] 29.3x.
Track 03: 13 of 49 MB written (fifo 100%) [buf 99%] 30.3x.
Track 03: 14 of 49 MB written (fifo 100%) [buf 99%] 29.4x.
Track 03: 15 of 49 MB written (fifo 100%) [buf 100%] 30.3x.
Track 03: 16 of 49 MB written (fifo 100%) [buf 99%] 29.4x.
Track 03: 17 of 49 MB written (fifo 99%) [buf 99%] 30.3x.
Track 03: 18 of 49 MB written (fifo 99%) [buf 100%] 29.5x.
Track 03: 19 of 49 MB written (fifo 100%) [buf 99%] 30.4x.
Track 03: 20 of 49 MB written (fifo 100%) [buf 99%] 29.5x.
Track 03: 21 of 49 MB written (fifo 100%) [buf 99%] 30.4x.
Track 03: 22 of 49 MB written (fifo 99%) [buf 99%] 29.5x.
Track 03: 23 of 49 MB written (fifo 99%) [buf 99%] 30.4x.
Track 03: 24 of 49 MB written (fifo 99%) [buf 99%] 29.6x.
Track 03: 25 of 49 MB written (fifo 100%) [buf 99%] 30.5x.
Track 03: 26 of 49 MB written (fifo 100%) [buf 99%] 29.6x.
Track 03: 27 of 49 MB written (fifo 99%) [buf 99%] 30.5x.
Track 03: 28 of 49 MB written (fifo 100%) [buf 99%] 29.6x.
Track 03: 29 of 49 MB written (fifo 100%) [buf 99%] 30.6x.
Track 03: 30 of 49 MB written (fifo 100%) [buf 99%] 29.7x.
Track 03: 31 of 49 MB written (fifo 100%) [buf 99%] 30.6x.
Track 03: 32 of 49 MB written (fifo 100%) [buf 100%] 29.7x.
Track 03: 33 of 49 MB written (fifo 99%) [buf 98%] 30.7x.
Track 03: 34 of 49 MB written (fifo 99%) [buf 99%] 29.7x.
Track 03: 35 of 49 MB written (fifo 99%) [buf 100%] 30.7x.
Track 03: 36 of 49 MB written (fifo 99%) [buf 99%] 29.8x.
Track 03: 37 of 49 MB written (fifo 99%) [buf 99%] 30.8x.
Track 03: 38 of 49 MB written (fifo 99%) [buf 99%] 29.8x.
Track 03: 39 of 49 MB written (fifo 99%) [buf 99%] 30.8x.
Track 03: 40 of 49 MB written (fifo 99%) [buf 99%] 29.8x.
Track 03: 41 of 49 MB written (fifo 99%) [buf 99%] 30.8x.
Track 03: 42 of 49 MB written (fifo 100%) [buf 99%] 30.0x.
Track 03: 43 of 49 MB written (fifo 100%) [buf 99%] 30.8x.
Track 03: 44 of 49 MB written (fifo 100%) [buf 100%] 31.8x.
Track 03: 45 of 49 MB written (fifo 100%) [buf 99%] 30.8x.
Track 03: 46 of 49 MB written (fifo 99%) [buf 99%] 31.8x.
Track 03: 47 of 49 MB written (fifo 99%) [buf 100%] 30.9x.
Track 03: 48 of 49 MB written (fifo 99%) [buf 100%] 31.9x.
Track 03: 49 of 49 MB written (fifo 100%) [buf 99%] 30.9x.
Track 03: Total bytes read/written: 51624048/51624048 (21949 sectors).
Starting new track at sector: 87785
Track 04: 0 of 36 MB written.
Track 04: 1 of 36 MB written (fifo 100%) [buf 99%] 30.3x.
Track 04: 2 of 36 MB written (fifo 100%) [buf 100%] 31.1x.
Track 04: 3 of 36 MB written (fifo 100%) [buf 99%] 32.2x.
Track 04: 4 of 36 MB written (fifo 100%) [buf 99%] 31.2x.
Track 04: 5 of 36 MB written (fifo 100%) [buf 99%] 32.2x.
Track 04: 6 of 36 MB written (fifo 100%) [buf 99%] 31.2x.
Track 04: 7 of 36 MB written (fifo 99%) [buf 99%] 32.3x.
Track 04: 8 of 36 MB written (fifo 100%) [buf 99%] 31.3x.
Track 04: 9 of 36 MB written (fifo 99%) [buf 99%] 32.3x.
Track 04: 10 of 36 MB written (fifo 100%) [buf 99%] 31.3x.
Track 04: 11 of 36 MB written (fifo 99%) [buf 99%] 32.3x.
Track 04: 12 of 36 MB written (fifo 99%) [buf 99%] 31.3x.
Track 04: 13 of 36 MB written (fifo 99%) [buf 100%] 32.4x.
Track 04: 14 of 36 MB written (fifo 100%) [buf 100%] 31.4x.
Track 04: 15 of 36 MB written (fifo 100%) [buf 100%] 32.4x.
Track 04: 16 of 36 MB written (fifo 100%) [buf 99%] 31.4x.
Track 04: 17 of 36 MB written (fifo 99%) [buf 100%] 32.4x.
Track 04: 18 of 36 MB written (fifo 100%) [buf 100%] 31.4x.
Track 04: 19 of 36 MB written (fifo 99%) [buf 99%] 32.4x.
Track 04: 20 of 36 MB written (fifo 100%) [buf 99%] 31.4x.
Track 04: 21 of 36 MB written (fifo 99%) [buf 99%] 32.5x.
Track 04: 22 of 36 MB written (fifo 100%) [buf 99%] 31.5x.
Track 04: 23 of 36 MB written (fifo 99%) [buf 99%] 32.5x.
Track 04: 24 of 36 MB written (fifo 100%) [buf 99%] 31.5x.
Track 04: 25 of 36 MB written (fifo 99%) [buf 99%] 32.5x.
Track 04: 26 of 36 MB written (fifo 100%) [buf 99%] 31.6x.
Track 04: 27 of 36 MB written (fifo 100%) [buf 98%] 32.5x.
Track 04: 28 of 36 MB written (fifo 100%) [buf 99%] 31.6x.
Track 04: 29 of 36 MB written (fifo 100%) [buf 99%] 32.6x.
Track 04: 30 of 36 MB written (fifo 100%) [buf 99%] 31.6x.
Track 04: 31 of 36 MB written (fifo 99%) [buf 99%] 32.7x.
Track 04: 32 of 36 MB written (fifo 100%) [buf 99%] 31.7x.
Track 04: 33 of 36 MB written (fifo 99%) [buf 99%] 32.6x.
Track 04: 34 of 36 MB written (fifo 99%) [buf 99%] 31.7x.
Track 04: 35 of 36 MB written (fifo 99%) [buf 98%] 10.3x.
Track 04: 36 of 36 MB written (fifo 99%) [buf 99%] 31.8x.
Track 04: Total bytes read/written: 38504592/38504592 (16371 sectors).
Starting new track at sector: 104156
Track 05: 0 of 32 MB written.
Track 05: 1 of 32 MB written (fifo 99%) [buf 99%] 31.7x.
Track 05: 2 of 32 MB written (fifo 100%) [buf 99%] 32.6x.
Track 05: 3 of 32 MB written (fifo 99%) [buf 99%] 33.7x.
Track 05: 4 of 32 MB written (fifo 100%) [buf 99%] 32.6x.
Track 05: 5 of 32 MB written (fifo 99%) [buf 99%] 33.7x.
Track 05: 6 of 32 MB written (fifo 99%) [buf 99%] 32.6x.
Track 05: 7 of 32 MB written (fifo 100%) [buf 99%] 33.7x.
Track 05: 8 of 32 MB written (fifo 99%) [buf 99%] 32.7x.
Track 05: 9 of 32 MB written (fifo 100%) [buf 99%] 33.7x.
Track 05: 10 of 32 MB written (fifo 100%) [buf 99%] 32.7x.
Track 05: 11 of 32 MB written (fifo 99%) [buf 99%] 33.8x.
Track 05: 12 of 32 MB written (fifo 99%) [buf 99%] 32.7x.
Track 05: 13 of 32 MB written (fifo 99%) [buf 99%] 33.8x.
Track 05: 14 of 32 MB written (fifo 100%) [buf 99%] 32.8x.
Track 05: 15 of 32 MB written (fifo 99%) [buf 99%] 33.8x.
Track 05: 16 of 32 MB written (fifo 99%) [buf 99%] 32.8x.
Track 05: 17 of 32 MB written (fifo 99%) [buf 99%] 33.8x.
Track 05: 18 of 32 MB written (fifo 99%) [buf 99%] 32.9x.
Track 05: 19 of 32 MB written (fifo 100%) [buf 99%] 33.9x.
Track 05: 20 of 32 MB written (fifo 99%) [buf 99%] 32.8x.
Track 05: 21 of 32 MB written (fifo 100%) [buf 99%] 33.9x.
Track 05: 22 of 32 MB written (fifo 100%) [buf 99%] 32.9x.
Track 05: 23 of 32 MB written (fifo 100%) [buf 99%] 33.9x.
Track 05: 24 of 32 MB written (fifo 100%) [buf 99%] 32.9x.
Track 05: 25 of 32 MB written (fifo 100%) [buf 99%] 34.0x.
Track 05: 26 of 32 MB written (fifo 100%) [buf 99%] 32.9x.
Track 05: 27 of 32 MB written (fifo 100%) [buf 99%] 34.0x.
Track 05: 28 of 32 MB written (fifo 100%) [buf 99%] 32.9x.
Track 05: 29 of 32 MB written (fifo 100%) [buf 99%] 34.0x.
Track 05: 30 of 32 MB written (fifo 100%) [buf 99%] 33.0x.
Track 05: 31 of 32 MB written (fifo 100%) [buf 99%] 34.1x.
Track 05: 32 of 32 MB written (fifo 100%) [buf 99%] 33.0x.
Track 05: Total bytes read/written: 34266288/34266288 (14569 sectors).
Writing time: 75.604s
Average write speed 26.4x.
Min drive buffer fill was 98%
Fixating...
Fixating time: 3.601s
/usr/bin/wodim: fifo had 4400 puts and 4400 gets.
/usr/bin/wodim: fifo was 0 times empty and 2688 times full, min fill was 98%.
BURN-Free was 3 times used.
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=48 -sao driveropts=burnfree textfile=/tmp/k3b.UUdwJd -useinfo -audio /home/siamhie/Videos/k3b_audio_0_01.inf /home/siamhie/Videos/k3b_audio_0_02.inf /home/siamhie/Videos/k3b_audio_0_03.inf /home/siamhie/Videos/k3b_audio_0_04.inf /home/siamhie/Videos/k3b_audio_0_05.inf
Audio CD playing in qmplay2
audio-cd.png
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 12:32 pm
by AlphaElwedritsch
i like the way to see calendar by clicking on time in status bar (xfce) and the calendar popup.
in beta 2 a seperat calendar app is opening. i think that's a step back...
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 1:11 pm
by i_ri
oops. i wanted this on fluxbox screenshots?
Hello JayM and everyone
fluxbox conky Corner TR, Top Right
It is one line.
The one line happens to be a background image.
If the one single line gets #commented out, then
zero conky.text line count
the conky is transparent.
lua
percent;
battery
cpu
ram
Try lightsvg or darkpng or Try #{image ..} for transparent.
A no-line conky.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 3:18 pm
by MintHawk
Eadwine Rose wrote: Thu Jun 22, 2023 10:13 am
On k3b: Modify device settings in K3b to solve this problem.
is there a setting in k3b then??
When you go to k3b configuration, there is nothing that I personally can configure...
Code: Select all
Devices
-----------------------
HL-DT-ST DVDRAM GH24NSD1 LG00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]
System
-----------------------
K3b Version: 22.12.3
KDE Version: 5.103.0
Qt Version: 5.15.8
Kernel: 6.1.0-9-amd64
Used versions
-----------------------
cdrecord: 1.1.11
cdrecord
-----------------------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
/usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero.
Text len: 90
TOC Type: 0 = CD-DA
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=10 -sao driveropts=burnfree textfile=/tmp/k3b.VwxpPP -useinfo -audio /home/mx-desktop/Videos/k3b_audio_0_01.inf /home/mx-desktop/Videos/k3b_audio_0_02.inf
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 3:22 pm
by keos
@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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 3:30 pm
by gRegNfo
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.
He's right, all it takes is for VENTOY devs to update the files MX team renamed lately.
Boot proc searches for older MX names and can't boot. It will be addressed eventually, until then just burn to a spare usb drive.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 3:32 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 3:34 pm
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
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 4:02 pm
by keos
Thanks.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 4:17 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 4:37 pm
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
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
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 4:53 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 4:58 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 5:10 pm
by mklym
Okay, now I see the difference. It makes sense to me now. The upgrade has started unpacking the files.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 5:16 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 5:26 pm
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
help?
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 5:56 pm
by mklym
Finished the upgrade. No issues so far. Got the broken pipe errors during install but all seems okay. I will post if any issues arise.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 5:58 pm
by gRegNfo
fehlix wrote: Thu Jun 22, 2023 5:26 pm
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
help?
You're a patient life saver
I ended up going to synaptic just to browse again... and the search for GAIL is different from LIBGAIL, my bad.
I also reenabled the status tray plugin on my panel.
I'm dumber by the day!
That's why this community and OS is the best! Thanks
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 6:02 pm
by fehlix
mklym wrote: Thu Jun 22, 2023 5:56 pm
Finished the upgrade. No issues so far. Got the broken pipe errors during install but all seems okay. I will post if any issues arise.
The "broke pipe" warning is a dkms tool issue, which probably some one upstream need to fix :
Until than in post
#114 in this thread a working fix was mentioned.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 6:23 pm
by i_ri
hello dolphin_oracle
mx-installer 23.6.05
minstall --oem Success.
finished; then startup ootb.
install had a home/demo directory that i deleted.
yes home has a demo and the user the ootb just created. demo is not an account, just a directory, so i delete the directory.
The previous installer triggered once --ootb on a xfce install and was got the same stray /demo directory. i deleted it.
Beautiful. almost the new default except the spare /demo.
Best installer in the business.
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: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <superuser required>
Chassis: Hewlett-Packard type: 3 serial: <superuser required>
Mobo: MSI model: IONA v: 1.0 serial: <superuser required> BIOS: American Megatrends v: 5.15
date: 06/25/2010
CPU:
Info: model: Intel Core i3 530 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1331 high: 1463 min/max: 1200/2933 scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 1463 2: 1200 3: 1463 4: 1200 bogomips: 23409
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: intel dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 mapped: VGA1 model: AOC 2436 serial: <filter> built: 2010 res: 1920x1080
hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d800 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: c080 bus-ID: 00:1f.2
chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 1.86 TiB used: 19.47 GiB (1.0%)
ID-1: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: Cruzer Glide size: 29.25 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1.00
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
SMART Message: Unable to run smartctl. Root privileges required.
ID-2: /dev/sdf maj-min: 8:80 vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ABB0
scheme: MBR
ID-3: /dev/sdg maj-min: 8:96 type: USB vendor: SanDisk model: Cruzer Glide size: 14.56 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.27
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 29.24 GiB size: 28.62 GiB (97.86%) used: 10.93 GiB (38.2%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2446 libs: 1346 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://la.mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 205 Uptime: 2h 25m wakeups: 1 Memory: 7.62 GiB used: 2.33 GiB (30.6%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 7:50 pm
by karens_haircut
fehlix wrote: Thu Jun 22, 2023 4:37 pm
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
Thank you!
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 9:30 pm
by gRegNfo
UPDATE
If any one has a problem with error:
Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915
or similar do this
Code: Select all
~$ mkdir firmware
~$ cd firmware
~$ wget -r -nd -e robots=no -A '*.bin' --accept-regex '/plain/' https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915/
~$ sudo mv *.bin /lib/firmware/i915/
~$ sudo update-initramfs -c -k all
Also errors with RTL8812AU (search github for updated drivers of your device - mine is RTL8821CE - for kernel 6x and read the docs)
Code: Select all
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
were removed:
Code: Select all
~$ sudo apt update
~$ sudo apt install git dkms
~$ sudo git clone https://github.com/ivanovborislav/rtl8812au
~$ sudo cp -r rtl8812au /usr/src/rtl8812au-5.13.6
~$ sudo dkms add -m rtl8812au -v 5.13.6
~$ sudo dkms build -m rtl8812au -v 5.13.6
~$ sudo dkms install -m rtl8812au -v 5.13.6
although because of a warning from using build and installed different modules after retries I ended up using:
Code: Select all
~$ dkms status
~$ rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: (different modules warning here!!!)
~$ sudo dkms remove rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ sudo dkms install rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ dkms status
~$ rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: installed
There maybe typos here... I'm using also a dozen kernels for testing future nvidia modules from v5 to v6 also ahs...
Hope it helps!
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 9:45 pm
by pbear
fehlix wrote: Thu Jun 22, 2023 6:02 pm
mklym wrote: Thu Jun 22, 2023 5:56 pm
Finished the upgrade. No issues so far. Got the broken pipe errors during install but all seems okay. I will post if any issues arise.
The "broke pipe" warning is a dkms tool issue, which probably some one upstream need to fix :
Until than in post
#114 in this thread a working fix was mentioned.
Is there any reason not to remove the Realtek -dkms packages, assuming of course the user doesn't have a Realtek wireless adapter?
If a user has a Realtek adapter, is there any reason not to remove the other two packages (keeping only the one matching the adapter)?
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 22, 2023 10:02 pm
by gRegNfo
pbear wrote: Thu Jun 22, 2023 9:45 pm
fehlix wrote: Thu Jun 22, 2023 6:02 pm
mklym wrote: Thu Jun 22, 2023 5:56 pm
Finished the upgrade. No issues so far. Got the broken pipe errors during install but all seems okay. I will post if any issues arise.
The "broke pipe" warning is a dkms tool issue, which probably some one upstream need to fix :
Until than in post
#114 in this thread a working fix was mentioned.
Is there any reason not to remove the Realtek -dkms packages, assuming of course the user doesn't have a Realtek wireless adapter?
If a user has a Realtek adapter, is there any reason not to remove the other two packages (keeping only the one matching the adapter)?
I just posted a solution for my RTL882CE issue, not sure if it implements your device!
Mine is an internal wifi/bluetooth pcie I changed (not original, first one died) a while ago on my laptop.
https://github.com/ivanovborislav/rtl8812au
The installation is not straightforward and feel free to ask if I made any typos
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 23, 2023 1:32 pm
by BV206
Ventoy 1.0.93 was released today.
It fixed MX-23 not booting (for me, anyway).
https://github.com/ventoy/Ventoy/releases
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 23, 2023 1:45 pm
by siamhie
+1
I'm sure the MX patch was added to this version. 1.0.91 didn't have it.
*edit
@BV206 Installed Ventoy 1.0.93 on my thumb drive and copied over my MX-23 fluxbox beta 2 ISO and it booted up without any errors.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 23, 2023 3:28 pm
by Jaki
Will it update MX-23 “Libretto” beta 2 to stable version?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 23, 2023 3:42 pm
by Jerry3904
Very likely, but better to start with the RC
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 23, 2023 3:48 pm
by fehlix
siamhie wrote: Fri Jun 23, 2023 1:45 pm
+1
I'm sure the MX patch was added to this version. 1.0.91 didn't have it.
*edit
@BV206 Installed Ventoy 1.0.93 on my thumb drive and copied over my MX-23 fluxbox beta 2 ISO and it booted up without any errors.
Some "cosmetic" errors do still show up:
Code: Select all
Error: /ventoy/hook/debian/antix-disk.sh: line 43: vtoy_unsquashfs: not found
Error: /ventoy/hook/debian/antix-disk.sh: line 49: vtoy_unsquashfs: not found
but seems not to prevent from booting.
You can view the live-log on screen with disabled splasht-screen or with [Alt]+F1 on VT1
or on live booted either on command line with colors
Code: Select all
less -R /var/log/live/initrd.log.color
ventoy-hook-error.jpg
or just using "Quick System Info" tool:
ventoy-live-log.jpg
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 23, 2023 11:23 pm
by siamhie
fehlix wrote: Fri Jun 23, 2023 3:48 pm
Some "cosmetic" errors do still show up:
Code: Select all
Error: /ventoy/hook/debian/antix-disk.sh: line 43: vtoy_unsquashfs: not found
Error: /ventoy/hook/debian/antix-disk.sh: line 49: vtoy_unsquashfs: not found
but seems not to prevent from booting.
You can view the live-log on screen with disabled splasht-screen or with [Alt]+F1 on VT1
or on live booted either on command line with colors
Code: Select all
less -R /var/log/live/initrd.log.color
ventoy-hook-error.jpg
or just using "Quick System Info" tool:
ventoy-live-log.jpg
Will do
@fehlix when RC rolls out. In the mean time, ISO's seem to boot without the antiX error message.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 2:17 am
by user-green
Dear Developers,
mx-packageinstaller-pkglist (in /usr/share/mx-packageinstaller-pkglist ) does not reflect mx-packageinstaller-description which has been translated at Transifex.
As a result, descriptions are still indicated in default English. See the attached image for reference.
Best regards,
Green
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 2:37 am
by i_ri
hello dolphin_oracle
kde systemd runaway unusable; systemd is not sleeping;
my guess is that it is looking for something in the Actions category, because
The shutdown buttons are not present in the Menu nor are the shutdown buttons active in sddm.
kde initV is fine.
jasalt mentioned running kde on systemd; is that okay?
kc1di and Jamey and darknetmatrix testing kde on systemd?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 3:30 am
by i_ri
hello dolphin_oracle
custom-toolbox 23.6
keyboard Enter key Return
is locked onto the bottom frame of buttons
About, Help, Edit, Close >Return coincides.
Navigating the highlight to a Category item entry
additionally places the highlight on About,
key Return of a highlighted Category item
brings the About page.
Search the same; >Return brings About.
custom-toolbox should be a default install on all iso s. xfce, kde, mxfluxbox.
<custom-toolbox> needs to be a dependency for <mx-fluxbox>; right now mx-fluxbox installs without custom-toolbox.
sidenote:
Sample example representative of the work to create new -launchers; the new Execs are working.
.
example.list sample -is universal amongst three systems and
-refresh .desktop names.
Code: Select all
# EXAMPLE LAUNCHER
# Simple text file containing Name= Comment= Category=(text)
# with the list of .desktop names under each Category=
# Sorts Category (text) alphabetically. .
Name=Example Launcher
Comment=This is a comment for the launcher
Category=1Live
mx-remastercc
mx-live-usb-maker
mx-snapshot
Category=Maintenance
mx-user
mx-boot-repair
Category=AUtilities
system-config-printer
about-mx-linux
pavucontrol
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 6:20 am
by thinkpadx
Jerry3904 wrote: Fri Jun 23, 2023 3:42 pm
Very likely, but better to start with the RC
Thanks Jerry! I was wondering. I usually install from rc1 and all is well but for some reason i was wondering about the beta path.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 6:46 am
by keos
Hello,
I continue with the same problem, I keep getting the same 'Fatal Error'.
I downloaded and extracted the new Ventoy:
https://github.com/ventoy/Ventoy/releases
Screenshot_2023-06-24_06-32-00.png
I copy snapshot via 'send' in the file manager, to the Ventoy ...
I configure the Bios ... reboot, MX-23 appears in Ventoy, click ... I start to open it and it gives the same error as before. (?)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 6:52 am
by gRegNfo
I tried installing MX 21.3 on some old machine (dual core from 2008??) from network through PXE.
I had similar error like the VENTOY ones.
Don't know if it's the PXE firmware version...
I managed to boot from PE based disk management like AOMEI and MACRIUM though...
PXE-Boot-MX213.jpg
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 6:52 am
by Jerry3904
@i_ri custom-toolbox should be a default install on all iso s. xfce, kde, mxfluxbox.
<custom-toolbox> needs to be a dependency for <mx-fluxbox>; right now mx-fluxbox installs without custom-toolbox.
The MXFB Settings Manager is using it, so you might want to check again
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 7:01 am
by gRegNfo
siamhie wrote: Fri Jun 23, 2023 11:23 pm
fehlix wrote: Fri Jun 23, 2023 3:48 pm
Some "cosmetic" errors do still show up:
Code: Select all
Error: /ventoy/hook/debian/antix-disk.sh: line 43: vtoy_unsquashfs: not found
Error: /ventoy/hook/debian/antix-disk.sh: line 49: vtoy_unsquashfs: not found
but seems not to prevent from booting.
You can view the live-log on screen with disabled splasht-screen or with [Alt]+F1 on VT1
or on live booted either on command line with colors
Code: Select all
less -R /var/log/live/initrd.log.color
ventoy-hook-error.jpg
or just using "Quick System Info" tool:
ventoy-live-log.jpg
Will do @fehlix when RC rolls out. In the mean time, ISO's seem to boot without the antiX error message.
I already addressed the github team the GTK GUI errors I got, but it still works and installs... just some minor stuff.
You should think about checking it and help addressing your issues with the Ventoy team directly? here:
https://github.com/ventoy/Ventoy/issues
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 7:28 am
by fehlix
gRegNfo wrote: Sat Jun 24, 2023 6:52 am
I tried installing MX 21.3 on some old machine (dual core from 2008??) from network through PXE.
I had similar error like the VENTOY ones.
Don't know if it's the PXE firmware version...
I managed to boot from PE based disk management like AOMEI and MACRIUM though...
PXE-Boot-MX213.jpg
I believe the current MX/antiX live system won't boot through PXE.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 7:56 am
by i_ri
Hello Jerry3904
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 8:10 am
by keos
Ventoy installs but deletes/formats everything ...
I was installing this option: Source code (tar.gz)
Switch for option:
ventoy-1.0.93-linux.tar.gz
and it worked correctly
... but it erased the previously installed system: MX-21
*During the installation it said something like it was going to format the "device", I assumed it was the partition inside the corresponding ventoy ... not all of it ...
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 8:29 am
by fehlix
keos wrote: Sat Jun 24, 2023 8:10 am
Ventoy installs but deletes/formats everything ...
Note: This is not a How to use ventoy thread, but a MX23-beta2 feadback thread.
Please read ventoy FAQ or Help and README provided by ventoy.
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 8:35 am
by j2mcgreg
@keos wrote:
*During the installation it said something like it was going to format the "device", I assumed it was the partition inside the corresponding ventoy ... not all of it ...
That's the default behaviour for a USB creation tool. You should chalk this one up to a learning experience, Always, always, if you are going to reuse USB drives for this purpose, check them first to be sure that they contain nothing important.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 9:09 am
by keos
Well I will keep it in mind ...
but the previous one never formatted me ...
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 9:35 am
by Adrian
i_ri wrote: Sat Jun 24, 2023 3:30 am
hello dolphin_oracle
custom-toolbox 23.6
keyboard Enter key Return
is locked onto the bottom frame of buttons
About, Help, Edit, Close >Return coincides.
Navigating the highlight to a Category item entry
additionally places the highlight on About,
key Return of a highlighted Category item
brings the About page.
Search the same; >Return brings About.
Thanks, I think I fixed that, for some reason autdefault for buttons in Qt is weird.
WiFi Finder is unstable
Posted: Sat Jun 24, 2023 10:13 am
by Frankarnold
... sometimes not finding any wifi devices, on next boot finding the device and all available connections
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: TREKSTOR product: Surfbook A13B v: N/A serial: <superuser required>
Mobo: TS_inet model: Geminilake_PN5_V01 serial: <superuser required> UEFI: American Megatrends
v: BIOS_V1.2.4 date: 07/23/2018
Battery:
ID-1: BAT0 charge: 24.8 Wh (70.9%) condition: 35.0/35.0 Wh (100.0%) volts: 7.6 min: N/A
model: GLK MRD Li-ion Battery type: Li-ion serial: <filter> status: discharging
CPU:
Info: model: Intel Pentium Silver N5000 bits: 64 type: MCP arch: Goldmont Plus level: v2
built: 2017 process: Intel 14nm family: 6 model-id: 0x7A (122) stepping: 1 microcode: 0x3E
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 224 KiB desc: d-4x24 KiB; i-4x32 KiB
L2: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1182 high: 1309 min/max: 800/2700 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1055 2: 1309 3: 1193 4: 1172 bogomips: 8755
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel GeminiLake [UHD Graphics 605] driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:3184 class-ID: 0300
Device-2: Alcor Micro USB 2.0 Web Camera type: USB driver: uvcvideo bus-ID: 1-7:5
chip-ID: 058f:5608 class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: Najing CEC Panda LC133LF4L01 built: 2015 res: 1920x1080 hz: 60 dpi: 166
gamma: 1.2 size: 294x165mm (11.57x6.5") diag: 337mm (13.3") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 605 (GLK 3) direct-render: Yes
Audio:
Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: Realtek
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_apl bus-ID: 00:0e.0
chip-ID: 8086:3198 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 Wireless 3165 driver: iwlwifi v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:3165 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
chip-ID: 8087:0a2a class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 1000 hci-v: 4.2 rev: 1000
Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 57.62 GiB used: 9.13 GiB (15.8%)
ID-1: /dev/mmcblk0 maj-min: 179:0 model: NCard size: 57.62 GiB block-size: physical: 512 B
logical: 512 B type: SSD serial: <filter> rev: 0x8 scheme: GPT
SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
ID-1: / raw-size: 57.36 GiB size: 56.16 GiB (97.91%) used: 9.13 GiB (16.3%) fs: ext4
dev: /dev/mmcblk0p2 maj-min: 179:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/mmcblk0p1 maj-min: 179:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2056 libs: 1041 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://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
Info:
Processes: 207 Uptime: 6m wakeups: 2 Memory: 3.66 GiB used: 1.66 GiB (45.3%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 11:39 am
by faithflux
I have a Minisforum Neptune HX99G. This mini PC has AMD Radeon™ RX 6600M dedicated video card and a AMD Ryzen™ 9 6900HX Processor with GPU as well (AMD Radeon™ 680M).
At live boot I get a screen to select one. MX Linux will only boot from the processor graphic not from the dedicated AMD Radeon™ RX 6600M. Don't know why. If I select this one,
My monitor will go black and it gets like disconnected. Any ideas?
Top
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=/antiX/vmlinuz quiet splasht nosplash
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop System: Micro (HK) Tech product: HX99G v: N/A serial: <superuser required>
Mobo: Shenzhen Meigao Equipment model: F7BAA serial: <superuser required> UEFI: American
Megatrends LLC. v: 0.18 date: 03/02/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3 serial: <filter> charge: 100%
(should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 9 6900HX with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68)
stepping: 1 microcode: 0xA404102
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1510 high: 1801 min/max: 1600/4934 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1511 2: 1415 3: 1799 4: 1801 5: 1376 6: 1420
7: 1484 8: 1600 9: 1377 10: 1547 11: 1385 12: 1600 13: 1355 14: 1514 15: 1385 16: 1600
bogomips: 105402
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: none empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 03:00.0 chip-ID: 1002:73ff
class-ID: 0300
Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-4
empty: DP-3, DP-5, DP-6, DP-7, DP-8, DP-9, eDP-1 bus-ID: e8:00.0 chip-ID: 1002:1681
class-ID: 0300 temp: 37.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: DP-4 mapped: DisplayPort-3 model: HP U32 4K HDR serial: <filter> built: 2022
res: 3840x2160 hz: 60 dpi: 138 gamma: 1.2 size: 709x411mm (27.91x16.18") diag: 820mm (32.3")
ratio: 16:9 modes: max: 3840x2160 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (rembrandt LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: bus-ID: 3-3:2
chip-ID: 0d8c:0014 gen: 4 speed: 16 GT/s class-ID: 0300 lanes: 16 bus-ID: 03:00.1
chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e8:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x v: kernel
alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: e8:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-4: AMD Family 17h/19h HD Audio vendor: Realtek driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e8:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-5: C-Media Audio Adapter (Unitek Y-247A) type: USB
driver: cmedia_hs100b,snd-usb-audio,usbhid
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 Ethernet I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: N/A bus-ID: 04:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel modules: wl pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 14c3:0608 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 5-3:3
chip-ID: 0e8d:0608 class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2302 hci-v: 5.2 rev: 119
Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 2.3 TiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8PGP41024Q-A0 size: 953.87 GiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: ELFK0S.6 temp: 46.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: SSD serial: <filter>
scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: PNY model: USB 2.0 FD size: 7.55 GiB block-size:
physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 8192 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: 2.02 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb4
maj-min: 8:20
Sensors:
System Temperatures: cpu: 41.2 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 36.0 C device: amdgpu temp: 38.0 C mem: 38.0 C fan: 0 watts: 3.00
Repos:
Packages: pm: dpkg pkgs: 2056 libs: 1041 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://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 376 Uptime: 20m wakeups: 3 Memory: 30.63 GiB used: 3.17 GiB (10.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: UEFI
SecureBoot enabled
: added code tags
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 11:41 am
by Eadwine Rose
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 1:23 pm
by AK-47
faithflux wrote: Sat Jun 24, 2023 11:39 am
I have a Minisforum Neptune HX99G. This mini PC has AMD Radeon™ RX 6600M dedicated video card and a AMD Ryzen™ 9 6900HX Processor with GPU as well (AMD Radeon™ 680M).
At live boot I get a screen to select one. MX Linux will only boot from the processor graphic not from the dedicated AMD Radeon™ RX 6600M. Don't know why. If I select this one,
My monitor will go black and it gets like disconnected. Any ideas?
In the BIOS there should be a setting which will control which GPU will be used for the primary display. Make sure it is set to start with your discrete GPU instead of the IGPU.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 1:41 pm
by keos
I have 'Librewolf' installed but it doesn't show up here, instead in the command output there are two chromium when I only have one - I don't understand, something I'm doing wrong? Thanks...
Code: Select all
keos@kaos:~
$ sudo -i
[sudo] password for keos:
root@kaos:~# update-alternatives --config x-www-browser
There are 3 choices for the alternative x-www-browser (providing /usr/bin/x-www-browser).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/bin/chromium 40 auto mode
1 /usr/bin/chromium 40 manual mode
2 /usr/bin/mx-viewer 20 manual mode
3 /usr/bin/palemoon 40 manual mode
Press <enter> to keep the current choice[*], or type selection number:
Code: Select all
System:
Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64
root=UUID=600e4d5d-7c43-4bb6-8e4c-cbecb57df9ed ro quiet splash
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
v: 4.18.0 dm: LightDM v: 1.26.0 Distro: MX-23_beta2_x64 Libretto June 15
2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: Dell product: Inspiron 3583 v: N/A serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: Dell model: 0WHCP7 v: A00 serial: <filter> UEFI: Dell v: 1.5.1
date: 05/30/2019
Battery:
ID-1: BAT0 charge: 39.9 Wh (100.0%) condition: 39.9/42.0 Wh (95.0%)
volts: 12.6 min: 11.4 model: SMP DELL VM73283 type: Li-poly serial: <filter>
status: full
CPU:
Info: model: Intel Core i5-8265U socket: BGA1528 (U3E1) note: check bits: 64
type: MT MCP arch: Comet/Whiskey Lake note: check gen: core 8 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0xF6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled 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: 837 high: 1800 min/max: 400/3900 base/boost: 3700/3900
scaling: driver: intel_pstate governor: powersave volts: 0.9 V
ext-clock: 100 MHz cores: 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700
8: 1800 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
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: Enhanced IBRS, IBPB: conditional, RSB
filling, PBRSB-eIBRS: SW sequence
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3ea0
class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 1-6:4 chip-ID: 0bda:5520 class-ID: 0e02 serial: <filter>
Display: server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: AU Optronics 0x10ec built: 2017 res: 1366x768
hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (WHL
GT2) direct-render: Yes
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:9dc8 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: off with: 1: pipewire-pulse
status: off 2: wireplumber status: off tools: pw-cat,pw-cli,wpctl
Server-2: PulseAudio v: 16.1 status: active (root, process)
tools: pacat,pactl,pavucontrol
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 297.07 GiB used: 15.49 GiB (5.2%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: PC SN520 NVMe WDC 256GB size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
rev: 20200012 temp: 44.9 C scheme: GPT
SMART: yes health: PASSED on: 370d 23h cycles: 3,615
read-units: 31,379,068 [16.0 TB] written-units: 133,214,496 [68.2 TB]
ID-2: /dev/sda maj-min: 8:0 type: USB model: N/A size: 58.59 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
rev: 2.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 44.69 GiB size: 43.68 GiB (97.76%) used: 15.48 GiB (35.4%)
fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 1.43 GiB size: 1.43 GiB (99.80%)
used: 18.6 MiB (1.3%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 47.0 C pch: 46.0 C mobo: 38.0 C
Fan Speeds (RPM): cpu: 0
Repos:
Packages: pm: dpkg pkgs: 2527 libs: 1419
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
2: deb http://security.debian.org/debian-security/ bookworm-security non-free contrib main
Active apt repos in: /etc/apt/sources.list.d/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bullseye main
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
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com/ stable non-free
Info:
Processes: 252 Uptime: 13m wakeups: 2 Memory: 7.63 GiB used: 2.1 GiB (27.6%)
Init: SysVinit v: 3.06 runlevel: 5 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 alt: 12 clang: 14.0.6 Shell: Bash (sudo) v: 5.2.15
running-in: xfce4-terminal inxi: 3.3.26
root@kaos:~#
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 2:17 pm
by j2mcgreg
@keos wrote:
I have 'Librewolf' installed but it doesn't show up here, instead in the command output there are two chromium when I only have one - I don't understand, something I'm doing wrong? Thanks...
Librewolf is not available because this is a beta release and the repositories are not nearly complete. I think that you would be better off to return to MX 21.3 and wait for the release candidates before attempting to upgrade.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 3:06 pm
by keos
I don"t know what to say but i got it from mx-installer, i did wrong?
Screenshot_2023-06-24_15-07-28.png
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 4:01 pm
by dolphin_oracle
user-green wrote: Sat Jun 24, 2023 2:17 am
Dear Developers,
mx-packageinstaller-pkglist (in /usr/share/mx-packageinstaller-pkglist ) does not reflect mx-packageinstaller-description which has been translated at Transifex.
As a result, descriptions are still indicated in default English. See the attached image for reference.
Best regards,
Green
i do not have the tools to import the strings form transifex into the package descriptions. all that was set up by other people. if someone wants to do it and make a pull request to our git hub for mx-packageinstaller-pkglist, I will surely incorporate them.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 4:02 pm
by dolphin_oracle
keos wrote: Sat Jun 24, 2023 3:06 pm
I don"t know what to say but i got it from mx-installer, i did wrong?
Screenshot_2023-06-24_15-07-28.png
likley you did nothing wrong, but I would file a bug with librewolf. that is a third-party repo and we do not package it, they do.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 4:08 pm
by dolphin_oracle
gRegNfo wrote: Thu Jun 22, 2023 3:32 pm
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.
will be fixed for final, thanks
Re: k3b & Xfburn - weird issues...
Posted: Sat Jun 24, 2023 4:12 pm
by dolphin_oracle
MintHawk wrote: Thu Jun 22, 2023 6:14 am
Revisiting the burning issue with k3b and Xfburn:
On Mint XFCE 21.2 Beta, everything works fine. k3b works great, no errors, Xfburn burns .mp3s without the above-mentioned distortion and easyMP3gain can easily be installed via Snap instead of manually downloading the front-end here (as stated in another thread). Also, on the other PC which runs MX23 Beta, for some reason, easyMP3gain does not work, but on the PC I'm using right now it does...
I'm pretty sure things with k3b are gonna be OK on MX23 KDE Beta 2, but for the sake of the argument, I'll download it and check it out so the developers now where to focus.
Overall, each one uses their PC for their own personal reasons, with a set of specific tasks in mind they want to perform.
There are some who still burn CDs (for some crazy reason) and it seems I cannot do that right now on MX23 Beta. Thus, I'll have to uninstall MX23 Beta from the other PC
and install an Ubuntu derivative that does the job (probably Mint XFCE). However, I wouldn't like to uninstall MX23 from this PC, so I would appreciate it if a solution could be found concerning the issue with k3b. Alternatively, I'll have to go for another distro that can do that hassle free.
are you burning music or data cds?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 4:44 pm
by keos
OK. What about the 'two chromiums', one say it is 'auto mode' and other 'manual mode' ... which one is the real one?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 5:54 pm
by j2mcgreg
keos wrote: Sat Jun 24, 2023 4:44 pm
OK. What about the 'two chromiums', one say it is 'auto mode' and other 'manual mode' ... which one is the real one?
They are the same thing. "auto" just means that it has been automatically selected as your default browser.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 11:00 pm
by i_ri
hello dolphin_oracle
systemd
i reported that kde not running on systemd.
now turned to xfce trial using systemd does not start.
forced into root account it says it is hung on power manager.
no shutdown buttons are all broken.
halt.
back to sysV everything works sysV.
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: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23_beta2_x64 Libretto June 15
2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <superuser required>
Chassis: Hewlett-Packard type: 3 serial: <superuser required>
Mobo: MSI model: IONA v: 1.0 serial: <superuser required> BIOS: American Megatrends v: 5.15
date: 06/25/2010
CPU:
Info: model: Intel Core i3 530 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1455 high: 1459 min/max: 1200/2933 scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 1455 2: 1459 3: 1448 4: 1459 bogomips: 23410
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: crocus gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 mapped: VGA1 model: AOC 2436 serial: <filter> built: 2010 res: 1920x1080
hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d800 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: c080 bus-ID: 00:1f.2
chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 1.82 TiB used: 15.21 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ABB0
scheme: MBR
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.79 TiB (98.37%) used: 15.21 GiB (0.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: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 30.2 C mobo: 21.6 C
Fan Speeds (RPM): cpu: 821 fan-2: 866 fan-3: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.33 vbat: 3.28
Repos:
Packages: pm: dpkg pkgs: 2189 libs: 1118 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 201 Uptime: 18m wakeups: 1 Memory: 7.62 GiB used: 1.25 GiB (16.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)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jun 24, 2023 11:15 pm
by dolphin_oracle
i_ri wrote: Sat Jun 24, 2023 11:00 pm
hello dolphin_oracle
systemd
i reported that kde not running on systemd.
now turned to xfce trial using systemd does not start.
forced into root account it says it is hung on power manager.
no shutdown buttons are all broken.
halt.
back to sysV everything works sysV.
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: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23_beta2_x64 Libretto June 15
2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <superuser required>
Chassis: Hewlett-Packard type: 3 serial: <superuser required>
Mobo: MSI model: IONA v: 1.0 serial: <superuser required> BIOS: American Megatrends v: 5.15
date: 06/25/2010
CPU:
Info: model: Intel Core i3 530 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1455 high: 1459 min/max: 1200/2933 scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 1455 2: 1459 3: 1448 4: 1459 bogomips: 23410
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: crocus gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 mapped: VGA1 model: AOC 2436 serial: <filter> built: 2010 res: 1920x1080
hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d800 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: c080 bus-ID: 00:1f.2
chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 1.82 TiB used: 15.21 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ABB0
scheme: MBR
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.79 TiB (98.37%) used: 15.21 GiB (0.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: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 30.2 C mobo: 21.6 C
Fan Speeds (RPM): cpu: 821 fan-2: 866 fan-3: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.33 vbat: 3.28
Repos:
Packages: pm: dpkg pkgs: 2189 libs: 1118 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 201 Uptime: 18m wakeups: 1 Memory: 7.62 GiB used: 1.25 GiB (16.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)
I cannot duplicate. I suggest checking for unfinished updates.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 25, 2023 12:15 am
by davidy
If your hardware likes the ahs releases will it be OK to run these betas? I just realized that when updating kernels from an ahs one, that works, one should stick with ahs. Not sure how MX-23 relates to the liquorix kernels, if at all.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 25, 2023 3:17 am
by i_ri
hello dolphin_oracle
systemd
all three iso.s Error systemd
Cannot Connect TPM Chip.
Just did installing mx23_fluxbox beta2 and it does not start on systemd.
three systems, kde xfce fluxbox, across two machines. no systemd beta2. a lot of installing. i have a fluxbox-alpha running systemd.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 25, 2023 6:46 am
by gRegNfo
keos wrote: Sat Jun 24, 2023 8:10 am
Ventoy installs but deletes/formats everything ...
I was installing this option: Source code (tar.gz)
Switch for option:
ventoy-1.0.93-linux.tar.gz
and it worked correctly
... but it erased the previously installed system: MX-21
*During the installation it said something like it was going to format the "device", I assumed it was the partition inside the corresponding ventoy ... not all of it ...
It should be able to keep a partition to itself, and UPDATE it not format it all...
I also did that on a 256GB drive and it worked. I did update it though I don't know if you chose the wrong option or if it's a bug.
This version is very buggy !
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 25, 2023 1:12 pm
by davidy
I'd say that's a go. lol
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 25, 2023 5:19 pm
by Laurentius
hello.
Congratulations for the upcoming release.
I would like to recall an old post I have made about mx-comfort theme and Thunderbird:
viewtopic.php?p=670683#p670683
That issue still remains.
Just in case.
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Intel product: Intel powered classmate PC v: Clamshell
serial: <superuser required> Chassis: NULL type: 9 v: 0.1 serial: <superuser required>
Mobo: Intel model: Intel powered classmate PC v: Clamshell serial: <superuser required>
UEFI: Phoenix v: MPBYT10A.88F.0039.2016.0622.1403 date: 06/22/2016
Battery:
ID-1: BAT1 charge: 27.7 Wh (86.0%) condition: 32.2/36.6 Wh (87.9%) volts: 11.6 min: 11.1
model: ECS CMPC type: Li-ion serial: <filter> status: discharging
CPU:
Info: model: Intel Celeron N2808 bits: 64 type: MCP arch: Silvermont level: v2 built: 2013-15
process: Intel 22nm family: 6 model-id: 0x37 (55) stepping: 8 microcode: 0x838
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB desc: d-2x24 KiB; i-2x32 KiB
L2: 1024 KiB desc: 1x1024 KiB
Speed (MHz): avg: 568 high: 636 min/max: 500/2249 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 500 2: 636 bogomips: 6333
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Elite Systems
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: eDP-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0f31 class-ID: 0300
Device-2: Chicony USB 2.0 Camera type: USB driver: uvcvideo bus-ID: 1-3.1:5 chip-ID: 04f2:b445
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1040 built: 2013 res: 1366x768 hz: 60 dpi: 156
gamma: 1.2 size: 222x125mm (8.74x4.92") diag: 255mm (10") ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (BYT) direct-render: Yes
Audio:
Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio vendor: Elite Systems
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:0f04 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: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel modules: wl
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 01:00.0 chip-ID: 10ec:b723
class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Elite Systems driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 02:00.0 chip-ID: 10ec:8136
class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Realtek RTL8723B Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-3.3:7
chip-ID: 0bda:b723 class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 9 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 9f73 hci-v: 4.0 rev: e2f
Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 465.76 GiB used: 44.1 GiB (9.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000LPCX-22VHAT0 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 1A01 scheme: GPT
Partition:
ID-1: / raw-size: 39.06 GiB size: 38.15 GiB (97.67%) used: 6.58 GiB (17.3%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 4.9 MiB (1.0%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 301 GiB size: 295.21 GiB (98.08%) used: 37.51 GiB (12.7%) fs: ext4
dev: /dev/sda4 maj-min: 8:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.01 GiB used: 6.6 MiB (0.1%) priority: -2 dev: /dev/sda6
maj-min: 8:6
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2060 libs: 1041 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://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 196 Uptime: 1d 7h 14m wakeups: 20 Memory: 3.7 GiB used: 1.69 GiB (45.6%)
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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Sun Jun 25, 2023 5:59 pm
by Somewhat Reticent
Updated a stick to the latest Ventoy version (using GUI), generated modified ISO snapshots.
From mod-ISO used MXPI to add handbrake, libbdplus, libbluray, libdvdcss;
used
copy/paste (substituting Bookworm for Bullseye) to add makemkv via deb.
Test rig couldn't play Blu-ray disc directly (can't play 1080p with vlc) but handbrake-shrunk 480p played OK.
Re: How can I disable os-prober in MX-23 beta 2
Posted: Mon Jun 26, 2023 2:35 am
by wizardfromoz
Hello. I downloaded and installed the XFCE version.
My situation is rather unique in that I run 76 Linux Distros on this Dell rig.
My practice with other Distros is to modify or add a line in /etc/default/grub to show
but I cannot do that here, and have it work, in MX-23 Beta2.
Why is this so important? Because os-prober takes, as per my document
MX-23 Beta 2 - HDD
real 130m2.718s
NOTE - when os-prober disabled (moved /etc/grub.d/30_os-prober to Documents)
real 4m41.887s , saved 2hr 5min 20sec !!
System Info as follows
Code: Select all
[CODE]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 noquiet nosplash
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Dell product: Inspiron 5770 v: N/A serial: <superuser required> Chassis:
type: 10 serial: <superuser required>
Mobo: Dell model: 0XH3XD v: A00 serial: <superuser required> UEFI: Dell v: 1.1.5
date: 04/03/2018
Battery:
ID-1: BAT0 charge: 39.9 Wh (100.0%) condition: 39.9/42.0 Wh (95.0%) volts: 12.6 min: 11.4
model: SMP DELL Y3F7Y6B type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Coffee Lake gen: core 8 level: v3
note: check built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 0xA (10)
microcode: 0xF2
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 800 min/max: 400/4000 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 31999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300
Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 M440/M445 530/535 620/625 Mobile]
vendor: Dell driver: amdgpu v: kernel arch: GCN-3 code: Volcanic Islands process: TSMC 28nm
built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 8
bus-ID: 01:00.0 chip-ID: 1002:6900 class-ID: 0380 temp: 53.0 C
Device-3: Realtek Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-5:3 chip-ID: 0bda:568a
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: amdgpu,modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: AU Optronics 0x139d built: 2017 res: 1920x1080 hz: 60 dpi: 128
gamma: 1.2 size: 381x214mm (15x8.43") diag: 437mm (17.2") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
direct-render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 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: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell
driver: ath10k_pci v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
chip-ID: 168c:0042 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-7:5 chip-ID: 0cf3:e009
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 25a hci-v: 4.2
Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060
bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
Local Storage: total: 5.69 TiB used: 44.76 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000LM007-1R8174 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: SDM2 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Micron model: 1100 SATA 256GB size: 238.47 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: L022 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital model: WD40EZRZ-00GXCB0
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
rev: 4004 scheme: GPT
Partition:
ID-1: / raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 12.06 GiB (61.8%) fs: ext4
dev: /dev/sda30 maj-min: 259:14
ID-2: /boot/efi raw-size: 1023.3 MiB size: 1021.3 MiB (99.80%) used: 505.9 MiB (49.5%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 54.0 C pch: 49.5 C mobo: 48.0 C sodimm: SODIMM C gpu: amdgpu
temp: 54.0 C
Fan Speeds (RPM): cpu: 2775
Repos:
Packages: pm: dpkg pkgs: 2150 libs: 1116 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
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 293 Uptime: 1h 20m wakeups: 105 Memory: 15.52 GiB used: 3.72 GiB (23.9%)
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: UEFI
[/code]
I have a rather cumbersome workaround for this at the moment
Workaround for now to disable os-prober
1. Modify /etc/default/grub to comment out last three of four lines, ie edit to
#if [ -e /etc/default/grub.mx-defaults ]; then
# . /etc/default/grub.mx-defaults
#fi
2. Move grub.mx-defaults from /etc/default to Documents
3. Move 30_os-prober script from /etc/grub.d to Documents.
This then, reduces updating grub by time 2 hours.
Output, then, is
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/mytheme.txt
Found linux image: /boot/vmlinuz-6.1.0-9-amd64
Found initrd image: /boot/initrd.img-6.1.0-9-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
To re-enable, reverse the steps.
I also wonder why the change from previous versions, on this subject.
Thanks
Chris Turner
wizardfromoz
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 3:15 am
by pbear
There's a much simpler way to disable OS prober: sudo chmod -x /etc/grub.d/30_os-prober. Put a comment in /etc/default/grub so you will remember what you've done. If you prefer to move it, I suggest /root (the home folder of user-root) makes more sense than Documents. What changed, by the way, is a perception by the Grub developers (about a year ago?) that os-prober is a potential security risk.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 5:00 am
by asqwerth
I know exactly how @wizardfromoz feels, though I "only" have 15 distros instead of 76. I find the time to generate grub.cfg for 15 distros is already long, so it must be an eternity for you.
As for why the change, it's because Debian decided for Bookworm that even if you manually enabled os-prober, they would disable that again at the next update of the grub package.
Unfortunately MX Devs' solution is to make the exact opposite: even if a user manually disabled os_prober with that line, it would be ignored. That was done, presumably, because many newcomers use MX and they would keep asking after every update of grub, "where is my Windows menu entry?" or "where are my other distros?"
So for the sake of a general solution that suits the majority of use cases, I'm doing what the devs advised and have made a note in my MX install notes going forward to simply make the op-prober script unexecutable.
The thing is that in Arch-based distros, os_prober is not enabled by default (has been like this for ages) but the expectation is that users have to be more proactive and knowledgeable and sort out their own boot setups.
[ADDED] It may not be that helpful to move that os_prober script to Documents. When an update to grub package is installed, that script could be re-added back to /etc/grub.d/
It happens all the time to me in my Manjaro install (which controls my grub), because I rename the 41_custom script to 09 in order that my custom entries appear before those in grub.cfg. However after every update of grub package, 41_custom is restored and I get a super-long grub menu with custom entries, then grub.cfg entries, then custom entries again (until I delete 41_custom yet again).
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 5:35 am
by AK-47
asqwerth wrote: Mon Jun 26, 2023 5:00 amUnfortunately MX Devs' solution is to make the exact opposite: even if a user manually disabled os_prober with that line, it would be ignored. That was done, presumably, because many newcomers use MX and they would keep asking after every update of grub, "where is my Windows menu entry?" or "where are my other distros?"
As a Windows user, I can honestly say that the os-prober hasn't been useful, so I agree. You can add custom menus by adding them to /etc/grub.d/40_custom which is what I do and I like that predictability.
I hope this decision is reconsidered. If a "newbie" is sextuple booting multiple distros, I dare say they already know what they're doing. Even someone like me who jumped straight from Windows, enough googling got me where I needed, and it was even easier than dealing with the silly bcdedit nonsense in Windows.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 5:36 am
by i_ri
hello dolphin_oracle
mx-installer
On the --oem switch is that a circumstance where
on the installation complete dialog
"Automatically Reboot ..." is deselected by default?
or without checkbox.(?)
Re: How can I disable os-prober in MX-23 beta 2
Posted: Mon Jun 26, 2023 6:09 am
by fehlix
wizardfromoz wrote: Mon Jun 26, 2023 2:35 am
My practice with other Distros is to modify or add a line in /etc/default/grub to show
but I cannot do that here, and have it work, in MX-23 Beta2.
Why is this so important? Because os-prober takes, as per my document
I have a rather cumbersome workaround for this at the moment
Workaround for now to disable os-prober
This then, reduces updating grub by time 2 hours.
I also wonder why the change from previous versions, on this subject.
Thanks
Debian did some changes to always have disabled os prober during GRUB upgrade by default.
The way to disable / enabled OS prober have been changed in MX-23.
Instead of adjusting GRUB_DISABLE_OS_PROBER with /etc/default/grub,
one would set flag within the debconf-database.
One way todo this:
and select/de-select the correspoding os-prober related option.
+++EDIT+++
Or just set the os-prober related flag within debconf db directly:
E.g here with disabled os-prober:
Code: Select all
echo "grub-pc grub2/enable_os_prober boolean false" | sudo debconf-set-selections
or here with enabled os-pober
Code: Select all
echo "grub-pc grub2/enable_os_prober boolean true" | sudo debconf-set-selections
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:10 am
by asqwerth
AK-47 wrote: Mon Jun 26, 2023 5:35 am
asqwerth wrote: Mon Jun 26, 2023 5:00 amUnfortunately MX Devs' solution is to make the exact opposite: even if a user manually disabled os_prober with that line, it would be ignored. That was done, presumably, because many newcomers use MX and they would keep asking after every update of grub, "where is my Windows menu entry?" or "where are my other distros?"
As a Windows user, I can honestly say that the os-prober hasn't been useful, so I agree. You can add custom menus by adding them to /etc/grub.d/40_custom which is what I do and I like that predictability.
I hope this decision is reconsidered. If a "newbie" is sextuple booting multiple distros, I dare say they already know what they're doing. Even someone like me who jumped straight from Windows, enough googling got me where I needed, and it was even easier than dealing with the silly bcdedit nonsense in Windows.
creating a /boot/grub/custom.cfg file and depending on 41_custom script is better than editing 40_custom script , in my opinion. No need to run sudo update-grub after any change to custom.cfg ! Unlike when you edit 40_custom.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:12 am
by fehlix
asqwerth wrote: Mon Jun 26, 2023 5:00 am
Unfortunately MX Devs' solution is to make the exact opposite: even if a user manually disabled os_prober with that line, it would be ignored. That was done, presumably, because many newcomers use MX and they would keep asking after every update of grub, "where is my Windows menu entry?" or "where are my other distros?"
As mentioned the way to disable os-prober has been changed.
Instead of changing with /etc/default/grub,
adjust the os-prober related flag within debconf.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:25 am
by asqwerth
fehlix wrote: Mon Jun 26, 2023 6:12 am
asqwerth wrote: Mon Jun 26, 2023 5:00 am
Unfortunately MX Devs' solution is to make the exact opposite: even if a user manually disabled os_prober with that line, it would be ignored. That was done, presumably, because many newcomers use MX and they would keep asking after every update of grub, "where is my Windows menu entry?" or "where are my other distros?"
As mentioned the way to disable os-prober has been changed.
Instead of changing with /etc/default/grub,
adjust the os-prober related flag within debconf.
No ordinary user will know that unless it's documented somewhere, and so far in MX23 alpha/betas, this has not been made clear.
or maybe MX Boot Options can have an added function to help us do it? It seems appropriate to have a tool to reenable the default grub behaviour, since we (MX) are forcing os_prober to be run against the latest standard behaviour of grub.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:34 am
by fehlix
asqwerth wrote: Mon Jun 26, 2023 6:25 am
fehlix wrote: Mon Jun 26, 2023 6:12 am
asqwerth wrote: Mon Jun 26, 2023 5:00 am
Unfortunately MX Devs' solution is to make the exact opposite: even if a user manually disabled os_prober with that line, it would be ignored. That was done, presumably, because many newcomers use MX and they would keep asking after every update of grub, "where is my Windows menu entry?" or "where are my other distros?"
As mentioned the way to disable os-prober has been changed.
Instead of changing with /etc/default/grub,
adjust the os-prober related flag within debconf.
No ordinary user will know that unless it's documented somewhere, and so far in MX23 alpha/betas, this has not been made clear.
or maybe MX Boot Options can have an added function to help us do it? It seems appropriate to have a tool to reenable the default grub behaviour, since we (MX) are forcing os_prober to be run against the latest standard behaviour of grub.
Debian disabled os-prober, mentioned with Dbeian 12 news. For people relying
on other os-menu entry in grub menu, would face the sitiation to beeing locked out. Hnce the reverted adjstments made. Doesn't stop to add this information or to MX Tools to how handle os-prober in MX23.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:38 am
by asqwerth
@fehlix I mean that the solution to/instructions on how to actually disable os_prober in MX23 has to be properly documented, since we are removing the default Debian12 behaviour. Some users (obviously not just me) actually want the new default behaviour.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:40 am
by dolphin_oracle
i_ri wrote: Mon Jun 26, 2023 5:36 am
hello dolphin_oracle
mx-installer
On the --oem switch is that a circumstance where
on the installation complete dialog
"Automatically Reboot ..." is deselected by default?
or without checkbox.(?)
No checkbox but will reboot
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 6:59 am
by i_ri
hello dolphin_oracle
no reboot. job done. unplug. box. (?)
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 10:09 am
by i_ri
hello dolphin_oracle
mx-installer 23.6.06
The systemd failure to load that i had [23.6.05]
is consistent with installations done with the --oem switch.
sysV can also not work with oem install. [23.6.06]
installations without the oem switch work just fine.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 11:09 am
by Senpai
Hi:
I have installed MX23 Fluxbox_beta2_386, and in the 1st update I see some "Broken pipe" (Tubería rota) errors in the module update "rtl8812**-dkms", which I attach with the .log of the "apt/term.log.
As I had problems on my PC with kernel 6.0 and now on 6.1, (
viewtopic.php?p=730972#p730972) I'm not sure if it's a beta2 issue or something related to those modules in particular...
Code: Select all
System:
Kernel: 6.1.0-9-686-pae [6.1.27-1] arch: i686 bits: 32 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-686-pae root=UUID=<filter> ro quiet splash
Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0
Distro: MX-23_fluxbox_beta2_386 Libretto June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Other-vm? System: Acer product: Aspire 5715Z v: V1.45 serial: <superuser required>
Mobo: Acer model: Acadia v: V1.45 serial: <superuser required> BIOS: Acer v: 1.45
date: 11/10/2008
Battery:
ID-1: BAT0 charge: 0% condition: 24.0/48.8 Wh (49.2%) volts: 10.4 min: 11.1
model: SANYO GC86508SAT0 type: Li-ion serial: N/A status: discharging
CPU:
Info: model: Intel Pentium Dual T2370 bits: 64 type: MCP arch: Core2 Merom built: 2006-09
process: Intel 65nm family: 6 model-id: 0xF (15) stepping: 0xD (13) microcode: 0xA4
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
L2: 1024 KiB desc: 1x1024 KiB
Speed (MHz): avg: 798 min/max: 800/1733 scaling: driver: acpi-cpufreq governor: ondemand cores:
1: 798 2: 798 bogomips: 6916
Flags: ht lm nx pae sse sse2 sse3 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Acer Incorporated ALI driver: N/A
alternate: i915 arch: Gen-4 process: Intel 65n built: 2006-07 bus-ID: 00:02.0 chip-ID: 8086:2a02
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: vesa dri: swrast gpu: N/A
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 78 s-size: 333x212mm (13.11x8.35") s-diag: 395mm (15.54")
Monitor-1: default res: 1024x768 size: N/A modes: N/A
API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 128 bits) direct-render: Yes
Audio:
Device-1: Intel 82801H HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:284b class-ID: 0403
API: ALSA v: k6.1.0-9-686-pae 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: Broadcom NetLink BCM5906M Fast Ethernet PCI Express vendor: Acer Incorporated ALI
driver: tg3 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0
chip-ID: 14e4:1713 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter vendor: AMBIT Microsystem
AR5BXB63 802.11bg NIC driver: ath5k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 06:00.0 chip-ID: 168c:001c class-ID: 0200
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 5.19 GiB (1.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS547550A9E384 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: A60A
scheme: MBR
Partition:
ID-1: / raw-size: 60 GiB size: 58.76 GiB (97.93%) used: 5.19 GiB (8.8%) fs: ext4 dev: /dev/sda5
maj-min: 8:5
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 4 GiB used: 1.8 MiB (0.0%) priority: -2 dev: /dev/sda1
maj-min: 8:1
Sensors:
System Temperatures: cpu: 62.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 1794 libs: 876 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://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ bookworm main non-free
Info:
Processes: 172 Uptime: 1h 3m wakeups: 3 Memory: 1.96 GiB used: 716.2 MiB (35.8%) 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)
Code: Select all
Log started: 2023-06-26 10:56:35
(Leyendo la base de datos ...
(Leyendo la base de datos ... 5%
(Leyendo la base de datos ... 10%
(Leyendo la base de datos ... 15%
(Leyendo la base de datos ... 20%
(Leyendo la base de datos ... 25%
(Leyendo la base de datos ... 30%
(Leyendo la base de datos ... 35%
(Leyendo la base de datos ... 40%
(Leyendo la base de datos ... 45%
(Leyendo la base de datos ... 50%
(Leyendo la base de datos ... 55%
(Leyendo la base de datos ... 60%
(Leyendo la base de datos ... 65%
(Leyendo la base de datos ... 70%
(Leyendo la base de datos ... 75%
(Leyendo la base de datos ... 80%
(Leyendo la base de datos ... 85%
(Leyendo la base de datos ... 90%
(Leyendo la base de datos ... 95%
(Leyendo la base de datos ... 100%
(Leyendo la base de datos ... 288897 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../00-custom-toolbox_23.6.01_i386.deb ...
Desempaquetando custom-toolbox (23.6.01) sobre (0.23.6) ...
Preparando para desempaquetar .../01-ddm-mx_23.06.01_all.deb ...
Desempaquetando ddm-mx (23.06.01) sobre (23.03.05) ...
Preparando para desempaquetar .../02-featherpad-l10n_1.4.1-0.1~mx23+1_all.deb ...
Desempaquetando featherpad-l10n (1.4.1-0.1~mx23+1) sobre (1.4.0-0.1~mx23+1) ...
Preparando para desempaquetar .../03-featherpad_1.4.1-0.1~mx23+1_i386.deb ...
Desempaquetando featherpad (1.4.1-0.1~mx23+1) sobre (1.4.0-0.1~mx23+1) ...
Preparando para desempaquetar .../04-firefox_114.0.2~mozillabinaries-1mx23+1_i386.deb ...
Desempaquetando firefox (114.0.2~mozillabinaries-1mx23+1) sobre (114.0.1~mozillabinaries-1mx23+1) ...
Preparando para desempaquetar .../05-mx-conky-data_20230601_all.deb ...
Desempaquetando mx-conky-data (20230601) sobre (20230501) ...
Preparando para desempaquetar .../06-mx-docs_20230614mx23_all.deb ...
Desempaquetando mx-docs (20230614mx23) sobre (20230609mx23) ...
Preparando para desempaquetar .../07-mx-fluxbox_23.06.05mx23_all.deb ...
Desempaquetando mx-fluxbox (23.06.05mx23) sobre (23.06.04mx23) ...
Preparando para desempaquetar .../08-mx-fluxbox-data_23.06.05mx23_all.deb ...
Desempaquetando mx-fluxbox-data (23.06.05mx23) sobre (23.06.04mx23) ...
Preparando para desempaquetar .../09-mxfb-accessories_23.06.10_all.deb ...
Desempaquetando mxfb-accessories (23.06.10) sobre (23.05.09mx23) ...
Preparando para desempaquetar .../10-mx-installer_23.6.06mx23_i386.deb ...
Desempaquetando mx-installer (23.6.06mx23) sobre (23.6.02mx23) ...
Preparando para desempaquetar .../11-mx-iso-template_23.06.01mx23_i386.deb ...
Desempaquetando mx-iso-template (23.06.01mx23) sobre (23.05.02mx23) ...
Preparando para desempaquetar .../12-mx-repo-list_23.6_all.deb ...
Desempaquetando mx-repo-list (23.6) sobre (23.5.01) ...
Preparando para desempaquetar .../13-mx-snapshot_23.6_i386.deb ...
Desempaquetando mx-snapshot (23.6) sobre (23.5.05) ...
Preparando para desempaquetar .../14-rtl8812au-dkms_5.13.6+git20230615-1~mx23_all.deb ...
Module 8812au-5.13.6 for kernel 6.1.0-9-686-pae (i686).
Before uninstall, this module version was ACTIVE on this kernel.
8812au.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-9-686-pae/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.......
Deleting module 8812au-5.13.6 completely from the DKMS tree.
Desempaquetando rtl8812au-dkms (5.13.6+git20230615-1~mx23) sobre (5.13.6+git20221020-1~mx21) ...
Preparando para desempaquetar .../15-rtl8821ce-dkms_5.5.2.1+git20230504-0~mx23+1_all.deb ...
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Module rtl8821ce-5.5.2.1+git20221215 for kernel 6.1.0-9-686-pae (i686).
Before uninstall, this module version was ACTIVE on this kernel.
rtl8821ce.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-9-686-pae/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module rtl8821ce-5.5.2.1+git20221215 completely from the DKMS tree.
Desempaquetando rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) sobre (5.5.2.1+git20221215-0.1~mx21+1) ...
Preparando para desempaquetar .../16-rtl8821cu-dkms_5.12.0+git20230215-1~mx23+3_all.deb ...
Module rtl8821cu-5.12.0 for kernel 6.1.0-9-686-pae (i686).
Before uninstall, this module version was ACTIVE on this kernel.
8821cu.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-9-686-pae/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Desempaquetando rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) sobre (5.12.0+git20230215-1~mx21+1) ...
Preparando para desempaquetar .../17-plymouth-themes-mx_23.06.03_all.deb ...
Desempaquetando plymouth-themes-mx (23.06.03) sobre (23.06.01) ...
Configurando firefox (114.0.2~mozillabinaries-1mx23+1) ...
Configurando mx-installer (23.6.06mx23) ...
Configurando mx-iso-template (23.06.01mx23) ...
Configurando mx-fluxbox-data (23.06.05mx23) ...
found x86 arch, using mx defaults
Configurando rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) ...
Loading new rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/usr/src/rtl8821ce-5.5.2.1+git20230504/dkms.conf)
Building for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Building initial module for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Done.
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
rtl8821ce.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-686-pae/updates/dkms/
depmod....
Configurando rtl8812au-dkms (5.13.6+git20230615-1~mx23) ...
Creating symlink /var/lib/dkms/8812au/5.13.6/source -> /usr/src/8812au-5.13.6
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
./dkms-make.sh.......................................................................................................................................................................................................................................
Signing module /var/lib/dkms/8812au/5.13.6/build/8812au.ko
Cleaning build area...
8812au.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-686-pae/updates/dkms/
depmod....
Finished running dkms install steps.
Configurando mxfb-accessories (23.06.10) ...
Configurando featherpad-l10n (1.4.1-0.1~mx23+1) ...
Configurando ddm-mx (23.06.01) ...
Configurando rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) ...
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Building for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Building initial module for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Done.
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-686-pae/updates/dkms/
depmod...
Configurando mx-docs (20230614mx23) ...
Configurando mx-snapshot (23.6) ...
Configurando mx-conky-data (20230601) ...
Configurando custom-toolbox (23.6.01) ...
Configurando mx-repo-list (23.6) ...
Configurando plymouth-themes-mx (23.06.03) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-9-686-pae
I: The initramfs will attempt to resume from /dev/sda1
I: (UUID=476ef026-c294-4c27-942c-20ffe28073e0)
I: Set the RESUME variable to override this.
Configurando featherpad (1.4.1-0.1~mx23+1) ...
Configurando mx-fluxbox (23.06.05mx23) ...
fluxbox ya estaba fijado como instalado manualmente.
mx-fluxbox-data ya estaba fijado como instalado manualmente.
mx-idesktool ya estaba fijado como instalado manualmente.
wmalauncher ya estaba fijado como instalado manualmente.
moka-icon-theme ya estaba fijado como instalado manualmente.
lxappearance no se puede marcar porque no está instalado.
gkrellm ya estaba fijado como instalado manualmente.
mxfb-art no se puede marcar porque no está instalado.
mx-dockmaker ya estaba fijado como instalado manualmente.
mxfb-docs ya estaba fijado como instalado manualmente.
rofi ya estaba fijado como instalado manualmente.
rofi-calc ya estaba fijado como instalado manualmente.
mx-fluxbox-about no se puede marcar porque no está instalado.
mx-rofi-manager ya estaba fijado como instalado manualmente.
tint2 ya estaba fijado como instalado manualmente.
Procesando disparadores para mailcap (3.70+nmu1) ...
Procesando disparadores para desktop-file-utils (0.26-1) ...
Procesando disparadores para hicolor-icon-theme (0.17-2) ...
Procesando disparadores para man-db (2.11.2-2) ...
Log ended: 2023-06-26 11:40:32
Best regards
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 11:16 am
by dolphin_oracle
Senpai wrote: Mon Jun 26, 2023 11:09 am
Hi:
I have installed MX23 Fluxbox_beta2_386, and in the 1st update I see some "Broken pipe" (Tubería rota) errors in the module update "rtl8812**-dkms", which I attach with the .log of the "apt/term.log.
As I had problems on my PC with kernel 6.0 and now on 6.1, (
viewtopic.php?p=730972#p730972) I'm not sure if it's a beta2 issue or something related to those modules in particular...
Code: Select all
System:
Kernel: 6.1.0-9-686-pae [6.1.27-1] arch: i686 bits: 32 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-686-pae root=UUID=<filter> ro quiet splash
Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0
Distro: MX-23_fluxbox_beta2_386 Libretto June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Other-vm? System: Acer product: Aspire 5715Z v: V1.45 serial: <superuser required>
Mobo: Acer model: Acadia v: V1.45 serial: <superuser required> BIOS: Acer v: 1.45
date: 11/10/2008
Battery:
ID-1: BAT0 charge: 0% condition: 24.0/48.8 Wh (49.2%) volts: 10.4 min: 11.1
model: SANYO GC86508SAT0 type: Li-ion serial: N/A status: discharging
CPU:
Info: model: Intel Pentium Dual T2370 bits: 64 type: MCP arch: Core2 Merom built: 2006-09
process: Intel 65nm family: 6 model-id: 0xF (15) stepping: 0xD (13) microcode: 0xA4
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
L2: 1024 KiB desc: 1x1024 KiB
Speed (MHz): avg: 798 min/max: 800/1733 scaling: driver: acpi-cpufreq governor: ondemand cores:
1: 798 2: 798 bogomips: 6916
Flags: ht lm nx pae sse sse2 sse3 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Acer Incorporated ALI driver: N/A
alternate: i915 arch: Gen-4 process: Intel 65n built: 2006-07 bus-ID: 00:02.0 chip-ID: 8086:2a02
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: vesa dri: swrast gpu: N/A
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 78 s-size: 333x212mm (13.11x8.35") s-diag: 395mm (15.54")
Monitor-1: default res: 1024x768 size: N/A modes: N/A
API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 128 bits) direct-render: Yes
Audio:
Device-1: Intel 82801H HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:284b class-ID: 0403
API: ALSA v: k6.1.0-9-686-pae 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: Broadcom NetLink BCM5906M Fast Ethernet PCI Express vendor: Acer Incorporated ALI
driver: tg3 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0
chip-ID: 14e4:1713 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter vendor: AMBIT Microsystem
AR5BXB63 802.11bg NIC driver: ath5k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 06:00.0 chip-ID: 168c:001c class-ID: 0200
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 5.19 GiB (1.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS547550A9E384 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: A60A
scheme: MBR
Partition:
ID-1: / raw-size: 60 GiB size: 58.76 GiB (97.93%) used: 5.19 GiB (8.8%) fs: ext4 dev: /dev/sda5
maj-min: 8:5
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 4 GiB used: 1.8 MiB (0.0%) priority: -2 dev: /dev/sda1
maj-min: 8:1
Sensors:
System Temperatures: cpu: 62.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 1794 libs: 876 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://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ bookworm main non-free
Info:
Processes: 172 Uptime: 1h 3m wakeups: 3 Memory: 1.96 GiB used: 716.2 MiB (35.8%) 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)
Code: Select all
Log started: 2023-06-26 10:56:35
(Leyendo la base de datos ...
(Leyendo la base de datos ... 5%
(Leyendo la base de datos ... 10%
(Leyendo la base de datos ... 15%
(Leyendo la base de datos ... 20%
(Leyendo la base de datos ... 25%
(Leyendo la base de datos ... 30%
(Leyendo la base de datos ... 35%
(Leyendo la base de datos ... 40%
(Leyendo la base de datos ... 45%
(Leyendo la base de datos ... 50%
(Leyendo la base de datos ... 55%
(Leyendo la base de datos ... 60%
(Leyendo la base de datos ... 65%
(Leyendo la base de datos ... 70%
(Leyendo la base de datos ... 75%
(Leyendo la base de datos ... 80%
(Leyendo la base de datos ... 85%
(Leyendo la base de datos ... 90%
(Leyendo la base de datos ... 95%
(Leyendo la base de datos ... 100%
(Leyendo la base de datos ... 288897 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../00-custom-toolbox_23.6.01_i386.deb ...
Desempaquetando custom-toolbox (23.6.01) sobre (0.23.6) ...
Preparando para desempaquetar .../01-ddm-mx_23.06.01_all.deb ...
Desempaquetando ddm-mx (23.06.01) sobre (23.03.05) ...
Preparando para desempaquetar .../02-featherpad-l10n_1.4.1-0.1~mx23+1_all.deb ...
Desempaquetando featherpad-l10n (1.4.1-0.1~mx23+1) sobre (1.4.0-0.1~mx23+1) ...
Preparando para desempaquetar .../03-featherpad_1.4.1-0.1~mx23+1_i386.deb ...
Desempaquetando featherpad (1.4.1-0.1~mx23+1) sobre (1.4.0-0.1~mx23+1) ...
Preparando para desempaquetar .../04-firefox_114.0.2~mozillabinaries-1mx23+1_i386.deb ...
Desempaquetando firefox (114.0.2~mozillabinaries-1mx23+1) sobre (114.0.1~mozillabinaries-1mx23+1) ...
Preparando para desempaquetar .../05-mx-conky-data_20230601_all.deb ...
Desempaquetando mx-conky-data (20230601) sobre (20230501) ...
Preparando para desempaquetar .../06-mx-docs_20230614mx23_all.deb ...
Desempaquetando mx-docs (20230614mx23) sobre (20230609mx23) ...
Preparando para desempaquetar .../07-mx-fluxbox_23.06.05mx23_all.deb ...
Desempaquetando mx-fluxbox (23.06.05mx23) sobre (23.06.04mx23) ...
Preparando para desempaquetar .../08-mx-fluxbox-data_23.06.05mx23_all.deb ...
Desempaquetando mx-fluxbox-data (23.06.05mx23) sobre (23.06.04mx23) ...
Preparando para desempaquetar .../09-mxfb-accessories_23.06.10_all.deb ...
Desempaquetando mxfb-accessories (23.06.10) sobre (23.05.09mx23) ...
Preparando para desempaquetar .../10-mx-installer_23.6.06mx23_i386.deb ...
Desempaquetando mx-installer (23.6.06mx23) sobre (23.6.02mx23) ...
Preparando para desempaquetar .../11-mx-iso-template_23.06.01mx23_i386.deb ...
Desempaquetando mx-iso-template (23.06.01mx23) sobre (23.05.02mx23) ...
Preparando para desempaquetar .../12-mx-repo-list_23.6_all.deb ...
Desempaquetando mx-repo-list (23.6) sobre (23.5.01) ...
Preparando para desempaquetar .../13-mx-snapshot_23.6_i386.deb ...
Desempaquetando mx-snapshot (23.6) sobre (23.5.05) ...
Preparando para desempaquetar .../14-rtl8812au-dkms_5.13.6+git20230615-1~mx23_all.deb ...
Module 8812au-5.13.6 for kernel 6.1.0-9-686-pae (i686).
Before uninstall, this module version was ACTIVE on this kernel.
8812au.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-9-686-pae/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.......
Deleting module 8812au-5.13.6 completely from the DKMS tree.
Desempaquetando rtl8812au-dkms (5.13.6+git20230615-1~mx23) sobre (5.13.6+git20221020-1~mx21) ...
Preparando para desempaquetar .../15-rtl8821ce-dkms_5.5.2.1+git20230504-0~mx23+1_all.deb ...
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20221215/source/dkms.conf)
Module rtl8821ce-5.5.2.1+git20221215 for kernel 6.1.0-9-686-pae (i686).
Before uninstall, this module version was ACTIVE on this kernel.
rtl8821ce.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-9-686-pae/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module rtl8821ce-5.5.2.1+git20221215 completely from the DKMS tree.
Desempaquetando rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) sobre (5.5.2.1+git20221215-0.1~mx21+1) ...
Preparando para desempaquetar .../16-rtl8821cu-dkms_5.12.0+git20230215-1~mx23+3_all.deb ...
Module rtl8821cu-5.12.0 for kernel 6.1.0-9-686-pae (i686).
Before uninstall, this module version was ACTIVE on this kernel.
8821cu.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-9-686-pae/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module rtl8821cu-5.12.0 completely from the DKMS tree.
Desempaquetando rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) sobre (5.12.0+git20230215-1~mx21+1) ...
Preparando para desempaquetar .../17-plymouth-themes-mx_23.06.03_all.deb ...
Desempaquetando plymouth-themes-mx (23.06.03) sobre (23.06.01) ...
Configurando firefox (114.0.2~mozillabinaries-1mx23+1) ...
Configurando mx-installer (23.6.06mx23) ...
Configurando mx-iso-template (23.06.01mx23) ...
Configurando mx-fluxbox-data (23.06.05mx23) ...
found x86 arch, using mx defaults
Configurando rtl8821ce-dkms (5.5.2.1+git20230504-0~mx23+1) ...
Loading new rtl8821ce-5.5.2.1+git20230504 DKMS files...
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/usr/src/rtl8821ce-5.5.2.1+git20230504/dkms.conf)
Building for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Building initial module for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Done.
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
rtl8821ce.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-686-pae/updates/dkms/
depmod....
Configurando rtl8812au-dkms (5.13.6+git20230615-1~mx23) ...
Creating symlink /var/lib/dkms/8812au/5.13.6/source -> /usr/src/8812au-5.13.6
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
./dkms-make.sh.......................................................................................................................................................................................................................................
Signing module /var/lib/dkms/8812au/5.13.6/build/8812au.ko
Cleaning build area...
8812au.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-686-pae/updates/dkms/
depmod....
Finished running dkms install steps.
Configurando mxfb-accessories (23.06.10) ...
Configurando featherpad-l10n (1.4.1-0.1~mx23+1) ...
Configurando ddm-mx (23.06.01) ...
Configurando rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) ...
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Building for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Building initial module for 6.1.0-9-686-pae
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
Done.
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
/usr/sbin/dkms: línea 2497: echo: error de escritura: Tubería rota
8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-686-pae/updates/dkms/
depmod...
Configurando mx-docs (20230614mx23) ...
Configurando mx-snapshot (23.6) ...
Configurando mx-conky-data (20230601) ...
Configurando custom-toolbox (23.6.01) ...
Configurando mx-repo-list (23.6) ...
Configurando plymouth-themes-mx (23.06.03) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-9-686-pae
I: The initramfs will attempt to resume from /dev/sda1
I: (UUID=476ef026-c294-4c27-942c-20ffe28073e0)
I: Set the RESUME variable to override this.
Configurando featherpad (1.4.1-0.1~mx23+1) ...
Configurando mx-fluxbox (23.06.05mx23) ...
fluxbox ya estaba fijado como instalado manualmente.
mx-fluxbox-data ya estaba fijado como instalado manualmente.
mx-idesktool ya estaba fijado como instalado manualmente.
wmalauncher ya estaba fijado como instalado manualmente.
moka-icon-theme ya estaba fijado como instalado manualmente.
lxappearance no se puede marcar porque no está instalado.
gkrellm ya estaba fijado como instalado manualmente.
mxfb-art no se puede marcar porque no está instalado.
mx-dockmaker ya estaba fijado como instalado manualmente.
mxfb-docs ya estaba fijado como instalado manualmente.
rofi ya estaba fijado como instalado manualmente.
rofi-calc ya estaba fijado como instalado manualmente.
mx-fluxbox-about no se puede marcar porque no está instalado.
mx-rofi-manager ya estaba fijado como instalado manualmente.
tint2 ya estaba fijado como instalado manualmente.
Procesando disparadores para mailcap (3.70+nmu1) ...
Procesando disparadores para desktop-file-utils (0.26-1) ...
Procesando disparadores para hicolor-icon-theme (0.17-2) ...
Procesando disparadores para man-db (2.11.2-2) ...
Log ended: 2023-06-26 11:40:32
Best regards
its an issue in the dkms script, and I'm not sure why its a problem for some dkms packages and not others, but its a failure on a sanity check checking for the existene of something before proceeding. in almost all cases, that something exists, sot he check doesn't even really do anything.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 2:29 pm
by gRegNfo
davidy wrote: Sun Jun 25, 2023 12:15 am
If your hardware likes the ahs releases will it be OK to run these betas? I just realized that when updating kernels from an ahs one, that works, one should stick with ahs. Not sure how MX-23 relates to the liquorix kernels, if at all.
I have 2013 hardware, and it likes the AHS kernel a lot! :) feels more responsive maybe it's me...
My problem is the nVidia support... It will be a pain to get it working, but I won't stop!
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 2:32 pm
by gRegNfo
dolphin_oracle wrote: Sat Jun 24, 2023 11:15 pm
i_ri wrote: Sat Jun 24, 2023 11:00 pm
hello dolphin_oracle
systemd
i reported that kde not running on systemd.
now turned to xfce trial using systemd does not start.
forced into root account it says it is hung on power manager.
no shutdown buttons are all broken.
halt.
back to sysV everything works sysV.
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: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23_beta2_x64 Libretto June 15
2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: HP-Pavilion product: AY022AA-ABA p6330f v: N/A serial: <superuser required>
Chassis: Hewlett-Packard type: 3 serial: <superuser required>
Mobo: MSI model: IONA v: 1.0 serial: <superuser required> BIOS: American Megatrends v: 5.15
date: 06/25/2010
CPU:
Info: model: Intel Core i3 530 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1455 high: 1459 min/max: 1200/2933 scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 1455 2: 1459 3: 1448 4: 1459 bogomips: 23410
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: crocus gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: VGA-1 mapped: VGA1 model: AOC 2436 serial: <filter> built: 2010 res: 1920x1080
hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d800 bus-ID: 01:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: c080 bus-ID: 00:1f.2
chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 1.82 TiB used: 15.21 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ABB0
scheme: MBR
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.79 TiB (98.37%) used: 15.21 GiB (0.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: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 30.2 C mobo: 21.6 C
Fan Speeds (RPM): cpu: 821 fan-2: 866 fan-3: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.33 vbat: 3.28
Repos:
Packages: pm: dpkg pkgs: 2189 libs: 1118 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 201 Uptime: 18m wakeups: 1 Memory: 7.62 GiB used: 1.25 GiB (16.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)
I cannot duplicate. I suggest checking for unfinished updates.
It looks like an ACPI problem, right?
Maybe look more into updating those drivers and firmwares?
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 3:09 pm
by gRegNfo
dolphin_oracle wrote: Mon Jun 26, 2023 11:16 am
Senpai wrote: Mon Jun 26, 2023 11:09 am
Hi:
I have installed MX23 Fluxbox_beta2_386, and in the 1st update I see some "Broken pipe" (Tubería rota) errors in the module update "rtl8812**-dkms", which I attach with the .log of the "apt/term.log.
As I had problems on my PC with kernel 6.0 and now on 6.1, (
viewtopic.php?p=730972#p730972) I'm not sure if it's a beta2 issue or something related to those modules in particular...
Best regards
its an issue in the dkms script, and I'm not sure why its a problem for some dkms packages and not others, but its a failure on a sanity check checking for the existene of something before proceeding. in almost all cases, that something exists, sot he check doesn't even really do anything.
Hi
Senpai wrote: Mon Jun 26, 2023 11:09 am
I had this same problem with this rtl8812u driver and it's gone now!
And also managed to solve a problem with i915 too!
Take a look here:
viewtopic.php?p=730427#p730427
Make sure you clone that github code and build it.
Then you remove the driver from the kernels you are using, and install it again using the name showed on that cli command.
If my explanation is wrong or incomplete, make sure you message me and I'll try to help you better. It's easy but I also made some mistakes along the way!
I tried a lot of stuff and I'm using a lot of kernels so... please msg me.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 4:13 pm
by daemonspudguy
Quick System Info appears to have broken for me.
Code: Select all
Error 22: Unsupported option: --filter-all
Check -h for correct parameters.
Boot Mode: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 4:16 pm
by dolphin_oracle
daemonspudguy wrote: Mon Jun 26, 2023 4:13 pm
Quick System Info appears to have broken for me.
Code: Select all
Error 22: Unsupported option: --filter-all
Check -h for correct parameters.
Boot Mode: UEFI
what version of inxi do you have installed?
Re: MX-23 beta 2 feedback thread
Posted: Mon Jun 26, 2023 4:16 pm
by daemonspudguy
Version: 3.3.26-1-1
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 4:15 am
by wizardfromoz
Thanks to one and all for the input. I have been using antiX and MX since they were in their 14's going to 15.
So I will digest all of the above, in particular the information from @fehlix , check with my Debian Bookworm I also have, and see where I go from there.
Cheers
Wizard
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 8:59 am
by dolphin_oracle
dolphin_oracle wrote: Sat Jun 24, 2023 4:01 pm
user-green wrote: Sat Jun 24, 2023 2:17 am
Dear Developers,
mx-packageinstaller-pkglist (in /usr/share/mx-packageinstaller-pkglist ) does not reflect mx-packageinstaller-description which has been translated at Transifex.
As a result, descriptions are still indicated in default English. See the attached image for reference.
Best regards,
Green
i do not have the tools to import the strings form transifex into the package descriptions. all that was set up by other people. if someone wants to do it and make a pull request to our git hub for mx-packageinstaller-pkglist, I will surely incorporate them.
adrian came to my rescue. any descriptions that have 100% translation complete should now be uploaded in the latest mx-packageinstaller-pkglist update. that was 26 languages. Not all descriptions were online, but 365 were.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 10:13 am
by siamhie
The live boot screen no longer works. All I see is a static image during booting.
mxbo.png
Is it because of the work currently being done?
MX Boot Animation at testing
viewtopic.php?t=73798
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
amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
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 System: Micro-Star product: MS-7C56 v: 2.0 serial: <superuser required>
Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required> UEFI: American
Megatrends LLC. v: A.B0 date: 08/11/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 3800X 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: 0x8701021
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2181 high: 2204 min/max: 2200/4559 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 2200 2: 2199 3: 1961 4: 2200 5: 2200 6: 2200
7: 2200 8: 2200 9: 2200 10: 2200 11: 2199 12: 2204 13: 2200 14: 2200 15: 2134 16: 2200
bogomips: 124803
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 0b:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 mapped: DisplayPort-0 model: HP X27q serial: <filter> built: 2021
res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
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: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel modules: wl pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 8.19 TiB used: 881.17 GiB (10.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital model: WDS500G1X0E-00AFY0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 613000WD temp: 38.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 102000WD temp: 36.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 465.26 GiB size: 456.89 GiB (98.20%) used: 8.78 GiB (1.9%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 572 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 65 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme1n1p1
maj-min: 259:1
Sensors:
System Temperatures: cpu: 34.8 C mobo: N/A gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 774
Repos:
Packages: pm: dpkg pkgs: 2239 libs: 1192 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/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bullseye main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Info:
Processes: 335 Uptime: 6m wakeups: 2 Memory: 31.27 GiB used: 2.35 GiB (7.5%) Init: systemd v: 252
target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 10:47 am
by dolphin_oracle
siamhie wrote: Tue Jun 27, 2023 10:13 am
The live boot screen no longer works. All I see is a static image during booting.
mxbo.png
Is it because of the work currently being done?
MX Boot Animation at testing
viewtopic.php?t=73798
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
amdgpu.ppfeaturemask=0xffffffff init=/lib/systemd/systemd
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 System: Micro-Star product: MS-7C56 v: 2.0 serial: <superuser required>
Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required> UEFI: American
Megatrends LLC. v: A.B0 date: 08/11/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 7 3800X 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: 0x8701021
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2181 high: 2204 min/max: 2200/4559 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 2200 2: 2199 3: 1961 4: 2200 5: 2200 6: 2200
7: 2200 8: 2200 9: 2200 10: 2200 11: 2199 12: 2204 13: 2200 14: 2200 15: 2134 16: 2200
bogomips: 124803
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 0b:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 mapped: DisplayPort-0 model: HP X27q serial: <filter> built: 2021
res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
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: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel modules: wl pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, audio, telephony
Drives:
Local Storage: total: 8.19 TiB used: 881.17 GiB (10.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital model: WDS500G1X0E-00AFY0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 613000WD temp: 38.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 102000WD temp: 36.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 465.26 GiB size: 456.89 GiB (98.20%) used: 8.78 GiB (1.9%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 572 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 65 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme1n1p1
maj-min: 259:1
Sensors:
System Temperatures: cpu: 34.8 C mobo: N/A gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 774
Repos:
Packages: pm: dpkg pkgs: 2239 libs: 1192 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/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bullseye main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Info:
Processes: 335 Uptime: 6m wakeups: 2 Memory: 31.27 GiB used: 2.35 GiB (7.5%) Init: systemd v: 252
target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
maybe but its also possible its just loading very very fast on that machine. I see the animation on my core i7, but its very fast.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 10:49 am
by fehlix
dolphin_oracle wrote: Tue Jun 27, 2023 8:59 am
dolphin_oracle wrote: Sat Jun 24, 2023 4:01 pm
user-green wrote: Sat Jun 24, 2023 2:17 am
Dear Developers,
mx-packageinstaller-pkglist (in /usr/share/mx-packageinstaller-pkglist ) does not reflect mx-packageinstaller-description which has been translated at Transifex.
As a result, descriptions are still indicated in default English. See the attached image for reference.
Best regards,
Green
i do not have the tools to import the strings form transifex into the package descriptions. all that was set up by other people. if someone wants to do it and make a pull request to our git hub for mx-packageinstaller-pkglist, I will surely incorporate them.
adrian came to my rescue. any descriptions that have 100% translation complete should now be uploaded in the latest mx-packageinstaller-pkglist update. that was 26 languages. Not all descriptions were online, but 365 were.
Hmme not sure, e.g Japanese is 100% translated,
trnasifex-pkg-desc_ja.jpg
but still shows description in English:
mxpi-pkd-des_ja.jpg
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 10:52 am
by dolphin_oracle
fehlix wrote: Tue Jun 27, 2023 10:49 am
dolphin_oracle wrote: Tue Jun 27, 2023 8:59 am
dolphin_oracle wrote: Sat Jun 24, 2023 4:01 pm
i do not have the tools to import the strings form transifex into the package descriptions. all that was set up by other people. if someone wants to do it and make a pull request to our git hub for mx-packageinstaller-pkglist, I will surely incorporate them.
adrian came to my rescue. any descriptions that have 100% translation complete should now be uploaded in the latest mx-packageinstaller-pkglist update. that was 26 languages. Not all descriptions were online, but 365 were.
Hmme not sure, e.g Japanese is 100% translated,
trnasifex-pkg-desc_ja.jpg
but still shows description in English:
mxpi-pkd-des_ja.jpg
probably need to remove the ja_JP localization from the pm files.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 11:51 am
by siamhie
dolphin_oracle wrote: Tue Jun 27, 2023 10:47 am
maybe but its also possible its just loading very very fast on that machine. I see the animation on my core i7, but its very fast.
@dolphin_oracle It is fast but I was able to see both lines create the X portion of the logo. I saw it during beta 1 and initially beta 2.
I'll boot to Sys-V to see if there is any difference. (possible I have a service taking it's time to load)
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 11:54 am
by dolphin_oracle
siamhie wrote: Tue Jun 27, 2023 11:51 am
dolphin_oracle wrote: Tue Jun 27, 2023 10:47 am
maybe but its also possible its just loading very very fast on that machine. I see the animation on my core i7, but its very fast.
@dolphin_oracle It is fast but I was able to see both lines create the X portion of the logo. I saw it during beta 1 and initially beta 2.
I'll boot to Sys-V to see if there is any difference. (possible I have a service taking it's time to load)
the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 1:04 pm
by siamhie
dolphin_oracle wrote: Tue Jun 27, 2023 11:54 am
siamhie wrote: Tue Jun 27, 2023 11:51 am
dolphin_oracle wrote: Tue Jun 27, 2023 10:47 am
maybe but its also possible its just loading very very fast on that machine. I see the animation on my core i7, but its very fast.
@dolphin_oracle It is fast but I was able to see both lines create the X portion of the logo. I saw it during beta 1 and initially beta 2.
I'll boot to Sys-V to see if there is any difference. (possible I have a service taking it's time to load)
the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.
@dolphin_oracle I just see a static image (probably loaded by the time the image appears on my screen) when booting to either Sys V or SystemD. Shame because I really liked that animation at boot.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 1:04 pm
by Senpai
gRegNfo wrote: Thu Jun 22, 2023 9:30 pm
UPDATE
Also errors with RTL8812AU (search github for updated drivers of your device - mine is RTL8821CE - for kernel 6x and read the docs)
Code: Select all
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
were removed:
although because of a warning from using build and installed different modules after retries I ended up using:
Code: Select all
~$ dkms status
~$ rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: (different modules warning here!!!)
~$ sudo dkms remove rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ sudo dkms install rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ dkms status
~$ rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: installed
There maybe typos here... I'm using also a dozen kernels for testing future nvidia modules from v5 to v6 also ahs...
Hope it helps!
Hi:
This solution has helped me to uninstall the 8812au module that in my PC with MX21.3 was giving me kernel panic in Kernels 6.1 and 5.19, I have uninstalled it and both are booting... as it is a PC without wiffi, it seems that it does not need it... although I do not know the reason why in the kernel 6.0 of the same machine it does not give error...
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 1:28 pm
by gRegNfo
Senpai wrote: Tue Jun 27, 2023 1:04 pm
gRegNfo wrote: Thu Jun 22, 2023 9:30 pm
UPDATE
Also errors with RTL8812AU (search github for updated drivers of your device - mine is RTL8821CE - for kernel 6x and read the docs)
Code: Select all
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: line 2497: echo: write error: Broken pipe
were removed:
although because of a warning from using build and installed different modules after retries I ended up using:
Code: Select all
~$ dkms status
~$ rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: (different modules warning here!!!)
~$ sudo dkms remove rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ sudo dkms install rtl8812au/5.13.6 -k <kernel from dkms status here>
~$ dkms status
~$ rtl8812au/5.13.6, 6.1.0-9-amd64, x86_64: installed
There maybe typos here... I'm using also a dozen kernels for testing future nvidia modules from v5 to v6 also ahs...
Hope it helps!
Hi:
This solution has helped me to uninstall the 8812au module that in my PC with MX21.3 was giving me kernel panic in Kernels 6.1 and 5.19, I have uninstalled it and both are booting... as it is a PC without wiffi, it seems that it does not need it... although I do not know the reason why in the kernel 6.0 of the same machine it does not give error...
Thanks
Hi Senpai, really glad it was useful...
Though that driver is also used for Bluetooth connectivity and I can't tell if anything else.
But go on like that and check if everything is working as the beta is being trialed.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 1:30 pm
by dolphin_oracle
siamhie wrote: Tue Jun 27, 2023 1:04 pm
dolphin_oracle wrote: Tue Jun 27, 2023 11:54 am
siamhie wrote: Tue Jun 27, 2023 11:51 am
@dolphin_oracle It is fast but I was able to see both lines create the X portion of the logo. I saw it during beta 1 and initially beta 2.
I'll boot to Sys-V to see if there is any difference. (possible I have a service taking it's time to load)
the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.
@dolphin_oracle I just see a static image (probably loaded by the time the image appears on my screen) when booting to either Sys V or SystemD. Shame because I really liked that animation at boot.
you could try updating the initramfs again. it should have been done automatically.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 3:27 pm
by Danathar
I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.
As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 3:36 pm
by gRegNfo
I just ran
yesterday for my laptop MX23b2.
I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.
Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!
By now I use Time-Shift too and will report next time I ruin my system
I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.
I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!
I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)
Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 3:40 pm
by dolphin_oracle
gRegNfo wrote: Tue Jun 27, 2023 3:36 pm
I just ran
yesterday for my laptop MX23b2.
I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.
Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!
By now I use Time-Shift too and will report next time I ruin my system
I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.
I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!
I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)
Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!
running that "command" as written wouldn't do anything. please update to indicate what you actually ran, or provide the /var/log/ddm.log file.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 3:55 pm
by gRegNfo
dolphin_oracle wrote: Tue Jun 27, 2023 3:40 pm
gRegNfo wrote: Tue Jun 27, 2023 3:36 pm
I just ran
yesterday for my laptop MX23b2.
I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.
Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!
By now I use Time-Shift too and will report next time I ruin my system
I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.
I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!
I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)
Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!
running that "command" as written wouldn't do anything. please update to indicate what you actually ran, or provide the /var/log/ddm.log file.
I Was very distracted sorry, you're very right... it was actually:
Code: Select all
sudo ddm-mx -i nvidia -f nvidia-tesla-470-driver
I don't know what this installer runs after but it broke everything.
Am I supposed to run dkms or initramfs as I did later after ddm-mx? Or is it self sufficient ?
I can assure the synaptic installation was a success though. I even tried checking a lot of the 470 modules just to try it all.
As I reversed it installing the snapshot I don't have a valid DDM.LOG file anymore, but I can sacrifice my system and redo it if you want. ( I have snapshot and timeshift, and am willing to give it a go as a good beta :) )
It takes me just a bit my system is quite fast!
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 4:31 pm
by dolphin_oracle
gRegNfo wrote: Tue Jun 27, 2023 3:55 pm
dolphin_oracle wrote: Tue Jun 27, 2023 3:40 pm
gRegNfo wrote: Tue Jun 27, 2023 3:36 pm
I just ran
yesterday for my laptop MX23b2.
I don't know if I had to make something by the end of it... But booting, it completely ruined all my Kernels.
None would boot up! It broke the wlan first and next usb3... and stalled there probing a lot of Genius inputs until I Ctrl-Alt-Del and re-installed my Snapshot.
Yes it really works now like a charm, doesn't stall at 11% and Ventoy already fixed the code!
By now I use Time-Shift too and will report next time I ruin my system
I ended up after the snapshot, installing the driver and modules (Tesla 470) by hand on Synaptic... It works when rebooted right away.
After I did DKMS and UPDATE-INITRAMFS to specific kernels, and it works! None broken.
I even got the NVIDIA X Server settings module working at last!!!! It displays all info! I'm quite amazed!
I'll try in the future to run specific 3D rendered stuff to check it out.
Not sure yet how to work the changing of GPU but I'll get it (bumblebee is broken, or deprecated? We'll see)
Primus Optimus and Vulkan drivers are still buzzwords to check too. It's too much for now!
running that "command" as written wouldn't do anything. please update to indicate what you actually ran, or provide the /var/log/ddm.log file.
I Was very distracted sorry, you're very right... it was actually:
Code: Select all
sudo ddm-mx -i nvidia -f nvidia-tesla-470-driver
I don't know what this installer runs after but it broke everything.
Am I supposed to run dkms or initramfs as I did later after ddm-mx? Or is it self sufficient ?
I can assure the synaptic installation was a success though. I even tried checking a lot of the 470 modules just to try it all.
As I reversed it installing the snapshot I don't have a valid DDM.LOG file anymore, but I can sacrifice my system and redo it if you want. ( I have snapshot and timeshift, and am willing to give it a go as a good beta :) )
It takes me just a bit my system is quite fast!
provide the output of this:
please.
make sure the latest ddm-mx is installed first though. there have been updates since beta2 launch.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 5:10 pm
by gRegNfo
dolphin_oracle wrote: Tue Jun 27, 2023 4:31 pm
provide the output of this:
please.
make sure the latest ddm-mx is installed first though. there have been updates since beta2 launch.
First, I think looking at my own logs (snippets) that I messed up using
option! It's meant for devs only...
It was a typo, I then corrected it to use
options!!!
(maybe it did something wrong and messed the DD-MX installer?) I'll try to replicate the next time I have a chance to backup all.
DDM-MX v.23.06.01
The Tesla v.470 drivers and kernel related files I LOCKED on synaptic so they won't upgrade to v.520 for now... until I test it and know they are fully supported.
So, here is what you asked, and a little more to add more insight:
Code: Select all
$ nvidia-detect-mx
Distribution: MX
Latest = 525.105.17
Detected NVIDIA GPUs:
01:00.0 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 740M] [10de:0fdf] (rev a1)
Checking card: NVIDIA Corporation GK107M [GeForce GT 740M] (rev a1)
Your card is supported by the nvidia 340 drivers series. nvidia-legacy-340xx-driver
Your card is supported by the nvidia 390 drivers series. nvidia-legacy-390xx-driver
Your card is supported by the nvidia tesla 418 drivers series. nvidia-tesla-418-driver
Your card is supported by the nvidia tesla 470 drivers series. nvidia-tesla-470-driver
It is recommended to install the following:
INSTALL: nvidia-tesla-470-driver
To install alternate driver packages, use sudo ddm-mx -i nvidia -f [driver package name]
Code: Select all
$ inxi -G
Graphics:
Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
Device-2: NVIDIA GK107M [GeForce GT 740M] driver: nvidia v: 470.182.03
Device-3: Chicony UVC 1.00 device HD WebCam type: USB driver: uvcvideo
Display: x11 server: X.Org v: 1.21.1.7 driver: X:
loaded: modesetting,nvidia unloaded: fbdev,vesa dri: crocus gpu: i915
resolution: 1920x1080~60Hz
API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4000 (IVB
GT2)
Code: Select all
$ nvidia-smi
Tue Jun 27 21:51:58 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.182.03 Driver Version: 470.182.03 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... Off | 00000000:01:00.0 N/A | N/A |
| N/A 48C P8 N/A / N/A | 3MiB / 4039MiB | N/A Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
Code: Select all
$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.182.03 Fri Feb 24 03:29:56 UTC 2023
GCC version: gcc version 12.2.0 (Debian 12.2.0-14)
Code: Select all
$ cat /sys/module/nvidia/version
470.182.03
Code: Select all
$ grep "X Driver" /var/log/Xorg.0.log
[ 10.715] (II) NVIDIA dlloader X Driver 470.182.03 Fri Feb 24 03:24:48 UTC 2023
Code: Select all
$ cat /proc/driver/nvidia/gpus/0000:01:00.0/information
Model: Unknown
IRQ: 36
GPU UUID: GPU-dd0cd3d3-dd92-bf7b-a5c7-0529b6d4097d
Video BIOS: 80.07.95.00.07
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:01:00.0
Device Minor: 0
GPU Excluded: No
Sorry I spamed here, just threw all I had in my notes here...
I hope it's enough
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 5:22 pm
by 8bit
Hope this is posted in the correct place.
In 23B2 when one clicks on the clock a separate window opens which must be manually closed. In 21.x the same click opened a pop-out that closed with another click. Can and how do I get 23b2 to act like 21.x
PS I've tried all the settings I could find before asking.
Thanks for your time.
Al
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 5:41 pm
by dolphin_oracle
@gRegNfo
Ok good.
so the updated tool should have installed that driver anyway, without the -f option. likely your problem was with the tool prior to the update.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 5:43 pm
by dolphin_oracle
8bit wrote: Tue Jun 27, 2023 5:22 pm
Hope this is posted in the correct place.
In 23B2 when one clicks on the clock a separate window opens which must be manually closed. In 21.x the same click opened a pop-out that closed with another click. Can and how do I get 23b2 to act like 21.x
PS I've tried all the settings I could find before asking.
Thanks for your time.
Al
swap out the default clock plugin for the deprecated but still present datetime plugin.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 5:53 pm
by gRegNfo
dolphin_oracle wrote: Tue Jun 27, 2023 5:41 pm
@gRegNfo
Ok good.
so the updated tool should have installed that driver anyway, without the -f option. likely your problem was with the tool prior to the update.
@dolphin_oracle
Oh no, quite the opposite.
I first may have messed up with the DDM-MX installer I don't know. But I couldn't boot any kernel at al!!! They all panicked and stalled...
So I did revert it to the snapshot I made earlier. And after that I installed drivers (470 TESLA)via the Synaptic GUI tool. And locked the v.470 Tesla version.
It worked... And after I did mess with dkms and initramfs just to be sure all modules were up to date and installed.
It all checked out!
I never tried the ddm-mx again! As I reverted it to the point I was before using it the first time... so no merit for that
But I will in the future so you know if it's reliable or I made a mess... I bet the later
Thanks man!
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 6:40 pm
by fehlix
Danathar wrote: Tue Jun 27, 2023 3:27 pm
I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.
As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.
Not sure I undertand. Live-USB-Maker in full-feature mode creates a LiveUSB, which can be used with enabled persistence or with not enabled persistence.
Persistence would be enabled with one of the persistence related boot-parameter - not during creation of the LiveUSB.
The Live-USB-Storage folder found within the home of the live user is actually a bind-mount
pointing onto the ext4-boot-device to a directory with the same name "/Live-USB-Storage/[live-user].
The Live-usb-storage was introduced to offer the user a convenient way to have write access
onto the boot-device on the LiveUSb ext4 partition.
On encrypted this ext4-partition is located within the luks-encrytped partition". And the Live-usb-storage bind-mount
within the users-home folder points onto the ext4-partition within the luks-encrypted partition. Not onto any not-encrypted part of the LiveUSB.
AFAIK, LiveUSB maker would not clone the content of Live-usb-storage b/c Live-usb-storage is not part of the Live-system, and would be created with the new LiveUSB when needed/enabled.
E.g booting with toram you may not have a live-usb-storage bind-mount access onto the ext4-boot-device.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 7:02 pm
by siamhie
dolphin_oracle wrote: Tue Jun 27, 2023 1:30 pm
siamhie wrote: Tue Jun 27, 2023 1:04 pm
dolphin_oracle wrote: Tue Jun 27, 2023 11:54 am
the revised theme is faster than the original. not saying that its so fast you aren't seeing it, but it is much quicker.
@dolphin_oracle I just see a static image (probably loaded by the time the image appears on my screen) when booting to either Sys V or SystemD. Shame because I really liked that animation at boot.
you could try updating the initramfs again. it should have been done automatically.
@dolphin_oracle Still no go. I even tried changing my grub theme from mx_linux to mx_logo_ribbon but it didn't help. I'll make a post in the MX Boot Animation thread.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 8:08 pm
by Danathar
fehlix wrote: Tue Jun 27, 2023 6:40 pm
Danathar wrote: Tue Jun 27, 2023 3:27 pm
I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.
As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.
Not sure I undertand. Live-USB-Maker in full-feature mode creates a LiveUSB, which can be used with enabled persistence or with not enabled persistence.
Persistence would be enabled with one of the persistence related boot-parameter - not during creation of the LiveUSB.
The Live-USB-Storage folder found within the home of the live user is actually a bind-mount
pointing onto the ext4-boot-device to a directory with the same name "/Live-USB-Storage/[live-user].
The Live-usb-storage was introduced to offer the user a convenient way to have write access
onto the boot-device on the LiveUSb ext4 partition.
On encrypted this ext4-partition is located within the luks-encrytped partition". And the Live-usb-storage bind-mount
within the users-home folder points onto the ext4-partition within the luks-encrypted partition. Not onto any not-encrypted part of the LiveUSB.
AFAIK, LiveUSB maker would not clone the content of Live-usb-storage b/c Live-usb-storage is not part of the Live-system, and would be created with the new LiveUSB when needed/enabled.
E.g booting with toram you may not have a live-usb-storage bind-mount access onto the ext4-boot-device.
wait...that last part, about toram. The first image I made I booted with the toram option. Maybe it's as simple as that?
Re: k3b & Xfburn - weird issues...
Posted: Tue Jun 27, 2023 9:06 pm
by dolphin_oracle
MintHawk wrote: Thu Jun 22, 2023 6:14 am
Revisiting the burning issue with k3b and Xfburn:
On Mint XFCE 21.2 Beta, everything works fine. k3b works great, no errors, Xfburn burns .mp3s without the above-mentioned distortion and easyMP3gain can easily be installed via Snap instead of manually downloading the front-end here (as stated in another thread). Also, on the other PC which runs MX23 Beta, for some reason, easyMP3gain does not work, but on the PC I'm using right now it does...
I'm pretty sure things with k3b are gonna be OK on MX23 KDE Beta 2, but for the sake of the argument, I'll download it and check it out so the developers now where to focus.
Overall, each one uses their PC for their own personal reasons, with a set of specific tasks in mind they want to perform.
There are some who still burn CDs (for some crazy reason) and it seems I cannot do that right now on MX23 Beta. Thus, I'll have to uninstall MX23 Beta from the other PC
and install an Ubuntu derivative that does the job (probably Mint XFCE). However, I wouldn't like to uninstall MX23 from this PC, so I would appreciate it if a solution could be found concerning the issue with k3b. Alternatively, I'll have to go for another distro that can do that hassle free.
xfburn does indeed seem to have an issue burning audio cds from mp3 files. I get high-pitched distoration with mine.
k3b was OK, after I did this from the commandline (without k3b running) to set permissions on a couple of helper programs that k3b needs.
Code: Select all
sudo chmod 4711 /usr/bin/wodim; sudo chmod 4711 /usr/bin/cdrdao
there is an interface in k3b for changing the permissions, but it sets 4710 instead of 4711 and the apps did not actually start configured such.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jun 27, 2023 9:33 pm
by dolphin_oracle
Danathar wrote: Tue Jun 27, 2023 8:08 pm
fehlix wrote: Tue Jun 27, 2023 6:40 pm
Danathar wrote: Tue Jun 27, 2023 3:27 pm
I believe I've discovered a bug in the live-USB storage creation process. I created a persistent, fully-featured, encrypted drive using the "Clone Live Running System" option in the USB Creator while running off a non-persistent beta USB stick. However, the resulting USB stick did not have the live-usb-storage folder or the file system for the rest of the stick.
As an experiment, I created a 21.3 stick and performed the same process. This time, I made the resulting USB stick from an image I downloaded (beta), and the resulting USB image did have the live-usb-storage folder.
Not sure I undertand. Live-USB-Maker in full-feature mode creates a LiveUSB, which can be used with enabled persistence or with not enabled persistence.
Persistence would be enabled with one of the persistence related boot-parameter - not during creation of the LiveUSB.
The Live-USB-Storage folder found within the home of the live user is actually a bind-mount
pointing onto the ext4-boot-device to a directory with the same name "/Live-USB-Storage/[live-user].
The Live-usb-storage was introduced to offer the user a convenient way to have write access
onto the boot-device on the LiveUSb ext4 partition.
On encrypted this ext4-partition is located within the luks-encrytped partition". And the Live-usb-storage bind-mount
within the users-home folder points onto the ext4-partition within the luks-encrypted partition. Not onto any not-encrypted part of the LiveUSB.
AFAIK, LiveUSB maker would not clone the content of Live-usb-storage b/c Live-usb-storage is not part of the Live-system, and would be created with the new LiveUSB when needed/enabled.
E.g booting with toram you may not have a live-usb-storage bind-mount access onto the ext4-boot-device.
wait...that last part, about toram. The first image I made I booted with the toram option. Maybe it's as simple as that?
could be. I just verified with a standard full live-usb that the live-usb-storage folder is created.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 12:46 am
by i_ri
Hello @PPC
mxfb-menu-generator
nodisplay true
line 121 if [[ $nodisplay == *"true"* ]]; then
"rue" is "true"?
i visit in <mxfb-menu-generator> to add a custommenu
and then add a matching [end] for the [begin] placed at the start.
after the [submenu][end] line 186
another end;
line 187 echo '[end]' >> $FILE
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 2:33 am
by i_ri
hello dolphin_oracle
/home/demo/.fluxbox/init
session.screen0.workspaceNames:
Try what it does with many spaces after a comma?
It does not want a space after a comma between names.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 3:05 am
by i_ri
hello dolphin_oracle
mxfb-settings.list
remove -lxappearance
not a .desktop entry mugshot
remove -mugshot add .desktop entry for About Me
+org.bluesabre.Mugshot
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 6:42 am
by 8bit
dolphin_oracle wrote: Tue Jun 27, 2023 5:43 pm
8bit wrote: Tue Jun 27, 2023 5:22 pm
Hope this is posted in the correct place.
In 23B2 when one clicks on the clock a separate window opens which must be manually closed. In 21.x the same click opened a pop-out that closed with another click. Can and how do I get 23b2 to act like 21.x
PS I've tried all the settings I could find before asking.
Thanks for your time.
Al
swap out the default clock plugin for the deprecated but still present datetime plugin.
Thanks for the reply.
After further testing, the clock plugin can be set to act like the deprecated datetime plugin of 21.x by leaving the Calendar - Command field blank.
Regards,
8bit
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 7:00 am
by keos
Just to say that my system is stable, according to the basic applications I use everything works correctly.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 10:39 am
by siamhie
i_ri wrote: Wed Jun 28, 2023 2:33 am
hello dolphin_oracle
/home/demo/.fluxbox/init
session.screen0.workspaceNames:
Try what it does with many spaces after a comma?
It does not want a space after a comma between names.
The manual shows a space between the names.
Code: Select all
session.screen0.workspaceNames: <names>
Here is where the user can name their workspaces. However it is
recommended to use the tool available in the Configuration Menu to set
these. Default: one, two, three, four
(man fluxbox--RESOURCES section)
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 7:25 pm
by i_ri
yes, the manual, siamhie, indicates spaces. That is why i write to You about not spaces. and i will ask again, siamhie, Have You tried what it does with one or many spaces after a comma? and it ends with a comma. the man does not mention that end with comma.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 7:45 pm
by m_pav
2 questions
1) Has the issue with the startup logo covering an encrypted password prompt been fixed? I haven't read of it or I may have missed it.
2) where can I find the documentation or thread that shows how to re-use an encrypted /home with our installer? I've tried for the last 30 mins and just got a headache. I'm sure Ive seen it somewhere.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 7:49 pm
by dolphin_oracle
m_pav wrote: Wed Jun 28, 2023 7:45 pm
2 questions
1) Has the issue with the startup logo covering an encrypted password prompt been fixed? I haven't read of it or I may have missed it.
2) where can I find the documentation or thread that shows how to re-use an encrypted /home with our installer? I've tried for the last 30 mins and just got a headache. I'm sure Ive seen it somewhere.
I can answer 1> yes. we are going to update the theme one more time though the encryption box is fixed already.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 8:03 pm
by dolphin_oracle
m_pav wrote: Wed Jun 28, 2023 7:45 pm
2 questions
1) Has the issue with the startup logo covering an encrypted password prompt been fixed? I haven't read of it or I may have missed it.
2) where can I find the documentation or thread that shows how to re-use an encrypted /home with our installer? I've tried for the last 30 mins and just got a headache. I'm sure Ive seen it somewhere.
for two, open the encrypted home partition BEFORE starting the installer. it will then show up in the custom layout. it will be preserved. also, you'll need to right-click the real partition and select "Add to Crypttab" or else it won't be opened up at boot.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 8:04 pm
by daemonspudguy
dolphin_oracle wrote: Mon Jun 26, 2023 4:16 pm
daemonspudguy wrote: Mon Jun 26, 2023 4:13 pm
Quick System Info appears to have broken for me.
Code: Select all
Error 22: Unsupported option: --filter-all
Check -h for correct parameters.
Boot Mode: UEFI
what version of inxi do you have installed?
is there any update for the problem? The version of inxi is the package smxi-inxi-antix version 0.4.22, self reported as inxi 3.3.06
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 8:14 pm
by dolphin_oracle
daemonspudguy wrote: Wed Jun 28, 2023 8:04 pm
dolphin_oracle wrote: Mon Jun 26, 2023 4:16 pm
daemonspudguy wrote: Mon Jun 26, 2023 4:13 pm
Quick System Info appears to have broken for me.
Code: Select all
Error 22: Unsupported option: --filter-all
Check -h for correct parameters.
Boot Mode: UEFI
what version of inxi do you have installed?
is there any update for the problem? The version of inxi is the package smxi-inxi-antix version 0.4.22, self reported as inxi 3.3.06
you are using mx-23?
we switched to the main inxi package rather than the smxi-inxi-antix package. so if you moved via upgrade from mx21, you probably need to update inxi.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 8:15 pm
by daemonspudguy
Yes. Okay. That makes sense.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 8:16 pm
by daemonspudguy
That works!
Re: MX-23 beta 2 feedback thread
Posted: Wed Jun 28, 2023 10:25 pm
by siamhie
i_ri wrote: Wed Jun 28, 2023 7:25 pm
yes, the manual, siamhie, indicates spaces. That is why i write to You about not spaces. and i will ask again, siamhie, Have You tried what it does with one or many spaces after a comma? and it ends with a comma. the man does not mention that end with comma.
@i_ri OK, now I understand what you're asking. Here are some examples below.
If you don't have any spaces between the comma and the next workspace name, then the Send To option has all the work spaces in one row.
work1.png
Here I have one space between the first comma and work space #2 and two spaces between the second comma and work space #3. This gives it a cascading effect.
(If I add another work space I would place the third comma right after #3 and give it three spaces before adding the word four to keep the cascading effect going)
work2.png
Here I'm playing around. I have one space after the first comma, fifteen spaces after the second comma.
work3.png
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 1:59 am
by i_ri
siamhie You know the small details of fluxbox; thank You for chatting with me about workspaceNames:
just like the ending comma determines the end of the last name, spaces can be forced onto the beginning of the first name by beginning the string of workspace names with a comma before the first name.
i tried to simplify by telling do not use spaces after a comma.
W-1,W-2,
, W-1, W-2,
my windowmenu send-to and workspacemenu are center justified, so it does not make evident the spaces, i see space out-of-place when the names are the same length. Your left-justify plainly shows the space after the comma.; the fluxbox toolbar workspaces tool does show name-spaces in the toolbar. spaces are inherited from the longest-name entry.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 3:47 am
by andy
Hello @dolphin_oracle ,
please, do you have any news about solution of the Timeshift bug - not working with BTRFS on LUKS?
I am eager to try the new version, but this is crucial for me. I was looking at github issues for linuxmint/timeshift, but not found anything regarding.
Thank you,
Andy
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 4:28 am
by fehlix
andy wrote: Thu Jun 29, 2023 3:47 am
Hello @dolphin_oracle ,
please, do you have any news about solution of the Timeshift bug - not working with BTRFS on LUKS?
I am eager to try the new version, but this is crucial for me. I was looking at github issues for linuxmint/timeshift, but not found anything regarding.
Thank you,
Andy
If you can confirm that it works on Linux Mint, chances are good that it will work on MX Linux after MX customization.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 4:35 am
by andy
fehlix wrote: Thu Jun 29, 2023 4:28 am
andy wrote: Thu Jun 29, 2023 3:47 am
Hello @dolphin_oracle ,
please, do you have any news about solution of the Timeshift bug - not working with BTRFS on LUKS?
I am eager to try the new version, but this is crucial for me. I was looking at github issues for linuxmint/timeshift, but not found anything regarding.
Thank you,
Andy
If you can confirm that it works on Linux Mint, chances are good that it will work on MX Linux after MX customization.
Do you mean the Ubuntu based version (21.2 Victoria)? Or LMDE 5 Elsie?
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 4:40 am
by fehlix
andy wrote: Thu Jun 29, 2023 4:35 am
fehlix wrote: Thu Jun 29, 2023 4:28 am
andy wrote: Thu Jun 29, 2023 3:47 am
Hello @dolphin_oracle ,
please, do you have any news about solution of the Timeshift bug - not working with BTRFS on LUKS?
I am eager to try the new version, but this is crucial for me. I was looking at github issues for linuxmint/timeshift, but not found anything regarding.
Thank you,
Andy
If you can confirm that it works on Linux Mint, chances are good that it will work on MX Linux after MX customization.
Do you mean the Ubuntu based version (21.2 Victoria)? Or LMDE 5 Elsie?
Whatever Linux Mint version it would work, would gives a potential clue to make it work in MX.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 5:03 am
by andy
fehlix wrote: Thu Jun 29, 2023 4:40 am
andy wrote: Thu Jun 29, 2023 4:35 am
fehlix wrote: Thu Jun 29, 2023 4:28 am
If you can confirm that it works on Linux Mint, chances are good that it will work on MX Linux after MX customization.
Do you mean the Ubuntu based version (21.2 Victoria)? Or LMDE 5 Elsie?
Whatever Linux Mint version it would work, would gives a potential clue to make it work in MX.
So I'll try the Ubuntu one, I think it should be closer to Bookworm.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 5:57 am
by andy
Timeshift snapshots via BTRFS filesystems on LUKS encrypted root partition are working.
edit: in Linux Mint. In MX Linux it does not work.
Timeshift1.png
Timeshift2.png
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 6:24 am
by keos
As I've gotten used to this deficiency ...
I forgot to say that the problem with the cursor moving or jumping continues in this version too, I'm refering to what was discussed here:
viewtopic.php?t=69229
*I did all the different recommendations given for a touchpad configuration but nothing worked -- not here in MX-23 either.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 6:32 am
by HausiMX
I am trying the following:
as the last line in /etc/sudoers:
%sudo ALL=(ALL:ALL) NOPASSWD: /usr/sbin/gparted
but it still asks me for the password
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 7:33 am
by CaputAlista
HausiMX wrote: Thu Jun 29, 2023 6:32 am
I am trying the following:
as the last line in /etc/sudoers:
%sudo ALL=(ALL:ALL) NOPASSWD: /usr/sbin/gparted
but it still asks me for the password
try this
sudo visudo
root ALL=(ALL:ALL)
%sudo ALL=(ALL:ALL) NOPASSWD: ALL
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 7:53 am
by j2mcgreg
HausiMX wrote: Thu Jun 29, 2023 6:32 am
I am trying the following:
as the last line in /etc/sudoers:
%sudo ALL=(ALL:ALL) NOPASSWD: /usr/sbin/gparted
but it still asks me for the password
That's because the user (in use) making the change is still required to provide a password. After the change is implemented, no password will be required.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:07 am
by fehlix
andy wrote: Thu Jun 29, 2023 5:57 am
Timeshift snapshots via BTRFS filesystems on LUKS encrypted root partition are working.
edit: in Linux Mint. In MX Linux it does not work.
Timeshift1.png
Timeshift2.png
Thanks. For comparison, what errors do you get on MX Linux with encrypted btrfs.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:18 am
by andy
fehlix wrote: Thu Jun 29, 2023 8:07 am
andy wrote: Thu Jun 29, 2023 5:57 am
Timeshift snapshots via BTRFS filesystems on LUKS encrypted root partition are working.
edit: in Linux Mint. In MX Linux it does not work.
Timeshift1.png
Timeshift2.png
Thanks. For comparison, what errors do you get on MX Linux with encrypted btrfs.
I''ll reinstall it again (as it was replaced by Mint just before a while
)
But as I remember, just timeshift not allowing to select BTRFS option, maybe even not showing its partition.
Please guide me what logs to send to you (beside the ordinary ones).
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:33 am
by fehlix
andy wrote: Thu Jun 29, 2023 8:18 am
fehlix wrote: Thu Jun 29, 2023 8:07 am
andy wrote: Thu Jun 29, 2023 5:57 am
Timeshift snapshots via BTRFS filesystems on LUKS encrypted root partition are working.
edit: in Linux Mint. In MX Linux it does not work.
Timeshift1.png
Timeshift2.png
Thanks. For comparison, what errors do you get on MX Linux with encrypted btrfs.
I''ll reinstall it again (as it was replaced by Mint just before a while
)
But as I remember, just timeshift not allowing to select BTRFS option, maybe even not showing its partition.
Please guide me what logs to send to you (beside the ordinary ones).
Not sure, as much info/screenshot as you can provide showing that "it does not work".
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:41 am
by andy
fehlix wrote: Thu Jun 29, 2023 8:33 am
andy wrote: Thu Jun 29, 2023 8:18 am
fehlix wrote: Thu Jun 29, 2023 8:07 am
Thanks. For comparison, what errors do you get on MX Linux with encrypted btrfs.
I''ll reinstall it again (as it was replaced by Mint just before a while
)
But as I remember, just timeshift not allowing to select BTRFS option, maybe even not showing its partition.
Please guide me what logs to send to you (beside the ordinary ones).
Not sure, as much info/screenshot as you can provide showing that "it does not work".
I have provided much more, in fact everything DolphinOracle asked for.
Please search about two weeks before.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:52 am
by andy
Hello
@fehlix,
First I was reporting a bug, that installer let me go without /boot partition assigned.
But after properly assingnig /boot and installed to / on BTRFS on LUKS, Timeshift does not allow to use BRTFS and throws errors.
In this (last) message of that conversation is a summary.
viewtopic.php?p=729395#p729395
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:55 am
by andy
Of course I will provide every info, I will be asked for. Just waiting for orders of you, real programmers. But please, do fix it.
Screenshot_20230629_085906.png
Screenshot_20230629_090051.png
Edit: My reasoning why asking to repair this bug:
For me encryption is crucial, and as I want to stay with MX Linux, I am forced to use EXT4.
But as BTRFS matures and offers nice functionality like instant snapshots, it is a welcome replacement to RSYNC.
I would like to use this nice feature, at least on my stronger machine with SSD with TBW large enough.
(in the past I have used BTRFS on LinuxMint, without encryption. After some years I have watched more closely whats going on on I/O side, and was shocked by continuous write traffic. So I stopped using BTRFS to save my SSDs. Years have passed. Then later I switched to MX-Linux, and now, after another four years, the TBW on large disks is big enough to withstand BTRFS write amplification).
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 10:11 am
by fehlix
andy wrote: Thu Jun 29, 2023 8:55 am
Of course I will provide every info, I will be asked for. Just waiting for orders of you, real programmers. But please, do fix it.
Screenshot_20230629_085906.png
Screenshot_20230629_090051.png
Thanks, yes indeed this gives us a clue.
The reason is kind of simple: MX Linux uses the /@ subvolume for root as required by timeshift (which was originally developed for Ubuntu's /@-root layout). But MX Linux is also using /@-as default mount-subvol, which Ubuntu is not using and timeshift simply assumes to always mount by default at top-subvol. We had a similare fix for non-encrypted and may need to find the place to apply this fix also for encrypted-btrfs.
You can test-breaking timeshift on Ubuntu by simply settings the default-mount subvol to /@
and Ubuntu and friends would still work, but timeshift may stop to work on btrfs.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 10:23 am
by andy
@fehlix ,
is this issue related?
https://github.com/linuxmint/timeshift/issues/131
edit: there is reference to issue #90, which seems exactly spot on.
https://github.com/linuxmint/timeshift/issues/90
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 11:19 am
by fehlix
Good found. Maybe someone send a MX-patch to Linux Mint.
The reason we haven't done so, is also simple: The original version we applied the default-subvol patch
was an older version. Meanwhile Linux Mint took over the maintenance and we currently using
Debian's provided version based on Linux Mint - so we may send the patch if it works to Linux Mint.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 1:36 pm
by HausiMX
CaputAlista wrote: Thu Jun 29, 2023 7:33 am
HausiMX wrote: Thu Jun 29, 2023 6:32 am
I am trying the following:
as the last line in /etc/sudoers:
%sudo ALL=(ALL:ALL) NOPASSWD: /usr/sbin/gparted
but it still asks me for the password
try this
sudo visudo
root ALL=(ALL:ALL)
%sudo ALL=(ALL:ALL) NOPASSWD: ALL
thanks for replying, but it still does not work as expected. My "workaround" is deleting my password
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 2:35 pm
by Danathar
This may be pretty esoteric, and I don't know if this is the case on the last version of MX since I'm running currently on the beta, but I enabled zram and noticed on shutdown with the live USB with persistence that an error trying to unload the zram kernel module (too early)? I have zram enabled for swap.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 3:40 pm
by dolphin_oracle
HausiMX wrote: Thu Jun 29, 2023 6:32 am
I am trying the following:
as the last line in /etc/sudoers:
%sudo ALL=(ALL:ALL) NOPASSWD: /usr/sbin/gparted
but it still asks me for the password
gparted launches from the menu with pkexec. you could likely launch with "sudo gparted" from the cli with what you've indicated.
either way, not likely to actually be a beta issue.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 4:04 pm
by CaputAlista
dolphin_oracle wrote: Thu Jun 29, 2023 3:40 pm
HausiMX wrote: Thu Jun 29, 2023 6:32 am
I am trying the following:
as the last line in /etc/sudoers:
%sudo ALL=(ALL:ALL) NOPASSWD: /usr/sbin/gparted
but it still asks me for the password
gparted launches from the menu with pkexec. you could likely launch with "sudo gparted" from the cli with what you've indicated.
either way, not likely to actually be a beta issue.
direct acces in kde gparted, dolphin etc
sudo pkexec env DISPLAY=$DISPLAY XAUTHORITY=$AUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true gparted
Re: MX-23 beta 2 feedback thread
Posted: Thu Jun 29, 2023 8:41 pm
by Stevo
I don't know if anyone has reported VLC losing hardware accelerated decoding and encoding in Bookworm, but that seems to be unavoidable with the Debian packages.
5.2.3. Limited hardware-accelerated video encoding/decoding support in VLC
The VLC video player supports hardware-accelerated video decoding and encoding via VA-API and VDPAU. However, VLC's support for VA-API is tightly related to the version of FFmpeg. Because FFmpeg was upgraded to the 5.x branch, VLC's VA-API support has been disabled. Users of GPUs with native VA-API support (e.g., Intel and AMD GPUs) may experience high CPU usage during video playback and encoding.
Users of GPUs offering native VDPAU support (e.g., NVIDIA with non-free drivers) are not affected by this issue.
Support for VA-API and VDPAU can be checked with vainfo and vdpauinfo (each provided in a Debian package of the same name).
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 2:52 am
by Eadwine Rose
@Stevo
I reported in about Kodi a bit ago, which I found also (when googling) seemed to affect VLC. Post 54. Did include a solution that I was unable to test.
viewtopic.php?p=729379#p729379
Maybe that downgrade they mention will sort it?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 3:17 am
by Freja
Stevo wrote: Thu Jun 29, 2023 8:41 pm
I don't know if anyone has reported VLC losing hardware accelerated decoding and encoding in Bookworm, but that seems to be unavoidable with the Debian packages.
5.2.3. Limited hardware-accelerated video encoding/decoding support in VLC
The VLC video player supports hardware-accelerated video decoding and encoding via VA-API and VDPAU. However, VLC's support for VA-API is tightly related to the version of FFmpeg. Because FFmpeg was upgraded to the 5.x branch, VLC's VA-API support has been disabled. Users of GPUs with native VA-API support (e.g., Intel and AMD GPUs) may experience high CPU usage during video playback and encoding.
Users of GPUs offering native VDPAU support (e.g., NVIDIA with non-free drivers) are not affected by this issue.
Support for VA-API and VDPAU can be checked with vainfo and vdpauinfo (each provided in a Debian package of the same name).
(This case is at my "Intel" machine.)
I usually using SMplayer (not VLC), VA-API is not working in MX-23 beta2,
Instead of
"gpu-next" worked very well. I think it will be a replacement.
2023-06-30_16-11-32.png
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 4:40 am
by wizardfromoz
Regarding my Previous on How to Disable os-prober:
I have done further work on this, and thank you, the advice on
works fine.
That being acknowledged, this statement from
@fehlix
Debian did some changes to always have disabled os prober during GRUB upgrade by default.
is at odds with the reality, in my experience.
I have Debian Bookworm, Cinnamon, and a part of its /etc/default/grub reads as follows
Code: Select all
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
# OS_PROBER re-enabled by Debian Calamares installation:
GRUB_DISABLE_OS_PROBER=false
... and os-prober works fine with that, so Calamares appears to have detected I am a multi-booter and adjusted for that.
No offence to mx-installer (which I have used for years), but once again - mx-tools? A mention in the final release notes? and so on would help.
Cheers
Wizard
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 4:44 am
by i_ri
hello dolphin_oracle and everyone
mx23_fluxbox is headed to distro of the decade.
Hello Melber
fluxbox Style MX-comfort
A Wonderful Style.
personalizing;
Made three rows of color at the top of maximize-pressed.xpm to
match the three rows of color in maximize-active.xpm.
Likewise all "pressed" buttons changed to color top three rows if active color.
Our X flashes red on the close-pressed.xpm.
Dot red for stick-toggled-active.xpm.
mxing with the maximize button.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 6:13 am
by fehlix
wizardfromoz wrote: Fri Jun 30, 2023 4:40 am
Regarding my Previous on How to Disable os-prober:
I have done further work on this, and thank you, the advice on
works fine.
That being acknowledged, this statement from @fehlix
Debian did some changes to always have disabled os prober during GRUB upgrade by default.
is at odds with the reality, in my experience.
I have Debian Bookworm, Cinnamon, and a part of its /etc/default/grub reads as follows
Code: Select all
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
# OS_PROBER re-enabled by Debian Calamares installation:
GRUB_DISABLE_OS_PROBER=false
... and os-prober works fine with that, so Calamares appears to have detected I am a multi-booter and adjusted for that.
No offence to mx-installer (which I have used for years), but once again - mx-tools? A mention in the final release notes? and so on would help.
Cheers
Wizard
It's about grub-package upgrade, where grub-install may be triggered, and potentically a debconf popup window is shown to the user , which by the way can happen als in UEFI install. Debian has disabled to run os-probe by default,
and people may face the situation to not find any menu entry for other installs within the generated grub menu. Even in UEFI-install the grub-pc upgrade may be triggerd if user, eg. installed also onto mbr. To avoid this potential show stopper, the place (to define to/set disable/enable os-prober) was moved into debconf.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 8:45 am
by Arnox
Hey, I'm going to download and install the beta now on some bare metal. Would you guys like me to report bugs in this thread or is it preferred to use the official bug tracker?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 9:08 am
by j2mcgreg
Arnox wrote: Fri Jun 30, 2023 8:45 am
Hey, I'm going to download and install the beta now on some bare metal. Would you guys like me to report bugs in this thread or is it preferred to use the official bug tracker?
Please do it here.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 9:28 am
by Arnox
j2mcgreg wrote: Fri Jun 30, 2023 9:08 am
Arnox wrote: Fri Jun 30, 2023 8:45 am
Hey, I'm going to download and install the beta now on some bare metal. Would you guys like me to report bugs in this thread or is it preferred to use the official bug tracker?
Please do it here.
Sounds good. Will report back as soon as I can.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 10:46 am
by andy
Hello
@fehlix,
can I rest assured, that the LUKS+BTRFS+Timeshift trio will operate in next beta or RC? Is it planned to fix?
Rougly at what time can we expect next install media iteration?
If the fix will not come in the next iteration, is there any possibility to properly prepare LUKS+BTRFS manually from live session just before install, to achieve proper operation of the trio?
And if yes - will the next iteration's "defaults" be compatible with RC, therefore can I install it and consider it after upgrade the same "quality" as RC or final?
I am eager to try and play with the new bookworm, (to replace bullseye on my not-so-important portable machine), but I do not want to do all the hassle of customizing again after final comes out.
Thank you for your answers and for effort of all the team for making this version real.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 11:05 am
by fehlix
andy wrote: Fri Jun 30, 2023 10:46 am
Hello @fehlix,
can I rest assured, that the LUKS+BTRFS+Timeshift trio will operate in next beta or RC?
No. B/c it has first to be fixed. And don't think next release will debend on this issue been fixed or not.
andy wrote: Fri Jun 30, 2023 10:46 am
Is it planned to fix?
Maybe when we find time and see how to fix the showstopper.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 11:07 am
by siamhie
@Jerry3904 Seems About Fluxbox is not installed. I still have About MX Linux (system) and About Me (settings).
fluxbox-about.jpg
*Edit: Just found the package in MXPI. Seems the package doesn't get installed from the ISO.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 11:15 am
by andy
andy wrote: Fri Jun 30, 2023 10:46 am
...
is there any possibility to properly prepare LUKS+BTRFS manually from live session just before install, to achieve proper operation of the trio?
...
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 11:31 am
by Jerry3904
siamhie wrote: Fri Jun 30, 2023 11:07 am
@Jerry3904 Seems About Fluxbox is not installed. I still have About MX Linux (system) and About Me (settings).
fluxbox-about.jpg
*Edit: Just found the package in MXPI. Seems the package doesn't get installed from the ISO.
That's by design, since it's deprecated now that MXFB has been integrated with MX. whose Welcome contains all relevant info.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 12:18 pm
by siamhie
Jerry3904 wrote: Fri Jun 30, 2023 11:31 am
siamhie wrote: Fri Jun 30, 2023 11:07 am
@Jerry3904 Seems About Fluxbox is not installed. I still have About MX Linux (system) and About Me (settings).
fluxbox-about.jpg
*Edit: Just found the package in MXPI. Seems the package doesn't get installed from the ISO.
That's by design, since it's deprecated now that MXFB has been integrated with MX. whose Welcome contains all relevant info.
OK, thanks
@Jerry3904. I'll disregard that message whenever mx-fluxbox gets updated.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 1:44 pm
by Arnox
64-bit KDE version tested. systemd loaded.
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
init=/lib/systemd/systemd
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2802 date: 10/22/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 5 3600XT 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: 0x8701021
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: 3088 high: 4434 min/max: 2200/4635 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 4434 2: 4366 3: 2951 4: 2041 5: 1871 6: 2795
7: 2793 8: 4347 9: 3959 10: 1910 11: 2794 12: 2795 bogomips: 91036
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GP102 [TITAN Xp] driver: nvidia v: 525.105.17 non-free: 530.xx+
status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-21 pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.0 chip-ID: 10de:1b02 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71") s-diag: 554mm (21.82")
Monitor-1: DP-5 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
diag: 547mm (21.54") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.105.17 renderer: NVIDIA TITAN Xp/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GP102 HDMI Audio driver: snd_hda_intel v: kernel pcie: bus-ID: 7-3:2
chip-ID: b58e:9e84 gen: 3 speed: 8 GT/s class-ID: 0300 serial: <filter> lanes: 16 bus-ID: 09:00.1
chip-ID: 10de:10ef 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
Device-3: Blue Microphones Yeti Stereo Microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid
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: f000 bus-ID: 05: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.96 TiB used: 201.69 GiB (10.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 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QEXM7 temp: 47.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SUV400S37120G size: 111.79 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 96R9 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.82 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 95.53 GiB size: 95.53 GiB (100.00%) used: 30.04 GiB (31.4%) fs: btrfs
dev: /dev/sdb1 maj-min: 8:17
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sdb3 maj-min: 8:19
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 16 GiB used: 42.2 MiB (0.3%) priority: -2 dev: /dev/sdb2
maj-min: 8:18
Sensors:
System Temperatures: cpu: 58.0 C mobo: 44.0 C gpu: nvidia temp: 59 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 34%
Repos:
Packages: 2568 pm: dpkg pkgs: 2562 libs: 1430 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 6
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://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 318 Uptime: 59m wakeups: 5 Memory: 15.52 GiB used: 3.95 GiB (25.5%) Init: systemd
v: 252 target: graphical (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: UEFI
1B. In the KDE Wallpaper picker, image descriptions can flow out of bounds.
2B. In the MX Package Installer, "Installed" and "Upgrade available" package legends are clickable buttons that don't seem to do anything.
3B. As examples, in LibreOffice 7.4.5 and Kate 22.12.3, tooltips will glitch and partially cut off sometimes when moving from one item to another. This doesn't seem to happen at all with tooltips that are "out-of-app" though. Unchecking "Morphing Popups" in Desktop Effects fixes the issue.
4B. LazPaint 7.2.2 crashes on changing canvas size. Known old bug. Recommend removing app.
5B. In the MX Linux Installer, for the "Customize the disk layout" option, Layout Builder does not create any swap partition even though it was requested. When Layout Builder is applied, does not allow partition changes until "New layout" is selected.
6B. When program loading/processing occurs, mouse cursor sometimes starts to heavily lag.
Recommendations:
1R. Highly recommend including the Synthesizer plugin in GIMP by default.
2R. In the MX Linux Installer, for the "Customize the disk layout" option, it is recommended to have the setting for all "Use for" dialog boxes to start out blank to ensure no unintentional writes to other drives.
3D Graphical Testing Done (Nvidia Drivers Used for All Games):
1G. SuperTuxKart (Debian Native)
2G. Unreal Tournament (1999) (Steam and Steam Proton)
3G. Star Wars Jedi Knight: Dark Forces 2 (Steam and Steam Proton)
4G. Red Faction: Guerilla (Wrecking Crew Stress Test) (Steam and Steam Proton)
Beyond Dark Forces 2 being its usual annoying self to get running, all ran without issues or frame dips.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 3:13 pm
by rej
Hi-
MX-23 is beautiful - love the elegant wallpaper.
Hope this is not a duplicate.
MX-23 Beta Live USB Persistence made from installed, configured snapshot - first update fail/errors:
---------------------------------------
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools
Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /boot/initrd.img-6.1.0-9-amd64 with 1.
dpkg: error processing package plymouth-themes-mx (--configure):
installed plymouth-themes-mx package post-installation script subprocess returned error ex
it status 1
-----------------------------------------
Mouse and Touchpad settings missing - "Disable touchpad while typing"
------------------------------------------
Code: Select all
Snapshot created on: 20230625_1354
System:
Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: hwclock=local
gfxsave persist_all
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_x64 Libretto June 25 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: LENOVO product: 20BWCTO1WW v: ThinkPad T450s serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20BWCTO1WW v: SDK0E50512 STD serial: <superuser required>
UEFI-[Legacy]: LENOVO v: JBET48WW (1.13 ) date: 04/20/2015
Battery:
ID-1: BAT0 charge: 11.5 Wh (97.5%) condition: 11.8/23.5 Wh (50.4%) volts: 12.4 min: 11.4
model: LGC 45N1113 type: Li-ion serial: <filter> status: not charging
ID-2: BAT1 charge: 14.1 Wh (96.6%) condition: 14.6/23.5 Wh (62.3%) volts: 12.4 min: 11.4
model: LGC 45N1127 type: Li-ion serial: <filter> status: not charging
CPU:
Info: model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell gen: core 5 level: v3
note: check built: 2015-18 process: Intel 14nm family: 6 model-id: 0x3D (61) stepping: 4
microcode: 0x1D
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 1197 high: 1198 min/max: 500/2700 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 1198 2: 1197 3: 1197 4: 1197 bogomips: 17559
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel arch: Gen-8
process: Intel 14nm built: 2014-15 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
Monitor-1: eDP-1 model: AU Optronics 0x303e built: 2012 res: 1600x900 hz: 60 dpi: 132
gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1600x900
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 5500 (BDW GT2)
direct-render: Yes
Audio:
Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:03.0
chip-ID: 8086:160c class-ID: 0403
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 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 Ethernet I218-V vendor: Lenovo driver: e1000e v: kernel port: 4080
bus-ID: 00:19.0 chip-ID: 8086:15a3 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee v: kernel
modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:818b
class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 2-7:4 chip-ID: 0bda:8761
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 4380 hci-v: 4.0 rev: e3e
Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 473.3 GiB used: 11.64 GiB (2.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Transcend model: TS128GMTS430S size: 119.24 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: U17A scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0105 scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 type: USB model: General USB Flash Disk size: 116.06 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Kingston model: DataTraveler 2.0 size: 14.42 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP 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: file size: 3 GiB used: 0 KiB (0.0%) priority: -2
file: /live/boot-dev/swap-file
Sensors:
System Temperatures: cpu: 43.0 C pch: 46.0 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: pm: dpkg pkgs: 2110 libs: 1075 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/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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 240 Uptime: 30m wakeups: 3 Memory: 7.46 GiB used: 3.1 GiB (41.5%) 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)
Code: Select all
full upgrade
apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
xfce4-dev-tools (4.18.0-1)
Use 'apt autoremove' to remove it.
The following packages will be upgraded:
formatusb (23.05.05 => 23.06.01)
google-chrome-stable (114.0.5735.133-1 => 114.0.5735.198-1)
lo-main-helper (23.07.13mx23 => 23.07.15mx23)
mx-conky-data (20230601 => 20230627)
mx-docs (20230614mx23 => 20230630mx23)
mx-installer (23.6.05mx23 => 23.6.06mx23)
mx-packageinstaller-pkglist (23.07.13mx23 => 23.07.15mx23)
neofetch (7.1.0+git20210726-0.2~mx21+1 => 7.1.0+git20210726-0.3~mx23+1)
plymouth-themes-mx (23.06.03 => 23.06.05)
xfce4-docklike-plugin (0.4.0+git20220122-1~mx23 => 0.4.1-0.1~mx23+1)
10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 216 MB of archives.
After this operation, 80.9 kB of additional disk space will be used.
Get:1 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 formatusb amd64 23.06.01 [78.0 kB]
Get:2 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 lo-main-helper all 23.07.15mx23 [7,216 B]
Get:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 mx-conky-data all 20230627 [8,230 kB]
Get:4 https://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 114.0.5735.198-1 [94.3 MB]
Get:5 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 mx-docs all 20230630mx23 [96.6 MB]
Get:6 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 mx-installer amd64 23.6.06mx23 [521 kB]
Get:7 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 mx-packageinstaller-pkglist all 23.07.15mx23 [206 kB]
Get:8 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 neofetch all 7.1.0+git20210726-0.3~mx23+1 [81.6 kB]
Get:9 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 xfce4-docklike-plugin amd64 0.4.1-0.1~mx23+1 [86.1 kB]
Get:10 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/main amd64 plymouth-themes-mx all 23.06.05 [15.7 MB]
Fetched 216 MB in 1min 43s (2,103 kB/s)
(Reading database ... 286675 files and directories currently installed.)
Preparing to unpack .../0-google-chrome-stable_114.0.5735.198-1_amd64.deb ...
Unpacking google-chrome-stable (114.0.5735.198-1) over (114.0.5735.133-1) ...
Preparing to unpack .../1-formatusb_23.06.01_amd64.deb ...
Unpacking formatusb (23.06.01) over (23.05.05) ...
Preparing to unpack .../2-lo-main-helper_23.07.15mx23_all.deb ...
Unpacking lo-main-helper (23.07.15mx23) over (23.07.13mx23) ...
Preparing to unpack .../3-mx-conky-data_20230627_all.deb ...
Unpacking mx-conky-data (20230627) over (20230601) ...
Preparing to unpack .../4-mx-docs_20230630mx23_all.deb ...
Unpacking mx-docs (20230630mx23) over (20230614mx23) ...
Preparing to unpack .../5-mx-installer_23.6.06mx23_amd64.deb ...
Unpacking mx-installer (23.6.06mx23) over (23.6.05mx23) ...
Preparing to unpack .../6-mx-packageinstaller-pkglist_23.07.15mx23_all.deb ...
Unpacking mx-packageinstaller-pkglist (23.07.15mx23) over (23.07.13mx23) ...
Preparing to unpack .../7-neofetch_7.1.0+git20210726-0.3~mx23+1_all.deb ...
Unpacking neofetch (7.1.0+git20210726-0.3~mx23+1) over (7.1.0+git20210726-0.2~mx21+1) ...
Preparing to unpack .../8-xfce4-docklike-plugin_0.4.1-0.1~mx23+1_amd64.deb ...
Unpacking xfce4-docklike-plugin:amd64 (0.4.1-0.1~mx23+1) over (0.4.0+git20220122-1~mx23) ..
.
Preparing to unpack .../9-plymouth-themes-mx_23.06.05_all.deb ...
Unpacking plymouth-themes-mx (23.06.05) over (23.06.03) ...
Setting up google-chrome-stable (114.0.5735.198-1) ...
Setting up mx-installer (23.6.06mx23) ...
Setting up neofetch (7.1.0+git20210726-0.3~mx23+1) ...
Setting up formatusb (23.06.01) ...
Setting up mx-packageinstaller-pkglist (23.07.15mx23) ...
Setting up lo-main-helper (23.07.15mx23) ...
Setting up mx-docs (20230630mx23) ...
Setting up mx-conky-data (20230627) ...
Setting up xfce4-docklike-plugin:amd64 (0.4.1-0.1~mx23+1) ...
Setting up plymouth-themes-mx (23.06.05) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-9-amd64
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools
Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /boot/initrd.img-6.1.0-9-amd64 with 1.
dpkg: error processing package plymouth-themes-mx (--configure):
installed plymouth-themes-mx package post-installation script subprocess returned error ex
it status 1
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for menu (2.1.49) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Errors were encountered while processing:
plymouth-themes-mx
E: Sub-process /usr/bin/dpkg returned an error code (1)
full upgrade complete (or was canceled)
this terminal window can now be closed
Press any key to close...
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 3:19 pm
by dolphin_oracle
disble touchpad while typing is the default driver behavior with the new libinput touchpad drivers. we are no longer shipping with synaptic touchpad driver, although its still available in the repo.
good catch on the plymouth theme package error. will adjust.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jun 30, 2023 4:22 pm
by i_ri
hello rej
touchpad settings held now in
/etc/X11/xorg.conf.d/30-touchpad-libinput.conf
there is a setting for disable when typing;
As dolphin_oracle stated, the default setting for disable while typing is true, yes, on,
so the only need for it to be included/ present in the driver configuration is to set disable while typing to false, no, off.
sample, Option "DisableWhileTyping" "bool"
Code: Select all
Section "InputClass"
Identifier "touchpad"
Driver "libinput"
MatchIsTouchpad "on"
Option "Tapping" "on"
Option "TappingButtonMap" "lmr"
Option "AccelSpeed" "0.075"
Option "SendEventsMode" "disabled-on-external-mouse"
Option "DisableWhileTyping" "false"
EndSection
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 12:39 am
by m_pav
Something a little funky going on with the default conky. On startup, Live and installed on 2 machines with Intel Graphics, the minutes are missing altogether but the rest of it is there. Images are from the Celeron based NUC, but identical issue on both machines. The issue prevails whether I boot the machines with Modesetting or Intel Drivers using MX Tweak between boots. I can get the minutes to display on the Laptop by opening MX Conky Manager and selecting another conky to display simultaneously, then uncheck it so only Cowon-midblue remains, but on the NUC, it's a more hit and miss.
Can anybody else replicate this?
Live-Boot1.jpg
Live-Boot2.jpg
My Daily Driver
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=/antiX/vmlinuz quiet splasht nosplash lang=en_NZ kbd=us
tz=Pacific/Auckland hwclock=local grubsave
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: LENOVO product: 20FHCTO1WW v: ThinkPad T560 serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20FHCTO1WW v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO
v: N1KET50W (1.37 ) date: 11/20/2020
Battery:
ID-1: BAT0 charge: 39.2 Wh (99.5%) condition: 39.4/44.5 Wh (88.5%) volts: 12.6 min: 11.4
model: SONY 45N1743 type: Li-poly serial: <filter> status: not charging
ID-2: BAT1 charge: 62.7 Wh (100.0%) condition: 62.7/72.2 Wh (86.9%) volts: 12.4 min: 11.1
model: SANYO 45N1125 type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Core i7-6600U bits: 64 type: MT MCP arch: Skylake gen: core 6 level: v3
note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x4E (78) stepping: 3
microcode: 0xE2
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 2800 min/max: 400/3400 scaling: driver: intel_pstate governor: powersave
cores: 1: 2800 2: 2800 3: 2800 4: 2800 bogomips: 22399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Lenovo driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
Device-2: Lite-On Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:6 chip-ID: 04ca:7058
class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: LG Display 0x054f built: 2016 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 520 (SKL GT2)
direct-render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d70 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 Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:156f class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24f3 class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: wwan0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:5
chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 1.94 TiB used: 2.04 GiB (0.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Netac model: USB Flash Drive size: 119.24 GiB
block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 1301 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 29.0 C pch: 28.5 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1046 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 200 Uptime: 47m wakeups: 3 Memory: 15.48 GiB used: 1.7 GiB (11.0%) 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: UEFI
Crappy old Intel NUC Celeron N3050
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: hwclock=local
lang=en_NZ tz=Pacific/Auckland quiet splasht nosplash
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: Intel model: NUC5CPYB v: H61145-404 serial: <superuser required>
UEFI-[Legacy]: Intel v: PYBSWCEL.86A.0043.2015.0904.1904 date: 09/04/2015
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont level: v2 built: 2015-17
process: Intel 14nm family: 6 model-id: 0x4C (76) stepping: 3 microcode: 0x351
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB desc: d-2x24 KiB; i-2x32 KiB
L2: 2 MiB desc: 2x1024 KiB
Speed (MHz): avg: 681 high: 792 min/max: 480/2160 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 792 2: 571 bogomips: 6400
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics
driver: i915 v: kernel arch: Gen-8 process: Intel 14nm built: 2014-15 ports: active: DP-1
empty: DP-2,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:22b1 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.48x10.91") s-diag: 523mm (20.6")
Monitor-1: DP-1 model: LG (GoldStar) W2242 serial: <filter> built: 2010 res: 1680x1050 hz: 60
dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65") diag: 585mm (23") ratio: 3:2, 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 400 (BSW) direct-render: Yes
Audio:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2284 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 Wireless 3165 driver: iwlwifi v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:3165 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Intel driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-5.1:4
chip-ID: 8087:0a2a class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 1000 hci-v: 4.2 rev: 1000
Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 117.55 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SP310 size: 59.63 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5.2 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: A-Data model: USB Flash Drive size: 57.92 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1100 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: 2.02 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
maj-min: 8:2
Sensors:
System Temperatures: cpu: 41.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1046 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 198 Uptime: 4m wakeups: 4 Memory: 3.74 GiB used: 1.12 GiB (29.9%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 7:07 am
by fehlix
m_pav wrote: Sat Jul 01, 2023 12:39 am
Something a little funky going on with the default conky. On startup, Live and installed on 2 machines with Intel Graphics, the minutes are missing altogether but the rest of it is there. Images are from the Celeron based NUC, but identical issue on both machines. The issue prevails whether I boot the machines with Modesetting or Intel Drivers using MX Tweak between boots. I can get the minutes to display on the Laptop by opening MX Conky Manager and selecting another conky to display simultaneously, then uncheck it so only Cowon-midblue remains, but on the NUC, it's a more hit and miss.
Can anybody else replicate this?
Any error on the cli, when re-invoking this way ( e.g after login) within the terminal.
Code: Select all
killall conky; cd ~/.conky/MX-CowonMildBlue; conky -c MX-Cowon_MildBlue
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 9:00 am
by dolphin_oracle
I' seeing the same as m_pav. on first boot of live of new test builds. toggling conky on and off doens't solve the problem, but toggling off and on in conky-manager does. font issue maybe?
will get some more data and post it.
note: the midblue variant is the proposed new default. the beta2 isos still uses the tangram variant, not midblue. the tangram variant appears to launch correctly.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 10:01 am
by Melber
I've been using MildBlue for the last two weeks on mxfb-23 beta2 and have not seen this issue.
The conky code was copied from tangram, the only changes that I knowingly made were the colours and a few small offset adjustments.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 10:40 am
by Jerry3904
I have been doing the same, with same results.
I may have installed it directly from a post, so maybe something got changed when it went into GitHub...it's been known to happen.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 10:52 am
by Arnox
Unfortunately, I can't test Conky for this problem as literally all three of my computers are running full Nvidia hardware. lol
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 11:36 am
by dolphin_oracle
Melber wrote: Sat Jul 01, 2023 10:01 am
I've been using MildBlue for the last two weeks on mxfb-23 beta2 and have not seen this issue.
The conky code was copied from tangram, the only changes that I knowingly made were the colours and a few small offset adjustments.
It’s fine launching from the conky manager but not on fresh iso startup
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 11:57 am
by siamhie
Melber wrote: Sat Jul 01, 2023 10:01 am
I've been using MildBlue for the last two weeks on mxfb-23 beta2 and have not seen this issue.
The conky code was copied from tangram, the only changes that I knowingly made were the colours and a few small offset adjustments.
Launches fine for me at boot. The only change I see in the text section is at line 118. (tangram on the left--mildblue on the right)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 12:39 pm
by CharlesV
m_pav wrote: Sat Jul 01, 2023 12:39 am
Something a little funky going on with the default conky. On startup, Live and installed on 2 machines with Intel Graphics, the minutes are missing altogether but the rest of it is there. Images are from the Celeron based NUC, but identical issue on both machines. The issue prevails whether I boot the machines with Modesetting or Intel Drivers using MX Tweak between boots. I can get the minutes to display on the Laptop by opening MX Conky Manager and selecting another conky to display simultaneously, then uncheck it so only Cowon-midblue remains, but on the NUC, it's a more hit and miss.
Can anybody else replicate this?
Live-Boot1.jpg
Live-Boot2.jpg
I have several intel only test machines, both currently on mx23 and will check this a little later today.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 1:03 pm
by CharlesV
btw - I went through the Tour yesterday for the very first time... and I was HIGHLY impressed with it! That is one of the best tours I have ever seen and kudo's to the persons(s) that developed it!!
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 1:13 pm
by mklym
When saving a screenshot of the desktop, the "Save Screenshot As..." window extends off the bottom of the screen so you can not see the "Cancel" or "Save" buttons. I have to grab the top edge of the window and drag it down, then grab the title bar and drag the window up until the buttons are visible. Seems to happen the first time you go to save a screenshot, subsequent "Save Screenshot As.." windows display as adjusted the first time.
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
resume=UUID=<filter> resume_offset=25731072
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Panasonic product: CF-53AAGHYDM v: 001 serial: <superuser required> Chassis:
type: 10 v: 001 serial: <superuser required>
Mobo: Panasonic model: CF53-1 v: 1 serial: <superuser required> BIOS: American Megatrends
v: 1.00L14 date: 07/12/2011
Battery:
ID-1: BAT1 charge: 73.7 Wh (100.0%) condition: 73.7/91.0 Wh (81.0%) volts: 12.3 min: 10.7
model: Panasonic CF-VZSU46 type: Li-ion serial: <filter> status: not charging
Device-1: hid-00:02:76:2c:7f:27-battery model: ThinkPad Bluetooth Laser Mouse serial: N/A
charge: N/A status: discharging
CPU:
Info: model: Intel Core i5-2520M bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 873 high: 1000 min/max: 800/3200 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 800 2: 894 3: 800 4: 1000 bogomips: 19955
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Matsushita
driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
active: LVDS-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0126
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
Monitor-1: LVDS-1 res: 1366x768 hz: 58 size: N/A modes: 1366x768
API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
direct-render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Matsushita 6
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 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 82579LM Gigabit Network vendor: Matsushita driver: e1000e v: kernel port: e080
bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel modules: wl
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 0a:00.0 chip-ID: 8086:0082 class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: wwan0 state: down mac: N/A
Bluetooth:
Device-1: Alps UGTZ4 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-1.1:3 chip-ID: 044e:3001
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 1.2 lmp-v: 2.1
sub-v: 149c hci-v: 2.1 rev: 149c
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 111.79 GiB used: 89.8 GiB (80.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Intel model: SSDSC2BB120G6R size: 111.79 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: DL2B scheme: MBR
Partition:
ID-1: / raw-size: 111.78 GiB size: 109.47 GiB (97.93%) used: 89.8 GiB (82.0%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 10.64 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 68.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2059 libs: 1044 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.it.ubc.ca/mxlinux/mx/repo/ bookworm main non-free
2: deb http://mirror.it.ubc.ca/mxlinux/mx/repo/ bookworm ahs
Info:
Processes: 225 Uptime: 1h 3m wakeups: 4 Memory: 7.64 GiB used: 1.72 GiB (22.5%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 3:07 pm
by dolphin_oracle
m_pav wrote: Sat Jul 01, 2023 12:39 am
Something a little funky going on with the default conky. On startup, Live and installed on 2 machines with Intel Graphics, the minutes are missing altogether but the rest of it is there. Images are from the Celeron based NUC, but identical issue on both machines. The issue prevails whether I boot the machines with Modesetting or Intel Drivers using MX Tweak between boots. I can get the minutes to display on the Laptop by opening MX Conky Manager and selecting another conky to display simultaneously, then uncheck it so only Cowon-midblue remains, but on the NUC, it's a more hit and miss.
Can anybody else replicate this?
Live-Boot1.jpg
Live-Boot2.jpg
My Daily Driver
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=/antiX/vmlinuz quiet splasht nosplash lang=en_NZ kbd=us
tz=Pacific/Auckland hwclock=local grubsave
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: LENOVO product: 20FHCTO1WW v: ThinkPad T560 serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20FHCTO1WW v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO
v: N1KET50W (1.37 ) date: 11/20/2020
Battery:
ID-1: BAT0 charge: 39.2 Wh (99.5%) condition: 39.4/44.5 Wh (88.5%) volts: 12.6 min: 11.4
model: SONY 45N1743 type: Li-poly serial: <filter> status: not charging
ID-2: BAT1 charge: 62.7 Wh (100.0%) condition: 62.7/72.2 Wh (86.9%) volts: 12.4 min: 11.1
model: SANYO 45N1125 type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Core i7-6600U bits: 64 type: MT MCP arch: Skylake gen: core 6 level: v3
note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x4E (78) stepping: 3
microcode: 0xE2
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 2800 min/max: 400/3400 scaling: driver: intel_pstate governor: powersave
cores: 1: 2800 2: 2800 3: 2800 4: 2800 bogomips: 22399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Lenovo driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
Device-2: Lite-On Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:6 chip-ID: 04ca:7058
class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: LG Display 0x054f built: 2016 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 520 (SKL GT2)
direct-render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d70 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 Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:156f class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24f3 class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: wwan0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:5
chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 1.94 TiB used: 2.04 GiB (0.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Netac model: USB Flash Drive size: 119.24 GiB
block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 1301 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 29.0 C pch: 28.5 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1046 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 200 Uptime: 47m wakeups: 3 Memory: 15.48 GiB used: 1.7 GiB (11.0%) 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: UEFI
Crappy old Intel NUC Celeron N3050
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: hwclock=local
lang=en_NZ tz=Pacific/Auckland quiet splasht nosplash
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: Intel model: NUC5CPYB v: H61145-404 serial: <superuser required>
UEFI-[Legacy]: Intel v: PYBSWCEL.86A.0043.2015.0904.1904 date: 09/04/2015
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont level: v2 built: 2015-17
process: Intel 14nm family: 6 model-id: 0x4C (76) stepping: 3 microcode: 0x351
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB desc: d-2x24 KiB; i-2x32 KiB
L2: 2 MiB desc: 2x1024 KiB
Speed (MHz): avg: 681 high: 792 min/max: 480/2160 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 792 2: 571 bogomips: 6400
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics
driver: i915 v: kernel arch: Gen-8 process: Intel 14nm built: 2014-15 ports: active: DP-1
empty: DP-2,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:22b1 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.48x10.91") s-diag: 523mm (20.6")
Monitor-1: DP-1 model: LG (GoldStar) W2242 serial: <filter> built: 2010 res: 1680x1050 hz: 60
dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65") diag: 585mm (23") ratio: 3:2, 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 400 (BSW) direct-render: Yes
Audio:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2284 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 Wireless 3165 driver: iwlwifi v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:3165 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Intel driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-5.1:4
chip-ID: 8087:0a2a class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 1000 hci-v: 4.2 rev: 1000
Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 117.55 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SP310 size: 59.63 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5.2 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: A-Data model: USB Flash Drive size: 57.92 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1100 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: 2.02 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
maj-min: 8:2
Sensors:
System Temperatures: cpu: 41.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2062 libs: 1046 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://la.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 198 Uptime: 4m wakeups: 4 Memory: 3.74 GiB used: 1.12 GiB (29.9%) 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)
this a problem with the the build-iso theme, not the conky. will have fixed later today, I know the problem. thanks for the repor.t
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 3:31 pm
by rej
Hi-
MX-23 Beta Live USB Persistence made from installed, configured snapshot:
"Wi-fi network connection" in Systray Icons - piling up.
Because I never saw this before (and don't usually use Live with Persistence), I don't know if this is a new normal or a glitch.
Please ignore this post if this is supposed to be happening.
Thank you.
Code: Select all
Snapshot created on: 20230625_1354
System:
Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: hwclock=local persist_all
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_x64 Libretto June 25 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: LENOVO product: 20BWCTO1WW v: ThinkPad T450s serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20BWCTO1WW v: SDK0E50512 STD serial: <superuser required>
UEFI-[Legacy]: LENOVO v: JBET48WW (1.13 ) date: 04/20/2015
Battery:
ID-1: BAT0 charge: 11.4 Wh (96.6%) condition: 11.8/23.5 Wh (50.4%) volts: 12.4 min: 11.4
model: LGC 45N1113 type: Li-ion serial: <filter> status: not charging
ID-2: BAT1 charge: 14.0 Wh (95.9%) condition: 14.6/23.5 Wh (62.3%) volts: 12.4 min: 11.4
model: LGC 45N1127 type: Li-ion serial: <filter> status: not charging
CPU:
Info: model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell gen: core 5 level: v3
note: check built: 2015-18 process: Intel 14nm family: 6 model-id: 0x3D (61) stepping: 4
microcode: 0x1D
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 674 high: 798 min/max: 500/2700 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 600 2: 798 3: 798 4: 500 bogomips: 17559
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel arch: Gen-8
process: Intel 14nm built: 2014-15 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
Monitor-1: eDP-1 model: AU Optronics 0x303e built: 2012 res: 1600x900 hz: 60 dpi: 132
gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1600x900
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 5500 (BDW GT2)
direct-render: Yes
Audio:
Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:03.0
chip-ID: 8086:160c class-ID: 0403
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 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 Ethernet I218-V vendor: Lenovo driver: e1000e v: kernel port: 4080
bus-ID: 00:19.0 chip-ID: 8086:15a3 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee v: kernel
modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:818b
class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 2-7:4 chip-ID: 0bda:8761
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 4380 hci-v: 4.0 rev: e3e
Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 502.14 GiB used: 44.3 GiB (8.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0105 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Transcend model: TS128GMTS430S size: 119.24 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: U17A
scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 type: USB model: General USB Flash Disk size: 116.06 GiB
block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Kingston model: DataTraveler 2.0 size: 28.84 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-5: /dev/sde maj-min: 8:64 type: USB vendor: Kingston model: DataTraveler 2.0 size: 14.42 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP 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: file size: 3 GiB used: 0 KiB (0.0%) priority: -2
file: /live/boot-dev/swap-file
Sensors:
System Temperatures: cpu: 42.0 C pch: 47.5 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: pm: dpkg pkgs: 2109 libs: 1075 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/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://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
Processes: 217 Uptime: 2h 12m wakeups: 4 Memory: 7.46 GiB used: 1.36 GiB (18.3%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 3:50 pm
by Jerry3904
What happens if you click on the bottom button "Clear Known Items"?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 5:40 pm
by andy
andy wrote: Fri Jun 30, 2023 11:15 am
andy wrote: Fri Jun 30, 2023 10:46 am
...
is there any possibility to properly prepare LUKS+BTRFS manually from live session just before install, to achieve proper operation of the trio?
...
As I did't recieve any answer, even "I don't know (yet)", etc..
So I decided to investigate for myself. Sacrificed five hours until now. (I am not so effective as those, who know better where to search)
Here is, what I have found:
in Linux Mint the result is
Code: Select all
mint@mint-VirtualBox:~$ sudo btrfs subvolume get-default /
ID 5 (FS_TREE)
in MX Linux
Code: Select all
mx@mx:~
$ sudo btrfs subvolume get-default /
ID 256 gen 82 top level 5 path @
after changing default subvolume, the result is the same.
Code: Select all
$ sudo btrfs subvolume set-default 5 /
mx@mx:~
$ sudo btrfs subvolume get-default /
ID 5 (FS_TREE)
in Linux Mint, after creating some manual and automatic snapshots
Code: Select all
mint@mint-VirtualBox:~$ sudo btrfs subvolume list /
[sudo] password for mint:
ID 256 gen 129 top level 5 path @
ID 257 gen 130 top level 5 path @home
ID 258 gen 129 top level 5 path timeshift-btrfs/snapshots/2023-07-01_19-37-37/@
ID 259 gen 75 top level 5 path timeshift-btrfs/snapshots/2023-07-01_19-53-27/@
ID 260 gen 127 top level 5 path timeshift-btrfs/snapshots/2023-07-01_22-00-02/@
After reading this:
https://github.com/linuxmint/timeshift/issues/90
I checked kernel parameter
rootflags=subvol=@
It is set accordingly.
Timeshift still does not allow to use BTRFS in settings.
BUT: somehow (I almost never boot with SystemD) I got an idea to boot with SystemD,
and: Timeshift allowed to use BTRFS. Creating snapshot last unusually long time (about 30 secs), but the snapshot did not appear in the list in the GUI windows of Timeshift.
by checking I get
Code: Select all
mx@mx:~
$ sudo btrfs subvolume list /
[sudo] password for mx:
ID 256 gen 72 top level 5 path @
ID 257 gen 72 top level 5 path @home
ID 258 gen 58 top level 256 path srv
I have tried to delete subvolume
Code: Select all
sudo btrfs subvolume delete -i 258 /
after few seconds by checking I get again
mx@mx:~
$ sudo btrfs subvolume list /
[sudo] password for mx:
ID 256 gen 72 top level 5 path @
ID 257 gen 72 top level 5 path @home
ID 258 gen 58 top level 256 path srv
but as I read, the operation is finishing in the background, so I let a minute pass, then do reboot, which was waiting about one more minute to finish.
After next boot (with SystemD of course), the SRV subvolume was still there, but issued and checked again:
Code: Select all
mx@mx:~
$ sudo btrfs subvolume delete -i 258 --commit-each /
Delete subvolume (commit): '//@/srv'
mx@mx:~
$ sudo btrfs subvolume list /
ID 256 gen 92 top level 5 path @
ID 257 gen 91 top level 5 path @home
Checking Timeshift settings again, were fine, created snapshot, progress window closed with the message snapshot was created.
Again no line in the table.
Code: Select all
mx@mx:~
$ sudo btrfs subvolume list /
ID 256 gen 103 top level 5 path @
ID 257 gen 100 top level 5 path @home
Very weird.
Clicking on Browse, Dolphin run as root shows four subdirectories of these four attempts,
but each one is empty.
/run/timeshift/5456/backup/timeshift-btrfs/snapshots/
Closed Timeshift GUI, run in terminal:
Code: Select all
mx@mx:~
$ sudo timeshift --list
Mounted '/dev/dm-0 (sda4)' at '/run/timeshift/6082/backup'
btrfs: Quotas are not enabled
Device : /dev/dm-0 (sda4)
UUID : a528b0bb-64ae-4342-a6ba-881e8c3575f2
Path : /run/timeshift/6082/backup
Mode : BTRFS
Status : No snapshots on this device
First snapshot requires: 0 B
No snapshots found
Code: Select all
mx@mx:~
$ cat /etc/timeshift/timeshift.json
{
"backup_device_uuid" : "a528b0bb-64ae-4342-a6ba-881e8c3575f2",
"parent_device_uuid" : "afd1330e-fdbb-4f63-a00e-62044032f7a1",
"do_first_run" : "false",
"btrfs_mode" : "true",
"include_btrfs_home_for_backup" : "false",
"include_btrfs_home_for_restore" : "false",
"stop_cron_emails" : "true",
"schedule_monthly" : "false",
"schedule_weekly" : "false",
"schedule_daily" : "true",
"schedule_hourly" : "false",
"schedule_boot" : "false",
"count_monthly" : "2",
"count_weekly" : "3",
"count_daily" : "5",
"count_hourly" : "6",
"count_boot" : "5",
"date_format" : "%Y-%m-%d %H:%M:%S",
"exclude" : [],
"exclude-apps" : []
Code: Select all
mx@mx:~
$ sudo timeshift --create --comments "from_commandline"
Using system disk as snapshot device for creating snapshots in BTRFS mode
Mounted '/dev/dm-0 (sda4)' at '/run/timeshift/6136/backup'
btrfs: Quotas are not enabled
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/6136/backup
Created directory: /run/timeshift/6136/backup/timeshift-btrfs/snapshots/2023-07-01_17-08-24
E: ERROR: cannot snapshot '/run/timeshift/6136/backup/@': Text file busy
E: btrfs returned an error: 256
E: Failed to create subvolume snapshot: @
Failed to create snapshot
------------------------------------------------------------------------------
Removing snapshots (incomplete):
------------------------------------------------------------------------------
Removing snapshot: 2023-07-01_16-15-31
Deleted directory: /run/timeshift/6136/backup/timeshift-btrfs/snapshots/2023-07-01_16-15-31
Removed snapshot: 2023-07-01_16-15-31
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Removing snapshot: 2023-07-01_16-26-31
Deleted directory: /run/timeshift/6136/backup/timeshift-btrfs/snapshots/2023-07-01_16-26-31
Removed snapshot: 2023-07-01_16-26-31
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Removing snapshot: 2023-07-01_16-28-03
Deleted directory: /run/timeshift/6136/backup/timeshift-btrfs/snapshots/2023-07-01_16-28-03
Removed snapshot: 2023-07-01_16-28-03
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Removing snapshot: 2023-07-01_16-58-29
Deleted directory: /run/timeshift/6136/backup/timeshift-btrfs/snapshots/2023-07-01_16-58-29
Removed snapshot: 2023-07-01_16-58-29
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Removing snapshot: 2023-07-01_17-08-24
Deleted directory: /run/timeshift/6136/backup/timeshift-btrfs/snapshots/2023-07-01_17-08-24
Removed snapshot: 2023-07-01_17-08-24
------------------------------------------------------------------------------
Ran again:
Code: Select all
mx@mx:~
$ sudo timeshift --create --comments "from_commandline"
Using system disk as snapshot device for creating snapshots in BTRFS mode
Mounted '/dev/dm-0 (sda4)' at '/run/timeshift/6220/backup'
btrfs: Quotas are not enabled
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/6220/backup
Created directory: /run/timeshift/6220/backup/timeshift-btrfs/snapshots/2023-07-01_17-10-22
E: ERROR: cannot snapshot '/run/timeshift/6220/backup/@': Text file busy
E: btrfs returned an error: 256
E: Failed to create subvolume snapshot: @
Failed to create snapshot
------------------------------------------------------------------------------
Removing snapshots (incomplete):
------------------------------------------------------------------------------
Removing snapshot: 2023-07-01_17-10-22
Deleted directory: /run/timeshift/6220/backup/timeshift-btrfs/snapshots/2023-07-01_17-10-22
Removed snapshot: 2023-07-01_17-10-22
------------------------------------------------------------------------------
As I have again traded few hours of my sleep, I am giving up.
I hope my discoveries will save the time for the developers.
Attaching logs, too.
Interesting info here (maybe not related to timeshift, but related to BTRFS and switching subvolumes for root):
https://bbs.archlinux.org/viewtopic.php?id=210582
Maybe a time to check different solution.
https://github.com/digint/btrbk
or
https://gitlab.com/btrfs-assistant/btrfs-assistant
Does somebody have experiences with BTRFS Assistant?
Does it work without SystemD?
Enough of Timeshift (without "F" ???
)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 6:11 pm
by dolphin_oracle
@andy we have not given up on timeshift, but the particular problem is not likely to be fixed before release of mx23. timeshift is very finicky about how its set up, and our btrfs setup does not match linux mint's.
one other thing, a btrfs snapshot will apparently fail if a swapfile is present in the subvolume.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 01, 2023 7:01 pm
by fehlix
andy wrote: Sat Jul 01, 2023 5:40 pm
andy wrote: Fri Jun 30, 2023 11:15 am
andy wrote: Fri Jun 30, 2023 10:46 am
...
is there any possibility to properly prepare LUKS+BTRFS manually from live session just before install, to achieve proper operation of the trio?
...
As I did't recieve any answer, even "I don't know (yet)", etc..
Maybe you missed the answer given
viewtopic.php?p=731447#p731447
And yes, we know what this issue is, the fix we have for non-luks+btrfs unfortunately won't work with btrfs+luks.
I'v applied already the MX-patch to latest Linux Mint provided version, which does fix the subvol issue,
but for some reason not with the combo luks+btrfs.
So suggest, stay patient until further findings to fix have been made.
Thanks
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 1:45 am
by rej
Jerry3904 wrote: Sat Jul 01, 2023 3:50 pm
What happens if you click on the bottom button "Clear Known Items"?
Hi Jerry-
It removes all the W-fi entries and un-checks what was previously checked as "Hidden".
Then it immediately starts accumulating again.
That was just a couple of days worth in the image I had attached.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 6:00 am
by Eadwine Rose
Stevo wrote: Thu Jun 29, 2023 8:41 pm
I don't know if anyone has reported VLC losing hardware accelerated decoding and encoding in Bookworm, but that seems to be unavoidable with the Debian packages.
5.2.3. Limited hardware-accelerated video encoding/decoding support in VLC
The VLC video player supports hardware-accelerated video decoding and encoding via VA-API and VDPAU. However, VLC's support for VA-API is tightly related to the version of FFmpeg. Because FFmpeg was upgraded to the 5.x branch, VLC's VA-API support has been disabled. Users of GPUs with native VA-API support (e.g., Intel and AMD GPUs) may experience high CPU usage during video playback and encoding.
Users of GPUs offering native VDPAU support (e.g., NVIDIA with non-free drivers) are not affected by this issue.
Support for VA-API and VDPAU can be checked with vainfo and vdpauinfo (each provided in a Debian package of the same name).
@Stevo haven't seen you post here since? Has anyone tested that downgrade I quoted here to see if that fixes things?
viewtopic.php?p=729379#p729379
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 6:31 am
by sughero
i'm trying mx23 beta
I noticed that the thumbnails of the image file icons (jpg, png etc) do not appear.
on debian stable the problem is not there
on mx23 beta I saw that the libgdk-pixbuf-2.0-dev and libgdk-pixbuf2.0-bin packages are missing
moreover, thumbnails do not appear on device folders such as smartphones
translated by google
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 7:30 am
by j2mcgreg
sughero wrote: Sun Jul 02, 2023 6:31 am
i'm trying mx23 beta
I noticed that the thumbnails of the image file icons (jpg, png etc) do not appear.
on debian stable the problem is not there
on mx23 beta I saw that the libgdk-pixbuf-2.0-dev and libgdk-pixbuf2.0-bin packages are missing
moreover, thumbnails do not appear on device folders such as smartphones
translated by google
We need your QSI.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 10:16 am
by sughero
sorry
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: MATE v: 1.26.0 info: mate-panel wm: marco v: 1.26.1 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 System: Hewlett-Packard product: HP Compaq 8100 Elite CMT PC v: N/A
serial: <superuser required> Chassis: type: 6 serial: <superuser required>
Mobo: Hewlett-Packard model: 304Bh serial: <superuser required> BIOS: Hewlett-Packard
v: 786H1 v01.13 date: 07/14/2011
CPU:
Info: model: Intel Core i5 650 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1331 high: 1463 min/max: 1199/3333 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1463 2: 1199 3: 1463 4: 1199 bogomips: 25538
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: marco v: 1.26.1 driver: X: loaded: intel
dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 359x203mm (14.13x7.99") s-diag: 412mm (16.24")
Monitor-1: VGA-1 mapped: VGA1 res: 1360x768 hz: 60 size: N/A modes: max: 1024x768 min: 640x480
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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 82578DM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
port: 1100 bus-ID: 00:19.0 chip-ID: 8086:10ef class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.36 TiB used: 8.14 GiB (0.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: HP74 scheme: MBR
Partition:
ID-1: / raw-size: 47.86 GiB size: 46.81 GiB (97.80%) used: 8.14 GiB (17.4%) fs: ext4
dev: /dev/sdb8 maj-min: 8:24
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 3.04 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb6
maj-min: 8:22
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2040 libs: 961 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/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
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://it.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 196 Uptime: 1m wakeups: 1 Memory: 3.63 GiB used: 887 MiB (23.9%) 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)
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 10:18 am
by shmu26
This thread seems to have uncovered a bug in MX-23 beta 2
viewtopic.php?p=731648#p731648
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 10:21 am
by dolphin_oracle
sughero wrote: Sun Jul 02, 2023 10:16 am
sorry
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: MATE v: 1.26.0 info: mate-panel wm: marco v: 1.26.1 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 System: Hewlett-Packard product: HP Compaq 8100 Elite CMT PC v: N/A
serial: <superuser required> Chassis: type: 6 serial: <superuser required>
Mobo: Hewlett-Packard model: 304Bh serial: <superuser required> BIOS: Hewlett-Packard
v: 786H1 v01.13 date: 07/14/2011
CPU:
Info: model: Intel Core i5 650 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1331 high: 1463 min/max: 1199/3333 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1463 2: 1199 3: 1463 4: 1199 bogomips: 25538
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0042 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: marco v: 1.26.1 driver: X: loaded: intel
dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 359x203mm (14.13x7.99") s-diag: 412mm (16.24")
Monitor-1: VGA-1 mapped: VGA1 res: 1360x768 hz: 60 size: N/A modes: max: 1024x768 min: 640x480
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK) direct-render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 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 82578DM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
port: 1100 bus-ID: 00:19.0 chip-ID: 8086:10ef class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.36 TiB used: 8.14 GiB (0.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: HP74 scheme: MBR
Partition:
ID-1: / raw-size: 47.86 GiB size: 46.81 GiB (97.80%) used: 8.14 GiB (17.4%) fs: ext4
dev: /dev/sdb8 maj-min: 8:24
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 3.04 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb6
maj-min: 8:22
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2040 libs: 961 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/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
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://it.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 196 Uptime: 1m wakeups: 1 Memory: 3.63 GiB used: 887 MiB (23.9%) 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)
Mate is not one of our official desktops. Does installing either of the packages fix your issue?
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 10:33 am
by sughero
installing the 2 packages solved the problem on the pc folders.
the report referred to the fact that on the stable debian the 2 packages are installed.
smartphone preview view doesn't work on fluxbox desktop either on mx23 beta (nor on official debian either)
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 11:20 am
by Jerry3904
smartphone preview view
How are you trying to see it? In Thunar?
MX samba config
Posted: Sun Jul 02, 2023 11:22 am
by richierich
Posting from MX-23 beta 2 on my machine, cannot share videos using share option in thunar or using MX samba config, had no problem in older versions of MX, could share video from computer to vlc on phone and Kodi on home network.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 11:36 am
by sughero
How are you trying to see it? In Thunar?
smartphone photos.
i tried in various ways: thunar and caja.
As a normal user and as root, unfortunately without results
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 2:29 pm
by shmu26
The issue is about controlling the scroll LED behavior for alternative keyboard layouts. The LED lights up when the user switches keyboard layout, and that shouldn't be the default behavior. Or at least, it should be configurable like it says in the documentation. However, the behavior does not respond to configuration.
This concerns the Xfce desktop, and the underlying problem seems to be with gxkb which is the keyboard switcher. Gxkb also seems to be responsible for the whole "System Keyboard" section in Xfce settings.
The github page for gxkb is here:
https://github.com/zen-tools/gxkb
It says that gxkb is configurable by means of
However, changes made to that config file do not stick. They revert to their default values.
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2208 date: 07/09/2021
Battery:
ID-1: hidpp_battery_0 charge: 83% condition: N/A volts: 4.0 min: N/A model: Logitech G903
LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A serial: <filter> status: discharging
CPU:
Info: model: Intel Core i7-9700 bits: 64 type: MCP arch: Coffee Lake gen: core 9 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
microcode: 0xF8
Topology: cpus: 1x cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB
L2: 2 MiB desc: 8x256 KiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 4501 high: 4510 min/max: 800/4700 scaling: driver: intel_pstate
governor: powersave cores: 1: 4500 2: 4501 3: 4500 4: 4497 5: 4501 6: 4500 7: 4500 8: 4510
bogomips: 48000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Device-2: USB C Video Adaptor type: USB driver: N/A bus-ID: 1-3.1.1:8 chip-ID: 25a4:9321
class-ID: 1100 serial: <filter>
Device-3: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.4:7
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 4480x1080 s-dpi: 96 s-size: 1185x286mm (46.65x11.26")
s-diag: 1219mm (47.99")
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: VG27AQ1A serial: <filter>
built: 2020 res: 1920x1080 hz: 120 dpi: 82 gamma: 1.2 size: 596x336mm (23.46x13.23")
diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: right model: Samsung S24B300 serial: <filter>
built: 2013 res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54")
diag: 598mm (23.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 1-3.4:7 chip-ID: 0c45:636b bus-ID: 00:1f.3 class-ID: 0102 chip-ID: 8086:a2f0
serial: <filter> class-ID: 0403
Device-2: Microdia USB Live camera 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: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-4.1:4
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: eth1 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 1-10:6 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 2.26 TiB used: 902.01 GiB (39.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: K1B3 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD120 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ACF0
scheme: GPT
Partition:
ID-1: / raw-size: 46.96 GiB size: 45.92 GiB (97.79%) used: 12.9 GiB (28.1%) fs: ext4
dev: /dev/sda7 maj-min: 8:7
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.5 MiB (26.5%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 2233 pm: dpkg pkgs: 2227 libs: 1171 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 6
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/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://mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:
Processes: 298 Uptime: 43m wakeups: 8 Memory: 15.49 GiB used: 9.32 GiB (60.2%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 2:38 pm
by fehlix
shmu26 wrote: Sun Jul 02, 2023 2:29 pm
The issue is about controlling the scroll LED behavior for alternative keyboard layouts. The LED lights up when the user switches keyboard layout, and that shouldn't be the default behavior. Or at least, it should be configurable.
This concerns the Xfce desktop, and the underlying problem seems to be with gxkb which is the keyboard switcher. Gxkb also seems to be responsible for the whole "System Keyboard" section in Xfce settings.
You can disable gxkb switcher and enable Xfce buildin keyboard-layout plugin.
Let us know whether it fxes the issues you mentioned.
shmu26 wrote: Sun Jul 02, 2023 2:29 pm
The github page for gxkb is here:
https://github.com/zen-tools/gxkb
It says that gxkb is configurable by means of
However, changes made to that config file do not stick. They revert to their default values.
That's by design, in order to let Xfce-keyboard selection work and to allow user to select keyboard at login.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 2:42 pm
by shmu26
@fehlix I disabled gxkb switcher, and enabled the Xfce built-in switcher, but strangely it doesn't solve the issue. The LED still lights up when I switch to my alternative keyboard layout.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 6:50 pm
by Stuart_M
@shmu26: I got it working. The reason the change did not take effect was because a reboot is needed and I had only been testing on a Live MX-23 beta2. See my Post #10
viewtopic.php?p=731701#p731701 in your original thread for a little more detail.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 02, 2023 9:59 pm
by shmu26
@Stuart_M Yes, it works after a reboot, like you said.
Re: MX samba config
Posted: Mon Jul 03, 2023 5:02 am
by FullScale4Me
richierich wrote: Sun Jul 02, 2023 11:22 am
Posting from MX-23 beta 2 on my machine, cannot share videos using share option in thunar or using MX samba config, had no problem in older versions of MX, could share video from computer to vlc on phone and Kodi on home network.
This is covered in the MX23 user manual, Firewall section number 4 dot 5 dot 1.
User manual is linked from your start menu and an icon on the desktop.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 03, 2023 9:17 am
by Arnox
Tested with both SysVInit and systemd.
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
init=/lib/systemd/systemd
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2802 date: 10/22/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 5 3600XT 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: 0x8701021
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: 3088 high: 4434 min/max: 2200/4635 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 4434 2: 4366 3: 2951 4: 2041 5: 1871 6: 2795
7: 2793 8: 4347 9: 3959 10: 1910 11: 2794 12: 2795 bogomips: 91036
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GP102 [TITAN Xp] driver: nvidia v: 525.105.17 non-free: 530.xx+
status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-21 pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.0 chip-ID: 10de:1b02 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71") s-diag: 554mm (21.82")
Monitor-1: DP-5 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
diag: 547mm (21.54") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.105.17 renderer: NVIDIA TITAN Xp/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GP102 HDMI Audio driver: snd_hda_intel v: kernel pcie: bus-ID: 7-3:2
chip-ID: b58e:9e84 gen: 3 speed: 8 GT/s class-ID: 0300 serial: <filter> lanes: 16 bus-ID: 09:00.1
chip-ID: 10de:10ef 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
Device-3: Blue Microphones Yeti Stereo Microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid
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: f000 bus-ID: 05: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.96 TiB used: 201.69 GiB (10.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 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QEXM7 temp: 47.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SUV400S37120G size: 111.79 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 96R9 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.82 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 95.53 GiB size: 95.53 GiB (100.00%) used: 30.04 GiB (31.4%) fs: btrfs
dev: /dev/sdb1 maj-min: 8:17
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sdb3 maj-min: 8:19
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 16 GiB used: 42.2 MiB (0.3%) priority: -2 dev: /dev/sdb2
maj-min: 8:18
Sensors:
System Temperatures: cpu: 58.0 C mobo: 44.0 C gpu: nvidia temp: 59 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 34%
Repos:
Packages: 2568 pm: dpkg pkgs: 2562 libs: 1430 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 6
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://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
Processes: 318 Uptime: 59m wakeups: 5 Memory: 15.52 GiB used: 3.95 GiB (25.5%) Init: systemd
v: 252 target: graphical (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: UEFI
8B. Foliate online catalogs are pretty much non-functional. The Standard Ebooks catalog, for example, causes an application hang when selecting All Ebooks.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 03, 2023 9:34 am
by Marek
Hello all! Forgive me for participating so little in the life of the forum. I wanted to ask if the current test version, is suitable for daily use? I don't play, but only browse web content, telegram and discord, sometimes spreadsheets or other documents. To review the entire topic, I would have to spend a lot of time, and I still lack it
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 03, 2023 9:49 am
by Jerry3904
You would do better to wait a few more days for the RC to become available.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 03, 2023 7:43 pm
by thinkpadx
Thanks Jerry! I check in multiple times a day waiting for new from DO about the RC1 release. :-)
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 10:13 am
by i_ri
moon 98%
hello dolphin_oracle
Independence Day, USA aka national hand-injury day.
In wofi drun,run when type in search "calc" three results xcalc, GtkHash, Galculator.
In dmenu,run when type in search "calc" one result xcalc.
In rofi,drun when type in search "calc" one result GtkHash.
In xfce appfinder "calc" is seven results GtkHash, Galculator, calendar, settings.
In synapse search "calc" four results xcalc, /rofi/calc-help, two-search files for calc.
double-click? no; single tap now.
I have my rofi it works throughout categories with touchpad single tap on mxfb-appfinder.rasi. Plugged in everwhere! me select Mouse, until it worked on all rofi pages.
Code: Select all
#!
THEMERFI=$(cat ~/.config/rofi/config.rasi |grep @theme|cut -d '"' -f2)
rofi -show drun -hover-select -me-select-entry '' -me-accept-entry MousePrimary -theme $THEMERFI
/usr/local/bin/rofinder
An .s h, I think you already gave it the name mxfb-appfinder, but i cannot find it.
rofi is lost without tint2; a Launcher?
With this .sample/bin/ This is a .desktop file for rofi-mx, mxfb-appfinder, sample named rofinder.
Code: Select all
[Desktop Entry]
Exec=rofinder
Icon=/usr/share/icons/Papirus/32x32/apps/pyzologo.svg
StartupNotify=false
Terminal=false
Type=Application
Categories=Utility;
Name=Application roFinder
Name[am]=ፕሮግራም ፈላጊ
Name[ar]=مكتشف التطبيقات
Name[ast]=Guetador d'aplicaciones
Name[be]=Пошук праграм
Name[bg]=Търсене на програма
Name[bn]=অ্যাপ্লিকেশন অনুসন্ধানকারী
Name[ca]=Cercador d'aplicacions
Name[cs]=Vyhledávač aplikací
Name[da]=Programfinder
Name[de]=Anwendungsfinder
Name[el]=Εύρεση εφαρμογών
Name[en_AU]=Application Finder
Name[en_CA]=Application Finder
Name[en_GB]=Application Finder
Name[es]=Buscador de aplicaciones
Name[et]=Rakenduste leidja
Name[eu]=Aplikazio bilatzailea
Name[fi]=Sovellusten hakutyökalu
Name[fr]=Liste des applications
Name[gl]=Buscador de aplicacións
Name[he]=מוצא יישומים
Name[hi]=अनुप्रयोग खोज
Name[hr]=Nalaznik programa
Name[hu]=Alkalmazáskereső
Name[hy_AM]=Յաւելուածների Որոնում
Name[hye]=Յաւելուածների Որոնում
Name[id]=Pencari Aplikasi
Name[ie]=Trovator de applicationes
Name[is]=Forritaleit
Name[it]=Trova applicazioni
Name[ja]=アプリケーションファインダー
Name[kk]=Қолданбаларды табушы
Name[ko]=프로그램 탐색기
Name[lt]=Programų paieška
Name[lv]=Lietotņu meklētājs
Name[ms]=Pencari Aplikasi
Name[nb]=Programkatalog
Name[nl]=Toepassingenzoeker
Name[nn]=Programfinnar
Name[oc]=Lista de las aplicacions
Name[pa]=ਐਪਲੀਕੇਸ਼ਨ ਫਾਈਡਰ
Name[pl]=Wyszukiwarka programów
Name[pt]=Localizar aplicações
Name[pt_BR]=Localizador de aplicativos
Name[ro]=Pornire de programe
Name[ru]=Поиск приложений
Name[si]=යෙදුම් සෙවුම
Name[sk]=Vyhľadávač aplikácií
Name[sl]=Iskalec aplikacije
Name[sq]=Gjetës Aplikacionesh
Name[sr]=Проналазач програма
Name[sv]=Programstartare
Name[te]=అనువర్తన శోధకం
Name[th]=เครื่องมือค้นหาโปรแกรม
Name[tr]=Uygulama Bulucu
Name[ug]=پروگرامما ئىزدىگۈ
Name[uk]=Пошук встановлених програм
Name[ur]=اطلاقیہ تلاش کار
Name[ur_PK]=اطلاقیہ تلاش کار
Name[vi]=Application Finder
Name[zh_CN]=应用程序查找器
Name[zh_HK]=應用程式協尋器
Name[zh_TW]=應用程式協尋器
Comment=rofi search for settings, Find and Launch installed applications
Comment[ar]=العثور و إطلاق التطبيقات المثبتة في نظامك
Comment[ast]=Alcuentra y llanza aplicaciones instalaes nel to sistema
Comment[be]=Пошук і запуск усталяваных у вашай сістэме праграм
Comment[bg]=Намиране и стартиране на инсталирани приложения
Comment[bn]=আপনার সিস্টেমে ইনস্টলকৃত অ্যাপ্লিকেশন খুঁজে বের করে চালু করুন
Comment[ca]=Cerqueu i llanceu les aplicacions instal·lades al vostre sistema
Comment[cs]=Umožňuje najít a spouštět aplikace nainstalované v systému.
Comment[da]=Find og start programmer, som er installeret på dit system
Comment[de]=Im System installierte Anwendungen finden und starten
Comment[el]=Εύρεση και εκτέλεση εγκατεστημένων εφαρμογών στο σύστημά σας.
Comment[en_AU]=Find and launch applications installed on your system
Comment[en_CA]=Find and launch applications installed on your system
Comment[en_GB]=Find and launch applications installed on your system
Comment[es]=Encuentre e inicie las aplicaciones instaladas en el sistema
Comment[et]=Leia ja käivita süsteemi paigaldatud rakendusi
Comment[eu]=Bilatu eta abiarazi sisteman instalatutako aplikazioak
Comment[fi]=Etsi ja käynnistä järjestelmään asennettuja sovelluksia
Comment[fr]=Rechercher et lancer des applications installées sur votre système
Comment[gl]=Busque e inicie aplicacións instaladas no sistema
Comment[he]=מציאה והפעלת יישומים המותקנים במחשבך
Comment[hi]=सिस्टम पर इंस्टॉल हो रखें अनुप्रयोग खोजकर आरंभ करें।
Comment[hr]=Nađi i pokreni programe instalirane u vašem sustavu
Comment[hu]=A rendszerre telepített alkalmazások keresése és indítása
Comment[hy_AM]=Որոնել եւ գործարկել համակարգում առկայ յաւելուածները
Comment[hye]=Որոնել եւ գործարկել համակարգում առկայ յաւելուածները
Comment[id]=Mencari dan menjalankan aplikasi terinstal di sistem anda
Comment[ie]=Trovar e lansar applicationes installat in vor sistema
Comment[is]=Finna og ræsa forrit sem uppsett eru á kerfinu
Comment[it]=Trova e avvia le applicazioni installate nel sistema
Comment[ja]=システムにインストールされたアプリケーションの検索および起動を行います
Comment[kk]=Жүйеңізде орнатылған қолданбаларды табады және орындайды
Comment[ko]=시스템에 설치한 프로그램을 찾고 실행합니다
Comment[lt]=Surasti ir paleisti programas įdiegtas jūsų sistemoje
Comment[lv]=Atrodiet un izsauciet lietotnes, kas ir instalētas jūsu sistēmā.
Comment[ms]=Cari dan lancar aplikasi dipasang pada sistem anda
Comment[nb]=Finn og kjør programmer installert på datamaskinen din
Comment[nl]=Zoek en start toepassingen die geïnstalleerd zijn in uw systeem
Comment[nn]=Finn og køyr alle programma på maskina di
Comment[oc]=Recercar e aviar d'aplicacions installadas sus vòstre sistèma
Comment[pa]=ਆਪਣੇ ਸਿਸਟਮ ਉੱਤੇ ਇੰਸਟਾਲ ਹੋਈਆਂ ਐਪਲੀਕੇਸ਼ਨ ਲੱਭੋ ਤੇ ਚਲਾਓ
Comment[pl]=Wyszukuje i uruchamia programy zainstalowane w systemie
Comment[pt]=Procura e inicia as aplicações instaladas no seu sistema
Comment[pt_BR]=Localize e execute aplicativos instalados no seu sistema
Comment[ro]=Căutați și porniți programe instalate în sistem
Comment[ru]=Поиск и запуск установленных в вашей системе приложений
Comment[si]=ඔබගේ පද්ධතියේ ස්ථාපනය කර ඇති යෙදුම් සොයා ක්රියාත්මක කරන්න
Comment[sk]=Vyhľadáva a spúšťa nainštalované aplikácie v systéme
Comment[sl]=Najdi in zaženi aplikacije nameščene na vaš sistem
Comment[sq]=Gjeni dhe nisni aplikacione të instaluar në sistemin tuaj
Comment[sr]=Пронађите и покрените неки од програма на систему
Comment[sv]=Sök och starta program som är installerade på ditt system
Comment[te]=మీ వ్యవస్థలో స్థాపించబడిన అనువర్తనాలను కనుగొను మరియు ప్రారంభించు
Comment[th]=ค้นหาและเรียกทำงานโปรแกรมที่ติดตั้งอยู่ในระบบของคุณ
Comment[tr]=Sisteminde kurulu uygulamaları bul ve başlat
Comment[ug]=كومپيۇتېرىڭىزغا ئورنىتىلغان پروگراممىلارنى ئىزدەيدۇ ۋە ئىجرا قىلىدۇ
Comment[uk]=Шукати та запускати програми встановлені в Вашій системі
Comment[ur]=نظام میں نصب اطلاقیے تلاش کریں اور چلائیں
Comment[ur_PK]=نظام میں نصب اطلاقیے تلاش کریں اور چلائیں
Comment[vi]=Tìm và chạy ứng dụng đã cài đặt trên hệ thống của bạn
Comment[zh_CN]=查找和启动在您系统上安装的应用程序
Comment[zh_HK]=尋找並啟動系統安裝的應用程式
Comment[zh_TW]=尋找並啟動您系統上安裝的應用程式
Keywords=program;applications;bookmarks;
Keywords[be]=праграма;праграмы;закладкі;
Keywords[bg]=програма;приложения, отметки;
Keywords[ca]=programar;aplicacions;marcadors;
Keywords[cs]=program;aplikace;záložky;
Keywords[da]=program;programmer;bogmærker;
Keywords[de]=Programm;Anwendungen;Lesezeichen;
Keywords[en_CA]=program;applications;bookmarks;
Keywords[es]=programa;aplicaciones;marcadores;
Keywords[et]=program;applications;bookmarks;programm;programmid;rakendus;rakendused;järjehoidjad;
Keywords[eu]=programak;aplikazioak;laster-markak;
Keywords[fr]=programme;applications;marque-pages;
Keywords[gl]=programas;aplicacións;marcadores;
Keywords[he]=program;applications;bookmarks;
Keywords[hi]=प्रोग्राम;अनुप्रयोग;पृष्ठ स्मृति;
Keywords[hy_AM]=ծրագիր;ծրագրեր;էջանիշեր;
Keywords[id]=program;aplikasi;markahbuku;
Keywords[ie]=programma;applicationes;marca-págines;
Keywords[it]=program;applications;bookmarks;
Keywords[ja]=プログラム;アプリケーション;ブックマーク;
Keywords[kk]=бағдарлама;қолданбалар;бетбелгілер;
Keywords[ko]=program;프로그램;applications;애플리케이션;앱;bookmarks;북마크;즐겨찾기;즐겨 찾기;
Keywords[lt]=programa;programos;žymelės;adresyno įrašai;
Keywords[ms]=program;aplikasi;tanda buku;
Keywords[nb]=program;programmer;bokmerker;
Keywords[nl]=programma;toepassingen;bladwijzers;
Keywords[oc]=programa;aplicacions;marcapagina;favorits;preferits;logicials;
Keywords[pl]=program;aplikacje;zakładki;
Keywords[pt]=programas;aplicações;marcadores;
Keywords[pt_BR]=programa, aplicativos, marcadores;
Keywords[ru]=приложение;приложения;закладки;
Keywords[sk]=program;aplikácie;záložky;
Keywords[sl]=program;aplikacija;zaznamki;
Keywords[sq]=program;aplikacione;faqerojtës;
Keywords[sr]=програм;апликације;белешке;забелешке;обележивачи;
Keywords[sv]=program;applikation;bokmärken
Keywords[th]=โปรแกรม;แอปพลิเคชัน;ที่คั่น;
Keywords[tr]=program;uygulamalar;yerimleri;yer imleri;
Keywords[uk]=програма;застосунки;закладки;
Keywords[zh_CN]=program;applications;bookmarks;程序;应用;书签;
Keywords[zh_HK]=程序；應用程序；書籤；
Keywords[zh_TW]=program;applications;bookmarks;
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 10:21 am
by baldyeti
Arnox wrote: Mon Jul 03, 2023 9:17 am
7B. Wayland is immediately crashing back to the login screen whenever one tries to start a Wayland session. SysVInit, systemd, doesn't matter. Only X11 works.
On plain debian bookworm (where the KDE wayland session seems to work from my limited testing), here are the wayland-related packages i see; are these pre-installed in MX23-beta (KDE) ?
Code: Select all
ii kwayland-data 4:5.103.0-1 all Qt library wrapper for Wayland libraries - data files
ii kwayland-integration:amd64 5.27.5-2 amd64 kwayland runtime integration plugins
ii kwin-wayland 4:5.27.5-3 amd64 KDE window manager, wayland version, PREVIEW release
ii libkf5waylandclient5:amd64 4:5.103.0-1 amd64 Qt library wrapper for Wayland libraries
ii libqt5waylandclient5:amd64 5.15.8-2 amd64 QtWayland client library
ii libqt5waylandcompositor5:amd64 5.15.8-2 amd64 QtWayland compositor library
ii libva-wayland2:amd64 2.17.0-1 amd64 Video Acceleration (VA) API for Linux -- Wayland runtime
ii libwayland-client0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - client library
ii libwayland-cursor0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - cursor library
ii libwayland-egl1:amd64 1.21.0-1 amd64 wayland compositor infrastructure - EGL library
ii libwayland-server0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - server library
ii plasma-workspace-wayland 4:5.27.5-2 amd64 Plasma Workspace for KF5 - Wayland integration
ii qtwayland5:amd64 5.15.8-2 amd64 QtWayland platform plugin
ii wayland-utils 1.1.0-1+b1 amd64 Wayland utilities
ii xwayland 2:22.1.9-1 amd64 X server for running X clients under Wayland
Personally i wouldn't mind if only X11 was pre-loaded in MX23, but then wayland should not even be offered as an option at the login manager level.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 11:17 am
by Jerry3904
@i_ri What is your expectation here?
In wofi drun,run when type in search "calc" three results xcalc, GtkHash, Galculator.
In dmenu,run when type in search "calc" one result xcalc.
In rofi,drun when type in search "calc" one result GtkHash.
In xfce appfinder "calc" is seven results GtkHash, Galculator, calendar, settings.
In synapse search "calc" four results xcalc, /rofi/calc-help, two-search files for calc.
As far as the name App Finder is concerned, it's way too late to change. You will not find it b/c it's not a program of any kind, it's just a theme of rofi.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 12:03 pm
by i_ri
Hello Jerry3904
sharing.
Facilitated Changing the tint2 button to the rofi /bin/Launcher command
channels me through to the touchpad connection i want for tap clicking.
The .desktop will appear in your Accessories menu with whatever name you give to it and is supposed to launch any theme, still testing that.
A .desktop in custom-toolbox, docks, ,, give to this rofi Masterpiece a button.
The MX instance of rofi icon is mxlogo.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 4:20 pm
by Arnox
baldyeti wrote: Tue Jul 04, 2023 10:21 am
Arnox wrote: Mon Jul 03, 2023 9:17 am
7B. Wayland is immediately crashing back to the login screen whenever one tries to start a Wayland session. SysVInit, systemd, doesn't matter. Only X11 works.
On plain debian bookworm (where the KDE wayland session seems to work from my limited testing), here are the wayland-related packages i see; are these pre-installed in MX23-beta (KDE) ?
Code: Select all
ii kwayland-data 4:5.103.0-1 all Qt library wrapper for Wayland libraries - data files
ii kwayland-integration:amd64 5.27.5-2 amd64 kwayland runtime integration plugins
ii kwin-wayland 4:5.27.5-3 amd64 KDE window manager, wayland version, PREVIEW release
ii libkf5waylandclient5:amd64 4:5.103.0-1 amd64 Qt library wrapper for Wayland libraries
ii libqt5waylandclient5:amd64 5.15.8-2 amd64 QtWayland client library
ii libqt5waylandcompositor5:amd64 5.15.8-2 amd64 QtWayland compositor library
ii libva-wayland2:amd64 2.17.0-1 amd64 Video Acceleration (VA) API for Linux -- Wayland runtime
ii libwayland-client0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - client library
ii libwayland-cursor0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - cursor library
ii libwayland-egl1:amd64 1.21.0-1 amd64 wayland compositor infrastructure - EGL library
ii libwayland-server0:amd64 1.21.0-1 amd64 wayland compositor infrastructure - server library
ii plasma-workspace-wayland 4:5.27.5-2 amd64 Plasma Workspace for KF5 - Wayland integration
ii qtwayland5:amd64 5.15.8-2 amd64 QtWayland platform plugin
ii wayland-utils 1.1.0-1+b1 amd64 Wayland utilities
ii xwayland 2:22.1.9-1 amd64 X server for running X clients under Wayland
Personally i wouldn't mind if only X11 was pre-loaded in MX23, but then wayland should not even be offered as an option at the login manager level.
Yep, I got everything on that list plus some extras. Even the versions are exact.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 4:45 pm
by baldyeti
Arnox wrote: Tue Jul 04, 2023 4:20 pm
Yep, I got everything on that list plus some extras. Even the versions are exact.
Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 5:47 pm
by Arnox
baldyeti wrote: Tue Jul 04, 2023 4:45 pm
Arnox wrote: Tue Jul 04, 2023 4:20 pm
Yep, I got everything on that list plus some extras. Even the versions are exact.
Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?
Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 6:12 pm
by dolphin_oracle
Arnox wrote: Tue Jul 04, 2023 5:47 pm
baldyeti wrote: Tue Jul 04, 2023 4:45 pm
Arnox wrote: Tue Jul 04, 2023 4:20 pm
Yep, I got everything on that list plus some extras. Even the versions are exact.
Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?
Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?
someone tells me what that is and maybe we can fix that.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 7:52 pm
by Arnox
dolphin_oracle wrote: Tue Jul 04, 2023 6:12 pm
Arnox wrote: Tue Jul 04, 2023 5:47 pm
baldyeti wrote: Tue Jul 04, 2023 4:45 pm
Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?
Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?
someone tells me what that is and maybe we can fix that.
Doing some super quick looking online, it looks like Wayland with Nvidia proprietary drivers may still just be flat out non-functional in general right now. I'm gonna download Debian 12 and install it and see if I get the same issue.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 04, 2023 9:48 pm
by Arnox
dolphin_oracle wrote: Tue Jul 04, 2023 6:12 pm
Arnox wrote: Tue Jul 04, 2023 5:47 pm
baldyeti wrote: Tue Jul 04, 2023 4:45 pm
Was worth checking; I am on oldish gen4 intel HD, perhaps someone on nvidia like you could try a wayland session ?
Ok, I think I've isolated the problem further. Wayland seems to work fine on nouveau (though it was a very quick test) but the proprietary Nvidia drivers make Wayland instantly crash on session start. I wonder if the Nvidia Driver Installer isn't set to properly configure the system for Wayland operation yet maybe?
someone tells me what that is and maybe we can fix that.
UPDATE: Yep, Debian 12 has the exact same behavior. Nvidia drivers are installed along with the appropriate Xorg config generated, then Wayland just refuses to open a session after that.
I did find this:
https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland
In Debian 12 (currently Debian Testing), almost all issues should be resolved and most Wayland sessions should "just work" with the 495-series driver, however some major issues remain with KDE Plasma. These will require merging KDE's Qt 5 patch collection to fix:
https://salsa.debian.org/qt-kde-team/qt ... requests/5
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 3:23 am
by jacklarge
Forgive me if this isn't anything to worry about!
I have been pretty impressed with the Beta as I tried it on a new home-built PC and not only did the PC run without issues but the Beta software also installed and found everything without complaint or the need to edit config files. However I did notice that after a couple of updates apt gave warnings about amdgpu (I am using AMD Ryzen 7 5700G without a dedicated Graphic Card currently). This is a screen shot of the latest one:
https://flic.kr/p/2oMzVcD
As requested here is my Quick System Info:
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK MAX WIFI (MS-7C91) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 2.20 date: 08/30/2022
CPU:
Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80)
stepping: 0 microcode: 0xA50000D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1507 high: 1696 min/max: 1400/4672 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1400 2: 1695 3: 1696 4: 1414 5: 1519 6: 1687
7: 1400 8: 1414 9: 1400 10: 1696 11: 1688 12: 1451 13: 1437 14: 1400 15: 1414 16: 1414
bogomips: 121366
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel
arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: DP-1 empty: DP-2,HDMI-A-1 bus-ID: 30:00.0
chip-ID: 1002:1638 class-ID: 0300 temp: 25.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 mapped: DisplayPort-0 model: Dell U2719DC serial: <filter> built: 2020
res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
6.1.0-9-amd64) direct-render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6
chip-ID: 1022:15e3 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: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel modules: wl pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 29:00.0 chip-ID: 14c3:0608 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 port: f000 bus-ID: 2a:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-9:6
chip-ID: 0e8d:0608 class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 5 state: down bt-service: N/A rfk-block: hardware: no
software: yes address: <filter>
Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
Local Storage: total: 1.82 TiB used: 23.37 GiB (1.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 4B2QEXM7 temp: 28.9 C scheme: MBR
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 5B2QGXA7 temp: 28.9 C scheme: GPT
Partition:
ID-1: / raw-size: 931.25 GiB size: 915.56 GiB (98.31%) used: 23.37 GiB (2.6%) fs: ext4
dev: /dev/nvme1n1p2 maj-min: 259:4
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme1n1p1 maj-min: 259:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 30.6 C mobo: N/A gpu: amdgpu temp: 25.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2152 libs: 1116 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://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
Info:
Processes: 393 Uptime: 3d 7m wakeups: 11 Memory: 58.75 GiB used: 5.87 GiB (10.0%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 4:58 am
by Wallon
Dear Developers,
I can confirm Debian 12 with Gnome and a Nvidia graphics card.
Wayland is not compatible with the proprietary Nvidia driver.
I have 2 USB keys with 2 installations.
a) A Debian 12 Gnome USB key with the « nouveau » driver and Wayland.
b) A Debian 12 Gnome USB key with the proprietary Nvidia driver - X display server, so without Wayland.
In Debian 12, you need to start the session with the X display server and install the proprietary Nvidia driver.
When you restart, Wayland is automatically deleted.
Please note;
1) I don't know if KDE Plasma is still able to work with the X display server. I haven't tested it under Debian 12.
2) Gnome does not work in the same way with the « nouveau » driver as with the proprietary Nvidia driver. For example: when you click on the Gnome dock icon, you no longer have focus on the window that opens with the proprietary Nvidia driver. So there could also be differences for KDE Plasma with the 2 drivers.
My Nvidia GTX960 graphics card is able to decode YouTube VP9.
With the « nouveau » driver, I get a lot of « dropped frames » in YouTube's « Nerd Stats », especially if I move the mouse to my second screen.
The proprietary Nvidia driver makes much better use of my graphics card and I get almost no dropped frames with 60 fps (full HD 1080p).
It's not easy to choose between the 2 drivers. Each has its advantages.
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 6:12 am
by Wallon
Dear Developers,
Localization
Debian 11 and Debian 12 automatically configure the "papersize" file.
In my case, Debian 12 puts "a4" in the file.
MX Linux never localizes this file.
Why doesn't MX Linux do the same as Debian?
This is an important variable for configuring certain software.
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 8:58 am
by Wallon
Dear Developers,
When installing Debian 12, LibreOffice and Firefox are directly localized in the installation language.
Why doesn't MX Linux set the installation language directly for the software?
It would be easier for new users.
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 9:01 am
by hurricane74
- Sorry, I discovered something dumb I was doing right after posting this. Therefore I deleted it. -
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 10:35 am
by Jerry3904
Thanks--not the first time, and not a problem.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 10:38 am
by megaherz33
It turned out to install 23 Beta, recorded the image using MX Live Usb-Maker and no critical error message appeared.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 11:49 am
by siamhie
jacklarge wrote: Wed Jul 05, 2023 3:23 am
Forgive me if this isn't anything to worry about!
I have been pretty impressed with the Beta as I tried it on a new home-built PC and not only did the PC run without issues but the Beta software also installed and found everything without complaint or the need to edit config files. However I did notice that after a couple of updates apt gave warnings about amdgpu (I am using AMD Ryzen 7 5700G without a dedicated Graphic Card currently). This is a screen shot of the latest one:
https://flic.kr/p/2oMzVcD
@jacklarge That's normal. The amdgpu package provides drivers for multiple cards. I get the same message with my 6700XT when initramfs gets updated.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 11:58 am
by Wallon
Dear Developers,
I know that you use MX Linux in English.
@marcelocripe and I would be happy to improve the localization of MX Linux.
I made a comparison of the localization packages installed on Debian 12, Antix 23 Full (fr_BE) and MX Linux 23 (fr_BE).
Some really important packages are missing from MX Linux.
MX Linux could copy these fundamental packages when installing in a language other than English.
Is this complicated to do?
I'm not a Linux specialist, so maybe other fundamental packages are missing.
Best regards,
Wallon
Code: Select all
Debian 12 - packages installed for localization
+++++++++++++++++++++++++++++++++++++++++++++++
debconf-i18n =====> Important
e2fsprogs-l10n =====> Important
featherpad-l10n following soft installed
firefox-esr-l10n-fr following soft installed
gnupg-l10n =====> Important
hunspell-fr =====> Important
hunspell-fr-classical =====> Important
krb5-locales =====> Important
libc-l10n =====> Important
libgphoto2-l10n =====> Important
libosinfo-l10n =====> Important
libreoffice-l10n-fr =====> Important
locales =====> Important
menu-l10n =====> Important
qt6-translations-l10n =====> Important
qttranslations5-l10n =====> Important
tzdata =====> Important
util-linux-locales =====> Important
antiX 23 Full - packages installed for localization
++++++++++++++++++++++++++++++++++++++++++++++++
claws-mail-i18n following soft installed
debconf-i18n =====> Important
e2fsprogs-l10n =====> Important
firefox-esr-l10n-fr following soft installed
gnupg-l10n =====> Important
gnupg1-l10n (obsolete) ? to be or not installed ?
hunspell-fr =====> Important
hunspell-fr-classical =====> Important
libc-l10n =====> Important
libgpg-error-l10n =====> Important
libgphoto2-l10n =====> Important
libparted-i18n =====> Important
libreoffice-l10n-fr =====> Important
locales =====> Important
menu-l10n =====> Important
tzdata =====> Important
MX Linux 23 Xfce - packages installed for localization
++++++++++++++++++++++++++++++++++++++++++++++++++++
debconf-i18n
featherpad-l10n
gnupg-l10n
hunspell-fr
hunspell-fr-classical
krb5-locales
libc-l10n
libreoffice-l10n-fr
locales
nomacs-l10n
qttranslations5-l10n
tzdata
util-linux-locales
vlc-l10n
Missing in MX Linux for good localization;
++++++++++++++++++++++++++++++++++++++++++
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
menu-l10n
qt6-translations-l10n
qttranslations5-l10n
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 11:59 am
by Eadwine Rose
Can we not put this discussion in the beta thread but keep it where it is located right now, the translation forums?
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 12:02 pm
by Arnox
Wallon wrote: Wed Jul 05, 2023 4:58 am
Dear Developers,
I can confirm Debian 12 with Gnome and a Nvidia graphics card.
Wayland is not compatible with the proprietary Nvidia driver.
If that is true, that is incredibly disappointing to hear, and I'm not sure why Nvidia or Debian would allow Wayland solutions to be released and then not be compatible in any way whatsoever with Nvidia hardware. Nouveau is fine for office work, web browsing, and media playing, but anything more intensive than that and you're gonna need the proprietary drivers, period, end of story.
I guess it's not that big a deal at all in the end, but damn it, I'd be lying if I said I wasn't looking forward to finally having a stable Wayland experience on MX/Debian.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 12:34 pm
by Wallon
The « nouveau » driver has made huge progress and works very well with Wayland. I think it’s a good solution for older graphics cards that can no longer get the proprietary Nvidia driver. They are well integrated into the Gnome desktop environment. I was surprised to see that there was no more screen tearing, for example. But « nouveau » doesn’t yet use the full potential of Nvidia graphics cards. Nvidia is still keeping some of its language a secret.
I also think that Nvidia is not developing a proprietary driver compatible with Wayland. It’s not Debian’s fault.
In conclusion, it can’t be easy for MX Linux developers to combine all these KDE, Gnome, « nouveau », Wayland options...
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 1:40 pm
by dolphin_oracle
@Wallon easy enough to add.
Code: Select all
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
menu-l10n
qt6-translations-l10n
qttranslations5-l10n
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 2:12 pm
by jacklarge
siamhie wrote: Wed Jul 05, 2023 11:49 am
@jacklarge That's normal. The amdgpu package provides drivers for multiple cards. I get the same message with my 6700XT when initramfs gets updated.
Thanks for the reassurance Siamhie
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 05, 2023 9:51 pm
by artytux
Curious to see if MX-23 beta would be any problems for this computer, only had time to run a few live sessions of MX-23 b2 and have to congratulate the MX team what wonderful work, honestly tried to find anything that didn't work properly went back in a few time just could not find anything MX have that is broken or just not what it should be,
software tried and worked out well
Geeqie I like it good for comparing before and after Gimp adjustments
Gimp no problems impressive
Quod Libet music player since GmusicBrowser is not on with Debian anymore
FSearch super lightning fast as usual
Artha, Backintime and Timeshift
All work on Ext4 filesystem no encryption no Nvidia
Code: Select all
System: Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-21.3_KDE_x64 Wildflower January 15 2023
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B360-PLUS v: Rev 1.xx serial: <filter>
UEFI-[Legacy]: American Megatrends v: 1101 date: 11/15/2018
CPU: Info: 6-Core model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Kaby Lake
note: check family: 6 model-id: 9E (158) stepping: A (10) microcode: F0 cache:
L2: 12 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 76799
Speed: 3200 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 3200 2: 800 3: 3200 4: 3200
5: 3200 6: 800 7: 3200 8: 3200 9: 800 10: 3200 11: 3200 12: 3200
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
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: IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics: Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915
v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 3280x1080 s-dpi: 96 s-size: 867x285mm (34.1x11.2")
s-diag: 913mm (35.9")
Monitor-1: HDMI-2 res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.9x11.8")
diag: 609mm (24")
Monitor-2: DP-1 res: 1360x768 hz: 60 dpi: 60 size: 575x323mm (22.6x12.7")
diag: 660mm (26")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 22.0.5
direct render: Yes
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348
class-ID: 0403
Device-2: Sony WH-1000XM3 [Wireless Noise-Canceling Headphones] type: USB
driver: hid-generic,usbhid bus-ID: 1-1.4.2.1:12 chip-ID: 054c:0cd3 class-ID: 0300
Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee v: kernel
modules: wl port: 4000 bus-ID: 03:00.0 chip-ID: 10ec:818b class-ID: 0280
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: 3000 bus-ID: 07:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Sony WH-1000XM3 [Wireless Noise-Canceling Headphones] type: USB
driver: hid-generic,usbhid bus-ID: 1-1.4.2.1:12 chip-ID: 054c:0cd3 class-ID: 0300
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb
v: 0.8 bus-ID: 1-1.3.4:8 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: slave accept service-classes: rendering, capturing, object transfer, audio
Drives: Local Storage: total: 8.41 TiB used: 1.57 TiB (18.6%)
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: 6.0 Gb/s type: SSD serial: <filter>
rev: 1B6Q scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Toshiba model: External USB 3.0
size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
rev: 5438 scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital
model: WD Elements SE 2623 size: 1.82 TiB block-size: physical: 512 B logical: 512 B
type: N/A serial: <filter> rev: 1026 scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Western Digital
model: WD My Passport 2627 size: 4.55 TiB block-size: physical: 4096 B logical: 512 B
type: N/A serial: <filter> rev: 4010 scheme: GPT
Partition: ID-1: / raw-size: 87.7 GiB size: 85.77 GiB (97.80%) used: 10.04 GiB (11.7%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 137.18 GiB size: 133.96 GiB (97.66%) used: 4.48 GiB (3.3%)
fs: ext4 dev: /dev/sda3 maj-min: 8:3
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
maj-min: 8:2
Sensors: System Temperatures: cpu: 27.8 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Packages: note: see --pkg apt: 2451 lib: 1348 flatpak: 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 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/mx.list
1: deb http://mx.debian.nz/mx/repo/ bullseye main non-free
2: deb http://mx.debian.nz/mx/repo/ bullseye ahs
Info: Processes: 293 Uptime: 1h 55m wakeups: 1 Memory: 46.91 GiB used: 5.09 GiB (10.8%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A
alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
No problems with MXLinux
KDE is really amazing just be nice if KDE didnot remove the desktop cube bad enough when KDE removed each desktop having a separate wallpaper now the cube is gone,
"Outside the square, Inside the cube"
I guess it doesn't serve any real purpose except maintenance resources that be used in other places But it just so cool to show off with, progress.
Big Thank You
Regards
artytux
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 4:20 am
by Wallon
There's no flag for Belgium in the systray for the gxkb programme.
I know, it's a small country...
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 6:26 am
by fehlix
Wallon wrote: Thu Jul 06, 2023 4:20 am
There's no flag for Belgium in the systray for the gxkb programme.
I know, it's a small country...
Thanks. Would this help?
Code: Select all
sudo ln -s /usr/share/flags-common/be.png /usr/share/gxkb/flags/
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 6:44 am
by OlafD
Proposal:
In KDE Plasma preinstall the font "fonts-noto-color-emoji", then you have colorful emojis with "superkey + ."
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 6:57 am
by Wallon
Thank you
@fehlix
Your command line works very well.
Code: Select all
sudo ln -s /usr/share/flags-common/be.png /usr/share/gxkb/flags/
I rebooted the computer and found the Belgian flag.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 7:02 am
by Wallon
Dear
@dolphin_oracle
Concerns localisation.
I have found 3 new missing files.
compton-conf-l10n
pavucontrol-qt-l10n
rpm-i18n
I have updated the list of missing packages to improve localisation.
Code: Select all
Missing in MX Linux for good localisation;
++++++++++++++++++++++++++++++++++++++++++
compton-conf-l10n (*)
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
menu-l10n
pavucontrol-qt-l10n (*)
qt6-translations-l10n
qttranslations5-l10n
rpm-i18n (*)
Kinds regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 7:45 am
by dolphin_oracle
Wallon wrote: Thu Jul 06, 2023 7:02 am
Dear @dolphin_oracle
Concerns localisation.
I have found 3 new missing files.
compton-conf-l10n
pavucontrol-qt-l10n
rpm-i18n
I have updated the list of missing packages to improve localisation.
Code: Select all
Missing in MX Linux for good localisation;
++++++++++++++++++++++++++++++++++++++++++
compton-conf-l10n (*)
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
menu-l10n
pavucontrol-qt-l10n (*)
qt6-translations-l10n
qttranslations5-l10n
rpm-i18n (*)
Kinds regards,
Wallon
is pavucontrol-qt installed?
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 9:57 am
by Wallon
Dear
@dolphin_oracle
I wasn't paying attention.
The pavucontrol package is installed.
The pavucontrol-qt package is not installed.
Therefore, pavucontrol-qt-l10n should not be installed.
I'm modifying the list of packages.
Kind regards,
Wallon
Code: Select all
Missing in MX Linux 23 for good localization;
++++++++++++++++++++++++++++++++++++++++++
compton-conf-l10n (*)
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
menu-l10n
qt6-translations-l10n
qttranslations5-l10n
rpm-i18n (*)
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:34 am
by davemx
I've tried to read through 47 pages but I might have missed this. I was a bit late as I needed my spare partition to test a script across a few common distros, so I only got to MX23-beta in the last two days.
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?
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:53 am
by Jerry3904
It works here on wireless (MX-21.3, will test on other MX-23 in a minute), it just took a minute or so to get started. EDIT: yup, on MX-23b2 also.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 11:01 am
by Jerry3904
The graph uses black for the actual data and that is hard to see against a dark background such as the default one.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 11:48 am
by siamhie
Jerry3904 wrote: Thu Jul 06, 2023 11:01 am
The graph uses black for the actual data and that is hard to see against a dark background such as the default one.
@Jerry3904 You can set the transparency level to make it easier to see. Open Conky Manager > Edit Widget > Transparency.
Set Transparency Type to Semi-Transparent and any value besides 100 for Opacity. (compton must be running)
transparent.jpg
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 12:16 pm
by davemx
I had re-written the Geeky-Tower conky file, so I tried two other things - 1. I created a temporary new user and copied over from there, the bit that did the Ethernet speed, to no avail. Then I logged in as the new user, and changed conky to the Geeky-Tower, displaying a totally unamended version, as provided with MX Linux, and still no graphical confirmation of download and upload speeds. I don't know why Jerry's computer should behave differently to mine!
In the temporary new user area, I also tried switching off my wired internet and connecting via a wireless dongle, and it made no difference. Textual confirmation of the wireless speed but no graphic.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 1:19 pm
by Jerry3904
siamhie wrote: Thu Jul 06, 2023 11:48 am
Jerry3904 wrote: Thu Jul 06, 2023 11:01 am
The graph uses black for the actual data and that is hard to see against a dark background such as the default one.
@Jerry3904 You can set the transparency level to make it easier to see. Open Conky Manager > Edit Widget > Transparency.
Set Transparency Type to Semi-Transparent and any value besides 100 for Opacity. (compton must be running)
transparent.jpg
I know. Was trying to help the problem poster figure out how to diagnose and solve.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 2:53 pm
by FullScale4Me
Problem installing Liquorix 64 bit Kernel from MX Package Installer Popular Applications Kernels section.
This stands out: "E: Internal Error, No file name for linux-headers-6.3.9-1-liquorix-amd64:amd64"
It ends with: "Problem detected while installing, please inspect the console output." Copied below.
Code: Select all
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease
Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Reading package lists...
W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease
Get:5 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Packages [63.1 kB]
Get:6 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Packages [70.3 kB]
Get:7 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Contents (deb) [1,106 kB]
Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Get:8 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Contents (deb) [481 kB]
Fetched 1,720 kB in 1s (1,511 kB/s)
Reading package lists...
W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 19 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for linux-headers-6.3.9-1-liquorix-amd64:amd64
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease
Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Reading package lists...
W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
MXPI.LOG
Code: Select all
2023-07-06 14:39:27.847 DBG default: mx-packageinstaller version: 23.6
2023-07-06 14:39:27.889 WRN default: QMetaObject::connectSlotsByName: Connecting slot on_comboRemote_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
2023-07-06 14:39:27.890 DBG default: +++ void MainWindow::setProgressDialog() +++
2023-07-06 14:39:27.890 DBG default: +++ void MainWindow::setup() +++
2023-07-06 14:39:27.892 DBG default: dpkg-query -f '${Version}' -W flatpak
2023-07-06 14:39:27.916 DBG default: "1.14.4-1"
2023-07-06 14:39:27.917 DBG default: apt-get update --print-uris | grep -m1 -qE '/mx/testrepo/dists/bookworm/test/'
2023-07-06 14:39:27.973 DBG default: +++ void MainWindow::loadPmFiles() +++
2023-07-06 14:39:28.092 DBG default: +++ void MainWindow::refreshPopularApps() +++
2023-07-06 14:39:28.092 DBG default: +++ QStringList MainWindow::listInstalled() +++
2023-07-06 14:39:28.092 DBG default: dpkg --get-selections | grep -v deinstall | cut -f1
2023-07-06 14:39:28.119 DBG default: +++ void MainWindow::displayPopularApps() const +++
2023-07-06 14:39:42.354 DBG default: +++ void MainWindow::on_pushInstall_clicked() +++
2023-07-06 14:39:42.356 DBG default: +++ void MainWindow::on_tabWidget_currentChanged(int) +++
2023-07-06 14:39:42.356 DBG default: +++ bool MainWindow::installPopularApps() +++
2023-07-06 14:39:42.733 DBG default: +++ bool MainWindow::updateApt() +++
2023-07-06 14:39:42.734 DBG default: apt-get update -o=Dpkg::Use-Pty=0 -o Acquire::http:Timeout=10 -o Acquire::https:Timeout=10 -o Acquire::ftp:Timeout=10
2023-07-06 14:39:42.879 DBG default: "Hit:1 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:39:42.882 DBG default: "Hit:2 http://deb.debian.org/debian bookworm InRelease\nHit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:39:43.594 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:39:44.112 DBG default: "Reading package lists..."
2023-07-06 14:39:45.077 DBG default: ""
2023-07-06 14:39:45.089 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:39:45.090 DBG default: sources updated OK
2023-07-06 14:39:45.090 DBG default: +++ bool MainWindow::installBatch(const QStringList&) +++
2023-07-06 14:39:45.090 DBG default: Post-install
2023-07-06 14:39:45.091 DBG default:
2023-07-06 14:39:45.098 DBG default: +++ bool MainWindow::installPopularApp(const QString&) +++
2023-07-06 14:39:45.098 DBG default: Pre-install
2023-07-06 14:39:45.098 DBG default: [ $(apt-get update --print-uris | grep -c -m1 -E "/mx/repo/dists/bookworm/ahs/") = 0 ] || exit 0
MXREPO=$(apt-get update --print-uris | grep -m1 -oE "https?://.*/mx/repo/dists/bookworm/main" | tail -1 | sed "s:^:deb :; s:/repo/dists/:/repo/ :; s:/main: ahs:")
: ${MXREPO:=deb http://mxrepo.com/mx/repo/ bookworm ahs}
echo "$MXREPO" > /etc/apt/sources.list.d/mxpitemp.list
apt-get update
2023-07-06 14:39:45.277 DBG default: "Hit:1 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:39:45.279 DBG default: "Hit:2 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:39:45.286 DBG default: "Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:39:45.843 DBG default: "Get:5 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Packages [63.1 kB]"
2023-07-06 14:39:45.931 DBG default: "Get:6 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Packages [70.3 kB]"
2023-07-06 14:39:45.939 DBG default: "Get:7 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Contents (deb) [1,106 kB]"
2023-07-06 14:39:46.022 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:39:46.129 DBG default: "Get:8 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Contents (deb) [481 kB]"
2023-07-06 14:39:50.924 DBG default: "Fetched 1,720 kB in 1s (1,511 kB/s)\nReading package lists..."
2023-07-06 14:39:51.847 DBG default: ""
2023-07-06 14:39:51.861 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:39:51.862 DBG default: +++ bool MainWindow::install(const QString&) +++
2023-07-06 14:39:52.161 DBG default: +++ bool MainWindow::confirmActions(const QString&, const QString&) +++
2023-07-06 14:39:52.161 DBG default: names "linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64" and ()
2023-07-06 14:39:52.161 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) LANG=C apt-get -s -V -o=Dpkg::Use-Pty=0 install --reinstall linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64|grep 'Inst\|Remv'| awk '{V=""; P="";}; $3 ~ /^\[/ { V=$3 }; $3 ~ /^\(/ { P=$3 ")"}; $4 ~ /^\(/ {P=" => " $4 ")"}; {print $2 ";" V P ";" $1}'
2023-07-06 14:39:53.191 DBG default: "linux-headers-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst\nlinux-image-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst"
2023-07-06 14:39:53.192 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) LANG=C aptitude -sy -V -o=Dpkg::Use-Pty=0 install --without-recommends linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64 |tail -2 |head -1
2023-07-06 14:39:54.021 DBG default: "Need to get 0 B of archives. After unpacking 0 B will be used."
2023-07-06 14:39:54.021 DBG default: detailed installed names sorted ("linux-headers-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst", "linux-image-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst")
2023-07-06 14:40:02.416 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) apt-get -o=Dpkg::Use-Pty=0 install -y --reinstall linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64
2023-07-06 14:40:02.459 DBG default: "Reading package lists..."
2023-07-06 14:40:02.470 DBG default: ""
2023-07-06 14:40:02.473 DBG default: "Building dependency tree..."
2023-07-06 14:40:02.658 DBG default: "Reading state information..."
2023-07-06 14:40:02.659 DBG default: ""
2023-07-06 14:40:03.064 DBG default: "0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 19 not upgraded.\n2 not fully installed or removed.\nAfter this operation, 0 B of additional disk space will be used."
2023-07-06 14:40:03.065 WRN default: "E: Internal Error, No file name for linux-headers-6.3.9-1-liquorix-amd64:amd64"
2023-07-06 14:40:03.072 DBG default: Post-install
2023-07-06 14:40:03.073 DBG default: rebuild_dkms_packages.sh linux-image-6.3.9-1-liquorix-amd64
rm -f /etc/apt/sources.list.d/mxpitemp.list
apt-get update
2023-07-06 14:40:03.193 DBG default: "Hit:1 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:40:03.197 DBG default: "Hit:2 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:40:03.227 DBG default: "Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:40:03.928 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:40:08.576 DBG default: "Reading package lists..."
2023-07-06 14:40:09.477 DBG default: ""
2023-07-06 14:40:09.489 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:40:09.494 DBG default: +++ void MainWindow::refreshPopularApps() +++
2023-07-06 14:40:09.494 DBG default: +++ QStringList MainWindow::listInstalled() +++
2023-07-06 14:40:09.494 DBG default: dpkg --get-selections | grep -v deinstall | cut -f1
2023-07-06 14:40:09.522 DBG default: +++ void MainWindow::displayPopularApps() const +++
2023-07-06 14:45:04.851 DBG default: +++ void MainWindow::on_tabWidget_currentChanged(int) +++
2023-07-06 14:45:04.852 DBG default: +++ void MainWindow::setCurrentTree() +++
2023-07-06 14:45:04.852 DBG default: +++ void MainWindow::updateInterface() +++
2023-07-06 14:46:40.870 DBG default: +++ void MainWindow::on_tabWidget_currentChanged(int) +++
2023-07-06 14:48:19.697 DBG default: +++ void MainWindow::on_tabWidget_currentChanged(int) +++
2023-07-06 14:48:19.698 DBG default: +++ void MainWindow::setCurrentTree() +++
2023-07-06 14:48:19.698 DBG default: +++ void MainWindow::updateInterface() +++
2023-07-06 14:48:27.140 DBG default: +++ void MainWindow::on_pushInstall_clicked() +++
2023-07-06 14:48:27.141 DBG default: +++ void MainWindow::on_tabWidget_currentChanged(int) +++
2023-07-06 14:48:27.142 DBG default: +++ bool MainWindow::installPopularApps() +++
2023-07-06 14:48:27.563 DBG default: +++ bool MainWindow::installBatch(const QStringList&) +++
2023-07-06 14:48:27.563 DBG default: Post-install
2023-07-06 14:48:27.564 DBG default:
2023-07-06 14:48:27.580 DBG default: +++ bool MainWindow::installPopularApp(const QString&) +++
2023-07-06 14:48:27.580 DBG default: Pre-install
2023-07-06 14:48:27.580 DBG default: [ $(apt-get update --print-uris | grep -c -m1 -E "/mx/repo/dists/bookworm/ahs/") = 0 ] || exit 0
MXREPO=$(apt-get update --print-uris | grep -m1 -oE "https?://.*/mx/repo/dists/bookworm/main" | tail -1 | sed "s:^:deb :; s:/repo/dists/:/repo/ :; s:/main: ahs:")
: ${MXREPO:=deb http://mxrepo.com/mx/repo/ bookworm ahs}
echo "$MXREPO" > /etc/apt/sources.list.d/mxpitemp.list
apt-get update
2023-07-06 14:48:27.762 DBG default: "Hit:1 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:48:27.766 DBG default: "Hit:2 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:48:27.813 DBG default: "Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:48:28.234 DBG default: "Get:5 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Packages [63.1 kB]"
2023-07-06 14:48:28.327 DBG default: "Get:6 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Packages [70.3 kB]"
2023-07-06 14:48:28.351 DBG default: "Get:7 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Contents (deb) [481 kB]"
2023-07-06 14:48:28.413 DBG default: "Get:8 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Contents (deb) [1,106 kB]"
2023-07-06 14:48:28.560 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:48:33.382 DBG default: "Fetched 1,720 kB in 1s (1,708 kB/s)\nReading package lists..."
2023-07-06 14:48:34.271 DBG default: ""
2023-07-06 14:48:34.285 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:48:34.286 DBG default: +++ bool MainWindow::install(const QString&) +++
2023-07-06 14:48:34.621 DBG default: +++ bool MainWindow::confirmActions(const QString&, const QString&) +++
2023-07-06 14:48:34.621 DBG default: names "linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64" and ()
2023-07-06 14:48:34.621 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) LANG=C apt-get -s -V -o=Dpkg::Use-Pty=0 install --reinstall linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64|grep 'Inst\|Remv'| awk '{V=""; P="";}; $3 ~ /^\[/ { V=$3 }; $3 ~ /^\(/ { P=$3 ")"}; $4 ~ /^\(/ {P=" => " $4 ")"}; {print $2 ";" V P ";" $1}'
2023-07-06 14:48:35.671 DBG default: "linux-headers-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst\nlinux-image-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst"
2023-07-06 14:48:35.672 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) LANG=C aptitude -sy -V -o=Dpkg::Use-Pty=0 install --without-recommends linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64 |tail -2 |head -1
2023-07-06 14:48:36.455 DBG default: "Need to get 0 B of archives. After unpacking 0 B will be used."
2023-07-06 14:48:36.455 DBG default: detailed installed names sorted ("linux-headers-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst", "linux-image-6.3.9-1-liquorix-amd64;[6.3-9~mx23+1] => (6.3-9~mx23+1);Inst")
2023-07-06 14:48:38.516 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) apt-get -o=Dpkg::Use-Pty=0 install -y --reinstall linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64
2023-07-06 14:48:38.591 DBG default: "Reading package lists..."
2023-07-06 14:48:38.602 DBG default: ""
2023-07-06 14:48:38.605 DBG default: "Building dependency tree..."
2023-07-06 14:48:38.793 DBG default: "Reading state information..."
2023-07-06 14:48:38.795 DBG default: ""
2023-07-06 14:48:39.223 DBG default: "0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 19 not upgraded.\n2 not fully installed or removed.\nAfter this operation, 0 B of additional disk space will be used."
2023-07-06 14:48:39.223 WRN default: "E: Internal Error, No file name for linux-headers-6.3.9-1-liquorix-amd64:amd64"
2023-07-06 14:48:39.224 DBG default: Post-install
2023-07-06 14:48:39.225 DBG default: rebuild_dkms_packages.sh linux-image-6.3.9-1-liquorix-amd64
rm -f /etc/apt/sources.list.d/mxpitemp.list
apt-get update
2023-07-06 14:48:39.426 DBG default: "Hit:1 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:48:39.465 DBG default: "Hit:2 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:48:39.474 DBG default: "Hit:3 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:48:40.126 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:48:45.125 DBG default: "Reading package lists..."
2023-07-06 14:48:46.038 DBG default: ""
2023-07-06 14:48:46.051 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:48:46.060 DBG default: +++ void MainWindow::refreshPopularApps() +++
2023-07-06 14:48:46.061 DBG default: +++ QStringList MainWindow::listInstalled() +++
2023-07-06 14:48:46.061 DBG default: dpkg --get-selections | grep -v deinstall | cut -f1
2023-07-06 14:48:46.090 DBG default: +++ void MainWindow::displayPopularApps() const +++
QSI
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_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop System: Dell product: OptiPlex 7050 v: N/A serial: <superuser required> Chassis:
type: 3 serial: <superuser required>
Mobo: Dell model: 0NW6H5 v: A00 serial: <superuser required> UEFI: Dell v: 1.21.0
date: 07/12/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse B330/M330/M331 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Core i7-7700 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0xF2
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 1200 min/max: 800/4200 scaling: driver: intel_pstate governor: powersave
cores: 1: 1200 2: 1200 3: 1200 4: 1200 5: 1200 6: 1200 7: 1200 8: 1200 bogomips: 57600
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, HDMI-A-2,
HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:5912 class-ID: 0300
Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-4:4
chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Acer K242HYL serial: <filter> built: 2019
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.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 630 (KBL GT2)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Dell driver: snd_hda_intel v: kernel
bus-ID: 1-4:4 chip-ID: 046d:0825 bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0102 class-ID: 0403
serial: <filter>
Device-2: Logitech Webcam C270 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: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
chip-ID: 8086:15e3 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1012.46 GiB used: 181.68 GiB (17.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingfast model: N/A size: 953.87 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 9B0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB model: Specific STORAGE DEVICE size: 58.59 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 0009 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 355.47 GiB size: 348.82 GiB (98.13%) used: 181.64 GiB (52.1%) fs: ext4
dev: /dev/sda6 maj-min: 8:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 44.1 MiB (45.9%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 37.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 2646 pm: dpkg pkgs: 2640 libs: 1477 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 6
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
No active apt repos in: /etc/apt/sources.list.d/mike.list
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
Active apt repos in: /etc/apt/sources.list.d/slack.list
1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
Info:
Processes: 237 Uptime: 7m wakeups: 4 Memory: 31.21 GiB used: 2.2 GiB (7.0%) 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: UEFI
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 3:26 pm
by siamhie
Sorry
@Jerry3904. Didn't realize you were responding to davemx.
@davemx geekytowerLogo works for me also. I made two small changes to see the results better. (changed the update interval from 5 seconds to 1 second and the color white (000000) to green (19db69))
conky.config section
Code: Select all
-- Update interval in seconds
update_interval = 1,
conky.text section (template6 = 'wlan0')
Code: Select all
${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 19db69 19db69} $alignr${upspeedgraph ${template6} 30,120 19db69 19db69}${else}
geeky.png
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 3:38 pm
by Jerry3904
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 3:43 pm
by ceeslans
davemx wrote: Thu Jul 06, 2023 12:16 pm
I had re-written the Geeky-Tower conky file, so I tried two other things - 1. I created a temporary new user and copied over from there, the bit that did the Ethernet speed, to no avail. Then I logged in as the new user, and changed conky to the Geeky-Tower, displaying a totally unamended version, as provided with MX Linux, and still no graphical confirmation of download and upload speeds. I don't know why Jerry's computer should behave differently to mine!
In the temporary new user area, I also tried switching off my wired internet and connecting via a wireless dongle, and it made no difference. Textual confirmation of the wireless speed but no graphic.
In order to see the up-/down speedgraphs you could set two colors.
in below screen capture I used '000000' (black) and 'ffffff' (white) --> which creates the graph fading from white to dark-grey, You can of course play with any other color combo that you like.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 4:10 pm
by hurricane74
In KDE the title bar colors quit changing unless I logout or restart. This was working fine for the past week that I have been testing beta 2 and only started giving trouble today.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 4:57 pm
by Jerry3904
ceeslans wrote: Thu Jul 06, 2023 3:43 pm
davemx wrote: Thu Jul 06, 2023 12:16 pm
I had re-written the Geeky-Tower conky file, so I tried two other things - 1. I created a temporary new user and copied over from there, the bit that did the Ethernet speed, to no avail. Then I logged in as the new user, and changed conky to the Geeky-Tower, displaying a totally unamended version, as provided with MX Linux, and still no graphical confirmation of download and upload speeds. I don't know why Jerry's computer should behave differently to mine!
In the temporary new user area, I also tried switching off my wired internet and connecting via a wireless dongle, and it made no difference. Textual confirmation of the wireless speed but no graphic.
In order to see the up-/down speedgraphs you could set two colors.
in below screen capture I used '000000' (black) and 'ffffff' (white) --> which creates the graph fading from white to dark-grey, You can of course play with any other color combo that you like.
Hey, people: please stop posting here on this topic. It has nothing to do with this very long thread.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 6:30 pm
by siamhie
Jerry3904 wrote: Thu Jul 06, 2023 3:38 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:07 pm
by i_ri
hello dolphin_oracle
big mistakke
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:14 pm
by fehlix
FullScale4Me wrote: Thu Jul 06, 2023 2:53 pm
Problem installing Liquorix 64 bit Kernel from MX Package Installer Popular Applications Kernels section.
This stands out: "E: Internal Error, No file name for linux-headers-6.3.9-1-liquorix-amd64:amd64"
It ends with: "Problem detected while installing, please inspect the console output." Copied below.
The posted log indicates a failed reinstallation attempt of the liquorix linux kernel.
The error message seems not really helpful to figure out the cause of the issue.
But the reason might be this:
During installation a dkms-rebuild of some modules failed. In this case
the module rtl8821cu seems to be the show stopper.
Which is also clearly indicated with the package description of rtl8821cu-dkms:
Code: Select all
apt show rtl8821cu-dkms
...
Description: rtl8821cu driver in DKMS format, builds up to 5.17 kernels.
So to fix the installation would be to purge the show stopper:
OK, this removing of the conflicting package could be considered to be added to the MXPI entry within Populare Apps itself to avoid the installation hanger. Maybe someone could adjust this entry in MXPI at least as long as this package is conflicting
@dolphin_oracle
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:19 pm
by dolphin_oracle
rtl882cu-dkms package has a directive in it to skip building on the kernels after 6.1. I have both rtl8821cu-dkms and the 6.3 liquorix kernel installed.
I don't want to remove a driver that may be in use. the part is supported in the 6.3 kernels I believe. but will play with it some more.
but this doesn't cause the error the user reports. the installation should complete, but with a problem report due to the skipped driver build. but its actually fully installed, just exits with a non-zero exit code.
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:34 pm
by entropyfoe
My MX 23 beta2 is up 20 day now, so far so good.
I noticed firefox was using LOTs of RAM. I have 32G, and 27 was used, when I shut off most applications except firefox, as usual, some "isolated web content" , tabs using lots of memory and lots of CPU, usual firefox memory leaks and stuff. Though as an experiment on this beta install,I did not install no-script into fire fox as an experiment- I usually do. I think it limits some of these excess memory used in some tabs.
So after I killed firefox, and restarted it, restoring the session, looked and noticed many of my processes, as seen in top, the pid were over 1.3 million ! I never noticed this before, and I guess, things are running well, but those do seem bigger than what I usually see. These "big pids" can be from user or root. [It makes it harder to remember a pid to type a kill command]
Code: Select all
GiB Mem : 31.3 total, 17.8 free, 10.5 used, 3.7 buff/cache
GiB Swap: 32.2 total, 32.2 free, 0.0 used. 20.8 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1319969 music 20 0 5256188 2.4g 117712 R 48.5 7.8 34:06.65 Isolated Web Co
2301 root 20 0 6744636 221292 59120 S 9.3 0.7 18,04 Xorg
1313678 music 20 0 12.9g 1.1g 244852 S 9.0 3.5 25:52.48 firefox-bin
1315681 music 20 0 10.7g 172000 86560 S 7.0 0.5 4:39.48 Isolated Web Co
3467 music 20 0 897196 58700 38292 S 4.7 0.2 41:50.98 xfce4-terminal
1087698 music 20 0 3715568 268860 89592 S 3.0 0.8 36:01.42 strawberry
2375 root -51 0 0 0 0 S 2.3 0.0 82:31.52 irq/111-nvidia
1314390 music 20 0 3077448 316896 107384 S 2.3 1.0 7:53.83 Isolated Web Co
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 10:44 pm
by FullScale4Me
fehlix wrote: Thu Jul 06, 2023 10:14 pm
FullScale4Me wrote: Thu Jul 06, 2023 2:53 pm
Problem installing Liquorix 64 bit Kernel from MX Package Installer Popular Applications Kernels section.
This stands out: "E: Internal Error, No file name for linux-headers-6.3.9-1-liquorix-amd64:amd64"
It ends with: "Problem detected while installing, please inspect the console output." Copied below.
The posted log indicates a failed reinstallation attempt of the liquorix linux kernel.
The error message seems not really helpful to figure out the cause of the issue.
@dolphin_oracle
I went back and grabed the log of the initial attempt to install that kernel.
Code: Select all
mxpi.log.old
-----------------------------------------------------------
MXPI SESSION
-----------------------------------------------------------
2023-07-06 14:27:22.804 DBG default: mx-packageinstaller version: 23.6
2023-07-06 14:27:22.823 WRN default: QMetaObject::connectSlotsByName: Connecting slot on_comboRemote_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
2023-07-06 14:27:22.823 DBG default: +++ void MainWindow::setProgressDialog() +++
2023-07-06 14:27:22.824 DBG default: +++ void MainWindow::setup() +++
2023-07-06 14:27:22.826 DBG default: dpkg-query -f '${Version}' -W flatpak
2023-07-06 14:27:22.846 DBG default: "1.14.4-1"
2023-07-06 14:27:22.847 DBG default: apt-get update --print-uris | grep -m1 -qE '/mx/testrepo/dists/bookworm/test/'
2023-07-06 14:27:22.894 DBG default: +++ void MainWindow::loadPmFiles() +++
2023-07-06 14:27:22.936 DBG default: +++ void MainWindow::refreshPopularApps() +++
2023-07-06 14:27:22.936 DBG default: +++ QStringList MainWindow::listInstalled() +++
2023-07-06 14:27:22.936 DBG default: dpkg --get-selections | grep -v deinstall | cut -f1
2023-07-06 14:27:22.962 DBG default: +++ void MainWindow::displayPopularApps() const +++
2023-07-06 14:27:59.101 DBG default: +++ void MainWindow::on_pushInstall_clicked() +++
2023-07-06 14:27:59.103 DBG default: +++ void MainWindow::on_tabWidget_currentChanged(int) +++
2023-07-06 14:27:59.104 DBG default: +++ bool MainWindow::installPopularApps() +++
2023-07-06 14:27:59.488 DBG default: +++ bool MainWindow::updateApt() +++
2023-07-06 14:27:59.489 DBG default: apt-get update -o=Dpkg::Use-Pty=0 -o Acquire::http:Timeout=10 -o Acquire::https:Timeout=10 -o Acquire::ftp:Timeout=10
2023-07-06 14:27:59.609 DBG default: "Get:1 http://deb.debian.org/debian bookworm-updates InRelease [52.1 kB]"
2023-07-06 14:27:59.643 DBG default: "Hit:2 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:27:59.662 DBG default: "Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:28:00.369 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:28:00.756 DBG default: "Fetched 52.1 kB in 1s (48.2 kB/s)\nReading package lists..."
2023-07-06 14:28:01.637 DBG default: ""
2023-07-06 14:28:01.648 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:28:01.649 DBG default: sources updated OK
2023-07-06 14:28:01.649 DBG default: +++ bool MainWindow::installBatch(const QStringList&) +++
2023-07-06 14:28:01.649 DBG default: Post-install
2023-07-06 14:28:01.649 DBG default:
2023-07-06 14:28:01.656 DBG default: +++ bool MainWindow::installPopularApp(const QString&) +++
2023-07-06 14:28:01.656 DBG default: Pre-install
2023-07-06 14:28:01.657 DBG default: [ $(apt-get update --print-uris | grep -c -m1 -E "/mx/repo/dists/bookworm/ahs/") = 0 ] || exit 0
MXREPO=$(apt-get update --print-uris | grep -m1 -oE "https?://.*/mx/repo/dists/bookworm/main" | tail -1 | sed "s:^:deb :; s:/repo/dists/:/repo/ :; s:/main: ahs:")
: ${MXREPO:=deb http://mxrepo.com/mx/repo/ bookworm ahs}
echo "$MXREPO" > /etc/apt/sources.list.d/mxpitemp.list
apt-get update
2023-07-06 14:28:01.825 DBG default: "Hit:1 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:28:01.831 DBG default: "Hit:2 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:28:01.852 DBG default: "Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:28:02.446 DBG default: "Get:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Packages [70.3 kB]"
2023-07-06 14:28:02.573 DBG default: "Get:5 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Packages [63.1 kB]"
2023-07-06 14:28:02.594 DBG default: "Get:6 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs i386 Contents (deb) [481 kB]"
2023-07-06 14:28:02.653 DBG default: "Get:7 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 Contents (deb) [1,106 kB]"
2023-07-06 14:28:03.101 DBG default: "Hit:8 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:28:09.865 DBG default: "Fetched 1,720 kB in 2s (1,108 kB/s)\nReading package lists..."
2023-07-06 14:28:10.740 DBG default: ""
2023-07-06 14:28:10.754 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:28:10.760 DBG default: +++ bool MainWindow::install(const QString&) +++
2023-07-06 14:28:11.065 DBG default: +++ bool MainWindow::confirmActions(const QString&, const QString&) +++
2023-07-06 14:28:11.066 DBG default: names "linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64" and ()
2023-07-06 14:28:11.066 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) LANG=C apt-get -s -V -o=Dpkg::Use-Pty=0 install --reinstall linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64|grep 'Inst\|Remv'| awk '{V=""; P="";}; $3 ~ /^\[/ { V=$3 }; $3 ~ /^\(/ { P=$3 ")"}; $4 ~ /^\(/ {P=" => " $4 ")"}; {print $2 ";" V P ";" $1}'
2023-07-06 14:28:12.130 DBG default: "irqbalance;(1.9.2-1);Inst\nlibbabeltrace1;(1.5.11-1+b2);Inst\nlinux-headers-6.3.9-1-liquorix-amd64;(6.3-9~mx23+1);Inst\nlinux-image-6.3.9-1-liquorix-amd64;(6.3-9~mx23+1);Inst"
2023-07-06 14:28:12.130 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) LANG=C aptitude -sy -V -o=Dpkg::Use-Pty=0 install --without-recommends linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64 |tail -2 |head -1
2023-07-06 14:28:12.946 DBG default: "Need to get 121 MB of archives. After unpacking 216 MB will be used."
2023-07-06 14:28:12.947 DBG default: detailed installed names sorted ("irqbalance;(1.9.2-1);Inst", "libbabeltrace1;(1.5.11-1+b2);Inst", "linux-headers-6.3.9-1-liquorix-amd64;(6.3-9~mx23+1);Inst", "linux-image-6.3.9-1-liquorix-amd64;(6.3-9~mx23+1);Inst")
2023-07-06 14:28:39.617 DBG default: DEBIAN_FRONTEND=$(dpkg -l debconf-kde-helper 2>/dev/null | grep -sq ^i && echo kde || echo gnome) apt-get -o=Dpkg::Use-Pty=0 install -y --reinstall linux-image-6.3.9-1-liquorix-amd64 linux-headers-6.3.9-1-liquorix-amd64
2023-07-06 14:28:39.658 DBG default: "Reading package lists..."
2023-07-06 14:28:39.670 DBG default: ""
2023-07-06 14:28:39.674 DBG default: "Building dependency tree..."
2023-07-06 14:28:39.855 DBG default: "Reading state information..."
2023-07-06 14:28:39.858 DBG default: ""
2023-07-06 14:28:40.047 DBG default: "The following additional packages will be installed:"
2023-07-06 14:28:40.051 DBG default: "irqbalance libbabeltrace1"
2023-07-06 14:28:40.054 DBG default: "Suggested packages:\n linux-doc-6.3 crda"
2023-07-06 14:28:40.073 DBG default: "The following NEW packages will be installed:"
2023-07-06 14:28:40.076 DBG default: "irqbalance libbabeltrace1 linux-headers-6.3.9-1-liquorix-amd64\n linux-image-6.3.9-1-liquorix-amd64"
2023-07-06 14:28:40.154 DBG default: "0 upgraded, 4 newly installed, 0 to remove and 19 not upgraded.\nNeed to get 121 MB of archives.\nAfter this operation, 216 MB of additional disk space will be used.\nGet:1 http://deb.debian.org/debian bookworm/main amd64 irqbalance amd64 1.9.2-1 [48.9 kB]"
2023-07-06 14:28:40.187 DBG default: "Get:2 http://deb.debian.org/debian bookworm/main amd64 libbabeltrace1 amd64 1.5.11-1+b2 [172 kB]"
2023-07-06 14:28:40.278 DBG default: "Get:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 linux-headers-6.3.9-1-liquorix-amd64 amd64 6.3-9~mx23+1 [12.9 MB]"
2023-07-06 14:28:41.977 DBG default: "Get:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm/ahs amd64 linux-image-6.3.9-1-liquorix-amd64 amd64 6.3-9~mx23+1 [108 MB]"
2023-07-06 14:28:57.702 DBG default: "Fetched 121 MB in 17s (7,174 kB/s)"
2023-07-06 14:28:57.744 DBG default: "Selecting previously unselected package irqbalance."
2023-07-06 14:28:57.859 DBG default: "(Reading database ... 317479 files and directories currently installed.)"
2023-07-06 14:28:57.871 DBG default: "Preparing to unpack .../irqbalance_1.9.2-1_amd64.deb ..."
2023-07-06 14:28:57.878 DBG default: "Unpacking irqbalance (1.9.2-1) ..."
2023-07-06 14:28:57.922 DBG default: "Selecting previously unselected package libbabeltrace1:amd64."
2023-07-06 14:28:57.968 DBG default: "Preparing to unpack .../libbabeltrace1_1.5.11-1+b2_amd64.deb ..."
2023-07-06 14:28:57.972 DBG default: "Unpacking libbabeltrace1:amd64 (1.5.11-1+b2) ..."
2023-07-06 14:28:58.041 DBG default: "Selecting previously unselected package linux-headers-6.3.9-1-liquorix-amd64."
2023-07-06 14:28:58.069 DBG default: "Preparing to unpack .../linux-headers-6.3.9-1-liquorix-amd64_6.3-9~mx23+1_amd64.deb ..."
2023-07-06 14:28:58.072 DBG default: "Unpacking linux-headers-6.3.9-1-liquorix-amd64 (6.3-9~mx23+1) ..."
2023-07-06 14:29:01.030 DBG default: "Selecting previously unselected package linux-image-6.3.9-1-liquorix-amd64."
2023-07-06 14:29:01.087 DBG default: "Preparing to unpack .../linux-image-6.3.9-1-liquorix-amd64_6.3-9~mx23+1_amd64.deb ..."
2023-07-06 14:29:01.097 DBG default: "Unpacking linux-image-6.3.9-1-liquorix-amd64 (6.3-9~mx23+1) ..."
2023-07-06 14:29:03.363 DBG default: "Setting up irqbalance (1.9.2-1) ..."
2023-07-06 14:29:03.447 DBG default: "Starting SMP IRQ Balancer: irqbalance"
2023-07-06 14:29:03.451 DBG default: "."
2023-07-06 14:29:03.549 WRN default: "Created symlink /etc/systemd/system/multi-user.target.wants/irqbalance.service → /lib/systemd/system/irqbalance.service."
2023-07-06 14:29:03.555 DBG default: "Setting up linux-image-6.3.9-1-liquorix-amd64 (6.3-9~mx23+1) ..."
2023-07-06 14:29:09.767 DBG default: "I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-9-amd64\nI: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-9-amd64\nI: /vmlinuz is now a symlink to boot/vmlinuz-6.3.9-1-liquorix-amd64\nI: /initrd.img is now a symlink to boot/initrd.img-6.3.9-1-liquorix-amd64"
2023-07-06 14:29:09.774 DBG default: "/etc/kernel/postinst.d/dkms:\ndkms: running auto installation service for kernel 6.3.9-1-liquorix-amd64."
2023-07-06 14:29:10.002 WRN default: "Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)"
2023-07-06 14:29:10.099 WRN default: "Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)"
2023-07-06 14:29:10.215 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:29:10.571 DBG default: "Building module:"
2023-07-06 14:29:10.577 DBG default: "Cleaning build area..."
2023-07-06 14:29:10.656 DBG default: ""
2023-07-06 14:29:10.663 DBG default: "./dkms-make.sh..."
2023-07-06 14:29:13.663 DBG default: "."
2023-07-06 14:29:16.666 DBG default: "."
2023-07-06 14:29:19.687 DBG default: "."
2023-07-06 14:29:22.703 DBG default: "."
2023-07-06 14:29:25.705 DBG default: "."
2023-07-06 14:29:28.711 DBG default: "."
2023-07-06 14:29:31.723 DBG default: "."
2023-07-06 14:29:33.500 DBG default: ""
2023-07-06 14:29:35.139 DBG default: "Cleaning build area..."
2023-07-06 14:29:35.190 DBG default: ""
2023-07-06 14:29:35.213 DBG default: "8812au.ko.xz:\nRunning module version sanity check."
2023-07-06 14:29:35.264 DBG default: "- Original module"
2023-07-06 14:29:35.267 DBG default: "- No original module exists within this kernel\n - Installation\n - Installing to /lib/modules/6.3.9-1-liquorix-amd64/updates/dkms/"
2023-07-06 14:29:35.274 DBG default: "depmod..."
2023-07-06 14:29:38.275 DBG default: "."
2023-07-06 14:29:41.277 DBG default: "."
2023-07-06 14:29:41.496 DBG default: ""
2023-07-06 14:29:41.506 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:29:41.622 DBG default: "Building module:"
2023-07-06 14:29:41.625 DBG default: "Cleaning build area..."
2023-07-06 14:29:41.664 DBG default: ""
2023-07-06 14:29:41.667 DBG default: "make -j8 KERNELRELEASE=6.3.9-1-liquorix-amd64 KVER=6.3.9-1-liquorix-amd64..."
2023-07-06 14:29:44.667 DBG default: "."
2023-07-06 14:29:45.115 DBG default: ""
2023-07-06 14:29:46.908 DBG default: "Cleaning build area..."
2023-07-06 14:29:46.949 DBG default: ""
2023-07-06 14:29:46.963 DBG default: "wl.ko.xz:\nRunning module version sanity check."
2023-07-06 14:29:47.016 DBG default: "- Original module"
2023-07-06 14:29:47.019 DBG default: "- No original module exists within this kernel\n - Installation\n - Installing to /lib/modules/6.3.9-1-liquorix-amd64/updates/dkms/"
2023-07-06 14:29:47.026 DBG default: "depmod..."
2023-07-06 14:29:50.028 DBG default: "."
2023-07-06 14:29:53.030 DBG default: "."
2023-07-06 14:29:53.315 DBG default: ""
2023-07-06 14:29:53.325 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:29:53.535 DBG default: "Building module:"
2023-07-06 14:29:53.538 DBG default: "Cleaning build area..."
2023-07-06 14:29:53.563 DBG default: ""
2023-07-06 14:29:53.566 DBG default: "'make' all KVER=6.3.9-1-liquorix-amd64..."
2023-07-06 14:29:56.566 DBG default: "."
2023-07-06 14:29:59.568 DBG default: "."
2023-07-06 14:30:02.569 DBG default: "."
2023-07-06 14:30:05.571 DBG default: "."
2023-07-06 14:30:08.572 DBG default: "."
2023-07-06 14:30:11.573 DBG default: "."
2023-07-06 14:30:11.819 DBG default: "(bad exit status: 2)"
2023-07-06 14:30:11.823 WRN default: "Error! Bad return status for module build on kernel: 6.3.9-1-liquorix-amd64 (x86_64)\nConsult /var/lib/dkms/rtl8188fu/1.0/build/make.log for more information."
2023-07-06 14:30:11.831 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:30:11.865 WRN default: "Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)"
2023-07-06 14:30:12.293 DBG default: "Building module:"
2023-07-06 14:30:12.301 DBG default: "Cleaning build area..."
2023-07-06 14:30:12.378 DBG default: ""
2023-07-06 14:30:12.384 DBG default: "'make' -j8 KVER=6.3.9-1-liquorix-amd64 USER_MODULE_NAME=rtl8821ce CONFIG_RTW_DEBUG=n..."
2023-07-06 14:30:15.384 DBG default: "."
2023-07-06 14:30:18.399 DBG default: "."
2023-07-06 14:30:21.401 DBG default: "."
2023-07-06 14:30:24.419 DBG default: "."
2023-07-06 14:30:27.435 DBG default: "."
2023-07-06 14:30:30.437 DBG default: "."
2023-07-06 14:30:33.451 DBG default: "."
2023-07-06 14:30:36.466 DBG default: "."
2023-07-06 14:30:37.593 DBG default: ""
2023-07-06 14:30:39.026 DBG default: "Cleaning build area..."
2023-07-06 14:30:39.079 DBG default: ""
2023-07-06 14:30:39.106 DBG default: "rtl8821ce.ko.xz:\nRunning module version sanity check."
2023-07-06 14:30:39.156 DBG default: "- Original module"
2023-07-06 14:30:39.160 DBG default: "- No original module exists within this kernel\n - Installation\n - Installing to /lib/modules/6.3.9-1-liquorix-amd64/updates/dkms/"
2023-07-06 14:30:39.166 DBG default: "depmod..."
2023-07-06 14:30:42.168 DBG default: "."
2023-07-06 14:30:45.169 DBG default: "."
2023-07-06 14:30:45.525 DBG default: ""
2023-07-06 14:30:45.535 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:30:45.572 WRN default: "Error! The /var/lib/dkms/rtl8821cu/5.12.0/6.3.9-1-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.\nThis indicates that it should not be built."
2023-07-06 14:30:45.582 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:30:45.726 DBG default: "Building module:"
2023-07-06 14:30:45.733 DBG default: "Cleaning build area..."
2023-07-06 14:30:45.741 DBG default: ""
2023-07-06 14:30:45.746 DBG default: "make -j8 KERNELRELEASE=6.3.9-1-liquorix-amd64 -C /lib/modules/6.3.9-1-liquorix-amd64/build M=/var/lib/dkms/virtualbox/7.0.8/build..."
2023-07-06 14:30:48.747 DBG default: "."
2023-07-06 14:30:50.785 DBG default: ""
2023-07-06 14:30:51.111 DBG default: "Cleaning build area..."
2023-07-06 14:30:51.114 DBG default: ""
2023-07-06 14:30:51.134 DBG default: "vboxdrv.ko.xz:\nRunning module version sanity check."
2023-07-06 14:30:51.185 DBG default: "- Original module"
2023-07-06 14:30:51.188 DBG default: "- No original module exists within this kernel\n - Installation"
2023-07-06 14:30:51.191 DBG default: "- Installing to /lib/modules/6.3.9-1-liquorix-amd64/updates/dkms/"
2023-07-06 14:30:51.193 DBG default: "vboxnetadp.ko.xz:\nRunning module version sanity check."
2023-07-06 14:30:51.243 DBG default: "- Original module"
2023-07-06 14:30:51.246 DBG default: "- No original module exists within this kernel\n - Installation\n - Installing to /lib/modules/6.3.9-1-liquorix-amd64/updates/dkms/"
2023-07-06 14:30:51.249 DBG default: "vboxnetflt.ko.xz:"
2023-07-06 14:30:51.252 DBG default: "Running module version sanity check."
2023-07-06 14:30:51.302 DBG default: "- Original module"
2023-07-06 14:30:51.305 DBG default: "- No original module exists within this kernel\n - Installation"
2023-07-06 14:30:51.307 DBG default: "- Installing to /lib/modules/6.3.9-1-liquorix-amd64/updates/dkms/"
2023-07-06 14:30:51.310 DBG default: "depmod..."
2023-07-06 14:30:54.312 DBG default: "."
2023-07-06 14:30:57.314 DBG default: "."
2023-07-06 14:30:57.674 DBG default: ""
2023-07-06 14:30:57.676 DBG default: "dkms: autoinstall for kernel: 6.3.9-1-liquorix-amd64 failed!"
2023-07-06 14:30:57.677 WRN default: "Error! One or more modules failed to install during autoinstall.\nRefer to previous errors for more information.\nrun-parts: /etc/kernel/postinst.d/dkms exited with return code 11\ndpkg: error processing package linux-image-6.3.9-1-liquorix-amd64 (--configure):\n installed linux-image-6.3.9-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1"
2023-07-06 14:30:57.681 DBG default: "Setting up libbabeltrace1:amd64 (1.5.11-1+b2) ..."
2023-07-06 14:30:57.692 DBG default: "Setting up linux-headers-6.3.9-1-liquorix-amd64 (6.3-9~mx23+1) ..."
2023-07-06 14:30:57.702 DBG default: "/etc/kernel/header_postinst.d/dkms:\ndkms: running auto installation service for kernel 6.3.9-1-liquorix-amd64."
2023-07-06 14:30:57.912 WRN default: "Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)"
2023-07-06 14:30:57.952 WRN default: "Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)"
2023-07-06 14:30:58.089 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:30:58.162 DBG default: "Building module:"
2023-07-06 14:30:58.166 DBG default: "Cleaning build area..."
2023-07-06 14:30:58.190 DBG default: ""
2023-07-06 14:30:58.192 DBG default: "'make' all KVER=6.3.9-1-liquorix-amd64..."
2023-07-06 14:31:01.193 DBG default: "."
2023-07-06 14:31:04.195 DBG default: "."
2023-07-06 14:31:07.196 DBG default: "."
2023-07-06 14:31:10.198 DBG default: "."
2023-07-06 14:31:13.199 DBG default: "."
2023-07-06 14:31:16.200 DBG default: "."
2023-07-06 14:31:16.608 DBG default: "(bad exit status: 2)"
2023-07-06 14:31:16.612 WRN default: "Error! Bad return status for module build on kernel: 6.3.9-1-liquorix-amd64 (x86_64)\nConsult /var/lib/dkms/rtl8188fu/1.0/build/make.log for more information."
2023-07-06 14:31:16.620 DBG default: "Sign command: /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file\nBinary /lib/modules/6.3.9-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed"
2023-07-06 14:31:16.656 WRN default: "Error! The /var/lib/dkms/rtl8821cu/5.12.0/6.3.9-1-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.\nThis indicates that it should not be built."
2023-07-06 14:31:16.659 DBG default: "dkms: autoinstall for kernel: 6.3.9-1-liquorix-amd64 failed!"
2023-07-06 14:31:16.659 WRN default: "Error! One or more modules failed to install during autoinstall.\nRefer to previous errors for more information.\nrun-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11\nFailed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.3.9-1-liquorix-amd64.postinst line 11.\ndpkg: error processing package linux-headers-6.3.9-1-liquorix-amd64 (--configure):\n installed linux-headers-6.3.9-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1"
2023-07-06 14:31:16.662 DBG default: "Processing triggers for man-db (2.11.2-2) ..."
2023-07-06 14:31:17.205 DBG default: "Processing triggers for libc-bin (2.36-9) ..."
2023-07-06 14:31:17.262 WRN default: "Errors were encountered while processing:\n linux-image-6.3.9-1-liquorix-amd64\n linux-headers-6.3.9-1-liquorix-amd64"
2023-07-06 14:31:17.489 WRN default: "E: Sub-process /usr/bin/dpkg returned an error code (1)"
2023-07-06 14:31:17.490 DBG default: Post-install
2023-07-06 14:31:17.491 DBG default: rebuild_dkms_packages.sh linux-image-6.3.9-1-liquorix-amd64
rm -f /etc/apt/sources.list.d/mxpitemp.list
apt-get update
2023-07-06 14:31:17.611 DBG default: "Hit:1 http://deb.debian.org/debian bookworm-updates InRelease"
2023-07-06 14:31:17.657 DBG default: "Hit:2 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease"
2023-07-06 14:31:17.684 DBG default: "Hit:3 http://deb.debian.org/debian bookworm InRelease"
2023-07-06 14:31:18.426 DBG default: "Hit:4 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease"
2023-07-06 14:31:24.656 DBG default: "Reading package lists..."
2023-07-06 14:31:25.642 DBG default: ""
2023-07-06 14:31:25.653 WRN default: "W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."
2023-07-06 14:31:25.655 DBG default: +++ void MainWindow::refreshPopularApps() +++
2023-07-06 14:31:25.656 DBG default: +++ QStringList MainWindow::listInstalled() +++
2023-07-06 14:31:25.656 DBG default: dpkg --get-selections | grep -v deinstall | cut -f1
2023-07-06 14:31:25.685 DBG default: +++ void MainWindow::displayPopularApps() const +++
2023-07-06 14:35:15.293 DBG default: +++ void MainWindow::on_pushCancel_clicked() +++
2023-07-06 14:35:15.293 DBG default: +++ void MainWindow::cleanup() +++
Re: MX-23 beta 2 feedback thread
Posted: Thu Jul 06, 2023 11:11 pm
by dolphin_oracle
I think I will set up removing rtl8821cu-dkms before installing kernels above 6.1. even with the build directrive to skip building, the postinstalls are still exiting with a non-zero exit code and the kernel, despite the fact that it works, will still try to reconfigure next app operation. @timkb4cq
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 9:44 am
by Wallon
Dear
@dolphin_oracle ,
As the "libparted2" package is installed on the MX 23 iso, you also need to install the "libparted-i18n" package for localisation.
I've updated the list.
Kind regards,
Wallon
Code: Select all
Missing in MX Linux for good localization;
++++++++++++++++++++++++++++++++++++++++++
compton-conf-l10n
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
libparted-i18n (*)
menu-l10n
qt6-translations-l10n
rpm-i18n
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 9:58 am
by dolphin_oracle
Wallon wrote: Fri Jul 07, 2023 9:44 am
Dear @dolphin_oracle ,
As the "libparted2" package is installed on the MX 23 iso, you also need to install the "libparted-i18n" package for localisation.
I've updated the list.
Kind regards,
Wallon
Code: Select all
Missing in MX Linux for good localization;
++++++++++++++++++++++++++++++++++++++++++
compton-conf-l10n
e2fsprogs-l10n
libgphoto2-l10n
libgpg-error-l10n
libparted-i18n (*)
menu-l10n
qt6-translations-l10n
rpm-i18n
all add thanks
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 10:12 am
by Jerry3904
Good work keeping up with this, you two!
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 12:23 pm
by megaherz33
I recorded the image with the help of Ventoy, MX 23 Beta was installed. Before that, there was an inscription about a critical error.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 1:01 pm
by rbeltz48
I don't know if this has already been reported and don't have time to look through 49 pages here. When using VLC media player 3gp media files do not play properly. The output is jerky and unintelligible. It appears that this is a Debian bug carried over into MX Beta and other Debian derivatives. Doesn't matter which Lenovo Thinkpad I'm using. Gives the same unintelligible results.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 1:41 pm
by Eadwine Rose
Start VLC through the terminal, what output does it give?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 1:43 pm
by megaherz33
MX Updater disappeared from the panel. How to return ?
MX 23 Beta 2..
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 1:48 pm
by Jerry3904
Menu: MX Updater
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 1:51 pm
by megaherz33
I can not find.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 2:00 pm
by megaherz33
It was possible to restore using the command:
sudo apt install --reinstall apt-notifier
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 2:35 pm
by daemonspudguy
Does MX-23 have a scheduled release date yet?
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 2:51 pm
by megaherz33
daemonspudguy wrote: Fri Jul 07, 2023 2:35 pm
Does MX-23 have a scheduled release date yet?
Should be out in July.
Re: MX-23 beta 2 feedback thread
Posted: Fri Jul 07, 2023 3:37 pm
by Eadwine Rose
Should be out when it is ready
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 3:34 am
by kobaian
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
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 6:10 am
by Melber
kobaian wrote: Sat Jul 08, 2023 3:34 am
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
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 10:47 am
by davemx
siamhie wrote: Thu Jul 06, 2023 6:30 pm
Jerry3904 wrote: Thu Jul 06, 2023 3:38 pm
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?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 12:22 pm
by 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).
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 12:32 pm
by 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
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 12:48 pm
by Eadwine Rose
The easiest thing to check.. did the download's check out (md5sum etc)? Did the stick's check turn out ok?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 1:32 pm
by 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.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 1:44 pm
by davemx
Jerry3904 wrote: Sat Jul 08, 2023 12:22 pm
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.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 1:47 pm
by siamhie
davemx wrote: Sat Jul 08, 2023 10:47 am
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}
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}
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.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 1:56 pm
by 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?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 2:20 pm
by 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)
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 2:27 pm
by Wallon
Dear @Jerry3904,
You need to review the localisation for [fr_BE].
When I save information from the Quick Info PC program, I get a window that opens and asks "Open with zzzFM"?
zzzFM is used by antiX and not by MX Linux.
I don't know if zzzFM is compatible with MX Linux.
I have used SpaceFM a lot with MX Linux but not zzzFM.
Even the "Exit Options" button is not translated into [fr_BE]!
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 4:03 pm
by davemx
To close up the Conky issue...
In the built-in version of geeky-tower that comes with MX-23beta, the colours for ${downspeedgraph and ${upspeedgraph default to 000000 000000. It should be changed to FFFFFF FFFFFF for the release. What threw me in some of the replies I got, was that people were saying that 000000 000000 defaults to black, and I still couldn't see it when I put a light background behind it. It doesn't default to black, it defaults to transparent. Which is why the replies I got made no sense to me. What is odder, is that in the previous version, MX21, these colour settings appeared to be ignored, they came out white — I tried the MX23 version of geeky-tower on my MX21 install and I could see the graphs. This suggests that if some of the Conky scripts haven't been changed since MX21, they may need to be!
Anyway, I've solved my issue, and hopefully helped the developers make the final MX23 perfect!! I'd expect nothing less.
P.S. I'm guessing that in 000000 000000 or FFFFFF FFFFFF, one figure is colour, the other is opaqueness.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 4:26 pm
by ceeslans
davemx wrote: Sat Jul 08, 2023 4:03 pmTo close up the Conky issue...
>snip<
P.S. I'm guessing that in 000000 000000 or FFFFFF FFFFFF, one figure is colour, the other is opaqueness.
No, it is not.
As clarified in the
conky man-pages:
downspeedgraph (netdev) (height),(width) (gradient colour 1) (gradient colour 2) (scale) (-t) (-l)
Download speed graph, colours defined in hex, minus the #. If scale is non-zero, it becomes the scale for the graph. Uses a logarithmic scale (to see small numbers) when you use -l switch. Takes the switch `-t' to use a temperature gradient, which makes the gradient values change depending on the amplitude of a particular graph value (try it and see).
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 5:18 pm
by Jerry3904
So what change do we need to make?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 5:40 pm
by davemx
Jerry3904 wrote: Sat Jul 08, 2023 5:18 pm
So what change do we need to make?
Ensure that colours for down-and-up-speedgraph are FFFFFF FFFFFF and not 000000 000000.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 5:42 pm
by davemx
ceeslans wrote: Sat Jul 08, 2023 4:26 pm
davemx wrote: Sat Jul 08, 2023 4:03 pmTo close up the Conky issue...
>snip<
P.S. I'm guessing that in 000000 000000 or FFFFFF FFFFFF, one figure is colour, the other is opaqueness.
No, it is not.
As clarified in the
conky man-pages:
downspeedgraph (netdev) (height),(width) (gradient colour 1) (gradient colour 2) (scale) (-t) (-l)
Download speed graph, colours defined in hex, minus the #. If scale is non-zero, it becomes the scale for the graph. Uses a logarithmic scale (to see small numbers) when you use -l switch. Takes the switch `-t' to use a temperature gradient, which makes the gradient values change depending on the amplitude of a particular graph value (try it and see).
I see. Well, if the background itself for the conky script is black, but made transparent so it comes out see-through grey, then the graph will be the same see-through grey and you won't be able to see it against any desktop, light or dark.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 5:47 pm
by ceeslans
Perhaps use the gradient combo 000000 FFFFFF ???
The graph would start clear white and fades out to dark grey.
Actually, shouldn't this be decided by the author?
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 6:11 pm
by CharlesV
Of all the default backgrounds, the gradient combo 000000 FFFFFF works well with all of them, except one, and stays with the authors color scheme also .
Edit: I guess it would matter where the tower was placed too ;-/
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 8:00 pm
by siamhie
Why not use a middle ground color like grey (808080) so that it shows on both light or dark colored backgrounds.
grey.png
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 9:14 pm
by 4ps4all
Is it possible to have drivers for a usb wifi adapter "wifi ac1300 Archer t3u plus tplink" in the kernel without to have to add them ?
lsusb
ID 2357:0138 TP-Link 802.11ac NIC
iwconfig
Bit Rate:400 Mbit/s
Kernel 6.1 does not seem to have these drivers. I tested some other newer kernel (liquorix 6.2 ) with not good results. The usb wifi adapter was very slow or not stable.
I found a guide to install the driver , with this driver the USB wifi Adapter seems quite stable with 6.1 kernel.
Anyway to have to install wifi drivers does not seem a simple thing (you need another way to access internet for example). I made a search for the module which is called RTL8822bu in synaptic , but it's not present any module with that name.
this is the link to the driver and the guide
https://github.com/morrownr/88x2bu
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 9:47 pm
by dolphin_oracle
Wallon wrote: Sat Jul 08, 2023 2:27 pm
Dear @Jerry3904,
You need to review the localisation for [fr_BE].
When I save information from the Quick Info PC program, I get a window that opens and asks "Open with zzzFM"?
zzzFM is used by antiX and not by MX Linux.
I don't know if zzzFM is compatible with MX Linux.
I have used SpaceFM a lot with MX Linux but not zzzFM.
Even the "Exit Options" button is not translated into [fr_BE]!
the exit-options tooltip on the tint2 panel is coded into the tint2rc file. I'm not sure that file supports localization.
as for the "open file in zzzFM". apparently that's in the translation file. It should just be "Open Folder". Likely the translation was automatically pulled from antiX string source.
** fixed now. apparently the translations were updated on transifex the day after the last packaging. all good.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 9:55 pm
by dolphin_oracle
Wallon wrote: Sat Jul 08, 2023 12:32 pm
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
the side panel tool-tips do not support localization. the tool-tips are not produced from the desktop files, but from the entries in the .fluxbox/scripts/DefaultDock.mxdk file.
I believe we have already fixed the non-working links.
the "settings manager" is custom-toolbox. not sure why its not localizing.
@Adrian . In my test some parts localize and some parts don't with fr_BE, but es_ES works much better.
Re: MX-23 beta 2 feedback thread
Posted: Sat Jul 08, 2023 10:00 pm
by dolphin_oracle
kobaian wrote: Sat Jul 08, 2023 3:34 am
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
thanks, fixing the icon and dekstop file now.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 12:15 am
by dolphin_oracle
Jerry3904 wrote: Sat Jul 08, 2023 5:18 pm
So what change do we need to make?
conky change made.
000000 ffffff
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 4:52 am
by maci01
This error occurred during the first update. Just announcing. It should be a bluetooth driver.
Nastavuje se balík rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) …
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Done.
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-amd64/updates/dkms/
Sorry, this is my first bug report and I'm a beginner. Have a nice day.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 9:50 am
by Joseph DeGarmo
Testing the beta 2 live session for KDE. Thanks for fixing the gamepad bug as well as editing the system info screen and adding the Wayland session. One minor bug: When a USB gamepad is connected or has been disconnected and then logging out and starting a new Wayland session, the attemped login kicks me back to the login screen. WORKAROUND: After SDDM loads, wait 10 seconds without touching the keyboard, then input the password to login. That will fix the Wayland login issue. Rebooting may also fix the issue, but I cannot really test that in a live session. I'm not sure how to fix this bug, but it's nothing major as long as you perform the workaround.
It's also worth noting that when the USB gamepad remains connected and you log in by inputting the password without clicking on the password field, then you should be fine.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 2:28 pm
by Stevo
I've ported over a PPA's GTK 4 current Celluloid,version 0.25 of an mpv frontend for MX 23 test, since I haven't installed it yet and don't know how it interacts with our GTK 3 theming in XFCE and compatibility in KDE. Also we can check out installing from MXPI's test repo tab now. Currently, Celluloid is the only application in the TR.
I don't know if there are any other GTK 4 apps in Debian at all, but it is supposed to be the future, and we might need a whole discussion thread on its theming issues if it's anything like GTK 3.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 3:28 pm
by dolphin_oracle
Stevo wrote: Sun Jul 09, 2023 2:28 pm
I've ported over a PPA's GTK 4 current Celluloid,version 0.25 of an mpv frontend for MX 23 test, since I haven't installed it yet and don't know how it interacts with our GTK 3 theming in XFCE and compatibility in KDE. Also we can check out installing from MXPI's test repo tab now. Currently, Celluloid is the only application in the TR.
I don't know if there are any other GTK 4 apps in Debian at all, but it is supposed to be the future, and we might need a whole discussion thread on its theming issues if it's anything like GTK 3.
I believe file-roller is also gtk4. we learned alot about its themeing, and make sure to set the dark-mode switch in gconf to accommodate it.
and its nice to have things in test now...
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 3:45 pm
by Stevo
maci01 wrote: Sun Jul 09, 2023 4:52 am
This error occurred during the first update. Just announcing. It should be a bluetooth driver.
Nastavuje se balík rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) …
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Done.
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-amd64/updates/dkms/
Sorry, this is my first bug report and I'm a beginner. Have a nice day.
I'm sorry, but I can't see any error...those messages are what we get with a successful module build and install!
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 4:11 pm
by fehlix
Stevo wrote: Sun Jul 09, 2023 3:45 pm
maci01 wrote: Sun Jul 09, 2023 4:52 am
This error occurred during the first update. Just announcing. It should be a bluetooth driver.
Nastavuje se balík rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) …
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Done.
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-amd64/updates/dkms/
Sorry, this is my first bug report and I'm a beginner. Have a nice day.
I'm sorry, but I can't see any error...those messages are what we get with a successful module build and install!
This issue is about the reported broken pipe "Error" within the dkms script itself at line 2497 with /sbin/dkms.
They do use "smart" logic to check whether /proc is mounted or not:
Code: Select all
# The <(cmd) idiom does not work if /proc is not mounted
if [ ! -e <(echo) ]; then
warn $"dkms will not function properly if /proc is not mounted."
fi
I guess something changed in bash - but despite bash's broken pipe the test seems to work.
Re: MX-23 beta 2 feedback thread
Posted: Sun Jul 09, 2023 4:41 pm
by gRegNfo
@maci01
Can you check your hardware fits this driver?
I managed to solve it. You can message me if you want guidlines
https://github.com/ivanovborislav/rtl8812au
fehlix wrote: Sun Jul 09, 2023 4:11 pm
Stevo wrote: Sun Jul 09, 2023 3:45 pm
I'm sorry, but I can't see any error...those messages are what we get with a successful module build and install!
This issue is about the reported broken pipe "Error" within the dkms script itself at line 2497 with /sbin/dkms.
They do use "smart" logic to check whether /proc is mounted or not:
Code: Select all
# The <(cmd) idiom does not work if /proc is not mounted
if [ ! -e <(echo) ]; then
warn $"dkms will not function properly if /proc is not mounted."
fi
I guess something changed in bash - but despite bash's broken pipe the test seems to work.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 5:17 am
by Wallon
Dear developers,
A developer reacted by telling me that I shouldn't use Rufus.
He asked me to recreate a Live USB key with the "MX Live USB Maker" program to install the MX Fluxbox 23 ISO beta 2.
I downloaded the ISO again.
I used the "GtkHash" program to check the MD5 and SHA256.
I burned the ISO on a Live USB key with "MX Live USB Maker".
The Live USB key works very well.
Language selection [fr_BE], time zone selection Brussels.
The Azerty keyboard for Belgium is recognised in Geany.
The 3 icons (Videos, Software, Install MX) don't work.
I have restarted the Live USB key.
Language selection [fr], Paris time zone selection.
The Azerty keyboard for France is recognised in Geany.
The 3 icons (Videos, Software, Install MX) don't work.
So there's no difference between Rufus and MX Live USB Maker.
Will there be a new MX Fluxbox 23 ISO version beta 3 ?
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 10:20 am
by rbeltz48
To: Eadwine Rose
Re: Post #492 regarding unintelligible audio with VLC
Here's the output when running VLC through the Terminal, both initializing and then trying to run the .3gp video file in question. Video is OK but audio is garbled both with VLC and also with Dragon Player. However, the file runs AOK with Mint 21.2.
rick@rick-testing:~/Desktop
$ vlc
VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
[000055b08b6a3550] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Gtk-Message: 10:15:52.822: Failed to load module "gail"
** (vlc:27223): WARNING **: 10:15:52.833: (../atk-adaptor/bridge.c:1105):atk_bridge_adaptor_init: runtime check failed: (root)
[000055b08b73de00] main playlist: playlist is empty
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[00007fdb5c00c0b0] avcodec decoder: Using OpenGL/VAAPI backend for VDPAU for hardware decoding
[mpeg4 @ 0x7fdb5c050780] Failed setup for format vdpau: hwaccel initialisation returned error.
[00007fdb5c00c0b0] avcodec decoder error: existing hardware acceleration cannot be reused
[00007fdb244abb50] gl gl: Initialized libplacebo v4.208.0 (API v208)
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
[00007fdb24136ed0] gl gl: Initialized libplacebo v4.208.0 (API v208)
rick@rick-testing:~/Desktop
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 10:24 am
by Eadwine Rose
@Stevo a vaapi issue above? Cannot remember if you ever saw my post with the tip to downgrade a package to solve the error.. No idea with post # that was anymore though.
edit:
viewtopic.php?p=729379#p729379
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 11:08 am
by Wallon
Dear developers,
I have installed MX Linux KDE beta 2 in [fr_BE] on USB key (format "f2fs")
All is good.
I noticed that the SHA256 and MD5 checks on the SourceForge website do not match the ISO.
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 11:15 am
by mklym
Code: Select all
System:
Kernel: 6.1.0-9-686-pae [6.1.27-1] arch: i686 bits: 32 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-686-pae 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_beta2_386 Libretto June 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Matsushita product: CF-29LTQGZBM v: 004 serial: <superuser required>
Mobo: Matsushita model: CF29-4 v: 001 serial: <superuser required> BIOS: Phoenix K.K.
v: 4.00L11 date: 07/19/2005
Battery:
ID-1: BATA charge: 14.4 Wh (27.0%) condition: 53.4/84.9 Wh (62.9%) volts: 11.6 min: 11.1
model: Panasonic CF-VZSU29A type: Li-ion serial: <filter> status: charging
CPU:
Info: model: Intel Pentium M bits: 32 arch: M Dothan built: 2003-05 process: Intel 90nm family: 6
model-id: 0xD (13) stepping: 8 microcode: 0x20
Topology: cpus: 1x cores: 1 smt: <unsupported> cache: 2 MiB note: check
Speed (MHz): 1600 min/max: 600/1600 scaling: driver: acpi-cpufreq governor: ondemand core:
1: 1600 bogomips: 3191
Flags: nx pae sse sse2
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics vendor: Matsushita driver: i915
v: kernel arch: Gen-3 code: Intel 130nm built: 2004-05 ports: active: LVDS-1 empty: VGA-1
bus-ID: 00:02.0 chip-ID: 8086:2592 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: intel
unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99") s-diag: 338mm (13.3")
Monitor-1: LVDS-1 mapped: LVDS1 res: 1024x768 hz: 60 size: N/A modes: 1024x768
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: i915 (: 915GM) direct-render: Yes
Audio:
Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio vendor: Matsushita driver: snd_intel8x0
v: kernel bus-ID: 00:1e.2 chip-ID: 8086:266e class-ID: 0401
API: ALSA v: k6.1.0-9-686-pae 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: Marvell 88E8053 PCI-E Gigabit Ethernet vendor: Matsushita driver: sky2 v: 1.30 pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 11ab:4362 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel PRO/Wireless 2915ABG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq
modules: wl bus-ID: 06:02.0 chip-ID: 8086:4223 class-ID: 0280
IF: eth1 state: down mac: <filter>
Drives:
Local Storage: total: 27.96 GiB used: 17.96 GiB (64.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: THNSNB030GMCJ size: 27.96 GiB block-size:
physical: 512 B logical: 512 B speed: <unknown> type: SSD serial: <filter> rev: 0202 scheme: MBR
Partition:
ID-1: / raw-size: 27.95 GiB size: 27.34 GiB (97.83%) used: 17.96 GiB (65.7%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 1024 MiB used: 340.2 MiB (33.2%) priority: -2 file: /swapfile
Sensors:
Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
Packages: pm: dpkg pkgs: 2046 libs: 1035 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.it.ubc.ca/mxlinux/mx/repo/ bookworm main non-free
Info:
Processes: 184 Uptime: 46m wakeups: 6 Memory: 1.46 GiB used: 1.09 GiB (74.5%) 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)
Unit runs good without any major issues. VLC works with no errors. I was just streaming some SuperCars from Oz in 720p and it was smooth without artifacts, tearing, etc.
I did notice that the QSI shows "Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors." but I have a terminal open running watch on sensors w/2 sec refresh showing 61.8C after watching the stream.
One thing that I have noticed is that when the screensaver, w/the default settings, kicks in the only way I can get out of it is ctrl+alt+backspace and then log back into my account.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 1:06 pm
by daemonspudguy
What is considered the default wallpaper for MX-23 beta 2? I've been using the Tangram wallpaper but I'm curious which is default. Also, I would personally suggest shipping 16:9 aspect ratio wallpapers as well because it's way more common than 16:10 in this day and age.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 1:17 pm
by dolphin_oracle
daemonspudguy wrote: Mon Jul 10, 2023 1:06 pm
What is considered the default wallpaper for MX-23 beta 2? I've been using the Tangram wallpaper but I'm curious which is default. Also, I would personally suggest shipping 16:9 aspect ratio wallpapers as well because it's way more common than 16:10 in this day and age.
the wallpaper that is on beta2 is default. it should be in your desktop settings as "default.png".
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 2:01 pm
by maci01
@gRegNfo
It is elderly NTB asus x571G intel630/nv1050 mobile. I tried connecting BT headphones and they work. It was probably really just a message about a bad module loading. Sorry for the alarm and thank you for your time. Have a nice evening.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 2:42 pm
by dadada
Hi.
I am currently using Mx-23. The question is, which version? I know that I downloaded the beta one and had it installed. I was enjoying using that. Later I downloaded beta two with intentions of checking it out for you (and of course myself.) I am not certain if I installed it. I don't think so.
Is there someway to check which beta I am using? Or is beta one updated to beta two anyway, by way of updates?
Thanks for your attention.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 2:43 pm
by Eadwine Rose
Of course.. check the menu, quick system info. That will tell you :) Welcome!
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 2:53 pm
by dolphin_oracle
dadada wrote: Mon Jul 10, 2023 2:42 pm
Hi.
I am currently using Mx-23. The question is, which version? I know that I downloaded the beta one and had it installed. I was enjoying using that. Later I downloaded beta two with intentions of checking it out for you (and of course myself.) I am not certain if I installed it. I don't think so.
Is there someway to check which beta I am using? Or is beta one updated to beta two anyway, by way of updates?
Thanks for your attention.
quick-system-info will tell you.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 3:45 pm
by Melber
Wallon wrote: Mon Jul 10, 2023 5:17 am
...
Language selection [fr_BE], time zone selection Brussels.
The 3 icons (Videos, Software, Install MX) don't work.
...
Language selection [fr], Paris time zone selection.
The 3 icons (Videos, Software, Install MX) don't work.
...
I can't reproduce this.
beta2 live USB, language fr_BE, idesk icons launch firefox, mxpi and mx-installer as expected.
beta2 live USB, language fr, idesk icons launch firefox, mxpi and mx-installer as expected.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 6:01 pm
by Jerry3904
Just to let MXFB people know: thanks to excellent and quick work by my @fehlix the All Apps menu will be localized in the RC.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 6:15 pm
by Wallon
Dear @Melber ,
I have no problem installing;
MX XFCE beta 2 - 64bits
MX KDE beta 2 - 64bits
So I don't understand how you install MX Fluxbox beta 2 - 64bits?
Have you tested the 32-bit version or the 64-bit version?
In what language do you launch the Live USB key? English?
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 6:44 pm
by Melber
@Wallon
Code: Select all
MX-23_fluxbox_beta2_x64 Libretto June 15 2023
I installed with the system language set to German (de_DE) and just clicked the install icon. I had first tested the live-usb with both English and German and all 3 icons worked fine.
The videos and software icons also work fine in my installed version (with German as system language).
As I said, I don't have your issue when I boot the live-usb and select either fr_BE or fr as system language at the grub screen.
Have you tried creating a new desktop icon with MX-idesktool and checking if the new icon works?
+++edit+++
What are the contents of these files on your live usb?
/usr/local/share/live-files/files/etc/skel/.idesktop/gazelle.lnk
~/.idesktop/Software.lnk
~/.idesktop/Videos.lnk
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 7:54 pm
by Wallon
Dear @Melber,
To install MX Flubox beta 2 - 64 bit, you need to launch the Live USB key in English.
The icons are active. I managed to install it in [fr_BE]
So there is a big BUG! If you launch the Live USB key in French or in French Belgium, the icons are not active.
Translation problem? Wrong typewriter apostrophe in the translation?
Best regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 7:57 pm
by dolphin_oracle
Wallon wrote: Mon Jul 10, 2023 7:54 pm
Dear @Melber,
To install MX Flubox beta 2 - 64 bit, you need to launch the Live USB key in English.
The icons are active. I managed to install it in [fr_BE]
So there is a big BUG! If you launch the Live USB key in French or in French Belgium, the icons are not active.
Translation problem? Wrong typewriter apostrophe in the translation?
Best regards,
Wallon
they are active for me on MX-23_fluxbox_beta2. when launched in fr_BE.
I'm not sure where your problem lies.
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 10:13 pm
by m_pav
@Wallon, what type of USB stick are you using when making the Live-USB? It has been my experience that budget models can be troublesome. On a machine like yours, it should take roughly 3-5 minutes to burn a Live-USB using a median quality USB Thumb drive. If it's taking much longer, like 7 minutes, then I would recommend replacing it with a quality unit, they make a world of difference. Personally, I use USB-SSD drives like this one -->
https://www.netac.com/product/US2-54.html, and the key to getting a decent unit is to look for the drives capabilities in MBPS instead of just the USB standard it conforms to.
Another thing I noticed from your qsi posted on page 51 -->
viewtopic.php?p=732433#p732433 <-- where your hardware stands out from the norm is the 4K 3840*1080 display with the open-source Noveau driver. If you can spare the time and effort, what effect does installing the nvidia driver have on your machine? I'm thinking in terms of the display x-y mapping here potentially not aligning with the icon positioning.
@dolphin_oracle is it possible to boot live with root persistence, install the nvidia drivers and reboot with persistence again to get a working nvidia driver at the next boot? I don't have any machines with such hardware so I just don't know.
If it is possible, I wonder if it would assist with the issue above, specifically in relation to mapping the icon positions to mouse clicks. Wallon has now got a fully featured Live USB and should be able to make changes running live, save them in persistence and potentially re-use them? (drivers) for subsequent live-with-persistence runs.
EDIT - added link to wallons qsi thread
Re: MX-23 beta 2 feedback thread
Posted: Mon Jul 10, 2023 10:53 pm
by dolphin_oracle
m_pav wrote: Mon Jul 10, 2023 10:13 pm
@dolphin_oracle is it possible to boot live with root persistence, install the nvidia drivers and reboot with persistence again to get a working nvidia driver at the next boot? I don't have any machines with such hardware so I just don't know.
yes you can use nvidia drivers on a live usb with persistence.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 1:54 am
by Eadwine Rose
Wallon wrote: Mon Jul 10, 2023 11:08 am
Dear developers,
I have installed MX Linux KDE beta 2 in [fr_BE] on USB key (format "f2fs")
All is good.
I noticed that the SHA256 and MD5 checks on the SourceForge website do not match the ISO.
Best regards,
Wallon
I think this is where your problem lies.. the checks match for me.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 4:03 am
by Wallon
Dear @Eadwine Rose ,
Regarding : SHA256 and MD5 checks
It wasn't a problem for me because I installed MX KDE beta 2 - 64 bits without any problems.
Kind regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 4:11 am
by Eadwine Rose
If the numbers don't match you are bound to run into issues. Hunting those down basically are a waste of time as the iso you installed from was faulty, even though it did install. Been there, done that, just a tip for the future.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 7:22 am
by Danathar
This isn't really a bug report, but rather a general question about using the beta live with persistence. Once the beta period is over and the official release is out, is there any reason why I can't continue to use it? Will the beta automatically transition into the production version? I'm just curious if I'll need to re-image my USB drive once the beta is over. Thanks for all your hard work!
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 7:41 am
by m_pav
You could use it but it wouldn't be complete. Already there are adjustments that are introduced at the build stage for the next RC1 when it comes available. Your best option is the use our "User Installed Packages" to make a list of your package modifications and reinstall when the final is released, however, we usually support RC1 and later through to full release status unless there are any major show-stoppers.
Note for reinstalling, if you've heavily modified your users accounts home folder, you can back it up and selectively restore elements that do not overwrite critical configs. If you use Firefox, you can restore your entire ~/.mozilla folder in full to the same location in your fresh install provided you have not yet opened firefox and it will be exactly as you remember it, but if you restore by overwriting the primary folders like Documents, Pictures, etc, then you may experience some oddities, however, it is perfectly safe to restore the contents of each folder without overwriting the folder itself.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 7:51 am
by Wallon
Dear @Eadwine Rose , Dear @dolphin_oracle , Dear @Melber , Dear @Jerry3904 , Dear @m_pav , Dear @fehlix ,
I've found the solution for using Live USB sticks with MX Fluxbox Beta 2 - 64 bits with language [fr] or [fr_BE] and with an Azerty keyboard!
I've tried several Live sticks. I always had the same problem, the icons on the desktop are not active.
I tested my Live keys on my Dell Latitude Pro 5590 laptop (i5-8350U - 16 GO ram - no graphics card - Intel UHD Graphics 620 - i915 driver). Still the same problem, the icons on the desktop are not active!
So it's not linked to the « nouveau » driver for Nvidia graphics cards!
Here's the solution for my computers;
F2 Language = French or French (BE)
F3 Time Zone = Paris or Brussels
F7 Console = ask
Press " Enter
Choose 1920x1080x8 resolution or 1920x1080x16 resolution or 1920x1080x32 resolution.
All the icons on the desktop are active on all my Live USB sticks.
Remark;
I should never do this with antiX.
I should never do this with MX Linux XFCE or MX Linux KDE.
I should never do this with Debian 12 Gnome or Debian 12 IceWm (net install each time, I don't use Calamarès).
Thank you for your patience, I know this has upset many people on the forum.
Kind regards,
Wallon
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 8:03 am
by dolphin_oracle
Wallon wrote: Tue Jul 11, 2023 7:51 am
Dear @Eadwine Rose , Dear @dolphin_oracle , Dear @Melber , Dear @Jerry3904 , Dear @m_pav , Dear @fehlix ,
I've found the solution for using Live USB sticks with MX Fluxbox Beta 2 - 64 bits with language [fr] or [fr_BE] and with an Azerty keyboard!
I've tried several Live sticks. I always had the same problem, the icons on the desktop are not active.
I tested my Live keys on my Dell Latitude Pro 5590 laptop (i5-8350U - 16 GO ram - no graphics card - Intel UHD Graphics 620 - i915 driver). Still the same problem, the icons on the desktop are not active!
So it's not linked to the « nouveau » driver for Nvidia graphics cards!
Here's the solution for my computers;
F2 Language = French or French (BE)
F3 Time Zone = Paris or Brussels
F7 Console = ask
Press " Enter
Choose 1920x1080x8 resolution or 1920x1080x16 resolution or 1920x1080x32 resolution.
All the icons on the desktop are active on all my Live USB sticks.
Remark;
I should never do this with antiX.
I should never do this with MX Linux XFCE or MX Linux KDE.
I should never do this with Debian 12 Gnome or Debian 12 IceWm (net install each time, I don't use Calamarès).
Thank you for your patience, I know this has upset many people on the forum.
Kind regards,
Wallon
not upset, just puzzled.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 12:03 pm
by shmu26
I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:
Code: Select all
sudo apt update && sudo apt upgrade 18:57:44
[sudo] password for Shmuel:
Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://deb.debian.org/debian bookworm InRelease
Hit:5 https://linux.teamviewer.com/deb stable InRelease
Hit:3 https://mxrepo.com/mx/repo bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apt-notifier mx-docs mx-installer mx-user
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/116 MB of archives.
After this operation, 1,852 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 362400 files and directories currently installed.)
Preparing to unpack .../apt-notifier_23.07.02_all.deb ...
Unpacking apt-notifier (23.07.02) over (23.07.01) ...
Preparing to unpack .../mx-docs_20230710_all.deb ...
Unpacking mx-docs (20230710) over (20230701+1) ...
Preparing to unpack .../mx-installer_23.7.02mx23_amd64.deb ...
Unpacking mx-installer (23.7.02mx23) over (23.7.01mx23) ...
Preparing to unpack .../mx-user_23.7.03_amd64.deb ...
Unpacking mx-user (23.7.03) over (23.7.02) ...
Setting up mx-user (23.7.03) ...
Setting up mx-installer (23.7.02mx23) ...
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
dpkg: error processing package appimagelauncher (--configure):
installed appimagelauncher package post-installation script subprocess returned error exit status 1
Setting up apt-notifier (23.07.02) ...
Setting up mx-docs (20230710) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
appimagelauncher
E: Sub-process /usr/bin/dpkg returned an error code (1)
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: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-23_beta2_x64 Libretto June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 2208 date: 07/09/2021
Battery:
ID-1: hidpp_battery_0 charge: 56% condition: N/A volts: 3.8 min: N/A model: Logitech G903
LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A serial: <filter> status: discharging
CPU:
Info: model: Intel Core i7-9700 bits: 64 type: MCP arch: Coffee Lake gen: core 9 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
microcode: 0xF8
Topology: cpus: 1x cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB
L2: 2 MiB desc: 8x256 KiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/4700 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 48000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Device-2: USB C Video Adaptor type: USB driver: N/A bus-ID: 1-3.1.1:8 chip-ID: 25a4:9321
class-ID: 1100 serial: <filter>
Device-3: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.4:7
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: kwin_x11 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: iris gpu: i915 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: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: VG27AQ1A serial: <filter>
built: 2020 res: 1920x1080 dpi: 82 gamma: 1.2 size: 596x336mm (23.46x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: right model: Samsung S24B300 serial: <filter>
built: 2013 res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54")
diag: 598mm (23.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 1-3.4:7 bus-ID: 00:1f.3 chip-ID: 0c45:636b chip-ID: 8086:a2f0 class-ID: 0102
class-ID: 0403 serial: <filter>
Device-2: Microdia USB Live camera 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: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-4.1:7
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: eth1 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
bus-ID: 1-10:6 chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
sub-v: 22bb hci-v: 4.0 rev: 22bb
Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 2.26 TiB used: 916.56 GiB (39.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: K1B3 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD120 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ACF0
scheme: GPT
Partition:
ID-1: / raw-size: 46.96 GiB size: 45.92 GiB (97.79%) used: 13.07 GiB (28.5%) fs: ext4
dev: /dev/sda7 maj-min: 8:7
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 26.7 MiB (27.8%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: pm: dpkg pkgs: 2673 libs: 1431 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/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://mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:
Processes: 265 Uptime: 16m wakeups: 8 Memory: 15.49 GiB used: 3.67 GiB (23.7%) 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: UEFI
Screenshot_20230711_184951.png
Screenshot_20230711_185022_2.png
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 12:05 pm
by shmu26
After the errors with MXPI, the desktop freezes
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 12:19 pm
by Danathar
m_pav wrote: Tue Jul 11, 2023 7:41 am
You could use it but it wouldn't be complete. Already there are adjustments that are introduced at the build stage for the next RC1 when it comes available. Your best option is the use our "User Installed Packages" to make a list of your package modifications and reinstall when the final is released, however, we usually support RC1 and later through to full release status unless there are any major show-stoppers.
Note for reinstalling, if you've heavily modified your users accounts home folder, you can back it up and selectively restore elements that do not overwrite critical configs. If you use Firefox, you can restore your entire ~/.mozilla folder in full to the same location in your fresh install provided you have not yet opened firefox and it will be exactly as you remember it, but if you restore by overwriting the primary folders like Documents, Pictures, etc, then you may experience some oddities, however, it is perfectly safe to restore the contents of each folder without overwriting the folder itself.
Thanks! I'll probably do a re-install, it's a little bit of work to get things back to where I am now on the beta but it's probably the best thing to do. I'm not too customized at this point that I couldn't re-create things in a hour or so (or less). The beta has been pretty solid thus far for me, other than the issue I had with not having the correct zram init script installed because I didn't have zramswap-sysvinit-compat installed and was using the script that came by default.
Really looking forward to the release!
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 12:24 pm
by shmu26
shmu26 wrote: Tue Jul 11, 2023 12:05 pm
After the errors with MXPI, the desktop freezes
Even after a couple reboots, the desktop no longer loads properly and is unusable.
Posting from a different distro...
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 1:23 pm
by siamhie
shmu26 wrote: Tue Jul 11, 2023 12:03 pm
I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:
Code: Select all
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Boot to systemd, not sys-v.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 1:36 pm
by shmu26
siamhie wrote: Tue Jul 11, 2023 1:23 pm
shmu26 wrote: Tue Jul 11, 2023 12:03 pm
I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:
Code: Select all
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Boot to systemd, not sys-v.
And maybe I should uninstall this Appimage Launcher?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 1:47 pm
by shmu26
siamhie wrote: Tue Jul 11, 2023 1:23 pm
shmu26 wrote: Tue Jul 11, 2023 12:03 pm
I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:
Code: Select all
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Boot to systemd, not sys-v.
The desktop is still broken after booting to systemd.
I think the issue is this one, which I reported once upon a time:
viewtopic.php?t=74421
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 1:55 pm
by Adrian
That has nothing to do with having the desktop broken.... what do you mean by broken, does it boot to CLI?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 2:02 pm
by shmu26
Adrian wrote: Tue Jul 11, 2023 1:55 pm
That has nothing to do with having the desktop broken.... what do you mean by broken, does it boot to CLI?
Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen. So that makes it hard to do anything.
Right now I am chrooted into MX from another distro.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 2:15 pm
by Adrian
Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen.
Doesn't sound related to MX PackageInstaller at all.
Run the package installer with -s "sudo mx-packagesinstaller -s" (see --help)
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 2:34 pm
by shmu26
Adrian wrote: Tue Jul 11, 2023 2:15 pm
Broken means I can't even open a terminal, either from an icon or by keyboard shortcut. Everything is frozen.
Doesn't sound related to MX PackageInstaller at all.
Run the package installer with -s "sudo mx-packagesinstaller -s" (see --help)
I ran a system restore to fix my desktop, and then ran your suggested command
MXPI works correctly, that way.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 2:44 pm
by 4ps4all
This is a guide for MXlinux to install protonvpn
https://protonvpn.com/support/official- ... -mx-linux/
The guide to install protonvpn work well with MX21,instead with MX23 the part of "Linux system tray icon" of proton-vpn-gui doesn't work.( the guide ton install for debian seems the same ).
In the guide say to install this package "gir1.2-appindicator3-0.1" but this package does not exist.
It would be great to add "protonvpn" in mx-packageinstaller.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 2:55 pm
by shmu26
shmu26 wrote: Tue Jul 11, 2023 1:47 pm
siamhie wrote: Tue Jul 11, 2023 1:23 pm
shmu26 wrote: Tue Jul 11, 2023 12:03 pm
I am having issues with MXPI.
See screenshots below.
It says no internet, but I have internet:
Code: Select all
Setting up appimagelauncher (2.2.0-travis995~0f91801+bionic) ...
Installing AppImageLauncher as interpreter for AppImages
+ systemctl restart systemd-binfmt
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Boot to systemd, not sys-v.
The desktop is still broken after booting to systemd.
I think the issue is this one, which I reported once upon a time:
viewtopic.php?t=74421
I succeeded in fixing MXPI using the same suggestion as
@Adrian made in the other thread
viewtopic.php?p=716854#p716854
where you said
Sorry, I think the config file is read from /root/.config/MX-Linux/mx-packageinstaller.conf (it might depend how you launch the program), so add the "skiponlinecheck=true" there too.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 3:00 pm
by Eadwine Rose
@shmu26 Please stop deleting post content. You know how to use the edit function, please edit your posts instead. Thanks.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 3:04 pm
by shmu26
Eadwine Rose wrote: Tue Jul 11, 2023 3:00 pm
@shmu26 Please stop deleting post content. You know how to use the edit function, please edit your posts instead. Thanks.
What's the best thing to do when the whole post is a useless mistake?
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 3:07 pm
by Eadwine Rose
Edit the post by strike out for instance, so it can still be seen, and state the mistake. Because people respond to it when they see it, and then having it gone devaluates their effort to help you. It is also bad form to remove the entire content.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 3:10 pm
by shmu26
Eadwine Rose wrote: Tue Jul 11, 2023 3:07 pm
Edit the post by strike out for instance, so it can still be seen, and state the mistake. Because people respond to it when they see it, and then having it gone devaluates their effort to help you. It is also bad form to remove the entire content.
Thanks, will do.
@Adrian Although I got MXPI to behave properly, using your old fix, I still ended up with a permanently frozen desktop. Can't figure that one out. I had to run a system restore several times so I could continue testing.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 4:22 pm
by siamhie
4ps4all wrote: Tue Jul 11, 2023 2:44 pm
This is a guide for MXlinux to install protonvpn
https://protonvpn.com/support/official- ... -mx-linux/
The guide to install protonvpn work well with MX21,instead with MX23 the part of "Linux system tray icon" of proton-vpn-gui doesn't work.( the guide ton install for debian seems the same ).
In the guide say to install this package "gir1.2-appindicator3-0.1" but this package does not exist.
It would be great to add "protonvpn" in mx-packageinstaller.
@4ps4all Seems that link is for previous versions of MX. Debian Bookworm doesn't have gir1.2-appindicator3-0.1 in it's repo.
Have you tried this method.
https://protonvpn.com/support/official- ... pn-debian/
Code: Select all
Linux system tray icon
Please note that we don’t support the system tray icon on Debian 11
because the package gir1.2-appindicator3-0.1 has been depreciated
and is not present on Debian 11.
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 4:30 pm
by FullScale4Me
4ps4all wrote: Tue Jul 11, 2023 2:44 pm
This is a guide for MXlinux to install protonvpn
https://protonvpn.com/support/official- ... -mx-linux/
The guide to install protonvpn work well with MX21,instead with MX23 the part of "Linux system tray icon" of proton-vpn-gui doesn't work.( the guide ton install for debian seems the same ).
In the guide say to install this package "gir1.2-appindicator3-0.1" but this package does not exist.
It would be great to add "protonvpn" in mx-packageinstaller.
The Proton install guide you cite has been written some time ago. It refers to "MX Linux 19+" in the line under the title. It links to a Deb file dated 12-May-2023.
For MX Linux 23 the desktops were updated: Xfce was updated from 4.16 to 4.18 and KDE Plasma was updated from 5.20.5 to 5.27.5
Let us know what their Debian 12 (released June 2023) support plans are. It would be best that you, as a Proton account holder make a support inquiry. MX 19 was based on Debian 10 and MX 21 was based on Debian 11.
ALSO: knowing what that extra bit they ask to be installed (gir1.2-appindicator3-0.1) actually is as that would help in packaging it for MX 23 too. I checked and found:
Code: Select all
$ apt info gir1.2-appindicator3-0.1
Package: gir1.2-appindicator3-0.1
State: not a real package (virtual)
N: Can't select candidate version from package gir1.2-appindicator3-0.1 as it has no candidate
N: Can't select versions from package 'gir1.2-appindicator3-0.1' as it is purely virtual
N: No packages found
Re: MX-23 beta 2 feedback thread
Posted: Tue Jul 11, 2023 5:03 pm
by Melber
@Wallon It is puzzling because no-one else has reported such an issue.
Wallon wrote: Tue Jul 11, 2023 7:51 am
...I've tried several Live sticks. I always had the same problem, the icons on the desktop are not active....
Do you mean you made various live-usbs from the same "bad" iso or did you download the iso again and then make a live-usb from that?
Are the icons active if you boot the "bad" live-usb with English as system language? What about other languages?
Does a right click on inactive icons do anything? It should open an idesk menu.
...Here's the solution for my computers...
F7 Console = ask
Press " Enter
Choose 1920x1080x8 resolution or 1920x1080x16 resolution or 1920x1080x32 resolution.
All the icons on the desktop are active on all my Live USB sticks...
Maybe idesk has a problem with whatever is getting set with auto screen resolution selection on your system rather than the language selection?
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 12, 2023 3:38 am
by oswald_c
FullScale4Me wrote: Tue Jul 11, 2023 4:30 pm
4ps4all wrote: Tue Jul 11, 2023 2:44 pm
This is a guide for MXlinux to install protonvpn
https://protonvpn.com/support/official- ... -mx-linux/
The guide to install protonvpn work well with MX21,instead with MX23 the part of "Linux system tray icon" of proton-vpn-gui doesn't work.( the guide ton install for debian seems the same ).
In the guide say to install this package "gir1.2-appindicator3-0.1" but this package does not exist.
It would be great to add "protonvpn" in mx-packageinstaller.
The Proton install guide you cite has been written some time ago. It refers to "MX Linux 19+" in the line under the title. It links to a Deb file dated 12-May-2023.
For MX Linux 23 the desktops were updated: Xfce was updated from 4.16 to 4.18 and KDE Plasma was updated from 5.20.5 to 5.27.5
Let us know what their Debian 12 (released June 2023) support plans are. It would be best that you, as a Proton account holder make a support inquiry. MX 19 was based on Debian 10 and MX 21 was based on Debian 11.
ALSO: knowing what that extra bit they ask to be installed (gir1.2-appindicator3-0.1) actually is as that would help in packaging it for MX 23 too. I checked and found:
Code: Select all
$ apt info gir1.2-appindicator3-0.1
Package: gir1.2-appindicator3-0.1
State: not a real package (virtual)
N: Can't select candidate version from package gir1.2-appindicator3-0.1 as it has no candidate
N: Can't select versions from package 'gir1.2-appindicator3-0.1' as it is purely virtual
N: No packages found
gir1.2-appindicator is in both the main MX21 repo
https://mxrepo.com/mx/repo/pool/main/li ... _amd64.deb (Maintainer: SwampRabbit) and the MX21 Test repo
https://mxrepo.com/mx/testrepo/pool/tes ... _amd64.deb (Maintainer: Steven Pusser). ProtonVPN therefore installs fine for me in MX21 with the system tray icon.
The absence of gir1.2-appindicator in Bullseye also affects quodlibet -
https://github.com/quodlibet/quodlibet/issues/3842.
If one of the current maintainers in MX21 could do so for MX23 it would be very welcome.
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 12, 2023 8:28 am
by Wallon
Dear
@Melber ,
In summary, the MX Fluxbox ISO image has always been good and I have always checked the SHA256 and MD5 signatures. I have never had a problem with the MX Fluxbox beta 2 - 64 bits ISO image. I downloaded the MX Fluxbox ISO image several times and the signatures were always good.
I have never had a problem with my USB keys. They are of good quality!
I always checked with "Arandr" if the resolution was good on my Live USB sticks. But that doesn't seem to be enough.
When I do "F7 Console" when I start up my Live USB sticks to choose the right resolution, I can right-click on the desktop icons. I get an English menu or a new help window.
I've installed Nvidia's proprietary driver because there's screen tearing with the "nouveau" driver. The installation went well.
For the moment, my MBR installation (Legacy) is working well in [fr_BE].
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: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
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: 0xF0
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: 1200 min/max: 800/3300 scaling: driver: intel_pstate governor: powersave
cores: 1: 1200 2: 1200 3: 1200 4: 1200 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: nvidia v: 525.105.17
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
bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
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: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 92 s-size: 1060x301mm (41.73x11.85")
s-diag: 1102mm (43.38")
Monitor-1: DP-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 90 size: 544x303mm (21.42x11.93")
diag: 623mm (24.52") modes: N/A
Monitor-2: HDMI-0 pos: right res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.75x11.65")
diag: 604mm (23.8") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.105.17 renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
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 serial: <filter> class-ID: 0403
Device-2: NVIDIA GM206 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 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.24 TiB used: 13.84 GiB (1.1%)
ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Samsung model: Flash Drive size: 119.51 GiB
block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s type: SSD serial: <filter> rev: 1100
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
SMART Message: Unable to run smartctl. Root privileges required.
ID-2: /dev/sdg maj-min: 8:96 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-3: /dev/sdh maj-min: 8:112 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
Partition:
ID-1: / raw-size: 59 GiB size: 59 GiB (100.00%) used: 13.84 GiB (23.5%) fs: f2fs dev: /dev/sda1
maj-min: 8:1
Swap:
Kernel: swappiness: 5 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 31.0 C pch: 46.5 C mobo: N/A gpu: nvidia temp: 47 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: pm: dpkg pkgs: 2090 libs: 1096 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://nl.mxrepo.com/mx/repo/ bookworm main non-free
Info:
Processes: 205 Uptime: 24m wakeups: 0 Memory: 15.57 GiB used: 1.7 GiB (10.9%) Init: systemd
v: 252 target: graphical (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)
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 12, 2023 10:47 am
by keos
What do i have to do update yt-dlp?
Code: Select all
keos@kaos:~
$ sudo yt-dlp -U
Available version: stable@2023.07.06, Current version: stable@2023.03.04
ERROR: As yt-dlp has been installed via apt, you should use that to update. If you're on a stable release, also check backports.
keos@kaos:~
$
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 12, 2023 12:38 pm
by Senpai
Modo oscuro falla.png
Hi:
Although I see that RC1 is not announced, I have tested the Fluxbox RC1s and I have seen this:
I don't know if it has to be like that, I ask... in Fluxbox (x32 and x64) the packages "mx-fluxbox-about and mxfb-art" are not installed.
In Fluxbox (x32 and x64) the installer does not pick up the change to dark mode with the "mx-confort-dark" theme that I do from the ISO-Live, I attach image.
In Fluxbox (x32 and x64) the "Mugshog" app runs at the same time with a terminal, I think that was only for the beta.
Regards
Re: MX-23 beta 2 feedback thread
Posted: Wed Jul 12, 2023 12:43 pm
by Jerry3904
We're looking at it, thanks.
Closing this tread.
