I installed Ubuntu 25.10 on a Dell 16 Pro Plus PB16250 Laptop and noticed the speakers builtin to the laptop don't work (Linux Mint 22.2 USB Live Mode, speakers do work). Not sure what info I need to add to this. I am new to Linux.

00:1f.3 Audio device: Intel Corporation Lunar Lake-M HD Audio Controller (rev 10) (prog-if 80)
    Subsystem: Dell Device 0cdd
    Flags: bus master, fast devsel, latency 64, IRQ 191, IOMMU group 20
    Memory at 3015200000 (64-bit, non-prefetchable) [size=512K]
    Memory at 3015000000 (64-bit, non-prefetchable) [size=2M]
    Capabilities: [50] Power Management version 3
    Capabilities: [c0] Vendor Specific Information: Intel <unknown>
    Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Kernel driver in use: sof-audio-pci-intel-lnl
    Kernel modules: snd_sof_pci_intel_lnl, snd_hda_intel

00:1f.3 Audio device [0403]: Intel Corporation Lunar Lake-M HD Audio Controller [8086:a828] (rev 10)
    Subsystem: Dell Device [1028:0cdd]
    Kernel driver in use: sof-audio-pci-intel-lnl


Speaker doesn't show up as an option at all in sound section.
The system does recognize the 2 speakers in the 2 monitors that are connected by HDMI but no sound plays from them either.

Sound does come out of my USB headset (Jabra).  I have disconnected it to make sure the USB headset wasn't the issue.


**** 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: 0/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

It seems that Clam AV is not being supported. Many other antivirus claim to work on Ubuntu but do not. Is there an antivirus that is in use NOW?

I replaced my Windows 10 Pro with Ubuntu 24.04 recently...I'm not new to Linux or Ubuntu.

My computer is an HP Compaq 8200 Elite with 8gb RAM and an i5 processor. It is EFI capable but does not have the secure boot available. I did update my Grub to reflect this. It should be okay for what I'm doing as I understand things.

Ubuntu keeps randomly locking up while I'm editing my Zen Cart PHP files.

I usually have 2 to 4 tabs open in Firefox, 3 or 4 files in gedit or text edit, and 2 to 4 nautilus file manger windows.

I have reduced a Firefox setting for "instances" from 8 to 4, tried running in the alternative graphics environment, printed journalctl, and kept open programs to a minimum when possible.

When it locks up, I've tried Alt SysRq REISUB but it will not work...even if I wait 10 second between each letter. Ctl Alt Del...nothing happens. Plugging in a wired mouse and keyboard does not work. My Blackweb RF keyboard becomes unresponsive. I have disconnected and reconnected it to try and unfreeze the system but nothing happens. The only way to get out of the freeze is a hard power off reset and I know that is not the correct way to exit a freeze...but necessary in my case.

I'm writing this in the alternate graphics startup so I don't know if running in this mode is going to fix my issue.

My system is up to date.

Could someone, please, guide me in the correct direction to resolve this?

Thanks.

absolute beginner no prior experience . my end goal is to use a waveshare driver hat (A) with a pizero2w and gamepad for wireless control of waveshare arm m3.

I have installed ubuntu 22.4.3 lite 64 bit on a 32gb micro sd card on the pi, no problem to ssh to the pi from windows 11 laptop.

Following the you tube video ( How to Install ROS 2 Humble on Raspberry Pi) seamed to be going ok till the end of the install when I get (unable to locate package dependency_packagefor jammy 0.2.1-100 all) message. I tried looking up how to fix but nothing has worked ?

I,m not sure if Ubuntu 22.4.3lite 64 bit is the one I should have used in the first place ? For a 75 year old who has no experience with any robotics, and tons of info (all with a different method or info) the more I look the deeper and more confusing all this gets, till I have no clue what I,m doing ! Any help or advice would be appreciated ! thanks for reading this

I had an issue in 25.04 as the system was unable to go in sleep mode. Displays went off first, but login screen appeared again. This was resolved by switching back from Wayland to Xorg.

Same issue appears now that I moved to 25.10, but this upgrade no longer gives the possibility to choose Xorg instead of Wayland. I understand Wayland is now the only gdm available so I have no immediate solution.

My computer is based on AMD 5 CPU, with Radeon Vega integrated graphics.

What should I investigate further ?

Thanks in advance.

Is there somebody have installed this application Howler_2026_0081.exe with success on Ubuntu ? If yes, thanks to tell me how ! Thanks.

I'm new with Ubuntu.

I'm french: sorry for my English level.

I have a problem with my application menu.

Many applications are list with multiple icons for the same application (sometimes 20 icons).

How can i delete the icons in order to have only one icon for each applications ?

Thanks for your answer.

I want to emulate a piece of commercial hardware with an LTS24.4 system. The target system is controlled by telnet, via a non-standard port. I cannot see anything in /etc/inet that would allow me to create a second port. If it is possible, could someone please point me in the right direction?

I should be able to watch YouTube videos edit some basic documents and browse the internet fluently

My pc-kernel snap somehow became disabled, so I wanted to enable it (to update it afterwards). However, I couldn't do it due to this package being refreshed.

➜  ~ sudo snap enable pc-kernel              
error: snap "pc-kernel" has "auto-refresh" change in progress

I found out that change has been pending for 4 days, so I decided that it must be broken and aborted it. However, instead of going to "Aborted" state, it became "Undo".

➜  ~ sudo snap abort 4         
➜  ~ snap changes     
ID   Status  Spawn                     Ready  Summary
4    Undo    4 days ago, at 13:39 MSK  -      Auto-refresh snaps "snapd", "pc-kernel", "firmware-updater"

At this point, my snaps are still locked, and I can't do anything about it: snap abort, reboots, snapd restarts - whatever I do, change is still in "Undo" state. I've tried setting KeyringMode=shared as in https://bugs.launchpad.net/snapd/+bug/2117444 , but that didn't help. Also, there is no documentation about changes and manually reverting those. Is there anything I can try, or did this snap bug just make my system unupdatable?

A few months ago I migrated from W11 to ubuntu 25.04 on my laptop, HP Elitebook 845 G8 because I got, lets say, very angry at windows. Almost everything is fine, except support for my LTE modem - XMM7360 (internal PCIe device, not USB) which is simply not working. It is important for me, as I work a lot far away from any wifi connection.

Firstly, I've tried a few options found on google and once managed it to start and connect but it was problematic and did not survive any restart or sleep. In meantime I got external, usb lte modem which works (most of the time), have its own problems, but it is enough as a temporary solution.

After upgrading to Ubuntu 25.10 i decided to give it a try again and try internal modem because i thought that is should work out of box already after seeing that got accepted and merged.

The main problem is that on previous Ubuntu, internal modem was "visible" by the system and modem manager was showing "No SIM card inserted" message, but now, after upgrade it is completely missing. I've tried all scripts I could find, re-do all steps made in previous attempts, nothing. Modem is enabled in BIOS, and visible in lspci as usual. But nothing more.

