Impossible to login in live-cd created

[gmstyle]

Hi guys,
thanks a lot for your work!There is a problem with Customizer 4.1.0 on Ubuntu 14.04.1. it is impossible to login with the iso created (starting from ubuntu-mini-remix 14.04.1 iso). any solution?

gabriele@gabriele-Aspire-5810T:$ uname -r
3.13.0-35-generic
gabriele@gabriele-Aspire-5810T:$

thanks a lot again

[fluxer]

I will have to investigate the issue as it is something I was not aware of. Will look into it soon.

[fluxer]

Just tested with UMR i386 14.04.1 - no issues after rebuild with and without
changes. I can not test the amd64 ISOs, which ISO are you trying to customize
and what changes did you made?

[gmstyle]

@fluxer i try with ubuntu 14.04 (SalentOS 14.04) 32bit and the only changes are made by dist-upgrade command and i removed old kernel leaving the 3.13.0-35-generic one with headers. Now i'm building again the iso with the same changes and when finish i will update you if it works or not.

[fluxer]

That's exactly what I hoped to hear - first you report issue against ubuntu-mini-remix 14.04.1
and now you are going to test this against SalentOS 14.04 (never heard of it). If it does
successed you may prove that there is something wrong with UMR but I can not be sure
if that will be the case. SalentOS may have some changes under the hood that affect the
customization process.

Unless you have the same issue with SalentOS and nobody else can replicate the issue I will
have to close it but it will stay open for a while, let's see what happens.

[gmstyle]

@fluxer SalentOS is simply an Ubuntu based distro that i develop :) but it not have changes under the hood. the only diffrences between ubuntu are under the desktop environement that is openbox and not unity or others. Live user is salentos like the host. But now i'm waiting to finish the iso rebuild ;)

[fluxer]

Good to know. Next time, please, mention this in advance.

[gmstyle]

rebuild completed but same issue. impossible to login. i made a screenshot

i also tried to leave user and host "ubuntu" but same problem

[fluxer]

The ISO structure/tree of UMR is quite different from that of Linux Mint for
an example. It's burdens should be carried or it should be fixed in UMR
itself, I'm keen on the second. Unless someone steps in I would rather not
recommend UMR anymore (see issue #70). It has bitten me before a few
times in the past and I'm getting sick of it.

[gmstyle]

1st Test:
Starting from SalentOS 14.04 (ubuntu 14.04) iso and only upgrading system with apt-get upgrade the iso was built and it login normally (user and host "salentos"). Kernel is 3.13.0-24 generic and was not upgraded.
Repeat, login in live mode works fine.

2nd Test:
Rebuilding iso from the same SalentOS 14.04 (ubuntu 14.04) iso. NO changes respect the 1st test but simply doing rebuild iso button.
Login failed and error like in the screenshot up.

1-the issue could be random?

[fluxer]

I doubt that the issue is random, usually such issues appear when kernel upgrade is made
in chroot. Something is wrong with this capser-thingy and I just can't figure it out.

@fluxer
I do agree that this issue might not be random. Just to recall, we do have similar issue filed under #54 ("Unable to login into the created Live CD/DVD ISO image").

In my experience, this "unable to login" issue is caused by external application i.e. Dropbox that is installed while in chroot.

Which may suggests that, it is not necessarily kernel issue and may have other root cause.

@fluxer
I will try to reproduce this issue soon on my side as well.

Based on above conversation, I should use UMR 14.04 ISO image file (albeit 32 bit for my side) with Customizer 4.1 on 14.04 host system. Then I shall run dist-upgrade command and try rebuild it (I will try without Desktop Environment to save rebuild/testing time).

Am I missing anything important?

[fluxer]

@clearkimura

Which may suggests that, it is not necessarily kernel issue and may have other root cause.

You may be right.

Am I missing anything important?

No, you are not missing anything.

@gmstyle
Can we have the packages list from the chroot filesystem? It can help to reproduce
the issue by not just dist-upgrading but also installing the same packages as you.