linuxmint / ubiquity Goto Github PK

Linux Mint should have ption to easy installation codec to open encrypted dvds.
Good places are: mint-install when i install system on computer (checkbox near flash plugin and mp3 licenses) or mint-drivers when i install driver for my graphics card or something else hardware.
http://packages.ubuntu.com/xenial/libdvdcss2

What do you think?

linuxmint/mintdrivers#37

Sorry for spam.

Hi,

please add the option to select a target disk when using the option "Erase disk and install Linux Mint"

I know I can go to "Something else" and do it all manually.

But I actually love the comfort of the installer just creating everything with LVM and encryption, without me having to fiddle around in that little window (cannot even be resized) with all my disks and create it all manually. It would be a massive improvement for me, if I could just select a disk here, that the installer will complely use without touching any of the other disks.

Is there any other way to achieve this? Currently I just unplug all other disks for a Mint installation. Every year I come back checking if the installer has been improved, but I seems I'm the only one who would find that option useful?

Regards,
Sven

After installing Linux Mint 17.3 bêta, I saw that swap partition is in a logical partition, alone in an extended partition.
Putting the swap partition at the end of the disk is a good idea because it's easiest to move the swap partition after cloning by example. But why not only create a primary partition for swap, instead of a logical partition, when there isn't another system installed with Linux Mint ? It would be perfect.

Reported by two separate users on LM17 and LM17.1, one using installer DVD, the other installing from a USB key. Full details of our reports here:
http://forums.linuxmint.com/viewtopic.php?f=46&t=189595

To summarize, on a multi-disk system, user chose to install Mint on /dev/sdc, but the installer ran grub-install /dev/sda (despite having correctly installed Mint OS files on /dev/sdc). As a result, attempting to boot /dev/sdc will fail (because no bootloader was installed on this disk), and attempting to boot /dev/sda will ACTUALLY boot the fresh Mint install on /dev/sdc (because the bootloader on /dev/sda actually boots the OS from /dev/sdc)! This makes the user think that the Mint installer erased /dev/sda and put a fresh Mint install on /dev/sda (which is NOT the case). This could lead to catastrophic data loss.

Both of the reported cases involved LUKS + LVM installs; not sure if that is an important factor.

I've installed Linux Mint using the ZFS option, and I find the default layout provided by the installer is really not good (rationale below) so I had to customize /usr/share/ubiquity/zsys-setup to produce something more usable.
script: zsys-setup
diff: zsys-setup.diff

And I think it would be good to contribute those changes upstream. I'd need to clean up the script a bit, but is anyone here interested in that? Is this the correct place to submit?

Why did I have to make changes to the ZFS layout?

For context, the default layout is

fat32 EFI    512 MiB
linux-swap   2 GiB
zfs bpool    2 GiB
zfs rpool    rest of disk

This is not good because (and this is the only downside of ZFS) it's not possible to resize ZFS partitions. So if you want to add more swap or dual boot, you can't. You're stuck. So I changed zsys-setup to produce this for my 2TiB NVMe drive:

fat32 EFI    512 MiB
zfs bpool    2 GiB
zfs rpool    500 GiB
linux-swap   2 GiB
unallocated  rest of disk

This leaves a bunch of unallocated space to be used how you wish. And if you want all that space in the rpool, you can easily create a second vdev and attach it to the rpool. In my case this is how I used the space:

fat32 EFI        512 MiB
zfs bpool        2 GiB
zfs rpool        500 GiB
zfs rpool(vdev2) 1.25 TiB
zfs SLOG(hdd)    32 GiB (SLOG for hdd pool separate from rpool)
linux-swap       64 GiB

Currently installing Linux Mint as encrypted is quite complicated. I would propose to add the system-config-lvm package by default.
In addition I would expect to have ability to choose LVM-volumes inside LUKS-encrypted partition - currently it is not possible. E.g. I would choose separate partitions for / and home.
The idea is that if operating system is needed to be reinstalled - I would expect, that I could reused /home partition as currently when it is not encrypted. So there should be possible to mount LUKS-encrypted partition during installation and continue partitioning like usually (currently) with LVM-volumes. I mean I would like to format / and just mount /home but not format inside LUKS like I currently do when disk is not encrypted. I also need to rename the old user folder inside /home volume to avoid accidental overwriting old user home folder with empty one.
I could currently find ZuluCrypt application - https://github.com/mhogomchungu/zuluCrypt and website http://mhogomchungu.github.io/zuluCrypt/ - possibly would this app useful to integrate but it seems that this app needs some improvements - even system-config-lvm has better UI (shows graphically volumes)
Also hibernate feature should be restored when encrypting swap.

