date:20200420

It stopped working again, and rebooting fixed it.  I also ran some
scripts when it was working and not working, attached here.

** Attachment added: "internal-mic-broken.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5357004/+files/internal-mic-broken.txt

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

Here's the attachment of the script when the internal microphone was
working.

** Attachment added: "internal-mic-working.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5357005/+files/internal-mic-working.txt

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1872551] Re: software-properties-qt: nvidia driver version switch fails

This bug was fixed in the package software-properties - 0.98.9

---
software-properties (0.98.9) focal; urgency=medium

  * softwareproperties/gtk/SoftwarePropertiesGtk.py:
- Gtk is doing something that takes a lock while processing checkbox
  toggled events, the polkit auth dialog can't be displayed in return,
  we don't have a proper fix and it might require GTK changes,
  meanwhile we want a working interface so workaround with a sleep
  (lp: #1727908)

 -- Sebastien Bacher   Thu, 16 Apr 2020 11:57:50
+0200

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-qt: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

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

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

A thing noticeable about the diff of the working and broken internal
microphone is that the one that's not working shows the processes that
are accessing the sound card (pacmd list-clients) includes libcanberra.

>   application.name = "libcanberra"
>   native-protocol.peer = "UNIX socket client"
>   native-protocol.version = "32"
>   application.version = "0.30"
>   application.id = "org.freedesktop.libcanberra"
>   application.process.id = "1550"
>   application.process.user = "linda"
>   application.process.host = "gazelle"
>   application.process.binary = "gsd-media-keys"
>   application.language = "en_US.UTF-8"
>   window.x11.display = ":0"
>   application.process.machine_id = 
> "df4e0d95e2e6bc9d6b63c5a35372e1c3"
>   application.process.session_id = "1"
> index: 2
>   driver: 
>   owner module: 12
>   properties:

The other thing I wondered about is that in the broken one, the IRQ pin
numbers reported by "cat /proc/asound/cards" and "lspci -vvv | grep -A9
Audio" are different.

cat /proc/asound/cards

 0 [HDMI   ]: HDA-Intel - HDA Intel HDMI
  HDA Intel HDMI at 0xf7e14000 irq 34
 1 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xf7e1 irq 33

lspci -vvv | grep -A9 Audio

00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

--
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
Subsystem: CLEVO/KAPOK Computer 8 Series/C220 Series Chipset High 
Definition Audio Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

I don't know if this has anything to do with why this internal mic stops
working.  I wonder what is calling libcanberra.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

This bug was fixed in the package software-properties - 0.98.9

---
software-properties (0.98.9) focal; urgency=medium

  * softwareproperties/gtk/SoftwarePropertiesGtk.py:
- Gtk is doing something that takes a lock while processing checkbox
  toggled events, the polkit auth dialog can't be displayed in return,
  we don't have a proper fix and it might require GTK changes,
  meanwhile we want a working interface so workaround with a sleep
  (lp: #1727908)

 -- Sebastien Bacher   Thu, 16 Apr 2020 11:57:50
+0200

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

Then it stopped working again, but this time libcanberra is not shown by
"pacmd list-clients", so maybe that has nothing to do with it.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

2020-04-20 Thread Hontvári József Levente

I actually tried to add a Release file without signing it, because it
would be simple, only a single command:

  apt-ftparchive release . > Release

But that did not work either. The apt update command exits with error:

root@pipa11:~# apt update
Hit:1 http://mirror.hk.leaseweb.net/ubuntu bionic InRelease
Hit:2 http://mirror.hk.leaseweb.net/ubuntu bionic-updates InRelease 

Hit:3 http://mirror.hk.leaseweb.net/ubuntu bionic-backports InRelease   

Ign:4 http://XXX/deb  InRelease 

Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:6 http://XXX/deb  Release   
Ign:7 http://XXX/deb  Release.gpg
Reading package lists... Done
Building dependency tree   
Reading state information... Done
All packages are up to date.
W: Skipping acquire of configured file 'Packages' as repository 'http://XXX/deb 
 InRelease' does not seem to provide it (sources.list entry misspelt?)

This is only a warning, the exit code is 0, but 'apt install' does not
find any packages in the private repo.

The setup seems to be valid, here is the HTTP log:

[20/Apr/2020:09:43:32 +0200] "GET /deb/InRelease HTTP/1.1" 404 442 "-" "Debian 
APT-HTTP/1.3 (1.6.12)"
[20/Apr/2020:09:43:32 +0200] "GET /deb/Release HTTP/1.1" 200  "-" "Debian 
APT-HTTP/1.3 (1.6.12)"
[20/Apr/2020:09:43:32 +0200] "GET /deb/Release.gpg HTTP/1.1" 404 442 "-" 
"Debian APT-HTTP/1.3 (1.6.12)"

apt update actually stores the release file, which seems to be valid:

root@pipa11:~# cat /var/lib/apt/lists/fa_deb_Release 
Date: Mon, 20 Apr 2020 07:42:24 UTC
MD5Sum:
 b531ad26ae3d375d18cb8d8bb2460102 2400 Packages.xz
 b317cbfe3c8f98153ff8b531764dab80   36 Release
SHA1:
 d45be5187c0ee43bb002cee304428f23b889fcc4 2400 Packages.xz
 af287f2a445167dd64b3af88ccfa78f4363dcb29   36 Release
SHA256:
 7466d08346b7986267dd39c3e25359402d40693d2b75f9a9ebd797a9f206c6e2 
2400 Packages.xz
 43a8eb775cee00e6ca2b8ffa58d26e08fff7bd52b560a68e82d4c6765879a8b7   
36 Release
SHA512:
 
0395b40f19e7589682e9d29b5e39b92c3f9a9a88f75770d5ba8417f77b1d4ffb3ff9b9a5a78bd78ecea970e72e19b6744c566fd55fadc11125c547a4a14b5a8a
 2400 Packages.xz
 
1a8a46da3d3d2c3344d87c37acdbd32888b35b4bde58b6f249db57fb5b016a41b821c701a7a748e34511bc098adb66510603578442145cd3d176d60e8732be5f
   36 Release

The Packages.xz file is there and valid (apt update reads and uses it,
if there is no Release file).

My sources file contains trusted=yes:
  
  deb [trusted=yes lang=none pdiffs=no] http://XXX:/deb/ /



I think it I only guess that it would work if there were a signature file. I 
think
had problems with it. I do not remember was not sure why Even if my

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreig

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

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

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873764] [NEW] CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

2020-04-20 Thread Pablo Catalina

Public bug reported:

I noted the following messages on a just installed Ubuntu Focal:

$ dmesg | grep cups
[ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 
comm="cups-browsed" capability=23  capname="sys_nice"
[ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 
comm="cups-browsed" capability=23  capname="sys_nice"
[ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


It happened after installing Brother DCPL3550CDW Linux drivers.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-daemon 2.3.1-9ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
Uname: Linux 5.4.0-25-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 20 10:49:08 2020
InstallationDate: Installed on 2020-04-19 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
Lpstat: device for DCPL3550CDW: 
dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4b66edd
MachineType: LENOVO 20MAS0DF03
Papersize: a4
PpdFiles: DCPL3550CDW: Brother DCP-L3550CDW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log p

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-20 Thread vijay kumar

I have clean installed 20.04 development daily built for 23rd March and 
everything was working fine.
Then i updated my Ubuntu to 20.04 beta release and now i cannot login in 
GDM(auto logging is disabled , after i enter my correct password it redirects 
me to login screen)
I have 2070 super with NVIDIA 440 drivers.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

--

[Touch-packages] [Bug 1870957] Re: Lost all VPN passwords on upgrades and refuses to save them now

2020-04-20 Thread Adam Funk

Here's the journalctl output, filtered with grep -Pi 'network|nm'.
Please let me know if you need more information,

** Attachment added: "filtered journalctl output"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870957/+attachment/5357060/+files/journalctl.network.txt

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

Title:
  Lost all VPN passwords on upgrades and refuses to save them now

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  On upgrade to Ubuntu-MATE 19.10, the network manager lost all my VPN
  passwords and now silently fails to store them when I select "save for
  this user", and even if I delete a VPN connection and create it again
  with that option, I always have to re-enter the password to use the
  VPN.

  It did not lose an wi-fi passwords.

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

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

[Touch-packages] [Bug 1873767] [NEW] Ubuntu not shutting down

2020-04-20 Thread Bijudas Porathur

Public bug reported:

Ubuntu is not shutting down automatically i need to press the power
button always, after shutdown command

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 20 14:42:45 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: anbox, 1: added
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:5044]
InstallationDate: Installed on 2020-04-13 (6 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=5f34b0fd-f3e5-4d60-8c63-bd2c110bf24a ro intel_idle.max_cstate=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
 Identifier "Card0"
 Driver "intel"
 Option "AccelMethod" "sna"
 EndSection
dmi.bios.date: 05/21/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33FB
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81072-306
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDG33FB:rvrAAD81072-306:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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 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/1873767

Title:
  Ubuntu not shutting down

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu is not shutting down automatically i need to press the power
  button always, after shutdown command

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:42:45 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:5044]
  InstallationDate: Installed on 2020-04-13 (6 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=5f34b0fd-f3e5-4d60-8c63-bd2c110bf24a ro intel_idle.max_cstate=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Card0"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 05/21/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33FB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81072-306
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDG33FB:rvrAAD81072-306:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

To manage notific

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-04-20 Thread Jeffrey Bouter

This bug is affecting me as well, I have a USB pre-amp (which also works
as audio card) and sounds emits just fine there. However, when I plug in
my headphones directly into my laptop, only sometimes I get the gnome
popup asking me what kind of device I plugged in.

When I click "headphones", sound of all applications is properly
directed towards my headphones. However, the gnome-settings sound "test"
button will still emit audio over my regular speakers. Selecting
different audio cards does not resolve anything.

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

Title:
External audio device shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker, or none at
all.

Status in gnome-control-center:
Unknown
Status in PulseAudio:
New
Status in gnome-control-center package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress
Status in gnome-control-center source package in Focal:
Invalid
Status in pulseaudio source package in Focal:
In Progress

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
2. Make sure it's the one selected as "Output device"
3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
5. Try to switch back to the BT device and click Test
-> same result as in step 3

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the
BT device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output
from the internal laptop speakers, even when the BT device is selected
in the Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions

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

[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

2020-04-20 Thread Julian Andres Klode

That release file is sort of invalid, as we also need the uncompressed
Packages file hashed, because we check hashes after decompression too.

So usually you generate Packages, compress it (having both around), then
create Release file, and then delete the uncompressed Packages file if
you don't need it anymore.

I guess this should work more automatically, apt-ftparchive could
transparently decompress compressed files to add them to Release file.

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

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

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

[Touch-packages] [Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

2020-04-20 Thread staedtler-przyborski

With openssl 1.1.1f-1ubuntu1 Qvpn from Qnap works again, so this bug can
be closed IMHO.

Neverthertheless I would prefer companies/producers of VPN solutions fix
and update their signatures (shouldn't be a rocket-science).

In my company I stay with PiVPN (instead of QVNP) seems more secure,
faster, and runs independend on its own device.

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

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  After upgrading openssl on my Focal-install this morning (upgrade
  openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log),
  my OpenVPN tunnel refuses to connect to our corporate VPN (from
  /var/log/syslog):

  corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature 
digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, 
emailAddress=XX
  corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL 
routines:tls_process_server_certificate:certificate verify failed

  I'm told we're running a SHA1-signed CA, which we're guessing has been
  deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog
  for -2ubuntu4 mentions importing some upstream changes, but isn't more
  specific than that:
  https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1
  .1d-2ubuntu4/changelog

  As a work-around, the internet suggests two work-arounds (neither of
  which has worked for me):

  1) Adding the following to /etc/defaults/openssl:

  OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0"

  2) Adding the following to /etc/ssl/openssl.conf:

  CipherString= :@SECLEVEL=1

  I also tried rolling back the package, but the old version doesn't
  seem to be available:

  $ sudo apt install openssl=1.1.1d-2ubuntu3
  ...
  E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found

  
  I am no SSL-expert and would appreciate any pointers to get around this. (Our 
network-dept. does not have the bandwidth to roll over our CA on short notice, 
so I will need some other way to move ahead).

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

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

[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

2020-04-20 Thread Sly_tom_cat

The same issue on Acer Swift 5F314-56 model N17W7 with Realtek ALC256
chip (HDA-Intel - HDA Intel PCH sound card).

Both internal and external microphones doesn't work.

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1873767] Re: Ubuntu not shutting down

2020-04-20 Thread Daniel van Vugt

** Package changed: xorg (Ubuntu) => 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/1873767

Title:
  Ubuntu not shutting down

Status in Ubuntu:
  New

Bug description:
  Ubuntu is not shutting down automatically i need to press the power
  button always, after shutdown command

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:42:45 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:5044]
  InstallationDate: Installed on 2020-04-13 (6 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=5f34b0fd-f3e5-4d60-8c63-bd2c110bf24a ro intel_idle.max_cstate=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Card0"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 05/21/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33FB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81072-306
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDG33FB:rvrAAD81072-306:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

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

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

[Touch-packages] [Bug 1873574] Re: Cannot enable repository source

2020-04-20 Thread Sebastien Bacher

Thank you for your bug report, the issue has been fixed recently with
that upload

https://bugs.launchpad.net/ubuntu/+source/software-properties/0.98.9

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

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

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

Title:
  Cannot enable repository source

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Context:
  I upgraded from 18.04 to 20.04 and wanted to enable again some repository 
sources that were disabled for the upgrade.

  Steps to reproduce:
  * Open software-properties-gtk
  * Go to the "Other software" tab
  * Click on any checkbox in front of each source address

  Expected result:
  * A popup appears prompting me to enter my password
  * The list does not scroll and the checkbox is checked

  Actual result:
  * The list scrolls up to the top
  * The checkbox is not checked

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 18 18:03:43 2020
  InstallationDate: Installed on 2018-04-07 (742 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2020-04-04 (13 days ago)

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

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

[Touch-packages] [Bug 1873777] [NEW] Update to 2.64.2

2020-04-20 Thread Sebastien Bacher

Public bug reported:

The bug is a placeholder for SRU information if needed

** Affects: glib-networking (Ubuntu)
 Importance: High
 Status: In Progress

** Changed in: glib-networking (Ubuntu)
   Importance: Undecided => High

** Changed in: glib-networking (Ubuntu)
   Status: New => Confirmed

** Changed in: glib-networking (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Update to 2.64.2

Status in glib-networking package in Ubuntu:
  In Progress

Bug description:
  The bug is a placeholder for SRU information if needed

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

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

[Touch-packages] [Bug 1846443] Re: Strange behavior of GNOME Tweak header when changing button positions (eoan wayland)

2020-04-20 Thread Dragosh

https://gitlab.gnome.org/GNOME/gnome-tweaks/-/issues/245

** Bug watch added: gitlab.gnome.org/GNOME/gnome-tweaks/-/issues #245
   https://gitlab.gnome.org/GNOME/gnome-tweaks/-/issues/245

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

Title:
  Strange behavior of GNOME Tweak header when changing button positions
  (eoan wayland)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  19.10 eoan
  Wayland sessions

  If the GNOME Tweak Tools window is not maximized to the full screen,
  then when you change the buttons from right to left, the title bar
  starts to behave strangely, as if it does not have enough space to
  place information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1846443/+subscriptions

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

[Touch-packages] [Bug 1873785] [NEW] Root can't modify files of other users in directories with sticky bit anymore

2020-04-20 Thread Jan Rathmann

Public bug reported:

Hello,

in Focal the behaviour has changed when a program running as root tries
to modify a file which belongs to a user/group other than root in a
directory with sticky bit set.

I'm not sure if this is a bug or the behaviour is intentional (for
certain security reasons).

Steps to reproduce:

- Boot current Focal daily iso
- Open terminal
- Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
- Create an empty file with user:group set to anything different that root 
(e.g. ubuntu:ubuntu, ubuntu:whoospie, ...)
- Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.

This behaviour is different than in previous Ubuntu versions. In Eoan it
is possible to modify the file as root in the scenario described above.

I discovered this because after changing my main installation to Eoan I
noticed that I got weird error messages from rsync when backing up my
root subvolume. In my backup script rsync runs as root, and can't update
backed up contents of /var/crash or /var/spool/cups/tmp anymore because
it isn't allowed to modify the respective files anymore.

For me personally this is a regression compared to previous Ubuntu
versions where I never saw such errors during backup.

Whether PAM is the appropriate package to report this bug against I'm
not sure, so please feel free to assign it to the correct package.

If this is intentional, does anybody have a clue how to work around this
for use cases like backup with rsync?

Kind regards,
Jan

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libpam-runtime 1.3.1-5ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 20 12:11:32 2020
InstallationDate: Installed on 2020-04-08 (11 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
PackageArchitecture: all
SourcePackage: pam
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Description changed:

  Hello,
  
  in Focal the behaviour has changed when a program running as root tries
  to modify a file which belongs to a user/group other than root in a
  directory with sticky bit set.
  
  I'm not sure if this is a bug or the behaviour is intentional (for
  certain security reasons).
  
  Steps to reproduce:
  
  - Boot current Focal daily iso
  - Open terminal
  - Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
  - Create an empty file with user:group set to anything different that root 
(e.g. ubuntu:ubuntu, ubuntu:whoospie, ...)
  - Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.
  
  This behaviour is different than in previous Ubuntu versions. In Eoan it
  is possible to modify the file as root in the scenario described above.
  
  I discovered this because after changing my main installation to Eoan I
  noticed that I got weird error messages from rsync when backing up my
  root subvolume. In my backup script rsync runs as root, and can't update
  backed up contents of /var/crash or /var/spool/cups/tmp anymore because
  it isn't allowed to modify the respective files anymore.
  
  For me personally this is a regression compared to previous Ubuntu
  versions where I never saw such errors during backup.
  
  Whether PAM is the appropriate package to report this bug against I'm
  not sure, so please feel free to assign it to the correct package.
  
- If this is intentional, does anybode have a clue how to work around this
+ If this is intentional, does anybody have a clue how to work around this
  for use cases like backup with rsync?
  
  Kind regards,
  Jan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 12:11:32 2020
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Root can't modify files of other users in directories with sticky bit
  anymore

Status in pam package in

[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working

2020-04-20 Thread Raz Ziv

I'm also affected. "Intel corporation: Wireless 8260" on 19.10

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

Title:
  software-properties-gtk erroneously reports that Intel Wireless-AC
  9260 device is not working

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 has broken dhcp based NTP updates

Forwarded the systemd part: https://salsa.debian.org/systemd-
team/systemd/-/merge_requests/89

The systemd part only emits an error from the dhclient hook, thus the DHCP 
based NTP updates are not broken.
I'll fix systemd in the next update after Focal's release.

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: systemd (Ubuntu Eoan)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

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

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

Title:
  245.4-2ubuntu1 has broken dhcp based NTP updates

Status in chrony package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in chrony source package in Bionic:
  New
Status in systemd source package in Bionic:
  Invalid
Status in chrony source package in Eoan:
  New
Status in systemd source package in Eoan:
  Invalid

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

2020-04-20 Thread Dan Streetman

Are you able to manually trigger the segfault by running 'sudo systemctl
daemon-reload' ?

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd package in Ubuntu:
  New

Bug description:
  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic 
root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-cosmic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-cosmic
  dmi.sys.vendor: QEMU
  mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328

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

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

[Touch-packages] [Bug 1873536] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@2512:main:run:conffile_prompt

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Invalid

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

Title:
  /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-
  upgrade@2512:main:run:conffile_prompt

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1983, in main
  res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2232, in run
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 1236, in conffile_prompt
  deb = apt_inst.DebFile(destFile)
  apt_pkg.Error: E:Invalid archive signature

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
2.3, the problem page at 
https://errors.ubuntu.com/problem/6889811b0d0f066ff5789f7b90b61056bf2fa859 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

2020-04-20 Thread Hontvári József Levente

Yes, it worked that way. Thank you!

For the record:
The most simple, currently working way to create a private, unsigned directory:

  cd /srv/deb
  apt-ftparchive packages . > Packages
  apt-ftparchive release . > Release

Assuming that the document root of the HTTP server is /srv/ and deb is
the directory with your .deb files.

on your machines which will use the repo:
  
  nano /etc/apt/sources.list.d/myserver
insert into the file:
  deb [trusted=yes] http://myserver:/deb/ /

Assuming that the host name of your HTTP server is myserver.

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

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

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

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

[Touch-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails

2020-04-20 Thread Dan Streetman

** Description changed:

+ [impact]
+ 
+ TEST-21-SYSUSERS autopkgtest fails
+ 
+ [test case]
+ 
+ see original description
+ 
+ [regression potential]
+ 
+ any regression would be limited to incorrect pass/fail of
+ TEST-21-SYSUSERS
+ 
+ [scope]
+ 
+ TEST-21-SYSUSERS does not exist in Xenial, it is first contained in
+ Bionic.  This is needed for B, E, and F.
+ 
+ [original description]
+ 
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz
  
  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  
  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  TEST-21-SYSUSERS autopkgtest fails

  [test case]

  see original description

  [regression potential]

  any regression would be limited to incorrect pass/fail of
  TEST-21-SYSUSERS

  [scope]

  TEST-21-SYSUSERS does not exist in Xenial, it is first contained in
  Bionic.  This is needed for B, E, and F.

  [original description]

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

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

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

[Touch-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04

Do you only see this when running the installer in "Try" mode?

** Changed in: gdebi (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Deb Files are not opened by the installer 20.04

Status in gdebi package in Ubuntu:
  Incomplete

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

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

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

[Touch-packages] [Bug 1801540]

2020-04-20 Thread adam.reichold

The problem still seems to affect Raven Ridge ([1022:15e3] in a HP
ProBook 455R G6) using kernel version 5.6.4.

Disabling the SNDRV_PCM_INFO_BATCH workaround subjectively improves
capture quality using `parecord` but it is not really usable either way.

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-20 Thread Alberto Milone

I have just updated an Eoan installation to Focal, enabled auto-login,
and I can't reproduce the problem. I am using the 440.64 driver, and
nvidia-drm.modeset is disabled. I can also see the bootsplash.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

2020-04-20 Thread Paolo Pisati

Here is a test kernel, could you test it and tell us if it fixes your
problem?

https://people.canonical.com/~ppisati/lp1871182/

linux-image-unsigned-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb
linux-modules-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb
linux-modules-extra-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb

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

Title:
  [RTL810xE] No ethernet connection

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04

2020-04-20 Thread Peter Jones

Hi Brian,

No. After installing.  I am doing the 'minimum install' as normal.

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

Title:
  Deb Files are not opened by the installer 20.04

Status in gdebi package in Ubuntu:
  Incomplete

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

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

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

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

2020-04-20 Thread Harry Coin

Just tried it three times, all normal, nothing in the logs except a few
netfilter reports of correctly dropped packets.

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd package in Ubuntu:
  New

Bug description:
  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic 
root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-cosmic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-cosmic
  dmi.sys.vendor: QEMU
  mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328

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

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

[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

** Tags added: regression-release

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

Title:
  [RTL810xE] No ethernet connection

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1870589] Re: test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic

2020-04-20 Thread Dan Streetman

** Description changed:

  [impact]
  
  test case failure
  
  [test case]
  
  check autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz
  
  /* test_restrict_suid_sgid */
  Failed to add suid/sgid rule for architecture arm64, skipping: Numerical 
argument out of domain
  Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at 
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
  suidsgidseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function 
test_restrict_suid_sgid(). Aborting.
  FAIL: test-seccomp (code: 134)
  Aborted (core dumped)
  
  [regression potential]
  
- TBD
+ this improves the function that (tries to) install seccomp suid/sgid
+ filters, so and regression would involve failure to restrict suid/sgid
+ with seccomp filters; however on arm64, the this functionality already
+ fails 100% of the time (which is what the failed test case was pointing
+ out).
  
  [scope]
  
  this appears to fail only in Bionic, and this specific testcase was
  backported in patch CVE-2019-384x-2.patch.  It does not appear that it
  ever passed in Bionic on arm64.
  
  [other info]
  
  systemd bionic arm64 autopkgtests have failed forever, but we should fix
  that.

** Description changed:

  [impact]
  
- test case failure
+ RestrictSUIDSGID (backported to Bionic in security CVE) fails 100% of
+ the time on arm64, and testcase failure indicates this as well.
  
  [test case]
  
  check autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz
  
  /* test_restrict_suid_sgid */
  Failed to add suid/sgid rule for architecture arm64, skipping: Numerical 
argument out of domain
  Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at 
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
  suidsgidseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function 
test_restrict_suid_sgid(). Aborting.
  FAIL: test-seccomp (code: 134)
  Aborted (core dumped)
  
  [regression potential]
  
  this improves the function that (tries to) install seccomp suid/sgid
  filters, so and regression would involve failure to restrict suid/sgid
  with seccomp filters; however on arm64, the this functionality already
  fails 100% of the time (which is what the failed test case was pointing
  out).
  
  [scope]
  
- this appears to fail only in Bionic, and this specific testcase was
- backported in patch CVE-2019-384x-2.patch.  It does not appear that it
- ever passed in Bionic on arm64.
+ this fails only in Bionic, and this specific feature and testcase was
+ backported in patches for CVE-2019-384x.  It does not appear that the
+ backported feature, or its testcase, ever passed in Bionic on arm64.
  
  [other info]
  
  systemd bionic arm64 autopkgtests have failed forever, but we should fix
  that.

** Changed in: systemd (Ubuntu Bionic)
   Importance: Low => Medium

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

Title:
  test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  RestrictSUIDSGID (backported to Bionic in security CVE) fails 100% of
  the time on arm64, and testcase failure indicates this as well.

  [test case]

  check autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz

  /* test_restrict_suid_sgid */
  Failed to add suid/sgid rule for architecture arm64, skipping: Numerical 
argument out of domain
  Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at 
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
  suidsgidseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function 
test_restrict_suid_sgid(). Aborting.
  FAIL: test-seccomp (code: 134)
  Aborted (core dumped)

  [regression potential]

  this improves the function that (tries to) install seccomp suid/sgid
  filters, so and regression would involve failure to restrict suid/sgid
  with seccomp filters; however on arm64, the this functionality already
  fails 100% of the time (which is what the failed test case was

[Touch-packages] [Bug 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

2020-04-20 Thread Dan Watkins

cloud-init has support for ubuntu-drivers, it's not clear from this bug
what work we would need to do so I've marked our task Incomplete.

** Changed in: cloud-init
   Status: New => Incomplete

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

Title:
  Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

Status in cloud-init:
  Incomplete
Status in MAAS:
  Triaged
Status in subiquity:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Could subiquity provide an option in the UI to install and execute
  ubuntu-drivers-common on the target? The use case I'm interested in is
  an "on-rails" installation of Nvidia drivers for servers being
  installed for deep learning workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1872124/+subscriptions

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

[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

2020-04-20 Thread alex

@Paolo, the test kernel does fix the problem for me.

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

Title:
  [RTL810xE] No ethernet connection

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors

The packages upgraded on the second laptop that are libx related are:

$ grep 'Upgrade: hunspell' /var/log/apt/history.log  | grep -o 'libx[^ ]*'
libxml2-utils:amd64
libxml2:amd64
libxatracker2:amd64
libxcomposite1:amd64
libxcomposite1:i386
libxml2-dev:amd64
libxfixes3:amd64
libxfixes3:i386
libxdamage1:amd64
libxdamage1:i386
libxml2:amd64
libxml2:i386
libxres1:amd64

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.

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

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

[Touch-packages] [Bug 1873895] [NEW] Regression: block staircase display with side-by-side monitors

Public bug reported:

Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that is having package upgrades applied
regularly.

With dual monitors and the external monitor placed left or right the
display has a blocked staircase effect shown in the attached photograph,
and seems related to

https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10

More detailed investigation suggests it only happens when the X
coordinate of the two monitors is different. The symptom looks like an
off-by-one error because it appears as if the display is divided into,
say, 10 rows and 15 columns but the first row has 16 'columns' worth of
blocks on it and so wraps to the beginning of the 2nd row, and so on.

On the laptop without package upgrades being applied this didn't happen.
So I upgraded it (314 packages) and restarted and it too sees the same
problem.

I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
that didn't solve it.

I now suspect libxcb but so far haven't been able to prove it.

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

** Attachment added: "Blocked Staircase across two monitors"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357157/+files/IMG_0023.JPG

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.

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

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

[Touch-packages] [Bug 1873559] Re: O audio do meu Ubuntu não esta funcionando

2020-04-20 Thread Mike Salvatore

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  O audio do meu Ubuntu não esta funcionando

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Conectei os fones de ouvido no meu Ubuntu e depois de um tempo ou um
  som parar de funcionar, tanto com os fones quanto com o falante
  automático

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

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

[Touch-packages] [Bug 1872947] Re: The computer powers off even before the critical or low battery percentage is reached and no low power indication is shown. It shutsdown abruptly.

2020-04-20 Thread Sebastien Bacher

Thank you for your bug report. Could you add a 'journalctl' log from the
session which had the issue?

Is your battery working correctly or does it see drops between levels?

Is it possible to reproduce the issue? If so it would be useful to get a low of 
levels as reported by upower
$ while :; do upower -d | grep perc >> log; sleep 30; done
Then add 'log' after hitting the issue


** Package changed: indicator-power (Ubuntu) => upower (Ubuntu)

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

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

Title:
  The computer powers off even before the critical or low battery
  percentage is reached and no low power indication is shown. It
  shutsdown abruptly.

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  The computer powers off even before the critical or low battery
  percentage is reached and no low power indication is shown. It shuts
  down abruptly.

  Tried to reinstall the package through apt to fix the problem, but no
  avail. This is most probably a bug in the indicator-power package.

  
  Info about release:

  OS   Ubuntu Focal Fossa (development branch)
  GNOME Version3.36.1
  OS Type  64 bit

  
  indicator-power:

Installed: 12.10.6+17.10.20170829.1-0ubuntu5
Candidate: 12.10.6+17.10.20170829.1-0ubuntu5
Version table:
   *** 12.10.6+17.10.20170829.1-0ubuntu5 500
  500 http://in.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: indicator-power 12.10.6+17.10.20170829.1-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 15:29:24 2020
  InstallationDate: Installed on 2020-04-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore

2020-04-20 Thread Jan Rathmann

As additional information, I tested if using the Eoan kernel with Focal
would do any difference on this - it didn't, so this seems not to be
dependent on the kernel version in Focal.

** Description changed:

  Hello,
  
  in Focal the behaviour has changed when a program running as root tries
  to modify a file which belongs to a user/group other than root in a
  directory with sticky bit set.
  
  I'm not sure if this is a bug or the behaviour is intentional (for
  certain security reasons).
  
  Steps to reproduce:
  
  - Boot current Focal daily iso
  - Open terminal
  - Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
- - Create an empty file with user:group set to anything different that root 
(e.g. ubuntu:ubuntu, ubuntu:whoospie, ...)
+ - Create an empty file with user:group set to anything different than root 
(e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...)
  - Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.
  
  This behaviour is different than in previous Ubuntu versions. In Eoan it
  is possible to modify the file as root in the scenario described above.
  
  I discovered this because after changing my main installation to Eoan I
  noticed that I got weird error messages from rsync when backing up my
  root subvolume. In my backup script rsync runs as root, and can't update
  backed up contents of /var/crash or /var/spool/cups/tmp anymore because
  it isn't allowed to modify the respective files anymore.
  
  For me personally this is a regression compared to previous Ubuntu
  versions where I never saw such errors during backup.
  
  Whether PAM is the appropriate package to report this bug against I'm
  not sure, so please feel free to assign it to the correct package.
  
  If this is intentional, does anybody have a clue how to work around this
  for use cases like backup with rsync?
  
  Kind regards,
  Jan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 12:11:32 2020
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Root can't modify files of other users in directories with sticky bit
  anymore

Status in pam package in Ubuntu:
  New

Bug description:
  Hello,

  in Focal the behaviour has changed when a program running as root
  tries to modify a file which belongs to a user/group other than root
  in a directory with sticky bit set.

  I'm not sure if this is a bug or the behaviour is intentional (for
  certain security reasons).

  Steps to reproduce:

  - Boot current Focal daily iso
  - Open terminal
  - Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
  - Create an empty file with user:group set to anything different than root 
(e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...)
  - Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.

  This behaviour is different than in previous Ubuntu versions. In Eoan
  it is possible to modify the file as root in the scenario described
  above.

  I discovered this because after changing my main installation to Eoan
  I noticed that I got weird error messages from rsync when backing up
  my root subvolume. In my backup script rsync runs as root, and can't
  update backed up contents of /var/crash or /var/spool/cups/tmp anymore
  because it isn't allowed to modify the respective files anymore.

  For me personally this is a regression compared to previous Ubuntu
  versions where I never saw such errors during backup.

  Whether PAM is the appropriate package to report this bug against I'm
  not sure, so please feel free to assign it to the correct package.

  If this is intentional, does anybody have a clue how to work around
  this for use cases like backup with rsync?

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 12:11:32 2020
  InstallationDate: Installed o

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors

These are the packages I've tested via a downgrade:

$ apt list --upgradeable
Listing... Done
libxcomposite1/focal 1:0.4.5-1 amd64 [upgradable from: 1:0.4.5-0ubuntu1]
libxcomposite1/focal 1:0.4.5-1 i386 [upgradable from: 1:0.4.5-0ubuntu1]
libxdamage1/focal 1:1.1.5-2 amd64 [upgradable from: 1:1.1.5-1]
libxdamage1/focal 1:1.1.5-2 i386 [upgradable from: 1:1.1.5-1]
libxfixes3/focal 1:5.0.3-2 amd64 [upgradable from: 1:5.0.3-1]
libxfixes3/focal 1:5.0.3-2 i386 [upgradable from: 1:5.0.3-1]
linux-generic/focal 5.4.0.25.31 amd64 [upgradable from: 5.4.0.21.25]
linux-headers-generic/focal 5.4.0.25.31 amd64 [upgradable from: 5.4.0.21.25]
linux-image-generic/focal 5.4.0.25.31 amd64 [upgradable from: 5.4.0.21.25]
netplan.io/focal 0.99-0ubuntu1 amd64 [upgradable from: 0.98-0ubuntu4]

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.

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

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

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors

I'm attaching the complete list of packages upgraded on the second
laptop that triggered this bug.

The total list is over 300 packages. I've prefixed the unlikely package
with #. That leaves 77 possibles all related to X server or display
drivers.

** Attachment added: "List of upgraded packages with unlikely's prefixed #"
   
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1873895/+attachment/5357163/+files/upgrade.list

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.

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

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

[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

2020-04-20 Thread Ryan Amick

Ethernet stopped working again after update today.
@vicamo here are the results for would you suggested in #8. It does appear that 
realtek.ko was included automatically for me but still not working.

finisdiem@finisdiem-HP-Pavilion-g6-Notebook-PC:~$ sudo modprobe -r realtek
[sudo] password for finisdiem: 
finisdiem@finisdiem-HP-Pavilion-g6-Notebook-PC:~$ sudo update-initramfs -v -u
Available versions: 5.4.0-25-generic
5.4.0-24-generic
5.4.0-23-generic
5.4.0-22-generic
5.4.0-21-generic
Keeping /boot/initrd.img-5.4.0-25-generic.dpkg-bak
update-initramfs: Generating /boot/initrd.img-5.4.0-25-generic
Copying module directory kernel/drivers/usb/host
(excluding hwa-hc.ko sl811_cs.ko sl811-hcd.ko u132-hcd.ko whci-hcd.ko)
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/ehci-fsl.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/isp116x-hcd.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/ssb/ssb.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/ssb-hcd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/fotg210-hcd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/max3421-hcd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/r8a66597-hcd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/oxu210hp-hcd.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/bcma/bcma.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/bcma-hcd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/host/fsl-mph-dr-of.ko
Copying module directory kernel/drivers/usb/c67x00
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/c67x00/c67x00.ko
Copying module directory kernel/drivers/usb/chipidea
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/gadget/udc/udc-core.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/common/ulpi.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/roles/roles.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/phy/phy-generic.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/chipidea/ci_hdrc.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/chipidea/ci_hdrc_pci.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/chipidea/ci_hdrc_msm.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/chipidea/ci_hdrc_usb2.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/chipidea/ci_hdrc_zevio.ko
Copying module directory kernel/drivers/usb/dwc2
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/dwc2/dwc2_pci.ko
Copying module directory kernel/drivers/usb/dwc3
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/dwc3/dwc3-haps.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/dwc3/dwc3.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/dwc3/dwc3-pci.ko
Copying module directory kernel/drivers/usb/isp1760
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/usb/isp1760/isp1760.ko
Copying module directory kernel/drivers/usb/musb
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/usb/musb/musb_hdrc.ko
Copying module directory kernel/drivers/input/keyboard
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/sunkbd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/gpio_keys.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/adp5588-keys.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/matrix-keymap.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/twl4030_keypad.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/input-polldev.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/gpio_keys_polled.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/lkkbd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/qt2160.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/matrix_keypad.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/tca6416-keypad.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/adp5520-keys.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/adp5589-keys.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/xtkbd.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/mcs_touchkey.ko
Adding module /lib/modules/5.4.0-25-generic/kernel/drivers/iio/industrialio.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/adc-keys.ko
Adding module 
/lib/modules/5.4.0-25-generic/kernel/drivers/input/keyboard/opencores-kbd.ko
Adding module 
/lib/modules/

[Touch-packages] [Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore

This doesn't come from pam, but from procps / systemd which now set
fs.protected_regular by default to block uid mismatches in sticky
directories.  See /usr/lib/sysctl.d/protect-links.conf.

** Package changed: pam (Ubuntu) => procps (Ubuntu)

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

Title:
  Root can't modify files of other users in directories with sticky bit
  anymore

Status in procps package in Ubuntu:
  New

Bug description:
  Hello,

  in Focal the behaviour has changed when a program running as root
  tries to modify a file which belongs to a user/group other than root
  in a directory with sticky bit set.

  I'm not sure if this is a bug or the behaviour is intentional (for
  certain security reasons).

  Steps to reproduce:

  - Boot current Focal daily iso
  - Open terminal
  - Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
  - Create an empty file with user:group set to anything different than root 
(e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...)
  - Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.

  This behaviour is different than in previous Ubuntu versions. In Eoan
  it is possible to modify the file as root in the scenario described
  above.

  I discovered this because after changing my main installation to Eoan
  I noticed that I got weird error messages from rsync when backing up
  my root subvolume. In my backup script rsync runs as root, and can't
  update backed up contents of /var/crash or /var/spool/cups/tmp anymore
  because it isn't allowed to modify the respective files anymore.

  For me personally this is a regression compared to previous Ubuntu
  versions where I never saw such errors during backup.

  Whether PAM is the appropriate package to report this bug against I'm
  not sure, so please feel free to assign it to the correct package.

  If this is intentional, does anybody have a clue how to work around
  this for use cases like backup with rsync?

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 12:11:32 2020
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore

See also the discussion on ubuntu-devel about this behavior change:
https://lists.ubuntu.com/archives/ubuntu-devel/2020-February/040904.html

** Tags added: ff-incoming

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

Title:
  Root can't modify files of other users in directories with sticky bit
  anymore

Status in procps package in Ubuntu:
  New

Bug description:
  Hello,

  in Focal the behaviour has changed when a program running as root
  tries to modify a file which belongs to a user/group other than root
  in a directory with sticky bit set.

  I'm not sure if this is a bug or the behaviour is intentional (for
  certain security reasons).

  Steps to reproduce:

  - Boot current Focal daily iso
  - Open terminal
  - Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
  - Create an empty file with user:group set to anything different than root 
(e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...)
  - Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.

  This behaviour is different than in previous Ubuntu versions. In Eoan
  it is possible to modify the file as root in the scenario described
  above.

  I discovered this because after changing my main installation to Eoan
  I noticed that I got weird error messages from rsync when backing up
  my root subvolume. In my backup script rsync runs as root, and can't
  update backed up contents of /var/crash or /var/spool/cups/tmp anymore
  because it isn't allowed to modify the respective files anymore.

  For me personally this is a regression compared to previous Ubuntu
  versions where I never saw such errors during backup.

  Whether PAM is the appropriate package to report this bug against I'm
  not sure, so please feel free to assign it to the correct package.

  If this is intentional, does anybody have a clue how to work around
  this for use cases like backup with rsync?

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 12:11:32 2020
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors

2020-04-20 Thread Timo Aaltonen

as you can see we already had the upstream versions of those libs, so
they didn't break it

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.

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

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

[Touch-packages] [Bug 1873907] [NEW] initramfs no dhcp because of 'Error getting hardware address for " en2s0": No such device'

2020-04-20 Thread Thorsten Bonhagen

Public bug reported:

kernel cmdline "ip=dhcp"

results in: 
Error getting hardware address for " en2s0": No such device
No network during boot

I have to change /usr/share/initramfs-tools/scripts/functions

fix:
run_dhclient() {
...
dhclient -v -1 -cf "$conffile" -pf "$pidfile" "$@"
to 
dhclient -v -1 -cf "$conffile" -pf "$pidfile" $@

regards

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: initramfs-tools-core 0.136ubuntu6 [modified: 
usr/share/initramfs-tools/hook-functions 
usr/share/initramfs-tools/scripts/functions]
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 20 18:49:00 2020
InstallationDate: Installed on 2020-04-18 (2 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  initramfs no dhcp because of 'Error getting hardware address for "
  en2s0": No such device'

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  kernel cmdline "ip=dhcp"

  results in: 
  Error getting hardware address for " en2s0": No such device
  No network during boot

  I have to change /usr/share/initramfs-tools/scripts/functions

  fix:
  run_dhclient() {
  ...
  dhclient -v -1 -cf "$conffile" -pf "$pidfile" "$@"
  to 
  dhclient -v -1 -cf "$conffile" -pf "$pidfile" $@

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools-core 0.136ubuntu6 [modified: 
usr/share/initramfs-tools/hook-functions 
usr/share/initramfs-tools/scripts/functions]
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 18:49:00 2020
  InstallationDate: Installed on 2020-04-18 (2 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04

2020-04-20 Thread Peter Jones

I enclose a screen grab to show the issue.  This is 20.04 Beta installed
with minimal install.

** Attachment added: "Deb Files.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357184/+files/Deb%20Files.PNG

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

Title:
  Deb Files are not opened by the installer 20.04

Status in gdebi package in Ubuntu:
  Incomplete

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

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

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

[Touch-packages] [Bug 1817077] Re: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128

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

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

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

Title:
  package linux-image-4.15.0-44-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2
  exited with return code 128

Status in debconf package in Ubuntu:
  Confirmed
Status in grub-legacy-ec2 package in Ubuntu:
  Incomplete

Bug description:
  I applied an system update and was presented with this error after the
  next login.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Feb 14 00:00:24 2019
  ErrorMessage: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with 
return code 128
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=36f6b4c3-1f42-11e9-99c9-00155d195067 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  RfKill:
   
  SourcePackage: grub-legacy-ec2
  Title: package linux-image-4.15.0-44-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with 
return code 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0298-0271-9062-6147-4258-1509-89
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Touch-packages] [Bug 1873920] [NEW] default vi on focal emits escape sequences unrecognized by bionic's terminal?

2020-04-20 Thread Dan Kegel

Public bug reported:

On ubuntu 18.04, opening the default terminal (gnome-terminal
3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04 system,
running 'vi', and pressing 'i' shows the unwelcome garbage ESC [>4;m.
Pressing ESC emits more garbage: ESC [>4;2m

Focal's default vi is provided by vim.tiny via alternatives.  Oddly,
when running vim.tiny by itself, or if you install vim and let it
provide vi, the garbage does not appear.

Evidently focal's vim.tiny is confused about what escape sequences
ubu1804's Terminal accepts.

TERM is xterm-256color.  The problem also occurs if TERM is xterm.

There is no .vimrc.

If I use xterm on ubuntu 18.04, all is well.  Evidently xterm accepts
ESC[>4;m and gnome-terminal doesn't?

I captured a session using 'script' and dumped typescript via hexdump -C. 
In this session, I typed i, Q, and escape. Here's an excerpt
showing the end of vi's welcome message, followed by five escape sequences
and then the Q I typed.  The unrecognized ESC > 4;m is visible in the dump,
followed by ESC[?25l (CURSOR OFF)

1070  66 61 75 6c 74 1b 5b 33  34 6d 3c 45 6e 74 65 72  |fault.[34m.[m for info on|
1090  20 74 68 69 73 1b 5b 31  3b 31 48 1b 5b 3f 32 35  | this.[1;1H.[?25|
10a0  68 1b 5b 3f 32 30 30 34  6c 1b 5b 3e 34 3b 6d 1b  |h.[?2004l.[>4;m.|
10b0  5b 3f 32 35 6c 51 1b 5b  38 3b 34 37 48 1b 5b 31  |[?25lQ.[8;47H.[1|

The mystery sequence ESC [ > 4;m appears to be "Set/reset key modifier options, 
xterm",
per https://invisible-island.net/xterm/ctlseqs/ctlseqs.html.  So it's trying
to modify function keys, or something.

ssh'ing in from a mac worked fine (TERM there was also xterm-256color),
as did ssh'ing from an ubuntu 19.04 system with gnome-terminal.
ssh'ing from another ubuntu 18.04 system exhibited the same problem.

So it's a little family squabble between focal's vim.tiny and ubuntu
18.04/bionic's gnome-terminal...?

Given how long 18.04's going to be supported, this seems worth resolving
somehow.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vim-tiny 2:8.1.2269-1ubuntu5 [modified: 
usr/share/vim/vim81/doc/help.txt usr/share/vim/vim81/doc/tags]
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr 20 09:27:50 2020
InstallationDate: Installed on 2020-01-27 (83 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: vim (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 vim in Ubuntu.
https://bugs.launchpad.net/bugs/1873920

Title:
  default vi on focal emits escape sequences unrecognized by bionic's
  terminal?

Status in vim package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04, opening the default terminal (gnome-terminal
  3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04
  system, running 'vi', and pressing 'i' shows the unwelcome garbage ESC
  [>4;m.  Pressing ESC emits more garbage: ESC [>4;2m

  Focal's default vi is provided by vim.tiny via alternatives.  Oddly,
  when running vim.tiny by itself, or if you install vim and let it
  provide vi, the garbage does not appear.

  Evidently focal's vim.tiny is confused about what escape sequences
  ubu1804's Terminal accepts.

  TERM is xterm-256color.  The problem also occurs if TERM is xterm.

  There is no .vimrc.

  If I use xterm on ubuntu 18.04, all is well.  Evidently xterm accepts
  ESC[>4;m and gnome-terminal doesn't?

  I captured a session using 'script' and dumped typescript via hexdump -C. 
  In this session, I typed i, Q, and escape. Here's an excerpt
  showing the end of vi's welcome message, followed by five escape sequences
  and then the Q I typed.  The unrecognized ESC > 4;m is visible in the dump,
  followed by ESC[?25l (CURSOR OFF)

  1070  66 61 75 6c 74 1b 5b 33  34 6d 3c 45 6e 74 65 72  |fault.[34m.[m for info on|
  1090  20 74 68 69 73 1b 5b 31  3b 31 48 1b 5b 3f 32 35  | this.[1;1H.[?25|
  10a0  68 1b 5b 3f 32 30 30 34  6c 1b 5b 3e 34 3b 6d 1b  |h.[?2004l.[>4;m.|
  10b0  5b 3f 32 35 6c 51 1b 5b  38 3b 34 37 48 1b 5b 31  |[?25lQ.[8;47H.[1|

  The mystery sequence ESC [ > 4;m appears to be "Set/reset key modifier 
options, xterm",
  per https://invisible-island.net/xterm/ctlseqs/ctlseqs.html.  So it's trying
  to modify function keys, or something.

  ssh'ing in from a mac worked fine (TERM there was also xterm-256color),
  as did ssh'ing from an ubuntu 19.04 system with gnome-terminal.
  ssh'ing from another ubuntu 18.04 system exhibited the same problem.

  So it's a little family squabble between focal's vim.tiny and ubuntu
  18.04/bionic's gnome-terminal...?

  Given how long 18.04's going to be supported, this seems w

[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

2020-04-20 Thread Ryan Amick

@Paolo, test kernel didn't work for me. I had to reinstall official
Realtek driver again like i did in #3.

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

Title:
  [RTL810xE] No ethernet connection

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore

** Tags removed: ff-incoming
** Tags added: rls-ff-incoming

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

Title:
  Root can't modify files of other users in directories with sticky bit
  anymore

Status in procps package in Ubuntu:
  New

Bug description:
  Hello,

  in Focal the behaviour has changed when a program running as root
  tries to modify a file which belongs to a user/group other than root
  in a directory with sticky bit set.

  I'm not sure if this is a bug or the behaviour is intentional (for
  certain security reasons).

  Steps to reproduce:

  - Boot current Focal daily iso
  - Open terminal
  - Create a directory with sticky bit set (chmod o+t; or use an existing 
directory with sticky bit, e.g. /var/crash )
  - Create an empty file with user:group set to anything different than root 
(e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...)
  - Open the file with nano running as root (sudo nano testfile.txt), write 
something in it, and try to save it. This won't work and gives a "permission 
denied" error message.

  This behaviour is different than in previous Ubuntu versions. In Eoan
  it is possible to modify the file as root in the scenario described
  above.

  I discovered this because after changing my main installation to Eoan
  I noticed that I got weird error messages from rsync when backing up
  my root subvolume. In my backup script rsync runs as root, and can't
  update backed up contents of /var/crash or /var/spool/cups/tmp anymore
  because it isn't allowed to modify the respective files anymore.

  For me personally this is a regression compared to previous Ubuntu
  versions where I never saw such errors during backup.

  Whether PAM is the appropriate package to report this bug against I'm
  not sure, so please feel free to assign it to the correct package.

  If this is intentional, does anybody have a clue how to work around
  this for use cases like backup with rsync?

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-runtime 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 20 12:11:32 2020
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873926] Re: Super button and Ctrl not working with Bulgarian keyboard since upgrade to focal

2020-04-20 Thread Lyubomir Parvanov

** Attachment added: "xkbmap.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873926/+attachment/5357229/+files/xkbmap.txt

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

Title:
  Super button and Ctrl not working with Bulgarian keyboard since
  upgrade to focal

Status in systemd package in Ubuntu:
  New

Bug description:
  Since i upgraded from eoan to focal, the Super button doesn't show
  Activities anymore when keyboard is set to Bulgarian. Also Ctrl + D
  and Ctrl + C don't work in terminal when keyboard is in Bulgarian
  (though i am not sure about these 2 whether this worked on eoan). Ctrl
  + Alt + T works both in Bulgarian and English US keyboard. I've
  checked keycodes with evtest and they look correct and the same for
  both Ctrl And Super, in both Bulgarian and English.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
  Uname: Linux 5.4.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.authy.rules 70-snap.thunderbird.rules 
70-snap.core.rules
  Date: Mon Apr 20 20:37:50 2020
  InstallationDate: Installed on 2020-02-08 (72 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1873926] Re: Super button and Ctrl not working with Bulgarian keyboard since upgrade to focal

2020-04-20 Thread Lyubomir Parvanov

** Attachment added: "lsinput.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873926/+attachment/5357230/+files/lsinput.log

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

Title:
  Super button and Ctrl not working with Bulgarian keyboard since
  upgrade to focal

Status in systemd package in Ubuntu:
  New

Bug description:
  Since i upgraded from eoan to focal, the Super button doesn't show
  Activities anymore when keyboard is set to Bulgarian. Also Ctrl + D
  and Ctrl + C don't work in terminal when keyboard is in Bulgarian
  (though i am not sure about these 2 whether this worked on eoan). Ctrl
  + Alt + T works both in Bulgarian and English US keyboard. I've
  checked keycodes with evtest and they look correct and the same for
  both Ctrl And Super, in both Bulgarian and English.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
  Uname: Linux 5.4.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.authy.rules 70-snap.thunderbird.rules 
70-snap.core.rules
  Date: Mon Apr 20 20:37:50 2020
  InstallationDate: Installed on 2020-02-08 (72 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1873926] [NEW] Super button and Ctrl not working with Bulgarian keyboard since upgrade to focal

2020-04-20 Thread Lyubomir Parvanov

Public bug reported:

Since i upgraded from eoan to focal, the Super button doesn't show
Activities anymore when keyboard is set to Bulgarian. Also Ctrl + D and
Ctrl + C don't work in terminal when keyboard is in Bulgarian (though i
am not sure about these 2 whether this worked on eoan). Ctrl + Alt + T
works both in Bulgarian and English US keyboard. I've checked keycodes
with evtest and they look correct and the same for both Ctrl And Super,
in both Bulgarian and English.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: udev 245.4-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
Uname: Linux 5.4.0-25-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.authy.rules 70-snap.thunderbird.rules 
70-snap.core.rules
Date: Mon Apr 20 20:37:50 2020
InstallationDate: Installed on 2020-02-08 (72 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
 Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire A515-51G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charmander_KL
dmi.board.vendor: KBL
dmi.board.version: V2.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.02
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-51G
dmi.product.sku: 
dmi.product.version: V2.02
dmi.sys.vendor: Acer

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1873926

Title:
  Super button and Ctrl not working with Bulgarian keyboard since
  upgrade to focal

Status in systemd package in Ubuntu:
  New

Bug description:
  Since i upgraded from eoan to focal, the Super button doesn't show
  Activities anymore when keyboard is set to Bulgarian. Also Ctrl + D
  and Ctrl + C don't work in terminal when keyboard is in Bulgarian
  (though i am not sure about these 2 whether this worked on eoan). Ctrl
  + Alt + T works both in Bulgarian and English US keyboard. I've
  checked keycodes with evtest and they look correct and the same for
  both Ctrl And Super, in both Bulgarian and English.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
  Uname: Linux 5.4.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.authy.rules 70-snap.thunderbird.rules 
70-snap.core.rules
  Date: Mon Apr 20 20:37:50 2020
  InstallationDate: Installed on 2020-02-08 (72 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~touch

[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 has broken chrony autopkgtest

** Summary changed:

- 245.4-2ubuntu1 has broken dhcp based NTP updates
+ 245.4-2ubuntu1 has broken chrony autopkgtest

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

Title:
  245.4-2ubuntu1 has broken chrony autopkgtest

Status in chrony package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in chrony source package in Bionic:
  New
Status in systemd source package in Bionic:
  Invalid
Status in chrony source package in Eoan:
  New
Status in systemd source package in Eoan:
  Invalid

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

As stated, this is believed to not be a bug in initramfs-tools, only in
the kernel for displaying a spurious message.  Hence the 'linux' bug
task is confirmed.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

> I am having the same trouble, but during INSTALLATION, I already
installed Ubuntu 20.04 twice and I haven't access to it yet.

That is not this bug.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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

[Touch-packages] [Bug 1870088] Re: xz-utils ftbfs in focal

** Also affects: xz-utils (Ubuntu Focal)
   Importance: High
   Status: Confirmed

** Tags removed: rls-ff-incoming

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

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Confirmed
Status in xz-utils source package in Focal:
  Confirmed
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

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

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

[Touch-packages] [Bug 1870073] Re: python-debian ftbfs in focal

Fixed in 0.1.36ubuntu1.

python-debian (0.1.36ubuntu1) focal; urgency=medium

  * lib/debian/doc-debtags: Change shebang to python3.
  * debian/rules: Fix a couple of missed references to "python".
  * debian/tests/python3-debian: fix lintian failure
"runtime-test-file-uses-installed-python-versions".

 -- Michael Hudson-Doyle   Wed, 08 Apr 2020
17:17:21 +1200


** Changed in: python-debian (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  python-debian ftbfs in focal

Status in python-debian package in Ubuntu:
  Fix Released

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963359
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963359/+files/buildlog_ubuntu-focal-amd64.python-debian_0.1.36build1_BUILDING.txt.gz

  the failure is this:

  /bin/sh: 1: lib/debian/doc-debtags: not found

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

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

[Touch-packages] [Bug 1872844] [NEW] Changing theme Light<->Standard doesn't restore the title bar color

You have been subscribed to a public bug:

This is Ubuntu 20.04 beta.

Start a program that has title bar. Try Firefox or whatever. Then navigate to 
settings->appearance.
Now set the theme to Standard, then Light - Firefox will now have white theme 
with dark titlebar.

Setting to Dark resets the bug.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: focal
-- 
Changing theme Light<->Standard doesn't restore the title bar color
https://bugs.launchpad.net/bugs/1872844
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

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

[Touch-packages] [Bug 1872844] Re: Changing theme Light<->Standard doesn't restore the title bar color

2020-04-20 Thread Sebastian Ramacher

vlc has no code to handle that. That's all done by Qt. Re-assigning
accordingly.

** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu)

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

Title:
  Changing theme Light<->Standard doesn't restore the title bar color

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  This is Ubuntu 20.04 beta.

  Start a program that has title bar. Try Firefox or whatever. Then navigate to 
settings->appearance.
  Now set the theme to Standard, then Light - Firefox will now have white theme 
with dark titlebar.

  Setting to Dark resets the bug.

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

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

[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  smartctl-validate is borked in a recent release

Status in lxd:
  Unknown
Status in MAAS:
  Triaged
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Bug (maybe?) details first, diatribe second.

  Bug Summary: multi-hdd / raid with multiple drives / multiple devices
  or something along those lines cannot be commissioned anymore: 2.4.x
  worked fine, 2.7.0 does not.

  Here is the script output of smartctl-validate:

  -
  # /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac)

  Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial 
'6842b2b0740e9900260e66c9220df4ac' not found!
  This indicates the storage device has been removed or the OS is unable to 
find it due to a hardware failure. Please re-commission this node to 
re-discover the storage devices, or delete this device manually.
  Given parameters:
  {'storage': {'argument_format': '{path
  }', 'type': 'storage', 'value': {'id_path': 
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i', 
'name': 'sda', 'physical_blockdevice_id': 33, 'serial': 
'6842b2b0740e9900260e66c9220df4ac'
  }
  }
  }
  Discovered storage devices: [
  {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': 
'6842b2b0740e9900260e66c9220df4ac'
  },
  {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': 
'6842b2b0740e9900260e66f924ecece0'
  },
  {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': 
'10092013112645'
  }
  ]
  Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
  }
  -
  -
  # /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0)
  Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial 
'6842b2b0740e9900260e66f924ecece0' not found!
  This indicates the storage device has been removed or the OS is unable to 
find it due to a hardware failure. Please re-commission this node to 
re-discover the storage devices, or delete this device manually.
  Given parameters: {'storage': {'argument_format': '{path
  }', 'type': 'storage', 'value': {'id_path': 
'/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i', 
'name': 'sdb', 'physical_blockdevice_id': 34, 'serial': 
'6842b2b0740e9900260e66f924ecece0'
  }
  }
  }
  Discovered storage devices: [
  {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': 
'6842b2b0740e9900260e66c9220df4ac'
  },
  {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': 
'6842b2b0740e9900260e66f924ecece0'
  },
  {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': 
'10092013112645'
  }
  ]
  Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1'
  }
  -

  You can see that it says the storage cannot be found and immediately
  lists it as a discovered device. It does it for both tests (one for
  each drive), and for both servers

  Bug Details:
  I had maas 2.4.x for the longest time over my journey (see below journey) and 
have never had any problems re-commissioning (or deleting and re-discovering 
over boot PXE) 2 of my servers (r610, r710).

  r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual 
disk.
  r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks

  So commission after commission trying to get through my journey, 0
  problems. After I finally get everything figured out on the juju,
  network/vlan, quad-nic end, I go to re-commission and I cannot.
  smartctl-validate fails on both, over and over again. I even destroyed
  and re-created the raid/VDs, still not.

  After spending so much time on it I remembered that it was the first
  time I had tried to re-commission these two servers since doing an
  upgrade from 2.4.x->2.7 in an effort to use the updated KVM
  integration to add a couple more guests. Once I got all everything
  figured out I went to re-commission everything and boom.

  [Upgrade path notes]
  In full disclosure, in case this matters. I was on apt install of 2.4.x and 
using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and 
did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to 
snap but do not know how to without losing all maas data and could not find 
docs on it, so a problem for another day. But in case that is part of the 
problem for some odd reason, I wanted to share.

  
  [Diatribe]
  My journey to get maas+juju+openstack+kubernets has been less then stellar. I 
have ran into problem after problem; albeit some of which were my own. I am so 
close, after spending the last 6 months on/off when I had time, and really 
hardcore the last 4 days. The last half day of which has

[Touch-packages] [Bug 1817077] Re: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128

2020-04-20 Thread dioulde balde

** Changed in: grub-legacy-ec2 (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: grub-legacy-ec2 (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  package linux-image-4.15.0-44-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2
  exited with return code 128

Status in debconf package in Ubuntu:
  Confirmed
Status in grub-legacy-ec2 package in Ubuntu:
  Confirmed

Bug description:
  I applied an system update and was presented with this error after the
  next login.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Feb 14 00:00:24 2019
  ErrorMessage: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with 
return code 128
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=36f6b4c3-1f42-11e9-99c9-00155d195067 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  RfKill:
   
  SourcePackage: grub-legacy-ec2
  Title: package linux-image-4.15.0-44-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with 
return code 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0298-0271-9062-6147-4258-1509-89
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps

** Also affects: apport (Ubuntu Focal)
   Importance: Undecided
   Status: Triaged

** Changed in: apport (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1

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

Title:
  ubuntu-bug doesn't know how to file bugs against snaps

Status in Snapcraft:
  New
Status in snapd:
  Triaged
Status in Snap Store:
  New
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Triaged

Bug description:
  Hello, I had problems with subiquity in the focal live server install
  image. I tried to use 'ubuntu-bug subiquity' to report the bug, but
  ubuntu-bug apparently cannot file bug reports against snaps.

  This is frustrating that users need to know which portions of Ubuntu
  are delivered via debs, which portions are delivered by snaps, and try
  to find a way to report bugs correctly.

  ubuntu-bug should know how to report bugs for Canonical software.

  Thanks

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

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

[Touch-packages] [Bug 1873528] Re: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order

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

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

Title:
  sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse
  lexographic order

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf'
  for use in Ubuntu cloud images.  I wanted to add a config file and see
  if I had done things correctly.  I assumed that the files were sourced
  lexographically (based on use of glob() in readconf.h) so that I could
  document how users could override our tuning.  But it appears from
  'sshd -T' output and observed behavior that the first file in
  /etc/sshd_config.d/ to define a parameter wins.  I see in 'sshd -ddd'
  output that they are parsed lexographically but it seems that their
  settings apply in reverse (or whichever comes first) if that makes
  sense.  I'd like to understand if this is correct behavior and get it
  documented.

  Steps to reproduce on focal with openssh-server 1:8.2p1-4:

  1. Create the following files in /etc/ssh/sshd_config.d/ with the content 
shown below:
  40-cloudimg-settings.conf:
ClientAliveInterval 110
PasswordAuthentication yes
PermitRootLogin no

  50-cloudimg-settings.conf:
ClientAliveInterval 120
PermitRootLogin yes

  60-cloudimg-settings.conf:
ClientAliveInterval 180

  2. Check what sshd thinks the values will be with 'sshd -T|grep -i 
clientaliveinterval' and 'sshd -T|grep permitrootlogin'
  clientaliveinterval 110
  permitrootlogin no

  (The tuning I cared about was ClientAliveInterval for my work but
  PermitRootLogin is easier to demonstrate)

  3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing 
behavior:
  debug2: load_server_config: filename /etc/ssh/sshd_config
  debug2: load_server_config: done config len = 296
  debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296
  debug2: /etc/ssh/sshd_config line 13: new include 
/etc/ssh/sshd_config.d/*.conf
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf
  debug2: load_server_config: done config len = 71
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting 
ClientAliveInterval 110
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting 
PasswordAuthentication yes
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting 
PermitRootLogin no
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf
  debug2: load_server_config: done config len = 46
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46
  debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting 
ClientAliveInterval 120
  debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting 
PermitRootLogin yes
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf
  debug2: load_server_config: done config len = 25
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25
  debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting 
ClientAliveInterval 180

  4. Set a root password and unlock the account.

  5. Attempt to ssh as root to the instance with a password.

  Observation:
   * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf 
and 'yes' in 50-foo.conf
   * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf 
and 'no' in 50-foo.conf

  It appears in 'sshd -ddd' output that files are parsed in lexographic
  order (40-foo.conf before 50-foo.conf) but the behavior observed
  indicates that the value set in 40-foo.conf overrides 50-foo.conf
  which is counter to expectations.

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

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

[Touch-packages] [Bug 1873942] [NEW] gnome-screenshot takes a screenshot of the wrong screen

You have been subscribed to a public bug:

I have a dual monitor setup, with the external monitor defined as the "primary" 
one (and the laptop one secondary).
When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
(Choosing an area on the laptop screen works OK.)

I use the vanilla Gnome session (with Wayland), installed with apt.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Mon Apr 20 20:58:46 2020
InstallationDate: Installed on 2020-04-11 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal wayland-session
-- 
gnome-screenshot takes a screenshot of the wrong screen
https://bugs.launchpad.net/bugs/1873942
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-20 Thread Mephi

Just a note to say that I found I had the same problem.
I documented it in the linked question: 
https://answers.launchpad.net/ubuntu/+question/689859

I'm happy to help gather more debug information if there's a problem
reproducing it.

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory

[Touch-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load

Still happening with 20.04

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

** Tags added: apport-collected focal

** Description changed:

  Every time my SSD is under heavy writing load (e.g. copying large files
  from a USB stick, or downloading an ISO from a fast website), the entire
  Ubuntu (Gnome) desktop, including mouse pointer, freezes.
  
  My computer is an Asus UX410UAK with a Micron 1100 SSD.
  guillaume@massada:~$ sudo dmidecode | grep -i UX
Version: UX410UAK.308
Product Name: UX410UAK
Family: UX
Product Name: UX410UAK
  guillaume@massada:~$ cat /proc/scsi/scsi
  Attached devices:
  Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: ATA  Model: Micron_1100_MTFD Rev: A020
Type:   Direct-AccessANSI  SCSI revision: 05
  
  This is a recurring problem, and has always been with this machine
  (including previous kernel and Ubuntu versions, at least for the past 2
  years).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  6 18:20:01 2020
  InstallationDate: Installed on 2018-07-28 (526 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  guillaume   1685 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-11 (9 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
+  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX410UAK
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-25-generic N/A
+  linux-backports-modules-5.4.0-25-generic  N/A
+  linux-firmware1.187
+ Tags:  focal wayland-session
+ Uname: Linux 5.4.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/17/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX410UAK.312
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX410UAK
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: ZenBook
+ dmi.product.name: UX410UAK
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  Desktop freezing while SSD under heavy load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every time my SSD is under heavy writing load (e.g. copying large
  files from a USB stick, or downloading an ISO from a fast website),
  the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes.

  My computer is an Asus UX410UAK with a Micron 1100 SSD.
  guillaume@massada:~$ sudo dmidecode | grep -i UX
Version: UX410UAK.308
Product Name: UX410UAK
Family: UX
Product Name: UX410UAK
  guillaume@massada:~$ cat /proc/scsi/scsi
  Attached devices:
  Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: ATA  Model: Micron_1100_MTFD Rev: A020
Type:   Direct-AccessANSI  SCSI revision: 05

  This is a recurring problem, and has always been with this machine
  (including previous kernel and Ubuntu versions, at least for the past
  2 years).

[Touch-packages] [Bug 1873942] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357323/+files/DpkgLog.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1873942/+attachment/5357333/+files/UdevDb.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357330/+files/ProcCpuinfoMinimal.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357325/+files/Lspci-vt.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357334/+files/XorgLog.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357327/+files/Lsusb-v.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357326/+files/Lsusb-t.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] Xrandr.txt

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1873942/+attachment/5357336/+files/Xrandr.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] [NEW] gnome-screenshot takes a screenshot of the wrong screen

Public bug reported:

I have a dual monitor setup, with the external monitor defined as the "primary" 
one (and the laptop one secondary).
When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
(Choosing an area on the laptop screen works OK.)

I use the vanilla Gnome session (with Wayland), installed with apt.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Mon Apr 20 20:58:46 2020
InstallationDate: Installed on 2020-04-11 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
DistUpgraded: Fresh install
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
 acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
 acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
InstallationDate: Installed on 2020-04-11 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX410UAK
Package: wayland (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Tags:  focal wayland-session ubuntu
Uname: Linux 5.4.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/17/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX410UAK.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX410UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: UX410UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug apport-collected focal ubuntu wayland-session

** Package changed: gnome-screenshot (Ubuntu) => wayland (Ubuntu)

** Tags added: apport-collected ubuntu

** Description changed:

  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)
  
  I use the vanilla Gnome session (with Wayland), installed with apt.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  Install

[Touch-packages] [Bug 1873942] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1873942/+attachment/5357324/+files/Lspci.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357337/+files/xdpyinfo.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] MonitorsUser.xml.txt

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357328/+files/MonitorsUser.xml.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357332/+files/ProcModules.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357331/+files/ProcInterrupts.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357322/+files/CurrentDmesg.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357335/+files/XorgLogOld.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873942] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1873942/+attachment/5357329/+files/ProcCpuinfo.txt

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

Title:
  gnome-screenshot takes a screenshot of the wrong screen

Status in wayland package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357346/+files/Dependencies.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357347/+files/DpkgLog.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1873895/+attachment/5357350/+files/Lspci.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] LightdmDisplayLog.txt

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357348/+files/LightdmDisplayLog.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors

apport information

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: apport-collected focal ubuntu

** Description changed:

  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades applied
  regularly.
  
  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached photograph,
  and seems related to
  
  https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
  
  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth of
  blocks on it and so wraps to the beginning of the 2nd row, and so on.
  
  On the laptop without package upgrades being applied this didn't happen.
  So I upgraded it (314 packages) and restarted and it too sees the same
  problem.
  
  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.
  
  I now suspect libxcb but so far haven't been able to prove it.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CasperMD5CheckResult: skip
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: focal
+ DistroRelease: Ubuntu 20.04
+ DistroVariant: ubuntu
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
+Subsystem: Lenovo ThinkPad E595 [17aa:5124]
+ InstallationDate: Installed on 2020-04-08 (11 days ago)
+ InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
+ MachineType: LENOVO 20NECTO1WW
+ Package: xserver-xorg-video-amdgpu 19.1.0-1
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
+ Tags:  focal ubuntu ubuntu
+ Uname: Linux 5.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
+ _MarkForUpload: True
+ dmi.bios.date: 12/23/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: R11ET32W (1.12 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20NECTO1WW
+ 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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad E495
+ dmi.product.name: 20NECTO1WW
+ dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
+ dmi.product.version: ThinkPad E495
+ dmi.sys.vendor: LENOVO
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.101-2
+ version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
+ version.libgl1-mesa-glx: libgl1-mesa-glx N/A
+ version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357345/+files/CurrentDmesg.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop

[Touch-packages] [Bug 1873895] LightdmLog.txt

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357349/+files/LightdmLog.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357354/+files/Lsusb-v.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357353/+files/Lsusb-t.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1873895/+attachment/5357355/+files/ProcCpuinfo.txt

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

Title:
  Regression: block staircase display with side-by-side monitors

Status in libxcb package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Two identical Lenovo E495 laptops with 20.04 installed. The problem
  occurred initially on the laptop that is having package upgrades
  applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  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.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873895] ProcCpuinfoMinimal.txt