Bug 211384 - regression: kernel 2.6.18-1.2200.fc5 crashes gui applications
regression: kernel 2.6.18-1.2200.fc5 crashes gui applications
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
ppc64 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-10-18 17:09 EDT by Mark Smith
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-13 21:39:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
back trace of xclock crash (6.87 KB, text/plain)
2006-10-18 17:09 EDT, Mark Smith
no flags Details

  None (edit)
Description Mark Smith 2006-10-18 17:09:57 EDT
Description of problem:
ssh -X <ppc64host> 
# xclock  (or firefox or any gui)
with FC5 stock kernel: 2.6.15-1.2054_FC5  all is OK.
# yum update 
 and reboot with new 2.6.18-1.2200.fc5 kernel and 
 repeat, but apps crash.

Version-Release number of selected component (if applicable):
FC5  yum update to latest

How reproducible:easy
Actual results:
gui apps crash

Expected results:

Additional info:
I really did search for a duplicate but could not find any hits for kernel 
version & libc.so.6    :-)

*** buffer overflow detected ***: xclock terminated
======= Backtrace: =========

I believe other symptoms are vnc sessions coming up blank (with color, not 
black, but no desktop)
Comment 1 Mark Smith 2006-10-18 17:09:58 EDT
Created attachment 138835 [details]
back trace of xclock crash
Comment 2 Mark Smith 2006-10-18 17:14:07 EDT
arrgg, please reject this copy as duplicate.  Bugzilla told me (erroneously) 
that product = Fedora%20Core was invalid and I needed to retry.

Comment 3 Mark Smith 2006-10-18 17:16:43 EDT
211383 is the original.
sorry, but my id does not allow me to cancel, close, or dup this off myself.

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