I'm currently trying to install Ubuntu 26.04 on my Dell laptop, which is equipped with a Realtek RTL8852BE Wi-Fi card. I booted from the installation ISO, but I am running into issues when trying to connect to the internet.

The installer successfully detects and lists all available Wi-Fi networks. However, whenever I try to connect, the authentication fails. I have verified that both the SSID and passwords are correct, and the exact same problem occurs across all the different routers I have tested.

What should I check or investigate to troubleshoot this connection issue during the install phase?

Also, would it be a viable strategy to proceed with an offline installation first and then attempt to resolve the driver/network issues post-install?

Any guidance or troubleshooting steps would be greatly appreciated.

I'm trying to connect to a VPN (ProtonVPN) from a Kali VM on Ubuntu 24.04 host, connected via a university campus network known to use deep packet inspection (DPI).

Symptoms:

• VPN connection attempts fail whether using TCP or UDP transport — same failure pattern regardless of protocol.
• wget to the VPN provider's repo fails with "Temporary failure in name resolution."
• nslookup google.com resolves fine via the local stub resolver (127.0.0.53).
• nslookup repo.protonvpn.com 1.1.1.1 (querying an external DNS server directly) times out completely — no response at all.
• Accessing the VPN provider's website directly in browser also fails to load.

This suggests the network is blocking VPN traffic by detecting the protocol's handshake pattern (DPI), not just blocking a specific port or relying on DNS blacklisting alone, since even external DNS queries on port 53 are unreachable.

Questions:

1. Is this consistent with DPI-based VPN protocol fingerprinting rather than simple port/DNS blocking?
2. What diagnostic steps (e.g., packet capture with tcpdump/Wireshark, testing specific ports) would confirm this definitively?
3. Are there legitimate, commonly-recommended approaches for VPN connectivity on networks like this (e.g., TLS-wrapped tunnels, alternate ports) that are worth investigating, keeping in mind institutional network policies?

I'm a relative newbie to Linux, and I've been unable to boot following recent updates. I have done bunch of research online, and I got to the point of loading live USB. However, upon using Boot Repair, I see that it's not mounting correctly. I thought that maybe I'm missing some configuration step. Please help!

Staging Ground Your question is considered off-topic. Voted off-topic by David, jps.

Off-topic reason: This question is not about programming or software development. Don’t agree your question is off-topic? Edit your question to make it clear why it belongs on Stack Overflow. You can submit your question again for re-evaluation. Tips This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. You can edit the question so it's on-topic or see if it can be answered on another Stack Exchange site, but be sure to read the on-topic page for a site before posting there.

This post is temporarily locked while a community member reviews it. Please check back later. Linux Mint Boot Repair cannot mount Off topic Evaluated 3 hours ago | I'm a relative newbie to Linux, and I've been unable to boot following recent updates. I have done bunch of research online, and I got to the point of loading live USB. However, upon using Boot Repair, I see that it's not mounting correctly. I thought that maybe I'm missing some configuration step. Please help!

boot-repair-4ppa2088 [20260609_2205]

============================== Boot Info Summary ===============================

sda: ___________________________________________________________________________

File system:       iso9660
Boot sector type:  Unknown
Boot sector info:
Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.
   dmesg(1) may have more information after failed mount system call.

================================ 0 OS detected =================================

================================ Host/Hardware =================================

