Error when installing Kali using qemu on Linux Mint

I installed qemu and kvm. Created an image using…

sudo qemu-img create -f qcow2 debian.img 15G 

…and when tried to load the iso file…

sudo kvm -hda debian.img kali-linux.iso -m 2048 -net nic -net user -soundhw all 

then this error shows up…

qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:EDX.syscall [bit 11] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:EDX.lm [bit 29] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2] 

What can I do now?

Linux Mint GRUB over Ubuntu GRUB

I have two disk drives, one is Windows & Ubuntu together (500gb). Today i decided to install L. Mint on my 250gb hdd (USB) when it finished the installation i realised L. Mint had it GRUB installed over the Ubuntu one, and now everytime i disconnect the disk it just doesn’t work, i have searched Google and all i could find is using boot-repair to fix this

My laptop is a Lenovo Thinkpad T430, Intel i7, x64 bit system

So, how can i make it so i can get Ubuntu GRUB back again?

Error al instalar Ubuntu o Linux mint 19.1

Tengo una laptop Fujitsu lifebook t901 4gb ram 320 HDD i5 2410m 2.5

Sucede que tengo 2 USB una con Ubuntu 19.04 y otra con Linux mint 19.01 64 bits ambas.

Cuando intento arrancar la USB me sale el siguiente error

Could not get fio for li->DeviceHandle: Invalid Parameter Failed to find fs: Invalid Parameter Failed to load image \EFI\BOOT\grubx64.efi: Invalid Parameter start_image() returned Invalid Parameter

No sé a qué se debe ese error y no puedo arrancar

Tengo otra laptop una Fujitsu E744 Con 8gb ram 120 gb sdd i5 4210 2.5

Y me funciona perfecto en esta laptop

When I installed Linux Mint 19 and then tried to upgrade, I encountered this error: [on hold]

dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2:  gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides default-dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   PackNo apport report written because MaxReports is reached already                                                                     No apport report written because MaxReports is reached already                                                   No apport report written because MaxReports is reached already                                 No apport report written because MaxReports is reached already               No apport report written because MaxReports is reached already                                                                             No apport report written because MaxReports is reached already                                                           No apport report written because MaxReports is reached already                                         No apport report written because MaxReports is reached already                       No apport report written because MaxReports is reached already     No apport report written because MaxReports is reached already                                                                   No apport report written because MaxReports is reached already                                                 No apport report written because MaxReports is reached already                               age dbus-x11 which provides dbus-session-bus is not configured yet.  dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2:  gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides default-dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   Package dbus-x11 which provides dbus-session-bus is not configured yet.  dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2:  gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides defaultNo apport report written because MaxReports is reached already                                 No apport report written because MaxReports is reached already               No apport report written because MaxReports is reached already                                                                             No apport report written because MaxReports is reached already                                                           No apport report written because MaxReports is reached already                                         No apport report written because MaxReports is reached already                       No apport report written because MaxReports is reached already     No apport report written because MaxReports is reached already                                                                   No apport report written because MaxReports is reached already                                                 No apport report written because MaxReports is reached already                               No apport report written because MaxReports is reached already             No apport report written because MaxReports is reached already                                                                           No apport report written because MaxReports is reached already                                                         -dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   Package dbus-x11 which provides dbus-session-bus is not configured yet.  dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2:  gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides default-dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   Package dbus-x11 which provides dbus-session-bus is not configured yet.  dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2: No apport report written because MaxReports is reached already                                                               No apport report written because MaxReports is reached already                                             No apport report written because MaxReports is reached already                           No apport report written because MaxReports is reached already         No apport report written because MaxReports is reached already                                                                        gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides default-dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   Package dbus-x11 which provides dbus-session-bus is not configured yet.  dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2:  gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides default-dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   Package dbus-x11 which provides dbus-session-bus is not configured yet.  dpkg: error processing package gconf2 (--configure):  dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2:  gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:   Package default-dbus-session-bus is not installed.   Package dbus-user-session which provides default-dbus-session-bus is not configured yet.   Package dbus-session-bus is not installed.   Package dbus-user-session which provides dbus-session-bus is not configured yet.   Package dbus-x11 which provides dbus-session-bus is not configured yet. 

How to install SPFZilla on Mint or Ubuntu [on hold]

I’m using Mint (I know it’s called ask Ubuntu, but Mint is based on Ubuntu, so Ubuntu solutions should work either way), and I would like to install SPFileZilla

Though I’m relatively new to Linux and I can’t install a Program without an guide (I can work on Debian, Ubuntu and Mint and I mainly use the terminal. I’m not very talented with Bash scripting but I know some stuff).

The Problem is, I haven’t found any guide on how to install SPFileZilla, not on the site nor by searching google for +30min).

The Question is, how do you install SPFileZilla? Is it an extension or mod to FileZilla or is it a standalone programm?

I cannot use mouse and keyboard while installing linux mint in virtualbox

I am trying to install a Linux mint VM in virtualbox, but it is not booting and I also tried to experiment with ubuntu, but the icon shows a little keyboard and a little man in a circle which makes me think it is trying to say there is not input hardware detected. I remember running into this trouble before, but there was a video which got me through it stating “here is where you need to use the input tab and select something to get moving during installation” but I was not able to find this again.

