Bug 234939 - General KDE apps lockup, then kwallet crash
Summary: General KDE apps lockup, then kwallet crash
Status: RESOLVED DUPLICATE of bug 254198
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: 1.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Leupold
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-21 02:30 UTC by Christopher Heiny
Modified: 2013-09-04 12:46 UTC (History)
1 user (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 Christopher Heiny 2010-04-21 02:30:50 UTC
Application: kwalletmanager (1.5)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.32.11-99.fc12.x86_64 x86_64
Distribution: "Fedora release 12 (Constantine)"

-- Information about the crash:
ssh 'ed from one machine to another, ran kmail, akregator, konqueror, thunderbird, firefox displayed back to first machine.  Eventually all KDE functions locked up, had to be killed from konsole.  Then kwallet crashed.

 -- Backtrace:
Application: KDE Wallet Manager (kwalletmanager), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#5  Private (this=0x7fff95993870, p=...) at kernel/qvariant.h:352
#6  QVariant::QVariant (this=0x7fff95993870, p=...) at kernel/qvariant.cpp:1391
#7  0x00000038a6a56a57 in QDBusPendingReplyData::argumentAt (this=0x7fff959938d0, index=<value optimized out>) at qdbuspendingreply.cpp:268
#8  0x00000038ad488ecd in argumentAt<0> () at /usr/include/QtDBus/qdbuspendingreply.h:174
#9  operator QStringList () at /usr/include/QtDBus/qdbuspendingreply.h:184
#10 KWallet::Wallet::walletList () at /usr/src/debug/kdelibs-4.4.1/kdeui/util/kwallet.cpp:176
#11 0x000000000041b99e in _start ()

Possible duplicates by query: bug 214921.

Reported using DrKonqi
Comment 1 Valentin Rusu 2013-09-04 12:46:03 UTC
I think that the fix for 254198 will also fix this.

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