lives-exe crashed with SIGSEGV

Bug #638869 reported by Guybrush88
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LiVES
Unknown
Unknown
lives (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: lives

i got this crash at the startup with the version 1.3.7 on maverick

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: lives 1.3.7-1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Sep 15 12:59:05 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/lives/lives-exe
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/lives/lives-exe
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: lives
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: lives-exe crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1607): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1613): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:1608): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Related branches

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

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
salsaman (salsaman) wrote :

Running through valgrind I noted an unitialised value being freed.

I have fixed this and released version 1.3.8.

Please let me know if it is fixed in the new version.

Changed in lives (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Changed in lives (Ubuntu):
assignee: nobody → Alessio Treglia (quadrispro)
status: Confirmed → In Progress
Changed in lives (Ubuntu):
assignee: Alessio Treglia (quadrispro) → nobody
status: In Progress → Fix Committed
Changed in lives (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
salsaman (salsaman) wrote :

Hi,
another user testing 1.3.8 reported a (probably second) crash on startup bug. So please test with the newly released 1.3.9 when it becomes available.

Revision history for this message
Guybrush88 (guybrush) wrote :

now with 1.3.8 i don't get any crash, but it doesn't get opened

Revision history for this message
salsaman (salsaman) wrote :

Try starting it with
lives -nothreaddialog

Revision history for this message
salsaman (salsaman) wrote :

The user who reported the second crash on startup in 1.3.8 has confirmed that 1.3.9 is working for him/her.

Revision history for this message
Alessio Treglia (quadrispro) wrote :

I have already uploaded the 1.3.9 release, please test.

Revision history for this message
Guybrush88 (guybrush) wrote :

the 1.3.9 version works for me

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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