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? Lately we get the worst of both worlds. All the lack of support of a diy distro with none of the flexibility of a diy distro. If we have to do it ourselves, then Arch or slack or linux-from-scratch or gentoo seems to be a much better investment of our time, because, being diy distros, they don't get in the users way and step on the users toes trying to do things automatically but failing at it. Again this is all just lately, the last few years. I know the reason I picked opensuse in the first place was because it was well engineered and more things "just worked" than other distros and up to that point suse had a pretty long and consistent history of being well engineered. But since then it has become much more slapdash. or at least, I certainly encounter more problems on average and have to do more manual work-arounds to things that used to work as advertised. Suse really exemplifies the truism that past performance is no indicator of future performance. You can't decimate the engineering staff and expect the product not to suck before long. You can't allow the product to grow sucky and expect the users not to notice. You can't expect the users to like and continue to use a product that has grown sucky on them. You can't expect the users to become skilled developers and analysts and give skilled time and effort to a project that answers criticisms with responses like yours. Perhaps you're swamped and harried because the upper levels of your organization and your work experience have changed out from under you just as our distribution has on us. If so, your response is understandable if not forgivabel or tolerable. I sympathize, but I do not accept. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org