from:"Joshua"

I can confirm for myself now aswell that I am experiencing issues. Some
applications, most of them listed above in one way or another can be
found to properly be unable to handle these images.

Gdk-pixbuf still crashes but no longer is a buffer overwrite.
Technically a win - but the key issue is apps do not know how to respond
to what to do when gdk-pixbuf dies.

Take eye of gnome - if you open a file directly from terminal using one
of the POCs, it is fine and reads the gdk-pixbuf error correctly. But
cycle to the next POC and it crashes.

Probably a lot of this is apps being tied into gdk-pixbuf, and if I am
correct it is a part of Gtk so apps are sort of forced to be connected
to it. When one breaks down, it's like a cable wire. In the future, for
stability purposes patches need to be made to apps so whenever a
component like gdk-pixbuf fails, the rest of the app doesn't (or has
some fallback state)

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

** Attachment added: "Eye of MATE Crash"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605633/+files/EOMCrash.tar.gz

** Description changed:

  [Impact]
  
   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer limit.
  
   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.
  
   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.
  
   * Any app using gdk-pixbuf is affected, mainly file managers and image
  viewers.
  
  [Test Plan]
  
   * Take the POC's - they can be found in the issue in the GNOME repo
  
   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
+  - Eye of MATE (eom) segfaults
  
   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.
  
  [Where problems could occur]
  
   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.
  
   * It is possible, and has happened in the past (which has been patched)
  that other bad GIFs can cause other crashes.
  
   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems
  
   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs
  
  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.
  
  [Other Info]
  
   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
-  * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
+  * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

** Attachment added: "Nautilus crash"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605632/+files/NautilusCrash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Hmm… check Jammy/Kinetic. Can you send me the crash file/syslog?

Some apps I think have proper handling of bad files while others don’t.
For example, EOG can detect its a bad file.

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

** Description changed:

  [Impact]
  
-  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
+  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
-  * The GIF loader runs out of memory with specifically crafted files
+  * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer limit.
  
-  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
+  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.
  
-  * Or, in other ways, bad gif files in other applications can open the
+  * Or, in other ways, bad gif files in other applications can open the
  door for exploits.
  
-  * Any app using gdk-pixbuf is affected, mainly file managers and image
+  * Any app using gdk-pixbuf is affected, mainly file managers and image
  viewers.
  
  [Test Plan]
  
-  * Take the POC's - they can be found in the issue in the GNOME repo
+  * Take the POC's - they can be found in the issue in the GNOME repo
  
-  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
-  - Nautilus, GNOME's file manager
-  - Nemo, Cinnamon's file manager
-  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
-  - PCManFM, LXDE's file manager which straight up crashes
-  I have not been able to produce any results with Caja (MATE's file manager) 
but have personally experienced issues with Nautilus. POC logs and crashes are 
attached.
+  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
+  - Nautilus, GNOME's file manager
+  - Nemo, Cinnamon's file manager
+  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
+  - PCManFM, LXDE's file manager which straight up crashes
+  - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
+  - Eye of GNOME (eog) triggers the segfault in syslog
  
-  * If you or the system couldn't tell something is wrong, cat
+  * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.
  
  [Where problems could occur]
  
-  * The patch itself is simple, but since gdk-pixbuf is often used with
+  * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.
  
-  * It is possible, and has happened in the past (which has been patched)
+  * It is possible, and has happened in the past (which has been patched)
  that other bad GIFs can cause other crashes.
  
-  * That patch is essentially overflow checks -  changes with GLib
+  * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems
  
-  * Other failures to properly handle GIFs and broken or intentionally
+  * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs
  
  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.
  
  [Other Info]
-  
-  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
-  * Files attached are examples or crashes
-  * Again, all apps using gdk-pixbuf are affected
-  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
-  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
+ 
+  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
+  * Files attached are examples or crashes
+  * Again, all apps using gdk-pixbuf are affected
+  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
+  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

** Description changed:

- There is a buffer overwrite in gdk-pixbuf. I will eventually create a
- whole SRU document with how to reproduce and all, but I'll just say it
- is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
- causes the entire system to run out of memory. (With firefox, 1612/3922
- MB - which says something.)
+ [Impact]
  
- It may be possible all apps using gdk-pixbuf can have a problem handling
- files like the PoC.
+  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
- https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
+  * The GIF loader runs out of memory with specifically crafted files
+ with bad frame data (and images with its sizes) over the integer limit.
+ 
+  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
+ RAM systems like my old iMac, the system can completely run out of
+ memory.
+ 
+  * Or, in other ways, bad gif files in other applications can open the
+ door for exploits.
+ 
+  * Any app using gdk-pixbuf is affected, mainly file managers and image
+ viewers.
+ 
+ [Test Plan]
+ 
+  * Take the POC's - they can be found in the issue in the GNOME repo
+ 
+  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
+  - Nautilus, GNOME's file manager
+  - Nemo, Cinnamon's file manager
+  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
+  - PCManFM, LXDE's file manager which straight up crashes
+  I have not been able to produce any results with Caja (MATE's file manager) 
but have personally experienced issues with Nautilus. POC logs and crashes are 
attached.
+ 
+  * If you or the system couldn't tell something is wrong, cat
+ /var/log/syslog and enjoy the segfaults or out of memory warnings or
+ even kernel spam.
+ 
+ [Where problems could occur]
+ 
+  * The patch itself is simple, but since gdk-pixbuf is often used with
+ GTK apps a mistake here could be problematic.
+ 
+  * It is possible, and has happened in the past (which has been patched)
+ that other bad GIFs can cause other crashes.
+ 
+  * That patch is essentially overflow checks -  changes with GLib
+ (GNOME's, not to be confused with glibc) and the functions used in not
+ only the patch but all of gdk-pixbuf can cause problems
+ 
+  * Other failures to properly handle GIFs and broken or intentionally
+ tampered GIFs can continue and always will open the door for security
+ holes for other bugs
+ 
+ * Again, overall a simple patch but as long as the GIFs remain handled
+ properly, and no changes to the GLib functions are made and to other
+ apps that use gdk-pixbuf (and assuming are not affected by the change
+ and still work), the patch does not have much regression potential.
+ 
+ [Other Info]
+  
+  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
+  * Files attached are examples or crashes
+  * Again, all apps using gdk-pixbuf are affected
+  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
+  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Here's proposal focal patch - I noticed some whitespaces but those are
in the code and not introduced by me.

** Patch added: "Proposed focal patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605438/+files/gdk-pixbuf_2.40.0+dfsg-3ubuntu0.3.debdiff

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => In Progress

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

PCManFM crashed to this.

that's my last POC - I'm going to create the patch

** Attachment added: "pcmanfmcrash.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605437/+files/pcmanfmcrash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Thunar, which uses tumbler for thumbnailing, produced a crash.

** Attachment added: "Tumbler (xfce thumbnailer crash)"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605436/+files/libgdkpixbufloader-gif-crash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Here is what it did to my iMac.

** Attachment added: "OldiMacSyslog"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605435/+files/OldiMacSyslog

** Changed in: gdk-pixbuf (Ubuntu)
 Assignee: (unassigned) => Joshua Peisach (itzswirlz)

** Tags removed: jammy
** Tags added: bionic xenial

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1982898] [NEW] CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

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

Public security bug reported:

There is a buffer overwrite in gdk-pixbuf. I will eventually create a
whole SRU document with how to reproduce and all, but I'll just say it
is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
causes the entire system to run out of memory. (With firefox, 1612/3922
MB - which says something.)

It may be possible all apps using gdk-pixbuf can have a problem handling
files like the PoC.

https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Tue Jul 26 19:33:41 2022
InstallationDate: Installed on 2021-11-24 (244 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
SourcePackage: gdk-pixbuf
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Assignee: Joshua Peisach (itzswirlz)
 Status: New


** Tags: amd64 apport-bug bionic focal xenial

** Information type changed from Private Security to Public Security

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-46829

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1981769] ProcCpuinfoMinimal.txt

2022-07-15 Thread Joshua McClintock

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1981769/+attachment/5603369/+files/ProcCpuinfoMinimal.txt

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

Title:
  blkid fails to find btrfs zoned filesystem label or uuid

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System Info:

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem

  sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
  btrfs-progs v5.16.2
  See http://btrfs.wiki.kernel.org for more information.

  Resetting device zones /dev/sdb (52156 zones) ...
  NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)

  Label:  cf1657839355
  UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
  Node size:  16384
  Sector size:4096
  Filesystem size:12.73TiB
  Block group profiles:
Data: single  256.00MiB
Metadata: single  256.00MiB
System:   single  256.00MiB
  SSD detected:   no
  Zoned device:   yes
Zone size:256.00MiB
  Incompat features:  extref, skinny-metadata, no-holes, zoned
  Runtime features:   free-space-tree
  Checksum:   crc32c
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  112.73TiB  /dev/sdb

  2. Try to use LABEL method to mount

  sudo mount LABEL=cf1657839355 cf1657839355
  mount: cf1657839355: can't find LABEL=cf1657839355.

  Expected that LABEL would be found.  I suspect that libblkid is where
  the issue is since this commands returns all of my other block devices
  except for /dev/sdb.

  sudo blkid|grep sdb

  
  It will mount using hard coded device path

  sudo mount /dev/sdb cf1657839355
  df -h /dev/sdb
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb 13T  3.5M   13T   1% /cf1657839355
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-05-20 (421 days ago)
  InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  Package: util-linux 2.37.2-4ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-14 (1 days ago)
  UserGroups: N/A
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1981769] Re: blkid fails to find btrfs zoned filesystem label or uuid

2022-07-15 Thread Joshua McClintock

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  System Info:
  
  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04
  
  
  1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem
  
  sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
  btrfs-progs v5.16.2
  See http://btrfs.wiki.kernel.org for more information.
  
  Resetting device zones /dev/sdb (52156 zones) ...
  NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)
  
  Label:  cf1657839355
  UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
  Node size:  16384
  Sector size:4096
  Filesystem size:12.73TiB
  Block group profiles:
Data: single  256.00MiB
Metadata: single  256.00MiB
System:   single  256.00MiB
  SSD detected:   no
  Zoned device:   yes
Zone size:256.00MiB
  Incompat features:  extref, skinny-metadata, no-holes, zoned
  Runtime features:   free-space-tree
  Checksum:   crc32c
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  112.73TiB  /dev/sdb
  
  2. Try to use LABEL method to mount
  
  sudo mount LABEL=cf1657839355 cf1657839355
  mount: cf1657839355: can't find LABEL=cf1657839355.
  
  Expected that LABEL would be found.  I suspect that libblkid is where
  the issue is since this commands returns all of my other block devices
  except for /dev/sdb.
  
  sudo blkid|grep sdb
  
  
  It will mount using hard coded device path
  
  sudo mount /dev/sdb cf1657839355
  df -h /dev/sdb
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb 13T  3.5M   13T   1% /cf1657839355
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2021-05-20 (421 days ago)
+ InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
+ Package: util-linux 2.37.2-4ubuntu3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
+ Tags:  jammy uec-images
+ Uname: Linux 5.15.0-41-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-07-14 (1 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1981769/+attachment/5603368/+files/Dependencies.txt

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

Title:
  blkid fails to find btrfs zoned filesystem label or uuid

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System Info:

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem

  sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
  btrfs-progs v5.16.2
  See http://btrfs.wiki.kernel.org for more information.

  Resetting device zones /dev/sdb (52156 zones) ...
  NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)

  Label:  cf1657839355
  UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
  Node size:  16384
  Sector size:4096
  Filesystem size:12.73TiB
  Block group profiles:
Data: single  256.00MiB
Metadata: single  256.00MiB
System:   single  256.00MiB
  SSD detected:   no
  Zoned device:   yes
