Bug 163939 – GdkPixbuf-CRITICAL on new graph.

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 163939 - GdkPixbuf-CRITICAL on new graph.


Summary:	GdkPixbuf-CRITICAL on new graph.


Status:	RESOLVED FIXED

Product:	Gnumeric
Classification:	Applications
Component:	Charting
Version:	git master
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Emmanuel Pacaud
QA Contact:	Jody Goldberg

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-01-13 14:23 UTC by Morten Welinder
Modified:	2005-01-14 05:29 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Morten Welinder 2005-01-13 14:23:27 UTC

1. Enter 1, 2, 3 in A1:A3 and select.
2. Press Graph.
3. Press Insert.
4. Click and...
5. ...drag to mark an area.

Between 4 and 5 I get...

Breakpoint 1, g_log (log_domain=0xfb335208 "GdkPixbuf",
log_level=G_LOG_LEVEL_CRITICAL, format=0xfaae24a8 "%s: assertion `%s' failed")
at gmessages.c:507
507       g_logv (log_domain, log_level, format, args);

+ Trace 54467

#0 g_log
at gmessages.c line 507
#1 g_return_if_fail_warning
at gmessages.c line 522
#2 gdk_pixbuf_new
at gdk-pixbuf.c line 283
#3 gog_renderer_pixbuf_update
at gog-renderer-pixbuf.c line 852
#4 gog_control_foocanvas_update
at gog-control-foocanvas.c line 190
#5 foo_canvas_item_invoke_update
at foo-canvas.c line 433
#6 foo_canvas_group_update
at foo-canvas.c line 1383
#7 foo_canvas_item_invoke_update
at foo-canvas.c line 433
#8 foo_canvas_group_update
at foo-canvas.c line 1383
#9 foo_canvas_item_invoke_update
at foo-canvas.c line 433
#10 do_update
at foo-canvas.c line 2926
#11 idle_handler
at foo-canvas.c line 2961
#12 g_idle_dispatch
at gmain.c line 3821
#13 g_main_dispatch
at gmain.c line 1947
#14 g_main_context_dispatch
at gmain.c line 2497
#15 g_main_context_iterate
at gmain.c line 2578
#16 g_main_loop_run
at gmain.c line 2782
#17 bonobo_main
at bonobo-main.c line 297
#18 main
at main-application.c line 366
#0 g_log
at gmessages.c line 507
#1 gog_renderer_pixbuf_update
at gog-renderer-pixbuf.c line 855
#2 gog_control_foocanvas_update
at gog-control-foocanvas.c line 190
#3 foo_canvas_item_invoke_update
at foo-canvas.c line 433
#4 foo_canvas_group_update
at foo-canvas.c line 1383
#5 foo_canvas_item_invoke_update
at foo-canvas.c line 433
#6 foo_canvas_group_update
at foo-canvas.c line 1383
#7 foo_canvas_item_invoke_update
at foo-canvas.c line 433
#8 do_update
at foo-canvas.c line 2926
#9 idle_handler
at foo-canvas.c line 2961
#10 g_idle_dispatch
at gmain.c line 3821
#11 g_main_dispatch
at gmain.c line 1947
#12 g_main_context_dispatch
at gmain.c line 2497
#13 g_main_context_iterate
at gmain.c line 2578
#14 g_main_loop_run
at gmain.c line 2782
#15 bonobo_main
at bonobo-main.c line 297
#16 main
at main-application.c line 366


** (gnumeric:4275): WARNING **: Chart is too large

Comment 1 Morten Welinder 2005-01-13 14:24:37 UTC

Note, that you need to run the debugger from another X server.  The breakpoint
is hit with a active grab.

Comment 2 Emmanuel Pacaud 2005-01-13 15:05:41 UTC

You don't even have to drag. A simple click which should give you a graph with
default size shows the same message.

There's two problem here. First is probably related to #162631, where a graph
with  a null size is created.

And we should not try to create a null sized pixbuf in gog_renderer_pixbuf_update.

Comment 3 Jody Goldberg 2005-01-14 05:29:49 UTC

patched.