flegita crashed with SIGSEGV in gsj_build_pipeline()

Bug #531131 reported by DebianSidUser
58
This bug affects 12 people
Affects Status Importance Assigned to Milestone
gnomescan (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnomescan

flegita crashed with SIGSEGV in gsj_build_pipeline()

ProblemType: Crash
Architecture: amd64
Date: Wed Mar 3 00:01:00 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/flegita
NonfreeKernelModules: nvidia
Package: flegita 0.6.2-0ubuntu1
ProcCmdline: flegita
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/username
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x7fa97af5b18f <gsj_build_pipeline+255>: cmpq $0x0,0x8(%r14)
 PC (0x7fa97af5b18f) ok
 source "$0x0" ok
 destination "0x8(%r14)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnomescan
StacktraceTop:
 gsj_build_pipeline ()
 gnome_scan_job_run_once ()
 gnome_scan_job_run ()
 ?? () from /usr/lib/libgnomescan.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: flegita crashed with SIGSEGV in gsj_build_pipeline()
Uname: Linux 2.6.32-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
DebianSidUser (raza) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gsj_build_pipeline (job=<value optimized out>) at gnome-scan-job.c:423
 gnome_scan_job_run_once (job=0x13c68e0)
 gnome_scan_job_run (job=0x13c68e0)
 gsad_job_run (job=0x1705c20)
 ?? () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnomescan (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Rolf Leggewie (r0lf) wrote :

This bug has enough information for a developer to start working on it. Setting to confirmed. I think you may want to consider reporting the problem upstream to get it fixed as fast as possible.

https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-scan

Changed in gnomescan (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in gnomescan (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.