robot-playercam crashed with SIGABRT in __assert_fail_base()

[Stefan Herbrechtsmeier]

Error message:
robot-playercam: /build/buildd/player-3.0.2+dfsg/utils/playercam/playercam.c:470: player_update: Assertion `allocated_size > g_camera->image_count*3' failed

The assert is bogus, because allocated_size is set to g_camera->image_count in player_init.

The bug was fixed in svn revision 8941.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: robot-player 3.0.2+dfsg-3ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 12 15:02:06 2012
ExecutablePath: /usr/bin/robot-playercam
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120411)
ProcCmdline: robot-playercam -h 192.168.0.60
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 LANG=en_US.UTF-8
 LANGUAGE=
Signal: 6
SourcePackage: player
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 player_update ()
Title: robot-playercam crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x4034f0 "allocated_size > g_camera->image_count*3", file=0x4034b0 "/build/buildd/player-3.0.2+dfsg/utils/playercam/playercam.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x4034f0 "allocated_size > g_camera->image_count*3", file=0x4034b0 "/build/buildd/player-3.0.2+dfsg/utils/playercam/playercam.c", line=470, function=0x4031cc "player_update") at assert.c:103
 player_update () at /build/buildd/player-3.0.2+dfsg/utils/playercam/playercam.c:470
 render_camera (data=<optimized out>) at /build/buildd/player-3.0.2+dfsg/utils/playercam/playercam.c:201
 g_main_dispatch (context=0x2018650) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:2515

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures

[Stefan Herbrechtsmeier (stefan-n1by9)]

I have backport the fix from upstream http://sourceforge.net/p/playerstage/svn/8941.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "player_3.0.2+dfsg-3ubuntu3.debdiff" of this bug report has been identified as being a patch in the form of a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. 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-sponsors 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.]

[Dimitri John Ledkov (xnox)]

* Patch targets precise, instead of current development release (raring)
* debian bug #979841, doesn't exist did you mean to use (LP: #979841) in the changelog & Bug-Ubuntu: in the patch header?

The patch is good.

Cannot upload into raring just yet, as it needs python multiarch fix as well (currently FTBFS in raring).

[Stefan Herbrechtsmeier (stefan-n1by9)]

Sorry, I mean LP not debian. Should I update the debdiff?

[Daniel Holbach (dholbach)]

Thanks for your work on this. I'll upload the raring portion. Which other releases are affected?

[Stefan Herbrechtsmeier (stefan-n1by9)]

As this is a bug in version 3.0.2 all releases since oneiric should be affected.

[Launchpad Janitor (janitor)]

This bug was fixed in the package player - 3.0.2+dfsg-4ubuntu3

---------------
player (3.0.2+dfsg-4ubuntu3) raring; urgency=low

  * Fix bogus assertion that cause playercam to crash. (LP: #979841)
 -- Stefan Herbrechtsmeier <email address hidden> Fri, 11 Jan 2013 13:24:36 +0100

[Stefan Herbrechtsmeier (stefan-n1by9)]

It would be nice if this bug could be also fixed in Quantal