Computer info:

• Dell XP 15 9560
• Ubuntu 20.04.3 LTS (yeah, I know)
• bootable USB with Ubuntu 24.04.3 LTS
• The disk has a small ext2 partition for /boot, the rest has been assigned to a logical volume group.

When I tried to boot after a power outage, it dropped to initramfs.

Neither blkid nor lsblk returned anything (the initramfs prompt is returned immediately).

This is odd. The initramfs prompt proves that at least partition one of the disk should be visible.

I ran a full hardware scan from the BIOS. It reported a problem with the batteries (which I removed when they started to swell) and with the integrated webcam (which I don't use anyway).  Even in thorough test mode the disk comes out clean.

I tried booting in recovery mode. There it complains that it cannot find volume group ubuntu-mate-vg. To me this suggests a VG corruption.

When I boot from a bootable USB (Ubuntu 24.04.3), there's no trace of the disk. It does not show up in lshw. When it is not visible, I cannot examine it further.

Any suggestions on how this is possible and how I might proceed?

PS Note that the disk is not detected in Ubuntu 24.04.3 LTS. So this is not just a old-version issue.

Ubuntu Studio 25.10.

I have a Mad Catz Rat 8+ mouse. This has a second scroll wheel that I use for the system volume control. It worked out of the box like that. After a reboot the volume control stopped working and I don't know why. This mouse is not supported in Piper. I'm at a loss. It's one of the reasons I love the mouse.

I checked it with xev in the terminal and it does work. Buttons 6 and 7 are the scroll wheel buttons that I use for the volume control. I can't get information that I can rely on how to remap the mouse wheel.

How to install the driver for DLink 131 wifi adapter in the latest version of Ubuntu?

Hopefully it isn't too difficult of an issue to fix? I'm just not sure where to start. The headset itself works fine, and the output from their speakers is functional. However, neither Ubuntu's native system nor Discord's detects the headset's microphone. Which, as you can imagine, is a bit of an issue! It worked previously on a Windows install, so I know it's not the headset itself. And the hive its connected to is functional, so I'm assuming I'm missing something that would allow it to recognize the device? However, it's a traditional jack headset, so it doesn't come with any drivers that I'm aware of, so I'm unsure what to look for?

Here's some of the general information:

    Headset = HyperX Cloud Alpha wired gaming headset (if I'm remembering correctly)

    OS = Ubuntu 24.04.3 LTS

    Firmware Version = 1616

    OS Type = 64-bit

    GNOME Version = 46

    Windowing System = Wayland

    Kernel Version = Linux 6.14.0-37-generic

    Hardware Model = ASUS ROG STRIX X670E-I GAMING WIFI

    Processor = AMD Ryzen 7 7800X3D x 16

    Graphics = AMD Radeon RX 7900 XT

    Graphics 1 = AMD Ryzen 7 7800X3D

    Memory = 32 GiB

    Disk Capacity = 4 TB

I have Ubuntu 25.10 installed and updated on my laptop. Sometimes out of nowhere, I lose the ability to select and close windows I have open, no matter if it's the browser I'm using or a window of the system itself (files, apps, definitions, etc.). I just lose the ability to close or properly use the open window.

When this happens, neither the wireless mouse or the "physical" laptop mouse works. The keyboard also presents malfunctions when this happens.

Thank you for your attention.

So, for a little context:

• I am still fairly new to Ubuntu

• I had to freshly install Ubuntu last night because Windows 11 finally stopped booting for me last night after plugging in the PC from a move for the first time?

While most things seem to be functioning fine and how I expect for an install (I've done this before on an old tablet laptop of mine for college), there are a few things that have me a bit worried.

For one, every once and awhile, especially when loading up an app, the computer seems to freeze momentarily and the fans kick up before calming down and continuing as normal. I wouldn't be so worried if it didn't seem so common at the moment? After all, I'm not loading up anything more intensive than Discord and Firefox right now and it happens even with something as simple as the Settings app. And this PC isn't an old or low-end one by any means, really.

Secondly, and more concretely of a problem, I did experience this upon boot the first two times while installing and updating the software. I'm not quite sure what's going on, but my guess is that something's up with the GPU and it's spamming enough errors to possibly slow down the system as a whole?

I'd appreciate the help in getting this up and working properly, since this is the only PC I have that I do frequent for work and college. Without it, I'd be in a bit of a pickle :(

Here's the current system info:

• OS = Ubuntu 24.04.3 LTS

• Firmware Version = 1616

• OS Type = 64-bit

• GNOME Version = 46

• Windowing System = Wayland

• Kernel Version = Linux 6.14.0-37-generic

• Hardware Model = ASUS ROG STRIX X670E-I GAMING WIFI

• Processor = AMD Ryzen 7 7800X3D x 16

• Graphics = AMD Radeon RX 7900 XT

• Graphics 1 = AMD Ryzen 7 7800X3D

• Memory = 32 GiB

• Disk Capacity = 4 TB

And here's a photo (pardon it's quality, I had to take it on my phone at night) of the error:

EDIT: Alright, with some further testing there certainly seems to be something of a problem going on. I've found I can't maintain Firefox, Discord, and Steam being open at the same time without one or two of them crashing. Upon opening just Steam and Text Editor, the Text Editor froze before Steam crashed & now Steam no longer opens at all without flickering in the sidebar while not displaying it's window what-so-ever.

I opened up System Monitor to watch things while testing and this is what I've managed to view that seems odd to me: Above is while just running Firefox & the System Monitor. I do seem to have some heavy CPU spikes, but I'm unsure why?

Above is what it looks like while Firefox, System Monitor, and Steam is open while steam fails to properly load. There seems to be some kind of pattern to it there. I'll admit, I'm getting a little frustrated since prior to all these issues, my PC hadn't had any major problems like this before being packed up to move for the holidays. :( I'm worried it could be something in the hardware being damaged, but I don't know where I'd even begin to look for something like that?

I routinely prepare screenshot graphs from my running activities as logged on Strava for input and analysis by an AI on the free plan of ChatGPT. There are substantial limitations for image upload and analysis with ChatGPT's free plan, currently it allows only 3 images for detailed analysis per 24 hour period and these images have a size limitation.

Currently I stitch the 3 required images together with GIMP, convert them to a single image, resize this image and then export the final image. Cumbersome...

How can I semi-automate this process using the Ubuntu command line, producing a small but clear image that can be easily analyzed by an AI? An example of 3 typical images / graphs is here, labelled on my system splits.png, power.png and HR.png:

I usually organize the taller image 'Power' to the left side and the remaining images stacked on top of each other on the right side...

I think this is a new feature, I can enter suspend on my Lenovo ThinkPad P14s either via GUI menu or:

sudo systemctl suspend -f

I know it is suspended because when in suspend the LED blinks slowly.

But then if I close the lid it wakes up! So if I suspend and close to put it into my backup, it wakes up.

I think I have found a workaround: if I close the lid very quickly after clicking to start suspend, then the sleep stays on. This seems to be because the sleep takes a few seconds to start, so if I close the lid before it starts, the lid close event must happen before the sleep and does not affect it. But I'r really rather avoid this unreliable gymnastic each time!

I think I have tried everything from How can I tell Ubuntu to do nothing when I close my laptop lid? but nothing helped including:

sudo sed -i '/HandleLidSwitch/d' /etc/systemd/logind.conf
echo 'HandleLidSwitch=ignore' | sudo tee -a /etc/systemd/logind.conf
sudo sed -i '/IgnoreLid/d' /etc/UPower/UPower.conf
echo 'IgnoreLid=true' | sudo tee -a /etc/UPower/UPower.conf

followed by reboot.

I also checked:

$ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP0      S0    *disabled
GPP1      S4    *disabled
GPP2      S3    *disabled
GPP5      S0    *enabled   pci:0000:00:02.1
GPP6      S4    *enabled   pci:0000:00:02.2
GP11      S4    *disabled
SWUS      S4    *disabled
GP12      S4    *enabled   pci:0000:00:04.1
SWUS      S4    *disabled
XHC0      S3    *enabled   pci:0000:64:00.3
XHC1      S4    *enabled   pci:0000:64:00.4
XHC2      S4    *disabled  pci:0000:66:00.0
NHI0      S3    *disabled
XHC3      S3    *enabled   pci:0000:66:00.3
NHI1      S4    *enabled   pci:0000:66:00.6
XHC4      S3    *enabled   pci:0000:66:00.4
LID       S4    *enabled   platform:PNP0C0D:00
SLPB      S3    *enabled   platform:PNP0C0E:00

and tried to disable them all with:

for d in `awk 'NR>1 && $3=="*enabled"{print $1}' /proc/acpi/wakeup`; do
  printf "$d\n" | sudo tee /proc/acpi/wakeup
done

and:

$ cat /sys/power/mem_sleep
[s2idle]

and it seems that deep sleep is not supported on my system?

$ echo deep | sudo tee /sys/power/mem_sleep
deep
tee: /sys/power/mem_sleep: Invalid argument (os error 22)

Logs after I start suspend: https://gist.github.com/cirosantilli/dfe4082c1cfd2b50d92638732cc84ce5

Shame that after all these years they still haveng figured out how to add a working setting for this on the main settings GUI...

The problem did not happen on my ThinkPad P51 on a fresh 25.10 install from ISO.

Related:

• Laptop wake up from suspend when lid is closed old, closed as dupe but it's not clear that it's an actual dupe

I want to istall ubuntu on my new laptop a honor magic book 14 pro with a ultra 5 125h processor.

Details:

-- Core Issue:

The Ubuntu installer fails to find the bootable medium (USB stick) after starting the boot process.

Error Message: "unable to find medium containing a live file system"

-- Initial Troubleshooting Steps:

BIOS Configuration: Secure Boot and Fast Boot have been disabled.

BIOS Limitations: The system BIOS is locked down and does not provide any settings to change the storage controller mode (e.g., no option to switch from Intel VMD/RST to AHCI).

Hardware Verification: The same bootable USB stick and ISO image were successfully used to boot another laptop, confirming the integrity of the installation medium. Different USB ports were also tested on the Honor laptop.

Firmware: Checked the official Honor support website; no BIOS updates are available for this model.

-- Tested Linux Distributions and Methods:

Ubuntu 24.04 LTS: Fails with the core error.

Ubuntu 25.04 (Daily Build): Fails with the exact same error, suggesting the issue is not resolved by a newer kernel (as of the date of testing).

USB Creation Method: The live USB was created using Rufus in both "ISO Image mode" and "DD Image mode," with neither method resolving the issue.

-- Tested Kernel Boot Parameters and Results: A series of kernel parameters were tested by editing the GRUB command line at boot.

nomodeset: No effect, still resulted in the "unable to find medium" error.

nvme_core.default_ps_max_latency_us=0: No effect, still resulted in the "unable to find medium" error.

intel_iommu=off: This changed the behavior. The system froze indefinitely at the graphical Ubuntu loading screen (with the logo spinner).

acpi=off: This also changed the behavior. The system froze at an early text-based stage, displaying only the message "booting a command list".

is there any way to fix this or do I just have to wait until this is adressed by honor or linux developers ?

Did I miss anything that might solve this problem ?

I'm trying to completely disable pipewire on an Ubuntu 24.04.2 machine. So far I have tried:

sudo systemctl --global disable pipewire.service
sudo systemctl --global disable pipewire.socket
sudo systemctl --global disable pipewire-pulse.service
sudo systemctl --global disable pipewire-pulse.socket
sudo systemctl --global disable wireplumber.service

I have also tried to disable it for an individual user:

systemctl --user disable pipewire.service
systemctl --user disable pipewire.socket
systemctl --user disable pipewire-pulse.service
systemctl --user disable pipewire-pulse.socket
systemctl --user disable wireplumber.service

However when I log in, even after a reboot, there are pipewire processes running. What am I missing? Is there some bit of config that needs to change?

I am trying to install Lubuntu 24.04 to old motherboard MSI J1900l (It's Intel SoC Celeron J1900). Previously, the CentOS system was installed on the computer. I checked installation with both values: UEFI and LEGACY+UEFI for parameter Boot mode select in BIOS And parameter Security boost is disabled.

I have downloaded iso (torrent from lubuntu.me) and made bootable USB stick with Rufus application. I can use this bootable USB stick as a Live USB. However, I cannot install Lubuntu on hard drive (SATA SSD) with it. The Lubuntu distro is installing with Calamares 3.3.5

Partitions:

Creating new GPT partition table on /dev/sda (Samsung SSD 750 EVO 120GB)...
Create new 300MIB partition on /dev/sda (Samsung SSD 750 EVO 120GB)
Set flags on 300MiB fat32 partition to boot
Create new 114168MIB partition on /dev/sda (Samsung SSD 750 EVO 120GB) with entries lubuntu_2404
Set up new fat32 partition with mount point /boot/efi
Install Lubuntu on new ext4 system partition

After reboot there is a grub command-line.

grub> ls
(proc) (memdisk) (hd0) (hd0,gpt2) (hd0,gpt1) 
grub> ls (hd0)
Device hdo: No known filesystem detected - Sector size 512B - Total size 117220824KiB
grub> ls (hd0,gpt2) 
        Partition hd0,gpt2: Filesystem type ext* - Label `lubuntu_2404' - .......
grub> ls (hd0,gpt1)
    Partition hd0,gpt1: Filesystem type fat, UUID .......

The following are parameters for bootloader@bootloader job in Calamares:

Key              Value
==============================================
efiBootLoader    grub
efiBootloaderid  ubuntu
fallback         /initramfs-linux-fallback.img
grubCfg          /boot/grub/grub.cfg
grubinstall      grub-install
grubMkconfig     grub-mkconfig
img              /initramfs-linux.img
kernel           /vmlinuz-linux
timeout          10

The installation failed with error:

The bootloader could not be installed. The installation command <pre>grub-install 
--target=x86_64-efi --efi- directory=/boot/efi --bootloader-id=ubuntu --force</ pre> returned 
error code 1.

So, I tried to run this command in terminal:

lubuntu@lubuntu:~$ grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntu --force
grub-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.

That's true. There are neither file modinfo.sh nor directory /usr/lib/grub/x86_64-efi The following is the content of the parent directory:

lubuntu@lubuntu:/usr/lib$ ls -1pr /usr/lib/grub
i386-pc/
grub-sort-version
grub-multi-install
grub-mkconfig_lib

There is also directory grub-legacy:

lubuntu@lubuntu:/usr/lib$ ls -1pr /usr/lib/grub-legacy/
update-grub

What am I doing wrong, and how to install lubuntu on my computer?

Additonal info

1.Partition info from fdisk:

lubuntu@lubuntu:~$ sudo fdisk /dev/sda
Welcome to fdisk (util-linux 2.39.3).
Command (m for help): p

Disk /dev/sda: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Samsung SSD 750 
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: D46C3C91-0455-4642-8631-D154BF70EE30

Device      Start       End   Sectors   Size Type
/dev/sda1    4096    618495    614400   300M EFI System
/dev/sda2  618496 234436544 233818049 111.5G Linux filesystem

2.lscpu output

lubuntu@lubuntu:~$ lscpu

Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          36 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   4
  On-line CPU(s) list:    0-3
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz
    CPU family:           6
    Model:                55
    Thread(s) per core:   1
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             3
    CPU(s) scaling MHz:   63%
    CPU max MHz:          2415.7000
    CPU min MHz:          1332.8000
    BogoMIPS:             4000.00
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnttsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow flexpriority ept vpid tsc_adjust smep erms dtherm ida arat vnmi

3.Symlinks

3.1 I tried to add symbolic link /usr/lib/grub/x86_64-efi pointing to the /usr/lib/grub/i386-pc like this question from lubuntu.me. However, it didn't work

3.2 I found modinfo.sh from a folder x86_64-efi with the following command:

find / -name modinfo.sh

Then I add a symbolic link /usr/lib/grub/x86_64-efi pointing to the found x84_64-efi directory. After I run the same command grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntu --force I have got an error failed to get canonical path of /boot/efi

I want to experiment with Ubuntu on a Lenovo laptop which has Manjaro installed (and nothing else, no Windows). I downloaded Ubuntu-24.04-desktop-amd64.iso on a Windows machine and burned it to a USB stick. After a lot of trouble I got the boot process to start on the Lenovo and fixed the black screen by typing e at the Try Ubuntu without installing option and replacing quiet splash with nomodeset, then F10 to boot. But now I am stuck with this message on the screen: EFI stub: Loaded initrd from LLINUX_EFI_INITRD_MEDIA_GUID device path What next please? EDIT 24 May 2024 - I never did solve the problem. I changed to a different machine and have stopped trying to use the Manjaro machine for Linux. I have wiped it, installed Windows, and will keep it for things that won't run on Linux.

Can you let me know what I am doing wrong to install the KVM in Virtual Machine Ubuntu that I see the error of "CPU does not support KVM extensions"?

I am running a Linux (Ubuntu 22.04.3 LTS) OS as a VM machine in VirtualBox (version 7.0) and My host machine is Windows 11 pro OS. My Virtualization is Enabled in the BIOS/UEFI of the host machine. I have turned off Hyper-V, Windows HyperVisor Platform, Virtual Machine Platform, and Windows Hypervisor Platform in the Windows Features. Then I have added the VM machine that trying to install KVM to the nested Virtualization by "VBoxManage modifyvm "YourVMName" --nested-hw-virt on" in my host PC. I have installed VM_VirtualBox_Extension_Pack-7.0.14 in Virtual Box.

I am trying to install Docker in my VM linux, for which I need the KVM. But after "sudo apt install qemu-kvm ovmf" it shows installed. But then after "sudo kvm-ok" I see the following error as KVM not supported in my machine:

"INFO: Your CPU does not support KVM extensions

KVM acceleration can NOT be used"

The linux architecture is in the following where KVM is also showed:

""Architecture: x86_64

CPU op-mode(s): 32-bit, 64-bit

Address sizes: 39 bits physical, 48 bits virtual

Byte Order: Little Endian

CPU(s): 4

On-line CPU(s) list: 0-3

Vendor ID: GenuineIntel

Model name: 11th Gen Intel(R) Core(TM) i9-11900 @ 2.50GHz

CPU family:          6

Model:               167

Thread(s) per core:  1

Core(s) per socket:  4

Socket(s):           1

Stepping:            1

BogoMIPS:            4991.99

Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc

                     a cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall n

                     x rdtscp lm constant_tsc rep_good nopl xtopology nonsto

                     p_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pci

                     d sse4_1 sse4_2 movbe popcnt aes rdrand hypervisor lahf

                     _lm abm 3dnowprefetch invpcid_single ibrs_enhanced fsgs

                     base bmi1 bmi2 invpcid rdseed clflushopt arat md_clear 

                     flush_l1d arch_capabilities

Virtualization features:

Hypervisor vendor: KVM

Virtualization type: full

Caches (sum of all):

L1d: 192 KiB (4 instances)

L1i: 128 KiB (4 instances)

L2: 2 MiB (4 instances)

L3: 64 MiB (4 instances)

NUMA:

NUMA node(s): 1

NUMA node0 CPU(s): 0-3

Vulnerabilities:

Gather data sampling: Not affected

Itlb multihit: Not affected

L1tf: Not affected

Mds: Not affected

Meltdown: Not affected

Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode;

                     SMT Host state unknown

Retbleed: Mitigation; Enhanced IBRS

Spec rstack overflow: Not affected

Spec store bypass: Vulnerable

Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer

                      sanitization

Spectre v2: Mitigation; Enhanced / Automatic IBRS, RSB filling, PBR

                     SB-eIBRS SW sequence

Srbds: Not affected

Tsx async abort: Not affected

""

Hello Ask Ubuntu users,

I installed Ubuntu 22.04.3 LTS on a Levono Ideapad 3 Chromebook. When installing it, I wasn't able to get the audio to work. I am assuming this is a driver issue. Does anyone have any idea on how to fix this problem?

More computer specs (If needed):

4GB - Memory Intel® Celeron(R) N4020 CPU @ 1.10GHz × 2 core - CPU Mesa Intel® UHD Graphics 600 (GLK 2)

Why does this error appear when I try to copy files from my Ubuntu partition to my Windows partition?

I'm trying to connect a Dell Dock station WD19S on my Ubuntu 22.04 laptop (my goal is to connect 2 external monitors to my laptop). Under Devices list, when I plug in a USB-C cable from the Dock station to my laptop, I see that Dell dock is listed, but the boltctl command is giving nothing.

I installed Displaylink drivers from this site (https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu), then followed this procedure (https://support.displaylink.com/knowledgebase/articles/1944022-how-to-install-displaylink-software-on-ubuntu-20-0) and finally rebooted my laptop, but the Dell dock station is still not recognized.

I installed Ubuntu 22.04.1 and it was working fine until after couple of restarts. Now, it no longer boots to a desktop environment. I get this black screen with login:

After entering the password it enters a directory and not the desktop.

xubuntu-desktop installs by default many non-latin fonts, which is great for asian or arabic users but clutters my (western-user) interface to pick a font in the fonts list.

So I did remove many fonts I never use:

sudo apt-get remove --purge fonts-beng fonts-beng-extra fonts-deva fonts-deva-extra fonts-gargi fonts-gubbi fonts-gujr fonts-gujr-extra fonts-guru fonts-guru-extra fonts-indic fonts-kalapi
  fonts-khmeros-core fonts-knda fonts-lao fonts-lklug-sinhala fonts-lohit-beng-assamese fonts-lohit-beng-bengali fonts-lohit-deva fonts-lohit-gujr fonts-lohit-guru
  fonts-lohit-knda fonts-lohit-mlym fonts-lohit-orya fonts-lohit-taml fonts-lohit-taml-classical fonts-lohit-telu fonts-mlym fonts-nakula fonts-navilu 
  fonts-orya fonts-orya-extra fonts-pagul fonts-sahadeva fonts-samyak-deva fonts-samyak-gujr fonts-samyak-mlym
  fonts-samyak-taml fonts-sarai fonts-sil-abyssinica fonts-sil-padauk fonts-smc fonts-smc-anjalioldlipi fonts-smc-chilanka fonts-smc-dyuthi fonts-smc-gayathri
  fonts-smc-karumbi fonts-smc-keraleeyam fonts-smc-manjari fonts-smc-meera fonts-smc-rachana fonts-smc-raghumalayalamsans fonts-smc-suruma fonts-smc-uroob fonts-taml
  fonts-telu fonts-telu-extra fonts-thai-tlwg fonts-tibetan-machine fonts-tlwg-garuda fonts-tlwg-garuda-ttf fonts-tlwg-kinnari fonts-tlwg-kinnari-ttf fonts-tlwg-laksaman
  fonts-tlwg-laksaman-ttf fonts-tlwg-loma fonts-tlwg-loma-ttf fonts-tlwg-mono fonts-tlwg-mono-ttf fonts-tlwg-norasi fonts-tlwg-norasi-ttf fonts-tlwg-purisa
  fonts-tlwg-purisa-ttf fonts-tlwg-sawasdee fonts-tlwg-sawasdee-ttf fonts-tlwg-typewriter fonts-tlwg-typewriter-ttf fonts-tlwg-typist fonts-tlwg-typist-ttf fonts-tlwg-typo
  fonts-tlwg-typo-ttf fonts-tlwg-umpush fonts-tlwg-umpush-ttf fonts-tlwg-waree fonts-tlwg-waree-ttf fonts-yrsa-rasa 
  fonts-noto-core fonts-noto-hinted fonts-noto-ui-core  fonts-noto-cjk

And thus my fonts list (in LibreOffice or Inkscape, a.o.) became much more useable, huray !

But this purge had the side-effect of removing xubuntu-default-settings (depending on fonts-noto-hinted), and thus xubuntu-core and xubuntu-desktop as well... meaning most of my software (including LibreOffice) is now on the apt autoremove list... so I can't clean my installs anymore.

How can I remove these non latin fonts while keeping the software stack of xubuntu-desktop untouched ?

I tried to reinstall xubuntu-desktop without recommended packages but to no avail (due to dependency on fonts-noto):

sudo apt-get install --no-install-recommends xubuntu-desktop

I also tried to Pin all these fonts to never install via adding to /etc/apt/preferences:

Package: <all fonts packages>
Pin: release *
Pin-Priority: -1

But my problem remained.

I updated ubuntu to the version 20.04 and before the update PHPmyadmin was working fine, there is blank screen and internal error 500. I have reinstalled and followed the instructions to install phpmyadmin on ubuntu 20.04, but it is not working, have some one same error? is there any solution? is there mandatory to have ssh installed?

Thank you!

I restarted my machine (Ubuntu 20.04 LTS on Dell XPS) and got the gnu grub 2.04 screen, instead of booting up my operating system normally. As far as I can tell, I didn't do anything weird to my grub config file.

I tried booting linux manually on grub, using the tutorial found here.

I found a bunch of different partitions in grub:

grub> ls
(proc) (hd0) (hd0,gpt2) (hd0,gpt1) (hd1) (hd2) (hd2,gpt2) (hd2,gpt1)

After looking inside each one, I determined that I should be booting from (hd2,2), since it contains my file system:

grub> ls (hd2,2)/
lost+found/ boot/ swapfile etc/ media/ var/ bin dev/ home/ lib lib32 lib64 libx32 mnt/ opt/ proc/
root/ run/ sbin snap/ srv/sys/ tmp/ usr/ cdrom/

I continued to follow the tutorial:

grub> set root=(hd2,2)
grub> linux /boot/vmlinuz-5.4.0-39-generic root=/dev/sdc2
grub> initrd /boot/initrd-5.4.0-39-generic
grub> boot

In line 2 I chose /dev/sdc2, following the instructions in the tutorial: "How do you know the correct partition? hd0,1 = /dev/sda1. hd1,1 = /dev/sdb1. hd3,2 = /dev/sdd2. I think you can extrapolate the rest." I extrapolated that hd2,2 = /dev/sdc2.

The system did not boot, instead giving the message:

Gave up waiting for root file system device. Common problems:
 - Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sdc2 does not exist. Dropping to a shell!

I am not sure what to do from here. Any help would be appreciated.

I have these users in MySQL

I want to connect to it remotely from my mac via SSH

I can't connect. I kept getting

2013 - Lost connection to MySQL server at 'reading initial communication packet', system error: 0 "Internal error/check (Not system error)"

I know if I did add this record below.

I will be able to connect, but it seems not very secure to do that. I thought we can connect to our database via SSH. Please correct me what I did wrong.

I don't have anything set in the local firewalls in my server, but I do that have networking firewall rules at Digital Ocean.

All rules configured

The DMA-API-HOWTO document says that dma_alloc_coherent() returns two values: the virtual address which you can use to access it from the CPU and dma_handle which you pass to the card.

Shouldn't the virtual address and the dma_handle map to the same physical address? That is not what I see.

Is it expected that the dma_handle is the same as its physical address?

I am using a x86_64 system with the IOMMU enabled. The OS is Ubuntu 18.04, and the kernel is 4.15.0-47-generic.

My code:

ret = dma_set_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(64));

dmabuffp = dma_alloc_coherent (dev_ptr, (size_t)4*1024*1024, &dma_hndl, GFP_KERNEL | GFP_DMA);

printk(KERN_INFO "init: dma_hndl = 0x%llX\n", dma_hndl);<br />
printk(KERN_INFO "init: dmabuffp VA = 0x%llX\n", (uint64_t)dmabuffp);<br />
printk(KERN_INFO "init: dma_hndl VA = 0x%llX\n", (uint64_t)bus_to_virt(dma_hndl));

printk(KERN_INFO "init: dmabuffp PA = 0x%010llX\n", (uint64_t)virt_to_phys(dmabuffp));<br />
printk(KERN_INFO "init: dma_hndl PA = 0x%010llX\n",(uint64_t)virt_to_phys(bus_to_virt(dma_hndl)));

After the module loads, dmesg shows this:

init: dma_hndl = 0xFFC00000<br />
init: dmabuffp VA = 0xFFFF888E9B000000<br />
init: dma_hndl VA = 0xFFFF88873FC00000<br />
init: dmabuffp PA = 0x085B000000<br />
init: dma_hndl PA = 0x00FFC00000

The device can write and read using dma_hndl, but the value it writes is not at *buffptr.

What am I missing and/or doing wrong?

I am using Ubuntu 18.04.1 version and now wants to use Windows 10 as well. I have downloaded WoeUSB to create bootable USB for Windows, but I'm getting the below error message when installing. Before this step I have formatted the USB as NTFS.

Installation failed!
Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
==============================
Mounting source filesystem...
mount: /media/woeusb_source_1533820829_2541: wrong fs type, bad option, bad superblock on /dev/loop8, missing codepage or helper program, or other error.
mount_source_filesystem: Error: Unable to mount source media
Error: Unable to mount source filesystem
Unmounting and removing "/media/woeusb_source_1533820829_2541"...
umount: /media/woeusb_source_1533820829_2541: not mounted.
cleanup_mountpoint: Warning: Unable to unmount "/media/woeusb_source_1533820829_2541".
Some mountpoints are not unmount/cleaned successfully and must be done manually
You may now safely detach the target device

So today I plugged in my 31 GB USB flash drive and opened it up. I was in the process of creating a Windows bootable device, when I tried to copy the files from my computer to the USB. I got an error message telling me I do not have permissions to add files.

• I added and removed partitions on the usb thousands of times
• I formatted it a bazillion times

And it seems I am unable to do the simple task of copying and pasting files.

I have passwords for the systems. I own the computer.

Why can't I copy files?

Formated it to ext2, fat32 and nfts: no results, same nonsense

I have been using Virtualbox to run mininet simulations. I have two adapters, eth0 uses NAT and has the IP address 192.168.56.1 and eth1 is a host only adapter. I can SSH into the VM using 192.168.56.1, however when I try to reach anything external to the network from the VM (for example cloning a git repository), I get the message network unreachable. I have tried pinging IP addresses directly to check that it is not a DNS issue. Why can I not reach the internet? I understand that a common issue is that an IP address has not been assigned to one of the adapters, but here eth0 quite clearly has an IP address.

ifconfig -a:

eth0      Link encap:Ethernet  HWaddr 08:00:27:ef:9b:c8  
          inet addr:192.168.56.101  Bcast:192.168.56.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:235 errors:0 dropped:0 overruns:0 frame:0
          TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:25042 (25.0 KB)  TX bytes:23566 (23.5 KB)

eth1      Link encap:Ethernet  HWaddr 08:00:27:76:c7:9a  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:432 errors:0 dropped:0 overruns:0 frame:0
          TX packets:432 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:34376 (34.3 KB)  TX bytes:34376 (34.3 KB)

After installing Ubuntu 17.04 with its bootloader in a patition (hd0,5), I was unable to boot it via EasyBCD 2.3.207 (my preferred bootloader). I have installed Ubuntu after Windows and don't want to use grub on MBR of first disk. I can boot Ubuntu by Super Grub Disk but when I try it by EasyBCD, either by automatically choosing or selecting the partition manually, it end up in Grub> prompt. The following commands are also not effective : Root=(hd0,5) chanloader +1 boot

Now I am in Grub rescue > prompt. Interestingly, I now can boot into Ubuntu by:
set prefix=(hd0,6)/boot/grub
set root=(hd0,6)
insmod normal
normal

This gives me the grub menu and I can choose any option therein. The problem is that it is impossible to do this every time for booting or use Super Grub Disk. How can I use BCDedit or EasyBCD or Neogrub bootloader to do this automatically (tried it unsuccessfully by manipulating the menu.lst file of Neogrub ).

Please help,

Thanks,

Tapas

I'm trying to install sextractor on a dual-booted Windows8.1/Ubuntu14.04 machine with i5 processor.

I'm following this guide on how to install ATLAS onto Ubuntu.

I always encounter the error:

../configure
make: `xconfig' is up to date.
./xconfig -d s /home/user/Programs/atlas/bld/../ -d b /home/user/Programs/atlas/bld 

OS configured as Linux (1)

Assembly configured as GAS_x8664 (2)

Vector ISA Extension configured as  AVXMAC (3,488)

Architecture configured as  Corei3 (28)

Clock rate configured as 3100Mhz

Maximum number of threads configured as  4
Parallel make command configured as '$(MAKE) -j 4'
CPU Throttling apparently enabled!
It appears you have cpu throttling enabled, which makes timings
unreliable and an ATLAS install nonsensical.  Aborting.
See ATLAS/INSTALL.txt for further information
xconfig exited with 1

The reported clock rate changes every time I run it!

I have no idea what to do...

I have the keyboard backlight turned on in bios to timer setting (1 second). When laptop boots the backlight works, but once ubuntu begins to load the backlights turn off.

There is a function key combo that is supposed to turn it on (Fn+Z), hitting that brings up a notification balloon showing the backlit keyboard icon but it is grayed out.

I tried using KeyTouch to try and get the backlight working but my laptop model isn't on the list.

I've read in forums that if you dual boot with windows 7, that doing a complete power cycle (or put to sleep/hibernate) while in windows 7 and restart into Ubuntu that the backlight will work. All information I've seen point to this being an ACPI issue. I've seen scripts to toggle the backlight from within ubuntu, but I don't know how to create/run scripts.

I'm new to Ubuntu, and have been searching the web and can't seem to find any answers that will work for my particular situation. Any information would be MUCH appreciated. Thanks!

Recently we upgraded from a windows 2003 DHCP server to a Ubuntu 10.04 DHCP3-server.

The problem I am faced with now is that my windows 7 clients are now getting IPv6 ip address along with the IPv4 address. This is creating a AAAA record in our windows DNS server. But when I switch back to the Windows DHCP server the address doesn't get assigned and no AAAA record is created in the DNS server.

I have set ddns-update-style none; and ignore client-updates

I can disable IPv6 on the computer it self but I would like to find out what the setting that will make the DHCP NOT assign a IPv6 address to w7 clients or disable auto-config for IPv6 on w7 pcs.

Thanks.

authoritative;
ddns-update-style none;
log-facility local7;
ignore client-updates;

subnet 192.168.1.0 netmask 255.255.255.0 {

        range 192.168.1.50 192.168.1.58;
    default-lease-time 86400;
        max-lease-time 86400;
        option routers                  192.168.1.1;
        option ip-forwarding off;
        option subnet-mask              255.255.255.0;
        option broadcast-address        192.168.1.225;
        option domain-name-servers      192.168.1.2, 192.168.1.3;
    option domain-name              "my.domain";



}

        host host1 {
                hardware ethernet FF:FF:FF:FF:FF;
                fixed-address 192.168.1.50;
        }
        host host2 {
                hardware ethernet AA:AA:AA:AA:AA;
        fixed-address 192.168.1.51;
    } 

Cheers!

They used to be in /usr/lib/X11/XKeysymDB or /usr/share/X11/XKeysymDB, but those have been missing from Ubuntu for a while. I've tried google, but all I get are more references to XKeysymDB or the outputs of different people's xmodmap -pke. Where is the concise list?