Bug 2165949 - ValueError: New minimal size cannot be bigger than current maximum size.
Summary: ValueError: New minimal size cannot be bigger than current maximum size.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: blivet-gui
Version: 37
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vojtech Trefny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:481615f2ce4bdac0db8318cbdf0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-31 14:57 UTC by heinoldk
Modified: 2024-01-12 22:38 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-01-12 22:38:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (1.85 MB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: anaconda.log (32.52 KB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: dbus.log (3.60 KB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: environ (562 bytes, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: journalctl (1.27 MB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: lsblk_output (1.48 KB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: nmcli_dev_list (1.56 KB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: os_info (712 bytes, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: program.log (21.26 KB, text/plain)
2023-01-31 14:57 UTC, heinoldk
no flags Details
File: storage.log (487.85 KB, text/plain)
2023-01-31 14:58 UTC, heinoldk
no flags Details

Description heinoldk 2023-01-31 14:57:47 UTC
Description of problem:
Just out of curiosity tried to check the encrypt checkbox when creating a boot partition with the advanced custom partition maker during setup, but it crashed when checking the box. This is in a virtual machine.

Version-Release number of selected component:
anaconda-core-37.12.6-1.fc37.x86_64

The following was filed automatically by anaconda:
anaconda 37.12.6 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.11/site-packages/blivetgui/dialogs/size_chooser.py", line 748, in min_size
    raise ValueError("New minimal size cannot be bigger than current maximum size.")
  File "/usr/lib/python3.11/site-packages/blivetgui/dialogs/size_chooser.py", line 255, in set_parents_reserved_size
    self.main_chooser.min_size = self.min_size
  File "/usr/lib/python3.11/site-packages/blivetgui/dialogs/add_dialog.py", line 590, in update_size_area_limits
    self.size_area.set_parents_reserved_size(reserved_size)
  File "/usr/lib/python3.11/site-packages/blivetgui/dialogs/add_dialog.py", line 913, in on_encrypt_check
    self.update_size_area_limits(min_size=self._get_min_size_limit(),
  File "/usr/lib/python3.11/site-packages/blivetgui/dialogs/widgets.py", line 379, in _on_encrypt_toggled
    handler.method(self.encrypt, *handler.args)
ValueError: New minimal size cannot be bigger than current maximum size.

Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --graphical
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-37-1-7 rd.live.image rd.live.check quiet
dnf.librepo.log: 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         6.0.7-301.fc37.x86_64
other involved packages: blivet-gui-runtime-2.4.0-1.fc37.noarch
product:        Fedora
release:        Fedora release 37 (Thirty Seven)
type:           anaconda
version:        37

Comment 1 heinoldk 2023-01-31 14:57:49 UTC
Created attachment 1941317 [details]
File: anaconda-tb

Comment 2 heinoldk 2023-01-31 14:57:51 UTC
Created attachment 1941318 [details]
File: anaconda.log

Comment 3 heinoldk 2023-01-31 14:57:52 UTC
Created attachment 1941319 [details]
File: dbus.log

Comment 4 heinoldk 2023-01-31 14:57:53 UTC
Created attachment 1941320 [details]
File: environ

Comment 5 heinoldk 2023-01-31 14:57:55 UTC
Created attachment 1941321 [details]
File: journalctl

Comment 6 heinoldk 2023-01-31 14:57:56 UTC
Created attachment 1941322 [details]
File: lsblk_output

Comment 7 heinoldk 2023-01-31 14:57:57 UTC
Created attachment 1941323 [details]
File: nmcli_dev_list

Comment 8 heinoldk 2023-01-31 14:57:58 UTC
Created attachment 1941324 [details]
File: os_info

Comment 9 heinoldk 2023-01-31 14:57:59 UTC
Created attachment 1941325 [details]
File: program.log

Comment 10 heinoldk 2023-01-31 14:58:01 UTC
Created attachment 1941326 [details]
File: storage.log

Comment 11 Aoife Moloney 2023-11-23 01:09:46 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 12 Aoife Moloney 2024-01-12 22:38:18 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.