They sort of did solve this bug. Rather than using gksu and running applications as an administrator, most applications that require "administrator-privileges" use a separate background application. Those applications have a "unlock" button.
Most applications have already been upgraded to this new approach, except for a few, like the update-manager. I think the plan, there, is to integrate it, within the USC. I'm not an ubuntu-dev, but it seems they were aiming to fix many problems at once, using this new architecture, but it's more work, so it takes a bit longer, but when it's done, not just this bug, but many others can be closed. It's a different trade-off. On the other hand, the customization, and manual themes in general, is taking a back-seat to other priorities. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/24280 Title: applications run through gksu cannot use themes in ~/.themes Status in The "GKSu" Gnome Frontend for "su": Invalid Status in One Hundred Paper Cuts: Invalid Status in “gksu” package in Ubuntu: Confirmed Bug description: The user interface of the theme manager does not make clear that it can only install themes for the current user. Furthermore it does not provide an option to install themes system wide. This very often leads to bug results like this one: Scenario: A) User finds spiffy (or totally hideous) theme online and loves it. B) User installs theme and uses it. C) User selects any sudo-required admin app and is greeted with the default GTK theme. Solutions: 1) Live with it and wait until GTK uses a nice default theme (dapper + 1 if we're lucky?). Is this even good enough? 2) Stick the user $HOME/.themes directories into whatever path gtk uses to find themes so the admin apps match the user apps no matter what awful creation the user might be imposing upon [him|her]self. 3) Be smart enough to know if a theme is not available and fallback to the default Human theme or something along those lines... basically just do anything to avoid showing it un-themed. 4) Create a new theme specifically for use with apps that require sudo priv. Use this theme at all times. Maybe make it an /etc setting somewhere for people that can't stand it and "must" change it for whatever reason. To manage notifications about this bug go to: https://bugs.launchpad.net/gksu/+bug/24280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
