reassign 550877 kdebase-runtime retitle 550877 componentchooser KCM shall not kill window manager not under KDE thanks Hello, On antradienis 13 Spalis 2009 23:16:49 David Steiner wrote: > "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. Well, then "Cancel" button would not hurt obviously. > 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. But following such a logic all Xorg crash bugs would be critical. That's not the case. > "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. It changes KDE desktop or KDE application settings. That particular setting is of KDE desktop, it does not affect KDE applications (contrary to e.g. default browser). > "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. Since you are not running KDE session manager, it cannot start window manager for you. That setting would start Openbox under KDE session though. > "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. But it used to work like it was set before (i.e. KWin), didn't it? So golden rule - don't fix what ain't broken :D > "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. Since KDE has a session manager, it can replace current window manager without terminating X session. So why wouldn't it? It's a feature and it is safe under KDE. However, I agree that it should not do that under non-KDE session since it might not be safe. -- Modestas Vainius <modestas@vainius.eu>
Attachment:
signature.asc
Description: This is a digitally signed message part.