KDE Discover Software Center: PageUp/PageDown in "More Information" not working

Help
1

Hi, do the pageup/pagedown keys work for you guys when you browse details of the System Software/System Upgrade?

I can scroll with mouse wheel and cursor keys, but not page up/down… Really annonying…

2

Hi - hmm, I just checked and I’m able to use both the cursor keys and the PgUp/PgDn keys (Fedora 41, Plasma 6.2.4).

Could you please share your system information from the Info Center app just to check what versions you have running? The Copy Details button is the easiest way to go there:

image
image1023×236 30.8 KB

3

Hi John & Megh,

thank you for your response. I will gladly provide my install details:

Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.10-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland

$ dnf info plasma-discover
Updating and loading repositories:
Repositories loaded.
Installed packages
Name            : plasma-discover
Epoch           : 0
Version         : 6.2.4
Release         : 1.fc41
Architecture    : x86_64
Installed size  : 2.0 MiB
Source          : plasma-discover-6.2.4-1.fc41.src.rpm

To be precise, I am trying to check if there are critical updates before deciding if I apply (kernel etc.) by going to “Discover → Updates → System Software → More Information…” and then trying to scroll through the package details pane that appears on the right.

Funny thing is, the keys work fine in the same app when browsing package categories, it’s just this one view where I would need them most that does not work :slight_smile:

4

Okay this is strange, I was fooling around a bit more with this, and found out the following:

  • If I use the keys immediately after hitting “More Information”, they work!
  • As soon as I click anywhere in that pane, they stop working and there is no way to get them back except completely reopening that view.

Good enough for me as a workaround, happy to file a bug if you think this is weird and anyone can point me in the right direction.

1 Like
5

Ah, I see that now following those specific steps! In my opinion, it’s worth a bug report so folks contributing code can see that the issue is there (and who knows, that might feed into some bigger underlying issue!)

Thanks!

Edit: Here’s a reference to reporting issues in KDE software, in case it’s helpful: Get Involved/Issue Reporting - KDE Community Wiki

1 Like