Bug 126561 - display button not showing up after the KDE update for KUBUNTU
Summary: display button not showing up after the KDE update for KUBUNTU
Status: RESOLVED DUPLICATE of bug 135725
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Simon Edwards
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-01 12:27 UTC by Vittorio
Modified: 2008-06-26 15:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Vittorio 2006-05-01 12:27:58 UTC 
Version:           0.2 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu0 breezy)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12-10-386

In the Display settings, hardware section, there was the Display button that allowed to change your monitor resolution. It was already buggy, since only one resolution showed up in the drop down menu despite i put several resolutions in my xorg.conf file amd since it only provided a frequency of -15321 Hz (yes, a negative frequency).
However after the update KDE 3.5.2 released from the kubuntu team, that button is totally missing, both from the system settings and from the "configure desktop" option the right-click on the desktop.
So i cannot even see the available resolution because there's no "Display" button at all!

thanks for the help
Comment 1 Gene Mosher 2007-07-19 16:45:33 UTC 
This disappearance of this Display Button is tied to the problem discussed in Bug report # 135725, in System Setting, Monitor & Display error message "The module Monitor & Display could not be loaded. On my box the graphics card is ATI Radeon X850 Pro.  This feature worked earlier.

I have another box running KDE 3.5.7 (Nvidia) on Debian which shows the Display Button and shows Monitor & Display System Settings.
Comment 2 FiNeX 2008-06-26 15:13:07 UTC 

*** This bug has been marked as a duplicate of 135725 ***