I've been being annoyed by this for a week or two now. I'm attaching a
backtrace with debug symbols just for completeness (I'm not running
Ubuntu's pidgin, but .
This is http://developer.pidgin.im/ticket/8766 in Pidgin's BTS and has
been reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?
This is probably fixed by
http://developer.pidgin.im/viewmtn/revision/info/34f4897e97207306dbf82089892390d2c2d34847
--
pidgin crashed with SIGSEGV in jabber_parser_process()
https://bugs.launchpad.net/bugs/319010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
A plugin offering that option should be available in Pidgin 2.6.0. It's
probably compilable for Pidgin 2.5.5 (haven't tested, though).
http://developer.pidgin.im/viewmtn/revision/file/63eed8332804fcd21df43cd1d222794c6018b79f/libpurple/plugins/one_time_password.c
--
pidgin stores password and retr
The last line in Pidgin (the mystatusbox plugin uses code existing in Pidgin) at
#10 0x004a048a in pidgin_status_box_redisplay_buddy_icon
(status_box=0x2592b50) at ../../pidgin/gtkstatusbox.c:2260
is
GdkPixbufLoader *loader = gdk_pixbuf_loader_new();
So I don't believe this is a c
I believe you need to run
`handle SIGPIPE nostop`
in order to get a usable backtrace. Your two backtraces so far have just
stopped on SIGPIPE, which indicates that the socket (for an OSCAR and XMPP
connection respectively) has been closed (which is not a SIGSEGV)
--
pidgin crash with Pulse Audi
I'm also a little confused how gtkmain.c seems to have debug symbols but
the libpurple doesn't. Make sure you have the appropriate debug
libraries installed...
--
pidgin crash with Pulse Audio
https://bugs.launchpad.net/bugs/317897
You received this bug notification because you are a member of Ub
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
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
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"
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.
This issue, along with other MSN SOAP crashes, was maybe (likely?)
(don't quote me on that) fixed by this commit:
http://developer.pidgin.im/viewmtn/revision/info/881df13836308d7b078687b7576861609e9c
That commit should make the SOAP code a lot less mysteriously crashy,
though.
--
pidgin cras
There is a patch for 2.5.5 on the upstream ticket (which is
http://developer.pidgin.im/ticket/8774 as Sebastien noted).
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ken, my patch fixes the underlying problem where Cody's patch fixes the
specific null deference that causes the crash.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse
and that will give the file the appropriate permissions and ownership.
Ondřej Cífka:
Your problem with mounting smb://192.16
I see the same symptom on firefox3.0=3.0.3+build1+nobinonly-0ubuntu1
under Intrepid x86_64.
The bad version number is coming from
/usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js.
The last line in the file is:
pref("general.useragent.extra.firefox", "Firefox/3.0.1");
Changing that
I see the same symptom on firefox3.0=3.0.3+build1+nobinonly-0ubuntu1
under Intrepid x86_64.
The bad version number is coming from
/usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js.
The last line in the file is:
pref("general.useragent.extra.firefox", "Firefox/3.0.1");
Changing that
obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse
and that will give the file the appropriate permissions and ownership.
Ondřej Cífka:
Your problem with mounting smb://192.16
I believe you need to run
`handle SIGPIPE nostop`
in order to get a usable backtrace. Your two backtraces so far have just
stopped on SIGPIPE, which indicates that the socket (for an OSCAR and XMPP
connection respectively) has been closed (which is not a SIGSEGV)
--
pidgin crash with Pulse Audi
I'm also a little confused how gtkmain.c seems to have debug symbols but
the libpurple doesn't. Make sure you have the appropriate debug
libraries installed...
--
pidgin crash with Pulse Audio
https://bugs.launchpad.net/bugs/317897
You received this bug notification because you are a member of Ub
I've been being annoyed by this for a week or two now. I'm attaching a
backtrace with debug symbols just for completeness (I'm not running
Ubuntu's pidgin, but .
This is http://developer.pidgin.im/ticket/8766 in Pidgin's BTS and has
been reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?
This is probably fixed by
http://developer.pidgin.im/viewmtn/revision/info/34f4897e97207306dbf82089892390d2c2d34847
--
pidgin crashed with SIGSEGV in jabber_parser_process()
https://bugs.launchpad.net/bugs/319010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
A plugin offering that option should be available in Pidgin 2.6.0. It's
probably compilable for Pidgin 2.5.5 (haven't tested, though).
http://developer.pidgin.im/viewmtn/revision/file/63eed8332804fcd21df43cd1d222794c6018b79f/libpurple/plugins/one_time_password.c
--
pidgin stores password and retr
The last line in Pidgin (the mystatusbox plugin uses code existing in Pidgin) at
#10 0x004a048a in pidgin_status_box_redisplay_buddy_icon
(status_box=0x2592b50) at ../../pidgin/gtkstatusbox.c:2260
is
GdkPixbufLoader *loader = gdk_pixbuf_loader_new();
So I don't believe this is a c
I believe you need to run
`handle SIGPIPE nostop`
in order to get a usable backtrace. Your two backtraces so far have just
stopped on SIGPIPE, which indicates that the socket (for an OSCAR and XMPP
connection respectively) has been closed (which is not a SIGSEGV)
--
pidgin crash with Pulse Audi
I'm also a little confused how gtkmain.c seems to have debug symbols but
the libpurple doesn't. Make sure you have the appropriate debug
libraries installed...
--
pidgin crash with Pulse Audio
https://bugs.launchpad.net/bugs/317897
You received this bug notification because you are a member of Ub
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"
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.
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
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
There is a patch for 2.5.5 on the upstream ticket (which is
http://developer.pidgin.im/ticket/8774 as Sebastien noted).
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ken, my patch fixes the underlying problem where Cody's patch fixes the
specific null deference that causes the crash.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue, along with other MSN SOAP crashes, was maybe (likely?)
(don't quote me on that) fixed by this commit:
http://developer.pidgin.im/viewmtn/revision/info/881df13836308d7b078687b7576861609e9c
That commit should make the SOAP code a lot less mysteriously crashy,
though.
--
pidgin cras
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"
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.
I've been being annoyed by this for a week or two now. I'm attaching a
backtrace with debug symbols just for completeness (I'm not running
Ubuntu's pidgin, but .
This is http://developer.pidgin.im/ticket/8766 in Pidgin's BTS and has
been reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?
This is probably fixed by
http://developer.pidgin.im/viewmtn/revision/info/34f4897e97207306dbf82089892390d2c2d34847
--
pidgin crashed with SIGSEGV in jabber_parser_process()
https://bugs.launchpad.net/bugs/319010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
A plugin offering that option should be available in Pidgin 2.6.0. It's
probably compilable for Pidgin 2.5.5 (haven't tested, though).
http://developer.pidgin.im/viewmtn/revision/file/63eed8332804fcd21df43cd1d222794c6018b79f/libpurple/plugins/one_time_password.c
--
pidgin stores password and retr
The last line in Pidgin (the mystatusbox plugin uses code existing in Pidgin) at
#10 0x004a048a in pidgin_status_box_redisplay_buddy_icon
(status_box=0x2592b50) at ../../pidgin/gtkstatusbox.c:2260
is
GdkPixbufLoader *loader = gdk_pixbuf_loader_new();
So I don't believe this is a c
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
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
This issue, along with other MSN SOAP crashes, was maybe (likely?)
(don't quote me on that) fixed by this commit:
http://developer.pidgin.im/viewmtn/revision/info/881df13836308d7b078687b7576861609e9c
That commit should make the SOAP code a lot less mysteriously crashy,
though.
--
pidgin cras
There is a patch for 2.5.5 on the upstream ticket (which is
http://developer.pidgin.im/ticket/8774 as Sebastien noted).
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ken, my patch fixes the underlying problem where Cody's patch fixes the
specific null deference that causes the crash.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see the same symptom on firefox3.0=3.0.3+build1+nobinonly-0ubuntu1
under Intrepid x86_64.
The bad version number is coming from
/usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js.
The last line in the file is:
pref("general.useragent.extra.firefox", "Firefox/3.0.1");
Changing that
obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse
and that will give the file the appropriate permissions and ownership.
Ondřej Cífka:
Your problem with mounting smb://192.16
I see the same symptom on firefox3.0=3.0.3+build1+nobinonly-0ubuntu1
under Intrepid x86_64.
The bad version number is coming from
/usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js.
The last line in the file is:
pref("general.useragent.extra.firefox", "Firefox/3.0.1");
Changing that
I see the same symptom on firefox3.0=3.0.3+build1+nobinonly-0ubuntu1
under Intrepid x86_64.
The bad version number is coming from
/usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js.
The last line in the file is:
pref("general.useragent.extra.firefox", "Firefox/3.0.1");
Changing that
obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse
and that will give the file the appropriate permissions and ownership.
Ondřej Cífka:
Your problem with mounting smb://192.16
I believe you need to run
`handle SIGPIPE nostop`
in order to get a usable backtrace. Your two backtraces so far have just
stopped on SIGPIPE, which indicates that the socket (for an OSCAR and XMPP
connection respectively) has been closed (which is not a SIGSEGV)
--
pidgin crash with Pulse Audi
I'm also a little confused how gtkmain.c seems to have debug symbols but
the libpurple doesn't. Make sure you have the appropriate debug
libraries installed...
--
pidgin crash with Pulse Audio
https://bugs.launchpad.net/bugs/317897
You received this bug notification because you are a member of Ub
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"
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.
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
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
obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse
and that will give the file the appropriate permissions and ownership.
Ondřej Cífka:
Your problem with mounting smb://192.16
I've been being annoyed by this for a week or two now. I'm attaching a
backtrace with debug symbols just for completeness (I'm not running
Ubuntu's pidgin, but .
This is http://developer.pidgin.im/ticket/8766 in Pidgin's BTS and has
been reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?
This is probably fixed by
http://developer.pidgin.im/viewmtn/revision/info/34f4897e97207306dbf82089892390d2c2d34847
--
pidgin crashed with SIGSEGV in jabber_parser_process()
https://bugs.launchpad.net/bugs/319010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
A plugin offering that option should be available in Pidgin 2.6.0. It's
probably compilable for Pidgin 2.5.5 (haven't tested, though).
http://developer.pidgin.im/viewmtn/revision/file/63eed8332804fcd21df43cd1d222794c6018b79f/libpurple/plugins/one_time_password.c
--
pidgin stores password and retr
The last line in Pidgin (the mystatusbox plugin uses code existing in Pidgin) at
#10 0x004a048a in pidgin_status_box_redisplay_buddy_icon
(status_box=0x2592b50) at ../../pidgin/gtkstatusbox.c:2260
is
GdkPixbufLoader *loader = gdk_pixbuf_loader_new();
So I don't believe this is a c
There is a patch for 2.5.5 on the upstream ticket (which is
http://developer.pidgin.im/ticket/8774 as Sebastien noted).
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ken, my patch fixes the underlying problem where Cody's patch fixes the
specific null deference that causes the crash.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue, along with other MSN SOAP crashes, was maybe (likely?)
(don't quote me on that) fixed by this commit:
http://developer.pidgin.im/viewmtn/revision/info/881df13836308d7b078687b7576861609e9c
That commit should make the SOAP code a lot less mysteriously crashy,
though.
--
pidgin cras
I've been being annoyed by this for a week or two now. I'm attaching a
backtrace with debug symbols just for completeness (I'm not running
Ubuntu's pidgin, but .
This is http://developer.pidgin.im/ticket/8766 in Pidgin's BTS and has
been reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?
This is probably fixed by
http://developer.pidgin.im/viewmtn/revision/info/34f4897e97207306dbf82089892390d2c2d34847
--
pidgin crashed with SIGSEGV in jabber_parser_process()
https://bugs.launchpad.net/bugs/319010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
A plugin offering that option should be available in Pidgin 2.6.0. It's
probably compilable for Pidgin 2.5.5 (haven't tested, though).
http://developer.pidgin.im/viewmtn/revision/file/63eed8332804fcd21df43cd1d222794c6018b79f/libpurple/plugins/one_time_password.c
--
pidgin stores password and retr
The last line in Pidgin (the mystatusbox plugin uses code existing in Pidgin) at
#10 0x004a048a in pidgin_status_box_redisplay_buddy_icon
(status_box=0x2592b50) at ../../pidgin/gtkstatusbox.c:2260
is
GdkPixbufLoader *loader = gdk_pixbuf_loader_new();
So I don't believe this is a c
I believe you need to run
`handle SIGPIPE nostop`
in order to get a usable backtrace. Your two backtraces so far have just
stopped on SIGPIPE, which indicates that the socket (for an OSCAR and XMPP
connection respectively) has been closed (which is not a SIGSEGV)
--
pidgin crash with Pulse Audi
I'm also a little confused how gtkmain.c seems to have debug symbols but
the libpurple doesn't. Make sure you have the appropriate debug
libraries installed...
--
pidgin crash with Pulse Audio
https://bugs.launchpad.net/bugs/317897
You received this bug notification because you are a member of Ub
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"
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.
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
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
There is a patch for 2.5.5 on the upstream ticket (which is
http://developer.pidgin.im/ticket/8774 as Sebastien noted).
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ken, my patch fixes the underlying problem where Cody's patch fixes the
specific null deference that causes the crash.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue, along with other MSN SOAP crashes, was maybe (likely?)
(don't quote me on that) fixed by this commit:
http://developer.pidgin.im/viewmtn/revision/info/881df13836308d7b078687b7576861609e9c
That commit should make the SOAP code a lot less mysteriously crashy,
though.
--
pidgin cras
I see the same symptom on firefox3.0=3.0.3+build1+nobinonly-0ubuntu1
under Intrepid x86_64.
The bad version number is coming from
/usr/lib/firefox-3.0.3/defaults/preferences/firefox-branding.js.
The last line in the file is:
pref("general.useragent.extra.firefox", "Firefox/3.0.1");
Changing that
obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse
and that will give the file the appropriate permissions and ownership.
Ondřej Cífka:
Your problem with mounting smb://192.16
I've been being annoyed by this for a week or two now. I'm attaching a
backtrace with debug symbols just for completeness (I'm not running
Ubuntu's pidgin, but .
This is http://developer.pidgin.im/ticket/8766 in Pidgin's BTS and has
been reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?
This is probably fixed by
http://developer.pidgin.im/viewmtn/revision/info/34f4897e97207306dbf82089892390d2c2d34847
--
pidgin crashed with SIGSEGV in jabber_parser_process()
https://bugs.launchpad.net/bugs/319010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
A plugin offering that option should be available in Pidgin 2.6.0. It's
probably compilable for Pidgin 2.5.5 (haven't tested, though).
http://developer.pidgin.im/viewmtn/revision/file/63eed8332804fcd21df43cd1d222794c6018b79f/libpurple/plugins/one_time_password.c
--
pidgin stores password and retr
The last line in Pidgin (the mystatusbox plugin uses code existing in Pidgin) at
#10 0x004a048a in pidgin_status_box_redisplay_buddy_icon
(status_box=0x2592b50) at ../../pidgin/gtkstatusbox.c:2260
is
GdkPixbufLoader *loader = gdk_pixbuf_loader_new();
So I don't believe this is a c
I believe you need to run
`handle SIGPIPE nostop`
in order to get a usable backtrace. Your two backtraces so far have just
stopped on SIGPIPE, which indicates that the socket (for an OSCAR and XMPP
connection respectively) has been closed (which is not a SIGSEGV)
--
pidgin crash with Pulse Audi
I'm also a little confused how gtkmain.c seems to have debug symbols but
the libpurple doesn't. Make sure you have the appropriate debug
libraries installed...
--
pidgin crash with Pulse Audio
https://bugs.launchpad.net/bugs/317897
You received this bug notification because you are a member of Ub
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"
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.
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
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
There is a patch for 2.5.5 on the upstream ticket (which is
http://developer.pidgin.im/ticket/8774 as Sebastien noted).
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/349009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 102 matches
Mail list logo
