On Saturday 24 of November 2007, Jason Stubbs wrote:
> There was a person (fm_) asking about the following bug on #kde4-krush.
>
> https://bugzilla.novell.com/show_bug.cgi?id=335530
>
> Apparently the issue has happened before with ksplashx and patched for.
>
> https://bugzilla.novell.com/show_bug.cgi?id=290988
> http://lists.opensuse.org/opensuse-commit/2007-07/msg00648.html
>
> The attached patch does essentially the same in Corona::loadDefaultSetup().
> This handles the desktop part, but kwin would also need to be updated to
> handle maximizing correctly.

 Please don't. There's no point in patching every single place, this needs to 
be handled in libraries. KSplashX is patched because it's directly using X 
libraries.

> Personally, I wonder if the Intel driver isn't just buggy...

 No, not really. It is a (mis)feature of supporting XRandr1.2. XRandr1.2 
provides info about every output, and SUSE has its X patched to also always 
enable another X output (which means the problem should be only SUSE-specific 
these days). It's got mainly something to do with laptops and external 
outputs, I don't know exactly, but the point is that you have your normal 
resolution and also 1024x768, sharing the same topleft corner. Now the 
problem is that Xinerama API is now only a wrapper around this and reports 
this as two screens even though it's practically only one screen (really 
smart from X people).

 Dirk Mueller will forwardport the Qt3 patch for #335530.

-- 
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak@suse.cz , l.lunak@kde.org
Lihovarska 1060/12   tel: +420 284 028 972
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http//www.suse.cz
_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel