This happens whichever new workspace you select?
--
[Gutsy] Move to Another Workspace has no effect
https://bugs.launchpad.net/bugs/131169
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
For what little it's worth, it's working fine for me with 2.18.2
(feisty) and 2.19.55 (upstream trunk), but the same operation in wncklet
seems to be broken. I don't have a gutsy system to hand. What version is
in gutsy?
--
[Gutsy] Move to Another Workspace has no effect
So what would fix this bug, then? Gutsy upgrading to the latest 2.19
release? I know I'm a GNOME person and not so much an Ubuntu person, and
I know Gutsy isn't released yet, but it's kind of not so much of a
surprise when things break from time to time in the unstable branch.
--
[Gutsy] Move to
(FWIW there's nothing in the changelog which appears to fix this between
2.19.34 and 2.19.55, or even affect it other than the reordering of
window menu options.)
--
[Gutsy] Move to Another Workspace has no effect
https://bugs.launchpad.net/bugs/131169
You received this bug notification because
I'm attempting to replicate this over here. We (upstream) did push the
gnome-2-18 branch last night, so it could be a problem introduced there.
--
Regression: metacity fails to create windows, sscrolbars, or toolbars in April
10th Synaptic upgrade
https://bugs.launchpad.net/bugs/105271
You
Procedural question: How do I get the core dump out of the .crash file?
I could write a program to do it, but I'm sure something else exists
already. I asked on IRC and googled around, but I couldn't find anything
out.
--
Metacity crashes at startup
https://launchpad.net/bugs/84080
--
Oh, thanks. That's nifty.
So now I have a file called CoreDump, and file thinks it's a coredump
and gdb doesn't. Am I doing something wrong here?
[EMAIL PROTECTED]:/tmp/ap$ file CoreDump
CoreDump: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style,
from 'metacity'
[EMAIL
Thanks for your bug report. I'll try and get this reproduced tonight or
tomorrow and let you know what I find out.
--
metacity crash when increasing no of virtual desktops to 3
https://launchpad.net/bugs/84646
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Checked in the fix upstream.
--
Strange behavior while moving maximized window (xinerama)
https://launchpad.net/bugs/62894
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Is this still happening for you? Can you still reproduce it? I just
tried here (running edgy): I set the number of workspaces to 16, then to
36, then back down to 16, and nothing unusual happened. Did you have
windows in any of these workspaces? How many rows do you have your
workspaces arranged
So you're saying that when you click in the middle of the window, it
doesn't get focus, but when you click on the titlebar, it does?
--
window focus
https://launchpad.net/bugs/74636
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I am wondering how come g_int_hash is shown as calling dcgettext, when
g_int_hash is defined as simply
guint
g_int_hash (gconstpointer v)
{
return *(const gint*) v;
}
--
metacity crash while scrolling in youtube
https://launchpad.net/bugs/75807
--
desktop-bugs mailing list
Elijah explains in the upstream bug that this behaviour is according to
design. When raise_on_click is not set, the *only* thing which can raise
a window is a pager. gajim is not a pager, therefore it cannot raise
windows (not even its own). The solution is for gajim to register as a
pager.
**
Did you have compositing turned on in metacity?
--
Metacity (and X Server) crashed when starting beryl
https://launchpad.net/bugs/78191
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I've checked the version in trunk and the version in Edgy, and they both
call the colour tab Colors. Are you sure you're running in en_US?
--
gnome-terminal misspells color
https://launchpad.net/bugs/78266
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I'm not certain, but I think en_US isn't a valid value for LANGUAGE
(so it falls back to the next option, en_GB). I think what you want is
C: LANG=C:en_GB;en.
--
gnome-terminal misspells color
https://launchpad.net/bugs/78266
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
chantra: with respect, I think you misunderstood: the problem here, as I
see it, is that John Moser is using the environment variable
LANGUAGE=en_US:en_GB:en, and en_US is invalid, so it falls back to
en_GB. If you just use en_US, it will fall back to C (the default). In
addition, chantra, are you
Hi, I'm the author of the upstream alt-f6 code. It does actually use the
X window's group property. It appears to me that the problem is that
multiple gnome-terminals don't have the same group property as one
another. You can add the debugging statement below to demonstrate this.
Unless I'm
This is at least a problem with metacity, if not a problem with gtk;
it's not gedit-specific. More information as we have it.
--
incorrect title when using a rtl language
https://bugs.launchpad.net/bugs/109723
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This has happened before with Beryl, but at the time this particular bug
happened you were running Metacity?
--
Mozilla, gimp, and others windows disappear
https://bugs.launchpad.net/bugs/119170
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
You might want to hold off a few hours on backporting it: someone just
provided a patch to the patch. I'll talk to Elijah about whether we
should do an extra release just for that.
--
Metacity mistakenly opens Impress presentation on primary head of dual head
setup
Thanks for your report. I have just run KSig under GNOME on Hardy and
it shows KSig as the title. So since I can't see it, please could you
test some things?
1. Go through these commands and tell us whether you still see %c as
the title:
compiz --replace
metacity --replace
kwin --replace
(I
Thanks for doing that. This is quite interesting.
The xprop file you attach contains the line:
WM_NAME(STRING) = %c
This indicates that Kopete itself is claiming that its title is %c,
rather than that any window manager is misinterpreting it.
Furthermore, if all of metacity, kwin, and
This is a matter for gnome-session, not metacity.
** Changed in: gnome-session (Ubuntu)
Sourcepackagename: metacity = gnome-session
--
Sessions not saved in Sessions Preferences
https://bugs.launchpad.net/bugs/281403
You received this bug notification because you are a member of Ubuntu
Desktop
I think the trouble is that Metacity is not tunable enough to do this by
design: Metacity is supposed to be a small, simple window manager
without a whole lot of options and bells and whistles. Of course we
could patch it at the Ubuntu level to behave differently, or to be more
tunable, and we
Thank you for taking the time to report this problem. However, without
a way of reproducing the problem, it will be difficult to fix. Is it
possible for you to find a predictable sequence of actions which often
or always reproduce the problem?
--
Only in this Workspace isn't honored
Sorry, was typing faster than I thought. The file will have the
extension .ms, not .sm, and it will be in a subdirectory sessions of
one of those directories I told you about.
--
After upgrading to hardy, gnome-terminal windows are not properly restored on
login
Okay, that's pretty interesting. The next thing to figure out is
whether the configuration was saved wrongly, or is being restored
wrongly.
You should have a directory called ~/.config/metacity, or one called
~/.metacity. (Or perhaps you have both.) In one of these directories
you'll find a
(Just making it clear that this is an invalid bug in nautilus rather
than in metacity.)
** Changed in: nautilus (Ubuntu)
Sourcepackagename: metacity = nautilus
--
Change Desktop Background
https://bugs.launchpad.net/bugs/214908
You received this bug notification because you are a member of
Oh, wonderful. Thanks for finding that. I'll see about implementing it
soon (unless Iain does).
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 213432 ***
https://bugs.launchpad.net/bugs/213432
We just have to find a way to make everyone happy. I have heard that
kwin treats Firefox specially, but I don't know how true that is.
--
clicking on minimized app in window list doesn't change desktop
I'm working on some focus issues at present and I hope that this will be
one of them. (It's the expected_focus_window problem again.)
--
Cannot alt + tab out of fullscreen games
https://bugs.launchpad.net/bugs/63245
You received this bug notification because you are a member of Ubuntu
Desktop
If laubster's diagnosis is correct, then this is a gnome-terminal bug
and not a WM bug.
--
After upgrading to hardy, gnome-terminal windows are not properly restored on
login
https://bugs.launchpad.net/bugs/221144
You received this bug notification because you are a member of Ubuntu
Desktop
Marking as fixed upstream, then.
** Changed in: metacity
Status: New = Fix Committed
** Changed in: metacity
Status: Fix Committed = Fix Released
--
[dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier
properly
https://bugs.launchpad.net/bugs/37214
You
** Changed in: metacity
Importance: Undecided = Unknown
Bugwatch: None = GNOME Bug Tracker #529123
Status: New = Unknown
--
desktop switching issue
https://bugs.launchpad.net/bugs/54410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Neil: Do note that this is a bug against Metacity. Whether Compiz
understands the settings is a matter for Compiz, and you should probably
have a separate bug for that.
** Changed in: metacity
Importance: Undecided = Unknown
Bugwatch: None = GNOME Bug Tracker #529125
Status: New
You will have at least one of: a directory called ~/.metacity/sessions/
, and a directory called ~/.config/metacity/sessions/ . What I would
like you to do is to find the one that has the timestamp from when you
logged out in this experiment (run it again if you need to), check it to
make sure it
Sorry, thought error.
In those two directories there will be many files with the extension
.ms. What I would like you to do is to find the one that has the
timestamp... etc.
--
[hardy] window sizes not saved across sessions
https://bugs.launchpad.net/bugs/218296
You received this bug
** Bug watch added: GNOME Bug Tracker #528927
http://bugzilla.gnome.org/show_bug.cgi?id=528927
** Also affects: metacity via
http://bugzilla.gnome.org/show_bug.cgi?id=528927
Importance: Unknown
Status: Unknown
--
[hardy] amsn does not blink / flash on new messages with metacity
I would like to finish dealing with this bug from Metacity's point of
view. We have two options here:
1) We can say that this is an invalid bug, because the EWMH says that
the switcher decides the workplace layout, and if you remove the
switcher, you won't have a workplace layout. Then we can
I think this is possibly a window manager bug, since it's the window
manager's job to resize the windows on restart. I don't see why it
would affect compiz and metacity equally, though.
--
After upgrading to hardy, gnome-terminal windows are not properly restored on
login
a) This would be a trivial fix;
b) This has been raised repeatedly upstream and they have decided to make it a
policy decision not to implement it;
c) We could implement it with an Ubuntu-specific patch if people decided it was
something worth going for.
--
move to workspace should wrap around
** Bug watch added: GNOME Bug Tracker #89315
http://bugzilla.gnome.org/show_bug.cgi?id=89315
** Also affects: metacity via
http://bugzilla.gnome.org/show_bug.cgi?id=89315
Importance: Unknown
Status: Unknown
--
move to workspace should wrap around
And suddenly, there was movement upstream! Erwann Chenede has found
the bug and sent in a patch of approximately four lines which fixes the
whole thing.
** Bug watch added: GNOME Bug Tracker #529925
http://bugzilla.gnome.org/show_bug.cgi?id=529925
** Also affects: metacity via
This isn't really a bug in Metacity or in Compiz; what you're really
asking for is either that Metacity or Compiz should be the exclusive
window manager in use or that an enormous effort should be expended on
making the UI of each one exactly the same in every little detail. Both
of those are far
A further thought occurred to me while attempting to explain this to
someone at 1am over a cheese sandwich.
The EWMH doesn't actually say that the switcher decides the workspace
layout. What it says is that _NET_DESKTOP_LAYOUT (which is what decides
the number of rows) must only be set by the
Is this repeatable?
The line in question appears to be
tmp = workspace-mru_list;
and with that call stack, workspace is the current workspace. I can't
see why it would be pointing outside the current segment, though I'd
like to know. If you can repeat this, we can capture logs and see.
--
*** This bug is a duplicate of bug 178953 ***
https://bugs.launchpad.net/bugs/178953
This is a dupe of #178953 (is there a way I can mark it as such, or does
someone else need to)?
It has nothing to do with session management, incidentally.
--
Compiz Fusion cannot be enabled in Ubuntu
Sorry to be slow here, but what's the name of the executable of the
tracker applet? I don't seem to have anything on the add applets
dialogue of this machine (running gutsy) that looks like it would be
called that in English. Does this exist only in hardy? I'll upgrade if
necessary.
--
Search
Is this the same as http://bugzilla.gnome.org/show_bug.cgi?id=482354 ?
--
[hardy] firefox3 siezes focus when loading a page via liferea
https://bugs.launchpad.net/bugs/197761
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in
Yeah, I think this is a gnome-session thing. Moving over to them
upstream.
--
[Gutsy Beta] .xsession-errors: 'Failed to read saved session file'
https://bugs.launchpad.net/bugs/150721
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Have you tested with trunk and confirmed it still does this?
--
'Downloading package information' and 'building dependency tree' progress
dialogs steal focus
https://bugs.launchpad.net/bugs/35876
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I should note that, although I don't know the specifics of the problem
and so I can't say whether it's been fixed, Robert's answer is certainly
not the whole truth. Metacity has no way of knowing whether a window
needs input.
Metacity policy (and also the policy of any other sane WM, as Bogdan
So it's not just existing windows raising themselves, or newly-created
transients of existing windows: even newly-launched applications
shouldn't appear over the top of the current one? What about if, say, I
choose them from the Applications menu; should they steal focus then?
--
'Downloading
Wouter: I still don't have a concrete understanding of what in the
meantime means. Clearly you mean that if focus hasn't changed, and no
keyboard activity has occured, between time A and time B, the new window
should not get focus. Time B is presumably the time when the window
appears on the
last click was on the panel's menu window, which doesn't exist anymore
That isn't the way menus work, though; you can see this with the menus
of any application. The case you mention in your first footnote is in
fact the general case for all menus-- they always give focus back to
where it came
Looks like a Metacity problem to me, not a kernel problem.
--
gnome-appearance-properties crashed with SIGSEGV in meta_theme_get_frame_style()
https://bugs.launchpad.net/bugs/199402
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I am attempting to reproduce the problem. I haven't looked at the stack
traces yet.
Bug #204882 is interesting because the two pieces of theme code given
(it would have been useful to have an entire theme attached for problems
involving theme formats!) are both clearly broken: one contains
Wait, no need. The stack traces have shed abundant light on the matter.
--
gnome-appearance-properties crashed with SIGSEGV in meta_theme_get_frame_style()
https://bugs.launchpad.net/bugs/199402
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I believe I've found the problem, though since I can't reproduce the
crash I can't say for sure. There is a pretty glaring bug in the exact
place the stack trace shows, though. Can anyone confirm?
** Attachment added: Fix for bug, I believe.
(Please excuse me if I have messed this up: yesterday was the first day
I tried doing this in Ubuntu.)
--
gnome-appearance-properties crashed with SIGSEGV in meta_theme_get_frame_style()
https://bugs.launchpad.net/bugs/199402
You received this bug notification because you are a member of Ubuntu
Thank you for reporting this bug. Could you let us know what theme it
occurs with? (This is the output of gconftool -g
/apps/metacity/general/theme.)
--
gnome-appearance-properties crashed with SIGSEGV in
gnome_theme_meta_info_compare()
https://bugs.launchpad.net/bugs/191708
You received this
Thank you for your help raising this, anyway.
This isn't really a Metacity problem. gnome_theme_meta_info_compare()
is a function in libtheme.
** Changed in: gnome-themes (Ubuntu)
Sourcepackagename: metacity = gnome-themes
--
gnome-appearance-properties crashed with SIGSEGV in
** Bug watch added: GNOME Bug Tracker #502644
http://bugzilla.gnome.org/show_bug.cgi?id=502644
** Also affects: metacity via
http://bugzilla.gnome.org/show_bug.cgi?id=502644
Importance: Unknown
Status: Unknown
--
Better animations
https://bugs.launchpad.net/bugs/234154
You
Suggestions as to what would be better are welcome.
Are you talking about the minimise effect with the compositor turned on,
or not?
--
Better animations
https://bugs.launchpad.net/bugs/234154
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Note that I don't mean compiz or something, I mean Metacity's own
compositor. You can find the answer by typing
gconftool -g /apps/metacity/general/compositing_manager
--
Better animations
https://bugs.launchpad.net/bugs/234154
You received this bug notification because you are a member of
It's not a huge priority, since people can use Metacity's compositor
which has a better minimise effect, but if you have any better ideas as
to how it should look, please let us know.
The minimise effect clearly works as designed, though (your complaint is
that it should work differently), so I'm
(oops, trying that again)
** Changed in: metacity (Ubuntu)
Importance: Low = Wishlist
--
Better animations
https://bugs.launchpad.net/bugs/234154
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
desktop-bugs
You can turn it on with
gconftool -s /apps/metacity/general/compositing_manager true --type=bool
or by running gconf-editor, navigating to /apps/metacity/general, and
turning on compositing_manager. As to why it's not on by default, I
don't know: that's a question for the packagers.
--
@phenest: A number of odd compositing bugs were fixed in trunk upstream
recently. If you can reproduce the problem reliably with the version in
Hardy, is it possible you can install the most recent upstream version
(2.23.21) and see whether that fixes the problem?
--
Gnome Do has visual
(If you need any help in doing that, please let me know.)
--
Gnome Do has visual problems when run with Metacity's compositing manager
https://bugs.launchpad.net/bugs/206870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in
Josef: If you use compiz, you should raise another bug against compiz.
This is a metacity bug.
--
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@qinjuehang: Please don't say the compositor to mean Compiz, in a
Metacity bug about Metacity's compositor. (I assume that's what you
mean from context.) It does muddy the waters rather.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You
With trunk it causes Metacity to crash (it may well have done in earlier
situations too, since the session manager sees Metacity going down and
brings up another one, so crashes can be invisible). This is not a
happy situation. I'm escalating.
Expect some kind of patch by tonight, I hope.
--
Patch to fix the segfault is committed to upstream trunk, but it still
doesn't let Compiz accept the CM selection! I shall continue to
investigate, and hope to get more information to you tomorrow.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
Here are my thoughts.
Part one, the background reading: It seems to me after a while of
digging through the ICCCM that Travis Watkins was incorrect back in
December when he said that Metacity was not giving up control of the
compositor selection. Section 2.8 of the ICCCM says that anyone who
Compiz fails to check return code of XSetSelectionOwner which is
returning it a low-level X error.
** Changed in: compiz (Ubuntu)
Status: Invalid = New
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification
(Sorry, that wasn't a reply to crdlb; I only just got the notification
email.)
@crdlb: Your first paragraph sounds like a good solution. I'll try it
out this evening and see what I find.
Your second para is entirely correct, of course, but a failure there
doesn't necessarily mean that it's the
@perfran: I'll write a page on blogs.gnome.org later explaining the
rather complicated current state of play.
--
drag drop improvement: delay bringing window to front until mouse released
https://bugs.launchpad.net/bugs/29560
You received this bug notification because you are a member of Ubuntu
@Murat: phenest was asking for help with installing Metacity from
source, which doesn't use Launchpad answers.
--
Gnome Do has visual problems when run with Metacity's compositing manager
https://bugs.launchpad.net/bugs/206870
You received this bug notification because you are a member of Ubuntu
The effect is activ in the compiz-desktop only
Then this bug does not belong under metacity. I'm moving it to compiz
in case they have any ideas.
** Changed in: compiz (Ubuntu)
Sourcepackagename: metacity = compiz
--
The close, max and min buttons have vanished from the right side of all
Here we go: http://blogs.gnome.org/metacity/2008/06/11/drag-and-drop/
I learned quite a lot myself writing that!
--
drag drop improvement: delay bringing window to front until mouse released
https://bugs.launchpad.net/bugs/29560
You received this bug notification because you are a member of
Metacity won't fix this because:
1) it's not a window manager issue; applications ought to be responsible
enough to create their windows where they want them;
2) it violates separation of concerns; there can be a separate process
(such as devilspie) which moves a user's windows around to their
(Sorry, that of course wasn't supposed to be patronising; I apologise
if it sounded that way.) You can install a theme with wider borders, or
modify the borders of the existing one as explained elsewhere on this
page.
--
Window Resize Difficult (Window Border Thickness)
Paul: You also have the option of changing the theme size, of course.
--
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for metacity in ubuntu.
--
Does this happen every time we do an upstream release? I thought it was
fairly automatic.
I can have the release script signal someone, or something, if you like.
--
Please sponsor metacity 2.21.8 (main) into Hardy
https://bugs.launchpad.net/bugs/188817
You received this bug notification
Does it work with kwin? If it does, I'll see how they do it.
--
compiz doesn't start if metacity compositor is enabled
https://bugs.launchpad.net/bugs/178953
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for metacity in ubuntu.
--
This is a matter for the workspace switcher to decide. Metacity merely
uses the setting that's set in the workspace switcher. I can't see how
this is metacity's problem.
--
Number of rows of desktops forgotten if no switcher on panel
https://bugs.launchpad.net/bugs/116807
You received this bug
When you say changing windows, you mean switching between windows,
right? Do you do this with alt-Tab or similar, or by clicking on the
taskbar, or by clicking on the windows? Do you have compositing turned
on in Metacity, do you know?
--
graphical glitches when changing windows
** Tags added: need-i386-retrace
** Tags added: crash
--
Metacity crashed
https://bugs.launchpad.net/bugs/64009
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Neil: Are you still seeing this problem in Hardy? It's working fine
here.
--
Metacity button_layout ignored
https://bugs.launchpad.net/bugs/102787
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
André: Hi. Could you run xprop, and click on the window which doesn't
have a minimise button, and then paste the output here?
--
Gnome wine runs all programs without window's minimize button
https://bugs.launchpad.net/bugs/202456
You received this bug notification because you are a member of
(Attaching it would probably be better; it can get lengthy.)
--
Gnome wine runs all programs without window's minimize button
https://bugs.launchpad.net/bugs/202456
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
Jurgis: Was the application, or any document in the application, already
open?
--
double click in file from my desktop folder open the application, but focus is
not in new application.
https://bugs.launchpad.net/bugs/70951
You received this bug notification because you are a member of Ubuntu
I have opened Nautilus, double-clicked files of two types (text and SVG)
and the relevant program (gedit and eog) appeared on top with focus both
times.
Please let us know whether this happens with files of every type, or
whether it just happens with specific types, and whether it always
happens.
[Sorry, I asked this upstream and the reporter clearly didn't get the
message.]
This is going to be a tough one to track down if we can't reproduce it.
Can you reproduce this bug? What were you actually doing, not moving
windows around or switching between windows or anything? Were you just
Does this happen in metacity?
--
new windows are put in the background
https://bugs.launchpad.net/bugs/129396
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
desktop-bugs mailing list
I did actually add a check for verbose mode yesterday, so that the log
message's size and content are not calculated unless it'll be used, and
hence g_list_length won't be called. This closes the presenting
problem. But we still have the difficulty that the presenting problem
can only have been
Travis: are you sure comment 5 is the same thing? I don't think you can
have multiple Totem windows open at once. I took it to mean
1. open Nautilus (in window N1) and launch a video file
2. Totem (in a new window T1) gains focus
3. Go back to N1 and launch another video file
4. Video opens in
So can I take Metacity off the list for now?
--
new windows are put in the background
https://bugs.launchpad.net/bugs/129396
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
--
desktop-bugs mailing list
1 - 100 of 193 matches
Mail list logo