This only is replaced by "Linux Mint" after kernel updates or manual sudo update-grub2 (I'm not even sure).
This is a Pita for newbies and supporters which try to help them without seeing the problem but only have (wrong) descriptions, see this on Reddit:

https://www.reddit.com/r/linuxmint/comments/115iuag/linux_mint_isnt_booting_from_ssd/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button

There are two bugs in Ubiquity when installing Linux Mint 18.1 along with other OSs following the instructions on https://community.linuxmint.com/tutorial/view/2026 (+1 for offering support for full-disk-encryption when installing Linux in parallel to another OS). These two bugs may cause most of the error reports and questions that can be found on the network. Reproducible on a Lenovo X260 laptop.

Bug 1: When the grub installation fails in Ubiquity, an error pop-up is shown. After clicking OK, the user ends up in the "Bootloader install failed" dialog box. Non-depending what is selected (Choose a different device to install the bootloader on, Continue without a bootloader, cancel the installation) the button has no function - i.e., users are caught in an infinite loop and there's no way of bypassing this dialog.

Bug 2: Grub installation fails within the installation process because Ubiquity fails to configure the GRUB_ENABLE_CRYPTODISK=y line in /etc/default/grub - despite the fact that users have created a physical volume for encryption in the partitioning step and set up Linux on an encrypted partition as outlined in the link above. Because of Bug 1 there's no way to work around this issue, as the installation stops during grub installation. There's a corresponding error message in /var/log/syslog (grub-installer: grub-install.real: error: attempt to install to encrypted disk without cryptodisk enabled. Set 'GRUB_ENABLE_CRYPTODISK=1' in file '/etc/default/grub' ..). Obviously the error output of grub is also erroneous (should read: GRUB_ENABLE_CRYPTODISK=y and NOT =1).

hih J

Hello , I click on the linux mint installation icon.
I click on forward and then I get this error. "Installer Crashed"
I want to use Linux mint distribution but I am getting this error.

I don't have access to the bug now, but to reproduce, I unplugged my HDD, installed via a USB stick, and when trying to find a persistent driver, clicked + to see what pops up, but it crashed the installer.

Hello, I get an error when trying to install linux mint 20.3 (latest installer) on this configuration:

• 2 nvme drives
• one luks partition on the 1st drive to be mounted as "/"
• one ext4 partition on the 1st drive to be mounted ad "/boot"
• one fat32 partition on the 1st drive to be used ad "EFI"
• one luks partition on the 2nd drive to be mounted as "/home"
  The creation of the partitions (with luks) works well enough (but there are some minor bugs there as well), but whatever fs type I decide to use for "/" and "/home" (be it ext4 or btrfs) as soon as I get to the page where I can specify the time zone, after a few seconds I get the message that "The attempt to mount a filesystem with type ext4 (or btrfs) in Encrypted volume (...) at /home failed. You may resume...". Then if I go back the UI is a little bit out of sync...

I have tried many times: restarting, rebooting, reloading... it's always the same result: cannot install linux mint in that computer.
There are already another 2 linux distributions on the 2 drives with the same configuration and they work well.
Uploading a screenshot and the syslog.

syslog.gz

Issue/Bug Description:
if you want to choose in the install process what packages you want to keep/remove you can't do that , you have to do that after, this should be in the iso to pick what packages you want, or pick just xorg/wayland to install everything your self

Expected behavior:

step X on the install process
[] libreoffice
[X] vlc
[] gnome-disks
[] nemo
Other Notes:

This issue isn't a bug or a request for features or other changes. I decided to ask the question here, as a Google search of "debootstrap" pointed me here.

Exactly what process do you use to transform the Debian Linux ISO into the LMDE ISO? What automated script do you run that starts off with Debian Linux and produces the LMDE ISO in the end? From what I've read and from my past experience in remastering LMDE (using MintConstructor) and antiX Linux, I'm guessing that your process involves creating a Linux distro using the debootstrap command to create your own special directory and download minimal Debian, chrooting into this directory, installing packages on top of this local Debian system, creating a special ISO directory (that includes all of the files that appear when one opens the ISO file), updating the file in the ISO directory that corresponds to the main system, and finally transforming the contents of the ISO directory into an ISO file.

Hi,
after installing Linux Mint on BTRFS filesystem, I noted that the swapfile is not enabled. I read that swapfile couldn't work with Copy-on-Write feature enabled for this specific file.

Up to LM14 ubiquity has always had a bug. It showed the instructions in Italian, but when it's installing and a presentation is shown there is an alternating of pages in English and in Italian. When I mean alternating I want to say that page 1 is in Italian, page 2 in English, page 3 in Italian again, and the same after. Is this related to a bug in ubiquity or are there untranslated parts? If it's the latter I propose myself for translating.

I want to know what ubiquity would do when user choose layout and variant in ubi-console-setup.py?
Which script will be run at that time?
What's the principle when the 'next' button be clicked?

The image in installer slide show should be updated, because for 3 years now Firefox redesigned its interface - pictures below. This is important to ensure Mint doesn't seem outdated, especially to new users who open up Firefox after installing the OS and see the inconsistency.

https://blog.mozilla.org/en/products/firefox/fresh-new-look-for-firefox/

Current:

Expected:

This is an old but still reproducible bug ticket. I report it here again, since before there were no issues on this repo.
Previous ticket: linuxmint/linuxmint#320

Ubiquity installer from LiveCD (actually USB) crashes on a step after choosing Language, Keyboard Layout and Wi-Fi network:

Error message in text:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 843, in <lambda>
    lambda: self.dbfilter.start(auto_process=True))
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 103, in start
    prep = self.prepare()
  File "/usr/lib/ubiquity/plugins/ubi-prepare.py", line 478, in prepare
    self.setup_sufficient_space()
  File "/usr/lib/ubiquity/plugins/ubi-prepare.py", line 503, in setup_sufficient_space
    free = self.free_space()
  File "/usr/lib/ubiquity/plugins/ubi-prepare.py", line 517, in free_space
    devices = proc.communicate()[0].rstrip('\n').split('\n')
  File "/usr/lib/python3.8/subprocess.py", line 1011, in communicate
    stdout = self.stdout.read()
  File "/usr/lib/python3.8/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa1 in position 89: invalid start byte

The problem is reproducible with Mint 20 Cinnamon, Mint 20 Mate, Ubuntu 20.04 Desktop and Ubuntu 20.10 Desktop.

My assumption is that the problem lies in the name of SSD "Innovation??IT" where ?? are two strange characters, not readable in console.
F.i. parted shows it like this:

