Separate X-screen, apps launched from 2nd screen appear on first screen

[Ng Oon-Ee]

My system is using NVidia's separate X-screen instead of TwinView. If I click Places->Home Folder in the 2nd screen it opens in the first screen. This is 100% reproducible.

Same behaviour observed if running
DISPLAY=:0.1 nautilus --browser
or if running from Alt-F2

However, for gnome-terminal, running from the menus opens it in the wrong (first) screen, but running
DISPLAY=:0.1 gnome-terminal
or running from Alt-F2 opens it in the correct (2nd) screen.

Firefox/thunderbird open properly in the 2nd screen in all cases. Compiz-config settings manager has same behaviour as gnome-terminal. Problem seems to be non-app specific.

http://ubuntuforums.org/showthread.php?t=1089578 shows another user with the same problem. May be linked to the binary nvidia, am unable to test without since I'm not aware of any way to get separate X with nv or mesa.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: ASUSTeK Computer Inc. Device [1043:1517]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 9300M G [10de:042e] (rev a1)
     Subsystem: ASUSTeK Computer Inc. Device [1043:17c2]

[Ng Oon-Ee (ngoonee)]

Though the bug has been marked as nvidia (and it does, since only nvidia AFAIK can have separate x-screens), I've noticed that the apps affected seem to be only those specific to ubuntu. Apps that are more generic/cross-platform (openoffice, matlab, firefox, thunderbird, etc.) seem to be unaffected. Amarok is affected, as well as most of the default apps from the menus (though as previously mentioned, some work IF run from alt-F2 or terminal).

Can no-one confirm this? Since these same drivers work with Intrepid, perhaps the bug should be assigned specifically to Jaunty (or to the new xorg-server version being used).

Please request any information required. Since this isn't a crash I'm really at a lost with what else I can post concerning this bug.

[Ng Oon-Ee (ngoonee)]

Just did some more checking. As far as I can see, nautilus is the ONLY app that cannot be forced to launch on display 0.1, all the other apps I've tried (most of the default apps in a new install) launch on the wrong screen from the gnome-panel menu but correctly from terminal or even on the correct screen if DISPLAY=:0.1 is explicitly set.

I believe this bug to be in gnome-panel or nautilus, based on the above rudimentary testing.

[Bryce Harrington (bryce)]

Hi ngoonee,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Gord Allott (gordallott)]

I can confirm this on a geforce 6600 with the 180 series drivers in jaunty. applications loaded on the second xserver screen show up on the first - makes simple things like trying to use my tv-out to watch a movie impossible.

attached xorg.conf and lspci output follows:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge [1106:3205]
 Subsystem: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge [1106:3205]
 Flags: bus master, 66MHz, medium devsel, latency 8
 Memory at c0000000 (32-bit, prefetchable) [size=256M]
 Capabilities: <access denied>
 Kernel driver in use: agpgart-via
 Kernel modules: via-agp

00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198]
 Flags: bus master, 66MHz, medium devsel, latency 0
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 Memory behind bridge: e0000000-e2ffffff
 Prefetchable memory behind bridge: d0000000-dfffffff
 Capabilities: <access denied>
 Kernel modules: shpchp

00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
 Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
 Flags: bus master, medium devsel, latency 32, IRQ 21
 I/O ports at d000 [size=32]
 Capabilities: <access denied>
 Kernel driver in use: uhci_hcd

00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
 Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
 Flags: bus master, medium devsel, latency 32, IRQ 21
 I/O ports at d400 [size=32]
 Capabilities: <access denied>
 Kernel driver in use: uhci_hcd

00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
 Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
 Flags: bus master, medium devsel, latency 32, IRQ 21
 I/O ports at d800 [size=32]
 Capabilities: <access denied>
 Kernel driver in use: uhci_hcd

00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82) (prog-if 20)
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7340]
 Flags: bus master, medium devsel, latency 32, IRQ 21
 Memory at e3000000 (32-bit, non-prefetchable) [size=256]
 Capabilities: <access denied>
 Kernel driver in use: ehci_hcd

00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
 Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
 Flags: bus master, stepping, medium devsel, latency 0
 Capabilities: <access denied>
 Kernel modules: i2c-viapro, via-ircc

