[Bug 2069635] [NEW] package sslh 1.20-1 failed to install/upgrade: installed sslh package post-installation script subprocess returned error exit status 1
Public bug reported: I am running do-release-upgrade and it is failing on this. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sslh 1.20-1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 17 17:20:20 2024 ErrorMessage: installed sslh package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-28 (1357 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200810) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: sslh Title: package sslh 1.20-1 failed to install/upgrade: installed sslh package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2024-06-17 (0 days ago) mtime.conffile..etc.default.sslh: 2020-10-15T21:22:38.661695 ** Affects: sslh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069635 Title: package sslh 1.20-1 failed to install/upgrade: installed sslh package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sslh/+bug/2069635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696500] Re: /var/log/wtmp is updated to 1970-01-01 before systemd-update-utmp.service (or fake-hwclock)
This is still a problem in June 2021. Would you mind please explaining the reason for not fixing it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696500 Title: /var/log/wtmp is updated to 1970-01-01 before systemd-update- utmp.service (or fake-hwclock) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812430] Re: intel hd 500 - j3455 no graphic driver
Anyone has a solution to this? - I have a J3455 and there is no display driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812430 Title: intel hd 500 - j3455 no graphic driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1812430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871963] Re: dpkg fails to install grub-efi-amd64 signed and shim-signed
It seems to only happen when doing: # DEBIAN_FRONTEND=noninteractive apt-get -f install When it is interactive, it asks to select /dev/sda and then it upgrades. How to upgrade this package non interactive? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871963 Title: dpkg fails to install grub-efi-amd64 signed and shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859870] Re: package libc6 2.23-0ubuntu11 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Bus error), core dumped
Same problem here, any solution or workaround? root@TimeBox-fda381d10fc57bfd8b1b:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libc-bin libc6 Suggested packages: glibc-doc The following NEW packages will be installed: libc-bin The following packages will be upgraded: libc6 1 upgraded, 1 newly installed, 0 to remove and 102 not upgraded. 1 not fully installed or removed. Need to get 0 B/3464 kB of archives. After this operation, 3718 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Bus error (core dumped) (Reading database ... 82500 files and directories currently installed.) Preparing to unpack .../libc6_2.27-3ubuntu1.2_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libc6_2.27-3ubuntu1.2_amd64.deb (--unpack): new libc6:amd64 package pre-installation script subprocess was killed by signal (Bus error), core dumped Errors were encountered while processing: /var/cache/apt/archives/libc6_2.27-3ubuntu1.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@TimeBox-fda381d10fc57bfd8b1b:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859870 Title: package libc6 2.23-0ubuntu11 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Bus error), core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1859870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828929] Re: upload speed is reported wrong
I've got the same issue :( - any solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828929 Title: upload speed is reported wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1828929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795936 Title: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
As a workaround, removing the -proposed repositories from the sources.list file fixes 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/1795936 Title: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
** Description changed: I'm building a Ubuntu Server in a chroot with: $ debootstrap --arch amd64 bionic /mnt/ubuntu - Once inside the chroot I run apt-get install linux-image-generic - this - was working correctly earlier today but at the moment I get the + Once inside the chroot I run apt-get install linux-image-generic grub-pc + - this was working correctly earlier today but at the moment I get the following: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ``` Any ideas? --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcCpuinfoMinimal: Error: [Errno 2] No such file or directory: '/proc/cpuinfo' ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/11605/environ' Tags: bionic Uname: Linux 4.17.1-smos x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True ** Description changed: I'm building a Ubuntu Server in a chroot with: $ debootstrap --arch amd64 bionic /mnt/ubuntu Once inside the chroot I run apt-get install linux-image-generic grub-pc - - this was working correctly earlier today but at the moment I get the - following: + - this was working correctly earlier today (and the many times I did + this past few months) but at the moment I get the following: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src
[Bug 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
** Tags added: apport-collected ** Description changed: This was working an hour ago, but at the moment I get the following when I run: apt-get install linux-image-generic: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ``` Any ideas? + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: linux (not installed) + ProcCpuinfoMinimal: Error: [Errno 2] No such file or directory: '/proc/cpuinfo' + ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/11605/environ' + Tags: bionic + Uname: Linux 4.17.1-smos x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: - This was working an hour ago, but at the moment I get the following when - I run: apt-get install linux-image-generic: + I'm building a Ubuntu Server in a chroot with: + $ debootstrap --arch amd64 bionic /mnt/ubuntu + + Once inside the chroot I run apt-get install linux-image-generic - this + was working correctly earlier today but at the moment I get the + following: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable -Recommends: thermald but it is not going to be installed + linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable + Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ```
[Bug 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
** Package changed: apport (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795936 Title: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795936] [NEW] linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
Public bug reported: This was working an hour ago, but at the moment I get the following when I run: apt-get install linux-image-generic: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ``` Any ideas? ** Affects: apport (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/1795936 Title: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1795936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696500] [NEW] /var/log/wtmp is updated to 1970-01-01 before systemd-update-utmp.service (or fake-hwclock)
Public bug reported: I have a raspberry pi with fake-hwclock installed and it seems the documented behaviour doesn't work E.g. from /lib/systemd/system/systemd- timesyncd.service, specifically: "ensure [clock] monotonically advances even if the system lacks a battery-buffered RTC chip" - this doesn't actually happen. I have tried editing /lib/systemd/system/fake-hwclock.service to have: [Unit] Description=Restore / save the current clock Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=systemd-update-utmp.service sysinit.target Conflicts=shutdown.target I also tried to edit /lib/systemd/system/systemd-update-utmp.service to have: [Unit] Description=Update UTMP about System Boot/Shutdown Documentation=man:systemd-update-utmp.service(8) man:utmp(5) DefaultDependencies=no RequiresMountsFor=/var/log/wtmp Conflicts=shutdown.target # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service After=systemd-timesyncd.service fake-hwclock.service time-sync.target Before=sysinit.target shutdown.target [Service] Type=oneshot RemainAfterExit=yes ExecStartPre=/sbin/fake-hwclock load ExecStart=/lib/systemd/systemd-update-utmp reboot ExecStop=/lib/systemd/systemd-update-utmp shutdown However on reboot, the wtmp file is still being updated before systemd- update-utmp.service and fake-hwclock: $ last reboot | head -n 3 reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 still running reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 - 22:04 (17316+21:04) reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 - 22:04 (17316+21:04) Looking at the journalctl I can see the time is already set and /var/log/wtmp is already updated to 1970 before any of the above can run: $ sudo journalctl -u systemd-update-utmp -- Logs begin at Wed 2017-06-07 17:18:08 IST, end at Wed 2017-06-07 17:19:05 IST. -- Jun 07 17:18:14 TimeBox systemd[1]: Starting Update UTMP about System Boot/Shutdown... Jun 07 17:18:14 TimeBox fake-hwclock[823]: Current system time: 2017-06-07 16:18:14 Jun 07 17:18:14 TimeBox fake-hwclock[823]: fake-hwclock saved clock information is in the past: 2017-06-07 16:18:08 Jun 07 17:18:14 TimeBox fake-hwclock[823]: To set system time to this saved clock anyway, use "force" Jun 07 17:18:14 TimeBox systemd[1]: Started Update UTMP about System Boot/Shutdown. So the "Update UTMP about System Boot/Shutdown." doesn't work, the time is already set to 1 Jan 1970 by something else. How do I run a service/command before /var/log/wtmp is touched and set to 1 Jan 1970? - It seems the documented behaviour/methods do not work. I'm using Ubuntu 16.04 with systemd 229-4ubuntu17 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: fakehw-clock raspberrypi rtc systemd ** Description changed: I have a raspberry pi with fake-hwclock installed and it seems the documented behaviour doesn't work E.g. from /lib/systemd/system/systemd- timesyncd.service, specifically: "ensure [clock] monotonically advances even if the system lacks a battery-buffered RTC chip" - this doesn't actually happen. I have tried editing /lib/systemd/system/fake-hwclock.service to have: - [Unit] - Description=Restore / save the current clock - Documentation=man:fake-hwclock(8) - DefaultDependencies=no - Before=systemd-update-utmp.service sysinit.target - Conflicts=shutdown.target + [Unit] + Description=Restore / save the current clock + Documentation=man:fake-hwclock(8) + DefaultDependencies=no + Before=systemd-update-utmp.service sysinit.target + Conflicts=shutdown.target + + I also tried to edit /lib/systemd/system/systemd-update-utmp.service to have: - [Unit] - Description=Update UTMP about System Boot/Shutdown - Documentation=man:systemd-update-utmp.service(8) man:utmp(5) - DefaultDependencies=no - RequiresMountsFor=/var/log/wtmp - Conflicts=shutdown.target - # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service - After=systemd-timesyncd.service fake-hwclock.service time-sync.target - Before=sysinit.target shutdown.target + [Unit] + Description=Update UTMP about System Boot/Shutdown + Documentation=man:systemd-update-utmp.service(8) man:utmp(5) + DefaultDependencies=no + RequiresMountsFor=/var/log/wtmp + Conflicts=shutdown.target + # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service + After=systemd-timesyncd.service fake-hwclock.service time-sync.target + Before=sysinit.target shutdown.target - [Service] - Type=oneshot - RemainAfterExit=yes - ExecStartPre=/sbin/fake-hwclock load - ExecStart=/lib/systemd/systemd-update-utmp reboot - ExecStop=/lib/systemd/systemd-update-utmp shutdown - However on reboot, the wtmp file is still being
[Bug 1616894] Re: [BYT] display hotplug doesn't work on console
I've just reproduced the same behaviour on 17.04 - 4.10.0-22-generic - so it seems this is still an issue on latest versions of the kernel/ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616894 Title: [BYT] display hotplug doesn't work on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616894] Re: [BYT] display hotplug doesn't work on console
I'm also experiencing the same problem on a Gigabyte Brix J1900 unit (similar to Intel Nuc). When I plug in a monitor before turning the unit on, console shows a login on the display. If I plug a monitor after boot, it shows no input signal. Same kernel/ubuntu version. Here is output from lspci -v: 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Gigabyte Technology Co., Ltd Atom Processor Z36xxx/Z37xxx Series Graphics & Display Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at d000 (32-bit, non-prefetchable) [size=4M] Memory at c000 (32-bit, prefetchable) [size=256M] I/O ports at f080 [size=8] Expansion ROM at [disabled] Capabilities: [d0] Power Management version 2 Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [b0] Vendor Specific Information: Len=07 Kernel modules: i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616894 Title: [BYT] display hotplug doesn't work on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616894] Re: [BYT] display hotplug doesn't work on console
I'm using 4.4.0-79-generic and experiencing this problem (Ubuntu Server 16.04.2) $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) This is a Shuttle XS35-V2 with a Pentium G2020 CPU. If booting with the monitor plugged in, it shows the console login. If connecting a monitor after the boot, the monitor shows no input signal. Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616894 Title: [BYT] display hotplug doesn't work on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616894] Re: [BYT] display hotplug doesn't work on console
Full PCI device info (with lspci -v) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f780 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at [disabled] Capabilities: Kernel modules: i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616894 Title: [BYT] display hotplug doesn't work on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691729] Re: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin
Thank you for the workaround, that's very helpful :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691729 Title: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691729] Re: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin
Any solution to this? - Experiencing the same problem: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 18 not fully installed or removed. Need to get 0 B/38.7 MB of archives. After this operation, 5624 kB of additional disk space will be used. Do you want to continue? [Y/n] Y N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension (Reading database ... 105518 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.157.10_all.deb ... Unpacking linux-firmware (1.157.10) over (1.157.8) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.10_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43430-sdio.bin', which is also in package linux-firmware-raspi2 1.20161020-0ubuntu1~0.2~rpi3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691729 Title: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692175] Re: package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Wow, how can a package that does not install because of a syntax error be committed to production? - Are there no automated tests to prevent this sort of thing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692175 Title: package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1692175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
Note, after following Anthony's tip and doing an apt-get dist-upgrade, wifi stops working :( - anyone have any ideas how to get wifi working on the latest kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
StatnMap, what RaspberryPi do you have? - I installed https://ubuntu-pi- flavour-maker.org/download/ classic server 16.04 and ran apt-get update; apt-get dist-upgrade and this has bricked by Raspberry Pi3. Anthony's solution worked for me, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
I take it this have not been fixed. I just tried installing ubuntu again, ran apt-get upgrade; apt-get dist-upgrade, rebooted and it says: ERROR: `server' not set. and Config file not found. and will not boot :( Is there a permanent solution to this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
Any updates on this? - it's a critical issue that is bricking all raspberry pi units out there without any user intervention... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
As a workaround for those that haven't bricked their Raspberry, run this to prevent bricking until this is resolved: sudo apt-mark hold linux-raspi2 linux-image-raspi2 linux-headers-raspi2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
I'm having the same issue, linux-image-4.4.0-1009-raspi2 boots without issues, upgrading to linux-image-4.4.0-1040-raspi2 and the Raspberry Pi 3 does not boot anymore :( - any solution except downgrading? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I'm on systemd 229-4ubuntu10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I'm on Xenial and I ran an apt-get update; apt-get dist-upgrade and my eth0 changed back to enxb827djdk after reboot :( My biggest issue is virtual interfaces do NOT work with these "predictable" network names. I can do ifconfig eth0:0 192.168.123.123 but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just overrites the main IP, rather than creating another virtual interface :( Previously, I was able to follow these steps: Edit/boot/firmware/config.txt to add: net.ifnames=0 biosdevname=0 Run: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules Make sure this file is absent (which it was anyway): /lib/udev/rules.d/73-usb-net-by-mac.rules Run: update-initramfs -k all -u But now, running the above steps no longer works and I'm getting enxb827djdk again :( I also checked /proc/cmdline and I have net.ifnames=0 there so it's definitely being passed. I'm running kernel 4.4.0-1023-raspi2 Sep 6 16:12:44 UTC 2016 Is there a solution/workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562219] Re: xinit will not work as non-root.
The workaround is not working :( - $ sudo setfacl -m u:kodi:rw /dev/tty0 /dev/tty7 setfacl: Option -m: Invalid argument near character 3 $ sudo chmod 0660 /dev/tty* $ $ startx ... Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory) ... Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: xinit will not work as non-root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Any solution to this? - I'm passing net.ifnames=0 biosdevname=0 but after the latest apt-get upgrade, it is ignored :( -- deployer@ubuntu:~$ uname -a Linux ubuntu 4.4.0-1021-raspi2 #27-Ubuntu SMP Fri Aug 12 11:44:06 UTC 2016 armv7l armv7l armv7l GNU/Linux deployer@ubuntu:~$ cat /proc/cmdline 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa02082 bcm2709.serial=0x80f5f71c smsc95xx.macaddr=B8:27:EB:F5:F7:1C bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait net.ifnames=0 biosdevname=0 deployer@ubuntu:~$ ifconfig -a enxb827ebf5f71c Link encap:Ethernet HWaddr b8:27:eb:f5:f7:1c inet addr:192.168.101.69 Bcast:192.168.101.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fef5:f71c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:666 errors:0 dropped:0 overruns:0 frame:0 TX packets:514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:106425 (106.4 KB) TX bytes:94870 (94.8 KB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585906] Re: Can't disable consistent device naming (biosdevname) for Wifi
Any solution to this? - I'm passing net.ifnames=0 biosdevname=0 but after the latest apt-get upgrade, it is ignored :( -- deployer@ubuntu:~$ uname -a Linux ubuntu 4.4.0-1021-raspi2 #27-Ubuntu SMP Fri Aug 12 11:44:06 UTC 2016 armv7l armv7l armv7l GNU/Linux deployer@ubuntu:~$ cat /proc/cmdline 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa02082 bcm2709.serial=0x80f5f71c smsc95xx.macaddr=B8:27:EB:F5:F7:1C bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait net.ifnames=0 biosdevname=0 deployer@ubuntu:~$ ifconfig -a enxb827ebf5f71c Link encap:Ethernet HWaddr b8:27:eb:f5:f7:1c inet addr:192.168.101.69 Bcast:192.168.101.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fef5:f71c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:666 errors:0 dropped:0 overruns:0 frame:0 TX packets:514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:106425 (106.4 KB) TX bytes:94870 (94.8 KB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585906 Title: Can't disable consistent device naming (biosdevname) for Wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1585906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545441] Re: Xenial/4.4 kernel does not honor biosdevname=0
Any solution to this? - I'm passing net.ifnames=0 biosdevname=0 but after the latest apt-get upgrade, it is ignored :( -- deployer@ubuntu:~$ uname -a Linux ubuntu 4.4.0-1021-raspi2 #27-Ubuntu SMP Fri Aug 12 11:44:06 UTC 2016 armv7l armv7l armv7l GNU/Linux deployer@ubuntu:~$ cat /proc/cmdline 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa02082 bcm2709.serial=0x80f5f71c smsc95xx.macaddr=B8:27:EB:F5:F7:1C bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait net.ifnames=0 biosdevname=0 deployer@ubuntu:~$ ifconfig -a enxb827ebf5f71c Link encap:Ethernet HWaddr b8:27:eb:f5:f7:1c inet addr:192.168.101.69 Bcast:192.168.101.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fef5:f71c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:666 errors:0 dropped:0 overruns:0 frame:0 TX packets:514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:106425 (106.4 KB) TX bytes:94870 (94.8 KB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545441 Title: Xenial/4.4 kernel does not honor biosdevname=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1531299] Re: postfix upgrade can fail due to "newaliases: fatal: inet_addr_local[getifaddrs]: getifaddrs: Address family not supported by protocol" under qemu-static
This is affecting xenial clean install also :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531299 Title: postfix upgrade can fail due to "newaliases: fatal: inet_addr_local[getifaddrs]: getifaddrs: Address family not supported by protocol" under qemu-static To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1531299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554806] Re: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now
Ah, sorry, didn't read the report properly. Thank you for the workaround! -- Any workaround for echo "en_GB.UTF-8 UTF-8" > /var/lib/locales/supported.d/local? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554806 Title: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1554806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554806] Re: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now
Any workaround for this? - How would one automate setting a timezone on 16.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554806 Title: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1554806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1531299] Re: postfix upgrade can fail due to "newaliases: fatal: inet_addr_local[getifaddrs]: getifaddrs: Address family not supported by protocol" under qemu-static
Any permanent solution to this? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531299 Title: postfix upgrade can fail due to "newaliases: fatal: inet_addr_local[getifaddrs]: getifaddrs: Address family not supported by protocol" under qemu-static To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1531299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558447] Re: vivid/linux: total ADT test failures
Experiencing the same :( - any workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558447 Title: vivid/linux: total ADT test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558447] Re: vivid/linux: total ADT test failures
Thank you, problem went away with latest kernel upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558447 Title: vivid/linux: total ADT test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
I think "blacklist pinctrl-cherryview" helps with boot, but now experiencing stability issues: the system freezes after a few days of operation which never happened before on 15.04 :( -- do you experience any similar issues? any solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
Thank you for that. I've actually switched to 15.04 because 15.10 seems to be unusable on these NUCs :( -- But for those NUCs already on 15.10 I will blacklist pinctrl-cherryview as you suggest, thank you!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527914] Re: Huawei E3372 is not detected and cannot be used
This is what I see when I plug mine in: https://gist.github.com/xanview/3a37e6eb0cf24a12908b The key lines are: Jan 28 16:19:23 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:19:23 TimeBox systemd[1]: usb_modeswitch@1-1.5-1-1.5:1.0.service: main process exited, code=exited, status=1/FAILURE It seems Ubuntu is trying to do the wrong thing, it is trying to do systemctl start usb_modeswitch@1-1.5-1-1.5:1.0 when in reality the command should be: $ systemctl start usb_modeswitch@1-1.5:1.0 When I run the correct command, I see this in syslog: Jan 28 16:34:05 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: Could not read attribute: No such file or directory Jan 28 16:34:06 TimeBox usb_modeswitch: switch device 12d1:14fe on 001/008 Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: message repeated 2 times: [ Could not read attribute: No such file or directory] Jan 28 16:34:07 TimeBox usb_modeswitch[10502]: usb_modeswitch: switched to 12d1:14fe on 1/8 Jan 28 16:34:08 TimeBox usb_modeswitch_dispatcher[10502]: Unable to open bind list file: No such file or directory Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: add device ID 12d1:14fe to driver option Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: please report the device ID to the Linux USB developers! Jan 28 16:34:15 TimeBox systemd[1]: Started USB_ModeSwitch. So seems this is an unsupported device still? (I'm on Ubuntu 15.04 Vivid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527914 Title: Huawei E3372 is not detected and cannot be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330262] Re: HUAWEI E3531 not connected on Ubuntu 14.04
I am seeing something completely different and for me the issue is with usb_modeswitch first: This is what I see when I plug mine in: https://gist.github.com/xanview/3a37e6eb0cf24a12908b The key lines are: Jan 28 16:19:23 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:19:23 TimeBox systemd[1]: usb_modeswitch@1-1.5-1-1.5:1.0.service: main process exited, code=exited, status=1/FAILURE It seems Ubuntu is trying to do the wrong thing, it is trying to do systemctl start usb_modeswitch@1-1.5-1-1.5:1.0 when in reality the command should be: $ systemctl start usb_modeswitch@1-1.5:1.0 When I run the correct command, I see this in syslog: Jan 28 16:34:05 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: Could not read attribute: No such file or directory Jan 28 16:34:06 TimeBox usb_modeswitch: switch device 12d1:14fe on 001/008 Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: message repeated 2 times: [ Could not read attribute: No such file or directory] Jan 28 16:34:07 TimeBox usb_modeswitch[10502]: usb_modeswitch: switched to 12d1:14fe on 1/8 Jan 28 16:34:08 TimeBox usb_modeswitch_dispatcher[10502]: Unable to open bind list file: No such file or directory Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: add device ID 12d1:14fe to driver option Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: please report the device ID to the Linux USB developers! Jan 28 16:34:15 TimeBox systemd[1]: Started USB_ModeSwitch. So seems this is an unsupported device still? (I'm on Ubuntu 15.04 Vivid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330262 Title: HUAWEI E3531 not connected on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1330262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424181] Re: Huawei E3372 USB modem not always detected
This is what I see when I plug mine in: https://gist.github.com/xanview/3a37e6eb0cf24a12908b The key lines are: Jan 28 16:19:23 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:19:23 TimeBox systemd[1]: usb_modeswitch@1-1.5-1-1.5:1.0.service: main process exited, code=exited, status=1/FAILURE It seems Ubuntu is trying to do the wrong thing, it is trying to do systemctl start usb_modeswitch@1-1.5-1-1.5:1.0 when in reality the command should be: $ systemctl start usb_modeswitch@1-1.5:1.0 When I run the correct command, I see this in syslog: Jan 28 16:34:05 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: Could not read attribute: No such file or directory Jan 28 16:34:06 TimeBox usb_modeswitch: switch device 12d1:14fe on 001/008 Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: message repeated 2 times: [ Could not read attribute: No such file or directory] Jan 28 16:34:07 TimeBox usb_modeswitch[10502]: usb_modeswitch: switched to 12d1:14fe on 1/8 Jan 28 16:34:08 TimeBox usb_modeswitch_dispatcher[10502]: Unable to open bind list file: No such file or directory Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: add device ID 12d1:14fe to driver option Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: please report the device ID to the Linux USB developers! Jan 28 16:34:15 TimeBox systemd[1]: Started USB_ModeSwitch. So seems this is an unsupported device still? (I'm on Ubuntu 15.04 Vivid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424181 Title: Huawei E3372 USB modem not always detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431179] Re: usb_modeswitch@.service fails
I'm having the same issue. Ubuntu tries to start service usb_modeswitch@1-1.4-1-1.4:1.0 -- this fails. If I start service: usb_modeswitch@1-1.4:1.0 manually, running systemctl start usb_modeswitch@1-1.4:1.0 - that works fine and my 3g modem starts working. Anyone have a permanent solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431179 Title: usb_modeswitch@.service fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1431179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Any workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509769 Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1509769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
It seems the following helps: BIOS > Boot > Boot Configuration > OS Selection > set Linux However this is not required in previous versions of the kernel and it is not practical to do this when all of your NUC machines are in different locations across the country :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
I don't understand - I already ran ubuntu-bug - others have confirmed the issue. Why do you need it ran again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
How many people do you want to run ubuntu-bug linux? - I already ran it in the original bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
How many people do you want to run ubuntu-bug linux? - I already ran it in the original bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
When the bug was reported, I used the latest version of the BIOS available for download. I am presently abroad, but I will download and try with PY0047 when I am back on the 26th. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
I also reported this to Intel here: https://communities.intel.com/thread/94213 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
I also reported this to Intel here: https://communities.intel.com/thread/94213 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Attachment added: "DSDT generated with "sudo -u \#0 acpidump -bn DSDT; iasl -d dsdt.dat"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+attachment/4529649/+files/dsdt.dsl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Description changed: - This bug might be related to this bug: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 - I have an Intel NUC NUC5CPYH. This is the unit: http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux- - image-4.2.0-19-generic on the latest PY0044 BIOS version, it does not - boot at all. If I downgrade the BIOS to PY0043, it boots, but then I am - not able to reboot it. + image-4.2.0-19-generic on the latest PY0044 BIOS version, it freezes on + boot almost every time, reported bug here: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 - When I run "reboot", it freezes showing this screen: + If I downgrade the BIOS to PY0043, it boots most of the time, but when I + run "reboot" it freezes almost every single time. This is what I see on + the screen when it freezes: + https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 I am also attaching the full syslog, dmesg and the relevant part of the syslog when the system froze. + + I tried to boot with acpi_osi="Windows 2013" as well as Windows 2015 and + Windows 2009, that did not seem to make any difference. Any ideas? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 15.10 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG= SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Description changed: This bug might be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 - I have a NUC NUC5CPYH. It boots and reboots beautifully on Ubuntu 15.04 - and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to - boot with linux-image-4.2.0-19-generic on the latest PY0044 BIOS - version, it does not boot at all. If I downgrade the BIOS to PY0043, it - boots, but then I am not able to reboot it. + I have an Intel NUC NUC5CPYH. This is the unit: + http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html + + It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with + linux-image-3.19.0-34-generic -- but when I try to boot with linux- + image-4.2.0-19-generic on the latest PY0044 BIOS version, it does not + boot at all. If I downgrade the BIOS to PY0043, it boots, but then I am + not able to reboot it. When I run "reboot", it freezes showing this screen: https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 I am also attaching the full syslog, dmesg and the relevant part of the syslog when the system froze. Any ideas? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 15.10 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG= SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Description changed: - I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu - 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with - linux-image-4.2.0-19-generic I simply see the following: + I have an Intel NUC NUC5CPYH. This is the unit: + http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html + + It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux- + image-3.19.0-34-generic -- but when I try to boot with linux- + image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( - I tried installing a clean 15.10 version on a blank hard drive (with debootstrap so latest packages) I am able to boot if I add systemd.unit=emergency.target to the kernel line. I can run "systemctl start networking" for example and it works, but if I run "systemctl start apport" (or ssh even) - I see this and the system freezes: https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the failed boot :( Any suggestions? - EDIT: It seems downgrading from the latest PY0044 BIOS version to PY0043 allows me to boot the system, but it freezes if running "reboot" - more details in this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528794/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528792/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528797/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528796/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Attachment added: "Full unaltered syslog from old (working) BIOS" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+attachment/4528798/+files/syslog-PY0043.txt ** Description changed: - This bug is related to this bug: + This bug might be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 - If downgrading the BIOS from PY0044 to PY0043. I am able to get the NUC - to boot. But it does not reboot if running "reboot". + I have a NUC NUC5CPYH. It boots and reboots beautifully on Ubuntu 15.04 + and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to + boot with linux-image-4.2.0-19-generic on the latest PY0044 version, it + does not boot at all. If I downgrade the BIOS to PY0043, it boots, but + then I am not able to reboot it. - It freezes showing this screen: + When I run "reboot", it freezes showing this screen: https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 - I am also attaching the full syslog, dmesg and the relevant part of the syslog showing the freeze asking to reboot. - --- - AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.2.0-19-generic. - AplayDevices: Error: [Errno 2] No such file or directory + I am also attaching the full syslog, dmesg and the relevant part of the + syslog showing the freeze asking to reboot. + + Any ideas? + + --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 - ArecordDevices: Error: [Errno 2] No such file or directory - AudioDevicesInUse: 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 DistroRelease: Ubuntu 15.10 - Lspci: Error: [Errno 2] No such file or directory - Lsusb: Error: [Errno 2] No such file or directory - Package: linux (not installed) - PciMultimedia: - + ProcEnviron: - TERM=linux - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG= - SHELL=/bin/bash + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG= + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: - linux-restricted-modules-4.2.0-19-generic N/A - linux-backports-modules-4.2.0-19-generic N/A - linux-firmware1.149.3 + linux-restricted-modules-4.2.0-19-generic N/A + linux-backports-modules-4.2.0-19-generic N/A + linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
I am able to boot the system if I downgrade the BIOS to PY0043 from PY0044. However there are still side effects that are not present on linux-image-3.19.0-34-generic - for instance, I cannot reboot the system. More details in this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528791/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528793/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528795/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528787/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528786/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528790/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Attachment added: "Syslog showing the point of system freeze when asking to reboot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+attachment/4528785/+files/syslog-reboot-freeze-PY0043.txt ** Tags added: apport-collected wily ** Description changed: This bug is related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 If downgrading the BIOS from PY0044 to PY0043. I am able to get the NUC to boot. But it does not reboot if running "reboot". It freezes showing this screen: https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 - I am also attaching the full syslog, dmesg and the relevant part of the - syslog showing the freeze asking to reboot. + I am also attaching the full syslog, dmesg and the relevant part of the syslog showing the freeze asking to reboot. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.2.0-19-generic. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: 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 + DistroRelease: Ubuntu 15.10 + Lspci: Error: [Errno 2] No such file or directory + Lsusb: Error: [Errno 2] No such file or directory + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG= + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 + ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 + RelatedPackageVersions: + linux-restricted-modules-4.2.0-19-generic N/A + linux-backports-modules-4.2.0-19-generic N/A + linux-firmware1.149.3 + RfKill: Error: [Errno 2] No such file or directory + Tags: wily + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 4.2.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/04/2015 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 + dmi.board.name: NUC5CPYB + dmi.board.vendor: Intel Corporation + dmi.board.version: H61145-404 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
Dmesg on booted system with old BIOS version (does not boot with latest BIOS version) ** Attachment added: "Dmesg on booted system with old BIOS version (does not boot with latest BIOS version)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+attachment/4528784/+files/dmesg-PY0043.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528788/+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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1522201/+attachment/4528789/+files/Card0.Codecs.codec.2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] [NEW] NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
Public bug reported: This bug might be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 I have a NUC NUC5CPYH. It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic on the latest PY0044 BIOS version, it does not boot at all. If I downgrade the BIOS to PY0043, it boots, but then I am not able to reboot it. When I run "reboot", it freezes showing this screen: https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 I am also attaching the full syslog, dmesg and the relevant part of the syslog when the system froze. Any ideas? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 15.10 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG= SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Description changed: This bug might be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 I have a NUC NUC5CPYH. It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to - boot with linux-image-4.2.0-19-generic on the latest PY0044 version, it - does not boot at all. If I downgrade the BIOS to PY0043, it boots, but - then I am not able to reboot it. + boot with linux-image-4.2.0-19-generic on the latest PY0044 BIOS + version, it does not boot at all. If I downgrade the BIOS to PY0043, it + boots, but then I am not able to reboot it. When I run "reboot", it freezes showing this screen: https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 I am also attaching the full syslog, dmesg and the relevant part of the - syslog showing the freeze asking to reboot. + syslog when the system froze. Any ideas? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 15.10 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG= SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: ** 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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( - I tried installing a clean 15.10 version on a blank hard drive (with debootstrap so latest packages) I am able to boot if I add systemd.unit=emergency.target to the kernel line. I can run "systemctl start networking" for example and it works, but if I run "systemctl start apport" (or ssh even) - I see this and the system freezes: https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the failed boot :( Any suggestions? + + - EDIT: It seems downgrading from the latest PY0044 BIOS version to + PY0043 allows me to boot the system, but it freezes if running "reboot" + - more details in this bug report: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( - I tried installing a clean 15.10 version on a blank hard drive (with debootstrap so latest packages) I am able to boot if I add systemd.unit=emergency.target to the kernel - line. If I run "systemctl start sshd" (or apport even) - I see this and - the system freezes: + line. I can run "systemctl start networking" for example and it works, + but if I run "systemctl start apport" (or ssh even) - I see this and the + system freezes: https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the failed boot :( Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Summary changed: - NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) + NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528223/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528222/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528216/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
** 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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] [NEW] NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
Public bug reported: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" - I tried disabling devices in the bios like audio I am not sure how to troubleshoot. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 15.10 4.2.0 linux nuc nuc5cpyh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. - - Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg installed. + Here is output from lspci -vnvn < http://pastie.org/10596250 - I am + running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" - I tried disabling devices in the bios like audio I am not sure how to troubleshoot. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? ** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - - I tried adding GRUB_CMDLINE_LINUX="nomodeset" + - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (as well as noacpi and noapic) - I tried disabling devices in the bios like audio I am not sure how to troubleshoot. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? ** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (as well as noacpi and noapic) + - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio I am not sure how to troubleshoot. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528215/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528219/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528220/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528217/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528218/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
apport information ** Tags added: apport-collected wily ** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio I am not sure how to troubleshoot. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Dec 1 20:34 seq + crw-rw 1 root audio 116, 33 Dec 1 20:34 timer + AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.19.0-34-generic. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 15.10 + IwConfig: + eth0 no wireless extensions. + + tap0 no wireless extensions. + + lono wireless extensions. + JournalErrors: + No journal files were found. + -- No entries -- + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0a2a Intel Corp. + Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub + Bus 001 Device 002: ID 046d:c315 Logitech, Inc. Classic Keyboard 200 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-34-generic root=UUID=d9294595-7978-4fd1-b911-a23cf894cf7d ro nomodeset + ProcVersionSignature: Ubuntu 3.19.0-34.39-generic 3.19.8-ckt7 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-34-generic N/A + linux-backports-modules-3.19.0-34-generic N/A + linux-firmware 1.149.3 + RfKill: Error: [Errno 2] No such file or directory + Tags: wily + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-34-generic x86_64 + UpgradeStatus: Upgraded to wily on 2015-12-01 (0 days ago) + UserGroups: audio dialout sudo video + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 09/25/2015 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: PYBSWCEL.86A.0044.2015.0925.1143 + dmi.board.name: NUC5CPYB + dmi.board.vendor: Intel Corporation + dmi.board.version: H61145-404 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0044.2015.0925.1143:bd09/25/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528214/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528221/+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/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] UserAsoundrc.txt
apport information ** Attachment added: "UserAsoundrc.txt" https://bugs.launchpad.net/bugs/1521749/+attachment/4528224/+files/UserAsoundrc.txt ** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio - I am not sure how to troubleshoot. When I reboot and select Kernel 3.19, - there is nothing in /var/log/syslog from the failed boot :( + If I select "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from + the list, it boots into the recovery console + + I am not sure how to troubleshoot further. When I reboot and select + Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? - --- - AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Dec 1 20:34 seq - crw-rw 1 root audio 116, 33 Dec 1 20:34 timer - AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.19.0-34-generic. - AplayDevices: Error: [Errno 2] No such file or directory - ApportVersion: 2.19.1-0ubuntu5 - Architecture: amd64 - ArecordDevices: Error: [Errno 2] No such file or directory - DistroRelease: Ubuntu 15.10 - IwConfig: - eth0 no wireless extensions. - - tap0 no wireless extensions. - - lono wireless extensions. - JournalErrors: - No journal files were found. - -- No entries -- - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 8087:0a2a Intel Corp. - Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub - Bus 001 Device 002: ID 046d:c315 Logitech, Inc. Classic Keyboard 200 - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Package: linux (not installed) - ProcFB: - - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-34-generic root=UUID=d9294595-7978-4fd1-b911-a23cf894cf7d ro nomodeset - ProcVersionSignature: Ubuntu 3.19.0-34.39-generic 3.19.8-ckt7 - RelatedPackageVersions: - linux-restricted-modules-3.19.0-34-generic N/A - linux-backports-modules-3.19.0-34-generic N/A - linux-firmware 1.149.3 - RfKill: Error: [Errno 2] No such file or directory - Tags: wily - UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' - Uname: Linux 3.19.0-34-generic x86_64 - UpgradeStatus: Upgraded to wily on 2015-12-01 (0 days ago) - UserGroups: audio dialout sudo video - WifiSyslog: - - _MarkForUpload: True - dmi.bios.date: 09/25/2015 - dmi.bios.vendor: Intel Corp. - dmi.bios.version: PYBSWCEL.86A.0044.2015.0925.1143 - dmi.board.name: NUC5CPYB - dmi.board.vendor: Intel Corporation - dmi.board.version: H61145-404 - dmi.chassis.type: 3 - dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0044.2015.0925.1143:bd09/25/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio If I select "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( -- or rather it appears intermittent, sometimes it boots, most of the time it does not. + I am able to boot if I add systemd.unit=emergency.target to the kernel + line. If I run "systemctl start sshd" - I see this and the system + freezes: + + https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 + I am not sure how to troubleshoot further. When I reboot and select - Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( + Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the + failed boot :( Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio If I select "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( -- or rather it appears intermittent, sometimes it boots, most of the time it does not. I am able to boot if I add systemd.unit=emergency.target to the kernel - line. If I run "systemctl start sshd" - I see this and the system - freezes: + line. If I run "systemctl start sshd" (or apport even) - I see this and + the system freezes: https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the failed boot :( Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio If I select "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from - the list, it boots into the recovery console + the list, it does not boot into the recovery console either :( -- or + rather it appears intermittent, sometimes it boots, most of the time it + does not. I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog from the failed boot :( Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521749] Re: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10)
** Description changed: I have a NUC NUC5CPYH. It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux-image-4.2.0-19-generic I simply see the following: https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0 The keyboard stops responding after this line: systemd[1]: Started udev Kernel Device Manager. Here is output from lspci -vnvn < http://pastie.org/10596250 - I am running headless, so there is no Xorg (or any other X server) installed. - I tried updating the NUC bios to the latest (PY0044) - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic) - I tried disabling devices in the bios like audio - - If I select "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from - the list, it does not boot into the recovery console either :( -- or - rather it appears intermittent, sometimes it boots, most of the time it - does not. + - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from the list, it does not boot into the recovery console either :( + - I tried installing a clean 15.10 version on a blank hard drive (with debootstrap so latest packages) I am able to boot if I add systemd.unit=emergency.target to the kernel line. If I run "systemctl start sshd" (or apport even) - I see this and the system freezes: https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0 I am not sure how to troubleshoot further. When I reboot and select Kernel 3.19, there is nothing in /var/log/syslog or journalctl from the failed boot :( Any suggestions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521749 Title: NUC NUC5CPYH Does not boot on 4.2.0-19 (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Any temporary solution in the mean time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509769 Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458323] Re: Asterisk crashes with default install because of pjsip
I noticed after a recent apt-get dist-upgrade asterisk stopped working. Thank you for the workaround, I added noload = res_pjsip.so to /etc/asterisk/modules.conf and now it starts again. There are still a bunch of warnings in the log however, e.g.: [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_refer.so': /usr/lib/asterisk/modules/res_pjsip_refer.so: undefined symbol: ast_copy_pj_str [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_refer.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_transport_websocket.so': /usr/lib/asterisk/modules/res_pjsip_transport_websocket.so: undefined symbol: ast_sip_create_serializer [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_transport_websocket.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_acl.so': /usr/lib/asterisk/modules/res_pjsip_acl.so: undefined symbol: ast_copy_pj_str [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_acl.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_pidf_digium_body_supplement.so': /usr/lib/asterisk/modules/res_pjsip_pidf_digium_body_supplement.so: undefined symbol: ast_sip_presence_xml_create_node [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_pidf_digium_body_supplement.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_messaging.so': /usr/lib/asterisk/modules/res_pjsip_messaging.so: undefined symbol: ast_sip_default_outbound_endpoint [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_messaging.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_authenticator_digest.so': /usr/lib/asterisk/modules/res_pjsip_authenticator_digest.so: undefined symbol: ast_sip_unregister_authenticator [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_authenticator_digest.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_registrar.so': /usr/lib/asterisk/modules/res_pjsip_registrar.so: undefined symbol: ast_sip_report_mem_limit [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_registrar.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_multihomed.so': /usr/lib/asterisk/modules/res_pjsip_multihomed.so: undefined symbol: ast_sip_get_pjsip_endpoint [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_multihomed.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_endpoint_identifier_anonymous.so': /usr/lib/asterisk/modules/res_pjsip_endpoint_identifier_anonymous.so: undefined symbol: ast_copy_pj_str [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_endpoint_identifier_anonymous.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_phoneprov_provider.so': /usr/lib/asterisk/modules/res_pjsip_phoneprov_provider.so: undefined symbol: ast_sip_get_pjsip_endpoint [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_phoneprov_provider.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_header_funcs.so': /usr/lib/asterisk/modules/res_pjsip_header_funcs.so: undefined symbol: ast_sip_session_register_supplement [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_header_funcs.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_one_touch_record_info.so': /usr/lib/asterisk/modules/res_pjsip_one_touch_record_info.so: undefined symbol: ast_sip_session_register_supplement -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1458323 Title: Asterisk crashes with default install because of pjsip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1458323/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458323] Re: Asterisk crashes with default install because of pjsip
I noticed after a recent apt-get dist-upgrade asterisk stopped working. Thank you for the workaround, I added noload = res_pjsip.so to /etc/asterisk/modules.conf and now it starts again. There are still a bunch of warnings in the log however, e.g.: [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_refer.so': /usr/lib/asterisk/modules/res_pjsip_refer.so: undefined symbol: ast_copy_pj_str [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_refer.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_transport_websocket.so': /usr/lib/asterisk/modules/res_pjsip_transport_websocket.so: undefined symbol: ast_sip_create_serializer [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_transport_websocket.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_acl.so': /usr/lib/asterisk/modules/res_pjsip_acl.so: undefined symbol: ast_copy_pj_str [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_acl.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_pidf_digium_body_supplement.so': /usr/lib/asterisk/modules/res_pjsip_pidf_digium_body_supplement.so: undefined symbol: ast_sip_presence_xml_create_node [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_pidf_digium_body_supplement.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_messaging.so': /usr/lib/asterisk/modules/res_pjsip_messaging.so: undefined symbol: ast_sip_default_outbound_endpoint [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_messaging.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_authenticator_digest.so': /usr/lib/asterisk/modules/res_pjsip_authenticator_digest.so: undefined symbol: ast_sip_unregister_authenticator [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_authenticator_digest.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_registrar.so': /usr/lib/asterisk/modules/res_pjsip_registrar.so: undefined symbol: ast_sip_report_mem_limit [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_registrar.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_multihomed.so': /usr/lib/asterisk/modules/res_pjsip_multihomed.so: undefined symbol: ast_sip_get_pjsip_endpoint [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_multihomed.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_endpoint_identifier_anonymous.so': /usr/lib/asterisk/modules/res_pjsip_endpoint_identifier_anonymous.so: undefined symbol: ast_copy_pj_str [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_endpoint_identifier_anonymous.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_phoneprov_provider.so': /usr/lib/asterisk/modules/res_pjsip_phoneprov_provider.so: undefined symbol: ast_sip_get_pjsip_endpoint [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_phoneprov_provider.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_header_funcs.so': /usr/lib/asterisk/modules/res_pjsip_header_funcs.so: undefined symbol: ast_sip_session_register_supplement [Jun 24 09:24:06] WARNING[24844] loader.c: Module 'res_pjsip_header_funcs.so' could not be loaded. [Jun 24 09:24:06] WARNING[24844] loader.c: Error loading module 'res_pjsip_one_touch_record_info.so': /usr/lib/asterisk/modules/res_pjsip_one_touch_record_info.so: undefined symbol: ast_sip_session_register_supplement -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458323 Title: Asterisk crashes with default install because of pjsip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1458323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382707] Re: trusty-utopic non-interactive upgrade outputs garbage, and is interactive
Created a topic thread about this looking for possible workarounds: http://ubuntuforums.org/showthread.php?t=2265877 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382707 Title: trusty-utopic non-interactive upgrade outputs garbage, and is interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/1382707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382707] Re: trusty-utopic non-interactive upgrade outputs garbage, and is interactive
It seems this is still an issue, I am tailing apt-term.log and I see: Configuration file '/etc/sysctl.conf'^M == Modified (by you or by a script) since installation.^M == Package distributor has shipped an updated version.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** sysctl.conf (Y/I/N/O/D/Z) [default=N] ? This should never happen as I am running: do-release-upgrade -f DistUpgradeViewNonInteractive Any workarounds or fixes for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382707 Title: trusty-utopic non-interactive upgrade outputs garbage, and is interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/1382707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