Zone size:256.00MiB
  Incompat features:  extref, skinny-metadata, no-holes, zoned
  Runtime features:   free-space-tree
  Checksum:   crc32c
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  112.73TiB  /dev/sdb

  2. Try to use LABEL method to mount

  sudo mount LABEL=cf1657839355 cf1657839355
  mount: cf1657839355: can't find LABEL=cf1657839355.

  Expected that LABEL would be found.  I suspect that libblkid is where
  the issue is since this commands returns all of my other block devices
  except for /dev/sdb.

  sudo blkid|grep sdb

  
  It will mount using hard coded device path

  sudo mount /dev/sdb cf1657839355
  df -h /dev/sdb
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb 13T  3.5M   13T   1% /cf1657839355
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1

[Touch-packages] [Bug 1981769] Re: blkid fails to find btrfs zoned filesystem label or uuid

2022-07-15 Thread Joshua McClintock

The system this is on has some private information.  Will the command
you want me to run post this publically?

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

Title:
  blkid fails to find btrfs zoned filesystem label or uuid

Status in util-linux package in Ubuntu:
  New

Bug description:
  System Info:

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem

  sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
  btrfs-progs v5.16.2
  See http://btrfs.wiki.kernel.org for more information.

  Resetting device zones /dev/sdb (52156 zones) ...
  NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)

  Label:  cf1657839355
  UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
  Node size:  16384
  Sector size:4096
  Filesystem size:12.73TiB
  Block group profiles:
Data: single  256.00MiB
Metadata: single  256.00MiB
System:   single  256.00MiB
  SSD detected:   no
  Zoned device:   yes
Zone size:256.00MiB
  Incompat features:  extref, skinny-metadata, no-holes, zoned
  Runtime features:   free-space-tree
  Checksum:   crc32c
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  112.73TiB  /dev/sdb

  2. Try to use LABEL method to mount

  sudo mount LABEL=cf1657839355 cf1657839355
  mount: cf1657839355: can't find LABEL=cf1657839355.

  Expected that LABEL would be found.  I suspect that libblkid is where
  the issue is since this commands returns all of my other block devices
  except for /dev/sdb.

  sudo blkid|grep sdb

  
  It will mount using hard coded device path

  sudo mount /dev/sdb cf1657839355
  df -h /dev/sdb
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb 13T  3.5M   13T   1% /cf1657839355

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


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

[Touch-packages] [Bug 1981769] [NEW] blkid fails to find btrfs zoned filesystem label or uuid

2022-07-14 Thread Joshua McClintock

Public bug reported:

System Info:

lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04


1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem

sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
btrfs-progs v5.16.2
See http://btrfs.wiki.kernel.org for more information.

Resetting device zones /dev/sdb (52156 zones) ...
NOTE: several default settings have changed in version 5.15, please make sure
  this does not affect your deployments:
  - DUP for metadata (-m dup)
  - enabled no-holes (-O no-holes)
  - enabled free-space-tree (-R free-space-tree)

Label:  cf1657839355
UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
Node size:  16384
Sector size:4096
Filesystem size:12.73TiB
Block group profiles:
  Data: single  256.00MiB
  Metadata: single  256.00MiB
  System:   single  256.00MiB
SSD detected:   no
Zoned device:   yes
  Zone size:256.00MiB
Incompat features:  extref, skinny-metadata, no-holes, zoned
Runtime features:   free-space-tree
Checksum:   crc32c
Number of devices:  1
Devices:
   IDSIZE  PATH
112.73TiB  /dev/sdb

2. Try to use LABEL method to mount

sudo mount LABEL=cf1657839355 cf1657839355
mount: cf1657839355: can't find LABEL=cf1657839355.

Expected that LABEL would be found.  I suspect that libblkid is where
the issue is since this commands returns all of my other block devices
except for /dev/sdb.

sudo blkid|grep sdb


It will mount using hard coded device path

sudo mount /dev/sdb cf1657839355
df -h /dev/sdb
Filesystem  Size  Used Avail Use% Mounted on
/dev/sdb 13T  3.5M   13T   1% /cf1657839355

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  blkid fails to find btrfs zoned filesystem label or uuid

Status in util-linux package in Ubuntu:
  New

Bug description:
  System Info:

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem

  sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
  btrfs-progs v5.16.2
  See http://btrfs.wiki.kernel.org for more information.

  Resetting device zones /dev/sdb (52156 zones) ...
  NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)

  Label:  cf1657839355
  UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
  Node size:  16384
  Sector size:4096
  Filesystem size:12.73TiB
  Block group profiles:
Data: single  256.00MiB
Metadata: single  256.00MiB
System:   single  256.00MiB
  SSD detected:   no
  Zoned device:   yes
Zone size:256.00MiB
  Incompat features:  extref, skinny-metadata, no-holes, zoned
  Runtime features:   free-space-tree
  Checksum:   crc32c
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  112.73TiB  /dev/sdb

  2. Try to use LABEL method to mount

  sudo mount LABEL=cf1657839355 cf1657839355
  mount: cf1657839355: can't find LABEL=cf1657839355.

  Expected that LABEL would be found.  I suspect that libblkid is where
  the issue is since this commands returns all of my other block devices
  except for /dev/sdb.

  sudo blkid|grep sdb

  
  It will mount using hard coded device path

  sudo mount /dev/sdb cf1657839355
  df -h /dev/sdb
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb 13T  3.5M   13T   1% /cf1657839355

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


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

[Touch-packages] [Bug 1972115] Re: ubuntu-bug exits after dialog instead of sending data

2022-06-03 Thread Joshua Peisach

This even happened to me on Focal (latest update) when reporting the
gthumb CVE I found. I manually uploaded the crash dump, separated the
big apport file and put it up. Maybe a server issue

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

Title:
  ubuntu-bug  exits after dialog instead of sending data

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Jammy:
  Confirmed
Status in apport source package in Kinetic:
  Confirmed

Bug description:
  After a gnome-shell crash, I am trying to manually submit it by
  running 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This
  results in an apport-gtk prompt asking me "Send problem report to the
  developers?"  When I click 'send', the dialog disappears and ubuntu-
  bug exits, without uploading data to launchpad or interfacing with the
  browser.

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


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

[Touch-packages] [Bug 1955859] [NEW] ubuntu-core on jammy daily: apt-key has no access to /dev/null

2021-12-27 Thread Joshua Peisach

Public bug reported:

Ubuntu Jammy Core - Smoke test fails.

One of the issues that I believe may be the primary issue is that apt-
key has no access to /dev/null.

root@Joshua-PC:/# apt-get update
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:3 http://security.ubuntu.com/ubuntu jammy-security Release [89.8 kB]
Get:4 http://security.ubuntu.com/ubuntu jammy-security Release.gpg [819 B]
0% [Waiting for headers]/usr/bin/apt-key: 95: cannot create /dev/null: 
Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Ign:4 http://security.ubuntu.com/ubuntu jammy-security Release.gpg
Ign:5 http://archive.ubuntu.com/ubuntu jammy InRelease 
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates Release [89.8 kB] 
Get:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [90.7 kB] 
0% [Working]   13.8 kB/s 
0s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Err:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease   
  gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Get:8 http://archive.ubuntu.com/ubuntu jammy Release [269 kB]  
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates Release.gpg [819 B]   
0% [Working]   13.8 kB/s 
6s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates Release.gpg   
Get:10 http://archive.ubuntu.com/ubuntu jammy Release.gpg [819 B]  
0% [Working]   13.8 kB/s 
6s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Ign:10 http://archive.ubuntu.com/ubuntu jammy Release.gpg  
Reading package lists... Done  
W: GPG error: http://security.ubuntu.com/ubuntu jammy-security Release: gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security Release' is 
not signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' 
is not signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates Release: gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates Release' is 
not signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy Release: gpgv, gpgv2 or 
gpgv1 required for verification, but neither seems installed
E: The repository 'http://archive.ubuntu.com/ubuntu jammy Release' is not 
signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: apt 2.3.9
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 27 20:14:22 2021
InstallationDate: Installed on 2020-10-23 (430 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 SHELL=/bin/

[Touch-packages] [Bug 1926840] Re: Display/Graphics bug

2021-05-01 Thread Joshua Joseph Myers

I found out what the issue was. The problem is the new linux kernal
update Linux 5.8.0-50-generic.

After booting up with Linux 5.8.0-48-generic (the previous one), the
problem is resolved

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

Title:
  Display/Graphics bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu was perfect before updating it.

  I ran the command sudo apt update. After that, my computer graphics
  have become choppy. I have attached a screenshot of the problem.

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200
  v2/3rd Gen Core processor Graphics Controller (rev 09)

  Intel® HD Graphics 2500 (IVB GT1)
  GNOME version 3.36.8
  Windowing system X11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:20:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
  InstallationDate: Installed on 2021-02-09 (80 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. OptiPlex 7010
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=8e9a679a-a7d5-4d98-8a50-1e4ab130a8d4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0WR7PY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/21/2015:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA03:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.sku: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1926840] [NEW] Display/Graphics bug

2021-05-01 Thread Joshua Joseph Myers

Public bug reported:

Ubuntu was perfect before updating it.

I ran the command sudo apt update. After that, my computer graphics have
become choppy. I have attached a screenshot of the problem.

Description:Ubuntu 20.04.2 LTS
Release:20.04

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd
Gen Core processor Graphics Controller (rev 09)

Intel® HD Graphics 2500 (IVB GT1)
GNOME version 3.36.8
Windowing system X11

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  1 19:20:51 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
InstallationDate: Installed on 2021-02-09 (80 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. OptiPlex 7010
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=8e9a679a-a7d5-4d98-8a50-1e4ab130a8d4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 12/21/2015
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A21
dmi.board.name: 0WR7PY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/21/2015:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA03:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 7010
dmi.product.sku: OptiPlex 7010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
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.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "An image so you can see what the issue is"
   
https://bugs.launchpad.net/bugs/1926840/+attachment/5494056/+files/Untitled.png

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

Title:
  Display/Graphics bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu was perfect before updating it.

  I ran the command sudo apt update. After that, my computer graphics
  have become choppy. I have attached a screenshot of the problem.

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200
  v2/3rd Gen Core processor Graphics Controller (rev 09)

  Intel® HD Graphics 2500 (IVB GT1)
  GNOME version 3.36.8
  Windowing system X11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:20:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core

[Touch-packages] [Bug 1923517] [NEW] tracker-store crashed with signal 5

2021-04-12 Thread Joshua Peisach

Public bug reported:

This happens with g_listenv

jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> 
addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi
g_listenv
??:?

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker 2.3.6-2
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: X-Cinnamon
Date: Mon Apr 12 18:16:39 2021
ExecutablePath: /usr/libexec/tracker-store
InstallationDate: Installed on 2021-04-07 (5 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407)
ProcCmdline: /usr/libexec/tracker-store
RebootRequiredPkgs: libc6
Signal: 5
SourcePackage: tracker
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
Title: tracker-store crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
separator:

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


** Tags: amd64 apport-crash hirsute need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  tracker-store crashed with signal 5

Status in tracker package in Ubuntu:
  New

Bug description:
  This happens with g_listenv

  jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> 
  addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi
  g_listenv
  ??:?

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 12 18:16:39 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-04-07 (5 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: libc6
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
  Title: tracker-store crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

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

[Touch-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate

2021-04-02 Thread Jeffrey Joshua Rollin

** Tags added: hirsute

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

Title:
  LightDM can't use the user background on Mate

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

Bug description:
  Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04
  alpha 2).

  On Mate, the LightDM Gtk Greeter can't use the user background. It
  works fine on other DEs like Xfce.

  From what I understand, LightDM and/or the Gkt greeter (not sure which
  one handles the background) gets the background path from Gsettings,
  so I assume it can't find the one from Mate, which stores it in
  "org.mate.background picture-filename".

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

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

[Touch-packages] [Bug 1919255] [NEW] tracker-store crashed with signal 5

2021-03-15 Thread Joshua Peisach

Public bug reported:

This just happened...

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker 2.3.6-2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
Date: Mon Mar 15 17:47:12 2021
ExecutablePath: /usr/libexec/tracker-store
InstallationDate: Installed on 2021-02-28 (15 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
ProcCmdline: /usr/libexec/tracker-store
Signal: 5
SourcePackage: tracker
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
 () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
Title: tracker-store crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
separator:

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


** Tags: amd64 apport-crash hirsute need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  tracker-store crashed with signal 5

Status in tracker package in Ubuntu:
  New

Bug description:
  This just happened...

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Mon Mar 15 17:47:12 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (15 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   tracker_db_interface_sqlite_fts_delete_id () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
  Title: tracker-store crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

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

[Touch-packages] [Bug 1918186] [NEW] tracker-store crashed with signal 5 in g_printerr()

2021-03-08 Thread Joshua Peisach

Public bug reported:

Just happened, didn't really do anything.

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker 2.3.6-2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Mar  8 14:50:14 2021
ExecutablePath: /usr/libexec/tracker-store
InstallationDate: Installed on 2021-02-28 (8 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
ProcCmdline: /usr/libexec/tracker-store
RebootRequiredPkgs: evolution-data-server
Signal: 5
SourcePackage: tracker
StacktraceTop:
 g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libsqlite3.so.0
 ()
 ()
 ()
Title: tracker-store crashed with signal 5 in g_printerr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
separator:

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


** Tags: amd64 apport-crash hirsute need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  tracker-store crashed with signal 5 in g_printerr()

Status in tracker package in Ubuntu:
  New

Bug description:
  Just happened, didn't really do anything.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: tracker 2.3.6-2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar  8 14:50:14 2021
  ExecutablePath: /usr/libexec/tracker-store
  InstallationDate: Installed on 2021-02-28 (8 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
  ProcCmdline: /usr/libexec/tracker-store
  RebootRequiredPkgs: evolution-data-server
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libsqlite3.so.0
   ()
   ()
   ()
  Title: tracker-store crashed with signal 5 in g_printerr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  separator:

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

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

[Touch-packages] [Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking

2021-02-22 Thread Joshua Powers

Fixed in 20210222 daily images. Marking fix released.

** Changed in: systemd (Ubuntu)
   Status: New => 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/1911059

Title:
  gce: 247.1-4ubuntu1 causes loss of networking

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Summary
  ===
  On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.

  Expected Result
  ===
  Working network access

  Actual Result
  ===
  After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.

  Steps to Reproduce
  ===
  1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
  2. sudo apt update
  3. sudo apt install systemd
  4. ssh is lost

  The images, built with this version do not appear to be able to start
  networking.

  Logs
  ===
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915724] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978762] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978803] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042242] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042302] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105412] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105448] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168141] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168178] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00

  $ journalctl --no-pager -u systemd-net
  -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 
