maemo.org Bugzilla – Bug 4900
IRC Plugin Doesn't Always Show User Nicks When People Speak
Last modified: 2010-03-11 16:01:04 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: See Version selected above. (Control Panel > General > About product) STEPS TO REPRODUCE THE PROBLEM: 1) Add IRC account. 2) Enter a chatroom (I've been in the official #maemo IRC room on freenode.net) 3) Wait for people to speak. EXPECTED OUTCOME: IRC plugin should always prefix all channel messages with the name of the person speaking. ACTUAL OUTCOME: It seems one particular person just does not have their name prefixed to their channel messages... in my case, stskeeps. His messages appear in green just like action messages (/me messages) and without his name. REPRODUCIBILITY: Sometimes, depending on who speaks, it seems. (always/sometimes/once) EXTRA SOFTWARE INSTALLED: RTCOMM OTHER COMMENTS: It is impossible to tell who is speaking when this bug happens. It's only by comparing what I see on my screen with the #maemo IRC log that I can see who it was that was speaking. It seems to only affect ONE person at a time. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.2; .NET CLR 3.5; ffco7) Gecko/2008090514 Firefox/3.0.2
I fully realize that this bug won't be fixed in Diablo and that the plugin is (sadly) not included in Fremantle so this bug won't be fixed, but I wanted to make sure this was documented. Screenshot from tablet coming soon.
There's a very good chance that the people that are not having their names shown in the chat are all ops/moderators.
Yepp, screenshot welcome. :)
Created an attachment (id=1306) [details] screenshot user Razumihn speaking in the channel. All instances of this happening appear to be from users whose names start with a capital letter, like bug #4905.
The user also is not an op or voiced. Some people that originally were affected yesterday, such as Stskeeps, were not affected today for some reason. I'll be properly testing this in a controlled environment tonight to narrow down the cause.
This is a WONTFIX for Maemo4. If bug 5139 for Maemo5 gets solved in the future and if the problem reporterd here will be still an issue in Maemo5 after fixing bug 5139, please update this report (steps, Version field) and reopen it. Thanks.