running stock ubuntu 24.04

in Settings -> Ubuntu Desktop -> Auto-hide the Dock <-- enabled

all works fine until somehow

Launcher bar

stays showing from time to time

... Its on screen left ... is there a fix to this bad behavior

Typically I have a couple of terminal windows butted against screen far left ... on the off chance launcher gets stuck showing --> work around is to just move any app away from far left screen then I can put them back

And no I have not mucked about this is stock ubuntu 24.04 for the most part regarding anything window manager related

This is from a fresh install of Pop!OS and Kubuntu with the latest versions for both. This issue happens with one GPU (OLAND [radeonsi, , ACO, DRM 2.50, 6.16.3-76061603-generic]), but doesn't with a different older one (Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]).

While using my PC, the screen will freeze and then go to a white static screen. On Pop, I was still able to move my mouse, while Kubuntu completely froze. Here is an example of the issue on Pop, with the white square being the mouse. After a minute or two, it will reboot itself.

Certain programs seem to trigger it. I've noticed so far Zen Browser and Discord do, and Lutris may have. It's something where if I were to play a game in one monitor and watch a video on the other, Firefox would be fine for hours, but Zen Browser could cause this to happen immediately. For another example if I have Discord open, it seems to happen more randomly.

I could not get this to happen with an installation media (I also verified that it was detecting and using my external GPU). For Kubuntu, I tested it in the same set up with the exact same bootable USB I used to install it, and it didn't happen. I did notice while I was testing with the installation media that this popped up with an error.

I've asked around and it was suggested to me with this error that this could be a bug on Ubuntu's end, but I wanted to ask in case there is a way to fix it (since it seems to be a driver issue?).

Here are the specs:

• Processor: AMD® Phenom(tm) ii x6 1035t processor × 6
• GPU: OLAND (radeonsi, , ACO, DRM 2.50, 6.16.3-76061603-generic)
• 24 GB RAM
• 1 TB SSD, and also tested with installing and booting into a 1 TB HDD

I'm brand new to Linux (like one year experience using Pop on a laptop), and I'm sorry if anything here seems a little ignorant. I've reached the ends of what I could Google and so far no one's been able to help me with a solution.

Am using Ubuntu 24.04.3 LTS with all updates. Earlier the machine (I believe) went into suspension when I closed the lid, and everything was fine. Now it does not, and also if I choose "suspend" from the power menu, then the screen is off when I turn it on again so that I need to reboot anyway.

The command gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action reports suspend.

Editing /etc/systemd/logind.conf does not seem to have any effect (and it seems to say suspend anyway, iirc).

The dconf record /org/gnome/settings-daemon/plugins/power/ does not contain the key lid-close-ac-action (as suggested here).

What is the current way to configure close lid behaviour?

AMD Ryzen 5 5600H processor. Motherboard: DMI:American Megatrends International, LLC. Windows 11 required additional drivers to recognize Bluetooth and WiFi. These drivers I received from PC seller and they are named: 20250902_R6.0_WHQL_V3.4.0.1335_BT_V1.1043.0.555 20250902_R6.0_WHQL_WLAN_V3.4.0.1335_BT_V1.1043.0.555 I can not find those drivers for Linux.

Am trying to install the latest Ubuntu on a laptop with a less than perfect hard disk. The disk contains a root partition that is about 25% of total capacity. It was formatted using the "Disk" app, seemingly without problems. The installation proceeds until the end and then reports unknown error. Booting fails with a bios msg that there is no OS. Presumably the problem is that GRUB/MSR could not be written.

Are there any practical things I can try to get this to work? Can I tell the installer to put GRUB in the root partition and ignore the boot record? Or something?

Update: this is a cannibalised inherited laptop, not that old. It seems it should be possible to get this to work.

I'm trying to configure the network in a Latte Panda Mu, that is a regular N100 intel processor with a regular wifi radio.

I can install Ubuntu 24 server, I faced several issues.

1. Upon install ethernet didn't work

2. I configured netplan with screen and keyboard ip a cat /dev to look at interfaces /etc/netplan/50-cloud-init.yaml to use dhcp on the ethernet that was mapped enp2s0

3. I connected with ethernet and putty and it was working

4. I added a wifi module and the network stopped working. I looked via screen/keyboard and baffingly to me, ubuntu remapped the ports so netplan stopped working enp3s0for the ethernet wlp2s0

5. So I added the wifi configuration (below I saved it and just removed the wifi ssid and password)

6. Now ethernet, wifi and screen, all do not work. I can tell it is doing something by the activity LED on the NVME so the operating system is running.

Lattepanda Bricking Netplan

sudo cat /etc/netplan/50-cloud-init.yaml
network:
  version: 2
  ethernets:
    enp3s0:
      dhcp4: true
  wifis:
    wlp2s0:
      dhcp4: true
      access-points:
        "myssid":
          password: "mypassword"

