fractal issueshttps://gitlab.gnome.org/World/fractal/-/issues2024-03-27T15:46:09Zhttps://gitlab.gnome.org/World/fractal/-/issues/1415Emote replies turn into regular emotes2024-03-27T15:46:09ZAlexandre FrankeEmote replies turn into regular emotes## Steps to reproduce
1. Open Fractal
2. Enter a room
3. Right click on any message and select the Reply menu item
4. Send an emote reply (message starting with `/me`)
A regular, non-reply, message is sent.
## Information
* [x] This ...## Steps to reproduce
1. Open Fractal
2. Enter a room
3. Right click on any message and select the Reply menu item
4. Send an emote reply (message starting with `/me`)
A regular, non-reply, message is sent.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-69d0a2a<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39<!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly<!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->
* **Homeserver**: matrix.org<!-- The homeserver for your matrix account, e.g. matrix.org, gnome.org, … You can mention several of them if this is reproducible on multiple ones. -->https://gitlab.gnome.org/World/fractal/-/issues/1409Composer not disabled in historic room2024-03-06T20:29:41ZAlexandre FrankeComposer not disabled in historic roomIn *one* (out of nine) of my historic rooms.
* the composer is not disabled, as it should be
![Capture_d_écran_du_2024-03-06_21-11-25](/uploads/9379f7646b82f41d35f18f9edc97224e/Capture_d_écran_du_2024-03-06_21-11-25.png)
* I appear in...In *one* (out of nine) of my historic rooms.
* the composer is not disabled, as it should be
![Capture_d_écran_du_2024-03-06_21-11-25](/uploads/9379f7646b82f41d35f18f9edc97224e/Capture_d_écran_du_2024-03-06_21-11-25.png)
* I appear in the room members list, but we checked with another account who’s in the room and I’m not there anymore
![Capture_d_écran_du_2024-03-06_21-12-10](/uploads/ef2c56b1d8b1c7ca143708e26b982241/Capture_d_écran_du_2024-03-06_21-12-10.png)
That could be because on sync, the HS does not send the state event for leaving the room, and we rely on that.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-05302e4<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39<!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly<!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->
* **Homeserver**: matrix.org<!-- The homeserver for your matrix account, e.g. matrix.org, gnome.org, … You can mention several of them if this is reproducible on multiple ones. -->https://gitlab.gnome.org/World/fractal/-/issues/1408Close room when filter opened via shortcut in narrow mode2024-03-06T17:39:54ZAlexandre FrankeClose room when filter opened via shortcut in narrow modeIn narrow mode, hitting <kbd>Ctrl</kbd><kbd>K</kbd> will pop out the room filter (good!) in the room list (sidebar). The room list remains hidden though. The filter also steals focus, so hitting <kbd>Esc</kbd> won’t close the current roo...In narrow mode, hitting <kbd>Ctrl</kbd><kbd>K</kbd> will pop out the room filter (good!) in the room list (sidebar). The room list remains hidden though. The filter also steals focus, so hitting <kbd>Esc</kbd> won’t close the current room to reveal the list.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-05302e4<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->https://gitlab.gnome.org/World/fractal/-/issues/1405Widgets that are disabled are not focusable2024-03-28T13:06:59ZKévin CommailleWidgets that are disabled are not focusableWhen we want to prevent a widget from being interacted with, we usually disable it with `.set_sensitive(false)`. That means that the widget is not focusable anymore.
This is problematic if the widget still provides some information, but...When we want to prevent a widget from being interacted with, we usually disable it with `.set_sensitive(false)`. That means that the widget is not focusable anymore.
This is problematic if the widget still provides some information, but the value is just not editable, as that prevents users depending on keyboard focus to discover the information.
This is an issue we might have in several places, but that I mainly noticed in the room details.
I am also wondering if we have the same issue with `SpinnerButton`: when it is activated, it shows the spinner and is disabled, which means that the focus has no choice but to move to the next widget (if possible), which can be confusing because the main information here is that there is something happening.Fractal 7https://gitlab.gnome.org/World/fractal/-/issues/1402Infinite spinner in new direct chat dialog2024-03-28T10:51:11ZAlexandre FrankeInfinite spinner in new direct chat dialog## Steps to reproduce
1. Open Fractal
2. Go to the primary menu (above sidebar) and select the new direct chat entry
3. Type in a mxid
There will be a spinner that never stops. It is thus impossible to start a new direct chat from here...## Steps to reproduce
1. Open Fractal
2. Go to the primary menu (above sidebar) and select the new direct chat entry
3. Type in a mxid
There will be a spinner that never stops. It is thus impossible to start a new direct chat from here.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-a84a603<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39<!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly<!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->
* **Homeserver**: matrix.org <!-- The homeserver for your matrix account, e.g. matrix.org, gnome.org, … You can mention several of them if this is reproducible on multiple ones. -->Fractal 7https://gitlab.gnome.org/World/fractal/-/issues/1401"Cancel" button has focus2024-03-28T09:46:44ZAlexandre Franke"Cancel" button has focusSince the paste-image dialog was ported to `AdwDialog`, the "Cancel" button has focus and so if you paste then hit enter, nothing gets sent.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this bo...Since the paste-image dialog was ported to `AdwDialog`, the "Cancel" button has focus and so if you paste then hit enter, nothing gets sent.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-fb3306a<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39 <!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly <!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->Fractal 7https://gitlab.gnome.org/World/fractal/-/issues/1397Changing room avatar to SVG succesfully fails2024-02-12T19:49:32ZAlexandre FrankeChanging room avatar to SVG succesfully fails## Steps to reproduce
1. Open Fractal
2. Enter a room
3. Open room details and try to set room avatar to an SVG file loaded from disk. A toast tells you that avatar was succesfully changed, but the room avatar is a letter avatar that ca...## Steps to reproduce
1. Open Fractal
2. Enter a room
3. Open room details and try to set room avatar to an SVG file loaded from disk. A toast tells you that avatar was succesfully changed, but the room avatar is a letter avatar that can’t be removed
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-81e1af2<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39<!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly<!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->https://gitlab.gnome.org/World/fractal/-/issues/1395No error when media fails to open from history2024-02-12T19:41:58ZAlexandre FrankeNo error when media fails to open from history## Steps to reproduce
1. Open Fractal
2. Enter a room where an SVG file has been posted, thumbnail is displayed
3. Click on the thumbnail, get a black media viewer, with no error.
## Information
* [x] This bug is reproducible from the...## Steps to reproduce
1. Open Fractal
2. Enter a room where an SVG file has been posted, thumbnail is displayed
3. Click on the thumbnail, get a black media viewer, with no error.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-81e1af2<!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39<!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly<!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->https://gitlab.gnome.org/World/fractal/-/issues/1394Swiping back from media viewer in media history closes the gallery2024-02-13T09:56:40ZKévin CommailleSwiping back from media viewer in media history closes the galleryIt should only close the media viewer, and show the media history gallery. A second swipe back would close the gallery.It should only close the media viewer, and show the media history gallery. A second swipe back would close the gallery.https://gitlab.gnome.org/World/fractal/-/issues/1390Black avatar images2024-02-21T18:52:08ZFabioBlack avatar imagesFractal shows black avatars for some rooms
## Steps to reproduce
1. Open Fractal
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
...Fractal shows black avatars for some rooms
## Steps to reproduce
1. Open Fractal
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* Fractal 6: <!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* Arch Linux: <!-- Operating system version, e.g. Fedora 36 -->
* Arch 'extra' repo and compiled from sourc: <!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->
In console it prints
```
(fractal:113714): Gdk-CRITICAL **: 15:55:25.776: gdk_memory_texture_new: assertion 'stride >= width * gdk_memory_format_bytes_per_pixel (format)' failed
```
which come from building `gdk::MemoryTexture` in function `texture_from_data()` in `src/components/image_printable.rs`.
Looks like it happens when image is not 3 bytes per pixel (eg `gdk::MemoryFormat::R16g16b16`).
For a 480x480px `R16g16b16` image , `layout` param is
```
SampleLayout { channels: 3, channel_stride: 1, width: 480, width_stride: 3, height: 480, height_stride: 1440 }
```
`height_stride` is passed as `stride` param.
`R16g16b16` is 6 bytes per pixes, times 480px, stride should be 2880, but `height_stride` here is 1440, so assert triggers.
layout comes from [image crate](https://github.com/image-rs/image/blob/master/src/flat.rs#L144) where height_stride is calculated as `n_of_channels * width`
but `gdk::MemoryTexture` expects `bytes_per_pixes * width`
I was thinking it was a bug in image crate, but [docs for SampleLayout](https://docs.rs/image/0.24.8/image/flat/struct.SampleLayout.html) talks about 'index to get next sample', so it works when every channel is one bytehttps://gitlab.gnome.org/World/fractal/-/issues/1385Join Room dialog doesn’t close with escape key2024-02-05T16:07:15ZAlexandre FrankeJoin Room dialog doesn’t close with escape key<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
All our dialogs except this one close on hitting <kbd>escape</kbd>.
## Steps to reproduce
1. Open Fractal
2. In the primary menu (...<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
All our dialogs except this one close on hitting <kbd>escape</kbd>.
## Steps to reproduce
1. Open Fractal
2. In the primary menu (above room list), select the Join room item
3. A dialog opens. Hit <kbd>escape</kbd> and notice how it doesn’t close.
4. Close it with the icon in the top right corner. Optionnaly, select any other menu item that opens a dialog, such as the top two in the primary menu, or the account settings, or the room details. Notice how they close on hitting <kbd>escape</kbd>.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6-7a35b0a <!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: Fedora 39 <!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: GNOME Apps Nightly<!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->https://gitlab.gnome.org/World/fractal/-/issues/1381Scroll to the bottom button does not update the keyboard focus properly2024-03-21T14:37:34ZPeter VágnerScroll to the bottom button does not update the keyboard focus properly<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so...<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so issues with the stable release are unlikely to be fixed. -->
When the scroll to the bottom button in the room history is pressed it scrolls the room history and focus moves to the Send a file button. When navigating with tab or shift+tab back to the room history navigation continues from the initial position where the selection started before pressing the scroll to the bottom button instead of from the very last item in the list.
## Steps to reproduce
1. Open Fractal
2. Enter a room
3. Use tab or shift+tab to navigate to the room history.
4. Use up arrow key to navigate until the scroll to the bottom button becomes available and remember what event is selected in the room history
5. Now use the tab key to navigate until the focus lands on the scroll to the bottom button and activate the button by pressing the enter key
6. Now use shift+tab to navigate back to the room history.
7. Once in the room history use up or down arrow to navigate and notice the navigation continues from the initial position that you have remembered in step 4 rather from the last item in the list in the bottom.
## Information
* [ ] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: Fractal 6 git commit 6968115e>
* **OS Version**: Arch linux with GNOME 45
* **Installation Source**: AUR
* **Homeserver**: pvagner.tkhttps://gitlab.gnome.org/World/fractal/-/issues/1380Unable to expand read receipts with the keyboard2024-01-27T19:07:52ZPeter VágnerUnable to expand read receipts with the keyboard<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so...<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so issues with the stable release are unlikely to be fixed. -->
In the room history each item displays read receipts for the displayed event. When using this part of the UI with orca screen reader I can use tab key to navigate and reach a button labelled like "2 members read" or similar. When pressing the enter key to expand it nothing happens. I'd expect some kind of a list with display names and times being able to find out who and when has read the original event.
## Steps to reproduce
1. Open Fractal with orca running
2. Enter a room
3. Use tab or shift+tab to navigate into the room history.
4. Use up or down arrow to navigate to find out an event in the history with read receipts showing.
5. Use tab key to navigate to the read receipts and notice orca presenting the collapsed button.
6. Try to activate the button by pressing the enter key or the space bar key.
Is this part generally not implemented yet or is it not accessible with keyboard only?
## Information
* [ ] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: Fractal 6 git commit 6968115e>
* **OS Version**: Arch linux with GNOME 45
* **Installation Source**: AUR
* **Homeserver**: pvagner.tkFractal 7https://gitlab.gnome.org/World/fractal/-/issues/1379Touchscreen long-press on the message input box does not bring up a context menu2024-02-03T15:01:32Zclayton craftTouchscreen long-press on the message input box does not bring up a context menuWhen using Fractal with a touchscreen, long-pressing on the text input box does not bring up the context menu as one might expect. An example of why you'd want to do this is for copy/pasting text into this box.
## Steps to reproduce
1....When using Fractal with a touchscreen, long-pressing on the text input box does not bring up the context menu as one might expect. An example of why you'd want to do this is for copy/pasting text into this box.
## Steps to reproduce
1. Open Fractal
2. Enter a room
3. long-press on the text input box... nothing happens
## Information
* [ ] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6
* **OS Version**: postmarketOS
* **Installation Source**: flathub
* **Homeserver**: postmarketos.org (shouldn't matter though?)https://gitlab.gnome.org/World/fractal/-/issues/1377Logging in on a server which supports both local password and SSO without `id...2024-01-25T16:25:21ZQuentin GliechLogging in on a server which supports both local password and SSO without `identity_providers` only prompts for local passwordWhen Fractal discovers a server which has both the `m.login.password` and `m.login.sso` , it only shows the username/password login method.
The `m.login.sso` method must also have `identity_providers` set (this field is optional).
## St...When Fractal discovers a server which has both the `m.login.password` and `m.login.sso` , it only shows the username/password login method.
The `m.login.sso` method must also have `identity_providers` set (this field is optional).
## Steps to reproduce
1. Open Fractal
2. Use `synapse-oidc.lab.element.dev` as homeserver
3. Only the username/password prompt should be shown, even though this server supports `m.login.sso`
## Information
* [x] This bug is reproducible from the latest nightly build
* **Fractal Version**: 6-047f7c4
* **OS Version**: Fedora 39
* **Installation Source**: GNOME Apps Nightly
* **Homeserver**: synapse-oidc.lab.element.dev
---
The logic to display those buttons is here: https://gitlab.gnome.org/World/fractal/-/blob/047f7c41a53654b1ea8af77dac841e81249a0373/src/login/method_page.rs#L162-171
It doesn't add the "other SSO" button if the `identity_providers` is empty.Fractal 7https://gitlab.gnome.org/World/fractal/-/issues/1376"Failed to logout the session" for unreachable homeserver2024-01-26T09:44:31Zboogie woogie"Failed to logout the session" for unreachable homeserverhttps://gitlab.gnome.org/World/fractal/-/issues/1230 is not fatal anymore with the new version thanks to multiple sessions, as one can now add a new account that works. Great news, I can now use fractal again!
However, the old defunct s...https://gitlab.gnome.org/World/fractal/-/issues/1230 is not fatal anymore with the new version thanks to multiple sessions, as one can now add a new account that works. Great news, I can now use fractal again!
However, the old defunct session, where the homeserver does not exist anymore, still cannot be removed. When attempting to remove it via the `Log Out` button (both under "General" and "Sessions"), then `Continue`, Fractal returns `Failed to logout the session.` and nothing happens. The defunct session keeps cluttering the session list with no option to clear it.
Client output indicates it's failing to clear the session locally due to no server response:
```
2024-01-25T10:44:54.544152Z ERROR fractal::session::model::session: Failed to perform sync: error sending request for url (https://nonexistent.homeserver.com/_matrix/client/versions): error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889: (hostname mismatch)
2024-01-25T10:44:54.677104Z ERROR matrix_sdk::sync: Received an invalid response: error sending request for url (https://nonexistent.homeserver.com/_matrix/client/versions): error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889: (hostname mismatch)
```
Again, a pointer to relevant files to remove or dconf settings to clear so fractal state is **completely** reset would already be very helpful as a workaround.https://gitlab.gnome.org/World/fractal/-/issues/1374Content overflowing when there are mentions to members with long display names2024-02-19T11:01:28ZGuanran WangContent overflowing when there are mentions to members with long display names<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so...<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so issues with the stable release are unlikely to be fixed. -->
Window content is overflowing when there are messages from members with long names.
Excuse me for my poor English. I don't know how to describe this exactly...
See images below:
![image](/uploads/7f733edf9f20dee873e3833921cd1efb/image.png)
![image](/uploads/e9d6a1d64758168abc8213508b8b5e8b/image.png)
## Steps to reproduce
1. Open Fractal
2. Enter a room with messages sent that mention a member with extra-long names
3. Chat timeline is not fully visible within the current window and is capped by their name's length
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6 <!-- The version of Fractal you were using when the bug occurred. Check the "About Fractal" dialog for this information -->
* **OS Version**: NixOS Unstable 24.05.20240121.612f972 (Uakari) <!-- Operating system version, e.g. Fedora 36 -->
* **Installation Source**: nixpkgs (nixos-unstable) <!-- Where you installed Fractal from, e.g. Flathub, GNOME Apps Nightly, AUR, or distro repositories -->
* **Homeserver**: mozilla.org <!-- The homeserver for your matrix account, e.g. matrix.org, gnome.org, … You can mention several of them if this is reproducible on multiple ones. -->
<!-- If you have a crash report, use the "Attach A File" button in the issue editor to attach it, or paste it in a code block below. -->
<!-- To create a code block, you surround the code with two lines with three "`" characters like so:
```
code goes here
```
-->Fractal 7https://gitlab.gnome.org/World/fractal/-/issues/1373Problems navigating context menus with keyboard2024-01-29T13:08:16ZPeter VágnerProblems navigating context menus with keyboard<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so...<!-- This is a template to report bugs, select the corresponding template to request a new feature. -->
<!-- Please note that Fractal was rewritten from scratch and our current focus is on the main branch
or the latest nightly build, so issues with the stable release are unlikely to be fixed. -->
Detailed description of the issue. Provide as much information as you can, potentially with images
or videos showing the issue.
When pressing shift+F10 to display a context menu in the sidebar room list or in the item of a message history it is not possible to navigate in the menu.
## Steps to reproduce
1. Open Fractal
2. Use tab or shift+tab to navigate and stop when the room list receives the focus
2. Use up or down arrow key to navigate, choose a direct chat or a room (not the room category) and press shift+F10 to open the context menu.
3. Now try to use up or down arrow keys to navigate in the menu. Either nothing is reported orscreen reader is reporting the room list as if I were not navigating the context menu but the room list.
4. The context menu in the room history is behaving in the same way for me.
## Information
* [ ] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: fractal built from git gdf92df5a
* **OS Version**: arch linux with gnome 45
* **Installation Source**: AUR
* **Homeserver**: Only tested with my own homeserver pvagner.tk running synapse but I don think this is applicable
<!-- If you have a crash report, use the "Attach A File" button in the issue editor to attach it, or paste it in a code block below. -->
<!-- To create a code block, you surround the code with two lines with three "`" characters like so:
```
code goes here
```
-->https://gitlab.gnome.org/World/fractal/-/issues/1371Images orientation metadata ignored when opened (incorrect rotation)2024-01-28T15:00:41ZGNImages orientation metadata ignored when opened (incorrect rotation)## Steps to reproduce
1. Send/receive image with orientation (rotation) metadata.
2. Click/tap image to view large version.
## Expected result
Image shown with correct orientation.
## Actual result
Image shown with incorrect "as enc...## Steps to reproduce
1. Send/receive image with orientation (rotation) metadata.
2. Click/tap image to view large version.
## Expected result
Image shown with correct orientation.
## Actual result
Image shown with incorrect "as encoded" orientation, with orientation metadata ignored.
## Additional information
Preview orientation is correct.
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6
* **OS Version**: -
* **Installation Source**: Flathub.
* **Homeserver**: -https://gitlab.gnome.org/World/fractal/-/issues/1370notification settings don't work2024-01-22T15:57:42Zprimalmotionnotification settings don't work
I can't get notificatios settings to work. Right now Fractal just spams every message in every rooms. when I go to the account settings then notifications, then try to select "all messages in direct chats, and mentions and keywords in ...
I can't get notificatios settings to work. Right now Fractal just spams every message in every rooms. when I go to the account settings then notifications, then try to select "all messages in direct chats, and mentions and keywords in all rooms" or "Only mentions and keywords in all rooms" I get an error "Could not change global notifications" and the radio button returns to "All messagesin all rooms"
The log says
```
024-01-19T22:56:52.564202Z ERROR matrix_sdk::notification_settings: Unable to set underride push rule `.org.matrix.msc3930.rule.poll_start` actions: the server returned an error: [404 / M_NOT_FOUND] push rule ID not found
2024-01-19T22:56:52.568525Z ERROR fractal::session::model::notifications::notifications_settings: Failed to change global group chats notifications setting: Unable to update push rule
```
When I try the same in a room setting (room details), it seems to work (the radio button stays on whatever I select) but will be reset to "All Messages" after I close and reopen the room details dialog. In that case, the log says
```
024-01-19T23:12:26.019773Z WARN matrix_sdk_base::client: Failed to deserialize a global account data event: missing field `sender` at line 1 column 5477 event_type="m.push_rules"
2024-01-19T23:12:26.021344Z WARN matrix_sdk_base::client: Failed to deserialize a global account data event: missing field `sender` at line 1 column 5477 event_type="m.push_rules"
2024-01-19T23:12:26.031433Z WARN matrix_sdk::event_handler: Failed to deserialize event, skipping event handler.
Deserialization error: missing field `sender` at line 1 column 5477 event_type="m.push_rules" event_kind=GlobalAccountData
```
## Information
* [x] This bug is reproducible from the latest nightly build <!-- Check this box if the bug happens on Fractal's development version -->
* **Fractal Version**: 6
* **OS Version**: PureOS
* **Installation Source**: Flathub
* **Homeserver**: antisocial.ly. personal server, running latest dendriteFractal 7