| Summary: | KBibTeX crashes when closing after saving | ||
|---|---|---|---|
| Product: | [Applications] KBibTeX | Reporter: | Erik Quaeghebeur <bugs.kde.org> |
| Component: | General | Assignee: | Thomas Fischer <fischer> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version First Reported In: | 0.9 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Erik Quaeghebeur
2019-09-23 06:38:04 UTC
I have not been able to reproduce this crash. Any ideas how to reproduce this crash without keeping KBibTeX a few days open? Also, to get more details, I recommend to launch KBibTeX from the command line and append the output of the last 20 lines or so. For example, File::property mentioned in the crash report prints out a warning if it thinks there is something wrong. (In reply to Thomas Fischer from comment #1) > […] Any ideas how to reproduce > this crash without keeping KBibTeX a few days open? No, I cannot reproduce it willingly either. Every so often (every month?), I get a crash like this. > Also, to get more details, I recommend to launch KBibTeX from the command > line and append the output of the last 20 lines or so. For example, > File::property mentioned in the crash report prints out a warning if it > thinks there is something wrong. Is that debug output also available in the logs? (It is a bit inconvenient to start from a console and keep that console around for multiple days.) (In reply to Erik Quaeghebeur from comment #2) > Is that debug output also available in the logs? (It is a bit inconvenient > to start from a console and keep that console around for multiple days.) One way to mitigate this is to create a small shell script which launches KBibTeX and redirects the program's output into (temporary) logfiles: #!/usr/bin/env bash /usr/bin/kbibtex >/tmp/kbibtex.log 2>&1 Store this script at one of the usual places, make it executable, and add this script to your preferred application launcher. Use this new "application" by default instead of the regular application entry for KBibTeX. Whenever KBibTeX crashes, the logfile will contain the latest console output which then can be attached to the bug report. Any news on this bug? Have you tested running this script? (In reply to Thomas Fischer from comment #3) > (In reply to Erik Quaeghebeur from comment #2) > > Is that debug output also available in the logs? (It is a bit inconvenient > > to start from a console and keep that console around for multiple days.) > One way to mitigate this is to create a small shell script which launches > KBibTeX and redirects the program's output into (temporary) logfiles: (In reply to Thomas Fischer from comment #4) > Any news on this bug? Have you tested running this script? I haven't been running KBibTeX as much the last period and have had no more crashes. (In reply to Erik Quaeghebeur from comment #5) > (In reply to Thomas Fischer from comment #4) > > Any news on this bug? Have you tested running this script? > I haven't been running KBibTeX as much the last period and have had no more > crashes. Any news here? (In reply to Thomas Fischer from comment #6) > > Any news here? No more crashes in the meantime. |