You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Saturday, June 3rd 2006, 9:54pm

[Kopete] Winpopup protocol

I use the winpopup protocol in my network with Linpopup. Since Kopete 0.12 adds support for it I though about removing Linpopup but I have problems making it work, I can send messages but I not receive them.
- Samba is configured correctly since Linpopup worked
- I made the needed changes to work with Kopete. And everything looks correct, winpopup-send.sh makes his work:

Source code

1
2
3
# ls -l
total 4
-rw-rw-rw- 1 nobody nobody 38 2006-06-03 22:14 1149365667_603734000

Source code

1
2
3
4
# cat 1149365667_603734000
primero
2006-06-03T22:14:27+0200
hola

But Kopete doesn't gives signals of working. When messages are received Kopete doesn't shows them.

Since I never before used winpopup with Kopete I 'm not sure if is a bug or my fault, but... any idea? Exactly what search for Kopete to show a message?

This post has been edited 1 times, last edit by "RedDwarf" (Jun 3rd 2006, 10:17pm)


strohel

Beginner

Posts: 1

Location: Prague, Czechia (yup - that's in Europe)

  • Send private message

2

Thursday, August 3rd 2006, 4:08pm

You just need to add winpopup pseudo-account to Kopete. (just Kopete Main window -> Settings -> Configure.. -> Accounts -> New...)

You should version 0.12 or later, but it looks you already have it, since you have a winpopup-send.sh script)

Tell me it it worked.

3

Thursday, August 3rd 2006, 10:45pm

Well I just tried again and now works. I'm not sure about what was the problem, now I have an updated Kopete 0.12.1 package.
But perhaps the problem was that I used the config from the wiki that says to use the "%m" parameter, but samba man says:

Quoted

This parameter is not available when Samba listens on port 445, as clients no longer send this information

And well, I'm listening on port 445 ;)

Sorry, it's late and I haven't time to test.