Re: Crosshairs in gimp 2.10.22 in Debian 11.7.

[peter]

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.

[Dan Ritter]

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.

[peter]

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

gimp scripts

[mick.crane]

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

Re: Trimming boundary of image in GIMP.

[peter]

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.

[Tixy]

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.

[The Wanderer]

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.

[peter]

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.

[tomas]

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.

[Tixy]

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.

[Tixy]

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.

[Tixy]

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.

[peter]

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.

[Tixy]

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.

[peter]

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!

[Weaver]

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!

[riveravaldez]

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!

[Rebecca Matthews]

```
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

[Andrei POPESCU]

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

[Joachim Fahnenmüller]

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

[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.

Re: Can't start Gimp in Bullseye

[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.

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: Can't start Gimp in Bullseye

[Weaver]

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

[Joachim Fahnenmüller]

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

[Kent West]

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

[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


-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Can't start Gimp in Bullseye

[Joachim Fahnenmüller]

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

[Ryan Young]

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}}, pr

Re: Gimp crash on screenshot debian bullseye

[Renato Gallo]

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

[Cindy Sue Causey]

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

[Cindy Sue Causey]

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

[Renato Gallo]

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

Gimp crash on screenshot debian bullseye

[Renato Gallo]

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

[Jonas Smedegaard]

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

[Renato Gallo]

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 0x00

Gimp crash on Open File | Kali Linux XFCE

[MMIROJV]

```
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  0x7f6546

Re: Arrow annotation in GIMP.

[Joe]

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.

[Siard]

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.

[mick crane]

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.

[peter]

*   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

Gimp 2.10.8 crash

[caliandro adriano]

```
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_signa

Re: Arrow annotation in GIMP.

[tomas]

On Fri, Aug 16, 2019 at 10:40:59AM -0700, pe...@easthope.ca wrote:
> From: Dan Ritter 
> Date: Wed, 14 Aug 2019 08:26:18 -0400
> > Set the background to transparent.
> 

[...]

> Really I don't understand the representation used in GIMP. From what 
> I've read, there are three channels, R, G, B.  OK.  Plus an optional 
> 4th, alpha. What is it?

There are four: RGBA -- [1] should address your other questions. The
alpha channel is useful when you overlay images (like in your arrow
case): you want the arrow be "on top" of your image, but you don't
want the arrow's background obscuring the rest of your image.

You could achieve that with a "mask" (an array of bits of your image's
size with an 1 for each "relevant" pixel and a 0 for each "irrelevant"
one). This is an alpha channel with one bit depth. A deeper alpha
channel allows semi-transparency, where the foreground image could,
for example, merge "softly" into the background.

A neat effect would be to make your arrow semi-transparent: you
would still see through, as if the arrow was smoked glass.

Best you play with that under Gimp, then you'll "get" it quickly.

Cheers

[1] https://en.wikipedia.org/wiki/RGBA
-- t


signature.asc
Description: Digital signature

Re: Arrow annotation in GIMP.

[peter]

From: Dan Ritter 
Date: Wed, 14 Aug 2019 08:26:18 -0400
> Set the background to transparent.

Menus: Layer > Tranparency > Add Alpha Channel. The new viewer remains 
black.  Might be transparent. Might not.  (If all else fails, will see 
what happens when the arrow is dropped on the image layer.  If the 
result has the appearance of the arrow layer, the arrow background is 
not transparent and my image is obscured.)

Really I don't understand the representation used in GIMP. From what 
I've read, there are three channels, R, G, B.  OK.  Plus an optional 
4th, alpha. What is it?

What is the point of alpha? Transparent should be simply no marking.  
RGB = (0,0,0). What does alpha represent?  

Thanks, ... P.

-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Unicode in GIMP Text Tool.

[tomas]

On Wed, Aug 14, 2019 at 05:26:16PM -0500, David Wright wrote:

[...]

> You're welcome to use anything from
> https://lists.debian.org/debian-user/2019/07/msg00926.html

Nice post, thanks for it -- I must have missed it at a moment
of high load.

> Most of the methods I see posted have limitations (like non-VC).

> > [1] 
> > https://unix.stackexchange.com/questions/185349/is-there-a-universal-way-to-write-unicode-characters


...and this is surely one. It works for Gtk+ applications (doh,
I think it's spelt Gtk these days?), it doesn't for plain X, much
less for the Linux VC. Dunno about Qt.

This is indeed a sad situation. Debian goes to some lengths to
unify X and the VCs -- whereas all the "user-experience-y" GUIs
out there seem to go out of their way to break as much as they
can -- as if they were competitors for market share. I guess
some anti-patterns are just hard to unlearn.

In this context I've to thank you, David, for your heroic effort,
and thanks for writing so nicely about it!

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: Unicode in GIMP Text Tool.

[David Wright]

On Wed 14 Aug 2019 at 23:44:31 (+0200), to...@tuxteam.de wrote:
> On Wed, Aug 14, 2019 at 02:04:21PM -0700, pe...@easthope.ca wrote:
> > *   From: deloptes 
> > *   Date: Wed, 14 Aug 2019 22:16:16 +0200
> > > what DE are you using?
> > 
> > LX
> > 
> > > I open the char selector (each desktop I know has one) and select the char
> > > to import - than copy/paste into the text box
> > 
> > Good idea.  Copy and paste the character; from the Web browser maybe.  
> > I was typing the character entity reference in the GIMP tool.
> 
> You might have more luck with the Unicode input method, CTRL-SHIFT-U, then
> the hexadecimal code [1]
> 
> For characters you use often, you can set up a compose sequence.
> 
> Just ask :)

You're welcome to use anything from
https://lists.debian.org/debian-user/2019/07/msg00926.html
Most of the methods I see posted have limitations (like non-VC).

> [1] 
> https://unix.stackexchange.com/questions/185349/is-there-a-universal-way-to-write-unicode-characters

Cheers,
David.

Re: Unicode in GIMP Text Tool.

[tomas]

On Wed, Aug 14, 2019 at 02:04:21PM -0700, pe...@easthope.ca wrote:
> * From: deloptes 
> * Date: Wed, 14 Aug 2019 22:16:16 +0200
> > what DE are you using?
> 
> LX
> 
> > I open the char selector (each desktop I know has one) and select the char
> > to import - than copy/paste into the text box
> 
> Good idea.  Copy and paste the character; from the Web browser maybe.  
> I was typing the character entity reference in the GIMP tool.

You might have more luck with the Unicode input method, CTRL-SHIFT-U, then
the hexadecimal code [1]

For characters you use often, you can set up a compose sequence.

Just ask :)

Cheers

[1] 
https://unix.stackexchange.com/questions/185349/is-there-a-universal-way-to-write-unicode-characters

-- tomás


signature.asc
Description: Digital signature

Re: Re (2): Arrow annotation in GIMP.

[David Wright]

On Wed 14 Aug 2019 at 08:51:55 (-0700), pe...@easthope.ca wrote:
> BEGIN ANOTHER TEDIOUS ASIDE
> No References in the "header" of the Web page this replies to.  
> Consequently I snagged the Messge-Id  (Message-id?) from the Web page 
> for my original message.  Let's see how References comes out.  >8~|

You appear to have inserted the magnifying glass again, albeit in a
less destructive manner. The web page might put it between the <> to
indicate that the link will search for that reference, but you can't
reuse its display presentation like that in a posting without deleting
the eye candy.

> END ANOTHER TEDIOUS ASIDE

> I haven't found whether GIMP is Unicode capable. If ࢗ is typed 
> at the insertion point for the Text tool, can the lower-left pointing 
> arrow be displayed.  Hasn't succeeded here yet.

Of all the ways of notating Unicode, you've assumed that Gimp will
honour HTML's, and there's no reason why it should. Simply typing
unicode text gimp
into google will give you a different answer (which I haven't checked).


Cheers,
David.

Re: Unicode in GIMP Text Tool.

[peter]

*   From: deloptes 
*   Date: Wed, 14 Aug 2019 22:16:16 +0200
> what DE are you using?

LX

> I open the char selector (each desktop I know has one) and select the char
> to import - than copy/paste into the text box

Good idea.  Copy and paste the character; from the Web browser maybe.  
I was typing the character entity reference in the GIMP tool.

Thanks, ... P.

-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Arrow annotation in GIMP.

[David Wright]

On Wed 14 Aug 2019 at 07:24:58 (-0700), pe...@easthope.ca wrote:
> BEGIN TEDIOUS ASIDE
> For the header for this message I copied References holus-bolus and 
> appended the Message-id from the Web page. I understand David's 
> suggestion of including In-Repy-To rather than References but can 
> afford a few extra ms for References.  In-Reply-To is the last 
> parameter of References; therefore References contains all the 
> information that In-Reply-To does; therefore nothing is lost by 
> supplying References and not In-Reply-To.  We'll see how the header 
> for this message comes out.  =8~|
> 
> The case specificity of In-Reply-To rather than In-reply-to appears to 
> be unnecessary but that is what the IETF chose.  So the mailing list 
> software could stick to that. Putting In-reply-to on the Web pages is 
> just another source of distraction and confusion.

If you want to write iN-rePLy-to, go ahead. The web pages will massage
it into the same Capitalised style however you happen to write it; it
will perform its function just as well.

Many people on this list post emails containing In-reply-to, and that
*is* the commonest alternative to In-Reply-To, as might be expected.
https://lists.debian.org/debian-user/2015/03/msg00059.html
is the only instance of a saved email containing in-reply-to that I
happen to have a copy of, and you can see that the Debian web page
threaded it correctly.

Said email was emitted by the Atmail 6.6.0.13042 mailer, which google
seems to show is more frequently used in Australia. My email hosting
provider retired Atmail in favour of RoundCube back in 2014, or so I read.

> END TEDIOUS ASIDE

Cheers,
David.

Re: Unicode in GIMP Text Tool.

[deloptes]

pe...@easthope.ca wrote:

> Can GIMP accept and display a Unicode glyph beyond plain old ASCII.
> The "South West Arrow", & # 2199; for example.  (Spaces inserted
> after & and # to prevent interpretation.)
> 
> If so, how?
> 
> Thanks,  ... P.

I don't see a problem - what DE are you using? Did you check your locales?

I open the char selector (each desktop I know has one) and select the char
to import - than copy/paste into the text box

Unicode in GIMP Text Tool.

[peter]

Can GIMP accept and display a Unicode glyph beyond plain old ASCII.  
The "South West Arrow", & # 2199; for example.  (Spaces inserted 
after & and # to prevent interpretation.)

If so, how?

Thanks,  ... P.

-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Arrow annotation in GIMP.

[Tom Browder]

On Tue, Aug 13, 2019 at 20:51  wrote:

>
> Hi,
>
> Can anyone recommend a means for adding an arrow to
> an image in GIMP?
>
> The article here describes something called ArrowsCreator.
>
> https://graphicdesign.stackexchange.com/questions/44797/how-do-i-insert-arrows-into-a-picture-in-gimp
> Is it advisable?
>
> Any other recommendations?


If you're adventurous and want to be able to add more overlays to images
you could use ImageMagick and write a wrapper program to do exactly what
you wish. I have done so using Perl 6 (aka Raku) and plan to make it public
when I get the time.

Check out https://perl6.org for more info on the language.

Best regards,

-Tom

Re: Re (2): Arrow annotation in GIMP.

[Sven Hartge]

pe...@easthope.ca wrote:

> No References in the "header" of the Web page this replies to.
> Consequently I snagged the Messge-Id  (Message-id?) from the Web page
> for my original message.  Let's see how References comes out.  >8~|

Broken: 

References: <[?0;] E1hxhmC-0004v6-DR@dalton.invalid> <[?0;] 
20190814005429.5eea229a@northpole>

What is it with people seemingly trying to use this mailinglist in the
most difficult and error-prone way possible in the recent past?

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re (2): Arrow annotation in GIMP.

[peter]

BEGIN ANOTHER TEDIOUS ASIDE
No References in the "header" of the Web page this replies to.  
Consequently I snagged the Messge-Id  (Message-id?) from the Web page 
for my original message.  Let's see how References comes out.  >8~|
END ANOTHER TEDIOUS ASIDE

*   From: Cindy-Sue Causey 
*   Date: Wed, 14 Aug 2019 00:54:29 -0400
> Dingbats had ... various arrows.

I haven't found whether GIMP is Unicode capable. If ࢗ is typed 
at the insertion point for the Text tool, can the lower-left pointing 
arrow be displayed.  Hasn't succeeded here yet.

Thanks,  ... P.



-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Arrow annotation in GIMP.

[Eduardo M KALINOWSKI]

On qua, 14 ago 2019, peter wrote:

BEGIN TEDIOUS ASIDE
For the header for this message I copied References holus-bolus and
appended the Message-id from the Web page. I understand David's
suggestion of including In-Repy-To rather than References but can
afford a few extra ms for References.  In-Reply-To is the last
parameter of References; therefore References contains all the
information that In-Reply-To does; therefore nothing is lost by
supplying References and not In-Reply-To.  We'll see how the header
for this message comes out.  =8~|

The case specificity of In-Reply-To rather than In-reply-to appears to
be unnecessary but that is what the IETF chose.  So the mailing list
software could stick to that. Putting In-reply-to on the Web pages is
just another source of distraction and confusion.
END TEDIOUS ASIDE


Or you could use any modern MUA that does all that automatically and  
is not prone to errors.


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: Arrow annotation in GIMP.

[peter]

BEGIN TEDIOUS ASIDE
For the header for this message I copied References holus-bolus and 
appended the Message-id from the Web page. I understand David's 
suggestion of including In-Repy-To rather than References but can 
afford a few extra ms for References.  In-Reply-To is the last 
parameter of References; therefore References contains all the 
information that In-Reply-To does; therefore nothing is lost by 
supplying References and not In-Reply-To.  We'll see how the header 
for this message comes out.  =8~|

The case specificity of In-Reply-To rather than In-reply-to appears to 
be unnecessary but that is what the IETF chose.  So the mailing list 
software could stick to that. Putting In-reply-to on the Web pages is 
just another source of distraction and confusion.
END TEDIOUS ASIDE

*   From: Dan Ritter 
*   Date: Wed, 14 Aug 2019 08:26:18 -0400
> Open a new image. Set the background to transparent. Draw an
> arrow. Save it. Don't close it.
> 
> Open your primary image. ...

OK, thanks.  That method is entirely serviceable.

  ... P.
  
-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Arrow annotation in GIMP.

[Dan Ritter]

pe...@easthope.ca wrote: 
> 
> Hi, 
> 
> Can anyone recommend a means for adding an arrow to 
> an image in GIMP?
> 
> The article here describes something called ArrowsCreator.
> https://graphicdesign.stackexchange.com/questions/44797/how-do-i-insert-arrows-into-a-picture-in-gimp
> Is it advisable?
> 
> Any other recommendations?

Open a new image. Set the background to transparent. Draw an
arrow. Save it. Don't close it.

Open your primary image. Figure out where the arrow goes. Create
a new layer on top. Cut and paste the arrow into the primary
image. Move it around until you like it. Save. Export to the
format you want.

Next time you want an arrow, you've already got the same one, so
you can be consistent.

-dsr-

Re: Arrow annotation in GIMP.

[Cindy-Sue Causey]

On 8/13/19, pe...@easthope.ca  wrote:
> 
> Can anyone recommend a means for adding an arrow to 
> an image in GIMP?
> 
> The article here describes something called ArrowsCreator.
> https://graphicdesign.stackexchange.com/questions/44797/how-do-i-insert-arrows-into-a-picture-in-gimp
> Is it advisable?
> 
> Any other recommendations?


Hi, Peter.. I played with this a little bit and also installed a font
viewer which was already a to-do item. Gnome-font-viewer. Super simple.
It apparently opens up in the font directory.

Dingbats had a few various arrows. The file I found for it has Adobe's
name on it, adobe-dingbats, but I can't figure out when it's pulled
into my debootstraps. It should be from the main repository, most
likely.

If that Adobe name is a deal-breaker because of e.g. copyrights or
something, your webpage there reminded me that you can do a key
combination that lets you draw a PERFECT straight line.

I just tested it with the "pencil tool" and one of the acrylic
"brushes" for its tip. That gave it a "chalkboard chalk" outer edge.
The star brush gives you kind of a sawtooth look, by the way. :)

My sample came out well enough that I added it as my own brush, grin.
Their instructions worked just as written there. I'd forgotten we can
create our own brushes.

Mine's imperfectly shaped using that option of clicking the first
point, next click AND HOLD "shift" then click your second point... And
move-cursor-&-click and move-cursor-&-click until you get whatever shape
you want then release the shift key when you're finished.

If you do freehand but still want it symmetrical, you could draw the
first half, copy & paste a copy, flip that copy, and line it up to make
the whole arrow.

Have fun!

Cindy :)

PS My apologies if this reply warps anything. I'm replying through the
Lists webpage to see if that works properly on my end.

For one thing, I haven't seen a line count toggle anywhere (yet). It's
bringing up memories of a thread about that very topic from quite a
while back. :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Arrow annotation in GIMP.

[peter]

Hi, 

Can anyone recommend a means for adding an arrow to 
an image in GIMP?

The article here describes something called ArrowsCreator.
https://graphicdesign.stackexchange.com/questions/44797/how-do-i-insert-arrows-into-a-picture-in-gimp
Is it advisable?

Any other recommendations?

Thanks,   ... P.



-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: GIMP on Jessie causes total freeze

[Tomaž Šolc]

Hi

On 21. 05. 19 16:42, Дмитриев Александр wrote:
> I've encountered a problem with GIMP on Jessie. It causes total system
> freeze with latest available kernel, but not with the previous. This can
> be reproduced on at least 2 PCs.
> I've tried to file a bug via reportbug, but it returns error 500.
> What are my further steps?

Jessie is an obsolete stable release. I doubt you will find anyone
interested in fixing this bug.

Consider upgrading your PCs to Stretch.

3.16 series kernels are still supported upstream. Latest release is
3.16.67. If you're feeling up to it, you can also try running your
Jessie system with an upstream kernel and see if your issue was already
fixed.

https://wiki.debian.org/BuildingKernelFromUpstreamSources

If that is not an option, downgrade the kernel and be aware that you're
running an old kernel with known security problems.

You can find the previous kernel version in /var/log/dpkg.log. Then
either pull the .deb file from /var/cache/apt/archives or try to find it
if it still exists on Debian mirrors online.

Best regards
Tomaž



signature.asc
Description: OpenPGP digital signature

GIMP on Jessie causes total freeze

[Дмитриев Александр]

Hello, I've encountered a problem with GIMP on Jessie. It causes total system freeze with latest available kernel, but not with the previous. This can be reproduced on at least 2 PCs.I've tried to file a bug via reportbug, but it returns error 500.What are my further steps? uname -a:Linux debian 3.16.0-8-amd64 #1 SMP Debian 3.16.64-2 (2019-04-01) x86_64 GNU/Linuxgimp -v:GNU Image Manipulation Program version 2.8.14git-describe: GIMP_2_8_12-2-ge62e6fe  Alexander. -- С уважением,Дмитриев Александр 

Re: GIMP Crash

[Alexandre GRIVEAUX]

Le 17/03/2019 à 01:27, Adam Haas a écrit :
> I was working with the Gnu Image Manipulation Program yesterday when a
> segmentation fault occurred. Attached is the information spit out in
> association with the event. Please let me know what additional
> information you need from me and I will pass it along.
>
> - Adam Haas

Hello,


Can you send the content of your /etc/apt/sources.list ?


Thanks.

GIMP Crash

[Adam Haas]

I was working with the Gnu Image Manipulation Program yesterday when a
segmentation fault occurred. Attached is the information spit out in
association with the event. Please let me know what additional information
you need from me and I will pass it along.

- Adam Haas
```
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.14 (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:
```
/usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7efecef12e27]
gimp-2.10(+0xd14a0)[0x564d3eac34a0]
gimp-2.10(+0xd18d8)[0x564d3eac38d8]
gimp-2.10(+0xd2037)[0x564d3eac4037]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7efece20e730]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x179e4)[0x7efecee749e4]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(pango_attribute_copy+0xf)[0x7efecee742df]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(pango_attr_list_copy+0x28)[0x7efecee74c98]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x20697)[0x7efecee7d697]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x24143)[0x7efecee81143]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x26302)[0x7efecee83302]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x12802a)[0x7efecf15a02a]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x84a35)[0x7efecf0b6a35]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xf53bc)[0x7efecf1273bc]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x84a35)[0x7efecf0b6a35]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1a52d2)[0x7efecf1d72d2]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8]
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x84a35)[0x7efec

Re: (OT) Top Posting (was Re: Gimp Babl too old)

[Ben Finney]

Kenneth Parker  writes:

> I have a special issue:  Using Gmail on a Phone or Tablet (I have
> both).

Both of those devices lack a proper keyboard. That makes them unsuitable
for composing anything but very short messages, and wholly unsuitable
for editing text.

> Seriously, how do others of you deal with navigating this Debian List
> on Android, while being a "Good Netizen"?

I deal with it by never composing or editing messages without a proper
keyboard.

Handheld, full-touchscreen devices are fine as reading devices, and
maybe for very limited gross-control input, but it's a mistake to try to
use them as text editing devices until you connect a real keyboard.

-- 
 \ “I know you believe you understood what you think I said, but I |
  `\ am not sure you realize that what you heard is not what I |
_o__) meant.” —Robert J. McCloskey |
Ben Finney

