Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
From: SourceForge.net <noreply@so...> - 2005-09-21 17:23:42
|
Bugs item #1277746, was opened at 2005-09-01 00:59 Message generated for change (Settings changed) made by buliabyak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1277746&group_id=93438 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Win32 >Status: Closed >Resolution: Duplicate Priority: 9 Submitted By: Jimdoria (jimdoria) Assigned to: Nobody/Anonymous (nobody) >Summary: WIN32: crash on start: shape.c: line 75 (pango_shape) Initial Comment: I just installed Inkscape 0.42 for the first time on a Windows ME machine. When I try to run it, the following error appears: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... When I click OK for this error, I get a Microsoft Visual C++ Runtime Library dialog with the message: Runtime Error! Program C:\PROGRAM FILES\INKSCAPE\INKSCAPE.EXE abnormal program termination. Seems like an MSVCRT DLL version mismatch in the WINDOWS\SYSTEM folder. Shouldn't the correct version be put in place by the installer? Which version is required? ---------------------------------------------------------------------- Comment By: Steffen (vonhalenbach) Date: 2005-09-20 18:46 Message: Logged In: YES user_id=1332704 Hello ! I had exactley the same error message. That was my first install of Inkscape. The next two installs were ok. Where do you got the Install-pakage from? Can you go to the console, into the Inkscape folder an type in: dir /O *.dll > def.txt and upload it here? I have seen that in my broken folder the dlls alone are 42MB big. In the folder with the working inkscape it is all together about 16.4MB big. I hope it helps. Greetings Steffen ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-15 19:36 Message: Logged In: YES user_id=1338183 OK, I ran from the command line. The output was Inkscape 0.42+devel (Sep 9 2005) I grabbed the latest version to see if the problem had fixed itself. I also tested with the previous version - 0.42.2 (August 23 2005) was the --version output - and had identical results. Inkscape is still crashing on startup with the same messages as in my 09/01 posting. Crashes on startup in exactly the same way when run from the command line. Here is the backtrace: C:\mingw\bin>gdb "\Program Files\Inkscape\inkscape.exe" GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (gdb) run Starting program: \Program Files\Inkscape\inkscape.exe Program received signal SIGSEGV, Segmentation fault. 0x01d4b581 in ?? () (gdb) bt #0 0x01d4b581 in ?? () #1 0x01cb7aa6 in ?? () #2 0x01cb7b7b in ?? () #3 0x00401bab in sp_main_gui(int, char const**) () #4 0x004316c8 in Inkscape::NSApplication::Application::run() () #5 0x0040165e in main () (gdb) > If you suspect that an MSVCRT DLL version mismatch > might be to blame, then can you indicate what version > you're currently using, and say how someone else can > find out what version they're using? The version of MSVCRT I'm using would seem to be 6.01.0924. You can find USUALLY out what version is in use by searching the WINDOWS\SYSTEM folder (for Win 9X) or WINDOWS\SYSTEM32 folder (for Win 2K/XP) for MSVCRT.DLL then checking the file properties dialog. (Info is displayed on the Version tab.) I say usually, because if there is another version of this file on the system, perhaps hiding in an application directory, that version may get loaded first and prevent the "right one" from loading into memory. (Only one version of a given Windows DLL may be loaded at a time.) Well-behaved apps are supposed to check the version of MSVCRT (and other core DLLs) during install, and place their version in the SYSTEM folder ONLY if it is later than the one that is already there. But not all apps behave well, as we know. ;-) To find out which version is currently loaded into memory, you need the Process Explorer utility from http://www.sysinternals.com. I used this to verify that the version in my SYSTEM folder is actually the one that is in memory when the crash occurs. Anyway, the MSVCRT connection was only a guess on my part - and a fairly uneducated one at that. > If the problem is because of a DLL version mismatch, > then compiling for yourself should fix the problem. That's nice to know. Now if only I were a C++ developer and knew how to compile X-platform binaries, I'd be all set. ;-) Sadly, I'm just a lowly end-user and such things are beyond my abilities. Is it possible that something in the latest Windows INSTALLER package is not doing it's job properly? I noticed that the file size for .42 is substantially smaller than that for .41. Has something been left out of the install package that used to be there? I'd really like to get this working on my system. I've gone back to 0.41 which runs fine on this system. But I'm running into compatibility issues when I try to switch SVG files between the different versions, so I'd like to bring all my systems up to 0.42-2 if I can. Also, since I'm using Inkscape to work on a project right now, I'd like to be able to report any bugs I find, but I can't do this if I'm not using the latest version on my primary work platform. ---------------------------------------------------------------------- Comment By: Peter J. R. Moulder (pjrm) Date: 2005-09-12 13:36 Message: Logged In: YES user_id=827826 One simple thing to try to start with: humour me and try running inkscape --version from the command-line to verify that you really are running 0.42.2. (I'm told you may need to do inkscape --version > tmp.txt and then type tmp.txt.) Then run inkscape (with no arguments) from the same command-line and reproduce the bug. It wouldn't be the first time that I or anyone else had mistakenly run the wrong version of something. If you suspect that an MSVCRT DLL version mismatch might be to blame, then can you indicate what version you're currently using, and say how someone else can find out what version they're using? (I can't help here, as I'm not a windows user.) If the problem is because of a DLL version mismatch, then compiling for yourself should fix the problem. In case the bug is in inkscape code rather than a build problem, I've just now added some assertions to the sole place in inkscape that directly calls pango_shape. However, pango_shape can also be called by functions within pango. A backtrace might be helpful to see what bit of inkscape code is responsible for having pango_shape called. See http://inkscape.org/report_bugs.php for how to get a backtrace. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-01 18:10 Message: Logged In: YES user_id=1338183 Uninstalled .42.1 and installed .42.2. Stilll gettng the first error: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... When I click OK for this message a second message is displayed: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... Pango-CRITICAL (recursed) **: _pango_engine_shape_shape: assertion 'PANGO_IS_FONT (font)' failed aborting... Then nothing. ---------------------------------------------------------------------- Comment By: bulia byak (buliabyak) Date: 2005-09-01 06:19 Message: Logged In: YES user_id=741217 This is one of the bugs fixed in 0.42.2. Please upgrade. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-01 01:07 Message: Logged In: YES user_id=1338183 ALSO: A second message is displayed following the first: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... GLib-GObject-CRITICAL (recursed) **:g_object_ref:assertion 'G_IS_OBJECT (object)' failed aborting... Clicking OK again produces the MS VC++ Runtime error dialog. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1277746&group_id=93438 |
From: SourceForge.net <noreply@so...> - 2005-09-26 15:52:07
|
Bugs item #1277746, was opened at 2005-08-31 16:59 Message generated for change (Comment added) made by jimdoria You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1277746&group_id=93438 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Win32 >Status: Open >Resolution: Rejected >Priority: 8 Submitted By: Jimdoria (jimdoria) Assigned to: Nobody/Anonymous (nobody) Summary: WIN32: crash on start: shape.c: line 75 (pango_shape) Initial Comment: I just installed Inkscape 0.42 for the first time on a Windows ME machine. When I try to run it, the following error appears: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... When I click OK for this error, I get a Microsoft Visual C++ Runtime Library dialog with the message: Runtime Error! Program C:\PROGRAM FILES\INKSCAPE\INKSCAPE.EXE abnormal program termination. Seems like an MSVCRT DLL version mismatch in the WINDOWS\SYSTEM folder. Shouldn't the correct version be put in place by the installer? Which version is required? ---------------------------------------------------------------------- >Comment By: Jimdoria (jimdoria) Date: 2005-09-26 11:52 Message: Logged In: YES user_id=1338183 This bug is NOT the same as 1247061. That bug prevents the File Open dialog from appearing. This bug prevents the program from RUNNING AT ALL. This bug is STILL OCURRING with the 2005.9.23 build under Windows ME. IT HAS NOT BEEN FIXED. 1. Uninstalled the (working) Inkscape 0.41-1. 2. Installed the "thrice-daily" build inkscape-0509260200.exe. Output of inkscape --version = Inkscape 0.42+dvel (Sep 23 2005) 3. Ran Inkscape. SAME ERROR as in my 2005.09.01 posting. INKSCAPE WILL NOT RUN. You guys broke something starting with the .42 build. New backtrace info (using the gdb installed with inkscape): (gdb) run Starting program: C:\Program Files\Inkscape/inkscape.exe Program received signal SIGSEGV, Segmentation fault. 0xee589af8 in ?? () (gdb) bt #0 0xee589af8 in ?? () #1 0x01cb7aa6 in ?? () #2 0x01cb7b7b in ?? () #3 0x00401bab in sp_main_gui(int, char const**) () #4 0x00431918 in Inkscape::NSApplication::Application::run() () #5 0x0040165e in main () (gdb) Vonhalenbach, I don't want to clutter up the bug with directory listing dumps, but if you (or someone else) want to see the listing of files for the latest install that is crashing, go to: http://www.geocities.com/jim_doria/sourceforge/inkscape.txt IS THIS HELPING? ---------------------------------------------------------------------- Comment By: Steffen (vonhalenbach) Date: 2005-09-20 10:46 Message: Logged In: YES user_id=1332704 Hello ! I had exactley the same error message. That was my first install of Inkscape. The next two installs were ok. Where do you got the Install-pakage from? Can you go to the console, into the Inkscape folder an type in: dir /O *.dll > def.txt and upload it here? I have seen that in my broken folder the dlls alone are 42MB big. In the folder with the working inkscape it is all together about 16.4MB big. I hope it helps. Greetings Steffen ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-15 11:36 Message: Logged In: YES user_id=1338183 OK, I ran from the command line. The output was Inkscape 0.42+devel (Sep 9 2005) I grabbed the latest version to see if the problem had fixed itself. I also tested with the previous version - 0.42.2 (August 23 2005) was the --version output - and had identical results. Inkscape is still crashing on startup with the same messages as in my 09/01 posting. Crashes on startup in exactly the same way when run from the command line. Here is the backtrace: C:\mingw\bin>gdb "\Program Files\Inkscape\inkscape.exe" GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (gdb) run Starting program: \Program Files\Inkscape\inkscape.exe Program received signal SIGSEGV, Segmentation fault. 0x01d4b581 in ?? () (gdb) bt #0 0x01d4b581 in ?? () #1 0x01cb7aa6 in ?? () #2 0x01cb7b7b in ?? () #3 0x00401bab in sp_main_gui(int, char const**) () #4 0x004316c8 in Inkscape::NSApplication::Application::run() () #5 0x0040165e in main () (gdb) > If you suspect that an MSVCRT DLL version mismatch > might be to blame, then can you indicate what version > you're currently using, and say how someone else can > find out what version they're using? The version of MSVCRT I'm using would seem to be 6.01.0924. You can find USUALLY out what version is in use by searching the WINDOWS\SYSTEM folder (for Win 9X) or WINDOWS\SYSTEM32 folder (for Win 2K/XP) for MSVCRT.DLL then checking the file properties dialog. (Info is displayed on the Version tab.) I say usually, because if there is another version of this file on the system, perhaps hiding in an application directory, that version may get loaded first and prevent the "right one" from loading into memory. (Only one version of a given Windows DLL may be loaded at a time.) Well-behaved apps are supposed to check the version of MSVCRT (and other core DLLs) during install, and place their version in the SYSTEM folder ONLY if it is later than the one that is already there. But not all apps behave well, as we know. ;-) To find out which version is currently loaded into memory, you need the Process Explorer utility from http://www.sysinternals.com. I used this to verify that the version in my SYSTEM folder is actually the one that is in memory when the crash occurs. Anyway, the MSVCRT connection was only a guess on my part - and a fairly uneducated one at that. > If the problem is because of a DLL version mismatch, > then compiling for yourself should fix the problem. That's nice to know. Now if only I were a C++ developer and knew how to compile X-platform binaries, I'd be all set. ;-) Sadly, I'm just a lowly end-user and such things are beyond my abilities. Is it possible that something in the latest Windows INSTALLER package is not doing it's job properly? I noticed that the file size for .42 is substantially smaller than that for .41. Has something been left out of the install package that used to be there? I'd really like to get this working on my system. I've gone back to 0.41 which runs fine on this system. But I'm running into compatibility issues when I try to switch SVG files between the different versions, so I'd like to bring all my systems up to 0.42-2 if I can. Also, since I'm using Inkscape to work on a project right now, I'd like to be able to report any bugs I find, but I can't do this if I'm not using the latest version on my primary work platform. ---------------------------------------------------------------------- Comment By: Peter J. R. Moulder (pjrm) Date: 2005-09-12 05:36 Message: Logged In: YES user_id=827826 One simple thing to try to start with: humour me and try running inkscape --version from the command-line to verify that you really are running 0.42.2. (I'm told you may need to do inkscape --version > tmp.txt and then type tmp.txt.) Then run inkscape (with no arguments) from the same command-line and reproduce the bug. It wouldn't be the first time that I or anyone else had mistakenly run the wrong version of something. If you suspect that an MSVCRT DLL version mismatch might be to blame, then can you indicate what version you're currently using, and say how someone else can find out what version they're using? (I can't help here, as I'm not a windows user.) If the problem is because of a DLL version mismatch, then compiling for yourself should fix the problem. In case the bug is in inkscape code rather than a build problem, I've just now added some assertions to the sole place in inkscape that directly calls pango_shape. However, pango_shape can also be called by functions within pango. A backtrace might be helpful to see what bit of inkscape code is responsible for having pango_shape called. See http://inkscape.org/report_bugs.php for how to get a backtrace. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-01 10:10 Message: Logged In: YES user_id=1338183 Uninstalled .42.1 and installed .42.2. Stilll gettng the first error: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... When I click OK for this message a second message is displayed: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... Pango-CRITICAL (recursed) **: _pango_engine_shape_shape: assertion 'PANGO_IS_FONT (font)' failed aborting... Then nothing. ---------------------------------------------------------------------- Comment By: bulia byak (buliabyak) Date: 2005-08-31 22:19 Message: Logged In: YES user_id=741217 This is one of the bugs fixed in 0.42.2. Please upgrade. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-08-31 17:07 Message: Logged In: YES user_id=1338183 ALSO: A second message is displayed following the first: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... GLib-GObject-CRITICAL (recursed) **:g_object_ref:assertion 'G_IS_OBJECT (object)' failed aborting... Clicking OK again produces the MS VC++ Runtime error dialog. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1277746&group_id=93438 |
From: SourceForge.net <noreply@so...> - 2005-09-26 20:15:10
|
Bugs item #1277746, was opened at 2005-08-31 13:59 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1277746&group_id=93438 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Win32 Status: Open Resolution: Rejected Priority: 8 Submitted By: Jimdoria (jimdoria) Assigned to: Nobody/Anonymous (nobody) Summary: WIN32: crash on start: shape.c: line 75 (pango_shape) Initial Comment: I just installed Inkscape 0.42 for the first time on a Windows ME machine. When I try to run it, the following error appears: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... When I click OK for this error, I get a Microsoft Visual C++ Runtime Library dialog with the message: Runtime Error! Program C:\PROGRAM FILES\INKSCAPE\INKSCAPE.EXE abnormal program termination. Seems like an MSVCRT DLL version mismatch in the WINDOWS\SYSTEM folder. Shouldn't the correct version be put in place by the installer? Which version is required? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-26 13:15 Message: Logged In: NO We replaced the gtk2.6 libs with the gtk2.8 libs. Adib. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-26 08:52 Message: Logged In: YES user_id=1338183 This bug is NOT the same as 1247061. That bug prevents the File Open dialog from appearing. This bug prevents the program from RUNNING AT ALL. This bug is STILL OCURRING with the 2005.9.23 build under Windows ME. IT HAS NOT BEEN FIXED. 1. Uninstalled the (working) Inkscape 0.41-1. 2. Installed the "thrice-daily" build inkscape-0509260200.exe. Output of inkscape --version = Inkscape 0.42+dvel (Sep 23 2005) 3. Ran Inkscape. SAME ERROR as in my 2005.09.01 posting. INKSCAPE WILL NOT RUN. You guys broke something starting with the .42 build. New backtrace info (using the gdb installed with inkscape): (gdb) run Starting program: C:\Program Files\Inkscape/inkscape.exe Program received signal SIGSEGV, Segmentation fault. 0xee589af8 in ?? () (gdb) bt #0 0xee589af8 in ?? () #1 0x01cb7aa6 in ?? () #2 0x01cb7b7b in ?? () #3 0x00401bab in sp_main_gui(int, char const**) () #4 0x00431918 in Inkscape::NSApplication::Application::run() () #5 0x0040165e in main () (gdb) Vonhalenbach, I don't want to clutter up the bug with directory listing dumps, but if you (or someone else) want to see the listing of files for the latest install that is crashing, go to: http://www.geocities.com/jim_doria/sourceforge/inkscape.txt IS THIS HELPING? ---------------------------------------------------------------------- Comment By: Steffen (vonhalenbach) Date: 2005-09-20 07:46 Message: Logged In: YES user_id=1332704 Hello ! I had exactley the same error message. That was my first install of Inkscape. The next two installs were ok. Where do you got the Install-pakage from? Can you go to the console, into the Inkscape folder an type in: dir /O *.dll > def.txt and upload it here? I have seen that in my broken folder the dlls alone are 42MB big. In the folder with the working inkscape it is all together about 16.4MB big. I hope it helps. Greetings Steffen ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-15 08:36 Message: Logged In: YES user_id=1338183 OK, I ran from the command line. The output was Inkscape 0.42+devel (Sep 9 2005) I grabbed the latest version to see if the problem had fixed itself. I also tested with the previous version - 0.42.2 (August 23 2005) was the --version output - and had identical results. Inkscape is still crashing on startup with the same messages as in my 09/01 posting. Crashes on startup in exactly the same way when run from the command line. Here is the backtrace: C:\mingw\bin>gdb "\Program Files\Inkscape\inkscape.exe" GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (gdb) run Starting program: \Program Files\Inkscape\inkscape.exe Program received signal SIGSEGV, Segmentation fault. 0x01d4b581 in ?? () (gdb) bt #0 0x01d4b581 in ?? () #1 0x01cb7aa6 in ?? () #2 0x01cb7b7b in ?? () #3 0x00401bab in sp_main_gui(int, char const**) () #4 0x004316c8 in Inkscape::NSApplication::Application::run() () #5 0x0040165e in main () (gdb) > If you suspect that an MSVCRT DLL version mismatch > might be to blame, then can you indicate what version > you're currently using, and say how someone else can > find out what version they're using? The version of MSVCRT I'm using would seem to be 6.01.0924. You can find USUALLY out what version is in use by searching the WINDOWS\SYSTEM folder (for Win 9X) or WINDOWS\SYSTEM32 folder (for Win 2K/XP) for MSVCRT.DLL then checking the file properties dialog. (Info is displayed on the Version tab.) I say usually, because if there is another version of this file on the system, perhaps hiding in an application directory, that version may get loaded first and prevent the "right one" from loading into memory. (Only one version of a given Windows DLL may be loaded at a time.) Well-behaved apps are supposed to check the version of MSVCRT (and other core DLLs) during install, and place their version in the SYSTEM folder ONLY if it is later than the one that is already there. But not all apps behave well, as we know. ;-) To find out which version is currently loaded into memory, you need the Process Explorer utility from http://www.sysinternals.com. I used this to verify that the version in my SYSTEM folder is actually the one that is in memory when the crash occurs. Anyway, the MSVCRT connection was only a guess on my part - and a fairly uneducated one at that. > If the problem is because of a DLL version mismatch, > then compiling for yourself should fix the problem. That's nice to know. Now if only I were a C++ developer and knew how to compile X-platform binaries, I'd be all set. ;-) Sadly, I'm just a lowly end-user and such things are beyond my abilities. Is it possible that something in the latest Windows INSTALLER package is not doing it's job properly? I noticed that the file size for .42 is substantially smaller than that for .41. Has something been left out of the install package that used to be there? I'd really like to get this working on my system. I've gone back to 0.41 which runs fine on this system. But I'm running into compatibility issues when I try to switch SVG files between the different versions, so I'd like to bring all my systems up to 0.42-2 if I can. Also, since I'm using Inkscape to work on a project right now, I'd like to be able to report any bugs I find, but I can't do this if I'm not using the latest version on my primary work platform. ---------------------------------------------------------------------- Comment By: Peter J. R. Moulder (pjrm) Date: 2005-09-12 02:36 Message: Logged In: YES user_id=827826 One simple thing to try to start with: humour me and try running inkscape --version from the command-line to verify that you really are running 0.42.2. (I'm told you may need to do inkscape --version > tmp.txt and then type tmp.txt.) Then run inkscape (with no arguments) from the same command-line and reproduce the bug. It wouldn't be the first time that I or anyone else had mistakenly run the wrong version of something. If you suspect that an MSVCRT DLL version mismatch might be to blame, then can you indicate what version you're currently using, and say how someone else can find out what version they're using? (I can't help here, as I'm not a windows user.) If the problem is because of a DLL version mismatch, then compiling for yourself should fix the problem. In case the bug is in inkscape code rather than a build problem, I've just now added some assertions to the sole place in inkscape that directly calls pango_shape. However, pango_shape can also be called by functions within pango. A backtrace might be helpful to see what bit of inkscape code is responsible for having pango_shape called. See http://inkscape.org/report_bugs.php for how to get a backtrace. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-09-01 07:10 Message: Logged In: YES user_id=1338183 Uninstalled .42.1 and installed .42.2. Stilll gettng the first error: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... When I click OK for this message a second message is displayed: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... Pango-CRITICAL (recursed) **: _pango_engine_shape_shape: assertion 'PANGO_IS_FONT (font)' failed aborting... Then nothing. ---------------------------------------------------------------------- Comment By: bulia byak (buliabyak) Date: 2005-08-31 19:19 Message: Logged In: YES user_id=741217 This is one of the bugs fixed in 0.42.2. Please upgrade. ---------------------------------------------------------------------- Comment By: Jimdoria (jimdoria) Date: 2005-08-31 14:07 Message: Logged In: YES user_id=1338183 ALSO: A second message is displayed following the first: Pango-ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting... GLib-GObject-CRITICAL (recursed) **:g_object_ref:assertion 'G_IS_OBJECT (object)' failed aborting... Clicking OK again produces the MS VC++ Runtime error dialog. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1277746&group_id=93438 |