[Bug 350944] Re: pidgin crashed with SIGSEGV in free()
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?id=576563 (a git change is referenced as fixing it there). ** Bug watch added: Pidgin Trac #8766 http://developer.pidgin.im/ticket/8766 ** Bug watch added: GNOME Bug Tracker #576563 http://bugzilla.gnome.org/show_bug.cgi?id=576563 ** Attachment added: "backtrace-with-symbols.txt" http://launchpadlibrarian.net/26319502/backtrace-with-symbols.txt -- pidgin crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/350944 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/mailman/listinfo/ubuntu-bugs
[Bug 319010] Re: pidgin crashed with SIGSEGV in jabber_parser_process()
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335511] Re: pidgin seg fault when xmpp server sends NULL conversation
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335511] Re: pidgin seg fault when xmpp server sends NULL conversation
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 sufficient. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335591] Re: pidgin stores password and retries on disconnect
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 retries on disconnect https://bugs.launchpad.net/bugs/335591 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/mailman/listinfo/ubuntu-bugs
[Bug 371898] Re: adding an avatar makes pidgin crash
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 crash in Pidgin, but instead is something else. It didn't crash for BUGabundo when he set MALLOC_CHECK_=2 and MALLOC_PERTURB_=254. Any chance this is the fatal assertions in development versions of gtk/gdk/glib? -- adding an avatar makes pidgin crash https://bugs.launchpad.net/bugs/371898 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/mailman/listinfo/ubuntu-bugs
[Bug 184796] Re: pidgin crashes with glibc error "double free or corruption"
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 added: "Fix nautilus-sendto pidgin plugin double free" http://launchpadlibrarian.net/23757902/nautilus-plugin-dbl-free.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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184796] Re: pidgin crashes with glibc error "double free or corruption"
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 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/mailman/listinfo/ubuntu-bugs
[Bug 279083] Re: firefox 3.0.3 on intrepid reports 3.0.1 as user agent
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 to 3.0.3 fixed the problem.
** Changed in: firefox-3.0 (Ubuntu)
Status: New => Confirmed
--
firefox 3.0.3 on intrepid reports 3.0.1 as user agent
https://bugs.launchpad.net/bugs/279083
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/mailman/listinfo/ubuntu-bugs
[Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.
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.168.0.2/shared/ may be unrelated to the patch, as the patch should only affect the listing of shares (so smb://192.168.0.2), not actually connecting to a share. -- nautilus does not display samba shares for machines inside an ADS network. https://bugs.launchpad.net/bugs/207072 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/mailman/listinfo/ubuntu-bugs
[Bug 317897] Re: pidgin crash with Pulse Audio
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 Audio https://bugs.launchpad.net/bugs/317897 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/mailman/listinfo/ubuntu-bugs
[Bug 317897] Re: pidgin crash with Pulse Audio
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184796] Re: pidgin crashes with glibc error "double free or corruption"
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" 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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184796] Re: 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. Instead, what you can do is something like: $ cd ~ $ mkdir pidgin-core-dumps and then start Pidgin (always) as: cd ~/pidgin-core-dumps; ulimit -c unlimited; pidgin & When pidgin crashes, it will leave coredumps in that directory, which you can get a backtrace from like: gdb pidgin -c ~/pidgin-core-dumps/core-file -- 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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349009] Re: pidgin crashed with SIGSEGV
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349009] Re: pidgin crashed with SIGSEGV
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354272] Re: pidgin crashed with g_log: purple_ssl_read: assertion `gsc != NULL' failed xmlnode: Error parsing xml file: Document is empty
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 crashed with g_log: purple_ssl_read: assertion `gsc != NULL' failed xmlnode: Error parsing xml file: Document is empty https://bugs.launchpad.net/bugs/354272 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/mailman/listinfo/ubuntu-bugs
[Bug 360328] Re: pidgin crashed with SIGSEGV in xmlParseChunk()
Whether it appears with jabber or bonjour is basically immaterial. It's an issue with libraries mis-using libxml2 (there's no sane reason they should be registering global error handlers) and libxml2 not prioritizing the per-context error handler over a global one. It appears to have re-occurred with libgsf in some manner, which is the bug that kenorb linked to. -- pidgin crashed with SIGSEGV in xmlParseChunk() https://bugs.launchpad.net/bugs/360328 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/mailman/listinfo/ubuntu-bugs
[Bug 1730657] Re: systemd don't find userservice- and usertimer-files
I'm not sure what (else) changed between 17.04 and 17.10, but this seems to be an ordering issue between `systemd --user` and ecryptfs mounting the decrypted $HOME. Reordering pam_ecryptfs to occur before pam_systemd in /etc/pam.d /common-session appears to address the issue for me. (Note that I _think_ the order is unchanged between 17.04 and 17.10.) I independently came to the same conclusion as https://bugs.launchpad.net/ecryptfs/+bug/1734290, which was to assign a higher priority (e.g. 1) for ecryptfs's pam-config, which seems to be sufficient. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730657 Title: systemd don't find userservice- and usertimer-files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1730657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362890] Re: pidgin crashed with SIGSEGV in _sasl_MD5Update()
This ticket was closed incorrectly. It already contains a perfectly good backtrace as decoded by Apport retracing service. FWIW, this has been reported to Pidgin upstream as http://developer.pidgin.im/ticket/11560 (Windows) and in Spectrum (open- source XMPP transport that leverages libpurple), with the same backtrace. ** Bug watch added: Pidgin Trac #11560 http://developer.pidgin.im/ticket/11560 -- pidgin crashed with SIGSEGV in _sasl_MD5Update() https://bugs.launchpad.net/bugs/362890 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/mailman/listinfo/ubuntu-bugs
[Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
I can also confirm this is fixed after upgrading mutter / libmutter-5-0 to 3.34.1+git20191107-1ubuntu1~19.10.1. Thank you! ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
