| 2023-04-11 09:28:11 |
Daniel van Vugt |
bug |
|
|
added bug |
| 2023-04-11 09:28:50 |
Daniel van Vugt |
tags |
|
lunar |
|
| 2023-04-11 09:44:48 |
Benjamin Drung |
apport (Ubuntu): status |
New |
Incomplete |
|
| 2023-04-11 18:00:21 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2023-04-12 08:21:08 |
Daniel van Vugt |
attachment added |
|
_usr_bin_gnome-shell.1000.crash https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5663203/+files/_usr_bin_gnome-shell.1000.crash |
|
| 2023-04-12 08:32:53 |
Daniel van Vugt |
attachment added |
|
_usr_bin_gnome-shell.1000.crash https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5663204/+files/_usr_bin_gnome-shell.1000.crash |
|
| 2023-04-12 08:34:59 |
Daniel van Vugt |
apport (Ubuntu): status |
Incomplete |
New |
|
| 2023-04-17 13:15:30 |
Benjamin Drung |
description |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" |
|
| 2023-04-17 13:47:39 |
Benjamin Drung |
apport (Ubuntu): importance |
Undecided |
High |
|
| 2023-04-17 13:47:39 |
Benjamin Drung |
apport (Ubuntu): status |
New |
Triaged |
|
| 2023-04-19 11:40:51 |
Benjamin Drung |
attachment added |
|
0001-apport-Write-coredump-at-beginning-and-quit.patch https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5665206/+files/0001-apport-Write-coredump-at-beginning-and-quit.patch |
|
| 2023-04-19 11:41:11 |
Benjamin Drung |
bug task added |
|
linux (Ubuntu) |
|
| 2023-04-19 11:48:46 |
Benjamin Drung |
description |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized" |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized"
Steps to reproduce
==================
1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell
2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293)
3. Remove all crashes: `sudo rm -f /var/crash/*`
4. Interact with the desktop, icon grid and calendar for 30 seconds.
5. Log out.
6. Crash files written.
To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport-retrace -g` on the .crash file. It will fail to print the backtrace:
```
$ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash
[...]
Warnung: Error reading shared library list entry at 0x646c747200000000
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
Warnung: Section `.reg-xstate/10527' in core file too small.
(gdb) bt
#0 0x00007fe1c8090ffb in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0
``` |
|
| 2023-04-19 11:49:51 |
Benjamin Drung |
description |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized"
Steps to reproduce
==================
1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell
2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293)
3. Remove all crashes: `sudo rm -f /var/crash/*`
4. Interact with the desktop, icon grid and calendar for 30 seconds.
5. Log out.
6. Crash files written.
To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport-retrace -g` on the .crash file. It will fail to print the backtrace:
```
$ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash
[...]
Warnung: Error reading shared library list entry at 0x646c747200000000
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
Warnung: Section `.reg-xstate/10527' in core file too small.
(gdb) bt
#0 0x00007fe1c8090ffb in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0
``` |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized"
Steps to reproduce
==================
1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell
2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293)
3. Remove all crashes: `sudo rm -f /var/crash/*`
4. Interact with the desktop, icon grid and calendar for 30 seconds.
5. Log out.
6. Crash files written.
To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport-retrace -g` on the .crash file. It will fail to print the backtrace:
```
$ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash
[...]
Warnung: Error reading shared library list entry at 0x646c747200000000
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
Warnung: Section `.reg-xstate/10527' in core file too small.
(gdb) bt
#0 0x00007fe1c8090ffb in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0
```
You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. |
|
| 2023-04-19 11:52:28 |
Benjamin Drung |
summary |
Repeatedly unusable truncated crash files |
Repeatedly unusable truncated crash files (on log-out) |
|
| 2023-04-19 12:00:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2023-04-19 12:15:49 |
Ubuntu Foundations Team Bug Bot |
tags |
lunar |
lunar patch |
|
| 2023-04-19 12:15:56 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Terry Rudd |
| 2023-04-19 12:34:58 |
Benjamin Drung |
description |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized"
Steps to reproduce
==================
1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell
2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293)
3. Remove all crashes: `sudo rm -f /var/crash/*`
4. Interact with the desktop, icon grid and calendar for 30 seconds.
5. Log out.
6. Crash files written.
To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport-retrace -g` on the .crash file. It will fail to print the backtrace:
```
$ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash
[...]
Warnung: Error reading shared library list entry at 0x646c747200000000
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
Warnung: Section `.reg-xstate/10527' in core file too small.
(gdb) bt
#0 0x00007fe1c8090ffb in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0
```
You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out. |
Repeatedly unusable truncated crash files:
Bug 2012974, bug 2015842, bug 2015140, bug 2012075
Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete.
If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell).
Running `apport-retrace -g $crash` on the .crash files will fail with "/tmp/apport_core_[...] is not a core dump: file format not recognized"
Steps to reproduce
==================
1. Use Ubuntu 23.04 (lunar) desktop with GNOME shell
2. Downgrade gjs and libgjs0g to 1.76.0-1 (for triggering bug 1974293)
3. Remove all crashes: `sudo rm -f /var/crash/*`
4. Interact with the desktop, icon grid and calendar for 30 seconds.
5. Log out.
6. Crash files written.
To test the core file, either use `apport-unpack` on the /var/crash/*.crash file to extract the CoreDump file or use `apport-retrace -g` on the .crash file. It will fail to print the backtrace:
```
$ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash
[...]
Warnung: Error reading shared library list entry at 0x646c747200000000
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
Warnung: Section `.reg-xstate/10527' in core file too small.
(gdb) bt
#0 0x00007fe1c8090ffb in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd59a40fe0
```
You can use the 0001-apport-Write-coredump-at-beginning-and-quit.patch on apport to only write the coredump and adjust the slowdown to 100% reproduce the behavior on log-out.
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-20-generic 6.2.0-20.20
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=6278216c-6f7c-4a94-8eab-e9c43da65227 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 |
|
| 2023-04-19 12:35:55 |
Benjamin Drung |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
