Jami flatpak no more launched after upgrade to Fedora 30 !

[Nokia808]

Hi. I upgraded my Fedora 28 to 30 by CLI via tty terminal without error messages. After upgraded, all my flatpak application from FlatHub are working without any issue. Only this package, which completely failed to start !

I remove it then re-installed it again but same error - see screenshot bellow:

[different55]

Also having this issue on Fedora 30 with Jami installed from FlatHub. Girlfriend on Solus isn't having any issues with Jami from FlatHub.

[AmarOk1412]

dring is not in the flatpak, so indeed the flatpak is not a standalone app for now.

I tried an approach in the PR linked to that issue. But I never did any flatpak packages before. For now, I can use the flatpak as a standalone app, create accounts/do calls (audio, can't access the webcam)/send messages.

[ntninja]

@Nokia808 @different55: Since I have continued work on this, it'd be very helpful if at least one of you could give some feedback if the latest version still exhibits this issue for you. (Actually dring did start but kept immediately crashing until jami-gnome appp gave up on it.)

For what it's worth: Sorry for the long radio-silence everybody – after Flathub failed to build the package for indecipherable reasons I ended up looking at other projects for the time being instead.

[Nokia808]

@alexander255 Hi. I tested the new version you just pushed (20191209.1.4b48135). The application still NOT launched ! It is always crashing at every time trying to launch it !

Moreover, it seem now more sever. I received a system error notification saying:

"Oops! We are sorry, it looks like a problem occurred. If you'd like to help resolve the issue, please send a report."

---

Edit: there is something new too: after installed it by GNOME software, AFTER THAT BY ABOUT 15 MINUTES I received a notification that "installation is completed & now you can use Jami" !!! I received this after I posted this replay, so I re-tried to re-launched Jami, BUT SAME ERROR:

"Oops! We are sorry, it looks like a problem occurred. If you'd like to help resolve the issue, please send a report."

[ntninja]

@Nokia808 Thanks for the quick feedback! Are you still on Fedora? Does that “Oops!” notification have any extra information that could be useful?

[Nokia808]

@alexander255

Hi. I'm still on Fedora 30 X64 bit Cinnamon edition.

Please do you noticed my edition for previous replay ? I added something new & will post it bellow also:

there is something new too: after installed it by GNOME software, AFTER THAT BY ABOUT 15 MINUTES I received a notification that "installation is completed & now you can use Jami" !!! I received this after I posted this replay, so I re-tried to re-launched Jami, BUT SAME ERROR:

"Oops! We are sorry, it looks like a problem occurred. If you'd like to help resolve the issue, please send a report."

[ntninja]

Yes, I've seen the edit. Does clicking on the “Oops!” message show anything useful?

Also beyond that: Are you willing to help me out on in diagnosing this issue, because I'm here on Debian and everything just works… :slightly_frowning_face:

[Nokia808]

@alexander255 Yes I would like to help you, but how? Please notice that I'm not a programmer & merely a desktop user not a system admin of a server, so I'm not a power user of Linux.

I think that there is a fatal error in the flatpak package as long as it working on Debian but not on other distro like Fedora. Also, I thing that the best way is to test this issue by you on a Fedora on a secondary PC like your old PC if available .....

[ntninja]

Yes I would like to help you, but how? Please notice that I'm not a programmer & merely a desktop user not a system admin of a server, so I'm not a power user of Linux.

That's OK, I just need you to run some commands in terminal and send me the results. :slightly_smiling_face:

So if your willing to help please install the GNOME SDK runtime:
flatpak install flathub org.gnome.Sdk//3.34

Then run dring standalone with debug output:
flatpak run --devel --command=/app/lib/ring/dring net.jami.Jami -cdp 2>&1 | tee dring.log

Then, in another terminal window, start jami itself:
flatpak run --devel net.jami.Jami --debug 2>&1 | tee jami-gnome.log

After everything has crashed, collect the generated dring.log and jami-gnome.log files and upload them for me to review: https://storage.ninetailed.ninja/index.php/s/byAeXkqZN2jcXbc

Thanks for your help!

[Nokia808]

@alexander255 Hi I perform all what you asked me to do apart from uploading logs file to you because there is something you did not expect ! The case is as following:

1) No thing crashed ! Jami launched. I did not tried to create new account. I just tried to see if I click "import from other device" option work or not. I click on it, & it opened to me window asked for password + PIN. I did not complete the import, but I clicked on "previous" then exit Jami.