Re: Is GIMP seriously broken in Buster?

[A_Man_Without_Clue]

On 09/14/2018 07:52 AM, Gary Dale wrote:
> Am I missing something or is GIMP seriously broken? In my Buster/AMD64
> system, I open a picture, select a section and try to cut it and the
> whole picture disappears. I'm left with a white or transparent
> background. If I select a region and try to copy it, GIMP crashes.
> 
> I'm reduced to using KolourPaint for the urgent editing work I'm trying
> to do.
> 


I am running Buster and got problem with GIMP after recent update as well.
I get this message

"BABL version too old!

GIMP requires BABL version 0.1.56 or later.
Installed BABL version is 0.1.46.

Somehow you or your software packager managed
to install GIMP with an older BABL version.

Please upgrade to BABL version 0.1.56 or later."


Man with new problem now

Re: Is GIMP seriously broken in Buster?

[songbird]

Gary Dale wrote:

> Am I missing something or is GIMP seriously broken? In my Buster/AMD64 
> system, I open a picture, select a section and try to cut it and the 
> whole picture disappears. I'm left with a white or transparent 
> background. If I select a region and try to copy it, GIMP crashes.

  no problems for me, what desktop are you using?

  i made sure my current versions were updated and
i did the operations you've cited...


> I'm reduced to using KolourPaint for the urgent editing work I'm trying 
> to do.

  why do you use Buster if you have urgent editing work?

  testing should not be used for production work, or at