mint@mint:~$ cat /proc/mdstat
Personalities : 
unused devices: <none>
mint@mint:~$ sudo parted -l
Warning: The driver descriptor says the physical block size is 2048 bytes, but
Linux says it is 512 bytes.
Ignore/Cancel? c                                                          
Model: SanDisk Ultra USB 3.0 (scsi)
Disk /dev/sda: 123GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Model: INNOVATION��IT (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  945MB   944MB   ntfs            Basic data partition          hidden, diag
 2      945MB   1217MB  273MB   fat32           EFI system partition          boot, esp
 3      1217MB  1352MB  134MB                   Microsoft reserved partition  msftres
 4      1352MB  382GB   381GB   ntfs            Basic data partition          msftdata
 6      382GB   416GB   33.6GB  linux-swap(v1)                                swap
 7      416GB   1012GB  596GB   ext4
 5      1012GB  1024GB  12.6GB  ntfs            Basic data partition          hidden, diag

INXI:

mint@mint:~$ inxi -Fxz
System:    Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: MATE 1.24.0 Distro: Linux Mint 20 Ulyana 
           base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: LENOVO product: 20L6S0AF00 v: ThinkPad T480 serial: <filter> 
           Mobo: LENOVO model: 20L6S0AF00 v: SDK0J40697 WIN serial: <filter> UEFI [Legacy]: LENOVO v: N24ET48W (1.23 ) 
           date: 02/20/2019 
Battery:   ID-1: BAT0 charge: 1.3 Wh condition: 23.9/23.9 Wh (100%) model: LGC 01AV489 status: Unknown 
           ID-2: BAT1 charge: 8.1 Wh condition: 22.8/24.1 Wh (95%) model: Celxpert 01AV424 status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 
           Speed: 700 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 700 2: 700 3: 701 4: 700 
Graphics:  Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.4 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo ThinkPad T480 driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.4.0-26-generic 
Network:   Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 
           IF: enp0s31f6 state: down mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
           IF: wlp3s0 state: up mac: <filter> 
Drives:    Local Storage: total: 1.04 TiB used: 198.7 MiB (0.0%) 
           ID-1: /dev/nvme0n1 vendor: Innovation model: IT size: 953.87 GiB 
           ID-2: /dev/sda type: USB vendor: SanDisk model: Ultra USB 3.0 size: 114.56 GiB 
Partition: ID-1: / size: 7.58 GiB used: 138.0 MiB (1.8%) fs: overlay source: ERR-102 
           ID-2: /var/log size: 110.38 GiB used: 60.7 MiB (0.1%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 191 Uptime: 21m Memory: 15.16 GiB used: 734.7 MiB (4.7%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
           Shell: bash v: 5.0.16 inxi: 3.0.38 

The problem was already reported at Linuxmint forums two times before:

• MATE Python install error
• Linux Mint 19.3 and 20 Mate installation error

and again after me:

• Installer crashes all time, can't figure out why

I am not sure if this is the right place to post this but I accidentally discovered a bug in the Linux Mint Mate upgrade to 21.3 installer.

One of my machines I updated a few weeks ago all of a sudden could not connect to the internet. Something about system clock not correct. I checked and sure enough instead of a March 2024 date it showed Nov 21 2023. I corrected the date and then access to the internet was restored.

Further investigation showed that the update removed the ntp service but did not install the timesyncd service. I have now confirmed this on two other machine upgrades. Once I installed the timesyncd service the clock stays up to date. So far the first one was a laptop and the other 2 are newer desktops. I suspect I will find this to be true for the rest of the desktops I am responsible for. The two newer machines were only off by 20 to 30 seconds so I would have not noticed the problem on them for a while.
The laptop was actually a 2013 Chromebook converted to Linux Mint a while back when they stopped updating it. I suspect the user ran the battery down and the machine powered off. After recharging the clock was really off.

I have recently installed LMDE, then attempted to install (onto a different partition on the same PC) the main edition of Linux Mint. I found the main-edition installer to have several usability problems, and I don't remember the LMDE installer being that bad. So maybe the LMDE installer should be used for the main edition in the future.

To give you an idea of what I'm talking about, I'll list what I happen to remember:

• The partition setup screen had several issues:
  • The graphic can omit some partitions if they are very small; this happened to the 0.1GB EFI system partition. This was disorienting to me, since I'd spent a lot of effort putting that partition there, so in my mind it wasn't zero pixels wide. :-) As a result of this partition being omitted, the color coding (of the graphic vs. the legend below it) didn't seem to match up until I realized what the problem was.
  • The graphic also doesn't show the partitions' % space used, which could help a user very much in identifying the partitions, since in normal PC usage (and also in Windows) the partitions typically aren't referred to with Linux device names like "/dev/sda2".
  • An existing bootable Ubuntu "/" partition wasn't detected as having an OS on it. This could easily allow the user to install Linux Mint onto that partition by mistake.
  • In the popup window for editing a partition, the default is to ask the user to select a format type (btrfs, ext4fs, etc.) - implying that the partition will be reformatted - even when (maybe because the partition contains valuable data) the user hasn't ticked the checkbox to reformat the partition.
  • The GUI should make it more obvious that the most common mount points to specify are / and /home. For example, the mount-point combobox currently defaults to blank, letting the user type a text string, but I'd prefer if this control were a listbox which defaulted to one of the standard values ("/", "/home", etc.) and had an option for "Other" which opened a text-entry field.
  • At the lower left of the partition screen, there is a button called "Change" which is mandatory for the user to click in order to set up the partitions correctly. This button-label sounds too drastic. All I wanted to do was to decompress Linux Mint from the USB stick to an existing, blank, Linux-formatted partition, not to "change" anything else on the hard drive.
• Erasing the whole hard drive is the default? I suspect that:
  • Almost all Linux Mint installs are either (a) "distro-hopping" or (b) a dual-boot with Windows. Even the usual same-distro upgrade (from, say, Linux Mint 17 to Linux Mint 18 when LM17's support is about to expire) is just a special case of "distro-hopping." In neither (a) nor (b) should the whole hard drive be erased.
  • Therefore, it probably takes more admin experience to know that it is safe to erase the whole hard drive than to want to preserve existing data on that drive.
  • OEMs, who seem to be the most likely market segment to erase the whole hard drive, may do the install in a more automated way (e.g., UEFI allows netboot) and not use this GUI.

Some of these issues may sound unimportant, but the installer is one of the most important components that has to make sophisticated admin tasks be straightforward for inexperienced users. I could write a few more sentences about this, but hopefully I don't have to.

If you want a more definitive list of the problems, I can try the main-edition install again & take notes. However, I offered the suggestion the way I did because I hope this way would be less work than fixing the problems with the existing main-edition installer.

The fact that a separate installer exists for LMDE may indicate that the development team has already been aware of the above issues.

The current releases of Linux Mint are LMDE 2 "Betsy" (2017 update) and Linux Mint (Main Edition) 18.1 Serena.

(this was tested on both Cinnamon and XFCE)

1. boot the live CD

2. run the Mint installer

3. when you get to the point that has the option to "Erase disk and install Vanessa", click "Install now"

4. in the window that pops up notifying you of partition changes, click "go back"

5. regardless of what option you select, the "Install now" or "Continue" button will be stuck greyed out

If you click back, then click "Continue", the options will no longer be greyed out... until you repeat steps 3 and 4, at which point the issue re-occurs:

I am using the 21.1 live installer.

I have 2 disks -- nvme0 with an existing linux installation and nvme1 as the target for the new installation. When using the advanced partitioner, I specifically request to ignore/do-not-use any partitions on the disk with the existing installation.

Despite that, the installer consistently mounts nvme0's EFI partition to /target/boot/efi, installing the boot files into it and adding it to /etc/fstab.

Currently there is not possible to resize the installer window and especially it is problematic when partitioning the disk. I would propose to add window resize buttons also to the installer window. Also there would be useful to just drag window bigger with mouse like usually.

The essence of the problem: there are 2 disks - these are SSD and nvme disks. Windows is installed on nvme. Linux is installed on ssd, and /boot/efi is always installed on nvme for some reason, even if it was created on ssd.

Reproducing the problem:

1. create partitions on ssd (/boot/efi, /)

Expected Behavior: Created on ssd

Current behavior: root partition is created on ssd, and /boot/efi is created on nvme

Addition:
This problem is not reproducible in Ubuntu 23.04

Logs: https://linux-hardware.org/?probe=0dfc0118d2

When was selected as the language for the installation of German, is pre-selected later in the language for the keyboard English. It should be preset but in this case German.

You need to install mdadm before starting the installer and create raid. After install you need to chroot yourself and install the mdadm on the current install so you can boot with raid on.

I have also had issues with not able to install grub when trying to enable raid.

Windows 7 and Internet Explorer are now deprecated since some time now and image in installer slide show should be updated, maybe jumping directly to windows 11

Unfortunately, the ubiquity repo doesn't have an Issues tab so I'll just post here in the hopes that someone can fix it.

In the space allocation step of the installer, using a dark theme in XFCE will result in white text on a white background.

Source: https://www.reddit.com/r/linuxmint/comments/sotp0b/this_happens_when_doing_the_partition_mint_xfce/

I downloaded Linux Mint 21 with the Cinnamon desktop environment from here:
https://mirror.karneval.cz/pub/linux/linuxmint/iso/stable/21/

inxi -Szxxx
System:
  Kernel: 5.15.0-43-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: Cinnamon 5.4.8 tk: GTK 3.24.33 wm: Mutter vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy

I tested it in Virtualbox.
The installer crashes when searching for mirrors...
I tried several times, always with the above result.
So I turned off the network in Virtualbox while installing Linux Mint 21. So the installation completed.
To be fair, I also turned off the installation of the Multimedia codecs (installer), but I did that for the test later.

I updated the system (in terminal) on the first boot after installation:

sudo apt-get update

sudo apt-get upgrade

System reboot...

Using the Update Manager, I installed the available kernel update.

System reboot...

I switched to a faster mirror...

( Sorry, some of the output will be in Hungarian language )

Multimedia codecs (install)

Available at

apt-cache policy mint-meta-codecs
mint-meta-codecs:
  Telepítve: (nincs)
  Jelölt:    2022.07.03
  Verziótáblázat:
     2022.07.03 500
        500 http://mirror.pmf.kg.ac.rs/mint/packages.linuxmint.com vanessa/main amd64 Packages
        500 http://mirror.pmf.kg.ac.rs/mint/packages.linuxmint.com vanessa/main i386 Packages

Attempt to install the package

sudo apt-get install mint-meta-codecs --simulate
Csomaglisták olvasása... Kész
Függőségi fa építése... Kész
Állapotinformációk olvasása... Kész
Néhány csomagot nem lehetett telepíteni. Ez azt jelentheti, hogy
egy lehetetlen állapotot kért, vagy ha az unstable disztribúciót
használja, akkor néhány igényelt csomag még nem készült el vagy ki
lett mozdítva az Incoming-ból.
Az alábbi információk segíthetnek megoldani a problémát:

Az alábbi csomagoknak teljesítetlen függőségei vannak:
 gstreamer1.0-vaapi : Függ ettől: libgstreamer-plugins-bad1.0-0 (>= 1.20.3) de csak 1.20.1-1ubuntu2 telepíthető
E: A problémák nem javíthatók, sérült csomagokat fogott vissza.

Dependencies

apt-cache policy libgstreamer-plugins-bad1.0-0
libgstreamer-plugins-bad1.0-0:
  Installed: (none)
  Candidate: 1.20.1-1ubuntu2
  Version table:
     1.20.3-0ubuntu1 1 (phased 60%)
        500 https://mirror.alwyzon.net/ubuntu jammy-updates/universe amd64 Packages
     1.20.1-1ubuntu2 500
        500 https://mirror.alwyzon.net/ubuntu jammy/universe amd64 Packages

And there it is..., just not the one selected.

Installation

sudo apt-get install libgstreamer-plugins-bad1.0-0=1.20.1-1ubuntu2

or

sudo apt-get install libgstreamer-plugins-bad1.0-0=1.20.3-0ubuntu1

... none of these are good for installing mint-meta-codecs. If one is installed, the other is missing, and vice versa.

The solution seems to be to use aptitude (I'll abbreviate as much as possible).

sudo aptitude install mint-meta-codecs
A következő ÚJ csomagok lesznek telepítve:        
  cabextract{a} gstreamer1.0-libav{a} gstreamer1.0-plugins-bad{a}
  gstreamer1.0-plugins-ugly{a} imagemagick-6-common{a} liba52-0.7.4{a}
  libdca0{a} libde265-0{a} libdvdcss2{a} libfaad2{a} libfftw3-double3{a}
  libfluidsynth3{a} libfreeaptx0{a} libgssdp-1.2-0{a} libgupnp-1.2-1{a}
  libgupnp-igd-1.0-4{a} libheif1{a} libilmbase25{a} libinstpatch-1.0-2{a}
  libjxr-tools{a} libjxr0{a} libkate1{a} libldacbt-enc2{a} liblqr-1-0{a}
  libltc11{a} libmagickcore-6.q16-6{a} libmagickcore-6.q16-6-extra{a}
  libmagickwand-6.q16-6{a} libmjpegutils-2.1-0{a} libmodplug1{a}
  libmpcdec6{a} libmpeg2-4{a} libmpeg2encpp-2.1-0{a} libmplex2-2.1-0{a}
  libmspack0{a} libnice10{a} libopencore-amrnb0{a} libopencore-amrwb0{a}
  libopenexr25{a} libopenh264-6{a} libopenni2-0{a} libqrencode4{a}
  libsidplay1v5{a} libsoundtouch1{a} libspandsp2{a} libsrtp2-1{a}
  libunshield0{a} libvo-aacenc0{a} libvo-amrwbenc0{a} libwildmidi2{a}
  libzbar0{a} libzxingcore1{a} mint-meta-codecs{b} timgm6mb-soundfont{a}
  unrar{a} unshield{a}
0 csomag fog frissülni, 56 csomag lesz újonnan telepítve, 0 lesz eltávolítva és 1 nem fog frissülni.
Az archívumból 17,2 MB letöltendő. Kicsomagolás után 45,7 MB lesz elfoglalva.
A következő csomagoknak vannak nem teljesített függőségeik:
 mint-meta-codecs : Függ ettől: gstreamer1.0-vaapi de nem telepíthető
                    Függ ettől: libavcodec-extra de nem telepíthető
A következő műveletek oldják fel ezeket a függőségeket:
...
Megoldás elfogadása? [Y/n/q/?] n

A következő műveletek oldják fel ezeket a függőségeket:

     Az alábbi csomagok eltávolítása:                                           
1)     libavcodec58 [7:4.4.2-0ubuntu0.22.04.1 (jammy-security, jammy-updates, no

     Az alábbi csomagok telepítése:                                             
2)     gstreamer1.0-vaapi [1.20.1-1 (jammy)]                                    
3)     libaribb24-0 [1.0.3-2 (jammy)]                                           
4)     libavcodec-extra [7:4.4.2-0ubuntu0.22.04.1 (jammy-security, jammy-updates
5)     libavcodec-extra58 [7:4.4.2-0ubuntu0.22.04.1 (jammy-security, jammy-updat

Megoldás elfogadása? [Y/n/q/?] Y
A következő ÚJ csomagok lesznek telepítve:
  cabextract{a} gstreamer1.0-libav{a} gstreamer1.0-plugins-bad{a}
  gstreamer1.0-plugins-ugly{a} gstreamer1.0-vaapi{a}
  imagemagick-6-common{a} liba52-0.7.4{a} libaribb24-0{a}
  libavcodec-extra{a} libavcodec-extra58{a} libdca0{a} libde265-0{a}
  libdvdcss2{a} libfaad2{a} libfftw3-double3{a} libfluidsynth3{a}
  libfreeaptx0{a} libgssdp-1.2-0{a} libgupnp-1.2-1{a} libgupnp-igd-1.0-4{a}
  libheif1{a} libilmbase25{a} libinstpatch-1.0-2{a} libjxr-tools{a}
  libjxr0{a} libkate1{a} libldacbt-enc2{a} liblqr-1-0{a} libltc11{a}
  libmagickcore-6.q16-6{a} libmagickcore-6.q16-6-extra{a}
  libmagickwand-6.q16-6{a} libmjpegutils-2.1-0{a} libmodplug1{a}
  libmpcdec6{a} libmpeg2-4{a} libmpeg2encpp-2.1-0{a} libmplex2-2.1-0{a}
  libmspack0{a} libnice10{a} libopencore-amrnb0{a} libopencore-amrwb0{a}
  libopenexr25{a} libopenh264-6{a} libopenni2-0{a} libqrencode4{a}
  libsidplay1v5{a} libsoundtouch1{a} libspandsp2{a} libsrtp2-1{a}
  libunshield0{a} libvo-aacenc0{a} libvo-amrwbenc0{a} libwildmidi2{a}
  libzbar0{a} libzxingcore1{a} mint-meta-codecs timgm6mb-soundfont{a}
  unrar{a} unshield{a}
A következő csomagok lesznek ELTÁVOLÍTVA:
  libavcodec58{a}
0 csomag fog frissülni, 60 csomag lesz újonnan telepítve, 1 lesz eltávolítva és 1 nem fog frissülni.
Az archívumból 23,1 MB letöltendő. Kicsomagolás után 46,7 MB lesz elfoglalva.
Folytatás? [Y/n/?] y
...
                                                   
Current status: 2 (+1) upgradable.

Check

apt-cache policy libgstreamer-plugins-bad1.0-0 mint-meta-codecs
libgstreamer-plugins-bad1.0-0:
  Telepítve: 1.20.1-1ubuntu2
  Jelölt:    1.20.1-1ubuntu2
  Verziótáblázat:
     1.20.3-0ubuntu1 1 (phased 60%)
        500 https://mirror.alwyzon.net/ubuntu jammy-updates/universe amd64 Packages
 *** 1.20.1-1ubuntu2 500
        500 https://mirror.alwyzon.net/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status
mint-meta-codecs:
  Telepítve: 2022.07.03
  Jelölt:    2022.07.03
  Verziótáblázat:
 *** 2022.07.03 500
        500 http://mirror.pmf.kg.ac.rs/mint/packages.linuxmint.com vanessa/main amd64 Packages
        500 http://mirror.pmf.kg.ac.rs/mint/packages.linuxmint.com vanessa/main i386 Packages
        100 /var/lib/dpkg/status

System check

sudo apt-get update

sudo apt-get upgrade
Csomaglisták olvasása... Kész
Függőségi fa építése... Kész
Állapotinformációk olvasása... Kész
Frissítés kiszámítása... Kész
Az alábbi csomagok vissza lesznek tartva:
  gstreamer1.0-vaapi language-pack-en
0 frissített, 0 újonnan telepített, 0 eltávolítandó és 2 nem frissített.

and

sudo apt-get dist-upgrade
Csomaglisták olvasása... Kész
Függőségi fa építése... Kész
Állapotinformációk olvasása... Kész
Frissítés kiszámítása... Kész
Az alábbi csomagok vissza lesznek tartva:
  gstreamer1.0-vaapi language-pack-en
0 frissített, 0 újonnan telepített, 0 eltávolítandó és 2 nem frissített.

Still not good. The solution may again be aptitude.

sudo aptitude update

sudo aptitude full-upgrade
A következő csomagok lesznek frissítve:            
  gstreamer1.0-vaapi{b} language-pack-en{b}
2 csomag fog frissülni, 0 csomag lesz újonnan telepítve, 0 lesz eltávolítva és 0 nem fog frissülni.
Az archívumból 338 kB letöltendő. A kicsomagolás után 4.096 B fog felszabadulni.
A következő csomagoknak vannak nem teljesített függőségeik:
 language-pack-en : Függ ettől: language-pack-en-base (>= 1:22.04+20220721) but 1:22.04+20220415 is installed
 gstreamer1.0-vaapi : Függ ettől: libgstreamer-plugins-bad1.0-0 (>= 1.20.3) but 1.20.1-1ubuntu2 is installed
A következő műveletek oldják fel ezeket a függőségeket:
...
Megoldás elfogadása? [Y/n/q/?] n
A következő műveletek oldják fel ezeket a függőségeket:

     Az alábbi csomagok frissítése:                                                                   
1)     gstreamer1.0-plugins-bad [1.20.1-1ubuntu2 (jammy, now) -> 1.20.3-0ubuntu1 (jammy-updates)]     
2)     language-pack-en-base [1:22.04+20220415 (jammy, now) -> 1:22.04+20220721 (jammy-updates)]      
3)     libgstreamer-plugins-bad1.0-0 [1.20.1-1ubuntu2 (jammy, now) -> 1.20.3-0ubuntu1 (jammy-updates)]

Megoldás elfogadása? [Y/n/q/?] Y
A következő csomagok lesznek frissítve:
  gstreamer1.0-plugins-bad gstreamer1.0-vaapi language-pack-en language-pack-en-base
  libgstreamer-plugins-bad1.0-0
5 csomag fog frissülni, 0 csomag lesz újonnan telepítve, 0 lesz eltávolítva és 0 nem fog frissülni.
Az archívumból 3.377 kB/3.866 kB letöltendő. Kicsomagolás után 29,7 kB lesz elfoglalva.
Folytatás? [Y/n/?]
...
                                                   
Current status: 0 (-5) upgradable.

Check

sudo apt-get update
Találat:1 https://mirror.alwyzon.net/ubuntu jammy InRelease
Találat:2 https://mirror.alwyzon.net/ubuntu jammy-updates InRelease
Találat:3 https://mirror.alwyzon.net/ubuntu jammy-backports InRelease
Találat:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Mellőz:5 http://mirror.pmf.kg.ac.rs/mint/packages.linuxmint.com vanessa InRelease
Találat:6 http://mirror.pmf.kg.ac.rs/mint/packages.linuxmint.com vanessa Release
Csomaglisták olvasása... Kész

and

sudo apt-get upgrade
Csomaglisták olvasása... Kész
Függőségi fa építése... Kész
Állapotinformációk olvasása... Kész
Frissítés kiszámítása... Kész
0 frissített, 0 újonnan telepített, 0 eltávolítandó és 0 nem frissített.

However, the error reporting application is showing problems (while the Update Manager is already fine).

Screenshots:

https://postimg.cc/4KPPVNww
https://postimg.cc/8JCHHQ0G

After system reboot when I install the mint-meta-codecs package package, there is no indication of the same, but there is for the language package.

Message

The following packages have unmet dependencies:

language-pack-hu: Depends: language-pack-hu-base (>= 1:22.04+20220721) but 1:22.04+20220415 is to be installed

Check

apt-cache policy language-pack-hu-base
language-pack-hu-base:
  Telepítve: (nincs)
  Jelölt:    1:22.04+20220415
  Verziótáblázat:
     1:22.04+20220721 1 (phased 60%)
        500 https://mirror.alwyzon.net/ubuntu jammy-updates/main amd64 Packages
        500 https://mirror.alwyzon.net/ubuntu jammy-updates/main i386 Packages
     1:22.04+20220415 500
        500 https://mirror.alwyzon.net/ubuntu jammy/main amd64 Packages
        500 https://mirror.alwyzon.net/ubuntu jammy/main i386 Packages

Attempt to install the package

sudo apt-get install language-pack-hu-base
[sudo] password for mchegy:             
Csomaglisták olvasása... Kész
Függőségi fa építése... Kész
Állapotinformációk olvasása... Kész
Néhány csomagot nem lehetett telepíteni. Ez azt jelentheti, hogy
egy lehetetlen állapotot kért, vagy ha az unstable disztribúciót
használja, akkor néhány igényelt csomag még nem készült el vagy ki
lett mozdítva az Incoming-ból.
Az alábbi információk segíthetnek megoldani a problémát:

Az alábbi csomagoknak teljesítetlen függőségei vannak:
 language-pack-hu : Függ ettől: language-pack-hu-base (>= 1:22.04+20220721) de csak 1:22.04+20220415 telepíthető
E: A problémák nem javíthatók, sérült csomagokat fogott vissza.

Aptitude again

sudo aptitude install language-pack-hu-base
A következő ÚJ csomagok lesznek telepítve:         
  language-pack-hu-base{b} 
0 csomag fog frissülni, 1 csomag lesz újonnan telepítve, 0 lesz eltávolítva és 0 nem fog frissülni.
Az archívumból 937 kB letöltendő. Kicsomagolás után 3.911 kB lesz elfoglalva.
A következő csomagoknak vannak nem teljesített függőségeik:
 language-pack-hu-base : Függ ettől: language-pack-hu (>= 1:22.04+20220415) de nem telepíthető
A következő műveletek oldják fel ezeket a függőségeket:

     Az alábbi csomagok jelenlegi verzión tartása:
1)     language-pack-hu-base [Nincs telepítve]    

Megoldás elfogadása? [Y/n/q/?] n
A következő műveletek oldják fel ezeket a függőségeket:

     Az alábbi csomagok telepítése:               
1)     language-pack-hu [1:22.04+20220415 (jammy)]

