savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2019-04-16T12:54:08Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1007Line breaks in the middle of words2019-04-16T12:54:08ZFrançois Naggar-TremblayLine breaks in the middle of wordsLines should only break where there are spaces (apart from non-breakable spaces)Lines should only break where there are spaces (apart from non-breakable spaces)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1009[Intercom] Caller “Toggle show chat” takes up the whole screen with only the ...2019-04-21T10:03:10Zovari[Intercom] Caller “Toggle show chat” takes up the whole screen with only the current call/conversationWhen in an intercom audio call, double-click “Toggle show chat”, the:
1. Conversations list disappears
2. Menu, Settings, Account Selector, Minimize, Restore and Maximize disappears
3. Panel in Linux Mint disappears (the operating system...When in an intercom audio call, double-click “Toggle show chat”, the:
1. Conversations list disappears
2. Menu, Settings, Account Selector, Minimize, Restore and Maximize disappears
3. Panel in Linux Mint disappears (the operating system menu, in Windows it is called the Start button)
An incomplete list of reasons include:
1. Enable adding another person to make a group call
2. Allow minimizing Jami to open a document on the Desktop
3. Being able to open a program on the Panel or open a program in the operating system menu using the mouse
Linux Mint 19.1<br>
First noticed this occurring with Jami 2019-04-13
Thank you
Edit: The intercom caller doesn't not work correctly; however, the intercom receiver works correctly.
Not sure if this is just a bug for intercom calls or if it is also a bug for non-intercom callshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1010"Clear history" doesn't refresh the chat window during a call2019-11-18T01:10:12Zovari"Clear history" doesn't refresh the chat window during a call1. Place an intercom audio call
2. Right-click on the conversation and select "Clear history"<br>
for some strange reason the conversation jumps to near the end of the list. Could you enable the conversation (contact) to stay at the top?...1. Place an intercom audio call
2. Right-click on the conversation and select "Clear history"<br>
for some strange reason the conversation jumps to near the end of the list. Could you enable the conversation (contact) to stay at the top? https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1010#note_12886
3. Single left-click on "Toggle show chat" works to toggle chatview https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1010#note_13783 <s>does nothing (bug as it should open the chat)</s>
4. Double left-click on "Toggle show chat" makes Jami takes up the whole screen with the current call and the chat does not show
5. Single <s>Double</s> left-click on "Toggle show chat" and the chat history is not cleared (**bug** as it should show the chat with the history cleared)
Are you able to reproduce?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1011Avatar doesn't show the capitalized first letter2020-03-15T08:38:42ZovariAvatar doesn't show the capitalized first letterJami client shows the avatar as a `?` instead of a `T` for a contact that was added. Please see See https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1011#note_14739 below.
Thank youJami client shows the avatar as a `?` instead of a `T` for a contact that was added. Please see See https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1011#note_14739 below.
Thank youSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1012[bug] [UI] Notification indicator is displayed incorrectly, when there are tw...2021-08-20T16:05:25ZJan Wielkiewicz[bug] [UI] Notification indicator is displayed incorrectly, when there are two accountsNotification indicator (the red thing with a number on a contact image) is displayed incorrectly - when there are two accounts added to one Jami client and both accounts have each other added to the contact list and you send a message fr...Notification indicator (the red thing with a number on a contact image) is displayed incorrectly - when there are two accounts added to one Jami client and both accounts have each other added to the contact list and you send a message from the first one to the second one, and then switch to the other account, the notification indicator is displayed on both accounts, instead of just one. Sorry for such a complicated sentence, I'll show it on a screenshot.
Okay, it's even simpler than this. You just sent a message, click on another contact and the notification indicator appears on the image of the account, we're sending a message to. It displays on the second account too. It happens always.
Have a nice day!
![notification_1](/uploads/6d945a9e808fc973147b112649f3a9bb/notification_1.png)
![notification_2](/uploads/dcec78be00f30083f387fd4d90e21a3f/notification_2.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1013[UI or UX] [enhancement] While typing a message in the typing bar and switchi...2023-05-26T13:59:35ZJan Wielkiewicz[UI or UX] [enhancement] While typing a message in the typing bar and switching to a different conversation, the unready message is displayed there.While typing a message in the typing bar and switching to a different conversation, the unready message is still displayed there. This should be unique for all contacts and accounts (because it happens after switching to another account ...While typing a message in the typing bar and switching to a different conversation, the unready message is still displayed there. This should be unique for all contacts and accounts (because it happens after switching to another account too) to avoid sending a message to a different person, the message was for and to let users type long messages to different people at the same time.
![typing_bar_1](/uploads/8e733cf3b1a48688b09ecd73f9ad1e91/typing_bar_1.png)
After switching:
![typing_bar_2](/uploads/435431390f3bd935d2e7e29d63fdb7e0/typing_bar_2.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1014Audio only call, intermittent internet, makes sound not sent and/or received2019-05-03T16:22:27ZovariAudio only call, intermittent internet, makes sound not sent and/or received**Device A**<br>
Linux Mint 19.1 Cinnamon<br>
3G or 4G mobile internet<br>
Jami built on 2019-04-19 23:02:35 UTC<br>
*OR*<br>
Windows 10<br>
Wired internet
**Device B**<br>
Linux Mint 19.1 Cinnamon<br>
Wired internet<br>
Jami built on 2...**Device A**<br>
Linux Mint 19.1 Cinnamon<br>
3G or 4G mobile internet<br>
Jami built on 2019-04-19 23:02:35 UTC<br>
*OR*<br>
Windows 10<br>
Wired internet
**Device B**<br>
Linux Mint 19.1 Cinnamon<br>
Wired internet<br>
Jami built on 2019-04-19 23:02:35 UTC
1. Device A audio only call to Device B
2. During call Device B internet drops out then is restored (about 3-5 seconds with no internet)
3. Once Internet is restored on Device B, Device B can hear Device A; however, Device A can’t hear Device B.<br>
a) Does Device B resume sending audio once internet is reestablished?<br>
b) Can Device A receive audio once internet is reestablished on Device B?
Tested with non-intercom calls and sound no longer works in conversation when Internet resumes.
Should this issue remain in the GNOME client or should be moved to the daemon (or elsewhere)?
Workarounds:
* End Jami call and call again (Connecting, Searching, Calling, Accept)
* Use Skype
Can you reproduce?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1015Background blur for video calls2019-05-02T14:16:44ZovariBackground blur for video callsPlease enable Jami to blur the background when in a video call.
> ### What is background blur in Skype?
> When the focus belongs on you and not your room, you can choose to blur your background during a video call in Skype. The option ...Please enable Jami to blur the background when in a video call.
> ### What is background blur in Skype?
> When the focus belongs on you and not your room, you can choose to blur your background during a video call in Skype. The option to blur your background is available in Skype on Windows, Mac, Linux, and Skype for Windows 10 (version 14).
>
> #### How do I blur my background during a video call in Skype?
> To start your call with the background blurred, hover over the video button button and select Blur my background. To blur your background during a call, hover over the video button or select the **More** menu and then select **Blur My background**.
>
> #### How do I blur my background for all video calls in Skype?
> To turn background blur on for all calls, click your **profile picture** and click Settings. Click **Audio & Video** then toggle **Blur my background for all calls** to **On**.
>
> #### Why don't I see the option to blur my video?
> In order to blur your background in Skype, your computer processor needs to support Advanced Vector Extensions 2 (AVX2). For more information, check with your computer manufacturer.
>
> https://support.skype.com/en/faq/FA34896/what-is-background-blur-in-skypehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1016Chatview Settings2021-09-26T08:45:47ZovariChatview SettingsSettings, General, Chatview (shown below)
![image](/uploads/a959cbbab0042c2467066f7aaf4fd04f/image.png)
Suggestions:
1. Rename<br>
`Show chatview on the right (on the bottom if off)`<br>
to<br>
`Chatview Pane`
It will make the string ...Settings, General, Chatview (shown below)
![image](/uploads/a959cbbab0042c2467066f7aaf4fd04f/image.png)
Suggestions:
1. Rename<br>
`Show chatview on the right (on the bottom if off)`<br>
to<br>
`Chatview Pane`
It will make the string shorter, more concise.
2. Change<br>
`toggle`<br>
to a<br>
`drop-down`
Depending on your style guide, radio buttons could be shown instead of a drop-down. The radio buttons could be:<br>
`o Side o Bottom`
3. Have drop-down options:<br>
`Side`<br>
`Bottom`
The reason to change `right` to `side` is that right-to-left languages would show the chatview on the left. Having side would make it easier to translate as the context is less likely to get confused.
4. Since the heading is `Chatview`, rename<br>
`Display images and videos into the chatview`<br>
to<br>
`Preview images and videos`
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1018Intercom audio-only calls and chats not working Jami built on 2019-05-02 13:3...2020-10-05T21:05:09ZovariIntercom audio-only calls and chats not working Jami built on 2019-05-02 13:32:46 UTCLinux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-02 13:32:46 UTC
1. Intercom audio calls are not calling calling on the other device. Both devices calling each other at the same time not working either.
2. Intercom chats are not getti...Linux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-02 13:32:46 UTC
1. Intercom audio calls are not calling calling on the other device. Both devices calling each other at the same time not working either.
2. Intercom chats are not getting through to the other device
3. Intercom chats are now showing on the device that wrote the message once the device is shut down and restarted. As you can see in the image below, we shut down the device and turned on the device 12 hours later and our own message was shown. This message should not have been shown as we sent it. Should there be an if statement in the chatview like:<br>
```
IF ( (incomingMessageAccountID=thisDeviceAccountID) AND (incomingMessageDeviceID=thisDeviceID) ) {
// do nothing as this message originated from this device
} ELSE {
// show message is this message did not originate from this device
}
```
![Intercom_audio_calls_and_chats_not_working_Jami_built_on_2019-05-02_133246_UTC](/uploads/e36b3a95dbc7141fbe4b153b28518863/Intercom_audio_calls_and_chats_not_working_Jami_built_on_2019-05-02_133246_UTC.png)
Could this pleased be fixed in the next update as this is a feature we have been using frequently to test Jami. This seems to be a regression as intercom audio calls worked in the previous version of Jami.
Thank you
https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/677<br>
https://git.jami.net/savoirfairelinux/ring-project/issues/554https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1019Intercom contact/conversation should not have a green dot when only 1 instanc...2021-08-19T18:36:05ZovariIntercom contact/conversation should not have a green dot when only 1 instance of the account is onlineWe have ourselves in the conversations list to enable intercom calls, chats and file transfers (we are yet to test intercom file transfers).
Since Jami built on 2019-05-02 13:32:46 UTC, there is always a green dot when there is only one...We have ourselves in the conversations list to enable intercom calls, chats and file transfers (we are yet to test intercom file transfers).
Since Jami built on 2019-05-02 13:32:46 UTC, there is always a green dot when there is only one instance of our account online. There should be no green dot as an intercom call can only be made when there is 2 or more devices online with our name.
This seems to be regression which was introduced with Jami built on 2019-05-02 13:32:46 UTC as the previous version of Jami did not show a green dot when only one instance of our Jami account was online.
Below is an image showing a green dot when only one instance of our Jami account is online.<br>
![image](/uploads/1ec3cb44193c7524cdf6705cca63e740/image.png)
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1020Jami stays offline with no wireless connection and if the wired connection is...2019-09-12T09:23:03ZovariJami stays offline with no wireless connection and if the wired connection is not available when the computer is turned onLinux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-04 03:08:27 UTC
1. Toggle off Wireless connection
2. Toggle on Wired connection
3. Pull out Ethernet cable
4. Turn off computer
5. Turn on computer and leave for a few minutes (eg. moni...Linux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-04 03:08:27 UTC
1. Toggle off Wireless connection
2. Toggle on Wired connection
3. Pull out Ethernet cable
4. Turn off computer
5. Turn on computer and leave for a few minutes (eg. monitor turns off)
6. Plug in Ethernet cable, message on screen shows that connection has been established
7. Check email, this website and they all work<br>
Jami should show online but is showing offline as shown in the image below<br>
![Jami Offline](/uploads/36707fbc193273613dba50899a130fde/image.png)
Can you reproduce?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1021Show Jami connection status in Panel (aka Task Bar in Windows)2021-09-26T07:51:32ZovariShow Jami connection status in Panel (aka Task Bar in Windows)1. Jami icon in the operating system Panel (aka Task Bar in Windows) should show:<br>
![image](/uploads/b71563bc98f11986092bbb1a42842b75/image.png)<br>
a) A `green dot` if all Jami and SIP accounts are online<br>
b) A `red dot` if all Ja...1. Jami icon in the operating system Panel (aka Task Bar in Windows) should show:<br>
![image](/uploads/b71563bc98f11986092bbb1a42842b75/image.png)<br>
a) A `green dot` if all Jami and SIP accounts are online<br>
b) A `red dot` if all Jami and SIP accounts are office<br>
c) A `orange dot` if a combination of Jami and SIP accounts are offline and online
2. This would help knowing Jami's connection status when Jami automatically opens on computer login and is minimized. https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1020#note_13092
3. For accessibility (eg color blind, poor eyesight), the dot could also be replaced by **different** and **larger** symbols, similar to how the Linux Mint Update Manager has different icons depending on its state, as shown in the images below:<br>
a) The `green dot` could be replaced by a `green tick`<br>
![image](/uploads/6dc13724f8b26ba766f6c8ca3ced496d/image.png)<br>
b) The `red dot` could be replaced by a `red X`<br>
![image](/uploads/64a11a069313fd8c263d73a25e3343e6/image.png)<br>
c) The `orange dot` could be replaced by an `orange semicircle` (sorry no orange semicircle shown below)<br>
![image](/uploads/87775e1efe02aa3318550ace916ef3e3/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1022Cannot receive incoming calls until reconnect2023-05-26T13:59:12ZRichard NeumannCannot receive incoming calls until reconnectI am using Arch Linux with jami-{daemon,gnome}-20190412-1 with one SIP account.
I have jami in my gnome-tweaks autostart and jami-gnome is running after login:
`1080 tty2 00:00:04 jami-gnome`
However I will not be able to receive cal...I am using Arch Linux with jami-{daemon,gnome}-20190412-1 with one SIP account.
I have jami in my gnome-tweaks autostart and jami-gnome is running after login:
`1080 tty2 00:00:04 jami-gnome`
However I will not be able to receive calls. All incoming calls will go to voicemail.
I can only receive incoming calls after opening the Jami client GUI, selecting the account preferences and toggling the "Online" Switch back and forth.
From then on I will be able to receive calls.
I'd be happy to help debugging this. Here's today's log:
```
May 07 10:24:36 ThinkCentre jami-gnome[18863]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:24:36 ThinkCentre jami-gnome[18863]: git ref: unknown
May 07 10:24:36 ThinkCentre dbus-daemon[2083]: [session uid=1000 pid=2083] Activating service name='cx.ring.Ring' requested by ':1.104' (uid=1000 pid=18863 comm="jami-gnome ")
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Migrate "/home/neumann/.local/share/gnome-ring" / "." to "/home/neumann/.local/share/jami/."
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Migrate "/home/neumann/.local/share/gnome-ring" / ".." to "/home/neumann/.local/share/jami/.."
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Migrate "/home/neumann/.local/share/gnome-ring" / "profiles" to "/home/neumann/.local/share/jami/profiles"
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Migrate "/home/neumann/.local/share/gnome-ring" / "ring.db" to "/home/neumann/.local/share/jami/ring.db"
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Migrate "/home/neumann/.local/share/gnome-ring" / "vCard" to "/home/neumann/.local/share/jami/vCard"
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Updating all accounts
May 07 10:24:37 ThinkCentre jami-gnome.desktop[2167]: Loading "476e49e2015d7f1a"
May 07 10:24:38 ThinkCentre jami-gnome[18863]: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
May 07 10:24:38 ThinkCentre jami-gnome.desktop[2167]: QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.105'
May 07 10:24:38 ThinkCentre jami-gnome.desktop[2167]: No profile selected or none exists
May 07 10:24:38 ThinkCentre jami-gnome[18863]: no primary network connection detected, check network settings
May 07 10:24:38 ThinkCentre dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.470' (uid=1000 pid=18863 comm="jami-gnome ")
May 07 10:25:17 ThinkCentre jami-gnome.desktop[2167]: UPNP_ENABLED: true
May 07 10:25:19 ThinkCentre jami-gnome.desktop[2167]: UPNP_ENABLED: true
May 07 10:26:17 ThinkCentre jami-gnome.desktop[2167]: UPNP_ENABLED: true
May 07 10:28:57 ThinkCentre jami-gnome[19519]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:28:57 ThinkCentre jami-gnome[19519]: git ref: unknown
May 07 10:29:44 ThinkCentre jami-gnome[1087]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:29:44 ThinkCentre jami-gnome[1087]: git ref: unknown
May 07 10:29:46 ThinkCentre dbus-daemon[831]: [session uid=1000 pid=831] Activating service name='cx.ring.Ring' requested by ':1.61' (uid=1000 pid=1087 comm="jami-gnome --restore-last-window-state ")
May 07 10:31:10 ThinkCentre jami-gnome[1086]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:31:10 ThinkCentre jami-gnome[1086]: git ref: unknown
May 07 10:31:11 ThinkCentre dbus-daemon[826]: [session uid=1000 pid=826] Activating service name='cx.ring.Ring' requested by ':1.61' (uid=1000 pid=1086 comm="jami-gnome --restore-last-window-state ")
May 07 10:31:44 ThinkCentre jami-gnome.desktop[872]: Failed to register: Zeitüberschreitung wurde erreicht
May 07 10:32:30 ThinkCentre jami-gnome.desktop[872]: Failed to register: Zeitüberschreitung wurde erreicht
May 07 10:34:14 ThinkCentre jami-gnome[1088]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:34:14 ThinkCentre jami-gnome[1088]: git ref: unknown
May 07 10:34:15 ThinkCentre dbus-daemon[824]: [session uid=1000 pid=824] Activating service name='cx.ring.Ring' requested by ':1.61' (uid=1000 pid=1088 comm="jami-gnome --restore-last-window-state ")
May 07 10:34:51 ThinkCentre jami-gnome.desktop[870]: Failed to register: Zeitüberschreitung wurde erreicht
May 07 10:36:20 ThinkCentre dbus-daemon[2050]: [session uid=1001 pid=2050] Activating service name='cx.ring.Ring' requested by ':1.84' (uid=1001 pid=2743 comm="jami-gnome ")
May 07 10:37:07 ThinkCentre jami-gnome[3279]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:37:07 ThinkCentre jami-gnome[3279]: git ref: unknown
May 07 10:37:08 ThinkCentre dbus-daemon[3034]: [session uid=1000 pid=3034] Activating service name='cx.ring.Ring' requested by ':1.63' (uid=1000 pid=3279 comm="jami-gnome --restore-last-window-state ")
May 07 10:37:10 ThinkCentre jami-gnome[3279]: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
May 07 10:37:10 ThinkCentre jami-gnome.desktop[3279]: Updating all accounts
May 07 10:37:10 ThinkCentre jami-gnome.desktop[3279]: QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.64'
May 07 10:37:10 ThinkCentre jami-gnome[3279]: no primary network connection detected, check network settings
May 07 10:37:40 ThinkCentre jami-gnome[3279]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 07 10:37:40 ThinkCentre jami-gnome.desktop[3279]: Syncing lrc accounts list with the daemon
May 07 10:37:40 ThinkCentre jami-gnome.desktop[3279]: detected new account ae2773cab659814
May 07 10:37:40 ThinkCentre jami-gnome[3279]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
May 07 10:37:40 ThinkCentre jami-gnome[3279]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
May 07 10:37:40 ThinkCentre jami-gnome[3279]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
May 07 10:37:40 ThinkCentre jami-gnome[3279]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: received account changed for non existing account "ae2773cab659814"
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: Loading "ae2773cab659814"
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: building missing account "ae2773cab659814"
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: Updating all accounts
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: Reloading "ae2773cab659814" "SIP"
May 07 10:37:41 ThinkCentre jami-gnome.desktop[3279]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:37:55 ThinkCentre jami-gnome.desktop[3279]: UPNP_ENABLED: true
May 07 10:37:56 ThinkCentre jami-gnome.desktop[3279]: UPNP_ENABLED: true
May 07 10:37:58 ThinkCentre jami-gnome.desktop[3279]: UPNP_ENABLED: true
May 07 10:37:58 ThinkCentre jami-gnome.desktop[3279]: Account "ae2773cab659814" status changed to "Forbidden"
May 07 10:37:59 ThinkCentre jami-gnome.desktop[3279]: UPNP_ENABLED: true
May 07 10:37:59 ThinkCentre jami-gnome.desktop[3279]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:38:00 ThinkCentre jami-gnome.desktop[3279]: Account "ae2773cab659814" status changed to "Forbidden"
May 07 10:38:10 ThinkCentre jami-gnome.desktop[3279]: UPNP_ENABLED: true
May 07 10:38:10 ThinkCentre jami-gnome.desktop[3279]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:38:46 ThinkCentre jami-gnome[3279]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:38:46 ThinkCentre jami-gnome[3279]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:38:46 ThinkCentre jami-gnome[3279]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:38:46 ThinkCentre jami-gnome[3279]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:38:46 ThinkCentre jami-gnome[3279]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:39:24 ThinkCentre jami-gnome[1069]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:39:24 ThinkCentre jami-gnome[1069]: git ref: unknown
May 07 10:39:25 ThinkCentre dbus-daemon[813]: [session uid=1000 pid=813] Activating service name='cx.ring.Ring' requested by ':1.61' (uid=1000 pid=1069 comm="jami-gnome --restore-last-window-state ")
May 07 10:39:27 ThinkCentre jami-gnome.desktop[1069]: Updating all accounts
May 07 10:39:27 ThinkCentre jami-gnome.desktop[1069]: Loading "ae2773cab659814"
May 07 10:39:30 ThinkCentre jami-gnome[1069]: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
May 07 10:39:30 ThinkCentre jami-gnome.desktop[1069]: No profile selected or none exists
May 07 10:39:30 ThinkCentre jami-gnome[1069]: no primary network connection detected, check network settings
May 07 10:39:30 ThinkCentre jami-gnome.desktop[1069]: QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.62'
May 07 10:40:49 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:40:49 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:40:50 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:40:50 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:41:07 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:41:07 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:41:55 ThinkCentre jami-gnome.desktop[1069]: could not open shm area "" , shm_open failed: Das Argument ist ungültig
May 07 10:42:22 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:22 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:42:27 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:27 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:42:32 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:32 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:42:34 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:34 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:42:34 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:34 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:42:38 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:38 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:42:43 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:42:43 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:43:05 ThinkCentre jami-gnome[1069]: invalid cast from 'IncomingCallView' to 'ChatView'
May 07 10:43:05 ThinkCentre jami-gnome[1069]: void chat_view_update_temporary(ChatView*): assertion 'IS_CHAT_VIEW(self)' failed
May 07 10:43:05 ThinkCentre jami-gnome.desktop[1069]: Add call to conversation with [redacted]
May 07 10:43:05 ThinkCentre jami-gnome.desktop[1069]: Add call to conversation with [redacted]
May 07 10:43:05 ThinkCentre jami-gnome.desktop[1069]: slotCallStateChanged (call: 3781969971853620026), from Eingehend to Sprechend
May 07 10:43:05 ThinkCentre jami-gnome.desktop[1069]: vCard image loading failed
May 07 10:43:11 ThinkCentre jami-gnome.desktop[1069]: slotCallStateChanged (call: 3781969971853620026), from Sprechend to Abgeschlossen
May 07 10:43:11 ThinkCentre jami-gnome[1069]: g_source_remove: assertion 'tag > 0' failed
May 07 10:43:11 ThinkCentre jami-gnome.desktop[1069]: slotCallStateChanged (call: 3781969971853620026), from Abgeschlossen to Abgeschlossen
May 07 10:43:11 ThinkCentre jami-gnome.desktop[1069]: Renderer 3781969971853620026 not found
May 07 10:43:15 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:43:15 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:43:37 ThinkCentre jami-gnome.desktop[1069]: UPNP_ENABLED: true
May 07 10:43:37 ThinkCentre jami-gnome.desktop[1069]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:43:42 ThinkCentre jami-gnome.desktop[1069]: Add call to conversation with [redacted]
May 07 10:43:42 ThinkCentre jami-gnome.desktop[1069]: Add call to conversation with [redacted]
May 07 10:43:49 ThinkCentre jami-gnome.desktop[1069]: slotCallStateChanged (call: 1407943447111313409), from Eingehend to Abgeschlossen
May 07 10:43:49 ThinkCentre jami-gnome.desktop[1069]: slotCallStateChanged (call: 1407943447111313409), from Abgeschlossen to Abgeschlossen
May 07 10:43:49 ThinkCentre jami-gnome.desktop[1069]: Renderer 1407943447111313409 not found
May 07 10:43:58 ThinkCentre jami-gnome[1069]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:44:34 ThinkCentre jami-gnome[1072]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:44:34 ThinkCentre jami-gnome[1072]: git ref: unknown
May 07 10:44:36 ThinkCentre dbus-daemon[812]: [session uid=1000 pid=812] Activating service name='cx.ring.Ring' requested by ':1.60' (uid=1000 pid=1072 comm="jami-gnome --restore-last-window-state ")
May 07 10:44:39 ThinkCentre jami-gnome.desktop[1072]: Updating all accounts
May 07 10:44:39 ThinkCentre jami-gnome.desktop[1072]: Loading "ae2773cab659814"
May 07 10:44:41 ThinkCentre jami-gnome[1072]: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
May 07 10:44:41 ThinkCentre jami-gnome.desktop[1072]: QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.62'
May 07 10:44:41 ThinkCentre jami-gnome.desktop[1072]: No profile selected or none exists
May 07 10:44:41 ThinkCentre jami-gnome[1072]: no primary network connection detected, check network settings
May 07 10:46:09 ThinkCentre dbus-daemon[473]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.285' (uid=1000 pid=1072 comm="jami-gnome --restore-last-window-state ")
May 07 10:46:20 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:46:20 ThinkCentre jami-gnome.desktop[1072]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:46:23 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:46:23 ThinkCentre jami-gnome.desktop[1072]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:46:23 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:46:23 ThinkCentre jami-gnome.desktop[1072]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:46:25 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:46:25 ThinkCentre jami-gnome.desktop[1072]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:46:25 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:46:25 ThinkCentre jami-gnome.desktop[1072]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:46:56 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:46:56 ThinkCentre jami-gnome.desktop[1072]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:47:01 ThinkCentre jami-gnome.desktop[1072]: UPNP_ENABLED: true
May 07 10:47:07 ThinkCentre jami-gnome.desktop[1072]: Add call to conversation with [redacted]
May 07 10:47:07 ThinkCentre jami-gnome.desktop[1072]: Add call to conversation with [redacted]
May 07 10:47:10 ThinkCentre jami-gnome.desktop[1072]: slotCallStateChanged (call: 8400130596285038025), from Eingehend to Inaktiv
May 07 10:47:10 ThinkCentre jami-gnome.desktop[1072]: slotCallStateChanged (call: 8400130596285038025), from Inaktiv to Abgeschlossen
May 07 10:47:10 ThinkCentre jami-gnome.desktop[1072]: Renderer 8400130596285038025 not found
May 07 10:47:20 ThinkCentre jami-gnome[1072]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:47:20 ThinkCentre jami-gnome[1072]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:47:20 ThinkCentre jami-gnome[1072]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:47:58 ThinkCentre jami-gnome[1077]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:47:58 ThinkCentre jami-gnome[1077]: git ref: unknown
May 07 10:47:58 ThinkCentre dbus-daemon[828]: [session uid=1000 pid=828] Activating service name='cx.ring.Ring' requested by ':1.61' (uid=1000 pid=1077 comm="jami-gnome --restore-last-window-state ")
May 07 10:48:02 ThinkCentre jami-gnome.desktop[1077]: Updating all accounts
May 07 10:48:02 ThinkCentre jami-gnome.desktop[1077]: Loading "ae2773cab659814"
May 07 10:48:04 ThinkCentre jami-gnome[1077]: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
May 07 10:48:04 ThinkCentre jami-gnome.desktop[1077]: QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.62'
May 07 10:48:04 ThinkCentre jami-gnome.desktop[1077]: No profile selected or none exists
May 07 10:48:04 ThinkCentre jami-gnome[1077]: no primary network connection detected, check network settings
May 07 10:49:43 ThinkCentre jami-gnome.desktop[1077]: slotCallStateChanged (call: 7835061968924342749), from Suchen to Verbindet
May 07 10:49:47 ThinkCentre jami-gnome.desktop[1077]: slotCallStateChanged (call: 7835061968924342749), from Verbindet to Rufaufbau
May 07 10:49:49 ThinkCentre jami-gnome.desktop[1077]: slotCallStateChanged (call: 7835061968924342749), from Rufaufbau to Abgeschlossen
May 07 10:49:50 ThinkCentre jami-gnome.desktop[1077]: slotCallStateChanged (call: 7835061968924342749), from Abgeschlossen to Abgeschlossen
May 07 10:49:50 ThinkCentre jami-gnome.desktop[1077]: Renderer 7835061968924342749 not found
May 07 10:50:11 ThinkCentre jami-gnome.desktop[1077]: UPNP_ENABLED: true
May 07 10:50:11 ThinkCentre jami-gnome.desktop[1077]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:50:14 ThinkCentre jami-gnome.desktop[1077]: UPNP_ENABLED: true
May 07 10:50:21 ThinkCentre jami-gnome.desktop[1077]: Add call to conversation with [redacted]
May 07 10:50:21 ThinkCentre jami-gnome.desktop[1077]: Add call to conversation with [redacted]
May 07 10:50:23 ThinkCentre jami-gnome.desktop[1077]: slotCallStateChanged (call: 14059482004884193457), from Eingehend to Inaktiv
May 07 10:50:23 ThinkCentre jami-gnome.desktop[1077]: slotCallStateChanged (call: 14059482004884193457), from Inaktiv to Abgeschlossen
May 07 10:50:23 ThinkCentre jami-gnome.desktop[1077]: Renderer 14059482004884193457 not found
May 07 10:50:41 ThinkCentre jami-gnome[1077]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:50:41 ThinkCentre jami-gnome[1077]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:50:41 ThinkCentre jami-gnome[1077]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
May 07 10:51:27 ThinkCentre jami-gnome[1080]: Jami GNOME client version: 5e0c3e2b3557ff936b5d3fc87670fef0e9a3b8d1
May 07 10:51:27 ThinkCentre jami-gnome[1080]: git ref: unknown
May 07 10:51:28 ThinkCentre dbus-daemon[817]: [session uid=1000 pid=817] Activating service name='cx.ring.Ring' requested by ':1.61' (uid=1000 pid=1080 comm="jami-gnome --restore-last-window-state ")
May 07 10:51:32 ThinkCentre jami-gnome.desktop[1080]: Updating all accounts
May 07 10:51:32 ThinkCentre jami-gnome.desktop[1080]: Loading "ae2773cab659814"
May 07 10:51:33 ThinkCentre jami-gnome[1080]: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
May 07 10:51:33 ThinkCentre jami-gnome.desktop[1080]: QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.62'
May 07 10:51:33 ThinkCentre jami-gnome.desktop[1080]: No profile selected or none exists
May 07 10:51:33 ThinkCentre jami-gnome[1080]: no primary network connection detected, check network settings
May 07 10:52:48 ThinkCentre jami-gnome.desktop[1080]: UPNP_ENABLED: true
May 07 10:52:48 ThinkCentre jami-gnome.desktop[1080]: Account "ae2773cab659814" status changed to "Default status message"
May 07 10:52:49 ThinkCentre jami-gnome.desktop[1080]: UPNP_ENABLED: true
May 07 10:52:53 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with [redacted]
May 07 10:52:53 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with [redacted]
May 07 10:52:55 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 11321424850374077373), from Eingehend to Inaktiv
May 07 10:52:55 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 11321424850374077373), from Inaktiv to Abgeschlossen
May 07 10:52:55 ThinkCentre jami-gnome.desktop[1080]: Renderer 11321424850374077373 not found
May 07 10:53:09 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with 10
May 07 10:53:09 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with 10
May 07 10:53:12 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 6131540438392397977), from Eingehend to Sprechend
May 07 10:53:12 ThinkCentre jami-gnome[1080]: g_source_remove: assertion 'tag > 0' failed
May 07 10:53:12 ThinkCentre jami-gnome.desktop[1080]: vCard image loading failed
May 07 10:53:16 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 6131540438392397977), from Sprechend to Abgeschlossen
May 07 10:53:16 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 6131540438392397977), from Abgeschlossen to Abgeschlossen
May 07 10:53:16 ThinkCentre jami-gnome.desktop[1080]: Renderer 6131540438392397977 not found
May 07 10:53:32 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with [redacted]
May 07 10:53:32 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with [redacted]
May 07 10:53:35 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 5674002857852068064), from Eingehend to Sprechend
May 07 10:53:35 ThinkCentre jami-gnome.desktop[1080]: vCard image loading failed
May 07 10:53:46 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 5674002857852068064), from Sprechend to Abgeschlossen
May 07 10:53:46 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 5674002857852068064), from Abgeschlossen to Abgeschlossen
May 07 10:53:46 ThinkCentre jami-gnome.desktop[1080]: Renderer 5674002857852068064 not found
May 07 10:53:52 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with [redacted]
May 07 10:53:52 ThinkCentre jami-gnome.desktop[1080]: Add call to conversation with [redacted]
May 07 10:54:01 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 2391830086933611372), from Eingehend to Inaktiv
May 07 10:54:01 ThinkCentre jami-gnome.desktop[1080]: slotCallStateChanged (call: 2391830086933611372), from Inaktiv to Abgeschlossen
May 07 10:54:01 ThinkCentre jami-gnome.desktop[1080]: Renderer 2391830086933611372 not found
```https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1023Both contacts (me & peer) are online (green dot), but cached messages are not...2021-08-16T20:53:22ZannaBoth contacts (me & peer) are online (green dot), but cached messages are not deliveredThe "sending dots" are still bouncing. Latest Ubuntu 18.04 Jami nightly build.
And it looks as if this event occurs several times a day.The "sending dots" are still bouncing. Latest Ubuntu 18.04 Jami nightly build.
And it looks as if this event occurs several times a day.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1025[intercom] Clicking "Open conversation" in the Notifications doesn't do anything2020-10-09T16:18:12Zovari[intercom] Clicking "Open conversation" in the Notifications doesn't do anythingSeems to be a regression as this used to work.
![image](/uploads/89e5aa1483eaa8cbe4c2e72b58c01c38/image.png)
Have not yet checked with non-intercom chat messages. If a developer reads this and has us on their Jami account, feel free to...Seems to be a regression as this used to work.
![image](/uploads/89e5aa1483eaa8cbe4c2e72b58c01c38/image.png)
Have not yet checked with non-intercom chat messages. If a developer reads this and has us on their Jami account, feel free to send a message and we will update this ticket. Thanks in advance.
Linux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-04 03:08:27 UTChttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1026Do not show the "Let a Message View" for SIP accounts2020-11-26T21:27:23ZSébastien BlinDo not show the "Let a Message View" for SIP accountshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1027Account' settings bug2019-11-17T23:41:37ZMohamed FenjiroAccount' settings bugWhen first installing Jami and going into settings, the user cannot go directly in account's settings
![image](/uploads/40837fde9172ad957559e9c552d11452/image.png)When first installing Jami and going into settings, the user cannot go directly in account's settings
![image](/uploads/40837fde9172ad957559e9c552d11452/image.png)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1028Account linking with archive doesn't seem to work2019-06-05T18:41:14ZMohamed FenjiroAccount linking with archive doesn't seem to workIf you take the .gz archive from another Linux computer and load it into the gnome client, it fails.
Logs:
![image](/uploads/4ab5721388232b7325ce7de84f670349/image.png)If you take the .gz archive from another Linux computer and load it into the gnome client, it fails.
Logs:
![image](/uploads/4ab5721388232b7325ce7de84f670349/image.png)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1029Jami-gnome wont start; LLVM error2020-04-02T08:14:33ZherrwuselJami-gnome wont start; LLVM errorSo installed Jami first from the homepage's deb file and then upgraded it from the provided source ``https://dl.jami.net/ring-nightly/ubuntu_18.10/ ring main`` on my Kubuntu 18.10 machine.
When trying to open Jami I get this:
```
$ jami...So installed Jami first from the homepage's deb file and then upgraded it from the provided source ``https://dl.jami.net/ring-nightly/ubuntu_18.10/ ring main`` on my Kubuntu 18.10 machine.
When trying to open Jami I get this:
```
$ jami-gnome
** Message: 10:08:03.232: Jami GNOME client version: 470dfebacccd57b1b5571b04a35d98eadde0c94d
** Message: 10:08:03.232: git ref: unknown
Updating all accounts
Loading "93fc7f94b97b8a1e"
Loading "9896cc78b4126170"
LLVM ERROR: out of memory
Abgebrochen (Speicherabzug geschrieben)
```