https://bugzilla.novell.com/show_bug.cgi?id=686449 https://bugzilla.novell.com/show_bug.cgi?id=686449#c2 --- Comment #2 from Ricardo Cruz 2011-04-09 15:42:13 UTC --- (In reply to comment #0)

Expected Results: Like all well-behaved graphical programs, the software manager should restore the window layout that was used when the it was closed.

I agree, a well-behaved program should store such information. But few do, because there isn't presently an uniform way to do it. In the case of yast2, it's much harder to do because of it running as root. We want to store such information in an user basis, just like the gnome-session settings are individualized (ie. styles, fonts), but it's not clear how you go about to do it, given yast2 is running within the root shell. I will put some thought into that... We can also tweak the default window size. It is already dependent on the font size and all that, and we could further improve it. An ugly alternative is to just maximize yast2 by default, at least the software manager tool. ;) This is what the Ubuntu software manager (Synaptic) does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=686449 https://bugzilla.novell.com/show_bug.cgi?id=686449#c3 --- Comment #3 from Holger Arnold 2011-04-09 22:01:36 CEST --- The GTK software manager already stores some settings in /etc/sysconfig/yast2-gtk, so a quick hack would be to store at least the window size there (and make sure that the side bar has a useful minimum size). Generally, however, storing *any* gui settings under /etc/sysconfig is ugly since these settings have nothing to do with system configuration. The yast2-gtk file should eventually be removed from this directory. But the deeper problem is running yast2 as root at all. Running a full gui application as root is *fundamentally* wrong. First, it causes annoyances like bad-looking fonts, wrong gui styles, or the inability to store settings at proper places. But more importantly, it can become a security problem because large and complex libraries such as GTK and Qt are simply not designed to be run in a root context. The only sane solution is to run the gui unprivileged in the user context and let small privileged background processes to the actual configuration work. By today's standards, one should probably use PolicyKit for this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=686449 https://bugzilla.novell.com/show_bug.cgi?id=686449#c5 --- Comment #5 from Ricardo Cruz 2011-04-09 20:33:48 UTC --- (In reply to comment #3)

The only sane solution is to run the gui unprivileged in the user context and let small privileged background processes to the actual configuration work. By today's standards, one should probably use PolicyKit for this.

webyast/yast3 has been in the works for some time now, and that is one point they meant to address, among other exciting stuff. But I dunno how far behind the production stage it is... But meanwhile, sure, let's hack something through. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.