Brightness all way up. Drivers installed. Rolled back to known good configuration. Settings at default. Still dim. External monitor is fine. Any ideas?
I recently installed Kubuntu 26.04 on my Framework 16 laptop.
When I installed Kubuntu, I created a user, "foo", and set it to log in automatically on boot.
Since then, I have created another user, "bar". (Both "foo" and "bar" are administrative users.)
I would now like "bar" to be the user which is logged in automatically on boot, rather than "foo". However, I can't find any way to change this.
This article says to go to the "Startup and Shutdown" item in the left sidebar of System Settings.
However, on my computer, there is no "Startup and Shutdown" item present in the left sidebar:
I've looked at other items that seem promising, such as "Screen Locking", "Users", "Autostart", and "Session", but none of them have a way to change the auto-login behavior.
How can I change it to log in "bar" instead of "foo"?
this is my first time using linux on a real machine. I have run vm's before, but this is my first ever install.
I want to clarify that I already tried managing audio settings. I can see the bar move, but nothing happens. I can hear from the bios, so I know that it isn't hardware.
It looks to me as if it has detected my HDMI audio, but that my laptops speakers and headphone jack themselves just don't appear.
I have compiled the following of what i found that may be helpful:
System
Laptop: HP OmniBook X Flip Laptop 14-kc0xxx
DMI Product Version: Type1ProductConfigId
Platform: AMD Krackan / Ryzen AI
Kernel: 7.0.0-28-generic
Distribution: Kubuntu
PCI Devices
HDMI Audio
Device: AMD Radeon High Definition Audio Controller
PCI ID: 1002:1640
Driver: snd_hda_intel
Audio Coprocessor
Device: AMD Audio Coprocessor
PCI ID: 1022:15e2
Subsystem: HP 103c:8ea1
Driver: snd_acp_pci
Symptoms
Internal speakers are missing.
Headphone output is missing.
HDMI audio works.
Internal microphone works.
PipeWire only exposes HDMI outputs.
ALSA only exposes HDMI playback devices.
ALSA
aplay -l only reports HDMI playback devices.
aplay -L contains only:
HDMI outputs
PipeWire
null
No internal playback device exists.
/proc/asound/cards
Card 0
HD-Audio Generic (HDMI)
Card 1
acp-pdm-mach
The second card is capture-only (internal microphone).
No internal playback card exists.
PipeWire
PipeWire detects only the Radeon HDMI outputs.
No Speaker, Headphones, or Internal Audio sink is created.
Loaded Audio Modules
Relevant modules include:
snd_sof
snd_sof_amd_acp
snd_sof_amd_acp70
snd_sof_pci
snd_soc_core
snd_acp_pci
snd_soc_nau8821
soundwire_amd
dmesg
No errors related to:
cs35l41
max98373
max98390
rt5682
rt711
rt722
rt715
No firmware loading failures were observed.
No SOF boot failures were observed.
No codec initialization messages appear at all.
Additional Information
The ACP PDM microphone machine driver initializes correctly.
The speaker playback topology never appears to be instantiated.
This appears to be a missing machine driver / topology / ACPI quirk for HP subsystem ID:
103c:8ea1
rather than a PipeWire or ALSA userspace configuration issue.
Reproduction
Boot Linux.
Open Sound Settings.
Only HDMI outputs are available.
Internal speakers and headphone output are absent.
Expected Result
Internal speakers and headphone output should be detected and usable.
Actual Result
Only HDMI playback devices are created.
My Bluetooth headset works perfectly for audio output, but its microphone never
appears anywhere -- not in Settings > Sound, not in `pactl`, not in browsers.
Every guide says to switch the headset to the HSP/HFP profile in pavucontrol.
I can't: that profile isn't in the list. `pactl list cards` only offers A2DP:
Profiles:
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
a2dp-sink: High Fidelity Playback (A2DP Sink, codec SBC) (sinks: 1, sources: 0, ...)
a2dp-sink-sbc_xq: High Fidelity Playback (A2DP Sink, codec SBC-XQ) (sinks: 1, sources: 0, ...)
Active Profile: a2dp-sink
The headset does advertise HFP, so this isn't a headset that lacks the profile:
$ sdptool search --bdaddr AA:BB:CC:DD:EE:FF HF
Service Class ID List:
"Handsfree" (0x111e)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0107
It advertises no HSP at all, so there's no fallback (`sdptool search ... HS`
returns nothing).
`journalctl -u bluetooth` repeatedly shows:
bluetoothd[1146]: src/profile.c:ext_io_disconnected() Unable to get io data for
Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
So HFP is being connected and then torn down, but I can't tell why.
System: Ubuntu 24.04.4 LTS, PipeWire 1.0.5, WirePlumber 0.4.17, bluez 5.72,
Intel AX201. `libspa-0.2-bluetooth` is installed. Things I already ruled out:
- mic permission in the browser (granted)
- `bluez5.roles` -- HFP roles are enabled by default
- `bluez5.hfphsp-backend-native-modem = "any"` -- no effect, this laptop has no
cellular modem so ModemManager exposes nothing
How do I find out why the HFP link is dropping?
Iam new to linux Ubuntu and it is my first day , iam not able to adjust brightness at all .. Please anyone help me out . Version is ubuntu 2026
Here is an interesting bug I discovered in Ubuntu 26.04. I am set up for auto-login since I am the only user on the system. A day or two ago I decided to take a look at the Cinnamon desktop option. So I logged out and during the login process switched to the Cinnamon desktop.
When the desktop came on I had no keyboard or mouse access and there were no menu items and no way I could discover to gain control of the system and return to my default desktop.
So I powered down and restarted only to come right back to the inaccessible Cinnamon desktop.
I had to boot up in recover mode and go through the root line command and access my user profile desktop option to remove Cinnamon and replace it with another desktop that would function so I could actually log out and then back in setting the desktop back to Ubuntu default.
This took about four hours with the help of AI (that was basically going around in circles until I suggested that we look at the user profile) I was able to get this mess straightened out.
The question is this - Can you please add an option on the Reboot Recovery Mode that will allow a user to reboot into the default Ubuntu or other Gnome desktops that might be available on the current system???
One thing to note: in older Ubuntu versions such as Ubuntu 16 - this was not a problem, even when entering into experimental desktops that crashed or acted similarly to the above Cinnamon problem - I was always able to access my keyboard.
Thank you for looking into this…
cb
On Ubuntu MATE .. I think Gnome has it too, there is sticky notes. I like that app for quick little notes. I'm wondering if there is a similar panel app for Obsidian? If that makes sense. I like Obsidian, but it's a whole thing, not really good for just busting out a quick note. Granted, I just started using Obsidian, so maybe I'm missing something here. I'm looking for a panel applet to do what sticky notes does, but with Obsidian. Is there such a thing?
My Ubuntu 22.04 operating system on an HP laptop is stuck at a black screen showing /dev/nvme0n1p5: clean, 569467/30539776 files, 13734959/122139392 blocks with a blinking cursor right after the disk check; the disk has plenty of free space and internet works in recovery mode, but sudo apt update fails with multiple errors — likely due to corrupted package sources — so I cannot reinstall GDM or the graphics drivers to fix the GUI. The laptop works with dual boot with Windows, and Windows works normally. Note they both were working normally together, and I didn't change anything. I was just booting Ubuntu as usual.
Ubuntu 26.04, new installation. Although I tell Libreoffice Writer to print multiples it doesn't.
Do I need to edit a config file? If so, how do I access them?
Is there any laptop that is near-perfectly compatible with Ubuntu?
Why is this like in Apple-computers ? In terminal I cannot use char for (.) and not for (;) when I want to type in new password ?
The char for (.) and for (;) is declared as wrong char in /bin/bash when I want to type in new password ?
These chars (.) and for (;) are not accepted inside a password ?
This was not the case in earlier versions of bash ?
I am facing a crash when I try to start my system with plasma-login-manager and multiple monitors. I'd like to report the crash, but
coredumpctl info PID
Shows me the core dump, but with several placeholders (n/a) like
Stack trace of thread 1521:
#0 0x00007d8d73898d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1 0x00007d8d7389b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2 0x00007d8d70b99edd n/a (libgallium-25.2.8-0ubuntu0.24.04.2.so + 0x599edd)
#3 0x00007d8d70b65fbb n/a (libgallium-25.2.8-0ubuntu0.24.04.2.so + 0x565fbb)
#4 0x00007d8d70b99e0c n/a (libgallium-25.2.8-0ubuntu0.24.04.2.so + 0x599e0c)
#5 0x00007d8d7389caa4 start_thread (libc.so.6 + 0x9caa4)
#6 0x00007d8d73929c6c __clone3 (libc.so.6 + 0x129c6c)
So I guess there are missing debug symbols. But apt search libgallium does not list any debug symbol package. I already added the ddebs repo as explained (here and there).
Where do I get the debug symbols from?
My distribution: KDE Neon / Ubuntu 24.04
I'm a complete Linux newbie and I'm trying to install the GMP library on Kubuntu 26.04 to run some computations, since everything on Linux runs faster.
While running the configure file for GMP i get the following error:
leona@leona:~/Downloads/PARI/gmp-6.3.0$ sudo ./configure --enable-cxx
checking build system type... raptorlake-pc-linux-gnu
checking host system type... raptorlake-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=64
checking compiler gcc -O2 -pedantic -fomit-frame-pointer -m64 ... no, long long reliability test 1
checking whether cc is gcc... yes
checking compiler cc -O2 -pedantic -fomit-frame-pointer -m64 ... no, long long reliability test 1
checking ABI=x32
checking compiler gcc -O2 -pedantic -fomit-frame-pointer -mx32 ... no, program does not run
checking whether cc is gcc... yes
checking compiler cc -O2 -pedantic -fomit-frame-pointer -mx32 ... no, program does not run
checking ABI=32
checking compiler gcc -m32 -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
checking compiler gcc -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
checking compiler icc -no-gcc ... no
checking whether cc is gcc... yes
checking compiler cc -m32 -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
checking compiler cc -O2 -pedantic -fomit-frame-pointer ... no, long long reliability test 1
configure: error: could not find a working compiler, see config.log for details
I can confirm that gcc and g++ are correctly installed and working. Looking this error up online I also found out that adding the build option --build=x86_64-linux might solve the issue but I had no luck.
Lastly, having installed gcc from apt, I saw that it has been installed in /usr instead of the classical /usr/local, but adding --prefix=/usr does not help again.
I am lost, if somebody could help I'd really appreciate it. Thank you!
Hardware:
RTX 3090, LG 32LF510Z TV over HDMI
Software:
NVIDIA 595.84, kernel 7.0.0-28, Ubuntu 24.04, GDM/Xorg
Symptom:
Plymouth / Ubuntu boot logos display correctly on the TV. Once GDM starts, the TV shows “No signal.” The box is not headless — nvidia-smi works, another monitor works fine over the same GPU.
What the logs say
Xorg init prints:
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-1
(--) NVIDIA(GPU-0): DFP-5: connected
...
(WW) NVIDIA(0): No valid modes for "1360x768+0+0"; removing.
(WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
(II) NVIDIA(0): Setting mode "DFP-5:nvidia-auto-select"
Xorg sees the connector, but cannot read EDID. Without EDID it rejects every forced candidate and falls back to nvidia-auto-select, which the TV then refuses.
What was tried (all failed):
| Fix | Result |
|---------------------------------------------------------------------------------------------------------------|--------------------------------------------|
| video=HDMI-A-2:1360x768@60e boot param | No signal; kernel DRM rejects 1366x768 |
| video=HDMI-A-2:1360x768@60e nvidia_drm.fbdev=1 | Same |
| Xorg Option "ConnectedMonitor" "DFP-5" + AllowNonEdidModes + metamodes 1360x768, 1366x760, 1366x762, 1366x765 | All rejected: “No valid modes … removing.” |
| Stock config (no overrides) | Same EDID read failure, blank TV |
| Different HDMI port + different cable | Same |
| Different monitor | Works immediately |
Diagnosis:
The TV’s EDID reports 1360x768 as preferred timing, but the panel is natively 1366x768. Early boot (firmware/kernel fbcon) ignores EDID and pushes a mode anyway, so logos appear. Xorg’s NVIDIA DDX respects EDID, cannot read it cleanly on this driver/kernel combo, and ends up with a timing the TV won’t lock onto.
Open question / workaround:
Has anyone gotten this TV (or any EDID-lying panel with preferred != native) working under NVIDIA 595 + kernel 7.0 without a custom EDID blob? The untested path is capturing the EDID, patching the preferred timing to 1366x768, and loading it via Xorg CustomEDID.
TL;DR — Box is healthy. This is an NVIDIA + LG EDID handshake bug. Boot path works, however Xorg path does not.
I'm trying to install Ubuntu Desktop 26.04 on a chassis that was manufactured as a backup appliance. The installer keeps failing with no specific error message, I only get the curtin logs and that's it. (The UI shows me a log file and then I figured out how to get the same log file through terminal so I could start saving and comparing logs.)
The OS drive is a refurbished solid state drive that I just got, because the old OS drive in the device was bad.
I figured out some things that I think are helping it get a bit further than it used to:
I haven't been trying to boot Ubuntu after most of these installs. The one time that I did, it was when it thought it had an internet connection but couldn't actually use it due to having no DNS, and it was missing a bunch of basic utilities. I gave up and tried to reinstall when I hit something I needed (forget which command unfortunately) that normally comes with Ubuntu but was absent, and is installed with a deb file instead of apt, but I couldn't find the deb file online anywhere because it's supposed to come with the OS.
Here are the most recent two logs. One was taken with an additional USB drive plugged in that I use to store the log files, the other one I waited til after it had run before plugging in the log storage USB.
Here's the last little bit of the log that seemed to get the farthest:
Applying debconf selections
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'debconf-set-selections'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'dpkg-query', '--list'] with allowed return codes [0] (capture=True)
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.006
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.009
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
UEFI remove old olders efi state:
EFIBootState(current='0009', timeout='1 seconds', order=['000A', '0009', '0005'], entries={'0005': EFIBootEntry(name='Hard Drive', path='BBS(HD,,0x0)414d474f414d4e4fa5000000010000006f0057004400430020005700440042004e0043004500320035003000300050004e00430000000501090002000000007fff040002010c00d041030a0000000001010600021f03120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63800310032003400370032003200340030003100350037002000200020002000200020002000200000007fff0400414d424f414d4e4f9b000000010000006300200055005300420020004400490053004b00200032002e003000200050004d004100500000000501090002000000007fff040002010c00d041030a000000000101060000140305060001007fff040001043600ef47642dc93ba041ac194d51d01b4ce6300037003000310039003700360032004600380042003200440045003000380000007fff0400414d424f'), '0009': EFIBootEntry(name='UEFI: USB DISK 2.0 PMAP', path='PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,2fdf80be-e145-40c5-aa51-61a53ab5282e,0xc21d04,0x2838)AMBO'), '000A': EFIBootEntry(name='UEFI: WDC WDBNCE2500PNC', path='PciRoot(0x0)/Pci(0x1f,0x2)/Sata(4,65535,0)/HD(1,GPT,502aff24-45b2-456a-a358-7eafc504c6f4,0x800,0x219800)AMBO')})
installing grub to target=/target devices=['/dev/sda1'] [replace_defaults=True]
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'dpkg', '--print-architecture'] with allowed return codes [0] (capture=True)
updated /target/etc/default/grub to set: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Using grub install command: /usr/lib/grub/grub-multi-install
Grub install cmds:
[['efibootmgr', '-v'], ['dpkg-reconfigure', 'grub-efi-amd64'], ['update-grub'], ['/usr/lib/grub/grub-multi-install'], ['efibootmgr', '-v']]
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'dpkg-reconfigure', 'grub-efi-amd64'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'update-grub'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', '/usr/lib/grub/grub-multi-install'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.004
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
Skipped reordering of UEFI boot methods.
Currently booted UEFI loader might no longer boot.
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.008
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: SUCCESS: installing grub to target devices
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: SUCCESS: configuring target system bootloader
start: cmd-install/stage-curthooks/builtin/cmd-curthooks/copy-cdrom-metadata: copying metadata from /cdrom
copying media-info into target
/cdrom/.disk/ubuntu_dist_channel not found, skipping
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/copy-cdrom-metadata: SUCCESS: copying metadata from /cdrom
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: SUCCESS: curtin command curthooks
{'current': '0009', 'timeout': '1 seconds', 'order': '000A,0009,0005'}
{'current': '0009', 'timeout': '1 seconds', 'order': '000A,0009,0005'}
{'current': '0009', 'timeout': '1 seconds', 'order': '0000,000A,0009,0005'}
curtin: Installation finished.
I've been struggling with this device for multiple days at this point. I've installed earlier versions of Ubuntu desktop on laptops without issue several times before (currently I'm posting this from 24.04), but this particular hardware just hates me or something.
Xubuntu 26.04 - the display brightness slider in the upper panel area is not working anymore, moving it just has no effect.
I added this command line:
xrandr --output eDP1 --brightness 0.7
to the Session and Startup panel - autostart
but obviously the power manager seems to overrule this entry - it also shows no effect other than reducing the brightness after startup for about one second and then going up to 100 % again.
Does anyone has an advice for this issue? Thanks!
After installing Ubuntu 26.04 in Asus Expertbook Ultra (X7 385H) why getting problem in some function keys. Like brightness increase / decrease, fingerprint option not showing in settings, and IR facial recognition login option is not working.
im having a really annoying problem on my dell latitude e7450 (intel graphics) where Ubuntu won't turn the screen back on after sleep. the laptop wakes up, but the screen just stays totally black.
I'm on the latest version of Ubuntu and I'm using Wayland. (just to be clear, I want to stick with Wayland and I haven't tried xorg at all for this).
Here's a list of what I've tried so far using Kate to edit the config files:
I tried fixing the Intel power-saving stuff:
I added i915.enable_dc=0 and i915.enable_psr=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.
Forced deep sleep:
I also added mem_sleep_default=deep to the grub cmdline to make sure it's actually going into a real sleep state.
Enabled early KMS for the graphics driver:
I added i915 to the bottom of my /etc/initramfs-tools/modules file so the driver loads early.
After doing all that, i ran sudo update-grub and sudo update-initramfs -u and rebooted.
Even after updating Ubuntu to the latest version and applying all these fixes, it still doesn't fix the screen wake up problem. Does anyone know what else I can try to fix this black screen issue on Wayland?
Date generated: 2026-07-22 20:42:03
Hardware Information:
Hardware Model: Dell Inc. Latitude E7450
Memory: 16.0 GiB
Processor: Intel Core i7-5600U × 4
Graphics: Intel HD Graphics 5500 (BDW GT2)
Disk Capacity: 512.1 GB
Software Information:
Firmware Version: A24
OS: Ubuntu 26.04
OS Build: (null)
OS Type: 64-bit
GNOME Version: 50
Windowing System: Wayland
Kernel Version: Linux 7.0.0-28-generic
Note: This is definitely an Ubuntu specific software issue. The laptop wakes from sleep perfectly fine on other operating systems like MX Linux,Fedora, EndeavourOS so the hardware and screen are fully functional.
After a routine fwupd firmware update my laptop's built-in screen became very dim, even at "100%" brightness. An external monitor on the same machine looks completely normal.
Laptop: Dell Latitude 5430, Intel Iris Xe (Alder Lake, i915), internal eDP panel (AU Optronics).
OS: Ubuntu 24.04, GNOME.
Trigger: fwupd auto-flashed the Dell system BIOS from 1.36.0 to 1.39.1 (check with fwupdmgr get-history). The screen was fine before that.
What I already ruled out (none of these help):
Not a kernel regression — dim on every kernel I tried; the panel is only bright in recovery mode / with nomodeset (i.e. when i915 is not driving it).
Not gamma/ICC — xrandr Brightness 1.0, Gamma 1.0, no VCGT in the ICC profile.
Not a software brightness slider — /sys/class/backlight/intel_backlight reports brightness == actual_brightness == max_brightness (1023), yet the panel is dim.
Brightness keys only make it dimmer, never brighter.
Downgrading the BIOS is blocked: LVFS only offers 1.39.1, so fwupdmgr / GNOME Firmware cannot roll back.
How do I get the panel bright again without a BIOS downgrade?
I've been trying to get my UB600 Bluetooth dongle to work, however it seems that it's not compatible out of the box. In fact, there's only 1 place with a solution how to get it to work however it seems the explanation on how to do it goes over my head. I've tried using what they gave me in konsole but some things just error and I can't seem to get around that. The fix I've been attempting is this. The issue I'm having is, it detects the Bluetooth dongle, but the computer is then unable to detect any Bluetooth devices at all. The lsusb is exactly as shown on that link as is the journalctl.
Results of lsusb | grep -i 'tp-link':
Bus 001 Device 012: ID 37ad:0600 TP-Link Bluetooth USB Adapter
Results of journalctl:
usb 1-1: new full-speed USB device number 12 using xhci_hcd
usb 1-1: New USB device found, idVendor=37ad, idProduct=0600, bcdDevice= 2.00
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: TP-Link Bluetooth USB Adapter
usb 1-1: Manufacturer:
usb 1-1: SerialNumber: 18694530DB8B
Bluetooth: MGMT ver 1.23
I ran sudo dmesg | grep -i bluetooth and got this:
server@server-z87hd3:~$ sudo dmesg | grep -i bluetooth
[sudo] password for server:
[647887.635955] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[647887.709668] Bluetooth: MGMT ver 1.23
[648046.220743] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648046.221733] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648046.222744] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648046.222748] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648046.224331] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648046.224378] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648046.376751] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648046.443866] Bluetooth: MGMT ver 1.23
[648062.029928] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648062.105001] Bluetooth: MGMT ver 1.23
[648220.950989] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648220.951983] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648220.952966] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648220.952969] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648220.953197] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648220.953223] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648221.105982] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648221.173128] Bluetooth: MGMT ver 1.23
[648256.225222] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648256.298247] Bluetooth: MGMT ver 1.23
[649742.374342] Bluetooth: MGMT ver 1.23
[682771.713073] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[682771.785356] Bluetooth: MGMT ver 1.23
Is there any chance somebody could explain to me like I'm a 5 year old how to apply that patch, or better yet, create a solution for me? I am running Kubuntu 26.04 on kernel 7.0.0-27-27.
Edit: Following "david" in the comments advice results.
server@server-z87hd3:~$ sudo apt install bluetooth bluez -y
[sudo: authenticate] Password:
bluez is already the newest version (5.85-4ubuntu0.1).
bluez set to manually installed.
Installing:
bluetooth
Suggested packages:
bluez-meshd
Summary:
Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 3
Download size: 6,600 B
Space needed: 36.9 kB / 180 GB available
Get:1 http://archive.ubuntu.com/ubuntu resolute-updates/universe amd64 bluetooth all 5.85-4ubuntu0.1 [6,600 B]
Fetched 6,600 B in 0s (121 kB/s)
Selecting previously unselected package bluetooth.
(Reading database… 268329 files and directories currently installed.)
Preparing to unpack …/bluetooth_5.85-4ubuntu0.1_all.deb…
Unpacking bluetooth (5.85-4ubuntu0.1)…
Setting up bluetooth (5.85-4ubuntu0.1)…
server@server-z87hd3:~$ sudo systemctl start bluetooth
server@server-z87hd3:~$ sudo systemctl enable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable bluetooth
server@server-z87hd3:~$ bluetoothctl show | grep "Powered"
Powered: yes
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 18:69:45:30:DB:8B Discovering: yes
[bluetoothctl]> power on#
Invalid argument on#
[bluetoothctl]> power on
Changing power on succeeded
[bluetoothctl]> agent on
Agent is already registered
[bluetoothctl]> default-agent
Default agent request successful
[bluetoothctl]> discoverable on
hci1 new_settings: powered connectable bondable ssp br/edr le secure-conn ll-privacy
[CHG] Controller 18:69:45:30:DB:8B Connectable: yes
hci1 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn ll-privacy
Changing discoverable on succeeded
[CHG] Controller 18:69:45:30:DB:8B Discoverable: yes
[bluetoothctl]> pairable on
Changing pairable on succeeded
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[bluetoothctl]>
I have disabled Secure Boot and run Bluetoothctl show:
server@server-z87hd3:~$ bluetoothctl show
Controller 18:69:45:30:DB:8B (public)
Manufacturer: 0x005d (93)
Version: 0x0a (10)
Name: server-z87hd3 #2
Alias: server-z87hd3 #2
Class: 0x006c0104 (7078148)
Powered: yes
PowerState: on
Discoverable: yes
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Client (0000112e-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (185f3df4-3268-4e3f-9fca-d4d5059915bd)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0555
Discovering: yes
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
SupportedCapabilities.MinTxPower: 0xffffffa6 (-90)
SupportedCapabilities.MaxTxPower: 0x0000 (0)
SupportedCapabilities.MaxAdvLen: 0xfb (251)
SupportedCapabilities.MaxScnRspLen: 0xfb (251)
SupportedFeatures: CanSetTxPower
SupportedFeatures: HardwareOffload
server@server-z87hd3:~$
This is what my results are like with my 5.0 dongle for comparison:
server@server-z87hd3:~$ bluetoothctl show
Controller 04:42:1A:54:A8:55 (public)
Manufacturer: 0x005d (93)
Version: 0x0a (10)
Name: server-z87hd3 #2
Alias: Asus 5.0
Class: 0x006c0104 (7078148)
Powered: yes
PowerState: on
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (185f3df4-3268-4e3f-9fca-d4d5059915bd)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Client (0000112e-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0555
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
SupportedCapabilities.MinTxPower: 0xffffffed (-19)
SupportedCapabilities.MaxTxPower: 0x0017 (23)
SupportedCapabilities.MaxAdvLen: 0xfb (251)
SupportedCapabilities.MaxScnRspLen: 0xfb (251)
SupportedFeatures: CanSetTxPower
SupportedFeatures: HardwareOffload
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[NEW] Media /org/bluez/hci0
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 04:42:1A:54:A8:55 Discovering: yes
[G522 Gaming Headset]> scan on
SetDiscoveryFilter success
Discovery started
[NEW] Device DE:B6:45:46:3D:0B Govee_H6076_3D0B
[NEW] Device FF:02:3C:C8:FA:46 BLE MF8470
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbd (-67)
[NEW] Device D0:C8:03:C6:6F:76 Govee_H61D5_6F76
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[NEW] Device 33:36:9F:00:1E:8B 33-36-9F-00-1E-8B
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device FF:02:3C:C8:FA:46 UUIDs: 19fe1b3d-4c5b-36b8-4043-c09ddc76099e
[NEW] Device DE:CD:2F:A8:FA:1A ET-2850 Series
[NEW] Device DC:6E:02:C6:22:87 Govee_H7078_2287
[NEW] Device DE:B6:41:06:19:77 Govee_H6022_1977
[NEW] Device C8:FF:77:CB:9B:32 VW1-UK-MAA1830A
[NEW] Device 13:12:70:E3:1C:0B 13-12-70-E3-1C-0B
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffab (-85)
[NEW] Device DC:B4:D9:F4:2A:42 DC-B4-D9-F4-2A-42
[NEW] Device D6:50:84:C6:55:17 Govee_H6099_5517
[NEW] Device 00:00:00:00:00:00 00-00-00-00-00-00
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffad (-83)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb3 (-77)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbf (-65)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbf (-65)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device D6:50:84:C6:55:17 AdvertisingFlags:
00 .
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffad (-83)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffb9 (-71)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device D6:50:84:C6:55:17 AdvertisingFlags:
06 .
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffaf (-81)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbf (-65)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa7 (-89)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffaf (-81)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbd (-67)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbf (-65)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffcd (-51)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbd (-67)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffab (-85)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffb1 (-79)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffc7 (-57)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[DEL] Device 13:12:70:E3:1C:0B 13-12-70-E3-1C-0B
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffad (-83)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffc7 (-57)
iw reg get with both dongles in:
server@server-z87hd3:~$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
server@server-z87hd3:~$
iw reg get with only 6.0
server@server-z87hd3:~$ iw reg get
global
country 00: DFS-UNSET
(755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
server@server-z87hd3:~$
iw reg get with neither:
server@server-z87hd3:~$ iw reg get
global
country 00: DFS-UNSET
(755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
server@server-z87hd3:~$
Edit: I should specify this dongle is a Bluetooth 6.0 dongle.
After upgrading from Ubuntu 25.10 to Ubuntu 26.04, randomly when starting Thunderbird the screen freezes and says kernel panic fatal exception in interrupt After restarting it continues to work, but randomly crashes again.
I am a newbie, so i am sorry in advance.
I have a very old scanner/printer. It worked on Windows 11 but every since i changed to ubundu (24.04.3), i cannot make it work.
I read that the transition package libpango1.0-0 was dropped in ubundu 24, and i dont know how to tell my scanner's drivers which depend on libpango1.0-0 that it's the same as libpango-1.0-0.
sudo apt-get install libpango1.0-0 did not work
scanner driver is from there https://asia.canon/en/support/0100551901?model=8330B, (there was also a source file , but i did not get any better results https://asia.canon/en/support/0100553202?model=8330B)
I tried to creat sym link as follows:
sudo
ln -s /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
/usr/lib/libpango1.0.so.0
and rebooted but it did not get any results , i think maybe because i dont know where install.sh is looking for dependencies . I nano-ed into install.sh, but i could not figure it out.
I appreciate ur help.
Best wishes
I'm looking for a reliable WhatsApp client that works well on Ubuntu 24.04 LTS. Ideally, the client should have:
How to set this up?
I have a new Logitech LIFT mouse and want to remap the thumb buttons. Now the buttons are assigned to go back one page in the web browser and forward, essentially as Alt+← and Alt+→, repsectively.
I want to remap them to Ctrl+Tab and Ctrl+Shift+Tab instead, so I can cycle through my tabs in the browser and other applications.
I have tried to map them with Solaar following THIS POST but it does not seem to recognize the thumb buttons there. It might also be that I do not understand how "Key Button Diversion" works.
I am unsure how to approach this further, and where to look.
I am running Ubuntu 24.10 and GNOME 47 (Wayland), but am still very new to this.
I am using Ubuntu 24.04 on an Asus laptop. I have both Windows 11 and Ubuntu. When I boot to Ubuntu I am getting the following error message:
EFI stub: WARNING: Failed to measure data for event 1: 0800000000000000b EFI stub
EFI stub: WARNING: Failed to measure data for event 1: 0800000000000000b EFI stub
It will stay there for 5 minutes and then I can boot, enter and get Ubuntu.
Can someone please tell me what is the issue that's causing this error and how to fix it, so that my boot and load Ubuntu much faster within seconds like my Windows 11.
I am trying to setup a raspberry pi to automatically copy SD card contents when it's inserted. I have managed to manually mount the cards fine using the mount command but usbmount has so far not worked at all.
At the moment I get this logged when I plug in a new device:
Apr 20 07:43:11 pi3testbench mtp-probe[839]: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.4"
Apr 20 07:43:11 pi3testbench mtp-probe[839]: bus: 1, device: 9 was not an MTP device
Apr 20 07:43:11 pi3testbench mtp-probe[840]: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.4"
Apr 20 07:43:11 pi3testbench mtp-probe[840]: bus: 1, device: 9 was not an MTP device
Apr 20 07:43:13 pi3testbench systemd-udevd[844]: sdc: Process '/usr/share/usbmount/usbmount add' failed with exit code 2.
Apr 20 07:43:13 pi3testbench usbmount[870]: /dev/sdd does not contain a filesystem or disklabel
Apr 20 07:43:13 pi3testbench systemd-udevd[846]: sdd: Process '/usr/share/usbmount/usbmount add' failed with exit code 1.
I can see the drive using lsblk fine:
pi@pi3testbench:~ $ lsblk -fp
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
/dev/sdb
└─/dev/sdb1 exfat 1.0
and as I said I can manually mount it and see the files.
(the following might be best as a second question but I'll put it here anyway)
I have previously seen usbmount run mount commands but the drive contents never appears. I tried running exactly the same mount commands and they work fine but they don't work when run by usbmount. This was alos with a "not an MTP device" error so perhaps this issue will be resolved when the MTP device issue is fixed.
I did try some suggestions I found such as modifying the /etc/usbmount/usbmount.conf and changing the options used for different file systems but that didn't help.
I have tried several different usb sticks and SD cards from different manufacturers but they all have the same problem.
What is the right way to update chrome on Ubuntu 20.04. My installation was with .deb file
I started getting update chrome warning messages on my chrome now. I do not want to uninstall and then reinstall to save my bookmarks and saved credentials.
is Google Sync a safe option for this?
I'm having a hard time trying to install on my Windows 10 the Grub bootloader. I downloaded the Ubuntu 18.04.4-desktop-amd64 ISO then ran the Ubuntu live session, then I ran this command sudo fdisk -l
SSD:
According to some internet articles I need to shrink my current SSD at least by 400 MB in order to format a boot partition as EFI FAT32 with a proper flag, and with that I will be able to install GRUB there. I have never used a Linux distro before.
Would someone here give me guidance me with proper commands in order to shrink my current drive which has 223 size, but only has a free space of 33 GIB? I only need a 400 MB boot partition.
Once I have installed Grub, finally I would be able to ran the grub configuration to finally fix the HPET of my motherboard firmware among other things.
With GRUB booting Windows, I can access to the configuration of the motherboard firmware allowed in Asrock, and with that force High Event Precision Timing to Disable Cause in a regular way my motherboard firmware is causing issues with HPET forced enable even if I disabled it, so with the GRUB there is a configuration to force HPET to disable, and force the Windows timer to 3.580 MHz.
I am using Ubuntu 14.04. I am a high school teacher, and I want a software to create a school timetable. Just to feed it with the class lessons and teacher, for the teacher section. To provide it with subjects being taught, to auto generate it.
Would be an alternative to Windows's aScTimeTables.
I am currently running Ubuntu 12.0.4 on a 64 bit machine. I have an AM335X development board. Along with the kit came the compressed kernel (linux 3,2), rootfs, u-boot, and ARM cross compiler (arm-2010q1).
I uncompressed everything to a sub folder (/home/brent/work).
I have added the following to my .bashrc file:
PATH=/home/brent/work/arm-2010q1/bin:$PATH
CROSS_COMPILE=arm-none-linux-gnueabi-
I have also installed the following:
sudo apt-get install ia32-libs
When I go to built u-boot I am doing the following (per instructions that came with the kit):
brent@brent~/work/u-boot$ sudo make distclean
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
brent@brent~/work/u-boot$ sudo make myd_am335x_lcd4.3_config
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
Configuring for myd_am335x_lcd4.3 - Board: myd_am335x, Options: DISPLAY_LCD43
brent@brent~/work/u-boot$ sudo make
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk
/bin/bash: line 3: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk.dep
/bin/bash: line 3: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-ld: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
arm-none-linux-gnueabi-gcc -DDO_DEPS_ONLY \
-g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -I/home/brent/CropVentures/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem -pipe -DCONFIG_ARM -D__ARM__ -march=armv5 -Wall -Wstrict-prototypes \
-o lib/asm-offsets.s lib/asm-offsets.c -c -S
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
make: *** [lib/asm-offsets.s] Error 127
I have verified the binary is located at /home/brent/work/arm-2010q1/bin
I am also not sure why I need to have sudo as part of the command? If I do not I get a permissions error.
Any help or information on what I am doing wrong would be greatly appreciated.