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,
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.
--
pitivi should be able to ignore unknown streams
https://bugs.launchpad.net/bugs/305731
You received this
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,
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,
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.
** Changed in: pitivi (Ubuntu)
Status: New = Incomplete
--
pitivi crashed with RuntimeError in
Marking it as obsolete then, as it's on an old release anyway.
** Changed in: pitivi (Ubuntu)
Status: New = Invalid
--
pitivi crashed with PipelineError in _getFactoryEntryForStream()
https://bugs.launchpad.net/bugs/410683
You received this bug notification because you are a member of
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
--
pitivi crashed with signal 7
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
--
[ubuntu karmic] pitivi does not start
*** This bug is a duplicate of bug 438366 ***
https://bugs.launchpad.net/bugs/438366
** This bug has been marked a duplicate of bug 438366
software-center crashed with AttributeError: 'module' object has no
attribute 'Element'
** Changed in: pitivi (Ubuntu)
Status: New = Invalid
** Changed in: pitivi (Ubuntu)
Status: New = Invalid
** Changed in: pitivi (Ubuntu)
Status: Invalid = Incomplete
--
pitivi should be able to ignore unknown streams
https://bugs.launchpad.net/bugs/305731
You received this bug notification because you are a member of Ubuntu
Bugs,
P.s.: if you can provide a sample file to test with, it would be nice to
make sure it really is fixed with the git version.
--
Failed to retrieve channel layout from caps
https://bugs.launchpad.net/bugs/500499
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is a bug in the bad plugins, which is supposedly fixed in the dev
version.
** Package changed: pitivi (Ubuntu) = gst-plugins-bad0.10 (Ubuntu)
** Changed in: gst-plugins-bad0.10 (Ubuntu)
Status: New = Fix Committed
--
Failed to retrieve channel layout from caps
Public bug reported:
Binary package hint: pitivi
Taken from the PiTiVi user manual:
Some GStreamer codecs, such as the Fluendo MP3 and MPEG muxers, while
providing you with a legal way to playback files (in countries where software
patents laws are upheld), may not be completely compliant to
*** This bug is a duplicate of bug 503410 ***
https://bugs.launchpad.net/bugs/503410
** This bug is no longer a duplicate of bug 212661
pitivi crashed with TypeError in warn_explicit() when importing mpeg file
with fluendo codecs
** This bug has been marked a duplicate of bug 503410
*** This bug is a duplicate of bug 503410 ***
https://bugs.launchpad.net/bugs/503410
Fluendo codecs won't work with PiTiVi, this is an issue we can do
nothing about until they fix their codecs. See the PiTiVi user manual or
bug #503410 for more information.
** This bug has been marked a
*** This bug is a duplicate of bug 503410 ***
https://bugs.launchpad.net/bugs/503410
Fluendo codecs won't work with PiTiVi, this is an issue we can do
nothing about until they fix their codecs. See the PiTiVi user manual or
bug #503410 for more information.
** This bug has been marked a
Well if you can indeed reproduce the bug with the latest versions, and
provide more debugging info, then yes... but it may be complex to debug
(and be a driver, xorg or gtk issue).
--
Openoffice+Pitivi=complete Xorg Crash!
https://bugs.launchpad.net/bugs/344138
You received this bug notification
** Changed in: pitivi (Ubuntu)
Status: Incomplete = Invalid
--
[ubuntu karmic] pitivi does not start
https://bugs.launchpad.net/bugs/401846
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: phatch
Currently, if you uncheck the Overwrite existing images option, phatch
still processes the image before trying to check if it should be saved
or not.
I know this is not easy to fix, but ideally, when I have a thousand
images to process and launch
Public bug reported:
Binary package hint: istanbul
The current 0.2.2 version of istanbul in ubuntu is beyond useless. It
doesn't work because it's bitrotten (it's 2-4 years old!). Clicking the
record button causes a traceback, and clicking the stop button causes
another traceback!
I have heard
I located the problem with the commandline recordmydesktop tool: for
this to work correctly, I *need* to specify the -v_bitrate parameter.
Without it, with any parameter combination, I get the laggy output.
--
recordmydesktop does not record frames properly in karmic
Also happens if using gnome-shell, the wallpaper is then replaced by a
solid blue.
--
fails to display wallpaper image (root window is all white)
https://bugs.launchpad.net/bugs/477567
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35319324/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35319325/XsessionErrors.txt
** Bug watch added: Debian Bug tracker #552410
Public bug reported:
If nautilus is set to not show icons on the desktop, when you run
mutter --replace in Ubuntu 9.10, the wallpaper is replaced by a solid
white screen. Replacing mutter by metacity or compiz correctly reverts
the wallpaper.
ProblemType: Bug
Architecture: i386
Date: Sat Nov 7
This is specific to the LPIA versions. I am using clearlooks as my theme
of choice, and:
- generic architecture with intel graphics (desktop) = no problem
- LPIA architecture with intel graphics (netbook) = OMG PINK PONIES!!!
--
GTK themes show incorrect color when shade is used
Public bug reported:
Binary package hint: gtk-recordmydesktop
For some reason, RMD in karmic doesn't record properly. Even if I set it
to record at 30 fps (and I have a quadcore processor, it's clearly not
the bottleneck), it seems to record at 0.5 or 1 frame per second.
Completely useless,
Public bug reported:
Binary package hint: youtube-dl
The current package of youtube-dl is very outdated. Please update it to
version 2009.09.13
** Affects: youtube-dl (Ubuntu)
Importance: Undecided
Status: New
--
please update the package for youtube-dl
** Changed in: specto (Ubuntu)
Status: Incomplete = Invalid
--
Crash after partial system upgrade
https://bugs.launchpad.net/bugs/226958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
From what I can tell by looking at the traceback, network manager was
misbehaving after your comeback from hibernation. Anyway, I'm guessing
that this is not relevant anymore due to that version of specto being
quite outdated.
** Changed in: specto (Ubuntu)
Status: New = Invalid
--
*** This bug is a duplicate of bug 354909 ***
https://bugs.launchpad.net/bugs/354909
** This bug is no longer a duplicate of bug 349054
specto crashed with ImportError: No module named numpy.core.multiarray
** This bug has been marked a duplicate of bug 354909
python 2.6 support -
*** This bug is a duplicate of bug 354909 ***
https://bugs.launchpad.net/bugs/354909
** This bug has been marked a duplicate of bug 354909
python 2.6 support - jaunty
--
specto crashed with ImportError: No module named numpy.core.multiarray
https://bugs.launchpad.net/bugs/349054
You
This doesn't happen in Specto 0.3.1.
** Changed in: specto (Ubuntu)
Status: New = Fix Released
--
specto crashed with RuntimeError in __init__()
https://bugs.launchpad.net/bugs/241747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, no traceback and it's with an old version of Specto. Unless more
info is provided, I have no idea what happened there.
** Changed in: specto (Ubuntu)
Status: New = Invalid
--
specto crashed with ImportError in module()
https://bugs.launchpad.net/bugs/351749
You received this bug
Julien, I have to ask, what's up with the sudden dozen of 1+ year old
bugs suddenly being made public (they could have been investigated much
sooner)? I don't even know if this one is relevant. Steffen, are you
still affected by this (especially with version 0.3.1)?
** Changed in: specto (Ubuntu)
Confirming the behavior. I'm wondering if this is a duplicate of bug
#399732 though?
** Package changed: ubuntu = virtualbox-guest-additions (Ubuntu)
** Changed in: virtualbox-guest-additions (Ubuntu)
Status: New = Confirmed
--
Karmic as a VirtualBox guest does not support X11 guest
No, the Specto MOTU package in karmic still points to the GPL v3.
As for asking the question on the debian mailing lists, I did not have
the time/inclination/courage to do it.
--
don't patch the licence files
https://bugs.launchpad.net/bugs/390240
You received this bug notification because you
The package is still wrongly patched with to its license, as reported in
bug #390240.
** Changed in: specto (Ubuntu)
Status: Fix Released = New
--
please update the Ubuntu package for Specto 0.3.1
https://bugs.launchpad.net/bugs/398536
You received this bug notification because you are a
Partly, as this does not tell me why the need to make them links instead
of providing the original file in the first place. That debian doc page
tells me the procedure, but does not explain the rationale behind it.
** Changed in: specto (Ubuntu)
Status: Incomplete = New
--
don't patch
This is worse than I thought. You folks point to the GPL version 3
(/usr/share/common-licenses/GPL). Specto is licensed GPL version 2. I am
aware of the or later clause, but this is violating the intent of the
authors. And I have not had the permission to use the GPL v3 from my
fellow specto devs.
By the way, this post was not intended to be a flame (altough it sounds
as if I was angry), it's really because I don't understand the benefits
of this approach (on the contrary, I see drawbacks: bugs cropping up as
the result of such patches, and errors like the wrong license being
used).
--
Related question in bug #390240
--
please update the Ubuntu package for Specto 0.3.1
https://bugs.launchpad.net/bugs/398536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
Public bug reported:
Binary package hint: specto
The Ubuntu packages for Specto should be updated to the new 0.3.1
version; the 0.2.x series is very outdated and buggy, and does not
behave well with notify-osd (introduced in Ubuntu 9.04).
I think it's not too late for Ubuntu 9.10 right?
Links,
Public bug reported:
Binary package hint: specto
For some reason, the debian/ubuntu packages patch about.py to link to a
systemwide gpl-2 license file, and strip out the COPYING file that comes
with the package.
Now, I'd like to know why this is done. Because it breaks when either
about.py
Well that particular dependency has been there forever, so I'm not sure
what would be problematic. The only stuff that changed recently is that
you need python-numpy. All the dependencies I know of are listed on
http://specto.sourceforge.net/?go=download
But python-gnome2-extras refusing to
0.3 is out. Packages for Ubuntu will be coming sometime soon.
** Changed in: specto (Ubuntu)
Status: Fix Committed = Fix Released
--
specto lost all my urls
https://bugs.launchpad.net/bugs/242339
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well in my case, there is no video group (judging from the system
users admin GUI), although, indeed, the files in /dev/dvb/adapter0 seem
to belong to the user root and the group video. wtf?
--
mplayer tv tuner DVB CONFIGURATION IS EMPTY in Jaunty
https://bugs.launchpad.net/bugs/369349
You
Doesn't work with the generic 2.6.30 kernel either. Used to work in
Intrepid without problems.
My card is this one:
02:00.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135
Video Broadcast Decoder (rev d1)
--
mplayer tv tuner DVB CONFIGURATION IS EMPTY in Jaunty
Having this problem with a KWorld ATSC 115 tuner (firmware: dvb-fe-
nxt2004.fw), I'm running the 2.6.28-11-server kernel. However, VLC and
totem can't tune either. Is this really mplayer's fault?
** Changed in: mplayer (Ubuntu)
Status: New = Confirmed
--
mplayer tv tuner DVB
This is with the old version of specto. Could you try the version
provided in our PPAs and see if it works better?
** Changed in: specto (Ubuntu)
Status: New = Incomplete
--
specto crashed with SIGSEGV in PyEval_EvalFrameEx()
https://bugs.launchpad.net/bugs/363602
You received this bug
Please try again with the 0.3.x version from the PPAs, if possible.
** Changed in: specto (Ubuntu)
Status: New = Incomplete
--
specto crashed with IncompleteRead in _safe_read()
https://bugs.launchpad.net/bugs/179538
You received this bug notification because you are a member of Ubuntu
Alessio, what changes did you make to your PPA version? perhaps you
could provide your patch on
http://code.google.com/p/specto/issues/detail?id=216 ?
For what it's worth, the last time I tried swapping hashlib and md5,
this caused serious problems (web watches not working at all).
--
python
More info might be needed on this issue upstream:
http://code.google.com/p/specto/issues/detail?id=216
--
python 2.6 support - jaunty
https://bugs.launchpad.net/bugs/354909
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Might I ask wtf is this numpy module I've never heard about before as a
dev, though? :) it used to work without it.
--
python 2.6 support - jaunty
https://bugs.launchpad.net/bugs/354909
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did you try that using the main specto bazaar branch? It seems to me
that fixing the other python 2.6 issues may have made this vanish, at
least I haven't experienced this particular problem.
--
python 2.6 support - jaunty
https://bugs.launchpad.net/bugs/354909
You received this bug
No, I never had java installed at all since December (according to my
memory and to synaptic's history), so it's a different issue.
--
[iG33] xorg crash while browsing the web
https://bugs.launchpad.net/bugs/326742
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: xserver-xorg-video-intel
X just crashed randomly while I was surfing the web. I'm using Ubuntu
8.10, 2.6.27-11-server. Adobe Flash is not installed.
** Affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
--
xorg
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/22138631/Xorg.0.log
--
xorg crash while browsing the web
https://bugs.launchpad.net/bugs/326742
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Here's my hardware list
** Attachment added: lspci-.txt
http://launchpadlibrarian.net/22138641/lspci-.txt
--
xorg crash while browsing the web
https://bugs.launchpad.net/bugs/326742
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
... and my Xorg configuration.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/22138664/xorg.conf
--
xorg crash while browsing the web
https://bugs.launchpad.net/bugs/326742
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'll add that this is using a Dell Inspiron 530n (which was bought with
Ubuntu 8.04), but I can't find a way so that this bug report is c.c.ed
to the Dell Ubuntu team/project.
--
xorg crash while browsing the web
https://bugs.launchpad.net/bugs/326742
You received this bug notification because
If you're able to be lucky like that, then I would recommend testing
the specto-main branch. I have not experienced the issue since I began
using it last spring. Your feedback on that development version (which
actually is more stable than the 0.2.2 version) is welcome.
--
specto lost all my
For the record, he is not using desktop effects (just plain metacity
with composite turned off). xorg.conf has not been touched since the
clean install from 8.10.
--
Square freezes on the screen
https://bugs.launchpad.net/bugs/293422
You received this bug notification because you are a member of
87 matches
Mail list logo
