[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Vivid) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1600124 Title: Adjust KBL PCI-ID's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in libdrm source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in xserver-xorg-video-intel source package in Xenial: New Bug description: Current list of KBL PCI-ID's is incomplete, there are a few that are should not be listed and few that are missing. To fix this, adjust the list in kernel/libdrm/mesa/ddx to match upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550090] Re: linux-image-3.19.0-51-generic fails to boot to desktop under VMWare Player
*** This bug is a duplicate of bug 1548587 *** https://bugs.launchpad.net/bugs/1548587 ** This bug has been marked a duplicate of bug 1548587 Ubuntu 14.04/15.10 VMWare guest won't show UI after upgrading to 4.2.0-30.35 or 3.19.0-51.57 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1550090 Title: linux-image-3.19.0-51-generic fails to boot to desktop under VMWare Player Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After updating my VMWare Player install of Ubuntu 14.04 amd64 to linux-image-3.19.0-51-generic it fails to boot - plymouth appears to hang during boot and so it never reaches the GDM login screen - also seems I am not alone: http://askubuntu.com/questions/738083/ubuntu-14-04-4-lts-hangs-on-boot-after-latest-dist-upgrade-in-vmware http://ubuntuforums.org/showthread.php?t=2314723 Booting from the previous kernel 3.19.0-49-generic works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1550090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