Below image of the screen before I rebooted to apply netplan and wasn't able to access anymore.

I plan to wire up the service UART to use PUTTY via serial interface, I just need to solder it but I'm baffled why it doesn't work.

As sanity check I used this file on a raspberry pi with ubuntu server using eth0 and wlan0 as interface name as shown by ip a and it works fine

Raspberry Pi working netplan

sudo cat /etc/netplan/50-cloud-init.yaml
network:
  version: 2
  ethernets:
    eth0:
      dhcp4: true
  wifis:
    wlan0:
      dhcp4: true
      access-points:
        "myssid":
          password: "mypassword"

What am I doing wrong here? I do I configure netplan on ubuntu 24 server for intel processors?

I am having Wi-Fi issues on my laptop after installing Ubuntu. My wireless card is Realtek 8852BE Wireless LAN WiFi 6 PCI-E NIC, and it does not work properly on Ubuntu. The connection is unstable, sometimes disconnects, and the speed is very low compared to Windows.

Here are my device specifications:

  Device name: Alisher
  Processor: AMD Ryzen 5 7430U with Radeon Graphics (2.30 GHz)
  RAM: 16 GB
  System type: 64-bit operating system, x64-based processor
  Wireless adapter: Realtek 8852BE WiFi 6 PCI-E NIC

I think Ubuntu does not have a stable driver for this Wi-Fi chipset. Could you please help me install the correct driver or provide a fix for this issue?

I created a video file with OBS. I put it on a website to share with a class I am teaching. When I try to see the video on my Firefox browser (I am running Ubuntu 22.04 and Firefox 132.0.2 ).

When I click on the link for the video, I get the message "No video with supported format and MIME type found". I have looked through various sites, including askUbuntu and have done what folks in the past have done, apparently successfully (I have installed ffmpeg, although I already had it installed). But, nothing seems to work.

Can someone help?

I’m 88 years old. I brought a mini PC with Ubuntu installed. I figured it would keep my old brain active. Everything was fine until I tried to upgrade to ubuntu-24.04.3-desktop-amd64 from a bootable USB. When I start the mini it is asking for a password. I used the password I originally used, but it says the password is invalid, so at this point the mini is useless.

Specs:

  BOSGAME Ubuntu Linux Mini PC
  Intel N95
  16GB RAM
  512GB SSD
  Mini server computers
  Micro PC 4K Triple Display
  WiFi 5
  BT 4.2
  USB 3.2
  2.5G LAN for home/office

Intel I219-LM on Lenovo M90n-1 IoT detected in PCI but e1000e probe fails on Ubuntu 24.04.3 LTS Server

I’m trying to use the second Ethernet port (Intel I219-LM) on a Lenovo ThinkCentre M90n-1 IoT running Ubuntu 24.04.3 LTS Server, but the NIC never initializes. The Realtek NIC works normally.

Ubuntu does detect the I219-LM in lspci, and the correct Intel driver (e1000e) loads, but the driver probe fails with error -2, and the interface never appears in ip a.

System

• Model: Lenovo ThinkCentre M90n-1 IoT
• BIOS: Latest available from Lenovo support website
• OS: Ubuntu 24.04.3 LTS Server (fresh, clean install)
• NIC Port 1: Realtek RTL8111/8168 → works
• NIC Port 2: Intel I219-LM → detected by PCI but does not work

Diagnostic information

PCI device is detected:

lspci | grep -i i219
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-LM (rev 30)

Driver module loads, but probe fails:

lsmod | grep e1000
e1000e                356352  0

sudo dmesg | grep -i e1000e
[    1.113767] e1000e: Intel(R) PRO/1000 Network Driver
[    1.114432] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.116625] e1000e 0000:00:1f.6: Interrupt Throttling Rate set to dynamic conservative mode
[    1.757815] e1000e: probe of 0000:00:1f.6 failed with error -2

Detailed PCI dump:

sudo lspci -vvv -s 00:1f.6

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-LM (rev 30)
  DeviceName: Onboard - Ethernet
  Subsystem: Lenovo Ethernet Connection (6) I219-LM
  Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
  Interrupt: pin A routed to IRQ 16
  IOMMU group: 11
  Region 0: Memory at a1300000 (32-bit, non-prefetchable) [size=128K]
  Capabilities: [c8] Power Management version 3
    Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
    Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
  Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address: 0000000000000000  Data: 0000
  Kernel modules: e1000e

Only the Realtek NIC appears in ip a:

ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    ....
2: enp2s0:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether ... brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.35/24 metric 100 brd 192.168.2.255 scope global dynamic enp2s0
       valid_lft 3565sec preferred_lft 3565sec
    inet6 .../64 scope link 
       valid_lft forever preferred_lft forever

