@hausoo: It's for KDE, not Gnome.
@Bleobq: Updating is crucial for not being vulnerable too ! ;)
@SpectrE_Fth: Have you take a look at yours logs ? Maybe a Gnome update is not correctly...
Type: Posts; User: iojymbo
@hausoo: It's for KDE, not Gnome.
@Bleobq: Updating is crucial for not being vulnerable too ! ;)
@SpectrE_Fth: Have you take a look at yours logs ? Maybe a Gnome update is not correctly...
The reason is Metasploit does not load module interactively, you can look to this tutorial to see how:
- http://carnal0wnage.attackresearch.com/2008/07/adding-your-own-exploits-in-metasploit.html
...
"Intel VT-d" is related to virtualization :
-...
Most of the time, "black screen with a blinking cursor" means graphical card issue. You don't have this with Live USB / CD because it uses a generic driver and doesn't try to fit your hardware...
Did you try to install the standalone VMware Remote Console (VMRC) ? Works great for me !
It's text consoles, press CTRL+ALT+F3.
I think the only way to mitigate this, is to install Kali on an other HDD and pointing GRUB installation on it.
John_Doe is right, you use only your CPU, not your GPU, look at the documentation:
- http://docs.kali.org/general-use/install-nvidia-drivers-on-kali-linux
"/etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf" is probably locked because like trevorx said, don't update your system in GUI, use tty instead.
Maybe related to this bug:
- https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1614191
Look if you have this line "DPkg::Tools::Options::/usr/bin/apt-listchanges::InfoFD "20";" in...
Maybe "Secure BIOS" settings enabled.
Agree with grid, a simply way to check if a package is available on the Kali repo:
# apt-cache search <pattern to search>
According to bash syntax, it's: DESKTOPID=$(xwininfo -int -name Desktop | head -2 | awk '{print $4}')
Thanks Ed, and don't hesitate to ask here if you need help to achieve this ! ;)
I know how it's frustrating, I've spent many hours with a lots of hardware issues on Linux too... I think it's not really a Kali bug but a generic Debian issue, some advanced users applied custom...
Example :
# dpkg -i /path/to/Download/folder/your_deb_file
Don't worry mate, I'm unfortunately don't live in UK but I'm glad to trying to help you. Have you try to remove Catalyst driver and installing theses packages in replacement ?
# apt-get install...
Change your current directory to the "Download" folder before using "dpkg" or use full path to deb file.
If you cannot fix it with advices given here (https://forums.kali.org/showthread.php?31763-Grey-screen-with-working-mouse-after-login), try to install another desktop than Gnome, g0tmi1lk explains...
No problem edlovesiraq, your problem seems to be a sharing address issue with an other device / driver of your system, you'll probably need to patch "sp5100_tco source code" for changing this and...
First, control if your graphic card is know by your system with:
# lspci
Next, try to look if you have any error at startup:
# dmesg
@frequency: Try hitting "ESC" after you logon or wait some minutes, this bug is related to "Gnome" with some graphic cards, not Kali itself.
I understand you have installed Kali Rolling from the...
You can simply disable this feature with "dconf" at "org.gnome.desktop.media-handling", uncheck "automount" and "automount-open".
Past your /var/log/Xorg.0.log mate.
Change the value of "allowed_users=console" to "allowed_users=anybody" in /etc/X11/Xwrapper.config must be fix your problem.
Yes, you can have some issues with others packages who need this dependency.
No problem mate, we learn everyday too ! ;)
The reason is new distros use "Systemd" in replacement of "SysVinit", "service" command is deprecated now, you should use "systemctl" instead.
For answer to your question, your TOR daemon looks...
I found my personal note about installing it, you just need to remove Nvidia driver (apt-get purge nvidia-*) before and open a tty as "root" :
# systemctl stop gdm
# apt-get install...
Do you have a process listening on 127.0.0.1:8080 ?
Perhaps you can try to install "Bumblebee" in replacement of Nvidia driver because "i915.ko" is an Intel driver related, so your card must have an integrated Intel card ! ;)
Hi Kalilama,
First, you can't use your MacBook wifi card directly into Virtual Box, it works only with USB device, your embedded hardwares are already in use by OSX, that's why your guest Kali...
Just a driver issue, you should solve your problem with this thread : https://ubuntuforums.org/showthread.php?t=1420984
Did you replug your SSD ? In this case, your second HDD become "/dev/sdb" and your Kali partition "/dev/sdb2".
You don't need to unplug your first HDD for installing Kali, Grub needs to know your...
Have you try to simply use /home/user/bashrc for setting $HISTFILE var ? Because you can easily deploy your "code to timestamp history file" to /etc/skel/.bashrc (used when a new user profile is...
Maybe a Gnome / Nvidia compatibility issue, look at my answer here : https://forums.kali.org/showthread.php?32020-upgrade-4-6-0-screen-flash&p=62423#post62423
@yasgur99: Probably "Intel Graphic Series" are the most supported on Linux. Others manufacturers like Nvidia are in priority focused to develop theirs drivers for Windows OS, that's why many users on...
Maybe the same issue than new Elantech touchpad series, you can try to reset it at startup by adding "i8042.kbdreset=1" to yours kernel parameters :
-...
I had the same symptom a couple mouths ago after upgrading Kali Sana to Kali Rolling. It's not a Kali bug, but a "Gnome Shell" issue since 3.18, especially with Nvidia driver as usual ! ;)
If...
Like duxim said before, you should check md5 & sha1 sum of your downloaded Kali ISO. If the 2 matchs, try another USB key ! ;)