[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Seyeong Kim]

Hello

I've verified this -proposed pkg on my local.

#2 on description working fine.

xtrusia@ubuntu:~$ dpkg -l | grep network-manager
ii  network-manager1.10.6-2ubuntu1.4
   amd64network management framework (daemon and userspace 
tools)
ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1.2
   all  NetworkManager configuration to enable connectivity 
checking
ii  network-manager-gnome  1.8.10-2ubuntu3  
   amd64network management framework (GNOME frontend)
ii  network-manager-pptp   1.2.6-1  
   amd64network management framework (PPTP plugin core)
ii  network-manager-pptp-gnome 1.2.6-1  
   amd64network management framework (PPTP plugin GNOME GUI)


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
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/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 au

[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Christian Ehrhardt ]

Merge Proposal review is complete, but waiting on some feedback that
helps to classify the severity and urgency correctly.

Depending on that the options will be:
- actually unimportant: don't SRU it at all
- some reasonable cases exists, but are very rare: SRU it but hold the release 
in block-proposed until the next "important" update comes
- reasonable case for the Ubuntu community, SRU right away

Setting the task to incomplete while waiting on that feedback

** Changed in: openssh (Ubuntu Bionic)
   Status: Triaged => Incomplete

-- 
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/1863930

Title:
  SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * The version check in ssh was broken no more following RFC 4253 and
     thereby denying some clients that it shouldn't

   * Upstream fixed that and this is backporting the changes to bionic.

  [Test Case]

   # Prep
   * configure the ssh server to generally work
   # Testcase
   $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
   $ apt install python3-paramiko
   $ python3 test_bug_1863930.py localhost (or whatever your host is)

   Will report "Server is not patched." or "Server is patched.

   * for an extra regression check it might be worth to do some "normal" ssh 
 connections as well

  [Regression Potential]

   * The change is very small and reviewable as well as being upstream and 
 in all Ubuntu releases >=Cosmic for a while now so it seems safe.
 If anything the kind of regression to expect is that some former 
 (wrong) connection denials will then succeed. I can only think of
 that being an issue in test suites but not in the real world.

  [Other Info]

   * n/a

  --

  SSHD closes the connection and logs the error message below when a
  client presents a protoversion of "1.99":

  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX

  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat
  it as "2.0".

  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1865906] Re: software-properties-* import key issue

[Walter Lapchynski]

** No longer affects: lubuntu-meta (Ubuntu)

-- 
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/1865906

Title:
  software-properties-* import key issue

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  My system: Lubuntu 19.04 run from Live-CD (from the original ISO
  image)

  
  Note: Followig issue apply to both software-properties: Qt and KDE run from 
LiveCD.

  After opening thru the console (as root) the software-properties,
  switching to the "Authentication" tab and pressing the "Import key
  file", I recieve following error output:

  # software-properties-qt

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Trackback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 712, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  =

  same happens with software-properties-kde.

  When I'm trying to check their version, I'll get following output:

  # software-properties-qt -v

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
  root'

  software-properties-qt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1865906/+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 1865906] Re: software-properties-* import key issue

[Michal Dziczkowski]

@Chris Guiver (guiverc): After opening in the terminal (as root) the
given by you command, I had received a authorization link to Launchpad.
After opening it (I was already logged in into my account), I saw the
Launchpad page with following message:

The information on this page is private.

Michal Dziczkowski (mdziczkowski) •

Launchpad.net

Not allowed here

Sorry, you don't have permission to access this page or the information
in this page is not shared with you.

You are logged in as Michal Dziczkowski.

==

Please fix it asap, else I won't be able to send the required
information's from apport

-- 
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/1865906

Title:
  software-properties-* import key issue

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  My system: Lubuntu 19.04 run from Live-CD (from the original ISO
  image)

  
  Note: Followig issue apply to both software-properties: Qt and KDE run from 
LiveCD.

  After opening thru the console (as root) the software-properties,
  switching to the "Authentication" tab and pressing the "Import key
  file", I recieve following error output:

  # software-properties-qt

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Trackback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 712, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  =

  same happens with software-properties-kde.

  When I'm trying to check their version, I'll get following output:

  # software-properties-qt -v

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
  root'

  software-properties-qt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865906/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Kai-Heng Feng]

Please file an upstream bug at intel graphics upstream:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs

-- 
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/1767654

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1865906] Re: software-properties-* import key issue

[Chris Guiver]

Also note, if you do test in Lubuntu 19.10, you should also please
execute the following command only once, as it will automatically gather
debugging information, in a terminal:

apport-collect 1865906

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

-- 
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/1865906