Output shows:

• lo
• enp2s0 (Realtek RTL8111/8168 with a valid IPv4 address)

The Intel NIC never appears as an interface (normally it would be something like enp0s...).

What I have tried

• Fresh reinstall of Ubuntu 24.04.3 LTS Server
• Updated to latest Lenovo BIOS
• Verified both NICs are enabled in BIOS
• Swapped cables, ports, and switches
• Booted with the Intel port connected and disconnected
• Confirmed the e1000e kernel module is loaded

Behavior is always the same:

• The Realtek NIC works perfectly.
• The Intel I219-LM is visible in PCI, but e1000e fails to probe it and no network interface is created.

Additional test: Windows 10 works on the same hardware

To rule out hardware failure, I booted the exact same ThinkCentre M90n-1 IoT from a Windows 10 Pro portable USB with the Ethernet cable plugged only into the Intel I219-LM port (Realtek port unused):

• Windows detected the Intel NIC.
• It obtained an IP address via DHCP.
• The machine was reachable on the LAN and had working network connectivity.

So:

• The Intel I219-LM hardware and port are known-good.
• BIOS configuration appears sufficient for the NIC to operate.
• The failure seems specific to the Ubuntu 24.04.3 + in-kernel e1000e + Lenovo OEM NVM/firmware combination, not a physical or cabling issue.

Intel documentation

Intel’s official driver README for this NIC says:

• I219-LM is supported
• Ubuntu 24.04 LTS is supported

Intel also states:

“If you purchased an OEM-branded system, contact your OEM for an SW/FW version compatible with your exact NVM. Using mismatched SW/FW versions may affect performance or stability.”

This suggests Lenovo may use a Lenovo-specific NVM/firmware for the I219-LM on this model.

Question for AskUbuntu

• Is this a known issue with the I219-LM on Ubuntu 24.04.3 LTS Server (kernel 6.8) on the ThinkCentre M90n-1 IoT?
• Does the in-kernel e1000e driver need a different version or special module options for this OEM firmware/NVM?
• Could this be caused by an Intel NVM or ME/UEFI firmware mismatch on this Lenovo platform?
• How can I further debug what probe of 0000:00:1f.6 failed with error -2 actually means here?

Any help or pointers on getting the Intel I219-LM to initialize properly on this system would be greatly appreciated.

I'm facing an issue on a Lubuntu VM. I did some changes, firefox was broken so I removed the snap version for the apt version. But I can't be sure this is the cause. Just the last thing I did.

Afterwards I was not able to open my home dir in file explorer. I just decided to reboot in the hope that would solve the issue. But now I can't even login (using rdp with xrdp).

it fails to login, again seems to be a problem with home dir.

I can connect via ssh.

question is I'm not seeing any error. How can I figure out the issue? ls -l in cli will also block so there is some issue with the file structure. How can I trobleshoot this?

EDIT:

Lubuntu 22.04 LTS

It worked at some point, but now it doesn't work. When I try to run it from the CLI I get this error:

cannot set memlock limit to 524288:524288: Operation not permitted

When I run it from the menu, nothing happens at all. I tried to reinstall the Firefox snap package, but the same issue persists.

What is causing this and how can I fix it?

EDIT:

from some other link I found out that if I run

snap run --strace firefox

Then firefox starts and runs. but not really a solution merely an indication that something is very off.

When attempting to reinstall blueman and other apt-get functions I get the following message:

sudo apt-get install --reinstall blueman
N: Ignoring file 'google-chro' in directory '/etc/apt/sources.list.d/' as it has no filename extension
E: Conflicting values set for option Signed-By regarding source http://dl.google.com/linux/chrome/deb/ stable: /usr/share/keyrings/google-chrome.gpg != /etc/apt/trusted.gpg.d/google.gpg

Ubuntu 25.10 can not run apt-get refers to google cloud. I am not certain how to perform the recommendations for chrome.

Per the request here is the output of ls -l /etc/apt/sources.list.d

