[Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Erick Brunzell]

We're 99% of the way there. Setting auto-login during install still
doesn't work though so I filed bug 1571415.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to sddm in Ubuntu.
https://bugs.launchpad.net/bugs/1547297

Title:
  No auto login in Ubuntu GNOME Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1560356] Re: ubiquity will not start on Xenial liveUSB

[Erick Brunzell]

The Ubuntu Xenial 20160321 amd64 image was OK and I notice this in the
ubiquity changelog:

ubiquity (2.21.50) xenial; urgency=medium

  * Adjust code for change of fwupdate-%arch-signed renaming to fwupdate-signed
  * Automatic update of included source packages: hw-detect
1.114ubuntu4.

 -- Mario Limonciello   Mon, 21 Mar 2016
19:23:36 +

** Tags added: ubuntu-gnome

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1560356

Title:
  ubiquity will not start on Xenial liveUSB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560356/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1560356] Re: ubiquity will not start on Xenial liveUSB

[Erick Brunzell]

Testing Ubuntu Xenial 20160322 amd64 I get the following behavior:

Boot live image, press enter to display advanced menu and select check
disc for defects. Test completes successfully.

Press enter to let image reboot and do nothing expecting the standard
boot menu to appear, but the boot menu never appears. Instead a window
pops up warning that "The installer encountered an unrecoverable error.
A desktop session will now run so that you may investigate the problem
or try installing again". (image attached)

Click on OK and the live DE appears. Try launching ubiquity and nothing
happens.

Reboot and thsi time enter the advanced boot menu again. Then select
install from the advanced boot menu and the same warning dialog appears.



** Attachment added: "ubi_crash.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560356/+attachment/4607467/+files/ubi_crash.JPG

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1560356

Title:
  ubiquity will not start on Xenial liveUSB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560356/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

I never could get Vivid's usb-creator to create a working live USB,
always ending with the error Failed to install the bootloader, so I
filed bug #1446646. You might want to compare logs to see if the errors
look the same. I've just been too busy to deal with it any further - for
all intents and purposes I've just given up on usb-creator ever working
properly.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

I've had no problem with Unetbootin, only usb-creator*.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

Less than 24 hours to go before Utopic is released :^(

Is this not a regression to bug #1112878?

Should we not at least mention it in the release notes?

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

Thanks Colin.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

Here is the log from my Trusty that most recently made bad Utopic live
USB's.

I'll have to study how to create a live USB with dd, something I should
learn anyway.

** Attachment added: usb-creator.log
   
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1325801/+attachment/4215456/+files/usb-creator.log

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

Using dd to create a live USB works just fine in that same Trusty that
spits out bad live USB's using usb-creator.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

[Erick Brunzell]

An Ubuntu Utopic 20140922 i386 live USB created in Precise using Startup
Disk Creator also fails with the error reported here, so I'd have to
amend that last statement to say, Utopic live USB's created with the
Trusty or Precise versions of 'usb-creator-gtk' fail to boot and display
the error reported in this bug.

Sort of leaves me wondering if we need to fix the image or if we should
do separate SRU's for both Precise and Trusty 'usb-creator-gtk'???

It would be nice if someone could try creating a Utopic live USB in
Windows (probably both Win 7 and Win 8) following the official USB
creation methods linked to on the main download page. I have no Windows
machines to test with.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1325801

Title:
  failed to boot from USB disk with error: gfxboot.c32: not a COM32R
  Image boot:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1080701] Re: After 'Preparing to install Ubuntu' screen, raring installation hangs

[Erick Brunzell]

@ Hugh Kernohan,

While the symptoms may seem similar I believe your's is a different bug,
so I recommend filing a new bug report.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1080701

Title:
  After 'Preparing to install Ubuntu' screen, raring installation hangs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1080701/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1080701] Re: After 'Preparing to install Ubuntu' screen, raring installation hangs

[Erick Brunzell]

I may, OR MAY NOT, be onto something here. But before I proceed let me
point out that I'm not shouting when I use all caps .. I'm just
stressing a point which may or may not be important. I've spent several
hours testing this with very little rest so cut me some slack :^)

You will have to read to the end to see what I suspect the problem might
be!!!

I'm totally ignorant when it comes to using VM's other than using
testdrive w/virtualbox in a simple live test, so I use mostly bare
metal. In this case I'm using:

VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
1GB DDR2 RAM

It's not adequate to run Ubuntu itself but it will run both Lubuntu and
Xubuntu. I prefer Lubuntu.

