VLC and Xine volume controls interacting https://askubuntu.com/questions/1562951/vlc-and-xine-volume-controls-interacting

Ever since "upgrading" to 24.04 from 22.04 I have noticed an odd interaction between vlc and xine.

First) I am unable to tell vlc to start at a certain volume level every time it starts. "Always reset audio start level to" is disabled. Nothing I've found allowed me to enable that.

  1. Using the volume control in the UI, I can only go 99% or 101%. No matter what I do, I can not position that slider to exactly 100%.

c) (and here is the odd part) If I watch a video using xine, despite having "startup audio volume" set to 0, if I increase the volume in vlc, xine will start up at that volume level (set in vlc) instead.

  1. In xine, if I enable "restore volume level at startup," the program will lock up.

&) if I set the volume in xine to 0, vlc will open the next video with the volume muted.

It's like the two programs are in cahoots.

How to reset speakers not working https://askubuntu.com/questions/1562949/how-to-reset-speakers-not-working

I am running Ubuntu on a Samsung Galaxy Book and the speakers are no longer working (no sound). I played with the sound configuration days ago, and I am not sure on how I changed the configuration (I used Claude Code). How would you proceed to reset the audio configuration and get the speakers working? Thanks!

Windows 10 - Ubuntu Guest - SMB Host Bus Contoller and Bluetooth errors https://askubuntu.com/questions/1562946/windows-10-ubuntu-guest-smb-host-bus-contoller-and-bluetooth-errors

In the Past, i installed different Guests without problems.

Now, i can't install anymore.

Allways errors something about: "No SM Bus Host controller" and allso Bluetooth errors. Code 28

Done with: VM Ware Workstation 12.5.9

I reinstalled VM Ware Workstation 12.5.9 - nothing changed

As i told: until today without errors.

I guess, that something in my: Windows 10 Enterprise is damaged.

Edit: just run DISM to repair from the original DVD Result: told, that it was repaired - but nothing changed....

Cant boot from new Ubuntu boot USB. Secure boot is on, but have no Microsoft account & no Bitlocker recovery key https://askubuntu.com/questions/1562943/cant-boot-from-new-ubuntu-boot-usb-secure-boot-is-on-but-have-no-microsoft-acc

Created a Ubuntu boot USB flash drive.

It shows as an option in Boot Menu, but selecting it does nothing. Ubuntu instructions recommend turning Secure Boot off, but have read that i will then get a request for a Bitlocker recovery key which i don't have since i set up my Lenovo Think Pad without a Microsoft Account. I've seen online warnings that say if i get to that request, i will be stuck there without a key.

I'm skeeert to proceed.

Any suggestions?

I do have a recovery disk & backups but.....

Thanks

Broken Nvidia packages on Ubuntu 22.04.5 LTS https://askubuntu.com/questions/1562942/broken-nvidia-packages-on-ubuntu-22-04-5-lts
sudo ubuntu-drivers autoinstall
Reading package lists... Done
Building dependency tree... Done
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:
 linux-modules-nvidia-580-open-6.8.0-90-generic : Depends: nvidia-kernel-common-580 (<= 580.95.05-1) but 580.126.09-1ubuntu1 is to be installed
E: Unable to correct problems, you have held broken packages.

After purging nvidia* and rebooting, I've encounteres this issue when running ubuntu-drivers autoinstall. How can I fix the broken nvidia packages?

Critical LVM volume degraded due to missing physical disk on Ubuntu Server 22.04 https://askubuntu.com/questions/1562941/critical-lvm-volume-degraded-due-to-missing-physical-disk-on-ubuntu-server-22-04

We are facing a critical storage issue on an Ubuntu Server running on bare metal hardware, and we need guidance on safe recovery steps.

System details:

  • Deployment type: Bare metal (physical server)
  • OS: Ubuntu Server
  • Storage: LVM (non-RAID, single LV spanning multiple PVs)
  • Environment criticality: Production / critical data
  • One physical disk has failed and is no longer detected by the kernel (/dev/sdc not visible in lsblk, /proc/partitions, or sysfs). As a result, the LVM Volume Group is in a degraded state with one missing Physical Volume.
  • Despite the missing PV, the Logical Volume is still active and the filesystem remains mounted and readable due to cached LVM metadata.

Current LVM state (summary):

  • VG: vg_data
  • Total PVs: 2 (1 present, 1 missing)
  • Missing PV shows as [unknown] with attributes a-m
  • LV size: ~29 TB (spans both disks)
  • Filesystem usage: ~92% mounted at /backup_data
  • LVM warnings indicate a missing PV UUID.

Observed behavior:

  • Filesystem is readable but unstable.
  • Any reboot, remount, or write operation risks permanent data loss.
  • No RAID or mirroring is configured.
  • The missing disk previously showed SATA I/O errors and was disabled by the kernel.

Actions already taken:

  • Writes have been stopped.

  • Filesystem has been remounted read-only.

  • Critical data is being copied off the system.

  • No destructive LVM commands (vgreduce, pvremove, fsck) have been executed.

