[Touch-packages] [Bug 1984058] [NEW] File size mismatch with http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz

[Peter]

Public bug reported:

Steps to reproduce:


1. configured debug repo with vim into /etc/apt/source.list like:

deb http://ddebs.ubuntu.com/ubuntu/ focal-updates main

Did that in a docker container where the following is installed:

apt update; apt-get install -y ca-certificates; apt install curl -y; apt
install vim -y; apt install gnupg -y

2.add the GPG key with 
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 

3. apt clean before I fired up apt update.

Then the file size mismatch:

Err:4 http://ddebs.ubuntu.com focal-updates/main amd64 Packages
  File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 
185.125.190.18 80]
  Hashes of expected file:
   - Filesize:480068 [weak]
   - 
SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be
   - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a
   - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak]
   - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak]
  Release file created at: Wed, 27 Jul 2022 20:48:02 +
Fetched 42.7 kB in 1s (30.3 kB/s)
Reading package lists... Done
E: Failed to fetch 
http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz  File 
has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 
185.125.190.18 80]
   Hashes of expected file:
- Filesize:480068 [weak]
- 
SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be
- SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a
- SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak]
- MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak]
   Release file created at: Wed, 27 Jul 2022 20:48:02 +
E: Some index files failed to download. They have been ignored, or old ones 
used instead.


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 2.0.6
Uname: Linux 121a7a7831cf 5.10.104-linuxkit x86_64
Architecture: amd64
Date: Tue 09 Aug 2022 09:11:32 AM UTC
SourcePackage: apt

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

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

Title:
  File size mismatch with http://ddebs.ubuntu.com/dists/focal-
  updates/main/binary-amd64/Packages.xz

Status in apt package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  
  1. configured debug repo with vim into /etc/apt/source.list like:

  deb http://ddebs.ubuntu.com/ubuntu/ focal-updates main

  Did that in a docker container where the following is installed:

  apt update; apt-get install -y ca-certificates; apt install curl -y;
  apt install vim -y; apt install gnupg -y

  2.add the GPG key with 
  apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 

  3. apt clean before I fired up apt update.

  Then the file size mismatch:

  Err:4 http://ddebs.ubuntu.com focal-updates/main amd64 Packages
File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 
185.125.190.18 80]
Hashes of expected file:
 - Filesize:480068 [weak]
 - 
SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be
 - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a
 - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak]
 - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak]
Release file created at: Wed, 27 Jul 2022 20:48:02 +
  Fetched 42.7 kB in 1s (30.3 kB/s)
  Reading package lists... Done
  E: Failed to fetch 
http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz  File 
has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 
185.125.190.18 80]
 Hashes of expected file:
  - Filesize:480068 [weak]
  - 
SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be
  - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a
  - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak]
  - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak]
 Release file created at: Wed, 27 Jul 2022 20:48:02 +
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.6
  Uname: Linux 121a7a7831cf 5.10.104-linuxkit x86_64
  Architecture: amd64
  Date: Tue 09 Aug 2022 09:11:32 AM UTC
  SourcePackage: apt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1984058/+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 2003387] [NEW] ubuntu-desktop-minimal should depend on cryptsetup, lvm2

[Peter]

Public bug reported:

The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on
everything needed for a functioning desktop / server installation
respectively. Well, almost everything.

Two packages that they don't depend on, but should, or at least it should 
recommend them are:
- cryptsetup
- lvm2

The reason is that if Ubuntu was installed with disk encryption and/or
LVM turned on, these packages are essential. The system won't even boot
without cryptsetup, for example (found this out the hard way).

The release of Ubuntu you are using: 22.10
The version of the package you are using: ubuntu-desktop-minimal 1.497

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: net-snmp (Ubuntu) => ubuntu-meta (Ubuntu)

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

Title:
  ubuntu-desktop-minimal should depend on cryptsetup, lvm2

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on
  everything needed for a functioning desktop / server installation
  respectively. Well, almost everything.

  Two packages that they don't depend on, but should, or at least it should 
recommend them are:
  - cryptsetup
  - lvm2

  The reason is that if Ubuntu was installed with disk encryption and/or
  LVM turned on, these packages are essential. The system won't even
  boot without cryptsetup, for example (found this out the hard way).

  The release of Ubuntu you are using: 22.10
  The version of the package you are using: ubuntu-desktop-minimal 1.497

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003387/+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 2003387] Re: ubuntu-desktop-minimal should depend on cryptsetup, lvm2

[Peter]

@jbicha
After installation, it was fine. It's just that in the process of trying to 
clean up leftover packages years later, I did something like:

# apt-get update && apt-get dist-upgrade
# apt-mark auto '*'
# apt-mark manual ubuntu-minimal
# apt-mark manual ubuntu-desktop-minimal
# apt-mark manual linux-generic 
...same for some other packages I actively used...
# apt-get autopurge

After these steps, the system was left in an unbootable state because in
the "autopurge" / autoremove stage, cryptsetup was uninstalled, hence it
was missing from the new initrd.


I don't know if this is an "intended use case" for the ubuntu-* metapackages, 
but apart from cryptsetup (and lvm2 which I suspected is needed so I 
fortunately marked it as manual), every other package that's needed for a 
functioning system is actually Depended / Recommended by the combination of 
ubuntu-minimal and ubuntu-desktop-minimal. 

(Only other exception being the kernel package but I understand the
reasoning behind that.)



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

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

Title:
  ubuntu-desktop-minimal should depend on cryptsetup, lvm2

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on
  everything needed for a functioning desktop / server installation
  respectively. Well, almost everything.

  Two packages that they don't depend on, but should, or at least it should 
recommend them are:
  - cryptsetup
  - lvm2

  The reason is that if Ubuntu was installed with disk encryption and/or
  LVM turned on, these packages are essential. The system won't even
  boot without cryptsetup, for example (found this out the hard way).

  The release of Ubuntu you are using: 22.10
  The version of the package you are using: ubuntu-desktop-minimal 1.497

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003387/+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 2003387] Re: ubuntu-desktop-minimal should depend on cryptsetup, lvm2

[Peter]

I see.  
"apt-mark auto '*'" may not be "supported" but it works and has been for a long 
time, even on Debian. If my installation wouldn't have had an encrypted root, I 
wouldn't have run into any issue. And I guess those with a non-encrypted setup 
don't need cryptsetup so in this sense ubuntu-minimal stays true to its name.

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

Title:
  ubuntu-desktop-minimal should depend on cryptsetup, lvm2

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on
  everything needed for a functioning desktop / server installation
  respectively. Well, almost everything.

  Two packages that they don't depend on, but should, or at least it should 
recommend them are:
  - cryptsetup
  - lvm2

  The reason is that if Ubuntu was installed with disk encryption and/or
  LVM turned on, these packages are essential. The system won't even
  boot without cryptsetup, for example (found this out the hard way).

  The release of Ubuntu you are using: 22.10
  The version of the package you are using: ubuntu-desktop-minimal 1.497

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003387/+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 2003387] Re: ubuntu-desktop-minimal should depend on cryptsetup, lvm2

[Peter]

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Opinion

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

Title:
  ubuntu-desktop-minimal should depend on cryptsetup, lvm2

Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  The meta-packages ubuntu-desktop-minimal / ubuntu-minimal depend on
  everything needed for a functioning desktop / server installation
  respectively. Well, almost everything.

  Two packages that they don't depend on, but should, or at least it should 
recommend them are:
  - cryptsetup
  - lvm2

  The reason is that if Ubuntu was installed with disk encryption and/or
  LVM turned on, these packages are essential. The system won't even
  boot without cryptsetup, for example (found this out the hard way).

  The release of Ubuntu you are using: 22.10
  The version of the package you are using: ubuntu-desktop-minimal 1.497

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003387/+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 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

[Peter]

@seb128 I am aware that this has been fixed in hirsuite, but it remains
unfixed in focal. I am committed to staying on an LTS release.

If this is not the right place to report this bug, could you please
point me to how I can navigate the relevant backporting request process?

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

Title:
  PDF documents signed with DocuSign show the error message "The
  document contains no pages"

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---

  1. Open a document signed with DocuSign

  Expected behaviour:
  ---

  Document opens fine

  Actual behaviour:
  ---

  Evince refuses to display the document, with the error message "The
  document contains no pages".

  If document is opened with `pdftotext`, the output is:

  ```
  Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
  Syntax Error: Invalid XRef entry 3
  Syntax Error: Top-level pages object is wrong type (null)
  Command Line Error: Wrong page range given: the first page (1) can not be 
after the last page (0).
  ```

  Other information
  ---

  This appears to be a bug in libpoppler, described at
  https://stackoverflow.com/questions/66636441/pdf2image-library-
  failing-to-read-pdf-signed-using-docusign and
  https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I
  believe that bumping the version of Poppler and/or Evince will solve
  the issue, though I have no way to test this as compiling from source
  is a significant undertaking.

  I do not have a public sample document that I could share, but
  examples of DocuSigned documents should be available online.

  Ubuntu version: 20.04 LTS (up to date)
  Evince version: 3.36.10 (official package)
  Poppler version: 0.86.1-0ubuntu1 (official package)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+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 1917871] [NEW] VIM cannot update file on SMB share

[Peter]

Public bug reported:

I cannot edit files on a Windows share that is smb-mounted by Ubuntu
using VI, VIM or GVIM.

Other applications on Ubuntu do not have this problem, including GEDIT
and LibreOffice

Bizarrely I can create a file with VI, VIM and GVIM, but saving changes in any 
subsequent edit session fails with:
E212: Cannot open file for writing

I attach a screenshot of the problem showing the error when I am in the mounted 
directory:
/run/user/1000/gvfs/smb-share:server=jcpr-dell-3,share=e/temp/uplay

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vim-gtk3 2:8.1.2269-1ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  5 10:19:47 2021
ExecutablePath: /usr/bin/vim.gtk3
InstallationDate: Installed on 2020-11-11 (113 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2021-03-05 09-20-29.png"
   
https://bugs.launchpad.net/bugs/1917871/+attachment/5473346/+files/Screenshot%20from%202021-03-05%2009-20-29.png

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

Title:
  VIM cannot update file on SMB share

Status in vim package in Ubuntu:
  New

Bug description:
  I cannot edit files on a Windows share that is smb-mounted by Ubuntu
  using VI, VIM or GVIM.

  Other applications on Ubuntu do not have this problem, including GEDIT
  and LibreOffice

  Bizarrely I can create a file with VI, VIM and GVIM, but saving changes in 
any subsequent edit session fails with:
  E212: Cannot open file for writing

  I attach a screenshot of the problem showing the error when I am in the 
mounted directory:
  /run/user/1000/gvfs/smb-share:server=jcpr-dell-3,share=e/temp/uplay

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim-gtk3 2:8.1.2269-1ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 10:19:47 2021
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2020-11-11 (113 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Peter]

How to stop receiving this emails?


---
V prípade akýchkoľvek otázok alebo nejasností ma neváhajte kontaktovať.
S pozdravom a úctou / Best regards and respectfully

Peter Onger
Mobil - 00421 904 526 034
Email - ogi2...@gmail.com

-
Zeitgeist - The Movie - Duch doby - český dabing
<https://www.youtube.com/watch?v=vGu1Xb6iTU0>
Zeitgeist - Addendum - Duch doby: Dodatek - český dabing
<https://www.youtube.com/watch?v=UoAHKQtooo0>
Zeitgeist - Moving Forward - Duch doby: Stále vpred - slovenský dabing
<https://www.youtube.com/watch?v=BEAPbmhpfZY>
Americký sen - drsný animovaný film o americké centrální bance - český
dabing <https://www.youtube.com/watch?v=Awa0FQi3l3Y>
Váž si svoju planétu - Planet Earth is You by @CarlosChaviraTV
<https://www.youtube.com/watch?v=6_dRTlUc7cw>

Škola online - KhanAcademy.org <https://www.khanacademy.org/>


št 14. 1. 2021 o 14:41 Łukasz Zemczak <1871...@bugs.launchpad.net>
napísal(a):

> 14:32 < juliank> sil2100: everything is straight forward cherry-picked
> from master, which is 2.1.18
>
>
> ** Changed in: apt (Ubuntu)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
>   Installation fails due to useless immediate configuration error when
>   "Install Third-Party Drivers" is selected
>
> Status in Ubuntu CD Images:
>   Fix Released
> Status in apt package in Ubuntu:
>   Fix Released
> Status in apt source package in Bionic:
>   In Progress
> Status in apt source package in Focal:
>   In Progress
> Status in apt source package in Groovy:
>   In Progress
> Status in apt package in Debian:
>   Unknown
>
> Bug description:
>   [Impact]
>   Installations that really succeeded would then fail because APT could
> not immediately configure a package. Which is a pointless way to fail at
> that point, because everything did work out anyway.
>
>   We have two changes that help address this:
>
>   * The first one stops immediately configuring multi-arch siblings
>   (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
>   necessary, and caused all the libc6:i386 failures here.
>
>   * The second change sort of also supersedes the first one: It just
>   ignores any errors from immediate configuration, relying on the fact
>   that it's checked and rectified at a later point if there are
>   unconfigured packages (which is what made all those failures happen
>   spuriously after having successfully installed everything).
>
>   [Test case]
>   We have one test case in EIPP format in the Debian bug 973305 which was
> only helped by the second change, not the first one. Run
> /usr/lib/apt/planners < eipp.log and check there are no errors.
>
>   TODO: It's unclear if the APT from proposed installed in the live
>   session will fix the installer, needs investigation, but would make a
>   useful test case.
>
>   [Regression potential]
>   It's imaginable that we missed something somewhere and some path that
> checked for a set error doesn't check it anymore, and we report success
> when we hit an error, but it seems unlikely.
>
>   Behavior of --simulate changes. This used to fail before as well, and
>   will now only produce a warning. We don't believe that is a reason of
>   concern.
>
>   [Groovy SRU]
>   The groovy SRU is a sync of the 2.1.11 micro release from Debian
> unstable which also incorporates changes to the documentation: A typo fix,
> replacing focal with groovy in examples, and minor Dutch manual pages
> translation updates.
>
>   We do not have test cases for the documentation changes, and we do not
>   consider there to be a huge regression potential. As long as they
>   build, they should be readable - maybe some words are wrong in the
>   translation, who knows.
>
>   [Original bug report]
>   Test Case
>   1. Install Ubuntu Desktop on hardware with an nVidia card and select to
> install 3rd party drivers
>   2. Proceed with installation
>
>   The following error message is displayed in /var/log/syslog
>   /plugininstall.py: Verifying downloads ...
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version:
> '9.3.0-1ubuntu2' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb:
> "Version: '4.4.10-10ubuntu4' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/g/gcc

[Touch-packages] [Bug 1831162] [NEW] Xorg freeze

[Peter]

Public bug reported:

Nvidia driver 430 is definitely the cause of freezing. I have
reinstalled ubunutu twice! I also use an EGPU with my system, the 1080
ti. I have an nvidia dgpu, the 1050 ti. My computer is the dell xps 15
9570. I have finally achieved a stable system state with the nvidia
418.67 driver. So what I did was installed the lasted release of cuda
10.1 via the local run file method. That method allows you to install
the 418.67 driver and cuda 10.1 all in a nice package. I also have
nouveau.modeset=0 in grub set to run on every boot. I also uncommented
the wayfarenabled=false. I also use gswitcher, a small program designed
to make the xorg conf file for the egpu.

I have disabled secure boot and cstates

Good luck fixing nvidia driver 430.

Thank you for your dedication!

Peter

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.67  Sat Apr  6 03:07:24 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10)
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 30 19:53:15 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696]
InstallationDate: Installed on 2019-05-30 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=24f351e3-258b-46a3-8a35-bf4806a89b1c ro quiet splash 
nouveau.modeset=0 nvidia-drm.modeset=0 vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic freeze possible-manual-nvidia-install ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Nvidia driver 430 is definitely the cause of freezing. I have
  reinstalled ubunutu twice! I also use an EGPU with my system, the 1080
  ti. I have an nvidia dgpu, the 1050 ti. My computer is the dell xps 15
  9570. I have finally achieved a stable system state with the nvidia
  418.67 driver. So what I did was installed the lasted release of cuda
  10.1 via the local run file method. That method allows you to install
  the 418.67 driver and cuda 10.1 all in a nice package. I also have
  nouveau.modeset=0 in grub set to run on every boot. I also uncommented
  the wayfarenabled=false. I also use

[Touch-packages] [Bug 1831347] [NEW] Xorg freeze - update

[Peter]

Public bug reported:

Dear Ubuntu,

Thank you for taking the time to read this report. My last report stated
that nvidia-430 driver was the problem. I have since reinstalled ubuntu
18.4 and carefully followed the EGPU setup provided online using
gswitch. I should note that last install I forgot to add "systemctl
enable gswitch". I have noticed far fewer issues. Interestingly, I also
enabled autologin for my account. This appears to have helped the
problem significantly. I did try switching to regular password required
at login and the freezing / hanging did occur during some web browsing
but it was only for about 5 - 10 seconds. I then immediately switched
back to autologins and I have not noticed any freezing or hanging! I
believe the problem with regular password req logins is that it causes
my internal display (laptop screen) to be enabled first during the login
when I enter my password. After I enter my password the internal display
turns off and then I use my external display only as I have that
confiured in the ubuntu device settings. But with autologin, the
computer boots momentarily to internal screen when you see the ubuntu
dots sliding to the right and then into gnome.

So it appears using autologin is more stable when using an EGPU with
external display only! I am using nvidia-430 drivers.

So I think gdm3 needs an update or X11 needs an update so that it can
honor the external display better? Anyways! I will keep you posted.

Thanks for your dedication guys!!

Take care,

Peter

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.14  Wed May  8 01:10:53 
UTC 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  1 16:26:04 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696]
InstallationDate: Installed on 2019-06-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=96ec9aa4-d13a-4223-b15b-4284df054c79 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu

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

Title:
  Xorg freeze - update

Status in xorg package in Ubuntu:
  

[Touch-packages] [Bug 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10

[Peter]

We seem to be still affected by this even with 1.1.1-1ubuntu2.1~18.04.4
installed.  Though our use case is during a PXE install, but we will get
prompted to restart services where is before that was never the case.
bionic LTS is the only LTS we are seeing on it.  I can repo the issue
and send any logs that you may need

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

Title:
  installed libssl1.1:amd64 package post-installation script subprocess
  returned error exit status 10

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Committed
Status in openssl source package in Disco:
  Fix Committed
Status in openssl source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Systems that have in error removed debconf database fail to upgrade
  libssl1.1 (as e.g. is known to be done in some vagrant boxes)

   * libssl1.1 tries to use debconf template from libc6 package, but
  doesn't ship one by itself as it should for shared templates. As it is
  not guaranteed that template will be available.

  [TestCase]

  # DO NOT DO THIS ON PRODUCTION MACHINES #
  # echo PURGE | debconf-communicate libpam0g:amd64
  0
  # echo PURGE | debconf-communicate libpam0g
  0
  # echo PURGE | debconf-communicate libc6:amd64
  0
  # echo PURGE | debconf-communicate libc6
  0

  Then upgrade from bionic-release to the -proposed package and it
  should work.

  It should not fail with exit code 10.

  [Regression Potential]

   * A new template is added, an identical import from glibc without any
  further changes. This registers the template in debconf, for this
  package, preventing the above describe error. This has no codechanges,
  only metadata.

  [Other Info]
   
   * Original bug report 

  The error happens when trying to configure libssl1.1:amd64 (dpkg
  --configure -D 2  libssl1.1)

  dpkg: error processing package libssl1.1:amd64 (--configure):
   installed libssl1.1:amd64 package post-installation script subprocess 
returned error exit status 10
  D02: post_script_tasks - ensure_diversions
  D02: post_script_tasks - trig_incorporate
  D02: check_triggers_cycle pnow=libc-bin:amd64 first
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  D02: post_postinst_tasks - trig_incorporate
  Errors were encountered while processing:
   libssl1.1:amd64

  [ WORKAROUND TO RECOVER YOUR SYSTEM ]

  $ sudo dpkg-reconfigure libc6
  $ sudo dpkg --configure libssl1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1810277] [NEW] package linux-image-extra-4.4.0-141-generic 4.4.0-141.167 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[peter]

*** This bug is a security vulnerability ***

Private security bug reported:

Can't install packages like wireshark

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-141-generic 4.4.0-141.167
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   newkon 1962 F...m pulseaudio
 /dev/snd/controlC1:  newkon 1962 F pulseaudio
 /dev/snd/controlC0:  newkon 1962 F pulseaudio
Date: Wed Jan  2 03:05:13 2019
DpkgHistoryLog:
 Start-Date: 2019-01-02  03:03:25
 Commandline: apt-get install wireshark
 Requested-By: newkon (1000)
 Install: libc-ares2:i386 (1.10.0-3ubuntu0.2, automatic), libqgsttools-p1:i386 
(5.5.1-4ubuntu2, automatic), libnghttp2-14:i386 (1.7.1-1, automatic), 
libwireshark11:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwiretap8:i386 
(2.6.4-2~ubuntu16.04.0, automatic), libwsutil9:i386 (2.6.4-2~ubuntu16.04.0, 
automatic), wireshark:i386 (2.6.4-2~ubuntu16.04.0), wireshark-gtk:i386 
(2.6.4-2~ubuntu16.04.0, automatic), libqt5multimediawidgets5:i386 
(5.5.1-4ubuntu2, automatic), libqt5multimedia5-plugins:i386 (5.5.1-4ubuntu2, 
automatic), wireshark-common:i386 (2.6.4-2~ubuntu16.04.0, automatic), 
libwscodecs2:i386 (2.6.4-2~ubuntu16.04.0, automatic), libspandsp2:i386 
(0.0.6-2.1, automatic), libmaxminddb0:i386 (1.0.4-2.1, automatic), 
libwireshark-data:i386 (2.6.4-2~ubuntu16.04.0, automatic), wireshark-qt:i386 
(2.6.4-2~ubuntu16.04.0, automatic), libsmi2ldbl:i386 (0.4.8+dfsg2-11, automatic)
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=24bdc8fd-bb52-4ca7-981e-53bbc1b94d1a
InstallationDate: Installed on 2018-07-15 (170 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Hewlett-Packard HP ProBook 650 G1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-141-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.20
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-141-generic 4.4.0-141.167 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2018-10-09 (84 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L77 Ver. 01.02
dmi.board.name: 1993
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.02:bd12/05/2013:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10203:rvnHewlett-Packard:rn1993:rvrKBCVersion16.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 650 G1
dmi.product.version: A3009DD10203
dmi.sys.vendor: Hewlett-Packard

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check xenial

** Information type changed from Public to Public Security

** Information type changed from Public Security to Private Security

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

Title:
  package linux-image-extra-4.4.0-141-generic 4.4.0-141.167 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Can't install packages like wireshark

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   newkon 1962 F...m pulseaudio
   /dev/snd/controlC1:  newkon 1962 F pulseaudio
   /dev/snd/controlC0:  newkon 1962 F pulseaudio
  Date: Wed Jan  2 03:05:13 2019
  DpkgHistoryLog:
   Start-Date: 2019-01-02  03:03:25
   Commandline: apt-get install wireshark
   Requested-By: newkon (1000)
   Install: libc-ares2:i386 (1.10.0-3ubuntu0.2, automatic), 
libqgsttools-p1:i386 (5.5.1-4ubuntu2, automatic), libnghttp2-14:i386 (1.7.1-1, 
automatic), libwireshark11:i386 (2.6.4-2~ubuntu16.04.0, automatic), 
libwiretap8:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwsutil9:i386 
(2.6.4-2~ubuntu16.04.0, automatic), wireshark:i386 (2.6.4-2~ubuntu16.04.0), 
wireshark-gtk:i386 (2.6.4-2~ubuntu16.04.0, automatic), 
libqt5multimediawidgets5:i386 (5.5.1-4ubuntu2, automatic), 
libqt5multimedia5-pl

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Peter]

Adding

 DNSMASQ_EXCEPT=lo

to
 /etc/default/dnsmasq

solves the problem in my case, kubuntu 17.10, kernel 4.15.rc7,
for several days now.

Peter

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05

[Touch-packages] [Bug 1517052] [NEW] [TravelMate P256-M, Realtek ALC283, Speaker, Internal] No sound at all

[peter]

Public bug reported:

No sound from the speakers which work fine "on test". Problem is recent
as ok last month.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18
Uname: Linux 3.16.0-53-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  peter  1793 F pulseaudio
 /dev/snd/controlC0:  peter  1793 F pulseaudio
CurrentDesktop: Unity
Date: Tue Nov 17 13:45:03 2015
InstallationDate: Installed on 2015-04-07 (223 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  peter  1793 F pulseaudio
 /dev/snd/controlC0:  peter  1793 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [TravelMate P256-M, Realtek ALC283, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA50_HB
dmi.board.vendor: Acer
dmi.board.version: V1.09
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/11/2014:svnAcer:pnTravelMateP256-M:pvrV1.09:rvnAcer:rnBA50_HB:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: TravelMate P256-M
dmi.product.version: V1.09
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  [TravelMate P256-M, Realtek ALC283, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound from the speakers which work fine "on test". Problem is
  recent as ok last month.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peter  1793 F pulseaudio
   /dev/snd/controlC0:  peter  1793 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 17 13:45:03 2015
  InstallationDate: Installed on 2015-04-07 (223 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peter  1793 F pulseaudio
   /dev/snd/controlC0:  peter  1793 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [TravelMate P256-M, Realtek ALC283, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/11/2014:svnAcer:pnTravelMateP256-M:pvrV1.09:rvnAcer:rnBA50_HB:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P256-M
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1517052/+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 1518663] [NEW] Disconnected path errors

[Peter]

Public bug reported:

The first error is that the audit message (notice the path):

type=AVC msg=audit(1448143203.902:359992): apparmor="DENIED"
operation="file_mmap" info="Failed name lookup - disconnected path"
error=-13 profile="/usr/sbin/openvpn" name="run/nscd/dbfQMsBd" pid=25814
comm="openvpn" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

appears in the audit log. The second is that aa-logprof throws an
exception on reading it:

Traceback (most recent call last):
  File "/usr/sbin/aa-logprof", line 54, in 
apparmor.do_logprof_pass(logmark)
  File "/usr/lib/python3.4/site-packages/apparmor/aa.py", line 2289, in 
do_logprof_pass
ask_the_questions()
  File "/usr/lib/python3.4/site-packages/apparmor/aa.py", line 1762, in 
ask_the_questions
severity = sev_db.rank(path, mode_to_str(mode))
  File "/usr/lib/python3.4/site-packages/apparmor/severity.py", line 141, in 
rank
raise AppArmorException("Unexpected rank input: %s" % resource)
apparmor.common.AppArmorException: 'Unexpected rank input: run/nscd/dbfQMsBd'

I've been having this problem for several years.

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

** Also affects: apparmor (openSUSE)
   Importance: Undecided
   Status: New

** No longer affects: apparmor (openSUSE)

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

Title:
  Disconnected path errors

Status in apparmor package in Ubuntu:
  New

Bug description:
  The first error is that the audit message (notice the path):

  type=AVC msg=audit(1448143203.902:359992): apparmor="DENIED"
  operation="file_mmap" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/openvpn" name="run/nscd/dbfQMsBd"
  pid=25814 comm="openvpn" requested_mask="r" denied_mask="r" fsuid=0
  ouid=0

  appears in the audit log. The second is that aa-logprof throws an
  exception on reading it:

  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 54, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3.4/site-packages/apparmor/aa.py", line 2289, in 
do_logprof_pass
  ask_the_questions()
File "/usr/lib/python3.4/site-packages/apparmor/aa.py", line 1762, in 
ask_the_questions
  severity = sev_db.rank(path, mode_to_str(mode))
File "/usr/lib/python3.4/site-packages/apparmor/severity.py", line 141, in 
rank
  raise AppArmorException("Unexpected rank input: %s" % resource)
  apparmor.common.AppArmorException: 'Unexpected rank input: run/nscd/dbfQMsBd'

  I've been having this problem for several years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1518663/+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 1492580] Re: Display corruption

[Peter]

** Attachment added: "Corruption  at the bottom of the search window"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1492580/+attachment/4457852/+files/Screenshot%20from%202015-09-05%2014%3A29%3A23.png

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

Title:
  Display corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running a newly installed and updated Ubuntu 14.04.3 LTS on a
  Samsung P500 Laptop (Model NP-P500I, NP-P500-RA01DE). I guess this
  issue is related to the graphics card, which is a Radeon Xpress 1250.

  The display corruption occurs directly after login on the top of the
  screen and i mentioned something at the bottom of the search window. I
  attached  screenshots of it.

  I see similar corruption with ubuntu 15.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep  5 14:05:22 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] 
[1002:7942] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c034]
  InstallationDate: Installed on 2015-09-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R59P/R60P/R61P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=baa0aac5-0549-40cc-b292-1b9a4af32753 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 09YI
  dmi.board.name: R59P/R60P/R61P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr09YI:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR59P/R60P/R61P:pvr02YI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR59P/R60P/R61P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R59P/R60P/R61P
  dmi.product.version: 02YI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Sep  5 13:47:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3~trusty1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1492580/+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 1492580] [NEW] Display corruption

[Peter]

Public bug reported:

I am running a newly installed and updated Ubuntu 14.04.3 LTS on a
Samsung P500 Laptop (Model NP-P500I, NP-P500-RA01DE). I guess this issue
is related to the graphics card, which is a Radeon Xpress 1250.

The display corruption occurs directly after login on the top of the
screen and i mentioned something at the bottom of the search window. I
attached  screenshots of it.

I see similar corruption with ubuntu 15.04.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep  5 14:05:22 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] [1002:7942] 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c034]
InstallationDate: Installed on 2015-09-05 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R59P/R60P/R61P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=baa0aac5-0549-40cc-b292-1b9a4af32753 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 09YI
dmi.board.name: R59P/R60P/R61P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr09YI:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR59P/R60P/R61P:pvr02YI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR59P/R60P/R61P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
dmi.product.name: R59P/R60P/R61P
dmi.product.version: 02YI
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Sep  5 13:47:09 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3~trusty1
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 corruption trusty ubuntu

** Attachment added: "Screenshot1"
   
https://bugs.launchpad.net/bugs/1492580/+attachment/4457826/+files/Screenshot%20from%202015-09-05%2014%3A24%3A46.png

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

Title:
  Display corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running a newly installed and updated Ubuntu 14.04.3 LTS on a
  Samsung P500 Laptop (Model NP-P500I, NP-P500-RA01DE). I guess this
  issue is related to the graphics card, which is a Radeon Xpress 1250.

  The display corruption occurs directly after login on the top of the
  screen and i mentioned something at the bottom of the search window. I
  attached  screenshots of it.

  I see similar corruption with ubuntu 15.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep  5 14:05:22 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] 
[1002:7942] (prog-if 00 [VGA controller])
 Subsystem: S

[Touch-packages] [Bug 1723708] [NEW] package unattended-upgrades 0.98ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Peter]

Public bug reported:

I've got this error message while auto upgrading in Ubuntu 17.10 Artful
Aardvark (development branch)

Kernel: 4.13.0-12-generic

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: unattended-upgrades 0.98ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
.var.log.unattended-upgrades.unattended-upgrades.log: 2017-10-15 07:37:39,650 
INFO Not running on the development release.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sun Oct 15 07:55:37 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-10-07 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.98ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package unattended-upgrades 0.98ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I've got this error message while auto upgrading in Ubuntu 17.10
  Artful Aardvark (development branch)

  Kernel: 4.13.0-12-generic

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.98ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log: 2017-10-15 07:37:39,650 
INFO Not running on the development release.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 15 07:55:37 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.98ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1723708/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Peter]

The solution proposed by Juan Hernandez (message 32) worked for me. I am
running Xubuntu 16.04 on a Dell Inspiron 3542. I finally decided to look
for a fix after successfully using a wireless mouse for some time. I did
not have to modify /usr/share/X11/xorg.conf.d/90-libinput.conf as some
others did.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

[Peter]

Hi. I have the same problem with my installation. I'm using Ubuntu 16.04. I get 
the same popping sounds as other users. It seems like that the sound goes very 
high for a split second every minute or so and I get the volume notification 
bubble with it.
It also happens when I mute the sound. In that case it unmutes the sound and 
stays unmutted.
Has anybody with understanding of the inner workings of the sound system 
identified the problem yet?
This wasn't an issue for me in Ubuntu 14.04.

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

Title:
  Volume notification keeps popping up constantly(the notifyosd bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings flashes briefly
  during every popup. Someone on IRC suggested to kill pulseaudio and
  thus restart it, that does not fix the issue. I also tried the Live
  environment thinking it might be due to some old config files in home
  partition (which was preserved during upgrade), but this problem
  happens in the live environment as well, which makes sense because it
  was present during installation as well.

  Users with the same issue:
  http://ubuntuforums.org/showthread.php?t=2323815
  http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
  
http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sidd   1651 F pulseaudio
   /dev/snd/controlC0:  sidd   1651 F pulseaudio
   /dev/snd/controlC1:  sidd   1651 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 12:31:12 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1420025] [NEW] No upper panel or window decorations after upgrading from 14.04

[Peter]

Public bug reported:

I just upgraded Ubuntu from 12.04 to 14.04 to 14.10. After the first
update the system booted and everything was fine (when the updater asked
me about configuration of something I always clicked "Replace"), but
after the second update I also could log in, but after that I only saw
the wallpaper and some icons. There is no top menu bar or the Launcher.
The only way for me to run an application is to press Ctrl+Alt+F1 and
type "export:DISPLAY=:0" and then "chromium-browser" for example.  The
applications are  missing the decorations and I can't use any keyboard
shortcuts.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.0:
 
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb  9 22:45:38 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:21d7]
InstallationDate: Installed on 2011-01-10 (1491 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Gigabyte Technology Co., Ltd. GA-770T-USB3
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=86e64e82-e0e2-4dbf-a9b2-40ba4917e444 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-770T-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd01/06/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-770T-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Mon Feb  9 22:35:43 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Gaming Mouse G300 MOUSE, id 8
 inputLogitech Gaming Mouse G300 KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic

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

Title:
  No upper panel or window decorations after upgrading from 14.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded Ubuntu from 12.04 to 14.04 to 14.10. After the first
  update the system booted and everything was fine (when the updater
  asked me about configuration of something I always clicked "Replace"),
  but after the second update I also could log in, but after that I only
  saw the wallpaper and some icons. There is no top menu bar or the
  Launcher. The only way for me to run an application is to press
  Ctrl+Alt+F1 and type "export:DISPLAY=:0" and then "chromium-browser"
  for example.  The applications are  missing the decorations and I
  can't use any keyboard shortcuts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8.1
 

[Touch-packages] [Bug 1420025] Re: No upper panel or window decorations after upgrading from 14.04

[Peter]

Just wanted to update that launching the Gnome seems like a workaround,
because it works fine.

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

Title:
  No upper panel or window decorations after upgrading from 14.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded Ubuntu from 12.04 to 14.04 to 14.10. After the first
  update the system booted and everything was fine (when the updater
  asked me about configuration of something I always clicked "Replace"),
  but after the second update I also could log in, but after that I only
  saw the wallpaper and some icons. There is no top menu bar or the
  Launcher. The only way for me to run an application is to press
  Ctrl+Alt+F1 and type "export:DISPLAY=:0" and then "chromium-browser"
  for example.  The applications are  missing the decorations and I
  can't use any keyboard shortcuts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb  9 22:45:38 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:21d7]
  InstallationDate: Installed on 2011-01-10 (1491 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MachineType: Gigabyte Technology Co., Ltd. GA-770T-USB3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=86e64e82-e0e2-4dbf-a9b2-40ba4917e444 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-770T-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd01/06/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770T-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Feb  9 22:35:43 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Gaming Mouse G300 MOUSE, id 8
   inputLogitech Gaming Mouse G300 KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1420025/+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 1420025] Re: Unity doesn't show the top menu bar or launcher after upgrading from 10.04 to 14.04

[Peter]

** Summary changed:

- No upper panel or window decorations after upgrading from 14.04
+ Unity doesn't show the top menu bar or launcher after upgrading from 10.04 to 
14.04

** Summary changed:

- Unity doesn't show the top menu bar or launcher after upgrading from 10.04 to 
14.04
+ Unity doesn't show the top menu bar or launcher after upgrading from 12.04 to 
14.04

** Summary changed:

- Unity doesn't show the top menu bar or launcher after upgrading from 12.04 to 
14.04
+ Unity doesn't show the top menu bar or launcher after upgrading from 14.04 to 
14.10

** Description changed:

  I just upgraded Ubuntu from 12.04 to 14.04 to 14.10. After the first
- update the system booted and everything was fine (when the updater asked
- me about configuration of something I always clicked "Replace"), but
- after the second update I also could log in, but after that I only saw
- the wallpaper and some icons. There is no top menu bar or the Launcher.
- The only way for me to run an application is to press Ctrl+Alt+F1 and
- type "export:DISPLAY=:0" and then "chromium-browser" for example.  The
- applications are  missing the decorations and I can't use any keyboard
- shortcuts.
+ update the system launched Unity and everything was fine (when the
+ updater asked me about configuration of something I always clicked
+ "Replace"). After the second update I could log in, but there was only
+ the wallpaper and some icons displayed. There is no top menu bar or the
+ Launcher. The only way for me to run an application is to press
+ Ctrl+Alt+F1 and type "export:DISPLAY=:0" and then "chromium-browser" for
+ example.  The applications are  missing the decorations and I can't use
+ any keyboard shortcuts.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  .tmp.unity.support.test.1:
-  
+ 
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb  9 22:45:38 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
-Subsystem: Gigabyte Technology Co., Ltd Device [1458:21d7]
+  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
+    Subsystem: Gigabyte Technology Co., Ltd Device [1458:21d7]
  InstallationDate: Installed on 2011-01-10 (1491 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MachineType: Gigabyte Technology Co., Ltd. GA-770T-USB3
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pl_PL.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=86e64e82-e0e2-4dbf-a9b2-40ba4917e444 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-770T-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd01/06/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770T-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Feb  9 22:35:43 2015
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputLogitech Gaming Mouse G300 MOUSE, id 8
-  inputLogitech Gaming

[Touch-packages] [Bug 1640299] [NEW] Nvidia Quadro FX5600

[Peter]

Public bug reported:

No Display or Bad Quality

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov  8 21:43:17 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. M5A88-V EVO [1043:843e]
 NVIDIA Corporation G80GL [Quadro FX 5600] [10de:019d] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation G80GL [Quadro FX 5600] [10de:0409]
InstallationDate: Installed on 2016-11-07 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6b81fad4-813f-41e1-aeb9-db6be080c430 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88TD-V EVO/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd05/11/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Tue Nov  8 21:27:55 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety

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

Title:
  Nvidia Quadro FX5600

Status in xorg package in Ubuntu:
  New

Bug description:
  No Display or Bad Quality

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov  8 21:43:17 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. M5A88-V EVO [1043:843e]
   NVIDIA Corporation G80GL [Quadro FX 5600] [10de:019d] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80GL [Quadro FX 5600] [10de:0409]
  InstallationDate: Installed on 2016-11-07 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System manufacturer System Product Name
 

[Touch-packages] [Bug 1573903] [NEW] package libc6 2.19-0ubuntu6.7 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libc6/changelog.Debian.gz', which is different from other insta

[Peter]

Public bug reported:

➜  cache sudo apt-get -f install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  cpp-4.8 g++-4.8 gcc-4.8 gcc-4.8-base gir1.2-gtk-2.0 lib32gcc1 libasan0
  libatomic1 libexpat1-dev libgail-common libgail18 libgcc-4.8-dev
  libgdk-pixbuf2.0-dev libgfortran3 libgomp1 libgtk2.0-0 libgtk2.0-bin
  libgtk2.0-dev libitm1 libjasper-dev libpixman-1-dev libpng12-dev
  libquadmath0 libstdc++-4.8-dev libstdc++6 libtsan0
Suggested packages:
  gcc-4.8-locales g++-4.8-multilib gcc-4.8-doc libstdc++6-4.8-dbg
  gcc-4.8-multilib libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg
  libasan0-dbg libtsan0-dbg libquadmath0-dbg libgtk2.0-doc libstdc++-4.8-doc
The following packages will be upgraded:
  cpp-4.8 g++-4.8 gcc-4.8 gcc-4.8-base gir1.2-gtk-2.0 lib32gcc1 libasan0
  libatomic1 libexpat1-dev libgail-common libgail18 libgcc-4.8-dev
  libgdk-pixbuf2.0-dev libgfortran3 libgomp1 libgtk2.0-0 libgtk2.0-bin
  libgtk2.0-dev libitm1 libjasper-dev libpixman-1-dev libpng12-dev
  libquadmath0 libstdc++-4.8-dev libstdc++6 libtsan0
26 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.
267 not fully installed or removed.
Need to get 0 B/37.2 MB of archives.
After this operation, 3,187 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up libpcre3:amd64 (1:8.31-2ubuntu2.1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
(Reading database ... 231050 files and directories currently installed.)
Preparing to unpack .../libitm1_4.8.4-2ubuntu1~14.04.1_amd64.deb ...
Unpacking libitm1:amd64 (4.8.4-2ubuntu1~14.04.1) over (4.8.4-2ubuntu1~14.04) ...
Preparing to unpack .../libgomp1_4.8.4-2ubuntu1~14.04.1_amd64.deb ...
Unpacking libgomp1:amd64 (4.8.4-2ubuntu1~14.04.1) over (4.8.4-2ubuntu1~14.04) 
...
Preparing to unpack .../gcc-4.8-base_4.8.4-2ubuntu1~14.04.1_amd64.deb ...
Unpacking gcc-4.8-base:amd64 (4.8.4-2ubuntu1~14.04.1) over 
(4.8.4-2ubuntu1~14.04) ...
dpkg: error processing archive 
/var/cache/apt/archives/gcc-4.8-base_4.8.4-2ubuntu1~14.04.1_amd64.deb 
(--unpack):
 trying to overwrite shared '/usr/share/doc/gcc-4.8-base/changelog.Debian.gz', 
which is different from other instances of package gcc-4.8-base:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6 2.19-0ubuntu6.7
ProcVersionSignature: Ubuntu 3.16.0-70.90~14.04.1-generic 3.16.7-ckt25
Uname: Linux 3.16.0-70-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Thu Apr 21 21:25:16 2016
Dependencies:
 gcc-4.9-base 4.9.3-0ubuntu4
 libc6 2.19-0ubuntu6.7
 libgcc1 1:4.9.3-0ubuntu4
 multiarch-support 2.19-0ubuntu6.7
DuplicateSignature: package:libc6:2.19-0ubuntu6.7:trying to overwrite shared 
'/usr/share/doc/libc6/changelog.Debian.gz', which is different from other 
instances of package libc6:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libc6/changelog.Debian.gz', which is different from other 
instances of package libc6:amd64
InstallationDate: Installed on 2016-04-15 (7 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.12
SourcePackage: eglibc
Title: package libc6 2.19-0ubuntu6.7 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libc6/changelog.Debian.gz', which is different 
from other instances of package libc6:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict trusty

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

Title:
  package libc6 2.19-0ubuntu6.7 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libc6/changelog.Debian.gz', which is
  different from other instances of package libc6:amd64

Status in eglibc package in Ubuntu:
  New

Bug description:
  ➜  cache sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following extra packages will be installed:
cpp-4.8 g++-4.8 gcc-4.8 gcc-4.8-base gir1.2-gtk-2.0 lib32gcc1 libasan0
libatomic1 libexpat1-dev libgail-common libgail18 libgcc-4.8-dev
libgdk-pixbuf2.0-dev libgfortran3 libgomp1 libgtk2.0-0 libgtk2.0-bin
libgtk2.0-dev libitm1 libjasper-dev libpixman-1-dev libpng12-dev
libquadmath0 libstdc++-4.8-dev libstdc++6 libtsan0
  Suggested packages:
gcc-4.8-locales g++-4.8-multilib gcc-4.8-doc libstdc++6-4.8-dbg
gcc-4.8-multilib libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg
libasan0-dbg libtsan0-dbg libquadmath0-dbg libgtk2.0-doc libstdc++-4.8-doc
  The following pac

[Touch-packages] [Bug 1476218] [NEW] package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

[Peter]

Public bug reported:

Errors were encountered while processing:
 dictionaries-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: dictionaries-common 1.20.5
ProcVersionSignature: Ubuntu 3.2.0-87.125-generic 3.2.69
Uname: Linux 3.2.0-87-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.9
Architecture: amd64
Date: Mon Jul 20 12:50:35 2015
ErrorMessage: subprocess installed post-installation script returned error exit 
status 255
PackageArchitecture: all
SourcePackage: dictionaries-common
Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 255
UpgradeStatus: Upgraded to trusty on 2015-07-20 (0 days ago)

** Affects: dictionaries-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package dictionaries-common 1.20.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in dictionaries-common package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   dictionaries-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: dictionaries-common 1.20.5
  ProcVersionSignature: Ubuntu 3.2.0-87.125-generic 3.2.69
  Uname: Linux 3.2.0-87-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  Date: Mon Jul 20 12:50:35 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  PackageArchitecture: all
  SourcePackage: dictionaries-common
  Title: package dictionaries-common 1.20.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to trusty on 2015-07-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1476218/+subscriptions

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

Re: [Touch-packages] [Bug 497949] Re: pycurl contents missing

[Peter]

Hi Barry,
I dont work with ubuntu any more, sorry
Dňa 2.10.2014 17:55 používateľ "Barry Warsaw" <497...@bugs.launchpad.net>
napísal:

> This bug is quite old.  Is it still a problem in newer versions of
> Ubuntu?
>
> ** Changed in: pycurl (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/497949
>
> Title:
>   pycurl contents missing
>
> Status in “pycurl” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When i try to use package manager for installing / un-installing of any
> software, it keeps failing with following progress:
>   I couldn't find a solution for this. What could be the problem please?
>   Thanks
>
>   peter@peterk:~$ sudo apt-get install vlc
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   vlc is already the newest version.
>   0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>   18 not fully installed or removed.
>   After this operation, 0B of additional disk space will be used.
>   Setting up python-pycurl (7.18.2-1build1) ...
>   /var/lib/dpkg/info/python-pycurl.postinst: 14: pycentral: not found
>   dpkg: error processing python-pycurl (--configure):
>subprocess post-installation script returned error exit status 127
>   Setting up python-pexpect (2.1-1build1) ...
>   /var/lib/dpkg/info/python-pexpect.postinst: 9: pycentral: not found
>   dpkg: error processing python-pexpect (--configure):
>subprocess post-installation script returned error exit status 127
>   dpkg: dependency problems prevent configuration of python-smartpm:
>python-smartpm depends on python-pycurl; however:
> Package python-pycurl is not configured yet.
>python-smartpm depends on python-pexpect; however:
> Package python-pexpect is not configured yet.
>   dpkg: error processing python-smartpm (--configure):
>dependency problems - leaving unconfigured
>   dpkg: dependency problems prevent configuration of landscape-common:
>landscape-common depends on python-smartpm (>=
> 1.1.1~bzr20081010-0ubuntu1); however:
> Package python-smartpm is not configured yet.
>   dpkg: error processing landscape-common (--configure):
>dependency problems - leaving unconfigured
>   Setting up linux-image-2.6.27-15-generic (2.6.27-15.43) ...
>   No apport report written because the error message indicates its a
> followup error from a previous failure.
> No apport report written because MaxReports is
> reached already
>   Running depmod.
>   update-initramfs: Generating /boot/initrd.img-2.6.27-15-generic
>   Running postinst hook script /sbin/update-grub.
>   Searching for GRUB installation directory ... found: /boot/grub
>   Searching for default file ... found: /boot/grub/default
>   Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
>   Searching for splash image ... none found, skipping ...
>   Found kernel: /boot/vmlinuz-2.6.27-16-generic
>   Found kernel: /boot/vmlinuz-2.6.27-15-generic
>   Found kernel: /boot/vmlinuz-2.6.27-14-generic
>   Found kernel: /boot/vmlinuz-2.6.27-11-generic
>   Found kernel: /boot/vmlinuz-2.6.27-9-generic
>   Found kernel: /boot/vmlinuz-2.6.27-7-generic
>   Found kernel: /boot/vmlinuz-2.6.24-21-generic
>   Found kernel: /boot/memtest86+.bin
>   Updating /boot/grub/menu.lst ... done
>
>   Examining /etc/kernel/postinst.d.
>   run-parts: executing /etc/kernel/postinst.d/nvidia-common
>   /etc/kernel/postinst.d/nvidia-common: /usr/bin/nvidia-detector:
> /usr/bin/python: bad interpreter: No such file or directory
>   run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code
> 126
>   Failed to process /etc/kernel/postinst.d at
> /var/lib/dpkg/info/linux-image-2.6.27-15-generic.postinst line 1002.
>   dpkg: error processing linux-image-2.6.27-15-generic (--configure):
>subprocess post-installation script returned error exit status 2
>   No apport report written because MaxReports is reached already
> Setting up
> linux-image-2.6.27-16-generic (2.6.27-16.44) ...
>   Running depmod.
>   update-initramfs: Generating /boot/initrd.img-2.6.27-16-generic
>   Running postinst hook script /sbin/update-grub.
>   Searching for GRUB installation directory ... found: /boot/grub
>   Searching for default file ... found: /boot/grub/default
>   Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
>   Searching for splash image ... none found, skipping ...
>   Found kernel: /boot/vmlinuz-2.6.27-16-generic
>   Found kernel

[Touch-packages] [Bug 1388825] [NEW] expand_ppa_line function removed from ppa

[Peter]

Public bug reported:

The following change removes the expand_ppa_line function, without any
mention elsewhere.

http://bazaar.launchpad.net/~ubuntu-core-dev/software-
properties/main/revision/904#softwareproperties/ppa.py

I don't know if this is intended, if so: shouldn't this change have been
done in a non BC breaking way, by first deprecating the function?

DistroRelease: Ubuntu 14.10
Package: python-software-properties 0.94

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

Title:
  expand_ppa_line function removed from ppa

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The following change removes the expand_ppa_line function, without any
  mention elsewhere.

  http://bazaar.launchpad.net/~ubuntu-core-dev/software-
  properties/main/revision/904#softwareproperties/ppa.py

  I don't know if this is intended, if so: shouldn't this change have
  been done in a non BC breaking way, by first deprecating the function?

  DistroRelease: Ubuntu 14.10
  Package: python-software-properties 0.94

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1388825/+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 1244021] Re: After upgrading to 13.10, clang and GCC erroneously look for GCC-4.7 headers

[peter]

After a dist-upgrade of my Linux Mint (to Olivia), I ran into the same
problems.

Your fix (renaming all c++/4.7 directory to something like c++/4.7_old)
fixed it. Just my directories were /usr/include/c++/4.7/ and
/usr/include/i386-linux-gnu/c++/4.7/ . But that was easy to find.

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

Title:
  After upgrading to 13.10, clang and GCC erroneously look for GCC-4.7
  headers

Status in “gcc-4.8” package in Ubuntu:
  Confirmed

Bug description:
  I'm a Firefox developer.  13.04 was working fine.  I upgraded to 13.10
  and now I can't compile Firefox with either clang or GCC.

  Here's a reduced test case:

#include 
int main(void) {}

  If I compile this with clang I get this:

  [fjord:~/moz/mi5] clang++ a.cpp
  In file included from a.cpp:1:
  In file included from 
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/memory:62:
  
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/allocator.h:92:29:
 error: 
unknown template name '__allocator_base'
  class allocator: public __allocator_base<_Tp>
  ^
  
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/allocator.h:116:25:
 error: 
expected '('
: __allocator_base<_Tp>(__a) { }
  ^
  
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/allocator.h:116:25:
 error: 
expected '{' or ','
  3 errors generated.

  The results with GCC are similar.

  I found the problem is that both clang and GCC are somehow configured
  to look for some GCC 4.7 headers as well as GCC 4.8 headers -- both of
  them have |-I/usr/lib/gcc/x86_64-linux-
  gnu/4.7/../../../../include/x86_64-linux-gnu/c++/4.7| hardwired in the
  default flags.

  As a workaround, I renamed /usr/include/c++/4.7/ and
  /usr/include/x86_64-linux-gnu/c++/4.7/ so the compilers could no
  longer find them, and now things are working normally.  But obviously
  this should be fixed properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1244021/+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 1787729] Re: apport-autoreport.service fails if whoopsie isn't running

[Peter Goodall]

still happening in ubuntu 22.04

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.4 LTS
Release:22.04
Codename:   jammy

Feb 21 09:19:54 <> systemd[1]: Started ACPI Events Check.
Feb 21 09:19:54 <> systemd[1]: Started Process error reports when automatic 
reporting is enabled (file watch).

Can I help with more information?

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

Title:
  apport-autoreport.service fails if whoopsie isn't running

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  If automatic crash reporting is enabled and apport-autoreport.service starts 
before whoopsie on boot then crash reports that happened during shutdown or 
start up will not be automatically uploaded to the error tracker.

  Test Case
  -
  1) install apport-noui
  2) sudo service apport stop
  3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating 
the situation where whoopsie isn't running. I did this by copying lines 159,160 
to 161,162 and unindenting them. N.B. this isn't necessary if you are on a 
system where whoopsie is starting after apport.
  4) touch /var/crash/my.crash
  5) reboot
  5) run 'systemctl status apport-autoreport.service' and observe it failed 
because whoopsie isn't running

  When testing the proposed version of apport you'll want to revert the
  changes you made to whoopsie-upload-all. With the version of apport
  from -proposed you should no longer see the failure message for the
  apport-autoreport.service. The best test case is just having an
  affected system test the package from -proposed though.

  Regression Potential
  
  We are clearly fixing something that was a mistake in the original service so 
there is little chance for regression.

  

  ProblemType: BugDistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 2058415] Re: Reading binary data in paraview broken by libexpat1 update

[Peter Heywood]

On Jammy, the update from 2.4.7-1ubuntu0.2 to 2.4.7-1ubuntu0.3 causes
simialr XML not well formed (invalid token) errors for files which
contain binary data. Downgrading to 2.4.7-1 resolved the issue.

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

Title:
  Reading binary data in paraview broken by libexpat1 update

Status in expat package in Ubuntu:
  Confirmed
Status in paraview package in Ubuntu:
  Confirmed

Bug description:
  The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. 
  In particular reading vtu files containing binary data fails since this 
update. When trying to open files that worked fine before, Paraview now reports 
a parsing error like this one:

  ERROR: In vtkXMLParser.cxx, line 376
  vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, 
column 0, byte index 1036: not well-formed (invalid token)

  ERROR: In vtkXMLReader.cxx, line 521
  vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file.  
ReadXMLInformation aborting.

  The problem disappears when reverting libexpat1 to version 2.5.0-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/expat/+bug/2058415/+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 2061995] Re: ULLTS 22, 24: FontConfig broken by including ".conf" file

[Peter Grandi]

** Also affects: fontconfig (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ULLTS 22,24: FontConfig broken by including ".conf" file

Status in Ubuntu:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in
  somewhat different ways:

  * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts
  are rendered as if the font were not hinted or 'hinting' were 'false'.
  This is not noticeable if antialiasing is on, and most users default
  to antialiasing.

  * In ULTS 22 if there is a file
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer
  found, or get rendered with rectangular shapes. I guess not many users
  customize their font settings.

  A telling example from ULTS 22:

  $  cat /etc/fonts/conf.d/10-antialias.conf
  
  
  
  

  false

  
  $  cp -p /etc/fonts/conf.d/10-antialias.conf 
$XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  This happens also with a skeleton
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf')
  too:

  $  cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf
  
  
  
  
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  None of these anomalies happen under ULST 20.

  My impression: symptoms vary and are weird, so probably it is
  something like a buffer overflow when reading the ".conf" files or the
  use of not-initialized memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2061995/+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 2061995] Re: ULTS 22, 24: FontConfig broken by including ".conf" file

[Peter Grandi]

** Summary changed:

- ULLTS 22,24: FontConfig broken by including ".conf" file
+ ULTS 22,24: FontConfig broken by including ".conf" file

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

Title:
  ULTS 22,24: FontConfig broken by including ".conf" file

Status in Ubuntu:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in
  somewhat different ways:

  * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts
  are rendered as if the font were not hinted or 'hinting' were 'false'.
  This is not noticeable if antialiasing is on, and most users default
  to antialiasing.

  * In ULTS 22 if there is a file
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer
  found, or get rendered with rectangular shapes. I guess not many users
  customize their font settings.

  A telling example from ULTS 22:

  $  cat /etc/fonts/conf.d/10-antialias.conf
  
  
  
  

  false

  
  $  cp -p /etc/fonts/conf.d/10-antialias.conf 
$XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  This happens also with a skeleton
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf')
  too:

  $  cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf
  
  
  
  
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  None of these anomalies happen under ULST 20.

  My impression: symptoms vary and are weird, so probably it is
  something like a buffer overflow when reading the ".conf" files or the
  use of not-initialized memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2061995/+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 2058415] Re: Reading binary data in paraview broken by libexpat1 update

[Peter Heywood]

VTK has been patched upstream to correctly handle AppendedData elements
in .vtu files  with the updated/patched libexpat1:


https://gitlab.kitware.com/vtk/vtk/-/commit/db8f9efca220c9d16a30958e179abae3379d0011

https://gitlab.kitware.com/vtk/vtk/-/issues/19258

This will need backporting to older VTK releases on ubuntu's where
libexpat1's fixes have been backported, which if I'm reading the ubuntu
package release dates correctly is Jammy(security, updates), Mantic
(security, updates) and potentially Noble (release).

** Bug watch added: gitlab.kitware.com/vtk/vtk/-/issues #19258
   https://gitlab.kitware.com/vtk/vtk/-/issues/19258

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

Title:
  Reading binary data in paraview broken by libexpat1 update

Status in dune-grid package in Ubuntu:
  New
Status in expat package in Ubuntu:
  Confirmed
Status in paraview package in Ubuntu:
  Confirmed

Bug description:
  The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. 
  In particular reading vtu files containing binary data fails since this 
update. When trying to open files that worked fine before, Paraview now reports 
a parsing error like this one:

  ERROR: In vtkXMLParser.cxx, line 376
  vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, 
column 0, byte index 1036: not well-formed (invalid token)

  ERROR: In vtkXMLReader.cxx, line 521
  vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file.  
ReadXMLInformation aborting.

  The problem disappears when reverting libexpat1 to version 2.5.0-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+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 2058415] Re: Reading binary data in paraview broken by libexpat1 update

[Peter Heywood]

** Also affects: vtk7
   Importance: Undecided
   Status: New

** No longer affects: vtk7

** Also affects: vtk7 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Reading binary data in paraview broken by libexpat1 update

Status in dune-grid package in Ubuntu:
  New
Status in expat package in Ubuntu:
  Confirmed
Status in paraview package in Ubuntu:
  Confirmed
Status in vtk7 package in Ubuntu:
  New

Bug description:
  The recent update of libexpat1 to version 2.5.0-2ubuntu0.1 broke Paraview. 
  In particular reading vtu files containing binary data fails since this 
update. When trying to open files that worked fine before, Paraview now reports 
a parsing error like this one:

  ERROR: In vtkXMLParser.cxx, line 376
  vtkXMLDataParser (0x5b0ac36fc970): Error parsing XML in stream at line 21, 
column 0, byte index 1036: not well-formed (invalid token)

  ERROR: In vtkXMLReader.cxx, line 521
  vtkXMLUnstructuredGridReader (0x5b0ac3d3b670): Error parsing input file.  
ReadXMLInformation aborting.

  The problem disappears when reverting libexpat1 to version 2.5.0-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/2058415/+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 597337] Re: lsb_release should show history of release upgrades

[Peter Matulis]

** Changed in: lsb (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 lsb in Ubuntu.
https://bugs.launchpad.net/bugs/597337

Title:
  lsb_release should show history of release upgrades

Status in lsb package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: lsb

  Currently (Lucid), lsb_release only shows information about current
  system status.  It would be nice (wishlist) if we could keep track of
  the last fresh install and all intervening release upgrades.

  Current output to lsb_release -a (omitting ugly LSB Version output):

  ---
  Distributor ID: Ubuntu
  Description:Ubuntu 10.04 LTS
  Release:10.04
  Codename:   lucid
  ---

  Suggested output:

  ---
  Distributor ID: Ubuntu
  Release history: jaunty, karmic-dev, karmic, lucid-dev, lucid
  Description:Ubuntu 10.04 LTS
  Release:10.04
  Codename:   lucid
  ---

  Not sure if we can break 'release-dev' into parts:

  release-alpha1
  release-beta

  and so on.

  Also not sure if this can create confusion if users upgrade manually
  (editing sources.list and then 'apt-get dist-upgrade').

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/597337/+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 664264] Re: GID is not defined upon user GDM login

[Peter Matulis]

** Changed in: bash (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 bash in Ubuntu.
https://bugs.launchpad.net/bugs/664264

Title:
  GID is not defined upon user GDM login

Status in bash package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: bash

  The GID variable is not defined upon user GDM login for the bash
  shell.

  I've tested this on Ubuntu releases 9.04 to 10.10 and the behaviour is
  the same.  I've tested the Zsh shell and I don't see this (GID is
  defined).

  I believe that this variable should be assigned a value when the user
  logs in without having to manually cook something in initialization
  files (id -g).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/664264/+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 1982523] [NEW] error in commented-out NAME_REGEX

[Peter Abeln]

Public bug reported:

The default /etc/adduser.conf contains the line:

#NAME_REGEX="^[a-z][-.a-z0-9_]*\$"

Commenting this out in preparation of updating it does not work as
expected:

pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
NAME_REGEX="^[a-z][-a-z0-9_]*\$"
adduser: Please enter a username matching the regular expression configured
via the NAME_REGEX[_SYSTEM] configuration variable.  Use the 
`--force-badname'
option to relax this check or reconfigure NAME_REGEX.
pra@PABELN-X1E:~$

This is due to the overeager escaping of the dollar sign, which has the
undesired effect of requring that usernames end in `$`:

pra@PABELN-X1E:~$ sudo adduser testuser$
Adding user `testuser$' ...
Adding new group `testuser$' (1002) ...
Adding new user `testuser$' (1002) with group `testuser$' ...
Creating home directory `/home/testuser$' ...
Copying files from `/etc/skel' ...
New password:

Removing the backslash escaping the terminal `$` corrects the issue:

pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
NAME_REGEX="^[a-z][-a-z0-9_]*$"
Adding user `testuser' ...
Adding new group `testuser' (1002) ...
Adding new user `testuser' (1002) with group `testuser' ...
Creating home directory `/home/testuser' ...
Copying files from `/etc/skel' ...
New password:

I reported this for the `adduser` package because it seemed the closest
match.  The file /etc/adduser.conf is not owned by any package.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adduser 3.118ubuntu5
Uname: Linux 5.10.102.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Jul 21 19:56:02 2022
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: adduser
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  error in commented-out NAME_REGEX

Status in adduser package in Ubuntu:
  New

Bug description:
  The default /etc/adduser.conf contains the line:

  #NAME_REGEX="^[a-z][-.a-z0-9_]*\$"

  Commenting this out in preparation of updating it does not work as
  expected:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*\$"
  adduser: Please enter a username matching the regular expression 
configured
  via the NAME_REGEX[_SYSTEM] configuration variable.  Use the 
`--force-badname'
  option to relax this check or reconfigure NAME_REGEX.
  pra@PABELN-X1E:~$

  This is due to the overeager escaping of the dollar sign, which has
  the undesired effect of requring that usernames end in `$`:

  pra@PABELN-X1E:~$ sudo adduser testuser$
  Adding user `testuser$' ...
  Adding new group `testuser$' (1002) ...
  Adding new user `testuser$' (1002) with group `testuser$' ...
  Creating home directory `/home/testuser$' ...
  Copying files from `/etc/skel' ...
  New password:

  Removing the backslash escaping the terminal `$` corrects the issue:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*$"
  Adding user `testuser' ...
  Adding new group `testuser' (1002) ...
  Adding new user `testuser' (1002) with group `testuser' ...
  Creating home directory `/home/testuser' ...
  Copying files from `/etc/skel' ...
  New password:

  I reported this for the `adduser` package because it seemed the
  closest match.  The file /etc/adduser.conf is not owned by any
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: adduser 3.118ubuntu5
  Uname: Linux 5.10.102.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jul 21 19:56:02 2022
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: adduser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1982523/+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 2061995] Re: ULTS 22, 24: FontConfig broken by including ".conf" file

[Peter Grandi]

After several hundred package updates over time this problem is no
longer occurring, I suspect that it was something buggy in the XML
library used by FotnConfig.

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

Title:
  ULTS 22,24: FontConfig broken by including ".conf" file

Status in Ubuntu:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in
  somewhat different ways:

  * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts
  are rendered as if the font were not hinted or 'hinting' were 'false'.
  This is not noticeable if antialiasing is on, and most users default
  to antialiasing.

  * In ULTS 22 if there is a file
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer
  found, or get rendered with rectangular shapes. I guess not many users
  customize their font settings.

  A telling example from ULTS 22:

  $  cat /etc/fonts/conf.d/10-antialias.conf
  
  
  
  

  false

  
  $  cp -p /etc/fonts/conf.d/10-antialias.conf 
$XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  This happens also with a skeleton
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf')
  too:

  $  cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf
  
  
  
  
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  None of these anomalies happen under ULST 20.

  My impression: symptoms vary and are weird, so probably it is
  something like a buffer overflow when reading the ".conf" files or the
  use of not-initialized memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2061995/+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 2029100] Re: general protection fault when detaching a gnome-terminal

[Peter Silva]

I open one terminal window, then use + on top left to open a second. then on 
the second one,
I pick detach. and it crashes (this is in 24.04.)

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

Title:
  general protection fault when detaching a gnome-terminal

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 23.04 (I haven't had this bug in earlier releases) when
  detaching a gnome terminal tab most of the time (but not always) all
  open instances of the gnome terminal crash with the following dmesg:

  gnome-terminal-[3639] general protection fault ip:7f35f3341d41
  sp:7fffe4f846b0 error:0 in libgtk-3.so.0.2405.32[7f35f3083000+38e000]

  Not sure whether this is relevant but I'm using the NVIDIA 535.54.03
  proprietary drivers on X11

  
  libgtk-3-0:
Installed: 3.24.37-1ubuntu1
Candidate: 3.24.37-1ubuntu1
Version table:
   *** 3.24.37-1ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2029100/+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 2007837] [NEW] 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression

[Peter Thomassen]

Public bug reported:

rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling, leading
another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04) to
surface [1].

It practically makes using BackupPC 3 impossible with clients using
rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04
can't be used to back up machines with 22.04 is rather surprising and
has bitten other users [2].

It's unclear whether the bug will be fixed in 18.04's and 20.04's
libfile-rsyncp-perl package (for status, see [3]).

Because of this, the rsync maintainer has included a patch in 3.2.4 that
fixes this regression [4] (even though not strictly an rsync bug). As a
result, rsync 3.2.3 is the only affected version, which happens to be
the one packaged in 22.04.

This report is to request backporting that fix [4] to Ubuntu 22.04, so
that things don't silently break in scenarios where the backup server is
left at 20.04, and some backup clients happen to upgrade to 22.04.

I'm not sure what the criteria for security releases are, but as the
issue causes backup denial of service and has easy mitigation, I think
it would make sense to put it through the security channel.

[1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358
[2]: 
https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html
[3]: https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833
[4]: 
https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8

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

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

Title:
  22.04: Backport request from 3.2.4 for fix of 3.2.3 regression

Status in rsync package in Ubuntu:
  New

Bug description:
  rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling,
  leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04)
  to surface [1].

  It practically makes using BackupPC 3 impossible with clients using
  rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04
  can't be used to back up machines with 22.04 is rather surprising and
  has bitten other users [2].

  It's unclear whether the bug will be fixed in 18.04's and 20.04's
  libfile-rsyncp-perl package (for status, see [3]).

  Because of this, the rsync maintainer has included a patch in 3.2.4
  that fixes this regression [4] (even though not strictly an rsync
  bug). As a result, rsync 3.2.3 is the only affected version, which
  happens to be the one packaged in 22.04.

  This report is to request backporting that fix [4] to Ubuntu 22.04, so
  that things don't silently break in scenarios where the backup server
  is left at 20.04, and some backup clients happen to upgrade to 22.04.

  I'm not sure what the criteria for security releases are, but as the
  issue causes backup denial of service and has easy mitigation, I think
  it would make sense to put it through the security channel.

  [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358
  [2]: 
https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html
  [3]: 
https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833
  [4]: 
https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 2007837] Re: 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression

[Peter Thomassen]

Thank you for looking into this. The test case is described in
https://github.com/backuppc/backuppc/issues/369#issuecomment-693663922
and boils down to:

> * Create temporary file on host [i.e. backup client, with rsync 3.2.3]
> * Run `/usr/share/backuppc/bin/BackupPC_dump -v -f host` manually on the 
> server cmdline as correct user [use BackupPC v3 with buggy 
> libfile-rsyncp-perl, as present in Ubuntu 18.04 and 20.04)
> * Wait for rsync to start dumping files (i.e. indexing is complete), then 
> delete temporary file on host

HTH.

** Bug watch added: github.com/backuppc/backuppc/issues #369
   https://github.com/backuppc/backuppc/issues/369

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

Title:
  22.04: Backport request from 3.2.4 for fix of 3.2.3 regression

Status in rsync package in Ubuntu:
  New
Status in rsync source package in Jammy:
  Incomplete
Status in rsync package in Debian:
  Unknown

Bug description:
  rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling,
  leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04)
  to surface [1].

  It practically makes using BackupPC 3 impossible with clients using
  rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04
  can't be used to back up machines with 22.04 is rather surprising and
  has bitten other users [2].

  It's unclear whether the bug will be fixed in 18.04's and 20.04's
  libfile-rsyncp-perl package (for status, see [3]).

  Because of this, the rsync maintainer has included a patch in 3.2.4
  that fixes this regression [4] (even though not strictly an rsync
  bug). As a result, rsync 3.2.3 is the only affected version, which
  happens to be the one packaged in 22.04.

  This report is to request backporting that fix [4] to Ubuntu 22.04, so
  that things don't silently break in scenarios where the backup server
  is left at 20.04, and some backup clients happen to upgrade to 22.04.

  I'm not sure what the criteria for security releases are, but as the
  issue causes backup denial of service and has easy mitigation, I think
  it would make sense to put it through the security channel.

  [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358
  [2]: 
https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html
  [3]: 
https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833
  [4]: 
https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 2007837] Re: Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix available in 3.2.4

[Peter Thomassen]

fixed: https://launchpad.net/ubuntu/+source/rsync/3.2.7-0ubuntu0.22.04.2

** Changed in: rsync (Ubuntu Jammy)
   Status: Triaged => Fix Released

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

Title:
  Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix
  available in 3.2.4

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Fix Released
Status in rsync package in Debian:
  Unknown

Bug description:
  rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling,
  leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04)
  to surface [1].

  It practically makes using BackupPC 3 impossible with clients using
  rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04
  can't be used to back up machines with 22.04 is rather surprising and
  has bitten other users [2].

  It's unclear whether the bug will be fixed in 18.04's and 20.04's
  libfile-rsyncp-perl package (for status, see [3]).

  Because of this, the rsync maintainer has included a patch in 3.2.4
  that fixes this regression [4] (even though not strictly an rsync
  bug). As a result, rsync 3.2.3 is the only affected version, which
  happens to be the one packaged in 22.04.

  This report is to request backporting that fix [4] to Ubuntu 22.04, so
  that things don't silently break in scenarios where the backup server
  is left at 20.04, and some backup clients happen to upgrade to 22.04.

  I'm not sure what the criteria for security releases are, but as the
  issue causes backup denial of service and has easy mitigation, I think
  it would make sense to put it through the security channel.

  [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358
  [2]: 
https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html
  [3]: 
https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833
  [4]: 
https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 2043215] Re: Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.

[Peter Freeth]

Same problem. Under Xorg, the Wacom tablet can move the pointer but as
soon as I tap to click, the system locks up. Pressing alt tab a few
times restores movement to the pointer. The Wacom is therefore unusable
under Xorg. Sadly, in GIMP it's also unusable under Wayland as the
pointers are invisible.

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

Title:
  Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
  Xorg.

Status in xorg package in Ubuntu:
  New

Bug description:
  There is more information on this issue: 
https://github.com/xournalpp/xournalpp/issues/5303
  and the other bug report that is linked there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 07:17:22 2023
  DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
  InstallationDate: Installed on 2021-05-25 (899 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 1.15
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.15
  dmi.board.name: FJNB288
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
  dmi.product.name: LIFEBOOK T935
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2043215/+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 1728616] Re: using 'devel' in sources.list causes apt-get update to fail

[Peter Kehl]

FYI This bug still exists (in Focal/Mantic made to use `devel`: `sudo
sed -i 's/focal/devel/g' /etc/apt/sources.list` -
https://discourse.ubuntu.com/t/ubuntu-as-rolling-release/14751/106).

Any alternatives or workarounds to get as close to "rolling release" as
possible, please?

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

Title:
  using 'devel' in sources.list causes apt-get update to fail

Status in apt package in Ubuntu:
  Opinion

Bug description:
  Our /etc/apt/sources.list looks like this:
  $ cat /etc/apt/sources.list
  | deb http://archive.ubuntu.com//ubuntu devel main restricted universe 
multiverse
  | deb http://archive.ubuntu.com//ubuntu devel-updates main restricted 
universe multiverse
  | deb http://archive.ubuntu.com//ubuntu devel-security main restricted 
universe multiverse
  | deb http://archive.ubuntu.com//ubuntu devel-backports main restricted 
universe multiverse

  I noticed today that 'apt-get update' started failing.  Likely that
  started on Thursday or Friday when bionic opened.

  This seems less than desireable, but even if the failure is expected, what is
  the solution to "accept" this change?

  It does mention 'apt-secure(8)' but nothing there obviously points to
  the solution.

  
  $ sudo apt-get update
  Hit:2 http://ppa.launchpad.net/uvtool-dev/master/ubuntu devel InRelease
  Get:1 http://archive.ubuntu.com//ubuntu devel InRelease [235 kB]
  Get:3 http://archive.ubuntu.com//ubuntu devel-updates InRelease [65.4 kB]
  Get:4 http://archive.ubuntu.com//ubuntu devel-security InRelease [65.4 kB]
  Get:5 http://archive.ubuntu.com//ubuntu devel-backports InRelease [65.5 kB]
  Reading package lists... Done  
  W: Conflicting distribution: 
http://ppa.launchpad.net/uvtool-dev/master/ubuntu devel InRelease (expected 
devel but got zesty)
  W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel 
InRelease (expected devel but got bionic)
  N: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 
'Version' value from '17.10' to '18.04'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 
'Suite' value from 'artful' to 'bionic'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 
'Codename' value from 'artful' to 'bionic'
  N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
  W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-updates 
InRelease (expected devel-updates but got bionic)
  N: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' 
changed its 'Version' value from '17.10' to '18.04'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' 
changed its 'Suite' value from 'artful-updates' to 'bionic-updates'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' 
changed its 'Codename' value from 'artful' to 'bionic'
  N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
  W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-security 
InRelease (expected devel-security but got bionic)
  N: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' 
changed its 'Version' value from '17.10' to '18.04'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' 
changed its 'Suite' value from 'artful-security' to 'bionic-security'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' 
changed its 'Codename' value from 'artful' to 'bionic'
  N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
  W: Conflicting distribution: http://archive.ubuntu.com//ubuntu 
devel-backports InRelease (expected devel-backports but got bionic)
  N: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' 
changed its 'Version' value from '17.10' to '18.04'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' 
changed its 'Suite' value from 'artful-backports' to 'bionic-backports'
  E: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' 
changed its 'Codename' value from 'artful' to 'bionic'
  N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 30 14:37:22 2017
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.

[Touch-packages] [Bug 2018996] Re: whoopsie uses 100% CPU indefinitely on chrome crash file

[Peter Cornelius]

+1

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

Title:
  whoopsie uses 100% CPU indefinitely on chrome crash file

Status in whoopsie package in Ubuntu:
  New

Bug description:
  $@ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  
  $@ apt-cache policy whoopsie
  whoopsie:
Installed: 0.2.77
Candidate: 0.2.77
Version table:
   *** 0.2.77 500
  500 http://jp.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  
  TL;DR whoopsie will happily consume 100% for hours in what seems like a 
pretty futile attempt to deal with massive crash files. It should be more aware 
of what is a realistic crash to upload.

  This has happened a couple of times today, so I searched, found

  https://askubuntu.com/questions/1245078/woopsie-upload-all-process-
  consumes-cpu-100/1296481#1296481

  which suggested looking in /var/crash/

  where I found

  $@ ls -lh /var/crash/
  total 8.3G
  -rw-r- 1 fergal   whoopsie 8.3G May  8 23:03 
_opt_google_chrome_chrome.1000.crash

  I don't know what whoopsie was doing but I doubt that was ever going
  to be productive and I cannot have a service that is going to
  occasionally use 100% CPU for hours.

  Here's what `top` had to say before I killed it

94802 root  20   0   11.7g  11.3g  58624 R 100.0  36.6 108:11.76
  whoopsie-upload

  So it had been trying for 108 minutes and was using 11G of RAM.

  I would love to enable crash reporting but this is unacceptable. I've
  deleted the crash file and uninstalled whoopsie. I'll happily
  reinstall it if it gains some safeguards against this kind of thing.

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


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

Re: [Touch-packages] [Bug 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

[Peter Burnett]

Thanks for responding. Why is it then that the occurrences are identical with 
openSUSE please? 
rsvp & thx again. Peter

On Tuesday, May 25, 2021, 12:50:37 PM EDT, Adolfo Jayme 
<1929...@bugs.launchpad.net> wrote:  
 
 AFAIK, Ubuntu disables some of these emergency keys by default

** Package changed: gnome-screensaver (Ubuntu) => ubuntu-settings
(Ubuntu)

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1929011

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Left-Alt is always operational & Right-Alt is not at any time & not specific 
to this report's subject category.
  True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso.
  It is natural to use Right-Alt due to a closer distance to the SysRq key.
  This might help explain why some say REISUB does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 00:27:12 2021
  InstallationDate: Installed on 2020-07-14 (309 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Left-Alt is always operational & Right-Alt is not at any time & not specific 
to this report's subject category.
  True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso.
  It is natural to use Right-Alt due to a closer distance to the SysRq key.
  This might help explain why some say REISUB does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 00:27:12 2021
  InstallationDate: Installed on 2020-07-14 (309 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1929011/+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 1930669] [NEW] Ubuntu 20.04 suspend not working with nvidia-driver-450-server

[Peter Roelants]

Public bug reported:

I switched to nvidia-driver-450-server because my second monitor stopped
working after switching to nvidia-driver-460. However, this switch broke
suspend on my ThinkPad running Ubuntu 20.04. The laptop doesn't properly
suspend anymore, and when trying to get it out of suspend it gets stuck
on a black screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
Uname: Linux 5.10.0-1029-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.119.04  Sat Apr 24 
00:01:33 UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun  3 07:54:17 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia-srv, 450.119.04, 5.10.0-1029-oem, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Device [17aa:22c0]
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
InstallationDate: Installed on 2020-12-15 (169 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20THCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem 
root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2021
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET30W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20THCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P1 Gen 3
dmi.product.name: 20THCTO1WW
dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
dmi.product.version: ThinkPad P1 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu

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

Title:
  Ubuntu 20.04 suspend not working with nvidia-driver-450-server

Status in xorg package in Ubuntu:
  New

Bug description:
  I switched to nvidia-driver-450-server because my second monitor
  stopped working after switching to nvidia-driver-460. However, this
  switch broke suspend on my ThinkPad running Ubuntu 20.04. The laptop
  doesn't properly suspend anymore, and when trying to get it out of
  suspend it gets stuck on a black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
  Uname: Linux 5.10.0-1029-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64

[Touch-packages] [Bug 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers

[Peter Beurle]

This became an issue in Fedora 33 when they went to systemd-resolved.
They have just packaged and updated to strongsWan 5.9.2 and I can
confirm it resolves this issue without workarounds.

This is a VPN, surely for security reasons alone we should be getting
the latest packages as updates? This affects every version of Ubuntu 18
/ Bionic as the latest I can find is 5.9.1

I would appreciate any hints on how to ask for something to be done...

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

Title:
  systemd-resolved updated by network-manager-strongswan needed to
  restart to use the new dns servers

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 / bionic

  systemd:
Installé : 237-3ubuntu10.3

  Fresh install on a VM, was facing a bug when connecting to strongswan
  ikev2 vpn
  (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705)

  -> Updated from cosmic the required packages for the VPN that has the
  bug fixed (5.6.2-2):

  network-manager-strongswan:
    Installé : 1.4.4-1
    Candidat : 1.4.4-1
   Table de version :
   *** 1.4.4-1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
   1.4.2-2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  libcharon-extra-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  libcharon-standard-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  libstrongswan-extra-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  libstrongswan-standard-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Before connecting the VPN, `systemd-resolve --status` shows :
   DNS Servers: 192.168.1.254 # my home box resolver

  After connecting :
   DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server
    192.168.1.254 # my home box resolver

  This seems OK, but the resolution fails as it is still using the local DNS :
  systemd-resolved[270]: Server returned error NXDOMAIN, mitigating potential 
DNS violation DVE-2018-0001, retrying transaction with reduced feature level 
UDP.

  After issuing `systemctl reload-or-restart systemd-resolved.service`,
  everything seems fine.

  systemd-resolved[5651]: Got DNS stub UDP query packet for id 24298
  systemd-resolved[5651]: Looking up RR for my.host.inside.vpn IN A.
  systemd-resolved[5651]: Switching to DNS server 10.0.0.254 for interface 
enp0s3.
  systemd-resolved[5651]: Cache miss for my.host.inside.vpn IN A
  systemd-resolved[5651]: Transaction 9273 for  scope 
dns on enp0s3/*.
  systemd-resolved[5651]: Using feature level UDP+EDNS0 for transaction 9273.
  systemd-resolved[5651]: Using DNS server 10.0.0.254 for transaction 9273.

  I was hoping that `systemd-resolved` could find the new DNS without
  restarting its service after connecting to the VPN.

  Thanks for reading
  Best Regards,
  Vincent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783377/+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 1906741] Re: Firefox sometimes causes garbled audio

[Peter Mertz]

I have seen this happening for months, though not very often. But it
happened yesterday and today again.

Music playing in the background (via Audacious) is garbled. This usually
happens when I open a website in a new tab. Sounds like a bitcrusher
effect to me.

I can reverse the effect by closing tabs, but I do not see a clear
cause-and-effect pattern. There are not too many tabs open (< 15), it
began when I opened Red Hat's site, but I had to close three other tabs
before it reverted to normal.

Also, the sites did not even play Audio, none of them.

I'm on Linux for more than 15 years. This is one of the strangest things I have 
seen so far.
;)

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

Title:
  Firefox sometimes causes garbled audio

Status in firefox package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Opening certain applications/websites at the same time as Firefox
  causes the audio to become garbled.

  The audio sounds distorted with an echo.

  Certain actions are guaranteed to cause this, but it can also
  happening when only running instances of Firefox.

  I've been able to consistently cause this by launching Zoom from a link 
within Firefox. 
  This does not occur when using Chrome. 

  The only way to fix the issue is to shut down all audio-related
  programs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rdevans   55475 F pulseaudio
   /dev/snd/controlC0:  rdevans   55475 F pulseaudio
   /dev/snd/controlC3:  rdevans   55475 F pulseaudio
   /dev/snd/controlC1:  rdevans   55475 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 16:55:36 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-10-20 (1140 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 
   10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 
   169.254.0.0/16 dev enp7s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: H67M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+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 1965634] [NEW] make: recognize more shell built-ins

[Peter Pentchev]

Public bug reported:

Hi,

Thanks a lot for taking care of GNU make in Ubuntu!

Please take a look at https://bugs.debian.org/1007969 for the bug report
itself and the two patches that backport upstream commits from version
4.3. In short, make(1) does not realize that it needs to execute some
commands via /bin/sh, it tries to run e.g. "command" directly, which
fails in Makefiles that try to use "command -v" or "command -pv" to
figure out the full path of an executable program.

Thanks in advance, and keep up the great work!

G'luck,
Peter

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: make 4.2.1-1.2
Uname: Linux 5.16.0-4-amd64 x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Mar 19 18:42:11 2022
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 SHELL=/bin/bash
SourcePackage: make-dfsg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: make-dfsg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  make: recognize more shell built-ins

Status in make-dfsg package in Ubuntu:
  New

Bug description:
  Hi,

  Thanks a lot for taking care of GNU make in Ubuntu!

  Please take a look at https://bugs.debian.org/1007969 for the bug
  report itself and the two patches that backport upstream commits from
  version 4.3. In short, make(1) does not realize that it needs to
  execute some commands via /bin/sh, it tries to run e.g. "command"
  directly, which fails in Makefiles that try to use "command -v" or
  "command -pv" to figure out the full path of an executable program.

  Thanks in advance, and keep up the great work!

  G'luck,
  Peter

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: make 4.2.1-1.2
  Uname: Linux 5.16.0-4-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Mar 19 18:42:11 2022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: make-dfsg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1965634/+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 1970731] [NEW] iptables empty when using firewalld

[Peter Englmaier]

Public bug reported:

Summary:
I am using firewalld/jammy,now 1.1.1-1ubuntu1 on my vpn server. The vpn server 
is using wireguard and I could successfully configure zones and policies in 
firewalld. Yet, iptables does not show the rules from firewalld.

1) System
root@vpn:~# uname -a
Linux vpn 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux
root@vpn:~# lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04

All updates installed.


2) What happens:

I am setting rules with firewall-cmd.

These firewall rules are visible with:
   nft list table inet firewalld
but not with 'iptables'.

3) What I expect to happen:

The toutput of
  iptables --list
should also reflect firewalld settings.

4) What happened instead

However, the iptables output shows only empty tables (filter, mangle,
nat).

root@vpn:~# iptables -t nat --list
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain PREROUTING (policy ACCEPT)
target prot opt source   destination 

Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source   destination 
root@vpn:~# iptables -t filter --list
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 
root@vpn:~# iptables-legacy -t nat --list
Chain PREROUTING (policy ACCEPT)
target prot opt source   destination 

Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source   destination 
root@vpn:~# iptables-legacy -t filter --list
Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 


5) Further information

The ufw firewall is disabled and uninstalled.

According to the release notes of 22.04, the backend has changed to nftables. 
I was assuming, that the backend default is kind of transparent to the user, 
meaning iptables should still work as normal. 

I wonder if on my system is iptables correctly linked to the backend.

Iptables points to xtables-nft-multi:
root@vpn:~# ls -l /usr/sbin/iptables
lrwxrwxrwx 1 root root 26 Aug 24  2021 /usr/sbin/iptables -> 
/etc/alternatives/iptables
root@vpn:~# ls -l /etc/alternatives/iptables
lrwxrwxrwx 1 root root 22 Apr 25 18:56 /etc/alternatives/iptables -> 
/usr/sbin/iptables-nft
root@vpn:~# ls -l /usr/sbin/iptables-nft
lrwxrwxrwx 1 root root 17 Mar 24 12:58 /usr/sbin/iptables-nft -> 
xtables-nft-multi
root@vpn:~# ls -l /usr/sbin/xtables-nft-multi
-rwxr-xr-x 1 root root 224296 Mar 24 12:58 /usr/sbin/xtables-nft-multi


Perhaps this is an issue with the upgrade process of ubuntu.

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

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

Title:
  iptables empty when using firewalld

Status in ufw package in Ubuntu:
  New

Bug description:
  Summary:
  I am using firewalld/jammy,now 1.1.1-1ubuntu1 on my vpn server. The vpn 
server is using wireguard and I could successfully configure zones and policies 
in firewalld. Yet, iptables does not show the rules from firewalld.

  1) System
  root@vpn:~# uname -a
  Linux vpn 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
  root@vpn:~# lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  All updates installed.

  
  2) What happens:

  I am setting rules with firewall-cmd.

  These firewall rules are visible with:
 nft list table inet firewalld
  but not with 'iptables'.

  3) What I expect to happen:

  The toutput of
iptables --list
  should also reflect firewalld settings.

  4) What happened instead

  However, the iptables output shows only empty tables (filter, mangle,
  nat).

  root@vpn:~# iptables -t nat --list
  # Warning: iptables-legacy tables present, use iptables-legacy to see them
  Chain PREROUTING (policy ACCEPT)
  target prot opt source   destination 

  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  t

[Touch-packages] [Bug 1945288] [NEW] Search domains missing from resolv.conf stub

[Peter Ludikovsky]

Public bug reported:

System is Mint 20.2, with the relevant packages taken from Ubuntu Focal.

This is the output of `systemd-resolv --status vpn0`:
Link 7 (vpn0)
  Current Scopes: DNS
DefaultRoute setting: yes
   LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  Current DNS Server: 10.0.0.53
 DNS Servers: 10.0.0.53
  DNS Domain: example.com
  example.com.rpz
  privatelink.blob.core.windows.net
  node.prd.lan.example.com
  node.stg.lan.example.com
  node.dev.lan.example.com

However that last domain is missing from `/etc/resolv.conf` (symlink to 
`/run/systemd/resolve/stub-resolv.conf`), instead there is a line
# Too many search domains configured, remaining ones ignored.

According to resolv.conf(5) since glibc 2.26 the number of search
domains should be unlimited, and installed is 2.31-0ubuntu9.3

VPN is PaloAlto GlobalProtect through the OpenConnect plugin on
NetworkManager.

Exact same setup and behaviour for a colleague using Pop!_OS 20.04

--
systemd:
  Installed: 245.4-4ubuntu3.13
  Candidate: 245.4-4ubuntu3.13
  Version table:
 *** 245.4-4ubuntu3.13 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3.11 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 245.4-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

libc-bin:
  Installed: 2.31-0ubuntu9.3
  Candidate: 2.31-0ubuntu9.3
  Version table:
 *** 2.31-0ubuntu9.3 100
100 /var/lib/dpkg/status
 2.31-0ubuntu9.2 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
 2.31-0ubuntu9 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


** Tags: focal

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

Title:
  Search domains missing from resolv.conf stub

Status in systemd package in Ubuntu:
  New

Bug description:
  System is Mint 20.2, with the relevant packages taken from Ubuntu
  Focal.

  This is the output of `systemd-resolv --status vpn0`:
  Link 7 (vpn0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 10.0.0.53
   DNS Servers: 10.0.0.53
DNS Domain: example.com
example.com.rpz
privatelink.blob.core.windows.net
node.prd.lan.example.com
node.stg.lan.example.com
node.dev.lan.example.com

  However that last domain is missing from `/etc/resolv.conf` (symlink to 
`/run/systemd/resolve/stub-resolv.conf`), instead there is a line
  # Too many search domains configured, remaining ones ignored.

  According to resolv.conf(5) since glibc 2.26 the number of search
  domains should be unlimited, and installed is 2.31-0ubuntu9.3

  VPN is PaloAlto GlobalProtect through the OpenConnect plugin on
  NetworkManager.

  Exact same setup and behaviour for a colleague using Pop!_OS 20.04

  --
  systemd:
Installed: 245.4-4ubuntu3.13
Candidate: 245.4-4ubuntu3.13
Version table:
   *** 245.4-4ubuntu3.13 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3.11 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  libc-bin:
Installed: 2.31-0ubuntu9.3
Candidate: 2.31-0ubuntu9.3
Version table:
   *** 2.31-0ubuntu9.3 100
  100 /var/lib/dpkg/status
   2.31-0ubuntu9.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
   2.31-0ubuntu9 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945288/+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 1948877] Re: Bluetooth headphones media buttons no longer work

[Peter Rebrun]

I have got the same issue on 21.10.

Headphones: JBL LIVE 650BTNC

Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb 
v: 0.8 bus-ID: 1-9:6 chip-ID: 8087:0aa7 
   class-ID: e001 
   Report: hciconfig ID: hci0 rfk-id: 0 state: up address:  
bt-v: 2.1 lmp-v: 4.2 sub-v: 1100 hci-v: 4.2 
   rev: 1100 
   Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff 
link-mode: slave accept 
   service-classes: rendering, capturing, object transfer, audio, 
telephony 

Again it was working fine on 21.04 and 20.10

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (21.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001
     serial: 
     Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0
     rev: e2f
     Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept
     service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1948877/+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 1949774] [NEW] ntp does not synchronize on an AMD 5700G system

[Peter Jansen]

e are
any other tests or actions you would like me to take to try fixing this
annoying problem, probably only on this AMD 5700G CPU based system (in
an ASUS Desktop X300M system), please just ask.

Thanks for all your efforts.

Peter J. Jansen
Fichtlirain 13
CH-4105 Biel-Benken
Switzerland

Mob.: 0041 79 759 47 40
E-Mail (IEEE Life Member) : p.jan...@computer.org
E-Mail (S/MIME signed) : peter.jan...@ebmnet.ch

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ntp 1:4.2.8p12+dfsg-3ubuntu4.20.04.1
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Thu Nov  4 13:07:22 2021
InstallationDate: Installed on 2021-09-04 (61 days ago)
InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
NtpStatus:
 remote   refid  st t when poll reach   delay   offset  jitter
 ==
  pjjrpiz.pj.org  .PPS.1 u   11   64  3770.465  24032.5 2120.23
  time2.ethz.ch   .PPS.1 u   12   64  177   11.307  24028.7 2386.31
SourcePackage: ntp
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ntp.conf: [modified]
mtime.conffile..etc.ntp.conf: 2021-11-01T10:08:38.252598

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


** Tags: amd64 apport-bug focal

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

Title:
  ntp does not synchronize on an AMD 5700G system

Status in ntp package in Ubuntu:
  New

Bug description:
  On an AMD 5700G system, NTP does NOT synchronize :

  hercules@pjamdz3a:~$ timedatectl
 Local time: Thu 2021-11-04 12:57:24 CET
 Universal time: Thu 2021-11-04 11:57:24 UTC
   RTC time: Thu 2021-11-04 11:57:44
  Time zone: Europe/Zurich (CET, +0100)
  System clock synchronized: no
NTP service: n/a
RTC in local TZ: no
  hercules@pjamdz3a:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   pjjrpiz.pj.org  .PPS.1 u   11   64  3770.574  19761.2 2151.25
   time2.ethz.ch   .PPS.1 u   16   64  377   12.743  19729.7 2132.80
  hercules@pjamdz3a:~$ apt-cache policy ntp chrony systemd-timesyncd
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu4.20.04.1
Candidate: 1:4.2.8p12+dfsg-3ubuntu4.20.04.1
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu4.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.2.8p12+dfsg-3ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  chrony:
Installed: (none)
Candidate: 3.5-6ubuntu6.2
Version table:
   3.5-6ubuntu6.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.5-6ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  systemd-timesyncd:
Installed: (none)
Candidate: 245.4-4ubuntu3.13
Version table:
   245.4-4ubuntu3.13 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3.11 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  hercules@pjamdz3a:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal
  hercules@pjamdz3a:~$

  But on a nearly identical Intel based system, (as well as on a
  Raspberry Pi 20.04 or an Ubuntu 18.04 system), there are no problems
  whatsoever :

  hercules@pjlu2004:~$ timedatectl
 Local time: Thu 2021-11-04 12:55:10 CET
 Universal time: Thu 2021-11-04 11:55:10 UTC
   RTC time: Thu 2021-11-04 11:55:10
  Time zone: Europe/Zurich (CET, +0100)
  System clock synchronized: yes
NTP service: n/a
RTC in local TZ: no
  hercules@pjlu2004:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *pjjrpiz.pj.org  .PPS.1 u   32   64  3770.5324.204   2.957
  +time2.ethz.ch   .PPS. 

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Peter Klausner]

Recent Ubuntu 22.04.2 LTS, libgtk-4-common 4.6.6+ds-0ubuntu1,
libgtk-3-common 3.24.33-1ubuntu2,vivaldi-stable 5.7.2921.65-1

'Save as' dialog now works as expected: focus is on filename keyboard
entry,  immediately closes dialog.

BAD regression:  
Vivaldi window is frozen after that. Does not happen with other distros, cf 
https://forum.vivaldi.net/topic/85488/bug-saving-a-web-page-freezes-browser-window

This is since about 1 week now. As I got used to mousing my way around
the previous bug, I did not immediately notice the changed behaviour.
Except the browser hang, of course.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

[Peter Müller]

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

@Hui Wang:

Mistake in Linux Mint 21.1:

 sudo add-apt-repository ppa:hui.wang/pa-testing
PPA kann nicht hinzugefügt werden: »'Dieses PPA unterstützt jammy nicht

What can I Do?

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

Title:
  [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output 
didn't work anymore. 
  Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 
5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get 
the exact same problem (On 20.04 Livesystem it works) 
  An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device 
uses the wrong Kernel Module (Audio Input is working since it uses the correct 
kernel module and driver)

  
  07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:5081]
Kernel modules: snd_hda_intel
  --
  07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:5081]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:5081]
Kernel modules: snd_hda_intel

  Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.8.16-050816-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Oct 23 10:17:36 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed
  Symptom_Card: Webcam Vitade AF - USB 2.0 Camera
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [acp - acp, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD0013GE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD0013GE
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Peter Müller]

@Hui Wang:

Mistake in Linux Mint 21.1:

 sudo add-apt-repository ppa:hui.wang/pa-testing
PPA kann nicht hinzugefügt werden: »'Dieses PPA unterstützt jammy nicht

What can I Do?

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in ALSA Libraries:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in alsa-lib source package in Hirsute:
  Fix Released
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPad

[Touch-packages] [Bug 2024585] [NEW] dbus-daemon segfault if group lookup fails

[Peter Benie]

Public bug reported:

Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
dbus version: 1.12.20-2ubuntu4.1

This is related to
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which an
sssd was upgraded before its libraries. This caused dbus-daemon to
crash, which in turn ended the user's X session along with many other
programs. It also triggered NetworkManager to exit so it was no longer
doing DHCP renewals; he network connection was lost a few hours later
when the lease expired.

The failure of dbus-daemon was triggered by it reloading its
configuration while group lookups were not functioning, which revealed
an error in the dbus's error handling code.

The failure happened in two stages.

First, it failed to load the policy, and reported this error:
dbus-daemon[1207]: Unable to reload configuration: (null)

Then, a few seconds later, dbus-daemon reloaded its config again, and
this time it segfaulted.

dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28 error 
6 in dbus-daemon[5602b181b000+24000]
Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 
1e fa 83 07 01 48 89 f8 c3
  0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb fb 
ff ff 66 66 2e 0f 1f

The code corresponds to policy->refcount -= 1, inside
bus_client_policy_unref(). This error can only happen if policy was NULL
on entry.

bus_connections_reload_policy() has this code:

// connection.c line 1644
  bus_client_policy_unref (d->policy);
  d->policy = bus_context_create_client_policy (connections->context,
connection,
error);
  if (d->policy == NULL)
{
  _dbus_verbose ("Failed to create security policy for connection %p\n",
  connection);
  _DBUS_ASSERT_ERROR_IS_SET (error);
  return FALSE;
}

If bus_context_create_client_policy fails, the code decrements the
policy reference count and sets d->policy to NULL. The second time
round, the reference count is decremented again, but policy is already
NULL from last time round, hence the crash.

I've included a patch that I think should fix the error, but note that
it is not well tested!

Peter

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

** Patch added: "dbus-reload-segv.patch"
   
https://bugs.launchpad.net/bugs/2024585/+attachment/5681228/+files/dbus-reload-segv.patch

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

Title:
  dbus-daemon segfault if group lookup fails

Status in dbus package in Ubuntu:
  New

Bug description:
  Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
  dbus version: 1.12.20-2ubuntu4.1

  This is related to
  https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which
  an sssd was upgraded before its libraries. This caused dbus-daemon to
  crash, which in turn ended the user's X session along with many other
  programs. It also triggered NetworkManager to exit so it was no longer
  doing DHCP renewals; he network connection was lost a few hours later
  when the lease expired.

  The failure of dbus-daemon was triggered by it reloading its
  configuration while group lookups were not functioning, which revealed
  an error in the dbus's error handling code.

  The failure happened in two stages.

  First, it failed to load the policy, and reported this error:
  dbus-daemon[1207]: Unable to reload configuration: (null)

  Then, a few seconds later, dbus-daemon reloaded its config again, and
  this time it segfaulted.

  dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28 
error 6 in dbus-daemon[5602b181b000+24000]
  Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 
1e fa 83 07 01 48 89 f8 c3
0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb 
fb ff ff 66 66 2e 0f 1f

  The code corresponds to policy->refcount -= 1, inside
  bus_client_policy_unref(). This error can only happen if policy was
  NULL on entry.

  bus_connections_reload_policy() has this code:

  // connection.c line 1644
bus_client_policy_unref (d->policy);
d->policy = bus_context_create_client_policy (connections->context,
  connection,
  error);
if (d->policy == NULL)
  {
_dbus_verbose ("Failed to create security policy for connection 
%p\n",
connection);
_DBUS_ASSERT_ERROR_IS_SET (error);
return FALSE;
  }

  If bus_context_create_client_policy fails, the c

[Touch-packages] [Bug 2024585] Re: dbus-daemon segfault if group lookup fails

[Peter Benie]

Done. I found someone else reporting a problem that had the same
underlying cause, which led to an interesting conversation with a
developer. You can read it here:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/343

The tl;dr version is to use dbus 1.14.x in which the code path that
triggers the fault is replaced by SO_PEERGROUPS.


This makes it immune to nss disappearing under its feet, though it is a slight 
change in behaviour. When applying a policy, it will be the user's current 
groups that count, rather than the groups they would get if they logged in now.

Peter

** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #343
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/343

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

Title:
  dbus-daemon segfault if group lookup fails

Status in dbus package in Ubuntu:
  New

Bug description:
  Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
  dbus version: 1.12.20-2ubuntu4.1

  This is related to
  https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which
  an sssd was upgraded before its libraries. This caused dbus-daemon to
  crash, which in turn ended the user's X session along with many other
  programs. It also triggered NetworkManager to exit so it was no longer
  doing DHCP renewals; he network connection was lost a few hours later
  when the lease expired.

  The failure of dbus-daemon was triggered by it reloading its
  configuration while group lookups were not functioning, which revealed
  an error in the dbus's error handling code.

  The failure happened in two stages.

  First, it failed to load the policy, and reported this error:
  dbus-daemon[1207]: Unable to reload configuration: (null)

  Then, a few seconds later, dbus-daemon reloaded its config again, and
  this time it segfaulted.

  dbus-daemon[1207]: segfault at 0 ip 5602b18336e4 sp 7ffe2579de28 
error 6 in dbus-daemon[5602b181b000+24000]
  Code: 00 00 00 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 
1e fa 83 07 01 48 89 f8 c3
0f 1f 44 00 00 f3 0f 1e fa <83> 2f 01 74 07 c3 66 0f 1f 44 00 00 e9 bb 
fb ff ff 66 66 2e 0f 1f

  The code corresponds to policy->refcount -= 1, inside
  bus_client_policy_unref(). This error can only happen if policy was
  NULL on entry.

  bus_connections_reload_policy() has this code:

  // connection.c line 1644
bus_client_policy_unref (d->policy);
d->policy = bus_context_create_client_policy (connections->context,
  connection,
  error);
if (d->policy == NULL)
  {
_dbus_verbose ("Failed to create security policy for connection 
%p\n",
connection);
_DBUS_ASSERT_ERROR_IS_SET (error);
return FALSE;
  }

  If bus_context_create_client_policy fails, the code decrements the
  policy reference count and sets d->policy to NULL. The second time
  round, the reference count is decremented again, but policy is already
  NULL from last time round, hence the crash.

  I've included a patch that I think should fix the error, but note that
  it is not well tested!

  Peter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2024585/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Peter Klausner]

For 22.04, I can additionally confirm the problem for Vivaldi's save dialog.
Whereas the seemingly identical dialog in LibreOffice works as intended.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

[Peter Surda]

The bug described here looks like the one I'm experiencing. I have
multiple yubikeys which I use for SSH and GPG (occasionally U2F but that
doesn't appear to be affected by this). If I just enable the pcscd
service, the daemon doesn't auto-start after a reboot. Running ssh or
gpg commands fails to access the key. I also need to enable the socket.
Then the daemon auto-starts and I can use ssh/gpg:

$ systemctl enable pcscd
# after a reboot, pcscd is stopped, ssh/gpg unable to access the key. Need to 
start pcscd manually.

$ systemctl enable pcscd.socket
# now after reboot both the socket and the service are running and ssh/gpg works

It wasn't like this with 20.04, there enabling pcscd.service was enough.

Hope this helps others with the issue, and/or the maintainers to address
it.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1995236] [NEW] Xsessions has_option code error with fix

[Peter D.]

Public bug reported:

Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
reports and failed fixes for this over several years and releases.

There are a couple of problems in /etc/X11/Xsessions where it fails to
handle options, causing bogus error messages and, doubtless, many
errors.

The first bug is that the entire options file, including comments, is
read into a variable.

Where the variable "OPTIONS" is assigned;

Replacing "cat" with "grep" strips out comments and blank lines;

$ diff Xsession Xsession.orig 
65c65
< grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
---
> cat "$OPTIONFILE"

The second problem is that checking for a non-existent directory inside
a command substitution does not work.  It just appends garbage onto the
output string.

That is probably a bug in BASH, but I defer to your opinion there.

The immediate work around is to create an empty directory so that the
test does not fail.  Better still, force the creation of the directory
and remove the test.


eg. change this;

OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
  fi
  if [ -d /etc/X11/Xsession.options.d ]; then
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  fi
)"

to this;

OPTIONSDIR=/etc/X11/Xsession.options.d
mkdir --parents ${OPTIONSDIR}
OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  fi
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
)"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Oct 31 16:33:14 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
InstallationDate: Installed on 2022-10-20 (11 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.C0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error

[Touch-packages] [Bug 1995236] Re: Xsessions has_option code error with fix

[Peter D.]

Bother.  There is a third problem, a scope issue of some sort. 
The errors in ~/.xsession.error go away if "has_options" is moved from Xsession 
to its own file in Xsession.d

I don't see why sourceing it should make any difference, but it does.

$ cat /etc/X11/Xsession.d/00
has_option () {
  # Ensure that a later no-foo overrides an earlier foo
  if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" == "$1" ]; then
return 0
  else
return 1
  fi
}

Also I changed a "=" to "==", but that should be cosmetic.

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xor

[Touch-packages] [Bug 1995236] Re: Xsessions has_option code error with fix

[Peter D.]

And now OPTIONS has to be exported, 
and probably should be protected against being empty in the new file. So it 
becomes ${OPTIONS:-} and ${1:-}

What else have I missed?

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notificat

[Touch-packages] [Bug 1995749] [NEW] Maximum resolution not available after suspend / screen detach

[Peter Dedecker]

Public bug reported:

I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my 
laptop which is used at two locations:
- at work I have my primary built-in 4K display and 2 additional 1920x1080 
monitor connected to a HP DisplayLink docking station using DP, connected to my 
laptop using USB-C
- at home, I have my primary built-in 4K display and an additional 4x monitor 
directly connected using the mini-DP

After boot, everything works perfect. However, after working at work,
putting the laptop into suspend (by closing the lid), attaching to my
monitor at home and opening the lid again, I get my external display at
a poor resolution which I cannot change to 4K in the settings menu: the
4K resolution is not available. Also in xrandr, the 4K resolution is not
available. The resolution is however correctly provided by the monitor
at all times:

$ sudo get-edid -b 8 | parse-edid
8
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 8 as per your request.
256-byte EDID successfully retrieved from i2c bus 8
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier "PHL 328P6V"
ModelName "PHL 328P6V"
VendorName "PHL"
# Monitor Manufactured week 30 of 2020
# EDID version 1.4
# Digital Display
DisplaySize 700 400
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-160
VertRefresh 23-80
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x960, 60Hz
#Not giving standard mode: 1440x900, 75Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1280x720, 60Hz

#Extension block found. Parsing...
Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 
2191 +hsync -vsync 
Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168  
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 
+hsync +vsync 
Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 
 +hsync -vsync 
Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 
 +hsync -vsync 
Option "PreferredMode" "Mode 12"
EndSection


Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could 
easily be solved by unplugging the external monitor and plugging in back again, 
which worked most of the times, sometimes only after a few retries. Now, with 
Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this 
situation and logging in again in an Xorg session doesn't help either. Only a 
reboot seems to help.

Additional debug information at a situation with wrong resolution can be
provided on Monday, as I just rebooted again :-)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  4 23:29:27 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.12.0, 5.15.0-52-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:0962]
InstallationDate: Installed on 2022-10-21 (14 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/boo

[Touch-packages] [Bug 1995749] Re: Maximum resolution not available after suspend / screen detach

[Peter Dedecker]

Now I have a related problem at work, where the external monitors were
not detected after plugging in the laptop in the docking station and
opening the lid. Turning off and on one monitor resulted in detection
(in poor resolution) but not the second external one. When both are
turned off and on, the system hangs until I disconnect the USB-C cable
to the docking station.

A terminal window was open where lsusb was my previous command. During
the unresponsive period whilst the docking station was connected, I
could press , without seeing anything on the screen,
but after disconnecting the docking station again the command and output
where shown:



$ lsusb -tv
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
ID 1d6b:0003 Linux Foundation 3.0 root hub
|__ Port 2: Dev 26, If 0, Class=Hub, Driver=hub/4p, 5000M
ID 04b4:6504 Cypress Semiconductor Corp. 
|__ Port 1: Dev 27, If 0, Class=Hub, Driver=hub/4p, 5000M
ID 04b4:6504 Cypress Semiconductor Corp. 
|__ Port 2: Dev 28, If 0, Class=Vendor Specific Class, Driver=r8152, 
5000M
ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet 
Adapter
|__ Port 3: Dev 29, If 3, Class=Audio, Driver=snd-usb-audio, 5000M
ID 17e9:600a DisplayLink 
|__ Port 3: Dev 29, If 1, Class=Application Specific Interface, 
Driver=usbfs, 5000M
ID 17e9:600a DisplayLink 
|__ Port 3: Dev 29, If 4, Class=Audio, Driver=snd-usb-audio, 5000M
ID 17e9:600a DisplayLink 
|__ Port 3: Dev 29, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
ID 17e9:600a DisplayLink 
|__ Port 3: Dev 29, If 0, Class=Vendor Specific Class, Driver=usbfs, 
5000M
ID 17e9:600a DisplayLink 
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
ID 0c45:6723 Microdia 
|__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
ID 0c45:6723 Microdia 
|__ Port 6: Dev 58, If 0, Class=Hub, Driver=hub/4p, 480M
ID 04b4:6506 Cypress Semiconductor Corp. CY4603
|__ Port 1: Dev 59, If 0, Class=Hub, Driver=hub/4p, 480M
ID 04b4:6506 Cypress Semiconductor Corp. CY4603
|__ Port 1: Dev 60, If 0, Class=Hub, Driver=hub/4p, 480M
ID 05e3:0608 Genesys Logic, Inc. Hub
|__ Port 2: Dev 64, If 1, Class=Vendor Specific Class, Driver=, 
12M
ID 03f0:0867 HP, Inc 
|__ Port 2: Dev 64, If 0, Class=, Driver=, 12M
ID 03f0:0867 HP, Inc 
|__ Port 3: Dev 65, If 0, Class=Mass Storage, 
Driver=usb-storage, 480M
ID 0ea0:2272 Ours Technology, Inc. 
|__ Port 1: Dev 62, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse
|__ Port 2: Dev 61, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax 
PMX-KPR1101U Keyboard
|__ Port 2: Dev 61, If 1, Class=Human Interface Device, 
Driver=usbhid, 1.5M
ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax 
PMX-KPR1101U Keyboard
|__ Port 3: Dev 63, If 2, Class=Audio, Driver=snd-usb-audio, 12M
ID 045e:077f Microsoft Corp. LifeChat LX-6000 Headset
|__ Port 3: Dev 63, If 0, Class=Audio, Driver=snd-usb-audio, 12M
ID 045e:077f Microsoft Corp. LifeChat LX-6000 Headset
|__ Port 3: Dev 63, If 3, Class=Human Interface Device, 
Driver=usbhid, 12M
ID 045e:077f Microsoft Corp. LifeChat LX-6000 Headset
|__ Port 3: Dev 63, If 1, Class=Audio, Driver=snd-usb-audio, 12M
ID 045e:077f Microsoft Corp. LifeChat LX-6000 Headset
|__ Port 7: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
ID 8087:0029 Intel Corp. AX200 Bluetooth
|__ Port 7: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
ID 8087:0029 Intel Corp. AX200 Bluetooth


I'll reboot again...

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

Title:
  Maximum resolution not available after suspend / screen detach

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my 
laptop which is used at two locations:
  - at work I have my primary built-in 4K display and 2 additional 1920x1080 
monitor connected to a HP DisplayLink docking station u

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Peter Klausner]

This bug is mighty annoying. E.g. you can't simply type  to get out
of the save dialog, if you wrongly typed . You first need to
mouse the pointer to the text field.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers

[Peter Beurle]

This might provide some relief;

https://wiki.strongswan.org/projects/strongswan/repository/revisions/44e5e8367691dd64f4e5ba0105fdc28b1f81ff25

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

Title:
  systemd-resolved updated by network-manager-strongswan needed to
  restart to use the new dns servers

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 / bionic

  systemd:
Installé : 237-3ubuntu10.3

  Fresh install on a VM, was facing a bug when connecting to strongswan
  ikev2 vpn
  (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705)

  -> Updated from cosmic the required packages for the VPN that has the
  bug fixed (5.6.2-2):

  network-manager-strongswan:
    Installé : 1.4.4-1
    Candidat : 1.4.4-1
   Table de version :
   *** 1.4.4-1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
   1.4.2-2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  libcharon-extra-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  libcharon-standard-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  libstrongswan-extra-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  libstrongswan-standard-plugins:
    Installé : 5.6.2-2ubuntu1
    Candidat : 5.6.2-2ubuntu1
   Table de version :
   *** 5.6.2-2ubuntu1 300
  300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
   5.6.2-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Before connecting the VPN, `systemd-resolve --status` shows :
   DNS Servers: 192.168.1.254 # my home box resolver

  After connecting :
   DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server
    192.168.1.254 # my home box resolver

  This seems OK, but the resolution fails as it is still using the local DNS :
  systemd-resolved[270]: Server returned error NXDOMAIN, mitigating potential 
DNS violation DVE-2018-0001, retrying transaction with reduced feature level 
UDP.

  After issuing `systemctl reload-or-restart systemd-resolved.service`,
  everything seems fine.

  systemd-resolved[5651]: Got DNS stub UDP query packet for id 24298
  systemd-resolved[5651]: Looking up RR for my.host.inside.vpn IN A.
  systemd-resolved[5651]: Switching to DNS server 10.0.0.254 for interface 
enp0s3.
  systemd-resolved[5651]: Cache miss for my.host.inside.vpn IN A
  systemd-resolved[5651]: Transaction 9273 for  scope 
dns on enp0s3/*.
  systemd-resolved[5651]: Using feature level UDP+EDNS0 for transaction 9273.
  systemd-resolved[5651]: Using DNS server 10.0.0.254 for transaction 9273.

  I was hoping that `systemd-resolved` could find the new DNS without
  restarting its service after connecting to the VPN.

  Thanks for reading
  Best Regards,
  Vincent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783377/+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 1908063] [NEW] gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

Public bug reported:

This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic -- the
previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

Reproduce:
Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

Run
 qemu-aarch64 -g 1234 path/to/some/aarch64/binary

In another terminal, start gdb-multiarch. At the (gdb) prompt, type
"target remote :1234". GDB will dump core:

(gdb) target remote :1234
Remote debugging using :1234
Recursive internal problem.
Aborted (core dumped)

You can see a variant of this also in the QEMU test suite with "make -C
your-qemu-build-dir check-tcg", where the error message includes an
assertion failure:

[...]

timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
/build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This is a bug, please report it.  For instructions, see:
.

Aborted (core dumped)
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

** Affects: gdb (Ubuntu Bionic)
 Importance: Undecided
 Status: New

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1908063/+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 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

Further testing with the old gdb-8.1-0ubuntu3 package shows that this
isn't a regression since then, as that version fails too. I must have
been misled by the apt history.log somehow; sorry for the confusion
there.

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1908063/+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 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

It looks like the reason QEMU's test suite passed was that the older
Ubuntu gdb didn't have a fix for LP:1901026 (support remote connection
over UNIX domain socket), so the test suite would simply skip the
offending test and never get as far as falling over the assertion
failure. After pulling various old binaries out of my backups to test
I'm forced to conclude that I was simply misremembering by-hand use of
the gdbstub working and I must not have used it as recently as I'd
thought. So this is a bug, but not a regression.

A possible set of commits for a cherry-picked fix would be
c8ec2f334c3751c28d5f and 4ef0bef68cfc777e59156fce1 (which together
remove the hard-coded limit on register size and thus also the
assertion), but the former is not a completely trivial patch. I haven't
attempted such a cherry-pick to see if it works.

A workaround is to tell QEMU not to emulate SVE (eg with "-cpu
max,sve=off" -- it is the large SVE vector registers which trigger the
problem.


** Summary changed:

- gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error 
when connecting to QEMU aarch64 gdbstub
+ gdb-multiarch 8.1.1-0ubuntu1: assertion failure or internal error when 
connecting to QEMU aarch64 gdbstub

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1: assertion failure or internal error when
  connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

  This is a bug, please report it.  For instructions, see:
  .

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1908063/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Peter Klein]

I have performed the installation several times.  It only happens with
either a BT 4 or a BT 5 dongle.  Bluetooth 4 is CRS.  Bluetooth 5 is
mediatek.

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: am

[Touch-packages] [Bug 1910405] [NEW] bluetoothd hangs and cannot be killed

[Peter Dedecker]

Public bug reported:

Hi,

When having a bluetooth headphone (JBL Live) connected  using the A2DP
pulseaudio sink, the output sound suddenly stops during a music
streaming of videocall session. Sometimes just disconnecting and
reconnecting the headphone works, but some times reconnection is not
possible anymore due to the hanging of bluetoothd. Bluetoothd still
appears in the processes list, but cannot be killed, neither with "sudo
service bluetooth stop" or "kill -9":

$ ps afx | grep blue
 9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
 5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
10694 pts/0S+ 0:00  \_ grep blue
20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

All programs keep working normally, only bluetooth is affected as well
as the bluetooth settings page.

The only solution is a hard reboot. A soft reboot doesn't even work: the
systems keeps trying to end the bluetoothd process so one needs to press
the power button for a few seconds to terminate the process.

$ bluetoothd --version
5.48

$ uname -a
Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been
working nice for over one year now just like previous versions.

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

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been
  working nice for over one year now just like previous versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910768] [NEW] apport-collect hangs and makes computer hang

[Peter Dedecker]

Public bug reported:

This bug is related to bug 1723558
(https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I
could not transfer the generated information.

After a crash of bluetoothd (see bug 1910405) I tried to run apport-
collect with the bug ID, but the process hangs. After clicking cancel,
it makes the computer hang totally, except running teams calls that keep
streaming but without interaction possible. All is released when apport
is killed manually.

The problem also occurs when a crash of the Brave browser causes a call
to apport.

This bug is generated through ubuntu-bug -w after clicking on the
apport-collect window. This second apport process doesn't hang.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport-gtk 2.20.9-0ubuntu7.21
ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  8 15:29:04 2021
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2019-11-22 (412 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  apport-collect hangs and makes computer hang

Status in apport package in Ubuntu:
  New

Bug description:
  This bug is related to bug 1723558
  (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I
  could not transfer the generated information.

  After a crash of bluetoothd (see bug 1910405) I tried to run apport-
  collect with the bug ID, but the process hangs. After clicking cancel,
  it makes the computer hang totally, except running teams calls that
  keep streaming but without interaction possible. All is released when
  apport is killed manually.

  The problem also occurs when a crash of the Brave browser causes a
  call to apport.

  This bug is generated through ubuntu-bug -w after clicking on the
  apport-collect window. This second apport process doesn't hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.9-0ubuntu7.21
  ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  8 15:29:04 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2019-11-22 (412 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1910768] Re: apport-collect hangs and makes computer hang

[Peter Dedecker]

This time I could kill the proces from terminal instead of having to do
a remote login over ssh:

$ apport-collect 1910405

^CException ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 1294, in _shutdown
t.join()
  File "/usr/lib/python3.6/threading.py", line 1056, in join
self._wait_for_tstate_lock()
  File "/usr/lib/python3.6/threading.py", line 1072, in _wait_for_tstate_lock
elif lock.acquire(block, timeout):
KeyboardInterrupt

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

Title:
  apport-collect hangs and makes computer hang

Status in apport package in Ubuntu:
  New

Bug description:
  This bug is related to bug 1723558
  (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I
  could not transfer the generated information.

  After a crash of bluetoothd (see bug 1910405) I tried to run apport-
  collect with the bug ID, but the process hangs. After clicking cancel,
  it makes the computer hang totally, except running teams calls that
  keep streaming but without interaction possible. All is released when
  apport is killed manually.

  The problem also occurs when a crash of the Brave browser causes a
  call to apport.

  This bug is generated through ubuntu-bug -w after clicking on the
  apport-collect window. This second apport process doesn't hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.9-0ubuntu7.21
  ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  8 15:29:04 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2019-11-22 (412 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1910768] Re: apport-collect hangs and makes computer hang

[Peter Dedecker]

$ cat /var/log/apport.log
ERROR: apport (pid 16819) Fri Jan  8 13:01:19 2021: called for pid 31066, 
signal 4, core limit 0, dump mode 1
ERROR: apport (pid 16819) Fri Jan  8 13:01:19 2021: executable: 
/opt/brave.com/brave/brave (command line "/opt/brave.com/brave/brave")
ERROR: apport (pid 16819) Fri Jan  8 13:01:19 2021: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 16819) Fri Jan  8 13:05:33 2021: Unhandled exception:
Traceback (most recent call last):
  File "/usr/share/apport/apport", line 800, in 
os.chmod(report, 0o640)
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_opt_brave.com_brave_brave.1001.crash'
ERROR: apport (pid 16819) Fri Jan  8 13:05:33 2021: pid: 16819, uid: 1001, gid: 
1001, euid: 1001, egid: 1001
ERROR: apport (pid 16819) Fri Jan  8 13:05:33 2021: environment: environ({})

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

Title:
  apport-collect hangs and makes computer hang

Status in apport package in Ubuntu:
  New

Bug description:
  This bug is related to bug 1723558
  (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I
  could not transfer the generated information.

  After a crash of bluetoothd (see bug 1910405) I tried to run apport-
  collect with the bug ID, but the process hangs. After clicking cancel,
  it makes the computer hang totally, except running teams calls that
  keep streaming but without interaction possible. All is released when
  apport is killed manually.

  The problem also occurs when a crash of the Brave browser causes a
  call to apport.

  This bug is generated through ubuntu-bug -w after clicking on the
  apport-collect window. This second apport process doesn't hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.9-0ubuntu7.21
  ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  8 15:29:04 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2019-11-22 (412 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1910405] Re: bluetoothd hangs and cannot be killed

[Peter Dedecker]

I'm sorry, the apport-collect comment also results in a hanging process.
See this bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been
  working nice for over one year now just like previous versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] Dependencies.txt

[Peter Dedecker]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451722/+files/Dependencies.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] ProcCpuinfoMinimal.txt

[Peter Dedecker]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451726/+files/ProcCpuinfoMinimal.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] ProcCpuinfo.txt

[Peter Dedecker]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451725/+files/ProcCpuinfo.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] Re: bluetoothd hangs and cannot be killed

[Peter Dedecker]

apport information

** Tags added: apport-collected

** Description changed:

  Hi,
  
  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with "sudo
  service bluetooth stop" or "kill -9":
  
  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd
  
  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.
  
  The only solution is a hard reboot. A soft reboot doesn't even work: the
  systems keeps trying to end the bluetoothd process so one needs to press
  the power button for a few seconds to terminate the process.
  
  $ bluetoothd --version
  5.48
  
  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  
- Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been
- working nice for over one year now just like previous versions.
+ Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.21
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-11-22 (415 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: Dell Inc. XPS 13 7390
+ Package: linux
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
+ Tags:  bionic
+ Uname: Linux 5.4.0-59-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 10/22/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.7.0
+ dmi.board.name: 0G2D0W
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 13 7390
+ dmi.product.sku: 0962
+ dmi.sys.vendor: Dell Inc.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
+   DOWN 
+   RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
+   TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451721/+files/CurrentDmesg.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

[Touch-packages] [Bug 1910405] ProcEnviron.txt

[Peter Dedecker]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451727/+files/ProcEnviron.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] ProcInterrupts.txt

[Peter Dedecker]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451728/+files/ProcInterrupts.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] ProcModules.txt

[Peter Dedecker]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451729/+files/ProcModules.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] UdevDb.txt

[Peter Dedecker]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1910405/+attachment/5451730/+files/UdevDb.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] getfacl.txt

[Peter Dedecker]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1910405/+attachment/5451731/+files/getfacl.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] rfkill.txt

[Peter Dedecker]

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1910405/+attachment/5451732/+files/rfkill.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] Lspci.txt

[Peter Dedecker]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1910405/+attachment/5451723/+files/Lspci.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] Lsusb.txt

[Peter Dedecker]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1910405/+attachment/5451724/+files/Lsusb.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] syslog.txt

[Peter Dedecker]

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1910405/+attachment/5451733/+files/syslog.txt

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] Re: bluetoothd hangs and cannot be killed

[Peter Dedecker]

For some reason, killing the bluetoothd process just worked today unlike
previous attempts in the past days. The problem of the headset loosing
connection during a meeting, blocking the bluetooth process and settings
interface, still occurs requiring a restart of the bluetooth service and
the headset itself.

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:1D:96:DA:70:EA  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:4127584 acl:43 sco:9279 events:521650 errors:0
TX bytes:340220846 acl:518394 sco:8547 commands:3166 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910405] Re: bluetoothd hangs and cannot be killed

[Peter Dedecker]

The problem is back. This time I let the restart process wait for
several minutes. See this output.


peddecke@omer:~$ sudo service bluetooth restart
Job for bluetooth.service failed because the control process exited with error 
code.
See "systemctl status bluetooth.service" and "journalctl -xe" for details.
peddecke@omer:~$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: failed (Result: exit-code) since Wed 2021-02-03 14:21:30 CET; 14s ago
 Docs: man:bluetoothd(8)
  Process: 18598 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/
 Main PID: 18598 (code=exited, status=1/FAILURE)
   Status: "Starting up"
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
   └─25952 /usr/lib/bluetooth/bluetoothd
feb 03 14:15:29 omer systemd[1]: bluetooth.service: Main process exited, 
code=exited, status=1/FAILURE
feb 03 14:15:29 omer bluetoothd[18598]: Unable to get on D-Bus
feb 03 14:16:59 omer systemd[1]: bluetooth.service: State 'stop-sigterm' timed 
out. Killing.
feb 03 14:16:59 omer systemd[1]: bluetooth.service: Killing process 25952 
(bluetoothd) with signal SIGKILL.
feb 03 14:18:30 omer systemd[1]: bluetooth.service: Processes still around 
after SIGKILL. Ignoring.
feb 03 14:20:00 omer systemd[1]: bluetooth.service: State 'stop-final-sigterm' 
timed out. Killing.
feb 03 14:20:00 omer systemd[1]: bluetooth.service: Killing process 25952 
(bluetoothd) with signal SIGKILL.
feb 03 14:21:30 omer systemd[1]: bluetooth.service: Processes still around 
after final SIGKILL. Entering failed mode.
feb 03 14:21:30 omer systemd[1]: bluetooth.service: Failed with result 
'exit-code'.
feb 03 14:21:30 omer systemd[1]: Failed to start Bluetooth service.


Seems the same problem where killing doesn't work.

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

Title:
  bluetoothd hangs and cannot be killed

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working 
nice for over one year now just like previous versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-11-22 (415 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 7390
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=d3a4ed7f-d7f9-494e-91ed-554159c1b8ae ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-59.65~18.04.1-generic 5.4.78
  Tags:  bionic
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:r

[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

[Peter Ludwig]

Today I used tasksel to add "lubuntu-desktop" to an "ubuntu-desktop"
installation. Already installed and noticed by tasksel was additionally:
"SSH-Service" and "Print Server".

The installation of "lubunut-desktop" went fine. I logged in to lubuntu-
desktop and now I wanted to remove the "ubuntu-desktop" only ... because
it is an odroid and disk space is precoius.

I ran tasksel and deselected "ubuntu-Desktop".

I was logged in and was able to see how my desktop, start menue, icons
... were removed / uninstalled until in the end a completely naked
dektop was left. I was not able to run tasksel again. So I had to
reinstall again. :((

Ubuntu 18.04 on odroid u3.
 Image name: 
"ubuntu-18.04-4.16.0-v7-desktop-odroid-u2-u3-20190308_shrink.img.xz"

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+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 1867537] Re: 10-link-restrictions.conf missing - removed by postinst

[Peter White]

Just found this, because I also noticed the debsums error. A quick look in the 
changelog finds this:
> procps (2:3.3.16-1ubuntu1) focal; urgency=low
> [...]
>   * Dropped changes, no longer needed:
> ...
> - 10-link-restrictions.conf: this is redundant with link-protect.conf
>   from Debian.
>   * debian/procps.maintscript: handle migration of link-protect.conf from
> /etc to /usr.
>
>  -- Steve Langasek   Thu, 13 Feb 2020 22:53:02 
> -0800

But apparently that file never arrived downstream? Neither find /usr ...
nor apt-file search can find it. Having had a look at the contents of
said file by opening the .deb archive has me a bit worried:

> # These settings eliminate an entire class of security vulnerability:
> # time-of-check-time-of-use cross-privilege attacks using guessable
> # filenames (generally seen as "/tmp file race" vulnerabilities).

This could very well warrant a bump in severity, given there are
security implications.

A simple workaround is to just copy that file manually into
/etc/sysctl.d under a different name, so postinst can't find it, should
it try to murder it again. :P Of course it won't solve the debsums error
but it solves the bigger problem of the file missing entirely.

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

Title:
  10-link-restrictions.conf missing - removed by postinst

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The file "10-link-restrictions.conf" is listed in DEBIAN/conffiles in
  the binary deb package, and the file is present/installed, but it is
  removed by the "postinst" script resulting in "debsums" flagging it as
  a missing config file:

  root@beluga:~# lsb_release -d
  Description:  Ubuntu Focal Fossa (development branch)
  root@beluga:~# apt policy procps
  procps:
Installed: 2:3.3.16-1ubuntu2
Candidate: 2:3.3.16-1ubuntu2
Version table:
   *** 2:3.3.16-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@beluga:~# debsums -ac procps
  debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps 
package)

  This is not an issue in 18.04:

  manager@brigante:~$ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  manager@brigante:~$ apt policy procps
  procps:
Installed: 2:3.3.12-3ubuntu1.2
Candidate: 2:3.3.12-3ubuntu1.2
Version table:
   *** 2:3.3.12-3ubuntu1.2 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:3.3.12-3ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2:3.3.12-3ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  manager@brigante:~$ debsums -ac procps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867537/+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 1867537] Re: 10-link-restrictions.conf missing - removed by postinst

[Peter White]

Oh, I just found the file. It has a different name than suggested in the
changelog:

/usr/lib/sysctl.d/protect-links.conf

And silly me didn't of just checking what sysctl returns for those values set 
in there. It's all good:
$ sudo sysctl fs.protected_fifos
fs.protected_fifos = 1
$ sudo sysctl fs.protected_hardlinks
fs.protected_hardlinks = 1
$ sudo sysctl fs.protected_regular
fs.protected_regular = 2
$ sudo sysctl fs.protected_symlinks
fs.protected_symlinks = 1

So, from my POV the debsums error, while technically correct, is a non-
issue.

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

Title:
  10-link-restrictions.conf missing - removed by postinst

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The file "10-link-restrictions.conf" is listed in DEBIAN/conffiles in
  the binary deb package, and the file is present/installed, but it is
  removed by the "postinst" script resulting in "debsums" flagging it as
  a missing config file:

  root@beluga:~# lsb_release -d
  Description:  Ubuntu Focal Fossa (development branch)
  root@beluga:~# apt policy procps
  procps:
Installed: 2:3.3.16-1ubuntu2
Candidate: 2:3.3.16-1ubuntu2
Version table:
   *** 2:3.3.16-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@beluga:~# debsums -ac procps
  debsums: missing file /etc/sysctl.d/10-link-restrictions.conf (from procps 
package)

  This is not an issue in 18.04:

  manager@brigante:~$ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  manager@brigante:~$ apt policy procps
  procps:
Installed: 2:3.3.12-3ubuntu1.2
Candidate: 2:3.3.12-3ubuntu1.2
Version table:
   *** 2:3.3.12-3ubuntu1.2 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:3.3.12-3ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2:3.3.12-3ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  manager@brigante:~$ debsums -ac procps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867537/+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 696098] Re: cron @reboot rules fail for users wuth autofs homes, due to missing upstart dependancy

[Peter Benie]

I am using systemd rather than upstart, but the bug is the same: cron
depends on remote-fs.target, autofs depends on remote-fs.target, so they
start together. The result is that the job is run with the working
directory set to /var/spool/cron.

What cron should be waiting for is home directories being available, but
there doesn't seem to be a suitable systemd target for to achieve this.

The attached patch makes cron detect failure to chdir to the home
directory; failure to chdir is treated as a critical error and the job
is not started.

In addition, if some reboot jobs don't start due to the home directory
not being available, this will try them for up to 5 times before giving
up (about 5 minutes).


** Patch added: "cron-reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/696098/+attachment/5681677/+files/cron-reboot.patch

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

Title:
  cron @reboot rules fail for users wuth autofs homes, due to missing
  upstart dependancy

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  If a user has a @reboot cron entry like:
  ===
  @reboot date >> date.log
  ===

  And their home directory is mounted by autofs into /home

  then, the job will fail during a machine reboot because the
  cron service starts before autofs service.

  I think this is a missing dependency between in the cron upstart
  configuration, to fix this I think that cron should be started after
  autofs (only when autofs is enabled).

  
  ProblemType: Bug
  Architecture: amd64
  Date: Fri Dec 31 12:32:49 2010
  Dependencies:
   adduser 3.112ubuntu1
   base-files 5.0.0ubuntu23
   base-passwd 3.5.22
   coreutils 8.5-1ubuntu3
   debconf 1.5.32ubuntu3
   debconf-i18n 1.5.32ubuntu3
   debianutils 3.2.3
   dpkg 1.15.8.4ubuntu3
   findutils 4.4.2-1ubuntu1
   gcc-4.5-base 4.5.1-7ubuntu2
   libacl1 2.2.49-3
   libattr1 1:2.4.44-2
   libbz2-1.0 1.0.5-4ubuntu1
   libc-bin 2.12.1-0ubuntu10
   libc6 2.12.1-0ubuntu10
   libdb4.8 4.8.30-1
   libgcc1 1:4.5.1-7ubuntu2
   liblocale-gettext-perl 1.05-6
   liblzma2 4.999.9beta+20100527-1
   libncurses5 5.7+20100626-0ubuntu1
   libpam-modules 1.1.1-4ubuntu2
   libpam-runtime 1.1.1-4ubuntu2
   libpam0g 1.1.1-4ubuntu2
   libselinux1 2.0.94-1
   libtext-charwidth-perl 0.04-6
   libtext-iconv-perl 1.7-2
   libtext-wrapi18n-perl 0.06-7
   lsb-base 4.0-0ubuntu8
   ncurses-bin 5.7+20100626-0ubuntu1
   passwd 1:4.1.4.2-1ubuntu3
   perl-base 5.10.1-12ubuntu2
   sed 4.2.1-7
   sensible-utils 0.0.4ubuntu1
   tzdata 2010o-0ubuntu0.10.10
   xz-utils 4.999.9beta+20100527-1
   zlib1g 1:1.2.3.4.dfsg-3ubuntu1
  DistroRelease: Ubuntu 10.10
  NonfreeKernelModules: nvidia
  Package: cron 3.0pl1-114ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  SourcePackage: cron
  Tags: maverick
  Uname: Linux 2.6.35-24-generic x86_64

  
  /etc/init/cron.conf
  ===
  # cron - regular background program processing daemon
  #
  # cron is a standard UNIX program that runs user-specified programs at
  # periodic scheduled times

  description "regular background program processing daemon"

  start on runlevel [2345]
  stop on runlevel [!2345]

  expect fork
  respawn

  exec cron
  ===

  ps aux | grep -E '(automount|cron)'
  root  1542  0.0  0.0  21128   628 ?Ss   Dec23   0:01 cron
  root  1867  0.0  0.0 123208  1044 ?Ssl  Dec23   0:02 
/usr/sbin/automount

  cron has a lower pid so it started first...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/696098/+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 2025027] [NEW] When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Th

[Peter Hric]

Public bug reported:

See my public question open here:
https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate

I'd expect, to see the option "dis/enable wifi" at least when I disconnect from 
LAN, (if not regardless on LAN connection). 
But I can not see that option to enable wifi, nor available wifi networks even 
when I disconnect the LAN cable..

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99
Uname: Linux 5.15.0-75-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Jun 26 09:48:33 2023
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 # Include files from /etc/network/interfaces.d:
 source /etc/network/interfaces.d/*
InstallationDate: Installed on 2023-02-09 (136 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
IpRoute:
 default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 
 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 
 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 
metric 100
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.36.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: amd64 apport-bug jammy

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

Title:
  When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise.
  The option to enable Wi-Fi is not available (does not pop up and it is
  hidden while on LAN). Therefore, I can't see any available WiFi
  networks. The issue gets resolved when I reboot the PC.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  See my public question open here:
  
https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate

  I'd expect, to see the option "dis/enable wifi" at least when I disconnect 
from LAN, (if not regardless on LAN connection). 
  But I can not see that option to enable wifi, nor available wifi networks 
even when I disconnect the LAN cable..

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99
  Uname: Linux 5.15.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Jun 26 09:48:33 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2023-02-09 (136 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IpRoute:
   default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 
   169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 
   192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 
metric 100
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+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 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Ther

[Peter Hric]

1. I boot my PC with LAN cable connected. Lan works, but I only see "Enable 
networking" when I open the network manager options in the top right corner of 
the screen.  I guess, the "Enable Wireless" option is disabled deliberately, 
while on LAN - which is not the best idea IMHO.
Can't screenshot as this view hides when I click anything else - like 
screenshot utility.

2. Then I disconnect my LAN cable. The wired network icon changes and
message shows LAN network disconnected. I click the disconnected network
icon to open the roll - down menu and enable wireless => I would expect
this option will be available now.

3. But the "Enable Wireless" option is still NOT AVAILABLE. Hence I can
not choose from available wifi networks and must only use LAN
connection.

4. When I reboot PC WITH LAN CABLE DISCONNECTED, the WiFi automatically
connects and the "Enable Wireless" is available again.

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

Title:
  When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise.
  The option to enable Wi-Fi is not available (does not pop up and it is
  hidden while on LAN). Therefore, I can't see any available WiFi
  networks. The issue gets resolved when I reboot the PC.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  See my public question open here:
  
https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate

  I'd expect, to see the option "dis/enable wifi" at least when I disconnect 
from LAN, (if not regardless on LAN connection). 
  But I can not see that option to enable wifi, nor available wifi networks 
even when I disconnect the LAN cable..

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99
  Uname: Linux 5.15.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Jun 26 09:48:33 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2023-02-09 (136 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IpRoute:
   default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 
   169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 
   192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 
metric 100
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+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 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Ther

[Peter Hric]

I have to correct the information - currently even if I rebooted several
times, the option "Enable Wireless" is not available :-o

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

Title:
  When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise.
  The option to enable Wi-Fi is not available (does not pop up and it is
  hidden while on LAN). Therefore, I can't see any available WiFi
  networks. The issue gets resolved when I reboot the PC.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  See my public question open here:
  
https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate

  I'd expect, to see the option "dis/enable wifi" at least when I disconnect 
from LAN, (if not regardless on LAN connection). 
  But I can not see that option to enable wifi, nor available wifi networks 
even when I disconnect the LAN cable..

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99
  Uname: Linux 5.15.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Jun 26 09:48:33 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2023-02-09 (136 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IpRoute:
   default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 
   169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 
   192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 
metric 100
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

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