[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
Maybe a workaround fix could be to restart ubuntu if dependent services had to be stopped to update something? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] Re: docker stopped when containerd updated
Here are people who are hit by this except for mysql: https://askubuntu.com/questions/1037285/starting-daily-apt-upgrade-and-clean-activities-stopping-mysql-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades-dpkg.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades-dpkg.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346860/+files/unattended-upgrades-dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346859/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] [NEW] docker stopped when containerd updated
Public bug reported: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description:Ubuntu 18.04.4 LTS Release:18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl --since "2020-04-03 06:33:52" --until "2020-04-03 06:54:50" >journalctl.log" https://bugs.launchpad.net/bugs/1870876/+attachment/5346855/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled Status in systemd package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. A suggested fix could be (ordered based on how nice of a solution it is): a. The capability detection is fixed (https://github.com/systemd/systemd/issues/9384) b. Force-disabling capability detection exists (this is what I also requested here: https://github.com/systemd/systemd/issues/14435) c. Patch Ubuntu version not to allow such a foot gun, update documentation (this is theoretically what Ubuntu could do meanwhile) d. Remove DNSSEC from resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+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 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
Called upstream's attention to this via: https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870843 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync() Status in ibus package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 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-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:03:51 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fee4f4e8f5b : orq $0x0,(%rsp) PC (0x7fee4f4e8f5b) ok source "$0x0" ok destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+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 1870856] [NEW] Changing Icons does not automatically change on desktop
Public bug reported: Ubuntu Desktop: Please note first that I had cinnamon-remix installed-I was bored so I installed Ubuntu and Ubuntu Budgie desktops, along with gnome-tweaks and gnome-shell. I was changing the icons using GNOME Tweak Tool. In nautilus, the changes automatically would apply. However, for the desktop, the changes would NOT automatically apply. I had to re-login to see the changes. If possible, I hope you guys can install a fresh Ubuntu and confirm this. Theme used was Kimmo-Dark from Ubuntu Cinnamon, and I found this issue for pretty much all the themes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.447 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 20:39:23 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: cinnamon-remix 20.04 "focal" - all amd64 (20200401) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1870856 Title: Changing Icons does not automatically change on desktop Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Desktop: Please note first that I had cinnamon-remix installed-I was bored so I installed Ubuntu and Ubuntu Budgie desktops, along with gnome-tweaks and gnome-shell. I was changing the icons using GNOME Tweak Tool. In nautilus, the changes automatically would apply. However, for the desktop, the changes would NOT automatically apply. I had to re-login to see the changes. If possible, I hope you guys can install a fresh Ubuntu and confirm this. Theme used was Kimmo-Dark from Ubuntu Cinnamon, and I found this issue for pretty much all the themes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.447 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 20:39:23 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: cinnamon-remix 20.04 "focal" - all amd64 (20200401) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1870856/+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 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key
Plus, of course: Delete key affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key Status in ibus package in Ubuntu: Triaged Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key
Just stumbled upon this issue: https://github.com/ibus/ibus/issues/2130 Common denominators are: * Error in ~/.XCompose * Upgrade to ibus 1.5.21 ** Bug watch added: github.com/ibus/ibus/issues #2130 https://github.com/ibus/ibus/issues/2130 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key Status in ibus package in Ubuntu: Triaged Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
** Summary changed: - Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal] + Multi-line paste broken between kitty and nano 4.8 [focal] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] Status in nano package in Ubuntu: New Bug description: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi-line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+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 1870850] [NEW] Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal]
Public bug reported: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi- line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. ** Affects: nano (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal] Status in nano package in Ubuntu: New Bug description: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi-line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+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 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870843 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync() Status in ibus package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 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-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:03:51 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fee4f4e8f5b : orq $0x0,(%rsp) PC (0x7fee4f4e8f5b) ok source "$0x0" ok destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+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 1030489] Re: Additional Drivers says Wifi is not in use when using open driver
Similar in Ubuntu 20.04 final beta. Shows "This device is not working" and "Do not use device" is selected (and grayed out), but wireless is working. -- 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/1030489 Title: Additional Drivers says Wifi is not in use when using open driver Status in software-properties package in Ubuntu: Confirmed Bug description: Hello, I have an internal wifi card BCM43224 and I am using the open-source driver brcmsmac. In Ubuntu Quantal, Additional Drivers says that "The Device is not working" instead of offering the brcmsmac driver. $ lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 $ apt-cache policy software-properties-common software-properties-common: Installed: 0.91 Candidate: 0.91 Version table: *** 0.91 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status Regards, Aurélien To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1030489/+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 1866820] Re: crash in nano-4.8 when typing ^6 ^J [patch]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nano (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1866820 Title: crash in nano-4.8 when typing ^6 ^J [patch] Status in nano package in Ubuntu: Confirmed Bug description: Nanos since version 4.0 contain a silly oversight: when the user tries to justify an empty region (with ^6 ^J, or similar), nano crashes. Attached upstream patch fixes the problem. Please apply to Focal before it is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1866820/+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 1870851] [NEW] When closing the lid or suspending and turning on, wifi goes to airplane mode
Public bug reported: when computer is suspended or the lid is closed it goes to airplane mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 01:09:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-24 (102 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-03-15 (20 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- wlo1 wifi unavailable none none /org/freedesktop/NetworkManager/Devices/3 -- ---- p2p-dev-wlo1 wifi-p2p unavailable none none /org/freedesktop/NetworkManager/Devices/4 -- ---- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled disabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870851 Title: When closing the lid or suspending and turning on, wifi goes to airplane mode Status in network-manager package in Ubuntu: New Bug description: when computer is suspended or the lid is closed it goes to airplane mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 01:09:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-24 (102 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-03-15 (20 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- wlo1 wifi unavailable none none /org/freedesktop/NetworkManager/Devices/3 -- ---- p2p-dev-wlo1 wifi-p2p unavailable none none /org/freedesktop/NetworkManager/Devices/4 -- ---- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870851/+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 1865411] Re: Need to restart Network Manager frequently
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #267 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/267 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/267 Importance: Unknown Status: Unknown -- 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/1865411 Title: Need to restart Network Manager frequently Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Bug description: My WiFi connection keeps stopping to work every once in a while (sometimes as often as every 10 minutes). Restarting NetworkManager usually resolves this problem. But I am not sure why that is the case. I do not think there is a connectivity issue as it happens even when I am right next to the access point. I have a standard Intel Wireless chip and use GNOME shell with some extensions. Nothing exotic. Note this happened on eoan as well as focal (and maybe even before that). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 19:56:11 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-09 (236 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/fish SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.8 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1865411/+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 1844867] Re: gtkfileselector window "open file" cannot be maximized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/1844867 Title: gtkfileselector window "open file" cannot be maximized Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When I do "Open file" from within any application, the nautilus window appears but it doesn't have the "maximize" button and also the double-click on its titlebar does nothing. I must resize it manually by dragging each border... In the previous versions of nautilus this action were possible and much useful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 14:20:27 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'890x545+428+170'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-09-07 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1844867/+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 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
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/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: Yesterday I was using the HDMI cable to duplicate the monitor in the tv and play sound with the tv by selecting HDMI exit sound in ubuntu settings. With the pc turned off I removed the HDMI from the tv but ubuntu doesn't automatically set the exit sound to the default till in the settings there is only that option and till I selected it, ubuntu was still trying to reproduce the audio via HDMI... Also rebooting the system the problem persists. Also by reloading pulseaudio the problem persists. The only solution was installing a third-party program to switch correctly to the default audio exit... lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy pulseaudio: pulseaudio: Installato: 1:11.1-1ubuntu7.2 Candidato: 1:11.1-1ubuntu7.4 Tabella versione: 1:11.1-1ubuntu7.4 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 1:11.1-1ubuntu7.2 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+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 1844239] Re: ubuntu-bug (apport) does not open a new tab in the browser after click “send”
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1844239 Title: ubuntu-bug (apport) does not open a new tab in the browser after click “send” Status in apport package in Ubuntu: Confirmed Bug description: I do "ubuntu-bug packageName" in the terminal, then the window appear asking to me to chose "not send" or "send". After clicking "send" nothing happens and the window closes, without open a new tab in the browser. I already inserted Crash in /etc/apport/crashdb.conf The file /etc/default/apport already contains: enabled=1 lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy apport: apport: Installato: 2.20.9-0ubuntu7.6 Candidato: 2.20.9-0ubuntu7.7 Tabella versione: 2.20.9-0ubuntu7.7 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages *** 2.20.9-0ubuntu7.6 100 100 /var/lib/dpkg/status 2.20.9-0ubuntu7 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1844239/+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 1685754] Re: gnome-terminal unduly forces umask=0022
With systemd version 245.2-1ubuntu2 from Ubuntu 20.04 Beta (Focal
Fossa), the issue is still the same.
** Tags added: eoan focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1865411] Re: Need to restart Network Manager frequently
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1865411 Title: Need to restart Network Manager frequently Status in network-manager package in Ubuntu: Confirmed Bug description: My WiFi connection keeps stopping to work every once in a while (sometimes as often as every 10 minutes). Restarting NetworkManager usually resolves this problem. But I am not sure why that is the case. I do not think there is a connectivity issue as it happens even when I am right next to the access point. I have a standard Intel Wireless chip and use GNOME shell with some extensions. Nothing exotic. Note this happened on eoan as well as focal (and maybe even before that). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 19:56:11 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-09 (236 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/fish SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.8 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1865411/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
** Description changed: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] - see any failed build or failed root-unittest, e.g. + see any failed build, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. -- 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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
** Description changed: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build or failed root-unittest, e.g. - https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/s/systemd/20200331_010822_1c88e@/log.gz + https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. -- 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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build or failed root-unittest, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1870824] Re: Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh
The attachment "Patch that fixes the two errors" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1870824 Title: Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh Status in avahi package in Ubuntu: New Bug description: In line 42 and 46 Command Substitution is used wrongly because the shell expects to execute what it returns. See attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1870824/+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 1870837] [NEW] Ubuntu 20.04 (focal): hcitool lescan broken
Public bug reported: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870837 Title: Ubuntu 20.04 (focal): hcitool lescan broken Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870820] Re: Super (command) on Mac doesn't open Search
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1870820 Title: Super (command) on Mac doesn't open Search Status in ubuntu-meta package in Ubuntu: New Bug description: Pressing Super, which is the right command on Mac, doesn't open the start menu. I opened the Keyboard Shortcuts and there was none set for default, and I couldn't set the default to a command, I could only set it to at least 2 characters, so I had to use RCmd and Space. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.447 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: Sat Apr 4 17:15:50 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1870820/+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 1870820] [NEW] Super (command) on Mac doesn't open Search
You have been subscribed to a public bug: Pressing Super, which is the right command on Mac, doesn't open the start menu. I opened the Keyboard Shortcuts and there was none set for default, and I couldn't set the default to a command, I could only set it to at least 2 characters, so I had to use RCmd and Space. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.447 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: Sat Apr 4 17:15:50 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Super (command) on Mac doesn't open Search https://bugs.launchpad.net/bugs/1870820 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1870725] Re: artifacts appearing on gnome shell
I believed I narrowed down the issue to how gnome-shell uses Xorg. As said before GDM did not have any issues, and (i may be seriously wrong here) GDM uses Wayland by default. When I launch the Ubuntu desktop with Wayland, the graphical issue went away and is running smoothly. So I narrowed down the issue to Xorg or gnome-shell. So I went ahead and installed Cinnamon DE which uses Xorg, and the issue did not arise. My theory is that gnome-shell has a problem with rendering the shell (not programs) with Xorg. I also attached another image showing the problem, could the issue be the compositor??? ** Attachment added: "Screenshot from 2020-04-04 13-11-46.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1870725/+attachment/5346554/+files/Screenshot%20from%202020-04-04%2013-11-46.png ** No longer affects: ubuntu-meta (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1870725 Title: artifacts appearing on gnome shell Status in gnome-shell package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: problems appear on the desktop and lock screen (not in gdm) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 22:50:55 2020 DistUpgraded: 2020-04-03 20:26:10,751 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20L5CTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5CTO1WW dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/gnome-shell/+bug/1870725/+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 543767] Re: ssh logins doesn't show the MOTD when connecting with public key authorisation
** Changed in: server-papercuts Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/543767 Title: ssh logins doesn't show the MOTD when connecting with public key authorisation Status in Ubuntu Server papercuts: Invalid Status in openssh package in Ubuntu: Invalid Bug description: This is merely a minor annoyance, but nonetheless worth a bug report for the servers papercut team: The method to display a MOTD described in the official Ubuntu server guide, chapter 22 (https://help.ubuntu.com/9.10/serverguide/C/update- motd.html) doesn't work as soon as you connect with public key authorisation. Connecting /w password only shows the MOTD correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/543767/+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 1870829] [NEW] AptX and AptX HD unavailable as Bluetooth audio quality options
Public bug reported: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. ** Affects: pulseaudio (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/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: New Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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.
A workaround is to install https://developer.nvidia.com/cuda- downloads?target_os=Linux&target_arch=x86_64&target_distro=Ubuntu&target_version=1804&target_type=debnetwork -- 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 : https://launchpad.net/~touch
[Touch-packages] [Bug 1870824] [NEW] Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh
Public bug reported: In line 42 and 46 Command Substitution is used wrongly because the shell expects to execute what it returns. See attached patch. ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Patch added: "Patch that fixes the two errors" https://bugs.launchpad.net/bugs/1870824/+attachment/5346540/+files/diff-1.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1870824 Title: Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh Status in avahi package in Ubuntu: New Bug description: In line 42 and 46 Command Substitution is used wrongly because the shell expects to execute what it returns. See attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1870824/+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 1870814] Re: Lists of Output and Input devices empty on sound settings
I'm guessing this is either a pulseaudio or a gnome-control-center issue. Assigning to pulseaudio for the moment. ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntubudgie -- 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/1870814 Title: Lists of Output and Input devices empty on sound settings Status in pulseaudio package in Ubuntu: New Bug description: While both Sound Input and Output is working well, their respective lists on the Sound tab on Settings are empty, preventing from adjusting and testing any settings. Aspire-A315-55G:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal Aspire-A315-55G:~$ budgie-desktop --version budgie-desktop 10.5.1 Copyright © 2014-2019 Budgie Desktop Developers Aspire-A315-55G:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 Aspire-A315-55G:~$ arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870814/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
** Description changed: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build or failed root-unittest, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/s/systemd/20200331_010822_1c88e@/log.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] - this is needed in all releases. + Xenial does not use meson, so can not be adjusted. This is needed in + Bionic and later. ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Invalid -- 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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build or failed root-unittest, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/s/systemd/20200331_010822_1c88e@/log.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1870779] Re: Ubuntu 20.04 beta: Blank/black screen after login
** 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/1870779 Title: Ubuntu 20.04 beta: Blank/black screen after login Status in xorg package in Ubuntu: New Bug description: I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login right after installation, but after a few reboots a black screen is displayed after login. I'm able to switch to a tty and tried to collect information with ubuntu-bug, but I am not sure if that help. I'm happy to provide further information if needed. I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the same. 19.10 works without any problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 4 14:05:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7] InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5675 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.7 dmi.board.name: 0477DV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.7 dmi.modalias: dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7: dmi.product.family: Inspiron dmi.product.name: Inspiron 5675 dmi.product.sku: 07EE dmi.product.version: 1.3.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+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/xorg/+bug/1870779/+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 1870811] [NEW] compile auto test failure, and root-unittest failure, is extremely noisy
Public bug reported: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build or failed root-unittest, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/s/systemd/20200331_010822_1c88e@/log.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] this is needed in all releases. ** Affects: systemd (Ubuntu) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Xenial) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Bionic) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Eoan) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress -- 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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build or failed root-unittest, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/s/systemd/20200331_010822_1c88e@/log.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] this is needed in all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1870779] [NEW] Ubuntu 20.04 beta: Blank/black screen after login
You have been subscribed to a public bug: I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login right after installation, but after a few reboots a black screen is displayed after login. I'm able to switch to a tty and tried to collect information with ubuntu-bug, but I am not sure if that help. I'm happy to provide further information if needed. I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the same. 19.10 works without any problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 4 14:05:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7] InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5675 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.7 dmi.board.name: 0477DV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.7 dmi.modalias: dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7: dmi.product.family: Inspiron dmi.product.name: Inspiron 5675 dmi.product.sku: 07EE dmi.product.version: 1.3.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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 crash focal ubuntu -- Ubuntu 20.04 beta: Blank/black screen after login https://bugs.launchpad.net/bugs/1870779 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 1870805] [NEW] pas de son
Public bug reported: je n'ai pas de son qui sort de l'ordinateur, pas de sortie audio ni d'applications pour le son avec Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 17:25:31 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2018 dmi.bios.version: HQ-BI-14.1-Y116CR600-CC34I-014-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHQ-BI-14.1-Y116CR600-CC34I-014-D:bd01/08/2018:svnSCHNEIDER:pnSCL141CTP:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SCL141CTP dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: SCHNEIDER ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870805 Title: pas de son Status in pulseaudio package in Ubuntu: New Bug description: je n'ai pas de son qui sort de l'ordinateur, pas de sortie audio ni d'applications pour le son avec Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 17:25:31 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2018 dmi.bios.version: HQ-BI-14.1-Y116CR600-CC34I-014-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHQ-BI-14.1-Y116CR600-CC34I-014-D:bd01/08/2018:svnSCHNEIDER:pnSCL141CTP:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SCL141CTP dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: SCHNEIDER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870805/+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 193230] Re: libpcre3 < 7.6 is vulnerable to a buffer overflow resulting in remote code execution bug
Launchpad has imported 26 comments from the remote bug at https://bugs.gentoo.org/show_bug.cgi?id=209067. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-02-05T23:55:57+00:00 hoffie wrote: dev-libs/libpcre-7.6 fixes a buffer overflow issue: 1. A character class containing a very large number of characters with codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer overflow. Ebuild should be in the tree soon (thanks to Opfer), see the other bug for details. Reply at: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/193230/comments/0 On 2008-02-05T23:57:51+00:00 fauli wrote: *** Bug 209060 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/193230/comments/1 On 2008-02-06T00:01:53+00:00 fauli wrote: x86 already stable, adding arches Reply at: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/193230/comments/2 On 2008-02-06T00:03:15+00:00 fauli wrote: Stabilise dev-libs/libpcre-7.6 please Reply at: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/193230/comments/3 On 2008-02-06T00:04:46+00:00 wolf31o2 wrote: Don't forget to add release@ to security bugs. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/193230/comments/4 On 2008-02-06T02:12:04+00:00 ranger wrote: ppc64 done Reply at: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/193230/comments/5 On 2008-02-06T03:43:06+00:00 jieryn wrote: amd64 stable - Package emerges fine, and I remerged grep with USE="pcre". No obvious regressions. Portage 2.1.3.19 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.23.9 x86_64) = System uname: 2.6.23.9 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ Timestamp of tree: Wed, 06 Feb 2008 03:00:01 + distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r6 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.10-r5 sys-apps/sandbox:1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer -fweb -ftracer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer -fweb -ftracer" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--verbose --nospinner" FEATURES="buildpkg collision-protect distlocks fixpackages metadata-transfer multilib-strict parallel-fetch sandbox sfperms strict test unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"; LINGUAS="en" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.1.102/gentoo-portage" USE="3dnow X a52 aac acl acpi alsa amd64 ao apache2 audiofile autoipd automount avahi bash-completion berkdb bitmap-fonts bzip2 caps cddb cdparanoia cli cracklib crypt dbus directfb dri dvd encode expat fbcon ffmpeg flac fontconfig ftp gdbm gif gnutella gnutls hal iconv icu id3 idea imagemagick imlib ipv6 isdnlog java jpeg kerberos key-screen lame logrotate lzo mad mdnsresponder-compat midi mmap mmx mp3 mpeg mplayer ncurses network nolvm1 nptl nptlonly ogg openft openmp pam pcre perl png pppd pulseadio pulseaudio python quicktime readline reflection samba sdl search-screen session spl sse sse2 ssl subtitles svg swat syslog tcpd test theora threads tiff truetype truetype-fonts type1-fonts unicode vorbis x264 xgetdefault xinetd xml xorg xvid zeroconf
[Touch-packages] [Bug 186578] Re: [libicu] [CVE-2007-4770] [CVE-2007-4771] potential execution of arbitrary code via malformed regular expressions
Launchpad has imported 19 comments from the remote bug at https://bugs.gentoo.org/show_bug.cgi?id=208001. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-01-29T07:34:24+00:00 lars wrote: Will Drewry has reported some vulnerabilities in International Components for Unicode, which can be exploited by malicious people to cause a DoS (Denial of Service) or potentially compromise an application using the library. 1) A regular expression containing a back reference to capture group zero (\0) may reference random memory areas, which can be exploited to crash an application using the library. 2) The library does not limit the size of the backtracking stack. This can be exploited to cause a heap-based buffer overflow via certain specially crafted regular expressions. The vulnerability is reported in version 3.8.1. Other versions may also be affected. Solution: Apply patch. http://source.icu-project.org/repos/icu/icu/branches/maint/maint-3-8 Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/9 On 2008-01-29T07:37:00+00:00 lars wrote: maintainers - please provide an updated ebuild Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/10 On 2008-01-29T08:17:50+00:00 jakub wrote: *** Bug 207905 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/11 On 2008-02-01T22:51:47+00:00 rbu wrote: ping Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/12 On 2008-02-01T23:35:32+00:00 rbu wrote: I reproduced the 4771 issue on 3.6.1. Caolan McNamara from RedHat backported the patches to 3.6: https://bugzilla.redhat.com/show_bug.cgi?id=429023 This bug also affects OpenOffice, as it currently uses an internal copy of icu. OpenOffice herd, please advise here. Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/13 On 2008-02-02T00:06:31+00:00 rbu wrote: OpenOffice, please try building against the (security patched) libicu 3.8.1-r1 here: http://overlays.gentoo.org/svn/proj/php/migration/dev- libs/icu/ If that does not work, please patch the copy of icu. Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/14 On 2008-02-02T18:27:58+00:00 suka wrote: (In reply to comment #5) > OpenOffice, please try building against the (security patched) libicu 3.8.1-r1 > here: http://overlays.gentoo.org/svn/proj/php/migration/dev-libs/icu/ > > If that does not work, please patch the copy of icu. > I've added a new revision (-r1) of openoffice-2.3.1 to portage, this uses external icu again (we had to back this out prior to stabilizing 2.3.1 as it was broken in OOo), works fine here on x86, other archs will have to test accordingly Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/15 On 2008-02-02T21:56:35+00:00 hoffie wrote: icu-3.8.1-r1 with the patch is in the tree now, thanks to jakub. I did not do any tests except from compiling (I haven't touched that package before anyway). I might try building OOo tomorrow, but certainly not today. Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/16 On 2008-02-02T22:24:27+00:00 hoffie wrote: icu-3.6-r2 in the tree as well (with the patch from redhat). You probably want 3.8* stable for OpenOffice anyway, but I don't really know, ask jakub if in doubt. ;) Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/17 On 2008-02-03T08:54:55+00:00 jakub wrote: (In reply to comment #8) > icu-3.6-r2 in the tree as well (with the patch from redhat). You probably want > 3.8* stable for OpenOffice anyway, but I don't really know, ask jakub if in > doubt. ;) Well, yes, definitely. It won't compile with ~icu-3.6. arches, please test and stabilize the following: dev-libs/icu-3.6-r2 (will be hanging around for dev-libs/xerces-c-2.8.0 at least unless someone fixes the messy thing to work w/ icu-3.8.x) dev-libs/icu-3.8.1-r1 Reply at: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/186578/comments/18
[Touch-packages] [Bug 1870788] [NEW] Sound randomly stops working for individual programs
Public bug reported: 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 ** Affects: alsa-driver (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 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="un
[Touch-packages] [Bug 1863919] Re: [regression] lingering pvscan during boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1863919 Title: [regression] lingering pvscan during boot Status in lvm2 package in Ubuntu: Confirmed Bug description: Since lvm2 was updated to 2.02.176-4.1ubuntu3.18.04.2 on Bionic (LP: #1854981), we notice that some of our machines have lingering pvscan processes apparently running from the initramfs's root that persist/never finish/exit. On the affected servers, this is visible as there are 2 instances of systemd-udevd, one in the init.scope and another in system.slice: $ systemd-cgls | cat Control group /: -.slice ├─user.slice │ ├─user-501.slice │ │ ├─session-7.scope │ │ │ ├─12324 sshd: foo [priv] │ │ │ ├─12353 sshd: foo@pts/2 │ │ │ ├─12354 script --quiet --return --command /bin/bash -l /dev/null │ │ │ ├─12356 /bin/bash -l │ │ │ ├─12375 sudo -i │ │ │ └─12385 -bash │ │ └─user@501.service │ │ └─init.scope │ │ ├─12326 /lib/systemd/systemd --user │ │ └─12327 (sd-pam) │ └─user-500.slice │ ├─user@500.service │ │ └─init.scope │ │ ├─12185 /lib/systemd/systemd --user │ │ └─12186 (sd-pam) │ └─session-3.scope │ ├─12170 sshd: sdeziel [priv] │ ├─12254 sshd: sdeziel@pts/0 │ ├─12255 script --quiet --return --command /bin/bash -l /dev/null │ ├─12257 /bin/bash -l │ ├─14409 systemd-cgls │ └─14410 cat ├─init.scope │ ├─ 1 /sbin/init kaslr nosplash │ ├─1451 /lib/systemd/systemd-udevd --daemon --resolve-names=never │ ├─1466 /sbin/lvm pvscan --cache --activate ay --major 8 --minor 3 │ ├─1470 /sbin/lvm pvscan --cache --activate ay --major 8 --minor 2 │ ├─1481 /sbin/lvm pvscan --cache --activate ay --major 253 --minor 1 │ └─1551 /sbin/lvm pvscan --cache --activate ay --major 253 --minor 1 └─system.slice ├─irqbalance.service │ └─2796 /usr/sbin/irqbalance --foreground ├─systemd-networkd.service │ └─2833 /lib/systemd/systemd-networkd ├─systemd-udevd.service │ └─1627 /lib/systemd/systemd-udevd ├─cron.service │ ├─ 2786 /usr/sbin/cron -f │ └─12308 /usr/bin/python /usr/sbin/ganeti-noded -b 172.20.30.212 ├─system-serial\x2dgetty.slice │ └─serial-getty@ttyS0.service │ └─12112 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220 ├─systemd-journald.service │ └─1601 /lib/systemd/systemd-journald ├─ssh.service │ └─12115 /usr/sbin/sshd -D ├─rsyslog.service │ └─2781 /usr/sbin/rsyslogd -n ├─nagios-nrpe-server.service │ └─12108 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -f ├─lvm2-lvmetad.service │ └─1630 /sbin/lvmetad -f ├─systemd-resolved.service │ └─3280 /lib/systemd/systemd-resolved ├─dbus.service │ └─2762 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidf... ├─systemd-timesyncd.service │ └─2491 /lib/systemd/systemd-timesyncd ├─system-getty.slice │ └─getty@tty1.service │ └─12113 /sbin/agetty -o -p -- \u --noclear tty1 linux ├─systemd-logind.service │ └─2797 /lib/systemd/systemd-logind └─ganeti.service ├─ 3892 /usr/sbin/ganeti-confd ├─12173 /usr/sbin/ganeti-kvmd └─12276 /usr/sbin/ganeti-mond The systemd-udevd in init.scope and the many /sbin/lvm pvscan it launched during boot are left there forever. This trips our monitoring for binaries using deleted binaries/libs and is also visible like that: # pgrep systemd-udevd 1451 1627 # ls -l /proc/1451/exe lrwxrwxrwx 1 root root 0 Feb 19 10:35 /proc/1451/exe -> '/lib/systemd/systemd-udevd (deleted)' # ls -l /proc/1627/exe lrwxrwxrwx 1 root root 0 Feb 19 10:35 /proc/1627/exe -> /lib/systemd/systemd-udevd This can be compared with another server *NOT AFFECTED*, where the init.scope is cleaner (/sbin/init only) and a single systemd-udevd process: # systemd-cgls | cat Control group /: -.slice ├─user.slice │ └─user-0.slice │ ├─session-313.scope │ │ ├─90332 sshd: root@pts/0 │ │ ├─90406 script --quiet --return --command /bin/bash -l /dev/null │ │ ├─90410 /bin/bash -l │ │ ├─90436 systemd-cgls │ │ └─90437 cat │ └─user@0.service │ └─init.scope │ ├─90334 /lib/systemd/systemd --user │ └─90335 (sd-pam) ├─init.scope │ └─1 /sbin/init kaslr nosplash └─system.slice ... ├─systemd-udevd.service │ └─2622 /lib/systemd/systemd-udevd ... ├─lvm2-lvmetad.service │ └─2621 /sbin/lvmetad -f ... Additional information: # lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 # apt-cache policy lvm2 systemd lvm2: Installed: 2.02.176-4.1ubuntu3.18.04.2 Candidate: 2.02.176-4.1ubuntu3.18.04.2 Version table: *** 2.02.176-4.1ubuntu3.18.04.2 500
[Touch-packages] [Bug 1863919] Re: [regression] lingering pvscan during boot
Do you also see slow shutdowns? One of my servers which has other problems with this patch (bug #1870783) has been seen to get stuck shutting down / rebooting showing a message about (I think) lvmetad (hard to tell due to very small server console truncating message) .. systemd eventually times it out (after, a bit randomly, 105 secs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1863919 Title: [regression] lingering pvscan during boot Status in lvm2 package in Ubuntu: Confirmed Bug description: Since lvm2 was updated to 2.02.176-4.1ubuntu3.18.04.2 on Bionic (LP: #1854981), we notice that some of our machines have lingering pvscan processes apparently running from the initramfs's root that persist/never finish/exit. On the affected servers, this is visible as there are 2 instances of systemd-udevd, one in the init.scope and another in system.slice: $ systemd-cgls | cat Control group /: -.slice ├─user.slice │ ├─user-501.slice │ │ ├─session-7.scope │ │ │ ├─12324 sshd: foo [priv] │ │ │ ├─12353 sshd: foo@pts/2 │ │ │ ├─12354 script --quiet --return --command /bin/bash -l /dev/null │ │ │ ├─12356 /bin/bash -l │ │ │ ├─12375 sudo -i │ │ │ └─12385 -bash │ │ └─user@501.service │ │ └─init.scope │ │ ├─12326 /lib/systemd/systemd --user │ │ └─12327 (sd-pam) │ └─user-500.slice │ ├─user@500.service │ │ └─init.scope │ │ ├─12185 /lib/systemd/systemd --user │ │ └─12186 (sd-pam) │ └─session-3.scope │ ├─12170 sshd: sdeziel [priv] │ ├─12254 sshd: sdeziel@pts/0 │ ├─12255 script --quiet --return --command /bin/bash -l /dev/null │ ├─12257 /bin/bash -l │ ├─14409 systemd-cgls │ └─14410 cat ├─init.scope │ ├─ 1 /sbin/init kaslr nosplash │ ├─1451 /lib/systemd/systemd-udevd --daemon --resolve-names=never │ ├─1466 /sbin/lvm pvscan --cache --activate ay --major 8 --minor 3 │ ├─1470 /sbin/lvm pvscan --cache --activate ay --major 8 --minor 2 │ ├─1481 /sbin/lvm pvscan --cache --activate ay --major 253 --minor 1 │ └─1551 /sbin/lvm pvscan --cache --activate ay --major 253 --minor 1 └─system.slice ├─irqbalance.service │ └─2796 /usr/sbin/irqbalance --foreground ├─systemd-networkd.service │ └─2833 /lib/systemd/systemd-networkd ├─systemd-udevd.service │ └─1627 /lib/systemd/systemd-udevd ├─cron.service │ ├─ 2786 /usr/sbin/cron -f │ └─12308 /usr/bin/python /usr/sbin/ganeti-noded -b 172.20.30.212 ├─system-serial\x2dgetty.slice │ └─serial-getty@ttyS0.service │ └─12112 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220 ├─systemd-journald.service │ └─1601 /lib/systemd/systemd-journald ├─ssh.service │ └─12115 /usr/sbin/sshd -D ├─rsyslog.service │ └─2781 /usr/sbin/rsyslogd -n ├─nagios-nrpe-server.service │ └─12108 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -f ├─lvm2-lvmetad.service │ └─1630 /sbin/lvmetad -f ├─systemd-resolved.service │ └─3280 /lib/systemd/systemd-resolved ├─dbus.service │ └─2762 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidf... ├─systemd-timesyncd.service │ └─2491 /lib/systemd/systemd-timesyncd ├─system-getty.slice │ └─getty@tty1.service │ └─12113 /sbin/agetty -o -p -- \u --noclear tty1 linux ├─systemd-logind.service │ └─2797 /lib/systemd/systemd-logind └─ganeti.service ├─ 3892 /usr/sbin/ganeti-confd ├─12173 /usr/sbin/ganeti-kvmd └─12276 /usr/sbin/ganeti-mond The systemd-udevd in init.scope and the many /sbin/lvm pvscan it launched during boot are left there forever. This trips our monitoring for binaries using deleted binaries/libs and is also visible like that: # pgrep systemd-udevd 1451 1627 # ls -l /proc/1451/exe lrwxrwxrwx 1 root root 0 Feb 19 10:35 /proc/1451/exe -> '/lib/systemd/systemd-udevd (deleted)' # ls -l /proc/1627/exe lrwxrwxrwx 1 root root 0 Feb 19 10:35 /proc/1627/exe -> /lib/systemd/systemd-udevd This can be compared with another server *NOT AFFECTED*, where the init.scope is cleaner (/sbin/init only) and a single systemd-udevd process: # systemd-cgls | cat Control group /: -.slice ├─user.slice │ └─user-0.slice │ ├─session-313.scope │ │ ├─90332 sshd: root@pts/0 │ │ ├─90406 script --quiet --return --command /bin/bash -l /dev/null │ │ ├─90410 /bin/bash -l │ │ ├─90436 systemd-cgls │ │ └─90437 cat │ └─user@0.service │ └─init.scope │ ├─90334 /lib/systemd/systemd --user │ └─90335 (sd-pam) ├─init.scope │ └─1 /sbin/init kaslr nosplash └─system.slice ... ├─systemd-udevd.service │ └─2622 /lib/systemd/systemd-udevd ... ├─lvm2-lvmetad.service │ └─2621 /sbin/lvmetad -f ... Additional information: # lsb_release -rd Description: Ubuntu 18.04.4 LTS Rel
[Touch-packages] [Bug 1859829] Re: server will not boot after updating lvm2 package
Just reported my own bug #1870783 - my server appears to hang (without above message), but eventually successfully boots after ~ 180 secs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1859829 Title: server will not boot after updating lvm2 package Status in lvm2 package in Ubuntu: Confirmed Bug description: After updating lvm2 from 2.02.176-4.1ubuntu3.18.04.1 to 2.02.176-4.1ubuntu3.18.04.2, server will not boot. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 2.02.176-4.1ubuntu3.18.04.2 3) What you expected to happen I expect the server to boot. 4) What happened instead The server hangs at boot. As the server will not boot, I can not provide any logs. I can only provide a screen captures of the boot failure messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1859829/+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 1870726] Re: Ubuntu Login Screen Loop
** Description changed: * Ubuntu Focal Fossa 20.04 (dev) * xorg: - Installed: 1:7.7+19ubuntu14 - Candidate: 1:7.7+19ubuntu1 + Installed: 1:7.7+19ubuntu14 + Candidate: 1:7.7+19ubuntu1 + * VirtualBox version : 5.2.34_Ubuntu r133883 (installed via apt) Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. - Steps to reproduce : + Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=d609fc71-9cba-4875-8bc1-795cb584a629 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1870726 Title: Ubuntu Login Screen Loop Status in xorg package in Ubuntu: New Bug description: * Ubuntu Focal Fossa 20.04 (dev) * xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu1 * VirtualBox version : 5.2.34_Ubuntu r133883 (installed via apt) Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox U
[Touch-packages] [Bug 1870783] [NEW] 2.02.176-4.1ubuntu3.18.04.2 causes 3 min boot hang
Public bug reported: 2.02.176-4.1ubuntu3.18.04.2 causes at least one of my servers to hang on boot for ~ 3 minutes. adding debug=y to kernel command line seems to show the last script was init-top/udev. Downgrading to 2.02.176-4.1ubuntu3 resolves the problem. Possibly related to bug #1859829 and bug #1863919. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 4 13:59:05 2020 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lvm.lvm.conf: 2018-11-09T14:30:02.719390 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: 2.02.176-4.1ubuntu3.18.04.2 causes at least one of my servers to hang on boot for ~ 3 minutes. adding debug=y to kernel command line seems to show the last script was init-top/udev. Downgrading to 2.02.176-4.1ubuntu3 resolves the problem. - Possibly related to #1859829 and #1863919. + Possibly related to bug #1859829 and bug #1863919. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 4 13:59:05 2020 ProcEnviron: - TERM=screen.xterm-256color - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=screen.xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lvm.lvm.conf: 2018-11-09T14:30:02.719390 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1870783 Title: 2.02.176-4.1ubuntu3.18.04.2 causes 3 min boot hang Status in lvm2 package in Ubuntu: New Bug description: 2.02.176-4.1ubuntu3.18.04.2 causes at least one of my servers to hang on boot for ~ 3 minutes. adding debug=y to kernel command line seems to show the last script was init-top/udev. Downgrading to 2.02.176-4.1ubuntu3 resolves the problem. Possibly related to bug #1859829 and bug #1863919. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 4 13:59:05 2020 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lvm.lvm.conf: 2018-11-09T14:30:02.719390 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1870783/+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 1870617] Re: Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)
** Description changed: Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main) Sorry, I can't work on this merge myself. - It fixes Debian bugs, and they can be related to Ubuntu too. + + It fixes Debian bugs, especially this one + https://bugs.debian.org/568686, which is related to performance, and + they can be related to Ubuntu too. Explanation of the Ubuntu delta: * Really include the symbols file update * debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch: - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings which make autopkgtests fail * Upload proposed patch from upstream bug #103652. If the fontconfig - cache was built on a system that has nanosecond timestamps and then - later transplanted to one that doesn't - for example by mksquashfs as - part of a live CD build - we consider the cache invalid and rebuild it - during the boot process. Depending on the fonts involved, this can - take a significant amount of time and potentially cause knock-on - timeouts. The approach in this patch is to ignore the nanosecond - portion of the cache's value if we get 0 when stat()ing the referenced - directory, meaning it is considered fresh if the rest of the timestamp - matches. (LP: #1749546) + cache was built on a system that has nanosecond timestamps and then + later transplanted to one that doesn't - for example by mksquashfs as + part of a live CD build - we consider the cache invalid and rebuild it + during the boot process. Depending on the fonts involved, this can + take a significant amount of time and potentially cause knock-on + timeouts. The approach in this patch is to ignore the nanosecond + portion of the cache's value if we get 0 when stat()ing the referenced + directory, meaning it is considered fresh if the rest of the timestamp + matches. (LP: #1749546) * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes: - debian/source_fontconfig.py, debian/fontconfig.install: + Install apport hook - Add 03_prefer_dejavu.patch: + Prefer DejaVu to Bitstream Vera - Add 04_ubuntu_monospace_lcd_filter_conf.patch: + Use legacy lcdfilter with smaller monospace fonts - Add 05_ubuntu_add_antialiasing_confs.patch: + Add config file for antialiasing - Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy", used in Ubuntu before upstream introduced "lcdlegacy" - Add 07_no_bitmaps.patch: + Install 70-no-bitmaps.conf - Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates, debian/fontconfig-config.config, and associatedpo files. Modify debian/rules, debian/fontconfig-config.postinst, debian/fontconfig-config.postrm, and debian/README.Debian. + Don't provide debconf prompts - Modify debian/rules, debian/fontconfig-config.install, debian/fontconfig-config.links, debian/fontconfig-config.postrm, and debian/fontconfig-udeb.install: + Delay doing the transition from /etc to /usr * New upstream release * Refresh patches * Update Ubuntu patches to use mode="append" and target="pattern" (LP: #1192175) * Drop patches applied in new release: - 01_fonts_nanum.patch - 03_locale_c.utf8.patch - 06_cross.patch - CVE-2016-5384.patch Changelog entries since current focal version 2.13.1-2ubuntu2: fontconfig (2.13.1-3) unstable; urgency=medium [ Laurent Bigonville ] * debian/rules: Stop looking for fonts in /usr/X11R6/lib/X11/fonts, nothing is installing fonts there for years and it's causing gnome-settings-daemon to check the location every few seconds (Closes: #568686) [ Fabian Greffrath ] * fontconfig-config: extend, clean-up and order fontconfig-config's font dependencies (Closes: #879503) [ Emilio Pozuelo Monfort ] * Split documentation into a -doc package to avoid multi-arch problems in the -dev one (Closes: #935760, #844607) * Since we're going through NEW, rename libfontconfig1-dev to libfontconfig-dev and provide the former. * Switch to debhelper-compat. -- Emilio Pozuelo Monfort Wed, 18 Mar 2020 00:56:46 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1870617 Title: Merge fontconfig 2.13.1-3 (main) from Debian unstable (main) Status in fontconfig package in Ubuntu: New Bug description: Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main) Sorry, I can't work on this merge myself. It fixes Debian bugs, especially this one https://bugs.debian.org/568686, which is related to performance, and they can be related to Ubuntu too. Explanation of the Ubuntu delta: * Really include the symbols file update * de
[Touch-packages] [Bug 1870746] Re: System froze during suspension since Linux kernel v5.3.0-42.
** 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/1870746 Title: System froze during suspension since Linux kernel v5.3.0-42. Status in xorg package in Ubuntu: New Bug description: Hello, I found that my system froze during the suspension process since Linux kernel v5.3.0-42. When the display switches to a blank terminal with a cursor on the top-left corner, the system got stuck. Sometimes I was able to switch to a virtual TTY with Control+Alt+[F2-F7], but it got stuck as well within a few seconds. Also, I've noticed that the backlight of my keyboard stays on indefinitely after the system froze, even though I've set a timeout for it to turn off. I've tried the ways to debug system crash mentioned in the Community Help Wiki, but with no luck. But it seems that I was able to connect to my computer via SSH if I was not connected to it before it froze, otherwise the SSH server will freeze as well. After some investigation, I found some information in "/var/log/syslog" that might be useful. I've found that "systemd- sleep[5261]: Suspending system..." was the last message that was logged to that file if the system froze, although there might be one more random or garbage message follow it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是個目錄: '/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 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 4 16:08:25 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-40-generic, x86_64: installed nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround (Update: Yes, if it's not too technical) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0922] Subsystem: Dell Device [1028:0922] InstallationDate: Installed on 2019-10-20 (166 days ago) InstallationMedia: Kubuntu 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 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=4ddf851b-8d25-493d-92b4-e10623bc1531 ro quiet splash nouveau.modeset=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/xorg/+bug/1870746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~to
[Touch-packages] [Bug 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
** Bug watch added: github.com/ibus/ibus/issues #2187 https://github.com/ibus/ibus/issues/2187 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2187 Importance: Unknown Status: Unknown -- 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/1864561 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event Status in ibus: Unknown Status in gtk+3.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1864561/+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 1870617] Re: Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)
** Description changed: Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main) Sorry, I can't work on this merge myself. It fixes Debian bugs, and they can be related to Ubuntu too. Explanation of the Ubuntu delta: - * Really include the symbols file update - * debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch: - - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings - which make autopkgtests fail - * Upload proposed patch from upstream bug #103652. If the fontconfig cache - was built on a system that has nanosecond timestamps and then later - transplanted to one that doesn't - for example by mksquashfs as part of a - live CD build - we consider the cache invalid and rebuild it during the - boot process. Depending on the fonts involved, this can take a significant - amount of time and potentially cause knock-on timeouts. The approach in - this patch is to ignore the nanosecond portion of the cache's value if we - get 0 when stat()ing the referenced directory, meaning it is considered - fresh if the rest of the timestamp matches. (LP: #1749546) - * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes: - - debian/source_fontconfig.py, debian/fontconfig.install: - + Install apport hook - - Add 03_prefer_dejavu.patch: - + Prefer DejaVu to Bitstream Vera - - Add 04_ubuntu_monospace_lcd_filter_conf.patch: - + Use legacy lcdfilter with smaller monospace fonts - - Add 05_ubuntu_add_antialiasing_confs.patch: - + Add config file for antialiasing - - Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy", - used in Ubuntu before upstream introduced "lcdlegacy" - - Add 07_no_bitmaps.patch: - + Install 70-no-bitmaps.conf - - Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates, - debian/fontconfig-config.config, and associatedpo files. - Modify debian/rules, debian/fontconfig-config.postinst, - debian/fontconfig-config.postrm, and debian/README.Debian. - + Don't provide debconf prompts - - Modify debian/rules, debian/fontconfig-config.install, - debian/fontconfig-config.links, debian/fontconfig-config.postrm, - and debian/fontconfig-udeb.install: - + Delay doing the transition from /etc to /usr - * New upstream release - * Refresh patches - * Update Ubuntu patches to use mode="append" and target="pattern" - (LP: #1192175) - * Drop patches applied in new release: - - 01_fonts_nanum.patch - - 03_locale_c.utf8.patch - - 06_cross.patch - - CVE-2016-5384.patch + * Really include the symbols file update + * debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch: + - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings + which make autopkgtests fail + * Upload proposed patch from upstream bug #103652. If the fontconfig + cache was built on a system that has nanosecond timestamps and then + later transplanted to one that doesn't - for example by mksquashfs as + part of a live CD build - we consider the cache invalid and rebuild it + during the boot process. Depending on the fonts involved, this can + take a significant amount of time and potentially cause knock-on + timeouts. The approach in this patch is to ignore the nanosecond + portion of the cache's value if we get 0 when stat()ing the referenced + directory, meaning it is considered fresh if the rest of the timestamp + matches. (LP: #1749546) + * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes: + - debian/source_fontconfig.py, debian/fontconfig.install: + + Install apport hook + - Add 03_prefer_dejavu.patch: + + Prefer DejaVu to Bitstream Vera + - Add 04_ubuntu_monospace_lcd_filter_conf.patch: + + Use legacy lcdfilter with smaller monospace fonts + - Add 05_ubuntu_add_antialiasing_confs.patch: + + Add config file for antialiasing + - Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy", + used in Ubuntu before upstream introduced "lcdlegacy" + - Add 07_no_bitmaps.patch: + + Install 70-no-bitmaps.conf + - Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates, + debian/fontconfig-config.config, and associatedpo files. + Modify debian/rules, debian/fontconfig-config.postinst, + debian/fontconfig-config.postrm, and debian/README.Debian. + + Don't provide debconf prompts + - Modify debian/rules, debian/fontconfig-config.install, + debian/fontconfig-config.links, debian/fontconfig-config.postrm, + and debian/fontconfig-udeb.install: + + Delay doing the transition from /etc to /usr + * New upstream release + * Refresh patches + * Update Ubuntu patches to use mode="append" and target="pattern" + (LP: #1192175) + * Drop patches applied in new release: + - 01_fonts_nanum.patc
[Touch-packages] [Bug 1870746] [NEW] System froze during suspension since Linux kernel v5.3.0-42.
You have been subscribed to a public bug: Hello, I found that my system froze during the suspension process since Linux kernel v5.3.0-42. When the display switches to a blank terminal with a cursor on the top- left corner, the system got stuck. Sometimes I was able to switch to a virtual TTY with Control+Alt+[F2-F7], but it got stuck as well within a few seconds. Also, I've noticed that the backlight of my keyboard stays on indefinitely after the system froze, even though I've set a timeout for it to turn off. I've tried the ways to debug system crash mentioned in the Community Help Wiki, but with no luck. But it seems that I was able to connect to my computer via SSH if I was not connected to it before it froze, otherwise the SSH server will freeze as well. After some investigation, I found some information in "/var/log/syslog" that might be useful. I've found that "systemd-sleep[5261]: Suspending system..." was the last message that was logged to that file if the system froze, although there might be one more random or garbage message follow it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是個目錄: '/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 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 4 16:08:25 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-40-generic, x86_64: installed nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround (Update: Yes, if it's not too technical) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0922] Subsystem: Dell Device [1028:0922] InstallationDate: Installed on 2019-10-20 (166 days ago) InstallationMedia: Kubuntu 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 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=4ddf851b-8d25-493d-92b4-e10623bc1531 ro quiet splash nouveau.modeset=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan fonts kubuntu ubuntu -- System froze during suspension since Linux kernel v5.3.0-42. https://bugs.launchpad.net/bugs/1870746 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 1829297] Re: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()
Called upstream's attention to this via: https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1829297 Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get() Status in ibus package in Ubuntu: New Bug description: browser reading and listening to a yutube-stream, suddeny this bug message pops up ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-50.54-lowlatency 4.15.18 Uname: Linux 4.15.0-50-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Wed May 15 23:10:18 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2018-08-08 (280 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 SegvAnalysis: Segfault happened at: 0x7f550a55f207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f550a55f207) ok source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: tcache_get (tc_idx=2) at malloc.c:2943 __GI___libc_malloc (bytes=48) at malloc.c:3050 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcConfigParseAndLoad () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom colord crontab daemon dialout dip disk fax floppy games geoclue gnats input irc kmem lightdm list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl scanner shadow src ssh ssl-cert staff sudo sys tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1829297/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
Called upstream's attention to this via: https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1869484 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold() Status in ibus package in Ubuntu: Incomplete Bug description: i don't know what's happened ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 23:00:56 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 InstallationDate: Installed on 2018-08-07 (598 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1843958] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
Called upstream's attention to this via: https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1843958 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() Status in ibus package in Ubuntu: New Bug description: I was adding a new user in system settings in the liveusb version of Ubuntu 19.10 alpha when the error message appeared bellow the other windows. I didn't notice anything crashing, AFAICR ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 13 22:16:39 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fac162ecf3e :movl $0xfbad8004,0x20(%rsp) PC (0x7fac162ecf3e) ok source "$0xfbad8004" ok destination "0x20(%rsp)" (0x7ffdf646afd0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843958/+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 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()
Called upstream's attention to this via: https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870747 Title: ibus-ui-gtk3 crashed with SIGABRT in raise() Status in ibus package in Ubuntu: New Bug description: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:27:38 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870747/+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 1843195] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
Called upstream's attention to this via: https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1843195 Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal() Status in ibus package in Ubuntu: New Bug description: switch user not working. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 2 18:03:59 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 , ap=0x7ffe1ea7fc20, mode_flags=2) at vfprintf-internal.c:1289 __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, mode_flags=) at ../libio/libioP.h:947 Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843195/+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 1843195] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1843195 Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal() Status in ibus package in Ubuntu: New Bug description: switch user not working. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 2 18:03:59 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 , ap=0x7ffe1ea7fc20, mode_flags=2) at vfprintf-internal.c:1289 __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, mode_flags=) at ../libio/libioP.h:947 Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843195/+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 1829297] Re: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1829297 Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get() Status in ibus package in Ubuntu: New Bug description: browser reading and listening to a yutube-stream, suddeny this bug message pops up ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-50.54-lowlatency 4.15.18 Uname: Linux 4.15.0-50-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Wed May 15 23:10:18 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2018-08-08 (280 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 SegvAnalysis: Segfault happened at: 0x7f550a55f207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f550a55f207) ok source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: tcache_get (tc_idx=2) at malloc.c:2943 __GI___libc_malloc (bytes=48) at malloc.c:3050 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 FcConfigParseAndLoad () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom colord crontab daemon dialout dip disk fax floppy games geoclue gnats input irc kmem lightdm list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl scanner shadow src ssh ssl-cert staff sudo sys tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1829297/+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 1843958] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1843958 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() Status in ibus package in Ubuntu: New Bug description: I was adding a new user in system settings in the liveusb version of Ubuntu 19.10 alpha when the error message appeared bellow the other windows. I didn't notice anything crashing, AFAICR ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 13 22:16:39 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fac162ecf3e :movl $0xfbad8004,0x20(%rsp) PC (0x7fac162ecf3e) ok source "$0xfbad8004" ok destination "0x20(%rsp)" (0x7ffdf646afd0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843958/+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 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870747 Title: ibus-ui-gtk3 crashed with SIGABRT in raise() Status in ibus package in Ubuntu: New Bug description: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:27:38 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870747/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Kai Heng Feng, Thank you very much for quick reply. I upgrade kernel from your link. However still same issue. Please see the attachment. Best regards, Phuc Minh Cai ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5346246/+files/prevboot.txt -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 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 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/linux/+bug/1860754/+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 1870748] Re: Authentication Window Stays Open
I attempted to make a change to a repository by launching Software & Updates and editing an unselected package from eoan to fossa - the authentication window persisted at the top left of my screen throughout - even after entering my credentials in the central authentication window that popped up (and went as normal) -- 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/1870748 Title: Authentication Window Stays Open Status in software-properties package in Ubuntu: New Bug description: I left the Beta of Focal Fossa running overnight and when I logged in this morning, I found an open Authentication window with the message "To change software repository settings, you need to authenticate" (see attached screenshot). I enter my password and the password field grey out. The window stays persistent but is "invisible" to the mouse - i.e. if I click anywhere in it, it actually clicks the thing behind it. The Cancel button does nothing. I had this same issue yesterday when actually running Software & Updates. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:55:33 2020 InstallationDate: Installed on 2020-01-24 (70 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870748/+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 1870748] [NEW] Authentication Window Stays Open
Public bug reported: I left the Beta of Focal Fossa running overnight and when I logged in this morning, I found an open Authentication window with the message "To change software repository settings, you need to authenticate" (see attached screenshot). I enter my password and the password field grey out. The window stays persistent but is "invisible" to the mouse - i.e. if I click anywhere in it, it actually clicks the thing behind it. The Cancel button does nothing. I had this same issue yesterday when actually running Software & Updates. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:55:33 2020 InstallationDate: Installed on 2020-01-24 (70 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of persistent Software & Updates authentication window" https://bugs.launchpad.net/bugs/1870748/+attachment/5346150/+files/Screenshot%20from%202020-04-04%2009-58-06.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1870748 Title: Authentication Window Stays Open Status in software-properties package in Ubuntu: New Bug description: I left the Beta of Focal Fossa running overnight and when I logged in this morning, I found an open Authentication window with the message "To change software repository settings, you need to authenticate" (see attached screenshot). I enter my password and the password field grey out. The window stays persistent but is "invisible" to the mouse - i.e. if I click anywhere in it, it actually clicks the thing behind it. The Cancel button does nothing. I had this same issue yesterday when actually running Software & Updates. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:55:33 2020 InstallationDate: Installed on 2020-01-24 (70 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870748/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I have exactly the same problem on a Samsung Galaxy Flex Book. Headphones are working with the following options snd-hda-intel model=mono-speakers Speakers do not work. -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[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.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822482 seems also to be related. -- 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 : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1870550] Re: PCI/internal sound card not detected
Hey Hui, Thank you for looking into this! It's unfortunate but installing that kernel didn't fix the problem, I've attached the dmesg output to this email. I will also mention this may be part of a bigger bug, as I cannot change my brightness either (assuming display driver issue here too, also tried many fixes online didn't change anything) ALSO, my mic doesn't work as well (assuming same as the sound card driver issues) and, sometimes when I start my computer the wifi adaptor is not detected (to fix this I just have to restart again and it works) Thank you so much for looking into this, as it definitely hinders my ability to do my work. Regards, Eric On Sat, Apr 4, 2020 at 11:50 AM Hui Wang wrote: > https://people.canonical.com/~hwang4/testdsp/ please test this kernel. > if it doesn't help. please upload a dmesg with that kernel. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1870550 > > Title: > PCI/internal sound card not detected > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > The sound card is not detected on my machine > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 > Uname: Linux 5.3.0-45-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 4 00:51:33 2020 > InstallationDate: Installed on 2020-02-25 (37 days ago) > InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 > (20200203.1) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Title: PCI/internal sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/02/2020 > dmi.bios.vendor: AMI > dmi.bios.version: F.13 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.46 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx > dmi.product.sku: 8UR41PA#ABG > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870550/+subscriptions > ** Attachment added: "dmesg_out.txt" https://bugs.launchpad.net/bugs/1870550/+attachment/5346073/+files/dmesg_out.txt -- 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/1870550 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The sound card is not detected on my machine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 00:51:33 2020 InstallationDate: Installed on 2020-02-25 (37 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2020 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.46 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8UR41PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870550/+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 1870740] [NEW] Refresh Rate
Public bug reported: Hi.After i installed my video card i did some display changes like Scale and Refresh Rate.After i changed Refresh Rate from 30 to 50 & 59 it crush .I reinstalled 3 times ubuntu because my monitor was no signal receive from I use Samsung Led TV with 60 Hz Refresh Rate.Sorry from my english ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 11:06:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] [1462:3160] InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=b8f882ee-4da2-404b-b880-6142322cc80d ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P.50 dmi.board.asset.tag: Default string dmi.board.name: X99A RAIDER (MS-7885) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP.50:bd07/19/2016:svnMSI:pnMS-7885:pvr5.0:rvnMSI:rnX99ARAIDER(MS-7885):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.sku: Default string dmi.product.version: 5.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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 -- 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/1870740 Title: Refresh Rate Status in xorg package in Ubuntu: New Bug description: Hi.After i installed my video card i did some display changes like Scale and Refresh Rate.After i changed Refresh Rate from 30 to 50 & 59 it crush .I reinstalled 3 times ubuntu because my monitor was no signal receive from I use Samsung Led TV with 60 Hz Refresh Rate.Sorry from my english ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 11:06:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (
[Touch-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Yes, please test https://people.canonical.com/~khfeng/lp1860754-2/ -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 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 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/linux/+bug/1860754/+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
