Hi,
My Fedora 43 KDE Plasma was working smoothly without any problems. However when I’ve installed Fedora 44 KDE Plasma it started to work very slow. The only change, if I remember, was that I have manually established partitions during installation.
Do you have any advice what to do?
Gather evidence of what is slow - is the CPU running at high utilisation, are the fans spinning hard, is there anything in the journal, is there noticeable lag in mouse movement or windows drawing slowly etc.
Your post is the car equivalent of “it’s making a funny noise” and we’re supposed to guess what the issue is without being able to see it or hear it.
Start with posting the output from inxi -Fzxx and describe why you think it’s slow and how it’s different from F43.
Hi,
First of all thanks for the answer. I’m rather new at Linux therefore sometimes I don’t quite know what information I supposed to deliver.
By saying that Fedora 44 works slow I do have in mind that apps are opening several seconds slower. For exaple Libreoffice on Fedora 42 and 43 was opening in one or two seconds. Now I need to wait up to ten seconds or more. Libreoffice is gettin stuck very often and is scrolling pages is not smooth.
Disciver used to launch in up to three seconds and now it takes ten seconds or more, not to mention showing search results, uploaded apps or updates.
Both Fedora 42 and 43 were working on dual boot, and now F44 is my only OS.
Below you can find the output from inxi -Fxxz
System:
Kernel: 7.0.4-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A wm: kwin_wayland dm: N/A
Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Laptop System: ASUSTeK product: X411UA v: 1.0
serial:
Mobo: ASUSTeK model: X411UA v: 1.0 serial:
Firmware: UEFI vendor: American Megatrends v: X411UA.303 date: 12/28/2017
Battery:
ID-1: BAT0 charge: 4.8 Wh (17.8%) condition: 27.3/42.1 Wh (64.8%)
volts: 11.52 min: 11.52 model: ASUSTeK ASUS Battery serial: N/A charging:
status: charging cycles: 427
CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP
arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2500 min/max: 400/3400 cores: 1: 2500 2: 2500 3: 2500
4: 2500 5: 2500 6: 2500 7: 2500 8: 2500 bogomips: 28800
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Kaby Lake-R GT2 [UHD Graphics 620] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1
empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: IMC Networks VGA UVC WebCam driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-6:3 chip-ID: 13d3:5a07
Display: wayland server: Xwayland v: 24.1.11 compositor: kwin_wayland
driver: gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x06f3 res: 1920x1080 hz: 57 dpi: 158
diag: 354mm (13.9")
API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.6 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
device-ID: 8086:5917 display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: integrated-gpu
driver: mesa intel device-ID: 8086:5917 device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
API: ALSA v: k7.0.4-200.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: AzureWave
driver: rtw88_8822be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000
bus-ID: 02:00.0 chip-ID: 10ec:b822
IF: wlp2s0 state: up mac:
Bluetooth:
Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-8:4 chip-ID: 13d3:3526
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: bt-v: 4.2
lmp-v: 8
Drives:
Local Storage: total: 238.47 GiB used: 28.9 GiB (12.1%)
ID-1: /dev/sda vendor: Micron model: 1100 MTFDDAV256TBN size: 238.47 GiB
speed: 6.0 Gb/s serial:
Partition:
ID-1: / size: 235.89 GiB used: 28.37 GiB (12.0%) fs: btrfs dev: /dev/sda3
ID-2: /boot size: 1.9 GiB used: 522.3 MiB (26.8%) fs: ext4 dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 235.89 GiB used: 28.37 GiB (12.0%) fs: btrfs
dev: /dev/sda3
Swap:
ID-1: swap-1 type: zram size: 7.63 GiB used: 161.7 MiB (2.1%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.0 C pch: 40.5 C mobo: N/A
Fan Speeds (rpm): cpu: 2900
Info:
Memory: total: 8 GiB available: 7.63 GiB used: 2.83 GiB (37.1%)
Processes: 309 Power: uptime: 13m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 22
Compilers: N/A Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40
Gotcha - don’t sweat it about the “not sure what to supply” - the basic rule is “the more, the better”.
This does sound quite sluggish; you have a definite feel that the response from asking an application to start to the time it actually appears is significantly longer than F43 used to do the same task.
Is there any issue once the application is running - does it feel as responsive as is used to on F43 when you’re running an application does everything feel a little “off”? (trying to determine if this is a disk issue if starting apps, or a CPU issue when running them)
Can you also install btop, start it running in a decently size terminal window and let it sit for about 5 minutes, just letting the machine idle. Then fire up LibreOffice, Discover, or anything which you feel is slow enough to demonstrate this issue and after it’s fired up leave it for maybe 20 seconds, before stopping it. Then take a screenshot of the btop terminal window - it’ll be something like this
I’d like to see what the system look like when it’s just idling (hence the few minutes delay) then what happens when you start the application and then what happens after the app is loaded and is running. Ideally we’d capture this in some text output but I can’t find anything which shows history, temps, CPU activity, memory pressure, running threads and so on all in one place!