dual screen all panels end up on one screen at startup

Bug #290935 reported by ldm
78
This bug affects 10 people
Affects Status Importance Assigned to Milestone
GNOME Panel
Expired
Medium
gnome-panel (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

On startup with a dual screen setup all four panels end up on screen 0. The panel were originally setup two to each monitor, one top and one bottom. I can set them up so they are correct but upon the next startup both are on the screen 0. I am running with a nvidia type card on a asus mother board. The problem is repeatable.

Revision history for this message
ldm (ldmaiden) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, that's an upstream issue and should be sent to bugzilla.gnome.org by somebody having a similar configuration who can reply to their comments

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
Pedro Villavicencio (pedro) wrote :

any news about this? did you opened a bug upstream? may you tell us the bug number ? thanks in advance.

Revision history for this message
ldm (ldmaiden) wrote : Re: [Bug 290935] Re: dual screen all panels end up on one screen at startup

No I did not open and upstream bug report. I am not sure how to do it.
I am attaching a copy of the last two days of my user.log file

Nov 20 16:56:23 ldm-desktop python: hp-makeuri[6352]: warning:
hp-makeuri should not be run as root.
Nov 20 16:56:23 ldm-desktop python: hp-makeuri[6522]: warning:
hp-makeuri should not be run as root.
Nov 20 16:56:23 ldm-desktop python: hp-makeuri[6522]: error: Device does
not support fax.
Nov 20 16:56:40 ldm-desktop pulseaudio[6624]: ltdl-bind-now.c: Failed to
find original dlopen loader.
Nov 20 16:56:40 ldm-desktop pulseaudio[6626]: main.c:
setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Nov 20 16:56:40 ldm-desktop pulseaudio[6626]: main.c:
setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Nov 20 16:56:45 ldm-desktop pulseaudio[6626]: module-x11-xsmp.c: X11
session manager not running.
Nov 20 16:56:45 ldm-desktop pulseaudio[6626]: module.c: Failed to load
module "module-x11-xsmp" (argument: ""): initialization failed.
Nov 20 16:58:10 ldm-desktop hp: io/hpmud/pp.c 627: unable to read
device-id ret=-1
Nov 20 16:58:12 ldm-desktop python: io/hpmud/pp.c 627: unable to read
device-id ret=-1
Nov 20 22:11:17 ldm-desktop bonobo-activation-server (ldm-15604): could
not associate with desktop session: Failed to connect to
socket /tmp/dbus-rAK2e8JJcv: Connection refused
Nov 20 22:11:22 ldm-desktop bonobo-activation-server (ldm-16130): could
not associate with desktop session: Failed to connect to
socket /tmp/dbus-rAK2e8JJcv: Connection refused
Nov 21 17:54:26 ldm-desktop python: hp-makeuri[6350]: warning:
hp-makeuri should not be run as root.
Nov 21 17:54:26 ldm-desktop python: hp-makeuri[6522]: warning:
hp-makeuri should not be run as root.
Nov 21 17:54:35 ldm-desktop python: hp-makeuri[6522]: error: Device does
not support fax.
Nov 21 18:04:33 ldm-desktop pulseaudio[6649]: ltdl-bind-now.c: Failed to
find original dlopen loader.
Nov 21 18:04:33 ldm-desktop pulseaudio[6651]: main.c:
setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Nov 21 18:04:33 ldm-desktop pulseaudio[6651]: main.c:
setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Nov 21 18:04:37 ldm-desktop pulseaudio[6651]: module-x11-xsmp.c: X11
session manager not running.
Nov 21 18:04:37 ldm-desktop pulseaudio[6651]: module.c: Failed to load
module "module-x11-xsmp" (argument: ""): initialization failed.
Nov 21 18:05:50 ldm-desktop hp: io/hpmud/pp.c 627: unable to read
device-id ret=-1
Nov 21 18:05:51 ldm-desktop python: io/hpmud/pp.c 627: unable to read
device-id ret=-1

On Fri, 2008-11-21 at 11:26 +0000, Pedro Villavicencio wrote:
> any news about this? did you opened a bug upstream? may you tell us the
> bug number ? thanks in advance.
>

Revision history for this message
ldm (ldmaiden) wrote :

I just filed a bug report at bugzilla

Bug 561964 – all panels endup on one screen in dual screen setup

On Fri, 2008-11-21 at 11:26 +0000, Pedro Villavicencio wrote:
> any news about this? did you opened a bug upstream? may you tell us the
> bug number ? thanks in advance.
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for sending the bug to GNOME

Changed in gnome-panel:
status: New → Triaged
Changed in gnome-panel:
status: Unknown → New
Revision history for this message
Ramon Casha (rcasha) wrote :

I have a similar problem, but it doesn't occur every time.

I have two screens - laptop at 1600x1024 and external at 1600x1200. Often at startup, both of my panels which are on the laptop screen end up on the external screen instead. Sometimes I restart X and they load correctly.

I also noticed that, when this happens, the wallpaper ends up the size of the laptop screen, rather than stretched across both screens, and the right-click only has an effect on that region.

I'm guessing that sometimes, Gnome does not find both screens immediately, so it sets the desktop size to the size of the only screen it finds and places all panels on it, then by the time everything is loaded both screens are available so that the panels end up on the leftmost screen.

I have Ubuntu 8.10, Intel Mobile GM965/GL960 onboard graphics chip

Added the above info to the Gnome bug report

Revision history for this message
Vincent Gerris (vgerris) wrote :

I reported it upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=580103

I also added a link to this post.
I hope it gets solved quickly :)!