$ ls -l /etc/apt/sources.list.d
total 128
-rw-r--r-- 1 root root  1782 Oct 30 08:13 audio-recorder-ubuntu-ppa-noble.sources
-rw-r--r-- 1 root root  1782 Oct 25 09:24 audio-recorder-ubuntu-ppa-noble.sources.save
-rw-r--r-- 1 root root  1785 Oct 30 08:13 audio-recorder-ubuntu-ppa-oracular.sources
-rw-r--r-- 1 root root  1785 Oct 25 09:24 audio-recorder-ubuntu-ppa-oracular.sources.save
-rw-r--r-- 1 root root  1797 Oct 30 08:13 gezakovacs-ubuntu-ppa-oracular.sources
-rw-r--r-- 1 root root  1797 Oct 25 09:24 gezakovacs-ubuntu-ppa-oracular.sources.save
-rw-r--r-- 1 root root   116 Apr 13  2024 google-chro
-rw-r--r-- 1 root root   116 Nov 13 07:25 google-chrome.list
-rw-rw-r-- 1 root root   192 Oct 25 09:24 google-chrome.list.save
-rw-r--r-- 1 root root 17758 Oct 30 08:13 google-chrome.sources
-rw-r--r-- 1 root root 17758 Oct 25 09:24 google-chrome.sources.save
-rw-r--r-- 1 root root   180 Nov 13 07:07 google.list
-rw-r--r-- 1 root root  1817 Oct 30 08:13 openshot_developers-ubuntu-ppa-noble.sources
-rw-r--r-- 1 root root  1817 Oct 25 09:24 openshot_developers-ubuntu-ppa-noble.sources.save
-rw-r--r-- 1 root root   250 Mar  7  2025 signal-xenial.list.save
-rw-r--r-- 1 root root   216 Oct 30 08:13 ubuntu-esm-apps.sources
-rw-r--r-- 1 root root   216 Oct 25 09:24 ubuntu-esm-apps.sources.save
-rw-r--r-- 1 root root   220 Oct 30 08:13 ubuntu-esm-infra.sources
-rw-r--r-- 1 root root   220 Oct 25 09:24 ubuntu-esm-infra.sources.save
-rw-r--r-- 1 root root   394 Oct 30 08:13 ubuntu.sources
-rw-r--r-- 1 root root  2580 Apr 10  2024 ubuntu.sources.curtin.orig
-rw-r--r-- 1 root root   383 Oct 25 09:24 ubuntu.sources.save
-rw-r--r-- 1 root root  1813 Oct 30 08:13 ubuntuhandbook1-ubuntu-audio-recorder-oracular.sources
-rw-r--r-- 1 root root  1813 Oct 25 09:24 ubuntuhandbook1-ubuntu-audio-recorder-oracular.sources.save

I recently installed chrome. How can I correct this error?

First, Opera-developer stopped working, and a few days/update later Opera-beta. Both on Ubuntu 24.04 LTS and 25.10. On 24.04 I got it working by starting an X11 session.

Both fail on Wayland with this error message:

/usr/share/libdrm/amdgpu.ids: No such file or directory
amdgpu: unknown (family_id, chip_external_rev): (150, 64)
/usr/share/libdrm/amdgpu.ids: No such file or directory
amdgpu: unknown (family_id, chip_external_rev): (150, 64)
[xx:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[xx:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[xx:ERROR:ui/aura/env.cc:257] The platform failed to initialize.  Exiting.

Is there any testing being done at Opera at all?

I thought snaps were going to fix problems, but it seems to me they're causing just more and more (rather silly) issues.

Does anyone know a fix?

after a common app update this is the error while i open the app tradingview. i did all update and upgrade and reinstalled Gnome. i've never modify nothing related with wayland.

:~$ tradingview
Initializing LoggerService
dbus-send: /snap/tradingview/68/lib/x86_64-linux-gnu/libdbus-1.so.3: version `LIBDBUS_PRIVATE_1.12.16' not found (required by dbus-send)
[3949:1102/122304.278458:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[3949:1102/122304.278546:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[3949:1102/122304.278561:ERROR:ui/aura/env.cc:257] The platform failed to initialize.  Exiting.
[1102/122304.284290:ERROR:third_party/crashpad/crashpad/util/linux/scoped_ptrace_attach.cc:27] ptrace: Operation not permitted (1)
Segmentation fault (core dumped)

I have a new laptop HP Elitebook 8 G1i 14 AI whose internal speakers worked without problem under Windows (i.e. there is no hardware problem). However, under Ubuntu they don't work.

In Ubuntu 24.04 LTS, the internal speakers are detected as "sof-hda-dsp" but no sound comes out. I can get sound through the headphone jack.

I have also tried Ubuntu 25.10 (kernel 6.17.0), then the speakers appear in the system settings as "Lunar Lake M HD Audio Controller" but they still don't produce any sound (the headphone jack still works).

In case this information might help: the BIOS says that the Audio Controller is Realtek ALC3315.

I could only find old questions about similar problems in older HP notebooks which apparently have been solved in newer Ubuntu versions, but maybe I'm the first person to have a problem with this model?

Any help would be greatly appreciated.

Ubuntu 24.04 comes only with Python 3 but I need to work also with programs that only use Python 2. I know that the best way is via venv, yet I have to have an installation of Python 2 which I'm currently lacking of. What is the best way to install Python 2 without messing up with my Python 3 system-wide installation? Since Python 2 is not part of the apt anymore, I would prefer to install it from the most credible source rather than some random github repo. Cheers.

I recently updated to 20.04 and I love the new full range of full color emoji but they disappear when I print, export to PDF or even if I download a pdf from email.

I thought it was a libre office issue at first until I noticed them disappear from the downloaded PDF. In the screencapture is a Libre office spreadsheet print preview screen full of emoji, and on the right is what I get if I export to PDF or print.

I have verified that "objects/images" is checked in LibreOffice, tried from a fresh file, and tried it in LibreOffice's safe mode. Please help.

After a day of restarting my computer i finally given up. I had Ubuntu 18.10 installed and worked perfectly and then i got the upgrade prompt and upgraded to 19.04. The upgrade crashed and after that the system was still booting except 80% of the time. Most of the boots resulted in a purple screen and that is all. I tried everything on the web and nothing seams to work. It is very very random. Couldn't find a way to see where it hangs. The frozen boots fo not appear in the journal. If i try to boot the recovery both messages appear so loads the kernel and the other thing and then it hangs. I reinstalled Ubuntu 18.10 (with updates) and had the same problem. I did the upgrade (which this time worked) to 19.04 and same problem. Now I installed Ubuntu 18.04.2 without any updates and i got it working 4/4 boots. I did the updates 400ish mb of updates and then started doing the same thing with the purple screen. I reinstalled the 18.04.2 and didn't do the updates.

I have no other options than to hope.. I have a Zenbook UX433FA and dualboot with Windows. I guess it is one of the packages that gets updated on 18.04.2 but i don't know which one.

Thank you.

edit: before the 18.10 reinstall i did a fresh reinstall of 19.04

To upgrade from 18.04 to 18.10 I executed the following commands: "sudo apt-get dist-upgrade" and "sudo do-release-upgrade"

Upgrade proceeded normally until the system reached the reboot phase. Following reboot the normal maroon dot progress screen was displayed for a few seconds. This was replaced with a black screen with the message "Main-Linux clean 574402/3567072 files, 7146011/14350592 blocks". And there it stopped with no further changes evident.

Ctrl-F1 took me to the normal console log in. I could log in and found everything was running normally. Disks were all present, active and with plenty of free space. Ctrl-F7 took me back to the black screen with the single message at the top of the screen.

I tried booting with the previous kernel but got the same result.

I have a spare 18.04 Linux on another partition. After booting into it a cursory look at my main system showed nothing untoward.

I have successfully upgraded Ubuntu for more than ten years and this is the first problem I have experienced.

Where do I go from here? How do I fix the problem?

Edit:

After booting into my spare Ubuntu 18.04 on another partition I used the Disks program to do file system checks on the main partitions. This reported that the file systems were clean. I then tried to reboot into 18.10 but again got the same problem, described above.

I have checked the SMART status of the SSD and it reports all is OK after self-test. The processor is Intel Pentium(R) CPU G4400 @ 3.30GHz × 2 and the GPU is Intel HD Graphics 510 (Skylake GT1)

Update:

After logging in at the console(Alt-Ctrl-F1) I can start the GUI by entering startx. For some reason the GUI subsystem fails to start automatically, as it did before.

I have Ubuntu 16.04.3 LTS with EVE-NG running on top of it. I have run into a known issue with Predictable-Network-Interface-Names and changed interface names to old style, but something is still wrong.

During the boot I see "failed to start raise network interfaces" message. Then, that's what systemctl shows:

* networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           `-50-insserv.conf-$network.conf
   Active: failed (Result: exit-code) since Tue 2017-11-14 07:06:04 EST; 20min ago
     Docs: man:interfaces(5)
  Process: 677 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 570 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (
 Main PID: 677 (code=exited, status=1/FAILURE)

Nov 14 07:06:03 eve-ng ifup[677]: Waiting for pnet2 to get ready (MAXWAIT is 32 seconds).
Nov 14 07:06:04 eve-ng ifup[677]: SIOCADDRT: File exists
Nov 14 07:06:04 eve-ng ifup[677]: Failed to bring up pnet2.
Nov 14 07:06:04 eve-ng ifup[677]: Waiting for pnet3 to get ready (MAXWAIT is 32 seconds).
Nov 14 07:06:04 eve-ng ifup[677]: interface eth4 does not exist!
Nov 14 07:06:04 eve-ng ifup[677]: Waiting for pnet4 to get ready (MAXWAIT is 32 seconds).
Nov 14 07:06:04 eve-ng systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Nov 14 07:06:04 eve-ng systemd[1]: Failed to start Raise network interfaces.
Nov 14 07:06:04 eve-ng systemd[1]: networking.service: Unit entered failed state.
Nov 14 07:06:04 eve-ng systemd[1]: networking.service: Failed with result 'exit-code'

However, my interfaces are successfully renamed: dmesg | grep eth confirms no renamig occurs during boot.

All of interfaces are up and running, I'm able to SSH to this host.

There are four things I have already done (and none worked):

You disable the assignment of fixed names, so that the unpredictable kernel names are used again. For this, simply mask udev's rule file for the default policy: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules // done

You pass the net.ifnames=0 on the kernel command line // done

You create your own manual naming scheme, for example by naming your interfaces "internet0", "dmz0" or "lan0". For that create your own .link files in /etc/systemd/network/, that choose an explicit name or a better naming scheme for one, some, or all of your interfaces. // done:

cat /etc/systemd/network/10-eth.link
[Match]
MACAddress=00:0c:29:20:c2:66
[Link]
Name=eth0
[Match]
MACAddress=00:0c:29:20:c2:70
[Link]
Name=eth1
[Match]
MACAddress=00:0c:29:20:c2:7a
[Link]
Name=eth2
[Match]
MACAddress=00:0c:29:20:c2:84
Name=eth3

I did create a new file 10-rename-network.rules in /etc/udev/rules.d/ and added the following content to it: SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0" //done:

cat /etc/udev/rules.d/10-rename-network.rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0c:29:20:c2:66", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0c:29:20:c2:70", NAME="eth1"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0c:29:20:c2:7a", NAME="eth2"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0c:29:20:c2:84", NAME="eth3"

Is there anything I'm missing?

I downloaded Ubuntu 16.04 and installed it on my system using UNetbootin. When everything is finished and I restarted, and selected UNetbootin. Don't know why but Windows Boot Manager complains that some necessary file are not present or corrupt. Please send me the details you require and the possible reason.

Windows Boot Manager  

Windows failed to start. A recent hardware or software change might be the cause.  
To fix the problem:

  1. Insert your Windows installation disc and restart your computer. 
  2. Choose your language settings, and then click "Next."
  3. Click "repair your computer."

If you don't have this disc, contact your system administrator or computer
manufacturer for assistance. 

  File:  

  Status: 0xc700000b  

  Info: 

Note:

1. I want to dual boot Windows 10 and Ubuntu.
2. I am absolute beginner to Linux.

I apologize in advance as my Linux knowledge is very limited.I've installed Ubuntu 17.04 Server in a test environment and attempted to install Samba. During the installation the winbind daemon will not start. I've ran apt update && upgrade before installing Samba however it seems that it didn't help out. I've tested Ubuntu version 16.04 LTS and it works without any errors. I'm a bit lost as to why Winbind will not work on 17.04, Google search results didn't help. If anyone needs more info I'll gladly provide it but you'll probably need to show me the command to do it.

Thank you

Jun 14 10:53:18 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jun 14 10:53:18 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 14 10:53:18 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.
Jun 14 10:53:30 UbtNicholas sudo[23772]: nilaberge : TTY=pts/0 ; PWD=/home/nilaberge ; USER=root ; COMMAND=/bin/su
Jun 14 10:53:30 UbtNicholas sudo[23772]: pam_unix(sudo:session): session opened for user root by nilaberge(uid=0)
Jun 14 10:53:30 UbtNicholas su[23773]: Successful su for root by root
Jun 14 10:53:30 UbtNicholas su[23773]: + /dev/pts/0 root:root
Jun 14 10:53:30 UbtNicholas su[23773]: pam_unix(su:session): session opened for user root by nilaberge(uid=0)
Jun 14 10:53:30 UbtNicholas su[23773]: pam_systemd(su:session): Cannot create session: Already running in a session
Jun 14 10:53:55 UbtNicholas systemd[1]: Starting Samba Winbind Daemon...
-- Subject: Unit winbind.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has begun starting up.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Supervising process 23803 which is not our child. We'll most likely not notice
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 10:53:55 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.

There's almost a similar question but the question assumes that it worked on 17.04

Link to the similar question: Winbind Broken on Reboot In Ubuntu 17.04

UPDATE 1: After following andreas advice in running testparm, it found some lines that were old so I've removed them and restarted the winbind service. Still does an error but the systemCTL has found something that might pin point a bit better where the issue is.

Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.432130,  0] ../source3/winbindd/winbindd_cache.c:3244(initialize_winbindd_cache)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.435598,  0] ../source3/winbindd/winbindd_util.c:892(init_domain_list)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   Could not fetch our SID - did we join?
Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.436118,  0] ../source3/winbindd/winbindd.c:1401(winbindd_register_handlers)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   unable to initialize domain list
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 10:14:29 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.

Before this happened... I located uninstall.sh file and when I opened it.. it said some characters are undefined something of that sort and asked 'do you want to save it anyway' and I accidentally clicked yes after which it showed this

How am I suppose to resolve and uninstall netbeans 8.1 or in that case reinstall it on Ubuntu

Where should I place a grub theme file? I read grub manual and didn't find anything about exact folder to place it in.

I am trying to install grub2 from a live CD of lubuntu 16.04, I am following this tutorial, after I mounted the /dev/sda1 in the mnt folder using this commands

sudo mount /dev/sda1 /mnt
sudo mount /dev/sda1 /mnt/boot
sudo mount --bind /dev /mnt/dev

Then changing the root directory :

    sudo chroot /mnt

But when try installing grub using sudo grub-install /dev/sda I get this error :

sudo: unable to resolve host ubuntu
grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist.   Please specify --target or --directory.

I tried turning off the uefi mode from bios but I think that my bios version doesn't even support it because it is from 2005

I am using an ASUS N53J that is currently using MBR boot. I have enabled UEFI booting in the bios can can seem to boot USB drives that have been configured with gpt tables. Though I have not figured out how to make use of a dedicated EFI boot partition on the USB drive as yet.

Separately I have connected a second hdd to the laptop via the external SATA connection, created a gpt partition table, esp boot partition, and the filesystem and swap partitions.

When I run grub-mkconfig on the internal hdd, it finds the new linux image on the external hdd. I can boot to that external image and confirm that the esp boot partition gets mounted at /boot/efi, so it appears that I should be able to configure grub2. However, if I run grub-mkconfig when executing from the external drive, its own image does not get found, only the linux and windows images on the internal drive.

I also cannot get efibootmgr to run. The tutorials I have read either are not clear on both the how and the why so I can troubleshoot myself or use commands that I cannot find in the packages I think they are using. Does anyone have a good pointer on how to configure the disk before I install it as the primary boot disk?

Thanks.

Update 2015-12-30 I have progressed to making a USB drive that will at least boot into grub rescue. I do not know why grub won't run from this drive but it at least allows me to manually boot to my target OS. Since I have now booted via a UEFI boot efibootmgr is available.

I performed a new grub-install targeting the esp partition mounted at /boot/efi. This completed without errors. However, when I select the target system for booting the firmware loader stops at a blank screen. This occurs whether the disk is connected via ESATA or has been moved to be the primary disk in the machine.

the output of efibootmgr -v is:

BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0005,0002,0003,0004,0000,0001
Boot0000  Hard Drive    BBS(HD,,0x0)
Boot0001  CD/DVD Drive  BBS(CDROM,,0x0)P1: Slimtype BD  E  DS4E1S    .
Boot0002* ubuntu 15.10  HD(1,GPT,8b6800c2-0b24-4f00-aa66-b1378052604e,0x800,0xfa000)/File(\bootx64.efi)
Boot0003* grub  HD(2,GPT,b07e72fd-9168-4924-a17c-b75e55ed685c,0x800,0xfa000)/File(\Shellx64.efi)
Boot0004* UEFI: SanDisk Cruzer Micro 1.26   PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(2,0)/HD(2,GPT,b07e72fd-9168-4924-a17c-b75e55ed685c,0x800,0xfa000)
Boot0005* ubuntu15.10   HD(1,GPT,8b6800c2-0b24-4f00-aa66-b1378052604e,0x800,0xfa000)/File(\EFI\ubuntu15.10\grubx64.efi)

The desired target is Boot0005. Boot0002 is an experiment copying grubx64.efi to /boot/efi/bootx64.efi. Both Boot0002 and Boot0005 behave similarly.

Boot0003 (grub) is the USB drive and the only means to boot, though it only starts in grub rescue.

Any ideas where I should explore or what additional information may assist diagnosis?

More progress:

grub rescue> set  
prefix=(hd0,2)/boot/grub  ... This is the fat32-formatted esp boot partition  

grub rescue>ls (hd0,2)/  
unknown filesystem      ... or similar words to that effect

grub rescue>set prefix=(hd0,1)/boot/grub  ... ext4-formatted partition
grub rescue> insmod fat
grub rescue>ls (hd0,2)/
                    .... the directory is now read

setting the root to the target boot system and the prefix to the /boot/grub directory of that target system I can insmod linux search config file and normal. If normal does not start the boot option page the following will:

grub rescue>configfile /boot/grub/grub.cfg

I can eventually get the target to boot from the menu.

My synopsis is that grubx64.efi on the USB drive is not configured with the necessary modules for the boot method being used.

While efi-booted into my target filesystem I created a new USB drive, also with a gpt partition table, this time with esp boot as partition 1. I only mention that to assist with reading the bios boot table presented later.

mounting USB partition 2 to an appropriate node:

mkdir -p /boot/efi

mount (USB partition 1) to (USB partition 2)/boot/efi

grub-install --target=x86_64-efi --efi-directory=(USB partition 2)/boot/efi --removable

generates EFI/BOOT/BOOTx64.EFI. The UEFI: Sandisk entry in the bios boot table is the means to boot via this loader

grub-install --target=x86_64-efi --efi-directory=(USB partition2)/boot/efi --bootloader-id=USBboot

generates EFI/USBboot/grubx64.efi. The USBboot entry is also written int the bios boot table

cmp -v BOOT/BOOTx64.EFI USBboot/grubx64.efi yields no differences
either boot option now boots directly to the target filesystem without displaying any grub boot menu. Since the USB drive does not have a /boot/grub directory or a grub.cfg, grubx64.exe must be configured to search for this directory on the target rather than USB.

$ efibootmgr -v
BootOrder: 0007,0004,0005,0002,0003,0008,0000,0001
Boot0000  Hard Drive    BBS(HD,,0x0)
Boot0001  CD/DVD Drive  BBS(CDROM,,0x0)P1: Slimtype BD  E  DS4E1S    .
Boot0002* ubuntu 15.10  HD(1,GPT,8b6800c2-0b24-4f00-aa66-b1378052604e,0x800,0xfa000)/File(\bootx64.efi)
Boot0003* grub  HD(2,GPT,b07e72fd-9168-4924-a17c-b75e55ed685c,0x800,0xfa000)/File(\Shellx64.efi)
Boot0004* ubuntu_15_10  HD(1,GPT,8b6800c2-0b24-4f00-aa66-b1378052604e,0x800,0xfa000)/File(\EFI\ubuntu_15_10\grubx64.efi)
Boot0005* ubuntu15.10   HD(1,GPT,8b6800c2-0b24-4f00-aa66-b1378052604e,0x800,0xfa000)/File(\EFI\ubuntu15.10\grubx64.efi)
Boot0007* USBboot   HD(1,GPT,f887bf87-18a9-40e1-9bca-6c4bfd1cbb4a,0x800,0xc8000)/File(\EFI\USBboot\grubx64.efi)
Boot0008* UEFI: SanDisk PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(4,0)/HD(1,GPT,f887bf87-18a9-40e1-9bca-6c4bfd1cbb4a,0x800,0xc8000)

I still have not figured out how to even get to grub rescue without booting from the external USB drive. Is seems as though I have two problems:

1. I don't fully understand how to configure grub for its intended use, how to make sure necessary modules are built in and the prefix is properly set.
2. I either do not have the bios on the ASUS N53J properly configured or it is not accepting the hard disk configuration as a valid boot configuration.

Any other ideas? I now this is getting rather long. How can I document this to be more readable?

Status Update

Browsing on the web I have discovered grub-mkimage. I have not started working with this and will report progress once I have done so and can either understand the results or can pose a new question about it.

I'm using Ubuntu 14.10 on a VirtualBox VM. It installed fine, I was even able to install Guest Additions and a few apps before shutting it down for the day. Now when I try to boot the VM all that loads is the UEFI Interactive shell.

How do I get it to boot back into the normal desktop?

I am trying to recover a disk that has corrupted superblock but I cant seem to unmount the disk at all. I used bcache for the three extra drive after a reboot one of the drive stopped working. so I removed the SSD cache drive and still cant seem to recover the drive

pavs@VAS:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0 149.1G  0 disk 
├─sda1        8:1    0 133.4G  0 part /
├─sda2        8:2    0     1K  0 part 
└─sda5        8:5    0  15.7G  0 part [SWAP]
sdb           8:16   0   2.7T  0 disk 
└─sdb1        8:17   0   2.7T  0 part 
  └─bcache0 251:0    0   2.7T  0 disk /var/www/html/directlink/FTP1
sdc           8:32   0   1.8T  0 disk 
└─sdc1        8:33   0   1.8T  0 part 
  └─bcache1 251:1    0   1.8T  0 disk 
sdd           8:48   0   1.8T  0 disk 
└─sdd1        8:49   0   1.8T  0 part 
  └─bcache2 251:2    0   1.8T  0 disk



pavs@VAS:~$ sudo fsck.ext4 -v /dev/sdd1
e2fsck 1.42.9 (4-Feb-2014)
/dev/sdd1 is in use.
e2fsck: Cannot continue, aborting.


pavs@VAS:~$ umount -l /dev/sdd
umount: /dev/sdd is not mounted (according to mtab)
pavs@VAS:~$ umount -l /dev/sdd1
umount: /dev/sdd1 is not mounted (according to mtab)


 1072.806897] EXT4-fs (bcache2): ext4_check_descriptors: Checksum for group 640 failed (57199!=0)
[ 1072.806900] EXT4-fs (bcache2): group descriptors corrupted!

I see the linux-hwe-generic package as part of the kernels you can install in Ubuntu.

What is hardware enablement (HWE)?