[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2009-06-09 Thread Apport retracing service
*** This bug is a duplicate of bug 100066 *** https://bugs.launchpad.net/bugs/100066 ** Attachment removed: CoreDump.gz http://launchpadlibrarian.net/11138738/CoreDump.gz -- wammu crashed with SIGSEGV in PyObject_Call() https://bugs.launchpad.net/bugs/180189 You received this bug

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-10-21 Thread Michal Čihař
*** This bug is a duplicate of bug 100066 *** https://bugs.launchpad.net/bugs/100066 ** This bug has been marked a duplicate of bug 100066 [apport] wammu crashed with SIGSEGV in PyArg_ParseTupleAndKeywords() -- wammu crashed with SIGSEGV in PyObject_Call()

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-09-25 Thread Apport retracing service
StacktraceTop:?? () ?? () ?? () ?? () ?? () ** Tags removed: need-amd64-retrace ** Tags added: apport-failed-retrace ** Attachment added: Stacktrace.txt (retraced) http://launchpadlibrarian.net/17966268/Stacktrace.txt -- wammu crashed with SIGSEGV in PyObject_Call()

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-09-04 Thread Apport retracing service
** Tags added: need-amd64-retrace -- wammu crashed with SIGSEGV in PyObject_Call() https://bugs.launchpad.net/bugs/180189 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

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-02-04 Thread Javier Jardón
I think is a good idea to include these log file in every wammu crash -- wammu crashed with SIGSEGV in PyObject_Call() https://bugs.launchpad.net/bugs/180189 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-02-04 Thread Javier Jardón
Tested with wammu 0.25-1.hardy.ppa.1 (See duplicate bug 182752) -- wammu crashed with SIGSEGV in PyObject_Call() https://bugs.launchpad.net/bugs/180189 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-01-03 Thread Brian Murray
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/11138738/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/11138739/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/11138740/Disassembly.txt ** Attachment

[Bug 180189] Re: wammu crashed with SIGSEGV in PyObject_Call()

2008-01-03 Thread Brian Murray
wammu seems to have created a log file in '/tmp/' however that log file is empty. Is this something that should be included with every wammu crash? If so it may be possible to add a wammu package hook for apport to include the log file. -- wammu crashed with SIGSEGV in PyObject_Call()