Bug 346762

Summary: Settings are not migrated from 2.14 to 3.0
Product: [Applications] konsole Reporter: Martin Ueding <mu>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED FIXED    
Severity: normal CC: ben, cpigat242, rdieter
Priority: NOR    
Version: 3.0.1   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Martin Ueding 2015-04-27 07:11:30 UTC
I performed the Ubuntu upgrade to 15.04 on 2015-04-23. The previous version of Ubuntu (14.10) used this version of Konsole:

Qt: 4.8.6
KDE: 4.14.1
Konsole: 2.14.1

The new one uses this version:

Qt: 5.4.1
KDE Frameworks: 5.9.0
Konsole: 3.0.1

When I start Konsole now, it starts with factory settings and not with my profile. I saw that my profiles are sitting in the .kde folder whereas the new profiles are in .local.

I think all those settings should be migrated automatically, especially since I do not really know whether there is more than just the profiles.
Comment 2 Kurt Hindenburg 2015-07-23 00:54:14 UTC
Git commit 5c13d4641ac05704550af9a69d6cdd8f696a6f0d by Kurt Hindenburg.
Committed on 23/07/2015 at 00:51.
Pushed by hindenburg into branch 'Applications/15.08'.

Migrate KDE4 apps files to new KDE5

The rc and ui files were already migrated.  This patch copies the other
files from share/apps/konsole to local/share/konsole.
FIXED-IN: 15.08.0

M  +27   -4    src/main.cpp

http://commits.kde.org/konsole/5c13d4641ac05704550af9a69d6cdd8f696a6f0d
Comment 3 Kurt Hindenburg 2015-07-23 01:31:50 UTC
Git commit 921000d026a728ad55fc8c83524dc13b67aa86c5 by Kurt Hindenburg.
Committed on 23/07/2015 at 01:31.
Pushed by hindenburg into branch 'master'.

Migrate KDE4 apps files to new KDE5

The rc and ui files were already migrated.  This patch copies the other
files from share/apps/konsole to local/share/konsole.
FIXED-IN: 15.08.0
(cherry picked from commit 5c13d4641ac05704550af9a69d6cdd8f696a6f0d)

M  +27   -4    src/main.cpp

http://commits.kde.org/konsole/921000d026a728ad55fc8c83524dc13b67aa86c5
Comment 4 Ben Creasy 2018-08-19 04:28:26 UTC
Kurt, it seems like your commits 3 years ago fixed this? 

Tentatively setting this as Resolved->Fixed - please correct if this is mistaken.