Bug 220085 - krandr does nothing when trying to set orientation, at the same session, xrandr works
Summary: krandr does nothing when trying to set orientation, at the same session, xran...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: krandr
Classification: Miscellaneous
Component: krandrtray (show other bugs)
Version: 4.6
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-25 20:25 UTC by pelzi
Modified: 2015-01-23 00:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pelzi 2009-12-25 20:25:04 UTC
Version:           0.5 (using 4.3.2 (KDE 4.3.2), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.30-2-amd64

krandr simply does nothing when I select a different orientation and press "apply" (or OK). Switching resolution with krandr works, so does switching orientation in xrandr (started from konsole with the same user in the same session). krandr correctly detects the orientations available, and the currently set orientation.

Setup:
- nvidia 8400 GS with nvidia driver/glx, randr option enabled
- DVI or analog connection doesn't make a difference
- following errors appear in .xsession-errors:
findServiceByDesktopPath: randr not found
findServiceByDesktopPath: nvidiadisplay not found
findServiceByDesktopPath: nvidia3d not found
findServiceByDesktopPath: kgamma not found
findServiceByDesktopPath: energy not found
- seems to be similar to http://bugs.kde.org/show_bug.cgi?id=170811 - but I'm on KDE 4.3!
Comment 1 Vincent Petry 2010-12-04 18:59:17 UTC
I enabled debug logging and here is the output:

When krandrtray starts:
display-randr(20326) RandRDisplay::RandRDisplay: Using XRANDR extension 1.3 or greater.
display-randr(20326) RandRDisplay::RandRDisplay: XRANDR error base:  176
display-randr(20326) RandRScreen::loadSettings: Creating CRTC object for XID 0 ("None")
display-randr(20326) RandRScreen::loadSettings: Creating CRTC object for XID 351
display-randr(20326) RandRCrtc::loadSettings: Querying information about CRTC 351
display-randr(20326) RandRScreen::loadSettings: Creating output object for XID 352
display-randr(20326) RandROutput::queryOutputInfo: XID 352 is output "default" (connected)
display-randr(20326) RandROutput::setCrtc: Setting CRTC 351 (enabled) on output "default"
display-randr(20326) RandROutput::queryOutputInfo: Possible CRTCs for output "default" :
display-randr(20326) RandROutput::queryOutputInfo:    - CRTC 351
display-randr(20326) RandROutput::queryOutputInfo: Current configuration for output "default" :
display-randr(20326) RandROutput::queryOutputInfo:    - Refresh rate: 50
display-randr(20326) RandROutput::queryOutputInfo:    - Rect: QRect(0,0 1280x800)
display-randr(20326) RandROutput::queryOutputInfo:    - Rotation: 1
QSystemTrayIcon::setVisible: No Icon set
display-randr(20326) RandRScreen::loadSettings: Creating CRTC object for XID 0 ("None")
display-randr(20326) RandRCrtc::loadSettings: Querying information about CRTC 351

When trying to rotate left:
display-randr(20326) RandRDisplay::needsRefresh: Cache: 1632390 Server: 1632390 Config: 1636018
display-randr(20326) KRandRSystemTray::populateMenu: Active outputs:  1
display-randr(20326) RandROutput::applyProposed: Applying proposed changes for output "default" ...
display-randr(20326) RandROutput::tryCrtc: Trying to change output "default" to CRTC 351 ...
display-randr(20326) RandRCrtc::applyProposed: Applying proposed changes for CRTC 351 ...
display-randr(20326) RandRCrtc::applyProposed:        Current Screen rect: QRect(0,0 1280x800)
display-randr(20326) RandRCrtc::applyProposed:        Current CRTC rect: QRect(0,0 1280x800)
display-randr(20326) RandRCrtc::applyProposed:        Current rotation: 1
display-randr(20326) RandRCrtc::applyProposed:        Proposed CRTC rect: QRect(0,0 1280x800)
display-randr(20326) RandRCrtc::applyProposed:        Proposed rotation: 2
display-randr(20326) RandRCrtc::applyProposed:        Proposed refresh rate: 50
display-randr(20326) RandRCrtc::applyProposed:        Enabled outputs:
display-randr(20326) RandRCrtc::applyProposed:           - "default"
display-randr(20326) RandRCrtc::applyProposed: Applying proposed changes for CRTC 351 ...
display-randr(20326) RandRCrtc::applyProposed:        Current Screen rect: QRect(0,0 1280x800)
display-randr(20326) RandRCrtc::applyProposed:        Current CRTC rect: QRect(0,0 1280x800)
display-randr(20326) RandRCrtc::applyProposed:        Current rotation: 1
display-randr(20326) RandRCrtc::applyProposed:        Proposed CRTC rect: QRect(0,0 1280x800)
display-randr(20326) RandRCrtc::applyProposed:        Proposed rotation: 1
display-randr(20326) RandRCrtc::applyProposed:        Proposed refresh rate: 50
display-randr(20326) RandRCrtc::applyProposed:        Enabled outputs:
display-randr(20326) RandRCrtc::applyProposed:           - "default"
display-randr(20326) RandRCrtc::applyProposed: Changes for CRTC 351 successfully applied.
display-randr(20326) RandROutput::tryCrtc: Failed to change output "default" to CRTC 351
display-randr(20326) RandROutput::tryCrtc:    Switching back to old CRTC 351


It looks like it sets the rotation back to its initial value.

I have a NVIDIA chipset with the proprietary driver version 260.19.21.
CPU is x86, distro is openSUSE 11.3 with KDE 4.5.80
Only one screen (laptop display panel)
Comment 2 Christoph Feck 2015-01-23 00:12:13 UTC
Thank you for your bug report or feature request.

Unfortunately, we did not have a maintainer for the "krandr" components, which are used to manage displays and monitors in the KDE Workspaces.

The "krandr" components has been superseded by "KScreen" in newer releases of the KDE Workspaces. It is compatible with all versions since 4.11, and is also used with Plasma 5. Please check with your distribution how to update to KScreen.

If this issue or feature request is still applicable to KScreen version 1.0.5 or newer, please add a comment. We will then reassign this ticket to KScreen developers.

If you are already using KScreen to manage displays or monitors, and found a different bug or need a specific feature, please create a new ticket for "KScreen" product in this bugzilla using this link: https://bugs.kde.org/enter_bug.cgi?product=KScreen

(This is an automatic message from the KDE Bug Triaging Team)