Details
-
Bug
-
Resolution: Fixed
-
P3: Somewhat important
-
5.12.8
-
None
Description
A recent conversation on email had shown that a skilled developer has problems to figure out what to do to find out why some parts of the UI are not working properly. The below conversation was not needed if such steps where documented.
The fact that parameters for logging categories are set in the neptune3.service and not in am-confg anymore has to be documented as well
######################
For the crashes, please take look on the logs either via
- journalctl | grep neptune3-ui
or by starting the “neptune3-ui” executable with “-- verbose” in the systemd “neptune3.service”.
I would expect there are some system problems something OS specific. If logs do not tell you anything, send them over.
On Qt Auto side information about debugging is available here:
https://doc-snapshots.qt.io/qtapplicationmanager-dev/debugging.html
and here
https://doc-snapshots.qt.io/qtapplicationmanager-dev/configuration.html
######################
Attachments
For Gerrit Dashboard: AUTOSUITE-837 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
267726,7 | [docs] Adding a new Troubleshoot page | 5.13 | qt-apps/neptune3-ui | Status: MERGED | +2 | 0 |
268931,1 | [docs] Adding a new Troubleshoot page | dev | qt-apps/neptune3-ui | Status: ABANDONED | 0 | 0 |