[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#245111: marked as done (kcontrol: Missing "Multiple Monitors" configuration module)

Your message dated Sat, 20 May 2006 09:56:09 +0200
with message-id <20060520075609.GA4172@hades.madism.org>
and subject line %20Bug#245111: kcontrol: Missing "Multiple Monitors" configuration
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kcontrol
Version: 4:3.2.2-1
Severity: normal

I'm testing my system in Xinerama mode, and it comes up fine. 
However, I've been reading in reviews of KDE 3.2 that it is supposed to
have a new and much improved module for Xinerama configuration. I've
seen screenshots where a "Multiple Monitors" item appears just below
"Multiple Desktops" under "Desktop", and I certainly can't find that.

Also "Peripherals -> Display -> Multiple Monitors" says that "This
module is only for configuring systems with a single desktop spread
across multiple monitors. You do not appear to have this configuration."
But I do, at least I think I do, assuming it is Xinerama it is referred
to. I type this on the second screen. 

However, I also note that "Desktop -> Panels" understand that I have a
Xinerama set-up, as it has the "Xinerama screen:" box. 

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-backstreet-ruby.2004-03-25.1-owl
Locale: LANG=C, LC_CTYPE=C

Versions of packages kcontrol depends on:
ii  kdebase-data               4:3.2.2-1     KDE Base (shared data)
ii  kdelibs4                   4:3.2.2-1     KDE core libraries
ii  libart-2.0-2               2.3.16-3      Library of functions for 2D graphi
ii  libasound2                 1.0.4-1       Advanced Linux Sound Architecture 
ii  libaudio2                  1.6c-3        The Network Audio System (NAS). (s
ii  libc6                      2.3.2.ds1-11  GNU C Library: Shared libraries an
ii  libfam0c102                2.7.0-5       client library to control the FAM 
ii  libfontconfig1             2.2.2-2       generic font configuration library
ii  libfreetype6               2.1.7-2       FreeType 2 font engine, shared lib
ii  libgcc1                    1:3.3.3-6     GCC support library
ii  libjpeg62                  6b-9          The Independent JPEG Group's JPEG 
ii  libpcre3                   4.5-1.1       Perl 5 Compatible Regular Expressi
ii  libpng12-0                 1.2.5.0-5     PNG library - runtime
ii  libqt3c102-mt              3:3.2.3-2     Qt GUI Library (Threaded runtime v
ii  libraw1394-5               0.10.1-1      library for direct access to IEEE 
ii  libssl0.9.7                0.9.7d-1      SSL shared libraries
ii  libstdc++5                 1:3.3.3-6     The GNU Standard C++ Library v3
ii  libxcursor1                1.0.2-4       X Cursor management library
ii  libxft2                    2.1.2-5       FreeType-based font drawing librar
ii  libxrender1                0.8.3-5       X Rendering Extension client libra
hi  xlibmesa-gl [libgl1]       4.3.0-0pre1v3 Mesa 3D graphics library [XFree86]
ii  xlibs                      4.3.0-0pre1v3 X Window System client libraries
ii  zlib1g                     1:1.2.1-5     compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
  this now works even for cards in "mergedfb" mode. if the problem
persist on your computer it's mostly due to an X configuration problem.

closing.

On Fri, May 21, 2004 at 10:00:19PM +0200, Kjetil Kjernsmo wrote:
> On fredag 21. mai 2004, 14:28, Niels Donninger wrote:
> > So, here's the solution:
> > Even if you plug two monitors into your videocard, you still make two
> > sections 'Device' with the same BusID for your videocard.
> > Notice that I put 'screen 0' in the first device and 'screen 1' in
> > the second. In an example I saw this thing in the 'ServerLayout'
> > section, but that didn't work for me.
> 
> Thanks for the instructions, it certainly addresses many of the problems 
> I have, but I'm not quite there yet. For those wondering what is going 
> on, Niels found he had the same problem as I reported in this bug, and 
> we started discussing offline, he found some solutions, and I thought 
> it would be better to address it in the BTS, so others can see. 
> 
> For one thing, for various reasons, I'm using two cards, not a single. 
> That should be straightforward, just use two different BusIDs. 
> 
> > Also notice that I disabled the 'option "MonitorLayout"': When I
> > enable this one, the whole thing doesn't work.
> 
> OK, never had it. 
> 
> > In the section 'serverlayout', two screens are defined, one default,
> > and one with external screen. Notice that the first one is the
> > default screen and not the external, otherwise it doesn't work
> > either. (sensitive isn't it ?;-) 
> 
> Yup... 
> 
> > Then, for the xinerama mode, include 
> > a section 'serverflags' where the option 'xinerama' is set to 'true'.
> 
> Aha, OK. I was lacking this. 
> 
> It is inconvenient for me to use, since I'm usually using the Ruby 
> patches to use two different X servers, with the new IsolateDevice 
> stuff in X and all.
> 
> However, RTFMing, I discovered that X can take an option +xinerama which 
> should do the same thing, so I used that, and indeed, it made a whole 
> lot of difference. Now, by background image spans two screens, uhm that 
> looks weird... :-) I think I liked the behaviour when it was 
> misconfigured better...
> 
> > That's for the XF86config.
> > With all this configured, the 'multiple monitors' option is now
> > visible in: control center -> peripherals -> display
> 
> Yup, I see that too, but if I have understood the KDE folks correctly, 
> that's just a small part of the new kcontrol modules. A big part is 
> what you're supposed to find if you go Control Center -> Desktop -> 
> Multiple Monitors, and that's something I still do not see... 
> 
> Admittedly, it seems to make it more and more likely that it is a 
> configuration problem, and so it may be OK to close the bug as invalid 
> and take the discussion elsewhere. Maintainers, please speak up and say 
> so if you think so. But since there still seems to be something 
> missing, I'm continuing... 
> 
> Best,
> 
> Kjetil
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: