[Bug 1927802] [NEW] ALSA: cannot set period size to 1024 frames for capture with sofhdadsp [sof-hda-dsp] Instead buffer sizes of 1008, 240, 120 work

2021-05-07 Thread Andrew Bailey
Public bug reported:

This was first reported in Bug #1872244 by John Smith on 2020-04-11

That bug report was converted into a question: question #692397: I
reported this on that thread however have heard no response.

However, I consider it to be a bug as it is not possible to configure
the standard power of 2 buffer sizes.

Instead buffer sizes of 1008, 240, 120 work.

The man page states that they should be powers of 2, and most jack audio
software fails to work properly.


My card is a

card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0

uname -a
Linux rtx 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

All software has been updated to the latest versions.

apt-cache policy jackd
jackd:
  Installed: 5+nmu1
  Candidate: 5+nmu1
  Version table:
 *** 5+nmu1 500
500 http://co.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://co.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status


With the default configuration

jackd -R -d alsa -d hw:1,0
...
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel

As reported jackd starts with a buffer size of 1008, a non standard, non
power of 2

jackd -R -d alsa -d hw:1,0 -p 1008

creating alsa driver ... hw:1,0|hw:1,0|1008|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1008 frames (21.0 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 24bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian
ALSA: use 2 periods for playback

I consider this a bug as the manual page for jackd states

-p, --period int

Specify the number of frames between JACK process() calls. This value
must be a power of 2, and the default is 1024.

And the current situation is that the only way jackd starts is with a
non power of 2.

Also buffer sizes of 240, 120 works

jackd -R -d alsa -d hw:1,0 -p 240

creating alsa driver ... hw:1,0|hw:1,0|240|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 240 frames (5.0 ms), buffer = 2 periods

jackd -R -d alsa -d hw:1,0 -p 120

creating alsa driver ... hw:1,0|hw:1,0|120|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 120 frames (2.5 ms), buffer = 2 periods

FYI a buffer size of 48 also works however I get another message (maybe
because I am not running with a low latency kernel ... yet)

Please see attachment for details.

** Affects: jackd-defaults (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "jack_buffer_bug.txt"
   
https://bugs.launchpad.net/bugs/1927802/+attachment/5495609/+files/jack_buffer_bug.txt

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

Title:
  ALSA: cannot set period size to 1024 frames for capture with sofhdadsp
  [sof-hda-dsp]   Instead buffer sizes of 1008, 240, 120 work

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

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

[Bug 1918482] Re: Update for CVE-2021-21381

2021-05-06 Thread Andrew Hayzen
I've also done some exploratory testing of .desktop icon related tests
from the test plan on a Bionic VM and things are working normally.

$ apt policy flatpak
flatpak:
  Installed: 1.0.9-0ubuntu0.3
  Candidate: 1.0.9-0ubuntu0.3
  Version table:
 *** 1.0.9-0ubuntu0.3 500
500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu 
bionic/main amd64 Packages
100 /var/lib/dpkg/status
 1.0.9-0ubuntu0.2 500
500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
 0.11.3-3 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

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

Title:
  Update for CVE-2021-21381

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

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

[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)

2021-05-06 Thread Andrew Moore
I agree with Aaron and Daniel. I have a custom MOTD generation script
that uses the output of updater-notifier `head -qn 2 /var/lib/update-
notifier/updates-available`. Not having any text in that file if there
are no updates available breaks the layout of the MOTD output.

Regardless of my custom setup, having the blank lines in the default
MOTD generated by `/etc/motd.d/90-updates-available` does make me think
something is broken. It's nice to have the validation of "0 packages can
be updated", IMO.

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

Title:
  Empty MOTD on up-to-date systems (includes fix)

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

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

[Bug 1927064] [NEW] Bluetooth toggle not working in Ubuntu 21.04

2021-05-04 Thread andrew robinson
Public bug reported:

After updating my OS from 20.10 to 21.04 the Bluetooth service remains
turned off even when I turn the toggle switch on.

The toggle is not working, neither from the top bar dropdown menu nor
from the settings window. Switching on the toggle did not have any
effect.

I have tried using these commands in the terminal:

sudo modprobe -r btusb
sudo modprobe btusb

They worked once, then when I toggle off and toggle on bluetooth it
remains turned off. I have restart the system for the commands to work
again

I also tried from the terminal:

sudo systemctl restart Bluetooth

Again it did restart the bluetooth service but if I toggle off and then
on again bluetooth service remains off. As before I have to restart the
system for the command to work.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-16-generic 5.11.0-16.17
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  andrew 1376 F pulseaudio
 /dev/snd/controlC0:  andrew 1376 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May  4 09:37:29 2021
InstallationDate: Installed on 2021-04-15 (18 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Acer Aspire E5-572G
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=6b9d5149-b57c-405b-802b-9e82a0fe23e3 ro quiet splash 
resume=UUID=69d3cfd8-3a1a-4a9e-b158-4c66cfe64a1a vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-16-generic N/A
 linux-backports-modules-5.11.0-16-generic  N/A
 linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-04-22 (11 days ago)
dmi.bios.date: 12/17/2014
dmi.bios.release: 1.3
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.03
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HWS
dmi.board.vendor: Acer
dmi.board.version: V1.03
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2014:br1.3:efr1.3:svnAcer:pnAspireE5-572G:pvrV1.03:rvnAcer:rnEA50_HWS:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: SharkBay System
dmi.product.name: Aspire E5-572G
dmi.product.sku: Aspire E5-572G_0922_V1.03
dmi.product.version: V1.03
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug hirsute wayland-session

** Attachment added: "bluetoot-toogle-1r.png"
   
https://bugs.launchpad.net/bugs/1927064/+attachment/5494634/+files/bluetoot-toogle-1r.png

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

Title:
  Bluetooth toggle not working in Ubuntu 21.04

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

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

[Bug 1926856] [NEW] Dismissing reminder for recurring meeting removes from all instances

2021-05-01 Thread Andrew Schepler
Public bug reported:

See upstream bug report https://gitlab.gnome.org/GNOME/evolution-
ews/-/issues/144 . It is reported as fixed in Evolution 3.40.

Using the Gnome Evolution email and calendar client with an Exchange
account. When a reminder comes up for an instance of a recurring meeting
which was added from an Exchange invite email, pressing the "Dismiss"
button will remove reminders from all instances of that meeting, so that
reminders do not appear for future instances.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evolution-ews 3.36.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May  1 18:01:17 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution-ews
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-ews (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/1926856

Title:
  Dismissing reminder for recurring meeting removes from all instances

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-29 Thread Andrew Taylor
Installed and booted into the newly supplied kernel:

root@jenkins-lon02-02-general-swarm-node-03:~# dpkg -l | grep linux | grep 144
ii  linux-image-unsigned-4.15.0-144-generic 4.15.0-144.148~LP1926081.2  
amd64Linux kernel image for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-4.15.0-144-generic4.15.0-144.148~LP1926081.2  
amd64Linux kernel extra modules for version 4.15.0 on 64 
bit x86 SMP

root@jenkins-lon02-02-general-swarm-node-03:~# uname -r
4.15.0-144-generic

root@jenkins-lon02-02-general-swarm-node-03:~# uptime
 08:06:22 up 19 min,  1 user,  load average: 0.74, 0.31, 0.21

root@jenkins-lon02-02-general-swarm-node-03:~# ls -l /boot/
total 201933
-rw-r--r-- 1 root root  1537161 Jul 17  2018 abi-4.15.0-29-generic
-rw-r--r-- 1 root root   217414 Mar 24 12:47 config-4.15.0-141-generic
-rw-r--r-- 1 root root   217426 Apr 28 09:46 config-4.15.0-144-generic
-rw-r--r-- 1 root root   216807 Jul 17  2018 config-4.15.0-29-generic
-rw-r--r-- 1 root root   237757 Apr 12 17:02 config-5.4.0-72-generic
drwxr-xr-x 5 root root 1024 Apr 29 04:06 grub
-rw-r--r-- 1 root root 43066106 Apr 15 09:40 initrd.img-4.15.0-141-generic
-rw-r--r-- 1 root root 24589989 Apr 29 04:06 initrd.img-4.15.0-144-generic
-rw-r--r-- 1 root root 39975786 Apr 15 08:14 initrd.img-4.15.0-29-generic
-rw-r--r-- 1 root root 44490420 Apr 27 04:50 initrd.img-5.4.0-72-generic
drwx-- 2 root root12288 Apr 15 07:55 lost+found
-rw-r--r-- 1 root root0 Jul 17  2018 retpoline-4.15.0-29-generic
-rw--- 1 root root  4081420 Mar 24 12:47 System.map-4.15.0-141-generic
-rw--- 1 root root  4081469 Apr 28 09:46 System.map-4.15.0-144-generic
-rw--- 1 root root  4040379 Jul 17  2018 System.map-4.15.0-29-generic
-rw--- 1 root root  4585968 Apr 12 17:02 System.map-5.4.0-72-generic
-rw--- 1 root root  8445600 Mar 24 11:00 vmlinuz-4.15.0-141-generic
-rw--- 1 root root  8447776 Apr 28 09:46 vmlinuz-4.15.0-144-generic
-rw--- 1 root root  8257272 Jul 17  2018 vmlinuz-4.15.0-29-generic
-rw--- 1 root root  9445632 Apr 12 17:15 vmlinuz-5.4.0-72-generic

I've run my test through 5 times, and there has been no observed leak in
the writeback queue/memory used, so everything still looks good from my
side.

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-29 Thread Andrew Taylor
Tim,

I'll cordon off the machine we've been using again and run some tests
with this new kernel, hopefully I'll be able to do it today.

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-27 Thread Andrew Taylor
Awesome, 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/1926081

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-27 Thread Andrew Taylor
Good news on the custom -144 kernel you provided:

root@jenkins-lon02-02-general-swarm-node-03:~# uname -r
4.15.0-144-generic

root@jenkins-lon02-02-general-swarm-node-03:~# dpkg -l | grep 144
ii  linux-image-unsigned-4.15.0-144-generic 4.15.0-144.148~LP1926081.1  
amd64Linux kernel image for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-4.15.0-144-generic4.15.0-144.148~LP1926081.1  
amd64Linux kernel extra modules for version 4.15.0 on 64 
bit x86 SMP

root@jenkins-lon02-02-general-swarm-node-03:~# uptime
 08:53:37 up 48 min,  1 user,  load average: 1.22, 3.54, 3.05

root@jenkins-lon02-02-general-swarm-node-03:~# grep "writeback" /proc/vmstat
nr_writeback 0
nr_writeback_temp 0

I've run through my testcase 3 times on this new kernel and I've not
seen any permanent increase in the `nr_writeback` value, it always
returns to zero, which is great.

So from my end, this looks really good - is there anything else you'd
like me to do or test, or is this good enough to pull them in for the
-144 update?

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-27 Thread Andrew Taylor
Thank you both,

I'll give that kernel a go now.

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-27 Thread Andrew Taylor
So, good news.

I pulled in the ubuntu kernel sources and applied the main patch I had
previously identified
(https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe).
Looking at the other patch
(https://github.com/torvalds/linux/commit/e27be240df53), that seems to
be related to the accuracy of returned statistics which is not something
that my testcase is going to show up.

I built a version of the 4.15.0-142 kernel with patch, and booted back
into it, and with two iterations of my testcase my `nr_writeback` value
has ended up on zero - which is excellent news. From previous runs it
has never failed to leak, so this looks good to me. I will run it some
more, but it is safe to say I am pretty happy at this point.

To that end, I believe that
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
"mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats" does
indeed fix this issue and the symptoms I have reported above.

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-27 Thread Andrew Taylor
Guilherme, thank you for your kind words :)

I have been trying to reproduce this bug on several other systems that I
have access to in our cloud account, but I have been unable to reproduce
it on a VM (either with SAN or local SSD storage). The main set of
servers where this has been seen by us are bare-metal servers with a
RAID card backed by SSDs - it's possible that a combination of the
resources available on the machine (CPU, RAM, disk IO) cause this bug to
be more reproducible with my basic testcase.

I have taken a server out of production and rebooted it into the 4.15
kernel (4.15.0-141-generic) where the issue is able to be seen.

I confirmed my testcase still reproduces the issue here, and it does -
nr_writeback is currently stuck at 2641 after one iteration.

I have supplied the apport collected information from that server, which
is now attached to this issue.


This is my first bug report on Launchpad, so I am as yet unfamiliar with the 
process of testing the potential patches I need. Are you suggesting that I 
follow the process to rebuild the kernel 
(https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel) including the patches you 
have mentioned?

Assuming that is the correct course of action I'll attempt to follow the
instructions and do that, and report back.

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] UdevDb.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1926081/+attachment/5492737/+files/UdevDb.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] ProcModules.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1926081/+attachment/5492736/+files/ProcModules.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] ProcInterrupts.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1926081/+attachment/5492735/+files/ProcInterrupts.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] ProcEnviron.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1926081/+attachment/5492734/+files/ProcEnviron.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] ProcCpuinfoMinimal.txt

2021-04-27 Thread Andrew Taylor
apport information

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

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Lsusb.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1926081/+attachment/5492731/+files/Lsusb.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Lspci.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1926081/+attachment/5492730/+files/Lspci.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] CurrentDmesg.txt

2021-04-27 Thread Andrew Taylor
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1926081/+attachment/5492729/+files/CurrentDmesg.txt

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-27 Thread Andrew Taylor
apport information

** Tags added: apport-collected

** Description changed:

  
  Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above contain a 
memory leak due to the inclusion of patch from the upstream kernel, but not the 
fix for that patch which was released later.
  
  This issue manifests itself as an increasing amount of memory used by
  the writeback queue, which never returns to zero. This can been seen
  either as the value of `nr_writeback` in /proc/vmstat, or the value of
  `Writeback` in /proc/meminfo.
  
  Ordinarily these values should be at or around zero, but on our servers
  we observe the `nr_writeback` value increasing to over 8 million, (32GB
  of memory), at which point it isn't long before the system IO slows to a
  crawl (tens of Kb/s). Our servers have 256GB of memory, and are
  performing many CI related activities - this issue appears to be related
  to concurrent writing to disk, and can be demonstrated with a simple
  testcase (see later).
  
  On our heavily used systems this memory leak can result in an unstable
  server after 2-3 days, requiring a reboot to fix it.
  
  After much investigation the issue appears to be because the patch "mm:
  memcontrol: fix excessive complexity in memory.stat reporting" was
  brought in to the 4.15.0-137 Ubuntu kernel (see
  https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of "
  Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
  however in the mainline kernel there was a follow up patch because this
  initial patch introduced concurrency issues. The patch "mm: memcontrol:
  fix NR_WRITEBACK leak in memcg and system stats" is required, and should
  be brought into the Ubuntu packaged kernel to fix the issues reported.
  
  The required patch is here:
  
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
  and was committed a few weeks after the original (broken) patch:
  
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
  
  I have checked the release notes for Ubuntu versions -137 to -143, and
  none include this second patch that should fix the issue. (I checked
  https://people.canonical.com/~kernel/info/kernel-version-map.html for
  all the kernel versions, and then visited each changelog page in turn,
  e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
  for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats").
  
  We do not observe this on the 5.4.0 kernel (supported HWE kernel on
  18.05.5), which includes this second patch. That kernel may also include
  other patches, so we do not know if any other fixes are also required,
  but the one we have linked above seems to definitely be needed, and
  seems to match our symptoms.
  
  Testcase:
  
  The following is enough to permanently increase the value of
  `nr_writeback` on our systems (by about 2000 during most executions):
  
  ```
  date
  grep nr_writeback /proc/vmstat
  mkdir -p /docker/testfiles/{1..5}
  
  seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
  seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
  seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
  seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
  seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
  
  wait $(jobs -p)
  grep nr_writeback /proc/vmstat
  date
  ```
  
  Subsequent iterations of the test raise it further, and on a system
  doing a lot of writing from a lot of different processes, it can rise
  quickly.
  
  System details:
  
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  
  Affected kernel: 4.15.0-137 onwards (current latest version tried was
  4.15.0-142)
  
  e.g.
  
  apt-cache policy linux-image-4.15.0-141-generic
  linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
   *** 4.15.0-141.145 500
  500 http://mirrors.service.networklayer.com/ubuntu 
bionic-updates/main amd64 Packages
  500 http://mirrors.service.networklayer.com/ubuntu 
bionic-security/main amd64 Packages
  100 /var/lib/dpkg/status
  
  According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies I
  should include additional information from the server, but at this stage
  we have upgraded all our affected systems to 5.4.0, and therefore the
  kernel versions do not match those with this issue.
  
  We likely have other servers used in other services that are not as
  heavily loaded that have not been as affected by this issue - and
  therefore and I may be able to get the equivalent diagnostics from there
  after confirming 

[Bug 1918482] Re: Update for CVE-2021-21381

2021-04-26 Thread Andrew Hayzen
@Steve Beattie, was there any progress on this or anything I can do to
help ? Or is it just stuck in a queue of items to be reviewed? :-)

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

Title:
  Update for CVE-2021-21381

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

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

[Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+

2021-04-25 Thread Andrew Taylor
I did not initially run the `apport-collect` command as the servers on
which I observed this bug have been upgraded to use the 5.4.0 kernel to
mitigate the issue (as mentioned in the initial report), therefore the
kernel related information may be misleading.

I will endeavour to find a server that is exhibiting this issue that
remains on an impacted kernel, however I cannot do so today, and given
that I have identified a required upstream patch I believe some progress
can be made with this bug without this information.

If an `apport-collect` command on a server that has been upgraded to the newer 
kernel is still useful, please let me know and I can see if I can generate the 
information there.
I will attempt to find a server that has not been upgraded, replicate the 
issue, and then will upload the required logs from that server.

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

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

Title:
  nr_writeback memory leak in kernel 4.15.0-137+

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

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

[Bug 1926081] [NEW] nr_writeback memory leak in kernel 4.15.0-137+

2021-04-25 Thread Andrew Taylor
Public bug reported:


Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above contain a 
memory leak due to the inclusion of patch from the upstream kernel, but not the 
fix for that patch which was released later.

This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.

Ordinarily these values should be at or around zero, but on our servers
we observe the `nr_writeback` value increasing to over 8 million, (32GB
of memory), at which point it isn't long before the system IO slows to a
crawl (tens of Kb/s). Our servers have 256GB of memory, and are
performing many CI related activities - this issue appears to be related
to concurrent writing to disk, and can be demonstrated with a simple
testcase (see later).

On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.

After much investigation the issue appears to be because the patch "mm:
memcontrol: fix excessive complexity in memory.stat reporting" was
brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of "
Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because this
initial patch introduced concurrency issues. The patch "mm: memcontrol:
fix NR_WRITEBACK leak in memcg and system stats" is required, and should
be brought into the Ubuntu packaged kernel to fix the issues reported.

The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da

I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats").

We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also include
other patches, so we do not know if any other fixes are also required,
but the one we have linked above seems to definitely be needed, and
seems to match our symptoms.

Testcase:

The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):

```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}

seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom 
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &

wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```

Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.

System details:

lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04

Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)

e.g.

apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
  Installed: 4.15.0-141.145
  Candidate: 4.15.0-141.145
  Version table:
 *** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu bionic-updates/main 
amd64 Packages
500 http://mirrors.service.networklayer.com/ubuntu bionic-security/main 
amd64 Packages
100 /var/lib/dpkg/status

According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies I
should include additional information from the server, but at this stage
we have upgraded all our affected systems to 5.4.0, and therefore the
kernel versions do not match those with this issue.

We likely have other servers used in other services that are not as
heavily loaded that have not been as affected by this issue - and
therefore and I may be able to get the equivalent diagnostics from there
after confirming that they demonstrate the same issue with my testcase

Workaround:

After several weeks narrowing this down, our only option was to upgrade
our servers to the 5.4 kernel, which is included as the HWE kernel in
18.04.5:

apt update && apt install 

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2021-04-24 Thread Andrew Bailey
Please can you look into this. It has been marked as Invalid, however,
it is not a support request as has been assumed.

My card is a

card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0

uname -a
Linux rtx 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

All software has been updated to the latest versions.


With the default configuration

jackd -R -d alsa -d hw:1,0
...
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel

As reported jackd starts with a buffer size of 1008, a non standard, non
power of 2

jackd -R -d alsa -d hw:1,0 -p 1008

