Open Yassine-cdev opened 1 week ago
In that way you install calamares?
Install it with the command: sudo eggs calamares --install
I'm not sure this is the problem, it's just a suggestion.
I use often calamares on Debian bookworm and can't confirm your problem. Someone can confirm this and in that release?
@pieroproietti Thank you for your suggestion. Yes, I did install Calamares using this command , I would appreciate it if anyone who uses this release could confirm if they have encountered the same problem or if there’s something specific to my setup that might be causing this.
Today, reading your test, I decided to make a test and I installed a common debian-bookworm remastered with penguins-eggs-10.0.42 (last version) on UEFI.
Again nothing to say, the installation - using calamares - went OK.
i get the same issue in vbox
**During the installation of Debian Bookworm (using Calamares), the installation fails with the following error message:
Boost.Python error in job "mount".** The error seems to occur when Calamares tries to mount the partitions. Below is the detailed error log from Calamares: <class 'Boost.Python.ArgumentError'> Python argument types in libcalamares.utils.mount(str, str, str, list) did not match C++ signature: mount(std::cxx11::basic_string<char, std::char_traits, std::allocator > device_path, std::__cxx11::basic_string<char, std::char_traits, std::allocator > mount_point)
mount(std:: cxx11::basic_string<char, std::char_traits, std::allocator > device_path, std::cxx11::basic_string<char, std::char_traits, std::allocator > mount_point, std::__cxx11::basic_string<char, std::char_traits, std::allocator > filesystem_name)
mount(std:: cxx11::basic_string<char, std::char_traits, std::allocator > device_path, std::cxx11::basic_string<char, std::char_traits, std::allocator > mount_point, std::__cxx11::basic_string<char, std::char_traits, std::allocator > filesystem_name, std:: cxx11::basic_string<char, std::char_traits, std::allocator > options)
System Information:
Live Environment: The issue is occurring while using a live USB environment for the installation. Partition Layout (from lsblk) NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 2.7G 1 loop /usr/lib/live/mount/rootfs/filesystem.squashfs /run/live/rootfs/filesystem.squashfs sda 8:0 1 57.3G 0 disk └─sda1 8:1 1 2.8G 0 part /usr/lib/live/mount/medium /run/live/medium sdb 8:16 1 14.6G 0 disk └─sdb1 8:17 1 14.6G 0 part /media/van/ESD-USB nvme0n1 259:0 0 238.5G 0 disk ├─nvme0n1p1 │ 259:2 0 300M 0 part /tmp/calamares-root-ye7qfh7j/boot/efi └─nvme0n1p2 259:3 0 238.2G 0 part /tmp/calamares-root-ye7qfh7j Steps Taken:
I tried running the installer, but it failed with the error mentioned. Manually checked and mounted partitions. Attempted to use fsck and mount manually, no issues there. Possible Cause: The issue seems to be related to a mismatch between the Python function signature and the expected C++ signature in the Calamares mount function, which causes it to fail when trying to mount the partitions. Could someone help resolve this issue or provide guidance on how to bypass or fix the partition mount error?