Bug 183669 - kpersonalizer should be ported to KDE4
Summary: kpersonalizer should be ported to KDE4
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-08 11:55 UTC by Jan Gerrit Marker
Modified: 2024-09-14 16:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Gerrit Marker 2009-02-08 11:55:39 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

It would be nice to have a wizard in that you could do settings like the EMail settings, the Kopete settings, the look and feel settings, a plasma model and so things. This wizard would be started at the first start of KDE and you could start it easily from systemsettings.
Comment 1 Jonathan Marten 2009-02-08 16:59:08 UTC
This sounds like the old kpersonalizer under KDE3, although that didn't do PIM settings.  kpersonalizer was removed from KDE4 in Sep 2006 (r588649), so presumably needs to be ported.  See the "Desktop configuration" section in http://wiki.kde.org/tiki-index.php?page=KDE+4+Application+Cleanup for more information and rationale.

Changing bug title to better reflect wish.
Comment 2 Aaron J. Seigo 2009-02-08 17:12:23 UTC
this actually sounds nothing like the old kpersonalizer which focused on visual features not useful things like setting up your identity information. there is no intention to resurrect kpersonalizer for kde4, but something that was actually useful like an "OEM post-install wizard" would be nice.
Comment 3 Christoph Cullmann 2024-09-14 16:17:31 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann