[Touch-packages] [Bug 1793060] Re: configure_networking uses features not available in initramfs.
** Description changed: initramfs-tools 0.131ubuntu10 modified configure_networking to use - run_dhclient instead of ipconfig. configure_network now fails to + run_dhclient instead of ipconfig. configure_networking now fails to configure networking in the initramfs because it now uses features not available in the initramfs. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe run_dhclient calls dhclient which calls /sbin/dhclient-script. /sbin/dhclient-script calls 'chown --reference=$resolv_conf $new_resolv_conf', but chown isn't available in initramfs /boot/initrd.img-4.18.0-7-generic. /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf $new_resolv_conf' but busybox chmod in the initramfs does not support the option --reference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1793060 Title: configure_networking uses features not available in initramfs. Status in initramfs-tools package in Ubuntu: New Bug description: initramfs-tools 0.131ubuntu10 modified configure_networking to use run_dhclient instead of ipconfig. configure_networking now fails to configure networking in the initramfs because it now uses features not available in the initramfs. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe run_dhclient calls dhclient which calls /sbin/dhclient-script. /sbin/dhclient-script calls 'chown --reference=$resolv_conf $new_resolv_conf', but chown isn't available in initramfs /boot/initrd.img-4.18.0-7-generic. /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf $new_resolv_conf' but busybox chmod in the initramfs does not support the option --reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1793060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793060] [NEW] configure_networking uses features not available in initramfs.
Public bug reported: initramfs-tools 0.131ubuntu10 modified configure_networking to use run_dhclient instead of ipconfig. configure_network now fails to configure networking in the initramfs because it now uses features not available in the initramfs. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe run_dhclient calls dhclient which calls /sbin/dhclient-script. /sbin/dhclient-script calls 'chown --reference=$resolv_conf $new_resolv_conf', but chown isn't available in initramfs /boot/initrd.img-4.18.0-7-generic. /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf $new_resolv_conf' but busybox chmod in the initramfs does not support the option --reference. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1793060 Title: configure_networking uses features not available in initramfs. Status in initramfs-tools package in Ubuntu: New Bug description: initramfs-tools 0.131ubuntu10 modified configure_networking to use run_dhclient instead of ipconfig. configure_network now fails to configure networking in the initramfs because it now uses features not available in the initramfs. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe run_dhclient calls dhclient which calls /sbin/dhclient-script. /sbin/dhclient-script calls 'chown --reference=$resolv_conf $new_resolv_conf', but chown isn't available in initramfs /boot/initrd.img-4.18.0-7-generic. /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf $new_resolv_conf' but busybox chmod in the initramfs does not support the option --reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1793060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703275] Re: package libqt5test5:amd64 5.5.1+dfsg-16ubuntu7 [modified: usr/lib/x86_64-linux-gnu/libQt5Test.so.5.5.1] failed to install/upgrade: package libqt5test5:amd64 is not r
[Expired for qtbase-opensource-src (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qtbase-opensource-src (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1703275 Title: package libqt5test5:amd64 5.5.1+dfsg-16ubuntu7 [modified: usr/lib/x86_64-linux-gnu/libQt5Test.so.5.5.1] failed to install/upgrade: package libqt5test5:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in qtbase-opensource-src package in Ubuntu: Expired Bug description: some fuction didn't work properly. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5test5:amd64 5.5.1+dfsg-16ubuntu7 [modified: usr/lib/x86_64-linux-gnu/libQt5Test.so.5.5.1] 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.6 Architecture: amd64 Date: Mon Jul 10 07:53:02 2017 DuplicateSignature: package:libqt5test5:amd64:5.5.1+dfsg-16ubuntu7 [modified: usr/lib/x86_64-linux-gnu/libQt5Test.so.5.5.1] Unpacking thunderbird-locale-en-gb (1:52.2.1+build1-0ubuntu0.16.04.1) ... dpkg: error processing package libqt5test5:amd64 (--configure): package libqt5test5:amd64 is not ready for configuration ErrorMessage: package libqt5test5:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-19 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: qtbase-opensource-src Title: package libqt5test5:amd64 5.5.1+dfsg-16ubuntu7 [modified: usr/lib/x86_64-linux-gnu/libQt5Test.so.5.5.1] failed to install/upgrade: package libqt5test5:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1703275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672335] Re: Black screen on quartered apps with a 5th overlapping
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1672335 Title: Black screen on quartered apps with a 5th overlapping Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: STEPS: 1. open the following 5 apps in the deb version of unity8: mines thunderbird firefox ubuntu-terminal-app system-settings 2. Open a youtube video in firefox 3. Sign into an email account on thunderbird 4. Start a game of mines 5. tail -f ~/.cache/upstart/unity8.log in terminal 6. Drop these four apps 1 in each corner so you see all four 7. Drop system-settings in the middle over lapping the other four EXPECTED: All 5 apps to run without issue ACTUAL: One of the apps will randomly trigger a blank window and title bar to overlay the entire screen. If mines triggers it just displays the title bar no idea why it is different. Thunderbird and Firefox seem to be the main culprits. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675683] Re: Computer sluggish/irresponsive for several minutes after hibernation
[Expired for pm-utils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pm-utils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1675683 Title: Computer sluggish/irresponsive for several minutes after hibernation Status in pm-utils package in Ubuntu: Expired Bug description: Hi, my computer is very sluggish for a good five minutes after thawing from hibernation. Booting the system and the thawing process in itself seems to run fine : the console displays the progress of reloading contents into RAM at a satisfying pace, then the lightdm unlock interface displays. From this point on, things become strange : the computer has an constant and intense hard drive activity and applications do not respond to input in a swift manner (moving the mouse cursor works in "real time" though, and the clock, which displays seconds, also works almost normally). This reminds me of what happens when you set focus back to an application that had been paged to swap : it is irresponsive until it is back in RAM. Except this happens for all applications at once. This stops after several minutes (more than five) and the computer becomes usable again. I experienced the problem today again. The current RAM usage is 7.2 Gio / 15.6 Gio and swap usage is 4.2 Gio / 31.3 Gio. Main memory usage is : firefox 3.4 Gio firefox (other instance) 1.7 Gio thunderbird 624 Mio xfwm4 213 Mio Hibernation with TuxOnIce did not induce this problem (I am not using it currently due to mismanagement of video drivers). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pm-utils 1.4.1-16 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 24 09:20:15 2017 InstallationDate: Installed on 2016-09-07 (197 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1675683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672335] Re: Black screen on quartered apps with a 5th overlapping
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1672335 Title: Black screen on quartered apps with a 5th overlapping Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: STEPS: 1. open the following 5 apps in the deb version of unity8: mines thunderbird firefox ubuntu-terminal-app system-settings 2. Open a youtube video in firefox 3. Sign into an email account on thunderbird 4. Start a game of mines 5. tail -f ~/.cache/upstart/unity8.log in terminal 6. Drop these four apps 1 in each corner so you see all four 7. Drop system-settings in the middle over lapping the other four EXPECTED: All 5 apps to run without issue ACTUAL: One of the apps will randomly trigger a blank window and title bar to overlay the entire screen. If mines triggers it just displays the title bar no idea why it is different. Thunderbird and Firefox seem to be the main culprits. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704815] Re: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin
[Expired for coreutils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: coreutils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1704815 Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz usr/share/man/man8/chroot.8.gz] failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') Status in coreutils package in Ubuntu: Expired Bug description: Tried to update Thunderbird ProblemType: Package DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz usr/share/man/man8/chroot.8.gz] ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Mon Jul 17 17:44:14 2017 DpkgTerminalLog: dpkg: error processing package coreutils (--configure): package coreutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package coreutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-10-01 (289 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: coreutils Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/share/man/man1/id.1.gz usr/share/man/man1/pinky.1.gz usr/share/man/man1/printenv.1.gz usr/share/man/man1/sha1sum.1.gz usr/share/man/man8/chroot.8.gz] failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1704815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 606579] Re: Digital output has a higher priority than analog output
Lenovo Y550P-4CWI is not available anymore, so I re-verified this issue on another laptop - Acer Aspire 7560G (Radeon HD 6620G+6650M). This time I tested with Kubuntu 18,10 daily image, instead of Kubuntu 17.10. With Radeon driver digital output is disabled by default, so audio goes to internal audio adapter. Also when I enabled HDMI output manually in System Settings, it priority remain below internal audio adapter which is desired behaviour. Unfortunately, I can no longer verify if issue is present with nouveau, but let's hope it's fixed there too. For the time being, I close this report. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/606579 Title: Digital output has a higher priority than analog output Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: phonon Digital output (nVidia GT216M HDMI) has a higher priority than analog output (hda_codec: ALC272) in Ubuntu Maverick. In result after boot LiveCD/DVD on laptop (Lenovo Y550P-4CWI) user not hear any sound. Analog outputs should have higher priority by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/606579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
I'll chime in as well. This bug is absolutely ridiculous. I lost half a day to this. I completely agree with Marten in 35: > This is a blocking issue for non-technical users I thought I had some nasty bug with my alexa to ngrok to django set up. Turns out, name lookups were just slow, causing my Alexa skill to time out. Once I figured out the cause, it was a 10m fix, but the hours of troubleshooting python packages to figure out the issue was just a waste. Thank you to those of you who provided the details for the fix. Saved me a bunch of time. To anyone that stumbles on this, I followed 8, 14 and 31 above, removing the file, relinking, and editing the systemd file to add a nameserver. Here were my steps, YMMV: sudo rm -f /etc/resolv.conf sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf sudo nano /etc/systemd/resolved.conf then added the google nameservers to my file, adding this line. nameserver 8.8.8.8 Good luck! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774049] Re: df incorrectly reports available space left
$ lsb_release -l Usage: lsb_release [options] lsb_release: error: no such option: -l ** Changed in: coreutils (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1774049 Title: df incorrectly reports available space left Status in coreutils package in Ubuntu: New Bug description: When using df command, it reports 19GB available on /home, however trying to write anything to that gives a no space left error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1774049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
@BrettSkogen - thanks for reporting back. I was going to try the OpenSSL downgrade myself but haven't had the time. I'd be curious to see what you find out by looking at the update-crypto-policies command. Let us know what you find out. Going to take a look at it myself now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I can tell you something that doesn't work, to hopefully save you some time. One of the earlier comments on this bug suggested that the issue was being caused by support for 3DES being removed from Bionic Beaver. I downloaded the source code for OpenSSL 1.1.0i, and compiled the code with the option to enable weak ciphers. My install of OpenSSL now supports 3DES, but I am still unable to connect to WPA2 Enterprise WiFi networks. I downloaded the source code for the update-crypto-policies command that Fedora uses. It looks like it is just a bunch of perl scripts. I am going to look at what the LEGACY scripts do to see if I can figure out exactly what option they are using on Fedora to work around this issue. Unfortunately I haven't been able to look through all of the scripts yet. On Mon, Sep 17, 2018 at 5:21 AM NAGENDRA PRABHU <1748...@bugs.launchpad.net> wrote: > I also ran into this issue after upgrading from 16.04 to 18.04. > Any updates on this? > What's the Ubuntu equivalent of the Fedora workaround for this? ($ > update-crypto-policies --set LEGACY) > If it is not available, is it possible to make a fix by downgrading > openSSL? If so, can you please explain the steps? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1748839 > > Title: > Problem to connect to WPA2/PEAP WIFI - gnome-shell > > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > This problem is also happened on my desktop. > > After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC > could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no > CA certificate/true username and password. > > > I tried to solve the problem following URL link; however, it could not > help me also. > > https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c > > > My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × > 4, OS: Ubuntu 18.04.1 (64-bit). > > root@joe-UBTPC:/root # lspci > > 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core > processor DRAM Controller (rev 09) > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd > Gen Core processor Graphics Controller (rev 09) > 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series > Chipset Family MEI Controller #1 (rev 04) > 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset > Family USB Enhanced Host Controller #2 (rev 05) > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset > Family High Definition Audio Controller (rev 05) > 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset > Family PCI Express Root Port 1 (rev b5) > 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset > Family PCI Express Root Port 2 (rev b5) > 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset > Family PCI Express Root Port 3 (rev b5) > 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset > Family PCI Express Root Port 4 (rev b5) > 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset > Family PCI Express Root Port 5 (rev b5) > 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset > Family PCI Express Root Port 6 (rev b5) > 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset > Family USB Enhanced Host Controller #1 (rev 05) > 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC > Controller (rev 05) > 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset > Family SATA AHCI Controller (rev 05) > 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family > SMBus Controller (rev 05) > 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network > Adapter > 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU:
[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system
** Summary changed: - update-initramfs hangs on upgrade, dpkg unusable, unbootable system + [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system ** Summary changed: - [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system + [SRU] update-initramfs should sync only the filesystem containing the initramfs image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at
Re: [Touch-packages] [Bug 1792786] Re: package humanity-icon-theme 0.6.15 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Thanks for your help, i did the command and after the update and juste the first step of fsck cause it's write it will be dangerous for the system to continue, now everything seems to be ok, (at the beginning there was a non-opening of the usb key on the desk, but it doesn't matter because with thunar it was ok, and now it's ok by "choose the option open with the folder) best regards Le 16/09/2018 à 14:17, Ubuntu Foundations Team Bug Bot a écrit : > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It seems that there was an error on your system when > trying to install a particular package. Please execute the following > command, as it will clear your package cache, in a terminal: > > sudo apt-get clean > > Then try performing the update again. This will likely resolve your > issue, but the failure could be caused by filesystem or memory > corruption. So please also run a fsck on your filesystem(s) and a > memory test. Thanks in advance! > > [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] > > ** Tags added: corrupted-package > > ** Changed in: humanity-icon-theme (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1792786 Title: package humanity-icon-theme 0.6.15 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive Status in humanity-icon-theme package in Ubuntu: Invalid Bug description: During the updating Ubuntu 1- to 18 beaver, bests regards ProblemType: Package DistroRelease: Ubuntu 18.04 Package: humanity-icon-theme 0.6.15 ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18 Uname: Linux 4.15.0-35-generic i686 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: i386 Date: Sun Sep 16 10:12:10 2018 ErrorMessage: corrupted filesystem tarfile - corrupted package archive InstallationDate: Installed on 2013-07-10 (1894 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-12:41 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: humanity-icon-theme Title: package humanity-icon-theme 0.6.15 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1792786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792984] [NEW] graphic lag
Public bug reported: the graphic not very smooth ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Sep 18 00:38:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2018-09-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 02YHJP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd04/02/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn02YHJP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792984 Title: graphic lag Status in xorg package in Ubuntu: New Bug description: the graphic not very smooth ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Sep 18 00:38:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2018-09-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 02YHJP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd04/02/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn02YHJP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1792984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
This bug was fixed in the package initramfs-tools - 0.131ubuntu11 --- initramfs-tools (0.131ubuntu11) cosmic; urgency=medium * debian/initramfs-tools.postinst: remove orphaned old-dkms initrd files in /boot. (LP: #1791959) -- Tiago Stürmer Daitx Wed, 12 Sep 2018 12:06:58 + ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
This bug was fixed in the package systemd - 239-7ubuntu8 --- systemd (239-7ubuntu8) cosmic; urgency=medium [ Dimitri John Ledkov ] * Cherrypick many bugfixes from master. * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) [ Julian Andres Klode ] * Improve networkd states documentation. -- Dimitri John Ledkov Wed, 12 Sep 2018 16:03:08 +0100 ** Changed in: systemd (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: Confirmed Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789502] Re: Update to 0.6.50
indicator-messages was updated in https://code.launchpad.net/~robert- ancell/indicator-messages/has-messages/+merge/355127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792978] [NEW] initscript avahi-daemon, action "start" failed
Public bug reported: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed Status in avahi package in Ubuntu: New Bug description: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788608] Re: wget doesn't support compression, it needs zlib1g-dev
** Changed in: wget (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1788608 Title: wget doesn't support compression, it needs zlib1g-dev Status in wget package in Ubuntu: New Status in wget package in Debian: Fix Released Bug description: wget can use zlib1g for a few features, notably --compression support. The Debian package doesn't explicitly build-depend on zlib1g-dev, it gets it via libgnutls28-dev; since the Ubuntu package drops the latter, compression support is lost too. Please consider adding zlib1g-dev. (I've also asked the Debian maintainer to do so, see the linked bug; however the libgnutls28-dev removal in Ubuntu should take this into account IMO.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1788608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
I did prepare some slightly modified proposal for this and will try to get things progressing tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: New Status in OEM Priority Project: New Status in kmod package in Ubuntu: Confirmed Status in kmod source package in Xenial: Confirmed Status in kmod source package in Bionic: Confirmed Status in kmod source package in Cosmic: Confirmed Bug description: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792954] Re: Search for bluetooth devices stuck
Please: 1. Describe the problem in more detail; and 2. Run this command to send us more information about the system: apport-collect 1792954 ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1792954 Title: Search for bluetooth devices stuck Status in bluez package in Ubuntu: Incomplete Bug description: This seems to be an old bug with no visible resolution. As of today September 17 2018 (!) I am running this os64@os64-desktop:~$ uname -a Linux os64-desktop 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782950] Re: package libkmod2 24-1ubuntu3 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/ch
*** This bug is a duplicate of bug 1658374 *** https://bugs.launchpad.net/bugs/1658374 ** This bug has been marked a duplicate of bug 1658374 package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1782950 Title: package libkmod2 24-1ubuntu3 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in kmod package in Ubuntu: New Bug description: Upgrade failed (or at least reported an error). Ubuntu 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libkmod2 24-1ubuntu3 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Jul 21 21:01:02 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libkmod2:24-1ubuntu3 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (24-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-enXHF1/11-libkmod2_24-1ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2014-01-08 (1655 days ago) InstallationMedia: Custom 13.10 - Release amd64 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: kmod Title: package libkmod2 24-1ubuntu3 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to bionic on 2018-05-20 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1782950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750474] Re: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/ch
*** This bug is a duplicate of bug 1658374 *** https://bugs.launchpad.net/bugs/1658374 ** This bug has been marked a duplicate of bug 1658374 package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1750474 Title: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in kmod package in Ubuntu: Confirmed Bug description: I'm not sure if this is a new bug or not but I haven't been able to install new software for quite some time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Feb 19 19:31:53 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2018-02-19 19:31:46 Commandline: apt-get -f install Requested-By: robert (1000) Install: libkmod2:i386 (22-1ubuntu5, automatic) Upgrade: udev:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:i386 (229-4ubuntu19, 229-4ubuntu21.1), libudev-dev:i386 (229-4ubuntu19, 229-4ubuntu21.1) DpkgTerminalLog: Preparing to unpack .../libkmod2_22-1ubuntu5_i386.deb ... Unpacking libkmod2:i386 (22-1ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 DuplicateSignature: package:libkmod2:22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2017-03-28 (328 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: kmod Title: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2017-07-05 (229 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1750474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792967] [NEW] CVE-2018-7738 - command execution via unmount's bash-completion
*** This bug is a security vulnerability *** Public security bug reported: "In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion." https://security-tracker.debian.org/tracker/CVE-2018-7738 Here is the patch that Debian applied earlier: https://salsa.debian.org/debian/util-linux/blob/1d518f8b38e81cfcc6e0cd1ecbf9ea72d568e53a/debian/patches/bash-completion-umount-use-findmnt-escape-a-space-in.patch It's already been fixed in cosmic but needs to be fixed in bionic. I saw this link on social media this weekend: https://blog.grimm-co.com/post/malicious-command-execution-via-bash-completion-cve-2018-7738/ ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7738 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1792967 Title: CVE-2018-7738 - command execution via unmount's bash-completion Status in util-linux package in Ubuntu: New Bug description: "In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion." https://security-tracker.debian.org/tracker/CVE-2018-7738 Here is the patch that Debian applied earlier: https://salsa.debian.org/debian/util-linux/blob/1d518f8b38e81cfcc6e0cd1ecbf9ea72d568e53a/debian/patches/bash-completion-umount-use-findmnt-escape-a-space-in.patch It's already been fixed in cosmic but needs to be fixed in bionic. I saw this link on social media this weekend: https://blog.grimm-co.com/post/malicious-command-execution-via-bash-completion-cve-2018-7738/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1792967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1791405 Title: bluetooth always in discoverable mode (security issue) Status in apport package in Ubuntu: New Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1791405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792135] Re: jackd crashed with SIGABRT in std::terminate()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1792135/+attachment/5187930/+files/CoreDump.gz ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1792135 Title: jackd crashed with SIGABRT in std::terminate() Status in jackd2 package in Ubuntu: New Bug description: Disabling the Jack Server ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-lowlatency 4.18.5 Uname: Linux 4.18.0-7-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Wed Sep 12 18:24:54 2018 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2018-09-08 (3 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180906) ProcCmdline: /usr/bin/jackd -T -ndefault -dalsa -dhw:UR22mkII -r96000 -p256 -n2 Signal: 6 SourcePackage: jackd2 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libjackserver.so.0 Title: jackd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1792135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
** Description changed: - At least four users, including myself, are having an issue with update- - initramfs hanging while updating ubuntu 16.04. The bug has been - documented while attempting an update to multiple kernel versions ( - 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or - install to fail, and may also lead to an unbootable system. + [Impact] + If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. + + [Test Case] + One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. + + 1. Setup a nfs server and export a directory with write permissions for + the client + + 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) + $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress + Note: adjust the "count" accordingly to how fast/slow your system is. + + 3. Call sync and verify that it only finished after "dd" is done. + + 4. Repeat step #2 and now call "sync -f /boot/". + Verify that it finished immediatly. + + [Regression Potential] + Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. + + [Other] + If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). + + The 'sync' and 'syncfs' specifications are pretty much similar and + syncfs is expected to work the same as a normal sync regarding data + integrity. Also altought the patch introduces the initrd file as an + extra argument which would cause 'sync -f' to fail if the file does not + exist, the update-initramfs script would fail earlier than that because + that file is created by the 'mv' call a few lines above. Thus no + regressions are expected. + + [References] + [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 + [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html + + [Original bug report] + At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade - Fetched 1,571 MB in 2min 9s (12.2 MB/s) + Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic - (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. + (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic - (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line
[Touch-packages] [Bug 1792241] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792241 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: I don know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Wed Sep 12 22:09:42 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-02-24 (1661 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-09-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1792241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain
** Changed in: gcc-defaults (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1786940 Title: Enable arm-linux-gnueabi target on ppc64el toolchain Status in The Ubuntu-power-systems project: Incomplete Status in binutils package in Ubuntu: Fix Released Status in gcc-7-cross package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Incomplete Bug description: Dear Canonical. We would like to have arm-linux-gnueabi target on ppc64el cross toolchain. This would enable us to use a ppc64el host to do cross compilation for aarch64. I talked to Matthias Klose already, and he is aware of this request. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1786940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain
** Changed in: ubuntu-power-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1786940 Title: Enable arm-linux-gnueabi target on ppc64el toolchain Status in The Ubuntu-power-systems project: Incomplete Status in binutils package in Ubuntu: Fix Released Status in gcc-7-cross package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Incomplete Bug description: Dear Canonical. We would like to have arm-linux-gnueabi target on ppc64el cross toolchain. This would enable us to use a ppc64el host to do cross compilation for aarch64. I talked to Matthias Klose already, and he is aware of this request. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1786940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Please test proposed package
Hello Matthias, or anyone else affected, Accepted cross-toolchain-base-ports into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /cross-toolchain-base-ports/22ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in cross-toolchain-base source package in Bionic: Fix Committed Status in cross-toolchain-base-ports source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792954] [NEW] Search for bluetooth devices stuck
Public bug reported: This seems to be an old bug with no visible resolution. As of today September 17 2018 (!) I am running this os64@os64-desktop:~$ uname -a Linux os64-desktop 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1792954 Title: Search for bluetooth devices stuck Status in bluez package in Ubuntu: New Bug description: This seems to be an old bug with no visible resolution. As of today September 17 2018 (!) I am running this os64@os64-desktop:~$ uname -a Linux os64-desktop 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Please test proposed package
Hello Matthias, or anyone else affected, Accepted cross-toolchain-base-ports into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /cross-toolchain-base-ports/22ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-defaults (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in cross-toolchain-base source package in Bionic: Fix Committed Status in cross-toolchain-base-ports source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
Hello Matthias, or anyone else affected, Accepted cross-toolchain-base into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /cross-toolchain-base/26ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cross-toolchain-base (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: cross-toolchain-base-ports (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in cross-toolchain-base source package in Bionic: Fix Committed Status in cross-toolchain-base-ports source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Please test proposed package
Hello Matthias, or anyone else affected, Accepted gcc-defaults-ports into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc- defaults-ports/1.176ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in cross-toolchain-base source package in Bionic: Fix Committed Status in cross-toolchain-base-ports source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Please test proposed package
Hello Matthias, or anyone else affected, Accepted gcc-defaults into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc- defaults/1.176ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-defaults-ports (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in cross-toolchain-base source package in Bionic: Fix Committed Status in cross-toolchain-base-ports source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
** Changed in: zsh (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Triaged Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
** Changed in: wget (Ubuntu) Status: New => Triaged ** Changed in: wget (Ubuntu) Assignee: Noël Köthe (noel) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Triaged Status in zsh package in Ubuntu: New Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792934] Re: symlink loop detected in path 'usr/share/doc/module-init-tools/changelog.Debian.gz'
(TBH I've no idea what debsums is nattering about, /usr/share/doc /module-init-tools/changelog.Debian.gz is a regular file, and no parent directory is a symlink.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1792934 Title: symlink loop detected in path 'usr/share/doc/module-init- tools/changelog.Debian.gz' Status in kmod package in Ubuntu: New Bug description: I ran debsums -ac and it printed this error debsums: Error: symlink loop detected in path 'usr/share/doc /module-init-tools/changelog.Debian.gz'. Please file a bug again module-init-tools. So here I am, filing a bug against module-init-tools. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: module-init-tools 24-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 16:13:36 2018 InstallationDate: Installed on 2012-11-02 (2144 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kmod UpgradeStatus: Upgraded to bionic on 2018-09-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1792934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792934] [NEW] symlink loop detected in path 'usr/share/doc/module-init-tools/changelog.Debian.gz'
Public bug reported: I ran debsums -ac and it printed this error debsums: Error: symlink loop detected in path 'usr/share/doc/module- init-tools/changelog.Debian.gz'. Please file a bug again module-init- tools. So here I am, filing a bug against module-init-tools. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: module-init-tools 24-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 16:13:36 2018 InstallationDate: Installed on 2012-11-02 (2144 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kmod UpgradeStatus: Upgraded to bionic on 2018-09-16 (1 days ago) ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1792934 Title: symlink loop detected in path 'usr/share/doc/module-init- tools/changelog.Debian.gz' Status in kmod package in Ubuntu: New Bug description: I ran debsums -ac and it printed this error debsums: Error: symlink loop detected in path 'usr/share/doc /module-init-tools/changelog.Debian.gz'. Please file a bug again module-init-tools. So here I am, filing a bug against module-init-tools. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: module-init-tools 24-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 16:13:36 2018 InstallationDate: Installed on 2012-11-02 (2144 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kmod UpgradeStatus: Upgraded to bionic on 2018-09-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1792934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
Maybe this is the fix: x86/speculation/l1tf: fix overflow on l1tf_pfn_limit() on 32bit https://lkml.org/lkml/2018/8/20/222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
On Xenial, update to "linux-image-4.4.0-135-generic 4.4.0-135.161" did not fix the problem, but I noticed a message, that might be related to the issue: [3.083083] Truncating oversized swap area, only using 0k out of 261116k -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792930] [NEW] split does not break on error when reading from standard input
Public bug reported: Hi all, I found a bug in "split". I want to tar some files but some of them have wrong permissions. tar puts out an exit code 2 "Cannot open: Permission denied". That is good because in my script I can catch this error and react to this. $ tar -c -f /tmp/test.tar -C /media/testpath testfile ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 2 Unfortunately my tar directory is too big to save it in one file on my filesystem that I have to split the archive. But doing this "split" does not get the error code 2 from standard input (tar) and does not break as it should: $ tar -c -f - -C /media/testpath testfile | split - ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 0 In the end I got a tar file without files that have no permissions and my script does not break because of error code 0. Ubuntu 18.04.1 tar 1.29b coreutils 8.28 Best regards, Alexander ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1792930 Title: split does not break on error when reading from standard input Status in coreutils package in Ubuntu: New Bug description: Hi all, I found a bug in "split". I want to tar some files but some of them have wrong permissions. tar puts out an exit code 2 "Cannot open: Permission denied". That is good because in my script I can catch this error and react to this. $ tar -c -f /tmp/test.tar -C /media/testpath testfile ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 2 Unfortunately my tar directory is too big to save it in one file on my filesystem that I have to split the archive. But doing this "split" does not get the error code 2 from standard input (tar) and does not break as it should: $ tar -c -f - -C /media/testpath testfile | split - ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 0 In the end I got a tar file without files that have no permissions and my script does not break because of error code 0. Ubuntu 18.04.1 tar 1.29b coreutils 8.28 Best regards, Alexander To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1792930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Please test proposed package
Hello Matthias, or anyone else affected, Accepted gcc-7-cross-ports into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-7 -cross-ports/17ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
Hello Matthias, or anyone else affected, Accepted gcc-8-cross-ports into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-8 -cross-ports/9ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-8-cross-ports (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: gcc-7-cross-ports (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532314] Re: Buffer overflow in cgmanager
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1532314 Title: Buffer overflow in cgmanager Status in cgmanager package in Ubuntu: Confirmed Status in libnih package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Host: Ubuntu 15.10 lxc: 1.1.5-0ubuntu0.15.10.3 cgmanager: 0.39-2ubuntu2 Container: Ubuntu 15.10 Got the following trace in syslog. Please let me know what other information will be useful for troubleshooting. Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: *** buffer overflow detected ***: /sbin/cgmanager terminated Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: === Backtrace: = Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7f1929550c4e] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f19295f0e8c] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(+0x116e80)[0x7f19295eee80] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(+0x118dd7)[0x7f19295f0dd7] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libnih.so.1(nih_io_handle_fds+0xad)[0x7f1929d01b3d] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libnih.so.1(nih_main_loop+0x13f)[0x7f1929d05faf] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /sbin/cgmanager(+0x5145)[0x562d8fc75145] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f19294f8a40] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /sbin/cgmanager(+0x53d9)[0x562d8fc753d9] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: === Memory map: Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fc7-562d8fc92000 r-xp ca:01 12884 /sbin/cgmanager Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fe92000-562d8fe94000 r--p 00022000 ca:01 12884 /sbin/cgmanager Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fe94000-562d8fe95000 rw-p 00024000 ca:01 12884 /sbin/cgmanager Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d915f8000-562d9203 rw-p 00:00 0 [heap] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927d44000-7f1927d5a000 r-xp ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927d5a000-7f1927f59000 ---p 00016000 ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f59000-7f1927f5a000 r--p 00015000 ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f5a000-7f1927f5b000 rw-p 00016000 ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f5b000-7f1927f67000 r-xp ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f67000-7f1928166000 ---p c000 ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928166000-7f1928167000 r--p b000 ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928167000-7f1928168000 rw-p c000 ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928168000-7f1928173000 r-xp ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928173000-7f1928372000 ---p b000 ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928372000-7f1928373000 r--p a000 ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928373000-7f1928374000 rw-p b000 ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928374000-7f192838b000 r-xp ca:01 403845 /lib/x86_64-linux-gnu/libnsl-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f192838b000-7f192858a000 ---p 00017000 ca:01 403845 /lib/x86_64-linux-gnu/libnsl-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f192858a000-7f192858b000 r--p 00016000 ca:01 403845
[Touch-packages] [Bug 1792900] Re: help
** Package changed: xorg (Ubuntu) => gstreamer0.10 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1792900 Title: help Status in gstreamer0.10 package in Ubuntu: New Bug description: root@chika:~# gst-launch-0.10 tcpclientsrc host=10.0.0.240 port=5000 ! multipartdemux ! jpegdec ! v4l2sink device=/dev/video0 Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... root@chika:~# ls -l /dev/video* ls: cannot access /dev/video*: No such file or directory root@chika:~# gnome-control-center *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (gnome-control-center.real:6331): screen-cc-panel-WARNING **: Error getting brightness: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (gnome-language-selector:6364): Gtk-DEBUG: Connecting to session manager (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called expand (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called fill (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called position (gnome-control-center.real:6331): GLib-GIO-CRITICAL **: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_get_int32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_INT32)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (gnome-control-center.real:6331): GLib-CRITICAL **: Source ID 8200 was not found when attempting to remove it Error getting devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Power was not provided by any .service files *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug ** (deja-dup:6798): DEBUG: DuplicityInstance.vala:197: Running the following duplicity (6813) command: duplicity 'collection-status' '-- gio' 'file:///root/deja-dup' '--no-encryption' '--verbosity=9' '--gpg- options=--no-use-agent' '--archive-dir=/root/.cache/deja-dup' '-- tempdir=/tmp' '--log-fd=16' ** (deja-dup:6798): DEBUG: DuplicityInstance.vala:570: duplicity (6813) exited with value 0 (gnome-control-center.real:6331): info-cc-panel-WARNING **: Failed to get fallback mode: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files root@chika:~# gstreamer-properties (gstreamer-properties:6857): Gtk-WARNING **: Unknown property: GtkDialog.has-separator (gstreamer-properties:6857): Gtk-WARNING **: Unknown property: GtkDialog.has-separator gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosink' gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'v4lsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosrc' gstreamer-properties-Message: Error running pipeline 'Video for Linux 2 (v4l2)': Cannot identify device '/dev/video0'. [v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src1: system error: No such file or directory] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-135-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I also ran into this issue after upgrading from 16.04 to 18.04. Any updates on this? What's the Ubuntu equivalent of the Fedora workaround for this? ($ update-crypto-policies --set LEGACY) If it is not available, is it possible to make a fix by downgrading openSSL? If so, can you please explain the steps? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633754] Re: dirmngr is used as daemon
What I want to do is provide stable versioned CLI APIs that you can specify in scripts in an environment variable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1633754 Title: dirmngr is used as daemon Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 16.10 with gnupg2 2.1.15-1ubuntu6 and for example if I'm using apt-key to receive keys I'm noticing that dirmngr is started and kept open after the task is done. If apt-key is used multiple times even multiple times dirmngr is started while the old processes are still open. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1633754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792900] [NEW] help
Public bug reported: root@chika:~# gst-launch-0.10 tcpclientsrc host=10.0.0.240 port=5000 ! multipartdemux ! jpegdec ! v4l2sink device=/dev/video0 Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... root@chika:~# ls -l /dev/video* ls: cannot access /dev/video*: No such file or directory root@chika:~# gnome-control-center *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (gnome-control-center.real:6331): screen-cc-panel-WARNING **: Error getting brightness: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (gnome-language-selector:6364): Gtk-DEBUG: Connecting to session manager (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called expand (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called fill (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called position (gnome-control-center.real:6331): GLib-GIO-CRITICAL **: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_get_int32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_INT32)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (gnome-control-center.real:6331): GLib-CRITICAL **: Source ID 8200 was not found when attempting to remove it Error getting devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Power was not provided by any .service files *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug ** (deja-dup:6798): DEBUG: DuplicityInstance.vala:197: Running the following duplicity (6813) command: duplicity 'collection-status' '-- gio' 'file:///root/deja-dup' '--no-encryption' '--verbosity=9' '--gpg- options=--no-use-agent' '--archive-dir=/root/.cache/deja-dup' '-- tempdir=/tmp' '--log-fd=16' ** (deja-dup:6798): DEBUG: DuplicityInstance.vala:570: duplicity (6813) exited with value 0 (gnome-control-center.real:6331): info-cc-panel-WARNING **: Failed to get fallback mode: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files root@chika:~# gstreamer-properties (gstreamer-properties:6857): Gtk-WARNING **: Unknown property: GtkDialog .has-separator (gstreamer-properties:6857): Gtk-WARNING **: Unknown property: GtkDialog.has-separator gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosink' gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'v4lsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosrc' gstreamer-properties-Message: Error running pipeline 'Video for Linux 2 (v4l2)': Cannot identify device '/dev/video0'. [v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src1: system error: No such file or directory] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-135-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 17 11:36:31 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
wget builds and works with pcre2 in Debian (uploaded). I cannot change the Status to Triaged. Maybe somebody with higher privileges can change the wget status of this bug to Triaged. thx. ** Changed in: wget (Ubuntu) Assignee: (unassigned) => Noël Köthe (noel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: New Status in zsh package in Ubuntu: New Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633754] Re: dirmngr is used as daemon
@Julian So, if I understand well, you want remove the APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE environment variable but keep the warning when APT-KEY detect that its output is captured? That would be tedious for us.. We do not want such a warn in our case. We capture STDOUT for the purpose of debugging (STDOUT goes to a log file and is print to screen, depending on context). Sometime, you should let developers take decisions. If they are not able to stick to the man page recommendations, that not your problem, isn't it? Or do you consider that all developers are idiot? BTW: It seem that simply putting keys into the trusted directory is not sufficient. APT still warn about missing PUBKEY... See also https://askubuntu.com/questions/31286/additional-keyrings-for-apt-in- trusted-gpg-d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1633754 Title: dirmngr is used as daemon Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 16.10 with gnupg2 2.1.15-1ubuntu6 and for example if I'm using apt-key to receive keys I'm noticing that dirmngr is started and kept open after the task is done. If apt-key is used multiple times even multiple times dirmngr is started while the old processes are still open. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1633754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532314] Re: Buffer overflow in cgmanager
Based on the most recent comments, changing the priority back to undecided since there is no clear path forward for now. ** Changed in: libnih (Ubuntu) Importance: High => Undecided ** Changed in: lxc (Ubuntu) Importance: High => Undecided ** Changed in: cgmanager (Ubuntu) Status: New => Confirmed ** Changed in: libnih (Ubuntu) Status: New => Confirmed ** Changed in: lxc (Ubuntu) Status: Incomplete => Confirmed ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1532314 Title: Buffer overflow in cgmanager Status in cgmanager package in Ubuntu: Confirmed Status in libnih package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Host: Ubuntu 15.10 lxc: 1.1.5-0ubuntu0.15.10.3 cgmanager: 0.39-2ubuntu2 Container: Ubuntu 15.10 Got the following trace in syslog. Please let me know what other information will be useful for troubleshooting. Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: *** buffer overflow detected ***: /sbin/cgmanager terminated Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: === Backtrace: = Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7f1929550c4e] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f19295f0e8c] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(+0x116e80)[0x7f19295eee80] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(+0x118dd7)[0x7f19295f0dd7] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libnih.so.1(nih_io_handle_fds+0xad)[0x7f1929d01b3d] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libnih.so.1(nih_main_loop+0x13f)[0x7f1929d05faf] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /sbin/cgmanager(+0x5145)[0x562d8fc75145] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f19294f8a40] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: /sbin/cgmanager(+0x53d9)[0x562d8fc753d9] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: === Memory map: Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fc7-562d8fc92000 r-xp ca:01 12884 /sbin/cgmanager Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fe92000-562d8fe94000 r--p 00022000 ca:01 12884 /sbin/cgmanager Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fe94000-562d8fe95000 rw-p 00024000 ca:01 12884 /sbin/cgmanager Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d915f8000-562d9203 rw-p 00:00 0 [heap] Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927d44000-7f1927d5a000 r-xp ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927d5a000-7f1927f59000 ---p 00016000 ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f59000-7f1927f5a000 r--p 00015000 ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f5a000-7f1927f5b000 rw-p 00016000 ca:01 395872 /lib/x86_64-linux-gnu/libgcc_s.so.1 Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f5b000-7f1927f67000 r-xp ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f67000-7f1928166000 ---p c000 ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928166000-7f1928167000 r--p b000 ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928167000-7f1928168000 rw-p c000 ca:01 403839 /lib/x86_64-linux-gnu/libnss_files-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928168000-7f1928173000 r-xp ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928173000-7f1928372000 ---p b000 ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928372000-7f1928373000 r--p a000 ca:01 403823 /lib/x86_64-linux-gnu/libnss_nis-2.21.so Jan 8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928373000-7f1928374000 rw-p b000 ca:01 403823
[Touch-packages] [Bug 1792907] Re: apport-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1552577, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1792907/+attachment/5189781/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1792907/+attachment/5189783/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1792907/+attachment/5189786/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1792907/+attachment/5189787/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1792907/+attachment/5189788/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1792907/+attachment/5189789/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1792907/+attachment/5189790/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1792907 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: Crash occurred under Daily build of Xubuntu 18.10. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: apport-gtk 2.20.10-0ubuntu9 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CrashReports: 600:0:123:219125:2018-09-17 02:17:21.487040382 -0500:2018-09-17 02:26:24.198513594 -0500:/var/crash/xubuntu-artwork.0.crash 640:0:123:7121410:2018-09-17 02:20:57.253659963 -0500:2018-09-17 02:20:58.253659963 -0500:/var/crash/_usr_share_apport_apport-gtk.0.crash Date: Mon Sep 17 02:20:52 2018 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-09-16 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 SegvAnalysis: Segfault happened at: 0x7fc90c9fb879:mov(%rbx),%rdi PC (0x7fc90c9fb879) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1792907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
Hello Matthias, or anyone else affected, Accepted gcc-8-cross into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-8-cross/18ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-8-cross (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792906] [NEW] resolv.conf written after network-online.target
Public bug reported: On the server the docker.service is run. Sometimes after reboots it hands down a default resolv.conf to docker domains (8.8.8.8 and 8.8.4.4 if I'm correct) and NOT our local resolv.conf (which is generated from /etc/network/interfaces). It looks like a race condition between the docker service and the status of the hosts /etc/resolv.conf (which is a link to /run/resolvconf/resolv.conf) since other times thing work out OK. network-online.target should only be met after /run/resolvconf/resolv.conf is complete in my opinion. docker-ce service definition is: (/lib/systemd/system/docker.service) Wants=network-online.target ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 12:00:39 2018 InstallationDate: Installed on 2018-05-09 (130 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-05-09 (130 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792906 Title: resolv.conf written after network-online.target Status in systemd package in Ubuntu: New Bug description: On the server the docker.service is run. Sometimes after reboots it hands down a default resolv.conf to docker domains (8.8.8.8 and 8.8.4.4 if I'm correct) and NOT our local resolv.conf (which is generated from /etc/network/interfaces). It looks like a race condition between the docker service and the status of the hosts /etc/resolv.conf (which is a link to /run/resolvconf/resolv.conf) since other times thing work out OK. network-online.target should only be met after /run/resolvconf/resolv.conf is complete in my opinion. docker-ce service definition is: (/lib/systemd/system/docker.service) Wants=network-online.target ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 12:00:39 2018 InstallationDate: Installed on 2018-05-09 (130 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-05-09 (130 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1792906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1791324] Re: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@598:run_argv:run_crashes:run_crash
This bug was fixed in the package apport - 2.20.10-0ubuntu11 --- apport (2.20.10-0ubuntu11) cosmic; urgency=medium * Drop build/test dependency on obsolete libnih-dev. -- Steve Langasek Wed, 12 Sep 2018 20:28:31 -0700 ** Changed in: apport (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1791324 Title: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport- gtk@598:run_argv:run_crashes:run_crash Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: New Bug description: [Impact] * The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee * The theory is that those crashes are trigger by reports generated (but not send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, and thus, the new apport, when reporting, is crashing. * We now ignore if the key isn't present and just consider the answer as "false", which is a no-op. [Test Case] * Install apport 2.20.9-0ubuntu7.1 * Generate a crash but don't report it. * Upgrade to apport apport 2.20.9-0ubuntu7.3 * Report this crash. -> No apport crash should be triggered [Regression Potential] * We are doing a python2 compatible try/except to ignore the KeyError which was the regression. It doesn't seem it can trigger other regressions. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1791324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792725] Re: display issues.
Can you please explain what "shows display is not set" means? Can you provide a photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792725 Title: display issues. Status in Ubuntu: Incomplete Bug description: after restart of system it shows display is not set, so need to set default generic driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 15 22:27:07 2018 DistUpgraded: 2018-09-12 10:39:47,750 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2014-04-28 (1600 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: LENOVO 20B7S0RE0H ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic root=UUID=4a814860-4f54-4fd4-b365-de28a77e523f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-09-12 (3 days ago) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0RE0H dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20B7S0RE0H:pvrThinkPadT440:rvnLENOVO:rn20B7S0RE0H:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20B7S0RE0H dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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: Sat Sep 15 22:18:30 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633754] Re: dirmngr is used as daemon
@Julian Thank for your advise. So basically, putting keys into the trusted.gpg.d directory should be sufficient to make APT happy? I never tried that way, even worse (shame on me), I was not aware of that possibility... Regarding the environment variable, I really don't understand why we are warned. Capturing APT stdout doesn't necessarily mean parsing process... Even through, developers which invoke APT in automation script should known what they are doing. At least, a simple warn in the documentation should be sufficient... So yes, I'm with out on that point, that warn, should be dropped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1633754 Title: dirmngr is used as daemon Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 16.10 with gnupg2 2.1.15-1ubuntu6 and for example if I'm using apt-key to receive keys I'm noticing that dirmngr is started and kept open after the task is done. If apt-key is used multiple times even multiple times dirmngr is started while the old processes are still open. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1633754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792874] Re: Bluetooth will get off after turn it on few seconds.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1792874 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1792874 Title: Bluetooth will get off after turn it on few seconds. Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Test machine: M820z-1 Image: sutton-wilkes-xenial-amd64-20180717-84 (OEM image) CPU: Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92] BIOS: M1NKT25A Steps: 1. Installed system and log in. 2. Connect BT device (computer). 3. Transfer a file to the device 4. Open system settings -> Bluetooth window 5. Navigate to Bluetooth logo in top of right corner 6. Unfold and hover on the connecting device 7. Verify the result Actual result: Bluetooth will turn off few seconds later. Please refer to the video in attachment. Expected result: Bluetooth should not turn off automatically. Note: The issue can reproduce on Ubuntu 16.04 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371170] Re: information disclosure: clipboard contents can be obtained without user knowledge
** Changed in: content-hub (Ubuntu) Status: New => Won't Fix ** Changed in: mir (Ubuntu) Status: New => Confirmed ** Changed in: canonical-devices-system-image Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1371170 Title: information disclosure: clipboard contents can be obtained without user knowledge Status in Canonical System Image: Invalid Status in Mir: New Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Status in content-hub package in Ubuntu: Won't Fix Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Currently, the clipboard is implemented such that all apps can access the contents at any time. The clipboard contents should only be given to apps based on user driven input (eg, a paste operation). Attack scenario: 1. user launches malicious app 'baz' that polls the clipboard for contents 2. user launches legitimate app 'foo', at which point 'baz' is backgrounded 3. user selects some text and puts it into the clipboard 4. user opens legitimate app 'bar' and pastes text 5. user foregrounds 'baz' which now has access to the clipboard contents In the above, users can understand that 'foo' and 'bar' have access to the text put in the clipboard. However, it is unexpected that 'baz' also has access since the user didn't paste the text into it. As it is currently implemented, there is no clipboard timeout, so the contents will persist through the session (unless changed by another copy operation). Application lifecycle will help a little, but not fully since whenever an app is foregrounded, it can the contents of the keyboard. In the short term, we should require that only a foregrounded app whould be able to get clipboard contents. Push helpers should have an explicit deny to the (upcoming) DBus clipboard access. Background apps should not be allowed to push content into the clipboard (application lifecycle deals with this, but we need this for the future). Ideally this would be handled via wholly user-driven interactions. While this could be achieved via keyboard driven interactions, it is difficult with toolkit driven interactions (ie, 'Paste' from a menu is necessarily a pull operation). One idea is not to block access but instead make users aware of the clipboard access (eg, an overlay that says "Pasted from clipboard" and then fades out)-- this should be as unobtrusive as possible. Another idea is to implement paste in the input method menu, and make that the official way for users to paste inside applications, rather than use menu items or toolbar buttons. (Ie, remove the DBus clipboard support and implement this instead. At that point, apparmor-easyprof- ubuntu can remove the (now unused) DBus clipboard access). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1371170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790377] Re: Ubuntu 18.04.1 and below: Information disclosure through world readable by default home directory permissions
*** This bug is a duplicate of bug 48734 *** https://bugs.launchpad.net/bugs/48734 ** This bug has been marked a duplicate of bug 48734 Home permissions too open ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1790377 Title: Ubuntu 18.04.1 and below: Information disclosure through world readable by default home directory permissions Status in shadow package in Ubuntu: New Bug description: 1)Ubuntu 18.04.1 2)package passwd 4.5-1ubuntu1 (shadow) 3)Expected default home directory permissions of 0700 (no one should be able to read anyone else's files - probably required by European GDPR and others). 4) Home directory permissions of the first created user (potential root via sudo) on fresh Ubuntu 18.04.1 installation are 0755 (world read and executable). useradd -m NEWUSER also creates home directories with 0755 permissions (rx by world). Creating a new User via GUI also creates home directories with 0755 permissions (rx by world). GUI unfortunately creates Documents, Music, Videos, ... with world readable permissions too (another OS I have seen insecure home directory permissions too, but there at least the subfolders did not have world readable permissions). Thus every local user can read files created by other local users (security type "Loss of Privacy"). That there are other ways to read non-encrypted files is no excuse for such open permissions. If i.e. this was a web server and Apache is badly configured it could be used to remotely read confidential information without valid credentials too (increases risk and exploitability). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1790377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
Hello Matthias, or anyone else affected, Accepted gcc-7-cross into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-7-cross/21ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-7-cross (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792873] Re: FFE: 18.2.x for cosmic
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1792873 Title: FFE: 18.2.x for cosmic Status in mesa package in Ubuntu: Triaged Bug description: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633754] Re: dirmngr is used as daemon
There's no way to distinguish between output being parsed and not, so that's the safest thing to do. Without it, scripts will parse it, regardless of what the manpage says; and they will break, and everyone will be unhappy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1633754 Title: dirmngr is used as daemon Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 16.10 with gnupg2 2.1.15-1ubuntu6 and for example if I'm using apt-key to receive keys I'm noticing that dirmngr is started and kept open after the task is done. If apt-key is used multiple times even multiple times dirmngr is started while the old processes are still open. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1633754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
** Also affects: cross-toolchain-base-ports (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792798] Re: gdm3 will start in a new tty after suspend
** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792798 Title: gdm3 will start in a new tty after suspend Status in gdm3 package in Ubuntu: New Bug description: I'm not sure if there is any related info in log files because there is no actual crash or error messages. Im using Ubuntu 18.04 and Gnome3 on Xorg. Also, I have a NVidia GT520M with nvidia-390 driver installed through ubuntu-drivers utility. Cant confirm that is a graphics driver issue because I installed it on a fresh Ubuntu. Description === Whenever I suspend my laptop (e.g. close lid) and then turn it on, a new session will be opened in tty2 causing two graphical sessions being executed at the same time (?) Workaround === I found a workaround that simply requires to Log Out from the 2nd session (tty2) and pressing Ctrl+Alt+F1 to go back to the original Xorg session. After that the Login screen will appear. The background image will get pixelized and very distorted when the 2nd Xorg session is loaded. Will try to add a screenshot as attachment. Also, this bug could lead to "bypass" the login menu. I was able to change session without being asked for user password: one is stuck at the login screen and the other is logged in already. Not sure if it is a security issue because it would require a successful authentication beforehand. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Sep 16 14:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-08-19 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. K53SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=d07ee961-7df7-4a6a-9fc9-10d6724a7e9b ro quiet splash intel_pstate=enable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SJ.315 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SJ.315:bd09/26/2011:svnASUSTeKComputerInc.:pnK53SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK53SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.family: K dmi.product.name: K53SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1792798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1792807] Re: Login screen freeze
** Summary changed: - Xorg freeze + Login screen freeze ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze Status in gnome-shell package in Ubuntu: New Bug description: Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is frozen. I tried both gdm3 and lightdm login managers, with either I don't get into the system. I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD Graphics 2000. I have an external 24" ASUS display connected with VGA (tried HDMI as well but same problem). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 18:16:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-15 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. H67M-UD2H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/12/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: H67M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1809150630.283282~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809160730.149768~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0+git1809141934.80514b~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792816] Re: Several troubles
Can you please attach a screenshot or photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792816 Title: Several troubles Status in Ubuntu: Incomplete Bug description: Several troubles: wallpaper doesn't run, doesn't change. Bottons mini, max, stop (freeze). I went to google translate but my account was blocked. I speak little English. Sorry. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.17.11-041711-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 16 16:27:58 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:161d] InstallationDate: Installed on 2017-12-02 (287 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X553MA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.11-041711-generic root=UUID=ee051471-6a54-433a-bede-353f3c3d1b4c ro quiet splash intel_idle.max:cstate=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X553MA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X553MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X553MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Sep 16 16:25:29 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792816/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792814] Re: -
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792814 Title: - Status in Ubuntu: Incomplete Bug description: - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 16 21:01:41 2018 DistUpgraded: 2018-09-16 20:13:54,386 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0567] InstallationDate: Installed on 2018-09-12 (3 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Acer TravelMate 8481 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=9a861a15-371d-487b-89e1-48bc0bbf0d63 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA41_HS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.13 dmi.modalias: dmi:bvnAcer:bvrV2.13:bd04/24/2012:svnAcer:pnTravelMate8481:pvrV2.13:rvnAcer:rnBA41_HS:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.13: dmi.product.name: TravelMate 8481 dmi.product.version: V2.13 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Sep 16 19:36:12 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792820] Re: help you me
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792820 Title: help you me Status in Ubuntu: Incomplete Bug description: I don#t know what i am doing. How can I help you? help you me ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 16 22:33:39 2018 DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d] InstallationDate: Installed on 2016-10-16 (700 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X102BA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago) dmi.bios.date: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X102BA.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X102BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X102BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Sep 3 23:15:32 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792874] [NEW] Bluetooth will get off after turn it on few seconds.
Public bug reported: Test machine: M820z-1 Image: sutton-wilkes-xenial-amd64-20180717-84 (OEM image) CPU: Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92] BIOS: M1NKT25A Steps: 1. Installed system and log in. 2. Connect BT device (computer). 3. Transfer a file to the device 4. Open system settings -> Bluetooth window 5. Navigate to Bluetooth logo in top of right corner 6. Unfold and hover on the connecting device 7. Verify the result Actual result: Bluetooth will turn off few seconds later. Please refer to the video in attachment. Expected result: Bluetooth should not turn off automatically. Note: The issue can reproduce on Ubuntu 16.04 and 18.04 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluez ** Attachment added: "Ubuntu BT.zip" https://bugs.launchpad.net/bugs/1792874/+attachment/5189740/+files/Ubuntu%20BT.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1792874 Title: Bluetooth will get off after turn it on few seconds. Status in bluez package in Ubuntu: New Bug description: Test machine: M820z-1 Image: sutton-wilkes-xenial-amd64-20180717-84 (OEM image) CPU: Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92] BIOS: M1NKT25A Steps: 1. Installed system and log in. 2. Connect BT device (computer). 3. Transfer a file to the device 4. Open system settings -> Bluetooth window 5. Navigate to Bluetooth logo in top of right corner 6. Unfold and hover on the connecting device 7. Verify the result Actual result: Bluetooth will turn off few seconds later. Please refer to the video in attachment. Expected result: Bluetooth should not turn off automatically. Note: The issue can reproduce on Ubuntu 16.04 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
BTW - I'm running Kubuntu, and doing the upgrade with kubuntu-devel- release-upgrade works just fine without needing to update appstream to 0.12.2 first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792873] [NEW] FFE: 18.2.x for cosmic
Public bug reported: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) ** Affects: mesa (Ubuntu) Importance: Medium Status: Triaged ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1792873 Title: FFE: 18.2.x for cosmic Status in mesa package in Ubuntu: Triaged Bug description: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792822] Re: dual monitor not working in 18.04(.1)
It sounds like this problem may be limited to Wayland sessions (which includes the login screen). Please try this workaround next time you install 18.04: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false Then reboot. ** Tags added: multi-monit radeon ** Tags removed: multi-monit ** Tags added: multi-monitor ** Summary changed: - dual monitor not working in 18.04(.1) + Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792822 Title: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system Status in mutter package in Ubuntu: Incomplete Bug description: Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1). This renders 18.04 useless. Till this is solved will have to stick with 16.04. i.e. this is a pretty critical bug! After a fresh install from DVD first got a freeze on login screen (live CD will run ubuntu though!). This could be solved by switching to lightdm display manager. (Boo! for GDM that cannot even show a login screen without freezing the system) But one issue remains: the dual monitor setup will not work in 18.04. I can see the mouse move to the second monitor. I can drag windows there (and lose sight of them). I can see the mouse cursor change to click a link. But otherwise there is a completely black screen, or dots / colored fields, but nothing even resembling a program. MB: Gigabyte GA-A75M-UD2H Monitor that works fine: ASUS on Radeon HD 6550D monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the gigabyte motherboard) Note: dual monitor setup did not work with other upgrades after 16.04. I hoped this would be solved with the next LTS update. Not so, to great disappointment! Ubuntu really fails if with new major updates it makes systems fall down. This kind of thing should work FLAWLESS out of the box! How would anyone move to Ubuntu when this kind of thing does not work? Windows is a drama, but at least it has the mere basics working! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 16 23:09:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] [1002:9640] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] [174b:0851] InstallationDate: Installed on 2016-10-02 (714 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6c dmi.board.name: GA-A75M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1792857] Re: Mouse pointer is the wrong size after resuming from suspend
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792857 Title: Mouse pointer is the wrong size after resuming from suspend Status in gnome-shell package in Ubuntu: New Bug description: After resuming from suspend, but mouse pointer is the wrong size when located in some parts of the screen. Specifically, when mousing over the left or top bars of the UI (not the desktop or any running programs), the pointer is too large. A workaround is to open display settings, pick any other resolution, click apply, then click revert. When the original resolution is restored, the pointer size returns to normal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:46:42 2018 DistUpgraded: 2018-05-28 17:09:21,096 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2016-04-27 (872 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20BSCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-05-29 (111 days ago) dmi.bios.date: 08/13/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET32W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon May 28 16:18:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1049 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
binutils, gcc-7 and gcc-8 built successfully. All autopkg tests pass, testsuites look good. New scheduled the cross builds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Have the same issue upgrading from bionic to cosmic. Updating appstream to the version from cosmic workedaround the problem. Please backport fix to bionic so that other people will be able to upgrade using the Ubuntu normal upgrade process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792752] Re: do-release-upgrade failed on ec2
The error in your log shows: insserv: warning: script 'S99startEverything' missing LSB tags and overrides insserv: warning: script 'startEverything.sh' missing LSB tags and overrides [...] insserv: There is a loop between service startEverything and udev if started insserv: loop involving service udev at depth 1 insserv: There is a loop at service startEverything if started insserv: Starting startEverything.sh depends on grub-common and therefore on system facility `$all' which can not be true! [...] You appear to have a local init script, /etc/init.d/startEverything.sh, which is not a valid LSB init script and therefore causes problems on upgrade when trying to calculate init script dependencies. It's a problem that this is treated as a fatal error in the upgrader. Nevertheless, this script probably isn't going to do what you want it to post-upgrade due to the lack of correct init script dependency declarations. You will want to either adjust this init script to contain a proper LSB init header, or remove it from your system, and try the upgrade again with 'sudo apt-get -f install && sudo apt-get dist- upgrade'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1792752 Title: do-release-upgrade failed on ec2 Status in sysvinit package in Ubuntu: New Bug description: I tried upgrading my ec2 instance from 14.04 using sudo do-release- upgrade I get this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initscripts 2.88dsf-59.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-158.208-generic 3.13.11-ckt39 Uname: Linux 3.13.0-158-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Sep 15 22:25:52 2018 Ec2AMI: ami-066736b10f23b32a3 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-south-1a Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: sysvinit Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-15 (0 days ago) mtime.conffile..etc.default.rcS: 2015-03-25T11:52:34.180359 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1792752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
