Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow the viewing of crash reports even when a package is not found

Open
#109 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

Start with usr/lib/linuxmint/mintreport/app.py at lines 722-746 and trace the package validation that prevents the crash report from being displayed. Check how the Bug Tracker button is configured when no package is found; done means the report remains viewable while that button is disabled or unavailable.

Written by the indexing model from the issue text.

Description

https://github.com/linuxmint/mintreport/blob/2265561f9db2c65daa9f2c0eceae68d7c66173bc/usr/lib/linuxmint/mintreport/app.py#L722-L746

Currently this code checks if a valid package can be found and if not it bails on displaying the crash repot.

The package providing /uber/leet/executable-that-crashed could not be found.
If you want to generate a stack trace for this crash report, please reinstall it.

It does so, from what i can gather, solely because mintreport wants a valid package so the Bug Tracker button knows where to send the user should they click on it.

Having the button is great but shouldn't be the sole reason for whether a crash report can be viewed or not.

If a package was not installed via package or cant be found for other unknown reasons. Then the Bug Tracker button should simply be disabled and the report shown because the crash report does exist at the end of the day.

Even the bottom of the panel says...

Developers need to know where the code fails or how to reproduce the issue. Always provide a trace and reliable instructions to trigger/observe the problem

Kind of a bummer to prevent users from seeing traces because a Bug Tracker button can't be resolved to a valid url.

I commented out the check on my local machine and didn't notice any explosions when exploring crash dumps from personal work.

And as a software dev myself I much prefer gui tools when available. I would like to be able to use mintreports to see my crash logs during development.

Dominant language
Python
Stars
30
Forks
26
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/mintreport

All issues in linuxmint/mintreport

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.