gnucash crashes when navigating ledger

Bug #1790388 reported by Marc D.
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnucash (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

- Start gnucash
- Create new file
- Add default accounts
- Open account "Cash in Wallet"
- Press Up Arrow key or Page Up key.
- Gnucash crashes:

[36068.237677] gnucash[10001]: segfault at f0 ip 00007fd15647be22 sp 00007ffda4625608 error 4 in libgdk-3.so.0.2302.0[7fd15645c000+82000]

Expected behavior: Gnucash does not crash.

This behavior is new with the update 1:2.6.19-1 → 1:3.2-1ubuntu4

All output on stdio:

marc@ellen:~$ gnucash --nofile
Found Finance::Quote version 1.47

(gnucash:10735): Gtk-WARNING **: 20:58:54.406: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:58:54.406: gtk_widget_size_allocate(): attempt to underallocate GtkButton's child GtkBox 0x55996d87e460. Allocation is 14x24, but minimum required size is 16x16.

(gnucash:10735): Gtk-WARNING **: 20:58:54.462: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:58:54.523: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:58:54.575: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:58:59.339: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:59:02.596: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:59:04.092: gtk_widget_size_allocate(): attempt to underallocate GncTreeViewAccount's child GtkButton 0x55996d8ba180. Allocation is 26x25, but minimum required size is 28x25.

(gnucash:10735): Gtk-WARNING **: 20:59:05.131: GtkScrollbar 0x55996c5c8260 is drawn without a current allocation. This should not happen.

(gnucash:10735): Gtk-WARNING **: 20:59:05.131: GtkScrollbar 0x55996c5c8860 is drawn without a current allocation. This should not happen.

(gnucash:10735): Gtk-WARNING **: 20:59:05.156: GtkScrollbar 0x55996c5c8260 is drawn without a current allocation. This should not happen.

(gnucash:10735): Gtk-WARNING **: 20:59:05.156: GtkScrollbar 0x55996c5c8860 is drawn without a current allocation. This should not happen.
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnucash 1:3.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: LXQt
Date: Sun Sep 2 20:47:57 2018
InstallationDate: Installed on 2016-01-20 (955 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gnucash
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Marc D. (koshy) wrote :
Revision history for this message
Marc D. (koshy) wrote :

Please notice the core file I have added.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnucash (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc D. (koshy) wrote :

The problem does not occur on Debian buster in Version 3.2-1

Revision history for this message
Marc D. (koshy) wrote :

Still happens in 1:3.3-2

[ 1212.139113] gnucash[30485]: segfault at f0 ip 00007f37ed7e2102 sp 00007fff028ad118 error 4 in libgdk-3.so.0.2400.1[7f37ed7c3000+78000]
[ 1212.139124] Code: 89 df e8 61 3d fe ff e9 ad fd ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 8b 87 f0 00 00 00 c3 0f 1f 84 00 00 00 00 00 31 c0 <48> 39 bf f0 00 00 00 0f 94 c0 c3 0f 1f 00 41 55 41 54 55 48 89 f5

Revision history for this message
Marc D. (koshy) wrote :

I experimented a bit and found that removing the user .xinputrc file solved the problem for me.

Its active contents were:

run_im xim

I do not remember ever having generated the file, although that is possible.

According to im-config, my input method was xim, after deleting the config and logging out of and back into X it now is fcitx.

Revision history for this message
Marc D. (koshy) wrote :

The .xinputrc file was from January 2016, so this still is a regression introduced with the upgrade mentioned in the description.

Revision history for this message
Matthias Jordan (matjordan) wrote :

Still happens with GnuCash 3.7 in Ubuntu 19.10.
Relevant dmesg lines:
[ 268.839500] gnucash[2767]: segfault at f8 ip 00007f70b26f8a96 sp 00007ffd4525bac8 error 4 in libgdk-3.so.0.2404.8[7f70b26d5000+80000]
[ 268.839511] Code: 26 fe ff e9 57 fd ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 8b 87 f8 00 00 00 c3 0f 1f 40 00 f3 0f 1e fa 31 c0 <48> 39 bf f8 00 00 00 0f 94 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00

Steps to repro is basically: create a new GnuCash file, navigate to ledger view, press any key to segfault.

This bug is related to Bug 1110862.

Revision history for this message
Matthias Jordan (matjordan) wrote :

Addendum to my previous comment: removing .xinputrc and logging out and in again did actually work 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.