The Windows 11 SATA drive kept trying to boot first despite my attempts at changing the boot sequence in the BIOS as well as a few other fixes that failed until I just decided to wipe them both and create all new partitions with Ubuntu Studio installed on the NVMe drive and use the other SATA drive to partition as ext4 for storage use for Ubuntu and just chuck Windows altogether for now at least. This took some doing, but I had AI assisting (Claude). Although we did manage to get things running the start-up was still having to press F12, then F2 and scroll to UEFI options and choose the NVMe option to boot Ubuntu.

Today upon powering on I got the message "no drive found to boot from" or similar. So I rebooted, pressed F12 and don't know why there is now "Ubuntu" as well as "NVMe" options under UEFI BOOT, as the NVMe is the Ubuntu drive. And I no longer see the other hard drive, maybe due to taking it off legacy in BIOS boot options after checking the "clear" box in the Security section of the BIOS window as advised to do.

I'm trying to get my Ubuntu Studio running normally or not having to deal with starting it up and getting something other than the Ubuntu studio windows. The other AI has been assisting for 3 days now, so I thought I'd get a fresh perspective on things. Can you help me?

Maybe I just need to remove the hardware I added (the SATA SSD?). I don't know. I originally would have liked to have a dual boot with Windows 10 on the SATA SSD and tried settling for just Ubuntu at least functioning consistently.

I am using a fresh install of Kubuntu 25.10. But after booting, I get a black screen. Then, I can press Ctrl+Alt+F3 to get a console. After logging in, I execute

startplasma-wayland

and the Desktop loads...
But without this manual procedure nothing happens and the screen stays black.

