[Bug 1906885] Re: [20.04.1] The replacement of default copy/move system is not supported....

2020-12-04 Thread Norbert 
** Also affects: caja (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906885

Title:
  [20.04.1] The replacement of default copy/move system is not
  supported

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1429483] Re: Kubuntu Vivid 1 Beta 15.04: Muon preferences are not saved

2020-12-04 Thread Krótki 
More details to comment #3 above:

This might be a user rights issue. Muon apparently reads the "Treat
recommended packages as dependencies" setting from APT config files in
/etc/apt. (see "man apt.conf"). But since I was launching Muon as a non-
root user, it was obviously not able to update settings in /etc/apt.

If I create an /etc/apt.apt.conf file with the following contents:

APT::Install-Recommends "false";

and restart Muon, then the "Treat recommended packages as dependencies"
becomes unchecked. (Though checking/unchecking of this option is again
not saved.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429483

Title:
  Kubuntu Vivid 1 Beta 15.04: Muon preferences are not saved

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906907] Status changed to Confirmed

2020-12-04 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906907

Title:
  Laptop unable to wake up after being suspended

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1429483] Re: Kubuntu Vivid 1 Beta 15.04: Muon preferences are not saved

2020-12-04 Thread Krótki 
I am experiencing the same bug on a fresh install of Kubuntu 20.10
(Polish language version).

1. Launch Muon from the KDE "start menu".
2. Open "Settings -> Configure Muon Package Manager...".
3. Uncheck "Treat recommended packages as dependencies".
4. Click "OK".
5. Reopen "Settings -> Configure Muon Package Manager...".

Expected result:
The "Treat recommended packages as dependencies" option is unchecked.
Actual result:
The "Treat recommended packages as dependencies" option is checked.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429483

Title:
  Kubuntu Vivid 1 Beta 15.04: Muon preferences are not saved

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906907] [NEW] Laptop unable to wake up after being suspended

2020-12-04 Thread Rafael Santos 
Public bug reported:

Laptop was unable to wake up after being suspended by lid's closing,
resulting in a blank black screen, while LEDs on the laptop showed that
it had woken up. This bug happened using kernel 5.4.0-56.62, and it was
"solved" by changing the kernel used to version 5.4.0-54.60, in which
the default behavior of suspension when lid was closed and lock/login
screen after lid being lifted up ocurred as it always was.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-56-generic 5.4.0-56.62
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rafael 1700 F pulseaudio
 /dev/snd/controlC1:  rafael 1700 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  5 02:35:57 2020
InstallationDate: Installed on 2020-10-09 (57 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: TOSHIBA Satellite C55t-A
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=9b883e7b-5549-4c98-8084-ff648bf6066e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-54-generic N/A
 linux-backports-modules-5.4.0-54-generic  N/A
 linux-firmware1.187.4
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd04/28/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Durban-Curiosity 10S/10SG
dmi.product.name: Satellite C55t-A
dmi.product.sku: PSCFJU
dmi.product.version: PSCFJU-00T00J
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906907

Title:
  Laptop unable to wake up after being suspended

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

2020-12-04 Thread Chi Hang 
** Also affects: containerd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906906] Re: Memory leak in X.org

2020-12-04 Thread Antoine Fontaine 
** Description changed:

  Hi, I think I've found a memory leek in X.org. The memory usage goes up
  and up (I was at ~3.4GB when I decided to open this bug report), and
- barely goes down when I close X clients (windows) (closing half of them
- brought me to 3.3GB).
+ barely goes down when I close X clients (closing half of the windows
+ brought me down to 3.3GB).
  
  https://paste.gnugen.ch/raw/oUhi
  
  I'm using Ubuntu 20.04 LTS and I am kinda stuck with X.org for Wacom
- tablet support. This is quite annoying and made the system hang (out of
- memory -> 100% CPU usage while Linux was trying not to kill anything. A
- force reboot was required). I had to add more swap, because 8GB + 2GB of
- swap (the default) wasn't enough.
+ tablet support. This is quite annoying and made the system hang twice.
+ (The system ran out of memory, which caused 100% CPU usage while Linux
+ was trying not to kill anything, and a force reboot was required). I had
+ to add more swap, because 8GB + the default 2GB of swap weren't enough.
  
  From the debugging X wiki page http://wiki.ubuntu.com/X/Reporting (last 
edited in 2012) :
  ```
  $ sudo cat /sys/kernel/debug/dri/0/i915_gem_objects
  412 shrinkable [0 free] objects, 140279808 bytes
  
  systemd-logind: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 
unbound, 0 closed)
  Xorg: 221 objects, 113086464 bytes (0 active, 52482048 inactive, 33603584 
unbound, 0 closed)
  Xorg: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 unbound, 0 
closed)
  Xorg: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 unbound, 
0 closed)
  gnome-shell: 857 objects, 274239488 bytes (0 active, 127623168 inactive, 
146616320 unbound, 0 closed)
  gnome-shell: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 
unbound, 0 closed)
  Xorg: 1 objects, 4096 bytes (0 active, 0 inactive, 4096 unbound, 0 closed)
  ```
  After conversion, all bytes values are between 100 and 260MiB, which is large 
but not *that* large.
  
  I know the basics of how to use GDB, but don't know how to find what's
  using the memory. I am willing to compile and test a patched package
  someone suggests a patch.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 05:51:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
  InstallationDate: Installed on 2020-11-05 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
-  Bus 001 Device 002: ID 8087:8001 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 002 Device 003: ID 5986:0366 Acer, Inc Integrated Camera
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 002: ID 8087:8001 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 002 Device 003: ID 5986:0366 Acer, Inc Integrated Camera
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20CLS28G02
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=356b9ac9-6bdb-4fd6-83a5-5fcec346ace9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET40W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CLS28G02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: 479364
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET40W(1.19):bd12/08/2015:svnLENOVO:pn20CLS28G02:pvrThinkPadX250:rvnLENOVO:rn20CLS28G02:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X250
  dmi.product.name: 20CLS28G02
  dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6

[Bug 1906906] [NEW] Memory leak in X.org

2020-12-04 Thread Antoine Fontaine 
Public bug reported:

Hi, I think I've found a memory leek in X.org. The memory usage goes up
and up (I was at ~3.4GB when I decided to open this bug report), and
barely goes down when I close X clients (closing half of the windows
brought me down to 3.3GB).

https://paste.gnugen.ch/raw/oUhi

I'm using Ubuntu 20.04 LTS and I am kinda stuck with X.org for Wacom
tablet support. This is quite annoying and made the system hang twice.
(The system ran out of memory, which caused 100% CPU usage while Linux
was trying not to kill anything, and a force reboot was required). I had
to add more swap, because 8GB + the default 2GB of swap weren't enough.

>From the debugging X wiki page http://wiki.ubuntu.com/X/Reporting (last edited 
>in 2012) :
```
$ sudo cat /sys/kernel/debug/dri/0/i915_gem_objects
412 shrinkable [0 free] objects, 140279808 bytes

systemd-logind: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 
unbound, 0 closed)
Xorg: 221 objects, 113086464 bytes (0 active, 52482048 inactive, 33603584 
unbound, 0 closed)
Xorg: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 unbound, 0 
closed)
Xorg: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 unbound, 0 
closed)
gnome-shell: 857 objects, 274239488 bytes (0 active, 127623168 inactive, 
146616320 unbound, 0 closed)
gnome-shell: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 
unbound, 0 closed)
Xorg: 1 objects, 4096 bytes (0 active, 0 inactive, 4096 unbound, 0 closed)
```
After conversion, all bytes values are between 100 and 260MiB, which is large 
but not *that* large.

