Hello,
I am getting the message
“updates_checker.vala:59: check updates”
whenever the system auto-checks for updates ever since I put the line
IgnorePkg = gimp*
in my pacman.conf file. I would like to ask for help stopping this.
BTW, the message is always accompanied by a warning
“tray.vala:136: Error receiving data: Connection reset by peer”
System is completely up-to-date Intel 64 Manjaro (excepting gimp, which broke my scriptfu).
Thanks in advance,
Ken Koehler
Remove the IgnorePkg = gimp* line from /etc/pacman.conf.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
Output of this command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide more information and outputs from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Regards.
It must be pointed out that if you withhold packages, your system is not completely up-to-date, and is therefore in an unsupported state. 
I would suggest a containerized version such as an AppImage or Flatpak, with which it is (supposedly) possible to get older builds, until you can get your scripts to work with the upcoming versions; please note I have absolutely no experience with such package systems at present (I use the repos and, for a few packages, the AUR), so this requires some more research on my part.
Another alternative, would be to install it in a Virtual Machine, for now at least, using e.g. a Debian (based) distro, until these scripts are updated by the maintainers. GIMP 3 still quite “fresh-out-of-the-box”.
I’m using GIMP 3.0.2 and have found no issues.
I note there seems to have been a spate, or perhaps a spatter, of users choosing to ignore random applications lately - monkey see, monkey do - many of these instances were likely unnecessary. 
Since it is allowed by pacman, it should be perfectly “legal” to blacklist an isolated application without constantly getting error messages.
In this case, I am doing so because Gimp 3 requires wholesale changes to any scriptfu (scheme) scripts, which I have a ton of, and I have yet to find any useful way to simply migrate them from Gimp 2.10. If anyone knows a straightforward way of doing this, I’d be happy to resume using Gimp 3.
Perhaps this will be useful;
“Legitimate” is probably the word you were aiming for; and I agree, at least, up to the point where doing so affects the system.
While short-term downgrading of a typical userland application is perfectly valid, system packages and packages that directly interact with system packages are another story. Sometimes yes, mostly not.
In a rolling release distribution such as Manjaro or Arch that could easily be a recipe for what we call an unsupported state, where package versions on your machine become distanced from those of the usual sync/update system.
Maintaining your system in a predictably stable state becomes increasingly difficult. These are the times when so many scream “the update broke (whatever)” - actually, it’s quite the opposite - lack of proper maintenance is typically the real culprit.
I’m rather tired; hopefully the logic was easy to follow. 
Regards.
Thanks. The link was very useful, in so far as it (and other docs mentioned therein) convinced me that I have a lot of work to do before I could consider upgrading to Gimp 3.
So that leaves me with the irritation of all these messages…
Maybe you don’t need to use that wildcard - or not like that.
gimp
and
gimp-plugin-gmic
seem to be the only ones that “need to be” blocked
Put the first one or both on ignore - instead of the wildcard?
… isn’t there an AppImage of the older Gimp?
Install and use that - and don’t have to worry about Gimp from the repo at all.
There’s a G’Mic plugin for Gimp available for Gimp 3, I have it installed, myself. I might have misinterpreted your comment, though.
It did appear to indicate the path to converting the scripts. As with anything, if it’s worth doing, the time spent to do it right is often warranted, rather than looking for a shortcut; a quick fix.
Regards.
An update: I removed my changes to pacman.conf and opened the pamac-manager plug-in and in preferences/advanced, added gimp to the ignored upgrades list. This introduced the line
IgnorePkg = gimp
to pacman.conf.
However, every time I open the pamac-manager plug-in, I get the Gdk-CRITICAL error
“gdk_window_set_cursor: assertion ‘GDK_IS_WINDOW (window)’ failed”.
This has to be a bug, IMHO.
This condition persists under xfce themes
Default, Daloa, Kok0di, Matcha, Moheli and Vimix.
When I refresh databases (preferences) I still get the errors
“updates_checker.vala:59: check updates”
“tray.vala:136: Error receiving data: Connection reset by peer”
Mod edit:- your misspelling of pamac-manager has been corrected for you, this one time. In future, please correct any mistakes when brought to your attention, in the interest of accuracy and to avoid possible confusion of those who may read this topic at a future time.
is unlikely to be related to:
It is pamac-manager - not pacman-manager (there is no such thing)
I can’t reproduce the issue at all
by inserting
IgnorePkg = gimp
or
IgnorePkg = gimp*
… simply nothing happens - not the error message in the title of this post, and not this one either
“gdk_window_set_cursor: assertion ‘GDK_IS_WINDOW (window)’ failed”
I’m sorry, I was not clear. I did not intend to imply a relationship between gimp and pamac-manager (sorry about the misspelling). May I ask what version of pamac-manager and which WM and theme you are using?
I’m not really using it - I just tried to replicate the issue by putting.
gimp*
or
gimp
on the ignore list.
I did this in an Xfce4 VM - I have two of them.
Both of them nearly unchanged - default theme and fully updated.
In one I have completely removed pamac,
in the other (where I tried this) only the update checker is disabled -
but I did enable it in order to test this.
Every time I open pamac-manager, I get Gdk-CRITICAL error
“gdk_window_set_cursor: assertion ‘GDK_IS_WINDOW (window)’ failed”
WM is Xfce4 4.20.2-1 running on intel-64
Something failed (I don’t know what) - but it is not an error, just a message.
I get the same message when I start pamac-manager from terminal.
pamac-manager
(pamac-manager:1115): Gdk-CRITICAL **: 20:19:33.059: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
inxi -zv8 gives me this line in it’s output:
Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
Is your system up to date (you said so in the other thread)?
sudo pacman-mirrors -c Germany
or
sudo pacman-mirrors -f
then:
sudo pacman -Syu
but as I said: I get this message too
terminal invocation likewise. same inxi output as you. system is up to date.
Please provide system information as described (below).
Output of this command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide more information and outputs from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
My Xfce system has a similar “Gdk-Critical” error
(pamac-manager:187139): Gdk-CRITICAL **: 10:45:06.802: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
but GUI works normally
Sorry, I posted the system info to
I started that thread to disconnect the pamac-manager bug from my gimp issues.