I think somebody may have accessed my laptop and, amongst other things, changed the admin password. Now I cannot log in as admin. Is there a way to fix it?

Lately I've been struggling to install a few updates for the ubuntu snap store. The password that works for logging in and the terminal works, but for whatever reason it won't work on the snap store despite me having no memory or changing I at all. Any idea tl fix this?

I have a few Pi's running UC24 and wanted to "upgrade" them to UC26.

I followed the instructions for the remodel and ran into a boot failure issue on reboot.

From there I decided to install fresh. There was no UC26 option in the rpi-imager so I pulled the

    ubuntu-core-26-arm64+raspi.img.xz

image from https://cdimage.ubuntu.com/ubuntu-core/26/stable/current/ . This boots to a blank screen for me (tried both micro-HDMI ports).

Does anyone else have UC26 running on a Pi5? If so, which image did you use and were there any extra steps?

I just installed kubuntu 26.04; but then I just cannot connect to my University WPA2 enterprise wifi (like I could with 25.20, 24.04 and 22.04), signal eduroam.

This signal is configured with wpa2 enterprise, mschapv2 and peap, but no CA certificate.

At NetworkManager I (no longer? I cannot recall in previous kubuntu versions...) do not have a square to tick "No CA certificate" (initially I thought leaving it blank would mean "No certificate").

The command nm-connection-editor does show a window where I have such square - I save the configuration for eduroam, but I cannot devise where it is saved.

In fact, I can see a file netplan-NM-44fa4c25-2dc7-4a52-b83e-adcd7dd39185-eduroam.nmconnection at /run/NetworkManager/system-connections, but this file does not contain a line , e.g.,

system-ca-cert=false

(or whatever line I should provide to say there is no CA certificate). Also, this file is created at run time.

Yet, at /etc/NetworkManager/system-connections I produced a file netplan-NM-44fa4c25-2dc7-4a52-b83e-adcd7dd39185-eduroam.nmconnection with such line - but I could not devise how to convince the system to use this configuration file when I call for a connection to eduroam.

Currently I see some alternatives, that I do not know exactly how to put in action: i) the NetworkManager to be instructed to not use a certificate, even if it is does not present this option at its configuration window ii) the gui issued by the nm-connection-editor command to record a configuration file that does become used iii) to connect by the nmcli command, but to use a specific configuration file

I googled around , but I must miss some detail here. Thank you,

J.

As indicated, I add to the original question my new comments:

Thanks heynnema and Andrei Borzenkov for inputs.

a) I tried netplan apply and retested, no difference (so I learn there is a /etc/netplan/ directory with some .yaml configuration files); b) I thought my problem might be the CA certificate - well I might not be sure of this. I try to connect to eduroam and it keeps asking for my password, again and again. I do get this eduroam connection through windows 10 (dual boot machine). c) If I understand, this issue of CA certificate might not be the culprit. So I report what I observe at trying to log and I also write below the log "with journactl" with the "relevant lines" (sorry for the length):

"

Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.7625] audit: op="connection-activate" uuid="44fa4c25-2dc7-4a52-b83e-adcd7dd39185" name="eduroam" pid=1873 uid=1000 result="success"
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.7753] audit: op="statistics" interface="wlp0s20f3" ifindex=2 args="0" pid=1873 uid=1000 result="success"
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8335] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8337] dhcp4 (wlp0s20f3): canceled DHCP transaction
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8338] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8338] dhcp4 (wlp0s20f3): state changed no lease
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8531] manager: NetworkManager state is now DISCONNECTED
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8532] device (wlp0s20f3): Activation: starting connection 'eduroam' (44fa4c25-2dc7-4a52-b83e-adcd7dd39185)
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8537] device (wlp0s20f3): supplicant interface state: completed -> disconnected
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8537] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8549] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8561] manager: NetworkManager state is now CONNECTING
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8562] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8564] device (wlp0s20f3): Activation: (wifi) access point 'eduroam' has security, but secrets are required.
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8564] device (wlp0s20f3): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8570] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8571] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8572] device (wlp0s20f3): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No new secrets needed.
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'ssid' value 'eduroam'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'scan_ssid' value '1'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'bgscan' value 'simple:30:-65:300'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'password' value '<hidden>'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'eap' value 'PEAP'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'fragment_size' value '1266'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8576] Config: added 'phase2' value 'auth=MSCHAPV2'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8577] Config: added 'identity' value 'iulek'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8577] Config: added 'proactive_key_caching' value '1'
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8795] device (wlp0s20f3): supplicant interface state: disconnected -> authenticating
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.8795] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> authenticating
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.9218] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.9219] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.9393] device (wlp0s20f3): supplicant interface state: associating -> associated
Jun 15 15:07:08 silicon NetworkManager[213851]: <info>  [1781546828.9394] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
Jun 15 15:07:12 silicon NetworkManager[213851]: <info>  [1781546832.0253] device (wlp0s20f3): supplicant interface state: associated -> disconnected
Jun 15 15:07:12 silicon NetworkManager[213851]: <info>  [1781546832.0253] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> disconnected
Jun 15 15:07:12 silicon NetworkManager[213851]: <info>  [1781546832.1254] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Jun 15 15:07:12 silicon NetworkManager[213851]: <info>  [1781546832.1255] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Jun 15 15:07:25 silicon NetworkManager[213851]: <info>  [1781546845.6761] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
Jun 15 15:07:25 silicon NetworkManager[213851]: <info>  [1781546845.6761] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
Jun 15 15:07:25 silicon NetworkManager[213851]: <info>  [1781546845.7191] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jun 15 15:07:25 silicon NetworkManager[213851]: <info>  [1781546845.7192] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jun 15 15:07:25 silicon NetworkManager[213851]: <info>  [1781546845.7364] device (wlp0s20f3): supplicant interface state: associating -> associated
Jun 15 15:07:25 silicon NetworkManager[213851]: <info>  [1781546845.7364] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
Jun 15 15:07:34 silicon NetworkManager[213851]: <warn>  [1781546854.5693] device (wlp0s20f3): Activation: (wifi) association took too long
Jun 15 15:07:34 silicon NetworkManager[213851]: <info>  [1781546854.5693] device (wlp0s20f3): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jun 15 15:07:34 silicon NetworkManager[213851]: <warn>  [1781546854.5695] device (wlp0s20f3): Activation: (wifi) asking for new secrets
Jun 15 15:07:34 silicon NetworkManager[213851]: <info>  [1781546854.5967] device (wlp0s20f3): supplicant interface state: associated -> disconnected
Jun 15 15:07:34 silicon NetworkManager[213851]: <info>  [1781546854.5967] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> disconnected
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9711] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9715] device (wlp0s20f3): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9719] device (wlp0s20f3): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No new secrets needed.
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9728] Config: added 'ssid' value 'eduroam'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9728] Config: added 'scan_ssid' value '1'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9728] Config: added 'bgscan' value 'simple:30:-65:300'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9728] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9729] Config: added 'password' value '<hidden>'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9729] Config: added 'eap' value 'PEAP'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9729] Config: added 'fragment_size' value '1266'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9729] Config: added 'phase2' value 'auth=MSCHAPV2'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9729] Config: added 'identity' value 'iulek'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9729] Config: added 'proactive_key_caching' value '1'
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9824] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Jun 15 15:07:57 silicon NetworkManager[213851]: <info>  [1781546877.9825] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Jun 15 15:08:00 silicon NetworkManager[213851]: <info>  [1781546880.7687] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
Jun 15 15:08:00 silicon NetworkManager[213851]: <info>  [1781546880.7688] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
Jun 15 15:08:00 silicon NetworkManager[213851]: <info>  [1781546880.8126] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jun 15 15:08:00 silicon NetworkManager[213851]: <info>  [1781546880.8127] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jun 15 15:08:00 silicon NetworkManager[213851]: <info>  [1781546880.8349] device (wlp0s20f3): supplicant interface state: associating -> associated
Jun 15 15:08:00 silicon NetworkManager[213851]: <info>  [1781546880.8350] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
Jun 15 15:08:05 silicon NetworkManager[213851]: <info>  [1781546885.8040] device (wlp0s20f3): supplicant interface state: associated -> disconnected
Jun 15 15:08:05 silicon NetworkManager[213851]: <info>  [1781546885.8040] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> disconnected
Jun 15 15:08:05 silicon NetworkManager[213851]: <info>  [1781546885.9055] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Jun 15 15:08:05 silicon NetworkManager[213851]: <info>  [1781546885.9055] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Jun 15 15:08:19 silicon NetworkManager[213851]: <info>  [1781546899.4321] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
Jun 15 15:08:19 silicon NetworkManager[213851]: <info>  [1781546899.4322] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
Jun 15 15:08:19 silicon NetworkManager[213851]: <info>  [1781546899.4753] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jun 15 15:08:19 silicon NetworkManager[213851]: <info>  [1781546899.4754] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jun 15 15:08:19 silicon NetworkManager[213851]: <info>  [1781546899.4951] device (wlp0s20f3): supplicant interface state: associating -> associated
Jun 15 15:08:19 silicon NetworkManager[213851]: <info>  [1781546899.4952] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated
Jun 15 15:08:22 silicon NetworkManager[213851]: <info>  [1781546902.6583] device (wlp0s20f3): supplicant interface state: associated -> disconnected
Jun 15 15:08:22 silicon NetworkManager[213851]: <info>  [1781546902.6583] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> disconnected
Jun 15 15:08:22 silicon NetworkManager[213851]: <info>  [1781546902.7585] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Jun 15 15:08:22 silicon NetworkManager[213851]: <info>  [1781546902.7585] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Jun 15 15:08:23 silicon NetworkManager[213851]: <warn>  [1781546903.5690] device (wlp0s20f3): Activation: (wifi) association took too long
Jun 15 15:08:23 silicon NetworkManager[213851]: <info>  [1781546903.5690] device (wlp0s20f3): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jun 15 15:08:23 silicon NetworkManager[213851]: <warn>  [1781546903.5692] device (wlp0s20f3): Activation: (wifi) asking for new secrets
Jun 15 15:08:25 silicon NetworkManager[213851]: <info>  [1781546905.5123] device (wlp0s20f3): supplicant interface state: scanning -> inactive
Jun 15 15:08:25 silicon NetworkManager[213851]: <info>  [1781546905.5123] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> inactive
Jun 15 15:08:26 silicon NetworkManager[213851]: <warn>  [1781546906.2536] device (wlp0s20f3): no secrets: User canceled the secrets request.
Jun 15 15:08:26 silicon NetworkManager[213851]: <info>  [1781546906.2536] device (wlp0s20f3): state change: need-auth -> failed (reason 'no-secrets', managed-type: 'full')
Jun 15 15:08:26 silicon NetworkManager[213851]: <info>  [1781546906.2538] manager: NetworkManager state is now DISCONNECTED
Jun 15 15:08:26 silicon NetworkManager[213851]: <warn>  [1781546906.2539] device (wlp0s20f3): Activation: failed for connection 'eduroam'
Jun 15 15:08:26 silicon NetworkManager[213851]: <info>  [1781546906.2541] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Jun 15 15:08:28 silicon NetworkManager[213851]: <info>  [1781546908.9803] policy: auto-activating connection 'acessoLivreUEPG' (6ca6770e-ad6c-4f89-8685-3ec9f427180e)

"

(acessoLivre - undesirable - is the signal it gets automatically if no success in with eduroam).

I hope this brings in more details. Please, let me know if you need more information. I also try to learn from the points you raise.

Thanx.

J.

Since the 26.04 kubuntu upgrade, when I try to log in with ssh using a password, I get a graphical window box asking for the password. I cannot emphasize enough how much I do not want this.

So I disabled the use kdewallet in the system settings, but that wasn't enough. I saw I also had to remove ksshaskpass, which I did, only to receive ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory, so I installed ssh-askpassand now there is a lame looking box asking for a password. Neither of those boxes work, and worse of all they break the use ofsshpass` which I need in some scripts. Yes, I know "use keys", but I can't on some systems, it's not allowed, don't ask me why.

So, how do I get ssh to ask for the password in text, as is traditional ?

I have been using Ubuntu and Windows without issues on a dual-boot setup. The Windows drive mounts automatically on startup in Ubuntu.

However, I want to re-enable BitLocker to encrypt the Windows drive. After reenabling it, Ubuntu will not start. I get the following message:

You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup. Press Enter for system maintenance (or press Control-D to continue):

If I type "systemctl reboot," nothing happens. If I type "exit", the same message appears again.

I have disabled Bitlocker again, but still, I would prefer to have the Windows drive encrypted (it is a laptop I sometimes travel with).

