Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I have been trying to make sure that release notes are visible in correct languages as part of a documentation QE effort. I've come across this issue too many times now not to report a bug.
I'm installing from an internal server on a virtual machine using virtual machine manager. I give the virtual machine 1024MB RAM and 14GB disk.
The installation gets about half way through, and crashes.
I don't know how to investigate any further.
+++ This bug was initially created as a clone of Bug #957889 +++
Description of problem:
Installing Fedora19 Alpha using downloaded DVD ISO image into vmware Workstation 9.0.2. The installation is stopped abruptly when anakonda is trying to launch graphical instal. Fedora18 installed without problems.
Apparently the component from the bug I cloned this one from does not exist in RHEL7 land, so I picked one. I hope that doesn't confuse matters.
Version-Release number of selected component (if applicable):
anakonda-19.20-1
How reproducible:
always
Steps to Reproduce:
1. Create a new VM in vmware Workstation and set the CD path to installation ISO image
2. Boot the VM
3. Select start installation
Actual results:
Installation freezes when trying to launch graphical install.
This is the output on the console:
anaconda 19.20-1 for Fedora 19-Alpha (pre-release) started.
21:16:26 Not asking for VNC because we don't have a network
(anaconda:691): Gtk-CRITICAL **: gtk_tree_model_filter_get_path: assertion `GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed
LibThai: Fail to open dictionary at '/usr/share/libthai/thbrk.tri'.
(anaconda:691): Gdk-WARNING **: anaconda: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Pane is dead
Expected results:
Clean installation
Additional info:
Fedora15 - Fedora18 works fine in vmware workstation.
--- Additional comment from Chris Lumens on 2013-04-29 15:56:42 EDT ---
Please attach /tmp/X.log.
--- Additional comment from Jaroslav Franek on 2013-04-29 15:56:45 EDT ---
seems there is a segmentation fault in X server, /tmp/X.log attached
--- Additional comment from Chris Lumens on 2013-04-29 15:59:11 EDT ---
[ 113.371] (EE) Backtrace:
[ 113.373] (EE) 0: Xorg (OsLookupColor+0x129) [0x46e569]
[ 113.374] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f659186cf9f]
[ 113.398] (EE) 2: /lib64/libc.so.6 (__memcpy_ssse3_back+0x209c) [0x7f65905e5d0c]
[ 113.399] (EE) 3: /lib64/libpixman-1.so.0 (pixman_rasterize_edges+0xe006) [0x7f65914156b6]
[ 113.400] (EE) 4: /lib64/libpixman-1.so.0 (pixman_image_composite32+0x453) [0x7f65913c6063]
[ 113.400] (EE) 5: /lib64/libpixman-1.so.0 (pixman_glyph_cache_insert+0xf0) [0x7f6591407c50]
[ 113.401] (EE) 6: /usr/lib64/xorg/modules/libfb.so (fbComposite+0x3bc) [0x7f6589d2c53c]
[ 113.403] (EE) 7: Xorg (DamageRegionAppend+0x7e6) [0x5209e6]
[ 113.403] (EE) 8: Xorg (AddTraps+0x408e) [0x51db8e]
[ 113.404] (EE) 9: Xorg (SendErrorToClient+0x3f7) [0x436e17]
[ 113.404] (EE) 10: Xorg (_init+0x3aad) [0x429abd]
[ 113.405] (EE) 11: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f65904beb75]
[ 113.406] (EE) 12: Xorg (_start+0x29) [0x42671d]
[ 113.407] (EE) 13: ? (?+0x29) [0x29]
--- Additional comment from Jaroslav Franek on 2013-05-04 08:32:22 EDT ---
Created attachment 893106[details]
screenshot of crash
I know this screenshot is not too helpful. However, when I get to this point, I don't know what I can do.
I can reproduce the error on RHEL 7.2 during a network installation in non gui mode.
If you hit "Ctrl + | (pipe symbol)" the installer crashes with the message "Pane is dead"
(In reply to Oliver Haessler from comment #10)
> I can reproduce the error on RHEL 7.2 during a network installation in non
> gui mode.
>
> If you hit "Ctrl + | (pipe symbol)" the installer crashes with the message
> "Pane is dead"
That's not totally surprising, ^\ sends SIGQUIT.
We haven't seen any further reports like this, and don't have a reproducer, closing. Please reopen if this issue recurs.
Comment 12Red Hat Bugzilla
2023-09-14 02:07:28 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days