[Desktop-packages] [Bug 621048] Re: mission-control-5 crashed with SIGSEGV in __libc_start_main()
The only case where this could happen is if MC failed to connect to D-Bus for some reason. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/621048 Title: mission-control-5 crashed with SIGSEGV in __libc_start_main() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: Binary package hint: telepathy-mission-control-5 1. lsb_release -rd Description: Ubuntu maverick (development branch) Release: 10.10 2. apt-cache policy telepathy-mission-control-5 telepathy-mission-control-5: Installed: 1:5.5.3-1 Candidate: 1:5.5.3-1 Version table: *** 1:5.5.3-1 0 500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: telepathy-mission-control-5 1:5.5.3-1 ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2 Uname: Linux 2.6.35-16-generic x86_64 Architecture: amd64 Date: Fri Aug 20 14:19:14 2010 ExecutablePath: /usr/lib/telepathy/mission-control-5 ProcCmdline: /usr/lib/telepathy/mission-control-5 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.utf8 SegvAnalysis: Segfault happened at: 0x40eb70: mov0x18(%rdi),%rdi PC (0x0040eb70) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: ?? () ?? () __libc_start_main () from /lib/libc.so.6 ?? () ?? () Title: mission-control-5 crashed with SIGSEGV in __libc_start_main() UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse pulse-access sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/621048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 621048] Re: mission-control-5 crashed with SIGSEGV in __libc_start_main()
This patch should handle this scenario more gracefully http://cgit.freedesktop.org/telepathy/telepathy-mission- control/commit/?h=telepathy-mission- control-5.16id=3d3a13c561e858853af5c601373be3ea0746f58c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/621048 Title: mission-control-5 crashed with SIGSEGV in __libc_start_main() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: Binary package hint: telepathy-mission-control-5 1. lsb_release -rd Description: Ubuntu maverick (development branch) Release: 10.10 2. apt-cache policy telepathy-mission-control-5 telepathy-mission-control-5: Installed: 1:5.5.3-1 Candidate: 1:5.5.3-1 Version table: *** 1:5.5.3-1 0 500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: telepathy-mission-control-5 1:5.5.3-1 ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2 Uname: Linux 2.6.35-16-generic x86_64 Architecture: amd64 Date: Fri Aug 20 14:19:14 2010 ExecutablePath: /usr/lib/telepathy/mission-control-5 ProcCmdline: /usr/lib/telepathy/mission-control-5 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.utf8 SegvAnalysis: Segfault happened at: 0x40eb70: mov0x18(%rdi),%rdi PC (0x0040eb70) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: ?? () ?? () __libc_start_main () from /lib/libc.so.6 ?? () ?? () Title: mission-control-5 crashed with SIGSEGV in __libc_start_main() UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse pulse-access sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/621048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 296867]
(In reply to comment #81) I've made most of the changes I wanted but haven't had time to test them yet. Use at own risk: http://cgit.freedesktop.org/~smcv/telepathy-gabble/log/?h=untested-otr I did not manage to start an OTR session with this branch. The '/otr start' command was displaying OTR:$blob in empathy-chat. I did manage to start a session using Xavier's branch but noticed the following bug: - Start an OTR session between Empathy and Pidgin - In Pidgin using the OTR menu pick End private conversation - Try sending a message from Empathy. The message doesn't reach Pidgin and this error is displayed: Your message was not sent because cassidy-te...@jabber.belnet.be closed their connection. Either close your private connection, or refresh it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption Status in Chat app, and Telepathy user interface: Confirmed Status in One Hundred Papercuts: Invalid Status in Telepathy framework - library: Confirmed Status in “empathy” package in Ubuntu: Triaged Status in “libtelepathy” package in Ubuntu: Confirmed Status in “empathy” package in Fedora: Won't Fix Bug description: Binary package hint: empathy Hello, I just tried empathy (the Intrepid version) and it looked very solid and stable. There were a few minor things that could be improved (e.g. automatically resizing the contact list), but that is not the topic here. The reason why I won't switch to empathy from pidgin is the missing OTR support (http://www.cypherpunks.ca/otr/ ). This is a really important feature because no one should read your messages. There were others with the same idea (links at the bottom). Would be so great if it could support that important encryption standard. Thanks for helping out! Links: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2 http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html http://bugs.freedesktop.org/show_bug.cgi?id=16891 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 296867]
(In reply to comment #54) trust_level_to_str(): I'd mention encrypt using OTR to be clearer and avoid confusion my server encryption. Fixed. return _(The conversation is currently unencrypted.); I'd say unencrypted with OTR to stay coherent and crystal clear. Your branch looks good to me. I'm fine merging it to Empathy master as soon as the Gabble branch lands. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption Status in Chat app, and Telepathy user interface: Confirmed Status in One Hundred Papercuts: Invalid Status in Telepathy framework - library: Confirmed Status in “empathy” package in Ubuntu: Triaged Status in “libtelepathy” package in Ubuntu: Confirmed Status in “empathy” package in Fedora: Won't Fix Bug description: Binary package hint: empathy Hello, I just tried empathy (the Intrepid version) and it looked very solid and stable. There were a few minor things that could be improved (e.g. automatically resizing the contact list), but that is not the topic here. The reason why I won't switch to empathy from pidgin is the missing OTR support (http://www.cypherpunks.ca/otr/ ). This is a really important feature because no one should read your messages. There were others with the same idea (links at the bottom). Would be so great if it could support that important encryption standard. Thanks for helping out! Links: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2 http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html http://bugs.freedesktop.org/show_bug.cgi?id=16891 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 296867]
From a (very) quick look on the Gabble branch, it seems that all the channel messages are now sent through OTR (if built with it), even when it has not been activated. Is that really what we want? Also, shouldn't we use it only for contact channels? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption Status in Chat app, and Telepathy user interface: Confirmed Status in One Hundred Papercuts: Invalid Status in Telepathy framework - library: Confirmed Status in “empathy” package in Ubuntu: Triaged Status in “libtelepathy” package in Ubuntu: Confirmed Status in “empathy” package in Fedora: Won't Fix Bug description: Binary package hint: empathy Hello, I just tried empathy (the Intrepid version) and it looked very solid and stable. There were a few minor things that could be improved (e.g. automatically resizing the contact list), but that is not the topic here. The reason why I won't switch to empathy from pidgin is the missing OTR support (http://www.cypherpunks.ca/otr/ ). This is a really important feature because no one should read your messages. There were others with the same idea (links at the bottom). Would be so great if it could support that important encryption standard. Thanks for helping out! Links: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2 http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html http://bugs.freedesktop.org/show_bug.cgi?id=16891 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 296867]
(In reply to comment #46) Empathy: http://cgit.collabora.com/git/user/xclaesse/empathy.git/log/?h=otr Ok for the first commit. Second commit: + tuple = empathy_gdbus_channel_interface_otr1_get_remote_fingerprint ( + priv-otr_proxy); I have no idea how these new generated API work, but GVariant API are usually 'return: (transfer full)' that's not the case here? + level = empathy_gdbus_channel_interface_otr1_get_trust_level ( + priv-otr_proxy); I guess this returns a cached value (not a blocking call) right? What happens if the proxy is not ready yet? Aren't we going to treat it as a wrong level and update it right after? + g_variant_get (tuple, (s@ay), fp, NULL); What's the 'ay' arg being ignored? Please add at least one comment. What happens if the user doesn't trust the fingerprint. The communication is still crypted? +N_(/otr action: Interact with the Off-The-Record system. Possible actions are:\n Is there a way to check (without changing) the current trust level? + g_variant_get (tuple, (s@ay), NULL, fp_variant); + empathy_gdbus_channel_interface_otr1_call_initialize ( + priv-otr_proxy, NULL, NULL, NULL); How does the user know if the operation succeeded or not? Just wait for the level update message? I think we should explicitely say if it failed so user explicitely know the conversation is not safe. + g_variant_get (tuple, (s@ay), NULL, fp_variant); I think fp_variant is leaked. chat_command_otr() will crash/assert if one of the D-Bus API failed. Also, shouldn't we use async API here? trust_level_to_str(): I'd mention encrypt using OTR to be clearer and avoid confusion my server encryption. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption Status in Chat app, and Telepathy user interface: Confirmed Status in One Hundred Papercuts: Invalid Status in Telepathy framework - library: Confirmed Status in “empathy” package in Ubuntu: Triaged Status in “libtelepathy” package in Ubuntu: Confirmed Status in “empathy” package in Fedora: Won't Fix Bug description: Binary package hint: empathy Hello, I just tried empathy (the Intrepid version) and it looked very solid and stable. There were a few minor things that could be improved (e.g. automatically resizing the contact list), but that is not the topic here. The reason why I won't switch to empathy from pidgin is the missing OTR support (http://www.cypherpunks.ca/otr/ ). This is a really important feature because no one should read your messages. There were others with the same idea (links at the bottom). Would be so great if it could support that important encryption standard. Thanks for helping out! Links: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2 http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html http://bugs.freedesktop.org/show_bug.cgi?id=16891 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237191]
Created attachment 98618 wocky-jingle-info: don't try using self if it's NULL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1237191 Title: telepathy-gabble crashed with SIGSEGV in stun_server_resolved_cb() Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: During boot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: telepathy-gabble 0.18.1-1 Uname: Linux 3.9.0-030900-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 8 20:43:37 2013 ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationDate: Installed on 2011-08-31 (769 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True ProcCmdline: /usr/lib/telepathy/telepathy-gabble SegvAnalysis: Segfault happened at: 0x7f25ca249dbf:mov0x18(%r12),%r15 PC (0x7f25ca249dbf) ok source 0x18(%r12) (0x0018) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-gabble StacktraceTop: ?? () from /usr/lib/telepathy/gabble-0/lib/libwocky-telepathy-gabble-0.18.1.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: telepathy-gabble crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to saucy on 2013-10-08 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1237191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237191]
(In reply to comment #2) Fixed for 0.18.2 and 0.19.0 (which may actually be 1.0). And I just released 0.18.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1237191 Title: telepathy-gabble crashed with SIGSEGV in stun_server_resolved_cb() Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: During boot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: telepathy-gabble 0.18.1-1 Uname: Linux 3.9.0-030900-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 8 20:43:37 2013 ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationDate: Installed on 2011-08-31 (769 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True ProcCmdline: /usr/lib/telepathy/telepathy-gabble SegvAnalysis: Segfault happened at: 0x7f25ca249dbf:mov0x18(%r12),%r15 PC (0x7f25ca249dbf) ok source 0x18(%r12) (0x0018) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-gabble StacktraceTop: ?? () from /usr/lib/telepathy/gabble-0/lib/libwocky-telepathy-gabble-0.18.1.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: telepathy-gabble crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to saucy on 2013-10-08 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1237191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237191]
Fixed for 0.18.2 and 0.19.0 (which may actually be 1.0). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1237191 Title: telepathy-gabble crashed with SIGSEGV in stun_server_resolved_cb() Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: During boot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: telepathy-gabble 0.18.1-1 Uname: Linux 3.9.0-030900-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 8 20:43:37 2013 ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationDate: Installed on 2011-08-31 (769 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True ProcCmdline: /usr/lib/telepathy/telepathy-gabble SegvAnalysis: Segfault happened at: 0x7f25ca249dbf:mov0x18(%r12),%r15 PC (0x7f25ca249dbf) ok source 0x18(%r12) (0x0018) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-gabble StacktraceTop: ?? () from /usr/lib/telepathy/gabble-0/lib/libwocky-telepathy-gabble-0.18.1.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: telepathy-gabble crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to saucy on 2013-10-08 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1237191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 296867]
For the record, here is a thread summarising the design issues regarding end-to-end security in Telepathy: http://lists.freedesktop.org/archives/telepathy/2012-June/006122.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption Status in Chat app, and Telepathy user interface: Confirmed Status in One Hundred Paper Cuts: Invalid Status in Telepathy framework - library: Confirmed Status in “empathy” package in Ubuntu: Triaged Status in “libtelepathy” package in Ubuntu: Confirmed Status in “empathy” package in Fedora: Won't Fix Bug description: Binary package hint: empathy Hello, I just tried empathy (the Intrepid version) and it looked very solid and stable. There were a few minor things that could be improved (e.g. automatically resizing the contact list), but that is not the topic here. The reason why I won't switch to empathy from pidgin is the missing OTR support (http://www.cypherpunks.ca/otr/ ). This is a really important feature because no one should read your messages. There were others with the same idea (links at the bottom). Would be so great if it could support that important encryption standard. Thanks for helping out! Links: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/253452/comments/2 http://lists.cypherpunks.ca/pipermail/otr-users/2008-September/001479.html http://bugs.freedesktop.org/show_bug.cgi?id=16891 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915047]
This bug is in the top 5 of the most common empathy crash on Ubuntu ( https://errors.ubuntu.com/?package=empathy ) so I think we may have to re-open. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/915047 Title: empathy-chat crashed with SIGSEGV in _tpl_event_queue_insert_sorted_after() Status in Chat app, and Telepathy user interface: Invalid Status in “empathy” package in Ubuntu: Invalid Bug description: Work with empathy, account Gtalk, MSN, chat, Facebook and salut... ON. Click in user gtalk and crash. Duplicated bug #807566 (?) ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 Uname: Linux 3.1.8-030108-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Jan 11 18:28:36 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1) ProcCmdline: /usr/lib/empathy/empathy-chat SegvAnalysis: Segfault happened at: 0x7f867b532d6e _tpl_event_queue_insert_sorted_after+78: mov(%rdx),%rdi PC (0x7f867b532d6e) ok source (%rdx) (0x39373a746168632d) not located in a known VMA region (needed readable region)! destination %rdi ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: _tpl_event_queue_insert_sorted_after (events=0x7f865de0dad0, index=0x7f8664026700, event=0x154cf20) at util.c:128 _tpl_log_manager_get_filtered_events (manager=optimized out, account=0x1528630, target=0x14d6300, type_mask=1, num_events=5, filter=0x43ebb0 chat_log_filter, user_data=0x1570080) at log-manager.c:592 _get_filtered_events_async_thread (simple=0x1cc2700, object=optimized out, cancellable=optimized out) at log-manager.c:1086 run_in_thread (job=optimized out, c=0x0, _data=0x15b7190) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:843 io_job_thread (data=0x1de3080, user_data=optimized out) at /build/buildd/glib2.0-2.30.0/./gio/gioscheduler.c:180 Title: empathy-chat crashed with SIGSEGV in _tpl_event_queue_insert_sorted_after() UpgradeStatus: Upgraded to oneiric on 2011-10-04 (99 days ago) UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/915047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1064786] Re: empathy-auth-client SIGABRT in tls_certificate_got_all_cb(): cert_data != NULL
Forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=61616 ** Bug watch added: freedesktop.org Bugzilla #61616 https://bugs.freedesktop.org/show_bug.cgi?id=61616 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1064786 Title: empathy-auth-client SIGABRT in tls_certificate_got_all_cb(): cert_data != NULL Status in “empathy” package in Ubuntu: Confirmed Bug description: updated system, restarted, started empathy, client crashed ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 Date: Wed Oct 10 02:20:32 2012 ExecutablePath: /usr/lib/empathy/empathy-auth-client InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120909) ProcCmdline: /usr/lib/empathy/empathy-auth-client ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Signal: 6 SourcePackage: empathy StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0 Title: empathy-auth-client crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: vboxusers XsessionErrors: (indicator-multiload:2345): GLib-GIO-CRITICAL **: GApplication subclass 'Main' failed to chain up on ::startup (from start of override function) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1064786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 959084] Re: empathy-chat consistently uses 9-10 % CPU
I did some testing and this bug only appears when using Ubuntu's adium theme so it's either a theme bug (like some js infinite loop or something) or a webkit-gtk one. I can reproduce this bug on F17 as well. I won't have time to investigate this issue further but the next step could do to try some profiling using Webkit's inspector tool: - gsettings set org.gnome.Empathy.conversation enable-webkit-developer-tools true - Open a chat with the adium theme - Right click and select 'Inspect Element' It would be cool if some webkit(-gtk) could take a look on this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/959084 Title: empathy-chat consistently uses 9-10 % CPU Status in Ubuntu Adium Theme: New Status in Chat app, and Telepathy user interface: Unknown Status in “adium-theme-ubuntu” package in Ubuntu: Triaged Status in “empathy” package in Ubuntu: Triaged Bug description: This may have started since I upgraded my system to 12.04, it was certainly a recent development at around that time. I am using empathy for IRC only, connected to four channels on two servers, though even disabling all accounts does not change this. The empathy- chat process is very consistently at 9% CPU, with spikes at 10% or higher from time to time. I have tested this on mobile broadband, wifi and ethernet. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 09:28:49 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/959084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 959084] Re: empathy-chat consistently uses 9-10 % CPU
I don't think we use to have this bug with the previous ubuntu version. So another useful thing to do would be to bisect through the theme history and find which commit introduced this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/959084 Title: empathy-chat consistently uses 9-10 % CPU Status in Ubuntu Adium Theme: New Status in Chat app, and Telepathy user interface: Unknown Status in “adium-theme-ubuntu” package in Ubuntu: Triaged Status in “empathy” package in Ubuntu: Triaged Bug description: This may have started since I upgraded my system to 12.04, it was certainly a recent development at around that time. I am using empathy for IRC only, connected to four channels on two servers, though even disabling all accounts does not change this. The empathy- chat process is very consistently at 9% CPU, with spikes at 10% or higher from time to time. I have tested this on mobile broadband, wifi and ethernet. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 09:28:49 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/959084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1044057] Re: empathy no longer allows for extended jabber configuration
The import code isn't run in this log. Are you sure you reset the sanity-cleaning-number gsetting key before ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1044057 Title: empathy no longer allows for extended jabber configuration Status in “empathy” package in Ubuntu: Confirmed Status in “empathy” source package in Quantal: Confirmed Bug description: I have been using Empathy for a longtime, primarily for Jabber to a private network. Recent updates in 12.10 imported my previous settings ok, but I am no longer able to edit those settings because when I click Empathy/Accounts from the global menu, I get the Online Accounts setup, and it doesn't seem to know about my previous setup. Furthermore, if I try to add a jabber account, the account setup is far too limited with only a jabber id and password presented, which prevents me from using empathy with the aforementioned private network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1022685] Re: empathy crashed with SIGSEGV in ffi_call_SYSV()
*** This bug is a duplicate of bug 1037810 *** https://bugs.launchpad.net/bugs/1037810 ** This bug has been marked a duplicate of bug 1037810 empathy crashed with SIGSEGV in ffi_call_SYSV() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1022685 Title: empathy crashed with SIGSEGV in ffi_call_SYSV() Status in “empathy” package in Ubuntu: Incomplete Bug description: was just looking trough the menus when it chrased. becouse it did not show msn contacts but was logged in , it did show google talk contacts ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: empathy 3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic i686 ApportVersion: 2.3-0ubuntu1 Architecture: i386 Date: Mon Jul 9 20:29:42 2012 Disassembly: = 0x: Cannot access memory at address 0x ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120627) ProcCmdline: empathy SegvAnalysis: Segfault happened at: 0x:Cannot access memory at address 0x PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: empathy crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1022685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1037810] Re: empathy crashed with SIGSEGV in ffi_call_SYSV()
Fixed in Empathy 3.6.0.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1037810 Title: empathy crashed with SIGSEGV in ffi_call_SYSV() Status in “empathy” package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 apt-cache policy empathy empathy: Installed: 3.5.5-0ubuntu1 Candidate: 3.5.5-0ubuntu1 Version table: *** 3.5.5-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status When responding to a message from a GMail account, the winow crashed and this error was reported. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: empathy 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic i686 NonfreeKernelModules: wl ApportVersion: 2.4-0ubuntu8 Architecture: i386 Date: Thu Aug 16 17:45:30 2012 Disassembly: = 0xb232d020: Cannot access memory at address 0xb232d020 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: empathy ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb232d020:Cannot access memory at address 0xb232d020 PC (0xb232d020) in non-executable VMA region: 0xb232d000-0xb2332000 r--p /home/j/.config/dconf/user SegvReason: executing non-writable VMA /home/j/.config/dconf/user Signal: 11 SourcePackage: empathy StacktraceTop: ?? () ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: empathy crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: Upgraded to quantal on 2012-08-16 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1037810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1020317] Re: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close()
This crash is fixed in telepathy-gabble 0.16.2 (but best to update to 0.16.3). See https://bugs.freedesktop.org/show_bug.cgi?id=53087 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1020317 Title: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: telepathy-gabble 0.16.1-1 ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4 Uname: Linux 3.5.0-2-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.2.5-0ubuntu1 Architecture: amd64 Date: Mon Jul 2 18:34:11 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) ProcCmdline: /usr/lib/telepathy/telepathy-gabble SegvAnalysis: Segfault happened at: 0x7fecd91dfa2e tp_base_channel_close+14: mov (%rdi),%rbp PC (0x7fecd91dfa2e) ok source (%rdi) (0x742f656c62626167) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: telepathy-gabble StacktraceTop: tp_base_channel_close () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0 ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1020317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1052375] Re: The online account g-c-c interface doesn't support i18n
Upstream Empathy bug report: https://bugzilla.gnome.org/show_bug.cgi?id=684281 ** Bug watch added: GNOME Bug Tracker #684281 https://bugzilla.gnome.org/show_bug.cgi?id=684281 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1052375 Title: The online account g-c-c interface doesn't support i18n Status in Chat app, and Telepathy user interface: New Status in Gwibber: New Status in Online Accounts: GNOME Control Center: In Progress Status in Shotwell: New Status in Ubuntu Translations: Triaged Status in Google Documents Lens: New Status in Photos Lens: New Status in “empathy” package in Ubuntu: Confirmed Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Status in “gwibber” package in Ubuntu: Confirmed Status in “shotwell” package in Ubuntu: Confirmed Status in “unity-lens-photos” package in Ubuntu: Confirmed Status in “unity-scope-gdocs” package in Ubuntu: Confirmed Status in “empathy” source package in Quantal: Confirmed Status in “gnome-control-center-signon” source package in Quantal: Confirmed Status in “gwibber” source package in Quantal: Confirmed Status in “shotwell” source package in Quantal: Confirmed Status in “unity-lens-photos” source package in Quantal: Confirmed Status in “unity-scope-gdocs” source package in Quantal: Confirmed Bug description: The online accounts UI loads the plugins integration from some .application files. Those are not translated, not translatable. What needs to be done, is: - rename the .application in .application.in - ensuring that upstream have an application.in files with translatable tags (using _, as in _descriptionI want to be translated/_description). Example [1] - add a translations tag containing the upstream domain - then, at build time: 1. Running intltool-extract files.applications.in so that it gets merged into a files.applications.in.h file. If you are using intltool already in your build system (and you probably are), this should be happening already and you can skip to step 2. 2. Including the .in file somewhere in the build system (like po/POTFILES.in for Python apps and Makefiles.am for C/vala apps) so that it's merged into the .pot file. In Python, it's just a matter of adding it as an extra line to the po/POTFILES.in file (example [2]): [gettext/xml]data/gwibber.application.in 3. And running intltool-merge --no-translations -x -u foo.applications.in foo.application to create the xml upstream file which is shipped - online-account (the g-c-c plugin) should be patched to load them, looking at the translations tag and gettext (package, string) [1] http://bazaar.launchpad.net/~dpm/+junk/testintl/view/head:/data/gwibber.application.in [2] http://bazaar.launchpad.net/~dpm/+junk/testintl/view/head:/po/POTFILES.in To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1052375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1049504] Re: mission-control-5 crashed with SIGSEGV in g_str_hash()
Fixed with http://git.gnome.org/browse/empathy/commit/?id=5676e2a343460465e4439449e4d6d834f21ccdbd ** Package changed: telepathy-mission-control-5 (Ubuntu) = empathy (Ubuntu) ** Changed in: empathy (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1049504 Title: mission-control-5 crashed with SIGSEGV in g_str_hash() Status in “empathy” package in Ubuntu: Fix Committed Bug description: I was testing shotwell with UOA; I killed the signon-ui process (which is the one providing the com.canonical.indicators.webcredentials service) and a couple of seconds later apport notified me that MC5 had crashed (I wasn't actively using empathy). ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: telepathy-mission-control-5 1:5.13.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Wed Sep 12 10:19:39 2012 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=e6a73b41-3db6-4165-ab61-812600c6adda ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f1168f16360 g_str_hash: movsbl (%rdi),%edx PC (0x7f1168f16360) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_str_hash (v=0x0) at /build/buildd/glib2.0-2.33.12/./glib/ghash.c:1730 g_hash_table_lookup_node (hash_return=synthetic pointer, key=0x0, hash_table=0x1e000c0) at /build/buildd/glib2.0-2.33.12/./glib/ghash.c:401 g_hash_table_lookup (hash_table=0x1e000c0, key=key@entry=0x0) at /build/buildd/glib2.0-2.33.12/./glib/ghash.c:1074 mcd_account_manager_lookup_account (account_manager=optimized out, name=name@entry=0x0) at mcd-account-manager.c:1772 reconnect_cb (plugin=optimized out, name=0x0, data=0x1dcfa30) at mcd-account-manager.c:420 Title: mission-control-5 crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1049504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1044057] Re: empathy no longer allows for extended jabber configuration
The import code has been improved in 3.5.91.1 I'd be interested to see the logs when trying to re-import using this version. Could you please once 3.5.91.1 has reached Ubuntu: - Make sure any Empathy account is configured and not empathy process is running (especially empathy-auth-client) - gsettings set org.gnome.Empathy sanity-cleaning-number 0 - EMPATHY_PERSIST=1 EMPATHY_DEBUG=all G_MESSAGES_DEBUG=all EMPATHY_LOGFILE=/tmp/auth.log /usr/lib/empathy/empathy-auth-client - Attach /tmp/auth.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1044057 Title: empathy no longer allows for extended jabber configuration Status in “empathy” package in Ubuntu: Confirmed Status in “empathy” source package in Quantal: Confirmed Bug description: I have been using Empathy for a longtime, primarily for Jabber to a private network. Recent updates in 12.10 imported my previous settings ok, but I am no longer able to edit those settings because when I click Empathy/Accounts from the global menu, I get the Online Accounts setup, and it doesn't seem to know about my previous setup. Furthermore, if I try to add a jabber account, the account setup is far too limited with only a jabber id and password presented, which prevents me from using empathy with the aforementioned private network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1044057] Re: empathy no longer allows for extended jabber configuration
Actually, you can create your account using the 'simple' account widget and then change its advanced settings later. The real bug here is that your account has been migrated to Ubuntu Online Accounts but doesn't appear in the UOA panel. Which Empathy version are you using? Could you please post the output of 'mc-tool dump' ? (mission-control 5.13.1 needed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1044057 Title: empathy no longer allows for extended jabber configuration Status in “empathy” package in Ubuntu: New Status in “empathy” source package in Quantal: New Bug description: I have been using Empathy for a longtime, primarily for Jabber to a private network. Recent updates in 12.10 imported my previous settings ok, but I am no longer able to edit those settings because when I click Empathy/Accounts from the global menu, I get the Online Accounts setup, and it doesn't seem to know about my previous setup. Furthermore, if I try to add a jabber account, the account setup is far too limited with only a jabber id and password presented, which prevents me from using empathy with the aforementioned private network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 958699] Re: Empathy doesn't open chat windows
Please attach logs from empathy-debugger when you experience this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/958699 Title: Empathy doesn't open chat windows Status in “empathy” package in Ubuntu: Incomplete Bug description: Empathy does not open text chat windows when I double click on a contact's name, or when I right click on their name and select Chat. This is a major bug that hinderences usage of the program, and I believe it should be a high priority. I've been experiencing this bug for the last 5 months. It makes using Empathy completely pointless. Empathy does not show any feedback in the form of opening a chat window when I've received a message either. I believe this bug is linked with other bug reports of not being able to open the chat window using the Gnome Shell, and only being able to use the message bubbles. As others have suggested, I've checked Open new chats in separate windows and unchecked Display incoming events in the notification area and Enable bubble notifications in Empathy's preferences. I'm running Empathy 3.2.0.1 on Oneiric, gnome fallback mode. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Mar 18 12:58:35 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/958699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042170] [NEW] account-plugin-* packages should depend on the right telepathy connection manager
Public bug reported: In bug #1035265 we split UOA plugins in different packages. That's good but each package should depend on the relevant Telepathy connection manager as it's unusable without having the proper telepathy backend installed. account-plugin-aim : telepathy-haze account-plugin-gadugadu : telepathy-haze account-plugin-groupwise : telepathy-haze account-plugin-icq : telepathy-haze account-plugin-irc : telepathy-idle account-plugin-jabber : telepathy-gabble account-plugin-mxit : telepathy-haze account-plugin-myspace : telepathy-haze account-plugin-salut : telepathy-salut account-plugin-sametime : telepathy-haze account-plugin-sip : telepathy-rakia account-plugin-yahoo : telepathy-haze account-plugin-yahoojp : telepathy-haze account-plugin-zephyr : telepathy-haze ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1042170 Title: account-plugin-* packages should depend on the right telepathy connection manager Status in “empathy” package in Ubuntu: New Bug description: In bug #1035265 we split UOA plugins in different packages. That's good but each package should depend on the relevant Telepathy connection manager as it's unusable without having the proper telepathy backend installed. account-plugin-aim : telepathy-haze account-plugin-gadugadu : telepathy-haze account-plugin-groupwise : telepathy-haze account-plugin-icq : telepathy-haze account-plugin-irc : telepathy-idle account-plugin-jabber : telepathy-gabble account-plugin-mxit : telepathy-haze account-plugin-myspace : telepathy-haze account-plugin-salut : telepathy-salut account-plugin-sametime : telepathy-haze account-plugin-sip : telepathy-rakia account-plugin-yahoo : telepathy-haze account-plugin-yahoojp : telepathy-haze account-plugin-zephyr : telepathy-haze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1042170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035265] [NEW] Split packages of Empathy Ubuntu Online Accounts plugins
Public bug reported: Atm, all the Empathy UOA plugins are in the 'account-plugin-empathy' plugin. # dpkg -L account-plugin-empathy /. /usr /usr/lib /usr/lib/libaccount-plugin-1.0 /usr/lib/libaccount-plugin-1.0/providers /usr/lib/libaccount-plugin-1.0/providers/libjabber.so /usr/lib/libaccount-plugin-1.0/providers/libaim.so /usr/lib/libaccount-plugin-1.0/providers/libirc.so /usr/lib/libaccount-plugin-1.0/providers/libicq.so /usr/lib/libaccount-plugin-1.0/providers/libmxit.so /usr/lib/libaccount-plugin-1.0/providers/libzephyr.so /usr/lib/libaccount-plugin-1.0/providers/libsametime.so /usr/lib/libaccount-plugin-1.0/providers/liblocal-xmpp.so /usr/lib/libaccount-plugin-1.0/providers/libsip.so /usr/lib/libaccount-plugin-1.0/providers/libyahoo.so /usr/lib/libaccount-plugin-1.0/providers/libyahoojp.so /usr/lib/libaccount-plugin-1.0/providers/libmyspace.so /usr/lib/libaccount-plugin-1.0/providers/libgadugadu.so /usr/lib/libaccount-plugin-1.0/providers/libgroupwise.so /usr/lib/libaccount-plugin-1.0/applications /usr/lib/libaccount-plugin-1.0/applications/libempathy.so /usr/share /usr/share/accounts /usr/share/accounts/providers /usr/share/accounts/providers/zephyr.provider /usr/share/accounts/providers/mxit.provider /usr/share/accounts/providers/yahoo.provider /usr/share/accounts/providers/local-xmpp.provider /usr/share/accounts/providers/groupwise.provider /usr/share/accounts/providers/sametime.provider /usr/share/accounts/providers/myspace.provider /usr/share/accounts/providers/sip.provider /usr/share/accounts/providers/aim.provider /usr/share/accounts/providers/icq.provider /usr/share/accounts/providers/gadugadu.provider /usr/share/accounts/providers/jabber.provider /usr/share/accounts/providers/irc.provider /usr/share/accounts/providers/yahoojp.provider /usr/share/accounts/services /usr/share/accounts/services/icq-im.service /usr/share/accounts/services/jabber-im.service /usr/share/accounts/services/sip-im.service /usr/share/accounts/services/irc-im.service /usr/share/accounts/services/aim-im.service /usr/share/accounts/services/yahoo-im.service /usr/share/accounts/services/groupwise-im.service /usr/share/accounts/services/sametime-im.service /usr/share/accounts/services/gadugadu-im.service /usr/share/accounts/services/zephyr-im.service /usr/share/accounts/services/mxit-im.service /usr/share/accounts/services/yahoojp-im.service /usr/share/accounts/services/myspace-im.service /usr/share/accounts/services/local-xmpp-im.service /usr/share/accounts/applications /usr/share/accounts/applications/empathy.application /usr/share/doc /usr/share/doc/account-plugin-empathy /usr/share/doc/account-plugin-empathy/copyright /usr/share/doc/account-plugin-empathy/NEWS.gz /usr/share/doc/account-plugin-empathy/changelog.Debian.gz /usr/share/doc/account-plugin-empathy/TODO /usr/share/doc/account-plugin-empathy/README /usr/share/doc/account-plugin-empathy/changelog.gz /usr/share/doc/account-plugin-empathy/AUTHORS Ideally, each protocol should have its own package containing its plugin, provider and service files. We should also make sure that each of those package depends on the right telepathy connection manager (jabber depending on gabble, local-xmpp on salut, etc). The application plugin (/usr/lib/libaccount- plugin-1.0/applications/libempathy.so) can either be a separated package or be part of the main empathy package. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1035265 Title: Split packages of Empathy Ubuntu Online Accounts plugins Status in “empathy” package in Ubuntu: New Bug description: Atm, all the Empathy UOA plugins are in the 'account-plugin-empathy' plugin. # dpkg -L account-plugin-empathy /. /usr /usr/lib /usr/lib/libaccount-plugin-1.0 /usr/lib/libaccount-plugin-1.0/providers /usr/lib/libaccount-plugin-1.0/providers/libjabber.so /usr/lib/libaccount-plugin-1.0/providers/libaim.so /usr/lib/libaccount-plugin-1.0/providers/libirc.so /usr/lib/libaccount-plugin-1.0/providers/libicq.so /usr/lib/libaccount-plugin-1.0/providers/libmxit.so /usr/lib/libaccount-plugin-1.0/providers/libzephyr.so /usr/lib/libaccount-plugin-1.0/providers/libsametime.so /usr/lib/libaccount-plugin-1.0/providers/liblocal-xmpp.so /usr/lib/libaccount-plugin-1.0/providers/libsip.so /usr/lib/libaccount-plugin-1.0/providers/libyahoo.so /usr/lib/libaccount-plugin-1.0/providers/libyahoojp.so /usr/lib/libaccount-plugin-1.0/providers/libmyspace.so /usr/lib/libaccount-plugin-1.0/providers/libgadugadu.so /usr/lib/libaccount-plugin-1.0/providers/libgroupwise.so /usr/lib/libaccount-plugin-1.0/applications /usr/lib/libaccount-plugin-1.0/applications/libempathy.so /usr/share /usr/share/accounts /usr/share/accounts/providers /usr/share/accounts/providers/zephyr.provider
[Desktop-packages] [Bug 1020317]
Created attachment 65271 Other trace Here is another trace when Gabble crashed because of a SSO auth error (the token expired). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1020317 Title: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() Status in Jabber/XMPP connection manager: Confirmed Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: telepathy-gabble 0.16.1-1 ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4 Uname: Linux 3.5.0-2-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.2.5-0ubuntu1 Architecture: amd64 Date: Mon Jul 2 18:34:11 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) ProcCmdline: /usr/lib/telepathy/telepathy-gabble SegvAnalysis: Segfault happened at: 0x7fecd91dfa2e tp_base_channel_close+14: mov (%rdi),%rbp PC (0x7fecd91dfa2e) ok source (%rdi) (0x742f656c62626167) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: telepathy-gabble StacktraceTop: tp_base_channel_close () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0 ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: telepathy-gabble crashed with SIGSEGV in tp_base_channel_close() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1020317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026629] Re: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid()
I commented on the upstream bug ( https://bugzilla.gnome.org/show_bug.cgi?id=680303 ) would be cool if someone experiencing the crash could provide the info there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1026629 Title: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid() Status in Chat app, and Telepathy user interface: Unknown Status in “empathy” package in Ubuntu: Confirmed Bug description: When i want too launch chat ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: empathy 3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7 Uname: Linux 3.5.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 19 16:16:29 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120309) ProcCmdline: /usr/lib/empathy/empathy-chat ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x4605ca empathy_adium_path_is_valid+26: cmpb $0x2f,(%rdi) PC (0x004605ca) ok source $0x2f ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: empathy StacktraceTop: empathy_adium_path_is_valid () empathy_adium_info_new () empathy_adium_data_new () ?? () ?? () Title: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid() UpgradeStatus: Upgraded to quantal on 2012-06-08 (41 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: gnome-session[1996]: WARNING: Error while executing session-migration: L'exécution du processus fils « session-migration » a échoué (Aucun fichier ou dossier de ce type) gnome-session[1996]: WARNING: Failed to start app: Unable to start application: L'exécution du processus fils « L2tpIPsecVpn » a échoué (Aucun fichier ou dossier de ce type) (empathy:2597): tp-glib-CRITICAL **: tp_connection_upgrade_contacts: assertion `tp_proxy_is_prepared (self, TP_CONNECTION_FEATURE_CONNECTED)' failed (empathy:2597): Gtk-WARNING **: GtkMenuBar 0x1ca83b0 is mapped but visible=1 child_visible=1 parent EmpathyRosterWindow 0x1bfc090 mapped=0 (empathy:2597): tp-glib-CRITICAL **: tp_connection_upgrade_contacts: assertion `tp_proxy_is_prepared (self, TP_CONNECTION_FEATURE_CONNECTED)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1026629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026629] Re: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid()
I'm pretty sure that's a packaging issue, see https://bugzilla.gnome.org/show_bug.cgi?id=680303#c2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1026629 Title: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid() Status in Chat app, and Telepathy user interface: Unknown Status in “empathy” package in Ubuntu: Confirmed Bug description: When i want too launch chat ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: empathy 3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7 Uname: Linux 3.5.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Thu Jul 19 16:16:29 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120309) ProcCmdline: /usr/lib/empathy/empathy-chat ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x4605ca empathy_adium_path_is_valid+26: cmpb $0x2f,(%rdi) PC (0x004605ca) ok source $0x2f ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: empathy StacktraceTop: empathy_adium_path_is_valid () empathy_adium_info_new () empathy_adium_data_new () ?? () ?? () Title: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid() UpgradeStatus: Upgraded to quantal on 2012-06-08 (41 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: gnome-session[1996]: WARNING: Error while executing session-migration: L'exécution du processus fils « session-migration » a échoué (Aucun fichier ou dossier de ce type) gnome-session[1996]: WARNING: Failed to start app: Unable to start application: L'exécution du processus fils « L2tpIPsecVpn » a échoué (Aucun fichier ou dossier de ce type) (empathy:2597): tp-glib-CRITICAL **: tp_connection_upgrade_contacts: assertion `tp_proxy_is_prepared (self, TP_CONNECTION_FEATURE_CONNECTED)' failed (empathy:2597): Gtk-WARNING **: GtkMenuBar 0x1ca83b0 is mapped but visible=1 child_visible=1 parent EmpathyRosterWindow 0x1bfc090 mapped=0 (empathy:2597): tp-glib-CRITICAL **: tp_connection_upgrade_contacts: assertion `tp_proxy_is_prepared (self, TP_CONNECTION_FEATURE_CONNECTED)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1026629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 540536]
*** Bug 34111 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-haze in Ubuntu. https://bugs.launchpad.net/bugs/540536 Title: Empathy does not support AIM buddy chat Status in Telepathy Haze: Confirmed Status in “telepathy-haze” package in Ubuntu: Triaged Bug description: Binary package hint: empathy Empathy does not support AIM buddy chat. This is a request to implement AIM buddy chat support in Empathy, similar to how it is supported in Pidgin. Empathy already has support for multiuser chats for other protocols so only the AIM-specific logic should be needed. Related to bug #540525 To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-haze/+bug/540536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966556] Re: Share Desktop with Empathy need before to go to Share your Desktop
This is https://bugzilla.gnome.org/show_bug.cgi?id=651960 which I fixed upstream. ** Bug watch added: GNOME Bug Tracker #651960 https://bugzilla.gnome.org/show_bug.cgi?id=651960 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/966556 Title: Share Desktop with Empathy need before to go to Share your Desktop Status in “empathy” package in Ubuntu: Confirmed Bug description: I try to share my Desktop with a XMPP'S contact. On the Contextual's menu Share my Desktop is black. It's means this action is possible. But it's don't work. Before i need to go on the Dash, to find Desktop Sharing preference dialog and allow the other to view my Desktop (Allow other users to view your desktop) Expected: An advertissement like this one: Before you need to allow to share your Desktop. After it works Sorry for my english. Franch: J'essaie de partager mon Bureau avec un contact XMPP. Le menu contextuel donne une écriture noir à Partager votre Bureau: l'action est donc possible. Mais cela ne marche pas. Il faut avant aller dans Partage de Bureau et cliquer sur Autoriser d'autres utilisateurs à voir votre Bureau. Ensuite, vous pouvez passer par le menu contextuel, vous recevez une notification comme quoi le bureau va être partagé et le correspondant reçoit la notificatio et cela marche. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.92-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 22:05:56 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/966556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 934394] Re: can't use share my desktop option in empathy
This is https://bugzilla.gnome.org/show_bug.cgi?id=651960 which I fixed upstream. ** Bug watch added: GNOME Bug Tracker #651960 https://bugzilla.gnome.org/show_bug.cgi?id=651960 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/934394 Title: can't use share my desktop option in empathy Status in “empathy” package in Ubuntu: Expired Bug description: I am trying to use this feature of empathy. But share my desktop option remains grayed and not able to click. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Feb 17 23:46:34 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/934394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966556] Re: Share Desktop with Empathy need before to go to Share your Desktop
That's fixed in vino master, not yet released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/966556 Title: Share Desktop with Empathy need before to go to Share your Desktop Status in “empathy” package in Ubuntu: Confirmed Bug description: I try to share my Desktop with a XMPP'S contact. On the Contextual's menu Share my Desktop is black. It's means this action is possible. But it's don't work. Before i need to go on the Dash, to find Desktop Sharing preference dialog and allow the other to view my Desktop (Allow other users to view your desktop) Expected: An advertissement like this one: Before you need to allow to share your Desktop. After it works Sorry for my english. Franch: J'essaie de partager mon Bureau avec un contact XMPP. Le menu contextuel donne une écriture noir à Partager votre Bureau: l'action est donc possible. Mais cela ne marche pas. Il faut avant aller dans Partage de Bureau et cliquer sur Autoriser d'autres utilisateurs à voir votre Bureau. Ensuite, vous pouvez passer par le menu contextuel, vous recevez une notification comme quoi le bureau va être partagé et le correspondant reçoit la notificatio et cela marche. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.92-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 22:05:56 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/966556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966556] Re: Share Desktop with Empathy need before to go to Share your Desktop
That's Ubuntu's choice. They can backport my fix to the vino package if they want to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/966556 Title: Share Desktop with Empathy need before to go to Share your Desktop Status in “empathy” package in Ubuntu: Confirmed Bug description: I try to share my Desktop with a XMPP'S contact. On the Contextual's menu Share my Desktop is black. It's means this action is possible. But it's don't work. Before i need to go on the Dash, to find Desktop Sharing preference dialog and allow the other to view my Desktop (Allow other users to view your desktop) Expected: An advertissement like this one: Before you need to allow to share your Desktop. After it works Sorry for my english. Franch: J'essaie de partager mon Bureau avec un contact XMPP. Le menu contextuel donne une écriture noir à Partager votre Bureau: l'action est donc possible. Mais cela ne marche pas. Il faut avant aller dans Partage de Bureau et cliquer sur Autoriser d'autres utilisateurs à voir votre Bureau. Ensuite, vous pouvez passer par le menu contextuel, vous recevez une notification comme quoi le bureau va être partagé et le correspondant reçoit la notificatio et cela marche. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.92-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 22:05:56 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/966556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 912454] Re: Blank incoming messages
I receveid a log of this bug but it appeared to be a telepathy-butterfly bug. I suggest you to switch to telepathy-haze instead as butterfly is not supported any more. If you manage to reproduce it with another connection manager please mail me dbus-monitor logs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/912454 Title: Blank incoming messages Status in “empathy” package in Ubuntu: Incomplete Bug description: I keep receiving notifications for new incoming messages, by when I click the bubble in the notification area to see the message, a blank chat window opens. The message is actually received correctly, since when I close the window and open it again (by starting a new chat with the sender), the text of the message appears in the recent log (I mean, in the chat window I've just opened). This problem seems to happend with every account I have configured. Protocols used are: msn, gtalk, facebook chat, yahoo, icq. I mostly chat using the first two accounts. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Jan 5 16:40:57 2012 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-16 (81 days ago) XsessionErrors: (jupiter:1684): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private-update_and_descendants_freeze_count 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/912454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 907739]
Merged to master; will be in 0.15.4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/907739 Title: empathy cannot call to android phones Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: 1. I was trying to call to android phone ( Galaxy S II, Gingerbread 2.3.4 with video call enabled) . However, there are no options to call the person. Only initiating chat options are available. 2. Calling from the phone to empathy, the call does not connect immediately when I click 'accept with video call' option. There is a delay of atlest 30 secs 3. The symbol on the phone does not show a video device is available. Compared to Empathy, Pidgin is able to complete the call and I can hear the voice and see video on the computer immediately. The symbol on the phone also indicates a video device is available for a video call. To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/907739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 304889] Re: Does not use system proxy settings
Le mercredi 30 novembre 2011 à 15:55 +, Felipe Contreras a écrit : * telepathy-haze This works fine. Stop claiming that switching to Haze is the solution of all the world's problems. Haze can be an option for protocols not having a proper CM but it would be completely stupid to switch to it for XMPP: no call, no file transfer, no muc, no desktop sharing... * telepathy-butterfly It uses papyon, which looks like it's going to be discontinued. It has basic proxy support, but it's not done through GIO, as it probably should be. I agree that Haze could be used. Actually we're going to switch to Haze for MSN accounts in 3.4 as butterfly (and the other Python CMs) are not properly maintained and lake all the recent Telepathy APIs. * telepathy-gabble Seems to have proxy support through GIO, but there are issues. Which issues exactly? Are there in Gabble? in GIO? * telepathy-idle No proxy support on the horizon. Idle has switched to GIO (fdo #37145) so SHOULD be at the same state as Gabble. * telepathy-rakia No proxy support on the horizon. Or bug report about it. Please feel free to open one. * telepathy-sunshine No proxy support on the horizon. Or bug report about it. Same as Butterfly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/304889 Title: Does not use system proxy settings Status in Chat app, and Telepathy user interface: Invalid Status in Jabber/XMPP connection manager: Confirmed Status in Telepathy Haze: Confirmed Status in A full-featured IRC connection manager for telepathy.: Confirmed Status in “empathy” package in Ubuntu: Invalid Status in “empathy” source package in Lucid: Invalid Status in “empathy” package in Unity Linux: Invalid Bug description: Binary package hint: empathy Empathy wont connect to any major service trough a proxy. I've tried Google Talk, Jabber, MSN and Yahoo. I set the proxy preferences in GNOME, it's a plain proxy for all protocols, without authentication. Pidgin works normally in the same setup. Ubuntu 8.10, Empathy 2.24.1 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/304889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 828802] Re: empathy crashed with SIGSEGV in __memcpy_ssse3()
ls -l /home/username/.cache/telepathy/avatars/gabble/jabber/de0a606f4e61733076fe1f86f3588b4186276e58 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/828802 Title: empathy crashed with SIGSEGV in __memcpy_ssse3() Status in Chat app, and Telepathy user interface: New Status in “empathy” package in Ubuntu: New Bug description: I'm working with empathy and crash. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Thu Aug 18 10:36:09 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1) ProcCmdline: empathy ProcEnviron: PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f604a097040 __memcpy_ssse3+144: movdqu -0x10(%rsi,%rdx,1),%xmm0 PC (0x7f604a097040) ok source -0x10(%rsi,%rdx,1) (0x0506bdf0) not located in a known VMA region (needed readable region)! destination %xmm0 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:119 g_memdup (mem=0x2835f00, byte_size=42163968) at /usr/include/x86_64-linux-gnu/bits/string3.h:52 empathy_avatar_new (data=0x2835f00 \002, len=42163968, format=0x0, filename=0x3663cc0 /home/username/.cache/telepathy/avatars/gabble/jabber/de0a606f4e61733076fe1f86f3588b4186276e58) at empathy-contact.c:1428 contact_set_avatar_from_tp_contact (contact=0x2d4e670) at empathy-contact.c:1818 g_closure_invoke (closure=0x2835f00, return_value=0x0, n_param_values=2, param_values=0x2595040, invocation_hint=optimized out) at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773 Title: empathy crashed with SIGSEGV in __memcpy_ssse3() UpgradeStatus: Upgraded to oneiric on 2011-08-13 (5 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/828802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
