gaim crash after an unsuccessfull connection "read error" (msn_session_set_login_step)

Bug #71031 reported by nakof
130
Affects Status Importance Assigned to Milestone
Gaim
Invalid
Undecided
Unassigned
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

gaim crash after an unsuccessfull connection. it says "read error". note: i'm using connecting over a tor proxy.

Revision history for this message
nakof (nakof) wrote :
Revision history for this message
Eduardo (eduardolella) wrote :

same crash, I am connected directly without a Proxy.

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

Debug backtrace:

"#0 msn_session_set_login_step (session=0x2, step=MSN_LOGIN_STEP_AUTH) at ../../../../src/protocols/msn/session.c:370
#1 0xb71ea51b in nexus_connect_cb (data=0x855c0d0, gsc=0x8543970, cond=GAIM_INPUT_READ)
    at ../../../../src/protocols/msn/nexus.c:482
#2 0xb71a6fb3 in ssl_gnutls_handshake_cb (data=0x8543970, source=14, cond=GAIM_INPUT_READ)
    at ../../../plugins/ssl/ssl-gnutls.c:96
#3 0x080fafe3 in gaim_gtk_io_invoke (source=0x84ada00, condition=G_IO_IN, data=0x853c7f0) at ../../src/gtkeventloop.c:74
#4 0xb78acc8d in g_io_unix_dispatch (source=0x85772e0, callback=0x80fafa0 <gaim_gtk_io_invoke>, user_data=0x853c7f0)
    at giounix.c:162
#5 0xb7883802 in IA__g_main_context_dispatch (context=0x8184180) at gmain.c:2045
#6 0xb78867df in g_main_context_iterate (context=0x8184180, block=1, dispatch=1, self=0x8165378) at gmain.c:2677
#7 0xb7886b89 in IA__g_main_loop_run (loop=0x85476b8) at gmain.c:2881
#8 0xb7bb8574 in IA__gtk_main () at gtkmain.c:1024
#9 0x0810fd0c in main (argc=Cannot access memory at address 0x5
) at ../../src/gtkmain.c:764"

Might be similar to http://sourceforge.net/tracker/index.php?func=detail&aid=1235998&group_id=235&atid=100235 upstream which has been closed without any clear reason (or the SF bug tracker is confusing)? Does anybody knows if that has been fixed or if the bug should be reopened upstream?

Changed in gaim:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Spyros Melcher (spyrakos73) wrote :

I'm getting the same behaviour, too. In fact, I've been getting crashes lately in many different situations, i.e. upon failed MSN login, window closure or completely random. However, this crash report refers to a crash occured after an unsuccesful MSN connection.

OS: Edgy eft fully updated on Fujitsu A1667G2.

Revision history for this message
JackBandit69 (jackbandit27) wrote : Re: [Bug 71031] Re: gaim crash after an unsuccessfull connection "read error" (msn_session_set_login_step)

Oh wow, same here. I didnt think those would be related and attempted to
submit a bugreport previously for them, I am not sure if it worked or not
though. But I have had those same issues. I would give you a copy of my
crash reports for those incidenets, but I had to reformat about 9 times in
the last 3 days. I am trying to dual boot Ubuntu Edgy Eft 6.10 w/ all the
updates and OpenSuSE 10.2 w/ all updates (of course). And I have been having
some nasty Grub issues, so I am Lilo'ing it and things are good so far,
havent tried booting into Edgy yet since adding the info to lilo.conf for
it. Been more trying to get important business work done first. (I like
money). Well if you come across any ideas or solutions please let me know.
As when I get straight here I will work on seeing what I can do to resolve
that issue also. Thanks for the reply.
    Tee

On 1/15/07, SMelcher <email address hidden> wrote:
>
> I'm getting the same behaviour, too. In fact, I've been getting crashes
> lately in many different situations, i.e. upon failed MSN login, window
> closure or completely random. However, this crash report refers to a
> crash occured after an unsuccesful MSN connection.
>
> OS: Edgy eft fully updated on Fujitsu A1667G2.
>
> ** Attachment added: "crash report"
> http://librarian.launchpad.net/5752885/_usr_bin_gaim.1000.crash
>
> --
> gaim crash after an unsuccessfull connection "read error"
> (msn_session_set_login_step)
> https://launchpad.net/bugs/71031
>

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. The link to upstream bug gives just an error message.

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

Other bug subscribers

Remote bug watches

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