Thanks!

enter image description hereHI team ubuntu.

I have installed 26.04 with cinnamon desktop 6.14 to get custom as desklets, applets etc... but they don't work. the sever does not run and give nothing to see !?

thank you all for your lights.

I have installed 26.04 with cinnamon desktop 6.14 to get custom desklets, applets etc... but they don't work. The server does not run and gives no error messages!

I have a good wired connection, but I can't get anything with applets settings to download. it sounds the server doesn't run at all. I hope the developers team will take a look at it. btw, it always worked with Mint!

I recently upgraded Ubuntu on a multi-boot system. I'm trying a few different linux distro's to try and decide witch is maybe better for what. Anyway the issue was that Ubuntu upgrade just ignored my current config and destroyed grub. The problem was that I am not that experienced so I waisted over 4 hours of my day restoring some semblance of the grub2 that I had to get things up and running again. While this was a learning opportunity!! I was wondering if I did something wrong when I did the upgrade or is there a way to avoid this problem next time? This is important to me because I have no intention of going back to Microsoft again for anything. Thanks in advance.

I am not very computer literate. I installed Ubuntu on an old Surface Go tablet I had and it was working fine except that the website can (command???) didn't work.

In trying to resolve this I followed the kernel installation advice here. Now all I get is a black screen with a commend line. I've tried to reboot from a USB, but nothing happens and I just restart to the black screen every time.

I'd be happy just to start again with a reinstall, but don't know how to do that.

I was a user of RealVNC, because it allows to connect to my computers across any network after signing in with RealVNC account.

However, RealVNC does not support Wayland, and KDE will drop support for X11 in 2027. While Kubuntu 26.04 is going to be supported for five more years, I want to prepare for the full Wayland transition.

There are ways to connect to Wayland via TigerVNC, and it is also possible to connect to PCs in a different network (via tailscale), as explained in this answer. However, this method has some bugs, e.g. the ctrl button does not always work, which is a pain, because I need to run code in my workstation, and it is hard to copy/paste/undo without the control button.

I have read that there are other available options such as RDP, RustDesk and more, but I don't know if they properly support Wayland. I have also read conflicting comments about what actually works, apart from VNC.

What are the other options (apart from TigerVNC) for KDE Wayland, and how to set them up? Does it also support remotely logging in (this feature is supported in RealVNC, but does not work for the related answer regarding TigerVNC, which is running from a logged in account)?

It would be nice if the method also supports other Wayland setups (e.g. GNOME), but that is not strictly necessary.

I installed the latest "Ubuntu touch" on my "Google Pixel 3a" yesterday. But, when I rebooted it, I found a message that "The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device." So, what should I do to solve this serious problem? Please someone help me.

I am experiencing an issue where my Wi-Fi is completely disabled after installing/updating to Ubuntu 26.04 on my Acer Aspire E5-475G laptop.Here are my hardware details:Laptop: Acer Aspire E5-475GWi-Fi Chipset: Qualcomm Atheros QCA9377 Wireless Network Adapter (rev 31)The Problem:The Wi-Fi option is grayed out or shows as "disabled" in the system settings. Clicking the toggle to turn it on does nothing. Bluetooth (which is on the same combo chip) works fine.

What I have tried:Checked BIOS settings to ensure wireless is enabled.Tried toggling the physical Fn + Wi-Fi key combination.How can I get this Qualcomm QCA9377 chipset working properly on Ubuntu 26.04? Is there a specific firmware package (firmware-ath9k or ath10k) or a kernel module parameter needed for this version?Thank you in advance for your help!

