soffice.bin crashed with SIGSEGV in sane_v4l_read()

[James P. Carter]

Binary package hint: openoffice.org

Attempted to scan a printed document into an openoffice text writer document.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/openoffice/program/soffice.bin
NonfreeKernelModules: nvidia
Package: openoffice.org-core 1:2.4.1-11ubuntu2.1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/openoffice/program/soffice.bin -writer -splash-pipe=5
ProcEnviron:
 PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: openoffice.org
StacktraceTop:
 sane_v4l_read () from /usr/lib/sane/libsane-v4l.so.1
 ?? ()
 ?? ()
 vos::threadWorkerFunction_impl ()
 ?? ()
Title: soffice.bin crashed with SIGSEGV in sane_v4l_read()
Uname: Linux 2.6.27-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:sane_v4l_read (handle=0x2bc0a90, buf=0x2bcf210 "",
?? ()
?? ()
vos::threadWorkerFunction_impl ()
?? ()

[Chris Cheney (ccheney)]

Bad backtrace, but I will attempt to reproduce to see if I can make it happen.

[James P. Carter (jpcarter)]

Am I missing a dependency that would make the backtrace function more
appropriately? Let me know and I will attempt to re-create as well. I've
got the time. ;-)

james

Chris Cheney wrote:
> Bad backtrace, but I will attempt to reproduce to see if I can make it
> happen.
>
> ** Changed in: openoffice.org (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: openoffice.org (Ubuntu)
> Assignee: (unassigned) => Chris Cheney (ccheney)
>
>

[Chris Cheney (ccheney)]

I don't think you are missing anything yourself as there is an application on the server side that does the retracing. I'm not sure why it didn't retrace properly.

[Chris Cheney (ccheney)]

Confirmed this does not work, I need to test on official version and see it is broken there too.

[penalvch (penalvch)]

James P. Carter, does LibreOffice work for you? If using Lucid or Maverick feel free to perform at the Terminal:

sudo add-apt-repository ppa:libreoffice/ppa && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-writer

[Björn Michaelsen (bjoern-michaelsen)]

[This is an automated message.]
There are no new official OpenOffice.org releases in Ubuntu packaging anymore => Won't Fix

If the problem persists, please mark this bug as "also affects project Libreoffice" or "also affects distribution Libreoffice (Ubuntu)" if that has not happened already.

Please leave references to upstream OpenOffice.org bugs in place to allow cross pollination.

[penalvch (penalvch)]

No reference URL.

[penalvch (penalvch)]

James P. Carter, your crash report for LibreOffice is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.