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 664480 - white screen on second monitor when using two xsessions
white screen on second monitor when using two xsessions
Status: RESOLVED WONTFIX
Product: nautilus
Classification: Core
Component: Desktop
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-21 15:13 UTC by Pedro Villavicencio
Modified: 2014-08-10 15:03 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-11-21 15:13:45 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/885989

"If enable dual head mode (two X screens), the second monitor went white after login . After tracking the gnome-session, it is caused by running "nautilus -n" for this configuration. And if kill the nautilus process, the desktop showed up normally on second screen."

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/885989/+attachment/2590318/+files/nautilus.patch

"I tried to fix the problem, and my fix seems to be working."

users on the downstream bug reported that the patch worked fine for them
Comment 1 Sebastien Bacher 2011-11-24 14:24:22 UTC
ok, alex said that "we don't want to construct a new object each time, rather we want one per screen" so that needs some work, I've pinged the submitter on launchpad to see if he's interested to update his patch for that
Comment 2 Pedro Villavicencio 2011-11-24 14:29:55 UTC
Ok so the bug is there, marking this as NEW and waiting for the new patch from the submitter on lp. thanks a lot.
Comment 3 georgopl 2012-01-19 15:22:33 UTC
I just want to mention that I am also affected by this bug.
Comment 4 zoubidoo 2012-02-01 18:46:13 UTC
alex: "we don't want to construct a new object each time, rather
we want one per screen" 
Sebastien: [the patch] needs some work, I've pinged the submitter on
launchpad to see if he's interested to update his patch for that

This patch works even if it isn't perfect.  Since the bug affects quite a few people can we accept this suboptimal patch for now and leave improvements until someone has time to look at it?  That seems more practical than just leaving people stuck with the problem.
Comment 5 georgopl 2012-02-24 22:49:20 UTC
one other thing that i noticed, is that :

1. start  a nautilus window on screen :0.0 
2. go to the second screen
3. start a nautilus windows on screen :0.1

the window appears on the first screen :0.0 . Also, the reverse occurs. 

expected behaviour: the window should appear on the screen that it has been called from, i.e. the second window should appear on screen :0.0 (and the reverse)
Comment 6 Haakon Løtveit 2012-03-25 08:22:08 UTC
I have the same problem.
I don't know if this helps, but when I did killall nautilus, and then ran nautilus in the terminal I got the following warnings:

haakon@Haakon-Desktop:~$ killall nautilus
haakon@Haakon-Desktop:~$ nautilus 
Initializing nautilus-gdu extension

** (nautilus:2626): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS

** (nautilus:2626): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS

** (nautilus:2626): WARNING **: Can not get _NET_WORKAREA

** (nautilus:2626): WARNING **: Can not determine workarea, guessing at layout
^C
haakon@Haakon-Desktop:~$ 

Hope this helps somehow.
Comment 7 Daniel 2012-05-16 04:13:16 UTC
I am getting the exact same issue as Haakon. 12.04 64bit w/ GeForce 7800 GT. Using WAC cintiq21ux and dell 2405fpw monitors.
Comment 8 Alberts Muktupāvels 2012-12-05 15:07:38 UTC
(In reply to comment #1)
> ok, alex said that "we don't want to construct a new object each time, rather
> we want one per screen" so that needs some work, I've pinged the submitter on
> launchpad to see if he's interested to update his patch for that

I have 4 screens, wanted to know how many times constructor will be called with this patch. Added 2 lines to nautilus_desktop_background_constructor before return:

GdkScreen *screen = gtk_widget_get_screen(singleton->details->widget);
g_printerr("Desktop background constructed for screen %i!\n", gdk_screen_get_number(screen));

After building and installing new packages, when i run nautilus from terminal i got 4 lines:
Desktop background constructed for screen 0!
Desktop background constructed for screen 1!
Desktop background constructed for screen 2!
Desktop background constructed for screen 3!

So it seems that submitted patch already constructs new object only once per screen! Or am I missing something?
Comment 9 Bill Turner 2013-02-14 15:05:59 UTC
What is the status on this fix?

While there are only "7" subscribed to this bug, there are at least "40" subscribed to another bug that is pointed to this one.  I have also found a number of other "similar" bugs that should probably be pointed to this bug as well.

Until this fix is out of the way, other problems/issues with two separate xscreens using a dual-head NVidia video card cannot be resolved.

It has been almost three years now, since I had the full use of my multiple monitor setup.

1) I have two relatively high-end NVidia video cards, both of which are dual-port cards.

2) The first card has a pair of 1440x900 LCD screens attached, run as a single desktop.

3) The second card would normally have a Matrox triple-to-go adapter, which can control three separate monitors, as a single desktop. The Matrox adaptor would normally be connected to one display port, and a 1024x768 monitor woulds be connected to the other port.

   Currently I only have the single 1024x768 lcd monitor attached, which I would prefer to use as a separate X-screen with its own set of multiple logical workspaces.

Because of this bug, and possibly others, I can no longer configure my monitors the way I want them as a multiple set of separate X-screens, and instead am forced to configure them as a single desktop...  ...when I switch workspaces, I must then move some application windows to the new desktop, just to be able to function.

Please give some priority to accepting this patch "as is" and then modifing it later for performance enhancements if they are really required.

While I am an experienced programmer (45+ years), I am not a "C" programmer, nor an experienced Linux patch applier, so I am not able to apply the fix for myself, and am, therefore, forced to wait for the maintainers to apply them for me....

Thank you.

/s/ Bill Turner, wb4alm
Comment 10 António Fernandes 2013-03-08 18:47:55 UTC
NautilusDesktopBackground has been removed in 3.7: https://git.gnome.org/browse/nautilus/commit/?id=372c60d3f8590280df23f457a67652adec369697

Does it fix this bug?
Comment 11 James M. Leddy 2013-05-09 15:59:16 UTC
(In reply to comment #10)
> NautilusDesktopBackground has been removed in 3.7:
> https://git.gnome.org/browse/nautilus/commit/?id=372c60d3f8590280df23f457a67652adec369697
> 
> Does it fix this bug?

That actually made things worse to where we have a white background on both. There are more details in the following launchpad bug:

https://bugs.launchpad.net/ubuntu-gnome/+bug/1159430
Comment 12 Alberts Muktupāvels 2014-08-10 15:03:22 UTC
I am closing this bug as wontfix:
1) Nautilus does not draw background anymore.
2) Multi-screen support has been removed from GTK+.