GNOME Bugzilla – Bug 646379
pitivi issue using Ubuntu 10.10
Last modified: 2011-07-01 06:06:41 UTC
Hi, it happen to me just a little ago... parik70@parik70-desktop:~$ pitivi ** Message: pygobject_register_sinkfunc is deprecated (GstObject) (pitivi:6187): GStreamer-CRITICAL **: Padname src is not unique in element pitivi+elements+singledecodebin+singledecodebin1, not adding Traceback (most recent call last):
+ Trace 226520
self._unblockPad(target=self._target)
target.remove_event_probe(self._eventProbeId)
Killed parik70@parik70-desktop:~$ I was compelled to forcely quit the program as id DO not respond anymore, like blocked. I'm going to install all necessary packages for my linux distro to provide additional debug and strack tracing information. That's intend to temporarly fix the issue. My system is: ubuntu 10.10, Kernel Linux 2.6.35-28-generic, GNOME 2.32.0, RAM 1001.6 MB Intel Pentium 4 CPU 2.66GHz parik70@parik70-desktop:~$ sudo lshw -C video[sudo] password for parik70: *-display description: VGA compatible controller product: NV18 [GeForce4 MX 440 AGP 8x] vendor: nVidia Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a2 width: 32 bits clock: 66MHz capabilities: pm agp agp-3.0 vga_controller bus_master cap_list rom configuration: driver=nouveau latency=32 maxlatency=1 mingnt=5 resources: irq:16 memory:de000000-deffffff memory:d0000000-d7ffffff memory:dfde0000-dfdfffff parik70@parik70-desktop:~$ glxinfo | grep renderdirect rendering: Yes OpenGL renderer string: Software Rasterizer GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fragment_program, parik70@parik70-desktop:~$
Thanks for taking the time to report this bug. Without bug reproduction instructions it's very hard to determine what caused it. Please provide precise steps to trigger the bug. Also please specify the pitivi version you are using.
by now pitivi v.0.13.5. more info in a while... also posted here: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/747098
parik70, can you please update the bug with more information ?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!