Bug 529398 - Regression: Twinview, can no longer drag panels, or create panels on separate monitors.
Summary: Regression: Twinview, can no longer drag panels, or create panels on separate...
Keywords:
Status: CLOSED DUPLICATE of bug 537959
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 11
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-16 16:00 UTC by Bill C. Riemers
Modified: 2010-01-25 15:52 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-25 15:50:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bill C. Riemers 2009-10-16 16:00:25 UTC
Description of problem:

The technique described at:

 http://www.lloydleung.com/2006/10/14/gnome-multiple-monitor-taskbar-window-listing/

no longer works.  Panels can not be dragged to an alternate manner.   To make this problem even more critical the Windows List component no longer lists windows on a separate monitor.

My desktop was working fine since I upgraded from Fedora 10, with twinview two monitors.   However, what happened is I accidentally logged in with my right monitor turned off.   So naturally gnome moved my right monitor's panel to my left desk top.   In the past when this happened I simply logged back in again and dragged the panel.   Now the panel can not be dragged, and if I create a new panel it can not be moved to the other monitor.

If I open a new window on my right monitor, or I drag one to my right monitor and then minimize the window, the window does not appear in my window's list.   So I constantly get errors like I can not start thunderbird because thunderbird is already running.

As a quick workaround I enabled Xinerana.   However, for me this is not a viable long term solution, because I have a two inch gap between monitors.   With Xinerana most windows will open spanning this gap, making it difficult or impossible to read.

Bill


Version-Release number of selected component (if applicable):

[docbill@hartnell ~]$ rpm -qa |grep gnome
gnome-applet-sensors-2.2.1-2.fc11.x86_64
gnome-panel-libs-2.26.3-1.fc11.x86_64
gnome-commander-1.2.8.2-1.fc11.x86_64
PolicyKit-gnome-libs-0.9.2-3.fc11.x86_64
libgnomeprint22-2.18.6-1.fc11.x86_64
gnome-python2-canvas-2.26.1-1.fc11.x86_64
compiz-fusion-gnome-0.7.8-8.fc11.x86_64
gnome-terminal-2.26.3.1-1.fc11.x86_64
NetworkManager-gnome-0.7.1-8.git20090708.fc11.x86_64
libgnomecanvas-devel-2.26.0-1.fc11.x86_64
gnome-media-libs-2.27.90.fix-1.fc11.x86_64
gnome-applet-music-2.5.1-2.fc11.x86_64
gnome-netstatus-2.26.0-1.fc11.x86_64
gnome-keyring-devel-2.26.3-1.fc11.x86_64
gnome-sharp-2.24.0-4.fc11.x86_64
gnome-python2-gtkhtml2-2.25.3-7.fc11.x86_64
gnome-mime-data-2.18.0-4.fc11.noarch
compiz-gnome-0.7.8-19.fc11.x86_64
gnome-mplayer-common-0.9.8-1.fc11.x86_64
gnome-bluetooth-2.27.8-3.fc11.x86_64
libgnomeui-2.24.1-1.fc11.x86_64
gnome-doc-utils-0.16.1-1.fc11.noarch
gnome-desktop-sharp-2.26.0-4.fc11.x86_64
gnome-vfs2-smb-2.24.1-2.fc11.x86_64
gnome-python2-gnome-2.26.1-1.fc11.x86_64
gnome-doc-utils-stylesheets-0.16.1-1.fc11.noarch
libgnomeprintui22-devel-2.18.4-1.fc11.x86_64
gnome-vfsmm26-2.26.0-1.fc11.x86_64
gnome-menus-2.26.2-1.fc11.x86_64
gnome-settings-daemon-2.26.1-11.fc11.x86_64
gnome-mag-0.15.7-1.fc11.x86_64
libgnome-devel-2.26.0-1.fc11.x86_64
gnome-python2-gconf-2.26.1-1.fc11.x86_64
gnome-mount-0.8-5.fc11.x86_64
gnome-python2-gnomevfs-2.26.1-1.fc11.x86_64
gnome-session-xsession-2.26.2-1.fc11.x86_64
gnome-screensaver-2.26.1-3.fc11.x86_64
gnome-packagekit-2.27.3-1.fc11.x86_64
libgnomekbd-2.26.0-1.fc11.x86_64
gnome-applet-timer-2.1.2-2.fc11.x86_64
gnome-python2-extras-2.25.3-7.fc11.x86_64
themes-backgrounds-gnome-0.5.1-2.fc11.noarch
libgnomecups-0.2.3-6.fc11.x86_64
gnome-disk-utility-libs-0.3-1.fc11.x86_64
PolicyKit-gnome-devel-0.9.2-3.fc11.x86_64
libgnomemm26-2.26.0-1.x86_64
libgnomeuimm26-2.26.0-1.fc11.x86_64
gnome-devel-docs-2.26.2-1.fc11.noarch
gnome-media-2.27.90.fix-1.fc11.x86_64
gnome-speech-0.4.25-2.fc11.x86_64
gnome-python2-2.26.1-1.fc11.x86_64
wireshark-gnome-1.1.3-1.fc11.x86_64
gnome-panel-2.26.3-1.fc11.x86_64
gnome-power-manager-2.26.4-3.fc11.x86_64
libgnomeprintui22-2.18.4-1.fc11.x86_64
gnome-python2-desktop-2.26.0-3.fc11.x86_64
nodoka-theme-gnome-0.3.90-3.fc11.noarch
gnome-vfs2-2.24.1-2.fc11.i586
gnome-device-manager-libs-0.2-4.fc11.x86_64
gnome-user-docs-2.26.2-1.fc11.noarch
gnome-theme-curvylooks-0.3-2.fc11.noarch
PolicyKit-gnome-0.9.2-3.fc11.x86_64
gnome-utils-2.26.0-1.fc11.x86_64
gnome-keyring-2.26.3-1.fc11.x86_64
gnome-keyring-pam-2.26.3-1.fc11.x86_64
gnome-pilot-devel-2.0.17-3.fc11.x86_64
gnome-icon-theme-2.26.0-2.fc11.noarch
libgail-gnome-1.20.1-2.fc11.x86_64
gnome-mplayer-0.9.8-1.fc11.x86_64
gnome-bluetooth-libs-2.27.8-3.fc11.x86_64
gnome-python2-gtksourceview-2.26.0-3.fc11.x86_64
fedora-gnome-theme-8.0.0-9.fc11.noarch
gnome-pilot-2.0.17-3.fc11.x86_64
gnome-python2-gnomeprint-2.26.0-3.fc11.x86_64
gnome-python2-bonobo-2.26.1-1.fc11.x86_64
libgnomeprint22-devel-2.18.6-1.fc11.x86_64
gnome-python2-applet-2.26.0-3.fc11.x86_64
gnome-system-monitor-2.26.1-2.fc11.x86_64
gnome-vfs2-obexftp-0.4-9.fc11.x86_64
gnome-user-share-2.26.0-3.fc11.x86_64
gnome-python2-libegg-2.25.3-7.fc11.x86_64
libgnome-2.26.0-1.fc11.x86_64
libopenraw-gnome-0.0.5-3.fc11.x86_64
libgnomecanvasmm26-2.26.0-1.fc11.x86_64
gnome-device-manager-0.2-4.fc11.x86_64
gnome-audio-2.22.2-4.fc11.noarch
gnome-session-2.26.2-1.fc11.x86_64
gnome-vfs2-devel-2.24.1-2.fc11.x86_64
gnome-desktop-2.26.3-2.fc11.x86_64
gnome-python2-gnomekeyring-2.26.0-3.fc11.x86_64
gnome-phone-manager-0.65-3.fc11.x86_64
gnomebaker-0.6.4-5.fc11.x86_64
gnome-vfs2-2.24.1-2.fc11.x86_64
gnome-panel-devel-2.26.3-1.fc11.x86_64
gnome-applets-2.26.3-1.fc11.x86_64
libgnomeui-devel-2.24.1-1.fc11.x86_64
gnome-python2-libwnck-2.26.0-3.fc11.x86_64
gnome-applet-netspeed-0.15.2-2.fc11.x86_64
gnome-themes-2.26.3-1.fc11.noarch
libgnomecanvas-2.26.0-1.fc11.x86_64
gnome-desktop-devel-2.26.3-2.fc11.x86_64
libgnome-2.26.0-1.fc11.i586
gnome-backgrounds-2.24.1-1.fc11.noarch