CPU architecture: 64-bit Video: CoffeeLake-H GT2 [UHD Graphics 630] from Intel Corporation Live-session OS is Linuxmint 64-bit (Linux Mint 22.3, zena, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 1.23.0(1.23) from Dell Inc. The firmware is EFI-compatible, and is set in EFI-mode for this live-session. SecureBoot disabled (confirmed by mokutil). BootCurrent: 0005 Timeout: 0 seconds BootOrder: 0000,0001,0003,0004,0005,0006 Boot0000* Ubuntu HD(1,GPT,d7fb0bbe-44ea-494d-b86e-1c1ad78220a9,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) Boot0001* UEFI: SSDPEMKF512G8 NVMe INTEL 512GB, Partition 1 HD(1,GPT,d7fb0bbe-44ea-494d-b86e-1c1ad78220a9,0x800,0x100000)/File(\EFI\Boot\BootX64.efi)0000424f Boot0003* Onboard NIC(IPV4) PciRoot(0x0)/Pci(0x1f,0x6)/MAC(98e7435f140b,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f Boot0004* Onboard NIC(IPV6) PciRoot(0x0)/Pci(0x1f,0x6)/MAC(98e7435f140b,0)/IPv6([::]:<->[::]:,0,0)0000424f Boot0005* UEFI: VendorCoProductCode 2.00 PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/CDROM(1,0x2104,0xa000)0000424f Boot0006* UEFI: VendorCoProductCode 2.00, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,MBR,0x24a1e612,0x2104,0x2800)0000424f

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

Partitions info (1/3): _________________________________________________________

Partitions info (2/3): _________________________________________________________

Partitions info (3/3): _________________________________________________________

fdisk -l (filtered): ___________________________________________________________

Disk sda: 7.5 GiB, 8053063680 bytes, 15728640 sectors Disk identifier: 0x24a1e612 Boot Start End Sectors Size Id Type sda1 * 64 6038399 6038336 2.9G 0 Empty sda2 8452 18691 10240 5M ef EFI (FAT-12/16/32) sda3 6041600 15728639 9687040 4.6G 83 Linux

parted -lm (filtered): _________________________________________________________

sda:8053MB:scsi:512:512:unknown:VendorCo ProductCode:;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL sda iso9660 2026-01-08-18-32-58-00 Linux Mint 22.3 Cinnamon 64-bit ├─sda1 iso9660 2026-01-08-18-32-58-00 24a1e612-01 Linux Mint 22.3 Cinnamon 64-bit ├─sda2 vfat 695F-F85A 24a1e612-02
└─sda3 ext4 0e719347-233e-431e-8905-3e640e76b898 24a1e612-03 writable

Mount points (filtered): _______________________________________________________

                                                         Avail Use% Mounted on

/dev/sda1 0 100% /cdrom efivarfs 292.1K 23% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/sda1 iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sda

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

sprunge.us ko ()

I want to install some zsh themes. But stupidly, I have deleted the whole configuration of the zshrc configuration file, and left the window blank. So it looks like this:

The problem is that manually typing the command ZSH_THEMES="jonathan" doesn't work after saving, and it doesn't show the theme.

I tried fixing it by typing these commands:

Resetting my zsh configuration using this command:

rm -f ~/.zshrc*

To verify the path of my shell:

which zsh

Set the default shell to zsh, if not done with:

chsh -s $(which zsh)

But the terminal still stays the same. My question is: How can I reset my zsh config so the blank file disappears?

The result should look like this:

(And yes I'am a newbie to Ubuntu)

I've been tasked with setting up Smartcard authentication on Ubuntu (and other flavors), but I need some help specifically with Gnome login screen on Ubuntu 22.04/24.04.

The system in question has the smartcard and krb authentication working, but for whatever reason I can't get the GNOME (GDM login) screen to start reading my USB card reader. It's a supported reader and using pkcs tools I can read the card and slot with no problem. I just can't get GNOME to attempt to read the card. The reader never flashes at all. I've followed various tutorials online to no avail.

I have installed the server on VirtualBox and allocated 2 vCPUs and 4096MB base memory.

So if I run free -h the output tells me 3.3Gi total, 474Mi used, and 2.7Gi free. Also 360Mi buff/cache and 2.8Gi available.

The same thing can be confirmed by using top. However the story changes when I use htop instead:

Memory is shown at 252M used out of 3.3G, much lower than the previous reports.
Why is this? I haven't changed any of VirtualBox's advanced settings & only used the unattended install with automatic download of Guest Additions, as well as the CPU & RAM allocations aforementioned.

These Gimp random crashes make me mad. I lost my half an hour work. Why does it crash randomly? I am using 3.0.6 flatpak version. I have installed few plugins but crashes happen when I am not using them. These crashes actually happen when I open about 15-20 images totaling around 100-150 mbs. My laptop has 16 gb ram and AMD Ryzen 5 PRO 3500U. It isn't overheating. Does Gimp have a known bug with working on multiple images?

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.

Following up: Thanks to enzyklopädie instructions below , I can connect to eduroam !

I try to learn and do better next time - I see a log from journalctl in my original question would already help, as pointed by others. I cannot devise how you enzyklopädie got the solution and the command you issued to see the alert you wrote - I think I would take ages to reach out the reason. So, help me educate myself, pls.

By the way, the command:

"

nmcli connection modify eduroam 802-1x.openssl-ciphers "DEFAULT:@SECLEVEL=0"

"

introduces the lines:

"

#Netplan: passthrough setting
openssl-ciphers=DEFAULT:@SECLEVEL=0

"

into

/run/NetworkManager/system-connections/netplan-NM-44fa4c25-2dc7-4a52-b83e-adcd7dd39185-eduroam.nmconnection

but this file is overwritten every time I come to reconnect. So, there remains the question - how to make this instruction/configuration permanent (I come and go between eduroam and other signals)?

I went further to check my thunderbird capabilities under eduroam and I cannot tell how much necessary is to set (but I did) at its configuration:

"

security.tls.version.min 1

"

and for some reason to be able to use the smtp server I use as "Connection Security: " STARTLS rather than SSL/TLS (and the corresponding correct port, of course).

OK, there remains the question "how to make a instruction/configuration permanent" for a given SSI signal?

J.

Good morning.

New additions based on the last comment by heynnema.

My understanding then is that the configuration about the SSL version to be used when I use eduroam is stored in a file called, in my case, /etc/netplan/90-NM-44fa4c25-2dc7-4a52-b83e-adcd7dd39185.yaml (id est, a yaml format file). I check it now and it has the lines (I do not describe here the complete hierarchy)

"

      802-1x.openssl-ciphers: "DEFAULT:@SECLEVEL=0"

"

I have not hand edited this file - my thought is that it (also) became edited with the command

nmcli connection modify eduroam 802-1x.openssl-ciphers "DEFAULT:@SECLEVEL=0"

I had given (which changed also the file a "corresponding" file at
/run/NetworkManager/system-connections ) .

So I think the run time file is generated based upon what is (permanently stored) at the /etc/netplan corresponding yaml file. Therefore, there is the due configuration for me to use with eduroam even after any reboot.

I should say that now I got all configurations I needed. Thanks to everyone who took time to help me.

J.

After the latest operating system update I realized that my productivity went down as I was unable to configure my shell to open a new tab console in the same directory as the already opened tab.

How to reproduce:

• Open a terminal (Ctrl Alt T)
• cd Downloads
• Open a new terminal (Ctrl Shift T)
• New tab opens in ~ but in 24.04 the console opened in ~/Downloads

Any idea how I can get the old behaviour after my update?

The graphical UI has a setting "Preserve Working Directory" with available options: Always - Never - Safe, that does not change the behaviour of the terminal. New tabs open always open in the home directory.

My prompt command variable was used in 24.04 and remains unchanged:

 $ echo $PROMPT_COMMAND setLastCommandState;
echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/$HOME/~}\007";setGitPrompt

Thanks

Solution: switching back to gnome-terminal restored the functionality I worked with in 24.04. Thanks for the help nevertheless! Let's see if ptyxis will add this productivity feature in the future. Nevertheless I love the new Ctrl . to open a terminal from a nautilus window in 26.04.

I'm using Ubuntu 22.04 on a WSLv1 system, which does not support snap:

$ snap list
Interacting with snapd is not yet supported on Windows Subsystem for Linux 1.
This command has been left available for documentation purposes only.

Doing sudo do-release-upgrade breaks with:

sudo do-release-upgrade

Traceback (most recent call last):
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/noble", line 8, in <module>
    sys.exit(main())
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeMain.py", line 241, in main
    if app.run():
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2642, in run
    return self.fullUpgrade()
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 2447, in fullUpgrade
    if not self.doPostInitialUpdate():
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeController.py", line 1438, in doPostInitialUpdate
    self.quirks.run("PostInitialUpdate")
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 102, in run
    func()
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 127, in noblePostInitialUpdate
    self._test_and_fail_on_tpm_fde()
  File "/tmp/ubuntu-release-upgrader-uqmd8iby/DistUpgrade/DistUpgradeQuirks.py", line 1898, in _test_and_fail_on_tpm_fde
    snap_list = subprocess.check_output(['snap', 'list'])
  File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['snap', 'list']' returned non-zero exit status 1.

It is only fair because snap list errors out. Is it possible to upgrade to Ubuntu 24.04 by somehow disabling any snap interaction and sidetracking its attempt to do snap list?

Thanks!

I have a home server that I plan to boot off a USB drive (NOT a live USB, but rather a permanent install to the USB drive). The usual procedure for creating a USB drive with a permanent install on it is this: you use two USB drives. One is a live USB that you boot into, which you then use to install the OS to the other as if it were a normal drive.

Is it possible to skip the middleman and create the permanent install directly? Can I run the installer as a CLI application from within an existing installation, instead of from within the live USB environment?

This might be an XY problem, in which case I'd appreciate any pointers to a better solution! My use case for this is that I'd like to automate my setup as much as possible. Ideally I'd have a script that creates a full installation on a drive without any manual intervention.

Background

My normal process for writing ISOs is downloading them (zsync via script which performs a ISO validation & shows me the package changes (ie. manifest diff from prior download)), then use mkusb to write it to thumb-drive, eg.

guiverc@d7050-next:/de2900/lubuntu_64$ sudo mkusb-nox mantic-desktop-amd64.iso all

I then quickly scan messages & if it looks good, eject the thumb-drive, and boot it on a nearby box & confirm media write there using a method documented here, ie.

• boot it in try mode, and wait awhile to let background media validation occur, scanning the systemd journal using

sudo journalctl |grep casper-md5check

watching for

May 11 08:37:47 ubuntu casper-md5check[3924]: Checking ./boot/grub/loopback.cfg...../boot/grub/loopback.cfg: OK
May 11 08:37:47 ubuntu casper-md5check[3924]: Check finished: no errors found.
May 11 08:37:47 ubuntu systemd[1]: Finished casper-md5check.service - casper-md5check Verify Live ISO checksums.

This validation I believe is essential, as I find 5-8% of ISO writes fail regardless of the hardware being used (ie. different boxes & different thumb-drives).

Question

Can I validate the ISO write using an easy tool, using the same box I used to write it (ie. no reboot or nearby box necessary).

My preference is terminal; as it's where I am for these tasks.

I recently tried using this answer to create a custom .img of my system. I created a fresh Ubuntu Install in a new partition, set everything up, installed all the bloat I need for some stuff and then switched to main my Main Partition to flash an .img of the partition using the default disk manager and Create Partition Image.

It all worked and I now have the .img. I named it accordingly:

(It is 16gb in size)

Then I tried using dd to flash it to a SanDisk 32 Gb USB Stick (150MB Read Speed):

sudo dd bs=4M if=BloatBuntu.img of=/dev/sdd conv=fsync status=progress

That all went fine. I now had the Stick with the stuff on it:

Then I shut off my laptop, pressed down the F12 key as hard as I could and there it was. The glorious Boot Menu. I selected my USB stick thinking everything would go fine and I'd have a nice Live USB everything usable and cool and amazing and rainbow. Instead I got launched right back into the boot menu. Then I tried again - same thing.

So I booted back into my main partition and tried to use this thing in the default disk manager to flash it again. I assumed I'd just messed up the command or something (I'm quite new to Linux, maybe 1 Week). Then I waited for a long period of time and It finished!

Excited I boot into the menu. It said that the Disk isn't bootable and that I should "insert a bootable floppy disk".
Then, a thought came to my mind "Maybe this 32GB San Disk USB Stick is just broken". So I flashed it to a 64 GB San Disk Ultra Extreme SD Card that was much faster. I tried again and again. Nothing ever worked.

When I tried an Ubuntu ISO, which I downloaded via Torrrent to not put strain on their mirrors, it all worked and booted fine.

Now I come here, does anybody have an idea why my USB wont boot? What can be done to help it?

For clarity, I have an Acer Aspire 5 A515-51G-5504

I installed 18.04 years ago and I've been using it ever since. I now use virtual machines for everything but when I started dabbling in linux back in 2018, I didn't understand how bad it was to install stuff on my host machine.

A couple years ago I had to install Wine to do some stuff for work and I'm kind of suspicious that it's malicious. I've tried to get rid of it but it refuses to die, like Tyrion Lannister. I've backed up everything I care about so now I'm 100% cool with nuking this whole thing and starting with a fresh installation of 18.04

My question is: should I change anything about BIOS or UEFI before I plug in my bootable flash drive and go through the installation process? I'm pretty sure I evidently did everything correct when I did this back in 2018 because everything has been fine. I changed my password in BIOS (which I do remember) and I'm pretty sure I enabled secure boot back then for UEFI. I just don't know if I should do this stuff again. Note: I do use this computer for work so I'm super nervous about screwing it up

This is what I get when I do lspci:

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01)
02:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)

And this is what I get when I do sudo dmidecode -t bios -q

    Vendor: Insyde Corp.
    Version: V1.13
    Release Date: 11/08/2017
    Address: 0xE0000
    Runtime Size: 128 kB
    ROM Size: 8192 kB
    Characteristics:
        PCI is supported
        BIOS is upgradeable
        BIOS shadowing is allowed
        Boot from CD is supported
        Selectable boot is supported
        EDD is supported
        Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
        Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
        5.25"/360 kB floppy services are supported (int 13h)
        5.25"/1.2 MB floppy services are supported (int 13h)
        3.5"/720 kB floppy services are supported (int 13h)
        3.5"/2.88 MB floppy services are supported (int 13h)
        8042 keyboard services are supported (int 9h)
        CGA/mono video services are supported (int 10h)
        ACPI is supported
        USB legacy is supported
        BIOS boot specification is supported
        Targeted content distribution is supported
        UEFI is supported
    BIOS Revision: 1.13
    Firmware Revision: 1.10

Please note that apparently, installing Ubuntu on Acer Aspires is notoriously difficult but somehow I managed to do it in 2018. If I should upgrade my BIOS, will that do something unexpected and negative? Part of me doesn't want to touch anything that isn't broken but I also do not want to compromise my security at all.

So am I good-to-go for doing a fresh install of 18.04 from here? Or am I about to screw this up? Thanks :)

I am unable to install anything on my Ubuntu 20.04. The reason looks like dpkg: error: dpkg frontend lock is locked by another process. This is used by following root process /usr/bin/python3 /usr/bin/unattended-upgrade. Also I tried to kill the process but I am getting following error:bash: kill: (9006) - Operation not permitted.Not sure what I can do.Can anyone please help me with this.

If I launch Thunar from the command line it works, but if I try to launch Thunar using sudo, only the icon on the status bar shows up but no window; the same problem happens with gparted, synaptic and double commander, what is wrong?

My problem is the following: on the 192.168.1. * network I have 3 machines. I call them U1 (Ubuntu Desktop), US2 (Ubuntu Server), W1(Windows) and a router named R1 in 192.168.1.1. U1 makes and receives response of a ping from W1 and R1. US2 can ping OUTSIDE the local network (and to R1) but receives no responses from W1 or U1. U1 and W1, when they ping US2, they receive no response. All machines access the internet over R1. US2 is updated with "apt update" without any problem. I apologize for the inconvenience and if this topic is trivial, but I have run out of neurons and I have not found an answer. Thank you in advance for your help. (Google translator) I can't insert logs of US2 because he has only user interface within command line, not GUI.

I want help to

• make Ubuntu 'update && upgrade' itself automatically,
• select the settings for this automatic system.

How can I do it? Please advice about

• where to find the menu (GUI) or file (command line) to do it,
• what settings that can be recommended (if different from the default).

As a bonus, please describe how different types of program packages are treated,

• program packages from Ubuntu repositories and PPAs
• snap packages
• flatpak packages
• other kinds of programs/packages.

I've installed a persistent installation of Lubuntu 19.04 on my USB a while back, which was running with no problems until the booting process started giving errors.

Only the lines after and including [ OK ] started appearing when it stopped booting. The lines before that have always appeared, but they didn't prevent the system from booting.

I've used this tutorial to install before.

The USB used to appear as one drive before in Windows 10, but now it appears like this:

I have no clue what any of these errors mean, and because I'm not very fluent in Linux I think it might be easier to make a fresh install, so if anyone knows how I can fix this that would be great! But if fixing it is too difficult for someone that's not great with Linux, I'm also OK with making a backup of the persistent storage and reinstalling the system, which I would also need help for.

Persistent live drive with a partition for persistence

There are some web sites describing

• new tools
• new features in [new versions of] old tools

that can create a persistent live drive from an iso file with Ubuntu 19.10 and the corresponding Ubuntu family flavours.

• Why and how does it work?
• How is it different from earlier methods for persistent live drives?
• Isn't live the default for a cloned drive?

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.

Questions about the Ubuntu Development version

Background

AskUbuntu is dedicated to helping users with the current released versions of standard Ubuntu and Ubuntu community flavours (Kubuntu, Lubuntu ... Xubuntu).

Still, we may want to try the next Ubuntu version live and/or install it, and we may need to interact with other people about it.

Questions

• How can I participate or get help with the Ubuntu Development Version?

  In April 2018 'Bionic' was released as 18.04 LTS and in July 2018 the first point release as 18.04.1 LTS.

  In April 2020 'Focal' was released as 20.04 LTS and in August 2020 the first point was released as 20.04.1 LTS. In October 2020 'Groovy' will be released as 20.20.

• When should I upgrade if I want a smooth ride (and get help here at AskUbuntu)?

mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/lib/mysql/mysql.sock' (2)

service mysql status
mysql stop/waiting

service mysql restart
stop: Unknown instance: 
start: Job failed to start

find / -name mysql.sock
/var/lib/mysql/mysql.sock

However, I cannot find the file mysql.sock in my server. I don't know how to deal with this problem. Is there any information else I can provide to help me get assistance?
I need your help.

In my /etc/apt/apt.conf.d/50unattended-upgrades i found this:

// Automatically reboot *WITHOUT CONFIRMATION*
//  if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";

The issue is that I don't know what the default value is and so if I need to uncomment the line (I don't want my server to reboot btw).

Should I uncomment the line by safety? Are there further actions to perform after doing that?

I downloaded latest stable Ubuntu (ubuntu-16.04.3-desktop-amd64.iso image that I double checked for authenticity) and used it to boot my new Win10 system which I wanted to wipe. I followed the instructions, like those at

https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase

to unfreeze the drive and wipe it using the

time hdparm --user-master u --security-erase ... /dev/sda3

command. In fact I ran it another time (after resetting the drive password) and running with --security-erase-enhanced option second time (thanks to http://www.stevenmaude.co.uk/posts/securely-erasing-frozen-hard-disks-with-hdparm instructions).

It took almost 2 hours each time to go through the erase process. At the end, no errors were printed out. 0's were shown for various times, like 0 cpu time and 0 system time. Only the elapsed time was showing ~2 hours.

After those two runs, I was still able to open random text and xml files in both Windows and non-Windows directories and look at their contents even though I had not opened them earlier in that same Ubuntu session, so it could not have cached them!

then...

• I could no longer boot into Windows - guess that's a good sign :-)

• After restarting computer and loading up Ubuntu again, it no longer auto-mounts /dev/sda3 (or anything else resembling a hard drive). fdisk -l shows the drive but that's about it.

• Tried loading Paragon bootable CD and it also shows no filesystem.

Any ideas as to what I am missing?

It's almost as if it blew away the entry into the file system but after the two erases it was still able to navigate and find file content in that same session of running Ubuntu. Now I don't seem to be able to see anything because anything I try to run no longer finds starting point for the file system, but I wonder if all the data is still laid out there on disk?!

Thank you!

it has come to my attention that Ubuntu will drop i386 desktop images. so i'm wondering what will happen to software of the same(i386) architecture.

I installed Ubuntu 17.10. Now I am having trouble with gksu:

$ gksu -dg synaptic
No ask_pass set, using default!
xauth: /tmp/libgksu-HgUjgQ/.Xauthority
STARTUP_ID: gksu/synaptic/8760-0-alex-XPS-15-9530_TIME4974977
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: synaptic
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
Unable to init server: Could not connect: Connection refused
(synaptic:8767): Gtk-WARNING **: cannot open display: :1
xauth: /tmp/libgksu-HgUjgQ/.Xauthority
xauth_env: (null)
dir: /tmp/libgksu-HgUjgQ

If I don't use -g, the password dialog is disabled. So looks like a problem with creating a tty for root.

Any advice?

• Ubuntu 14.04LTS server, I have no GUI desktop
• In my example I'll use a fake IP address.
• Trying to mount from Ubuntu to \1.2.3.4\users\me\subdir. Someone has to put a spreadsheet file on the \1.2.3.4\users\me\subdir and my program on Ubuntu has to read it.
• I can ping 1.2.3.4 just fine, so it can't be a firewall issue, right?

I have read about 12 pages from my goole search, a few from this forum but I have nothing that works yet. This is what I did.

sudo mount -t cifs '\\1.2.3.4/users/shared/chuck/subdir' /home/comp/mnt/subdir -o username=chuck,password=CR4gilson 
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

This message is in /var/log/syslog:

Feb 15 09:43:56 ubuntucomp kernel: [7519048.289580] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 15 09:43:56 ubuntucomp kernel: [7519048.289872] CIFS VFS: cifs_mount failed w/return code = -115

In my ufw output samba seems to be allowed anywhere:

Samba                      ALLOW       Anywhere

Thank you!

I know questions that sound like this one have been asked before, but none of the "solutions" are working for me. I am using Gnome Classic option.

• I could not find any extension that does what I want.
• I could not find any entry for gnome-panel in my dconfEditor

Will you please help me.

I installed Gnome 3 using sudo apt-get install ubuntu-gnome-desktop. I am talking of the panel visible in the following picture:

These are the list of extensions I have installed:

Long time forum forager, first time poster.

I bought a Toshiba 500 GB usb 3.0 hard drive last week and instantly ran home to see how fast I could push it. On my desktop (that I built) I was able to get 200 MB/sec. On my laptop (MSI FX something or other), which I dual boot Windows 7/Ubuntu 11.10, I was able to get about 120 MB/sec on Windows, but on Ubuntu, i get about 25 MB/sec.

lsusb shows:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 1532:0015 Razer USA, Ltd
Bus 004 Device 002: ID 0480:a007 Toshiba America Info. Systems, Inc.

lspci -vvv shows that the USB 3.0 host controller is using the kernel driver in use is xhci_hcd.

dmesg |grep usb shows:

[ 1815.455368] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1815.475459] scsi7 : usb-storage 4-1:1.0

The built in disk utility says its connected via usb at 705 MB/s, but that's not what it reports when I transfer files over to it.

Not really sure what to do at this point. Any help would be very nice.