(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 m
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
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 Ubun
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 subscribed
** 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 receiv
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 Bugs
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 Bu
*** 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
http
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 subscrib
(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 Ubu
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 fil
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
https://bugs.launchpad.net/bug
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
https://b
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 cou
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 swi
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
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
http://bugz
** 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
https://bugs.launchpad.net/bugs/2
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
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
https://bugs.launchpad
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 cl
** 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 metaci
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 notifica
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
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
** 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
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
Yo
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
gnome_theme_me
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
(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
D
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."
http://launchpadlibrarian.net/12969268/ANSWER.deb
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 subscrib
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
unquo
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 metacity
"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
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 scre
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
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
me
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 subscri
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.
--
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 ubu
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.
--
Searc
*** 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 Hardy
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.
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
https://bugs.la
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
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.
--
de
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 because
(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)
https://bugs.launchpad.n
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.
--
Good luck; let us know how it goes!
--
window manager crash & nonload programs
https://bugs.launchpad.net/bugs/185629
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for metacity in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@list
It looks like it's not Metacity-specific, yes. The trouble now is trying
to figure what it is! If it's affecting both OpenOffice *and* WINE, I'd
guess it's a problem with your X server, but that's just a guess. (I
only do window managers, so this is a bit beyond my knowledge.)
--
window manager c
Hello. Can you confirm whether this bug occurs when you are running some
other window manager? For example, if you are running kwin or icewm? (If
you don't know how to test with kwin: if you don't already have kwin,
you can get it by opening a terminal and typing "sudo apt-get install
kwin", then g
That means pretty much exactly that it only happens when you're running
compiz, and never when you're running metacity, right?
--
Some programs open with windows bigger than maximised
https://bugs.launchpad.net/bugs/12956
You received this bug notification because you are a member of Ubuntu
Deskt
Well,
1) it's not really my call, I just hack the window manager; this is something
the HIG people need to figure out. But
2) notificationisation and minimisation appear to me to be functionally very
similar and I don't see why they should both be supported
3) if only one of them is supported it
Um, yes, it's called "minimisation".
--
Shrinking to notification area should have its own title bar button
https://bugs.launchpad.net/bugs/124326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bu
Okay, before anything else, since you want this on some windows and not
others, we would need a way of knowing which windows knew how to go to
the notification area. This would be done with a new EWMH property on
those windows. This would mean we had to update the EWMH, which can't be
done without
HIG bugs go to http://bugzilla.gnome.org/enter_bug.cgi?product=HIG
Are you suggesting that *every* app should be minimisable to the
notification area, or just the ones that already know how? How is this
different from minimisation?
--
Shrinking to notification area should have its own title bar
This is not, as far as I can see, a Metacity problem. Compiz is failing
to start because it sees another compositor is running. I am not closing
the metacity bug here because I may be wrong, but I will check when I'm
less immediately busy.
** Also affects: compiz (Ubuntu)
Importance: Undecided
I think this is actually slightly different from the bug upstream, and
is a GDM problem (but unless we can repeat it is essentially unfixable).
--
fast-user-switch-applet crashed with SIGSEGV
https://bugs.launchpad.net/bugs/130610
You received this bug notification because you are a member of Ubu
Alt+Escape is probably already bound for you, and this binding will
probably take precedence. Are Ctrl+Escape and Shift+Escape also bound?
--
escape key keyboard shortcuts do not work
https://bugs.launchpad.net/bugs/176195
You received this bug notification because you are a member of Ubuntu
Desk
Thank you for your bug report!
The keystroke ctrl-S causes searching in a treeview widget when that
widget is focussed. You can change this in the keyboard preferences
window for the whole of GNOME.
This has nothing to do with Metacity, incidentally.
** Changed in: metacity (Ubuntu)
Statu
As the person who mostly looks after theme support in Metacity, I'd love
to hear discussions on and suggestions for what's needed in version
three of the format.
--
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because
Oh, I'm sorry, I didn't see that. My fault.
--
impress lacks window list entry in dual head
https://bugs.launchpad.net/bugs/156272
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for metacity in ubuntu.
--
desktop-bugs mailing list
desk
Oh, don't apologise for asking questions :) I think
http://qa.openoffice.org/issue_handling/pre_submission.html is the place
to go, but if you have problems come back and ask. Once you're done,
post here about where the new bug report is and we can track it from
launchpad.
--
impress lacks window
Sounds very much like an Impress problem, then. If you raise it
upstream, link to it here so I can subscribe to the upstream bug in case
I can be of any help from the window manager side.
--
impress lacks window list entry in dual head
https://bugs.launchpad.net/bugs/156272
You received this bug
If you've tried it in (say) kwin and icewm and got the same result, it's
probably a problem with the way Impress talks to WMs rather than any WMs
getting things wrong.
So both these windows are on the same display, yet the presence of the
second display causes the problem? That's pretty bizarre. I
If it occurs regardless of WM, it is not a bug in metacity.
** Changed in: metacity (Ubuntu)
Status: New => Invalid
--
impress lacks window list entry in dual head
https://bugs.launchpad.net/bugs/156272
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
What is the result of
gconftool -g /apps/metacity/general/focus_mode
on your system?
--
Clicking mouse does not always give clicked window focus
https://bugs.launchpad.net/bugs/158564
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
Is this repeatable?
--
metacity crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/157627
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
https://lists.ubuntu.com/
Sebastien was correct: it was a feature added in the constraints-
experiments branch at revision 2275 on 14 November '05:
http://svn.gnome.org/viewvc/metacity/branches/constraints_experiments/src/frames.c?annotate=2275
which made it into trunk along with everything else from that branch
five days
Upstream read this too, you know :) I'll talk to my fellow-developers
and look in the changelog and try to figure out what to do. (I don't
remember this going in, so I don't have any recollection of whether this
is the result of a compromise reached after some great primordial battle
of the First A
(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 y
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
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
https://bugs.launchpad.ne
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
desktop-bugs@lists
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
https://bugs.launchpad.net/bug
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 con
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, whi
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 recei
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
https://lists.ubuntu.com/m
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 PROTECT
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
--
desktop-b
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 mis
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, ar
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
ht
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
https://lists.ubuntu.com/mai
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
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.
** Bug
This is explicitly done in window_activate() in window.c. Elijah added
the check in revision 1.408; I've contacted him to ask why.
--
gtk.Window.present()
https://launchpad.net/bugs/36485
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/deskto
Confirmed. This doesn't seem to happen in 2.17.1 (the version in Edgy)
but it occurs with HEAD. Now investigating.
** Changed in: metacity (Ubuntu)
Assignee: Ubuntu Desktop Bugs => Thomas Thurman
Status: Unconfirmed => Confirmed
--
gtk.Window.present()
https://launchp
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
desktop-bugs@lists
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
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 in
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
101 - 195 of 195 matches
Mail list logo