Megoldás elfogadása? [Y/n/q/?] n
A következő műveletek oldják fel ezeket a függőségeket:

     Az alábbi csomagok telepítése:                            
1)     language-pack-hu [1:22.04+20220721 (jammy-updates)]     
2)     language-pack-hu-base [1:22.04+20220721 (jammy-updates)]

Megoldás elfogadása? [Y/n/q/?] Y
A következő ÚJ csomagok lesznek telepítve:
  language-pack-hu{a} language-pack-hu-base 
0 csomag fog frissülni, 2 csomag lesz újonnan telepítve, 0 lesz eltávolítva és 0 nem fog frissülni.
Az archívumból 940 kB letöltendő. Kicsomagolás után 3.920 kB lesz elfoglalva.
Folytatás? [Y/n/?] Y
Leszedés: 1 https://mirror.alwyzon.net/ubuntu jammy-updates/main amd64 language-pack-hu-base all 1:22.04+20220721 [938 kB]
Leszedés: 2 https://mirror.alwyzon.net/ubuntu jammy-updates/main amd64 language-pack-hu all 1:22.04+20220721 [1.896 B]
Fetched 940 kB in 0mp (3.756 kB/s)      
Selecting previously unselected package language-pack-hu-base.
(Adatbázis olvasása ... 318832 files and directories currently installed.)
Preparing to unpack .../language-pack-hu-base_1%3a22.04+20220721_all.deb ...
Unpacking language-pack-hu-base (1:22.04+20220721) ...
Selecting previously unselected package language-pack-hu.
Preparing to unpack .../language-pack-hu_1%3a22.04+20220721_all.deb ...
Unpacking language-pack-hu (1:22.04+20220721) ...
Beállítás: language-pack-hu (1:22.04+20220721) ...
Beállítás: language-pack-hu-base (1:22.04+20220721) ...
Generating locales (this might take a while)...
Generation complete.

