Private and not private button in pidgin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pidgin
I have enclosed the conversation that I tried to have with a friend:
started.
(21:38:40) Chuck Hubele: hi
(21:38:44) Unable to send message: The message is too large.
(21:39:03) Private conversation with chazzie1900 lost.
(21:39:08) markinmadison: how is that?
(21:41:30) markinmadison: can you see this message?
(21:41:48) Chuck Hubele: yes and now im talking with tym and its not doing that
(21:41:50) Private conversation with chazzie1900 started.
---
21:40
(21:42:38) markinmadison: ok, I just quit and now restarted
(21:42:57) markinmadison: how is it now?
(21:44:08) markinmadison: Hello?
(21:44:30) markinmadison: you there?
(21:44:48) Chuck Hubele: im here
(21:44:48) Unable to send message: The message is too large.
[Image] (21:44:51) Private conversation with chazzie1900 started.
(21:44:55) Chuck Hubele: but it keeps going back to the other
21:45
(21:45:06) Unable to send message: The message is too large.
I tried to talk to a friend of mine that is also using Pidgin and it asks to authenticate and go to a private conversation. When we try to do this, it doesn't authenticate. When I try to turn off the private option, it gives me an error of "Unable to send message: The message is too large." I believe that this is a security problem because it won't go into a private conversation. What can I do about this? I would like to talk to my friend.....
ProblemType: Bug
Architecture: i386
Date: Sat Oct 31 21:45:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: pidgin 1:2.6.2-1ubuntu7
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: pidgin
Uname: Linux 2.6.31-14-generic i686
security vulnerability: | yes → no |
tags: | added: karmic |
Thanks for reporting this issue.
I'm not sure what you mean by "private conversation".
Could you please give steps on how to reproduce this issue?
Also, what protocol were you communicating with?