I know the basics of how to use GDB, but don't know how to find what's
using the memory. I am willing to compile and test a patched package
someone suggests a patch.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  5 05:51:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
InstallationDate: Installed on 2020-11-05 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 001 Device 002: ID 8087:8001 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 5986:0366 Acer, Inc Integrated Camera
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20CLS28G02
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=356b9ac9-6bdb-4fd6-83a5-5fcec346ace9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET40W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CLS28G02
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: 479364
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET40W(1.19):bd12/08/2015:svnLENOVO:pn20CLS28G02:pvrThinkPadX250:rvnLENOVO:rn20CLS28G02:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X250
dmi.product.name: 20CLS28G02
dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250
dmi.product.version: ThinkPad X250
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906906

Title:
  Memory leak in X.org

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1831348] Re: The Progress Bar for emptying the Trash stuck at 0

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for pluma (Ubuntu) because there has been no activity for 60
days.]

** Changed in: pluma (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831348

Title:
  The Progress Bar for emptying the Trash stuck at 0

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893900] Re: ModuleNotFoundError: No module named 'distutils.sysconfig'

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for zfs-linux (Ubuntu) because there has been no activity for
60 days.]

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893900

Title:
  ModuleNotFoundError: No module named 'distutils.sysconfig'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893900] Re: ModuleNotFoundError: No module named 'distutils.sysconfig'

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for zfs-linux (Ubuntu Groovy) because there has been no
activity for 60 days.]

** Changed in: zfs-linux (Ubuntu Groovy)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893900

Title:
  ModuleNotFoundError: No module named 'distutils.sysconfig'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895405] Re: Bluetooth mouse does not work in Ubuntu 16.04

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895405

Title:
  Bluetooth mouse does not work in Ubuntu 16.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895405] Re: Bluetooth mouse does not work in Ubuntu 16.04

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895405

Title:
  Bluetooth mouse does not work in Ubuntu 16.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897603] Re: [FFe] update llvm-defaults toolchain to 11

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for llvm-defaults (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: llvm-defaults (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897603

Title:
  [FFe] update llvm-defaults toolchain to 11

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895710] Re: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden.

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895710

Title:
  Die Paketliste oder die Statusdatei konnte nicht eingelesen oder
  geöffnet werden.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898059] Re: [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes (in kernel 5.4.0-48.52, but 5.8.13 works)

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898059

Title:
  [POSITIVO BGH] Repeated sound constantly, and some cracky noise
  sometimes (in kernel 5.4.0-48.52, but 5.8.13 works)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897993] Re: Upgrade from v18 LTS to 20.04.1 LTS doesn't work both via shell and using upgrade manager

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897993

Title:
  Upgrade from v18 LTS to 20.04.1 LTS doesn't work both via shell and
  using upgrade manager

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898302] Re: Lubuntu makes /bin and /sbin symlinks

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for lubuntu-meta (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: lubuntu-meta (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898302

Title:
  Lubuntu makes /bin and /sbin symlinks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898560] Re: all it is ok

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898560

Title:
  all it is ok

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898470] Re: Activities and apps view overlap after session is active for some time

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898470

Title:
  Activities and apps view overlap after session is active for some time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1898470/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898562] Re: Si è verificato un problema irresolubile durante il calcolo dell'avanzamento.

2020-12-04 Thread Launchpad Bug Tracker 
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898562

Title:
  Si è verificato un problema irresolubile durante il calcolo
  dell'avanzamento.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1832132] Re: incorrect results for g++ -std=c++11 -O3 -DNDEBUG

2020-12-04 Thread Bradley Bell 
It turns out it was an error in my test; see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98151

** Bug watch added: GCC Bugzilla #98151
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98151

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832132

Title:
  incorrect results for g++ -std=c++11 -O3 -DNDEBUG

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906904] [NEW] Copying Screenshots To Clipboard Is Only Effective As Long As MATE Screenshot Is Not Closed

2020-12-04 Thread Clayton Diggs 
Public bug reported:

When taking a screenshot with MATE Screenshot, the copy to clipboard
option is only effective while MATE Screenshot remains open. Ideally,
the running status of the screenshot utility should not affect the
contents of the clipboard. Typically, the screenshot utility is only
needed while taking and saving screenshots, but is no longer useful once
that action transitions to sending or sharing that screenshot, which
takes you away from the application (thus closing it).

Ubuntu MATE 20.10 (All packages up to date as of filing.)

MATE Utils Version: 1.24.0-1 amd64
MATE Screenshot Version: 1.24.0

System information:
System:Kernel: 5.8.0-31-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 
Desktop: MATE 1.24.1 
   Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   Type: Desktop Mobo: Micro-Star model: MPG X570 GAMING PLUS (MS-7C37) 
v: 2.0 
   serial:  UEFI: American Megatrends v: A.B0 date: 10/29/2020 
CPU:   Info: 8-Core model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: 
Zen 2 L2 cache: 4096 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 140007 
   Speed: 4375 MHz min/max: N/A Core speeds (MHz): 1: 4375 2: 4375 3: 
4380 4: 4375 5: 4375 
   6: 4375 7: 4375 8: 4376 9: 4375 10: 4375 11: 4366 12: 4375 13: 4375 
14: 4375 15: 4375 
   16: 4375 
Graphics:  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] 
vendor: XFX Pine 
   driver: amdgpu v: kernel bus ID: 2f:00.0 
   Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati 
   unloaded: fbdev,modesetting,radeon,vesa resolution: 3840x2160~60Hz 
   OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.38.0 
5.8.0-31-generic LLVM 11.0.0) 
   v: 4.6 Mesa 20.2.1 direct render: Yes 
Audio: Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus 
ID: 2f:00.1 
   Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI 
driver: snd_hda_intel 
   v: kernel bus ID: 31:00.4 
   Device-3: Logitech HD Pro Webcam C920 type: USB driver: 
snd-usb-audio,uvcvideo 
   bus ID: 5-1:3 
   Device-4: Kingston HyperX 7.1 Audio type: USB driver: 
hid-generic,snd-usb-audio,usbhid 
   bus ID: 3-1:2 
   Device-5: C-Media Blue Snowball type: USB driver: 
hid-generic,snd-usb-audio,usbhid 
   bus ID: 5-4:2 
   Sound Server: ALSA v: k5.8.0-31-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
   vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel port: d000 
bus ID: 27:00.0 
   IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac:  
Drives:Local Storage: total: 2.27 TiB used: 90.89 GiB (3.9%) 
   ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3X0C-00SJG0 
size: 465.76 GiB 
   ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
   ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
   ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
   ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
