crash when adding a jabber account

Bug #68717 reported by Jurica Zeleznjak
12
Affects Status Importance Assigned to Milestone
Gaim
Invalid
Undecided
Unassigned
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

steps:
- remove an existing jabber account
- crash happens when adding a new one (also jabber)

Revision history for this message
ville palo (vi64pa) wrote :

Thanks, but could you attach a backtrace/crash dump. Is this reproducable? Did this happen on edgy or dapper?

Changed in gaim:
status: Unconfirmed → Needs Info
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

I have the same issue, current edgy (release). I have attached the crash report, I'll try to reproduce with gaim-dbg installed and let you know.

On a similar note though, there are reports of some similar jabber crashes being fixed in beta4, I can't be certain, but that might fix this.

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

Ok, can replicate with stacktrace.

Revision history for this message
ville palo (vi64pa) wrote :

Thanks, This is confirmed.

Changed in gaim:
status: Needs Info → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :
Download full text (6.6 KiB)

More added debug symbols, somebody of the team should forward this upstream.

--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `gaim'.
Program terminated with signal 11, Segmentation fault.
#0 0xb69f8545 in srv_resolved_cb (resp=0x0, results=0, data=0x87ac378) at ../../../../src/protocols/jabber/jabber.c:485
 in ../../../../src/protocols/jabber/jabber.c
#0 0xb69f8545 in srv_resolved_cb (resp=0x0, results=0, data=0x87ac378) at ../../../../src/protocols/jabber/jabber.c:485
 js = (JabberStream *) 0x87ac378
#1 0x080a4adc in resolved (data=0x87ac3f0, source=33, cond=3) at ../../src/dnssrv.c:188
 size = 0
 res = (GaimSrvResponse *) 0x0
 i = 0
 cb = (GaimSRVCallback) 0xb69f84e0 <srv_resolved_cb>
#2 0x080fafe3 in gaim_gtk_io_invoke (source=0x87a1210, condition=17, data=0x8763a78) at ../../src/gtkeventloop.c:74
 gaim_cond = 3
#3 0xb7914c8d in g_io_unix_dispatch (source=0x87b4020, callback=0x80fafa0 <gaim_gtk_io_invoke>, user_data=0x8763a78) at giounix.c:162
 buffer_condition = 0
#4 0xb78eb802 in IA__g_main_context_dispatch (context=0x81860f8) at gmain.c:2045
No locals.
#5 0xb78ee7df in g_main_context_iterate (context=0x81860f8, block=1, dispatch=1, self=0x8165558) at gmain.c:2677
 got_ownership = <value optimized out>
 max_priority = 125
 timeout = 0
 some_ready = 1
 nfds = <value optimized out>
 allocated_nfds = <value optimized out>
 fds = (GPollFD *) 0x865f5c8
 __PRETTY_FUNCTION__ = "g_main_context_iterate"
#6 0xb78eeb89 in IA__g_main_loop_run (loop=0x8625dd0) at gmain.c:2881
 got_ownership = -1215781920
 self = (GThread *) 0x8165558
 __PRETTY_FUNCTION__ = "IA__g_main_loop_run"
#7 0xb7c20574 in IA__gtk_main () at gtkmain.c:1024
 tmp_list = (GList *) 0x0
 functions = (GList *) 0x0
 init = (GtkInitFunction *) 0x0
 loop = (GMainLoop *) 0x8625dd0
#8 0x0810fd0c in main (argc=) at ../../src/gtkmain.c:764
 saved_status = <value optimized out>
 opt_help = <value optimized out>
 opt_login = 0
 opt_nologin = 0
 opt_version = <value optimized out>
 opt_config_dir_arg = 0x0
 opt_login_arg = 0x0
 opt_session_arg = 0x0
 sig_indx = <value optimized out>
 sigset = {__val = {81927, 0 <repeats 31 times>}}
 prev_sig_disp = <value optimized out>
 opt = <value optimized out>
 gui_check = <value optimized out>
 debug_enabled = 0
 errmsg = "0\022õ¿ô\177ú·\000\000\000\0005`H·P\023õ¿ô\177ú·\003\000\000\000\000\000\000\000Ø\022õ¿U\021ú·\b\000\000\000\f\000\000\000\000\000\000\000t/õ¿þ\225ù·\210\212A·x\212A·\f\000\000\000\000\000\000\000š\227\204·è\034}·\000\000\000\000\001\000\000\000\000\000\000\000zòJ·è\023õ¿\226ªù·D/õ¿!\020ú· \200ú·€\201\000\000g/õ¿`/õ¿\\/õ¿\030\206ú·ô\177ú·\v\000\000\000\000\000\000\000P\023õ¿U\021ú·\b\000\000\000,\000\000\000\000\000\000\000t/õ¿þ\225ù·H\212A·\030\212A·,", '\0' <repeats 15 times>, "\030"...
 segfault_message_tmp = <value optimized out>
 error = (GError *) 0x0
 long_options = {{name = 0x8155c71 "config", has_arg = 1, flag = 0x0, val = 99}, {name = 0x814bf0d "debug", has_arg = 0, flag = 0x0,
    val = 100}, {name = 0x814beef "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x8138cd4 "login", has_arg = 2, flag = 0x0, val = 108}, {
    name = 0x81534e2 "nologin...

Read more...

Changed in gaim:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

might be fixed with 2.0beta4, some similar upstream bugs are marked as fixed

Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash from bug #68692 looks the same issue:

1812 setting = g_hash_table_lookup(account->settings, name);
(gdb) bt
#0 0x08070cec in gaim_account_get_int (account=0xffffd1e0, name=0xb68371fe "port", default_value=0)
    at ../../src/account.c:1812
#1 0xb6828550 in srv_resolved_cb (resp=0x0, results=0, data=0x878ee08) at ../../../../src/protocols/jabber/jabber.c:485
#2 0x080a4adc in resolved (data=0x878d028, source=23, cond=3) at ../../src/dnssrv.c:188
#3 0x080fafe3 in gaim_gtk_io_invoke (source=0x8647b00, condition=17, data=0x87626e8) at ../../src/gtkeventloop.c:74

Changed in gaim:
assignee: desktop-bugs → nobody
Revision history for this message
Richard Laager (rlaager) wrote :

If this is still happening with Pidgin, please let us know.

Changed in gaim:
status: New → Incomplete
Richard Laager (rlaager)
Changed in gaim:
status: Incomplete → Invalid
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in gaim:
status: Confirmed → Incomplete
Revision history for this message
Adam Niedling (krychek) wrote :

Edgy and gaim are not supported anymore. Please open a new bug if you get a crash with pidgin in a later version of Ubuntu.

Changed in gaim:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.