Hi All,
I was following the information found at <
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg >
and have hit into 2 snags. Snag one is that the url <
http://dev-downloads.libreoffice.org/symstore/symbols > gives a 4.3 and
snag two is that when i'm running the analyze co
>
> Do you know how playback is implemented on windows as i wanted to do
> testing on it. Someone mentioned that if i plays in windows media
> player, then it should play in impress, but unfortunately that is not
> the case.
>
> I plan to set up a wiki page with Joel's help to provide details of
Le 03/06/2014 13:24, Caolán McNamara a écrit :
I carried out more comprehensive testing on OSX 10.9 with several
different video container formats over the various releases of LO, and
posted the results here :
fdo 79546
On my OSX 10.9.3 system, I have :
Quicktime Player 10.3 (727.4)
Flip Pla
On 06/03/2014 03:24 PM, Caolán McNamara wrote:
> For Linux, we're using gstreamer under Linux to play back video, so I
> suggest if there's an issue playing back video under Linux that the
> reporter checks if it works in totem which typically defaults to having
> gstreamer as its backend. So as a
The few movie files I have on my Mac are taken with my Canon DSLR,
named *.mov, encoded in H.264 I think, and open with "QuickTime
Player". One of those files was the one I successfully inserted in a
Writer doc when I tested the recent Mac patches to avmedia.
--tml
> For MacOSX I wonder if Tor knows of a basic/built-in video viewer on
> MacOSX which uses the same route we are using to render video which can
> be used as an example program to compare against to filter out missing
> codecs vs libreoffice-side bustate ?
No idea. I would just double-click on the
On Sat, 2014-05-31 at 11:17 -0700, Joel Madero wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=56847
>
> So QA has some questions:
> 1. Should we close this particular bug as INVALID because it's a
> disaster with comments and lots of different issues being posted?
Its got 67 comments in it
Excellent idea! Sorting by priority and separating by OS does speed up
selecting where to start.
Well done!
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Suggested-Triage-Order-tp435p4111205.html
Sent from the QA mailing list archive at Nabble.com.
__
Hi,
On Tue, Jun 03, 2014 at 01:42:52PM +0800, ANiKET JAiN wrote:
> Hi,
>
> Various bugs identified in LibreOffice are listed at
> "https://bugs.freedesktop.org"; with specific id's. I want to map those bugs
> to specific commits, so that i can know which files were changed because of
> that b
Hi,
Various bugs identified in LibreOffice are listed at
"https://bugs.freedesktop.org"; with specific id's. I want to map those bugs to
specific commits, so that i can know which files were changed because of that
bug. Usually, developers specify those bug id's during the comment of a commit,
10 matches
Mail list logo
