Bug 427016 - Crashes after updating packages with a "Floating point exception".
Summary: Crashes after updating packages with a "Floating point exception".
Status: RESOLVED UNMAINTAINED
Alias: None
Product: apper
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 1.0.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-27 08:39 UTC by Bernie
Modified: 2025-06-10 18:22 UTC (History)
1 user (show)

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


Attachments
Debug report. (7.74 KB, text/plain)
2020-09-27 08:39 UTC, Bernie
Details
New crash information added by DrKonqi (15.70 KB, text/plain)
2020-11-18 02:27 UTC, Jerry Orlando
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernie 2020-09-27 08:39:01 UTC
Created attachment 131955 [details]
Debug report.

SUMMARY

Crashes after updating packages with a "Floating point exception".

STEPS TO REPRODUCE
1. Press "Update" button
2. Wait for updates to finish
3. Crash

OBSERVED RESULT
Crash

EXPECTED RESULT
Remain alive and return to main screen??? I have not observed a succesful completion of the Update task.

SOFTWARE/OS VERSIONS
Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-10-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

ADDITIONAL INFORMATION
See attachment, if you like.
Comment 1 Jerry Orlando 2020-11-18 02:27:49 UTC
Created attachment 133422 [details]
New crash information added by DrKonqi

apper (1.0.0) using Qt 5.11.3

- What I was doing when the application crashed:
I installed Debian 10 stable on a new computer and wanted to get security updates.  I tried selecting one package in Apper under the Updates.  It did some installation steps, then Apper crashed with a floating point error.  Another day I selected a different package and got the same crash error.  The updated packages don't appear in the list to update after the crash so I assume they did update.  I haven't seen the correct behavior without a crash.

-- Backtrace (Reduced):
#4  0x00007f9b273fc879 in QHashData::nextNode (node=node@entry=0x7f9b26fc7ca0) at tools/qhash.cpp:594
#5  0x00007f9b2948cd2a in QHash<QString, PackageModel::InternalPackage>::iterator::operator++ (this=<synthetic pointer>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:328
#6  QHash<QString, PackageModel::InternalPackage>::erase (this=this@entry=0x5650119a2220, it=..., it@entry=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:865
#7  0x00007f9b29485b2b in QHash<QString, PackageModel::InternalPackage>::erase (it=..., this=0x5650119a2220) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:475
#8  PackageModel::clearSelectedNotPresent (this=0x5650119a21e0) at ./libapper/PackageModel.cpp:494
Comment 2 Christoph Cullmann 2025-06-10 18:22:52 UTC
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.