gedit switches workspaces

[WW]

I'm not sure if this is a bug, but it is certainly a nuisance. HrdwrBob on the
IRC channel said he thought it might be a bug.

If I have gedit running in one workspace, and I start gedit in another
workspace, the gedit from the first workspace is moved to the second workspace.
 I have to right-click the title bar of the window and use the "Move to another
workspace" option to put it back. I would like to have two different instances
of gedit, one in each workspace, each with their own list of open files.

I chose the UNKNOWN component for this bug report because I don't know if this
is a gedit problem or a gnome problem.

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

[Sebastien Bacher (seb128)]

gedit's bug. Upstream bug report:
http://bugzilla.gnome.org/show_bug.cgi?id=104011

[WW (wweckesser)]

What happens to "upstream" problems like this? Will this ever be fixed?
I would love to see a fixed gedit in warty-updates. I realize there is
no security problem, but this is an extremely annoying usability bug.
Sticking with the bug metaphor, it isn't a giant cockroach chewing on
my leg, but it is an annoying mosquito, buzzing around my head every
time I use gedit.

The commenters in the link given above got it right: "Additional
Comment #23" by Matthew Gatto explains how it *should* work.
But that comment is from May 1.

[Sebastien Bacher (seb128)]

(In reply to comment #2)
> What happens to "upstream" problems like this? Will this ever be fixed?

"upstream" mean that's the problem is an upstream one and has been
forwarded (at least for the GNOME packages). The best way to get it
fixed is to deal with upstream/send a patch. When the bug is fixed upstream
the patch is included in the package usually.

> I would love to see a fixed gedit in warty-updates. I realize there is
> no security problem, but this is an extremely annoying usability bug.

This change is probably not a good candidate for a warty update. That's
not a major issue (security or crasher) and not a lot of people complain
about it, so in the global context that's not a priority to fix and that can
wait the next release.

> The commenters in the link given above got it right: "Additional
> Comment #23" by Matthew Gatto explains how it *should* work.
> But that comment is from May 1.

You're free to ping the upstream to know what's going on with this bug.

[WW (wweckesser)]

Work-around: Use the --new-window command line option with gedit.

Sebastien, thanks for the explanation.

[Sebastien Bacher (seb128)]

this seems to be fixed with the current hoary version, I'm closing the bug. Feel
free to reopen if you think that's still an issue.