So my question is:
What breaks the automatism and how can I fix it?
And has it anything to do with the NVidia drivers (I'm using nvidia-driver-580-open)?

10th December update broke Chrome & Brave. Makes me log-in with log-in ring password (it didn't before) & all of my bookmarks have vanished. I'm logged out of everything. Firefox is working fine. Will this be fixed soon? I'm running Ubuntu LTS (24.04 LTS). Brave & Chrome were running fine until the update.

I followed the manual for building ubuntu-image classic

https://canonical-subiquity.readthedocs-hosted.com/en/latest/howto/ubuntu-image-classic-examples.html

and I got an error:

Error: Error running command "/usr/sbin/chroot img/scratch/loopback grub-install /dev/loop3 --boot-directory=/boot --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot --no-nvram". Error: exit status 1. Output:

grub-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.

I have installed Xubuntu v25.10 on a old Chromebook.

It seems to be working fine however if I open the App Center app there is screen tearing happening.

It flickers between normal and scrambled.

I have no problems with other apps I have tried. I have used Xfce Terminal, Firefox and LibreOffice Writer so far.

If I run lspci -k | grep -EA3 'VGA|3D|Display' I get the following:

00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)

   DeviceName: VGA compatible controller
   Subsystem: Intel Corporation Device 7270
   Kernel driver in use: i915
   Kernel modules: i915

I am not a Linux user so I don't know where to start to fix the problem.

Apologies in advance for poor formatting. I have to do this on my phone because I'm locked out on my laptop & it's infuriating.

I installed a few apps (GIMP, Inkscape, Krita, Gnome Tweaks) then my laptop locked from idle time while I was waiting for a few updates. When I went to log in again it gave me "Authentication Error" when just clicking on the password entry box. I attempted to restart to fix the issue (There was no option to do a normal shut down so I suppose this would be considered an unclean shutdown) & this is what I was left with

I've tried running the command sudo systemctl start graphical.target to no avail, it simply moves me to another line as if to enter another command

Why am I stuck on this screen? It's like a full screen terminal & nothing else is showing. I've tried everything I can think of & it keeps saying it's wrong.

Do I need to reinstall Ubuntu? What is the problem?

I installed the RRClone client in Ubuntu 25.04 and it went well, but then it prompted me to grant OneDrive access.

I then created a OneDrive folder in my home directory.

Now I run rclone --vfs-cache-mode writes mount onedrive: ~/OneDrive and get the following error message: CRITICAL: Failed to create file system for "onedrive:": didn't find section in config file ("onedrive")

I can't mount the OneDrive folder.

I would like to know how to have pictures/photos fit the window when using them as wallpaper - it doesn't seem to matter the size or type of either - most of them posted far larger than the window size - is there any way to fix that? TIA

A few days ago I had to force my computer to shut down by holding the power button because I had a blank (dark) screen and could not get the machine to display anything. I had earlier tried to go to the login screen by "changing user". Although there is no other user registered I thought it would default to the login screen.

Since forced shutdown I cannot login. The machine boots to a login screen that is different to the normal one, and I can enter my password, but nothing happens when I press Enter.

I have booted to recovery mode and tried the various tools on the menu: dpkg, fsck, grub, root (drop to root shell prompt), System summary. None of them have solved the problem.

I have also tried (all the following commands (with sudo):

systemctrl restart sddm
startx
apt update, apt install --reinstall sddm plasma, dpkg -reconfigure sddm, reboot*
{checked logs} journalctl -b -p err --no-pager, systemctl status sddm
cat /home/(userfolder)/.xsession-errors 2>/dev/null || true
{checked disk space} df -h /

From what I can see the problem is not sddm (simple desktop display manager), even though that has replaced the previous Plasma display manager. The problem is something to do with LVM (Logical Volume Management). Something about the disk/volume management has been corrupted or deleted.

In System Summary everything else reports ok except this:
"=== LVM state===
Physical Volumes: not ok (BAD)
Volume Groups: ok (good)"
Note: while volume groups reports good, when I run vgdisplay, vgscan or lvdisplay they return no information, I think because they do not identify any volumes or volume groups.

When I run pvscan it returns No matching physical volumes found, yet when I run fdisk -l it returns information on all the storage devices and their partitions, and I can navigate through directories and look at their contents.

One other oddity: fdisk -l returns this comment in red Partition 1 does not start on physical sector boundary. after the listing for a hard disk I use only for data.

If anyone has any idea how to solve this problem I would be very grateful. BTW I will be away for a few days and unable to reply to any posts until next Monday.

Edit: Regarding space, the disk is almost empty. About 17% used. And I am running an up to date kubuntu installation that I only reinstalled a few weeks ago using an ISO labelled "kubuntu-24.04.2-desktop-amd64.iso".

I am having trouble with generic US keyboards in Ubuntu Studio 25.10 (questing) using Konsole in Plasma on Wayland. I have updated my packages today using apt.

The uppercase and lowercase letters often are the wrong case, despite what the caps-lock indicator shows. The Shift key does not seem to be coordinated with my typing. It frequently does not seem to update the status of the shift key when I type fast.

The plus sign on the keypad has been remapped to an equal sign. Pressing Shift on the main keyboard and plus on the keypad sends a plus sign, although the keyboards have a plus sign painted on them.

I tried System Settings > Keyboard to change the Model to "Logitech | Logitech", since that is the closest match to my external keyboard. I also tried reset to "Defaults" in "Keyboard - System Settings".

Under Accessibility, I only have "Audible Bell" and "Shake cursor to find it" enabled.

Problem persists.

I am creating a script for my Java Library to run. However fdisk (when resizing my partition) constantly throws an error.

Here's the script: https://gist.github.com/RishonDev/2affcd0002b970855a222b5e9fdf4a41

The --addPartition is where it goes wrong. Rest of the stuff works fine. What may be the cause? The command I used is listed below (pass is the password of the admin account of that linux system.)

PASSWORD="pass" ./format2.sh --addPartition /dev/sda 100MiB fat32 EFI

Here's the output of part sudo parted -m -s /dev/sda unit MiB print free

BYT;
/dev/sda:14939MiB:scsi:512:512:gpt:SanDisk Cruzer Blade:;
1:0.02MiB:1.00MiB:0.98MiB:free;
1:1.00MiB:14938MiB:14937MiB::primary:msftdata;
1:14938MiB:14939MiB:0.98MiB:free;

lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0     4K  1 loop /snap/bare/5
loop1    7:1    0  68.9M  1 loop /snap/core22/2140
loop2    7:2    0 250.2M  1 loop /snap/firefox/7473
loop3    7:3    0 232.8M  1 loop /snap/firefox/7182
loop4    7:4    0  61.9M  1 loop /snap/core24/1226
loop5    7:5    0  22.8M  1 loop /snap/desktop-security-center/100
loop6    7:6    0  68.9M  1 loop /snap/core22/2164
loop7    7:7    0 493.6M  1 loop /snap/gnome-42-2204/228
loop8    7:8    0   614M  1 loop /snap/gnome-46-2404/147
loop9    7:9    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop10   7:10   0 174.6M  1 loop /snap/mesa-2404/1166
loop11   7:11   0  13.1M  1 loop /snap/prompting-client/105
loop12   7:12   0    10M  1 loop /snap/snap-store/1271
loop13   7:13   0  44.3M  1 loop /snap/snapd/25585
loop14   7:14   0   560K  1 loop /snap/snapd-desktop-integration/338
loop15   7:15   0   552K  1 loop /snap/snapd-desktop-integration/316
loop16   7:16   0 218.5M  1 loop /snap/thunderbird/850
sda      8:0    1  14.6G  0 disk 
└─sda1   8:1    1  14.6G  0 part 
sr0     11:0    1  1024M  0 rom  
vda    253:0    0    64G  0 disk 
├─vda1 253:1    0     1G  0 part 
└─vda2 253:2    0  62.9G  0 part /

The files copy normally on nautilus and the filesystem is ext4. The current version of Ubuntu is 25.10 and it's on a virtual machine (Using UTM for macOS). Feel free to ask for more details.

I just bought a new Asus ROG Strix Scar 18 (2025) laptop with Windows 11 installed. When I am loading from an Ubuntu USB stick (I tried both Ubuntu 22.04 and 24.04), the system does not detect the SSD at all. When browsing with Google, I saw that the RAID mode of SSD can be an issue, however when I disable VMD mode in the BIOS, the SSD disappears even from BIOS boot options.

My installation of Ubuntu 24.04.3 LTS halts at this text:

Dec 10 19:16:26 ubuntu subiquity_log.4243[7584]: 
rsync: [sender] read errors mapping "/tmp/tmpmuay3ljg/mount/var/lib/snapd/seed/snaps/thunderbird_769.snap": 
Input/output error (5)

This is my second attempt, and it just sits at this part.

Ubuntu 24.04.3 LTS https://ubuntu.com/download/desktop?version=24.04&architecture=amd64&lts=true

I simply downloaded the image and loaded it onto a flash drive using another Ubuntu computer. I tested Ubuntu 24 LTS: images text browser. But then [2-3 days later] these catastrophic failures started.

You forbade attaching screenshots. So here are the links from the image hosting.

https://postimg.cc/JDfS1N6W https://postimg.cc/N93Zg6Jv https://postimg.cc/dkkzPHBV https://postimg.cc/DWmNLjRL

I want to experience Ubuntu outside of a virtual machine, and I want to install Ubuntu on my laptop. There are two problems though. First, I don't have a spare USB or something like that. Second, I have a big fear of BIOS-related menus meaning I don't want to access Novo menu, BIOS setup or boot menu. My Lenovo laptop didn't came with Intel RST or Bitlocker meaning I'm prepared for install. Any comment saying "go buy a USB/enter boot menu" will be ignored as they bring no beneficial value to my problem.

I have the installation partition prepared on my secondary 1Tb drive and Ubuntu version is 24.04.

I bought a USB and I'm ready to boot it from Windows Recovery.

In October, I migrated from Win 10 to Ubuntu, rather than suffer Win 11. It has been going well, but I am getting this problem when Ubuntu Discover tries to do a "firmware update":

Ubuntu Discover update "failed to write-firmware: failed to write (null): failed to write data to efivarsfs: Error writing to file descriptor: Invalid argument"

Even more irritating, I dismiss the error message and it pops right back. The Discover updater captures the cursor too quickly to close the program, leaving me stuck. The cursor/mouse is captured by Discover, leaving me unable to do anything other than close the error message box, which pops right back endlessly.

The first time this happened, I tried the reset button on the PC, but that had the bad side effect of leaving a couple drives with "missing mount points", which I had to remove from the PC and put in my old Win 10 pc and run partition manager to scan them for errors, then back in to my main PC and all was happy again. Yes, I know there is a way to do this in Ubuntu, but I felt too newbie to try it and risk losing important data. And yes, I do have a back up, but some recent things might have been lost.

The second time this happened, just this morning, I was able to click on the Discover icon on the left of the Task Manager bar and manage to quit Discover after several tries. A quick right click on the icon and then a typed Q to quit, if done quickly enough was able to do the job.

Thank you for any help

The stuff everyone will ask:

• Operating System: Ubuntu Studio 25.10
• KDE Plasma Version: 6.4.5
• KDE Frameworks Version: 6.17.0
• Qt Version: 6.9.2
• Kernel Version: 6.17.0-7-generic (64-bit)
• Graphics Platform: Wayland
• Processors: 16 × Intel® Core™ i7-6900K CPU @ 3.20GHz (overclocked -to 4.2GHz)
• Memory: 128 GiB of RAM (125.7 GiB usable)
• Graphics Processor: NVIDIA GeForce GTX 1070 Ti driving 3 monitors
• Manufacturer: ASUS
• Product Name: All Series
• Motherboard - Asus X99-A II

sudo dmidecode -t 0
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: 1401
        Release Date: 11/08/2016
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 16 MB
Characteristics:
                PCI is supported
                APM is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                ...
                BIOS boot specification is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 5.11

        

fwupdmgr update -v
(fwupdmgr:428045): GLib-GIO-DEBUG: 07:13:34.760: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
....
appears to be installed


╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade KEK CA from 2011 to 2023?                                            ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This updates the UEFI Signature Database (the "KEK") to the latest release   ║
║ from Microsoft, signed by ASUSTeK MotherBoard PK Certificate.                ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: Y
(fwupdmgr:428045): FuMain-DEBUG: 07:14:48.251: ignoring: No releases found
(fwupdmgr:428045): FuMain-DEBUG: 07:14:48.251: ignoring: No releases found
(fwupdmgr:428045): FuMain-DEBUG: 07:14:48.252: ignoring: No releases found
(fwupdmgr:428045): FuMain-DEBUG: 07:14:48.252: ignoring: No releases found
(fwupdmgr:428045): FuMain-DEBUG: 07:14:48.263: ignoring: No releases found
Fwupd-INFO: 07:14:48.263: downloading https://fwupd.org/downloads/73ea2c69621eec29df454264907a2d3586d57ab2e58b7ff596d013bc37ca1714-KEK-ASUS.cab
(fwupdmgr:428045): pxbackend-DEBUG: 07:14:48.264: px_manager_get_proxies_sync: url=https://fwupd.org/downloads/73ea2c69621eec29df454264907a2d3586d57ab2e58b7ff596d013bc37ca1714-KEK-ASUS.cab online=1
(fwupdmgr:428045): pxbackend-DEBUG: 07:14:48.264: px_manager_get_proxies_sync: Proxy[0] = direct://
(fwupdmgr:428045): pxbackend-DEBUG: 07:14:48.264: px_manager_get_proxies_sync: url=none://fwupd.org:65535 online=1
(fwupdmgr:428045): pxbackend-DEBUG: 07:14:48.264: px_manager_get_proxies_sync: Proxy[0] = direct://
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.334: Emitting ::status-changed() [downloading]
Downloading…             [          |                            ]Fwupd-INFO: 07:14:48.517: download progress: 100%
Downloading…             [***************************************]Fwupd-INFO: 07:14:48.755: download progress: 9%
Downloading…             [***                                    ]Fwupd-INFO: 07:14:48.755: download progress: 15%
Downloading…             [*****                                  
...
Downloading…             [************************************   ]Fwupd-INFO: 07:14:48.761: download progress: 100%
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.761: Emitting ::status-changed() [idle]
Fwupd-INFO: 07:14:48.761: status-code was 200
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.764: Emitting ::status-changed() [decompressing]
Decompressing…           [***************************************](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.894: Emitting ::status-changed() [waiting-for-auth]
Authenticating…          [ -                                     ](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.927: Emitting ::status-changed() [device-busy]
Waiting…                 [ -                                     ](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.927: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.927: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.935: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.935: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.935: Emitting ::status-changed() [device-write]
Writing…                 [                                       ](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.936: Emitting ::status-changed() [decompressing]
Decompressing…           [                                       ](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.936: Emitting ::status-changed() [device-restart]
Restarting device…       [******************************         ](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.936: Emitting ::status-changed() [device-write]
Writing…                 [******************************         ](fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.936: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.936: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.954: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.954: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.962: Emitting ::device-changed(b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7)
(fwupdmgr:428045): Fwupd-DEBUG: 07:14:48.963: Emitting ::status-changed() [idle]

failed to write-firmware: failed to write (null): failed to write data to efivarsfs: Error writing to file descriptor: Invalid argument

I am on Ubuntu 24.04.2 LTS running on an HP ZBook 15 G2. My problem is that when I attach my computer to a USB docking station and plug headphones into the dock's aux port, they are not detected; i.e. they do not show up as an option in the "Output Device" dropdown of the sound menu in Settings, only the laptop's internal speakers show up. The headphones work and when I plug them directly into the laptop's aux port, they show up as Headphones - Built-in Audio in the dropdown and I can play audio through them. When I was running Windows on this computer, the dock fully worked, including the aux port. After switching to Ubuntu, it seems that the aux port and USB ports on the dock do not work, which leads me to believe that it may be some missing USB driver. The rest of the dock works fine (monitors, Ethernet, charging).

Info:

/proc/asound/version:

Advanced Linux Sound Architecture Driver Version k6.11.0-28-generic.

/proc/asound/cards:

 0 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xce830000 irq 38
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xce000000 irq 17

/proc/asound/devices:

  1:        : sequencer
  2: [ 1- 3]: digital audio playback
  3: [ 1- 7]: digital audio playback
  4: [ 1- 8]: digital audio playback
  5: [ 1- 9]: digital audio playback
  6: [ 1- 0]: hardware dependent
  7: [ 1]   : control
  8: [ 0- 0]: digital audio playback
  9: [ 0- 0]: digital audio capture
 10: [ 0- 0]: hardware dependent
 11: [ 0]   : control
 33:        : timer

Alsamixer indicates that I'm using PipeWire for the card and chip. I also installed PulseAudio Volume Control and it also doesn't detect headphones in the dock (Headphones: Unplugged). Oddly enough, it does detect the speakers of an external monitor connected to the dock as GK 106 HDMI Audio Controller Digital Stereo (HDMI).

I'm trying to upgrade from Bionic 18.04.6 LTS, but I am running into problems. I've looked at

EOL Upgrade Ubuntu 18.04.6 LTS (Bionic Beaver)

https://help.ubuntu.com/community/FocalUpgrades

Uprading Ubuntu 18.04.6 LTS to 20.04

Here's what I get.

$ sudo do-release-upgrade -c
Checking for a new Ubuntu release
New release '20.04.6 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

$ sudo do-release-upgrade
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

This is interesting because the Kubuntu Software Center (Discover) says my system is up to date.

$ sudo apt update
Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease                                 
Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease                          
Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease                         
Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease                       
Hit:1 https://packages.microsoft.com/repos/code stable InRelease                           
Get:6 https://download.docker.com/linux/ubuntu bionic InRelease [64.4 kB]                  
Hit:7 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security InRelease                    
Hit:8 https://esm.ubuntu.com/apps/ubuntu bionic-apps-updates InRelease
Hit:9 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security InRelease
Hit:10 https://esm.ubuntu.com/infra/ubuntu bionic-infra-updates InRelease
Fetched 64.4 kB in 2s (42.4 kB/s)                  
Reading package lists... Done
Building dependency tree       
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.

No updates are reported. Next I try the full upgrade.

$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Next I try update-manager. A window says

The software on this computer is up to date.
However, Kubuntu 20.04.6 LTS is now available (you have 18.04).

I click to upgrade, and it says

Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

apt-mark showhold shows no held packages.

At this point, I'm stumped, and it seems like I'm going in circles. Can anyone help?

UPDATE

Thank you, @guiverc. I didn't look at the upgradable package because I thought I should only consider updates, not upgrades. Here's the output:

$ apt list --upgradable
Listing... Done
code/stable 1.96.2-1734607745 amd64 [upgradable from: 1.83.1-1696982868]
N: There are 129 additional versions. Please use the '-a' switch to see them.

I tried to upgrade the package identified, but I got an error that I don't really understand.

$ sudo apt upgrade code/stable 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Selected version '1.96.2-1734607745' (code stable:stable [amd64]) for 'code'
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 code : Depends: libc6 (>= 2.28) but 2.27-3ubuntu1.6+esm3 is to be installed
        Depends: libxkbfile1 (>= 1:1.1.0) but 1:1.0.9-2 is to be installed
E: Broken packages

@guiverc - I checked the sources in update-manager and both Canonical-supported (main) and Community-maintained (universe) boxes are checked.

SUCCESS!

@guiverc - Thank you so much! That is indeed the problem. I did

$ sudo apt remove code/stable

Then the upgrade worked!

I just started encountering this issue where seemingly if I do anything too intense, my screen stops updating. Audio persists, and I can still alt tab and that switches between apps fine. So it’s seems like the computer is still totally functioning, except I just can’t see anything move. Not even mouse.

I only recently had this start happening. I tried Sudoku which worked for a good 40 minutes, and if I set my display scale to 1920-1080 seems like I could play Getting Over It with Bennett Foddy for longer than I could otherwise, but this issue just occurred right after I set it back to 4k. So I suspect it might have something to do with display?

For some background, my computer is an HP Spectre x360 15t Convertible with Windows as the main partition. I also have mainly used linux to experiment with LibTAS, and I was recently trying to test different versions and used a purge command to try and make sure nothing lingered from another version. I suspect that command might have done something but I am not familiar with Linux enough to know certainly.

I have 22.04 Jellyfish. I installed it with Rufus a couple years ago. My screen just freezes, not flashes or any of that nonsense.

I'm facing some troubles in the first configuration for ultrawide monitor. My laptop is a dell vostro 3501, core i5-1035G1 and monitor is a LG Ultrawide 25.7, model 26WQ500-B, 2560x1080, 75Hz

To create a modeline with the monitor's setup, I ran this command:

cvt 2560 1080 75

which displayed this:

2560x1080 74.94 Hz (CVT) hsync: 84.68 kHz; pclk: 294.00 MHz
Modeline "2560x1080_75.00"  294.00  2560 2744 3016 3472  1080 1083 1093 1130 -hsync +vsync

I ran the next command to create a new modeline using xrandr:

xrandr --newmode "2560x1080_75.00"  294.00  2560 2744 3016 3472  1080 1083 1093 1130 -hsync +vsync

I added this modeline to the LG Monitor HDMI output, described as XWAYLAND0 (xrandr):

xrandr --addmode XWAYLAND0 "2560x1080_75.00"

And finally, set the default output for XWAYLAND0 (HDMI port):

xrandr --output XWAYLAND0 --mode "2560x1080_75.00"

and it didn't work! A message was displayed further:

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  139 (RANDR)
  Minor opcode of failed request:  21 (RRSetCrtcConfig)
  Value in failed request:  0x556
  Serial number of failed request:  29
  Current serial number in output stream:  29

I really don't understand what's going on. I use the same LG Monitor in a core i5 8º generation laptop, with Ubuntu 20.04 LTS installed and it works perfectly, the 2560x1080 resolution. Just like I checked other discussions about Wayland and Xrandr compatibility or CVT can't gives the right parameters for modeline, maybe a customized modeline could work. I'd really aprecciate some help. Thank you, guys

on the Ubuntu 18.04 system I have cloned a project and to run it needs gradle but at running the gradle command gradle swiplRun I get the following error

Task :dockerRun FAILED docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/create?name=swiprolog: dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'.

Task :dockerRunStatus FAILED Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/swiprolog/json: dial unix /var/run/docker.sock: connect: permission denied

FAILURE: Build completed with 2 failures.

to solve I tried

$ sudo groupadd docker
$ sudo usermod -a -G docker myname  
"and once with"
$ sudo gpasswd -a myname docker

so I can run docker commands without sudo, but the same error also ./gradlew --stop and logout/login and reboot did not work too.

is it because of Docker or Gradle?

How can i made apache2 service active? when i tried to start apache2 service it gives me this error.apache2.service is not active, cannot reload.help me on this.on my localhost/phpmyadmin 403 Forbidden nginx/1.10.3 (Ubuntu)

How to configure samba on Ubuntu 18.04

I installed Samba from Ubuntu Software and its not launching and I also installed gksu after uninstalling samba and reinstalled it

I have problems with the iwlwifi network driver, and I want to try upgrading it to the newest available version. On AskUbuntu, I found a suggestion to download a driver from https://wireless.wiki.kernel.org. I found a page there for the iwlwifi driver, at:

https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi?s[]=iwlwifi

My adapter is an Intel Wireless 3160. The "Firmware" section on the kernel.org page has multiple entries for the 3160 card for different kernels, e.g.:

• 3.10+ → iwlwifi-3160-ucode-22.1.7.0.tgz
• ...
• 4.1+ → iwlwifi-3160-ucode-25.30.13.0.tgz
• 4.3+ → iwlwifi-3160-ucode-16.242414.0.tgz

I'm on Ubuntu 16.04 LTS, checking the kernel version:

$ uname -a
Linux akavel-lenovo 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

My kernel is 4.4 — so, which one of the above drivers should I choose? My first thought was to use the 4.3+ — but then I noticed the driver version is apparently 16.x, while 4.1+ has 25.x — so can I use the 4.1+? Is the driver really newer, or the ucode numbers mean something else? Or do I have to use the 4.3+? Or something else? I'm confused :( Or should I maybe just compile a driver on my own? If yes, then how? To add the confusion, the page also has a section like below (emphasis mine):

7260, 3160, 7265, 7265D, 3165 and 3168 support

Those devices will not be supported by the newest firmware versions: the last firmware that was released for 3160, 7260 and 7265 is -17.ucode. Bug fixes will be ported to -17.ucode.

Looking into the linux-firmware.git repository mentioned somewhere else on the page indeed seems to show an iwlwifi-3160-17.ucode as the one with the highest number. But when I downloaded the iwlwifi-3160-ucode-16.242414.0.tgz, it only has a iwlwifi-3160-16.ucode inside...

To summarize: the "Firmware" section on the wireless.wiki.kernel.org website is confusing to me, I don't really know which version should I download?

edit 1: Hm; after downloading the iwlwifi-3160-ucode-25.30.13.0.tgz and looking into it, it has an iwlwifi-3160-13.ucode file inside, so at least it seems to clear part of the confusion, in that the internal ordering follows the kernel version ordering, and I should probably just ignore the weird versioning in the tgz names. Still not sure what is it about the ucode-17 mentioned as the "newest version" but not being present in the newest tarball.

Online I find that there used to be a sticky edges toggle in the Displays settings window, but I can't find it there.

Was the feature dropped? Was the toggle moved?

As the tag says: I'm on Kubuntu, not vanilla Ubuntu.

I just purchased a network adapter which according to the driver CD is a RT2870 (It isn't written on the adapter). I've installed other things using commands before but the instructions on the readme file that came with it are quite confusing.

Has anybody made this network adapter work successfully in Ubuntu? I'd really appreciate some simple step by step instructions of how to make this work.

While installing: sudo apt-get install python-gnomedesktop python-rsvg ipython

I receive the error: E: Unable to locate package python-gnomedesktop

I run on one problem. My USB Bluetooth dongle ASUS USB-BT400 is not working. I'm googling the whole day for some clues, but without success. Could you please help me?

USB device is properly found:

lsusb:
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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 008: ID 0b05:17cb ASUSTek Computer, Inc. 
Bus 001 Device 007: ID 17ef:4816 Lenovo

But when I try to hciconfig, I don't get any output.

I tried it with some old BT dongle, and that worked... But I need to use especially this one because of BT4.0 support.

According to this: http://lists.freebsd.org/pipermail/freebsd-bugs/2013-September/053719.html It uses BCM20702A chipset, which should work under Linux, but maybe it's not properly recognized with this device? (Same issue, which is described in the linked site)

I will appreciate any help.

"Continue running background apps" is checked. There is no Chrome entry in Startup applications. This command didn't work:

google-chrome --no-startup-window

Everybody is complaining how to disable chrome running in background and I can't enable it. Am I missing something?

Forgot to add that I am using Ubuntu 12.10 and Chrome 22.

I see this error briefly at the top of a full screen console-type text screen as the computer restarts from suspend. At the start of the message is something about ATA, so I think it's to do with a hard disk restarting and something failing.

Should I worry? Everything seems to be working.

Edit: Smart status on the 2 disk drives is green, although one has a few bad sectors. I will watch it more closely.