How reproducible:

100%

Steps to Reproduce:
1. Enable twin view
2. Try and create a panel on the second monitor.
3.
  
Actual results:

Panels can only be created on the primary monitor, and can only be positioned on that monitor.

Expected results:

Panel should be drag-able and creatable on both monitors.

Additional info:

Comment 1 Florent Le Coz 2009-10-21 15:48:56 UTC
Still a problem in fedora 12 beta.

Comment 2 Bill C. Riemers 2009-10-21 16:27:11 UTC
I found a somewhat better workaround is to list my monitors as if the are stacked vertically.   It gets confusing needing to move the mouse down the screen to move to the right, but then I do not get any pop-up windows between monitors, and somehow the "maximize" button knows to extend only the size of one monitor.

Bill

Comment 3 Bill C. Riemers 2009-10-21 16:37:35 UTC
I changed xorg.conf file "screen" section as follows:

Section "Screen"
    Identifier     "Screen0"
    Device         "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "Xinerama" "1"
    Option         "TwinViewXineramaInfoOrder" "DFP-0"
    Option         "NoTwinViewXineramaInfo" "False"
    Option         "metamodes" "CRT-0: 1280x1024_75 +0+0, CRT-1: 1280x1024_75 +1
280+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

This resolves all my problems, except the one reported in the subject line. I still can not move or create panels on my right monitor.

Bill

Comment 4 Matthew Carpenter 2009-11-23 18:32:32 UTC
Yep, I am having the same issue here.  Started with F-11 and continues in F-12.  It was really nice having a separate panel/window list for the second screen.  If this ability could be re-introduced it would be great.

Comment 5 Christopher Beland 2010-01-25 15:50:12 UTC

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

Comment 6 Christopher Beland 2010-01-25 15:52:28 UTC
Bug 494740 notes that panels *can* be moved with Alt + drag.


Note You need to log in before you can comment on or make changes to this bug.