[Touch-packages] [Bug 1681025] Re: dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd-timesyncd.service
Please find the attached patch service that was used to delay the network initialization so that it is not affected by the time-change by systemd-timesyncd.service. This may not exactly be an acceptable solution but demonstrates how equivalent changes can be performed to arrive at the solution. ** Attachment added: "delayNetwork.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681025/+attachment/4857992/+files/delayNetwork.service -- 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/1681025 Title: dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd- timesyncd.service Status in network-manager package in Ubuntu: New Bug description: System Information: Description: Ubuntu 16.04.2 LTS Release: 16.04 Package Information: network-manager: Installed: (none) Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Expected Behavior: The system has one ethernet interface ens160 that is expected to be assigned an IPv4 address using DHCP as part of the bootup process so that services that depends on presence of IPv4 address do not fail to initialize during the boot process. Problem Behavior: The ethernet interface ens160 was UP but no IPv4 address was assigned inspite of correct response from the DHCP server, thereby causing the services that depends on presence of IPv4 address to fail during the boot process. Problem Details: The default 16.04.2 LTS server installed in a VMWare virtual machine running on SuperMicro server using ESXi 6 fails to obtain an IP address from a DHCP server during system startup when there is a simultaneous time change as evidenced by "systemd[1]: Time has been changed" entry in syslog. The system successfully obtains the IP address after significant delay (ranging from 2 - 5 minutes) after system startup. Note that the system has open-vmware-tools package and the VMWare tools settings are set to NOT synchronize the guest time, thereby eliminating any scope of interference from virtualization host (The host itself is set to use NTP synchronization and has correct timing). Wireshark was used to sniff the BOOTP messages. When system is rebooted, system sends a DHCP Release to the DHCP server. When system starts, it broadcasts a valid DHCP Discover to network and received a valid DHCP Offer from the network within 4 secs. Note that a "Time has been changed" log appears just before dhclient logs "No DHCPOFFERS received" in syslog. (The time appears to be moved ahead by around 6 mins.) After about 4 minutes, system broadcasts a valid DHCP Discover to which DHCP server responds with DHCP Offer, system responds with DHCP Request and DHCP server responds with DHCP Ack and the system is assigned its IP address. The dhclient logs in syslog concurs with the wireshark trace: Apr 6 18:39:05 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 255.255.255.255 port 67 interval 3 (xid=0x92322e17) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 255.255.255.255 port 67 interval 8 (xid=0x92322e17) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPREQUEST of 192.168.1.161 on ens160 to 255.255.255.255 port 67 (xid=0x172e3292) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPOFFER of 192.168.1.161 from 192.168.1.1 Apr 6 18:39:09 etCorgServer dhclient[1071]: DHCPACK of 192.168.1.161 from 192.168.1.1 Apr 6 18:39:09 etCorgServer dhclient[1071]: bound to 192.168.1.161 -- renewal in 33171 seconds. An attempt to release and reacquire the IP address after the system is up and running always succeeds immediately with the aforesaid "happy" usecase. Workaround Attempted: Turning off systemd-timesyncd.service always allows dhclient to immediately assign the IP address during the boot process. Turning it on leads to the above problem usecase with very high probability. Based on this observation, an assumption can be made that the time synchronization happens to overlap the DHCP processing performed by dhclient. There is a time-change which causes the DHCP Offer sent by the DHCP server to be ignored and dhclient to snooze for a long time before attempting another DHCP Discover message to the server. Under such circumstances, the services that depend on presence of an IP address fail. Attempted Workaround: Above assumption was further used to create a delayNetwork.service patch one-shot systemd ser
[Touch-packages] [Bug 1681025] Re: dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd-timesyncd.service
Please find the attached wireshark trace of the BOOTP messages for problem usecase, whereby the system was rebooted. ** Attachment added: "Wireshark trace of the problem reboot sequence." https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681025/+attachment/4857990/+files/bootp.pcapng -- 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/1681025 Title: dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd- timesyncd.service Status in network-manager package in Ubuntu: New Bug description: System Information: Description: Ubuntu 16.04.2 LTS Release: 16.04 Package Information: network-manager: Installed: (none) Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Expected Behavior: The system has one ethernet interface ens160 that is expected to be assigned an IPv4 address using DHCP as part of the bootup process so that services that depends on presence of IPv4 address do not fail to initialize during the boot process. Problem Behavior: The ethernet interface ens160 was UP but no IPv4 address was assigned inspite of correct response from the DHCP server, thereby causing the services that depends on presence of IPv4 address to fail during the boot process. Problem Details: The default 16.04.2 LTS server installed in a VMWare virtual machine running on SuperMicro server using ESXi 6 fails to obtain an IP address from a DHCP server during system startup when there is a simultaneous time change as evidenced by "systemd[1]: Time has been changed" entry in syslog. The system successfully obtains the IP address after significant delay (ranging from 2 - 5 minutes) after system startup. Note that the system has open-vmware-tools package and the VMWare tools settings are set to NOT synchronize the guest time, thereby eliminating any scope of interference from virtualization host (The host itself is set to use NTP synchronization and has correct timing). Wireshark was used to sniff the BOOTP messages. When system is rebooted, system sends a DHCP Release to the DHCP server. When system starts, it broadcasts a valid DHCP Discover to network and received a valid DHCP Offer from the network within 4 secs. Note that a "Time has been changed" log appears just before dhclient logs "No DHCPOFFERS received" in syslog. (The time appears to be moved ahead by around 6 mins.) After about 4 minutes, system broadcasts a valid DHCP Discover to which DHCP server responds with DHCP Offer, system responds with DHCP Request and DHCP server responds with DHCP Ack and the system is assigned its IP address. The dhclient logs in syslog concurs with the wireshark trace: Apr 6 18:39:05 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 255.255.255.255 port 67 interval 3 (xid=0x92322e17) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 255.255.255.255 port 67 interval 8 (xid=0x92322e17) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPREQUEST of 192.168.1.161 on ens160 to 255.255.255.255 port 67 (xid=0x172e3292) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPOFFER of 192.168.1.161 from 192.168.1.1 Apr 6 18:39:09 etCorgServer dhclient[1071]: DHCPACK of 192.168.1.161 from 192.168.1.1 Apr 6 18:39:09 etCorgServer dhclient[1071]: bound to 192.168.1.161 -- renewal in 33171 seconds. An attempt to release and reacquire the IP address after the system is up and running always succeeds immediately with the aforesaid "happy" usecase. Workaround Attempted: Turning off systemd-timesyncd.service always allows dhclient to immediately assign the IP address during the boot process. Turning it on leads to the above problem usecase with very high probability. Based on this observation, an assumption can be made that the time synchronization happens to overlap the DHCP processing performed by dhclient. There is a time-change which causes the DHCP Offer sent by the DHCP server to be ignored and dhclient to snooze for a long time before attempting another DHCP Discover message to the server. Under such circumstances, the services that depend on presence of an IP address fail. Attempted Workaround: Above assumption was further used to create a delayNetwork.service patch one-shot systemd service that causes the networking service to delay networking.service until time-sync.target is reached by the systemd-timesyncd.service. Such patch seems to ca
[Touch-packages] [Bug 1681025] [NEW] dhclient fails to assign IP address during system boot inspite of valid DHCP Offer when time change is performed by systemd-timesyncd.service
Public bug reported: System Information: Description:Ubuntu 16.04.2 LTS Release:16.04 Package Information: network-manager: Installed: (none) Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Expected Behavior: The system has one ethernet interface ens160 that is expected to be assigned an IPv4 address using DHCP as part of the bootup process so that services that depends on presence of IPv4 address do not fail to initialize during the boot process. Problem Behavior: The ethernet interface ens160 was UP but no IPv4 address was assigned inspite of correct response from the DHCP server, thereby causing the services that depends on presence of IPv4 address to fail during the boot process. Problem Details: The default 16.04.2 LTS server installed in a VMWare virtual machine running on SuperMicro server using ESXi 6 fails to obtain an IP address from a DHCP server during system startup when there is a simultaneous time change as evidenced by "systemd[1]: Time has been changed" entry in syslog. The system successfully obtains the IP address after significant delay (ranging from 2 - 5 minutes) after system startup. Note that the system has open-vmware-tools package and the VMWare tools settings are set to NOT synchronize the guest time, thereby eliminating any scope of interference from virtualization host (The host itself is set to use NTP synchronization and has correct timing). Wireshark was used to sniff the BOOTP messages. When system is rebooted, system sends a DHCP Release to the DHCP server. When system starts, it broadcasts a valid DHCP Discover to network and received a valid DHCP Offer from the network within 4 secs. Note that a "Time has been changed" log appears just before dhclient logs "No DHCPOFFERS received" in syslog. (The time appears to be moved ahead by around 6 mins.) After about 4 minutes, system broadcasts a valid DHCP Discover to which DHCP server responds with DHCP Offer, system responds with DHCP Request and DHCP server responds with DHCP Ack and the system is assigned its IP address. The dhclient logs in syslog concurs with the wireshark trace: Apr 6 18:39:05 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 255.255.255.255 port 67 interval 3 (xid=0x92322e17) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPDISCOVER on ens160 to 255.255.255.255 port 67 interval 8 (xid=0x92322e17) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPREQUEST of 192.168.1.161 on ens160 to 255.255.255.255 port 67 (xid=0x172e3292) Apr 6 18:39:08 etCorgServer dhclient[1071]: DHCPOFFER of 192.168.1.161 from 192.168.1.1 Apr 6 18:39:09 etCorgServer dhclient[1071]: DHCPACK of 192.168.1.161 from 192.168.1.1 Apr 6 18:39:09 etCorgServer dhclient[1071]: bound to 192.168.1.161 -- renewal in 33171 seconds. An attempt to release and reacquire the IP address after the system is up and running always succeeds immediately with the aforesaid "happy" usecase. Workaround Attempted: Turning off systemd-timesyncd.service always allows dhclient to immediately assign the IP address during the boot process. Turning it on leads to the above problem usecase with very high probability. Based on this observation, an assumption can be made that the time synchronization happens to overlap the DHCP processing performed by dhclient. There is a time-change which causes the DHCP Offer sent by the DHCP server to be ignored and dhclient to snooze for a long time before attempting another DHCP Discover message to the server. Under such circumstances, the services that depend on presence of an IP address fail. Attempted Workaround: Above assumption was further used to create a delayNetwork.service patch one-shot systemd service that causes the networking service to delay networking.service until time-sync.target is reached by the systemd-timesyncd.service. Such patch seems to cause dhclient to always assign IP address during boot process. However, it would be desirable to ensure that dhclient and/or the networking.service take correct steps to protect itself against race conditions that may arise due to time changes affected by the systemd-timesyncd.service. At the very least, possibility of time change during such critical and vulnerable system component initialization must be minimized by isolating the time change to occur during a bootup phase when such components are not being initialized. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 22:50:11 2
[Touch-packages] [Bug 1337576] Re: dash inability - cron starts binary with /bin/sh
[Expired for dash (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dash (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1337576 Title: dash inability - cron starts binary with /bin/sh Status in dash package in Ubuntu: Expired Bug description: -- Problem Description -- CRON uses shell to start a binary executable defined in crontab, which is a waste of the resources for the extra shell process hanging in the system. It's supposed to run it directly with exec system call. *** Here are some command outputs to see the extra process(12327) and relevant information: *** # ps -ef | grep -e CRON -e PMLnx root 12326 771 0 13:59 ?00:00:00 CRON root 12327 12326 0 13:59 ?00:00:00 /bin/sh -c /var/perf/pm/bin/daemon_PMLnx <--- extra layer, a waste root 12328 12327 0 13:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx # crontab -l 59 * * * * /var/perf/pm/bin/daemon_PMLnx # file /var/perf/pm/bin/daemon_PMLnx /var/perf/pm/bin/daemon_PMLnx: ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.0, BuildID[sha1]=1761d6d97eabb4e52870cb517fe6bf457e5bf89e, stripped # uname -a Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux # dpkg -l cron Name VersionArchitecture Description +++-=-==-=-= ii cron 3.0pl1-124ubuntu2 ppc64el process scheduling daemon *** Expect cron to directly execute a binary like this *** # ps -ef | grep -e CRON -e PMLnx root 2293 2223 0 09:59 ?00:00:00 /usr/sbin/CRON -n root 2294 2293 0 09:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx # uname -a Linux hulala 3.12.15-3-default #1 SMP Wed Apr 2 17:08:55 UTC 2014 (69c2ea8) ppc64le ppc64le ppc64le GNU/Linux # cat /etc/SuSE-release SUSE Linux Enterprise Server 12 (ppc64le) VERSION = 12 PATCHLEVEL = 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1337576/+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 1389164] Re: Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab
[Expired for mountall (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mountall (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1389164 Title: Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab Status in mountall package in Ubuntu: Expired Bug description: Problem Description It seems the remote mounts in my /etc/fstab file are not being automatically mounted at bootup with ppc64le Ubuntu 14.10. This leads to some of my upstart scripts not running because they require certain mounts being available. I can give access to the machine via SSH key or password. Using mount -a or any other mount command works just fine after bootup. I don't personally notice a problem in logs with mounts. The machine is a VM hosted on a Power8 PowerKVM system running: # uname -a Linux kvm10d724t.rtp.raleigh.ibm.com 3.10.23-1700.pkvm2_1.2.ppc64 #1 SMP Mon Jun 2 20:14:25 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux # cat /etc/base-release IBM_PowerKVM release 2.1.0 build 18 Service (pkvm2_1) VM details: # uname -a Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.10 DISTRIB_CODENAME=utopic DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)" If I recall correctly, we installed the 141002 daily build of Utopic Unicorn (14.10). I have implemented a workaround for now. I updated /etc/fstab to use IP addresses instead of names, put "mount -a" as the first non- commented line in /etc/init.d/mountnfs.sh and updated the crontab to run the jobs I had in the upstart configs. This works until the problem is fixed. ---uname output--- Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = ppc64le Steps to Reproduce = Without the workaround implemented and NFS mounts in your /etc/fstab, boot up the machine. It should be evident the mount points aren't there with df -h. == Comment: #3 - Breno Henrique Leitao - == I was able to reproduce this problem. NFS is not mounted automatically, but it is when you run 'mount -a'. I also toggled ASYNCMOUNTNFS in /etc/defaults/rcS and no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1389164/+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 1579957] Re: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()
[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 mir in Ubuntu. https://bugs.launchpad.net/bugs/1579957 Title: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available() Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.12+15.04.20160504.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2c3cad3ba17d755e656dc7db06c77e7854c117b8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579957/+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 1579957] Re: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()
[Expired for mir (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mir (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579957 Title: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available() Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.12+15.04.20160504.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2c3cad3ba17d755e656dc7db06c77e7854c117b8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579957/+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 1579957] Re: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()
[Expired for Mir because there has been no activity for 60 days.] ** Changed in: mir Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579957 Title: Unity8 crashes in std::string::_Rep::_S_empty_rep_storage() from mir::client::rpc::MirProtobufRpcChannel::on_data_available() Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.12+15.04.20160504.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2c3cad3ba17d755e656dc7db06c77e7854c117b8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579957/+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 1648959] Re: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1648959 Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Expired Bug description: after installing updates via Software Updater Ubuntu version:16.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Sat Dec 10 10:52:01 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 MachineType: TOSHIBA Satellite L650 ProcKernelCmdLine: file=/cdrom/multiboot/hostname-16.04.1-desktop-amd64/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true persistent persistent-path=/multiboot/hostname-16.04.1-desktop-amd64 noprompt floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/hostname-16.04.1-desktop-amd64/casper/ initrd=/multiboot/hostname-16.04.1-desktop-amd64/casper/initrd.lz quiet splash --- debian-installer/language=cs keyboard-configuration/layoutcode?=cz RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: systemd Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-0CR008CZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L650 dmi.product.version: PSK1JE-0CR008CZ dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648959/+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 1681013] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
*** This bug is a duplicate of bug 1621396 *** https://bugs.launchpad.net/bugs/1621396 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 #1621396, 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/1681013/+attachment/4857928/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1681013/+attachment/4857931/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1681013/+attachment/4857937/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1681013/+attachment/4857939/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1681013/+attachment/4857940/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1681013/+attachment/4857942/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1681013/+attachment/4857944/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1621396 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1681013 Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() Status in systemd package in Ubuntu: New Bug description: I ran the Software Center, and this bug came up. Ubuntu GNOME 17.04 beta 2 GNOME 3.24.0 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Apr 7 19:39:42 2017 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2017-04-07 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SA ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=c50922c4-a4e1-4c6b-9b00-ddb215d63d2f ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-232.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-232.so sd_event_run () from /lib/systemd/libsystemd-shared-232.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/17/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 0VCN18WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad FLEX 4-1470 dmi.modalias: dmi:bvnLENOVO:bvr0VCN18WW(V1.03):bd05/17/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470: dmi.product.name: 80SA dmi.product.version: Lenovo ideapad FLEX 4-1470 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681013/+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 1654918] Re: No Internet access with default of Automatic (DHCP) & current kernel
also seen in Ubuntu-Gnome install ** Also affects: network-manager Importance: Undecided Status: New -- 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/1654918 Title: No Internet access with default of Automatic (DHCP) & current kernel Status in Linux: New Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh 17.04 install, wireless router connects without any issue but there is no internet connection/access. This continues thru disconnecting, reconnecting, rebooting ect, Nothing.. If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & manually add Google DNS nameservers: then internet is enabled. screen attached Note this also affects ethernet, not just wireless Hardware is: description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:08:00.0 logical name: wlp8s0 version: 73 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 link=ye s multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:c240-c2401fff To note: this hardware works perfectly in 14.04 > 16.04 Add. note; issue doesn't arise with 4.11.x kernel ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 8 22:08:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108) IpRoute: default via 192.168.1.1 dev wlp8s0 proto static metric 600 169.254.0.0/16 dev wlp8s0 scope link metric 1000 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp8s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 06F21A fb815a75-4091-455e-b73d-2c1f2d97220f /org/freedesktop/NetworkManager/ActiveConnection/0 enp7s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1654918/+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 1674201] Re: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it
This bug was fixed in the package systemd - 232-21ubuntu2 --- systemd (232-21ubuntu2) zesty; urgency=medium * pkgconfig: Cherrypick upstream fix to libdir locations in .pc files (LP: #1674201) -- Dimitri John Ledkov Tue, 28 Mar 2017 16:59:14 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1674201 Title: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Bug description: Mir fails to build on arm64 cross-compiled: [ 11%] Linking CXX shared library ../../lib/libmirplatform.so /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: cannot find -ludev /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: cannot find -ludev collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1674201/+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 1673860] Re: systemd-resolved unit should run Before=network-online.target
This bug was fixed in the package systemd - 232-21ubuntu2 --- systemd (232-21ubuntu2) zesty; urgency=medium * pkgconfig: Cherrypick upstream fix to libdir locations in .pc files (LP: #1674201) -- Dimitri John Ledkov Tue, 28 Mar 2017 16:59:14 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => 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/1673860 Title: systemd-resolved unit should run Before=network-online.target Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Bug description: === Begin SRU Template === [Impact] For releases using systemd-resolved (yakkety and zesty); the unit configuration does not require that the service be active before allowing systemd to reach 'network-online.target' which is a special target used to allow other units which require networking access to run. In some cases, units which run After=network-online.target may encounter DNS failures if systemd-resolved is not yet completely active. The fix is to add Before=network-online.target to the Unit directives for systemd-resolved.service. [Test Case] 1. lxc launch ubuntu-daily:yakkety y1 2. lxc exec y1 -- journalctl -o short-precise \ --unit systemd-resolved --unit network-online.target 3. Check order of units; If 'Reached target Network is Online' is listed before 'Started Network Name Resolution', then DNS may not be up. Example FAIL output: # apt-cache policy systemd systemd: Installed: 231-9ubuntu3 Candidate: 231-9ubuntu3 Version table: *** 231-9ubuntu3 500 500 http://archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages # journalctl -o short-precise -u systemd-resolved -u network-online.target -- Logs begin at Thu 2017-03-23 21:22:42 UTC, end at Thu 2017-03-23 21:22:49 UTC. -- Mar 23 21:22:47.173454 y1 systemd[1]: Reached target Network is Online. Mar 23 21:22:47.197566 y1 systemd[1]: systemd-resolved.service: Failed to reset devices.list: Operation not permitted Mar 23 21:22:47.198023 y1 systemd[1]: Starting Network Name Resolution... Mar 23 21:22:47.207216 y1 systemd-resolved[438]: Positive Trust Anchors: Mar 23 21:22:47.207265 y1 systemd-resolved[438]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3 Mar 23 21:22:47.207319 y1 systemd-resolved[438]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add Mar 23 21:22:47.216370 y1 systemd-resolved[438]: Using system hostname 'y1'. Mar 23 21:22:47.237441 y1 systemd-resolved[438]: Switching to system DNS server 10.245.119.1. Mar 23 21:22:47.399614 y1 systemd[1]: Started Network Name Resolution. Example PASS output: # journalctl -o short-precise -u systemd-resolved -u network-online.target -- Logs begin at Thu 2017-03-23 21:25:08 UTC, end at Thu 2017-03-23 21:25:11 UTC. -- Mar 23 21:25:10.206276 y1 systemd[1]: systemd-resolved.service: Failed to reset devices.list: Operation not permitted Mar 23 21:25:10.206685 y1 systemd[1]: Starting Network Name Resolution... Mar 23 21:25:10.229430 y1 systemd-resolved[445]: Positive Trust Anchors: Mar 23 21:25:10.229449 y1 systemd-resolved[445]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde3 Mar 23 21:25:10.229491 y1 systemd-resolved[445]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-add Mar 23 21:25:10.229759 y1 systemd-resolved[445]: Using system hostname 'y1'. Mar 23 21:25:10.231969 y1 systemd-resolved[445]: Switching to system DNS server 10.245.119.1. Mar 23 21:25:10.291591 y1 systemd[1]: Started Network Name Resolution. Mar 23 21:25:10.291944 y1 systemd[1]: Reached target Network is Online. [Regression Potential] Changing order in boot can be dangerous. This is a possiblity of units using the defaults in /etc/resolv.conf (which doesn't point to systemd-resolved until later during boot) would now run when /etc/resolv.conf points to systemd-resolved service (127.0.0.53). [Original Description] 1) Xenial, Yakkety and Zesty; (Xenial is affected if you're using networkd and resolved, but it's not the default) 2) 229-4ubuntu16, 231-9ubuntu3, 232-18ubuntu1 respectively to (1) 3) DNS resolution should be available once systemd has reached 'network-online.target' state 4) Sometimes systemd-resolved has not become active prior to network-online.target and DNS service is not available. The remaining issue for the systemd-resolved.service unit is that it needs to include a Before=network-online.target to ensure it's ordered to run before system
[Touch-packages] [Bug 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild
This bug was fixed in the package pygobject-2 - 2.28.6-12ubuntu2 --- pygobject-2 (2.28.6-12ubuntu2) zesty; urgency=medium * Sync build-arch fix from debian, thanks to Emilio Monfort (LP: #1679835). * Use --disable-silent-rules also as per debian. -- Robert Bruce Park Thu, 06 Apr 2017 17:11:50 -0700 ** Changed in: pygobject-2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1679835 Title: pygobject-2 FTBFS on most arches during zesty test rebuild Status in pygobject-2 package in Ubuntu: Fix Released Bug description: pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on most (not amd64) arches during a test rebuild of zesty. The build log can be found here: https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386 .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz The failure seems to be due to the following: debian/rules build-arch make: *** No rule to make target 'build-arch'. Stop. dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 1681001] [NEW] des plantages
Public bug reported: Bonjour, Mon ordi se fige régulièrement et très souvent par moment la connection internet s'arrête (filaire et wifi) et je perds des messqges assez long que j'étais entrain d'écrire. Merci de me dépanner, en espérant que ce n'est pas difficile. A bientôt. PS : S'il vous plait, ce serait bien l'aide en français. Merci encore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 8 03:08:26 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 4.4.0-66-generic, x86_64: installed ndiswrapper, 1.60, 4.4.0-70-generic, x86_64: installed ndiswrapper, 1.60, 4.4.0-71-generic, x86_64: installed ndiswrapper, 1.60, 4.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:14c7] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:14c7] InstallationDate: Installed on 2016-11-10 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X75VC ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=84851d8d-6614-4115-b387-fc45015f127a ro drm.debug=0xe intel_idle.max_cstate=1 plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X75VC.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X75VC 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.:bvrX75VC.202:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnX75VC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX75VC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X75VC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Apr 8 02:29:10 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5928 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1681001 Title: des plantages Status in xorg package in Ubuntu: New Bug description: Bonjour, Mon ordi se fige régulièrement et très souvent par moment la connection internet s'arrête (filaire et wifi) et je perds des messqges assez long que j'étais entrain d'écrire. Merci de me dépanner, en espérant que ce n'est pas difficile. A bientôt. PS : S'il vous plait, ce serait bien l'aide en français. Merci encore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 8 03:08:26 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 4.4.0-66-generic, x86_64: installed ndiswrapper, 1.60,
[Touch-packages] [Bug 1669655] Re: Adapt to new Nautilus icon name
** Changed in: humanity-icon-theme (Ubuntu) Assignee: (unassigned) => rahmadani (rahmadani) ** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => rahmadani (rahmadani) ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => rahmadani (rahmadani) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1669655 Title: Adapt to new Nautilus icon name Status in humanity-icon-theme package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Nautilus 3.24's app icon name is org.gnome.Nautilus instead of system- file-manager for better flatpak compatibility. I have updated ubuntu-themes and humanity-icon-theme for this change (adding a new symlink pointing to system-file-manager). ubuntu-themes is handled via bileto so I'll ask the appropriate people to sponsor that separately. DONE I pushed my change to the humanity bzr branch but I don't have upload rights for it so I'll need sponsorship for this: https://code.launchpad.net/~ubuntu-art-pkg/humanity/release/ I let other Ubuntu flavors know about this change at bug 1669663. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1669655/+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 1680976] Re: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1680976 Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package is unable to install. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.45.57 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: virginia 1835 F pulseaudio /dev/snd/controlC1: virginia 1835 F pulseaudio Date: Thu Mar 30 18:35:11 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=40ae2381-7761-48fd-8e94-c9e9b0fb4643 InstallationDate: Installed on 2017-03-12 (26 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK Computer Inc. K54HR ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=f5bd7ab4-fa8d-40b6-89a7-3966074160e8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 SourcePackage: initramfs-tools Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54HR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54HR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54HR.203:bd02/23/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K54HR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1680976/+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 1581302] Re: Monitor remains blanked with Intel Graphics
I'm experiencing this behavior with a Dell XPS 13 9360 Developer Edition I'm not running xfce. I'm using stock Unity, but lightdm is running. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1581302 Title: Monitor remains blanked with Intel Graphics Status in lightdm package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Confirmed Bug description: Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port or HDMI Running Xubuntu 16.04 - latest all current patches Sometimes the monitor remains blanked even when the session has reactivated. I have been able to reproduce this problem by letting the monitor remain in the 'blanked' state for > 60 minutes, or powering off the monitor. When the monitor is powered back on and the session is woken up with mouse or keyboard input, it does wake up but the monitor remains blanked. I was able to prove to myself the session was awake by leaving it with terminal opened to full screen with VIM running on an NFS mounted file system. I could type and save at the black monitor screen and see that the file got updates from a different system. So the session is "live" but the computer has forgotten to re-establish the DisplayPort link. An error appears in the lightdm logs about setting a CRTC, if you activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr --output DP1 --auto` it also registers that CRTC error. HOWEVER, if you ssh in from a different machine, tell bash to export DISPLAY=:0 (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the screen turns on again! This also happens on a Gigabyte BRIX system (same NUC reference design but in that case a core i3 rather than a Core i7). To reproduce, turn off the monitor, wait an hour, and turn it on again. You can also kill HUP the lightdm process and that will restart a new session (but open windows in the previous session are lost). So interesting questions, why does typing xrandr "locally" give you the error but running it from an ssh session work? Since xrandr and restarting the session can both "fix" the problem, the driver seems to know how to turn the display on if told correctly. How can I find out where the code is getting the CRTC error? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu May 12 20:33:01 2016 InstallationDate: Installed on 2016-05-08 (4 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch LightdmLog: [+80180.09s] DEBUG: Seat seat0 changes active session to [+80189.53s] DEBUG: Seat seat0 changes active session to 64 [+80222.67s] DEBUG: Seat seat0 changes active session to c4 [+80222.67s] DEBUG: Session c4 is already active SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581302/+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 1680811] Re: Request to add wireguard interface to interface-order
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1680811 Title: Request to add wireguard interface to interface-order Status in resolvconf package in Ubuntu: Confirmed Bug description: This started from https://github.com/jlund/streisand/issues/557. Basically wg* namespace is not in interface-order and acts last in * scope, and this makes resolv.conf to stay in the same state. I suggest the following change: :/etc/resolvconf/interface-order # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo +wg* tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* @(br|eth)*([^.]).inet6 @(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)*([^.]).inet @(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811/+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 1678507] Re: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1678507 Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8.2 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportLog: ERROR: apport (pid 6288) Sat Apr 1 15:23:30 2017: called for pid 6216, signal 11, core limit 0 ERROR: apport (pid 6288) Sat Apr 1 15:23:30 2017: executable: /usr/bin/webbrowser-app (command line "webbrowser-app") ERROR: apport (pid 6288) Sat Apr 1 15:23:30 2017: debug: session gdbus call: (true,) ERROR: apport (pid 6288) Sat Apr 1 15:23:55 2017: wrote report /var/crash/_usr_bin_webbrowser-app.1000.crash ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Sat Apr 1 14:47:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-31 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: apport Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1678507/+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 1678507] Re: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1678507 Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8.2 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportLog: ERROR: apport (pid 6288) Sat Apr 1 15:23:30 2017: called for pid 6216, signal 11, core limit 0 ERROR: apport (pid 6288) Sat Apr 1 15:23:30 2017: executable: /usr/bin/webbrowser-app (command line "webbrowser-app") ERROR: apport (pid 6288) Sat Apr 1 15:23:30 2017: debug: session gdbus call: (true,) ERROR: apport (pid 6288) Sat Apr 1 15:23:55 2017: wrote report /var/crash/_usr_bin_webbrowser-app.1000.crash ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Sat Apr 1 14:47:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-31 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: apport Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1678507/+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 1678594] Re: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/sha
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1678594 Title: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 Status in libav package in Ubuntu: New Bug description: 'Error: Brokencount > 0' ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Sun Apr 2 16:15:39 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.11 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.9 DpkgTerminalLog: Preparing to unpack .../libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb ... Unpacking libavutil52:i386 (6:9.20-0ubuntu0.14.04.1) over (6:9.11-2ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 DuplicateSignature: package:libavutil52:6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 InstallationDate: Installed on 2017-03-22 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: libav Title: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1678594/+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 1678594] Re: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/sha
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 libav in Ubuntu. https://bugs.launchpad.net/bugs/1678594 Title: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 Status in libav package in Ubuntu: New Bug description: 'Error: Brokencount > 0' ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Sun Apr 2 16:15:39 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.11 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.9 DpkgTerminalLog: Preparing to unpack .../libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb ... Unpacking libavutil52:i386 (6:9.20-0ubuntu0.14.04.1) over (6:9.11-2ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libavutil52_6%3a9.20-0ubuntu0.14.04.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 DuplicateSignature: package:libavutil52:6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 InstallationDate: Installed on 2017-03-22 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: libav Title: package libavutil52 6:9.20-0ubuntu0.14.04.1 [modified: usr/share/doc/libavutil52/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libavutil52/changelog.Debian.gz', which is different from other instances of package libavutil52:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1678594/+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 1678504] Re: Wifi does not connect to network
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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1678504 Title: Wifi does not connect to network Status in network-manager package in Ubuntu: New Bug description: I do not speak the jargon language you guys used to, so bear with me. Although I can only try my best as to describe the trouble that I'm going through with my network manager, I really don't know whats going wrong? Moments ago I filled-out this field and when I was done and hit the "Submit Bug Report" button, I was brought to a blank page stating network issues. Whether I go and start Firefox, Thunderbird, or conduct an update through "update manager" or command line, I get a network error. My way of working around this issue is to initialize Chromium. When I start Chromium I'll go to ebay.com or any site I normally peruse, I get a blank page, it automatically refreshes and I'd finally get a web page open up like normal. I close chromium, conduct an update, open FireFox or start Chromium and it'll work like normal. But if I spend long enough time, I am no longer able to browse. Redirect me if I filled out the wrong bug report Please help ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Apr 1 12:12:08 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-25 (341 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.9 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 C8A090 e897215f-3697-44f8-9676-c912b3554dad /org/freedesktop/NetworkManager/ActiveConnection/5 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1678504/+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 1679939] Re: package libdrm2:amd64 2.4.70-1~ubuntu16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1679939 Title: package libdrm2:amd64 2.4.70-1~ubuntu16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libdrm package in Ubuntu: New Bug description: Facing so many problems... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm2:amd64 2.4.70-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 5 12:18:26 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgHistoryLog: Start-Date: 2017-04-05 12:18:20 Commandline: apt-get install -f Requested-By: abhishek (1000) Upgrade: libdrm2:i386 (2.4.67-1ubuntu0.16.04.2, 2.4.70-1~ubuntu16.04.1) DuplicateSignature: package:libdrm2:amd64:2.4.70-1~ubuntu16.04.1 Setting up libdrm2:i386 (2.4.70-1~ubuntu16.04.1) ... dpkg: error processing package libdrm2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2016-11-30 (125 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=21523131-9895-4edd-88f5-3199f38e8d77 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libdrm Title: package libdrm2:amd64 2.4.70-1~ubuntu16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.44 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd02/05/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 5 12:14:01 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1679939/+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 1679939] Re: package libdrm2:amd64 2.4.70-1~ubuntu16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1679939 Title: package libdrm2:amd64 2.4.70-1~ubuntu16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libdrm package in Ubuntu: New Bug description: Facing so many problems... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm2:amd64 2.4.70-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 5 12:18:26 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgHistoryLog: Start-Date: 2017-04-05 12:18:20 Commandline: apt-get install -f Requested-By: abhishek (1000) Upgrade: libdrm2:i386 (2.4.67-1ubuntu0.16.04.2, 2.4.70-1~ubuntu16.04.1) DuplicateSignature: package:libdrm2:amd64:2.4.70-1~ubuntu16.04.1 Setting up libdrm2:i386 (2.4.70-1~ubuntu16.04.1) ... dpkg: error processing package libdrm2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2016-11-30 (125 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=21523131-9895-4edd-88f5-3199f38e8d77 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libdrm Title: package libdrm2:amd64 2.4.70-1~ubuntu16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.44 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd02/05/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 5 12:14:01 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1679939/+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/List
[Touch-packages] [Bug 1680976] Re: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- 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/1680976 Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: package is unable to install. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.45.57 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: virginia 1835 F pulseaudio /dev/snd/controlC1: virginia 1835 F pulseaudio Date: Thu Mar 30 18:35:11 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=40ae2381-7761-48fd-8e94-c9e9b0fb4643 InstallationDate: Installed on 2017-03-12 (26 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK Computer Inc. K54HR ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=f5bd7ab4-fa8d-40b6-89a7-3966074160e8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 SourcePackage: initramfs-tools Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54HR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54HR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54HR.203:bd02/23/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K54HR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1680976/+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 1680976] [NEW] package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: package is unable to install. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.45.57 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: virginia 1835 F pulseaudio /dev/snd/controlC1: virginia 1835 F pulseaudio Date: Thu Mar 30 18:35:11 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=40ae2381-7761-48fd-8e94-c9e9b0fb4643 InstallationDate: Installed on 2017-03-12 (26 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK Computer Inc. K54HR ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=f5bd7ab4-fa8d-40b6-89a7-3966074160e8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 SourcePackage: initramfs-tools Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54HR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54HR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54HR.203:bd02/23/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K54HR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- 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/1680976 Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: package is unable to install. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.45.57 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: virginia 1835 F pulseaudio /dev/snd/controlC1: virginia 1835 F pulseaudio Date: Thu Mar 30 18:35:11 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=40ae2381-7761-48fd-8e94-c9e9b0fb4643 InstallationDate: Installed on 2017-03-12 (26 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK Computer Inc. K54HR ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=f5bd7ab4-fa8d-40b6-89a7-3966074160e8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 SourcePackage: initramfs-tools Title: package linux-image-generic 4.8.0.45.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54HR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54HR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54HR.203:bd02/23/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K54HR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1680976/+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 1680974] [NEW] libegl1-mesa depends on libmirclient9
Public bug reported: Mir is dead. libegl1-mesa should no longer depend on it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libegl1-mesa 17.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Fri Apr 7 23:55:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1197 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 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: Fri Apr 7 20:23:48 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu zesty -- 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/1680974 Title: libegl1-mesa depends on libmirclient9 Status in mesa package in Ubuntu: New Bug description: Mir is dead. libegl1-mesa should no longer depend on it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libegl1-mesa 17.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Fri Apr 7 23:55:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1197 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.cha
[Touch-packages] [Bug 1680964] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()
*** This bug is a duplicate of bug 1663954 *** https://bugs.launchpad.net/bugs/1663954 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 #1663954, 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/1680964/+attachment/4857699/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1680964/+attachment/4857701/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1680964/+attachment/4857705/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1680964/+attachment/4857706/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1680964/+attachment/4857707/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1680964/+attachment/4857709/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1680964/+attachment/4857710/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1663954 ** 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 signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1680964 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() Status in signon-ui package in Ubuntu: New Bug description: connecting Kontact with Owncloud CalDav/CardDav ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 7 22:38:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2017-04-07 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) ProcCmdline: /usr/bin/signon-ui Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1680964/+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 1680957] [NEW] [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: missing audio output ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaon 3414 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 8 02:26:22 2017 InstallationDate: Installed on 2017-04-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaon 3414 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.8 dmi.board.name: 0664DJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1680957 Title: [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: missing audio output ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaon 3414 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 8 02:26:22 2017 InstallationDate: Installed on 2017-04-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaon 3414 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.8 dmi.board.name: 0664DJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1680957/+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 1680952] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()
*** This bug is a duplicate of bug 1663954 *** https://bugs.launchpad.net/bugs/1663954 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 #1663954, 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/1680952/+attachment/4857635/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1680952/+attachment/4857637/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1680952/+attachment/4857641/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1680952/+attachment/4857642/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1680952/+attachment/4857643/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1680952/+attachment/4857645/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1680952/+attachment/4857646/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1663954 ** 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 signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1680952 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() Status in signon-ui package in Ubuntu: New Bug description: I tried to add GTalk IM account but the Google button did nothing and then the crash report popped up. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 7 23:08:34 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2014-03-07 (1126 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) ProcCmdline: /usr/bin/signon-ui Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: Upgraded to zesty on 2017-03-29 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (thunderbird:2467): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (thunderbird:2467): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (rhythmbox:2464): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (thunderbird:2456): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (thunderbird:2456): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1680952/+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 1283610] Re: indicator-datetime-service crashed with SIGABRT in g_assertion_message()
happy to help -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1283610 Title: indicator-datetime-service crashed with SIGABRT in g_assertion_message() Status in Indicator Date and Time: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Upgraded from 13.10 to 14.04 alpha 1 via update manager -d. This popped up after reboot and subsequent login. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140219.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Feb 22 16:52:41 2014 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2013-09-14 (161 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: PATH=(custom, user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: indicator-datetime StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () unity::indicator::datetime::PlannerEds::Impl::on_source_enabled(_ESourceRegistry*, _ESource*, void*) () g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-datetime-service crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-02-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283610/+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 1679849] Re: vim FTBFS during a rebuild test for zesty
This builds for me locally, so I think this may have fixed itself. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1679849 Title: vim FTBFS during a rebuild test for zesty Status in vim package in Ubuntu: Invalid Bug description: vim version 2:8.0.0095-1ubuntu3 failed to build from source on amd64 during an archive rebuild test for zesty. The build log can be found here: https://launchpadlibrarian.net/312225140/buildlog_ubuntu-zesty- amd64.vim_2%3A8.0.0095-1ubuntu3_BUILDING.txt.gz The failure seems to be: rm -rf *.out *.failed *.res *.rej *.orig test.log messages test.out X* viminfo tiny.vim small.vim mbyte.vim mzscheme.vim lua.vim test.ok benchmark.out valgrind.* make[3]: Leaving directory '/<>/src/testdir' if test -d po; then \ cd po; /usr/bin/make checkclean; \ fi make[3]: Entering directory '/<>/src/po' Makefile:4: ../auto/config.mk: No such file or directory make[3]: *** No rule to make target '../auto/config.mk'. Stop. make[3]: Leaving directory '/<>/src/po' Makefile:2181: recipe for target 'testclean' failed make[2]: *** [testclean] Error 2 make[2]: *** Waiting for unfinished jobs cp config.mk.dist auto/config.mk make[2]: Leaving directory '/<>/src' Makefile:36: recipe for target 'distclean' failed make[1]: *** [distclean] Error 2 make[1]: Leaving directory '/<>' debian/rules:251: recipe for target 'autoconf-stamp' failed make: *** [autoconf-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1679849/+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 1680937] [NEW] package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of
Public bug reported: Problem during standard "sudo apt upgrade" procedure ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3.2 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 20:55:38 2017 DuplicateSignature: package:libgtk-3-0:3.18.9-1ubuntu3.2 Unpacking libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.18.9-1ubuntu3.2) ... dpkg: error processing archive /var/cache/apt/archives/libgtk-3-0_3.18.9-1ubuntu3.3_amd64.deb (--unpack): trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2016-02-28 (404 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1680937 Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 Status in gtk+3.0 package in Ubuntu: New Bug description: Problem during standard "sudo apt upgrade" procedure ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3.2 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 20:55:38 2017 DuplicateSignature: package:libgtk-3-0:3.18.9-1ubuntu3.2 Unpacking libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.18.9-1ubuntu3.2) ... dpkg: error processing archive /var/cache/apt/archives/libgtk-3-0_3.18.9-1ubuntu3.3_amd64.deb (--unpack): trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2016-02-28 (404 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1680937/+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 1680937] Re: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of pa
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1680937 Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 Status in gtk+3.0 package in Ubuntu: New Bug description: Problem during standard "sudo apt upgrade" procedure ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.18.9-1ubuntu3.2 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 20:55:38 2017 DuplicateSignature: package:libgtk-3-0:3.18.9-1ubuntu3.2 Unpacking libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) over (3.18.9-1ubuntu3.2) ... dpkg: error processing archive /var/cache/apt/archives/libgtk-3-0_3.18.9-1ubuntu3.3_amd64.deb (--unpack): trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2016-02-28 (404 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.18.9-1ubuntu3.2 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1680937/+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 1662670] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-MfyGcj8Fq2: Connection refused
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1662670 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-MfyGcj8Fq2: Connection refused Status in dbus package in Ubuntu: Confirmed Bug description: Got this error after switching from Cinnamon to Xubuntu-Desktop nico@nico-lenovo-ubuntu:~$ dropbox stop Dropbox daemon stopped. nico@nico-lenovo-ubuntu:~$ dropbox start Starting Dropbox... ** (dropbox:3817): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-MfyGcj8Fq2: Connection refused Done! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dbus 1.10.10-1ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-37.39-lowlatency 4.8.16 Uname: Linux 4.8.0-37-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Feb 7 21:02:58 2017 InstallationDate: Installed on 2016-10-20 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1662670/+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 1631246] Re: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também est
** Also affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Changed in: account-plugins (Ubuntu) Status: New => Confirmed ** Tags added: package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1631246 Title: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit- options.d/api.twitter.com.conf', que também está no pacote account- plugin-twitter 0.12+16.04.20160126-0ubuntu1 Status in account-plugins package in Ubuntu: Confirmed Status in kaccounts-providers package in Ubuntu: Confirmed Bug description: Error during installation of KDE Plasma on Ubuntu 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 7 01:55:46 2016 ErrorMessage: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também está no pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-09-11 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: a tentar sobre-escrever '/etc/signon-ui/webkit-options.d/api.twitter.com.conf', que também está no pacote account-plugin-twitter 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631246/+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 1680921] Re: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libasyncns in Ubuntu. https://bugs.launchpad.net/bugs/1680921 Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libasyncns package in Ubuntu: New Bug description: did not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasyncns0:i386 0.8-5build1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 13:48:11 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 DuplicateSignature: package:libasyncns0:i386:0.8-5build1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libasyncns0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-05 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libasyncns Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libasyncns/+bug/1680921/+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 1680921] [NEW] package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Public bug reported: did not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasyncns0:i386 0.8-5build1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 13:48:11 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 DuplicateSignature: package:libasyncns0:i386:0.8-5build1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libasyncns0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-05 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libasyncns Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libasyncns (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libasyncns in Ubuntu. https://bugs.launchpad.net/bugs/1680921 Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libasyncns package in Ubuntu: New Bug description: did not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasyncns0:i386 0.8-5build1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 13:48:11 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 DuplicateSignature: package:libasyncns0:i386:0.8-5build1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libasyncns0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-05 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libasyncns Title: package libasyncns0:i386 0.8-5build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libasyncns/+bug/1680921/+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 1639815] Re: apt list output format
Hopefully this gets improved properly, but in the meantime here's an
alias that offers better convenience than 'apt search' for package name
search:
alias apts="apt list 2> /dev/null | sed 's/\// \//' | grep "
And a bulky, quick and dirty bash function for full description search:
aptse() { # temporary 'apt search' improvement
tput rmam; # no-wrap
apt search $1 2>/dev/null |# skip the interface warning
tail -n+3 |# skip unimportant sorting info
grep -v '^$' | # delete empty lines
sed 'N;s/\n//' | # append every second line
sed 's/\// \//' | # replace first '/' with space
awk '{$2="";$4="";print}' |# remove useless info
sed -r 's/(\[.*)installed(.*\])/\1i\2/' | # shorten
sed -r 's/(\[.*)automatic(.*\])/\1a\2/' | # shorten
sed -r 's/(\[.*),(.*\])/\1\2/' | # prettier shortened '[]'
egrep --color "$1|"# highlighting
tput smam; # wrap again
}
Since the search expression is always a pattern with grep, neither
suffers from the 'apt list' behaviour described in my previous comment
(https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1639815/comments/1).
--
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/1639815
Title:
apt list output format
Status in apt package in Ubuntu:
New
Bug description:
I'm trying to get used to the new 'apt' utility and have three
wishlist items (don't want to clutter the tracker with multiple
feature requests) in descending priority:
1. apt list firefox
In the output, can we please have a space after the package name, before the
slash?
A very convenient feature of apt-cache/aptitude is to search for a package,
then double click + middle click the name of a result to speedily select it and
paste it into the current prompt (which is prepared with e.g. an install, show
or depends command).
'apt list' appends '/repo,XXX' (where XXX is most often garbage... ehm, I
mean strings like 'now' or again 'other_repo,now') right after the package
name, which makes the double click select more than just a package name.
E.g. 'apt policy firefox/yakkety-updates' fails.
This would also be more convenient for awk scripts (despite the stable
interface warning).
2. apt list fox
Can we please have substring matching by default (or a storable user pref)
for 'apt list'?
'apt search' is _way_ too noisy (the three line output per package instead of
one line is just clutter).
But 'apt list' doesn't match like 'apt-cache search' (or aptitude). The
alternative is defaulting to 'apt l **' and then filling in between the
asterisks, or resorting to 'apt l|grep' as standard 'apt-cache search'
replacement.
I don't see the justification for the current exact searching in only the
package names. And there's still 'apt search' for searching the description.
3. apt sh
A minor complaint: all current apt commands complete once they are tabbed
when their string becomes unique, and append a space. Only 'apt show' in 16.10
(as opposed to 16.04) does not due to the undocumented showsrc command. This
often leads to 'apt showfirefox' after writing 'apt shfirefox', because
it's inconsistent with the other commands.
So, find another name for showsrc?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1639815/+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 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild
This is in -proposed, awaiting unblock ** Changed in: pygobject-2 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1679835 Title: pygobject-2 FTBFS on most arches during zesty test rebuild Status in pygobject-2 package in Ubuntu: Fix Committed Bug description: pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on most (not amd64) arches during a test rebuild of zesty. The build log can be found here: https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386 .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz The failure seems to be due to the following: debian/rules build-arch make: *** No rule to make target 'build-arch'. Stop. dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+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 1652463] Re: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland
** Changed in: gtk Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1652463 Title: gnome-terminal-server crashed with SIGSEGV in XSync() when launched from desktop under Wayland Status in GTK+: Fix Released Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: New Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that when I use the right-click menu to open Terminal from the desktop that a window looking like this shows up on the screen for about a second or less: Terminal_Opened_From_Desktop.png And then when it closes all the other Terminal sessions go with it instantly killing anything I've got running from any of the gnome- terminal windows which is really quite annoying and luckily I didn't have anything vital running from one at the time. But this could seriously cause something quite bad for another unsuspecting person. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 24 19:59:50 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-05-15 (223 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-terminal StacktraceTop: ?? () XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 gdk_window_process_all_updates () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libvte-2.91.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-terminal-server crashed with SIGSEGV in XSync() UpgradeStatus: Upgraded to yakkety on 2016-10-19 (66 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1652463/+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 1675163] Re: Don't attempt to create devices in LXC containers
EH uses Arachsys contain for their containers - this is based on the same kernel cgroups technology as LXC, but aims to be more lightweight. If it's a bug not to detect LXC, it's logically a bug not to detect other container systems that work the same way, and makedev should include this as a second option to test against. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Released Status in makedev source package in Trusty: Fix Released Status in makedev source package in Xenial: Fix Released Status in makedev source package in Yakkety: Fix Released Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+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 1675163] Re: Don't attempt to create devices in LXC containers
( link https://github.com/arachsys/containers ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Released Status in makedev source package in Trusty: Fix Released Status in makedev source package in Xenial: Fix Released Status in makedev source package in Yakkety: Fix Released Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+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 1679691] Fix for "s390: handle multiplexed syscalls correctly"
Default Comment by Bridge ** Attachment added: "Fix for "s390: handle multiplexed syscalls correctly"" https://bugs.launchpad.net/bugs/1679691/+attachment/4857407/+files/0001-s390-handle-multiplexed-syscalls-correctly.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1679691 Title: libseccomp fix - s390: handle multiplexed syscalls correctly Status in Ubuntu on IBM z Systems: New Status in libseccomp package in Ubuntu: New Bug description: Within Xenial version 2.2.3 of seccomp is included. With Yaketty version 2.3.1 is available and fixed this problem. Even Docker is working on a SNAP solution, please provide the fix to 16.04. With following patches this can be applied to 2.2.3 in support of the 16.04 LTS Release 16.04 Here the upstream git commits for the patches: 0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch 1d63fad4a064b80e0b921b16ed419f3342337ed4 0001-all-block-negative-syscall-numbers-from-the-filter.patch 51c46f80c1edee863bbc4eb21b03decc44e69a45 0001-api-limit-errno-values-to-MAX_ERRNO.patch 0d287caf43792239b107ee3215b32b8bc901f9c3 0001-db-fix-a-minor-style-problem.patch 61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 0001-db-make-the-individual-db-filter-ops-private.patch a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16 0001-db-store-the-rules-used-to-build-the-filter.patch f16f405f61ecdbad202257b61004b85fce64d75c 0001-arch-make-use-of-function-tables-instead-of-switch-s.patch 57df79c166b26d5044e7e27099e6e69671e727dd 0001-db-introduce-transaction-support.patch 9be1538a4ac0e45047a3f1b79691505c3d11ca31 0001-arch-move-the-low-level-filter-rule-addition-code-in.patch 996e445a74823c735757413fda809e1ed0afc7d4 0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch 5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 0001-arch-basic-support-for-multiplexed-and-direct-socket.patch d32c3bfa4b07add90dcd04292eb4ba278dd103ba 0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch 983835f3e0fd000a42c8beaea9d7fbe72665 0001-tests-add-a-test-for-the-different-types-of-socket-s.patch 099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 0001-api-add-a-seccomp_version-API-call.patch 58a7c20d4c2defc1c984c5c7391ecc60093f85fa 0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch 8ed78c3859f476d302995b43d6739f3341f5b37d 0001-s390-handle-multiplexed-syscalls-correctly.patch 47516603828396f85107ea3e2a254958c2bc3ff5 0001-arch-fix-the-multiplexed-ipc-syscalls.patch 3a89bd144885f54aff86f2e275859a1483992edd With the following additional commit all tests pass with "make check" 0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch 0d8504bc192e0989494df06efc4b186a9f02e20a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679691/+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 1680750] Re: pm-hibernate does nothing at all
** Package changed: powerman (Ubuntu) => pm-utils (Ubuntu) -- 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/1680750 Title: pm-hibernate does nothing at all Status in pm-utils package in Ubuntu: New Bug description: I have run from a command line: # sudo pm-hibernate and NOTHING f***ing happens. Usually it works (except for lots of issues on resume), but now I have tried it twice and it does nothing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: powerman (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 7 10:47:47 2017 InstallationDate: Installed on 2013-10-11 (1273 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: powerman UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1680750/+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 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly
** Changed in: libseccomp (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) ** Changed in: libseccomp (Ubuntu) Milestone: None => ubuntu-17.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1679691 Title: libseccomp fix - s390: handle multiplexed syscalls correctly Status in Ubuntu on IBM z Systems: New Status in libseccomp package in Ubuntu: New Bug description: Within Xenial version 2.2.3 of seccomp is included. With Yaketty version 2.3.1 is available and fixed this problem. Even Docker is working on a SNAP solution, please provide the fix to 16.04. With following patches this can be applied to 2.2.3 in support of the 16.04 LTS Release 16.04 Here the upstream git commits for the patches: 0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch 1d63fad4a064b80e0b921b16ed419f3342337ed4 0001-all-block-negative-syscall-numbers-from-the-filter.patch 51c46f80c1edee863bbc4eb21b03decc44e69a45 0001-api-limit-errno-values-to-MAX_ERRNO.patch 0d287caf43792239b107ee3215b32b8bc901f9c3 0001-db-fix-a-minor-style-problem.patch 61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 0001-db-make-the-individual-db-filter-ops-private.patch a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16 0001-db-store-the-rules-used-to-build-the-filter.patch f16f405f61ecdbad202257b61004b85fce64d75c 0001-arch-make-use-of-function-tables-instead-of-switch-s.patch 57df79c166b26d5044e7e27099e6e69671e727dd 0001-db-introduce-transaction-support.patch 9be1538a4ac0e45047a3f1b79691505c3d11ca31 0001-arch-move-the-low-level-filter-rule-addition-code-in.patch 996e445a74823c735757413fda809e1ed0afc7d4 0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch 5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 0001-arch-basic-support-for-multiplexed-and-direct-socket.patch d32c3bfa4b07add90dcd04292eb4ba278dd103ba 0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch 983835f3e0fd000a42c8beaea9d7fbe72665 0001-tests-add-a-test-for-the-different-types-of-socket-s.patch 099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 0001-api-add-a-seccomp_version-API-call.patch 58a7c20d4c2defc1c984c5c7391ecc60093f85fa 0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch 8ed78c3859f476d302995b43d6739f3341f5b37d 0001-s390-handle-multiplexed-syscalls-correctly.patch 47516603828396f85107ea3e2a254958c2bc3ff5 0001-arch-fix-the-multiplexed-ipc-syscalls.patch 3a89bd144885f54aff86f2e275859a1483992edd With the following additional commit all tests pass with "make check" 0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch 0d8504bc192e0989494df06efc4b186a9f02e20a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679691/+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 1680750] [NEW] pm-hibernate does nothing at all
You have been subscribed to a public bug: I have run from a command line: # sudo pm-hibernate and NOTHING f***ing happens. Usually it works (except for lots of issues on resume), but now I have tried it twice and it does nothing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: powerman (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 7 10:47:47 2017 InstallationDate: Installed on 2013-10-11 (1273 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: powerman UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- pm-hibernate does nothing at all https://bugs.launchpad.net/bugs/1680750 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. -- 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 1673717] Re: rsyslog GnuTLS error -50
What is this bug's destiny? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: New Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+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 1680831] [NEW] GDM3 info for other bug
Public bug reported: GDM3 info for other bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 7 14:24:32 2017 DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902] Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b] InstallationDate: Installed on 2016-05-18 (323 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash intel_pstate=enable SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN47WW(V3.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE50-80: dmi.product.name: 80J2 dmi.product.version: Lenovo E50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1~16.04~0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1~16.04~0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1~16.04~0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Fri Apr 7 13:10:45 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu xenial -- 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/1680831 Title: GDM3 info for other bug Status in xorg package in Ubuntu: New Bug description: GDM3 info for other bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 7 14:24:32 2017 DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902] Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b] InstallationDate: Installed on 2016-05-18 (323 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash intel_pstate=enable SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN47WW(V3.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.
[Touch-packages] [Bug 1680832] [NEW] GDM3 info for other bug
*** This bug is a duplicate of bug 1680826 *** https://bugs.launchpad.net/bugs/1680826 Public bug reported: GDM3 info for other bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 7 14:24:32 2017 DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902] Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b] InstallationDate: Installed on 2016-05-18 (323 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash intel_pstate=enable SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN47WW(V3.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE50-80: dmi.product.name: 80J2 dmi.product.version: Lenovo E50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1~16.04~0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1~16.04~0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1~16.04~0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Fri Apr 7 13:10:45 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu xenial -- 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/1680832 Title: GDM3 info for other bug Status in xorg package in Ubuntu: New Bug description: GDM3 info for other bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 7 14:24:32 2017 DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902] Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b] InstallationDate: Installed on 2016-05-18 (323 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash intel_pstate=enable SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN47WW(V3.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag d
[Touch-packages] [Bug 1680832] Re: GDM3 info for other bug
*** This bug is a duplicate of bug 1680826 *** https://bugs.launchpad.net/bugs/1680826 ** This bug has been marked a duplicate of bug 1680826 GDM shows and when trying to log in to gnome session blank screen appears -- 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/1680832 Title: GDM3 info for other bug Status in xorg package in Ubuntu: New Bug description: GDM3 info for other bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 7 14:24:32 2017 DistUpgraded: 2016-06-21 20:05:53,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:3902] Subsystem: Lenovo Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [17aa:381b] InstallationDate: Installed on 2016-05-18 (323 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5792b9b7-677c-4f15-9a88-49e4092413b2 ro quiet splash intel_pstate=enable SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-06-21 (289 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN47WW(V3.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN47WW(V3.00):bd07/14/2015:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE50-80: dmi.product.name: 80J2 dmi.product.version: Lenovo E50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1~16.04~0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1~16.04~0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1~16.04~0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Fri Apr 7 13:10:45 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1680832/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule
I have placed amd64 test kernels at
http://people.canonical.com/~jj/lp1679704/
It fixes the complain issue, which should let you proceed without
removing the profile and I am working on a regression test to add to the
test suite.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1679704
Title:
libvirt profile is blocking global setrlimit despite having no rlimit
rule
Status in apparmor package in Ubuntu:
New
Bug description:
Hi,
while debugging bug 1678322 I was running along apparmor issues.
Thanks to jjohansen we debugged some of it and eventually I was asked to
report to a bug.
Symptom:
[ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED"
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd"
rlimit=memlock value=1610612736
But none of the profiles has any rlimit statement in it:
$ grep -Hirn limit /etc/apparmor*
/etc/apparmor.d/sbin.dhclient:58: # such, if the dhclient3 daemon is
subverted, this effectively limits it to
/etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
/etc/apparmor.d/abstractions/ubuntu-helpers:64: # in limited libraries so
glibc's secure execution should be enough to not
/etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime
The profile contains a child profile which makes reading the dumps a bit
painful, but I'll attach them anyway for you to take a look.
To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via
libvirt.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1680811] [NEW] Request to add wireguard interface to interface-order
Public bug reported: This started from https://github.com/jlund/streisand/issues/557. Basically wg* namespace is not in interface-order and acts last in * scope, and this makes resolv.conf to stay in the same state. I suggest the following change: :/etc/resolvconf/interface-order # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo +wg* tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* @(br|eth)*([^.]).inet6 @(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)*([^.]).inet @(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Attachment added: "wg-namespace.patch" https://bugs.launchpad.net/bugs/1680811/+attachment/4857204/+files/wg-namespace.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1680811 Title: Request to add wireguard interface to interface-order Status in resolvconf package in Ubuntu: New Bug description: This started from https://github.com/jlund/streisand/issues/557. Basically wg* namespace is not in interface-order and acts last in * scope, and this makes resolv.conf to stay in the same state. I suggest the following change: :/etc/resolvconf/interface-order # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo +wg* tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* @(br|eth)*([^.]).inet6 @(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)*([^.]).inet @(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811/+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 940030] Re: rsyslog stops working after logrotate until restarted
Same issue here with rsyslog and logrotate on many ubuntu 16.04 servers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted Status in rsyslog package in Ubuntu: Confirmed Bug description: This could otherwise be titled, rsyslog reload does not create log files; only restart does. This is happening on a number of machines I work on. It's happening on 10.04 and 11.04. It might be similar to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 But in my case after the restart there is no /var/log/syslog being created, nor auth.log, kern.log, etc. The files are rotated, rsyslog is reloaded, and none of the log files are created and nothing is being logged. This has been plaguing my systems since moving from syslog-ng, which I may return to as it seems it was actually production ready. Without manually restarting those files don't exist so here's what I did on an 11.04 system: logrotate --force --verbose /etc/logrotate.conf gives: rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log /var/log/syslog does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log /var/log/kern.log does not exist -- skipping considering log /var/log/auth.log log /var/log/auth.log does not exist -- skipping considering log /var/log/user.log log /var/log/user.log does not exist -- skipping considering log /var/log/lpr.log log /var/log/lpr.log does not exist -- skipping considering log /var/log/cron.log log /var/log/cron.log does not exist -- skipping considering log /var/log/debug log /var/log/debug does not exist -- skipping considering log /var/log/messages log /var/log/messages does not exist -- skipping not running postrotate script, since no logs were rotated Then /sbin/reload rsyslog logger -i testing At this point there is no /var/log/syslog Then: /sbin/restart rsyslog And voila there is a /var/log/syslog beginning with: Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg started. Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com";] (re)start Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114 Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108 Then to recreate: logrotate --force --verbose /etc/logrotate.conf rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log needs rotating rotating log /var/log/syslog, log->rotateCount is 7 dateext suffix '-20120223' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' compressing log with: /bin/gzip renaming /var/log/syslog to /var/log/syslog-20120223 running postrotate script removing old log /var/log/syslog-20111219.gz rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log needs rotating considering log /var/log/auth.log log needs rotating considering log /var/log/user.log log /var/log/user.log does not exist -- skip
[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1552577 ** Tags added: iso-testing -- 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/1552577 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: Confirmed Bug description: Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) 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/1552577/+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 1680796] 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/1680796/+attachment/4857194/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1680796/+attachment/4857196/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1680796/+attachment/4857199/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1680796/+attachment/4857200/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1680796/+attachment/4857201/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1680796/+attachment/4857202/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1680796/+attachment/4857203/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV ** 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/1680796 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: Story: just after installing zesty daily amd64 and doing a update & full-upgrade apport-gtk reported this error: - Es(language) - Spanish kb - Zesty daily amd64 in kvm ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: apport-gtk 2.20.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CrashReports: 640:1000:122:7467911:2017-04-07 12:34:57.133341312 +0200:2017-04-07 12:34:58.133341312 +0200:/var/crash/_usr_bin_compiz.1000.crash 640:1000:122:6849341:2017-04-07 12:35:05.034369707 +0200:2017-04-07 12:35:06.034369707 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: Unity:Unity7 Date: Fri Apr 7 12:35:00 2017 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1490811393 InstallationDate: Installed on 2017-04-07 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170406) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/vigo-zeste-es ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f315ffe4909:mov(%rbx),%rdi PC (0x7f315ffe4909) 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: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1680796/+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 1678187] Re: dpkg fails to remove a linux-image-extra package, if /boot is about full
** Summary changed: - update-initramfs requires more space in /boot when removing a linux-image-extra package + dpkg fails to remove a linux-image-extra package, if /boot is about full -- 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/1678187 Title: dpkg fails to remove a linux-image-extra package, if /boot is about full Status in dpkg package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. A workaround would be to remove the respective /boot/initrd.img- file before running dpkg --purge for the linux-image-extra package. That could also be done by sudo update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1678187/+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 1678187] Re: update-initramfs requires more space in /boot when removing a linux-image-extra package
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- 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/1678187 Title: update-initramfs requires more space in /boot when removing a linux- image-extra package Status in dpkg package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. A workaround would be to remove the respective /boot/initrd.img- file before running dpkg --purge for the linux-image-extra package. That could also be done by sudo update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1678187/+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 1680784] [NEW] Glitches
Public bug reported: I switch pc to sleep? then i wake up him, now i get glitchs lines, if i reboot pc, lines will lost. There is screenshot of screen with glitch https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing ProblemType: Graphic glitch DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 7 13:12:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 610] [1462:809f] InstallationDate: Installed on 2017-03-22 (15 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=ru PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=5ab9fb9f-7d9b-4ec4-ab26-936456251d31 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0113 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM DH dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0113:bd03/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Fri Apr 7 10:17:12 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB OPTICAL MOUSEMOUSE, id 8 inputLogitech K270KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** Description changed: - I switch pc to sleep? then i wake up him, now i get glitchs lines + I switch pc to sleep, then i wake up him, now i get glitchs lines ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 - GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) + NVRM version: NVI
[Touch-packages] [Bug 1677997] Re: aa-enforce gives syntax error on snapd config
The bug is fixed in 2.10.95-0ubuntu2.6 The system that was failing was pulling in 2.10.95-0ubuntu2 ** Description changed: Ubuntu 16.04.02 LTS (Cloud OVA Image) - apparmor 2.10.95-0ubuntu2.6 + apparmor 2.10.95-0ubuntu2 snap-confine 2.22.6 When I run aa-enforce I get - ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine line 71: - change_profile unsafe /** -> [^u/]**, + ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine line 71: + change_profile unsafe /** -> [^u/]**, The same command worked around 1 month ago but now exhibits the above error. I don't think the the offending lines in /etc/apparmor.d/usr.lib.snapd.snap-confine have changed for months. ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1677997 Title: aa-enforce gives syntax error on snapd config Status in apparmor package in Ubuntu: Fix Released Bug description: Ubuntu 16.04.02 LTS (Cloud OVA Image) apparmor 2.10.95-0ubuntu2 snap-confine 2.22.6 When I run aa-enforce I get ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine line 71: change_profile unsafe /** -> [^u/]**, The same command worked around 1 month ago but now exhibits the above error. I don't think the the offending lines in /etc/apparmor.d/usr.lib.snapd.snap-confine have changed for months. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1677997/+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 1671873] Re: Upgrade to Yakkety removes eth0 from /etc/network/interfaces
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1671873 Title: Upgrade to Yakkety removes eth0 from /etc/network/interfaces Status in network-manager package in Ubuntu: Confirmed Bug description: I've just upgraded this machine from Kubuntu 16.04 to Kubuntu 16.10 using the uprading UI. Before the upgrade, I had lo and eth0 in /etc/network/interfaces. After the upgrade, there was only lo, no eth0 anymore, leaving me without a network connection. I had to re-enter eth0 into the file and restart the networking service to get networking functionality again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 10 17:24:57 2017 IfupdownConfig: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp InstallationDate: Installed on 2012-01-28 (1868 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.100.254 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2017-03-09 (1 days ago) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671873/+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 1660832] Re: unix domain socket cross permission check failing with nested namespaces
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1660832 Title: unix domain socket cross permission check failing with nested namespaces Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Confirmed Status in linux source package in Yakkety: Triaged Status in apparmor source package in Zesty: Confirmed Status in linux source package in Zesty: Fix Released Bug description: When using nested namespaces policy within the nested namespace is trying to cross validate with policy outside of the namespace that is not visible to it. This results the access being denied and with no way to add a rule to policy that would allow it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660832/+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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in tor package in Ubuntu: Invalid Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in tor source package in Xenial: Invalid Status in apparmor source package in Yakkety: New Status in linux source package in Yakkety: Triaged Status in tor source package in Yakkety: Invalid Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/+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 1661030] Re: regession tests failing after stackprofile test is run
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1661030 Title: regession tests failing after stackprofile test is run Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in apparmor source package in Xenial: Fix Committed Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Committed Status in linux source package in Yakkety: Triaged Status in apparmor source package in Zesty: Fix Released Status in linux source package in Zesty: Incomplete Bug description: from source, I'm running the tests and the makefile fails at the end with: running stackprofile Makefile:303: recipe for target 'tests' failed make: *** [tests] Error 1 No idea why that is happening. It's breaking on our kernel team regression tests runs, so can this be investigated? The source was fetched using "apt-get source apparmor". A full run is below: king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make USE_SYSTEM=1 tests running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) (ioperm) (iopl) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12503 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12537 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12803 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12833 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12869 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12905 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12941 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ Fatal Error (environ): Unable to run test sub-executable running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root running ptrace using ptrace v6 tests ... running pwrite running query_label Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked as expected pass but known problem (xpass) xpass: QUERY file (all base perms #1) Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked as expected pass but known problem (xpass) xpass: QUERY file (all base perms #2) running regex running rename running readdir running rw running socketpair running swap mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 0600 suggested. swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 0600 suggested. running sd_flags running setattr running symlink running syscall running tcp running unix_fd_server runnin
[Touch-packages] [Bug 1316873] Re: Left mouse button stops working
I have the same issue and the trigger seemed to be moving from an AMD to an Nvidia graphics card. Switching to console (CTRL Alt F1) and back fixes it but can cause some issues with any graphical applications running at the time. I am also using the Ubuntu automatic Nvidia driver that appears to currently be one version behind the one on their website. -- 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/1316873 Title: Left mouse button stops working Status in xorg package in Ubuntu: Confirmed Bug description: This problem has plagued me for a few years across different laptops and Ubuntu versions. Current I am experiencing this on a Dell Inspiron 15z running Ubuntu 14.04 LTS. It typically starts after I have used the chat or call feature in gmail, by clicking on the phone icon in the left chat margin. I am a Firefox user and have not tested this with chrome etc. It has not happened if i dont install google-talkplugin so it is quite possible that the plugin is to blame. Symptom === The left mouse button on all attached mice - USB , Trackpad and touch - will not do anything however the right mouse button continues to work. This happens to all applications and also to the desktop. The keyboard continues to function as normal. When this occurs , my solution is to Alt-F4 close all windows and log out of the X session. When I re-login the left mouse button works as normal. This is an irritant and work disruptor as I have to save all browser and desktop applications to safe state before I logout to reset the mouse. I will appreciate any soltion or workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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: Tue May 6 21:41:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058f] InstallationDate: Installed on 2014-04-17 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5523 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0GKGJG dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5523 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 6 21:20:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+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 1680330] Re: lxc-execute can run commands in current namespace
I didn't expect it. While I understand that there is no such entity as "a container" on linux, the functionality of lxc being a construct of several underlying features, lxc appears to me to be trying to construct a consistent abstraction on those features. The unit of reference throughout the documentation is "the container", and seems geared to be towards being able to treat them as atomic units. I can name them, create, delete and snapshot them, given them IP addresses etc. For lxc-execute to function with partial functionality, without warning, breaking the abstraction model of the suite, seems to me to be undesirable behavior. Regards, Tristan -- 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/1680330 Title: lxc-execute can run commands in current namespace Status in lxc package in Ubuntu: Invalid Bug description: If lxc-execute is passed a non-existent container name, then the command given is run in the current namespace. I believe it should failed with a "container not found" error, as otherwise it can lead to unexpected consequences in the host environment. example: # lxc-ls files foreman ns01proxy ## Example typo on the -n option # lxc-execute -n ns1 -- touch /tmp/ns01 # ls -l /tmp/ns01 -rw-r--r-- 1 root root 0 Apr 6 16:07 /tmp/ns01 ## Command ran outside of container! # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1680330/+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 1670745] Re: ssh-keyscan : bad host signature when using port option
Hello,
Thank you Colin for your clarification.
I don't understand why the package I downloaded was not the good one.
Anyway, after having followed selective proposed update documentation, I have :
#ssh -V
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g 1 Mar 2016
#dpkg -l | grep openssh
ii openssh-client 1:7.2p2-4ubuntu2.2
amd64secure shell (SSH) client, for secure access to
remote machines
==> and now, the problem is fixed. I can confirm that the port is well
hashed.
For information, what will be the releasing process of this proposed
patch ? Will it be included main stream ?
Thank you for your work,
Sincerely,
Gautier.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1670745
Title:
ssh-keyscan : bad host signature when using port option
Status in portable OpenSSH:
Unknown
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Xenial:
Fix Committed
Status in openssh source package in Yakkety:
Fix Committed
Status in openssh package in Debian:
Fix Released
Bug description:
[Impact]
* using ssh-keyscan while using the port (-p) option of it will create
bad entries. They will contain the port and thereby be invalid for
latter use under the purpose of known_hosts.
* Fix by backporting upstream fix.
[Test Case]
* Further evolving from the simplification Josh provided:
Testcase:
$ release=xenial
$ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
$ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
$ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port
/' /etc/ssh/sshd_config
$ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
$ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
$ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p
${IP}
# See the port in the Hash still
# Install the fixed version in *-client and see the port gone from the
output
[Regression Potential]
* Change is limited to ssh-keyscan (not any touching other parts of openssh)
* Fix is from upstream (no "Ubuntu special" change)
* Fix is small and "only" changing string creation (11 lines touched)
So overall the regression potential should be low.
[Other Info]
* n/a
---
When I use the port option with ssh-keygen, the result is not
compatible with ssh known_host file format.
UBUNTU VERSION :
lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
BAD :
:~/.ssh$ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l
:~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
# [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
debug1: Enabling compatibility mode for protocol 2.0
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha...@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC:
compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC:
compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
[|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...]
ecdsa-sha2-nistp256
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
==> we see the port number because it is not hashed !
GOOD :
rm ~/.ssh/known_hosts
:~/$ ssh -p [...port...] [...snip...]
The authenticity of host '[[...snip...]]:[...port...]
([[...snip...]]:[...port...])' can't be established.
ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list
of known hosts.
[...snip...]@[...snip...]'s password:
:~/$ !cat
cat ~/.ssh/known_hosts
|1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs=
ecdsa-sha2-nistp256
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
|1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8=
ecdsa-sha2-nistp256
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
==> we cannot see the port number as it is well hashed !
REMARKS :
==
Same problem has already reported here (on macOS):
https://github.com/ansible/ansible-modules-extras/issues/2651
[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps
The 16.04 update is in the SRU queue since March 14th, but for some reason it is still not accepted. -- 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/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: In Progress Status in Canonical System Image: In Progress Status in sni-qt: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Confirmed Status in qtbase-opensource-src source package in Yakkety: Confirmed Bug description: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right- clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org /plasma-integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1680726] Re: Xorg.freeze
Sorry, a typo... "switcht go VT" means "switch to" -- 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/1680726 Title: Xorg.freeze Status in xorg package in Ubuntu: New Bug description: We cannot login via lightdm if we wait too long after boot: Cursor in password input field stops blinking and if user inputs password anyways, then pc freezes. No switcht go VT or login via ssh possible. Only magic sysreq helps for rebooting. When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into gui, then the cursor is blinking again and everything is normal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 08:57:59 2017 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1680726/+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 1680726] [NEW] Xorg.freeze
Public bug reported: We cannot login via lightdm if we wait too long after boot: Cursor in password input field stops blinking and if user inputs password anyways, then pc freezes. No switcht go VT or login via ssh possible. Only magic sysreq helps for rebooting. When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into gui, then the cursor is blinking again and everything is normal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 08:57:59 2017 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze xenial -- 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/1680726 Title: Xorg.freeze Status in xorg package in Ubuntu: New Bug description: We cannot login via lightdm if we wait too long after boot: Cursor in password input field stops blinking and if user inputs password anyways, then pc freezes. No switcht go VT or login via ssh possible. Only magic sysreq helps for rebooting. When user switches to a virtual terminal via ctrl-alt-F(1..6) and back into gui, then the cursor is blinking again and everything is normal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Apr 7 08:57:59 2017 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1680726/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
to David Ford (djfordz-q) thank for help, but it doesn't make external mic to work I've setup option: `options snd-hda-intel model=laptop-dmic,headset-mic` and reboot notebook - doesn't help, internal working, external not. Searching an internet, help to find a solution that works. So then I've install "alsa-tools-gui" launch "HDAJackRetask", select codec ALC256, checked "Show unconnected pins" then check pin ID: 0x19 and select "Microphone" then hit "Apply now". Started pavucontrol for checks and it work. Both of them built-in, and external headset microphone works now. So launch "HDAJackRetask" and make a permanent change, hit "Install boot override" After reboot it work for all users on notebook. P.S. As for other models and codecs it may be other pins number in "HDAJackRetask" utility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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
