kcontrol monitor and display settings module cannot start

Bug #63517 reported by P
22
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Since upgrade to edgy beta1, I am unable to launch monitor and display settings neither from guidance nor kcontrol.

Guidance says the module is probably broken.

try kcontrol > devices (peripheriques FR) > monitor and display

Revision history for this message
P (p92) wrote :

confirmed on irc

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
Freddy Martinez (freddymartinez9) wrote :

I have the same error on a XGL/compiz install (but they are not causing it)

Revision history for this message
Anthony Mercatante (tonio) wrote :

No issues here on edgy beta...
Can you launch "kcmshell displayconfig" in the shell and paste your output here ?

Changed in kdebase:
status: Confirmed → Needs Info
Revision history for this message
P (p92) wrote :

Pythonize constructor -- pid = 9888
Python interpreter initialized!

Pythonize constructor -- pid = 9888
open /dev/mem: Permission denied
VESA BIOS Extensions not detected.
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.4/displayconfig.py", line 1687, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.4/displayconfig.py", line 443, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 371, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 376, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1085, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1635, in _finalizeInit
    self.original_size = self.getAvailableResolutions()[self.currentsizeindex]
IndexError: list index out of range
error: *** runFunction failure

and in the window that appears it says it needs superuser rights

I click on administrator mode button

Pythonize constructor -- pid = 9915
Python interpreter initialized!

Pythonize constructor -- pid = 9915
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.4/displayconfig.py", line 1687, in create_displayconfig

return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.4/displayconfig.py", line 443, in __init__

self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 371, in __init__

self._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 376, in _finalizeInit

gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1085, in _finalizeInit

screen._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1635, in _finalizeInit

self.original_size = self.getAvailableResolutions()[self.currentsizeindex]
IndexError
:
list index out of range

error: *** runFunction failure
;

and in the window it says "impossible to load module..."

Revision history for this message
P (p92) wrote :

it does not work nor as user nor as root. I don't use xgl.

Revision history for this message
P (p92) wrote :
Revision history for this message
P (p92) wrote :
Revision history for this message
P (p92) wrote :

still true on edgy rc1

Revision history for this message
P (p92) wrote :

still true on edgy
seems related to bug #34316

Revision history for this message
Vanessa Dannenberg (vanessadannenberg) wrote :

Same problem here on a fresh Edgy install (via alternate CD, with all repositories enabled and updated) this morning.

Revision history for this message
Ulrich Lukas (ulrich-lukas) wrote :

There is some additional information in the description of bug #37165
https://launchpad.net/distros/ubuntu/+source/kdebase/+bug/37165

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Do you still have this problem on current Feisty?

Revision history for this message
Vanessa Dannenberg (vanessadannenberg) wrote : Re: [Bug 63517] Re: kcontrol monitor and display settings module cannot start

On Thursday 05 April 2007 3:07:51 pm Yuriy Kozlov wrote:
> Do you still have this problem on current Feisty?

I have since switched to another distribution, however the display module did
seem to work fine under Feisty.

--
"Life is full of happy and sad events. If you take the time
to concentrate on the former, you'll get further in life."
Vanessa Ezekowitz <email address hidden>

Revision history for this message
Sebastian Kügler (sebasje) wrote :

Closing it at this point.

Changed in kde-guidance:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.