[Bug 523688] [NEW] postinst calls start(8) instead of invoke-rc.d(8), ignores policy-rc.d(8).
Public bug reported: policy-rc.d(8) can be used to prevent sysvinit services from booting. This is particularly important within chroots. In Debian Sid, I used pbuilder(8) to create a lucid "base.tgz" chroot. I then used pbuilder --login to get a shell, and ran "apt-get install apport". (I had heard that apport didn't just fire up a web browser, and so I was trying to use it to report a bug in lucid's kernel.) To my surprise, I found the postinst was trying to start a service: Setting up apport (1.12-0ubuntu5) ... start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused Luckily it failed, because I wasn't running upstart outside the chroot. But it seems to me that either upstart's start(8) should either honour policy-rc.d, or at least reinvent it. I see five things that could happen here: - I've misunderstood the error message. Flag MOREINFO. - upstart already has a policy-rc.d equivalent, and apport needs to be told to honor it in apport's postinst. Assign to apport. - upstart already has a policy-rc.d equivalent, and pbuilder needs to be told to create the appropriate "deny all" policy when creating Ubuntu-based chroots. Assign to pbuilder. - upstart has no policy-rc.d equivalent, and needs to grow one. Assign to upstart. - upstart has no policy-rc.d equivalent, and the upstart developers think it doesn't need one. Flag WONTFIX and I get grumpier. ProblemType: Bug Architecture: amd64 Date: Thu Feb 18 08:25:52 2010 DistroRelease: Ubuntu 10.04 Package: apport 1.12-0ubuntu5 PackageArchitecture: all ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: apport Uname: Linux 2.6.24-23-openvz x86_64 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid upstart -- postinst calls start(8) instead of invoke-rc.d(8), ignores policy-rc.d(8). https://bugs.launchpad.net/bugs/523688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523688] Re: postinst calls start(8) instead of invoke-rc.d(8), ignores policy-rc.d(8).
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39352001/Dependencies.txt -- postinst calls start(8) instead of invoke-rc.d(8), ignores policy-rc.d(8). https://bugs.launchpad.net/bugs/523688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523688] Re: postinst calls start(8) instead of invoke-rc.d(8), ignores policy-rc.d(8).
Acting upon information received, I have filed http://bugs.debian.org/571054 and http://bugs.debian.org/571056 This malone ticket should probably be linked to those debbugs tickets, and reassigned to pbuilder. ** Bug watch added: Debian Bug tracker #571054 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571054 ** Bug watch added: Debian Bug tracker #571056 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571056 -- postinst calls start(8) instead of invoke-rc.d(8), ignores policy-rc.d(8). https://bugs.launchpad.net/bugs/523688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539432] [NEW] powerbtn.sh assumes acpi-support is installed.
Public bug reported: Binary package hint: acpid As you can see from the transcript below, acpid's power button event handler has started to assume that acpi-support is installed. As I only need the power button to be supported, I haven't installed acpi-support. # sh -vx /etc/acpi/powerbtn.sh #!/bin/sh # /etc/acpi/powerbtn.sh # Initiates a shutdown when the power putton has been # pressed. . /usr/share/acpi-support/power-funcs + . /usr/share/acpi-support/power-funcs .: 1: Can't open /usr/share/acpi-support/power-funcs ProblemType: Bug Architecture: i386 Date: Tue Mar 16 08:36:30 2010 DistroRelease: Ubuntu 10.04 Package: acpid 1.0.10-5ubuntu2 ProcEnviron: PATH=(custom, no user) LANG= SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: acpid Uname: Linux 2.6.32-16-generic i686 ** Affects: acpid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- powerbtn.sh assumes acpi-support is installed. https://bugs.launchpad.net/bugs/539432 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539432] Re: powerbtn.sh assumes acpi-support is installed.
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/40997515/Dependencies.txt -- powerbtn.sh assumes acpi-support is installed. https://bugs.launchpad.net/bugs/539432 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 529686] Re: Depressing power button does not shutdown computer
Jonathan Thomas wrote: > Looks like acpid needs a dependency on acpi-support. Um, isn't the whole point of separating acpi-support from acpid that you can use the latter without being forced to pull in all the laptop/desktop-oriented dependencies of the former? -- Depressing power button does not shutdown computer https://bugs.launchpad.net/bugs/529686 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315833] subscribe
subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315833 Title: Ubuntu’s rmadison should have wider column defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/madison-lite/+bug/315833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781397] subscribe
subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781397 Title: Help opens web browser (Epiphany, Konqueror), Inkscape stays in modal state . To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/781397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
Serge Hallyn wrote: > @Joseph, > > re-enabling CONFIG_NET_NS has been rejected. As I understand it, > because backport kernels are supported on LTS releases, that is seen as > the right path for those requiring network namespaces. At least one other person on this ticket asserted that the backport kernels are too unreliable for their taste. Bringing in a whole new kernel to reenable one option sounds like lunacy to me. I am not enthusiastic about this solution -- I would rather reroll the LTS 2.6.32 kernels (as they appear on lucid-security) with a trivial in-house patch that reenables cgroups, than to run a completely new kernel from backports. And indeed, as soon as I see a kernel USN that worries me sufficiently, that is exactly what I will do. Until then I have simply pinned the kernel at 2.6.32-31. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 796937] [NEW] Disable CONFIG_NET_NS (for #720095) breaks LXC
Public bug reported: affects ubuntu/lxc affects ubuntu/linux importance critical tag regression-updates done Justification: LXC is the *ONLY* lightweight virtualization system available in Lucid; without it, the next lightest is KVM. My containers need their own network stacks. After upgrading from 2.6.32-31 to -32, my containers completely failed to start. I believe this is because you removed CONFIG_NET_NS for #720095. This *may* even break containers that share host node's network stack, I haven't checked. The lxc package includes an "lxc-checkconfig" script you can use to check the compile-time options of the running kernel. ** Affects: linux (Ubuntu) Importance: Critical Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: regression-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796937 Title: Disable CONFIG_NET_NS (for #720095) breaks LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/796937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 796993] subscribe sconklin
subscribe sconk...@canonical.com done I was talking to sconklin in #ubuntu-kernel about this issue and he asked to be subscribed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796993 Title: Disable CONFIG_NET_NS (for #720095) breaks LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/796993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581744] Affects lucid
affects lucid thanks >From #ubuntu-server: 13:54 So guess what I just discovered 13:54 Purging ufw from lucid causes it to disable the firewall -- EVEN IF ufw wasn't involved in firewalling 13:55 This is especially great when I happen to be removing ufw from a chroot, on a production server running AT A PRISON 13:56 Grin! This is why we should do our learning and trying out new things on a test machine in a safe and controlled environment... I don't think a live production server in a prison counts as a "safe and controlled environment" :) 13:57 jmarsden, thanks - reading it now - urr once samba.org wakes up! 13:57 jmarsden: well, yes, we did test things 13:57 fluvvell: You're welcome 13:57 jmarsden: but you tend not to notice when the firewall falls into "allow all" mode on the test box, or you just assume it was one of the other idiot devs that did it 14:06 urk, ufw is installed by default! I never noticed that when I installed shorewall 14:12 fluvvell: it's installed but not enabled 14:12 fluvvell: BUT, purging it doesn't check whether it's enabled first 14:13 IMO its postrm should say "am I enabled? If not, leave the firewall the hell alone" 00:21 twb: re ufw purge-- this is bug #581744, fixed in maverick. would you mind adding a comment to that bug, saying it affects you on lucid, and I can do an SRU This is with a 8.04 server as the host OS and a 10.04 chroot (generated by extracting the filesystem.squashfs from the 10.04.3 desktop live/install CD). You can *probably* reproduce this by simply debootstraping a lucid chroot, chroot it apt-get install ufw, chroot it apt-get purge ufw. ** Also affects: lucid Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581744 Title: Purging should not set reset policies/chains if ufw wasn't enabled -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660904] [NEW] tcpdump 4.0.0-6ubuntu3 denied read access to ethers(5) by apparmor profile
Public bug reported: affects ubuntu/tcpdump importance low While debugging the configuration of my Ubuntu router, I noticed the following in dmesg: [ 2410.773511] type=1503 audit(1286949714.517:12): operation="open" pid=1228 parent= profile="/usr/sbin/tcpdump" requested_mask="r::" denied_mask="r::" fsuid=0 ouid=0 name="/etc/ethers" [92714.036092] type=1503 audit(1287040017.780:13): operation="open" pid=19770 parent=19592 profile="/usr/sbin/tcpdump" requested_mask="r::" denied_mask="r::" fsuid=0 ouid=0 name="/etc/ethers" I don't know why tcpdump *wants* to access ethers(5); probably to supplement the in-kernel neighbours (ARP) table. Note that out-of-the-box there is no /etc/ethers, which is probably why nobody noticed this before. I use ethers(5) to tell dnsmasq which MACs get "fixed" IPs via DHCP allocation. ** Affects: tcpdump (Ubuntu) Importance: Low Status: New -- tcpdump 4.0.0-6ubuntu3 denied read access to ethers(5) by apparmor profile https://bugs.launchpad.net/bugs/660904 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537133] subscribe trentb...@gmail.com
subscribe trentb...@gmailcom thank you -- mountall issues with NFS root filesystem https://bugs.launchpad.net/bugs/537133 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
