Bug 258788 - kwalletmanager crashes every time maybe qt4.7 problem
Summary: kwalletmanager crashes every time maybe qt4.7 problem
Status: RESOLVED DUPLICATE of bug 244301
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Leupold
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-04 12:38 UTC by Caleb Cushing
Modified: 2010-12-06 02:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Caleb Cushing 2010-12-04 12:38:50 UTC 
Version:           unspecified
OS:                Linux

when run from cli I get this output and it never opens. using qt-4.7.1

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()



Reproducible: Always




doesn't seem to affect storage and retrieval of password, just the manager
Comment 1 Caleb Cushing 2010-12-04 12:40:27 UTC 
oops forgot parts of the form... arch linux packages kde 4.5.4 right now though this has been present since at least 4.5.3... maybe since we moved to qt 4.7.1 or before...
Comment 2 Christoph Feck 2010-12-04 13:14:00 UTC 
Check the system tray, there should be an icon for the Wallet Manager (you might need to click on the system tray arrow to show hidden icons).
Comment 3 Caleb Cushing 2010-12-04 15:28:44 UTC 
no it never opens... it crashes or never fully spawns or something at that point. the ui never becomes available. (this is not the first time I've used the manager)
Comment 4 Caleb Cushing 2010-12-04 16:06:14 UTC 
... you know what... I'm a liar... it's been opening directly into the hidden icons section of systray... sorry for the trouble
Comment 5 Christoph Feck 2010-12-06 02:00:17 UTC 
Thanks for the update.

*** This bug has been marked as a duplicate of bug 244301 ***