Disabling 'Report to Canonical: App crashes and errors' sets wrong core_pattern

Bug #1654479 reported by Daniel van Vugt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
New
Low
Unassigned
apport (Ubuntu)
New
Low
Unassigned

Bug Description

Disabling 'Report to Canonical: App crashes and errors' sets wrong core_pattern.

On a fresh boot with error reporting disabled by default:
# cat /proc/sys/kernel/core_pattern
/bad_core_pattern

Enable 'Report to Canonical: App crashes and errors':
# cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %P

Disable 'Report to Canonical: App crashes and errors':
# cat /proc/sys/kernel/core_pattern
core

I think it should be reverting to "/bad_core_pattern" instead of "core". Because "core" could fill the filesystem with core files (if ulimit allows it).

affects: ubuntu-system-settings (Ubuntu) → apport (Ubuntu)
Revision history for this message
Brian Murray (brian-murray) wrote :

There's noting in apport that writes "bad_core_pattern". I also looked in ubuntu-system-settings and didn't find anything there either.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

This is set per the fix for lp:1505302 but that also sets suid_dumpable to 0. The core pattern seems moot in that case?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Indeed, it sounds like that would make this moot. So it's an invisible issue, but still worth fixing. We still don't want core files unexpectedly appearing if the other factors happen to go away in future.

Changed in canonical-devices-system-image:
importance: Undecided → Low
Changed in apport (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.