Tried compiling driver from this repo/instruction but it failed right away after make command complaining about non-existent functions. I guess it is no more compatible with newer libraries used by 25.10?

I do not really want to go down rabbit hole of modems and drivers in ubuntu, but now I'm seriously confused what to do to get it working.

Anybody has any advice what to do?

I followed this guide https://itsfoss.com/share-folders-local-network-ubuntu-windows/ to share a folder on an Ubuntu PC and access it from a Windows 11 PC.

Sadly it doesn't work and other, more complicated, guides I could find are bringing the same results.

What I tried on Windows PC:

• all network settings for filesharing are active and it is possible to access folders on another Windows laptop.

• Ubuntu PC can be pinged but isn't visible under Network

• Installing SMB 1.0 Client and Server

• Accessing shared folder with \\IP\foldername or \\UbuntuPCname\foldername results in non-descript error

• setting up a networkdrive also fails

What I tried on Ubuntu PC (24.04.3 LTS):

• follow mentioned guide from beginning to share a folder in user homefolder and folder on separate drive

• adding samba to ufw

• enable/disable ufw

• removing nautilus and samba follwing this guide https://thelinuxcode.com/how-to-remove-samba-from-ubuntu/

• reinstalling samba and nautilus

• adding shared folder to smb.conf manually with different variations according to multiple guides

• confirmed that domain workgroup is identical

Nothing works and I hope someone can tell me what I am missing or doing wrong, as it is shown to be so easy according to all of those guides.

Thanks for the help!

"edit"

Ran a testparm command with the following results:

Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)

Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

Global parameters

[global] log file = /var/log/samba/log.%m logging = file map to guest = Bad User max log size = 1000 obey pam restrictions = Yes pam password change = Yes panic action = /usr/share/samba/panic-action %d passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully . passwd program = /usr/bin/passwd %u server role = standalone server server string = %h server (Samba, Ubuntu) unix password sync = Yes usershare allow guests = Yes idmap config * : backend = tdb

[printers] browseable = No comment = All Printers create mask = 0700 path = /var/tmp printable = Yes

[print$] comment = Printer Drivers path = /var/lib/samba/printers

[Public] force user = pit guest ok = Yes path = /srv/Public read only = No

"edit"

Windows Error Message in german: Windows 11 Error Message

Translation:

\Skynet\Public couldn't be accessed (post here doesn't show a double )

It is the "standard" error message when trying to access an address. Also comes up if the wrong address is entered.

I've noticed recently, maybe in the past year, that many new installations of Ubuntu and its derivatives seem to deviate from old-school DNS settings. I try to nslookup a box on my LAN or VPN using the local DNS server given by DHCP, and it gets no match from 127.0.0.53. When I nslookup that same name and specify the DNS server that's given by DHCP, it works fine. I'd expect the system to get a DNS server from DHCP and then use it everywhere. With systemd-resolved, it seems like that DHCP setting isn't used.

The local caching stub server doesn't respect the DHCP setting. I can nslookup somename.mynetwork.local and get no match. Then, nslookup somename.mynetwork.local 10.1.2.3 and it returns the right host. The local cache does not look at the local DNS server. Furthermore, resolvectl does show the correct DNS server. It just never queries it. I confirmed this from the DNS server logs. There is no traffic coming from the new Ubuntu host. When I add DNS=10.1.2.3, Domains=mynetwork.local to resolved.conf, it works fine. The problem is that I'm now hardcoding an IP address instead of using DHCP. This is not intuitive because resolvectl shows the right DNS server from DHCP the whole time.

I can make zone-specific DNS settings, force overwrite resolv.conf, or do other manual tweaks to solve the immediate problem. That seems weird to have to do on every fresh install. I wonder if there's a better, standard way to make a fresh install use the DNS settings I want. That is, install a fresh Ubuntu Server or Desktop, check a box or something like "use DHCP for DNS," and then reboot and not think about it again. Thanks.

Output of resolvectl status

Global
         Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub

Link 2 (eth0)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
       DNS Servers: 10.1.2.3

I'm moving from Windows11 to Kubuntu 25.10 KDE Plasma Version: 6.4.5. Thunderbird 144.0.1 (64-bit) Windows 11. Thunderbird 140.3.0esr (64-bit) Linux.

I know what to do to copy my profile from Windows to linux, but the version needs to be the same. So I need to update Thunderbird. How do I do that?

Thanks very much!

arbyars

I have Ubuntu 24.04.03 LTS with GPU I have GPU Nvidia GeForce RTX 3060

installed and was working fine for 3 months.

I had only one issue that after entering username password, using it for a while and locking then logging-in again black screen appeared.(other issue How to fix Ubuntu 24.04.3 LTS Black Screen On Un-Suspend and Nvidia GeForce RTX 3060?)

Now the problem is fatal! Just after turning on the pc, selecting Ubuntu (in dual boot menu with windows) I see black full screen!!!

I tried Ubuntu recovery mode, and all options available and all show fully black screen!

Please I need help, it took me around 1 month to setup all the software in Ubuntu and now it is unusable.

The Problem

Whenever I try to wake up the PC from sleep/suspend mode, the system initially appears to respond, but then the screen freezes & doesn't respond to anything I do. At this point, the only way out appears to be to force-shutdown the machine by holding the power button for 5 seconds, then starting it up again.