All this is not enough, we need more here...

Screenshots:

https://postimg.cc/t7Yknb6t
https://postimg.cc/S2tG1TBM
https://postimg.cc/wRyQC5zb

History

cat /var/log/apt/history.log

...
Start-Date: 2022-07-30  10:46:45
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 65011726 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpx6vorgv9
Requested-By: mchegy (1000)
Install: linux-image-5.15.0-43-generic:amd64 (5.15.0-43.46, automatic), linux-headers-5.15.0-43-generic:amd64 (5.15.0-43.46, automatic), linux-modules-5.15.0-43-generic:amd64 (5.15.0-43.46, automatic), linux-modules-extra-5.15.0-43-generic:amd64 (5.15.0-43.46, automatic), linux-headers-5.15.0-43:amd64 (5.15.0-43.46, automatic)
Upgrade: linux-headers-generic:amd64 (5.15.0.41.43, 5.15.0.43.44), linux-generic:amd64 (5.15.0.41.43, 5.15.0.43.44), linux-image-generic:amd64 (5.15.0.41.43, 5.15.0.43.44)
End-Date: 2022-07-30  10:51:25

Start-Date: 2022-07-30  11:00:04
Commandline: apt-get install libgstreamer-plugins-bad1.0-0=1.20.3-0ubuntu1
Requested-By: mchegy (1000)
Install: libgstreamer-plugins-bad1.0-0:amd64 (1.20.3-0ubuntu1)
End-Date: 2022-07-30  11:00:06

