I'm getting a similar error, but pidgin crashes immediately after trying to run
it, see the attached pidgin-crash.txt
It however doesn't crash when I run it with Valgrind as asked for above
** Attachment added: "pidgin-crash.txt"
http://launchpadlibrarian.net/27046722/pidgin-crash.txt
--
pid
the valgrind log
** Attachment added: "valgrind-logs-pidgin.tar.gz"
http://launchpadlibrarian.net/27046735/valgrind-logs-pidgin.tar.gz
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a mem
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in: naut
my audio is selected to ALSA already, nautilus plugin is unchecked, but still
crash.
matt...@priapus:~/bug-report$ *** glibc detected *** /usr/bin/pidgin: double
free or corruption (fasttop): 0x0a7e3220 ***
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6[0xb75e4454]
/lib/tls/i686/cmov/l
this bug has a zillion gdb logs now, what would be useful is somebody
having the issue sending the bug to bugzilla.gnome.org rather than
keeping adding logs there
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notificati
** Attachment added: "gdb-pidgin.90.txt"
http://launchpadlibrarian.net/24153191/gdb-pidgin.90.txt
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
again. (PS. libxml-gdb is installed)
** Attachment added: "gdb-pidgin.88.txt"
http://launchpadlibrarian.net/24054242/gdb-pidgin.88.txt
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a mem
crashed with no error msg.
** Attachment added: "gdb-pidgin.87.txt"
http://launchpadlibrarian.net/24053955/gdb-pidgin.87.txt
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubu
Moving to nautilus-sendto package as upstream seems to think the problem
lies there.
** Changed in: nautilus-sendto (Ubuntu)
Sourcepackagename: pidgin => nautilus-sendto
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug no
BUGabundo, the libxml comment wasn't directed at you.
http://launchpadlibrarian.net/23818717/gdb-pidgin.85.txt (from BlueT)
contains a number of calls in libxml2, for which it would probably be
helpful to have those debug symbols.
In general, you don't need to run pidgin inside of gdb constantly.
On Tuesday 17 March 2009 17:57:48 Brian Curtis wrote:
> I cant reproduce this issue, so if you can,
It happened once its a fluke!
--
Hi, I'm BUGabundo, and I am Ubuntu (whyubuntu.com)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net && Ubuntu LoCoTeam Portugal
http://ubuntu-pt.org
Linux user
i already have libxml2-dbg installed.
do i need to go run pidgin again on gdb the all time as i used too?
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
BUGabundo: can you test that patch. I cant reproduce this issue, so if you
can, please follow https://wiki.ubuntu.com/Bugs/PatchTesting and give that
patch a test following the guidelines in that.
Thanks!
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net
BUGabundo, yours is also almost likely the same nautilus.so crash as
BlueT's (see patch above).
BlueT, it might be helpful to install libxml2-dbg to get symbols from
the libxml in your backtrace, since the crash is mostly in libxml2
--
pidgin crashes with glibc error "double free or corruption"
New one!
$ pidgin
E: client-conf-x11.c: XOpenDisplay() failed
E: shm.c: shm_open() failed: Too many open files
E: socket-client.c: socket(): Too many open files
E: socket-client.c: socket(): Too many open files
E: socket-client.c: socket(): Too many open files
E: socket-client.c: socket(): Too ma
Brian: yes I disabled the Nautilus integration and select the sound
device to ALSA already.
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
BlueT: have you tested the patch and/or the "Tools->Plugins and uncheck
the Nautilus one." fix?
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
There's no error msg but still crash frequently.
** Attachment added: "gdb-pidgin.85.txt"
http://launchpadlibrarian.net/23818717/gdb-pidgin.85.txt
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because
** Changed in: pidgin
Status: New => Invalid
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Tools->Plugins and uncheck the Nautilus one.
Your last crash is probably caused by the Gstreamer PulseAudio leak.
Tools->Preferences->Sounds and change Sound Method to ALSA.
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bu
hello darkrain42,
is there anything I can do except recompile nautils from source with this patch?
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: pidgin (Ubuntu)
Status: Confirmed => Triaged
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
(pidgin:24293): Pango-WARNING **: failed to create cairo scaled font,
expect ugly output. the offending font is 'AR PL UMing HK Light
8.33203125'
(pidgin:24293): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='AR PL UMing HK Light 8.33203125', text=''
I don't want to clutter up the pidgin ticket, but bluet's crashes are
all caused by the nautilus integration plugin [nautilus-sendto package]
with the attached patch (I thought I'd done something with this, but
apparently not) fixing what I see as the likely cause of the double
free.
** Attachment
** Bug watch added: Pidgin Trac #8635
http://developer.pidgin.im/ticket/8635
** Also affects: pidgin via
http://developer.pidgin.im/ticket/8635
Importance: Unknown
Status: Unknown
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/18479
** Changed in: pidgin
Status: Unknown => New
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
matt...@priapus:~/bug-report$ backtrace.sh pidgin &
[1] 1385
matt...@priapus:~/bug-report$ outputting trace to '/tmp/gdb-pidgin.txt'
matt...@priapus:~/bug-report$ *** glibc detected *** /usr/bin/pidgin:
double free or corruption (!prev): 0x09cce580 ***
[1]+ Donebacktrace.sh p
matt...@priapus:~/bug-report$ Trying to open sysfs for reading: 開啟太多檔案
Trying to open sysfs for reading: 開啟太多檔案
*** glibc detected *** /usr/bin/pidgin: double free or corruption (!prev):
0x20063d30 ***
matt...@priapus:~/bug-report$
[1]+ Donebacktrace.sh pidgin
" 開啟太多檔案" mean
matt...@priapus:~/bug-report$ backtrace.sh pidgin &
[1] 21648
matt...@priapus:~/bug-report$ outputting trace to '/tmp/gdb-pidgin.txt'
matt...@priapus:~/bug-report$
(pidgin:21650): Pango-WARNING **: failed to create cairo scaled font, expect
ugly output. the offending font is 'AR PL UMing HK Ligh
Brian, I got the error again.
https://bugs.edge.launchpad.net/ubuntu/+source/pidgin/+bug/326252/comments/4
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Could you please try http://www.getdeb.net/search.php?keywords=pidgin
the newest version of pidgin to see if you still get the error?
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member o
matt...@priapus:~/bug-report$
(pidgin:6956): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='AR PL UMing TW Light 9.9990234375', text='恩'
*** glibc detected *** /usr/bin/pidgin: double free or corruption (out):
0x0b47f990 ***
matt...@priapus:~/bug-repor
to Brian,
matt...@priapus:~$ LANG="C" apt-cache policy pidgin
pidgin:
Installed: 1:2.5.2-0ubuntu1
Candidate: 1:2.5.2-0ubuntu1
Version table:
*** 1:2.5.2-0ubuntu1 0
500 http://ftp.twaren.net intrepid/main Packages
100 /var/lib/dpkg/status
--
pidgin crashes with glibc error "
BlueT: What version of Pidgin and Ubuntu are you using?
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
matt...@priapus:~$
(pidgin:30911): Pango-WARNING **: failed to create cairo scaled font, expect
ugly output. the offending font is 'Kochi Gothic 9.9990234375'
(pidgin:30911): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='Kochi Gothic 9.9990234375', t
matt...@priapus:~$ *** glibc detected *** /usr/bin/pidgin: double free
or corruption (!prev): 0x09fd5310 ***
[1]+ Donebacktrace.sh pidgin
** Attachment added: "gdb-pidgin.56.txt"
http://launchpadlibrarian.net/22897682/gdb-pidgin.56.txt
--
pidgin crashes with glibc error
matt...@priapus:~$
(pidgin:19106): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='AR PL UMing TW Light 9.9990234375',
text='老公，我要換掉'
*** glibc detected *** /usr/bin/pidgin: double free or corruption (!prev):
0x8aa0f350 ***
[1]+ Done
Just happened to me for the 1st time... its something new cause I have
lots of Pidgin crash, but this just happened today.
$ pidgin
*** glibc detected *** pidgin: double free or corruption (fasttop):
0x08365480 ***
=== Backtrace: =
/lib/libc.so.6[0x7fb174a57d48]
/lib/libc.so.
(pidgin:8013): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='AR PL UMing TW Light 9.9990234375', text='这'
*** glibc detected *** /usr/bin/pidgin: double free or corruption (!prev):
0xb1d271a0 ***
[1]+ Donebacktrace.sh pidgin
**
matt...@priapus:~$
(pidgin:18594): Pango-WARNING **: shaping failure, expect ugly output.
shape-engine='BasicEngineFc', font='AR PL UMing TW Light 9.9990234375',
text='有的話就幫妳介紹啊,'
*** glibc detected *** /usr/bin/pidgin: double free or corruption (!prev):
0x08428920 ***
[1]+ Done
I got similar problem too.
Pidgin crashed, I didn't even know when.
matt...@priapus:~$ backtrace.sh pidgin &
[1] 12295
matt...@priapus:~$ outputting trace to '/tmp/gdb-pidgin.txt'
matt...@priapus:~$ *** glibc detected *** /usr/bin/pidgin: double free
or corruption (!prev): 0x08f66050 ***
[1]+
The same problem here. It sometimes just "Segmentation fault", sometimes with
"double free or corruption".
No special protocol or server - simple plain AOL ICQ.
version of pidgin and libpurple - 2.4.1-ubuntu2-1 (hardy-updates).
[EMAIL PROTECTED]:~$ /usr/bin/pidgin
Segmentation fault
[EMAIL PROT
I no longer work at a location with an OpenFire-brand Jabber server
running on an Amazon EC2 instance, so I can't speak to this one way or
another.
This doesn't mean that the bug is fixed, but I have no way of testing it
now.
--
pidgin crashes with glibc error "double free or corruption"
https:/
due to no response, marking as invalid
** Changed in: pidgin (Ubuntu)
Status: Incomplete => Invalid
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/184796
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Are you still experiencing this issue with an up-to-date system. Pidgin
is up to 2.4.3 on hardy and 2.5.0 on intrepid Alpha4.
** Changed in: pidgin (Ubuntu)
Status: Confirmed => Incomplete
--
pidgin crashes with glibc error "double free or corruption"
https://bugs.launchpad.net/bugs/1847
I seem to be running into this problem. I was attempting to migrate our
(OpenFire) Jabber server to an Amazon EC2 box; TCP port 5222 is open on
the security policy. Oddly, while I can connect fine over our VPN, going
over the internet (which is to say, through Amazon's firewall) causes a
crash. Att
I'm sorry I can't do that. I live behind a http/https proxy so apport
will not work for me. See this bug for info.
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/94130
I have a .crash file though, is there any other way I can send it?
** Changed in: pidgin (Ubuntu)
Status: Won't Fi
Hi Geoff
Thank you for taking the time to report this bug and helping to make Ubuntu
better. However, your crash report is either missing or challenging to deal
with as a ".crash" file. Please follow these instuctions to have apport report
a new bug about your crash that can be dealt with by the
49 matches
Mail list logo
