[Bug 1959047] [NEW] systemd ignores RootDirectory option in .service units
Public bug reported: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu Jan 25 20:40:40 dolly lsb_release[362]: Description:Ubuntu 14.04 LTS Jan 25 20:40:40 dolly lsb_release[362]: Release:14.04 Jan 25 20:40:40 dolly lsb_release[362]: Codename:trusty Jan 25 20:40:40 dolly systemd[1]: lsb-release.service: Succeeded. On the problematic system, however, I get the following result. Jan 25 21:21:08 savelog systemd[1]: Starting LSB Release Information... Jan 25 21:21:08 savelog systemd[1]: Started LSB Release Information. Jan 25 21:21:08 savelog pwd[81114]: / Jan 25 21:21:08 savelog lsb_release[81115]: No LSB modules are available. Jan 25 21:21:08 savelog lsb_release[81115]: Distributor ID:Ubuntu Jan 25 21:21:08 savelog lsb_release[81115]: Description:Ubuntu Jammy Jellyfish (development branch) Jan 25 21:21:08 savelog lsb_release[81115]: Release:22.04 Jan 25 21:21:08 savelog lsb_release[81115]: Codename:jammy Jan 25 21:21:08 savelog systemd[1]: lsb-release.service: Deactivated successfully. It totally run the service on the host's root filesystem, it didn't care even the slightest that a RootDirectory is specified. Tested on the following releases / systemd versions: Ubuntu 18.04.6 Bionic Beaver – ISSUE NOT PRESENT systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Ubuntu 20.04.3 Focal Fossa – ISSUE NOT PRESENT systemd 245 (245.4-4ubuntu3.15) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Ubuntu 21.10 Impish Indri – ISSUE NOT PRESENT systemd 248 (248.3-1ubuntu8.2) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Ubuntu 22.04 Jammy Jellyfish (development branch) – ISSUE PRESENT systemd 249 (249.5-2ubuntu4) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Note that the problem is produced under an LXC container; since systemd detects virtualization, it might change how it behaves. It's either a bug or an intentional change I don't understand yet (i.e. the RootDirectory option has deprecated and is about to be replaced with something else, or there are additional conditions to be met before RootDirectory is considered), but I think in the latter case I should at least get a warning that there is a change in configuration. I imagine suddenly everyone's existing service units utilizing RootDirectory silently stop working without any information regarding why. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913240] Re: do-release-upgrade ignores APT proxy exemption
Posted a 10 USD bounty on this issue: https://www.bountysource.com/issues/96530138-do-release-upgrade-ignores-apt-proxy-exemption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913240 Title: do-release-upgrade ignores APT proxy exemption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1913240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913240] [NEW] do-release-upgrade ignores APT proxy exemption
Public bug reported:
When I try to check for an upgrade, this is what happens:
# do-release-upgrade -c
Checking for a new Ubuntu release
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your
Internet connection or proxy settings
There is no development version of an LTS available.
To upgrade to the latest non-LTS develoment release
set Prompt=normal in /etc/update-manager/release-upgrades.
With tcpdump, I discovered that do-release-upgrade tries to connect the
configured APT-Cacher-NG proxy. The proxy only listens on plaintext HTTP
(TCP:80), while the script tries to connect it on HTTPS (TCP:443),
because it wants to download meta-release-lts through an https:// URL.
Since I have no intention to configure SSL certificates on the proxy for
the sole reason to enable upgraders to operate, I thought I'd rather
exempt it from the APT proxy setting.
Currently, I have this APT proxy configuration under
/etc/apt/apt.conf.d:
Acquire::http {
Proxy::changelogs.ubuntu.com "DIRECT";
Proxy "http://taranis.lan";;
};
Acquire::https {
Proxy::changelogs.ubuntu.com "DIRECT";
};
I added an explicit section for https too, just in case. According to
man apt-transport-http, the syntax should be correct and `apt-config
dump` reports that it correctly parsed the config file and understands
that it needs to exempt changelogs.ubuntu.com.
Acquire::http::Proxy "http://taranis.lan";;
Acquire::http::Proxy::changelogs.ubuntu.com "DIRECT";
Acquire::https::Proxy "";
Acquire::https::Proxy::changelogs.ubuntu.com "DIRECT";
However, trying `do-release-upgrade -c` has the same result, the
upgrader still wants to get the meta-release file via the proxy. It is a
strange situation, because it seems `do-release-upgrade` wants to honour
the APT proxy configuration, but it ignores the exemptions. In my case,
it would be better to ignore the proxy altogether.
I have this proxy for quite a while and the server was configured to use
it, and I don't remember encountering this issue on any previous release
upgrade, but I haven't run one since 2018. I guess the feature of
honouring the APT proxy config was added recently in the last 2 years. I
have this issue on my Bionic server, and I reproduced it on a pristine
Focal VM installation as well.
I think the intended or desirable behaviour would be to adhere to the
APT proxy configuration in its entirety, including the exemptions.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic dist-upgrade focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913240
Title:
do-release-upgrade ignores APT proxy exemption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1913240/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Sorry, I didn't actually test Focal and Groovy. Xenial will be supported for about a year, so I think it worth to fix it there as well; however it's relative what worth to fix and what not, as most users probably left Xenial behind already or applied a workaround if they were ever affected by this issue. On the other hand it can be a real pain if you don't know about this and just happen to convert your root LV to raid1 and then your system doesn't boot. "The supported configuration for raid1 is mdadm after all, not removing mdadm and the meta packages that depend on it and using lvm's raid support." I don't know where LVM over DM-RAID is defined as the "supported configuration" as opposed to RAID1 over LVM. I always thought about them as equal alternatives for slightly different use cases. My rule of thumb is when you can afford to get identical sized disks and mirror everything, go with LVM over DM-RAID. If you can't guarantee to have identical sized disks and need a more dynamic solution, then RAID1 over LVM (i.e. using LVM's raid1 support) is more suitable. I recommend the former in productive server environments and the latter in smaller SOHO, home servers and personal computers. If one of my disks goes bye-bye, I wouldn't want to reinstall my system or lose my documents, so I have my / and /home LVs in raid1. However I couldn't care less about my Steam library because I can just re-download the games anytime, so I don't have it mirrored, as I'd rather not want it to use twice the precious disk space. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Hi Steve, Julian, Łukasz, everyone, Sorry that I didn't test the package on time – my life circumstances have significantly changed since I reported this bug, nowadays I don't have enough free time to do as much testing as I did back in the day. I've been using the workaround ever since then, returning to this now after more than 4 years really feels nostalgic. I still had my test VM from 2016, upgraded it up to Eoan and confirmed the problem was present there as well. Then I installed the new lvm2 package which just got into -updates and indeed it fixed the issue. I know this finding is not so useful after Julian has already tested, but I wanted to see. Since this problem was present from Wily and been around in all Ubuntu releases onwards, are you going to port this fix to all currently supported releases? While it's fixed for Bionic and Eoan; Xenial, Focal, and the actual development version (Groovy) are still affected. Now that I caught up on this again, do you want me to verify the problem in all the remaining releases? Anyway, thanks everyone who contributed to fixing this! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
Thanks for the fix, it solved my issue too! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798840] Re: Night Light is not functioning
Guys, with today's reboot Night Light works with Wayland. Now I see a fix for Mutter has been released for #1847551 that I installed on Nov 21 but didn't reboot until today. Indeed it was not an issue with Wayland, sorry for reporting it as such. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798840 Title: Night Light is not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798840] Re: Night Light is not functioning
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798840 Title: Night Light is not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798840] Re: Night Light is not functioning
Now I found out that it depends on whether I login with Xorg or Wayland. Night Light works with Xorg, but doesn't with Wayland. I honestly don't remember whether I was running Disco with Xorg or Wayland, most probably I just went with the default. My guess is that Disco used Xorg by default and Eoan changed to Wayland, that's why I thought it's broken with the upgrade. ** Also affects: wayland (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/1798840 Title: Night Light is not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798840] Re: Night Light is not functioning
Night light stopped working for me from Disco to Eoan upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798840 Title: Night Light is not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
It works, thanks! \o/ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
# LANG=C apt-cache policy libnvidia-gl-390 libnvidia-gl-390: Installed: 390.48-0ubuntu3 Candidate: 390.48-0ubuntu3 Version table: *** 390.48-0ubuntu3 500 500 http://hu.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 100 /var/lib/dpkg/status # LANG=C dpkg -l libnvidia-gl-390 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===--- ii libnvidia-gl-390:amd64 390.48-0ubuntu3 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
I'm not using oibaf. I used to use it, but uninstalled it with ppa-purge, but this problem is present regardless of oibaf is installed. ** Changed in: mesa (Ubuntu) Status: Invalid => New ** Changed in: xorg-server (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
How can I switch to Wayland? Contrary to the articles those tell otherwise, I have no option to select it on the login screen. Anyway, 17.10 worked fine with Wayland, so switching back to Wayland might probably help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
** Also affects: xorg-server (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/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
** Attachment added: "Xorg log from ~/.local/share/xorg/" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141626/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
I don't know why, but apport attached wrong (outdate) Xorg logs to my report. Probably it's a gdm feature that it puts logs elsewhere instead of the usual /var/log/Xorg.0.log. The actual logs made by my X11 server are located here: /var/lib/gdm3/.local/share/xorg/Xorg.0.log /home/megabrutal/.local/share/xorg/Xorg.1.log I attach the correct logfiles. ** Attachment added: "Xorg log from /var/lib/gdm3/.local/share/xorg/" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141625/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
** Attachment added: "thinkpad-glxinfo-normalboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141597/+files/thinkpad-glxinfo-normalboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
I've made a live bootable pendrive to test the issue. I've found that it's not present when I boot a live OS, so something must have gone wrong during the upgrade. I've attached glxinfo outputs. thinkpad-glxinfo-livecd.txt: How it looks like when I boot from USB drive. It's normal. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset OpenGL version string: 2.1 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.20 thinkpad-glxinfo-normalboot.txt: How it looks like when I boot my usual system on the same hardware. Software rendering is enforced. OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits) OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 ** Attachment added: "thinkpad-glxinfo-livecd.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141596/+files/thinkpad-glxinfo-livecd.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
** Also affects: xorg (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/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770940] [NEW] Kexec reboot doesn't work on 18.04 non-EFI system
Public bug reported: Unclear whether to report it against kexec-tools or systemd. After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the following error message: Cannot find the ESP partition mount point. What's interesting is that strace shows that systemctl tries to find the EFI partition before it emits the error message, like it was expecting an EFI system. My laptop is not capable of EFI, and it wasn't a problem for previous Ubuntu releases – the „systemctl kexec” command worked fine before. Here is my systemd version: root@thinkpad:~# systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid And my kexec-tools version is 1:2.0.16-1ubuntu1. I attached an strace output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kexec-tools 1:2.0.16-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 13 12:48:25 2018 InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: kexec-tools UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "strace-kexec.log" https://bugs.launchpad.net/bugs/1770940/+attachment/5138678/+files/strace-kexec.log ** Also affects: systemd (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/1770940 Title: Kexec reboot doesn't work on 18.04 non-EFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1770940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770913] [NEW] Software rendering is forced after 18.04 upgrade
Public bug reported: After upgrading to Ubuntu 18.04, my desktop uses software rendering, no matter what I do. As far as I know, all necessary packages are installed. Formerly I had oibaf installed, but suspecting that this may cause the problem, I removed it with ppa-purge. It didn't help. First I noticed the problem when I tried to play HD videos. It was fine before the upgrade. My hardware is capable for 3D acceleration, as it worked on 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 13 06:13:09 2018 DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ Renderer: Software SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun May 13 06:01:23 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1770913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722418] Re: [Unity desktop] My applications became darker for unknown reason
** Description changed: My display freezed and I had to forcefully restart my laptop. Since then, my applications and some UI elements are rendered darker than usual for no apparent reason. Not all applications are affected. For example, Firefox, LibreOffice are not affected. GNOME Terminal, System Monitor, Calculator, GEdit are affected, however. System volume bar, system menus, file selection dialogs (regardless of which application they were opened from) are also darker. See the attached screenshot. It is well visible that my applications are rendered darker than other desktop components: the Unity taskbar and the global title bar are rendered with their normal brightness, while the applications are noticeably darker. The purple background of the GNOME Terminal is almost like black. What might be the reason and how could I fix it? I use Unity desktop on Ubuntu 17.04. + + Related AskUbuntu question: + https://askubuntu.com/questions/961762/unity-desktop-my-applications-became-darker-for-unknown-reason?noredirect=1#comment1537687_961762 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722418 Title: [Unity desktop] My applications became darker for unknown reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1722418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722418] [NEW] [Unity desktop] My applications became darker for unknown reason
Public bug reported: My display freezed and I had to forcefully restart my laptop. Since then, my applications and some UI elements are rendered darker than usual for no apparent reason. Not all applications are affected. For example, Firefox, LibreOffice are not affected. GNOME Terminal, System Monitor, Calculator, GEdit are affected, however. System volume bar, system menus, file selection dialogs (regardless of which application they were opened from) are also darker. See the attached screenshot. It is well visible that my applications are rendered darker than other desktop components: the Unity taskbar and the global title bar are rendered with their normal brightness, while the applications are noticeably darker. The purple background of the GNOME Terminal is almost like black. What might be the reason and how could I fix it? I use Unity desktop on Ubuntu 17.04. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: gnome zesty ** Attachment added: "Képernyőkép – 2017-10-03 23-51-33.png" https://bugs.launchpad.net/bugs/1722418/+attachment/4966298/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202017-10-03%2023-51-33.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722418 Title: [Unity desktop] My applications became darker for unknown reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1722418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671753] [NEW] "NMI watchdog: BUG: soft lockup" and "page allocation stalls" errors
Public bug reported: My computer running Ubuntu Yakkety with 32 bit 4.8.0-41-generic kernel often locks up. Error messages like this appear in syslog: Mar 10 09:49:22 ReThinkCentre kernel: [47896.075600] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kswapd0:38] In later mainline kernels (4.10.0, or maybe even 4.9.0), the error message changes to this: Mar 4 22:07:04 ReThinkCentre kernel: [ 2815.183424] kthreadd: page allocation stalls for 11600ms, order:1, mode:0x17000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK) I believe the root cause is the same behind the two kinds of error messages, the latter being more specific. One kernel version never shows these messages mixed, they either log "NMI watchdog" or "page allocation stalls", there is no kernel version which logs both. With kernel bisection, I found that the following commit solves the problem in the mainline kernel: 71ab6cfe88dcf9f6e6a65eb85cf2bda20a257682 mm, vmscan: consider eligible zones in get_scan_count However, this patch doesn't easily apply to 4.8.0. I tried to backport it with git cherry-pick, but it run into conflicts. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-41-generic 4.8.0-41.44 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kutya 18471 F pulseaudio Date: Fri Mar 10 09:53:23 2017 HibernationDevice: RESUME=UUID=e0ebed7b-f012-4399-a6d9-584b8c64950b InstallationDate: Installed on 2014-08-16 (936 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP Compaq dc5800 Small Form Factor ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/centrevg-rootlv ro rootflags=subvol=@ rootdelay=300 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2017-01-22 (47 days ago) dmi.bios.date: 02/13/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.55 dmi.board.asset.tag: CZC8428PV6 dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8428PV6 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.55:bd02/13/2009:svnHewlett-Packard:pnHPCompaqdc5800SmallFormFactor:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc5800 Small Form Factor dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 kernel-fixed-upstream regression-release reverse-bisect-done yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671753 Title: "NMI watchdog: BUG: soft lockup" and "page allocation stalls" errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613758] Re: [RM] iscsitarget should be removed from Yakkety
OK, men, but then what is the replacement for iscsitarget? What should I replace my current configuration with? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613758 Title: [RM] iscsitarget should be removed from Yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1613758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643202] [NEW] Loading tab circle/wheel is now blue instead of Ubuntu orange
Public bug reported: I'm not sure whether I should report this, and whether is it an intentional change or not. I just installed an update for Firefox via apt. Now I have package version 50.0+build2-0ubuntu0.16.04.2. I noticed, when I open a tab and load a page, the little spinning circle (or wheel) which signs that the page is still loading, is now blue instead of Ubuntu orange. As far as I know, the orange colour of the loading wheel is a customization of Ubuntu, the original Firefox comes with a different colour (either blue or green, I rarely use vanilla Firefox), so I have a reason to think that this time, the package maintainers have forgot to add this part of the Ubuntu customization when they built the new Firefox package. On the other hand, if this change is intentional, so it is a deliberate decision to introduce it in the Ubuntu version of Firefox, that's fine. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of blue spinning wheel" https://bugs.launchpad.net/bugs/1643202/+attachment/4780119/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202016-11-19%2014-21-12.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643202 Title: Loading tab circle/wheel is now blue instead of Ubuntu orange To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621482] [NEW] Disconnect with ERRINFO_INVALID_INPUT_PDU_MOUSE (0x000010D0)
Public bug reported: I'm using FreeRDP to connect through an SCB (Shell Control Box) v4.1 to a Windows 2008 Server. When I connect to the server, FreeRDP immediately disconnects with the following error message: ERRINFO_INVALID_INPUT_PDU_MOUSE (0x10D0): (a) A Slow-Path Mouse Event (section 2.2.8.1.1.3.1.1.3) or Extended Mouse Event (section 2.2.8.1.1.3.1.1.4) has been received with an invalid pointerFlags field. (b) A Fast-Path Mouse Event (section 2.2.8.1.2.2.3) or Fast-Path Extended Mouse Event (section 2.2.8.1.2.2.4) has been received with an invalid pointerFlags field. Failed to check FreeRDP file descriptor Upon investigation, I found that it was a regression which was introduced in the FreeRDP source code in the past, and it has already been corrected in the upstream FreeRDP source code. Very old historical versions don't have this error and connect smoothly, while a build from the most-up-to-date Git repository also doesn't have this problem. With bisection, I found that the issue disappears after this merge commit: commit a83ccfd3658437cbff1d01c9cf61256afeebca7d Merge: b91c103 aa466a8 Author: Marc-Andr Moreau Date: Tue Apr 8 23:53:45 2014 -0400 Merge branch 'master' of github.com:FreeRDP/FreeRDP into smartcard Note that I couldn't get a more accurate result as many commits around this merge fail to compile, but this commit was the first one I found which compiles and works correctly. I also know that this commit fixes a build problem AND has the above PDU_MOUSE error: 7324ded7a26384817c8086f047c85a17fb9c6c2e. I kindly ask the package maintainer to backport commit a83ccfd3658437cbff1d01c9cf61256afeebca7d to the Xenial release of FreeRDP, or package a recent 2.0.0 build and release it into Xenial. ** Affects: freerdp (Ubuntu) Importance: Undecided Status: New ** Tags: bisect-done regression-release upgrade-software-version xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621482 Title: Disconnect with ERRINFO_INVALID_INPUT_PDU_MOUSE (0x10D0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1621482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574833] [NEW] setkey is not run automatically on system start
Public bug reported: The „setkey” service should run at system startup to add keys defined in /etc/ipsec-tools.conf. However, no keys are defined after system boot: root@ReThinkCentre:~# setkey -D No SAD entries. After inquiring systemd, I learn this: root@ReThinkCentre:~# systemctl status setkey ● setkey.service - LSB: option to manually manipulate the IPsec SA/SP database Loaded: loaded (/etc/init.d/setkey; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) ápr 25 21:15:28 ReThinkCentre systemd[1]: setkey.service: Job setkey.service/start deleted to break ordering cycle starting with sysinit.target/start Upon manually calling „systemctl start setkey” after the system booted up, the keys are added properly – but it is not feasible to do after each reboot. Moreover, I can't help to notice that /etc/init.d/setkey is a legacy SysV init script. No proper systemd service file seems to exist for setkey. I think it would be a great time to add one. ** Affects: ipsec-tools (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags added: wily xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574833 Title: setkey is not run automatically on system start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/1574833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540157] Re: Xenial: Mouse pointer disappears after release upgrade
** Also affects: ubuntu-release-upgrader (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/1540157 Title: Xenial: Mouse pointer disappears after release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1540157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540157] [NEW] Xenial: Mouse pointer disappears after release upgrade
Public bug reported: After release upgrade from Wily to Xenial, the mouse pointer is invisible. Reproduce: – Install Ubuntu Wily Werewolf desktop from the official Live CD. – Upgrade to Xenial Xerus with „do-release-upgrade -d”. Only had a chance to test it on KVM virtual machine, but it happened every time I upgraded a virtual machine to Xenial. Also, only tested via Wily -> Xenial upgrade, haven't tried Trusty -> Xenial. Nature Xenial install from the Xenial Live CD daily build right away doesn't have this issue, so I assume something goes wrong during the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20151218-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jan 31 22:45:19 2016 DistUpgraded: 2016-01-31 21:18:14,758 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2016-01-31 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic root=/dev/mapper/wvg-root ro Renderer: Software SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-01-31 (0 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-vivid dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-vivid dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Sun Jan 31 22:44:03 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 9 inputspice vdagent tablet TOUCHSCREEN, id 10 xserver.errors: systemd-logind: failed to get session: PID 700 does not belong to any known session AIGLX: reverting to software rendering qxl(0): EXECBUFFER failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual-0 Virtual-1 Virtual-2 Virtual-3 xserver.version: 2:1.17.3-2ubuntu2 xserver.video_driver: qxl ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1540157 Title: Xenial: Mouse pointer disappears after release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1540157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Thanks for the workaround! It seems adding raid1 is enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)
Same here:
$ ubuntu-support-status
Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 135, in
pkg.name, support_tag)
File "/usr/bin/ubuntu-support-status", line 51, in get_maintenance_status
raise Exception("No date tag found")
Exception: No date tag found
Line numbers are different, but I think it's the same error, because the
same exception is raised, and those line numbers don't differ too
much... I guess I have a different version of the script which still has
the reported bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503979
Title:
ubuntu-support-status throws exeption No date tag found (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1503979/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container
** Description changed: When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual development version) within an LXC container, the upgrade script hangs at the message „Calculating the changes”. Steps to reproduce: 1. Make an LXC container with Wily (quickest option is to use lxc-create -t download, choose ubuntu, wily, amd64/i386). - 2. Boot up the container, log in, „apt-get -y install ubuntu-release-upgrader”. + 2. Boot up the container, log in, „apt-get -y install ubuntu-release-upgrader-core”. 3. Start the upgrade with „do-release-upgrade -d”. You will see that the upgrade process will hang at the message „Calculating the changes”. The process which hangs: „/usr/bin/python3 /tmp/ubuntu-release-upgrader- 1mpotr5d/xenial --mode=server --frontend=DistUpgradeViewText --devel- release” With strace, it is revealed that the process hangs at a „futex” system call: futex(0x7f419c10, FUTEX_WAIT_PRIVATE, 0, NULL This system call never returns, the process must be interrupted with CTRL-C or kill. Upgrading to any previous release within an LXC container works without problems, therefore I consider it as a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511875 Title: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511875] [NEW] Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container
Public bug reported: When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual development version) within an LXC container, the upgrade script hangs at the message „Calculating the changes”. Steps to reproduce: 1. Make an LXC container with Wily (quickest option is to use lxc-create -t download, choose ubuntu, wily, amd64/i386). 2. Boot up the container, log in, „apt-get -y install ubuntu-release-upgrader”. 3. Start the upgrade with „do-release-upgrade -d”. You will see that the upgrade process will hang at the message „Calculating the changes”. The process which hangs: „/usr/bin/python3 /tmp/ubuntu-release-upgrader- 1mpotr5d/xenial --mode=server --frontend=DistUpgradeViewText --devel- release” With strace, it is revealed that the process hangs at a „futex” system call: futex(0x7f419c10, FUTEX_WAIT_PRIVATE, 0, NULL This system call never returns, the process must be interrupted with CTRL-C or kill. Upgrading to any previous release within an LXC container works without problems, therefore I consider it as a regression. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release wily xenial ** Also affects: lxc (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/1511875 Title: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Reproducible: upgraded another Ubuntu installation in VM and got the same result. Since the bug prevents booting, I suggest to increase priority to High. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Tags added: regression-release wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
I can't collect logs on non-booting system. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509717] [NEW] Wily LVM-RAID1 – md: personality for level 1 is not loaded
Public bug reported: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Also affects: initramfs-tools (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/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501529] [NEW] GnuCash crashes when I scroll over the account tabs in Wily Werewolf
Public bug reported: I have GnuCash 2.6.6 rev 132c9e3+ on 2015-08-12. When I have many tabs open (accounts and reports), so that they don't fit in the GnuCash windows horizontally, I used to scroll over the open accounts to select one that is not seen on the screen at the moment. The crash used to happen when I scroll to the left direction. At the moment of crash, the following error message appears on console: GLib- GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) ProblemType: RecoverableProblem DistroRelease: Ubuntu 15.10 Package: gnucash 1:2.6.6-2ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ActionNames: ActionPaths: /com/canonical/unity/gtk/window/5; Added: 1 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BusName: :1.83 CurrentDesktop: Unity Date: Thu Oct 1 00:08:34 2015 DuplicateSignature: /usr/bin/gnucash:GMenuModelItemsChangedInvalidIndex EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnucash InstallationDate: Installed on 2013-10-01 (728 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ItemCount: 1 LinkType: section MenuLabel: MenuName: MenuPath: /com/canonical/unity/gtk/window/5 ParentActionNames: ; ParentLinkType: sub menu ParentMenuLabel: ParentMenuName: Position: -1 ProcCmdline: gnucash /tmp/mnt/thinkhome/Dokumentumok/GnuCash/Folyószámla.gnucash Removed: 1 SourcePackage: gnucash UpgradeStatus: Upgraded to wily on 2015-05-13 (140 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-recoverableproblem wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501529 Title: GnuCash crashes when I scroll over the account tabs in Wily Werewolf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1501529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1074460] Re: kvm: windows xp installation hangs after "Setup is inspecting your computer's hardware configuration"
I experience this even today with Ubuntu Vivid. Anyone has a workaround (which not involves building QEMU/KVM from source)? My current qemu package version is 1:2.2+dfsg-5expubuntu9.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074460 Title: kvm: windows xp installation hangs after "Setup is inspecting your computer's hardware configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1074460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
I used the Trusty 14.04.0 Live CD for like half a day and didn't experience the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
To be honest, I don't remember. It appeared around the time when Utopic was released, but I don't know whether it was before or after the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
I experience the exact same problems with the most recent Vivid Vervet Live CD build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
** Attachment added: "Képernyőkép – 2014-12-06 15:04:50.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+attachment/4375901/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202014-12-06%2015%3A04%3A50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
** Attachment added: "Képernyőkép – 2015-04-15 07:39:27.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+attachment/4375900/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202015-04-15%2007%3A39%3A27.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444268] [NEW] [Lenovo ThinkPad T400] Screen corruption
Public bug reported: I often perceive massive screen corruption, most prominently in Firefox / GMail, but it may happen with any application, including terminals. Sometimes oversized letters appear. I run video stress tests, but they run without errors. I suspect the problem presents when many text needs to be rendered on-screen, as odd as it sounds. I will attach screenshots. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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 CurrentDesktop: Unity Date: Wed Apr 15 07:23:31 2015 DistUpgraded: 2014-11-11 12:36:03,224 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2014-06-10 (308 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-11 (154 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Apr 11 00:20:40 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16435 vendor LEN xserver.version: 2:1.16.0-1ubuntu1.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437536] Re: Screen corruption under KVM
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-driver-vesa/+bug/1437536/+attachment/4359299/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437536 Title: Screen corruption under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437536] Re: Screen corruption under KVM
** Summary changed: - Screen corruption under KVM with Spice display + Screen corruption under KVM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437536 Title: Screen corruption under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437536] Re: Screen corruption under KVM with Spice display
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-driver-vesa (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/1437536 Title: Screen corruption under KVM with Spice display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
The issue was fixed with `linux-image-3.16.0-33-generic`, as it finally contains commit f285f4a21c3253887caceed493089ece17579d59. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437536] [NEW] Screen corruption under KVM with Spice display
Public bug reported: I was experimenting with Ubuntu MATE, and I found severe screen corruption whenever I run the image under a KVM virtual machine. I attached a screenshot. I don't think the problem is Ubuntu MATE specific. I also found it doesn't depend on the display manager. (It can be either LightDM or GDM.) Reproduce instructions: 1. Boot up a KVM virtual machine with an Ubuntu Vivid Vervet image. 2. Put some stress on the display: what I used to do is to launch Firefox and htop in a terminal, then lock the screen, or let it lock by itself. 3. Wait a little, then unlock the computer. 4. You'll see letters missing and images corrupted, like on the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 Date: Sat Mar 28 02:04:36 2015 InstallationDate: Installed on 2015-03-27 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcEnviron: LANGUAGE=hu TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "UbuntuMATE-display-error.png" https://bugs.launchpad.net/bugs/1437536/+attachment/4358376/+files/UbuntuMATE-display-error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437536 Title: Screen corruption under KVM with Spice display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428952] Re: strings in UI incorrectly displayed with lots of spacing
This is another example of the display bug. ** Attachment added: "Screenshot_UbuntuMATE_2015-03-27_05:19:14.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428952/+attachment/4357560/+files/Screenshot_UbuntuMATE_2015-03-27_05%3A19%3A14.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428952 Title: strings in UI incorrectly displayed with lots of spacing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428952] Re: strings in UI incorrectly displayed with lots of spacing
This bug seems to be very prominent with beta versions of Vivid, recently I encountered it on a virtual machine during Ubuntu MATE installation. I'd suggest to triage it asap and increase its priority. ** Tags added: utopic vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428952 Title: strings in UI incorrectly displayed with lots of spacing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
@Astara: > Now, I've noticed when I am booting, it *does* take a bit of time to mount > bring up and mount all of the lvs, but you can the root mount is NOT > in an VG/LV -- It's on a "regular device" (numbers on left are w/kernel time > printing turned on -- so they are in seconds after boot): > > [ 4.207621] XFS (sdc1): Mounting V4 Filesystem > [ 4.278746] XFS (sdc1): Starting recovery (logdev: internal) > [ 4.370757] XFS (sdc1): Ending recovery (logdev: internal) > [ 4.379839] VFS: Mounted root (xfs filesystem) on device 8:33. If I understand you well, you have your root FS on a regular partition, thus you are not affected by this bug, as partitions don't need to be „activated”. You need to have your root FS on an LV to be affected. > if test -d /etc/lvm -a -x /sbin/vgscan -a -x /sbin/vgchange ; then > # Waiting for udev to settle > if [ "$LVM_DEVICE_TIMEOUT" -gt 0 ] ; then > echo "Waiting for udev to settle..." > /sbin/udevadm settle --timeout=$LVM_DEVICE_TIMEOUT > fi > echo "Scanning for LVM volume groups..." > /sbin/vgscan --mknodes > echo "Activating LVM volume groups..." > /sbin/vgchange -a y $LVM_VGS_ACTIVATED_ON_BOOT > mount -c -a -F Well, this is some interesting stuff. At first I thought you quoted it from an initrd script, but then I read you don't use an initrd. So where this script comes from? Did you write it, or is it shipped with the distro? Maybe the timeouts can be tweaked to allow a longer activation time, and it is also sane to only allow the root VG to activate at boot time and then activating the data VG later (probably asynchronously), after the root LV was successfully mounted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
Turns out, the suggested --setactivationskip option is not present in Utopic, as Utopic comes with an LVM version which dates back to 2012 (2.02.98(2) (2012-10-15)), while the feature was implemented in 2013. Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01). Activation skip could be a nice workaround if it would be backported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
Got an interesting reply from the Red Hat LVM mailing list: https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html Haven't tested the suggestion yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
With the knowledge that the hang is caused by snapshots, some googling has brought up some duplicates: https://bugs.launchpad.net/lvm2/+bug/360237 https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645 It seems the issue was hanging around since 2009 or earlier. In Trusty (or probably even earlier distros) it was possible to work around by setting a sufficiently long rootdelay, and eventually all the LVs in all VGs came online. But since Utopic, initrd gives up altogether. No matter how long my rootdelay is, my 2nd VG never gets activated after the snapshot came online in the 1st VG. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot
*** This bug is a duplicate of bug 1396213 *** https://bugs.launchpad.net/bugs/1396213 ** This bug is no longer a duplicate of bug 995645 udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' ** This bug has been marked a duplicate of bug 1396213 LVM VG is not activated during system boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/360237 Title: cannot boot root on lvm2 with (largish) snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/360237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995645] Re: udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''
*** This bug is a duplicate of bug 1396213 *** https://bugs.launchpad.net/bugs/1396213 ** This bug has been marked a duplicate of bug 1396213 LVM VG is not activated during system boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995645 Title: udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432899] Re: VESA error: Cannot read int vect
Today's update of xserver-xorg-core has fixed the issue. xorg-server (2:1.17.1-0ubuntu3) vivid; urgency=medium * Add a patch to fix vesa int10 failure. (LP: #1433198) -- Maarten Lankhorst Thu, 19 Mar 2015 10:13:08 +0100 ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-driver-vesa (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xorg (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-driver-vesa Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432899 Title: VESA error: Cannot read int vect To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-vesa/+bug/1432899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
Now I have some more info about this. What actually makes the VG activation so long is that I have a snapshot. Activating the snapshot takes very long, and bringing up the entire VG takes about 5 minutes. This wouldn't be such a big problem, as I could just patiently wait for the activation (with rootdelay). But I think the problem is that something kills vgchange before it could finish bringing up all VGs. I had the fortune to boot a developmental Vivid, and I've seen some 'watershed' messages stating that 'vgchange' was killed because it was taking "too long". If we'd let 'vgchange' to finish properly, I had the 2nd VG, which contains my root FS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432899] Re: VESA error: Cannot read int vect
** Also affects: xserver-xorg-driver-vesa (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (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/1432899 Title: VESA error: Cannot read int vect To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-vesa/+bug/1432899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
Is there anything I can do to get the patch actually backported? Can I somehow backport it myself or something? Even with the latest Utopic kernel which was published few days ago, I still don't have a kexec-able kernel. I can imagine the Vivid release will happen earlier than I'll get a patched kernel in Utopic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423796] Re: Unable to mount lvmcache root device at boot time
** Description changed: - I'm experiencing with Vivid Vervet on a virtual machine and tried a new + I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. - System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1423796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423796] Re: Unable to mount lvmcache root device at boot time
** Tags added: vivid ** Description changed: I'm experiencing with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other initrd hacking. + + + System details: + + Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 + x86_64 x86_64 x86_64 GNU/Linux + + Distributor ID: Ubuntu + Description: Ubuntu Vivid Vervet (development branch) + Release: 15.04 + Codename: vivid + + LVM version: 2.02.111(2) (2014-09-01) + Library version: 1.02.90 (2014-09-01) + Driver version: 4.28.0 ** Description changed: I'm experiencing with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, - preferably without /etc/initramfs-tools/modules and other initrd + preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1423796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423796] Re: Unable to mount lvmcache root device at boot time
This is an lvm2 bug and I wanted to report it to lvm2, not Linux. I remember that I exactly typed lvm2, I don't know why it was still reported to linux. Could someone help me to sort it out? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423796] [NEW] Unable to mount lvmcache root device at boot time
Public bug reported: I'm experiencing with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other initrd hacking. ** Affects: linux (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/1423796 Title: Unable to mount lvmcache root device at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
The following commit fixes the problem in mainline: commit f285f4a21c3253887caceed493089ece17579d59 Author: Kees Cook Date: Thu Jan 15 16:51:46 2015 -0800 x86, boot: Skip relocs when load address unchanged On 64-bit, relocation is not required unless the load address gets changed. Without this, relocations do unexpected things when the kernel is above 4G. Reported-by: Baoquan He Signed-off-by: Kees Cook Tested-by: Thomas D. Cc: Vivek Goyal Cc: Jan Beulich Cc: Junjie Mao Cc: Andi Kleen Cc: sta...@vger.kernel.org Link: http://lkml.kernel.org/r/20150116005146.ga4...@www.outflux.net Signed-off-by: Thomas Gleixner -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
I've tested the issue with mainline kernel v3.19-rc7-vivid, and it works now! However, the actual Ubuntu kernel, 3.16.0-30-generic, still has the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
Please try the patch mentioned here: https://lkml.org/lkml/2014/12/1/790 If it works, it would be nice to tell the authors to get it included in the mainline kernel. I've already told them, but one man is probably not enough. (I'm not sure if it's included already, and currently I have no time to test.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400176] Re: Missing git-daemon-* package for Upstart
Yeah, but I always felt, using sysvinit scripts under Upstart is a legacy solution which is provided for compatibility, but is deprecated. I remembered the switch would happen with the next LTS, but probably you have more accurate information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400176 Title: Missing git-daemon-* package for Upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1400176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400176] [NEW] Missing git-daemon-* package for Upstart
Public bug reported: I've seen there are packages to set up git-daemon easily with sysvinit and runit (git-daemon-sysvinit and git-daemon-run). I've been wondering why there isn't a package which sets up an Upstart job, since Upstart is widely used in Ubuntu. I've made such package: git-daemon-upstart. If you'd kindly verify it and put it into the repositories, everyone would benefit from it. :) ** Affects: git (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Git-daemon package for Upstart" https://bugs.launchpad.net/bugs/1400176/+attachment/4275880/+files/git-daemon-upstart.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400176 Title: Missing git-daemon-* package for Upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1400176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
I've had a backup of my old Trusty system, and I've built an initrd for 3.16.0-23-generic in that environment. With that initrd, the kernel booted properly. Note, still it takes several minutes for the VG to activate, but it eventually comes up if the kernel waits enough with "rootdelay=300". Now, kernel bisection would take me to nowhere, as it seems the problem is not with the kernel itself. Any initrd I build under Utopic has the symptom, even older kernels from the 3.13 series. Could you advise how could I investigate further? I have no idea how could I debug/bisect initrd-s. As I found, the lvm2 package hasn't changed between Trusty and Utopic, so it's not lvm2's initrd scripts themselves. ** Also affects: lvm2 (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/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391429] Re: grub-probe takes snapshot LV instead of origin
Reported upstream to BTRFS developers: https://bugzilla.kernel.org/show_bug.cgi?id=89121 ** Bug watch added: Linux Kernel Bug Tracker #89121 http://bugzilla.kernel.org/show_bug.cgi?id=89121 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391429 Title: grub-probe takes snapshot LV instead of origin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1391429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
I've posted the problem report. Here are the URLs to track from several mail archives: http://www.spinics.net/lists/kernel/msg1878907.html http://marc.info/?l=linux-kernel&m=141741553905446&w=2 https://lkml.org/lkml/2014/12/1/15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: kexec reboot fails
The first bad commit is 8ab3820fd5b2896d66da7bb2a906bc382e63e7bc x86, kaslr: Return location from decompress_kernel which introduces KASLR. The problem only presents itself when CONFIG_RANDOMIZE_BASE=y. While this bug has been around in the kernel source for quite a time, it was dormant, as this option wasn't enabled in some previous Ubuntu kernel configurations. (This actually caused some headache during the bisection, as I needed to realize that I have to make sure this option is always enabled to get proper test results.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: kexec reboot fails
I did the BIOS upgrade and nothing has changed. 7UET94WW (3.24 ) 10/17/2012 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
Yeah, I was in hurry and didn't have the time to give you the reason why I did this. I sent the latest apport from a kernel with which I don't experience the issue. The difference is that I see these messages: [5.527952] bio: create slab at 1 [ 151.415509] bio: create slab at 2 [ 161.717873] bio: create slab at 3 [ 162.277013] bio: create slab at 4 When the last of these appears, boot immediately continues correctly. Not sure if it's of any relevance. Anyway, today I've tried the following mainline kernels: 3.13.0-031300 3.14.0-031400 3.15.0-031500 3.16.0-031600 What surprised me is that even with 3.13.0-031300 I experienced the problem. I'm kind of confused now. I'll continue investigation tomorrow. I will do kernel bisection as you requested, but first I'd like to make sure the problem is not with initrd-s. I don't know what to do if it turns out my initrd-s are the culprits. The only working kernel I have (vmlinuz-3.13.0-37-generic) has its initrd generated from the old Trusty times. It seems every initrd I generate with any new installed kernel with Utopic, has the problem. I won't send more apports, sorry for the inconvenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: kexec reboot fails
** Description changed: After release upgrade to Utopic, when I reboot with kexec (simply with "reboot" command), my computer cold reboots after "Starting new kernel" (i.e. I need to get through the POST and GRUB), instead of the new kernel being loaded. Previously I didn't experience problems with Trusty. It matters which kernel I try to boot, while it doesn't matter what kernel I kexec from, and which version of kexec-tools I have. I can't boot 3.16.0-25, nor 3.18.0-031800rc6 from any installed kernels, while I can boot 3.13.0-39 from any kernels without any problems. I tried to downgrade kexec-tools from 1:2.0.7-1ubuntu2 (utopic) to 1:2.0.6-0ubuntu2.1 (trusty), but it made no difference. - I have a Lenovo Thinkpad T410. I didn't experience the same on my other + I have a Lenovo Thinkpad T400. I didn't experience the same on my other machines, so I suspect some hardware-dependent issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC0: megabrutal 2497 F pulseaudio - /dev/snd/seq:timidity 1420 F timidity + USER PID ACCESS COMMAND + /dev/snd/controlC0: megabrutal 2497 F pulseaudio + /dev/snd/seq:timidity 1420 F timidity Date: Thu Nov 27 07:40:07 2014 HibernationDevice: RESUME=UUID=3d113c6f-7cf8-477f-81e1-857aa62102c2 InstallationDate: Installed on 2014-06-10 (169 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcEnviron: - LANGUAGE=hu - TERM=xterm - PATH=(custom, no user) - LANG=hu_HU.UTF-8 - SHELL=/bin/bash + LANGUAGE=hu + TERM=xterm + PATH=(custom, no user) + LANG=hu_HU.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.16.0-25-generic N/A - linux-backports-modules-3.16.0-25-generic N/A - linux-firmware 1.138 + linux-restricted-modules-3.16.0-25-generic N/A + linux-backports-modules-3.16.0-25-generic N/A + linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-11 (15 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474B84 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:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269741/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269743/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269738/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269739/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269740/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269735/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269742/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
apport information ** Description changed: Hi all, I open this report based on the linked conversation I had on the linux-lvm mailing list, and the Ask Ubuntu question I posted regarding this case. https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot I have 2 VGs on my system, and for some reason, only one of them gets activated during the initrd boot sequence, which doesn't have my root LV, so my boot sequence halts with an initrd prompt. When I get to the initrd BusyBox prompt, I can see my LVs are inactive with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The boot sequence continues as I exit the BusyBox prompt. The expected behaviour would be that both VGs should activate automatically. On LVM mailing list, I've been advised it may be a problem with Ubuntu initrd scripts, hence I report this problem here. (I'm not sure if I'm reporting it to the correct place by assigning it to "linux", but I didn't find a package directly related to the initrd only, so I assumed initrd scripts are maintained by the kernel team. If you think it's an error, and know the correct package, please reassign!) Our suspicion is, initrd prematurely issues "vgchange -ay" before all the PVs come online. This makes sense. I already tried to set the "rootdelay" kernel parameter to make initrd wait longer for the boot LV to come up, but it didn't work. Note however, it worked with previous kernel versions. The problem came up when I upgraded to Utopic, and got kernel vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty (vmlinuz-3.13.0-37-generic), it works fine. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.16.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0 InstallationDate: Installed on 2013-12-06 (354 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: WinFast 6150M2MA Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ rootdelay=300 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-23-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 01/19/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 686W1D28 dmi.board.name: 6150M2MA dmi.board.vendor: WinFast dmi.board.version: FAB2.0 dmi.chassis.type: 3 dmi.chassis.vendor: WinFast dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd01/19/2008:svnWinFast:pn6150M2MA:pvrFAB2.0:rvnWinFast:rn6150M2MA:rvrFAB2.0:cvnWinFast:ct3:cvr: dmi.product.name: 6150M2MA dmi.product.version: FAB2.0 dmi.sys.vendor: WinFast --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2013-12-06 (355 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: utopic Uname: Linux 3.18.0-031800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to u
[Bug 1396213] Card1.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: "Card1.Codecs.codec97.0.ac97.0.0.regs.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269734/+files/Card1.Codecs.codec97.0.ac97.0.0.regs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269732/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Card1.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: "Card1.Codecs.codec97.0.ac97.0.0.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269733/+files/Card1.Codecs.codec97.0.ac97.0.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269737/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269736/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4269731/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] [NEW] kexec reboot fails
Public bug reported: After release upgrade to Utopic, when I reboot with kexec (simply with "reboot" command), my computer cold reboots after "Starting new kernel" (i.e. I need to get through the POST and GRUB), instead of the new kernel being loaded. Previously I didn't experience problems with Trusty. It matters which kernel I try to boot, while it doesn't matter what kernel I kexec from, and which version of kexec-tools I have. I can't boot 3.16.0-25, nor 3.18.0-031800rc6 from any installed kernels, while I can boot 3.13.0-39 from any kernels without any problems. I tried to downgrade kexec-tools from 1:2.0.7-1ubuntu2 (utopic) to 1:2.0.6-0ubuntu2.1 (trusty), but it made no difference. I have a Lenovo Thinkpad T410. I didn't experience the same on my other machines, so I suspect some hardware-dependent issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: megabrutal 2497 F pulseaudio /dev/snd/seq:timidity 1420 F timidity Date: Thu Nov 27 07:40:07 2014 HibernationDevice: RESUME=UUID=3d113c6f-7cf8-477f-81e1-857aa62102c2 InstallationDate: Installed on 2014-06-10 (169 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=hu TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-11 (15 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474B84 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:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kernel-bug-exists-upstream kernel-bug-exists-upstream-3.18-rc6 utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
I experience the same symptoms with the mainline kernel. Note, if the problem is really with initrd scripts, then probably the kernel version doesn't matter much. On the other hand, as I see, lvm2 initrd scripts haven't changed since Trusty, which would suggest it's a kernel bug, after all. Hard to pinpoint. Either way, I suspect one of my hard disks (/dev/sda, Maxtor) initializes late, and that might cause the problem. Still interesting that older kernels bother to wait for it and properly activate the vmhost-vg. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.18-rc6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396213] Re: LVM VG is not activated during system boot
** Description changed: Hi all, I open this report based on the linked conversation I had on the linux-lvm mailing list, and the Ask Ubuntu question I posted regarding this case. https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot I have 2 VGs on my system, and for some reason, only one of them gets activated during the initrd boot sequence, which doesn't have my root LV, so my boot sequence halts with an initrd prompt. When I get to the initrd BusyBox prompt, I can see my LVs are inactive with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The boot sequence continues as I exit the BusyBox prompt. The expected behaviour would be that both VGs should activate automatically. On LVM mailing list, I've been advised it may be a problem with Ubuntu initrd scripts, hence I report this problem here. (I'm not sure if I'm reporting it to the correct place by assigning it to "linux", but I didn't find a package directly related to the initrd only, so I assumed initrd scripts are maintained by the kernel team. If you think it's an error, and know the correct package, please reassign!) Our suspicion is, initrd prematurely issues "vgchange -ay" before all the PVs come online. This makes sense. I already tried to set the "rootdelay" kernel parameter to make initrd wait longer for the boot LV to come up, but it didn't work. Note however, it worked with previous kernel versions. The problem came up when I upgraded to Utopic, and got kernel vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty (vmlinuz-3.13.0-37-generic), it works fine. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.16.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0 InstallationDate: Installed on 2013-12-06 (354 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: WinFast 6150M2MA Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ rootdelay=300 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-23-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 01/19/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 686W1D28 dmi.board.name: 6150M2MA dmi.board.vendor: WinFast dmi.board.version: FAB2.0 dmi.chassis.type: 3 dmi.chassis.vendor: WinFast dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd01/19/2008:svnWinFast:pn6150M2MA:pvrFAB2.0:rvnWinFast:rn6150M2MA:rvrFAB2.0:cvnWinFast:ct3:cvr: dmi.product.name: 6150M2MA dmi.product.version: FAB2.0 dmi.sys.vendor: WinFast + --- + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 14.10 + InstallationDate: Installed on 2013-12-06 (355 days ago) + InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US:en + TERM=linux + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: utopic + Uname: Linux 3.18.0-031800rc6-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to utopic on 2014-10-28
[Bug 1396213] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1396213/+attachment/4268375/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
