This is surely a bug in gstreamer. Pitivi can't open such videos either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/993937
Title:
Totem can't play some FLV videos encoded by H.264
Apparently upstream this is fixed in 3.6.1 maintenance release. Can this
be built and released in Ubuntu main?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1055497
Title:
This bug is because of kernel upstream bug
https://bugzilla.kernel.org/show_bug.cgi?id=52471
All the info is in that bug report, including 2 patches to fix it.
In short form, the (doomed to fail by timeout) battery status reporting
injects a 5 second delay in keyboard device removal. Due to
Libreoffice 3.5.3 (recently in the Ubuntu Precise repos) fixes this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/545346
Title:
[upstream] [3.3] Sound is Duplicated and
I have this problem too, but my totem depends on gstreamer1.0, not 0.10.
Could the problem be upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=688803
apparently fixed, though I don't think the code has trickled into the ubuntu
repos
** Bug watch added: GNOME Bug Tracker #688803
Installing version 1.2.2 of gstreamer1.0-plugings-ugly in saucy (by
using the latest package from Trusty archive) fixes the problem on my
system
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
My (32 bit) system is showing the same behaviour, and totem gives the
following error message each time:
** (totem:7505): CRITICAL **: gst_video_decoder_allocate_output_frame:
assertion 'frame-output_buffer == NULL' failed
A quick trawl on upstream gstreamer lead me to:
Hi Ablenzo
Its highly unorthodox as a method ... but in this case it gets us out of
a hole.
- Use packages.ubuntu.com to find the gstreamer1.0-plugins-ugly package from
the Trusty series
- From that page, 'Downloads' section near the bottom, you can click on 'i386'
or 'amd64' link (depending
Public bug reported:
In evolution, open a message which opens a 'message reader' window.
In that window press the 'Reply' button - this opens a new 'message
composer' window in which to type the reply
In 17.10 running under gnome-shell, the composer window is opened, but
it also seems that the
Yep - I'm on Ubuntu 18.04 using gnome-shell/wayland 3.28 and confirm it
is now working okay
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1732454
Title:
Reply to message composer
Okay - your print defaults are to 'print to ps' rather than 'print to
pdf'.
So to recreate the steps you can either:
a) Go to Tools -> Options -> Print -> and enable 'PDF as standard print
job format, then re-run the steps
OR
b) wherever in my steps I say 'pdf' or filename.pdf, change to 'ps'
Right - I have managed to force over my libreoffice to using ps (uncheck
the 'PDF as standard print job format' option, click Okay, and let lo
restart).
When in 'PS' mode, you are correct that the bug as I have described does not
manifest. I conclude that it only manifests when in 'PDF' mode.
Hmmm - somewhat curious that your setup is locked into ps and mine is
pdf with no apparent way of switching.
But in step 6-c it is important to click on a file name in the chooser,
and then edit it in the type in field. The bug doesn't manifest if you
just edit the name type in field to the
>I think the bug happens when the dialogue self-flips the type selector
to 'Portable Document Format'.
Yep ... if I manually flip the type selector to 'Portable Document
Format' it loses my desired file name and pseudo-randomly selects a pdf
file from the list of files in the folder.
So there
This screenshot manages to show the problem.
Here I have typed in the 'Name' field 'test_2.pdf' when I already have
that filename in my folder (as well as the dummy sample.pdf). I then
press Enter, expecting to get the confirmation dialogue box asking about
overwriting the file.
The confirmation
Public bug reported:
This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3
installed).
Under certain conditions print to file over-writes an existing pdf file
in the chosen folder which doesn't match the name chosen by the user
(and without any warning or confirmation dialog).
Submitted upstream:
https://bugs.documentfoundation.org/show_bug.cgi?id=122075
** Bug watch added: Document Foundation Bugzilla #122075
https://bugs.documentfoundation.org/show_bug.cgi?id=122075
--
You received this bug notification because you are a member of Desktop
Packages, which is
17 matches
Mail list logo
