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 641596 - crash in Pitivi Video Editor: Startup
crash in Pitivi Video Editor: Startup
Status: RESOLVED INCOMPLETE
Product: pitivi
Classification: Other
Component: General
0.13.5
Other All
: High critical
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2011-02-05 12:14 UTC by mike.blewett
Modified: 2011-02-05 14:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description mike.blewett 2011-02-05 12:14:13 UTC
What were you doing when the application crashed?
Startup


Distribution: Ubuntu 11.04 (natty)
Gnome Release: 2.32.1 2010-12-23 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.38-1-generic #28-Ubuntu SMP Fri Jan 28 15:17:31 UTC 2011 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10999901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ambiance
Icon Theme: ubuntu-mono-dark
GTK+ Modules: gnomesegvhandler

Memory status: size: 112209920 vsize: 112209920 resident: 31264768 share: 15982592 rss: 31264768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1296907990 rtime: 41 utime: 29 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/python2.7'

[Thread debugging using libthread_db enabled]
[New Thread 0xb72cbb70 (LWP 2551)]
0x003d5416 in __kernel_vsyscall ()

Thread 1 (Thread 0xb78616c0 (LWP 2543))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomesegvhandler.so
  • #5 <signal handler called>
  • #6 g_datalist_id_set_data_full
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/pymodules/python2.7/gobject/_gobject.so
  • #12 ??
  • #13 PyEval_EvalFrameEx
  • #14 PyEval_EvalFrameEx
  • #15 PyEval_EvalCodeEx
  • #16 ??
  • #17 PyObject_Call
  • #18 ??
  • #19 PyObject_Call
  • #20 ??
  • #21 ??
  • #22 PyObject_Call
  • #23 PyEval_EvalFrameEx
  • #24 PyEval_EvalFrameEx
  • #25 PyEval_EvalCodeEx
  • #26 ??
  • #27 PyObject_Call
  • #28 ??
  • #29 PyObject_Call
  • #30 ??
  • #31 ??
  • #32 PyObject_Call
  • #33 PyEval_EvalFrameEx
  • #34 PyEval_EvalFrameEx
  • #35 PyEval_EvalCodeEx
  • #36 ??
  • #37 PyObject_Call
  • #38 ??
  • #39 PyObject_Call
  • #40 ??
  • #41 ??
  • #42 PyObject_Call
  • #43 PyEval_EvalFrameEx
  • #44 PyEval_EvalFrameEx
  • #45 PyEval_EvalFrameEx
  • #46 PyEval_EvalFrameEx
  • #47 PyEval_EvalCodeEx
  • #48 PyEval_EvalCode
  • #49 PyRun_SimpleFileExFlags
  • #50 Py_Main
  • #51 main
A debugging session is active.

	Inferior 1 [process 2543] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Comment 1 Akhil Laddha 2011-02-05 14:54:41 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!