This is not a poll about big issues or bugs! Besides, there are none:P
(So please don’t write about computers refusing to boot or the openSuSE installer nuking Windows partitions. That just doesn’t happen!)
State your three most hated minor nuisances in openSuSE. I know, I know, you’ll be hard pressed to keep the number down to 3…
My three all-time favorites:
3. Without a physics degree, Kwallet and Kmail can’t be made to actually work together, although they are both part of the KDE environment. Now, that’s what I call Kompatibility.
2. The kqemu accelerator module (for the QEMU emulator) has root-only permissions, so it’s not available for non-root users by default. In order to play Hearts in Windows at acceptable speed, you have to be root! Nice. Makes me remember the days when I still had Windows on my drive and had to log in as Administrator just to play Rayman 2. Definitely the way to go, openSuSE!
1. And the winner is: knetworkmanager starts up way too late in the boot sequence. Since I always tell KDE to remember my previous session, all my saved Konqueror sessions time out with “Page not found” messages before knetworkmanager even tries to connect to an Access Point…
A frustration is not put away knowing that it is as it is. And I may go off topic. I have the idea that the role of knetworkmanager is not quite understood either by me or a lot of others.
knetworkmanager is part of KDE and has nothing to do with the bootsequence. You may think different about when the boot sequence ends, but imho ‘runlevel 5 reached’ is realy the end of it. After that comes a login of the end-user (maybe automatic) and with that a Desktop environment is started that may be different for different users or for the same user at different times. Then knetworkmanager starts. Why?
Normaly the network in a Unix/Linux system is started as one of the first actions at runlevel 3 and that is in time for all the network services started in runlevel 3 and above. This is known in YaST as ‘Traditional method with ifup’. So why knetworkmanager?
I think it is because of the laptops and the wifi. The end-user wants to influence the way the system contacts one of the networks available. So knetworkmanager is a way to present to the end-user a dynamic way to do the bussiness of the system administrator.
But as the end-user starts doing this, the system is way beyond the boot sequence.
That this raises frustation can be found in several threads on the Forum where people are trying to make start/stop scripts in init.d to circumvent this. We are not in a perfect world, even with Linux.
Wait! is this about KDE or opensuse??
coz if this is about opensuse, then all these problems vanish if you just switch to (example) gnome (which gives rise to gnome problems…which are not there in kde etc etc.)
> 3. Without a physics degree, Kwallet and Kmail can’t be made to
> actually work together, although they are both part of the KDE
> environment. Now, that’s what I call Kompatibility.
My bad! Should’ve written “can’t be made not to work together”, meaning that, if you want to disable kwallet for kmail only (leaving it enabled for other programs), you’ll be facing some hard time.
So your first most anoyance in KDE (not in openSUSE) is:
Without a physics degree, Kwallet and Kmail can’t be made not to actually work together, although they are both part of the KDE environment. Now, that’s what I call Kompatibility.
I do not think much people will support this as an anoyance. And yes they seem to be very Kompatibel which each other.