Bios says virtualization is enabled and I tried to let mint auto-boot at start but I get a blinking cursor for hours with no activity. While I was trying earlier the cursor stopped blinking and it would just hang. I gave 8GB memory and have 32GB on the host. I gave 30GB storage and 4 cores. I was able to boot the VM in hyper V after disabling secure boot, but I do not know how to change this in VirtualBox. I am trying to attached my logs , but I do not know how many lines you may need.

fresh install Linux Mint has random connections to Google [on hold]

[The Issue]

A fresh install of Mint (19 xfce 32bit), set up with auto-connect to OVPN using native NetworkManager (NM) was giving me some issues with DNS Leak. Delving into this, I got the leaking fixed by setting the DNS servers in NM, for the eth0, manually to the internal DNS of the VPN. Sweet, Fixed!

Nope. Stay with me, that’s not the problem. After I fixed the leak, I was monitoring all the traffic over the eth0 using ‘iftop -i eth0’ while OVPN was connected. Expecting to see only traffic to/from the VPN server (and regular multicasts etc.) Most all traffic was. But, I was surprised to see single intermittent short duration connections to various Google servers that come at a frequency of every few minutes or so. This occurred even when no web browser was open!

Since all traffic should be going over the VPN (tun0), no connections to anywhere, especially google, should be occurring in the clear on eth0!

Looking into this still further, I used ‘nethogs -d 1’ to identify the program responsible for the traffic. Doing nothing on the computer but monitoring nethogs after a fresh boot, showed the google traffic is being brought on by ‘/usr/sbin/NetworkManager’ under user root.

I cannot figure out why a native program, NetworkManager, calls out to google over eth0, when everything should be going over tun0.

Obviously there are some security concerns with this, since the traffic is supposed to be directed to tun0. Does anyone have any thoughts. I am willing to bet that you can replicate this without setting up the VPN. Just look for connections to “googleusercontent” domains, or something like that.

[The Question] Thoughts? How to I disable this traffic? I do not think its NTP. Nethogs reports that its http traffic. And; Even if the traffic goes over tun0, why is the OS talking to google unsolicited?

[Also]

Feel free NOT to respond if your simply giving your own thoughts about paranoia or what you think should or should not be important. This is not a conspiracy, or paranoid delusion. I am only interested in helpful thoughts on fixing this issue, and not interested in what your “OK” with your computer doing over the network,in the background, and behind your back.

Respectfully, -ding

Dual Boot – Windows 10 & Unix Mint Sylvia – 2 physical disks

I would need help on how to make this combination works. I am not new to dual booting/Unix installations, but now I’m really stucked. I have installed on my first disk (sda) windows 10. In the following, an example of output from windows terminal, I also have the whole full output of boot-repair, but it’s too long and I cannot attach it here.

DISKPART> list disk    Disk ###  Status         Size     Free     Dyn  Gpt   --------  -------------  -------  -------  ---  ---   Disk 0    Online          465 GB      0 B        *   Disk 1    Online          111 GB   111 GB 

In Mint GUI, disk0 is sda and disk1 is sdb. And here the volumes:

DISKPART> list volume    Volume ###  Ltr  Label        Fs     Type        Size     Status     Info   ----------  ---  -----------  -----  ----------  -------  ---------  --------   Volume 0     D                       DVD-ROM         0 B  No Media   Volume 1         Recovery     NTFS   Partition    499 MB  Healthy   Volume 2     C                NTFS   Partition    465 GB  Healthy    Boot   Volume 3                      FAT32  Partition     99 MB  Healthy    System 

At the moment, I have unallocated all disk1 to start from a clear disk (I have also shredded it and created a new partion table of type msdos – was this wrong? better gpt?).

I performed different tentatives, here a sampling, I would really glad if someone could lead me to the right path:

  • Tentative 1)

I perform the installation from a live USB stick of Linux Mint. During the installation, I create two partition (root and swap).

When the installer asks my for boot loader partion, I select sda.

Output: at restart, no grub menu. If I force to select the linux partition from the bios boot order, I get the “grub rescue” console

  • Tentative 2)

I perform the installation from a live USB stick of Linux Mint. During the installation, I create two partition (root and swap).

When the installer asks my for boot loader partion, I select sdb.

Output: at restart, no grub menu. If I force to select the linux partition from the bios boot order, I get a black console, with no indication of whatsever

I also tried other ways (but for sure some of those are wrong, in one of this I reached a normal “grub” console, but even in this way, no luck).

At the moment my biggest questions are:

  1. Should I shred the disk again and put inside a gpt instead of mddos (previous the initial shred, it was msdos, but I see that the windows disk is GPT)

  2. From what I see, Volume 2 of disk 0 is the windows boot partition. This (actual) configuration must stay true also after a successfull installation, or the boot partion must change (and become, for example, sdb1)

  3. Is it any useful to add in disk1 (sdb) a boot partition?

  4. If I leave an unallocated partition at the start of disk1/sdb of some MBs, is correct or wrong?

  5. I have removed the option of secure boot from bios. Is this correct?

Linux mint freezes after exiting tty

I have this awkward bug, where Linux totally freezes, black screen and nothing works except forcing shutdown then restart again What i have: Linux mint 19.1 with i3wm Steps to reproduce: startx from tty1 switch to tty2 log in the type “exit” Everything will freeze, and if u switch to tty1 it will give u black screen I find this really weird and awkward, can someone give u a solution for this ?