Avatar for Rooms?

[mr8tom]

The user profiles show the avatars correctly, but they are not being updated on the rooms. The other bridges like tg & wa work like that :)

private_chat_portal_meta: true

Is there anythin (else) I have to change in the config?
Thanks :)

[Medformatik]

I have the same problem. The room name is empty and the avatar of the room is not set.

[beposec]

For me Element-Web shows the picture and name correctly, when I /converttodm.
But this does not fix it in Element X or Fluffychat.

So it seems the bridge is creating a room without dm flag and does not set up name and picture.

[Marco98]

For me Element-Web shows the picture and name correctly, when I /converttodm. But this does not fix it in Element X or Fluffychat.

So it seems the bridge is creating a room without dm flag and does not set up name and picture.

I have the exact same issue. However it looks like a regression to me, because all old portals are fine and newer are not.

My knowledge is not too deep here, but it seems like the only difference i can find is the "creator" of the portals.
All "good" portals are created by the puppet account, but the newer "bad" portals by the bridgebot-account.

When manually setting the room to be a dm-room by using /converttodm or changing m.direct-data everything works as expected in element-web.

Observation:
When using /converttodm in element-web it will flag the room in the account data m.direct (Docs) as a dm-room to the bridgebot-account and not the puppet-account. Maybe the decision is based on who created the room as suspected (?)

But after manually fixing i still have the same issue as @beposec when using element-x-android. It is probably not related to element-hq/element-x-android#3074 as even with a fresh m.direct it will not show correctly in element-x-android.
Maybe the creator can't be a "functional member" of the room which overrides the manual decision via m.direct. It is at least the only theory i can think of.