So we see this consistently, and it seems to happen (sometimes) when
Chrome pops up a new window (I see it when gchat creates a mole, or when
a link opens in a new tab, though not always). The size of the white box
is the size of whatever window was being created.
The white box is not a window; X
Public bug reported:
unity --reset is great if you've broken your configuration.
However. If you've broken it so much that it doesn't even start
sensibly, or you can't find a terminal, then you need to use a VT or ssh
to run it. And then you get this error:
% unity --reset
WARNING: no DISPLAY
ping?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933870
Title:
libnfsidmap2 fails to install
To manage notifications about this bug go to:
ping
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963533
Title:
opencryptoki version churn has broken some systems
To manage notifications about this bug go to:
Yes, we know for sure that purge reinstall fixes the problem...that's
our advice to affected users.
But the packaging system is supposed to work automatically, and we rely
on that to maintain tens of thousands of machines. (Though obviously not
that much is running precise right now.) This issue
Are you sure that every old version of the package correctly stopped the
daemon in the prerm?
(Hey, that might explain why the other bug I noted was happening.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In our case, the problem was traced to lockd and portmap. Specifically,
without access to lockd, NFS can only do the 30 second fallback method
of retrying locks. We had restricted portmap to listen only on
localhost, which is why lockd was unable to function properly. Once we
unrestricted portmap
A new option has been added to lightdm which provides the needed
functionality here. So AFAIC this one can be closed.
On Mar 27, 2012 8:31 AM, Sebastien Bacher seb...@ubuntu.com wrote:
** Also affects: indicator-session
Importance: Undecided
Status: New
--
You received this bug
Fix works for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880104
Title:
Using pam_group results in: pam_group(lightdm:setcred): unable to set
the group membership for user: operation not
We rely on pam_mkhomedir. We're using it with the standard options.
It used to work fine on lightdm, but as of recently, it doesn't.
It works fine with ssh.
This is crucial for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The documentation for pam_open_session says, It should be noted that
the effective uid, geteuid(2). of the application should be of
sufficient privilege to perform such tasks as creating or mounting the
user's home directory for example.
AFAICT, this is contrary to Steve Langasek's assertion that
Public bug reported:
In the ongoing version churn of opencryptoki and libopencryptoki0, we
have users who are in the following state:
Our archive (and apt-cache policy agrees) has version 2.3.1+dfsg-
3ubuntu4 for both opencryptoki and libopencryptoki0.
But installed on the system are
Public bug reported:
Version 2.3.1+dfsg-3ubuntu4.
opencryptoki postinst does
invoke-rc.d opencryptoki start || exit $?
In turn, /etc/init.d/opencryptoki [start] does
start-stop-daemon --start --quiet --pidfile /var/lib/opencryptoki/.slotid
--exec /usr/sbin/pkcsslotd --
But if pkcsslotd
It is possible that this is the root cause underlying
https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/963533.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963565
Title:
opencryptoki
Whoops, error in editing. the transcript of the failing init.d script
should look like this:
# /etc/init.d/opencryptoki stop
Stopping PKCS#11 slot daemon: pkcsslotd.
# echo $?
0
# /etc/init.d/opencryptoki start
Starting PKCS#11 slot daemon: pkcsslotd.
# echo $?
0
# /etc/init.d/opencryptoki start
I'm concerned that this bug exposes a very severe security bug in X, at
least, on affected hardware.
If I understand correctly, I could create a pixmap, not initialize it, and
thus gain access to various bits of previous screen real-estate. (Note
that people have seen on their display desktop
Didn't we just have this?
https://bugs.launchpad.net/bugs/954303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960546
Title:
package libopencryptoki0 2.3.1+dfsg-3ubuntu2 failed to
It's back:
https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/960546
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954306
Title:
package libopencryptoki0 2.3.1+dfsg-3ubuntu1 failed to
I know apport-collect is now SOP to insert a delay into the processing
of every bug, but I do think it's perfectly clear what's going on here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953494
Thanks for this Robert; it works great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844044
Title:
Unity Greeter - Add Network Login option
To manage notifications about this bug go to:
I just tried a login with a second factor module in place in pam, and
whether it's deliberate or not, I see that a two-factor auth prompt
shows up nicely in the unity-greeter box. Perhaps this is because we
switched to teh new greeter-show-manual-login and disabled greeter-hide-
users, or not, but
We've seen this as well on Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877904
Title:
Top panel visible in locked screen
To manage notifications about this bug go to:
An additional data point, consistent with what's been said here, is that
our users with lightdm and unity-greeter who log in to a gnome-shell
session instead of a unity session see exactly the same sort of
corruption.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Version 2.3.1+dfsg-3ubuntu1 of opencryptoki includes
/usr/lib/opencryptoki/stdll/PKCS11_SW.so in both the libopencryptoki0
and opencryptoki packages:
$ dpkg-deb --contents
/var/cache/apt/archives/opencryptoki_2.3.1+dfsg-3ubuntu1_amd64.deb | grep
PKCS11
lrwxrwxrwx
Public bug reported:
In lucid, ia32-libs contains the 32-bit version of libgconf-2-4:
$ dpkg -L ia32-libs | grep gconf
/usr/lib32/pkgconfig
/usr/lib32/pkgconfig/gtk-engines-2.pc
/usr/lib32/gio/modules/libgiogconf.so
/usr/lib32/libgconf-2.so.4.1.5
/usr/lib32/libgconf2-4
We no longer see the error message, but pam_group is still not setting
the groups we need it to set.
** Changed in: lightdm
Status: Incomplete = Confirmed
** Changed in: lightdm (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member
Please do not confuse hiding user list with providing a user-name
entry box.
We want a user list *and* we want the ability to enter a user-name by
hand if the person logging in is not in the list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
data leakage is a security issue :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931967
Title:
Corrupted graphics after the login until the unity launcher appears
To manage notifications about
Robert, I think that will be very great for our case. I agree completely
that it is not plausible to distinguish a network account. For our
part, we are not concerned so much with the labeling, and whatever looks
good to the designers is fine with us. I'm very pleased that this change
will let us
Here is a screenshot of glitchy menu behavior. Here, menus show the
background shadow effect, but the actual foreground text is missing or
partial, and shows up when you mouse over it.
In both cases, I believe the bug is that Unity thinks that some texture
or other has particular contents, but
Screenshot of glitchy menu
** Attachment added: IMG_20120227_144839.jpg
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/936506/+attachment/2819255/+files/IMG_20120227_144839.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here is screenshots of the glitchy launcher. This happens (reliably) on
a 24 Dell monitor, the system is a Dell T3500 with Quadro FX 580.
This happens when I switch from the X display to a VT and then back. The
launcher and the top menu/notification bar both look glitchy. As soon as
the mouse
*** This bug is a duplicate of bug 844039 ***
https://bugs.launchpad.net/bugs/844039
John, I'm confused by why you think this is a dup of bug #844039. That
bug requests that the Other option be disabled. This bug complains the
opposite: that it *is* disabled, even when it should not be.
--
Public bug reported:
Reporting against unity-greeter because it's a UI problem, but it might
well go deeper.
We have a pam auth module which needs to use pam_conv.conv (the callback
function which prompts the user). It implements a two-factor
authentication regime, in which the first factor is a
It appears that user-list.vala (user_list.show_prompt) basically ignores
the text of the prompt and displays its own messages, based on the guess
that if echo is off then it's a password, and if echo is on, it's a
user, sort of, sometimes.
This is quite wrong.
--
You received this bug
I have seen this bug both on precise and oneiric (haven't checked
anything older).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937665
Title:
Ubuntu 12.04, compiz snap plugin behaves
Has any progress happened on this bug? It turns out it's even more
important to us than we initially realized; we rely on it to add users
to the fuse and cdrom groups; being absent those groups cases real
inconvenience.
--
You received this bug notification because you are a member of Ubuntu
This appears to be one of several serious regressions in
295.20-0ubuntu1. I can confirm that we see it as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936506
Title:
graphical glitch after
Public bug reported:
trousers version 0.3.7-2 can't start
$ sudo /etc/init.d/trousers start
* Starting Trusted Computing daemon tcsd
I'm pleased to report that with the newly rebuilt installer images that
include this patch, the symptoms we reported are no longer visible.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926447
It's already there.
On Sun, Feb 5, 2012 at 2:05 PM, Alec Warner
732...@bugs.launchpad.netwrote:
Can we get it in Precise?
On Sun, Feb 5, 2012 at 1:31 PM, Russ Allbery r...@debian.org wrote:
As of libpam-krb5 4.5, the temporary ticket cache will be written to
ccache_dir rather than /tmp if
Public bug reported:
As of ubuntu7 (and maybe ubuntu6), we get failing installs related to
the new resolvconf changes which do the /etc/resolv.conf link in the
postinst.
During the select and install software step, we see /etc/resolv.conf
go away (simply vanish) at some point in the prep step,
We're case 2. Listing all the users is impossible anyhow. Where would you
get the list? But we're OK I believe with listing those who have logged in
before on the particular machine. That's not essential however.
Right now the other selector is totally missing. It should be impossible
for that to
I have confirmed that adding greeter-hide-users=true in the
SeatDefaults stanza of lightdm.conf fixes the problem.
We would still like to have the behavior I saw before, where if a user
was known to the accounts manager, they would be listed, but there was
always an other box also. However, this
No. We are fine with users who have already logged in having their
username visible; that's helpful.
It's not a lightdm issue, but I'm really quite flabbergasted how even
one user shows up in the accounts manager before anyone has logged in,
on our configuration. In any case, we like the idea
By the way, this bug is quite new. With our configuration, in December,
it worked just fine, as far as I can tell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921315
Title:
lightdm greeter
Sounds great. Given the large number of packages using defoma, it might
be worth a comprehensive scan across lucid to make sure the no-op prerm
is in place for all of them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for looking at this Colin; I appreciate the eyes! It's in the
depths of dark magic to me sometimes.
For this to work reliably in a cross-version lucid-precise upgrade,
however, won't you need to push a new libwmf0.2-7 package in lucid that
fixes its prerm?
--
You received this bug
We have this problem too. Our users typically do not have a home
directory until the first time they log in, by the way, with the use of
pam_mkhomedir.so to create it, however this behavior is independent of
whether the home directory exists or not.
We do not see the session chooser widget until
Public bug reported:
In our configuration, nearly all users are granted access to the system
via pam. The User Accounts dialog in Settings shows only a single user
which was created at install time...and I'm not sure where from, because
we preseed d-i passwd/make-user boolean false to try and
Can this please not be closed just because it was (mostly) ignored?
** Changed in: indicator-session (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888714
I'm confused about why chroot_setup is the issue here. It's the apt-
install command inside the grub_probe command which is spitting out
output, and the output it spits out looks like typical apt-get output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We have this problem too. The fix is in grub-installer in the udeb.
The problem is the grub_probe function in that script. It does an apt-
install and then calls grub-probe in the chroot. The apt-install prints
output, however, and the callers of grub_probe expect to see only the
output from
As far as I can tell, this isn't fixed. I just had the following:
Unpacking evince-common (from .../evince-common_3.2.1-1ubuntu4_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/evince-common_3.2.1-1ubuntu4_all.deb (--unpack):
trying to overwrite
Public bug reported:
at-spi (1.32.0-0ubuntu4) contains the file
/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml which is also
present in libatk-adaptor-schemas (2.3.2-0ubuntu3).
At the least a Conflicts is likely needed.
** Affects: at-spi2-atk (Ubuntu)
Importance: Undecided
Public bug reported:
nsscache has a syntax error in
/usr/share/pyshared/nss_cache/lock_test.py which produces a compiler
warning in precise. I believe that Jamie Wilkinson is uploading a patch
to Debian soon, which should get pulled into precise once it's in
Debian.
** Affects: nsscache (Ubuntu)
Public bug reported:
Upgrading from lucid to precise finds a problem with the defoma
invocation in the prerm of the libwmf0.2-7 package, when upgrading from
0.2.8.4-6.1ubuntu2 to 0.2.8.4-8.1ubuntu1, and with apt-get's invocation
of debsums.
The error reported is this, from dpkg (via apt-get):
** Summary changed:
- perl-moules lucid-precise upgrade failure
+ perl-modules lucid-precise upgrade failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901741
Title:
perl-modules lucid-precise
Happens to us too:
Setting up hyphen-en-us (2.7.1-4ubuntu1) ...
Error: update-openoffice-dicts not present or executable. Missing dependency on
dictionaries-common?
Said program is gone now; postinst should call it conditionally.
--
You received this bug notification because you are a member
Public bug reported:
libnm-glib-vpn1 in precise contains the file /usr/lib/libnm-glib-
vpn.so.1 which was also found in lucid's libnm-glib2 package. At the
least it needs to declare an appropriate conflict.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
evince-common version 3.2.1-1ubuntu1 (in precise) contains the file
/etc/apparmor.d/abstractions/evince, which is also found in the evince
package 2.30.3-0ubuntu1.2 (in lucid). It should declare a conflict, at
the very least.
** Affects: evince (Ubuntu)
Importance:
Public bug reported:
The python-desktopcouch-application (version 1.0.8-0ubuntu1) package
contains the file
/usr/share/pyshared/desktopcouch/pair/couchdb_pairing/__init__.py which
also exists in the python-desktopcouch package in lucid
(0.6.4-0ubuntu3.3). A package conflict, at least, should be
Enterprises need to insulate their systems from reporting upstream,
not because of an objection to participating in upstream development,
but because we need to prevent our users from accidentally leaking
confidential information.
Somewhere the following dependency chain needs to be broken:
Our user confirms that 1.34.13 solves the problem on lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882685
Title:
lucid linux-firmware lacks ath3k driver update
To manage notifications about
Got filed against incorrect package for some reason.
** Package changed: shadow (Ubuntu) = xdiagnose (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888749
Title:
xdiagnose declares
Public bug reported:
I need to disable guest logins for lightdm, and did so by adding the
line allow-guest=false to /etc/lightdm/lightdm.conf.
However, this also has the side-effect of disabling the user-switcher in
the indicator area of Unity after I log in, which is bad. I want the
Public bug reported:
xdiagnose currently declares a dependency on apport. This is not
necessary; it seems that xdiagnose includes some apport hooks, but
that's fine to do (and the rest of the package runs fine) without apport
present. This dependency should be changed to a Recommends or Suggests.
I think I see what's going on. By removing the guest account, the
desktop now thinks there is only one user...
First, that's incorrect. With pam, there may well be accounts that
lightdm can log in to, but which are not visible in the accounts
database, and the Switch User Account option would
Let me stress that this is not a fairly minor problem, but is a
critical security vulnerability in some contexts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when
Public bug reported:
The version of linux-firmware in lucid-updates is 1.34.7.
This lacks an update to the ath3k driver which was released in the
git.kernel.org firmware repo on December 13, 2010. See
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-
I think this may have been caused by a local configuration change. We
will not know for certain for a few weeks. I would like to leave the bug
alone until I can confirm this newer understanding, at which point I'll
close it.
There isn't any need to spend energy on it right now.
--
You received
This affects lucid; can the patch be pulled in to an SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/377367
Title:
gnome-terminal doesn't handle colons in URLs
To manage notifications about
On Tue, Oct 4, 2011 at 3:37 PM, Marc Deslauriers
marc.deslauri...@canonical.com wrote:
Actually, we do want a reboot notification when we issue security
updates. When we issue security updates, we don't enter the major
upgrade section, as we don't want the update to automatically restart
How do you distinguish a server from a desktop, and what about servers that
don't run ssl-using daemons?
Thomas
On Oct 4, 2011 2:05 PM, Marc Deslauriers marc.deslauri...@canonical.com
wrote:
We've already removed reboot notifications from openssl on desktops, I'm
just talking about servers.
On Wed, Oct 5, 2011 at 12:54 AM, Marc Deslauriers
marc.deslauri...@canonical.com wrote:
Right now, the best way we have of determining if we're a server or a
desktop is to check if X is running. It's not ideal, and suggestions are
welcome.
I think my question is suggesting that there really
Thank you, David. I've joined that list and added my thoughts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/817269
Title:
Pulseaudio lock of pulsecookie file is pessimal on NFS
To manage
The following patch solves the problem.
** Attachment added: use-read-locks
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/817269/+attachment/2290468/+files/use-read-locks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
/sbin/shadowconfig from the passwd package uses pwck -p and grpck
-p. On some other Linux systems, the -p flag to these programs says to
silently fix problems found in those files.
But the Ubuntu Lucid versions do not actually do that. The Ubuntu Lucid
versions ignore the
[Not sure why launchpad is insisting on labelling this package shadow,
but on lucid it's passwd.]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828319
Title:
shadowconfig uses pwck -p and grpck -p
Oh, that's the source package name.
This bug is also in the Debian stable version of the package as well.
** Also affects: shadow (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reported to Debian bts as http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=638263.
** Bug watch added: Debian Bug tracker #638263
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638263
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The following script (if ~ is in NFS) will demonstrate the problem. The
two pactl processes both try to acquire the lock on the file
simultaneously, and whichever one loses will take thirty seconds before
it wins, because of the needless contention (and the unfortunate facts
of how lockd in NFS
Public bug reported:
Pulseaudio uses a cookie file (normally ~/.pulse-cookie). This file is
manipulated by the code in src/pulsecore/authkey.c. Currently it does this to
read the key:
1) Open the file
2) Acquire a write-lock for the file.
3) Read the file.
4) If the file is not a good cookie,
Public bug reported:
Binary package hint: tcsh
tcsh truncates the .history when multiple scripts are run.
See https://bugzilla.redhat.com/show_bug.cgi?id=648592 for the
description of how to reproduce this.
We know the problem happens in tcsh 6.17.00, and it was reportedly fixed
in 6.17.01
Because we run a modified kernel, it would be inconvenient to need to
install a vanilla system in order to verify the fix there. Etienne has/had a
vanilla setup reproducing the bug. I can confirm that the patch successfully
solves the problem for our kernel.
Thomas
On Thu, Jan 13, 2011 at 8:34
Awesomeness! I'll give it a try today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683938
Title:
kernel crash on symlink chased from NFS to failing automount
--
ubuntu-bugs mailing list
This is not quite right. The second one should use
ARRAY_SIZE(mnt3_procedures). The value happens to be the same, but
still...let's not make a new bug if someone implements another part of
the protocol someday. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'll do some more checking here to see about it.
On Wed, Dec 8, 2010 at 6:29 AM, Fabio Marconi marconifa...@ubuntu-
it.orgwrote:
I assign to metacity, but i cannot reproduce this issue
** Package changed: ubuntu = metacity (Ubuntu)
--
You received this bug notification because you are a
Stefan says While in the case we test, the request is seen as success
but then the authentication flavours do not match and the client does an
explicit umount request (probably the same happens when the
authentication methods are supported but the authentication fails).
I spent a lot of time
What lies behind the comment on the umount call is this: the NFS
protocol requests that clients tell servers when they unmount
partitions, so that servers can stop reporting it in tools like
showmount. The client doesn't care at all if the server ever gets it,
and even if you do an unmount RPC,
I've been busy this morning with other responsibilities, but I can
report now that I agree that no automount involvement is necessary;
merely repeating the mount request eventually provokes the failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Removing the umount attempt seems to make the problem go away. Not a
fix, but it's nice to have a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683938
Title:
kernel crash on symlink
Public bug reported:
Using metacity on gnome in lucid:
Steps to reproduce:
Before everything, make sure you turn of compiz (desktop effects).
1) Open a terminal
2) Maximize it
3) Open another terminal, overlaying on top of the first one
4) Try to grab the title bar of the second
101 - 193 of 193 matches
Mail list logo