LTC Owner is: thinh.com LTC Originator is: shenlinf.com Problem description: I was testing "fedora-development tree (aka rawhide), snapshot May26" on discoverylp1. During vnc install, anaconda reported Gdk-ERROR. Connecting discoverylp1 by vnc showed nothing. The same problem didn't occur in May1 version, so it seems that it's a regression. If this is a customer issue, please indicate the impact to the customer: If this is not an installation problem, Describe any custom patches installed. Provide output from "uname -a", if possible: Hardware Environment Machine type (p650, x235, SF2, etc.): Squadron SF4+ Cpu type (Power4, Power5, IA-64, etc.): Power5 Describe any special hardware you think might be relevant to this problem: Please provide contact information if the submitter is not the primary contact. My backups are Shaowu Yang(shaowu.com) in Austin and Changhai Jiang(jiangchh.com) in China. Please provide access information for the machine if it is available. Is this reproducible? If so, how long does it (did it) take to reproduce it? Describe the steps: If not, describe how the bug was encountered: Is the system (not just the application) hung? If so, describe how you determined this: Did the system produce an OOPS message on the console? If so, copy it here: Is the system sitting in a debugger right now? If so, how long may it stay there? Additional information: anaconda output: -------------------------- Running anaconda, the Fedora Core system installer - please wait... Framebuffer ioctl failed. Exiting. Probing for video card: Unable to probe Probing for monitor type: Unknown monitor No video hardware found, assuming headless Starting VNC... WARNING!!! VNC server running with NO PASSWORD! You can use the vncpassword=<password> boot option if you would like to secure the server. The VNC server is now running. Please connect to discoverylp1.upt.austin.ibm.com:1 to begin the install... Gdk-ERROR **: The program 'mini-wm' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest'. (Details: serial 72 error_code 1 request_code 146 minor_code 2) (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.) aborting... --------------------------
*** This bug has been marked as a duplicate of 193555 ***
changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Other |devel ------- Additional Comments From marksmit.com 2006-06-06 00:20 EDT ------- I am changing the version to 'devel' to properly reflect that this recreates on rawhide.
Created attachment 130724 [details] 193555.txt
----- Additional Comments From marksmit.com 2006-06-08 02:22 EDT ------- error as created on June6 rawhide snapshot The June7 snapshot of rawhide appears to recreate with a different error. I hit <enter> to get a shell prompt and the string of 1470 errors occurred. The VNC did start successfully and gave me the welcome screen. When I clicked on 'next', then the serial 886 error occurred. Fedora/RPMS/anaconda-11.1.0.24-1.ppc.rpm
----- Additional Comments From marksmit.com 2006-06-08 02:24 EDT ------- argg. sorry. the text labeling the attachment as a June6 recreate is wrong. it is a June7 snapshot of rawhide.
The assertions you were seeing were being caused by a GTK bug which is fixed in today's rawhide.
Created attachment 130793 [details] 193555.txt
----- Additional Comments From marksmit.com 2006-06-08 20:00 EDT ------- June8 rawhide gives 934 error You are correct. The old error is gone. With June8 rawhide I am seeing (Details: serial 934 error_code 1 request_code 146 minor_code 23) Gdk-error when I click on the 'next' of the welcome screen.