Ubuntu

jackdbus sigsegv handling itself crashes [SRU]

Reported by David Henningsson on 2012-04-17
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
jackd2 (Ubuntu)
High
Unassigned
Precise
High
Unassigned
Quantal
High
Unassigned

Bug Description

[Problem]
<1-2 sentence summary of the issue>

[Impact]
<fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release>

[Development Fix]
<fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. >

[Stable Fix]
<fill me in by pointing out a minimal patch applicable to the stable version of the package.>

[Text Case]
<fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem.>
1.
2.
3.
Broken Behavior:
Fixed Behavior:

[Regression Potential]
<fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected.>

[Original Report]
On shutdown (calling stop from qjackctl) jackdbus crashes. The (first?) error seems to be in the sigsegv chain itself. See attached patch.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: jackd2 1.9.8~dfsg.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 12:26:00 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120103)
SourcePackage: jackd2
UpgradeStatus: No upgrade log present (probably fresh install)

David Henningsson (diwic) wrote :

The attachment "0001-jackdbus-Fix-sigsegv-handling-segfaulting-by-itself.patch" 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.]

tags: added: patch

My patch has now been committed in the upstream master branch, see https://github.com/jackaudio/jack2/commit/f82ec71566b2c18f159004e00a70c2cf3e46d755

Changed in jackd2 (Ubuntu):
status: New → In Progress
status: In Progress → Fix Committed
status: Fix Committed → Triaged
David Henningsson (diwic) wrote :

Please sponsor this debdiff.

Changed in jackd2 (Ubuntu):
status: Triaged → Confirmed
Bryce Harrington (bryce) wrote :

Heya, first off, thanks for this contribution to the LTS, it's much
appreciated!

As it happens, Ubuntu Precise has now progressed into Final Freeze.
Right now changes to the distro are limited to just ultra-critical
release bugs that the release team has flagged as priorities. Most
other bugs, including this one, need to now be handled as Stable
Release Updates (SRUs) or left until the next release (Q-series) opens
for development.

For reference, here is the SRU Policy Doc:
  https://wiki.ubuntu.com/StableReleaseUpdates

I've looked at your patch and think it may qualify as an SRU, but
there's a bit extra paperwork, which helps establish the justification
for the change and makes the change easier for reviewers. Would you
mind helping by filling in some blanks?

I've pasted in the standard SRU template into the bug description.
Click the yellow pencil icon to the right of 'Bug Description', and fill
in the empty sections.

Also, while the patch itself looks ok, there are a few changes necessary
to target it as an SRU:

 1. In the changelog entry, target the upload to 'precise-proposed'
    rather than just 'precise'.

 2. The version number should increment by a point rather than a full
    number. Examples:

     Currently in precise Proposed for precise-proposed
     foobar-1.2-1 ---> foobar-1.2-1ubuntu0.1
     foobar-1.2-1ubuntu2 ---> foobar-1.2-1ubuntu2.1
     foobar-1.2~dfsg.1-1 ---> foobar-1.2~dfsg.1-1ubuntu0.1
     foobar-1.2-1ubuntu1.5 ---> foobar-1.2-1ubuntu1.6

 3. Make certain the correct bug # is listed in the changelog entry
    description, in this format: (LP: #123456)

 4. Doublecheck the maintainer is set to Ubuntu. Easy to do, just run
    `update-maintainer` and it'll fix it.

Changed in jackd2 (Ubuntu):
status: Confirmed → Incomplete
description: updated
Changed in jackd2 (Ubuntu Precise):
importance: Undecided → High
milestone: none → precise-updates
summary: - jackdbus sigsegv handling itself crashes
+ jackdbus sigsegv handling itself crashes [SRU]
Bryce Harrington (bryce) wrote :

Please re-subscribe the ubuntu-sponsors team to the bug report once the above has been done.

Launchpad Janitor (janitor) wrote :

[Expired for jackd2 (Ubuntu Quantal) because there has been no activity for 60 days.]

Changed in jackd2 (Ubuntu Quantal):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers