[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files (on log-out)

2023-04-19 Thread Benjamin Drung
Added package version to the description (apport-collect does not allow me to collect the data since I am not the original reporter). ** Description changed: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files (on log-out)

2023-04-19 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly unusable truncated crash files (on log-out) Status in apport package in

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files (on log-out)

2023-04-19 Thread Benjamin Drung
This behavior is only noticeable on log-out. Killing gnome-shell works. I am using the 0001-apport-Write-coredump-at-beginning-and-quit.patch with a delay of 0.005s: ``` $ killall -11 gnome-shell $ tail /var/log/apport.log ERROR: apport (pid 15107) 2023-04-19 13:53:03,089: called for pid 14206,

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-19 Thread Benjamin Drung
Note: Apport triggers this behavior, because it compresses the core dump and base64 encodes the compressed result. That increases the time to read the coredump file. In addition apport also takes some time to collect the crash information. ** Summary changed: - Repeatedly unusable truncated

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-19 Thread Benjamin Drung
One day of debugging gave more insight. Apport is not directly the culprit. If reading from stdin takes too long, the input will be truncated. Attached a patch for apport to write the coredump at the beginning and quit. It can be slowed down by sleeping between the 1 MB blocks. The longer the

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-18 Thread Daniel van Vugt
Yes I noticed full gnome-shell core files are often 500MB (as is the RSS), though they seem to be mostly zeroes as evidenced by the reported filesystem usage. Not saying that's a bug, just an observation. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-18 Thread Benjamin Drung
I modified apport to write the core file right at the beginning and it was correctly written. That points to an issue with apport itself. The written core file is around 500 MB. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-17 Thread Benjamin Drung
If I kill gnome-shell the crash file is written correctly: ``` $ killall -11 gnome-shell $ apport-retrace -g /var/crash/_usr_bin_gnome-shell.1000.crash [...] [New LWP 7620] Warnung: Section `.reg-xstate/7229' in core file too small. Downloading separate debug info for

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-17 Thread Benjamin Drung
Thanks for providing the steps to reproduce. Preparation: 1. Ubuntu 23.04 (lunar) desktop in a VM 2. Remove all crashes: `sudo rm -f /var/crash/*` 3. Downgrade gjs and libgjs0g to 1.76.0-1 Then did your steps. On the first tries the crash file was 49 MB in size and retracing looks correct. On my

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-17 Thread Benjamin Drung
** Description changed: 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

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-12 Thread Daniel van Vugt
Steps to reproduce: 1. Make sure you don't have the fix for bug 1974293, so make sure libgjs0g == 1.76.0-1 2. Log into Lunar. 3. Interact with the desktop, icon grid and calendar for 30 seconds. 4. Log out. 5. Crash files written. ** Changed in: apport (Ubuntu) Status: Incomplete =>

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-12 Thread Daniel van Vugt
And another. ** 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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-12 Thread Daniel van Vugt
I suspect the fix for bug 1974293 (released a minute ago) will hide the problem for now, but my machine does still have one "useless" crash file from last week (attached). ** Attachment added: "_usr_bin_gnome-shell.1000.crash"

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-11 Thread Brian Murray
I sort of recall there being code in apport to not capture crash files during the log out process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2015857 Title: Repeatedly

[Touch-packages] [Bug 2015857] Re: Repeatedly unusable truncated crash files

2023-04-11 Thread Benjamin Drung
Do you have logs and example for it? The linked bugs do not contain any apport logs or the original .crash file. Can you provide an example how to reproduce it? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of