Hello guys i have 2 issues with steam on ubuntu 25.10 First issue Steam app creating duplicates of games shortcuts in app launcher. And the second issue is problem with external drive.I have installed games on 2 drives main drive with system and second is external hdd drive. Every time i add the hdd drive to steam after reboot installed games and external disk disappear from steam. In Heroic Games launcher there is no problem and games run perfect enter image description here

I upgraded my machine from Ubuntu 24.04.3 LTS to Ubuntu 25.10 and i've been trying to install Solaar for mouse and keyboard basically i only need to see battery percentage for both nothing else.

I tried to install via different methods

1. https://launchpad.net/%7Esolaar-unifying/+archive/ubuntu/stable

Command: sudo add-apt-repository ppa:solaar-unifying/stable

Error:

E: The repository 'https://ppa.launchpadcontent.net/solaar-unifying/stable/ubuntu questing Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

2. sudo apt install solaar

Error:

rules cannot access modifier keys in Wayland, accessing process only works on GNOME with Solaar Gnome extension installed
solaar: error: Traceback (most recent call last):
  File "/usr/share/solaar/lib/solaar/cli/__init__.py", line 217, in run
    raise Exception(
        'No supported device found. Use "lsusb" and "bluetoothctl devices Connected" to list connected devices.'
    )
Exception: No supported device found. Use "lsusb" and "bluetoothctl devices Connected" to list connected devices.

List of helpful topics: How do I install and configure the latest version of `solaar` to manage my Logitech wireless mouse or keyboard on Linux Ubuntu?

https://pwr-solaar.github.io/Solaar/installation/

Both keyboard and mouse are connected via bolt receiver not bluetooth.

Is there any alternative that i can use/install to display the keyboard/mouse battery.

This is really hunting me down

I have a older IMac 21 inch model from around 2020 currently running a fresh install of ubuntu desktop. My wifi device, which has a PCI ID of [14e4:4464] (rev 3) (found using lspci -nn -d 14e4:) does not work, my bluetooth does work however. Currently I am using USB tethering for network, but I would like to run a web server off this machine in the future. If needed I am also fine with doing a second fresh install of Ubuntu, although I would prefer not to.

My reason for posting this question which is similar to this is the line within the answer "If you have a Broadcom card that has a different pci.id, please ask a new question. Once solved, the solution will be added to this howto." my pci id is different and I was not able to find another solution on this forum that has worked.

I'm seeking assistance with a very stubborn hardware acceleration issue on a new Mini PC running an Intel Processor N150 (Alder Lake-N) on Ubuntu Server 24.04.3 LTS (Kernel 6.8.x).

I am trying to run Jellyfin in a Docker container with Quick Sync Video (QSV) enabled. Despite extensive troubleshooting, the VAAPI driver fails to initialize, which results in the Jellyfin container constantly crashing.

1. Hardware Status (Confirmed Working)

   • CPU: Intel N150 (Alder Lake-N)
   • Problem ID: PCI ID 8086:46d4 (Confirmed via lspci)

   Host Ready: I have confirmed that the iGPU is active by plugging in a monitor, and the required device file is created: ls /dev/dri shows card0 (but NO renderD128).

2. Diagnosis Details (The Problem)

   When attempting to diagnose the VAAPI drivers on the host (with LIBVA_DRIVERS_PATH set), I get consistent errors, proving the current Ubuntu drivers are incompatible:

   Driver Tested   Command Output  Diagnosis
   i965 (Old)  libva error: ... i965_drv_video.so init failed  Driver too old for Alder Lake-N.
   iHD (New)   unsupported drm device by media driver: simp    Current iHD driver/firmware conflicts with the N150 kernel implementation.
   

3. Docker Failure

   When running the Jellyfin container with the necessary flags (--device /dev/dri:/dev/dri, --cap-add=SYS_RESOURCE), the container immediately crashes with Exit Code 139 (Segmentation Fault) during VAAPI initialization.

The Question:

Has anyone successfully achieved stable VAAPI/QSV hardware transcoding in a Docker container on the Intel N150/N100 (Alder Lake-N) using Ubuntu 24.04 LTS?

If so, please share:

• Which specific kernel version (uname -r) are you running?
• Which VAAPI driver version are you using (if known)?
• Your working docker run command (or Compose file).

I am willing to try installing newer kernels or backported Intel drivers if a proven solution exists. Thank you!

I recently upgraded my laptop to Ubuntu 24.04 LTS (Noble Numbat), and since then, I’ve been facing a strange issue. Whenever I suspend my system and then resume, it either freezes completely or the screen remains black with only the cursor visible.

Here are my system details:

OS: Ubuntu 24.04 LTS x86_64 Kernel: 6.8.0-36-generic GPU: NVIDIA GeForce GTX 1650 Drivers: nvidia-driver-550 (proprietary) Desktop: GNOME 46 (Wayland)

I’ve tried a few things, but nothing seems to help:

Reinstalled the NVIDIA driver

sudo apt purge nvidia-* sudo apt install nvidia-driver-550

Switched between Wayland and Xorg sessions.

Disabled hybrid graphics and used only the NVIDIA GPU via:

sudo prime-select nvidia

Checked logs using:

journalctl -b -1 | grep -i nvidia

and found multiple lines like:

NVRM: Xid (PCI:0000:01:00): 79, pid=1832, GPU has fallen off the bus

It seems to be a driver issue but I’m not entirely sure. Before downgrading, I wanted to know if anyone else has faced similar freezing problems after suspend/resume with Ubuntu 24.04 and NVIDIA 550 drivers.

I also tried adding kernel parameters in /etc/default/grub like:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"

and then ran:

sudo update-grub

But the issue still persists.

Questions:

Is this a known bug in the 550 series drivers on Ubuntu 24.04?

Would switching to the open-source nouveau driver help temporarily?

Is there a way to automatically restart the NVIDIA driver on [resume to avoid a full system][4] freeze?

Any help, logs to check, or [workaround suggestions][5] would be much appreciated.

Additional Info (from dmesg):

[ 645.812382] NVRM: GPU 0000:01:00.0: GPU has fallen off the bus. [ 645.812392] NVRM: A GPU crash dump has been created. If possible, run [ 645.812394] NVRM: nvidia-bug-report.sh to collect this data before rebooting.

What I’ve noticed: If I switch to Intel graphics (sudo prime-select intel), suspend/resume works perfectly fine. So this definitely seems to be NVIDIA related.

TL;DR

Ubuntu 24.04 + NVIDIA 550 drivers → system freezes after suspend/resume. Tried reinstalling, kernel parameters, and switching display servers — no luck so far.

after upgrading to 25.10, when I check the graphical drivers, I get a strange configuration, saying that my system is using «manually installed» drivers, and I can not select the other «official» drivers. To you have any idea of how I should proceed to get the right nvidia drivers ? Thanks.

rip chatgpt, cant compile this gpt gives me invalid packs. im on kubuntu 25.10

https://pastebin.com/B4RgA0ED

I have a VM built with Vagrant, based on bento/ubuntu-24.04 that I can give to people with Windows and Mac OS using VMWare as a provider (VMWare Workstation ono Windows and VMWare Fusion on Mac OS). VirtualBox is not available for Mac OS, and to be able to give the same system to everyone using my VM, I also want to provide via VMWare in Linux.

But I have not been able to set up VMWare Workstation, for use with Vagrant, on a Ubuntu 24 laptop. Not with version 17.5.2, not with 17.6.4, and not with 25h2. The message that keeps coming back on all of them is

==> default: Cloning VMware VM: 'bento/ubuntu-24.04'. This can take some time...
An error occurred while executing `vmrun`, a utility for controlling
VMware machines. The command and output are below:

Command: [ "-T", 
           "player", 
           "snapshot", 
           "/home/amwink/.vagrant.d/boxes/bento-VAGRANTSLASH-ubuntu-24.04/202508.03.0/amd64/vmware_desktop/ubuntu-24.04-amd64.vmx", 
           "80ae4d15-cfca-454e-b64e-0f3449e16acd", 
           {:notify=>[:stdout, :stderr]} ]

Stdout: Error: The operation is not supported
Stderr: 

The problem, as far as I can figure out, is that Vagrant insists to call VMWare in "player" mode, which is either

1. not the right mode for use in Vagrant
2. not a mode that is available in my VMWare installation (just installed 25h2 from the bundle, with vmnet and vmmon running)

or neither of those two.

I have looked in different places to see if "player" could be forced to "ws" but it does not seem to be in the Vagrant settings, not in the plugin settings, not in VMWare Workstation itself or in the bento/ubuntu-24.04 configuration.

Does anyone know if this can be made to work?

I use Lubuntu 22.04.5 LTS on a Medion Akoya E4251 laptop connected with a Wacom CTH-460 pen & touch tablet.

Because I hate using mouses (RSI!) and also the touchpad as a substitute for a mouse, I use a Wacom CTH-460 pen & touch tablet's pen instead of a mouse, I disabled the touch part on the Wacom with a script that tells the device "Wacom Bamboo 2FG 4x5 Finger touch" to switch the touch part off so it won't interfere with the pen when my hand touches the surface of the tablet when using the pen. In conjunction with the pen on the Wacom tablet I also use the touchpad of my laptop just for two finger scrolling which I find very convenient, I disabled the other options for the touchpad so they do not interfere with the Wacom.

Recently the Wacom began to give me trouble because it kept on reacting again on touch. When I called the script to disable the touch on the tablet, it would not disable the touch. The reason for the failing of this script is because the device that I used in the script "Wacom Bamboo 2FG 4x5 Finger touch" can't be found anymore.

This is the script that I call for toggling the touch function of the Wacom:

#!/bin/bash -x

## Get the "Device name" or ID number
## for touch from 'xsetwacom list dev'

DEVICE="Wacom Bamboo 2FG 4x5 Finger touch" 
TOUCH_STATE=`xsetwacom get "$DEVICE" touch`
if [ "$TOUCH_STATE" == "on" ]
  then
    echo "Touch is ON, turning OFF."
    xsetwacom set "$DEVICE" touch off
  else
    echo "Touch is OFF, turning ON."
    xsetwacom set "$DEVICE" touch on
fi

The trouble seemed to start after I applied a fix for the touchpad of my laptop that suddenly refused to work and I fixed it by using the fix given on https://github.com/lxqt/lxqt-config/issues/644 : (/etc/X11/xorg.conf.d/40-libinput.conf):

Section "InputClass"
   Identifier "Tuxedo1704 Touchpad"
   Driver "libinput" # <-- "synaptics" is unsupported
   MatchIsTouchpad "on"
   Option "Tapping" "on"
   Option "TappingButtonMap" "lrm"
   Option "ScrollMethod" "two-finger"
   Option "NaturalScrolling" "true"
EndSection

I also gave the above configuration file a higher number (120) to be sure that it will be preferred over possible other touchpad configs, but it made no difference.

Because I thought that this fix did interfere with the Wacom touch part I also tried another fix for the touchpad on the laptop, but to no avail: (/etc/X11/xorg.conf.d/100-touchpad.conf)

Section "InputClass"
        Identifier "libinput touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
EndSection

Still "Wacom Bamboo 2FG 4x5 Finger touch" is not listed when I do

xsetwacom list

this is the result.

Wacom Bamboo 2FG 4x5 Pen stylus         id: 10  type: STYLUS    
Wacom Bamboo 2FG 4x5 Pad pad            id: 12  type: PAD       
Wacom Bamboo 2FG 4x5 Pen eraser         id: 16  type: ERASER

At the moment I am stuck and want help, who can point me to a solution that disables the touch part on the Wacom?

I got a spam of these errors:

Oct 31 15:43:21 vland-Z890-AORUS-ELITE-WIFI7 kernel: ACPI Error: AE_NOT_FOUND, while evaluating GPE method [_L6B] (20240827/evgpe-511)
Oct 31 15:43:21 vland-Z890-AORUS-ELITE-WIFI7 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_GPE.AL6B.WAK0], AE_NOT_FOUND (20240827/psargs-332)
Oct 31 15:43:21 vland-Z890-AORUS-ELITE-WIFI7 kernel: ACPI Error: Aborting method \_GPE.AL6B due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Oct 31 15:43:21 vland-Z890-AORUS-ELITE-WIFI7 kernel: ACPI Error: Aborting method \_GPE._L6B due to previous error (AE_NOT_FOUND) (20240827/psparse-529)

Do I update my BIOS or do I downgrade my kernel or what?

My motherboard is the Gigabyte Aorus Elite Z890 wifi7 with an Intel 7 265K processor.

Exact OS version: Ubuntu 24.04.3 LTS.

When I Launch Software Updater, I find 2 main categories of software updates available:

• Security updates
• Other updates

I want to deselect some of the items under the Other updates category, but if I click the checkbox near one of those, the whole tool becomes unresponsive and the mouse cursor switches to "spinner-mode". It hangs like this for minutes, and it does not really deselect the item.

What steps should I try to fix this ?

I need help while setting up my Ubuntu 22.

I am having a hard time finding all the packages for PetaLinux (Getting Started with PetaLinux) to install.

Can somebody help ?

Chrome states it is out of date. I press the update button and the .deb file is downloaded but I don't know where to continue from there. Many thanks, Stan

Ubuntu 24.04 OS

Please advise which will be an ideal screenrecorder for screen recording ?

I have the default "Take a screen" app which can record screen without audio. The file format is webm. I don't mind without audio but the webm video is jumping while editing it on OpenShot, difficult to control.

I also tried installing "SimpleScreenRecorder" but it can't work on the X-window of Ubuntu 24.04

Please help. Thanks in advance.

Regards

Imagine I'm on a bad connection. Suddently snapd flares up and starts downloading hundred of megabytes of updates I don't need right now.

It does not bother to announce it, even though system notifications exist - I discover that via iotop. The question is - how do I tell snap to never download anything until further notice?

It seems to be hostile to the idea, to the extent that systemctl stop snapd hangs - it clearly considers its desire to saturate my internet connection is paramount to me wanting it to stop right now as a super user.

Existing answers circle around stopping and masking the service, but the problem is, firefox cannot do most file operations when snapd is offline, and won't even start if snapd is not running.

So the question is, how to tell snapd to stop auto-updating via network without getting rid of it completely? I also know there is --hold, but the problem is, I neither know nor care what specific package is it going to download.

I am a new to Ubuntu (unix).

I have installed pytubefix using:

pipx install pytubefix

After installing, successful and globally available messages also displayed.

However, when I try to import pytubefix at python3 prompt, it get:

ModuleNotFoundError: No module named 'pytubefix'

Setup:

• ubuntu 25.10
• python 3.13.7
• pytubefix 10.1.1

My first q here & a noob to Linux/Ubuntu - be merciful...

When I query my early-2013 MacBook Pro via the CLI using

cat /sys/class/power_supply/BAT0/uevent | grep -i capacity | cut -d'=' -f2

I get a number that is a few units lower than what I see in the Gnome system tray.

I'm on Ubuntu 24.04, all updates current as per my 'Pro' subscription.

Anyone know why this is? Perhaps a timing or method issue in terms of how Gnome obtains its info?

update (Oct 30)

If you install/run CLI system monitor btop you'll see the same: a battery charge level several % lower than Gnome reports in the system tray.

I have written a bash script that runs as a cron job to pop a notification to the user to either plug in or unplug based on whatever numbers you enter to define your battery's happy place - if anyone is interested (if appropriate here), happy to share - it's about 30 lines and a couple lines for crontab.

The backstory is that once I got done with the hill-climb of Linux installation/config and started using my MBP to do real work, the first thing I noticed is how power-hungry Linux seems to be, even on 'Power Saver'.

Firefox is a big offender (+10W or more), but one that's hard to work around unless one is ready for browser migration. That said, I don't have this problem running Catalina on the other side of the dual-boot world.

update 2 (Oct 30)

Back to the original question of why the Gnome system tray battery charge differs from what some other system tools report, I wonder if it has to do with this issue:

https://maniacx.github.io/Battery-Health-Charging/polkitbug

I spent the morning installing this extension today (another long, somewhat complicated, but ultimately successful venture) & it occurred to me 2.5 min could be about right for queries by different methods to produce different charge numbers.

As an aside, my laptop's operating temp has settled down noticeably since adding the Battery Health Charging Gnome extension, as it obviously negates the charge/discharge cycle I was in while plugging/unplugging to try to keep the battery in a happy place. If anyone wants the step-by-step, I'll add it in - configuring applesmc-next and polkit were the two complications, but not too hard to work through.

I've since noticed:

cat /sys/class/power_supply/BAT0/uevent | grep -i capacity | cut -d'=' -f2

and

$ upower -i $(upower -e | grep 'BAT')

yield different results - no idea which is most accurate or which might be a delayed or adjusted figure.

I'm trying to clip an mkv for further processing and hit a snag:

ffmpeg -ss 02:09:42 -t 00:00:00 -i -bsf:v h264_mp4toannexb "input.mkv" -vcodec copy -acodec copy output3.avi

returns

-bsf:v: Protocol not found
Did you mean file:-bsf:v?

How to fix?

I understand that the purpose of /run/keystore/rpool is to provide the system.key file to ZFS via the keylocation property. However, once this task is complete, why is system.key still mounted? Wouldn't it be far safer to umount the file system and close the crypt device?

For example:

➜  ~ sudo umount /run/keystore/rpool                                                                   
➜  ~ sudo cryptsetup close keystore-rpool

Is there a technical reason why this file needs to remain available for reading after the boot is complete?

I am using I am using ubuntu-24.04.3-live-server-arm64 on my macOS and installed a desktop. I tried gnome, xfce and kubuntu and the audio stutters whenever I play a video in the virtual machine. I've tried changing changing up some settings like disabling the sound card and changing the hard disk but nothing. I also installed pavucontrol and VMware tools hoping it would work and it stills stutters. I also looked into the .vmx file to see if that was the problem everything seems fine

What can I do to fix it. Do I need to install something through the VM to make the audio run smoothly?

Advice on this topic would be appreciated I am new to this

I have attempted to dual boot Ubuntu alongside Windows 11 on my Acer Spin-5 laptop. Everything seemed fine and dandy at first; I created a live USB, installed Ubuntu, and it actually booted up without the USB and was working!

This is where the trouble began. At some point when I was away from the computer, it had been turned off. I'm not sure if it was a hard shut-down (like holding the power button) or if the computer had been turned off from in the software, however on reboot, Linux started displaying the "Minimal Bash-like" error which I've seen is very common. I also loaded windows and noticed that it had gone into recovery mode.

I have tried several approaches to try to fix this myself, but not a single online or posted fix has worked for me thus far.

The following is what I've tried in order:

1. Tried using boot-repair in the live USB, however the only option boot repair gave me was to make a report. It didn't seem to even recognize a problem.
2. Checked my Partitions (Linux System is in /dev/sba5 with 40G of space.)
3. I used a guide specifically for Acer spin-5 laptops to install Ubuntu, which is apparently tricky. The guide said that I would need to change the SATA mode to AHCI through Windows Command prompt, which I did, however this did not help the installation either.
4. I attempted the method of mounting a root partition using sudo mount to my /dev/sba5 partition and installing grub, however this did not seem to work either (I have a UEFI system).
5. I attempted to simply reinstall Linux using the live USB, however where the installer should have had the option to re-install Linux, it only gave me the options to erase disk, install alongside Windows, and something else.
6. Finally I simply tried deleting the partition /dev/sba5, the Linux System File, using fdisk so I could just completely start over, however fdisk didn't recognize the partition even existing.

At this point I'm not sure where to go from here and I really appreciate any help that I might get. I will continue to update this thread as I try different solutions and receive feedback as what to try. Thanks so much for reading and any advice that you may give! :)

Resources

• Acer guide: https://community.acer.com/en/discussion/comment/876353/#Comment_876353

• Bash-like error fix: https://www.linuxfordevices.com/tutorials/ubuntu/fixed-minimal-bash-like-line-editing-is-supported-error

• Reinstalling Linux: https://itsfoss.com/reinstall-ubuntu/

Updates:

• I tried typing exit into the minimal prompt however no error message appeared. The computer just seemed to restart and boot directly into the minimal prompt as it did before. Thanks user68186 for the first attempt lol! :)
• So I think the problem may be a result of either not having all the files required to boot present on my disk or perhaps it may be bad file locations, as in GRUB doesn't know where to look to load the kernel. The following are my partitions accessed through my live USB and there will be a picture of the set command while in GRUB.

ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/loop0: 2.33 GiB, 2502324224 bytes, 4887352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 61.89 MiB, 64901120 bytes, 126760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 155.63 MiB, 163188736 bytes, 318728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 248.76 MiB, 260841472 bytes, 509456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 45.86 MiB, 48087040 bytes, 93920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 43.63 MiB, 45748224 bytes, 89352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 81.26 MiB, 85209088 bytes, 166424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: HFS256G39TND-N21
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D1FF29AD-6B22-4C76-A90D-2203D0A78407

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    206847    204800   100M EFI System
/dev/sda2     206848    239615     32768    16M Microsoft reserved
/dev/sda3     239616 414169586 413929971 197.4G Microsoft basic data
/dev/sda4  498020352 500117503   2097152     1G Windows recovery environment
/dev/sda5  414171136 498020351  83849216    40G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 3.75 GiB, 4026531840 bytes, 7864320 sectors
Disk model: UDisk           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 18929DE9-0851-4C8A-8A1B-CE3271B13118

Device     Start     End Sectors  Size Type
/dev/sdb1   2048 7864286 7862239  3.7G Microsoft basic data


Disk /dev/loop8: 284 KiB, 290816 bytes, 568 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I wanted to re-install Ubuntu (dual boot with Win10) to have it on a larger partition (ran out of space beforehand). To do this, I have changed the boot order to have it boot directly to Win10, and then I deleted and merged the partition with the Win10 partition. I have also deleted the ubuntu boot folder via Diskpart (as explained here).

Then, I created a new (larger, 100GB) partition and created a live USB with the latest 20.04 release from the Ubuntu website, but when I boot from this USB I do not get the 'install ubuntu' option. The only options are (similar to this):

• Ubuntu
• Ubuntu (safe graphics)
• OEM install (for manufacturers)
• Boot from next volume
• UEFI firmware settings

So, the things I have tried didn't work, and I was curious if anyone here has another suggestion as to what may help me install my dual boot. Things I tried:

• Disabled secure boot
• Disabled fast startup
• Tried creating live USB with Rufus and Universal USB Installer
• Tried all options, the first three give me a black screen and the fourth boots to Win10, fifth goes to UEFI
• Tried to manually boot into the three available EFI files on the live USB (BOOTx64.efi, grubx64.efi, mmx64.efi)
• Looked for booting in legacy mode (as suggested here) but my UEFI doesn't show this option

Additionally, in the UEFI the only option it gives next to the Windows Bootloader is booting from the USB itself, which usually should get me to the 'install Ubuntu' option.

I have no idea what to try next, but my friend suggested that somehow the USB may think that a version of Ubuntu is still installed (maybe some remnants from the deleted install?), and will therefore try to boot it but can't find it, hence the black screen. Please let me know if you have any suggestions!

Laptop is an Asus ZenBook Flip 15.

Ubuntu18.04, GPU GeForce 2070S

I upgraded GPU driver from 460 to 470, using commands:

sudo apt-add-repository -r ppa:graphics-drivers/ppa
sudo apt remove nvidia*
sudo apt autoremove
sudo ubuntu-drivers autoinstall

after reboot, no networks and bluetooth ;(

> ping 8.8.8.8
connect: Network is unreachable

> sudo service networking status
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2021-09-23 23:56:31 CST; 24h ago
     Docs: man:interfaces(5)
  Process: 9891 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo (code=exited, status=0/SUCCESS)
  Process: 9972 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
  Process: 9962 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=1/FAILURE)
 Main PID: 9972 (code=exited, status=0/SUCCESS)

9月 23 23:56:31 fey-pc systemd[1]: Starting Raise network interfaces...
9月 23 23:56:31 fey-pc systemd[1]: Started Raise network interfaces.

> sudo service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:bluetoothd(8)

> sudo ifconfig -a
br-0edafad07ad9: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.19.0.1  netmask 255.255.0.0  broadcast 172.19.255.255
        inet6 fe80::42:2ff:fedf:94e2  prefixlen 64  scopeid 0x20<link>
        ether 02:42:02:df:94:e2  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 331  bytes 48011 (48.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-ab415028e09a: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:18:4f:89:44  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:cc:31:62:ec  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 71164  bytes 47374312 (47.3 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 71164  bytes 47374312 (47.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I check apt log

> less /var/log/apt/history.log

Start-Date: 2021-09-23  22:48:59
Commandline: apt remove nvidia*
Requested-By: fey (1000)
Remove: nvidia-kernel-common-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-modprobe:amd64 (384.111-2), nvidia-utils-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-prime:amd64 (0.8.16~0.18.04.1), nvidia-dkms-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-compute-utils-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-driver-440:amd64 (450.119.03-0ubuntu0.18.04.1), nvidia-driver-450:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-driver-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-kernel-source-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-settings:amd64 (470.57.01-0ubuntu0.18.04.1)
End-Date: 2021-09-23  22:49:15

Start-Date: 2021-09-23  22:49:25
Commandline: apt autoremove
Requested-By: fey (1000)
Remove: libdrm-nouveau2:i386 (2.4.101-2~18.04.1), libnvidia-compute-460:i386 (460.91.03-0ubuntu0.18.04.1), libnvidia-encode-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-encode-460:i386 (460.91.03-0ubuntu0.18.04.1), xserver-xorg-video-nvidia-460:amd64 (460.91.03-0ubuntu0.18.04.1), libpciaccess0:i386 (0.14-1), libnvidia-gl-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-gl-460:i386 (460.91.03-0ubuntu0.18.04.1), libgl1:i386 (1.0.0-2ubuntu2.3), libnvidia-fbc1-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-fbc1-460:i386 (460.91.03-0ubuntu0.18.04.1), libelf1:i386 (0.170-0.4ubuntu0.1), libnvidia-decode-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-decode-460:i386 (460.91.03-0ubuntu0.18.04.1), linux-headers-5.3.0-53-generic:amd64 (5.3.0-53.47~18.04.1), libnvidia-cfg1-460:amd64 (460.91.03-0ubuntu0.18.04.1), dkms:amd64 (2.3-3ubuntu9.7), libdrm-amdgpu1:i386 (2.4.101-2~18.04.1), libllvm10:i386 (1:10.0.0-4ubuntu1~18.04.2), libnvidia-ifr1-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-ifr1-460:i386 (460.91.03-0ubuntu0.18.04.1), libglx0:i386 (1.0.0-2ubuntu2.3), libgl1-mesa-dri:i386 (20.0.8-0ubuntu1~18.04.1), screen-resolution-extra:amd64 (0.17.3), libxdamage1:i386 (1:1.1.4-3), linux-headers-5.3.0-53:amd64 (5.3.0-53.47~18.04.1), libedit2:i386 (3.1-20170329-1), libdrm-intel1:i386 (2.4.101-2~18.04.1), libdrm-radeon1:i386 (2.4.101-2~18.04.1), libnvidia-common-460:amd64 (460.91.03-0ubuntu0.18.04.1), libatomic1:i386 (8.4.0-1ubuntu1~18.04), libnvidia-extra-460:amd64 (460.91.03-0ubuntu0.18.04.1), libxcb-glx0:i386 (1.13-2~ubuntu18.04), libsensors4:i386 (1:3.4.0-4), libglx-mesa0:i386 (20.0.8-0ubuntu1~18.04.1)
End-Date: 2021-09-23  22:49:33

Start-Date: 2021-09-23  22:51:09
Commandline: apt-get install -o DPkg::options::=--force-confnew -y nvidia-driver-470 linux-modules-nvidia-470-generic-hwe-18.04-edge
Requested-By: fey (1000)
Install: libdrm-nouveau2:i386 (2.4.101-2~18.04.1, automatic), linux-image-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), libnvidia-compute-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-compute-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-encode-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-encode-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-kernel-common-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libpciaccess0:i386 (0.14-1, automatic), xserver-xorg-video-nvidia-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-gl-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-gl-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libgl1:i386 (1.0.0-2ubuntu2.3, automatic), libnvidia-fbc1-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-fbc1-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libelf1:i386 (0.170-0.4ubuntu0.1, automatic), libnvidia-decode-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-decode-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-cfg1-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-utils-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-prime:amd64 (0.8.16~0.18.04.1, automatic), libdrm-amdgpu1:i386 (2.4.101-2~18.04.1, automatic), libllvm10:i386 (1:10.0.0-4ubuntu1~18.04.2, automatic), linux-signatures-nvidia-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), linux-modules-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), nvidia-compute-utils-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), linux-modules-nvidia-470-generic-hwe-18.04-edge:amd64 (5.4.0-86.97~18.04.1), libnvidia-ifr1-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-ifr1-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-driver-470:amd64 (470.63.01-0ubuntu0.18.04.2), libglx0:i386 (1.0.0-2ubuntu2.3, automatic), libgl1-mesa-dri:i386 (20.0.8-0ubuntu1~18.04.1, automatic), screen-resolution-extra:amd64 (0.17.3, automatic), libxdamage1:i386 (1:1.1.4-3, automatic), libedit2:i386 (3.1-20170329-1, automatic), libdrm-intel1:i386 (2.4.101-2~18.04.1, automatic), libdrm-radeon1:i386 (2.4.101-2~18.04.1, automatic), libnvidia-common-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libatomic1:i386 (8.4.0-1ubuntu1~18.04, automatic), linux-objects-nvidia-470-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), libnvidia-extra-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libxcb-glx0:i386 (1.13-2~ubuntu18.04, automatic), libsensors4:i386 (1:3.4.0-4, automatic), nvidia-kernel-source-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-settings:amd64 (470.57.01-0ubuntu0.18.04.1, automatic), linux-modules-nvidia-470-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), libglx-mesa0:i386 (20.0.8-0ubuntu1~18.04.1, automatic)
Remove: libnvidia-compute-460:amd64 (460.91.03-0ubuntu0.18.04.1)
End-Date: 2021-09-23  22:52:01

