I have the latest Ubuntu ISO on a USB stick but GRUB doesn't seem to recognize it. It's path is something like /media/ SanDisk 3.2Gen1/ubuntu-24.04.3-desktop-amd64.iso and I suspect the SanDisk part of the path makes it invisble to GRUB.

Any idea how to move the iso up one tier or to tell Grub to decend the path?

I have an old computer with 5 hard drives, and Kubuntu 24.04. I am able to connect locally to a shared folder on the main hard drive where Kubuntu is installed, but I get "permission denied" when trying to connect to a share on one of the other physical drives mounted in /media/mrx/Crucial2TB. Here are the configs:

/etc/samba/smb.conf

[ls1]
path = /media/mrx/Crucial2TB/shared
read only = no
browsable = yes
valid users = sambauser, @sambashare
writeable = yes
force user = sambauser

[ls2]
path=/home/sambauser/shared
read only = no
browsable = yes
valid users = sambauser, @sambashare
writeable = yes
force user = sambauser

and the shares:

$ sudo stat /media/mrx/Crucial2TB/shared
  File: /media/mark/Crucial2TB/shared
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 8,65    Inode: 110100481   Links: 2
Access: (0777/drwxrwxrwx)  Uid: ( 1001/sambauser)   Gid: (  988/sambashare)

$ sudo stat /home/sambauser/shared
  File: /home/sambauser/shared
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 8,33    Inode: 9832830     Links: 2
Access: (0755/drwxr-xr-x)  Uid: ( 1001/sambauser)   Gid: (  988/sambashare)

and the mount commands:

sudo mount -t cifs //10.0.0.9/ls1 /mnt/local_shared1/ -o username=sambauser
sudo mount -t cifs //10.0.0.9/ls2 /mnt/local_shared2/ -o username=sambauser

the mount point in /etc/fstab for the crucial drive:

UUID=791ec2e1-fb58-4d17-3214-803ee65ff45 /media/mrx/Crucial2TB        ext4    defaults        0 2

I get "permission denied" for ls1, but ls2 works.

When I go to print some documents (both created by LibreOffice, and PDFs printed from Okular / Browser), the printer is able to print the page, but really sloppily, as some parts of lines (not the full lines!) of text will be truncated, sort of horizontally cut off:

Using the "Copy page" function on the printer itself doesn't have the striping on the resulting printout, so I am assuming the problem lies somewhere between my text editor and the printer.

OS: Kubuntu 25.10

I tried to create a bootable USB drive using Ventoy and then dragged the macOS.img file onto it. When I booted my MacBook and held the Option key to select the USB drive, it didn't boot.

I have 2 external monitors, set to their standard 2560x1440 resolution, and 100% scale factor.
I'm using X11 as display server.

The problem
If my PC gets in "display off" mode, after turning it back on, (this usually happens after Locking it and leaving it locked for a few minutes), only inside the Kate text editor, the mouse pointer is HUGE.

This gets solved by stopping Kate and starting it again.

How can I fix this ?

I using Ubuntu 25.10 and RX9070XT.

When I watch youtube av1 or vp9 video with Firefox, the percentage of GPU decode in nvtop does not be higher.

My firefox is not snap-firefox I use Linux binary from official download from firefox.com

It keeps 0% even RX9070XT has VP9 and AV1 Hardware decode capability.

How to enable it?

My vainfo output looks correct but it doesn't work:

rying display: wayland
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 25.2.3-1ubuntu1 for AMD Radeon RX 9070 XT (radeonsi, gfx1201, LLVM 20.1.8, DRM 3.64, 6.17.0-6-generic)
vainfo: Supported profile and entrypoints
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileAV1Profile0            : VAEntrypointVLD
      VAProfileAV1Profile0            : VAEntrypointEncSlice
      VAProfileNone                   : VAEntrypointVideoProc

I had a crash while installing updates on my system and now I can't start my machine anymore.

I have found this : Error: vgubuntu-root does not exist. Dropping to a shell & https://unix.stackexchange.com/questions/225246/missing-root-vg-dropped-to-an-initramfs-shell but was not able to solve the issue.

I thought I would have a solution here https://fr.linux-terminal.com/?p=4744 but the command fsck doesn't give any successful output.

Starting in safe mode doesn't help. I created an Ubuntu USB key and was able to start a live session but I have no clue what I could try with it to repair the system.