Title:
  software-properties-* import key issue

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  My system: Lubuntu 19.04 run from Live-CD (from the original ISO
  image)

  
  Note: Followig issue apply to both software-properties: Qt and KDE run from 
LiveCD.

  After opening thru the console (as root) the software-properties,
  switching to the "Authentication" tab and pressing the "Import key
  file", I recieve following error output:

  # software-properties-qt

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Trackback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 712, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  =

  same happens with software-properties-kde.

  When I'm trying to check their version, I'll get following output:

  # software-properties-qt -v

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
  root'

  software-properties-qt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865906/+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 1865906] Re: software-properties-* import key issue

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 19.04 (disco) and all flavors reached end-of-life on January 23,
2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu/Lubuntu version and re-test. If you then find the bug is
still present in the newer Ubuntu version, please add a comment here
telling us which new version it is in and change the bug status to
Confirmed.

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Incomplete

-- 
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/1865906

Title:
  software-properties-* import key issue

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  My system: Lubuntu 19.04 run from Live-CD (from the original ISO
  image)

  
  Note: Followig issue apply to both software-properties: Qt and KDE run from 
LiveCD.

  After opening thru the console (as root) the software-properties,
  switching to the "Authentication" tab and pressing the "Import key
  file", I recieve following error output:

  # software-properties-qt

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Trackback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 712, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  =

  same happens with software-properties-kde.

  When I'm trying to check their version, I'll get following output:

  # software-properties-qt -v

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
  root'

  software-properties-qt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865906/+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 1865906] Re: software-properties-* import key issue

[Dan Simmons]

Thank you for taking the time to report this bug. It should be noted
that 19.04 is an EOL release for Lubuntu. I am however able to confirm
the same behavior in both Lubuntu 19.10 and 20.04 development release
installed from 20200303 daily media.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

-- 
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/1865906

Title:
  software-properties-* import key issue

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  My system: Lubuntu 19.04 run from Live-CD (from the original ISO
  image)

  
  Note: Followig issue apply to both software-properties: Qt and KDE run from 
LiveCD.

  After opening thru the console (as root) the software-properties,
  switching to the "Authentication" tab and pressing the "Import key
  file", I recieve following error output:

  # software-properties-qt

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Trackback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 712, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  =

  same happens with software-properties-kde.

  When I'm trying to check their version, I'll get following output:

  # software-properties-qt -v

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
  root'

  software-properties-qt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865906/+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 1865906] Re: software-properties-* import key issue

[Dan Simmons]

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1865906

Title:
  software-properties-* import key issue

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  My system: Lubuntu 19.04 run from Live-CD (from the original ISO
  image)

  
  Note: Followig issue apply to both software-properties: Qt and KDE run from 
LiveCD.

  After opening thru the console (as root) the software-properties,
  switching to the "Authentication" tab and pressing the "Import key
  file", I recieve following error output:

  # software-properties-qt

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Trackback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 712, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  =

  same happens with software-properties-kde.

  When I'm trying to check their version, I'll get following output:

  # software-properties-qt -v

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
  root'

  software-properties-qt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865906/+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 1780680] Re: Older version in bionic than in xenial

[Andy Whitcroft]

** Changed in: linux-meta-azure (Ubuntu)
   Status: New => Fix Released

** Changed in: linux-meta-gcp (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780680

Title:
  Older version in bionic than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  Won't Fix
Status in libdrm package in Ubuntu:
  Won't Fix
Status in linux-meta-azure package in Ubuntu:
  Fix Released
Status in linux-meta-gcp package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Won't Fix
Status in patch package in Ubuntu:
  Invalid
Status in python-pyvmomi package in Ubuntu:
  Invalid
Status in snapcraft package in Ubuntu:
  Fix Released
Status in wireless-regdb package in Ubuntu:
  Fix Released

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+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 1865907] Re: Loading IM context type 'ibus' failed

[liufeng4080]

Symptom unreproducible after glib upgraded to proposed libglib2.0-0
/focal-proposed,now 2.64.0-1 amd64 [installed].

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1865907

Title:
  Loading IM context type 'ibus' failed

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Regression issue caused by recent system updates on Ubuntu 20.04 Focal
  Fossa (development branch)

  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...

  and Pinyin input method does not work in these applications.

  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0

  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

[Egmont Koblinger]

> It appears we would need a new upstream bug to track this because the
old one didn't go anywhere.

This is not true. The old one did go somewhere: It examined the behavior
and clearly concluded that upstream gnome-terminal is NOT buggy here, it
never was. It's one of the Ubuntu patches that introduces the bug. This
conclusion was also stated in this thread here.

