GNOME Bugzilla – Bug 634235
crash in Pitivi Video Editor: Video verschoben
Last modified: 2010-11-08 14:43:04 UTC
What were you doing when the application crashed? Video verschoben Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Neu GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 495505408 vsize: 495505408 resident: 86384640 share: 30547968 rss: 86384640 rss_rlim: 18446744073709551615 CPU usage: start_time: 1289154969 rtime: 52247 utime: 9919 stime: 42328 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/python2.6' [Thread debugging using libthread_db enabled] [New Thread 0x9e8fcb70 (LWP 4799)] [New Thread 0xa00ffb70 (LWP 4796)] [New Thread 0xad5f5b70 (LWP 4795)] [New Thread 0xa0cfeb70 (LWP 4794)] [New Thread 0x9e0fbb70 (LWP 4791)] [New Thread 0x9f0fdb70 (LWP 4789)] [New Thread 0x9f8feb70 (LWP 4788)] [New Thread 0xac5f3b70 (LWP 4786)] [New Thread 0xa14ffb70 (LWP 4763)] [New Thread 0xa1efbb70 (LWP 4762)] [New Thread 0xa76ffb70 (LWP 4760)] [New Thread 0xaf5f9b70 (LWP 4759)] [New Thread 0xa8bfcb70 (LWP 4741)] [New Thread 0xa93fdb70 (LWP 4740)] [New Thread 0xa9bfeb70 (LWP 4739)] [New Thread 0xacdf4b70 (LWP 4737)] [New Thread 0xabdf2b70 (LWP 4735)] [New Thread 0xab5f1b70 (LWP 4734)] [New Thread 0xb0dfcb70 (LWP 4720)] [New Thread 0xae737b70 (LWP 4719)] [New Thread 0xb15fdb70 (LWP 4718)] [New Thread 0xb05fbb70 (LWP 4715)] [New Thread 0xa6efeb70 (LWP 4713)] [New Thread 0xb1dfeb70 (LWP 4707)] [New Thread 0xaddf6b70 (LWP 4689)] [New Thread 0xb41feb70 (LWP 4654)] [New Thread 0xb39fdb70 (LWP 4653)] [New Thread 0xb69f1b70 (LWP 4652)] [New Thread 0xb31fcb70 (LWP 4651)] [New Thread 0xb49ffb70 (LWP 4646)] [New Thread 0xb71f2b70 (LWP 4642)] 0x00110422 in __kernel_vsyscall ()
+ Trace 224543
Thread 9 (Thread 0xac5f3b70 (LWP 4786))
A debugging session is active. Inferior 1 [process 4639] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1719): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). --------------------------------------------------
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!
We are also missing step-by-step instructions to reproduce this bug.