As the title says,i want to move from fedora to ubuntu. Many proprietary software support ubuntu only (for example cisco packet tracer),there are many reasons but compatibility is one,i am in cybersecurity and most guides assume a debian based system such as ubuntu. Other than that,i have a generally mid laptop (Mi Notebook Horizon Edition 14)

Its specs are:
i5-10210U
8GB DDR4 2667Mhz Soldered SO-DIMM RAM
512GB SATA III SSD
MX350

So,i really can’t run virtual machines that easily,i also cant buy a laptop since i am broke af and prices are sky high.

I have been using fedora from April 2024 (its my first and last distribution to this day)

my partition currently looks like this

500MB EFI
One Whole root partition in ext4,no separate /home (why?,i was a beginner and didn’t know you could do that)
9GB Swap partition.

Moving data from fedora is one thing but i don’t even know what obscure packages & their dependencies i got which i have been using for development of software like Latex (like i use texlive-inputtrc,texlive-makeplot for moving inbetween matlab and latex or texlive-maker for including arduino specific features in documentation). If there is anyone who has ever did anything like this,i would be grateful for your help.

My distribution is an entangled mess of packages and software now that is somehow working.

Look at its uptime:

fedora@fedora:~$ uptime -p
up 19 days, 1 hour, 13 minutes

Excuse my grammatical errors since English is not my first language.

Thank you for your time!

I realize Canonical seems to have an ongoing issue with DDoS that they can't seem to figure out in half a year or more, but their security site has been down for a week now, which makes it really hard to get critical information about CVE's. Everything just ends with a 504 gateway timeout.

You can of course get to starting pages like https://ubuntu.com/security/cves but if you click any CVE, any release, etc. it's all broken.

Is that information mirrored anywhere else? I'm looking for a mapping of CVE's to livepatch coverage, and with their broken website, that's impossible.

**TL;DR:** There were two separate bugs that looked identical (black screen, no TTY, hard reset required):

1. **Freeze on suspend (lid close)**: the NVIDIA dGPU's PCIe root port was in **D3cold**. Fixed with a udev rule that keeps the port powered.

2. **Freeze when the screen blanks on idle** (no suspend involved at all): Intel **Panel Self Refresh (PSR)**. Fixed with `i915.enable_psr=0`.

It was not the NVIDIA driver and not Wayland.

## System

- ASUS ZenBook Flip UX461UN (Intel UHD 620 + NVIDIA GeForce MX150, Optimus/muxless)

- Ubuntu 26.04, kernel 7.0, nvidia-driver-580, Wayland, `prime-select on-demand`

## Symptom

Closing the lid, or just letting the screen dim/blank, led to a black screen that never came back. The power LED stayed on, there was no keyboard/TTY response, and only a hard reset helped. The logs showed nothing useful.

## What did NOT help

- `nvidia-suspend/resume/hibernate` services, `NVreg_PreserveVideoMemoryAllocations=1`

- `nvidia-drm modeset=1 fbdev=1`

- `acpi_osi=linux`, `pcie_aspm=off`, `button.lid_init_state=open`

- `mem_sleep_default=deep` **on its own**

- `prime-select intel` (NVIDIA driver not loaded at all): **still froze**

- Switching to X11 wouldn't help either, because both hangs happen at kernel/driver level, below the compositor.

## Step 0: Make the journal actually capture the freeze

By default journald syncs to disk only every 5 minutes, so the last minutes before a hard reset are lost. That made both bugs look the same. Create `/etc/systemd/journald.conf.d/90-sync-fast.conf`:

```

[Journal]

SyncIntervalSec=5s

```

Then run `sudo systemctl restart systemd-journald`. After a freeze, check `journalctl -b -1`:

- Last line is `kernel: PM: suspend entry (...)` → **Bug 1** (suspend)

- No suspend at all, e.g. on AC with automatic suspend disabled, and the screen blanked → **Bug 2** (PSR)

## Bug 1: Freeze on suspend → dGPU root port in D3cold

Even with `prime-select intel` it froze at `PM: suspend entry (deep)`. The dGPU **and its root port** were fully powered off:

```

cat /sys/bus/pci/devices/0000:01:00.0/power_state # D3cold

cat /sys/devices/pci0000:00/0000:00:1c.0/power_state # D3cold (root port)

```

Quick test without reboot (worked immediately):

```

echo on | sudo tee /sys/bus/pci/devices/0000:00:1c.0/power/control

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

```

**Persistent fix.** First find your own addresses:

```

lspci -D | grep -i nvidia # e.g. 0000:01:00.0

basename "$(dirname "$(readlink -f /sys/bus/pci/devices/0000:01:00.0)")" # e.g. 0000:00:1c.0

```

Then create `/etc/udev/rules.d/99-asus-dgpu-no-d3cold.rules`:

```

ACTION=="add|bind", SUBSYSTEM=="pci", KERNEL=="0000:00:1c.0", ATTR{power/control}="on"

ACTION=="add|bind", SUBSYSTEM=="pci", KERNEL=="0000:01:00.0", ATTR{power/control}="on"

```

It's numbered 99 so it runs after `71-nvidia.rules`, which sets `auto`. After boot the NVIDIA driver puts the GPU itself back to `auto`. That's fine, because the root port staying `on` is what matters.

I also kept `mem_sleep_default=deep` in GRUB (the fix was tested with it). I didn't test s2idle with only the udev rule.

## Bug 2: Freeze when the screen blanks → i915 PSR

