I am just testing the SuSE studio service and it is really a great tool.
During my tests, i encountered the following issues (bugs ?) :
1 - When selecting icewm with autostart programs, the programs are never launched. The .icewm/xstartup file is created but never execute. It seems related to the fact that the .xinitrc file calls icewmbg instead of icewm-session
2 - When using the configuration on my local host with KIWI, the bootsplash are never displayed : instead grub shows an error message and fallback to text. I have no clue on what happens here, as the custom theme and pictures are present in /etc/bootsplash and so on. Any idea ?
On Mon, 27 Sep 2010 20:36:04 +0000, inpixal wrote:
> I am just testing the SuSE studio service and it is really a great tool.
>
> During my tests, i encountered the following issues (bugs ?) :
>
> 1 - When selecting icewm with autostart programs, the programs are never
> launched. The .icewm/xstartup file is created but never execute. It
> seems related to the fact that the .xinitrc file calls icewmbg instead
> of icewm-session
I’ve run into that myself as well - what I did to work around it was
modify the .xinitrc file to run icewm-session, rename the file to another
name, and then in the post-build script have it copy the
modified .xinitrc file over the one generated by the build file.
That seems to have worked fine for my uses.
> 2 - When using the configuration on my local host with KIWI, the
> bootsplash are never displayed : instead grub shows an error message and
> fallback to text. I have no clue on what happens here, as the custom
> theme and pictures are present in /etc/bootsplash and so on. Any idea ?
1 - That’s exactly what id did at the end ! Works perfectly now, even if not 100% satisfactory.
2 - “gfxboot error” or something like that. I guess that something is missing in the config.xml file somewhere, i tried notably to add boot-theme parameter, but strictly no effect. I think this issue is easy to reproduce :
On Tue, 28 Sep 2010 07:06:02 +0000, inpixal wrote:
> 1 - That’s exactly what id did at the end ! Works perfectly now, even
> if not 100% satisfactory.
Good to hear.
> 2 - “gfxboot error” or something like that. I guess that something is
> missing in the config.xml file somewhere, i tried notably to add
> boot-theme parameter, but strictly no effect. I think this issue is easy
> to reproduce :
> - Create an appliance
> - customize its logo/background
> - Download the kiwi package
> - Rebuild it with KIWI and test it …
It sounds like either the video mode isn’t being set properly or the
framebuffer device isn’t being used for some reason. I don’t know a lot
about Kiwi myself, so hopefully someone else can jump in and suggest a
course of action.
! Works perfectly now, even if not 100% satisfactory.