MX-23 beta 2 feedback thread

[Jerry3904]

What happens if you click on the bottom button "Clear Known Items"?

[andy]

...
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" ??? )

[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.

[fehlix]

...
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

[rej]

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.

[Eadwine Rose]

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

[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

[j2mcgreg]

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.

[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)

[shmu26]

This thread seems to have uncovered a bug in MX-23 beta 2
viewtopic.php?p=731648#p731648