*** This bug is a duplicate of bug 1263278 ***
https://bugs.launchpad.net/bugs/1263278
** This bug has been marked a duplicate of bug 1263278
Use FFmpeg instead of Libav
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libav in U
** Changed in: inkscape (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/977003
Title:
ink
correction: fixed in experimental rev 13413, trunk rev 13444
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/977003
Title:
inkscape crashe
** Branch linked: lp:inkscape
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/977003
Title:
inkscape crashed with SIGSEGV in Avoid::VertIn
fixed in rev. 13413
because of constructor "ConnRef(Router *router, const unsigned int id)",
_srcVert and _dstVert can be NULL, and _active can be false. this
constructor seems unfinished, but is used elsewhere in the code. hence
the crash.
** Changed in: inkscape
Status: Triaged => Fix Co
** Branch linked: lp:inkscape/experimental
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/977003
Title:
inkscape crashed with SIGSEGV in
how to reproduce in trunk?
** Changed in: inkscape
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1275164
"wait for it to start destroying objects."
wait for it before starting to destroy objects.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/96
So to fix this, the exit procedure should be able to figure out if some
threads are running in the background (the saving thread), and wait for
it to start destroying objects.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in
It depends on quick timing. When saving the document, control returns to
the GUI before the save is complete. If inkscape is closed in that
period: crash.
It seems a ton of crashes can happen when the save is still happening
while inkscape is closed. The code is not at all ready for
multithreading
I just tried now with Audacity HEAD built with system libsbsms 2.0.1-1
on Ubuntu 14.04, and there is no crash.
However I could not reproduce the bug in Audacity HEAD built with system
libsbsms 2.0.1-1 on Ubuntu 13.10, until I installed the 2.0.3 package
of Audacity. The 2.0.3 package crashed eve
Guys,
I've already done this:
https://bugzilla.libav.org/show_bug.cgi?id=700
There are several more similar (maybe duplicate) bugs reported, and
still open.
That's why I propose to theck which of both, ffmpeg and avconv, is more
stable and reliable.
** Bug watch added: bugzilla.libav.org #70
What about getting in touch with the Libav developers to get libav
fixed so that they can process your videos?
On Sun, Jun 29, 2014 at 12:12 PM, Hadmut Danisch wrote:
> Well, the fact is, avconv doesn't work for several of my videos, whereas
> ffmpeg worked at least for the test samples I've give
Yes but you provided no details about exactly what you're trying to do
that is not working, no cli output, just a vague "it won't work" type
statement, and then submit a bug with a title that is 100% politics. How
seriously is anyone supposed to take that.
--
You received this bug notification be
Well, the fact is, avconv doesn't work for several of my videos, whereas
ffmpeg worked at least for the test samples I've given someone to test.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libav in Ubuntu.
Matching subscriptions: Ub
I reported this upstream (gnome) and attached a patch there. I think (but I'm
not 100% sure) that is the best way to handle this.
https://bugzilla.gnome.org/show_bug.cgi?id=732432
-Joe
** Bug watch added: GNOME Bug Tracker #732432
https://bugzilla.gnome.org/show_bug.cgi?id=732432
--
You rec
It's a good thing the ffmpeg developers are an unbiased source of
information about bugs in libav.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to libav in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bu
Public bug reported:
Hi,
I currently have the problem that I have around 2 dozens of video (still
counting) that can't be converted with avconv because of a bug in
avconv, causing it to abort. I have been informed by ffmpeg people that
avconv currently contains several hundred of open bugs that
** Changed in: gtk-recordmydesktop
Status: New => Confirmed
** Changed in: qt-recordmydesktop
Status: New => Confirmed
** Changed in: recordmydesktop (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, whic
** Description changed:
This current version has some serious issue since it was based off of the
Master branch rather than the Stable branch.
The problems relate to unstable plugins, and features that were not ready for
production.
Since Tursty is an LTS, only stable mature software shou
** Changed in: shotwell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to shotwell in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1335600
Title:
Publishing
** Description changed:
The flickr api went to https only on June 27th 2014. It appears the
shotwell is still using http so "publishing" to flickr no longer works.
https://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-
27th-2014/
Problem appears to be present in:
Public bug reported:
The flickr api went to https only on June 27th 2014. It appears the
shotwell is still using http so "publishing" to flickr no longer works.
https://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-
27th-2014/
Problem appears to be present in:
Shotwell 0.15.0-0ub
I ran into this problem on Ubuntu 14.04 64 bit. The method from pos 14
initially did not work for me, but setting PULSE_LATENCY_MSEC=1 using
the same command did the trick. I also tried the method from post 21
first, which, unfortunately, did not work for me.
--
You received this bug notification
24 matches
Mail list logo
