And encouragement I hope?
I have understanding and love the tiny @Manjaro-Team
Things can happen.
To me it seems they are working their a**es of fixing everything!
And encouragement I hope?
I have understanding and love the tiny @Manjaro-Team
Things can happen.
To me it seems they are working their a**es of fixing everything!
libpamac 11.5.7 should fix the false warning on successful DB sync. Was a logic error on my end when removing some code.
Nothing is fixed here. After the update to libpamac 11.5.7, the problems persist. What a mess …
it fixed for me - refresh databases & mirrors a couple of times, it should work out.
That’s exactly what I’ve done several times now.
I had to disable the “Check for updates” options, then re-enable to fix it.
Well you can try this:
/var/tmp/pamac/dbs/sync
as root/var/tmp/pamac/dbs/sync
as normal userpacman -Syy
as rootpamac update
as normal user@philm
I dont really understand where this commands (pacman merge) really good for… i mean, where is the goal from this?
Are this commands only for removing the Community section (eye candy) and i can skip this or is there something behind this, that i maybe dont see… maybe a bug prevention or security issue?
I solved the issue on my side by just simply commenting out following section in /etc/pacman.conf
#[community]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
After this I just updated the database. Now everything is working fine. I did not merge as suggested before.
The “merge” would have removed the section from the file that you commented.
This is new since the Update
This spam’s the Log
Jul 11 23:36:00 pamac-manager[3728]: Invalid UTF-8 string passed to pango_layout_set_text()
Jul 11 23:42:04 pamac-manager[3945]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Jul 11 23:42:09 pamac-manager[3945]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
and this
Jul 11 23:17:14 kded5[1275]: g_settings_set_value: key 'scaling-factor' in 'org.gnome.desktop.interface' expects type 'u', but a GVariant of type 'i' was given
i use KDE
The pipewire raop-sink bug is fixed !
it is a wiki post. so the content may be from me or from other users. You may ask @Yochanan has he is more in keeping the files clean and tidy. On my end I never used any program to merge pacnew files when there are any.
You use Pamac-GTK which is the GTK4 version. You may want to install pamac-gtk3 to solve your theme issue on KDE:
Thank you @philm this fixed it.
this is now the only new entry since the update
@philm @Yochanan
Okay i just openend the file pacman.con and the .pacnew file with my text editor to see the changes and what im confused here to see under this section:
(pacman.con file)
# Misc options
#UseSyslog
#Color
#TotalDownload
#We cannot check disk space from within a chroot environment
CheckSpace
#VerbosePkgLists
(pacman.con.pacnew file)
# Misc options
#UseSyslog
Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
ParallelDownloads = 4
ILoveCandy
ILoveCandy
WTF going on here? Is this some kind of candy crush Win10 joke?
I wondered about that too
Can someone please tell me what the correct value is?
This is what I have entered
gsettings get org.gnome.desktop.interface scaling-factor
uint32 0
It has nothing to do with Windows or Candy Crush.
It is actually an easter egg that refers to the game with the same name (pacman).
update fails:
error: failed to prepare transaction (conflicting dependencies)
:: nodejs-lts-hydrogen and nodejs-lts-gallium are in conflict
It’s an easter egg that changes the progress bar from ###…to a pseudo-chomping pac-man.