I have installed x86 binary:
http://launchpadlibrarian.net/154931008/libx264-123_0.123.2189%2Bgit35cf912-1ubuntu1.1_i386.deb
and I am fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
This bug was fixed in the package x264 -
2:0.123.2189+git35cf912-1ubuntu1.1
---
x264 (2:0.123.2189+git35cf912-1ubuntu1.1) saucy-proposed; urgency=low
* Compile using -fno-aggressive-loop-optimizations to work around
segfault caused by changes in gcc 4.8 (LP: #1241772).
--
Fixed for me too... Maarten, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
To manage notifications about this bug
Just activated the -proposed updates and installed them. Everything
works fine, as it did with Maarten Baert's ppa, and I'm seeing no
regressions at all so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The proposed package resolves this bug for me as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
fixed for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
To manage notifications about this bug go to:
proposed sources with apt-get are also working for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
To manage notifications
libx264-123 from saucy-proposed fixed the bug for me as well. It is not
yet in the main saucy repository where the segfault still happens. What
does it take to move the package over from proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It needs a week in -proposed for regression testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
To manage notifications
I tried following the directions in the EnableProposed link, but the
aptitude program complains there are no packages for saucy-proposed.
Using apt-get specifically worked, though? At any rate, I finally got
it installed and no more segfault.
--
You received this bug notification because you
I can confirm that Maarten Baert's ppa has resolved my problems with
avconv on the command-line. Tnx dude!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8
Hello Alex, or anyone else affected,
Accepted x264 into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/x264/2:0.123.2189+git35cf912-1ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/saucy-proposed/x264
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
To manage notifications about
This bug was fixed in the package x264 -
2:0.123.2189+git35cf912-1ubuntu2
---
x264 (2:0.123.2189+git35cf912-1ubuntu2) trusty; urgency=low
* Compile using -fno-aggressive-loop-optimizations to work around
segfault caused by changes in gcc 4.8 (LP: #1241772).
-- Andrew
I can confirm that Maarten Baert's ppa has resolved the issue I was
having with x264 on 13.10. Kazam works fine now and mp4 playback is also
working. I have had no negative side-effects so far, but I'll be sure to
report back if I find any problems.
--
You received this bug notification because
** Also affects: x264 (Ubuntu Saucy)
Importance: Undecided
Status: New
** Changed in: x264 (Ubuntu Saucy)
Status: New = Triaged
** Changed in: x264 (Ubuntu Saucy)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Andrew Starr-Bochicchio has pointed out that his bug also affects kazam:
https://bugs.launchpad.net/ubuntu/+source/kazam/+bug/1241924
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
** Changed in: x264 (Ubuntu)
Status: Triaged = In Progress
** Changed in: x264 (Ubuntu)
Assignee: (unassigned) = Andrew Starr-Bochicchio (andrewsomething)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: x264 (Ubuntu Saucy)
Status: Triaged = In Progress
** Changed in: x264 (Ubuntu Saucy)
Assignee: (unassigned) = Andrew Starr-Bochicchio (andrewsomething)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
+ * A segfault in libx264-123 has caused major regressions in vlc, kazam,
+ avidemux, and avconv among others. Nearly any program that encodes video
+ in H264 is probably affected.
+
+ [Test Case]
+
+ * As this impacts many
** Patch added: saucy-sru.debdiff
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1241772/+attachment/3887704/+files/saucy-sru.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/x264/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
To
In light of this being an SRU candidate for 13.10, I recommend we simply
compile using -fno-aggressive-loop-optimizations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
@Doug: x264 can't be updated without recompiling or even updating libav
as well, AFAIK.
I've added a patched version of x264 to my PPA:
https://launchpad.net/~maarten-baert/+archive/simplescreenrecorder
Normally I wouldn't mess with official packages, but since the official one is
completely
Maarten: Do you have a pointer to some discussion about that patch? Is
this really a gcc optimisation bug or is vlc doing something that's not
legal/safe but didn't happen to trigger on older gcc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This affects vlc, avidemux, and command line use of avconv. All produce
segfaults on my 64-bit Kubuntu 13.10 upgraded computer. It affects all
ways in which avconv uses libx264.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I couldn't find any info either. As far as I understand, x264 was doing
something that wasn't standard-compliant (array overreads), and the GCC
optimization aggressive-loop-optimizations relies on the assumption that
all code is standard-compliant. So this is not a GCC bug.
It may be possible to
Triaged: Upstream fix found
High: Affecting multiple common packages making them unusable.
** Changed in: x264 (Ubuntu)
Importance: Undecided = High
** Changed in: x264 (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The attachment Upstream patch (backported) seems to be a patch. If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Rebuilding the libx264-123_0.123.2189+git35cf912-1ubuntu2 packages with
-fno-aggressive-loop-optimizations indeed solves the problem on 13.10,
there is no more segfault:
https://www.dropbox.com/sh/0o1bi2vzmp5p11o/vBzFd8nCgx
--
You received this bug notification because you are a member of Ubuntu
I can confirm both the problem and the workaround (--extra-cflags=-fno-
aggressive-loop-optimizations) as well, after testing on 13.10 (64-bit)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
On 10/19/2013 10:13 PM, 3vi1 wrote:
I can confirm both the problem and the workaround (--extra-cflags=-fno-
aggressive-loop-optimizations) as well, after testing on 13.10 (64-bit)
You all could also just use a newer version of x264, the current is a
bit stale, from late april 2013
(same goes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: x264 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241772
Title:
I can confirm this. It affects anything that uses libx264, not just VLC
but also avconv (the command line tool) and any program that encodes
video with libavcodec (i.e. most video editors and screencasting
software).
The backtrace in avconv is mostly the same:
#0 __memcmp_ssse3 () at
34 matches
Mail list logo
