I don’t think the first thing I’m supposed to see when testing my build is penguins dancing around, but that’s what I get. Strange thing is that the About dialog of this penguin atrocity has a web link that does not resolve, and a directory to a /boot/message file, promising that it can stop this penguin madness, yet when I cd terminal into /boot and then ls terminal it to show its contents after nano said it doesn’t exist since I tried to edit it like it taunted me to, there is neither a “message” directory nor a message file to begin with. I posted a link to some screenshots. The one with the green progress bar shows the GUI screen which is practically a dead end, it doesn’t do anything after that. I’ve used up my whole hour allotted for testing the appliance in one instance, thinking it would eventually load my desktop on its own, but it never went past showing a green bar across the bottom of the screen after it filled up. So another time I tried startx (there’s a screenshot of the output), and another instance I even tried sudo gdm, but there’s no point in posting a screenshot of that because it only made a black screen forever. I also include the “system menu” screenshot which is executed after I press the Alt-F1 button on the side of the testing window. Please, help me. https://drive.google.com/folderview?id=0BzygWR1ZgugnSjduV0czdkR2aWc&usp=sharing
Edit: Oh yeah, and I tried to post this report in SuseStudio.com/forum, but no matter how many times I tried to register on the site, the code image would never work. I tried to enter the alphanumeric code in the picture tens of time, and it never accepted it, even though the characters in the images were not hard to recognize. I already signed up to susestudio.org earlier in the day with success (obviously), so I’m using this thread to file my report instead.