Partition: ID-1: / size: 463.85 GiB used: 15.18 GiB (3.3%) fs: btrfs dev: 
/dev/nvme0n1p3 
   ID-2: /boot size: 945.6 MiB used: 214.4 MiB (22.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
   ID-3: /home size: 463.85 GiB used: 15.18 GiB (3.3%) fs: btrfs dev: 
/dev/nvme0n1p3 
Swap:  ID-1: swap-1 type: zram size: 32.91 GiB used: 0 KiB (0.0%) dev: 
/dev/zram0 
Sensors:   System Temperatures: cpu: 59.5 C mobo: N/A gpu: amdgpu temp: 54.0 C 
   Fan Speeds (RPM): N/A gpu: amdgpu fan: 522 
Info:  Processes: 436 Uptime: 2h 15m Memory: 31.34 GiB used: 6.35 GiB 
(20.2%) Init: systemd 
   runlevel: 5 Compilers: gcc: 10.2.0 Packages: 2085 Shell: Bash v: 
5.0.17 inxi: 3.1.07

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: mate-utils 1.24.0-1
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Dec  4 20:20:40 2020
InstallationDate: Installed on 2020-12-02 (2 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: mate-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mate-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906904

Title:
  Copying Screenshots To Clipboard Is Only Effective As Long As MATE
  Screenshot Is Not Closed

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

--

[Bug 1901609] Re: signond causes qprocess crash

2020-12-04 Thread Sandro 
Sorry read the message only partially on my phone at the time.   Here is
the requisite info:

Tested on Ubuntu 20.04 (KDE Neon, the only way this bug manifests
currently, as it only affects systems running Qt >= 5.19.0)

Updated the package and it successfully fixes the bug, using package in
proposed channel: 8.59+17.10.20170606-0ubuntu2.20.04.1

Opening SystemSettings/Online Accounts and adding a new Google account
now works:  A window appears with a web view asking user to submit
authentication credentials.  I added two accounts, and all worked fine.
Removing and re-adding an account also worked.  Closing the window
without completing workflow and trying again also works.  I couldn't
think of any other reasonable scenario.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901609

Title:
  signond causes qprocess crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted

2020-12-04 Thread Gordon Lack 
>> You can silence this with "df -x fuse.portal"

I can, but that's not the point.

Whatever is putting the mountpoint there (it's not my choice) should be
putting it there in such a way that this does not happen. I *own* the
mountpoint directory and file-system.  Why should I get an EPERM error
that I cannot remove?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905623

Title:
  df: /run/user/1000/doc: Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892929] Re: Gnome Tweak Tool titlebar not showing up

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

** Changed in: gnome-tweaks (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892929

Title:
  Gnome Tweak Tool titlebar not showing up

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900401] Re: Ryzen 1800X soft lockups

2020-12-04 Thread ed20900 
I have installed Linux 5.10-rc2. Currently, 30 minutes of uptime.

** Attachment added: "Linux 5.10 rc6 dmesg 30 minutes uptime"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900401/+attachment/5441146/+files/dmesg-ryzen-7-1800x-linux5.10rc6.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900401

Title:
  Ryzen 1800X soft lockups

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906250] Re: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.

2020-12-04 Thread Bug Watch Updater 
** Changed in: glibc
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906250

Title:
  Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
  qemu-s390x on x86_64.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906250]

2020-12-04 Thread Florian Weimer 
Fixed for glibc 2.33 via:

commit 84ba719b260551918965d0a433914de683087645
Author: Florian Weimer 
Date:   Fri Dec 4 09:13:43 2020 +0100

elf: Add endianness markup to ld.so.cache (bug 27008)

Use a reserved byte in the new format cache header to indicate whether
the file is in little endian or big endian format.  Eventually, this
information could be used to provide a unified cache for qemu-user
and similiar scenarios.

Reviewed-by: Adhemerval Zanella  

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906250

Title:
  Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
  qemu-s390x on x86_64.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835024]

2020-12-04 Thread Dtownsend 
*** Bug 1680439 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835024

Title:
  firefox fails to use the default profile from classic snaps

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835024]

2020-12-04 Thread Dtownsend 
I vaguely recall some plan to distribute devedition as a separate snap
at some point which this would break but it looks like that hasn't
happened so this is fine. I really wish there was a sane API to detect
this though, environment variable detection always seemed likely to be
flakey.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835024

Title:
  firefox fails to use the default profile from classic snaps

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

2020-12-04 Thread Bryce Harrington 
I'd like to give you all an update and outline our plans for this.

The Canonical server team has made analysis of this issue a top
priority.  We've identified and tested out several possible theories.
Our findings suggest that the breakage involves two distinct issues, one
the BindTo= issue mentioned above, the other caused by a bug in the
docker.io package causing the service to stop on package upgrade; see
specifically the service stop command at the end of
/var/lib/dpkg/info/docker.io.prerm.  We'll use LP: #1870514 to track the
former issue, and #1906364 the latter.  LP: #1658691 gives some past
background for reference.

