Launchpad has imported 31 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=307581.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2007-09-26T18:09:57+00:00 Bill wrote: Description of problem: When I open a new tab (via right click on a terminal, clicking on something in liferea, whatever), firefox immediately jumps onto the current workspace. This is irritating. Version-Release number of selected component (if applicable): firefox-2.0.0.6-11.fc8 Additional info: Seems related to the startup notification patch, as it worked ok in 2.0.0.6-8.fc8. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/0 ------------------------------------------------------------------------ On 2007-10-01T00:17:03+00:00 Adam wrote: I will second this. Very irritating! Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/1 ------------------------------------------------------------------------ On 2007-10-01T19:22:40+00:00 Christopher wrote: Owen says this is a metacity bug. The following program also hops windows. #!/bin/env python import gtk import gobject w = gtk.Window() w.set_title("Foo") w.show() def on_timeout(): w.present() return False gobject.timeout_add(5000, on_timeout) gtk.main() Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/2 ------------------------------------------------------------------------ On 2007-10-01T19:23:35+00:00 Christopher wrote: er, hops workspaces Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/3 ------------------------------------------------------------------------ On 2007-10-01T19:34:29+00:00 Colin wrote: To give some background on this issue, Firefox now supports startup notification: https://bugzilla.mozilla.org/show_bug.cgi?id=223492 The issue in this bug only occurs when there are multiple workspaces. Removing this Firefox patch would be a regression in the single workspace case because it would require clicking on a flashing browser entry in the task list after activating an external link. >From IRC: <owen> walters: metacity could look at the window role and alter the behavior based on that Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/4 ------------------------------------------------------------------------ On 2007-10-01T19:48:25+00:00 Bill wrote: FWIW, commenting out the call to gdk_window_focus() in the patch makes it DTRT for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/5 ------------------------------------------------------------------------ On 2007-10-01T20:00:33+00:00 Owen wrote: Actually, what I meant was that based on the "type" of the window application vs. dialog, you could do different things. A application never, under any circumstances, should be moved between desktops. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/6 ------------------------------------------------------------------------ On 2007-10-01T20:03:13+00:00 Colin wrote: Bill, what effect does that have in the single-workspace case? Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/7 ------------------------------------------------------------------------ On 2007-10-01T20:04:24+00:00 Colin wrote: Also, I've filed this bug upstream here: http://bugzilla.gnome.org/show_bug.cgi?id=482354 Since there seems to be agreement this is an upstream Metacity issue, please continue discussion there. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/8 ------------------------------------------------------------------------ On 2007-10-01T20:10:27+00:00 Bill wrote: Colin: when it's on the same workspace, I get the throbbing entry in the panel. When it's on the other workspace, I don't. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/9 ------------------------------------------------------------------------ On 2007-10-11T20:06:50+00:00 David wrote: We need to fix this for F8... Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/10 ------------------------------------------------------------------------ On 2007-10-11T21:48:48+00:00 Jeremy wrote: This is also happening in compiz... so more than just metacity at work here. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/11 ------------------------------------------------------------------------ On 2007-10-11T23:26:44+00:00 Christopher wrote: Jeremy: not quite... in metacity, the _window_ switches to the current workspace. In compiz, the _active workspace_ switches. This is about the metacity issue, which everyone agrees is clearly wrong. The compiz behavior seems more or less sane. While different, i've already gotten used to it. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/12 ------------------------------------------------------------------------ On 2007-10-12T03:06:19+00:00 Matthias wrote: The long discussion leading to the current metacity behaviour can be found here: http://bugzilla.gnome.org/show_bug.cgi?id=166379 Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/13 ------------------------------------------------------------------------ On 2007-10-12T04:48:32+00:00 Bill wrote: So, going back to the beginning. The original patch (for firefox) has the following comments usptream from Elijah (https://bugzilla.mozilla.org/show_bug.cgi?id=223492#c31): ************ >+ if (desktopStartupID.IsEmpty()) { >+ PRUint32 timestamp = GTKToolkit->GetFocusTimestamp(); >+ if (timestamp) { >+ gdk_window_focus(aWindow->window, timestamp); >+ GTKToolkit->SetFocusTimestamp(0); >+ } >+ return; >+ } This block of SetUserTimeAndStartupIDForActivatedWindow() is a little confusing. It doesn't set the user time or the startup id for the activated window. Instead, it sends an "activate me, please" message to the window manager. I understand it's just a workaround when no startup id is available (because either firefox wasn't launched with startup-notification or wasn't built with MOZ_ENABLE_STARTUP_NOTIFICATION), but it'd be nice to have it documented as such. It'd also be good to verify in testing that this block of code isn't being executed (i.e. that startup id is non-empty), since it is just a workaround. ***************** I find it odd that the supposed 'workaround' part of the code is what's causing the problem in my testing. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/14 ------------------------------------------------------------------------ On 2007-10-12T06:34:52+00:00 Bill wrote: Created attachment 225081 partial fix for firefox Note that due to missing changes to the configury, we aren't even *building* the SN support at the moment - this patch fixes that. Doesn't change the behavior, though. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/15 ------------------------------------------------------------------------ On 2007-10-17T20:15:02+00:00 David wrote: "This is not a blocker" Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/16 ------------------------------------------------------------------------ On 2007-10-18T04:33:20+00:00 Jens wrote: <notting> halfline: why not just take the patch out of ff, since we're not even applying it in a way that works <juhp> notting: exactly <halfline> notting: that's not a horrible idea notting: might be worth talking to stransky about or caillon if he pops on Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/17 ------------------------------------------------------------------------ On 2007-10-18T15:32:34+00:00 Bill wrote: *** Bug 337721 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/18 ------------------------------------------------------------------------ On 2007-10-18T20:33:15+00:00 Colin wrote: Note there is now a patch for metacity upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=482354#c2 Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/19 ------------------------------------------------------------------------ On 2007-10-18T21:25:49+00:00 Colin wrote: Also in response to: <notting> halfline: why not just take the patch out of ff, since we're not even applying it in a way that works The patch does function as expected in the single workspace case, even if it may be entering into a fallback section of the code (will investigate). Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/20 ------------------------------------------------------------------------ On 2007-10-19T00:15:15+00:00 Colin wrote: I have built a new version of metacity with the patch: http://koji.fedoraproject.org/koji/buildinfo?buildID=21629 Please test, if it works well then we can reable to re-enable the Firefox fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/21 ------------------------------------------------------------------------ On 2007-10-19T00:33:39+00:00 Bill wrote: (In reply to comment #20) > Also in response to: > > <notting> halfline: why not just take the patch out of ff, since we're not > even > applying it in a way that works > > The patch does function as expected in the single workspace case, even if it > may > be entering into a fallback section of the code (will investigate). The patch adds configury for using libstartupnotification, and ifdef'd code to use libsn. We then build moz without sn support. If it's functioning, it's completely by accident. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/22 ------------------------------------------------------------------------ On 2007-10-19T00:52:52+00:00 Jens wrote: (In reply to comment #21) > I have built a new version of metacity with the patch: > http://koji.fedoraproject.org/koji/buildinfo?buildID=21629 > > Please test, if it works well then we can reable to re-enable the Firefox fix. Thanks, Colin! Yes, that works well for me so far. :) Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/23 ------------------------------------------------------------------------ On 2007-10-19T01:15:11+00:00 Colin wrote: (In reply to comment #22) > > The patch adds configury for using libstartupnotification, and ifdef'd code to > use libsn. We then build moz without sn support. If it's functioning, it's > completely by accident. Ok, I'm at home so I can't actually test this with my rawhide computer, but from looking at the patch again, the section you identified earlier (which calls gdk_window_focus which ultimately causes the focus event) is the source of the behavior under discussion. The startup notification specification if supported correctly would make Firefox display a progress status on first launch, but this (to me) is not the most useful part of the patch. The most useful part is the behavior that when one clicks on a link in an external program, the web browser appears and displays the link. Some people feel that behavior wasn't right for multiple desktops (and the metacity patch addresses this), but please when testing things, try the single workspace case. The expected behavior is that the browser appears; it should not pulse as in comment #9. This is the way clicking on links works on other platforms, and is the most sensible thing I believe for most situations in the single-workspace case. There might be some more special cases such as feed readers (liferea?) where one wants to click a number of links to "queue" urls; I am open to discussion around those. Probably the right solution for them will be to have the ability at link-click time whether or not you want to see it. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/24 ------------------------------------------------------------------------ On 2007-10-19T01:17:11+00:00 Colin wrote: I meant to mention above; the reason the patch still has effect is because the gdk_window_focus call is outside the #ifdef MOZ_ENABLE_STARTUP_NOTIFICATION. Also, bear in mind this patch is already upstreamed and will be in the Firefox 3 release; I am not yet sure whether it will be in the 2.0.0.7 stream. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/25 ------------------------------------------------------------------------ On 2007-10-19T12:21:59+00:00 Christopher wrote: We'll probably want this metacity fix for FC7 too before Firefox's support makes it there. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/26 ------------------------------------------------------------------------ On 2007-10-22T13:22:20+00:00 Matthias wrote: Fixed in F8, moving off blocker Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/27 ------------------------------------------------------------------------ On 2007-10-22T19:56:16+00:00 Mauricio wrote: Its fixed for me after last update in F8 Cheers Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/28 ------------------------------------------------------------------------ On 2008-05-14T14:31:36+00:00 Bug wrote: This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/40 ------------------------------------------------------------------------ On 2008-06-02T19:17:23+00:00 Peter wrote: Thank you for the bug report. Closing bug as per comment #27 and comment #28. If you still experience this problem after updating to our latest Fedora release, reopen this bug against that version if this bug exists there. Reply at: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/44 ** Changed in: metacity (Fedora) Status: Fix Released => Won't Fix ** Changed in: metacity (Fedora) Importance: Unknown => High ** Bug watch added: Mozilla Bugzilla #223492 https://bugzilla.mozilla.org/show_bug.cgi?id=223492 ** Bug watch added: GNOME Bug Tracker #166379 https://bugzilla.gnome.org/show_bug.cgi?id=166379 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/207744 Title: Clicking notification panel icon doesn't switch desktops Status in Gaim: Invalid Status in Metacity: Fix Released Status in Pidgin: Invalid Status in metacity package in Ubuntu: Fix Released Status in pidgin package in Ubuntu: Invalid Status in metacity package in Fedora: Won't Fix Status in pidgin package in Fedora: Won't Fix Bug description: Binary package hint: pidgin laney@chicken:~$ lsb_release -rd Description: Ubuntu hardy (development branch) Release: 8.04 laney@chicken:~$ apt-cache policy pidgin pidgin: Installed: 1:2.3.1-2ubuntu1 Candidate: 1:2.3.1-2ubuntu1 Version table: *** 1:2.3.1-2ubuntu1 0 800 http://archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status When a message is received in Pidgin, the notification area icon flashes as expected. Clicking this icon in Gutsy always used to switch to the desktop with the IM window on and activate it. Clicking it now only shows the IM window in the window list. It does not switch to the desktop with it on, nor does it cancel the unread status. Steps to repro: 1. Start a conversation with somebody 2. Switch to another desktop 3. When a message is received and the notification area icon is flashing, click it 4. The desktop is not switched to the one with the IM window, but the IM window now appears in window list. Expected behaviour: At 4, the desktop should switch and activate the IM window. This is a regression from Gutsy. To manage notifications about this bug go to: https://bugs.launchpad.net/gaim/+bug/207744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
