On 09.11.2011 06:36, Brian K. White wrote:
On 11/8/2011 11:23 PM, Ken Schneider - openSUSE wrote:
On 11/08/2011 11:10 PM, Brian K. White pecked at the keyboard and wrote:
On 11/8/2011 3:33 AM, Andreas Jaeger wrote:
On Tuesday, November 08, 2011 01:38:23 Felix Miata wrote:
Not quite that bad, but way too many for an RC2.
Many KDE base packages apparently depend on bootsplash, many more than in previous KDE releases, which, along with splashy, I taboo on every install.
Grub failed to finish installing. I booted 11.4 and finished it myself with the Grub shell. Menu.lst had two copies of the default stanza, non-identical, besides a useless HD stanza and two failsafes.
Startx as root failed even after fixing permissions.local and doing 'SuSEconfig --module permissions'. How it failed I couldn't tell. It appeared the default X session was icewm, and it gave some wacko lack of space error, then shut down after I clicked OK, the only thing on the screen to click.
AllowRootLogin=true in kdmrc was apparently ignored (once it could be found squirreled away somewhere in the /usr rats nest instead of logically where config files belong in /etc), so getting into KDE via runlevel 5 was initially impossible, since I create no users on test systems, and even when not test systems I only create users after base installation is complete in order to assign user and group IDs appropriately to match all the other installed distros on the system.
Too many failed deps to remember, most probably based upon taboo of *kde*branding-openSUSE and *splash*.
So, you're doing something outside the normal way. Please fix it yourself. Fixes to packages are welcome but I doubt anybody will help debugging all this,
Typically unhelpful suse answer of the last few years.
Requiring those splash programs without some clear and sure way to ensure that they never try to touch the video hardware is broken.
The safe mode boot options are not the answer for this either. It's already too late to even select them by the time gfxboot has killed the console or worse.
It's like this: if you want to say that it's the users responsibility to fix opensuse bugs and develop opensuse enhancements, then why should the user use opensuse in the first place?
Brian,
You just do not get it! openSuSE is provided with a specified set of packages that need to be from the "official repos" _only_ AND package dependencies need to be adhered to. If the person installing the distro doesn't want to follow these simple guidelines then they are on their own. There is no magic here.
If anyone doesn't like the way the openSuSE is assembled they are free to create their own distribution.
I get all any user needs to get. If the distribution sucks, it sucks. You can't tell a user who pops the cd in, tries to use the system, and encounters all those problems, that it's their fault.
Those branding packages *break some systems*.
Did you file bugs for those? (the gfxboot case might be hard to fix, but I'm pretty sure deselecting gfxboot and gfxboot-branding does not break your install) Kernel developers are usually quite interested in "loading this module breaks my hardware".
I also taboo them because I CAN NOT have grub loading gfxboot and I CAN NOT have the kernel trying to switch into graphical console modes
tabooing those packages will not prevent the kernel from switching into graphical console mode.
probably an Arch one. Then I would go and do that and suse's
unsuitability for servers would no longer be a problem for me and you would no longer have to hear reports of things that don't work and it would no longer annoy me that you don't care about anything you don't happen to do yourself.
Fact is, this is a Factory users and developers mailing list. I personally (as a developer, who does most of the work in his free time) could not be less concerned about your problems commercially deploying openSUSE here, simply because it does not really help me improve Factory. File bugreports for that. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org