The tricky part is that unfortunately any change we make to docker.io
requires the running of the prerm script (the version of the script
already present on your system, not the one we'd be installing), and
thus triggers the bug.  In other words, updating your system to prevent
the bug will cause one more docker stop.  Thereafter, the upgrade will
not restart the service when rolling out CVE fixes to either containerd
or docker.io; it may prompt to do so if running interactively (e.g.
https://imgur.com/2Za5dbQ.png), otherwise it should respect the debconf
setting.

We would appreciate feedback, testing and/or review of the proposed fix,
available in this PPA:

   https://launchpad.net/~bryce/+archive/ubuntu/containerd-sru-lp1870514
-docker-dh/


** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: containerd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Hirsute)
   Importance: Undecided
   Status: Won't Fix

** Also affects: docker.io (Ubuntu Hirsute)
   Importance: Undecided
   Status: Confirmed

** Also affects: containerd (Ubuntu Hirsute)
   Importance: Undecided
   Status: Confirmed

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: containerd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: containerd (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: unattended-upgrades (Ubuntu Groovy)
   Status: New => Won't Fix

** No longer affects: containerd (Ubuntu)

** Changed in: unattended-upgrades (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: docker.io (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: docker.io (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Xenial)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: docker.io (Ubuntu Xenial)
   Importance: High => Critical

** Changed in: docker.io (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Focal)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Groovy)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Hirsute)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: docker.io (Ubuntu Hirsute)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** No longer affects: containerd (Ubuntu Xenial)

** No longer affects: containerd (Ubuntu Bionic)

** No longer affects: containerd (Ubuntu Focal)

** No longer affects: containerd (Ubuntu Groovy)

** No longer affects: containerd (Ubuntu Hirsute)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364

Title:
  unattended-upgrade still restarts blacklisted daemons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906894] Re: package grub-efi-amd64 2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 255

2020-12-04 Thread Apport retracing service 
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906894

Title:
  package grub-efi-amd64 2.04-1ubuntu12.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 255

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

2020-12-04 Thread Bryce Harrington 
I'd like to give you all an update and outline our plans for this.

The Canonical server team has made analysis of this issue a top
priority.  We've identified and tested out several possible theories.
Our findings suggest that the breakage involves two distinct issues, one
the BindTo= issue mentioned above, the other caused by a bug in the
docker.io package causing the service to stop on package upgrade; see
specifically the service stop command at the end of
/var/lib/dpkg/info/docker.io.prerm.  We'll use LP: #1870514 to track the
former issue, and #1906364 the latter.  LP: #1658691 gives some past
background for reference.

The tricky part is that unfortunately any change we make to docker.io
requires the running of the prerm script (the version of the script
already present on your system, not the one we'd be installing), and
thus triggers the bug.  In other words, updating your system to prevent
the bug will cause one more docker stop.  Thereafter, the upgrade will
not restart the service when rolling out CVE fixes to either containerd
or docker.io; it may prompt to do so if running interactively (e.g.
https://imgur.com/2Za5dbQ.png), otherwise it should respect the debconf
setting.

We would appreciate feedback, testing and/or review of the proposed fix,
available in this PPA:

   https://launchpad.net/~bryce/+archive/ubuntu/containerd-sru-lp1870514
-docker-dh/


** Package changed: containerd (Ubuntu Xenial) => docker.io (Ubuntu
Xenial)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1870514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906894] [NEW] package grub-efi-amd64 2.04-1ubuntu12.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 255

2020-12-04 Thread Tauane Fabris dos Santos 
Public bug reported:

Não consigo atualizar para a versão 20.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: grub-efi-amd64 2.04-1ubuntu12.2
ProcVersionSignature: Ubuntu 4.15.0-1093.103-oem 4.15.18
Uname: Linux 4.15.0-1093-oem x86_64
ApportVersion: 2.20.11-0ubuntu8.9
AptOrdering:
 google-chrome-stable:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Dec  4 22:08:32 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
DpkgHistoryLog:
 Start-Date: 2020-12-04  22:07:11
 Commandline: aptdaemon role='role-commit-packages' sender=':1.877'
 Upgrade: google-chrome-stable:amd64 (87.0.4280.66-1, 87.0.4280.88-1)
ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 255
InstallationDate: Installed on 2019-12-21 (349 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1093-oem 
root=UUID=7f206797-8c2e-45fe-966a-4bef5c202815 ro mem_sleep_default=deep quiet 
splash vt.handoff=7
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4ubuntu0.1
SourcePackage: grub2
Title: package grub-efi-amd64 2.04-1ubuntu12.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906894

Title:
  package grub-efi-amd64 2.04-1ubuntu12.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 255

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904270] Re: ubiquity does not support existing LUKS encrypted partitions

2020-12-04 Thread Tim Edwards 
Yeah it's a pretty ridiculous bug to have in an LTS release. Disk
encryption is a must these days, and other OSes like Windows support it
by default

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904270

Title:
  ubiquity does not support existing LUKS encrypted partitions

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900401] Re: Ryzen 1800X soft lockups

2020-12-04 Thread ed20900 
I tested with Linux 5.8.16 (https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.8.16/) and the lockups persisted. I installed a Ryzen 7
2700X and I have not had a single lockup in 17 days of uptime.

Is there any change in Linux 5.10 rc2 (or the latest, rc6) which affects
this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900401

Title:
  Ryzen 1800X soft lockups

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904640] Re: [SRU] [groovy] New upstream microrelease flatpak 1.8.3

2020-12-04 Thread Andrew Hayzen 
Sorry, a binary sync was performed by mistake this should have been a
source only sync.

Flatpak 1.8.3 provides what upstream has decided are important fixes for
users on the 1.8.x stable series, as you can see below some of the
improvements fix crashes, error reporting, authentication, and user
experience etc.

Upstream state the changes are as follows:

Fixed progress reporting for OCI and extra-data
The in-memory summary cache is more efficient
Fixed authentication getting stuck in a loop in some cases
Fixed authentication error reporting
We now extract OCI info for runtimes as well as apps
Fixed crash if anonymous authentication fails and -y is specified
flatpak info now only looks at the specified installation
if one is specified
Better error reporting for server HTTP errors during download
Uninstall now removes applications before the runtime it depends on
Fixed test-suite to pass with the latest OSTree version
Fixed dbus environment variables in flatpak enter
Avoid updating metadata from the remote when uninstalling
Fixed error message handling in various places
FlatpakTransaction now verifies all passed in refs to avoid
potential issues with invalid names
Updated translations

As with previous accepted flatpak changes, these should not break
ABI/API, tests are run during package build, autopkgtests are passing,
and a manual test plan is executed.

Let me know if I need to provide more information.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904640

Title:
  [SRU] [groovy] New upstream microrelease flatpak 1.8.3

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Matthew Ruffell 
** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901609] Re: signond causes qprocess crash

2020-12-04 Thread Sandro 
I can confirm that the updated packages work for me.  After adding them
to my system using -proposed as suggested, I am now able to get the
window to open asking for my google credentials when selecting to add a
new Google account.

As far as I'm concerned this fixes it for me.  Thanks to all for taking
the time to fix this :)

Please note, in case people come back here and start conflating issues
again - the scope of this fix is *only* to get the web view window where
you can enter your Google credentials.  It is well known that there were
other issues that may come along *after* that, but they are not related
to this bug at all.  As long as you get the window where you can enter
your email address, this bug is fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901609

Title:
  signond causes qprocess crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Ubuntu Foundations Team Bug Bot 
The attachment "Debdiff for adcli on Bionic" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Matthew Ruffell 
** Changed in: cyrus-sasl2 (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-04 Thread Ubuntu Foundations Team Bug Bot 
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906877

Title:
  diagnostics panel can leave automatic crash reporting enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted

2020-12-04 Thread Jalon Funk 
You can silence this with "df -x fuse.portal"

xdg-desktop-portal isn't tied to flatpak.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905623

Title:
  df: /run/user/1000/doc: Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906673] Re: Realm join hangs

2020-12-04 Thread Matthew Ruffell 
*** This bug is a duplicate of bug 1906627 ***
https://bugs.launchpad.net/bugs/1906627

** This bug has been marked a duplicate of bug 1906627
   adcli fails, can't contact LDAP server

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906673

Title:
  Realm join hangs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

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

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

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

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844453]

2020-12-04 Thread That-man-colin 
This from Google drive support in response to me asking them how to gain
access;

Currently, Google Drive does not have a feature where you can set a pin
or password to a certain files. Google Drive only saved the files the
way we created it. If you forgot the password on the file you want to
access you need to contact the program developer who created the apps or
program you used prior saving it to Google Drive.

Since you are trying to unlock Libre Office documents, you need to reach
their support for further assistance.

Libre Office Community Support
Libre Office Professional Support

When you contact Libre Office Support, please let them know that you
need help with the 6 digit PIN so that it will allow remote access from
your Libre Office account.

Where does the 6 digit pin originate?

I imagine even if LO fixes the issue then "newer" LO users who haven't
previously availed themselves of the service simply won't have a 6 Digit
PIN.

That's certainly my situation. I'm not trying to access existing files,
just trying to implement the cloud storage for some CALCs by File> Open
Remote> Add Service (from the dropdown menu defaulting to Manage
services.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844453

Title:
  [upstream] Access to the Google remote account does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844453]

2020-12-04 Thread That-man-colin 
This from Google drive support in response to me asking them how to gain
access;

Currently, Google Drive does not have a feature where you can set a pin
or password to a certain files. Google Drive only saved the files the
way we created it. If you forgot the password on the file you want to
access you need to contact the program developer who created the apps or
program you used prior saving it to Google Drive.

Since you are trying to unlock Libre Office documents, you need to reach
their support for further assistance.

