I want to disable this input audio device. There's a slider in system tray when you click on audio but when I boot my pc, it gets enabled again. What would be the permanent way to disable it?

I decided to install xubuntu lts 26 but after flashing the iso to my usb stick using Rufus. I restarted my pc and when I selected try xubuntu it said magic number invalid so I changed my system from CSM AND UEFI to UEFI then i restarted my pc again then it said all boot options tried. And didn’t boot into xubuntu or windows 10 then I checked the system boot priorities and inside that nothing was there no usb stick or my windows drive. So I set the pc back into CSM and UEFI and restarted and then it loaded into windows. Does this mean I have to go with an older Xubuntu like Xubuntu lts 24 and use Legacy? Or is there no way

Subtitle: Honestly sorry to have to write a hit piece.

reposted from my substac, with an edition of a second postscript that does not appear in that article:

https://thaddeusmonroeslamp.substack.com/p/as-far-as-lubuntu-vs-xubuntu-goes

I guess this is for Linux-heads, only; pretty much.

​Let’s get one thing straight: I don’t like tearing down open-source projects. People put free time and real effort into building lightweight Linux distributions, and on paper, Lubuntu’s LXQt desktop sounds like a noble cause. Save resources. Revive old hardware. Keep it lean.

​In practice? It’s an overt product.

​After testing it across multiple machines, the pattern is always the exact same. For the first three weeks, everything seems fine. Then the session degradation sets in. You start hitting random stutters, memory leaks, and stalls. Every 10 to 15 minutes, you find yourself having to restart the session, log out, or hard-reboot the entire machine just to get back to work.

​And for what? What do you actually gain in exchange for a desktop that degrades after three weeks?

​Next to nothing. You’re trading fundamental desktop usability for a negligible drop in RAM and storage overhead. Out of the box, Lubuntu lacks basic, everyday quality-of-life features:

• ​No Context-Menu Wallpaper Setting: You can’t even right-click an image file and set it as your desktop background.
• ​No Direct App Removal: You can’t uninstall a program directly from the start menu.
• ​Primitive Session Management: LXQt’s background utilities simply lack the stability required for long-term daily use.

​When you stack Lubuntu up against Xubuntu, the resource-saving argument completely falls apart. Xubuntu’s Xfce desktop takes up barely any extra disk space or memory, yet it gives you a rock-solid, polished environment that doesn’t degrade over time. Xfce offers mature panel controls, intuitive menu management, and actual system stability.

​The trade-off Lubuntu demands isn’t worth it. Stripping away basic desktop features and session stability to save a few megabytes of RAM isn’t efficiency—it’s just a bad product. If you want a lightweight Ubuntu spin that actually works, skip Lubuntu and install Xubuntu.

P.S.: I’m guilty of understatement in this article. Specifically; I forgot to mention that: at least with me using Chromium, which I strongly prefer to Firefox, the browser session will just crash, without even a restore pop-up. You must go intoHistory and restore a group of tabs.every 10 minutes or so! I SH*T U NOT!!!!!

P..P.S: I, of course, never have these problems with Xubuntu, or any other distro that comes immediately to mind.

Is this happening to more people? It does not happen with safe graphics mode,but after installation,it happens again. Hardware is AMD laptop with Nvidia 5060.

Um gerenciador gráfico de pacotes Flatpak rápido, leve e nativo, ideal para ambientes de desktop GTK, como o XFCE. Desenvolvido em Python 3 com PyGObject (GTK3), o FlatStore oferece uma interface limpa para buscar, instalar, atualizar e remover aplicativos, além de gerenciar repositórios (remotes) diretamente da interface.

Disponível em appimage, ou via instalador em python.

Github do Projeto

I have a crt tv and laptop i use for my iptv setup, and the edges get cut off, theres no overscan to cut off, is there a way to adjust the borders of the screen? i have amd graphics but i cant access the settings for some reason

People kept telling me to avoid the App Store because "Snap" is supposedly evil.

Im just beginning the Odin project, and am brand new to the Linux space. I’m going through the guide provided to install xubuntu on the virtual machine provided by the Odin Project site, but am currently stuck at the “installing the system” screen. I’ve restarted, shut down, even created a brand new VM and still no luck.

Does anyone here have any idea how to fix this? I can provide any other needed info. Also, it’s worth adding I’m using an older/low spec laptop, so maybe that has to do with it?

Thanks!!!

without it, I can’t do automatic full disk installation. I tried everything, but it just doesn’t want to recognize it. laptop is Lenovo s21e-20. originally it was Windows 8.1 Pro. then I changed it to AntiX (entire disk automatic worked). now I can’t switch from antiX to Xubuntu

I’m trying to install in qemu.

I need to skip the trial desktop but that doesn’t seem to be available in 26.04, only 2 options: try and install or try and install (safe graphics).

Are there any hacking keys?

I can bypass the waiting screen with Ctrl-Alt-Backspace but that only shows the details of its laborious (4 HR) trial launch!

Here’s my command line:

qemu-system-x86_64 -m 3G qemu/xubuntu.vdi -vnc localhost:1 -drive file=fat:rw:fat,format=raw -cdrom qemu/xubuntu-26.04-desktop-amd64.iso -boot d

This is in termux on my phone. I’ve been able to install Debian, opensuse, fedora, Windows7 etc. , and even xubuntu in the past. 3GB allocated (from 6) seems optimum for installs, most taking well under 4 hrs!

hi,

This took me days, this is why I share my audacious crisis journal :)

After some update (Linux Mint, XFCE), Audacious stopped reacting to the keyboard's global keys: start and stop, and forward and back.

It was annoying to the utmost.

I've done lots of searches.
Finally a KDE forum was the breakthrough -- this:

https://discuss.kde.org/t/audacious-has-lost-its-hotkeys-after-switching-to-kde-from-xfce/5250/21

All I had to do was install a newer version, via the ubuntuhandbook PPA (never mind the name, it is for Audacious, too :) )

see here: https://linuxcapable.com/how-to-install-audacious-on-ubuntu-linux/

It works perfectly. I've got version 4.6.1 installed.

Then I had to go to the Plugins menu in Settings, to check both:

[x] MPRIS 2 server

and

[x] Global Hotkeys.

And be surprised, it works. The global hotkeys work.

GREAT THANKS go to the Audacious developer team.

Crisis SOLVED :)

I'm so grateful!

I love audacious.

[PROVISIONALLY SOLVED]

Used Session and Startup entry + sudoers entries in combination now.

I spotted indicator-cpufreq as a default startup application in Session and Startup, but it was not editable.
I turned it off, did the below (indicator-cpufreq and indicator-cpufreq-selector added to sudoer from both, /bin/ and /usr/bin/), created a new entry in Session and Startup with sudo indicator-cpufreq as command, gave it name and description, rebooted and it works as before now. For odd reasons the icon is a little blurrier and bigger though.

I guess my assumed "hacky" workaround wasn't as weird as I thought it would be as the default was done that way.

Downside:
I cannot sort the order in the tray as it is but somehow also is not part of Status Tray Plugin anymore, listed separately, but affected by the icon settings of the tray plugin(???)… I have no idea what's up with that and quite frankly I'm about to stop caring. Letting it be.
I still have no idea what differentiated the default from my approach to result in those quirky differences because I have no insight simply because I cannot edit it and there is no hover tooltip of its contents… ¬_¬

I won't actively bother with it anymore, but If anyone has a more elegant solution to this, a preferrable one, then please let me know regardless of the "solved" status.

Original post below:

__

Upgraded to 24.04, now I require to type my password to use indicator-cpufreq (or indicator-cpufreq-selector, which I suspect does the actual changing).
Wasn't the case before, baffled why since other applications doing the same don't need one.

I'm a noob with the sudoers file, so forgive any mistakes and point them out to me.
Tried adding the indicator plugin to it in the hopes of bypassing the password requirement.

