| Summary: | Apper crashes after updating finishes when using sandboxed APT | ||
|---|---|---|---|
| Product: | [Unmaintained] apper | Reporter: | myndstream |
| Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | minor | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Accessories in Apper | ||
|
Description
myndstream
2020-04-25 20:15:31 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. 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? Created attachment 128511 [details]
Accessories in Apper
(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 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. Oh, it's already there, never mind. 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
This project is unfortunately no longer maintained. If a new maintainer wants to step up and take care, the project is archived here: https://invent.kde.org/system/apper You can just clone it in your private namespace on invent.kde.org and if you have started to work on it and fixed/implemented something get it reviewed and the project unarchived. Sorry for the inconveniences. |