That is most likely because you didn’t save the configuration in nvidia-config to the config file in /etc/X11/mhwd.d/ (the button “Save to X configuration file” in the “X server configuration” menu), you only “apply them” for this session if you don’t.
Make sure you name the file correctly when you save. I recomend doing a backup of the config file before starting to play around with the settings.
Yes, Pamac is a GTK product. As far as I know, no non-GTK versions exist. The GTK version number used does not show up in the file names. if I cd to /usr/bin and do “ls pamac*” I get “pamac pamac-daemon pamac-installer pamac-manager pamac-tray pamac-tray-plasma”. It’s all GTK.
To return from the GTK-4 version of pamac to the GTK-3 version, simply launch pamac and install “pamac-gtk3”. That will automatically un-install “pamac-gtk” (which is based on GTK-4) and replace it with a pamac version basked on GTK-3.
I’ve been doing that to all my computers the last few days, because pamac-gtk has crappy-looking icons, at least on my KDE-Plasma desktops. (Maybe it looks better on Gnome, but I don’t run Gnome.)
1 Like
Since you can set the powerstate of your NVidia card via terminal and the tooltip says its not persistant, i doubt x.org conf has anything to do with it.
Doubt as much as you like.
Didn’t say you should change the xorg conf, I suggested you save your nvidia settings to the nvidia conf (whatever the name is on YOUR computer, I changed it to nvidia.conf) that is symlinked by 90-mhwd.conf
That’s explained in the “Known Issues” near the top of this thread. To fix that, launch a console, become root, and type “pacman -Sy libpamac”, hit Enter, then answer “y Enter” to all questions. Once that completes, restart machine and re-launch pamac and it will work right.
I created 2 bash scripts to change Preset modes, the scripts are for GPU:0 if you have a second GPU in your system this can lead maybe to problems:
For max Performance:
#!/bin/bash
nvidia-settings -a "[gpu:0]/GpuPowerMizerMode=1"
For Auto Detection:
#!/bin/bash
nvidia-settings -a "[gpu:0]/GpuPowerMizerMode=2"
You can also check your states in terminal with:
nvidia-settings -q GpuPowerMizerMode
2 Likes
Should I do this update with pamac or pacman -Syyu ?
I have just hd-idle-go from AUR installed, nothing else. Edit; ok just removed that…
(Btw, which is better hd-idle or hd-idle-go, these support spin downs of my HD that has no SMART support)?
Doesn’t matter anymore. You can use pamac or pamac, whichever you prefer.
1 Like
All the choices. 
Hey, I have the same problem during update of my AUR packages. My list differs a bit.
cbkcomp, game-devices-udev, tieshift, v86d
It says corrupted database. I have updates all keys and so on as in another post described. But the error is still be there. In the extended log is no more detailed error to be seen. I can edit the build files, but that was it.
Checking <application> dependencies...
Failed to prepare transaction:
invalid or corrupted database
Transaction cancelled.
Any ideas how to solve this?
I was not really counting but I got the impression that if somebody moved the senseless-pacnew-discussion posts and all the pamac-issue posts into separate threads this one would not be 100 posts long.
Something to think about, on both counts.
2 Likes
Its a common symptom of the announcement threads that a good number of people treat it like their personal troubleshooting thread and/or neglect reading it and post the same thing multiple times.
See … any other one … they are all rather long, especially if not heavily moderated. Last month: 322.
(the lowest I see is somewhere in the 40s, and those are little ones with another happening days later)
This sounds similar to an earlier post in this thread. Please read the post and the response. If you need assistance with editing the file, please ask.
Hi,
Kernel 6.3, 6.3-rt, 6.4 and 6.4-rt not functioning on MSI GS65-9SF
@Pentastarch did you resolve this? I’m seeing a very similar issue to you it seems. I couldn’t get steam to launch - it was present in the tray though.
I installed the lib recommended in the troubleshooting steps above. This allowed me to launch steam. But after I rebooted, steam no longer launches (tray only).
I tried running steam-runtime on shell and got some output like this:
steam.sh[105221]: Running Steam on manjarolinux 23.0.0 64-bit
steam.sh[105221]: STEAM_RUNTIME is enabled automatically
setup.sh[105295]: Steam runtime environment up-to-date!
steam.sh[105221]: Steam client's requirements are satisfied
[2023-07-13 18:08:38] Startup - updater built Jul 10 2023 23:58:24
[2023-07-13 18:08:38] Startup - Steam Client launched with: '/home/username/.local/share/Steam/ubuntu12_32/steam'
07/13 18:08:38 Init: Installing breakpad exception handler for appid(steam)/version(1689034492)/tid(105352)
[2023-07-13 18:08:38] Loading cached metrics from disk (/home/username/.local/share/Steam/package/steam_client_metrics.bin)
[2023-07-13 18:08:38] Using the following download hosts for Public, Realm steamglobal
[2023-07-13 18:08:38] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2023-07-13 18:08:38] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2023-07-13 18:08:38] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-07-13 18:08:38] Verifying installation...
[2023-07-13 18:08:38] Verification complete
Loaded SDL version 3.0.0-1782-g214d5daa3
/usr/share/themes/Breeze/gtk-2.0/widgets/entry:70: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:36: error: invalid string constant "combobox_entry", expected valid string constant
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xefe23db0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xefe22500
GetWin32Stats: display was not open yet, good
ComputeStartupMode: found registry default startup mode: 0
Switching to desktopui, since -vgui was not specified
GetWin32Stats: display was not open yet, good
steamwebhelper.sh[105358]: Runtime for steamwebhelper: defaulting to /home/username/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[105358]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
CAppInfoCacheReadFromDiskThread took 80 milliseconds to initialize
Failed to init SteamVR because it isn't installed
local (potentially out of sync) copy of roaming config loaded - 1652 bytes.
BRefreshApplicationsInLibrary 1: 1ms
roaming config store loaded successfully - 1652 bytes.
migrating temporary roaming config store
System startup time: 3.41 seconds
steamwebhelper.sh[105773]: Runtime for steamwebhelper: defaulting to /home/username/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[105773]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
BuildCompleteAppOverviewChange: 353 apps
RegisterForAppOverview 1: 14ms
RegisterForAppOverview 2: 14ms
There are several workarounds to get steam running.
Which lib did you install? I also had steam first running with lib32-libudev0-shim but after a restart it crashed again, then i delete lib32-libudev0-shim and reinstalled it and since then steam is running flawless.
I have no idea why i had to reinstalled, i was expecting that i had to reinstall lib32-libudev0-shim after every system restart, but i was wrong.
--------------------------------------------------------------------------------------------------------------------------------
I have several Pamac GUI crashes since this update on my Laptop and also on my PC
when i switch though the menue sections its randomly crash after time.
God help us, when this crashes happend on a big updates -.-
systemd-coredump[9744]: [🡕] Process 9272 (pamac-manager) of user 1000 dumped core.
Stack trace of thread 9272:
#0 0x00007f160991cf20 alpm_pkg_get_origin (libalpm.so.13 + 0x17f20)
#1 0x00007f160a63fbe7 n/a (libpamac.so.11 + 0x22be7)
#2 0x00007f160a63fc88 n/a (libpamac.so.11 + 0x22c88)
#3 0x00005646222205d9 n/a (pamac-manager + 0x155d9)
#4 0x00007f160a896d9d n/a (libglib-2.0.so.0 + 0x5fd9d)
#5 0x00007f160a896d37 n/a (libglib-2.0.so.0 + 0x5fd37)
#6 0x00007f160a896d29 n/a (libglib-2.0.so.0 + 0x5fd29)
#7 0x00007f160a896d29 n/a (libglib-2.0.so.0 + 0x5fd29)
#8 0x00007f160a896d29 n/a (libglib-2.0.so.0 + 0x5fd29)
#9 0x00007f160a896d37 n/a (libglib-2.0.so.0 + 0x5fd37)
#10 0x00007f160a896d29 n/a (libglib-2.0.so.0 + 0x5fd29)
#11 0x00007f160a896d29 n/a (libglib-2.0.so.0 + 0x5fd29)
#12 0x00007f160a89af10 n/a (libglib-2.0.so.0 + 0x63f10)
#13 0x000056462222327a n/a (pamac-manager + 0x1827a)
#14 0x000056462222acac n/a (pamac-manager + 0x1fcac)
#15 0x000056462222aeba n/a (pamac-manager + 0x1feba)
#16 0x00007f160aa8c644 n/a (libgio-2.0.so.0 + 0xa8644)
#17 0x00007f160aa906ad n/a (libgio-2.0.so.0 + 0xac6ad)
#18 0x000056462223b9f1 n/a (pamac-manager + 0x309f1)
#19 0x0000564622232416 n/a (pamac-manager + 0x27416)
#20 0x00007f160aa8c644 n/a (libgio-2.0.so.0 + 0xa8644)
#21 0x00007f160aa906ad n/a (libgio-2.0.so.0 + 0xac6ad)
#22 0x00007f160a665fae n/a (libpamac.so.11 + 0x48fae)
#23 0x00007f160a891a31 g_main_context_dispatch (libglib-2.0.so.0 + 0x5aa31)
#24 0x00007f160a8eecc9 n/a (libglib-2.0.so.0 + 0xb7cc9)
#25 0x00007f160a88f0e2 g_main_context_iteration (libglib-2.0.so.0 + 0x580e2)
#26 0x00007f160aac1ed6 g_application_run (libgio-2.0.so.0 + 0xdded6)
#27 0x0000564622218423 n/a (pamac-manager + 0xd423)
#28 0x00007f160a456850 n/a (libc.so.6 + 0x23850)
#29 0x00007f160a45690a __libc_start_main (libc.so.6 + 0x2390a)
#30 0x0000564622218555 n/a (pamac-manager + 0xd555)
Stack trace of thread 9274:
#0 0x00007f160a5362ed syscall (libc.so.6 + 0x1032ed)
#1 0x00007f160a8e6ca7 g_cond_wait (libglib-2.0.so.0 + 0xafca7)
#2 0x00007f160a85c144 n/a (libglib-2.0.so.0 + 0x25144)
#3 0x00007f160a8c62fe n/a (libglib-2.0.so.0 + 0x8f2fe)
#4 0x00007f160a8c3d75 n/a (libglib-2.0.so.0 + 0x8cd75)
#5 0x00007f160a4ba44b n/a (libc.so.6 + 0x8744b)
#6 0x00007f160a53de40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 9276:
#0 0x00007f160a530c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007f160a8eec2f n/a (libglib-2.0.so.0 + 0xb7c2f)
#2 0x00007f160a890fef g_main_loop_run (libglib-2.0.so.0 + 0x59fef)
#3 0x00007f160aaf428c n/a (libgio-2.0.so.0 + 0x11028c)
#4 0x00007f160a8c3d75 n/a (libglib-2.0.so.0 + 0x8cd75)
#5 0x00007f160a4ba44b n/a (libc.so.6 + 0x8744b)
#6 0x00007f160a53de40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 9275:
#0 0x00007f160a530c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007f160a8eec2f n/a (libglib-2.0.so.0 + 0xb7c2f)
#2 0x00007f160a88f0e2 g_main_context_iteration (libglib-2.0.so.0 + 0x580e2)
#3 0x00007f160a88f132 n/a (libglib-2.0.so.0 + 0x58132)
#4 0x00007f160a8c3d75 n/a (libglib-2.0.so.0 + 0x8cd75)
#5 0x00007f160a4ba44b n/a (libc.so.6 + 0x8744b)
#6 0x00007f160a53de40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 9304:
#0 0x00007f160a530c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007f160a8eec2f n/a (libglib-2.0.so.0 + 0xb7c2f)
#2 0x00007f160a88f0e2 g_main_context_iteration (libglib-2.0.so.0 + 0x580e2)
#3 0x00007f15fe7aefde n/a (libdconfsettings.so + 0x5fde)
#4 0x00007f160a8c3d75 n/a (libglib-2.0.so.0 + 0x8cd75)
#5 0x00007f160a4ba44b n/a (libc.so.6 + 0x8744b)
#6 0x00007f160a53de40 n/a (libc.so.6 + 0x10ae40)
ELF object binary architecture: AMD x86-64
░░ Subject: Process 9272 (pamac-manager) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 9272 (pamac-manager) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Okay i have Meld installed now, but Related to the file permissions what you suggested, how should i save the changes?
When i use pacdiff -S it cycles though all .pacnew files, and i viewed a few pacnew files with v and i saved the files with Meld after i edited them but is that the right way to handle the permissions?
I just wanted to be sure, because there is also m for merge and i have no clue what merge exactly does and where is the difference between merge and overwrite in pacdiff?
So is there a difference related to replace (viewed/edited till files are identical lead to autodelete, i found out) with meld or overwrite with pacdiff?
run pacdiff -s
choose view the file.
edit the changes you want and save in meld and close it.
choose remove in the pacdiff question (it is still the same file you choosed to view).
repeat procedure until pacdiff no longer asks.
The risk with overwriting is if you have added anything in the file, that will disappear.
If you are 1000% sure you have not, or anything else (like an installed program you have) have made any changes from default, then it’s most likely fine to overwrite.
As for merge, I got it described as “not optimal” to do. You do what you want with that answer.
today, after installed a libpamac 11.5.7 and a couple days from this the updater works fine and correct: I used a terminal for checking update (sudo pacman -Syu and pamac upgrade -a) for this days but today the terminal and GUI pamac has same picture.
However, the problem with screen resolution with 6.4 kernel for now isn’t been
Thank you, that worked as intended, I just commented those lines.
Not sure why it didn’t do it as it should.
I didn’t notice the first post about it, so sorry for that.