| 2022-07-22 08:08:58 |
Benjamin Drung |
bug |
|
|
added bug |
| 2022-07-22 08:09:04 |
Benjamin Drung |
apport: importance |
Undecided |
Medium |
|
| 2022-07-22 08:09:06 |
Benjamin Drung |
apport: status |
New |
Triaged |
|
| 2022-07-22 08:09:24 |
Benjamin Drung |
bug task added |
|
apport (Ubuntu) |
|
| 2022-07-22 08:09:29 |
Benjamin Drung |
apport (Ubuntu): status |
New |
Triaged |
|
| 2022-07-22 08:09:32 |
Benjamin Drung |
apport (Ubuntu): importance |
Undecided |
Medium |
|
| 2022-07-22 08:21:38 |
Benjamin Drung |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-07-22 08:21:38 |
Benjamin Drung |
bug task added |
|
apport (Ubuntu Jammy) |
|
| 2022-07-22 08:21:38 |
Benjamin Drung |
nominated for series |
|
Ubuntu Focal |
|
| 2022-07-22 08:21:38 |
Benjamin Drung |
bug task added |
|
apport (Ubuntu Focal) |
|
| 2022-07-22 09:13:39 |
Benjamin Drung |
apport: status |
Triaged |
Fix Committed |
|
| 2022-07-22 09:13:39 |
Benjamin Drung |
apport: milestone |
|
2.23.0 |
|
| 2022-07-22 16:46:53 |
Benjamin Drung |
attachment added |
|
apport_2.20.11-0ubuntu82.2.debdiff https://bugs.launchpad.net/apport/+bug/1982555/+attachment/5604814/+files/apport_2.20.11-0ubuntu82.2.debdiff |
|
| 2022-07-22 16:47:22 |
Benjamin Drung |
attachment added |
|
apport_2.20.11-0ubuntu27.25.debdiff https://bugs.launchpad.net/apport/+bug/1982555/+attachment/5604815/+files/apport_2.20.11-0ubuntu27.25.debdiff |
|
| 2022-07-22 20:22:35 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2022-07-25 10:10:06 |
Launchpad Janitor |
apport (Ubuntu Focal): status |
New |
Confirmed |
|
| 2022-07-25 10:10:06 |
Launchpad Janitor |
apport (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2022-07-25 17:32:04 |
Benjamin Drung |
attachment added |
|
apport_2.20.11-0ubuntu27.25.debdiff https://bugs.launchpad.net/apport/+bug/1982555/+attachment/5605243/+files/apport_2.20.11-0ubuntu27.25.debdiff |
|
| 2022-07-25 17:32:44 |
Benjamin Drung |
attachment added |
|
apport_2.20.11-0ubuntu82.2.debdiff https://bugs.launchpad.net/apport/+bug/1982555/+attachment/5605244/+files/apport_2.20.11-0ubuntu82.2.debdiff |
|
| 2022-08-22 20:24:27 |
Benjamin Drung |
apport: status |
Fix Committed |
Fix Released |
|
| 2022-08-23 20:50:08 |
Benjamin Drung |
description |
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. |
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. |
|
| 2022-08-23 20:52:18 |
Benjamin Drung |
description |
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. |
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is accompanied by a test case.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. |
|
| 2022-08-27 20:26:30 |
Launchpad Janitor |
apport (Ubuntu): status |
Triaged |
Fix Released |
|
| 2022-09-19 17:18:44 |
Benjamin Drung |
description |
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is accompanied by a test case.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. |
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is accompanied by a test case.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug.
Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review.
* jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb
* focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 |
|
| 2022-10-17 13:00:47 |
Timo Aaltonen |
apport (Ubuntu Jammy): status |
Confirmed |
Fix Committed |
|
| 2022-10-17 13:00:50 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-10-17 13:00:52 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2022-10-17 13:00:54 |
Timo Aaltonen |
tags |
patch |
patch verification-needed verification-needed-jammy |
|
| 2022-10-17 13:06:10 |
Timo Aaltonen |
apport (Ubuntu Focal): status |
Confirmed |
Fix Committed |
|
| 2022-10-17 13:06:15 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-jammy |
patch verification-needed verification-needed-focal verification-needed-jammy |
|
| 2022-10-18 14:24:43 |
Benjamin Drung |
tags |
patch verification-needed verification-needed-focal verification-needed-jammy |
patch verification-done-jammy verification-needed verification-needed-focal |
|
| 2022-10-18 14:28:00 |
Benjamin Drung |
tags |
patch verification-done-jammy verification-needed verification-needed-focal |
patch verification-done verification-done-focal verification-done-jammy |
|
| 2022-11-23 00:49:15 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-11-23 02:02:38 |
Launchpad Janitor |
apport (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-11-23 02:24:28 |
Launchpad Janitor |
apport (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-11-23 16:04:38 |
Benjamin Drung |
nominated for series |
|
Ubuntu Bionic |
|
| 2022-11-23 16:04:38 |
Benjamin Drung |
bug task added |
|
apport (Ubuntu Bionic) |
|
