Thanks! I appreciate having this info as we're all to quick to dismiss
a similar bug as having the same root cause, which does not seem to be
the case here!
Thanks much!
Mike
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification
I pulled down what I think is the source for Jaunty (pidgin_2.5.5 plus
ubuntu-specific diff patch) and looking at the code, it appears to use
the (later) rewritten/reorganized authentication code (yay!)
If you're seeing the same symptoms, my guess is that maybe it's a
different root cause this tim
any chance at a patch for Jaunty?
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Works fine now in version 1:2.4.3-0ubuntu1~hardy1.
** Changed in: pidgin (Ubuntu)
Status: Confirmed => Fix Released
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Here is a package for i386 with the patch applied.
** Attachment added: "libpurple0_2.4.1-1ubuntu2_i386.deb"
http://launchpadlibrarian.net/15295587/libpurple0_2.4.1-1ubuntu2_i386.deb
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug not
Sorry, I meant to say "I experience this problem without the force old
SSL or the allow plain-text over unencrypted options."
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I experience this problem with the force old SSL or the allow plain-text
over unencrypted options.
The patch above fixes it for me. Attached is a deb package to replace
libpurple0 on 64-bit that includes the patch.
** Attachment added: "libpurple0_2.4.1-1ubuntu2_amd64.deb"
http://launchpadlib
The problem looks pretty straightforward.
In libpurple/protocols/jabber/auth.c,
static void auth_old_cb(JabberStream *js, xmlnode *packet, gpointer
data)
...
const char *challenge;
guchar digest[16];
char h[17], *p;
I'd like to humbly disagree with the Importance ranking of "Low" on this
bug. Lack of communication with my company's internal jabber server is
directly affecting my day to day work, which must be the case with
countless others as well. I'm at the point where I'm going to downgrade
just to get bac
Same problem configured with XMPP to a Mac OS X 10.5.2 iChat server,
with default XMPP protocol settings.
The version in Gutsy works fine (1:2.2.1-1ubuntu4.1).
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification because you are
Add me in the "me too" category.. Upgraded from Ubuntu 7.10 to 8.04 and
now pidgin dies with the same error/stacktrace as above. I do have a
company-internal jabber server account on my list of accounts, as was
mentioned above, and I also used the "Force old (port 5223) SSL" option.
--
stack sma
It seems to be active for an xmpp session, when trying to use the
"plaintext auth over unencrypted streams" AND the "Force old (port 5223)
SSL" in the tab "Advanced" for a XMPP account.
This is strange since this exact configuration worked and was required
by some servers.
Furthermore, I'm not wi
For information, the settings for this account that make pidgin badly
crash are as follow :
[quote]
[...]
1
0
0
ichat.lip6.fr
1
1
I have got the same problem.
Just upgraded from Ubuntu 7.08 to 8.04 and pidgin doesn't even starts,
giving me this error :
$ pidgin
*** stack smashing detected ***: pidgin terminated
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb765e138]
/lib/tls/i686/cmov/li
Still not working... even tried stopping the app-armor stuff.
$ pidgin
*** stack smashing detected ***: pidgin terminated
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7641138]
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb76410f0]
/usr/lib/purple-2/libja
Nevermind as soon as it connects to an internal jabber server over SSL
it dumps core again.
*** stack smashing detected ***: pidgin terminated
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7699138]
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb76990f0]
/u
That worked!
Thanks,
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
When I setup a new user that account is able to start pidgin. I am
going to try and move my ~/.purple directory and see if it is just
something corrupt in there.
Thanks,
--
stack smashing detected: pidgin terminated
https://bugs.launchpad.net/bugs/211507
You received this bug notification becau
Hi there
are you able to reproduce this crash using a new user account?
Thanks in advance
** Changed in: pidgin (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Basilio Kublik (sourcercito)
Status: New => Incomplete
--
stack smashing detected: pidgin terminated
htt
19 matches
Mail list logo