I tried yesterday with an Lubuntu i386 20130418 Live DVD creating a
situation where I thought this bug would manifest:

I used only an 80GB IDE drive and created 3 primary partitions with one
logical partition for swap. I then used something else (aka: manual
partitioning) to install three Lubuntu's. After doing so I plugged in a
USB flash drive that I use for transferring data - that drive MUST NOT
be a bootable drive!

Then I rebooted to try another installation (whether it be to replace an
existing install or resize) and it appeared to hang so I thought, OK
this is easy to reproduce. At that point I took a prolonged toilet
break - maybe 10 to 15 minutes - but when I came back the busy-wheel
had stopped spinning so I decided I'd just been impatient.

NOW, we move onto todays testing. I was very methodical:

Step #1: With only the 80GB drive connected I performed an entire disc
install using an Lubuntu i386 20130418 Live DVD. No problem.

Step #2: I rebooted the same DVD and then performed  an auto-resize test
choosing a new partition size of about 15GB, again no problem.

Step #3: I rebooted the same DVD and used Gparted to shrink sda1, create
2 new primary partitions, each about 15GB, and free space of about 15GB.
I then started a new “install alongside” test, but since I now had
adequate free space the Continue button showed Install now as expected.
Once again this installation completed with no problems. So I now had:

lance@lance-VIA-desktop:~$ sudo parted -l
[sudo] password for lance: 
Model: ATA WDC WD800BB-63JK (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType  File system Flags
 1  1049kB  15.8GB  15.7GB  primary   ext4boot -- entire disc 
install
 3  15.8GB  31.5GB  15.7GB  primary   ext4-- not used 
yet
 4  31.5GB  47.2GB  15.7GB  primary   ext4-- not used 
yet
 2  47.2GB  80.0GB  32.8GB  extended
 7  47.2GB  64.0GB  16.8GB  logical   ext4  -- free 
space test
 6  64.0GB  79.0GB  15.0GB  logical   ext4  -- 
auto-resize test
 5  79.0GB  80.0GB  1005MB  logical   linux-swap(v1)

It shouldn’t matter but just to be thorough I’ll mention that sda7 in
charge of booting ATM since it was the last installed.

Step #4: I shut down the computer and connected a 30GB drive as “slave
that I’d used yesterday with the same DVD to perform an entire disc
install. And I check in BIOS that the 80GB is still the boot drive
before proceeding. I then run “update-grub”:

lance@lance-VIA-desktop:~$ sudo update-grub
[sudo] password for lance: 
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.8.0-18-generic
Found initrd image: /boot/initrd.img-3.8.0-18-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu Raring Ringtail (development branch) (13.04) on /dev/sda1
Found Ubuntu Raring Ringtail (development branch) (13.04) on /dev/sda6
Found Ubuntu Raring Ringtail (development branch) (13.04) on /dev/sdb1
done

NOW IT GETS INTERESTING, and it may coincide with yesterdays prolonged
potty break.

When I tried the next install, I was hoping to install manually to
either sda3 or sda4 but it again appeared to hang. So once again I
took a prolonged break, this time to feed the dogs and make a pot of
coffee - like I need more caffeine ;^/

Once again after a prolonged break (maybe 15 to 20 minutes) I come back
and find that the spinning wheel has stopped spinning.

But now, being the dummy that I am, I notice for the first time that
Raring includes a System column in ubiquity. That was not present in
Quantal and I tried booting Quantal to try an install which appeared
like it would work OK QUICKLY, but I didn't complete it.

So let's think for a moment. Did adding the system ID thing to
ubiquity contribute to this bug??

Maybe whatever process is identifying existing system info is simply
slowing the process so much that the user thinks things are hung when
in fact that process is still reading.

Does that make any sense at all?

-- 
You received this 

[Bug 436936] Re: gdm upstart job checks /proc/cmdline for single user mode, won't start on post-boot runlevel change

[Erick Brunzell]

Ah, disregard that last comment. I ended up here due to James Hunt's
request for testing at bug 735805 and I'd not taken time to read the
history of this bug.

Regarding Natty only,  using the 'gdm.conf' provided by James Hunt in
post #20 telinit 2 from a recovery shell does start gdm. Using the
officially packaged gdm.conf (currently gdm (2.32.0-0ubuntu12) natty)
telinit 2 from a recovery shell does NOT start gdm.

Indeed selecting the Resume button does not work with either.

Sorry for my confusion.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/436936

Title:
  gdm upstart job checks /proc/cmdline for single user mode, won't start
  on post-boot runlevel change

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs