date:20210803

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1938753, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1938753
   package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, 
»/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches 
auch in Paket pulseaudio 1:14.2-2ubuntu2 ist

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

Title:
  package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/share/bash-
  completion/completions/pulseaudio', which is also in package
  pulseaudio 1:14.2-2ubuntu2

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Crash occurred during apt upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio-utils 1:14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1695 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Aug  3 06:06:50 2021
  ErrorMessage: trying to overwrite 
'/usr/share/bash-completion/completions/pulseaudio', which is also in package 
pulseaudio 1:14.2-2ubuntu2
  InstallationDate: Installed on 2021-07-04 (29 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210704)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulsecommon-14.2.so: cannot open 
shared object file: No such file or directory
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: pulseaudio
  Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: 
trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which 
is also in package pulseaudio 1:14.2-2ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted]

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


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

[Touch-packages] [Bug 1303316] Re: Digital S/PDIF output is not present in 5.1 mode

Thanks. Which Ubuntu version is that?

** Changed in: pulseaudio (Ubuntu)
   Status: Won't Fix => Incomplete

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

Title:
  Digital S/PDIF output is not present in 5.1 mode

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have the sound connected through digital S / PDIF 
  Sound works properly selecting stereo, but can not get it to work using 5.1 
  When I select stereo sound, appears on the tab below to phonon spdif output 
option. 
  When I select Output 5.1, that option does not appear. 

  I imagine the error will also occur selecting 7.1

  Deputy screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: phonon 4:4.7.0really4.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Apr  6 13:12:42 2014
  InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: phonon
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1868129] Re: I can't attach a writecache to LV

2021-08-03 Thread Stephen

Is there a workaround while this waits?
Seems like this is pretty important to me but

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

Title:
  I can't attach a writecache to LV

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  #lvconvert --type writecache --cachesettings 'low_watermark=0 
high_watermark=10 writeback_jobs=2048' --cachevol cache ssd/data
WARNING: Unrecognised segment type writecache
Invalid argument for --type: writecache
Error during parsing of command line.

  I see that lvm2 package was build without key --with-
  writecache=internal

  #lvm version
LVM version: 2.03.07(2) (2019-11-30)
Library version: 1.02.167 (2019-11-30)
Driver version: 4.41.0
Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --exec-prefix= 
--bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin 
--with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 
--with-cache=internal --with-device-uid=0 --with-device-gid=6 
--with-device-mode=0660 --with-default-pid-dir=/run 
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm 
--with-thin=internal --with-thin-check=/usr/sbin/thin_check 
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair 
--enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd 
--enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock 
--enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline 
--enable-udev_rules --enable-udev_sync

  # lsmod | grep dm_writecache
  dm_writecache 36864 0

  #cat /etc/os-release
  NAME="Ubuntu"
  VERSION="20.04 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Focal Fossa (development branch)"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  #uname -a
  Linux sw-sed-ubuntu 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  #apt info lvm2
  Package: lvm2
  Version: 2.03.07-1ubuntu1
  Priority: optional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Thu Mar 19 16:06:17 2020
  InstallationDate: Installed on 2020-03-19 (0 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200317)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Touch-packages] [Bug 1303316] Re: Digital S/PDIF output is not present in 5.1 mode

2021-08-03 Thread Hicks

Latest Ubuntu version.
Same bug, ten years ago...

Spdif Digital 5.1 not appears. Only HDMI 5.1.


El jue, 29 jul 2021 a las 22:13, Daniel van Vugt (<
1303...@bugs.launchpad.net>) escribió:

> Thank you for reporting this bug to Ubuntu.
> Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test. If you then find the bug is still
> present in the newer Ubuntu version, please add a comment here telling
> us which new version it is in.
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1303316
>
> Title:
>   Digital S/PDIF output is not present in 5.1 mode
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+subscriptions
>
>

-- 

nolesvotes.com
wiki .


** Attachment added: "Captura de pantalla de 2021-08-03 21-12-18.png"
   
https://bugs.launchpad.net/bugs/1303316/+attachment/5515608/+files/Captura%20de%20pantalla%20de%202021-08-03%2021-12-18.png

** Attachment added: "Captura de pantalla de 2021-08-03 21-12-28.png"
   
https://bugs.launchpad.net/bugs/1303316/+attachment/5515609/+files/Captura%20de%20pantalla%20de%202021-08-03%2021-12-28.png

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

Title:
  Digital S/PDIF output is not present in 5.1 mode

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I have the sound connected through digital S / PDIF 
  Sound works properly selecting stereo, but can not get it to work using 5.1 
  When I select stereo sound, appears on the tab below to phonon spdif output 
option. 
  When I select Output 5.1, that option does not appear. 

  I imagine the error will also occur selecting 7.1

  Deputy screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: phonon 4:4.7.0really4.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Apr  6 13:12:42 2014
  InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: phonon
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1406031] Re: Cannot connect to wifi having short password

2021-08-03 Thread Matej Kovacic

Sorry, this is just sick.

Bug reported and confirmed (!) in 2016, but still not resolved.

I confirm this bug still exists and is affecting me and other users. We
do not have control over WiFi, so we cannot change the password. But we
cannot use the WiFi, because of this bug.

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

Title:
  Cannot connect to wifi having short password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can't connect to a wifi network with security "WPA & WPA2 Personal"
  and a password of 7 ASCII characters. Of course this password is
  invalid, but I can't change that, and I should be able to connect
  anyway. Actually I could connect the first time, and after that it
  wouldn't enable the "connect" button anymore. I hope we're not in the
  business of policing other people's wifi... I really can't configure
  their system, but if you relax the constraints on your side, then I
  can have wifi access and work on my PhD project. Thanks for
  considering the net value of policing other people.

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


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

[Touch-packages] [Bug 1926827] Re: base-passwd does not really provide options to specify home folder for irc user when launching from GUI

** Tags removed: groovy

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

Title:
  base-passwd does not really provide options to specify home folder for
  irc user when launching from GUI

Status in base-passwd package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.10 installed, boot it
  2. Install all updates and run upgrade to 21.04 using graphical 
`update-manager -cd` command
  3. Wait for the "Configuring base-passwd" window to appear with a question (!)

  Do you want to change the home directory of user irc?

  Expected results:
  * the interface asks user a question, user is able to answer this question in 
GUI window

  Actual results:
  * user is unable to answer the question, only can click the Help (useless) 
and/or Next (does not respect the answer from user) buttons.

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


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

[Touch-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

** Tags removed: eoan
** Tags added: focal

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-themes-extra package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions


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

[Touch-packages] [Bug 1723272] Re: apport-bug unable to init server, dumps core

** Tags removed: artful

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

Title:
  apport-bug unable to init server, dumps core

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, apport-bug fails with the follow error:

  # apport-bug
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  Calling apport-cli directly works just fine. The problem seems to be a
  general Xwayland permission issue, since nothing can connect to the
  display server if sudo/su is used:

  $ sudo xclock
  No protocol specified
  Error: Can't open display: :0
  $ xauth list
  xauth:  file /home/user/.Xauthority does not exist

  If that's the way things are going to be in Ubuntu from now on, we
  need to make apport-bug a bit smarter in the way it decides whether to
  use the GUI version or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 
+1100:2017-10-13 09:46:23.546417474 
+1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
  Date: Fri Oct 13 09:49:17 2017
  InstallationDate: Installed on 2016-12-02 (313 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)

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


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

[Touch-packages] [Bug 1742509] Re: software-properties-gtk should not disable security.ubuntu.com mirror to local one

** Tags removed: artful trusty zesty

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

Title:
  software-properties-gtk should not disable security.ubuntu.com mirror
  to local one

Status in software-properties package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu without any changes in /etc/apt/sources.list
  (ensure that is has http://security.ubuntu.com/ubuntu

  $ grep http://security.ubuntu.com/ubuntu /etc/apt/sources.list | grep -v ^#
  deb http://security.ubuntu.com/ubuntu xenial-security main restricted
  deb http://security.ubuntu.com/ubuntu xenial-security universe
  deb http://security.ubuntu.com/ubuntu xenial-security multiverse
  $

  ).
  2. Launch `software-properties-gtk` and select local mirror, for example 
Switzerland mirror.switch.ch (or *Select Best Server*), *Reload* lists and 
check again:

  $grep http://security.ubuntu.com/ubuntu /etc/apt/sources.list | grep -v ^#
  $ # returns nothing

  Notes:
  * I discovered this while upgrading my machines to fix Meltdown vulnerability 
(as bug 1741934 and kernels 4.4.0-108 and 4.4.0-109). Only one my machine was 
upgraded to 109. It used *Main server* and http://security.ubuntu.com/ubuntu.
  * All releases seems to be affected by this mirror-problem.
  * Setting back to *Main server* does not return 
http://security.ubuntu.com/ubuntu to sources.list.
  * This clearly does not correspond to the official documentation ( 
https://wiki.ubuntu.com/SecurityTeam/FAQ#What_repositories_and_pockets_should_I_use_to_make_sure_my_systems_are_up_to_date.3F
 )

  Expected results:
  * Ubuntu must save http://security.ubuntu.com/ubuntu mirror in 
/etc/apt/sources.list for really fast fixing of critical bugs

  Actual results:
  * Ubuntu switches all mirrors and disables http://security.ubuntu.com/ubuntu .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20.7
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 10 20:57:55 2018
  InstallationDate: Installed on 2018-01-04 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  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/1742509/+subscriptions


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

[Touch-packages] [Bug 1750122] Re: gnome-terminal right mouse click drop-down menu is small, unreadable and unusable

** Tags removed: artful

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

Title:
  gnome-terminal right mouse click drop-down menu is small, unreadable
  and unusable

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Launch `gnome-terminal`
  3. Run some command - for example `uname -a`
  4. Try to copy command output by right mouse click and selecting *Copy* from 
it.

  Expected results:
  Right mouse click drop-down menu has normal size, readable and usable

  Actual results:
  Right mouse click drop-down menu is small, unreadable and unusable (see 
screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 14:17:48 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

** Tags removed: eoan groovy
** Tags added: impish

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

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

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


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

[Touch-packages] [Bug 1238408] Re: apport-collect is not functional until manual installation of python-apport

** Tags removed: artful

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

Title:
  apport-collect is not functional until manual installation of python-
  apport

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to launch `apport-collect 1712200`

  Expected results:
  apport-collect works out-the-box and collected corresponding info

  Actual results:
  apport-collect does not work and shows message:

  "You need to run 'sudo apt-get install python-apport' for apport-
  collect to work."

  Note: manual installation of python-apport adds 15 MB of new packages,
  after that apport-collect works as expected.

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


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

[Touch-packages] [Bug 1547561] Re: Unable to use Scilab with default Ambiance theme because of low contrast in the menu

** Tags removed: cosmic disco eoan trusty

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

Title:
  Unable to use Scilab with default Ambiance theme because of low
  contrast in the menu

Status in scilab package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with all default settings (Ambiance theme)
  2. Install Scilab
  3. Launch Scilab
  4. Try to use Scilab menu on the top of its window
  5. This menu has low contrast (see screenshot from 14.04).

  Temporary solution:
  switch theme to light (Radiance) theme.

  Affected Ubuntu versions:
  12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10, 17.04, 17.10, 18.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: scilab 5.5.0-2
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Feb 19 18:31:09 2016
  InstallationDate: Installed on 2015-12-12 (68 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1390792] Re: Synaptic Other Software tab jumps/scrolls to top when a repository check box is clicked

** Tags removed: disco eoan

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

Title:
  Synaptic Other Software tab jumps/scrolls to top when a repository
  check box is clicked

Status in gtk+3.0 package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  Confirmed
Status in synaptic package in Ubuntu:
  Confirmed

Bug description:
  In Synaptic's Software & Updates window, clicking the check box for a
  repository in the Other Software tab causes the list of repositories
  to jump to the top of the list. The scroll position of the list is
  instantly lost, disorienting the user, and hiding the fact that the
  click did anything, until the user scrolls back down to find the item
  that was clicked.

  This is only noticeable when there are enough repositories in the list
  to require scrolling.

  Finding the clicked repository again is especially difficult when all of them 
look nearly identical, as is the case when they're all PPAs with no comment 
string. (Every item in the list is just a long URL that looks very similar to 
the others.) It's even worse when there are both package and
  source URLs for each repo.

  This is especially problematic when updating the repo URLs after a
  distribution upgrade, because it's a very repetitive task, and the
  scroll window jumps and loses its place every single time.

  Ubuntu 14.04.1 LTS
  synaptic 0.81.1ubuntu1 amd64

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


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

[Touch-packages] [Bug 1725991] Re: GNOME applications are not shown in wmctrl -lx output on Wayland

** Tags removed: artful

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

Title:
  GNOME applications are not shown in wmctrl -lx output on Wayland

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in wmctrl package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Login to the default Ubuntu session
  3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc.
  4. Install wmctrl and use it from terminal with `wmctrl -lx`

  Expected results:
  wmctrl shows list of windows

  Actual results:
  wmctrl do not show list of windows

  Note:
  inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 .

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:21:23 2017
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1323285] Re: Tab for "Other software" repositories isn't usable with keyboard

** Tags removed: apport-bug disco eoan trusty
** Tags added: apport-bub

** Tags removed: apport-bub
** Tags added: apport-bug

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

Title:
  Tab for "Other software" repositories isn't usable with keyboard

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  The "other software" tab isn't keyboard-accessible.

  The list of software repositories can be navigated using the keyboard
  instead of a mouse.  However it's not possible to enable/disable the
  repositories.  Neither Enter nor Space have any effect on the
  checkboxes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon May 26 13:54:08 2014
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to trusty on 2014-05-22 (4 days ago)

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


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

[Touch-packages] [Bug 1683576] Re: cd with multiple directory argument fails

** Tags removed: artful zesty

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

Title:
  cd with multiple directory argument fails

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  In bash 4.4, a new behaviour was introduced for cd, where it would complain 
if multiple arguments are provided. From config-top.h [1]:
   
  /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
 error messages about multiple directory arguments to `cd'. */
  #define CD_COMPLAINS

  It seems like this is enabled for Ubuntu. However, this behaviour
  conflicts with the manual (both Ubuntu's and GNU's), which says
  something similar to: "Any additional arguments following directory
  are ignored."

  Please revert to the old behaviour, or correct the manual. This is not
  a user-configurable setting, and push is also affected.

  Ubuntu 17.04
  bash 4.4-2ubuntu1

  
  [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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


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

[Touch-packages] [Bug 1261945] Re: When editing PPAs, software-properties sometimes scrolls back to the top of the list

** Tags removed: disco eoan

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

Title:
  When editing PPAs, software-properties sometimes scrolls back to the
  top of the list

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I use software-properties quite frequently, and particularly extensive
  use when I upgrade my system (as I have recently done). Whilst working
  my way through the long list of PPA who's names have been branded with
  Canonical's infernal 'disabled during upgrade to saucy' appendage,
  I've noticed that every so often (quite frequently, but not always)
  when I edit a PPA somewhere down the list, I'll be returned to
  software-properties main dialogue scrolled back to the top of the
  list.  This, as I am sure you can imagine, is quite annoying,
  especially when working ones way through a long list of PPA, having to
  find your way back to where you were, and positively infuriating when
  coupled with the effects of bug 1261942.

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


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

[Touch-packages] [Bug 1807761] Re: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi

** Tags removed: cosmic disco eoan

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

Title:
  Unable to install deb-file stored on Desktop (which is controlled by
  nautilus-desktop) with GDebi

Status in gdebi package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS or Ubuntu 18.10
  2. Download some deb-file to the desktop - for with help of terminal:

   cd ~/Desktop
   apt-get download meld

  3. Install GDebi package installer with

   sudo apt install gdebi

  4. Select deb-file on desktop, make right click on it, select *Open
  With Other Application* select *GDebi Package Installer*, click
  *Select*, in opened window select *Install Package*

  Expected results:
  * GDebi asks user (sudo-able) password and installs the package

  Actual results:
  * GDebi do not ask user for password and do not install the package

  Notes:
  * first seen on AskUbuntu ( https://askubuntu.com/q/1099387/66509 )
  * you can view my screencast to get first person view :)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 23:14:16 2018
  GsettingsChanges:

  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


-- 
Mailing list: https://launchpad.net/~touch-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

** Tags removed: eoan

-- 
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 OEM Priority Project:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in grub2 source package in Groovy:
  Invalid
Status in initramfs-tools source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Fix Released
Status in grub2 source package in Hirsute:
  Invalid
Status in initramfs-tools source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Fix Released

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.

  [Impact]

   * Decoding failure messages in dmsg with a single lz4 initrd

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when loaded by grub

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when there is padding between them

  [Test Case]

   * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4

   * Create an lz4 compressed initrd with a single test-file in it with
  some content. I.e. echo "second-initrd" > test-file, and then pack
  that with cpio hewc owned by root & lz4 -l.

   * Create a combined padded initrd of stock initrd, pad4, and the
  test-marker initrd created above.

   * Boot above with "break=top" kernel command line.

   * With broken kernels, there should be dmesg error message that
  decoding failed, and one will observe that /test-file does not exist
  in the shell.

   * With fixed kernel, /test-file in the initrd shell should exist, and
  should have the expected content "second-initrd".

   * The alignment and padding in the above test case depends on the
  size of the first initrd => if a given padded initrd does not
  reproduce the problem, try varying the size of the first initrd or
  that of the padding between 0..4.

  
  [Where problems could occur]

   * This changes compatible lz4 decompressor in the kernel, which can
  also be used by other kernel modules such as cryptography, squashfs,
  zram, f2fs, comprssed kernel image, pstore. For example, previously
  rejected files with "bogus" length and extra padding may now be
  accepted, whereas they were previously getting rejected by the
  decompressor.

   * Ideally kernel should switch to the stable lz4 format which has
  better specification of end of stream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+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 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

And this is the debdiff for Hirsute, thanks.

** Patch added: 
"mesa_21.0.3-0ubuntu0.2.dsc-to-mesa_21.0.3-0ubuntu0.3.dsc.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1937988/+attachment/5515607/+files/mesa_21.0.3-0ubuntu0.2.dsc-to-mesa_21.0.3-0ubuntu0.3.dsc.debdiff

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

@Timo, Thanks for help, I rebased to 21.0.3, on Focal and Hirsute.

This is the debdiff for Focal, thanks.

** Patch added: 
"mesa_21.0.3-0ubuntu0.2~20.04.1.dsc-to-mesa_21.0.3-0ubuntu0.3~20.04.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1937988/+attachment/5515606/+files/mesa_21.0.3-0ubuntu0.2~20.04.1.dsc-to-mesa_21.0.3-0ubuntu0.3~20.04.1.debdiff

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

** Tags removed: groovy
** Tags added: impish

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  New
Status in console-setup package in Ubuntu:
  New
Status in kbd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)

  Expected results:
  * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function

  Actual results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions


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

[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts

** Tags removed: artful trusty utopic vivid wily yakkety zesty

** Tags removed: saucy
** Tags added: bionic focal hirsute impish

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

Title:
  xkeyboard-config, console-setup, and ubiquity should use Super+Space
  for switching keyboard layouts

Status in xkeyboard-config:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in console-setup source package in Trusty:
  Confirmed
Status in ubiquity source package in Trusty:
  Confirmed
Status in xkeyboard-config source package in Trusty:
  In Progress

Bug description:
  Super+Space is default combination for switching keyboard layouts in
  gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg;
  console-setup; and ubiquity should also use Super+Space combination
  for switching keyboard layouts.

  reading xkeyboard-config sources and documentations i don't see that
  xkeyboard-config can support grp:lwin_space and i guess that needs to
  be the first step to properly support super+space.

  
  Original bug report below:

  
  Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10.
  I use two keyboard layouts - English and Russian.
  So I select them on the corresponding screen of ubiquity setup wizard.

  It quietly set the keyboard switching shortcut to Alt+Shift and wrote this 
setting to /etc/default/keyboard:
  # ...
  XKBMODEL="pc105"
  XKBLAYOUT="us,ru"
  XKBVARIANT=","
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
  # ...

  On first boot of installed system the small notification pop-up showed
  that Ibus will use Super+Space for layout switching.

  Please fix this configuration inconsistency.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Mon Oct 21 12:16:58 2013
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash --
  InstallationDate: Installed on 2013-10-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
  MarkForUpload: True
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions


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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

** Tags removed: artful
** Tags added: focal hirsute impish

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in aptitude source package in Xenial:
  Confirmed
Status in synaptic source package in Xenial:
  Confirmed
Status in update-notifier source package in Xenial:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in aptitude source package in Hirsute:
  Fix Released
Status in synaptic source package in Hirsute:
  Triaged
Status in update-notifier source package in Hirsute:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  READ ME FIRST
  =
  This is only a regression on a cosmetic level. Previous versions of apt did 
not have any sandboxing whatsoever, so this means apt reverted back to that old 
behavior.

  update-notifier SRU
  ---
  [Impact]
  Cosmetic. Warnings when installing packages using update-notifier downloading 
stuff

  [Test case]

  Install flashplugin-installer with apt and check that the output does
  not contain a message like this:

  W: Can't drop privileges for downloading as file '...' couldn't be
  accessed by user '_apt'

  [Regression Potential]

  It just chowns /var/lib/update-notifier/package-data-
  downloads/partial/ to _apt:root, there should not be any regression.

  Original report
  ---

  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

** Tags removed: artful

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Released
Status in Boot-Repair:
  Fix Released
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Released
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions

2021-08-03 Thread Paul White

** No longer affects: hundredpapercuts

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

Title:
  On laptops, screen brightness and keyboard backlight isn't memorized
  between sessions

Status in Dell Sputnik:
  New
Status in upstart :
  Confirmed
Status in cinnamon-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Won't Fix
Status in mate-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop.
    2. Set a different screen (or keyboard) backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  FIX:
    A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA
  sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight
  sudo apt-get update
  sudo apt-get install sysvinit-backlight

  NOTES:
  1. If you have installed previous non-deb version, please remove it 
carefully manually
    sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness 
/etc/rc?.d/?25brightness
      2. If you have installed previous version from my PPA on Ubuntu 14.04 
LTS, please reinstall the package by:
    sudo apt-get purge sysvinit-backlight
    sudo apt-get install sysvinit-backlight
  3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too.

    B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from  
January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should 
upgrade them to Ubuntu 16.04 (see C below).
   My script is incompatible with these Ubuntu versions - remove it with
    sudo apt-get purge sysvinit-backlight
    sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight

    C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It 
saves and restores screen and keyboard backlight levels.
   My script is incompatible with these Ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions


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

[Touch-packages] [Bug 1452216] Re: libgcrypt11 not present in Vivid (15.04), Xenial (16.04) - Spotify, Brackets and other app issue.

** Tags removed: ubuntu vivid

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

Title:
  libgcrypt11 not present in Vivid (15.04), Xenial (16.04) - Spotify,
  Brackets and other app issue.

Status in libgcrypt11 package in Ubuntu:
  Confirmed

Bug description:
  The package libgcrypt11 is not present anymore in official ubuntu
  vivid repositories.

  This cause app crash, such as spotify:
  spotify: error while loading shared libraries: libgcrypt.so.11: cannot open 
shared object file: No such file or directory

  Current workaround is to manually download the .deb package from
  launchpad/debian package such as
  https://packages.debian.org/wheezy/libgcrypt11 and manually install
  with dpkg.

  Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

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


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

[Touch-packages] [Bug 1303249] Re: Indicator-datetime doesn't show evolution/eds calendar color for all-day events (Trusty/Xenial)

** Tags removed: trusty utopic vivid

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

Title:
  Indicator-datetime doesn't show evolution/eds calendar color for all-
  day events (Trusty/Xenial)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It used to show respective calendar color from evolution for all-day
  events & clock/alarm icon for events with time. But with latest
  update, it seems it has stopped showing evolution calendar color for
  all-day events in indicator-datetime.

  However alarm/clock icon still appears as usual. I have attached a
  screenshot.

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


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

[Touch-packages] [Bug 1173728] Re: bash programmable completion is not loaded in subshells when running a login shell

** Tags removed: raring trusty

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

Title:
  bash programmable completion is not loaded in subshells when running a
  login shell

Status in base-files package in Ubuntu:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I don't know it's bug or feature, but [TAB] autocomplete won't work
  with sudo on 13.04 (and 12.10 too). To fix this, you need to uncomment
  some lines in /etc/bash.bashrc and then [TAB] autocomplete will work.

  http://askubuntu.com/questions/209778/auto-completion-does-not-work-
  for-sudo-apt-get-install

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bash 4.2-5ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat Apr 27 22:03:33 2013
  InstallationDate: Installed on 2013-04-26 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)

** Tags removed: artful saucy trusty utopic vivid wily yakkety

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

Title:
  icons in indicators are small (difficult to view on FullHD display and
  smaller than was on 12.04)

Status in ido package in Ubuntu:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  I have Ubuntu 14.04 with all updates installed.

  My screen resolution is 1920x1080 (FullHD) at 16.4 inches.
  Icons from the menu of newest indicator-keyboard and other gnome-panel icons 
are very small (difficult to read).

  Please adapt icon sizes to large screen resolutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Dec 21 00:41:25 2013
  InstallationDate: Installed on 2013-10-20 (61 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago)

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


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

[Touch-packages] [Bug 622106] Re: history expansion conflicts with variable expansion, maybe token parsing issue

** Tags removed: precise

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

Title:
  history expansion conflicts with variable expansion, maybe token
  parsing issue

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: bash

  $ cat /etc/issue
  Ubuntu 10.04.1 LTS \n \l

  
  $ echo $BASH_VERSION
  4.1.5(1)-release

  $ sleep 5 & pid=$!
  $ sleep 5 & pid=$!; echo $pid
  bash: !: event not found
  $ sleep 5 & pid=$! ; echo $pid
  3434
  $ (sleep 5 & pid=$!; echo $pid)
  bash: !: event not found
  $ (sleep 5 & pid=$\!; echo $pid)
  $!
  $ {sleep 5 & pid=$!; echo $pid;}
  bash: !: event not found
  $ 

  Seems like the workaround is to include whitespace after the $!,
  however that doesn't help existing scripts.

  $ aptitude show bash
  Package: bash
  Essential: yes
  State: installed
  Automatically installed: no
  Version: 4.1-2ubuntu3
  Priority: required
  Section: shells
  Maintainer: Ubuntu Developers 
  Uncompressed Size: 3,576k
  Depends: base-files (>= 2.1.12), debianutils (>= 2.15)
  PreDepends: dash, libc6 (>= 2.11), libncurses5 (>= 5.6+20071006-3)
  Recommends: bash-completion (>= 20060301-0)
  Suggests: bash-doc
  Conflicts: bash-completion (< 20060301-0)
  Replaces: bash-completion (< 20060301-0), bash-doc (<= 2.05-1)

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


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

[Touch-packages] [Bug 839561] Re: (gtk-update-icon-cache:17946): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': no such file

** Tags removed: artful oneiric

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

Title:
  (gtk-update-icon-cache:17946): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': no such file or folder

Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Debian:
  Invalid

Bug description:
  got this error into update dialog box while upgrading latest package
  on Oneiric i386 b1

  (gtk-update-icon-cache:17946): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': no such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gir1.2-gdkpixbuf-2.0 2.24.0-1
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic-pae 3.0.3
  Uname: Linux 3.0.0-9-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Sep  2 15:13:56 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 778627] Re: bash completion now quotes shell variable references rather than expanding them

** Tags removed: natty

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

Title:
  bash completion now quotes shell variable references rather than
  expanding them

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Quantal:
  Fix Released
Status in bash source package in Raring:
  Fix Released
Status in bash package in Debian:
  Fix Released
Status in bash package in Fedora:
  New

Bug description:
  Binary package hint: bash

  NB! NB! NB!

  After applying the update to resolve this problem one _also_ must
  enable direxpand option by issuing:

  shopt -s direxpand

  If you do not do this, the variable expansion will not happen.

  NB! NB! NB!

  [Impact]
  Bash-4.2 tries to leave completed directory names as the user typed them,
  without expanding them to a full pathname.  One effect of this is that
  shell variables used in pathnames being completed (e.g., $HOME) are left
  unchanged, but the `$' is quoted by readline because it is a special
  character to the shell.

  [Test Case]
  - [Current test case showing expected behavior]

  Items to address so far:
    - that $ is escaped less
    - that direxpand does not expand as expected
    - that direxpand option is available and if enabled, expands directories 
with variable names.

  zef:~/Projects/precise-amd64$ mkdir -p /tmp/testd/finger/toe
  zef:~/Projects/precise-amd64$ cd /tmp/testd/
  zef:/tmp/testd$ td=`pwd`
  zef:/tmp/testd$ cd ../
  zef:/tmp$ ls \$td/finger

  zef:/tmp$ shopt -s direxpand
  zef:/tmp$ ls $td/fing
  zef:/tmp$ ls /tmp/testd/finger/
  toe

  - [Previous Test Case showing non-working bash installation]
  ~$ mkdir -p /tmp/testd/finger/toe
  /tmp$ cd /tmp/testd
  /tmp/testd$ td=`pwd`
  /tmp/testd$ cd ../
  /tmp$ ls $td/fing

  Type a TAB character at this point, and bash completion makes the line:
  /tmp$ ls \$td/finger

  Note that while 'fing' has been expanded to 'finger ' (with a space at the 
end), the $td variable reference has had the
  $ character quoted with a backslash.  This prevents further extension of the 
pathname, and in fact makes
  the command invalid; if I type a newline at this point, I get:
  ls: cannot access $td/finger: No such file or directory

  This is not useful behavior.  I believe that in Ubuntu 10.10, the $td 
variable would have been expanded
  to  '/tmp/testd', and subsequent completions starting from 
'/tmp/testd/finger' would have worked.

  [The version of /etc/bash_completion.d/acroread.sh that is installed
  starts with:

  # _filedir : to handle file and directories with spaces in their names.
  if ! type _filedir &> /dev/null ; then

  so I don't think that file is overriding /etc/bash_completion's
  _filedir ...]

  [Regression Potential]
  - (#32) low potential for regressions since this bug is related to the 
interactive command line and would not influence any scripts.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bash 4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Fri May  6 09:48:29 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: bash
  UpgradeStatus: Upgraded to natty on 2011-04-30 (6 days ago)

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


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

[Touch-packages] [Bug 1315422] Re: add-apt-repository should have an option for adding only binary DEBs (without DEB-SRC)

** Tags removed: precise

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

Title:
  add-apt-repository should have an option for adding only binary DEBs
  (without DEB-SRC)

Status in Charm Helpers:
  New
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE:
1. launch terminal
2. add some repository (for example, proprietary Opera without source code) 
with 
 sudo add-apt-repository 'deb http://deb.opera.com/opera/ stable non-free'
3. update repositories with 
 sudo apt-get update

  EXPECTED RESULTS:
Index files are updated, opera package may be installed with 
  sudo apt-get install opera

  ACTUAL RESULTS:
Got error messages:
 W: Failed to fetch http://deb.opera.com/opera/dists/stable/Release  Unable 
to find expected entry 'non-free/source/Sources' in Release file (Wrong 
sources.list entry or malformed file)

  E: Some index files failed to download. They have been ignored, or
  old ones used instead.

Unable to install opera with   
  sudo apt-get install opera
Able to install opera after commenting out deb-src line.

  
  Please add option to add-apt-repository for skipping deb-src line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-helpers/+bug/1315422/+subscriptions


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

[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions

** Tags removed: precise quantal raring saucy trusty utopic

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

Title:
  On laptops, screen brightness and keyboard backlight isn't memorized
  between sessions

Status in Dell Sputnik:
  New
Status in One Hundred Papercuts:
  Won't Fix
Status in upstart :
  Confirmed
Status in cinnamon-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Won't Fix
Status in mate-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop.
    2. Set a different screen (or keyboard) backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  FIX:
    A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA
  sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight
  sudo apt-get update
  sudo apt-get install sysvinit-backlight

  NOTES:
  1. If you have installed previous non-deb version, please remove it 
carefully manually
    sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness 
/etc/rc?.d/?25brightness
      2. If you have installed previous version from my PPA on Ubuntu 14.04 
LTS, please reinstall the package by:
    sudo apt-get purge sysvinit-backlight
    sudo apt-get install sysvinit-backlight
  3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too.

    B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from  
January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should 
upgrade them to Ubuntu 16.04 (see C below).
   My script is incompatible with these Ubuntu versions - remove it with
    sudo apt-get purge sysvinit-backlight
    sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight

    C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It 
saves and restores screen and keyboard backlight levels.
   My script is incompatible with these Ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions


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

[Touch-packages] [Bug 1023717] Re: crashed with Error in notification(): GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications

** Tags removed: oneiric precise

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

Title:
  crashed with Error in notification():
  GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded:
  Exceeded maximum number of notifications

Status in blueman package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in gm-notify package in Ubuntu:
  Confirmed
Status in gnome-clocks package in Ubuntu:
  Confirmed
Status in notification-daemon package in Ubuntu:
  Confirmed
Status in soundconverter package in Ubuntu:
  Confirmed

Bug description:
  Programs which use notification-daemon for displaying messages do not
  work because of

  Error in notification():
  GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded:
  Exceeded maximum number of notifications


  Problem confirmed on Ubuntu 11.10 and 12.04.

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


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

[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

** Tags removed: precise trusty

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

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


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

[Touch-packages] [Bug 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.

** Tags removed: precise raring trusty ubuntu utopic vivid

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

Title:
  [QEMU] Corrupted desktop screen for raring desktop installation in
  QEMU guest (Cirrus graphics).  Affects KVM but not VBox.

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  The desktop screen appears corrupted after raring desktop
  installation. Please see attached screenshot for how it looks. Going
  through System settings -> Appearance and selecting different wall
  papers does not solve the isssue.

  Test Steps:
  1. Install Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121119)
  2. Reboot after the installation and log in

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
  Uname: Linux 3.7.0-2-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.6.2-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CurrentDmesg: [   18.945219] hda-intel: IRQ timing workaround is activated 
for card #0. Suggest a bigger bdl_pos_adj.
  Date: Mon Nov 19 12:26:26 2012
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc Device [1af4:1100]
  InstallationDate: Installed on 2012-11-19 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121119)
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Bochs Bochs
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic 
root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
  dmi.product.name: Bochs
  dmi.sys.vendor: Bochs
  version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.4-0ubuntu1
  xserver.bootTime: Mon Nov 19 12:23:11 2012
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 8
  xserver.errors: open /dev/dri/card0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.13.0-0ubuntu7

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


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

[Touch-packages] [Bug 1565932] Re: /sbin/insserv file is missed in Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS

** Tags removed: precise trusty wily

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

Title:
  /sbin/insserv file is missed in Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS

Status in insserv package in Ubuntu:
  Confirmed

Bug description:
  It seems that Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS does not have 
  /sbin/insserv file (see 
http://packages.ubuntu.com/search?suite=xenial=any=filename=contents=%2Fsbin%2Finsserv).

  
  But Debian has this file (see 
https://packages.debian.org/search?suite=sid=any=path=contents=%2Fsbin%2Finsserv).

  This package is needed by some software (for example NI-VISA 15.5 -
  http://www.ni.com/download/ni-visa-15.5/5848/en/). Please add it to
  Ubuntu 14.04 LTS and 16.04 LTS.

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


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

[Touch-packages] [Bug 1938814] [NEW] package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2021-08-03 Thread Sudhanshu Prasad

Public bug reported:

Unable to install it.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
AptOrdering:
 libevview3-3:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Aug  3 20:40:35 2021
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2021-08-03 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: gst-plugins-base1.0
Title: package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-base1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  Unable to install it.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   libevview3-3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Aug  3 20:40:35 2021
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-08-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: gst-plugins-base1.0
  Title: package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1938814/+subscriptions


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

[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

2021-08-03 Thread Simon Chopin

For hirsute, all but two were flaky that turned green on rerun. The
other ones will necessitate hints :

https://code.launchpad.net/~schopin/britney/+git/hints-ubuntu/+merge/406595
https://code.launchpad.net/~schopin/britney/+git/hints-ubuntu/+merge/406596

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

Title:
  [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Committed
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Released

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


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

[Touch-packages] [Bug 1938810] [NEW] Reverse lookup of 127.0.0.1 does not work

2021-08-03 Thread Nick Anderson

Public bug reported:

I expected a reverse lookup of 127.0.0.1 to return localhost, instead it
returned nothing.

```
root:~# dig -x 127.0.0.1

; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60017
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.IN  PTR

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Aug 03 09:25:20 CDT 2021
;; MSG SIZE  rcvd: 51

```

If I explicitly lookup using 127.0.0.1 instead of the default
127.0.0.53, I do get a record as expected.

```
root:~# dig -x 127.0.0.1 @127.0.0.1

; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1 @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51602
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa. 10800   IN  PTR localhost.

;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Aug 03 09:25:15 CDT 2021
;; MSG SIZE  rcvd: 74

```

I have an entry in /etc/hosts.

```
root:~# grep 127.0.0.1 /etc/hosts
127.0.0.1   localhost
```

Looks like unbound which seems to work as expected is running on
127.0.0.1:53, and systemd-resolv which is not working is on
127.0.0.53:53.

```
tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN  
1839/unbound
tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN  
1511/systemd-resolv 

```

I am running 20.04.2:

```
root:~# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
```

With systemd version 245.4-4ubuntu3.7

```
root@:~# apt-cache policy systemd
systemd:
  Installed: 245.4-4ubuntu3.7
  Candidate: 245.4-4ubuntu3.11
  Version table:
 245.4-4ubuntu3.11 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 *** 245.4-4ubuntu3.7 100
100 /var/lib/dpkg/status
 245.4-4ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
 237-3ubuntu10.50 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages

```

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

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

Title:
  Reverse lookup of 127.0.0.1 does not work

Status in systemd package in Ubuntu:
  New

Bug description:
  I expected a reverse lookup of 127.0.0.1 to return localhost, instead
  it returned nothing.

  ```
  root:~# dig -x 127.0.0.1

  ; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60017
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;1.0.0.127.in-addr.arpa.IN  PTR

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Aug 03 09:25:20 CDT 2021
  ;; MSG SIZE  rcvd: 51

  ```

  If I explicitly lookup using 127.0.0.1 instead of the default
  127.0.0.53, I do get a record as expected.

  ```
  root:~# dig -x 127.0.0.1 @127.0.0.1

  ; <<>> DiG 9.16.1-Ubuntu <<>> -x 127.0.0.1 @127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51602
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;1.0.0.127.in-addr.arpa.IN  PTR

  ;; ANSWER SECTION:
  1.0.0.127.in-addr.arpa. 10800   IN  PTR localhost.

  ;; Query time: 3 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Tue Aug 03 09:25:15 CDT 2021
  ;; MSG SIZE  rcvd: 74

  ```

  I have an entry in /etc/hosts.

  ```
  root:~# grep 127.0.0.1 /etc/hosts
  127.0.0.1   localhost
  ```

  Looks like unbound which seems to work as expected is running on
  127.0.0.1:53, and systemd-resolv which is not working is on
  127.0.0.53:53.

  ```
  tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN
  1839/unbound
  tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN
  1511/systemd-resolv 

  ```

  I am running 20.04.2:

  ```
  root:~# lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  ```

  With systemd version 245.4-4ubuntu3.7

  ```
  root@:~# apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3.7

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2021-08-03 Thread Vladislav Shumkin

Any plans for releasing Pulseaudio 15 for Hirsute?

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-08-03 Thread Frank Villaro

Hi, Sorry for the late reply I didn't receive the notifications.

This problem happens on a "bare" environment: it's a simple server (IPv6
RA + v4 DHCP) with some IPv6 ranges assigned to the `lo` interface.

Don't hesitate if you need more info, although we don't reproduce the
bug anymore due to our backport

Cheers !

** Attachment added: "some logs"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5515576/+files/logs1

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

Title:
  network configuration failed on reboot

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

Bug description:
  [impact]

  number of statically defined addresses for an interface in systemd-
  networkd is limited

  [test case]

  Note: this only occurs in a container; this is not reproducable in a
  VM or bare metal.

  Configure netplan with the attached yaml file (10-test.yaml)

  enable debug for systemd-networkd

  reboot the system and check the journalctl output to see if any errors
  were reported for systemd-networkd, e.g.:

  $ journalctl -b -u systemd-networkd | grep 'could not set'
  Jul 23 13:16:52 lp1930738-b systemd-networkd[189]: eth0: could not set 
address: Connection timed out
  ...

  Note that systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  this is needed in f and b

  this is fixed upstream with commits
  628f08b66d43d1947b03419409d817d28eb47321 and PR 16982 which are
  included in v246 and later, so this is fixed in h and later

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [original description]

  This issue was reported at
  https://github.com/systemd/systemd/issues/17012

  **Used distribution**
   > Ubuntu 20.04.1 LTS

  **systemd version the issue has been seen with**
  > 245.4-4ubuntu3.2

  **Issue details**
  I configured 255 IPv4 address (including primary IP) using netplan but when 
the server restart, it time out on configuring the interface.  If I limit total 
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.

  Below are my configurations and error logs.

  **/etc/netplan/10-ens3.yaml**
  ```
  network:
    version: 2
    renderer: networkd
    ethernets:
  ens3:
    dhcp4: no
    addresses:
  - 140.XX.XX.XX/23
  - 103.XXX.XX.1/24
  - 103.XXX.XX.2/24
  - CONTINUED IP ADDRESS UPTO BELOW ...
  - 103.XXX.XX.254/24
    gateway4: 140.XX.XX.X
    nameservers:
  addresses: [1.1.1.1, 1.0.0.1]
    routes:
  - to: 169.254.0.0/16
    via: 140.XX.XX.X
    metric: 100
  ```
  The above config works if I run `netplan apply` but when I reboot, it does 
not work.

  **networkctl**
  ```
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 ens3 etherroutablefailed

  2 links listed.
  ```

  **/etc/systemd/system/systemd-networkd.service.d/override.conf**
  ```
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  ```

  **systemctl status systemd-networkd.service**
  ```
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; 
enabled-runtime; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-networkd.service.d
   └─override.conf
   Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
     Docs: man:systemd-networkd.service(8)
     Main PID: 346 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 1074)
   Memory: 3.8M
   CGroup: /system.slice/systemd-networkd.service
   └─346 /lib/systemd/systemd-networkd

  Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router 
Solicitation, next solicitation in 7s
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received 
before link confirmation timeout
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback 
for 'timeout' event.
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router 
Solicitation, next solicitation in 15s
  Sep 10 19:47:23

[Touch-packages] [Bug 1938771] Re: lxc-test-rootfs test regression with 4.0.10-0ubuntu3

2021-08-03 Thread Christian Brauner

** Changed in: lxc (Ubuntu Impish)
   Status: In Progress => Fix Committed

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

Title:
  lxc-test-rootfs test regression with 4.0.10-0ubuntu3

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Impish:
  Fix Committed

Bug description:
  It looks like the option "lxc.rootfs.options = ro" is not honored with
  lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1
  (kernel is the same, I'm testing this with 5.13.0-13.13).

  Output of the test:

  09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
  + PHASE=setup
  + trap cleanup EXIT
  + lxc-destroy -n lxc-test-rootfs -f
  lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
  + true
  + lxc-create -t busybox -n lxc-test-rootfs
  + PHASE=ro_rootfs
  + echo 'Starting phase ro_rootfs'
  Starting phase ro_rootfs
  + config=/var/lib/lxc/lxc-test-rootfs/config
  + sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
  + echo 'lxc.rootfs.options = ro'
  + lxc-start -n lxc-test-rootfs
  ++ lxc-info -n lxc-test-rootfs -p -H
  + pid=2147
  + ro=0
  + mkdir /proc/2147/root/rotest
  + '[' 0 -ne 0 ']'
  + cleanup
  + set +e
  + lxc-destroy -n lxc-test-rootfs -f
  + '[' ro_rootfs '!=' done ']'
  + echo 'rootfs test failed at ro_rootfs'
  rootfs test failed at ro_rootfs
  + exit 1

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


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

[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

2021-08-03 Thread Simon Chopin

For the focal migration, I have asked for the following britney hints:

https://code.launchpad.net/~schopin/britney/+git/hints-ubuntu/+merge/406594
https://code.launchpad.net/~schopin/britney/+git/hints-ubuntu/+merge/406593

The other tests seem to be flaky.

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

Title:
  [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Committed
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Released

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


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

[Touch-packages] [Bug 1905285] Re: socket-activated sshd breaks on concurrent connections

2021-08-03 Thread Athos Ribeiro

I verified the fixes by following the steps in the test plan described
above by using the attached script on both focal and hirsute LXC
containers.

The tests show that the patch successfully fixes the described issue.

** Attachment added: "reproduce.sh"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1905285/+attachment/5515564/+files/reproduce.sh

** Tags removed: verification-needed verification-needed-focal 
verification-needed-hirsute
** Tags added: verification-done verification-done-focal 
verification-done-hirsute

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

Title:
  socket-activated sshd breaks on concurrent connections

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Users of the systemd socket activated ssh service may experience a
  race condition that may lead an ssh instance to fail.

  The race condition happens when, for a running socket activated ssh
  service,

  an instance A is started, creating the RuntimeDirectory for the
  service; then

  an instance B is started, relying on the RuntimeDirectory created for
  instance A; then

  instance A halts, causing the RuntimeDirectory to be deleted.

  If, at this point, instance B has not chrooted into RuntimeDirectory
  yet, then instance B will fail.

  The proposed patch fixes the issue by preserving the RuntimeDirectory
  after an instance A of the socket activated ssh service halts.

  [Test Plan]

  1) Stop any running instances of ssh.
  `systemctl stop ssh`

  2) Start the socket activated ssh service.
  `systemctl start ssh.socket`

  3) Verify that no errors related to ssh were logged in /var/log/auth.log
  `cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or 
directory'`

  4) perform several ssh connections to the running server in a short time 
span. ssh-keyscan may help here.
  `ssh-keyscan localhost`

  5) Verify that errors related to ssh were logged in /var/log/auth.log
  `cat /var/log/auth.log | grep 'sshd.*fatal.*chroot.*No such file or 
directory'`

  6) Apply the proposed fix (make sure the socket activated service is
  restarted)

  7) repead step (4), then verify that no new entries were appended to
  the step (5) output

  [Where problems could occur]

  If the changes to the socket activated unit file are wrong, the socket
  activated service may fail to start after the package upgrade. In this
  case, we would need to instruct users to perform local changes to the
  unit file with possible additional fixes while a new version of the
  patch lands.

  [racb] There might be cases where users are inadvertently depending on
  the cleanup that will now be disabled - for example by a bug or
  misconfiguration that would result in /run filling up otherwise. By
  disabling systemd cleanup and relying solely on openssh for cleanup,
  such a bug or misconfiguration may be exposed and cause problems on
  such systems.

  [Other Info]

  This fix has been forwarded to Debian and accepted in
  https://salsa.debian.org/ssh-team/openssh/-/merge_requests/12

  [Original message]

  This is mostly the same issue as https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=934663.

  With the default configuration of openssh-server and systemd, sshd
  will complain and crash when multiple connections are made and
  terminated in a quick succession, e.g. with `ssh-keyscan`. It results
  in the following errors in /var/log/auth.log:

  ```
  Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port 
41460: no matching host key type found. Their offer: 
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
  Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:34 {host} sshd[14568]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:34 {host} sshd[14566]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:47 {host} sshd[14584]: Connection closed by {client} port 59312 
[preauth]
  Nov 22 20:53:47 {host} sshd[14586]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:48 {host} sshd[14585]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  ```

  as well as e.g. missing responses in ssh-keyscan:

  ```
  $ ssh-keyscan -vvv {host}
  debug2: fd 3 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 2
  debug2: fd 4 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 4
  debug2: fd 5 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 8
  debug2: fd 6 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 32
  debug2: fd 7 setting O_NONBLOCK
  debug3:

[Touch-packages] [Bug 1938771] Re: lxc-test-rootfs test regression with 4.0.10-0ubuntu3

2021-08-03 Thread Christian Brauner

Also added tests around rootfs mount options.

** Changed in: lxc (Ubuntu Impish)
   Status: Confirmed => In Progress

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

Title:
  lxc-test-rootfs test regression with 4.0.10-0ubuntu3

Status in lxc package in Ubuntu:
  In Progress
Status in lxc source package in Impish:
  In Progress

Bug description:
  It looks like the option "lxc.rootfs.options = ro" is not honored with
  lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1
  (kernel is the same, I'm testing this with 5.13.0-13.13).

  Output of the test:

  09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
  + PHASE=setup
  + trap cleanup EXIT
  + lxc-destroy -n lxc-test-rootfs -f
  lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
  + true
  + lxc-create -t busybox -n lxc-test-rootfs
  + PHASE=ro_rootfs
  + echo 'Starting phase ro_rootfs'
  Starting phase ro_rootfs
  + config=/var/lib/lxc/lxc-test-rootfs/config
  + sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
  + echo 'lxc.rootfs.options = ro'
  + lxc-start -n lxc-test-rootfs
  ++ lxc-info -n lxc-test-rootfs -p -H
  + pid=2147
  + ro=0
  + mkdir /proc/2147/root/rotest
  + '[' 0 -ne 0 ']'
  + cleanup
  + set +e
  + lxc-destroy -n lxc-test-rootfs -f
  + '[' ro_rootfs '!=' done ']'
  + echo 'rootfs test failed at ro_rootfs'
  rootfs test failed at ro_rootfs
  + exit 1

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


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

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2021-08-03 Thread Maanus Kask

I want to test it in Bionic.

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Won't Fix
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

2021-08-03 Thread Ubuntu Foundations Team Bug Bot

The attachment "mesa_20.2.6-0ubuntu0.20.04.1to2.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1938791] [NEW] [18.04] systemd-resolve does not update DNS servers

2021-08-03 Thread Peter De Sousa

Public bug reported:

Hi,


A number of my nodes were in a broken state resolving DNS on an 
unattended-upgrades enabled nodes, running dhclient and checking 
systemd-resolve --status shows the following:

Link 2 (eth0)  
  Current Scopes: none 
   LLMNR setting: yes  
MulticastDNS setting: no   
  DNSSEC setting: no   
DNSSEC supported: no

Compared to a working node:

Link 2 (eth0)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 145.218.226.65
  145.218.238.29
  DNS Domain: reddog.microsoft.com

[Workaround]

Reboot the node, DNS should return back to normal.

sos report and additional information: https://private-
fileshare.canonical.com/~pjds/dsv/dns-issue/

Thanks,

Peter

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

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

Title:
  [18.04] systemd-resolve does not update DNS servers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  
  A number of my nodes were in a broken state resolving DNS on an 
unattended-upgrades enabled nodes, running dhclient and checking 
systemd-resolve --status shows the following:

  Link 2 (eth0)  
Current Scopes: none 
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no

  Compared to a working node:

  Link 2 (eth0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 145.218.226.65
145.218.238.29
DNS Domain: reddog.microsoft.com

  [Workaround]

  Reboot the node, DNS should return back to normal.

  sos report and additional information: https://private-
  fileshare.canonical.com/~pjds/dsv/dns-issue/

  Thanks,

  Peter

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


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

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

** No longer affects: oem-priority/focal

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1938771] Re: lxc-test-rootfs test regression with 4.0.10-0ubuntu3

2021-08-03 Thread Christian Brauner

Thanks for reporting this. I've fixed this in:
https://github.com/lxc/lxc/pull/3921

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

** Changed in: lxc (Ubuntu Impish)
 Assignee: (unassigned) => Christian Brauner (cbrauner)

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

Title:
  lxc-test-rootfs test regression with 4.0.10-0ubuntu3

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Impish:
  Confirmed

Bug description:
  It looks like the option "lxc.rootfs.options = ro" is not honored with
  lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1
  (kernel is the same, I'm testing this with 5.13.0-13.13).

  Output of the test:

  09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
  + PHASE=setup
  + trap cleanup EXIT
  + lxc-destroy -n lxc-test-rootfs -f
  lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
  + true
  + lxc-create -t busybox -n lxc-test-rootfs
  + PHASE=ro_rootfs
  + echo 'Starting phase ro_rootfs'
  Starting phase ro_rootfs
  + config=/var/lib/lxc/lxc-test-rootfs/config
  + sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
  + echo 'lxc.rootfs.options = ro'
  + lxc-start -n lxc-test-rootfs
  ++ lxc-info -n lxc-test-rootfs -p -H
  + pid=2147
  + ro=0
  + mkdir /proc/2147/root/rotest
  + '[' 0 -ne 0 ']'
  + cleanup
  + set +e
  + lxc-destroy -n lxc-test-rootfs -f
  + '[' ro_rootfs '!=' done ']'
  + echo 'rootfs test failed at ro_rootfs'
  rootfs test failed at ro_rootfs
  + exit 1

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


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

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

2021-08-03 Thread Timo Aaltonen

for hirsute/focal you need to rebase on 21.1.3

impish will get this via 21.2.0~rc4

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project focal series:
  New
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1932155] Re: Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT)

2021-08-03 Thread Timo Aaltonen

is fixed in 21.1.4-1 in impish

** Changed in: mesa (Ubuntu)
   Status: New => Fix Released

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

Title:
  Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD
  GPUs (e.g. RX 5500 XT)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets
  occur with various previous-generation AMD Radeon GPUs, for instance
  Radeon RX 5500 XT. There is a recent fix in the mesa library.

  Please see upstream mesa bug including available patch:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

  Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like
  it could apply to 21.0 (which is in focal-proposed) too, with minor
  effort.

  Thanks if you can backport this!

  amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145

  I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from
  focal-updates/focal-security

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


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

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

2021-08-03 Thread Timo Aaltonen

** Also affects: mesa (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project focal series:
  New
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1938779] [NEW] package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which is also in packa

2021-08-03 Thread Cliff Carson

Public bug reported:

Crash occurred during apt upgrade.

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: pulseaudio-utils 1:14.2-2ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cliff  1695 F pulseaudio
CasperMD5CheckResult: pass
Date: Tue Aug  3 06:06:50 2021
ErrorMessage: trying to overwrite 
'/usr/share/bash-completion/completions/pulseaudio', which is also in package 
pulseaudio 1:14.2-2ubuntu2
InstallationDate: Installed on 2021-07-04 (29 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210704)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulsecommon-14.2.so: cannot open 
shared object file: No such file or directory
Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.6
SourcePackage: pulseaudio
Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: 
trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which 
is also in package pulseaudio 1:14.2-2ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W35_37ET
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.
modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted]

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


** Tags: amd64 apport-package impish

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

Title:
  package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/share/bash-
  completion/completions/pulseaudio', which is also in package
  pulseaudio 1:14.2-2ubuntu2

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Crash occurred during apt upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio-utils 1:14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1695 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Aug  3 06:06:50 2021
  ErrorMessage: trying to overwrite 
'/usr/share/bash-completion/completions/pulseaudio', which is also in package 
pulseaudio 1:14.2-2ubuntu2
  InstallationDate: Installed on 2021-07-04 (29 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210704)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulsecommon-14.2.so: cannot open 
shared object file: No such file or directory
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: pulseaudio
  Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: 
trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which 
is also in package pulseaudio 1:14.2-2ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted]

To

[Touch-packages] [Bug 1938771] [NEW] lxc-test-rootfs test regression with 4.0.10-0ubuntu3

2021-08-03 Thread Andrea Righi

Public bug reported:

It looks like the option "lxc.rootfs.options = ro" is not honored with
lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1 (kernel
is the same, I'm testing this with 5.13.0-13.13).

Output of the test:

09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
+ PHASE=setup
+ trap cleanup EXIT
+ lxc-destroy -n lxc-test-rootfs -f
lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
+ true
+ lxc-create -t busybox -n lxc-test-rootfs
+ PHASE=ro_rootfs
+ echo 'Starting phase ro_rootfs'
Starting phase ro_rootfs
+ config=/var/lib/lxc/lxc-test-rootfs/config
+ sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
+ echo 'lxc.rootfs.options = ro'
+ lxc-start -n lxc-test-rootfs
++ lxc-info -n lxc-test-rootfs -p -H
+ pid=2147
+ ro=0
+ mkdir /proc/2147/root/rotest
+ '[' 0 -ne 0 ']'
+ cleanup
+ set +e
+ lxc-destroy -n lxc-test-rootfs -f
+ '[' ro_rootfs '!=' done ']'
+ echo 'rootfs test failed at ro_rootfs'
rootfs test failed at ro_rootfs
+ exit 1

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

** Affects: lxc (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Also affects: lxc (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  lxc-test-rootfs test regression with 4.0.10-0ubuntu3

Status in lxc package in Ubuntu:
  New
Status in lxc source package in Impish:
  New

Bug description:
  It looks like the option "lxc.rootfs.options = ro" is not honored with
  lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1
  (kernel is the same, I'm testing this with 5.13.0-13.13).

  Output of the test:

  09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
  + PHASE=setup
  + trap cleanup EXIT
  + lxc-destroy -n lxc-test-rootfs -f
  lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
  + true
  + lxc-create -t busybox -n lxc-test-rootfs
  + PHASE=ro_rootfs
  + echo 'Starting phase ro_rootfs'
  Starting phase ro_rootfs
  + config=/var/lib/lxc/lxc-test-rootfs/config
  + sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
  + echo 'lxc.rootfs.options = ro'
  + lxc-start -n lxc-test-rootfs
  ++ lxc-info -n lxc-test-rootfs -p -H
  + pid=2147
  + ro=0
  + mkdir /proc/2147/root/rotest
  + '[' 0 -ne 0 ']'
  + cleanup
  + set +e
  + lxc-destroy -n lxc-test-rootfs -f
  + '[' ro_rootfs '!=' done ']'
  + echo 'rootfs test failed at ro_rootfs'
  rootfs test failed at ro_rootfs
  + exit 1

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


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

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

the fix in https://launchpad.net/~xueshengyao/+archive/ubuntu/mesa is
much easier for Focal(only 2 lines changed), but it was based on a
workaround cannot upstream.

And the latest upstream mesa fixed this issue, so I cherry-picked 4 Mesa's
upstream commits to Focal:

a3a4517f4147a0a7c1b34a4bcd42de45d552df5f

55d1b8f929bbba58734bc7b1f79a6f53ab5aa0e8

0e856b95c59d4b9d1909bd96eca0296dd14b41ff

f1a66e7c90ceb4796085989d0d8374689753121e

and made a new package:

https://launchpad.net/~xueshengyao/+archive/ubuntu/mesa2

it fixed this issue in my testing.

I also attached the debdiff.

@Timo, could you please help on the SRU process? many thanks.

** Patch added: "mesa_20.2.6-0ubuntu0.20.04.1to2.debdiff"

https://bugs.launchpad.net/oem-priority/+bug/1937988/+attachment/5515520/+files/mesa_20.2.6-0ubuntu0.20.04.1to2.debdiff

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

Title:
The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
In Progress
Status in OEM Priority Project focal series:
New
Status in mesa package in Ubuntu:
New

Bug description:
[Steps to reproduce]
1. Connect a monitor on the AMD GPU.
2. Power on the system and boot into OS.
3. Run below command to launch glxgear
Cmd> DRI_PRIME=1 glxgears -info

[Expected result]
The image is not distrorted while running the glxgears

[Actual result]
The image is distrorted while running the glxgears

---

Here is the upstream bug for tracking this issue.

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions

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

[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

This bug was fixed in the package directx-headers - 1.0.2-1~20.04.1

---
directx-headers (1.0.2-1~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)

 -- Timo Aaltonen   Wed, 19 May 2021 11:25:36 +0300

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

This bug was fixed in the package xorg-server -
2:1.20.11-1ubuntu1~20.04.2

---
xorg-server (2:1.20.11-1ubuntu1~20.04.2) focal; urgency=medium

  * modesetting-disable-reverse-prime-offload-udl.diff: Fix a regression
on displaylink devices after mesa update. (LP: #1931547)

xorg-server (2:1.20.11-1ubuntu1~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
- don't disable building xwayland

 -- Timo Aaltonen   Tue, 06 Jul 2021 13:17:51 +0300

** Changed in: xorg-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: directx-headers (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Touch-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen   Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
   Status: Invalid => Fix Released

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

Title:
  FFE: new upstream release 21.0 and migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Invalid

Bug description:
  Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's
  been in Debian experimental since rc1. The packaging also migrates it
  to use llvm 12.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before hirsute is
  frozen, and then push more as an SRU.

  I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too
  with some games, all good.

  packages for hirsute are available on ppa:canonical-x/x-staging

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


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

[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

This bug was fixed in the package libdrm - 2.4.105-3~20.04.1

---
libdrm (2.4.105-3~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1923880, #1925320)

 -- Timo Aaltonen   Wed, 19 May 2021 11:15:08 +0300

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Touch-packages] [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen   Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions


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

[Touch-packages] [Bug 1923880] Re: libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

This bug was fixed in the package libdrm - 2.4.105-3~20.04.1

---
libdrm (2.4.105-3~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1923880, #1925320)

 -- Timo Aaltonen   Wed, 19 May 2021 11:15:08 +0300

** Changed in: libdrm (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

Status in libdrm package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in libdrm source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  There is a new minor release available, which adds support for i915
  Jasper Lake (JSL) and Alder Lake S (ADL-S), among other things.

  With this added, JSL can boot hirsute with the native driver.

  [Test case]

  Boot on JSL/ADL hardware, check that the native drm/dri driver is used
  (mesa support is already included).

  [What could go wrong]

  The worst case would be that the native driver would not be used
  anymore with this version, but there's no chance for that.

  Two regressing commits were reverted for impish, and we'll include
  those too.

  --

  git shortlog since 2.4.104:

  6b4e956d299c6ff Bump version to 2.4.105
  1d13cc1032bf66f amdgpu: add function of INFO ioctl for querying video caps
  50c98335c7b4013 amdgpu: sync up amdgpu_drm.h with latest from kernel
  b362850689d1b00 xf86drmMode: set FB_MODIFIERS flag when modifiers are supplied
  a5a400c9581c3b9 tests/amdgpu: fix bo eviction test issue
  af871ec1a6f017b drm/tests/amdgpu: fix Metadata test failed issue
  6d821612d9a4bc4 xf86drmMode: introduce drmModeGetPropertyType
  f5abbc303361980 test/amdgpu: remove static varible in Syncobj test
  cd3681976c3bbef intel: Keep libdrm working without pread/pwrite ioctls
  52f05d3d896480e meson: use library() instead of shared_library().
  7d6a1759900ffde xf86drm: fix null pointer deref in drmGetBufInfo
  2e67fef5f6c5870 intel: Add support for JSL
  a9bb32cfe1ee87f xf86drm: cap number of reported devices by drmGetDevice(2)
  06844b6eaefb03c Revert "xf86drm: cap number of reported devices by 
drmGetDevice(2)"
  632f59fcbfc790a xf86drm: warn about GEM handle reference counting
  523b3658aa8efa7 xf86drmMode: add drmIsKMS
  1225171bd55f65d amdgpu_drm: sync up with the latest amdgpu_drm.h based on 
drm-next (https://cgit.freedesktop.org/drm/drm)
  3b6cfb20fb3b7dd intel: add INTEL_ADLS_IDS to the pciids list
  9086ff9dafa87f9 intel: sync i915_pciids.h with kernel
  869ef0e4b22b8ba amdgpu: update marketing names
  a43cac24db2876b Avoid some compiler errors for 
tests/util/pattern.c62b9a3eee9bdaaf
  8cb12a2528d795c xf86drm: cap number of reported devices by drmGetDevice(2)
  19f0a9cb878da5b tests/amdgpu/vcn: clean abundant codes
  2315bcddd643b4b tests/amdgpu: add vcn test support for dimgrey_cavefish
  10377d661a31c7a tests/amdgpu: add vcn test support for navy_flounder
  5f85a6d98baba1d tests/util: Add mxsfb-drm driver
  62b9a3eee9bdaaf meson: Also search for rst2man.py
  10dd3eb6d5ab6c1 Use dep_rt in amdgpu/meson.build

  diffstat:
   amdgpu/amdgpu-symbols.txt|1
   amdgpu/amdgpu.h  |   17 +++
   amdgpu/amdgpu_gpu_info.c |   15 ++
   amdgpu/meson.build   |4 -
   core-symbols.txt |1
   data/amdgpu.ids  |6 ++
   etnaviv/meson.build  |2
   exynos/meson.build   |2
   freedreno/meson.build|2
   include/drm/amdgpu_drm.h |   51 +++---
   intel/i915_pciids.h  |  177 
+++--
   intel/intel_bufmgr_gem.c |   96 -
   intel/intel_chipset.c|2
   intel/meson.build|2
   libkms/meson.build   |2
   meson.build  |6 +-
   nouveau/meson.build  |2
   omap/meson.build |2
   radeon/meson.build   |2
   tegra/meson.build|2
   tests/amdgpu/amdgpu_test.c   |6 --
   tests/amdgpu/basic_tests.c   |   13 +++--
   tests/amdgpu/bo_tests.c  |4 -
   tests/amdgpu/syncobj_tests.c |2
   tests/amdgpu/vcn_tests.c |6 +-
   tests/util/kms.c |1
   tests/util/pattern.c |5 --
   xf86drm.c|   11 
   xf86drm.h|   18 +++
   xf86drmMode.c|   14 +-
   xf86drmMode.h|   12 +
   31 files changed, 365 insertions(+), 121 deletions(-)

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


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

[Touch-packages] [Bug 1925320] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen   Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: libdrm (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Touch-packages] [Bug 1925434] Re: New bugfix release 21.0.3

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen   Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  New bugfix release 21.0.3

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 21.0.x-series, we should put it
  in hirsute so latest bugfixes would get there, and in focal for
  20.04.3 image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Touch-packages] [Bug 1925434] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  New bugfix release 21.0.3

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 21.0.x-series, we should put it
  in hirsute so latest bugfixes would get there, and in focal for
  20.04.3 image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Touch-packages] [Bug 1932311] Re: migrate to llvm 12

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen   Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  (split off from bug 1917763)

  [Impact]

  Mesa should migrate to llvm 12 for new AMDGPU features and HW support.
  Normally this would be done during the devel series, but this version
  was delayed too much to migrate before hirsute was out.

  [Fix]
  Build-depend on the new packages, including libclc which is now built from 
llvm sources.

  [Test case]

  Test AMD graphics and/or qemu desktop (llvmpipe) after installing
  migrated packages.

  [Regression potential]

  This has been in Impish for a month now without issues.

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


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

[Touch-packages] [Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen   Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which 
shows as graphical corruption on the desktop apps with certain hardware.

  The fix is to add a commit from upstream staging/21.0 -branch, which
  never got released as 21.0.4.

  [Test case]
  Install the update, use desktop apps, see that it works correctly now.

  [Where things could go wrong]
  The fix adds a single line for an earlier commit that was incomplete. In 
theory it might regress some other amd hw, but this is highly unlikely.

  --

  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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


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

[Touch-packages] [Bug 1932311] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  (split off from bug 1917763)

  [Impact]

  Mesa should migrate to llvm 12 for new AMDGPU features and HW support.
  Normally this would be done during the devel series, but this version
  was delayed too much to migrate before hirsute was out.

  [Fix]
  Build-depend on the new packages, including libclc which is now built from 
llvm sources.

  [Test case]

  Test AMD graphics and/or qemu desktop (llvmpipe) after installing
  migrated packages.

  [Regression potential]

  This has been in Impish for a month now without issues.

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


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

[Touch-packages] [Bug 1934783] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which 
shows as graphical corruption on the desktop apps with certain hardware.

  The fix is to add a commit from upstream staging/21.0 -branch, which
  never got released as 21.0.4.

  [Test case]
  Install the update, use desktop apps, see that it works correctly now.

  [Where things could go wrong]
  The fix adds a single line for an earlier commit that was incomplete. In 
theory it might regress some other amd hw, but this is highly unlikely.

  --

  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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


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

[Touch-packages] [Bug 1918855] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions


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

[Touch-packages] [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2

---
mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

mesa (21.0.3-0ubuntu0.1) hirsute; urgency=medium

  * New upstream release. (LP: #1925434)
- drisw-move-zink-down.diff dropped, upstream
  * Migrate to llvm-12. (LP: #1932311)
  * iris-avoid-abort-if-enomem.diff: Don't abort when out of memory.
(LP: #1918855)

 -- Timo Aaltonen   Mon, 19 Jul 2021 22:26:12 +0300

** Changed in: mesa (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions


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

[Touch-packages] [Bug 1925434] Re: New bugfix release 21.0.3

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2

---
mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

mesa (21.0.3-0ubuntu0.1) hirsute; urgency=medium

  * New upstream release. (LP: #1925434)
- drisw-move-zink-down.diff dropped, upstream
  * Migrate to llvm-12. (LP: #1932311)
  * iris-avoid-abort-if-enomem.diff: Don't abort when out of memory.
(LP: #1918855)

 -- Timo Aaltonen   Mon, 19 Jul 2021 22:26:12 +0300

** Changed in: mesa (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  New bugfix release 21.0.3

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 21.0.x-series, we should put it
  in hirsute so latest bugfixes would get there, and in focal for
  20.04.3 image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Touch-packages] [Bug 1932311] Re: migrate to llvm 12

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2

---
mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

mesa (21.0.3-0ubuntu0.1) hirsute; urgency=medium

  * New upstream release. (LP: #1925434)
- drisw-move-zink-down.diff dropped, upstream
  * Migrate to llvm-12. (LP: #1932311)
  * iris-avoid-abort-if-enomem.diff: Don't abort when out of memory.
(LP: #1918855)

 -- Timo Aaltonen   Mon, 19 Jul 2021 22:26:12 +0300

** Changed in: mesa (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  (split off from bug 1917763)

  [Impact]

  Mesa should migrate to llvm 12 for new AMDGPU features and HW support.
  Normally this would be done during the devel series, but this version
  was delayed too much to migrate before hirsute was out.

  [Fix]
  Build-depend on the new packages, including libclc which is now built from 
llvm sources.

  [Test case]

  Test AMD graphics and/or qemu desktop (llvmpipe) after installing
  migrated packages.

  [Regression potential]

  This has been in Impish for a month now without issues.

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


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

[Touch-packages] [Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2

---
mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
radeonsi caused by a bad backport. (LP: #1934783)

mesa (21.0.3-0ubuntu0.1) hirsute; urgency=medium

  * New upstream release. (LP: #1925434)
- drisw-move-zink-down.diff dropped, upstream
  * Migrate to llvm-12. (LP: #1932311)
  * iris-avoid-abort-if-enomem.diff: Don't abort when out of memory.
(LP: #1918855)

 -- Timo Aaltonen   Mon, 19 Jul 2021 22:26:12 +0300

** Changed in: mesa (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which 
shows as graphical corruption on the desktop apps with certain hardware.

  The fix is to add a commit from upstream staging/21.0 -branch, which
  never got released as 21.0.4.

  [Test case]
  Install the update, use desktop apps, see that it works correctly now.

  [Where things could go wrong]
  The fix adds a single line for an earlier commit that was incomplete. In 
theory it might regress some other amd hw, but this is highly unlikely.

  --

  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

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


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

[Touch-packages] [Bug 1823521] Re: on_ac_power returns 1 if battery is not present

2021-08-03 Thread Todd Taft

I'm having a similar issue on Ubuntu 20.04 on a Lenovo P340, which is a
desktop workstation system and thus doesn't even have any capability for
battery operation without an external UPS.  I'm attaching a copy of
selected directories in /sys and /proc that the script inspects.

** Attachment added: "Tar of selected directories in /sys and /proc"
   
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1823521/+attachment/5515514/+files/on_ac_power_bug.tgz

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

Title:
  on_ac_power returns 1 if battery is not present

Status in Xfce4 Power Manager:
  New
Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  
  on_ac_power should return 0 (as exit code).

  Besides Xfce Power Manager tells in Devices tab that Line power is
  "Not plugged in".

  Tested by an old Macbook.

  (I don't have battery to test with.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: powermgmt-base 1.33
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr  7 14:02:36 2019
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-05 (821 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: powermgmt-base
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-power-manager/+bug/1823521/+subscriptions


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

[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

2021-08-03 Thread jeremyszu

** Summary changed:

- The image is distrorted while use iGPU rendering and output via AMD GPU
+ The image is distorted while use iGPU rendering and output via AMD GPU

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project focal series:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions


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

[Touch-packages] [Bug 1652842] Re: ......

Ubuntu 14.04 (trusty) reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  ..

Status in Ubuntu:
  Won't Fix

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-58.79~14.04.1-generic 4.4.35
  Uname: Linux 4.4.0-58-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec 27 15:38:21 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0534]
   NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:1534]
  InstallationDate: Installed on 2015-11-17 (406 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Latitude E6430
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic 
root=UUID=c2f1bd8e-f965-4fc0-81c7-d35b284c3de9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/20/2013:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Dec 27 15:31:18 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12606 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.2~trusty3

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


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

[Touch-packages] [Bug 1661994] Re: Xdiagnistics

Sorry for the lack of replies. If you're still experiencing a problem on
this machine then please explain in more detail what it is.

** Tags added: radeon

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
   Xdiagnistics

Status in Ubuntu:
  Incomplete

Bug description:
  Report sent

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Feb  5 18:34:32 2017
  DistUpgraded: 2016-08-01 11:52:39,263 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
 Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
  MachineType: Hewlett-Packard HP Compaq dc5750 Microtower
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=5c6c0f08-be2e-4bbf-8e22-05238972f64e ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (188 days ago)
  dmi.bios.date: 01/25/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.10
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC72544ZW
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:svnHewlett-Packard:pnHPCompaqdc5750Microtower:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc5750 Microtower
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Aug  1 02:46:56 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
   inputHP WMI hotkeys   KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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


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

[Touch-packages] [Bug 1669393] Re: Sound card

** Package changed: xorg (Ubuntu) => ubuntu

** Package changed: ubuntu => pulseaudio (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/1669393

Title:
   Sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
My Sound  just stopped working  with the LXDE Desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar  2 22:15:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-62-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-64-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [1028:04a5]
 Subsystem: Dell Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [1028:04a5]
  InstallationDate: Installed on 2016-06-28 (247 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude 2120
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=e8f6cc65-b73f-4489-bc62-a90932f2a4e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0YY3FH
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd10/31/2011:svnDellInc.:pnLatitude2120:pvr:rvnDellInc.:rn0YY3FH:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude 2120
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Mar  2 22:12:51 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 734 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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

[Touch-packages] [Bug 1938753] Re: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Pa

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

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

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

Title:
  package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade:
  Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu
  überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Just tried to install updates, then the error reporting popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio-utils 1:14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucl   2483 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Aug  3 08:12:26 2021
  ErrorMessage: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu 
überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist
  InstallationDate: Installed on 2021-08-02 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210801)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulsecommon-14.2.so: cannot open 
shared object file: No such file or directory
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: pulseaudio
  Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: 
Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, 
welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Touch-packages] [Bug 1938753] Re: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Pa

Confirmed. But this fixed it for me:

  sudo apt --fix-broken install

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

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

Title:
  package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade:
  Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu
  überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Just tried to install updates, then the error reporting popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio-utils 1:14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucl   2483 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Aug  3 08:12:26 2021
  ErrorMessage: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu 
überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist
  InstallationDate: Installed on 2021-08-02 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210801)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulsecommon-14.2.so: cannot open 
shared object file: No such file or directory
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: pulseaudio
  Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: 
Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, 
welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Touch-packages] [Bug 1669393] [NEW] Sound card

You have been subscribed to a public bug:

  My Sound  just stopped working  with the LXDE Desktop

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Mar  2 22:15:01 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-62-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-64-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [1028:04a5]
   Subsystem: Dell Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [1028:04a5]
InstallationDate: Installed on 2016-06-28 (247 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Latitude 2120
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=e8f6cc65-b73f-4489-bc62-a90932f2a4e5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0YY3FH
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd10/31/2011:svnDellInc.:pnLatitude2120:pvr:rvnDellInc.:rn0YY3FH:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude 2120
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Mar  2 22:12:51 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 734 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug ubuntu xenial
-- 
 Sound card
https://bugs.launchpad.net/bugs/1669393
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1823521] Re: on_ac_power returns 1 if battery is not present