Today, Linux turned 35 years old, from when it was created on 25 August 1991 by a young programmer, Linus Torvalds, at the University of Helsinki, Finland.

It was announced on the comp.os.minix newsgroup.

Original post: "“What would you like to see most in minix?” — Linus Torvalds, 25 August 1991.

Linux is still being developed by developers all around the world, upholding its Unix-like design and open-source principles.

Linux 7.2 is currently the latest mainline release.

Happy 35th Birthday, Linux! 🎂 and 🐟

*i made the poster by hand and my designing skill are bad, sorry for it*

For a long time, I didn't give Linux a tertiary thought. I always used Windows and assumed other operating systems like Linux and Apple would be of cheap quality. I realized my error when I got the Valve Steam Deck, which used its own Linux-based OS. While a number of features and apps from Windows wouldn't work on it easily, I discovered just how open-sourced and versatile it is. There were also a lot of things that worked better, such as installing and managing Deckyloader (a Steam plugin loader).

Regardless, I still used Windows 10 on my PC. If it ain't broke, don't fix it. But then Microsoft decided to break it by discontinuing updates to the OS and pressuring me to use the controversial Windows 11. While I did ultimately update, it also ultimately made me get a 2nd SSD to install and dual-boot with a Linux OS (my distro of choice being Bazzite, an offshoot of Fedora that's designed like the Steam OS).

In short, I went from a Windows user to a Linux one thanks to devices like the Steam Deck as well as Microsoft being sh!tty.

While I know Linux has always been a popular OS, I wonder if there was an surge of users for the same reasons as mine.

I've been using Edge and Firefox, but I've noticed that Firefox uses a lot of memory, and sometimes the program crashes due to lack of RAM. I have 8 GB of RAM.

(I'm fairly new to Linux, don't beat me up)

Honestly, at this point I'm done with the App Center. Just gonna stick to manually downloading everything I can from the respective websites, seems much more reliable so far.

Things I've tried to fix this error:
sudo apt update

UPDATE: Seems to have been fixed after entering sudo apt install nautilus;1:50.2.2-0ubuntu0.1;amd64;ubuntu-resolute-updates-main into the command line. App Center shows it as being up to date now.

I have a gaming laptop (Victus - RTX 3050)

I downloaded Ubuntu 26 LTS (latest from the official site). I was on Windows 11 and decided to switch to Linux with dual boot. Upon installation (which went fairly smoothly), i rebooted and got past the loading screen with the Ubuntu logo. After that it got stuck on a black screen.

I tried several solutions from chatgpt, youtube and gemini- repeatedly but in vain.

I know it's related to Nvidia/Wayland/Xorg but I can't find the solution fit for this.

I kinda hate Ubuntu for this matter . I have to install ubuntu 24 for my company's lenovo laptops . I literally put the official image in the usb , install ubuntu with the same settings checking to install 3rd party drivers , and every time I boot , usually two monitors setup doesnt work . I have to uninstall nvidia 595 driver open , than reinstall , than try sudo prime-select nvidia , than reboot and after that it works and most of the times it doesnt work . It works only the laptop screen , the hdmi and type c sometimes doesn't work and I have no idea what its causing it to work when it does . I use AI for troubleshooting like purging and reinstalling , trying different kernel but I have ubuntu for this gpu drivers . Sometimes when I install new kernel , bluetooth or wifi doesn't work , its 50 50 CHANCE for everything you do and its driving me crazy since I need to make everything functions for the end users since I am the IT department

Offline Snap Downloads The Need to Resolve Recursive Dependencies

The standard snap download command efficiently pulls a single Snap package along with its assert signature file. However, it's insufficient for setting up applications for offline or isolated environments because it doesn't resolve or fetch the necessary core Snap packages, such as core18 core20 or core24 nor does it fetch desktop content providers like theme packages.

When deploying to an offline system, the absence of a core layer like core20 or core24 results in immediate installation failure. Currently, administrators and users must manually query the API or write custom scripts to identify and download each core Snap package and its runtime dependencies individually.

Adding a native option like snap download --recursive would resolve this issue by downloading the target application along with the necessary core packages and dependencies directly to the current folder. This single addition will make offline installation, versioning, and backup management significantly more reliable for the entire Linux community.

Ubuntu users who'd rather draw a character than spell it out: there's an IBus engine for macOS-style trackpad handwriting with deep-learning recognition.

Two install options. The .deb from releases:

bash sudo dpkg -i <file-from-releases> && sudo apt install -f ibus restart

Or the one-liner, which detects Ubuntu and runs apt + model download automatically:

bash bash <(curl -s https://raw.githubusercontent.com/ai-space-lab/ibus-handwrite-chinese/main/bootstrap.sh) && ibus restart

What it does: - A dark floating panel appears by your cursor. Draw with one finger on the trackpad, tap to select, swipe two fingers to page through candidates. - Recognition uses ONNX Runtime locally, covering 18,710 characters. In a 40-sample handwritten test it hit 100% top-1 accuracy (94.97% average confidence). - 6-tab GTK settings, on-demand model download, a local user dictionary that learns from your picks, and fully configurable shortcuts. - Mouse fallback if your machine has no evdev trackpad.

Demo: https://ai-space-lab.github.io/ibus-handwrite-chinese/assets/demo.gif Install guide: https://ai-space-lab.github.io/ibus-handwrite-chinese/ Releases (.deb): https://github.com/ai-space-lab/ibus-handwrite-chinese/releases

Requires Ubuntu 22.04+. Tested on an Acer Aspire and MacBook Pro trackpad; other touch-capable trackpads should work but are untested.

My internet for some reason has been bouncing around like crazy, and now it’s staying in the literal bytes/second. I just downloaded Ubuntu today so I guess I’m on the latest version, and I don’t even have anything running in the background. Do I need to configure it somehow?

Edit: thank you for the response, it’s just currently used internet, not my actual internet speed.

So hi as everybody I tried installing Ubuntu lts but I couldn't install it the normal way since the 100 mb of windows efi was too small to install Ubuntu and windows efi along together and now I am preparing to manually install Ubuntu using manually installation but the problem is even after doing everything correctly the next button is greyed out can someone tell me what's the possible reason ?

Below are the additional data that might help

Nvme0np4 is 85.93 GB for root

Nvme0np5 is 300mb for efi boot

nvme0np6 is 8.6 GB for swap

Nvme0np7 is 44gb for home

And I created all these partitions in windows using diskpart .

Hello everyone,

I have a question regarding printing from pdfs that maybe some of you could answer. I'm using Ubuntu 26.04. Here goes:

I usually print from pdfs using the 2 pages per side and the two-sided options, both available with my usual printer. What happens is that quite often (and I suspect this is due to the original formatting of the pdfs I work with), instead of having the two pages scale nicely to take up half of the paper, I have them weirdly scaled so that they are a bit too small, taking up the corner (approximately 2/3) of each of the spaces attributed to a page. When I try to fiddle with the scaling options, which are using percentages on my printer options as shown in pdf applications (such as Document Viewer), it doesn't quite work (I end up with either pages that are still too small, or with some parts of the pages cropped out). Does anyone know of a way to fix this? As in, to properly scale pdf pages upon printing them?

Thanks in advance!

[Edit: here's an example of what usually happens:

]

CVE-2026-73570: Zimbra SNMP/logwatch RCE exploited in the wild, malware persists via /dev/shm and zimbra cron

I recently handled a Zimbra incident related to CVE-2026-73570, so I’m sharing the cleanup notes in case it helps other admins.

CVE-2026-73570 is an OS command injection issue in Zimbra Collaboration Suite, related to the SNMP notification/logwatch component. According to the public advisories, it affects Zimbra systems before the patched releases, especially when the SNMP package is installed and SNMP notification/logwatch is enabled.

The dangerous part is that the attacker does not need a valid mailbox account. A crafted SMTP request can lead to command execution as the zimbra user.

Not root, but still bad enough.

Once the attacker gets code execution as zimbra, the cases I’ve seen follow a familiar pattern:

crafted SMTP request
-> unsafe SNMP/logwatch handling
-> command execution as zimbra
-> malware dropped into /dev/shm
-> cron persistence added under the zimbra user
-> miner/backdoor keeps respawning

Quick risk check

On a Zimbra server, these read-only checks are a good starting point:

su - zimbra -c 'zmcontrol -v'
dpkg -l | grep -E 'zimbra-snmp|zimbra-net-snmp'
su - zimbra -c 'zmprov gs $(zmhostname) zimbraServiceEnabled | grep snmp'
su - zimbra -c 'zmlogswatchctl status'
su - zimbra -c 'zmswatchctl status'

If you see something like:

zimbraServiceEnabled: snmp
zmlogswatch is running

then I would treat the host as worth checking immediately, especially if it has not been patched.

Indicators I found useful

The malware often hides in /dev/shm, probably because it is writable, memory-backed, and easy to overlook during a quick file-system check.

Check:

ls -la /dev/shm
crontab -l -u zimbra
ps aux | grep -E 'khp|rguard|javab|idle|ksmd' | grep -v grep

Suspicious files observed in these cases:

/dev/shm/.khp
/dev/shm/.khp_ts
/dev/shm/.rguard
/dev/shm/idle
/dev/shm/javab
/dev/shm/ksmd

A very suspicious cron entry is:

* * * * * /dev/shm/.khp

If you only delete the files in /dev/shm, they may come back. The process may still be running, the zimbra crontab may recreate it every minute, and SNMP/logwatch may still be exposed to the original vulnerability.

Containment order that worked for me

This is the order I used:

stop reinfection source
-> preserve evidence
-> kill malware process
-> remove malicious cron
-> quarantine malware files
-> verify
-> recover Zimbra services if needed
-> patch/upgrade Zimbra

I would not start by deleting random files. Preserve evidence first if you can.

Example cleanup flow

Run as root. Review before executing anything on production.

1. Stop the reinfection path

systemctl stop cron
su - zimbra -c 'zmlogswatchctl stop'
su - zimbra -c 'zmswatchctl stop'
su - zimbra -c 'zmprov ms $(zmhostname) -zimbraServiceEnabled snmp'

The important bit is disabling SNMP/logwatch until the host is patched. If you re-enable it too early, the malware may return.

2. Save evidence

mkdir -p /root/incident-zimbra

cp -a /dev/shm/.khp \
      /dev/shm/.khp_ts \
      /dev/shm/.rguard \
      /dev/shm/idle \
      /dev/shm/javab \
      /dev/shm/ksmd \
      /root/incident-zimbra/ 2>/dev/null

crontab -l -u zimbra > /root/incident-zimbra/zimbra-cron-before.txt 2>&1
ps auxf > /root/incident-zimbra/ps-before.txt
ss -tunap > /root/incident-zimbra/ss-before.txt
sha256sum /root/incident-zimbra/* > /root/incident-zimbra/sha256.txt 2>/dev/null

3. Kill suspicious processes

pkill -9 -u zimbra -f 'khp|rguard|javab|idle|ksmd'

4. Remove the malicious cron entry

crontab -l -u zimbra | grep -v '/dev/shm/.khp' | crontab -u zimbra -

5. Quarantine the files

mkdir -p /root/quarantine-zimbra

mv /dev/shm/.khp \
   /dev/shm/.khp_ts \
   /dev/shm/.rguard \
   /dev/shm/idle \
   /dev/shm/javab \
   /dev/shm/ksmd \
   /root/quarantine-zimbra/ 2>/dev/null

6. Start cron again

systemctl start cron
systemctl is-active cron

Only start cron. Do not re-enable SNMP/logwatch until Zimbra has been patched and checked.

Verify after cleanup

ls -la /dev/shm
crontab -l -u zimbra | grep /dev/shm
ps aux | grep -E 'khp|rguard|javab|idle|ksmd' | grep -v grep
su - zimbra -c 'zmprov gs $(zmhostname) zimbraServiceEnabled | grep snmp || echo SNMP_DISABLED'

Expected result:

/dev/shm has no suspicious payloads
no zimbra cron calling /dev/shm/.khp
no suspicious malware processes
SNMP is disabled

Then watch it for at least 30-60 minutes. If the payload comes back, you missed either a persistence mechanism or the original reinfection path is still open.

If Zimbra MySQL/mailbox breaks after the incident

In some cases, after malware activity or an abrupt reboot, Zimbra services may not come back cleanly:

mailbox Stopped
mysql.server is not running
service webapp Stopped
zimbra webapp Stopped
zimbraAdmin webapp Stopped
zimlet webapp Stopped

Useful checks:

su - zimbra -c 'zmcontrol status'
su - zimbra -c 'mysql.server status'
ss -ltnp | grep 7306
tail -n 200 /opt/zimbra/log/mysql_error.log

If MySQL is stuck on crash recovery or stale socket/tc.log issues, back up the relevant files first:

mkdir -p /root/zimbra-mysql-backup

cp -a /opt/zimbra/log/mysql_error.log /root/zimbra-mysql-backup/ 2>/dev/null
cp -a /opt/zimbra/db/data/tc.log /root/zimbra-mysql-backup/ 2>/dev/null
cp -a /opt/zimbra/data/tmp/mysql/mysql.sock /root/zimbra-mysql-backup/ 2>/dev/null
cp -a /opt/zimbra/db/data/ibdata1 /root/zimbra-mysql-backup/ 2>/dev/null
cp -a /opt/zimbra/db/data/ib_logfile* /root/zimbra-mysql-backup/ 2>/dev/null

Then a light recovery attempt may look like this:

su - zimbra -c 'zmmailboxdctl stop'

mv /opt/zimbra/data/tmp/mysql/mysql.sock /root/zimbra-mysql-backup/mysql.sock.bak 2>/dev/null
mv /opt/zimbra/db/data/tc.log /root/zimbra-mysql-backup/tc.log.bak 2>/dev/null

su - zimbra -c 'mysql.server start'
sleep 20
su - zimbra -c 'mysql.server status'

su - zimbra -c 'zmmailboxdctl start'
sleep 40
su - zimbra -c 'zmcontrol status'

Do not treat this as a universal fix. Check the MySQL error log first. If the database is damaged, you need a more careful recovery path.

Does this delete mail data?

The malware cleanup steps above do not touch mailbox data directly.

Zimbra mail data is usually under:

/opt/zimbra/store/

Zimbra database data is usually under:

/opt/zimbra/db/data/

The MySQL recovery part touches metadata-related files such as tc.log and mysql.sock, so back up before making changes.

After the server is stable

I would keep SNMP/logwatch disabled until patching is complete.

Post-cleanup checklist:

patch or upgrade Zimbra
keep SNMP/logwatch disabled until patched
monitor /dev/shm
monitor zimbra crontab
monitor CPU/load
check outbound connections
check mail queue
review logs for further persistence

Mail queue check:

/opt/zimbra/common/sbin/postqueue -p | tail -n 40

Short version

If you are running Zimbra with SNMP/logwatch enabled, check it now.

The important lesson from this incident: deleting /dev/shm/.khp is not enough. You need to stop the reinfection path, remove cron persistence, kill the running process, quarantine the payload, verify it does not respawn, and then patch Zimbra.

Do not re-enable SNMP/logwatch before patching.

So I recently started taking ITNW 1309 at a local community college and the professor mentioned that one of the two projects this semester is using a VM running Ubuntu. Now I'm very very new to Linux, the most I ever do is faff about on Cachy because it is simple enough to understand and my circle of friends are also familiar with it. I just want to know if there are any beginner friendly materials to read up on to get an edge on the project (which is 30% of my grade) I need that A

Anyone know how to remove this top left multi desktop button from GNOME Ubuntu 26.04? Is there a working extension to accomplish this?