sorry, make that .bz2 as it's a bit smaller then
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
crash report at:
http://saturn.flamingspork.com/~stewart/_usr_bin_evolution-2.8.1000.crash
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The permission for that file doesn't seem to be correct, you can also
attach the crash file to the bug if you want
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
gah, sorry about that. It's a 53MB dump, so a bit hard to attach. should
be fixed now.
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Rejected
--
Crash wh
Could you run apport-retrace on the crash file with libglib2.0-0-dbg
evolution-data-server-dbg evolution-dbg installed and then attach the
stripped version of the crash to the bug page?
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@l
The following doesn't really give me much:
$ apport-retrace -s _usr_bin_evolution-2.8.1000.crash
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
--- thread stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Could t
The coredump are limited to 200M by default probably, can you get that
crash reliably? In which case maybe try running evolution with gdb and
get the backtrace from gdb directly
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
sorry, make that .bz2 as it's a bit smaller then
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
crash report at:
http://saturn.flamingspork.com/~stewart/_usr_bin_evolution-2.8.1000.crash
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The permission for that file doesn't seem to be correct, you can also
attach the crash file to the bug if you want
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Rejected
--
Crash wh
gah, sorry about that. It's a 53MB dump, so a bit hard to attach. should
be fixed now.
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could you run apport-retrace on the crash file with libglib2.0-0-dbg
evolution-data-server-dbg evolution-dbg installed and then attach the
stripped version of the crash to the bug page?
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@l
The following doesn't really give me much:
$ apport-retrace -s _usr_bin_evolution-2.8.1000.crash
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
--- thread stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Could t
The coredump are limited to 200M by default probably, can you get that
crash reliably? In which case maybe try running evolution with gdb and
get the backtrace from gdb directly
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
The following doesn't really give me much:
$ apport-retrace -s _usr_bin_evolution-2.8.1000.crash
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
--- thread stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Could t
The coredump are limited to 200M by default probably, can you get that
crash reliably? In which case maybe try running evolution with gdb and
get the backtrace from gdb directly
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
sorry, make that .bz2 as it's a bit smaller then
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
crash report at:
http://saturn.flamingspork.com/~stewart/_usr_bin_evolution-2.8.1000.crash
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The permission for that file doesn't seem to be correct, you can also
attach the crash file to the bug if you want
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
gah, sorry about that. It's a 53MB dump, so a bit hard to attach. should
be fixed now.
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could you run apport-retrace on the crash file with libglib2.0-0-dbg
evolution-data-server-dbg evolution-dbg installed and then attach the
stripped version of the crash to the bug page?
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@l
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Rejected
--
Crash wh
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Rejected
--
Crash wh
The following doesn't really give me much:
$ apport-retrace -s _usr_bin_evolution-2.8.1000.crash
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
--- thread stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Could t
The coredump are limited to 200M by default probably, can you get that
crash reliably? In which case maybe try running evolution with gdb and
get the backtrace from gdb directly
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
sorry, make that .bz2 as it's a bit smaller then
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
crash report at:
http://saturn.flamingspork.com/~stewart/_usr_bin_evolution-2.8.1000.crash
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The permission for that file doesn't seem to be correct, you can also
attach the crash file to the bug if you want
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
gah, sorry about that. It's a 53MB dump, so a bit hard to attach. should
be fixed now.
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could you run apport-retrace on the crash file with libglib2.0-0-dbg
evolution-data-server-dbg evolution-dbg installed and then attach the
stripped version of the crash to the bug page?
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@l
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Rejected
--
Crash wh
The following doesn't really give me much:
$ apport-retrace -s _usr_bin_evolution-2.8.1000.crash
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
--- thread stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Could t
The coredump are limited to 200M by default probably, can you get that
crash reliably? In which case maybe try running evolution with gdb and
get the backtrace from gdb directly
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
sorry, make that .bz2 as it's a bit smaller then
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
crash report at:
http://saturn.flamingspork.com/~stewart/_usr_bin_evolution-2.8.1000.crash
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The permission for that file doesn't seem to be correct, you can also
attach the crash file to the bug if you want
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
gah, sorry about that. It's a 53MB dump, so a bit hard to attach. should
be fixed now.
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could you run apport-retrace on the crash file with libglib2.0-0-dbg
evolution-data-server-dbg evolution-dbg installed and then attach the
stripped version of the crash to the bug page?
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@l
The following doesn't really give me much:
$ apport-retrace -s _usr_bin_evolution-2.8.1000.crash
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
--- thread stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Could t
The coredump are limited to 200M by default probably, can you get that
crash reliably? In which case maybe try running evolution with gdb and
get the backtrace from gdb directly
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
sorry, make that .bz2 as it's a bit smaller then
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
crash report at:
http://saturn.flamingspork.com/~stewart/_usr_bin_evolution-2.8.1000.crash
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The permission for that file doesn't seem to be correct, you can also
attach the crash file to the bug if you want
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
gah, sorry about that. It's a 53MB dump, so a bit hard to attach. should
be fixed now.
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could you run apport-retrace on the crash file with libglib2.0-0-dbg
evolution-data-server-dbg evolution-dbg installed and then attach the
stripped version of the crash to the bug page?
--
Crash while running offlineimap
https://launchpad.net/bugs/75426
--
ubuntu-bugs mailing list
ubuntu-bugs@l
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Rejected
--
Crash wh
48 matches
Mail list logo