540261 - Further SeaMonkey windows start at the wrong desktop

Status: RESOLVED INVALID

(SeaMonkey :: OS Integration, defect)

Description

[dolphin001]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.11) Gecko/20070217 Iceape/1.0.8 (Debian-1.0.8-4)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1

I use "Debian 5.0.3" with KDE 3.5.10 and "SeaMonkey 2.0.1" or
"SeaMonkey 2.0.2". My SeaMonkey resides in "/opt/seamonkey".

If I have a start link from the KDE desktop to start SeaMonkey
or if I have a KDE shortcut to start SeaMonkey, then as soon I
use one of these methods to start SeaMonkey, SeaMonkey behaves nasty
in conjunction with KDE desktops.

Example:

Via right mouse button, I klicked at the "K" menu Icon of KDE to get the
"Menu Editor". There, I generated a new Item with the following properties:

- Name: SeaMonkey
- Description: SeaMonkey
- Command: /opt/seamonkey/seamonkey
- Current shortcut key: Win + M

Now, I go to KDE desktop 5 and press Win+M.
A new SeaMonkey window appears at Desktop 5.

Then, I go to KDE desktop 6 and press Win+M.
A new SeaMonkey window appears at Desktop 5.

The problem is, that I expected that the new window
appears at desktop 6, but it stubbornly appears at
desktop 5.

Constraints
===========
1. If I start SeaMonkey from an xterm running bash, then this bug
   does not appear.

2. The bug appears in a time frame. Most systems I used to test it have a time
   slot of 20 minutes. Another system has a time slot of 60 seconds. I don't
   know what causes this time slot. When the time slot is expired, the bug
   does not appear until an entire restart of SeaMonkey (close all SeaMonkey
   windows and start again with openign SeaMonkey windows).

More details
============
I hat posted at the following forums about this bug:
http://forums.mozillazine.org/viewtopic.php?f=40&t=1696825&p=8467275#p8467275
http://debianforum.de/forum/viewtopic.php?f=29&t=117387

I made a downloadable test linux Debian 5.0.3 that has this bug with
a time slot of 60 seconds.

http://www.jumping-blue-turtle.com/seamonkey-bug/instructions.txt

The 401 MB 7z archive can be downloaded until January 21 @ 03:51 PM MST
at transferbigfiles.com. This was the most convenient service that I found
to host large files, but it hosts files only for 5 day.

Please ask me for details to reproduce this bug.

dolphin


Reproducible: Always

Steps to Reproduce:
1. Make a KDE shortcut or a KDE desktop link to SeaMonkey
2. Run the shortcut or link at one desktop
3. SeaMonkey starts at this desktop
4. Go to another desktop
5. Repeat step 2
Actual Results:  
New windows appear at the first desktop that was used to create the first
SeaMonkey window.

Expected Results:  
New windows appear at the current desktop.

This bug affects a SeaMonkey 2.0.1 that Idownloaded at the end of December
here:
http://download.mozilla.org/?product=seamonkey-2.0.1\&os=linux\&lang=en-US
If versions 2.0.1 updates itself to 2.0.2, then the Bug still is existing.

Comment 1

[dolphin001]

More details about this bug
===========================

- If I click with the middle mouse button on a link, then a new window
  opens. This new window appears at this desktop at which I opened the
  first window of SeaMonkey. I have to search all desktops and search
  for this new window.

- If I press Ctrl+N, then a new window
  opens. This new window appears at this desktop at which I opened the
  first window of SeaMonkey. I have to search all desktops and search
  for this new window.

- If I use my KDE-Shortcat Win+M, then a new window
  opens. This new window appears at this desktop at which I opened the
  first window of SeaMonkey. I have to search all desktops and search
  for this new window.

dolphin

Comment 2

[dolphin001]

Interestingly, this bug only occurs at "KDE 3.5".
Today, I tested it at Gnome, at Sawfish and some other window managers,
with the effect that this bug did not occur. Even if I run Sawfish
in combination with kicker (the panel of KDE 3.5.10), I could not
observe this bug.

There must be something special that only comes into effect
if both KDE 3.5 and SeaMonkey are running. But, what could this
be?

dolphin

Comment 3

[Frank Wein [:mcsmurf]]

btw: I asked some user of KDE 3.5 about this problem and he could not reproduce this problem.

Comment 4

[dolphin001]

Finding an accurate diagnosis should not fail because you merely cannot
reproduce the bug.

I you really want to reproduce the bug, I can provide you with a readily
installed Debian Linux:

- it is a Debian Lenny 5.0.3
- it comes with a freshly installed KDE 3.5.10 (I used apt-get)
- it contains an installed SeaMonkey (I used seamonkey-2.0.1.tar.bz2)
- I compressed this system into a 447 MB small 7-Zip archive

If you need this system to reproduce the bug, you can request it.
Either I deploy it at a free upload service like "www.transferbigfiles.com"
or I use MediaCenter of "www.gmx.de".

To let this readily installed Debian Linux run on your computer,
I made some instructions for you:
http://www.jumping-blue-turtle.com/seamonkey-bug/instructions.txt

For the case that you are afraid that I infiltrated malicious code
into this system:
- I do not do such things, because my interest is not to harm someone
  but rather to get bug free software
- you can check every bit of this system against MD5 and SHA1
- you can download these checksums from my web site (this web site contains
  my real name and my real address)
- if you do not even trust this web site:
  - I can e-mail you the checksums
  - we can arrange a phone call to make sure that the
    checksums are really provided by me in person (I speak English
    and German)

dolphin

Comment 5

[dolphin001]

(In reply to comment #4)
> For the case that you are afraid that I infiltrated malicious code
> into this system:
> - I do not do such things, because my interest is not to harm someone
>   but rather to get bug free software
> - you can check every bit of this system against MD5 and SHA1
> - you can download these checksums from my web site (this web site contains
>   my real name and my real address)
> - if you do not even trust this web site:
>   - I can e-mail you the checksums
>   - we can arrange a phone call to make sure that the
>     checksums are really provided by me in person (I speak English
>     and German)

- you do not have to connect the computer with the internet (so my
  system cannot act as a spam catapult or something)
- actually, all you need is:
  - a computer (provided with a CPU and with RAM)
  - a hard disk (internal or external; SATA, eSATA or USB)

dolphin

Comment 6

[Philip Chee]

If this only occurs with KDE 3.5 and not with other window managers then odds on it is a KDE WM bug. Please open a bug with the KDE issue tracker first.