# Installer crash at partition step **URL:** \ **Category:** EndeavourOS installation\ **Created:** [January 31, 2025, 4:16pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164 "2025-01-31T16:16:07Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![cih187](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/dfb087/32.png) [@cih187](https://forum.endeavouros.com/u/cih187)\ **Post date:** [January 31, 2025, 4:16pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/1 "2025-01-31T16:16:07Z")
Hi, I originally described the issue here: [Installer crash on partition - #13 by joekamprad](https://forum.endeavouros.com/t/installer-crash-on-partition/54473/13) > I removed all partitions before running the installer. When I am at the partitioning stage, I select the NVMe disk, select erase to create a SWAP partition with hibernate. The installer crashes. > It seems like there is a random chance when changing the SWAP option for the installer to crash. > > Here is the log: [https://0x0.st/88E-.txt](https://0x0.st/88E-.txt) (although I looked into it and I do not see any errors there) These debug lines appeared even when the installer ran correctly so I don’t think these are related. ```auto 08:41:35 [6]: DEBUG (Qt): getting temp failed for "/dev/nvme0n1" : No such file or directory 08:41:35 [6]: DEBUG (Qt): getting powered on time failed for "/dev/nvme0n1" : No such file or directory 08:41:35 [6]: DEBUG (Qt): getting power cycles failed for "/dev/nvme0n1" : No such file or directory ``` ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [January 31, 2025, 4:27pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/2 "2025-01-31T16:27:05Z")
Did you try creating a new gpt partition on the disk first with gparted. Then run the installer and select erase disc swap file and bootloader of choice. Edit: I am suggesting this rather than just deleting the partitions because something maybe not quite right with the main GPT partition. ---
**Author:** ![cih187](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/dfb087/32.png) [@cih187](https://forum.endeavouros.com/u/cih187)\ **Post date:** [January 31, 2025, 4:37pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/3 "2025-01-31T16:37:45Z")
I completed the installation successfully after a few tries. The issue was appearing randomly when changing the SWAP option. If I kept changing the option it would crash when selecting it, not when applying the change. As I already ran the installer, I could try to reproduce the issue, but my disk would not be unallocated. To be clear, there was not any partitions on the disk selected. And I was able to reproduce it multiple times. ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [January 31, 2025, 4:46pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/4 "2025-01-31T16:46:04Z")
If you are randomly changing the swap option and I don’t know if that was after one attempt or not it is best to restart the ISO and select what you want. If you make changes after making a setting it has to reset and sometimes it can cause it to crash. > [@cih187](#): > > To be clear, there was not any partitions on the disk selected. And I was able to reproduce it multiple times. Do you mean it was unallocated space and no GPT partition existed? What I was suggesting was to create the initial GPT partition first with gparted and then run the installer if you are having this issue. But it’s all a moot point since you already have it installed. ---
**Author:** ![cih187](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/dfb087/32.png) [@cih187](https://forum.endeavouros.com/u/cih187)\ **Post date:** [January 31, 2025, 4:58pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/5 "2025-01-31T16:58:26Z")
I am writing this because it happened multiple times when I first selected the option. Then, by trying more times, I noticed it was randomly crashing, and I guess I was not lucky the first time. The installer works great after that, and if you keep trying it will work. My understanding is, there may be a bug when querying some information that makes the installer crash. It was unallocated space. Creating the initial GPT partition might resolve the issue, but there might be something to fix in the installer to avoid users encountering this in the future. Maybe it only happens when you modify the partition using gparted before running the installer ? ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [January 31, 2025, 5:09pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/6 "2025-01-31T17:09:48Z")
I know it happens to some users but it isn’t frequent. I do a lot of installs testing and if anyone would run into this it should happen to me. It’s surprising that i haven’t worn out my disks by now. All i can say is that it’s not happened to me. That way the installer works with scripts is that sometimes like i said it has to reset and maybe it gets tripped up when doing that. It could be for a number of reasons because it is an online installer there are many factors that could possibly cause it to have a conniption. 🤷‍♂️ > [@cih187](#): > > Maybe it only happens when you modify the partition using gparted before running the installer ? I haven’t found this happening to me. The only issue i have seen is when using replace partition sometimes which i rarely use. ---
**Author:** ![cih187](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/dfb087/32.png) [@cih187](https://forum.endeavouros.com/u/cih187)\ **Post date:** [January 31, 2025, 5:14pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/7 "2025-01-31T17:14:26Z")
What kind of tools should I use to gather more information about what the installer is trying to do if I try to reproduce the issue in the future (as the log is not detailed enough to capture the information) ? ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [January 31, 2025, 5:16pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/8 "2025-01-31T17:16:15Z")
The install log is all that I know. 🤷 Edit: I’m also not that great at deciphering what I’m always looking through either. 😉 I try my best! ---
**Author:** ![cih187](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/dfb087/32.png) [@cih187](https://forum.endeavouros.com/u/cih187)\ **Post date:** [January 31, 2025, 5:56pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/9 "2025-01-31T17:56:42Z")
So I restarted the ISO, selected all default settings, and I was able to reproduce the issue. The system log from dmesg shows the following: ```auto [237.324273] calamares[2655]: segfault at 10000000000 ip 00007c9f332a12a6 sp 00007fffe8d58a08 error 4 in libQt6Gui.so.6.7.2[4a12a6,7c9f32ed9000+627000] likely on CPU 7 (core 3, socket 0) [237.324283] Code: 4c 39 47 08 75 35 48 8b 76 08 48 85 f6 74 2c 48 8b 76 08 3b 46 40 7d 23 8b 7e 44 39 f9 7d 1c 0f af c7 48 8b 56 30 01 c8 48 98 <48> 8b 14 c2 48 89 d0 c3 66 90 48 8b 97 08 01 00 00 48 89 d0 c3 90 [237.324326] audit: type=1701 audit(1738345378.616:174): auid=1000 uid=0 gid=0 ses=2 pid=2655 comm="calamares" exe="/usr/bin/calamares" sig=11 res=1 ``` I tried to look at strace too: ```auto statx(AT_FDCWD, "/root/.config/kdeglobals", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=3421, ...}) = 0 statx(AT_FDCWD, "/root/.config/kdeglobals", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=3421, ...}) = 0 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10001006b} --- +++ killed by SIGSEGV (core dumped) +++ ``` if someone needs extra information, I can easily reproduce the issue (at least on my machine 🙂 ) ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [January 31, 2025, 6:41pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/10 "2025-01-31T18:41:30Z")
It will have to be looked at by the devs. 😉 ---
**Author:** ![cih187](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/c/dfb087/32.png) [@cih187](https://forum.endeavouros.com/u/cih187)\ **Post date:** [February 1, 2025, 5:51pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/11 "2025-02-01T17:51:40Z")
After looking through the github issues of calamares, I found an issue that looks like mine: [https://github.com/calamares/calamares/issues/2405](https://github.com/calamares/calamares/issues/2405) except I am not sure it fixes exactly the same thing. I guess we can wait until [https://github.com/calamares/calamares/pull/2414/commits/3e9eabe9df8a8412d0cccd583001440a2075bb61](https://github.com/calamares/calamares/pull/2414/commits/3e9eabe9df8a8412d0cccd583001440a2075bb61) gets into the endeavouros fork. ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [February 1, 2025, 7:32pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/12 "2025-02-01T19:32:37Z")
> > > A SEGV may occur when collecting boot loader information. > > 14:33:33 \[2\]: W…ARNING (Qt): beginResetModel called on BootLoaderModel(0x5555565c5b70) without calling endResetModel first > 14:33:33 \[2\]: WARNING (Qt): endResetModel called on BootLoaderModel(0x5555565c5b70) without calling beginResetModel first > 14:33:33 \[2\]: WARNING (Qt): beginResetModel called on BootLoaderModel(0x5555565c5b70) without calling endResetModel first > 14:33:33 \[2\]: WARNING (Qt): endResetModel called on BootLoaderModel(0x5555565c5b70) without calling beginResetModel first > > Thread 1 "calamares" received signal SIGSEGV, Segmentation fault. > 0x00007ffff60c8b65 in ?? () from /usr/lib/libQt6Gui.so.6 > > > \*\*Describe the bug\*\* > When updating boot loader information or partition information, multiple threads are started, and SEGV occurs in some cases. From the log, it can be inferred that mutex is not working properly. > > \*\*To Reproduce\*\* > Steps to reproduce the behavior: > 1. sudo gdb --args calamares -D8 -T --debug > 2. catch signal SIGSEGV > 3. run > 4. next and next and next... > 5. Select Manual partitioning and click next > 6. After the screen changes, a dialog box will appear and the partition information will be scanned. > 7. SEGV may occur > > \*\*Expected behavior\*\* > After collecting partition information, no SEGV occurs and a list of partition information is displayed. > > \*\*Screenshots and Logs\*\* > 14:33:33 \[2\]: WARNING (Qt): beginResetModel called on BootLoaderModel(0x5555565c5b70) without calling endResetModel first > 14:33:33 \[2\]: WARNING (Qt): endResetModel called on BootLoaderModel(0x5555565c5b70) without calling beginResetModel first > 14:33:33 \[2\]: WARNING (Qt): beginResetModel called on BootLoaderModel(0x5555565c5b70) without calling endResetModel first > 14:33:33 \[2\]: WARNING (Qt): endResetModel called on BootLoaderModel(0x5555565c5b70) without calling beginResetModel first > > Thread 1 "calamares" received signal SIGSEGV, Segmentation fault. > 0x00007ffff60c8b65 in ?? () from /usr/lib/libQt6Gui.so.6 > > \*\*Additional context\*\* > I have observed this occur with some frequency when a Chrome OS (brunch) partition is present on /dev/sdc. ---
**Author:** ![9tgsw](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/9/a8b319/32.png) [@9tgsw](https://forum.endeavouros.com/u/9tgsw)\ **Post date:** [October 6, 2026, 6:06pm UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/13 "2026-10-06T18:06:26Z")
Hello! I’m new here so I’m not sure if this is a helpful addition to the discussion, but I had the installer crash on me today when I was using the keyboard to cycle through options for “swap” in the “Partitions” section of the installer. Searching found me this bug report which seems related. I’m able to restart the installer so this isn’t stopping me from progressing, but I figured I’d add this experience to the discussion. ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [October 7, 2026, 4:54am UTC](https://forum.endeavouros.com/t/installer-crash-at-partition-step/67164/14 "2026-10-07T04:54:46Z")
2 years later 👋