** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/40662800/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/40662801/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/40662802/ArecordDevices.txt
** Attachment added: screenshot - detected only as stereo
http://launchpadlibrarian.net/40663243/Screenshot-Sound%20Preferences.png
--
CM106 usb sound card incorrectly detected as stereo only
https://bugs.launchpad.net/bugs/535476
You received this bug notification because you are a member
** Summary changed:
- USB-Audio CMI106 USB Sound card causes weird errors in the logs
+ USB-Audio CM106 USB Sound card causes weird errors in the logs
--
USB-Audio CM106 USB Sound card causes weird errors in the logs
https://bugs.launchpad.net/bugs/535453
You received this bug notification
** Attachment added: screenshot - correctly detected as surround-capable on my
desktop machine
http://launchpadlibrarian.net/40663520/detected%20as%205.1.png
--
CM106 usb sound card incorrectly detected as stereo only
https://bugs.launchpad.net/bugs/535476
You received this bug notification
No it isn't solved, it hasn't changed at all. Your screenshot
illustrates the same thing as mine (except that mine has version numbers
toggled on).
This bug is about having summary be on top of the package names instead
of the other way around. Currently you see the package names in big bold
I know, I just wanted to make it clear for those stumbling on the bug
report :)
--
package synopsis/tagline/summary should be first, not package name
https://bugs.launchpad.net/bugs/386196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
PIng for the 100 paper cuts? My naïve understanding (IANAD etc.) is that
this would be trivial to fix, maybe even a one-liner.
--
package synopsis/tagline/summary should be first, not package name
https://bugs.launchpad.net/bugs/386196
You received this bug notification because you are a member
*** This bug is a duplicate of bug 436028 ***
https://bugs.launchpad.net/bugs/436028
Public bug reported:
Binary package hint: indicator-session
Clicking on the portrait image in lucid's indicator session applet
brings you to gnome-about-me, allowing you to set your
avatar/image/photo. This
Nope, still reproduceable.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete = New
--
recording volume is randomly reset
https://bugs.launchpad.net/bugs/527866
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Nope, [it is still] reproducible [the problem is still there] (sorry
if my answer was contradictory in its wording). You asked if this could
still be reproduced with the latest *ubuntu11 updates in lucid, right?
If yes, then yes, the bug is still there.
--
recording volume is randomly reset
Public bug reported:
Binary package hint: pulseaudio
As the title says.
This is with pulseaudio 0.9.22 in lucid.
I filed http://pulseaudio.org/ticket/793 upstream about it. It has debug logs,
screencasts, and even a video explaining everything:
http://www.youtube.com/watch?v=T0Irz_EgQr4
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/39782675/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/39782676/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/39782678/ArecordDevices.txt
Bleh, filed bug #527866 instead so that it can start fresh.
--
Gnome should keep the volume settings when disconnecting an USB audio device
https://bugs.launchpad.net/bugs/498550
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm hesitating between option #1 and #3. If you implement #3, it should
not be YES/NO, it should have clear button labels. It could look like
this:
_
| Resume session? X|
Oh, my pretty ascii art :(
--
performance: check for existing files *before* doing the processing on a picture
https://bugs.launchpad.net/bugs/497594
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Seb, this issue is not fixed with the new gnome-media package update.
The volume of the devices are always reset to the base level when
replugging them. And I don't see this issue mentionned in the changelog
in comment #8.
--
Gnome should keep the volume settings when disconnecting an USB audio
Take a look at https://bugzilla.gnome.org/show_bug.cgi?id=607457 for a
thorough explanation of the problem (and that broadcom must fix their
drivers). So network-manager says it's not a bug on their side.
Broadcom's contact form basically autoreplies that they don't care about
end-users, and that
Public bug reported:
Binary package hint: gcc-4.4
gcc -Wall -O2 -g -fomit-frame-pointer -mpreferred-stack-boundary=2
-falign-functions=0 -fno-reorder-blocks -fno-optimize-sibling-calls -I.
-I/home/roy/qemu-0.5.1/target-i386 -I/home/roy/qemu-0.5.1 -D_GNU_SOURCE -c -o
op.o
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39577209/Dependencies.txt
** Attachment added: PreprocessedSource.txt
http://launchpadlibrarian.net/39577210/PreprocessedSource.txt
** Attachment added: XsessionErrors.txt
*** This bug is a duplicate of bug 509092 ***
https://bugs.launchpad.net/bugs/509092
** This bug has been marked a duplicate of bug 509092
Pitivi still needs hal
--
pitivi does not start
https://bugs.launchpad.net/bugs/525419
You received this bug notification because you are a member of
duplicate of bug #509092 or vice versa?
--
pitivi crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/433716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Indeed, my bad for misreading that wikipedia page :)
--
Broken support for AVCHD (MTS/M2TS)
https://bugs.launchpad.net/bugs/327872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Milan, could you tell me what's the status on this? I still don't see
services-admin available in Lucid. It's rather important to have in a
LTS release :)
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Bugs, which
The title and description of this bug is, from what I can tell, wrong.
AVCHD is *not* MPEG-2 TS, and certainly not HDV. Take a look at
http://en.wikipedia.org/wiki/AVCHD ; it's all H.264 AVC there.
Thus the current bug report should be about MPEG-2 Transport Stream
camcorders, because actual
Erik, your .deb package from your PPA solves my problem! If the same
patch is applied in Lucid, then yay!
--
recordmydesktop does not record frames properly in karmic
https://bugs.launchpad.net/bugs/463019
You received this bug notification because you are a member of Ubuntu
Bugs, which is
To stay true to the spirit of this bug report (codec autodetection), I
filed a new bug after some crazy investigation I did today. Indeed, many
codecs are not properly detected. See
https://bugzilla.gnome.org/show_bug.cgi?id=610325 for detailed info.
This also affects totem in a slightly different
Yes, do test with
https://launchpad.net/~gstreamer-developers/+archive/ppa and
https://launchpad.net/~rowinggolfer/+archive/pitivi-unstable (depends on the
gstreamer ppa)
And see if it makes any difference.
--
GStreamer problem playing video
https://bugs.launchpad.net/bugs/508464
You
I added a screencast and debug logs in the upstream bug report, hoping
this will help in figuring out wtf is going on.
--
GStreamer problem playing video
https://bugs.launchpad.net/bugs/508464
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I found a bug report upstream:
https://sourceforge.net/tracker/?func=detailaid=2827013group_id=172357atid=861428
Which points to the redhat bugzilla and theora 1.1 as the cause:
https://bugzilla.redhat.com/show_bug.cgi?id=525155
Now if anyone here could look at this and figure out what's going
Nothing. It's up to Fluendo to fix their codecs. This bug report is here
so that users are aware of it and we can mark bugs as duplicates of
this.
--
Fluendo MP3 and MPEG codecs are not supported
https://bugs.launchpad.net/bugs/503410
You received this bug notification because you are a member
Does it happen only with that particular file? Are you able to provide a
sample video file that causes the problem?
--
pitivi crashed with signal 5 in g_object_unref()
https://bugs.launchpad.net/bugs/515160
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: GNOME Bug Tracker #609426
https://bugzilla.gnome.org/show_bug.cgi?id=609426
** Also affects: pitivi via
https://bugzilla.gnome.org/show_bug.cgi?id=609426
Importance: Unknown
Status: Unknown
--
Missing codecs are not properly detected
wtf @ bugs being made public nearly one year after being reported. This
is on the 0.11.x series, it's unsupported. Marking invalid.
** Changed in: pitivi
Status: New = Invalid
** Changed in: pitivi (Ubuntu)
Status: New = Invalid
--
pitivi crashes or freezes when trying to render
When pitivi 0.13.4 comes out... which I have no idea when it will happen
because there is a lot on the dev's plates and there doesn't seem to be
a clear list of required feature/criteria for determining when we have
reached the required feature set and should make a release.
If the ubuntu
Actually
https://bugzilla.gnome.org/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDproduct=pitiviquery_format=advancedorder=bug_severity,bug_id
--
Razor , an odd name for the split tool
https://bugs.launchpad.net/bugs/506642
You received this bug notification because you are a
That deadline is definitely too close. I'm not a dev but I hang with them
almost every day and run pitivi git. Many issues from 0.13.3 are solved in
the git version. (See
I'll try to chat with at least one of the devs about this before posting to
that mailing list, I'll add that to my todo list.
In the meantime, I would also like to add that gstreamer good/bad/ugly
plugins only get released on february the 23th, if I recall correctly (see:
** Bug watch added: GNOME Bug Tracker #605920
https://bugzilla.gnome.org/show_bug.cgi?id=605920
** Also affects: pitivi via
https://bugzilla.gnome.org/show_bug.cgi?id=605920
Importance: Unknown
Status: Unknown
--
Pitivi still needs hal
https://bugs.launchpad.net/bugs/509092
You
Bug #509092 seems to be a duplicate of this (or the other way around)...
--
Pitivi won't run, complains about missing dbus hal .service file
https://bugs.launchpad.net/bugs/484707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Does this still happen?
** Changed in: pitivi (Ubuntu)
Status: New = Incomplete
--
pitivi crashed with SIGSEGV
https://bugs.launchpad.net/bugs/512092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can't reproduce the problem on my end with PiTiVi git, the gstreamer
packages from the PPA and Ubuntu 9.10.
--
GStreamer encountered a general stream error
https://bugs.launchpad.net/bugs/514887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can you attach a sample video file?
--
GStreamer encountered a general stream error
https://bugs.launchpad.net/bugs/514887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ok, with your provided sample files, I can finally reproduce the
problem. Seeking them in the timeline causes gstreamer errors as
described with pitivi git; I guess this will also need to be tested with
the soon-to-be-released gstreamer packages too (or maybe Ed can try it).
** Changed in: pitivi
** Bug watch added: GNOME Bug Tracker #608064
https://bugzilla.gnome.org/show_bug.cgi?id=608064
** Also affects: pitivi via
https://bugzilla.gnome.org/show_bug.cgi?id=608064
Importance: Unknown
Status: Unknown
--
GStreamer problem playing video
** Changed in: pitivi (Ubuntu)
Status: New = Fix Committed
--
pitivi contextual menu description is not translated in Italian
https://bugs.launchpad.net/bugs/386116
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: pitivi (Ubuntu)
Status: New = Fix Committed
--
pitivi menu description is not translated in Italian
https://bugs.launchpad.net/bugs/386114
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Does it affect only a specific video file?
Does it still occur after logging out of your desktop session and logging back
in, or even a reboot?
--
GStreamer problem playing video
https://bugs.launchpad.net/bugs/508464
You received this bug notification because you are a member of Ubuntu
Bugs,
Can you provide a sample video file?
--
GStreamer problem playing video
https://bugs.launchpad.net/bugs/508464
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Aw man, I'm glad I'm not crazy. I had reported a similar (identical?)
issue back in august, but nobody except me seemed to be experiencing it;
see bug #427520 (which also had its own upstream bug reports on gnome
and pulseaudio)
--
Gnome should keep the volume settings when disconnecting an USB
This has been re-filed by Lennart in upstream gnome as
https://bugzilla.gnome.org/show_bug.cgi?id=606914
** Bug watch added: GNOME Bug Tracker #606914
https://bugzilla.gnome.org/show_bug.cgi?id=606914
--
Gnome should keep the volume settings when disconnecting an USB audio device
** Changed in: pitivi (Ubuntu)
Status: Incomplete = Fix Committed
--
pitivi crashed with TypeError in _unblockPad()
https://bugs.launchpad.net/bugs/508755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Chris, any progress or further upstream discussions on finding what
causes this?
I'm still experiencing issues with my netbook randomly not being able to
go idle (and thus, no screen dimming, dpms off, or auto suspend...). I
couldn't pinpoint the cause, it usually works the first few times after
Actually, I'm thinking this is not compiz-specific (because it also
happens with mutter), and that this is a duplicate of bug #414240 ...
please check?
--
[i915gm] [Karmic] X freezes when using compiz on external monitor
https://bugs.launchpad.net/bugs/441873
You received this bug notification
Strange, I'm running ubuntu 9.10 with pulseaudio and pitivi git (and the
gstreamer-developers PPA), and never experienced this issue...
--
GStreamer problem playing video
https://bugs.launchpad.net/bugs/508464
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm thinking this is a duplicate of bug #505509
--
pitivi crashed with AssertionError in __init__()
https://bugs.launchpad.net/bugs/429941
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Okay, I think there's a bunch of new bugs being filed on pitivi on
launchpad due to ubuntu pulling out HAL (that's not even considering the
bunch of bugs of people who can't import MPEG2-TS files)...
I can't triage them all alone, especially the HAL bugs, because I lack
the expertise to figure
Hmmm. Well pitivi is already *supposed* to detect and prompt for missing
codecs, but it seems that it works incorrectly then.
** Summary changed:
- MPEG-2 Transport Stream files (.mts or .m2ts) support
+ Missing codecs are not properly detected
--
Missing codecs are not properly detected
Ok, it was just me misunderstanding what happened then, because there's
a bunch of bug reports on launchpad I can do nothing about, I don't know
what is causing them exactly. There's a bunch of them that seem somewhat
similar but not quite, and they pretty much all lack sample files/repro
You need to be more specific. Please attach the exact file that causes
the problem.
I tried with the ogv, oga and spx files in /usr/share/example-content,
in pitivi 0.13.3 an error pops up, but in pitivi git they all seem to
work... only a notification: Invalid mode encountered. The stream is
No problem here on Ubuntu 9.10. Do you have python-gst0.10 installed?
In a terminal, run python
Then enter the following two lines at the prompts:
import pygst
pygst.require('0.10')
On my end, it doesn't spit any errors.
** Changed in: pitivi (Ubuntu)
Status: New = Incomplete
--
No, this is something you need to contact the translation teams about...
Packagers don't do the translations.
http://l10n.gnome.org/teams/it
** Changed in: pitivi (Ubuntu)
Status: New = Invalid
--
pitivi contextual menu description is not translated in Italian
Both are translation issues that you should report to the translation
team at http://l10n.gnome.org/teams/it
** Changed in: pitivi (Ubuntu)
Status: New = Invalid
--
pitivi menu description is not translated in Italian
https://bugs.launchpad.net/bugs/386114
You received this bug
Hi, please provide the ogv file that causes the problem.
** Changed in: pitivi (Ubuntu)
Status: New = Incomplete
--
pitivi crashed with AttributeError in debug()
https://bugs.launchpad.net/bugs/435420
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm thinking this is specific to Ubuntu 10.04 and related to gir... but
Ed or ubuntu devs should probably comment on this.
--
pitivi crashed with ImportError in filter()
https://bugs.launchpad.net/bugs/507259
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have tested with a Sony HDR-XR200 camcorder today, which produces .mts
files. I suspected that this is the currently released gstreamer
versions don't support MPEG2-TS yet. Not sure what the status of this
is, and there's no bug open on PiTiVi (because it's a gstreamer issue,
not really pitivi).
** Changed in: pitivi (Ubuntu)
Status: Incomplete = Invalid
--
cannot play movie with pitivi
https://bugs.launchpad.net/bugs/399973
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Do you have the fluendo mp3/mpeg codecs installed, by any chance?
--
pitivi should ask the user to install missing codecs
https://bugs.launchpad.net/bugs/505509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This is already fixed in the git version of pitivi; it is a Split tool
now, and it is modeless. See also http://jeff.ecchi.ca/blog/2009/11/30
/move-playhead-on-click-modeless-splitting-full-height-playhead/
** Changed in: pitivi (Ubuntu)
Status: New = Fix Committed
--
Razor , an odd name
Although if the scissors icon is not the best metaphor for Split, I'm
sure better icons would be welcome. I'm not as good as some tango
artists/pixel pushers out there.
--
Razor , an odd name for the cut/crop tool
https://bugs.launchpad.net/bugs/506642
You received this bug notification because
Do you have a sample file you could provide so I can test on my end?
--
pitivi should ask the user to install missing codecs
https://bugs.launchpad.net/bugs/505509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: pitivi (Ubuntu)
Status: New = Confirmed
** Bug watch added: GNOME Bug Tracker #593663
https://bugzilla.gnome.org/show_bug.cgi?id=593663
** Also affects: pitivi via
https://bugzilla.gnome.org/show_bug.cgi?id=593663
Importance: Unknown
Status: Unknown
--
We suspect that this issue has been fixed in the development version of
PiTiVi. If you can provide the project and files used in this project,
however, it could be possible to test if that's indeed the case.
** Changed in: pitivi (Ubuntu)
Status: Incomplete = Fix Committed
--
[karmic]
Hi, this sounds a lot like https://bugzilla.gnome.org/show_bug.cgi?id=603102
Many users have experienced a problem where rendering did not behave correctly
when you loaded a PiTiVi project and tried to render directly, without seeking
(moving the playhead) in the timeline first. That issue has
Martin, I just subscribed to the ubuntu bug reports for PiTiVi, as it
seems that there was a huge unseen pile of bug reports, most of which
are on obsolete releases. It seems there was not much bug triaging going
on, so I will attempt to fill that role (as time permits). I'll start by
attempting a
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
** Changed in: pitivi (Ubuntu)
Status: Incomplete = Invalid
--
pitivi crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/410094
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
The version of PiTiVi you are using is not the latest version, and the
PiTiVi devs can only afford to investigate bugs that are reproducible on
the latest PiTiVi release or the development (git) version. Your problem
may have been fixed in either of those versions, and, as such, will be
marked as
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
The PiTiVi devs can only afford to investigate bugs that are
reproducible on the latest PiTiVi release or the development (git)
version. Your problem may have been fixed in either of those versions,
and, as such, will be marked as obsolete. If you can still reproduce
this problem on these
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Is this reproducible on the latest PiTiVi release or the development
version? If yes, you should file a bug upstream (see
http://www.pitivi.org/?go=bugs) and link it to this bug report.
In particular, this bug might have been fixed in the development version
(if I remember correctly).
** Changed
Is this reproducible on the latest PiTiVi release or the development
version? If yes, you should file a bug upstream (see
http://www.pitivi.org/?go=bugs) and link it to this bug report.
** Changed in: pitivi (Ubuntu)
Status: New = Incomplete
--
[hardy] Hangs when appending clip
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Is this reproducible on the latest PiTiVi release or the development
version? If yes, you should file a bug upstream (see
http://www.pitivi.org/?go=bugs) and link it to this bug report.
** Changed in: pitivi (Ubuntu)
Status: New = Incomplete
--
cannot play movie with pitivi
Is this reproducible on the latest PiTiVi release or the development
version? If yes, you should file a bug upstream (see
http://www.pitivi.org/?go=bugs) and link it to this bug report.
In particular, this sounds a lot more like a driver problem instead of a
pitivi bug.
** Changed in: pitivi
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
Thanks for reporting this bug. The version of PiTiVi you are using is
not the latest version, and the PiTiVi devs can only afford to
investigate bugs that are reproducible on the latest PiTiVi release or
the development (git) version. Your problem may have been fixed in
either of those versions,
601 - 700 of 1231 matches
Mail list logo