mstoeck3/autopsy-flatpak
1
0
Fork 0
mirror of https://github.com/overcuriousity/autopsy-flatpak.git synced 2025-07-06 21:00:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6682 from APriestman/fontSizeDoc

Browse Source 
Add section on adjusting font size.
This commit is contained in:
Richard Cordovano 2021-01-29 12:29:53 -05:00 committed by GitHub
commit 8db460c0a6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/doxygen-user/troubleshooting.dox
View File

@ -16,7 +16,25 @@ If you are experiencing an error, we encourage you to post on the forum (https:/
<li>If there were any errors in the \ref troubleshooting_logs "logs"
</ul>
\section troubleshooting_user_folder Deleting the Autopsy User Folder
\section troubleshooting_specific_issues Specific Issues
\subsection troubleshooting_fond_size Font Size Too Small in Windows
Make the following changes if the application is hard to navigate in High DPI systems:
<ol>
<li>Right-click on the application icon on your Desktop, Start Menu, etc.
<li>Choose Properties.
<li>Go to Compatibility tab.
<li>Click "Change high DPI settings" button.
<li>Select "Override high DPI scaling behavior".
<li>Change the "Scaling performed by:" drop down box to "System".
<li>Restart Autopsy.
</ol>
\section troubleshooting_general General Troubleshooting
\subsection troubleshooting_user_folder Deleting the Autopsy User Folder
If Autopsy starts behaving strangely, stops loading entirely, or menu items go missing, you probably need to delete your user folder. Doing so essenitally gives you a fresh installation. On Windows the user folder is located in "C:\Users\(user name)\AppData\Roaming\autopsy".
@ -30,7 +48,7 @@ Note that if you delete this folder you will lose all your Autopsy settings incl
Alternately, you could copy the fresh user folder somewhere, move your old version back, and replace folders until it works again.
\section troubleshooting_logs Viewing the Logs
\subsection troubleshooting_logs Viewing the Logs
The logs are generally the most helpful in figuring out why an error is occurring. There are two sets of logs - the system logs and the case logs. There is an option in the UI to open the log folder:
@ -70,7 +88,7 @@ Caused by: java.sql.SQLException: ResultSet closed
If the error message doesn't help you solve the problem yourself, please post to the <a href="https://sleuthkit.discourse.group/">forum</a> including the full stack trace (if available).
\section troubleshooting_stack Creating a Thread Dump
\subsection troubleshooting_stack Creating a Thread Dump
You can also generate a thread dump of the current state. This is useful if an ingest module or other process seems to be stuck. To generate a thread dump, go to "Help" then "Thread Dump" in the UI.