lives-exe crashed with SIGSEGV

Bug #634805 reported by Guybrush88
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LiVES
Unknown
Unknown
lives (Ubuntu)
New
High
Unassigned

Bug Description

Binary package hint: lives

Hi, i just upgraded LiVES to the 1.3.5 version and i got this crash on the startup. LiVES 1.3.4 on maverick at its latest version didn't have this issue

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: lives 1.3.5-1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Fri Sep 10 12:30:49 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:1602): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1606): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:1603): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
Guybrush88 (guybrush) wrote :
visibility: private → public
Changed in lives (Ubuntu):
importance: Undecided → High
Revision history for this message
Guybrush88 (guybrush) wrote :

this crash happens just after a while the window with the plugins getting loaded appears

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

Please try the latest revision uploaded to maverick.

Revision history for this message
Guybrush88 (guybrush) wrote :

now with the new update i got it opened

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.