After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 662513 - crash in Empathy: Resume computer after su...
crash in Empathy: Resume computer after su...
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: General
2.33.x
Other All
: Normal critical
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-23 11:53 UTC by Reinis Danne
Modified: 2012-09-13 09:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Attachments
empathy auth client backtrace (12.52 KB, text/plain)
2011-10-23 12:20 UTC, Reinis Danne
Details

Description Reinis Danne 2011-10-23 11:53:25 UTC
Version: 2.34.0

What were you doing when the application crashed?
Resume computer after suspend.


Distribution: Gentoo Base System release 2.1
Gnome Release: 2.32.1 2011-10-21 (Gentoo)
BugBuddy Version: 2.32.0

System: Linux 3.0.7-gentoo #1 SMP PREEMPT Wed Oct 19 14:08:43 EEST 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 11004000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Darklooks
Icon Theme: Neu
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 608124928 vsize: 608124928 resident: 38772736 share: 27557888 rss: 38772736 rss_rlim: 18446744073709551615
CPU usage: start_time: 1319370383 rtime: 155 utime: 139 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/empathy'

[Thread debugging using libthread_db enabled]
[New Thread 0x7fb3c265c700 (LWP 18613)]
[New Thread 0x7fb3c7fff700 (LWP 18207)]
[New Thread 0x7fb3ccc71700 (LWP 18206)]
0x00007fb3dfdd464d in __libc_waitpid (pid=<optimized out>, stat_loc=<optimized out>, options=<optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7fb3e125d900 (LWP 18202))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 g_spawn_sync
    at gspawn.c line 404
  • #2 g_spawn_command_line_sync
    at gspawn.c line 717
  • #3 run_bug_buddy
    at gnome-segvhanlder.c line 240
  • #4 bugbuddy_segv_handle
    at gnome-segvhanlder.c line 191
  • #5 <signal handler called>
  • #6 __strlen_sse42
    at ../sysdeps/x86_64/multiarch/strlen-sse4.S line 32
  • #7 g_strdup
    at gstrfuncs.c line 99
  • #8 gtk_status_icon_set_image
    at gtkstatusicon.c line 1877
  • #9 status_icon_blink_timeout_cb
    at empathy-status-icon.c line 352
  • #10 g_timeout_dispatch
    at gmain.c line 3891
  • #11 g_main_dispatch
    at gmain.c line 2425
  • #12 g_main_context_dispatch
    at gmain.c line 2995
  • #13 g_main_context_iterate
    at gmain.c line 3073
  • #14 g_main_loop_run
    at gmain.c line 3281
  • #15 IA__gtk_main
    at gtkmain.c line 1256
  • #16 main
    at empathy.c line 566

	Inferior 1 [process 18202] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
** Message: removing killswitch idx 2
** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
** Message: RFKILL event: idx 1 type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
** Message: RFKILL event: idx 4 type 2 (BLUETOOTH) op 0 (ADD) soft 0 hard 0
** Message: adding killswitch idx 4 state KILLSWITCH_STATE_UNBLOCKED
** Message: RFKILL event: idx 4 type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0
** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
** (bluetooth-applet:18049): DEBUG: Unhandled custom UUID 00000004-0000-1000-8000-0002ee000002 (0x4)
** (bluetooth-applet:18049): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)
** (bluetooth-applet:18049): DEBUG: Unhandled UUID 00005005-0000-1000-8000-0002ee000001 (0x5005)
** (bluetooth-applet:18049): DEBUG: Unhandled UUID 00005601-0000-1000-8000-0002ee000001 (0x5601)
41	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
--------------------------------------------------
Comment 1 Reinis Danne 2011-10-23 12:18:01 UTC
I was connected to two IRC channels at FreeNode and to Google Talk. After resuming and logging in I get channel messages from IRC, clicking on Empathys tray icon to read them, after that the icon shows a lock, then clicking on it Bug Buddy comes up. On a fresh stratup it doesn't ask any passwords, it remembers them.

Sometimes empathy auth client crashes, but that crash is not possible to report (Bug Budy crash?). I'm not sure if that is the same issue, will attach the backtrace here.
Comment 2 Reinis Danne 2011-10-23 12:20:54 UTC
Created attachment 199757 [details]
empathy auth client backtrace

This one happened on fresh startup.
Comment 3 Reinis Danne 2011-10-23 12:24:36 UTC
Gentoo bug here:
https://bugs.gentoo.org/show_bug.cgi?id=388205
Comment 4 Pacho Ramos 2011-10-23 14:26:37 UTC
This seems a dupe of bug 648845, that points to a memory corruption that could cause this (probably due suspend)
Comment 5 Guillaume Desmottes 2011-10-24 09:01:17 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 648845 ***
Comment 6 Reinis Danne 2011-10-24 09:30:58 UTC
But do you have any intention to actually fix the bug?? That other bug is marked as obsolete and you didn't change its status. But I'm still having the issue!
Comment 7 Pacho Ramos 2011-10-24 09:32:07 UTC
Go to bug 648845 for commenting then :)
Comment 8 Guillaume Desmottes 2011-10-24 09:40:07 UTC
You're using a pretty old version as well (2.34). Any chance you could upgrade to 3.2 and check if this bug is still present?
Comment 9 Reinis Danne 2011-10-24 09:55:53 UTC
No, soorry. It would pull in Gnome 3. I'm not willing to do that to my box at this time.
Comment 10 Guillaume Desmottes 2012-09-13 09:23:39 UTC
Closing as this bug was with an old version of Empathy. Please re-open if
you can reproduce with 3.5/3.6.