least if you are expecting such needs make sure it works
before you get in a jam.

  i always keep a stable bootable partition for such
things.


  songbird

Re: (OT) Top Posting (was Re: Gimp Babl too old)

[Anders Andersson]

On Fri, Sep 14, 2018 at 6:17 AM, Kenneth Parker  wrote:
> Seriously, how do others of you deal with navigating this Debian List on
> Android, while being a "Good Netizen"?

Personally I don't. A phone is a horrible tool for composing texts and
is nowhere near a replacement for a computer. Using an inferior tool
is no excuse to inconvenience others. My pet peeve here is when people
try to use the Stack Exchange app or whatever, and excuse the lousy
formatting on "I'm on the phone", but thanks for pointing out another
one: gmail top posting! It's bad enough in an an actual browser on a
real computer...

I loathe the "appification" of everything these days, dumbing down
everything to the lowest lousiest common denominator for people who
can only point and click with their thumbs.

(I was about to write  but I will never stop ranting about this!)

Re: Is GIMP seriously broken in Buster?

[Joe]

On Fri, 14 Sep 2018 06:27:34 +0100
Brad Rogers  wrote:

> On Thu, 13 Sep 2018 18:52:45 -0400
> Gary Dale  wrote:
> 
> Hello Gary,
> 
> >Am I missing something or is GIMP seriously broken? In my
> >Buster/AMD64   
> 
> Works fine here.  Admittedly, it's not a package I use often, but even
> so, I've never seen the behaviour you're experiencing.
> 

When in doubt, blame GTK. I have (in sid) had what are almost certainly 
GTK problems that seem to have affected just one application at a time
and been unique to me.

-- 
Joe

Re: Is GIMP seriously broken in Buster?

[Brad Rogers]

On Thu, 13 Sep 2018 18:52:45 -0400
Gary Dale  wrote:

Hello Gary,

>Am I missing something or is GIMP seriously broken? In my Buster/AMD64 

Works fine here.  Admittedly, it's not a package I use often, but even
so, I've never seen the behaviour you're experiencing.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
No you can't hop into my shower
Leave Me Alone (I'm Lonely) - P!nk


pgpwgfKkIIosU.pgp
Description: OpenPGP digital signature

(OT) Top Posting (was Re: Gimp Babl too old)

[Kenneth Parker]

On Thu, Sep 13, 2018 at 10:07 PM Ric Moore  wrote:

>
> 
>


> Same reason some people top post. They just ignore the conventions.
>

I have a special issue:  Using Gmail on a Phone or Tablet (I have both).  I
have yet to find a Straightforward way to Snip lots of lines, using the
Android App.  Also, Gmail "hides" the lines from the prior responses in the
Thread, making it  *WAY*  too easy to Top Post. (You have to touch a link
to see them).

So, since I "feel your Pain", I generally save my Debian Responses for,
when I get home with, either my Debian 9 Laptop, my Ubuntu 16.04 Laptop (to
be upgraded to Debian 9 in the next month), or the Chromebook I am typing
on now.

Seriously, how do others of you deal with navigating this Debian List on
Android, while being a "Good Netizen"?

Thank you and best regards,

Kenneth Parker, Computer Consultant

Re: Is GIMP seriously broken in Buster?

[Gary Dale]

On 2018-09-13 08:44 PM, Matthew Crews wrote:
Try the Flatpak version of GIMP. 


I'm not a fan of the attempts to create universal packages. The problem 
they create is that you have multiple different versions of the same 
libraries and you're now relying on multiple people to patch security 
holes and bugs in all the different versions.


One of Debian's strengths is that all the programs (eventually) work 
together perfectly. I'll put up with bugs that sometimes creep into the 
testing versions because I know that they get sorted out and the final 
stable product is very stable and secure.


I do admit that I've seen more, and more serious, bugs in this testing 
release than in previous ones. However I also note that there have been 
some amazing changes right the way through so you have to expect that 
things will break.


I think the GIMP problems may already be fixed. After tonight's upgrades 
it seems to be working a lot better.

Re: Gimp Babl too old

[Ric Moore]

On 09/13/2018 12:41 PM, Nicholas Geovanis wrote:

Tixy wrote: "Sounds like the sort of thing the third party repository at
deb-multimedia.org does"

Why do they do that? Simply to order their repository ahead of the others?


Same reason some people top post. They just ignore the conventions.


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Is GIMP seriously broken in Buster?

[Cindy-Sue Causey]

On 9/13/18, Gary Dale  wrote:
> Am I missing something or is GIMP seriously broken? In my Buster/AMD64
> system, I open a picture, select a section and try to cut it and the
> whole picture disappears. I'm left with a white or transparent
> background. If I select a region and try to copy it, GIMP crashes.
>
> I'm reduced to using KolourPaint for the urgent editing work I'm trying
> to do.


I'm sorry, I don't have an immediate answer, but I do feel your pain.
Seriously firsthand empathy when sound goes missing for video editing.
:)