We would like confirmation and guidance on:

  • Whether Ubuntu provides any safe, supported method to stabilize or recover an LVM VG when a PV is permanently missing (without RAID/mirroring)

  • Best practice steps to avoid further data corruption while the LV remains active

  • Confirmation that data recovery is limited to copying readable data off the mounted filesystem before shutdown.

Please note this is a high impact production issue, and data integrity is the top priority.

Microk8s dashboard on remote laptop https://askubuntu.com/questions/1562933/microk8s-dashboard-on-remote-laptop

I have installed the latest version of Ubuntu to a cluster bramble of 4 Raspberry Pi 4s, each with 4GB.

I use a miniswitch to link all via Ethernet.

The 4 Pi's have static IPs for wireless, starting with 198.162.0.100 for the first node.

I have installed microk8s to all and set up a cluster.

I can see all 4 nodes.

On the first node, if I plug in a keyboard, mouse and HDMI screen,and open up Firefox, I am able to get to the K8s dashboard after entering the token.

What I would like to do though is access the dashboard via a remote laptop (also running the latest version of Ubuntu), but using the instructions on the Canonical microk8s, I can't get a connection, even though I can ssh to all 4 nodes OK. UFW is inactive on all machines.

Can anyone advise why it's not connecting at all?

Can't start Linux PC - suspected full hard drive https://askubuntu.com/questions/1562914/cant-start-linux-pc-suspected-full-hard-drive

My Linux-based PC boots to a black screen with blinking cursor. The computer ("old") has Linux and Windows 10 installed on separate partitions.

I used Recovery mode and checked the disk. It showed my that C: drive is about 450GB and about 420GB was used. Usage was 100%. That's why I assumed that lack of free space on the hard drive is a problem.

I used a live CD and live USB sticks, opened up the problematic drive (let's call it "old") and tried to delete some unimportant files/folders from the old HD. They could not be deleted.

Is there a way to delete (or copy) unwanted large files/folders from the old hard drive using the terminal (with a live USB)?

Orca Slicer is running unusably slow https://askubuntu.com/questions/1562836/orca-slicer-is-running-unusably-slow

I'm currently running Ubuntu 25.10 and am trying to run OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.1.AppImage (the latest stable version from Orca). The application launches fine but is unusably slow. I have an NVIDIA 5060 GPU (drivers are working fine) and 32 gigs of RAM with a AMD Ryzen 5 CPU (should be plenty to run slicer software).

I have checked the application logs and there is nothing to indicate a problem. When I say unusable, I can try to slice an object and it will be (so far) 2 days before it completes or will allow me to make changes. I'm not sure if this is an Ubuntu issue or an Orca issue, so I thought I would see if anyone here is having similar problems. I'm using a Creality K2 Plus printer over a LAN connection.

Can only consistently boot Ubuntu with recovery mode https://askubuntu.com/questions/1562613/can-only-consistently-boot-ubuntu-with-recovery-mode

Unlike Can only boot Ubuntu 20.04.1 LTS when holding shift, I have Ubuntu 24.04.3 running on a HDD with the CPU being an AMD Ryzen 5 7600X.

Going into GRUB and then into Recovery Mode, seems to be the only way to boot all the way to desktop consistently.

enter image description here

Latest Recovery had black sections before I moved the selected options over them. Maybe it works is also related to how the resolution becomes 1024 x 768.

And even when I get GRUB, rarely, using the "Ubuntu" option boots fine. Holding down Shift during the boot logo might actually do something useful, or might just be me making a false cause fallacy.

Unlike the linked question's answer, my sudo nano /etc/default/grub reads:

> GRUB_DEFAULT=0  
GRUB_TIMEOUT_STYLE=hidden  
GRUB_TIMEOUT=0  
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`  
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"  
GRUB_CMDLINE_LINUX=""

Is it because I have quad boot options on my GRUB? Ubuntu, Advanced, Memory Tests, then Windows 10, XP, and another XP spread out over 3 HDDs. They're all on Legacy, but I'm always just trying to boot into Ubuntu.

I bet it's more due to graphics related stuff that flickers my screen as the boot logo screen adjusts to fit my monitor. My card and monitor are really old, (NVIDIA GT 220 connecting to a Hanns.G HG-216D), but it does that no matter if I go to GRUB, although the screen doesn't tear if I actually get to see the GRUB menu.

It seems even just getting to GRUB isn't a total fix. Did a sudo shutdown -r now from a successful boot to get to GRUB, left it on GRUB for a while while typing most of this out, picked Ubuntu, and the screen didn't tear, but there's still a black screen after the boot logo.

I got a copy of the logs of a successful boot, but it's sort of long, and nothing obvious jumps out at me?

Can't install Ubuntu 25.10 on HP Victus 15 https://askubuntu.com/questions/1562208/cant-install-ubuntu-25-10-on-hp-victus-15

PS:I'm actually a novice in the Linux World so please be nice :(.

I've been trying to install Ubuntu 25.10 alongside W11 in my HP Victus 15, but anyway I try unknown error crashed with UnicodeDecodeError always appears. All of this happened with Secure Boot enabled, knowing Ubuntu should handle that fine.

The live environment itself works fine, I can connect to Wifi, Bluetooth works, Audio is not bugged, but since my keyboard layout is Latin America, I have to change that in Keyboard settings, but nothing more strange. The only thing not working entirely is the installer.

What i tried:

  • Shutting down and rebooting,
  • Using both Rufus in W11 (formatting to GPT) and my friend's laptop with Kubuntu's "ISO Image Writer" re-flashed my USB many times. (Verified the ISO image before burning and verified the USB after)
  • Attempted using another Ubuntu Desktop version to install (so far only 24.04.3 LTS, 25.10 interim and 26.04 LTS Daily Build),
  • Used another USB, doing the same procedure as before.

Then I ran into a "temporal" solution, which means changing the locale thing, so that i ran that and then export LANG=en_US.UTF-8 && export LC_ALL=en_US.UTF-8. It did made the previous error disappear, but now the "Preparing Ubuntu" screen stays buffering indefinitely.

Both of the USBs I've tested before, they do boot and they can install Ubuntu just fine in other laptops, while in mine it doesn't. And this just happens with Ubuntu specifically, any other Linux distro I've tried in my laptop boots, and the installer works.

here are My laptop specs:

HP Victus 15-fb2xxx
Ryzen 5 8645HS w/ Radeon 760M
NVIDIA GeForce RTX 3050 6GB Laptop
16 GB DDR5 RAM 5600 MT/s
1TB M.2 NVMe of Storage

Chrome crashing on Wayland https://askubuntu.com/questions/1553950/chrome-crashing-on-wayland

Chrome (Version 138.0.7204.157 (Official Build) (64-bit)) is crashing (something to do with Wayland/GPU). It works if launched using --disable-gpu but this isn't obviously that useful.

Grateful for any suggestions/pointers.

System:

Ubuntu 24.04.2

GPU Radeon RX550/550
Aug 02 21:32:33 opti systemd[4146]: Started app-com.google.Chrome-81822.scope.
Aug 02 21:32:33 opti gnome-shell[4782]: WL: error in client communication (pid 81822)
Aug 02 21:32:33 opti google-chrome.desktop[81829]: [81822:81822:0802/213233.519225:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a
Aug 02 21:32:33 opti google-chrome.desktop[81829]: [0802/213233.526070:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 02 21:32:33 opti google-chrome.desktop[81829]: [0802/213233.526597:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 02 21:32:33 opti google-chrome.desktop[81829]: [0802/213233.533188:ERROR:third_party/crashpad/crashpad/util/file/directory_reader_posix.cc:43] opendir /home/user1/.config/google-chrome/Crash Reports/attachments/846a4598-6efd-4ec5-a1fb-e657a44e4ef3: No such file or directory (2)
Aug 02 21:32:33 opti google-chrome.desktop[81829]: [81882:81903:0802/213233.632005:ERROR:net/socket/ssl_client_socket_impl.cc:896] handshake failed; returned -1, SSL error code 1, net_error -3
Aug 02 21:32:33 opti google-chrome.desktop[81829]: [81882:81903:0802/213233.632231:ERROR:net/socket/ssl_client_socket_impl.cc:896] handshake failed; returned -1, SSL error code 1, net_error -3
Problem with nouveau driver and Ubuntu 24.04 https://askubuntu.com/questions/1520162/problem-with-nouveau-driver-and-ubuntu-24-04

I'm having a problem on Ubuntu 24.04. After a fresh installation, I notice that there are graphical bugs appearing in Gnome. My config is as follows:

kernel : 6.8.0_36-generic
Kernel driver in use: nouveau
2x Intel cores 2 duo T9550 @ 2,66ghz
3,8 giga RAM
NVIDIA Geforce 9600M GT (rev a1)

Menus and listmenu are often invisible (the elements appear when hovering the cursor) or twinkle. This bug is present in gnome-control-center, nautilus but also in the gnome scanner application. In the gnome control center the list of wallpapers or theme colors is not displayed and twinkle. gnome-software also encounters the same type of problem. Sometimes the desktop freezes completely and I have to do a hard reboot (even though ssh responds well). I installed kde via apt install kubuntu-desktop. and I encounter much fewer problems with KDE applications. But even under kde, gnome applications have bugs. On the Kde side only the system monitoring application is not displayed correctly. sddm is also unusable. I have to stay on gdm3. When I start grub with the nomodeset parameter there are no more problems. The problem appears both under X and Wayland

Here are the logs that I was able to recover before a freeze or when displaying wallpapers under Gnome.

2024-07-09T10:34:32.872181+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - Unknown CUDA fault at address 00201c0e00
2024-07-09T10:34:32.872182+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000ff2, e1c: 00000000, e20: 00000000, e24: 09030000
2024-07-09T10:34:32.872185+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 1 - Unknown CUDA fault at address 00201caa00
2024-07-09T10:34:32.872202+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 1 - e0c: 00000000, e18: 00000ff2, e1c: 00000000, e20: 00000000, e24: 09030000
2024-07-09T10:34:32.872203+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: 00200000 [] ch 22 [001dc12000 gnome-control-c[20738]] subc 3 class 8297 mthd 15e0 data 00000000
2024-07-09T10:34:32.872216+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - Unknown CUDA fault at address 00201c2800
2024-07-09T10:34:32.872218+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000ff2, e1c: 00000000, e20: 00000000, e24: 09030000
2024-07-09T10:34:32.872219+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 1 - Unknown CUDA fault at address 00201ca000
2024-07-09T10:34:32.872221+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 1 - e0c: 00000000, e18: 00000ff2, e1c: 00000000, e20: 00000000, e24: 09030000
2024-07-09T10:34:32.872222+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: 00200000 [] ch 22 [001dc12000 gnome-control-c[20738]] subc 3 class 8297 mthd 15e0 data 00000000
2024-07-09T10:34:32.872224+02:00 xxxx kernel: nouveau 0000:01:00.0: fb: trapped write at 00201ca000 on channel 22 [1dc12000 gnome-control-c[20738]] engine 00 [PGRAPH] client 0b [PROP] subclient 09 [LOCAL] reason 00000002 [PAGE_NOT_PRESENT]

Here are logs retrieved during display problems under kde:

2024-07-10T11:30:05.166274+02:00 xxxx kernel: nouveau 0000:01:00.0: fb: trapped write at 00201bb200 on channel 9 [1efe6000 plasma-systemmo[12057]] engine 00 [PGRAPH] client 0b [PROP] subclient 09 [LOCAL] reason 00000002 [PAGE_NOT_PRESENT]
2024-07-10T11:30:05.166276+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - Unknown CUDA fault at address 00201b0c00
2024-07-10T11:30:05.166278+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000ff2, e1c: 00000000, e20: 00000000, e24: 09030000
2024-07-10T11:30:05.166280+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 1 - Unknown CUDA fault at address 00201bb400
2024-07-10T11:30:05.166282+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_PROP - TP 1 - e0c: 00000000, e18: 00000f02, e1c: 00000000, e20: 00000000, e24: 09030000
2024-07-10T11:30:05.166284+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: 00200000 [] ch 9 [001efe6000 plasma-systemmo[12057]] subc 3 class 8297 mthd 15e0 data 00000000
2024-07-10T11:30:05.166286+02:00 xxxx kernel: nouveau 0000:01:00.0: fb: trapped write at 00201b0c00 on channel 9 [1efe6000 plasma-systemmo[12057]] engine 00 [PGRAPH] client 0b [PROP] subclient 09 [LOCAL] reason 00000002 [PAGE_NOT_PRESENT]
2024-07-10T11:30:05.166288+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: magic set 0:
2024-07-10T11:30:05.166290+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  00408904: 20097d01
2024-07-10T11:30:05.166292+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  00408908: 00000000
2024-07-10T11:30:05.166293+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  0040890c: 40000430
2024-07-10T11:30:05.166295+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  00408910: 00000000
2024-07-10T11:30:05.166297+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_TEXTURE - TP0: 00000003 [ FAULT]
2024-07-10T11:30:05.166299+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: magic set 1:
2024-07-10T11:30:05.166301+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  00409904: 20097f01
2024-07-10T11:30:05.166302+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  00409908: 00000000
2024-07-10T11:30:05.166304+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  0040990c: 40000430
2024-07-10T11:30:05.166306+02:00 xxxx kernel: nouveau 0000:01:00.0: gr:  00409910: 00000000
2024-07-10T11:30:05.166308+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: TRAP_TEXTURE - TP1: 00000003 [ FAULT]
2024-07-10T11:30:05.166310+02:00 xxxx kernel: nouveau 0000:01:00.0: gr: 00200000 [] ch 9 [001efe6000 plasma-systemmo[12057]] subc 3 class 8297 mthd 15e0 data 00000000
2024-07-10T11:30:05.166321+02:00 xxxx kernel: nouveau 0000:01:00.0: fb: trapped write at 00201b5000 on channel 9 [1efe6000 plasma-systemmo[12057]] engine 00 [PGRAPH] client 0b [PROP] subclient 09 [LOCAL] reason 00000002 [PAGE_NOT_PRESENT]
2024-07-10T11:30:14.420438+02:00 xxxx kernel: perf: interrupt took too long (3934 > 3933), lowering kernel.perf_event_max_sample_rate to 50000

I also spotted these logs when using gnome:

2024-07-10T11:10:03.914954+02:00 xxxx kernel: nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
2024-07-10T11:10:03.914968+02:00 xxxx kernel: nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
2024-07-09T10:18:50.496002+02:00 xxxx gnome-shell[12508]: DING: (gjs:13017): GLib-GIO-CRITICAL **: 10:18:50.484: GFileInfo created without standard::is-hidden
2024-07-09T10:18:50.498934+02:00 xxxx gnome-shell[12508]: DING: (gjs:13017): GLib-GIO-CRITICAL **: 10:18:50.484: file ../../../gio/gfileinfo.c: line 1632 (g_file_info_get_is_hidden): should not be reached
2024-07-09T10:18:50.499189+02:00 xxxx gnome-shell[12508]: DING: (gjs:13017): GLib-GIO-CRITICAL **: 10:18:50.484: GFileInfo created without standard::is-backup
2024-07-09T10:18:50.499330+02:00 xxxx gnome-shell[12508]: DING: (gjs:13017): GLib-GIO-CRITICAL **: 10:18:50.484: file ../../../gio/gfileinfo.c: line 1654 (g_file_info_get_is_backup): should not be reached
2024-07-09T10:18:50.499646+02:00 xxxx gnome-shell[12508]: DING: (gjs:13017): GLib-GIO-CRITICAL **: 10:18:50.484: GFileInfo created without standard::is-symlink
2024-07-09T10:18:50.500417+02:00 xxxx gnome-shell[12508]: DING: (gjs:13017): GLib-GIO-CRITICAL **: 10:18:50.484: file ../../../gio/gfileinfo.c: line 1676 (g_file_info_get_is_symlink): should not be reached

The problem therefore seems to be on the nouveau driver. Unfortunately the graphics card is too old to be compatible with a proprietary Nvidia driver.

Note that the problem appears in the live session before installation, but this problem was not present on version 23.10 of Ubuntu.

Do you know what I can do?

USB-C to HDMI adapter shows as a billboard device - no display https://askubuntu.com/questions/1436289/usb-c-to-hdmi-adapter-shows-as-a-billboard-device-no-display

I've tried a few different adapters to get display output from my USB-C port. None of them have worked on Ubuntu. This is what I get (or similar) from lsusb for every USB-C to HDMI adapter that I bought:

Bus 001 Device 010: ID 0bda:2172 Realtek Semiconductor Corp. BillBoard Device

From what I can gather 'Billboard' just means that switching to alternate mode failed because of some issue.

In monitor settings, I only see the built-in monitor. Similarly, I installed ARandR and no other outputs appear.

Adapter

I have tried a few adapters. The one I'm trying currently is 'plugable USB-C to HDMI adapter'. It is stated to support Linux and any USB-C port that supports DisplayPort Alternate Mode.

Laptop

I have the ASUS C523N. It is stated to support driving a display from usb-c, but nothing more specific: spec sheet.

This is a Chromebook. When I boot into Chrome OS, the display works through the same USB-C port.

Other details

Kernel: 5.15.0-50-generic

jasper@crbook1:~$ cat /boot/config-$(uname -r) | grep TYPEC_DP
CONFIG_TYPEC_DP_ALTMODE=m

Ubuntu: 22.04.1 LTS

dmesg:

[80603.451223] usb 1-2: new full-speed USB device number 8 using xhci_hcd
[80603.610532] usb 1-2: not running at top speed; connect to a high speed hub
[80603.628180] usb 1-2: New USB device found, idVendor=0bda, idProduct=2172, bcdDevice= 1.00
[80603.628202] usb 1-2: New USB device strings: Mfr=17, Product=18, SerialNumber=19
[80603.628210] usb 1-2: Product: BillBoard Device
[80603.628217] usb 1-2: Manufacturer: Realtek
[80603.628223] usb 1-2: SerialNumber: 00000000000000000

Related issue

The only issue that I can find matching is this: USB-C to HDMI not working on Dell XPS 13 9370

The solution there was just to try another adapter. I'm on my third purchase and I can't always get returns. This one explicitly says it supports Linux. I will try to contact their support and report back here. I really can't keep buying cables and hoping that it works. I'm looking to at least get a handle on what the problem is here.

New boot messages after upgrading to 22.04.1 https://askubuntu.com/questions/1426579/new-boot-messages-after-upgrading-to-22-04-1

Prior to upgrading to 22.04.1 the screen never presented boot [error] messages. Now I get a series of boot messages that I'm clueless about. Would anyone know anything about the messages that are shown below?

[    0.213170] pnp 00:01: can't evaluate _CRS: 12311
[    0.579031] ima: Error Communicating to TPM chip
[    0.582101] ima: Error Communicating to TPM chip
[    0.585673] ima: Error Communicating to TPM chip
[    0.589218] ima: Error Communicating to TPM chip
[    0.592686] ima: Error Communicating to TPM chip
[    0.595877] ima: Error Communicating to TPM chip
[    0.599619] ima: Error Communicating to TPM chip
[    0.603061] ima: Error Communicating to TPM chip
/dev/sda2: clean, 410292/6250496 files, 8657488/24999936 blocks
[    6.978283] mtd device must be supplied (device name is empty)
[   11.967777] mtd device must be supplied (device name is empty)
_
Ubuntu doesn't recognize my internal hard drive https://askubuntu.com/questions/1395756/ubuntu-doesnt-recognize-my-internal-hard-drive

All of a sudden yesterday when I boot Ubuntu 20.04 from EFI (grub) it just goes to a black screen. In the BIOS it recognizes my hard drive as the 250GB Samsung SSD, but when I go to load Ubuntu, it boots to a black screen.

So I loaded Ubuntu from a USB and when I went to install there was nothing on the Drives page. I cancelled the installation and went to "Try Ubuntu" and into Disks and the only disks it showed were the loop stuff and the 32GB USB stick. It didn't pick up the 250GB internal hard drive.

I don't mind a clean reinstall if something is corrupted, but I do need files off the original install.

ubuntu@ubuntu:~$ sudo lsblk -f
NAME   FSTYPE   LABEL                     UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squash                                                               0   100%   /rofs
loop1  squash                                                               0   100%   /snap/core
loop2  squash                                                               0   100%   /snap/gnome
loop3  squash                                                               0   100%   /snap/gtk-
loop4  squash                                                               0   100%   /snap/snap
loop5  squash                                                               0   100%   /snap/snap
sda    iso9660  Ubuntu 20.04.3 LTS amd64  2021-08-19-11-03-38-00
├─sda1 iso9660  Ubuntu 20.04.3 LTS amd64  2021-08-19-11-03-38-00              0   100%   /cdrom
├─sda2 vfat     54C5-9C6C
└─sda3 ext4     writable                 9fbee645-7648-4108-a9c2-9690006d103a 16.3G   32%   /var/crash
sr0
ubuntu@ubuntu:~$
What is the effect of packages installed by snap on memory usage? https://askubuntu.com/questions/1364420/what-is-the-effect-of-packages-installed-by-snap-on-memory-usage

I never used snaps before. When reading the vague descriptions I assume it's implemented in a way really similar to containers.

This makes me assume that programs in snaps all use their own libraries. But because 'regular' programs use the default libs from the system I assume multiple libs will be loaded which will cost a lot of memory...

Is this indeed the case ?

Related: Are there other disadvantages with running programs installed with snaps ?
(Note that I mention "running" instead of installing)

Desktop stuck in alt-tab mode https://askubuntu.com/questions/1344748/desktop-stuck-in-alt-tab-mode

I don't know how I managed to do this but my desktop is stuck in the alt-tab application selector mode. Clicking on an application does nothing, it stays on the zoomed out view.

Any tips on how I can escape this?

Things I have tried so far.

  • Restarting computer, works initially then goes back to zoomed out mode when changing apps.

  • Restarting lightdm.

  • Using super+w and other common keyboard shortcuts.

Cheers

EDIT

Seems to be a glitch with the mouse input, after rebooting a few times it seems to be back to normal.

screenshot

Apache proxy error failed to make connection to backend 127.0.0.1" https://askubuntu.com/questions/1341919/apache-proxy-error-failed-to-make-connection-to-backend-127-0-0-1

I can't connect to my company website. it shows service unavailable.

Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.4.18 (Ubuntu) Server at www.leangiap.com Port 44

I tried to track using curl command and it returned 503 Service Unavailable.

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html>

<head>
    <title>503 Service Unavailable</title>
</head>

<body>
    <h1>Service Unavailable</h1>
    <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p>
    <hr>
    <address>Apache/2.4.18 (Ubuntu) Server at 47.254.196.130 Port 80</address>
</body>

</html>

I checked the apache error.log. It showed

apache proxy error failed to make connection to backend 127.0.0.1

Can anyone help??? Thanks

screenful of log

Problems with Chrome browser after suspending the computer on Ubuntu 20.04 https://askubuntu.com/questions/1273399/problems-with-chrome-browser-after-suspending-the-computer-on-ubuntu-20-04
  • Kubuntu 20.04, 64 bit
  • GPU: Geforce GT610
  • nvidia-driver-390
  • Chrome Version 85.0.4183.83
  • Intel i5-4430, core 4, 4 thread , 3GHz
  • RAM: 16GB

Each time I go into suspend mode and then resume, Chrome browser displays the current tab as full of sand of colors, something like dithering in image processing.

screenshot

Other tabs display glitches too.

The current solution is to close and reopen the browser.

I tested nvidia-driver-418 but got a black screen problem and reinstalled nvidia-driver-390.

The problem is more evident in Chrome, but it sometimes appears in vscode in small areas. There, hovering the mouse over the affected place or resizing the window fixes the problem. In Kubuntu the avatar of the user in the application launcher also shows dithered.

screenshot

I tested in the same machine with fedora 32 workstation(gnome), nvidia driver, and had the same problems with Chrome browser.

ubuntu-drivers output

Could it be a GPU problem?

Can only boot Ubuntu 20.04.1 LTS when holding shift https://askubuntu.com/questions/1269920/can-only-boot-ubuntu-20-04-1-lts-when-holding-shift

I have a laptop which purely runs Ubuntu (no dual-boot), and whenever I boot my laptop the boot screen goes on without stopping. When I first came across this issue I tried to access GRUB by holding down shift while I booted, however this just caused Ubuntu to boot normally and did not show the GRUB screen at all. I thought this issue could be because GRUB wasn't my default boot manager, however after running boot-repair, the issue still persists.

Ubuntu from 32 to 64 bit fresh install - how to reinstall the same packages? https://askubuntu.com/questions/1022604/ubuntu-from-32-to-64-bit-fresh-install-how-to-reinstall-the-same-packages

I would like to update an Ubuntu installation from 32 to 64 bit. I'd also like to save most of the configurations, especially the installed packages because I have added and deleted quite a big number of them.

So the basic idea is to backup the /etc, /var, and /home directories (actually these are two separate partitions, so I suppose that I could simply not format them), make a fresh installation, and reinstall the old packages. Then copy the relevant /etc/directories from the older installations.

What I am trying to find is how to automate the package reinstall, and if it's possible, to automate the /etc restore.

Are the instruction found in this answer still valid? https://ubuntuforums.org/showthread.php?t=261366

I found out how to do this recently and thought it might be helpful to >some people. To output this information to a file in your home directory >you would use,

Code: dpkg --get-selections > installed-software And if you wanted to use the list to reinstall this software on a fresh ubuntu setup,

Code: dpkg --set-selections < installed-software followed by

Code: dselect

Command line connect to L2TP Windows Server VPN https://askubuntu.com/questions/1017717/command-line-connect-to-l2tp-windows-server-vpn

I have been searching for a couple of days not much luck as and everything i come across relies on using the Network Manager UI.

Could someone provide me with a noobish tutorial on how I would configure the ubuntu server to automatically (on startup) connect to an L2TP over IPSec VPN with Windows Login credentials?

It does not have to be L2TP over IPSec, I do also have the Windows Server configured to allow PPTP VPN connections but I would prefer L2TP as it's more secure.

I would also need to know if there is a special configuration I need to prevent the Internet connection being tunneled through the VPN as I know windows does this by default and it has to be turned off on the VPN Network Adapter in windows if the same need to happen on the Ubuntu server I will need to know how to do that so I don't lock myself out of the server by it losing its internet connection :D

The reason for this is that I have quite a lot of attempts on the SSH Port's so I want to set the Hardware Firewall in front of the server to not allow SSH through it and make it so the only way to connect to the SSH server is via the Corporate VPN.

Ubuntu doesn't bind usb device after reboot https://askubuntu.com/questions/888752/ubuntu-doesnt-bind-usb-device-after-reboot

My problem is that when I restart my computer, Ubuntu recognize my wireless keyboard and mouse usb dongle, but it doesn't recognize my usb wireless network adapter. Here is my lsusb results:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The device that is not recognized is:

"Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter"

As soon as I manually unplug it and plug it back again, I can see it in my usb devices list and it works fine, but I can't do that every time I reboot my computer. I'm looking for a way to fix this or at least put something in my .bashrc to unplug this specific device and put it back so it works. Or maybe restarting that usb port to force it to check again. Any solutions is a huge help.

I know that there are a lot of questions similar to this one but I ask it because none of them worked for me.

java: error while loading shared libraries: libjli.so cannot open shared object file: no such file or directory https://askubuntu.com/questions/871401/java-error-while-loading-shared-libraries-libjli-so-cannot-open-shared-object

When I try to run any java program or simply java -version in my ubuntu 14.04 system getting the following error:

"java: error while loading shared libraries: libjli.so cannot open shared object file: no such file or directory"`

I have tried the solution in the this link but it doesn't work

Please help me how to make java work in my system

How to use k380-function-keys-conf https://askubuntu.com/questions/813814/how-to-use-k380-function-keys-conf

I am trying to change the default setting for the function keys on k380 Bluetooth keyboard.

They are currently working as a special keys to control such as audio volume, unless I press "fn" key at the same time. I searched around and found another thread in this site.

Logitech K380 bluetooth keyboard - make function keys default

I managed to download k380-function-keys-conf at GitHub.

The files consiste of the following 4 files. LICENCE, README.md, buils.sh, k380_conf.c

I read README as well as the links included in README, but still got no idea how to use buils.sh, k380_conf.c to change k380's default function key setting.

I am using Mint Cinnamon 18 which is based on Ubuntu 16.04. I am not an absolute beginner but not an advanced user either.

If anyone can help me, it will be greatly appreciated.

No Network Connection - ifconfig shows only lo - lshw -c network says *-network unclaimed https://askubuntu.com/questions/755217/no-network-connection-ifconfig-shows-only-lo-lshw-c-network-says-network

I got a new ThinkPad E460 with no OS installed, but had an ubuntu 13.10 USB stick around which I used to install ubuntu 13.10.

The OS works fine, however I can't connect to the internet through Ethernet or Wireless. (Also the clickpad won't work.)

I am not very used to linux, but know a little how to use a shell.

So far, to solve my problem, I googled and found numerous approaches, of which none worked for me, but I found some things out.

ifconfig -a returns:

eth0      Link encap:Ethernet  HWaddr 02:cd:fe:b5:c4:17  
          inet addr:172.20.10.3  Bcast:172.20.10.15  Mask:255.255.255.240
          inet6 addr: fe80::cd:feff:feb5:c417/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18970 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18365 errors:2 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12962022 (12.9 MB)  TX bytes:2967244 (2.9 MB)

lo    Link encap:Local Loopback  
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:4564 errors:0 dropped:0 overruns:0 frame:0
      TX packets:4564 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0 
      RX bytes:451662 (451.6 KB)  TX bytes:451662 (451.6 KB)

The eth0 should be my iPhones Mobile Hotspot via Bluetooth.

sudo lshw -c network returns:

 *-network UNCLAIMED     
   description: Network controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@0000:01:00.0
   version: 99
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: latency=0
   resources: memory:f1200000-f1201fff
 *-network UNCLAIMED
   description: Ethernet controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1f.6
   bus info: pci@0000:00:1f.6
   version: 21
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: latency=0
   resources: memory:f1300000-f131ffff
 *-network
   description: Ethernet interface
   physical id: 2
   bus info: usb@1:3
   logical name: eth0
   serial: 02:cd:fe:b5:c4:17
   capabilities: ethernet physical
   configuration: broadcast=yes driver=ipheth ip=172.20.10.3 link=yes multicast=yes

From what I understood, the UCLAIMED means a driver issue, however I failed to load them through backport. Loading a new Version of Ubuntu or any other OS is not possible, since I don't want to blow my phones data plan.

For now I have to leave, but will be back in about 2 hours. Any help will be greatly appreciated and any information needed to solve the problem, I will provide.

Bluetooth disabled and not showing up in LSPCI - ASUS G750JM https://askubuntu.com/questions/521190/bluetooth-disabled-and-not-showing-up-in-lspci-asus-g750jm

The modem installed properly on 14.04, it worked on installation of ubuntu. It's a Broadcom modem, and it's tied into the Broadcom bluetooth card. But the bluetooth does not function on 14.04. Ubuntu says it's disabled what can I do to fix this? It doesn't say that it's not there, it just says disabled even after I turn it on.

rfkill list all
    0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    1: brcmwl-0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    2: asuswlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    3: asus-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: no

UPDATE: I removed asus-bluetooth's soft block by running the following commands:

$sudo modprobe -b asus-wmi
$rfkill unblock all

But it's still disabled in settings and I can't use it and it returns to being disabled after a short time

UPDATE:

$hcitool scan
Device is not available: No such device

$ lsmod | grep asus

asus_nb_wmi            16990  0 
asus_wmi               24191  1 asus_nb_wmi
sparse_keymap          13948  1 asus_wmi
wmi                    19177  2 mxm_wmi,asus_wmi
video                  19476  2 i915,asus_wmi

