Even I clicked enter or control d it is not working I can’t navigate to login page

My laptop spontaneously updated itself to 26.04 LTS, after previously not being able to calculate the upgrade.

Now it asks for a login: david-ashton-Surface-Pro-4 login_

I never created one.Why is it doing this? Is there a default login? How do I circumvent it and/or get rid of it?

I used the Extract command on Rhythmbox; it took an appropriate amount of time for each of 21 tracks, with a status message near the bottom of the UI indicating that it was extracting 1, 2, etc. But now I cannot find the music, nor documentation on where Rhythmbox Extract puts the music.

In case it matters: I extracted to MP3, I have lame installed.

EDIT: Yes, I have looked through the folders in ~/Music/

EDIT 2: I have even done a search starting at / for words I think should be in extracted filenames, but didn't find anything that way either. However, the output of that is large, I was hoping someone could tell me where they're supposed to end up.

I installed Ubuntu into a partition that I created on my Lenovo, but now Windows doesn't work. It shows a blurred screen during login, and my laptop turns off after some time if it's not connected to a battery.

I am encountering the following error

ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x000000032) is beyond end of object (length 0x32) (20250807/exoparg2-393)

Jul 11 15:03:18 localhost kernel: ACPI Error: Aborting method _SB.WMID.WQBE due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-529)

on an HP Spectre X360. A perfectly working solution to resolve that problem is given by Luiz Agamez in Full system freeze on boot with charger connected — ACPI BIOS Error (AE_AML_BUFFER_LIMIT) on HP Victus 15-fb3xxx

When I follow the steps described:

Steps:

1. sudo acpidump -b and confirmed WQBZ lives in dsdt.dat.

2. iasl -d dsdt.dat to decompile.

