Bug#550877: Reply
Hello,
"It gave you a fat warning about a new window
manager, you ignored it and now you complain with severity serious?"
It shouldn't have changed anything, but it did.
It's not clear to assume "start new window manager" means kill the currently running one. Also there was no Cancel button, just an Ok.
I put it on serious because that's how the debian bug tracker says: "Can loose important data", like if I'm typing a long post in the browser, it would be lost, or an unsaved openoffice document. No big deal, change it to a normal bug. i haven't posted many bugs before.
"systemsettings is a KDE configuration app."
So it isn't being developed to work with other components? Seems reasonable, but kind of unintuitive when you use KDE apps outside.
"Again, why are messing with KDE systemsettings if you are not using KDE?"
i use konqueror, kmail and ktorrent. hence why i changed the Default Applications.
"However, this problem is mainly your own fault. You got what
you wanted and frankly, I still don't understand what you intended to achieve
changing that setting."
i changed it because i didn't want to screw up the login process. it was set to KWin, so to be safe i put it to OpenBox.
"Killing window manager under KDE would not kill the whole session which is obviously not the case under Openbox."
I still wonders me, why the window manager would get changed instantly. Isn't that the job of the Login Manager, KDM? Why not let the user select his window manager there? Then it wouldn't interfere with other login managers.
Reply to: