[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 290309] New: Starting kwalletmanager for a new user does not
From:       Christoph Bartoschek <bartoschek () gmx ! de>
Date:       2012-01-01 11:46:33
Message-ID: bug-290309-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=290309

           Summary: Starting kwalletmanager for a new user does not
                    trigger setup of kwallet
           Product: kwalletmanager
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: lemma@confuego.org
        ReportedBy: bartoschek@gmx.de


Version:           unspecified (using Devel) 
OS:                Linux

I create a new user. Now I want to setup kwallet. Normally this is done when a
client application first tries to access the wallet. But I want to do it before
I start kmail which is currently broken.

I expect that the first start of kwalletmanager startes the setup. But nothing
happens. Instead if I then choose to create a new wallet, I am first asked for
a name.  Then the basic setup starts and creates a default wallet. Then I can
set the password for the new wallet. This is not user friendly.

In my opinion the first start of kwalletmanager should trigger the basic setup.
If you do not want to have this, then the creation of a wallet should trigger
the basic setup, but it should not create an additional wallet.
If you want to keep it similar to the current behaviour then the basic setup
started after choosing the wallet name should use the given name for the
default wallet and not "kdewallet".

Reproducible: Always

Steps to Reproduce:
See above.

Actual Results:  
See above.

Expected Results:  
See above.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]