3. In the WQBZ method, inserted an early Return (DerefOf (N012 [Arg0])) right after the local variable initialization, before the loops that overflow the buffer — effectively neutralizing the method (I don't need the HP WMI feature it feeds on Linux).

4. Recompiled with iasl -tc dsdt.dsl.

5. Packed into a cpio at kernel/firmware/acpi/dsdt.aml and loaded it via GRUB_EARLY_INITRD_LINUX_CUSTOM in /etc/default/grub.

Key gotcha: the first attempt didn't apply — the kernel found the table in initrd but kept using the original. The fix was incrementing the OEM Revision in the DefinitionBlock (from 0x01072009 to 0x01072010). The kernel silently ignores a DSDT override whose revision isn't higher than the firmware's. After bumping it, the override applied.

recompilation with iasl in step 4 gives several remarks, warnings and also, unfortunately, 8 errors.

Here is the output of step 2

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20251212
Copyright (c) 2000 - 2025 Intel Corporation

File appears to be binary: found 73192 non-ASCII characters, disassembling
Binary file appears to be a valid ACPI table, disassembling
Input file dsdt.dat, Length 0x33DD2 (212434) bytes
ACPI: DSDT 0x0000000000000000 033DD2 (v02 HPQOEM 827F     01072009 ACPI 20160422)
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
 Warning - Emitting ASL code "External (BNUM)"
           This is a conflicting declaration with some other declaration within the ASL code.
           This external declaration may need to be deleted in order to recompile the dsl file.

Disassembly completed
ASL Output:    dsdt.dsl - 1572703 bytes

In the file dsdt.dsl I have removed the line External (BNUM) and added the line mentioned in step 3 above. I get the following error output: https://drive.google.com/file/d/1VH26vi5cdDM-DdoHrgJpCS2mcF_HjDm1/view?usp=drive_link . Here is the dsdt.dsl file I am trying to recompile with iasl: https://drive.google.com/file/d/1i3mBBsEl2JrX5-kEBM0llZH7kVcO-1xw/view?usp=drive_link

Any help is greatly appreciated as the ACPI BIOS error is impactful! This is very well described in the abovementioned post of Luiz Agamez. In my specific case, the fan is not working properly, causing the battery to continuously overheat. Also, the system reboots after the set 10' of idle time, although the action set on idle time is sleep. And lastly, when shutting down, the system automatically restarts. The only way I can shut down the system is with the power on/off button. All of these I have lived with for the past three months, since my last kernel upgrade from 6.8.1 to 6.19.10.1, but especially the fan not working is an issue! And if there is a solution at hand, I find it a shame not to be able to implement it. Thanks again!

I will definitely also need help with Step 5 and incrementing the OEM revision, but I'll take the steps one by one :-)

In Ubuntu 26.04 there is a new version 4.8.33 and parameter -P Print last working directory does not work any more.

This is very inconvenient because when you exit Midnight Commander, you end up in the directory you were in when you started it. The expected behavior is that you should end up in the directory you were in most recently before exiting.

After a little bit of tweaking I managed to get my headphones recognized by the system.

Problem is that neither from apps nor from the testing I'm able to hear sounds.

I've tried every solution found online but they don't work.

The problem was happening indeed on Debian. On Windows 11 they just worked fine.

Thanks in advance for anyone who can help me.

so my

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 26.04 LTS"
NAME="Ubuntu"
VERSION_ID="26.04"
VERSION="26.04 LTS (Resolute Raccoon)"
VERSION_CODENAME=resolute
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=resolute
LOGO=ubuntu-logo

Has been running just fine, I did try using the pi it's HDD is connected to for other purpose recenly now when I try to open Ubuntu I get the desktop login When I click my username and put in my passwork after checking it is correct, goes away as if it right but then a black screen and comes back to the login again.

I did try CTRL+ALT+F4 goes into a terminal login but comes back and says incorrect password.

From a remote terminal I am able to ssh to the machine and login correctly.

Suggestions please.

Ardour is not seeing my Scarlette 2i2 in the input, so I am unable to record. A certain error message pops up when I open the app manually through the terminal (I run it on Linux).

Ardour: [ERROR]: AudioEngine: cannot load module "/snap/ardour-snap/33/usr/lib/ardour9/backends/libalsa_audiobackend.so" (libOSSlib.so: cannot open shared object file: No such file or directory)

I've copied the message into Gemini, and it told me that a certain file was broken. Gemini is telling me to download the "native binary version", but that version is older (5.0), and my files were created in a newer Ardour version. I also used to have the binary version, and it kept crashing on me, which is why I switched to the current one. I appreciate any help with this problem, and I apologize in advance if any of the technical wording is bad (I have little experience with Linux software)

I hate to ask but I've tried what seems like everything with no luck. I installed Ubuntu alongside my wife's Mint 19 but get blank screen unless it's in recovery mode. It doesn't seem to recognize my monitor but works fine when booting Mint. I've tried updating, installing drivers, cleaning files, dpkg repair, in root installed Nvidia driver 550, tried "sudo ubuntu-drivers install"(said all drivers installed already), looked for additional drivers in software updater and said there wasn't any, made sure secure boot is off, and just about everything I could find online. Just tried a reinstall and still nothing. I've been using Linux for 15 years with very few problems. I'm too old to be real techy but have been able to figure most things out eventually. Feel free to talk down to me. Any help would be appreciated. Lenovo ideacentre 310S Ubuntu 24.04.4 LTS Proccessor AMD A9-9425 RADEON R3, 5 COMPUTE CORES 2C+3G X 2 Firmware O2HKT64A Kernel: Linux 6.17.0-35-generic Let me know what else I'd need to show here. Thanks!

I am trying to connect a Sony DCR-TRV120 Digital8 camcorder (from ~2000) via its FireWire iLink DV In/Out interface to an Ubuntu PC to transfer old Digital8 / video Hi8 tape recorded video to my PC. I am receiving an Error: no camera exits message with each dvgrab attempt. I have be following several of the Ask Ubuntu Q&As, but have not been successful.

Here is some information on my setup:

• Sony DCR-TRV120 Digital8 camcorder, using digital tape

• Intel based desktop PC

• IEEE-1394 PCI (plug-in) card (Installed after Linux installation)

• Cable connections: FireWire 400 4-pin into camcorder; FireWire 400 6-pin into IEEE-1394 PCI card, installed in PC

• Ubuntu 24.04.4 LTS

Results of lspci | grep -E -i "firewire":

03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 \[Fire II(M)\] IEEE 1394 OHCI Controller (rev 80)

Results of lsmod | grep firewire:

firewire_ohci          65536  0
firewire_core         229376  1 firewire_ohci
crc_itu_t              12288  1 firewire_core

Results of sudo dvgrab -i card=0:

• NOTE: Tried card 0 & card 1

rom1394_0 warning: read failed: 0x0000fffff0000414
error reading config rom directory for node 0
Error: no camera exists

I have HP z book fury 15 G8, I installed Ubuntu 26.04 and updated the software, disabled secure boot, Nvidia graphics driver installed, Nvidia-smi gives me my card correctly, when I connect the HDMI the system shows me in the settings that I have a second monitor, and showing all it's info's but the external monitor not working and gives no HDMI connected..

I tried to install latest drivers and also tried to update the firmware, but did not fix my issue.

I have an HP Victus 15-fb3xxx (Ryzen 7 7445HS, RTX 3050 laptop, BIOS F.14) running Ubuntu 26.04 (kernel 7.0.0-27-generic). The system freezes completely (hard freeze, requires forced shutdown) consistently when booting with the charger connected, even without any heavy workload.

In journalctl -b -1 -p err from the boot right before the freeze, I consistently see this:

kernel: No irq handler for 1.55
kernel: No irq handler for 2.55
[...]
kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x000000032) is beyond end of object (length 0x32) (20251212/exoparg2-393)
kernel: ACPI Error: Aborting method \_SB.WMID.WQBZ due to previous error (AE_AML_BUFFER_LIMIT) (20251212/psparse-529)
kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error (AE_AML_BUFFER_LIMIT) (20251212/psparse-529)

WQBZ/WQBE appear to be HP-proprietary WMI methods related to temperature/power-mode reporting (also queried by the NVIDIA driver via PlatformRequestHandler, which in a separate log reports failed to get target temp from SBIOS).

I've already ruled out the WiFi driver (RTL8852BE-VT, rtw89_8852bte module) as the cause of this specific freeze — it had a separate, unrelated power-save-mode bug that I already fixed with rtw89_core.disable_ps_mode=1 via GRUB, and it no longer shows up in recent logs.

Concrete questions:

• Has anyone with an HP laptop (Victus, Omen, or similar) seen this exact AE_AML_BUFFER_LIMIT error on the WQBZ/WQBE methods, and correlated it with freezes specifically when the charger is connected/detected?
• Is there a kernel parameter or a way to blacklist the hp_wmi module that mitigates this without losing critical functionality (fan control, function keys)?
• Has HP fixed this ACPI table bug in any BIOS version newer than F.14 for this laptop line?

Happy to attach a full acpidump if that helps diagnose it further.

Update (July 10):

Some important corrections and new findings since posting:

• The charger is NOT the trigger. I initially correlated the freeze with the charger, but it also happens on battery, with no charger connected, after ~40 minutes of normal uptime. So the charger connection was a red herring — please disregard that part of the title.

• NVIDIA D3 power-state failure found. On one freeze I caught this on screen: nvidia 0000:01:00.0: Unable to change power state from D3hot to D0, device inaccessible (plus the same for snd_hda_intel and an nvidia-modeset HDMI-0 pixel clock error). I mitigated it with nvidia.NVreg_DynamicPowerManagement=0x00 in GRUB (confirmed Runtime D3 status: Disabled), but the freeze still occurs, so this was a symptom, not the root cause.

• The freeze leaves no trace in the local journal. journalctl -b -1 simply cuts off mid-activity with no error, oops, or panic — a silent hard hang. To capture it, I've set up netconsole / live journal streaming to a second machine over the network. Still waiting to catch a freeze with usable output.

• The ACPI AE_AML_BUFFER_LIMIT errors on WQBZ/WQBE remain present in every boot regardless of the mitigations above.

Current GRUB cmdline: rtw89_core.disable_ps_mode=1 rtw89_pci.disable_aspm_l1=1 rtw89_pci.disable_aspm_l1ss=1 pcie_aspm=off nvidia.NVreg_DynamicPowerManagement=0x00

Will update again once I capture the hang over netconsole and/or after testing noapic and a BIOS update to F.15.

Update 2 (July 10, later):

Caught a hard freeze with actual output on screen this time (previously it was a silent hang with nothing in the local journal). The screen showed:

kernel: nvidia 0000:01:00.0: Unable to change power state from D3hot to D0, device inaccessible kernel: snd_hda_intel 0000:01:00.1: Unable to change power state from D3hot to D0, device inaccessible nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device HDMI-0. kernel: BUG: unable to handle page fault for address: ffffcb14037700d0

So the D3hot→D0 resume failure I mentioned in Update 1 isn't just a cosmetic error — it culminates in a real kernel page fault (likely nvidia-modeset dereferencing an invalid pointer after the device dropped off the PCI bus), which is what causes the full hang.

Root cause of the gap: nvidia.NVreg_DynamicPowerManagement=0x00 (which I'd already set) only disables NVIDIA's own internal power management — it does NOT disable the kernel's generic PCI runtime power management, which is a separate control. Checking:

cat /sys/bus/pci/devices/0000:01:00.0/power/control

returned auto, meaning the kernel could still autosuspend the GPU independently of the NVIDIA driver setting.

Fix applied: forced it to on and made it persistent via udev:

echo on | sudo tee /sys/bus/pci/devices/0000:01:00.0/power/control

/etc/udev/rules.d/99-nvidia-no-pm.rules: SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{power/control}="on"

Currently monitoring to see if this closes the gap. Also using netconsole/live journal streaming to a second machine to catch any future freeze with full context, since local journalctl doesn't survive a hang this violent.

Update 3 (July 11):

Progress and new findings:

The freeze produces a real kernel page fault. After disabling runtime PM at the PCI level (echo on > /sys/bus/pci/devices/0000:01:00.0/power/control, made persistent via udev rule + systemd service), the freeze still occurred, and I caught this on screen before the black-screen hang:

nvidia 0000:01:00.0: Unable to change power state from D3hot to D0, device inaccessible snd_hda_intel 0000:01:00.1: Unable to change power state from D3hot to D0, device inaccessible nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device HDMI-0. BUG: unable to handle page fault for address: ffffcb14037700d0

So the failed D3hot->D0 transition leads to a kernel page fault. power/control was confirmed on at freeze time, so standard runtime PM wasn't the trigger — something else is still driving the GPU into D3.

Already in hybrid mode. prime-select query returns on-demand, so the hybrid configuration by itself does not prevent the freezes. HP Support has confirmed on their forums that Victus laptops aren't officially validated for Linux (GPU/audio/thermal only validated for Windows 11), consistent with the ACPI firmware bug being the root cause.

Currently testing noapic (boot logs show repeated No irq handler for X.55 messages, so interrupt routing via the broken ACPI tables seemed worth ruling out). Current cmdline:

rtw89_core.disable_ps_mode=1 rtw89_pci.disable_aspm_l1=1 rtw89_pci.disable_aspm_l1ss=1 pcie_aspm=off nvidia.NVreg_DynamicPowerManagement=0x00 noapic

Next isolated test, only if noapic proves insufficient, is fully disabling the dGPU via prime-select intel. The AE_AML_BUFFER_LIMIT / WQBZ/WQBE ACPI errors remain constant across every boot regardless of any mitigation.

Update (July 11) — root cause pinpointed in the ACPI method:

Captured the full AML failure via dmesg. The WQBZ method aborts on an off-by-one buffer access:

ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x32) is beyond end of object (length 0x32) (20251212/exoparg2-393) Initialized Local Variables for Method [WQBZ]: Local1: Integer 0x32 Local5: Integer 0x32 ACPI Error: Aborting method _SB.WMID.WQBZ due to previous error (AE_AML_BUFFER_LIMIT) ACPI Error: Aborting method _SB.WMID.WQBE due to previous error (AE_AML_BUFFER_LIMIT) hp_bioscfg: Returned error 0x3, "Invalid command value/Feature not supported"

The object length is 0x32 (50) and the method tries to index element 0x32 — one past the last valid index (0–49). A classic off-by-one in HP's AML bytecode. This is a firmware bug, not fixable via kernel parameters.

Things I've now ruled out as the freeze cause:

• WiFi driver (rtw89) — mitigated, no longer in logs.
• NVIDIA dGPU — freeze still happens with prime-select intel (dGPU fully off, nvidia-smi reports no device).
• External mouse/keyboard — they enumerate cleanly (Dell KB216, generic USB optical mouse), no i2c/usb errors tied to them.
• noapic — tested and removed; it introduced new amd_gpio / atkbd / i2c_designware controller timed out errors without fixing the hang.
• PCI runtime PM forced to on — freeze persists regardless.

Also note amdgpu 0000:06:00.0: Runtime PM not available — even the integrated AMD GPU can't do runtime PM here, consistent with the ACPI power subsystem being broken at the firmware level.

Current plan: attempt a BIOS update to F.15 (via HP's USB flash mechanism if supported, to avoid needing Windows), since the root cause is in firmware. If HP hasn't fixed the WQBZ off-by-one in F.15, the fallback is an ACPI table override (acpidump + iasl) patching the method. Will report back.

Update (July 11) — WORKAROUND APPLIED (pending real-world confirmation):

Since HP doesn't provide a Linux BIOS update path for this model (and BIOS updates on Victus laptops have a documented brick risk), I patched the broken method directly via a DSDT override loaded from initrd. No firmware flashing, fully reversible.

Steps:

1. sudo acpidump -b and confirmed WQBZ lives in dsdt.dat.
2. iasl -d dsdt.dat to decompile.
3. In the WQBZ method, inserted an early Return (DerefOf (N012 [Arg0])) right after the local variable initialization, before the loops that overflow the buffer — effectively neutralizing the method (I don't need the HP WMI feature it feeds on Linux).
4. Recompiled with iasl -tc dsdt.dsl.
5. Packed into a cpio at kernel/firmware/acpi/dsdt.aml and loaded it via GRUB_EARLY_INITRD_LINUX_CUSTOM in /etc/default/grub.

Key gotcha: the first attempt didn't apply — the kernel found the table in initrd but kept using the original. The fix was incrementing the OEM Revision in the DefinitionBlock (from 0x01072009 to 0x01072010). The kernel silently ignores a DSDT override whose revision isn't higher than the firmware's. After bumping it, the override applied.

Result: dmesg | grep AE_AML_BUFFER_LIMIT is now empty. WQBZ/WQBE no longer abort. Confirmed the patch survives initramfs regeneration (e.g. after prime-select), since the cpio is prepended independently.

NVIDIA is back in on-demand mode with the patch active. Now testing under the conditions that previously triggered the freeze (4K video, charging, sleep/resume) to confirm this actually eliminates the hangs and not just the log error. Will report back after a few days of uptime.

Update (July 11) — additional trigger found + note on HP Linux support:

After the DSDT patch eliminated the WQBZ freeze, the system was stable for general use. However, I hit a separate, more specific hang: it froze once while playing HD video on the external HDMI monitor. Notably, journalctl -b -1 was completely clean afterwards (silent hard hang, no ACPI error, no D3hot trace) — so this is a different mechanism from the WQBZ firmware bug, which remains fixed (AE_AML_BUFFER_LIMIT stays absent).

Since the HDMI port on this Victus is wired to the NVIDIA dGPU, HD video decode + HDMI output stresses the NVIDIA path specifically. Disabling Chrome's hardware acceleration (chrome://settings/system -> turn off "Use graphics acceleration when available") appears to prevent it — several HD videos have played without a freeze so far. This forces video decode off the NVIDIA GPU. Still confirming with longer uptime.

I also disabled system suspend entirely (systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target), because the NVIDIA D3hot->D0 resume failure would kill the external display on wake. On a hybrid NVIDIA laptop with this firmware, avoiding suspend proved more reliable than fighting the resume path.

Note for others considering this hardware on Linux: the root cause here is a firmware-level off-by-one in HP's own ACPI/WMI bytecode (WQBZ/WQBE), present verbatim across multiple HP models (another user confirmed the identical index on a Spectre X360). HP's official position is that Victus laptops are only validated for Windows, and there is no Linux BIOS update path — so fixing this requires decompiling and patching the DSDT by hand, which is out of reach for most users. The workarounds above make the machine fully usable on Linux, but it's worth being aware going in that this class of HP gaming laptop needs manual firmware-level intervention to run Linux reliably. Hopefully documenting the full fix here spares the next person the multi-hour debugging session.

I recently updated my Ubuntu Desktop PC from 24.04 to 26.04. I have a dual monitor setup, the primary screen in landscape and the secondary screen in portrait orientation. After turning on the PC, on the login screen, the user selection and password entry page appears on my secondary screen (which is in portrait orientation) in a landscape orientation.

I could handle it if the login screen was on the secondary (portrait) monitor in portrait orientation, but this is too much. Ideally I would have my login screen on my primary monitor in a landscape orientation. I had the same exact issue on Ubuntu 24.04, and I don't remember how I managed to fix it, but I did, and I can't figure it out now. I'm running Wayland across the board.

It simply freezes during installation and does not progress forward. I've tried different USB sticks, disabling Secure Boot, and nomodeset.

Reference image of where I'm stuck at:

and idk if this is helpful:

My Lenovo Yoga 9 14IRP8 often does not recognize stylus strokes from the Precision Pen 2 when drawing in (mainly vertical, but occasionally also horizontal) tablet/2-in-1 mode, as shown in the picture. I have a hard time to find the origin of this issue. It occurs in different desktop environments (KDE and GNOME) and different distributions (Fedora, Ubuntu 26.04, Ubuntu 24.04). The bugs only happen when my palm rests on the display, but persist when I disable the touchscreen via udev rule:

ACTION=="add|change", SUBSYSTEM=="input", ENV{ID_INPUT_TOUCHSCREEN}=="1", ENV{LIBINPUT_IGNORE_DEVICE}="1"

Kernel: 7.0.0-22-generic

libinput: 1.31.1

Running libinput debug-events reports ultra-short time windows where the pen is detected to be lifted and set back down. Note that the timespans seem too short for a human to lift the pen out of the proximity reach and set it back down, as illustrated by the following snippet:

event6   TABLET_TOOL_TIP              +11.969s      185.73*/103.15* tilt: -12.00 /9.00  pressure: 0.00* up
 event6   TABLET_TOOL_PROXIMITY        +11.971s     185.73 /103.15  tilt: -12.00 /9.00  pressure: 0.00  pen      ('AES Pen', 0x80a32bf2, id 0x846b) proximity-out
 event6   TABLET_TOOL_PROXIMITY        +12.064s     187.33*/104.03* tilt: -11.00*/3.00* pressure: 0.00* pen      ('AES Pen', 0x80a32bf2, id 0x846b) proximity-in    axes:pt btn:S
 event6   TABLET_TOOL_TIP              +12.066s     187.33 /104.03  tilt: -11.00 /3.00  pressure: 0.31* down

Does anyone have a similar issue? What is the most likely cause for this?

Stylus behavior in horizontal and vertical tablet mode:

This is a recent issue. It worked previously. I find that I cannot run any AppImage bundle on 22.04 LTS. I confirmed that libfuse2 is installed. But to ensure that is was installed correctly, I uninstalled and reinstalled it via apt-get.

When I attempt to execute the AppImage in Gnome, absolutely nothing happens and I get no error. But when I attempt to execute it via the command line, I get:

dlopen(): error loading libfuse.so.2

Has anyone else encountered and resolved this issue?

As a workaround, I did find that I could download the app (Balena Etcher) in .deb format. I did that, installed it and it worked fine. I still have no idea why the Etcher AppImage bundle is no longer running correctly. I found that Ubuntu has both fuse2 and fuse 3 installed on the machine and running the AppImage bundle for Balena Etcher results in the error above.

I've an extension composed by the following files:

and I'm wondering how can I install it. I'm using Ubuntu 20.04.

EDIT: I tried to install it by copying and pasting the js file into the terminal. Then I tried to search some tutorial about how to install js file extension, but all the results I got are about node.js.

Basically, I want to automate changing display settings manually in Gnome Settings. If I am not wrong, it seems that the settings is stored in ~/.config/monitors.xml. So, I guess I could create multiple of them and apply one via script, but how to apply that file?

I am using Wayland, and when I searched the web for a way to do it, the result was an old forum post that was just restarting gnome-shell. But, you cannot restart gnome-shell in Wayland.

I have recently been encountering an issue with lsusb and I suspect it is to do with libusb. Whenever I run it, I get the following error: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_get_port_number.

I have tried uninstalling and reinstalling usbutils and the error remains.

Any help is appreciated.

Cheers,

K

I've been using Ubuntu 20.04 for several days and then at one point when I tried to login I was met with a "Oh No! Something has gone wrong and the system can't recover. Please log out and try again." message and if I clicked it, it sent me back to the login screen. In addition to this screen I also had access to my terminal, I think because I have it setup to open on login. Rebooting did not help.

I'm a noob to linux so I'm going to list everything I tried even if some of it isn't relevant. Sorry for the long post.

The only "big" thing I remember doing before I logged out/ shutdown my computer before I started getting these messages was I installed this vim plugin to enable opencl syntax highlighting by git cloning it in ~/.vim/pack/plugins/start the syntax highlighting was working fine before I logged out. I was able to remove the ~/.vim/ and ~/.vimrc files from my home directory but it did not help.

Then I tried this solution by doing

sudo apt update && sudo apt dist-upgrade
sudo apt clean && sudo apt autoremove && sudo reboot

It worked without any problems but I still could not login.

I had installed rocm opencl previously by following this installation guide, and it was working fine, but I thought maybe this could be causing some problems for some reason, so I uninstalled it from the same guide. Some of the directories weren't removed because they had stuff in them so i manually removed the last few directories in /opt/rocm so now my /opt directory is empty. This still did not fix my problem.

From this post I found out that maybe logging in as a different user could work. So I created a new test user and logged in and it worked! I think this means that my problem is with my main user configuration and not with my system but idk. From this test user I su - main to my main account and tried to reinstall gnome following this post, because I read somewhere that this might help so first I did:

sudo dpkg-reconfigure gnome-shell

which still gave me the error message on my main user account when I tried logging in, so then I tried:

sudo apt remove gnome-shell
sudo apt install gnome-shell

This still did not fix my issue when I tried logging in with my main account but now when I log in with my test account the dock on the left side is hidden by default, and I can only access it with the windows key or by pressing activities in the top left. I made a test2 account to see what would happen and again the dock was hidden. I am currently writing this from my test2 account.

The next thing I was going to try was to remove configuration files in my main account and see what happens but I'm not sure what I should remove and how to do this safely and if this is even a good idea at all.

I am not opposed to backing up my files and reinstalling ubuntu because I have only been using it for a few days and I need to reinstall rocm opencl again either way. However, I would still like to know what happened and if there is a way to fix it so that this doesn't happen again (and if it does so I know how to fix it) when I would be more opposed to reinstalling ubuntu in the future.

Sorry for the long post, I really appreciate you taking the time to read it.

Edit: I decided to just create a new admin account and remove my old one and reconfigure everything. So far there have been no login issues or anything. I was also able to get the dock to appear again by doing: sudo apt install gnome-shell-extension-ubuntu-dock Thanks for all your help everyone I couldn't have done it without you!

I like to know is there any WhatsApp application for desktop or browser extension with video call ability in Ubuntu, i have tried this app and web base of WhatsApp that don't have call futures:

Thanks.

So I have multiple monitors to use, I know they can be used in mirror mode where they both essentially display the same thing, or multi monitor mode where they behave like two separate displays side by side.

Now, is there a way to have them act like one big continuous display? For example, can I have two 1920x1080 monitors connected as one big 3840x1080 display and basically be able to have windows spanning both of them?

Unfortunately, googling yields only results about normal multi monitor use.

The other day I decided I might try to make some music on Ubuntu 18.04. I have a synthesizer that can work on its own, but it can also send an receive MIDI, namely a Novation MiniNova.
So I downloaded LMMS from the Software Store, created a tune in it without the use of the keyboard. Up until this point, no problems.

Now, when I plugged in my MiniNova, I expected to just run a few commands and be done with it. How wrong could I be. LMMS didn't recognize my keyboard, neither did KMidiMon. I followed this guide by a bloke named Ted and followed every step closely up until the point where I had to run cat /proc/asound/cards to figure out what ALSA named my sound card. I used sox to generate a 440 Hz sine .wav file, then I typed aplay -D hw:1 test.wav and I heard the sine wave through my laptops speakers.
lsusb gave me the MiniNova in the list, but adding the verbose option told me that it Couldn't open the device, some information missing.which seems weird to me.

I did come across a weird little thing when I decided that it couldn't hurt to run LMMS through a terminal. When I did, I got the following result:

ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed: No such file or directory
cannot open MIDI-device: No such file or directory
Couldn't create MIDI-client, neither with ALSA nor with OSS. Will use dummy-MIDI-client.
Connection established.

Stream successfully created

MidiClientRaw: unhandled MIDI-event 176

MidiClientRaw: unhandled MIDI-event 176

MidiClientRaw: unhandled MIDI-event 176

The last three messages were after opening the project I had been working on.

If it's helpful, here are links to my results after typing:

• aplay -l
• cat /proc/asound/cards

Thanks in advance, WalrusGumboot

Im using Ubuntu 16.04.1
When I try to install some programs Im getting this error

Wine could not find a Gecko Package which is needed for applications embedding HTML to work properly. Wine can automatically download and install it for now.

When I click Install... It is trying to Download it... But at some point it is sticking always.

I also tried to install it from here https://wiki.winehq.org/Gecko I downloaded the .msi file But Wine is unable to install that msi file...

I also tried with

wine msiexec /i wine_gecko-2.47-x86_64.msi 

But getting this error -

fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:service:scmdatabase_autostart_services Auto-start service L"clr_optimization_v4.0.30319_32" failed to start: 1053
err:module:import_dll Library MSVCR100_CLR0400.dll (which is needed by L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscorsvw.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscorsvw.exe" failed, status c0000135
err:service:service_send_command service protocol error - failed to write pipe!
fixme:service:scmdatabase_autostart_services Auto-start service L"clr_optimization_v4.0.30319_64" failed to start: 1053

I also Tried copying the file to /usr/share/wine/gecko But When I try to install the program It is again saying Wine could not find a Gecko Package...

What can I do?

I want to set up a headless server and connect to it from a laptop (Windows). It is running Kubuntu 15.04 and I installed X11vnc by this description:

VNC/Servers - Have x11vnc start automatically via systemd in any environment (Vivid+)

After a reboot the service is enabled and active (I think?), but I can not connect from the laptop using UltraVNC.

Only when I run

x11vnc -auth guess -forever -loop -noxdamage -repeat -rfbauth /home/$USER/.vnc/passwd -rfbport 5900 -shared

in a terminal I can connect to the server with UltraVNC.

I don´t want to issue this command everytime I want to the server. I want to be able to connect to server after a reboot without doing anything at the server.

Any ideas what goes wrong?

I like the Sticky Notes very much, they are always on the desktop.

But I can't find it in Ubuntu since 12.04. Other programs like gnotes & Xjournal are not giving a feature to stay on the desktop.

So, is there any application similar to the old sticky notes in Ubuntu?

First of all, I'm aware a similar question for GNOME is asked here: "Switch off laptop backlight when locking screen".

Objective

I would like to turn off my screen on locking the session for power saving reasons.

Actual problem

Locking the screen on Kubuntu (KDE) inevitably triggers the screensaver as far as I can see. There's no screensaver option other than 'Blank screen' together with its background colour set to black that comes just close to my goal. It blanks the screen, but doesn't turn off the screen. Screen's backlight will still be on and not saving any power.

Current workaround

A workaround via a script + shortcut key is possible, however, it's just a workaround since it doesn't trigger on all ways to lock the session. Therefore, I think it should be possible to have it done more elegantly, for example by providing this option in KDE's configuration dialog of the screensaver.

The workaround I am now using is the following. A script that locks the screen and turns off the screen:

#!/bin/bash

qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock
xset dpms force standby

and let it run with a shortcut key via a custom menu entry. It works.

Here's why I consider it to be a workaround rather than a solution. It doesn't work for other ways to trigger the locking of the session.

My actual question(s)

Do I need to touching/patching KDE's source?

• If not what are my options?
• If so,
  • could someone point me to where I can get started?
  • what do you think is the recommended place in the GUI for configuration?

I'm using Kubuntu 12.04 and willing to upgrade to KDE 4.9 or waiting for the 12.10 release.

I want to verify that my cron job is executing and at what time. I believe there is a log for my sudo crontab -e jobs, but where?

I searched google and found recommendations to look in /var/log (in which I do not see anything with 'cron' in the name) and to edit the file /etc/syslog.conf which I also do not have.

I have recently added several new users, that I need for qmail. Now they appear in the box in the login screen and clutter it, and I have to scroll to find my user. How can I hide those users from the login box?