-
- | Filtering Type |
- Description |
-
-
- | Filtering by period |
- to filter in the order of log generating date
-
- - Options include: "All", "Today", "3 days", "1 week", "1 month", and "3 months". Default option is "All".
- - Applicable for: "period" is not displayed only for boot logs, other kinds of logs support filtering by period.
-
- |
-
-
- | Filtering by level |
- to filter by seriousness levels of events
-
- - Options include: "All", "Emergency", "Alert", "Critical", "Error", "Warning", "Notice", "Info"and "Debug". Default option is "Info".
- - Applicable for: system logs and application logs
-
- |
- | Filtering by status |
-
-
- - Options include: "All", "OK", and "Failed". Default option is "All".
- - Applicable for: boot logs only
-
- |
- | Filtering by application list: |
- to filter log files of applications, default option is the first one.
- Applicable for: application logs only. |
-
- | Filtering by event type |
-
-
- - Options include: "All", "Login", "Reboot", and "Shutdown", the default option is "all".
- - Applicable for: boot-shutdown events only.
-
- |
-
-
+## Overview
-### View Logs
-
-#### System Log
-
-1. On the main interface, click **System Log**.
-2. You can see a list of system logs which are detailed by "Level", "Process", "Date and Time", and "Info".
-3. Click a log, you can see its particular info below the list, including process, time, user, PID, level and info.
-
-
-
-#### Kernel Log
-
-1. On the main interface, click **Kernel Log**.
-2. Input login password in the pop-up authentication window.
-3. You can view the status and information of kernel logs.
-4. Click a log, you can see its particular info below the list, including process, time, user and info.
-
-
-
-
+The log collection tool is a small utility responsible for collecting logs generated during program execution, such as relevant information about the operating system and applications during startup, operation, etc. By analyzing detailed log information, you can quickly find the cause of failures and resolve issues.
-#### Boot Log
+## Getting Started
-1. On the main interface, click **Boot Log**.
-2. Input password in the popped up authentication window.
-3. You can view the status and information of boot logs.
-4. Click a log, you can see its particular info below the list, including user, status and info.
+You can run, close the log collection tool, or create shortcuts in the following ways.
+### Running the Log Collection Tool
+1. Click the launcher icon on the taskbar  to enter the launcher interface.
-
+2. Scroll up or down with the mouse wheel or search to find the log collection tool icon , and click to run it.
-#### dpkg Log
+3. Right-click on the icon, and you can:
-1. On the main interface, click **dpkg Log**.
-2. You can view time and information of dpkg logs.
-3. Click a log, you can see its particular info below the list, including time, user, action and info.
+ - Click **Send to Desktop** to create a shortcut on the desktop.
+ - Click **Send to Taskbar** to pin the application to the taskbar.
+ - Click **Start Automatically** to add the application to the startup items, so it runs automatically when the computer starts.
-
+### Closing the Log Collection Tool
-#### Xorg Log
+- In the log collection tool interface, click  to exit the log collection tool.
+- Right-click on the taskbar , and select **Close All** to exit the log collection tool.
+- In the log collection tool interface, click  and select **Exit** to close the tool.
-1. On the main interface, click **Xorg Log**.
-2. You can view time and information of Xorg logs.
-3. Click a log, you can see its particular info below the list, including user, time and info.
+## Operations Introduction
-
+>  The log collection tool supports the display of various log types. Due to differences in system versions or architectures, the available log types may vary. Please refer to the final page for the specific features.
+>
+>  Depending on the log type, the available filtering options, whether the log can be displayed in the file manager, and whether log clearing is supported may differ. Please refer to the final page for specific functionalities.
+>
+> The following section will introduce the operation of the log collection tool with **system logs** and **kernel logs** as examples.
-#### Application Log
+### Search Logs
-1. On the main interface, click **Application Log**.
-2. You can view level, time, source and information of application logs.
-3. Click a log, you can see its particular info below the list, including source, user, time, level and info.
+1. In the log collection tool search box, click .
+2. Enter keywords to display search results in real-time.
+3. Click  to clear the search content.
-
+
+### Filter Logs
-#### Boot-Shutdown Event
+1. In the log collection tool’s top filter bar, select the option you want to filter by.
+2. After clicking or selecting a filter, the log collection tool will immediately display the filtered results.
-1. On the main interface, click **Boot-Shutdown Event**.
-2. You can view event type, username, time and information of boot-shutdown events.
-3. Click a log, you can see its particular info below the list, including user, time, event type, username and info.
-
+
-#### Other Logs
-
-1. On the main interface, click **Other Logs**.
-2. Other logs display the file name and modification date of the log file in a file list format. Display similar log files in folder format.
-3. After selecting a file, you can view its detailed content. Drag and drop the file list and detailed content boundary to synchronize and adjust the size of the two regions.
+### View Logs
-
+1. In the log collection tool interface, click on the log type menu you wish to view, and the right-side list will display all logs of that type.
+2. Left-click on a log, and you can view the detailed information of the log in the lower section of the tool.
+
-### Custom logs
+### Custom Logs
-The custom log function is to add log files to the log collection tool for viewing and exporting. Custom logging compatible with Gsettings and Dconfig configurations.
+The custom log feature allows you to add log files to the log collection tool for viewing and exporting. Custom logs are compatible with both Gsettings and Dconfig configurations.
-**Gsettings configuration**
+**Gsettings Configuration**
-1. Execute the Gsettings configuration setting command on the terminal, fill in the log file path in "[]", for example: ['a. log ',' b. log ',' c. log '].
+1. Execute the Gsettings configuration command in the terminal. Replace the “[]” with the log file paths, for example: ['a.log', 'b.log', 'c.log'].
```shell
gsettings set com.deepin.log.viewer customlogfiles []
```
-2. On the main interface, click **Custom Log** to discover the existing configuration.
+1. In the log collection tool interface, click **Custom Logs**, and you will see the existing configuration.
-**Dconfig configuration**
+**Dconfig Configuration**
-1. Execute the Dconfig configuration setting command on the terminal, fill in the log file path in "[]", for example: ["a.log", "b. log", "c.log"]
+1. Execute the Dconfig configuration command in the terminal. Replace the “[]” with the log file paths, for example: ["a.log", "b.log", "c.log"].
```shell
dde-dconfig --set -a org.deepin.log.viewer -r org.deepin.log.viewer -k customLogFiles -v '["a.log","b.log","c.log"]'
```
-2. On the main interface, click **Custom Log** to discover the existing configuration.
-
+1. In the log collection tool interface, click **Custom Logs**, and you will see the existing configuration.
### Export Logs
-You can export logs to local computer so as to help you analyze, locate and solve problems.
+The export log function allows you to export the log query results to the local system, helping you analyze, locate, and resolve issues.
+
+1. Select a log type and click the **Export** button in the upper-right corner of the interface.
+2. If a password authentication window pops up, enter your user login password and click **OK**.
+3. In the pop-up window, select the storage location and click **Save**.
-1. Select a log type and click **Export** in the upper right corner.
-2. Input login password in the pop-up authentication window (if any) and click **Confirm**.
-3. Select the storing path in the pop-up window, and click **Save**.
+>  Note: You can also click the **Export All** button in the title bar  to export all logs.
-> Notes: you can also click the "Export All" button  on the title bar to export system logs, kernel logs, boot logs, dpkg logs, Xorg logs, application logs and logs of boot-shutdown events as well.
+
-### Refresh
+### Refresh Logs
-You can refresh the logs manually and automatically. For auto refresh, you can set the frequency.
+Logs can be refreshed manually or automatically. The frequency of automatic refresh can be customized.
-#### Manual Refresh
+#### Manual Log Refresh
-Click the "Refresh Now" button  on the title bar, or right-click on a log type and select **Refresh** to reload the log list.
+Click the **Refresh** button in the title bar ; or right-click on a log type and select **Refresh** to refresh the logs.
-#### Auto Refresh
+
-1. Click  > **Refresh interval** in the main interface.
-2. Select a proper refresh interval from **10 sec**, **1 min**, and **5 min**. Or select **No refresh** to stop auto refreshing.
+#### Automatic Log Refresh
+1. In the log collection tool interface, click  > **Refresh Frequency**.
+2. Select the automatic refresh frequency: **Every 10 seconds**, **Every 1 minute**, or **Every 5 minutes** to refresh the logs. Select **Do not refresh** to stop automatic log refreshing.
+
### Display in File Manager
-**Display in file manager** is only applicable for kernel log, boot log, dpkg log, Xorg log and application log.
+With the **Display in File Manager** feature, you can view the raw log files of certain logs.
-1. On the interface of Log Viewer, select a log type in the left panel and right-click.
-2. Select **Display in file manager**, the folder path of the current log will be opened.
+1. In the log collection tool’s left-side navigation bar, right-click on a log type.
+2. Select **Display in File Manager** to navigate to the current log’s storage location.
-
+
### Clear Log
-**Clear log** is only applicable for kernel log, boot log, dpkg log, Xorg log and application log.
-
-1. On the interface of File Manager, select a log type in the left panel and right-click.
-2. Select **Clear log**, click **Confirm** button in the pop-up window to clear current logs.
-3. If authentication window pops up, please input password to finish the operation.
+1. In the log collection tool’s left-side navigation bar, right-click on a log type.
+2. Select **Clear Log**.
+3. A prompt will appear asking you to confirm clearing the logs. Click **OK**.
+4. If a password authentication window pops up, enter your user login password and click **OK**.
+
## Main Menu
-In the main menu, you can [set refresh intervals](#Auto Refresh), switch themes, view help manual, and so on.
-
-### Theme
+In the main menu, you can [set the refresh frequency](https://chatgpt.com/c/677b9ca1-43e8-8009-91e4-3cafdf878f9c#auto-refresh-logs), switch window themes, view the help manual, and more.
-The window theme includes Light Theme, Dark Theme and System Theme.
+### Themes
-1. Click on the interface.
-2. Click **Theme** to select one.
+The window themes include Light Theme, Dark Theme, and System Theme.
+1. In the log collection tool interface, click .
+2. Select **Theme** and choose a theme color.
### Help
-Click Help to get the manual, which will help you further know and use Log Viewer.
-
-1. Click on the interface.
-2. Click **Help** to view the manual.
+To view the help manual and further understand how to use the log collection tool:
+1. In the log collection tool interface, click .
+2. Select **Help**.
+3. View the log collection tool's help manual.
### About
-1. Click on the interface.
-2. Click **About** to view version information and introduction about Log Viewer.
+1. In the log collection tool interface, click .
+2. Select **About**.
+3. View the version and introduction of the log collection tool.
### Exit
-1. Click on the interface.
-2. Click **Exit**.
+1. In the log collection tool interface, click .
+2. Select **Exit**.
+
+------
+Let me know if you'd like any additional modifications!
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/applog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/applog.png
deleted file mode 100755
index e2142409..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/applog.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/auto_refresh.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/auto_refresh.png
new file mode 100644
index 00000000..fb6e9698
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/auto_refresh.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/bootlog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/bootlog.png
deleted file mode 100755
index 0e15d4f3..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/bootlog.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/delete_log.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/delete_log.png
new file mode 100644
index 00000000..8611eefa
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/delete_log.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/dpkglog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/dpkglog.png
deleted file mode 100755
index 7c4dda1a..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/dpkglog.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/export_log.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/export_log.png
new file mode 100644
index 00000000..6daa9f51
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/export_log.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/filter_log.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/filter_log.png
new file mode 100644
index 00000000..e9aebd83
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/filter_log.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/kernlog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/kernlog.png
deleted file mode 100755
index 1a1e8139..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/kernlog.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/otherslog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/otherslog.png
deleted file mode 100644
index b166501b..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/otherslog.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/power_event.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/power_event.png
deleted file mode 100755
index f0bcc79b..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/power_event.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/refresh_log.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/refresh_log.png
new file mode 100644
index 00000000..bff1eab1
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/refresh_log.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/rightclick.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/rightclick.png
deleted file mode 100755
index c36f84ce..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/rightclick.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/search_log.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/search_log.png
new file mode 100644
index 00000000..97005c06
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/search_log.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/show_in_fileManager.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/show_in_fileManager.png
new file mode 100644
index 00000000..dc5a91f0
Binary files /dev/null and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/show_in_fileManager.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/syslog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/syslog.png
old mode 100755
new mode 100644
index 5c0d8929..fd583107
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/syslog.png and b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/syslog.png differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/xorglog.png b/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/xorglog.png
deleted file mode 100755
index 8e010aac..00000000
Binary files a/application/assets/deepin-log-viewer/log-viewer/zh_CN/fig/xorglog.png and /dev/null differ
diff --git a/application/assets/deepin-log-viewer/log-viewer/zh_CN/log-viewer.md b/application/assets/deepin-log-viewer/log-viewer/zh_CN/log-viewer.md
index 76bbe0b6..f1004dcc 100755
--- a/application/assets/deepin-log-viewer/log-viewer/zh_CN/log-viewer.md
+++ b/application/assets/deepin-log-viewer/log-viewer/zh_CN/log-viewer.md
@@ -4,11 +4,9 @@
日志收集工具是负责收集程序运行时所产生日志的小工具，如操作系统和应用程序在启动、运行等过程中的相关信息。您可以通过分析详细日志信息，快速地找到故障原因并解决问题。
-
-
## 使用入门
-您可以通过以下方式运行或关闭日志收集工具，或者创建快捷方式。
+您可以通过以下方式运行、关闭日志收集工具，或创建快捷方式。
### 运行日志收集工具
@@ -27,134 +25,37 @@
## 操作介绍
+> 日志收集工具支持多种日志类型的展示。由于系统版本或架构的不同，可查看的日志类型可能有所差异，具体功能请以最终页面显示内容为准。
+>
+>  由于日志类型的不同，提供的筛选项、是否能在文件管理器中显示及是否支持清除日志的功能也有所区别，具体功能请参照最终页面的显示内容。
+>
+> 下文将以系统日志和内核日志 **为例** ，介绍日志收集工具的操作方式。
+
### 搜索日志
1. 在日志收集工具搜索框中，单击 。
2. 输入关键字，实时显示搜索结果。
3. 单击  ，则清空搜索内容。
-
+
### 筛选日志
-您可以通过 **周期**、**级别**、**状态**、**应用列表** 或 **事件类型** 来筛选日志。
-