No init 5

Hi i have build some appliances and none of them can run in init 5 mode and when i try sax2 an error message comes out any suggestion??

I tried adding different packages with no result.
The graphical interface does not run neither in testdrive mode nor in a live CD

On Wed, 17 Mar 2010 13:36:02 +0000, mpbm23 wrote:

> Hi i have build some appliances and none of them can run in init 5 mode
> and when i try sax2 an error message comes out any suggestion??
>
> I tried adding different packages with no result. The graphical
> interface does not run neither in testdrive mode nor in a live CD
> 679
>
>
> ±---------------------------------------------------------------------+
> |Filename: print.jpg |
> |Download: http://forums.opensuse.org/attachment.php?attachmentid=679 |
> ±---------------------------------------------------------------------+

I’ve seen this from time to time when building up from a minimal install

  • which pattern are you starting with for the build?

Jim


Jim Henderson
openSUSE Forums Administrator

I tried the 32bit openSuse11.2 ,KDE and minimal X

On Wed, 17 Mar 2010 18:16:02 +0000, mpbm23 wrote:

> hendersj;2138202 Wrote:
>>
>> I’ve seen this from time to time when building up from a minimal
>> install
>> - which pattern are you starting with for the build?
>>
>> Jim
>>
> I tried the 32bit openSuse11.2 ,KDE and minimal X

Does it run in Testdrive?

I’m wondering if it may be hardware detection related.

Jim


Jim Henderson
openSUSE Forums Administrator

no it does not run on testdrive

On Wed, 17 Mar 2010 21:36:01 +0000, mpbm23 wrote:

> no it does not run on testdrive

What is the package/pattern selection you’ve made? I’ll try duping it
and see if I can reproduce your results.

Jim


Jim Henderson
openSUSE Forums Administrator

this is my minimal X appliance Sign in – SUSE Studio
and this is a KDE Sign in – SUSE Studio

On Thu, 18 Mar 2010 08:16:02 +0000, mpbm23 wrote:

> this is my minimal X appliance ‘Sign in – SUSE Studio’
> (http://susestudio.com/appliance/edit/169894) and this is a KDE ‘Sign in
> – SUSE Studio’ (http://susestudio.com/appliance/edit/169839)

Unfortunately, I’m not an admin of the SUSE Studio site, just another
user - so to duplicate your setup, I need to know what patterns/packages
were used in your appliance rather than having a link to the existing
appliance.

Jim


Jim Henderson
openSUSE Forums Administrator

I used just the standard packages provided by the patterns KDE,MinimalX,I didnt install anything else.I also tried the Gnome pattern and it had the same problem

On Sat, 20 Mar 2010 07:06:04 +0000, mpbm23 wrote:

> I used just the standard packages provided by the patterns
> KDE,MinimalX,I didnt install anything else.I also tried the Gnome
> pattern and it had the same problem

I’ve just installed 11.2 32-bit in testdrive with KDE4, and it seems to
be working here OK. I just went with the default KDE4 setup, didn’t add
or remove anything from it.

Let me see if I can ping someone in the Studio team to have a look at
your builds to see what’s up with them.

Jim


Jim Henderson
openSUSE Forums Administrator

The reason for the problem seems to be a bit tricky: One of the packages in the uploaded tar ball is providing libfreetype2.so.6:

rpm -qp --provides RPMS/userland/openoffice.org-userland-1.0-0.noarch.rpm

libfreetype.so.6

and it looks like there is a bug that when a tar ball containing rpms gets uploaded than the packages do not get selected but the dependencies to them checked and thus freetype2 from the x pattern unselected as it’s provided by the openoffice2 rpm.

This should only happen when the packages get actually selected and not by just uploading them.

A quick workaround is to just reselect the package freetype2 after uploading the tar ball until the bug is fixed (I filed it in bugzilla).

On a unrelated note, is it intended that the tar ball contains files beside the rpms as these get parsed as well after uploading. In case these are install files for the openoffice install I’d recommend to upload them as overlay files and not via the rpm upload interface.

On Tue, 23 Mar 2010 13:36:04 +0000, chuller wrote:

> The reason for the problem seems to be a bit tricky: One of the packages
> in the uploaded tar ball is providing libfreetype2.so.6:

Thanks for jumping in here. :slight_smile:

Jim


Jim Henderson
openSUSE Forums Administrator

it seems that the last note is in fact related as the xml description for fake-db contains the name tag for the package which is exactly the one as the package that provides freetype according to rpm. Anyway there is an issue inside studio that leads to this behavior and bugs are filed for this.