After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 164482 - Drawer popup from :0.1 pops up at :0.0
Drawer popup from :0.1 pops up at :0.0
Status: RESOLVED DUPLICATE of bug 114842
Product: gnome-panel
Classification: Other
Component: panel
2.8.x
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-18 16:18 UTC by Geir Asle Borgen
Modified: 2005-01-18 16:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Geir Asle Borgen 2005-01-18 16:18:09 UTC
Distribution: Debian 3.1
Package: gnome-panel
Severity: normal
Version: GNOME2.8.1 2.8.x
Gnome-Distributor: Debian
Synopsis: Drawer popup from :0.1 pops up at :0.0
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
Bugzilla-Version: 2.8.x
Description:
Description of Problem:
When I make a drawer on the gnome-panel on :0.1 (Screen 1), and click on
it the content of the drawer pops up on :0.0 (Screen 0)

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
Every time!

Additional Information:
I am running a Debian Sid (unstable) whit gnome-2.8.1.5, and using
Sawfish-1.3.1 (in sted of Metasity-2.8.8) whit the option --multihead
(dual screen). Yes, I do know that --multihead is at your one risck and
so on. The problem whit the drawer is the same if I run Metacity in sted
of Sawfish.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-18 11:18 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Vincent Untz 2005-01-18 16:24:43 UTC
Fixed in 2.9.x

*** This bug has been marked as a duplicate of 114842 ***