[Bug 1656064] Re: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups-filters (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656064 Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1656064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660052]
*** This bug is a duplicate of bug 541595 *** https://bugs.launchpad.net/bugs/541595 "[Bug 660052] Re: package gnome-nettool 2.30.0-0ubuntu1 failed to install/upgrade: ErrorMessage: package gnome-nettool is already installed and configured" Troels doc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660052 Title: package gnome-nettool 2.30.0-0ubuntu1 failed to install/upgrade: ErrorMessage: package gnome-nettool is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/660052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652876] Re: No proprietary driver available for NVIDIA [10de:13b4]
** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652876 Title: No proprietary driver available for NVIDIA [10de:13b4] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1652876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Is there any reason the lines creating the menu entry can't just be removed? https://bazaar.launchpad.net/~vcs-imports/network-manager- applet/git-master/view/head:/src/applet.c#L1322 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656486] Re: installer crashed while attempting write grub to disk
I did some more testing. The bug was the result of the flash drive I used rather than any of the hard drives. After some additional drives from other brands I was still getting this error. I rebooted from a live CD instead and was able to install and I did not get any errors when running gparted. Consider this issue resolved (unless someone wants to try and resolve the USB flash drive issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656486 Title: installer crashed while attempting write grub to disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1656486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
I think you meant https://codereview.qt-project.org/182310 (not 182307). Thanks for the patch anyway! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135624] Re: libapache2-mod-php5 should provide LAMP test page
** Changed in: php5 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/135624 Title: libapache2-mod-php5 should provide LAMP test page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/135624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656492] [NEW] package vim-runtime 2:7.4.1689-3ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/doc/tags', which is also in package vim-tiny 2:7.4.1689-3ubuntu1.2
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-runtime 2:7.4.1689-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Jan 11 08:50:44 2017 ErrorMessage: trying to overwrite '/usr/share/vim/vim74/doc/tags', which is also in package vim-tiny 2:7.4.1689-3ubuntu1.2 InstallationDate: Installed on 2016-12-21 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.15ubuntu0.2 SourcePackage: vim Title: package vim-runtime 2:7.4.1689-3ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/doc/tags', which is also in package vim-tiny 2:7.4.1689-3ubuntu1.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656492 Title: package vim-runtime 2:7.4.1689-3ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/doc/tags', which is also in package vim-tiny 2:7.4.1689-3ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1656492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656491] [NEW] please remove libmokoui2 from Ubuntu
Public bug reported: No reverse dependencies. Upstream hasn't been touched in years, and the package isn't being actively maintained in Ubuntu. ** Affects: libmokoui2 (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/1656491 Title: please remove libmokoui2 from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmokoui2/+bug/1656491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574347] Re: [SRU] Re-read the link type if the name changed
larabi: I came from Fedora, and I had been running it for the last releases on my laptop. Never had any WiFi issues, so there's not anything wrong with my hardware. I recently installed Ubuntu 16.04.1 LTS, but these WiFi issues are quite annoying and I'm contemplating switching back to Fedora. I don't understand how this still hasn't been fixed in an LTS version of the OS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: [SRU] Re-read the link type if the name changed To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
** Description changed: The following log comes from the installer syslog file. Since at least - Dec.16th a message is present in all variants of Ubuntu on startup. - Since then, in BIOS mode, all installers have opened in try Ubuntu. + Dec.16th a message is present in all variants of Ubuntu on startup + (ubiquity). Since then, in BIOS mode, all installers have opened in try + Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog - … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… - I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. - --- + --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently
[Bug 1655123] Re: Kernel 4.10 stalls on restart
Journal of errors can be seen is this bug #1656489 for the same installation. Sorry for sending info from the non-sudoer account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
apport information ** Description changed: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nopasswdlogin _MarkForUpl
[Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
Journal from admin account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656489 Title: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656489] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1656489/+attachment/4804160/+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/1656489 Title: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656489] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1656489/+attachment/4804158/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656489 Title: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656489] [NEW] AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
Public bug reported: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nopasswdlogin _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected bios mode ubiquity zesty ** Tags added: apport
[Bug 1656488] [NEW] Ubuntu 16.04.1 failed to install on Intel with XFS filesystem
Public bug reported: Ubuntu 16.04.1 failed to install on Intel with XFS filesystem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 Date: Fri Jan 13 23:32:54 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.2 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656488 Title: Ubuntu 16.04.1 failed to install on Intel with XFS filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1656488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656486] [NEW] installer crashed while attempting write grub to disk
Public bug reported: I connected a clean new hard disk to my new laptop and during the install, specifically when it tried to write grub to the disk, the installer crashes. I investigated a bit more by replacing the disk with an identical new disk thinking maybe the disk was bad. Same thing happened. I then ran gparted and got this error: When I run gparted it reports "The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes." ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Sat Jan 14 00:20:17 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-16.10.14 yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656486 Title: installer crashed while attempting write grub to disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1656486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
This bug was fixed in the package pollinate - 4.24-0ubuntu2 --- pollinate (4.24-0ubuntu2) zesty; urgency=medium * Add missing dependency on xxd. (LP: #1656484) -- Stefano Rivera Sat, 14 Jan 2017 14:41:35 +1100 ** Changed in: pollinate (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443042] Re: every time I remove ghc packages hoogle is downloaded
[Expired for haskell-hoogle (Ubuntu) because there has been no activity for 60 days.] ** Changed in: haskell-hoogle (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443042 Title: every time I remove ghc packages hoogle is downloaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haskell-hoogle/+bug/1443042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622548] Re: package vlc-nox 2.2.2-5 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
[Expired for vlc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vlc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622548 Title: package vlc-nox 2.2.2-5 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1622548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602941] Re: Draw cannot be loaded in 16.04 (Repackage needed since gcl has changed?)
Thanks Brian, that sounds like an accident. (-nc is only a good idea if you haven't picked up junk). Uploaded it again. ** Patch added: "maxima_5.37.2-8ubuntu0.16.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1602941/+attachment/4804144/+files/maxima_5.37.2-8ubuntu0.16.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602941 Title: Draw cannot be loaded in 16.04 (Repackage needed since gcl has changed?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1602941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640558] Re: 16.10 Backup Failure.
[Expired for duplicity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: duplicity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640558 Title: 16.10 Backup Failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1640558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640926] Re: Touchpad doesn't work after upgrading kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640926 Title: Touchpad doesn't work after upgrading kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639814] Re: nginx package upgrade on ubuntu 14.04 rewrites ssl config
[Expired for nginx (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nginx (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639814 Title: nginx package upgrade on ubuntu 14.04 rewrites ssl config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1639814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641280] Re: Issues on include/linux/aer.h
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641280 Title: Issues on include/linux/aer.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641580] Re: Errno 5
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641580 Title: Errno 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1641580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640789] Re: upgrade from 14.04 to 16.04 broke
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640789 Title: upgrade from 14.04 to 16.04 broke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1640789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641226] Re: ubuntu-minimal not found
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641226 Title: ubuntu-minimal not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1641226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640941] Re: unable to find ubuntu-minimal
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640941 Title: unable to find ubuntu-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1640941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641317] Re: Multiple issues on include/linux/audit.h
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641317 Title: Multiple issues on include/linux/audit.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641317/+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
Unfortunately, all of mine have upgraded, but I only rebooted one of them - and hoping the others will keep running until a fix is out. Or do anyone know a step by step solution for this, that wont prevent further updates later, ref: https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1652270/comments/10. Thanks! -- 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 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen
** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635447 Title: Upgraded or Live USB 16.10 hangs at boot up blank purple screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
** Patch added: "pollinate_4.23-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+attachment/4804142/+files/pollinate_4.23-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
** Patch added: "pollinate_4.23-0ubuntu1~14.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+attachment/4804141/+files/pollinate_4.23-0ubuntu1~14.04.1.debdiff ** Also affects: pollinate (Ubuntu Yakkety) 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/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
** Description changed: == SRU Impact == Pretty minimal, adding a dependency to a shell script. == Regression Potential == xxd has presumably already available on machines that have pollinate, or it'd have been reported by now. VIM is rather ubiquitous... So, this is - unlikely to have any effect for most users. And for the rest, it'll just - make pollinate start to work. + unlikely to have any effect for most users. + + For the rest, things are a little more fun: + vim-common Recommends: vim | vim-gnome | vim-gtk | vim-gtk3 | vim-athena | vim-nox | vim-tiny + So, upgraders will get a full-blown vim pulled in. They'll also get a working pollinate. == Test Case == In a minimal chroot, without vim-common & xxd: # pollinate BAD: <13>Jan 14 03:34:27 pollinate[9317]: client sent challenge to [https://entropy.ubuntu.com/] <13>Jan 14 03:34:28 pollinate[9317]: client verified challenge/response with [https://entropy.ubuntu.com/] /usr/bin/pollinate: 79: /usr/bin/pollinate: xxd: not found GOOD: <13>Jan 14 03:49:29 pollinate[22771]: client sent challenge to [https://entropy.ubuntu.com/] <13>Jan 14 03:49:31 pollinate[22771]: client verified challenge/response with [https://entropy.ubuntu.com/] <13>Jan 14 03:49:31 pollinate[22771]: client hashed response from [https://entropy.ubuntu.com/] <13>Jan 14 03:49:31 pollinate[22771]: client successfully seeded [/dev/urandom] - == Original report == # journalctl | grep pollinate Jan 13 10:48:21 plato pollinate[1601]: client sent challenge to [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1626]: client verified challenge/response with [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1564]: /usr/bin/pollinate: 80: /usr/bin/pollinate: xxd: not found Jan 13 10:48:22 plato systemd[1]: pollinate.service: Main process exited, code=exited, status=127/n/a Jan 13 10:48:22 plato systemd[1]: pollinate.service: Unit entered failed state. Jan 13 10:48:22 plato systemd[1]: pollinate.service: Failed with result 'exit-code'. # dpkg -l | grep pollina ii pollinate 4.23-0ubuntu1~16.04 all seed the pseudo random number generator # lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ** Patch added: "pollinate_4.23-0ubuntu1~16.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+attachment/4804140/+files/pollinate_4.23-0ubuntu1~16.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen
@Joseph, I've installed v4.10-rc3 via Ukuu and my laptop boots up successfully. ~$ uname -a Linux chengdu 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Everything seems work normal, even though I noticed some message about b43, but the WIFI works fine too. ~$ dmesg | grep b43 [ 21.933153] Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1 [ 21.933350] b43: probe of bcma0:1 failed with error -524 Thank you for your help. ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => Confirmed ** 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/1635447 Title: Upgraded or Live USB 16.10 hangs at boot up blank purple screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652486] Re: mesa gpu lockup
** Changed in: mesa (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652486 Title: mesa gpu lockup To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1652486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633725] Re: [resolved upstream] Mnemosyne fails to start in Yakkety due to missing PyQt4-WebKit
** Changed in: mnemosyne (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633725 Title: [resolved upstream] Mnemosyne fails to start in Yakkety due to missing PyQt4-WebKit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1633725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576762] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576762 Title: package initramfs-tools 0.122ubuntu8 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/1576762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
** Also affects: pollinate (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: + == SRU Impact == + + Pretty minimal, adding a dependency to a shell script. + + == Regression Potential == + + xxd has presumably already available on machines that have pollinate, or + it'd have been reported by now. VIM is rather ubiquitous... So, this is + unlikely to have any effect for most users. And for the rest, it'll just + make pollinate start to work. + + == Test Case == + + In a minimal chroot, without vim-common & xxd: + + # pollinate + <13>Jan 14 03:34:27 pollinate[9317]: client sent challenge to [https://entropy.ubuntu.com/] + <13>Jan 14 03:34:28 pollinate[9317]: client verified challenge/response with [https://entropy.ubuntu.com/] + /usr/bin/pollinate: 79: /usr/bin/pollinate: xxd: not found + + == Original report == + # journalctl | grep pollinate Jan 13 10:48:21 plato pollinate[1601]: client sent challenge to [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1626]: client verified challenge/response with [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1564]: /usr/bin/pollinate: 80: /usr/bin/pollinate: xxd: not found Jan 13 10:48:22 plato systemd[1]: pollinate.service: Main process exited, code=exited, status=127/n/a Jan 13 10:48:22 plato systemd[1]: pollinate.service: Unit entered failed state. Jan 13 10:48:22 plato systemd[1]: pollinate.service: Failed with result 'exit-code'. # dpkg -l | grep pollina ii pollinate 4.23-0ubuntu1~16.04 all seed the pseudo random number generator - # lsb_release -rd + # lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ** No longer affects: pollinate (Ubuntu Yakkety) ** Description changed: == SRU Impact == Pretty minimal, adding a dependency to a shell script. == Regression Potential == xxd has presumably already available on machines that have pollinate, or it'd have been reported by now. VIM is rather ubiquitous... So, this is unlikely to have any effect for most users. And for the rest, it'll just make pollinate start to work. == Test Case == In a minimal chroot, without vim-common & xxd: # pollinate + + BAD: <13>Jan 14 03:34:27 pollinate[9317]: client sent challenge to [https://entropy.ubuntu.com/] <13>Jan 14 03:34:28 pollinate[9317]: client verified challenge/response with [https://entropy.ubuntu.com/] /usr/bin/pollinate: 79: /usr/bin/pollinate: xxd: not found + + GOOD: + <13>Jan 14 03:49:29 pollinate[22771]: client sent challenge to [https://entropy.ubuntu.com/] + <13>Jan 14 03:49:31 pollinate[22771]: client verified challenge/response with [https://entropy.ubuntu.com/] + <13>Jan 14 03:49:31 pollinate[22771]: client hashed response from [https://entropy.ubuntu.com/] + <13>Jan 14 03:49:31 pollinate[22771]: client successfully seeded [/dev/urandom] + == Original report == # journalctl | grep pollinate Jan 13 10:48:21 plato pollinate[1601]: client sent challenge to [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1626]: client verified challenge/response with [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1564]: /usr/bin/pollinate: 80: /usr/bin/pollinate: xxd: not found Jan 13 10:48:22 plato systemd[1]: pollinate.service: Main process exited, code=exited, status=127/n/a Jan 13 10:48:22 plato systemd[1]: pollinate.service: Unit entered failed state. Jan 13 10:48:22 plato systemd[1]: pollinate.service: Failed with result 'exit-code'. # dpkg -l | grep pollina ii pollinate 4.23-0ubuntu1~16.04 all seed the pseudo random number generator # lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 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/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656484] [NEW] /usr/bin/pollinate uses xxd but does not depend on vim-common
Public bug reported: == SRU Impact == Pretty minimal, adding a dependency to a shell script. == Regression Potential == xxd has presumably already available on machines that have pollinate, or it'd have been reported by now. VIM is rather ubiquitous... So, this is unlikely to have any effect for most users. And for the rest, it'll just make pollinate start to work. == Test Case == In a minimal chroot, without vim-common & xxd: # pollinate <13>Jan 14 03:34:27 pollinate[9317]: client sent challenge to [https://entropy.ubuntu.com/] <13>Jan 14 03:34:28 pollinate[9317]: client verified challenge/response with [https://entropy.ubuntu.com/] /usr/bin/pollinate: 79: /usr/bin/pollinate: xxd: not found == Original report == # journalctl | grep pollinate Jan 13 10:48:21 plato pollinate[1601]: client sent challenge to [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1626]: client verified challenge/response with [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1564]: /usr/bin/pollinate: 80: /usr/bin/pollinate: xxd: not found Jan 13 10:48:22 plato systemd[1]: pollinate.service: Main process exited, code=exited, status=127/n/a Jan 13 10:48:22 plato systemd[1]: pollinate.service: Unit entered failed state. Jan 13 10:48:22 plato systemd[1]: pollinate.service: Failed with result 'exit-code'. # dpkg -l | grep pollina ii pollinate 4.23-0ubuntu1~16.04 all seed the pseudo random number generator # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 ** Affects: pollinate (Ubuntu) Importance: Undecided Status: New ** Affects: pollinate (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: pollinate (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: pollinate (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: pollinate (Ubuntu Zesty) 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/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
As I'm looking at the data some more, I see in the sos reports provided that there may be heavy pressure for the async I/O and that may actually be what's causing the problems here. In the syslog, I see the following events getting reported from multipathd soon after the the device is discovered (its part of the udev event hooks I believe): Jan 12 22:02:49 ub01 multipathd[179286]: sdch: add path (uevent) Jan 12 22:02:49 ub01 multipathd[179286]: io_setup failed Jan 12 22:02:49 ub01 multipathd[179286]: uevent trigger error The io_setup is a system call into the kernel which can fail for a few different reasons, but one of the reasons it will fail is if the number of async io requests are greater than the current amount. It will error out with an EAGAIN, but there's explicit documentation in the multipath that one of the reasons that the io_setup may fail in this case is due to the settings of the fs.aio-nr-max, which is essentially the maximum number of events for all currently active aio contexts. Checking the value collected I see these values: # Quick check on the box today fs.aio-max-nr = 65536 fs.aio-nr = 124928 # From the sosreport provided on 12/01 fs.aio-max-nr = 65536 fs.aio-nr = 131072 As you can see the aio-nr is well above the aio-max-nr. I'm not entirely sure what is causing this, but there are a large number of async io events queued up. I think the plan of action should be to: a) configure multipath to ignore the iscsi devices presented between cinder and nova b) cleanup any errors in the current paths used by multipath, so that we know that disk i/o to the actul backend is not an issue c) Possibly consider increasing the fs.aio-max-nr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-lowlatency/onza__4.4.0-60.81__2017-01-14_03-20-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640217] Re: python.so plugin fails to load under Zesty
** Changed in: claws-mail (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640217 Title: python.so plugin fails to load under Zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1640217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804137/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] Re: Kernel 4.10 stalls on restart
The bug is also present in bios mode alongside rs1. CKT 4.10.0-1.3 stalls on first restart and magic key works to restart again. As in UEFI mode the HDD is noisy, too noisy to keep it on board. Grub was OK for this test. That ends this bug report. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804135/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804138/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804131/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] Re: Kernel 4.10 stalls on restart
apport information ** Description changed: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 2454 F pulseaudio /dev/snd/controlC0: test 2454 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=fc87eaaa-07c4-4916-9cbd-4a3cb592b160 InstallationDate: Installed on 2017-01-11 (0
[Bug 1655123] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804136/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804130/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804134/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804132/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804129/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655123] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804133/+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/1655123 Title: Kernel 4.10 stalls on restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-lowlatency/onza__4.4.0-60.81__2017-01-14_02-52-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected
The label is pretty faded, so I'm not positive on this. But I think it's: Make: DisplayLink Model: E364109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655828 Title: Mouse flickers and disappears on primary monitor when additional monitor is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/onza__4.4.0-60.81__2017-01-14_02-26-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656451] Re: msttcorefonts installer unable to download Andale font
*** This bug is a duplicate of bug 1607535 *** https://bugs.launchpad.net/bugs/1607535 Duplicate of bug 1607535, that you couldn't find easily because it is itself the duplicate of a bug in apt that doesn't look related at all on first sight. ** This bug has been marked a duplicate of bug 1607535 ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656451 Title: msttcorefonts installer unable to download Andale font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1656451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463120] Re: Failure to boot if fstab disk mounts fail
I've tested this with kernel 4.10-rc3 in a local VirtualBox VM (Ubuntu Server 16.04), with the same fstab error as above, and am able to confirm most of the symptoms described by the reporter. When attempting to 'mount -a', it presents the expected "wrong filesystem type" error, but doesn't render the system unresponsive. Upon reboot, however, it drops into a maintenance console without presenting an error about a failed mount attempt. Consequently, the server would be unreachable for maintenance via SSH. 'journalctl -xb' provides a log that contains an error about the failed mount attempt, but doesn't point to it as the reason for dropping into a maintenance terminal, and it isn't the last thing logged. After fixing fstab (which requires physical access) and rebooting ('reboot' from the maintenance console), GRUB does still have a countdown, but it starts around 10 seconds, instead of 3 seconds (~3 seconds is the default for Ubuntu Server). Otherwise, at this point, the system is able to boot up automatically, without issue. After rebooting a second time (from the normal BASH prompt), the GRUB countdown is back to ~3 seconds, and the system boots normally (automatically), from there. Thanks, again, for helping to resolve this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i9
Looking at the file Christopher linked to earlier states this: "Organization: Intel Open Source Technology Center The Baytrail SOC has a built-in feature to demote core and module C6 to shallower idle states. Based on work in the Android copy of the Linux kernel tree, this feature was disabled starting in Linux-3.17-rc1:" ...So that looks promising as that is the exact thing we found in this bug report early on. Kernel 3.17 was the kernel i started getting huge freezes on, and when originally we were going through the bisecting rc1 was the one we had stopped at. So cool to see someone else has confirmed that portion. ...now to see if i can figure all this stuff Christopher wants me to do. Christopher i'm going to be honest and say that your really bad at explaining stuff since you just post links that are somewhat technical. I think i can figure it out, but my brain doesn't compute as fast as it used to. Right now i gather that i need to just edit my grub on bootup and test the intel_idle.max_cstate=1 parameter. (not sure if that will remain on future bootups or if that is persistent and will remain). Then if that works well i test the debug patch and script. (not sure if i need to disable intel_idle.max_cstate=1 when i do this). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic
I just did the same as John Russel, edited /etc/lsb-release to 16.10, and now it works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312673 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1312673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i9
Christopher, the latest kernels don't freeze as much as the older ones. Do you want me to go back to an older kernel that froze up a lot to test the intel_idle.max_cstate=1 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607535] Re: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts
As proposed in comments 56 57, I have temporarily removed the duplicate status of this bug to un-hide it in the package's bug list, in the hope that people will find it more easily and stop opening new bugs to report this problem. I have updated the description with all the findings made about this bug, in particular its cause, two workarounds, and Julian Klode's work to fix it in bug 1651923. Please improve on this description if you can. Thanks to all the people who contributed to investigating this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607535 Title: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i9
Okay i have just removed Vincent's patched kernel. I will try and proceed and test Christopher's request to follow his steps to test his stuff. Vincent i will add that your patch seemed to work well, though i did have it lock up once. Only once that i can remember though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557753] Re: mate-tweak crashed with psutil.NoSuchProcess in wrapper(): psutil.NoSuchProcess process no longer exists (pid=2537)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557753 Title: mate-tweak crashed with psutil.NoSuchProcess in wrapper(): psutil.NoSuchProcess process no longer exists (pid=2537) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-tweak/+bug/1557753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501010] Re: mate-tweak crashed with GLib.Error in __init__(): gtk-icon-theme-error-quark: Icon 'user-desktop' not present in theme gnome (0)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501010 Title: mate-tweak crashed with GLib.Error in __init__(): gtk-icon-theme- error-quark: Icon 'user-desktop' not present in theme gnome (0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-tweak/+bug/1501010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607535] Re: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts
** Description changed: - As noted in - https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1371783/comments/45, - the current 3.4 version of ttf-mscorefonts-installer searches for the - font files in an incorrect network location. The consequence of this is - that the core fonts are never installed. + [Symptoms] - The Debian (upstream) version 3.6 of ttf-mscorefonts-installer searches - for the font files in the correct network location, and will - successfully install the core fonts. + When installing or updating the package ttf-mscorefonts-installer in + Ubuntu 16.04 or 16.10, an error message appears in a GUI window, + indicating "failure to download extra data files" (the fonts themselves) + "after package installation" (the package itself appears to have been + installed). This error message re-appears regularly, as a cron-job re- + tries the failed download. - This problem occurs with Ubuntu 16.04 as of July 2016. (And with earlier - versions, including current LTS.) + If installing or updating from the command line, additional failure + information is given in an error message prefixed by "E:", but this + error message depends on the mirror server which is contacted for the + download: "404 Not Found" is common, but there is also "Protocol http + not supported or disabled in libcurl", and complains about invalid + Content-Range headers. + + [Cause] + + The current 3.4 version of ttf-mscorefonts-installer in Ubuntu 16.04 + delegates the download of the proprietary Microsoft Core Fonts for the + Web (Andale, Arial...) to the package update-notifier, which itself + delegates it to the program apt-helper provided by the package apt. The + download URL points to the host downloads.sourceforge.net, which + redirects to a randomly-chosen mirror server + .dl.sourceforge.net. + + Unfortunately, the program apt-helper has a bug in the way it treats + redirections. This bug makes apt-helper keep a space in the URL instead + of encoding it to %20 before contacting the mirror. It is more + extensively documented in bug 1655431 and bug 1651923. The mirror + replies to this malformed request with an error message (e.g. "404 Not + Found"), and download fails. + + Some mirrors appear to understand the malformed request nonetheless, and + send the requested font file, however since there are 11 fonts to + download, the chances of getting 11 understanding mirrors are low. Hence + why the error message usually concerns andale32.exe or arial32.exe + instead of webdin32.exe. + + [Workaround 1] + + Download the fonts manually and put them all in the same directory. You + can use wget for that, because contrary to apt-helper, it handles + redirections fine (command line formatted for readability, do not + include line breaks and line indents): + + $ wget http://downloads.sourceforge.net/corefonts/ + {andale32.exe,arial32.exe,arialb32.exe,comic32.exe,courie32.exe, + georgi32.exe,impact32.exe,times32.exe,trebuc32.exe,verdan32.exe, + webdin32.exe} + + Or you can use your browser: point it to + https://sourceforge.net/projects/corefonts/files/the%20fonts/final and + download the same files. + + Make sure the package is purged and no remaining setup triggers are + remaining, using your favorite package manager or command-line APT: + + $ sudo apt-get purge ttf-mscorefonts-installer + + Then reinstall the package, this time pointing to the previously- + downloaded fonts in a second step: + + $ sudo apt-get install ttf-mscorefonts-installer + # (this will most likely fail again) + $ sudo dpkg-reconfigure ttf-mscorefonts-installer + + The second command should return a "graphical" interface in the + terminal. Use it to point to the directory where you downloaded the + fonts (/path/to/directory/containing/the/fonts). Make sure no .deb files + are in this directory, they seem to be picked up too and then it fails. + + If a pop-up shows up for a post-install action later, just let it run, + it shouldn't come back. It may triggered by the file /var/lib/update- + notifier/user.d/data-downloads-failed and you may be successful in + avoiding the regularly-reappearing message by removing this file. But + this point is less clear. + + Once everything is working, you can delete the downloaded fonts in .exe + format, they have been uncompressed and installed in + /usr/share/fonts/truetype/msttcorefonts in .ttf format. + + Adapted from: Vincent Gerris (comment 17), Lesley Binks (comment 18). + + [Workaround 2] + + Remove Ubuntu's version of ttf-mscorefonts-installer and install + Debian's version instead. Indeed, Debian's version uses wget to download + the fonts, and contrary to apt-helper, wget handles redirections fine. + + Download the package from https://packages.debian.org/ttf-mscorefonts- + installer. Version 3.6 has been tested by several users. This workaround + should work with Debian's version 3.4+nmu1 too, but then you'd be + prompted to update to Ubuntu's problema
[Bug 1656084] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/ms10-35-mcdivittB0-kernel__4.4.0-60.81__2017-01-14_01-56-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/onza__4.4.0-60.81__2017-01-14_01-59-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/modoc__4.4.0-60.81__2017-01-14_02-06-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607535] Re: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts
Robin, comment 63: > This package comes originally from Debian, where the current > version is 3.6. That version seems to work without problem, > no matter how ugly it may be in doing so. As a matter of fact, even Debian's version 3.4 works. It works because it uses wget to download the fonts, while Ubuntu's version of the package uses apt-helper, which has a bug, see comments 50 52 by Adrien Beau, and the bug 1655431 he links to, which points to the root cause in bug 1651923. So it's not a case of "version 3.4 is broken, version 3.6 fixes the problem" but a case of "Ubuntu versions of the package are broken, Debian versions of the package work". I do not know why the Ubuntu package was modified in the first place, rather than simply copied from Debian (and I personally wish there were less delta between the two distributions, to avoid these Ubuntu-only bugs). Perhaps we can find out the reasons in the changelog for the Ubuntu package. > An update to the existing 3.6 code would > provide a clean solution Yes and no. On the one hand, using Debian's 3.6 package as-is certainly works, as mentionned in this thread. But the Ubuntu package cannot be updated to pure Debian 3.6 without losing the Ubuntu-specific changes. So the changes made in Debian between 3.4 and 3.6 should instead be merged to the Ubuntu package, for it to benefit from both the features of the new version and the Ubuntu- specific changes. Since one of these Ubuntu-specific changes is using apt-helper instead of wget, the bug would remain. > problem which, as you will have noticed, > affects a very large number of people It affects me too. > Unless someone is going actively to develop and test an updated > package which resolves the problems with version 3.4 Someone is: Julian Klode, see bug 1651923, of which this bug is a duplicate (although I am going to temporarily remove duplicate status, see this bug, comments 56 57). Julian has already released a fix, available in Ubuntu's upcoming 17.04 release, as is the correct procedure. Fixes aren't released directly to production releases, they are first tested in the development release, in case they don't work or cause new bugs. If you can use the development release, please test this package and report in bug 1651923. Feedback will be appreciated and will help the fix to be backported to the production releases. > (As a point of information, this bug also appears with 14.04.) Crap. I was quite sure it was specific to 16.06 and 16.10. Can you give more details? In bug 1651923, bottom of comment 24, Julian Klode mentions that there is a different issue with the downloads on Trusty (14.04). Can you confirm whether you are running into this different issue (download hangs) or the issue discussed in this bug (download fails)? ** This bug is no longer a duplicate of bug 1651923 apt https method decodes redirect locations and sends them to the destination undecoded. ** Tags removed: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607535 Title: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
I also tried to enable hibernation, same issue with NVME drives using hibernation as when using suspend. Skylake truly is a mess on Linux :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656480] [NEW] QEMU Does not Send L2 Broadcasts After Live Migration
Public bug reported: In short: 1) Get two Xenial hosts (instead, could be two lxd containers with QEMU inside or two VMs with nested virtualization enabled - doesn't matter); 1) Create a libvirt domain that uses QEMU (can be a bare instance, even without a disk, with a NIC without an IP address since we are testing L2 broadcasts); 2) Launch an instance; 3) Start listening for RARP packets on the destination host's bridge (QEMU uses a RARP L3 header and a broadcast L2 header which is easy to filter as no other software sends RARPs nowadays); 3) Do virsh migrate --live domain desturi; 4) Observe that no RARP packets are sent. The expected result (QEMU actually sends 5 of those, grep for SELF_ANNOUNCE_ROUNDS == 5 in the sources): sudo tcpdump -e -i br0 rarp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br0, link-type EN10MB (Ethernet), capture size 262144 bytes 18:19:32.460765 52:54:00:25:49:b7 (oui Unknown) > Broadcast, ethertype Reverse ARP (0x8035), length 60: Reverse Request who-is 52:54:00:25:49:b7 (oui Unknown) tell 52:54:00:25:49:b7 (oui Unknown), length 46 18:19:32.504609 52:54:00:25:49:b7 (oui Unknown) > Broadcast, ethertype Reverse ARP (0x8035), length 60: Reverse Request who-is 52:54:00:25:49:b7 (oui Unknown) tell 52:54:00:25:49:b7 (oui Unknown), length --- lsb_release -r Release:16.04 dpkg --status qemu-kvm | grep Version Version: 1:2.5+dfsg-5ubuntu10.6 -- Fortunately, there is already a fix for this: https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg04645.html http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ca1ee3d6b546e841a1b9db413eb8fa09f13a061b;hp=14e60aaece20a1cfc059a69f6491b0899f9257a8 The issue was introduced in fefe2a78abde932e0f340b21bded2c86def1d242: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fefe2a78abde932e0f340b21bded2c86def1d242 $ apt-get source qemu # we are looking at qemu_2.5+dfsg debian branch $ ls qemu*dsc qemu_2.5+dfsg-5ubuntu10.6.dsc $ git remote show origin | grep Fetch Fetch URL: git://anonscm.debian.org/pkg-qemu/qemu.git $ git checkout debian/qemu_2.5+dfsg-5 HEAD is now at aa4dbf2... Uploading version 2.5+dfsg-5 to unstable The commit that introduced the issue is present in qemu_2.5+dfsg-5. $ git merge-base --is-ancestor fefe2a78abde932e0f340b21bded2c86def1d242 HEAD ; echo $? 0 There are no patches for it: grep -RiP 'rarp' qemu-2.5+dfsg/debian/patches/ ; echo $? 1 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: live-migration qemu ** Description changed: In short: 1) Get two Xenial hosts (instead, could be two lxd containers with QEMU inside or two VMs with nested virtualization enabled - doesn't matter); 1) Create a libvirt domain that uses QEMU (can be a bare instance, even without a disk, with a NIC without an IP address since we are testing L2 broadcasts); 2) Launch an instance; 3) Start listening for RARP packets on the destination host's bridge (QEMU uses a RARP L3 header and a broadcast L2 header which is easy to filter as no other software sends RARPs nowadays); 3) Do virsh migrate --live domain desturi; 4) Observe that no RARP packets are sent. - The expected result (QEMU actually sends of those, grep for + The expected result (QEMU actually sends 5 of those, grep for SELF_ANNOUNCE_ROUNDS == 5 in the sources): sudo tcpdump -e -i br0 rarp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br0, link-type EN10MB (Ethernet), capture size 262144 bytes 18:19:32.460765 52:54:00:25:49:b7 (oui Unknown) > Broadcast, ethertype Reverse ARP (0x8035), length 60: Reverse Request who-is 52:54:00:25:49:b7 (oui Unknown) tell 52:54:00:25:49:b7 (oui Unknown), length 46 18:19:32.504609 52:54:00:25:49:b7 (oui Unknown) > Broadcast, ethertype Reverse ARP (0x8035), length 60: Reverse Request who-is 52:54:00:25:49:b7 (oui Unknown) tell 52:54:00:25:49:b7 (oui Unknown), length --- - lsb_release -r + lsb_release -r Release: 16.04 dpkg --status qemu-kvm | grep Version Version: 1:2.5+dfsg-5ubuntu10.6 -- Fortunately, there is already a fix for this: https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg04645.html http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ca1ee3d6b546e841a1b9db413eb8fa09f13a061b;hp=14e60aaece20a1cfc059a69f6491b0899f9257a8 The issue was introduced in fefe2a78abde932e0f340b21bded2c86def1d242: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fefe2a78abde932e0f340b21bded2c86def1d242 - $ apt-get source qemu # we are looking at qemu_2.5+dfsg debian branch $ ls qemu*dsc qemu_2.5+dfsg-5ubuntu10.6.dsc $ git remote show origin | grep Fetch - Fetch URL: git://anonscm.debian.org/pkg-qemu/qemu.git + Fetch URL: git://anonscm.debian.org/pkg-qemu/qemu.git $ git checkout debian/qemu_2.5+dfsg-5 HEAD is now at aa4dbf2... Uploading version 2.5+dfsg-5 to unstable The commit that introduced the issue is present in qemu
[Bug 1656084] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/s2lp3__4.4.0-59.80__2017-01-14_01-36-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] Re: linux: 4.4.0-60.81 -proposed tracker
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/kernel01__4.4.0-59.80__2017-01-14_01-36-00/results-index.html ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly (jpdonnelly) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-60.81 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded + kernel-stable-phase-changed:Saturday, 14. January 2017 01:33 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-60.81 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true derivative-trackers-created: true phase: Uploaded - kernel-stable-phase-changed:Saturday, 14. January 2017 01:33 UTC - kernel-stable-phase:Uploaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565080] Re: ubuntuBSD support
This bug was fixed in the package mesa - 13.0.3-1ubuntu2 --- mesa (13.0.3-1ubuntu2) zesty; urgency=medium * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: #1605796) * control: Fix dependencies for ubuntuBSD. (LP: #1565080) * compat,rules: Don't bump compat to 10, breaks applying patches before autoreconf which we need for the Mir EGL platform. -- Timo Aaltonen Thu, 12 Jan 2017 09:49:20 +0200 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565080 Title: ubuntuBSD support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1565080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605796] Re: mesa FTBFS on ppc64el with -O3 due to ICE
This bug was fixed in the package mesa - 13.0.3-1ubuntu2 --- mesa (13.0.3-1ubuntu2) zesty; urgency=medium * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: #1605796) * control: Fix dependencies for ubuntuBSD. (LP: #1565080) * compat,rules: Don't bump compat to 10, breaks applying patches before autoreconf which we need for the Mir EGL platform. -- Timo Aaltonen Thu, 12 Jan 2017 09:49:20 +0200 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605796 Title: mesa FTBFS on ppc64el with -O3 due to ICE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1605796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655556] Re: intel: add support for 16k wide textures
This bug was fixed in the package mesa - 13.0.3-1ubuntu2 --- mesa (13.0.3-1ubuntu2) zesty; urgency=medium * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: #1605796) * control: Fix dependencies for ubuntuBSD. (LP: #1565080) * compat,rules: Don't bump compat to 10, breaks applying patches before autoreconf which we need for the Mir EGL platform. -- Timo Aaltonen Thu, 12 Jan 2017 09:49:20 +0200 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/166 Title: intel: add support for 16k wide textures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
As I suspected, issue is still present with the 4.10 kernels. Tried it on a separate clean install using 16.10 upgrading the kernel to v4.10-rc3 mainline This warning is present for 4.10 as well as for older kernels on the Alienware 15 R2 update-initramfs: Generating /boot/initrd.img-4.10.0-041000rc3-generic W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 run-parts: executing /etc/kernel/postinst.d/pm-utils 4.10.0-041000rc3-generic /boot/vmlinuz-4.10.0-041000rc3-generic uname -a Linux starbase 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656477] [NEW] package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured
Public bug reported: new update install from tonight I believe.. above reported... there are three separate bugs saying the same thing already installed... OS update I believe. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjson-c2:i386 0.11-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Jan 13 19:52:41 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu5 DuplicateSignature: package:libjson-c2:i386:0.11-4ubuntu2 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libsystemd0:i386 (--configure): package libsystemd0:i386 is already installed and configured ErrorMessage: package libjson-c2:i386 is already installed and configured InstallationDate: Installed on 2017-01-10 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: dpkg Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656477 Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1656477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656474] [NEW] FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
Public bug reported: emacs25 25.1+1-3ubuntu1 reliably fails to build on the LP arm64 buildds. I wasn't able to reproduce this on bare metal but, while trying to simulate the buildd environment, I have found that it does *sometimes* occur when building in a KVM VM on an X-Gene system. #0 __flockfile (stream=0x0) at ../sysdeps/pthread/flockfile.c:28 #1 0x004e0cc4 in terminate_due_to_signal (sig=sig@entry=11, backtrace_limit=backtrace_limit@entry=40) at emacs.c:381 #2 0x004f74f8 in handle_fatal_signal (sig=sig@entry=11) at sysdep.c:1601 #3 0x004f7734 in deliver_thread_signal (sig=sig@entry=11, handler=0x4f74e8 ) at sysdep.c:1575 #4 0x004f77ac in deliver_fatal_thread_signal (sig=11) at sysdep.c:1613 #5 handle_sigsegv (sig=11, siginfo=, arg=) at sysdep.c:1695 #6 #7 unchain_marker (marker=marker@entry=0x130ad18) at marker.c:605 #8 0x005334a4 in free_marker (marker=marker@entry=19967257) at alloc.c:3850 #9 0x00505b98 in signal_before_change (preserve_ptr=0x0, end_int=44894, start_int=9854976) at insdel.c:2041 #10 prepare_to_modify_buffer_1 (start=start@entry=11223, end=end@entry=11223, preserve_ptr=preserve_ptr@entry=0x0) at insdel.c:1867 [...] ** Affects: emacs25 (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: emacs25 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
** Attachment added: "gdb bt" https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+attachment/4804070/+files/gdb-bt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656476] [NEW] package libxau6:i386 1:1.0.8-1 failed to install/upgrade: package libxau6:i386 is already installed and configured
Public bug reported: new update install from tonight I believe.. above reported... there are three separate bugs saying the same thing already installed... Os updates i believe ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxau6:i386 1:1.0.8-1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 13 19:52:42 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu5 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libxau6:i386:1:1.0.8-1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libsystemd0:i386 (--configure): package libsystemd0:i386 is already installed and configured ErrorMessage: package libxau6:i386 is already installed and configured GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Wrestler [Radeon HD 6310] [1179:fde8] InstallationDate: Installed on 2017-01-10 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655D PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=3fd048ec-4f40-424c-8580-8ccce36f6a06 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: dpkg Title: package libxau6:i386 1:1.0.8-1 failed to install/upgrade: package libxau6:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-007008:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-007008 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 13 16:09:46 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package compiz-0.9 i386 need-duplicate-check ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656476 Title: package libxau6:i386 1:1.0.8-1 failed to install/upgrade: package libxau6:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1656476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
This does not appear to be reproducible w/ pristine upstream 25.1 source built with the following commands: ./autogen.sh CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro" REL_ALLOC=no ./configure --build aarch64-linux-gnu --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --enable-locallisppath=/etc/emacs25:/etc/emacs:/usr/local/share/emacs/25.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/25.1/site-lisp:/usr/share/emacs/site-lisp --with-sound=alsa --build aarch64-linux-gnu --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --enable-locallisppath=/etc/emacs25:/etc/emacs:/usr/local/share/emacs/25.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/25.1/site-lisp:/usr/share/emacs/site-lisp --with-sound=alsa --with-x=yes --with-x-toolkit=gtk3 --with-toolkit-scrol l-bars make -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
** Attachment added: "gdb bt full" https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+attachment/4804071/+files/gdb-bt-full.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656475] [NEW] package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: package libsystemd0:i386 is already installed and configured
Public bug reported: new update install from tonight I believe.. above reported... there are three separate bugs saying the same thing already installed... OS updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsystemd0:i386 229-4ubuntu13 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Jan 13 19:52:41 2017 DuplicateSignature: package:libsystemd0:i386:229-4ubuntu13 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libsystemd0:i386 (--configure): package libsystemd0:i386 is already installed and configured ErrorMessage: package libsystemd0:i386 is already installed and configured InstallationDate: Installed on 2017-01-10 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: dpkg Title: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: package libsystemd0:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656475 Title: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: package libsystemd0:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1656475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656473] [NEW] /usr/bin/evolution:11:g_type_check_instance_is_fundamentally_a:g_object_unref:g_slist_foreach:e_plugin_lib_enable:e_plugin_enable
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution. This problem was most recently seen with package version 3.22.3-0ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/6389fd1d92d657fd9717f3ff20e9dfa92bb6e4a2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: utopic vivid xenial yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656473 Title: /usr/bin/evolution:11:g_type_check_instance_is_fundamentally_a:g_object_unref:g_slist_foreach:e_plugin_lib_enable:e_plugin_enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1656473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637733] Re: freeze on login with prime-select intel
same problem on my laptop: nvidia gtx 960M skylake i7 6700 HQ SSD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637733 Title: freeze on login with prime-select intel To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1637733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656084] Re: linux: 4.4.0-60.81 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly (jpdonnelly) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607535] Re: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts
*** This bug is a duplicate of bug 1651923 *** https://bugs.launchpad.net/bugs/1651923 Jeremy, comment 59: > the next Ubuntu bugfix update for this package (if there is one) > will be numbered something like 3.4+nmu1ubuntu2.1 It would be 3.4+nmu1ubuntu3 I believe. But there will be no new version of this package to fix this bug, as it has to be fixed in another package (apt), not in this package (ttf-mscorefonts-installer). cbcymru, comment 60: > So have those of us who have switched to version 3.6, and there > seem to be many, left our computers vulnerable? Only if there is a security vulnerability in Debian's v3.6 ttf- mscorefonts-installer, and only if it is found... > When the 3.4 version bug is finally fixed how could we switch back > to the fixed version 3.4? I was just wondering about that and it seems as trivial as using dpkg with the "purge" action (-P, --purge) instead of the "install" action (-i, --install): $ dpkg -P /path/to/ttf-mscorefonts-installer_3.6_all.deb And then you'd install the Ubuntu package. Running what Jeremy proposes in comment 61 would also install the Ubuntu package but without uninstalling the Debian package before, and given that these packages have differences, I'd rather be on the safe side and run whatever pre- removal and post-removal scripts are included in the Debian package. cbcymru, comment 62: > If you should discover how to stop the install prompt before > the fix is found, please post the details. Lesley Binks in comment 18 suggests removing the file: /var/lib/update-notifier/user.d/data-downloads-failed which he says triggers the message. Unfortunately he hasn't reported yet if it works and is safe. Also, note that this is in the context of Vincent Gerris's workaround in comment 17, not in the context of using Debian's version 3.6. Obviously, if you don't need Microsoft's Core Fonts, you may just uninstall the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607535 Title: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
** Also affects: chromium-browser Importance: Undecided Status: New ** No longer affects: chromium-browser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512027] Re: open of device pixma:MX7600_... failed: invalid argument
The sane project has already confirmed a fix exists in 1.0.25. Unless you go out and buy a Pixma MX7600, you're not gonna have my hardware whether I run apport or not. The apparent motivation to fix bugs in Ubuntu appears anemic at best already, I don't think I'm going to do much harm to that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512027 Title: open of device pixma:MX7600_... failed: invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651520] Re: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state
Christopher, *-rc versions are the release Candidates, once I installed it (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5) to check the same bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641152) in November and ended up without WiFi. I can't work on *-rc. The bug reproduced after the idle state, laptop lid closing or waking up from the sleeping mode with frequency about once per ~20-30 such actions. The probability seems to be higher when there are more opened windows and external monitor is plugging. In fact, the last 2 issues appeared on plugging the external monitor after the sleep mode. However the bug sometimes (about twice during 4 months) reproduced even on pure laptop without any external devices. I think that you don't have many reports about this bug only because the reporting should be done manually. Moreover, it's extremely hard for an ordinary user to perform such reporting when the UI is totally broken and apport-collect doesn't always success to report even if it was called (as nico mentioned, and I also had the same issue with the apport-collect). --- Info about the kernels: [a few older kernels (< 4.4.0-50) have the UI scrambling issue] -4.4.0-51 - OK: UI scrambling has never occurred, but sometimes (when UI scrambling occurs on another kernels) on this kernel system windows become non-sensitive to the mouse clicks: shortcuts on the desktop are clicked behind the foreground window instead of it. This can be fixed by closing and reopening the window (which does not help on another kernels with the UI scrambling issue). On this kernel the windows can always be moved using the title panel (the top bar of the window) even when the remained part of the [foreground] window is not sensitive (transparent for the mouse clicks). -4.4.0-53, 4.4.0-57, 4.4.0-59 - UI scrambling issue - 4.9.3-040903 - under the evaluation. It survived the stress testing without any issues: intentional subsequent lid closing, laptop suspending and external monitor plugging (up to 20 times). Now is under the "working" testing as my default working kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651520 Title: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656470] [NEW] lxde-common should depend on lxsession-logout
Public bug reported: lxde-common includes logout desktop icon (/usr/share/applications/lxde- logout.desktop) which tries to run lxsession-logout from lxsession- logout package, which is not installed because nor lxde-common, nor lxde not depend on it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxde-common 0.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 14 03:31:08 2017 InstallationDate: Installed on 2014-01-01 (1108 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: lxde-common UpgradeStatus: Upgraded to xenial on 2016-07-28 (169 days ago) ** Affects: lxde-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656470 Title: lxde-common should depend on lxsession-logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxde-common/+bug/1656470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
I have a similar problem with a super micro X10DRH system board. If I have the intel sata controller set to ACHI and install a fresh instance of 16.04 the server works without issue. If I have the intel sata controller in RSTe RAID mode with a 2 drive RAID1 configuration the server will hang on reboot at the 'Reached target shutdown" message. Are there any logs that I can provide to assist in troubleshooting? Thanks, -Matt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs