Project

General

Profile

tickets #93859

openSUSE Meet (Jitsi) is borked after upgrade

Added by Pharaoh_Atem 8 months ago. Updated 21 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Jitsi/ Meet
Target version:
-
Start date:
2021-06-10
Due date:
% Done:

100%

Estimated time:

Description

Hey all,

The openSUSE Meet system was upgraded today, but after the upgrade,
the site theme is broken. The UI widgets are not rendering properly
and the chat is broken.

Can someone take a look and see if the custom theme can be fixed?

--
真実はいつも一つ!/ Always, there's only one truth!


Related issues

Related to openSUSE admin - communication #99711: Server maintenance workflow for openSUSE MeetClosed2021-10-04

History

#1 Updated by Pharaoh_Atem 8 months ago

  • Private changed from Yes to No

#2 Updated by Pharaoh_Atem 8 months ago

Gertjan and I noticed it was fixed yesterday but it is now broken again today.

#3 Updated by lrupp 8 months ago

  • Category set to Jitsi/ Meet

#4 Updated by cdywan 7 months ago

It seems to work properly ~ same as meet.jitsi.org after force-refreshing this morning.

#5 Updated by okurz 4 months ago

Again there were bigger problems last week. Since the last upgrade people seemingly randomly fail to connect to sessions the first time or drop from calls.

#6 Updated by SchoolGuy 4 months ago

okurz wrote:

Again there were bigger problems last week. Since the last upgrade people seemingly randomly fail to connect to sessions the first time or drop from calls.

This can happen when users don't force refresh the browser with "Ctrl + F5" for every session they joined. But we will investigate deeper later this week.

#7 Updated by rsimai 4 months ago

I can't confirm drop from calls but we've just had a situation where (some of) 6 people couldn't randomly join a meeting, CTRL+F5 didn't help so we finally had to give up. Funny enough they were able to talk while they see the error page, until kicked out after 25 seconds with the automatic retry.

Is there anything how users could help resolve this? Anything special to try, besides CTRL+F5?

#8 Updated by cdywan 4 months ago

#9 Updated by lrupp 21 days ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Hi there - and a Happy and Healthy 2022!

I'm currently closing old tickets which did not see much change.
If the main concern still exists and should be handled, please re-open by just replying to this Email.

Thanks in advance,
Lars

Also available in: Atom PDF