pamac issueshttps://gitlab.manjaro.org/applications/pamac/-/issues2024-03-24T19:55:21Zhttps://gitlab.manjaro.org/applications/pamac/-/issues/1399Pamac extension is not working with Gnome 462024-03-24T19:55:21ZFrederic BeziesPamac extension is not working with Gnome 46## Pamac --version
Pamac 11.7.1-2 - libpamac 11.6.4-1
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
GNOME 46 from Manjaro unstable
## What's not working
Tray icon is not working
## How to reproduce?
* Swit...## Pamac --version
Pamac 11.7.1-2 - libpamac 11.6.4-1
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
GNOME 46 from Manjaro unstable
## What's not working
Tray icon is not working
## How to reproduce?
* Switch a Manjaro Gnome to unstable repository
* Upgrade to Gnome 46
* Log out then log in. No more application tray icon.https://gitlab.manjaro.org/applications/pamac/-/issues/1396Double-clicking flatpak opens Pamac, but does nothing2024-01-22T00:38:20Zphp4fanDouble-clicking flatpak opens Pamac, but does nothing## Pamac --version
Pamac 10.6.0 - libpamac I don't know
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
see below
## How to reproduce?
* I enabled Flatpak support in Pamac (was disa...## Pamac --version
Pamac 10.6.0 - libpamac I don't know
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
see below
## How to reproduce?
* I enabled Flatpak support in Pamac (was disabled by default)
* I downloaded a flatpak, namely Telegram Desktop
* I double-clicked on the downloaded file.
This opens Pamac but does nothing:
![image](/uploads/b98d804ad8b15f71a094fd66437a951d/image.png)
If this is because I haven't restarted after after enabling Flatpak (as [these instructions](https://flatpak.org/setup/Manjaro) seem to suggest), then it should tell me that I need to restart when I enable it. This would only be acceptable if there's absolutely no way for flatpak support to start working without restarting, which would be surprising (nothing that is not directly related to boot should ever require a restart, ever).
## More information (optional)Guillaume BenoitGuillaume Benoithttps://gitlab.manjaro.org/applications/pamac/-/issues/1395Request: Pamac theme option2024-01-25T00:34:00ZDemiray MuhteremRequest: Pamac theme optionIs it possible to add a section where we can choose a theme in Pamac options? ThanksIs it possible to add a section where we can choose a theme in Pamac options? Thankshttps://gitlab.manjaro.org/applications/pamac/-/issues/1394choose provider for dialog empty2024-01-17T11:12:43ZTodor Uzunovchoose provider for dialog empty## Pamac --version
Pamac 11.7.1-1 - libpamac 11.6.3-1
### Variant in use
GUI (gtk4), cli is reported working correctly
## Distribution
Manjaro
## Desktop environment
XFCE, reported also on KDE
## What's not working
The prompt "choo...## Pamac --version
Pamac 11.7.1-1 - libpamac 11.6.3-1
### Variant in use
GUI (gtk4), cli is reported working correctly
## Distribution
Manjaro
## Desktop environment
XFCE, reported also on KDE
## What's not working
The prompt "choose provider for" is empty, on clicking "choose" the entry(choice) 1 is selected
## How to reproduce?
* there has to be a "new provider for" type of conflict
* update
## More information (optional)
Several user reports and screenshots
https://forum.manjaro.org/t/stable-update-2024-01-13-kernels-systemd-qt5-mesa-dbus-firefox-thunderbird/155007/62https://gitlab.manjaro.org/applications/pamac/-/issues/1393This error message is not understandable nor actionable2023-12-21T22:49:49Zphp4fanThis error message is not understandable nor actionable## Pamac --version
Pamac 11.7.0-1 - libpamac I have no idea, About doesn't say
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
I opened Pamac (GUI), I selected all available updates,...## Pamac --version
Pamac 11.7.0-1 - libpamac I have no idea, About doesn't say
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
I opened Pamac (GUI), I selected all available updates, and I clicked "Apply".
I got this error:
![image](/uploads/480e0980121114d0b76d0c5d3bc5ce53/image.png)
This is completely nonsensical, at least as far as the user can tell.
It says "Failed to prepare transaction", but then there is an "Apply" button, which obviously I'm scared to even touch.
What am I going to apply, if the transaction has failed to be prepared???
What does "failed to prepare transaction" even mean? You have to understand that is not clear to a user unless they have a very deep technical understanding of how the process of installing updates work in detail.
When an error occurs when installing updates (which, regrettably, happens pretty often), there are **two crucial pieces of information that I expect** from the error message:
1. what I can do about it (and if the answer is nothing, tell me that very explicitly)
2. **what the source of the error is**, and by source I mean the project to which I need to report the bug.
Because when some update fails to install, there's a bug somewhere (unless it's something like a network error downloading a file or something of that kind, in which case there should be a "retry" button for me to press).
It cannot be something I did wrong, because I delegate all the work of installing and updating software to a package manager, and I never tinker with it, so if something fails to install properly, it's because either the package manager doesn't work properly (but that's very rare) or because some of the packages has a bug (whether that's in the form of a dependency not specified correctly or something else). So when I encounter such an error I want to report it immediately to whoever is maintaining that package.
In this case with such an error, I have no clue of either of these two things.
The "Edit build files" button, I have no idea if that offers a solution to someone with deep knowledge of the stuff being installed and how the install process works, but that's not me anyway.
I hit Esc (which I guess was the same as clicking Cancel) and I got this:
![image](/uploads/680343ac07fe825a81e2cb4946604454/image.png)
Assuming this is related to the first error (which seems a pretty reasonable assumption), this at least tells me that there's something wrong about the "gitahead" package (kind of answering question 2 above), but what sense does it make to have this as a second popup **after Cancel-ing** the first, nonsensical one??
This sequence doesn't make sense:
i) the first error, saying that some transaction has failed to be prepared, with no explanation of what the issue is, an "Apply" button that would apply who-knows what, and an option to cancel
ii) when I cancel, another error saying basically the same thing (failed to prepare transaction) but with a little bit more context. Was this a second error that occurred after cancelling the failed transaction? Doesn't seem likely. So why wasn't everything in a single popup?
I'm not sure whether the second popup was displayed after exiting the first popup, or if it was fired immediately before and was hidden behind it and became visible when I closed the other one.
## How to reproduce?
I don't know. What I did was:
* I selected all available updates
* clicked Apply
## More information (optional)https://gitlab.manjaro.org/applications/pamac/-/issues/1392Available Flatpaks seen only after restart2023-12-06T11:00:20ZivanAvailable Flatpaks seen only after restartPamac 10.6 Manjaro KDE
I enabled Flatpak packages, refreshed the mirror list and databases manually and still couldn't see a single flatpak package listed.
I needed to close and restart Pamac to have them appear during Search.
Expected...Pamac 10.6 Manjaro KDE
I enabled Flatpak packages, refreshed the mirror list and databases manually and still couldn't see a single flatpak package listed.
I needed to close and restart Pamac to have them appear during Search.
Expected result: once enabled, flatpaks should be seen under search immediately.https://gitlab.manjaro.org/applications/pamac/-/issues/1391Pamac and AUR2024-01-17T07:20:57ZRobin WheelerPamac and AUR## Pamac --version
Pamac 10.6.0-0 - libpamac 11.6.0-0
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
Cinnamon
## What's not working
Pamac preferences. You can enable AUR even if things like base-devel are not...## Pamac --version
Pamac 10.6.0-0 - libpamac 11.6.0-0
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
Cinnamon
## What's not working
Pamac preferences. You can enable AUR even if things like base-devel are not present
## How to reproduce?
Enable AUR in Pamac
Try to build Google Chrome it fails because base-devel is not present
## More information (optional)
Perhaps stop AUR being enabled if dependencies are missinghttps://gitlab.manjaro.org/applications/pamac/-/issues/1389[pamac-gtk3] GUI width increases to show text for Licences in one line, inst...2023-09-29T01:42:58Znik-gnomic[pamac-gtk3] GUI width increases to show text for Licences in one line, instead of adding line breaks## Pamac --version
pamac-cli 11.6.0 - libpamac 11.6.2
### Variant in use
pamac-gtk3 10.6.0-1
## Distribution
Manjaro
## Desktop environment
KDE and Xfce
## What's not working
pamac-gtk3 GUI increases from 1 or 2 columns wide to ...## Pamac --version
pamac-cli 11.6.0 - libpamac 11.6.2
### Variant in use
pamac-gtk3 10.6.0-1
## Distribution
Manjaro
## Desktop environment
KDE and Xfce
## What's not working
pamac-gtk3 GUI increases from 1 or 2 columns wide to 3 columns wide to show Licences text in one line, instead of using line breaks to display text on multiple lines to preserve width of GUI
## How to reproduce?
1. Open pamac-gtk3 with 1 or 2 columns of packages visible
2. Search for "qemu" and click on packages `qemu-audio-*`or `qemu-base` to view package details
3. GUI width increases to show Licence information in one line only:\
[KDE screenshot](https://forum.manjaro.org/uploads/default/original/3X/4/e/4e7ac63de9cdbfbaab24a0942b2c9c55f7e741f3.png)\
[Xfce screenshot](https://forum.manjaro.org/uploads/default/original/3X/b/7/b79c71f8db46e6a61c1fd9b05659954607da27ae.jpeg)
## More information (optional)
First reported to Manjaro forum: [Visual bug in pamac-gtk3](https://forum.manjaro.org/t/visual-bug-in-pamac-gtk3/148784)https://gitlab.manjaro.org/applications/pamac/-/issues/1388Scroll wheel stops working after moving window2023-09-20T19:16:10Zphp4fanScroll wheel stops working after moving window## Pamac --version
pamac-cli 11.6.0 - libpamac 11.6.2
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
The mouse's scroll wheel stops working
## How to reproduce?
* Open the System U...## Pamac --version
pamac-cli 11.6.0 - libpamac 11.6.2
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
The mouse's scroll wheel stops working
## How to reproduce?
* Open the System Updates GUI
* Go to some tab where you are sure to have enough items listed that they don't fit within the window, e.g. "Installed"
* try to scroll with the mouse wheel
* move the window by clicking and dragging on its title bar
* move the mouse cursor over the list of packages and try to scroll again with the mouse wheel
## More information (optional)
Expected behavior: when the mouse cursor is over the scrollable area, mouse wheel scroll should always work
Observed behavior: after moving the window, scrolling doesn't work, until you click within the area of the scrollable listhttps://gitlab.manjaro.org/applications/pamac/-/issues/1387It can't upgrade the system at shutdown, if plymouth is not installed.2023-12-16T06:01:53ZlaichiahengIt can't upgrade the system at shutdown, if plymouth is not installed.## Pamac --version
Pamac 10.6.0-3 - libpamac 11.6.2-1
### Variant in use
GUI
## Distribution
Arch
## Desktop environment
GNOME
## What's not working
upgrade the system at shutdown
## How to reproduce?
* Enable `upgrade the system...## Pamac --version
Pamac 10.6.0-3 - libpamac 11.6.2-1
### Variant in use
GUI
## Distribution
Arch
## Desktop environment
GNOME
## What's not working
upgrade the system at shutdown
## How to reproduce?
* Enable `upgrade the system at shutdown` in Pamac
* Shutdown or reboot
## More information (optional)
I have installed packagekit.https://gitlab.manjaro.org/applications/pamac/-/issues/1386slower startup2023-09-03T12:24:00Zgittymeslower startuppamac-cli 11.6.0 libpamac 11.6.2
KDE
Manjaro
pamac GUI is taking slightly longer to load the UI - perhaps the problem is...
```
$ pamac-manager
(pamac-manager:5066): Adwaita-WARNING **: 08:16:44.161: Using GtkSettings:gtk-application-...pamac-cli 11.6.0 libpamac 11.6.2
KDE
Manjaro
pamac GUI is taking slightly longer to load the UI - perhaps the problem is...
```
$ pamac-manager
(pamac-manager:5066): Adwaita-WARNING **: 08:16:44.161: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
```https://gitlab.manjaro.org/applications/pamac/-/issues/1385needs qt2023-08-31T12:02:22Zgittymeneeds qtthe gtk UI for pamac on KDE/qt is terrible and getting worse with each update
* pamac changes the mouse sensitivity after a system upgrade (this started a couple of updates back)
* auto-scrolling in the console when installing packages ...the gtk UI for pamac on KDE/qt is terrible and getting worse with each update
* pamac changes the mouse sensitivity after a system upgrade (this started a couple of updates back)
* auto-scrolling in the console when installing packages randomly stops working (this has been an issue for years)
* randomly changing width of app tiles and number of app tile columns when scrolling through apps (this started several months ago)
* app info window cursor resize handles are off of the edge of the window (missing window frame) (this started a couple of updates back)
* missing max/restore icons in app info windows (this started a couple of updates back)
* non-resizable (width) panels in UI
* non-wrapping/cut-off text when displaying build files
* searching for a package, then clearing the search input should revert to listing all packages for the selected category, but doesn't (i believe this is (another) new bug (feature?)
* viewing the file list for a package having more files than can be displayed results in not one, but two v scroll bars (???) and even with that it is practically impossible to scroll to the end of the list (test with LibreOffice for ex.)
* and more...https://gitlab.manjaro.org/applications/pamac/-/issues/1382[pamac-gtk3] Running "pamac-manager --version" generates a crash2023-08-23T12:11:01ZMedin[pamac-gtk3] Running "pamac-manager --version" generates a crash## Pamac --version
```
pamac-gtk3 10.6.0
pamac-cli 11.6.0
libpamac 11.6.0
```
### Variant in use
CLI
## System
Manjaro
## Desktop environment
Plasma KDE
## How to reproduce?
![Screenshot_20230822_171833](/uploads/83186b93af0d0e38dbd...## Pamac --version
```
pamac-gtk3 10.6.0
pamac-cli 11.6.0
libpamac 11.6.0
```
### Variant in use
CLI
## System
Manjaro
## Desktop environment
Plasma KDE
## How to reproduce?
![Screenshot_20230822_171833](/uploads/83186b93af0d0e38dbd901c15b0d26a1/Screenshot_20230822_171833.png)
## Backtrace
```
Core was generated by `pamac-manager --version'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f7b19e8a070 in ?? ()
[Current thread is 1 (Thread 0x7f7b16a5ee40 (LWP 25082))]
(gdb) bt full
#0 0x00007f7b19e8a070 in ()
#1 0x00007f7b192f18b4 in g_object_unref (_object=0x5586ad1b2bf0) at ../glib/gobject/gobject.c:3938
weak_locations = <optimized out>
nqueue = 0x5586ad17d200
old_ref = <optimized out>
object = 0x5586ad1b2bf0
__func__ = "g_object_unref"
#2 g_object_unref (_object=0x5586ad1b2bf0) at ../glib/gobject/gobject.c:3802
object = 0x5586ad1b2bf0
__func__ = "g_object_unref"
#3 0x00007f7b19045101 in () at /usr/lib/libpamac.so.11
#4 0x00007f7b192f18b4 in g_object_unref (_object=0x5586ad17d1b0) at ../glib/gobject/gobject.c:3938
weak_locations = <optimized out>
nqueue = 0x5586ad12dc20
old_ref = <optimized out>
object = 0x5586ad17d1b0
__func__ = "g_object_unref"
#5 g_object_unref (_object=0x5586ad17d1b0) at ../glib/gobject/gobject.c:3802
object = 0x5586ad17d1b0
__func__ = "g_object_unref"
#6 0x00007f7b1904b3e5 in () at /usr/lib/libpamac.so.11
#7 0x00007f7b192f18b4 in g_object_unref (_object=0x5586ad12dbf0) at ../glib/gobject/gobject.c:3938
weak_locations = <optimized out>
nqueue = 0x5586ad184f90
old_ref = <optimized out>
object = 0x5586ad12dbf0
__func__ = "g_object_unref"
#8 g_object_unref (_object=0x5586ad12dbf0) at ../glib/gobject/gobject.c:3802
object = 0x5586ad12dbf0
__func__ = "g_object_unref"
#9 0x00005586ac68b447 in ()
#10 0x00007f7b18c27cd0 in __libc_start_call_main (main=main@entry=0x5586ac68b090, argc=argc@entry=2, argv=argv@entry=0x7ffea074b5c8) at ../sysdeps/nptl/libc_start_call_main.h:58
self = <optimized out>
result = <optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140731590424008, 8693813850748394776, 0, 140731590424032, 140166692827136, 94036906783696, -8693106940168987368, -8768349980194333416}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7ffea074b5c8, 0x2}, data = {prev = 0x0, cleanup = 0x0, canceltype = -1602964024}}}
not_first_call = <optimized out>
#11 0x00007f7b18c27d8a in __libc_start_main_impl
(main=0x5586ac68b090, argc=2, argv=0x7ffea074b5c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffea074b5b8) at ../csu/libc-start.c:360
#12 0x00005586ac68b545 in ()
(gdb)
```https://gitlab.manjaro.org/applications/pamac/-/issues/1381RAM usage of pamac-manager above 700-800 MB just to open it2024-01-17T09:50:46ZTodor UzunovRAM usage of pamac-manager above 700-800 MB just to open it## Pamac --version
Pamac 11.6.0-0 - libpamac 11.6.0-0
### Variant in use
GUI - gtk4
## Distribution
Manjaro, kernel 6.1
## Desktop environment
XFCE
## What's not working
Pamac (at least the gui) is needing about 7-800 MB RAM just t...## Pamac --version
Pamac 11.6.0-0 - libpamac 11.6.0-0
### Variant in use
GUI - gtk4
## Distribution
Manjaro, kernel 6.1
## Desktop environment
XFCE
## What's not working
Pamac (at least the gui) is needing about 7-800 MB RAM just to start, which is ridiculous. And i am pretty sure it was not so about a month ago, but since then there were about 20 updates, so i cannot say since when is this behavour.
## How to reproduce?
* Start pamac from tray or whisker menu
## More information (optional)https://gitlab.manjaro.org/applications/pamac/-/issues/1375[pamac-gtk3] having libpamac-appstream-plugin not installed might break search2023-08-06T07:04:22ZPhilip Müller[pamac-gtk3] having libpamac-appstream-plugin not installed might break search## Pamac --version
Pamac 10.6.0-0 - libpamac 11.6.0-0.1
### Variant in use
GUI (10.6.0)
## Distribution
Manjaro
## Desktop environment
doesn't matter
## What's not working
Package search might be broken when appstream plugin is not...## Pamac --version
Pamac 10.6.0-0 - libpamac 11.6.0-0.1
### Variant in use
GUI (10.6.0)
## Distribution
Manjaro
## Desktop environment
doesn't matter
## What's not working
Package search might be broken when appstream plugin is not installed
## How to reproduce?
* not having appstream plugin installed
* try to search for a package
## More information (optional)
![image](/uploads/2d89d7717ef999144ddafa75708f4b40/image.png)https://gitlab.manjaro.org/applications/pamac/-/issues/1374[pamac-gtk3] AUR options still available even if libpamac-aur-plugin is not i...2023-08-06T06:38:50ZPhilip Müller[pamac-gtk3] AUR options still available even if libpamac-aur-plugin is not installed## Pamac --version
Pamac 10.6.0-0 - libpamac 11.6.0-0.1
### Variant in use
GUI (10.6.0)
## Distribution
Manjaro
## Desktop environment
doesn't matter
## What's not working
When libpamac-aur-plugin isn't installed you still have the...## Pamac --version
Pamac 10.6.0-0 - libpamac 11.6.0-0.1
### Variant in use
GUI (10.6.0)
## Distribution
Manjaro
## Desktop environment
doesn't matter
## What's not working
When libpamac-aur-plugin isn't installed you still have the AUR options in GTK3 UI. It is fine with GTK4 UI.
## How to reproduce?
* uninstall libpamac-aur-plugin
* You will find still options of it in the UI
## More information (optional)
![image](/uploads/5ba9a6bcb0b8d8ee33ddf8ae1e75d43c/image.png)https://gitlab.manjaro.org/applications/pamac/-/issues/1373Added missing Name and keywords2023-08-05T07:04:10ZphoepsilonixAdded missing Name and keywords## Pamac --version
Pamac 11.0.1 - libpamac 11.5.7
### Variant in use
GUI or CLI
## Distribution
Manjaro
## Desktop environment
GNOME
Added missing Name and keywords.
[0001-added-Name-and-Keywords-of-desktop-files.patch](/uploads/bc...## Pamac --version
Pamac 11.0.1 - libpamac 11.5.7
### Variant in use
GUI or CLI
## Distribution
Manjaro
## Desktop environment
GNOME
Added missing Name and keywords.
[0001-added-Name-and-Keywords-of-desktop-files.patch](/uploads/bc4b6f8a4f01043bad8da46da5d3af5e/0001-added-Name-and-Keywords-of-desktop-files.patch)https://gitlab.manjaro.org/applications/pamac/-/issues/1372Prevents incorrect termination due to corrupted package information.2023-08-05T07:01:44ZphoepsilonixPrevents incorrect termination due to corrupted package information.## Pamac --version
Pamac 11.0.1 - libpamac 11.5.7
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
GNOME
## What's not working
Prevents incorrect termination due to corrupted package information.
[PATCH] After...## Pamac --version
Pamac 11.0.1 - libpamac 11.5.7
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
GNOME
## What's not working
Prevents incorrect termination due to corrupted package information.
[PATCH] After the update operation, database.refresh().
[0001-After-the-update-operation-database.refresh.patch](/uploads/574d3a7cb5b63ba3e021cba1e0c31a81/0001-After-the-update-operation-database.refresh.patch)
![Screenshot_from_2023-08-03_12-15-54](/uploads/7430724d07c9b6918a106ff55b992d38/Screenshot_from_2023-08-03_12-15-54.png)https://gitlab.manjaro.org/applications/pamac/-/issues/1368Pamac-gtk (gui): Bad font rendering with anti-aliasing disabled (hinting enab...2023-07-26T06:55:08Zkde-userPamac-gtk (gui): Bad font rendering with anti-aliasing disabled (hinting enabled!) after update to version 11.0.1-2 in Manjaro KDE## Pamac --version
Pamac-GTK 11.0.1-2 - libpamac 11.5.7-2
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
Bad font rendering with anti-aliasing disabled (hinting enabled!).
Tested wit...## Pamac --version
Pamac-GTK 11.0.1-2 - libpamac 11.5.7-2
### Variant in use
GUI
## Distribution
Manjaro
## Desktop environment
KDE
## What's not working
Bad font rendering with anti-aliasing disabled (hinting enabled!).
Tested with kernels 515lts and 61lts on two different machines (main/real machine and virtual machine).
In the screenshots you see font Verdana, but it's similar with for example DejaVu Sans or also with the preselected Noto Sans.
Pamac-GTK 10.5.1-1:
![Pamac-gtk-10.5.1-1_anti-aliasing_off_Verdana](/uploads/662811a9c27c1cb547fbe1c1b1de9be8/Pamac-gtk-10.5.1-1_anti-aliasing_off_Verdana.png)
Pamac-GTK 11.0.1-2:
![Pamac-gtk-11.0.1-2_anti-aliasing_off_Verdana](/uploads/accb08d4f292070e48998d02e1ceb2ad/Pamac-gtk-11.0.1-2_anti-aliasing_off_Verdana.png)
## How to reproduce?
- [ ] 1. Use a current Manjaro KDE.
- [ ] 2. Make sure that you have installed an appropriate font, e.g. Verdana or the preinstalled DejaVu Sans or the preselected Noto Sans in Manjaro KDE is suitable. The difference is even a bit more visible with Verdana.
- [ ] 3. Go to System Settings -> Appearance -> Fonts and make the following settings (both options achieve the same effect):
- [ ] 3.1 (Option 1, I took a screenshot of this:) First, make sure that some kind of hinting is enabled, either "Light", "Medium" or "Full" (it doesn't matter which), because after anti-aliasing is disabled, hinting is grayed out and no longer adjustable. But Hinting must be activated in background, even if it is grayed out afterwards (and supposedly should have no function anymore!). Then: Anti-Aliasing -> Disable/Checkmark out
![System-settings_option_1](/uploads/529ce6edf80e3d1e9ed82e137e80606a/System-settings_option_1.png)
- [ ] 3.2 (Option 2:) Anti-Aliasing -> Enable/set checkmark; Exclude range from anti-aliasing -> Enable (8 - 15 pt -> the font size to be tested, e.g. 12 pt must be excluded); Sub-pixel rendering -> Best not to change, for me it is set to RGB; Hinting -> Light, Medium or Full <- important! Force font dpi -> Disable/Checkmark out
- [ ] 4. Remember that the changes made will only affect programs that are restarted afterwards! I have even experienced having to make and save changes twice until they were fully applied.
- [ ] 5. Open Pamac and you should see now the same bad font rendering as I've shown on the second screenshot.https://gitlab.manjaro.org/applications/pamac/-/issues/1366Search history will not highlight matches2023-08-02T14:22:43ZJohn LandmesserSearch history will not highlight matches## Pamac --version
Pamac 11.01-2 - libpamac 11.5.7-2
### Variant in use
GUI
## Distribution
e.g. Manjaro XFCE Stable
## Desktop environment
e.g. XFCE
## What's not working
Search in history will not highlight matches anymore
## H...## Pamac --version
Pamac 11.01-2 - libpamac 11.5.7-2
### Variant in use
GUI
## Distribution
e.g. Manjaro XFCE Stable
## Desktop environment
e.g. XFCE
## What's not working
Search in history will not highlight matches anymore
## How to reproduce?
* launch history in menue
* type for example removed in search box and click on down arrow
## More information (optional)