All Questions(ubuntu)

I am new to Linux / Ubuntu and want to install the flutter sdk and their docs recommend

1. Create a folder where you can install Flutter. Consider creating a directory at ~/development/.

2. Extract the file into the directory you want to store the Flutter SDK.

tar -xf ~/Downloads/flutter_linux_3.x.tar.xz -C ~/development/

When finished, the Flutter SDK should be in the ~/development/flutter directory.

But placing around 14000 files with a total size of 1.7 GB below my home ~/ directory seems wrong to me. Under Where to install libraries manually? or Where to store Android SDK files two options are recommended:

1. use /usr/local/lib/ as FHS recommends
2. use /opt/ and links to Linux-Filesystem-Hierarchy / opt

So I tried

$ sudo mkdir -p /usr/local/lib/flutter-sdk
$ tar -xf ~/Downloads/flutter_linux_3.24.3-stable.tar.xz  -C /usr/local/lib/flutter-sdk/

But I got hundreds of messages similar to

tar: flutter/docs/platforms/Hybrid-Composition.md: open failed: File or Folder not found
tar: flutter/docs: function mkdir failed: File or Folder not found

Trying sudo tar -xf ... failed.

Questions

• How can I extract the files into the destination folder /usr/local/lib/flutter-sdk/?
• Do I have to make changes of certain rights (read write access) for a normal / non-root user after the folders and files have been extracted?

To install Open-VPN on a server I followed these commands:

Install Ansible and Git:

sudo apt-get install -y python3-pip git rsync ansible

Clone this repository:

git clone https://github.com/d3vilh/openvpn-aws

Then enter the repository directory:

cd openvpn-aws

Install requirements:

ansible-galaxy collection install -r requirements.yml --force

If you see ansible-galaxy: command not found, you have to relogin and then try again.

Make copies of the configuration files and modify them for your environment:

yes | cp -p example.config.yml config.yml

Run the following command to add the docker group if it doesn't exist and add user to the docker group:

sudo groupadd docker

sudo usermod -aG docker $USER

Relogin now to apply group changes.

`Double check that ansible_user is correct for inventory.yml. Nee`d to run installtion on the remote server - follow the recomendations in config file.

`nano inventory.yml`, save the file - `Ctrl+O` and `Ctrl+X` to exit.

Run installation playbook:

sudo ansible-playbook main.yml

After following all instructions for installing OpenVPN, I encountered this error.

