New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Omni Issue Tracker for OMLx Rock/5.0 LXQt desktop #2952
Comments
This was a test on Vivobook ASUSLaptop M1605YA installed from Rock/5.0 znver1 LXQt iso.
This is the entire journal log: |
This issue has been mentioned on OpenMandriva forum. There might be relevant details there: https://forum.openmandriva.org/t/omni-tracker-for-issues-with-omlx-lxqt-desktop/5169/1 |
Closing, lack of interest. |
OpenMandriva version:
All with LXQt desktop
Describe the bug:
Omni Tracker bug report to track issues and enhancements for OMLx LXQt desktop.
Steps to reproduce:
Install your preferred version of LXQt ISO and test. Report and help resolve issues. Suggest enhancements.
Observed behavior:
Write your observed behavior about any issue or enhancement in a post and include OMLx version, ISO build ID number, and any relevant logs.
Expected behavior:
A well working but minimal desktop.
Additional comment:
Reports should include:
What you are testing on: What version of OMLx, please include the Build ID number of the iso you used. Is this the iso 'Live' or an installed system, is this on hardware or in VirtualBox or other VM?
Detailed description. This does not have to be long but there needs to be enough for someone to work with. This is a work project.
Any and all relevant logs and screen-shots. It would be wise to include the entire journal log with any report or post.
If you do not know how to do any of this please ask here and we will walk you through this.
Any terminal output longer than about 20-30 lines can be put in a .txt file and attached to your report.
Developers can not fix "it's broke" they need a cause or otherwise something to work on. That is what the screen-shots and especially the logs are for.
Logs and screenshots if relevant
Please do include logs and screenshots as much as possible.
The text was updated successfully, but these errors were encountered: