Bug 35353 - fullscreen mode (konqueror) b0rken on session restart
Summary: fullscreen mode (konqueror) b0rken on session restart
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: dualhead (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-26 09:48 UTC by Unknown
Modified: 2007-12-18 12:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2001-11-26 09:47:07 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kwin
Version:           KDE 2.2.2 
Severity:          normal
Installed from:    Debian Packages
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

I am using KDE 2.2.2 with two monitors with two independant desktops (I configured XFree86 4.1 this way). Perhaps this occurs only with two monitors.

To reproduce:

Start a konqueror in fullscreen mode (C-A-F) (I did this on the secondary monitor).
Then exit KDE. Relogin.
Now you have a Konqueror window that has moved about a quarter down and to the right without window border without menu not accepting keystrokes not movable (not even with Alt-+Mouse) not killable (C-A-Esc doesn't work strangely).

Actually C-A-Esc shows the skull cursor but when I click it kills the window on the _first_ monitor which was under the coordinates the mouse was but the mouse cursor was on the second monitor.

If this is due to KDE's non-Xinerama support (I think Debian's package mainateiner did not compile this in by default due to license problems) then please add a sort of disclaimer stating something like "You are running multiple monitors but haven't compiled KDE with Xinerama support. This might lead to unexpected behaviour of your desktop" at login. It took me quite a bit of time to figure out that Xinerama must be treated specially at all ...


Thanks a lot!

Jens Benecke


(Submitted via bugs.kde.org)
Comment 1 Cristian Tibirna 2001-12-02 02:16:11 UTC
Grrhm! Could you please find out and let me know what kind of license problems 
compiling with Xinerama poses???? First time I hear about this.

As about the bug itself I write it down and I will make sure to check it out 
ASAP (when I get my second video card - burned - replaced).

Thanks
-- 
Cristian Tibirna .. tibirna@sympatico.ca
PhD Student .. ctibirna@giref.ulaval.ca .. www.giref.ulaval.ca/~ctibirna
KDE contact - Canada .. tibirna@kde.org .. www.kde.org
Comment 2 Jens Benecke 2001-12-02 15:13:37 UTC
--hoZxPH4CaxYzWscb
Content-Type: multipart/mixed; boundary="iFRdW5/EC4oqxDHL"
Content-Disposition: inline

--iFRdW5/EC4oqxDHL
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat Dec 01 2001 at 09:16:11PM -0500 Cristian Tibirna wrote:

> Grrhm! Could you please find out and let me know what kind of license
> problems compiling with Xinerama poses???? First time I hear about this.
> As about the bug itself I write it down and I will make sure to check it
> out ASAP (when I get my second video card - burned - replaced).

Hi

I attached a related post from the debian-kde mailing list. It seems it's
rather a Debian policy issue and the X guys are to be blamed not the KDE
team.
=20
But I'd appreciate any help to resolve this ;)


--=20
Jens Benecke =B7=B7=B7=B7=B7=B7=B7=B7 http://www.hitchhikers.de/ - Europas =
Mitfahrzentrale

"... da=DF hotmail.com vom Code Red befallen wurde und tagelang lahm lag
hatte aber auch seine positiven Seiten: Die Verbreitung von Sircam wurde
merkbar verlangsamt."-- ZDNet Editorial sinngem=E4=DF

--iFRdW5/EC4oqxDHL
Content-Type: message/rfc822
Content-Disposition: inline

>From jens  Mon Sep 24 02:15:27 2001
Received: from localhost ([127.0.0.1])
by server.zuhause.de with esmtp (Exim 3.22 #1 (Debian))
id 15lJPD-0007tL-01
for <jens@localhost>; Mon 24 Sep 2001 02:15:27 +0200
Received: from pop.kundenserver.de
by localhost with POP3 (fetchmail-5.8.3)
for jens@localhost (single-drop); Mon 24 Sep 2001 02:15:27 +0200 (CEST)
Received: from [216.234.231.6] (helo=murphy.debian.org)
by mxng02.kundenserver.de with smtp (Exim 3.22 #2)
id 15lJKw-00044u-00
for kde@jensbenecke.de; Mon 24 Sep 2001 02:11:03 +0200
Received: (qmail 24941 invoked by uid 38); 24 Sep 2001 00:01:25 -0000
X-Envelope-Sender: rkrusty@tdyc.com
Received: (qmail 24453 invoked from network); 24 Sep 2001 00:01:20 -0000
Received: from johnson.mail.mindspring.net (207.69.200.177)
  by murphy.debian.org with SMTP; 24 Sep 2001 00:01:20 -0000
Received: from tootie.covert.tdyc.com (pool-63.50.169.196.dnvr.grid.net [63.50.169.196])
by johnson.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id UAA29244
for <debian-kde@lists.debian.org>; Sun 23 Sep 2001 20:01:19 -0400 (EDT)
Received: by tootie.covert.tdyc.com (Postfix from userid 1000)
id 5F1EB232AB; Sun 23 Sep 2001 18:01:17 -0600 (MDT)
Date: Sun 23 Sep 2001 18:01:17 -0600
From: "Ivan E. Moore II" <rkrusty@tdyc.com>
To: debian-kde@lists.debian.org
Subject: Re: xinerama
Message-ID: <20010923180117.C32645@tdyc.com>
References: <E15kg2s-0007kU-00@bishop.dhs.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E15kg2s-0007kU-00@bishop.dhs.org>
User-Agent: Mutt/1.3.22i
Resent-Message-ID: <Aaxi7C.A.BFG.Vfnr7@murphy>
Resent-From: debian-kde@lists.debian.org
X-Mailing-List: <debian-kde@lists.debian.org> archive/latest/4503
X-Loop: debian-kde@lists.debian.org
Precedence: list
Resent-Sender: debian-kde-request@lists.debian.org
Resent-Bcc:
Resent-Date: Mon 24 Sep 2001 02:11:03 +0200

On Sat Sep 22 2001 at 12:18:46AM -0600 David Bishop wrote:
> Speaking of 2.2.1 does xinerama work for anyone else after upgrading?  It's 
> not even an option in window behavior-> advanced anymore.  And judging by 
> the behavior (bad old maximize across both screens) I would guess it isn't 
> working.  Did Ivan forget to compile --with-xinerama?  Hrrm well I can wait 
> until Monday for him to fix it....

Ok...let me see if I can partially explain this.  In order to include
Xinerama support one must link to a static library  libXinerama.a since
it is not provided as a shared object.  Unfortunaly this means compiling
in PIC code into a shared object which is a no-no and against Debian
policy.   If you want to know the pro's con's and the why's on all of
this read through the debian-devel mailing list archives for the past couple
months..you'll see several thread on this.  Originally I found out about
these problems when hppa tried building kdelibs.  hppa's compiler refused
to deal with it and thus a bug report was born.  I originally deal with
this by doing a "if arch is hppa don't compile in xinerama support" however
after reading the discussion on all of this I decided the "right" solution
was to not include xinerama support at this time.  Once the Xinerama lib's
are provided as shared objects I'll enable Xinerama support within the
kde packages.  

Ivan

-- 
----------------
Ivan E. Moore II
rkrusty@tdyc.com
http://snowcrash.tdyc.com
GPG KeyID=90BCE0DD
GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD


-- 
To UNSUBSCRIBE email to debian-kde-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


--iFRdW5/EC4oqxDHL--

--hoZxPH4CaxYzWscb
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: Weitere Infos: siehe http://www.gnupg.org

iD8DBQE8CkUh153rQBa8U44RAubJAJ0XlVSA0XxBMhFa0a50ja61svO7dgCePFAz
ZuYw3yVxO6B1ZgSexLpSVhc=
=EaXY
-----END PGP SIGNATURE-----

--hoZxPH4CaxYzWscb--
Comment 3 Stephan Kulow 2004-05-24 10:26:34 UTC
Replaced kde@jensbenecke.de with null@kde.org due to bounces by reporter
Comment 4 Lubos Lunak 2007-12-18 12:09:11 UTC
No reporter, no bug.