Libre Office Community Support
Libre Office Professional Support

When you contact Libre Office Support, please let them know that you
need help with the 6 digit PIN so that it will allow remote access from
your Libre Office account.

Where does the 6 digit pin originate?

I imagine even if LO fixes the issue then "newer" LO users who haven't
previously availed themselves of the service simply won't have a 6 Digit
PIN.

That's certainly my situation. I'm not trying to access existing files,
just trying to implement the cloud storage for some CALCs by File> Open
Remote> Add Service (from the dropdown menu defaulting to Manage
services.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844453

Title:
  [upstream] Access to the Google remote account does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

2020-12-04 Thread Launchpad Bug Tracker 
** Merge proposal linked:
   
https://code.launchpad.net/~bryce/ubuntu/+source/docker.io/+git/docker.io/+merge/394913

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

2020-12-04 Thread Launchpad Bug Tracker 
** Merge proposal linked:
   
https://code.launchpad.net/~bryce/ubuntu/+source/docker.io/+git/docker.io/+merge/394913

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364

Title:
  unattended-upgrade still restarts blacklisted daemons

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray 
I installed the version of apport from xenial-proposed and no longer
received a Traceback when running the test case.

Preparing to unpack .../python3-apport_2.20.1-0ubuntu2.28_all.deb ...
Unpacking python3-apport (2.20.1-0ubuntu2.28) over (2.20.1-0ubuntu2.27) ...
Preparing to unpack .../apport_2.20.1-0ubuntu2.28_all.deb ...
Unpacking apport (2.20.1-0ubuntu2.28) over (2.20.1-0ubuntu2.27) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for systemd (229-4ubuntu21.29) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Setting up python3-apport (2.20.1-0ubuntu2.28) ...
Setting up apport (2.20.1-0ubuntu2.28) ...
bdmurray@clean-xenial-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77b04320 in __read_nocancel () at 
../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) Saved corefile /tmp/tmplo7od5en/my.core
(gdb) ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: called for pid 2915, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: executable: /bin/cat 
(command line "/bin/cat")
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: wrote report 
/tmp/tmplo7od5en/_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
(gdb) --- post-processing /tmp/tmplo7od5en/_bin_cat.1000.crash


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray 
I installed the version of apport from bionic-proposed and no longer
received a Traceback when following the test case.

Setting up python3-apport (2.20.9-0ubuntu7.21) ...
Setting up apport (2.20.9-0ubuntu7.21) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.43) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
bdmurray@clean-bionic-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77af2151 in __GI___libc_read (fd=0, buf=0x77fc2000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:27
27  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmp1o0onv61/my.core
(gdb) ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: called for pid 2615, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: executable: /bin/cat 
(command line "/bin/cat")
ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: debug: session gdbus call: 
ERROR: apport (pid 2623) Fri Dec  4 15:42:11 2020: wrote report 
/tmp/tmp1o0onv61/_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
(gdb) --- post-processing /tmp/tmp1o0onv61/_bin_cat.1000.crash


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-04 Thread Matthew Ruffell 
Attached is a debdiff to revert the changes we made to adcli to restore
functionality to GSS-API.

** Patch added: "Debdiff for adcli on Bionic"
   
https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+attachment/5441133/+files/lp1906627_adcli_bionic.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1790202] Re: Ubuntu 16.04 on powerpc offered to upgrade to 18.04

2020-12-04 Thread Hayden Barnes 
/usr/lib/ubuntu-release-upgrader/check-new-release appears to lack any
architecture-awareness.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790202

Title:
  Ubuntu 16.04 on powerpc offered to upgrade to 18.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray 
I installed the version of apport from focal-proposed and no longer
received a Traceback when running the traceback.

Unpacking apport (2.20.11-0ubuntu27.14) over (2.20.11-0ubuntu27.12) ...
Setting up python3-apport (2.20.11-0ubuntu27.14) ...
Setting up apport (2.20.11-0ubuntu27.14) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (245.4-4ubuntu3.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
bdmurray@clean-focal-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...
(No debugging symbols found in cat)
(gdb) Starting program: /usr/bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77ed7142 in __GI___libc_read (fd=0, buf=0x77835000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:26
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmp3m7fnzeq/my.core
(gdb) ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: called for pid 3172, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: executable: /usr/bin/cat 
(command line "/usr/bin/cat")
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: debug: session gdbus call: 
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: wrote report 
/tmp/tmp3m7fnzeq/_usr_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
[Inferior 1 (process 3172) killed]
(gdb) --- post-processing /tmp/tmp3m7fnzeq/_usr_bin_cat.1000.crash


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray 
I installed the version of apport from groovy-proposed and there is no
longer a Traceback when running the test case.

Setting up python3-apport (2.20.11-0ubuntu50.3) ...
Setting up apport (2.20.11-0ubuntu50.3) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (246.6-1ubuntu1) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
bdmurray@clean-groovy-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...
(No debugging symbols found in cat)
(gdb) Starting program: /usr/bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77ed3cb2 in __GI___libc_read (fd=0, buf=0x77837000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:26
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmpehzet8ma/my.core
(gdb) ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: called for pid 3631, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: executable: /usr/bin/cat 
(command line "/usr/bin/cat")
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: debug: session gdbus call: 
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: wrote report 
/tmp/tmpehzet8ma/_usr_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
[Inferior 1 (process 3631) killed]
(gdb) --- post-processing /tmp/tmpehzet8ma/_usr_bin_cat.1000.crash


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906875] Re: Bionic update: upstream stable patchset 2020-12-04

2020-12-04 Thread Ian 
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906875

Title:
  Bionic update: upstream stable patchset 2020-12-04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906887] Re: 3rd level key options hidden in Tweaks if show-all-sources is true

2020-12-04 Thread Gunnar Hjalmarsson 
Originally reported at .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906887

Title:
  3rd level key options hidden in Tweaks if show-all-sources is true

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906887] [NEW] 3rd level key options hidden in Tweaks if show-all-sources is true

2020-12-04 Thread Gunnar Hjalmarsson 
Public bug reported:

Steps to reproduce:

* Enable show-all-sources

  gsettings set org.gnome.desktop.input-sources show-all-sources 'true'

* Open Tweaks and navigate to Keyboard & Mouse ->
  Additional Layout Options -> Key to choose the 3rd level

* Find that only two odd options are shown

I would have expected the lv3:* options to be shown, i.e.:

  grep lv3 /usr/share/X11/xkb/rules/base.lst

If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
the issue seems to be caused by some kind of incompatibility between
gnome-tweaks and xkb-data 2.29-2.

** Affects: gnome-tweaks (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal groovy hirsute

** Also affects: xkeyboard-config (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906887

Title:
  3rd level key options hidden in Tweaks if show-all-sources is true

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826266] Re: Nautilus no longer copies file path when a file is marked then copied

2020-12-04 Thread Gregory Kramida 
Currently, you can track the status of the MR for Nautilus for the fix
of this regression:
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573

The change in the gnome shell that was causing all this has already been 
reverted / altered here:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/634

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #634
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/634

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826266

Title:
  Nautilus no longer copies file path when a file is marked then copied

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848856] Re: zfs on root fails with grub syntax error with multidisks pools

