Bug 4258 - mageia2a3, kwalletmanager launch fails
Summary: mageia2a3, kwalletmanager launch fails
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-01-24 10:58 CET by episteme promeneur
Modified: 2012-01-24 18:22 CET (History)
1 user (show)

See Also:
Source RPM: kwallet
CVE:
Status comment:


Attachments

Description episteme promeneur 2012-01-24 10:58:02 CET
Description of problem:


install kwallet
then
launch kwallet
thne
notihing happens

in konsole we have this :

[x@localhost ~]$ kwalletmanager 
[x@localhost ~]$ 

as root we have this :

[root@localhost ~]# kwalletmanager 
QSystemTrayIcon::setVisible: No Icon set
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: name 'org.kde.kwalletd' had owner '' but we thought it was ':1.7'
[root@localhost ~]#
Comment 1 Manuel Hiebel 2012-01-24 16:23:08 CET
please do the following:
1) enable the "core release debug"
2) install the following packages: gdb glibc-debug kwalletdebug
3) run the following command from a terminal:
   gdb -q kwallet
4) then type "run"
5) when it segfaults, type "bt" and copy back the stack trace in a file you'll
attach (not paste) to this bug report
Thanks

Keywords: (none) => NEEDINFO

Comment 2 episteme promeneur 2012-01-24 16:49:35 CET
in a user konsole

[test@localhost ~]$ gdb -q kwalletmanager
Reading symbols from /usr/bin/kwalletmanager...Reading symbols from /usr/lib/debug/usr/bin/kwalletmanager.debug...done.
done.
(gdb) run
Starting program: /usr/bin/kwalletmanager 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 4153.
[Inferior 1 (process 4148) exited normally]
(gdb) 

and that'all, nothing more happens
Comment 3 Manuel Hiebel 2012-01-24 16:56:09 CET
hum, maybe it use python don't know.

Anyway, john, can you reproduce ?

CC: (none) => balcaen.john

Comment 4 episteme promeneur 2012-01-24 17:18:52 CET
an info :

there is a "kwalletmanager" process in the list of processes

if i right click on kwalletmanager process
then
i select display the app window
then
nothing happens

i killed it with success
Comment 5 John Balcaen 2012-01-24 17:54:30 CET
did you check your systray ?
(Please note that launching kwalletmanager as root won't help for your user)
Comment 6 episteme promeneur 2012-01-24 18:03:55 CET
yes it is in the systray but hidden; you must click the arrow to see it in the list

it's a big trap because for years by default kwallet manager window appears in desktop when launching with "kwalletmanager" even if it is in the systray
Comment 7 John Balcaen 2012-01-24 18:22:23 CET
That's the default upstream configuration here: kwallet is shown only if needed.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.