UPDATE:

$ lspci
    00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
    00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
    00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
    00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
    00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
    00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
    00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
    00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
    00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
    00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 
    00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
    00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
    00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
    01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev ff)
    03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03)
    04:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)

Am I to assume that since it doesn't list bluetooth anywhere in that list that Ubuntu just doesn't realize that I have a bluetooth device? It would explain why I've tried virtually everything to enable it but it won't work. Please help.

UPDATE:

Since upgrading to 14.10 bluetooth works as long as I rfkill unblock all

UPDATE:

and now since I removed ubuntu and reinstalled from scratch 14.10 it works fine without a hitch

import Certificate in Pdgin for Microsoft Lync 2013 https://askubuntu.com/questions/464716/import-certificate-in-pdgin-for-microsoft-lync-2013

I follow this issue to configure PIdgin for MS Lync 2013 .

I get this message :

Web ticket request to https://rproxy.mycompany.com:443/CertProv/CertProvisioningService.svc failed

enter image description here

Known that settings has been configured as following: enter image description here

And No proxy: enter image description here

i received this certificate from MS sysadmin .

enter image description here And i don't know if it is useful in Ubuntu . If so , How can i import it?

And Why rproxy appeared in message error even there is no proxy in my settings .

I mean :

https://rproxy.mycompany.com:443/CertProv/CertProvisioningService.svc

UPDATE :

I found where can i import certificate :

enter image description here

However , i get new error message:

SSL Connection Failed

Known that Authentication Scheme is: Kerberos , not TLS-DSK

pulse audio volume control https://askubuntu.com/questions/303877/pulse-audio-volume-control

having some trouble with pulse audio volume control.

When run it, I get the error message you can see in the window in the screen shot below.

enter image description here

However when I run start-pulseaudio-x11 in the terminal, you can see the output is "unknown job".

Does anybody know what I could do to get pulse audio volume control working again? Thanks!