Some IRC rooms empty since 71.0b1 update
Categories
(Chat Core :: IRC, defect)
Tracking
(Not tracked)
People
(Reporter: RyanVM, Unassigned)
Details
(Keywords: regression)
Since getting the 71.0b1 update, I've noticed that a couple of the IRC rooms I auto-join seem unable to display any content even when there's activity in the channel. On the left-hand panel, I still see the channel's new message notification when someone comments in the channel, but the actual channel pane is completely empty. I've seen it in #fx-team and #mobile, but other channels appear to be working fine. I'm also unable to view logs from the channel.
I checked the browser console but nothing is appearing there.
Comment 1•6 years ago
|
||
Hey Ryan, can you check the account logs (click Show Accounts, right click on the account and choose "Copy Debug Log"). Not sure if that will show anything different, but worth checking out.
This log shouldn't have passwords, etc. in it, but it will have personal information (what channels you join, who you talk to, messages, etc.)
I've been using IRC fine on TB 71b1 on moznet, so must be something different going on...
Reporter | ||
Comment 2•6 years ago
|
||
Not seeing anything obvious in those logs. Just regular channel activity.
Comment 3•6 years ago
|
||
Huh, that's a bit confusing. I wonder if this is a graphical issue of some sort and not a backend issue then...
I'm seeing the following when joining #mobile:
TypeError: Argument 1 of Node.insertBefore is not an object.imContentSink.jsm:258:19
cleanupNode resource:///modules/imContentSink.jsm:258
cleanupImMarkup resource:///modules/imContentSink.jsm:381
displayMessage chrome://chat/content/conversation-browser.js:598
displayPendingMessages chrome://chat/content/conversation-browser.js:503
displayPendingMessages self-hosted:869
This smells like bug 1591399. The fix for that will be in the next Thunderbird beta (which will hopefully come out in the next few days).
Comment 4•6 years ago
|
||
Ryan, we're shipping TB 71 beta 2 today with bug 1591399 fixed. The error location is exactly what we fixed in that bug:
https://hg.mozilla.org/releases/comm-beta/rev/5a596857b17a50819c55844b2e62967998d9b446#l1.11
Please let us know how you fare.
Reporter | ||
Comment 5•6 years ago
|
||
Yep, b2 is working fine.
Description
•