> fatal: [openvpn-aws]: FAILED! => {"reason": "couldn't resolve
> module/action 'community.docker.docker_compose_v2'. This often
> indicates a misspelling, missing collection, or incorrect module
> path.\n\nThe error appears to be in
> '/home/ubuntu/openvpn-aws/tasks/openvpn_ubuntu.yml': line 37, column
> 3, but may\nbe elsewhere in the file depending on the exact syntax
> problem.\n\nThe offending line appears to be:\n\n# to the `docker`
> group, so this task may fail.\n- name: Ensure OpenVPN is running
> (Ubuntu).\n  ^ here\n"}

I've been trying different solutions to install OpenVPN, but I haven't been successful. I've searched online for instructions on using Docker files and changing parameters in the openvpn_ubuntu.yml file, but they haven't been helpful. Do you have any ideas on how I can properly install OpenVPN?

This is the line 37 to 40 of this file mentioned in the error:

> 37 - name: Ensure OpenVPN is running (Ubuntu).                        
> 38   community.docker.docker_compose_v2:                              
> 39     project_src: "{{/home/ubuntu/openvpn-aws}}"                    
> 40     state: present

After upgrading to Kubuntu 24.10 yesterday, mounting my encrypted btrfs disks during boot no longer works. The system/primary boot disk, which is also encrypted, is not affected. The disks can be mounted manually via a terminal without any problems and are usable then. As the same thing happened to me with the 24.04 upgrade, I now have to investigate the cause; last time only a new installation helped, this time I had to use Timeshift.

Unfortunately, many help instructions deal with an encrypted boot partition, but it works for me. I have tried many of the suggested solutions from various sources (updating grub, rebuilding initramfs, keyfile pattern in configuration etc) but none of them have had any effect.

Before I try to install the upgrade again, I would be very grateful for any suggestions!

My steps

I have upgraded the system according to the official instructions.

After the upgrade, I restarted the system. The system started, the Grub menu appeared and I selected Kubuntu. I was prompted to enter the password for LUKS; that also worked. The system disk can be unlocked without any problems.

After that, however, the system locked up for 90 seconds because it cannot mount the btrfs disks (on which /home is also located). It then boots up to the login screen. The 90-second timeout can be fixed by commenting out the two btrfs entries in fstab.

fstab

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
#UUID=965E-2AC0                            /boot/efi      vfat    defaults   0 2
UUID=dc5dea20-a27c-4d6b-af94-eb475db79f3f /boot          ext4    defaults   0 2
/dev/mapper/luks-c1e3cbb8-73d0-49e8-b173-59455bb7279d /              ext4    defaults   0 1
/swapfile                                 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

# SSD Storage Pool
UUID=8429c8ad-62be-4298-8326-7f202187a03e /mnt/xxxxx_ssd btrfs defaults,noatime,autodefrag,compress=zstd 0 2

# HDD Storage Pool
UUID=6f9a885d-d08f-4684-a979-223d1e9c4edc /mnt/xxxxx_hdd btrfs defaults,noatime,autodefrag,compress=zstd 0 2

# Raspberry PI (WebDAV)
https://192.168.100.99/xxxxx-webdav    /mnt/xxxxx_ssd/home/xxxxx/.mounts/xxxxx-raspi      davfs   noauto,user,rw  0 0
https://192.168.100.99/transfer-webdav /mnt/xxxxx_ssd/home/xxxxx/.mounts/transfer-raspi   davfs   noauto,user,rw  0 0

# Bind HOME
/mnt/xxxxx_ssd/home /home none bind

UUID=965E-2AC0  /boot/efi       vfat    defaults      0       1

crypttab

# <name>               <device>                         <password> <options>
luks-c1e3cbb8-73d0-49e8-b173-59455bb7279d UUID=c1e3cbb8-73d0-49e8-b173-59455bb7279d     none

# SSD Storage Pool
xxxxx_ssd_1 UUID=79c67ffa-70f5-4f7c-ae48-7a6a8b2f909b /etc/storagekeys/xxxxx_ssd.key luks,noearly,discard
xxxxx_ssd_2 UUID=7534ad5d-094e-4259-aaa5-1fa1e63b5a21 /etc/storagekeys/xxxxx_ssd.key luks,noearly,discard

# HDD Storage Pool
xxxxx_hdd_1 UUID=0525c36c-6ff2-4a42-9b8b-edc21ca62f31 /etc/storagekeys/xxxxx_hdd.key luks,noearly
xxxxx_hdd_2 UUID=e0a7ae73-e13f-492f-82ad-3c2a9dff75f3 /etc/storagekeys/xxxxx_hdd.key luks,noearly

Output of blkid

/dev/mapper/luks-c1e3cbb8-73d0-49e8-b173-59455bb7279d: LABEL="kubuntu_2404" UUID="93370c80-cb8b-4b5d-9da5-8139400a5361" BLOCK_SIZE="4096" TYPE="ext4"
/dev/nvme0n1p5: LABEL="kubuntu_boot" UUID="dc5dea20-a27c-4d6b-af94-eb475db79f3f" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="kubuntu_boot" PARTUUID="c91f9fe9-a67f-4d01-a6c1-333cf0bed36a"
/dev/nvme0n1p3: LABEL="WinSystem" BLOCK_SIZE="512" UUID="54FC642DFC640C14" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5fdf9496-8daf-4df1-9887-4a63e2d93f59"
/dev/nvme0n1p1: UUID="965E-2AC0" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9ce15353-1e7e-44b6-856b-496df47550b9"
/dev/nvme0n1p6: UUID="c1e3cbb8-73d0-49e8-b173-59455bb7279d" TYPE="crypto_LUKS" PARTLABEL="kubuntu_2404" PARTUUID="14b68a26-8039-4ae8-b156-617e92a81c18"
/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="6408A54608A51856" TYPE="ntfs" PARTUUID="9d67681d-9424-4785-b5a8-b67e5d77a4e2"
/dev/sdd: UUID="7534ad5d-094e-4259-aaa5-1fa1e63b5a21" TYPE="crypto_LUKS"
/dev/sdb: UUID="79c67ffa-70f5-4f7c-ae48-7a6a8b2f909b" TYPE="crypto_LUKS"
/dev/sdc: UUID="e0a7ae73-e13f-492f-82ad-3c2a9dff75f3" TYPE="crypto_LUKS"
/dev/sda: UUID="0525c36c-6ff2-4a42-9b8b-edc21ca62f31" TYPE="crypto_LUKS"

Output of lsblk

sda                                             8:0    0   1,8T  0 disk  
└─xxxxx_hdd_1                                 252:3    0   1,8T  0 crypt /mnt/xxxxx_hdd
sdb                                             8:16   0 465,8G  0 disk  
└─xxxxx_ssd_1                                 252:4    0 465,7G  0 crypt /home
                                                                         /mnt/xxxxx_ssd
sdc                                             8:32   0   1,8T  0 disk  
└─xxxxx_hdd_2                                 252:1    0   1,8T  0 crypt 
sdd                                             8:48   0 465,8G  0 disk  
└─xxxxx_ssd_2                                 252:2    0 465,7G  0 crypt 
nvme0n1                                       259:0    0 931,5G  0 disk  
├─nvme0n1p1                                   259:1    0   100M  0 part  /boot/efi
├─nvme0n1p2                                   259:2    0    16M  0 part  
├─nvme0n1p3                                   259:3    0 499,2G  0 part  
├─nvme0n1p4                                   259:4    0   783M  0 part  
├─nvme0n1p5                                   259:5    0     4G  0 part  /boot
└─nvme0n1p6                                   259:6    0 427,4G  0 part  
  └─luks-c1e3cbb8-73d0-49e8-b173-59455bb7279d 252:0    0 427,4G  0 crypt /var/snap/firefox/common/host-hunspell
                                                                         /

If further configurations or files are required, I will be happy to provide them.

Hi everyone,

Last week update didn't go well for flatpak in a ubuntu 24.04 laptop :

Setting up flatpak (1.14.10-1~flatpak1~24.04.1) ...
fatal: Only one or two names allowed.
dpkg: error processing package flatpak (--configure)

I've tried to remove, reinstall, dpkg-reconfigure, added this flatpak repo from launchpad (which gives the 1.14 version), but to no avail. I've never seen this message before so I'm a bit in a loss in front of it.

Any idea I could try please ? For now I've removed it entirely because all updates are blocked because of this (but that's a poor workaround).

After upgrading Ubuntu LTS from jammy to 24.04 noble, logging in hangs with a movable white pointer over black background for a long time, then a graphical message appears that the system "failed to get sink information" in my profile, possibly related to some audio driver, but no helpful details other that I "should fix it".

Warning

Error found when loading /home/ingo/.profile:

Failed to get sink information: No such entity

As a result the session will not be configured correctly. You should fix the problem as soon as feasible.

OK

Does anyone know this message and how to fix?