21:52:03 UTC. --
  Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service...
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change 
detected, ens4 has been renamed to eth0.
  Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change 
detected, eth0 has been renamed to ens4.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 
10.138.0.56/32 via 10.138.0.1
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes 
received from DHCP server: ignoring router option
  Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 
lease lost
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd.service: Succeeded.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: 
Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration 
completed
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: 
DHCPv4 address 10.138.0.56/32 via 10.138.0.1

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

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

[Touch-packages] [Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking

2021-01-11 Thread Joshua Powers

Greater output of journalctl:
https://pastebin.canonical.com/p/XJzPMHrSbx/

** Description changed:

  Summary
  ===
  On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.
  
  Expected Result
  ===
  Working network access
  
  Actual Result
  ===
  After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.
  
  Steps to Reproduce
  ===
  1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
  2. sudo apt update
- 3. sudo apt install systems
+ 3. sudo apt install systemd
  4. ssh is lost
  
  The images, built with this version do not appear to be able to start
  networking.
  
  Logs
  ===
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915724] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978762] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978803] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042242] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042302] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105412] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105448] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168141] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168178] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  
  $ journalctl --no-pager -u systemd-net
  -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 
21:52:03 UTC. --
  Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service...
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change 
detected, ens4 has been renamed to eth0.
  Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change 
detected, eth0 has been renamed to ens4.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 
10.138.0.56/32 via 10.138.0.1
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes 
received from DHCP server: ignoring router option
  Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 
lease lost
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd.service: Succeeded.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: 
Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration 
completed
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: 
DHCPv4 address 10.138.0.56/32 via 10.138.0.1

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

Title:
  gce: 247.1-4ubuntu1 causes loss of networking

Status in systemd package in Ubuntu:
  New

Bug description:
  Summary
  ===
  On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.

  Expected Result
  ===
  Working network access

  Actual Result
  ===
  After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.

  Steps to Reproduce
  ===
  1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
  2. sudo apt update
  3. sudo apt install systemd
  4. ssh is lost

  The images, built with this version do not appear to be able to start
  networking.

  Logs
  ===
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: 
martian source 10.138.0.56 from

[Touch-packages] [Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking

2021-01-11 Thread Joshua Powers

$ sudo journalctl --no-pager -u systemd-networkd-wait-online.service
-- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 
22:01:17 UTC. --
Jan 11 21:30:35 ubuntu systemd[1]: Starting Wait for Network to be Configured...
Jan 11 21:30:37 ubuntu systemd-networkd-wait-online[416]: managing: ens4
Jan 11 21:30:37 ubuntu systemd[1]: Finished Wait for Network to be Configured.
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd-wait-online.service: Succeeded.
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Wait for Network 
to be Configured.
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Wait for Network 
to be Configured...
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Wait for Network 
to be Configured...
Jan 11 21:39:27 powersj-hirsuite-20210107 systemd-networkd-wait-online[2451]: 
Event loop failed: Connection timed out
Jan 11 21:39:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd-wait-online.service: Main process exited, code=exited, 
status=1/FAILURE
Jan 11 21:39:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Jan 11 21:39:27 powersj-hirsuite-20210107 systemd[1]: Failed to start Wait for 
Network to be Configured.

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

Title:
  gce: 247.1-4ubuntu1 causes loss of networking

Status in systemd package in Ubuntu:
  New

Bug description:
  Summary
  ===
  On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.

  Expected Result
  ===
  Working network access

  Actual Result
  ===
  After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.

  Steps to Reproduce
  ===
  1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
  2. sudo apt update
  3. sudo apt install systems
  4. ssh is lost

  The images, built with this version do not appear to be able to start
  networking.

  Logs
  ===
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915724] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978762] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978803] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042242] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042302] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105412] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105448] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168141] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168178] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00

  $ journalctl --no-pager -u systemd-net
  -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 
21:52:03 UTC. --
  Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service...
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change 
detected, ens4 has been renamed to eth0.
  Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change 
detected, eth0 has been renamed to ens4.
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 
10.138.0.56/32 via 10.138.0.1
  Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes 
received from DHCP server: ignoring router option
  Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 
lease lost
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network 
Service...
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: 
systemd-networkd.service: Succeeded.
  Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service.
  Jan 11 21:37:27

[Touch-packages] [Bug 1911059] [NEW] gce: 247.1-4ubuntu1 causes loss of networking

2021-01-11 Thread Joshua Powers

Public bug reported:

Summary
===
On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.

Expected Result
===
Working network access

Actual Result
===
After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.

Steps to Reproduce
===
1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
2. sudo apt update
3. sudo apt install systems
4. ssh is lost

The images, built with this version do not appear to be able to start
networking.

Logs
===
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: martian 
source 10.138.0.56 from 169.254.169.254, on dev ens4
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915724] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978762] IPv4: martian 
source 10.138.0.56 from 169.254.169.254, on dev ens4
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.978803] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042242] IPv4: martian 
source 10.138.0.56 from 169.254.169.254, on dev ens4
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.042302] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105412] IPv4: martian 
source 10.138.0.56 from 169.254.169.254, on dev ens4
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.105448] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168141] IPv4: martian 
source 10.138.0.56 from 169.254.169.254, on dev ens4
Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  484.168178] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00

$ journalctl --no-pager -u systemd-net
-- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 
21:52:03 UTC. --
Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service...
Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed
Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change 
detected, ens4 has been renamed to eth0.
Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service.
Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change 
detected, eth0 has been renamed to ens4.
Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled
Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP
Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier
Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 
10.138.0.56/32 via 10.138.0.1
Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes 
received from DHCP server: ignoring router option
Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 
lease lost
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network 
Service...
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd.service: 
Succeeded.
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service.
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network 
Service...
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: Gained 
IPv6LL
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration 
completed
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service.
Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: DHCPv4 
address 10.138.0.56/32 via 10.138.0.1

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

** Summary changed:

- gce: 247.1-4ubuntu1 causes loose of networking
+ gce: 247.1-4ubuntu1 causes loss of networking

** Description changed:

  Summary
  ===
- On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to lose network access.
+ On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud 
instance to loose network access.
  
  Expected Result
  ===
  Working network access
  
  Actual Result
  ===
  After upgrade, network access is lost and serial console is filled with 
messages about IPv4 martian source and ll header, see below.
  
  Steps to Reproduce
  ===
  1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image
  2. sudo apt update
  3. sudo apt install systems
  4. ssh is lost
  
  The images, built with this version do not appear to be able to start
  networking.
  
  Logs
  ===
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915720] IPv4: 
martian source 10.138.0.56 from 169.254.169.254, on dev ens4
  Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [  483.915724] ll header: 
: 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00
  Jan 11 21:38:32