I am using Python's SSH module to upload files from a Windows computer (IP: 192.168.5.3) to the device rk3588 (IP: 192.168.5.2). The rk3588 is running Ubuntu 22.04 with kernel version 5.10. Currently, I have 30 Windows PCs, and for some reason, 3 of them occasionally experience slow SSH transmission speeds. Normally, the transmission can be completed in about 6 minutes, but when there is an exception, it can take up to an hour to complete. When I capture packets on the rk3588 side, I find a large number of retransmissions.

I've done this many times on different systems, but this has me puzzled:

OS: Ubuntu 26

Had an external drive that I was mounting using the fstab.

/dev/sda1 /data ext4 defaults 0 0

I removed the drive and of course it rebooted and went into recovery mode. So I edited the /etc/fstab and removed the external drive mount. Now when it reboots, it still hangs up on trying to mount that drive.

Does Ubuntu 26 store the information that is/was in the fstab in another spot? Like a database or other file? I noticed the fstab in Ubuntu 26 is very minimal, so I'm guessing there is some sort of other place that needs to be updated??

I installed Ubuntu 26.04 recently on a new device and enabled full disk encryption.

When I enter the password, sometimes the system does not recognise it and prompts me to enter it again. When I do that, it gets stuck on the loading screen and never boots. Pressing ESC showed me some error messages about the crypt library.

How can I solve this problem? I am forced to do a force restart at least once a day because of that. The keyboard layout is shown to be de So I don't think it is related to a layout mismatch.

#Edit1 Logs below executing journalctl:

If I run reboot command the system logs in without peoblems. So i happens roughly 50% when booting from an off state. It does not happen at all on reboot.

[UPDATE]: I found some threads on Framework's Community boards, and apparently this is a known issue with the AMD motherboard, and a workaround is to use a USB-A to USB-C cable instead of a USB-C to USB-C. I tried it, and was able to pair the phone successfully and tether it to share the network! Would prefer not to involve USB-A, but it seems to be a functioning workaround.

Original post:

I have a Framework 13 laptop (AMD cpu) with Ubuntu 26.04 freshly installed and updated. I plug in my iPhone 16 Pro (iOS 26.5) via USB-C cable, and Ubuntu shows an "Untrusted Device" dialog, and the phone shows a "Trust This Computer?" dialog.

Before I can click "Trust" on the iPhone, the dialog is dismissed. After 3-4 seconds, Ubuntu overlays another "Untrusted Device" dialog, and the iPhone again flashes the "Trust This Computer?" dialog.

It keeps repeating this endlessly, and never gives me enough time to click "Trust" on the iPhone and type in the pairing code.

The USB-C cable is a known working cable from Apple, which works fine to pair/tether the phone to a MacBook. I believe I've also paired this phone and laptop on a previous install of ubuntu, but I hadn't used this laptop in a year, and did a fresh 26.04 install recently, and I'm traveling, and surprised that I can't seem to pair the two to share my phone's internet.

The workaround is to use a wireless tethering method (bluetooth or wifi), but I can't plug my phone in to charge off the laptop without it making both the phone and laptop pop up a dialog every 3-4 seconds.

I spent a couple hours this morning with Claude to see if it could help me track down the issue, and I asked it to summarize what we tried, and here's the relevant bits from that summary:

Root-cause isolation. Verbose usbmuxd logging showed a consistent per-cycle pattern: the device enumerates cleanly, usbmuxd connects, the configuration is switched (0 → 4), preflight begins, reaches "Waiting for user to trust this computer," and then ~0.6–0.8 seconds later the device drops (Device RX aborted due to error or disconnect / Removed device) and re-enumerates. The disconnect timing is fixed and regular, and occurs with nothing on the host actively tearing down the connection — usbmuxd is idle in the trust-wait state when the drop happens. This points to the USB connection being torn down below userspace, at the USB host-controller/xHCI or device level, rather than a pairing-software failure.

What we ruled out (no effect on the drop). Different USB-C ports; the Apple cable (works on macOS); stale host trust state (cleared /var/lib/lockdown, and did Reset Location & Privacy on the phone); the udev rule 39-usbmuxd.rules (masked it entirely — no change); GNOME gvfs/gvfsd-afc contention (masked the volume monitors — the gvfs storm stopped but the ~0.8s drop persisted unchanged); daemon lifecycle (ran a single persistent usbmuxd --foreground so no socket/udev respawn could interfere); and the ipheth kernel module (unloaded it with modprobe -r ipheth — the device still dropped at the same ~0.8s mark with the driver entirely absent).

I have Preserve Battery Health option enabled on Ubuntu 25.10. It is limiting the battery charging capacity at around 80% level but even after shutting down the laptop and turning it on next morning, I see the battery level stays at 80%.

Doesn't it suppose to start at 100% and go down to %80 and stay there? Since OS have no control on the battery after shut down, it should be charged to the maximum level.

What am I missing?

I have a Lenovo ThinkPad X9-15 Gen 1 with Ubuntu 26.04 (Resolute Raccoon, kernel 7.0.0-22-generic) and the built-in camera is not working in any application (Firefox, GNOME Camera, etc.). I tried to replicate solutions, given for ubuntu 24, but with no avail.

Some troubleshooting

Ubuntu version: 26.04

Ubuntu sees the camera:

$ v4l2-ctl --list-devices
Intel MIPI Camera (platform:v4l2loopback-000):
    /dev/video0

What I've already tried:

• Installed oem-sutton-dana-meta, libcamhal0, linux-modules-ipu7-generic, v4l2loopback-dkms

• v4l2-ctl --list-devices shows the camera via v4l2loopback

• ipu7x.so is present in /usr/lib/libcamhal/plugins/

• pw-cli list-objects shows the camera in PipeWire

v4l2-relayd -d fails with:

CamHAL[ERR] load_camera_hal_library, failed to open PCI device
gst_parse_launch_full: assertion 'pipeline_description != NULL' failed

libcamhal-ipu7x cannot be installed due to broken dependencies:

Depends: libjsoncpp25 but it is not installable (Ubuntu 26.04 has libjsoncpp26)
Depends: libia-cca-ipu7x0
Depends: libia-log-ipu7x0
Depends: libcamhal-ipu7x-common

I have a intel wifi adapter that is built into my motherboard and i was able to get wifi back up and running temporarily by just reloading my wifi module but now its not working again after I turned it off and on again the next day and I've tried redownlouding things and reloading wifi module again but nothing is working.the only why I've gotten wifi to my computer is through a wired connection through my phone. it does see the wifi adapter but for some reason i cant get wifi.

I'm setting up a test server on 24.04, moving it from W11 actually.

Got Apache all installed, works fine, http://localhost gives the expected output. Now need to move the web root from /var/www/html to a directory webroot on a different drive mounted as /media/nick/DATA. So:

Edited /etc/apache2/sites-available/000-default.conf to change the DocumentRoot line to /media/nick/DATA/webroot, added the following to /etc/apache2/apache2.conf

<Directory /media/nick/DATA/webroot/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
</Directory>

copied the index.html from the original document root into /media/nick/DATA/webroot, and restarted the server

sudo service apache2 restart

But, all I get is error 403, access forbidden.

Seems I have missed something?

I would like to transfer PDFs, MP3s, and MP4s from Ubuntu 20 Linux to iPhone 16, but I am struggling to find a way to easily do this, and I need your help.

On Android, I'm very used to connecting my phone to my computer with a USB cable, simply copying files over from my computer, locating them via the Files app on Android, and opening them with whatever app makes sense for the file type. I'd like to do the same thing with iPhone.

When I plug my iPhone into my computer via USB, I see two mounts in Files: "Documents on iPhone" and "iPhone". "iPhone" shows pictures and videos from my camera. If I try creating a folder there, I get an error: "Error while creating directory testing123. There was an error creating the directory in gphoto2://[...]. Error creating directory: -6: Not Supported".

In "Documents on iPhone", I see app icons for GarageBand, iMovie, Keynote, Numbers, Pages, Brave, and Firefox. If I double-click Brave or Firefox, I see a Downloads folder. If I try creating a folder there, I get an error: "Error while creating directory testing123. There was an error creating the directory in afc://[...]/Downloads. The connection was interrupted." At that point, I can no longer access ("This location could not be displayed. Sorry, could not display all the contents of "Brave": Unhandled Apple File Control error (2)"), and I have to remount.