creating alsa driver ... hw:1,0|hw:1,0|1008|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1008 frames (21.0 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 24bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian
ALSA: use 2 periods for playback

I consider this a bug as the manual page for jackd states

-p, --period int

Specify the number of frames between JACK process() calls.  This value
must be a power of 2, and the default  is  1024.

And the current situation is that the only way jackd starts is with a
non power of 2.

Also buffer sizes of 240, 120 works

jackd -R -d alsa -d hw:1,0 -p 240

creating alsa driver ... hw:1,0|hw:1,0|240|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 240 frames (5.0 ms), buffer = 2 periods

jackd -R -d alsa -d hw:1,0 -p 120

creating alsa driver ... hw:1,0|hw:1,0|120|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 120 frames (2.5 ms), buffer = 2 periods

FYI a buffer size of 48 also works however I get another message (maybe
because I am not running with a low latency kernel ... yet)


Please see attachment for details.


** Attachment added: "jack_buffer_bug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/jackd-defaults/+bug/1872244/+attachment/5491789/+files/jack_buffer_bug.txt

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

Title:
  Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1
  (7th gen)

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

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

[Bug 1917912] Re: Skip indexing s3fs

2021-04-18 Thread Andrew Gaul
Related to
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1918448.

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

Title:
  Skip indexing s3fs

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

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

[Bug 1001035] Re: lightdm uses a hardcoded path to .xsession-errors, please make it configurable

2021-04-17 Thread Andrew
Any update on this? I'd love to move xsession-errors file out of my SSD
to minimize writes.

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

Title:
  lightdm uses a hardcoded path to .xsession-errors, please make it
  configurable

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

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

[Bug 1879816] Re: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1

2021-04-10 Thread Andrew Ruthven
I pondered more on this issue this morning and decided to allow the
service to fail to start on installation and remove. This is now fixed
in 1.0.1-6.

** Changed in: mythtv-status (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/1879816

Title:
  package mythtv-status 1.0.1-1 failed to install/upgrade: installed
  mythtv-status package post-installation script subprocess returned
  error exit status 1

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

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

[Bug 1918482] Re: Update for CVE-2021-21381

2021-04-08 Thread Andrew Hayzen
Thanks for reviewing these updates!

I've done some exploratory testing of .desktop icon related tests from
the test plan on a Focal VM and things are working normally.

$ apt policy flatpak
flatpak:
  Installed: 1.6.5-0ubuntu0.3
  Candidate: 1.6.5-0ubuntu0.3
  Version table:
 *** 1.6.5-0ubuntu0.3 500
500 http://ppa.launchpad.net/ubuntu-security-proposed/ppa/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
 1.6.5-0ubuntu0.2 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages
 1.6.3-1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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

Title:
  Update for CVE-2021-21381

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

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

[Bug 706362] Re: update-motd.d script prevents updating motd

2021-04-08 Thread Andrew Ruthven
Ugh.

This evening I prepared a new package for Debian (1.0.1-2) which includes a 
patch for this:
http://git.etc.gen.nz/cgi-bin/gitweb.cgi?p=mythtv-status.git;a=commit;h=089616c32247d109dc735da56838a6a4bc5d12f8

I'll be releasing version 1.0.2 which will also include this soon.

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

Title:
  update-motd.d script prevents updating motd

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

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

[Bug 1879816] Re: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1

2021-04-08 Thread Andrew Ruthven
Hmm... I'm interested in hearing opinions here on how better to handle
this situation.

mythtv-status was unable to collect information from the mythtv-backend,
so it was a legitimate failure.

Should I be asking for the hostname to check during installation?

Treat failure as acceptable? (Which might hide the issue)

Something else?

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

Title:
  package mythtv-status 1.0.1-1 failed to install/upgrade: installed
  mythtv-status package post-installation script subprocess returned
  error exit status 1

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

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

[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

2021-04-06 Thread Andrew Robert
https://cdraustralia.org/ provided hassle-free professional CDR Writing
Services. I got my CDR professionally prepared on time. They offered me
a detailed questionnaire relevant to my projects and prepared the Career
Episodes Report and summary statements based on the information. Thanks
to your team member. Well-done!

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

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

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

[Bug 1922095] Re: usb-creator-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'isoinfo'

2021-04-02 Thread Andrew Enderson
Same issue with usb-creator-kde on kubuntu 21.04

 An unhandled exception occured:
 [Errno 2] No such file or directory: 'isoinfo'

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

Title:
  usb-creator-gtk crashed with FileNotFoundError in _execute_child():
  [Errno 2] No such file or directory: 'isoinfo'

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

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

[Bug 1915492] Re: ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout()

2021-03-31 Thread Andrew Hayzen
Upstream bug is here https://github.com/AyatanaIndicators/ayatana-
indicator-keyboard/issues/5

** Bug watch added: 
github.com/AyatanaIndicators/ayatana-indicator-keyboard/issues #5
   https://github.com/AyatanaIndicators/ayatana-indicator-keyboard/issues/5

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

Title:
  ayatana-indicator-keyboard-service crashed with SIGSEGV in
  keyboard_GetLayout()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-keyboard/+bug/1915492/+subscriptions

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

[Bug 1906535] Re: "Windows" Section/Setting Forces Window Button Placement To Left Side On Open

2021-03-27 Thread Andrew Hayzen
Reported a bug upstream with some analysis of the issue.
https://github.com/mate-desktop/mate-control-center/issues/640

** Bug watch added: github.com/mate-desktop/mate-control-center/issues #640
   https://github.com/mate-desktop/mate-control-center/issues/640

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

Title:
  "Windows" Section/Setting Forces Window Button Placement To Left Side
  On Open

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

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

[Bug 1920963] Re: Tried installing with ZFS, but two failures during format, I think.

2021-03-25 Thread Andrew Cochrane
I tried to install with ZFS again after rebooting.
It worked fine when making the first attempt when the target drive was not 
mounted.

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

Title:
  Tried installing with ZFS, but two failures during format, I think.

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

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

[Bug 1921135] [NEW] package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2021-03-24 Thread Andrew Whitehead
Public bug reported:

no further information

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar 18 10:34:46 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-01-23 (60 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

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

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

[Bug 1921136] [NEW] package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2021-03-24 Thread Andrew Whitehead
Public bug reported:

no further information

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.4
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 24 15:49:31 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-01-23 (60 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

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

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

[Bug 1920963] [NEW] Tried installing with ZFS, but two failures during format, I think.

2021-03-23 Thread Andrew Cochrane
Public bug reported:

Trying to install with zfs.
First attempt had drive mounted.
Second attempt with unmounted drive failed to format, maybe.
Third attempt failed after sending me time timezone selection. Then collected 
error report and brought me to the webpage.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 23 10:09:25 2021
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu

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

Title:
  Tried installing with ZFS, but two failures during format, I think.

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

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

[Bug 1920016] [NEW] Upgrade s3fs to 1.89

2021-03-18 Thread Andrew Gaul
Public bug reported:

Release notes:

https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.89

This release fixes a regression when writing objects larger than 10 GB
during periodic dirty data flush (on by default).  Is it possible to
include this in 21.04 or cherry pick the fix in a 1.88-3?

** Affects: s3fs-fuse (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/1920016

Title:
  Upgrade s3fs to 1.89

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

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

[Bug 1857073] Re: Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158 [ipmi_msghandler]

2021-03-18 Thread Andrew Cloke
I understand that there are no further f/w updates planned for these
ThunderX boards. Marking as "won't fix".

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

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

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

Title:
  Cavium ThunderX CN88XX Oops at smi_send.isra.4+0x80/0x158
  [ipmi_msghandler]

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

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

[Bug 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)

2021-03-15 Thread Andrew Cloke
** Changed in: kunpeng920/ubuntu-18.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920
   Status: Fix Committed => 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/1911376

Title:
  [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and
  advertise to userspace)

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

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

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-11 Thread Andrew Hayzen
Hirsute now contains 1.10.2-1 with the fix, so I am marking it as fixed
released.

** Changed in: flatpak (Ubuntu)
   Status: In Progress => Fix Released

** Description changed:

  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
  https://github.com/flatpak/flatpak/pull/4156
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859
+ https://security-tracker.debian.org/tracker/CVE-2021-21381
  
  [Impact]
  Versions in Ubuntu right now:
  Hirsute: 1.10.1-4
  Groovy: 1.8.2-1ubuntu0.1
  Focal: 1.6.5-0ubuntu0.2
  Bionic: 1.0.9-0ubuntu0.2
  
  Affected versions:
  >= 0.9.4
  
  Patched versions:
  >= 1.10.2
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all relevant
  architectures and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
  Sandbox escape via special tokens in .desktop file (flatpak#4146)
  
  Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature 
which can be used by an attacker to gain access to files that would not 
ordinarily be allowed by the app's permissions.
  Impact
  
  By putting the special tokens @@ and/or @@u in the Exec field of a
  Flatpak app's .desktop file, a malicious app publisher can trick flatpak
  into behaving as though the user had chosen to open a target file with
  their Flatpak app, which automatically makes that file available to the
  Flatpak app.
  
  A minimal solution is the first commit "Disallow @@ and @@U usage in desktop 
files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: 
Refuse to export .desktop files with suspicious uses of @@ tokens" are 
recommended, but not strictly required.
  Workarounds
  
  Avoid installing Flatpak apps from untrusted sources, or check the contents 
of the exported .desktop files in exports/share/applications/*.desktop 
(typically ~/.local/share/flatpak/exports/share/applications/*.desktop and 
/var/lib/flatpak/exports/share/applications/*.desktop) to make sure that 
literal filenames do not follow @@ or @@u.
  References
  
  Acknowledgements
  
  Thanks to @AntonLydike for reporting this issue, and @refi64 for
  providing the initial solution.

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-11 Thread Andrew Hayzen
This is now CVE-2021-21381, whoever comes to upload the debdiffs please
consider the following:

  * Please rename "- GHSA-xgh4-387p-hqpp" in the debian/changelog to "- 
CVE-2021-21381"
  * Please consider renaming the debian/patches from (for example) 
"GHSA-xgh4-387p-hqpp-1.patch" to "CVE-2021-21381-1.patch"

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

** Changed in: flatpak (Ubuntu Bionic)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

** Changed in: flatpak (Ubuntu Focal)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

** Changed in: flatpak (Ubuntu Groovy)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

** Changed in: flatpak (Ubuntu Bionic)
   Status: New => In Progress

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

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

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
** Description changed:

  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
  https://github.com/flatpak/flatpak/pull/4156
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859
  
  [Impact]
  Versions in Ubuntu right now:
  Hirsute: 1.10.1-4
  Groovy: 1.8.2-1ubuntu0.1
  Focal: 1.6.5-0ubuntu0.2
  Bionic: 1.0.9-0ubuntu0.2
  
  Affected versions:
  >= 0.9.4
  
  Patched versions:
  >= 1.10.2
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all relevant
  architectures and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
  Sandbox escape via special tokens in .desktop file (flatpak#4146)
  
  Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature 
which can be used by an attacker to gain access to files that would not 
ordinarily be allowed by the app's permissions.
  Impact
  
  By putting the special tokens @@ and/or @@u in the Exec field of a
  Flatpak app's .desktop file, a malicious app publisher can trick flatpak
  into behaving as though the user had chosen to open a target file with
  their Flatpak app, which automatically makes that file available to the
  Flatpak app.
  
  A minimal solution is the first commit "Disallow @@ and @@U usage in desktop 
files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: 
Refuse to export .desktop files with suspicious uses of @@ tokens" are 
recommended, but not strictly required.
  Workarounds
  
  Avoid installing Flatpak apps from untrusted sources, or check the contents 
of the exported .desktop files in exports/share/applications/*.desktop 
(typically ~/.local/share/flatpak/exports/share/applications/*.desktop and 
/var/lib/flatpak/exports/share/applications/*.desktop) to make sure that 
literal filenames do not follow @@ or @@u.
  References
  
  Acknowledgements
  
  Thanks to @AntonLydike for reporting this issue, and @refi64 for
  providing the initial solution.

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
If someone has the permissions could they add bionic, focal, and groovy
as affected series ?

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] Re: Placeholder for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
This is the bionic debdiff.

** Description changed:

- Patches and description coming soon ! I need this to generate a LP bug
- number :-)
+ [Links]
+ https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
+ https://github.com/flatpak/flatpak/pull/4156
+ 
+ [Impact]
+ Versions in Ubuntu right now:
+ Hirsute: 1.10.1-4
+ Groovy: 1.8.2-1ubuntu0.1
+ Focal: 1.6.5-0ubuntu0.2
+ Bionic: 1.0.9-0ubuntu0.2
+ 
+ Affected versions:
+ >= 0.9.4
+ 
+ Patched versions:
+ >= 1.10.2
+ 
+ [Test Case]
+ 
+ No test case has been mentioned yet, but in the patches there are
+ changes/additions to the unit tests.
+ 
+ [Regression Potential]
+ 
+ Flatpak has a test suite, which is run on build across all relevant
+ architectures and passes.
+ 
+ There is also a manual test plan
+ https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
+ 
+ Flatpak has autopkgtests enabled
+ http://autopkgtest.ubuntu.com/packages/f/flatpak .
+ 
+ Regression potential is low, and upstream is very responsive to any
+ issues raised.
+ 
+ [Other information]
+ 
+ Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature 
which can be used by an attacker to gain access to files that would not 
ordinarily be allowed by the app's permissions.
+ Impact
+ 
+ By putting the special tokens @@ and/or @@u in the Exec field of a
+ Flatpak app's .desktop file, a malicious app publisher can trick flatpak
+ into behaving as though the user had chosen to open a target file with
+ their Flatpak app, which automatically makes that file available to the
+ Flatpak app.
+ 
+ A minimal solution is the first commit "Disallow @@ and @@U usage in desktop 
files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: 
Refuse to export .desktop files with suspicious uses of @@ tokens" are 
recommended, but not strictly required.
+ Workarounds
+ 
+ Avoid installing Flatpak apps from untrusted sources, or check the contents 
of the exported .desktop files in exports/share/applications/*.desktop 
(typically ~/.local/share/flatpak/exports/share/applications/*.desktop and 
/var/lib/flatpak/exports/share/applications/*.desktop) to make sure that 
literal filenames do not follow @@ or @@u.
+ References
+ 
+ Acknowledgements
+ 
+ Thanks to @AntonLydike for reporting this issue, and @refi64 for
+ providing the initial solution.

** Summary changed:

- Placeholder for GHSA-xgh4-387p-hqpp
+ Update for GHSA-xgh4-387p-hqpp

** Description changed:

  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
  https://github.com/flatpak/flatpak/pull/4156
  
  [Impact]
  Versions in Ubuntu right now:
  Hirsute: 1.10.1-4
  Groovy: 1.8.2-1ubuntu0.1
  Focal: 1.6.5-0ubuntu0.2
  Bionic: 1.0.9-0ubuntu0.2
  
  Affected versions:
- >= 0.9.4
+ >= 0.9.4
  
  Patched versions:
- >= 1.10.2
+ >= 1.10.2
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all relevant
  architectures and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
+ Sandbox escape via special tokens in .desktop file (flatpak#4146)
+ 
  Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature 
which can be used by an attacker to gain access to files that would not 
ordinarily be allowed by the app's permissions.
  Impact
  
  By putting the special tokens @@ and/or @@u in the Exec field of a
  Flatpak app's .desktop file, a malicious app publisher can trick flatpak
  into behaving as though the user had chosen to open a target file with
  their Flatpak app, which automatically makes that file available to the
  Flatpak app.
  
  A minimal solution is the first commit "Disallow @@ and @@U usage in desktop 
files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: 
Refuse to export .desktop files with suspicious uses of @@ tokens" are 
recommended, but not strictly required.
  Workarounds
  
  Avoid installing Flatpak apps from untrusted sources, or check the contents 
of the exported .desktop files in exports/share/applications/*.desktop 
(typically ~/.local/share/flatpak/exports/share/applications/*.desktop and 
/var/lib/flatpak/exports/share/applications/*.desktop) to make sure that 
literal filenames do not follow @@ or @@u.
  References
  
  Acknowledgements
  
  Thanks to @AntonLydike for reporting this issue, and @refi64 for
  providing the initial solution.

** Information type changed from Public to Public Security

** Attachment added: "[bionic] 
flatpak_1.0.9-0ubuntu0.2_to_flatpak_1.0.9-0ubuntu0.3.debdiff.gz"
   

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
So we do not have a CVE yet, I believe one will be auto assigned via
github at some point (I don't know how long this takes :-) ).

I realised there is a typo in the bionic changelog "- GHSA-xgh4-387p-
hqpp-1" should be "- GHSA-xgh4-387p-hqpp".  But once a CVE is available
this line will need to be replaced anyway ?

For hirsute, 1.10.1-4 has the first commit from
https://github.com/flatpak/flatpak/pull/4156/commits  but 1.10.2-1 has
just been submitted to debian sid with the full fixes, so should be
syncing shortly ( https://tracker.debian.org/news/1235768/accepted-
flatpak-1102-1-source-into-unstable/ ).

I have not performed any deep testing yet, I have only built the bionic
and focal debdiffs in a PPA (I was surprised that the patches still
applied cleanly for bionic so wanted to check that, as the line numbers
are quite different).

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
This is the focal debdiff.

** Attachment added: "[focal] 
flatpak_1.6.5-0ubuntu0.2_to_flatpak_1.6.5-0ubuntu0.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+attachment/5475503/+files/flatpak_1.6.5-0ubuntu0.2_to_flatpak_1.6.5-0ubuntu0.3.debdiff.gz

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
This is the groovy debdiff.

** Attachment added: "[groovy] 
flatpak_1.8.2-1ubuntu0.1_to_flatpak_1.8.2-1ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+attachment/5475504/+files/flatpak_1.8.2-1ubuntu0.1_to_flatpak_1.8.2-1ubuntu0.2.debdiff.gz

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

Title:
  Update for GHSA-xgh4-387p-hqpp

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

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

[Bug 1918482] [NEW] Placeholder for GHSA-xgh4-387p-hqpp

2021-03-10 Thread Andrew Hayzen
Public bug reported:

Patches and description coming soon ! I need this to generate a LP bug
number :-)

** Affects: flatpak (Ubuntu)
 Importance: Undecided
 Assignee: Andrew Hayzen (ahayzen)
 Status: In Progress

** Changed in: flatpak (Ubuntu)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

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

Title:
  Placeholder for GHSA-xgh4-387p-hqpp

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

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

[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-03-08 Thread Andrew Paglusch
@Colin Would the package in your PPA be a better source of information
for trying to reproduce 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/1906476

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

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

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

[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-03-07 Thread Andrew Paglusch
I just upgraded to the latest ZoL release and am still having the same
problem. I also upgrade my pool (after creating a checkpoint).

$ modinfo zfs | head -12
filename:   /lib/modules/5.4.0-66-generic/updates/dkms/zfs.ko
version:2.0.3-0york0~20.04
license:CDDL
author: OpenZFS
description:ZFS
alias:  devname:zfs
alias:  char-major-10-249
srcversion: DCE77834FDF1B30075B1328
depends:spl,znvpair,icp,zlua,zzstd,zunicode,zcommon,zavl
retpoline:  Y
name:   zfs
vermagic:   5.4.0-66-generic SMP mod_unload

$ dpkg -l | grep zfs
ii  libzfs2linux 2.0.3-0york0~20.04
amd64OpenZFS filesystem library for Linux
ii  zfs-dkms 2.0.3-0york0~20.04all  
OpenZFS filesystem kernel modules for Linux
ii  zfs-zed  0.8.3-1ubuntu12.6 
amd64OpenZFS Event Daemon
ii  zfsutils-linux   2.0.3-0york0~20.04
amd64command-line tools to manage OpenZFS filesystems

$ zfs --version
zfs-2.0.3-0york0~20.04
zfs-kmod-0.8.3-1ubuntu12.6


Panic:
```
Mar  7 20:29:28 home-nas kernel: [  181.778239] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
Mar  7 20:29:28 home-nas kernel: [  181.778605] PANIC at 
zfs_znode.c:339:zfs_znode_sa_init()
Mar  7 20:29:28 home-nas kernel: [  181.778778] Showing stack for process 2854
Mar  7 20:29:28 home-nas kernel: [  181.778793] CPU: 0 PID: 2854 Comm: ls 
Tainted: P   OE 5.4.0-66-generic #74-Ubuntu
Mar  7 20:29:28 home-nas kernel: [  181.778796] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org 
04/01/2014
Mar  7 20:29:28 home-nas kernel: [  181.778798] Call Trace:
Mar  7 20:29:28 home-nas kernel: [  181.778948]  dump_stack+0x6d/0x9a
Mar  7 20:29:28 home-nas kernel: [  181.779068]  spl_dumpstack+0x29/0x2b [spl]
Mar  7 20:29:28 home-nas kernel: [  181.779081]  spl_panic+0xd4/0xfc [spl]
Mar  7 20:29:28 home-nas kernel: [  181.779491]  ? __zfs_dbgmsg+0xe0/0x110 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.779624]  ? 
sa_cache_constructor+0x27/0x50 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.779643]  ? _cond_resched+0x19/0x30
Mar  7 20:29:28 home-nas kernel: [  181.779657]  ? mutex_lock+0x13/0x40
Mar  7 20:29:28 home-nas kernel: [  181.779760]  ? 
dmu_buf_replace_user+0x60/0x80 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.779863]  ? 
dmu_buf_set_user_ie+0x1a/0x20 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.78]  
zfs_znode_sa_init.isra.0+0xdf/0xf0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780138]  zfs_znode_alloc+0x102/0x6d0 
[zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780249]  ? aggsum_add+0x196/0x1b0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780343]  ? 
dmu_buf_unlock_parent+0x38/0x80 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780429]  ? 
dbuf_read_impl.constprop.0+0x614/0x700 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780442]  ? 
spl_kmem_cache_alloc+0xc1/0x7d0 [spl]
Mar  7 20:29:28 home-nas kernel: [  181.780447]  ? _cond_resched+0x19/0x30
Mar  7 20:29:28 home-nas kernel: [  181.780452]  ? mutex_lock+0x13/0x40
Mar  7 20:29:28 home-nas kernel: [  181.780537]  ? aggsum_add+0x196/0x1b0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780541]  ? _cond_resched+0x19/0x30
Mar  7 20:29:28 home-nas kernel: [  181.780546]  ? _cond_resched+0x19/0x30
Mar  7 20:29:28 home-nas kernel: [  181.780551]  ? down_read+0x13/0xa0
Mar  7 20:29:28 home-nas kernel: [  181.780638]  ? dbuf_read+0x1d0/0x520 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780643]  ? _cond_resched+0x19/0x30
Mar  7 20:29:28 home-nas kernel: [  181.780647]  ? mutex_lock+0x13/0x40
Mar  7 20:29:28 home-nas kernel: [  181.780746]  ? 
dnode_rele_and_unlock+0x6c/0xe0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780751]  ? _cond_resched+0x19/0x30
Mar  7 20:29:28 home-nas kernel: [  181.780755]  ? mutex_lock+0x13/0x40
Mar  7 20:29:28 home-nas kernel: [  181.780847]  ? 
dmu_object_info_from_dnode+0x84/0xb0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.780975]  zfs_zget+0x1c3/0x270 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.781104]  zfs_dirent_lock+0x34b/0x680 
[zfs]
Mar  7 20:29:28 home-nas kernel: [  181.781232]  zfs_dirlook+0x90/0x2b0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.781358]  ? zfs_zaccess+0x153/0x410 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.781484]  zfs_lookup+0x1fd/0x3f0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.781608]  zpl_lookup+0xc9/0x1e0 [zfs]
Mar  7 20:29:28 home-nas kernel: [  181.781662]  ? security_capable+0x3d/0x60
Mar  7 20:29:28 home-nas kernel: [  181.781697]  __lookup_slow+0x92/0x160
Mar  7 20:29:28 home-nas kernel: [  181.781703]  lookup_slow+0x3b/0x60
Mar  7 20:29:28 home-nas kernel: [  181.781709]  walk_component+0x1da/0x360
Mar  7 20:29:28 home-nas kernel: [  181.781714]  ? 
link_path_walk.part.0+0x6d/0x550
Mar  7 20:29:28 home-nas 

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

2021-03-06 Thread Andrew Bauer
This appears to be the problem I ran into with Ubuntu Desktop 20.10 as reported 
here:
https://askubuntu.com/questions/1321431/ubuntu-desktop-20-10-on-usb-flash-drive-boots-only-on-original-computer
 

If it is the same problem (and not a limitation with the latest [but
old] ASUS N551VW BIOS) then please escalate this ABOVE CRITICAL.

I'm sure a lot more Windows 10 users would delight to have a bootable
Ubuntu system on a USB Flash Drive (or an externally USB-connected SSD,
e.g. in an ICY BOX) if the "Device for boot loader installation" set to
/dev/sdb would really write something there. I also noticed a couple of
error messages during booting - one was only a few seconds on the screen
so I was not able to capture it. I will post what I have (in AskUbuntu)
if it is of any assistance to you. My laptop works perfectly (error-
free) with Windows 10.

Apparently the workaround is to remove Disk 0 (Windows 10 drive) from
the laptop. I will give this a try though I doubt that the casual user
would go so far as to unscrew the back cover of their laptop to remove
their HD/SSD.

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

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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

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

[Bug 1917977] Re: Synaptiks touchpad not detected in kernel

2021-03-05 Thread Andrew Davis
I tried to run the command but it said command not available


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

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

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

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

Title:
  Synaptiks touchpad not detected in kernel

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

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

[Bug 1917977] [NEW] Synaptiks touchpad not detected in kernel

2021-03-05 Thread Andrew Davis
Public bug reported:

After using "cat /proc/bus/input/devices" no touchpad shows up same with
xinput and other commands.

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

** Summary changed:

- Synaptiks touchpad not detected in kernal
+ Synaptiks touchpad not detected in kernel

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

Title:
  Synaptiks touchpad not detected in kernel

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

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

[Bug 1917912] [NEW] Skip indexing s3fs

2021-03-05 Thread Andrew Gaul
Public bug reported:

updatedb crawls large remote S3 object stores which incurs a high IO
cost.  This confuses users who experience poor performance and high AWS
bills.  Similar to NFS and ceph, the s3fs project would like to add
fuse.s3fs to PRUNEFS.

Tracking issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1587

** Affects: mlocate (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/1917912

Title:
  Skip indexing s3fs

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

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

[Bug 1917757] Re: General protection fault in Bluetooth HID (Magic Mouse driver)

2021-03-04 Thread Andrew Novikov
** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1917757/+attachment/5472556/+files/dmesg.txt

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

Title:
  General protection fault in Bluetooth HID (Magic Mouse driver)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1917757/+subscriptions

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

[Bug 1917757] [NEW] General protection fault in Bluetooth HID (Magic Mouse driver)

2021-03-04 Thread Andrew Novikov
Public bug reported:

Description:KDE neon User Edition 5.21
Release:20.04

linux-image-5.10.0-1014-oem:
  Installed: 5.10.0-1014.15
  Candidate: 5.10.0-1014.15


Once in a while (typically once every 10 minutes or so) my Bluetooth Apple 
Magic Mouse (I gen) disconnects and reconnects again leading to the "magicmouse 
0005:05AC:030D.001E: unknown main item tag 0x0" messages in the kernel log. But 
this time it seems to have caused a crash in the Bluetooth stack. Here is the 
dmesg output:


[57748.295271] magicmouse 0005:05AC:030D.001E: unknown main item tag 0x0
[57748.295749] input: Magic Mouse as 
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:512/0005:05AC:030D.001E/input/input56
[57748.296035] magicmouse 0005:05AC:030D.001E: input,hidraw1: BLUETOOTH HID 
v3.06 Mouse [Magic Mouse] on 34:2e:b7:45:c7:ba

[62464.630828] general protection fault, probably for non-canonical address 
0xdead00e8:  [#1] SMP NOPTI
[62464.630835] CPU: 11 PID: 36176 Comm: kworker/u25:2 Tainted: G   O
  5.10.0-1014-oem #15-Ubuntu
[62464.630836] Hardware name: Dell Inc. Precision 5750/0XFTD8, BIOS 1.6.3 
12/30/2020
[62464.630860] Workqueue: hci0 hci_rx_work [bluetooth]
[62464.630867] RIP: 0010:__wake_up_common+0xbd/0x140
[62464.630869] Code: c0 00 74 26 41 83 c4 01 41 83 fc 40 7e 1c 48 8d 43 18 48 
39 45 d0 75 66 8b 45 c8 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <48> 8b 43 
18 48 89 df 48 8d 53 18 48 83 e8 18 48 39 55 d0 74 d9 48
[62464.630871] RSP: 0018:a0b58be0fb80 EFLAGS: 00010083
[62464.630873] RAX:  RBX: dead00e8 RCX: c1672078
[62464.630875] RDX: 0001 RSI: 0046 RDI: 0046
[62464.630876] RBP: a0b58be0fbc0 R08:  R09: a0b58be0faf8
[62464.630878] R10: 94fe130d5a10 R11: 95057d56c270 R12: 0002
[62464.630879] R13:  R14:  R15: 
[62464.630881] FS:  () GS:95057d6c() 
knlGS:
[62464.630883] CS:  0010 DS:  ES:  CR0: 80050033
[62464.630884] CR2: 119361d2e000 CR3: 0001b2bce004 CR4: 007706e0
[62464.630886] PKRU: 5554
[62464.630887] Call Trace:
[62464.630892]  __wake_up_common_lock+0x7c/0xc0
[62464.630896]  __wake_up+0x13/0x20
[62464.630898]  sock_def_wakeup+0x36/0x40
[62464.630919]  l2cap_sock_teardown_cb+0x1b1/0x200 [bluetooth]
[62464.630936]  l2cap_chan_del+0x4a/0x2e0 [bluetooth]
[62464.630952]  l2cap_conn_del+0x113/0x230 [bluetooth]
[62464.630969]  l2cap_disconn_cfm+0x3d/0x60 [bluetooth]
[62464.630983]  hci_disconn_complete_evt.isra.0+0x147/0x2e0 [bluetooth]
[62464.630998]  hci_event_packet+0x1b43/0x29b0 [bluetooth]
[62464.631010]  hci_rx_work+0x1a5/0x3b0 [bluetooth]
[62464.631013]  process_one_work+0x1ef/0x390
[62464.631016]  worker_thread+0x4d/0x3f0
[62464.631018]  kthread+0x114/0x150
[62464.631020]  ? process_one_work+0x390/0x390
[62464.631022]  ? kthread_park+0x90/0x90
[62464.631025]  ret_from_fork+0x1f/0x30
[62464.631027] Modules linked in: hid_magicmouse hidp rfcomm vboxnetadp(O) 
vboxnetflt(O) vboxdrv(O) ccm aufs cmac algif_hash algif_skcipher overlay af_alg 
bnep zram btusb btrtl btbcm btintel bluetooth nls_iso8859_1 ecdh_generic ecc 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common 
videodev mc snd_soc_sof_sdw snd_soc_hdac_hdmi snd_soc_rt715 snd_soc_rt1308_sdw 
snd_soc_rt711 regmap_sdw snd_soc_dmic snd_sof_pci snd_sof_intel_byt mei_hdcp 
intel_rapl_msr snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda 
dell_rbtn snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_codec_hdmi 
dell_laptop snd_hda_ext_core snd_soc_acpi_intel_match dell_smm_hwmon 
snd_soc_acpi ledtrig_audio snd_hda_intel joydev snd_intel_dspcfg 
soundwire_intel x86_pkg_temp_thermal intel_powerclamp 
soundwire_generic_allocation soundwire_cadence snd_seq_midi coretemp 
snd_seq_midi_event snd_hda_codec snd_rawmidi snd_hda_core kvm_intel snd_hwdep 
soundwire_bus snd_soc_core iwlmvm kvm snd_compress ac97_bus
[62464.631086]  dell_wmi snd_pcm_dmaengine dell_smbios mac80211 snd_seq rapl 
snd_pcm dcdbas libarc4 intel_cstate input_leds serio_raw efi_pstore 
dell_wmi_descriptor snd_seq_device wmi_bmof hid_sensor_gyro_3d 
intel_wmi_thunderbolt iwlwifi ee1004 snd_timer hid_sensor_als 
hid_sensor_trigger industrialio_triggered_buffer kfifo_buf 
hid_sensor_iio_common industrialio snd ucsi_ccg mei_me processor_thermal_device 
ucsi_acpi cfg80211 cros_ec_ishtp typec_ucsi intel_rapl_common mei 
hid_multitouch cros_ec soundcore intel_soc_dts_iosf intel_pch_thermal typec 
int3403_thermal int340x_thermal_zone mac_hid intel_hid int3400_thermal acpi_tad 
sparse_keymap acpi_pad acpi_thermal_rel sch_fq_codel msr parport_pc ppdev lp 
parport ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_sensor_custom hid_sensor_hub 

[Bug 1917278] [NEW] Unable to reinstall grub. Started with Windows 7. Installed Ubuntu 20.04 to dual boot. Upgraded to Windows 10. Got new monitor, did not recognize Ubuntu install. Reinstalled Ubunt

2021-02-28 Thread Andrew Stevens
Public bug reported:

>From what I can see, the original boot loader was not UEFI, it was
legacy(not sure what that means).  There are 3 primary partitions for
windows and all Ubuntu was installed on an extended partition.  I think
the boot loader is the first primary partition that is 100 mb, but it is
ntfs, not fat32 like efi partitions should be.  Boot-repair doesn't work
either.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
Date: Sun Feb 28 21:40:12 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
RebootRequiredPkgs:
 linux-image-5.8.0-25-generic
 linux-base
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu

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

Title:
  Unable to reinstall grub. Started with Windows 7. Installed Ubuntu
  20.04 to dual boot. Upgraded to Windows 10. Got new monitor, did not
  recognize Ubuntu install.  Reinstalled Ubuntu. Nothing works.  Post
  here. Cry in corner.

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

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

[Bug 1454306] Re: apt-btrfs-snapshot supported reports "Sorry, your system lacks support for the snapshot feature" since update of btrfs-tools to 4.0-2 in debian/testing

2021-02-27 Thread Andrew Derry
All these messages from 2016-2017 saying it's fixed in v16..
Now it's 2021, Feb, I'm using up-to date 20.04 LTS with apt-btrfs-snapshot v353.
I still get the message. How could it have been fixed 5 years ago, but I'm 
still having the problem?
I even made sure there was a copy in /bin and /sbin (and /usr/bin where it was 
according to which)
Thanks

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

Title:
  apt-btrfs-snapshot supported reports "Sorry, your system lacks support
  for the snapshot feature" since update of btrfs-tools to 4.0-2  in
  debian/testing

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

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

[Bug 1812892] Re: Use high ram memory by the gnome-shell-extension-gsconnect

2021-02-23 Thread Andrew Piziali
When I enable GSConnect version 28 (as reported by GSConnect > About) in
Tweaks > Extensions > GSConnect, after a while my Ubuntu 18.04 system
becomes unresponsive, with the disk activity light solidly on. With it
disabled, the system never becomes unresponsive.

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

Title:
  Use high ram memory by the gnome-shell-extension-gsconnect

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

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

[Bug 1730612] Re: Enable Remote desktop feature during build

2021-02-20 Thread Andrew Hayzen
@jik, I think that you need the package gnome-remote-desktop, this has a
MIR request in bug 1802614. And then another package will need to
recommend it to have it installed by default, you can follow this on the
Trello board here https://trello.com/c/NnUq5bHv/15-mir-gnome-remote-
desktop-and-seed-recommend-it

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

Title:
  Enable Remote desktop feature during build

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions

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

[Bug 1793124]

2021-02-17 Thread Andrew Travneff
Related meta: Bug 98754
Current ticket will celebrate 10th anniversary in a week

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

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

[Bug 1891934] Re: [MIR] google-osconfig-agent

2021-02-10 Thread Andrew Jackura
I worked on addressing a number of the concerns in the "Software Recipe" 
section of the agent, this included the File IO concerns as well as a number of 
unchecked errors and other issues. We are currently testing a new stable 
release containing these changes.
There was some concern around the archive extraction implementation overwriting 
files, we check for conflicts and abort the the extractions on any file 
conflicts.

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

Title:
  [MIR] google-osconfig-agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1891934/+subscriptions

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

[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled

2021-02-08 Thread Andrew Cloke
Waiting to close as "Fix Released" once the 5.10 kernel has landed in
hirsute. 5.10 kernel is currently in hirsute -proposed.

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

Title:
  5.10 kernel fails to boot with secure boot disabled

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

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

[Bug 1872476] Re: Shared files are shown as folders

2021-02-08 Thread Andrew Berezovskiy
@rmills: workaround is described in
https://askubuntu.com/questions/1288678/some-files-on-samba-shares-are-
displayed-as-folders (run `setfattr -x user.DOSATTRIB ` on every file
that shows as a dir).

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

Title:
  Shared files are shown as folders

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

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

[Bug 1869763] Re: Huawei Kunpeng 920 arm64 machine KVM guest frequently crash

2021-02-04 Thread Andrew Cloke
** Changed in: kunpeng920
   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/1869763

Title:
  Huawei Kunpeng 920 arm64 machine KVM guest frequently crash

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

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

[Bug 1913602] [NEW] Rendering of formatted cells is at odfds with Excel and Open Office

2021-01-28 Thread Andrew Grant
Public bug reported:

I have been writing an .xlsx file using java POI from InteliJ.

Rendering the sheet does not reflect the cell-styles which have been
applied.

The sheet is absolutely as expected in Excel (on Windows 10) and
OpenOffice on Ubuntu 20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-calc 1:6.4.6-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Jan 28 14:42:29 2021
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-20190418-59+beaver-osp1+X00
InstallationDate: Installed on 2020-08-18 (163 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
SourcePackage: libreoffice
UpgradeStatus: Upgraded to focal on 2020-08-25 (155 days ago)

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "peter.xlsx"
   https://bugs.launchpad.net/bugs/1913602/+attachment/5457770/+files/peter.xlsx

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

Title:
  Rendering of formatted cells is at odfds with Excel and Open Office

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

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

[Bug 1912902] Re: Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute

2021-01-27 Thread Andrew Hayzen
** Description changed:

- Placeholder as we merge the latest changes from Debian sid to Ubuntu
- hirsute.
+ Debian has a newer version of steam packaging available, let's merge the
+ changes into the Ubuntu version to bring us back into sync.

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

Title:
  Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-27 Thread Andrew Hayzen
@Paulo, was there any progress on this or anything you need help with ?
I've posted debdiffs for focal and groovy. Sounds like you have a diff
for bionic.

Let me know if there is anything I can do to help this move to the next
step :-)

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1913488] [NEW] could not determine upgrade an unresolvable problem occured

2021-01-27 Thread Andrew Rice
Public bug reported:

Could not determine the upgrade

An unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If 
you want to investigate this yourself the log files in 
'/var/log/dist-upgrade' will contain details about the upgrade. 
Specifically, look at 'main.log' and 'apt.log'. 


Restoring original system state

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.42
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 27 21:32:27 2021
InstallationDate: Installed on 2018-08-15 (896 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-01-27 (0 days ago)

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


** Tags: amd64 apport-bug bionic dist-upgrade

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

Title:
  could not determine upgrade an unresolvable problem occured

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

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

[Bug 1912902] [NEW] Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute

2021-01-23 Thread Andrew Hayzen
Public bug reported:

Placeholder as we merge the latest changes from Debian sid to Ubuntu
hirsute.

** Affects: steam (Ubuntu)
 Importance: Undecided
 Assignee: Andrew Hayzen (ahayzen)
 Status: In Progress

** Changed in: steam (Ubuntu)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

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

Title:
  Merge steam 1.0.0.68-1 from debian sid to ubuntu hirsute

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-21 Thread Andrew Hayzen
Please find attached the debdiff for Ubuntu 20.10 groovy. This includes
a similar set of patches to the focal set and has been picked from
between the 1.8.4 and 1.8.5 tags.

Let me know if anything has been done incorrectly or missed any commits.

I will leave it up to the security team to decide if Ubuntu should also
include the extra setuid patches provides by upstream in any of these
debdiffs.

** Attachment added: "flatpak_1.8.2-1_to_1.8.2-1ubuntu0.1.debdiff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+attachment/5455341/+files/flatpak_1.8.2-1_to_1.8.2-1ubuntu0.1.debdiff.gz

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

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-21 Thread Andrew Hayzen
@Kleber I have installed the focal hwe kernel from proposed (as seen
below). So far when A/B testing this kernel it is working correctly :-)
I will continue running this kernel and report any issues I have.

Also note that I have been continuously running the test kernel (from
comment 22) since last week and it has worked perfectly so far :-)

I look forward to this migrating from -proposed into focal.

$ uname -a
Linux xps-13-9360 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ apt policy linux-generic-hwe-20.04
linux-generic-hwe-20.04:
  Installed: 5.8.0.41.46~20.04.27
  Candidate: 5.8.0.41.46~20.04.27
  Version table:
 *** 5.8.0.41.46~20.04.27 500
500 http://gb.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 5.8.0.40.45~20.04.25 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 5.8.0.38.43~20.04.23 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 5.4.0.26.32 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  nvme drive fails after some time

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-21 Thread Andrew Hayzen
@Paulo, Thanks !

BTW smcv just pointed out two more potential patches that could be
included in the focal 1.6 patch, these are only for users that use
setuid on the bubblewrap binary though (users who disable user
namespaces - like Debian). It would be up to us if we want to include
them. See
https://github.com/flatpak/flatpak/pull/4070#issuecomment-764664659  I
can try and include these extra two commits if you think it is useful,
but not sure how many users would do this or if it would be considered
"supported" ?

For bionic note that the flatpak-1.2.x branch has the fixes applied
(with extra setuid patches here
https://github.com/flatpak/flatpak/pull/4087 ) these may help for
figuring out 1.0.x

And what would the security team prefer to do for groovy ? We could
either sync 1.8.5 from hirsute or apply the patches to 1.8.2 ? (although
looks like 1.10.0-2 is in hirsute-proposed, so might have to be quick
:') unless we can sync an older version somehow )

Please advise if you want me to attempt any other areas :-)

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))

2021-01-18 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   Status: Fix Committed => 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/1904585

Title:
  opal-prd: Have a worker process handle page offlining (Fixes
  "PlatServices: dyndealloc memory_error() failed" is getting reported
  in error log (opal-prd))

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

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

[Bug 1905393] Re: Ubuntu 20.04: opal-prd fails to start on 20.04

2021-01-18 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   Status: Fix Committed => 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/1905393

Title:
  Ubuntu 20.04: opal-prd fails to start on 20.04

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-15 Thread Andrew Hayzen
1.8.5 has landed in hirsute now, so marking hirsute as fixed released.

** Changed in: flatpak (Ubuntu Hirsute)
   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/1911473

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-15 Thread Andrew Hayzen
@Marcelo So far it looks good :-) It passes the "fio" command test when
A/B testing between a known bad kernel and this new kernel. I will
continue running it on this machine over the weekend to ensure longer
usage doesn't have any remaining issues - but looks like it resolves the
issue so far :-D Thanks!

$ uname -a
Linux xps-13-9360 5.8.0-38-generic #43+lp1910866 SMP Fri Jan 15 20:29:27 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  nvme drive fails after some time

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-15 Thread Andrew Hayzen
Thanks! I'll take a look :-)

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

Title:
  nvme drive fails after some time

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-15 Thread Andrew Hayzen
@kaihengfeng Thanks for the quick response!  bug 1908555 linked there
only lists groovy as a target series, I hope that this will also be
applied to the focal HWE kernel :-)

Also I am happy to test any kernel in a -proposed channel or PPA to
confirm it fixes the issue if that helps :-)

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

Title:
  nvme drive fails after some time

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-15 Thread Andrew Hayzen
@kaihengfeng

So v5.7 was fine and after many reboots it has been found that this
commit below introduced the issue.

Do I also need to find when the issue was resolved ? (between v5.8-rc1
and v5.9.10) or is this information enough ?


54b2fcee1db041a83b52b51752dade6090cf952f is the first bad commit
commit 54b2fcee1db041a83b52b51752dade6090cf952f
Author: Keith Busch 
Date:   Mon Apr 27 11:54:46 2020 -0700

nvme-pci: remove last_sq_tail

The nvme driver does not have enough tags to wrap the queue, and blk-mq
will no longer call commit_rqs() when there are no new submissions to
notify.

Signed-off-by: Keith Busch 
Reviewed-by: Sagi Grimberg 
Signed-off-by: Christoph Hellwig 
Signed-off-by: Jens Axboe 

 drivers/nvme/host/pci.c | 23 ---
 1 file changed, 4 insertions(+), 19 deletions(-)


And my $ git bisect log is the following FWIW.
git bisect start
# good: [3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162] Linux 5.7
git bisect good 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162
# bad: [b3a9e3b9622ae10064826dccb4f7a52bd88c7407] Linux 5.8-rc1
git bisect bad b3a9e3b9622ae10064826dccb4f7a52bd88c7407
# bad: [ee01c4d72adffb7d424535adf630f2955748fa8b] Merge branch 'akpm' (patches 
from Andrew)
git bisect bad ee01c4d72adffb7d424535adf630f2955748fa8b
# bad: [16d91548d1057691979de4686693f0ff92f46000] Merge tag 'xfs-5.8-merge-8' 
of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
git bisect bad 16d91548d1057691979de4686693f0ff92f46000
# good: [cfa3b8068b09f25037146bfd5eed041b78878bee] Merge tag 'for-linus-hmm' of 
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
git bisect good cfa3b8068b09f25037146bfd5eed041b78878bee
# good: [3fd911b69b3117e03181262fc19ae6c3ef6962ce] Merge tag 
'drm-misc-next-2020-05-07' of git://anongit.freedesktop.org/drm/drm-misc into 
drm-next
git bisect good 3fd911b69b3117e03181262fc19ae6c3ef6962ce
# good: [1966391fa576e1fb2701be8bcca197d8f72737b7] mm/migrate.c: 
attach_page_private already does the get_page
git bisect good 1966391fa576e1fb2701be8bcca197d8f72737b7
# bad: [0c8d3fceade2ab1bbac68bca013e62bfdb851d19] bcache: configure the 
asynchronous registertion to be experimental
git bisect bad 0c8d3fceade2ab1bbac68bca013e62bfdb851d19
# bad: [84b8d0d7aa159652dc191d58c4d353b6c9173c54] nvmet: use type-name map for 
ana states
git bisect bad 84b8d0d7aa159652dc191d58c4d353b6c9173c54
# good: [72e6329f86c714785ac195d293cb19dd24507880] nvme-fc and nvmet-fc: revise 
LLDD api for LS reception and LS request
git bisect good 72e6329f86c714785ac195d293cb19dd24507880
# good: [e4fcc72c1a420bdbe425530dd19724214ceb44ec] nvmet-fc: slight cleanup for 
kbuild test warnings
git bisect good e4fcc72c1a420bdbe425530dd19724214ceb44ec
# good: [31fdad7be18992606078caed6ff71741fa76310a] nvme: consolodate io settings
git bisect good 31fdad7be18992606078caed6ff71741fa76310a
# bad: [2a5bcfdd41d68559567cec3c124a75e093506cc1] nvme-pci: align io queue 
count with allocted nvme_queue in nvme_probe
git bisect bad 2a5bcfdd41d68559567cec3c124a75e093506cc1
# good: [6623c5b3dfa5513190d729a8516db7a5163ec7de] nvme: clean up error 
handling in nvme_init_ns_head
git bisect good 6623c5b3dfa5513190d729a8516db7a5163ec7de
# good: [74943d45eef4db64b1e5c9f7ad1d018576e113c5] nvme-pci: remove volatile 
cqes
git bisect good 74943d45eef4db64b1e5c9f7ad1d018576e113c5
# bad: [54b2fcee1db041a83b52b51752dade6090cf952f] nvme-pci: remove last_sq_tail
git bisect bad 54b2fcee1db041a83b52b51752dade6090cf952f
# first bad commit: [54b2fcee1db041a83b52b51752dade6090cf952f] nvme-pci: remove 
last_sq_tail

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

Title:
  nvme drive fails after some time

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-15 Thread Andrew Hayzen
** Changed in: flatpak (Ubuntu Focal)
   Status: New => In Progress

** Changed in: flatpak (Ubuntu Focal)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
If anyone has the permission to propose this bug for the series, bionic,
focal, and groovy that would be useful :-)

** Description changed:

+ [Links]
+ 
+ Upstream Advisory: 
https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2
+ Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261
+ DSA: https://security-tracker.debian.org/tracker/DSA-4830-1
+ 
  [Impact]
  
  Versions in Ubuntu right now:
  Hirsute: 1.8.4-2
  Groovy: 1.8.2-1
  Focal: 1.6.5-0ubuntu0.1
  Bionic: 1.0.9-0ubuntu0.1
  
  Affected versions:
  >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5
  
  Patched versions:
  Expected to be >= 1.9.4, 1.8.x >= 1.8.5
  
  There are also branches with patches for 1.6.x (Ubuntu 20.04), but
  nothing available yet for 1.0.x (Ubuntu 18.04).
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all architectures
  and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
  Simon McVittie discovered a bug in the flatpak-portal service that can
  allow sandboxed applications to execute arbitrary code on the host
  system (a sandbox escape).
  
  The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus 
service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox 
to launch their own subprocesses in a new sandbox instance, either with the 
same security settings as the caller or with
  more restrictive security settings. For example, this is used in 
Flatpak-packaged web browsers such as Chromium to launch subprocesses
  that will process untrusted web content, and give those subprocesses a more 
restrictive sandbox than the browser itself.
  
  In vulnerable versions, the Flatpak portal service passes caller-
  specified environment variables to non-sandboxed processes on the host
  system, and in particular to the flatpak run command that is used to
  launch the new sandbox instance. A malicious or compromised Flatpak app
  could set environment variables that are trusted by the flatpak run
  command, and use them to execute arbitrary code that is not in a
  sandbox.
- 
- https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-
- fxf6-vxg2
- 
- Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
Please find attached the debdiff for Ubuntu 20.04 focal. I have tested
this using the manual test plan in a VM and built in a PPA.

Let me know if anything has been done incorrectly.

** Summary changed:

- Placeholder for ghsa-4ppf-fxf6-vxg2
+ Update for ghsa-4ppf-fxf6-vxg2

** Description changed:

- Placeholder for ghsa-4ppf-fxf6-vxg2 as I prepare the debdiffs.
- 
  [Impact]
  
  Versions in Ubuntu right now:
  Hirsute: 1.8.4-2
  Groovy: 1.8.2-1
  Focal: 1.6.5-0ubuntu0.1
  Bionic: 1.0.9-0ubuntu0.1
  
  Affected versions:
  >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5
  
  Patched versions:
  Expected to be >= 1.9.4, 1.8.x >= 1.8.5
  
  There are also branches with patches for 1.6.x (Ubuntu 20.04), but
  nothing available yet for 1.0.x (Ubuntu 18.04).
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all architectures
  and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
  Simon McVittie discovered a bug in the flatpak-portal service that can
  allow sandboxed applications to execute arbitrary code on the host
  system (a sandbox escape).
  
  The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus 
service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox 
to launch their own subprocesses in a new sandbox instance, either with the 
same security settings as the caller or with
  more restrictive security settings. For example, this is used in 
Flatpak-packaged web browsers such as Chromium to launch subprocesses
  that will process untrusted web content, and give those subprocesses a more 
restrictive sandbox than the browser itself.
  
  In vulnerable versions, the Flatpak portal service passes caller-
  specified environment variables to non-sandboxed processes on the host
  system, and in particular to the flatpak run command that is used to
  launch the new sandbox instance. A malicious or compromised Flatpak app
  could set environment variables that are trusted by the flatpak run
  command, and use them to execute arbitrary code that is not in a
  sandbox.
  
  https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-
  fxf6-vxg2
  
- Debian: https://security-tracker.debian.org/tracker/TEMP-000-73A644
- (temporary)
+ Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261

** Attachment added: "flatpak_1.6.5-0ubuntu0.1_to_1.6.5-0ubuntu0.2.debdiff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+attachment/5453101/+files/flatpak_1.6.5-0ubuntu0.1_to_1.6.5-0ubuntu0.2.debdiff.gz

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
Also note that hirsute now has 1.8.5 in hirsute-proposed (which contains
the fix), although it looks like s390x has failed in the tests - I
wonder if a retest will make it pass or if it is a genuine failure.

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

Title:
  Update for ghsa-4ppf-fxf6-vxg2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+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

2021-01-14 Thread andrew
This has been like this for a lng time

-- 
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 1911473] Re: Placeholder for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-21261

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

Title:
  Placeholder for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1911473] Re: Placeholder for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
@Paulo

hirsute - can sync 1.8.5 from debian sid which contains the fix.
groovy - is a tricky one as it is one step behind in terms of microreleases 
(1.8.3) so either needs backporting or bumping to 1.8.5
focal - upstream have created a branch for me with relevant patches that allow 
it to build, but is untested (i plan on doing this later tonight)
bionic - there is no branch upstream for this series yet, we would need to 
figure out patches

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

Title:
  Placeholder for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1911473] Re: Placeholder for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
@Paulo, Hi yes there is no CVE yet, but I believe upstream have
requested one via github (I can see it says one has been requested). I
will also try to submit debdiffs for Ubuntu 20.04 shortly (hopefully
later tonight if testing goes well).

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

Title:
  Placeholder for ghsa-4ppf-fxf6-vxg2

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

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

[Bug 1911473] Re: Placeholder for ghsa-4ppf-fxf6-vxg2

2021-01-14 Thread Andrew Hayzen
This is now public.

** Information type changed from Private Security to Public Security

** Description changed:

  Placeholder for ghsa-4ppf-fxf6-vxg2 as I prepare the debdiffs.
  
  This issue will be made public I believe on 14/01/2021 daytime CET.
- 
  
  [Impact]
  
  Versions in Ubuntu right now:
  Hirsute: 1.8.4-2
  Groovy: 1.8.2-1
  Focal: 1.6.5-0ubuntu0.1
  Bionic: 1.0.9-0ubuntu0.1
  
  Affected versions:
- >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5 
+ >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5
  
  Patched versions:
- Expected to be >= 1.9.4, 1.8.x >= 1.8.5 
+ Expected to be >= 1.9.4, 1.8.x >= 1.8.5
  
  There are also branches with patches for 1.6.x (Ubuntu 20.04), but
  nothing available yet for 1.0.x (Ubuntu 18.04).
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all architectures
  and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
  Simon McVittie discovered a bug in the flatpak-portal service that can
  allow sandboxed applications to execute arbitrary code on the host
  system (a sandbox escape).
  
  The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus 
service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox 
to launch their own subprocesses in a new sandbox instance, either with the 
same security settings as the caller or with
  more restrictive security settings. For example, this is used in 
Flatpak-packaged web browsers such as Chromium to launch subprocesses
  that will process untrusted web content, and give those subprocesses a more 
restrictive sandbox than the browser itself.
  
  In vulnerable versions, the Flatpak portal service passes caller-
  specified environment variables to non-sandboxed processes on the host
  system, and in particular to the flatpak run command that is used to
  launch the new sandbox instance. A malicious or compromised Flatpak app
  could set environment variables that are trusted by the flatpak run
  command, and use them to execute arbitrary code that is not in a
  sandbox.
  
  https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-
  fxf6-vxg2
+ 
+ Debian: https://security-tracker.debian.org/tracker/TEMP-000-73A644
+ (temporary)

** Description changed:

  Placeholder for ghsa-4ppf-fxf6-vxg2 as I prepare the debdiffs.
- 
- This issue will be made public I believe on 14/01/2021 daytime CET.
  
  [Impact]
  
  Versions in Ubuntu right now:
  Hirsute: 1.8.4-2
  Groovy: 1.8.2-1
  Focal: 1.6.5-0ubuntu0.1
  Bionic: 1.0.9-0ubuntu0.1
  
  Affected versions:
  >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5
  
  Patched versions:
  Expected to be >= 1.9.4, 1.8.x >= 1.8.5
  
  There are also branches with patches for 1.6.x (Ubuntu 20.04), but
  nothing available yet for 1.0.x (Ubuntu 18.04).
  
  [Test Case]
  
  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.
  
  [Regression Potential]
  
  Flatpak has a test suite, which is run on build across all architectures
  and passes.
  
  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .
  
  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .
  
  Regression potential is low, and upstream is very responsive to any
  issues raised.
  
  [Other information]
  
  Simon McVittie discovered a bug in the flatpak-portal service that can
  allow sandboxed applications to execute arbitrary code on the host
  system (a sandbox escape).
  
  The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus 
service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox 
to launch their own subprocesses in a new sandbox instance, either with the 
same security settings as the caller or with
  more restrictive security settings. For example, this is used in 
Flatpak-packaged web browsers such as Chromium to launch subprocesses
  that will process untrusted web content, and give those subprocesses a more 
restrictive sandbox than the browser itself.
  
  In vulnerable versions, the Flatpak portal service passes caller-
  specified environment variables to non-sandboxed processes on the host
  system, and in particular to the flatpak run command that is used to
  launch the new sandbox instance. A malicious or compromised Flatpak app
  could set environment variables that are trusted by the flatpak run
  command, and use them to execute arbitrary code that is not in a
  sandbox.
  
  https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-
  

[Bug 1910866] Re: nvme drive fails after some time

2021-01-12 Thread Andrew Hayzen
And the bisect between 5.4.78 (good) and 5.8.18 (bad).

The following results with the mainline kernel
v5.8.18/FAIL
v5.8.4/ FAIL
v5.8-rc5/   FAIL
v5.8-rc1/   FAIL
v5.7.19/PASS
v5.7.18/PASS
v5.7.16/PASS
v5.6.14/PASS
v5.4.78/PASS

>From these and the previous comment's results it appears that the issue
was introduced with 5.8-rc1 and then was fixed with 5.9.9 or 5.9.10.
(it is unfortunate that 5.9.9 is missing so I cannot try it).

@kaihengfeng let me know if there is any other information I can
provide.

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

Title:
  nvme drive fails after some time

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-12 Thread Andrew Hayzen
So bisecting between 5.8.18 (bad) and 5.11-rc3 (good).

The following results with the mainline kernel
v5.11-rc3/  PASS
v5.9.12/PASS
v5.9.10/PASS
v5.9.9/ MISSING
v5.9.8/ FAIL (could not boot long enough for full test)
v5.9.7/ FAIL (could not boot long enough for full test)
v5.9.2/ FAIL (could not boot long enough for full test)
v5.8.18/FAIL

Note that 5.9.2, 5.9.7, 5.9.8 all crashed during either boot or logging
in (but after performing REISUB they all entered the Dell BIOS/recovery
stating that the hard disk could not be found, so I assume this is the
same failure).

>From these results it appears that between 5.9.8 and 5.9.10 it was
fixed.

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

Title:
  nvme drive fails after some time

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-12 Thread Andrew Hayzen
OK, so using https://people.canonical.com/~kernel/info/kernel-version-
map.html that states that Ubuntu kernel 5.8.0-36.40~20.04.1 matches
mainline version 5.8.18. I have installed 5.8.18 and it fails ! So it is
not the Ubuntu patches.

Ubuntu Kernels:
linux-image-5.4.0-59-generic: PASS
linux-image-5.8.0-36-generic: FAIL

Mainline Kernels:
linux-image-unsigned-5.8.18-050818-generic: FAIL
linux-image-unsigned-5.11.0-051100rc3-generic: PASS

I'll see if I can find where it changes from FAIL to PASS between 5.8.18
in the mainline kernels. Please advise if should also/instead compare
between 5.4 and 5.8.18 :-)

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

Title:
  nvme drive fails after some time

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-12 Thread Andrew Hayzen
@kaihengfeng

I have found that running the command "fio --name=basic
--directory=/path/to/empty/directory --size=1G --rw=randrw --numjobs=4
--loops=5" runs fine on linux-image-5.4.0-59-generic but when trying
with linux-image-5.8.0-36-generic it would freeze the system in the
"Laying out IO file" stage. I checked with two subsequent boots that the
5.8 does fail like this on an empty directory and will now use this as
my "test" if a kernel works or not.

I have installed the 5.11 rc3 mainline kernel you linked, note I have
had to disable secure boot to be able to use it. But this kernel worked
successfully on two boots with the fio test above.

So in summary so far on my system with the fio test:
linux-image-5.4.0-59-generic: PASS
linux-image-5.8.0-36-generic: FAIL
linux-image-unsigned-5.11.0-051100rc3-generic: PASS

Please advise how to proceed here, should I start manually picking (by
bisecting) kernels between 5.8 and 5.11 or between 5.4 and 5.8 ?

Also I guess I should also try 5.8 mainline to ensure that any Ubuntu
patches aren't causing an issue?

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

Title:
  nvme drive fails after some time

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

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

[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))

2021-01-12 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   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/1904585

Title:
  opal-prd: Have a worker process handle page offlining (Fixes
  "PlatServices: dyndealloc memory_error() failed" is getting reported
  in error log (opal-prd))

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

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

[Bug 1905393] Re: Ubuntu 20.04: opal-prd fails to start on 20.04

2021-01-12 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   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/1905393

Title:
  Ubuntu 20.04: opal-prd fails to start on 20.04

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

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

[Bug 1910866] Re: nvme drive fails after some time

2021-01-11 Thread Andrew Hayzen
FYI I have captured the `sudo lspci -vv` output on the kernel 5.8
*before* the issue here https://pastebin.ubuntu.com/p/GtZyTWzKTd/ it is
subtly different to the 5.4 kernel (which has not had the issue) in case
that mattered.

I was also able to reproduce the issue again by causing high disk I/O,
specifically I needed to have writes occurring for it to happen (I was
recursive grep'ing the whole filesystem while installing apt/pip
packages inside a docker container).

This then froze the system for 120 seconds until write timeouts
occurred, then the disk was remounted as read-only. After this point
commands on the system would fail with I/O errors (even basic ones such
as "top", although some such as "mount" still work).

However our plan was to try to retrieve more information by copying the
lspci binary and libs into a tmpfs system in RAM, so it'd still be
accessible when the disk stopped. This almost worked, but it appears a
few more configuration files would need to be placed in RAM (I could run
"lspci --help" but not "lspci" or "lspci -vv"). Instead popey has
suggested maybe using a USB key with debootstrap/chroot. (Any
suggestions of how we can retrieve more information at this point are
welcome and any commands that would be useful to run).

Also as a note, if I use REISUB (
https://en.m.wikipedia.org/wiki/Magic_SysRq_key#Uses ) to reboot the
machine it enters a Dell BIOS/recovery thing that states that "No Hard
Disk is found". Then after a full power off the machine works again.

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

Title:
  nvme drive fails after some time

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

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

[Bug 1832915] Re: numad crashes while running kvm guest

2021-01-11 Thread Andrew Cloke
Eoan is now EOL. Marking as "won't fix".

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

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

Title:
  numad crashes while running kvm guest

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

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

  1   2   3   4   5   6   7   8   9   10   >