Also here https://gist.github.com/bmiller59/2297db9d8df4a2fb39daceb82fe578e2 maybe some information. It seems to me very difficult to follow up the instructions.

Finally this https://serverfault.com/questions/375090/using-fsck-to-check-and-repair-luks-encrypted-disk but this is not clear for me if this is relevant in my case.

As you can see I am a bit lost and I am not very familiar with the Linux world.

Would the community and experts here please help me to recover my system if that's possible?

Thank you in advance for your help.

🎯 Goals

I aim to run multiple virtual machines (VMs) using KVM/Qemu on my laptop while achieving the following:

1. Pass through the host's GPU to a guest VM for high-performance graphics.
2. Maintain a graphical user interface (UI) on the host machine to easily connect to the GPU-accelerated guest VM.

🤔 Problem Description

When using PCI Passthrough to assign my laptop's sole GPU to a guest VM, the GPU becomes unavailable to the host operating system. This prevents the host from running a graphical environment (like X11 or Wayland), making it impossible to use the host UI to connect to the guest VM conveniently. I currently must connect from a separate, external computer.

✅ Solutions Checked & Status

💡 Planned Checks

I am considering the following alternative solution:

• Run a minimal X server on the host that does not require GPU acceleration (e.g., a simple framebuffer or software-rendered X server). Then, run a standard VNC client within this minimal host environment to connect to the GPU-accelerated guest VM.

❓ Main Question

I am seeking guidance on the most viable solution to connect to a GPU-passthrough guest VM from the same host, without losing the host's graphical environment. Specifically:

1. Is DirectVNC a current and viable solution for this use case, or is its failure to connect an indicator of an inherent issue?
2. Is it technically possible to run a minimal X server and a VNC client on the host machine without relying on a GPU?
3. Are there other established or suggested solutions to achieve a local, GPU-passthrough VM with easy UI access from the host?

Specifications :

• Ubuntu 24.04.3 LTS

• Dell Inc. Inspiron 5770

• Intel® Core™ i7-8550U × 8 / Intel Kabylake (Gen9)

• RAM 24 Gio

Issue description :

I'm running Ubuntu with a dual monitor (desktop integrated display + external monitor) for months. Both monitors are independent (joint display as opposed to clone mode). Since the beginning of this week, the integrated display randomly freezes. Even the mouse cursor remains displayed on the frozen screen. Meanwhile, the Ubuntu system and the external monitor keep working normally. The external monitor is configured as the main desktop display. Thus, I can open the settings. Then, switching to clone mode and immediately back to joint mode revive the integrated display.

I'm wondering if a recent software update may have compromised the system stability. Also, I noticed the computer may sometime be very busy, fans are running fast, during power saving mode. In this case, I'm unable to wake up the computer (forced power down).

Could you please help me diagnose the reasons why this occurs and, maybe, find a fix ?

Thanks.

After updating Ubuntu, my system is showing slower boot times and occasional freezes. How can I diagnose which service or driver is causing the slowdown, and what steps can I take to fix it?

System Ubuntu 24.04.3 Gnome Wayland. Hardware Micro-Star International Co., Ltd. MS-7E02; Processor I5-14600K; Video card Vulkan 1.4(NVIDIA GeForce RTX™ 3070 Ti (NVIDIA_PROPRIETARY)); Samsung 32' monitor 3840x2160 resolution; and XP-PEN 15.6 pro drawing tablet. Problem under Wayland, if I connect the drawing tablet to the computer and set the mirroring, the machine switches to the drawing tablet resolution which is 1920x1080. Then the desktop hangs off the edge of the display and the shutdown icon is not visible. If I separate the computer and the drawing tablet, the resolution remains but I cannot restore it to the original in the settings because (even though the primary display is Samsung) I can only choose between the drawing tablet options where FULLHD is the highest. How can I restore the original resolution to 3840x2160. Thanks in advance for your help.

I had docker running on my LTS 24.04 system that I had installed from the docker site--not the snap version from Ubuntu. However, I had not installed the docker-compose script (didn't know it wasn't included by default). Anyway, I naively tried to grab it using apt-get and suddenly I have the snap version of docker. This caused all kinds of problems, and I'd like to get rid of it, and start over.

I thought this would be easy, but my computer just hangs whenever I try