Revision history for this message
Vincent Gerris (vgerris) wrote :
Revision history for this message
Stefano Angeleri (weltall) wrote :

it's fixed upstream can it be merged?
http://bugzilla.gnome.org/show_bug.cgi?id=580103

Revision history for this message
TJ (tj) wrote :

I've cherry-picked the upstream patch and added it to the package and it will be available from my PPA for testing.

Revision history for this message
TJ (tj) wrote :

Debdiff for Jaunty

Revision history for this message
Stefano Angeleri (weltall) wrote :

i've tried it. It seems to fix my problems with the toolbar but on the other hand it gives issue with archivers (i can't double click on the file, it never opens), chat applications or similar which allows to open links by selecting open with browser from a context menu (like xchat), ubuntuone (never opens the first registration window)...
I'll try reverting later in order to confirm this

Revision history for this message
Vincent Gerris (vgerris) wrote :

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!

Sebastien, can you explain how this can be pushed to be available in the update manager?
It is a PITA bug :)!

Revision history for this message
Sebastien Bacher (seb128) wrote :

The change has not been targetting to stable because nobody really worked on that, that's not optimal but

- the team is way understaffed for the number of bugs and don't manage to read everything so forget about backporting every change, the focus is usually on the next version (if you keep working on stable versions bugs don't get fixed in the current version and you create a situation where you keep working on old code rather than making new versions stable)
- the bug require a dual screen for testing which most of team members don't have
- the patch seems non trivial for a security update

I suggest working on a stable update candidate if somebody is interested, the bug has a good basis but the debdiff uses a ppa versioning and the bug lacks details in the summary about the version used, the issue and how the change adress it, then ubuntu-main-sponsors should be subscribed and the bug nominated for jaunty

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could somebody try if karmic fixes the issue too

Revision history for this message
gabrys (piotr-ubuntubugs) wrote :

I experience the same problem in experimental karmic (updated every day or two).

I have two screens: one laptop, second external monitor, which is bigger, and the panel, no matter what position I chose -- top, bottom, left, right -- always sit on my laptop screen. I want this top panel to be located at my top screen (the external one).

Revision history for this message
gabrys (piotr-ubuntubugs) wrote :

I found a way to set the monitor number on which to display the panel:

gconf-editor and in

/apps/panel/top_panel_screen0

change monitor from 0 to 1.

Still new apps open on the monitor 0 (the laptop screen), so this is partial solution, but nice anyway.

What I would like is to set the default monitor, that is the monitor that new apps are launched on (in KDE3 there was setting always run new apps on screen X or run new apps on the screen where the mouse pointer is -- that configuration was really nice). If we want to avoid configuration option and prefer magic, I would suggest, that the biggest screen is the default.

Revision history for this message
gabrys (piotr-ubuntubugs) wrote :

Actually metacity is smarter than I though before. It shows new windows on the display that was last clicked. This is nice.

Revision history for this message
Dindon (elizetxea) wrote :

I confirm that the update in my case it worked.

I Find that after the update occurs the following behavior as has been reported "weltall" in #13:

Applications like Chromium, Opera and others (NOT Firefox) appears that use "gnome-open" to open the downloaded files and launch links as "mailto:".
Failure occurs and the files and applications are not opened by the system.

Case 1:
1.- Launch Opera or Chromium.
2.- Download a file.
3.- Try open the file with the download manager.
3.- Nothing happens.

Case 2:
1.- Launch Opera or Chromium.
2.- Click on a link with "mailto:"
3.- Nothing happens.

If I run the applications (Chromium or Opera) in a terminal I can view the following error when I try to open a pdf file:
 "(acroread:5958): Gtk-WARNING **: " cannot open display: "

It is the same error as if I launch in a terminal "gnome-open":

      user@computer :~$ gnome-open anyfile.pdf
      user@computer :~$ (acroread:5958): Gtk-WARNING **: cannot open display:

Could be confirmed if the same applies to you.

Thank you for your contributions.

tags: added: patch-forwarded-upstream
Changed in gnome-panel:
importance: Unknown → Medium
Changed in gnome-panel (Ubuntu):
status: Triaged → Invalid
Changed in gnome-panel:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.