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.

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.

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

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?

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.

I wish to install ubuntu on an XP3 machine. This has a 1Tb hdd, with around 900Mb free space.

I created another priary unformatted partition which I then partitioned, but left the third as unallocated space.

I created my ubuntu stick with version 16.04.6 for x86 windows.

When I selected the install option, ubuntu gave me the options to remove the windows system or install alongside.

When I selected the 2nd option, Ubuntu ignored the empty partitions and specified its own partition.

At which pointed I bailed out.

Do I take it that for dual boot Wndows/Ubuntu, Ubuntu creates its own partition, even if windows occupies the sole partition on the HDD?

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?

I recently purchased a PCSpecialist Lafite Pro 16 and installed Ubuntu 25.10 running Kernel 6.17. Everything works flawlessly except for the keyboard backlight, which I cannot turn on or control.

Specs:

• Model: PCSpecialist Lafite Pro 16 AMD
• CPU: AMD Ryzen AI 7 350 8 Core (5.0 GHz Turbo, 50 AI TOPS)
• GPU: Integrated AMD Radeon™ 860M
• Screen: 16" QHD+ (2560 x 1600) 240Hz LED
• OS: Ubuntu 25.10
• Kernel 6.17.0-8-generic

I contacted PCSpecialist support regarding Linux drivers, and they confirmed that the feature is software-dependent: "The keyboard lighting is managed via the Control Center software, which is compatible only with Windows. At the moment it is not supported on Linux and we have no alternatives to propose."

What I have tried so far (and failed):

• Tuxedo Drivers:
  I attempted to install tuxedo-drivers (via PPA and source), but compilation failed. The source code seems incompatible with the newer Kernel 6.17 (errors regarding platform_driver return types and X86_MATCH macros).

• Kernel Parameters:
  I tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor". This broke the screen brightness controls entirely and did not enable the keyboard light. I have since reverted this to default.

• OpenRGB: I installed the correct udev rules and ran the latest AppImage (with libfuse2t64 support). The application launches but does not detect the keyboard controller (it only detects RAM/Motherboard).

• Standard Tools: brightnessctl -l lists amdgpu_bl1 (screen) and standard LEDs (capslock, numlock), but no device for the keyboard backlight.

System Info (dmidecode):

Handle 0x0001, DMI type 1, 27 bytes
System Information
    Manufacturer: PCSpecialist
    Product Name: Lafite Pro 16 AMD
    Family: Lafite Pro 16 AMD Systems

My Question: Since the official "Control Center" is Windows-only, is there a known WMI driver, kernel module, or reverse-engineered tool that can interface with the EC (Embedded Controller) for this specific AMD Ryzen AI platform?

Any guidance on how to enable the backlight would be appreciated.

I want to write Russian text in LaTeX. I searched the web but did not find something which works.

I have tried:

`sudo apt install texlive-lang-cyrillic`

I got following answer: dpkg avbröts. Du måste köra ”sudo dpkg --configure -a” manuellt för att korrigera problemet. Which almost means: dpkg disrupted. You must run ”sudo dpkg --configure -a” manually to correct the problem. I ran: sudo dpkg --configure -a I get dpkg error: needs an action to perform I do not what it means.

Can anybody help me?

Thank you!

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.

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.

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?

Welcome :)

I have computer, NUC13 (i5, 64GB ram) with Ubuntu Server 24.04, equipped with two i226-V NICs (one built in, another one is NUC add-on). I observed some network issues, so I tested it with iPerf3. Results are very poor. iperf3 -c x.x.x.x results in speeds around 10-15-30Mbps, while iperf3 -c x.x.x.x -R shows correct transfers (up to 2.5Gbps). It may be worth to add, that UDP test iperf3 -c x.x.x.x -u -b 1000M succeed with 1Gbps. Problem exists on both NICs. I set up iperf binding to specific interfaces to isolate them during test without success. They behave exactly the same.

I already tried disabling eee, changing qdisc, using HWE kernel 6.14 and finally - upgraded Ubuntu to 25.10 with kernel 6.17. Nothing can fix my situation.

Im pretty much sure that networking itself is fine, as I have another machine connected to same switch which don't have any problems with network saturation. Its also not iperf3 issue, because openspeedtest instance shows the same problem.

ethtool output looks like this

Settings for enp86s0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
                            2500baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
                            2500baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: 2500Mb/s
    Duplex: Full
    Auto-negotiation: on
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: yes

Any ideas/advices can be helpful.

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?

I am trying to communicate with an HP48SX calculator over serial interface with C-Kermit and am getting an error message when trying to set the parameters to be compatible with the HP. Using Ubuntu 20.04LTS on a Dell Inspiron 17R. The message is:

Sorry, write access to UUCP lockfile directory denied

I can find no lockfiles on my system nor any reference to UUCP. The USB-to-DB9 adapter is recognized as ttyUSB0. I have searched with Google and tried various fixes offered there to no avail.

Any help would be greatly appreciated.

I am using a serial cable thru USB as we don't have RS-232 anymore which was the old way to do this under Windows. I have downloaded and compiled C-Kermit which created the necessary software to do this. There are various parameters that need to be set so the calculator can respond. Here they are :

./wermit                ; Start C-Kermit
; The following commands are entered at the "C-Kermit>" prompt...
set port /dev/ttyUSB0
set speed 9600          ; Serial port speed, HP48 defaults to 9600, also supports 4800 2400 1200
set carrier-watch off   ; It's not a modem connection so ignore carrier signal state.
set modem type none     ; No modem is involved; don't send AT commands.
set flow none           ; Flow control is not supported by HP48.
set parity none         ; 8 data bits, no parity
set control prefix all  ; HP48 Kermit requires all control characters to be encoded in printable form.
set file type binary    ; Might not always be needed.*  

