By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1264 - Allow display changes in Control Center without root permissions
Summary: Allow display changes in Control Center without root permissions
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeadmin (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: All All
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-10-13 05:38 CDT by Jan Stolarek
Modified: 2013-01-10 21:32 CST (History)
5 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Stolarek 2012-10-13 05:38:53 CDT
Applying any changes to monitor and display requires root permissions. I think it is bad to require root privileges to perform daily desktop tasks like connecting a second monitor. It would be better to allow user to make changes to the current session, without root permissions and either: without possibility to save these settings to global xorg.conf (or whatever the distro uses); or - even better - save these settings to users home directory so that they are restored on startup. There are already programs that allow to make changes to the current X session without root privileges (e.g. nvidia-settings, arandr).
Comment 1 Darrell 2012-10-13 15:33:37 CDT
This might seem to make sense on a single user or home system, but creates administrative challenges on multiple user or enterprise systems. Remember that Trinity is a desktop environment only that sits on top of the base operating system, where display options are configured. The tools provided in Trinity are conduits/wrappers to those operating system commands.

Conceptually, how would you go about implementing such a change?
Comment 2 Jan Stolarek 2012-10-14 01:42:50 CDT
(In reply to comment #1)
> Conceptually, how would you go about implementing such a change?
As I said it is already implemented by some program that allow to turn on additional display and configure its settings without root permissions. I do not know the details of HOW this programs implement it. The only thing is that they do not allow to save this settings and instead use it only for the current session. I imagine it would be possible to save this settings in user's ~ and restore them on Trinity startup.
Comment 3 Darrell 2012-10-14 01:54:47 CDT
There are two separate kcontrol modules for configuring the display. One is Peripherals->Display. The second is System Administration->Monitor & Display. Both have similar configuration options.

The one in Peripherals is user-based and the one in System Administration is global for the system. The options in Peripherals->Display will overrride those set by an administrator in System Administration->Monitor & Display.

Is the module in Peripherals->Display what you seek and sufficient to resolve your wishes?
Comment 4 Jan Stolarek 2012-10-16 02:59:30 CDT
(In reply to comment #3)
> There are two separate kcontrol modules for configuring the display. One is
> Peripherals->Display. The second is System Administration->Monitor & Display.
> Both have similar configuration options.
> 
> The one in Peripherals is user-based and the one in System Administration is
> global for the system. The options in Peripherals->Display will overrride those
> set by an administrator in System Administration->Monitor & Display.
> 
> Is the module in Peripherals->Display what you seek and sufficient to resolve
> your wishes?
No, I think it is not. Module available in peripherals does not allow to control desktop layout when a second monitor is attached. I also see no controls for gamma and brightness.
Comment 5 Darrell 2012-10-16 15:29:52 CDT
You have a point about layout and second monitors. I think part of the problem with gamma/brightness is the tabs are named differently: "Monitor Gamma" and "Brightness and Gamma."
Comment 6 Jan Stolarek 2012-10-17 01:05:01 CDT
(In reply to comment #5)
> You have a point about layout and second monitors. I think part of the problem
> with gamma/brightness is the tabs are named differently: "Monitor Gamma" and
> "Brightness and Gamma."
I have only two tabs in Peripherals -> Monitor: Size & orientation and Energy management (or whatever the English names are).
Comment 7 Darrell 2012-10-17 10:19:43 CDT
Huh. Something is not right. You're missing a tab in Peripherals->Display. Maybe contact the packager from whom you obtained the packages?
Comment 8 Jan Stolarek 2012-10-17 11:14:43 CDT
(In reply to comment #7)
> Huh. Something is not right. You're missing a tab in Peripherals->Display.
> Maybe contact the packager from whom you obtained the packages?

I have two tabs - I assume there should be more. The packages are from official Trinity repo for Debian. Why do you think it's a matter of packaging?
Comment 9 Darrell 2012-10-17 11:31:39 CDT
Probably not packaging but compiling, because you are missing the Peripherals->Display->Monitor Gamma tab. Contact Timothy Pearson in the developer's or user's mail list.
Comment 10 Jan Stolarek 2012-10-17 12:30:24 CDT
(In reply to comment #9)
> Probably not packaging but compiling, because you are missing the
> Peripherals->Display->Monitor Gamma tab. Contact Timothy Pearson in the
> developer's or user's mail list.

Doesn't he track the bugzilla?
Comment 11 Timothy Pearson 2012-10-17 12:56:23 CDT
(In reply to comment #10)
> (In reply to comment #9)
> > Probably not packaging but compiling, because you are missing the
> > Peripherals->Display->Monitor Gamma tab. Contact Timothy Pearson in the
> > developer's or user's mail list.
> 
> Doesn't he track the bugzilla?

Yes I do.

On my R14 test system all tabs are visible.  The System Administration->Monitor & Display is the "official" supported control panel; the one in Peripherals->Display is deprecated, NOT supported, and will be phased out very quickly.

Regarding the deprecation of the Peripherals->Display control module, that module was a Python-based hold-over from Ubuntu and has not been updated in years.  It tends to breaks systems more often than it works and duplicates a lot of low-level control code.  From a maintainer's perspective this is a very bad thing, and helped to force the rewrite.

All this being said, it appears that the official display control panel should support some kind of user-mode settings.  In reality this shouldn't be too hard, with the main difficulty being saving the user's settings somewhere and providing a means to restore each user's settings on virtual terminal switch.  It would also be a good idea to provide an option for a system administrator to lock out user-mode display configuration if desired (e.g. old monitors which could catch fire with bad modes, etc.).

Tim
Comment 12 Darrell 2012-10-17 17:08:00 CDT
I don't know. Ask him. :)
Comment 13 Slávek Banko 2012-10-18 20:26:18 CDT
For fast (singleshot) settings, such as a second monitor connected to the notebook, for me seems as best use KRandR in the tray. Unfortunately, can not be used to set two (or more) monitors independently - only as clone. Therefore I use xrandr from Konsole.
Comment 14 Timothy Pearson 2013-01-08 20:21:23 CST
This bug should be mostly resolved in GIT hash 477e956.  The only item not yet implemented is a configurable administrative lockout to prevent users from changing the display configuration when enabled.
Comment 15 Timothy Pearson 2013-01-10 21:32:59 CST
(In reply to comment #14)
> This bug should be mostly resolved in GIT hash 477e956.  The only item not yet
> implemented is a configurable administrative lockout to prevent users from
> changing the display configuration when enabled.

I don't currently see any way to lock out the xrandr extension (aside from completely disabling it, even for root), therefore I am opting not to implement an administrative lockout and closing this bug report.