Version: 0.12.4 (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux Whenever I get a broadcast message it pops up in a separate window despite the fact that I have specifically chosen "Group All Messages in Same Chat Window" in Settings -> Configure -> Behavior -> Chat. The broadcasts will even open separate windows when the broadcast is from the same contact.
What do you mean by broadcast message?
I've done more investigation on our side. We're using a Openfire Jabber server (http://www.igniterealtime.org/projects/openfire/index.jsp) with a Broadcast Plugin (http://www.igniterealtime.org/projects/openfire/plugins.jsp) The "broadcast" appears to be just a regular message which gets automatically re-sent to all persons within a group. In this particular case, messages are sent to groupa@broadcast.example.com and is delivered to everyone within the group "groupa". I garnered these XML transcripts from Pidgin's XMPP Console. I don't see anything in particular which identifies the message as a broadcast. The main thing I see missing here is a type='chat' attribute. I'm guessing this is not standard. Perhaps this bug needs to be changed to 'group all messages in same chat window" does not group Jabber messages without a "type" attribute'. This is a broadcast message sent to a list of persons by our monitoring server as it was received within Pidgin: <message to='brendan@chat.example.com' id='3' from='monitor@chat.example.com/331f746b'> <body>[Admin]%server %name %status %down (%msg)</body> </message> This is a regular message: <message type='chat' id='aacba' to='brendan@chat.example.com/Pidgin' from='kevinf@chat.example.com/Psi'> <body>body removed</body> <x xmlns='jabber:x:event'> <composing/> </x>
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!