Hi new here, elementary installer consistently crashing at start when doing fresh installs #305
Comments
|
|
|
I had issues getting the installer to launch from the dock icon, so I captured the StdOut and StdErr. The errors look similar to the above for CapturedSomething about the way I mounted the disk I'm trying to install to (via recovery instructions) and the elementary installer resulted in Rebooting to the ISO allowed me to run the installer -- continually clicking 'WAIT' when propted to kill the process |
|
installer fails after very tough setup for dual boot. Will install as only OS on the disk. This install setup is not ready for prime time. Neither is the basic OS. Can unzip a standard zip file with the installed File Roller. Many other stupid little issues. Attempted installations have been a total waste of time. Why is the file system totally different from anything real? I like the look and feel, but there is a roadblock everywhere. |
|
When will there be a new iso with install problems fixed? |
|
I wanted to try fix it myself, quickly realized that wasn't going to work, I know nothing about how PopOS handles these installers. But no underlying issue which is a bit sad: like going to the car dealership to buy a car and the salesman says: "Oh but I drive" and then he crashes at the first curb... Anyways, nothing related to comments here: just wanted to see if the installer can be fixed ? I even sanity checked myself and installed it on a 1500$ DELL and same results. |
|
By the way @CBroz1 I had the same issues, did you have a previous install with Encryption activated ? I destroyed a HDD SATA drive this way. I think this should be done post base install. 100%. At least other OSes propose this feature but definitely not during a critical set up step. (Like Vaults in KDE) But encrypting your drive while the install can still fail seems risky to say the least xD |
I don't think so, no |
|
I installed elementary os on the whole disk, which worked. I then tried to
shrink the partition to install Fedora. Could not do anything with the
elementary partition. Some weird file system and the partition would not
shrink. Encryption was not involved.
There are other problems with elementary os 8 and it should not be
presented as ready for wide use. Some apps would not install and it will
not install as the second OS on a drive. I like the desktop, but it is not
worth the hassle. Hopefully it will get fixed. I thought it was Ubuntu
underneath.
Bob McConnell
***@***.***
mobile: +1 425 999 6755
WhatsApp: +1 425 999 6755
Italian mobile: +39 366 118 7979
…On Thu, Jan 16, 2025 at 03:36 HADEON ***@***.***> wrote:
By the way @CBroz1 <https://github.com/CBroz1> I had the same issues, did
you have a previous install with Encryption activated ?
I destroyed a HDD SATA drive this way. I think this should be done post
base install. 100%.
At least other OSes propose this feature but definitely not during a
critical set up step.
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLAJV6Z7SPFXEYXMQK24HD2K6KSBAVCNFSM6AAAAABVDWUOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJVGI4DKNZVGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@CBroz1 The encrypt button is misleading, it feels like you need to encrypt so you might have clicked it by mistake initially. Anyways I had the same errors as you because fot aht, hence why it might be the culprit Device /dev/sde2 is not a valid LUKS device. From your logs |
|
Could be that I saw a very strange file system and could not shrink that
partition because it was encrypted.
Bob McConnell
***@***.***
US mobile: +1 425 999 6755
WhatsApp: +1 425 999 6755
…On Thu, Jan 16, 2025 at 8:31 AM HADEON ***@***.***> wrote:
@CBroz1 <https://github.com/CBroz1> The encrypt button is misleading, it
feels like you need to encrypt so you might have clicked it by mistake
initially. Anyways I had the same errors as you because fot aht, hence why
it might be the culprit
Device /dev/sde2 is not a valid LUKS device.
Device /dev/sdd2 is not a valid LUKS device.
Device /dev/sdc1 is not a valid LUKS device.
From your logs
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLAJV4D5XINLJ3RYUB7ZWD2K7NENAVCNFSM6AAAAABVDWUOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWGE4DCMJXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
The NVME drive was/is my pop installation. At least one of the attached drives is a windows boot, another is ext4, another is hfsplus. My storage solutions are an inconsistent mess of old drives |
|
I had trouble with an one year old system with a single NVMe drive.
Bob McConnell
***@***.***
US mobile: +1 425 999 6755
WhatsApp: +1 425 999 6755
…On Thu, Jan 16, 2025 at 8:45 AM Chris Broz ***@***.***> wrote:
Device /dev/sde2 is not a valid LUKS device.
Device /dev/sdd2 is not a valid LUKS device.
Device /dev/sdc1 is not a valid LUKS device.
The NVME drive was/is my pop installation. At least one of the attached
drives is a windows boot, another is ext4, another is hfsplus. My storage
solutions are an inconsistent mess of old drives
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLAJV4QZGPNWBIOITCIOP32K7O3RAVCNFSM6AAAAABVDWUOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWGIYTIOBSGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Again I think the encryption button is misleading it feels like you need to encrypt (but at a critical point in OS install) seems risky to me. |
|
I have been commenting on installing elementary os 8. It finally just
installed almost normally. (different PC, preset partitions). I am sure
that in a previous install, it locked up my SSD and I could not not do
anything with the drive. I had to just install Fedora on the whole drive,
then work from there.
Bob McConnell
***@***.***
US mobile: +1 425 999 6755
WhatsApp: +1 425 999 6755
…On Fri, Jan 17, 2025 at 4:37 AM HADEON ***@***.***> wrote:
Again I think the encryption button is misleading it feels like you need
to encrypt (but at a critical point in OS install) seems risky to me.
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLAJV4QMUG5JH3NQPMOFRT2LD2PLAVCNFSM6AAAAABVDWUOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJYGI3TINZYGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Been loving to play around in PopOS and and I now install it everywhere.... Actually 3 computers......
I did consistently find the original installer to crash (perhaps because other libraries aren't fully loaded yet?
I did some digging, can't really tell how useful
pop-os@pop-os:~$ io.elementary.installer
(io.elementary.installer:2786): GLib-GObject-CRITICAL **: 22:26:01.430: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(io.elementary.installer:2786): GLib-CRITICAL **: 22:26:02.577: g_utf8_collate: assertion 'str2 != NULL' failed
(io.elementary.installer:2786): GLib-CRITICAL **: 22:26:02.577: g_utf8_collate: assertion 'str2 != NULL' failed
(io.elementary.installer:2786): GLib-CRITICAL **: 22:26:02.577: g_utf8_collate: assertion 'str2 != NULL' failed
(io.elementary.installer:2786): GLib-CRITICAL **: 22:26:02.577: g_utf8_collate: assertion 'str2 != NULL' failed
(io.elementary.installer:2786): GLib-CRITICAL **: 22:26:02.577: g_utf8_collate: assertion 'str2 != NULL' failed
(io.elementary.installer:2786): GLib-CRITICAL **: 22:26:02.577: g_utf8_collate: assertion 'str2 != NULL' failed
Found OS boot entries
** (io.elementary.installer:2786): CRITICAL **: 22:26:05.135: installer_language_view_timeout: assertion 'self != NULL' failed
(io.elementary.installer:2786): GLib-GObject-CRITICAL **: 22:26:05.135: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ntary.installer
At first i thought it was this X-GNOME-Autostart-Delay=3 to fix just increase, or the translations not being fully loaded
But then I gave up
I also tried to maker a wrapper script to would just delay opening it for 30 seconds and then I got confused with ISO files 🥏
Distribution (run
cat /etc/os-release):Latest Intel Release
Related Application and/or Package Version (run
apt policy $PACKAGE NAME):No packages fresh installs
Issue/Bug Description:
Steps to reproduce (if you know):
Expected behavior:
Other Notes:
The text was updated successfully, but these errors were encountered: