[Bug 1885013] Re: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
It is/was probably just a transitional problem: After using the system for some time now, I experience no problem. It boots as reliable as before after it had to re-run the lilo-configuration again, anyhow, because of me phasing out old(er) kernels. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885013 Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/1885013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885013] [NEW] package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Problem occurred during a (longer) system update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.9 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Wed Jun 24 21:21:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-07-08 (1813 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885013 Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1885013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787228] [NEW] package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Just an upgrade from 16.04.5 to 18.04(.1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 15 16:54:17 2018 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-07-08 (1133 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787228 Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1787228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787223] [NEW] package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error
Public bug reported: While upgrading from 16.04.5 to 18.04(.1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 15 14:28:27 2018 ErrorMessage: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=c6796c6c-41da-4ce3-931e-c09f94ba0a4b InstallationDate: Installed on 2015-07-08 (1133 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 4389W1B ProcFB: ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 SourcePackage: linux Title: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 4389W1B dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W510 dmi.product.name: 4389W1B dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787223 Title: package linux-headers-4.15.0-32-generic 4.15.0-32.35 failed to install/upgrade: installed linux-headers-4.15.0-32-generic package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779687] [NEW] nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to build
Public bug reported: When switching kernels from 4.13.0-45-generic to 4.15.0-24-generic, dkms fails in buildign the nvidia-340 module(s). My graphics component doesn't allow for a newer nvidia driver than the 340 one. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.15.0-24-generic Date: Mon Jul 2 15:44:09 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia/340-340.104/build/nv.c:2407:5: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GT216GLM [Quadro FX 880M] [17aa:2145] InstallationDate: Installed on 2015-07-08 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 4389W1B PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 4389W1B dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W510 dmi.product.name: 4389W1B dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jul 2 15:11:57 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779687 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1779687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744891] [NEW] tp-smapi-dkms 0.41-1: tp-smapi kernel module failed to build
Public bug reported: Known error, but for a different Ubuntu (16.04(.2)) and kernel (4.13) version! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tp-smapi-dkms 0.41-1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.13.0-31-generic Date: Tue Jan 23 09:12:53 2018 DuplicateSignature: dkms:tp-smapi-dkms:0.41-1:./include/linux/moduleparam.h:346:67: error: return from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2015-07-08 (929 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all PackageVersion: 0.41-1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tp-smapi Title: tp-smapi-dkms 0.41-1: tp-smapi kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tp-smapi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744891 Title: tp-smapi-dkms 0.41-1: tp-smapi kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/1744891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534678] Re: huawei plugin not used on for USB webstick E173s-1 [usb: 12d1:14d1/14c9]
You seem to be correct, bug #1539348 describes exactly what happens to the IDs. I haven't yet checked for the "udevadm info" of the device (only), just for the whole tree. In the latter case, it is ok, but this is also the case for bug #1539348! What bug #1539348 doesn't touch nor resolves is the problem of the "dual stack" IPv4/v6 error. Thanks for paying so close an attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534678 Title: huawei plugin not used on for USB webstick E173s-1 [usb: 12d1:14d1/14c9] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1534678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534678] Re: huawei plugin not used on for USB webstick E173s-1 [usb: 12d1:14d1/14c9]
I can now confirm my analysis of the bug! And I got a new and unpleaseant surprise, too. First I compiled a version of modemmanager (1.4.10) where the wrongly returned pci-id 8068:3b34 is swapped to the correct usb-id 12d1:14c9 in "get_device_ids". This is just a hack, of course, no solution. Now the 'huawei' plugin is used instead of the 'generic' one and all seems well. Remember, the whole thing used to work in Ubuntu 15.04 and before! But now the NetworkManager complains with an odd message: NetworkManager[1108]: (ttyUSB2): Failed to connect 'Vodafone WebSessions': Connection requested both IPv4 and IPv6 but dual-stack addressing is unsupported by the modem. And although it is marked as a warning, it makes a network connection impossible: NetworkManager[1108]: (ttyUSB2): device state change: prepare -> failed (reason 'modem-init-failed') [40 120 28] Since the capabilities come from the modemmanager I still think, here is the right place to begin the repair. (From my previous (working!) connections I do know, that IPv4 will be sufficient, but I find no way to signal this to the NetworkManager!) Any usefull advice will be welcome. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534678 Title: huawei plugin not used on for USB webstick E173s-1 [usb: 12d1:14d1/14c9] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1534678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534678] [NEW] huawei plugin not used on for USB webstick E173s-1 [usb: 12d1:14d1/14c9]
Public bug reported: Starting with Ubuntu 15.10 (wily) my USB webstick does not work any longer. It used to work with Ubuntu for several previous versions. My stick is a Huawei E173s-1 with a usb-vendor/-product id 12d1:14d1 before and 12d1:14c9 after 'modeswitch'. The - or at least one - reason for not working any longer is, that modemmanager uses the 'generic' plugin, instead of the 'huawei' one. The behaviour does not depend on my software-configuration. It happens from a plain 15.10 live-version up to my installed up-to-date-patched notebook (amd64 architecture, but from what's written below, I don't think it is architecture-specific.) Using the --debug - option from 'modemmanager' and tracing with gdb after loading the -gdb .deb-package, I came to the following conclusions: The 'huawei' plugin is filtered out in the 'pre' phase, already, the reason being vendor-/product-id mismatch. The vendor-/product-ids 'detected' instead by the "get_device_ids"-function in "mm-device.c" are 8068:3b34 for the Intel USB 2 ehci host controller, which actually is a 'child'(??) device of the stick. The problem arises, when checking the first of the ttyUSBx (x being 0, 1, 2, and 3) devices for the stick in "find_physical_device", which calls "get_device_ids" later on. As far as I can tell, the error originates in the "g_udev_device_get_property" call for ID_VENDOR_ID and ID_MODEL_ID in the 'lib_gudev' library, which returns the false ids. It might even come from 'udev'. A 'udevadm info' display of the USB-tree shows the correct(!) vendor-/product-ids for the whole tree, though! Once the 'generic' plugin has been (wrongly) chosen, the debug info shows the correct ids (12d1:14c9) for the 'selected' device (again). It however won't configure my stick, telling me that the device is not capable of taking ipv4/ipv6 information. So far for the facts. Now allow me some speculation and a proposal: I would assume, that the whole mess comes from the very faulty, buggy and problematic 'systemd', which controls 'udev' in 'wily'. The "lib_gudev" is also a split-off part from it. With 'systemd' it is no longer possible to manually interfere with wrong or questionable decisions, as could be done with standard 'udev' via rules or 'sys-v-init' by changing (ba)sh-scripts. Now my proposal (and wish) would be to install some mechanism in 'modemmanager' to overwrite/force a plugin selection from the outside, as is e.g. done for selecting ports with the "77-mm-huawei-net-port- types.rules" (ID_MM_HUAWEI_MODEM_PORT and similar). Any other mechanism would be welcome, too. With this, one could correct any poor choice made by a binary program or library. And it would not hit ordinary or inexperienced users. Thank you. And thanks for the good work! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: modemmanager 1.4.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 15 17:37:09 2016 InstallationDate: Installed on 2015-07-08 (191 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: modemmanager UpgradeStatus: Upgraded to wily on 2015-10-23 (84 days ago) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534678 Title: huawei plugin not used on for USB webstick E173s-1 [usb: 12d1:14d1/14c9] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1534678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1288726] Re: MicMute key on lenovo w510 thinkpad doesn't work
Hello! Regarding the (complete) failure of the mic-key-test with the last kernel tested (v3.11.10.6-saucy), I can tell you that the situation has not deteriorated with the 14.04 Ubuntu-live beta version kernel; but it didn't get better with it, either. When started from a stick, the mic-key LED(!) worked (again), as it does now with the version 13.10 standard kernel, but the key itself doesn't seem to accomplish anything. This is a message just to keep things up-to-date. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288726 Title: MicMute key on lenovo w510 thinkpad doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1288726] Re: MicMute key on lenovo w510 thinkpad doesn't work
Hello! On Mar 12, Joseph Salisbury wrote: Can you see if this issue also happens with the latest upstream 3.11 kernel? yes, sorry, it still happens today (Mar 13, 2014), and worse, now it seems to ignore the MicMute-Key completely, meaning that the LED also isn't (properly) operated any longer. The kernel version I used for testing ... It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.6-saucy/ .. was [i386] 3.11.10-03111006-generic #201403120635. By the way, there was also no change from the regular switch from version 3.11.0-17 to 3.11.0-18 recently, but here the LED still works. Best whishes, Ruediger Oberhage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288726 Title: MicMute key on lenovo w510 thinkpad doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288726] [NEW] MicMute key on lenovo w510 thinkpad doesn't work
Public bug reported: Starting with linux-kernel 3.11.0-17 (linux-image- extra-3.11.0-17-generic), on a Lenovo ThinkPad W510 the LED within the MicMute key is working in the way that it is on by default (meaning mic is 'mute'/off). It turns off when activating the microphone via 'settings'/Internal Microphone 'on' and lights up again when the mic is turned off, correctly. But the key itself (MicMute, KEY_MICMUTE) isn't showing any function; especially it is not turning the microphone on or off. The change apparently comes form the thinkpad_acpi kernel module. It seems, that the MicMute-key press/release isn't registered at all, as I couldn't successfully detect an acpi key 'event'. This is for notification, mainly, but thanks for any activity to repair that behaviour. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-extra-3.11.0-17-generic 3.11.0-17.31 [modified: lib/modules/3.11.0-17-generic/kernel/drivers/net/usb/qmi_wwan.ko lib/modules/3.11.0-17-generic/kernel/drivers/usb/serial/option.ko] ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: me 3938 F pulseaudio /dev/snd/controlC0: me 3938 F pulseaudio Date: Thu Mar 6 13:35:53 2014 HibernationDevice: RESUME=UUID=1d10886c-db7f-450d-8dbb-96e685779dd1 InstallationDate: Installed on 2011-03-05 (1096 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) MachineType: LENOVO 4389W1B MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (138 days ago) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 4389W1B dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4389W1B dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288726 Title: MicMute key on lenovo w510 thinkpad doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222398] [NEW] package linux-image-3.8.0-30-generic 3.8.0-30.44 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Just an update error that crept up. I hope I can deal with it. So this is just for (your) information. Otherwise I'll post a follow-up. Thanks. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Sep 8 14:20:32 2013 DuplicateSignature: package:linux-image-3.8.0-30-generic:3.8.0-30.44:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=1d10886c-db7f-450d-8dbb-96e685779dd1 InstallationDate: Installed on 2011-03-05 (917 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) MachineType: LENOVO 4389W1B MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 SourcePackage: linux Title: package linux-image-3.8.0-30-generic 3.8.0-30.44 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-04-26 (135 days ago) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 4389W1B dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4389W1B dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222398 Title: package linux-image-3.8.0-30-generic 3.8.0-30.44 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176042] [NEW] Make an E173s-1 [12d1:14d1] Huawei usb-UMTS-stick work properly
Public bug reported: Dear package-management, I would like to get a Huawei USB-UMTS-stick to work now and persistently in future releases and avoid a kernel stop/crash at the same time. My stick is a ProSieben (delivery company), Vodafone (UMTS-, IP- provider, websession-connection) from Huawei (manufacturer) with the label E173s (E173s-1 on closer inspection) on it and with the USB-ids 12d1:14d1 before and 12d1:14c9 after the usb-modeswitch command. The impact is most likely a broader one, at least for the Huawei family, as its solution needs all the changes made for the E173 within the kernel (modules: option.ko (in usb/serial) and qmi_wwan.ko (in net/usb)) not to long ago and additional ones in modemmanager. With the modifcations described, my stick runs, so bear with me, when I get a little more detailed at the start. With a 'bare bones' raring ringtail-Ubuntu, when you plug the stick in, it will after a little while (about 2 minutes) crash Ubuntu in such a way, that only a hard switch-off of the device will help. The reason is, that USB-port 1 (numbering starts with 0) will get a USB tty device (/dev/ttyUSB3 in my case), and as soon as option.ko and following that usb_wwan.ko tries to operate that device, its queue will fill up and finally hang the kernel. For my stick, after the usb-modeswitch the (USB-)ports are labeled (GETPORTS-lookup- with SETPORT?-arrangement- command): (USB-0) NDIS, (USB-1) 7, (USB-2) PCSC, (USB-3) DIAG. Here 7 means the MS-Windows-7 NDIS mode, and an MDM label is missing, but NDIS takes its role. When option gets hold, it will in sequence name the USB-ports USB-0 /dev/ttyUSB0, USB-2 /dev/ttyUSB1, USB-3 /dev/ttyUSB2 and when it gets the chance USB-1 /dev/ttyUSB3, which will then run havoc (see above). So in the first place, by introducing the same blacklisting as exists now for E173 in option.ko for this stick - i.e. blacklisting (net_intf1_blacklist) interface-1 - and adding an entry in qmi_wwan.ko for it just like for E173, a device /dev/ttyUSB3 won't be generated. From that moment on, there will be no more kernel stop/crash. But it still doesn't work! This is where modemmanager comes into play: Because there is no MDM-entry, it will assign /dev/ttyUSB0 (ok!) and /dev/ttyUSB2 (no so good!) as modem devices. Now when it comes to connecting to the net it will link /dev/ttyUSB2 to the starting pppd (/dev/ttyUSB2 - pppd), which will not succeed! It should have been /dev/ttyUSB0! So NDIS' is the port to choose, here, instead of the missing modem. When you add NDIS in addition to MDM - as has been done in a PPA for quantal [modemmanager_0.6.0.0.really- 0ubuntu2~fix.lp1057186ubuntu1+168~quantal1(_i386.deb)] - /dev/ttyUSB0 and /dev/ttyUSB2 will again be claimed for 'modem' by modemmanager, but during the connection-phase /dev/ttyUSB0 (=USB-port 0) will be used and pppd succeeds. For this, just the source-code for libmm-plugin- huawei.so has to be adapted. The problem isn't really new for raring, but happened in midtime of quantal, when the E173-kernel-changes were introduced. But in quantal there were older kernels, that still worked, and the PPA- modemmanager-version. Now for raring, no kernel works, and modemmanager is also newer - and I have seen no adaptation for it, yet. So may be it's time to fix this thing once and for all. My assumption is, that there are (many) more - at least Huawei - devices affected by that queue-phenomenon, not just mine [12d1:14d1 - 14c9]. Should I have been unclear, should you need any additional information or have a question, just contact me. I'll do what I can to fix this thing. By the way, can you arrange for the necessary kernel-fixes to be made, too? You certainly have a better connection than me to the people responsible. That would be nice. Thanks for the help! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: modemmanager 0.6.0.0.really-0ubuntu5 [modified: usr/lib/ModemManager/libmm-plugin-huawei.so] ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri May 3 15:31:06 2013 InstallationDate: Installed on 2011-03-05 (789 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) MarkForUpload: True SourcePackage: modemmanager UpgradeStatus: Upgraded to raring on 2013-04-26 (7 days ago) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176042 Title: Make an E173s-1 [12d1:14d1] Huawei usb-UMTS-stick work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1176042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074418] Re: qemu:///sessions fail, when libvirtd hasn't been started properly before
Hello Brian, I did test your patch in a i386 environment with version 0.9.13-0ubuntu12.1 of libvirt0, libvirt-bin, libvirt-dev, libvirt-doc, and python-libvirt - it ran fine! Thank you very much! [I didn't install 'libvirt0-dbg'.] Thanks for the quick reaction-time, too! Best wishes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074418 Title: qemu:///sessions fail, when libvirtd hasn't been started properly before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1074418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074418] Re: qemu:///sessions fail, when libvirtd hasn't been started properly before
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074418 Title: qemu:///sessions fail, when libvirtd hasn't been started properly before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1074418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074418] [NEW] qemu:///sessions fail, when libvirtd hasn't been started properly before
Public bug reported: Starting with 12.10 the libvirt communications mechanism uses the XDG_RUNTIME_DIR environment variable to determine the directory to put in its pipe(s) and controlling files - this normally being /run/usr/$USER. Now when you run a qemu user(!) session (qemu:///session) an a 'libvirtd'-process owned by the user hasn't already be spawned - e.g. manually - libvirt0 will spawn one itself. When manually spawned from a terminal window, XDG_RUNTIME_DIR is properly set up and everything works well with libvirtd. When libvirt0 spawns the libvirtd, it will use $HOME/.cache/libvirt/qemu/run, the previous (up to and including 12.04) location for this, because this is seems to be its fallback-default. Thus when you start such a session with virsh -c qemu:///session or vitual-manager, respectively, it will fail, saying error: Failed to connect socket to '/run/user/me/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor in the former case. Either XDG_RUNTIME_DIR is not properly set when libvirt spawns libvirtd, or it is not respected. My assumption is the former, as XDG_RUNTIME_DIR seems to be set by some 'pam'-module, that probably isn't used when libvirt exececutes libvirtd. As a workaround one can set XDG_RUNTIME_DIR=.cache in the environment calling virsh or virtual-manager, the everything uses the old/former settings and works. The problem seems to be to tell libvirt about the proper XDG_RUNTIME_DIR contents or make it the new default. The way it is now, qemu-user-sessions will just fail when started by virsh or virt-manager. By the way, you can test it even with a 'live'-system (USB/DVD) by just adding the libvirt-bin and/or virt-manager packages, thus it is not dependent on the version of the packages installed on the actual system. Nevertheless as I can't see if that information is attached otherwise, here are the system data you require: Description:Ubuntu 12.10 Release:12.10 libvirt0: Installed: 0.9.13-0ubuntu12 Candidate: 0.9.13-0ubuntu12 Version table: *** 0.9.13-0ubuntu12 0 500 http://de.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status Best regards. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libvirt0 0.9.13-0ubuntu12 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Nov 2 17:13:51 2012 InstallationDate: Installed on 2011-03-05 (608 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) MarkForUpload: True SourcePackage: libvirt UpgradeStatus: Upgraded to quantal on 2012-10-26 (6 days ago) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074418 Title: qemu:///sessions fail, when libvirtd hasn't been started properly before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1074418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074418] Re: qemu:///sessions fail, when libvirtd hasn't been started properly before
** Description changed: Starting with 12.10 the libvirt communications mechanism uses the XDG_RUNTIME_DIR environment variable to determine the directory to put in its pipe(s) and controlling files - this normally being - /run/usr/$USER. + /run/user/$USER/libvirt. - Now when you run a qemu user(!) session (qemu:///session) an a + Now when you run a qemu user(!) session (qemu:///session) and a 'libvirtd'-process owned by the user hasn't already be spawned - e.g. manually - libvirt0 will spawn one itself. When manually spawned from a - terminal window, XDG_RUNTIME_DIR is properly set up and everything - works well with libvirtd. When libvirt0 spawns the libvirtd, it will use - $HOME/.cache/libvirt/qemu/run, the previous (up to and including 12.04) - location for this, because this is seems to be its fallback-default. + terminal window, XDG_RUNTIME_DIR is properly set up to + /run/user/$USER and everything works well with libvirtd. When libvirt0 + spawns the libvirtd, it will use $HOME/.cache/libvirt, the previous (up + to and including 12.04) location for this, because this seems to be its + fallback-default. Thus when you start such a session with virsh -c qemu:///session or vitual-manager, respectively, it will fail, saying - error: Failed to connect socket to '/run/user/me/libvirt/libvirt-sock': No such file or directory + error: Failed to connect socket to '/run/user/$USER/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor in the former case. Either XDG_RUNTIME_DIR is not properly set when libvirt spawns libvirtd, or it is not respected. My assumption is the former, as XDG_RUNTIME_DIR seems to be set by some 'pam'-module, that probably isn't used when libvirt exececutes libvirtd. As a workaround one can set XDG_RUNTIME_DIR=.cache in the environment calling virsh or virtual-manager, the everything uses the old/former settings and works. The problem seems to be to tell libvirt about the proper XDG_RUNTIME_DIR contents or make it the new default. The way it is now, qemu-user-sessions will just fail when started by virsh or virt-manager. By the way, you can test it even with a 'live'-system (USB/DVD) by just adding the libvirt-bin and/or virt-manager packages, thus it is not dependent on the version of the packages installed on the actual system. Nevertheless as I can't see if that information is attached otherwise, here are the system data you require: Description: Ubuntu 12.10 Release: 12.10 libvirt0: - Installed: 0.9.13-0ubuntu12 - Candidate: 0.9.13-0ubuntu12 - Version table: - *** 0.9.13-0ubuntu12 0 - 500 http://de.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 0.9.13-0ubuntu12 + Candidate: 0.9.13-0ubuntu12 + Version table: + *** 0.9.13-0ubuntu12 0 + 500 http://de.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages + 100 /var/lib/dpkg/status Best regards. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libvirt0 0.9.13-0ubuntu12 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Nov 2 17:13:51 2012 InstallationDate: Installed on 2011-03-05 (608 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) MarkForUpload: True SourcePackage: libvirt UpgradeStatus: Upgraded to quantal on 2012-10-26 (6 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074418 Title: qemu:///sessions fail, when libvirtd hasn't been started properly before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1074418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992034] [NEW] package gxine 0.5.905-4ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139
Public bug reported: Two step upgrade from 11.04 to 11.10 (fine as far as gxine is concerned) and then 11.10 to 12.04, which triggered the error. The update was done by 'update-manager' each time. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: gxine 0.5.905-4ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Mon Apr 30 17:09:48 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) SourcePackage: gxine Title: package gxine 0.5.905-4ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to precise on 2012-04-30 (0 days ago) ** Affects: gxine (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992034 Title: package gxine 0.5.905-4ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gxine/+bug/992034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992034] Re: package gxine 0.5.905-4ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992034 Title: package gxine 0.5.905-4ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gxine/+bug/992034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788632] [NEW] package xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139
Public bug reported: Binary package hint: xine-ui Just a normal 'dist-upgrade' (10.10 - 11.04), nothing fancy. Somehow xine-ui didn't like it :-). ProblemType: Package DistroRelease: Ubuntu 11.04 Package: xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11 Uname: Linux 2.6.35-27-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu May 26 15:16:16 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007.1) SourcePackage: xine-ui Title: package xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to natty on 2011-05-26 (0 days ago) ** Affects: xine-ui (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788632 Title: package xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] failed to install/upgrade: ErrorMessage: subprocess installed post- installation script returned error exit status 139 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788632] Re: package xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788632 Title: package xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] failed to install/upgrade: ErrorMessage: subprocess installed post- installation script returned error exit status 139 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 576429] Re: wait-for-root has problems with mknod generated root-devices
Hello, On Nov 27, Evan Broder wrote: Thanks for the great bug report. Your description of the problem made it really simple to track down the misbehavior. you're welcome and ... [Description of possible solution.] .. your patch/fix seems to work! I've pushed a patch to lp:~broder/ubuntu/natty/initramfs- tools/fix-576429, but before I ask for sponsorship, I'd like to get some verification that it works as desired. I've uploaded versions of initramfs-tools with this patch for lucid, maverick, and natty to my PPA (https://launchpad.net/~broder/+archive /ubuntu-tests). Could you please test whichever version is most convenient and let me know if the patch works? I've installed the 'maverick' (10.10) version of the two packages (...tools and ...tools-bin) and removed the 'rootdelay' setting in lilo.conf. It worked flawlessly (and fast) for me! Thanks for caring. Best regards, Ruediger Oberhage -- wait-for-root has problems with mknod generated root-devices https://bugs.launchpad.net/bugs/576429 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 576429] [NEW] wait-for-root has problems with mknod generated root-devices
Public bug reported: Binary package hint: initramfs-tools Hello! There's a long startup delay (until 'rootdelay' has passwd), when a (root-)device is set up in the /dev-tree only. This is (e.g.) the case, when the machine is started by 'lilo' and the root-device given as device numbers like 0806 or whatever. 'parse_numeric' from scripts/functions then 'mknod's a /dev/root device with the respective major and minor numbers. When /dev/root is then passed to 'wait-for-root' this times out, probably because there is no counterpart in sysfs or procfs and thus the udev 'database'. So it always times out, before the boot process continues. It doesn't happen, when the same(!) computer is booted by GRUB with a reference to /dev/sda6 (or so). This behaviour is new with 'lucid' ( - as is wait-for-root) and it is a real nuissance. if something can be done, other than setting a shorter 'rootdelay', this should be fixed, please. Thanks. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: initramfs-tools-bin 0.92bubuntu78 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Thu May 6 16:10:44 2010 LiveMediaBuild: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- wait-for-root has problems with mknod generated root-devices https://bugs.launchpad.net/bugs/576429 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 576429] Re: wait-for-root has problems with mknod generated root-devices
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47935176/Dependencies.txt -- wait-for-root has problems with mknod generated root-devices https://bugs.launchpad.net/bugs/576429 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 478392] Re: /tmp is not cleaned when on a separate partition
Comming back to the 'merged' bug #470797: Can't you just 'mimic' the Sys-V-init behaviour in upstart. That seemed to work satisfactorily. Package 'initscripts' installed a shell-script mountall-bootclean.sh which started some helper (also a shell-script, iirc) that did the actual job. It's all still there in 'jaunty'. There surely is a way to just incorporate that (the helper shell-script) into upstart, at least as a starting point. -- /tmp is not cleaned when on a separate partition https://bugs.launchpad.net/bugs/478392 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 470797] Re: /tmp isn't cleaned up on boot/startup any longer
SInce you asked for it, here is my /etc/fstab. Fairly common I'd guess. The only thing is that I'm dedicating a harddisk partition to /tmp. ** Attachment added: /etc/fstab with /tmp as a separate partition http://launchpadlibrarian.net/35469662/fstab -- /tmp isn't cleaned up on boot/startup any longer https://bugs.launchpad.net/bugs/470797 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 470797] [NEW] /tmp isn't cleaned up on boot/startup any longer
Public bug reported: Binary package hint: sysvinit After upgrading from 9.04 (jaunty) to 9.10 (karmic), /tmp isn't cleaned up any longer when booting. This used to be done with a script mountall-bootclean.sh and its helpers coming from package 'initscripts'. Now it is missing there, but it also isn't done by the new 'startup' package. Maybe this has to do with me upgrading to instead of installing 9.10, but probably not! I see no script with the intention to clean up/empty /tmp any longer. Thus /tmp is cluttering up now. Please re-integrate the clearing of /tmp again. Thanks. ProblemType: Bug Architecture: i386 Date: Mon Nov 2 14:55:48 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: initscripts 2.87dsf-4ubuntu11 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: sysvinit Uname: Linux 2.6.31-14-generic i686 ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- /tmp isn't cleaned up on boot/startup any longer https://bugs.launchpad.net/bugs/470797 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 470797] Re: /tmp isn't cleaned up on boot/startup any longer
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34955411/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/34955412/XsessionErrors.txt -- /tmp isn't cleaned up on boot/startup any longer https://bugs.launchpad.net/bugs/470797 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 323121] [NEW] package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade: package rhythmbox is already installed and configured
Public bug reported: I'm not sure that it is a probelm of rhythmbox and would assume it isn't. It is a problem of upgrading an intrepid system on proposed status today (Jan 30, 2009) with a lot of programs, specially (lib-)xine ones, gxine and some libgtk2. It threw an dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4' failed., which is the culprit one, as I assume, not rythmbox. The latter might just be the trigger when trying to recover with 'aptitude'. I'm now trying to recover by downgrading or purging packages. Thanks. ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: package rhythmbox is already installed and configured NonfreeKernelModules: nvidia Package: rhythmbox 0.11.6svn20081008-0ubuntu4.3 SourcePackage: rhythmbox Title: package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade: package rhythmbox is already installed and configured Uname: Linux 2.6.27-11-generic i686 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-package -- package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade: package rhythmbox is already installed and configured https://bugs.launchpad.net/bugs/323121 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 323121] Re: package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade: package rhythmbox is already installed and configured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/21800285/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/21800286/DpkgTerminalLog.txt -- package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade: package rhythmbox is already installed and configured https://bugs.launchpad.net/bugs/323121 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 290874] Re: /etc/init.d/opencryptoki stop does not stop pkcsslotd
On Dec 01, Chris Coulson wrote: Hang on, I'm wrong! I shouldn't have just skimmed through your post before replying ;) I did hang on :-). Ok, so what you're saying is that the stop action failed during the upgrade because the daemon had failed to start earlier for some other reason. Missing the --oknodo option from start-stop-daemon would cause this, and you should probably open another bug report for that as the stop action should always exit gracefully if the daemon is not running (that issue is separate from this bug). Quite right. The remark /etc/init.d/opencryptoki stop does not stop pkcsslotd is correct, but only since pkcsslotd didn't run in the first place, somehow dying after the '/etc/init.d/opencryptoki start' at startup. And (only) because of the missing --oknodo in the 'previous(!)' /etc/init.d/opencryptoki this lets the upgrade go wrong! Thanks for spotting that. You're welcome. But: should I really open a separate bug report because of the then(!) missing --oknodo? It is included in the actual version of the startup- script, so it has already been spottet and fixed by someone, probably even you. It used to be wrong, but isn't any longer. The problem 'just' is, how to get rid of that bad version for people, like me, with that script a n d where the daemon didn't stay around, as the error then prevents the upgrade. Otherwise, i.e. with a working daemon, the upgrade most likely succeeds. Other than that, can you verify that the Intrepid fix for this original bug works, by running the test case above? Which test case do you mean, exactly? I can tell that with the new /etc/init.d/opencryptoki, a stop doesn't lead to an error, even when the pkcsslotd doesn't run, but prints Stopping PKCS#11 slot daemon: pkcsslotd. as it would, when actually terminating the pkcsslotd. Better yet, starting the machine or giving a /etc/init.d/opencryptoki start actually makes and keeps pkcsslotd running after the upgrade now - at least for me. Is that, what you wanted to know? For me to test if an upgrade would succeed from the 'bad' version, I would have to re-install that. But I doubt that anything would change, it would still go wrong, as the stop would produce the error in the startup-script again. But when you tell me, I'll try to restore that/an old version and see if the upgrade works. Best regards, Ruediger -- /etc/init.d/opencryptoki stop does not stop pkcsslotd https://bugs.launchpad.net/bugs/290874 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 290874] Re: /etc/init.d/opencryptoki stop does not stop pkcsslotd
Dear Chris Coulson,
On Nov 29, Chris Coulson wrote:
I'm not sure which workaround you refer to, as you linked to this bug
report. Can you describe the problem that you are still experiencing and
describe the steps to recreate it (ie, does it happen during package
install, or an upgrade? If it was an upgrade, was it just a normal
update or were you upgrading from an earlier Ubuntu release?)
the notebook in question has been upgraded from 8.04 to 8.10, but at an
earlier stage, without a problem with respect to 'opencryptoki'.
This error occured from a '-proposed' upgrade with 8.10 (intrepid) itself.
I did find a solution for me, but it won't work for everyone, I assume,
as it required manual intervention.
The problem arose from the (old) init-script '/etc/init.d/opencryptoki'
giving a non-zero return value on 'stop' due to the fact that the 'start'
didn't successfully start the 'pkcsslotd'. Thus dpkg received an error
(from the 'stop') when trying to remove/upgrade the package, which went
up to the upgrade-manager.
My 'solution' was to put an 'exit 0' in the 'stop' branch before the
call to stop the daemon. This way the upgrade was done and I was only
asked if I wanted to actually replace /etc/init.d/opencryptoki (or
keep the old version), where I answered to install the new init-script
to. From then on, I had no problems any longer.
I think I do see the '--oknodo'-option in the 'stop'-case not present in
the older script. The problem is, that the old script won't be successfully
executed as long as it isn't swapped for the new one, thus aborting the
upgrade(s). When you've got more than one (error-)message for that problem
from me, it's from my trials do make the upgrade succeed; but it's actually
a 'one-time' event.
I'm fine the way it is, now. But I do think you might have to help other
people with the same problem.
Thanks for caring and for the fine software,
Ruediger Oberhage
--
Dr. H.-R. Oberhage
Mail: Univ. Duisburg-Essen E-Mail: [EMAIL PROTECTED]
Fachbereich Physik[EMAIL PROTECTED]
Campus Duisburg, MG 464
Lotharstrasse 1 Phone: {+49|0} 203 / 379-4736
47057 Duisburg, Germany FAX:{+49|0} 203 / 379-4732
--
/etc/init.d/opencryptoki stop does not stop pkcsslotd
https://bugs.launchpad.net/bugs/290874
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 130696] Re: xine and totem-xine crashes with the fglrx driver
I'd like to add to my remarks dated 2007-10-23, that I've now found the config file for 'totem' alias Movie Player under gnome. Activating the 'video.driver' entry and setting it to xshm in ~/.gnome2/Totem/xine_config now allows me to use totem like it used to be in version 7.04 alias feisty - and quite similar to 'xine' after adjusting its file. It still is a kludge/workaround/'patch' at best and does not solve the basic problem described. -- xine and totem-xine crashes with the fglrx driver https://bugs.launchpad.net/bugs/130696 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130696] Re: xine and totem-xine crashes with the fglrx driver
I'd like to an observation and a (maybe) workaround for some. The observation is, that for me, before calling totem for the first time, runs without an error, but (already) returns no values for the attribute starting with XV_BLENDING_MODE in the 'client gettable attribute' entry. After launching totem, experiencing the same problem as formerly describe, xvinfo now fails, too ecactly at the XV_BLENDING_MODE entry. The possible workaround with xine: When I edit 'video.driver' entry in the ~/.xine/config - file and set this to xshm, xine does run without problem for me. 'totem' still does not! And I've found no file or way to have 'totem' act like 'xine'. -- xine and totem-xine crashes with the fglrx driver https://bugs.launchpad.net/bugs/130696 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130696] Re: xine and totem-xine crashes with the fglrx driver
Sorry about too many typos in my above posting. To make it more understandable: I'd like to add an observation ... It should read: ... first time, xvinfo runs without an error ... and: ...xvinfo now fails, too, exactly at ... -- xine and totem-xine crashes with the fglrx driver https://bugs.launchpad.net/bugs/130696 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
