Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12872 - ekiga crash (don't start) after updating x264 to 20090108-1 version

Attached to Project: Arch Linux
Opened by Maxime de Roucy (akira86) - Wednesday, 21 January 2009, 03:38 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 31 January 2009, 05:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Eric Belanger (Snowman)
Aaron Griffin (phrakture)
Architecture x86_64
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After I update my system, I found that ekiga didn't start anymore.
ekiga crashed by a seg-fault.
I solve the problem by changing x264 by x264-git so it is sure that it is x264 the problem.

But, as I said, I already solve the problem. So I can't produce a trace anymore.

However, when I can produce a the crash, logs didn't show anything.

uname -a
Linux max-laptop2 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 18 19:41:52 UTC 2009 x86_64 AMD Athlon Dual-Core QL-60 AuthenticAMD GNU/Linux

the package version : 20090108-1
the package I install to solve the problem x264-git 20090108-1

forum discussion on that problem :
http://bbs.archlinux.org/viewtopic.php?pid=484143#p484143
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 31 January 2009, 05:44 GMT
Reason for closing:  Fixed
Comment by Eric Belanger (Snowman) - Wednesday, 21 January 2009, 06:41 GMT
I guess there's a problem with the snapshot I used for the x264 package. I'll try updating it to a newer one. BTW, what's the build date of your x264-git package?
Comment by Eric Belanger (Snowman) - Wednesday, 21 January 2009, 07:06 GMT
Maxime: Nevermind my question about the build date of your x264-git package. I'll just use the latest snapshot.

Aaron: should the update go straight in extra (hoping it won't introduce new problems) or in testing first?
Comment by Eric Belanger (Snowman) - Wednesday, 21 January 2009, 08:38 GMT
FTR: the seg fault only happens on x86_64.

To fix it, we need to use at least the 20090120 snapshot. Anything older (I haven't tested them all) gives the seg fault. The main problem is that 20090120 introduce a soname bump so we need to do a x264 rebuild again *sigh*. It'll probably be smaller than the last one as it also had a ffmpeg soname bump. I don't have time to do it before the end of this month. I could come up with the list of necessary rebuild and ask for a volunteer on the ML (unless you want to do it).


Just to be sure that the rebuild is needed - Maxime : Could you post here the output of 'pacman -Ql x264-git' ?
Comment by Maxime de Roucy (akira86) - Wednesday, 21 January 2009, 16:25 GMT
I found a new bug related to that update ... but I am not sure it's due to x264 package and I didn't find anyone with this problem, so maybe it is my config.

miro didn't display video anymore with the x264-git package and crash after each video with the x264 package. If someone could try miro with new x264 to undermind or confirm this problem...

% pacman -Ql 264-git
x264-git /usr/
x264-git /usr/bin/
x264-git /usr/bin/x264
x264-git /usr/include/
x264-git /usr/include/x264.h
x264-git /usr/lib/
x264-git /usr/lib/libx264.a
x264-git /usr/lib/libx264.so
x264-git /usr/lib/libx264.so.66
x264-git /usr/lib/pkgconfig/
x264-git /usr/lib/pkgconfig/x264.pc
Comment by Eric Belanger (Snowman) - Wednesday, 21 January 2009, 18:00 GMT
As you can see, your x264-git packages provides /usr/lib/libx264.so.66 while the x264 package in extra provides /usr/lib/libx264.so.65. So all package that depends on x264 (and perhaps ffmpeg) will need to be rebuild. To fix miro, try rebuilding ffmpeg and maybe xine-lib. let me know if that work.
Comment by Maxime de Roucy (akira86) - Wednesday, 21 January 2009, 20:20 GMT
I tried to rebuild ffmpeg and it make ekiga crash...
Comment by Eric Belanger (Snowman) - Wednesday, 21 January 2009, 20:38 GMT
Perhaps we'll also need to update ffmpeg. Try with ffmpeg-svn.
Comment by Maxime de Roucy (akira86) - Wednesday, 21 January 2009, 21:24 GMT
I just tried ffmpeg-svn and the crash problem of ekiga reappear.

but namcap tell me that when I finished to build ffmpeg-svn :

ffmpeg-svn E: Dependency detected and not included (ffmpeg) from files ['usr/lib/libavformat.so.52.25.0', 'usr/lib/libpostproc.so', 'usr/lib/libavdevice.so', 'usr/bin/ffplay', 'usr/lib/libavcodec.so.52', 'usr/bin/ffserver', 'usr/lib/libavdevice.so.52', 'usr/lib/libavformat.so', 'usr/lib/libswscale.so', 'usr/lib/libavcodec.so', 'usr/lib/libavcodec.so.52.11.0', 'usr/lib/libswscale.so.0.6.1', 'usr/lib/libswscale.so.0', 'usr/bin/ffmpeg', 'usr/lib/libavformat.so.52', 'usr/lib/libpostproc.so.51', 'usr/lib/libavdevice.so.52.1.0', 'usr/lib/libpostproc.so.51.2.0']
ffmpeg-svn W: Dependency included but already satisfied (lame)
ffmpeg-svn W: Dependency included but already satisfied (sdl)
ffmpeg-svn W: Dependency included but already satisfied (libvorbis)
ffmpeg-svn W: Dependency included but already satisfied (faad2)
ffmpeg-svn W: Dependency included but already satisfied (faac)
ffmpeg-svn W: Dependency included but already satisfied (xvidcore)
ffmpeg-svn W: Dependency included but already satisfied (zlib)
ffmpeg-svn W: Dependency included but already satisfied (imlib2)
ffmpeg-svn W: Dependency included but already satisfied (libtheora)
Comment by Eric Belanger (Snowman) - Wednesday, 21 January 2009, 21:33 GMT
you mean that ekiga crashes when you use both ffmpeg-svn and x264-git ? And you built ffmpeg-svn with x264-git installed, right?

Don't worry about namcap. It's normal. You still have ffmpeg on your system which confuse it a bit.
Comment by Maxime de Roucy (akira86) - Wednesday, 21 January 2009, 21:46 GMT
"you mean that ekiga crashes when you use both ffmpeg-svn and x264-git ? And you built ffmpeg-svn with x264-git installed, right?"

Yes, to summarize, ekiga crash when :
ffmpeg and x264 are used
ffmpeg(recompile with x264-git) and x264-git are used
ffmpeg-svn and x264-git are used

but it works when :
ffmpeg and x264-git are used
Comment by jim downes (milltek) - Saturday, 24 January 2009, 02:30 GMT
Is there a fix coming for this x264 issue? Ever since it happened I can't watch any video over the web. (CNN and Youtube for example).
Comment by Maxime de Roucy (akira86) - Saturday, 24 January 2009, 03:22 GMT
I came back to x264 instead of x264-git because of mplayer problem.

So I can't use ekiga anymore (but I can watch video on the web).

But it permit to me to generate a trace... maybe it will help.

I did it by the command-line :
strace -otrace ekiga
   trace (147.2 KiB)
Comment by Maxime de Roucy (akira86) - Tuesday, 27 January 2009, 05:54 GMT
it seems that ekiga don't crash with x264-git because ekiga is compiled to look for /usr/lib/libx264.so.65 but only /usr/lib/libx264.so.66 exist with x264-git.
so it made an error ... but don't crash ...

with x264 ekiga find libx264.so.65 use it ... and crash.

I made a new trace of ekiga but, this time with x264-git ... this trace is an example of what happen when ekiga work well.
   traceOK (1.44 MiB)
Comment by Eric Belanger (Snowman) - Saturday, 31 January 2009, 02:21 GMT
status update: I've started looking into it.
Comment by Eric Belanger (Snowman) - Saturday, 31 January 2009, 05:39 GMT
I figured it out. The problem was with opal. I rebuilt it (only for x86_64) and ekiga starts fine now.

Miro works fine. I guess the problem was caused because the x264-git had a soname bump and you didn't rebuilt one of miro's dependency. If miro doesn't work, open another bug report.

Loading...