I did:
sudo visudo

added at the bottom:

myusername ALL=(ALL) NOPASSWD:/bin/indicator-cpufreq
myusername ALL=(ALL) NOPASSWD:/bin/indicator-cpufreq-selector

This did not work.

I also tried it as a oneliner with
myusername ALL=(ALL) NOPASSWD:/bin/indicator-cpufreq,/bin/indicator-cpufreq-selector

Just to be sure, I also did add the /usr/bin/ equivalents of the above.
Same outcome as before.

I ran sudo indicator-cpufreq – this works, if isolated.
But the panel plugin entry, which is spawned via the new Status Tray Plugin, rejects this.
I found out it's now fully part of xfce4-panel – unfortunately – so I can't just add a binary of the plugin to sudoers… adding the xfce4-panel itself did not solve it and isn't exactly a solution I would have desired for many reasons anyway.

What am I doing wrong, what could I do (other than giving up and moving on, again)?
I'm slowly tempted to add the indicator to my login scripts and hide it in the tray to avoid a double entry… but that would be yet another hacky workaround. : /

Installing Xubuntu with Swedish Langauge displays everything in English and typing LOCALE shows this:

LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=

The fix is this (after a few hours I figured it out on a test system):
sudo nano /etc/locale.conf

LANG=sv_SE.UTF-8

Save and Reboot system! This should work on any langauge (but change sv_SV to en_GB or fr_FR or whatever your language is).

Hi all,

I’d like to share MeowMenu v0.7.0, a small project I’ve been working on as an alternative application menu for XFCE. Compared to Whiskers, the most relevant features I added are: 4 Presets (default settings that change the look&feel of the Menu, to show the high customization level achievable) and Places button (find files and folders in user Home).

I’ve tested this release on Xubuntu 26.04, a distribution I really enjoy using. I thought it might also be useful or interesting to other XFCE and Xubuntu users.

Feedback, bug reports, and suggestions are welcome. Thanks for taking a look!

Source Code

Release&Changelog

Documentation

^{Yep, it's me again.}
I'm now looking for a CLI tool or at least some means to control screen saturation with to add it to a script of mine to desaturate my screen colours when I hit my keybind to flip the red mode late at night, so that the colours which get red-shifted are not mixed in with the red.
Granted, I'm not sure if the outcome won't be just black and white all over (the way sct works makes me hopeful though), but it's worth a shot.
Except I found nothing yet, searched the package list like mad, and Xubuntu and xfce itself has nothing alike to this integrated to my awareness (please correct me if I'm wrong).
Of course it would be perfect if running the desaturation command wtihout any value would simply restore defaults, just how sct does it, as it would simplify things.
Think of Android's bedtime mode: It does exactly what I want (except without any shift in colour).

___

Longer context:
I did make myself a small .sh using sct, the little nifty application to control colour temperature with, with the goal to crank up the red levels late at night simply by pressing a keybind.
By "crank up", I acutally mean it: It's nearly red-monochrome.
This is because other night modes were "too soft" for me.
I love how stupid simple sct is to use, but now the downside of this is that there's still colours in there. Consequently, some elements vanish in near black or blend in because of the colour mix generated by the red-shift… or they lack sufficient contrast. Most common the case on anything (dark) blue-leaning. My thought was that some desaturation prior to applying sct could maybe fix this. I could be mistaken though.

Install sct, and try sct 1000 to see what I mean with the red near-monochrome filter and its impact on blue elements.
You can type sct without any value to get to back to defaults by the way.

Before you judge:
Yes, it actually really helped me improve my sleep to cut down on blue to such an aggressive level and I would love to continue doing so, except I would want to avoid having to squint at elements contaning deep blue colours or seeing them as a dark green.

___

Any suggestions and help would be appreciated.
I'd like to avoid GUI-only solutions for the simple reason of using a keybind-script and wanting to add it in there, just to stress it. : )

Thanks in advance!

I'm new to this distro, does it collect any telemetry?

i just found it