And another spam comment added just before mine. Can somebody please do
something about these fake users?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346964
Title:
menu items selected from screen
Can someone take care of this previous spam post(er)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346964
Title:
menu items selected from screen 1 open on screen 0
--
ubuntu-bugs mailing list
ubu
** Changed in: glib
Importance: Unknown => Medium
** Changed in: gnome-panel
Importance: Unknown => Medium
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
If you have applied TJ's prior patch, step-by-step have been added at
https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380
to update to the latest patch using Synaptic.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this
I've repackaged my previous Jaunty libglibc package to use yakovlev's
patch since it seems to perform better than my original upstream-
backport patch (which came from grossly refactored code).
In particular, yakolev's patch doesn't cause the launching of external
applications to fail (e.g. double
Step by step instructions used to correct this problem are given in the
answer to the following question:
https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notifi
There are related questions on Launchpad about this issue:
https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/77380
https://answers.launchpad.net/ubuntu/+question/77467
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug
Any way I can get the new version on Jaunty, without having to recompile
the package?
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
the new version is in karmic now
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: glib
Status: Unknown => Fix Released
** Changed in: gnome-panel
Status: New => Fix Released
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which
Just to inform all that this has been fixed in latest glibc, I'm on Arch
Linux and we've already gotten the fix. For those using Ubuntu 9.04, I
doubt its coming your way due to the freeze policy Ubuntu has on its
releases (I think only security-related patches are released).
Anyway, the problem HA
I'm having this problem also. Running Jaunty, all up to date.
I notice that gnome-panel is being started up with arguments as follows:
gnome-panel --sm-config-prefix /gnome-panel-svkHHa/ --sm-client-id
103a4ad18dff7eaf7012452818144070730036800023 --screen 0
notice that "--screen 0" bit.
Just to inform, this bug happens on Fedora 11 too
I think it is Gnome related. I fix it moving from Gnome to XFCE.
Leandro Tavares Carneiro
Analista de Suporte Linux/Unix
On Mon, Jun 15, 2009 at 8:27 PM, Nexos wrote:
> ** Changed in: glib
> Importance: Unknown => Undecided
>
> **
** Changed in: glib
Importance: Unknown => Undecided
** Changed in: glib
Remote watch: GNOME Bug Tracker #580103 => None
** Changed in: glib
Status: New => Fix Released
** Changed in: glib
Importance: Undecided => Unknown
** Changed in: glib
Status: Fix Released => Unknown
I am still confused.
That should read
"I did not have this bug in 8.10 and I do have it in 9.04"
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Now I am confused.
I did not have this bug in 8.04 and I do have it in 8.10.
I verified the code in the patch before applying it.
If this only refers to 8.04, do I need to open a new bug?
8.10 amd64
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
Y
On Thu, 2009-06-11 at 07:50 +, Sebastien Bacher wrote:
> the bug has been fixed upstream now
>
Excellent. Will that fix be backported to Jaunty, seeing how that's the
release we are all using currently?
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/3
the bug has been fixed upstream now
** Package changed: gnome-panel (Ubuntu) => glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => Fix Committed
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notificatio
The Places bug in 8.10 is a different nautilus bug. It is documented in
launchpad bug 282806, referenced above. My guess is that bug also
covers the drag&drop problem.
I'm not sure about the shutdown or properties bugs. I don't know how
those are launched.
I agree that things for dual-screen u
Intrepid is not so bug free...
Does this bug cover drag&drop from the menu to the desktop?
Because when i do that on the screen 1, the launcher appears on screen 0 (8.04,
32-bit).
Also, right click-->Properties on the launcher on panel opens properties window
on the wrong screen (0).
Opening anyt
Ubuntu 8.10 shouldn't have this bug, unless glib or gnome-panel was
updated recently (in which case, shame on the developers for breaking a
working release.)
The patch only fixes application launchers, which is the only thing
anyone mentioned having problems with. Gnome-panel internals are a
whol
I applied the patch and got mixed results.
Some launches opened in the correct screen while other did not.
Example Firefox open in the correct screen while System/Shutdown… does
not.
I am using Ubuntu 8.10 amd64.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/
** Changed in: glib
Status: Unknown => New
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
No Problem.
I did not realize that configure needed to be seeded with a prefix.
This bug is now fixed on my system.
It was very frustrating for a dual monitor user.
I am surprised that it was rated low importance.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.n
Launchpad is not a help forum. Please do not post troubleshooting
questions on bugs.
This page may help you: http://www.cyberciti.biz/faq/rebuilding-ubuntu-
debian-linux-binary-package/. For any further questions please visit
http://ubuntuforums.org/.
--
menu items selected from screen 1 open on
I am having trouble propagating the fix into my system.
I downloaded glib-2.20.1.tar.gz onto my Desktop.
Uncompressed it.
Patched it.
Typed:
connfigure
make install
Everything seemed to work, but I don't know how to replace the version I have
with the new one.
(Its probably simple, but I am not
Patch fixes it for me too.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
** Changed in: glib
Importance: Undecided => Unknown
** Changed in: glib
Status: New => Unknown
** Changed in: glib
Remote watch: None => GNOME Bug Tracker #580103
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notif
On Mon, 2009-06-01 at 18:56 +, LaChild wrote:
> The patched fixed it for me.
Great.
> Thanks for all the hard work, now we just need to get it patched
> upstream in time for Karmic Koala! :D
Uhm. And fixed ASAP for Jaunty. That's what most of the leading edge
Ubuntu userbase are all using.
The patched fixed it for me.
Thanks for all the hard work, now we just need to get it patched
upstream in time for Karmic Koala! :D
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
B
I added the patch to 580103. However, I don't know the right way to get
that bug moved from the gnome-panel team to the glib team.
Also, has anybody tried out the patch and made sure it fixes the
problem? I'm pretty confident it does, as I was able to observe bad
behavior on my single-head machi
could you add the change to the upstream bug?
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Here is a patch with both the fix and debugging information.
Use this only if the later patch doesn't work.
I don't know if you need libglib or libgio-fam, so install both .debs.
** Attachment added: "C:\cygwin\home\gwa\glib-fdfoo.patch"
http://launchpadlibrarian.net/27278331/C%3A%5Ccygwin%5
And here is the patch without debugging information.
TRY THIS FIRST.
Again, this is a bug in glib, NOT gnome-panel.
** Attachment added: "Patch to glib2.0 function is_env()."
http://launchpadlibrarian.net/27278363/C%3A%5Ccygwin%5Chome%5Cgwa%5Cglib-fix.patch
** Also affects: glib
Importan
Nope, above doesn't work, this should:
static gboolean
is_env (const char *a,
const char *b)
{
while (*a == *b)
{
if (*a == 0 || *b == 0 || *b == '=') /* cover naughty equals usage */
return FALSE;
a++;
b++;
}
if (*a == '=' && *b == 0)
return TRUE;
return
Okay, I think I found the problem.
I think this is a bug in the "is_env()" function in glib2.0 file
gdesktopappinfo.c.
I will be providing a patch shortly once I have tested it locally.
Basically what's happening is the environment passed to the spawned
process has 2 "DISPLAY=" lines, one with "
Actually, this helps a lot.
What this tells us is that this is actually a bug in glib2.0 function
g_app_info_launch_uris().
The bug occurs when this is launched with a context including a screen
with gdk_screen_make_display_name(screen)=":0.1" but the parent process
has DISPLAY=":0.0"
Here is a
Ok, here's the output of ~/foo when launching an app from screen 0.1 and
the app shows up incorrectly on 0.0
--
Adding Screen
Screen number: 0
screen name: :0.0
Adding Screen
Screen number: 1
screen name: :0.1
Launching URI
screen
Okay, now for a patched gnome-panel.
For this one, you'll need to install the gnome-panel and libpanel .debs.
To get the old ones, recompile without the patch and reinstall the
.debs. There also may be a way to force synaptic/apt-get to reinstall
over the current ones, but I'm not sure what it is
>From gnome bugzilla:
Bug 580103 – Terminal starts on Display :0.0 when started on :0.1 in Dual
screen conf
2009-04-24 11:03 UTC
http://bugzilla.gnome.org/show_bug.cgi?id=581502
Bug 581502 – Menu/panel items open on different screen
2009-05-05 17:48 UTC
http://bugzilla.gnome.org/show_bug.cgi?id=
Run from terminal on :0.0 with modified environment settings. Command
used: export DISPLAY=':0.1'; ./gnome-terminal
hmm... Maybe I should have saved everyone the email notifiations by
simply taring up these files into one post.
Sorry Guys,
LaChild
** Attachment added: "foo2_export_0_1.foo"
h
Run from terminal on screen :0.0
** Attachment added: "foo2_terminal_0_0.foo"
http://launchpadlibrarian.net/26781246/foo2_terminal_0_0.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member o
Run from terminal on screen :0.1 -> default terminal opened on 0.1 used
to open patched terminal with no environment changes
** Attachment added: "foo2_terminal_0_1.foo"
http://launchpadlibrarian.net/26781222/foo2_terminal_0_1.foo
--
menu items selected from screen 1 open on screen 0
https://
Run from panel on screen :0.0
** Attachment added: "foo2_panel_0_0.foo"
http://launchpadlibrarian.net/26781196/foo2_panel_0_0.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Run from panel on screen :0.1
** Attachment added: "foo2_panel_0_1.foo"
http://launchpadlibrarian.net/26781171/foo2_panel_0_1.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Patch Used
** Attachment added: "used.patch"
http://launchpadlibrarian.net/26781158/used.patch
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Interesting...
I need one more thing... it will take a while for me to get a new patch
file ready, if you can do this yourself, that would be great.
Basically, I need to add the following lines to the previous patch so
that I have the value of the "DISPLAY" environment variable. I think
some oth
Run from terminal on :0.0 with modified environment settings. Command
used: export DISPLAY=':0.1'; ./gnome-terminal
Let me know if you need anything else.
LaChild
** Attachment added: "export_0_1.foo"
http://launchpadlibrarian.net/26778635/export_0_1.foo
--
menu items selected from scre
Run from terminal on screen :0.1 -> default terminal opened on 0.1 used
to open patched terminal with no environment changes
** Attachment added: "Terminal was on :"
http://launchpadlibrarian.net/26778551/term_0_1.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpa
Run from terminal on screen :0.0
** Attachment added: "normal_term.foo"
http://launchpadlibrarian.net/26778458/normal_term.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bug
Run from panel on screen :0.0
** Attachment added: "from_screen_0_0.foo"
http://launchpadlibrarian.net/26778439/from_screen_0_0.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubunt
Run from panel on screen :0.1
** Attachment added: "from_screen_0_1.foo"
http://launchpadlibrarian.net/26778426/from_screen_0_1.foo
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubunt
oops I did miss the point. Now that I know step-by-step what to do I'll
get that for you shortly.
LaChild
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I think you're missing the point.
Add a gnome-panel launcher (temporarily, of course) to screen 1 which
launches the hacked gnome-terminal. Then use that to make it appear on
the *wrong* screen. **What I most need the output of is a run where
gnome-terminal shows up on the wrong screen.**
The o
Ok I tried to use the patch. There's one problem... In order to open
the program on screen 1 I have to use a hack to get it to open onto that
screen. Once the terminal is opened on the right screen calling the
apps directly through this opens up on the correct terminal.
Also if you set the envi
Sorry about that, didn't know that the comment took, it just wasn't
showing me the bug screen.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I've attached a hacked version of gnome-terminal that dumps some screen
information to a file called "foo" in your home directory when run.
THIS IS NOT a secure version, DO NOT install the resulting hacked .deb.
However, if you compile gnome-terminal with this patch to
src/terminal.c, you should
I've attached a hacked version of gnome-terminal that dumps some screen
information to a file called "foo" in your home directory when run.
THIS IS NOT a secure version, DO NOT install the resulting hacked .deb.
However, if you compile gnome-terminal with this patch to
src/terminal.c, you should
I've attached a hacked version of gnome-terminal that dumps some screen
information to a file called "foo" in your home directory when run.
THIS IS NOT a secure version, DO NOT install the resulting hacked .deb.
However, if you compile gnome-terminal with this patch to
src/terminal.c, you should
** This bug is no longer a duplicate of bug 290935
dual screen all panels end up on one screen at startup
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 290935 ***
https://bugs.launchpad.net/bugs/290935
** Changed in: gnome-panel
Status: Unknown => New
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 290935 ***
https://bugs.launchpad.net/bugs/290935
** Changed in: gnome-panel (Ubuntu)
Status: Confirmed => Triaged
** Also affects: gnome-panel via
http://bugzilla.gnome.org/show_bug.cgi?id=580103
Importance: Unknown
Status: Unknown
** T
http://bugzilla.gnome.org/show_bug.cgi?id=580103
** Bug watch added: GNOME Bug Tracker #580103
http://bugzilla.gnome.org/show_bug.cgi?id=580103
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a mem
I'm affected too.
** Changed in: gnome-panel (Ubuntu)
Status: New => Confirmed
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
This occurs on my amd64 upgrade from 8.10 to 9.04.
Gnome panel 2.26.0
It pretty much negates any advantage in two monitors in Dualview.
I think its importance should be higher.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug no
Opps guess only 344273 would be a dup of this one.
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
In case this helps: Bugs 324065 and 344273 are considered dups of
282806 which really should be dups of this issue. It doesn't look like
I can update that (which is probably a good thing... lol)
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You rec
let's undup for them since I don't have the right number but I've read
bugs about that before
** This bug is no longer a duplicate of bug 282806
2 screens -> nautilus shown on the wrong screen when opened via the panel
** Changed in: gnome-panel (Ubuntu)
Status: Invalid => New
--
menu
*** This bug is a duplicate of bug 282806 ***
https://bugs.launchpad.net/bugs/282806
On Sun, 2009-03-22 at 22:28 +, Sebastien Bacher wrote:
> *** This bug is a duplicate of bug 282806 ***
> https://bugs.launchpad.net/bugs/282806
>
> Thanks for the bug report. This particular bug has a
*** This bug is a duplicate of bug 282806 ***
https://bugs.launchpad.net/bugs/282806
Thanks for the bug report. This particular bug has already been
reported, but feel free to report any other bugs you find.
** Changed in: gnome-panel (Ubuntu)
Importance: Undecided => Low
** Changed in: g
70 matches
Mail list logo