Start-Date: 2022-07-30  11:01:03
Commandline: apt-get purge libgstreamer-plugins-bad1.0-0=1.20.3-0ubuntu1
Requested-By: mchegy (1000)
Purge: libgstreamer-plugins-bad1.0-0:amd64 (1.20.3-0ubuntu1)
End-Date: 2022-07-30  11:01:04

Start-Date: 2022-07-30  11:01:27
Commandline: apt-get install libgstreamer-plugins-bad1.0-0=1.20.1-1ubuntu2
Requested-By: mchegy (1000)
Install: libgstreamer-plugins-bad1.0-0:amd64 (1.20.1-1ubuntu2)
End-Date: 2022-07-30  11:01:28

Start-Date: 2022-07-30  11:02:42
Commandline: apt-get purge libgstreamer-plugins-bad1.0-0=1.20.3-0ubuntu1
Requested-By: mchegy (1000)
Purge: libgstreamer-plugins-bad1.0-0:amd64 (1.20.1-1ubuntu2)
End-Date: 2022-07-30  11:02:43

Start-Date: 2022-07-30  11:03:44
Commandline: apt-get install libgstreamer-plugins-bad1.0-0=1.20.3-0ubuntu1
Requested-By: mchegy (1000)
Install: libgstreamer-plugins-bad1.0-0:amd64 (1.20.3-0ubuntu1)
End-Date: 2022-07-30  11:03:45

Start-Date: 2022-07-30  11:04:37
Commandline: apt-get install libgstreamer-plugins-bad1.0-0=1.20.1-1ubuntu2
Requested-By: mchegy (1000)
Downgrade: libgstreamer-plugins-bad1.0-0:amd64 (1.20.3-0ubuntu1, 1.20.1-1ubuntu2)
End-Date: 2022-07-30  11:04:38

Start-Date: 2022-07-30  11:06:38
Requested-By: mchegy (1000)
Install: libltc11:amd64 (1.3.1-1, automatic), cabextract:amd64 (1.9-3, automatic), gstreamer1.0-plugins-ugly:amd64 (1.20.1-1, automatic), libfreeaptx0:amd64 (0.1.1-1, automatic), libunshield0:amd64 (1.4.2-1, automatic), libzxingcore1:amd64 (1.2.0-1, automatic), libfluidsynth3:amd64 (2.2.5-1, automatic), libvo-aacenc0:amd64 (0.1.3-2, automatic), libzbar0:amd64 (0.23.92-4build2, automatic), libheif1:amd64 (1.12.0-2build1, automatic), libmpeg2encpp-2.1-0:amd64 (1:2.1.0+debian-6build1, automatic), libspandsp2:amd64 (0.0.6+dfsg-2, automatic), libavcodec-extra:amd64 (7:4.4.2-0ubuntu0.22.04.1, automatic), libopencore-amrnb0:amd64 (0.1.5-1, automatic), libqrencode4:amd64 (4.1.1-1, automatic), libfftw3-double3:amd64 (3.3.8-2ubuntu8, automatic), mint-meta-codecs:amd64 (2022.07.03), libgupnp-1.2-1:amd64 (1.4.3-1, automatic), libopencore-amrwb0:amd64 (0.1.5-1, automatic), libmplex2-2.1-0:amd64 (1:2.1.0+debian-6build1, automatic), libmspack0:amd64 (0.10.1-2build2, automatic), libmpcdec6:amd64 (2:0.1~r495-2, automatic), libgupnp-igd-1.0-4:amd64 (1.2.0-1build1, automatic), libfaad2:amd64 (2.10.0-2, automatic), timgm6mb-soundfont:amd64 (1.3-5, automatic), libopenexr25:amd64 (2.5.7-1, automatic), libmodplug1:amd64 (1:0.8.9.0-3, automatic), libopenh264-6:amd64 (2.2.0+dfsg-2, automatic), libmagickcore-6.q16-6-extra:amd64 (8:6.9.11.60+dfsg-1.3build2, automatic), libmjpegutils-2.1-0:amd64 (1:2.1.0+debian-6build1, automatic), libgssdp-1.2-0:amd64 (1.4.0.1-2build1, automatic), libmagickwand-6.q16-6:amd64 (8:6.9.11.60+dfsg-1.3build2, automatic), libopenni2-0:amd64 (2.2.0.33+dfsg-15, automatic), libavcodec-extra58:amd64 (7:4.4.2-0ubuntu0.22.04.1, automatic), libkate1:amd64 (0.4.1-11build1, automatic), libsidplay1v5:amd64 (1.36.60-1, automatic), libwildmidi2:amd64 (0.4.3-1, automatic), libmpeg2-4:amd64 (0.5.1-9, automatic), libdca0:amd64 (0.0.7-2, automatic), libilmbase25:amd64 (2.5.7-2, automatic), libmagickcore-6.q16-6:amd64 (8:6.9.11.60+dfsg-1.3build2, automatic), libldacbt-enc2:amd64 (2.0.2.3+git20200429+ed310a0-4, automatic), libjxr-tools:amd64 (1.2~git20170615.f752187-5, automatic), unshield:amd64 (1.4.2-1, automatic), gstreamer1.0-vaapi:amd64 (1.20.1-1, automatic), libvo-amrwbenc0:amd64 (0.1.3-2, automatic), imagemagick-6-common:amd64 (8:6.9.11.60+dfsg-1.3build2, automatic), unrar:amd64 (1:6.1.5-1, automatic), libsrtp2-1:amd64 (2.4.2-2, automatic), liba52-0.7.4:amd64 (0.7.4-20, automatic), libnice10:amd64 (0.1.18-2, automatic), libinstpatch-1.0-2:amd64 (1.1.6-1, automatic), libsoundtouch1:amd64 (2.3.1+ds1-1, automatic), gstreamer1.0-plugins-bad:amd64 (1.20.1-1ubuntu2, automatic), libjxr0:amd64 (1.2~git20170615.f752187-5, automatic), gstreamer1.0-libav:amd64 (1.20.3-0ubuntu1, automatic), libaribb24-0:amd64 (1.0.3-2, automatic), libdvdcss2:amd64 (1.4.2-dmo1, automatic), libde265-0:amd64 (1.0.8-1, automatic), liblqr-1-0:amd64 (0.4.2-2.1, automatic)
Remove: libavcodec58:amd64 (7:4.4.2-0ubuntu0.22.04.1)
End-Date: 2022-07-30  11:06:59

