Bug 634832 – black slideshow + crash

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 634832 - black slideshow + crash


Summary:	black slideshow + crash


Status:	RESOLVED NOTGNOME

Product:	gthumb
Classification:	Other
Component:	general
Version:	2.12.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-11-14 17:26 UTC by Paolo Benvenuto
Modified:	2010-12-07 13:23 UTC

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

Description Paolo Benvenuto 2010-11-14 17:26:30 UTC

Reproduce it:

- run gthumb
- go to a directory with photos
- hit f5  -> instead of the slideshow you see a black screen
- alt-f4 in order to switch the black screen off
- hit f5 again -> crash

the result when gthumb is run from the terminal:

$ gthumb
The program 'gthumb' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 10693 error_code 9 request_code 137 minor_code 7)
  (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.)


When you hit f5 the first time and you get the black screen you can switch to gthumb or to another app with alt-tab, but you must hit alt-f4 in order to switch off the black screen. If instead of closing the black screen you go back to gthumb main window and hit f5, another black screen instance is generated.

Comment 1 Paolo Benvenuto 2010-11-14 17:26:57 UTC

I'm almost sure 2.11 didn't suffer this bug

Comment 2 Fabio Durán Verdugo 2010-11-14 19:46:54 UTC

Yes I can confirm this bug.

[New Thread 2193]
[New Thread 2197]
[New Thread 2194]
Core was generated by `gthumb'.
Program terminated with signal 6, Aborted.

+ Trace 224667

Thread 1 (Thread 2193)

#0 __kernel_vsyscall
#1 raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#2 abort
at abort.c line 92
#3 g_logv
at gmessages.c line 557
#4 g_log
at gmessages.c line 577
#5 gdk_x_error
at gdkmain-x11.c line 466
#6 _XError
at XlibInt.c line 3105
#7 handle_error
at xcb_io.c line 166
#8 _XReply
at xcb_io.c line 622
#9 DRI2GetBuffersWithFormat
at dri2.c line 454
#10 dri2GetBuffersWithFormat
at dri2_glx.c line 582
#11 intel_update_renderbuffers
at intel_context.c line 290
#12 intel_prepare_render
at intel_context.c line 438
#13 intelTexSubimage
at intel_tex_subimage.c line 78
#14 intelTexSubImage2D
at intel_tex_subimage.c line 223
#15 _mesa_TexSubImage2D
at main/teximage.c line 2748
#16 glTexSubImage2D
at ../../../src/mapi/glapi/glapitemp.h line 1802
#17 _cogl_texture_driver_upload_subregion_to_gl
at cogl-texture-driver.c line 146
#18 _cogl_texture_2d_set_region
at ./cogl-texture-2d.c line 486
#19 cogl_texture_set_region
at ./cogl-texture.c line 793
#20 _cogl_atlas_texture_set_region_with_border
at ./cogl-atlas-texture.c line 446
#21 _cogl_atlas_texture_new_from_bitmap
at ./cogl-atlas-texture.c line 1049
#22 cogl_texture_new_from_bitmap
at ./cogl-texture.c line 410
#23 cogl_texture_new_from_data
at ./cogl-texture.c line 399
#24 clutter_texture_set_from_data
at ./clutter-texture.c line 1302
#25 gtk_clutter_texture_new_from_pixbuf
at ./gtk-clutter-util.c line 319
#26 clutter_projector_construct
at gth-slideshow.c line 1142
#27 _gth_slideshow_construct
at gth-slideshow.c line 473
#28 gth_slideshow_new
at gth-slideshow.c line 489
#29 gth_browser_activate_action_view_slideshow
at actions.c line 83
#30 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 79
#31 g_closure_invoke
at gclosure.c line 766
#32 signal_emit_unlocked_R
at gsignal.c line 3252
#33 g_signal_emit_valist
at gsignal.c line 2983
#34 g_signal_emit
at gsignal.c line 3040
#35 _gtk_action_emit_activate
at gtkaction.c line 794
#36 closure_accel_activate
at gtkaction.c line 1764
#37 g_closure_invoke
at gclosure.c line 766
#38 signal_emit_unlocked_R
at gsignal.c line 3252
#39 g_signal_emit_valist
at gsignal.c line 2993
#40 g_signal_emit
at gsignal.c line 3040
#41 IA__gtk_accel_group_activate
at gtkaccelgroup.c line 889
#42 IA__gtk_accel_groups_activate
at gtkaccelgroup.c line 926
#43 IA__gtk_window_activate_key
at gtkwindow.c line 8348
#44 gtk_window_key_press_event
at gtkwindow.c line 5225
#45 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 86
#46 g_type_class_meta_marshal
at gclosure.c line 877
#47 g_closure_invoke
at gclosure.c line 766
#48 signal_emit_unlocked_R
at gsignal.c line 3290
#49 g_signal_emit_valist
at gsignal.c line 2993
#50 g_signal_emit
at gsignal.c line 3040
#51 gtk_widget_event_internal
at gtkwidget.c line 4992
#52 IA__gtk_propagate_event
at gtkmain.c line 2434
#53 IA__gtk_main_do_event
at gtkmain.c line 1665
#54 gdk_event_dispatch
at gdkevents-x11.c line 2377
#55 g_main_dispatch
at gmain.c line 2149
#56 g_main_context_dispatch
at gmain.c line 2702
#57 g_main_context_iterate
at gmain.c line 2780
#58 g_main_loop_run
at gmain.c line 2988
#59 IA__gtk_main
at gtkmain.c line 1237
#60 main
at main.c line 449

Comment 3 Matthias Hawran 2010-11-24 10:33:00 UTC

Which version are you guys running?

I cannot reproduce using latest git master

http://git.gnome.org/browse/gthumb/commit/?id=bfa536ba9212e2a61a08c76b5a77016767528c54

Comment 4 Paolo Benvenuto 2010-11-24 11:07:37 UTC

2.12 master

Comment 5 Paolo Benvenuto 2010-11-24 11:15:00 UTC

I can reproduce it in master http://git.gnome.org/browse/gthumb/commit/?id=bfa536ba9212e2a61a08c76b5a77016767528c54 : black screen when hitting f5

Comment 6 Matthias Hawran 2010-11-24 11:55:42 UTC

So there must be something different with your system.
Does it occur in any directory ?

The slideshow uses clutter, so maybe a problem there.
I have libclutter-gtk-0.10-0 
Version: 0.10.4-0ubuntu1

Comment 7 Paolo Benvenuto 2010-11-24 12:16:21 UTC

$ aptitude show libclutter-gtk-0.10-0
Package: libclutter-gtk-0.10-0                    
New: yes
State: installed
Automatic install: yes
Version: 0.10.4-1ubuntu3

Comment 8 Paolo Benvenuto 2010-11-24 12:17:24 UTC

with all dirs

Comment 9 Matthias Hawran 2010-11-24 12:56:58 UTC

Ok we maybe have something

What about libclutter-1.0-0 ?
I have
Version: 1.2.4-0ubuntu1
(Ubuntu lucid)

I suppose you have
1.2.12-0ubuntu13
(Ubuntu maverick ?)

After that I can't be of much more help...

Comment 10 Paolo Benvenuto 2010-11-24 13:04:12 UTC

$ aptitude show libclutter-1.0-0
Pacchetto: libclutter-1.0-0                         
Nuovo: sì
Stato: installato
Installato automaticamente: sì
Versione: 1.2.12-0ubuntu13

Comment 11 Matthias Hawran 2010-12-02 16:11:07 UTC

Paolo (meaning Bacchilega), can you reproduce with this version of libclutter ?
Looks like there's a break there.

Comment 12 Michael Chudobiak 2010-12-02 18:52:05 UTC

With git master, I just get a black screen for the slideshow, if I have a transition effect enabled. No crash though.

This happens using the embedded Intel video chipset, as well as a Radeon card (so it is not a driver issue).

clutter-1.2.14-1.fc14.1.x86_64

- Mike

Comment 13 Paolo Bacchilega 2010-12-07 13:23:33 UTC

this is a bug in clutter-gtk fixed since version 0.10.6