2020-12-04 Thread piersh 
this problem still exists in 20.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848856

Title:
  zfs on root fails with grub syntax error with multidisks pools

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Autopkgtest regression report (apport/2.20.1-0ubuntu2.28)

2020-12-04 Thread Ubuntu SRU Bot 
All autopkgtests for the newly accepted apport (2.20.1-0ubuntu2.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.1-0ubuntu2.28 (i386, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#apport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Autopkgtest regression report (apport/2.20.9-0ubuntu7.21)

2020-12-04 Thread Ubuntu SRU Bot 
All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.21) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.9-0ubuntu7.21 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#apport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2020-12-04 Thread Tom 
I have the same issue.  On 20.04, pulse audio creates of the HDMI/DP
device on wake after sleep, and starts using it even though I previously
configured the earlier copy of itself to "Off" using pavucontrol.

This is particularly annoying because it the device is built into my
monitor, is crappy, and there is no way to physically turn off the
device.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888598

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2020-12-04 Thread Tom 
I have the same issue.  On 20.04, pulse audio creates of the HDMI/DP
device on wake after sleep, and starts using it even though I previously
configured the earlier copy of itself to "Off" using pavucontrol.

This is particularly annoying because it the device is built into my
monitor, is crappy, and there is no way to physically turn off the
device.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888598

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821251] Re: please add cnf support to debmirror

2020-12-04 Thread Valters Jansons 
> The bug linked in the changelog of the SRU is this one, not bug
#1906541.

Indeed, I am not sure of the proper formatting rules, considering this
was my first merge request followed by SRU request of upstream changes.
The upstream changelog included the details of the original owner along
with this LP# considering the fix originated here.

> The SRU template needs to be on this bug

How should this be handled as of now? By who?

> in general, we should not be opening separate bugs for an SRU

In this case, this bug ticket is marked for multiple packages. It seemed
more straight-forward to me for the individual changes to be split off
in a separate ticket for the SRU itself. Would, instead, multiple SRU
templates be expected on this ticket - one for each package? Or would
the SRU potentially change depending on the changes required in the
individual packages?

This process is fairly scary from the outside perspective as these real
life scenarios are not covered. Considering this bug has not been fixed
for one-and-a-half years, with a patch laying around, I was trying to
get the ball rolling. I do ask once again for actionable items as of
now, or clarity of whether something should be done whatsoever (as it
may instead be handled in other communication channels without
information visible to the 'outside world').

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821251

Title:
  please add cnf support to debmirror

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted

2020-12-04 Thread Gordon Lack 
>> Thanks, that's being discussed upstream on https://github.com/flatpak
/xdg-desktop-portal/issues/512

No, it's not, as that issue has been closed.

Note that I'm seeing this WITHOUT having flatpak installed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905623

Title:
  df: /run/user/1000/doc: Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-12-04 Thread Reinis 
Many thanks to @coiby for providing the #189 fix - works great on the
latest Manjaro 5.9.11-3 with the MSFT0001:00 04F3:3140 touchpad on
Lenovo Legion 5 15ARH. Just had to install linux59-headers beforehand.

Let me know if there is any way I can help with this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906744] Re: xdg-document-portal creates a mountpoint which produces an error report from df

2020-12-04 Thread Andrew Hayzen 
*** This bug is a duplicate of bug 1905623 ***
https://bugs.launchpad.net/bugs/1905623

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

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

** This bug has been marked a duplicate of bug 1905623
   df: /run/user/1000/doc: Operation not permitted

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906744

Title:
  xdg-document-portal creates a mountpoint which produces an error
  report from df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1906744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1906107] Re: "unexpectedly disconnected from host boot status daemon" under high memory load

2020-12-04 Thread Bartłomiej Żogała 
Seems like long journey, please dont close the ticket as I will need few
days to confirm stability for each iteration

pt., 4 gru 2020, 07:25 użytkownik Kai-Heng Feng <1906...@bugs.launchpad.net>
napisał:

> Would it be possible for you to do a reverse kernel bisection?
>
> First, find the first -rc kernel works and the last -rc kernel doesn’t
> work from http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> Then,
> $ sudo apt build-dep linux
> $ git clone git://
> git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> $ cd linux
> $ git bisect start
> $ git bisect new $(the working version you found)
> $ git bisect old $(the non-working version found)
> $ make localmodconfig
> $ make -j`nproc` deb-pkg
> Install the newly built kernel, then reboot with it.
> If it doesn’t work,
> $ git bisect old
> Otherwise,
> $ git bisect new
> Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the
> issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1906107
>
> Title:
>   "unexpectedly disconnected from host boot status daemon" under high
>   memory load
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906107/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906107

Title:
  "unexpectedly disconnected from host boot status daemon" under high
  memory load

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901906] Re: amd64 images should have correct set of bootloaders installed

2020-12-04 Thread Launchpad Bug Tracker 
** Merge proposal linked:
   
https://code.launchpad.net/~powersj/livecd-rootfs/+git/livecd-rootfs-1/+merge/394910

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901906

Title:
  amd64 images should have correct set of bootloaders installed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small

2020-12-04 Thread Pat Viafore 
Version 2.525.48 of livecd-rootfs has fixed this issue.

Test case:
Built a box with the version of livecd-rootfs

vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name bionic-test
vagrant init bionic-test
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk size of drive mounted at / and observe that the disk is ~ 40G

To confirm that this won't break users upgrading to this box, but with <
40G disks, I checked the size of the VMDK backing the box. It was listed
at 1.1G. I created a 15G file with `dd if=/dev/urandom of=filename
bs=1024 count=15M` I was able to observe the VMDK growing by 15G.

So if a user were to have a 10G box fully allocated, and then upgrade to
the new box built with the latest version of livecd-rootfs, the user
would not be impacted until they tried to fill up the 40G.


** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596

Title:
  Xenial & bionic vagrant box disk size is too small

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906881] [NEW] mdadm --export --detail format incorrect

2020-12-04 Thread Chad Yates 
Public bug reported:

The mdadm --export --detail command creates environment variable
name/value pairs suitable to import into a scripts environment.  The
format of these has changed, and the change looks to be a bug.

Previously (prior to mdadm V4.1) the command would output in the following 
format:
MD_LEVEL=raid1
MD_DEVICES=2
MD_METADATA=1.2
MD_UUID=
MD_NAME=
MD_DEVICE_sdb_ROLE=0
MD_DEVICE_sdb_DEV=/dev/sdb

Now (mdadm V4.1) the command outputs in the following format:
MD_LEVEL=raid1
MD_DEVICES=2
MD_METADATA=1.2
MD_UUID=
MD_NAME=
MD_DEVICE_ev_sdb_ROLE=0
MD_DEVICE_ev_sdb_DEV=/dev/sdb

Note the differences in the the MD_DEVICE__ROLE and
MD_DEVICE__DEV variables where an extra "ev" string has been
included.

The "ev" string is added for all ROLE/DEV variables when multiple disks
are included in the RAID.

As this form of the --detail command is made as a consistent API
mechanism for scripts to use, it is important that it maintain correct
and consistent behavior.

I am using Ubuntu (20.04.1 LTS) along with mdadm (4.1-5ubuntu1.2).

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906881

