xserver failing to start from base server image plus gnome pattern (x86_64)

[dsmith27]

Hi,

I've built a new appliance starting with the base x86_64 server (text only), and added the gnome "pattern". I started out trying a live cd build, which stalls during boot (after the initial splash menu), both from the online "Testdrive", and from VirtualBox running the iso locally. IIRC, the errors seemed to be firewall related.

Today I tried removing the firewall, adding grub (since I was not going to be testing the livecd to begin with), and checking that basic stuff such as gdm and xserver are both present. I built a new image and ran the online "Testdrive" (from the disk image, not live cd), however it boots into console (though I selected Runlevel 5 Graphical login).

I can log in from the console, but I can't start xserver.

I have uploaded a screen shot of my Testdrive console output to:
http://205.207.168.174/appliancescreen.gif

Thanks

[James T.]

Hi there,

On 12/15/2011 04:32 PM, dsmith27 wrote:

> I've built a new appliance starting with the base x86_64 server (text only),
> and added the gnome "pattern". I started out trying a live cd build, which
> stalls during boot (after the initial splash menu), both from the online
> "Testdrive", and from VirtualBox running the iso locally. IIRC, the errors
> seemed to be firewall related.
>
> Today I tried removing the firewall, adding grub (since I was not going to
> be testing the livecd to begin with), and checking that basic stuff such as
> gdm and xserver are both present. I built a new image and ran the online
> "Testdrive" (from the disk image, not live cd), however it boots into
> console (though I selected Runlevel 5 Graphical login).
>
> I can log in from the console, but I can't start xserver.
>
> I have uploaded a screen shot of my Testdrive console output to:
> http://205.207.168.174/appliancescreen.gif

You're probably missing some other dependencies that the GNOME pattern
failed to pull in, especially since Studio only pulls in the required
packages by default and not the recommended ones to keep things small
(unlike YaST).

It's easiest to start with the GNOME template rather than trying get
from JeOS, unless you are familiar with the details.

Cheers,
James T.

[dsmith27]

Hi James,

Thanks for responding.

I kind of appreciate the rationale you describe: to keep it small, indeed that's why I'm interested in Studio.

Even so, can it not be assumed that if one is installing a desktop "pattern" (however minimal), one does so with the expectation to be able to boot into it?

Just to clarify: does selecting a "pattern" add software packages to the build, or only categories to the package manager in Yast2? To me, it implies the former, but that has not been my experience.

Thanks

 

David Smith

[hidden email]
www.designartcraft.com

---

From: James Tan <[hidden email]>
To: dsmith27 <[hidden email]>
Cc: [hidden email]
Sent: Friday, December 16, 2011 10:16:27 AM
Subject: Re: [studio-users] xserver failing to start from base server image plus gnome pattern (x86_64)

Hi there,

On 12/15/2011 04:32 PM, dsmith27 wrote:

> I've built a new appliance starting with the base x86_64 server (text only),
> and added the gnome "pattern". I started out trying a live cd build, which
> stalls during boot (after the initial splash menu), both from the online
> "Testdrive", and from VirtualBox running the iso locally. IIRC, the errors
> seemed to be firewall related.
>
> Today I tried removing the firewall, adding grub (since I was not going to
> be testing the livecd to begin with), and checking that basic stuff such as
> gdm and xserver are both present. I built a new image and ran the online
> "Testdrive" (from the disk image, not live cd), however it boots into
> console (though I selected Runlevel 5 Graphical login).
>
> I can log in from the console, but I can't start xserver.
>
> I have uploaded a screen shot of my Testdrive console output to:
> http://205.207.168.174/appliancescreen.gif

You're probably missing some other dependencies that the GNOME pattern failed to pull in, especially since Studio only pulls in the required packages by default and not the recommended ones to keep things small (unlike YaST).

It's easiest to start with the GNOME template rather than trying get from JeOS, unless you are familiar with the details.

Cheers,
James T.

[James T.]

Hi David,

On 12/16/2011 04:28 PM, David Smith wrote:

I kind of appreciate the rationale you describe: to keep it small, indeed that's why I'm interested in Studio.

Even so, can it not be assumed that if one is installing a desktop "pattern" (however minimal), one does so with the expectation to be able to boot into it?

Yes you're right, this is unexpected and often confusing. We are looking at ways to improve this or at least clearly document it without cluttering the user interface.

Just to clarify: does selecting a "pattern" add software packages to the build, or only categories to the package manager in Yast2? To me, it implies the former, but that has not been my experience.

Selecting a pattern in Studio will only include all the "included" or "required" packages, as defined by the pattern. Due to the way patterns are defined, you sometimes also want to include the "recommended" packages as well. To do this, you need to click the "add all" button in the pattern pop-up in the "Recommended software" section, eg: http://imagebin.org/index.php?mode=image&id=188842.

HTH,
James T.