Start-Date: 2021-09-23  23:26:26
Commandline: apt autoremove
Requested-By: fey (1000)
Remove: linux-modules-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-image-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1), linux-image-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-modules-extra-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1), linux-headers-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-hwe-5.4-headers-5.4.0-77:amd64 (5.4.0-77.86~18.04.1), linux-hwe-5.4-headers-5.4.0-78:amd64 (5.4.0-78.87~18.04.1), linux-headers-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1), linux-modules-extra-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-modules-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1)
End-Date: 2021-09-23  23:26:35

other info

> uname -r
5.4.0-86-generic

> dpkg -l | grep 'linux-' | grep '^ii'
ii  binutils-x86-64-linux-gnu                       2.30-21ubuntu1~18.04.5                           amd64        GNU binary utilities, for x86-64-linux-gnu target
ii  linux-base                                      4.5ubuntu1.6                                     all          Linux image base package
ii  linux-firmware                                  1.173.20                                         all          Firmware for Linux kernel drivers
ii  linux-generic-hwe-18.04                         5.4.0.81.91~18.04.73                             amd64        Complete Generic Linux kernel and headers
ii  linux-headers-5.4.0-81-generic                  5.4.0-81.91~18.04.1                              amd64        Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-18.04                 5.4.0.81.91~18.04.73                             amd64        Generic Linux kernel headers
ii  linux-hwe-5.4-headers-5.4.0-81                  5.4.0-81.91~18.04.1                              all          Header files related to Linux kernel version 5.4.0
ii  linux-image-5.4.0-81-generic                    5.4.0-81.91~18.04.1                              amd64        Signed kernel image generic
ii  linux-image-5.4.0-86-generic                    5.4.0-86.97~18.04.1                              amd64        Signed kernel image generic
ii  linux-image-generic-hwe-18.04                   5.4.0.81.91~18.04.73                             amd64        Generic Linux kernel image
ii  linux-libc-dev:amd64                            4.15.0-154.161                                   amd64        Linux Kernel Headers for development
ii  linux-modules-5.4.0-81-generic                  5.4.0-81.91~18.04.1                              amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-5.4.0-86-generic                  5.4.0-86.97~18.04.1                              amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-81-generic            5.4.0-81.91~18.04.1                              amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-nvidia-470-5.4.0-86-generic       5.4.0-86.97~18.04.1                              amd64        Linux kernel nvidia modules for version 5.4.0-86
ii  linux-modules-nvidia-470-generic-hwe-18.04-edge 5.4.0-86.97~18.04.1                              amd64        Extra drivers for nvidia-470 for the generic-hwe-18.04-edge flavour
ii  linux-objects-nvidia-470-5.4.0-86-generic       5.4.0-86.97~18.04.1                              amd64        Linux kernel nvidia modules for version 5.4.0-86 (objects)
ii  linux-signatures-nvidia-5.4.0-86-generic        5.4.0-86.97~18.04.1                              amd64        Linux kernel signatures for nvidia modules for version 5.4.0-86-generic
ii  linux-signed-generic-hwe-18.04                  5.3.0.62.115                                     amd64        Complete Signed Generic Linux kernel and headers (dummy transitional package)
ii  linux-sound-base                                1.0.25+dfsg-0ubuntu5                             all          base package for ALSA and OSS sound systems
ii  syslinux-common                                 3:6.03+dfsg1-2ubuntu0.18.04.2                    all          collection of bootloaders (common)
ii  syslinux-legacy                                 2:3.63+dfsg-2ubuntu9                             amd64        Bootloader for Linux/i386 using MS-DOS floppies