Start-Date: 2022-07-30  11:20:02
Requested-By: mchegy (1000)
End-Date: 2022-07-30  11:20:02

Start-Date: 2022-07-30  11:22:19
Requested-By: mchegy (1000)
Upgrade: language-pack-en-base:amd64 (1:22.04+20220415, 1:22.04+20220721), language-pack-en:amd64 (1:22.04+20220415, 1:22.04+20220721), libgstreamer-plugins-bad1.0-0:amd64 (1.20.1-1ubuntu2, 1.20.3-0ubuntu1), gstreamer1.0-vaapi:amd64 (1.20.1-1, 1.20.1-1ubuntu1), gstreamer1.0-plugins-bad:amd64 (1.20.1-1ubuntu2, 1.20.3-0ubuntu1)
End-Date: 2022-07-30  11:22:24

Start-Date: 2022-07-30  11:54:54
Requested-By: mchegy (1000)
Install: language-pack-hu:amd64 (1:22.04+20220721, automatic), language-pack-hu-base:amd64 (1:22.04+20220721)
End-Date: 2022-07-30  11:54:57

Start-Date: 2022-07-30  11:58:56
Commandline: aptdaemon role='role-install-packages' sender=':1.77'
Install: firefox-locale-hu:amd64 (103.0+linuxmint1+vanessa), hunspell-hu:amd64 (1:7.2.0-2), libreoffice-l10n-hu:amd64 (1:7.3.4-0ubuntu0.22.04.1), thunderbird-locale-hu:amd64 (1:91.11.0+build2-0ubuntu0.22.04.1), mythes-hu:amd64 (1:7.2.0-2), libreoffice-help-hu:amd64 (1:7.3.4-0ubuntu0.22.04.1), language-pack-gnome-hu-base:amd64 (1:22.04+20220721, automatic), language-pack-gnome-hu:amd64 (1:22.04+20220721), hyphen-hu:amd64 (1:7.2.0-2)
End-Date: 2022-07-30  11:59:22

Please, look at the problems.

Even after manual partitioning and selecting only one partition to be mounted at root, Linux mint installer still installed a bootloader, and automatically mounted /dev/sda1 to /boot/efi.

I remember ubuntu having an option like this.

• linuxmint-21.1-cinnamon-64bit.iso

This happens with Mint 18.2 BETA (MATE 64-bit), with the default disk size in VirtualBox. But regardless of what VirtualBox does, or what the installer expects, we should never see contradictory information.

By updating the message (second sentence), the situation could be easily fixed:
"This computer has less disk space than required for the installation".

Or adjust the first sentence:
"You need more than X disk space..."

Anyway, if this is not configurable, the problem depends on the upstream release of Ubiquity.

Installing Linux Mint with FDE with multiple drives is a pain, because even if you have multiple drives it will erease all of them without letting the user select the drive they actually want to do a FDE Install

I installed Mint recently and was surprised to see that it is not possible to set the clock to UTC, which is possible on Windows. Please add this option.

Users are quite helpless when facing issue such as https://forums.linuxmint.com/viewtopic.php?t=417620 unless they are knowledgeable in Linux.

Whatever reason making the display driver failed in live session, the installed Linux Mint will also fail if it isn't set into compatibility mode too. So we should install LM into compatibility mode.

Can no longer install Linux Mint mate when BIOS parameters are set to legacy settings. This problem just started fairly recently.

No, do not wish to have boot and partitioning that forces Linux Mint user into using UEFI bios.

All the previous installs that I have done over the past 15 years or so have allowed partitioning to be the following:
/ root
/home
swap partition

Nothing else required, and that is still how I (and probably a lot of other users) would like use of legacy BIOS to allow partitioning of install drive to be organized.

Let me know if you have questions. Thanks.

This is a suggestion/feature request to include all major Mint desktop environments (Cinnamon, MATE, KDE & Xfce) in unified Mint installer images. The desktop environment would be chosen at boot time from the Grub menu. Additionally a "minimal" or "no desktop environment" option would be a nice to have.

Advantages:

• Fewer download options - less choice and confusion for new users
• Only one download required for those who want to try/install the different desktop environments (less total bandwidth consumed in this case)
• Fewer torrents, more seeders, better availability of installer images
• Lower barrier to trying out the different desktop environments - just reboot the Live image (no more burning required)
• Fewer DVDs and memory sticks required for administrators

Downsides:

