I don't think this bug should be fixed. If you run application *as*
root, the application should use root's theme settings but not the
caller's.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
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
Next month this bug will celebrate its seventh birthday!
Please fix the theme issue for gksu / sudo / elevated-privilege
applications. Make GTK check for themes in the user's home directory,
make gksu create a temporary symlink to the user's theme directory, I
don't know, but in seven years
I'm out of the office until 1st August.
On 6 May 2011, at 09:03, Christoph Buchner 24...@bugs.launchpad.net
wrote:
it is now 2011, still not resolved.
for me, this bug has been triggered by this workaround around the
too dark inactive menu item text in ambiance:
gksu is a hack. fix your applications.
On 6 May 2011 09:11, Christoph Buchner 24...@bugs.launchpad.net
wrote:
it is now 2011, still not resolved.
for me, this bug has been triggered by this workaround around the too dark
inactive menu item text in ambiance:
it is now 2011, still not resolved.
for me, this bug has been triggered by this workaround around the too dark
inactive menu item text in ambiance:
http://askubuntu.com/questions/7561/how-to-change-the-color-of-menu-text
--
You received this bug notification because you are a member of Ubuntu
it is now 2010
this still has not been resolved
we are still in workaround-land
five years later
nice
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I just modified a theme recently, and put my own version in ~/.themes.
The day after, I discovered the issue with synaptic. I wanted to create
a bug about it to help improve the distro on that little issue, and I'm
amazed by the fact that it has been done 4 years before, and by the
amount of
Assuming my suggestion above is not stupid.
Rather than saying that it is a bug that affects sudo or gksudo
commands, we could change it into a feature requests that affects
whatever are the graphical applications that manage the gtk themes on
(x)ubuntu distributions. Or that the system lacks
I think it's a UX bug and not really specific to gksudo or gtk+.
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
So... I see this isn't getting into Karmic either.
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
The present behaviour is NOT a good feature. There is no value
whatsoever in having the user experience go from smooth to crap just
because the distro has decided to escallate a program to root
prividledges. The fact that in Ubuntu you have to [graphically or
otherwise] provide [sudo] your
i dont know if this is the same thing, but to use the theme of the
current user in your root system is done by :
sudo ln -s ~/.themes /root/.themes
sudo ln -s ~/.icons /root/.icons
sudo ln -s ~/.fonts /root/.fonts
now i would like to know how i could add an new user, and use the theme
that i use
The present behavior is actually a good feature.
The user can set a different theme/icon set for the root user, this is useful
when working with several windows and to quickly realize that the window has
root privileges. Especially when having the root windows open for a long time.
--
That's no reason to not fix this bug, as I'm pretty sure GTK explicitly
whinges about being run as root.
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Mmmmh, i do think it's a papercut. I install ubuntu for a lot of people,
and lots of them complaint about the theme/icons doesn't appears for
applications that runs for root (on gksu), so i have to do a sudo cp -R
./icons /usr/share/icons and that stuff all the time (or run themes on
normal users,
Any GTK app running as root is a total face gash. It should not be happening
under any circumstances. Let's fix that problem instead.
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member
Changing to invalid - this bug only affects small group of users that
download and install themes by themselves, therefore it's not a
papercut.
** Changed in: hundredpapercuts
Importance: Undecided = Low
** Changed in: hundredpapercuts
Status: New = Confirmed
** Changed in:
** Also affects: gksu
Importance: Undecided
Status: New
** Changed in: gksu
Status: New = Invalid
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
Please don't confuse this as a feature. The bug here is simply that
applications are being run as root.
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
There's a lot of confusion here. Themes should not be installed
globally, though I think they should all be available globallly after
installation.
I agree that it is good to have a different theme for root actions - so
I would like to launch gksu appearances to set my sudo theme, better
option
For me, two best solutions would be:
a) Advising a user that automatically installed themes affect only to
user account and won't be selected for administrator accounts.
b) creating an option in the appearance configuration dialog that lets
user install a theme globally and select it (obviously
the policykit use in hardy means that admin tools are running as user
now
--
applications run through gksu cannot use themes in ~/.themes
https://bugs.launchpad.net/bugs/24280
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
How about this for a solution:
Situation:
The user changes her theme to a non-standard one installed by downloading an
archive file and installing it with GNOME's appearance properties application.
Problem:
Applications launched by the user via. a sudo or gksu command do not
reflect the user's
24 matches
Mail list logo
