[Touch-packages] [Bug 1921475] Re: [2.9.2] Commissioning does not collect correct storage information
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd via https://github.com/lxc/lxd/issues/8718 Importance: Unknown Status: Unknown ** No longer affects: systemd ** Also affects: lxd via https://github.com/lxc/lxd/issues/8718 Importance: Unknown Status: Unknown -- 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/1921475 Title: [2.9.2] Commissioning does not collect correct storage information Status in lxd: Unknown Status in MAAS: Invalid Status in systemd package in Ubuntu: New Bug description: MAAS version 2.9.2 When commissioning servers with different storage types (SSDs in a virtual disk behind RAID controller, NVMes and HDDs), but everything shows up tagged as SSD. The commissioning step 50-maas-01-commissioning is generating _incorrect_ storage info such as a random serial and it’s missing the rpm for the virtual disk (behind RAID controller) and the HDDs. The commissioning step maas-lshw generates the correct info, but is not used. I have added screenshot of storage after commission and outputs from both 50-maas-01-commissioning and maas-lshw here: https://discourse.maas.io/t/how-to-work-with-storage- tags/4344/3?u=szeestraten See https://discourse.maas.io/t/how-to-work-with-storage-tags/4344 for conversation To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1921475/+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 1869116] Re: smartctl-validate is borked in a recent release
** Also affects: maas/2.8
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
Fix Released
Status in MAAS:
Triaged
Status in MAAS 2.8 series:
New
Status in util-linux package in Ubuntu:
Confirmed
Bug description:
Bug (maybe?) details first, diatribe second.
Bug Summary: multi-hdd / raid with multiple drives / multiple devices
or something along those lines cannot be commissioned anymore: 2.4.x
worked fine, 2.7.0 does not.
Here is the script output of smartctl-validate:
-
# /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66c9220df4ac' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters:
{'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i',
'name': 'sda', 'physical_blockdevice_id': 33, 'serial':
'6842b2b0740e9900260e66c9220df4ac'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
-
# /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial
'6842b2b0740e9900260e66f924ecece0' not found!
This indicates the storage device has been removed or the OS is unable to
find it due to a hardware failure. Please re-commission this node to
re-discover the storage devices, or delete this device manually.
Given parameters: {'storage': {'argument_format': '{path
}', 'type': 'storage', 'value': {'id_path':
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i',
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial':
'6842b2b0740e9900260e66f924ecece0'
}
}
}
Discovered storage devices: [
{'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66c9220df4ac'
},
{'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL':
'6842b2b0740e9900260e66f924ecece0'
},
{'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL':
'10092013112645'
}
]
Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
}
-
You can see that it says the storage cannot be found and immediately
lists it as a discovered device. It does it for both tests (one for
each drive), and for both servers
Bug Details:
I had maas 2.4.x for the longest time over my journey (see below journey) and
have never had any problems re-commissioning (or deleting and re-discovering
over boot PXE) 2 of my servers (r610, r710).
r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual
disk.
r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks
So commission after commission trying to get through my journey, 0
problems. After I finally get everything figured out on the juju,
network/vlan, quad-nic end, I go to re-commission and I cannot.
smartctl-validate fails on both, over and over again. I even destroyed
and re-created the raid/VDs, still not.
After spending so much time on it I remembered that it was the first
time I had tried to re-commission these two servers since doing an
upgrade from 2.4.x->2.7 in an effort to use the updated KVM
integration to add a couple more guests. Once I got all everything
figured out I went to re-commission everything and boom.
[Upgrade path notes]
In full disclosure, in case this matters. I was on apt install of 2.4.x and
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to
snap but do not know how to without losing all maas data and could not find
docs on it, so a problem for another day. But in case that is part of the
problem for some odd reason, I wanted to share.
[Diatribe]
My journey to get maas+juju+openstack+kubernets has been less then stellar. I
have ran into problem after problem; albeit some of which were my own. I am so
close, after spending the last 6 months on/off when I had time, and really
hardcore the last 4 days. The last half day of which has been this little gem.
Maas h
[Touch-packages] [Bug 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
** Changed in: maas Status: Incomplete => Invalid -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: Invalid Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Triaged Bug description: Also created bug on upstream : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1698181] Re: Switch to netplan renderer in Artful
** Changed in: maas (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: Fix Released Status in openvswitch: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: Fix Released Status in resolvconf package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+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 1860335] Re: Additional Drivers tab claims i8260 wifi card is not working
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1860335 Title: Additional Drivers tab claims i8260 wifi card is not working Status in software-properties package in Ubuntu: New Bug description: Recently upgraded to Focal, and despite having a stable, working wifi connection I see that the "Additional Drivers" tab of the GTK application shows that my wifi card is not working. Note there is only a single adapter in my laptop. From dmesg: [7.237957] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 From lspci: 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 15:20:11 2020 InstallationDate: Installed on 2016-11-01 (1175 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860335/+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 1860335] [NEW] Additional Drivers tab claims i8260 wifi card is not working
Public bug reported: Recently upgraded to Focal, and despite having a stable, working wifi connection I see that the "Additional Drivers" tab of the GTK application shows that my wifi card is not working. Note there is only a single adapter in my laptop. >From dmesg: [7.237957] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 >From lspci: 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 15:20:11 2020 InstallationDate: Installed on 2016-11-01 (1175 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of software-properties" https://bugs.launchpad.net/bugs/1860335/+attachment/5321714/+files/additional_drivers_no_wifi.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1860335 Title: Additional Drivers tab claims i8260 wifi card is not working Status in software-properties package in Ubuntu: New Bug description: Recently upgraded to Focal, and despite having a stable, working wifi connection I see that the "Additional Drivers" tab of the GTK application shows that my wifi card is not working. Note there is only a single adapter in my laptop. From dmesg: [7.237957] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 From lspci: 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 15:20:11 2020 InstallationDate: Installed on 2016-11-01 (1175 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860335/+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 1632808] Re: Consider supporting IPv6 autoconf in configure_networking
This bug has not seen any activity in the last 6 months, so it is being automatically closed. If you are still experiencing this issue, please feel free to re-open. MAAS Team ** Changed in: maas Status: Confirmed => 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/1632808 Title: Consider supporting IPv6 autoconf in configure_networking Status in MAAS: Invalid Status in initramfs-tools package in Ubuntu: Triaged Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
This bug has not seen any activity in the last 6 months, so it is being automatically closed. If you are still experiencing this issue, please feel free to re-open. MAAS Team ** Changed in: maas Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Invalid Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Fix Released Status in ifupdown source package in Yakkety: Fix Released Status in ifupdown package in Debian: Fix Released Bug description: === Begin SRU Template === [Impact] The systemd networking.service unit will bring down the loopback device (lo) when it is stopped. This behavior differs from the behavior in other Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down. The problem that was seen was that iscsi root over ipv6 would hang on shutdown. [Test Case] Test is fairly simple and can be demonstrated in lxc container. The key is really that the lo device should not have its link set down after stopping networking.service. So, below: out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty should not show 'empty', but should have LOOPBACK,UP,LOWER in its output. $ release=yakkety; name=y1 $ lxc launch ubuntu-daily:$release $name $ sleep 10 $ lxc exec $name /bin/bash ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP) % ip link show dev lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % ip address show dev lo up 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP'). % systemctl stop networking.service % ip link show dev lo 1: lo: mtu 65536 qdisc noqueue state DOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty empty ## Now enable proposed, install update, reboot and show. % rel=$(lsb_release -sc) % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" | sudo tee /etc/apt/sources.list.d/proposed.list % sudo apt update -qy && sudo apt install -qy ifupdown mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % ip address show dev lo up 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever % systemctl stop networking.service % ip link show dev lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever [Regression Potential] Should be pretty low. zesty and yakkety-proposed have this. Taking down 'lo' is often cause of problems, and never the solution to problems as far as I'm aware. [Other Info] === End SRU Template === With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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 1822073] [NEW] Bluetooth headset profile forgotten after disconnection
Public bug reported: Similar to bug 1283003, after connecting my Bluetooth headset (Sony WH- 1000X M3) they appear in Gnome Control Centre's Sound tab but are not selectable. I've narrowed down the circumstances to reproduce the bug as follows: 1. Start with working sound through Bluetooth to headset 2. In pavucontrol's Configuration tab, note that headset is listed with A2DP profile 3. Disconnect (power off) the headset 4. Note that sound comes out of fallback device (as expected) 5. Power on the headset and reconnect to Bluetooth 6. Look in Gnome Control Centre and note the headset appears in Sound, but is not selectable (buggy) 7. In pavucontrol's Configuration tab, note headset is listed with "Off" 8. Manually switch to A2DP 9. At the point, we have to cycle the connection again (disconnect/reconnect) and then sound is once more routed to the headset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 10:33:37 2019 InstallationDate: Installed on 2015-07-04 (1363 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822073 Title: Bluetooth headset profile forgotten after disconnection Status in pulseaudio package in Ubuntu: New Bug description: Similar to bug 1283003, after connecting my Bluetooth headset (Sony WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are not selectable. I've narrowed down the circumstances to reproduce the bug as follows: 1. Start with working sound through Bluetooth to headset 2. In pavucontrol's Configuration tab, note that headset is listed with A2DP profile 3. Disconnect (power off) the headset 4. Note that sound comes out of fallback device (as expected) 5. Power on the headset and reconnect to Bluetooth 6. Look in Gnome Control Centre and note the headset appears in Sound, but is not selectable (buggy) 7. In pavucontrol's Configuration tab, note headset is listed with "Off" 8. Manually switch to A2DP 9. At the point, we have to cycle the connection again (disconnect/reconnect) and then sound is once more routed to the headset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 10:33:37 2019 InstallationDate: Installed on 2015-07-04 (1363 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822073/+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 1765654] Re: Typo in 2FA prompt "passccode"
Good spot, have fixed the en_GB translation! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1765654 Title: Typo in 2FA prompt "passccode" Status in gnome-online-accounts package in Ubuntu: Invalid Status in language-pack-gnome-en package in Ubuntu: New Bug description: When logging in to Ubuntu SSO for enabling Livepatch, as a member of a Launchpad team which requires 2FA, I'm prompted for my second factor. The dialog has a typo and asks for my "passccode" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-initial-setup 3.28.0-2ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 10:57:22 2018 InstallationDate: Installed on 2015-07-04 (1021 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-initial-setup UpgradeStatus: Upgraded to bionic on 2018-03-15 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1765654/+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 1758844] Re: gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow → #3 → IA__FcStrSetAdd → IA__FcConfigParseAndLoad → FcConfigParseAndLoadDir → #7 → FcParseInclude
** Attachment added: "10-scale-bitmap-fonts.conf" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1758844/+attachment/5099805/+files/10-scale-bitmap-fonts.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1758844 Title: gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow → #3 → IA__FcStrSetAdd → IA__FcConfigParseAndLoad → FcConfigParseAndLoadDir → #7 → FcParseInclude → #9 → doContent → contentProcessor Status in fontconfig package in Ubuntu: New Status in gnome-software package in Ubuntu: New Bug description: Background crash report ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 07:05:25 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2015-07-04 (995 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f55edd0f207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f55edd0f207) ok source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: tcache_get (tc_idx=2) at malloc.c:2943 __GI___libc_malloc (bytes=48) at malloc.c:3050 () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcStrSetAdd () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcConfigParseAndLoad () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-software crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to bionic on 2018-03-15 (10 days ago) UserGroups: adm cdrom dip docker landscape libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1758844/+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 1559482] Re: add-apt-repository manpage does not mention new -u option
I've re-fixed this independently in https://code.launchpad.net/~adam- collard/software-properties/document-update-flag/+merge/328302 would love to have eyes on it to review. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1559482 Title: add-apt-repository manpage does not mention new -u option Status in software-properties package in Ubuntu: Triaged Bug description: The add-apt-repository tool has apparently gained a new option to update the package cache. However, the manpage does not reflect this (as seen on http://manpages.ubuntu.com/manpages/wily/en/man1/add-apt- repository.1.html or http://manpages.ubuntu.com/manpages/xenial/en/man1/add-apt- repository.1.html). While the tool's own help text does mention it, this should be documented in the manpage as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: software-properties-common 0.96.13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 19 21:07:41 2016 InstallationDate: Installed on 2016-02-01 (47 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1559482/+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 1559482] Re: add-apt-repository manpage does not mention new -u option
** Branch linked: lp:~adam-collard/software-properties/document-update- flag -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1559482 Title: add-apt-repository manpage does not mention new -u option Status in software-properties package in Ubuntu: Triaged Bug description: The add-apt-repository tool has apparently gained a new option to update the package cache. However, the manpage does not reflect this (as seen on http://manpages.ubuntu.com/manpages/wily/en/man1/add-apt- repository.1.html or http://manpages.ubuntu.com/manpages/xenial/en/man1/add-apt- repository.1.html). While the tool's own help text does mention it, this should be documented in the manpage as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: software-properties-common 0.96.13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 19 21:07:41 2016 InstallationDate: Installed on 2016-02-01 (47 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1559482/+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 1707236] Re: man page for add-apt-repository doesn't document --update
*** This bug is a duplicate of bug 1559482 *** https://bugs.launchpad.net/bugs/1559482 ** This bug has been marked a duplicate of bug 1559482 add-apt-repository manpage does not mention new -u option -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1707236 Title: man page for add-apt-repository doesn't document --update Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository accepts a --update flag which negates the need to run "apt[-get] update" after adding a repository, but this is undocumented in the man page. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: software-properties-common 0.96.24.13 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 28 16:34:06 2017 InstallationDate: Installed on 2015-07-04 (755 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to zesty on 2017-04-24 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1707236/+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 1707236] Re: man page for add-apt-repository doesn't document --update
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Adam Collard (adam-collard) ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1707236 Title: man page for add-apt-repository doesn't document --update Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository accepts a --update flag which negates the need to run "apt[-get] update" after adding a repository, but this is undocumented in the man page. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: software-properties-common 0.96.24.13 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 28 16:34:06 2017 InstallationDate: Installed on 2015-07-04 (755 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to zesty on 2017-04-24 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1707236/+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 1707236] [NEW] man page for add-apt-repository doesn't document --update
Public bug reported: add-apt-repository accepts a --update flag which negates the need to run "apt[-get] update" after adding a repository, but this is undocumented in the man page. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: software-properties-common 0.96.24.13 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 28 16:34:06 2017 InstallationDate: Installed on 2015-07-04 (755 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to zesty on 2017-04-24 (95 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1707236 Title: man page for add-apt-repository doesn't document --update Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository accepts a --update flag which negates the need to run "apt[-get] update" after adding a repository, but this is undocumented in the man page. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: software-properties-common 0.96.24.13 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 28 16:34:06 2017 InstallationDate: Installed on 2015-07-04 (755 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to zesty on 2017-04-24 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1707236/+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 892293] Re: Jenkins is not reporting the skipped tests
** Also affects: pyjunitxml (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyjunitxml in Ubuntu. https://bugs.launchpad.net/bugs/892293 Title: Jenkins is not reporting the skipped tests Status in pyjunitxml: Fix Released Status in pyjunitxml package in Ubuntu: New Bug description: We are using junitxml to generate a results file that will be parsed by Jenkins for the final reporting. The skipped tests are being reported as passed, because they are tagged "skip" but Jenkins expects them to be "skipped". I couldn't find any specification of the results file, but on [1] everything refers to the tag as "skipped". [1] http://wiki.apache.org/ant/Proposals/EnhancedTestReports To manage notifications about this bug go to: https://bugs.launchpad.net/pyjunitxml/+bug/892293/+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 1565767] [NEW] TagFile iteration raises SystemError when attempting to parse a signed .changes file
Public bug reported: Attempting to parse a .changes file using apt_pkg.TagFile such as http://paste.ubuntu.com/15611341/ raises a SystemError. http://paste.ubuntu.com/15611387/ contains a sample Python REPL with the given file. Note that this is a change in behaviour between Trusty and Xenial, parsing the same file in Trusty (python-apt 0.9.3.5ubuntu2) has no issues. The specific unit test that failed leading to this bug report is attempting to parse the .changes file when it is signed with an unknown key. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 4 15:04:29 2016 InstallationDate: Installed on 2012-08-17 (1325 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) SourcePackage: python-apt UpgradeStatus: Upgraded to xenial on 2016-03-07 (28 days ago) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kanban-cross-team landscape xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1565767 Title: TagFile iteration raises SystemError when attempting to parse a signed .changes file Status in python-apt package in Ubuntu: New Bug description: Attempting to parse a .changes file using apt_pkg.TagFile such as http://paste.ubuntu.com/15611341/ raises a SystemError. http://paste.ubuntu.com/15611387/ contains a sample Python REPL with the given file. Note that this is a change in behaviour between Trusty and Xenial, parsing the same file in Trusty (python-apt 0.9.3.5ubuntu2) has no issues. The specific unit test that failed leading to this bug report is attempting to parse the .changes file when it is signed with an unknown key. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 4 15:04:29 2016 InstallationDate: Installed on 2012-08-17 (1325 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) SourcePackage: python-apt UpgradeStatus: Upgraded to xenial on 2016-03-07 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1565767/+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 1549819] Re: SIGSEGV when reloading cache after setting architecture to ""
@Brian - I don't have permission to read that bug, so can't comment one way or the other -- 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/1549819 Title: SIGSEGV when reloading cache after setting architecture to "" Status in apt package in Ubuntu: Fix Released Status in landscape-client package in Ubuntu: Confirmed Bug description: When reloading the cache, after setting an architecture, the Python process segfaults. Simple script to reproduce is at: http://paste.ubuntu.com/15197359/ Tested on a Xenial LXD with Wily host (on the host, the script doesn't trigger the segfault). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Thu Feb 25 14:09:39 2016 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1549819/+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 1549819] Re: SIGSEGV when reloading cache after setting architecture
** Also affects: landscape-client (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1549819 Title: SIGSEGV when reloading cache after setting architecture Status in landscape-client package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When reloading the cache, after setting an architecture, the Python process segfaults. Simple script to reproduce is at: http://paste.ubuntu.com/15197359/ Tested on a Xenial LXD with Wily host (on the host, the script doesn't trigger the segfault). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Thu Feb 25 14:09:39 2016 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1549819/+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 1549819] [NEW] SIGSEGV when reloading cache after setting architecture
Public bug reported: When reloading the cache, after setting an architecture, the Python process segfaults. Simple script to reproduce is at: http://paste.ubuntu.com/15197359/ Tested on a Xenial LXD with Wily host (on the host, the script doesn't trigger the segfault). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Thu Feb 25 14:09:39 2016 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Affects: python-apt (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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1549819 Title: SIGSEGV when reloading cache after setting architecture Status in landscape-client package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When reloading the cache, after setting an architecture, the Python process segfaults. Simple script to reproduce is at: http://paste.ubuntu.com/15197359/ Tested on a Xenial LXD with Wily host (on the host, the script doesn't trigger the segfault). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Thu Feb 25 14:09:39 2016 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1549819/+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 1533244] [NEW] lxc-net thinks it's already running after it failed
Public bug reported: When lxc-net fails (because dnsmasq failed to bind on an interface), it claims to actually be running (the /var/run/lxc/network_up file is present) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.5-0ubuntu0.15.10.3 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 12 14:49:06 2016 InstallationDate: Installed on 2012-08-17 (1242 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-12-06 (37 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1533244 Title: lxc-net thinks it's already running after it failed Status in lxc package in Ubuntu: New Bug description: When lxc-net fails (because dnsmasq failed to bind on an interface), it claims to actually be running (the /var/run/lxc/network_up file is present) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.5-0ubuntu0.15.10.3 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 12 14:49:06 2016 InstallationDate: Installed on 2012-08-17 (1242 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-12-06 (37 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533244/+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 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts
I had this issue and then purged my system of the Intel Linux Graphics Installer packages, downgrading packages to the latest available in trusty-updates as appropriate. After doing that I was successfully able to install 14.04.2 using the Utopic HWE stack. -- 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/1429529 Title: Package resolver can't find *-lts-utopic package dependencies, aborts Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html Guess APT just get overwhelmed by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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