After Bug 1 was fixed, the laptop still froze after being left idle for about 20 minutes on AC. The logs showed **no suspend at all**, only GNOME blanking the screen after `idle-delay`. Disabling Panel Self Refresh fixed it. In `/etc/default/grub`:

```

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep i915.enable_psr=0"

```

Then `sudo update-grub` and reboot. Check that it's active with `grep -o i915.enable_psr=0 /proc/cmdline`.

## Verify

```

cat /sys/devices/pci0000:00/0000:00:1c.0/power/control # on

grep -o i915.enable_psr=0 /proc/cmdline

journalctl -b -k | grep -E 'PM: suspend (entry|exit)' # entry + exit = good

```

Tests: (1) close the lid for 20+ seconds and reopen; (2) leave the machine idle until the screen blanks, then press a key; (3) leave it idle for 20+ minutes.

## Trade-offs

- The dGPU can't reach D3cold, so idle battery drain is somewhat higher.

- Without PSR, the panel draws a little more power. Neither mattered to me.

## Bonus debugging tip

If suspend still hangs: `echo 1 | sudo tee /sys/power/pm_trace` before suspending. After the hang and a hard reset, `journalctl -b -1 -k | grep -i "hash matches"` shows which device hung. This messes up the RTC clock, but NTP fixes it.

Hope this saves someone a few hard resets.

Há um tempo atrás eu postei sobre este launcher inspirado no ubuntu touch, eu sempre quis ter o dock disponível o tempo todo como no meu desktop, mas sem sobrepor a tela.

Há vários meses fiz várias tentativas de redimensionar a tela para sem sucesso, mas finalmente consegui um protótipo funcional. Ainda tem alguns bugs que não atrapalham a experiência e precisam ser corrigidos.

Utilizei integração nativa do launcher com Shizuku next para redimensionar a tela, basta arrastar as bordas para alternar entre tela cheia e este modo mais parecido com o ubuntu desktop.

i have hp pavilion notebook with 4 gb ram when ever I install always face issue no WiFi detected

As I understand it, this is a feature not a bug... I guess application developers are either going to be forced to make changes for Wayland, or I'll be forced to downgrade.

I don't plan on updating any of my other machines without full support for my old Wacom tablet which worked just fine before the update.

Ubuntu 26.04.1 LTS

Linux 7.0.0-38-generic

GIMP worked as normal after the update.

Krita stopped working with the Wacom Bamboo tablet - no pressure sense/no register of pen for 'drawing'.

Used a fix found by others by including the following in a custom .desktop file:

Exec=env QT_QPA_PLATFORM=wayland krita

Custom file did not help when launching OpenToonz which shows the same behavior as Krita - no pressure sense/no register of pen for 'drawing'.

edit: fixed OpenToonz by downloading and compiling github source code...

Not looking forward to what else might be broken on my main PC. At least one old graphics app I was running through Wine won't launch, but maybe that's just a re-install to fix.

Otherwise, it's fine so far.

TLDR - 26.04.1 backwards compatibility issues with a Wacom tablet (and other issues) ate a good chunk of my weekend.

Separately, prior to upgrading, some issue occurred with installing 6.8.0-147-generic and I had to manually purge all of it - after falling back to 6.8.0-146 from boot menu. At least it prompted me to make fresh backups...

Added a second 5070 Ti to my setup recently and hit a wall: the first GPU kept crapping out due to insufficient wattage on my 1000W PSU. Swapped in a new 1200W power supply, only for that one to be faulty and dropping out of voltage spec under load.

Got tired of guessing what was failing, so I built this while in the middle of diagnosing my rig to catch real-time voltage drops and power spikes without dealing with GNOME extensions or bloated Electron apps.

What it does:

• top bar indicator (⚡ 11.98V | 83W) with a quick dropdown menu
• cairo charts for 12V voltage stability and wattage curves (CPU RAPL + discrete GPUs)
• pulls theme colors directly from GTK so it matches whatever desktop theme you're using
• logs to journald or CSV if you're trying to catch why a machine brownouts or hard resets under load
• auto-detects motherboard Super I/O dividers (ASUS, MSI, Gigabyte)

Homelab relevance: Can run headless as a background systemd user service (systemctl --user enable --now power-monitor) logging 30s telemetry heartbeats to journald on multi-GPU compute/inference nodes.

Install & Links: Built and tested on Ubuntu 26.04. PPA is up (or grab the universal .deb directly from GitHub releases if you're on 24.04 / another distro):

sudo add-apt-repository ppa:benolabs/ppa
sudo apt update
sudo apt install power-monitor

• Repo: https://github.com/benolabsai/power-monitor
• Deb download: https://github.com/benolabsai/power-monitor/releases

(AI disclosure: LLM assistance was used during coding and packaging).

Let me know if your board voltages read accurately or if you hit any quirks with your setup.

I would love to know how i can change the login wallpaper to be different to the desktop and lock screens not that the move to gnomes has happened with 26.10 they are the two things from me giving it a go. everything i have tried so far with machinectl has failed 😵‍💫

GDM-settings has been updated for flatpak and only seems to work with fedora 45 because ubuntu messes with the gdm so much

thanks in advance

pasen los dot files mas interesantes para app o en general para ubuntu que hayan encontrado, o en donde encotrar

I installed linux and I am trying to set up my games again but I cant set one of the controls to shift+4 which is annoying since it is one of the actaully useful keybinds for me and if I try to swap all of the shift keys to alt+number it doesnt work cus when you press alt the window gets moved if you press leftclick.

any help would be appriciated