Our company has its own GitLab instance on our development network. I've created an Ubuntu VM, added all of our networks certs to /usr/local/share/ca-certificates, run update-ca-certificates, installed gitlab-runner, set it up as a systemd service, and registered with GitLab as a shell executor.

All of that succeeds with no problem. GitLab shows the new runner and gitlab-runner verify succeeds.

However, when I actually issue a job, gitlab-runner complains:

WARNING: Certificate decoding error    Issuer=OurCompany Root Authority IssuerCertURL=[http://url/to/root_certification_authority.pem] Serial=... Subject=OurCompany Intermediate Authority context=certificate-chain-build error=invalid certificate: ber2der: BER tag length is more than available data method=fetchIssuerCertificate

I decided to navigate to our GitLab instance in the browser and inspect the certificate. At the bottom of the "OurCompany Intermediate Authority" tab, I see

Authority Info (AIA)

Location http://url/to/root_certification_authority.pem
Method CA Issuers

However, http://url/to/root_certification_authority.pem doesn't exist.

I've brought the issue up with our service desk and I'll see what they say. However, until then I'm tired of messing with cert chains. Is there any way to tell gitlab-runner to just blindly trust the certificates?

I’m trying to run Ubuntu 25.10 on a 2013 Mac Pro (“trashcan”, MacPro6,1) with the stock dual AMD FirePro D500 GPUs (Tahiti / Southern Islands).

Ubuntu installs and boots only when I use:

quiet splash nomodeset

Without nomodeset, the system freezes during early KMS initialization.

When booting without nomodeset, the kernel logs consistently show:

[drm] amdgpu kernel modesetting enabled.

amdgpu 0000:02:00.0: probe with driver amdgpu failed with error -22

amdgpu 0000:06:00.0: probe with driver amdgpu failed with error -22

This happens regardless of SI switching options, including:

radeon.si_support=0 amdgpu.si_support=1 amdgpu.dc=0

radeon.si_support=1 amdgpu.si_support=0

linux-firmware is fully up to date. No blacklisting of amdgpu/radeon is present. EFI hands off a framebuffer, and the system runs using simpledrm only.

Other observations:

/sys/kernel/debug/dri/* contains only simpledrm nodes.

Both GPUs appear in lspci and iommu grouping without errors.

No IOMMU/DMAR faults.

The amdgpu probe fails immediately with -22 before any ASIC init.

My question:

What does probe‐time error -22 typically indicate for Southern Islands (D500 “Tahiti LE”) hardware, and is there a known requirement or quirk for MacPro6,1 dual GPUs under recent kernels (6.17.x)?

Any guidance on whether I should be forcing radeon instead of amdgpu, or whether the dual-GPU Apple PCI layout requires special quirks, would be very helpful.

I recently installed Ubuntu 24.04.3 LTS on my 2-in-1 convertible laptop but out of the box it didn't supported touchscreen

following are the details

output of hostnamectl

       Icon name: computer-convertible
         Chassis: convertible
Operating System: Ubuntu 24.04.3 LTS                  
          Kernel: Linux 6.14.0-35-generic
    Architecture: x86-64
 Hardware Vendor: HP
  Hardware Model: HP ENVY x360 2-in-1 Laptop 13-bf0xxx

output of lspci

00:00.0 Host bridge: Intel Corporation Alder Lake Host and DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP4 GT2 [Iris Xe Graphics] (rev 0c)
00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 06)
00:05.0 Multimedia controller: Intel Corporation Alder Lake Imaging Signal Processor (rev 06)
00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 06)
00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 06)
00:07.1 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #1 (rev 06)
00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 06)
00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01)
00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 06)
00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 06)
00:10.0 Serial bus controller: Intel Corporation Alder Lake-P Serial IO I2C Controller #2 (rev 01)
00:10.6 Digitizer Pen: Intel Corporation Device 51d0 (rev 01)
00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)
00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
00:19.0 Serial bus controller: Intel Corporation Alder Lake-P Serial IO I2C Controller #0 (rev 01)
00:19.1 Serial bus controller: Intel Corporation Alder Lake-P Serial IO I2C Controller #1 (rev 01)
00:1c.0 PCI bridge: Intel Corporation Device 51bd (rev 01)
00:1e.0 Communication controller: Intel Corporation Alder Lake PCH UART #0 (rev 01)
00:1f.0 ISA bridge: Intel Corporation Alder Lake LPC Controller (rev 01)
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake Smart Sound Technology Audio Controller (rev 01)
00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
01:00.0 Non-Volatile memory controller: Sandisk Corp WD PC SN810 / Black SN850 NVMe SSD (rev 01)
7c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5228 (rev 01)

Output of lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

I run Ubuntu 24.04 (gnome 46) and I would like to connect a microscope digital camera to my laptop. I am also looking to measure part of the images so I need a calibration system. I am aware of micro manager but it requires compiling from source. Any easier options?

Ever since I updated from 22.04 to 24.04 some programs have this double border. If you click the buttons on the outer frame it crashes the desktop. I've tried purging and re-installing Budgie Desktop and that didn't fix it.

Does anyone know what's going on?

I tried to type Punjabi language in Text editor and LibreOffice Writer. I am facing an issue with typing because some of words are not typed like they are typed in Windows OS. Some words are opposite language input types than they are in Windows when I try to type them using the Shift key.

My hp zbook refuses to boot from a bootable ssb, secure booting disabled. UEFI enabled. USB boot option. Boot disk made with rufus for ubuntu. Any ideas?

I'm using Ubuntu 24.04, and after a recent software update, Chrome started using colorized digits, #, and *, and also using an extra-wide space in certain parts of its UI, including:

• address bar:
• menu:

I'm not sure which part of the update caused this problem. I'd slacked off on updating for a few months, and just ran apt update; apt upgrade and rebooted.

I've found that uninstalling the Noto Color Emoji font fixes this issue...

sudo apt remove fonts-noto-color-emoji

...but it results in emoji being monochrome or nonexistent in many places.

Prior to this update I'd had Noto Color Emoji installed for years, and never had this problem in Chrome.

Is this a known issue? How can I have Noto Color Emoji installed, but stop Chrome from using it for ASCII characters?

A partial upgrade ended up removing LibreOffice. I tried to install it and got this:

sudo apt install libreoffice
Solving dependencies... Error!  
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 libreoffice : Depends: libreoffice-base but it is not going to be installed
               Depends: libreoffice-calc but it is not going to be installed
               Depends: libreoffice-core (= 4:25.8.2-0ubuntu0.25.10.1) but it is not going to be installed
               Depends: libreoffice-draw but it is not going to be installed
               Depends: libreoffice-impress but it is not going to be installed
               Depends: libreoffice-math but it is not going to be installed
               Depends: libreoffice-report-builder-bin but it is not going to be installed
               Depends: libreoffice-writer but it is not going to be installed
               Depends: python3-uno but it is not going to be installed
               Recommends: libreoffice-gnome but it is not going to be installed or
                           libreoffice-plasma but it is not going to be installed
               Recommends: libreoffice-nlpsolver but it is not going to be installed
               Recommends: libreoffice-report-builder but it is not going to be installed
               Recommends: libreoffice-script-provider-bsh but it is not going to be installed
               Recommends: libreoffice-script-provider-js but it is not going to be installed
               Recommends: libreoffice-script-provider-python but it is not going to be installed
               Recommends: libreoffice-sdbc-mysql but it is not going to be installed
               Recommends: libreoffice-sdbc-postgresql but it is not going to be installed
               Recommends: libreoffice-wiki-publisher but it is not going to be installed
               Recommends: libreoffice-java-common (>= 4:25.8.2~) but it is not going to be installed
Error: Unable to satisfy dependencies. Reached two conflicting decisions:
   1. libreoffice-core:amd64=4:25.8.2-0ubuntu0.25.10.1 Depends libreoffice-sal-private-abi (= 25.8.2)
      but none of the choices are installable:
      - libuno-sal3t64:amd64=4:25.8.2-0ubuntu0.25.10.1 is not selected for install
   2. libreoffice-core:amd64=4:25.8.2-0ubuntu0.25.10.1 is selected for install because:
      1. libreoffice:amd64=4:25.8.2-0ubuntu0.25.10.1 is selected for install
      2. libreoffice:amd64=4:25.8.2-0ubuntu0.25.10.1 Depends libreoffice-core (= 4:25.8.2-0ubuntu0.25.10.1)

How do I fix this?

I am a beginner in Ubuntu, I decided to stick to me current computer. Windows 11 told me to change it, but I won’t… It works just fine ! So I decided to change and learn from every steps, even the smallest, using Ubuntu now (Ubuntu 24.04.3 LTS).

Here is my problem. I get an AppImage of the app SuperSlicer. https://github.com/supermerill/SuperSlicer/releases/tag/2.5.59.13 Prior to downloading it, I decided to install the AppImageLauncher, as I read a recommendation for it (just to know it). Everything works fine in the app when running. Except... the icon in the task bar when I launch the SuperSlicer app. The pinned icon on the bar is correct.

But the icon of the app after launching is a kind of a generic one AND there is not this little red dot (or dots when the app is running multiple times) just right of the pinned icon (as for Firefox in this example). This should actually be the only mark indicating that the app is running looking at the bar and that is the behavior I am looking for.

Generic icon of the app when launched:

I read a bit about this problem and learn that it could come from the .desktop file. But I do not see any trouble in it. Below is the icons location I found and the .desktop file content.

Icons location:

.desktop content:

But now thanks to your help in comment the result is almost what I am expecting. Indeed I had to change the wmclass in the .desktop file.

The situation is now that. There is still 2 icons, but it is a bit better!

New situation

I updated to 25.10 on Monday after the update was offered to me by my Ubuntu 25.04 installation. The system was running on 25.04 since I updated to that from 24.10, I basically updated to every new version when it was released over the past few years which was working more or less without problems.

When I rebooted the PC after the update this time however I noticed that many of the programs are just not opening anymore. This includes both programs that I installed as well as software that is shipped with Ubuntu.

What I noticed was not working:

• Settings (gnome-control-center)
• LibreOffice
• Google Chrome
• MySQL Workbench
• Jetbrains IDEs
• Rocket.Chat

What I am still able to open:

• Terminal
• Sublime Text
• KeePassXC
• Firefox

I am not really able to figure out what the issue may be based on the affected list of programs.

What I did try out so far as it seemed most reasonable to me was changing the graphics driver. I was running the NVIDIA driver 570 and then switched to 580 using apt install. The software updater does show me the installed driver as well as the other options of version 580, but it won't let me switch (pk client error quark 303).

When I for example attempt to open the settings from terminal (running gnome-control-center) nothing is happening. The process does not finish in the terminal, but there aren't any messages or any windows opening. The process just seems to be stuck.

Does anybody have any ideas what that issue could be?

Illustration of the problem: enter image description here

I've taken that screenshot several minutes after starting all those commands. Only chrome is showing some errors messages at all when not using any more debug flags for output. For chrome the dash also shows a supposed welcome window, but its not visible on any screen or dashboard.

Firefox has not saved credit card numbers for me since I upgraded to the Snap version. When I try to save a credit card number I see messages like this in the syslog:

dbus-daemon[3656]: apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.6" pid=5121 label="snap.firefox.firefox" peer_pid=3655 peer_label="unconfined"
dbus-daemon[3656]: apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.Secret.Service" member="OpenSession" mask="send" name=":1.6" pid=5121 label="snap.firefox.firefox" peer_pid=3655 peer_label="unconfined"

I spent about an hour grepping in the AppArmor config files, Googling, and searching Stack Exchange to no avail. What's the secret method to enable this commonly used feature for the snap?

Firefox 144.0.2 Ubuntu 24.04.3 LTS

PS:I am aware of the .deb version, of which I was previously a user. I am hoping we can get the snap version, which Ubuntu is enthusiastically promoting, to work properly so I don't have to go back

What's wrong

The OS starts in software rendering mode. The only thing I've changed (and found in the logs) is installing the updates for sudo-rs and intel microcode via the Ubuntu Software Updater (which I don't suspect to be an issue, I hope, as I don't use an Intel CPU).

I've been using the kernel-provided mesa drivers.

Boot logs also include "not hardware accelerated" pops up.

What I've tried

• Reverting back to 6.14.0-35 makes the GPU work correctly again.
• I've looked through update logs (apt, dpkg, unattended-upgrades) to verify what changed between the GPU working and not working
• In the past, I've been using amdgpu drivers from the AMD website, but these no longer install due to issues with DKMS compilation under 6.17-0.6. I've tried to install these again, to no avail. I've purged these since.

My assumptions

• I don't suspect my local packages, as things just work under Kernel 6.14, but I'm very happy to provide more info if that still may be the case

Additional info

1. vulkaninfo --summary output

Devices:
========
GPU0:
    apiVersion         = 1.4.318
    driverVersion      = 25.2.3
    vendorID           = 0x10005
    deviceID           = 0x0000
    deviceType         = PHYSICAL_DEVICE_TYPE_CPU
    deviceName         = llvmpipe (LLVM 20.1.8, 256 bits)
    driverID           = DRIVER_ID_MESA_LLVMPIPE
    driverName         = llvmpipe
    driverInfo         = Mesa 25.2.3-1ubuntu1 (LLVM 20.1.8)
    conformanceVersion = 1.3.1.1
    deviceUUID         = 6d657361-3235-2e32-2e33-2d3175627500
    driverUUID         = 6c6c766d-7069-7065-5555-494400000000

2. lshw -c video output

  *-display                 
       description: VGA compatible controller
       product: Navi 48 [Radeon RX 9070/9070 XT/9070 GRE]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:0b:00.0
       logical name: /dev/fb0
       version: c0
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list fb
       configuration: depth=32 latency=0 resolution=1024,768
       resources: iomemory:780-77f iomemory:7c0-7bf memory:7800000000-7bffffffff memory:7c00000000-7c0fffffff ioport:e000(size=256) memory:fcd00000-fcd7ffff memory:fcd80000-fcd9ffff

3. Kern.log after boot

./syslog-2025-11-11T21:48:50.613665+01:00 janitors-closet gnome-shell[2599]: Added device '/dev/dri/card0' (simpledrm) using a
tomic mode setting.
./syslog:2025-11-11T21:48:50.615750+01:00 janitors-closet gnome-shell[2599]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
./syslog-2025-11-11T21:48:50.615811+01:00 janitors-closet gnome-shell[2599]: Created gbm renderer for '/dev/dri/card0'
./syslog-2025-11-11T21:48:50.615853+01:00 janitors-closet gnome-shell[2599]: Integrated GPU /dev/dri/card0 selected as primary

Expected outcome

Anything I can do here to debug this more? I'd like to continue using the newer Kernel.

Huge thanks in advance!

Did a bit of searching around for answers, but nothing seemed to point to this oddity. I have an Ubuntu 24.04 server that currently has one QEMU/KVM running on it. I just installed a 2.5Gbit Network interface into the machine and did some network speed testing. Going directly to the host machine, my speed is 900+ Mbit, which is about what I get going through the gigabit adaptor. If I speed test to the VM running on that same server, my speed is 2300Mbit. I don't have ethernet cable plugged into any other NIC, so it isn't a routing difference. Any thoughts on this? I forgot to mention, the server is using SSD's so I don't believe it is a hard drive speed issue.

Just using a speedtest on the linux machines. It is much like Ookla speed test, but just between local machines. VM is set up with a bridge using the Virtio driver. One thing different is the host is testing over https while the guest is being tested over http. I know there would be a performance hit because of that, but more than 2x? – TheBearAK

Just a follow up. Another part of the oddity. I tried booting from a Debian 12 drive and the network speed is what I expect. Put the Ubuntu drive back in and it goes back to slower speed. Just odd. Maybe a driver issue? But then does VM's use the same driver? – TheBearAK

Question

How can I resolve the issue? I described the approach that uses a 3rd party tool egpu-switcher because previously I had a success with that tool, but I don't mind using it or not using it.

Issue

On the same laptop where eGPU was functioning on Ubuntu 22.04, now disk was wiped out and 24.04 is installed then this issue started happening. Upon booting when login window, screen is blacked out. Sometimes an underscore blinks at the top-left.

Steps to reproduce the issue

I basically follow a blog post on nvidia.com (posted in 2020) with a twist. Summarizing the steps:

1. Connect eGPU to the computer by Thunderbolt cable.
2. Install a toolkit. sudo apt update && sudo apt dist-upgrade && sudo apt install nvidia-cuda-toolkit
3. Disable Wayland by commenting out WaylandEnable=false in /etc/gdm3/custom.conf.
4. Informing the OS of GPU? Add 1 line in /usr/share/X11/xorg.conf.d/10-nvidia.conf

   Option "AllowExternalGpus" "True"
   

5. Set to boot w/runlevel 3 by changing /etc/default/grub. Then sudo update-grub && sudo shutdown --reboot.
6. Log in on the CLI prompt a runlevel 3.
7. Revert /etc/default/grub to the default by removing “3” from GRUB_CMDLINE_LINUX_DEFAULT and
8. Execute "egpu-switcher". sudo /usr/bin/egpu-switcher enable.
9. sudo update-grub && sudo shutdown --reboot.
10. Wait. BIOS then Ubuntu's logo show. After that the issue in question starts.

Iff I skip the line that contains egpu-switcher enable, the issue doesn't happen, but also nvidia-smi command doesn't show the external GPU either.

Environment

• Thinkpad p16s (laptop)
• GPU driver nvidia-driver-575-open
• Ubuntu 24.04
• eGPU: Sonnet eGPU Breakaway 650w
• GPU: NVIDIA GeForce RTX 4060 Ti OC Edition 16GB GDDR6
• Thunderbolt cable, tried both ver 4, ver 5.

$ lspci | grep -i "nvidia"
03:00.0 3D controller: NVIDIA Corporation TU117GLM [T550 Laptop GPU] (rev a1)
22:00.0 VGA compatible controller: NVIDIA Corporation AD106 [GeForce RTX 4060 Ti 16GB] (rev a1)
22:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1)

Part of /var/log/syslog from one of the days the issue occurred on my cloud.

Note:

• Ubuntu 24.04 was installed by overwriting the SSD (i.e. it was NOT upgraded from older Ubuntu distro).
• Before 24.04 was installed on the same computer, Ubuntu 22.04 was running and, eGPU was detected AND functioning i.e. Login screen showed up, applications were able to utilize eGPU, nvidia-smi showed the used percentage of the external GPU.
  • But on 22.04, I had to use hertg/egpu-switcher, i.e. without that being executed the GPU was detected but not functioning. On 22.04 its version was 0.19.0, but on 24.04 its version is 0.20.1 (I just noticed that version difference as I'm writing this. I should try 0.19.0).

$ sudo /usr/bin/egpu-switcher enable  
[info] created egpu bootup service to autorun 'egpu-switcher switch'
[ok] setup successful     

I think this generates the 2 files egpu.service, x11-template.conf.

$ sudo more /usr/share/egpu-switcher/egpu.service
# generated by egpu-switcher
[Unit]
Description=EGPU Service
Before=display-manager.service
After=bolt.service

[Service]
Type=oneshot
ExecStart=/usr/bin/egpu-switcher switch auto

[Install]
WantedBy=graphical.target

$ sudo more /usr/share/egpu-switcher/x11-template.conf 
# autogenerated by egpu-switcher
{{if .Modesetting}}
Section "Module"
    Load           "modesetting"
EndSection
{{end}}

Section "Device"
    Identifier     "{{.Id}}"
    Driver         "{{.Driver}}"
    BusID          "{{.Bus}}"
    Option         "AllowEmptyInitialConfiguration"
    Option         "AllowExternalGpus" "True"
EndSection

The 2 services that are called within egpu.service.

$ locate display-manager.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/display-manager.service.wants
/etc/systemd/system/display-manager.service.wants/gpu-manager.service
/var/lib/systemd/deb-systemd-helper-enabled/display-manager.service.wants
/var/lib/systemd/deb-systemd-helper-enabled/display-manager.service.wants/gpu-manager.service

$ more /etc/systemd/system/display-manager.service
[Unit]
Description=GNOME Display Manager

# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service

# replaces plymouth-quit since it quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service

# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and plymouth-quit.service
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service

# Start after cloud init is done generating the system configuration
# otherwise we might end up getting the wrong locale for example
After=cloud-config.service

# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service

[Service]
ExecStartPre=/usr/share/gdm/generate-config
ExecStart=/usr/sbin/gdm3
KillMode=mixed
Restart=always
RestartSec=1s
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
EnvironmentFile=-/etc/default/locale
ExecReload=/usr/share/gdm/generate-config
ExecReload=/bin/kill -SIGHUP $MAINPID
KeyringMode=shared

$ find /usr/ -iname bolt.service 
/usr/lib/systemd/system/bolt.service

$ more /usr/lib/systemd/system/bolt.service
[Unit]
Description=Thunderbolt system service
After=polkit.service
Documentation=man:boltd(8)

[Service]
Type=dbus
BusName=org.freedesktop.bolt
ExecStart=/usr/libexec/boltd
#Environment="G_MESSAGES_DEBUG=all"
Restart=on-failure
NotifyAccess=main
WatchdogSec=3min

MemoryDenyWriteExecute=yes
PrivateTmp=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectKernelModules=yes
ProtectSystem=full
RestrictAddressFamilies=AF_NETLINK AF_UNIX
RestrictRealtime=yes
ReadWritePaths=/var/lib/boltd
SystemCallFilter=~@mount
CapabilityBoundingSet=CAP_NET_ADMIN

#directory management
RuntimeDirectory=boltd
RuntimeDirectoryPreserve=yes
StateDirectory=boltd

I accidentally unplugged the power supply cord while I was using my desktop computer (Ubuntu 24.04.2 LTS).

After booting my PC, I noticed two uncommon behaviors:

• The Ethernet cable was not being detected. I can assert this because normally the ip address would similar to 192.168.1.XXX under a certain network interface, but when I executed that command, that IP address was not shown. I tried executing ping www.gnu.org, but I got ping: www.gnu.org: Name or service not known.
• After logging-in, the screen resolution was very low. I think this happened because the GPU was not being used.

I did a cold reboot, but those two behaviors persist.

I thought this was a hardware problem related to the motherboard caused by the sudden interruption of power. To discard this possibility, I started Ubuntu 24.04.1 LTS using a bootable USB with the installation image and the Ethernet port was being used (I can assert this because I could search information for the Internet, this PC doesn't have a Wi-Fi card) and the resolution of the GUI was high and smooth which makes me think that the GPU was being used. I disconnected the USB and rebooted my computer but the two problems described above persisted. I find it strange that the Ethernet port is used while using the USB, but it is not used while starting Ubuntu which is installed on my desktop computer.

Please let me know if you need further information or the output of some command to troubleshoot this issue and I will insert it at the bottom of this question.

UPDATE (2025-08-22T15:29:17+00:00)

I created a question on Ubuntu Forums: https://discourse.ubuntu.com/t/ethernet-cable-and-gpu-doesnt-seem-to-be-detected-after-a-power-outage/66729

UPDATE (2025-11-18T18:41:55-0500)

I am having the same issue, but this time, the problem was not caused by a power outage, but because I accidentally pressed the power button while my system was on. When I turn on my system, the login screen is shown at a very low resolution (it seems 800x600)

The post on Ubuntu Discourse had some relevant information to solve the issue, but as of time of writing, when I click on the link, the following message is shown: "Oops! That page doesn’t exist or is private.". I have some vague memories of the answer of that post:

These are the steps that I followed this time to troubleshoot the issue:

1. Edit grub configuration file

Set the following variables in the configuration file:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10

1. Execute "sudo update-grub"
2. Turn off system
3. Turn on system
4. In GRUB menu, press "e". Then, press "Advanced options for Ubuntu". The following options were shown:

Ubuntu, with Linux 6.14.0-34-generic
Ubuntu, with Linux 6.14.0-34-generic (recovery mode)
Ubuntu, with Linux 6.14.0-33-generic
Ubuntu, with Linux 6.14.0-33-generic (recovery mode)

I selected "Ubuntu, with Linux 6.14.0-33-generic". I inferred the GPU was correctly detected because the login screen was shown in the appropriate resolution: 2560x1080.

1. sudo apt update
2. sudo apt upgrade
3. Turn off computer
4. Turn on computer

The problem persisted.

1. Turn off computer.
2. Turn on computer.
3. In GRUB menu, press "e". A new option was added in "Advanced options for Ubuntu":

Ubuntu, with Linux 6.14.0-35-generic
Ubuntu, with Linux 6.14.0-35-generic (recovery mode)
Ubuntu, with Linux 6.14.0-34-generic
Ubuntu, with Linux 6.14.0-34-generic (recovery mode)
Ubuntu, with Linux 6.14.0-33-generic
Ubuntu, with Linux 6.14.0-33-generic (recovery mode)

When I selected "Ubuntu, with Linux 6.14.0-35-generic", the problem persisted.

I will be using "Ubuntu, with Linux 6.14.0-33-generic" for the time being.

UPDATE (2025-11-18T18:59:37-0500)

I checked my mail and I was able to find the messages from the post. The user who replied my post recommended executing sudo apt dist-upgrade. So, I followed these steps:

1. Turn on computer.
2. In GRUB menu, press "e"

The following options were shown:

Ubuntu, with Linux 6.14.0-35-generic
Ubuntu, with Linux 6.14.0-35-generic (recovery mode)
Ubuntu, with Linux 6.14.0-34-generic
Ubuntu, with Linux 6.14.0-34-generic (recovery mode)
Ubuntu, with Linux 6.14.0-33-generic
Ubuntu, with Linux 6.14.0-33-generic (recovery mode)

I selected "Ubuntu, with Linux 6.14.0-33-generic".

3. Log-in
4. Execute sudo apt dist-upgrade
5. Turn off computer
6. Turn on computer and wait for the timer in the GRUB menu to finish so that the default option is selected

I concluded that the problem was solved because I could see the login screen in full resolution: 2560x1080.

7. Revert the changes that I did in /etc/default/grub so that the GRUB menu is not shown whenever I turn on my computer.

Change from:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10

to:

GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0

8. Execute sudo update-grub.

I've been trying to enable hibernation functionality to my installation of Ubuntu 24.04 LTS and am failing miserably!

I'm running it on an Intel Core i7-7700K with 16GB of RAM and SSD. I'm using a 20GB SWAP partition at the end of my storage unit.

I tried to set my system to hibernate by using sudo systemctl hibernate, but it didn't work and got

Call to Hibernate failed: Sleep verb 'hibernate' is not configured or configuration is not supported by kernel

Then I tried to enable it in the kernel and recompile it, but also didn't work. The compilation broke for a different reason altogether, and I can't figure out why.

Can someone help me out here? Any help would be greatly appreciated!

On a fresh install of Ubuntu 24.04 Desktop on an old Dell Precision T3600, I'm experiencing constant mouse and keyboard freezes that require a reboot to recover. I've also tried to install 24.04 on a virtual machine on an XCP-ng 8.2.1 host but cannot even complete the install process without having to reboot the VM and rebuild it.

I've never had this kind of problems with an Ubuntu long term release going back to the original one in June 2006 or any previous release going back to the original one in 2004.

Has anyone else had the mouse / keyboard freeze problem and, if so, were you able to resolve the issue and how? As it is ... this new long term release is completely unusable.

I have an X710 dual 10Gbps SPF+ card made by Intel, it is not properly recognised by Ubuntu 20.04

I don't really know how to get it to work, does anyone know how to overcome this?

# lspci | grep X710
43:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
43:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)

ethtool enp67s0f0
Settings for enp67s0f0:
    Supported ports: [ ]
    Supported link modes:   Not reported
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: No
    Supported FEC modes: Not reported
    Advertised link modes:  Not reported
    Advertised pause frame use: No
    Advertised auto-negotiation: No
    Advertised FEC modes: Not reported
    Speed: Unknown!
    Duplex: Unknown! (255)
    Port: Other
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: off
    Supports Wake-on: d
    Wake-on: d
    Current message level: 0x00000007 (7)
                   drv probe link
    Link detected: no

# uname -r
5.15.0-48-generic

root@charles:~# lspci -nnk | grep 0200 -A3
01:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
    DeviceName:  Intel i350-AM2
    Subsystem: ASUSTeK Computer Inc. I350 Gigabit Network Connection [1043:853b]
    Kernel driver in use: igb
--
01:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
    DeviceName:  Intel i350-AM2
    Subsystem: ASUSTeK Computer Inc. I350 Gigabit Network Connection [1043:853b]
    Kernel driver in use: igb
--
43:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ [8086:1572] (rev 02)
    Subsystem: Intel Corporation Ethernet Converged Network Adapter X710-2 [8086:0007]
    Kernel driver in use: i40e
    Kernel modules: i40e
43:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ [8086:1572] (rev 02)
    Subsystem: Intel Corporation Ethernet Converged Network Adapter X710 [8086:0000]
    Kernel driver in use: i40e
    Kernel modules: i40e

$ sudo lshw -C network | grep -B5 enp67s0f
       description: Ethernet interface
       product: Ethernet Controller X710 for 10GbE SFP+
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:43:00.0
       logical name: enp67s0f0
--
       description: Ethernet interface
       product: Ethernet Controller X710 for 10GbE SFP+
       vendor: Intel Corporation
       physical id: 0.1
       bus info: pci@0000:43:00.1
       logical name: enp67s0f1

# dmesg | grep -e enp67 -e i40e
[    2.870003] i40e: Intel(R) Ethernet Connection XL710 Network Driver
[    2.877424] i40e: Copyright (c) 2013 - 2019 Intel Corporation.
[    2.907461] i40e 0000:43:00.0: fw 6.0.48442 api 1.7 nvm 6.01 0x800035cf 1.1747.0 [8086:1572] [8086:0007]
[    2.992889] i40e 0000:43:00.0: MAC address: 40:a6:b7:95:81:8c
[    2.999281] i40e 0000:43:00.0: FW LLDP is enabled
[    3.028430] i40e 0000:43:00.0: PCI-Express: Speed 8.0GT/s Width x8
[    3.049573] i40e 0000:43:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 64 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA
[    3.076016] i40e 0000:43:00.1: fw 6.0.48442 api 1.7 nvm 6.01 0x800035cf 1.1747.0 [8086:1572] [8086:0007]
[    3.190486] i40e 0000:43:00.1: MAC address: 40:a6:b7:95:81:8d
[    3.204780] i40e 0000:43:00.1: FW LLDP is enabled
[    3.235347] i40e 0000:43:00.1: PCI-Express: Speed 8.0GT/s Width x8
[    3.244233] i40e 0000:43:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 64 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA
[    3.359453] i40e 0000:43:00.0 enp67s0f0: renamed from eth0
[    3.621598] i40e 0000:43:00.1 enp67s0f1: renamed from eth1

# sudo modprobe -r i40e && sudo modprobe i40e
# ethtool enp67s0f0
Settings for enp67s0f0:
    Supported ports: [  ]
    Supported link modes:   Not reported
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: No
    Supported FEC modes: Not reported
    Advertised link modes:  Not reported
    Advertised pause frame use: No
    Advertised auto-negotiation: No
    Advertised FEC modes: Not reported
    Speed: Unknown!
    Duplex: Unknown! (255)
    Auto-negotiation: off
    Port: Other
    PHYAD: 0
    Transceiver: internal
    Supports Wake-on: d
    Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: no

I have windows 11, and I downloaded virtualbox and installed Ubuntu 22 04. I followd this tutorial step by step.

Ubuntu finished installation without any issues, but when I try to run it, it seems to get stuck. I am including a snapshot below:

I have tried restarting my computer, but nothing seems to work. Can anyone help with the solution? Thanks in advance.

PS I have looked at posts such as Unable to install Ubuntu 22.04 LTS on virtualbox But does not seem to solve my problem

First time Linux user.

I'm trying to get Ubuntu fully installed on an external SSD connected with a USBC cable. I want it to be fully installed, so it can work on any computer. The linux flashed thing is on a USB. The problem is that during the 'copying files' stage of the installation, I get Errno 5, Input / output error.

The first time I tried, I didn't realise I needed to disable the boot flags on the internal windows HDD. Linux was installed correctly with no errors - I could see the file system - but I couldn't boot from it.

The second time I tried, I disabled the boot flag on the internal hdd. Now when I try to install linux on the external SSD, I get the aforementioned error. I tried again and ran ubiquity no-migration-assistant before trying to install, but I got the same error.

Any thoughts?

Specific information:

• Secure boot is disabled. Fast boot is disabled. The laptop has ahci enabled.
• Version of linux: 22.04 LTS https://ubuntu.com/download/desktop
• The computer is an Acer i7-3537u, 2.0ghz, 4GB memory, 500TB HDD, with USB 3.0 and a nvidia geforce grafics card. Windows is installed on the HDD (I do not want to touch this HDD).

I recently started using a remote Ubuntu server for development and testing machine. However the hosting provider reported a crypto mining process was running and he had to shut down the server.

There were no logs or any data that could identify that process or anything that could help figure out what happened. Then it happened again, but this time they captured this:

PID    USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND  
246369 redis     20   0   13928  11444    908 S 746.7   0.2  62801:13 /tmp/kmv --pool pool.hashvault.pro:80 --username TRTLv2TW8sjC5LmSpiDdRZ2ndnEwPRpJ9Lgz3vgGY2CTSLkLeKAUFMefEeT6idQBxzSLsXfAvAqfhH5zkxMM3sHu2RL8xh1n5Pg --password x --algorithm chukwa_v2

The only ports that are open are Redis port, 6379.

admin@nicotine2:~$ sudo ufw status
Status: active

To                 Action      From
--                 ------      ----
22                 ALLOW       Anywhere
9200               DENY        Anywhere
6379/tcp           ALLOW       Anywhere
22 (v6)            ALLOW       Anywhere (v6)
9200 (v6)          DENY        Anywhere (v6)
6379/tcp (v6)      ALLOW       Anywhere (v6)

When I checked, there was no /tmp/kmv folder anywhere to be found. This has happened for the 2nd time.

Any clues, recommendations or suggestions to avoid this?

I've been trying to fix this for about 4 hours now and I'm not 100% sure how to phrase the problem, so bear with me.

Background

I've been using my Laptop with Linux for a couple of months now and everything mostly went fine. It was running Mint, but I'm not going to ask you for help with a Mint system. Anyway, for some reason I decided that I had to reboot my System today and that's where the woes began. There were a lot of different errors, most of which I don't really recall, nor found a solution to. I still had access to my files so I decided to back them up and reinstall the OS, the latest Ubuntu this time. The initial installation went mostly fine, however here are some of the problems I've encountered:

Problems

After the initial installation and the first reboot (which went without a problem), the reboot after that however did not succeed.

• Nouveau prevented me from both booting the system and getting into the GRUB menu.

  I don't have the exact error message, but I believe there are enough threads around on this very problem.

  I "solved" this by reinstalling it again and installing the official Nvidia Driver. As per standard, through the driver I selected the integrated GPU as standard, as the Nvidia one burns through my battery life quite quickly. Yada yada yada, next reboot:

• Same problem as before, despite having the nvidia driver installed.

  This time I thought it was smart. I booted up Ubuntu through my flash drive, mounted the other installation and looked up how to edit the grub.cfg without breaking anything. I replaced quiet splash with nomodeset on all the launch options, and rebooted again:

• Completely new problem: hdaudio hdaudioC0D2: Unable to bind the codec

  This wasn't just a warning, the entire system refused to boot after displaying the message. I still couldn't get into the GRUB. I also found nothing on the message except for some threads on other distributions and completely different situations.

Status Quo

I reinstalled Ubuntu and made sure not to leave the Nvidia GPU option. It does reboot fine, however, I would very much like this problem solved and I have no idea how. I'm hesitant to put any data on the system when it could basically break on any reboot. Is my laptop cursed or is there any way to save it?

Today, I installed the software update from Ubuntu. Then on reboot, I never got to login screen. Something kept flashing on screen, but was too fast to see what it was saying.

Was able to ssh from another computer, dmesg says: "API mismatch: the client has the version 384.111, but this kernel module has the version 384.90. Please make sure that this kernel module and all NVIDIA driver components have the same version."

How could this mismatch happen, since my updates are via the software updater? Appears someone released a driver that the kernel wasn't expecting or some other error occurred.

How do I fix this?

Thanks.

I'm trying to set up my Ubuntu server 16.04 LTS Xenial to run a DHCP Server that provides the required information to a very specific device.

That device is a TV Decoder by Orange ISP (French vendor is Sagem), and it only works if the IP address is assigned by the Livebox 3 by Orange (TM) (same vendor). This restriction avoids having a different DHCP server than the one provided by Orange.

If I want to use my own DHCP server running in Ubuntu 16.04 to avoid the one running at the Livebox (it's crappy) I need to adapt my configuration.

Bootstrap Protocol (ACK) using TV Decoder and DHCP, both from Sagem

Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0x35139a37
Seconds elapsed: 0
Bootp flags: 0x8000, Broadcast flag (Broadcast)
Client IP address: 0.0.0.0
Your (client) IP address: 192.168.1.153
Next server IP address: 192.168.1.1
Relay agent IP address: 0.0.0.0
Client MAC address: Sagemcom_37:a1:9a (f0:82:61:37:a1:9a)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (ACK)
    Length: 1
    DHCP: ACK (5)
Option: (54) DHCP Server Identifier
    Length: 4
    DHCP Server Identifier: 192.168.1.1
Option: (51) IP Address Lease Time
    Length: 4
    IP Address Lease Time: (843s) 14 minutes, 3 seconds
Option: (58) Renewal Time Value
    Length: 4
    Renewal Time Value: (421s) 7 minutes, 1 second
Option: (59) Rebinding Time Value
    Length: 4
    Rebinding Time Value: (737s) 12 minutes, 17 seconds
Option: (1) Subnet Mask
    Length: 4
    Subnet Mask: 255.255.255.0
Option: (6) Domain Name Server
    Length: 4
    Domain Name Server: 192.168.1.1
Option: (15) Domain Name
    Length: 4
    Domain Name: home
Option: (28) Broadcast Address
    Length: 4
    Broadcast Address: 192.168.1.255
Option: (3) Router
    Length: 4
    Router: 192.168.1.1
Option: (125) V-I Vendor-specific Information
    Length: 41
    Enterprise: The Broadband Forum (formerly 'ADSL Forum') (3561)
        Length: 36
        Option 125 Suboption: (4) GatewayManufacturerOUI
            Length: 6
            GatewayManufacturerOUI: 307CB2
        Option 125 Suboption: (5) GatewaySerialNumber
            Length: 15
            GatewaySerialNumber: AN16XXXXXXXXXX
        Option 125 Suboption: (6) GatewayProductClass
            Length: 9
            GatewayProductClass: Livebox 3
Option: (255) End
    Option End: 255

To emulate the same behavior from my own ISC DHCP Server in Ubuntu I had customized it, based on the found documentation and options.

Basically, the point is to send only to the TV decoder the following additional codes:

• Code 15: Domain name
• Code 72: Default World Wide Web Server.
• Code 125: V-I Vendor Specific Information

Based on the ISC DHCP server documentation, the three codes exist and they could be easily sent by adding the convinient options:

• domain-name text
• www-server ip-address
• vendor-encapsulated-options string

Firstly, I tried that way:

/etc/dhcp/dhcpd.conf

# Create an option namespace called orangetv
option space orangetv code width 1 length width 1;
option orangetv.GatewayManufacturerOUI code 4 = text;
option orangetv.GatewaySerialNumber code 5 = text;
option orangetv.GatewayProductclass code 6 = text;
    
# Linux Router
subnet 192.168.1.0 netmask 255.255.255.0 {
    option domain-name-servers 192.168.1.1;
    option broadcast-address 192.168.1.255;
    option subnet-mask 255.255.255.0;
    option routers 192.168.1.5;
    range 192.168.1.100 192.168.1.199;    
    class "sagem-vendor-classes" {
    match if substring(option vendor-class-identifier, 0, 5) = "sagem";        
    option domain-name "home";        
    option www-server 193.253.67.89;
    vendor-options-space orangetv;
    option orangetv.GatewayManufacturerOUI "307CB2";
    option orangetv.GatewaySerialNumber "AN16XXXXXXXXXXX";
    option orangetv.GatewayProductclass "Livebox 3";                       
    }

}

Once the new config was saved, I checked the configuration syntax by running: sudo dhcpd -t -cf /etc/dhcp/dhcpd.conf

Then, I restarted the DHCP server to reload the new config (ISC DHCP 4.3 fails sometimes to restart and reload the new config. This is somehow related to the Apache2 server. Therefore I suggest forcing it):

sudo -i
service dhcp restart
service isc-dhcp-server restart
service isc-dhcp-server6 restart
service apache2 restart

Now, I rebooted the TV Decoded, and traced the network with Wireshark again. The result of the Bootstrap ACK was

Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0x70907f18
Seconds elapsed: 0
Bootp flags: 0x8000, Broadcast flag (Broadcast)
Client IP address: 0.0.0.0
Your (client) IP address: 192.168.1.153
Next server IP address: 192.168.1.5
Relay agent IP address: 0.0.0.0
Client MAC address: Sagemcom_37:a1:9a (f0:82:61:37:a1:9a)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (ACK)
    Length: 1
    DHCP: ACK (5)
Option: (54) DHCP Server Identifier
    Length: 4
    DHCP Server Identifier: 192.168.1.5
Option: (51) IP Address Lease Time
    Length: 4
    IP Address Lease Time: (843s) 14 minutes, 3 seconds
Option: (1) Subnet Mask
    Length: 4
    Subnet Mask: 255.255.255.0
Option: (3) Router
    Length: 4
    Router: 192.168.1.5
Option: (6) Domain Name Server
    Length: 4
    Domain Name Server: 192.168.1.1
Option: (15) Domain Name
    Length: 4
    Domain Name: home
Option: (28) Broadcast Address
    Length: 4
    Broadcast Address: 192.168.1.255
Option: (72) Default WWW Server
    Length: 4
    Default WWW Server: 193.253.67.89
Option: (255) End
    Option End: 255
Padding: 0000000000000000

As you notice, options 15 and 72 were correctly parsed by option 125 is missing. So, I tried to use the encapsulated vendor options as recommended in the manual. I Used

option vendor-encapsulated-options 7d:29:00:00:0d:XXXXXXXX:20:33

instead of the vendor-options-space method, but it failed again.

I used another workaround to send the code 125 as explained in [https://lists.isc.org/pipermail/dhcp-users/2012-July/015793.html][1]

/etc/dhcp/dhcpd.conf

# Create an option namespace called orangetv
option space orangetv code width 1 length width 1;
option orangetv.GatewayManufacturerOUI code 4 = text;
option orangetv.GatewaySerialNumber code 5 = text;
option orangetv.GatewayProductclass code 6 = text;

# Package the orangetv namespace into option 125
option space vivso code width 4 length width 1;
option vivso.orangetv code 3561 = encapsulate orangetv;
option vivso.iana code 0 = string;
option op125 code 125 = encapsulate vivso;

# Linux Router
subnet 192.168.1.0 netmask 255.255.255.0 {
    option domain-name-servers 192.168.1.1;
    option broadcast-address 192.168.1.255;
    option subnet-mask 255.255.255.0;
    option routers 192.168.1.5;
    range 192.168.1.100 192.168.1.199;    
    class "sagem-vendor-classes" {
    match if substring(option vendor-class-identifier, 0, 5) = "sagem";        
    option domain-name "home";        
    option www-server 193.253.67.89;
    option vivso.iana 01:01:01;
    option orangetv.GatewayManufacturerOUI "307CB2";
    option orangetv.GatewaySerialNumber "AN16XXXXXXXXXXX";
    option orangetv.GatewayProductclass "Livebox 3";                       
    }

}

Despite these configurations, the DHCP server is not sending the code 125 win the vendor specifics.

Any other suggestions?

For some reason am unable to locate wpa_supplicant.conf file on my Ubuntu PC. I am using Ubuntu 16.04 LTS. I did run a find and here's the result:

~$ sudo find / -iname wpa_supplicant.conf
[sudo] password for popo01: 
find: ‘/run/user/1000/gvfs’: Permission denied
/etc/dbus-1/system.d/wpa_supplicant.conf

The wpa_supplicant.conf located in dbus-1 is an xml file and looks something like this:

https://apt-browse.org/browse/ubuntu/trusty/main/i386/wpasupplicant/2.1-0ubuntu1/file/etc/dbus-1/system.d/wpa_supplicant.conf

This doesn't seem to be the right wpa_supplicant.conf file.

Without the wpa_supplicant.conf, anytime I need to work with wpa_cli for establishing p2p connection between peer wifi devices, I need to kill wpa_supplicant and restart it again with my own p2p.conf file. How do I make these settings permanent? I do not want to go through the process of killing and restarting wpa_supplicant every time I boot my PC.

I have some serious tearing problems and I dont like Compton. And compiz is too heavy. Is there any WM alternatives?

I was using openshot and blender to create some animated titles and it was working fine until openshot just started to cry out for blender for no apparent reason. The previews work fine, and some appear to be working. It seems like simple ones involving just text work but any that require 3D modelling do not work. Here's the error I get:

Blender, the free open source 3D content creation suite is required for this action (http://www.blender.org).

Please check the preferences in OpenShot and be sure the Blender executable is correct. This setting should be the path of the 'blender' executable on your computer. Also, please be sure that it is pointing to Blender version 2.62 or greater.

Blender Path: blender

Error Output: No frame was found in the output from Blender

But it was working fine from the same directory before. And it should be a compatible version, as I've got 2.66a installed.

The only thing I can think is that this started happening after Ubuntu (13.04 Raring Ringtail) updated some python files. I'm not sure what they were exactly, but I know there was an update involving Python which I know blender needs to function, so it could be a bug in the latest Python or blender being incompatible with it.

I can also open blender and use it just fine, but I haven't tried rendering anything in it yet because I don't know how to use it, so I'd have nothing to render!

Thanks in advance, let me know if you need any more information and/or logs (but I'm a complete Ubuntu noob, so I'll need some help if you do want any logs :P).

EDIT: Just read Openshot's blog and saw that 1.4.4 was released and available through their PPA. I tried installing that, but the problem hasn't gone away. Here's the PPA if you're interested:

sudo add-apt-repository ppa:openshot.developers/ppa
sudo apt-get update
sudo apt-get install openshot openshot-doc

Another edit: Figuring it was a problem with blender I downloaded the latest version (2.68a) which comes in a .tar.bz2 file which is supposed to be run like a portable application. After redirecting openshot's blender directory to the extracted files the problem still remains. Got it from this site:

http://www.blender.org/download/get-blender/

I've recently upgraded my station to 13.04 and all mounts I had on /etc/fstab stopped working. I can't even mount them at terminal (using mount -t cifs) through smbclient or nautilus. I always get NT_STATUS_LOGON_FAILURE.

Provided nothing has changed at the server, I assume some configuration has changed in the packages of 13.04. Maybe password encryption, maybe port? I have just spent 10 hours looking for a solution and, since I have a serious time retrain, I am considering rolling back to 12.10. Could someone give a clue where to find it?

Thanks all.

I am looking for a step by step method for enabling write in indian languages (hindi and gujarati) in Ubuntu applications (browser, LibreOffice, Pidgin etc..).

Could anyone please provide me a method for beginner to do it or simply direct me to the one if you know?