[Bug 1257857] Re: cgroup-lite fails to install in container in precise
Upgrading ubuntu server 12.04 today still fails with the following: $ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up cgroup-lite (1.1.4) ... start: Job failed to start invoke-rc.d: initscript cgroup-lite, action start failed. dpkg: error processing cgroup-lite (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: cgroup-lite E: Sub-process /usr/bin/dpkg returned an error code (1) Also reported at http://askubuntu.com/questions/401268/dpkg-error- processing-cgroup-lite-configure#new- answer?newreg=4db336bfa0b248e2965009cec7186ee8 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1257857 Title: cgroup-lite fails to install in container in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1257857/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1257857] Re: cgroup-lite fails to install in container in precise
Upgrading ubuntu server 12.04 today still fails with the following: $ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up cgroup-lite (1.1.4) ... start: Job failed to start invoke-rc.d: initscript cgroup-lite, action start failed. dpkg: error processing cgroup-lite (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: cgroup-lite E: Sub-process /usr/bin/dpkg returned an error code (1) Also reported at http://askubuntu.com/questions/401268/dpkg-error- processing-cgroup-lite-configure#new- answer?newreg=4db336bfa0b248e2965009cec7186ee8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257857 Title: cgroup-lite fails to install in container in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1257857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015941] [NEW] SUDO_USER should be used also when calling with 'vcs commit'
Public bug reported: In the past a patch was submitted to have the unprivileged user calling 'sudo etckeeper' being reported as the commit author instead of root. This involved using SUDO_USER instead of USER when calling the undelying VCS command. This appear to be implemented only for 'etckeeper commit'. My workflow more frequently involves calling 'etckeeper vcs add/commit' to separate logically different changes and for documentation purpose. I can try to propose a patch for this but hints are welcome to focus on the right place to implement such a change. Reporting here because I use etckeeper (0.52) with Ubuntu server (11.04) but looking at upstream code, no related changes result in the repo. ** Affects: etckeeper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1015941 Title: SUDO_USER should be used also when calling with 'vcs commit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1015941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015941] Re: SUDO_USER should be used also when calling with 'vcs commit'
Hi Marc, After checking my vcs backend configuration (I use git here), I found a misconfiguration of user settings. Now, I have a normalized behaviour of both workflows. Thank you for the valuable suggestion! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1015941 Title: SUDO_USER should be used also when calling with 'vcs commit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1015941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015941] [NEW] SUDO_USER should be used also when calling with 'vcs commit'
Public bug reported: In the past a patch was submitted to have the unprivileged user calling 'sudo etckeeper' being reported as the commit author instead of root. This involved using SUDO_USER instead of USER when calling the undelying VCS command. This appear to be implemented only for 'etckeeper commit'. My workflow more frequently involves calling 'etckeeper vcs add/commit' to separate logically different changes and for documentation purpose. I can try to propose a patch for this but hints are welcome to focus on the right place to implement such a change. Reporting here because I use etckeeper (0.52) with Ubuntu server (11.04) but looking at upstream code, no related changes result in the repo. ** Affects: etckeeper (Ubuntu) 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/1015941 Title: SUDO_USER should be used also when calling with 'vcs commit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1015941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015941] Re: SUDO_USER should be used also when calling with 'vcs commit'
Hi Marc, After checking my vcs backend configuration (I use git here), I found a misconfiguration of user settings. Now, I have a normalized behaviour of both workflows. Thank you for the valuable suggestion! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015941 Title: SUDO_USER should be used also when calling with 'vcs commit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1015941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879166] Re: Kobil smartcard reader stops working due to libmtp-common
Hello, I went into a potentially related problem with a USB scanner. It is working fine in Lucid but fails in Oniric. After some investigation I narrowed down the problem to the mtp-probe script which is run by udev rules when USB devices get connected. As fas as I understand this is supposed to check if a generic USB device has MTP capabilities. See my question here [1] for more details. In order to verify if your smartcard reader is also mtp-probe unfriendly you could try to temporary rename /lib/udev/mtp-probe. For my scanner this was enough to bring it back. See [1] for a more persistent solution. I noticed other udev rules exceptions for some sensitive devices in upstream code used by libmtp people to build udev rules: shall we add exceptions for any buggy device which does not survive a mtp-probe? I have no idea where is the best place to fix this... Please, let me know if this is really related to my problem. [1] https://answers.launchpad.net/ubuntu/+source/sane- frontends/+question/178414 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879166 Title: Kobil smartcard reader stops working due to libmtp-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/879166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 466687] [NEW] BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8
Public bug reported: This incident happened while rebooting a Virtualbox WinXP guest ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gizero 2512 F pulseaudio CRDA: Error: [Errno 2] Nessun file o directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe7f8000 irq 22' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10438357,00100101' Controls : 35 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8fc000 irq 17' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100100' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Date: Sat Oct 31 14:41:10 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=8a71a97a-e93c-49e3-9c55-6eb9ee8e1146 IwConfig: lono wireless extensions. eth0 no wireless extensions. vboxnet0 no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: fglrx Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: root=/dev/md0 ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: SourcePackage: linux Tags: kernel-oops Title: BUG: unable to handle kernel NULL pointer dereference at 00b8 Uname: Linux 2.6.31-14-generic x86_64 WpaSupplicantLog: dmi.bios.date: 08/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd08/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- BUG: unable to handle kernel NULL pointer dereference at 00b8 https://bugs.launchpad.net/bugs/466687 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 466687] Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/34777811/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/34777812/AplayDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/34777815/ArecordDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/34777817/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/34777819/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/34777820/Card0.Codecs.codec.0.txt ** Attachment added: Card1.Codecs.codec.0.txt http://launchpadlibrarian.net/34777821/Card1.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/34777822/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34777823/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/34777824/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/34777825/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/34777826/OopsText.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/34777827/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/34777828/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/34777829/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/34777831/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/34777833/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/34777834/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/34777836/WifiSyslog.txt -- BUG: unable to handle kernel NULL pointer dereference at 00b8 https://bugs.launchpad.net/bugs/466687 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 45842] Re: nfs shares not mounted at startup
I investigated a little bit more around what david said on 2006-05-26 and found that /etc/network/if-up.d/mountnfs is not executed at boot because eth0 is already configured by the udev scripts. I checked this by removing my /etc/udev/rules.d/85-ifupdown.rules (causing the interface to be brought up before /etc/init.d/networking execution). This works for me and seems to have no side effects, but I have no idea if/how this could affect systems with hotpluggable network interfaces. Maybe it is a matter of fixing the udev rule or, if udev is really supposed to be run before networking scripts, to allow these to be aware of a possibly already configured iface. If I have some more time I'll check how this is arranged in other distros -- nfs shares not mounted at startup https://bugs.launchpad.net/bugs/45842 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