2) Then I tried to launch Jami by usual way:

• I closed all terminal windows,
• tried to launch Jami from within GUI (application menu Jami icon), BUT JAMI CRASHED !!

Now do you need for log files ?

Also, give me the command by which I can remove "org.gnome.Sdk//3.34" that you asked to install it because I'm not familiar so much with flatpak commands. I will remove it after you have no further need to use it.

I'm waiting you.

[Nokia808]

@alexander255 By the way, does log files contain some secret data that if known to hacker will allow him (or make it easer to him) to spay on my Jami communications ? I noticed that it contain:

0mSipTransportBroker@xxxxxxxxxxxxxxxxxxxxxxxxxx 0mSIPVoIPLink@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0mRegistered thread xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Are these secrets & should not known by hackers

[ntninja]

@Nokia808: Interesting result! Could you try running just flatpak run --devel net.jami.Jami --debug 2>&1 | tee jami-gnome.log without any other command and see if that also works?

If yes, then try running it with just: flatpak run net.jami.Jami 2>&1 | tee jami-gnome.log and check again.

The command for removing the SDK is flatpak uninstall org.gnome.Sdk//3.34, just the opposite of install actually.

Also please run the following so that I can see which command opening Jami from the applications list actually runs: for path in $(echo $XDG_DATA_DIRS | tr ':' ' '); do for filepath in ${path}/applications/*.desktop; do case "${filepath}" in */*jami*.desktop) echo "${filepath}"; cat "${filepath}"; echo; echo; esac; done; done

As far as I know the log do not contain confidential data, but in case I'm wrong please only upload your logs to https://storage.ninetailed.ninja/index.php/s/byAeXkqZN2jcXbc, so that nobody else can see. Also using throwaway accounts during testing helps making sure that nothing of importance may even be present in these logs. (I might ask for crash data in the future and this will contain sensitive key material, so only use dummy accounts in any case.)

[Nokia808]

@alexander255 Hi again ! 1) I tried only: flatpak run --devel net.jami.Jami --debug 2>&1 | tee jami-gnome.log it lead to launch Jami okay. So, & as you asked me to do: 2) I tried only: flatpak run net.jami.Jami 2>&1 | tee jami-gnome.log It worked also, & Jami launched okay. In both cases I did not do any thing else: just execute command then close Jami window & then close terminal. 3) the output of 3rd command is as following:

$ for path in $(echo $XDG_DATA_DIRS | tr ':' ' '); do for filepath in ${path}/applications/*.desktop; do case "${filepath}" in */*jami*.desktop) echo "${filepath}"; cat "${filepath}"; echo; echo; esac; done; done
/var/lib/flatpak/exports/share/applications/net.jami.Jami.desktop
[Desktop Entry]
Name=Jami
GenericName=Jami
Comment[hu]=A Jami egy biztonságos és elosztott csevegőprogram
Comment[ru]=Jami — приложение для защищённой связи с распределённой архитектурой
Comment=Jami is a secured and distributed communication software
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=jami-gnome --file-forwarding net.jami.Jami @@u %u @@
Icon=net.jami.Jami
StartupNotify=true
Terminal=false
Type=Application
Categories=GNOME;GTK;Network;Telephony;
Keywords=chat;talk;im;message;voip;
X-Flatpak-RenamedFrom=jami-gnome.desktop;
X-Flatpak=net.jami.Jami

4) please inform me know: which log command(s) you like me to upload to you? Till know you supply me by 4 log commands.

[ntninja]

please inform me know: which log command(s) you like me to upload to you? Till know you supply me by 4 log commands.

None yet I fear. After all it should have crashed, right?

Could you also try running the line from desktop file you posted:

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=jami-gnome --file-forwarding net.jami.Jami 2>&1 | tee jami-gnome.log

