[Bug 24280] Re: applications run through gksu cannot use themes in ~/.themes
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 Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24280] Re: [Theme Manager] No installation option for system wide themes, difference is not communicated in the user interface
I think the updated description to this bug confuses the issue. The problem is *not* that users can only install themes locally, the problem is that when a user installed theme is used the administration applications fall back to the default GTK theme (because they cannot find the user installed theme, obviously). This is a problem because: 1- Un-themed GTK is unattractive to all but the most eclectic tastes. 2- It is not the expected behavior to people who don't understand how themes work. Admittedly, this problem can be avoided. After all, if you can run administrator apps then you probably have the permission necessary to install themes globally. However, doing so requires knowledge in areas where knowledge shouldn't really be required (you shouldn't have to understand how GTK and GNOME work to use a system for Postfix, LDAP and Apache administration without undue confusion). In my mind the easiest solution is to tell GTK to use the Human theme as a fallback if the requested user theme cannot be found. At least that way, the user will see a familiar theme in front of them. I don't think allowing root applications to scan user directories for themes is a wise idea and I suspect the patch would never make it past the relevant maintainers. -- [Theme Manager] No installation option for system wide themes, difference is not communicated in the user interface https://bugs.launchpad.net/bugs/24280 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24280] Re: locally installed gtk themes not applied to admin apps
The problem is that the path that GTK searches for themes is based on the user running the program. So, if you have a theme in ~/.themes, GTK will not be able to find it when running as a different user. As Al says, this has nothing to do with gksu, gksudo, sudo, or su, it's simply that GTK is looking for a theme that is no longer available. Since the theme is set in gconf, maybe the theme search path could be set there too? This would solve the problem as far as I can tell. -- locally installed gtk themes not applied to admin apps https://bugs.launchpad.net/bugs/24280 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24280] Re: locally installed gtk themes not applied to admin apps
Ah, I had assumed that the theme information was coming from gconf settings. I guess it comes from the users ~/.gtkrc ? I can't test at the moment, but do apps run via sudo use the /root/.gtkrc ? -- locally installed gtk themes not applied to admin apps https://bugs.launchpad.net/bugs/24280 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 26177] supported developer meta-package
Public bug reported: Currently we have (from Debian) gnome-devel which pulls in pretty much anything anyone would need to do development in GNOME. Unfortunately some of the packages it pulls in are not in main or are redundant to packages in main. I think the easiest way to get a development environment is to run sudo apt-get build-dep $somepackage, not exactly ideal. Some form of official ubuntu development package to pull in a supported development environment would be fantastic. This of course brings up some larger questions that even the GNOME community itself struggles with (eg, which IDE) and would require no small amount of work to integrate the tools that have already been chosen (eg, making all docs findable from the Yelp UI). [my $0.02USD on tools would be Monodevelop and Monodoc... it would of course require someone built AddOn's for MonoDevelop to support non-clr environments like straight C, C++ and Python, and it would require a lot of work with existing docs to get them into Monodoc... but I think Monodevelop has the most potential to be a powerful tool for many different environments given its extension architecture and the many languages that can be used to extend it] ** Affects: Ubuntu Importance: Wishlist Assignee: Ubuntu Desktop Bugs Status: Unconfirmed -- supported developer meta-package https://launchpad.net/bugs/26177 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25654] Re: [dapper] gst-compprep-0.8 hangs and cannot be killed
I can't seem to reproduce it. Apologies for not responding sooner. -- [dapper] gst-compprep-0.8 hangs and cannot be killed https://launchpad.net/bugs/25654 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36171] gnome-terminal as preferred terminal breaks 'run in terminal' launchers
Public bug reported: https://launchpad.net/malone/bugs/36171 Affects: control-center gnome-control-center (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Selecting gnome-termianl as my preferred terminal sets the command to: gnome-terminal --working-directory=%f I then create a launcher with the Command: ssh example.com and check 'run in terminal' Attempting to launch the launcher gives: Could not launch menu item Details: Failed to execute child process gnome-terminal --working- directory=%f (No such file or directory) It would seem that the --working-directory argument is unnecessary as everything seems to work fine when I choose another terminal (or a gnome-terminal as a custom command without that argument). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31452] gnome-python-2.0.pc not installed with python-gnome2-dev
Public bug reported: https://launchpad.net/malone/bugs/31452 Affects: gnome-python python-gnome2-dev (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: gnome-python-2.0.pc does not exist, and I believe it should (it's not in python-gnome2-extras-dev or python-gnome2-desktop-dev). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 27651] Send to... can't work
Public bug report changed: https://launchpad.net/malone/bugs/27651 Comment: Is this a temporary fix? I was using it with bluetooth last week without any problems (granted, I have working bluetooth) and it was pretty nice to have. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
