[Touch-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
Sounding more and more like a kernel bug. Especially since comment #13 mentions that it occurs in 5.5 (but not 5.4!?). ** 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853374/+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 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
** Changed in: gtk Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in GTK+: Fix Released Status in apport package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
** No longer affects: apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in GTK+: Fix Released Status in apport package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
I guess you've turned off integrated titlebars, which is why I see different behaviour and no bug in Wayland sessions. ** Package changed: firefox (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+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 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
Oh come to think of it, there is a commonality between Firefox, VLC and Chrome. That is they all try to follow the system theme but all three are NOT GTK apps. They each use different toolkits. So I fear this is the same basic problem that will need to be fixed in three different toolkits. ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => firefox (Ubuntu) ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Also affects: vlc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+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 1872844] [NEW] Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
You have been subscribed to a public bug: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: focal -- Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) https://bugs.launchpad.net/bugs/1872844 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1863164] Re: ImportError: could not import gobject (error was: ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so: undefined symbol: PyExc_NotImple
[Expired for pygobject (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pygobject (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1863164
Title:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64
-linux-gnu.so: undefined symbol: PyExc_NotImplementedError'))
Status in pygobject package in Ubuntu:
Expired
Status in python3.8 package in Ubuntu:
Invalid
Bug description:
Steps to reproduce:
1. Install Ubuntu 20.04 LTS
2. Start first terminal with `tail -f ~/.xsession-errors`
3. Start second terminal and run `caja -q` from here
Expected results:
* there are no error messages or warnings in 1st terminl
Actual results:
* there are several error messages and warnings:
(caja:14755): Gtk-WARNING **: 22:55:26.070: Failed to register client:
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
client
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in
import apt_pkg
ImportError:
/usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_ValueError
Original exception was:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-apt 1.9.5
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 13 22:52:33 2020
InstallationDate: Installed on 2020-02-11 (1 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64
(20200211)
SourcePackage: python-apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1863164/+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 1873614] [NEW] Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Public bug reported:
Package lvm2 contains a init-premount script named /usr/share/initramfs-
tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does not
exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is the
case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1" argument
or strip the directory from "$0".
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873614/+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 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Forgot to mention, in the current bugged state the following message is
shown during boot:
ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such
file or directory
Presumedly the fail hook will not be invoked either.
** Description changed:
Package lvm2 contains a init-premount script named /usr/share/initramfs-
tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
- mkdir -p /tmp/mountroot-fail-hooks.d
- ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
+ mkdir -p /tmp/mountroot-fail-hooks.d
+ ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does not
exist.
-
- It is clear from lvm2's invocation that it expects the symlink to be named
"20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is the case:
+ It is clear from lvm2's invocation that it expects the symlink to be
+ named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is the
+ case:
add_mountroot_fail_hook()
{
- mkdir -p /tmp/mountroot-fail-hooks.d
- ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
+ mkdir -p /tmp/mountroot-fail-hooks.d
+ ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
-
-
- A simple fix might be to alter focal's version so it supports both
- invocation styles , e.g.
-
- ln -s "$0" /tmp/mountroot-fail-hooks.d/"${1:-$0}"
+ focal's version needs to be updated to either support the "$1" argument
+ or strip the directory from "$0".
--
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/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873614/+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 1853374] Re: pulseaudio disables GP107GL output every so often
** Also affects: pulseaudio (Debian) Importance: Undecided Status: New -- 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/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1853374] Re: pulseaudio disables GP107GL output every so often
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1853374] Re: pulseaudio disables GP107GL output every so often
i've just begun seeing this in debian 5.5.0-2 (linux 5.5.17-1) and 5.5.0-1 (5.5.13-1) pulseaudio -k fixes it for a while, and all i see that's relevant in the logs/dmesg is snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 0 booting back into 5.4.0-4 (5.4.19-1) and i have no problem. -- 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/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
This has been happening perhaps 3 times every 7 days, no obvious cause I can see. The system is a virtual machine that's just a router. No user activity, nobody logged in to the mate gui. Wish I had more to offer by way of a clue but that's it. -- 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/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+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 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
crash log ** Attachment added: "_usr_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+attachment/5356610/+files/_usr_lib_systemd_systemd.0.crash -- 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/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+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 1873607] [NEW] systemd segv coredump, reboot/poweroff ignored.
Public bug reported: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2
[Touch-packages] [Bug 1863874] Re: Backport GetFB2 ioctl, re-enable CCS compression for intel
This bug was fixed in the package mesa - 20.0.4-2ubuntu1 --- mesa (20.0.4-2ubuntu1) focal; urgency=medium * Merge from Debian. * disable-intel-ccs-compression.diff: Dropped, we use iris by default. (LP: #1863874) * Don't build with llvm-10 until ppc64el ftbfs is fixed. mesa (20.0.4-2) unstable; urgency=medium * fix-build-with-llvm-10.diff: Add a patch to fix build with Polly, and build with llvm-10 again. (Closes: #956004) * iris-drop-cache-coherent-cpu-mapping.diff: Fix corruption with iris (Closes: #954311) (LP: #1864274) * gallium-fix-bob-compute-shaders.diff: Fix vaapi with bob deinterlacing. (LP: #1867188) -- Timo Aaltonen Thu, 16 Apr 2020 09:22:34 +0300 ** Changed in: mesa (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1863874 Title: Backport GetFB2 ioctl, re-enable CCS compression for intel Status in XServer: New Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Status in libdrm source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in mesa source package in Focal: Fix Released Status in xorg-server source package in Focal: Won't Fix Bug description: We need this in order to re-enable intel CCS compression, which was originally disabled in mesa to fix this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776 GetFB2 was recently added to drm-misc, and should get upstream in 5.7, but would be best to have it in focal and unstable kernel so that the userland parts can be added. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver/+bug/1863874/+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 1864274] Re: [iris regression] gfx corruption
This bug was fixed in the package mesa - 20.0.4-2ubuntu1
---
mesa (20.0.4-2ubuntu1) focal; urgency=medium
* Merge from Debian.
* disable-intel-ccs-compression.diff: Dropped, we use iris by default.
(LP: #1863874)
* Don't build with llvm-10 until ppc64el ftbfs is fixed.
mesa (20.0.4-2) unstable; urgency=medium
* fix-build-with-llvm-10.diff: Add a patch to fix build with Polly,
and build with llvm-10 again. (Closes: #956004)
* iris-drop-cache-coherent-cpu-mapping.diff: Fix corruption with iris
(Closes: #954311) (LP: #1864274)
* gallium-fix-bob-compute-shaders.diff: Fix vaapi with bob
deinterlacing. (LP: #1867188)
-- Timo Aaltonen Thu, 16 Apr 2020 09:22:34 +0300
** Changed in: mesa (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1864274
Title:
[iris regression] gfx corruption
Status in Mesa:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor:
[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
This bug was fixed in the package mesa - 20.0.4-2ubuntu1 --- mesa (20.0.4-2ubuntu1) focal; urgency=medium * Merge from Debian. * disable-intel-ccs-compression.diff: Dropped, we use iris by default. (LP: #1863874) * Don't build with llvm-10 until ppc64el ftbfs is fixed. mesa (20.0.4-2) unstable; urgency=medium * fix-build-with-llvm-10.diff: Add a patch to fix build with Polly, and build with llvm-10 again. (Closes: #956004) * iris-drop-cache-coherent-cpu-mapping.diff: Fix corruption with iris (Closes: #954311) (LP: #1864274) * gallium-fix-bob-compute-shaders.diff: Fix vaapi with bob deinterlacing. (LP: #1867188) -- Timo Aaltonen Thu, 16 Apr 2020 09:22:34 +0300 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: Fix Released Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
This bug was fixed in the package atk1.0 - 2.35.1-1ubuntu2 --- atk1.0 (2.35.1-1ubuntu2) focal; urgency=medium * control, gbp.conf: Update for ubuntu/master branch * Revert "atksocket: make get_extents return parent extents by default" This reverts upstream commit 4b5ed8630c5ae9ef37884c4199da8463b7e5a127. This commit causes an infinite loop and a crash in the Ubuntu installer. (LP: #1870508) -- Iain Lane Fri, 17 Apr 2020 15:29:42 +0100 ** Changed in: atk1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to atk1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1870508 Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a() Status in atk1.0 package in Ubuntu: Fix Released Bug description: == Test Case == 1. Boot to ubiquity-dm 2. Enable the screenreader (Alt+Super+S) 3. Select "Install Ubuntu" 4. Proceed with all the steps of the installer = Actual Result = During installation, when the slideshow is running, this crash occurs. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 10:55:58 2020 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity ExecutableTimestamp: 1585729537 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only ProcCwd: / ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SegvAnalysis: Segfault happened at: 0x7fbd15f8f16a : mov%rax,-0x20(%rsp) PC (0x7fbd15f8f16a) ok source "%rax" ok destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: ubiquity StacktraceTop: g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0 atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0 Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1870508/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
This bug was fixed in the package evolution-data-server - 3.36.1-2 --- evolution-data-server (3.36.1-2) unstable; urgency=medium * debian/patches/git_stable_bugfixes.patch: - backport upstream fixes for webdav and goa calendar issues (lp: #1871019) -- Sebastien Bacher Wed, 15 Apr 2020 09:38:29 +0200 ** Changed in: evolution-data-server (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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in evolution-data-server package in Ubuntu: Fix Released Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3 --- pulseaudio (1:13.99.1-1ubuntu3) focal; urgency=medium * debian/patches/git_cherrypick_fixes.patch: - cherry pick pending commits from git, we are on a rc version but it looks like the stable isn't going to be rolled before focal is out so let's include the pending fixes in our package. - fixes for sound not working on Bay and Cherry trail (lp: #1872970) - remove git_ucm_assert.patch which was an individual cherrypick -- Sebastien Bacher Thu, 16 Apr 2020 10:07:10 +0200 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1872970 Title: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio package in Fedora: Unknown Bug description: I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 sound card. downgrade pulseaudio_13.0-1ubuntu1.1 sound work. https://bugzilla.redhat.com/show_bug.cgi?id=1818883 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/ please build next pulseaudio include patch, ucm: fix the port / ucm device activation on boot alsa sink/source: fix the mixer initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872970/+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 1873578] Re: Autorotation works but is backwards
** Package changed: ubuntu => xorg (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/1873578 Title: Autorotation works but is backwards Status in xorg package in Ubuntu: New Bug description: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873578/+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 737615] Re: Can't save changes in "Edit Connections..." for Wi-Fi networks to which one doesn't have the password
** This bug is no longer a duplicate of bug 1409866 Will not find network after connection info is edited -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/737615 Title: Can't save changes in "Edit Connections..." for Wi-Fi networks to which one doesn't have the password Status in Linux: Unknown Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: New Bug description: Binary package hint: network-manager Steps to reproduce: 1) Right-click on Network Manager's tray icon 2) select "edit connections" 3) go to the "wireless" tab 4) select any connection in the list, except the one you are currently connected to 5) Click "Edit" 5) Change some settings Expected: there should be some way to save those changes Observed: the "Apply" button is greyed out. There is no "Save" button. If you hit Cancel, obviously the changes are discarded. If you edit the network you are connected to, the Apply button works, but why on earth are'n you allowed to save changes to a network you are not connected to? And if there was a reason why you can't, then why are you allowed to edit in the first place? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: network-manager 0.8-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13 Uname: Linux 2.6.32-29-generic i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Mar 18 14:47:06 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) IpRoute: 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.105 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.2.1 dev wlan0 proto static Keyfiles: Error: [Errno 2] No such file or directory ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/737615/+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 1873086] Re: sound stutters when playing on a bluetooth receiver
@Daniel Thank you, will see where I get with sudo modprobe ath10k_core btcoex_enable=1 bt_ant_diversity=1 as seems to have been suggested under the related bug. Will try 5GHz and disabling WiFi, but the latter can obviously only be a temporary diagnostics step. -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1873578] [NEW] Autorotation works but is backwards
You have been subscribed to a public bug: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Autorotation works but is backwards https://bugs.launchpad.net/bugs/1873578 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1873086] Re: sound stutters when playing on a bluetooth receiver
** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356583/+files/lsusb.txt -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1873086] Re: sound stutters when playing on a bluetooth receiver
Adding lsusb output. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356582/+files/lspci.txt -- 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/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+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 1873591] [NEW] initramfs-tools-core multiarch dns problem
Public bug reported: Hi, in x86_64 multiarch environment the hook-functions -> add_dns() copy i386 libdns instead of 64bit one. in add_dns() i replace for f in "$d"/libc.so.?; do [ -f "$f" ] && break; done with for f in "$d"/libc.so; do [ -f "$f" ] && break; done to fix the problem regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools-core 0.136ubuntu6 [modified: usr/share/initramfs-tools/hook-functions] ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:10:51 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873591 Title: initramfs-tools-core multiarch dns problem Status in initramfs-tools package in Ubuntu: New Bug description: Hi, in x86_64 multiarch environment the hook-functions -> add_dns() copy i386 libdns instead of 64bit one. in add_dns() i replace for f in "$d"/libc.so.?; do [ -f "$f" ] && break; done with for f in "$d"/libc.so; do [ -f "$f" ] && break; done to fix the problem regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools-core 0.136ubuntu6 [modified: usr/share/initramfs-tools/hook-functions] ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:10:51 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873591/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Couldn't the nvidia packages all be modified to prune 'splash' from /boot/grub/grub.cfg prior to rebuilding its kernel modules and thus regenerating the initrd.img files? -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
Possibly related? https://bugzilla.kernel.org/show_bug.cgi?id=204343 ** Bug watch added: Linux Kernel Bug Tracker #204343 https://bugzilla.kernel.org/show_bug.cgi?id=204343 -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This bug is definitely triggered by the built kernel image loading the nvidia drivers. The autologin failures and associated hangs on restarts can be suppressed as follows... 1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT 2) Regenerate /boot/grub/grub.cfg with 'sudo update-grub' 3) Regenerate the initrd.img files by using 'sudo apt-get --reinstall install' to reinstall the currently installed kernel packages. After rebooting, the autologin feature in gdm3 can be reselected and on the next reboot, it will autologin as expected. No loading the nvidia module through initrd.img also eliminates the hangs on restarting while autologin is enabled. I suspect the folks who thought removing splash from grub.cfg didn't work had failed to rebuild the initrd.img files after regenerating grub.cfg. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Touch-packages] [Bug 1872153] Re: SIGSEGV in g_source_set_ready_time()
This bug was fixed in the package glib2.0 - 2.64.2-1~fakesync1 --- glib2.0 (2.64.2-1~fakesync1) focal; urgency=medium [ Simon McVittie ] * Add Breaks on older versions of gimp, which used a syntactically invalid property name in a plugin, and would crash when GObject rejects syntactically invalid property names [ Sebastien Bacher ] * New upstream release * debian/patches/git_gsource_segfault.patch: - backport an upstream git change to fix a signal handler disconnect segfault situation (lp: #1872153) -- Sebastien Bacher Wed, 15 Apr 2020 23:01:50 +0200 ** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872153 Title: SIGSEGV in g_source_set_ready_time() Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: cuando abro software ubuntu ma aparece tramsparente sin fondo iconos solos ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 19:48:54 2020 ExecutablePath: /usr/libexec/gsd-usb-protection InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/gsd-usb-protection ProcEnviron: LANG=es_AR.UTF-8 LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7faa5f4a2bf3 : cmp 0x10(%rax),%rbp PC (0x7faa5f4a2bf3) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872153/+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 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
Ingrid, the log you attached does not include any information about the libpam-modules package. It's possible you have the same bug, but this log does not help us debug it. Can you double check that the log file you attached was /var/log/dist- upgrade/apt-term.log? The log you attached does not look like a release upgrade log, but rather a regular apt term log. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871960 Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam- modules:amd64 Status in pam package in Ubuntu: Incomplete Bug description: I was updating ubuntu to the 20.04 version. Not all packages were updated. I receive new errors every few seconds. what should I do? Thanks safi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Fri Apr 10 00:36:08 2020 ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64 InstallationDate: Installed on 2019-12-28 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: pam Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64 UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871960/+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 1873574] [NEW] Cannot enable repository source
Public bug reported: Context: I upgraded from 18.04 to 20.04 and wanted to enable again some repository sources that were disabled for the upgrade. Steps to reproduce: * Open software-properties-gtk * Go to the "Other software" tab * Click on any checkbox in front of each source address Expected result: * A popup appears prompting me to enter my password * The list does not scroll and the checkbox is checked Actual result: * The list scrolls up to the top * The checkbox is not checked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 18:03:43 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-04 (13 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Context: I upgraded from 18.04 to 20.04 and wanted to enable again some repository sources that were disabled for the upgrade. - Step to reproduce: + Steps to reproduce: * Open software-properties-gtk * Go to the "Other software" tab * Click on any checkbox in front of each source address Expected result: * A popup appears prompting me to enter my password * The list does not scroll and the checkbox is checked Actual result: * The list scrolls up to the top * The checkbox is not checked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 18:03:43 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-04 (13 days ago) -- 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/1873574 Title: Cannot enable repository source Status in software-properties package in Ubuntu: New Bug description: Context: I upgraded from 18.04 to 20.04 and wanted to enable again some repository sources that were disabled for the upgrade. Steps to reproduce: * Open software-properties-gtk * Go to the "Other software" tab * Click on any checkbox in front of each source address Expected result: * A popup appears prompting me to enter my password * The list does not scroll and the checkbox is checked Actual result: * The list scrolls up to the top * The checkbox is not checked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 18:03:43 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-04 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1873574/+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 1873562] [NEW] package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before instal
Public bug reported: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1873562 Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux- gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error Status in mesa package in Ubuntu: New Bug description: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output
[Touch-packages] [Bug 1860547] Re: cupsd high memory consumption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1860547 Title: cupsd high memory consumption Status in cups package in Ubuntu: Confirmed Bug description: Ubuntu version: 19.10 cups version: 2.2.12-2ubuntu1 cupsd process slowly increases memory consumption. The /var/log/cups/error_log is full of errors below: E [22/Jan/2020:11:06:17 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:19 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:20 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:21 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:22 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:24 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:25 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:26 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:28 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:29 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:30 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:32 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:33 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1860547/+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 1872551] Re: software-properties-qt: nvidia driver version switch fails
A fix for this has been uploaded. It is currently stuck in proposed pocket due to an unrelated test failure of a reverse dependency, but I anticipate that being sorted before 20.04 release. -- 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/1872551 Title: software-properties-qt: nvidia driver version switch fails Status in software-properties package in Ubuntu: Fix Committed Bug description: Switching the Nvidia driver version with kubuntu-driver-manager doesn't work anymore: Selecting a different driver version (nvidia- driver-440 instead of the currently selected / installed -390) and clicking "Apply Changes" has no effect and produces this error message in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 895, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined Steps to reproduce: - sudo kubuntu-driver-manager - Under "Additional Drivers", select a different Nvidia driver version (in my case: 440 instead of 390) - Click "Apply Changes" - (observe error message in the terminal) Expected result: - No error message - Nvidia driver version 440 gets installed Actual result: - Error message - No change in the installed Nvidia driver version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-driver-manager (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 23:41:56 2020 InstallationDate: Installed on 2016-11-26 (1234 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: kubuntu-driver-manager UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1870788] Re: Sound randomly stops working for individual programs
Update I have found a work around so that I don't have to restart my computer as often but the bug is still live and kicking. I use "indicator-sound-switcher" https://github.com/yktoo/indicator-sound-switcher When the sound breaks I can use the indicator in the top bar to select "Starship/Matisse HD Audio Controller -line out". If I select this twice then the sound comes back. In Youtube if I pause, skip or watch a new video the sound cuts out and I have to select the option again two times for it to come back. This bug does however make Skype completely unusable. -- 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/1870788 Title: Sound randomly stops working for individual programs Status in alsa-driver package in Ubuntu: New Bug description: The sound for an individual program will randomly stop working. For example I am listening to music on youtube using firefox right now but VLC will not play sound. Randomly firefox will stop playing sound but other programs will work. The only way to fix it is to restart my computer every 45 minutes to 1.5 hours. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cortana3089 F pulseaudio /dev/snd/pcmC1D0p: cortana3089 F...m pulseaudio /dev/snd/controlC0: cortana3089 F pulseaudio /dev/snd/timer: cortana3089 f pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:59:21 2020 InstallationDate: Installed on 2018-11-10 (511 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Apr 04 13:46:12 Cortana-U dbus-daemon[1845]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.35' (uid=121 pid=2196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 04 13:46:13 Cortana-U dbus-daemon[1845]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.40' (uid=121 pid=2196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 04 13:46:25 Cortana-U systemd[2165]: pulseaudio.service: Succeeded. Apr 04 13:46:35 Cortana-U systemd[2165]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] fails after a while UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago) dmi.bios.date: 09/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5220 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5220:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870788/+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 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
Hi Steve, I am new to Ubuntu and just updated from 18.04 (there I had wifi connection issues). I encountered the same bug when I updated via update-manager. But I am very happy that the wifi connection is working well now. I am attaching the .log file and I hope this bug can be patched because I would really like to keep using Focal Fossa. Thank you for taking care of this! Let me know if I can help in any other way ** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871960/+attachment/5356422/+files/term.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871960 Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam- modules:amd64 Status in pam package in Ubuntu: Incomplete Bug description: I was updating ubuntu to the 20.04 version. Not all packages were updated. I receive new errors every few seconds. what should I do? Thanks safi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Fri Apr 10 00:36:08 2020 ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64 InstallationDate: Installed on 2019-12-28 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: pam Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64 UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871960/+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 1869673] Re: Updating initramfs - possible missing amdgpu firmware
** This bug is no longer a duplicate of bug 1850654 update-initramfs complains of missing amdgpu firmware files -- 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/1869673 Title: Updating initramfs - possible missing amdgpu firmware Status in initramfs-tools package in Ubuntu: Confirmed Bug description: On a clean install of Ubuntu 20.04 the following messages are printed while updating the initramfs. update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu I: The initramfs will attempt to resume from /dev/nvme0n1p2 I: (UUID=610d0eae-f18f-4d55-86a0-9cb12375dafb) I: Set the RESUME variable to override Checking in /lib/firmware/amdgpu/ I have a fair number of firmware files but those listed. I'm not sure if these are missing or not needed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 09:48:49 2020 InstallationDate: Installed on 2020-03-20 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869673/+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 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
** Attachment added: "Here's the alsa-info output for this system, in case it helps." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5356402/+files/alsa-info.txt.QsoAGgtfAU -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+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 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
With the -1ubuntu2 package, I no longer get a crash dump, but the audio is still not working. pulseaudio is aborting. Here is what is in syslog from bootup: Apr 18 01:13:09 shh dbus-daemon[1218]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=122 pid=1443 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") ... Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:10 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:10 shh systemd[1432]: Dependency failed for GNOME Sound sample caching handling. Apr 18 01:13:10 shh systemd[1432]: gsd-sound.target: Job gsd-sound.target/start failed with result 'dependency'. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 1. ... Apr 18 01:13:10 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:10 shh systemd[1432]: Starting Sound Service... ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:12 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:12 shh systemd[1432]: Startup finished in 2.727s. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Apr 18 01:13:12 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:12 shh systemd[1432]: Starting Sound Service... Apr 18 01:13:12 shh rtkit-daemon[1539]: Successfully made thread 1864 of process 1864 owned by '122' high priority at nice level -11. Apr 18 01:13:12 shh rtkit-daemon[1539]: Supervising 1 threads of 1 processes of 1 users. Apr 18 01:13:12 shh pulseaudio[1864]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or
[Touch-packages] [Bug 1873510] Re: Blank screen when hotplugging monitors connected through DisplayPort dock
It kind if sounds like the system is in partial sleep mode, or trying to get there. And that would make sense because when the bug occurs the lid is closed and you've disconnected the only other screen. So you're kind of asking for screen hotplugging (or switching back to it on the KVM) to wake the system. When you put it that way it's kind of not a bug, if the theory is right... Can you please run 'gnome-tweaks' and check that: Gnome Tweaks > Power > Suspend when laptop lid is closed = OFF ? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1873510 Title: Blank screen when hotplugging monitors connected through DisplayPort dock Status in Ubuntu: Incomplete Bug description: Hi, I run Ubuntu 18.04 on a Dell Precision 7540. Most of the time I use this through a Dell WD19DC dock. The dock is connected to a Trendnet TK-240DP KVM Switch. If I have the laptop clamshell closed, like I normally do, and switch my KVM to the other computer, and then switch back, my monitors stay enter power saving mode. Most of the time, I am able to recover the screens by pressing Control-Alt-F3, waiting a few seconds, and then pressing Control-Alt-F2. The problem does not happen if the clamshell is left open. Part of the problem is that this is a cheaper KVM, and from the laptop's perspective the screens are disconnected when the computer is switched. Changing a few small things makes the problem not occur: * Opening the clamshell when switching the KVM. Interestingly, if the clamshell is open during either the switch away OR the switch back, the screen recovers. * Manually removing the displays one at a time does not reliably trigger the problem. Though I have witnessed the problem occur once or twice when removing a single display. I am attaching three nvidia bug report logs: 1. nvidia-bug-report-before.log.gz is after a clean boot when I have not used the KVM. 2. nvidia-bug-report-blank.log.gz is after switching the KVM to the other computer and back. During this time, both screens are black. The log was taken over ssh. 3. nvidia-bug-report-workaround.log.gz is after I have recovered the screen after using Ctrl-Alt-F3 followed by Ctrl-Alt-F2. This problem happens when prime-select is set to intel or nvidia. These logs are when it was set to intel. Any advice would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.5.0-050500rc6-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 17 13:57:43 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 440.82, 4.15.0-1079-oem, x86_64: installed nvidia, 440.82, 5.0.0-1047-oem-osp1, x86_64: installed nvidia, 440.82, 5.5.0-050500rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0926] NVIDIA Corporation Device [10de:1f36] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0926] InstallationDate: Installed on 2020-01-03 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Precision 7540 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.5.0-050500rc6-generic root=UUID=7f01cb01-e7df-4259-9d7a-ae37a19f363b ro quiet splash dis_ucode_ldr vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1872698] Re: Curl linked against GnuTLS doesn't use TLS 1.3
Can confirm that the issue is indeed fixed after I updated to the latest released version. Thanks for the quick turnaround! -- 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/1872698 Title: Curl linked against GnuTLS doesn't use TLS 1.3 Status in curl package in Ubuntu: Fix Released Bug description: Ubuntu 20.04 ships a recent version of GnuTLS which supports TLS 1.3. Git uses GnuTLS for TLS through libcurl, so I had expected that it also uses TLS 1.3 for Git. Since early last year, I added TLS 1.3 on GitHub.com as announced in https://github.blog/changelog/2019-01-15-tls13-rollout/. Testing shows it's not used though: dirkjan@x:~/curl$ cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal dirkjan@x:~$ GIT_CURL_VERBOSE=1 git ls-remote https://github.com/torvalds/linux.git * Couldn't find host github.com in the .netrc file; using defaults * Trying 192.30.255.113:443... * TCP_NODELAY set * Connected to github.com (192.30.255.113) port 443 (#0) * found 384 certificates in /etc/ssl/certs * ALPN, offering h2 * ALPN, offering http/1.1 * SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256 * server certificate verification OK * server certificate status verification SKIPPED * common name: github.com (matched) * server certificate expiration date OK * server certificate activation date OK * certificate public key: RSA * certificate version: #3 * subject: businessCategory=Private Organization,jurisdictionOfIncorporationCountryName=US,jurisdictionOfIncorporationStateOrProvinceName=Delaware,serialNumber=5157550,C=US,ST=California,L=San Francisco,O=GitHub\, Inc.,CN=github.com * start date: Tue, 08 May 2018 00:00:00 GMT * expire date: Wed, 03 Jun 2020 12:00:00 GMT * issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert SHA2 Extended Validation Server CA * ALPN, server accepted to use http/1.1 > GET /torvalds/linux.git/info/refs?service=git-upload-pack HTTP/1.1 Host: github.com User-Agent: git/2.25.1 Accept: */* Accept-Encoding: deflate, gzip, br Accept-Language: en-US, *;q=0.9 Pragma: no-cache * Mark bundle as not supporting multiuse < HTTP/1.1 200 OK < Server: GitHub Babel 2.0 < Content-Type: application/x-git-upload-pack-advertisement < Transfer-Encoding: chunked < Expires: Fri, 01 Jan 1980 00:00:00 GMT < Pragma: no-cache < Cache-Control: no-cache, max-age=0, must-revalidate < Vary: Accept-Encoding < X-GitHub-Request-Id: E01C:5AF3:3377B9:45B65F:5E959D1B < X-Frame-Options: DENY As can be seen here with the "* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256" bit, only TLS 1.2 is used. After further investigation, I found the problem in Curl, and submitted a fix: https://github.com/curl/curl/pull/5223. The fix was merged & I also manually tested this by patching the version of Curl shipping with 20.04 and testing there: dirkjan@x:~/curl$ ./src/curl --version curl 7.68.0-DEV (x86_64-pc-linux-gnu) libcurl/7.68.0-DEV GnuTLS/3.6.13 zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3 Release-Date: [unreleased] dirkjan@x:~/curl$ ./src/curl -v https://github.com > /dev/null % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 140.82.118.3:443... * TCP_NODELAY set * Connected to github.com (140.82.118.3) port 443 (#0) * found 128 certificates in /etc/ssl/certs/ca-certificates.crt * ALPN, offering h2 * ALPN, offering http/1.1 * SSL connection using TLS1.3 / ECDHE_RSA_AES_128_GCM_SHA256 * server certificate verification OK * server certificate status verification SKIPPED * common name: github.com (matched) * server certificate expiration date OK * server certificate activation date OK * certificate public key: RSA * certificate version: #3 * subject: businessCategory=Private Organization,jurisdictionOfIncorporationCountryName=US,jurisdictionOfIncorporationStateOrProvinceName=Delaware,serialNumber=5157550,C=US,ST=California,L=San Francisco,O=GitHub\, Inc.,CN=github.com * start date: Tue, 08 May 2018 00:00:00 GMT * expire date: Wed, 03 Jun 2020 12:00:00 GMT *
