I have also recompiled the Ubuntu kernel with this flag enabled and can
confirm that NFS exports are now working. Trivial patch (for amd64, I am
happy to reroll for other platforms if desired) is attached.
** Patch added: "1121699.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/112
apport does not find anything of relevance. I am using Ubuntu Server
12.10 amd64, with standard kernel, aufs and nfs packages. I have
confirmed that CONFIG_AUFS_EXPORT appears to be disabled both in the
distributed kernel and in the Ubuntu Kernel git HEAD. This flag is
documented as a requirement f
Public bug reported:
This is needed to export aufs filesystems via nfs.
This was set in a previous version (in Debian - http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=490079), and released in Ubuntu build for
aufs 0+20080719-4
(https://launchpad.net/ubuntu/+source/aufs/0+20080719-4), so this c
Public bug reported:
This is related to #626451 - I have confirmed that the fix from that
ticket is present in /etc/apparmor.d/abstractions/ubuntu-
browsers.d/multimedia however the problem is not fixed.
The Google Talk plugin (64 bit on my 12.04 system) is installed, but
does not show up in plug
This also breaks the ability to use php within bash "complete -F"
function code (used for shell auto-completion). I have attached a test
case (test instructions and expected/actual results are comments in the
file). I am using the Jaunty PHP - PHP 5.2.6-3ubuntu4.1 with Suhosin-
Patch 0.9.6.2 (cli)
Debian has a openssh-blacklist-extra package that includes this blacklist file
and a few others:
http://packages.debian.org/sid/openssh-blacklist-extra
The download links are broken, but you can download the deb from
http://http.us.debian.org/debian/pool/main/o/openssh-blacklist/openssh-blacklist
@Ovation1357 - I think you are correct that the USB/flash drive is a
correlation, however I don't think it is an absolute dependence, because
I was using a fresh Ubuntu install on a totally normal HP desktop
machine hard disk with no USB/flash in sight. The only factor I can
think of is perhaps the
I checked out the trunk for gnome-keyring-daemon from svn.gnome.org,
installed gnome-devel and recompiled (installing with --prefix=/usr -
ugly, but not likely to break things worse than they are now!). I
restarted gdm and could now log in fine (and the daemon did not even
crash after login).
The
*** This bug is a duplicate of bug 218434 ***
https://bugs.launchpad.net/bugs/218434
** This bug has been marked a duplicate of bug 218434
gnome-keyring-daemon crashed with SIGSEGV
--
gnome-keyring-daemon segfaults
https://bugs.launchpad.net/bugs/216685
You received this bug notification
Ditto, exact same situation as the above - login to gdm causes it to
halt permanently on beige screen (and I can still Ctrl-Alt-F1 and log in
fine on the terminal). Log messages are also identical, so I won't
bother reposting.
I can add however that this bug reproduces on a completely new hardy
in
I can also reproduce this problem:
System.ExecutionEngineException: Failed to create shadow copy (mkstemp).
This is using 1.1.17.1-ubuntu6~dhx1 (not official)
--
gmcs keeps crashing
https://launchpad.net/bugs/61670
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
11 matches
Mail list logo