Bug 420589 - Apper crashes after updating finishes when using sandboxed APT
Summary: Apper crashes after updating finishes when using sandboxed APT
Status: REPORTED
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR minor
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-25 20:15 UTC by myndstream
Modified: 2020-08-01 14:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Accessories in Apper (8.77 KB, image/png)
2020-05-16 13:16 UTC, myndstream 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description myndstream 2020-04-25 20:15:31 UTC 
SUMMARY
I get this error almost always after installing or updating a package:
Application: Apper (apper), signal: Segmentation fault
This is happening since I enabled APT::Sandbox::Seccomp as described [url=https://unix.stackexchange.com/a/534993/233262]here[/url].

STEPS TO REPRODUCE
1. On Debian10/KDE enable APT::Sandbox::Seccomp
2. Install or update a package with apper

OBSERVED RESULT
It crashes and asks me to submit a bug report which I can't submit with reportbug due to it having collected too little information.

EXPECTED RESULT
Apper shouldn't crash.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.5
KDE Plasma Version: 5.14
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.en.html#apt-sandboxing
Comment 1 myndstream 2020-04-27 22:08:53 UTC 
Right now it only seems to crash when updating packages but not when installing new apps. It crashed after every update. I'll start apper over the console for the next update in case there are some messages that might be relevant.
Comment 2 myndstream 2020-05-07 15:43:01 UTC 
It also crashes after updating in a Kali Linux virtual machine. I didn't configure apt to use seccomp and pretty much didn't configure anything in that vm. There it generates crash information but it is considered "probably not useful". Could it be due to some firewall rule? The updates get installed just fine. What is Apper doing at the end of updates that might cause it to crash?
Comment 3 myndstream 2020-05-16 13:16:44 UTC 
Created attachment 128511 [details]
Accessories in Apper
Comment 4 myndstream 2020-05-16 13:23:17 UTC 
(In reply to myndstream from comment #3)
> Created attachment 128511 [details]
> Accessories in Apper

How can I delete the attachment I added here? It was meant to go to here: https://bugs.kde.org/show_bug.cgi?id=421616
Comment 5 Christoph Feck 2020-05-16 15:37:13 UTC 
Attachments are usually only deleted by system admins when private information got accidentally shared. In this case, I just suggest to add the image again to the related bug.
Comment 6 Christoph Feck 2020-05-16 15:37:54 UTC 
Oh, it's already there, never mind.
Comment 7 myndstream 2020-08-01 14:34:09 UTC 
Recently I get this error when I try to report the bug (can't submit it due to lack of data):

> Application: Apper (apper), signal: Floating point exception