• Releases have historically been staggered - all desktop environments would have to be made available at once (this might be easier for Mint >17)
• Increased complexity of Live image boot
• The installer downloads would obviously be larger (but wouldn't fit on a CD in any case)

The number of installer images could be reduced to five from the current fourteen (not including LMDE), as follows:

• Cinnamon, MATE, KDE & Xfce (32 & 64 bit)
• Cinnamon, MATE, KDE & Xfce - no codecs (32 & 64 bit)
• Cinnamon, MATE - OEM (64 bit)

linuxmint/cinnamon#5153 as discussed here,

Hello. The Mint Ubiquity installer prompts user for multimedia codec installation early during the install process. This is without regard to an active internet connection. If user without internet connection selects for codec installation, Ubiquity still attempts to install codec, unsuccessfully. User may also assume codecs were actually installed, when they were not.

If codecs are unavailable on iso, Ubiquity should defer user prompt when no internet connection exist. Please save user confusion and time.

See /var/log/installer/syslog beginning line 2313 refer to codec installation online. See beginning line 2622 refer to errors resolving network address.
syslog.txt

Apologies if this issue is outside the scope of your Ubiquity project.

System:
  Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy

If you boot the liveCD and then install mdadm to access an existing software raid, the install works fine until it comes time to install GRUB to the device, and it fails to recognize the mdadm raid partition, so fails and also causes ubiquity to quit without finishing its cleanup. The issue is that the generated chroot does not have mdadm installed, even if it is existing within the livecd.

I propose that ubiquity should fail gracefully if an issue occurs at grub install, still finishing the cleanup tasks that would normally take place, and alert you that your system is not bootable, and to retry installing grub manually, or better yet, have a check in place that if someone installed mdadm into the liveCD, to install it automatically into the chroot / for compatibility sake. It would not hurt someone if it was there in general, and would solve a great problem.

Thank you!

Is it possible to hide keyboard-configuration ui in ubiquity?
Keeps its keyboard been auto configured and hides its ui.

When using the installer at a given moment you are asked to type username and password for the new user.

In the Dutch translation of 'ask for password' there is the word 'vergen'.
This should be 'vragen' (to ask)

Due to a recent python3.4 update (3.4.0-2 -> 3.4.3-1) ubiquity2.18.8 hangs indefinitely.
The issue was reported on Ubuntu here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1326707

The issue was fixed upstream in 2.18.9, https://launchpadlibrarian.net/212954680/ubiquity_2.18.8.8_2.18.8.9.diff.gz (first diff)

Trying out latest Linux Mint iso, and when the partitioning step came up, I tried resizing the window for the installer but it's not possible.

Tried every way possible: Meta + mouse drag, double clicking window drag area, right clicking window title then Maximize. They all don't work.

Please add the ability to resize/maximize the installer window. This would help small screens.

Hi, I'm not sure I'm reporting an issue in the right place. Please let me know if it's not the right place.

I recently reinstall Linux mint 21 on an old laptop. I use the live installer and I ask for a new partition table. I didn't see any type option but I was expecting it will select the recommended one for my laptop then I move on to the other step.
The install succeed but I wasn't able to boot after the restart.

I fix the problem by creating the table partition to ms-doos using Gparted then reinstalling Linux mint.
I imagine the type created by the installer is gpt even if it's an old laptop (no uefi)

A solution would be to ask for a type of partition table like Gparted or to make them ms-doos if the laptop is not compatible with uefi
From my understanding eufi and gpt are linked together but I'm not sure.

Trying to revive a mid 2009 Macbook Pro using the Cinnamon Edition of Vanessa.

The live system is installed on an USB flash drive. It boots fine and the live desktop enviroment also works normally from what I can tell from the applications I started like Firefox or Libreoffice.

But when I click on the installation icon nothing happens at all. Copying the installation command into a terminal also does nothing at all. And I say nothing at all because the system doesn't seem to get busy at all like showing a busy ball instead of the regular mouse pointer.

What is wrong here? Or what else can I check?

Describe the bug
This occurs when installing from an iso file located in the same partition that will be formatted (e.g. as root or as boot) and installed.

The following procedure worked with linuxmint-20.3-cinnamon-64bit.iso.

I have been updating my systems this way so far. In brief, copying the iso file to /boot/grml or to /boot/boot-isos.
An entry could be added manually to grub, but I have been using the 'grml-rescueboot' package (installed from the repository with apt install) or booting from USB with Super Grub Disk.
In the boot sequence, in the ISO grub menu, edit the entry (pressing 'e') and add 'toram' to the 'linux' line and then boot ('F10').
After complete boot, in a terminal, losetup showed a loop for the iso file in the isodevice (the partition that contained the iso file) and mount showed /isodevice mount pointing to the partition (MOUNT DOES NOT SHOW THIS LINE ANY MORE IN MINT 21).
Then I deleted the loop (with losetup -d) and afterwards unmounted /isodevice (IN MINT 21 THIS PRODUCES AND ERROR BECAUSE THERE IS NOT SUCH MOUNT).
After that, I could install normally, formatting the partition that contained the iso file (NOT ANY MORE, NOW IT STOPS WITH AN ERROR BECAUSE THE PARTITION IS USED BY THE SYSTEM).

To Reproduce
Steps to reproduce the behavior:

1. COPY THE ISO FILE TO THE DESTINATION PARTITION AND INCLUDE IT IN GRUB

sudo apt install grml-rescueboot 
sudo cp /media/user/EXTERNAL/boot-isos/linuxmint-21-cinnamon-64bit-beta.iso /boot/grml/
sudo update-grub

Alternatively a manual entry in the grub menu could be added:

menuentry "Grml Rescue System (linuxmint-21-cinnamon-64bit-beta.iso)" {
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt5'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx
        else
          search --no-floppy --fs-uuid --set=root xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx
        fi
        iso_path="/boot/grml/linuxmint-21-cinnamon-64bit-beta.iso"
        export iso_path
        kernelopts="   "
        export kernelopts
        loopback loop "/boot/grml/linuxmint-21-cinnamon-64bit-beta.iso"
        set root=(loop)
        configfile /boot/grub/loopback.cfg
}

2. REBOOT AND SELECT GRUB ENTRY "Grml Rescue System (linuxmint-21-cinnamon-64bit-beta.iso)"
3. IN THE NEXT GRUB MENU (THE ONE OF THE ISO FILE) EDIT THE FIRST ENTRY
   Press 'e'.
   Add 'toram' to the 'linux' line. And press 'F10'

linux  /casper/vmlinuz file=/cdrom/pressed/linuxmint.seed boot=casper iso-scan/filename=${iso_path} toram quiet splash --

4. AFTER BOOTING, IN A TERMINAL WINDOW, TYPE:

mint@mint:~$ losetup
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE                         DIO LOG-SEC
/dev/loop1
             0      0         0  0 /cdrom/casper/filesystem.squashfs   0     512
/dev/loop0
             0      0         0  0 /isodevice/boot/grml/linuxmint-21-cinnamon-64bit-beta.iso
                                                                       0     512
mint@mint:~$ sudo losetup -d /dev/loop0
mint@mint:~$ mount
[[/isodevice IS NOT LISTED]]
mint@mint:~$ sudo umount /isodevice
umount: /isodevice: no mount point specified.
mint@mint:~$ 

5. INSTALL ON SDA5, AN ERROR IS RAISED
   
   
6. THE PARTITION IS BUSY. CONFIRMED IN GPARTED
   

Expected behavior
To work as it did with linuxmint-20.3-cinnamon-64bit.iso.
Everything works the same for 1, 2, and 3.
4. AFTER BOOTING, IN A TERMINAL WINDOW, TYPE:

mint@mint:~$ losetup
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE                         DIO LOG-SEC
/dev/loop1
             0      0         0  0 /cdrom/casper/filesystem.squashfs   0     512
/dev/loop0
             0      0         0  0 /isodevice/boot/grml/linuxmint-20.3-cinnamon-64bit.iso
                                                                       0     512
mint@mint:~$ sudo losetup -d /dev/loop0
mint@mint:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=1904916k,nr_inodes=476229,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=390432k,mode=755)
/dev/sda5 on /isodevice type ext4 (rw,relatime)
/dev/shm on /cdrom type tmpfs (rw,relatime,size=2307212k)
/dev/loop1 on /rofs type squashfs (ro,noatime)
[[... EDITED FOR BREVITY]]
mint@mint:~$ sudo umount /isodevice
mint@mint:~$ 

5. INSTALL ON SDA5 WORKS FLAWLESSLY
   

I am trying to install Mint 17 v2 and ReiserFS is completely absent from the "use as" menu in the partitioner. I do not want to reformat my home partition and I'd rather not have to fiddle with the fstab after installation.