sudo snap docker disable
sudo snap remove docker    # have tried with and without --purge

After running the command, I check on the process with

ps aux | grep snap

and see 2 processes that are in interruptible sleep mode (STAT Ss and S+) with sudo, and another process by root that has STAT Sl+, i.e, they are waiting on something...

I've tried killing the process and that causes snap to stop with

error: Change finished in status  Hold with no error message.

I can reset the snap demon following the solution here

How can I force remove a snap

But even after resetting the snap daemon, when I execute

sudo snap remove --purge docker

I'm back to a hung system.

I can see that the docker service and docker.socket are stopped, so that should not be why the snap.daemon is waiting.

@Rinzwind: No the service is not active. The system attempts to load it, but fails.

This did prompt me to remove the manually installed version of docker. That eliminates the docker service from even trying to start (it was broken since the snap install) since nothing is installed anymore. However, I still cannot get rid of the snap docker version. Even after reboot and cleaning the snapd/state.json activity related to previous attempts to remove docker.

snap changes yields

docker   28.4.0   3377   latest/stable    canonical✓  disabled

sudo systemctl status docker

yields

Unit docker.service could not be found.

docker.socket is also not running.

Any suggestions?

I installed Ubuntu 24.04 Server and attached its machine to Ubuntu Pro. When I try to update it, I get something like this:

On the sidebar with the icons, there is the Files icon. Earlier I was downloading books from Google drive and organizing them in folders in the Documents folder. Ever since there has been a 2 attached to the icon.

What is this telling me and is there some action I need to take?. I have tried restarting, and it has been there for hours now.

Thanks

When upgrading Ubuntu from 25.04 to 25.10, I lost GRUB (which was allowing me to run either Ubuntu or Windows). How to regain or reinstall the lost GRUB?

I have Ubuntu 20.04.2. I'm trying to use US international as is usual on Mac and Windows, where if I type ' + a -> á, and if I type ' + m -> 'm, but for some reason here it just writes ḿ instead. Is there a way to only put accents on vowels and not on consonants as is done in other OS?

This was asked here before, but as itś an old post, I thought I´d ask again.

I'm trying to install a Ubuntu VM on a SnapDragon X Plus laptop using WSL, using the recipe on the Qualcomm site with one difference: I need version 24 instead of 22.

Everything goes as described ion the site and I get the familiar bash prompt in a Windows Powershell screen, but when I type sudo apt update for the first time, it ignores all the sites because the VM has no internet access.

I did change the contents of /etc/resolv.conf to nameserver 8.8.8.8 using the command specified by Qualcomm and checked that it is persistent after wsl --shutdown. Stopping and starting WSL does not solve the issue though. The host has internet access, the guest does not.

Could there be a difference between Ubuntu 22 and 24 that makes this particular recipe not to work?

Suddenly (it USED to work) I have only "dummy" output on Ubuntu 25.10 on a Dell 14 Pro Plus. I need some guidance on how to find out what actually is amiss. A built-in hardware check in the BIOS was able to play some sound via the speakers.

linux-image-6.17.0-5-generic

Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002)
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915])
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: hda codecs found, mask 4
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: BT link detected in NHLT tables: 0x4
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 0
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1:
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware file:     intel/sof-ipc4/arl/sof-arl.ri
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware lib path: intel/sof-ipc4-lib/arl
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3:  Topology file:     intel/sof-ace-tplg/sof-arl-cs42l43-l0.tplg
Oct 17 18:43:22 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Loaded firmware library: ADSPFW, version: 2.13.0.1
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.13.0.1
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Using function topologies instead intel/sof-ace-tplg/sof-arl-cs42l43-l0.tplg
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: loading topology 0: intel/sof-ace-tplg/sof-sdca-jack-id0.tplg
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: loading topology 1: intel/sof-ace-tplg/sof-sdca-mic-id4.tplg
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: loading topology 2: intel/sof-ace-tplg/sof-sdca-1amp-id2.tplg
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: loading topology 3: intel/sof-ace-tplg/sof-hdmi-pcm5-id5.tplg
Oct 17 18:43:23 Pro-14-Plus kernel: sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1

lspci -v

00:1f.3 Audio device: Intel Corporation Device 7728 (prog-if 80)
    Subsystem: Dell Device 0ce8
    Flags: bus master, fast devsel, latency 64, IRQ 194, IOMMU group 16
    Memory at 50192d0000 (64-bit, non-prefetchable) [size=16K]
    Memory at 5019000000 (64-bit, non-prefetchable) [size=2M]
    Capabilities: <access denied>
    Kernel driver in use: sof-audio-pci-intel-mtl
    Kernel modules: snd_sof_pci_intel_mtl, snd_hda_intel


$ aplay -lL
null
    Discard all samples (playback) or generate zero samples (capture)
pipewire
    PipeWire Sound Server
default
    Default ALSA Output (currently PipeWire Media Server)
hw:CARD=sofsoundwire,DEV=0
    sof-soundwire, 
    Direct hardware device without any conversions
hw:CARD=sofsoundwire,DEV=2
    sof-soundwire, 
    Direct hardware device without any conversions
hw:CARD=sofsoundwire,DEV=5
    sof-soundwire, 
    Direct hardware device without any conversions
hw:CARD=sofsoundwire,DEV=6
    sof-soundwire, 
    Direct hardware device without any conversions
hw:CARD=sofsoundwire,DEV=7
    sof-soundwire, 
    Direct hardware device without any conversions
hw:CARD=sofsoundwire,DEV=31
    sof-soundwire, 
    Direct hardware device without any conversions
plughw:CARD=sofsoundwire,DEV=0
    sof-soundwire, 
    Hardware device with all software conversions
plughw:CARD=sofsoundwire,DEV=2
    sof-soundwire, 
    Hardware device with all software conversions
plughw:CARD=sofsoundwire,DEV=5
    sof-soundwire, 
    Hardware device with all software conversions
plughw:CARD=sofsoundwire,DEV=6
    sof-soundwire, 
    Hardware device with all software conversions
plughw:CARD=sofsoundwire,DEV=7
    sof-soundwire, 
    Hardware device with all software conversions
plughw:CARD=sofsoundwire,DEV=31
    sof-soundwire, 
    Hardware device with all software conversions
sysdefault:CARD=sofsoundwire
    sof-soundwire, 
    Default Audio Device
dmix:CARD=sofsoundwire,DEV=0
    sof-soundwire, 
    Direct sample mixing device
dmix:CARD=sofsoundwire,DEV=2
    sof-soundwire, 
    Direct sample mixing device
dmix:CARD=sofsoundwire,DEV=5
    sof-soundwire, 
    Direct sample mixing device
dmix:CARD=sofsoundwire,DEV=6
    sof-soundwire, 
    Direct sample mixing device
dmix:CARD=sofsoundwire,DEV=7
    sof-soundwire, 
    Direct sample mixing device
dmix:CARD=sofsoundwire,DEV=31
    sof-soundwire, 
    Direct sample mixing device
**** List of PLAYBACK Hardware Devices ****
card 0: sofsoundwire [sof-soundwire], device 0: Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 5: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 6: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 7: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 31: Deepbuffer Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I have a PC with the following specs:

• CPU: AMD Ryzen 5 8600G
• RAM: 32GB DDR5 4800MHz (2x16GB)
• Motherboard: ASUS TUF Gaming B650M-Plus
• PSU: Gigabyte 550W
• Display: LG 240Hz monitor

My system frequently freezes, likely due to issues with the AMDGPU driver, but I haven't been able to resolve it. The problem occurs on both DP (DisplayPort) and HDMI connections.

What I've Tried

I've experimented with various kernel boot options in /etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT. Here’s what I tested:

• amdgpu.dc=0 → Black screen on boot.
• amdgpu.dpm=0 → Black screen on boot.
• amdgpu.runpm=0 → Black screen on boot.
• amdgpu.gpu_recovery=1 or 0 → Freezes persist; sometimes the system recovers, sometimes not.
• amdgpu.noretry=0 → Freezes persist and stay frozen.
• amdgpu.ppfeaturemask=X → Tried multiple values; no improvement.

The only option that stops the freezes is nomodeset, but this disables GPU acceleration, locks the display at 60Hz, and reduces performance. It’s not a viable long-term solution.

Drivers and Distro Attempts

I installed AMDGPU Pro drivers (both open and proprietary versions) and Mesa drivers, but the issue persisted. I’ve reinstalled my Linux system multiple times across different distributions:

• Zorin OS 17 (tried twice).
• Zorin OS 16.
• Linux Mint Cinnamon.
• Ubuntu 24.04 (tried twice). Freezes happen on all of them.