Could you please clarify how you expect upstream gnome-terminal to fix
this situation?

Meanwhile, this bug is almost 3 years old, and I haven't seen any
worthwile comment from any Ubuntu developer trying to track down which
of its patches, and which part within that is the culprit.

Or if you believe that upstream gnome-terminal is indeed buggy, this bug
just doesn't happen to trigger anywhere else, except with your perfect
innocent patches, then this claim should be justified with technical
arguments, something I haven't seen in this thread yet.

And I can't help to notice that this is not the only issue where Ubuntu
introduces a regression to the overall gnome-terminal user experience,
and then really doesn't care about fixing it. Bug 1770507 is another
prominent example, you guys broke something during the feature freeze
period(!) of the previous LTS, and still til this day haven't cared
about fixing.

I'm sad and disappointed to see that the software I've been co-
developing for years, putting my passion, heart, and lots and lots of
time into, is broken in multiple ways by perhaps the most popular Linux
distribution, and its developers just don't care. I don't even know what
to think about you pointing fingers at us.

Instead, maybe could you Ubuntu devs finally please, pretty please get
yourself together and fix at the very least these two bugs that YOU
introduced, in time for the just-around-the-corner LTS release? If
simply by dropping the patches that introduces the bugs, along with then
dropping whatever features those patches add, so it be. Thanks!

I firmly believe that Ubuntu should revise its bug prioritizing policy,
and handle with much-much higher priority if one of its changes
introduces a regression from mainstream. It should be something like: if
a regression is found, and not fixed within a week, the patch is
automatically dropped. Think about it...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1691678

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1797678] Re: Printing stops with Status as "Idle - Filter failed"

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cups (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1797678

Title:
  Printing stops with Status as "Idle - Filter failed"

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This happened after an upgrade from Xenial to Bionic on this Barebones PC. 
Interestingly after an upgrade from Xenial to Bionic on a Laptop this problem 
did not occur. It also occurred with a clean install on another Barebones PC, 
but was fixed by installing package hplip. I've tried installing hplip on this 
PC but to no effect.
  PS I don't know if the problem is with CUPS or hplip or another package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 13 09:10:56 2018
  InstallationDate: Installed on 2018-02-09 (245 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat:
   device for Deskjet_2540_series_527711_: 
ipp://HPD0BF9C527711.local:631/ipp/print
   device for HP-Deskjet-2540-series: 
dnssd://Deskjet%202540%20series%20%5B527711%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9c527711
   device for Samsung-SCX-472x: socket://192.168.101.20:9100
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_2540_series_527711_.ppd', 
'/etc/cups/ppd/Samsung-SCX-472x.ppd', 
'/etc/cups/ppd/HP-Deskjet-2540-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Deskjet_2540_series_527711_.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung-SCX-472x.ppd: Permission denied
   grep: /etc/cups/ppd/HP-Deskjet-2540-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=f83725aa-582a-4c36-9ad8-738122da2e0c ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-07 (5 days ago)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797678/+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 1796948] Re: cups gives back "filter failed" for all trials to print to any printer

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cups (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1796948

Title:
  cups gives back "filter failed" for all trials to print to any printer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Any printing attempt to any printer is quitted with "filter failed" by
  cups. Even for test pages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
  Uname: Linux 4.15.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Tue Oct  9 20:21:26 2018
  InstallationDate: Installed on 2011-10-19 (2546 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Lpstat:
   device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100
   device for PDF: cups-pdf:/
   device for Roger-Router-Fax: roger-cups:/
  MachineType: Acer TravelMate P643-M
  Papersize: a4
  PpdFiles:
   Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1
   Roger-Router-Fax: roger fax printer, 1.0
   PDF: Generic CUPS-PDF Printer
   Kyocera_FS-1300D: Kyocera FS-1300D (KPDL)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic 
root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios 
ipv6.disable=1 vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer
  mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1796948/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

[Dimitri John Ledkov]

I've now opened upstream issues about this on the OpenSSL bug tracker.

However, todoodle.com could refresh their certificate chain with an up
to date G2 godaddy SSL certificate chain, instead of the one that ends
on a CA Root certificate which is no longer trustworthy.

** Changed in: openssl (Ubuntu)
   Importance: Undecided => Low

** Changed in: openssl (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/";)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  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: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

[Dimitri John Ledkov]

** Bug watch added: github.com/openssl/openssl/issues #11236
   https://github.com/openssl/openssl/issues/11236

** Also affects: openssl via
   https://github.com/openssl/openssl/issues/11236
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/";)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  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: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

[Dimitri John Ledkov]

So, in their chain of certs that they present there is still an RSA-SHA1
certificate. It shouldn't affect validation, as the other certs in the
chain are sufficient (for example gnutls-cli toodledo.com connects fine)
but it does trip up openssl:

- Certificate[3] info:
 - subject `OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group\, 
Inc.,C=US', issuer `OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy 
Group\, Inc.,C=US', serial 0x00, RSA key 2048 bits, signed using RSA-SHA1 
(broken!), activated `2004-06-29 17:06:20 UTC', expires `2034-06-29 17:06:20 
UTC', pin-sha256="VjLZe/p3W/PJnd6lL8JVNBCGQBZynFLdZSTIqcO0SJ8="

Now, they could remove that cert from the chain that their server uses.
But also they should not need to do this and openssl should just work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/";)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  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: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

[Dimitri John Ledkov]

Lifetimes of more than a year is only implemented by Apple on their
products. Longevity of the certifications do not matter on Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/";)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  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: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Salvatore]

I confirm the bug
The bug applies to all the distros I have tried:
Ubuntu; Linux Mint; Manjaro; Fedora; Opensuse etc.
I also tried various DEs: Kde, Gnome, Cinnamon, Xfce, Mate etc.
It's a general problem, not just of mutter and Gnome
The bug exists only with Mesa and Modesetting, if you install xf86-video-intel 
(Arch and Manjaro), the mouse does not lock but the mouse flashes and multiplies
Also, when there is a lock, I noticed that the left side of the screen 
"unlocks", but the mouse starts flashing (with Mesa and Modesetting)
It happens especially when I watch videos in full screen or at 60fps on Youtube

Intel Celeron J3160, with Hdmi (I can't try with VGA)

Edit: yesterday I tried to download and boot through USB Ubuntu 14.04.6
unity 64 bit ... and surprise: the problem does not exist

-- 
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/1767654

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1865907] Re: Loading IM context type 'ibus' failed

[Gunnar Hjalmarsson]

Thanks for your report! I could reproduce the problem, which is a bit
weird because IBus was updated yesterday and the IBus input methods I
tested worked fine then...

Anyway, I see in the error message: "GLib version too old". So I
upgraded the libglib2.0-* packages to version 2.64.0-1 (from focal-
proposed) and that fixed the issue.

So it looks like we just need to be patient and wait for libglib2.0-* to
migrate to focal-release.

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: ibus (Ubuntu)
   Importance: Undecided => High

** Changed in: ibus (Ubuntu)
   Status: New => Confirmed

-- 
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/1865907

Title:
  Loading IM context type 'ibus' failed

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Regression issue caused by recent system updates on Ubuntu 20.04 Focal
  Fossa (development branch)

  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...

  and Pinyin input method does not work in these applications.

  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0

  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+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 1865907] Re: Loading IM context type 'ibus' failed

[liufeng4080]

** Description changed:

+ Regression issue caused by recent system updates on Ubuntu 20.04 Focal
+ Fossa (development branch)
+ 
  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...
  
  and Pinyin input method does not work in these applications.
  
  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0
  
- 
  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

-- 
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/1865907

Title:
  Loading IM context type 'ibus' failed

Status in ibus package in Ubuntu:
  New

Bug description:
  Regression issue caused by recent system updates on Ubuntu 20.04 Focal
  Fossa (development branch)

  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...

  and Pinyin input method does not work in these applications.

  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0

  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865907/+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 1865907] [NEW] Loading IM context type 'ibus' failed

[liufeng4080]

Public bug reported:

Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
...
(lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
(lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
...

and Pinyin input method does not work in these applications.

Symptom occurs since I updated below 17 packages some hours before,
gir1.2-ibus-1.0
gvfs
gvfs-backends
gvfs-bin
gvfs-common
gvfs-daemons
gvfs-fuse
gvfs-libs
ibus
ibus-data
ibus-gtk
ibus-gtk3
libglib2.0-0
libgtk-3-0
libgtk2.0-0
libibus-1.0-5
python3-ibus-1.0


current versions of above packages are,
gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]

** Affects: ibus (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1865907

Title:
  Loading IM context type 'ibus' failed

Status in ibus package in Ubuntu:
  New

Bug description:
  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...

  and Pinyin input method does not work in these applications.

  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0


  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1865907/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Doug Smythies]

For what it's worth, the versions of things in my test computers, all
servers, no GUI:

name: serv-ff (a 20.04 VM, that has not had an update since around February 
12th):
initramfs-tools: 0.133ubuntu14
kmod; 26-3ubuntu1

name: s18 (a physical i5-9600K based computer, up to date as of a few days ago):
initramfs-tools: 0.136ubuntu1
kmod; 27-1ubuntu1

name: s15 (a physical i7-2600K based computer, up to date as of a few days ago):
initramfs-tools: 0.136ubuntu1
kmod; 27-1ubuntu1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864992

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 461260] Re: No sound was heard when running System Testing on a new Intel Apple iMac

[Andy Whitcroft]

** Changed in: linux-backports-modules-2.6.31 (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
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/461260

Title:
  No sound was heard when running System Testing on a new Intel Apple
  iMac

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-backports-modules-2.6.31 package in Ubuntu:
  Won't Fix

Bug description:
  I preformed a new install, updated, and upgraded Karmic Beta on a new
  Intel Apple iMac. No non-free drivers are in use. I ran System Testing
  and heard no sound.

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scottmaccal   1690 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5060 irq 20'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,106b3c00,00100103'
 Controls  : 29
 Simple ctrls  : 15
  CheckboxCommand: alsa_record_playback
  CheckboxTest: alsa_record_playback_alternates
  Date: Mon Oct 26 13:16:59 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 
(20091020.3)
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/461260/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

[Gunnar Hjalmarsson]

@Marc: Please see my short conversation with Alex on IRC:

https://irclogs.ubuntu.com/2020/02/11/%23ubuntu-desktop.html

I will ask Laney about the current status.

-- 
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/1844853

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Fix Committed
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

[Marc Deslauriers]

Is anyone actively working on the glib2.0 SRUs? We are blocked on them
for our ibus security update...

-- 
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/1844853

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Fix Committed
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1794478] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/237-3ubuntu10.39 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#network-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [

[Touch-packages] [Bug 1850267] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/237-3ubuntu10.39 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#network-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/1850267

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1855009] Autopkgtest regression report (network-manager/1.10.6-2ubuntu1.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/237-3ubuntu10.39 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#network-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/1855009

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Fix Committed
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

[Daniel van Vugt]

It appears we would need a new upstream bug to track this because the
old one didn't go anywhere. Please create one in:

  https://gitlab.gnome.org/GNOME/gnome-terminal/issues

or

  https://gitlab.gnome.org/GNOME/gtk/issues

and then tell us the URL.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1691678

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()

[Gunnar Hjalmarsson]

On 2020-03-03 14:33, Mel wrote:
> Hi Gunnar have updated and no further crash reports
> On ibis

Great! Closing then. Please feel free to submit a new bug report would
the issue re-appear.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1865857

Title:
  ibus-x11 crashed with SIGABRT in __open_nocancel()

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  possible Xorg crashing

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.21-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
  Uname: Linux 5.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  2 16:24:27 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  ExecutableTimestamp: 1581612711
  InstallationDate: Installed on 2020-02-29 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcCwd: /home/mel
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) 
at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45
   __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, 
posix_mode=, prot=prot@entry=438, read_write=8, 
is32not64=) at fileops.c:186
   _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, 
filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, 
mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281
   __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 
"/etc/localtime") at iofopen.c:75
   _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", 
mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86
  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/1865857/+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 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()

[Mel]

Hi Gunnar have updated and no further crash reports
On ibis

Still dealing with previous bug on dual monitor login

I had this problem on  18.04 and found no resolve

-- 
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/1865857

Title:
  ibus-x11 crashed with SIGABRT in __open_nocancel()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  possible Xorg crashing

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.21-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
  Uname: Linux 5.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  2 16:24:27 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  ExecutableTimestamp: 1581612711
  InstallationDate: Installed on 2020-02-29 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcCwd: /home/mel
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) 
at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45
   __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, 
posix_mode=, prot=prot@entry=438, read_write=8, 
is32not64=) at fileops.c:186
   _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, 
filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, 
mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281
   __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 
"/etc/localtime") at iofopen.c:75
   _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", 
mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86
  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/1865857/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

[Volodymyr Felyk]

Please find some solution for this bug

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => Incomplete

** Changed in: linux (Ubuntu)
   Status: Expired => Incomplete

-- 
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/1856392

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 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=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

[Mohammad Anwar Shah]

What's the current status of this bug? Where is the fix? One of my
report is made duplicate to this bug but I think this is much older. I'm
using 19.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1691678

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Christian Ehrhardt ]

Autopkgtests are complete on the PPA at 
https://bileto.ubuntu.com/#/ticket/3962
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3962/+packages

Tests all passed or are known force-badtest cases already.

Waiting for Kyle's response to properly handle the severity of this ...

-- 
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/1863930

