nemo crashed with SIGSEGV in gtk_tree_model_get_valist()

Bug #1920811 reported by Joshua Peisach
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nemo (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

See: https://github.com/linuxmint/nemo/issues/2614. Reproduced bug

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: nemo 4.8.6-1
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: X-Cinnamon
Date: Mon Mar 22 15:44:16 2021
ExecutablePath: /usr/bin/nemo
InstallationDate: Installed on 2021-02-28 (22 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
ProcCmdline: nemo
SegvAnalysis:
 Segfault happened at: 0x7ffb5fd36422 <gtk_tree_model_get_valist+274>: mov 0x30(%rax),%rcx
 PC (0x7ffb5fd36422) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nemo
StacktraceTop:
 gtk_tree_model_get_valist () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_tree_model_get () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 filename_cell_data_func (column=<optimized out>, renderer=0x55a2a9773830, model=0x55a2a92c3e40, iter=0x55a2a92c40e0, view=0x55a2a9aea550) at ../src/nemo-list-view.c:2162
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nemo crashed with SIGSEGV in gtk_tree_model_get_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
separator:

Revision history for this message
Joshua Peisach (itzswirlz) wrote :
information type: Private → Public Security
information type: Public Security → Public
Revision history for this message
Joshua Peisach (itzswirlz) wrote :

It actually traces to gtk_separator_menu_item_new.

tags: removed: need-amd64-retrace
Changed in nemo (Ubuntu):
status: New → Confirmed
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.