Recently my system (24.04) suggests the update Microsoft’s 2011 UEFI and KEK CAs are set to expire in June 2026 and are being replaced by 2023 CAs. This is also discussed at this link.
Is it safe to update or should I ignore it?
Ok, this is seriously impossible. I first tried to download the desktop version onto a 32GB USB stick, but it ran out of space after downloading about 4GB (4,194,268KB, to be exact). This is a brand new stick. Yes, I know that some space is used to help access the rest, but I am SURE 28.8GB is enough space to download 6.1GB. But just to be sure, I decided to try to download it onto a 128GB USB stick. Same problem. The download stopped because it is "out of storage space" after just 4GB. The download works fine when downloading on to my laptop, and only takes up ~6.8GB on my harddrive. What is preventing it from downloading onto my USB sticks? I can guarantee it isn't running out of space.
What's really weird, is that it's just the Desktop version. I've successfully downloaded Ubuntu Server onto the exact same brand 32GB USB stick.
I just swapped out my Microsoft intellimouse Classic with a Microsoft Intellimouse pro because of an issue with tracking on any surface that isn't white. I'm glad to say that tracking is now working. However, my middle-click to paste behaviour is no longer working, and when I middle click, it now brings up the workspace switcher in KDE. I'm running stock Ubuntu 22.04, but then installed the KDE desktop on top. If I plug in my old mouse, the middle mouse button works as expected.
When I googled for an answer, the Google AI told me to remap the buttons using something like:
xinput set-button-map "Microsoft Microsoft Pro Intellimouse Mouse" 1 9 3 4 5 6 7 8 2
However, I tried swapping 2 with every other number in the list, and nothing worked.
I then ran the following command to get a terminal to tell me which mouse button is down:
watch -n 1 xinput --query-state 11
which gives me output like below:
When i hold down on the left and right buttons I see that button 1 and 3 show as down respectively. However, holding down on the middle mouse button does not show any change, but does bring up a panel that appears on the left hand side, with an image of my desktop at the top that says "Default" as shown below:
I must confess that I don't actually know what this is.
Any help on how to get my middle mouse button working how it should be, with the default copy/paste behaviour that Linux has would be much appreciated. This is such an odd issue to have.
A comprehensive write up on the history, properties and importance of Keynesian school of thought.
For along time I am looking forward to a screenshot annotation wich works fine with Gnome + Wayland. I can't find, so I have created one.
If you have the same problem, please take look in: https://schero.codethings.dev/
Thanks!
I have an SFTP server running on Unbuntu 26.04. I originally built it using password authentication for the individual users. I had all the users in a group that had access to the SFTP directory only, and a few users that also had sudo access. This was working great until it was decided to convert to key authentication instead of password. I generated private keys for the users and put the public keys on the server. I have not disabled the passwords yet. This seems to be working for SFTP but when I try to login through PuTTY from my remote machine (running on Windows 11) it returns an error that states the server allows sftp access only and won't even give me access to my own account. How do it make it so users that have sudo permissions can have full access?
"I am trying to install Windows 11 on my Acer laptop without a USB drive. During the installation process, the rEFInd boot management screen does not appear. To access the BIOS settings and prioritize rEFInd as the primary boot option, I have to restart the computer and repeatedly press the F2 or F12 keys. However, despite installing both rEFInd and GRUB, and running numerous commands in the terminal, rEFInd still refuses to show up on my screen
I've try to install Ubuntu Server 26.04 into my new desktop PC. It I tryed with third party drives, without. I tryed see error logs, It simple don´t point anything. Ubuntu 24.05 works fine, but not if you update to 26.04 installer... you must keep 24.05 installer.
Anyone have the same issue? How to work around?
Resumo do PC
Processador
1 x Processador Intel Core Ultra 9 285K, 24-Core, 24-Threads, 3.7GHz (5.7GHz Turbo), Cache 36MB, LGA1851, BX80768285K
Cooler
1 x Water Cooler Acegeek CryoScreen 360, ARGB, 2.8 inch LCD, 360mm, Preto, AG-CRYOSCREEN360-BK
Placa Mãe
1 x Placa Mae MSI Z890 Gaming Plus WiFi, DDR5, LGA1851, ATX, Chipset Intel Z890, Z890-GAMING-PLUS-WIFI
Memória
2 x Memoria Corsair Vengeance, RGB, 16GB (1x16GB), DDR5, 5600MHz, C40, Preto, CMH16GX5M1B5600C40
Armazenamento
1 x SSD WD Black SN8100, 2TB, M.2 2280, PCIe NVMe, Leitura 14900MB/s, Gravacao 14000MB/s, WDS200T1X0M
Placa de Vídeo
1 x Placa de Video Asus GeForce RTX 5090 TUF Gaming OC, 32GB, GDDR7, 512-bit, TUF-RTX5090-O32G-GAMING
Fonte
1 x Fonte Corsair RM1000x Shift, 1000W, Full Modular, 80 Plus Gold, Preta, CP-9020253-BR
Gabinete
1 x Gabinete Gamer Aigo Darkflash Arcee DY470, ARGB, Full-Tower, Lateral de Vidro, Com 4 Fans, Preto, DY470-BK-4F
Cabo de Vídeo
1 x Cabo Displayport Pichau, 1.5m, Vermelho, PG-DPC-RD01
Cabo de Força
1 x Cabo de Forca Pichau, 1.5m, 3 Pinos, Preto, PG-PWC-BL01
Something went wrong when updating Synergy app and now it's impossible to do anything with the package: the dreaded (at least for me) "Sub-process /usr/bin/dpkg returned an error code (1)". I copy the log when trying to purge it:
(Reading database… 250720 files and directories currently installed.)
Removing synergy (3.6.1)…
production build
[dotenv@17.2.4] injecting env (0) from root/.config/Synergy/.env -- tip: 🛠️ run anywhere with `dotenvx run -- yourcommand`
loaded .env from: /root/.config/Synergy/.env
.env file parsed: {}
[env] SYNERGY_LOGGER: not set
[env] SYNERGY_FORCE_CORE_LOG_LEVEL: not set
[env] SYNERGY_FORCE_SERVICE_LOG_LEVEL: not set
using log level: INFO
using logger: /root/.local/state/Synergy/synergy.log
skipping node version check in production (current: v22.22.2)
exiting process with code: 1
dpkg: error processing package synergy (--remove):
old synergy package prerm maintainer script subprocess failed with exit status 1
dpkg: too many errors, stopping
production build
[dotenv@17.2.4] injecting env (0) from root/.config/Synergy/.env -- tip: ⚙️ write to custom object with { processEnv: myObject }
loaded .env from: /root/.config/Synergy/.env
.env file parsed: {}
[env] SYNERGY_LOGGER: not set
[env] SYNERGY_FORCE_CORE_LOG_LEVEL: not set
[env] SYNERGY_FORCE_SERVICE_LOG_LEVEL: not set
using log level: INFO
using logger: /root/.local/state/Synergy/synergy.log
skipping node version check in production (current: v22.22.2)
exiting process with code: 1
Errors were encountered while processing:
synergy
Processing was halted because there were too many errors.
Error: Sub-process /usr/bin/dpkg returned an error code (1)
I tried all the basic troubleshooting stuff like dpkg --configure -a, sudo apt -f install, apt-clean and several forms of deletion without success.
Thank you in advance.
What is it? When I run Android studio it end with this error: Operation rejected (Operace zamítnuta). So I cannot generate apk.
I’d like to install Ubuntu on an old 15" MacBook Pro from early 2013. When I try Ubuntu on the Mac, it seems to work very well, but I can’t get the WiFi to work.
I upgraded from Ubuntu 24.04.4 to 26.04. It seems all is working fine except for one thing. I can't change volume with the volume keys.
Volume is always at maximum. I can use the mute key. Volume up and down show a notification when I click them, but it doesn't change the volume. The only way I have to change volume is to use Settings -> Sound -> Volume levels.
I am using a Lenovo Legion R9000P ADR10 laptop. The internal speakers produce a very flat, quiet, and tinny sound with absolutely no bass. It feels like the subwoofers/woofers are completely disabled, and only the tweeters are functioning. Audio works perfectly fine under Windows, confirming it is a Linux driver/kernel configuration issue (missing pin quirk for this specific model).
System specifications:
Laptop model: Lenovo Yoga Slim 7i 15IMH05
OS: Ubuntu 26.04
Kernel version: Linux 7.0.0-27-generic
I'm running Ubuntu 22.04 on one of my laptops and suddenly DNS doesn't work. It works on all of the other machines on my network. Addressing nodes on my network by IP works. Pinging google or its nameservers gets no response. Resolv.conf looks fine, resolvd is running. Any ideas?
I have been having this problem for a while where the computer upon clicking suspend (or even typing systemctl suspend in the terminal) the display goes black for 1-2 seconds and turns back up in the lock screen.
I have tried the following command:
cat /proc/acpi/wakeup
Which shows this:
Device S-state Status Sysfs node
GPP0 S4 *enabled pci:0000:00:01.1
GPP1 S4 *disabled
GPP3 S4 *disabled
GPP4 S4 *disabled
GPP5 S4 *disabled
GPP6 S4 *disabled
GPP7 S4 *disabled
X161 S4 *disabled pci:0000:07:00.0
X162 S4 *disabled
GPPA S4 *disabled
GPPB S4 *disabled
GPPC S4 *disabled
GPPD S4 *disabled
GPPE S4 *disabled
GPPF S4 *disabled
GP10 S4 *disabled
GP11 S4 *disabled
GP12 S4 *enabled pci:0000:00:07.1
GP13 S4 *enabled pci:0000:00:08.1
XHC0 S4 *enabled pci:0000:09:00.3
GP30 S4 *disabled
GP31 S4 *disabled
PS2K S3 *disabled
PS2M S3 *disabled
UAR1 S4 *disabled pnp:00:01
*disabled serial-base:00:01:0
*disabled serial-base:00:01:0.0
GPP2 S4 *enabled pci:0000:00:01.3
PTX2 S4 *disabled pci:0000:04:00.0
RLAN S4 *disabled pci:0000:05:00.0
PTX1 S4 *disabled
PTXH S4 *enabled pci:0000:02:00.0
I have the tried to disable all of the enabled devices with this command(obviously typing the actual device in the place of [DEVICE])
sudo /bin/sh -c '/bin/echo [DEVICE] > /proc/acpi/wakeup'
...but even still nothing worked.
In https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#dquilt-ap which is from “Guide for Debian Maintainers” there is this sample:
dquilt new 000-prefix-usr.patch
In https://www.debian.org/doc/manuals/maint-guide/modify.en.html#fixupstream which is from “Debian New Maintainers’ Guide” (older than the one above), there is this sample:
dquilt new fix-gentoo-target.patch
Looking at the first, I supposed the digits at the start of the patch name, have some meaning for the system. But the second example does not use it.
Is it interpreted in any way by quilt or is it a convention some body have for their own purpose and some others don’t?
Side note for people who read this: dquilt is an alias of quilt, it’s not an installed command, as explained in the second link (it's easy to overlook it) and also explained here: What is dquilt and how do I get it?
We have two similar medical instruments that have stopped working. When the computer (Windows compatible) boots up, a DOS-looking message comes up that says that the Ubuntu operating system is expired and then a black screen with a cursor arrow that won't move, remains. It is Ubuntu 11.04.
Hi everyone,
I'm experiencing a strange display issue on my Ubuntu laptop that recently started happening on two different machines (including one at my office).
The Symptom:
Out of nowhere, the built-in laptop monitor completely goes dark.
Immediately after the monitor dies, the OS acts as if the system should go to sleep and suspends the machine.
If I wake it back up and plug in an external monitor, the external monitor works perfectly fine as the primary display, but the OS behaves as if the built-in monitor doesn't exist at all.
The issue is intermittent. A few minutes ago, it suddenly went back to normal and the built-in display worked again, only to die completely a few minutes later.
The display setting shows only one monitor (the external monitor) when the built-in monitor is not working.
Note: The BIOS still successfully recognizes the built-in monitor even when Ubuntu cannot see it.
Because this is happening on two separate physical machines, I suspect a recent software, kernel, or power management update might be causing a conflict or triggering a false "lid closed" event.
System Details:
OS: Ubuntu 24.04
Kernel: 6.17.0-35-generic
Session Type: wayland
Has anyone else run into this recently? What logs should I look into next to isolate whether this is a systemd-logind lid-switch bug or a graphics driver issue?
I have two monitors which I have turned physically in portrait position. One turned left and other turned right. I adjusted Settings -> Displays so that the layout for my desktop is okay, but the login screen is still landscape.
I read that this problem could be fixed with following instructions:
sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config/
sudo chown gdm:gdm /var/lib/gdm3/.config/monitors.xml
sudo systemctl restart gdm3
But to no avail, it just does not work. No matter if I reboot or even completely turn off and back on computer. The login screen remains in landscape position.
However gdm displays proper login screen when returning from suspend. This is of course logical since it is not providing multi-user login. Lock screen works as well.
I had my doubts for the monitors.xml solution, since there were no existing monitors.xml file in /var/lib/gdm3/.config/ directory. I even looked into gdm source code and there is no references to monitors.xml at all. So how should restarting could change login screen position according to monitors.xml. What a stupid idea.
This is a displaymanager problem which is run by gdm, not a desktop manager problem which has user configuration in ~/.config/monitors.xml. Copying that file into /var/lib/gdm3/.config/ is braindead solution, I bet it has never worked.
So what now? I guess I have to accept that login screen in gdm-land is carved into stone as landscape position , just like BIOS does. It is idiotic and stupid, but hey what can I do...
First of all, these are the laptop's specs:
Model: SAMSUNG LTD. 300E4A/300E5A/300E7A
Memory: 4 GiB
Processor: Intel Core i5-2450M x 4
Graphics: Intel HD Graphics 3000 (SNB GT2)
Disk: 1 TB HDD
It's old (10+ years) and I wanted to give it a new life just for lightwork. I checked and it is not under the supported hardware for ubuntu, but used the Try Ubuntu feature and it works, so I assume that even if it hasn't been tested to be in the supported devices tab it should work just fine.
The problem:
After the install process I rebooted and the PC asked to remove the bootable device and press enter, so I removed the USB flash drive I used and press enter. Now, when I try to boot the PC, it just gets stuck in a loop, trying to boot up. I can't get into the grub menu by holding down the Shift key. The only thing I can do is boot into BIOS in the Boot settings. I only have the option to change the Boot Priority Order. Another device appear on the list besides the HDD. I already tried changing the priorities, but nothing changes.
If I boot up with the bootable USB connected the grub menu appears without any input from me, and only two options are available: "Try or Install Ubuntu", and "Ubuntu (safe graphics)". The first time I clicked on the first option and just reinstalled the OS but the problem didn't go away. I can close the install window if I boot like that again and use Ubuntu as the Try Ubuntu feature, but nothing more.
I already tried different things I found online in forums, but I don't have the exact same issues or menus/options.
For example,I tried the solution in this forum, but I don't have the add customized boot option in my BIOS.
I also tried this one, but I don't have the Advanced options for Ubuntu on my GRUB menu.
The other thing that I tried was Boot-Repair twice. The first time it have back this link: https://paste.ubuntu.com/p/bpsF9b8Nqh/, and said to share it if the problem persists (which it does), and it also gave me this warning.
The second time I tried using Boot-Repair I got this error message: Glade2script-python3 Is Not Responding.
I screen recorded what happens when I turn on the PC with and without the USB:
Video 1: Booting without bootable USB and getting into BIOS
Video 2: Booting with bootable USB
I'm afraid I've gotten myself into something that's way above my understanding (I never used Linux before).
Edit: Result of sudo fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: SAMSUNG HN-M101M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D564C26C-C9BF-49E9-9DC6-3A995C70E836
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 1953521663 1953517568 931.5G Linux filesystem
Disk /dev/sdb: 14.51 GiB, 15581839360 bytes, 30433280 sectors
Disk model: STORE N GO
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x39ed4277
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 30433247 30431200 14.5G c W95 FAT32 (LBA)
does anyone know why widevine is not working for drm on older devices?
I have a lenovo b50 that no longer streams from ITVX, although some films seem to work, others don't. My dell optiplex 3020. 4th gen i5 with intel hd4060 graphics is also no longer being accepted by ITVX.
The browser, Firefox or Chrome, is displaying 'Update your browser'.
MTIA
[Edit] I am using Ubuntu desktop as installed yesterday 28th June. The latest 26.04 LTS So the latest version of browsers etc. with ubuntu restricted extras installed and DRM accepted on Firefox.
Firefox version 149.0.2 64 bit Ubuntu - kernel version: 7.0.0-27-generic
I have the same problem on Fedora workstation and Fedora Silverblue.
For a couple weeks now, I've been experiencing random reboots on my laptop.
They happen once or twice a day or not at all, either while in use (black screen), from suspend, or at boot (-> GRUB-menu). All I do at the laptop is write texts and ocassionally game.
From my logs, these "Previous system reset reason" messages jump out at me:
internal CPU shutdown event occured - Coincides with reboot times, except at boot.software wrote 0x6 to reset control register 0xCF9 - Too many, but a few coincide with at boot.ACPI power state transition occurred - Rare, possibly unrelated.See sample logs HERE and HERE. (Some things are redacted.) Also, see my CPU information HERE.
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 44 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 3 7320U with Radeon Graphics
CPU family: 23
Model: 160
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU(s) scaling MHz: 37%
CPU max MHz: 4151.7300
CPU min MHz: 425.1780
BogoMIPS: 4791.29
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pg
e mca cmov pat pse36 clflush mmx fxsr sse sse2 ht s
yscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constan
t_tsc rep_good nopl xtopology nonstop_tsc cpuid ext
d_apicid aperfmperf rapl pni pclmulqdq monitor ssse
3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xs
ave avx f16c rdrand lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw
ibs skinit wdt tce topoext perfctr_core perfctr_nb
bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_psta
te ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 a
vx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt
clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occ
up_llc cqm_mbm_total cqm_mbm_local clzero irperf xs
aveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock
nrip_save tsc_scale vmcb_clean flushbyasid decodea
ssists pausefilter pfthreshold avic v_vmsave_vmload
vgif v_spec_ctrl umip rdpid overflow_recov succor
smca sev sev_es
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 2 MiB (4 instances)
L3: 4 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-7
Vulnerabilities:
Gather data sampling: Not affected
Ghostwrite: Not affected
Indirect target selection: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Old microcode: Not affected
Reg file data sampling: Not affected
Retbleed: Mitigation; untrained return thunk; SMT enabled wit
h STIBP protection
Spec rstack overflow: Mitigation; Safe RET
Spec store bypass: Mitigation; Speculative Store Bypass disabled via p
rctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user poi
nter sanitization
Spectre v2: Mitigation; Retpolines; IBPB conditional; STIBP alw
ays-on; RSB filling; PBRSB-eIBRS Not affected; BHI
Not affected
Srbds: Not affected
Tsa: Not affected
Tsx async abort: Not affected
Vmscape: Mitigation; IBPB before exit to userspace
Since upgrading to Ubuntu 26.04, I've had Linux kernel panics at boot once in a blue moon. Could this be relevant?
The only software I've installed within these last few weeks are VSCodium and .NET SDK.
For VSCodium:
snap install codium --classicsudo rm /usr/local/bin/dotnet (again, see later)For .NET SDK:
sudo snap install dotnet-sdk --classic (or dotnet-sdk-100 when installing VSCodium)sudo ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet (for dot-net-100)~.profile:
export DOTNET_CLI_TELEMETRY_OPTOUT=trueexport DOTNET_ROOT=/snap/dotnet-sdk/currentWhat I've tried:
What I haven't tried:
As suggested by ChanganAuto, I updated the BIOS. As it turns out, I was on version 306 (2023/07/25). I followed the instructions from both "BIOS Update" and my laptop vendor's:
/boot/efi/EFI/boot/efi/EFIWill update if the issue still persists.
The problem is still present, perhaps worse. I had 3 reboots this morning. Oddly enough, I had none yesterday. See today's boot logs: 08:33, 08:56, 09:55, 10:28.
I am having a HP laptop with AMD ryzen 3 3250u processor and I installed ubuntu 26 LTS and I tried to add a hibernation device in the laptop using a swap file but what I am experiencing is that when I run the command sudo systemctl hibernate my screen goes blank for sometime and return back to the lockscreen, sometime it work for the first time and subsequent hibernate fails, I am pasting my configuration files
/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p8 during curtin installation
/dev/disk/by-uuid/4c859583-daba-499b-9918-8bc642b14b80 / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/D6BC-8F6E /boot/efi vfat defaults 0 1
/swapfile none swap sw 0 0
/etc/default/grub
# If you change this file or any /etc/default/grub.d/*.cfg file,
# run 'update-grub' afterwards to update /boot/grub/grub.cfg.
# For full documentation of the options in these files, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=4c859583-daba-499b-9918-8bc642b14b80 resume_offset=169984"
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE/GOP/UGA
# you can see them in real GRUB with the command `videoinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
findmnt -no UUID -T /swapfile
4c859583-daba-499b-9918-8bc642b14b80
sudo filefrag -v /swapfile | awk '$1=="0:" {print substr($4,1,length($4)-2)}'
169984
here is the result for the kernel command
journalctl --since today -p emerg..err
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:25 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:26 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (000000002bbd688e) [S>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 17:44:28 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:29 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:35 Zenbook kernel:
Jun 22 17:44:35 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:44:35 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 17:44:35 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:44:35 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 17:44:41 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:41 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:43 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:44 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:45 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:49 Zenbook gdm-password][2992]: gkr-pam: unable to locate daemon control file
Jun 22 17:44:53 Zenbook systemd[3231]: Failed to start app-gnome-snap\x2duserd\x2dautostart-37>
Jun 22 17:44:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:57 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:58 Zenbook systemd[3231]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 17:45:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:10 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:11 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:27 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:27 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:01 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:49 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:49 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:40 Zenbook gdm3[1640]: Gdm: Failed to list cached users: GDBus.Error:org.freedesk>
-- Boot 6222b8fdb133452c9a58e6ee5f5c0f39 --
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: Failed to create device parport0
Jun 22 17:50:05 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (00000000d3275a16) [S>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 17:50:14 Zenbook kernel:
Jun 22 17:50:14 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:50:14 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 17:50:14 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:50:14 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 17:50:20 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:20 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:22 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:22 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:45 Zenbook gdm-password][3131]: gkr-pam: unable to locate daemon control file
Jun 22 17:50:51 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:51 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:52 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:52 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:54 Zenbook systemd[3204]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 17:50:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:15 Zenbook systemd-sleep[5143]: Failed to put system to sleep. System resumed aga>
Jun 22 17:51:15 Zenbook kernel: PM: hibernation: Image allocation is 79836 pages short
Jun 22 17:51:15 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
Jun 22 17:51:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:34 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:35 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:51 Zenbook chronyd[1427]: Could not connect to [2620:2d:4002:1::3123]:4460 (4.ntp>
Jun 22 17:51:52 Zenbook chronyd[1427]: Could not connect to [2620:2d:4000:1::2123]:4460 (1.ntp>
Jun 22 12:28:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:31 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:32 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:43:13 Zenbook systemd-sleep[9679]: Failed to put system to sleep. System resumed aga>
Jun 22 12:43:13 Zenbook kernel: PM: hibernation: Image allocation is 116000 pages short
Jun 22 12:43:13 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
-- Boot f38d6bb7801c425387f1a8e9dbed4398 --
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (000000003573ea84) [S>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 12:55:51 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 12:55:51 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 12:55:51 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 12:55:51 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 12:56:00 Zenbook chronyd[1458]: Could not connect to [2620:2d:4002:1::3123]:4460 (4.ntp>
Jun 22 12:57:43 Zenbook gdm-password][3020]: gkr-pam: unable to locate daemon control file
Jun 22 12:57:51 Zenbook systemd[3095]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 12:58:16 Zenbook kernel: PM: hibernation: Image allocation is 83357 pages short
Jun 22 12:58:16 Zenbook systemd-sleep[4989]: Failed to put system to sleep. System resumed aga>
Jun 22 12:58:17 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
free
total used free shared buff/cache available
Mem: 5479732 3315900 944936 138456 1614868 2163832
Swap: 16777212 42820 16734392
sudo swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 16G 925.1M -1
ls -lha /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 160 Jun 28 22:19 .
drwxr-xr-x 12 root root 240 Jun 28 22:19 ..
lrwxrwxrwx 1 root root 10 Jun 28 22:19 15cf6fe2-efa4-47b6-9adc-bb279ca2ef48 -> ../../sda4
lrwxrwxrwx 1 root root 10 Jun 28 22:19 28D6-4C0F -> ../../sda3
lrwxrwxrwx 1 root root 15 Jun 28 22:19 4E4A61734A61592B -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 10 Jun 28 22:19 8E5A33945A337853 -> ../../sda2
lrwxrwxrwx 1 root root 15 Jun 28 22:19 C260-A33D -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 10 Jun 28 22:19 b8cfc018-6aa3-407c-bae8-4c7f643c146d -> ../../sda5
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1200800 5032 1195768 1% /run
/dev/sda4 54822144 34869628 17135236 68% /
tmpfs 3002000 39544 2962456 2% /dev/shm
efivarfs 160 87 69 56% /sys/firmware/efi/efivars
none 1024 0 1024 0% /run/credentials/systemd-journald.service
none 1024 0 1024 0% /run/credentials/systemd-resolved.service
tmpfs 3002000 348 3001652 1% /tmp
/dev/sda3 1046508 6452 1040056 1% /boot/efi
tmpfs 600400 100 600300 1% /run/user/1000
sudo blkid
/dev/nvme0n1p1: UUID="C260-A33D" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="ae7b16d0-eb14-47e7-9a6c-4b9e75b0af67"
/dev/nvme0n1p2: BLOCK_SIZE="512" UUID="4E4A61734A61592B" TYPE="ntfs" PARTUUID="f6b6807e-f516-4383-a17b-600f9967e2f9"
/dev/sda2: LABEL="Directory" BLOCK_SIZE="512" UUID="8E5A33945A337853" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="59c46e43-2a47-437e-9b29-917a7baebede"
/dev/sda3: LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="28D6-4C0F" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="BOOT" PARTUUID="588b1594-4bd0-44f9-922d-0f5b0ca8a030"
/dev/sda4: LABEL="ROOT" UUID="15cf6fe2-efa4-47b6-9adc-bb279ca2ef48" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="ROOT" PARTUUID="ae5cab5c-3514-494c-99f8-7acbb7710d44"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop17: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop8: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop15: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop13: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop11: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop9: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop16: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop14: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop12: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop10: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="236f1e99-7832-4089-9411-4dfdbeb10e8b"
Well, I have two virtual machines. One with ubuntu 22.04 lts and the other with 24.04 lts. On both, I created a "passenger" user account with the adduser command.
Then on the "passenger" I created a sidekiq service in the path /home/passenger/.config/systemd/user/sidekiq.service, here is the code:
[Unit]
Description=Sidekiq
After=network.target
[Service]
Type=simple
WorkingDirectory=/home/passenger/sidekiq-rails
ExecStart=/bin/bash -lc 'bundle exec sidekiq -e production >> log/sidekiq.log'
ExecStartPost=/bin/bash -lc "systemctl --user show --property MainPID sidekiq.service | awk 'BEGIN {FS=\"=\"} {print $2}' > tmp/sidekiq.pid"
Restart=on-failure
RestartSec=3
[Install]
WantedBy=default.target
--> https://pastebin.com/t7fyH1Qy
Smoothly starts systemctl --user start sidekiq.service. I installed the Monit tool and prepared in the path:
/etc/monit/conf.d/sidekiq
the following configuration:
check process sidekiq with pidfile /home/passenger/sidekiq-rails/tmp/sidekiq.pid
start program = "/bin/su - passenger -c 'XDG_RUNTIME_DIR=/run/user/$UID DBUS_SESSION_BUS_ADDRESS=unix:path=${XDG_RUNTIME_DIR}/bus systemctl --user start sidekiq.service'"
stop program = "/bin/su - passenger -c 'XDG_RUNTIME_DIR=/run/user/$UID DBUS_SESSION_BUS_ADDRESS=unix:path=${XDG_RUNTIME_DIR}/bus systemctl --user stop sidekiq.service'"
if memory usage > 1024 MB for 2 cycles then alert
if does not exist then alert
--> https://pastebin.com/dDxxNPkf
On the other hand, the problem starts when I testfully disable sidekiq by simply typing systemctl --user stop sidekiq. Then on Ubuntu 22.04 Monit using the prepared config fires sidekiq, and on Ubuntu 24.04 there is an error
[2025-06-26T09:59:33+0000] error : 'sidekiq' failed to start (exit status 1) -- '/bin/su - passenger -c XDG_RUNTIME_DIR=/run/user/$UID DBUS_SESSION_BUS_ADDRESS=unix:path=${XDG_RUNTIME_DIR}/bus systemctl --user start sidekiq.service': su: cannot set groups: Operation not permitted
--> https://pastebin.com/qaNZs49C
Of course I have:
ls -l /bin/su
-rwsr-xr-x 1 root root 55680 Dec 5 2024 /bin/su
loginctl enable-linger passenger executed on both machines
Which tool to use to take screenshots of areas selected by mouse on wayland, and annotate afterwards?
None of tools that I was using works with 24.04
The scanner in my USB-connected Brother DCP7030 multi-function device stopped working when I upgraded my Lubuntu to 22.04. In an attempt to get it working, I upgraded further to 24.04, but it still refuses to play ball. The printer in the MFD still works fine. I've installed the Brother drivers and fix to run as admin mode from the brother website. https://support.brother.com/g/b/downloadlist.aspx?c=gb&lang=en&prod=dcp7030_all&os=128 but it still refuses to be visible to SANE.
$ dpkg -l | grep Brother
ii brother-udev-rule-type1 1.0.2 all Brother udev rule type 1
ii brscan3 0.2.13-1 amd64 Brother Scanner Driver
ii printer-driver-brlaser 6-3build2 amd64 printer driver for (some) Brother laser printers
$ lsusb
Bus 001 Device 008: ID 04f9:01ea Brother Industries, Ltd DCP-7030
sane-find-scanner
found possible USB scanner (vendor=0x04f9, product=0x01ea) at libusb:001:008
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
Your USB scanner was (probably) detected. It may or may not be supported
by SANE. Try scanimage -L and read the backend's manpage.
$ scanimage -L
No scanners were identified.
If you were expecting something different, check that the scanner is plugged in,
turned on and detected by the sane-find-scanner tool
I just got an HP M110W printer and configured it as per HP Smart and connected it. It prints in Windows, but I use Ubuntu 22.04 (currently) 99.95% of the time. The printer shows in the Settings and, when I try to print a test page, it twitches but nothing prints. I installed hplip and the CUP libraries and can use lpstat, lpq,etc. but lp filename does not work either. I'm desperately hoping someone on this forum can help me print, otherwise I'm going to return the printer. I have run through all the procedures I found on the HP site but their Chat basically told me I'm on my own.
My computer hung up so I forced it to turn off. When it restarted, I had this error message:
The root filesystem on /dev/sda2 requires a manual fsck.
So then I typed in fsck -f /dev/sda1
Then I got a message:
fsck from util-linux 2.37.2
(initramfs)
I typed in "help" and got a long list of commands.
I have no idea what to do that this point. Please pretend I am your grandmother as I do not understand the Ubuntu jargon.
I'm new to Ubuntu and want to disable the turbo boost. I tried with cpufreq but i cant get it to work. is there any other way to do it.
In windows it was as easy as changing the CPU speed from 100 to 99.
What does this error mean, and how can I solve it?
Error mounting /dev/sda4 at /media/pzj/B8082EA0082E5D9E: Command-line
mount -t "ntfs" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177"
"/dev/sda4" "/media/pzj/B8082EA0082E5D9E"' exited with non-zero exit
status 18: Failed to write lock '/dev/sda4': Resource temporarily
unavailable Error opening '/dev/sda4': Resource temporarily
unavailable Failed to mount '/dev/sda4': Resource temporarily
unavailable (udisks-error-quark, 0)
Here is a snap of the Disk via disks.
Edit:
Output of sudo fdisk -l
pzj@cloudz:~$ sudo fdisk -l [sudo] password for pzj:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical):
512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096
bytes Disklabel type: gpt Disk identifier:
01F58508-AB5F-4912-9A0A-2CB7F87AD409
`Device Start End Sectors Size Type`
`/dev/sda1 2048 616447 614400 300M Windows recovery environment`
`/dev/sda2 616448 821247 204800 100M EFI System`
`/dev/sda3 821248 1083391 262144 128M Microsoft reserved`
`/dev/sda4 1083392 1953523711 1952440320 931G Microsoft basic data
Output of mount
pzj@cloudz:~$ mount
/dev/sdb5 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,nodev,noexec,nosuid)
sysfs on /sys type sysfs (rw,nodev,noexec,nosuid)
none on /sys/fs/cgroup type tmpfs (rw,uid=0,gid=0,mode=0755,size=1024)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /sys/firmware/efi/efivars type efivarfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,nodev,noexec,nosuid,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,nodev,noexec,nosuid,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sdb1 on /boot/efi type vfat (rw)
/dev/sdb4 on /var type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nodev,noexec,nosuid)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,noexec,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=pzj)
/dev/sda1 on /media/pzj/Recovery type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
pzj@cloudz:~$
I just installed Ubuntu 12.10 and I need to make a custom xorg.conf file. By default, there is not an xorg.conf file on my system. I know what I need to write in the config, but I just don't know how to make X load it...
Should I put my custom commands in a file that already exists? Where is it?
Should I make my own xorg.conf file and put it in /etc/X11?