00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7340]
 Flags: bus master, medium devsel, latency 32, IRQ 20
 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
 [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
 [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
 [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
 I/O ports at dc00 [size=16]
...

[Gord Allott (gordallott)]

attaching xorg log

[Ng Oon-Ee (ngoonee)]

My lspci -vvnn is attached here.

[Ng Oon-Ee (ngoonee)]

This is my Xorg.0.log, AFTER reproducing the issue.

[Ng Oon-Ee (ngoonee)]

My Xorg.0.log.old, in case its in any way useful.

[Ng Oon-Ee (ngoonee)]

My xorg.conf. Basically a typical dual-monitor setup, additional stuff for my touchpad (turning SHMConfig on), no Xinerama. The two screens are put far apart from each other, so that the mouse does not cross over, I use mouse-switchscreen to accomplish that.

Please indicate if more information is needed. Sorry for the delay, the new udev screwed my install up, had to regenerate the initrd.

[timaba (timaba)]

I have the same problem, but Nvidia 8400M GS. I will post xorg and the other stuff later.

[Jnifoo (jni)]

Using Separate X Screen under Ubuntu 8.10 (x86) with no problem at all with the proprietary driver installed via apt-get.

But, with 9.04 beta (amd64), after a fresh install, the Separate X Screen presented the bug reported here.

The only app I can open on the Screen 1, with a keyboard dedicated key, is the terminal. All other apps launch with the dropdown menu or desktop icons from the Screen1 opens in the Screen0 (so the screen1 is useless !).

Tried with the nvidia driver packed for Jaunty (180.37). Then today, deinstall it and used the last nvidia driver from the nvidia website (180.44). Exactly same bug.

nota: the XTwinView is working with both version of nvidia driver.
nota: trying with an absolute placement for both screen do not help. it is the same problem as the absolute placement for screen0 then placing the screen1 on the right of in the xorg.conf.

[Jnifoo (jni)]

here is the xorg.conf

[Jnifoo (jni)]

here is the xorg.log after a fresh reboot

[Leandro Carneiro (leotavaneiro)]

Well, I am with the same problem. I am using Jaunty beta, with Nvidia driver 180.37.

I really believe this is a gnome problem. Most reproductive with nautilus because it refuses to open on the secondary screen.

I hope you guys fix this fast....

[Leandro Carneiro (leotavaneiro)]

My xorg.conf

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[Jnifoo (jni)]

Hi,
Bug still present after updated my desktop to the new package and
activating the Separate X-Screen via nvidia-settings.
Regards
Jnifoo

Bryce Harrington a écrit :
> [This is an automated message]
>
> In Jaunty (9.04), we have just updated to the latest
> nvidia-graphics-drivers-180 package from nVidia, version 180.44.
>
> This package provides fixes for a large number of bugs, and we need your
> assistance in testing if it fixes the issue you reported.
>
> To do this, please do the following:
>
> a. Update to the 180.44 version of -nvidia using your favorite update
> method
>
> b. Attempt to reproduce your bug
>
> c. If your bug still remains, please simply reply to this email
> indicating so.
>
> d. If your bug is now solved, you can help us by setting your bug
> report to Fix Released:
> * In launchpad, go to your bug report
> * Click on the downward pointing arrow under Status
> * Set the Status field to 'Fix Released'
> * Comment on the change, such as, 'Verified fixed in 180.44'
> * Click 'Save Changes'
>
> e. If the original problem is solved but there are now other problems,
> please close the original bug and open new ones for those issues.
>
> Thank you!
>
> For details on the changes in this version of -nvidia, please see:
>
> http://www.nvidia.com/object/linux_display_ia32_180.44.html
>
>

[Ng Oon-Ee (ngoonee)]

Hi, this bug still remains. Even in version 185.13 which I'm using on my
Arch Linux install.

Bryce Harrington wrote:
> [This is an automated message]
>
> In Jaunty (9.04), we have just updated to the latest
> nvidia-graphics-drivers-180 package from nVidia, version 180.44.
>
> This package provides fixes for a large number of bugs, and we need your
> assistance in testing if it fixes the issue you reported.
>
> To do this, please do the following:
>
> a. Update to the 180.44 version of -nvidia using your favorite update
> method
>
> b. Attempt to reproduce your bug
>
> c. If your bug still remains, please simply reply to this email
> indicating so.
>
> d. If your bug is now solved, you can help us by setting your bug
> report to Fix Released:
> * In launchpad, go to your bug report
> * Click on the downward pointing arrow under Status
> * Set the Status field to 'Fix Released'
> * Comment on the change, such as, 'Verified fixed in 180.44'
> * Click 'Save Changes'
>
> e. If the original problem is solved but there are now other problems,
> please close the original bug and open new ones for those issues.
>
> Thank you!
>
> For details on the changes in this version of -nvidia, please see:
>
> http://www.nvidia.com/object/linux_display_ia32_180.44.html
>
>

[Leandro Carneiro (leotavaneiro)]

The bug still remains to me too. Using Nvidia 180.44.
----
Leandro Tavares Carneiro
Analista de Suporte Linux/Unix

On Fri, Apr 3, 2009 at 1:31 AM, Ng Oon-Ee <email address hidden> wrote:

> Hi, this bug still remains. Even in version 185.13 which I'm using on my
> Arch Linux install.
>
> Bryce Harrington wrote:
> > [This is an automated message]
> >
> > In Jaunty (9.04), we have just updated to the latest
> > nvidia-graphics-drivers-180 package from nVidia, version 180.44.
> >
> > This package provides fixes for a large number of bugs, and we need your
> > assistance in testing if it fixes the issue you reported.
> >
> > To do this, please do the following:
> >
> > a. Update to the 180.44 version of -nvidia using your favorite update
> > method
> >
> > b. Attempt to reproduce your bug
> >
> > c. If your bug still remains, please simply reply to this email
> > indicating so.
> >
> > d. If your bug is now solved, you can help us by setting your bug
> > report to Fix Released:
> > * In launchpad, go to your bug report
> > * Click on the downward pointing arrow under Status
> > * Set the Status field to 'Fix Released'
> > * Comment on the change, such as, 'Verified fixed in 180.44'
> > * Click 'Save Changes'
> >
> > e. If the original problem is solved but there are now other problems,
> > please close the original bug and open new ones for those issues.
> >
> > Thank you!
> >
> > For details on the changes in this version of -nvidia, please see:
> >
> > http://www.nvidia.com/object/linux_display_ia32_180.44.html
> >
> >
>
> --
> Separate X-screen, apps launched from 2nd screen appear on first screen
> https://bugs.launchpad.net/bugs/339783
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[ueland (david-ueland)]

I'm having the same problem. Using Jaunty coupled with Nvidia 180.44. My graphics card is 9500GT

Attached lspci

xorg.conf
http://pastebin.ca/1388738

xorg.conf dist-upgrade
http://pastebin.ca/1388739

[Paul Gortmaker (paul-gortmaker)]

It appears that the discussion is inadvertently steering towards the nvidia drivers, however based on what I'm seeing myself (on my own machine) it really looks like a gnome panel thing -- where it simply isn't passing the required :0.1 onto the application(s), and so it just goes with the assumed :0.0 instead.

[Ng Oon-Ee (ngoonee)]

I would like to second Paul Gortmaker, this does not seem to be an nvidia bug, though it will only affect nvidia chips since I think only they use separate x-screens? Wonder how the nv drivers would handle it...

Anyhow, the issue may be more nautilus than gnome-panel, since I HAVE observed that starting things from cairo-dock opens them in the first screen as well, and I assume that cairo-dock would not be interacting with gnome-panel at all. Which leads me to conclude that if I replace nautilus with pcmanfm I could check out whether that's true.

Will try that out when I have the time to reboot into Jaunty.

[Joe MacDonald (joeythesaint)]

On Wed, Apr 15, 2009 at 8:02 PM, Ng Oon-Ee <email address hidden> wrote:

> I would like to second Paul Gortmaker, this does not seem to be an
> nvidia bug, though it will only affect nvidia chips since I think only
> they use separate x-screens? Wonder how the nv drivers would handle
> it...
>
> Anyhow, the issue may be more nautilus than gnome-panel, since I HAVE
> observed that starting things from cairo-dock opens them in the first
> screen as well, and I assume that cairo-dock would not be interacting
> with gnome-panel at all. Which leads me to conclude that if I replace
> nautilus with pcmanfm I could check out whether that's true.

Interesting. Not something I'd considered. Paul and I had been discussing
the problem the other day and I suggested it seemed to me like it was
gnome-panel because I also use Nautilus plugin scripts
(~/.gnome2/nautilus-scripts/) which include the attached script. If I use
the right-click popup menu on the desktop and select "command_prompt_here"
from the "Scripts" submenu, the terminal appears on the correct screen
(either :0.0 or :0.1, depending on where the right-click menu started) so
I'd assumed the information provided by the X server was correct and
Nautilus was interpreting it properly (or at least not mangling it before
the script got hold of it).

I'm not sure what to make of your observation, though. Maybe I want to go
back and re-evaluate what my Nautilus plugins are doing.

-J.

>
>
> Will try that out when I have the time to reboot into Jaunty.
>
> --
> Separate X-screen, apps launched from 2nd screen appear on first screen
> https://bugs.launchpad.net/bugs/339783
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Joe MacDonald
:wq

[timaba (timaba)]

I can confirm that it should be an gnome/nautilus bug. I am working now with Intrepid and the 180-nvidia driver, it totally works! I had the described bug with this driver under Jackalope.

[Ed Holdsworth (eholdsworth)]

I have the same problem. Using Ubuntu 9.04 RC. Two nVidia GeForce 7600 GT cards with latest nVidia drivers installed. I have two screens, screen 0 and screen 1. Most apps when launched from screen 1 show up on screen 0. Firefox does appear on the screen from which it is launched. However, if I launch Firefox from screen 1, I get an error message if I try to launch a new instance of Firefox from screen 0 and vice versa. I can only run Firefox on one screen although multiple instances of it can be run from that screen but none on the other. Hope this makes sense.

[Ng Oon-Ee (ngoonee)]

To Ed Holdsworth,

What you're describing is actually 2 different issues. Firstly is the issue this bug report concerns, of applications launching in the wrong screen. Firefox itself is not able to run two instances (unless you have two separate profiles that you're using), this is a limitation in Firefox, and I believe there was a bug open on this about a year ago, haven't kept track of it though. This is just to clarify and avoid confusion of the issue on this bug.

[moeilijk (cvdveer)]

Tried reverting to the nvidia 173.14.16 driver. It resulted in the same problem so the issue must have been present since that version or seems not nvidia related. Could not get the 96 version to run to try that one.
Playing around with dual screens and resolutions I had to reset the gnome-panel settings several times so my suspicion is that way since Intrepid worked like a charm tweaking these settings around.

[Psykotik (linux-ikiru)]

Same here. Just upgrade from Intrepid, where I had also the Nvidia 18x driver. Tried to revert back on jaunty to the 170x driver, no luck.

Here is my xorg.conf

[Psykotik (linux-ikiru)]

And here is my Xorg.0.log

[trudnai (tamas-rudnai)]

I have made a workaround for this problem using 'basch -c' in front of the command. See the original post here:

http://ubuntuforums.org/showpost.php?p=7145344&postcount=21

Cheers,
Tamas

[trudnai (tamas-rudnai)]

Just created a perl hack to modify the menu items to this "bash -c " workaround if anyone nterested.

http://ubuntuforums.org/showthread.php?p=7146630#post7146630

Thanks
Tamas

[Alex F (frase)]

I'm having the same problem, also using the repository's nvidia 180 drivers and a custom xorg.conf which defines separate X screens.

This might be related or might be a red herring, but since switching to Jaunty (clean install from Hardy), I also cannot get XTestFakeMotionEvent() (from the XTest library) to work. I have a small C program called "switchscreen" which uses that function to "warp" the mouse cursor between my two X screens. It worked fine in Feisty, Gutsy and Hardy; now in Jaunty, the cursor no longer moves.

[Ng Oon-Ee (ngoonee)]

With reference to Alex F's comment, I can confirm that the behaviour of switchscreen is a red herring. The breakage of XTestFakeMotionEvent() occured before the behaviour reported in this bug, on my system (Jaunty since alpha 4)

Alex F, I have modified switchscreen such that it works on my system, using XWarpPointer instead. If you don't feel like modifying the code for that, I could email my modified source code to you.

[Hugh Eaves (hugh-hugheaves)]

I think this is a gnome problem as well, not just nvidia. I have this same problem using an X config with an Intel display on :0.0 and a sisusb on display :0.1. This configuration worked fine in Intrepid, but since upgrading to Jaunty, gnome applications no longer open from the launcher on the :0.1 display. (However, firefox and some others will open fine on :0.1)

[Ng Oon-Ee (ngoonee)]

Thank you Hugh for confirming what I and some others have been suspecting. I'm not sure if I have to right to re-assign the suspected bug cause, but that's what I'm going to try to do.

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[Ng Oon-Ee (ngoonee)]

I'm not really sure what the common practice is here, but doesn't the oldest bug as indicated by bug number take precedence? Not that its very important.

[Sebastien Bacher (seb128)]

that doesn't really make a difference, the other bug was assigned earlier on the right component and already had a duplicate

[pkc (pkcinna)]

Connecting to remote desktop at ":0.1" in Jaunty shows shows the :0.0 screen so all I get is a bunch of vnc windows displaying nested duplicates. It worked correctly in Intrepid. I could connect to :0.1 using remote desktop from my computer :0.0 screen and start up a Hulu show for a TV in another room. I assume this is a gnome issue.

[Alex F (frase)]

This was first marked as a duplicate of 346964, which sounds like the same issue. However then both this(339783) and 346964 were marked as duplicates of 290935, which I'm not sure is correct, unless there's been a lot more diagnosis that doesn't appear in the comments of any of those bugs.

This(339783) and 346964 describe applications started via gnome-panel launchers being assigned to the wrong X screen, which is especially annoying because windows cannot be dragged between X screens the way they can with TwinView or Xinerama. Bug 290935 describes all the gnome-panels from multiple X screens being moved to one screen at boot.

I think these are separate issues, because I remain affected by this(339783) and 346964 but I have never experienced 290935. My gnome-panels themselves all stay on the correct screen across multiple reboots; it is only the application windows launched from them that appear on the wrong screen for me. Can anyone else affected by this comment on whether this is actually a duplicate of 290935?

[Brian J. Murrell (brian-interlinx)]

On Tue, 2009-05-12 at 13:39 +0000, Alex F wrote:
> I think these are separate issues, because I remain affected by
> this(339783) and 346964 but I have never experienced 290935. My gnome-
> panels themselves all stay on the correct screen across multiple
> reboots; it is only the application windows launched from them that
> appear on the wrong screen for me.

What he said.

[Paul Gortmaker (paul-gortmaker)]

On Tue, May 12, 2009 at 9:39 AM, Alex F <email address hidden> wrote:
> *** This bug is a duplicate of bug 290935 ***
>    https://bugs.launchpad.net/bugs/290935
>
> This was first marked as a duplicate of 346964, which sounds like the
> same issue.  However then both this(339783) and 346964 were marked as
> duplicates of 290935, which I'm not sure is correct, unless there's been
> a lot more diagnosis that doesn't appear in the comments of any of those
> bugs.

Agreed -- unless someone knows that the same underlying problem is
creating these two completely different symptoms, but that sure isn't
captured in the text here....

>
> This(339783) and 346964 describe applications started via gnome-panel
> launchers being assigned to the wrong X screen, which is especially
> annoying because windows cannot be dragged between X screens the way
> they can with TwinView or Xinerama.  Bug 290935 describes all the gnome-
> panels from multiple X screens being moved to one screen at boot.
>
> I think these are separate issues, because I remain affected by
> this(339783) and 346964 but I have never experienced 290935.  My gnome-
> panels themselves all stay on the correct screen across multiple
> reboots; it is only the application windows launched from them that
> appear on the wrong screen for me.  Can anyone else affected by this
> comment on whether this is actually a duplicate of 290935?

I am seeing exactly what you see. Panels are fine; located where they
should be, but applications launched from the :0.1 panel appear on
the screen :0.0 -- and since I'm not using twinview/xinerama, I can't
simply drag the app back to the proper screen.

This most recent duplicate classification sure seems incorrect to me.

Paul.

[Stefano Angeleri (weltall)]

i agree with Paul Gortmaker above i don't get double panels in the first desktop they are properly in their own desktop only launching applications from them doesn't work correctly

[Ng Oon-Ee (ngoonee)]

Adding my support to the previous 4 posters.

[LaChild (shafer-w2002)]

I agree with the above. I only notice Bug 290935 when in twin view but not when using separate X sessions.

[keepitsimpleengr (keepitsimpleengineer)]

I would agree that this is a separate bug.

I gree with https://bugs.launchpad.net/~paul-gortmaker , https://bugs.launchpad.net/~weltall2, https://bugs.launchpad.net/~ngoonee, https://bugs.launchpad.net/~shafer-w2002, & al.

Attached are appropriate files archived.

[Alen (cshadow)]

I agree, this is a separate bug.
I would also comment that it exists in intrepid also in some way:
- starting nautilus from the menu on screen 1 - starts on screen 0
- dragging a application from the menu on screen 1 - shortcut appears on screen 0
Nvidia 7600 with repo 180 drivers, but it happened to me also with previous versions (17x).
Jaunty 64 bit - panels ok, apps starting os screen 0 in when launched on 1.

[Sebastien Bacher (seb128)]

could people stop commenting on this duplicate bug?

[Alex F (frase)]

I and the 7 folks who replied all agree that this bug's symptoms are not the same as bug 290935, and I can find no test results or developer's commentary in either bug report that indicates any connection. So, I have removed the duplicate setting.

[Sebastien Bacher (seb128)]

could one of those active commenter open a bug on bugzilla.gnome.org where the software writters will actually read about the issue?

[keepitsimpleengr (keepitsimpleengineer)]

Bug 581502 – Menu/panel items open on different screen 2009-05-05

http://bugzilla.gnome.org/show_bug.cgi?id=581502

Feel free to add your 2₵

[LaChild (shafer-w2002)]

There was one already opened on a duplicate launchpad bug with this issue...

See This Bug http://bugzilla.gnome.org/show_bug.cgi?id=580103

[Vincent Gerris (vgerris)]

Dear Sebastien,

In my opinion, this is not a duplicate?
This bug is about applications not starting on the right screen, the other
is specificly on loading.
Please don't simply try to close off bugs, although I know that is
important.
I do believe the bugs are related, unfortunately Gnome devs are silent.

regards,
Vincent

On Thu, May 14, 2009 at 12:26 AM, Sebastien Bacher <email address hidden>wrote:

> *** This bug is a duplicate of bug 290935 ***
> https://bugs.launchpad.net/bugs/290935
>
> could people stop commenting on this duplicate bug?
>
> --
> Separate X-screen, apps launched from 2nd screen appear on first screen
> https://bugs.launchpad.net/bugs/339783
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 290935).
>
> Status in “gnome-desktop” source package in Ubuntu: New
> Status in “gnome-panel” source package in Ubuntu: Invalid
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: New
>
> Bug description:
> My system is using NVidia's separate X-screen instead of TwinView. If I
> click Places->Home Folder in the 2nd screen it opens in the first screen.
> This is 100% reproducible.
>
> Same behaviour observed if running
> DISPLAY=:0.1 nautilus --browser
> or if running from Alt-F2
>
> However, for gnome-terminal, running from the menus opens it in the wrong
> (first) screen, but running
> DISPLAY=:0.1 gnome-terminal
> or running from Alt-F2 opens it in the correct (2nd) screen.
>
> Firefox/thunderbird open properly in the 2nd screen in all cases.
> Compiz-config settings manager has same behaviour as gnome-terminal. Problem
> seems to be non-app specific.
>
> http://ubuntuforums.org/showthread.php?t=1089578 shows another user with
> the same problem. May be linked to the binary nvidia, am unable to test
> without since I'm not aware of any way to get separate X with nv or mesa.
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960
> Memory Controller Hub [8086:2a00] (rev 03)
> Subsystem: ASUSTeK Computer Inc. Device [1043:1517]
> 01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 9300M
> G [10de:042e] (rev a1)
> Subsystem: ASUSTeK Computer Inc. Device [1043:17c2]
>
>

[Sebastien Bacher (seb128)]

gnome-desktop is a library and the about GNOME dialog, nothing to do with this issue

[Simon Lees (theleesy)]

It Say's here to only comment if you think its a duplicate but i can't see anywhere else to add comments / additional info about the First bug.

I just thought i'd point out i have had this same issue running Mandriva 2009 Spring and Sabayon 4.2 running a 7800GT with Gnome i did notice in Sabayon that i can get around this by Right clicking on the second monitors desktop opening a terminal and launching the app from there it will launch on the second display

[Vincent Gerris (vgerris)]

It might be a gnome-panel bug:
http://bugzilla.gnome.org/show_bug.cgi?id=580103

For that, a patch is supplied on the bottom of the page.
I have no clue how to get it in a 9.04 package, anyone?

[Vincent Gerris (vgerris)]

Thanks to midnightflash and keepitsimpleengr, here are some pretty nice instructions to get it fixed.

Why on Earth is this not available in update manager???

https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380

It worked for me, thank you all for your support!

[Leandro Carneiro (leotavaneiro)]

Hello:
I have good news for you. Last week, I have Order china 22
Products:<Philips 52PFL9703D/10 LCD TV 52 >
I have completed bank transfer payment.
I've received the item today this website:www.SLEUBO0.com
It's amazing! The item is original, brand new and has high quality,
but it's much cheaper. I'm pleased to share this good news with you!
I believe you will find what you want there and have an good experience
on shopping from them.
Regards!

mlnjnlkj8jio....妙

[Leandro Carneiro (leotavaneiro)]

http://russellash.id.au/wp-content/themes/classic/mylife.html

[Leandro Carneiro (leotavaneiro)]

http://196.214.136.122/hisword//images/site.html