Bug 181774 - nautilus crashes with BadAlloc error in .xsession-errors
Summary: nautilus crashes with BadAlloc error in .xsession-errors
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: metacity (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-16 14:36 UTC by K Donate
Modified: 2014-06-18 09:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-06 19:23:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
.xsession.errors file (6.59 KB, text/plain)
2006-02-16 14:49 UTC, K Donate
no flags Details
.xsession-errors file (924 bytes, text/plain)
2006-02-16 14:50 UTC, K Donate
no flags Details

Description K Donate 2006-02-16 14:36:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060111 Firefox/

Description of problem:
This problem is dificult to duplicate.  Users report nautilus crashing often during similar application use.  However, they are also more often than not able to perform the required steps inthe application without the crash.

Regardless, at first just the window title bars disappear or get corrupted with color blocks.  Then things progress to window menus popping up in non-relative positions to the window they belong to.  For example, I have a terminal window in the lower left corner of the screen.  I click on the File menu.  The file menu will actually pop up in the upper right of the desktop.

Often, as things degrade, text in the window titles and menus are no longer readible or visible.  Attachment .xsession-errors.1 has some BadAlloc error messages in it that may help.

Yesterday, things progressed to a point such that the user had absolutely no control over items on the desktop.  Eventually all the windows disappeared including his trash and home icons.  The .xsession-errors.2 file is from yesterday, saved after this event occured.

I wish I had more for you, but I'm not were to look.  The users are using eXceed and VNC to connect to the IBM xseries 336 boxes running RH WS3.  The problem occurs more frequently when eXceed is being used.  It has only happened once in the past week using VNC.  I've asked the users to notify as early as possible when the crash occurs so I can grab a screen shot.

Thank you.

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

How reproducible:

Steps to Reproduce:

Actual Results:  Window titles are "messed up", windows stop responding, window menu do align with their respective windows.  Evenutally, all windows disappear are are unrecognizable.

Expected Results:  none of that,

Additional info:

** (nautilus:12778): WARNING **: Throbber activation exception 'Child process did not give an error message, unknown failure occurred'
The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 293876 error_code 11 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Comment 1 K Donate 2006-02-16 14:49:31 UTC
Created attachment 124751 [details]
.xsession.errors file

Comment 2 K Donate 2006-02-16 14:50:56 UTC
Created attachment 124752 [details]
.xsession-errors file

Comment 3 Alexander Larsson 2006-02-17 14:27:44 UTC
Does the mispositioning and discoloring only happen for nautilus windows and
menus, or for other applications too?

Comment 4 K Donate 2006-02-17 14:36:56 UTC
All the windows, nautilus and other apps.

Comment 5 Alexander Larsson 2006-02-17 14:57:35 UTC
Then I don't think this is really a nautilus bug. Nautilus is just suffering
more than other apps from it. I'm not really sure where the real bug is though.
Maybe in eXceed, vnc, or the window manager.

Comment 6 K Donate 2006-02-17 15:02:41 UTC
Good point.  I hadn't really thought about it like that.  But, I needed to start
somewhere to get help with this problem.

eXceed and VNC never crash themselves.  They both stay operational, although you
can't do much of anything since the Linux windows themselves are either gone or
not responding.  I tend to think the window manager may be the next area to

What additional information can I try to get the determine the source of the

Comment 7 Alexander Larsson 2006-02-20 09:47:46 UTC
I'm sorry, i can't help much wrt eXceed, VNC and window managers.

Comment 8 K Donate 2006-02-20 13:11:19 UTC
The users are using Gnome, which I believe uses metacity as the window manager.
 How do I go about moving this bug over to those products?

Comment 9 Alexander Larsson 2006-02-20 17:14:04 UTC
Just change the component.

Comment 10 Søren Sandmann Pedersen 2006-09-06 19:23:50 UTC
Without either access to the system or more information, it is impossible to say
what this could be.

Comment 11 Søren Sandmann Pedersen 2006-09-06 19:25:48 UTC
For official Red Hat Enterprise Linux support, please log into the Red Hat
support website at http://www.redhat.com/support and file a support ticket,
or alternatively contact Red Hat Global Support Services at 1-888-RED-HAT1
to speak directly with a support associate and escalate an issue.

Comment 12 K Donate 2006-09-07 01:36:31 UTC
Not once did anyone ask me to supply additional data.  Perhaps that request
should have been made before closing due to "insufficient data".

Thanks for your help.  :-(

Comment 13 Søren Sandmann Pedersen 2006-09-07 16:48:11 UTC
Well, I can change the resolution to "CANTFIX" if you'd like, but I don't see
any way to fix this, as there isn't even a way to know which component is
responsible for the bug.

As I also said, for support for Red Hat Enterprise Linux, you need to use the
Red Hat support website at http://www.redhat.com/support and file a support ticket.

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