Crashes on startup in clutter_texture_bind_tile

[Tom Parker]

Attempting to try out the ume-launcher on a Debian unstable system (using clutter 0.6.4) causes a crash on startup with nothing ever displayed. I'm using the Nvidia binary drivers, and running a full Gnome desktop - some of which may clash with the ume-launcher, but it should really tell me this instead of just crashing.

tparker@shostakovich:[~/data/src/netbook-remix-launcher] gdb ./src/ume-launcher
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) r
Starting program: /data/tparker/src/netbook-remix-launcher/src/ume-launcher
[Thread debugging using libthread_db enabled]
[New Thread 0xb636b6e0 (LWP 25095)]
/homes/tparker/data/src/netbook-remix-launcher/data/Favorites.directory
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb636b6e0 (LWP 25095)]
0xb7f57e92 in clutter_texture_bind_tile (texture=0x8187ba0, index_=0) at clutter-texture.c:1828
1828 cogl_texture_bind (priv->target_type, priv->tiles[index_]);
(gdb) thread apply all bt

Thread 1 (Thread 0xb636b6e0 (LWP 25095)):
#0 0xb7f57e92 in clutter_texture_bind_tile (texture=0x8187ba0, index_=0) at clutter-texture.c:1828
#1 0x0805ffe1 in tidy_texture_frame_paint (self=0x81e8800) at tidy-texture-frame.c:124
#2 0xb7f2fb3c in clutter_actor_paint (self=0x81e8800) at clutter-actor.c:1242
#3 0xb7f430a5 in clutter_group_paint (actor=0x8182048) at clutter-group.c:103
#4 0xb7f2fb3c in clutter_actor_paint (self=0x8182048) at clutter-actor.c:1242
#5 0xb7f430a5 in clutter_group_paint (actor=0x80ad0d0) at clutter-group.c:103
#6 0xb7f55d07 in clutter_stage_paint (self=0x80ad0d0) at clutter-stage.c:112
#7 0xb7f2fb3c in clutter_actor_paint (self=0x80ad0d0) at clutter-actor.c:1242
#8 0xb7f5e738 in clutter_backend_glx_redraw (backend=0x808e860) at clutter-backend-glx.c:343
#9 0xb7f32c57 in _clutter_backend_redraw (backend=0x0) at clutter-backend.c:171
#10 0xb7f47d39 in clutter_redraw () at clutter-main.c:159
#11 0xb7f681e6 in clutter_stage_x11_show (actor=0x80ad0d0) at clutter-stage-x11.c:120
#12 0xb75c8c39 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
#13 0xb75ba089 in ?? () from /usr/lib/libgobject-2.0.so.0
#14 0x080726e0 in ?? ()
#15 0x00000000 in ?? ()
(gdb)

(FYI I'm also using my patch from https://bugs.launchpad.net/netbook-remix-launcher/+bug/240419 for uninstalled operation, but I doubt that's causing this)

[Tom Parker (palfrey)]

Recompiled with CFLAGS="-g -O0" (to check it wasn't some weird optimisation getting gdb confused and crashing somewhere else) just to check. No such luck, same crash occurs. Results from "thread apply all bt full" so we've got all the variable values:

0xb7f0ce92 in clutter_texture_bind_tile (texture=0x818aba0, index_=0) at clutter-texture.c:1828
1828 cogl_texture_bind (priv->target_type, priv->tiles[index_]);
(gdb) thread apply all bt full

Thread 1 (Thread 0xb63206e0 (LWP 16495)):
#0 0xb7f0ce92 in clutter_texture_bind_tile (texture=0x818aba0, index_=0) at clutter-texture.c:1828
 priv = (ClutterTexturePrivate *) 0x818ac30
 __PRETTY_FUNCTION__ = "clutter_texture_bind_tile"
#1 0x080622ce in tidy_texture_frame_paint (self=0x81eb800) at tidy-texture-frame.c:124
 priv = (TidyTextureFramePrivate *) 0x81eb898
 clone_texture = (ClutterCloneTexture *) 0x81eb800
 parent_texture = (ClutterTexture *) 0x818aba0
 width = 1094
 height = 1072
 pwidth = 0
 pheight = 0
 ex = 136230912
 ey = 134815744
 tx1 = 1966080
 ty1 = 1966080
 tx2 = -1966080
 ty2 = -1966080
 tw = 0
 th = 0
 target_type = 34037
 col = {red = 255 '�', green = 255 '�', blue = 255 '�', alpha = 255 '�'}
#2 0xb7ee4b3c in clutter_actor_paint (self=0x81eb800) at clutter-actor.c:1242
 priv = (ClutterActorPrivate *) 0x81eb820
 context = <value optimized out>
 __PRETTY_FUNCTION__ = "clutter_actor_paint"
#3 0xb7ef80a5 in clutter_group_paint (actor=0x8185048) at clutter-group.c:103
 child_item = (GList *) 0x81d8330
 __PRETTY_FUNCTION__ = "clutter_group_paint"
#4 0xb7ee4b3c in clutter_actor_paint (self=0x8185048) at clutter-actor.c:1242
 priv = (ClutterActorPrivate *) 0x8185068
 context = <value optimized out>
 __PRETTY_FUNCTION__ = "clutter_actor_paint"
#5 0xb7ef80a5 in clutter_group_paint (actor=0x80b00d0) at clutter-group.c:103
 child_item = (GList *) 0x818c170
 __PRETTY_FUNCTION__ = "clutter_group_paint"
#6 0xb7f0ad07 in clutter_stage_paint (self=0x80b00d0) at clutter-stage.c:112
 priv = (ClutterStagePrivate *) 0x80b01a0
#7 0xb7ee4b3c in clutter_actor_paint (self=0x80b00d0) at clutter-actor.c:1242
 priv = (ClutterActorPrivate *) 0x80b0128
 context = <value optimized out>
 __PRETTY_FUNCTION__ = "clutter_actor_paint"
#8 0xb7f13738 in clutter_backend_glx_redraw (backend=0x8091860) at clutter-backend-glx.c:343
No locals.
#9 0xb7ee7c57 in _clutter_backend_redraw (backend=0x0) at clutter-backend.c:171
No locals.
#10 0xb7efcd39 in clutter_redraw () at clutter-main.c:159
 ctx = (ClutterMainContext *) 0x8090ba8
 stage = (ClutterActor *) 0x80b00d0
 timer = (GTimer *) 0x0
 timer_n_frames = 0
#11 0xb7f1d1e6 in clutter_stage_x11_show (actor=0x80b00d0) at clutter-stage-x11.c:120
No locals.
#12 0xb757dc39 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#13 0xb756f089 in ?? () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#14 0x080756e0 in ?? ()
No symbol table info available.
#15 0x00000000 in ?? ()
No symbol table info available.
(gdb)

[Neil J. Patel (njpatel)]

Hi, can you do a full install (you can do an sudo make uninstall afterwards) to see if it works please. I'm wondering if it cannot find a image, therefore a texture is not being loaded correctly which means the tidy-texture-frame doesn't have a texture to bind to (which makes it crash).

[Tom Parker (palfrey)]

I just updated to the latest bzr head, and it appears to have gone away, so it's probably been fixed somewhere between 61 and 65. Notably, one way I found of stopping the problem from happening was using the "-w" switch (which also has the useful result of the launcher actually appearing on my desktop)

[Neil J. Patel (njpatel)]

Marking a fix-released (as per last comment). Please re-open if this problem still occurs,