Where Does Konversation Store Settings and Logs?
Konversation splits settings and channel logs across konversationrc and its data folder. Config, logs, and backup files.
Last updated
Konversation follows KDE's split-brain convention: settings in ~/.config/konversationrc, application data in ~/.local/share/konversation. Identities, server lists and appearance live in the rc file; channel and query logs accumulate in the data folder, one file per session that appends on revisit.
KDE's own beta-testing docs name exactly these two paths as the backup pair, which is the strongest possible confirmation. Ancient guides point at ~/.kde/share instead, the pre-Frameworks location that modern builds abandoned. Konversation is a Linux-first client; back up both spots together and nothing else is needed.
Where Konversation stores this, by platform
~/.local/share/konversation
konversationrc holds identities, servers and appearance; the data folder holds per-session logs plus scripts and themes. KDE names these two as the backup pair. Pre-Frameworks guides referencing ~/.kde are obsolete. Close the client before copying so logs flush.
Frequently asked questions
how do i move konversation to a new pc
Copy konversationrc plus the ~/.local/share/konversation folder to the new machine with Konversation closed. Identities, server entries and log history travel together. DCC download folders and scripts referenced by absolute path need recreating if locations differ.
how do i enable konversation logging
Open Settings, Configure Konversation, Behavior, Logging. Each server, channel and query logs to its own file which appends on revisit. Log viewer actions include saving elsewhere, refreshing and wiping the on-disk file. Disable per-channel if disk usage from years of idling bothers you.
why do guides mention kde share apps konversation
That is the KDE4-era location. Modern Konversation on Frameworks 5 and 6 uses ~/.config/konversationrc and ~/.local/share/konversation. Old guides and old dotfiles reference the .kde tree. Migrate by copying the old files to the new spots on first run of a current build.
Notice an outdated path? Let us know.