I tried using Wayland and Xorg, Ubuntu Desktop, Gnome Desktop, Gnome Classic, Cinnamon and DDE.

Windows Behavior

On Windows, I encountered similar issues, including HYPERVISOR_ERROR, frequent freezes, and black screens. However, uninstalling AMD software and using only the Windows Update GPU driver seems to have resolved the problem there.

Hardware Checks

I’ve ruled out hardware issues by running several tests:

• CPU and GPU stress tests: No errors.
• Memtest86 (3 passes): No issues found.
• SSD and HDD tests: Passed with no problems.

When Freezes Occur

Most often when using Chromium-based software (e.g., VS Code, Vivaldi Browser, Postman). Firefox can also cause freezes. Sometimes the system freezes when idle, with no specific application running.

It is worth noting that entire system continues to work normally, SSH commands are OK and no other CPU issues.

Logs

Immediate log after one of freezes:

[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=122066, emitted seq=122068
2024-11-24T11:12:06.665580-03:00 isaac-Ubuntu kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process vivaldi-bin pid 5600 thread vivaldi-bi:cs0 pid 5647
2024-11-24T11:12:06.665582-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset begin!
2024-11-24T11:12:06.879538-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - optc1_wait_for_state line:839
2024-11-24T11:12:07.301538-03:00 isaac-Ubuntu kernel: message repeated 2 times: [ amdgpu 0000:0b:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - optc1_wait_for_state line:839]
2024-11-24T11:12:07.439538-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:07.439551-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:07.567536-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:07.567544-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:07.695534-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:07.695538-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:07.824536-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:07.824541-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:07.952539-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:07.952548-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:08.080551-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:08.080560-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:08.208541-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:08.208546-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:08.337537-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:08.337542-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:08.465537-03:00 isaac-Ubuntu kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
2024-11-24T11:12:08.465542-03:00 isaac-Ubuntu kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
2024-11-24T11:12:08.669891-03:00 isaac-Ubuntu kernel: [drm:gfx_v11_0_cp_gfx_enable.isra.0 [amdgpu]] *ERROR* failed to halt cp gfx
2024-11-24T11:12:08.670530-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: MODE2 reset
2024-11-24T11:12:08.702533-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset succeeded, trying to resume
2024-11-24T11:12:08.703530-03:00 isaac-Ubuntu kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
2024-11-24T11:12:08.703534-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: SMU is resuming...
2024-11-24T11:12:08.705530-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: SMU is resumed successfully!
2024-11-24T11:12:08.707529-03:00 isaac-Ubuntu kernel: [drm] DMUB hardware initialized: version=0x08003700
2024-11-24T11:12:08.842521-03:00 isaac-Ubuntu kernel: [drm] kiq ring mec 3 pipe 1 q 0
2024-11-24T11:12:08.845519-03:00 isaac-Ubuntu kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
2024-11-24T11:12:08.845521-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
2024-11-24T11:12:08.845522-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
2024-11-24T11:12:08.845523-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
2024-11-24T11:12:08.845523-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
2024-11-24T11:12:08.845524-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
2024-11-24T11:12:08.845525-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
2024-11-24T11:12:08.845526-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
2024-11-24T11:12:08.845526-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
2024-11-24T11:12:08.845527-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
2024-11-24T11:12:08.845527-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
2024-11-24T11:12:08.845527-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
2024-11-24T11:12:08.845527-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
2024-11-24T11:12:08.845528-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
2024-11-24T11:12:08.845528-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
2024-11-24T11:12:08.846511-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: recover vram bo from shadow start
2024-11-24T11:12:08.846512-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: recover vram bo from shadow done
2024-11-24T11:12:08.846513-03:00 isaac-Ubuntu kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset(4) succeeded!
2024-11-24T11:12:08.847831-03:00 isaac-Ubuntu vivaldi-stable.desktop[5505]: amdgpu: amdgpu_cs_query_fence_status failed.
2024-11-24T11:12:08.922246-03:00 isaac-Ubuntu gnome-shell[5529]: amdgpu: The CS has been rejected (-125).
2024-11-24T11:12:08.922289-03:00 isaac-Ubuntu gnome-shell[5529]: (EE)
2024-11-24T11:12:08.922310-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) Backtrace:
2024-11-24T11:12:08.922326-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 0: /usr/bin/Xwayland (0x5939722f8000+0x170222) [0x593972468222]
2024-11-24T11:12:08.922343-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 1: /usr/bin/Xwayland (0x5939722f8000+0x173016) [0x59397246b016]
2024-11-24T11:12:08.922360-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7c4c5fa00000+0x45320) [0x7c4c5fa45320]
2024-11-24T11:12:08.922376-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x11c) [0x7c4c5fa9eb1c]
2024-11-24T11:12:08.922392-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x1e) [0x7c4c5fa4526e]
2024-11-24T11:12:08.922408-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xdf) [0x7c4c5fa288ff]
2024-11-24T11:12:08.922426-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7c4c48a00000+0x955110) [0x7c4c49355110]
2024-11-24T11:12:08.922442-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7c4c48a00000+0x957bf6) [0x7c4c49357bf6]
2024-11-24T11:12:08.922458-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7c4c48a00000+0xfcb81) [0x7c4c48afcb81]
2024-11-24T11:12:08.922474-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (0x7c4c48a00000+0x11d6fc) [0x7c4c48b1d6fc]
2024-11-24T11:12:08.922490-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (0x7c4c5fa00000+0x9ca94) [0x7c4c5fa9ca94]
2024-11-24T11:12:08.922510-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (0x7c4c5fa00000+0x129c3c) [0x7c4c5fb29c3c]
2024-11-24T11:12:08.922528-03:00 isaac-Ubuntu gnome-shell[5529]: (EE)
2024-11-24T11:12:08.922541-03:00 isaac-Ubuntu gnome-shell[5529]: (EE)
2024-11-24T11:12:08.922554-03:00 isaac-Ubuntu gnome-shell[5529]: Fatal server error:
2024-11-24T11:12:08.922567-03:00 isaac-Ubuntu gnome-shell[5529]: (EE) Caught signal 6 (Aborted). Server aborting
2024-11-24T11:12:08.922581-03:00 isaac-Ubuntu gnome-shell[5529]: (EE)
2024-11-24T11:12:08.922705-03:00 isaac-Ubuntu systemd[1]: Started systemd-timedated.service - Time & Date Service.
2024-11-24T11:12:08.922870-03:00 isaac-Ubuntu dbus-daemon[1031]: [system] Successfully activated service 'org.freedesktop.timedate1'
2024-11-24T11:12:08.973725-03:00 isaac-Ubuntu systemd[1]: update-notifier-download.service: Deactivated successfully.
2024-11-24T11:12:08.973939-03:00 isaac-Ubuntu systemd[1]: Finished update-notifier-download.service - Download data for packages that failed at package install time.
2024-11-24T11:12:10.037516-03:00 isaac-Ubuntu vivaldi-stable.desktop[5505]: X connection to :0 broken (explicit kill or server shutdown).
2024-11-24T11:12:10.037714-03:00 isaac-Ubuntu gnome-shell[2707]: Connection to xwayland lost
2024-11-24T11:12:10.040499-03:00 isaac-Ubuntu gnome-shell[2707]: X Wayland crashed; attempting to recover
2024-11-24T11:12:10.041450-03:00 isaac-Ubuntu systemd[2414]: Stopped target gnome-session-x11-services-ready.target - GNOME session X11 services.
2024-11-24T11:12:10.041567-03:00 isaac-Ubuntu systemd[2414]: launchpadlib-cache-clean.service - Clean up old files in the Launchpadlib cache was skipped because of an unmet condition check (ConditionPathExists=/home/isaac/.launchpadlib/api.launchpad.net/cache).
2024-11-24T11:12:10.041615-03:00 isaac-Ubuntu systemd[2414]: Stopping org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service...
2024-11-24T11:12:10.042095-03:00 isaac-Ubuntu gnome-shell[2707]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
2024-11-24T11:12:10.045563-03:00 isaac-Ubuntu systemd[2414]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE
2024-11-24T11:12:10.046175-03:00 isaac-Ubuntu gnome-shell[2707]: Using public X11 display :0, (using :1 for managed services)
2024-11-24T11:12:10.066368-03:00 isaac-Ubuntu systemd[2414]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'.
2024-11-24T11:12:10.066531-03:00 isaac-Ubuntu systemd[2414]: Stopped org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service.
2024-11-24T11:12:10.066602-03:00 isaac-Ubuntu systemd[2414]: Stopped target gnome-session-x11-services.target - GNOME session X11 services.
2024-11-24T11:12:10.139094-03:00 isaac-Ubuntu systemd[2414]: app-gnome-vivaldi\x2dstable-5498.scope: Consumed 1min 28.870s CPU time.

