| Summary: | app-emulation/virtualbox-4.2.24 - starting guest OS in virtualbox quietly crashes X | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | EncryptedPhreak <encryptedphreak> |
| Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | bkohler, encryptedphreak, patrick |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Xorg.0.log.old
Latest dmesg lsmod output prior to running VBox Xorg.0.log.old Latest Xorg.0.log |
||
|
Description
EncryptedPhreak
2014-06-15 12:40:46 UTC
Please DO not RANDOMLY capitalize WORDS, THANK you. as a first step, please try using a currently-supported gentoo-sources, preferably the latest stable. if that does not work, please attach the output of dmesg (if unavailable, try ssh or /var/log/messages) and /var/log/Xorg.0.log (if unavailable, try Xorg.0.log.old). this is almost certainly not a KDE bug. (In reply to Alex Xu (Hello71) from comment #2) > this is almost certainly not a KDE bug. Alex, I GET (non-random) your capitalization point. As can be seen above, I use hardened-sources, which afaik, is currently supported. I never claimed this is a KDE bug. I only filed it this way because I have never seen another app return me to the KDE <user> login screen...and I think the KDE devs should be aware of this, despite not (potentially) being involved. In fact, in every other instance, KDE works well for me using Gentoo Hardened. my apologies for the kernel misidentification. please try upgrading to the latest hardened-sources kernel or if that is not feasible, attach the requested logs. /var/log/X*.log.old should tell you why and how X crashed. If not, then dmesg would probably give a clue. Created attachment 378946 [details]
Xorg.0.log.old
grepping around only shows: grep Virtual Xorg.0.log.old [ 145.691] (--) NOUVEAU(G0): Virtual size is 1024x768 (pitch 0) grep Virtual Xorg.0.log [ 79.686] (--) NOUVEAU(G0): Virtual size is 1024x768 (pitch 0) grep virtual Xorg.0.log.old grep Virtual dmesg [ 1.026138] Bluetooth: Virtual HCI driver ver 1.4 I cannot attach /var/log/dmesg here (perhaps too large)? If you need me to search elsewhere, or for different terms, just let me know. Thanks /me defers to jer (In reply to EncryptedPhreak from comment #7) > I cannot attach /var/log/dmesg here (perhaps too large)? Usually because of insufficient permissions and because web browsers fail to tell you that in advance. For example, on a randomly chosen system here, it's marked 0640 and owned by root:root. Please make a copy as root and try to attach it again. Comment on attachment 378946 [details]
Xorg.0.log.old
All that output suggests that the X server crashed without even getting to write anything about it. I.e. very little.
Created attachment 379102 [details]
Latest dmesg
Created attachment 379104 [details]
lsmod output prior to running VBox
Created attachment 379106 [details]
Xorg.0.log.old
Created attachment 379108 [details]
Latest Xorg.0.log
Hi Jeroen, Thank you for explaining the dmesg attachment issue. Knowing that launching an OS from within VirtualBox would crash my X, I intentionally did so, and then rebooted. Hopefully, either the attached dmesg or the Xorg.0.log files have captured the error, and will provide the needed clue(s). I have also attached the output of lsmod just prior to attempting to run VBox. Of course, if you need me look elsewhere, just let me know. Please reopen if this is still a problem on current versions |
