Small typo in my previous post. The correct syntax for
AllowMouseOpenFail (as in xorg.conf) should be:
Option "AllowMouseOpenFail" "true"
with that displayconfig works fine. Without the "true" specified
explicitly, the X server will work, but displayconfig crashes
--
The module Monitor & Displa
I had this problem also (Hardy Heron kubuntu stable on AMD64). I was
just getting ready to give up, when I noticed the following error in the
displayconfig error trace:
raise ParseException,"Unknown line type '%s' on line %i" % (first,line)
xorgconfig.ParseException: Unknown line type 'allowm
I still have this bug, hardy heron 8.04
output of 'displayconfig'
Traceback (most recent call last):
File "/usr/bin/displayconfig", line 1754, in
displayapp = DisplayApp()
File "/usr/bin/displayconfig", line 441, in __init__
self.xsetup = XSetup(self.xconfigpath)
File "/var/lib/pyt
Please attach a copy of /etc/X11/xorg.conf to the bug.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
kcmshell displayconfig gives:
Pythonize constructor -- pid = 20864
Python interpreter initialized!
Pythonize constructor -- pid = 20864
Traceback (most recent call last):
File "", line 8, in kcontrol_bridge_create_displayconfig
File "/var/lib/python-support/python2.5/displayconfig.py", line
Work around for the resolution issue is to go into the Hardware tab and
configure your monitor to use a generic LCD/monitor with the desired
resolution. Would you please try that.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug no
This bug was fixed in the package kde-guidance -
0.8.0svn20080103-0ubuntu4
---
kde-guidance (0.8.0svn20080103-0ubuntu4) hardy; urgency=low
* Add kubuntu_14_displayconfig_survive_no_serverlayout.patch so
displaymanager doesn't crash if xorg.conf has no ServerLayout section
(L
This should be ready to upload shortly.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kde-guidance in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
Setting beta milestone. If we get the fix in soonish we can test it in
beta fix verification also (see:
https://wiki.ubuntu.com/Testing/ISO/Schedule)
** Changed in: kde-guidance (Ubuntu)
Target: None => ubuntu-8.04-beta
--
The module Monitor & Display could not be loaded.
https://bugs.lau
Hereby confirmed the changes/workaround work for the default xorg.conf
2 gripes:
- only 640x480 and 800x600 resolution.
- Gamma correction doesn't work... it also didn't work before the changes and I
will open a new bug tracker for it.
--
The module Monitor & Display could not be loaded.
https:
I've uploaded a test package to my that makes displaymanager work for me
when I remove the ServerLayout section from my xorg.conf. If I can
quickly get some test feedback, I can probably get this uploaded before
the beta freeze:
https://launchpad.net/~kitterman/+archive
--
The module Monitor &
xrandr is not a perfect solution either. See the blog post you link to about
it's bugginess. Also that's a gtk2/gnome tool, not one appropriate for
Kubuntu.
What I'm currently attempting is to see if I can teach displayconfig to
believe in a sane set of defaults if parts or all of xorg are mi
For now I would prefer Scott's idea on the development list, option "d)": use
the workaround for 8.4/KDE3. It would be sufficient for beginning users, while
more advanced users can install whatever they like.
a) is not really acceptable. And looking at time constraints/testing
cycles I would ke
If a re-write for Hardy is no option and the module is broken by design,
what can we do?
a) Remove it entirely and let the user deal with command-line xrandr
If "fixup" allows to port/backport
b) Backport the one from Kubuntu-Hardy-KDE4 that is prepared for XRandR
c) Port the one from Ubuntu Har
** Changed in: kde-guidance (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Scott Kitterman (kitterman)
Status: Confirmed => In Progress
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification b
this is a pity since the bug was filed on December :(
anyway better a workaround than nothing, but a question: Ubuntu how they do?
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Tea
Right, but we're close to release. A rewrite isn't happening for Hardy.
Fixups are really all we can do.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed
guys read comment "Harald Seipp wrote on 2008-02-23" that explains what is the
*real* problem.
readding "ServerLayout" is not a fix, just a workaround, but this module need
to be rewritten as xorg.conf is changing.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net
I ran "kdesudo displayconfig" from a konsole and I get the exact error message
as in the original posters (I'm running hardy alpha6).
After fiddling a bit it seems that as pointed out above adding the
"ServerLayout" section does the trick. Add it to xorg.conf and it opens
again (it won't close a
It's a problem with the xorg.conf (apparantly some items were removed
which Monitor&Display module still looks at), so anyone who by default
replaces it by his own probably won't get the error.
For first time users this would be pretty annoying.
--
The module Monitor & Display could not be loade
No progress with Kubuntu Hardy Alpha 6 - still the same error. Strange
that such a higly visible malfunction is not getting more attention...
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of
Looks like the smart way would be to use XRandR
(http://www.x.org/wiki/Projects/XRandR) as the preferred way to set screen
size, orientation and/or reflection of the outputs for a screen for modern X
servers.
Maybe some URandR (http://www.x.org/wiki/Projects/XRandR) or Python-XRandR
(https://c
Looks like the root cause is the integration of the new 1.4.0 X server. This
server does no longer require a ServerLayout section in xorg.conf - see that
attached xorg.conf for the Alpha 5 live CD.
When starting displayconfig, the code calls
/var/lib/python-support/python2.5/displayconfigabstrac
Installing python-dev with e.g. "sudo aptitude install python2.5-dev" only
fixes the kcmshell/python problem in user management. It doesn't fix the
monitor&display problem.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notific
Problem is still present with Kubuntu Hardy Alpha 5 (i386, liveCD).
Installing python-dev as suggested in a related thread did not help.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Ubunt
http://bryceharrington.org/drupal/display-config-1 describes the recent
progress of the Ubuntu display configuration.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is s
The first Kubuntu Hardy KDE4 Alpha
(https://wiki.kubuntu.org/HardyHeron/Alpha5/KubuntuKDE4) comes with a
completely new displayconfig module that indeed uses XRandR.
It is not fully operational yet (settings cannot be changed), but this looks
like the right approach.
Hopefully someone will backp
Hello folks,
Got the same here, with a fresh -installed- Hardy Alpha5 (+ current updates)
kernel i386 2.6.24-10-generic
KDE 3.5.9
python 2.5.2 (python says, but aptitude says 2.5.1-1ubuntu2 )
qt : 3.3.8-b-0ubuntu1 package
python-qt3 : 3.17.4.1ubuntu1
Error seems to come from
/var/lib/python-supp
Sebastian Schack:
> Without adding/changing anything manually, it does now work for me - with
> all the latest Hardy packages.
>
cannot confirm at all.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you ar
Without adding/changing anything manually, it does now work for me - with
all the latest Hardy packages.
2008/2/29, Shaikailash <[EMAIL PROTECTED]>:
>
> I had the same problem too...kubuntu hardy fresh installed.
> I have a laptop, dell xps M1530, nvidia geforce M 8600 GT, i have used the
> restri
I had the same problem too...kubuntu hardy fresh installed.
I have a laptop, dell xps M1530, nvidia geforce M 8600 GT, i have used the
restricted drivers and it works, but cannot change resolutions, and so on..
I tried to add the line in the /etc/X11/xorg.conf and now it seemes to
works. Could be
** Tags added: kde-guidance-displayconfig
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kde-guidance in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL P
i forgot to add my lspci output
lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobil
I have added this to the xorg.conf
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection
Now i can open displayconfig alright, but its pretty empty inside, i dont think
ubuntu/xorg has detected my hardw
I am also seeing this bug, and its real annoying when you want an
external screen on your laptop :(
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I did a bit of debug and I found this:
the problem is in displayconfigwidgets.py line 46 (and next) that object
screen passed to the function is null.
but the real problem seems in displayconfig.py @ line 1134 (or 1135)
self.xsetup.getPrimaryScreen() returns null and then assign null to
self.cur
still here with up-to-date hardy @ 19 Feb 2008
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kde-guidance in ubuntu.
--
kubuntu-bugs mailing list
Kubuntu Hardy Alpha 4, running as live session - the same bug here.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kde-guidance in ubuntu.
--
kubu
Another confirmation. Running the latest Hardy...
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
I can confirm this bug. I attached a screenshot as well.
** Changed in: kde-guidance (Ubuntu)
Status: New => Confirmed
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, w
I faced the same situation during first boot after kubuntu hardy alpha
3(i386) install(screenshot attahced). When I tried to load it in
'Administrator mode' the result was same.
My system is AMD Athlon 3000+ 64-bit, NVidia 6100GeForce on board VGA,
Motherboard - ASUS K8N-VM.
The problem is that I
I would like to say i got this bug too.
--
The module Monitor & Display could not be loaded.
https://bugs.launchpad.net/bugs/173768
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kde-guidance in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at [WWW]
https://wiki.ubuntu.co
43 matches
Mail list logo