I’m looking for a solution to make my PC stable on Linux with proper GPU acceleration. Any help is appreciated!

When I reinstalled the OS, I had only one, Ubuntu 22.04 Gnome desktop, option. I got used to MATE desktop. Therefore I installed MATE desktop too. Having two desktop environments, MATE & Gnome, how to switch between them? I cannot just remove Gnome as it affects LibreOffice. Do you have any suggestions?

For a few months I have been troubleshooting no audio coming from brave-browser installed on my Ubuntu 20.04 machine. For example, if I use the same YouTube URL in Brave and Firefox, I get audio from Firefox but not Brave. This lack of audio still occurs if I do a fresh install of Brave, Brave-beta, Brave-nightly, or Chromium - suggesting an issue with Chromium based browsers. Again, however, audio does work when I use Firefox.

However, if I switch user from my main account to another account, I do get audio from the Brave browser when I use that same URL.

I think this is strong evidence that something is awry with my main account. But I am not sure what settings would prevent audio coming from Chromium based browsers (like Brave + Chromium) but not prevent audio from FireFox.

I was hopeful someone might have a suggestion for where to look for what may be awry in my main profile.

Here is the link where I have been troubleshooting the issue: https://community.brave.com/t/ubuntu-no-audio-from-brave-but-working-from-firefox/448355/18

