** Description changed:
+ [ Impact ]
+
+ On affected systems, Python crashes will be owned by the crashing group
+ instead of whoopsie. This causes whoopsie to fail reading and uploading
+ the crash report. So a lot of Python crashes were not reporting and
+ keeping us blind.
+
+ [ Test Plan ]
+
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report crashes in a loop
To manage notifi
Proposed changes for the apport.service:
https://github.com/canonical/apport/pull/349
In addition the apport postinst should create and update the permission
to 3777.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Also affects: apport
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/2066995
Title:
apport-gtk keeps prompting to report crashes in a loop
To manage not
I've finally tracked down the permission issue:
In Jammy, we still have an old-school init script that's invoked to set
up the crash handler at the kernel level. As part of the script, there
an unconditional `chmod 1777 /var/run`. However, surprisingly, `chmod
1777` on a 3777 file will result in a
Somehow, I missed the chmod line in that postinst.
My current hypothesis is that apport.service is to blame for dropping
the g+s bit. It's the oneshot service that runs on non-container systems
at startup to set up the kernel crash handler (was an init script before
Lunar), and it forces the 1777
> It seems to boil down to a race condition between the apport postinst
> and the whoopsie postinst, the latter correctly chmoding /var/crash
> to 3777 *if it creates it*.
My read of the postinst is that it correctly chmod's /var/crash
regardless of whether it did the creating:
mk
$ journalctl --no-pager -lu apport-autoreport.service
-- No entries --
$
FTR:
│ ├─app-gnome-update\x2dnotifier-14736.scope
│ │ ├─ 14736 /usr/bin/update-notifier
│ │ ├─1602383 /usr/lib/update-notifier/livepatch-notification
│ │ ├─2268421 /usr/bi
$ ls -ld /var/crash/
drwxrwxrwt 2 root whoopsie 3 Jun 7 15:16 /var/crash/
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report crashes in a loop
To m
Could we have the apport-autoreport.service journal logs as well?
I'm now realizing that the reason I don't get spammed could simply be
that I configured my system to report everything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note that I still don't understand why it loops, whereas on my system
whoopsie will happily create the upload/uploaded files (with a NULL ID).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Tit
I found the wild goose!
Your Python crashes are owned by vorlon:vorlon, which is why whoopsie
cannot read them. I'm guessing that /var/crash doesn't have the 3777
permissions that would allow inheriting the whoopsie GID. My own system
has 1777, whereas fresh containers seem to be correctly using 3
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (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/2066995
Title:
app
> Steve, do you still have the crash file on your system?
No, but I have no trouble generating more of them on demand.
> If so, could you give us its mod and owner?
-rw-r- 1 vorlon vorlon 41580 Jun 3 17:51 /var/crash/_usr_bin_grep-
merges.1000.crash
--
You received this bug notification b
Interestingly, I see the same "could not be opened" patter in my recent
logs, all for crashes within Python executables.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps
Steve, do you still have the crash file on your system? If so, could you
give us its mod and owner?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report
> Can you provide the journal log from during that time frame?
For what service? For whoopsie, I see:
May 23 13:58:13 homer systemd[1]: Started whoopsie.service - crash report
submission.
May 23 13:58:13 homer whoopsie[147832]: [13:58:13] Using lock path:
/var/lock/whoopsie/lock
May 23 13:58:13
> Did you remove the content there?
I did not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report crashes in a loop
To manage notifications about thi
Why is ApportLog empty? Did you remove the content there? Otherwise it
means that /var/log/apport was empty (despite apport collecting
crashes).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
T
Can you provide the journal log from during that time frame? Did that
application crash multiple times?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to rep
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report crashes in a loop
To manage notifications about this bug go to:
http
21 matches
Mail list logo
