Bug 122431

Summary:	kopete does not attempt to sign in
Product:	[Unmaintained] kopete	Reporter:	Michael Yates <republicson>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	tayirvadai.vikram
Priority:	NOR
Version First Reported In:	0.10.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Michael Yates 2006-02-21 18:21:08 UTC

Version:           0.10.3 (using KDE 3.4.2, Mandrake Linux Cooker i586 - Cooker)
Compiler:          Target: i586-mandriva-linux-gnu
OS:                Linux (i686) release 2.6.12-12mdksmp

I have three accounts set up in Kopete: MSN, Yahoo, and Google Talk (through Jabber). When I initially set it up, i configured it to remember by passwords for this account. I told it to secure the passwords using Kwallet (I think), but it no longer even prompts me for the Kwallet password. When I start Kopete it does nothing. When I try to change my status to "online" it still does nothing. No friends appear in the list.

I have successfully used Kopete in the past, but have since tried to upgrade my version of KDE (which I am also having problems with). Not sure how the two are related, but I did have to re-setup Kopete after the attempted reinstall of KDE.

Comment 1 Will Stephenson 2006-02-21 21:58:52 UTC

2 possibilities:

1) The configs are messed up.  
We don't support downgrading KDE versions - so if you partially upgraded KDE, then backed out and downgraded again, it's likely that your configs (kopete, kwallet) have been modified to suit the new KDE version, and now don't work with the old one.  

Solution: set up a new user, and reconfigure Kopete with the account details.  If that works, then move aside or delete at least $HOME/.kde/share/config/kopeterc and $HOME/.kde/share/apps/kopete, possibly all of $HOME/.kde and reconfigure.

2) Your KDE installation is all messed up.  
Your system may now consist of a mishmash of different versions of KDE programs and libraries, resulting from desperate attempts to rpm -e things, rpm -I --force, and or hand installation with make install.  This cannot work.  If you've done this then turn to your distro's support channels to get help cleaning things up.  It can be done without a full reinstall but it may require  patience.

Comment 2 Thiago Macieira 2006-02-25 19:14:01 UTC

Both possibilities are non-bugs.

Comment 3 Olivier Goffart 2006-03-05 14:55:35 UTC

it's not the first time i heard about this problem related to kwallet that can't get opened.
(kopete is waiting indefinitively for kwallet to be open, and so, nothing seems to happen)

Comment 4 Olivier Goffart 2006-05-13 11:46:38 UTC

Can you paste the debug output of kopete that appears when you run in in a terminal

Comment 5 Olivier Goffart 2006-06-13 11:45:15 UTC

I cannot reproduce

Comment 6 Vikram Sai Balaji 2007-07-22 15:43:28 UTC

i faced a similar problem
here is the console output
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
Error: "/var/tmp/kdecache-vikram" is owned by uid 1000 instead of uid 0.
kopete: ERROR: Communication problem with kopete, it probably crashed.
vikram@vikram-laptop:~$ Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
Very strange! got a DCOPReply opcode, but we were not waiting for a reply!

kwalletmanager works. it opened properly when i ran the command "kwalletmanager" 

i tried for yahoo and gmail accounts. is there a bug which has the uid 1000 instead of uid 0 problem?

Also it did not try to open wallet manager when we configure the password,which is strange.