astroid crashed with SIGSEGV in Gtk::TreeView::gobj()

Bug #1940974 reported by Simon Chopin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
astroidmail (Ubuntu)
New
Medium
Unassigned

Bug Description

Trying out the astroid client (with an existing notmuch install). Crashed when I opened a thread from the main inbox view (I think).

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: astroid 0.15-7
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Tue Aug 24 16:30:51 2021
ExecutablePath: /usr/bin/astroid
InstallationDate: Installed on 2021-07-05 (49 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcCmdline: astroid
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f327f320423 <_ZN3Gtk8TreeView10get_cursorERNS_8TreePathERPNS_14TreeViewColumnE+67>: mov -0x18(%rax),%rax
 PC (0x7f327f320423) ok
 source "-0x18(%rax)" (0xffffffffffffffe8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: astroidmail
StacktraceTop:
 Gtk::TreeView::get_cursor(Gtk::TreePath&, Gtk::TreeViewColumn*&) () at /lib/x86_64-linux-gnu/libgtkmm-3.0.so.1
 Astroid::QueryLoader::on_thread_changed(Astroid::Db*, Glib::ustring) ()
 sigc::internal::slot_call<sigc::bound_mem_functor2<void, Astroid::QueryLoader, Astroid::Db*, Glib::ustring>, void, Astroid::Db*, Glib::ustring>::call_it(sigc::internal::slot_rep*, Astroid::Db* const&, Glib::ustring const&) ()
 sigc::internal::signal_emit2<void, Astroid::Db*, Glib::ustring, sigc::nil>::emit(sigc::internal::signal_impl*, Astroid::Db* const&, Glib::ustring const&) ()
 Astroid::ActionManager::emit_thread_changed(Astroid::Db*, Glib::ustring) ()
Title: astroid crashed with SIGSEGV in Gtk::TreeView::get_cursor()
UpgradeStatus: Upgraded to impish on 2021-07-22 (33 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd pkcs11 plugdev sambashare sbuild sudo
separator:

Revision history for this message
Simon Chopin (schopin) wrote :
Revision history for this message
Simon Chopin (schopin) wrote :

Please keep this report as private as there *might* be some personal data in the core dump. I don't believe I had any sensitive mail open, but I'm not entirely sure.

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Gtk::TreeView::gobj (this=<optimized out>) at ../gtkmm/treeview.h:256
 Gtk::TreeView::get_cursor (this=0x55a95b78fc40, path=..., focus_column=@0x7fff658aed28: 0x0) at treeview.cc:151
 Astroid::QueryLoader::on_thread_changed (this=0x55a95bc269a0, db=0x7fff658af3a0, thread_id=...) at ./src/modes/thread_index/query_loader.cc:337
 sigc::bound_mem_functor2<void, Astroid::QueryLoader, Astroid::Db*, Glib::ustring>::operator() (_A_a2=..., _A_a1=@0x7fff658af0b8: 0x7fff658af3a0, this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:2143
 sigc::adaptor_functor<sigc::bound_mem_functor2<void, Astroid::QueryLoader, Astroid::Db*, Glib::ustring> >::operator()<Astroid::Db* const&, Glib::ustring const&> (_A_arg2=..., _A_arg1=@0x7fff658af0b8: 0x7fff658af3a0, this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:108

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in astroidmail (Ubuntu):
importance: Undecided → Medium
summary: - astroid crashed with SIGSEGV in Gtk::TreeView::get_cursor()
+ astroid crashed with SIGSEGV in Gtk::TreeView::gobj()
Revision history for this message
Simon Chopin (schopin) wrote :

Looking through the attachments, I don't see anything particularly private in there. Consequently, I'm making the report public.

information type: Private → Public
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.