Re: Utiliser G'MIC dans gimp
Le Thu, 30 Nov 2023 16:37:23 +, benoit a écrit : > Je me répond ! > Désolé, je n'avais pas essayé... > Ca s'active quand on ouvre une image > > Benoit Avant de se plaindre que ça ne marche pas, brancher ;) C'est un exercice mental très sain de se remémorer de temps en temps les bases : les menus sont contextuels, donc activés en fonction du type de l'image ouverte.
Re: Utiliser G'MIC dans gimp
Le jeudi 30 novembre 2023 à 17:11, benoit a écrit : > Bonjour, > > J'ai installé le paquet gimp-gmic, mais c'est grisé dans gimp > > https://packages.debian.org/bookworm/gimp-gmic > > Je ne sais pas comme l'activer. Je me répond ! Désolé, je n'avais pas essayé... Ca s'active quand on ouvre une image Benoit
Utiliser G'MIC dans gimp
Bonjour, J'ai installé le paquet gimp-gmic, mais c'est grisé dans gimp https://packages.debian.org/bookworm/gimp-gmic Je ne sais pas comme l'activer. Merci d'avance -- Benoit Envoyé avec la messagerie sécurisée [Proton Mail.](https://proton.me/)
Re: Crosshairs in gimp 2.10.22 in Debian 11.7.
From: Dan Ritter Date: Sat, 12 Aug 2023 06:44:05 -0400 > Not by default. If someone finds an add-on providing lines intersecting at the hotpoint, a link will help. Thanks. > What you do get is an indicator triangle on the left and top rulers > that follows the cursor. OK, thanks. With a line being more than one point, the ruler points don't answer the requirement. Thanks for the reply, ... P. - mobile: +1 778 951 5147 VoIP: +1 604 670 0140
Re: Crosshairs in gimp 2.10.22 in Debian 11.7.
pe...@easthope.ca wrote: > I've retrieved 'Gregs Crosshairs.scm.zip' and unzipped to > /home/me/.config/GIMP/2.10/scripts/GregsCrosshairs.scm. > > If an image is open, Image > Guides gives a menu with four options. > New guide (by Percent)... > New guide... > New Guides from Selection > Remove all Guides > > "New guide" allows creation of a horizontal or vertical dashed line > at a specified fixed location. > > Can gimp have window sized crosshairs? Ie. horizontal and vertical > lines intersecting at the mouse pointer hotpoint. Not by default. What you do get is an indicator triangle on the left and top rulers that follows the cursor. -dsr-
Crosshairs in gimp 2.10.22 in Debian 11.7.
I've retrieved 'Gregs Crosshairs.scm.zip' and unzipped to /home/me/.config/GIMP/2.10/scripts/GregsCrosshairs.scm. If an image is open, Image > Guides gives a menu with four options. New guide (by Percent)... New guide... New Guides from Selection Remove all Guides "New guide" allows creation of a horizontal or vertical dashed line at a specified fixed location. Can gimp have window sized crosshairs? Ie. horizontal and vertical lines intersecting at the mouse pointer hotpoint. Thanks,... P. - mobile: +1 778 951 5147 VoIP: +1 604 670 0140
Re: Gimp 2.10 en français impossible
On Friday 21 July 2023 00:09:42 Yannick wrote: > Le 20/07/2023 à 20:11, ajh-valmer a écrit : > > Je suis sous Bookworm. > > Gimp fonctionne bien, mais impossible de le mettre en français. > > Il n'y a aucune mention des langues sauf le fichier "gimp-help-fr". > > Dans Edit => Preferences => interfaces, pas de français, > > que l'anglais US. > > Dans mon répertoire user j'ai 2 répertoires ".gimp-2.6" et ".gimp-2.8", > > pas de ".gimp-2.10". > Vu que ce qu'on t'a proposé jusqu'à présent ne marche pas je te suggère ceci > Supprimer tout ce qui a rapport à GIMP y compris la version 10 > Réinstaller une version propre de la version 10 > Je ne vais pas te donner de ligne de commande car je fais tout cela avec > Synaptic quand je suis seul, au moins je sais ce que je fais sans > prendre de risque de faire une bêtise qui aggraverait les choses. > Je te suggère de modifier la langue système en UTF8 auparavant bien sûr. Bonjour, J'ai purgé Gimp, et l'ai réinstallé avec flatpak (ex-xdg-app), (https://fr.wikipedia.org/wiki/Flatpak). Cette méthode est proposée sur le site de gimp : https://www.gimp.org/downloads/ Est-ce une bonne idée ? J'ignorais cet outil. Pour le lancer, il faut taper cette commande abscons : flatpak run org.gimp.GIMP//stable ou la mettre dans les propriétés d'une icône sur le bureau. Gimp 2.10.34 s'ouvre bien en français sans rien toucher aux locales. Si j'avais tapé "apt install gimp", j'aurais retrouvé gimp en anglais. @+ Bonne journée.
Re: Gimp 2.10 en français impossible
Bonjour, Pour traduire des fichiers d’un codage vers un autre il existe « iconv » qui fait ça très bien. % iconv -f latin9 -t UTF-8 toto.txt Par exemple pour traduire un codage « latin9 » vers de l’UTF-8. En combinant ça avec un « file -i » on peut effectuer un traitement au besoin et traiter tous ces vieux codages obsolètes. Bonne journée > Le 21 juil. 2023 à 08:46, Michel Verdier a écrit : > > Le 20 juillet 2023 benoit a écrit : > >> Du coup tous tes fichiers texte brut en français écrit avec le codage latin >> ne seront plus lisibles(les caractères accentués illisibles) en UTF-8 ! :( >> Mais il y a des outils pour convertir latin vers UTF >> Il faudra peut-être revenir en latin le temps de convertir tous les fichiers >> écrits avec des accents... > > Ça reste galère même avec les outils parce qu'il faut convertir seulement > ce qui est latin1 sinon on obtient un double encodage utf8 qui casse tout. > Mais déjà pour résoudre le problème de gimp il suffit de le lancer en > positionnant LANG auparavant, éventuellement en mettant ça dans un script : > > LANG=fr_FR.UTF-8 > /usr/bin/gimp > -- Pierre Malard «Mittler zwischen hirn und händen muss das hirz sein !» «La médiation entre le cerveau et les mains doit être le cœur !» Fritz Lang - "Métropolis" - 1929 |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- signature.asc Description: Message signed with OpenPGP
Re: Gimp 2.10 en français impossible
Le 20 juillet 2023 benoit a écrit : > Du coup tous tes fichiers texte brut en français écrit avec le codage latin > ne seront plus lisibles(les caractères accentués illisibles) en UTF-8 ! :( > Mais il y a des outils pour convertir latin vers UTF > Il faudra peut-être revenir en latin le temps de convertir tous les fichiers > écrits avec des accents... Ça reste galère même avec les outils parce qu'il faut convertir seulement ce qui est latin1 sinon on obtient un double encodage utf8 qui casse tout. Mais déjà pour résoudre le problème de gimp il suffit de le lancer en positionnant LANG auparavant, éventuellement en mettant ça dans un script : LANG=fr_FR.UTF-8 /usr/bin/gimp
Re: Gimp 2.10 en français impossible
Le 20/07/2023 à 20:11, ajh-valmer a écrit : Hello, Je suis sous Bookworm. Gimp fonctionne bien, mais impossible de le mettre en français. Il n'y a aucune mention des langues sauf le fichier "gimp-help-fr". Dans Edit => Preferences => interfaces, pas de français, que l'anglais US. Dans mon répertoire user j'ai 2 répertoires ".gimp-2.6" et ".gimp-2.8", pas de ".gimp-2.10". Bonsoir, Vu que ce qu'on t'a proposé jusqu'à présent ne marche pas je te suggère ceci Supprimer tout ce qui a rapport à GIMP y compris la version 10 Réinstaller une version propre de la version 10 Je ne vais pas te donner de ligne de commande car je fais tout cela avec Synaptic quand je suis seul, au moins je sais ce que je fais sans prendre de risque de faire une bêtise qui aggraverait les choses. Je te suggère de modifier la langue système en UTF8 auparavant bien sûr. Amitiés -- Yannick VOYEAUD Nul n'a droit au superflu tant que chacun n'a pas son nécessaire (Camille JOUFFRAY 1841-1924, maire de Vienne) http://www.voyeaud.org Créateur CimGenWeb: http://www.francegenweb.org/cimgenweb/ Journées du Logiciel Libre: http://jdll.org Généalogie en liberté avec Ancestris https://www.ancestris.org OpenPGP_signature Description: OpenPGP digital signature
Re : Re: Gimp 2.10 en français impossible
Le jeudi 20 juillet 2023 à 23:27, benoit a écrit : > Le jeudi 20 juillet 2023 à 23:19, ajh-valmer ajh.val...@free.fr a écrit : > > > > > Chez moi : > > $ echo $LANG > > fr_FR@euro > > > C'est pas l'ancien codage latin ça ( ISO-8859-15 je crois) ? > Ca fait dix ans que c'est obsolète non ? > > Je ne suis pas sûr, mais à tout hasard, ça ne coûte rien d'essayer en root : > dpkg-reconfigure locales > > passer en UTF-8 voir ce que ça donne... Du coup tous tes fichiers texte brut en français écrit avec le codage latin ne seront plus lisibles(les caractères accentués illisibles) en UTF-8 ! :( Mais il y a des outils pour convertir latin vers UTF Il faudra peut-être revenir en latin le temps de convertir tous les fichiers écrits avec des accents...
Re : Re: Gimp 2.10 en français impossible
Le jeudi 20 juillet 2023 à 23:19, ajh-valmer a écrit : > > Chez moi : > $ echo $LANG > fr_FR@euro C'est pas l'ancien codage latin ça ( ISO-8859-15 je crois) ? Ca fait dix ans que c'est obsolète non ? Je ne suis pas sûr, mais à tout hasard, ça ne coûte rien d'essayer en root : dpkg-reconfigure locales passer en UTF-8 voir ce que ça donne...
Re: Gimp 2.10 en français impossible
On Thursday 20 July 2023 22:47:58 benoit wrote: > Le jeudi 20 juillet 2023 à 21:39, NoSpam a écrit : > > Mon Gimp 2.10 est en FR sans avoir à rajouter (language "fr") Essayez en > > supprimant cette ligne et voyez si dans votre /etc/gimp/2.0 il n'y > > aurai pas une instruction forçant EN > C'est en Fr parce que c'est la : Langue du système > Dans le champs Langue de la config Edition-> préférence-> Interface > Si dans la home de l’utilisateur : > echo $LANG > N'est pas fr_FR.UTF-8 (ou un truc du genre) > Ca n'ira pas... : Chez moi : $ echo $LANG fr_FR@euro
Re : Re: Gimp 2.10 en français impossible
Le jeudi 20 juillet 2023 à 21:39, NoSpam a écrit : > Mon Gimp 2.10 est en FR sans avoir à rajouter (language "fr") Essayez en > supprimant cette ligne et voyez si dans votre /etc/gimp/2.0 il n'y > aurai pas une instruction forçant EN C'est en Fr parce que c'est la : Langue du système Dans le champs Langue de la config Edition-> préférence-> Interface Si dans la home de l’utilisateur : echo $LANG N'est pas fr_FR.UTF-8 (ou un truc du genre) Ca n'ira pas... -- Benoit
Re: Gimp 2.10 en français impossible
Le 20/07/2023 à 21:24, ajh-valmer a écrit : J'ai supprimé /.gimp-2.6 et ~/.gimp-2.8, d'après les docs, il faut écrire : (language "fr"), hélas, ça marche pas. Est-ce qu'une version Gimp en français existe pour Linux ? (j'ai vraiment cherché avec moteur de recherche). Bonne soirée. Gimp est multilingue essaie d'aller dans les menus de préférences de Gimp pour régler ça: ici en français ça donne Edition/Préférences/Interface/langue (en anglais un truc du style Edit/Preferences/Interface/Language) où si ton système est correctement configuré en français tu dois pouvoir laisser la valeur par défaut : "langue système" (system language), sinon tu peux forcer "français (fr)" (french (fr))
Re: Gimp 2.10 en français impossible
Mon Gimp 2.10 est en FR sans avoir à rajouter (language "fr") Essayez en supprimant cette ligne et voyez si dans votre /etc/gimp/2.0 il n'y aurai pas une instruction forçant EN Dans ~/.config/GIMP en majuscules au cas ou ... Le 20/07/2023 à 21:24, ajh-valmer a écrit : On Thursday 20 July 2023 20:31:07 steve wrote: Sauf erreur, les fichiers de configurations de Gimp sous bookworm se trouvent dans ~/.config/GIMP/2.10/. Dans ce répertoire, il y a un fichier gimprc où tu devrais pouvoir ajouter une ligne (language fr) et ça devrait marcher. Par contre, c'est une bidouille parce que gimp est censé détecter la langue de ton système automatiquement. Peut-être que les deux répertoires ~/.gimp-2.6 et ~/.gimp-2.8 interfèrent et leur suppression pourrait aider. Essaie déjà de les déplacer et vois si ça change quelque chose. Merci. J'ai supprimé /.gimp-2.6 et ~/.gimp-2.8, d'après les docs, il faut écrire : (language "fr"), hélas, ça marche pas. Est-ce qu'une version Gimp en français existe pour Linux ? (j'ai vraiment cherché avec moteur de recherche). Bonne soirée.
Re: Gimp 2.10 en français impossible
On Thursday 20 July 2023 20:31:07 steve wrote: > Sauf erreur, les fichiers de configurations de Gimp sous bookworm se > trouvent dans ~/.config/GIMP/2.10/. Dans ce répertoire, il y a un > fichier gimprc où tu devrais pouvoir ajouter une ligne > (language fr) > et ça devrait marcher. > Par contre, c'est une bidouille parce que gimp est censé détecter la > langue de ton système automatiquement. Peut-être que les deux > répertoires ~/.gimp-2.6 et ~/.gimp-2.8 interfèrent et leur suppression > pourrait aider. Essaie déjà de les déplacer et vois si ça change quelque > chose. Merci. J'ai supprimé /.gimp-2.6 et ~/.gimp-2.8, d'après les docs, il faut écrire : (language "fr"), hélas, ça marche pas. Est-ce qu'une version Gimp en français existe pour Linux ? (j'ai vraiment cherché avec moteur de recherche). Bonne soirée.
Re: Gimp 2.10 en français impossible
Salut, Sauf erreur, les fichiers de configurations de Gimp sous bookworm se trouvent dans ~/.config/GIMP/2.10/. Dans ce répertoire, il y a un fichier gimprc où tu devrais pouvoir ajouter une ligne (language fr) et ça devrait marcher. Par contre, c'est une bidouille parce que gimp est censé détecter la langue de ton système automatiquement. Peut-être que les deux répertoires ~/.gimp-2.6 et ~/.gimp-2.8 interfèrent et leur suppression pourrait aider. Essaie déjà de les déplacer et vois si ça change quelque chose. J'espère que ça aide.
Gimp 2.10 en français impossible
Hello, Je suis sous Bookworm. Gimp fonctionne bien, mais impossible de le mettre en français. Il n'y a aucune mention des langues sauf le fichier "gimp-help-fr". Dans Edit => Preferences => interfaces, pas de français, que l'anglais US. Dans mon répertoire user j'ai 2 répertoires ".gimp-2.6" et ".gimp-2.8", pas de ".gimp-2.10". Merci de votre aide. Bonne soirée.
gimp scripts
It would be useful to toggle the visibility of 2 layers in Gimp. somebody posted a script here. https://www.gimpusers.com/forums/gimp-user/19918-toggle-visibility-of-two-layers#message87577 Which works but the dialogue comes up each time so is not proper toggling. It's just as quick to click on the visibility in the layers window. I'd rather not learn how these scripts work if I don't have to. Anybody able to post adjustment to the guy's script to just toggle the top 2 layers without the dialogue? cheers mick
[HORS SUJET] Plugin Darktable dans Gimp
Bonjour à tou·te·s Dans gimp 2.10 il y a une fonctionnalité d’interopérabilité avec Darktable qui permet d'ouvrir un ficher RAW dans Darktable à partir de Gimp, faire les modifs qu'on veut dans darktable, fermer la fenêtre et gimp va ouvrir le fichier RAW modifié. Ma demande d'aide semble hors sujet, mais pas vraiment, car ça fonctionne parfaitement en Debian testing et pas en stable, d'où ma question sur la liste Debian. --- GIMP Message : Calling error for procedure 'gimp-file-load': Error opening file '/tmp/gimp/2.10/gimp-temp-253451.exr' for reading GIMP Message Opening '/home/benoit/RAW/D7100/DCIM/111D7100/NII_2044.NEF' failed: Raw Nikon plug-in could not open image --- C'est pas le Raw Nikon plug-in, car j'ai essayé avec le fichier RAW d'un Pentax et j'ai le même problème. Merci d'avance, -- Benoit Envoyé avec la messagerie sécurisée [Proton Mail](https://proton.me/).
Re: Installer GIMP 2.10.28
On Saturday 04 December 2021 17:36:19 Michel Memeteau - EKIMIA wrote: > Sinon plus simple > https://snapcraft.io/install/gimp/debian Super, réponse fonctionnelle qui m'a fait passer de la version Gimp 2.10.8 à 2.10.22. Merci ! (je verrai lors de la migration Buster=> Bullseye pour passer à la version 2.10.28,). AJH Valmer. PS : ... pas comme celle abstruse, en impasse de b.schoenac...@free.fr. > Le ven. 3 déc. 2021 à 18:59, ajh-valmer a écrit : > > Je suis sous Buster, avec la version Gimp 2.10.8 > > Je souhaite passer à la version 2.10.28. > > Sur le site de gimp il faut installer "flatpak", ce que j'ai fait. > > Après, je ne comprends pas comment installer Gimp avec "flatpak", > > quel est cet outil ? Je lis : > > Flatpak est un système de virtualisation d’application pour les > > distributions GNU/Linux de bureau. > > Quel rapport avec Gimp ? > > A. Valmer
Re: Installer GIMP 2.10.28
Sinon plus simple https://snapcraft.io/install/gimp/debian [image: photo] *Michel Memeteau* Directeur, Ekimia SAS +33 (0)9 72 30 83 34 <+33+9+72+30+83+34> | m...@ekimia.fr | Notre WebBoutique : https://shop.ekimia.fr <https://shop.ekimia.fr/> | 620 avenue de la roche fourcade 13400 Aubagne FRANCE <http://facebook.com/ekimiashop> <https://fr.linkedin.com/pub/michel-memeteau/50/793/126> <http://twitter.com/ekimiainfo> Contactez nous directement par Tchat sur http://bit.ly/ekitchat <http://bit.ly/ekitchat> Le ven. 3 déc. 2021 à 18:59, ajh-valmer a écrit : > Hello, > > Je suis sous Buster, avec la version Gimp 2.10.8 > Je souhaite passer à la version 2.10.28. > Sur le site de gimp il faut installer "flatpak", ce que j'ai fait. > Après, je ne comprends pas comment installer Gimp avec "flatpak", > quel est cet outil ? > Je lis : > Flatpak est un système de virtualisation d’application pour les > distributions GNU/Linux de bureau. > Quel rapport avec Gimp ? > > Sinon, il y a un paquet "the-gimp_2-10-28_fr_214450.tar.bz2", > téléchargé sur le site clubic. > > Quel choix adopter, et faut-il avant supprimer Gimp 2.10.8 complètement ? > > Merci de votre éclairage, bonne soirée. > > A. Valmer > >
Re: Installer GIMP 2.10.28
Le vendredi 03 décembre 2021 à 19:34 +0100, ajh-valmer a écrit : > On Friday 03 December 2021 19:16:46 MERLIN Philippe wrote: > > Le vendredi 3 décembre 2021, 18:59:06 CET ajh-valmer a écrit : > > > Je suis sous Buster, avec la version Gimp 2.10.8 > > > Je souhaite passer à la version 2.10.28. > > > Sur le site de gimp il faut installer "flatpak", ce que j'ai > > > fait. > > > Après, je ne comprends pas comment installer Gimp avec "flatpak", > > > quel est cet outil ? > > > Je lis : > > > Flatpak est un système de virtualisation d’application pour les > > > distributions GNU/Linux de bureau. Quel rapport avec Gimp ? > > > Sinon, il y a un paquet "the-gimp_2-10-28_fr_214450.tar.bz2", > > > téléchargé sur le site clubic. > > > Quel choix adopter, et faut-il avant supprimer Gimp 2.10.8 > > > complètement ? > > > Merci de votre éclairage, bonne soirée. > > > Plus simple la version Gimp 2.10.28-1 est disponible en SID > > (unstable) > > Comment installer la version Gimp 2.10.28-1 disponible en SID, > si je suis sous Buster ? > La version que tu souhaites est disponible dans unstable, Si tu es sous stable, tu peux installer des paquets de la version unstable avec le pinning, ce n'est pas tres compliqué, il faut se mefier des paquets qui peuvent être "tirés" avec ton paquet désiré. - il te faut modifier ton sources.list - editer un fichier preferences et utiliser "-t unstable" dans ta commande apt install et reflechir... Une petite recherche apt pinning debian devrait te donner toutes les clefs. Christophe
Re: Installer GIMP 2.10.28
Le 03/12/2021 à 19:16, MERLIN Philippe a écrit : Le vendredi 3 décembre 2021, 18:59:06 CET ajh-valmer a écrit : Hello, Je suis sous Buster, avec la version Gimp 2.10.8 Je souhaite passer à la version 2.10.28. Sur le site de gimp il faut installer "flatpak", ce que j'ai fait. Après, je ne comprends pas comment installer Gimp avec "flatpak", quel est cet outil ? Tu peux regarder les informations sur le paquet https://packages.debian.org/buster-backports/flatpak Puis lire cette page pas encore traduite en français pour savoir comment l'utiliser : https://wiki.debian.org/FlatPak Amicalement, Jean-Pierre Giraud Je lis : Flatpak est un système de virtualisation d’application pour les distributions GNU/Linux de bureau. Quel rapport avec Gimp ? Sinon, il y a un paquet "the-gimp_2-10-28_fr_214450.tar.bz2", téléchargé sur le site clubic. Quel choix adopter, et faut-il avant supprimer Gimp 2.10.8 complètement ? Merci de votre éclairage, bonne soirée. A. Valmer Plus simple la version Gimp 2.10.28-1 est disponible en SID (unstable) Amitiés. Philippe Merlin
Re: Installer GIMP 2.10.28
On Friday 03 December 2021 20:43:32 Bernard Schoenacker wrote
Pourquoi me répondre par 3 mails identiques ?
(un me suffit, et surtout vu les réponses).
> J'ai bien l'impression de réaliser une prestation de service avec
> une rémunération gratis pro deo :
Heureusement que j'ai pas payé ante service.
> Merci de bien vouloir relire ce que j'ai donné et réfléchir...
> dpkg -l |awk '/gimp/ {print $2,$3}' :
gimp 2.10.8-2
gimp-data 2.10.8-2
gimp-gmic 2.4.5-1
gimp-help-common 2.8.2-1
gimp-help-fr 2.8.2-1
gimp-plugin-registry 9.20180625
gimp-python 2.10.8-2
libgimp2.0 2.10.8-2
Voilà et ensuite... ?
Je pense que Gimp-2.10.28 n'est pas compatible avec Buster.
> "Le comportement consumériste et asymétrique ne me sied guère" :
Ça ne veut strictement rien dire, si tu appartiens au parti du polichinellisme,
pas moi.
Re: Installer GIMP 2.10.28
- Mail original -
> De: "ajh-valmer"
> À: debian-user-french@lists.debian.org
> Envoyé: Vendredi 3 Décembre 2021 20:11:36
> Objet: Re: Installer GIMP 2.10.28
>
> gimp, gimp-data, gimp-gmic, gimp-help-common, gimp-help-fr,
> gimp-plugin-registry
> gimp-python, libgimp2.0
> Ces infos ne donnent pas ma version de Gimp.
>
>
> n'affiche rien.
>
> Je désire installer gimp 2.10.28 (si c'est possible sous Buster).
>
bonjour,
dpkg -l |awk '/gimp/ {print $2,$3}'
J'ai bien l'impression de réaliser une prestation de service avec
une rémunération gratis pro deo
Merci de bien vouloir relire ce que j'ai donné et réfléchir ...
Le comportement consumériste et asymétrique ne me sied guère
Bien à toi
Bernard
Re: Installer GIMP 2.10.28
On Friday 03 December 2021 19:49:09 Bernard Schoenacker wrote:
> > Comment installer la version Gimp 2.10.28-1 disponible en SID,
> > si je suis sous Buster ?
> dpkg -l |awk '/gimp/ {print $2}' :
gimp, gimp-data, gimp-gmic, gimp-help-common, gimp-help-fr, gimp-plugin-registry
gimp-python, libgimp2.0
Ces infos ne donnent pas ma version de Gimp.
> apt-cache show $(dpkg -l |awk '/gimp/ {print $2}')|grep File |grep 2.10.28 :
n'affiche rien.
Je désire installer gimp 2.10.28 (si c'est possible sous Buster).
Re: Installer GIMP 2.10.28
- Mail original -
> De: "ajh-valmer"
> À: debian-user-french@lists.debian.org
> Cc: "MERLIN Philippe"
> Envoyé: Vendredi 3 Décembre 2021 19:34:51
> Objet: Re: Installer GIMP 2.10.28
>
> Comment installer la version Gimp 2.10.28-1 disponible en SID,
> si je suis sous Buster ?
>
bonjour,
En premier, prière de donner la liste des paquets installés :
dpkg -l |awk '/gimp/ {print $2}'
Pour obtenir les paquets :
apt-cache show $(dpkg -l |awk '/gimp/ {print $2}') |grep File |grep 2.10.28
Filename: pool/main/g/gimp/gimp_2.10.28-1_amd64.deb
Filename: pool/main/g/gimp/gimp-data_2.10.28-1_all.deb
Filename: pool/main/g/gimp/libgimp2.0_2.10.28-1_amd64.deb
les paquets suivants :
Filename: pool/main/g/gimp-data-extras/gimp-data-extras_2.0.2-1.1_all.deb
Filename: pool/main/g/gimp-help/gimp-help-common_2.10.0-1_all.deb
Filename: pool/main/g/gimp-help/gimp-help-fr_2.10.0-1_all.deb
Exemple :
http://deb.debian.org/debian/pool/main/g/gimp/gimp_2.10.22-4_amd64.deb
Ensuite, il suffit de se rendre sur l'un des dépôts miroir
afin de récupérer la suite des paquets et de les installer
à la main ...
sudo apt install -y ./
Merci
@+
Bernard
Re: Installer GIMP 2.10.28
On Friday 03 December 2021 19:16:46 MERLIN Philippe wrote: > Le vendredi 3 décembre 2021, 18:59:06 CET ajh-valmer a écrit : > > Je suis sous Buster, avec la version Gimp 2.10.8 > > Je souhaite passer à la version 2.10.28. > > Sur le site de gimp il faut installer "flatpak", ce que j'ai fait. > > Après, je ne comprends pas comment installer Gimp avec "flatpak", > > quel est cet outil ? > > Je lis : > > Flatpak est un système de virtualisation d’application pour les > > distributions GNU/Linux de bureau. Quel rapport avec Gimp ? > > Sinon, il y a un paquet "the-gimp_2-10-28_fr_214450.tar.bz2", > > téléchargé sur le site clubic. > > Quel choix adopter, et faut-il avant supprimer Gimp 2.10.8 complètement ? > > Merci de votre éclairage, bonne soirée. > Plus simple la version Gimp 2.10.28-1 est disponible en SID (unstable) Comment installer la version Gimp 2.10.28-1 disponible en SID, si je suis sous Buster ?
Installer GIMP 2.10.28
Hello, Je suis sous Buster, avec la version Gimp 2.10.8 Je souhaite passer à la version 2.10.28. Sur le site de gimp il faut installer "flatpak", ce que j'ai fait. Après, je ne comprends pas comment installer Gimp avec "flatpak", quel est cet outil ? Je lis : Flatpak est un système de virtualisation d’application pour les distributions GNU/Linux de bureau. Quel rapport avec Gimp ? Sinon, il y a un paquet "the-gimp_2-10-28_fr_214450.tar.bz2", téléchargé sur le site clubic. Quel choix adopter, et faut-il avant supprimer Gimp 2.10.8 complètement ? Merci de votre éclairage, bonne soirée. A. Valmer
Re: OT. Instalar la última versión de Gimp en Debian Buster
El 2021-07-13 a las 16:31 +0100, José Manuel (Abogado) escribió: > El 13/7/21 a las 6:53, Camaleón escribió: > > El 2021-07-13 a las 06:16 +0100, José Manuel (Abogado) escribió: > > > > > Quisiera instalar la última versión de Gimp 2.10.24 ya que en los > > > repositorios de Debian esta la 2.10.8.2. > > > He estado buscando por Google. Lo poco que he encontrado en español (no me > > > manejo bien con el inglés) me estoy liando y no se como conseguir > > > instalarlo. Por lo que me dirijo a la lista por si me pueden ayudar para > > > conseguir instalar la última versión. Gracias de antemano. > > En Debian, tienes la 2.10.22 (repositorio de testing), quizá te > > sirva. > > > > Compilarlo desde las fuentes sería lo más tedioso, quizá sería más > > conveniente usar el paquete que tienen en flatpak, aunque no sé cómo > > funciona este sistema en Debian: > > > > https://flathub.org/apps/details/org.gimp.GIMP > > https://wiki.debian.org/FlatPak > > Lo de flatpak, me parece interesante para estar a la última en los > programas. Por lo que entiendo lo separa del sistema y evita de cierta forma > perjudicar al sistema con un programa ajeno al sistema. > Pero hay una cosa que no me gusta mucho, por lo que he podido entender de la > página que adjuntas no lo pone después de instalar el programa en en > lanzador de aplicaciones, hay que pone en la consola flatpak run > "org.gimp.GIMP" entre comillas el nombre que le da flatpak al programa. Todo > esto es una lata, sería más cómodo poder poner un lanzador, pero no tengo ni > idea de como hacerlo. Entiendo que podrás añadir la aplicación a tu lanzador habitual, mediante los archivos .desktop, como siempre ¿no? :-? Si no lo hace automáticamente, siempre podrás hacerlo manualmente. Saludos, -- Camaleón
RE: OT. Instalar la última versión de Gimp en Debian Buster
Pues aprende como hacerlo! https://essentecla.com/xampp-8-0-2-crear-lanzador-en-debian-10-resuelto/ -Mensaje original- De: José Manuel (Abogado) Enviado el: martes, 13 de julio de 2021 11:32 Para: debian-user-spanish@lists.debian.org Asunto: Re: OT. Instalar la última versión de Gimp en Debian Buster El 13/7/21 a las 6:53, Camaleón escribió: > El 2021-07-13 a las 06:16 +0100, José Manuel (Abogado) escribió: > >> Quisiera instalar la última versión de Gimp 2.10.24 ya que en los >> repositorios de Debian esta la 2.10.8.2. >> He estado buscando por Google. Lo poco que he encontrado en español >> (no me manejo bien con el inglés) me estoy liando y no se como >> conseguir instalarlo. Por lo que me dirijo a la lista por si me >> pueden ayudar para conseguir instalar la última versión. Gracias de antemano. > En Debian, tienes la 2.10.22 (repositorio de testing), quizá te sirva. > > Compilarlo desde las fuentes sería lo más tedioso, quizá sería más > conveniente usar el paquete que tienen en flatpak, aunque no sé cómo > funciona este sistema en Debian: > > https://flathub.org/apps/details/org.gimp.GIMP > https://wiki.debian.org/FlatPak > > Saludos, > Hola Camaleón, Gracias por la contestar. Lo de flatpak, me parece interesante para estar a la última en los programas. Por lo que entiendo lo separa del sistema y evita de cierta forma perjudicar al sistema con un programa ajeno al sistema. Pero hay una cosa que no me gusta mucho, por lo que he podido entender de la página que adjuntas no lo pone después de instalar el programa en en lanzador de aplicaciones, hay que pone en la consola flatpak run "org.gimp.GIMP" entre comillas el nombre que le da flatpak al programa. Todo esto es una lata, sería más cómodo poder poner un lanzador, pero no tengo ni idea de como hacerlo. Reitero mi agradecimiento. -- Un saludo, José Manuel Gran Canaria/España
Re: OT. Instalar la última versión de Gimp en Debian Buster
El 13/7/21 a las 6:53, Camaleón escribió: El 2021-07-13 a las 06:16 +0100, José Manuel (Abogado) escribió: Quisiera instalar la última versión de Gimp 2.10.24 ya que en los repositorios de Debian esta la 2.10.8.2. He estado buscando por Google. Lo poco que he encontrado en español (no me manejo bien con el inglés) me estoy liando y no se como conseguir instalarlo. Por lo que me dirijo a la lista por si me pueden ayudar para conseguir instalar la última versión. Gracias de antemano. En Debian, tienes la 2.10.22 (repositorio de testing), quizá te sirva. Compilarlo desde las fuentes sería lo más tedioso, quizá sería más conveniente usar el paquete que tienen en flatpak, aunque no sé cómo funciona este sistema en Debian: https://flathub.org/apps/details/org.gimp.GIMP https://wiki.debian.org/FlatPak Saludos, Hola Camaleón, Gracias por la contestar. Lo de flatpak, me parece interesante para estar a la última en los programas. Por lo que entiendo lo separa del sistema y evita de cierta forma perjudicar al sistema con un programa ajeno al sistema. Pero hay una cosa que no me gusta mucho, por lo que he podido entender de la página que adjuntas no lo pone después de instalar el programa en en lanzador de aplicaciones, hay que pone en la consola flatpak run "org.gimp.GIMP" entre comillas el nombre que le da flatpak al programa. Todo esto es una lata, sería más cómodo poder poner un lanzador, pero no tengo ni idea de como hacerlo. Reitero mi agradecimiento. -- Un saludo, José Manuel Gran Canaria/España
Re: OT. Instalar la última versión de Gimp en Debian Buster
El 2021-07-13 a las 06:16 +0100, José Manuel (Abogado) escribió: > Quisiera instalar la última versión de Gimp 2.10.24 ya que en los > repositorios de Debian esta la 2.10.8.2. > He estado buscando por Google. Lo poco que he encontrado en español (no me > manejo bien con el inglés) me estoy liando y no se como conseguir > instalarlo. Por lo que me dirijo a la lista por si me pueden ayudar para > conseguir instalar la última versión. Gracias de antemano. En Debian, tienes la 2.10.22 (repositorio de testing), quizá te sirva. Compilarlo desde las fuentes sería lo más tedioso, quizá sería más conveniente usar el paquete que tienen en flatpak, aunque no sé cómo funciona este sistema en Debian: https://flathub.org/apps/details/org.gimp.GIMP https://wiki.debian.org/FlatPak Saludos, -- Camaleón
OT. Instalar la última versión de Gimp en Debian Buster
Hola Quisiera instalar la última versión de Gimp 2.10.24 ya que en los repositorios de Debian esta la 2.10.8.2. He estado buscando por Google. Lo poco que he encontrado en español (no me manejo bien con el inglés) me estoy liando y no se como conseguir instalarlo. Por lo que me dirijo a la lista por si me pueden ayudar para conseguir instalar la última versión. Gracias de antemano. Espero noticias -- Un saludo, José Manuel Gran Canaria/España
Re: Gimp Crash debug
El 2020-12-21 a las 15:03 -0300, S P escribió: (...) > > fatal error: Excepción de coma flotante > > Stack trace: > ``` > /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7fc21a756e27] > gimp-2.10(+0xd14a0)[0x5640ac7c04a0] > gimp-2.10(+0xd18d8)[0x5640ac7c08d8] > gimp-2.10(+0xd2037)[0x5640ac7c1037] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x3413c12730)[0x7fc219a5e730] > gimp-2.10(+0x44397f)[0x5640acb3297f] > gimp-2.10(+0x443c28)[0x5640acb32c28] > /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7fc219c42dd8] > /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4e1c8)[0x7fc219c431c8] > /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7fc219c434c2] > gimp-2.10(gimp_plug_in_manager_call_run+0x5ff)[0x5640aca67cef] > gimp-2.10(+0x37182e)[0x5640aca6082e] > gimp-2.10(gimp_procedure_execute+0x219)[0x5640aca540c9] > gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1f9)[0x5640aca4d609] > gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cb)[0x5640aca4dacb] > gimp-2.10(file_open_image+0x34a)[0x5640acb4ca2a] > gimp-2.10(file_open_with_proc_and_display+0x2a5)[0x5640acb4d975] > gimp-2.10(file_open_from_command_line+0x1ad)[0x5640acb4e1cd] > gimp-2.10(app_run+0x2ec)[0x5640ac7bfc4c] > gimp-2.10(main+0x395)[0x5640ac7bf5b5] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fc2198ad09b] > gimp-2.10(_start+0x2a)[0x5640ac7bf73a] GIMP crash with floating point exception on image save. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948380 Saludos, -- Camaleón
Gimp Crash debug
``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Debian 8.2.0-13) using GEGL version 0.4.12 (compiled against version 0.4.12) using GLib version 2.58.3 (compiled against version 2.58.1) using GdkPixbuf version 2.38.1 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Excepción de coma flotante Stack trace: ``` /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7fc21a756e27] gimp-2.10(+0xd14a0)[0x5640ac7c04a0] gimp-2.10(+0xd18d8)[0x5640ac7c08d8] gimp-2.10(+0xd2037)[0x5640ac7c1037] /lib/x86_64-linux-gnu/libpthread.so.0(+0x3413c12730)[0x7fc219a5e730] gimp-2.10(+0x44397f)[0x5640acb3297f] gimp-2.10(+0x443c28)[0x5640acb32c28] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7fc219c42dd8] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4e1c8)[0x7fc219c431c8] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7fc219c434c2] gimp-2.10(gimp_plug_in_manager_call_run+0x5ff)[0x5640aca67cef] gimp-2.10(+0x37182e)[0x5640aca6082e] gimp-2.10(gimp_procedure_execute+0x219)[0x5640aca540c9] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1f9)[0x5640aca4d609] gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cb)[0x5640aca4dacb] gimp-2.10(file_open_image+0x34a)[0x5640acb4ca2a] gimp-2.10(file_open_with_proc_and_display+0x2a5)[0x5640acb4d975] gimp-2.10(file_open_from_command_line+0x1ad)[0x5640acb4e1cd] gimp-2.10(app_run+0x2ec)[0x5640ac7bfc4c] gimp-2.10(main+0x395)[0x5640ac7bf5b5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fc2198ad09b] gimp-2.10(_start+0x2a)[0x5640ac7bf73a] ```
Re: Trimming boundary of image in GIMP.
From: The Wanderer Date: Thu, 08 Oct 2020 16:10:04 -0400 > This sounds as if the rectangle selection tool's "Fixed" option has been > selected, and set to "Aspect Ratio". That's it. The aspect ratio was fixed at 1:1. Didn't make the setting deliberately. Clicked the box when half asleep? Thanks! ... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Trimming boundary of image in GIMP.
On Thu, 2020-10-08 at 12:43 -0700, pe...@easthope.ca wrote: > From: Tixy > Date: Thu, 08 Oct 2020 08:37:33 +0100 > > I've attached screenshots of this... > > Same behaviour here until attempting to drag top downward. > > Open GIMP in debian 10, > open a rectangular image, > choose the selection tool (might not be necessary), > Select > All, > grab top boundary and drag downward, (top; not corner) I guess I was doing different things, I'm select an area using the Rectangle Select tool then changing it, but you are selecting an area with Select All then trying to drag the boundary of that area. For me the latter doesn't work, because clicking anywhere starts just starts using whatever tool is currently selected tool, for me, there doesn't seem to be a way to interact with the area Select All creates. -- Tixy
Re: Trimming boundary of image in GIMP.
On 2020-10-07 at 13:49, pe...@easthope.ca wrote: > Until recently the routine for trimming the boundary of an image was, > (1) Select > All, > (2) grab a boundary with pointer and drag it toward the center, > (3) drag other boundaries in a similar way until the desired boundary > was indicated, > (4) Image > Crop to Selection. > Done. > > Appears that an update since the last time I used GIMP added a new > feature. (?) Now left and right boundaries are linked with top and > bottom boundaries. Dragging the top boundary pulls the sides in > simultaneously. =8~( > > There must be cases where that is helpful but what if the objective > is to change only one boundary? The top for example. I've tried > unlinking Width and Height in Layer > Layer to Boundary Size. No > dice. > > I've tried holding , or while dragging a > boundary. No dice. > > How is the new feature overridden? This sounds as if the rectangle selection tool's "Fixed" option has been selected, and set to "Aspect Ratio". (The other options are "Width", "Height", and "Size".) Look in the toolbox (for me it appears at the side, but you may have it set up otherwise), and see what you find for this setting. The relevant toolbox and area are shown (highlighted by red border) in a screenshot on this question: https://superuser.com/questions/463585/how-to-set-a-custom-sized-rectangle-select-area-in-gimp That -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Trimming boundary of image in GIMP.
From: Tixy Date: Thu, 08 Oct 2020 08:37:33 +0100 > I've attached screenshots of this... Same behaviour here until attempting to drag top downward. Open GIMP in debian 10, open a rectangular image, choose the selection tool (might not be necessary), Select > All, grab top boundary and drag downward, (top; not corner) left and right side boundaries immediately contract inward to make the boundary square. Result visible here. http://easthope.ca/GIMP.png Thanks for the replies,... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Trimming boundary of image in GIMP.
On Wed, Oct 07, 2020 at 10:49:32AM -0700, pe...@easthope.ca wrote: > Until recently the routine for trimming the boundary of an image was, Doesn't happen here (Gimp 2.10.8 -- Debian package 2.10.8-2). Rectangle selection also behaves "normal" (i.e. it doesn't force a square). This assuming that I did understand what you're talking about: this what you call "borders" are what Gimp calls "guides", right? Cheers - t signature.asc Description: Digital signature
Re: Trimming boundary of image in GIMP.
On Thu, 2020-10-08 at 08:37 +0100, Tixy wrote: > I've attached screenshots of this... Ah, I just noticed that the screenshot program didn't include the modified mouse pointer I see, it just added a generic pointer. But they do show the selection area I describe. -- Tixy
Re: Trimming boundary of image in GIMP.
On Thu, 2020-10-08 at 08:32 +0100, Tixy wrote: > Not that I know. For me, with up-to-date Buster install, the Rectangle > Select is only 'square select' if you click inside the corners of the > selection box. In fact, hovering the mouse inside the selection box > shows an area to grab, which is either a square (if it's in the > corner), or a rectangle along a side where you can drag just that side. > The mouse pointer also changes to indicate the selection type. I've attached screenshots of this...
Re: Trimming boundary of image in GIMP.
On Wed, 2020-10-07 at 20:31 -0700, pe...@easthope.ca wrote: > From: Tixy > Date: Wed, 07 Oct 2020 20:24:01 +0100 > > I've always used the Rectangle Select tool by press the 'R' key . > > Yes, I've used rectangle select for years. Unfortunately it is now square > select. > In this GIMP at least. Is there an aspect ratio setting somewhere? Not that I know. For me, with up-to-date Buster install, the Rectangle Select is only 'square select' if you click inside the corners of the selection box. In fact, hovering the mouse inside the selection box shows an area to grab, which is either a square (if it's in the corner), or a rectangle along a side where you can drag just that side. The mouse pointer also changes to indicate the selection type. -- Tixy
Re: Trimming boundary of image in GIMP.
From: Tixy Date: Wed, 07 Oct 2020 20:24:01 +0100 > I've always used the Rectangle Select tool by press the 'R' key . Yes, I've used rectangle select for years. Unfortunately it is now square select. In this GIMP at least. Is there an aspect ratio setting somewhere? > I notice that Gimp remembers the last selection tool you used when > starting up, so maybe that's affecting the behaviour you see? Rectangle select can be chosen before any other action. Unfortunately the "rectangle" here is constrained to square. Thanks, ... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Trimming boundary of image in GIMP.
On Wed, 2020-10-07 at 10:49 -0700, pe...@easthope.ca wrote: > Until recently the routine for trimming the boundary of an image was, > (1) Select > All, > (2) grab a boundary with pointer and drag it toward the center, > (3) drag other boundaries in a similar way until the desired > boundary > was indicated, > (4) Image > Crop to Selection. > Done. > > Appears that an update since the last time I used GIMP added a new > feature. (?) Now left and right boundaries are linked with top and > bottom boundaries. Dragging the top boundary pulls the sides in > simultaneously. =8~( I've always used the Rectangle Select tool by press the 'R' key (may be different in no English locales?). That lets you select a rectangle by clicking then dragging, and you can alter the selection by dragging he sides and corners by putting the cursor inside the selection near the edge. I notice that Gimp remembers the last selection tool you used when starting up, so maybe that's affecting the behaviour you see? E.g. for me, after opening and image in Gimp, after Select All, trying to click the selection border doesn't work, I just end up creating a new selection because Rectangle Select is active as that was the last tool I used before closing Gimp. In fact, I can't see how to select 'no selection tool', I can just change it to the another type from the menu, but there is no 'None'... -- Tixy
Trimming boundary of image in GIMP.
Until recently the routine for trimming the boundary of an image was, (1) Select > All, (2) grab a boundary with pointer and drag it toward the center, (3) drag other boundaries in a similar way until the desired boundary was indicated, (4) Image > Crop to Selection. Done. Appears that an update since the last time I used GIMP added a new feature. (?) Now left and right boundaries are linked with top and bottom boundaries. Dragging the top boundary pulls the sides in simultaneously. =8~( There must be cases where that is helpful but what if the objective is to change only one boundary? The top for example. I've tried unlinking Width and Height in Layer > Layer to Boundary Size. No dice. I've tried holding , or while dragging a boundary. No dice. How is the new feature overridden? Thx, ... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: GIMP keeps crashing!
On 03-10-2020 13:48, riveravaldez wrote: > On 10/2/20, Rebecca Matthews wrote: >> ``` >> GNU Image Manipulation Program version 2.10.8 >> git-describe: GIMP_2_10_6-294-ga967e8d2c2 >> C compiler: >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper >> OFFLOAD_TARGET_NAMES=nvptx-none >> OFFLOAD_TARGET_DEFAULT=1 >> Target: x86_64-linux-gnu >> Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13' >> --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs >> --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr >> --with-gcc-major-version-only --program-suffix=-8 >> --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id >> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix >> --libdir=/usr/lib --enable-nls --enable-clocale=gnu >> --enable-libstdcxx-debug --enable-libstdcxx-time=yes >> --with-default-libstdcxx-abi=new --enable-gnu-unique-object >> --disable-vtable-verify --enable-libmpx --enable-plugin >> --enable-default-pie --with-system-zlib --with-target-system-zlib >> --enable-objc-gc=auto --enable-multiarch --disable-werror >> --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 >> --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none >> --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu >> --host=x86_64-linux-gnu --target=x86_64-linux-gnu >> Thread model: posix >> gcc version 8.2.0 (Debian 8.2.0-13) Hello Rebecca, This could be a number of issues. I find some applications dive on the Enlightenment desktop, or it could be even a hardware issue. Sometimes software and hardware clash. Have you checked out the bug lists, Debian and GIMP? Kind regards, Harry Weaver -- `Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful'. — Lucius Annæus Seneca. Terrorism, the new religion. Registered Linux User: 554515
Re: GIMP keeps crashing!
On 10/2/20, Rebecca Matthews wrote: > ``` > GNU Image Manipulation Program version 2.10.8 > git-describe: GIMP_2_10_6-294-ga967e8d2c2 > C compiler: > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none > OFFLOAD_TARGET_DEFAULT=1 > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13' > --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs > --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr > --with-gcc-major-version-only --program-suffix=-8 > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id > --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix > --libdir=/usr/lib --enable-nls --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --with-default-libstdcxx-abi=new --enable-gnu-unique-object > --disable-vtable-verify --enable-libmpx --enable-plugin > --enable-default-pie --with-system-zlib --with-target-system-zlib > --enable-objc-gc=auto --enable-multiarch --disable-werror > --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 > --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none > --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu > --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > gcc version 8.2.0 (Debian 8.2.0-13) Hi, Rebecca, this is Debian's users list, not GIMP developers bug tracker. Maybe you should check what are the best ways to inform of a problem and ask for some help -always in a gentle and respectful manner, because this is just a voluntary community effort. Anyway, you're not giving any relevant information, e.g., Debian version in use, symptoms of that crashing, the output of a terminal '$ gimp', etc. Probably with more (some) info about your issue someone will aport an idea to solve it. Best regards.
GIMP keeps crashing!
``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Debian 8.2.0-13)
Re: Can't start Gimp in Bullseye
On Sb, 22 aug 20, 21:50:42, Joachim Fahnenmüller wrote: > Am 22.08.20 um 21:00 schrieb Joachim Fahnenmüller: > > > > root@peter:~# ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 > > lrwxrwxrwx 1 root root 22 Jun 13 2019 > > /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1 > > > > apt-file search libbabl-0.1.so.0.177.1 > > libbabl-0.1-0: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0.177.1 > > > > Looks like libbabl hasn't upgraded. However, I don't know why and what > > to do about it. [...] > I got it working again, though I still don't understand what happened. > > I did: > apt-get install libbabl-0.1-0=0.1.78-1 > (it complained that it was a downgrade and also removed gimp) > apt-get install libgegl-common=0.4.24-1 > (similar, but then I could:) > apt-get install gimp > (and it works) See https://lists.debian.org/debian-devel/2020/08/msg00111.html Short story: you probably had and old libbabl from Deb Multimedia installed, which was preferred by APT due to the epoch. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Can't start Gimp in Bullseye
Am 22.08.20 um 21:00 schrieb Joachim Fahnenmüller: Am 10.08.20 um 22:47 schrieb Kent West: On Mon, Aug 10, 2020 at 1:49 PM Joachim Fahnenmüller wrote: Am 10.08.20 um 17:39 schrieb Kent West: On Mon, Aug 10, 2020 at 10:20 AM Joachim Fahnenmüller < jfahnenmuel...@web.de> wrote: Hi everybody, since I upgraded to Bullseye, Gimp does not start any more. I get the following: joachim@peter:~$ gimp gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by gimp) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpwidgets-2.0.so.0) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpcolor-2.0.so.0) gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract Any idea? What happens with: ~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 10:36 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.177.1 joachim@peter:~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 2019 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1 You might try: $ cd /usr/bin $ ldd gimp and look for any "not found" lines. root@peter:~# ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 2019 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1 apt-file search libbabl-0.1.so.0.177.1 libbabl-0.1-0: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0.177.1 Looks like libbabl hasn't upgraded. However, I don't know why and what to do about it. root@peter:/usr/bin# ldd gimp ./gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by ./gimp) (and more lines) That is the same as I posted originally. I got it working again, though I still don't understand what happened. I did: apt-get install libbabl-0.1-0=0.1.78-1 (it complained that it was a downgrade and also removed gimp) apt-get install libgegl-common=0.4.24-1 (similar, but then I could:) apt-get install gimp (and it works) Regards, Joachim
Re: Can't start Gimp in Bullseye
Am 10.08.20 um 22:47 schrieb Kent West: On Mon, Aug 10, 2020 at 1:49 PM Joachim Fahnenmüller wrote: Am 10.08.20 um 17:39 schrieb Kent West: On Mon, Aug 10, 2020 at 10:20 AM Joachim Fahnenmüller < jfahnenmuel...@web.de> wrote: Hi everybody, since I upgraded to Bullseye, Gimp does not start any more. I get the following: joachim@peter:~$ gimp gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by gimp) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpwidgets-2.0.so.0) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpcolor-2.0.so.0) gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract Any idea? What happens with: ~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 10:36 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.177.1 joachim@peter:~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 2019 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1 You might try: $ cd /usr/bin $ ldd gimp and look for any "not found" lines. root@peter:~# ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 2019 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1 apt-file search libbabl-0.1.so.0.177.1 libbabl-0.1-0: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0.177.1 Looks like libbabl hasn't upgraded. However, I don't know why and what to do about it. root@peter:/usr/bin# ldd gimp ./gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by ./gimp) (and more lines) That is the same as I posted originally.
Re: Can't start Gimp in Bullseye
On Mon, Aug 10, 2020 at 1:49 PM Joachim Fahnenmüller wrote: > Am 10.08.20 um 17:39 schrieb Kent West: > > On Mon, Aug 10, 2020 at 10:20 AM Joachim Fahnenmüller < > jfahnenmuel...@web.de> > > wrote: > > > >> Hi everybody, > >> > >> since I upgraded to Bullseye, Gimp does not start any more. I get the > >> following: > >> > >> joachim@peter:~$ gimp > >> gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > >> available (required by gimp) > >> gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > >> available (required by /usr/lib/libgimpwidgets-2.0.so.0) > >> gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > >> available (required by /usr/lib/libgimpcolor-2.0.so.0) > >> gimp: symbol lookup error: gimp: undefined symbol: > gegl_rectangle_subtract > >> > >> Any idea? > >> > >> > > What happens with: > > > > ~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 > > lrwxrwxrwx 1 root root 22 Jun 13 10:36 > > /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.177.1 > > > > > > > joachim@peter:~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 > lrwxrwxrwx 1 root root 22 Jun 13 2019 > /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1 > > You might try: $ cd /usr/bin $ ldd gimp and look for any "not found" lines. -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Re: Can't start Gimp in Bullseye
On 11-08-2020 01:19, Joachim Fahnenmüller wrote: > Hi everybody, > > since I upgraded to Bullseye, Gimp does not start any more. I get the > following: > > joachim@peter:~$ gimp > gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > available (required by gimp) > gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > available (required by /usr/lib/libgimpwidgets-2.0.so.0) > gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > available (required by /usr/lib/libgimpcolor-2.0.so.0) > gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract > > Any idea? No problem here, so it looks like an upgrade mishap. What version of GIMP are you running? Any messages in your package manager? -- `Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful'. — Lucius Annæus Seneca. Terrorism, the new religion. Registered Linux User: 554515
Re: Can't start Gimp in Bullseye
Am 10.08.20 um 17:39 schrieb Kent West: On Mon, Aug 10, 2020 at 10:20 AM Joachim Fahnenmüller wrote: Hi everybody, since I upgraded to Bullseye, Gimp does not start any more. I get the following: joachim@peter:~$ gimp gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by gimp) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpwidgets-2.0.so.0) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpcolor-2.0.so.0) gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract Any idea? What happens with: ~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 10:36 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.177.1 joachim@peter:~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 2019 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.165.1
Re: Can't start Gimp in Bullseye
On Mon, Aug 10, 2020 at 10:39 AM Kent West wrote: > > > On Mon, Aug 10, 2020 at 10:20 AM Joachim Fahnenmüller < > jfahnenmuel...@web.de> wrote: > >> Hi everybody, >> >> since I upgraded to Bullseye, Gimp does not start any more. I get the >> following: >> >> joachim@peter:~$ gimp >> gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information >> available (required by gimp) >> gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information >> available (required by /usr/lib/libgimpwidgets-2.0.so.0) >> gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information >> available (required by /usr/lib/libgimpcolor-2.0.so.0) >> gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract >> >> Any idea? >> >> > What happens with: > > ~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 > lrwxrwxrwx 1 root root 22 Jun 13 10:36 > /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.177.1 > > ~$ apt-file search libbabl-0.1.so.0.177.1 libbabl-0.1-0: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0.177.1 ~$ aptitude search libbabl i A libbabl-0.1-0- Dynamic, any to any, pixel format conversion library -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Re: Can't start Gimp in Bullseye
On Mon, Aug 10, 2020 at 10:20 AM Joachim Fahnenmüller wrote: > Hi everybody, > > since I upgraded to Bullseye, Gimp does not start any more. I get the > following: > > joachim@peter:~$ gimp > gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > available (required by gimp) > gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > available (required by /usr/lib/libgimpwidgets-2.0.so.0) > gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information > available (required by /usr/lib/libgimpcolor-2.0.so.0) > gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract > > Any idea? > > What happens with: ~$ ls -lah /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 lrwxrwxrwx 1 root root 22 Jun 13 10:36 /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 -> libbabl-0.1.so.0.177.1 -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Can't start Gimp in Bullseye
Hi everybody, since I upgraded to Bullseye, Gimp does not start any more. I get the following: joachim@peter:~$ gimp gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by gimp) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpwidgets-2.0.so.0) gimp: /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0: no version information available (required by /usr/lib/libgimpcolor-2.0.so.0) gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract Any idea? Regards, Joachim
Re: GIMP Crash
Ryan Young writes: > Here is the bug info > > ``` > GNU Image Manipulation Program version 2.10.8 In that case, if you are in Debian, you would be send bug report. So that the maintainer can be know what problem is. https://www.debian.org/Bugs/Reporting Actually, you must add contain keywords "Package" and "Version" ;;; Sincerely, Byung-Hee -- ^고맙습니다 _白衣從軍_ 감사합니다_^))//
GIMP Crash
Here is the bug info
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib
--enable-objc-gc=auto --enable-multiarch --disable-werror
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Debian 8.2.0-13)
using GEGL version 0.4.12 (compiled against version 0.4.12)
using GLib version 2.58.3 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 16588 - Thread 16588 #
[New LWP 16589]
[New LWP 16590]
[New LWP 16592]
[New LWP 16593]
[New LWP 16605]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd5bc55ed0, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7a5aacd05e00 (LWP 16588) "gimp-2.10" __libc_read
(nbytes=256, buf=0x7ffd5bc55ed0, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7a5aab4ad700 (LWP 16589) "gmain" 0x7a5aae982819
in __GI___poll (fds=0x581ef2edf1c0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
3Thread 0x7a5aaa957700 (LWP 16590) "gdbus" 0x7a5aae982819
in __GI___poll (fds=0x581ef2eb76a0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7a5a97ac8700 (LWP 16592) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7a5a972c7700 (LWP 16593) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7a5a95e51700 (LWP 16605) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 6 (Thread 0x7a5a95e51700 (LWP 16605)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7a5aaec97f9f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7a5aaf3310cd in ?? () from
/usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7a5aaec76415 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7a5aaea5efa3 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {134529480464128,
4780554623439464532, 140726143112750, 140726143112751, 134529480464128,
96889976575168, -5268408010271233964, -5268459145313916844}, mask_was_saved
= 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup =
0x0, canceltype = 0}}}
not_first_call =
#5 0x7a5aae98d4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 5 (Thread 0x7a5a972c7700 (LWP 16593)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7a5aaec97f9f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x581ef15b6423 in ?? ()
No symbol table info available.
#3 0x7a5aaec76415 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7a5aaea5efa3 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {134529501918976,
4780554623439464532, 140726143118094, 140726143118095, 134529501918976,
96889925393344, -5268403142999545772, -5268459145313916844}, mask_was_saved
= 0}}, priv = {pad
Re: OT - Gimp-plugin-registry en Debian 11
Amigo, buenas y si colocas repos debian estable y lo cargas solo ese plugin, no es lo mejor pero aveces me ha funcionado con algunas librerias que todavia no apacen. El vie., 12 jun. 2020 10:43 a. m., Camaleón escribió: > El 2020-06-12 a las 17:13 +0100, José Manuel (Abogado) escribió: > > > El 11/6/20 a las 7:02, Camaleón escribió: > > > El 2020-06-10 a las 22:43 +0100, José Manuel (Abogado) escribió: > > > > > > > He instalado en Debian bullseye: > > > > # apt install gimp-plugin-registry > > > > lo compruebo y me aparece > > > > # apt install gimp-plugin-registry > > > > Leyendo lista de paquetes... Hecho > > > > Creando árbol de dependencias > > > > Leyendo la información de estado... Hecho > > > > gimp-plugin-registry ya está en su versión más reciente > (9.20180625+nmu1). > > > > 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no > actualizados. > > > > > > > > Me indica que esta instalado, pero en Gimp /filtros/realzar/ no > aparece > > > (...) > > > > > > ¿Y qué filtro buscas, exactamente? > > > > > > El paquete que has instalado es una especie de recopilatorio de > > > extensiones de todo tipo (filtros, complementos y scripts) para The > Gimp, > > > por lo que cada uno aparecerá dentro de su sección correspondiente. > > > Saludos, > > > > Gracias por contestar. > > Tienes razón ese plugin tiene muchas herramientas una de ellas que a mi > me > > interesa es la heal selectión (quita objetos no deseados de las fotos, > > parecido al plugin que tiene photosohop). y es la que no me aparece al > > instalarlo en Debian bullseye ni a través de los repos ni manualmente > > descargándolo desde la página web > > > https://github.com/aferrero2707/gimp-plugins-collection/releases/tag/continuous > > > > y ponerlo en la carpeta /home/usuario/.config/GIMP/2.10/plug-ins pero > > tampoco me aparece o por lo menos yo no lo veo. > > Según este foro¹, sugieren que necesitas el paquete «gimp-python», pero > efectivamente, ese paquete no está disponible para testing². > > Si el filtro necesita algún paquete o biblioteca adicional, deberías > informar del > fallo en el BTS de Debian, para que lo corrijan (recuerda que estás con > una versión de pruebas). > > 'Heal Selection' Missing in Gimp 2.10.6 on Ubuntu 18.10 > <https://www.gimp-forum.net/Thread-Heal-Selection-Missing-in-Gimp-2-10-6- > on-Ubuntu-18-10 > <https://www.gimp-forum.net/Thread-Heal-Selection-Missing-in-Gimp-2-10-6-on-Ubuntu-18-10> > > > > ²No gimp-python in Debian (Testing) > <https://www.gimpusers.com/forums/gimp-user/21679-no-gimp-python-in-debi > an-testing > <https://www.gimpusers.com/forums/gimp-user/21679-no-gimp-python-in-debian-testing> > > > > Saludos, > > -- > Camaleón > >
Re: OT - Gimp-plugin-registry en Debian 11
El 2020-06-12 a las 17:13 +0100, José Manuel (Abogado) escribió: > El 11/6/20 a las 7:02, Camaleón escribió: > > El 2020-06-10 a las 22:43 +0100, José Manuel (Abogado) escribió: > > > > > He instalado en Debian bullseye: > > > # apt install gimp-plugin-registry > > > lo compruebo y me aparece > > > # apt install gimp-plugin-registry > > > Leyendo lista de paquetes... Hecho > > > Creando árbol de dependencias > > > Leyendo la información de estado... Hecho > > > gimp-plugin-registry ya está en su versión más reciente (9.20180625+nmu1). > > > 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no > > > actualizados. > > > > > > Me indica que esta instalado, pero en Gimp /filtros/realzar/ no aparece > > (...) > > > > ¿Y qué filtro buscas, exactamente? > > > > El paquete que has instalado es una especie de recopilatorio de > > extensiones de todo tipo (filtros, complementos y scripts) para The Gimp, > > por lo que cada uno aparecerá dentro de su sección correspondiente. > > Saludos, > > Gracias por contestar. > Tienes razón ese plugin tiene muchas herramientas una de ellas que a mi me > interesa es la heal selectión (quita objetos no deseados de las fotos, > parecido al plugin que tiene photosohop). y es la que no me aparece al > instalarlo en Debian bullseye ni a través de los repos ni manualmente > descargándolo desde la página web > https://github.com/aferrero2707/gimp-plugins-collection/releases/tag/continuous > > y ponerlo en la carpeta /home/usuario/.config/GIMP/2.10/plug-ins pero > tampoco me aparece o por lo menos yo no lo veo. Según este foro¹, sugieren que necesitas el paquete «gimp-python», pero efectivamente, ese paquete no está disponible para testing². Si el filtro necesita algún paquete o biblioteca adicional, deberías informar del fallo en el BTS de Debian, para que lo corrijan (recuerda que estás con una versión de pruebas). 'Heal Selection' Missing in Gimp 2.10.6 on Ubuntu 18.10 <https://www.gimp-forum.net/Thread-Heal-Selection-Missing-in-Gimp-2-10-6- on-Ubuntu-18-10> ²No gimp-python in Debian (Testing) <https://www.gimpusers.com/forums/gimp-user/21679-no-gimp-python-in-debi an-testing> Saludos, -- Camaleón
Re: OT - Gimp-plugin-registry en Debian 11
El 10/6/20 a las 23:21, JavierDebian escribió: El 10/6/20 a las 18:43, José Manuel (Abogado) escribió: Hola He instalado en Debian bullseye: # apt install gimp-plugin-registry lo compruebo y me aparece # apt install gimp-plugin-registry Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho gimp-plugin-registry ya está en su versión más reciente (9.20180625+nmu1). 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados. Me indica que esta instalado, pero en Gimp /filtros/realzar/ no aparece He buscado el Google algo que me iluminara pero no lo he conseguido por lo que me dirijo a la lista, para ver si me podéis ayudar, indicándome dónde esta el error por lo que no aparece y como solucionarlo. Gracias de antemano "pero en Gimp /filtros/realzar/ no aparece" errr No debe aparecer ahí. https://elgimper.files.wordpress.com/2016/04/gimp-fx-foundry.png?w=768 https://elgimper.wordpress.com/2016/04/17/gimp-plugin-registry/ JAP Hola Javier Gracias por contestar. Dentro de ese plugin tiene varias herramientas, una de ellas que a mi me interesa es la heal selectión (quita objetos no deseados de las fotos, parecido al plugin que tiene photosohop). Desde Debian 8 al instalar este plugin siempre ha estado y si vas algún tutorial de Gimp para ver como funciona se refiere a el en /filtros/realzar/. Pero ahora al instalarlo desde los repos en Debian bullseye no me aparece. He intentado hacerlo manual descargándolo desde la página web: https://github.com/aferrero2707/gimp-plugins-collection/releases/tag/continuous y ponerlo en la carpeta /home/usuario/.config/GIMP/2.10/plug-ins pero tampoco me aparece o por lo menos yo no lo veo. -- Un saludo, José Manuel Gran Canaria/España Si vas a escribir.. piensa en esto: no digas nada que no sea mas precioso que el silencio!!!
Re: OT - Gimp-plugin-registry en Debian 11
El 11/6/20 a las 7:02, Camaleón escribió: El 2020-06-10 a las 22:43 +0100, José Manuel (Abogado) escribió: He instalado en Debian bullseye: # apt install gimp-plugin-registry lo compruebo y me aparece # apt install gimp-plugin-registry Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho gimp-plugin-registry ya está en su versión más reciente (9.20180625+nmu1). 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados. Me indica que esta instalado, pero en Gimp /filtros/realzar/ no aparece (...) ¿Y qué filtro buscas, exactamente? El paquete que has instalado es una especie de recopilatorio de extensiones de todo tipo (filtros, complementos y scripts) para The Gimp, por lo que cada uno aparecerá dentro de su sección correspondiente. Saludos, Hola Camaleón Gracias por contestar. Tienes razón ese plugin tiene muchas herramientas una de ellas que a mi me interesa es la heal selectión (quita objetos no deseados de las fotos, parecido al plugin que tiene photosohop). y es la que no me aparece al instalarlo en Debian bullseye ni a través de los repos ni manualmente descargándolo desde la página web https://github.com/aferrero2707/gimp-plugins-collection/releases/tag/continuous y ponerlo en la carpeta /home/usuario/.config/GIMP/2.10/plug-ins pero tampoco me aparece o por lo menos yo no lo veo. -- Un saludo, José Manuel Gran Canaria/España Si vas a escribir.. piensa en esto: no digas nada que no sea mas precioso que el silencio!!!
Re: OT - Gimp-plugin-registry en Debian 11
El 2020-06-10 a las 22:43 +0100, José Manuel (Abogado) escribió: > He instalado en Debian bullseye: > # apt install gimp-plugin-registry > lo compruebo y me aparece > # apt install gimp-plugin-registry > Leyendo lista de paquetes... Hecho > Creando árbol de dependencias > Leyendo la información de estado... Hecho > gimp-plugin-registry ya está en su versión más reciente (9.20180625+nmu1). > 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados. > > Me indica que esta instalado, pero en Gimp /filtros/realzar/ no aparece (...) ¿Y qué filtro buscas, exactamente? El paquete que has instalado es una especie de recopilatorio de extensiones de todo tipo (filtros, complementos y scripts) para The Gimp, por lo que cada uno aparecerá dentro de su sección correspondiente. Saludos, -- Camaleón
Re: OT - Gimp-plugin-registry en Debian 11
El 10/6/20 a las 18:43, José Manuel (Abogado) escribió: Hola He instalado en Debian bullseye: # apt install gimp-plugin-registry lo compruebo y me aparece # apt install gimp-plugin-registry Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho gimp-plugin-registry ya está en su versión más reciente (9.20180625+nmu1). 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados. Me indica que esta instalado, pero en Gimp /filtros/realzar/ no aparece He buscado el Google algo que me iluminara pero no lo he conseguido por lo que me dirijo a la lista, para ver si me podéis ayudar, indicándome dónde esta el error por lo que no aparece y como solucionarlo. Gracias de antemano "pero en Gimp /filtros/realzar/ no aparece" errr No debe aparecer ahí. https://elgimper.files.wordpress.com/2016/04/gimp-fx-foundry.png?w=768 https://elgimper.wordpress.com/2016/04/17/gimp-plugin-registry/ JAP
OT - Gimp-plugin-registry en Debian 11
Hola He instalado en Debian bullseye: # apt install gimp-plugin-registry lo compruebo y me aparece # apt install gimp-plugin-registry Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho gimp-plugin-registry ya está en su versión más reciente (9.20180625+nmu1). 0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados. Me indica que esta instalado, pero en Gimp /filtros/realzar/ no aparece He buscado el Google algo que me iluminara pero no lo he conseguido por lo que me dirijo a la lista, para ver si me podéis ayudar, indicándome dónde esta el error por lo que no aparece y como solucionarlo. Gracias de antemano -- Un saludo, José Manuel Gran Canaria/España Si vas a escribir.. piensa en esto: no digas nada que no sea mas precioso que el silencio!!!
Re: Gimp 2.10
ajh-valmer a écrit : > On Saturday 30 November 2019 13:23:17 Jean-Pierre Giraud wrote: >>> >> Tu devrais directement contacter le mainteneur : >>> > Comment lui signaler, ou sera t-il à l'Opensummit de décembre ? > >>> Maintainer: Debian GNOME Maintainers > > > > Je leur ai écrit... : > > Voici les défauts constatés (liste non exhaustive) : > > - Menu "filtres" => "Amélioration" => > "Augmenter les contrastes et la netteté" a disparu. > > - La fenêtre "boîte à outils" qui s'affiche à côté, > est devenue quasi-illisible car beaucoup trop pâle. La couleur se règle. > - Menu images => "échelle et taille de l'image" : > on ne peut pas fixer une autre dimension, > le champ reste désespérement vide. > (le clavier devient inopérant). Je n'ai pas ce problème. À mon avis, vous avez deux couleurs identiques (caractères et fond). JKB
Re: Gimp 2.10
On Saturday 30 November 2019 13:23:17 Jean-Pierre Giraud wrote: > > >> Tu devrais directement contacter le mainteneur : > > > Comment lui signaler, ou sera t-il à l'Opensummit de décembre ? > > Maintainer: Debian GNOME Maintainers Je leur ai écrit... : Voici les défauts constatés (liste non exhaustive) : - Menu "filtres" => "Amélioration" => "Augmenter les contrastes et la netteté" a disparu. - La fenêtre "boîte à outils" qui s'affiche à côté, est devenue quasi-illisible car beaucoup trop pâle. - Menu images => "échelle et taille de l'image" : on ne peut pas fixer une autre dimension, le champ reste désespérement vide. (le clavier devient inopérant). - Fenêtre "boîte à outils" => Texte : idem, impossible de mettre la taille des caractères, (le clavier devient inopérant). On verra, affaire à suivre... sans illusion. J'avais signalé un défaut inhérent d'OpenOffice, LibreOffice, depuis très longtemps, plus de 15 ans. Rencontré un responsable de l'équipe à l'opensummit, écrit. Il n'est pas possible à l'intérieur d'un document de faire un copier/coller rapide : surbrillance d'un mot => appui bouton souris. 15 ans après, le défaut est toujours présent.
Re: Gimp 2.10
Bonjour, Le 30/11/2019 à 11:38, Manu Baylac a écrit : > Bonjour, > > Le 29/11/2019 à 20:21, ajh-valmer a écrit : > > >> Tu devrais directement contacter le mainteneur : > > Comment lui signaler, ou sera t-il à l'Opensummit de décembre ? > > $ apt show gimp > > [...] > Maintainer: Debian GNOME Maintainers > > > -- > Manu Si le problème ne concerne pas que Debian (?), tu pourrais poser la question sur la liste (en anglais) gimp-user-l...@gnome.org <mailto:gimp-user-l...@gnome.org> Amicalement, jipege <mailto:gimp-user-l...@gnome.org>
Re: Gimp 2.10
Bonjour, Le 29/11/2019 à 20:21, ajh-valmer a écrit : >> Tu devrais directement contacter le mainteneur : > Comment lui signaler, ou sera t-il à l'Opensummit de décembre ? $ apt show gimp [...] Maintainer: Debian GNOME Maintainers -- Manu
Re: Gimp 2.10
On Friday 29 November 2019 18:23:06 Fabien R wrote: > On 29/11/2019 14:36, ajh-valmer wrote: > > On Friday 29 November 2019 13:13:05 Daniel Caillibaud wrote: > >> Effectivement, installer le paquet gimp-plugin-registry en ramène pas mal > >> d'autres avec plein de greffons, mais y'a quand même un pb, la doc fr > >> n'est pas très à jour, car sur mon install > >> file:///usr/share/gimp/2.0/help/fr/filters-enhance.html > > > > Hélas, non, toujours pas. > > Le lien ci-dessus concerne l'ancien Gimp 2.8. > > Constrate + netteté semblent avoir disparu dans Gimp 2.10 > > Buster supportera t-il la version 2.8 ou 2.9 ? > Tu devrais directement contacter le mainteneur : Coment lui signaler, ou sera t-il à l'Opensummit de décembre ?
Re: Gimp 2.10
On 29/11/2019 14:36, ajh-valmer wrote: > On Friday 29 November 2019 13:13:05 Daniel Caillibaud wrote: >> Effectivement, installer le paquet gimp-plugin-registry en ramène pas mal >> d'autres avec plein de greffons, mais y'a quand même un pb, la doc fr >> n'est pas très à jour, car sur mon install >> file:///usr/share/gimp/2.0/help/fr/filters-enhance.html > > Hélas, non, toujours pas. > > Le lien ci-dessus concerne l'ancien Gimp 2.8. > > Constrate + netteté semblent avoir disparu dans Gimp 2.10 > > Buster supportera t-il la version 2.8 ou 2.9 ? > Tu devrais directement contacter le maintener. -- Fabien
Re: Gimp 2.10
On Friday 29 November 2019 13:13:05 Daniel Caillibaud wrote: > Effectivement, installer le paquet gimp-plugin-registry en ramène pas mal > d'autres avec plein de greffons, mais y'a quand même un pb, la doc fr > n'est pas très à jour, car sur mon install > file:///usr/share/gimp/2.0/help/fr/filters-enhance.html Hélas, non, toujours pas. Le lien ci-dessus concerne l'ancien Gimp 2.8. Constrate + netteté semblent avoir disparu dans Gimp 2.10 Buster supportera t-il la version 2.8 ou 2.9 ?
Re: Gimp 2.10
Le 29/11/19 à 9h46, elguero eric a écrit : > je ne sais pas si le problème vient de là > mais dans Gimp, les filtres sont des > "plug-in", c'est-à-dire qu'ils ne sont pas > dans le coeur du logiciel. Il est possible > que Buster ne les installe pas par défaut. Effectivement, installer le paquet gimp-plugin-registry en ramène pas mal d'autres avec plein de greffons, mais y'a quand même un pb, la doc fr n'est pas très à jour, car sur mon install file:///usr/share/gimp/2.0/help/fr/filters-enhance.html me montre une capture avec filtres / améliorations / augmenter les contrastes filtres / améliorations / améliorer la netteté mais je ne les ait pas dans mon gimp 2.10 (celui du paquet qui affiche cette doc) Si j'ajoute le paquet gimp-help-en, la capture d'écran de file:///usr/share/gimp/2.0/help/en/filters-enhance.html est à jour (donc sans ces 2 entrées de menu) Je ne sais pas où est l'équivalent de ces deux entrées, tu peux chercher "contrast" dans le navigateur de greffons, avec gimp-plugin-registry j'en ai 4 (0 sinon). -- Daniel La peur de l'ennui est la seule excuse au travail. Jules Renard.
Re: Gimp 2.10
je ne sais pas si le problème vient de là mais dans Gimp, les filtres sont des "plug-in", c'est-à-dire qu'ils ne sont pas dans le coeur du logiciel. Il est possible que Buster ne les installe pas par défaut. e.e. Le jeudi 28 novembre 2019 à 19:28:47 UTC+1, ajh-valmer a écrit : On Thursday 28 November 2019 18:40:52 Jean-Pierre Giraud wrote: > Le 28/11/2019 à 17:03, ajh-valmer a écrit : > > On Monday 25 November 2019 Bernard Schoenacker wrote: > >>> De: "ajh-valmer" > >>> En migrant de Stretch à Buster, je découvre Gimp dernière version > >>> 2.10. > >>> Ou est passé dans le menu "filtres" => "Amélioration" => > >>> "Augmenter les contrastes et la netteté" ? > >>> Parfois, les nouvelles versions sont moins biens que les précédentes > > Ce ne serait pas Fltres/Améliorer/Renforcer la netteté ? : + contraste, c'était dans la version antérieure. > Dans ma version en français j'ai à la place Filtres/Amélioration/Sharpen > (Unsharp mask). Mais je me trompe peut-être. Ce n'est pas ça. Il y a dans le menu "couleur" => contraste, mais pas "netteté". À croire que personne n'utilise Gimp 2.10 ou les outils de contraste et de netteté sur la ML :-) Le menu "Boîte à outils" qui s'affiche à côté est devenu bien pâlot, on voit à peine ses petits logos.
Re: Gimp 2.10
Le lundi 25 novembre 2019 à 12:40 +0100, ajh-valmer a écrit : > Hello, > > En migrant de Stretch à Buster, je découvre Gimp dernière version > 2.10. > > Ou est passé dans le menu "filtres" => "Amélioration" => > "Augmenter les contrastes et la netteté" ? > > Parfois, les nouvelles versions sont moins biens que les précédentes > :-( > > A. Valmer > Moi j'utilise surtout GMIC pour ce genre d'opérations. Il y a quand même pas mal d'outils dedans.
Re: Gimp 2.10
On Thursday 28 November 2019 18:40:52 Jean-Pierre Giraud wrote: > Le 28/11/2019 à 17:03, ajh-valmer a écrit : > > On Monday 25 November 2019 Bernard Schoenacker wrote: > >>> De: "ajh-valmer" > >>> En migrant de Stretch à Buster, je découvre Gimp dernière version > >>> 2.10. > >>> Ou est passé dans le menu "filtres" => "Amélioration" => > >>> "Augmenter les contrastes et la netteté" ? > >>> Parfois, les nouvelles versions sont moins biens que les précédentes > > Ce ne serait pas Fltres/Améliorer/Renforcer la netteté ? : + contraste, c'était dans la version antérieure. > Dans ma version en français j'ai à la place Filtres/Amélioration/Sharpen > (Unsharp mask). Mais je me trompe peut-être. Ce n'est pas ça. Il y a dans le menu "couleur" => contraste, mais pas "netteté". À croire que personne n'utilise Gimp 2.10 ou les outils de contraste et de netteté sur la ML :-) Le menu "Boîte à outils" qui s'affiche à côté est devenu bien pâlot, on voit à peine ses petits logos.
Re: Gimp 2.10
Bonjour, Le 28/11/2019 à 17:03, ajh-valmer a écrit : > On Monday 25 November 2019 Bernard Schoenacker wrote: >>> De: "ajh-valmer" >>> En migrant de Stretch à Buster, je découvre Gimp dernière version >>> 2.10. >>> Ou est passé dans le menu "filtres" => "Amélioration" => >>> "Augmenter les contrastes et la netteté" ? >>> Parfois, les nouvelles versions sont moins biens que les précédentes Ce ne serait pas Fltres/Améliorer/Renforcer la netteté ? Dans ma version en français j'ai à la place Filtres/Amélioration/Sharpen (Unsharp mask). Mais je me trompe peut-être. Amicalement, jipege >> voici la méthode : >> https://docs.gimp.org/2.10/fr/gimp-filter-unsharp-mask.html >> https://docs.gimp.org/2.10/fr/plug-in-sharpen.html >> il suffisait de gratter un peut ... > Je rêve... > et en plus "il suffisait de gratter un peu..." > Ces liens expliquent selon l'ancienne version de Gimp. > Il aurait fallu lire plus attentivement mon mail ci-dessus. > > Dans la 2.10, "Augmenter les contrastes et la netteté", > on ne sait ou il est passé ? >
Re: Gimp 2.10
On Monday 25 November 2019 Bernard Schoenacker wrote: > > De: "ajh-valmer" > > En migrant de Stretch à Buster, je découvre Gimp dernière version > > 2.10. > > Ou est passé dans le menu "filtres" => "Amélioration" => > > "Augmenter les contrastes et la netteté" ? > > Parfois, les nouvelles versions sont moins biens que les précédentes > voici la méthode : > https://docs.gimp.org/2.10/fr/gimp-filter-unsharp-mask.html > https://docs.gimp.org/2.10/fr/plug-in-sharpen.html > il suffisait de gratter un peut ... Je rêve... et en plus "il suffisait de gratter un peu..." Ces liens expliquent selon l'ancienne version de Gimp. Il aurait fallu lire plus attentivement mon mail ci-dessus. Dans la 2.10, "Augmenter les contrastes et la netteté", on ne sait ou il est passé ?
Re: Gimp 2.10
- Mail original - > De: "ajh-valmer" > À: debian-user-french@lists.debian.org > Envoyé: Lundi 25 Novembre 2019 12:40:41 > Objet: Gimp 2.10 > > Hello, > > En migrant de Stretch à Buster, je découvre Gimp dernière version > 2.10. > > Ou est passé dans le menu "filtres" => "Amélioration" => > "Augmenter les contrastes et la netteté" ? > > Parfois, les nouvelles versions sont moins biens que les précédentes > :-( > > A. Valmer > bonjour, voici la méthode : https://docs.gimp.org/2.10/fr/gimp-filter-unsharp-mask.html https://docs.gimp.org/2.10/fr/plug-in-sharpen.html il suffisait de gratter un peut ... @+ bernard
Gimp 2.10
Hello, En migrant de Stretch à Buster, je découvre Gimp dernière version 2.10. Ou est passé dans le menu "filtres" => "Amélioration" => "Augmenter les contrastes et la netteté" ? Parfois, les nouvelles versions sont moins biens que les précédentes :-( A. Valmer
Re: Gimp crash on screenshot debian bullseye
Opened https://gitlab.gnome.org/GNOME/gimp/issues/3955 bug report upstream Renato Gallo System Engineer sede legale e operativa: Via Privata Cefalonia, 14 - 20156 - Milano (MI) Tel. +39 02 - 87049490 Fax +39 02 - 48677349 Mobile. +39 342 - 6350524 Wi | FreeNumbers: https://freenumbers.way-interactive.com Wi | SMS: https://sms.way-interactive.com Wi | Voip: https://voip.way-interactive.com Asterweb: http://www.asterweb.org Le informazioni contenute in questo messaggio e negli eventuali allegati sono riservate e per uso esclusivo del destinatario. Persone diverse dallo stesso non possono copiare o distribuire il messaggio a terzi. Chiunque riceva questo messaggio per errore è pregato di distruggerlo e di informare immediatamente [ mailto:i...@sigmaware.it | info@ ] asterweb.org - Original Message - From: "Cindy Sue Causey" To: "debian-user" Sent: Wednesday, September 18, 2019 8:26:06 PM Subject: Re: Gimp crash on screenshot debian bullseye UPDATE: Bullseye's *GIMP upgrade now WORKS (for me)!* On 9/18/19, Cindy Sue Causey wrote: > On 9/18/19, Renato Gallo wrote: >> GIMP crash on taking a screenshot > > > Hey, Renato.. I myself tuned out as soon as I saw the word "Kali" the > other day. Didn't realize it was about GIMP.. so YEAH, ME, TOO! DEBIAN > Bullseye upgrade a couple days ago. What didn't click in mind for the first response I posted was that we were possibly both talking about PNG files. My copy failed while trying to click open then edit some Xfce4 printscreen PNG files by right clicking from within Thunar file manager. > PS *VERY COOL* how they do what they do there. I think I took a > printscreen to share in places such as here at Debian-User as an > example for others to potentially pursue in their own projects. > > Did you file a bug report? How they present that crash information > made it look SUPER easy to follow up by reaching out to them directly. > > Me? I, u.. purged mine before pursuing. I was going to try to > regress. Never got the whoosie-what's-it terminal command correct to > step back down to a functional package that I NEED DESPERATELY. So the purging the other day meant I had to reinstall SOMETHING in order to possibly help test why GIMP's upgrade failed. I decided to reinstall the upgrade so I could next gain the skill of a hopefully successful downgrade. Reinstalling the buggy upgrade triggered TWO MORE package downloads/upgrades just now: libgegl-common and libgegl-0.4-0. They must have been the problem because my copy works for PNG, JPEG, and XCF files all opened again from within Thunar. So maybe that will help you now? If not, there's still always those nice bug reporting directions that were in the COOL popup that *my* copy presented, anyway. > PPS I tripped over new apt-get skills in the process so I am SO NOT > complaining! :D > > GIMP does make it look REALLY easy to help them out if you follow > their directions (in case anyone else encounters this). *VERY COOL, > VERY COGNITIVELY FRIENDLY FEATURE!!!* Surprised the doodah out of me > when it popped up because their product has ALWAYS worked flawlessly > for the almost 2 decades I've been playing in their sandbox. > > >> GNU Image Manipulation Program version 2.10.8 >> git-describe: GIMP_2_10_6-294-ga967e8d2c2 >> C compiler: >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper >> OFFLOAD_TARGET_NAMES=nvptx-none:hsa >> OFFLOAD_TARGET_DEFAULT=1 > >> < Rest snipped for brevity > PPPS Learned something else on the fly here: Installs WILL occur even if specifically requested after apt-mark has been used to mark something on hold. That's nice to know. It was a thumbs up since I DID want to install a package while knowing that package had been deliberately placed on momentary hold... purely because we can. It was all about poking around under the Debian hood again since this upgrade fail opportunity unexpectedly presented itself. I think this may be the first package crash I've EVER experienced. Ditto on the *thumbs up* for that because my email inbox hints that time span may go back almost TEN YEARS. :) S regarding my downgrade attempt the other day: If this Debian wiki page is anywhere near correct, I keyed in the right command the other day so I don't know WHY my GIMP downgrade attempt failed: https://wiki.debian.org/RollbackUpdate I'm going to tinker around with that again just for fun and 'cause it left the taste of #FAIL in its tracks. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with.. a fabulous new grasp of WHY we use deb-src in apt/apt-get sources *
Re: Gimp crash on screenshot debian bullseye
UPDATE: Bullseye's *GIMP upgrade now WORKS (for me)!* On 9/18/19, Cindy Sue Causey wrote: > On 9/18/19, Renato Gallo wrote: >> GIMP crash on taking a screenshot > > > Hey, Renato.. I myself tuned out as soon as I saw the word "Kali" the > other day. Didn't realize it was about GIMP.. so YEAH, ME, TOO! DEBIAN > Bullseye upgrade a couple days ago. What didn't click in mind for the first response I posted was that we were possibly both talking about PNG files. My copy failed while trying to click open then edit some Xfce4 printscreen PNG files by right clicking from within Thunar file manager. > PS *VERY COOL* how they do what they do there. I think I took a > printscreen to share in places such as here at Debian-User as an > example for others to potentially pursue in their own projects. > > Did you file a bug report? How they present that crash information > made it look SUPER easy to follow up by reaching out to them directly. > > Me? I, u.. purged mine before pursuing. I was going to try to > regress. Never got the whoosie-what's-it terminal command correct to > step back down to a functional package that I NEED DESPERATELY. So the purging the other day meant I had to reinstall SOMETHING in order to possibly help test why GIMP's upgrade failed. I decided to reinstall the upgrade so I could next gain the skill of a hopefully successful downgrade. Reinstalling the buggy upgrade triggered TWO MORE package downloads/upgrades just now: libgegl-common and libgegl-0.4-0. They must have been the problem because my copy works for PNG, JPEG, and XCF files all opened again from within Thunar. So maybe that will help you now? If not, there's still always those nice bug reporting directions that were in the COOL popup that *my* copy presented, anyway. > PPS I tripped over new apt-get skills in the process so I am SO NOT > complaining! :D > > GIMP does make it look REALLY easy to help them out if you follow > their directions (in case anyone else encounters this). *VERY COOL, > VERY COGNITIVELY FRIENDLY FEATURE!!!* Surprised the doodah out of me > when it popped up because their product has ALWAYS worked flawlessly > for the almost 2 decades I've been playing in their sandbox. > > >> GNU Image Manipulation Program version 2.10.8 >> git-describe: GIMP_2_10_6-294-ga967e8d2c2 >> C compiler: >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper >> OFFLOAD_TARGET_NAMES=nvptx-none:hsa >> OFFLOAD_TARGET_DEFAULT=1 > >> < Rest snipped for brevity > PPPS Learned something else on the fly here: Installs WILL occur even if specifically requested after apt-mark has been used to mark something on hold. That's nice to know. It was a thumbs up since I DID want to install a package while knowing that package had been deliberately placed on momentary hold... purely because we can. It was all about poking around under the Debian hood again since this upgrade fail opportunity unexpectedly presented itself. I think this may be the first package crash I've EVER experienced. Ditto on the *thumbs up* for that because my email inbox hints that time span may go back almost TEN YEARS. :) S regarding my downgrade attempt the other day: If this Debian wiki page is anywhere near correct, I keyed in the right command the other day so I don't know WHY my GIMP downgrade attempt failed: https://wiki.debian.org/RollbackUpdate I'm going to tinker around with that again just for fun and 'cause it left the taste of #FAIL in its tracks. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with.. a fabulous new grasp of WHY we use deb-src in apt/apt-get sources *
Re: Gimp crash on screenshot debian bullseye
On 9/18/19, Renato Gallo wrote: > GIMP crash on taking a screenshot Hey, Renato.. I myself tuned out as soon as I saw the word "Kali" the other day. Didn't realize it was about GIMP.. so YEAH, ME, TOO! DEBIAN Bullseye upgrade a couple days ago. PS *VERY COOL* how they do what they do there. I think I took a printscreen to share in places such as here at Debian-User as an example for others to potentially pursue in their own projects. Did you file a bug report? How they present that crash information made it look SUPER easy to follow up by reaching out to them directly. Me? I, u.. purged mine before pursuing. I was going to try to regress. Never got the whoosie-what's-it terminal command correct to step back down to a functional package that I NEED DESPERATELY. PPS I tripped over new apt-get skills in the process so I am SO NOT complaining! :D GIMP does make it look REALLY easy to help them out if you follow their directions (in case anyone else encounters this). *VERY COOL, VERY COGNITIVELY FRIENDLY FEATURE!!!* Surprised the doodah out of me when it popped up because their product has ALWAYS worked flawlessly for the almost 2 decades I've been playing in their sandbox. > GNU Image Manipulation Program version 2.10.8 > git-describe: GIMP_2_10_6-294-ga967e8d2c2 > C compiler: > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none:hsa > OFFLOAD_TARGET_DEFAULT=1 > < Rest snipped for brevity > Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with.. a fabulous new grasp of WHY we use deb-src in apt/apt-get sources *
Gimp crash on screenshot debian bullseye
GIMP crash on taking a screenshot ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 6172 - Thread 6172 # [New LWP 6173] [New LWP 6174] [New LWP 6175] [New LWP 6176] [New LWP 6177] [New LWP 6178] [New LWP 6179] [New LWP 6180] [New LWP 6181] [New LWP 6182] [New LWP 6197] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f79a1c562cc in read () from /lib/x86_64-linux-gnu/libpthread.so.0 Id Target Id Frame * 1Thread 0x7f799fe15e00 (LWP 6172) "gimp"0x7f79a1c562cc in read () from /lib/x86_64-linux-gnu/libpthread.so.0 2Thread 0x7f799eed5700 (LWP 6173) "gmain" 0x7f79a1b71edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 3Thread 0x7f799dd08700 (LWP 6174) "gdbus" 0x7f79a1b71edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 4Thread 0x7f798bfff700 (LWP 6175) "async" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 5Thread 0x7f798b7fe700 (LWP 6176) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 6Thread 0x7f798affd700 (LWP 6177) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 7Thread 0x7f798a7fc700 (LWP 6178) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 8Thread 0x7f7989ffb700 (LWP 6179) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 9Thread 0x7f79897fa700 (LWP 6180) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 10 Thread 0x7f7988ff9700 (LWP 6181) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 11 Thread 0x7f7973fff700 (LWP 6182) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 12 Thread 0x7f79737fe700 (LWP 6197) "swap writer" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 Thread 12 (Thread 0x7f79737fe700 (LWP 6197)): #0 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f79a1e4895f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7f79a22f30cd in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0 No symbol table info available. #3 0x7f79a1e2689d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #4 0x7f79a1c4cfb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #5 0x7f79a1b7c49f in clone () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. Thread 11 (Thread 0x7f7973fff700 (LWP 6182)): #0 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f79a1e4895f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/li
Gimp crash on screenshot debian bullseye
what I wrote is not - Original Message - From: "Jonas Smedegaard" To: "MMIROJV" , "debian-user" Sent: Wednesday, September 18, 2019 2:46:38 PM Subject: Re: Gimp crash on Open File | Kali Linux XFCE Quoting MMIROJV (2019-09-18 13:55:04) > [lots of debug noise but no question or other comment] Hi MMIROJV, Please report bugs in Kali Linux to the developers of Kali Linux. This is a Debian user mailinglist - feel free to share _user_ experiences with other users here. That inlcudes experiences using Debian in the derived form as redistributed by Kali Linux, but in that case please beware that you are targeting a wider audience, so please mention explicitly - in context, not only in subject - that you don't use regular Debian. Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Re: Gimp crash on Open File | Kali Linux XFCE
Quoting MMIROJV (2019-09-18 13:55:04) > [lots of debug noise but no question or other comment] Hi MMIROJV, Please report bugs in Kali Linux to the developers of Kali Linux. This is a Debian user mailinglist - feel free to share _user_ experiences with other users here. That inlcudes experiences using Debian in the derived form as redistributed by Kali Linux, but in that case please beware that you are targeting a wider audience, so please mention explicitly - in context, not only in subject - that you don't use regular Debian. Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Gimp crash on Open File | Kali Linux XFCE
GIMP crash on taking a screenshot ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 6172 - Thread 6172 # [New LWP 6173] [New LWP 6174] [New LWP 6175] [New LWP 6176] [New LWP 6177] [New LWP 6178] [New LWP 6179] [New LWP 6180] [New LWP 6181] [New LWP 6182] [New LWP 6197] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f79a1c562cc in read () from /lib/x86_64-linux-gnu/libpthread.so.0 Id Target Id Frame * 1 Thread 0x7f799fe15e00 (LWP 6172) "gimp" 0x7f79a1c562cc in read () from /lib/x86_64-linux-gnu/libpthread.so.0 2 Thread 0x7f799eed5700 (LWP 6173) "gmain" 0x7f79a1b71edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 3 Thread 0x7f799dd08700 (LWP 6174) "gdbus" 0x7f79a1b71edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 4 Thread 0x7f798bfff700 (LWP 6175) "async" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 5 Thread 0x7f798b7fe700 (LWP 6176) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 6 Thread 0x7f798affd700 (LWP 6177) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 7 Thread 0x7f798a7fc700 (LWP 6178) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 8 Thread 0x7f7989ffb700 (LWP 6179) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 9 Thread 0x7f79897fa700 (LWP 6180) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 10 Thread 0x7f7988ff9700 (LWP 6181) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 11 Thread 0x7f7973fff700 (LWP 6182) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 12 Thread 0x7f79737fe700 (LWP 6197) "swap writer" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 Thread 12 (Thread 0x7f79737fe700 (LWP 6197)): #0 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f79a1e4895f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7f79a22f30cd in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0 No symbol table info available. #3 0x7f79a1e2689d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #4 0x7f79a1c4cfb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #5 0x7f79a1b7c49f in clone () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. Thread 11 (Thread 0x7f7973fff700 (LWP 6182)): #0 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f79a1e4895f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x55b3f63ced73 in ?? () No symbol table info available. #3 0x7f79a1e2
Gimp crash on Open File | Kali Linux XFCE
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6'
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2
--prefix=/usr --with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6)
using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 19806 - Thread 19806 #
[New LWP 19807]
[New LWP 19808]
[New LWP 19809]
[New LWP 19810]
[New LWP 19811]
[New LWP 19812]
[New LWP 20570]
[New LWP 20648]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffdbdc64f10, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f65440fae00 (LWP 19806) "gimp-2.10" __libc_read
(nbytes=256, buf=0x7ffdbdc64f10, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f654314f700 (LWP 19807) "gmain"
0x7f6545e55819 in __GI___poll (fds=0x7f65380018d0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
3Thread 0x7f654294e700 (LWP 19808) "gdbus"
0x7f6545e55819 in __GI___poll (fds=0x5560a30a2dc0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7f65351d1700 (LWP 19809) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f65349d0700 (LWP 19810) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f652bfff700 (LWP 19811) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f652b7fe700 (LWP 19812) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f65217fa700 (LWP 20570) "pool-gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7f6520ff9700 (LWP 20648) "swap writer"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 9 (Thread 0x7f6520ff9700 (LWP 20648)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f654616c95f in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f65466170cd in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f654614a89d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f6545f31fa3 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140072322045696,
5207195672897314293, 140727787342046, 140727787342047, 140072322045696,
93873605134592, -5293439168683254283, -5293656979864232459}, mask_was_saved
= 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup =
0x0, canceltype = 0}}}
not_first_call =
#5 0x7f6545e604cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 8 (Thread 0x7f65217fa700 (LWP 20570)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f654616ca7f in g_cond_wait_until () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f65460f30c1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7f65460f3681 in
Re: Arrow annotation in GIMP.
On Mon, 16 Sep 2019 12:55:46 +0200 Siard wrote: > Op Sun, 15 Sep 2019 16:55 -0700, pe...@easthope.ca wrote: > > > > Is another layer necessary? Can't the arrow be pasted directly > > onto the image? > > I guess that a separate layer makes it easier to position the arrow. > Then Image > Flatten Image to join the layers. > Always use extra layers when you can, and keep them separate. Exporting as jpg, png etc. will automatically combine them in the exported file, but you can still go back to the gimp file and make further changes to individual layers. It's easy to merge layers, but damn difficult to separate them again if you need to edit one. It's always a good idea to keep any original graphic on its own layer, then you still have a clean original if you need to remake the edited masterpiece. If necessary, copy the original to another layer and make that one invisible. It's depressing how often you need to abandon a disaster and start again (well, I do anyway), and this is easiest if you already have your original installed on a spare layer. Yes, there is 'undo', but that can be limited with a complex artwork. You don't want to discover the limitation when it's too late. -- Joe
Re: Arrow annotation in GIMP.
Op Sun, 15 Sep 2019 16:55 -0700, pe...@easthope.ca wrote: > * From: Dan Ritter > * Date: Wed, 14 Aug 2019 08:26:18 -0400 > > Open a new image. > > Right. > > > Set the background to transparent. > > Haven't quite got that. File > New In the dialog 'Create a New File': Advanced Options > Fill with > Transparency > From reading a few weeks ago, I added an alpha channel > (Layer > Transparency > Add Alpha Channel). Don't see how to make > anything transparent. Then select everything you want to make transparent and delete, OR: Layer > Transparency > Color to Alpha then change any color (usually white) to 'Alpha', i.e. transparency. Note that it cannot be exported to jpg, because it does not support transparency. png does. > > Draw an arrow. Save it. Don't close it. > > I managed to choose the pencil, set the background color to white > and the forground to red, and drew an arrow with straight lines using > the shift constraint. Note that a script for drawing an arrow exists, which makes it a lot easier. It can be found in many places, e.g. here: www.gimp-forum.net/Thread-Arrow-Script I have the script arrow-set-size.scm in ~/.config/GIMP/2.10/scripts Then in Gimp: Tools > Arrow-set-size > > Create a new layer on top. > > Is another layer necessary? Can't the arrow be pasted directly onto > the image? I guess that a separate layer makes it easier to position the arrow. Then Image > Flatten Image to join the layers.
Re: Arrow annotation in GIMP.
On 2019-09-16 00:55, pe...@easthope.ca wrote: * From: Dan Ritter * Date: Wed, 14 Aug 2019 08:26:18 -0400 Open a new image. Right. Set the background to transparent. Haven't quite got that. From reading a few weeks ago, I added an alpha channel (Layer > Transparency > Add Alpha Channel). Don't see how to make anything transparent. after add alpha channel you want to select everything except the thing you want and then delete. That can be on a layer or a separate document that you copy paste where you want. mick -- Key ID4BFEBB31
Re: Arrow annotation in GIMP.
* From: Dan Ritter * Date: Wed, 14 Aug 2019 08:26:18 -0400 > Open a new image. Right. > Set the background to transparent. Haven't quite got that. From reading a few weeks ago, I added an alpha channel (Layer > Transparency > Add Alpha Channel). Don't see how to make anything transparent. > Draw an arrow. Save it. Don't close it. I managed to choose the pencil, set the background color to white and the forground to red, and drew an arrow with straight lines using the shift constraint. > Create a new layer on top. Is another layer necessary? Can't the arrow be pasted directly onto the image? Thanks, ... Peter E. -- https://en.wikibooks.org/wiki/Medical_Machines https://en.wikibooks.org/wiki/Oberon Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: GIMP crashed with a fatal error: fatal error: Violación de segmento
Si un ave no rompe su huevo morirá antes de nacer. Nosotros somos el ave y el mundo es nuestro huevo. POR LA REVOLUCIÓN DEL MUNDO Ciudad de México El mié., 11 sept. 2019 a las 23:30, santo motorola () escribió: > ``` > GNU Image Manipulation Program version 2.10.8 > git-describe: GIMP_2_10_6-294-ga967e8d2c2 > C compiler: > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none:hsa > OFFLOAD_TARGET_DEFAULT=1 > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' > --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs > --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 > --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id > --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix > --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --with-default-libstdcxx-abi=new --enable-gnu-unique-object > --disable-vtable-verify --enable-plugin --enable-default-pie > --with-system-zlib --with-target-system-zlib=auto --enable-multiarch > --disable-werror --with-arch-32=i686 --with-abi=m64 > --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic > --enable-offload-targets=nvptx-none,hsa --without-cuda-driver > --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu > --target=x86_64-linux-gnu > Thread model: posix > gcc version 9.2.1 20190827 (Debian 9.2.1-6) > > using GEGL version 0.4.12 (compiled against version 0.4.14) > using GLib version 2.60.6 (compiled against version 2.60.6) > using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) > using GTK+ version 2.24.32 (compiled against version 2.24.32) > using Pango version 1.42.3 (compiled against version 1.42.3) > using Fontconfig version 2.13.1 (compiled against version 2.13.1) > using Cairo version 1.16.0 (compiled against version 1.16.0) > > ``` > > fatal error: Violación de segmento > Primero: usa memtest para revisar que tu memoria ram esté bien. Segundo: pasanos detalles sobre tu hardware, > > Stack trace: > ``` > /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f89a879ff98] > gimp-2.10(+0xd1590)[0x5625eabba590] > gimp-2.10(+0xd19b8)[0x5625eabba9b8] > gimp-2.10(+0xd2029)[0x5625eabbb029] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f89a7c98730] > gimp-2.10(gimp_gegl_mask_is_empty+0x91)[0x5625eafa5411] > gimp-2.10(+0x3b7810)[0x5625eaea0810] > gimp-2.10(+0x42ec18)[0x5625eaf17c18] > gimp-2.10(+0x3d5b50)[0x5625eaebeb50] > gimp-2.10(+0x42f2aa)[0x5625eaf182aa] > gimp-2.10(gimp_drawable_set_buffer_full+0x1cb)[0x5625eaebd9bb] > gimp-2.10(gimp_drawable_set_buffer+0x11d)[0x5625eaebdf9d] > gimp-2.10(gimp_drawable_new+0x106)[0x5625eaebe296] > gimp-2.10(gimp_layer_new+0x90)[0x5625eaf1b4d0] > gimp-2.10(+0x3319cc)[0x5625eae1a9cc] > gimp-2.10(gimp_procedure_execute+0x237)[0x5625eae53577] > gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5625eae4ca39] > gimp-2.10(gimp_plug_in_handle_message+0x216)[0x5625eae57626] > gimp-2.10(+0x36cf91)[0x5625eae55f91] > > /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f89a7e7d898] > /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7f89a7e7dc88] > > /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f89a7e7df82] > gimp-2.10(gimp_plug_in_manager_call_run+0x5fc)[0x5625eae6735c] > gimp-2.10(+0x376dbe)[0x5625eae5fdbe] > gimp-2.10(gimp_procedure_execute+0x237)[0x5625eae53577] > gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5625eae4ca39] > gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cd)[0x5625eae4cefd] > gimp-2.10(file_open_image+0x33d)[0x5625eaf4d6fd] > gimp-2.10(file_open_with_proc_and_display+0x29d)[0x5625eaf4e64d] > gimp-2.10(+0x113573)[0x5625eabfc573] > gimp-2.10(+0x1138b7)[0x5625eabfc8b7] > > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d] > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f89a7f77555] > > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae] > > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f] > > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d] > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f89a7f77555] > > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae] > > /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f] > /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8de25)[0x7f89a894ce25] > > /lib/
GIMP crashed with a fatal error: fatal error: Violación de segmento
``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Violación de segmento Stack trace: ``` /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f89a879ff98] gimp-2.10(+0xd1590)[0x5625eabba590] gimp-2.10(+0xd19b8)[0x5625eabba9b8] gimp-2.10(+0xd2029)[0x5625eabbb029] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f89a7c98730] gimp-2.10(gimp_gegl_mask_is_empty+0x91)[0x5625eafa5411] gimp-2.10(+0x3b7810)[0x5625eaea0810] gimp-2.10(+0x42ec18)[0x5625eaf17c18] gimp-2.10(+0x3d5b50)[0x5625eaebeb50] gimp-2.10(+0x42f2aa)[0x5625eaf182aa] gimp-2.10(gimp_drawable_set_buffer_full+0x1cb)[0x5625eaebd9bb] gimp-2.10(gimp_drawable_set_buffer+0x11d)[0x5625eaebdf9d] gimp-2.10(gimp_drawable_new+0x106)[0x5625eaebe296] gimp-2.10(gimp_layer_new+0x90)[0x5625eaf1b4d0] gimp-2.10(+0x3319cc)[0x5625eae1a9cc] gimp-2.10(gimp_procedure_execute+0x237)[0x5625eae53577] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5625eae4ca39] gimp-2.10(gimp_plug_in_handle_message+0x216)[0x5625eae57626] gimp-2.10(+0x36cf91)[0x5625eae55f91] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f89a7e7d898] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7f89a7e7dc88] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f89a7e7df82] gimp-2.10(gimp_plug_in_manager_call_run+0x5fc)[0x5625eae6735c] gimp-2.10(+0x376dbe)[0x5625eae5fdbe] gimp-2.10(gimp_procedure_execute+0x237)[0x5625eae53577] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5625eae4ca39] gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cd)[0x5625eae4cefd] gimp-2.10(file_open_image+0x33d)[0x5625eaf4d6fd] gimp-2.10(file_open_with_proc_and_display+0x29d)[0x5625eaf4e64d] gimp-2.10(+0x113573)[0x5625eabfc573] gimp-2.10(+0x1138b7)[0x5625eabfc8b7] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f89a7f77555] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f89a7f77555] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8de25)[0x7f89a894ce25] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x276a4)[0x7f89a7f776a4] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8cd69)[0x7f89a894bd69] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1331eb)[0x7f89a89f21eb] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x26dad)[0x7f89a7f76dad] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x47b)[0x7f89a7f7fb9b] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f] /lib/x86_64-linux-gnu/libgtk-x11-
Gimp 2.10.8 crash
``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Errore di segmentazione Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f3915b9ff98] gimp-2.10(+0xd1590)[0x5645c93e3590] gimp-2.10(+0xd19b8)[0x5645c93e39b8] gimp-2.10(+0xd2029)[0x5645c93e4029] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f3915098730] gimp-2.10(gimp_gegl_mask_is_empty+0x91)[0x5645c97ce411] gimp-2.10(+0x3b7810)[0x5645c96c9810] gimp-2.10(+0x42ec18)[0x5645c9740c18] gimp-2.10(+0x3d5b50)[0x5645c96e7b50] gimp-2.10(+0x42f2aa)[0x5645c97412aa] gimp-2.10(gimp_drawable_set_buffer_full+0x1cb)[0x5645c96e69bb] gimp-2.10(gimp_drawable_set_buffer+0x11d)[0x5645c96e6f9d] gimp-2.10(gimp_drawable_new+0x106)[0x5645c96e7296] gimp-2.10(gimp_layer_new+0x90)[0x5645c97444d0] gimp-2.10(+0x3319cc)[0x5645c96439cc] gimp-2.10(gimp_procedure_execute+0x237)[0x5645c967c577] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5645c9675a39] gimp-2.10(gimp_plug_in_handle_message+0x216)[0x5645c9680626] gimp-2.10(+0x36cf91)[0x5645c967ef91] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f391527d898] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7f391527dc88] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f391527df82] gimp-2.10(gimp_plug_in_manager_call_run+0x5fc)[0x5645c969035c] gimp-2.10(+0x376dbe)[0x5645c9688dbe] gimp-2.10(gimp_procedure_execute+0x237)[0x5645c967c577] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5645c9675a39] gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cd)[0x5645c9675efd] gimp-2.10(file_open_image+0x33d)[0x5645c97766fd] gimp-2.10(file_open_with_proc_and_display+0x29d)[0x5645c977764d] gimp-2.10(+0x113573)[0x5645c9425573] gimp-2.10(+0x1138b7)[0x5645c94258b7] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f3915377555] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f39153804ae] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3915380b6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f3915377555] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f39153804ae] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3915380b6f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8de25)[0x7f3915d4ce25] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x276a4)[0x7f39153776a4] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f39153804ae] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3915380b6f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8cd69)[0x7f3915d4bd69] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1331eb)[0x7f3915df21eb] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x26dad)[0x7f3915376dad] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_val
