Bug 63211 - redhat-config-users crashes when launched from Nautilus
Summary: redhat-config-users crashes when launched from Nautilus
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-users
Version: skipjack-beta2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 61590
TreeView+ depends on / blocked
 
Reported: 2002-04-11 08:42 UTC by Warren Togami
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-04-11 18:58:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Warren Togami 2002-04-11 08:42:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020405

Description of problem:
When I attempt to run redhat-config-users from Nautilus, it displays for a split
second then immediately disappears.  The process appears to die.

Tested as root and non-root (via userhelper-gtk) with same result.

Version-Release number of selected component (if applicable):
redhat-config-users-1.0-12 from Rawhide

How reproducible:
Always

Steps to Reproduce:
1. Log into Gnome.
2. In "Start Here" select "System Settings" 
3. Select "User Manager"

Alternative to Reproduce:
1. Nautilus "/usr/bin"
2. Run redhat-config-users from there.

Actual Results:  
You see redhat-config-users run for a split second, but disappears immediately.

Expected Results:  
It shouldn't disappear.

Comment 1 Jay Turner 2002-04-11 11:32:45 UTC
Little more information here.  This is only happening when the application is
launched from Nautilus.  Calling the application directly works just fine. 
Pretty odd.

Comment 2 Nalin Dahyabhai 2002-04-11 15:11:10 UTC
Please check if upgrading to eel-1.0.2-10 (in today's Raw Hide) fixes this
problem (it should).

Comment 3 Warren Togami 2002-04-12 10:23:43 UTC
Tested and confirmed fixed.

Was the problem gtk2 related?

Comment 4 Brent Fox 2002-04-12 14:09:05 UTC
Well, yes and no.  Technically, it was a bug in eel, so no.  However, pygtk2
(libglade2 actually) was dumping some silly error messages to stdout.  However,
eel wasn't opening stdout correctly, so when libglade2 (used by
redhat-config-users) tried to write error messages to stdout which wasn't open,
the program would crash.  The new eel solves the problem by opening stdout
correctly.


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