As soon as I try to enter any of these 'set' commands, I get the message I listed above. On the C-Kermit website, there are all the necessary instructions and the author did this on his machine with no problems so I think it is something missing in my Ubnutu 20.04 installation.

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.

I have a server with some instances of TigerVNC running to allow for remote access. I am starting them as a systemd service.

Since upgrade to Ubuntu 20.04 to 22.04 the servers fail to start with error:

Session startup via '/home/VNC/.vnc/xstartup' cleanly exited too early (< 3 seconds)!

Can anyone point me the right direction?

Here is what I have for service def:

[Unit]
 Description=Remote desktop service (VNC)
 After=syslog.target network.target

[Service]
  Type=forking
  User=VNC
  PIDFile=/home/VNC/.vnc/%H:%i.pid
  ExecStartPre=-/usr/bin/vncserver -kill :%i
  ExecStart=/usr/bin/vncserver -localhost no -depth 24 -geometry 1920x1080 :%i
  ExecStop=/usr/bin/vncserver -kill :%i

[Install]
  WantedBy=multi-user.target

Here is what I started with for &HOME/.vnc/xstartup:

#!/bin/bash
xhost +
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
export XKL_XMODMAP_DISABLE=1
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
autocutsel -fork
startxfce4 &

I read an article on this forum that talks about new vncserver needs to run in foreground so take the "&" off the startxfce4 command. I did this and the service starts. I can access from remote computer, however, after about 1min the service stops with an error: Job for vncserver@1.service failed because a timeout was exceeded.

Here is the systemctl status:

VNC@HP-EliteDesk-800:~/.vnc$ systemctl status vncserver@1.service
× vncserver@1.service - Remote desktop service (VNC)
     Loaded: loaded (/etc/systemd/system/vncserver@1.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Mon 2022-08-22 10:31:01 MDT; 2min 40s ago
    Process: 14603 ExecStartPre=/usr/bin/vncserver -kill :1 (code=exited, status=1/FAILURE)
    Process: 14606 ExecStart=/usr/bin/vncserver -localhost no -depth 24 -geometry 1920x1080 :1 (code=exited, status=0/SUCCESS)
        CPU: 4.972s

Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Activating service name='org.gnome.evolution.dataserver.Calendar8' requested by ':1.25' (uid=1001 pid=14753 comm=>
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Activating service name='org.gtk.vfs.Metadata' requested by ':1.13' (uid=1001 pid=14730 comm="xfdesktop " label=">
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Successfully activated service 'org.gtk.vfs.Metadata'
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Activating service name='ca.desrt.dconf' requested by ':1.41' (uid=1001 pid=14941 comm="/usr/libexec/evolution-ca>
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Activating service name='org.gnome.evolution.dataserver.AddressBook10' requested by ':1.41' (uid=1001 pid=14941 c>
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Successfully activated service 'ca.desrt.dconf'
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Activating service name='org.freedesktop.Tracker3.Miner.Extract' requested by ':1.26' (uid=1001 pid=14786 comm="/>
Aug 22 10:29:30 HP-EliteDesk-800 dbus-daemon[14633]: [session uid=1001 pid=14631] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'

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:~$

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)

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.

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

Logitech doesn't have an official driver for controlling the LED effects for Ubuntu. Is there any custom solution working (For example keyleds, openrgb, solaar, libratbag, anything else)?

As you know full-screen sharing is a missing option in Ubuntu Wayland session. I was going to join an online competition through google meet. Although you can share individual windows but not the entire screen. After searching for possible solutions I came across pipewire(I really don't know what it's).

I used their official manual to build it from source but there were no pages about its dependencies so I used apt-get install "dependency-name"* to install the available packages contain for each cmake dependency error dependency. By that, I got a lot of garbage packages installed in my system. But after installation, it was not working with Chrome (after enabling webrtc-pipewire flag) or Firefox. After struggling one hour I removed all installed files and packages from my system. I also tried it with Ubuntu's official pipewire packages(which was of an older version)

sudo apt install pipewire gstreamer1.0-pipewire libpipewire-0.2-1 libpipewire-0.2-dev libpipewire-0.2-doc

It made google meet not joining the conference. I also checked this manual and failed. I installed each of it's missing dependencies and failed.

What is the proper way to install pipewire on my 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.

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.

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

Could it be a GPU problem?

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.

I'm recently getting this error when trying to open a simple zip file using file-roller, aka Archive Manager.

I've unzip, unrar and 7zip installed already.

However, when I try decompressing the files using unzip in Terminal they work fine - except when using the Archive Manager GUI application. The Archive Manager installed is of version 3.28.0.

This is the error message box I'm getting:

How do I solve this? Is there a way to check the logs pertaining to the Archive Manager to diagnose the issue?

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.

I get it after updating in Synaptic Manager

I recently did a clean install of Ubuntu 17.04 from 16.10.

error message:-

W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/samba-libs_2%3a4.5.8+dfsg-0ubuntu0.17.04.1_i386.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

How can I remove the last 5 lines in bash history? So that when I reload the Ubuntu server, or restart it they're not there at all?

history -c only removes it from current session, but when I re-login I see the commands again, I want to clear the last 5.

I've run:

history

Then i'll see the numbers of the commands e.g:

  489  cd ..
  490  cd .zshrc
  491  cat .zshrc

Then I run for example:

history -d 489
history -c 

Then i close terminal and reopen it and i still see line 489 it was only deleted for that current session, how do I delete it permentantly from all sessions going forward?

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

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.

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!

I need to use two different Windows applications, one works well with Wine 1.4 but not on Wine 1.5 and the other application works well with the later version but not with the former.

Is there a way to have both versions of Wine installed, specifying which application should run with which Wine version?