This occurs regardless of whether the sleep was triggered manually or automatically after enough inactivity, and regardless of whether the wakeup attempt was done by moving the mouse, hitting the keyboard, or pressing the power button. Sometimes it visibly brings up the login screen again, but sometimes (I think if I'm already logged in), it shows a screen that's entirely black except for the mouse cursor. In any case, neither moving the mouse nor typing on the keyboard produces any visible response at all.

System

I'm running Ubuntu Studio 24.10, but if I remember correctly, the problem was also manifesting when I was still on 24.04.x.

My hardware is as follows:

Motherboard: ASUS Z790 GAMING WIFI7
CPU: Intel Core i9-14900K (x86_64)
GPU: AMD Radeon RX 7900XT
Storage: 8 TB SSD
RAM: 96 GB NVMe DDR5

Solutions I Have Already Tried (to no avail)

• When frozen, switching to a different TTY using Ctrl+Alt+F2–F6: It simply doesn't do anything at all.
  • (Incidentally, when I'm not frozen, Ctrl+Alt+F2 in particular, rather than taking me to a new shell session, displays an entirely-black screen with just a mouse cursor that's very similar to the one I sometimes see during the wakeup freezes, except that I can actually move the mouse around, as well as return to the main graphical session using Ctrl+Alt+F1.)
• Limiting the CPU's maximum C-state in GRUB config: I've tried creating a new file in /etc/default/grub.d/ and adding the line GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT intel_idle.max_cstate=1", then running sudo update-grub and rebooting. I've also tried changing the variable name to processor.max_cstate and the value to 4. No permutations of the aforementioned steps appear to make a difference in the end.
• Increasing swap space: The size of /swap.img was already 8 GB, but I increased it to 10 GB in accordance with advice I read stating that the swap file should be the square root of total system RAM. In retrospect, I'm not certain what difference I even expected this to make in the first place.
• Disabling systemd session freezing: Following other advice online, I experimented with adding the following environment variables for configuration of systemd 256+:
  • Created /etc/systemd/system/systemd-suspend.service.d/freeze_fix.conf:

    [Service]
    Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
    

  • Created /etc/systemd/system/systemd-sleep.service.d/ as a symlink to /etc/systemd/system/systemd-suspend.service.d.
  • Created /etc/systemd/system/systemd-homed.service.d/freeze_fix.conf:

    [Service]
    Environment="SYSTEMD_HOME_LOCK_FREEZE_SESSION=false"
    

(The people I've seen post similar issues on the internet in the past have often been told to check their system logs in /var/log/syslog and/or the output of journalctl (or more specifically, journalctl -b -1). The initial versions of this post had the results of those logs from the suspension process pasted below, but I have since removed them because they only contained messages from the suspension process itself rather than the process of waking up again, which is when the actual issue occurs.)

I have Ubuntu 24.04.1 LTS on a Dell XPS 9320 (not dual-boot). Since I upgraded from 22.04 last month, my internal speakers have not worked. In Settings, Sound Output lists "No Output Devices". I do get sound via USB devices (speakers or earbuds). I've tried many suggestions from many related questions (see below), but none have worked. Now I'm reaching out for help (please and thank you). From my reading of the related questions, here's relevant information for my case.

Based on remarks of V1del, a forum moderator at archlinux. I tried the following 4 commands to diagnose:

$ sudo fuser -v /dev/snd/*

                 USER        PID ACCESS COMMAND
/dev/snd/controlC0:  jim        2555 F.... wireplumber
/dev/snd/seq:        jim        2549 F.... pipewire


$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

$ pactl list cards
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

$ sudo pactl list sinks
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

I guess the two "Connection failure" are a problem, but I don't know what they mean.

Based on my research the past few weeks, the following also seem relevant to diagnosing my problem.

$ lspci | grep -i audio
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01)

and

$ inxi -A
Audio:
  Device-1: Intel Alder Lake Imaging Signal Processor driver: N/A
  Device-2: Intel Alder Lake PCH-P High Definition Audio
    driver: sof-audio-pci-intel-tgl
  API: ALSA v: k6.8.0-48-generic status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active

I don't see a sound problem in that output (the Device-1 line makes sense, as my camera doesn't work (Cheese, Skype); but that is not my focus here). I do see a problem from the next command I tried

$ sudo dmesg | grep -i snd

[    4.672746] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    4.672907] snd_hda_intel 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
[    6.313507] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    6.313627] snd_hda_intel 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
[    7.384054]  SDW0-Capture: ASoC: error at snd_soc_link_prepare on SDW0-Capture: -61
[    7.393206]  SDW0-Capture: ASoC: error at snd_soc_link_prepare on SDW0-Capture: -61
 … repeated 20+ times 
[   77.199398]  SDW0-Capture: ASoC: error at snd_soc_link_prepare on SDW0-Capture: -61
[   77.207304]  SDW0-Capture: ASoC: error at snd_soc_link_prepare on SDW0-Capture: -61

When I google "SDW0-Capture: ASoC: error at snd_soc_link_prepare on SDW0-Capture: -61" I see many posts (often Archlinux) that talk about downgrading the kernel. I don't know what that is, and it sounds bad (like a duct-tape fix, a patch not a fix). But maybe useful to note my kernel:

$ uname -r
6.8.0-48-generic

Please note that pipewire seems fine:

$ systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-11-10 08:43:39 EST; 2h 36min ago
TriggeredBy: ● pipewire.socket
   Main PID: 2549 (pipewire)
      Tasks: 3 (limit: 18626)
     Memory: 3.4M (peak: 3.8M)
        CPU: 77ms
     CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire.service
             └─2549 /usr/bin/pipewire

Nov 10 08:43:39 xps-13plus-xps-9320 systemd[2530]: Started pipewire.service - PipeWire Multimedia Service.

I think wireplumber's only problem is with the camera:

$ systemctl --user status wireplumber
● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-11-10 08:43:39 EST; 2h 37min ago
   Main PID: 2555 (wireplumber)
      Tasks: 6 (limit: 18626)
     Memory: 4.3M (peak: 5.5M)
        CPU: 348ms
     CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/wireplumber.service
             └─2555 /usr/bin/wireplumber

Nov 10 08:43:39 xps-13plus-xps-9320 systemd[2530]: Started wireplumber.service - Multimedia Service Session Manager.
Nov 10 08:43:40 xps-13plus-xps-9320 wireplumber[2555]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Nov 10 08:43:40 xps-13plus-xps-9320 wireplumber[2555]: PipeWire's libcamera SPA missing or broken. libcamera not supported.

Maybe this info about pipewire-pulse is relevant?

$ systemctl --user status pipewire-pulse
○ pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
     Active: inactive (dead)
TriggeredBy: ○ pipewire-pulse.socket 

I got changes, but no fix, with the following:

$ systemctl --user restart wireplumber pipewire-pulse pipewire

In Settings (Sound Output), this turned "No Output Devices" to "Dummy Output" in the Output of Sound. It also changed the cards and sinks listings, as follows:

$ pactl list cards
Card #46
    Name: alsa_card.pci-0000_00_1f.3-platform-sof_sdw
    Driver: alsa
    Owner Module: n/a
    Properties:
        api.acp.auto-port = "false"
        api.acp.auto-profile = "false"
        api.alsa.card = "0"
        api.alsa.card.longname = "Intel Soundwire SOF"
        api.alsa.card.name = "sof-soundwire"
        api.alsa.path = "hw:0"
        api.alsa.use-acp = "true"
        api.dbus.ReserveDevice1 = "Audio0"
        device.api = "alsa"
        device.bus = "pci"
        device.bus_path = "pci-0000:00:1f.3-platform-sof_sdw"
        device.description = "Alder Lake PCH-P High Definition Audio Controller"
        device.enum.api = "udev"
        device.icon_name = "audio-card-analog-pci"
        device.name = "alsa_card.pci-0000_00_1f.3-platform-sof_sdw"
        device.nick = "sof-soundwire"
        device.plugged.usec = "5766876"
        device.product.id = "0x51c8"
        device.product.name = "Alder Lake PCH-P High Definition Audio Controller"
        device.subsystem = "sound"
        sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sof_sdw/sound/card0"
        device.vendor.id = "0x8086"
        device.vendor.name = "Intel Corporation"
        media.class = "Audio/Device"
        factory.id = "14"
        client.id = "34"
        object.id = "46"
        object.serial = "46"
        object.path = "alsa:pcm:0"
        alsa.card = "0"
        alsa.card_name = "sof-soundwire"
        alsa.long_card_name = "Intel Soundwire SOF"
        alsa.driver_name = "snd_soc_sof_sdw"
        alsa.mixer_name = "Intel Alderlake-P HDMI"
        alsa.components = "HDA:8086281c,80860101,00100000 cfg-spk:4 cfg-amp:2 spk:rt1316 mic:rt715-sdca"
        alsa.id = "sofsoundwire"
        device.string = "0"
    Profiles:
        off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
        pro-audio: Pro Audio (sinks: 4, sources: 1, priority: 1, available: yes)
    Active Profile: off

and

$ pactl list sinks
Sink #39
    State: SUSPENDED
    Name: auto_null
    Description: Dummy Output
    Driver: PipeWire
    Sample Specification: float32le 2ch 48000Hz
    Channel Map: front-left,front-right
    Owner Module: 4294967295
    Mute: no
    Volume: front-left: 49808 /  76% / -7.15 dB,   front-right: 49808 /  76% / -7.15 dB
            balance 0.00
    Base Volume: 65536 / 100% / 0.00 dB
    Monitor Source: auto_null.monitor
    Latency: 0 usec, configured 0 usec
    Flags: DECIBEL_VOLUME LATENCY 
    Properties:
        node.name = "auto_null"
        device.description = "Dummy Output"
        audio.rate = "48000"
        audio.channels = "2"
        audio.position = "FL,FR"
        media.class = "Audio/Sink"
        factory.name = "support.null-audio-sink"
        node.virtual = "true"
        monitor.channel-volumes = "true"
        factory.id = "18"
        clock.quantum-limit = "8192"
        client.id = "36"
        node.driver = "true"
        factory.mode = "merge"
        audio.adapt.follower = ""
        library.name = "audioconvert/libspa-audioconvert"
        object.id = "39"
        object.serial = "39"
    Formats:
        pcm

Thank you in advance to any kind soul who can help me restore my speaker sound. And I'd be happy to share more info if it would help ...

PS If it helps, here is a sampling I other questions I've looked at for help:

Fixing No Sound (Dummy Output) Issue in Ubuntu 24.04 From the top answer there, I used sudo gedit to create /etc/modprobe.d/audiofix.conf and put in the lines

options snd-hda-intel dmic_detect=0
options snd-hda-intel model=laptop-amic enable=yes

After rebooting, no change.

No sound output devices listed after upgrade from 21.10 to 22.04 looks relevant, but it is about pulseaudio and 24.04 uses pipewire.

Fixing No Sound (Dummy Output) Issue in Ubuntu 24.04 suggests to downgrade the kernel, but that sounds bad to me. And my sound problem is "No Output Devices", not "Dummy Output"

I see several unanswered questions that may be about the same as mine, with no speaker-sound in 24.04; e.g. lenovo M90a, Ubuntu 24.04, missing sound on speakers, earphones ok

In my case aplay lists a sound card, so my problem differs from many other dealing with no sound in 24.04, such as No sound after upgrade from Ubuntu 22.04 to Ubuntu 24.04.

No sound in internal Speakers in Ubuntu 24.04 sounded promising, but the fix there was to disable fast-boot in Windows (I don't have Windows).

=== Here's more info,

 tail "/etc/modprobe.d/alsa-base.conf"
    options snd-usb-usx2y index=-2
    # Ubuntu #62691, enable MPU for snd-cmipci
    options snd-cmipci mpu_port=0x330 fm_port=0x388
    # Keep snd-pcsp from being loaded as first soundcard
    options snd-pcsp index=-2
    # Keep snd-usb-audio from beeing loaded as first soundcard
    options snd-usb-audio index=-2
    # options snd-hda-intel model=auto -- tried & failed for audio 
     fix 27Oct2024
    # blacklist snd_soc_avs
    options snd-hda-intel model=dell-headset-multi

As suggested by heynnema, here are two more pieces of info

    $ uname -r

6.8.0-48-generic

and

$ ls -al /boot
total 188920
drwxr-xr-x  4 root root     4096 Nov  1 07:53 .
drwxr-xr-x 24 root root     4096 Oct 27 09:24 ..
-rw-r--r--  1 root root   287493 Sep 27 13:21 config-6.8.0-47-generic
-rw-r--r--  1 root root   287459 Sep 27 08:22 config-6.8.0-48-generic
drwx------  4 root root     4096 Dec 31  1969 efi
drwxr-xr-x  5 root root     4096 Nov  1 07:53 grub
lrwxrwxrwx  1 root root       27 Nov  1 07:52 initrd.img -> initrd.img-6.8.0-48-generic
-rw-r--r--  1 root root 72110854 Oct 27 09:24 initrd.img-6.8.0-47-generic
-rw-r--r--  1 root root 72097106 Nov  1 07:52 initrd.img-6.8.0-48-generic
lrwxrwxrwx  1 root root       27 Nov  1 07:52 initrd.img.old -> initrd.img-6.8.0-47-generic
-rw-r--r--  1 root root   142796 Apr  8  2024 memtest86+ia32.bin
-rw-r--r--  1 root root   143872 Apr  8  2024 memtest86+ia32.efi
-rw-r--r--  1 root root   147744 Apr  8  2024 memtest86+x64.bin
-rw-r--r--  1 root root   148992 Apr  8  2024 memtest86+x64.efi
-rw-------  1 root root  9061992 Sep 27 13:21 System.map-6.8.0-47-generic
-rw-------  1 root root  9063891 Sep 27 08:22 System.map-6.8.0-48-generic
lrwxrwxrwx  1 root root       24 Nov  1 07:52 vmlinuz -> vmlinuz-6.8.0-48-generic
-rw-------  1 root root 14956936 Sep 27 14:47 vmlinuz-6.8.0-47-generic
-rw-------  1 root root 14952840 Sep 27 08:26 vmlinuz-6.8.0-48-generic
lrwxrwxrwx  1 root root       24 Nov  1 07:52 vmlinuz.old -> vmlinuz-6.8.0-47-generic

I updated my bios to the most recent (from 2.10 to 2.16.1) but that seems not to have affected anything.

video card seems to be Intel

$  lspci | grep VGA.
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c)

As suggested by @hynnema, I used Mainline to change kernels to 6.5.11 and added "options snd-hda-intel model=dell-headset-multi" to alsabase.conf and rebooted (kernel 6.5.11) but still No Output Devices in Sound Settings. But now pipewire has a problem:

pipewire.service - PipeWire Multimedia Service

     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-11-21 16:12:25 EST; 9min ago
TriggeredBy: ● pipewire.socket
   Main PID: 2932 (pipewire)
      Tasks: 3 (limit: 18609)
     Memory: 3.4M (peak: 3.8M)
        CPU: 88ms
     CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire.service
             └─2932 /usr/bin/pipewire

Nov 21 16:12:25 xps-13plus-xps-9320 systemd[2911]: Started pipewire.service - PipeWire Multimedia Service.
Nov 21 16:12:25 xps-13plus-xps-9320 pipewire[2932]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files

I plan use Dell's system restore, but first I need to back up my data and my legacy software programs.

I have started using Ubuntu22.04 on VirtualBox today. I'd like to see the RAM usage, but it shows, "This metric requires guest additions to work." However, I did add the guest by following this post. Does anyone know how to show it properly?

I've been having issues with my machine not detecting my second GPU (both RTX 3090s). This is not a new machine and is an issue that popped up a few weeks ago, which I resolved by rolling back to an older kernel (unknown version). But after a recent update, I lost that kernel and am stuck with this issue.

Here's what I've tried so far:

• Swapping GPUs in their PCI slots to rule out a hardware issue
• Update to latest mobo BIOS
• Fresh 22.04 install for each driver install below
• Every NVIDIA CUDA install (>= 11.7) from the NVIDIA downloads page (deb local, deb network and run file)
• Every Ubuntu nvidia-driver* as far back as I can go to maintain a minimum CUDA version of 11.7
• Rolling back to an abritrarily old kernel version (5.15) using mainline
• Rolling forward to kernel 6.4
• Booting with a HDMI monitor attached to GPU 2

*Note that all older Ubuntu nvidia-drivers-5XX are transitional packages to either 525 or 535 (apt search nvidia-driver). The last driver I had both GPUs working was 515.

The single GPU that is listed (also my display GPU) does run CUDA workloads, but seems to make my system unstable/laggy when the job (PyTorch) starts for a few mins.

❯ uname -r
5.19.0-46-generic

❯ lspci | grep VGA
09:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1)
43:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1)

❯ nvidia-smi
Sat Jul  1 12:11:41 2023       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.125.06   Driver Version: 525.125.06   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:43:00.0  On |                  N/A |
|  0%   41C    P8    24W / 350W |    562MiB / 24576MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1879      G   /usr/lib/xorg/Xorg                140MiB |
|    0   N/A  N/A      2338    C+G   ...ome-remote-desktop-daemon      258MiB |
|    0   N/A  N/A      2375      G   /usr/bin/gnome-shell               87MiB |
|    0   N/A  N/A      3338      G   ...566776601308618822,262144       73MiB |
+-----------------------------------------------------------------------------+

dmesg Link to GitHub Gist

The weird thing is very occasionally, after a fresh CUDA install (not isolated to a single driver version) and a restart, the 2nd GPU does show up in nvidia-smi. But after a reboot is disappears again. Uninstalling and reinstalling CUDA can replicate this but it appears to be random (and not what I want to do each time I reboot)

Any ideas how I can get my machine working properly again?

Link to nvidia-bug-report

So I recently installed Ubuntu WSL1 in my company PC and ran this command to update my installation, It seems ping is successful but "apt-get" fails to connect and download. I need some help here to trouble shoot this

sudo apt-get update

I'm getting the following error:

Err:2 http://security.ubuntu.com/ubuntu focal-security InRelease
  Could not connect to security.ubuntu.com:80 (2001:67c:1562::18). - connect (111: Connection refused) 
  Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease  Could not connect to archive.ubuntu.com:80 (2620:2d:4000:1::16). - connect (111: Connection refused) Could not connect to archive.ubuntu.com:80 (2620:2d:4000:1::19). - connect (111: Connection refused) Could not connect to archive.ubuntu.com:80 (2001:67c:1562::15). - connect (111: Connection refused) Could not connect to archive.ubuntu.com:80 (2001:67c:1562::18). - connect (111: Connection refused)


W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease  Could not connect to security.ubuntu.com:80 (2001:67c:1562::18). - connect (111: Connection refused) 

W: Some index files failed to download. They have been ignored, or old ones used instead.

I tried to ping archive.ubuntu.com and it is showing me it's successful. but the apt-get update does not work ?

 ping archive.ubuntu.com

--- archive.ubuntu.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12010ms
rtt min/avg/max/mdev = 220.761/221.066/221.704/0.251 ms

I am running 18.04LTS on a dell precision 7540. I have been using my Thunderbolt dock with it quite happily for about 9 months.

But this week, I updated some drivers (nvidia) and upgraded the kernel. Once I rebooted, my dock is no longer being recognized. Neither power, nor mouse, nor keyboard, nor displays attached to the dock are recognized.

Symptoms:

• modprobe thunderbolt returns no output.
• boltctl list returns no output.
• boltd is running.

Settings->Devices->Thunderbolt shows: "No devices attached"

However, lspci -tv yields:

+-1c.0-[04-6e]----00.0-[05-6e]--+-00.0-[06]----00.0  Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
|                               +-01.0-[07-39]--
|                               +-02.0-[3a]----00.0  Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018]
|                               \-04.0-[3b-6e]--

I have double checked my BIOS settings a couple times, but since things worked before my latest updates, I don't think this is related.

I have tried rolling back my kernel version to 5.4.0-48. (I had upgraded to 5.4.0-62).

I checked dmesg and I noticed one usb error: usb 1-2: 2:1: cannot get freq at ep 0x1, but not sure if it's related.

TLDR: All of the existing questions on this topic seem to be about enabling 4k display with the Spice virtual display driver. This question is about making it sticky.

Question:

I have no problem using my 4K display with Windows 10 guests after increasing the VRAM.

However, both Virt-Manager's builtin viewer and Virt-viewer have a nasty habit of resizing the guest resolution to 1080p every time I open them. This happens even when running virt-viewer with the full-screen commandline option.

How can I open a fullscreen viewer on my VM that retains the correct VM display resolution... or at least correctly resizes it to 2160p?

I'm new to this site and this OS "Ubuntu"

so I have problems with wifi and bluetooth..

I just check the logs and finally think the problem is related to firmware..

dmesg | grep iwl
[    2.819550] iwlwifi 0000:00:14.3: loaded firmware version 34.0.0 op_mode iwlmvm
[    2.833065] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x338
[    7.900012] iwlwifi 0000:00:14.3: Failed to load firmware chunk!
[    7.900015] iwlwifi 0000:00:14.3: iwlwifi transaction failed, dumping registers
[    7.900016] iwlwifi 0000:00:14.3: iwlwifi device config registers:
[    7.900050] iwlwifi 0000:00:14.3: 00000000: 34f08086 00100406 02800030 00800010 17114004 00000060 00000000 00000000
[    7.900051] iwlwifi 0000:00:14.3: 00000020: 00000000 00000000 00000000 00348086 00000000 000000c8 00000000 000001ff
[    7.900052] iwlwifi 0000:00:14.3: iwlwifi device memory mapped registers:
[    7.900086] iwlwifi 0000:00:14.3: 00000000: 00489008 00000040 00000000 00000000 00000000 00000000 00000000 00000000
[    7.900087] iwlwifi 0000:00:14.3: 00000020: 00000011 0c040005 00000332 d55555d5 d55555d5 d55555d5 80008040 001f0040
[    7.900106] iwlwifi 0000:00:14.3: Could not load the [0] uCode section
[    7.900110] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -110
[    7.913089] iwlwifi 0000:00:14.3: Failing on timeout while stopping DMA channel 8 [0x0bad1122]
[    7.925547] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110

dmesg|grep -i firmware
[    0.261195] pci 0000:00:1f.5: BAR 0: trying firmware assignment [mem 0xfe010000-0xfe010fff]
[    0.827494] [Firmware Bug]: Invalid critical threshold (0)
[    1.719365] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x4d5f02)
[    1.997497] iwlwifi 0000:00:14.3: loaded firmware version 34.0.0 op_mode iwlmvm
[    2.313386] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.314629] bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2
[    2.314631] Bluetooth: hci0: Failed to load Intel firmware file (-2)
[    2.316386] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.316393] bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2
[    2.316395] Bluetooth: hci0: Failed to load Intel firmware file (-2)
[    3.349840] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[    7.136131] iwlwifi 0000:00:14.3: Failed to load firmware chunk!

rfkill list all
0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy1: Wireless LAN
    Soft blocked: no
    Hard blocked: no

my laptop model is hp 15-cs3012tx and version of Ubuntu is 16.04 LTS I just searched of my adapter model, it says

Intel® Wireless-AC 9560 802.11a/b/g/n/ac (2x2) Wi-Fi® and Bluetooth® 5 Combo

so I just downloaded intel ac 9560 firmware to install

1. OVERVIEW

The file iwlwifi-5150-2.ucode provided in this package must be 
present on your system in order for the Intel Wireless WiFi Link
AGN driver for Linux (iwlagn) to operate on your system.

The "-2" in the filename reflects an interface/architecture version number.
It will change only when changes in new uCode releases make the new uCode
incompatible with earlier drivers.

On adapter initialization, and at varying times during the uptime of 
the adapter, the microcode is loaded into the memory on the network 
adapter.  The microcode provides the low level MAC features including 
radio control and high precision timing events (backoff, transmit, 
etc.) while also providing varying levels of packet filtering which can 
be used to keep the host from having to handle packets that are not of 
interest given the current operating mode of the device.

2. INSTALLATION

The iwlagn driver will look for the file iwlwifi-5150-2.ucode using the 
kernel's firmware_loader infrastructure.  In order to function 
correctly, you need to have this support enabled in your kernel.  When 
you configure the kernel, you can find this option in the following 
location:

        Device Drivers ->
                Generic Driver Options ->
                        Hotplug firmware loading support


You can determine if your kernel currently has firmware loader support 
by looking for the CONFIG_FW_LOADER definition on your kernel's 
.config.

In addition to having the firmware_loader support in your kernel, you 
must also have a working hotplug and udev infrastructure configured.  
The steps for installing and configuring hotplug and udev are very 
distribution specific. 

Once you have the firmware loader in place (or if you aren't sure and 
you just want to try things to see if it works), you need to install 
the microcode file into the appropriate location.

Where that appropriate location is depends (again) on your system 
distribution.  You can typically find this location by looking in the 
hotplug configuration file for your distro:

    % grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent

This should give you output like:

    FIRMWARE_DIR=/lib/firmware

If it lists more than one directory, you only need to put the 
microcode in one of them.  In the above example, installation is 
simply:

    % cp iwlwifi-5150-2.ucode /lib/firmware

You can now load the driver (see the INSTALL and README.iwlwifi provided with
the iwlwifi package for information on building and using that driver.)

this is the attached document with the firmware file

I typed the command and it showed like this

grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent
grep: /etc/hotplug/firmware.agent: No such file or directory

but in the document it was supposed to be like this

% grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent

This should give you output like:

    FIRMWARE_DIR=/lib/firmware

I can't install this firmware with the way above.. and I think this 9650 device is related to wifi and bluetooth..

could someone pls give me a hand to install this firmware..?

thank you for your hand in advance

edit) I also included logs with command dmesg|grep -i firmware

One day I moved the Documents directory inside the Downloads directory. I could still access it as usual, but, eventually, I ended receiving this message (also see the screenshot):

Oops! Something went wrong.
Unable to find the requested file. Please check the spelling and try again.

$ cat ~/.config/user-dirs.dirs
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/Templates"
XDG_PUBLICSHARE_DIR="$HOME/Public"
XDG_DOCUMENTS_DIR="$HOME/"
XDG_MUSIC_DIR="$HOME/"
XDG_PICTURES_DIR="$HOME/Pictures"
XDG_VIDEOS_DIR="$HOME/"

I ran

gedit ~/.config/user-dirs.dirs

Rerun of

$ cat ~/.config/user-dirs.dirs
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/Templates"
XDG_PUBLICSHARE_DIR="$HOME/Public"
XDG_DOCUMENTS_DIR="$HOME/Documents"
XDG_MUSIC_DIR="$HOME/Music"
XDG_PICTURES_DIR="$HOME/Pictures"
XDG_VIDEOS_DIR="$HOME/Videos"

Update 21st October 2019
As mentioned I moved my Music and Video files to the Home directory. So I did the re-run of gedit ~/.config/user-dirs.dirs. Type in Documents, Music and Videos.

Everything appeared as usual. I tried restarting it and shutting down my laptop. The Music and Videos directory remains there and can be opened. Did it again:

gedit ~/.config/user-dirs.dirs

XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/Templates"
XDG_PUBLICSHARE_DIR="$HOME/Public"
XDG_DOCUMENTS_DIR="$HOME/Documents"
XDG_MUSIC_DIR="$HOME/Music"
XDG_PICTURES_DIR="$HOME/Pictures"
XDG_VIDEOS_DIR="$HOME/Videos"

Yet the Documents directory has not appeared. So the Document Directory is deleted. I will now try to use Photorec to use recover my Home Directory and files.

mv $HOME/Downloads/Documents $HOME/Documents
mv: cannot stat '/home/user/Downloads/Documents': No such file or directory

Older information:

I clicked properties on Documents everything on basic came up unknown and permissions: The permissions of "" could not be found.

Older information:
cat '/etc/xdg/user-dirs.defaults'
# Default settings for user directories
#
# The values are relative pathnames from the home directory and
# will be translated on a per-path-element basis into the users locale
DESKTOP=Desktop
DOWNLOAD=Downloads
TEMPLATES=Templates
PUBLICSHARE=Public
    DOCUMENTS=Documents
    MUSIC=Music
    PICTURES=Pictures
    VIDEOS=Videos
    # Another alternative is:
    #MUSIC=Documents/Music
    #PICTURES=Documents/Pictures
    #VIDEOS=Documents/Videos

Problem

I'm trying to investigate this weird error where systemd-resolved is constantly crashing on 2 out of 4 machines. The one thing different with these two problematic machines (that I can think of), is that they are mounting a samba/cifs filesystem exported from machine #3 (on which systemd-resolved is running fine).

How do I get to the bottom of this?

OS

# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

# uname -a
Linux prod-delayed-jobs 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

# systemd --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid

Relevant journalctl output

Notice the /dev/null is not a device. line in the logs. This is occurring multiple times - during, before, and after systemd-resolved crashes.

Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPREQUEST of [REDACTED-IP-ADDRESS] on eth0 to 172.31.1.1 port 67 (xid=0x730cc4e4)
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: DHCPACK of [REDACTED-IP-ADDRESS] from 172.31.1.1
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopping Network Name Resolution...
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
Feb 12 14:23:21 prod-delayed-jobs systemd[11796]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
Feb 12 14:23:21 prod-delayed-jobs dhclient[794]: bound to [REDACTED-IP-ADDRESS] -- renewal in 32497 seconds.
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
Feb 12 14:23:21 prod-delayed-jobs systemd[11813]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Stopped Network Name Resolution.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: /dev/null is not a device.
Feb 12 14:23:21 prod-delayed-jobs systemd[1]: Starting Network Name Resolution...
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed to set up mount namespacing: Invalid argument
Feb 12 14:23:22 prod-delayed-jobs systemd[11831]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: Failed to start Network Name Resolution.
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Feb 12 14:23:22 prod-delayed-jobs systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.

/etc/fstab contents - in case this is relevant

UUID=2f54e8e6-ff9c-497a-88ea-ce159f6cd283 /               ext4    discard,errors=remount-ro 0       1
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
//[REDACTED]/uploaded_files /home/myuser/shared cifs rw,username=myuser,password=[REDACTED],uid=myuser,gid=myuser 0 0

Few systemd configuration files are pointing to /dev/null

This is the case on all the 4 machines, however only 2 out of these 4 are having trouble with systemd-resolved. Strangely, hostname.service is pointing to /dev/null - wonder why?

lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogd.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootlogs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 bootmisc.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkfs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot-bootclean.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 checkroot.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks-early.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 cryptdisks.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 fuse.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 halt.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hostname.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 hwclock.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 killprocs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Apr 12  2018 lvm2.service -> /dev/null
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm.service -> /dev/null
lrwxrwxrwx 1 root root    9 Jul  2  2018 mdadm-waitidle.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 motd.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall-bootclean.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountall.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountdevsubfs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountkernfs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs-bootclean.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 mountnfs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Jan 16  2018 nfs-common.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rc.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rcS.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 reboot.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 rmnologin.service -> /dev/null
lrwxrwxrwx 1 root root    9 Dec  6 11:10 screen-cleanup.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 sendsigs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 single.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 stop-bootlogd-single.service -> /dev/null
lrwxrwxrwx 1 root root    9 Dec  6 11:07 sudo.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountfs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountnfs.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 umountroot.service -> /dev/null
lrwxrwxrwx 1 root root    9 Nov 15 21:45 x11-common.service -> /dev/null

/lib/systemd/system

[Unit]
Description=Network Name Resolution
Documentation=man:systemd-resolved.service(8)
Documentation=https://www.freedesktop.org/wiki/Software/systemd/resolved
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
DefaultDependencies=no
After=systemd-sysusers.service systemd-networkd.service
Before=network.target nss-lookup.target shutdown.target
Conflicts=shutdown.target
Wants=nss-lookup.target

[Service]
Type=notify
Restart=always
RestartSec=0
ExecStart=!!/lib/systemd/systemd-resolved
WatchdogSec=3min
User=systemd-resolve
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
PrivateTmp=yes
PrivateDevices=yes
ProtectSystem=strict
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelTunables=yes
ProtectKernelModules=yes
MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap

I've installed GoG Heroes III Complete using Wine on Ubuntu 18.04 on an Acer Aspire TimelineX 5830TG laptop. When running the game, I see that some keyboard shortcuts won't work. For example, n to select New Game, r to select Random Mode, e to end turn, t to select city. However, Esc works to exit game, and Enter works for confirming selection.

I've stumbled upon this thread here: keyboard not working with games in wine which I hoped will help me, but after following it closely I had no luck.

I've tried changing Windows version in winecfg from XP to 7 to 8 to 10, but nothing happened.

I've tried switching Ubuntu's native input method from default to ibus and back, also with no results.

Any hope I fix this?

I installed Ubuntu 16.04 LTS on a new HP ZBook 15 from a bootable USB.

I have problems booting up and shutting down normally, e.g. the machine just freezes after login.

As a temporary solution I boot in recovery mode:

On start up I navigate to the GRUB menu >> Ubuntu Advanced Options >> choose Ubuntu (recovery mode) >> run the fsck option >> continue booting

That works but I have to do this every time. Can someone point me to a permanent fix?

The sleep mode also does not work, so I need to restart every day currently.

So I finally dual booted Windows 10 with Ubuntu 16.04. I have been running Xubuntu on my secondary laptop around 5-6 months and now decided to install it on my main laptop so far Ubuntu runs great but there's only one issue: I can't see my dedicated GPU [AMD Radeon 8670M] it only shows my Intel Integrated GPU [Intel HD Graphics 4400]. On Additional drivers section there are only Intel Proprietary Drivers.

Here are the Commands I ran :

$ sudo lshw -c video

 *-display               
       description: VGA compatible controller
       product: Haswell-ULT Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:44 memory:c2000000-c23fffff memory:b0000000-bfffffff ioport:6000(size=64)**

and

$ lspci -nn | grep VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09)

and

$ dmesg | egrep "radeon|drm"

[    1.345817] [drm] Initialized drm 1.1.0 20060810
[    1.386931] [drm] Memory usable by graphics device = 2048M
[    1.386937] fb: switching to inteldrmfb from VESA VGA
[    1.387046] [drm] Replacing VGA console driver
[    1.391211] [drm] radeon kernel modesetting enabled.
[    1.395226] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.395229] [drm] Driver supports precise vblank timestamp query.
[    1.398577] radeon 0000:0a:00.0: enabling device (0006 -> 0007)
[    1.424927] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
[    1.425088] [drm] initializing kernel modesetting (HAINAN 0x1002:0x6660 0x103C:0x2164).
[    1.425101] [drm] register mmio base: 0xC2400000
[    1.425102] [drm] register mmio size: 262144
[    1.429954] radeon 0000:0a:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    1.429956] radeon 0000:0a:00.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
[    1.429957] [drm] Detected VRAM RAM=1024M, BAR=256M
[    1.429958] [drm] RAM width 64bits DDR
[    1.430106] [drm] radeon: 1024M of VRAM memory ready
[    1.430107] [drm] radeon: 2048M of GTT memory ready.
[    1.430116] [drm] Loading hainan Microcode
[    1.430197] [drm] Internal thermal controller without fan control
[    1.430254] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[    1.438512] [drm] radeon: dpm initialized
[    1.438518] [drm] GART: num cpu pages 524288, num gpu pages 524288
[    1.439806] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[    1.439810] [drm] PCIE gen 2 link speeds already enabled
[    1.442772] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[    1.442964] radeon 0000:0a:00.0: WB enabled
[    1.442967] radeon 0000:0a:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800355bec00
[    1.442968] radeon 0000:0a:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8800355bec04
[    1.442970] radeon 0000:0a:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8800355bec08
[    1.442971] radeon 0000:0a:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800355bec0c
[    1.442973] radeon 0000:0a:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8800355bec10
[    1.442974] radeon 0000:0a:00.0: VCE init error (-22).
[    1.442976] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.442977] [drm] Driver supports precise vblank timestamp query.
[    1.442979] radeon 0000:0a:00.0: radeon: MSI limited to 32-bit
[    1.443009] radeon 0000:0a:00.0: radeon: using MSI.
[    1.443040] [drm] radeon: irq initialized.
[    1.551879] fbcon: inteldrmfb (fb0) is primary device
[    1.551995] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    1.680395] [drm] ring test on 0 succeeded in 1 usecs
[    1.680403] [drm] ring test on 1 succeeded in 1 usecs
[    1.680419] [drm] ring test on 2 succeeded in 0 usecs
[    1.680428] [drm] ring test on 3 succeeded in 4 usecs
[    1.680436] [drm] ring test on 4 succeeded in 4 usecs
[    1.680715] [drm] ib test on ring 0 succeeded in 0 usecs
[    1.680744] [drm] ib test on ring 1 succeeded in 0 usecs
[    1.680771] [drm] ib test on ring 2 succeeded in 0 usecs
[    1.680792] [drm] ib test on ring 3 succeeded in 0 usecs
[    1.680813] [drm] ib test on ring 4 succeeded in 0 usecs
[    1.681381] [drm] Radeon Display Connectors
[    1.682905] [drm] Initialized radeon 2.43.0 20080528 for 0000:0a:00.0 on minor 1
[   21.205885] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[   21.205890] [drm] PCIE gen 2 link speeds already enabled
[   21.212077] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[   21.212176] radeon 0000:0a:00.0: WB enabled
[   21.212178] radeon 0000:0a:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800355bec00
[   21.212180] radeon 0000:0a:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8800355bec04
[   21.212181] radeon 0000:0a:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8800355bec08
[   21.212183] radeon 0000:0a:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800355bec0c
[   21.212184] radeon 0000:0a:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8800355bec10
[   21.212186] radeon 0000:0a:00.0: VCE init error (-22).
[   21.448861] [drm] ring test on 0 succeeded in 1 usecs
[   21.448866] [drm] ring test on 1 succeeded in 1 usecs
[   21.448872] [drm] ring test on 2 succeeded in 1 usecs
[   21.448880] [drm] ring test on 3 succeeded in 4 usecs
[   21.448887] [drm] ring test on 4 succeeded in 4 usecs
[   21.448951] [drm] ib test on ring 0 succeeded in 0 usecs
[   21.449007] [drm] ib test on ring 1 succeeded in 0 usecs
[   21.449062] [drm] ib test on ring 2 succeeded in 0 usecs
[   21.449076] [drm] ib test on ring 3 succeeded in 0 usecs
[   21.449090] [drm] ib test on ring 4 succeeded in 0 usecs

EDIT: Formatting

after upgrade to ubuntu 16.04 i can't turn on bluetooth on my laptop . try reinstall bluez and other bluetooth application same as blueman and bluetooth but don't solve problem

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2016-05-15 10:14:59 IRDT; 5h 40min ago
     Docs: man:bluetoothd(8)
 Main PID: 1104 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 512)
   CGroup: /system.slice/bluetooth.service
           └─1104 /usr/lib/bluetooth/bluetoothd

May 15 10:15:03 morteza-CX61-2PC bluetoothd[1104]: Not enough free handles to register service
May 15 10:15:03 morteza-CX61-2PC bluetoothd[1104]: Not enough free handles to register service
May 15 10:15:03 morteza-CX61-2PC bluetoothd[1104]: Sap driver initialization failed.
May 15 10:15:03 morteza-CX61-2PC bluetoothd[1104]: sap-server: Operation not permitted (1)
May 15 10:15:04 morteza-CX61-2PC bluetoothd[1104]: Loading LTKs timed out for hci0
May 15 10:15:41 morteza-CX61-2PC bluetoothd[1104]: Failed to set mode: Not Powered (0x0f)
May 15 10:15:41 morteza-CX61-2PC bluetoothd[1104]: Failed to get connections: Not Powered (0x0f)
May 15 10:16:52 morteza-CX61-2PC bluetoothd[1104]: Failed to set mode: Failed (0x03)
May 15 10:17:02 morteza-CX61-2PC bluetoothd[1104]: Failed to set mode: Failed (0x03)
May 15 14:13:45 morteza-CX61-2PC bluetoothd[1104]: Failed to set mode: Failed (0x03)

lsusb

Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 13d3:3394 IMC Networks Bluetooth
Bus 003 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

rfkill list

0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no 

when i go to setting and choose bluetooth show "no bluetooth found" screenshot : http://storage6.static.itmages.com/i/16/0515/h_1463312053_7827113_7a4e2df260.png

dmesg | egrep -i 'blue|firm'

[    0.147244] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[    0.816454] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    1.761166] usb 3-7: Product: RT Bluetooth Radio
[    1.776032] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x550f00)
[   15.773162] Using firmware rtlwifi/rtl8723fw_B.bin
[   18.901441] Bluetooth: Core ver 2.21
[   18.901451] Bluetooth: HCI device and connection manager initialized
[   18.901454] Bluetooth: HCI socket layer initialized
[   18.901455] Bluetooth: L2CAP socket layer initialized
[   18.901459] Bluetooth: SCO socket layer initialized
[   19.093565] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
[   19.093568] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723a_fw.bin
[   40.996583] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   40.996585] Bluetooth: BNEP filters: protocol multicast
[   40.996588] Bluetooth: BNEP socket layer initialized
[   41.247665] Bluetooth: RFCOMM TTY layer initialized
[   41.247670] Bluetooth: RFCOMM socket layer initialized
[   41.247673] Bluetooth: RFCOMM ver 1.11
[   42.998956] Bluetooth: hci0 command 0x0c56 tx timeout
[  102.826854] Bluetooth: hci0 urb ffff8800c6322d80 failed to resubmit (113)
[  112.790161] Bluetooth: hci0 urb ffff8800a66bf240 failed to resubmit (113)

when i try search device in blueman software receive this error

Resource Not Ready
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/blueman/bluez/errors.py", line 146, in warp
    return func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/blueman/bluez/Adapter.py", line 135, in start_discovery
    self.get_interface().StartDiscovery()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NotReady: Resource Not Ready

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/blueman-manager", line 210, in inquiry
    self.List.DiscoverDevices()
  File "/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py", line 401, in DiscoverDevices
    self.Adapter.start_discovery()
  File "/usr/lib/python3/dist-packages/blueman/bluez/errors.py", line 148, in warp
    raise parse_dbus_error(exception)
blueman.bluez.errors.DBusNotReadyError: Resource Not Ready

when i trye to restart bluetooth service from terminal popup error message with this content

Connection to BlueZ failed
Bluez daemon is not running, blueman-manager cannot continue.
This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started.

I'm using Ubuntu 12.04 and I've installed Viber and I'm struggling for days with this problem. My Viber icon is located at the top left corner, few milimeters to the right from the dash icon. I have tried to whitelist it on desktop enviroment variables, it wroked with Skype, but not with Viber. Please help.