[Nexus7] Xorg crashed with SIGSEGV in __memcpy_ssse3_rep (from sna_video_overlay_set_port_attribute(): guvcview crashed when changing resolution of a picture

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1168250

Please attach the picture that caused the crash (if it can be shared).

Also please run apport-collect 1168250, since some of your log files didn't get added to the bug report for some reason.

Hi Bryce,

I'll try to reproduce that event with today's daily build of Lubuntu
i386 desktop.

I didn't keep the picture, it was the default jpeg picture from the
webcam with my ugly face ;-)

I think the bug is still there, that the jpeg picture is not read by the
default picture viewer of Lubuntu, gpicview. But Xorg will not crash
every time I try this procedure (and I don't know what makes it crash).

Best regards
Nio

On 2013-04-17 20:15, Bryce Harrington wrote:
> Please attach the picture that caused the crash (if it can be shared).
>
> Also please run apport-collect 1168250, since some of your log files
> didn't get added to the bug report for some reason.
>
> ** Description changed:
>
> I was testing Lubuntu Nexus 7 session in a persistent live system.
>
> First I noticed that it works with the built in camera :-)
>
> Then I noticed that the default setting (to save a jpeg picture) creates
> a bad picture file, that cannot be read by gpicview. Work-around: save a
> png picture. I suggest that the default setting is changed until the
> jpeg bug is fixed.
>
> Finally a changed the resolution to 1280x720 which worked. But when I
> changed back to the default 640x480, the program crashed the system and
> sent me back to the log in screen.
> +
> + #7 0xb774543e in FatalError (f=f@entry=0xb776d3c4 "Caught signal %d (%s). Server aborting\n")
> + at ../../os/log.c:793
> + args = 0xbfbb8024 "\v"
> + args2 = 0xbfbb8024 "\v"
> + beenhere = 1
> + #8 0xb773cee8 in OsSigHandler (sip=0xbfbb804c, signo=11, unused=<optimized out>)
> + at ../../os/osinit.c:146
> + #9 OsSigHandler (signo=11, sip=0xbfbb804c, unused=0xbfbb80cc) at ../../os/osinit.c:107
> + #10 <signal handler called>
> + #11 __memcpy_ssse3_rep () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3-rep.S:1289
> + #12 0xb6f27892 in sna_video_overlay_set_port_attribute (scrn=0xb4bb4478, attribute=614400,
> + value=614400, data=0xbfbb860c) at ../../../src/sna/sna_video_overlay.c:237
> + sna = 0x460
> + video = 0xbfbb860c
> +
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.04
> Package: xserver-xorg-core 2:1.13.3-0ubuntu5
> ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
> Uname: Linux 3.8.0-17-generic i686
> ApportVersion: 2.9.2-0ubuntu5
> Architecture: i386
> CasperVersion: 1.330
> Date: Fri Apr 12 08:14:26 2013
> ExecutablePath: /usr/bin/Xorg
> LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130410)
> MarkForUpload: True
> ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
> ProcEnviron:
> -
> +
> Signal: 6
> SourcePackage: xorg-server
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> ** Summary changed:
>
> - [Nexus7] guvcview crashed when changing resolution
> + [Nexus7] Xorg crashed with SIGSEGV in __memcpy_ssse3_rep (from sna_video_overlay_set_port_attribute(): guvcview crashed when changing resolution
>
> ** Summary changed:
>
> - [Nexus7] Xorg crashed with SIGSEGV in __memcpy_ssse3_rep (from sna_video_overlay_set_port_attribute(): guvcview crashed when changin...

I ran guvcview in today's daily build of Lubuntu desktop i386 iso file (similar to when Xorg crashed) in the same laptop. I could reproduce to bug, that the jpeg file is bad, while the png file is good. I tried a lot of changes in the 'guvcviewer controls window', but could not reproduce to crash in Xorg. I ran it in Lubuntu session as well as in Nexus 7 session.

Three files are attached, a bad jpeg file, a good png file and a text file showing my attempts to run the command

apport-collect 1168250

I think there is a bug in apport-collect, that makes it impossible to run, but maybe this information will help a little anyway.

sudodus, thanks for this information.

I think you want to install python-launchadlib. (I thought that was installed by default; by chance did you uninstall it manually? If not then there may be a bug there too...)

So I guess you have three bugs:
  1. Xorg crashed (this bug)
  2. The webcam generates bad jpeg images
  3. python-launchpadlib wasn't installed

I'd like to focus this bug report only to the first issue. Bug reports for the second and third would be worth filing, but I'm not sure what to file the webcam jpeg issue against.

StacktraceTop:
 ?? ()
 ?? ()

sudodus, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

2014-01-07 07:57, Christopher M. Penalver skrev:
> sudodus, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER
>
> Please note, given that the information from the prior release is
> already available, doing this on a release prior to the development one
> would not be helpful.
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> ** Changed in: xorg-server (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg-server (Ubuntu)
> Status: Confirmed => Incomplete
>

No, since there has been no activity at the bug report thread, I think
we need not worry about it. I think there are many other bugs, that
affect many more people.

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]