[Touch-packages] [Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

2021-04-09 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu4

---
gtk+3.0 (3.24.25-1ubuntu4) hirsute; urgency=medium

  * debian/patches/git_wayland_fonts.patch:
- cherry pick a fix for GTK applications hitting errors under wayland
  on GNOME40, it isn't in Ubuntu yet but it should make testing the
  new version easier and also updates packages are provided in ppa
  already for testing so it should avoid surprises for those users
  (lp: #1922464)

 -- Sebastien Bacher   Thu, 08 Apr 2021 11:17:35
+0200

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
  daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Applications running with GTK < 3.24.26 crash when running under GNOME
  40. This was fixed in GTK 3.24.26 by MR
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219

  Please package either current GTK 3 (3.24.28) or include the given MR
  in the current build.

  Thanks!

  Example crash:

  ```
  Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffeb8a7640 (LWP 58239)]
  [New Thread 0x7fffeb086640 (LWP 58240)]
  [New Thread 0x7fffea839640 (LWP 58241)]

  (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema
  'org.gnome.settings-daemon.plugins.xsettings' does not contain a key
  named 'antialiasing'

  Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap.
  0x774a5ea7 in g_log_structured_array () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x774a5ea7 in g_log_structured_array ()
  at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x774a62b9 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7735d9d1 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #5  0x7735e030 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #6  0x773625d1 in g_settings_get_enum () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x710d90ea in update_xft_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404
  #8  0x710d3c7d in init_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828
  #9  _gdk_wayland_screen_new (display=0x55a8a0e0)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320
  #10 _gdk_wayland_display_open (display_name=)
  at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617
  #11 0x71072635 in gdk_display_manager_open_display
  (manager=, name=0x0) at 
../../../../gdk/gdkdisplaymanager.c:462
  #12 0x76d011fb in gtk_init_check (argc=, 
argv=)
  at ../../../../gtk/gtkmain.c:1110
  #13 gtk_init_check (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1102
  #14 0x76d0122d in gtk_init (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1167
  #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1)
  at ../test/test-client.vala:32
  #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at 
../test/test-client.vala:9
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libgtk-3-0 3.24.25-1ubuntu3
  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
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr  4 11:11:05 2021
  InstallationDate: Installed on 2018-08-13 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago)

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

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


[Touch-packages] [Bug 1921636] Re: resolved CNAME redirect issues

2021-04-09 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  resolved CNAME redirect issues

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

Bug description:
  I am having issues loading certain websites such as linkedin.com and
  portions of google sites including images.google.com, hotmail.com
  login, etc. After looking through some logs and such I've determined
  that resolved is not properly following CNAMEs to an IP address.
  Querying the DNS server on my network directly for the info works
  fine. Loading the sites from other computers on the network works
  fine.

  In the #systemd IRC channel I was directed to the following two issues:
  https://github.com/systemd/systemd/pull/18892
  https://github.com/systemd/systemd/pull/19009

  System info:
  Ubuntu 20.10
  ii  systemd246.6-1ubuntu1.2 amd64system and service manager
  ii  linux-generic  5.8.0.48.53  amd64Complete Generic Linux kernel 
and headers

  Example:
  [11:06:00] host static-exp1.licdn.com
  Host static-exp1.licdn.com not found: 2(SERVFAIL)
  [11:06:17] resolvectl status
  Global
 LLMNR setting: no   
  MulticastDNS setting: no   
DNSOverTLS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no   
DNS Domain: rhos.bigfiber.net
bigfiber.net 

  Link 2 (enp6s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (enp4s0f0)
Current Scopes: DNS  
  DefaultRoute setting: yes  
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSOverTLS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no   
Current DNS Server: 10.18.1.1
   DNS Servers: 10.18.1.1
DNS Domain: ~.   
rhos.bigfiber.net
bigfiber.net 

  Link 4 (enp4s0f1)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  [11:06:26] host static-exp1.licdn.com 10.18.1.1
  Using domain server:
  Name: 10.18.1.1
  Address: 10.18.1.1#53
  Aliases: 

  static-exp1.licdn.com is an alias for 2-01-2c3e-003d.cdx.cedexis.net.
  2-01-2c3e-003d.cdx.cedexis.net is an alias for li-prod-static.azureedge.net.
  li-prod-static.azureedge.net is an alias for li-prod-static.afd.azureedge.net.
  li-prod-static.afd.azureedge.net is an alias for 
star-azureedge-prod.trafficmanager.net.
  star-azureedge-prod.trafficmanager.net is an alias for 
dual.t-0009.t-msedge.net.
  dual.t-0009.t-msedge.net is an alias for t-0009.t-msedge.net.
  t-0009.t-msedge.net is an alias for Edge-Prod-WSTr3.ctrl.t-0009.t-msedge.net.
  Edge-Prod-WSTr3.ctrl.t-0009.t-msedge.net is an alias for 
edge-prod-wstr3.ctrl.t-0001.trafficmanager.net.
  edge-prod-wstr3.ctrl.t-0001.trafficmanager.net is an alias for 
standard.t-0009.t-msedge.net.
  standard.t-0009.t-msedge.net has address 13.107.213.19
  standard.t-0009.t-msedge.net has address 13.107.246.19
  standard.t-0009.t-msedge.net has IPv6 address 2620:1ec:46::19
  standard.t-0009.t-msedge.net has IPv6 address 2620:1ec:bdf::19

  
  resolved debugging log is attached.

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

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


[Touch-packages] [Bug 1923273] Re: libcaca buffer-overflow

2021-04-09 Thread Seth Arnold
** Information type changed from Private Security 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/1923273

Title:
  libcaca buffer-overflow

Status in libcaca package in Ubuntu:
  New

Bug description:
  Hello Ubuntu Security Team
  I use libfuzzer to test libcaca api .I found two crash

  - https://github.com/cacalabs/libcaca/issues/53

  - https://github.com/cacalabs/libcaca/issues/54

  
  ## Vendor of Product
  https://github.com/cacalabs/libcaca

  
  ## Affected Product Code Base
  libcaca e4968ba
  
  ## Affected Component
  affected component:libcaca.so
  
  ## Affected source code file
  affected source code file(As call stack):

 ->caca_export_canvas_to_memory()  in
  libcaca/caca/codec/export.c

 ->caca_export_memory()in
  libcaca/caca/codec/export.c

 -> export_tga()in  
libcaca/caca/codec/export.c

-> export_troff()   in  
libcaca/caca/codec/export.c

   
  ## Attack Type
  Context-dependent

  
  ## Impact Denial of Service
  true

  
  ## Reference
  https://github.com/cacalabs/libcaca

  
  ## Discoverer
  fdgnneig

  
  ## Verification process and POC

  ### Verification steps:

  1.Get the source code of libcaca:

  2.Compile the libcaca.so library:

  ```shell
  $ cd libcaca
  $ apt-get install automake libtool pkg-config -y
  $ ./bootstrap
  $ ./configure
  $ make

  3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc

  4.Run POC

  
  POC.sh
  ```
  cat << EOF > poc_troff.cc
  #include "config.h"
  #include "caca.h"
  //#include "common-image.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  using namespace std;

  extern "C"  int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
  Size) {

   if(Size<8) return 0;
   size_t len=0;
   char* buffer = (char*)malloc(Size+1);
   memset(buffer,0,Size);
   memcpy(buffer,Data,Size);
   buffer[Size]='\0';
   caca_canvas_t *cv;
   cv = caca_create_canvas(0,0);
   for(int i=0;i<4;i++)
 caca_create_frame(cv,0);
   for(int i=0;i<4;i++){
 caca_set_frame(cv,i);
 caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
   }
   void* reData = caca_export_canvas_to_memory(cv,"troff",);
   if(reData!=NULL) free(reData);
   caca_free_canvas(cv);
   cv=NULL;
   free(buffer);
   buffer=NULL;

  }

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

 size_t  len = 0;
 unsigned char buffer[] = 
{0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11};
 len = sizeof(buffer)/sizeof(unsigned char);
 LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
 printf("%d\n",sizeof(buffer)/sizeof(unsigned char));

 return 0;

  }
  EOF

  clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address
  -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o
  poc_troff

  
  cat << EOF > poc_tga.cc
  #include "config.h"
  #include "caca.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  using namespace std;

  extern "C"  int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
  Size) {

   if(Size<8) return 0;
   size_t len=0;
   char* buffer = (char*)malloc(Size+1);
   memset(buffer,0,Size);
   memcpy(buffer,Data,Size);
   buffer[Size]='\0';
   caca_canvas_t *cv;
   cv = caca_create_canvas(0,0);
   for(int i=0;i<4;i++)
 caca_create_frame(cv,0);
   for(int i=0;i<4;i++){
 caca_set_frame(cv,i);
 caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
   }
   void* reData = caca_export_canvas_to_memory(cv,"tga",);
   if(reData!=NULL) free(reData);
   caca_free_canvas(cv);
   cv=NULL;
   free(buffer);
   buffer=NULL;
 return 0;
  }

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

 size_t  len = 0;
 unsigned char buffer[] = 
{0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11};
 len = sizeof(buffer)/sizeof(unsigned char);
 LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
 printf("%d\n",sizeof(buffer)/sizeof(unsigned char));

 return 0;
  }
  EOF

  clang++ -g poc_tga.cc -O2 -fno-omit-frame-pointer 

[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-09 Thread John Johansen
The cisecurity guide is wrong. While there is info that could be
leveraged, but on a modern system the really sensitive information is
split out into /etc/shadow (which very much should be only readable by
root). The reality is that on a modern system /etc/passwd needs to be
world readable (it is the local user db) for several applications that
users can and do use (eg. ls being able to display who owns a file).

If /etc/passwd is world readable, there is no point in changing the
permissions on the backup file.

If you don't want /etc/passwd be available to all applications/users.
You can use a MAC system to further restrict access to /etc/passwd and
its backup file.

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-09 Thread pkaeding
I suspect the rationale is that there is no need for everyone to be able
to access the backup file, and it does contain information that might be
useful to an attacker. `/etc/passwd`, on the other hand, needs to be
world-readable or else many existing tools would break.


The real-world usefulness to an attacker of data in the backup file, that is 
not in the live file, seems pretty limited, though.

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-09 Thread pkaeding
I agree, it was surprising to me as well. The rationale given is just
this:

```
It is critical to ensure that the /etc/passwd- file is protected from 
unauthorized access. Although it is protected by default, the file permissions 
could be changed either inadvertently or through malicious actions.
```

If you are interested, you can download the guide at
http://workbench.cisecurity.org (I don't recall the specific terms I
clicked through when I downloaded it, but I don't think I'm allowed to
post it here, even though anyone can download it directly for $0)

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923262] Re: backup /etc/passwd- file should be mode 0600

2021-04-09 Thread Seth Arnold
Hello, this sounds like surprising advice to me -- afterall the
/etc/passwd file is 644. I don't know what would be the point of hiding
this 'backup' file. Does the benchmark give a rationale for this?

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  backup /etc/passwd- file should be mode 0600

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  CIS hardening benchmarks (6.1.6) suggest that the /etc/passwd- file
  should be mode 0600 (or more restrictive).

  However, this file is 0644 after it is created when the /etc/passwd
  file is modified. (Ie, a hardening script that creates a hardened
  system for initial use could change this mode, but it will go out of
  compliance the next time a backup file is made.)

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

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


[Touch-packages] [Bug 1923267] [NEW] indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1

2021-04-09 Thread fprietog
Public bug reported:

Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64 
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)

After upgrading these packages:

libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin  2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1

The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):

abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload,
Impossible to read image from path '/run/user/1026/multiload-icons-
Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method
Gio.File.read_async: At least 3 arguments required, but only 2 passed

Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.

Thanks and best reagrds

** Affects: glib2.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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1923267

Title:
  indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2
  to 2.68.0-1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Problem tested in two different environments:
  - Ubuntu 21.04 Beta amd64 
  - Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)

  After upgrading these packages:

  libglib2.0-02.67.5-2 to 2.68.0-1
  libglib2.0-bin  2.67.5-2 to 2.68.0-1
  libglib2.0-data 2.67.5-2 to 2.68.0-1

  The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
  three dots (...) instead of the graphic expected. It's throwing error
  messages to the system journal every second or so (depends of the
  refresh interval selected in the app settings):

  abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
  multiload, Impossible to read image from path '/run/user/1026
  /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
  TypeError: method Gio.File.read_async: At least 3 arguments required,
  but only 2 passed

  Don't know if this is a documented change of that method and the bug
  should be open for the indicator-multiload app. Please, if that's the
  case just let me know to do it.

  Thanks and best reagrds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1923267/+subscriptions

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-09 Thread William Wilson
I have submitted a Debian bug report with the patch suggested, and
updated the bug description.

bluez is pre-installed on the desktop images, but not the server images.
This warning would be very useful for server users that want to install
bluez for the first time.

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-09 Thread William Wilson
** Description changed:

- In the case of upgrading bluez on certain raspberry pi devices, a reboot
- may be required to apply the changes. We should add a check for this
- scenario in the postinst script.
+ In the case of upgrading or installing bluez for the first time on
+ certain raspberry pi devices, a reboot may be required to apply the
+ changes. We should add a check for this scenario in the postinst script.

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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

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


[Touch-packages] [Bug 1873429] Re: Problem with printing in 20.04 version

2021-04-09 Thread Norm
Same problem with an old Epson Stylus NX215.  I can scan but not print.  The 
prompt tells be it was completed but the printer doesn't do anything.  I 
imagine I have the drivers installed as it recognizes the printer, scans and 
thinks it's printing. Seems like a common problem with 20.04.
Not overly techy with terminal etc. Has this been resolved?

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

Title:
  Problem with printing in 20.04 version

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  In previous 19.10 my Epson Stylus CX3600 both prints & scans fine.

  In 20.04 it scans fine, but in print mode the process banners show the
  job is sent to the printer, then printing is complete. However there
  is no print output. I reinstalled the Epson print drivers but without
  success.

  I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the
  printing issue is solved. The Epson is recognised and my documents
  print and scan fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 10:59:10 2020
  InstallationDate: Installed on 2019-12-10 (128 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago)

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

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


[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2021-04-09 Thread Dan Streetman
As suggested in the freedesktop bug, this probably was fixed with the patch 
added for bug 1817738 which is this commit:
https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/85d843af843589ce8538a59e5cb665b8253e380d

I haven't been able to reproduce this myself yet (when using the
plymouth version previous to that fix), but I'll try a few more times
next week.

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * The keyboard on the graphical login screen started on VT1 may stop
  working and or keypresses including passwords are leaked to the
  terminal console running 'behind' the graphical login screen or
  environment.

  [Test Case]

   * Reboot after installing the fixed systemd package.
   * Install sysdig
   * Start sysdig on a remote connection or on a terminal console:
$ sudo sysdig evt.type=ioctl | grep  request=4B4
   * While sysdig is running log in and out 3 times in GDM and press a few keys 
in the graphical session to see if keyboard still works
   * Log in and out on an other terminal console, too, running a few commands 
while being logged in to ensure that keyboard is working.
   * Observe that on terminal consoles the monitored keyboard setter ioctl is 
called with argument=3, but where the graphical screen is active only 
argument=4 is used, unlike with the buggy version observed in 
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14

  [Regression Potential]

   * The fix checks the current keyboard mode of the VT and allows only
  safe mode switches. The potential regression could be not allowing a
  valid mode switch keeping a keyboard in a non-operational mode.
  Testing covers that by typing the keyboard.

  
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1923233] Re: Computer is very slow

2021-04-09 Thread 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/1923233

Title:
  Computer is very slow

Status in xorg package in Ubuntu:
  New

Bug description:
  Lap Top Computer is very slow

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   [  OK  ] Started Manage, Install and Generate Color 
Profiles.
   [  OK  ] Started GNOME Display Manager.
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr  9 12:49:55 2021
  DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:8330]
  InstallationDate: Installed on 2018-02-18 (1145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP Laptop 15-bw0xx
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago)
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8330
  dmi.board.vendor: HP
  dmi.board.version: 27.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bw0xx
  dmi.product.sku: 1GR30LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Tue Nov 20 10:27:42 2018
  xserver.configfile: default
  xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: amdgpu

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

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


[Touch-packages] [Bug 1923233] [NEW] Computer is very slow

2021-04-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Lap Top Computer is very slow

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
 [  OK  ] Started Manage, Install and Generate Color 
Profiles.
 [  OK  ] Started GNOME Display Manager.
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Apr  9 12:49:55 2021
DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:8330]
InstallationDate: Installed on 2018-02-18 (1145 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: HP HP Laptop 15-bw0xx
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago)
dmi.bios.date: 11/01/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8330
dmi.board.vendor: HP
dmi.board.version: 27.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-bw0xx
dmi.product.sku: 1GR30LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Nov 20 10:27:42 2018
xserver.configfile: default
xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Computer is very slow
https://bugs.launchpad.net/bugs/1923233
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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes

2021-04-09 Thread Marcelo Cerri
Still happening with linux-azure 5.8.0-1027.29 for cycle sru-20210315
but also for sru-20210222.

** Tags added: sru-20210222

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

Title:
  ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits
  number of processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions

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


[Touch-packages] [Bug 1923115] Re: Networkd vs udev nic renaming race condition

2021-04-09 Thread Dariusz Gadomski
** Description changed:

  [Impact]
  
  systemd-networkd renames nic just after udev renamed it
  
  e.g
  
  kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
  kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
  systemd-networkd[511]: ens192: Interface name change detected, ens192 has 
been renamed to eth0.
  
  This cause netplan or the other network management pkg can't find proper
  nic sometimes.
  
  This happens on Bionic
  
  Below commit seems to solve this issue.
  
https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b
  
  There are bunch of related commits but above one the customer tested it
  worked.
  
  [Test Plan]
  
  The customer has issue and they could help us to test this.
  Internally they already test this and it worked.
  
  Please refer to github issue's reproduction step as well.
  https://github.com/systemd/systemd/issues/7293#issue-272917058
- 
+ where the test plan is described as:
+ "Reboot a couple of times. Sometimes the interface is renamed correctly. 
Sometimes it is not."
  
  [Where problems could occur]
  
  systemd-networkd should be restarted for this patch. systemd-networkd
  nic renaming could have issue. renaming may not be happening
  unexpectedly. e.g doesn't rename it properly or rename it when it should
  do.
  
  [Others]

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

Title:
  Networkd vs udev nic renaming race condition

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

Bug description:
  [Impact]

  systemd-networkd renames nic just after udev renamed it

  e.g

  kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
  kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
  systemd-networkd[511]: ens192: Interface name change detected, ens192 has 
been renamed to eth0.

  This cause netplan or the other network management pkg can't find
  proper nic sometimes.

  This happens on Bionic

  Below commit seems to solve this issue.
  
https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b

  There are bunch of related commits but above one the customer tested
  it worked.

  [Test Plan]

  The customer has issue and they could help us to test this.
  Internally they already test this and it worked.

  Please refer to github issue's reproduction step as well.
  https://github.com/systemd/systemd/issues/7293#issue-272917058
  where the test plan is described as:
  "Reboot a couple of times. Sometimes the interface is renamed correctly. 
Sometimes it is not."

  [Where problems could occur]

  systemd-networkd should be restarted for this patch. systemd-networkd
  nic renaming could have issue. renaming may not be happening
  unexpectedly. e.g doesn't rename it properly or rename it when it
  should do.

  [Others]

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

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-09 Thread Sebastien Bacher
Thanks for the details. You did address the part about upstreaming the
change to Debian. How important is that notification in practice? If
feels like we should have bluez preinstall on the raspi images if that's
not the case, and if it's pre-install is that really worth the packaging
overhead to have to carry a delta over Debian?

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  In the case of upgrading bluez on certain raspberry pi devices, a
  reboot may be required to apply the changes. We should add a check for
  this scenario in the postinst script.

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

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


[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)

2021-04-09 Thread Serge Hallyn
** Changed in: lxc (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  SRU of LXC 4.0.6 to focal (upstream bugfix release)

Status in lxc package in Ubuntu:
  New
Status in lxc source package in Focal:
  In Progress

Bug description:
  LXC released 4.0.6 as a bugfix release with the following changelog:

  - Improve handling for compatibility architectures for seccomp
  - Harden seccomp notifier implementation
  - Rework parsing of /proc//mountinfo to handle kernel regression
  - Improve network device restoration
  - Significantly cleanup and harden config file parsing
  - Support new capabilities CAP_PERFORM, CAP_BPF, and 
CAP_CHECKPOINT_RESTORE
  - Harden containers started without CAP_NET_ADMIN
* New upstream bugfix release (4.0.5):
  - Support allocating PTS devices from within the container
  - Harden more path/mount handling logics
  - Rework LSM logic to limit initializer use
* Cherry-pick upstream fixes:
  - 0002-commands-fix-check-for-seccomp-notify-support.patch
  - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch
  - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch
  - 0005-cgroups-fix-cgroup-mounting.patch
  - 0006-lsm-remove-obsolute-comment-about-constructor.patch
  - 0007-lxc_attach-include-rexec-conditionally.patch
  - 0008-tree-wide-fix-some-header-inclusions.patch
  - 0009-initutils-fix-missing-includes.patch
  - 0010-configure-support-static-binaries.patch
  - 0011-autotools-enable-static-builds-for-tools.patch
  - 0012-autotools-enable-static-builds-for-commands.patch
  - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch
  - 0014-config-update-ax_pthread.m4.patch
  - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch
  - 0016-autotools-update-build.patch
  - 0017-file_utils-introduce-read_file_at.patch
  - 0018-string_utils-add-must_make_path_relative.patch
  - 0019-cgroups-coding-style-fixes.patch
  - 0020-cgroups-rework-cg_unified_init.patch
  - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch
  - 0022-criu-handle-cgroup2-freezer.patch
  - 0023-mkdir-p-proc-sys-on-container-startup.patch
  - 0024-conf-fix-coding-style.patch
  - 0025-conf-coding-style-fixes.patch
  - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch
  - 0027-attach-invert-child-parent-handling.patch
  - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch
  - 0029-attach-tweak-logging.patch
  - 0030-attach-use-__do_close-for-labelfd.patch
  - 0031-attach-coding-style-fixes.patch
  - 0032-attach-use-free_disarm.patch
  - 0033-attach-s-attach_child_main-do_attach-g.patch
  - 0034-attach-mark-do_attach-as-__noreturn.patch
  - 0035-attach-make-do_attach-void.patch
  - 0036-attach-use-close_prot_errno_disarm.patch
  - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch
  - 0038-cgroups-fix-cgroup-mounting.patch
  - 0039-utils-fix-mount_at.patch
  - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch
  - 0041-cgroups-bpf-fixes.patch
  - 0042-croups-improve-__do_bpf_program_free.patch
  - 0043-cgroups-coding-style-fixes.patch
  - 0044-cgroups-don-t-initiliaze-NULL-log.patch
  - 0045-cgroups-ensure-all-memory-is-zeroed.patch
  - 0046-cgroups-use-zalloc.patch
  - 0047-cgroups-tweak-cgroup-initialization.patch
  - 0048-log-remove-pointless-inline.patch
  - 0049-log-add-lxc_log_get_fd.patch
  - 0050-seccomp-use-lxc_log_get_fd.patch
  - 0051-log-rework-lxc_log_get_level.patch
  - 0052-seccomp-use-lxc_log_get_level.patch
  - 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch
  - 0054-log-add-lxc_log_trace-helper.patch
  - 0055-cgroups-use-PTR_TO_U64.patch
  - 0056-cgroups-align-methods.patch
  - 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch
  - 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch
  - 0059-attach-fix-logging-for-stdfd-replacement.patch
  - 0060-attach-fix-error-checking-for-dup2.patch
  - 0061-cgroups-initialize-variable.patch
  - 0062-commands_utils-don-t-leak-memory.patch
  - 0063-conf-use-lxc_log_trace.patch
  - 0064-confile_utils-use-lxc_log_trace.patch
  - 0065-rexec-check-lseek-return-value.patch

* Cherry-pick upstream bugfix:
  - cgroups: fix armhf builds

* Cherry-pick upstream bugfix:
  - cgfsng: fix cgroup attach cgroup creation

* New upstream bugfix release (4.0.4):
  - Support for new Linux clone flags (clone into cgroup)
  - Support for new Linux VFS system calls
  - Internal symbols are now properly hidden from external consumers
* New upstream bugfix release (4.0.3):
  - 

[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)

2021-04-09 Thread Serge Hallyn
** No longer affects: lxc (Ubuntu Bionic)

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

Title:
  SRU of LXC 4.0.6 to focal (upstream bugfix release)

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

Bug description:
  LXC released 4.0.6 as a bugfix release with the following changelog:

  - Improve handling for compatibility architectures for seccomp
  - Harden seccomp notifier implementation
  - Rework parsing of /proc//mountinfo to handle kernel regression
  - Improve network device restoration
  - Significantly cleanup and harden config file parsing
  - Support new capabilities CAP_PERFORM, CAP_BPF, and 
CAP_CHECKPOINT_RESTORE
  - Harden containers started without CAP_NET_ADMIN
* New upstream bugfix release (4.0.5):
  - Support allocating PTS devices from within the container
  - Harden more path/mount handling logics
  - Rework LSM logic to limit initializer use
* Cherry-pick upstream fixes:
  - 0002-commands-fix-check-for-seccomp-notify-support.patch
  - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch
  - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch
  - 0005-cgroups-fix-cgroup-mounting.patch
  - 0006-lsm-remove-obsolute-comment-about-constructor.patch
  - 0007-lxc_attach-include-rexec-conditionally.patch
  - 0008-tree-wide-fix-some-header-inclusions.patch
  - 0009-initutils-fix-missing-includes.patch
  - 0010-configure-support-static-binaries.patch
  - 0011-autotools-enable-static-builds-for-tools.patch
  - 0012-autotools-enable-static-builds-for-commands.patch
  - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch
  - 0014-config-update-ax_pthread.m4.patch
  - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch
  - 0016-autotools-update-build.patch
  - 0017-file_utils-introduce-read_file_at.patch
  - 0018-string_utils-add-must_make_path_relative.patch
  - 0019-cgroups-coding-style-fixes.patch
  - 0020-cgroups-rework-cg_unified_init.patch
  - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch
  - 0022-criu-handle-cgroup2-freezer.patch
  - 0023-mkdir-p-proc-sys-on-container-startup.patch
  - 0024-conf-fix-coding-style.patch
  - 0025-conf-coding-style-fixes.patch
  - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch
  - 0027-attach-invert-child-parent-handling.patch
  - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch
  - 0029-attach-tweak-logging.patch
  - 0030-attach-use-__do_close-for-labelfd.patch
  - 0031-attach-coding-style-fixes.patch
  - 0032-attach-use-free_disarm.patch
  - 0033-attach-s-attach_child_main-do_attach-g.patch
  - 0034-attach-mark-do_attach-as-__noreturn.patch
  - 0035-attach-make-do_attach-void.patch
  - 0036-attach-use-close_prot_errno_disarm.patch
  - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch
  - 0038-cgroups-fix-cgroup-mounting.patch
  - 0039-utils-fix-mount_at.patch
  - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch
  - 0041-cgroups-bpf-fixes.patch
  - 0042-croups-improve-__do_bpf_program_free.patch
  - 0043-cgroups-coding-style-fixes.patch
  - 0044-cgroups-don-t-initiliaze-NULL-log.patch
  - 0045-cgroups-ensure-all-memory-is-zeroed.patch
  - 0046-cgroups-use-zalloc.patch
  - 0047-cgroups-tweak-cgroup-initialization.patch
  - 0048-log-remove-pointless-inline.patch
  - 0049-log-add-lxc_log_get_fd.patch
  - 0050-seccomp-use-lxc_log_get_fd.patch
  - 0051-log-rework-lxc_log_get_level.patch
  - 0052-seccomp-use-lxc_log_get_level.patch
  - 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch
  - 0054-log-add-lxc_log_trace-helper.patch
  - 0055-cgroups-use-PTR_TO_U64.patch
  - 0056-cgroups-align-methods.patch
  - 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch
  - 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch
  - 0059-attach-fix-logging-for-stdfd-replacement.patch
  - 0060-attach-fix-error-checking-for-dup2.patch
  - 0061-cgroups-initialize-variable.patch
  - 0062-commands_utils-don-t-leak-memory.patch
  - 0063-conf-use-lxc_log_trace.patch
  - 0064-confile_utils-use-lxc_log_trace.patch
  - 0065-rexec-check-lseek-return-value.patch

* Cherry-pick upstream bugfix:
  - cgroups: fix armhf builds

* Cherry-pick upstream bugfix:
  - cgfsng: fix cgroup attach cgroup creation

* New upstream bugfix release (4.0.4):
  - Support for new Linux clone flags (clone into cgroup)
  - Support for new Linux VFS system calls
  - Internal symbols are now properly hidden from external consumers
* New upstream bugfix release (4.0.3):
  - Improvement to cgroupv1/cgroupv2 handling
 

[Touch-packages] [Bug 1923232] [NEW] SRU of LXC 4.0.6 to focal (upstream bugfix release)

2021-04-09 Thread Serge Hallyn
Public bug reported:

LXC released 4.0.6 as a bugfix release with the following changelog:

- Improve handling for compatibility architectures for seccomp
- Harden seccomp notifier implementation
- Rework parsing of /proc//mountinfo to handle kernel regression
- Improve network device restoration
- Significantly cleanup and harden config file parsing
- Support new capabilities CAP_PERFORM, CAP_BPF, and CAP_CHECKPOINT_RESTORE
- Harden containers started without CAP_NET_ADMIN
  * New upstream bugfix release (4.0.5):
- Support allocating PTS devices from within the container
- Harden more path/mount handling logics
- Rework LSM logic to limit initializer use
  * Cherry-pick upstream fixes:
- 0002-commands-fix-check-for-seccomp-notify-support.patch
- 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch
- 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch
- 0005-cgroups-fix-cgroup-mounting.patch
- 0006-lsm-remove-obsolute-comment-about-constructor.patch
- 0007-lxc_attach-include-rexec-conditionally.patch
- 0008-tree-wide-fix-some-header-inclusions.patch
- 0009-initutils-fix-missing-includes.patch
- 0010-configure-support-static-binaries.patch
- 0011-autotools-enable-static-builds-for-tools.patch
- 0012-autotools-enable-static-builds-for-commands.patch
- 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch
- 0014-config-update-ax_pthread.m4.patch
- 0015-configure-add-AC_SYS_LARGEFILE-checking.patch
- 0016-autotools-update-build.patch
- 0017-file_utils-introduce-read_file_at.patch
- 0018-string_utils-add-must_make_path_relative.patch
- 0019-cgroups-coding-style-fixes.patch
- 0020-cgroups-rework-cg_unified_init.patch
- 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch
- 0022-criu-handle-cgroup2-freezer.patch
- 0023-mkdir-p-proc-sys-on-container-startup.patch
- 0024-conf-fix-coding-style.patch
- 0025-conf-coding-style-fixes.patch
- 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch
- 0027-attach-invert-child-parent-handling.patch
- 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch
- 0029-attach-tweak-logging.patch
- 0030-attach-use-__do_close-for-labelfd.patch
- 0031-attach-coding-style-fixes.patch
- 0032-attach-use-free_disarm.patch
- 0033-attach-s-attach_child_main-do_attach-g.patch
- 0034-attach-mark-do_attach-as-__noreturn.patch
- 0035-attach-make-do_attach-void.patch
- 0036-attach-use-close_prot_errno_disarm.patch
- 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch
- 0038-cgroups-fix-cgroup-mounting.patch
- 0039-utils-fix-mount_at.patch
- 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch
- 0041-cgroups-bpf-fixes.patch
- 0042-croups-improve-__do_bpf_program_free.patch
- 0043-cgroups-coding-style-fixes.patch
- 0044-cgroups-don-t-initiliaze-NULL-log.patch
- 0045-cgroups-ensure-all-memory-is-zeroed.patch
- 0046-cgroups-use-zalloc.patch
- 0047-cgroups-tweak-cgroup-initialization.patch
- 0048-log-remove-pointless-inline.patch
- 0049-log-add-lxc_log_get_fd.patch
- 0050-seccomp-use-lxc_log_get_fd.patch
- 0051-log-rework-lxc_log_get_level.patch
- 0052-seccomp-use-lxc_log_get_level.patch
- 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch
- 0054-log-add-lxc_log_trace-helper.patch
- 0055-cgroups-use-PTR_TO_U64.patch
- 0056-cgroups-align-methods.patch
- 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch
- 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch
- 0059-attach-fix-logging-for-stdfd-replacement.patch
- 0060-attach-fix-error-checking-for-dup2.patch
- 0061-cgroups-initialize-variable.patch
- 0062-commands_utils-don-t-leak-memory.patch
- 0063-conf-use-lxc_log_trace.patch
- 0064-confile_utils-use-lxc_log_trace.patch
- 0065-rexec-check-lseek-return-value.patch

  * Cherry-pick upstream bugfix:
- cgroups: fix armhf builds

  * Cherry-pick upstream bugfix:
- cgfsng: fix cgroup attach cgroup creation

  * New upstream bugfix release (4.0.4):
- Support for new Linux clone flags (clone into cgroup)
- Support for new Linux VFS system calls
- Internal symbols are now properly hidden from external consumers
  * New upstream bugfix release (4.0.3):
- Improvement to cgroupv1/cgroupv2 handling
- Various improvements and tests for lxc-usernsexec

Just like Ubuntu itself, upstream releases long term support releases,
e.g. 4.0, and then periodic point releases including all the accumulated
bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change 

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

2021-04-09 Thread William Wilson
The verification passed for focal:

jawn-smith@focal-vm:~$ apt-cache policy procps
procps:
  Installed: 2:3.3.16-1ubuntu2
  Candidate: 2:3.3.16-1ubuntu2.1
  Version table:
 2:3.3.16-1ubuntu2.1 500
500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
 *** 2:3.3.16-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
jawn-smith@focal-vm:~$ ulimit -S -s unlimited
jawn-smith@focal-vm:~$ pgrep bash
pgrep: cannot allocate 4611686018427387903 bytes
jawn-smith@focal-vm:~$ sudo apt install procps
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  procps
1 upgraded, 0 newly installed, 0 to remove and 64 not upgraded.
Need to get 233 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 procps 
amd64 2:3.3.16-1ubuntu2.1 [233 kB]
Fetched 233 kB in 0s (613 kB/s)
(Reading database ... 184500 files and directories currently installed.)
Preparing to unpack .../procps_2%3a3.3.16-1ubuntu2.1_amd64.deb ...
Unpacking procps (2:3.3.16-1ubuntu2.1) over (2:3.3.16-1ubuntu2) ...
Setting up procps (2:3.3.16-1ubuntu2.1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for systemd (245.4-4ubuntu3.6) ...
jawn-smith@focal-vm:~$ ulimit -S -s unlimited
jawn-smith@focal-vm:~$ pgrep bash
1744
jawn-smith@focal-vm:~$


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

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Focal:
  Fix Committed
Status in procps source package in Groovy:
  Fix Committed
Status in procps source package in Hirsute:
  Fix Released
Status in procps package in Debian:
  New

Bug description:
  [Impact]

- Users who have ulimit set high would see either slow
  or failed pgrep and pkill commands
- Users who have ulimit set to unlimited would see
  failed pgrep and pkill commands
- This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
  changed with a newer version of the kernel.

  [Test Case]

- set the ulimit to unlimited by running `ulimit -S -s unlimited`
- run `pgrep bash` to see that the "cannot allocate" error is
   printed and the command has failed.

  [Where Problems Could Occur]

- We have set upper and lower limits on the size of the malloc, but
  if further kernel versions break the call to sysconf in
  unexpected ways we could still see problems.

  [Original Description]

  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
    Installed: 2:3.3.16-1ubuntu2
    500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-09 Thread William Wilson
Seb,

A reboot is needed in this case because the bluetooth device on the
raspberry pi has to be initialized at boot time. Restarting the service
will not cause the device to be brought up.

The hardcoded addresses are the approach used in the pi-bluetooth
package, and recommended by waveform.

As for the description, I could certainly change that to be more
descriptive. This code would want to run on a fresh install of bluez, as
the bluetooth device would not be initialized if the pi had been booted
without bluez installed.

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  In the case of upgrading bluez on certain raspberry pi devices, a
  reboot may be required to apply the changes. We should add a check for
  this scenario in the postinst script.

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

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


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

2021-04-09 Thread Steve Langasek
** Changed in: ubuntu-cdimage
 Assignee: Alireza (alirezat) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

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

2021-04-09 Thread Alireza
** Changed in: ubuntu-cdimage
 Assignee: (unassigned) => Alireza (alirezat)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1921636] Re: resolved CNAME redirect issues

2021-04-09 Thread Dan Streetman
Quite a number of CNAME redirects you have there!

The resolved logs appear to be fine, e.g.:
Mar 28 11:30:27 castle systemd-resolved[73519]: Added positive unauthenticated 
cache entry for standard.t-0009.t-msedge.net IN A 30s on enp4s0f0/INET/10.18.1.1
Mar 28 11:30:27 castle systemd-resolved[73519]: Added positive unauthenticated 
cache entry for standard.t-0009.t-msedge.net IN A 30s on enp4s0f0/INET/10.18.1.1

And when I try to resolve your example hostname it only goes through 2 CNAMES:
$ host static-exp1.licdn.com
static-exp1.licdn.com is an alias for 2-01-2c3e-003d.cdx.cedexis.net.
2-01-2c3e-003d.cdx.cedexis.net is an alias for cs1404.wpc.epsiloncdn.net.
cs1404.wpc.epsiloncdn.net has address 152.199.24.163
cs1404.wpc.epsiloncdn.net has IPv6 address 
2606:2800:21f:fedd:8b7a:88ab:fc7e:fa3b


Do you have a different example hostname that I can try to reproduce this with?

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

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

** Bug watch added: github.com/systemd/systemd/issues #18819
   https://github.com/systemd/systemd/issues/18819

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/18819
   Importance: Unknown
   Status: Unknown

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

Title:
  resolved CNAME redirect issues

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

Bug description:
  I am having issues loading certain websites such as linkedin.com and
  portions of google sites including images.google.com, hotmail.com
  login, etc. After looking through some logs and such I've determined
  that resolved is not properly following CNAMEs to an IP address.
  Querying the DNS server on my network directly for the info works
  fine. Loading the sites from other computers on the network works
  fine.

  In the #systemd IRC channel I was directed to the following two issues:
  https://github.com/systemd/systemd/pull/18892
  https://github.com/systemd/systemd/pull/19009

  System info:
  Ubuntu 20.10
  ii  systemd246.6-1ubuntu1.2 amd64system and service manager
  ii  linux-generic  5.8.0.48.53  amd64Complete Generic Linux kernel 
and headers

  Example:
  [11:06:00] host static-exp1.licdn.com
  Host static-exp1.licdn.com not found: 2(SERVFAIL)
  [11:06:17] resolvectl status
  Global
 LLMNR setting: no   
  MulticastDNS setting: no   
DNSOverTLS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no   
DNS Domain: rhos.bigfiber.net
bigfiber.net 

  Link 2 (enp6s0)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  

  Link 3 (enp4s0f0)
Current Scopes: DNS  
  DefaultRoute setting: yes  
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSOverTLS setting: no   
DNSSEC setting: no   
  DNSSEC supported: no   
Current DNS Server: 10.18.1.1
   DNS Servers: 10.18.1.1
DNS Domain: ~.   
rhos.bigfiber.net
bigfiber.net 

  Link 4 (enp4s0f1)
Current Scopes: none
  DefaultRoute setting: no  
 LLMNR setting: yes 
  MulticastDNS setting: no  
DNSOverTLS setting: no  
DNSSEC setting: no  
  DNSSEC supported: no  
  [11:06:26] host static-exp1.licdn.com 10.18.1.1
  Using domain server:
  Name: 10.18.1.1
  Address: 10.18.1.1#53
  Aliases: 

  static-exp1.licdn.com is an alias for 2-01-2c3e-003d.cdx.cedexis.net.
  2-01-2c3e-003d.cdx.cedexis.net is an alias for li-prod-static.azureedge.net.
  li-prod-static.azureedge.net is an alias for li-prod-static.afd.azureedge.net.
  li-prod-static.afd.azureedge.net is an alias for 
star-azureedge-prod.trafficmanager.net.
  star-azureedge-prod.trafficmanager.net is an alias for 
dual.t-0009.t-msedge.net.
  dual.t-0009.t-msedge.net is an alias for t-0009.t-msedge.net.
  t-0009.t-msedge.net is an alias for Edge-Prod-WSTr3.ctrl.t-0009.t-msedge.net.
  Edge-Prod-WSTr3.ctrl.t-0009.t-msedge.net is an alias for 
edge-prod-wstr3.ctrl.t-0001.trafficmanager.net.
  edge-prod-wstr3.ctrl.t-0001.trafficmanager.net is an alias for 
standard.t-0009.t-msedge.net.
  standard.t-0009.t-msedge.net has address 13.107.213.19
  standard.t-0009.t-msedge.net has address 13.107.246.19
  standard.t-0009.t-msedge.net has IPv6 address 2620:1ec:46::19
  standard.t-0009.t-msedge.net has IPv6 address 2620:1ec:bdf::19

  
  resolved debugging log 

[Touch-packages] [Bug 1923167] Re: Screen flickering- QHD Benq

2021-04-09 Thread Brian Murray
** 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/1923167

Title:
  Screen flickering- QHD Benq

Status in xorg package in Ubuntu:
  New

Bug description:
  The Display continuously flickers when we are using the Displayport 
connection with QHD (2560x1440) Benq-Monitors.
  The affected Hardware is:
  Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx)

  Using a DP to HDMI-Adapter solves the problem with the given resolution. 
  This error occurs in both Ubuntu Releases 18.04 and 20.10.

  This is what we see in the Logs:

  [27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795
  [27.144] (II) AMDGPU(0): Using hsync ranges from config file
  [27.144] (II) AMDGPU(0): Using vrefresh ranges from config file
  [27.144] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
  [27.144] (II) AMDGPU(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 489 495 525 -hsync -vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 
1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 
1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "720x576"x0.0   27.00  720 732 796 864  
576 581 586 625 -hsync -vsync (31.2 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 
2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 
2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 
2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0   27.00  1440 1478 1602 
1716  480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0   27.00  1440 1464 1590 
1728  576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056 
 600 601 605 628 +hsync +vsync (37.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152 
 624 625 628 667 -hsync -vsync (49.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056 
 600 601 604 625 +hsync +vsync (46.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 
1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 
1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
  [30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked
  [33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed

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

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


[Touch-packages] [Bug 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS

2021-04-09 Thread Dan Streetman
Have you tried disabing resolved DNSSEC completely (not only for one
interface) to see if your mobile hotspot works then?

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

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

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

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

Title:
  Mobile phone hotspot unusable due to systemd-resolved not liking the
  DNS

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

Bug description:
  Seen in 20.04.

  Trying to connect to the internet using the mobile phone hotspot is
  impossible due to systemd-resolved not resolving and reporting things
  like:

  resolve call failed: DNSSEC validation failed: incompatible-server

  and

  systemd-resolved[81699]: DNSSEC validation failed for question 
d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN 
PTR: no-signature
  DNSSEC validation failed for question 
b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: 
no-signature

  etc etc.

  Name resolution works just fine from the mobile phone.

  Funny thing is that the issue persists if DNSSEC is disabled via
  resolvectl for the interface:

  Link 3 (wlan0)
Current Scopes: DNS  
  DefaultRoute setting: yes  
 LLMNR setting: yes  
  MulticastDNS setting: no   
DNSOverTLS setting: opportunistic
DNSSEC setting: no   
  DNSSEC supported: no   
Current DNS Server: 192.168.43.1 
   DNS Servers: 192.168.43.1

  Systemd-resolved won't accept the issue to be reported upstream saying
  that a too old version of systemd is being used.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.5
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Mar 22 15:39:23 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (400 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-05-23 (303 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139
  mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733

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

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


[Touch-packages] [Bug 1920107] Re: Failed messages of sd-umoun show with reboot/shutdown

2021-04-09 Thread Michael Vogt
** Package changed: snapd (Ubuntu) => systemd (Ubuntu)

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

Title:
  Failed messages of sd-umoun show with reboot/shutdown

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  We were seeing the same sequence of errors heppened on KVM and ARM
  device running UC20:

  """
  [12450.684692] sd-umoun[5922]: Failed to unmount /oldroot: Device or resource 
busy
  [12450.693515] sd-remou[5923]: Failed to remount '/oldroot/run/mnt/data' 
read-only: Device or resource busy
  [12450.704374] sd-umoun[5924]: Failed to unmount /oldroot/run/mnt/data: 
Device or resource busy
  [12450.714225] sd-umoun[5925]: Failed to unmount /oldroot/run: Device or 
resource busy
  [12450.726073] shutdown[1]: Could not detach loopback /dev/loop0: Device or 
resource busy
  [12450.735481] shutdown[1]: Failed to finalize file systems, loop devices, 
ignoring
  [12451.129165] reboot: Power down
  """

  [Steps to reproduce]

  $ sudo poweroff or $ sudo reboot

  There are few issues may be relevant but the PR listed on below was
  not useful for this case.

  https://github.com/systemd/systemd/issues/14298
  https://github.com/systemd/systemd/issues/14981
  https://github.com/systemd/systemd/pull/15566

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

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


[Touch-packages] [Bug 1920107] Re: Failed messages of sd-umoun show with reboot/shutdown

2021-04-09 Thread Steve Langasek
These messages appear to be coming from finalrd, and leading to an
actual unclean shutdown.

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

Title:
  Failed messages of sd-umoun show with reboot/shutdown

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  We were seeing the same sequence of errors heppened on KVM and ARM
  device running UC20:

  """
  [12450.684692] sd-umoun[5922]: Failed to unmount /oldroot: Device or resource 
busy
  [12450.693515] sd-remou[5923]: Failed to remount '/oldroot/run/mnt/data' 
read-only: Device or resource busy
  [12450.704374] sd-umoun[5924]: Failed to unmount /oldroot/run/mnt/data: 
Device or resource busy
  [12450.714225] sd-umoun[5925]: Failed to unmount /oldroot/run: Device or 
resource busy
  [12450.726073] shutdown[1]: Could not detach loopback /dev/loop0: Device or 
resource busy
  [12450.735481] shutdown[1]: Failed to finalize file systems, loop devices, 
ignoring
  [12451.129165] reboot: Power down
  """

  [Steps to reproduce]

  $ sudo poweroff or $ sudo reboot

  There are few issues may be relevant but the PR listed on below was
  not useful for this case.

  https://github.com/systemd/systemd/issues/14298
  https://github.com/systemd/systemd/issues/14981
  https://github.com/systemd/systemd/pull/15566

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

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


[Touch-packages] [Bug 1923167] [NEW] Screen flickering- QHD Benq

2021-04-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The Display continuously flickers when we are using the Displayport connection 
with QHD (2560x1440) Benq-Monitors.
The affected Hardware is:
Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx)

Using a DP to HDMI-Adapter solves the problem with the given resolution. 
This error occurs in both Ubuntu Releases 18.04 and 20.10.

This is what we see in the Logs:

[27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795
[27.144] (II) AMDGPU(0): Using hsync ranges from config file
[27.144] (II) AMDGPU(0): Using vrefresh ranges from config file
[27.144] (II) AMDGPU(0): Printing DDC gathered Modelines:
[27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
[27.144] (II) AMDGPU(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 489 495 525 -hsync -vsync (31.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 
1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 
1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "720x576"x0.0   27.00  720 732 796 864  
576 581 586 625 -hsync -vsync (31.2 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 
2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 2052 
2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 2492 
2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0   27.00  1440 1478 1602 
1716  480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0   27.00  1440 1464 1590 
1728  576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
[27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
[27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[27.144] (II) AMDGPU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  
624 625 628 667 -hsync -vsync (49.7 kHz e)
[27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  
600 601 604 625 +hsync +vsync (46.9 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 
1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 
1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked
[33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed

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


** Tags: bot-comment flickering igel monitor qhd
-- 
Screen flickering- QHD Benq
https://bugs.launchpad.net/bugs/1923167
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 1920107] [NEW] Failed messages of sd-umoun show with reboot/shutdown

2021-04-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

We were seeing the same sequence of errors heppened on KVM and ARM
device running UC20:

"""
[12450.684692] sd-umoun[5922]: Failed to unmount /oldroot: Device or resource 
busy
[12450.693515] sd-remou[5923]: Failed to remount '/oldroot/run/mnt/data' 
read-only: Device or resource busy
[12450.704374] sd-umoun[5924]: Failed to unmount /oldroot/run/mnt/data: Device 
or resource busy
[12450.714225] sd-umoun[5925]: Failed to unmount /oldroot/run: Device or 
resource busy
[12450.726073] shutdown[1]: Could not detach loopback /dev/loop0: Device or 
resource busy
[12450.735481] shutdown[1]: Failed to finalize file systems, loop devices, 
ignoring
[12451.129165] reboot: Power down
"""

[Steps to reproduce]

$ sudo poweroff or $ sudo reboot

There are few issues may be relevant but the PR listed on below was not
useful for this case.

https://github.com/systemd/systemd/issues/14298
https://github.com/systemd/systemd/issues/14981
https://github.com/systemd/systemd/pull/15566

** Affects: snapd
 Importance: Undecided
 Status: New

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


** Tags: rls-ff-incoming
-- 
Failed messages of sd-umoun show with reboot/shutdown
https://bugs.launchpad.net/bugs/1920107
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

2021-04-09 Thread Dan Streetman
marking invalid for systemd in x, as the seccomp support there is
completely different

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

Status in libseccomp package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in libseccomp source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in libseccomp source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

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

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


[Touch-packages] [Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

2021-04-09 Thread Dan Streetman
openat2 was added upstream in commit 8270e3d8ed3 which is included in
v246 so this is fixed already in g and later, marking as fix released

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

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

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

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

Title:
  Backport 2.5.1 to fix missing openat2 syscall, causing problems for
  fuse-overlayfs in nspawn containers

Status in libseccomp package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in libseccomp source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in libseccomp source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in libseccomp source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

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

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


[Touch-packages] [Bug 1923196] [NEW] Background noise when intel hd audio enters power save

2021-04-09 Thread Thomas Frans
Public bug reported:

There is a very high noise level whenever the audio driver doesn't get
used for a while (after 5-10 seconds). The problem goes away whenever
any sound plays, even a completely silent video. There is a solution
online that sets two values to prevent the audio driver going into power
save state, but the solution isn't permanent and isn't a real solution.
That 'hacky' solution uses the following two commands:

echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save_controller
echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save

Power save sounds like a good feature to have, but there should be an
option to disable it or something when the motherboard/audio card has
high noise levels when it enters power save...

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  thomas 2761 F pulseaudio
 /dev/snd/pcmC1D0p:   thomas 2761 F...m pulseaudio
 /dev/snd/controlC0:  thomas 2761 F pulseaudio
 /dev/snd/timer:  thomas 2761 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  9 14:34:09 2021
InstallationDate: Installed on 2021-02-09 (58 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: High background noise, or volume is too low
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
Background noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.20
dmi.board.name: B450 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug groovy

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

Title:
  Background noise when intel hd audio enters power save

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is a very high noise level whenever the audio driver doesn't get
  used for a while (after 5-10 seconds). The problem goes away whenever
  any sound plays, even a completely silent video. There is a solution
  online that sets two values to prevent the audio driver going into
  power save state, but the solution isn't permanent and isn't a real
  solution. That 'hacky' solution uses the following two commands:

  echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save_controller
  echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save

  Power save sounds like a good feature to have, but there should be an
  option to disable it or something when the motherboard/audio card has
  high noise levels when it enters power save...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 2761 F pulseaudio
   /dev/snd/pcmC1D0p:   thomas 2761 F...m pulseaudio
   /dev/snd/controlC0:  thomas 2761 F pulseaudio
   /dev/snd/timer:  thomas 2761 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 14:34:09 2021
  InstallationDate: Installed on 2021-02-09 (58 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: 

[Touch-packages] [Bug 1923059] Re: ntpd crashes using GPSD_JSON clock

2021-04-09 Thread Ubuntu Foundations Team Bug Bot
The attachment "copy of the upstream patch applied to my rebuild of ntp"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  ntpd crashes using GPSD_JSON clock

Status in ntp package in Ubuntu:
  New

Bug description:
  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  
  # apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu4
Candidate: 1:4.2.8p12+dfsg-3ubuntu4
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu4 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages
  100 /var/lib/dpkg/status

  # arch
  aarch64

  I am trying to use gpsd as a time source for ntp.  When I add this to
  ntp.conf:

  server 127.127.46.0 minpoll 4 maxpoll 4 noselect
  fudge 127.127.46.0 time1 0.0 time2 0.0 refid GPS

  Then ntp will crash shortly after starting although the amount of time
  the daemon runs for is not constant.  Running the normal ntpd command
  and adding -n and -d the last few lines of output are:

   8 Apr 14:34:14 ntpd[88025]: GPSD_JSON(0): GPSD revision=3.20 release=3.20 
protocol=3.14
  refclock_transmit: at 3 127.127.46.0
  refclock_receive: at 3 127.127.46.0
  event at 3 GPSD_JSON(0) 8014 84 reachable
  refclock_sample: n 1 offset -0.221798 disp 0.00 jitter 0.00
  filegen  2 3826877655
  clock_filter: n 1 off -0.221798 del 0.00 dsp 7.937500 jit 0.00
   8 Apr 14:34:16 ntpd[88025]: work_thread.c:219: INSIST(((void *)0) == 
c->workitems[c->head_workitem % c->workitems_alloc]) failed
   8 Apr 14:34:16 ntpd[88025]: exiting (due to assertion failure)
  Aborted (core dumped)

  gpsd is running and has a fix, the PPS and SHM ntp clocks are working
  with ntp.

  # ntpq -crv -pn
  associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
  version="ntpd 4.2.8p12@1.3728-o (1)", processor="aarch64",
  system="Linux/5.4.0-1032-raspi", leap=00, stratum=4, precision=-22,
  rootdelay=30.245, rootdisp=79.073, refid=15.39.164.186,
  reftime=e419899f.4a3ad96f  Thu, Apr  8 2021 14:54:39.289,
  clock=e4198a33.8e7058bf  Thu, Apr  8 2021 14:57:07.556, peer=13164, tc=6,
  mintc=3, offset=0.638826, frequency=-2.295, sys_jitter=0.034515,
  clk_jitter=0.241, clk_wander=0.065, tai=37, leapsec=20170101,
  expire=20211228

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   127.127.22.0.PPS.0 l-   16  3770.000   -0.869   0.028
   127.127.28.0.SHM.   15 l   15   16  3770.000  -119.64   5.299
   pool.example.com.POOL.  16 p-   6400.0000.000   0.000
  *  176.58.109.199   3 u   15   64  3770.4150.854   0.179
  +  176.58.109.199   3 u   18   64  3770.5670.825   0.140

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

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


[Touch-packages] [Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

2021-04-09 Thread Snufkin
hello

I'have Ubuntu and this work around not work for me how can I fix it
Please :(

below details:

Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal


Demons.conf:

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; remixing-produce-lfe = no
; remixing-consume-lfe = no
; lfe-crossover-freq = 0

; flat-volumes = no

; rescue-streams = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 48000
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 1
; deferred-volume-extra-delay-usec = 0

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

Title:
  Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Fedora:
  Confirmed

Bug description:
  Whenever I choose the Jabra Evolve 65 UC Headset as the playback
  device, there are sound chipmunks. The same was the case with Jabra
  Motion Headset as well. But those two headsets worked perfectly in
  Windows, Mac OS and Android.

  There was a workaround mentioned in
  https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the
  contents of /etc/pulseaudio/daemon.conf :

  Changing

   ;default-sample-rate=44100

  to

   default-sample-rate=48000

  and then running

   pulseaudio -k

  made the sound on Jabra good (no more chipmunks). Also, when I opened
  the Sound Settings with the changes in daemon.conf in place, there
  seems to be some distortions in headset sound, which goes away few
  seconds after I close the sound settings window.

  This problem should be fixed, as many new Linux users will find it
  difficult to edit files requiring root access, and those who do not
  use command line won't be okay with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   itachi10880 F...m pulseaudio
   /dev/snd/controlC2:  itachi10880 F pulseaudio
   /dev/snd/controlC1:  itachi10880 F pulseaudio
   /dev/snd/controlC0:  itachi10880 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 10 21:11:18 2017
  InstallationDate: Installed on 2016-08-27 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-09 Thread Bob H
I understand, thanks Rik.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Fix Released
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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


[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-09 Thread Rik Mills
The ISO file integrity check was recently changed so it now runs in the
background. It does not show while booting or delay boot.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Fix Released
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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


[Touch-packages] [Bug 1923059] Re: ntpd crashes using GPSD_JSON clock

2021-04-09 Thread James Dingwall
** Patch added: "copy of the upstream patch applied to my rebuild of ntp"
   
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1923059/+attachment/5485965/+files/ntp-1738.diff

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

Title:
  ntpd crashes using GPSD_JSON clock

Status in ntp package in Ubuntu:
  New

Bug description:
  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  
  # apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu4
Candidate: 1:4.2.8p12+dfsg-3ubuntu4
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu4 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages
  100 /var/lib/dpkg/status

  # arch
  aarch64

  I am trying to use gpsd as a time source for ntp.  When I add this to
  ntp.conf:

  server 127.127.46.0 minpoll 4 maxpoll 4 noselect
  fudge 127.127.46.0 time1 0.0 time2 0.0 refid GPS

  Then ntp will crash shortly after starting although the amount of time
  the daemon runs for is not constant.  Running the normal ntpd command
  and adding -n and -d the last few lines of output are:

   8 Apr 14:34:14 ntpd[88025]: GPSD_JSON(0): GPSD revision=3.20 release=3.20 
protocol=3.14
  refclock_transmit: at 3 127.127.46.0
  refclock_receive: at 3 127.127.46.0
  event at 3 GPSD_JSON(0) 8014 84 reachable
  refclock_sample: n 1 offset -0.221798 disp 0.00 jitter 0.00
  filegen  2 3826877655
  clock_filter: n 1 off -0.221798 del 0.00 dsp 7.937500 jit 0.00
   8 Apr 14:34:16 ntpd[88025]: work_thread.c:219: INSIST(((void *)0) == 
c->workitems[c->head_workitem % c->workitems_alloc]) failed
   8 Apr 14:34:16 ntpd[88025]: exiting (due to assertion failure)
  Aborted (core dumped)

  gpsd is running and has a fix, the PPS and SHM ntp clocks are working
  with ntp.

  # ntpq -crv -pn
  associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
  version="ntpd 4.2.8p12@1.3728-o (1)", processor="aarch64",
  system="Linux/5.4.0-1032-raspi", leap=00, stratum=4, precision=-22,
  rootdelay=30.245, rootdisp=79.073, refid=15.39.164.186,
  reftime=e419899f.4a3ad96f  Thu, Apr  8 2021 14:54:39.289,
  clock=e4198a33.8e7058bf  Thu, Apr  8 2021 14:57:07.556, peer=13164, tc=6,
  mintc=3, offset=0.638826, frequency=-2.295, sys_jitter=0.034515,
  clk_jitter=0.241, clk_wander=0.065, tai=37, leapsec=20170101,
  expire=20211228

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   127.127.22.0.PPS.0 l-   16  3770.000   -0.869   0.028
   127.127.28.0.SHM.   15 l   15   16  3770.000  -119.64   5.299
   pool.example.com.POOL.  16 p-   6400.0000.000   0.000
  *  176.58.109.199   3 u   15   64  3770.4150.854   0.179
  +  176.58.109.199   3 u   18   64  3770.5670.825   0.140

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

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


[Touch-packages] [Bug 1923059] Re: ntpd crashes using GPSD_JSON clock

2021-04-09 Thread James Dingwall
I rebuilt ntp to include the patch and it has run for over 10 minutes
without crashing after enabling the GPSD_JSON reference clock which
suggest it has resolved the problem.

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

Title:
  ntpd crashes using GPSD_JSON clock

Status in ntp package in Ubuntu:
  New

Bug description:
  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  
  # apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu4
Candidate: 1:4.2.8p12+dfsg-3ubuntu4
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu4 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages
  100 /var/lib/dpkg/status

  # arch
  aarch64

  I am trying to use gpsd as a time source for ntp.  When I add this to
  ntp.conf:

  server 127.127.46.0 minpoll 4 maxpoll 4 noselect
  fudge 127.127.46.0 time1 0.0 time2 0.0 refid GPS

  Then ntp will crash shortly after starting although the amount of time
  the daemon runs for is not constant.  Running the normal ntpd command
  and adding -n and -d the last few lines of output are:

   8 Apr 14:34:14 ntpd[88025]: GPSD_JSON(0): GPSD revision=3.20 release=3.20 
protocol=3.14
  refclock_transmit: at 3 127.127.46.0
  refclock_receive: at 3 127.127.46.0
  event at 3 GPSD_JSON(0) 8014 84 reachable
  refclock_sample: n 1 offset -0.221798 disp 0.00 jitter 0.00
  filegen  2 3826877655
  clock_filter: n 1 off -0.221798 del 0.00 dsp 7.937500 jit 0.00
   8 Apr 14:34:16 ntpd[88025]: work_thread.c:219: INSIST(((void *)0) == 
c->workitems[c->head_workitem % c->workitems_alloc]) failed
   8 Apr 14:34:16 ntpd[88025]: exiting (due to assertion failure)
  Aborted (core dumped)

  gpsd is running and has a fix, the PPS and SHM ntp clocks are working
  with ntp.

  # ntpq -crv -pn
  associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
  version="ntpd 4.2.8p12@1.3728-o (1)", processor="aarch64",
  system="Linux/5.4.0-1032-raspi", leap=00, stratum=4, precision=-22,
  rootdelay=30.245, rootdisp=79.073, refid=15.39.164.186,
  reftime=e419899f.4a3ad96f  Thu, Apr  8 2021 14:54:39.289,
  clock=e4198a33.8e7058bf  Thu, Apr  8 2021 14:57:07.556, peer=13164, tc=6,
  mintc=3, offset=0.638826, frequency=-2.295, sys_jitter=0.034515,
  clk_jitter=0.241, clk_wander=0.065, tai=37, leapsec=20170101,
  expire=20211228

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   127.127.22.0.PPS.0 l-   16  3770.000   -0.869   0.028
   127.127.28.0.SHM.   15 l   15   16  3770.000  -119.64   5.299
   pool.example.com.POOL.  16 p-   6400.0000.000   0.000
  *  176.58.109.199   3 u   15   64  3770.4150.854   0.179
  +  176.58.109.199   3 u   18   64  3770.5670.825   0.140

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

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


[Touch-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

2021-04-09 Thread Daniel van Vugt
Also proposed to Ubuntu in: https://salsa.debian.org/gnome-
team/mutter/-/merge_requests/72

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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


[Touch-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-09 Thread Daniel van Vugt
** Tags added: amdgpu radeon

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-09 Thread jeremyszu
When I attached another monitor to dGPU (which means connecting monitor
to each iGPU and dGPU), then there is no problem.

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

2021-04-09 Thread Daniel van Vugt
Second fix proposed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1817

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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


[Touch-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-09 Thread jeremyszu
I tried to install hirsute daily build
(495fe189e32d873ba79d7753134c22353ea89e8e6d62498f6c825a5de6a8a4a7) and
didn't see this issue.

but the xorg might have some problems when using hirsute.

here is the result of $ xrandr -d :0 --prop
---
PRIME Synchronization: 0 
supported: 0, 1
GAMMA_LUT_SIZE: 4096 
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096 
range: (0, -1)
GAMMA_LUT: 0 
range: (0, 65535)
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
0 1 
DEGAMMA_LUT: 0 
range: (0, 65535)
TearFree: auto 
supported: off, on, auto
subconnector: HDMI 
supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
HDCP Content Type: HDCP Type0 
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired 
supported: Undesired, Desired, Enabled
vrr_capable: 0 
range: (0, 1)
max bpc: 8 
range: (8, 16)
underscan vborder: 0 
range: (0, 128)
underscan hborder: 0 
range: (0, 128)
underscan: off 
supported: off, on, auto
scaling mode: None 
supported: None, Full, Center, Full aspect
link-status: Good 
supported: Good, Bad
CONNECTOR_ID: 80 
supported: 80
non-desktop: 0 
range: (0, 1)
---

When issuing the same command on hirsute daily build, it shows
---
non-desktop: 0 
range: (0, 1)
---
only.


Tried packages from 
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers doesn't help.

** Tags added: oem-priority originate-from-1916427 stella

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1923153] [NEW] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-09 Thread jeremyszu
Public bug reported:

[Steps to reproduce this issue]

1. Install a focal base image
2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
4. After logging it, the display shows laggy.

[Additional information]
1. doesn't see this issue if selecting 'Wayland'

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
Uname: Linux 5.10.0-1019-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr  9 16:23:42 2021
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Renoir [103c:872b]
InstallationDate: Installed on 2021-04-09 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.release: 2.0
dmi.bios.vendor: HP
dmi.bios.version: S09 Ver. 02.02.00
dmi.board.name: 872B
dmi.board.vendor: HP
dmi.board.version: KBC Version 09.94.00
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 9.148
dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: Confirmed

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


** Tags: amd64 apport-bug focal oem-priority originate-from-1916427 stella 
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/1923153

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir 

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

2021-04-09 Thread Daniel van Vugt
Thanks for the bug report. We will need to see a screenshot or original
log of the problem while it is happening. Not just a vague recollection
that there was a problem.

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

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Xorg freeze
+ Freeze

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

Title:
  Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Actually this is not the version that freezes the boot. With a clean
  install both of groovy and focal I can use the computer with no
  problem. The bug appears after installing the prompted updates at
  first login.

  I have three different outcomes when it comes to booting:
  - Blinking underscore cursor (with no error messages on the screen)
  - iwlwifi unhandled algorithm 0x707 error
  - FAULT found at  [IBUS] not exactly this message

  I guess I could install updates one by one and see which one faults at
  boot, then boot through tty4 (it is the only way I've found to do it
  after boot fails, or freezes) and then link the logs to this  issue.

  I could really use some guidance from a more experienced user because
  I don't really know how to debug this things :D

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 08:51:36 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09d9]
 Subsystem: Dell GP107M [GeForce MX350] [1028:09d9]
  InstallationDate: Installed on 2021-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. Inspiron 7400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b912e5af-f189-4002-8e26-306f96626d10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 072W08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd02/26/2021:br1.5:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn072W08:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7400
  dmi.product.sku: 09D9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


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

2021-04-09 Thread 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/1923140

Title:
  Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Actually this is not the version that freezes the boot. With a clean
  install both of groovy and focal I can use the computer with no
  problem. The bug appears after installing the prompted updates at
  first login.

  I have three different outcomes when it comes to booting:
  - Blinking underscore cursor (with no error messages on the screen)
  - iwlwifi unhandled algorithm 0x707 error
  - FAULT found at  [IBUS] not exactly this message

  I guess I could install updates one by one and see which one faults at
  boot, then boot through tty4 (it is the only way I've found to do it
  after boot fails, or freezes) and then link the logs to this  issue.

  I could really use some guidance from a more experienced user because
  I don't really know how to debug this things :D

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 08:51:36 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09d9]
 Subsystem: Dell GP107M [GeForce MX350] [1028:09d9]
  InstallationDate: Installed on 2021-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. Inspiron 7400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b912e5af-f189-4002-8e26-306f96626d10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 072W08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd02/26/2021:br1.5:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn072W08:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7400
  dmi.product.sku: 09D9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


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

2021-04-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Actually this is not the version that freezes the boot. With a clean
install both of groovy and focal I can use the computer with no problem.
The bug appears after installing the prompted updates at first login.

I have three different outcomes when it comes to booting:
- Blinking underscore cursor (with no error messages on the screen)
- iwlwifi unhandled algorithm 0x707 error
- FAULT found at  [IBUS] not exactly this message

I guess I could install updates one by one and see which one faults at
boot, then boot through tty4 (it is the only way I've found to do it
after boot fails, or freezes) and then link the logs to this  issue.

I could really use some guidance from a more experienced user because I
don't really know how to debug this things :D

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  9 08:51:36 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics [1028:09d9]
   Subsystem: Dell GP107M [GeForce MX350] [1028:09d9]
InstallationDate: Installed on 2021-04-08 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: Dell Inc. Inspiron 7400
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b912e5af-f189-4002-8e26-306f96626d10 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2021
dmi.bios.release: 1.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 072W08
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd02/26/2021:br1.5:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn072W08:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7400
dmi.product.sku: 09D9
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug freeze groovy ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1923140
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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-09 Thread Bob H
I downloaded Kubuntu daily build for 2021-04-09 and put the iso on a thumb drive
I am using the 'safe graphics' option needed by my system.

The on screen display of the initial file check process, with option to
skip, still doesn't show.

A splash screen eventually shows and flickers a few times before the
screen with 'try live' and 'install now' buttons appears.

I can now successfully access with the 'live screen' option,  also the
'install now' button works.

I successfully installed Kubuntu Hippo via the 'install now' button.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Fix Released
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug 

[Touch-packages] [Bug 1923115] Re: Networkd vs udev nic renaming race condition

2021-04-09 Thread Seyeong Kim
** Description changed:

  [Impact]
  
  systemd-networkd renames nic just after udev renamed it
  
  e.g
  
  kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
  kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
  systemd-networkd[511]: ens192: Interface name change detected, ens192 has 
been renamed to eth0.
  
  This cause netplan or the other network management pkg can't find proper
  nic sometimes.
  
  This happens on Bionic
  
  Below commit seems to solve this issue.
  
https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b
  
  There are bunch of related commits but above one the customer tested it
  worked.
  
  [Test Plan]
  
  The customer has issue and they could help us to test this.
  Internally they already test this and it worked.
  
+ Please refer to github issue's reproduction step as well.
+ https://github.com/systemd/systemd/issues/7293#issue-272917058
+ 
+ 
  [Where problems could occur]
  
  systemd-networkd should be restarted for this patch. systemd-networkd
  nic renaming could have issue. renaming may not be happening
  unexpectedly. e.g doesn't rename it properly or rename it when it should
  do.
  
  [Others]

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

Title:
  Networkd vs udev nic renaming race condition

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

Bug description:
  [Impact]

  systemd-networkd renames nic just after udev renamed it

  e.g

  kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
  kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
  systemd-networkd[511]: ens192: Interface name change detected, ens192 has 
been renamed to eth0.

  This cause netplan or the other network management pkg can't find
  proper nic sometimes.

  This happens on Bionic

  Below commit seems to solve this issue.
  
https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b

  There are bunch of related commits but above one the customer tested
  it worked.

  [Test Plan]

  The customer has issue and they could help us to test this.
  Internally they already test this and it worked.

  Please refer to github issue's reproduction step as well.
  https://github.com/systemd/systemd/issues/7293#issue-272917058

  
  [Where problems could occur]

  systemd-networkd should be restarted for this patch. systemd-networkd
  nic renaming could have issue. renaming may not be happening
  unexpectedly. e.g doesn't rename it properly or rename it when it
  should do.

  [Others]

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

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


[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-09 Thread Leó Kolbeinsson
I can confirm the fix works.

Tested daily ISO Kubuntu Hirsute ISO 20210409 with VirtualBox and no
errors.

See results here:
http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/229247/testcases/1300/results

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Fix Released
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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