> lspci -vvv
...
22:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
    Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 10
    Region 0: I/O ports at f000 [size=256]
    Region 2: Memory at f7504000 (64-bit, non-prefetchable) [size=4K]
    Region 4: Memory at f7500000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
...

however, nvidia driver works well

> nvidia-smi
Sat Sep 25 00:43:24 2021       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.63.01    Driver Version: 470.63.01    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:26:00.0  On |                  N/A |
| 33%   36C    P8    21W / 215W |    572MiB /  7974MiB |      1%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2194      G   /usr/bin/gnome-shell               88MiB |
|    0   N/A  N/A      3776      G   /usr/lib/xorg/Xorg                233MiB |
|    0   N/A  N/A      4000      G   /usr/bin/gnome-shell              183MiB |
|    0   N/A  N/A      4890      G   ...AAAAAAAAA= --shared-files       10MiB |
|    0   N/A  N/A      5757      G   gnome-control-center                2MiB |
|    0   N/A  N/A     11742      G   ...AAAAAAAAA= --shared-files       40MiB |
+-----------------------------------------------------------------------------+

Thanks for your help

i am trying to emulate Ubuntu/arm64 inside the QEMU emulator. Hence i am following the Ubuntu wiki (https://wiki.ubuntu.com/ARM64/QEMU) but i am not able to run it. First i installed qemu:

$ sudo apt-get install qemu-system-arm qemu-efi

then i created two pflash volumes for UEFI:

 $ dd if=/dev/zero of=flash0.img bs=1M count=64
 $ dd if=/usr/share/qemu-efi/QEMU_EFI.fd of=flash0.img conv=notrunc
 $ dd if=/dev/zero of=flash1.img bs=1M count=64

and finally:

  $ sudo qemu-system-aarch64 -m 1024 -cpu cortex-a57 -M virt -nographic -pflash flash0.img -pflash flash1.img -drive if=none,file=xenial-server-cloudimg-arm64-uefi1.img,id=hd0 -device virtio-blk-device,drive=hd0 -netdev type=tap,id=net0 -device virtio-net-device,netdev=net0,mac=$randmac

Running this command it gave me two warnings:

WARNING: Image format was not specified for 'flash0.img' and probing guessed raw.
     Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
     Specify the 'raw' format explicitly to remove the restrictions.

WARNING: Image format was not specified for 'flash1.img' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.

Therefore to overcame the warnings i specified the disk format as format=raw:

sudo qemu-system-aarch64 -m 1024 -cpu cortex-a57 -M virt -nographic -drive file=flash0.img,format=raw,if=pflash -drive file=flash1.img,format=raw,if=pflash -drive if=none,file=xenial-server-cloudimg-arm64-uefi1.img,id=hd0 -device virtio-blk-device,drive=hd0 -device virtio-net-device,netdev=net0,mac=$randmac -netdev type=tap,id=net0

but i got:

W: /etc/qemu-ifup: no bridge for guest interface found
qemu-system-aarch64: -device virtio-net-device,netdev=net0,mac=: Property 'virtio-net-device.mac' doesn't take value ''

What should i do ?

Note: I do not need to boot Ubuntu/arm64 necessarily, any other linux distro (e.g Debian) is ok.

Could anyone please help me ? Thank you.

I'm trying to install Ubuntu Server 20.04 on a remote server. Problem is, I cannot attach a USB drive and the hosting provider does not allow me to mount ISO images, all I have is a pre-installed Ubuntu system.

To launch the Ubuntu server setup I followed the instructions in this article to add a grub menuentry so I can boot from the Ubuntu Server ISO. Here's the menuentry:

menuentry "Ubuntu 20.04 ISO" {
   set isofile="/root/ubuntu-20.04.1-live-server-amd64.iso"
   rmmod tpm
   loopback loop (hd0,2)$isofile
   linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile noprompt noeject toram
   initrd (loop)/casper/initrd
}

Now when I select this menu entry, the installer starts, creates a ramdisk, copies the contents of the ISO to memory and I get through the first few steps of the setup, until:

well great, how did the setup fail to discover my hard drive?

when I switch to the terminal and run lsblk I see that sda clearly exists and that sda2 is still mounted at /isodevice - which is unexpected, since the ISO was already copied to ramdisk. umount /dev/sda2 returns "target is busy", but it works with the -l option.

Even then, I get the same error on the guided storage configuration page. What am I missing here? What would prevent the setup from detecting my hard drive, even though lsblk can see it?

update:

I tried it with the legacy installer, as suggested by @elder-geek, using this grub menuentry:

menuentry "Ubuntu 20.04 legacy server ISO" {
    rmmod tpm
    set root=(hd0,2)
    set isofile="/root/ubuntu-20.04.1-legacy-server-amd64.iso"
    loopback loop $isofile
    linux (loop)/install/vmlinuz boot=install iso-scan/filename=$isofile noeject toram
    initrd (loop)/install/initrd.gz
}

With this setup I can boot the legacy installer and walk through the first few steps, but then I get stuck because the installer can't mount the cd-rom drive it expects. Seems like the legacy installer does not support the toram option (unlike casper) and therefore I can't use it to run the installer from RAM, which is a strict requirement if I want to install from an ISO file on a file system that is going to be destroyed during setup.

update: tried it with the 20.10 installer, same issue. lsblk and parted can see my disk from the installer's command line, but the guided storage configuration fails. I'm running out of ideas here...

filed a bug report on launchpad now...

My USB stick got corrupted. I am not even able to format it as it is not found properly by my OS (Ubuntu 16.04).

What I tried:

It is found by neither fdisk -l, lsblk nor gparted.

It is shown by lsusb:

> lsusb | grep Kingston
Bus 004 Device 016: ID 0951:16a2 Kingston Technology

Logs from dmesg after plugging the stick in:

>dmesg | tail -n 11
[55597.440104] usb 4-2: new SuperSpeed USB device number 16 using xhci_hcd
[55597.466711] usb 4-2: New USB device found, idVendor=0951, idProduct=16a2
[55597.466718] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[55597.466722] usb 4-2: Product: DTR30G2
[55597.466726] usb 4-2: Manufacturer: Kingston
[55597.466729] usb 4-2: SerialNumber: 001A92053B6ABE7181348774
[55597.467697] usb-storage 4-2:1.0: USB Mass Storage device detected
[55597.469243] scsi host32: usb-storage 4-2:1.0
[55598.512257] scsi 32:0:0:0: Direct-Access     Kingston DTR30G2          PMAP PQ: 0 ANSI: 6
[55598.513179] sd 32:0:0:0: Attached scsi generic sg2 type 0
[55598.539725] sd 32:0:0:0: [sdc] Attached SCSI removable disk

usb_storage module seems to be loaded properly:

>lsmod | grep usb_storage
usb_storage            69632  1 uas

gnome-disk-utility finds the USB stick but provides only few information and does not enable formatting it :

Any help appreciated, thanks!

EDIT: on udevadm monitor I get following lines after plugging it in:

KERNEL[1423.875373] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2 (usb)
KERNEL[1423.876930] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0 (usb)
KERNEL[1423.877165] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19 (scsi)
KERNEL[1423.877207] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/scsi_host/host19 (scsi_host)
UDEV  [1423.903359] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2 (usb)
UDEV  [1423.910198] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0 (usb)
UDEV  [1423.912942] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19 (scsi)
UDEV  [1423.914774] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/scsi_host/host19 (scsi_host)
KERNEL[1424.921326] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0 (scsi)
KERNEL[1424.921915] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0 (scsi)
KERNEL[1424.921973] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/scsi_disk/19:0:0:0 (scsi_disk)
KERNEL[1424.922006] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/scsi_device/19:0:0:0 (scsi_device)
KERNEL[1424.922215] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/scsi_generic/sg2 (scsi_generic)
KERNEL[1424.922354] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/bsg/19:0:0:0 (bsg)
UDEV  [1424.924056] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0 (scsi)
UDEV  [1424.925759] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0 (scsi)
UDEV  [1424.927960] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/scsi_disk/19:0:0:0 (scsi_disk)
UDEV  [1424.930430] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/scsi_device/19:0:0:0 (scsi_device)
UDEV  [1424.931232] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/scsi_generic/sg2 (scsi_generic)
UDEV  [1424.931308] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/bsg/19:0:0:0 (bsg)
KERNEL[1424.945962] add      /devices/virtual/bdi/8:32 (bdi)
KERNEL[1424.946102] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/block/sdc (block)
KERNEL[1424.947369] change   /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/block/sdc (block)
UDEV  [1424.947824] add      /devices/virtual/bdi/8:32 (bdi)
UDEV  [1424.992658] add      /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/block/sdc (block)
UDEV  [1425.004852] change   /devices/pci0000:00/0000:00:14.0/usb4/4-2/4-2:1.0/host19/target19:0:0/19:0:0:0/block/sdc (block)

I am a new user and please forgive my ignorance.

I have Ubuntu Server 16.04 and am having trouble with file sharing.

Mission - give my workgroup read, write and execute access to a common drive on a Standalone Server based on a user account.

Have spend a few hours trying the standard config and testing but can only write files as the user in which the share was created. Have tried changing file level permission and added the user as admin users in the Samba Config file.

Just am now confused, the lines in the config file include the following:

[GDrive]
comment = shared document drive
path = "/home/techo1/Shared Files/GDrive"
valid users = techo1 techo2 techo3
admin users = techo1 techo2 techo3
read only = no
browsable = yes
writeable = yes
public = yes
guest ok = yes
create mask = 0644
directory mask = 0755

Also have altered the setfacl to give permission for techo2 and techo2 to have rwx access and these list with getfacl.

Am trying to connect from windows 7 clients, but there will be some windows 10 clients.

Thanks for the opportunity to post a question for this issue.

Regards

I am trying to remove wine and all of its remnants. When I use dpkg-query -l '*wine*' it tells me I have rc wine-staging-i version 1.9.10 with i386 architecture installed, but when I try to remove it outputs E: Unable to locate package wine-staging-i . I am running ubuntu 14.04 on a samsung chromebook with an intel processor. I'm sure it's obvious, but I'm super new to all of this and have no idea what I'm doing. I just trial and error-ed myself to this point. I apologize for any formatting or phrasing errors.

I have a usb device ext4 file system, I manually mount it like this

  mount -t ext4 /dev/sda1  /mnt/sdcard1 

then change permissions manually to enable others to write to it.

What line should I use in fstab so that all users have read/write permissions on it..

I'm looking for a good code snippet manager, with syntax highlighting and search capabilities. Another important feature is the capability of changing the code area background color. I have tested some Adobe Air apps that had white background everywhere, which hurts my eyes.

I'm using KDE btw. I use Kate for coding, but I don't like it's snippet plugin.