Hide Forgot
Description of problem: Starting Firefox from a gnome-terminal results in: Failed to create drawable LLVM_ERROR: Allocation failed when allocating new memory in the JIT Can't allocate RWX Memory: Permission denied Version-Release number of selected component (if applicable): firefox-7.0.1-1.fc17.x86_64 How reproducible: Don't know, tried once Steps to Reproduce: 1. Run Firefox from gnome-terminal 2. 3. Actual results: Error message as noted, no firefox Expected results: Firefox running Additional info:
I tried the above after trying to start it from the menu didn't work
Please, describe the steps that led to this issue and how to reproduce it. What settings, networks, or configurations are needed to reproduce the issue? What's you desktop environment? Could we get attached ~/.xsession-errors and /var/log/messages after the issue happens, please? Thank you
Just started in runlevel 3, then startx. Error window: Can't start, ICE socket. Tried again, sucess. I have Gnome, but fallback mode (reported as #745316). No network. Started a gnome-terminal, ran firefox from there.
Created attachment 527778 [details] Requested .xsession-errors
Created attachment 527779 [details] /var/log/messages since boot
Oh, forgot to mention: I logged in as my regular user on this Atom dual core netbook (Samsung N210). Also, xulrunner has been updated to 7.0.1-3.fc17 in the meantime, and llvm to 2.9-5.fc17. In any case, exactly the same result as reported before.
Your system seems to fail on so many places during the startup that I don't know where to start analyzing it. However, quite certainly, ICE issue is just last in the many. Didn't you have some kind of drive malfunction happening to you lately? There seem to be whole directories missing on your drive. Doesn't rpm -Va show some corrupted packages? Reassigning to systemd for further evaluation, but it could be PolKit as well.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log), and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Did a complete cleanup (removed orphans, deleted duplicates (none found), updated; reinstalled everything that "rpm -Va" was complaining about). Still the same.
Did a complete SELinux autorelabel, still the same.
BTW, no reports of HDD malfunction in /var/log/messages
OK, so could we get those files I requested in the comment 8, please? Thank you
Sorry, I was sure to have attached them. Must have gotten lost in the BZ update :-( In any case, as there were so many problems with this machine even after the cleanup, I did a clean install from Fedora 16 nightly 20111013, reinstalled my other stuff and it is now working fine. Sorry for the noise. Perhaps you should close it and say I'm an idiot :-/