Am writing to suggest trying to run it from a terminal window to see
if that helps at least give you some error messages to work with. It's
fresh in mind because I did that earlier with Thunar file manager just
to run as root user. Ended up accidentally uncovering some (missing)
flash related whoopsies I had caused to occur. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Is GIMP seriously broken in Buster?

[Matthew Crews]

Try the Flatpak version of GIMP.

Is GIMP seriously broken in Buster?

[Gary Dale]

Am I missing something or is GIMP seriously broken? In my Buster/AMD64 
system, I open a picture, select a section and try to cut it and the 
whole picture disappears. I'm left with a white or transparent 
background. If I select a region and try to copy it, GIMP crashes.


I'm reduced to using KolourPaint for the urgent editing work I'm trying 
to do.

Re: Gimp Babl too old

[Brad Rogers]

On Thu, 13 Sep 2018 13:32:57 -0400
Dan Ritter  wrote:

Hello Dan,

>Basically, people who use deb-multimedia.org want someone to package up
>fresh versions of the kinds of tools that get updated frequently with
>new features, while mostly maintaining the stability that comes with

It's not that simple.  DMO also includes stuff that Debian won't due to
licensing conflicts with DFSG.  DMO doesn't have the same criteria as
DFSG, so can include things Debian won't.  Acroread and flashplayer,
for example.

There is also similar treatment of software that isn't entirely legal in
certain jurisdictions.  For example, libdvdcss.

The reason DMO places a higher than Debian epoch on software versions is
to avoid the need to set up pinning to prefer DMO over Debian.  Of
course, this can have unfortunate consequences.  Especially if a user
decides to remove DMO as a repo.  The consequences aren't
insurmountable, but one does need to be careful dealing with the changes
from having DMO included in sources.list to a sources.list w/o DMO in it.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Every single one of us
Devil Inside - INXS


pgp_7jyHmXn29.pgp
Description: OpenPGP digital signature

Re: Gimp Babl too old

[Dan Ritter]

On Thu, Sep 13, 2018 at 11:41:39AM -0500, Nicholas Geovanis wrote:
> Tixy wrote: "Sounds like the sort of thing the third party repository at
> deb-multimedia.org does"
> 
> Why do they do that? Simply to order their repository ahead of the others?
> So why not just advise people to change sources.list? It seems like they don't
> themselves make a statement on the subject.

Basically, people who use deb-multimedia.org want someone to package up
fresh versions of the kinds of tools that get updated frequently with
new features, while mostly maintaining the stability that comes with
running Debian Stable.

So deb-multimedia.org has audio and video editors, players, MythTV,
encoders, decoders, transmogrifiers, and so forth.

It's a little like backports, but outside of the Debian organization
and not necessarily adhering to Debian rules.

Conflicts are inevitable, but mostly minor, like what we have
in this example. It's not like they're packaging new glibc or
xorg, where a thousand packages can scream in agony.

-dsr-

Re: Gimp Babl too old

[Nicholas Geovanis]

Tixy wrote: "Sounds like the sort of thing the third party repository at
deb-multimedia.org does"

Why do they do that? Simply to order their repository ahead of the others?
So why not just advise people to change sources.list? It seems like they don't
themselves make a statement on the subject.
On Thu, Sep 13, 2018 at 1:03 AM Tixy  wrote:
>
> On Wed, 2018-09-12 at 19:54 +0200, Étienne Mollier wrote:
> > At first, it sounded like the last `apt update` execution
> > occurred some time between “libbabl-dev” and “libbabl-0.1-0”
> > upgrade to version 0.1.56-1 on repositories side.
> >
> > But “libbabl-0.1-0” seems somehow picked from another
> > repository, the version convention “1:0.1.44-dmo1” looks like it
> > is designed to supersede Debian's initial package on purpose.
>
> Sounds like the sort of thing the third party repository at
> deb-multimedia.org does, and the 'dmo1' in the package name is a big
> clue that is the case here. Basically, every time a version of a
> library in deb-multimedia falls behind Debian you're likely to get some
> kind of breakage, because it has used the epoch number to fake up this
> 'I'm a higher version so install me instead of the of official Debian
> library'.
>
> If the OP is running Sid with deb-multimedia then this sort of thing is
> going to be a reoccurring problem.
>
> --
> Tixy
>

Re: Gimp Babl too old

[Pétùr]

On 13/09/18 07:03, Tixy wrote:

On Wed, 2018-09-12 at 19:54 +0200, Étienne Mollier wrote:

At first, it sounded like the last `apt update` execution
occurred some time between “libbabl-dev” and “libbabl-0.1-0”
upgrade to version 0.1.56-1 on repositories side.

But “libbabl-0.1-0” seems somehow picked from another
repository, the version convention “1:0.1.44-dmo1” looks like it
is designed to supersede Debian's initial package on purpose.


Sounds like the sort of thing the third party repository at
deb-multimedia.org does, and the 'dmo1' in the package name is a big
clue that is the case here. Basically, every time a version of a
library in deb-multimedia falls behind Debian you're likely to get some
kind of breakage, because it has used the epoch number to fake up this
'I'm a higher version so install me instead of the of official Debian
library'.

If the OP is running Sid with deb-multimedia then this sort of thing is
going to be a reoccurring problem.



Thnaks for the explanatio. I was indeed using deb-multimedia.org
repository a while ago.

Mystery solved!

Re: Gimp Babl too old

[Tixy]

On Wed, 2018-09-12 at 19:54 +0200, Étienne Mollier wrote:
> At first, it sounded like the last `apt update` execution
> occurred some time between “libbabl-dev” and “libbabl-0.1-0”
> upgrade to version 0.1.56-1 on repositories side.
> 
> But “libbabl-0.1-0” seems somehow picked from another
> repository, the version convention “1:0.1.44-dmo1” looks like it
> is designed to supersede Debian's initial package on purpose.

Sounds like the sort of thing the third party repository at
deb-multimedia.org does, and the 'dmo1' in the package name is a big
clue that is the case here. Basically, every time a version of a
library in deb-multimedia falls behind Debian you're likely to get some
kind of breakage, because it has used the epoch number to fake up this
'I'm a higher version so install me instead of the of official Debian
library'.

If the OP is running Sid with deb-multimedia then this sort of thing is
going to be a reoccurring problem.

-- 
Tixy

Re: Gimp Babl too old

[Étienne Mollier]

Bonjour Pétùr,

On 9/12/18 10:40 AM, Pétùr wrote:
> I can only find the 0.1-0 version:

Don't let yourself be fooled by the version number in the
package name (the part before the “/now”), and the real package
version number (the part between the “/now” and “amd64”).  It is
a way to have various versions of a same software installed on
your system.

> $ apt search libbabl
> En train de trier... Fait
> Recherche en texte intégral... Fait
> libbabl-0.1-0/now 1:0.1.44-dmo1 amd64  [installé, local]
>   Dynamic, any to any, pixel format conversion library
>
> libbabl-0.1-0-dbg/stable 0.1.18-1 amd64
>   bibliothèque dynamique de conversion de tous types de
>   formats de pixels –⋅symboles de débogage
>
> libbabl-dev/unstable,testing 0.1.56-1 amd64
>   bibliothèque dynamique de conversion de tous types de
>   formats de pixels –⋅fichiers de développement
>
> libbabl-doc/unstable,testing 0.1.56-1 all
>   bibliothèque dynamique de conversion de tous types de
>   formats de pixels –⋅documentation

At first, it sounded like the last `apt update` execution
occurred some time between “libbabl-dev” and “libbabl-0.1-0”
upgrade to version 0.1.56-1 on repositories side.

But “libbabl-0.1-0” seems somehow picked from another
repository, the version convention “1:0.1.44-dmo1” looks like it
is designed to supersede Debian's initial package on purpose.

If there are no more third party repository in your sources.list
files, you may be able to get the proper version by enforcing it
at installation:

# apt install libbabl-0.1-0=0.1.56-1

A warning may ask you if you are certain you wish to downgrade.
Once done, you *may* be able to make use of Gimp.

Please be aware that there are quite some chances other packages
have been affected by similar quirks, if you have installed a
few of them from third party repositories.

I hope this helps anyway,
Bien à vous,
-- 
Étienne Mollier 

Re: Gimp Babl too old

[Pétùr]

Le 11/09/2018 à 20:09, Dan Ritter a écrit :
> 
> and a check says that sid now has a version 0.1.56 of babl, so
> you should try installing that.

Hi,

I can only find the 0.1-0 version:


$ apt search libbabl
En train de trier... Fait
Recherche en texte intégral... Fait
libbabl-0.1-0/now 1:0.1.44-dmo1 amd64  [installé, local]
  Dynamic, any to any, pixel format conversion library

libbabl-0.1-0-dbg/stable 0.1.18-1 amd64
  bibliothèque dynamique de conversion de tous types de formats de
pixels –⋅symboles de débogage

libbabl-dev/unstable,testing 0.1.56-1 amd64
  bibliothèque dynamique de conversion de tous types de formats de
pixels –⋅fichiers de développement

libbabl-doc/unstable,testing 0.1.56-1 all
  bibliothèque dynamique de conversion de tous types de formats de
pixels –⋅documentation

Re: Gimp Babl too old

[Dan Ritter]

On Tue, Sep 11, 2018 at 07:12:19PM +0200, Pétùr wrote:
> Gimp does not start on debian sid and shows the message:
> 
> ---
> BABL version too old!
> 
> GIMP requires BABL version 0.1.56 or later.
> Installed BABL version is 0.1.44.
> 
> Somehow you or your software packager managed
> to install GIMP with an older BABL version.
> 
> Please upgrade to BABL version 0.1.56 or later.
> ---
> 
> How to fix it? I tried purge and reinstall, installing gegl.

As with all package questions about sid, the primary answer is
"have you checked with the packaging team?"

http://metadata.ftp-master.debian.org/changelogs//main/g/gimp/gimp_2.10.6-3_changelog

says:


gimp (2.10.6-3) unstable; urgency=medium

  * Add X-Ubuntu-Use-Langpack to opt in to Ubuntu language pack
  * handling
(LP: #1779574)
  * Bump Standards-Version to 4.2.1

 -- Jeremy Bicha   Tue, 04 Sep 2018 15:08:42
-0400

gimp (2.10.6-2) unstable; urgency=medium

  * debian/gimp.install: Remove extra line which caused file
  * conflict
(Closes: #906892)

 -- Jeremy Bicha   Tue, 21 Aug 2018 17:47:28
-0400

gimp (2.10.6-1) unstable; urgency=medium

  * New upstream release (Closes: #900819)
  * debian/libgimp2.0.symbols: Add new symbols
  * Bump minimum babl to 0.1.56 and gegl to 0.4.8
  * debian/gimp.install: Install gimp-test-clipboard
  * Update install files now that gimp add-ons are installed in
  * subdirectories

 -- Jeremy Bicha   Tue, 21 Aug 2018 13:42:06
-0400


and a check says that sid now has a version 0.1.56 of babl, so
you should try installing that.

-dsr-

Gimp Babl too old

[Pétùr]

Gimp does not start on debian sid and shows the message:

---
BABL version too old!

GIMP requires BABL version 0.1.56 or later.
Installed BABL version is 0.1.44.

Somehow you or your software packager managed
to install GIMP with an older BABL version.

Please upgrade to BABL version 0.1.56 or later.
---

How to fix it? I tried purge and reinstall, installing gegl.

Pétùr

Re: Sane via GIMP.

[Matthew Crews]

On 7/17/18 9:35 AM, pe...@easthope.ca wrote:
> Just updated this debian 9 and tried gimp > file > create > XSane > Device 
> dialogue.
> There chose the HP scanner.
> 
> A window entitled "xsane 0.999 C2500A:sg0" opened. There I selected 
> Window > Show preview.  (Previously, for years, the preview window 
> opened automatically.)  The result is at 
> http://easthope.ca/SanePreview.png 
> Ie. previewing and scanning appears to be impossible.
> 

Since you just upgraded to Stretch, have you verified that your HP
scanner drivers are using the most-recent version available? Perhaps you
should rerun "hp-setup" and reconfigure your scanner, and see if that helps.

-Matt

Sane via GIMP.

[peter]

Just updated this debian 9 and tried gimp > file > create > XSane > Device 
dialogue.
There chose the HP scanner.

A window entitled "xsane 0.999 C2500A:sg0" opened. There I selected 
Window > Show preview.  (Previously, for years, the preview window 
opened automatically.)  The result is at 
http://easthope.ca/SanePreview.png 
Ie. previewing and scanning appears to be impossible.

Ideas?

Thanks,  ... Peter E.


-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re: Gimp broken in Debian Sid?

[Thierry Rascle]

On Sun, 8 Jul 2018 10:37:10 +1200
Ben Caradoc-Davies  wrote:

> I would use ltrace to see where it is hanging:
> 
> ltrace -tt -n4 -S gimp
> 
> You will need to install ltrace and likely the debug packages for 
> wherever it is hanging.

ltrace -tt -n4 -S /usr/bin/gimp outputs a lot lines and the last one is
like:

10:01:04.820439 SYS_futex(0x7f8d0648a9d0, 0, 6356, 0

strace -f /usr/bin/gimp also outputs a lot lines and the last ones are
like:

[pid  6789] futex(0x7f1d25b6b9d0, FUTEX_WAIT, 6791, NULL 
[pid  6791] futex(0x7f1d3d401968, FUTEX_WAIT_PRIVATE, 2, NULL

'ps aux' tells me that one of the pid is gimp, and the other one is not
existing. So it could be that Gimp is just waiting for a dead process.
I don't know how to identify this dead process.

I looked for a way to force Gimp to run on a single thread and Google
pointed me to this URL:

https://superuser.com/questions/692138/how-to-force-a-process-to-run-on-a-single-thread-only-with-numactl

So I tried:

numactl --physcpubind=+1 /usr/bin/gimp

and Gimp works :-)

Of course I still don't know what the root cause of the problem is...

Many many thanks for your help and suggestions :-)

-- 
Thierry

Re: Gimp broken in Debian Sid?

[Thierry Rascle]

On Sat, 7 Jul 2018 18:04:31 +0200
Thierry Rascle  wrote:


> I've tried purging Gimp and some dependencies, and then reinstalling
> Gimp but it still doesn't work:
> 
>     apt-get purge ufraw gimp gimp-data gimp-ufraw libgimp2.0 \
> libgimp2.0-dev libgimp2.0-doc
> 
> apt-get autoremove
> 
> apt-get install gimp

I've done this purge / autoremove / install sequence again, adding a
purge of the configuration files of absolutely all uninstalled packages
on my system after the autoremove, without success.

> 
> I have two Debian sid installations: One main installation (on my
> internal hard drive) and a secondary installation (on an external USB
> hard drive). I dist-upgrade those two installations almost
> simultaneously, approximately once a week. So they're like twins. I
> don't use Gimp regularly on the secondary installation but I've
> verified: it's also affected by the problem.
> 
> I will probably end up doing a system reinstall on the external
> hard drive and see what happens.

I've done a fresh install of Debian stable + dist-upgrade to Sid on my
external hard drive and Gimp works on this installation.


-- 
Thierry

Re: Gimp broken in Debian Sid?

[Ben Caradoc-Davies]

On 08/07/18 03:36, Thierry Rascle wrote:

After removing ~/.config/GIMP/2.10, Gimp still doesn't work. And
there's no message on the command line, even when using the --verbose
option.


I would use ltrace to see where it is hanging:

ltrace -tt -n4 -S gimp

You will need to install ltrace and likely the debug packages for 
wherever it is hanging.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited <https://transient.nz/>
New Zealand

Re: Gimp broken in Debian Sid?

[Thierry Rascle]

On Fri, 6 Jul 2018 18:44:20 -0400
Cindy-Sue Causey  wrote:


> 
> With respect to dealing with that ghost, I have two things I do in
> these kinds of instances. The first one I do is kill that ghost
> instance then relaunch the problem program from within a terminal
> window. Sometimes you get lucky and see a bunch of error messages that
> can possibly help solve the problem.

Even after killing the instance or after rebooting, Gimp still doesn't
work. No error message on the command line.

> 
> The second thing I do... out of exasperation... is purge the problem
> program THEN secondarily ALSO PURGE all the various dependency
> packages. Apt-get is very neighborly about presenting that dependency
> list when a user is trying to upgrade or install just after having
> purged a primary package.

I've tried purging Gimp and some dependencies, and then reinstalling
Gimp but it still doesn't work:

apt-get purge ufraw gimp gimp-data gimp-ufraw libgimp2.0 \
libgimp2.0-dev libgimp2.0-doc

apt-get autoremove

apt-get install gimp

I have two Debian sid installations: One main installation (on my
internal hard drive) and a secondary installation (on an external USB
hard drive). I dist-upgrade those two installations almost
simultaneously, approximately once a week. So they're like twins. I
don't use Gimp regularly on the secondary installation but I've
verified: it's also affected by the problem.

I will probably end up doing a system reinstall on the external
hard drive and see what happens.

Thank you all anyway for your help!

-- 
Thierry

Re: Gimp broken in Debian Sid?

[Thierry Rascle]

On Sat, 7 Jul 2018 14:33:37 +1200
Ben Caradoc-Davies  wrote:

> On 07/07/18 08:13, Michael Wagner wrote:
>  [...]  
>  [...]  
>  [...]  
> 
> Same working for me under Xfce.
> 
> There have been a bunch of styling changes in 2.10.
> 
> Thierry, what desktop theme are you using? You could try moving your 
> ~/.config/GIMP/2.10 out of the way in case it has fallen down and
> cannot get up.
> 
> Do you get any error messages if you start gimp at the command line?
> 
> Kind regards,
> 

After removing ~/.config/GIMP/2.10, Gimp still doesn't work. And
there's no message on the command line, even when using the --verbose
option.

-- 
Thierry

Re: Gimp broken in Debian Sid?

[Ben Caradoc-Davies]

On 07/07/18 08:13, Michael Wagner wrote:

On Jul 06, 2018 um 07:58:41, Thierry Rascle wrote:

I'm using Debian Sid. Gimp does not seem to work any more (the user
interface does not show up). I've tried in Xmonad and in Openbox.
I have no idea what causes this. I don't see any error message.
Does anyone else have the same problem ?

Hello Thierry,
I'm using Debian Testing with gimp 2.10.2-1 from unstable and it works.
Michael


Same working for me under Xfce.

There have been a bunch of styling changes in 2.10.

Thierry, what desktop theme are you using? You could try moving your 
~/.config/GIMP/2.10 out of the way in case it has fallen down and cannot 
get up.


Do you get any error messages if you start gimp at the command line?

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited <https://transient.nz/>
New Zealand

Re: Gimp broken in Debian Sid?

[Cindy-Sue Causey]

On 7/6/18, Thierry Rascle  wrote:
> On Fri, 6 Jul 2018 07:33:16 +0100
> Joe  wrote:
>
>> On Fri, 6 Jul 2018 07:58:41 +0200
>> Thierry Rascle  wrote:
>>
>> > Hi,
>> >
>> > I'm using Debian Sid. Gimp does not seem to work any more (the user
>> > interface does not show up). I've tried in Xmonad and in Openbox.
>> >
>> > I have no idea what causes this. I don't see any error message.
>> >
>> > Does anyone else have the same problem ?
>> >
>> > Thanks!
>> >
>> > Thierry
>> >
>>
>> No. 2.10 behaves differently, and I find the toolbox much harder to
>> use, as I only use GIMP occasionally, but it's working. My sid is up
>> to date, but of course will be very different from your sid.
>>
>
> Yes, I noticed that the toolbox has changed with 2.10 two months ago.
> There was also a new issue with the gimp-ufraw plugin, forcing the user
> to use the standalone ufraw application instead. But Gimp was usable.
>
> Now it is totally unusable for me. A 'ps -ef' shows a gimp process
> running but I don't see any windows in any workspace. A 'xwininfo -tree
> -root' does not list any Gimp windows. Launching Gimp from a terminal
> does not give any error message.


A half-baked memory is coming back about Thunar giving me ghost
instances in unstable or Sid, I don't remember which..

I can't quite remember, but it was something about Thunar wasn't being
properly shut down when I rebooted. Yeah, I know, I don't know if
Thunar was still open when I rebooted or if it wasn't completely
shutting down and then the reboot still didn't finish the shut down
process on top of that.

I think I learned that because Thunar wasn't coming coming up for me
in a similar way as is being described here about GIMP. However it was
happening is why there was a "ghost" lingering in the background *for
me*. I never got around to reporting a bug, and it eventually resolved
itself via some one or another upgrades back then (maybe a couple
years ago?).

With respect to dealing with that ghost, I have two things I do in
these kinds of instances. The first one I do is kill that ghost
instance then relaunch the problem program from within a terminal
window. Sometimes you get lucky and see a bunch of error messages that
can possibly help solve the problem.

The second thing I do... out of exasperation... is purge the problem
program THEN secondarily ALSO PURGE all the various dependency
packages. Apt-get is very neighborly about presenting that dependency
list when a user is trying to upgrade or install just after having
purged a primary package.

There's also a remove option instead of purge that may be more
appropriate. I just like the sound of *PURGE IT!* and have never had
any problems going that route. :)

The reason I purge instead of "install --reinstall" is because
"install --reinstall" *ONLY* reinstalls the specifically named
package, i.e. *no dependencies*. There may be an option that triggers
the reinstallation of dependencies, too, but I've never encountered it
(yet).

I just went into "man apt-get" for a second. That reminded me that
users sometimes have good luck simply deleting existing config files
and NOT the whole program.

Those config files are the kind found in our /home directories unless
we've defined them to set up some place else. They're sometimes
(often?) only visible if we toggle CTRL+H on and off in our favorite
file managers.

If that seems like a friendly option, I'd make a backup copy of the
files I intend to delete just in case that doesn't work/turns out to
be a wasted effort. Moving those out of the way while simultaneously
making a backup is as simple as renaming the file or entire folder. We
can call them anything we want, but I tend to like to rename mine with
the date last used as a point of reference.

One of the things I've learned while deliberately pushing my copies to
the limit here is that there can be upgrade/downgrade(/crossgrade)
incompatibility problems with those config files. I learned that while
working through problems with the Opera-Beta browser.

Once the config file(s) became "contaminated" with new features while
older features started falling by the wayside, that's when I first
started seeing the problems AND then tied OTHER problems to how config
files MIGHT cause our programs' success and failures over a very
extended period of time...

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Gimp broken in Debian Sid?

[Thierry Rascle]

On Fri, 6 Jul 2018 07:33:16 +0100
Joe  wrote:

> On Fri, 6 Jul 2018 07:58:41 +0200
> Thierry Rascle  wrote:
> 
> > Hi,
> > 
> > I'm using Debian Sid. Gimp does not seem to work any more (the user
> > interface does not show up). I've tried in Xmonad and in Openbox.
> > 
> > I have no idea what causes this. I don't see any error message.
> > 
> > Does anyone else have the same problem ?
> > 
> > Thanks!
> > 
> > Thierry
> >   
> 
> No. 2.10 behaves differently, and I find the toolbox much harder to
> use, as I only use GIMP occasionally, but it's working. My sid is up
> to date, but of course will be very different from your sid.
> 

