FS#32073 - [nfoview] segmentation fault

Attached to Project: Community Packages
Opened by Bruno Guerreiro (American_Jesus) - Thursday, 18 October 2012, 22:59 GMT
Last edited by Ray Rashif (schivmeister) - Sunday, 04 November 2012, 17:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ray Rashif (schivmeister)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
nfoview stop working after last upgrade (1.10-1 -> 1.10-2)

[1] 2027 segmentation fault (core dumped) nfoview

Additional info:
nfoview 1.10-2


Steps to reproduce:
nfoview
This task depends upon

Closed by  Ray Rashif (schivmeister)
Sunday, 04 November 2012, 17:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.11
Comment by Alexander F. Rødseth (xyproto) - Friday, 19 October 2012, 11:55 GMT
Thanks for reporting. Is this on x86_64 or i686?
Comment by Bruno Guerreiro (American_Jesus) - Friday, 19 October 2012, 13:16 GMT
In x86_64
Comment by Ray Rashif (schivmeister) - Saturday, 20 October 2012, 08:31 GMT
Possibly depends on  FS#32034 , so we have to wait and see until gnome unstable hits, well, stable.
Comment by x33a (x33a) - Thursday, 01 November 2012, 13:57 GMT
With gnome 3.6 in stable, still no luck.

I am getting:

**
Gtk:ERROR:gtkstylecontext.c:1006:style_data_lookup: assertion failed: (priv->widget != NULL || priv->widget_path != NULL)
Comment by x33a (x33a) - Thursday, 01 November 2012, 13:57 GMT
Oh, and I am on i686.
Comment by Ray Rashif (schivmeister) - Saturday, 03 November 2012, 14:16 GMT
Yes, confirmed. This happens when the executable imports 'nfoview', so it is probably an app-specific issue related to gtk3 perhaps. Let me pursue this upstream if I can't find anything obvious in the code.
Comment by Ray Rashif (schivmeister) - Sunday, 04 November 2012, 11:44 GMT
  • Field changed: Category (Packages → Upstream Bugs)
Confirmed to be an upstream incompatibility with recent software, fix will be rolled out as an updated release:

https://bugzilla.gnome.org/show_bug.cgi?id=687513

So we will have to wait until 1.11.

Loading...