Well, you can use Long Path Tool for such issues, it works good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for long path names
To mana
** Changed in: apparmor (Ubuntu Precise)
Status: Confirmed => Invalid
** Changed in: apparmor (Ubuntu Quantal)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Marking the apparmor portion as invalid as the bug is entirely in the
apparmor kernel module, which is tracked under linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name loo
John, does this require a userspace change also, or can we mark the
"apparmor" tasks as invalid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path er
** Branch linked: lp:ubuntu/precise-proposed/linux-armadaxp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for long path names
To manage no
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Tit
This bug was fixed in the package linux - 3.2.0-25.40
---
linux (3.2.0-25.40) precise-proposed; urgency=low
[Luis Henriques]
* Release Tracking Bug
- LP: #1003534
[ Andy Whitcroft ]
* [Config] control.stub is an intermediate product not a dependancy
- LP: #992414
** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for long path names
To manage no
I can confirm that the name lookup errors are gone and AppArmor
correctly grants access to files with long path names.
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
This bug is awaiting verification that the kernel for precise in
-proposed solves the problem (3.2.0-25.40). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not do
This bug was fixed in the package linux - 3.4.0-3.8
---
linux (3.4.0-3.8) quantal; urgency=low
[ Andy Whitcroft ]
* [Config] include include/generated/compile.h
- LP: #942569
* [Config] fix up postinst to ensure we know which error is which
- LP: #1002388
[ Herton Ro
** Changed in: linux (Ubuntu Precise)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for long pa
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progr
** Description changed:
+ == Precise SRU Justification ==
+
+ This bug causes access failures when apparmor is mediating files with
+ long pathnames. This problem is easy to trip when a confined application
+ tries to access data encrypted with ecryptfs, but can occur on any
+ filesystem.
+
+ ==
The test kernel works fine, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for long path names
To manage notifications about this b
I have placed a test kernel with a fix at
http://people.canonical.com/~jj/linux-image-3.2.0-23-generic_3.2.0-23.36~aa_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Since kernel 3.2.0-21-generic the error message is:
info="Failed name lookup" error=-13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for l
Also it only seems to fail when extracting to non-root filesystems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955892
Title:
Failed name lookup - disconnected path error for long path names
To m
I can't reproduce this with anything other than tar.
tar prints these error messages: (note that I don't have any NFS file systems)
tar:
virtualbox-4.1.10-dfsg/src/VBox/Devices/EFI/Firmware2/VBoxPkg/Library/VBoxOemHookStatusCodeLib/VBoxOemHookStatusCodeLib.c:
Cannot open: Stale NFS file handle
20 matches
Mail list logo
