empathy issueshttps://gitlab.gnome.org/GNOME/empathy/issues2019-04-13T12:11:09Zhttps://gitlab.gnome.org/GNOME/empathy/issues/916Add missing prepend function in js for history loading2019-04-13T12:11:09ZGNOME Gitlab AutomationAdd missing prepend function in js for history loadingThe following Merge Request (MR) has been forwarded from GitHub in order to prevent
the GNOME Project from losing contributions coming from un-official channels. And for
contributors to not see their valuable contributions not being accounted for.
Relevant information:
Github handle: noonien-d
MR URL: https://github.com/GNOME/empathy/pull/6
Patch URL: https://github.com/GNOME/empathy/pull/6.patch
Body of the MR:
I experienced a bug in master regarding chat history not getting shown
sometimes. This is due to a missing "prepend" function in the webview
js code.githubhttps://gitlab.gnome.org/GNOME/empathy/issues/914Empathy at flathub.org2018-12-06T00:18:46ZMiguel Sánchez de León PequeEmpathy at flathub.orgIt would be great if Empathy could be distributed as a Flatpak package through [flathub.org](https://flathub.org).
Probably related: https://gitlab.gnome.org/GNOME/empathy/issues/902https://gitlab.gnome.org/GNOME/empathy/issues/913Jabber Account connecting forever2018-11-07T14:27:43ZP1zz4br0etch3nJabber Account connecting foreverI've tried using empathy to connect to our cisco jabber server several times in the past few years on different machines with different distros (ubuntu gnome, fedora) and it never worked while pidgin was always working fine. I can't believe that this isn't getting fixed.
Current Distro: Fedora 28\
Gnome Version: 3.28.3\
Empathy Version: 3.12.14
steps to reproduce:
1. start empathy
2. add jabber account
3. specify server (different from user domain)
4. accept server certificate
expected behaviour:\
Establish connection and load contact list
actual behaviour:\
say "connecting..." and never do
here are my logs from starting to connect:
[empathy.log](/uploads/42fffe53e8b9db2966bb69d697938b94/empathy.log)
I replaced every server/user/domain name with tags like `<server>` for privacy reasons
I hope this helps getting it finally fixedhttps://gitlab.gnome.org/GNOME/empathy/issues/911Yahoo Messenger ceasing operation July 18, 20182018-06-12T18:23:41ZMichael KaulbachYahoo Messenger ceasing operation July 18, 2018Adding Yahoo Messenger accounts to Empathy should probably be disabled after this date.
https://help.yahoo.com/kb/messenger/SLN28776.htmlhttps://gitlab.gnome.org/GNOME/empathy/issues/910BoF sscanf()2018-05-22T19:19:53Zbugzilla-migrationBoF sscanf()## Submitted by Team w00t
**[Link to original bug (#796266)](https://bugzilla.gnome.org/show_bug.cgi?id=796266)**
## Description
Hi Team,
https://github.com/GNOME/empathy/blob/master/libempathy-gtk/empathy-geometry.c#L229
i.e
sscanf (str, GEOMETRY_POSITION_FORMAT, &x, &y, &w, &h);
The scanf() family's %s operation, without a limit specification, permits buffer overflows such as (CWE-120, CWE-20).
Specify a limit to %s, or use a different input function. If the scanf format is influenceable by an attacker, it's exploitable.
i.e
sscanf (str, GEOMETRY_POSITION_FORMAT, &x, &y, &w, &h);
Request team to please have a look and advise for same.
Cheers
Team w00t
Version: 3.25.xbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/909fix crash when some external APIs fail2018-05-22T19:19:44Zbugzilla-migrationfix crash when some external APIs fail## Submitted by Zhouyang
**[Link to original bug (#793949)](https://bugzilla.gnome.org/show_bug.cgi?id=793949)**
## Description
Created attachment 369129
patch of the potential API bugs
Hi,
I'm a PhD student. I analyzed the empathy source code and found some potential API bugs that may cause crashes.
These crashes are mainly caused by insufficient error handling of API functions like notify_init or pa_context_connect.
I think it's unsafe to assume the library function would be correct. It would be better if we could handle the error properly.
Attached please find the patch against version current development version. Hopefully, it can solve these potential bugs.
Best,
Zhouyang
**Patch 369129**, "patch of the potential API bugs":
[api_bugs_empathy-trunk.patch](/uploads/97f5e5ef34fbb266df8107a5cb01a070/api_bugs_empathy-trunk.patch)
Version: 3.25.x5. Notificationsbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/908Bad usability problems with new-style Empathy2018-05-22T19:19:30Zbugzilla-migrationBad usability problems with new-style Empathy## Submitted by Tobias Wolf
**[Link to original bug (#788338)](https://bugzilla.gnome.org/show_bug.cgi?id=788338)**
## Description
I was using Empathy "in production" and received the new version when upgrading my work laptop to Ubuntu+1.
I appreciate the move to single windows kind of makes sense. But a lot of stuff is just broken now. This was released prematurely.
- No more user groups, seems to be LRU now?
But only changes after a restart
My company makes heavy use of groups
- "Show groups" has no effect
- "Hide offline" has no effect
- Ctrl-C for copy does not work, WTF, why?
- Alt-1 through Alt-9 for switching tabs is gone
- Ctrl-W for close tab is gone
- Ctrl-H for "hide offline" is gone
- No more type-ahead find in roster
- Large padding around central widget
- Font size changed, I was using a specific font size and had
to edit my theme file
Now I am really hesitant of upgrading
Version: 3.25.xbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/9073.25.90: empathy-tls-test fails on 32-bit architectures2018-05-22T19:19:19Zbugzilla-migration3.25.90: empathy-tls-test fails on 32-bit architectures## Submitted by Jeremy Bicha `@jbicha`
**[Link to original bug (#788161)](https://bugzilla.gnome.org/show_bug.cgi?id=788161)**
## Description
empathy 3.25.90 fails to build on 32-bit architectures.
https://buildd.debian.org/status/logs.php?pkg=empathy&ver=3.25.90-1
(Click Maybe Successful/Failed to see the full build logs).
Build log excerpt
-----------------
FAIL: empathy-tls-test
======================
/tls/certificate_basics: OK
/tls/certificate_verify_success_with_full_chain: FAIL empathy-tls-test (exit status: 139)
ppc64 and s390x (64-bit architectures) have a different failure:
---------------
FAIL: empathy-tls-test
======================
/tls/certificate_basics: OK
/tls/certificate_verify_success_with_full_chain:
(/<`<PKGBUILDDIR>`>/tests/.libs/empathy-tls-test:62599): Gcr-CRITICAL **: gcr_simple_certificate_new: assertion 'n_data' failed
Version: 3.25.xbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/906Last message summary in activity window isn&#39;t updated2018-05-22T19:19:08Zbugzilla-migrationLast message summary in activity window isn't updated## Submitted by Diane Trout `@detrout`
**[Link to original bug (#787565)](https://bugzilla.gnome.org/show_bug.cgi?id=787565)**
## Description
In the new 3.25 merged window view. It appears it's trying to show the last message received in the contact list.
Unfortunately its not being updated as new messages come in.
Version: 3.25.x5. Contact Listbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/905Renaming app to org.gnome.Empathy breaks app tracking2018-05-22T19:18:59Zbugzilla-migrationRenaming app to org.gnome.Empathy breaks app tracking## Submitted by Peter Y. Chuang `@peterychuang`
**[Link to original bug (#787298)](https://bugzilla.gnome.org/show_bug.cgi?id=787298)**
## Description
Patches from bug786783 rename app from "empathy" to "org.gnome.Empathy". That breaks the app tracking, so that when Empathy is running, the icon shown becomes a question mark instead of the correct icon.
Version: 3.25.xbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/904/tls/certificate_verify_success_with_full_chain test fails on x86 32bits2018-05-22T19:18:48Zbugzilla-migration/tls/certificate_verify_success_with_full_chain test fails on x86 32bits## Submitted by Laurent Bigonville `@bigon`
**[Link to original bug (#787117)](https://bugzilla.gnome.org/show_bug.cgi?id=787117)**
## Description
Hi,
In debian I enabled the checks at build time and /tls/certificate_verify_success_with_full_chain is failing on 32bits and/or bigendian architectures
https://buildd.debian.org/status/package.php?p=empathy&suite=unstable
Valgrind shows:
/tls/certificate_verify_success_with_full_chain: ==12616== Invalid read of size 4
==12616== at 0x57AE167: g_array_ref (garray.c:259)
==12616== by 0x57AF7A7: g_byte_array_ref (garray.c:1762)
==12616== by 0x573F94A: boxed_proxy_collect_value (gboxed.c:240)
==12616== by 0x574A0AA: g_object_new_valist (gobject.c:2090)
==12616== by 0x55A9608: g_initable_new_valist (ginitable.c:244)
==12616== by 0x55A966B: g_initable_new (ginitable.c:162)
==12616== by 0x4961A3B: tls_certificate_new_from_der (empathy-tls-verifier.c:80)
==12616== by 0x4961A3B: is_certificate_pinned_cb (empathy-tls-verifier.c:288)
==12616== by 0x55C366F: g_simple_async_result_complete (gsimpleasyncresult.c:801)
==12616== by 0x55C3727: complete_in_idle_cb_for_thread (gsimpleasyncresult.c:872)
==12616== by 0x57DCA83: g_main_dispatch (gmain.c:3148)
==12616== by 0x57DCA83: g_main_context_dispatch (gmain.c:3813)
==12616== by 0x57DCE98: g_main_context_iterate.isra.30 (gmain.c:3886)
==12616== by 0x57DD248: g_main_loop_run (gmain.c:4082)
==12616== by 0x10C6F5: test_certificate_verify_success_with_full_chain (empathy-tls-test.c:508)
==12616== by 0x5803D3E: test_case_run (gtestutils.c:2163)
==12616== by 0x5803D3E: g_test_run_suite_internal (gtestutils.c:2247)
==12616== by 0x5803C6A: g_test_run_suite_internal (gtestutils.c:2259)
==12616== by 0x5803F08: g_test_run_suite (gtestutils.c:2332)
==12616== by 0x5803F6C: g_test_run (gtestutils.c:1600)
==12616== by 0x10B88B: main (empathy-tls-test.c:768)
==12616== Address 0xee14564 is 0 bytes after a block of size 20 alloc'd
==12616== at 0x482E2BC: malloc (vg_replace_malloc.c:299)
==12616== by 0x57E1F88: g_malloc (gmem.c:94)
==12616== by 0x57FA159: g_slice_alloc (gslice.c:1025)
==12616== by 0x57B63F1: g_bytes_new_with_free_func (gbytes.c:184)
==12616== by 0x57B6443: g_bytes_new_take (gbytes.c:126)
==12616== by 0x57B64B2: g_bytes_new (gbytes.c:96)
==12616== by 0x4B379B4: tls_certificate_got_all_cb (tls-certificate.c:274)
==12616== by 0x4B24952: _tp_cli_properties_interface_invoke_callback_list_properties (tp-cli-generic-body.h:1852)
==12616== by 0x4B2A35F: tp_proxy_pending_call_idle_invoke (proxy-methods.c:156)
==12616== by 0x57DCA83: g_main_dispatch (gmain.c:3148)
==12616== by 0x57DCA83: g_main_context_dispatch (gmain.c:3813)
==12616== by 0x57DCE98: g_main_context_iterate.isra.30 (gmain.c:3886)
==12616== by 0x57DD248: g_main_loop_run (gmain.c:4082)
==12616== by 0x10BC71: ensure_certificate_proxy (empathy-tls-test.c:405)
==12616== by 0x10C6BE: test_certificate_verify_success_with_full_chain (empathy-tls-test.c:502)
==12616== by 0x5803D3E: test_case_run (gtestutils.c:2163)
==12616== by 0x5803D3E: g_test_run_suite_internal (gtestutils.c:2247)
==12616== by 0x5803C6A: g_test_run_suite_internal (gtestutils.c:2259)
==12616== by 0x5803F08: g_test_run_suite (gtestutils.c:2332)
==12616== by 0x5803F6C: g_test_run (gtestutils.c:1600)
==12616== by 0x10B88B: main (empathy-tls-test.c:768)
Version: 3.25.xbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/903Port to meson build system2018-05-22T19:18:30Zbugzilla-migrationPort to meson build system## Submitted by Iñigo Martínez `@inigomartinez`
**[Link to original bug (#786969)](https://bugzilla.gnome.org/show_bug.cgi?id=786969)**
## Description
Created attachment 358669
Port to meson build system
Port to meson build system of telepathy-account-widgets package.
Although libraries are created properly, I have found several files pointing to files and locations that don't exist anymore.
Coding style checks are also disabled because meson executes the scripts from unspecified location but check-c-style is expecting check-misc.sh to be located in the same directory and check-misc.sh is also expecting check-whitespace.sh to be located in the same directory. I don't know if this scripts are actually needed but they can be fixed to work with both build systems if needed.
~~**Patch 358669**~~, "Port to meson build system":
[0001-build-Port-to-meson-build-system.patch](/uploads/c4c9dc107061ec1b91576baf092d1049/0001-build-Port-to-meson-build-system.patch)5. Tp-Awbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/902Add flatpak build configuration for Empathy2018-12-06T00:18:46Zbugzilla-migrationAdd flatpak build configuration for Empathy## Submitted by Diane Trout `@detrout`
**[Link to original bug (#786783)](https://bugzilla.gnome.org/show_bug.cgi?id=786783)**
## Description
To help with testing, building, and to isolate a process that receives data over the network it'd be nice to have a flatpak build for Empathy.
This came up in bug #749001
There was some concern how telepathy would work over dbus between the host OS and the containerized application.
But it was pointed out that Polari has a flatpak build as "prior art".
So I started. It turns out Polari is actually building and shipping telepathy components. (Telepathy-logger, telepathy-mission-control, telepathy-glib, telepathy-idle)
I copied what they did and and added telepathy-gabble and its dependencies.
I'm still working my way through Empathy's additional dependencies.bugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/901Jabber unaccpeted spam contact pops up again and again2018-05-22T19:16:12Zbugzilla-migrationJabber unaccpeted spam contact pops up again and again## Submitted by Vít Ondruch
**[Link to original bug (#786548)](https://bugzilla.gnome.org/show_bug.cgi?id=786548)**
## Description
Created attachment 358027
Pop-up window
Glad to see some development in Empathy. However, with the recent UI change, I am constantly bombarded by popup (see attachmet) of some spam contacts, which I don't want to accept. I decline the contact, but it pops up again. This makes empathy unusable :/
$ rpm -q empathy
empathy-3.25.90-1.fc28.x86_64
**Attachment 358027**, "Pop-up window":
![Snímek_z_2017-08-20_21-08-28](/uploads/a1d9bc05d69cf3b670658f6c5d820914/Snímek_z_2017-08-20_21-08-28.png)5. Contact Listbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/900Name of groups in contact list that contains an ampersand (&quot;&amp;&quot;) are not displ...2018-05-22T19:15:59Zbugzilla-migrationName of groups in contact list that contains an ampersand ("&") are not displayed correctly.## Submitted by Benjamin P. Jung
**[Link to original bug (#786453)](https://bugzilla.gnome.org/show_bug.cgi?id=786453)**
## Description
Created attachment 357865
The name of the group "Commercial & Project Management" is not displayed correctly
Situation:
- Jabber/XMPP Account with server-side contact-groups and contacts
- One of the contact groups contains an ampersand
Issue:
Usually, contact group texts are rendered using a bold font in the contact list. The entry that contains the ampersand, however shows the markup and is not formatted using a bold font.
Assumption:
Contact group names in the contact listshould be escaped if they contain "&", "`<" or ">`".
Links:
- https://www.w3.org/International/questions/qa-escapes#use
**Attachment 357865**, "The name of the group "Commercial & Project Management" is not displayed correctly":
![empathy-contact-list-issue](/uploads/be6e2b8cefbcebd75297ae25b16d9cbd/empathy-contact-list-issue.png)
Version: 3.12.x5. Contact Listbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/899Empathy and Gnome session freezes when receiving a private message with a cer...2018-05-22T19:15:46Zbugzilla-migrationEmpathy and Gnome session freezes when receiving a private message with a certain format## Submitted by Enrique García
**[Link to original bug (#785310)](https://bugzilla.gnome.org/show_bug.cgi?id=785310)**
## Description
Empathy freezes as well as the Gnome session when receiving a private message like the following one:
https://a.bitexodus.com/render/?width=1509&height=814&target=a(action.ep.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%2C5)
I have reproduced this using openSUSE Tumbleweed and Fedora 26, as well using the Empathy code from git://git.gnome.org/empathy for IRC, Google Talk and Jabber.
Steps to reproduce:
1. Open Empathy and connect to an IRC server, Google Talk or Jabber account on a computer A.
2. Repeat step 1 in a computer B.
3. From computer B send a private message to computer A with this content: https://a.bitexodus.com/render/?width=1509&height=814&target=a(action.ep.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%2C5)
As a result, computer A doesn't show the message and becomes unresponsive. The process "gnome-shell" shows high CPU load.
Version: 3.12.x5. Chatbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/898Remove leftovers of the connectivity checks libraries2018-05-22T19:15:30Zbugzilla-migrationRemove leftovers of the connectivity checks libraries## Submitted by Laurent Bigonville `@bigon`
**[Link to original bug (#784464)](https://bugzilla.gnome.org/show_bug.cgi?id=784464)**
## Description
Remove leftovers of the connectivity checks libraries
Since ee4b8cc8d7db207588b33d1762d7e205f7820ca5, empathy relies on MC to
query the connectivity status.
Remove some leftover in the build system
Version: 3.12.xbugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/897[PATCH] Don&#39;t allow to detach chat tab2018-05-22T19:15:20Zbugzilla-migration[PATCH] Don't allow to detach chat tab## Submitted by Balló György
**[Link to original bug (#784455)](https://bugzilla.gnome.org/show_bug.cgi?id=784455)**
## Description
Created attachment 354802
Don't allow to detach chat tab
Detaching a tab causes undesired behaviour and crash with the new UI.
**Patch 354802**, "Don't allow to detach chat tab":
[0001-Don-t-allow-to-detach-chat-tab.patch](/uploads/7bd8bbdbca0fd6193c65287c8b1c45d8/0001-Don-t-allow-to-detach-chat-tab.patch)bugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/896wayland: keyboard shortcut to switch from one conversion to another2018-05-22T19:15:07Zbugzilla-migrationwayland: keyboard shortcut to switch from one conversion to another## Submitted by Maxime de Roucy `@maxime.deroucy`
**[Link to original bug (#782448)](https://bugzilla.gnome.org/show_bug.cgi?id=782448)**
## Description
Hello,
Under empathy 3.12.12+120+g4a4b45b94-1 I can't switch from one conversation to another using Ctrl+PageUp, Ctrl+PageDown.
This bug appear with the change of UI (I think commit : cb3852df479c2edefedbc6d8e3ef9862e1aa4f12 ).
configuration:
* wayland
* Archlinux
Do you need other information ?
Regards
Version: 3.12.x8. Accessibilitybugzillahttps://gitlab.gnome.org/GNOME/empathy/issues/895Start chats in new windows setting is not honoured2018-05-22T19:14:56Zbugzilla-migrationStart chats in new windows setting is not honoured## Submitted by Peter Y. Chuang `@peterychuang`
**[Link to original bug (#781705)](https://bugzilla.gnome.org/show_bug.cgi?id=781705)**
## Description
New chat fails to start in a new window when set specifically so in Preference or dconf.
Built from latest commit of master branch.
Version: 3.12.x5. Chatbugzilla