| Summary: | Crash after dismissing "Scanning devices..." and closing KPM | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | wazhai <wazhai> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ismailsahillioglu, jyn514 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/partitionmanager/2482eba7dea7e6f5e5bc1e459a2c610908a596b3 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
wazhai
2018-04-19 02:58:34 UTC
Actually, could this be drkonqi activating erroneously? Ok, I can reproduce this crash. So for me it crashes even earlier 1. Run KPM 2. Enter root password 3. Close "Scanning devices..." with 'X' 5. New ScanProgressDialog reappears and KPM crashes in a second OK, so I think in the kauth branch with which I'm working crash happens for slightly different reasons than in the master branch (which I haven't investigated). In KAuth branch the crash happens only if ScanProgressDialog is closed before DeviceScanner starts. (In reply to Andrius Štikonas from comment #4) > OK, so I think in the kauth branch with which I'm working crash happens for > slightly different reasons than in the master branch (which I haven't > investigated). > > In KAuth branch the crash happens only if ScanProgressDialog is closed > before DeviceScanner starts. Do you think it would be good enough if I just not allow to close ScanProgressDialogWindow until scanning is finished? Git commit 2482eba7dea7e6f5e5bc1e459a2c610908a596b3 by Andrius Štikonas. Committed on 19/04/2018 at 11:29. Pushed by stikonas into branch 'kauth'. Do not allow closing ScanProgressDialog M +8 -1 src/gui/scanprogressdialog.cpp M +2 -2 src/gui/scanprogressdialog.h https://commits.kde.org/partitionmanager/2482eba7dea7e6f5e5bc1e459a2c610908a596b3 I wasn't sure if this is an actual crash in comment #1 with version 3.2.1 because of "signal: Aborted" and because I observed something strange: 1. Perform steps from original report 2. One of the KPM processes crashes/aborts 3. Close drkonqi and that process resumes 4. "No administative privileges" dialogue appears 5. Select "run" 6. KPM opens again However, the fix should take care of this scenario. Still, I thought it's worth mentioning to you. Is this the desired behaviour when one process crashes? (In reply to Ivo C from comment #7) > I wasn't sure if this is an actual crash in comment #1 with version 3.2.1 > because of "signal: Aborted" and because I observed something strange: > > 1. Perform steps from original report > 2. One of the KPM processes crashes/aborts > 3. Close drkonqi and that process resumes > 4. "No administative privileges" dialogue appears > 5. Select "run" > 6. KPM opens again > > However, the fix should take care of this scenario. Still, I thought it's > worth mentioning to you. Is this the desired behaviour when one process > crashes? This was the artefact of Partition Manager needing to restart GUI to run as root, so this does not happen in KAuth branch where GUI does not run as root. And next release should be based on what is now in KAuth branch anyway. *** Bug 403927 has been marked as a duplicate of this bug. *** Created attachment 143860 [details]
New crash information added by DrKonqi
partitionmanager (3.3.1) using Qt 5.15.2
- What I was doing when the application crashed:
I was trying to format an SD memory card on /dev/sdb. However KDE Partition Manager was never ending up with scanning /dev/sdb. Then I had to cancel the scanning process which led to crash.
-- Backtrace (Reduced):
#9 0x00007f88bda77fe7 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#10 QMessageLogger::fatal (this=this@entry=0x7fff68054850, msg=msg@entry=0x7f88bdd7d800 "QThread: Destroyed while thread is still running") at global/qlogging.cpp:893
#11 0x00007f88bda78863 in QThread::~QThread (this=<optimized out>, __in_chrg=<optimized out>) at thread/qthread.cpp:456
#12 0x00007f88bf4f03e7 in DeviceScanner::~DeviceScanner (this=<optimized out>, this=<optimized out>) at /usr/src/debug/kpmcore-3.3.0-2.9.x86_64/src/core/devicescanner.h:33
#13 DeviceScanner::~DeviceScanner (this=<optimized out>, this=<optimized out>) at /usr/src/debug/kpmcore-3.3.0-2.9.x86_64/src/core/devicescanner.h:33
|