Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-16 Thread Sebastian Dröge
reassign 475735 gstreamer0.10 found 475735 0.10.18-2 thanks Am Dienstag, den 15.04.2008, 00:25 +0200 schrieb Alessio Gaeta: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: Thanks, hm could you change gst/gstregistrybinary.c line ~681 to the following?

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-16 Thread Sebastian Dröge
Am Mittwoch, den 16.04.2008, 17:40 +0200 schrieb Alessio Gaeta: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: reassign 475735 gstreamer0.10 found 475735 0.10.18-2 thanks ... Thanks, this helps much. I'll try to debug that in the next days,

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-16 Thread Alessio Gaeta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: Please test that anyway as it might be another bug in gvfs or gio :) I tried to do it, but build fails (it seems that some makefiles calls a registry scan, or something so). the build log in attach (and sorry for the

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-14 Thread Sebastian Dröge
Am Sonntag, den 13.04.2008, 18:15 +0200 schrieb Alessio Gaeta: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: Hm, maybe I found the bug... could you test rebuild gstreamer0.10 with this patch:

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-13 Thread Sebastian Dröge
Am Samstag, den 12.04.2008, 17:48 +0200 schrieb Alessio Gaeta: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: gstreamer0.10-plugins-base Severity: grave I get the error in subject whenever I use a gstreamer application (totem, rhytmbox). It occurs since yesterday, but I do not

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-13 Thread Alessio Gaeta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: Hi, could you run G_DEBUG=fatal_warnings gdb gst-inspect-0.10 and give a backtrace from the time where you get the first abort()? Also, try moving ~/.gstreamer-0.10/registry.i486.bin or similar out of the way and

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-13 Thread Sebastian Dröge
Am Sonntag, den 13.04.2008, 15:38 +0200 schrieb Sebastian Dröge: Am Sonntag, den 13.04.2008, 15:28 +0200 schrieb Alessio Gaeta: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: Hi, could you run G_DEBUG=fatal_warnings gdb gst-inspect-0.10 and

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-13 Thread Sebastian Dröge
Am Sonntag, den 13.04.2008, 15:28 +0200 schrieb Alessio Gaeta: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Dröge ha scritto: Hi, could you run G_DEBUG=fatal_warnings gdb gst-inspect-0.10 and give a backtrace from the time where you get the first abort()? Also,

Bug#475735: [gstreamer0.10-plugins-base] gstreamer fail to initialize with error Error re-scanning registry , child terminated by signal Could not initialize GStreamer

2008-04-12 Thread Alessio Gaeta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: gstreamer0.10-plugins-base Severity: grave I get the error in subject whenever I use a gstreamer application (totem, rhytmbox). It occurs since yesterday, but I do not remember which updates I (actually, update-manager...) made. I tried to