so far i was unable to reproduce this bug... but in the recent days there were huge amounts of updates (as usual), so maybe this problem is obsolete already. i'm using that valgrind memory check now, and if it happens again, i'll be sure to inform you about it!
On Thu, 2009-04-02 at 01:08 +0000, Andreas Moog wrote: > 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. > > ** Attachment removed: "CoreDump.gz" > http://launchpadlibrarian.net/24587001/CoreDump.gz > > ** Changed in: pidgin (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: pidgin (Ubuntu) > Status: New => Incomplete > > ** Visibility changed to: Public > -- pidgin crashed with SIGSEGV https://bugs.launchpad.net/bugs/352621 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
