retitle 482717 crashes on non-altivec machines
stop
Sebastian Dröge [EMAIL PROTECTED] writes:
Am Sonntag, den 01.06.2008, 16:53 +0200 schrieb Reinhard Tartler:
Up to now, I was using ffmpeg from debian-multimedia.org but I tried the
one from the debian archive and I get the same result.
Reinhard Tartler schrieb:
Could you please tell me the kernel version of the machine you were
experiencing this? If your kernel is earlier than 2.6.17, I think I know
what is happening here.
Does this
* new patch: 015_dont_provide_img_convert_in_avcodec_h.diff.
Since we build
tag 483960 pending
stop
Fabian Greffrath [EMAIL PROTECTED] writes:
Reinhard Tartler schrieb:
Could you please tell me the kernel version of the machine you were
experiencing this? If your kernel is earlier than 2.6.17, I think I know
what is happening here.
Does this
* new patch:
Reinhard Tartler schrieb:
In the end I think we should disable 005_runtime_cpudetect.diff. It is 2
years old, and its purpose is to fix runtime cpu detection on m68k and
i386. Runtime CPU detection isn't really favored upstream, see
Reinhard Tartler schrieb:
As for FHS compliance, well, since even libc6 is doing this, I'd think
this is okay.
Fine, I am not too literate in linker science. ;)
I'd say we install all variants in a single package and let the dynamic
linker choose the right library.
If the aforementioned is
Fabian Greffrath [EMAIL PROTECTED] writes:
However, a doable solution has been proposed here. lu_zero, the gentoo
ffmpeg maintainer suggested that we should install an altivec disabled
libavcodec in /usr/lib and an altivec enabled version in
/usr/lib/altivec. First very simple tests show the
Sebastian Dröge schrieb:
No, you probably mean another bug :)
Yes, definitely.
I meant #483960. ;)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Am Sonntag, den 01.06.2008, 16:53 +0200 schrieb Reinhard Tartler:
Up to now, I was using ffmpeg from debian-multimedia.org but I tried the
one from the debian archive and I get the same result.
I'm not sure it is a ffmpeg bug since the problem mentions the registry.
Does the crash
Am Montag, den 02.06.2008, 10:13 +0200 schrieb Fabian Greffrath:
Reinhard Tartler schrieb:
Could you please tell me the kernel version of the machine you were
experiencing this? If your kernel is earlier than 2.6.17, I think I know
what is happening here.
Does this
* new patch:
tag 482717 moreinfo
stop
[EMAIL PROTECTED] writes:
Is this on a PPC without altivec? Could you build gstreamer0.10-ffmpeg
with debugging symbols and get a backtrace from
gst-inspect-0.10 --gst-disable-registry-fork
I think this is a ffmpeg bug but let's get a backtrace first :)
Hello,
It
reassign 482717 ffmpeg-free
severity 482717 grave
found 482717 0.svn20080206-7
thanks
Resending, because the second and third line of Sebastian's original
mail were somehow corrupted...
Sebastian Dröge schrieb:
reassign 482717 ffmpeg-free
severity 482717 grave
found 482717 0.svn20080206-7
It happens when initializing the gstreamer ffmpeg plugin... which calls
stuff in ffmpeg. Could you try if you get the same crash when using
ffplay on some movie?
I get Illegal instruction. This is not good at all :(
Regards,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
reassign 482717 ffmpeg-free
severity 482717 grave
found 482717 0.svn20080206-7
Am Donnerstag, den 29.05.2008, 20:00 +0200 schrieb
[EMAIL PROTECTED]:
It happens when initializing the gstreamer ffmpeg plugin... which calls
stuff in ffmpeg. Could you try if you get the same crash when using
Is this on a PPC without altivec? Could you build gstreamer0.10-ffmpeg
with debugging symbols and get a backtrace from
gst-inspect-0.10 --gst-disable-registry-fork
I think this is a ffmpeg bug but let's get a backtrace first :)
Hello,
It is indeed on PPC G3, hence without altivec.
I'm afraid
Am Mittwoch, den 28.05.2008, 21:05 +0200 schrieb [EMAIL PROTECTED]:
Is this on a PPC without altivec? Could you build gstreamer0.10-ffmpeg
with debugging symbols and get a backtrace from
gst-inspect-0.10 --gst-disable-registry-fork
I think this is a ffmpeg bug but let's get a backtrace
Am Samstag, den 24.05.2008, 17:49 +0200 schrieb [EMAIL PROTECTED]:
Package: gstreamer0.10-ffmpeg
Version: 0.10.4-2
Severity: important
Hi,
This version breaks gnome-settings-daemon and al.
Running gnome-settings-daemon in a console gives:
Am Sonntag, den 25.05.2008, 11:34 +0200 schrieb [EMAIL PROTECTED]:
Could you run
GST_DEBUG=5 GST_DEBUG_NO_COLOR=1 gst-inspect-0.10 log
bzip the resulting log file and attach it to this bug? I assume things
also break for you when running gst-inspect-0.10...
Yes, sure. Here is it.
Is
Package: gstreamer0.10-ffmpeg
Version: 0.10.4-2
Severity: important
Hi,
This version breaks gnome-settings-daemon and al.
Running gnome-settings-daemon in a console gives:
[1211642757,000,xklavier.c:xkl_engine_start_listen/]The backend does not
require manual layout management - but it is
18 matches
Mail list logo