When I type the command sudo python3 -m venv venv001 I get this error:

The virtual environment was not created successfully because ensurepip is not available.  On Debian/Ubuntu systems, you need to install the python3-venv package using the following command.

    apt install python3.8-venv

You may need to use sudo with that command.  After installing the python3-venv package, recreate your virtual environment.

Failing command: ['/home/mike/venv001/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']

so, I try sudo apt install python3.8-env and get the error message:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3.8-venv : Depends: python3.8 (= 3.8.2-1ubuntu1) but 3.8.10-0ubuntu1~20.04 is to be installed
E: Unable to correct problems, you have held broken packages.

I've tried a couple of the sudo apt install -f, or --fix- commands, but still can't seem to recover from these errors.

I have always had a network share with my nas (Alt-F) setup in Ubuntu. To access it I allow port 137&138udp in and out and 139&445tcp in and out within ufw. Since upgrading to 20.04 those rules don't work anymore. I have to turn the firewall off to be able to see the share. Once it is mounted and the folder opened I can turn the firewall back on and it works as normal but to be able to see it on the network or open the main folder initially I have to turn off the firewall. Is there another port that now has to be opened in 20.04? The other strange thing is that if I turn SMB1 off on my NAS I can't see the share in Ubuntu, if I turn off SMB2 I can see it but I can't mount any shares, so both SMB1 and SMB2 both have to be activated so that I can see the share (SMB1) and mount it (SMB2). I have always had this working from versions 10-18.04 and in 20.04 is the first time I have had this issue.

I am following the steps listed here to try to get my WD Passport Wireless Pro 3TB HDD to work with Lubuntu 18.04: http://tutodir.com/how-to-mount-wd-my-passport-wireless-pro-on-ubuntu/

I run into the title error below:

owner@G700:~$ sudo mkdir /mnt/MyPassport
owner@G700:~$ sudo mount -t cifs -o guest //MyPassportIP/MyPassport /mnt/MyPassport
mount error: could not resolve address for MyPassportIP: Unknown error

owner@G700:~$ sudo mount -t cifs -o guest //192.168.60.1/MyPassport /mnt/MyPassport
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

owner@G700:~$ sudo mount -t cifs -o guest //192.168.60.1/MyPassport /mnt/MyPassport
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

owner@G700:~$ sudo nano /etc/fstab
owner@G700:~$ sudo mount -a
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

I believe this is the page being refered to, but I don't know what I should be looking for. Anyone know how to resolve this? https://linux.die.net/man/8/mount.cifs

I have been trying from last few days to create a Portable OS. My reasons being

1. Avoiding Dual Boot
2. To make the OS like Plug and Play

