When I add a key to an SSH agent (using ssh-add, for example), I get a dialog that pops up asking me to "Please enter a passphrase to protect the received secret key ... within gpg-agent's key storage". I don't understand what the point of this is supposed to be. I'm attempting to load this key into ssh-agent's memory and I don't understand what this dialog is proposing to do or what the purpose of its interference is meant to be. If the dialog times out, the key doesn't get retained by ssh-agent. I don't want to store the key anywhere other than where it already lives in ~/.ssh. How do I get this dialog to stop pestering me so I can just add keys to ssh-agent?

Assuming one must remain on 24.04, is it possible to use the built in Gnome integration for Onedrive? I've concluded it is not, but I've seen videos with the 24.04 background with it functioning. So a part of me is hoping I'm just missing something.

The question is to determine if it is possible or impossible. "How to do..." would be another question.

From what I gather:

• Ubuntu 24.04 only supports Gnome 46.

• Gnome 46 only supports gvfs 1.54.*

• gvfs 1.54.4-0ubuntu1 is the most up to date version of gvfs for 1.54.

• There are known bugs in gvfs 1.54.4-0ubuntu1 and prior which prevents the builtin Onedrive support from functioning.

• Those bugs are resolved in later releases (IE: 1.55.*) which are only supported if upgrading beyond 24.04.

I'm aware there are other solutions for connecting to Onedrive from Linux, which I'll begin to consider once I rule out the builtin support.

G'day all...typical question for a newbie,,,so tired of Microsoft-Windows controlling MY laptop. I am some what PC literate, curious to know (yep it's been asked many times I suppose) for me should I start with LTS or Pro. I have RUFUS downloaded and ready to get into Ubuntu/Linux. Running Dell 5220 Latitude 32gb ram 512 memory etc. Thanks.

My system is Lubuntu 22.04.5 LTS on a laptop.

Because I would like to keep my battery as healthy as possible, I want to make sure that the charging level stays between certain boundaries, but the hardware in my laptop does not support battery charge limits, so I turned to make use of a bash script (which I found at Github and modified it to my needs) which is called via crontab every 5 minutes. It then gives me a notification which tells me the battery charge in %, with a message warning me when it becomes to low (when the charger is not connected) or when it is too high (when the charger is plugged in), the third possibility in the notification text is that it just tells me the charge when it is between the given boundaries in the script. This works okay, but the trouble started when I added a spoken message to the script by using a line in the script that is meant to do just that.

The spoken message uses spd-say and the bash script works fine with spd-say giving the audio only when I call the script from terminal. But when the script is called from crontab it also makes the notification text appear alright, but then there is no sound at all to be heard.

I also tried aplay, which plays soundfiles and this gives a similar result, when the script is called from terminal it works, but not when called from crontab.

Here is the script, it is located at /usr/local/bin and it is called battmon.sh:

# ------------------------------------------------------------------
# Script Name:   battmon.sh
# Description:   A Simple Bash Script for Battery Level Charge 
#                Notifications
# Website:       https://gist.github.com/ostechnix
# ------------------------------------------------------------------
# Define thresholds
HIGH_THRESHOLD=80
LOW_THRESHOLD=40
LOGFILE="/tmp/battmon.log"
# Get the battery level
LEVEL=$(acpi -b | awk -F', ' '{print $2}' | tr -d '%,')
# Ensure LEVEL is a valid number
if [[ "$LEVEL" =~ ^[0-9]+$ ]]; then
    # Check for high battery level
    if [ "$LEVEL" -ge "$HIGH_THRESHOLD" ]; then
        echo "$(date) - Battery at $LEVEL%. Sending high battery notification..." >> "$LOGFILE"
        DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 notify-send -t 0 "Accu is vol" "De accu is nu opgeladen tot boven het ingestelde maximale niveau van $HIGH_THRESHOLD % en is nu $LEVEL % , ontkoppel de lader !" >> "$LOGFILE" 2>&1
        spd-say -t female1 -w "stop direct met opladen ! de accu is vol, stop meteen met opladen, want de accu is meer dan $LEVEL% procent vol!"
    fi
    # Check for low battery level
    if [ "$LEVEL" -le "$LOW_THRESHOLD" ]; then
        echo "$(date) - Battery at $LEVEL%. Sending low battery warning..." >> "$LOGFILE"
        DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 notify-send -t 0 "Accu is laag" "De accu is nu ontladen tot onder het ingestelde minimale niveau van $LOW_THRESHOLD % en is $LEVEL %. Sluit nu de lader aan!" >> "$LOGFILE" 2>&1
        spd-say -t female1 -w "begin nu direct met opladen ! de accu is leeg, begin  meteen met opladen, want de accu heeft nog maar $LEVEL% procent lading !"
    fi 
    # Check for good battery level
    if [ "$LEVEL" -ge "$LOW_THRESHOLD" ] && [ "$LEVEL" -le "$HIGH_THRESHOLD" ]   ; then
        echo "$(date) - Battery at $LEVEL%. Sending normal battery level message..." >> "$LOGFILE"
        DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 notify-send -t 10000 "De accu is geladen op een veilig niveau en is nu $LEVEL% procent" >> "$LOGFILE" 2>&1
        aplay /home/paul/Muziek/spraak/ttsmaker-file-2026-1-10-21-23-47-accuniveau-test-2.wav
        spd-say -t female1 -w "de accu heeft nog steeds een goede lading van op dit moment $LEVEL% procent"
    fi
fi

I used

crontab -e

and entered this line:

*/5 * * * * /usr/local/bin/battmon.sh >> /tmp/battmon.log 2>&1

I also tried to use the cron in another way, as I understood that there is the difference in cron for the user and the system, so to try it in the system way and I did:

sudo nano /etc/crontab

and added the same line there:

*/5 * * * * /usr/local/bin/battmon.sh >> /tmp/battmon.log 2>&1

But to no avail...

At this moment I have no clue how to fix this, maybe it is not possible at all to call these sound outputting programs from crontab, but maybe someone does know how to do it right. In either case I am very curious about the why and how.

So on Ubuntu 24.04, is there a way to reduce the volume when at max 100%? i have an external audio interface and i control the volume from there. but when i change from windows to Ubuntu i have to lower the volume to 80% in the system. i hope is this is not confusing, i just want to lower the volume when the slider is at 100% in the system settings. I am not trying to boost volume above 100%, and I am not looking for per-application volume control. I want a system-wide volume cap or scaling, preferably persistent across reboots.

I am currently working on an Ubuntu-based project, and require Git to be installed and available across the entire operating system. In addition, I need a compiler in order to build, compile, and manage the project properly.

My Zinnia Momentum MT1060 graphics tablet has a computer area and as phone area which means that it'll switch to the area of what electronic device that it is connected, however it has been recognizing my laptop as a phone meaning it's using the phone area and not the computer area. How can I fix this?

The drawing tablet is compatible with Ubuntu 16.04 and above as said in the readme.txt file that comes with it

The Graphics Tablet supports the following operating systems:

• Microsoft Windows XP, Vista, 7, 8, 10, 11 32-bit and 64-bit systems

• Apple MacOS 11 and above Version of the 64-bit system. The latest supported version is Mac OS 13.

• Android 4.4 and above. The latest supported version is Android 11.

• HarmonyOS 2.0

• AliYun OS and other Android-type set-top box operating systems

• Ubuntu 16.04 and later

And also my Ubuntu version:

   Distributor ID: Ubuntu
   Description: Ubuntu 24.04.3 LTS
   Release: 24.04
   Codename: noble

I noticed my package openhab was upgraded yesterday, although I told APT to hold it back:

erik@MinipcLG2:~$ sudo apt-mark showhold
openhab
openhab-addons
erik@MinipcLG2:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Linuxmint
Description:    Linux Mint 22.2
Release:        22.2
Codename:       zara

I've got unattended-upgrades running daily, but as far as I understood, apt hold should keep that from upgrading openhab. I've got another script running apt upgrade -y daily (which is probably frowned upon, but what's the difference with me running that script manually every day...?), but that also should not update any held packages, right...?

Does anyone have an idea what might have happened? And how I could avoid this in the future?

Thanks in advance for anyone's help!

Does anyone have any idea how this was possible? And how I could avoid it in the future?

Thanks in advance for anyone's help!

Newly installed Ubuntu 24.04.3 LTS on new machine. (ASUS Vivobook S 14 M3407HA)

I hear an intermittent connect/disconnect sound effect as though some hardware were being connected or disconnected (like a USB dongle). This maybe happens every two minutes or so. The sidebar briefly flickers at the same time. There's nothing plugged into the machine.

How can I diagnose and fix this issue?

I also saw similar behaviour in Fedora.

Some other posts have mentioned clues might be found in /var/log/syslog, so here's a dump of the last 200 lines: https://pastebin.com/mmM9H9Ww

Has anyone seen where nightlight is not working on 24.04 after an in place upgrade? I had this issue months ago, did a fresh install of 22.04 and night light worked perfect.

I finally upgraded to 24.04 again (same hardware) and again night light is not working. I've done everything I've found online but nothing works:

• add a color profile
• settings reset org.gnome.settings-daemon.plugins.color night-light-enabled

I really don't want to reinstall 22.04 again. Does anyone have any tips on how I can troubleshoot this and possibly fix it?

Did Not Connect: Potential Security Issue

Firefox detected a potential security threat and did not continue to www.torproject.org because this website requires a secure connection.

What can you do about it?

www.torproject.org has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.

The issue is most likely with the website, and there is nothing you can do to resolve it.

If you are on a corporate network or using antivirus software, you can reach out to the support teams for assistance. You can also notify the website’s administrator about the problem.

I'm trying to set up a DNS server on a VM. When I try to change the internet config so I can use some commands (That's what the guide I'm using says.) it just straight up doesn't work, and I don't know why. I have it 1 to 1. I tried changing the spaces, but it didn't change anything.

The config:

network:
    ethernets:
        enp0s3:
          optional: true
          addresses:
           dhcp4: true
           - 192.168.10.10/24
           gateway4: 192.168.10.1
           nameservers:
             addresses:
             - 192.168.10.10
             search: []
        enp0s8:
            addresses:
            - 192.168.10.10/10
            gateway4: 255.255.255.0
            nameservers:
               addresses: [192.168.10.200, 192.168.10.220]
    version: 2

root@server:/etc/netplan# netplan try
Invalid YAML: inconsistent indentation:
           - 192.168.10.10/24
           ^
root@server:/etc/netplan# _

How do I get Camera and Cheese to work without glitching? By Glitching I mean that the video is corrupted or dropped. The rate at which the video drops is in proportion to the amount of movement movement infront of the video camera. The glitching can occur from every 3 to 10 seconds.

The fact that Kamoso works fine makes me think that the C920 webcam may be configured differently between Camera and Kamoso or the streaming video may be processed differently.

ANSWER: The problem is the C920 can't support the bit rate over USB 2.0 that Camera configures by default. It may be raw YUYV I don't know. My guess is that Kamoso might use MJPEG which has a lower bit rate.

I suppose I could reload guvcview and see if I could configure it to drop frames. When I tried it briefly it didn't have any problem but I think I was using MJPEG.

This has been quite a learning experience. Thanks for coming along!

Using Ubuntu 24.04 LTS from a 128Gb USB stick.

HP EliteDesk 800 G1 SFF with Intel® Core™ i7-4770 × 8 and 32 G RAM

Windows SSD is disconnected so I don't accidentally mess it up.

Webcam is Logitech C920 HD Pro connected with USB.

Start Camera or Cheese. Both display video but it glitches.

I installed Kamoso and it just works. No glitches.

If I start Kamoso first, then run Camera or Cheese they no longer glitch. Without Kamoso running they glitch.

I also tried guvcview. It didn't glitch but it had way more capability than I needed.

I've tried the following but I'm just following hints from google search.

v4l2-ctl --list-devices
sudo apt update && sudo apt full-upgrade
video group: sudo usermod -aG video $USER

Fresh install of Ubuntu 24.04.

There's a desktop application called "gjs" that grabs focus on login. Appears in the sidebar as a cog icon. Other than the sidebar entry, there's nothing on screen, it just steals focus. Shown as "Desktop Icons 1" when tabbing between applications. If the process is killed it is immediately restarted.

What is it and how can I make it not do the thing it's doing?

More information:

$ echo $XDG_CURRENT_DESKTOP  
ubuntu:GNOME

I have an Nvidia laptop with hybrid graphics (RTX 4080 mobile + Intel iGPU) and Ubuntu 25.10 installed with the recommended drivers (version 580-open).

I know that since Ubuntu 25.04 Nvidia Dynamic Boost (which is working correctly on Windows) is enabled by default. However, how can I check if it is actually working?

At the moment, the instructions provided by Nvidia can only work on X11 while Ubuntu 25.04 and 25.10 defaults to Wayland https://download.nvidia.com/XFree86/Linux-x86_64/580.95.05/README/dynamicboost.html

I had to switch Grub to EFI on an Ubuntu server LTS 22.04 system historically installed in Legacy, so I have installed these following packages: grub-efi-amd64-signed + shim-signed + efibootmgr + grub-efi-amd64-bin via chroot (through Live Ubuntu desktop 22.04 LTS media).

So I have mounted all by following this method here : https://doc.ubuntu-fr.org/tutoriel/grub-efi

When I have done this:

modprobe efivars

I have a message "FATAL: Module efivars not found in kernel x.x.x.xx" (I assuming I have run my Live Ubuntu Desktop media through UEFI boot with Secure boot enabled, so efivars should be loaded?),
so once in chroot on my server, I have also mounted this mount point below (in more than the others mentioned).

mount -t efivarfs none /sys/firmware/efi/efivars

Once all is mounted, I have launched this command for installing Grub-EFI signed:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --uefi-secure-boot /dev/sda

All seems installed well, I can see several files installed in /boot/efi/EFI/ubuntu/* and in ../BOOT/* paths), but when I reboot normally on my Ubuntu server, Grub is displayed in "bash minimal" mode, unable to select the line for booting on my server as usual.

I did differently. I only installed "grub-efi" package and launched the install command like this:

grub-install --target=x86_64-efi --no-nvram /dev/sda

Once installed, I can boot on my server in UEFI mode but only without Secure boot...

How can I process to be able for my server to boot in UEFI with Secure boot (for avoiding reinstalling it on itself in UEFI mode)?

(I have tested to do the revert situation: changing boot Grub from UEFI to Legacy on a test-server Ubuntu 22.04 => success to boot both UEFI (when UEFI boot) + Legacy (when BIOS only mode).
Hybrid-boot Grub only perfectly works when server was first installed in UEFI with secure boot with Legacy mode added, if the server is first installed in Legacy, it no pass check of Secure Boot when I add UEFI boot).

Please someone can help me for Secure Boot to my Grub in UEFI mode? I would not want to keep Secure Boot disabled for booting in my server if possible.

Thank you very much for your help!

Here is a view of my devices disks:

Disk /dev/sda : 50 GiB, 53687091200 bytes, 104857600 sectors
Disk model: Virtual Disk
Units : sector of 1 × 512 = 512 bytes
Sector size (logical / physical) : 512 bytes / 512 bytes
I/O size (minimum / optimal) : 512 bytes / 512 bytes
Disk label type : gpt
Disk identifier : 17A739DC-BFE9-476C-A9AD-213A493D5775

Device        Start       End  Sectors Size Type
/dev/sda1       2048      4095      2048     1M BIOS boot
/dev/sda2       4096   1052671   1048576   512M EFI System
/dev/sda3    1052672 104855551 103802880  49,5G Linux RAID

Disk /dev/sdb : 50 GiB, 53687091200 bytes, 104857600 sectors
Disk model: Virtual Disk
Units : sector of 1 × 512 = 512 bytes
Sector size (logical / physical) : 512 bytes / 512 bytes
I/O size (minimum / optimal) : 512 bytes / 512 bytes
Disk label type : gpt
Disk identifier : C41F1F54-0484-4A91-A1C6-AB5BFBC692F3

Device        Start       End  Sectors Size Type
/dev/sdb1       2048      4095      2048     1M BIOS boot
/dev/sdb2       4096   1052671   1048576   512M EFI System
/dev/sdb3    1052672 104855551 103802880  49,5G Linux RAID

Disk /dev/md0 : 49,46 GiB, 53112471552 bytes, 103735296 sectors
Units : sector of 1 × 512 = 512 bytes
Sector size (logical / physical) : 512 bytes / 512 bytes
I/O size (minimum / optimal) : 512 bytes / 512 bytes
Disk label type : gpt
Disk identifier : A74B1A2E-8513-4DA2-B794-704D1218

I have a Dell Precision 7680 with Ubuntu 24.04. The webcam has not worked since I got it about a year and a half ago. Now I would like to use it and I'm having trouble getting it working in either the browser or camera apps like Cheese/Snapshot.

I have ran an apt-get update and upgrade. I don't think it should affect anything, but my Nvidia GPU is using the recommended drivers.

lsusb -v shows my webcam info:

Bus 001 Device 002: ID 0c45:6a1b Microdia Integrated_Webcam_FHD
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.01 ...

v4l2-ctl --list-devices shows:

Integrated_Webcam_FHD: Integrat (usb-0000:00:14.0-3):
    /dev/video0
    /dev/video1
    /dev/media0

I have confirmed that $USER is part of the video group.

I've tried getting my camera read by the browser -> camera is detected but no frame data.

I tried systemctl --user restart pipewire and running snapshot. Same thing, no frame data but the red camera icon shows up and the webcam led flashes white. I also installed cheese and I get the same result. Here are the cheese logs:

WARN IPAManager ipa_manager.cpp:154 No IPA found in '/usr/lib/x86_64-linux-gnu/libcamera'
[0:01:06.821076494] [5710]  INFO Camera camera_manager.cpp:284 libcamera v0.2.0

(cheese:5710): GStreamer-CRITICAL **: 20:01:43.887: gst_structure_get_value: assertion 'structure != NULL' failed

** (cheese:5710): WARNING **: 20:01:44.457: could not generate thumbnail for /home/esther/Videos/Webcam/2025-07-23-124636.webm (video/webm): Child process exited with code 1

Has anyone managed to get Chrome Remote Desktop working in 24.04?

I have just fresh installed on a KVM container and I'm really struggling to get it running. The .deb installs fine, but when trying to authorise it, I get the following errors (although it still lets me choose an access code):

mark@mark:~$ DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="xxx" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=$(hostname)
[0501/123811.619098:ERROR:host_config.cc(83)] Failed to read /home/mark/.config/chrome-remote-desktop/host#ea82410c7a9991816b5eeeebe195e20a.json
[0501/123811.619379:ERROR:usage_stats_consent_linux.cc(31)] No host config file found.
Enter a PIN of at least six digits: 
Enter the same PIN again: 
[0501/123820.196691:ERROR:host_config.cc(83)] Failed to read /home/mark/.config/chrome-remote-desktop/host#ea82410c7a9991816b5eeeebe195e20a.json
[0501/123820.351170:ERROR:host_starter_base.cc(305)] Failed to exchange the authorization_code due to an OAuth error.
Couldn't start host: OAuth error.

I have used CRD in Ubuntu since 2020 without any problems, including multiple reinstalls with 20.04 and 22.04.

This is an alternative error I also get on different attempts:

mark@mark:~$ DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="xxx" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=$(hostname)
[0501/125439.889574:ERROR:host_config.cc(83)] Failed to read /home/mark/.config/chrome-remote-desktop/host#ea82410c7a9991816b5eeeebe195e20a.json
[0501/125439.890030:ERROR:usage_stats_consent_linux.cc(31)] No host config file found.
Enter a PIN of at least six digits: 
Enter the same PIN again: 
[0501/125445.333032:ERROR:host_config.cc(83)] Failed to read /home/mark/.config/chrome-remote-desktop/host#ea82410c7a9991816b5eeeebe195e20a.json
Trace/breakpoint trap (core dumped)

Any help appreciated!

I moved Ubuntu to drive D (flash drive) with these commands:

wsl --shutdown
wsl --export Ubuntu D:\WSL\UbuntuBackup.tar 
wsl --unregister Ubuntu 
wsl --import Ubuntu D:\WSL\ D:\WSL\UbuntuBackup.tar --version 2 

I inserted the flash drive into my laptop, but my Ubuntu is not there. It needs to be imported as in the last command:

wsl --import Ubuntu D:\WSL\ D:\WSL\UbuntuBackup.tar --version 2 

After working on my laptop, I need to export my Ubuntu again and then import on my PC. It is very uncomfortable. I wish I didn't have to do this. I just want to plug in the flash drive and work. I have already seen similar questions on this site, but they were several years ago. Is this possible now?

I'm trying to install a Linux virtual machine on a macOS Monterey 12.4 to take some courses on Udemy and I'm having a problem. I leave a link with a series of images (they may or may not be useful, but I leave it anyway).

The last print shows the login to which it does not go beyond. The steps I followed were from here. This guide is designed to only work with installing Ubuntu on Apple Silicon Macs.

I used UTM virtual machine software for Mac.

I am a new Linux user; I've consulted other forum posts to the best of my ability but I have not been able to figure this issue out on my own.

This is a Dell Inspiron 7856, recently installed Ubuntu 22.04 LTS (removed Windows entirely after testing out features from live). It operated fine the first few days, and I have not messed with the terminal much besides installing basic program packages. As of recently, I cannot boot into the OS. There is some delay on the screen and then it displays the message:

Gave up waiting for root file system device. Common problems:

...

ALERT! UUID=4d71a352-fbe5-4718-b71f-f71a6c0fd37b does not exist. Dropping to a shell!

Easy solutions: I have not changed any BIOS settings besides those required for installation and I am not using a VM. Can confirm AHCI is enabled and secure boot disabled.

I am now in live mode from the USB I used to install. I am unsure if I have to access/reassign the UUIDs in question but when I search for them I only see UUIDs from the flash drive, to my understanding.

blkid

$ sudo blkid
/dev/sda1: BLOCK_SIZE="2048" UUID="2022-04-19-10-23-19-00" LABEL="Ubuntu 22.04 LTS amd64" TYPE="iso9660" PARTLABEL="ISO9660" PARTUUID="a09db2b8-b5f6-43ae-afb2-91e0a90189a1"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="ESP" LABEL="ESP" UUID="8D6C-A9F8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Appended2" PARTUUID="a09db2b8-b5f6-43ae-afb1-91e0a90189a1"
/dev/sda4: LABEL="writable" UUID="b3355d14-1ea5-4c5b-be3e-44e62dcafb3f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ab0aadc3-1a3f-7b4a-92e6-09b13e35d629"
/dev/loop1: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda3: PARTLABEL="Gap1" PARTUUID="a09db2b8-b5f6-43ae-afb0-91e0a90189a1"
/dev/loop5: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"

/dev/disk/by-uuid

$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Apr 27 03:36 2022-04-19-10-23-19-00 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 27 03:36 8D6C-A9F8 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 27 03:36 b3355d14-1ea5-4c5b-be3e-44e62dcafb3f -> ../../sda4

I only see UUIDs from different /sda#s. All of /dev/sda belongs to my flash drive according to fdisk. (Is this because I am in live mode, do I need to access the terminal differently?)

fdisk

$ sudo fdisk -l
Disk /dev/loop0: 2.33 GiB, 2502324224 bytes, 4887352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 61.89 MiB, 64901120 bytes, 126760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 248.76 MiB, 260841472 bytes, 509456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 155.63 MiB, 163188736 bytes, 318728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 81.26 MiB, 85209088 bytes, 166424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 43.63 MiB, 45748224 bytes, 89352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 284 KiB, 290816 bytes, 568 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 14.92 GiB, 16018046976 bytes, 31285248 sectors
Disk model: USB Flash Drive 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A09DB2B8-B5F6-43AE-AFB3-91E0A90189A1

Device       Start      End  Sectors  Size Type
/dev/sda1       64  7129427  7129364  3.4G Microsoft basic data
/dev/sda2  7129428  7137923     8496  4.1M EFI System
/dev/sda3  7137924  7138523      600  300K Microsoft basic data
/dev/sda4  7139328 31285184 24145857 11.5G Linux filesystem


Disk /dev/loop8: 45.86 MiB, 48087040 bytes, 93920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

/etc/fstab

$ ls -lh /mnt/etc/fstab
-rw-r--r-- 1 root root 37 Apr 19 06:02 /mnt/etc/fstab
$ cat /mnt/etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM

I was having some trouble finding the root partition due to /dev/sda being occupied by the USB, but I followed these steps to confirm its location on /dev/loop0. This is my new result after mounting it.

Also may be of note: when I click through the installer steps as if I were to re-install Ubuntu, it skips the step of asking me whether I want to install instead of / alongside the current OS and goes straight into custom partitioning, but only shows me a table underneath /dev/sda with a total of 16 GB to work with (size of flash drive).

Please let me know what other information I can provide / what commands used to do so and I will update my post. Thank you if you read this far; as I said much of this is new to me but I am trying to use it as a learning experience.

I'm quite new to Linux so I please bear with me.

The problem I'm having is that I have accidentally removed a system setting panel from gnome-control-center, using the Main Menu app. I thought it would remove the icon from my applications, but it seems to have removed the entire panel from system settings, making it impossible for me to get in to the settings again.

My question is, is it possible to completely remove gnome-control-center, refresh all the defaults, then re-install it again in hopes of bringing the panels back?

I get these errors in my terminal when trying to run gnome-control-center:

** (gnome-control-center:4523): WARNING **: 17:55:15.125: Ignoring broken panel wifi (missing desktop file)

** (gnome-control-center:4523): WARNING **: 17:55:15.126: Ignoring broken panel wacom (missing desktop file)
**
ERROR:../shell/cc-shell-model.c:419:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Bail out! ERROR:../shell/cc-shell-model.c:419:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)

Those are the panels I accidentally removed.

Yes, I know it was dumb to remove them, but please, I've only JUST migrated to Linux and learning as I go along.

Thanks!

I am very new to writing udev rules and the more I read, the more puzzled I get. I am trying to mount the filesystem of a USB stick to a persistent device name. Here is the output of udevadm info (cut off after block 3 for better readability):

looking at device '/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host2/target2:0:0/2:0:0:0/block/sda/sda1':
KERNEL=="sda1"
SUBSYSTEM=="block"
DRIVER==""
ATTR{SUBSYSTEM}=="block"
ATTR{DEVTYPE}=="partition"
ATTR{PARTN}=="1"
ATTR{MAJOR}=="8"
ATTR{MINOR}=="1"
ATTR{USEC_INITIALIZED}=="1235172438"
ATTR{ID_VENDOR}=="SanDisk"
ATTR{ID_VENDOR_ENC}=="SanDisk\x20"
ATTR{ID_VENDOR_ID}=="0781"
ATTR{ID_MODEL}=="Ultra"
ATTR{ID_MODEL_ENC}=="Ultra\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20"
ATTR{ID_MODEL_ID}=="5581"
ATTR{ID_REVISION}=="1.00"
ATTR{ID_SERIAL}=="SanDisk_Ultra_4C530001080716117381-0:0"
ATTR{ID_SERIAL_SHORT}=="4C530001080716117381"
ATTR{ID_TYPE}=="disk"
ATTR{ID_INSTANCE}=="0:0"
ATTR{ID_BUS}=="usb"
ATTR{ID_USB_INTERFACES}==":080650:"
ATTR{ID_USB_INTERFACE_NUM}=="00"
ATTR{ID_USB_DRIVER}=="usb-storage"
ATTR{ID_PATH}=="pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0"
ATTR{ID_PATH_TAG}=="pci-0000_00_14_0-usb-0_4_1_0-scsi-0_0_0_0"
ATTR{ID_PART_TABLE_UUID}=="7a6efb82"
ATTR{ID_PART_TABLE_TYPE}=="dos"
ATTR{ID_FS_UUID}=="f3f13dad-53c9-4f1b-b9af-95d504904a9f"
ATTR{ID_FS_UUID_ENC}=="f3f13dad-53c9-4f1b-b9af-95d504904a9f"
ATTR{ID_FS_VERSION}=="1.0"
ATTR{ID_FS_TYPE}=="ext4"
ATTR{ID_FS_USAGE}=="filesystem"
ATTR{ID_PART_ENTRY_SCHEME}=="dos"
ATTR{ID_PART_ENTRY_UUID}=="7a6efb82-01"
ATTR{ID_PART_ENTRY_TYPE}=="0x83"
ATTR{ID_PART_ENTRY_NUMBER}=="1"
ATTR{ID_PART_ENTRY_OFFSET}=="2048"
ATTR{ID_PART_ENTRY_SIZE}=="30029824"
ATTR{ID_PART_ENTRY_DISK}=="8:0"
ATTR{TAGS}==":systemd:"
looking at device '/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host2/target2:0:0/2:0:0:0/block/sda/sda1':
KERNEL=="sda1"
SUBSYSTEM=="block"
DRIVER==""
ATTR{SUBSYSTEM}=="block"
ATTR{DEVTYPE}=="partition"
ATTR{PARTN}=="1"
ATTR{MAJOR}=="8"
ATTR{MINOR}=="1"
ATTR{USEC_INITIALIZED}=="1235172438"
ATTR{ID_VENDOR}=="SanDisk"
ATTR{ID_VENDOR_ENC}=="SanDisk\x20"
ATTR{ID_VENDOR_ID}=="0781"
ATTR{ID_MODEL}=="Ultra"
ATTR{ID_MODEL_ENC}=="Ultra\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20"
ATTR{ID_MODEL_ID}=="5581"
ATTR{ID_REVISION}=="1.00"
ATTR{ID_SERIAL}=="SanDisk_Ultra_4C530001080716117381-0:0"
ATTR{ID_SERIAL_SHORT}=="4C530001080716117381"
ATTR{ID_TYPE}=="disk"
ATTR{ID_INSTANCE}=="0:0"
ATTR{ID_BUS}=="usb"
ATTR{ID_USB_INTERFACES}==":080650:"
ATTR{ID_USB_INTERFACE_NUM}=="00"
ATTR{ID_USB_DRIVER}=="usb-storage"
ATTR{ID_PATH}=="pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0"
ATTR{ID_PATH_TAG}=="pci-0000_00_14_0-usb-0_4_1_0-scsi-0_0_0_0"
ATTR{ID_PART_TABLE_UUID}=="7a6efb82"
ATTR{ID_PART_TABLE_TYPE}=="dos"
ATTR{ID_FS_UUID}=="f3f13dad-53c9-4f1b-b9af-95d504904a9f"
ATTR{ID_FS_UUID_ENC}=="f3f13dad-53c9-4f1b-b9af-95d504904a9f"
ATTR{ID_FS_VERSION}=="1.0"
ATTR{ID_FS_TYPE}=="ext4"
ATTR{ID_FS_USAGE}=="filesystem"
ATTR{ID_PART_ENTRY_SCHEME}=="dos"
ATTR{ID_PART_ENTRY_UUID}=="7a6efb82-01"
ATTR{ID_PART_ENTRY_TYPE}=="0x83"
ATTR{ID_PART_ENTRY_NUMBER}=="1"
ATTR{ID_PART_ENTRY_OFFSET}=="2048"
ATTR{ID_PART_ENTRY_SIZE}=="30029824"
ATTR{ID_PART_ENTRY_DISK}=="8:0"
ATTR{TAGS}==":systemd:"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host2/target2:0:0/2:0:0:0/block/sda':
KERNELS=="sda"
SUBSYSTEMS=="block"
DRIVERS==""
ATTRS{SUBSYSTEM}=="block"
ATTRS{DEVTYPE}=="disk"
ATTRS{MAJOR}=="8"
ATTRS{MINOR}=="0"
ATTRS{USEC_INITIALIZED}=="1235109014"
ATTRS{ID_VENDOR}=="SanDisk"
ATTRS{ID_VENDOR_ENC}=="SanDisk\x20"
ATTRS{ID_VENDOR_ID}=="0781"
ATTRS{ID_MODEL}=="Ultra"
ATTRS{ID_MODEL_ENC}=="Ultra\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20"
ATTRS{ID_MODEL_ID}=="5581"
ATTRS{ID_REVISION}=="1.00"
ATTRS{ID_SERIAL}=="SanDisk_Ultra_4C530001080716117381-0:0"
ATTRS{ID_SERIAL_SHORT}=="4C530001080716117381"
ATTRS{ID_TYPE}=="disk"
ATTRS{ID_INSTANCE}=="0:0"
ATTRS{ID_BUS}=="usb"
ATTRS{ID_USB_INTERFACES}==":080650:"
ATTRS{ID_USB_INTERFACE_NUM}=="00"
ATTRS{ID_USB_DRIVER}=="usb-storage"
ATTRS{ID_PATH}=="pci-0000:00:14.0-usb-0:4:1.0-scsi-0:0:0:0"
ATTRS{ID_PATH_TAG}=="pci-0000_00_14_0-usb-0_4_1_0-scsi-0_0_0_0"
ATTRS{ID_PART_TABLE_UUID}=="7a6efb82"
ATTRS{ID_PART_TABLE_TYPE}=="dos"
ATTRS{TAGS}==":systemd:"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host2/target2:0:0/2:0:0:0':
KERNELS=="2:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{SUBSYSTEM}=="scsi"
ATTRS{DRIVER}=="sd"
ATTRS{DEVTYPE}=="scsi_device"
ATTRS{MODALIAS}=="scsi:t-0x00"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host2/target2:0:0/2:0:0:0':
KERNELS=="2:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{SUBSYSTEM}=="scsi"
ATTRS{DRIVER}=="sd"
ATTRS{DEVTYPE}=="scsi_device"
ATTRS{MODALIAS}=="scsi:t-0x00"

According to the output I generated the following rule:

KERNEL=="sd?1", SUBSYSTEM=="block", ATTR{ID_VENDOR_ID}=="0781", ATTR{ID_SERIAL_SHORT}=="4C530001080716117381", OWNER="ft", SYMLINK+="music"

I cannot debug why this is not working. There is no /dev/music created, the stick is still mounted to a cryptic mount point.

I just installed a fresh Kubuntu 18.04 and have a really bad font rendering, or better to say subpixel rendering.

The characters are surrounded by red and green halos. It's different, depending on which font I use, but it's visible everywhere.

It's especially bad in the kde menu and in the "synaptics terminal window".

It's not that bad in Konsole window, but still hard to read (especially the "m"s).

I tried every combination in the "Use anti-aliasing" settings but to no avail, except when I switch it all off.

I even tried to put this in to /etc/environment

FREETYPE_PROPERTIES="truetype:interpreter-version=35 cff:no-stem-darkening=1 autofitter:warping=1"

This is somewhat different but the surrounding colors are still there.

I am using Intel graphics from an i3 6100 CPU.

What can I do?

I want to start a tftp server. Here, I am using inetd.

Configuration file for tftp in inetd.conf.d folder contains :

tftp dgram udp wait nobody /sbin/tftpd tftpd -l /var/tftp

I have changed the tftp folder permissions to 777 and owner to nobody.

When I am running:

 systemctl start /etc/init.d/tftpd

It is throwing this error:

Failed to start etc-init.d-tftpd.mount: Unit etc-init.d-tftpd.mount failed to load: No such file or directory.

What is this error is about ? How can I solve this error ?

Any guidance is greatly appreciated.

Thank You...!

I am trying to upgrade docker-compose since with the current version I get some error when running a .yml file. Here my current situation:

$ which docker
/usr/bin/docker
$ which docker compose
/usr/bin/docker-compose

$ ls -al | grep docker
-rwxr-xr-x  1 root   root    13511128 Feb 28 09:02 docker
-rwxr-xr-x  1 root   root         336 Dez 11  2015 docker-compose
-rwxr-xr-x  1 root   root    11314960 Feb 28 09:01 docker-containerd
-rwxr-xr-x  1 root   root    10464424 Feb 28 09:01 docker-containerd-ctr
-rwxr-xr-x  1 root   root     1976648 Feb 28 09:01 docker-containerd-shim
-rwxr-xr-x  1 root   root    39473368 Feb 28 09:03 dockerd
-rwxr-xr-x  1 root   root      862296 Feb 28 09:01 docker-init
-rwxr-xr-x  1 root   root     2573840 Feb 28 09:01 docker-proxy
-rwxr-xr-x  1 root   root     8195464 Feb 28 09:01 docker-runc

When tryint to update docker-compose from https://github.com/docker/compose/releases. The output of the command:

sudo curl -L https://github.com/docker/compose/releases/download/1.11.2/docker-compose-`uname -s`-`uname -m` > /usr/bin/docker-compose

gives me:

bash: /usr/bin/docker-compose: Permission denied

I am also sudoing the command. Why is that? thanks

I have a laptop running Ubuntu MATE 15.10, and said laptop has an internal media-card reader. I would like to be able to use that media-card reader to boot a liveCD installed on an SD card. Unfortunately, after much searching, I've been unable to find a way to do this. What makes this case special is:

1. My BIOS does not support booting from the SD card, so I need to find a workaround. Using my existing installation of GRUB2 to load a kernel, access the SD card, and boot would be my preferred method. Unfortunately,
2. Every guide I've found online to do this only describes how to boot to a drive that gets listed as an sd* device. My SD card reader lists as mmcblk0 in my Ubuntu install.

So far, I have tried adding modules to my initramfs.img, modifying my grub.cfg, attempting a wide variety of methods for installing a LiveCD image on an SD card, and using the grub console. At the end of the day, however, I still have the same problem: GRUB2 cannot see my mmcblk0 device. I am certain that all I need is to get GRUB to load the appropriate modules/drivers, and see this device.I can handle it from there. Unfortunately, I don't know how to get there.

EDIT:

To try and clarify a bit, what I would like to be able to do is:

1. Insert a bootable SD card with GRUB installed
2. Turn on the machine and procede to the GRUB2 menu
3. Select a generic "SD Card" that will bring up the menu for the GRUB2 install on the SD card.
4. Boot

To do this, I believe that I need to:

1. Load a Linux kernel
2. Load the SD card drivers via said kernel
3. Use the GRUB2 'chainboot' feature to boot onto the SD card

I have a Linux kernel available to GRUB2 on the local machine, with the necessary drivers enabled. All I need to know is how to load the kernel, and how to use it to detect the SD card.

So my computer froze while it was in powersave mode, and I could not reboot it with REISUB, or access it over the network, forcing me to hard reboot. When I rebooted, I was greeted with the message "Read Error" in the top left corner.

I booted into a LiveCD, and tried

fdisk -l

which gave me the following output:

root@ubuntu:/home/ubuntu# fdisk -l
fdisk: unable to read /dev/sda: Inappropriate ioctl for device

I immediately imaged the drive with gddrescue, and then proceeded to run e2fsck. That seemed to complete successfully, and now when I run fsck, I get:

fsck from util-linux 2.20.1e2fsck 1.42.8 (20-Jun-2013)
/dev/sda1: clean, 1475560/18317312 files, 48594157/73242187 blocks

So all seems good over there. However, I still cannot get any output from fdisk, and when I reboot, I still get the same error.

I've just installed Ubuntu 12.10 to dual boot with Windows 8, but every time I choose Ubuntu from grub menu, it always get stuck at this error and won't boot:

Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/920903aa-762f-40d2-8126-87f4b0e6f975 does not exist. Dropping to a shell!

BusyBox v1.19.3 (Ubuntu 1:1.10.3-7ubuntu1.1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs)

I tried with boot-repair, but it doesn't help, here is the log generated it.

I had a nice GUI for changing startup applications (after logging in) on GNOME 2. How can I start that application on GNOME 3?

Where can I download it? What is the package name? What command is used to launch it? I have Pidgin still launching on start, but I have converted back to Empathy, so I would like to know how I can remove Pidgin and start Empathy instead.