Title:
  mdadm --export --detail format incorrect

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-04 Thread Brian Murray 
** Patch removed: "lp1906877-focal.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+attachment/5441131/+files/lp1906877-focal.patch

** Patch added: "lp1906877-focal.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+attachment/5441132/+files/lp1906877-focal.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906877

Title:
  diagnostics panel can leave automatic crash reporting enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906078] Re: Whoopsie sends bug reports automatically without consent

2020-12-04 Thread Brian Murray 
Do you happen to have the apport-noui package installed?

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906078

Title:
  Whoopsie sends bug reports automatically without consent

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Please test proposed package

2020-12-04 Thread Steve Langasek 
Hello Brian, or anyone else affected,

Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.28 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-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. 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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Please test proposed package

2020-12-04 Thread Steve Langasek 
Hello Brian, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.21 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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: apport (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Please test proposed package

2020-12-04 Thread Steve Langasek 
Hello Brian, or anyone else affected,

Accepted apport into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu50.3 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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: apport (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Steve Langasek 
Hello Brian, or anyone else affected,

Accepted apport into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.14 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: apport (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

** Changed in: apport (Ubuntu Groovy)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906565

Title:
  traceback when running apport as non-root user

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901609] Please test proposed package

2020-12-04 Thread Steve Langasek 
Hello Sandro, or anyone else affected,

Accepted signon into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901609

Title:
  signond causes qprocess crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901609] Re: signond causes qprocess crash

2020-12-04 Thread Steve Langasek 
Hello Sandro, or anyone else affected,

Accepted signon into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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: signon (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

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

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901609

Title:
  signond causes qprocess crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821251] Re: please add cnf support to debmirror

2020-12-04 Thread Steve Langasek 
> This was handled as a merge in #1892110 and is being handled as an SRU
> in #1906541 with the patch provided in that SRU ticket including
> further upstream commits.

The bug linked in the changelog of the SRU is this one, not bug
#1906541.  The SRU template needs to be on this bug (and, in general, we
should not be opening separate bugs for an SRU).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821251

Title:
  please add cnf support to debmirror

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-04 Thread Brian Murray 
This debdiff fixes it for Ubuntu 20.04 LTS and patches for other
releases should look the same.

** Patch added: "lp1906877-focal.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+attachment/5441131/+files/lp1906877-focal.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906877

Title:
  diagnostics panel can leave automatic crash reporting enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics

2020-12-04 Thread Steve Langasek 
Reviewing the nvidia-prime upload in the queue, I do not understand the
rationale for this SRU change.  The changelog states that we are
removing "obsolete udev rules during upgrade".  However, this means that
the udev files on disk will only removed when upgrading *from* this
package version; so users installing this SRU will still have those
files on disk.  If your intent is to have them removed upon installation
of *this* package version, then the removal should happen in the
postinst, not in the postrm.

It would be helpful if you would lay out in this bug what your intent is
with this change.

** Changed in: nvidia-prime (Ubuntu Groovy)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904583

Title:
  SRU: Backport the latest developments on drivers detection and hybrid
  graphics

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906877] [NEW] diagnostics panel can leave automatic crash reporting enabled

2020-12-04 Thread Brian Murray 
Public bug reported:

If one selects "Automatic" in the "Send error reports to Canonical"
portion of "Problem Reporting" the file /var/lib/apport/autoreport is
created. However, if you later switch to "Never" the file is not removed
but the panel continues to show "Never".

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  4 12:38:37 2020
InstallationDate: Installed on 2016-01-22 (1778 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gnome-control-center (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: gnome-control-center (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: gnome-control-center (Ubuntu Groovy)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

** Also affects: gnome-control-center (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906877

Title:
  diagnostics panel can leave automatic crash reporting enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882432] Re: Can't open OpenArena on Xubuntu 20.04

2020-12-04 Thread Matthias Fenner 
And why does this not get fixed in the package to make OA work out of
the box ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882432

Title:
  Can't open OpenArena on Xubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904640] Re: [SRU] [groovy] New upstream microrelease flatpak 1.8.3

2020-12-04 Thread Steve Langasek 
The upload in the queue is a binary sync from a ppa whose configuration
we have no visibility on (https://launchpad.net/~ahayzen/+archive/ubuntu
/flatpak-manual-uploads-1-8-3-clean-1-groovy).  In fact, the ppa's
config is definitely not what we expect for one that is used for
binaries that will be copied to the Ubuntu archive, because it has built
only on amd64 and not on any other archs.  So on this basis I'm
rejecting the upload; if you're going to sync a package to the queue
from a ppa, please make it a source-only sync.

This is also a package with no approved micro-release exception on
record, and there is no mention of what bugs are being resolved that are
important enough to justify an SRU.  More detail is needed here before
this SRU should proceed.

** Changed in: flatpak (Ubuntu Groovy)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904640

Title:
  [SRU] [groovy] New upstream microrelease flatpak 1.8.3

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906875] Re: Bionic update: upstream stable patchset 2020-12-04

2020-12-04 Thread Kamal Mostafa 
** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2020-12-04
  
-upstream stable patchset 2020-12-04
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.206, v4.19.157,
+ v4.14.207, v4.19.158
+ 
+    from git://git.kernel.org/
+ 
+ UBUNTU: upstream stable to v4.14.206, v4.19.157
+ regulator: defer probe when trying to get voltage from unresolved supply
+ ring-buffer: Fix recursion protection transitions between interrupt context
+ time: Prevent undefined behaviour in timespec64_to_ns()
+ nbd: don't update block size after device is started
+ btrfs: sysfs: init devices outside of the chunk_mutex
+ btrfs: reschedule when cloning lots of extents
+ genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
+ hv_balloon: disable warning when floor reached
+ net: xfrm: fix a race condition during allocing spi
+ perf tools: Add missing swap for ino_generation
+ ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
+ can: rx-offload: don't call kfree_skb() from IRQ context
+ can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context
+ can: dev: __can_get_echo_skb(): fix real payload length return value for RTR 
frames
+ can: can_create_echo_skb(): fix echo skb generation: always use skb_clone()
+ can: peak_usb: add range checking in decode operations
+ can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
+ can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback is 
on
+ xfs: flush new eof page on truncate to avoid post-eof corruption
+ Btrfs: fix missing error return if writeback for extent buffer never started
+ ath9k_htc: Use appropriate rs_datalen type
+ usb: gadget: goku_udc: fix potential crashes in probe
+ gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
+ gfs2: Add missing truncate_inode_pages_final for sd_aspace
+ gfs2: check for live vs. read-only file system in gfs2_fitrim
+ scsi: hpsa: Fix memory leak in hpsa_init_one()
+ drm/amdgpu: perform srbm soft reset always on SDMA resume
+ mac80211: fix use of skb payload instead of header
+ cfg80211: regulatory: Fix inconsistent format argument
+ scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
+ iommu/amd: Increase interrupt remapping table limit to 512 entries
+ pinctrl: intel: Set default bias in case no particular value given
+ ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
+ pinctrl: aspeed: Fix GPI only function problem.
+ nbd: fix a block_device refcount leak in nbd_release
+ xfs: fix flags argument to rmap lookup when converting shared file rmaps
+ xfs: fix rmap key and record comparison functions
+ xfs: fix a missing unlock on error in xfs_fs_map_blocks
+ of/address: Fix of_node memory leak in of_dma_is_coherent
+ cosa: Add missing kfree in error path of cosa_write
+ perf: Fix get_recursion_context()
+ ext4: correctly report "not supported" for {usr,grp}jquota when !CONFIG_QUOTA
+ ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
+ thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
+ uio: Fix use-after-free in uio_unregister_device()
+ usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
+ mei: protect mei_cl_mtu from null dereference
+ futex: Don't enable IRQs unconditionally in put_pi_state()
+ ocfs2: initialize ip_next_orphan
+ selinux: Fix error return code in sel_ib_pkey_sid_slow()
+ don't dump the threads that had been already exiting when zapped.
+ drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
+ pinctrl: amd: use higher precision for 512 RtcClk
+ pinctrl: amd: fix incorrect way to disable debounce filter
+ swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
+ IPv6: Set SIT tunnel hard_header_len to zero
+ net/af_iucv: fix null pointer dereference on shutdown
+ net/x25: Fix null-ptr-deref in x25_connect
+ vrf: Fix fast path output packet handling with async Netfilter rules
+ r8169: fix potential skb double free in an

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

2020-12-04 Thread Alexander Selyutin 
I have similar issues - suddenly closed installation. Asrock z370
samsung 860 evo if it matters

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8

2020-12-04 Thread Dan Streetman 
This also is blocking migration of upstream systemd CI from bionic to focal (on 
s390x), as the system will hang at boot due to this problem when using upstream 
systemd code on focal with the latest 5.4 ubuntu kernel. Test systemd build is 
available at:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd-focal-ci

Installing that systemd package (without the patched kernel build from
that ppa) will cause systemd to hang when restarting any service and
will hang the boot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895132

Title:
  s390x broken with unknown syscall number on kernels < 5.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906875] [NEW] Bionic update: upstream stable patchset 2020-12-04

2020-12-04 Thread Kamal Mostafa 
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2020-12-04

Ported from the following upstream stable releases:
v4.14.206, v4.19.157,
v4.14.207, v4.19.158

   from git://git.kernel.org/

UBUNTU: upstream stable to v4.14.206, v4.19.157
regulator: defer probe when trying to get voltage from unresolved supply
ring-buffer: Fix recursion protection transitions between interrupt context
time: Prevent undefined behaviour in timespec64_to_ns()
nbd: don't update block size after device is started
btrfs: sysfs: init devices outside of the chunk_mutex
btrfs: reschedule when cloning lots of extents
genirq: Let GENERIC_IRQ_IPI select IRQ_DOMAIN_HIERARCHY
hv_balloon: disable warning when floor reached
net: xfrm: fix a race condition during allocing spi
perf tools: Add missing swap for ino_generation
ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link()
can: rx-offload: don't call kfree_skb() from IRQ context
can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context
can: dev: __can_get_echo_skb(): fix real payload length return value for RTR 
frames
can: can_create_echo_skb(): fix echo skb generation: always use skb_clone()
can: peak_usb: add range checking in decode operations
can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping
can: peak_canfd: pucan_handle_can_rx(): fix echo management when loopback is on
xfs: flush new eof page on truncate to avoid post-eof corruption
Btrfs: fix missing error return if writeback for extent buffer never started
ath9k_htc: Use appropriate rs_datalen type
usb: gadget: goku_udc: fix potential crashes in probe
gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free
gfs2: Add missing truncate_inode_pages_final for sd_aspace
gfs2: check for live vs. read-only file system in gfs2_fitrim
scsi: hpsa: Fix memory leak in hpsa_init_one()
drm/amdgpu: perform srbm soft reset always on SDMA resume
mac80211: fix use of skb payload instead of header
cfg80211: regulatory: Fix inconsistent format argument
scsi: scsi_dh_alua: Avoid crash during alua_bus_detach()
iommu/amd: Increase interrupt remapping table limit to 512 entries
pinctrl: intel: Set default bias in case no particular value given
ARM: 9019/1: kprobes: Avoid fortify_panic() when copying optprobe template
pinctrl: aspeed: Fix GPI only function problem.
nbd: fix a block_device refcount leak in nbd_release
xfs: fix flags argument to rmap lookup when converting shared file rmaps
xfs: fix rmap key and record comparison functions
xfs: fix a missing unlock on error in xfs_fs_map_blocks
of/address: Fix of_node memory leak in of_dma_is_coherent
cosa: Add missing kfree in error path of cosa_write
perf: Fix get_recursion_context()
ext4: correctly report "not supported" for {usr,grp}jquota when !CONFIG_QUOTA
ext4: unlock xattr_sem properly in ext4_inline_data_truncate()
thunderbolt: Add the missed ida_simple_remove() in ring_request_msix()
uio: Fix use-after-free in uio_unregister_device()
usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode
mei: protect mei_cl_mtu from null dereference
futex: Don't enable IRQs unconditionally in put_pi_state()
ocfs2: initialize ip_next_orphan
selinux: Fix error return code in sel_ib_pkey_sid_slow()
don't dump the threads that had been already exiting when zapped.
drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[]
pinctrl: amd: use higher precision for 512 RtcClk
pinctrl: amd: fix incorrect way to disable debounce filter
swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb"
IPv6: Set SIT tunnel hard_header_len to zero
net/af_iucv: fix null pointer dereference on shutdown
net/x25: Fix null-ptr-deref in x25_connect
vrf: Fix fast path output packet handling with async Netfilter rules
r8169: fix potential skb double free in an error path
net: Update window_clamp if SOCK_RCVBUF is set
random32: make prandom_u32() output unpredictable
x86/speculation: Allow IBPB to be conditionally enabled on CPUs with always-on 
STIBP
perf/core: Fix bad use of igrab()
perf/core: Fix crash when using HW tracing kernel filters
perf/core: Fix a memory leak in perf_event_parse_addr_filter()
Revert "kernel/reboot.c: convert simple_strtoul to kstrtoint"
reboot: fix overflow parsing reboot cpu number
Convert trailing spaces and periods in path components
xfs: fix scrub flagging rtinherit even if there is no rt device
drm/amd/pm: perform SMC reset on suspend/hibernation
drm/amd/pm: do not use ixFEATURE_STATUS for checking smc running
s390/smp: move

[Bug 1906725] Re: [SRU] ceph 15.2.7

2020-12-04 Thread Steve Langasek 
Hello Corey, or anyone else affected,

Accepted ceph into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ceph/15.2.7-0ubuntu0.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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: ceph (Ubuntu Groovy)
   Status: Triaged => Fix Committed

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

** Changed in: ceph (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906725

Title:
  [SRU] ceph 15.2.7

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906725] Please test proposed package

2020-12-04 Thread Steve Langasek 
Hello Corey, or anyone else affected,

Accepted ceph into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ceph/15.2.7-0ubuntu0.20.04.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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906725

Title:
  [SRU] ceph 15.2.7

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821251] Re: please add cnf support to debmirror

2020-12-04 Thread Valters Jansons 
This was handled as a merge in #1892110 and is being handled as an SRU
in #1906541 with the patch provided in that SRU ticket including further
upstream commits.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821251

Title:
  please add cnf support to debmirror

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   >