It really should do the same as that last command, otherwise I'm not sure what is happening unfortunately.

[Nokia808]

@alexander255 I run the line you asked me to run, & it worked: Jami launched okay. Also, I did not tried to do any thing else. I closed Jami & closed terminal.

Please, do you like me to perform further things like creating a test account, to see if crashes occurring or not? Also, meanwhile, what is the best command to run Jami for know from all what you gave me?

[Nokia808]

Hi. I run the following command:

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=jami-gnome --file-forwarding net.jami.Jami @@u %u @@

Jami launched normally! It is the same in application menu. So , I closed every thing (Jami & terminal) & tried to launch Jami from within GUI (Cinnamon application menu) & IT WORKED FOR ME !!

Will restarted my PC & retest from GUI again. What it was changed !!

[Nokia808]

Hi again. 1) I powered off my PC, 2) re-launched again after 19 minutes (after did a home task for family), 3) tried to launched Jami from within GUI (my Cinnamon application menu),

& it worked to me !! Jami, finally, launched on my Fedora 30 from GUI !! What it was this ?!

However, I noticed - by using terminal - the following output:

$ /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=jami-gnome --file-forwarding net.jami.Jami @@u %u @@
** Message: 13:14:57.394: Jami GNOME client version: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
** Message: 13:14:57.394: git ref: unknown
No accounts to migrate

(jami-gnome:2): Gtk-CRITICAL **: 13:14:57.842: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed

(jami-gnome:2): Gtk-WARNING **: 13:14:57.929: Theme parsing error: <data>:1:273: not a number
QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.713'

(jami-gnome:2): Gdk-CRITICAL **: 13:14:58.396: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

Please notice that I hide "client version" by xxxxxxxxxxxxxxxxxxxxxxxx though I think it is not something secure.

Also, when I tried to quit Jami from within system try icon of Jami, the following lines added to the above code:

(jami-gnome:2): Gtk-CRITICAL **: 13:17:02.844: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(jami-gnome:2): Gtk-CRITICAL **: 13:17:02.845: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(jami-gnome:2): Gtk-CRITICAL **: 13:17:02.846: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(jami-gnome:2): Gtk-CRITICAL **: 13:17:02.846: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

However, every thing closed: Jami & the terminal.

Next step is to try to use Jami for communication.

Any thing, further or closed this long standing issue? By the way, what : 13:17:02.846: & like refer to? A time stamp ?

[AmarOk1412]

The client version is only a commit and used for debug.

The only things that is confidential in logs are generally in the daemon logs:

• Your ip used to do p2p communications such as calls and file transfer
• Your jami id
• Your contacts id when getting presence update/doing name server requests

[Nokia808]

@AmarOk1412 Hi. Thank you very much for this replay. So, what I asked about is merely a time stamp (time at which launched Jami at which) & no thing confidental.

Only one question though not on this topic - as you a member in Jami team: which is more secure, create Jami account on Linux device then link it (by PIN) to Android mobile, or creating Jami account on Android device then link it to Linux device? Currently I'm using Jami account created on my Android mobile & link it to my PC using PIN option. Is deleting this account & creating new account on Fedora Linux then link it to my Android mobile will give more security or the same?

Otherwise, I'm waiting @alexander255 to close this issue.

[AmarOk1412]

The same code is used to generate accounts on android or Linux, it's just the daemon. It will give the exact same thing on both devices

[Nokia808]

@AmarOk1412 Many thanks for replay. I'm waiting @alexander255 if he need something else regarding this issue. Otherwise, I think it should be closed.

But please @AmarOk1412 I have other issue I will open it on Jami official repository (Android version).

Please @alexander255 if you have no thing else from me in this issue, then close it from your side. But follow me on remaining issue that opened by me & still open because now only IM messages are possible while no any audio nor video communication possible !

[ntninja]

@Nokia808: I'm glad to hear that it works for you now, although I hate when things suddenly just start working, as somebody else will also have this issue and they might not be so helpful in debugging.

Of course, since there is nothing more to do here, I'm going to close this issue as you suggested. Let's continue in issue #4, I'll be pushing a build with working audio calls soon and then ping you there.