segfault in rb_track_transfer_batch_check_profiles()

[Brian J. Murrell]

I have what appears to be a pretty reproducible segfault here in 2.96.

If you need any more info, please don't hesitate to ask.

FWIW, I do have a full apport crash report but since apport sends whole core files, which these days typically contain account credentials, I don't send apport bug reports. I will attach the ThreadedStacktrace though.

ProblemType: Bug
DistroRelease: LinuxMint 12
Package: rhythmbox 2.96-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: i386
Date: Wed Jan 2 06:08:13 2013
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian J. Murrell (brian-interlinx)]

This patch appears to fix the segfault in my local testing.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "patch to fix segfault" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Jeremy Bícha (jbicha)]

This was apparently fixed in rhythmbox 2.98 which is available in Ubuntu 13.04.

[Brian J. Murrell (brian-interlinx)]

On 13-04-14 02:36 PM, Jeremy Bicha wrote:
> This was apparently fixed in rhythmbox 2.98 which is available in Ubuntu
> 13.04.

Which doesn't really do LTS users much good. Can we have a fix
backported? Or even just the patch I supplied to this bug applied and
released?

TBH, getting a fix released in LTS doesn't really matter so much to me
since I have the patch here and I have patched my local copy, but I'm
just thinking of others that might be experiencing it.

[Jeremy Bícha (jbicha)]

Brian, if you want this fix for 12.04 LTS, you should look at the SRU procedures:
https://wiki.ubuntu.com/StableReleaseUpdates

[Brian J. Murrell (brian-interlinx)]

On 13-04-15 09:37 AM, Jeremy Bicha wrote:
> Brian, if you want this fix for 12.04 LTS, you should look at the SRU procedures:
> https://wiki.ubuntu.com/StableReleaseUpdates

Like I said, *I* don't need a release of this in LTS. I have my local
patched copy and it's working just fine.

But other users... inexperienced (i.e. with the bug
finding/reporting/fixing and package updating) users who might not even
know where to find information about this bug in their desktop O/S
deserve a fix.

Ultimately, users should not need to know the SRU procedure. They
should just get fixes because maintainers provide them for them.

[Jeremy Bícha (jbicha)]

If you think this patch needs to be in Ubuntu 12.04, then please add more specific information to the description than "a pretty reproducible segfault". I have no idea how common the crash is or how to reproduce it myself. Thanks.

[Brian J. Murrell (brian-interlinx)]

On 13-04-15 11:04 AM, Jeremy Bicha wrote:
> If you think this patch needs to be in Ubuntu 12.04, then please add
> more specific information to the description than "a pretty reproducible
> segfault". I have no idea how common the crash is or how to reproduce it
> myself. Thanks.

A segfault is a bug, by definition. Bugs should be fixed. They
shouldn't be allowed to fester, waiting for users to trip on them. What
more needs to be explained?

[Jeremy Bícha (jbicha)]

What specific steps should we take to recreate this bug?

I'm not at all saying that this bug shouldn't be fixed but honestly there isn't enough information here for me to know what the bug is, so it's impossible for me to independently verify whether the patch is sufficient to fix the bug on Ubuntu 12.04.

[Brian J. Murrell (brian-interlinx)]

On 13-04-15 11:37 AM, Jeremy Bicha wrote:
> What specific steps should we take to recreate this bug?

TBH, after all of this time, I don't recall.

> I'm not at all saying that this bug shouldn't be fixed but honestly
> there isn't enough information here for me to know what the bug is, so
> it's impossible for me to independently verify whether the patch is
> sufficient to fix the bug on Ubuntu 12.04.

Well, I can attest to the patch working. But if you need to do it
independently, I guess I can't help and we'll just have to leave this
unfixed for the next user to discover.