Title:
  SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * The version check in ssh was broken no more following RFC 4253 and
     thereby denying some clients that it shouldn't

   * Upstream fixed that and this is backporting the changes to bionic.

  [Test Case]

   # Prep
   * configure the ssh server to generally work
   # Testcase
   $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
   $ apt install python3-paramiko
   $ python3 test_bug_1863930.py localhost (or whatever your host is)

   Will report "Server is not patched." or "Server is patched.

   * for an extra regression check it might be worth to do some "normal" ssh 
 connections as well

  [Regression Potential]

   * The change is very small and reviewable as well as being upstream and 
 in all Ubuntu releases >=Cosmic for a while now so it seems safe.
 If anything the kind of regression to expect is that some former 
 (wrong) connection denials will then succeed. I can only think of
 that being an issue in test suites but not in the real world.

  [Other Info]

   * n/a

  --

  SSHD closes the connection and logs the error message below when a
  client presents a protoversion of "1.99":

  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX

  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat
  it as "2.0".

  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Released => 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/1865499

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()

[Gunnar Hjalmarsson]

IBus was recently upgraded to 1.5.22-1~exp1ubuntu1. Can you please
update the packages on your system (including IBus):

sudo apt update
sudo apt upgrade

and let us know if the issue is still present.

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

-- 
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/1865857

Title:
  ibus-x11 crashed with SIGABRT in __open_nocancel()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  possible Xorg crashing

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.21-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
  Uname: Linux 5.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  2 16:24:27 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  ExecutableTimestamp: 1581612711
  InstallationDate: Installed on 2020-02-29 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcCwd: /home/mel
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) 
at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45
   __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, 
posix_mode=, prot=prot@entry=438, read_write=8, 
is32not64=) at fileops.c:186
   _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, 
filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, 
mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281
   __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 
"/etc/localtime") at iofopen.c:75
   _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", 
mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86
  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/1865857/+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 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Mauricio Faria de Oliveira]

Setting the bug as Invalid; temporary issue on mirrors as initially
suspected.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863189

Title:
  package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I can't update my packages by using sudo apt-get update, because it fails to 
download some repositories. 
  (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease
  Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease
  Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB]
  Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB]
  Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 
[210 kB]
  Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 
[167 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata
  Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons
  Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons
  Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 
Metadata
  Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 
Icons
  Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 
Icons
  Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata
File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 
2801:82:80ff:8000::5 80]
Hashes of expected file:
 - Filesize:73000 [weak]
 - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3
 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak]
 - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak]
Release file created at: Thu, 13 Feb 2020 22:49:41 +
  Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons [9.954 B]
  Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons

  Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons [15,1 kB]
  Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons

  Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 
DEP-11 Metadata [26,2 kB]
  Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 
Metadata

  Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 
48x48 Icons [18,5 kB]
  Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 
Icons

  Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 
64x64 Icons [22,9 kB]
  Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 
Icons

  Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata [8.064 B]
  Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata
File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 
200.236.31.4 80]
Hashes of expected file:
 - Filesize:8064 [weak]
 - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e
 - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak]
 - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak]
Release file created at: Thu, 13 Feb 2020 22:50:01 +
  Baixados 186 kB em 4s (44,0 kB/s)   
  Lendo listas de pacotes... Pronto
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz
  File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 
2801:82:80ff:8000::5 80]
 Hashes of expected file:
  - Filesize:73000 [weak]
  - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3
  - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak]
  - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak]
 Release file created at: Thu, 13 Feb 2020 22:49:41 +
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz
  
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz
  
  E: Falhou ao buscar 
http://br.a

[Touch-packages] [Bug 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Mauricio Faria de Oliveira]

Obrigado por confirmar.

** Changed in: util-linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863189

Title:
  package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I can't update my packages by using sudo apt-get update, because it fails to 
download some repositories. 
  (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease
  Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease
  Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB]
  Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB]
  Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 
[210 kB]
  Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 
[167 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata
  Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons
  Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons
  Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 
Metadata
  Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 
Icons
  Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 
Icons
  Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata
File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 
2801:82:80ff:8000::5 80]
Hashes of expected file:
 - Filesize:73000 [weak]
 - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3
 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak]
 - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak]
Release file created at: Thu, 13 Feb 2020 22:49:41 +
  Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons [9.954 B]
  Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons

  Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons [15,1 kB]
  Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons

  Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 
DEP-11 Metadata [26,2 kB]
  Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 
Metadata

  Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 
48x48 Icons [18,5 kB]
  Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 
Icons

  Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 
64x64 Icons [22,9 kB]
  Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 
Icons

  Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata [8.064 B]
  Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata
