Bug 1036267

Description of problem:
Pressing ctrl+z.

Version-Release number of selected component:
inkscape-0.48.4-4.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        inkscape button-down.svg button-up.svg simple-player-buttons(1).svg simple-player-buttons.svg
crash_function: __kernel_vsyscall
executable:     /usr/bin/inkscape
kernel:         3.11.9-200.fc19.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
[New LWP 4152]
[New LWP 4153]
[New LWP 4154]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3600.3-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
warning: File "/var/cache/abrt-di/usr/lib/debug/usr/lib/libpython2.7.so.1.0.debug-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
To enable execution of this file add
	add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug/usr/lib/libpython2.7.so.1.0.debug-gdb.py
line to your configuration file "/home/ousia/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/ousia/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
Core was generated by `inkscape button-down.svg button-up.svg simple-player-buttons(1).svg simple-play'.
Program terminated with signal 11, Segmentation fault.
#0  sp_item_invoke_bbox_full (item=item@entry=0xd74d360, bbox=..., transform=..., flags=flags@entry=0, clear=clear@entry=0) at sp-item.cpp:846
846	        if (item->clip_ref->getObject()) {

Thread 3 (Thread 0xb1310b40 (LWP 4154)):
#0  0xb77cb424 in __kernel_vsyscall ()
No symbol table info available.
#1  0x440075bb in poll () at ../sysdeps/unix/syscall-template.S:81
No locals.
#2  0x49c65abc in poll (__timeout=__timeout@entry=-1, __nfds=__nfds@entry=3, __fds=__fds@entry=0xb0a01db8) at /usr/include/bits/poll2.h:46
No locals.
#3  g_poll (fds=fds@entry=0xb0a01db8, nfds=nfds@entry=3, timeout=timeout@entry=-1) at gpoll.c:132
No locals.
#4  0x49c56418 in g_main_context_poll (priority=2147483647, n_fds=3, fds=0xb0a01db8, timeout=-1, context=0x94f37a0) at gmain.c:3995
        poll_func = 0x49c65a90 <g_poll>
#5  g_main_context_iterate (context=0x94f37a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3696
        max_priority = 2147483647
        timeout = -1
        some_ready = <optimized out>
        nfds = 3
        allocated_nfds = <optimized out>
        fds = 0xb0a01db8
#6  0x49c56913 in g_main_loop_run (loop=0x9509510) at gmain.c:3895
        __PRETTY_FUNCTION__ = "g_main_loop_run"
#7  0x49e6991b in gdbus_shared_thread_func (user_data=0x94bcc48) at gdbusprivate.c:278

Timeout exceeded: 240 seconds, killing gdb.
Looks like gdb hung while generating backtrace.
This may be a bug in gdb. Consider submitting a bug report to gdb developers.
Please attach coredump from this crash to the bug report if you do.