Many recommend libimobiledevice and ifuse. I installed those on Ubuntu and can successfully mount my iPhone and copy files to it, but I can't see the files or access them from my iPhone.

I enabled Bluetooth and could successfully pair my iPhone with my computer, but I didn't see any option on either side to initiate a file transfer via Bluetooth, and https://help.ubuntu.com/stable/ubuntu-help/bluetooth-send-file.html.en says "Send Files does not work on unsupported devices such as iPhones."

I don't want to pay for an app to do what I think should be a very simple thing.

I don't want to use cloud services (such as iCloud, Dropbox, Google Drive) because I don't want to upload gigs of data and then download gigs of data. Same applies to email and messaging.

I don't have a Windows or macOS computer to work with.

I don't want to jailbreak my phone.

How can I successfully copy PDFs, MP3s, and MP4s from Ubuntu 20 Linux to iPhone 16 and open them from iPhone?

Im trying to install the IPTV program Hypnotix on Ubuntu 23.04. But i have not succeeded. I have googled around a bit and im starting to think the problem is that Ubuntu 23.04 is very new and for some reason doesnt support Hypnotix yet? Does anyone know what the problem might be? Best regards Ubuntu newcomer Emil

Just upgraded to 22.04 from 21.10. Flameshot not working. I click on the Flameshot icon and nothing happens. How to fix this?

I have a file with an xz extension, ubuntu-19.10-preinstalled-server-arm64+raspi3.img.xz. How do you get the .img out of it?

My goal is to flash the file on an SD card. I want to use www.etcher.io I finally got it to work, but etcher will only handle .iso and .img files.

I'm encountering a connection issue to my university WiFi network that I cannot solve: when attempting to connect, I get the following message with dmesg -T :

[ven. oct. 11 12:32:04 2019] wlan0: deauthenticating from X by local choice (Reason: 3=DEAUTH_LEAVING)

This problem has already been pointed out in the forum, but none of the solutions I tried worked:

• Disabling the powersave for WiFi (in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf set wifi.powersave = 2 ).
• Changing from NetworkManager to WICD.

• Adding the following lines to /etc/sysctl.conf:

  net.ipv6.conf.all.disable_ipv6 = 1
  net.ipv6.conf.default.disable_ipv6 = 1
  net.ipv6.conf.lo.disable_ipv6 = 1
  

None of these worked.

It's an old Asus laptop that i use sometime for programming. It's battery is dead so i have to be connected to power supply whenever i have to use. Was working fine for the last few years(even with a dead battery). Today while i was working on it, the power plug got dislodged from the socket and the computer instantly shutoff (normal, happened a lot previously). But this time when i tried to start it up, the first time- i could hear the wheezy sound(as usual) but the screen was complete black as if it was shutoff. I gave it some time but didn't see anything on the screen so i rebooted. Now the screen lights up proper (as usual) but i get the 'This is not a bootable disk ...Insert a bootable floppy and press any key...' error on the screen. I tried these at the BIOS setup

1. enable/disable UEFI

2. check boot priority ( there's only the hard drive and the dvd drive with the hard drive at the top priority).

No result.

I had a live USB of a Kali distro and i could boot from it (UEFI mode). My hard drive is GPT. It has Ubuntu 16.04 and Lubuntu 18.10 dual booted. Six partition including the sda1(grub_boot). There is no secure boot option in my BIOS setup.

Could anybody suggest :

1. Where should i look to see whether it is a hardware related problem or just the grub is messed up.

2. Should i go ahead with a Boot-repair or wait until it am sure where he problem is. Thanks in advance

                   :Update:

I restarted my system and now, as Ill luck would have it , the screen doesn't even light up though i can hear the fan noise see the power lights. Restarted a dozen of times but to no use so gave up. In the evening, i tried as the last ditch effort but now it's seemed the problem got worse as i could not even hear the fan noise or in fact no noise at all. So couldn't figure out if the POST test is happening or not after pressing the power button. So as a final effort, i started the pc on last time and kept in on for a good 20 minutes and then restarted the System. seems it solved the Dead screen issue and now i can see the pc logo and can enter the BIOS setup. But however, the initial problem still persist so now i am going to do some smart test from the live Kali on flash drive. This is a whole new experience, will update if get any major result.

I have a directory with a lots of images but they are in the wrong orientation. I want to rotate the images to correct the orientation (mostly ±90^o). Using image (shotwell photo) viewer I can rotate them individually by clicking the rotate button but that's too tedious.

I looked at man shotwell and shotwell --help-all but there's nothing that explains how to invoke the rotate command from the command line.

Is there any way I can invoke the rotate command of shotwell (or any other viewer) from the terminal? Or any other methods to rotate images are welcome too.

I'm entirely new to Linux/Ubuntu so please bear with me.

I currently have Windows 7 32Bit and wanted to install Ubuntu. I used the installation off the website and copied it onto my bootable USB. As I installed Ubuntu it says I need to reboot my system - so I did.

As I try to boot up in Ubuntu it just simply says 'MBR-helper missing' and nothing else, however, it lets me boot back up in Windows fine.

Is there a way to get around or repair this error? I can't find a clear answer on forums.

Is this error because I copied it into my USB? Or is this a common yet fixable problem?

Please help.

I have Win8 on my desktop, where a 120G SSD is used to run windows and some select applications, while I have a 2TB HDD to provide basic file storage and where possible, install applications instead of on the SSD.

I want to install Ubuntu on a new partition of the HDD (I allocated 300GB, with 5GB swap file).

I've used a USB to install the OS, which seemed to have done the job. However, after prompting for a restart, I can no longer boot to ubuntu.

During instillation I was confused about where to install the "boot loader instillation". I ended up selecting "/dev/stb" because I figured I would be able to boot with BIOS by selecting the HDD drive as a priority over the SSD.

The bootloader is a large part of where I think I went wrong.

My partition system looked something like this:

/dev/sta  ...               //SSD ~120 GB
/dev/sta1 NTFS (350 MB)     //Win8System
/dev/sta2 NTFS (118 GB)     //Win8C-Drive

/dev/stb ...                //HDD ~2TB
/dev/stb1 NTFS (1563 GB)    //FileStorage
/dev/stb5 Free Space (300 GB)    //Space I want to use for Linux

(NOTE: Created two partitions from the 300GB, ~5GB and 295GB. stb5,stb6.)

It'd be great if I could get an explanation of what drive you'd select for the boot loader and why, and what selections won't work with regards to the Boot Loader Instillation. I think I understand what Grub is, but I have no idea on how to use it, or play around with it.

I seem to be able to get back into OS from my usb, however I believe it's just showing me a preview/trial of Ubuntu (ie, can't access any of the system NTFS drives). Note, if I try to install from the USB again, it will recognize that a version of Ubuntu 13.10 exists on the system.

Apologies in advance, have used windows all my life, don't really know to much about Linux at all. Did have a brief skim over some similar questions, didn't find anything too useful. - Where to install bootloader when installing Ubuntu as secondary OS? - ubuntu 12.10 dual boot with windows 8 on two hdds - Dual-boot Windows 7 and Ubuntu on two SSDs with UEFI

EDIT: Found Solution

Turns out, after I attempted to re-installing once more, that what was required was to create the root partition (~295GB) as a primary partition instead of the default selected Logical. It wouldn't recognize a logically formatted root partition.

All working now, I'm typing this from Ubuntu as we speak. (Yipeee!)

EDIT: Clarification

I still left the boot loader instillation specified to '/stb', and now I can use the BIOS to boot from the SSD or the HDD interchangeably. Very handy.

I still require an explanation as to why:

• Using a Logical partition would not be recognised the system's BIOS (I have an ASUS H-87 Pro Mobo).
• What would be different if I changed my boot loader instillation instead to '/sta'? Would I no longer directly boot into Windows, and instead use the Grub interface every time?
• Is there a preferred place to install the boot loader instillation? Clarifying that specifying volumes such as '/sta1' or '/stb5' would not allow you to load the OS?