File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 
200.236.31.4 80]
Hashes of expected file:
 - Filesize:8064 [weak]
 - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e
 - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak]
 - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak]
Release file created at: Thu, 13 Feb 2020 22:50:01 +
  Baixados 186 kB em 4s (44,0 kB/s)   
  Lendo listas de pacotes... Pronto
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz
  File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 
2801:82:80ff:8000::5 80]
 Hashes of expected file:
  - Filesize:73000 [weak]
  - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3
  - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak]
  - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak]
 Release file created at: Thu, 13 Feb 2020 22:49:41 +
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz
  
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz
  
  E: Falhou ao b

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Timo Denissen]

I tested all versions since 18.04 up to 20.04, in no live session I
could reproduce this problem. Yet this problem occurs in our
installations. The youngest installation is about three weeks old and
has the same bug.

Is there a way to end pulseaudio and prevent it from auto-restarting, so
I can try and get some debug from "pulseaudio -vvv"? Killing the process
with kill/pkill, or with "pulseaudio --kill" restarts it immediately.

Attached is the output to syslog when dis- and reconnectiong the USB
headset.

** Attachment added: "pulseaudio_syslog"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+attachment/5333028/+files/pulseaudio_syslog

-- 
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/1865499

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1833116] Re: chtmax98090 not working out of the box

[Jaime Pérez]

https://bugzilla.kernel.org/show_bug.cgi?id=201787#c14

Bug is only "fixed" for Swanky and Gnawty chromebooks. They are marked
to use a quirk, as an update breaks sound. To get a fix you should
contact with Hans de Goede (you can in bugzilla) and ask for a fix.

-- 
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/1833116

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1833116] Re: chtmax98090 not working out of the box

[greensysadmin]

Attached is the output of the crashlog from 20.04 after applying the git
settings as detailed in the OP and rebooting - Pulseaudio seems to be
crashing.

** Attachment added: "_usr_bin_pulseaudio.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+attachment/5333027/+files/_usr_bin_pulseaudio.1000.crash

-- 
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/1833116

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

At that time .. kmod was 26+20191223-1ubuntu1, now kmod is
27-1ubuntu1... Will check if something happened in that upgrade that
made the mkinitramfs change buggy OR its something that was never
covered.

** Changed in: kmod (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: kmod (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864992

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More hel

[Touch-packages] [Bug 1865857] Re: ibus-x11 crashed with SIGABRT in __open_nocancel()

[Gunnar Hjalmarsson]

** 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/1865857

Title:
  ibus-x11 crashed with SIGABRT in __open_nocancel()

Status in ibus package in Ubuntu:
  New

Bug description:
  possible Xorg crashing

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.21-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
  Uname: Linux 5.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  2 16:24:27 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  ExecutableTimestamp: 1581612711
  InstallationDate: Installed on 2020-02-29 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcCwd: /home/mel
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   __GI___open64_nocancel (file=0x7fd6e8f24988 "/etc/localtime", oflag=524288) 
at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45
   __GI__IO_file_open (fp=fp@entry=0x558b12a50010, filename=, 
posix_mode=, prot=prot@entry=438, read_write=8, 
is32not64=) at fileops.c:186
   _IO_new_file_fopen (fp=fp@entry=0x558b12a50010, 
filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", mode=, 
mode@entry=0x7fd6e8f22fde "rce", is32not64=is32not64@entry=1) at fileops.c:281
   __fopen_internal (is32=1, mode=0x7fd6e8f22fde "rce", filename=0x7fd6e8f24988 
"/etc/localtime") at iofopen.c:75
   _IO_new_fopen (filename=filename@entry=0x7fd6e8f24988 "/etc/localtime", 
mode=mode@entry=0x7fd6e8f22fde "rce") at iofopen.c:86
  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/1865857/+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 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file

[Rafael David Tinoco]

*** This bug is a duplicate of bug 1864992 ***
https://bugs.launchpad.net/bugs/1864992

** This bug has been marked a duplicate of bug 1864992
   depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864436

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  linux Ubuntu 5.4.0-14.17-generic 5.4.18
  linux-modules-5.4.0-15-generic 5.4.0-15.18

  Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated 
error messages:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864436/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

@dsmythies, @kaihengfeng

you seem to be correct.

First time I saw that issue was in a kmod regression test iirc.

The fix was supposed to be in:

initramfs-tools (0.133ubuntu15) focal; urgency=medium

from:

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

but I see now that might not cover all cases.

I'll revisit this today.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864992

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864992

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1864992/+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 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file

[Rafael David Tinoco]

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864436

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  linux Ubuntu 5.4.0-14.17-generic 5.4.18
  linux-modules-5.4.0-15-generic 5.4.0-15.18

  Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated 
error messages:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864436/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported

[Jeff Lane]

** Tags removed: hwcert-server

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1089389

Title:
  juju bootstrap fail behind a proxy when a gpg key must be imported

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  This is related to a Maas environment hosted behind a proxy.

  I'm trying to use
  juju 0.6.0.1+bzr603-0juju1~precise1

  ubuntu@maas:~$ cat .juju/environments.yaml
  environments:
    mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa

  When juju boostrap, things do not behave as expected on the zookeeper
  node.

  Excerpt from the cloud-init-output.log:

  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not
  available: NO_PUBKEY 376A290EC8068B11

  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:

  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0

  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created
  gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created
  gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
  gpg: Total number processed: 1
  gpg: imported: 1 (RSA: 1)
  OK
  ubuntu@zookeeper:/var/log$ echo $?
  0

  On the zookeeper node, python-software-properties is version 0.82.7.3

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Dec 12 14:40:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Timo Denissen]

Got feedback from one of my colleagues that running Ubuntu 18.04.4 with
Kernel 5.3.0-40, "pkill -U $USER pulseaudio" does not resolve the
problem, only a full restart of the system.

Is there anything I can do to provide additional logs? Running a
debugger when plugging in the headset, logfiles with a specific log
level?

-- 
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/1865499

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

Thanks. If you can then please also try Ubuntu 19.10
(https://ubuntu.com/download/desktop) so we can get a slightly better
idea of which PulseAudio version introduced the fix.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Timo Denissen]

Just tested with Ubuntu 20.04, the problem does not occur in the live
session.

-- 
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/1865499

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1865499/+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 1855009] Re: autopkgtests all fail on s390x

[Łukasz Zemczak]

Hello Dan, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
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/1855009

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Fix Committed
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Łukasz Zemczak]

Hello bugproxy, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: network-manager (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
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/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv

[Touch-packages] [Bug 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq

[Łukasz Zemczak]

Hello Dan, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
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/1850267

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1865645] Re: its crash sometimes and its hang

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: xorg (Ubuntu)
   Status: New => Won't Fix

-- 
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/1865645

Title:
  its crash sometimes and its hang

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  its crash sometimes and its hang

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 04:50:48 2020
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:827e]
  InstallationDate: Installed on 2019-06-24 (252 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 
G3/G4/SE9 G2
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ac0XX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=eee03b6e-c69f-4398-9f52-40b9ef9cdb67 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.54
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
  dmi.product.sku: Y4P52AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1865645/+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 1865517] Re: cannot log in with long username

[Jo K]

Nothing but i misexplained, bug isn't related to the fact that account exists 
or not.
Please try to enter in a tty that exact login :

'username.lastnamelastnamelastn...@domain.fr'

It reset without asking for password, and the error line is added to
auth.log

Then try :

'username.lastn...@domain.fr'

It asks for password, even that account doesn't exists, and the error
line isn't added

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1865517

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  We use ldap authentication with mail addresses as usernames.
  So usernames are not posix and some are > 32 chars but are working.

  Some of them fire a bug :
  When trying to log, it doesn't asks for password, it just wait some seconds 
then reset to ask username.

  I can't clearly identify which regex fire the bug or not but this one does
  "username.lastnamelastnamelastn...@domain.fr"

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

  In auth.log, that line pops up when bug is started

  "Mar  2 16:23:14 premier agetty[97945]: checkname failed: Operation
  not permitted"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+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 1865517] Re: cannot log in with long username

[Jo K]

All Ubuntu systems are affected.
That's not related to a personal configuration, booting live latest ubuntu let 
me reproduce this.

Its more clear on tty, as you see username field resets, but it's the
same from ligthdm

So should i open a bug for agetty package instead ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1865517

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  We use ldap authentication with mail addresses as usernames.
  So usernames are not posix and some are > 32 chars but are working.

  Some of them fire a bug :
  When trying to log, it doesn't asks for password, it just wait some seconds 
then reset to ask username.

  I can't clearly identify which regex fire the bug or not but this one does
  "username.lastnamelastnamelastn...@domain.fr"

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

  In auth.log, that line pops up when bug is started

  "Mar  2 16:23:14 premier agetty[97945]: checkname failed: Operation
  not permitted"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+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 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file

[Doug Smythies]

I think bug 1864992 and this one are duplicates.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864436

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  linux Ubuntu 5.4.0-14.17-generic 5.4.18
  linux-modules-5.4.0-15-generic 5.4.0-15.18

  Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated 
error messages:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864436/+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