Bug 1379811 - firewall-config: Gtk-CRITICAL **: gtk_tree_view_get_path_at_pos: assertion 'tree_view != NULL' failed
Summary: firewall-config: Gtk-CRITICAL **: gtk_tree_view_get_path_at_pos: assertion 't...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Eric Garver
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2016-09-27 17:40 UTC by Ajinkya Patil
Modified: 2019-10-31 18:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-09 14:39:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ajinkya Patil 2016-09-27 17:40:07 UTC 
Description of problem:
when lunch firewall-config gets "firewall-config: Gtk-CRITICAL **: gtk_tree_view_get_path_at_pos: assertion 'tree_view != NULL' failed "

Version-Release number of selected component (if applicable):


How reproducible:
Always on customers system.
I did not receive this error.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
firewall-config should run without any error

Additional info:
Comment 2 Ajinkya Patil 2017-06-16 14:51:40 UTC 
Greetings,

When can we expect a fix?

Thanks,
Ajinkya Patil
Comment 3 Ajinkya Patil 2017-08-14 15:17:13 UTC 
Greetings,

When can we expect a fix?

Thanks,
Ajinkya Patil
Comment 5 Ajinkya Patil 2017-10-14 06:10:12 UTC 
Greetings,

Any update on this?

Thanks and Regards,
Ajinkya Patil
Comment 9 Eric Garver 2019-07-23 14:13:10 UTC 
I'm not seeing any issues with firewall-config on recent versions (>= 0.4.4.4).

Details are light in the report, can you provide more information? For example, what specific actions trigger the assertion?
Comment 12 Eric Garver 2019-08-09 14:39:36 UTC 
Closing due to insufficient data. See comment 9.
Note You need to log in before you can comment on or make changes to this bug.