Testing 1.3.20
This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
| Testing 1.3.20 | BandiPat | 10 Sep 00:04 |
| Testing 1.3.20 | Sven Neumann | 10 Sep 00:23 |
| Testing 1.3.20 | BandiPat | 10 Sep 01:03 |
| Testing 1.3.20 | Sven Neumann | 10 Sep 02:28 |
| Testing 1.3.20 (SOLVED) | BandiPat | 10 Sep 02:48 |
| Testing 1.3.20 | Tom Williams | 10 Sep 05:45 |
| Testing 1.3.20 | David Neary | 10 Sep 10:34 |
| Testing 1.3.20 | Tom Williams | 10 Sep 16:05 |
Testing 1.3.20
Hi all,
The new Gimp compiled fine today and installed. Upon trying to run it though, it got to a load point and just died. I ran it from the shell to check for more messages and found it doing a Segmentation fault
This is a development version of the GIMP Debug messages may appear here.
Testing CPU features...
mmx : yes
3dnow : yes
mmxext : yes
sse : yes
sse2 : no
gimp_composite: use=yes, verbose=no +mmx +sse +3dnow gimp: fatal error: Segmentation fault gimp (pid:8324): [E]xit, [H]alt, show [S]tack trace or [P]roceed:
So I then ask it to Stack trace, which gave me this:
#0 0x404b5010 in g_on_error_stack_trace () from
/usr/lib/libglib-2.0.so.0
#1 0x00000001 in ?? ()
#2 0x404b4f8d in g_on_error_query () from /usr/lib/libglib-2.0.so.0
#3 0x0807f132 in gimp_eek (reason=0x81f3720 "fatal error",
#4 0x0807f083 in gimp_fatal_error (fmt=0x85af338 "Segmentation fault")
#5
#6 0x4052482a in FcTestDestroy () from
/usr/X11R6/lib/libfontconfig.so.1
#7 0x405175dd in FcSubstDestroy () from
/usr/X11R6/lib/libfontconfig.so.1
#8 0x40517659 in FcConfigDestroy () from
/usr/X11R6/lib/libfontconfig.so.1
#9 0x4051783c in FcConfigSetCurrent () from
/usr/X11R6/lib/libfontconfig.so.1
#10 0x081c4f21 in gimp_fonts_load (gimp=0x40532674) at gimpfonts.c:98
#11 0x081c4d90 in gimp_fonts_init (gimp=0x82c3ac0) at gimpfonts.c:55
#12 0x081467f0 in gimp_restore (gimp=0x82c3ac0,
#13 0x0807dd9d in app_init (gimp_argc=0, gimp_argv=0xbffff3c8,
#14 0x0807e4c8 in main (argc=1, argv=0xbffff3c4) at main.c:380
#15 0x4059e8ae in __libc_start_main () from /lib/libc.so.6
--------------------------------
Not sure from the info given above that it's a font problem or X problem, but I'm guessing font loading due to the many references to fonts. Guess I'll go back to 1.3.19 for a while. What are others results? One thing I might mention too, is the recent installation of a new graphics card. ATI Radeon 9200 installed and using the ATI drivers (fglrx). I don't think that has any bearings on this problem as the 1.3.19 works fine.
Patrick
Testing 1.3.20
Hi,
BandiPat writes:
The new Gimp compiled fine today and installed. Upon trying to run it though, it got to a load point and just died. I ran it from the shell to check for more messages and found it doing a Segmentation fault
See http://bugzilla.gnome.org/show_bug.cgi?id=121752
Updating fontconfig to version 2.2 should fix the problem for like it fixed it for everyone else who reported this problem so far.
Sven
Testing 1.3.20
On Tuesday 09 September 2003 06:23 pm, Sven Neumann wrote:
Hi,
BandiPat writes:
The new Gimp compiled fine today and installed. Upon trying to run it though, it got to a load point and just died. I ran it from the shell to check for more messages and found it doing a Segmentation fault
See http://bugzilla.gnome.org/show_bug.cgi?id=121752
Updating fontconfig to version 2.2 should fix the problem for like it fixed it for everyone else who reported this problem so far.
Sven _______________________________________________
Sven,
Not sure if that is possible though without upsetting something else.
These are just a few of the conflicts I get when trying to install
fontconfig files.
file /etc/fonts/fonts.conf from install of fontconfig-2.2.0-14 conflicts with file from package xf86tools-0.1-537 file /etc/fonts/fonts.dtd from install of fontconfig-2.2.0-14 conflicts with file from package XFree86-4.3.0-15 -------------------------
I haven't tried to force it to see if anything bad happens, but obviously XFree86 is something that is needed to do X graphics, right? I'll go with your expertise on this as I know fontconfig will be used a lot for such things as Gimp.
Patrick
Testing 1.3.20
Hi,
BandiPat writes:
Not sure if that is possible though without upsetting something else. These are just a few of the conflicts I get when trying to install fontconfig files.
file /etc/fonts/fonts.conf from install of fontconfig-2.2.0-14 conflicts with file from package xf86tools-0.1-537 file /etc/fonts/fonts.dtd from install of fontconfig-2.2.0-14 conflicts with file from package XFree86-4.3.0-15 -------------------------
I haven't tried to force it to see if anything bad happens, but obviously XFree86 is something that is needed to do X graphics, right? I'll go with your expertise on this as I know fontconfig will be used a lot for such things as Gimp.
You should be careful here since it might be a bad idea to overwite /etc/fonts/fonts.conf since this is the system-wide font configuration for everything that uses fontconfig. I would suggest you make a backup of this file before you install fontconfig. Overwriting the DTD shouldn't do any harm.
Sven
Testing 1.3.20 (SOLVED)
On Tuesday 09 September 2003 07:03 pm, BandiPat wrote:
On Tuesday 09 September 2003 06:23 pm, Sven Neumann wrote:
Hi,
BandiPat writes:
The new Gimp compiled fine today and installed. Upon trying to run it though, it got to a load point and just died. I ran it from the shell to check for more messages and found it doing a Segmentation fault
See http://bugzilla.gnome.org/show_bug.cgi?id=121752
Updating fontconfig to version 2.2 should fix the problem for like it fixed it for everyone else who reported this problem so far.
Sven _______________________________________________
Sven,
Not sure if that is possible though without upsetting something else. These are just a few of the conflicts I get when trying to install fontconfig files.file /etc/fonts/fonts.conf from install of fontconfig-2.2.0-14 conflicts with file from package xf86tools-0.1-537 file /etc/fonts/fonts.dtd from install of fontconfig-2.2.0-14 conflicts with file from package XFree86-4.3.0-15 -------------------------
I haven't tried to force it to see if anything bad happens, but obviously XFree86 is something that is needed to do X graphics, right? I'll go with your expertise on this as I know fontconfig will be used a lot for such things as Gimp.
Patrick
===================
Ok, Sven, That did in fact fix things. I was getting those above conflicts while trying to install fontconfig and fontconf-devel, but using another source installs them without conflicts and Gimp 1.3.20 runs happily now. Thanks for the heads up on the bug, I should learn to check there too, but I thought you guys might know first.
Thanks again, Patrick
Testing 1.3.20
Sven Neumann wrote:
Hi,
BandiPat writes:
The new Gimp compiled fine today and installed. Upon trying to run it though, it got to a load point and just died. I ran it from the shell to check for more messages and found it doing a Segmentation fault
See http://bugzilla.gnome.org/show_bug.cgi?id=121752
Updating fontconfig to version 2.2 should fix the problem for like it fixed it for everyone else who reported this problem so far.
Sven
Thanks for posting a link to this bug report. I'm seeing a similar problem at startup but it's not font related and is related to the "tool-safe-mode" plugin:
tom@c71414-a:~/build/gimp-1.3.20$ gimp-1.3 This is a development version of the GIMP Debug messages may appear here.
Testing CPU features...
mmx : yes
3dnow : no
mmxext : no
sse : no
sse2 : no
gimp_composite: use=yes, verbose=no +mmx
added locale domain "gimp20-script-fu" for path "(null)"
/usr/lib/gimp/1.3/plug-ins/tool-safe-mode: fatal error: Segmentation fault
/usr/lib/gimp/1.3/plug-ins/tool-safe-mode (pid:32142): [E]xit, [H]alt,
show [S]tack trace or [P]roceed: S
#0 0x404bd304 in g_on_error_stack_trace (
#1 0xbffff394 in ?? ()
#2 0x404bd221 in g_on_error_query (prg_name=0xbffff394 "32142")
#3 0x400e5413 in gimp_plugin_sigfatal_handler (sig_num=1079078920)
#4
#5 0x40593e0b in strlen () at strlen:-1
#6 0x0804929a in safe_mode_init () at tool-safe-mode-plug-in.c:52
#7 0x400e462c in gimp_main (argc=6, argv=0xbffff8c4) at gimp.c:386
#8 0x080492db in main (argc=1, argv=0x1) at tool-safe-mode-plug-in.c:68
#9 0x4052dca6 in __libc_start_main (main=0x80492c0 , argc=6,
I'll install fontconfig 2.2.0 and see if that helps any.
Thanks!
Peace...
Tom
Testing 1.3.20
Tom Williams wrote:
Sven Neumann wrote:
Hi,
BandiPat writes:
The new Gimp compiled fine today and installed. Upon trying to run it though, it got to a load point and just died. I ran it from the shell to check for more messages and found it doing a Segmentation fault
See http://bugzilla.gnome.org/show_bug.cgi?id=121752
Updating fontconfig to version 2.2 should fix the problem for like it fixed it for everyone else who reported this problem so far.
Sven
Thanks for posting a link to this bug report. I'm seeing a similar problem at startup but it's not font related and is related to the "tool-safe-mode" plugin:
This is another commonly reported bug - see http://bugzilla.gnome.org/show_bug.cgi?id=118517
To find bugs like this, you should probably add "CLOSED" and "RESOLVED" to the default set of bug statuses, and search for the most prominent word - in this case, searching for tool-safe-mode turned up 3 links :)
In brief, that's an old plug-in that was removed in version 1.3.10, so if you had an older devel gimp installed and you didn't make uninstall of that, it's an old file left lying around. Delete it, and all will be well.
Cheers, Dave.
Testing 1.3.20
David Neary wrote:
Tom Williams wrote:
Thanks for posting a link to this bug report. I'm seeing a similar problem at startup but it's not font related and is related to the "tool-safe-mode" plugin:
This is another commonly reported bug - see http://bugzilla.gnome.org/show_bug.cgi?id=118517
To find bugs like this, you should probably add "CLOSED" and "RESOLVED" to the default set of bug statuses, and search for the most prominent word - in this case, searching for tool-safe-mode turned up 3 links :)
In brief, that's an old plug-in that was removed in version 1.3.10, so if you had an older devel gimp installed and you didn't make uninstall of that, it's an old file left lying around. Delete it, and all will be well.
Cheers, Dave.
Thanks for the info. That did the trick! :)
Peace...
Tom
