I used to use VNC but it does not work with Wayland. How can I connect to my Kubuntu 24.04 (Wayland) computer from another computer in another network so that I can access its GUI, just like in VNC?
I am using Ubuntu Cinnamon. When I use KDE Connect to browse an Android device, it open in VS Code rather than file manager (Nemo). How to fix the issue?
I use KDE Connect between my phone and laptop on my University WiFi. Very often, the IP address changes and the connection stops working. I have to manually find the IP of the computer with the command ip address and put it in my phone and connect manually. The same thing happens when I connect to a different network.
Is there any way to automate the connection process? AFAIK know Mac computers have some robust connection procedure with iOS devices.
I want to be able to do this for multiple computers with the same phone.
I've followed many tutorials, and verified that my old-ish graphics card is compatible with Vulkan, but I still cannot get a Steam games (testing with Balatro) to run on my fresh Ubuntu 24.04 install.
I'm using Nvidia 580.126.09 drivers which is what it defaults to installing when I use ubuntu-drivers install but I have also tried every other one available (that I can find) which are 535.288.01, 570.211.01, and 590.48.01.
I'm trying to use Steam + Proton to play Balatro (a Windows game) on Linux, which according to ProtonDB should work. My best guess as to why it doesn't work has something to do with Nvidia drivers, which is why I listed the graphics card.
My HP laptop has a single NVMe drive on it that I gave a 30GB partition for a new Ubuntu install. The goal was to have a dual-boot machine with Windows 10 being primary. The live CD/USB install of Ubuntu went well, but now I can't force a boot into the Windows partition.
I have tried boot-restore, but that caused an issue with GRUB not working right and making the Ubuntu install not accessible either. I have reverted back to a working Ubuntu install. I tried to fix the Windows 10 loader with a windows live USB, but it can't see the Windows partition. I have also tried a Hiren's Boot USB, but none of the tools there can see the Windows partition either.
What information do I need to share, or steps should I take? I really need to get access to the drive and don't want to wipe it.
Since Ubuntu 24.04LTS offers a very old version of QEMU I decided to compile the latest stable source from:
https://download.qemu.org/qemu-10.2.2.tar.xz
To compile his code I used:
mkdir build && cd build
../configure --enable-kvm --enable-sdl --enable-spice --enable-slirp --enable-usb-redir --enable-libusb \
--target-list=x86_64-softmmu
Of course I had to install several packages as:
sudo apt install python3-sphinx
sudo apt install python3-sphinx_rtd_theme
sudo apt install ninja-build -y
sudo apt-get install libglib2.0-dev
sudo apt-get install libglib2.0-dev
sudo apt install flex -y
sudo apt install bison -y
sudo apt-get install libpixman-1-dev libspice-protocol-dev libspice-server-dev
sudo apt-get install libsdl2-dev
sudo apt-get install libusb-1.0-0-dev libusbredirparser-dev libusbredirhost-dev
I also modified: /etc/libvirt/qemu.conf
to have at the end of this file:
emulatorpath = "/usr/local/bin/qemu-system-x86_64"
I also did:
sudo usermod -aG kvm,libvirt $USER
and finally to compile and install:
make -j$(nproc)
sudo make install
I edited my path to have:
export PATH=$PATH:/usr/local/bin
since the installtion places qemu executables at /usr/local/bin
$ ls -l /usr/local/bin
total 2308228
lrwxrwxrwx 1 root root 22 Mar 1 2025 nsys -> /etc/alternatives/nsys
lrwxrwxrwx 1 root root 25 Mar 1 2025 nsys-ui -> /etc/alternatives/nsys-ui
-rwxr-xr-x 1 root root 39461328 Apr 17 01:34 qemu-aarch64
-rwxr-xr-x 1 root root 39557224 Apr 17 01:35 qemu-aarch64_be
-rwxr-xr-x 1 root root 12175176 Apr 17 01:35 qemu-alpha
-rwxr-xr-x 1 root root 21312432 Apr 17 01:36 qemu-arm
-rwxr-xr-x 1 root root 21434288 Apr 17 01:36 qemu-armeb
-rwxr-xr-x 1 root root 2529984 Apr 17 02:52 qemu-edid
-rwxr-xr-x 1 root root 3836904 Apr 17 02:52 qemu-ga
-rwxr-xr-x 1 root root 22368288 Apr 17 01:37 qemu-hexagon
-rwxr-xr-x 1 root root 12876552 Apr 17 01:37 qemu-hppa
-rwxr-xr-x 1 root root 15575016 Apr 17 01:37 qemu-i386
-rwxr-xr-x 1 root root 10717352 Apr 17 02:52 qemu-img
-rwxr-xr-x 1 root root 10483576 Apr 17 02:52 qemu-io
-rwxr-xr-x 1 root root 2995888 Apr 17 02:52 qemu-keymap
-rwxr-xr-x 1 root root 17543800 Apr 17 01:37 qemu-loongarch64
-rwxr-xr-x 1 root root 13221784 Apr 17 01:37 qemu-m68k
-rwxr-xr-x 1 root root 12358184 Apr 17 01:37 qemu-microblaze
-rwxr-xr-x 1 root root 12257808 Apr 17 01:38 qemu-microblazeel
-rwxr-xr-x 1 root root 18589984 Apr 17 01:38 qemu-mips
-rwxr-xr-x 1 root root 18934112 Apr 17 01:38 qemu-mips64
-rwxr-xr-x 1 root root 18837040 Apr 17 01:39 qemu-mips64el
-rwxr-xr-x 1 root root 18490008 Apr 17 01:39 qemu-mipsel
-rwxr-xr-x 1 root root 19004248 Apr 17 01:39 qemu-mipsn32
-rwxr-xr-x 1 root root 18897880 Apr 17 01:40 qemu-mipsn32el
-rwxr-xr-x 1 root root 11483552 Apr 17 02:52 qemu-nbd
-rwxr-xr-x 1 root root 12268736 Apr 17 01:40 qemu-or1k
-rwxr-xr-x 1 root root 18017784 Apr 17 01:40 qemu-ppc
-rwxr-xr-x 1 root root 18369008 Apr 17 01:40 qemu-ppc64
-rwxr-xr-x 1 root root 18275944 Apr 17 01:41 qemu-ppc64le
-rwxr-xr-x 1 root root 4037752 Apr 17 02:52 qemu-pr-helper
-rwxr-xr-x 1 root root 20331808 Apr 17 01:41 qemu-riscv32
-rwxr-xr-x 1 root root 20642808 Apr 17 01:42 qemu-riscv64
-rwxr-xr-x 1 root root 14635728 Apr 17 01:42 qemu-s390x
-rwxr-xr-x 1 root root 12250120 Apr 17 01:42 qemu-sh4
-rwxr-xr-x 1 root root 12339144 Apr 17 01:42 qemu-sh4eb
-rwxr-xr-x 1 root root 12840424 Apr 17 01:42 qemu-sparc
-rwxr-xr-x 1 root root 13442920 Apr 17 01:42 qemu-sparc32plus
-rwxr-xr-x 1 root root 13376584 Apr 17 01:42 qemu-sparc64
-rwxr-xr-x 1 root root 13571816 Apr 17 02:52 qemu-storage-daemon
-rwxr-xr-x 1 root root 116882456 Apr 17 01:45 qemu-system-aarch64
-rwxr-xr-x 1 root root 52359936 Apr 17 01:45 qemu-system-alpha
-rwxr-xr-x 1 root root 95772416 Apr 17 01:46 qemu-system-arm
-rwxr-xr-x 1 root root 33879656 Apr 17 01:46 qemu-system-avr
-rwxr-xr-x 1 root root 53317136 Apr 17 01:46 qemu-system-hppa
-rwxr-xr-x 1 root root 80874232 Apr 17 01:47 qemu-system-i386
-rwxr-xr-x 1 root root 62130704 Apr 17 01:47 qemu-system-loongarch64
-rwxr-xr-x 1 root root 41044560 Apr 17 01:47 qemu-system-m68k
-rwxr-xr-x 1 root root 35236992 Apr 17 01:47 qemu-system-microblaze
-rwxr-xr-x 1 root root 35239360 Apr 17 01:47 qemu-system-microblazeel
-rwxr-xr-x 1 root root 60581136 Apr 17 01:48 qemu-system-mips
-rwxr-xr-x 1 root root 61566080 Apr 17 01:48 qemu-system-mips64
-rwxr-xr-x 1 root root 65288816 Apr 17 01:49 qemu-system-mips64el
-rwxr-xr-x 1 root root 60492144 Apr 17 01:49 qemu-system-mipsel
-rwxr-xr-x 1 root root 52019168 Apr 17 01:49 qemu-system-or1k
-rwxr-xr-x 1 root root 65632512 Apr 17 01:50 qemu-system-ppc
-rwxr-xr-x 1 root root 72287376 Apr 17 01:50 qemu-system-ppc64
-rwxr-xr-x 1 root root 66706088 Apr 17 01:51 qemu-system-riscv32
-rwxr-xr-x 1 root root 67065288 Apr 17 01:52 qemu-system-riscv64
-rwxr-xr-x 1 root root 34349728 Apr 17 01:52 qemu-system-rx
-rwxr-xr-x 1 root root 51494648 Apr 17 01:52 qemu-system-s390x
-rwxr-xr-x 1 root root 52246760 Apr 17 01:52 qemu-system-sh4
-rwxr-xr-x 1 root root 52337296 Apr 17 01:52 qemu-system-sh4eb
-rwxr-xr-x 1 root root 36288592 Apr 17 01:52 qemu-system-sparc
-rwxr-xr-x 1 root root 53588112 Apr 17 01:53 qemu-system-sparc64
-rwxr-xr-x 1 root root 34714872 Apr 17 01:53 qemu-system-tricore
-rwxr-xr-x 1 root root 84493168 Apr 17 02:53 qemu-system-x86_64
-rwxr-xr-x 1 root root 61588848 Apr 17 01:54 qemu-system-xtensa
-rwxr-xr-x 1 root root 61418928 Apr 17 01:55 qemu-system-xtensaeb
-rwxr-xr-x 1 root root 4005800 Apr 17 02:52 qemu-vmsr-helper
-rwxr-xr-x 1 root root 15485784 Apr 17 01:43 qemu-x86_64
-rwxr-xr-x 1 root root 21922456 Apr 17 01:43 qemu-xtensa
-rwxr-xr-x 1 root root 21754032 Apr 17 01:44 qemu-xtensaeb
I got all running with the some problems:
Error launching details: Host does not support virtualization type 'hvm' for architecture 'x86_64'
Another error I have related to an Ubuntu noble patch, etc.
Also, if I want to create a new VM I get the next two options for Architecture: cris and ppc64le
I have some VMs that for some reason even when they report the error they are able to run but most of the others simply crash.
Any suggestions? I will be placing some more info if necessary
Thanks in advance
Having issues with running sudo apt update and sudo apt upgrade commands. These commands fail with an error E: Failed to fetch ... 403 Forbidden [IP: w.x.y.z 80], where w.x.y.z is one of these security.ubuntu.com mirrors: 91.189.92.24, 91.189.91.81, 91.189.92.23, 91.189.92.22, 185.125.190.83, 185.125.190.81, 91.189.91.82, 185.125.190.82 or 91.189.91.83.
The corporate firewall has a restricted list of open outgoing ports, where port 80 (HTTP) is open for traffic.
The failed issues are all related to packages that have current CVE notices; the rest of the packages fetched from the Ubuntu archive mirrors succeed.
To us, it looks like the initial request on port 80 is succeeding in reaching a security.unbuntu.com mirror, yet failing to fetch the packages from security.unbuntu.com the mirror. We suspect the actual package fetch is using another port not on the corporate firewall allowed list.
We need the full list of ports that security.unbuntu.com mirrors are using for package delivery.
I have 50+ ubuntu servers in my estate, they vary from Azure to Built from ISO.
Since yesterday 16/04/2026 we have seen significant speed issues with the repos.
There have been no change request for firewall changes, we check with our suppliers as well. We have run speed checks on our networks and yet we cannot find anything wrong.
We have also fiddled with some of the hosts to see if tweaks to the apt config cold help.
I then attempted the same update on my ubuntu desktop personal laptop and got the exact same issues.
Is there down detector for ubuntu?
Why can I find even the slightest mention of a problem online?
This is what apt update look like? You can literally go have coffee while the headers download, and they are noteven downloaded when you get back.
Reading state information... Done
7 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/noble-updates/InRelease Connection failed [IP: 185.125.190.82 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/noble-security/InRelease Connection failed [IP: 91.189.92.22 80]
W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/noble-backports/restricted/dep11/Components-amd64.yml Connection failed [IP: 185.125.190.83 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Problem during installation.
Package download failed:
E: http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 libinput-bin amd64 1.25.0-1ubuntu3.4 is not (yet) available
(Cannot initiate the connection to ubuntu-mirror-3.ps5.canonical.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable)
Cannot initiate the connection to ubuntu-mirror-1.ps5.canonical.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable)
Cannot initiate the connection to ubuntu-mirror-2.ps5.canonical.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable)
Cannot initiate the connection to ubuntu-mirror-1.ps6.canonical.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable)
Cannot initiate the connection to ubuntu-mirror-3.ps6.canonical.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable)
Cannot initiate the connection to ubuntu-mirror-2.ps6.canonical.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable)
Could not connect to ubuntu-mirror-2.ps6.canonical.com:80 (91.189.91.82), connection timed out
Cannot initiate the connection to gb.archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable)
Cannot initiate the connection to gb.archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable)
Cannot initiate the connection to gb.archive.ubuntu.com:80 2620:2d:4000:1::103). - connect (101: Network is unreachable) \[IP: 91.189.91.82 80\])
E: http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 libinput10 amd64 1.25.0-1ubuntu3.4 is not (yet) available
(Cannot initiate the connection to gb.archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable)
Cannot initiate the connection to gb.archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable)
Cannot initiate the connection to gb.archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) \[IP: 91.189.91.82 80\])
I'm using Ubuntu 24.04 LTS, and everything was working fine until a recent system update.
After updating, I started noticing:
I already tried:
sudo apt update && sudo apt upgradetop...but the issue is still there.
Is this related to a recent kernel/update issue? How can I diagnose and fix this properly?
Are all the files and back ups I had on Ubuntu One cloud not retrievable, period?
I want to have a right hand mouse and a left hand mouse active at the same time in 24.04. I had used xinput on earlier versions but it does not look compatible with Xwayland server. I have loaded Input Remapper but I'm not understanding how to make the change. I get this far when changing one mouse to left hand but get stuck. How do I also change the left button? There is something basic I'm not understanding.
I think I have it now.
I'm going to publish a self-answer on how to properly fix the internal camera without breaking the audio stack.
In this guide I'll explain how to do it right because there are people out there that have suggested a solution either by the DKMS or by the development PPA from intel.
Both can work only under specific circumstances but will break sooner or later because do not take care of the root cause of the issue.
To give a bit of context Dell XPS 13 9315 with stock Ubuntu is at 20.04 LTS but during normal Ubuntu upgrades the camera breaks and upgrading to 22.04 did not fix it.
I don't have knowledge of this issue being addressed even in version 24.04 LTS. Moreover I don't recall a single Ubuntu upgrade issue-free in the last 10 years. So I can't recommend trying it to avoid following this procedure.
I have had many requests lately to install Ubuntu on older and newer laptops by our customers.
And although I really like it and use it myself on my personal laptop I have a hard time installing it for end users.
Normal procedure we pick the language, type of install, drivers to pick and username + password at start. But many users do forget it (password) or want to have different settings or languages by default.
Is there a way like it is on Windows where you install it and enter the key and then you shut down the PC, when the user starts the machine it goes further and the user defines all by himself the next steps including, language, username etc.
This is so useful for companies selling and repairing laptops, desktops etc.
Thank you in advance for your answers and wish you all a great day!
Matej
How can I change the rights to a volume to solve below described problem?
I am not able to create a new map on this below mentioned volume. I have tried to take ownership of the volume by using the command
sudo chown $piet:$piet -R /media/piet/44954a9f-4062-40da-ac60-9c09c9885e44
but that just resulted in
chown: changing the group of '/media/piet/44954a9f-4062-40da-ac60-9c09c9885e44': Input/output error
Trying to create a map in that drive results in following message:
Suspend/hibernate not working - no usable answers were provided, the only proposed solution does not work.
This is NOT a duplicate of "Computer does not resume from suspend". The computer does not sleep or suspend at all and answers in this thread are not relevant. The question I had asked before had no functional solutions.
This is NOT a duplicate of 24.04 doesn't sleep as that has an "answer" that I cannot downvote or delete as the "answer" doesn't work.
I have a brand new Lenovo ThinkBook 16 G8 IRL running Ubuntu 24.04.3. The computer has 32gb of RAM and 2 physical SSDs, one for a Win11 installation and the other for a fresh Ubuntu installation.
Sleep/Suspend works perfectly in the W11 environment, but not in Ubuntu. I have tested using Ubuntu versions 18 to 24, Mint Cinamonn 22 and Pop!_OS 22 and 24. They have all exhibited the same behavior.
The screen goes black, it looks like the machine tries to sleep, but then wakes up again within 5 seconds. This makes it impossible to use as a true laptop as I have to save all work and shut down the computer whenever I will travel with it - which is quite often.
This is not a problem of the computer not restarting or restoring from suspend, the computer does not enter suspend in the first place.
I agree the suspend command should work out of the box, so I'm not understanding this. I ran the below command and had the same effect - black screen for 3-5 seconds, then back to a login screen.
Swap is on and has plenty of space (32gb of RAM)
I have followed several recommendations and followed several directions.
There are no external devices plugged in
I have attempted to disable USB devices, use Gnome Tweaks to enable suspend, changed USB wake properties, but I had no luck.
Updates: Computer updated to 24.04.4 New dmesg added at the end Kernel updated to 6.17.0-20-generic
Latest dmesg:
[ 0.960269] kernel: Low-power S0 idle used by default for system suspend
[ 1.325652] kernel: sdhci: Secure Digital Host Controller Interface driver
[ 1.325655] kernel: sdhci: Copyright(c) Pierre Ossman
[ 1.329688] kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit
[ 1.330996] kernel: usb 3-6: new high-speed USB device number 2 using xhci_hcd
[ 1.335437] kernel: sdhci-pci 0000:45:00.0: SDHCI controller found [1217:8621] (rev 1)
[ 1.335535] kernel: sdhci-pci 0000:45:00.0: enabling device (0000 -> 0002)
[ 1.342077] kernel: mmc0: SDHCI controller on PCI [0000:45:00.0] using ADMA
[ 1.343738] kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
[ 1.343745] kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
[ 1.343826] kernel: nvme nvme1: pci function 0000:02:00.0
[ 1.343836] kernel: nvme nvme0: pci function 0000:01:00.0
[ 1.345158] kernel: intel-lpss 0000:00:15.3: enabling device (0000 -> 0002)
[ 1.346161] kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit
[ 1.364019] kernel: nvme nvme0: D3 entry latency set to 10 seconds
[ 1.374960] kernel: nvme nvme1: allocated 64 MiB host memory buffer (1 segment).
[ 1.378281] kernel: nvme nvme0: allocated 64 MiB host memory buffer (1 segment).
[ 1.387526] kernel: nvme nvme1: 12/0/0 default/read/poll queues
[ 1.391873] kernel: nvme1n1: p1 p2 p3 p4
[ 1.410882] kernel: nvme nvme0: 12/0/0 default/read/poll queues
[ 1.421148] kernel: nvme0n1: p1 p2
[ 1.495689] kernel: input: FTCS0038:00 2808:0106 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-FTCS0038:00/0018:2808:0106.0001/input/input4
[ 1.495877] kernel: input: FTCS0038:00 2808:0106 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-FTCS0038:00/0018:2808:0106.0001/input/input5
[ 2.422232] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[ 2.422343] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[ 2.422354] systemd[1]: Expecting device dev-disk-by\x2duuid-E27F\x2d1009.device - /dev/disk/by-uuid/E27F-1009...
[ 2.422367] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
[ 2.422382] systemd[1]: Reached target nss-user-lookup.target - User and Group Name Lookups.
[ 2.422389] systemd[1]: Reached target remote-fs.target - Remote File Systems.
[ 2.422395] systemd[1]: Reached target slices.target - Slice Units.
[ 2.422404] systemd[1]: Reached target snapd.mounts-pre.target - Mounting snaps.
[ 2.422418] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
[ 2.422508] systemd[1]: Listening on syslog.socket - Syslog Socket.
[ 2.422550] systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
[ 2.422578] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[ 2.422627] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[ 2.422675] systemd[1]: Listening on systemd-journald.socket - Journal Socket.
[ 2.422743] systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket.
The last entry is:
[ 2.422743] systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket.
I've had the RDSEED32 broken error come up for a while every time I boot. For a while I did not think anything of it since my system was performing normally, but I thought I would do a bit of research on it and what I found was a little bit concerning. From what I understood is that it affects the random generation of encryption keys, making them more predictable, I am assuming this includes encryption keys for everything, https traffic, password hashes, as well as local file encryption.
This did concern me, however a lot of the fixes suggest a BIOS update (the latest kernel update has not resolved it) I am a little anxious about doing a BIOS update when it has the potential to brick my motherboard (and I have never had the courage to run a BIOS update on any machine, even though I know I should).
I'm running Ubuntu 22.04 on a Ryzen 9 9900X3D and a Tomahawk B650 motherboard.
Is it something I should worry about?
Thanks
I installed Ubuntu 24.04 on my Asus Vivobook M1502YA (Ryzen 7 7000 series), but the Wi-Fi doesn’t work at all.
Details:
Wi-Fi chip: MediaTek MT7902 (lspci shows 01:00.0 Network controller: MEDIATEK Corp. Device 7902)
Kernel: 6.17.0-20-generic (uname -r)
What I tried:
Upgraded to latest kernel using Mainline
Installed linux-firmware
Ran sudo ubuntu-drivers autoinstall
Checked rfkill (no soft/hard block)
Output:
ip a
# shows only:
1: lo: <LOOPBACK,UP,LOWER_UP> ...
2: enx... (USB tethering interface)
# No wlan0 or wlp interface detected
Problem:
Wi-Fi interface is not detected. USB tethering works, so internet is fine.
Question:
Is MediaTek MT7902 supported on Ubuntu yet?
Any workarounds or experimental drivers to get it working?
Thanks in advance!
In Ubuntu, configuration of settings such as the following can be done via console as mentioned in this question, including:
With which GUI based open source software, can one perform ZFS configurations such as the above?
I am using Ubuntu Unity on a Lenovo Ideapad Flex 5 (14ARE05). When I go to the 'Brightness and Lock' settings there are only options to adjust lock, not the brightness. How do I fix this? I already tried the Fn keys, but they don't work.
Example:
Click image to enlarge it.
I don't know if it is related to this particular problem, but as background, I am experiencing other issues, like PrtSc key not working, wallpaper missing, etc. I did run echo "c" > /proc/sysrq-trigger as a joke to trigger a kernel panic. It seems to modify the PrtSc/SysEq behavior, possibly creating these issues?
I recently upgraded to 22.04LTS, and ever since the upgrade, my Dock-Icons have started to wiggle when there is an unread notification. Apparently, not all 22.04 users are experiencing this behavior, so I am unsure what could cause it. Does anyone have an idea how to stop this behaviour?
By default Ubuntu 21.10 (should be the same for 20.04) does generate temporary/privacy IPV6 addresses. I would like to disable this behavior in order to make my computer into a server, and to do so I would like to have an IPV6 address as stable as possible (notably to ease of process of configuring a DNS name without using DDNS, at least for the IPV6 address).
When looking at ip -6 address it looks like this:
inet6 2a02:a03f:a0bb:abcd:ea4b:d152:592e:74da/64 scope global temporary dynamic
valid_lft 83659sec preferred_lft 69259sec
inet6 2a02:a03f:a0bb:abcd:3c0d:e2ad:569e:2536/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 83659sec preferred_lft 69259sec
I want an autoconfigured permanent addresses like this (taken from a server in the same network, the address seem to have been generated using the modified EUI-64 algorithm):
inet6 2a02:a03f:a0bb:abcd:211:32ff:fe59:76be/64 scope global dynamic
valid_lft 64840sec preferred_lft 50440sec
Please note I don't want to configure a static IPV6address!
That's why I ask this question today. Most Google searchs about this issue ends in nonsensical advice explaining how to configure a static IPV6 address. It's not the same thing than a permanent autoconfigured address. To generate those the OS must listen for the router to get the first 64 bits of the address and the complete the remaining bits with its MAC address.
I've looked at many similar questions but unfortunately the solutions didn't work for me. I have recently installed Ubuntu 18.04 and my speakers are not working nor are they are detected in the settings, they are actually listed as not available after running pacmd command. They are working fine on windows so the problem must be related to the compatibility with the driver in ubuntu, but I suppose there must be some settings to fix it. here ill pastebin what I get from the sinks list:
1 sink(s) available.
* index: 0
name: <alsa_output.pci-0000_00_1f.3.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9039
volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 371.52 ms
card: 0 <alsa_card.pci-0000_00_1f.3>
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC255 Analog"
alsa.id = "ALC255 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xb4520000 irq 134"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1f.3"
sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "9d71"
device.product.name = "Sunrise Point-LP HD Audio"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC255"
alsa.components = "HDA:10ec0255,10251094,00100002 HDA:8086280b,80860101,00100000"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: yes)
properties:
device.icon_name = "audio-headphones"
active port: <analog-output-headphones>
It looks to me like the headphones and the speakers are in the same sink, although as you can see it gives the speaker as not available. Anyone knows how to handle it? I've tried out myself but I'm starting to give up... Here are the details about my sound card
$ lspci -v | grep -A7 -i "audio"
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 132
Memory at b4520000 (64-bit, non-prefetchable) [size=16K]
Memory at b4510000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
Even though I entered the right password to my machine I'm unable to login.
Issue
I start my machine and for the first time I'm able to login with my password.
Now I lock my machine or I suspend my laptop and try to login again. Then the Incorrect Password Issue appears.
Even though the password is correct I'm not able to login.
Temprorary Solution Whenever I switch the user and login with same user then I'm able to login or I restart the machine.
Has anybody, encountered this Issue? And are there any permanent solution?
OS: Ubuntu 16.04 LTS
Machine: Lenovo ideapad 300
I want to count the number of lines in a file using wc -l but only output the number, without the following space and filename.
Edit from comments: The filename may have numbers in it.
Currently if I do:
wc -l /path/to/file
On a file with 176 lines, the output is:
176 /path/to/file
This is within a bash script, and the resulting number will be assigned as the value of a variable.
I've been using Arch Linux with a patched kernel on my Surface Pro 3.
I switched to Ubuntu now and want to use the kernel that includes all the patches from Arch with Ubuntu. What is the best way to add the kernel? Can I simply copy the vmlinuz and initramfs and update-grub?
I copied the files and updated grub, which worked fine, but when I boot the new kernel I get a kernel panic: Unable to mount root root fs on unknown-block(0,0).
[ 0.515662] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.515760] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.0.1-1-surfacepro3 #1
[ 0.515839] Hardware name: Microsoft Corporation Surface Pro 3/Surface Pro 3, BIOS 3.11.0760 03/16/2015
[ 0.515940] 0000000000000000 00000000069595c28 ffff88024620bdb8 ffffffff8156818a
[ 0.516041] 0000000000000000 ffffffff81707070 ffff88024620be38 ffffffff81567357
[ 0.516141] ffff880200000010 ffff88024620be48 ffff88024620bde8 00000000069595c28
[ 0.516240] Call Trace:
[ 0.516279] [<ffffffff8156818a>] dump_stack+0x4c/0x6e
[ 0.516340] [<ffffffff81567357>] panic+0xd0/0x204
[ 0.516401] [<ffffffff818f85cf>] mount_block_root+0x296/0x2a5
[ 0.516469] [<ffffffff818f8632>] mount_root+0x54/0x58
[ 0.516530] [<ffffffff818f876e>] prepare_namespace+0x138/0x171
[ 0.516599] [<ffffffff818f8246>] kernel_init_freeable+0x1f6/0x21f
[ 0.516672] [<ffffffff8155ea30>] ? rest_init+0x90/0x90
[ 0.516733] [<ffffffff8155ea3e>] kernel_init+0xe/0xf0
[ 0.516795] [<ffffffff8156d898>] ret_from_fork+0x58/0x90
[ 0.516859] [<ffffffff8155ea30>] ? rest_init+0x90/0x90
[ 0.516969] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
[ 0.517078] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
_
The kernel here was provided precompiled with with /usr and /lib as a .tar.gz archive. The kernel package I used does not provide that. It just contains the patches, so I can't just copy /usr and /lib from the archive.
I could copy them from my arch distribution running this kernel, but what specific directories would I have to copy, the whole /usr and /lib?
I just received an e-mail from Canonical warning me that the Ubuntu One service is going to shutdown. Is this real? Has anyone else got the same e-mail? Why is this happening?
Any information would be appreciated :S
Email:
Hi,
We are writing to you to notify you that we will be shutting down the Ubuntu One file services, effective 1 June 2014. This email gives information about the closure and what you should expect during the shutdown process.
As of today, it will no longer be possible to purchase storage or music from the Ubuntu One store. The Ubuntu One file services apps in the Ubuntu, Google, and Apple stores will be updated appropriately.
As always, your content belongs to you. You can simply download your files onto your PC or an external hard drive. While the service will stop as of 1 June, you will have an additional two months (until 31 July 2014) to collect all of your content. After that date, all remaining content will be deleted.
If you have an active annual subscription, the unused portion of your fees will be refunded. The refund amount will be calculated from today's announcement.
We know you have come to rely on Ubuntu One, and we apologise for the inconvenience this closure may cause. We've always been inspired by the support, feedback and enthusiasm of our users and want to thank you for the support you've shown for Ubuntu One. We hope that you'll continue to support us as together we bring a revolutionary experience to new devices.
The Ubuntu One team
I have looked at similar questions:
However, neither one of them answer my problem.
I am running 12.04 AMD64 and have recently started getting an issue that when I update my repos from my connection at home through a terminal, using sudo apt-get update, it takes forever (literally after 2 hours it was at 28%), however when I run from a different location it takes less than 5 minutes to complete.
I have attempted changing which mirror I use, but that does not solve the issue. I have also cut down what is in my sources list, but this also makes no difference. There are no faults on my ADSL line, as I have already contacted my ISP to check this. It also makes no difference if I use a WiFi or network cable connection.
What could be my issue?
A speed test (www.speedtest.net) comes out at about 0.9 Mbps down and 0.42 Mbps up (which is a shade under the advertised line speed), I reside in South Africa and use the UCT LEG server. But I have also tried the other mirrors available in SA....none of them make a difference.
I'm following the upgrade instructions on Ubuntu's website, but on launching the upgrade tool I get this response:
Checking for a new ubuntu release
No new release found
Am I doing something wrong? Is there a workaround?
I have recently bought a new faster server and so I want to start migrating things over to the new server. Having my email server (Zimbra) installed in a virtual machine, I figured it should be a piece of cake, just move the .vdi, configure the new VM and enjoy the improved performance. Unfortunately I get a kernel panic on the new box when trying to boot:
3f44 c049f400
[ 5.682942] c044d395 c1fb2400 c021f782 00000001 00000000 00000000 0000
0000 00000000
[ 5.683686] Call Trace:
[ 5.683851] [<c044d975>] setup_boot_APIC_clock+0x235/0x560
[ 5.684095] [<c044d395>] APIC_init_uniprocessor+0xf5/0x160
[ 5.684338] [<c021f782>] __next_cpu+0x12/0x30
[ 5.684553] [<c044bd9f>] native_smp_prepare_cpus+0x3af/0x5b0
[ 5.684801] [<c012cb05>] set_cpus_allowed+0x45/0xa0
[ 5.685030] [<c0440450>] kernel_init+0x0/0x320
[ 5.685506] [<c04404a2>] kernel_init+0x52/0x320
[ 5.685908] [<c012e147>] schedule_tail+0x17/0x60
[ 5.686308] [<c01082be>] ret_from_fork+0x6/0x1c
[ 5.686707] [<c0440450>] kernel_init+0x0/0x320
[ 5.687103] [<c0440450>] kernel_init+0x0/0x320
[ 5.687499] [<c0108ffb>] kernel_thread_helper+0x7/0x10
[ 5.687920] =======================
[ 5.688237] Code: 04 8b 42 14 8b 72 10 89 c1 31 c0 0f a5 fd d3 e7 f6 c1 20 0f
45 ef 0f 45 f8 89 f8 89 ea 89 d1 31 d2 85 c9 89 c3 74 08 89 c8 31 d2 <f7> f6 89
c1 89 d8 f7 f6 89 ca 83 fa 00 89 c1 76 1f b8 ff ff ff ff
[ 5.692816] EIP: [<c014e350>] clockevent_delta2ns+0x40/0xa0 SS:ESP 0068:f7c53ed8
[ 5.693520] ---[ end trace ca143223eefdc828 ]---
[ 5.693865] Kernel panic - not syncing: Attempted to kill init!
_
Do you have any ideas on what could be causing this? Could it be related to new host being 64-bit?
Some info on server1 (working):
Virtualbox version: 3.2.12r68302
uname -a: `Linux server1 2.6.32-34-generic-pae #77-Ubuntu SMP Tue Sep 13 21:16:18 UTC 2011 i686 GNU/Linux`
Some info on server2 (Not working):
VirtualBox version: 4.1.6r74727
$ uname -a: Linux server2 2.6.32-33-server #72-Ubuntu SMP Fri Jul 29 21:21:55 UTC 2011 x86_64 GNU/Linux