[Touch-packages] [Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage
** Changed in: oem-priority Importance: Critical => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live 18.04 with broken seed causes snapd high CPU usage Status in OEM Priority Project: Confirmed Status in snapd package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+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 1772578] [NEW] audio crackling
Public bug reported:
Hello,
on Ubuntu this bug regularly appearing: audio suddenly crackling for all
softwares.
If I restart pulseaudio, it changes nothing.
But if I restart gnome-shell ("alt+F2", type "r"), the audio no more crackling.
I had this bug for Ubuntu 17.10 and perhaps 17.04 too.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D7p: romain 3648 F...m pulseaudio
/dev/snd/controlC0: romain 3648 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May 22 07:56:34 2018
InstallationDate: Installed on 2012-07-07 (2144 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago)
dmi.bios.date: 09/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77A-G45 (MS-7752)
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.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7752
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/1772578
Title:
audio crackling
Status in pulseaudio package in Ubuntu:
New
Bug description:
Hello,
on Ubuntu this bug regularly appearing: audio suddenly crackling for all
softwares.
If I restart pulseaudio, it changes nothing.
But if I restart gnome-shell ("alt+F2", type "r"), the audio no more
crackling.
I had this bug for Ubuntu 17.10 and perhaps 17.04 too.
Thank you for your help.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D7p: romain 3648 F...m pulseaudio
/dev/snd/controlC0: romain 3648 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May 22 07:56:34 2018
InstallationDate: Installed on 2012-07-07 (2144 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago)
dmi.bios.date: 09/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77A-G45 (MS-7752)
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.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7752
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/1772578/+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 1772565] [NEW] Addition of Remove Button to gdebi to uninstall an already installed package
Public bug reported: I was wondering if its possible to add a remove button to gdebi to uninstall an existing package. Since the reinstall button is already there, it just seemed to be a logical step. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon May 21 23:21:03 2018 InstallationDate: Installed on 2018-05-09 (12 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdebi (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 gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1772565 Title: Addition of Remove Button to gdebi to uninstall an already installed package Status in gdebi package in Ubuntu: New Bug description: I was wondering if its possible to add a remove button to gdebi to uninstall an existing package. Since the reinstall button is already there, it just seemed to be a logical step. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon May 21 23:21:03 2018 InstallationDate: Installed on 2018-05-09 (12 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1772565/+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 1636382] Re: [Ubuntu 16.10] Host BT couldn't send file to device on platform with Intel BT card like 8260/3168/8265
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1636382 Title: [Ubuntu 16.10] Host BT couldn't send file to device on platform with Intel BT card like 8260/3168/8265 Status in bluez package in Ubuntu: Expired Bug description: Platform information: BT Card: intel 3168/8265/8260 OS: Ubuntu 16.10 release Kernel: 4.8.0-27-generic Details: 1. Open Bluetooth Setting UI: set Bluetooth and Visble ON 2. Open Bluetooth on Phone and Pair with Host 3. On Bluetooth Setting UI, send a file from the host to the paired Phone and there is no response on the two devices. 4. Ubuntu 16.04 doesn't have such issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1636382/+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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
** Tags removed: id-59c57605d1dfa992a27e9102 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1717983 Title: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration Status in avahi package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: In Progress Status in controlaula package in Ubuntu: Invalid Status in ddclient package in Ubuntu: Triaged Status in maas package in Ubuntu: Invalid Status in madwimax package in Ubuntu: Triaged Status in ntp package in Ubuntu: Fix Released Status in openresolv package in Ubuntu: Won't Fix Status in resolvconf package in Ubuntu: Won't Fix Status in samba package in Ubuntu: Triaged Status in sendmail package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Triaged Bug description: dhclient has been used as the dhcp client in Ubuntu and debian for many years. Over time, many packages have integrated with dhclient. The list below is of packages that have declared a dependency and those that have shipped hooks to be invoked by dhclient. As we move to systemd-networkd these will have to be addressed. # ./get-rdeps isc-dhcp-client | sort -u breaks - initramfs-tools (initramfs-tools) depends - dracut (dracut-network) depends - isc-dhcp (isc-dhcp-client-ddns) depends - libguestfs (libguestfs0) depends - maas (python3-maas-provisioningserver) depends - netscript-2.4 (netscript-2.4) depends - network-manager (network-manager) depends - ubuntu-meta (ubuntu-minimal) depends - walinuxagent (walinuxagent) depends - whereami (whereami) depends - wicd (wicd-daemon) depends - wifi-radar (wifi-radar) enhances - resolvconf (resolvconf) recommends - avahi (avahi-autoipd) recommends - ifupdown (ifupdown) recommends - ifupdown2 (ifupdown2) recommends - madwimax (madwimax) $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u avahi-autoipd cloud-init controlaula ddclient isc-dhcp-client ntp ntpdate openresolv resolvconf samba-common sendmail-base systemd whereami Another possible integration point that is not likely listed in the package dependencies is reading of the leases file for additional information. As an example, Azure advertises the location of its http based metadata service as an option in a dhclient response. cloud-init will read the lease files to find the correct address. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: isc-dhcp-client 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 12:46:31 2017 DhclientLeases: EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (788 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
Per /usr/share/sendmail/dynamic, /etc/dhcp3/dhclient-exit-
hooks.d/sendmail is considered deprecated in favor of
/etc/network/if-{up,post-down}.d/sendmail. Therefore for sendmail's
purposes, this is a duplicate of LP: #1718227.
** Changed in: sendmail (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1717983
Title:
replacement of isc-dhcp-client with with systemd-networkd for dhclient
needs integration
Status in avahi package in Ubuntu:
Invalid
Status in cloud-init package in Ubuntu:
In Progress
Status in controlaula package in Ubuntu:
Invalid
Status in ddclient package in Ubuntu:
Triaged
Status in maas package in Ubuntu:
Invalid
Status in madwimax package in Ubuntu:
Triaged
Status in ntp package in Ubuntu:
Fix Released
Status in openresolv package in Ubuntu:
Won't Fix
Status in resolvconf package in Ubuntu:
Won't Fix
Status in samba package in Ubuntu:
Triaged
Status in sendmail package in Ubuntu:
Invalid
Status in ubuntu-meta package in Ubuntu:
Triaged
Bug description:
dhclient has been used as the dhcp client in Ubuntu and debian for
many years. Over time, many packages have integrated with dhclient.
The list below is of packages that have declared a dependency and
those that have shipped hooks to be invoked by dhclient.
As we move to systemd-networkd these will have to be addressed.
# ./get-rdeps isc-dhcp-client | sort -u
breaks - initramfs-tools (initramfs-tools)
depends - dracut (dracut-network)
depends - isc-dhcp (isc-dhcp-client-ddns)
depends - libguestfs (libguestfs0)
depends - maas (python3-maas-provisioningserver)
depends - netscript-2.4 (netscript-2.4)
depends - network-manager (network-manager)
depends - ubuntu-meta (ubuntu-minimal)
depends - walinuxagent (walinuxagent)
depends - whereami (whereami)
depends - wicd (wicd-daemon)
depends - wifi-radar (wifi-radar)
enhances - resolvconf (resolvconf)
recommends - avahi (avahi-autoipd)
recommends - ifupdown (ifupdown)
recommends - ifupdown2 (ifupdown2)
recommends - madwimax (madwimax)
$ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
avahi-autoipd
cloud-init
controlaula
ddclient
isc-dhcp-client
ntp
ntpdate
openresolv
resolvconf
samba-common
sendmail-base
systemd
whereami
Another possible integration point that is not likely listed in the package
dependencies is reading of the leases file for additional information.
As an example, Azure advertises the location of its http based metadata
service as an option in a dhclient response. cloud-init will read the
lease files to find the correct address.
Related bugs:
* bug 1713803: replacement of resolvconf with systemd needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: isc-dhcp-client 4.3.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 18 12:46:31 2017
DhclientLeases:
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (788 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~t
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen
attached dmesg ( dmesg >~/dmesg_2018-05-22.txt ) this COULD be the key bit - unsure (thanks to well_laid_down in #xubuntu) [488956.180193] [drm:cypress_dpm_set_power_state [radeon]] *ERROR* rv770_restrict_performance_levels_before_switch failed [488957.778128] traps: light-locker[9579] trap int3 ip:7f228a785c41 sp:7ffdee1a6c50 error:0 in libglib-2.0.so.0.5600.1[7f228a734000+113000] ( dmesg file is unedited, contains other crash info i believe unreleated; but may contain detail on the same problem yesterday morning ) ** Attachment added: "dmesg >~/dmesg_2018-05-22.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5142673/+files/dmesg_2018-05-22.txt -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: New Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/u
[Touch-packages] [Bug 1758255] Re: lxc-tests package is not available in Bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1758255 Title: lxc-tests package is not available in Bionic Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: This lxc-tests required by the ubuntu_lxc test is not available on Bionic https://packages.ubuntu.com/search?keywords=lxc-tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758255/+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 1758255] Re: lxc-tests package is not available in Bionic
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) ** Tags added: bionic -- 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/1758255 Title: lxc-tests package is not available in Bionic Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: This lxc-tests required by the ubuntu_lxc test is not available on Bionic https://packages.ubuntu.com/search?keywords=lxc-tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758255/+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 1758255] Re: lxc-tests package is not available in Bionic
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1758255 Title: lxc-tests package is not available in Bionic Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: This lxc-tests required by the ubuntu_lxc test is not available on Bionic https://packages.ubuntu.com/search?keywords=lxc-tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758255/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
@seb128 could you advice on next step to resolve this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+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 1772538] Re: Can't start arm64 VM due to apparmor error.
This is a top-notch bug report! Thanks -- 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/1772538 Title: Can't start arm64 VM due to apparmor error. Status in apparmor package in Ubuntu: New Status in libvirt package in Ubuntu: New Bug description: I can create an aarch64 VM but when I go to start the VM I see this error: $ virsh start legal-coyote error: Failed to start domain legal-coyote error: internal error: cannot load AppArmor profile 'libvirt-9728b707-1f47-4cd7-a4ca-6eddf5d98d04' This was on a brand new ubuntu 16.04.4 install. Below are the steps that were executed, including what produced there error as well as some system information. 1. $ sudo apt update && sudo apt upgrade && sudo apt install emacs libvirt-bin qemu-system-arm qemu-efi 2. Created a VM with MAAS. 3. $ virsh list --all IdName State - legal-coyote shut off 4. $ virsh dumpxml legal-coyote legal-coyote 9728b707-1f47-4cd7-a4ca-6eddf5d98d04 1048576 1048576 1 hvm /usr/share/AAVMF/AAVMF_CODE.fd /usr/share/AAVMF/AAVMF_VARS.fd destroy restart restart /usr/bin/qemu-system-aarch64 5. $ virsh start legal-coyote error: Failed to start domain legal-coyote error: internal error: cannot load AppArmor profile 'libvirt-9728b707-1f47-4cd7-a4ca-6eddf5d98d04' 6. Checking dmesg... [ 726.425389] virbr0: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenialport 1(virbr0-nic) entered listening state [ 726.425419] virbr0: port 1(virbr0-nic) entered listening state [ 727.959553] virbr0: port 1(virbr0-nic) entered disabled state [ 896.933127] audit: type=1400 audit(1526946784.127:18): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.933169] audit: type=1400 audit(1526946784.127:19): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.933846] audit: type=1400 audit(1526946784.127:20): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.933890] audit: type=1400 audit(1526946784.127:21): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.937130] audit: type=1400 audit(1526946784.131:22): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/var/lib/libvirt/maas-images/796e5e0f-ab62-4e44-8189-bbc754635e0b" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.086388] audit: type=1400 audit(1526946830.280:23): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.086429] audit: type=1400 audit(1526946830.280:24): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.087171] audit: type=1400 audit(1526946830.280:25): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.087214] audit: type=1400 audit(1526946830.280:26): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.090417] audit: type=1400 audit(1526946830.284:27): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/var/lib/libvirt/maas-images/796e5e0f-ab62-4e44-8189-bbc754635e0b" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 7. $ dpkg -l | grep libvirt ii libvirt-bin 1.3.1-1ubuntu10.23 arm64programs for the libvirt library ii libvirt0:arm64
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
pulseaudio (1:11.1-1ubuntu8) cosmic; urgency=medium * 0804-bluez5-device-Rewrite-of-thread-function-reduce-send.patch, 0805-bluez5-device-Fix-memory-leak-in-sco_process_render.patch: - Reduce latency over bluetooth, using A2DP, when the connection drops temporarily (LP: #405294). -- Alberto Milone Mon, 21 May 2018 16:41:41 +0200 -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
pulseaudio (1:11.1-1ubuntu8) cosmic; urgency=medium * 0804-bluez5-device-Rewrite-of-thread-function-reduce-send.patch, 0805-bluez5-device-Fix-memory-leak-in-sco_process_render.patch: - Reduce latency over bluetooth, using A2DP, when the connection drops temporarily (LP: #405294). -- Alberto Milone Mon, 21 May 2018 16:41:41 +0200 ** Changed in: pulseaudio (Ubuntu) Status: In Progress => Fix Committed -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1772383] Re: WD15 Dell Thunderbolt dock no audio
[No change - copying the file in the same dir adding .bak is sufficient right- or will this be read as a 2nd conf?] adding .bak is ok, after reboot, you can run pactl list cards to verify if the change takes effect or not. Before change: Profiles: output:analog-stereo-speaker: Speaker (sinks: 1, sources: 0, priority: 60, available: yes) output:analog-stereo-headphone+input:analog-stereo-mic: Headset (sinks: 1, sources: 1, priority: 80, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) After change, the 1st two profiles disappear. If the change takes effect, but it still can't work, I think it is not a pulseaudio issue, probably the firmware issue of dock or kernel driver issue. And you can verify by these commands: aplay -D plughw:CARD=xxx,DEV=0 test.wav (replace xxx with the name of usb audio card, aplay -L to check the name of usb audio card) aplay -D plughw:CARD=xxx,DEV=1 test.wav And BTW, what does "the vanilla ones from upstream" mean? -- 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/1772383 Title: WD15 Dell Thunderbolt dock no audio Status in pulseaudio package in Ubuntu: New Bug description: Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benste 2287 F pulseaudio /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1772383/+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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
samba-common's dhclient hook needs porting. Setting to 'medium' as this only affects dhcp-provided netbios nameservers and netbios scope, which are relatively uncommon options. ** Changed in: samba (Ubuntu) Importance: Undecided => Medium ** Changed in: samba (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1717983 Title: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration Status in avahi package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: In Progress Status in controlaula package in Ubuntu: Invalid Status in ddclient package in Ubuntu: Triaged Status in maas package in Ubuntu: Invalid Status in madwimax package in Ubuntu: Triaged Status in ntp package in Ubuntu: Fix Released Status in openresolv package in Ubuntu: Won't Fix Status in resolvconf package in Ubuntu: Won't Fix Status in samba package in Ubuntu: Triaged Status in sendmail package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Triaged Bug description: dhclient has been used as the dhcp client in Ubuntu and debian for many years. Over time, many packages have integrated with dhclient. The list below is of packages that have declared a dependency and those that have shipped hooks to be invoked by dhclient. As we move to systemd-networkd these will have to be addressed. # ./get-rdeps isc-dhcp-client | sort -u breaks - initramfs-tools (initramfs-tools) depends - dracut (dracut-network) depends - isc-dhcp (isc-dhcp-client-ddns) depends - libguestfs (libguestfs0) depends - maas (python3-maas-provisioningserver) depends - netscript-2.4 (netscript-2.4) depends - network-manager (network-manager) depends - ubuntu-meta (ubuntu-minimal) depends - walinuxagent (walinuxagent) depends - whereami (whereami) depends - wicd (wicd-daemon) depends - wifi-radar (wifi-radar) enhances - resolvconf (resolvconf) recommends - avahi (avahi-autoipd) recommends - ifupdown (ifupdown) recommends - ifupdown2 (ifupdown2) recommends - madwimax (madwimax) $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u avahi-autoipd cloud-init controlaula ddclient isc-dhcp-client ntp ntpdate openresolv resolvconf samba-common sendmail-base systemd whereami Another possible integration point that is not likely listed in the package dependencies is reading of the leases file for additional information. As an example, Azure advertises the location of its http based metadata service as an option in a dhclient response. cloud-init will read the lease files to find the correct address. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: isc-dhcp-client 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 12:46:31 2017 DhclientLeases: EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (788 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+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 1772542] Re: after waking from sleep i get text radeon error message then return login screen
** Description changed: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. - - I expected to see the locker screen asking for password to return to - last nights session, instead have text (radeon) error message then - quickly the greeter & new session (once I'm login in) - - - I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) + + extract of /var/log/auth.log (copied from `view` hence line numbers) + // last-night + 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered + 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered + 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + // overnight + 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) + 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root + 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered + 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered + 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. + 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc + 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root + 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. + 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. + 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. + 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) + 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. + 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. + 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. + 67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 166. + 68 May 22 09:37:39 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session opened for user guiverc by (uid=0) + 69 May 22 09:37:39 d960-ubu2 systemd-logind[1108]: New session 178 of user guiverc. + 70 May 22 09:38:11 d960-ubu2 db
[Touch-packages] [Bug 1772542] [NEW] after waking from sleep i get text radeon error message then return login screen
Public bug reported: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I expected to see the locker screen asking for password to return to last nights session, instead have text (radeon) error message then quickly the greeter & new session (once I'm login in) - I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue May 22 10:29:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-19-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126] InstallationDate: Installed on 2017-11-16 (186 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. OptiPlex 960 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=afa7971f-3dd5-4b30-9c98-0af3e56a6f2b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0F428D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 1701283234 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/05/2011:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Description changed: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is
[Touch-packages] [Bug 1772538] [NEW] Can't start arm64 VM due to apparmor error.
Public bug reported: I can create an aarch64 VM but when I go to start the VM I see this error: $ virsh start legal-coyote error: Failed to start domain legal-coyote error: internal error: cannot load AppArmor profile 'libvirt-9728b707-1f47-4cd7-a4ca-6eddf5d98d04' This was on a brand new ubuntu 16.04.4 install. Below are the steps that were executed, including what produced there error as well as some system information. 1. $ sudo apt update && sudo apt upgrade && sudo apt install emacs libvirt-bin qemu-system-arm qemu-efi 2. Created a VM with MAAS. 3. $ virsh list --all IdName State - legal-coyote shut off 4. $ virsh dumpxml legal-coyote legal-coyote 9728b707-1f47-4cd7-a4ca-6eddf5d98d04 1048576 1048576 1 hvm /usr/share/AAVMF/AAVMF_CODE.fd /usr/share/AAVMF/AAVMF_VARS.fd destroy restart restart /usr/bin/qemu-system-aarch64 5. $ virsh start legal-coyote error: Failed to start domain legal-coyote error: internal error: cannot load AppArmor profile 'libvirt-9728b707-1f47-4cd7-a4ca-6eddf5d98d04' 6. Checking dmesg... [ 726.425389] virbr0: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenialport 1(virbr0-nic) entered listening state [ 726.425419] virbr0: port 1(virbr0-nic) entered listening state [ 727.959553] virbr0: port 1(virbr0-nic) entered disabled state [ 896.933127] audit: type=1400 audit(1526946784.127:18): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.933169] audit: type=1400 audit(1526946784.127:19): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.933846] audit: type=1400 audit(1526946784.127:20): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.933890] audit: type=1400 audit(1526946784.127:21): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9083/auxv" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 896.937130] audit: type=1400 audit(1526946784.131:22): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/var/lib/libvirt/maas-images/796e5e0f-ab62-4e44-8189-bbc754635e0b" pid=9083 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.086388] audit: type=1400 audit(1526946830.280:23): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.086429] audit: type=1400 audit(1526946830.280:24): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.087171] audit: type=1400 audit(1526946830.280:25): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.087214] audit: type=1400 audit(1526946830.280:26): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/proc/9174/auxv" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 943.090417] audit: type=1400 audit(1526946830.284:27): apparmor="DENIED" operation="open" profile="/usr/lib/libvirt/virt-aa-helper" name="/var/lib/libvirt/maas-images/796e5e0f-ab62-4e44-8189-bbc754635e0b" pid=9174 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 7. $ dpkg -l | grep libvirt ii libvirt-bin 1.3.1-1ubuntu10.23 arm64programs for the libvirt library ii libvirt0:arm64 1.3.1-1ubuntu10.23 arm64library for interfacing with different virtualization systems 8. $ dpkg -l | grep qemu ii ipxe-qemu1.0.0+git-20150424.a25a16d-1ubuntu1.2 all PXE boot firmware - ROM images for qemu ii qemu-block-extra:arm64 1:2.5+dfsg-5ubuntu10.29 arm64extra block backend modules for qemu-system and qemu-utils ii qemu-efi 0~20160408.ffea0a2c-2 all UEFI firmware
[Touch-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
This bug was fixed in the package linux-hwe-edge - 4.15.0-22.24~16.04.1 --- linux-hwe-edge (4.15.0-22.24~16.04.1) xenial; urgency=medium * CVE-2018-3639 (powerpc) - powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit - stf-barrier: set eieio instruction bit 6 for future optimisations * CVE-2018-3639 (x86) - x86/nospec: Simplify alternative_msr_write() - x86/bugs: Concentrate bug detection into a separate function - x86/bugs: Concentrate bug reporting into a separate function - x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits - x86/bugs, KVM: Support the combination of guest and host IBRS - x86/bugs: Expose /sys/../spec_store_bypass - x86/cpufeatures: Add X86_FEATURE_RDS - x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation - x86/bugs/intel: Set proper CPU features and setup RDS - x86/bugs: Whitelist allowed SPEC_CTRL MSR values - x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if requested - x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest - x86/speculation: Create spec-ctrl.h to avoid include hell - prctl: Add speculation control prctls - x86/process: Allow runtime control of Speculative Store Bypass - x86/speculation: Add prctl for Speculative Store Bypass mitigation - nospec: Allow getting/setting on non-current task - proc: Provide details on speculation flaw mitigations - seccomp: Enable speculation flaw mitigations - x86/bugs: Make boot modes __ro_after_init - prctl: Add force disable speculation - seccomp: Use PR_SPEC_FORCE_DISABLE - seccomp: Add filter flag to opt-out of SSB mitigation - seccomp: Move speculation migitation control to arch code - x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass - x86/bugs: Rename _RDS to _SSBD - proc: Use underscores for SSBD in 'status' - Documentation/spec_ctrl: Do some minor cleanups - x86/bugs: Fix __ssb_select_mitigation() return type - x86/bugs: Make cpu_show_common() static * LSM Stacking prctl values should be redefined as to not collide with upstream prctls (LP: #1769263) // CVE-2018-3639 - SAUCE: LSM stacking: adjust prctl values linux (4.15.0-21.22) bionic; urgency=medium * linux: 4.15.0-21.22 -proposed tracker (LP: #1767397) * initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 (LP: #1766727) - Add linux-image-* Breaks on s390-tools (<< 2.3.0-0ubuntu3) * linux-image-4.15.0-20-generic install after upgrade from xenial breaks (LP: #1767133) - Packaging: Depends on linux-base that provides the necessary tools * linux-image packages need to Breaks flash-kernel << 3.90ubuntu2 (LP: #1766629) - linux-image-* breaks on flash-kernel (<< 3.90ubuntu2) -- Stefan Bader Tue, 15 May 2018 07:41:28 +0200 ** Changed in: linux-hwe-edge (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in linux-hwe-edge source package in Xenial: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Released Status in linux-hwe-edge source package in Bionic: Invalid Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable sta
[Touch-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
This bug was fixed in the package linux-hwe-edge - 4.15.0-22.24~16.04.1 --- linux-hwe-edge (4.15.0-22.24~16.04.1) xenial; urgency=medium * CVE-2018-3639 (powerpc) - powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit - stf-barrier: set eieio instruction bit 6 for future optimisations * CVE-2018-3639 (x86) - x86/nospec: Simplify alternative_msr_write() - x86/bugs: Concentrate bug detection into a separate function - x86/bugs: Concentrate bug reporting into a separate function - x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits - x86/bugs, KVM: Support the combination of guest and host IBRS - x86/bugs: Expose /sys/../spec_store_bypass - x86/cpufeatures: Add X86_FEATURE_RDS - x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation - x86/bugs/intel: Set proper CPU features and setup RDS - x86/bugs: Whitelist allowed SPEC_CTRL MSR values - x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if requested - x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest - x86/speculation: Create spec-ctrl.h to avoid include hell - prctl: Add speculation control prctls - x86/process: Allow runtime control of Speculative Store Bypass - x86/speculation: Add prctl for Speculative Store Bypass mitigation - nospec: Allow getting/setting on non-current task - proc: Provide details on speculation flaw mitigations - seccomp: Enable speculation flaw mitigations - x86/bugs: Make boot modes __ro_after_init - prctl: Add force disable speculation - seccomp: Use PR_SPEC_FORCE_DISABLE - seccomp: Add filter flag to opt-out of SSB mitigation - seccomp: Move speculation migitation control to arch code - x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass - x86/bugs: Rename _RDS to _SSBD - proc: Use underscores for SSBD in 'status' - Documentation/spec_ctrl: Do some minor cleanups - x86/bugs: Fix __ssb_select_mitigation() return type - x86/bugs: Make cpu_show_common() static * LSM Stacking prctl values should be redefined as to not collide with upstream prctls (LP: #1769263) // CVE-2018-3639 - SAUCE: LSM stacking: adjust prctl values linux (4.15.0-21.22) bionic; urgency=medium * linux: 4.15.0-21.22 -proposed tracker (LP: #1767397) * initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 (LP: #1766727) - Add linux-image-* Breaks on s390-tools (<< 2.3.0-0ubuntu3) * linux-image-4.15.0-20-generic install after upgrade from xenial breaks (LP: #1767133) - Packaging: Depends on linux-base that provides the necessary tools * linux-image packages need to Breaks flash-kernel << 3.90ubuntu2 (LP: #1766629) - linux-image-* breaks on flash-kernel (<< 3.90ubuntu2) -- Stefan Bader Tue, 15 May 2018 07:41:28 +0200 -- 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/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in linux-hwe-edge source package in Xenial: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Released Status in linux-hwe-edge source package in Bionic: Invalid Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for syste
[Touch-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
This bug was fixed in the package linux - 4.15.0-22.24 --- linux (4.15.0-22.24) bionic; urgency=medium * CVE-2018-3639 (powerpc) - powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit - stf-barrier: set eieio instruction bit 6 for future optimisations * CVE-2018-3639 (x86) - x86/nospec: Simplify alternative_msr_write() - x86/bugs: Concentrate bug detection into a separate function - x86/bugs: Concentrate bug reporting into a separate function - x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits - x86/bugs, KVM: Support the combination of guest and host IBRS - x86/bugs: Expose /sys/../spec_store_bypass - x86/cpufeatures: Add X86_FEATURE_RDS - x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation - x86/bugs/intel: Set proper CPU features and setup RDS - x86/bugs: Whitelist allowed SPEC_CTRL MSR values - x86/bugs/AMD: Add support to disable RDS on Fam[15,16,17]h if requested - x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest - x86/speculation: Create spec-ctrl.h to avoid include hell - prctl: Add speculation control prctls - x86/process: Allow runtime control of Speculative Store Bypass - x86/speculation: Add prctl for Speculative Store Bypass mitigation - nospec: Allow getting/setting on non-current task - proc: Provide details on speculation flaw mitigations - seccomp: Enable speculation flaw mitigations - x86/bugs: Make boot modes __ro_after_init - prctl: Add force disable speculation - seccomp: Use PR_SPEC_FORCE_DISABLE - seccomp: Add filter flag to opt-out of SSB mitigation - seccomp: Move speculation migitation control to arch code - x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass - x86/bugs: Rename _RDS to _SSBD - proc: Use underscores for SSBD in 'status' - Documentation/spec_ctrl: Do some minor cleanups - x86/bugs: Fix __ssb_select_mitigation() return type - x86/bugs: Make cpu_show_common() static * LSM Stacking prctl values should be redefined as to not collide with upstream prctls (LP: #1769263) // CVE-2018-3639 - SAUCE: LSM stacking: adjust prctl values linux (4.15.0-21.22) bionic; urgency=medium * linux: 4.15.0-21.22 -proposed tracker (LP: #1767397) * initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 (LP: #1766727) - Add linux-image-* Breaks on s390-tools (<< 2.3.0-0ubuntu3) * linux-image-4.15.0-20-generic install after upgrade from xenial breaks (LP: #1767133) - Packaging: Depends on linux-base that provides the necessary tools * linux-image packages need to Breaks flash-kernel << 3.90ubuntu2 (LP: #1766629) - linux-image-* breaks on flash-kernel (<< 3.90ubuntu2) -- Stefan Bader Tue, 15 May 2018 07:41:28 +0200 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639 ** Changed in: linux-hwe-edge (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in linux-hwe-edge source package in Xenial: Fix Released Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Released Status in linux-hwe-edge source package in Bionic: Invalid Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned
[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
python3-maas-provisioningserver calls dhclient directly in order to do network discovery. This does not need replaced with networkd integration. ** Changed in: maas (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1717983 Title: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration Status in avahi package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: In Progress Status in controlaula package in Ubuntu: Invalid Status in ddclient package in Ubuntu: Triaged Status in maas package in Ubuntu: Invalid Status in madwimax package in Ubuntu: Triaged Status in ntp package in Ubuntu: Fix Released Status in openresolv package in Ubuntu: Won't Fix Status in resolvconf package in Ubuntu: Won't Fix Status in samba package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Triaged Bug description: dhclient has been used as the dhcp client in Ubuntu and debian for many years. Over time, many packages have integrated with dhclient. The list below is of packages that have declared a dependency and those that have shipped hooks to be invoked by dhclient. As we move to systemd-networkd these will have to be addressed. # ./get-rdeps isc-dhcp-client | sort -u breaks - initramfs-tools (initramfs-tools) depends - dracut (dracut-network) depends - isc-dhcp (isc-dhcp-client-ddns) depends - libguestfs (libguestfs0) depends - maas (python3-maas-provisioningserver) depends - netscript-2.4 (netscript-2.4) depends - network-manager (network-manager) depends - ubuntu-meta (ubuntu-minimal) depends - walinuxagent (walinuxagent) depends - whereami (whereami) depends - wicd (wicd-daemon) depends - wifi-radar (wifi-radar) enhances - resolvconf (resolvconf) recommends - avahi (avahi-autoipd) recommends - ifupdown (ifupdown) recommends - ifupdown2 (ifupdown2) recommends - madwimax (madwimax) $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u avahi-autoipd cloud-init controlaula ddclient isc-dhcp-client ntp ntpdate openresolv resolvconf samba-common sendmail-base systemd whereami Another possible integration point that is not likely listed in the package dependencies is reading of the leases file for additional information. As an example, Azure advertises the location of its http based metadata service as an option in a dhclient response. cloud-init will read the lease files to find the correct address. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: isc-dhcp-client 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 12:46:31 2017 DhclientLeases: EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (788 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+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 1772537] [NEW] Wrong combining sequence in Compose for the Finnish locale
Public bug reported: The Compose file for the fi_FI.UTF-8 locale at /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following lines: : "Ệ" U1EC6 # LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND ACUTE : "Ệ" U1EC6 # LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND DOT BELOW Thus the codepoint "Ệ" U1EC6 is produced with two different sequences. Based on the key sequences and the comments at the ends of the lines, it is clear that the first line is a mistake. Instead of "Ệ" U1EC6, the line should read "Ế" U1EBE, a character which cannot be produced with the current Compose file otherwise at all. Description:Ubuntu 17.10 Release:17.10 libx11-data: Installed: 2:1.6.4-3 Candidate: 2:1.6.4-3 Version table: *** 2:1.6.4-3 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1772537 Title: Wrong combining sequence in Compose for the Finnish locale Status in libx11 package in Ubuntu: New Bug description: The Compose file for the fi_FI.UTF-8 locale at /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following lines: : "Ệ" U1EC6 # LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND ACUTE : "Ệ" U1EC6 # LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND DOT BELOW Thus the codepoint "Ệ" U1EC6 is produced with two different sequences. Based on the key sequences and the comments at the ends of the lines, it is clear that the first line is a mistake. Instead of "Ệ" U1EC6, the line should read "Ế" U1EBE, a character which cannot be produced with the current Compose file otherwise at all. Description: Ubuntu 17.10 Release: 17.10 libx11-data: Installed: 2:1.6.4-3 Candidate: 2:1.6.4-3 Version table: *** 2:1.6.4-3 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1772537/+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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
"high" for ddclient wrt the importance of the hook to the operation of the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1717983 Title: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration Status in avahi package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: In Progress Status in controlaula package in Ubuntu: Invalid Status in ddclient package in Ubuntu: Triaged Status in maas package in Ubuntu: New Status in madwimax package in Ubuntu: Triaged Status in ntp package in Ubuntu: Fix Released Status in openresolv package in Ubuntu: Won't Fix Status in resolvconf package in Ubuntu: Won't Fix Status in samba package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Triaged Bug description: dhclient has been used as the dhcp client in Ubuntu and debian for many years. Over time, many packages have integrated with dhclient. The list below is of packages that have declared a dependency and those that have shipped hooks to be invoked by dhclient. As we move to systemd-networkd these will have to be addressed. # ./get-rdeps isc-dhcp-client | sort -u breaks - initramfs-tools (initramfs-tools) depends - dracut (dracut-network) depends - isc-dhcp (isc-dhcp-client-ddns) depends - libguestfs (libguestfs0) depends - maas (python3-maas-provisioningserver) depends - netscript-2.4 (netscript-2.4) depends - network-manager (network-manager) depends - ubuntu-meta (ubuntu-minimal) depends - walinuxagent (walinuxagent) depends - whereami (whereami) depends - wicd (wicd-daemon) depends - wifi-radar (wifi-radar) enhances - resolvconf (resolvconf) recommends - avahi (avahi-autoipd) recommends - ifupdown (ifupdown) recommends - ifupdown2 (ifupdown2) recommends - madwimax (madwimax) $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u avahi-autoipd cloud-init controlaula ddclient isc-dhcp-client ntp ntpdate openresolv resolvconf samba-common sendmail-base systemd whereami Another possible integration point that is not likely listed in the package dependencies is reading of the leases file for additional information. As an example, Azure advertises the location of its http based metadata service as an option in a dhclient response. cloud-init will read the lease files to find the correct address. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: isc-dhcp-client 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 12:46:31 2017 DhclientLeases: EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (788 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
controlaula does not exist in Ubuntu beyond artful. So invalid for bionic, and wontfix for artful. ** Changed in: controlaula (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1717983 Title: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration Status in avahi package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: In Progress Status in controlaula package in Ubuntu: Invalid Status in ddclient package in Ubuntu: Triaged Status in maas package in Ubuntu: New Status in madwimax package in Ubuntu: Triaged Status in ntp package in Ubuntu: Fix Released Status in openresolv package in Ubuntu: Won't Fix Status in resolvconf package in Ubuntu: Won't Fix Status in samba package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Triaged Bug description: dhclient has been used as the dhcp client in Ubuntu and debian for many years. Over time, many packages have integrated with dhclient. The list below is of packages that have declared a dependency and those that have shipped hooks to be invoked by dhclient. As we move to systemd-networkd these will have to be addressed. # ./get-rdeps isc-dhcp-client | sort -u breaks - initramfs-tools (initramfs-tools) depends - dracut (dracut-network) depends - isc-dhcp (isc-dhcp-client-ddns) depends - libguestfs (libguestfs0) depends - maas (python3-maas-provisioningserver) depends - netscript-2.4 (netscript-2.4) depends - network-manager (network-manager) depends - ubuntu-meta (ubuntu-minimal) depends - walinuxagent (walinuxagent) depends - whereami (whereami) depends - wicd (wicd-daemon) depends - wifi-radar (wifi-radar) enhances - resolvconf (resolvconf) recommends - avahi (avahi-autoipd) recommends - ifupdown (ifupdown) recommends - ifupdown2 (ifupdown2) recommends - madwimax (madwimax) $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u avahi-autoipd cloud-init controlaula ddclient isc-dhcp-client ntp ntpdate openresolv resolvconf samba-common sendmail-base systemd whereami Another possible integration point that is not likely listed in the package dependencies is reading of the leases file for additional information. As an example, Azure advertises the location of its http based metadata service as an option in a dhclient response. cloud-init will read the lease files to find the correct address. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: isc-dhcp-client 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 12:46:31 2017 DhclientLeases: EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (788 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration
ddclient wants to send updated IP address information to the dyndns server when a new IP address is received from DHCP. This should be supplemented with a networkd-dispatcher routable.d hook. ** Changed in: ddclient (Ubuntu) Status: New => Triaged ** Changed in: ddclient (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1717983 Title: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration Status in avahi package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: In Progress Status in controlaula package in Ubuntu: Invalid Status in ddclient package in Ubuntu: Triaged Status in maas package in Ubuntu: New Status in madwimax package in Ubuntu: Triaged Status in ntp package in Ubuntu: Fix Released Status in openresolv package in Ubuntu: Won't Fix Status in resolvconf package in Ubuntu: Won't Fix Status in samba package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Triaged Bug description: dhclient has been used as the dhcp client in Ubuntu and debian for many years. Over time, many packages have integrated with dhclient. The list below is of packages that have declared a dependency and those that have shipped hooks to be invoked by dhclient. As we move to systemd-networkd these will have to be addressed. # ./get-rdeps isc-dhcp-client | sort -u breaks - initramfs-tools (initramfs-tools) depends - dracut (dracut-network) depends - isc-dhcp (isc-dhcp-client-ddns) depends - libguestfs (libguestfs0) depends - maas (python3-maas-provisioningserver) depends - netscript-2.4 (netscript-2.4) depends - network-manager (network-manager) depends - ubuntu-meta (ubuntu-minimal) depends - walinuxagent (walinuxagent) depends - whereami (whereami) depends - wicd (wicd-daemon) depends - wifi-radar (wifi-radar) enhances - resolvconf (resolvconf) recommends - avahi (avahi-autoipd) recommends - ifupdown (ifupdown) recommends - ifupdown2 (ifupdown2) recommends - madwimax (madwimax) $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u avahi-autoipd cloud-init controlaula ddclient isc-dhcp-client ntp ntpdate openresolv resolvconf samba-common sendmail-base systemd whereami Another possible integration point that is not likely listed in the package dependencies is reading of the leases file for additional information. As an example, Azure advertises the location of its http based metadata service as an option in a dhclient response. cloud-init will read the lease files to find the correct address. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: isc-dhcp-client 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 12:46:31 2017 DhclientLeases: EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (788 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1717983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1772530] [NEW] OpenLDAP depends on old version of KRB5 which conflicts with other packages
Hi Dylan, On Mon, May 21, 2018 at 10:22:23PM -, Dylan Gray wrote: >Currently, Ubuntu 16.04's newest offered version of OpenLDAP is version >2.4.42. This version depends on libgssapi3 which in turn depends libkrb5 >version 2.6. Many other common libraries (like gssapi_krb5) depend on >libkrb5 3.0. I'm not sure what you're trying to say here. The version numbers in the library filenames (3 and 26 in your examples) track the library's public interface, not the software version. libkrb5.so.3 is the MIT Kerberos implementation: https://packages.ubuntu.com/xenial-updates/libkrb5-3 libkrb5.so.26 is the Heimdal Kerberos implementation: https://packages.ubuntu.com/xenial-updates/libkrb5-26-heimdal Could you please be specific about what problem you are having and why you think it is caused by the Kerberos libraries? Note that if you use GSSAPI via SASL, then you can choose which Kerberos implementation is used, by installing resp. libsasl2-modules-gssapi-mit or libsasl2-modules-gssapi-heimdal. ** Changed in: openldap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1772530 Title: OpenLDAP depends on old version of KRB5 which conflicts with other packages Status in openldap package in Ubuntu: Incomplete Bug description: Currently, Ubuntu 16.04's newest offered version of OpenLDAP is version 2.4.42. This version depends on libgssapi3 which in turn depends libkrb5 version 2.6. Many other common libraries (like gssapi_krb5) depend on libkrb5 3.0. From what I can tell, OpenLDAP version 2.4.44 fixes this issue, but it is not available from any of the Ubuntu repo's. It would be fabulous if this could be fixed. Repo: > # OpenLDAP depends on krb5 2.6 > readelf -d /usr/lib/x86_64-linux-gnu/libldap.so Dynamic section at offset 0x4d548 contains 32 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [liblber-2.4.so.2] 0x0001 (NEEDED) Shared library: [libresolv.so.2] 0x0001 (NEEDED) Shared library: [libsasl2.so.2] 0x0001 (NEEDED) Shared library: [libgssapi.so.3] 0x0001 (NEEDED) Shared library: [libgnutls.so.30] 0x0001 (NEEDED) Shared library: [libpthread.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libldap_r-2.4.so.2] >readelf -d /usr/lib/x86_64-linux-gnu/libgssapi.so.3 Dynamic section at offset 0x3daa8 contains 34 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libheimntlm.so.0] 0x0001 (NEEDED) Shared library: [libkrb5.so.26] 0x0001 (NEEDED) Shared library: [libasn1.so.8] 0x0001 (NEEDED) Shared library: [libcom_err.so.2] 0x0001 (NEEDED) Shared library: [libhcrypto.so.4] 0x0001 (NEEDED) Shared library: [libroken.so.18] 0x0001 (NEEDED) Shared library: [libpthread.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libgssapi.so.3] > # gssapi_krb5 and default krb5 depend on krb5 3.0 > readelf -d /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so Dynamic section at offset 0x47c48 contains 31 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libkrb5.so.3] 0x0001 (NEEDED) Shared library: [libk5crypto.so.3] 0x0001 (NEEDED) Shared library: [libcom_err.so.2] 0x0001 (NEEDED) Shared library: [libkrb5support.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libgssapi_krb5.so.2] > readelf -d /usr/lib/x86_64-linux-gnu/libkrb5.so Dynamic section at offset 0xcfcc0 contains 32 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libk5crypto.so.3] 0x0001 (NEEDED) Shared library: [libcom_err.so.2] 0x0001 (NEEDED) Shared library: [libkrb5support.so.0] 0x0001 (NEEDED) Shared library: [libkeyutils.so.1] 0x0001 (NEEDED) Shared library: [libresolv.so.2] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libkrb5.so.3] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/177253
[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf
** Description changed: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. + [Regression Potential] + The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. + Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. [Regression Potential] The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+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 1768615] Re: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1768615 Title: Intel HD3000 Sandy Bridge - Wrong display driver used by X.org Status in xorg package in Ubuntu: Confirmed Bug description: Hello, in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor performance due to software acceleration. When I switch to Wayland, the correct driver (intel) with enabled hardware acceleration is loaded. I have two exactly the same laptops, the same issue on both. Hardware: HP ProBook 4330s Intel i5-2430M 8GB RAM 512GB SDD Kernel: 4.15.0-20-generic Installed packages: ii intel-gpu-tools1.22-1 ii intel-microcode3.20180312.0~ubuntu18.04.1 ii libdrm-intel1:amd642.4.91-2 ii libdrm-intel1:i386 2.4.91-2 ii libegl-mesa0:amd64 18.0.0~rc5-1ubuntu1 ii libegl1-mesa:amd64 18.0.0~rc5-1ubuntu1 ii libgl1-mesa-dri:amd64 18.0.0~rc5-1ubuntu1 ii libgl1-mesa-dri:i386 18.0.0~rc5-1ubuntu1 ii libgl1-mesa-glx:amd64 18.0.0~rc5-1ubuntu1 ii libgl1-mesa-glx:i386 18.0.0~rc5-1ubuntu1 ii libglapi-mesa:amd6418.0.0~rc5-1ubuntu1 ii libglapi-mesa:i386 18.0.0~rc5-1ubuntu1 ii libgles2-mesa:amd6418.0.0~rc5-1ubuntu1 ii libglu1-mesa:amd64 9.0.0-2.1build1 ii libglu1-mesa:i386 9.0.0-2.1build1 ii libglx-mesa0:amd64 18.0.0~rc5-1ubuntu1 ii libglx-mesa0:i386 18.0.0~rc5-1ubuntu1 ii libosmesa6:amd64 18.0.0~rc5-1ubuntu1 ii libosmesa6:i38618.0.0~rc5-1ubuntu1 ii libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1 ii mesa-utils 8.4.0-1 ii mesa-va-drivers:amd64 18.0.0~rc5-1ubuntu1 ii mesa-vdpau-drivers:amd64 18.0.0~rc5-1ubuntu1 ii libva-wayland2:amd64 2.1.0-3 ii libwayland-client0:amd64 1.14.0-2 ii libwayland-cursor0:amd64 1.14.0-2 ii libwayland-egl1-mesa:amd64 18.0.0~rc5-1ubuntu1 ii libwayland-server0:amd64 1.14.0-2 ii xwayland 2:1.19.6-1ubuntu4 ii xserver-xorg-video-intel 2:2.99.917+git20171229-1 ii xorg-docs-core 1:1.7.1-1.1 ii xserver-xorg 1:7.7+19ubuntu7 ii xserver-xorg-core 2:1.19.6-1ubuntu4 ii xserver-xorg-input-all 1:7.7+19ubuntu7 ii xserver-xorg-input-libinput0.27.1-1 ii xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 ii xserver-xorg-legacy2:1.19.6-1ubuntu4 ii xserver-xorg-video-all 1:7.7+19ubuntu7 ii xserver-xorg-video-amdgpu 18.0.1-1
[Touch-packages] [Bug 1772530] [NEW] OpenLDAP depends on old version of KRB5 which conflicts with other packages
Public bug reported: Currently, Ubuntu 16.04's newest offered version of OpenLDAP is version 2.4.42. This version depends on libgssapi3 which in turn depends libkrb5 version 2.6. Many other common libraries (like gssapi_krb5) depend on libkrb5 3.0. From what I can tell, OpenLDAP version 2.4.44 fixes this issue, but it is not available from any of the Ubuntu repo's. It would be fabulous if this could be fixed. Repo: > # OpenLDAP depends on krb5 2.6 > readelf -d /usr/lib/x86_64-linux-gnu/libldap.so Dynamic section at offset 0x4d548 contains 32 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [liblber-2.4.so.2] 0x0001 (NEEDED) Shared library: [libresolv.so.2] 0x0001 (NEEDED) Shared library: [libsasl2.so.2] 0x0001 (NEEDED) Shared library: [libgssapi.so.3] 0x0001 (NEEDED) Shared library: [libgnutls.so.30] 0x0001 (NEEDED) Shared library: [libpthread.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libldap_r-2.4.so.2] >readelf -d /usr/lib/x86_64-linux-gnu/libgssapi.so.3 Dynamic section at offset 0x3daa8 contains 34 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libheimntlm.so.0] 0x0001 (NEEDED) Shared library: [libkrb5.so.26] 0x0001 (NEEDED) Shared library: [libasn1.so.8] 0x0001 (NEEDED) Shared library: [libcom_err.so.2] 0x0001 (NEEDED) Shared library: [libhcrypto.so.4] 0x0001 (NEEDED) Shared library: [libroken.so.18] 0x0001 (NEEDED) Shared library: [libpthread.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libgssapi.so.3] > # gssapi_krb5 and default krb5 depend on krb5 3.0 > readelf -d /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so Dynamic section at offset 0x47c48 contains 31 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libkrb5.so.3] 0x0001 (NEEDED) Shared library: [libk5crypto.so.3] 0x0001 (NEEDED) Shared library: [libcom_err.so.2] 0x0001 (NEEDED) Shared library: [libkrb5support.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libgssapi_krb5.so.2] > readelf -d /usr/lib/x86_64-linux-gnu/libkrb5.so Dynamic section at offset 0xcfcc0 contains 32 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libk5crypto.so.3] 0x0001 (NEEDED) Shared library: [libcom_err.so.2] 0x0001 (NEEDED) Shared library: [libkrb5support.so.0] 0x0001 (NEEDED) Shared library: [libkeyutils.so.1] 0x0001 (NEEDED) Shared library: [libresolv.so.2] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libkrb5.so.3] ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1772530 Title: OpenLDAP depends on old version of KRB5 which conflicts with other packages Status in openldap package in Ubuntu: New Bug description: Currently, Ubuntu 16.04's newest offered version of OpenLDAP is version 2.4.42. This version depends on libgssapi3 which in turn depends libkrb5 version 2.6. Many other common libraries (like gssapi_krb5) depend on libkrb5 3.0. From what I can tell, OpenLDAP version 2.4.44 fixes this issue, but it is not available from any of the Ubuntu repo's. It would be fabulous if this could be fixed. Repo: > # OpenLDAP depends on krb5 2.6 > readelf -d /usr/lib/x86_64-linux-gnu/libldap.so Dynamic section at offset 0x4d548 contains 32 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [liblber-2.4.so.2] 0x0001 (NEEDED) Shared library: [libresolv.so.2] 0x0001 (NEEDED) Shared library: [libsasl2.so.2] 0x0001 (NEEDED) Shared library: [libgssapi.so.3] 0x0001 (NEEDED) Shared library: [libgnutls.so.30] 0x0001 (NEEDED) Shared library: [libpthread.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [l
[Touch-packages] [Bug 1772488] Re: ubuntu tries to report bugs against unofficial repository packages
** Package changed: ubuntu => apport (Ubuntu) -- 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/1772488 Title: ubuntu tries to report bugs against unofficial repository packages Status in apport package in Ubuntu: New Bug description: When a program dies a report problem to ubuntu window comes up, even if it can't actually report the problem to ubuntu because it isn't an official repository package. There is no reason for it to come up in the first place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1772488/+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 1772512] [NEW] Unable to install i386 and amd64 arch at the same time
Public bug reported: Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: libxkbcommon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: New Bug description: Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1772488] [NEW] ubuntu tries to report bugs against unofficial repository packages
You have been subscribed to a public bug: When a program dies a report problem to ubuntu window comes up, even if it can't actually report the problem to ubuntu because it isn't an official repository package. There is no reason for it to come up in the first place. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- ubuntu tries to report bugs against unofficial repository packages https://bugs.launchpad.net/bugs/1772488 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport 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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Artful) Status: New => Confirmed -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
We have multiple [1Password X](https://support.1password.com/getting- started-1password-x/) users who are unable to unlock 1Password due to this issue on Ubuntu 18.04. I have a [temporary post on our discussion form](https://discussions.agilebits.com/discussion/90011/p1) advising our users on this issue, but we hope for a timely fix. Thanks to everyone helping to get this resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+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 269651]
http://besides.foryourbirthday.ca Thomas Delbeke -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/269651 Title: console-kit-daemon crashed with SIGSEGV in g_str_hash() Status in ConsoleKit: Fix Released Status in consolekit package in Ubuntu: Fix Released Status in consolekit source package in Hardy: Won't Fix Status in consolekit source package in Intrepid: Fix Released Bug description: Binary package hint: consolekit i'm playing music with rhythymbox.. and the console- kit is falling down ProblemType: Crash Architecture: i386 CrashCounter: 1 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/sbin/console-kit-daemon NonfreeKernelModules: ath_hal Package: consolekit 0.2.10-1ubuntu4 ProcAttrCurrent: unconfined ProcCmdline: /usr/sbin/console-kit-daemon ProcEnviron: Signal: 11 SourcePackage: consolekit StacktraceTop: g_str_hash () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/libglib-2.0.so.0 ?? () ?? () ?? () Title: console-kit-daemon crashed with SIGSEGV in g_str_hash() Uname: Linux 2.6.27-2-generic i686 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/consolekit/+bug/269651/+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 275897]
*** This bug is a duplicate of bug 273761 *** https://bugs.launchpad.net/bugs/273761 http://mission.itafaji.com Thomas Delbeke -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/275897 Title: telinit crashed with SIGSEGV in main() Status in upstart package in Ubuntu: New Bug description: Binary package hint: upstart Crashed while doing updates on 29-Sept-08. ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /sbin/telinit NonfreeKernelModules: nvidia Package: upstart-compat-sysv 0.3.9-7 ProcAttrCurrent: unconfined ProcCmdline: init u ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: upstart Stacktrace: #0 0xb802c16e in ?? () from /sbin/telinit #1 0xb8028a9e in main () from /sbin/telinit StacktraceTop: ?? () from /sbin/telinit main () from /sbin/telinit ThreadStacktrace: . Thread 1 (process 7106): #0 0xb802c16e in ?? () from /sbin/telinit #1 0xb8028a9e in main () from /sbin/telinit Title: telinit crashed with SIGSEGV in main() Uname: Linux 2.6.27-4-generic i686 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/275897/+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 1763096] Re: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)
This bug was fixed in the package binutils - 2.30-20ubuntu2 --- binutils (2.30-20ubuntu2) cosmic; urgency=medium * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098. * Fix PR binutils/23054, memory corruption in as. LP: #1763096. * Fix PR ld/23055, memory corruption in ld. LP: #1763094. binutils (2.30-20ubuntu1) cosmic; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. binutils (2.30-20) unstable; urgency=medium * Update, taken from the 2.30 branch 20180516. - Fix PR binutils/23109, disassembly mask for vector sdot on AArch64. - Fix uninitialised memory acccess in COFF bfd backend. - Update Portuguese translations. binutils (2.30-19) unstable; urgency=medium * Build-depend on procps. -- Matthias Klose Wed, 16 May 2018 13:03:58 -0400 ** Changed in: binutils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1763096 Title: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1) Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: Confirmed Bug description: Dear all, The following binutils as-new memory corruptions were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing inputs and each ASAN report. Steps to reproduce: Build current verison of binutils: ``` pull-lp-source binutils cd binutils-2.30 CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" ./configure CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make ``` run inputs under ASAN: ``` ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./as-new $file ``` We can verify those issues for as-new binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source bintuils"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763096/+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 1763094] Re: Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)
This bug was fixed in the package binutils - 2.30-20ubuntu2 --- binutils (2.30-20ubuntu2) cosmic; urgency=medium * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098. * Fix PR binutils/23054, memory corruption in as. LP: #1763096. * Fix PR ld/23055, memory corruption in ld. LP: #1763094. binutils (2.30-20ubuntu1) cosmic; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. binutils (2.30-20) unstable; urgency=medium * Update, taken from the 2.30 branch 20180516. - Fix PR binutils/23109, disassembly mask for vector sdot on AArch64. - Fix uninitialised memory acccess in COFF bfd backend. - Update Portuguese translations. binutils (2.30-19) unstable; urgency=medium * Build-depend on procps. -- Matthias Klose Wed, 16 May 2018 13:03:58 -0400 ** Changed in: binutils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1763094 Title: Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1) Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: Confirmed Bug description: Dear all, The following binutils ld-new memory corruptions were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing inputs and each ASAN report. Steps to reproduce: Build current verison of binutils: ``` pull-lp-source binutils cd binutils-2.30 CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" ./configure CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make ``` Run inputs under ASAN: ``` ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./ld-new $file ``` We can verify those issues for ld-new binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source bintuils"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763094/+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 1763098] Re: Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)
This bug was fixed in the package binutils - 2.30-20ubuntu2 --- binutils (2.30-20ubuntu2) cosmic; urgency=medium * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098. * Fix PR binutils/23054, memory corruption in as. LP: #1763096. * Fix PR ld/23055, memory corruption in ld. LP: #1763094. binutils (2.30-20ubuntu1) cosmic; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. binutils (2.30-20) unstable; urgency=medium * Update, taken from the 2.30 branch 20180516. - Fix PR binutils/23109, disassembly mask for vector sdot on AArch64. - Fix uninitialised memory acccess in COFF bfd backend. - Update Portuguese translations. binutils (2.30-19) unstable; urgency=medium * Build-depend on procps. -- Matthias Klose Wed, 16 May 2018 13:03:58 -0400 ** Changed in: binutils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1763098 Title: Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1) Status in binutils package in Ubuntu: Fix Released Bug description: Dear all, The following binutils gprof memory corruptions were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing inputs and each ASAN report. Steps to reproduce: Build current verison of binutils: ``` pull-lp-source binutils cd binutils-2.30 CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" ./configure CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make ``` Run inputs under ASAN: ``` ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./gprof $file ``` We can verify those issues for gprof binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source bintuils"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763098/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: ethtool (Ubuntu)
Importance: Undecided => Low
** Changed in: ethtool (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
This also affects adobe brackets, as referenced here: https://github.com/adobe/brackets/issues/14171 ** Bug watch added: github.com/adobe/brackets/issues #14171 https://github.com/adobe/brackets/issues/14171 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1722185] Re: Crash installing packages using debconf
This bug was fixed in the package packagekit - 1.1.10-1ubuntu1 --- packagekit (1.1.10-1ubuntu1) cosmic; urgency=medium * debian/patches/0001-De-register-callbacks-on-PkClientHelper-finalize.patch: * debian/patches/0001-Fix-issues-with-debconf-helper-not-working.patch: - Fix debconf interaction (LP: #1722185) -- Robert Ancell Mon, 21 May 2018 15:13:02 +1200 ** Changed in: packagekit (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+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 1695784] Re: package python-crypto 2.6.1-4ubuntu0.2 [modified: usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/__init__.py usr/lib/python2.7/dist-packages/Crypto/SelfTe
Seems more like a bug in pycompile, as that is responsible to byte- compile the py files. ** Package changed: python-crypto (Ubuntu) => python-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1695784 Title: package python-crypto 2.6.1-4ubuntu0.2 [modified: usr/lib/python2.7 /dist-packages/Crypto/SelfTest/Signature/__init__.py usr/lib/python2.7 /dist-packages/Crypto/SelfTest/Signature/test_pkcs1_15.py usr/lib/python2.7/dist- packages/Crypto/SelfTest/Signature/test_pkcs1_pss.py] failed to install/upgrade: subprocess installed post-installation script returned error exit status 101 Status in python-defaults package in Ubuntu: New Bug description: I think package has been corrupted? Not really sure.. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-crypto 2.6.1-4ubuntu0.2 [modified: usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/__init__.py usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/test_pkcs1_15.py usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/test_pkcs1_pss.py] ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Mon Jun 5 07:37:06 2017 DuplicateSignature: package:python-crypto:2.6.1-4ubuntu0.2 [modified: usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/__init__.py usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/test_pkcs1_15.py usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/test_pkcs1_pss.py]:subprocess installed post-installation script returned error exit status 101 ErrorMessage: subprocess installed post-installation script returned error exit status 101 InstallationDate: Installed on 2015-04-30 (766 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-crypto Title: package python-crypto 2.6.1-4ubuntu0.2 [modified: usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/__init__.py usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/test_pkcs1_15.py usr/lib/python2.7/dist-packages/Crypto/SelfTest/Signature/test_pkcs1_pss.py] failed to install/upgrade: subprocess installed post-installation script returned error exit status 101 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1695784/+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 1154241]
*** This bug is a duplicate of bug 346386 *** https://bugs.launchpad.net/bugs/346386 http://treat.javaload.com Old Coot -- 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/1154241 Title: update manager error Status in apt package in Ubuntu: New Bug description: hi i was updating ubuntu 12.04 and came across this error An unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise-updates_main_i18n_Translation-en, E:The package lists or status file could not be parsed or opened.' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1154241/+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 1767535] Re: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126
It seems you managed to break your python installation. pyclean is provided by python-minimal - you could try re-installing it. ** Changed in: python-crypto (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1767535 Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126 Status in python-crypto package in Ubuntu: Incomplete Bug description: I tried updating ubuntu and then i got this error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-crypto 2.6.1-4build1 ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21 Uname: Linux 3.19.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Apr 27 18:49:42 2018 DuplicateSignature: package:python-crypto:2.6.1-4build1:subprocess new pre-removal script returned error exit status 126 ErrorMessage: subprocess new pre-removal script returned error exit status 126 InstallationDate: Installed on 2016-05-15 (712 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.14 SourcePackage: python-crypto Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126 UpgradeStatus: Upgraded to trusty on 2018-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1767535/+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 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
FWIW, I've run into what I believe to be this bug with MAAS 2.4 and Bionic, minus the juju aspect -- I'm unable to deploy when nodes must rely on a proxy for PPA access. It works without PPAs or when I enable NAT so that the nodes can retrieve the GPG keys without using a proxy. ** Tags added: hwcert-server -- 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/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported Status in software-properties package in Ubuntu: Triaged Bug description: This is related to a Maas environment hosted behind a proxy. I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK ubuntu@zookeeper:/var/log$ echo $? 0 On the zookeeper node, python-software-properties is version 0.82.7.3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 12 14:40:21 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+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 1772449] [NEW] system freezing
Public bug reported: Occasionally the system is totally silent after logging in a user. The screen remains empty. The keyboard does not work. No cursor movement possible. By changing users a few times I have been able to force this situation. To escape from this, I have to turn off the computer. Attached the auth.log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 18:35:16 2018 InstallationDate: Installed on 2018-04-27 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1772449 Title: system freezing Status in shadow package in Ubuntu: New Bug description: Occasionally the system is totally silent after logging in a user. The screen remains empty. The keyboard does not work. No cursor movement possible. By changing users a few times I have been able to force this situation. To escape from this, I have to turn off the computer. Attached the auth.log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 18:35:16 2018 InstallationDate: Installed on 2018-04-27 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1772449/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs
** Description changed: + [Impact] + + * Cannot hibernate & resume from a swapfile + + [Test Case] + + * Create or enlarge swapfile to be big enough for hibernation + * Attempt to hibernate and resume + + [Regression Potential] + + * Hibernation is not reliable technology in itself, and multiple things + may cause failure to resume. Thus it is sufficient to validate this bug + after swapfile is attempted for hibernation and the disk offset kernel + parameter is modified. Irrespective if actual suspending or resume were + successful or not. + + [Other Info] + + * Original bug report + In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html -- 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/1760106 Title: FFe: Enable configuring resume offset via sysfs Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Confirmed Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Description changed: + [Impact] + + * More captive portals have been discovered that do not handle DNS requests with D0 set. + * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. + + [Test Case] + + * systemd-resolved something-nonexistant.ubuntu.com + * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. + * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches + + [Regression Potential] + + * Legitimate NXDOMAIN queries will now take longer, as they will be + retried multiple times with different features sets until an answer is + found. At that point the query will be cached and will return quickly. + This is needed to work-around bad captive portals that do not support + dns queries with D0. Post-captive portal, the feature level can usually + be cranked back up and it does after a grace period. + + [Other Info] + + * Original bug report + I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working.
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Please approve pulseaudio 11.1-1ubuntu7.1 in bionic-proposed. ** Description changed: - As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped - working properly. It was working fine in Jaunty. + SRU Request: + + [Impact] + When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. + + [Test Case] + 1) Enable the -proposed repository, and install the new pulseaudio + + 2) Restart your computer, connect it to a bluetooth device (e.g. a + headset or a speaker), play one or more videos either locally or online, + and see if you can still reproduce the problem. + + [Regression Potential] + Low, as the changes are upstream, and, if anything, it should also fix a memory leak. + + + As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: http
[Touch-packages] [Bug 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)
** Description changed: + [Impact] + + * XEN virtualization missidentified as hyperv + * This may cause units limited to a virtualisation not to be started; or redundant units for the other type of virtualisation to be started instead. + * Previously xen & hyper-v were detected correctly separately, even when xen emulates/suggests that it is hyper-v. + + [Test Case] + + * Execute systemd-detect-virt and check that it detects Xen & Hyperv + + [Regression Potential] + + * Things that "fake" xen might not work as the detection code branches + are changed, but it would affect previous releases and future releases + of systemd-detect-virt. So far such things are not known to exist, and + if such things appear in the future support for them would need to land + upstream first. + + [Other Info] + + * Original bug report + Cherrypick https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a It appears that Xen-based VMs sometimes report themselves as Microsoft Hyper-V via CPUID — apparently this is for compatibility with Windows guests. systemd 237 (as found in Bionic) gives preference to this CPUID information when detecting Xen, and thus it erroneously assumes that the guest is running under Hyper-V. This causes Xen-related services (and anything else that relies on systemd's VM-detection functionality) to fail. I *believe* this is a regression from systemd 229 as used in Xenial — we have at least a few Xen-based VMs that report as Hyper-V via CPUID and don't have this issue on that version — but i haven't confirmed that for certain. Anyway, i've submitted a ticket with more details to the up-stream project, and that has now been resolved through a fairly simple change which applies cleanly to the Bionic systemd sources: https://github.com/systemd/systemd/issues/8844 Would it be possible to pull this down? As mentioned, Xen-based Ubuntu VMs can seriously misbehave without it. Thanks! See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573 --- % lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 % apt-cache policy systemd systemd: Installed: 237-3ubuntu10 Candidate: 237-3ubuntu10 Version table: *** 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1768104 Title: systemd sometimes misdetects Xen VMs (fixed up-stream) Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * XEN virtualization missidentified as hyperv * This may cause units limited to a virtualisation not to be started; or redundant units for the other type of virtualisation to be started instead. * Previously xen & hyper-v were detected correctly separately, even when xen emulates/suggests that it is hyper-v. [Test Case] * Execute systemd-detect-virt and check that it detects Xen & Hyperv [Regression Potential] * Things that "fake" xen might not work as the detection code branches are changed, but it would affect previous releases and future releases of systemd-detect-virt. So far such things are not known to exist, and if such things appear in the future support for them would need to land upstream first. [Other Info] * Original bug report Cherrypick https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a It appears that Xen-based VMs sometimes report themselves as Microsoft Hyper-V via CPUID — apparently this is for compatibility with Windows guests. systemd 237 (as found in Bionic) gives preference to this CPUID information when detecting Xen, and thus it erroneously assumes that the guest is running under Hyper-V. This causes Xen-related services (and anything else that relies on systemd's VM-detection functionality) to fail. I *believe* this is a regression from systemd 229 as used in Xenial — we have at least a few Xen-based VMs that report as Hyper-V via CPUID and don't have this issue on that version — but i haven't confirmed that for certain. Anyway, i've submitted a ticket with more details to the up-stream project, and that has now been resolved through a fairly simple change which applies cleanly to the Bionic systemd sources: https://github.com/systemd/systemd/issues/8844 Would it be possible to pull this down? As mentioned, Xen-based Ubuntu VMs can seriously misbehave without it. Thanks! See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573 --- % lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 % apt-cache po
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Changed in: pulseaudio (Ubuntu Bionic) Status: Triaged => In Progress -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: In Progress Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1772383] Re: WD15 Dell Thunderbolt dock no audio
@Hui Wang No change - copying the file in the same dir adding .bak is sufficient right- or will this be read as a 2nd conf? + iirc this is the line i had to add with the workaround - is there a way to ensure that both the 90-pulseaudio.rules as well as the "dell- dock-tb16-usb-audio.conf" match the vanilla ones from upstream? @Daniel - Could have been the upgrade to bionic ... Something within the last month if not weeks -- 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/1772383 Title: WD15 Dell Thunderbolt dock no audio Status in pulseaudio package in Ubuntu: New Bug description: Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benste 2287 F pulseaudio /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1772383/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: Triaged => In Progress ** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: Triaged Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1772423] [NEW] [Inspiron 5379, Realtek ALC3253, Black Headphone Out, Right] No sound at all
Public bug reported: tested 2 headphones, different brands. neither had any sound coming out of them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: mark 1485 F...m pulseaudio /dev/snd/pcmC0D0p: mark 1485 F...m pulseaudio /dev/snd/controlC0: mark 1485 F pulseaudio mark 4153 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Mon May 21 10:26:52 2018 InstallationDate: Installed on 2018-05-18 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [Inspiron 5379, Realtek ALC3253, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2017:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1772423 Title: [Inspiron 5379, Realtek ALC3253, Black Headphone Out, Right] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: tested 2 headphones, different brands. neither had any sound coming out of them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: mark 1485 F...m pulseaudio /dev/snd/pcmC0D0p: mark 1485 F...m pulseaudio /dev/snd/controlC0: mark 1485 F pulseaudio mark 4153 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Mon May 21 10:26:52 2018 InstallationDate: Installed on 2018-05-18 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [Inspiron 5379, Realtek ALC3253, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2017:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1772423/+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 1766503] Re: ibus-* randomly use high CPU
I am experiencing the exact same issue as Stelios. I can run htop and everything goes back to normal. SPECS: Processor : 2x AMD Athlon(tm) Dual Core Processor 5050e Memory : 4046MB OS : Ubuntu 16.04.4 LTS -Display- Resolution : 2560x1024 pixels OpenGL Renderer : GeForce GT 630/PCIe/SSE2 X11 Vendor : The X.Org Foundation DBUS-X11 ver: 1.10.6-1ubuntu3.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1772405] Re: freeipa dns install does not correctly configure reverse zones due to systemd-resolved
Fedora doesn't enable systemd-resolved, which is probably why this hasn't been hit before. It was proposed but apparently shot down. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1772405 Title: freeipa dns install does not correctly configure reverse zones due to systemd-resolved Status in freeipa package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: In Ubuntu 18.04, ipa-dns-intall (or ipa-server-install when asking to configure BIND) does not create reverse DNS zones for my domain. Note that I already fixed (or more correctly, circumvented) other bugs involving BIND, such as https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1769440. The problem seems due to the presence of systemd-resolved. When ipa- dns-install valuates whether to create a reverse DNS zone, it tries to use the local DNS for resolving the IP address of the server. When you want to install BIND alongside IPA, this normally fails, and the installer knows he needs to configure an appropriate reverse zone. But when systemd-resolved is active, it takes the role of local DNS and answers this query: therefore, the installer thinks a reverse DNS zone is already present. To fix this problem I had to perform the following steps before calling ipa-dns-install (or ipa-server-install): 1) stop systemd-resolved with "systemctl stop systemd-resolved". 2) disable systemd-resolved with "systemctl disable systemd-resolved". 3) delete the file "/etc/resolv.conf", which is a symlink to a file created by systemd. 4) optionally, recreate "/etc/resolv.conf" pointing to the (real) local DNS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1772405/+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 1722185] Re: Crash installing packages using debconf
Since the proposed changes are quite big and seem a bit intrusive, I would appreciate a Regression Potential analysis as per our SRU guidelines. I would like to know where we could expect regressions after this change lands in the stable series. Also, even though this does seem to be like a frequently-seen crash for both bionic and artful, I wouldn't want to jam it into the stable series too hastily. I see the second PackageKit pull request has not yet been approved by upstream - could we get someone reviewing it and merging before we proceed? Normally I'd also wait for cosmic to migrate, but I actually see we're only blocked on the armhf tests not being run - so it seems to be fine so far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+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 1500813] Re: package python3-software-properties 0.92.37.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1500813 Title: package python3-software-properties 0.92.37.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in software-properties package in Ubuntu: Confirmed Bug description: .. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3-software-properties 0.92.37.5 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Tue Sep 29 12:39:07 2015 DuplicateSignature: package:python3-software-properties:0.92.37.5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-06-28 (457 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: software-properties Title: package python3-software-properties 0.92.37.5 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/software-properties/+bug/1500813/+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 1760283] Re: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You have a broken custom init script named "start_my_apps" that will need to be removed. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- 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/1760283 Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: unable to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Mar 31 15:45:14 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-17 (560 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.20 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.5 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/util-linux/+bug/1760283/+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 1745664] Re: systemd-logind crashed with SIGABRT in __libc_connect()
I am getting this crash report pretty consistently. A lot of my problems have been clumped under this bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238?comments=all as it was the first one I ran into. I am running an i7-7820X on a msi x299 sli plus motherboard with a nvidia gtx 1050 card. So far this occurs without much warning. Usually my system will lock up and reboot on its own. Then the following boot, I will be using various applications and the desktop will go away and I'll be returned to the login screen. Then the ubuntu bug report will report this crash and an xorg crash. Sometimes these crashes happen soon after first boot and sometimes after I've been using the computer most of the day. This morning I booted the computer, launched firefox and chrome and a couple minutes later computer rebooted and after logging in again gui crashed similar to my description above. I do have nis setup but my main login is a sort of mixed nis login. My user account was created on my local machine to match the uuid of my server account so I'm technically logging in locally. Not sure how much nis is activating. Is there a way to tell? Error reports: systemd: https://errors.ubuntu.com/oops/9a5971bc-5869-11e8-ac5b-fa163e30221b https://errors.ubuntu.com/oops/22fde306-594e-11e8-9113-fa163e171d9b https://errors.ubuntu.com/oops/d9d2bcf0-5ae3-11e8-b7bb-fa163ed44aae https://errors.ubuntu.com/oops/ca27a03c-5cf9-11e8-89fe-fa163e192766 xserver-xorg-core https://errors.ubuntu.com/oops/ace611be-5869-11e8-9c14-fa163ef911dc https://errors.ubuntu.com/oops/43232196-594e-11e8-bc40-fa163e839e11 https://errors.ubuntu.com/oops/df54164c-5ae3-11e8-bb2e-fa163e839e11 https://errors.ubuntu.com/oops/19aa1018-5cfa-11e8-9065-fa163e839e11 -- 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/1745664 Title: systemd-logind crashed with SIGABRT in __libc_connect() Status in systemd package in Ubuntu: Confirmed Bug description: configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/
[Touch-packages] [Bug 1772410] [NEW] cannot load bionic beaver
Public bug reported: A) Bionic beaver stops at UID 129, just after the previous style cursor loads. Only way i can load it is via advanced/recovery/resume (I have tried all options-nothing works) Warns me that graphics may need to be altered but I cannot change graphics settings anyway! Display lags: 'you tube' impossible to watch. We also need: 1) The release of Ubuntu you are using, Ubuntu 18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center: Terminla gives N: Unable to locate package pkgname 3) What you expected to happen; Ubuntu to load 4) What happened instead see A) I have burned a lot of daylight trying to fix this/look for a solution so any ideas would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Mon May 21 14:34:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller [1028:0182] Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller [1028:0182] InstallationDate: Installed on 2012-12-15 (1983 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=36223365-2aeb-4e9c-bc13-0435c9ff6eb4 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0XD762 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0XD762:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772410 Title: cannot load bionic beaver Status in xorg package in Ubuntu: New Bug description: A) Bionic beaver stops at UID 129, just after the previous style cursor loads. Only way i can load it is via advanced/recovery/resume (I have tried all options-nothing works) Warns me that graphics may need to be altered but I cannot change graphics settings anyway! Display lags: 'you tube' impossible to watch. We also need: 1) The release of Ubuntu you are using, Ubuntu 18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center: Terminla gives N: Unable to locate package pkgname 3) What you expected to happen; Ubuntu to load 4) What happened instead see A) I have burned a lot of daylight trying to fix this/look for a solution so any ideas would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Mon May 21 14:34:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 0
[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Sorry, small adjustment. I use wayland as default since 17.10 with gdm (works well in general for me): loginctl show-session c1 -p Type Type=wayland -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard language does not work either most of the time (Super + Space). Those I use the most. Extremely annoying after some time, especially when using dual screens (since the Gnome top bar is only on one monitor which is even more annoying: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1682542). Worked fine in Ubuntu 17.10 with Gnome and previous versions with Unity. -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1772383] Re: WD15 Dell Thunderbolt dock no audio
And Please do a test:
backup the file /lib/udev/rules.d/90-pulseaudio.rules, then edit
90-pulseaudio.rules, find the line "ATTRS{idVendor}=="0bda",
ATTRS{idProduct}=="4014", ENV{PULSE_PROFILE_SET}="dell-dock-tb16-usb-
audio.conf"", and comment it by adding a # ahead the line, reboot and
redo the test.
--
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/1772383
Title:
WD15 Dell Thunderbolt dock no audio
Status in pulseaudio package in Ubuntu:
New
Bug description:
Followup from bug 1718824 and bug 1745765 respectively as reported in the
other bugs neither front (headphones) nor back (line-out) jack is working after
the updates.
A Workaround manually adding the profile for pulseaudio might have been
persistet from changes before the upgrade / updates.
pactl is listed in the other bug, alsa-info should be automatically
attached.
Output of pactl info:
"benste@benste-xps13-ubuntu:~$ pactl info
Server String: unix:/run/user/1000/pulse/native
Library Protocol Version: 32
Server Protocol Version: 32
Is Local: yes
Client Index: 21
Tile Size: 65472
User Name: benste
Host Name: benste-xps13-ubuntu
Server Name: pulseaudio
Server Version: 11.1
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink:
alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone
Default Source:
alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic
Cookie: bb32:a8fe"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: benste 2287 F pulseaudio
/dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon May 21 11:06:17 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-13 (584 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago)
dmi.bios.date: 10/03/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.1
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1772383/+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 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage
Both seed proposals merged. I believe nothing else needs doing, and tomorrow's dailies should be fixed then. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live 18.04 with broken seed causes snapd high CPU usage Status in OEM Priority Project: Confirmed Status in snapd package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+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 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.bionic ** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live 18.04 with broken seed causes snapd high CPU usage Status in OEM Priority Project: Confirmed Status in snapd package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+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 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage
** Branch linked: lp:~swem/ubuntu-seeds/ubuntu.cosmic ** Branch linked: lp:~swem/ubuntu-seeds/ubuntu.bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live 18.04 with broken seed causes snapd high CPU usage Status in OEM Priority Project: Confirmed Status in snapd package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+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 1766542] Re: Installation blocks when the machine is behind a proxy server
Hi @Steve, IMO, it would be great that the period is less than 30 seconds in total. In this case, the updating operation is always failed. Users should know that the Internet is not available before setting a proxy server. They may expect to have a minimum timeout or pre-configure the proxy server before installation. -- 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/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: New Status in ubiquity package in Ubuntu: Incomplete Status in apt source package in Bionic: New Status in ubiquity source package in Bionic: New Bug description: When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1772383] Re: WD15 Dell Thunderbolt dock no audio
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1772383 Title: WD15 Dell Thunderbolt dock no audio Status in pulseaudio package in Ubuntu: New Bug description: Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benste 2287 F pulseaudio /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1772383/+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 1772386] [NEW] message - Low Graphics mode - about 2/3 of startups - not all
Public bug reported: After a recent update (kernel?), I have begun to occasionally receive the message "Running in Low Graphics Mode" at boot (maybe half the time). I can tell it to use Default setting from the options it offers, and get by it, after which things look and work normally until a reboot, which may or may not occur correctly. I also usually get "System error detected, Report? at the same time, so I agree to report it. Please note that I'm using 16.04 (fully updated), Gnome Flashback Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] . This problem shows up no matter which of the above I'm using, or Unity. roger@roger-desktop:~$ uname -a Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux roger@roger-desktop:~$ free -m total used free shared buff/cache available Mem: 16013 3880 10410 363 1722 11443 Swap: 16348 0 16348 roger@roger-desktop:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 7.8G 0 7.8G 0% /dev tmpfs 1.6G 9.6M 1.6G 1% /run /dev/sda1 902G 77G 779G 9% / tmpfs 7.9G 127M 7.7G 2% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 1.6G 52K 1.6G 1% /run/user/1000 I have found a WORK-AROUND. Using x-diagnose, I selected all options under both Debug and Workarounds. After this, all works normally every time. However, I take this as a crutch, not a fix, and think other action should be taken Selecting "View Errors" shows no errors, so I never tried reporting from that point. This gives me a presumption that there is a bug in coding that interacts badly with my system and a few others like it, which I encountered in my search for a solution. Also, if I simply go to 18.04 (I don't really want to just yet.) will it likely fix this or might this block or damage the upgrade? 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu roger@roger-desktop:~$ lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center roger@roger-desktop:~$ apt-cache policy pkgname N: Unable to locate package pkgname ALSO - I'm unable to locate this information in Software Center 3) What you expected to happen Normal boot, no errors or problems 4) What happened instead "Running in Low Graphics Mode" displayed, along with subsequent "System Error Detected" messages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Mon May 21 01:56:23 2018 DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1002:683f] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [174b:e213] InstallationDate: Installed on 2014-07-07 (1413 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904 dmi.board.name: DZ77BH-55K dmi.board.vendor: Intel Corporation dmi.board.version: AAG39008-400 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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: Mon May 21 01:25:13 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.ver
[Touch-packages] [Bug 1772370] Re: every time I install nvidia driver in my ubuntu14.04, it's goes wrong,
nvidia-390 is not available in 14.04, so you're using unofficial packages, that's not supported ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1772370 Title: every time I install nvidia driver in my ubuntu14.04, it's goes wrong, Status in xorg package in Ubuntu: Invalid Bug description: if I install nvidia by ```sudo sh nvidia*.run```, it failed; if I install nvidia by ```sudo apt-get install nvidia-390```, it occured that login loop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-125.150~14.04.1-generic 4.4.128 Uname: Linux 4.4.0-125-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.28 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: Mon May 21 15:52:45 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8599] InstallationDate: Installed on 2017-08-29 (264 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: ASUSTeK COMPUTER INC. ESC500 G4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-125-generic.efi.signed root=UUID=c549c509-b5dd-44f3-9593-ace3d7d4bb6e ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: P10S WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/13/2017:svnASUSTeKCOMPUTERINC.:pnESC500G4:pvrRev1.XX:rvnASUSTeKCOMPUTERINC.:rnP10SWS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: ESC500 G4 dmi.product.version: Rev 1.XX dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 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: Mon May 21 15:52:06 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772370/+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 1772383] Re: WD15 Dell Thunderbolt dock no audio after updates/upgrade
There haven't been any updates to pulseaudio in bionic. So do you mean it regressed a while ago in an artful update? Do you know the last version in which it was working? ** Description changed: - Followup from #1718824 and #1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. + Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: benste 2287 F pulseaudio - /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: benste 2287 F pulseaudio + /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Summary changed: - WD15 Dell Thunderbolt dock no audio after updates/upgrade + WD15 Dell Thunderbolt dock no audio -- 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/1772383 Title: WD15 Dell Thunderbolt dock no audio Status in pulseaudio package in Ubuntu: New Bug description: Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benste 2287 F pulseaudio /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T
[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock
Hi there, i've created another new bug - https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1772383 and subscribed you to it. looking forward to any ideas. -- 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/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Artful: Fix Released Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1772383] [NEW] WD15 Dell Thunderbolt dock no audio
Public bug reported: Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benste 2287 F pulseaudio /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** 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/1772383 Title: WD15 Dell Thunderbolt dock no audio Status in pulseaudio package in Ubuntu: New Bug description: Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates. A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates. pactl is listed in the other bug, alsa-info should be automatically attached. Output of pactl info: "benste@benste-xps13-ubuntu:~$ pactl info Server String: unix:/run/user/1000/pulse/native Library Protocol Version: 32 Server Protocol Version: 32 Is Local: yes Client Index: 21 Tile Size: 65472 User Name: benste Host Name: benste-xps13-ubuntu Server Name: pulseaudio Server Version: 11.1 Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Generic_USB_Audio_200901010001-00.analog-stereo-headphone Default Source: alsa_input.usb-Generic_USB_Audio_200901010001-00.analog-stereo-mic Cookie: bb32:a8fe" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benste 2287 F pulseaudio /dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 21 11:06:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-13 (584 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago) dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1772383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Touch-packages] [Bug 1772370] [NEW] every time I install nvidia driver in my ubuntu14.04, it's goes wrong,
Public bug reported: if I install nvidia by ```sudo sh nvidia*.run```, it failed; if I install nvidia by ```sudo apt-get install nvidia-390```, it occured that login loop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-125.150~14.04.1-generic 4.4.128 Uname: Linux 4.4.0-125-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.28 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: Mon May 21 15:52:45 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8599] InstallationDate: Installed on 2017-08-29 (264 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: ASUSTeK COMPUTER INC. ESC500 G4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-125-generic.efi.signed root=UUID=c549c509-b5dd-44f3-9593-ace3d7d4bb6e ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: P10S WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/13/2017:svnASUSTeKCOMPUTERINC.:pnESC500G4:pvrRev1.XX:rvnASUSTeKCOMPUTERINC.:rnP10SWS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: ESC500 G4 dmi.product.version: Rev 1.XX dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 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: Mon May 21 15:52:06 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772370 Title: every time I install nvidia driver in my ubuntu14.04, it's goes wrong, Status in xorg package in Ubuntu: New Bug description: if I install nvidia by ```sudo sh nvidia*.run```, it failed; if I install nvidia by ```sudo apt-get install nvidia-390```, it occured that login loop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-125.150~14.04.1-generic 4.4.128 Uname: Linux 4.4.0-125-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.28 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: Mon May 21 15:52:45 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8599] InstallationDate: Installed on 2017-08-29 (264 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: ASUSTeK COMPUTER INC. ESC500 G4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-125-generic.efi.signed root=UUID=c549c509-b5dd-44f3-9593-ace3d7d4bb6e ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: P10S WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3
[Touch-packages] [Bug 1721626] Re: Remove obsolete versioned dependency on initramfs-tools Edit
What's the situation with console-setup right now? Should this upload be left in -proposed? It's been already around very long in the verification-failed state. Is this issue here still valid? I remember seeing the plymouth --ping issue addressed and released. Could anyone have a second look at this very old upload? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1721626 Title: Remove obsolete versioned dependency on initramfs-tools Edit Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Bug description: [SRU Justification] Up until artful, console-setup declares a versioned dependency on initramfs-tools. This was an Ubuntu-specific dependency only needed for upgrades, and the version referenced is ancient (ca. 2008). In artful and later, the dependency has now been removed. Since this is no longer relevant for upgrades and we would not otherwise have a dependency on initramfs-tools, we should drop this dependency to support building of images with initramfs-tools removed for systems that we know don't require an initramfs. [Test case] 1. On a xenial default cloud image install, try to run 'sudo apt purge initramfs-tools'. 2. Verify that this tries to remove console-setup, console-setup-linux, and kbd. 3. Cancel the removal. 4. Install console-setup from xenial-proposed. 5. Run 'sudo apt purge initramfs-tools' again. 6. Verify that console-setup, console-setup-linux, and kbd are not removed. 7. Run 'sudo apt install --reinstall console-setup' and confirm that the package can be installed successfully without initramfs-tools installed. [Regression Potential] If a user needs an initramfs in order to mount their root device, and console-setup is the only package on their system which depends on initramfs-tools, it is possible that the user may remove initramfs-tools and render their system unbootable. This is unlikely because initramfs-tools is still part of the 'minimal' seed and is therefore a dependency of ubuntu-minimal; and it remains a dependency of the generic kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721626/+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 1771345] Re: lscpu possible crash in min/max frequency
There are some autopkgtest regressions associated with the bionic, artful and xenial uploads. Could you check if those are real related regressions or not? -- 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/1771345 Title: lscpu possible crash in min/max frequency Status in util-linux package in Ubuntu: Fix Committed Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Committed Status in util-linux source package in Bionic: Fix Committed Bug description: [Impact] lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU frequency arrays and can call atof() on them, leading to crashes. It seems that's what caused the verification to fail for bug 1732865. The following fixes have been committed upstream: from 2.30: https://github.com/karelzak/util- linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd from 2.32: https://github.com/karelzak/util- linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2 I plan to backport them to xenial (both patches); and artful, bionic (second patch, they are > 2.30). [Regression potential] The worst possible regression is that lscpu would fail to correctly report min/max frequencies, but it seems unlikely, as we're only adding checks against null pointers / move an atof into a loop. [Test case] Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it does not crash (this removes min mhz file for cpu #0 for testing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1771345/+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