Before trying on External SSD as they are costly, I first tried installing OS on a 32 GB Sandisk Flashdrive which is working very smoothly. Hence I removed all the boot options other than my current windows and I tried installing on my SSD.

I bought Sandisk Extreme and Samsung T5 but Ubuntu Installation didn’t go through as planned. On both the drives it went Straight up to the GRUB Command Line. This feels like the BLUE SCREEN OF DEATH FOR UBUNTU. I must have tried installing more than 10 times, with the help of Answers on Internet.

How To Rescue Non Booting Grub2

I went through step by step as shown in this link. Even in my case I can see content only in (hd0, 1)/ . But I can see only 1 folder which is efi/. I cannot see any other folders that are shown in the link. Same answer is posted everywhere.

Folders - lost+found/ bin/ boot/ cdrom/ dev/ etc/ home/ lib/ lib64/ media/ mnt/ opt/ proc/ root/ run/ sbin/ srv/ sys/ tmp/ usr/ var/ vmlinuz vmlinuz.old initrd.img initrd.img.old

None of these folders are visible for me.

Let me Tell you my Ubuntu installation process.

1. Opened the Try and Install Ubuntu
2. Went through the initial installation process
3. Clicked on Something Else
4. 16GB for Swap (logical and end of the storage)
5. Rest for primary, ext4 and root as “/“ partition
6. Next , Next ....

This is what I followed.

I have reached the CONCLUSION that Ubuntu cannot be installed in an External SSD I HOPE IT”S NOT TRUE AND THERE SHOULD BE A WAY AROUND. It worked perfectly well in PenDrive. I could just plug the pendrive(INSTALLED OS AND NOT THE BOOTABLE) and start using Ubuntu.

I chose SSD because it is more durable as well as faster than a hdd.

I am open to any Suggestions to Improve my above long Question with Explanation if it’s not Understandable.

Please Let me know if any more details are required from my side.

^{GRUB command line}

Gnome-boxes begins to start then crashes on my account. However, I created another account and boxes loaded fine. I tried to delete the files in ~/.config and ~/.share but no luck.

When I launch from the CL I get the following error:

(gnome-boxes:13410): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed
Segmentation fault (core dumped)\

Update: gnome-boxes --checks results in:

(gnome-boxes:2803): Boxes-WARNING **: util-app.vala:270: Failed to execute child process ?virsh? (No such file or directory)

(gnome-boxes:2803): Boxes-WARNING **: util-app.vala:250: Failed to execute child process ?restorecon? (No such file or directory)
• The CPU is capable of virtualization: yes
• The KVM module is loaded: yes
• Libvirt KVM guest available: no
• Boxes storage pool available: no
    Could not get “gnome-boxes” storage pool information from libvirt. Make sure “virsh -c qemu:///session pool-dumpxml gnome-boxes” is working.
• The SELinux context is default: no

Report bugs to <https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes>.
Boxes home page: <https://wiki.gnome.org/Apps/Boxes>.`

Thanks in advance for any advice how to correct this problem.

I have 3rd gen Intel mobile CPU i5-3210M, with integrated HD4000 graphics.How can I tell what driver version (i915) I have and does it support Vulkan? What Mesa version I have in Kubuntu 16.10?

What happens if I run a game made with Vulkan API without Vulkan support in driver?

Is there a way to enable tap to click for the Thinkpad trackpoint using systemd in 15.04? I know sensitivity can be adjusted, but I have not seen a way to enable tap to click. There's instructions here on how to adjust sensitivity under systemd:

Increase Trackpoint Sensititvity with SystemD (Ubuntu 15.04 or later)

I've not found out how to enable tap to click though

I run Ubuntu 14.04 and have already downloaded and installed the driver for my Epson L210, but the printer is not recognised. When printing any document, the L210 does not appear in the printer list.

I have installed lirc, and I want to use irexec to control my music player daemon (mpd) using mpc commands from my mce remote control. Works fine, except for one thing:

If I want to edit the /etc/lirc/lircrc file to map the remote control buttons to commands, I need to reboot in order to read in and use the edited lircrc button/command definition file. To test things out is then a rather painful and time consuming experience.

/etc/init.d/lirc restart 

does NOT do the trick, it just makes the remote stop working. Function returns after reboot.

What elese needs to be restarted? Or should I use some other method?