View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001645Kali LinuxGeneral Bugpublic2014-08-06 08:072025-07-14 09:38
Reporteripatch Assigned Tomuts  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformArch Linux using qemu 2.1.50OSGNU/LinuxOS Versionlatest
Product Version1.0.8 
Summary0001645: Kali (latest) 1.0.8 fails to boot using qemu 2.1.50
Description

Hello, to whom it may concern. I am running an up to date Arch system on a MacBook Pro (2013 late). I installed qemu from the git source, and as of writing this I am running qemu 2.1.50 I have launched other Linux ISO distributions such as "parted magic" using qemu with no problems. However, when I try to boot Kali after a clean install the video in the qemu window acts / behaves erratic for a brief moment then goes back to a small black window.

Steps To Reproduce

Have an Arch Linux box with the latest versions of software as of (6AUG14), and install qemu from git source, version should be 2.1.50. Launch qemu with the newly created disk.img and kali.ISO, then install kali to the new disk image. After install completes boot kali and watch it load GRUB bootloader, and various other system services, then watch the screen become eratic and then become black.

Additional Information

https://bbs.archlinux.org/viewtopic.php?id=185228

Activities

ipatch

ipatch

2014-08-06 18:21

reporter   ~0002444

So I ended up downloaded the mini version of kali (1.0.7) amd64 ISO, and I was able to select which packages to install. I chose not to install the Xorg windowing server, and the system boots as intended. However, I selectively chose to install the Xorg windowing server after the system booted using apt-get, and sure enough, it crashes when I run the "startx" script. I'll attach the Xorg crash log to this bug report.
ipatch

ipatch

2014-08-07 23:08

reporter   ~0002446

X.org crash log => https://ghostbin.com/paste/xbcn9
muts

muts

2014-08-11 23:35

reporter   ~0002449

Thanks for this report, however is it so far off our path, we are unlikely to even try to reproduce this.

Issue History

Date Modified Username Field Change
2014-08-06 08:07 ipatch New Issue
2014-08-06 18:21 ipatch Note Added: 0002444
2014-08-07 23:08 ipatch Note Added: 0002446
2014-08-11 23:35 muts Note Added: 0002449
2014-08-11 23:35 muts Status new => closed
2014-08-11 23:35 muts Assigned To => muts
2014-08-11 23:35 muts Resolution open => no change required
2025-07-14 09:38 g0tmi1k Severity crash => minor