Re: [Touch-packages] [Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

2020-11-05 Thread Joshua Ivan Miranda Alfonso

This iso won't install.

On Tue, Nov 3, 2020 at 8:35 PM Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:

> Please run these commands:
>
>   ls -l /dev/dri/* > dri.txt
>   glxinfo > glx.txt
>
> and attach the resulting text files here.
>
> ** Changed in: mesa (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: xf86-video-armsoc (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902652
>
> Title:
>   [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
>
> Status in mesa package in Ubuntu:
>   Incomplete
> Status in xf86-video-armsoc package in Ubuntu:
>   Incomplete
>
> Bug description:
>   3d rendering is very slow, also when surfing the internet, webpages
>   take a while to render. Internet access is not the problem.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   Uname: Linux 4.19.64+ aarch64
>   ApportVersion: 2.20.9-0ubuntu7.18
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: XFCE
>   Date: Tue Nov  3 05:42:00 2020
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>
>   Lspci:
>
>   ProcEnviron:
>LANGUAGE=en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+
> root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@
> noquiet splash vt.handoff=1
>   Renderer: Software
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   XorgConf:
>Section "Device"
> Identifier  "Allwinner sun4i DRM driver"
> Driver  "armsoc"
> Option  "DRI2"  "true"
>EndSection
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2~18.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions
>

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

Title:
  [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Status in mesa package in Ubuntu:
  Incomplete
Status in xf86-video-armsoc package in Ubuntu:
  Incomplete

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To

Re: [Touch-packages] [Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

2020-11-03 Thread Joshua Ivan Miranda Alfonso

there is no ubuntu 20 for my board.

On Tue, Nov 3, 2020 at 12:25 AM Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:

> ** Summary changed:
>
> - 3d rendering is very slow
> + [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902652
>
> Title:
>   [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   3d rendering is very slow, also when surfing the internet, webpages
>   take a while to render. Internet access is not the problem.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   Uname: Linux 4.19.64+ aarch64
>   ApportVersion: 2.20.9-0ubuntu7.18
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: XFCE
>   Date: Tue Nov  3 05:42:00 2020
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>
>   Lspci:
>
>   ProcEnviron:
>LANGUAGE=en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+
> root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@
> noquiet splash vt.handoff=1
>   Renderer: Software
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   XorgConf:
>Section "Device"
> Identifier  "Allwinner sun4i DRM driver"
> Driver  "armsoc"
> Option  "DRI2"  "true"
>EndSection
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2~18.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902652/+subscriptions
>

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

Title:
  [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Status in mesa package in Ubuntu:
  New
Status in xf86-video-armsoc package in Ubuntu:
  New

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1902652] [NEW] 3d rendering is very slow

2020-11-02 Thread Joshua Ivan Miranda Alfonso

Public bug reported:

3d rendering is very slow, also when surfing the internet, webpages take
a while to render. Internet access is not the problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.19.64+ aarch64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Nov  3 05:42:00 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 
Lspci:
 
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
 EndSection
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: apport-bug arm64 bionic performance 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/1902652

Title:
  3d rendering is very slow

Status in xorg package in Ubuntu:
  New

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-10-09 Thread Joshua Powers

** Changed in: cloud-images
   Status: New => Fix Released

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  Fix Released
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-progs source package in Bionic:
  Invalid
Status in glibc source package in Bionic:
  Invalid
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed
   * It should contain pthread, and libgcc_s libraries

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.

  [Other Info]

   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.

   * Original bug report

  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2020-10-07 Thread Rayden Joshua Britto

ibpam0g

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

** Changed in: aptdaemon (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2020-10-07 Thread Rayden Joshua Britto

ibpam0g

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1891716] Re: Networking broken after systemd update

# journalctl -u systemd-networkd
https://paste.ubuntu.com/p/9M3xwgwgMj/

# systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Fri 2020-08-14 20:59:46 UTC; 
19min ago
TriggeredBy: ● systemd-networkd.socket
   Docs: man:systemd-networkd.service(8)
   Main PID: 1107 (code=exited, status=1/FAILURE)

Aug 14 20:59:46 g systemd[1]: systemd-networkd.service: Scheduled restart job, 
restart counter is at 5.
Aug 14 20:59:46 g systemd[1]: Stopped Network Service.
Aug 14 20:59:46 g systemd[1]: systemd-networkd.service: Start request repeated 
too quickly.
Aug 14 20:59:46 g systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
Aug 14 20:59:46 g systemd[1]: Failed to start Network Service.

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

Title:
  Networking broken after systemd update

Status in systemd package in Ubuntu:
  New

Bug description:
  # Description:

  After this upgrade in groovy, networking stopped working:

  Start-Date: 2020-08-14  17:02:50
  Commandline: apt-get dist-upgrade --assume-yes
  Requested-By: ubuntu (1000)
  Install: motd-news-config:amd64 (11ubuntu11, automatic)
  Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), 
alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 
(4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), 
cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), 
libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 
(1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 
(1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 
4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), 
systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 
(1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), 
libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 
(0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 
0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), 
libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 
(11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2)
  End-Date: 2020-08-14  17:03:10

  # Reproduction steps:

  $ multipass launch --name groovy-update-test daily:groovy
  $ multipass connect groovy-update-test
  # connected to VM
  $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes
  # works fine
  $ sudo apt-get update
  Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  $ sudo systemctl list-units --failed
    UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● systemd-networkd.service loaded failed failed Network Service
  ● systemd-networkd.socket  loaded failed failed Network Service Netlink Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  2 loaded units listed.
  $ systemctl status systemd-networkd.service
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor

[Touch-packages] [Bug 1891716] Re: Networking broken after systemd update

** Attachment added: "journal short-precise"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401580/+files/journal.short

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

Title:
  Networking broken after systemd update

Status in systemd package in Ubuntu:
  New

Bug description:
  # Description:

  After this upgrade in groovy, networking stopped working:

  Start-Date: 2020-08-14  17:02:50
  Commandline: apt-get dist-upgrade --assume-yes
  Requested-By: ubuntu (1000)
  Install: motd-news-config:amd64 (11ubuntu11, automatic)
  Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), 
alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 
(4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), 
cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), 
libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 
(1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 
(1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 
4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), 
systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 
(1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), 
libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 
(0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 
0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), 
libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 
(11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2)
  End-Date: 2020-08-14  17:03:10

  # Reproduction steps:

  $ multipass launch --name groovy-update-test daily:groovy
  $ multipass connect groovy-update-test
  # connected to VM
  $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes
  # works fine
  $ sudo apt-get update
  Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  $ sudo systemctl list-units --failed
    UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● systemd-networkd.service loaded failed failed Network Service
  ● systemd-networkd.socket  loaded failed failed Network Service Netlink Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  2 loaded units listed.
  $ systemctl status systemd-networkd.service
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 
12min ago
  TriggeredBy: ● systemd-networkd.socket
 Docs: man:systemd-networkd.service(8)
 Main PID: 2745 (code=exited, status=1/FAILURE)

  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main 
process exited, code=exited, status=1/FAILURE
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: 
Failed with result 'exit-code'.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: 
Scheduled restart job, restart counter is at 5.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]:

[Touch-packages] [Bug 1891716] Re: Networking broken after systemd update

** Attachment added: "journal from lxd"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401579/+files/journal

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

Title:
  Networking broken after systemd update

Status in systemd package in Ubuntu:
  New

Bug description:
  # Description:

  After this upgrade in groovy, networking stopped working:

  Start-Date: 2020-08-14  17:02:50
  Commandline: apt-get dist-upgrade --assume-yes
  Requested-By: ubuntu (1000)
  Install: motd-news-config:amd64 (11ubuntu11, automatic)
  Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), 
alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 
(4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), 
cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), 
libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 
(1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 
(1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 
4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), 
systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 
(1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), 
libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 
(0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 
0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), 
libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 
(11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2)
  End-Date: 2020-08-14  17:03:10

  # Reproduction steps:

  $ multipass launch --name groovy-update-test daily:groovy
  $ multipass connect groovy-update-test
  # connected to VM
  $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes
  # works fine
  $ sudo apt-get update
  Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  $ sudo systemctl list-units --failed
    UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● systemd-networkd.service loaded failed failed Network Service
  ● systemd-networkd.socket  loaded failed failed Network Service Netlink Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  2 loaded units listed.
  $ systemctl status systemd-networkd.service
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 
12min ago
  TriggeredBy: ● systemd-networkd.socket
 Docs: man:systemd-networkd.service(8)
 Main PID: 2745 (code=exited, status=1/FAILURE)

  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main 
process exited, code=exited, status=1/FAILURE
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: 
Failed with result 'exit-code'.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: 
Scheduled restart job, restart counter is at 5.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: Stopped Network

[Touch-packages] [Bug 1891716] Re: Networking broken after systemd update

Here are my notes from using a Groovy LXD container:

Expected Results
---
$ resolvectl status | grep "DNS Server"
  Current DNS Server: 192.168.100.1
 DNS Servers: 192.168.100.1

Actual Results
---
$ resolvectl status
Global
   LLMNR setting: no
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no

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


Steps to reproduce
---
$ lxc launch ubuntu-daily:g g
$ lxc exec g bash
# cat /etc/cloud/build.info 
build_name: server
serial: 20200813
# sudo apt update -qq
# apt-cache policy systemd
systemd:
  Installed: 245.7-1ubuntu1
  Candidate: 246-2ubuntu1
  Version table:
 246-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
 *** 245.7-1ubuntu1 100
100 /var/lib/dpkg/status
# resolvectl status | grep "DNS Server"
  Current DNS Server: 192.168.100.1
 DNS Servers: 192.168.100.1
# sudo apt install --yes systemd
...
Job for systemd-networkd.service failed because the control process exited with 
error code.
See "systemctl status systemd-networkd.service" and "journalctl -xe" for 
details.
Removing obsolete conffile /etc/dhcp/dhclient-enter-hooks.d/resolved ...
...
# resolvectl status
Global
   LLMNR setting: no
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no

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

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

Title:
  Networking broken after systemd update

Status in systemd package in Ubuntu:
  New

Bug description:
  # Description:

  After this upgrade in groovy, networking stopped working:

  Start-Date: 2020-08-14  17:02:50
  Commandline: apt-get dist-upgrade --assume-yes
  Requested-By: ubuntu (1000)
  Install: motd-news-config:amd64 (11ubuntu11, automatic)
  Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), 
alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 
(4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), 
cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), 
libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 
(1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 
(1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 
4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), 
systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 
(1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), 
libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 
(0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 
0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), 
libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 
(11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2)
  End-Date: 2020-08-14  17:03:10

  # Reproduction steps:

  $ multipass launch --name groovy-update-test daily:groovy
  $ multipass connect groovy-update-test
  # connected to VM
  $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes
  # works fine
  $ sudo apt-get update
  Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch

[Touch-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB

2020-07-15 Thread Joshua Peisach

It looks like this was already changed more recently in 2019/2020 with
4.4 - 4.6

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

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

Title:
  Port from legacy Xlib to modern XCB

Status in Compiz:
  Triaged
Status in 9wm package in Ubuntu:
  New
Status in aewm package in Ubuntu:
  New
Status in aewm++ package in Ubuntu:
  New
Status in afterstep package in Ubuntu:
  New
Status in amiwm package in Ubuntu:
  Invalid
Status in blackbox package in Ubuntu:
  New
Status in cairo package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Triaged
Status in ctwm package in Ubuntu:
  New
Status in dwm package in Ubuntu:
  Opinion
Status in enlightenment package in Ubuntu:
  New
Status in fvwm package in Ubuntu:
  New
Status in fvwm1 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in icewm package in Ubuntu:
  New
Status in jwm package in Ubuntu:
  Invalid
Status in larswm package in Ubuntu:
  New
Status in lwm package in Ubuntu:
  New
Status in matchbox-window-manager package in Ubuntu:
  New
Status in metacity package in Ubuntu:
  Invalid
Status in miwm package in Ubuntu:
  New
Status in muffin package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  New
Status in pekwm package in Ubuntu:
  New
Status in ratpoison package in Ubuntu:
  New
Status in sapphire package in Ubuntu:
  New
Status in sawfish package in Ubuntu:
  New
Status in spectrwm package in Ubuntu:
  Fix Released
Status in tinywm package in Ubuntu:
  New
Status in tritium package in Ubuntu:
  New
Status in twm package in Ubuntu:
  New
Status in vtwm package in Ubuntu:
  New
Status in w9wm package in Ubuntu:
  New
Status in windowlab package in Ubuntu:
  New
Status in wm2 package in Ubuntu:
  New
Status in wmaker package in Ubuntu:
  Opinion
Status in xmonad package in Ubuntu:
  New

Bug description:
  Port/rewrite the window manager to use the modern XCB (X C Binding)
  library instead of the old legacy Xlib.

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

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

[Touch-packages] [Bug 1882484] Re: Firewall rule in before.rules for dhcp is wrong

2020-06-15 Thread Joshua Stark

Thanks Jamie,

Ah, cool, so that ufw config is when the install is a client.

I am having issues with the install as a DHCPv4 server.

I will revert the UFW changes I have made and add in a new
/etc/ufw/application.d/dhcpd config to allow the install to run a DHCPv4
server

Thanks
Josh


PS. isc-dhcp-server when setup, by default is using "raw" sockets and thus the 
ufw rules are bypassed

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

Title:
  Firewall rule in before.rules for dhcp is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  The file delivered - /usr/share/ufw/iptables/before.rules
  which is then copied to - /etc/ufw/before.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT

  
  Package version found in:
0.36-0ubuntu0.1

  
  Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

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

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

[Touch-packages] [Bug 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong

2020-06-15 Thread Joshua Stark

Thanks Jamie,

Ah, cool, so that ufw config is when the install is a client.

I am having issues with the install as a DHCPv6 server.

I will revert the UFW changes I have made and add in a new
/etc/ufw/application.d/dhcpd config to allow the install to run a DHCPv6
server

Thanks
Josh

PS. isc-dhcp-server6 when setup, by default is not using "raw" sockets
and thus the ufw rules are enforced

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  When running DHCPv6, clients are not able get IP address.
  The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped and the dst address needs to be removed, as 
it's a broadcast

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for
  --sport and --dport are swapped
  -d fe80::/10 needs to be removed

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j
  ACCEPT

  Package version found in:
    0.36-0ubuntu0.1

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

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

[Touch-packages] [Bug 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong

2020-06-13 Thread Joshua Stark

** Description changed:

  When running DHCPv6, clients are not able get IP address.
- The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped
+ The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped and the dst address needs to be removed, as 
it's a broadcast
  
  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules
  
  Delivered by Package:
  
  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT
  
  The ports for
  --sport and --dport are swapped
+ -d fe80::/10 needs to be removed
  
  Should be:
  
- -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10
- --dport 547 -j ACCEPT
+ -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j
+ ACCEPT
  
  Package version found in:
    0.36-0ubuntu0.1

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  New

Bug description:
  When running DHCPv6, clients are not able get IP address.
  The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped and the dst address needs to be removed, as 
it's a broadcast

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for
  --sport and --dport are swapped
  -d fe80::/10 needs to be removed

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j
  ACCEPT

  Package version found in:
    0.36-0ubuntu0.1

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

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

[Touch-packages] [Bug 1882484] [NEW] Firewall rule in before.rules for dhcp is wrong

2020-06-07 Thread Joshua Stark

Public bug reported:

The file delivered - /usr/share/ufw/iptables/before.rules
which is then copied to - /etc/ufw/before.rules

Delivered by Package:

# allow dhcp client to work
-A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

The ports for
--sport and --dport are swapped

Should be:

-A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT


Package version found in:
  0.36-0ubuntu0.1


Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

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

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

Title:
  Firewall rule in before.rules for dhcp is wrong

Status in ufw package in Ubuntu:
  New

Bug description:
  The file delivered - /usr/share/ufw/iptables/before.rules
  which is then copied to - /etc/ufw/before.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT

  
  Package version found in:
0.36-0ubuntu0.1

  
  Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

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

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

[Touch-packages] [Bug 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong

2020-06-05 Thread Joshua Stark

** Description changed:

- Firewall rule in ip6table is incorrect, the ports need to be swapped
+ When running DHCPv6, clients are not able get IP address.
+ The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped
  
  The file delivered - /usr/share/ufw/iptables/before6.rules
- which is then copied to - /etc/ufw/before6.rules  
+ which is then copied to - /etc/ufw/before6.rules
  
  Delivered by Package:
  
  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT
  
- The ports for 
+ The ports for
  --sport and --dport are swapped
  
  Should be:
  
  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10
  --dport 547 -j ACCEPT
  
  Package version found in:
-   0.36-0ubuntu0.1
+   0.36-0ubuntu0.1

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  New

Bug description:
  When running DHCPv6, clients are not able get IP address.
  The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10
  --dport 547 -j ACCEPT

  Package version found in:
    0.36-0ubuntu0.1

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

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

[Touch-packages] [Bug 1882317] [NEW] Dual Stack DHCP clobber each other when using /run/dhcp-server/ for pid files

2020-06-05 Thread Joshua Stark

Public bug reported:

When installing dual stack IPv4 and IPv6 DHCP I found that DHCPv4 and
DHCPv6 clobber each others /run/dhcp-server path when you stop or
restart one of the daemons

I found that the config in the systemd unit has the /run path set to the
same location for both DHCPv4 and DHCPv6

In /lib/systemd/system/isc-dhcp-server.service the offending line that 
conflicts is:
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf 
$CONFIG_FILE $INTERFACES'

In /lib/systemd/system/isc-dhcp-server6.service the offending line that 
conflicts is:
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf 
$CONFIG_FILE $INTERFACES'

This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the
path /run/dhcp-server and removed the pid file for the alternate
process.

I have found a possible fix is to give DHCPv6 it's own /run path, thus I
suggest:

1) update DHCPv6 to use /run/dhcp-server6/

Update /lib/systemd/system/isc-dhcp-server6.service to use /run/dhcp-server6/
ie.
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server6/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'

Now we need to give dhcp access to this path in Apparmor:

2) Update /etc/apparmor.d/usr.sbin.dhcpd and add an additional line

38d39
  /var/lib/dhcp/dhcpd{,6}.leases* lrw,
  /var/log/ r,
  /var/log/** rw,
  /{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,
+  /{,var/}run/{,dhcp-server6/}dhcpd{,6}.pid rw,

Found in package version:
  4.4.1-2ubuntu5

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When installing dual stack IPv4 and IPv6 DHCP I found that DHCPv4 and
  DHCPv6 clobber each others /run/dhcp-server path when you stop or
  restart one of the daemons
  
  I found that the config in the systemd unit has the /run path set to the
  same location for both DHCPv4 and DHCPv6
  
- 
  In /lib/systemd/system/isc-dhcp-server.service the offending line that 
conflicts is:
-   exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'
- 
+   exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'
  
  In /lib/systemd/system/isc-dhcp-server6.service the offending line that 
conflicts is:
-   exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'
+   exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'
  
- 
- This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the path 
/run/dhcp-server and removed the pid file for the alternate process.
+ This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the
+ path /run/dhcp-server and removed the pid file for the alternate
+ process.
  
  I have found a possible fix is to give DHCPv6 it's own /run path, thus I
  suggest:
  
  1) update DHCPv6 to use /run/dhcp-server6/
  
  Update /lib/systemd/system/isc-dhcp-server6.service to use /run/dhcp-server6/
  ie.
-   exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server6/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'
+   exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server6/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'
  
  Now we need to give dhcp access to this path in Apparmor:
  
  2) Update /etc/apparmor.d/usr.sbin.dhcpd and add an additional line
  
  38d39
-   /var/lib/dhcp/dhcpd{,6}.leases* lrw,
-   /var/log/ r,
-   /var/log/** rw,
-   /{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,
+   /var/lib/dhcp/dhcpd{,6}.leases* lrw,
+   /var/log/ r,
+   /var/log/** rw,
+   /{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,
  +  /{,var/}run/{,dhcp-server6/}dhcpd{,6}.pid rw,
+ 
+ Found in package version:
+   4.4.1-2ubuntu5

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

Title:
  Dual Stack DHCP clobber each other when using /run/dhcp-server/ for
  pid files

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  When installing dual stack IPv4 and IPv6 DHCP I found that DHCPv4 and
  DHCPv6 clobber each others /run/dhcp-server path when you stop or
  restart one of the daemons

  I found that the config in the systemd unit has the /run path set to
  the same location for both DHCPv4 and DHCPv6

  In /lib/systemd/system/isc-dhcp-server.service the offending line that 
conflicts is:
    exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  In /lib/systemd/system/isc-dhcp-server6.service the offending line that 
conflicts is:
    exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'

  This means if you stop/restart DHCPv4 or DHCPv6, then it cleans up the
  path /run/dhcp-server and removed the pid file for the alternate
  process.

  I have found a possible fix is to give DHCPv6 it's own

[Touch-packages] [Bug 1882314] [NEW] Firewall rule in before6.rules for dhcp6 is wrong

2020-06-05 Thread Joshua Stark

Public bug reported:

Firewall rule in ip6table is incorrect, the ports need to be swapped

The file delivered - /usr/share/ufw/iptables/before6.rules
which is then copied to - /etc/ufw/before6.rules  

Delivered by Package:

# allow dhcp client to work
-A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

The ports for 
--sport and --dport are swapped

Should be:

-A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10
--dport 547 -j ACCEPT

Package version found in:
  0.36-0ubuntu0.1

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

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  New

Bug description:
  Firewall rule in ip6table is incorrect, the ports need to be swapped

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules  

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for 
  --sport and --dport are swapped

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 -d fe80::/10
  --dport 547 -j ACCEPT

  Package version found in:
0.36-0ubuntu0.1

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

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

[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2020-05-17 Thread Joshua Peisach

I would say there is probably a missing dependency-/etc/securetty
doesn't exist in Ubuntu and looks like it could be a typo.

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in pam package in Debian:
  New

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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

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

[Touch-packages] [Bug 1877856] [NEW] Display garbled after resume from suspect

2020-05-10 Thread Joshua Colson

Public bug reported:

I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my
laptop, the display is garbled blocks of random colors. It changes
frequently to other random colors. Power cycling the laptop clears the
issue, but only until it is suspended again.

The VT3 console shows:

nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 10 05:53:41 2020
DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
MachineType: Dell Inc. Latitude E6410
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0K42JR
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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: Sat May 19 22:08:24 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug focal 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/1877856

Title:
  Display garbled after resume from suspect

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my
  laptop, the display is garbled blocks of random colors. It changes
  frequently to other random colors. Power cycling the laptop clears the
  issue, but only until it is suspended again.

  The VT3 console shows:

  nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 05:53:41 2020
  DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
  MachineType: Dell Inc. Latitude E6410
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0K42JR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

[Touch-packages] [Bug 1870856] [NEW] Changing Icons does not automatically change on desktop

2020-04-04 Thread Joshua Peisach

Public bug reported:

Ubuntu Desktop:

Please note first that I had cinnamon-remix installed-I was bored so I
installed Ubuntu and Ubuntu Budgie desktops, along with gnome-tweaks and
gnome-shell.

I was changing the icons using GNOME Tweak Tool. In nautilus, the
changes automatically would apply. However, for the desktop, the changes
would NOT automatically apply. I had to re-login to see the changes.

If possible, I hope you guys can install a fresh Ubuntu and confirm
this. Theme used was Kimmo-Dark from Ubuntu Cinnamon, and I found this
issue for pretty much all the themes.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop 1.447
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 20:39:23 2020
InstallationDate: Installed on 2020-04-04 (0 days ago)
InstallationMedia: cinnamon-remix 20.04 "focal" - all amd64 (20200401)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Changing Icons does not automatically change on desktop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop:

  Please note first that I had cinnamon-remix installed-I was bored so I
  installed Ubuntu and Ubuntu Budgie desktops, along with gnome-tweaks
  and gnome-shell.

  I was changing the icons using GNOME Tweak Tool. In nautilus, the
  changes automatically would apply. However, for the desktop, the
  changes would NOT automatically apply. I had to re-login to see the
  changes.

  If possible, I hope you guys can install a fresh Ubuntu and confirm
  this. Theme used was Kimmo-Dark from Ubuntu Cinnamon, and I found this
  issue for pretty much all the themes.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.447
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 20:39:23 2020
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: cinnamon-remix 20.04 "focal" - all amd64 (20200401)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

2020-02-25 Thread Joshua Powers

@smoser

a looks merged

b has not had any changes since 2018 and looks up-to-date in Focal. What
am I missing?

c I see a devel branch, is it assumed that it uses a packaging structure
similar to cloud-init or can someone just grab and upload master?

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  Fix Committed
Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in cloud-utils package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

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

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

[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

2020-02-21 Thread Joshua Powers

After providing more background, the Trusty package needs to be uploaded
to the security pockets to ensure our Ubuntu Pro users are able to get
this update. This is essential to Pro users getting updates from the new
esm-infra pockets.

** Changed in: unattended-upgrades (Ubuntu Trusty)
   Status: Won't Fix => In Progress

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  In Progress
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
   * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.

  [Test Case]

   * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
   * 2) Trusty ESM

  [Regression Potential]

   * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
   * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.

  [Other Info]
   
  Previous description:

  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    "${distro_id}ESM:${distro_codename}-infra-security";
    "${distro_id}ESMApps:${distro_codename}-apps-security";
  };

  === Confirmed proper origin on an attached Trusty instance with ESM-
  infra enabled:

   500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
   release 
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main

  === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on 
an AWS Ubuntu PRO instance:
   500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64

   500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64

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

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

[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

2020-02-19 Thread Joshua Powers

** Tags removed: verification-failed-eoan
** Tags added: verification-needed-eoan

** Tags removed: verification-dibe-xenial
** Tags added: verification-done-xenial

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
   * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.

  [Test Case]

   * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
   * 2) Trusty ESM

  [Regression Potential]

   * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
   * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.

  [Other Info]
   
  Previous description:

  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    "${distro_id}ESM:${distro_codename}-infra-security";
    "${distro_id}ESMApps:${distro_codename}-apps-security";
  };

  === Confirmed proper origin on an attached Trusty instance with ESM-
  infra enabled:

   500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
   release 
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main

  === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on 
an AWS Ubuntu PRO instance:
   500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64

   500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64

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

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

[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

2020-02-19 Thread Joshua Powers

We will not drop the Eoan task as the SRU needs to go back to all
supported versions of the package, whether or not the UA components are
available in that release.

The test for Eoan then is to verify that nothing regressed. Please re-
test that unattended-upgrades continues to function with no new error
messages on Eoan.

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
   * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.

  [Test Case]

   * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
   * 2) Trusty ESM

  [Regression Potential]

   * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
   * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.

  [Other Info]
   
  Previous description:

  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    "${distro_id}ESM:${distro_codename}-infra-security";
    "${distro_id}ESMApps:${distro_codename}-apps-security";
  };

  === Confirmed proper origin on an attached Trusty instance with ESM-
  infra enabled:

   500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
   release 
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main

  === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on 
an AWS Ubuntu PRO instance:
   500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64

   500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2020-02-07 Thread Joshua Diamant

I am having this issue using IMSM / VROC 6.2 on Ubuntu 18.04 LTS, Kernel
5.3.0-28, mdadm - v4.1-rc1 - 2018-03-22.

I am running a bcache cache device on one of the RAID 1 IMSM (VROC)
arrays. At the very minimum, every reboot the device needs to resync
(not shutting down clean).

What other information is required to help us debug this issue?

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio,

[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

2020-01-22 Thread Joshua Powers

** Description changed:

+ [Impact]
+ 
+  * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
+  * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.
+ 
+ [Test Case]
+ 
+  * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
+  * 2) Trusty ESM
+ 
+ [Regression Potential]
+ 
+  * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
+  * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.
+ 
+ [Other Info]
+  
+ Previous description:
+ 
  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.
  
  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }
  
  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can be
  dropped or replaced.
  
  See RT #C122697 and #C121067 for the pocket/suite renames related to ESM
  
  What is needed after the ESM apt pocket/suite renames:
  
  Support for unattended upgrades for ESM for Infrastructure customers:
  
  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    "${distro_id}ESM:${distro_codename}-infra-security";
    "${distro_id}ESMApps:${distro_codename}-apps-security";
  };
  
  === Confirmed proper origin on an attached Trusty instance with ESM-
  infra enabled:
  
   500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
   release 
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
  
  === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on 
an AWS Ubuntu PRO instance:
   500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
  
   500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Bionic:
  New

Bug description:
  [Impact]

   * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
   * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.

  [Test Case]

   * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
   * 2) Trusty ESM

  [Regression Potential]

   * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
   * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.

  [Other Info]
   
  Previous description:

  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from

[Touch-packages] [Bug 1853956] Re: 34 wireguard peers result in invalid peer configuration

2019-12-05 Thread Joshua Sjoding

It turns out the fix for this issue was backported to systemd v240:

https://github.com/systemd/systemd-stable/pull/37

I performed a release upgrade on one of our affected servers, bringing
it up from ubuntu 18.04 to ubuntu 19.04 (which uses systemd v240), and I
can confirm that the peers are being configured correctly now.

So this issue affects ubuntu 18.04 LTS but not any later supported
releases. 18.10 was also affected but it's EOL.

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

Title:
  34 wireguard peers result in invalid peer configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu server 18.04.3 LTS
  systemd 237-3ubuntu10.31
  wireguard 0.0.20191012-wg1~bionic from PPA.

  We're using systemd-networkd to configure wireguard via
  wireguard.netdev and wireguard.network files in /etc/systemd/network/.
  All endpoints have IPv4 addresses.

  When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev
  file some peers are configured incorrectly. The affected peers seem to
  be related to the total number of peers (counting from 0 here):

  33 peers: No issue
  34 peers: Peer 1 and 2 fail
  35 peers: Peer 2 and 3 fail
  36 peers: Peer 3 and 4 fail
  37 peers: No issue

  In all cases peer 0 is functional. For an affected pair of peers A and
  B, peer A ends up with the allowed IP address range of peer B. Peer B
  ends up with no allowed IP addresses. This can be seen in the output
  of wg. The connections to both peers fail because of incorrect address
  range assignments.

  We first encountered this issue in a production environment when we
  moved from 33 to 34 unique peers on each server. The issue was
  reproduced on 3 different physical servers with similar configuration
  by adding and removing peer 34.

  The [WireGuardPeer] entries do not need to be unique to reproduce the
  issue. In my testing I used 6 distinct peers and then used 28 or more
  identical copies of a 7th peer. The results were the same.

  In January 2019 a bug was reported that was also related to the number of 
wireguard peers, but the description seems sufficiently different from our case 
that I felt I should file a distinct bug report. Here's a link to that report 
in case I'm wrong about that:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

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

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

[Touch-packages] [Bug 1811149] Re: 23 wireguard peers hang systemd-networkd

As near as I can tell the fix for this was never backported from systemd
v241 to bionic. I recently filed a related a bug report here:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853956

My symptoms are a little different (misconfiguration instead of an
infinite loop), but I have a strong suspicion that the underlying cause
is the same.

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

Title:
  23 wireguard peers hang systemd-networkd

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 18.04.1 LTS with systemd=237-3ubuntu10.9.
  Linux kernel version is 4.15.0-32-generic #35-Ubuntu SMP.
  wireguard=0.0.20181218-wg1~bionic from PPA.

  I have a Wireguard-based VPN server that has several peers. As soon as
  number of peers is 22 or lower, everything works okay. As soon as I
  add the 23rd peer, restart of `systemd-networkd` service fails with
  timeout while systemd-networkd hogs CPU.

  Moreover, if I reboot the box while wireguard configuration is
  "broken", systemd-networkd fails to apply network settings on boot and
  the box is no longer accessible over the network.

  Configuration is structured in a following way (keys are fake):

  ==> wg0.netdev
  [NetDev]
  Name=wg0
  Kind=wireguard
  Description=Wireguard VPN server
  [WireGuard]
  ListenPort=4500
  PrivateKey=kNl7tkhCM1Crj8RhUIn8xvwcg+UoOkw26kQjQEtZk1k=
  [WireGuardPeer]
  PublicKey=AfM1AN4IIUe5AVypFg2pcNrQmqOtZQIJLgusbkDYXkI=
  AllowedIPs=fd6f:b446:a2ca:0400:cb6f:b446:a2ca:bd0b/128
  AllowedIPs=fd6f:b446:a2ca:cb6f:b446:a2ca::/96
  # and 22 more [WireGuardPeer] like that

  ==> wg0.network
  Name=wg0
  [Network]
  Address=fd6f:b446:a2ca:0400::1/64
  [Route]
  Destination=fd6f:b446:a2ca:cb6f:b446:a2ca::/96
  # and 22 more [Route] sections like that

  syslog logs are attached both for "good" and "bad" cases, sample of
  strace logs is also attached for "bad" case.

  I'm filling the issue here as the aforementioned systemd version is
  already out of scope of upstream bug tracker per
  https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md
  #filing-issues

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

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

[Touch-packages] [Bug 1853956] Re: 34 wireguard peers result in invalid peer configuration

I think the underlying problem is improper fragmentation of netlink
messages sent to the WireGuard device by systemd v237 in the
set_wireguard_interface function:

https://github.com/systemd/systemd/blob/v237/src/network/netdev/wireguard.c#L107

Appending netlink message data can fail if the message size limit has
been exceeded. This can happen if there are too many peers or ip masks
in the netdev file, and the v237 code doesn't seem to handle this
properly. It's supposed to split the data up into message fragments, but
instead it can end up writing incoherent data to the netlink socket or
end up in an infinite loop.

This issue was fixed in systemd v241 by reworking the code over a few
commits:

https://github.com/systemd/systemd/pull/11418
https://github.com/systemd/systemd/pull/11580 (this fixed issues with the first
PR)

I found some comments (now resolved) on one of the commits illuminating:

https://github.com/systemd/systemd/pull/11418/commits/e1f717d4a02e15ae11a191dd4962b2f4d117678d

Mic92 on 2019-01-15:

> The idea is that netlink's messages are limited in size. If an
interface has many peers, addresses or ip masks then the configuration
might not fit into one message and has to be split across different
messages.

yuwata on 2019-01-15:

> Yeah. I guess there was some bug in the cancellation logic, and it
causes infinite loop with the magic number 23.

The infinite loop with 23 peers yuwata mentions is a reference to Leonid's bug
report from January:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

I expect that backporting these fixes from v241 to bionic's systemd v237
branch would resolve both my issue and the issue reported by Leonid.

I realize this is a non-trivial change and there's a regression risk.

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

Title:
34 wireguard peers result in invalid peer configuration

Status in systemd package in Ubuntu:
New

Bug description:
ubuntu server 18.04.3 LTS
systemd 237-3ubuntu10.31
wireguard 0.0.20191012-wg1~bionic from PPA.

We're using systemd-networkd to configure wireguard via
wireguard.netdev and wireguard.network files in /etc/systemd/network/.
All endpoints have IPv4 addresses.

When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev
file some peers are configured incorrectly. The affected peers seem to
be related to the total number of peers (counting from 0 here):

33 peers: No issue
34 peers: Peer 1 and 2 fail
35 peers: Peer 2 and 3 fail
36 peers: Peer 3 and 4 fail
37 peers: No issue

In all cases peer 0 is functional. For an affected pair of peers A and
B, peer A ends up with the allowed IP address range of peer B. Peer B
ends up with no allowed IP addresses. This can be seen in the output
of wg. The connections to both peers fail because of incorrect address
range assignments.

We first encountered this issue in a production environment when we
moved from 33 to 34 unique peers on each server. The issue was
reproduced on 3 different physical servers with similar configuration
by adding and removing peer 34.

The [WireGuardPeer] entries do not need to be unique to reproduce the
issue. In my testing I used 6 distinct peers and then used 28 or more
identical copies of a 7th peer. The results were the same.

In January 2019 a bug was reported that was also related to the number of
wireguard peers, but the description seems sufficiently different from our case
that I felt I should file a distinct bug report. Here's a link to that report
in case I'm wrong about that:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

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

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

[Touch-packages] [Bug 1853956] Re: 34 wireguard peers result in invalid peer configuration

I now believe the dmesg complaint in my last comment to be a separate
issue. A fix for it was backported to systemd v238 in this commit:

https://github.com/systemd/systemd-
stable/commit/7db3fe08c5eb83584f3a3d356876b4acaa797585#diff-
f29d1bfc98e548dc0eb497c3d17cbefa

It was not backported to systemd v237:

https://github.com/systemd/systemd-
stable/commits/v237-stable/src/network/netdev/wireguard.c

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

Title:
  34 wireguard peers result in invalid peer configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu server 18.04.3 LTS
  systemd 237-3ubuntu10.31
  wireguard 0.0.20191012-wg1~bionic from PPA.

  We're using systemd-networkd to configure wireguard via
  wireguard.netdev and wireguard.network files in /etc/systemd/network/.
  All endpoints have IPv4 addresses.

  When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev
  file some peers are configured incorrectly. The affected peers seem to
  be related to the total number of peers (counting from 0 here):

  33 peers: No issue
  34 peers: Peer 1 and 2 fail
  35 peers: Peer 2 and 3 fail
  36 peers: Peer 3 and 4 fail
  37 peers: No issue

  In all cases peer 0 is functional. For an affected pair of peers A and
  B, peer A ends up with the allowed IP address range of peer B. Peer B
  ends up with no allowed IP addresses. This can be seen in the output
  of wg. The connections to both peers fail because of incorrect address
  range assignments.

  We first encountered this issue in a production environment when we
  moved from 33 to 34 unique peers on each server. The issue was
  reproduced on 3 different physical servers with similar configuration
  by adding and removing peer 34.

  The [WireGuardPeer] entries do not need to be unique to reproduce the
  issue. In my testing I used 6 distinct peers and then used 28 or more
  identical copies of a 7th peer. The results were the same.

  In January 2019 a bug was reported that was also related to the number of 
wireguard peers, but the description seems sufficiently different from our case 
that I felt I should file a distinct bug report. Here's a link to that report 
in case I'm wrong about that:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

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

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

[Touch-packages] [Bug 1853956] Re: 34 wireguard peers result in invalid peer configuration

On two systems with 33 peers I noticed that this shows up in dmesg after
a reboot:

netlink: 'systemd-network': attribute type 5 has an invalid length.

These lines also show up whenever I run `sudo systemctl restart systemd-
networkd` now. They didn't show up before the reboot.

This suggests that there may be issues I haven't noticed yet even with
fewer than 34 peers. In our production environment not all of our peers
are online all the time, so an issue affecting a few of them could go
unnoticed.

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

Title:
  34 wireguard peers result in invalid peer configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu server 18.04.3 LTS
  systemd 237-3ubuntu10.31
  wireguard 0.0.20191012-wg1~bionic from PPA.

  We're using systemd-networkd to configure wireguard via
  wireguard.netdev and wireguard.network files in /etc/systemd/network/.
  All endpoints have IPv4 addresses.

  When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev
  file some peers are configured incorrectly. The affected peers seem to
  be related to the total number of peers (counting from 0 here):

  33 peers: No issue
  34 peers: Peer 1 and 2 fail
  35 peers: Peer 2 and 3 fail
  36 peers: Peer 3 and 4 fail
  37 peers: No issue

  In all cases peer 0 is functional. For an affected pair of peers A and
  B, peer A ends up with the allowed IP address range of peer B. Peer B
  ends up with no allowed IP addresses. This can be seen in the output
  of wg. The connections to both peers fail because of incorrect address
  range assignments.

  We first encountered this issue in a production environment when we
  moved from 33 to 34 unique peers on each server. The issue was
  reproduced on 3 different physical servers with similar configuration
  by adding and removing peer 34.

  The [WireGuardPeer] entries do not need to be unique to reproduce the
  issue. In my testing I used 6 distinct peers and then used 28 or more
  identical copies of a 7th peer. The results were the same.

  In January 2019 a bug was reported that was also related to the number of 
wireguard peers, but the description seems sufficiently different from our case 
that I felt I should file a distinct bug report. Here's a link to that report 
in case I'm wrong about that:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

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

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

[Touch-packages] [Bug 1853956] [NEW] 34 wireguard peers result in invalid peer configuration

2019-11-25 Thread Joshua Sjoding

Public bug reported:

ubuntu server 18.04.3 LTS
systemd 237-3ubuntu10.31
wireguard 0.0.20191012-wg1~bionic from PPA.

We're using systemd-networkd to configure wireguard via wireguard.netdev
and wireguard.network files in /etc/systemd/network/. All endpoints have
IPv4 addresses.

When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev file
some peers are configured incorrectly. The affected peers seem to be
related to the total number of peers (counting from 0 here):

33 peers: No issue
34 peers: Peer 1 and 2 fail
35 peers: Peer 2 and 3 fail
36 peers: Peer 3 and 4 fail
37 peers: No issue

In all cases peer 0 is functional. For an affected pair of peers A and
B, peer A ends up with the allowed IP address range of peer B. Peer B
ends up with no allowed IP addresses. This can be seen in the output of
wg. The connections to both peers fail because of incorrect address
range assignments.

We first encountered this issue in a production environment when we
moved from 33 to 34 unique peers on each server. The issue was
reproduced on 3 different physical servers with similar configuration by
adding and removing peer 34.

The [WireGuardPeer] entries do not need to be unique to reproduce the
issue. In my testing I used 6 distinct peers and then used 28 or more
identical copies of a 7th peer. The results were the same.

In January 2019 a bug was reported that was also related to the number of 
wireguard peers, but the description seems sufficiently different from our case 
that I felt I should file a distinct bug report. Here's a link to that report 
in case I'm wrong about that:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

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


** Tags: networkd systemd-networkd wireguard

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

Title:
  34 wireguard peers result in invalid peer configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu server 18.04.3 LTS
  systemd 237-3ubuntu10.31
  wireguard 0.0.20191012-wg1~bionic from PPA.

  We're using systemd-networkd to configure wireguard via
  wireguard.netdev and wireguard.network files in /etc/systemd/network/.
  All endpoints have IPv4 addresses.

  When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev
  file some peers are configured incorrectly. The affected peers seem to
  be related to the total number of peers (counting from 0 here):

  33 peers: No issue
  34 peers: Peer 1 and 2 fail
  35 peers: Peer 2 and 3 fail
  36 peers: Peer 3 and 4 fail
  37 peers: No issue

  In all cases peer 0 is functional. For an affected pair of peers A and
  B, peer A ends up with the allowed IP address range of peer B. Peer B
  ends up with no allowed IP addresses. This can be seen in the output
  of wg. The connections to both peers fail because of incorrect address
  range assignments.

  We first encountered this issue in a production environment when we
  moved from 33 to 34 unique peers on each server. The issue was
  reproduced on 3 different physical servers with similar configuration
  by adding and removing peer 34.

  The [WireGuardPeer] entries do not need to be unique to reproduce the
  issue. In my testing I used 6 distinct peers and then used 28 or more
  identical copies of a 7th peer. The results were the same.

  In January 2019 a bug was reported that was also related to the number of 
wireguard peers, but the description seems sufficiently different from our case 
that I felt I should file a distinct bug report. Here's a link to that report 
in case I'm wrong about that:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

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

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

[Touch-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

2019-11-01 Thread Joshua Powers

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

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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

[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates

2019-10-31 Thread Joshua Powers

Will fix in a follow-up upload with a fix to:

https://git.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/tree
/apt-hook/hook.cc?h=ubuntu/trusty-proposed#n218

** Changed in: update-notifier (Ubuntu)
   Status: Incomplete => Invalid

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

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  apt list --upgradable shows no additional updates

Status in apt package in Ubuntu:
  Invalid
Status in ubuntu-advantage-tools package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Invalid

Bug description:
  Running `apt list --upgradable` does not show any additional packages
  to install.  Should it?

  
  root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  60 additional updates are available with UA Infrastructure ESM.
  To see these additional updates run: apt list --upgradable
  See https://ubuntu.com/advantage or run: sudo ua status
  root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable
  Listing... Done
  root@humble-mynah:/etc/apt/sources.list.d#

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

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

[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates

2019-10-28 Thread Joshua Powers

Hmm I was able to reproduce even having 1.0.1ubuntu2.24; adding apt as a
affects as well.

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

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

Title:
  apt list --upgradable shows no additional updates

Status in apt package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  Incomplete

Bug description:
  Running `apt list --upgradable` does not show any additional packages
  to install.  Should it?

  
  root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  60 additional updates are available with UA Infrastructure ESM.
  To see these additional updates run: apt list --upgradable
  See https://ubuntu.com/advantage or run: sudo ua status
  root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable
  Listing... Done
  root@humble-mynah:/etc/apt/sources.list.d#

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

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

[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates

2019-10-28 Thread Joshua Powers

This is how I am reproducing:

multipass launch trusty --name t1
multipass exec t1 bash
echo "deb http://archive.ubuntu.com/ubuntu trusty-proposed main" | tee -a 
/etc/apt/sources.list
sudo apt update -qq
sudo apt upgrade -y
sudo apt list --upgradable

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

Title:
  apt list --upgradable shows no additional updates

Status in apt package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  Incomplete

Bug description:
  Running `apt list --upgradable` does not show any additional packages
  to install.  Should it?

  
  root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  60 additional updates are available with UA Infrastructure ESM.
  To see these additional updates run: apt list --upgradable
  See https://ubuntu.com/advantage or run: sudo ua status
  root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable
  Listing... Done
  root@humble-mynah:/etc/apt/sources.list.d#

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

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

[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

2019-10-25 Thread Joshua Powers

** Changed in: cloud-init
   Status: Confirmed => Fix Released

** Changed in: cloud-init (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

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

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

[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

2019-10-14 Thread Joshua Powers

It should be removed from all types eventually, this was a distro wide
change no an ISO specific change.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  The file /etc/network/interfaces is missing after install guestOS with
  eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi.

  This issue cause a failure for VMware Guest OS Customization

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

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

[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

2019-10-10 Thread Joshua Powers

Ubuntu discontinued the use of /etc/network/interfaces a number of
releases ago and in 19.10 have removed ifupdown. Please see the
migrating to netplan document:

https://wiki.ubuntu.com/MigratingToNetplan

If you need to continue using /etc/network/interfaces then there are
ways to install ifupdown and disable netplan.

I am closing this as invalid.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  The file /etc/network/interfaces is missing after install guestOS with
  eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi.

  This issue cause a failure for VMware Guest OS Customization

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

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

[Touch-packages] [Bug 1841654] Re: Replace mawk with gawk in main

2019-08-28 Thread Joshua Powers

** Tags removed: server-next

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

Title:
  Replace mawk with gawk in main

Status in mawk package in Ubuntu:
  New

Bug description:
  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.

  == Reasons against keeping mawk ==

  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version
  1.3.3-17, the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names=mawk

  *part-time maintainer Thomas E. Dickey (https://invisible-
  island.net/mawk/) called officially out that Debian "neglected" mawk
  in 2014 ("As noted, mawk has been neglected by some packagers (see for
  example this http://bugs.debian.org/cgi-
  bin/pkgreport.cgi?package=mawk)". And Debian (and Ubuntu) still ship
  the same version five years later

  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
  NetBSD pkgsrc/lang, OpenCSW (Solaris). But even that version is from
  2014 and doesn't seem to be developed anymore:
  https://github.com/ThomasDickey/mawk-20140914/commits/master

  *A planned rewrite mawk2 was planned by original author Mike Brennan
  in 2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master

  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.

  *This year it is 10 years unmaintained and largely untouched. At the
  end of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.

  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest
  from being POSIX compliant, missing things like named character
  classes like [[:space:]] within its EREs.

  == Reasons for gawk as a replacement ==

  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.

  *It is actively maintained with the last version 5.01 shipping in
  June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).

  *It is mostly compliant with the POSIX standard.

  *Most other distributions ship it as the standard POSIX
  implementation, with a awk symlink. So it had security reviews already
  by Red Hat and others.

  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==

  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out
  of the door.

  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To
  start gawk in --traditional or --posix mode and disable the extensions
  at compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd

2019-06-11 Thread Joshua Powers

I am cleaning up zookeeper bugs and I believe that this will not be
fixed given the release it was reported on. Xenial and newer versions do
not appear to be affected by this bug. As such I am marking this
incomplete for zookeeper and allowing someone to provide reproduction
steps if it still is an issue.

Thanks!

** Changed in: zookeeper (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  circular dependency causes zookeeperd to not be running after
  installation of zookeeperd

Status in apt package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  New
Status in zookeeper package in Ubuntu:
  Incomplete

Bug description:
  In a fresh quantal cloud image (i used ubuntu-quantal-daily-
  amd64-server-20120531), 'apt-get install zookeeperd' does not result
  in a running zookeeperd.

  to reproduce:
   * launch fresh instance
   * sudo apt-get install --assume-yes zookeeperd
* status zookeeper

  Note, if you have previously installed zookeeper (not zookeeperd) then
  things will be fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: zookeeperd 3.3.5+dfsg1-2
  ProcVersionSignature: User Name 3.4.0-3.8-generic 3.4.0
  Uname: Linux 3.4.0-3-generic x86_64
  ApportVersion: 2.1.1-0ubuntu1
  Architecture: amd64
  Date: Fri Jun  1 13:44:36 2012
  Ec2AMI: ami-00ed
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zookeeper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS

2019-04-14 Thread Matthew Joshua

Thanks @pujanm. Your method worked for me. I'm really grateful. Here's
my e-mail, brainyc...@outlook.com.

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

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

Title:
  Hash Sum mismatch Ubuntu Server 18.04.1 LTS

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I'm getting weird Hashes mismatch error while trying to update Ubuntu server 
18.04.1 LTS server. The error I'm receiving is as follows.

  $ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 
kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources 
[2,676 B]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[277 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[105 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [157 kB]
  Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    Hash Sum mismatch
    Hashes of expected file:
     - Filesize:157408 [weak]
     - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
     - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
     - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
    Hashes of received file:
     - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
     - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
     - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
     - Filesize:157408 [weak]
    Last modification reported: Tue, 07 Aug 2018 07:15:09 +
    Release file created at: Tue, 07 Aug 2018 07:15:03 +
  Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [71.0 kB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [3,772 B]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse 
Translation-en [2,376 B]
  Err:14 http://download.webmin.com/download/repository sarge InRelease
    Could not connect to download.webmin.com:80 (108.60.199.109), connection 
timed out
  Fetched 329 kB in 30s (10.9 kB/s)
  Reading package lists... Done
  W: Failed to fetch 
http://download.webmin.com/download/repository/dists/sarge/InRelease  Could not 
connect to download.webmin.com:80 (108.60.199.109), connection timed out
  E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:157408 [weak]
  - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
  - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
     Hashes of received file:
  - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
  - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
  - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
  - Filesize:157408 [weak]
     Last modification reported: Tue, 07 Aug 2018 07:15:09 +
     Release file created at: Tue, 07 Aug 2018 07:15:03 +
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I have tried solution provided in search  as "removing all files in
  /var/lib/apt/lists and update again" but it doesn't work. Don't know
  how to resolve it.

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

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

[Touch-packages] [Bug 1817627] Re: systemd-analyze verify reports failure

2019-02-26 Thread Joshua Powers

Marking the Ubuntu Manpage Repository task invalid and adding the
systemd (Ubuntu) task.

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

** Changed in: ubuntu-manpage-repository
   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/1817627

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+subscriptions

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

[Touch-packages] [Bug 1773007] Re: sntp return code is not EXIT_FAILURE when hostname query is not successful

2018-11-27 Thread Joshua Powers

Marking incomplete due to lack of response. If you did submit an
upstream bug please let us know and link to it here. Thanks!

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

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

Title:
  sntp return code is not EXIT_FAILURE when hostname query is not
  successful

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  # sntp abc
  sntp 4.2.8p10@1.3728-o (1)
  kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or 
directory
  abc lookup error Temporary failure in name resolution

  echo $?
  0

  
  from the manpage for sntp:

  EXIT STATUS
   One of the following exit values will be returned:

   0  (EXIT_SUCCESS)
 Successful program execution.

   1  (EXIT_FAILURE)
 The operation failed or the command syntax was not valid.

   66  (EX_NOINPUT)
 A specified configuration file could not be loaded.

   70  (EX_SOFTWARE)
 libopts had an internal operational error.  Please report 
it to auto‐
 gen-us...@lists.sourceforge.net.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sntp 1:4.2.8p10+dfsg-5ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 19:53:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2018-05-23T19:24:22.724839

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

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

[Touch-packages] [Bug 1797578] [NEW] unable to open Ubuntu Software

2018-10-12 Thread Joshua Sabbagha

Public bug reported:

when i try to open Ubuntu Software it flashes on the launcher then the
icon looks like it didn't open.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Oct 12 16:41:02 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3616]
InstallationDate: Installed on 2018-01-21 (264 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO Lenovo H420
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: DPKT22A
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: LENOVO
dmi.board.version: 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:bvnLENOVO:bvrDPKT22A:bd11/08/2011:svnLENOVO:pnLenovoH420:pvrLenovo:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Lenovo H420
dmi.product.version: Lenovo
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Oct 12 15:05:52 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input  USB Keyboard   KEYBOARD, id 8
 input  USB Keyboard   KEYBOARD, id 9
 inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  unable to open Ubuntu Software

Status in xorg package in Ubuntu:
  New

Bug description:
  when i try to open Ubuntu Software it flashes on the launcher then the
  icon looks like it didn't open.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 12 16:41:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3616]
  InstallationDate: Installed on 2018-01-21 (264 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO Lenovo H420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date:

[Touch-packages] [Bug 1795764] [NEW] systemd: core: Fix edge case when processing /proc/self/mountinfo

2018-10-02 Thread Joshua R. Poulson

Public bug reported:

>From the PR:
Currently, if there are two /proc/self/mountinfo entries with the same
mount point path, the mount setup flags computed for the second of
these two entries will overwrite the mount setup flags computed for
the first of these two entries. This is the root cause of issue #7798.
This patch changes mount_setup_existing_unit to prevent the
just_mounted mount setup flag from being overwritten if it is set to
true. This will allow all mount units created from /proc/self/mountinfo
entries to be initialized properly.

One line fix in https://github.com/systemd/systemd/pull/7811/files

Referenced issue: https://github.com/systemd/systemd/issues/7798

Related kubernetes issue:
https://github.com/kubernetes/kubernetes/issues/57345

systemd v237 has this fix, but we'd like to have it fixed in 16.04.

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

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

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  From the PR:
  Currently, if there are two /proc/self/mountinfo entries with the same
  mount point path, the mount setup flags computed for the second of
  these two entries will overwrite the mount setup flags computed for
  the first of these two entries. This is the root cause of issue #7798.
  This patch changes mount_setup_existing_unit to prevent the
  just_mounted mount setup flag from being overwritten if it is set to
  true. This will allow all mount units created from /proc/self/mountinfo
  entries to be initialized properly.

  One line fix in https://github.com/systemd/systemd/pull/7811/files

  Referenced issue: https://github.com/systemd/systemd/issues/7798

  Related kubernetes issue:
  https://github.com/kubernetes/kubernetes/issues/57345

  systemd v237 has this fix, but we'd like to have it fixed in 16.04.

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-28 Thread Joshua Powers

@Anthony - should someone on the kernel team review your proposed
merge/change rather than the server team?

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Confirmed
Status in kmod source package in Bionic:
  Confirmed
Status in kmod source package in Cosmic:
  Confirmed

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

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

[Touch-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section

2018-08-06 Thread Joshua Powers

Hi! Thanks for taking the time to file a bug. I have re-assigned this to
network-manager as this isn't a bug with the vlan package, but with the
UI itself. It may need to be moved to yet another package, but this
should get the right people's attention.

Could you also let us know what version of Ubuntu you are using? (e.g.
`cat /etc/os-release`)

Thanks!

** Package changed: vlan (Ubuntu) => network-manager (Ubuntu)

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

Title:
  VLAN in GUI's network setting is under Bluetooth section

Status in network-manager package in Ubuntu:
  New

Bug description:
  I install vlan package and  setup VLAN successfully. But when I check
  the Network settings in GUI, the created VLAN interface is under
  Bluetooth section.

  For reference, here is the screen shot of the issue.

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

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

[Touch-packages] [Bug 1780548] Re: SSH server won't start, exit code 255

2018-07-09 Thread Joshua Powers

Per the comment above, please take a look at your sshd_cofig file and
verify it is valid. I am marking this incomplete until then.

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

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

Title:
  SSH server won't start, exit code 255

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I keep trying to set up external SSH access using openssh server on my
  18.04 system and it throws back this error

  sudo service ssh status
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2018-07-07 09:33:19 CDT; 
12min ago
Process: 3243 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)

  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Service hold-off time 
over, scheduling restart.
  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 5.
  Jul 07 09:33:19 warehouse systemd[1]: Stopped OpenBSD Secure Shell server.
  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Start request repeated too 
quickly.
  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Jul 07 09:33:19 warehouse systemd[1]: Failed to start OpenBSD Secure Shell 
server.

  I was in the process of uninstalling the openssh-server and ssh
  packages and was prompted to start a bug report.  If it's in error,
  just let me know.  My ssh config file is all default except for
  passwordauthentication = yes.  I've toggled that to default as well,
  and still get the same error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   openssh-server:amd64: Install
   ssh:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jul  7 09:48:11 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 1: Bad configuration option: \342\200\213\342\200\213
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed 
openssh-server package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1778799] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

2018-06-26 Thread Joshua

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

Public bug reported:

update did not install. 
a similar thing has happened with several apps  have tried to download and the 
OS wont install them for some reason.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 26 22:26:14 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-08 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

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


** Tags: amd64 apport-package bionic package-from-proposed

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

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

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

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

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

[Touch-packages] [Bug 1778800] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

2018-06-26 Thread Joshua

Public bug reported:

update did not install. 
a similar thing has happened with several apps  have tried to download and the 
OS wont install them for some reason.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 26 22:26:14 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-08 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

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


** Tags: amd64 apport-package bionic package-from-proposed

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

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

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

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

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

[Touch-packages] [Bug 1778801] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error

2018-06-26 Thread Joshua

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

Public bug reported:

update did not install. 
a similar thing has happened with several apps  have tried to download and the 
OS wont install them for some reason.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 26 22:26:14 2018
ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-08 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

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


** Tags: amd64 apport-package bionic package-from-proposed

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

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

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  update did not install. 
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

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

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

[Touch-packages] [Bug 1773685] [NEW] package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-05-27 Thread Joshua Griffin

Public bug reported:

IDK Anything about this

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sun May 27 13:47:30 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2018-05-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  IDK Anything about this

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 13:47:30 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

This did not reproduce in xenial or bionic, so that narrows it down to a
change between 7.7p1-2 (cosmic) and 7.6p1-4 (bionic)

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

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

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

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

Confirmed this in a Cosmic container this morning. It appears the
version in cosmic has an issue with the underscore.

Steps to reproduce:
1. lxc launch ubuntu-daily:c c
2. lxc exec c bash
3. echo "PermitUserEnvironment yes" > /etc/ssh/sshd_config
4. ssh-import-id 
5. add environment="FOO_BAR=1" to start of ssh key line ~/.ssh/authorized_keys
6. attempt to ssh to container and get Permission denined
7. remove the underscore, attempt to ssh again, and ssh will be sucessful

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

** Changed in: openssh (Ubuntu)
   Importance: Low => High

** Tags added: cosmic

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

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

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

[Touch-packages] [Bug 1771359] Re: No matching cipher found even if client and server have matching cipher

Hi, thanks for taking the time to file a bug.

The three ciphers you listed, aes128-cbc, 3des-cbc, and des-cbc, I
believe are not considered secure anymore. While your SSH client can use
them, it may not offer them without explicitly saying you wish to use
them as you have discovered.

It may be possible to use `ssh -vv ...` to produce some additional debug
output and may show what ciphers were offered.

As such I do not think this is actually a bug in Ubuntu and will mark it
incomplete. If you disagree or have additional information please feel
free to add it to this bug. Thanks again!

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

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

Title:
  No matching cipher found even if client and server have matching
  cipher

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Since Bionic upgrade (from Artful) I encounter problem to call HP
  switch with SSH.

  After the upgrade, trying to ssh some switch give me this message :

  $ ssh 192.168.0.1
  Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their 
offer: aes128-cbc,3des-cbc,des-cbc

  So, I look for supported cipher :

  $ ssh -Q cipher
  3des-cbc
  aes128-cbc
  aes192-cbc
  aes256-cbc
  rijndael-...@lysator.liu.se
  aes128-ctr
  aes192-ctr
  aes256-ctr
  aes128-...@openssh.com
  aes256-...@openssh.com
  chacha20-poly1...@openssh.com

  I see that aes128-cbc seem both supported. So I try... :

  $ ssh -c aes128-cbc 192.168.0.1

  ...and It's work !

  Workaround :

  I've added “ciphers aes128-cbc” to ~/.ssh/config file for each switch
  I manage.

  The ssh-client should detect automatically the good cipher ? No ?

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 15 15:39:00 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:7.6p1-4
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (21 days ago)

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

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

[Touch-packages] [Bug 1771359] Re: No matching cipher found even if client and server have matching cipher