[apport] multisync crashed with SIGSEGV in irmc_obex_connect()

Thanks for your bug report.

StacktraceTop:?? ()
?? ()

Feisty is not supported anymore and there is a newer version of multisync. Please open a new bug if you still get a crash in a later version of Ubuntu.

<rant>Sure, we, as users can do that -- but for what benefit? I suspect what will happen is that 1yr 9months after the report of failure a dev would logon an reject the bug because <insert-current-ubuntu-release-here> is no longer supported. This all seems pretty pointless to me.</rant>

Still segfaults for me in Intrepid.

This is the only way to make sure if this is still an issue or not if the bug reporters don't update their bugs. Most of these segfaults happen in alpha/beta versions of Ubuntu and they mostly get fixed but the bug reports remain open forever.

Can you provide exact steps on how to make it crash?

Here's how I can re-create the problem:

1. Make sure multisync and all the libmultisync plugins are installed.
2. Create new profile
3. In the first plugin, chose IrMC. In the options make sure that the connection type is Bluetooth.
4. In the second plugin, chose Backup. In the options, specify any directory name for the backup location.
5. OK to save the new configuration.
6. Clink Sync in the main multisync window.
7. Witness segfault.

I think the key part in the above is the Bluetooth profile.

This problem persists in intrepid, following the procedure outlined by Ali Sheikh, and even with the Evolution 2 plugin. Stack trace:

#0 0x00007f5d9faf23e9 in irmc_obex_connect () from /usr/lib/multisync/libirmc_sync.so
#1 0x00007f5d9faf5f80 in sync_connect () from /usr/lib/multisync/libirmc_sync.so
#2 0x0000000000416725 in sync_main ()
#3 0x00007f5da96983ba in start_thread () from /lib/libpthread.so.0
#4 0x00007f5da94050ad in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Linux vind 2.6.28-4-generic #10-Ubuntu SMP Mon Jan 12 20:05:48 UTC 2009 x86_64 GNU/Linux

multisync 0.82-8.1ubuntu2

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu your reporting this issue on is in End of Life status. You can learn more about this at https://wiki.ubuntu.com/Releases Please update Ubuntu, provide a detailed error report, and mark this bug as new. Thanks!

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Hi there - thanks for the message. My only problem is that I did not
report this bug and am not sure what it is all about! Either someone has
stolen my identity to report bugs (which seems highly unlikely!) or that
there is a mix up somewhere in the database.

Bill

On 19/09/2010 02:25, rusivi1 wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. My apologies as I should not have marked this Invalid.
> The issue that you reported is one that should be reproducible with the
> live environment of the Desktop CD of the development release - Maverick
> Meerkat. It would help us greatly if you could test with it so we can
> work on getting it fixed in the next release of Ubuntu. You can find out
> more about the development release at http://www.ubuntu.com/testing/ .
> Thanks again and we appreciate your help.
>
> ** Changed in: multisync (Ubuntu)
> Status: Invalid => Incomplete
>
>

After updating to Maverick, I tried this out. I can no longer reproduce the crash.