[Bug 86307] Re: Weird behaviour with Beryl.

2012-09-29 Thread Thomas Hotz
Can somebody please close this bug completely please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/86307 Title: Weird behaviour with Beryl. To manage notifications about this bug go to:

[Bug 86307] Re: Weird behaviour with Beryl.

2008-01-16 Thread Christian Reis
** Changed in: beryl Importance: Unknown = Undecided Bugwatch: Beryl Project Bugs #971 = None Status: Unknown = New -- Weird behaviour with Beryl. https://bugs.launchpad.net/bugs/86307 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 86307] Re: Weird behaviour with Beryl.

2007-03-31 Thread Nick
The behaviour I'm seeing here is that when FSP is set to High or Extreme, invoking yakuake with F12 results in normal behaviour; the other half of the time, it shows up behind the front window. _Focus_ works as expected in all cases. Xprop indicates that there are no differences between the

[Bug 86307] Re: Weird behaviour with Beryl.

2007-03-27 Thread Nick
** Changed in: beryl-manager (Ubuntu) Sourcepackagename: beryl-manager = beryl-core Assignee: (unassigned) = Nick -- Weird behaviour with Beryl. https://launchpad.net/bugs/86307 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86307] Re: Weird behaviour with Beryl.

2007-03-25 Thread Matt Sicker
OK, I remember seeing this bug on Beryl's tracker, and now that Ubuntu officially has Beryl in its repositories, I can move the bug to beryl- manager and link to its external bug report. Enjoy! ** Bug watch added: Beryl Project Bugs #971 http://bugs.beryl-project.org/ticket/971 ** Also

[Bug 86307] Re: Weird behaviour with Beryl.

2007-03-25 Thread Nick
Oooh, lovely. It's actually a beryl-core bug, though, and I officially fail at launchpad. Meh. Workaround is, of course, FSP set to none, but the FSP code was taken (almost) verbatim from kwin, so it's interesting that kwin doesn't have the problem. Will look into it. -- Weird behaviour with