You opened Dolphin and nothing matches your workflow
You switched to Fedora KDE and launched Dolphin. The file manager works, but it feels wrong. You click a folder and a new window pops up instead of a tab. The sidebar is empty. Hidden files are invisible. You right-click and the context menu doesn't have the options you expect. You try to find a setting to fix this, but the menus are dense and the terminology is unfamiliar. You need to bend Dolphin to your workflow without breaking the KDE integration.
This happens when the default configuration doesn't align with your habits. Dolphin is powerful, but it hides advanced options behind nested dialogs. It also exposes a command-line interface and a plain-text configuration file for users who prefer direct control. You can fix the behavior through the GUI, script it with terminal commands, or edit the config file directly. Each method has a place.
What's actually happening
Dolphin is a KDE application. It stores all user preferences in a KConfig file located at ~/.config/dolphinrc. This file uses an INI-style format with sections and key-value pairs. The GUI writes to this file whenever you change a setting. You can also read and write to this file using kwriteconfig6 from the terminal.
Dolphin relies on kio (KDE Input/Output) for file operations. kio handles local files, network shares, archives, and remote protocols. If kio fails, Dolphin cannot list files or perform actions. Configuration errors usually affect the UI or behavior. kio errors usually affect functionality. Distinguishing between the two saves time.
Fedora ships with KDE Plasma 6. The configuration tools are versioned. You must use kwriteconfig6 and kreadconfig6. Tutorials referencing kwriteconfig5 apply to older releases and will fail on current Fedora. The config file path remains ~/.config/dolphinrc regardless of the Plasma version.
Think of dolphinrc as a personal registry for the file manager. The GUI is a safe editor. The terminal tools are precise scripts. The file itself is the source of truth.
Configure via the GUI
The GUI is the fastest way to explore options and see changes immediately. Open Dolphin and navigate to Settings > Configure Dolphin. This opens the configuration dialog. The dialog mirrors the structure of dolphinrc. Changes apply instantly to the current session and persist across reboots.
Use the General section to control window behavior. Enable Open folders in tabs to prevent window sprawl. Set Start in to define the default location. Check Show hidden files if you work with dotfiles regularly.
Use the Sidebar section to manage panels. Enable Places for quick access to home, documents, and network locations. Enable Tags if you use KDE's tagging system. Enable Filters to search within the current directory. The sidebar width is adjustable by dragging the edge, but the default size is stored in the config.
Use the View Modes section to customize details, icons, and columns. You can set default sort orders, enable column visibility, and adjust icon sizes. Each view mode has its own configuration block. Changes here affect all folders using that view mode.
Use the Advanced section to manage plugins and services. Enable Bulk Rename for renaming multiple files. Enable Git integration if you use version control. Disable unused plugins to reduce startup time.
Reboot before you debug. Half the time the symptom is gone.
Configure via the terminal
Terminal configuration is useful for scripting, automation, or applying settings without opening the GUI. kwriteconfig6 reads and writes to dolphinrc safely. It handles escaping and formatting automatically. You can chain commands to apply multiple settings at once.
Here's how to force Dolphin to open folders in tabs and enable hidden files by default.
# Force tab behavior for all navigation actions
kwriteconfig6 --file dolphinrc --group General --key OpenUrlInTab true
# Enable hidden files globally
kwriteconfig6 --file dolphinrc --group General --key ShowHiddenFiles true
# Set the default view mode to Details
kwriteconfig6 --file dolphinrc --group General --key ViewPropsMode DetailsView
# Launch Dolphin to verify the changes take effect
dolphin --new-window
You can also use dolphin command-line flags to control behavior for a single invocation. These flags do not change the configuration. They only affect the current launch.
# Open a specific path in a new tab of an existing window
dolphin --new-tab /var/log
# Open a path and select a specific file
dolphin --select /home/user/documents/report.txt
# Open Dolphin in a new window regardless of settings
dolphin --new-window /tmp
Use kwriteconfig6 when you are setting up a new machine or standardizing a workflow across multiple systems. The commands are reproducible and version-control friendly.
Run kwriteconfig6 --read before you change anything. Verify the current value first.
Inspect and edit the config file
You can edit ~/.config/dolphinrc directly with a text editor. This gives you full control over every key. It also carries risk. A syntax error can prevent Dolphin from starting. Always backup the file before editing.
Here's how to backup the config and inspect the General section.
# Create a backup before making manual edits
cp ~/.config/dolphinrc ~/.config/dolphinrc.bak
# Display the General section to review current settings
grep -A 20 '^\[General\]' ~/.config/dolphinrc
The config file uses INI syntax. Sections are enclosed in brackets. Keys are assigned values with an equals sign. Comments start with a hash.
[General]
# Global defaults for the file manager
OpenUrlInTab=true
ShowHiddenFiles=true
ViewPropsMode=DetailsView
# ...other keys omitted for clarity
[PlacesPanel]
# Configuration for the sidebar places panel
ShowTrash=true
ShowRemovableDevices=true
Edit the file when you need to migrate settings from another machine or batch-edit multiple keys. Use a reliable editor like nano or vim. Avoid word processors that add formatting characters.
Backup dolphinrc before mass edits. A corrupt config file can prevent Dolphin from starting.
Verify the configuration
After changing settings, verify they applied. The GUI shows the current state. The terminal can read specific keys. kreadconfig6 is the read counterpart to kwriteconfig6.
Here's how to verify the tab setting and hidden files setting.
# Read the OpenUrlInTab key to confirm it is true
kreadconfig6 --file dolphinrc --group General --key OpenUrlInTab
# Read the ShowHiddenFiles key to confirm it is true
kreadconfig6 --file dolphinrc --group General --key ShowHiddenFiles
# List all keys in the General section for a full audit
kreadconfig6 --file dolphinrc --group General --list
If the output doesn't match your expectation, check for typos in the key name. KConfig keys are case-sensitive. OpenUrlInTab is correct. openurlintab will return nothing.
If Dolphin ignores the setting, check for conflicting plugins or kio errors. Some settings are overridden by active plugins. Disable plugins one by one to isolate the conflict.
Check kio logs if the file list is empty. The issue is usually the backend, not the view.
Common pitfalls and errors
Configuration issues fall into three categories: config corruption, kio failures, and version mismatches.
Config corruption happens when the file contains invalid syntax. Dolphin may fail to start or revert to defaults. You'll see a crash dialog or an empty window. Restore the backup to fix this.
# Error output when dolphinrc is malformed
# This appears in the terminal or crash dialog
kconfig.core: Could not parse config file "/home/user/.config/dolphinrc"
kio failures happen when the backend cannot access a resource. You'll see a progress bar that hangs or an error message. Check journalctl for kio errors.
# Check recent kio errors in the journal
journalctl -xeu plasma-kio | grep -i error
Version mismatches happen when you use kwriteconfig5 on a Plasma 6 system. The command fails silently or writes to the wrong location. Always use kwriteconfig6 on Fedora.
If you see Could not find service 'dolphin', check your installation. Run rpm -q dolphin to verify the package is installed. Reinstall if necessary.
# Verify Dolphin is installed and check the version
rpm -q dolphin
# Reinstall Dolphin if the package is corrupted
sudo dnf reinstall dolphin
Trust the package manager. Manual file edits drift, snapshots stay.
When to use which method
Use the GUI when you are exploring options and want visual feedback. Use kwriteconfig6 when you are scripting a setup or need to apply a setting without opening the app. Use the config file when you are migrating settings from another machine or need to batch-edit multiple keys. Use dolphin --help when you need to pass a specific path or action to the file manager. Stay on the GUI for daily tweaks. Switch to the terminal for automation.