Bug 156282 - File --> New causes application to quit unexpectedly
Summary: File --> New causes application to quit unexpectedly
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster (Show other bugs)
(Show other bugs)
Version: 4
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-28 16:36 UTC by Paul Kennedy
Modified: 2015-04-20 00:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-28 22:51:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Paul Kennedy 2005-04-28 16:36:42 UTC
Description of problem:
At the configuration tool tab, opening a new configuration file (File --> New)
causes error dialog box with "The Application "system-config-cluster" has quit
unexpectedly..." message to be displayed. The problem happens on the second
attempt after starting the application. The first attempt works as expected. In
addition, failure symptoms vary according to the response to the Error dialog
box: Restart or Close.

Version-Release number of selected component (if applicable):
system-config-cluster 0.9.41 

How reproducible:
After starting application, open a new file, then cancel. Then try opening a new
file the second time. Attempting to open a new file the second time causes an
Error dialog box to be displayed, stating that the application has quit
unexpectedly. Subsequent failure symptoms vary depending on whether you click
Close or Restart Application at the Error dialog box. The "Steps to Reproduce"
section describes each scenario.

Steps to Reproduce:
Scenario 1 - Clicking Close at the Error dialog box:
1.  Start the system-config-cluster application.
2.  At the menu bar, click File --> New.
3.  Clicking File --> New causes the Lock Method dialog box to be displayed.
4.  Close Lock Method dialog box by clicking the Close Window button (X at the 
    upper right corner of the dialog box).
5.  At the menu bar, click File --> New again.
6.  Clicking File --> New causes an empty Lock Method dialog box and an Error
    dialog box to be displayed.
7.  Click Close. Dialog boxes in previous step close.
8.  Start system-config-cluster application.
9.  At the menu bar, click File --> New.
10. Clicking File --> New causes the Lock Method dialog box to be displayed.
11. Close Lock Method dialog box by clicking the Close Window button (X at the 
    upper right corner of the dialog box).
12. At the menu bar, click File --> New again.
13. Clicking File --> New causes an empty Lock Method dialog box to be
    displayed. In addition, intermittently, an error message at the command
    line:
(system-config-cluster:9931): Gtk-CRITICAL **: file gtkcontainer.c: line 1285
(gtk_container_foreach): assertion `GTK_IS_CONTAINER (container)' failed
14. Close the empty Lock Method dialog box by clicking the Close Window button.
15. Repeat step 13 causes same symptoms--occasionally, the Error dialog box is
    displayed.


Scenario 2 - Clicking Restart Application at the Error dialog box:
1.  Start the system-config-cluster application.
2.  At the menu bar, click File --> New.
3.  Clicking File --> New causes the Lock Method dialog box to be displayed.
4.  Close Lock Method dialog box by clicking the Close Window button (X at the 
    upper right corner of the dialog box).
5.  At the menu bar, click File --> New again.
6.  Clicking File --> New causes an empty Lock Method dialog box and an Error
    dialog box to be displayed.
7.  Click Restart Application. Dialog boxes in previous step close and
    application restarts.
8.  At the menu bar, click File --> New.
9.  Clicking File --> New causes the Lock Method dialog box to be displayed.
10. Close Lock Method dialog box by clicking the Close Window button (X at the 
    upper right corner of the dialog box).
11. At the menu bar, click File --> New.
12. Clicking File --> New causes the application to quit with no dialog boxes
    displayed.
    NOTE: For this step, intermittently, an empty Lock Method dialog box is
    displayed, and error message is displayed at the command line:
(system-config-cluster:9931): Gtk-CRITICAL **: file gtkcontainer.c: line 1285
(gtk_container_foreach): assertion `GTK_IS_CONTAINER (container)' failed


 
Actual results:
Application quits after a user tries opening a new file for the second time.

Expected results:
Application should stay running.

Additional info:

Comment 1 Jim Parsons 2005-04-28 18:12:36 UTC
Fixed in 0.9.43-1.0

Comment 2 Corey Marthaler 2005-04-28 22:51:32 UTC
fix verified in -43.


Note You need to log in before you can comment on or make changes to this bug.