@m_pav
Thanks for your insights. Yes the files are old and large and may not be of use any longer but, as I explained in the commentary, they were some of the first I came across exhibiting this problem.I do have other applications that make use of .js/.json files so I do need to get to the bottom of this issue. It is now spreading from a Thunar/Dolphin problem to a wider one that seems to affect other application where some sort of open process via File/Open type dialogue is used. Further it now seems to be causing me a problem with completing Duplicati backups. The actual Duplicati backup completes (ie backup files are copied to the backup location) but then Duplicati tries to calculate some sort of 'quota' by reading the file system. I suspect files of this type (.js/json) are causing this calculation process to fail and thus the backup process to be reported as errored/incomplete. I would like to get to the bottom this issue before starting something new with Duplicati if, as I suspect, the two are related.
Chris
Strange occurence with File Managers
Re: Strange occurence with File Managers
Hi
I have now completely rebuilt my desktop KDE Plasma system using the latest MX Linux 23.2 ISO, a new NVME drive and making use of the BTRFS file system. I have applied the latest updates but this time I have not reapplied any Timeshift backups. I have restored the Documents/Download folders. I still cannot open any folder using Dolphin (or Thunar on my XFCE laptop) which contains .js or .json files. Nor can I open any of these items with any other application (eg KWrite, Visual Studio Code) using the File/Open dialogue.
I am now pretty sure that there is an underlying problem with the way in which these files are being handled BELOW the application layer which is why they all suffer from the same problem. I don't think this is related to MIME handling or previews nor is it file size or content (other than that they are all .js or .json content - valid content or not) related. I does however seem strange that the FlatPak version of Dolphin CAN display these files within their folders but cannot start their associated application due to 'The Activity Manager is not running'.
Chris
I have now completely rebuilt my desktop KDE Plasma system using the latest MX Linux 23.2 ISO, a new NVME drive and making use of the BTRFS file system. I have applied the latest updates but this time I have not reapplied any Timeshift backups. I have restored the Documents/Download folders. I still cannot open any folder using Dolphin (or Thunar on my XFCE laptop) which contains .js or .json files. Nor can I open any of these items with any other application (eg KWrite, Visual Studio Code) using the File/Open dialogue.
I am now pretty sure that there is an underlying problem with the way in which these files are being handled BELOW the application layer which is why they all suffer from the same problem. I don't think this is related to MIME handling or previews nor is it file size or content (other than that they are all .js or .json content - valid content or not) related. I does however seem strange that the FlatPak version of Dolphin CAN display these files within their folders but cannot start their associated application due to 'The Activity Manager is not running'.
Chris
Re: Strange occurence with File Managers
Hi
I don't know if the following helps. I read somewhere to run 'journalctl -f' whilst trying to open the various applications causing problems, so here goes:
Standard Dolphin File Manager (v22.12.03)
Is
Does this help any or am I looking at red herrings ?
Chris
I don't know if the following helps. I read somewhere to run 'journalctl -f' whilst trying to open the various applications causing problems, so here goes:
Standard Dolphin File Manager (v22.12.03)
KwriteApr 16 17:40:22 CMHome systemd[2235]: Started app-org.kde.dolphin-718df28cb7c94dd4a704d4d1b64c6069.scope - Dolphin - File Manager.
Dolphin froze at this point when trying to access folder with .js and .json files in it, then when Dolphin was closed using the X in the top right corner:
Apr 16 17:41:01 CMHome kwin_x11[5752]: kf.notifications: Playing audio notification failed: Destroyed
Apr 16 17:41:01 CMHome kwin_x11[2396]: kwin_core: XCB error: 152 (BadDamage), sequence: 60708, resource id: 14695039, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Apr 16 17:41:01 CMHome systemd[2235]: app-org.kde.dolphin-718df28cb7c94dd4a704d4d1b64c6069.scope: Consumed 30.405s CPU time.
Apr 16 17:41:16 CMHome plasmashell[2443]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Apr 16 17:41:16 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/RunnerResultsList.qml:50:9: Unable to assign [undefined] to int
Apr 16 17:41:16 CMHome plasmashell[2443]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Apr 16 17:41:16 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/RunnerResultsList.qml:50:9: Unable to assign [undefined] to int
Apr 16 17:41:17 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/ItemListView.qml:33: TypeError: Value is null and could not be converted to an object
Apr 16 17:41:19 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/ItemListView.qml:33: TypeError: Value is null and could not be converted to an object
Visual Code StudioApr 16 17:41:19 CMHome systemd[2235]: Started app-org.kde.kwrite-8fcecbf2b1f344c8bb2d2eb58248f0ef.scope - KWrite - Text Editor.
Kwrite froze at this point when trying to access folder with .js and .json files in it, then when Kwrite was closed using the X in the top right corner:
Apr 16 17:41:44 CMHome kwin_x11[5814]: kf.notifications: Playing audio notification failed: Destroyed
Apr 16 17:41:44 CMHome systemd[2235]: app-org.kde.kwrite-8fcecbf2b1f344c8bb2d2eb58248f0ef.scope: Consumed 16.585s CPU time.
Apr 16 17:41:44 CMHome kwin_x11[2396]: kwin_core: XCB error: 152 (BadDamage), sequence: 3646, resource id: 14695555, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Apr 16 17:43:35 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString
Apr 16 17:43:35 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString
Apr 16 17:43:35 CMHome systemd[2235]: Started app-org.kde.dolphin-bba4b4dddecc4984aacd63718e71ece1.scope - Dolphin - File Manager.
Apr 16 17:43:45 CMHome kwin_x11[2396]: kwin_core: XCB error: 152 (BadDamage), sequence: 16341, resource id: 14696628, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Apr 16 17:43:47 CMHome systemd[2235]: app-org.kde.dolphin-bba4b4dddecc4984aacd63718e71ece1.scope: Consumed 1.238s CPU time.
It seems:Apr 16 17:39:04 CMHome systemd[2235]: Started app-code-7e72e48544a1417c88c492e7e83bd7d6.scope - Visual Studio Code - Text Editor.
VS Code opened but when I navigated to the folder containing the .js and .json files it immediate closed and gave:
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.708646:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.710895:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.711069:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.711119:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2)
followed by lots more of the two 'No such file or directory' errors until
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.724190:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.724263:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.724367:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane.: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5484]: [5484:0416/173904.724438:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or directory (2)
Apr 16 17:39:04 CMHome plasmashell[5450]: [main 2024-04-16T16:39:04.727Z] update#setState idle
Apr 16 17:39:25 CMHome kwin_x11[2396]: kwin_core: Failed to focus 0x5000003 (error 3)
Apr 16 17:39:25 CMHome systemd[2235]: app-code-7e72e48544a1417c88c492e7e83bd7d6.scope: Consumed 6.502s CPU time.
Apr 16 17:40:22 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString
Apr 16 17:40:22 CMHome plasmashell[2443]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString
is common to the Dolphin and Kwrite freezes andkwin_core: XCB error: 152 (BadDamage)
applies to the VS Code situation.kwin_core: Failed to focus 0x5000003 (error 3)
Is
the culprit here or is it just a symptom of these applications crashing ?kwin_core
Does this help any or am I looking at red herrings ?
Chris
Re: Strange occurence with File Managers
In order hopefully move this on, I have setup a new Debian 12 system with a KDE desktop. This uses the SAME version of Dolphin as MX-23-2. I have copied all the test files (big and small, incorrect format or not) to this new machine. They all, without exception, are available and can be opened by either double clicking on them and/or via the File /Open dialogue in applications. I have tried with Kwrite, Kate, VS Code and Dolphin - none of these experience the problems I am having with with these same applications in MX-23.
Debian Test System Details:
Debian 12 Bookworm
KDE Plasma Version: 5.27.5
KDE Framework: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0.20-amd64(64-bit)
Graphics Platform: Wayland
Dolphin Version: 22.12.3
MX Linux Details:
MX Linux MX-23-2
Debian Version: 12.5
KDE Plasma Version: 5.27.5
Kernel Version: Kernel: 6.1.0-17-amd64
Dolphin Version: 22.12.3
The main obvious difference is the kernel version. I don't know how to find out the KDE Framework and Qt versions in MX-23
Chris
Debian Test System Details:
Debian 12 Bookworm
KDE Plasma Version: 5.27.5
KDE Framework: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0.20-amd64(64-bit)
Graphics Platform: Wayland
Dolphin Version: 22.12.3
MX Linux Details:
MX Linux MX-23-2
Debian Version: 12.5
KDE Plasma Version: 5.27.5
Kernel Version: Kernel: 6.1.0-17-amd64
Dolphin Version: 22.12.3
The main obvious difference is the kernel version. I don't know how to find out the KDE Framework and Qt versions in MX-23
Chris
Re: Strange occurence with File Managers
... and the solution seems to be:
https://www.mail-archive.com/kde-bugs-d ... 61520.html
Deleting all files and folders in ~/.local/share/mime/ seems to do the trick.
How or why I am not sure - unless you know better :-)
Chris
https://www.mail-archive.com/kde-bugs-d ... 61520.html
Deleting all files and folders in ~/.local/share/mime/ seems to do the trick.
How or why I am not sure - unless you know better :-)
Chris
Re: Strange occurence with File Managers
That is proving it is something in the mime configs.
I personally would MOVE all of that to a backup folder, just in case you need it later.
You probably could do a little detective work in there . mime-cache and types files for one. after that.. I would move it all out and try it out.
I personally would MOVE all of that to a backup folder, just in case you need it later.
You probably could do a little detective work in there . mime-cache and types files for one. after that.. I would move it all out and try it out.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
Re: Strange occurence with File Managers
HI, I seem to be having a similar problem on my systems. I have read through this post and I followed the link mentioned in post #22, https://forum.xfce.org/viewtopic.php?id=17257. The discussion on that link has been updated as of December 2024 with the problem identified and a solution proposed. Unfortunately all of this has gone way above my technical skill level so I do not know how to test this solution on my own. I am hoping someone can review the proposed solution and provide some advice. If this is the wrong way to post about this please advise and I can start a new topic.
Cheers,
Gord
Cheers,
Gord
Code: Select all
System:
Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.5_KDE_x64 Libretto
January 21 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: Gigabyte product: Z590 AORUS PRO AX v: -CF serial: <superuser required>
Mobo: Gigabyte model: Z590 AORUS PRO AX serial: <superuser required> UEFI: American Megatrends
LLC. v: F9 date: 03/10/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: 11th Gen Intel Core i7-11700K bits: 64 type: MT MCP arch: Rocket Lake gen: core 11
level: v4 note: check built: 2021+ process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x62
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 640 KiB
desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1568 high: 4900 min/max: 800/4900:5000 scaling: driver: intel_pstate
governor: powersave cores: 1: 4900 2: 4900 3: 800 4: 800 5: 800 6: 4900 7: 800 8: 800 9: 800
10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 bogomips: 115200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW
sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] vendor: Gigabyte driver: i915 v: kernel
arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: DP-1 empty: HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:4c8a class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-1 model: Dell U2717D serial: <filter> built: 2019 res: 2560x1440 hz: 60 dpi: 109
gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440
min: 720x400
API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: Mesa Intel Graphics (RKL GT1)
direct-render: Yes
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 1-2:2 chip-ID: 0414:a00e alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 class-ID: 0300
chip-ID: 8086:43c8 class-ID: 0403
Device-2: Giga-Byte USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid
API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 06:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-14:10 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
Local Storage: total: 17.28 TiB used: 7.22 TiB (41.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:9 vendor: Western Digital model: WD BLACK SN850X 4000GB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 624361WD temp: 52.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:10 vendor: Western Digital model: WD BLACK SN850X 4000GB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 624361WD temp: 49.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Western Digital model: WDS100T3X0C-00SJG0
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 111110WD temp: 43.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS200T2B0A size: 1.82 TiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 90WD
scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD40EZRZ-19GXCB0 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD30EFRX-68EUZN0 size: 2.73 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A82 scheme: GPT
ID-7: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
scheme: GPT
ID-8: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
scheme: GPT
Partition:
ID-1: / raw-size: 128.25 GiB size: 125.18 GiB (97.60%) used: 20.96 GiB (16.7%) fs: ext4
dev: /dev/nvme2n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 40.4 MiB (42.1%) fs: vfat
dev: /dev/nvme2n1p1 maj-min: 259:1
ID-3: /home raw-size: 297.33 GiB size: 291.61 GiB (98.07%) used: 85.7 GiB (29.4%) fs: ext4
dev: /dev/nvme2n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme2n1p7
maj-min: 259:7
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 3379 pm: dpkg pkgs: 3364 libs: 2007 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 15
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/dropbox.list
1: deb [arch=i386,amd64 signed-by=/etc/apt/keyrings/dropbox.asc] http://linux.dropbox.com/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian/ stable main
No active apt repos in: /etc/apt/sources.list.d/tonfotos.list
Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
Processes: 349 Uptime: 1h 34m wakeups: 6 Memory: 31.14 GiB used: 3.48 GiB (11.2%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Strange occurence with File Managers
@gGord
You should start your own topic. Your equipment and MX version are going to be different from the OP's.
You should start your own topic. Your equipment and MX version are going to be different from the OP's.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
Re: Strange occurence with File Managers
Okay, thanks for the advice. I will try to do a better write up while I am at it.