Yes, I noticed that the toolbox has changed with 2.10 two months ago.
There was also a new issue with the gimp-ufraw plugin, forcing the user
to use the standalone ufraw application instead. But Gimp was usable.

Now it is totally unusable for me. A 'ps -ef' shows a gimp process
running but I don't see any windows in any workspace. A 'xwininfo -tree
-root' does not list any Gimp windows. Launching Gimp from a terminal
does not give any error message.

-- 
Thierry

Re: Gimp broken in Debian Sid?

[Michael Wagner]

On Jul 06, 2018 um 07:58:41, Thierry Rascle wrote:
> I'm using Debian Sid. Gimp does not seem to work any more (the user
> interface does not show up). I've tried in Xmonad and in Openbox.
> 
> I have no idea what causes this. I don't see any error message.
> 
> Does anyone else have the same problem ?
> 
Hello Thierry,

I'm using Debian Testing with gimp 2.10.2-1 from unstable and it works.

Michael


signature.asc
Description: PGP signature

Re: Gimp broken in Debian Sid?

[Joe]

On Fri, 6 Jul 2018 07:58:41 +0200
Thierry Rascle  wrote:

> Hi,
> 
> I'm using Debian Sid. Gimp does not seem to work any more (the user
> interface does not show up). I've tried in Xmonad and in Openbox.
> 
> I have no idea what causes this. I don't see any error message.
> 
> Does anyone else have the same problem ?
> 
> Thanks!
> 
> Thierry
> 

No. 2.10 behaves differently, and I find the toolbox much harder to
use, as I only use GIMP occasionally, but it's working. My sid is up to
date, but of course will be very different from your sid.

-- 
Joe

Gimp broken in Debian Sid?

[Thierry Rascle]

Hi,

I'm using Debian Sid. Gimp does not seem to work any more (the user
interface does not show up). I've tried in Xmonad and in Openbox.

I have no idea what causes this. I don't see any error message.

Does anyone else have the same problem ?

Thanks!

Thierry

Re: Installing Gimp 2.10.2

[steve]

Le mardi 05 juin 2018, HP Garcia a écrit :


On Wed, 6 Jun 2018 06:51:36 +0200
steve  wrote:


Le 05-06-2018, à 21:45:24 -0700, HP Garcia a écrit :

>I'm trying to install Gimp 2.10.2. I tried adding the flatpack
>repository but it message "sudo: add-apt-repository: command not
>found"

Have you the software-properties-common package installed?

If not install it then relaunch your command.



I installed the software-properties-common package and reran the
command.

I got this message this time "gpg: keyserver receive failed: No dirmngr"


sudo apt-get install dirmngr

should help  ;)

Re: Installing Gimp 2.10.2

[steve]

Le mardi 05 juin 2018, HP Garcia a écrit :


>I'm trying to install Gimp 2.10.2. I tried adding the flatpack
>repository but it message "sudo: add-apt-repository: command not
>found"

Have you the software-properties-common package installed?

If not install it then relaunch your command.



No, I didn't know I needed that.


That command belongs to that package. "command not found" is pretty
explicite.