Public bug reported:
Binary package hint: inkscape
I can corroborate this bug affects the amd64 and the x86 arquitecture,
i've reproduces the bug without any problem in all the computers I own.
To reproduce this bug, just open inkscape, open up the fill and stroke
dialog (shift+control+F) and click on the stroke style tab. That
instance of inkscape will probably crash (it happens every time in my
expirience).
The error it reports is the following:
(inkscape:7223): Gdk-CRITICAL **: gdk_drawable_get_size: assertion
`GDK_IS_DRAWABLE (drawable)' failed
(inkscape:7223): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable:
assertion `src != NULL' failed
(inkscape:7223): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy: assertion
`pixbuf != NULL' failed
(inkscape:7223): GdkPixbuf-CRITICAL **:
gdk_pixbuf_saturate_and_pixelate: assertion `GDK_IS_PIXBUF (src)' failed
(inkscape:7223): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(inkscape:7223): Gdk-CRITICAL **: gdk_draw_pixbuf: assertion
`GDK_IS_PIXBUF (pixbuf)' failed
(inkscape:7223): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
The program 'inkscape' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 27764 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
** Affects: inkscape (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
fatal crash with BadAlloc
https://launchpad.net/bugs/62348
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
