[Touch-packages] [Bug 1914733] [NEW] Volume keys not working on Ubuntu 20.10 Groovy Gorilla

2021-02-04 Thread anil sharma
Public bug reported:

Volume keys not working but sound  still coming.  Problem is that sound
is not decreasing or increasing by using volume keys. sound only
increase or decrease through Alsa Mixer.

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

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

Title:
  Volume keys not working on Ubuntu 20.10 Groovy Gorilla

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Volume keys not working but sound  still coming.  Problem is that
  sound is not decreasing or increasing by using volume keys. sound only
  increase or decrease through Alsa Mixer.

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

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


[Touch-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

2021-02-04 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Focal:
  Fix Committed
Status in binutils source package in Groovy:
  Fix Released

Bug description:
  == Comment: #0 - Heinz-Werner Seeck  - 
2020-07-31 03:28:30 ==
  On z13 we have that vector alignment hints are already accepted. This 
backport enables GAS to accept such hints not only for target z14 but also for 
z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly 
benefit from such alignment hints. (note a separate bugzilla entry for GCC 
allowing to emit alignment hints for z13 will be opened shortly)

  This is a backport of upstreams commit 26b6ab7a0e.

  Userspace tool common name: as

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Already included within 20.10 via LP:
  https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654

  This should also be SRUed for 20.04

  [Impact]

   * Vector alignment hints were enabled for z14 processors, but not z13

   * Since the z13 processors support vector alignment hints, binutils should
 have them enabled for z13

  [Test Case]

   * Run the test suite to make sure all tests pass

   * Pull in the change, and re-run the test suite to make sure all
 tests still pass. This backport includes tests for the vector
 alignment hints.

  [Where problems could occur]

   * If vector alignment hints were not enabled correctly we could still
 compile code with incorrectly ordered opcodes

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

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


[Touch-packages] [Bug 1914481] Re: use the size of the data when determing the server response

2021-02-04 Thread Launchpad Bug Tracker
** Branch linked: lp:whoopsie

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

Title:
  use the size of the data when determing the server response

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Focal:
  New
Status in whoopsie source package in Groovy:
  New
Status in whoopsie source package in Hirsute:
  Fix Released

Bug description:
  whoopsie's server_response code is using "g_string_append" instead of
  "g_string_append_len" which has the knock on effect of sending too
  much data to its "handle_response". This ends up being a problem if
  the daisy servers are running on Ubuntu 18.04 instead of Ubuntu 16.04.

  Here's an example when using whoopsie on groovy to send a crash to a
  bionic daisy server:

  [15:35:30] Sent; server replied with: No error
  [15:35:30] Response code: 200
  [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 
OOPSID
  0

  [15:35:30] Got command: OOPSID

  We can see a fair number of extra characters (\n0\n\n) after the OOSID
  command.

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

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


[Touch-packages] [Bug 1914652] Re: Broken dir and symlinks in package

2021-02-04 Thread Alex Murray
*** This bug is a duplicate of bug 1908818 ***
https://bugs.launchpad.net/bugs/1908818

** This bug has been marked a duplicate of bug 1908818
   pure packaging of libnss3

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

Title:
  Broken dir and symlinks in package

Status in nss package in Ubuntu:
  Confirmed

Bug description:
  /usr/lib/${DEB_HOST_MULTIARCH}# ls -al
  итого 8
  drwxr-xr-x   2 root root 4096 окт 22 17:02 .
  drwxr-xr-x 141 root root 4096 янв 25 23:13 ..
  lrwxrwxrwx   1 root root   18 ноя  1 15:59 libfreebl3.chk -> 
nss/libfreebl3.chk
  lrwxrwxrwx   1 root root   17 ноя  1 15:59 libfreebl3.so -> nss/libfreebl3.so
  lrwxrwxrwx   1 root root   22 ноя  1 15:59 libfreeblpriv3.chk -> 
nss/libfreeblpriv3.chk
  lrwxrwxrwx   1 root root   21 ноя  1 15:59 libfreeblpriv3.so -> 
nss/libfreeblpriv3.so

  https://packages.ubuntu.com/groovy/amd64/libnss3/filelist

  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk <-- what this?
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian/overrides/libnss3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb  4 23:54:38 2021
  InstallationDate: Installed on 2020-11-01 (95 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1908818] Re: pure packaging of libnss3

2021-02-04 Thread Alex Murray
** Also affects: nss (Ubuntu Hirsute)
   Importance: Undecided
   Status: Fix Released

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

Title:
  pure packaging of libnss3

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Groovy:
  Triaged
Status in nss source package in Hirsute:
  Fix Released

Bug description:
  dpkg -L libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share
  /usr/share/doc
  /usr/share/doc/libnss3
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/libnss3
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk

  
  as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to 
x86_64-linux-gnu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec 20 14:36:10 2020
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1477489] Re: Content indexing spamming syslog and logging personal information (emails etc) - there should be a way to disable file contents indexing

2021-02-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Content indexing spamming syslog and logging personal information
  (emails etc) - there should be a way to disable file contents indexing

Status in Tracker:
  Invalid
Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently changed from Ubuntu 15.04, to Ubuntu Gnome 15.04 (I was
  using Unity, now Gnome Shell), and since I have changed I have noticed
  some problems similar to this bug report in Tracker's logging to
  syslog: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754907

  So what I am noticing is that it is spamming my syslog with loads and
  loads of stuff similar to the bug report I linked to above. But not
  only is it spamming contents there, it is also putting the contents
  and details of my private emails etc, for instance I have OSSEC HIDS
  running and it keeps on reporting to me of these sorts of things:

  "

  OSSEC HIDS Notification. 2015 Jul 22 21:08:46

  Received From: Weaponised-Towel->/var/log/syslog Rule: 1003 fired
  (level 13) -> "Non standard syslog message (size too large)." Portion
  of the log(s):

  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]:
  nie:description "Beginning Android Games, Second Edition offers
  everything you need to join the ranks of successful Android game
  developers, including Android tablet game app development
  considerations. You'll start with game design fundamentals and
  programming basics, and then progress toward creating your own basic
  game engine and playable game apps that work on Android and earlier
  version compliant smartphones and now tablets. This will give you
  everything you need to branch out and write your own Android games.
  The potential user base and the wide array of available high-
  performance devices makes Android an attractive target for aspiring
  game developers. Do you have an awesome idea for the next break-
  through mobile gaming title? Beginning Android Games will help you
  kick-start your project. This book will guide you through the process
  of making several example game apps using APIs available in new
  Android SDK and earlier SDK releases for Android smartphones and
  tablets: The fundamentals of game development and design suitable for
  Android smartphones and tablets The Android platform basics to apply
  those fundamentals in the context of making a game, inc

  --END OF NOTIFICATION

  "

  And then when I checked my syslog for that time period these are the
  sorts of things that I saw:

  "

  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: INSERT {
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: GRAPH 
 {
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: 
 nie:dataSource 
 .
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: 
 a nfo:EBook ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator [ a 
nco:PersonContact ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:fullname "Zechner, 
Mario & Green, Robert" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameFamily 
"Zechner" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameGiven "Mario" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameAdditional "& 
Green, Robert" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator 
] ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator [ a 
nco:PersonContact ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:fullname "Robert 
Green" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameFamily "Green" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameGiven "Robert" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator 
] ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:title "Beginning 
Android Games" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:publisher [ a 
nco:Contact ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:fullname "Apress"] ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:identifier 
"URN:ISBN:978-1-4302-4677-0" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:identifier 
"9781430246770" ;
  Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:description "Beginning Android Games, Second Edition offers everything 
you need to join the ranks of successful Android game developers, including 
Android tablet game app development considerations. You'll start with game 
design fundamentals and programming basics, and then progress toward creating 
your own basic game engine and playable game apps 

[Touch-packages] [Bug 1914652] Re: Broken dir and symlynks in package

2021-02-04 Thread navycat
** Changed in: nss (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- Broken dir and symlynks in package
+ Broken dir and symlinks in package

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

Title:
  Broken dir and symlinks in package

Status in nss package in Ubuntu:
  Confirmed

Bug description:
  /usr/lib/${DEB_HOST_MULTIARCH}# ls -al
  итого 8
  drwxr-xr-x   2 root root 4096 окт 22 17:02 .
  drwxr-xr-x 141 root root 4096 янв 25 23:13 ..
  lrwxrwxrwx   1 root root   18 ноя  1 15:59 libfreebl3.chk -> 
nss/libfreebl3.chk
  lrwxrwxrwx   1 root root   17 ноя  1 15:59 libfreebl3.so -> nss/libfreebl3.so
  lrwxrwxrwx   1 root root   22 ноя  1 15:59 libfreeblpriv3.chk -> 
nss/libfreeblpriv3.chk
  lrwxrwxrwx   1 root root   21 ноя  1 15:59 libfreeblpriv3.so -> 
nss/libfreeblpriv3.so

  https://packages.ubuntu.com/groovy/amd64/libnss3/filelist

  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk <-- what this?
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian/overrides/libnss3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb  4 23:54:38 2021
  InstallationDate: Installed on 2020-11-01 (95 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1886161] Re: Unattended upgrades should work on roaming laptops

2021-02-04 Thread Robin
Just an update, for what it's worth.

I solved this problem with a shell script triggered by Network Manager's
"up" hook. Because UU does not update the package list, I had to resort
to a `apt-get update && apt-get dist-upgrade` with
`DEBIAN_FRONTEND=noninteractive` and a whole bunch of options to make
sure everything runs reliably in the background. Convoluted and
laborious.

But now my Ubuntu is *always* up to date. Before, it regularly went
*months* without a security update.

Putting aside whose fault it is, this absolutely IS a problem.

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

Title:
  Unattended upgrades should work on roaming laptops

Status in apt package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  For many if not most laptop computers, Unattended Upgrades seems all
  but useless by design.

  For upgrades to happen, with default config, 3 conditions must be met:

  - an internet connection must be up and running when the timer or cron or 
anacron tries the unattended upgrade
  - the connection must not be metered, whatever that means 
(Skip-Updates-On-Metered-Connections "true")
  - the computer must be plugged in (OnlyOnACPower "true")

  These are insurmountable problems for many laptops on the go.
  Inevitably, security upgrades will almost never run unattended on such
  computers. I discovered with shock that Unattended Upgrades had almost
  never run on my laptop. I tried all possible config tweaks. Nothing
  worked reliably and in the end I gave up and wrote a upgrade script
  which uses Network Manager's connection-up hook. Unattended Upgrades
  needs to do something like this out of the box. Users should not need
  to write scripts to ensure security upgrades.

  Unattended upgrades is an excellent project for servers. But it really
  needs to work, out of the box, on laptops too.

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

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


[Touch-packages] [Bug 1914481] Re: use the size of the data when determing the server response

2021-02-04 Thread Steve Beattie
For fixing this via an SRU for focal and groovy, the Ubuntu Security
team is okay with the result of this going to the security pocket,
assuming the update is built in a ppa where only security updates are
enabled.

Thanks!

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

Title:
  use the size of the data when determing the server response

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Focal:
  New
Status in whoopsie source package in Groovy:
  New
Status in whoopsie source package in Hirsute:
  Fix Released

Bug description:
  whoopsie's server_response code is using "g_string_append" instead of
  "g_string_append_len" which has the knock on effect of sending too
  much data to its "handle_response". This ends up being a problem if
  the daisy servers are running on Ubuntu 18.04 instead of Ubuntu 16.04.

  Here's an example when using whoopsie on groovy to send a crash to a
  bionic daisy server:

  [15:35:30] Sent; server replied with: No error
  [15:35:30] Response code: 200
  [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 
OOPSID
  0

  [15:35:30] Got command: OOPSID

  We can see a fair number of extra characters (\n0\n\n) after the OOSID
  command.

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

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


[Touch-packages] [Bug 1886161] Re: Unattended upgrades should work on roaming laptops

2021-02-04 Thread Robin
** Summary changed:

- UU should work on roaming laptops
+ Unattended upgrades should work on roaming laptops

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

Title:
  Unattended upgrades should work on roaming laptops

Status in apt package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  For many if not most laptop computers, Unattended Upgrades seems all
  but useless by design.

  For upgrades to happen, with default config, 3 conditions must be met:

  - an internet connection must be up and running when the timer or cron or 
anacron tries the unattended upgrade
  - the connection must not be metered, whatever that means 
(Skip-Updates-On-Metered-Connections "true")
  - the computer must be plugged in (OnlyOnACPower "true")

  These are insurmountable problems for many laptops on the go.
  Inevitably, security upgrades will almost never run unattended on such
  computers. I discovered with shock that Unattended Upgrades had almost
  never run on my laptop. I tried all possible config tweaks. Nothing
  worked reliably and in the end I gave up and wrote a upgrade script
  which uses Network Manager's connection-up hook. Unattended Upgrades
  needs to do something like this out of the box. Users should not need
  to write scripts to ensure security upgrades.

  Unattended upgrades is an excellent project for servers. But it really
  needs to work, out of the box, on laptops too.

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

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


[Touch-packages] [Bug 1894833] Re: [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background noise on internal microphone

2021-02-04 Thread Mircea Baja
Update: in my case I took the case with Dell support, they changed some
parts, which included obviously the internal microphone, but also the
trackpad (they are positioned close to each other physically. That fixed
the issue, the sound is good now. In my case the status 'Invalid' is
correct, it was a hardware issue.

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

Title:
  [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background
  noise on internal microphone

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Problem: Lots of background noise on the internal microphone. If I
  record it in Audacity it seems that most of the noise is in the Left-
  Front channel. The Right-Front channel is still noisy/bad quality, but
  not as bad.

  Hardware: Dell XPS 15 7590 laptop (basically 2019 model)
  OS: Ubuntu 20.04 fresh/plain installation:
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Other tests:
  - If I use a external/USB headsets+microphone sound is fine
  - If I boot from Ubuntu 20.04 live USB it still has the problem
  - Tested with other versions/distributions, but it still has the problem: 
ubuntu-19.10-desktop-amd64, linuxmint-20-cinnamon-64bit, 
Fedora-Workstation-Live-x86_64-32-1.6, xubuntu-20.04.1-desktop-amd64, 
pop-os_20.04_amd64_nvidia_13, ubuntu-18.04.5-desktop-amd64

  - I tried many steps involving changing config files e.g.
  https://wiki.ubuntu.com/Audio/PositionReporting + reboot, none fixed
  the problem, reverted the config files back after every change

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mircea 1400 F pulseaudio
   /dev/snd/pcmC0D0c:   mircea 1400 F...m pulseaudio
   /dev/snd/pcmC0D0p:   mircea 1400 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 12:33:31 2020
  InstallationDate: Installed on 2020-09-06 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 15 7590, Realtek ALC3266, Mic, Internal] Background noise or low 
volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd07/03/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-09-08T11:02:41.506649

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

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


[Touch-packages] [Bug 1914652] [NEW] Broken dir and symlynks in package

2021-02-04 Thread navycat
Public bug reported:

/usr/lib/${DEB_HOST_MULTIARCH}# ls -al
итого 8
drwxr-xr-x   2 root root 4096 окт 22 17:02 .
drwxr-xr-x 141 root root 4096 янв 25 23:13 ..
lrwxrwxrwx   1 root root   18 ноя  1 15:59 libfreebl3.chk -> nss/libfreebl3.chk
lrwxrwxrwx   1 root root   17 ноя  1 15:59 libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx   1 root root   22 ноя  1 15:59 libfreeblpriv3.chk -> 
nss/libfreeblpriv3.chk
lrwxrwxrwx   1 root root   21 ноя  1 15:59 libfreeblpriv3.so -> 
nss/libfreeblpriv3.so

https://packages.ubuntu.com/groovy/amd64/libnss3/filelist

/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk <-- what this?
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian/overrides/libnss3

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Feb  4 23:54:38 2021
InstallationDate: Installed on 2020-11-01 (95 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANGUAGE=ru
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  Broken dir and symlynks in package

Status in nss package in Ubuntu:
  New

Bug description:
  /usr/lib/${DEB_HOST_MULTIARCH}# ls -al
  итого 8
  drwxr-xr-x   2 root root 4096 окт 22 17:02 .
  drwxr-xr-x 141 root root 4096 янв 25 23:13 ..
  lrwxrwxrwx   1 root root   18 ноя  1 15:59 libfreebl3.chk -> 
nss/libfreebl3.chk
  lrwxrwxrwx   1 root root   17 ноя  1 15:59 libfreebl3.so -> nss/libfreebl3.so
  lrwxrwxrwx   1 root root   22 ноя  1 15:59 libfreeblpriv3.chk -> 
nss/libfreeblpriv3.chk
  lrwxrwxrwx   1 root root   21 ноя  1 15:59 libfreeblpriv3.so -> 
nss/libfreeblpriv3.so

  https://packages.ubuntu.com/groovy/amd64/libnss3/filelist

  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk <-- what this?
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian/overrides/libnss3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb  4 23:54:38 2021
  InstallationDate: Installed on 2020-11-01 (95 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

2021-02-04 Thread Brian Murray
Hello bugproxy, or anyone else affected,

Accepted binutils into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/binutils/2.34-6ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: binutils (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Focal:
  Fix Committed
Status in binutils source package in Groovy:
  Fix Released

Bug description:
  == Comment: #0 - Heinz-Werner Seeck  - 
2020-07-31 03:28:30 ==
  On z13 we have that vector alignment hints are already accepted. This 
backport enables GAS to accept such hints not only for target z14 but also for 
z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly 
benefit from such alignment hints. (note a separate bugzilla entry for GCC 
allowing to emit alignment hints for z13 will be opened shortly)

  This is a backport of upstreams commit 26b6ab7a0e.

  Userspace tool common name: as

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Already included within 20.10 via LP:
  https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654

  This should also be SRUed for 20.04

  [Impact]

   * Vector alignment hints were enabled for z14 processors, but not z13

   * Since the z13 processors support vector alignment hints, binutils should
 have them enabled for z13

  [Test Case]

   * Run the test suite to make sure all tests pass

   * Pull in the change, and re-run the test suite to make sure all
 tests still pass. This backport includes tests for the vector
 alignment hints.

  [Where problems could occur]

   * If vector alignment hints were not enabled correctly we could still
 compile code with incorrectly ordered opcodes

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

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


[Touch-packages] [Bug 1894833] Re: [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background noise on internal microphone

2021-02-04 Thread vak
Don't close this bug, please! The input from microphone is terrible :(

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

Title:
  [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background
  noise on internal microphone

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Problem: Lots of background noise on the internal microphone. If I
  record it in Audacity it seems that most of the noise is in the Left-
  Front channel. The Right-Front channel is still noisy/bad quality, but
  not as bad.

  Hardware: Dell XPS 15 7590 laptop (basically 2019 model)
  OS: Ubuntu 20.04 fresh/plain installation:
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Other tests:
  - If I use a external/USB headsets+microphone sound is fine
  - If I boot from Ubuntu 20.04 live USB it still has the problem
  - Tested with other versions/distributions, but it still has the problem: 
ubuntu-19.10-desktop-amd64, linuxmint-20-cinnamon-64bit, 
Fedora-Workstation-Live-x86_64-32-1.6, xubuntu-20.04.1-desktop-amd64, 
pop-os_20.04_amd64_nvidia_13, ubuntu-18.04.5-desktop-amd64

  - I tried many steps involving changing config files e.g.
  https://wiki.ubuntu.com/Audio/PositionReporting + reboot, none fixed
  the problem, reverted the config files back after every change

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mircea 1400 F pulseaudio
   /dev/snd/pcmC0D0c:   mircea 1400 F...m pulseaudio
   /dev/snd/pcmC0D0p:   mircea 1400 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 12:33:31 2020
  InstallationDate: Installed on 2020-09-06 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 15 7590, Realtek ALC3266, Mic, Internal] Background noise or low 
volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd07/03/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-09-08T11:02:41.506649

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

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


[Touch-packages] [Bug 1914644] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerw

2021-02-04 Thread Thomas Walther
Public bug reported:

package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
»installiertes initramfs-tools-Skript des Paketes post-
installation«-Unterprozess gab den Fehlerwert 1 zurück

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Feb  4 18:06:36 2021
ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to focal on 2021-02-04 (0 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  »installiertes initramfs-tools-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  »installiertes initramfs-tools-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb  4 18:06:36 2021
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to focal on 2021-02-04 (0 days ago)

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

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


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

2021-02-04 Thread Leon Pappas
I went along withe the whole mokutil route to get the NVidia drivers to 
work but that failed to rectify the problem.

The GUI started having huge issues (Second monitor stopped working. GUI 
would freeze and need a reboot). Tried reverting back to Nouveau and in 
the process lost my server.. Gui stopped working completely.

Luckily I could still access the drive contents. and installed on a new 
drive. Still not working 100% Second screen is detected but does not 
work. I get a black screen with a white mouse pointer. I can drag a 
window onto the monitor but if I release it it's gone. (I can't see 
where it is to drag it back)

On 2021/02/04 20:37, Alf Haakon Lund wrote:
> Even though the installer crashed, powering off the machine and
> restarting sent me to a 'Perform MOK management' menu where I had to
> input my chosen password from the relevant step in the installation
> process. After that rebooting took me to the Grub menu and I could
> successfully start Ubuntu Studio.
>
> After login there was a short flickering on the screen which I suspect
> could be the NVIDIA driver failing and falling back to the intel HD
> Graphics 530.
>

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

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

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

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

  We have two changes that help address this:

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

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

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

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

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

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

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

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

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1914278] Re: discover is not removing unused kernels

2021-02-04 Thread Erich Eickmeyer 
Since we narrowed it down, I filed the following upstream bug:
https://bugs.kde.org/show_bug.cgi?id=432513

** Bug watch added: KDE Bug Tracking System #432513
   https://bugs.kde.org/show_bug.cgi?id=432513

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

Title:
  discover is not removing unused kernels

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2021-02-04 Thread Alf Haakon Lund
Even though the installer crashed, powering off the machine and
restarting sent me to a 'Perform MOK management' menu where I had to
input my chosen password from the relevant step in the installation
process. After that rebooting took me to the Grub menu and I could
successfully start Ubuntu Studio.

After login there was a short flickering on the screen which I suspect
could be the NVIDIA driver failing and falling back to the intel HD
Graphics 530.

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

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

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

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

  We have two changes that help address this:

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

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

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

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

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

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

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

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

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

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

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

2021-02-04 Thread Alf Haakon Lund
Confirming bug as of today on HP ZBook 15 G3 with NVIDIA M2000M with
disk image downloaded yesterday from ubuntustudio.org
https://cdimage.ubuntu.com/ubuntustudio/releases/20.04.1/release/ubuntustudio-20.04.1
-dvd-amd64.iso.torrent

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

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

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

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

  We have two changes that help address this:

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-02-04 Thread Brian Murray
** Tags removed: rls-hh-incoming

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

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

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


[Touch-packages] [Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates

2021-02-04 Thread Brian Murray
** Tags removed: rls-ff-incoming

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

Title:
  update-initramfs should include firmware from /lib/firmware/updates

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Focal:
  New
Status in initramfs-tools source package in Groovy:
  New
Status in initramfs-tools source package in Hirsute:
  Triaged

Bug description:
  according to the kernel doc
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README

  Linux kernel will search firmware from
  "/lib/firmware/updates/" UTS_RELEASE,
  "/lib/firmware/updates",
  "/lib/firmware/" UTS_RELEASE,
  "/lib/firmware"

  But the add module function in initramfs-tools won't search the
  "/lib/firmware/updates".

  This problem applies to all Ubuntu releases.

  Attach patch to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:24:29 2016
  InstallationDate: Installed on 2014-04-23 (725 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates

2021-02-04 Thread Matthieu Clemenceau
** Tags added: fr-1103

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

Title:
  update-initramfs should include firmware from /lib/firmware/updates

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Focal:
  New
Status in initramfs-tools source package in Groovy:
  New
Status in initramfs-tools source package in Hirsute:
  Triaged

Bug description:
  according to the kernel doc
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README

  Linux kernel will search firmware from
  "/lib/firmware/updates/" UTS_RELEASE,
  "/lib/firmware/updates",
  "/lib/firmware/" UTS_RELEASE,
  "/lib/firmware"

  But the add module function in initramfs-tools won't search the
  "/lib/firmware/updates".

  This problem applies to all Ubuntu releases.

  Attach patch to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:24:29 2016
  InstallationDate: Installed on 2014-04-23 (725 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-02-04 Thread Matthieu Clemenceau
** Tags added: fr-1102

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

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

-- 
Mailing list: https://launchpad.net/~touch-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-04 Thread Balint Reczey
Systemd 247.3 fixes this which I'm pre-testing before upload at 
https://bileto.ubuntu.com/#/ticket/3840 .
ETA is next week.

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

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

Status in systemd:
  Fix Released
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 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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

2021-02-04 Thread William Wilson
** Changed in: binutils (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

** Changed in: binutils (Ubuntu Focal)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Focal:
  In Progress
Status in binutils source package in Groovy:
  Fix Released

Bug description:
  == Comment: #0 - Heinz-Werner Seeck  - 
2020-07-31 03:28:30 ==
  On z13 we have that vector alignment hints are already accepted. This 
backport enables GAS to accept such hints not only for target z14 but also for 
z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly 
benefit from such alignment hints. (note a separate bugzilla entry for GCC 
allowing to emit alignment hints for z13 will be opened shortly)

  This is a backport of upstreams commit 26b6ab7a0e.

  Userspace tool common name: as

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: binutils

  Already included within 20.10 via LP:
  https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654

  This should also be SRUed for 20.04

  [Impact]

   * Vector alignment hints were enabled for z14 processors, but not z13

   * Since the z13 processors support vector alignment hints, binutils should
 have them enabled for z13

  [Test Case]

   * Run the test suite to make sure all tests pass

   * Pull in the change, and re-run the test suite to make sure all
 tests still pass. This backport includes tests for the vector
 alignment hints.

  [Where problems could occur]

   * If vector alignment hints were not enabled correctly we could still
 compile code with incorrectly ordered opcodes

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

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


[Touch-packages] [Bug 1912326] Re: Privilege escalation to root with core file dump

2021-02-04 Thread Marc Deslauriers
** Information type changed from Private Security to Public Security

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

Title:
  Privilege escalation to root with core file dump

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released
Status in apport source package in Hirsute:
  Fix Released

Bug description:
  Vulnerabilities in Apport in ubuntu 20.04/18.04

  

  
  Author information 

  --


  Itai Greenhut(@Gr33nh4t)

  Aleph Research by HCL Appscan

  itai.green...@hcl.com


  SUMMARY

  ---

  We found several vulnerabilities in apport program which work on
  default installations of ubuntu 20.04/18.04.

  We were able to chain those vulnerabilities together to get local
  privilege escalation to root from an unprivileged user.


  Issue 1: Bypass drop_privileges and set Uid and Gid to arbitrary value

  --

  real_uid and real_gid are set by reading /proc/pid/status file and
  parsing its content.

  "get_pid_info" function will iterate through each line and if a line
  starts with "Uid:" or "Gid:" it takes the first argument in that line
  and puts it into real_uid and real_gid variables.

  We were able to bypass this by crashing a process with a file name set
  to "a\rUid: 0\rGid: 0".

  When the process crashed, we "injected" those values to
  /proc/pid/status file (in the Name field), causing apport to never
  really drop privileges in the function drop_privileges( real_uid now
  is 0 and real_gid is also 0).

  By having full control over real_uid and real_gid  we were able to
  bypass the suid check on "write_user_coredump" function.


  Issue 2: Bypass get_process_startime check 

  -

  Apport checks if the process was replaced after the crash by comparing
  between apport_start and process_start.

  process_start gets the start time of the process by parsing the
  content of /proc/pid/stat file.

  
  The start time is extracted from the 22 column of the /proc/pid/stat file. 

  We were able to bypass this check by recycle the pid with a process
  with " "(space) in its filename, causing get_process_starttime to
  return the wrong value (which is smaller than apport_start).


  Issue 3: delay apport get_pid_info by 30 seconds and recycle pid to
  suid process

  
-

  We were able to delay apport get_pid by 30 seconds from the process
  creation by acquiring the lock file of apport.

  We were able to lock the file by creating a fifo file with a
  predictable name file crash in /var/log, and then create a new
  instance of apport.


  Now when we create another apport instance it will then be locked for
  30 seconds before getting a timeout.

  We can release the lock file of the first instance by writing to the
  fifo file.


  Exploitation:

  -

  
  Our main goal in the exploitation is to write core file owned by root with 
our content to an arbitrary directory. 

  Apport creates a core file in the current directory of the crashed
  process.

  As seen before on other apport exploits, we will create a core file in
  /etc/logrotate.d/ directory and execute a root shell.

  
  In order to exploit those issues to gain local privilege escalation we need 
to perform the following steps: 


  1. Create unpackaged=true configuration in ~/.conf/apport/settings

  2. mkfifo a predictable file of a decoy process.

  3. Run the decoy process causing the first apport instance to "hang".

  4. Create a symlink to /usr/bin/sudo with the name "a\rUid: 0\rGid: 0"

  5. chdir to desired directory.

  6. Create the crash program.

  7. Fork lots of new processes to make the pid wrap to
  crash_program_pid - 1.

  8. Send SIGSEGV to crash the program and trigger an additional apport
  instance.

  9. Send SIGKILL to terminate the program and release
  crash_program_pid.

  10. Create new process with fork and execve("a/rUid: 0\rGid: 0"). (The
  crafted file name)

  11. Release the first process by writing to the fifo file.


  The second apport instance will continue with execution and create a
  core dump in the current directory of the new suid process.


  Now we have a root owned core file in desired directory, we can
  exploit this by having a valid configuration for logrotate inside the
  core dump and place the core dump inside /etc/logrotate.d/ directory.


  CREDITS

  

[Touch-packages] [Bug 1914278] Re: apt autoremove is not removing unused kernels

2021-02-04 Thread Balint Reczey
APT and u-u and marking work as designed.

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

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

** Summary changed:

- apt autoremove is not removing unused kernels
+ discover is not removing unused kernels

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

Title:
  discover is not removing unused kernels

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs

2021-02-04 Thread Dimitri John Ledkov
** Tags added: rls-ff-incoming

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

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

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


[Touch-packages] [Bug 1833826] Re: grub menu entry FSCK does not work

2021-02-04 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1807537 ***
https://bugs.launchpad.net/bugs/1807537

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

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

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

Title:
  grub menu entry FSCK does not work

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  after a fresh install of Xubuntu 18.04.02 I tried "Ubuntu, mit Linux 
4.15.0-51-generic (recovery mode)"
  and as a result got:

  /lib/recocery-mode/recovery-menu: line 80: /etc/default/rcS: No such file or 
directory
  fsck from util-linux 2.31.1
  /dev/sda4 is mounted
  e2fsck: Cannot continue, aborting.

  I check both the live DVD and the installed filesystem and found
  /etc/default/rcS to be missing.

  I copied it over from an old Xubuntu live DVD (it contains commented
  out lines only) and now the error message is still:

  fsck from util-linux 2.31.1
  /dev/sda4 is mounted
  e2fsck: Cannot continue, aborting.

  This shouldn't happen on a newly installed system. I am a newbie to
  Ubuntu and when my laptop has trouble when I'm on he road basics like
  that should IMHO work as I won't have the ability to look for
  workarounds and wouldn't want to boot into a possibly corrupted
  filesystem.

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  util-linux:
Installiert:   2.31.1-0.4ubuntu3.3
Installationskandidat: 2.31.1-0.4ubuntu3.3
Versionstabelle:
   *** 2.31.1-0.4ubuntu3.3 100
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2021-02-04 Thread Sebastien Bacher
Thanks Dave, the updated patches have been uploaded now, removing the
block-proposed

** Tags removed: block-proposed

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-02-04 Thread Dimitri John Ledkov
adding breaks on linux-meta in -security, on dkms package versions that
are in -updates only, would result in the kernel being held back and not
get autoinstalled.

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-02-04 Thread Dimitri John Ledkov
@seth-arnold @mdeslaur

Mostly the dkms packages ship source code only, without strict binary
deps on packages/libraries from updates. It should be safe to publish
them into -security pocket.

It is correct that there were a few bugs with dkms modules, which are
now resolved in -updates. But one can still upgrade from offline
installation using 20.04.1 media to something broken.

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1914481] Re: use the size of the data when determing the server response

2021-02-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.75

---
whoopsie (0.2.75) hirsute; urgency=medium

  * src/whoopsie.c: modify server_response() so that it does not incorrectly
assume that data is null-terminated and actually use the size of the data.
(LP: #1914481)

 -- Brian Murray   Wed, 03 Feb 2021 15:46:59 -0800

** Changed in: whoopsie (Ubuntu Hirsute)
   Status: Triaged => Fix Released

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

Title:
  use the size of the data when determing the server response

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Focal:
  New
Status in whoopsie source package in Groovy:
  New
Status in whoopsie source package in Hirsute:
  Fix Released

Bug description:
  whoopsie's server_response code is using "g_string_append" instead of
  "g_string_append_len" which has the knock on effect of sending too
  much data to its "handle_response". This ends up being a problem if
  the daisy servers are running on Ubuntu 18.04 instead of Ubuntu 16.04.

  Here's an example when using whoopsie on groovy to send a crash to a
  bionic daisy server:

  [15:35:30] Sent; server replied with: No error
  [15:35:30] Response code: 200
  [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 
OOPSID
  0

  [15:35:30] Got command: OOPSID

  We can see a fair number of extra characters (\n0\n\n) after the OOSID
  command.

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

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


[Touch-packages] [Bug 1913499] Re: Bluetooth input doesn't work w/ Bose QC35 ii

2021-02-04 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151

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

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

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

Title:
  Bluetooth input doesn't work w/ Bose QC35 ii

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Bose QC35 ii, the bluetooth audio works just fine
  initially, but the microphone does not. When I go to the sound
  settings and change the mic input to use the QC35 ii bluetooth input,
  the audio changes from stereo to mono and sounds terrible and cannot
  understand anything. Also the mic picks up some input, but the result
  output sounds about the same, completely un-understandable, a
  stuttering digitized version of the input.

  > lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6
  15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  3. I expected the microphone input and headset output to both work 
simultaneously via bluetooth.
  4. Only the headset output worked well, when enabling microphone both sounded 
terrible (unusable).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  Uname: Linux 5.10.5-051005-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 27 17:53:00 2021
  InstallationDate: Installed on 2021-01-06 (21 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic 
root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 03CPGC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn03CPGC:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: UART
BD Address: 28:C2:1F:87:52:EC  ACL MTU: 1024:8  SCO MTU: 240:4
UP RUNNING PSCAN 
RX bytes:1599 acl:0 sco:0 events:91 errors:0
TX bytes:198368 acl:0 sco:0 commands:849 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2021-01-27T17:24:11.108718

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

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


[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-02-04 Thread Kleber Sacilotto de Souza
The false positives on kernel ADT matrix were caused by an issue in
dkms-autopkgtest shipped by the dkms package, as we discussed here:

https://lists.ubuntu.com/archives/kernel-team/2021-February/116985.html

All the dkms packages which were failing to build in Focal with the
hwe-5.8 kernel are now fixed. We need now to fix dkms to make sure this
won't happen again.

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2021-02-04 Thread Norbert
Tested package from -proposed on both Ubuntu MATE 20.04.2 LTS and 20.10. 
Bug is now fixed. Thank you!

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

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Groovy:
  Fix Committed

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

  [Back trace]
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

  
  [Impact] 

   * If selected mirrors are not reachable or have
 expired GPG keys, software-properties-gtk
 would crash

  [Test Case]

   * Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors

   * Find your locale in this file and add a non-existent URL
 to the list

   * Run software-properties-gtk and choose your newly added
 URL from the "Download From" dropdown menu

   * Press "Close" in the bottom right, and when
 prompted press "Reload"

   * You should be presented with an error window rather than
 the program crashing

  [Where problems could occur]

   * The new error window binds to the parent window. If the
 parent window has gotten into a bad state this could
 cause problems

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

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


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2021-02-04 Thread Norbert
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

** Tags removed: eoan

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Groovy:
  Fix Committed

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

  [Back trace]
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

  
  [Impact] 

   * If selected mirrors are not reachable or have
 expired GPG keys, software-properties-gtk
 would crash

  [Test Case]

   * Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors

   * Find your locale in this file and add a non-existent URL
 to the list

   * Run software-properties-gtk and choose your newly added
 URL from the "Download From" dropdown menu

   * Press "Close" in the bottom right, and when
 prompted press "Reload"

   * You should be presented with an error window rather than
 the program crashing

  [Where problems could occur]

   * The new error window binds to the parent window. If the
 parent window has gotten into a bad state this could
 cause problems

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

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


[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

2021-02-04 Thread Peter Ludwig
Today I used tasksel to add "lubuntu-desktop" to an "ubuntu-desktop"
installation. Already installed and noticed by tasksel was additionally:
"SSH-Service" and "Print Server".

The installation of "lubunut-desktop" went fine. I logged in to lubuntu-
desktop and now I wanted to remove the "ubuntu-desktop" only ... because
it is an odroid and disk space is precoius.

I ran tasksel and deselected "ubuntu-Desktop".

I was logged in and was able to see how my desktop, start menue, icons
... were removed / uninstalled until in the end a completely naked
dektop was left. I was not able to run tasksel again. So I had to
reinstall again. :((

Ubuntu 18.04 on odroid u3.
 Image name: 
"ubuntu-18.04-4.16.0-v7-desktop-odroid-u2-u3-20190308_shrink.img.xz"

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

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

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