ardour-2.8.12 crashed with SIGSEGV in Gtk::Range::get_adjustment()

Bug #926450 reported by Trond Aasan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ardour (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Crashed when using arrow keys to scroll sideways in mixer window

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ardour 1:2.8.12-1
ProcVersionSignature: Ubuntu 3.2.0-13.22~ppa1-lowlatency 3.2.2
Uname: Linux 3.2.0-13-lowlatency x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sat Feb 4 01:48:03 2012
ExecutablePath: /usr/lib/ardour2/ardour-2.8.12
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/ardour2/ardour-2.8.12
SegvAnalysis:
 Segfault happened at: 0x7f491a2693a4 <_ZN3Gtk5Range14get_adjustmentEv+4>: mov (%rdi),%rax
 PC (0x7f491a2693a4) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ardour
StacktraceTop:
 Gtk::Range::get_adjustment() () from /usr/lib/x86_64-linux-gnu/libgtkmm-2.4.so.1
 Mixer_UI::scroll_right (this=0x4780b00) at gtk2_ardour/mixer_ui.cc:1554
 Mixer_UI::on_key_press_event (this=<optimized out>, ev=<optimized out>) at gtk2_ardour/mixer_ui.cc:1568
 Gtk::Widget_Class::key_press_event_callback(_GtkWidget*, _GdkEventKey*) () from /usr/lib/x86_64-linux-gnu/libgtkmm-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: ardour-2.8.12 crashed with SIGSEGV in Gtk::Range::get_adjustment()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip floppy fuse lpadmin plugdev sambashare sudo

Revision history for this message
Trond Aasan (trond-aasan) wrote :
Revision history for this message
Trond Aasan (trond-aasan) wrote :

Ardour seems to have problem with Ubuntu's overlay scrollbars.

Workaround: Launch Ardour with overlay scrollbars disabled

LIBOVERLAY_SCROLLBAR=0 ardour2

Changed in ardour (Ubuntu):
status: New → Fix Released
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.