[Bug 1778684] Re: man: command exited with status 4
Can anybody recreate this issue with a 4.15 kernel from the official Ubuntu archive? ** Changed in: man-db (Ubuntu Bionic) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Hello, I believe this issue can be addressed by backporting kernel commit 9fcf78cca198600b27c44b4e50f00f8af3927f17 to your kernel. (Possibly other changes are also necessary; this change may build upon earlier changes, and may be further modified by future changes. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
** Tags added: id-5d5ebbb85648f084c34ca454 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
@xnox, that seems unlikely to be helpful since the version you quote is older than the one in bionic! The reference to Debian bug #889617 is probably not correct even though they have similar symptoms. I don't recall fixing this particular problem in Debian, and we probably need to pull in an AppArmor expert to figure out what the problem is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
The duplicate bug has a "profile not found" syslog message which seems likely to be relevant; I suspect there's something going on in relation to man-db's use of stacked profiles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
** Also affects: man-db (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: man-db (Ubuntu Bionic) Status: New => Confirmed ** Changed in: man-db (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
I think we want to backport changes from the below upload to fix this man-db (2.8.1-1) unstable; urgency=medium * New upstream release. * Use stacked profiles for subprocesses so that AppArmor realises that they constitute a reduction in privileges and allows the transition even after a seccomp filter has been installed. * Build with seccomp again, now that it works in conjunction with AppArmor. * Breaks/Replaces manpages-tr (<< 1.0.5.1-3) (closes: #889805). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
** Changed in: man-db (Ubuntu) Status: Incomplete => Confirmed ** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Same problem here on a raspberry running volumio2. We've run out of ideas here. Everything seems ok, yet still the result is: Manual page man(1) line ?/? (END) (press h for help or q to quit) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Is groff installed? apt install groff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Worked on my pine64 but on the Rpi 3, OS at same level, it gives the following :' sudo apt install apparmor-utils Reading package lists... Done Building dependency tree Reading state information... Done apparmor-utils is already the newest version (2.12-4ubuntu5.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [3]- Done url=https://www.topgear.com.ph/features/lifestyle/lenovo-amd-laptops-a1008-20181202 [5]+ Done cd=CAEYACoUMTA0MDYyMTQwMTQ3MTcxODkyNTEyHGM5OTdmNGFhNDY5YzIwOWY6Y28udWs6ZW46R0I $ $ sudo aa-disable /usr/bin/man Disabling /usr/bin/man. ERROR: Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.) Warning: unable to find a suitable fs in /proc/mounts, is it mounted? Use --subdomainfs to override. Up shot man no still not working. Any Help, ideas available anybody ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
** Changed in: man-db Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
** Also affects: man-db via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889617 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Great, it works for 4.12, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Seems that problem in apparmor profile loading on older kernels. I have the same issue on custom kernel 4.4, but with ubuntu kernel 4.15 everything ok. Workaround for older kernels: apt install apparmor-utils aa-disable /usr/bin/man Upstream Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889617 ** Bug watch added: Debian Bug tracker #889617 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889617 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Switching to kernel 4.15 resolves also the problem for me. But unfortunately i have some applications that need kernel version 4.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
I am happy to here this Deepack, but unfortunately, for many reasons, I have to rely on 4.12! :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Thanks Lancillotto. It worked for me too :-) I had had Kernel 4.10.2-041002. upgrading to 4.15.0-29 solved this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
For me happens on Ubuntu 18.04 and Kernel 4.12. Switching to 4.15 it works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
I think it happens since upgraded from 16.04 to 18.04. ** Attachment added: "man.trace" https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+attachment/5170547/+files/man.trace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Hi Colin, Yes, running strace command has reproduced the bug. Attaching the man.trace herewith. ** Attachment added: "man.trace file" https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+attachment/5168586/+files/man.trace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Please run: strace -f -o man.trace -s 1024 man man ... make sure it reproduces the same bug, and attach the resulting man.trace file to this bug report. Thanks. ** Changed in: man-db (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
I have the same issue. How can I solve it? Thank you! Antonio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778684] Re: man: command exited with status 4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: man-db (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/1778684 Title: man: command exited with status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1778684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
