Ubuntu doesn’t boot after install, huge swapfile

Was working without issue within Ubuntu 18.04 on a dual-boot machine.

Installed a tex ide via the command line:

sudo apt-get install texmaker 

which appeared to complete successfully. I subsequently clicked on the first gummi link in a response on this SE page, which lanched a new tab, appeared to be resolving, but never fully resolved after a minute or so. I closed it, launched a new tab and searched, never successfully getting to the page.

I wasn’t doing much otherwise, just watching a youtube vid on an adjacent screen and realized my memory was blocked up after getting errors to cd via the command line. I tried a df on my home directory to see what might be causing it and showed most dirs with normal memory allocations, but a huge swapfile, multiple gigs. I tried restarting to clear it, but haven’t been able to get back in.

I’d allocated 40GB for the Ubuntu partition, and don’t save anything substantial there barring a couple GB movie files in the last couple days, without issue, so I wouldn’t expect the recent install of texmaker would have changed things, even at 1GB+. Checking Windows disk manager shows 100% free, not sure whether that’s good or bad (partition 5):

enter image description here

Any thoughts on how to diagnose and fix.

Edit (with additional boot detail): I’m able to boot, select Ubuntu from within the grub dialogue, and ultimately end up on a command-line looking screen with a version of:

/dev/p5 clean 234234/2342234 files, 234234/2324234 blocks 

after which it hangs.

Ubuntu Server 18.04.2 stuck on boot after install

So I just installed Ubuntu Server 18.04.2 on VirtualBox, and during the install reboot, it froze at:

[ OK ] Reached target Cloud-init target 

I gave it 1GB of memory, 1 core of CPU, and 500GB of storage because it is for a home server I am setting up.

Should I wait for it, shut it down the hard way, or do something else?

Thank you in advance.

No possible way to install Ubuntu on Asus Zenbook UX433FN

My laptop specs: 512 GB SSD CPU: COREI7 8’th generation RAM: 16GB Graphics: Nvidia Geforce MX150

I’ve had an Ubuntu 18.04 on my laptop for a while. I had to install ukuu to upgrade kernel to 4.20 (otherwise the output sound won’t work). It worked fine until recently that when I ran “sudo apt upgrade”, I encountered a freezing red screen before login. I changed boot parameters but it didn’t change anything.

I thought ukuu was causing this problem, So I tried to install Ubuntu 19.04 (which comes with kernel 5). But I failed to do so. The only way I can get past setup options is to choose “install Ubuntu in safe graphics”. After the installation finishes and I reboot, the freezing red screen reoccurs and I can’t login. I tried to change boot parameters by pressing E in boot menu. In the line “linux” line, I replaced “ro quiete splash” with “nomodeset” or “nouveau.modeset=0” (I also tried only adding these two latter commands at the end of the line only.) But it didn’t change anything. If I go to recovery mode (in any kernel version), it stucks on “loading initial ramdisk”.

I also tried installing Ubuntu 18.10 and then upgrade it to Ubuntu 19.04. I was successful in installing Ubuntu 18.10. However, in order to be able to boot into Ubuntu 18.10, I must add “noiveau.modeset=0” to boot parameters. When I was able to login, I installed Nvidia drivers by navigating to “Software & Updates” and installed recommended 390 version of Nvidia drivers. After that, the boot and reboot is ok but again when I run “sudo apt upgrade”, then after reboot the red freezing screen comes again. So I tried installing Nvidia driver version that is suitable for Geforce MX150 (I searched and found out that the latest supporting version is 430). I did it by adding Nvidia repository. After that, the red screen reoccured again. Trying to blacklist Nvidia drivers (by creating and editing a file in direcotry etc/modprobe.d/) lead to failure in the end again. And recovery mode (of any kernel version) stucks on “loading initial ramdisk” on Ubuntu 18.10 too.

I’m not much of an expert but I guess that some recent updates in Ubuntu packages are seriously not compatible with my laptop and especially Nvidia messes up everything. I tried to find any solution I find but still no beam of hope… I’d be really appreciated if someone gives me a solution to get rid of the curse of “freezing red screen” and get me back on Ubuntu.

Thank you for reading my problem folks.

Composer install dependency error drupal/drupal dev-master

I’m managing my site dependencies via composer, most of the times works really well. Now I installed my site on a new server, using the exact same code-base as before (but with composer 1.8.0 instead of 1.7.x as before though). On running composer install I get the following error:

  • don’t install drupal/core 8.6.4|remove drupal/drupal dev-master
  • remove drupal/drupal dev-master|remove drupal/core 8.6.4
  • Installation request for drupal/drupal dev-master -> satisfiable by drupal/drupal[dev-master].
  • Installation request for drupal/core 8.6.4 -> satisfiable by drupal/core[8.6.4].

Usually I can solve these sorts of errors but this time I’m having a hard time. What’s the meaning of drupal/drupal dev-master, because usually you do not specify this anywhere directly?

Kalarm install problem and “is configured multiple times” error

I installed kalarm and got some errors, quoted below, and kalarm said it was unable to create the first alarm. Now “New” alarm is grayed out as well as some other options. Tried resetting to defaults and also removing and reinstalling but no change.

Errors installing kalarm:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target DEP-11-icons-small (main/dep11/icons-48×48.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target DEP-11-icons (main/dep11/icons-64×64.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target DEP-11-icons-hidpi (main/dep11/icons-64×64@2.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target DEP-11-icons-large (main/dep11/icons-128×128.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3 W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome-beta.list:3 and /etc/apt/sources.list.d/google-chrome.list:3

I have unlocked my bootloader but ADB doesn’t detect my phone so I cant get into my bootloader mode to install TWRP

I have a Huawei P10 lite and I wanted to root my phone, so I had unlocked my bootloader after much effort, and now I’m trying to install TWRP but every time i try to enter my bootloader mode it doesn’t detect my phone. While my phone is on normally my ADB and Fastboot detects my phone perfectly. Only when I enter my phone into the fastboot mode does ADB not detect my phone Fastboot still works fine though. I have tried to install TWRP on my phone using other PC’s but all comes to the same result. Is there anything I can do to get my laptop to detect my phone. enter image description here As you can see while my phone on ADB find my phone details while it on, but when I try to enter bootloader options it no longer finds my phone. I’m pretty sure i unlocked my phone properly as every time I reset my phone it give me the “untrusted” message and in fastboot mode it says “phone unlocked”. Please any help would be appreciated

Thank you so much for your help.