zoomy942, the relevant part of that thread (the one about uvcvideo driver)
suggests to install latest trunk from uvcvideo svn.
That's the latest version before uvcvideo was included in mainline kernel
(2.27) and probably the same (or almost the same) one included in Hardy.
If it fixes the issue
> It may be the case that Cheese makes correct use of the API, in a way most
> other applications don't use the API, and that uvcvideo breaks when used
> this way.
The API? which api are you talking about? the v4l2 api? we just do *one* ioctl,
it's a very basic and simple one and it's already bee
Francisco, as I said previously (not sure if it was here), I'm not upset
with you or with anyone at all. It's just that lately I hear so many
people complaining that cheese doesn't work, I even read some rather
"expert" guy in the forums saying to newbies things like "cheese is
completely broken in
I talked about this issue with the uvcvideo maintainer. It seems it is
strictly connected with gstreamer's v4l2src switch to libv4l2. Anyway he
came up with a patch that fixes it, or at least fixes mine. He will
commit it to his branch on linuxtv.org soon, I'll keep you updated.
--
cheese malfunc
zoomy942,
Sure I didn't post it here because I was waiting for him to commit it.
The changeset is: http://linuxtv.org/hg/~pinchartl/uvcvideo/rev/62c88b326ecd
Could any of you give it a test to see if it fixes your issue too?
You can get the source running hg clone
http://linuxtv.org/hg/~pinchartl
zoomy, see the big fat warning printed when you run make? svn repository
is deprecated. If you want to give some help you should really try the
mercurial repository I pointed you a couple of hours ago
(http://linuxtv.org/hg/~pinchartl/uvcvideo). Anyway notice that it
contains the whole v4l-dvb stac
Jose, no it doesn't work by following the wiki. The method you posted is under
the statement "Use this section if you are using an Ubuntu version prior to
Gusty 7.10. ", so that guide supposes that intrepid should have debug symbols.
Anyway I already rebuilt the library from source, debugged my i
*** This bug is a duplicate of bug 290506 ***
https://bugs.launchpad.net/bugs/290506
Marking this bug as a duplicate of bug 290506, I know at least two
people with the very same hardware that managed to fix the issue
installing Stefan Bader kernel package listed in that bug or manually
compili
Hi, I'm a cheese developer, I really believe this is a duplicate of bug 290506.
I didn't find though any information about your laptop, can you confirm that
your webcam uses uvcvideo driver? Could you attach here the output from lsusb
and dmesg?
--
[Regression] Cheese stops when I try to record
For what it's worth (I wrote the patch), I confirm the package in hardy-
proposed fixes the issue here.
--
GNOME Mastermind grid is shifted to the right with new cairo releases
https://bugs.launchpad.net/bugs/222580
You received this bug notification because you are a member of Ubuntu
Bugs, which
The ChangeLog says this bug has been fixed in 2.6.30 with commit:
commit a8aa401f38cfb5fa26e970b48e93fb851d68fe64
Author: Johannes Berg
Date: Sat Apr 18 11:00:39 2009 +0200
USB: pass mem_flags to dma_alloc_coherent
When I want to use my webcam, I get:
I don't believe the feature requested here will happen anytime soon. Photos are
saved directly from the same stream of the viewfinder, a frame is taken and
encoded into a jpeg file. To do what the OP suggested we will need to stop the
pipeline, close the device, reopen it with an higher resoluti
Known bug, fixed in 2.27.2
** Bug watch added: GNOME Bug Tracker #582240
http://bugzilla.gnome.org/show_bug.cgi?id=582240
** Also affects: cheese via
http://bugzilla.gnome.org/show_bug.cgi?id=582240
Importance: Unknown
Status: Unknown
** Changed in: cheese (Ubuntu)
Status:
Also backported in 2.26.2
--
Cheese should be dependend on gnome-icon-theme
https://bugs.launchpad.net/bugs/375917
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
https://lists.ub
** Bug watch added: GNOME Bug Tracker #585761
http://bugzilla.gnome.org/show_bug.cgi?id=585761
** Also affects: cheese via
http://bugzilla.gnome.org/show_bug.cgi?id=585761
Importance: Unknown
Status: Unknown
--
Audio track becomes choppy & de-synchronized after 30 or so seconds o
Added a bug for this in the upstream tracker.
Please forward your bugs there if you want Cheese developers to notice it and
have a chance to get them fixed. I take a look here sometimes but it doesn't
happen really often.
--
Audio track becomes choppy & de-synchronized after 30 or so seconds of
Could you guys test the my last git commit? I'm quite confident it should fix
or at least reduce a lot a/v sync errors.
http://git.gnome.org/cgit/cheese/commit/?id=d25b64149249be6a1329880ae42d4accc0db06d3
--
Audio track becomes choppy & de-synchronized after 30 or so seconds of
recording.
https
Could you attach a "cheese -v" log?
Which driver does that webcam use? it seems it misreports the formats it
supports (as far as I can tell it advertises to support a continuous range of
resolutions, and that's quite unlikely, it should give a discrete list of
resolution/framerates)
--
cheese
reh4c, you have a different bug than this one. This is about cheese hanging on
start yours is about cheese hanging on video recording. It happens with almost
all netbooks because they are too much underpowered to do live theora encoding.
See http://bugzilla.gnome.org/show_bug.cgi?id=564957
** Bu
Cheese doesn't fail anything here. It is a known libv4l bug. Hans has
fixed it in a test development snapshot and it will definitely be fixed
in the next release. See
http://bugzilla.gnome.org/show_bug.cgi?id=571772
** Also affects: libv4l (Ubuntu)
Importance: Undecided
Status: New
** C
*** This bug is a duplicate of bug 345080 ***
https://bugs.launchpad.net/bugs/345080
** This bug is no longer a duplicate of bug 349255
Green webcam capture on isight
** This bug has been marked a duplicate of bug 345080
iSight camera images have green/purple tint
--
all-green image on
*** This bug is a duplicate of bug 345080 ***
https://bugs.launchpad.net/bugs/345080
** This bug has been marked a duplicate of bug 345080
iSight camera images have green/purple tint
--
Green webcam capture on isight
https://bugs.launchpad.net/bugs/349255
You received this bug notificatio
> Is it the same as bug #349255 ?
Yes it is, marked as duplicate
--
iSight camera images have green/purple tint
https://bugs.launchpad.net/bugs/345080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Public bug reported:
After upgrading to Jaunty brightness settings are not remembered anymore when
rebooting or when disconnecting power cable.
During boot process brigthness changes multiple times:
- at BIOS screen brightness gets correctly restored to last used one
- when ubuntu starts loading
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/23109865/dmesg.log
--
Brightness changes multiple times during boot up and doesn't get back to the
last used one
https://bugs.launchpad.net/bugs/334206
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/23109880/lspci-vnvn.log
--
Brightness changes multiple times during boot up and doesn't get back to the
last used one
https://bugs.launchpad.net/bugs/334206
You received this bug notification because you are a member of Ubun
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/23109887/uname-a.log
--
Brightness changes multiple times during boot up and doesn't get back to the
last used one
https://bugs.launchpad.net/bugs/334206
You received this bug notification because you are a member of Ubuntu
Bug
** Attachment added: "version.log"
http://launchpadlibrarian.net/23109893/version.log
** Summary changed:
- Brightness changes multiple times during boot up and gets back to the last
used one
+ Brightness changes multiple times during boot up and doesn't get back to the
last used one
--
B
Bryce, I think you're following a wrong path.. it's not a matter of single keys
not mapped correctly. It's the layout setting that gets forgotten after reboot.
Considering that dell-mini uses autologin I really believe this is a duplicate
of bug #196277
--
UNR - Italian Keyboard Configuration o
** Description changed:
After upgrading to Jaunty brightness settings are not remembered anymore when
rebooting or when disconnecting power cable.
During boot process brigthness changes multiple times:
- at BIOS screen brightness gets correctly restored to last used one
- when ubuntu star
I believe Ubuntu Hardy shipped with Dell Mini 9 is also affected by this bug
(it uses autologin), at least it is after latest upgrades.
As far as I can tell it worked fine before the upgrades so it could be fixed
reverting the change that introduced it, I don't know but maybe it would be
easier
Confirming the issue for gnome-power-manager: it sets brightness level to 100
as soon as it starts.
There is still something else that does the same while ubuntu is loading but
still I don't know which package.
pi...@tux:~$ killall gnome-power-manager
pi...@tux:~$ cat /proc/acpi/video/VGA/LCD/br
Another thing, not sure if it is ok to ask it on a launchpad bug.. could
anybody verify if the issue still stands with mainline drivers from the
v4l-dvb mercurial tree so that we can understand if it is an ubuntu
specific regression or an upstream one?
--
cheese doesn't work with my webcam (Phili
@Valerio,
I don't really think this is a gstreamer bug since both skype and xawtv users
reported the very same issue (see duplicates of this bug).
I don't know why it still works with vlc (someone said it works with camorama
too but I think it's using v4l1 api) but it's likely that this issue com
Andres, as I said in bugzilla I was wrong about libv4l.. I don't know
what made me believe that patch fixed the issue (it was late and I was
really tired) but, unfortunately, it doesn't.
Also please forgive me if I appeared rude with you, I didn't want it,
it's just that lately too much people say
I don't think the point here is if it works good with gstreamer+v4lsrc.
As Baptiste said in the upstream bug report the webcam works with right
colors using v4lsrc (v4l1) from gstreamer properties but it's tinted
green using it as a v4l2 device. So the bug is the v4l2 green tint,
forcing it to use
*** This bug is a duplicate of bug 282473 ***
https://bugs.launchpad.net/bugs/282473
Andres please notice that bug is not really linked to upstream.. it is
linked to a cheese bugzilla bug that I didn't close yet as NOTGNOME just
because I want it to still stay there as a reference for other
re
@Andres, no this bug really is a pwc specific one and it's not cheese related
at all.
Bug #290506 is uvcvideo specific and maybe it has something to do with cheese
but I'm still not sure.
--
cheese doesn't work with my webcam (Philips PCVC740K ToUcam Pro)
https://bugs.launchpad.net/bugs/282473
Andres, cheese asking hal for v4l capable devices has absolutely no
relation with this bug. Please don't blame us if you don't know what you
are talking about.
We just use gstreamer to access the webcam device.
The only thing we do on our own (directly accessing the device) is a
VIDIOC_QUERYCAP i
iSmith, do you mean the first gst-launch command? what about the second one?
does it lock you webcam?
Thanks
--
cheese doesn't show v4l2 video output and disables output on gstreamer-based
apps ran afterwards
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you
Fabian, probably your webcam doesn't support 1280x1024
Could you please check if gst-launch v4l2src ! xvimagesink locks the webcam?
--
cheese doesn't show v4l2 video output and disables output on gstreamer-based
apps ran afterwards
https://bugs.launchpad.net/bugs/290506
You received this bug not
dominko, that's a known issue with your webcam driver please take a look at
http://bugzilla.gnome.org/show_bug.cgi?id=531835 and
http://bugs.mediati.org/r5u870/issue17
So, am I the only one able to reproduce it both with cheese and plain
gstreamer?
--
cheese doesn't show v4l2 video output and d
Could any of you check if the issue can be reproduced with pre 2.27 kernels
too? The last one from 2.26 series should be fine.
I want to be 100% sure this thing has nothing to do with cheese (and possibly
with gstreamer too) and it is a uvcvideo issue only.
--
cheese doesn't show v4l2 video out
Public bug reported:
Not too much to say.. I have a segfault on a libselinux function but I'm
not able to debug it since there is no debug package. There was one in
hard (libselinux1-dbg) why it has been removed?
** Affects: libselinux (Ubuntu)
Importance: Undecided
Status: New
--
First, that guide doesn't talk about intrepid.
Second, there is no libselinux-dbg package in intrepid repos and no
libselinux-dbgsym package in intrepid ddebs repository.
Am I missing anything? As far as I can tell the debug package has been removed
in intrepid while there was one in hardy.. corr
Still I cannot understand why this patch is not being considered.. I
think it's ok, is there any reason why it cannot be commited in Hardy?
it's been 3 months since this bug is open and noone complained.
--
GNOME Mastermind grid is shifted to the right with new cairo releases
https://bugs.launchp
I confirm that this issue has nothing to do with libavg, I'm experiencing it
with gst-inspect too.
The sigsegv happens in fini_contex_translations function (setrans_client.c)
because it free a couple of uninitialized contexts.
Mike's patch doesn't seem to solve the issue here (current intrepid) t
Hi, I'm a Cheese developer,
Recently we had several (I'd say one per week, but sometimes even more) bug
reports on bugzilla.gnome.org from Ubuntu Intrepid users all more or less
caused by libv4l 0.5.6.
All users reported Cheese working again after upgrading to 0.5.7 from Loic's
PPA (and, of cour
Hi Martin, I'm a Cheese developer.
I think the "important" bug Loic did talk about was the one about webcams
supporting just one resolution not working properly. The other modifications
are just minor leak fixes.
I explicitly asked Loic to open this SRU for the improved debug information
about
I confirm the bug, it seems to happen with metacity themes that change their
color with the gtk color scheme. I can see it with almost every theme but
Ubuntu ones (probably ubuntu metacity has hardcoded color). Almost every other
window border is just pink after the upgrades.
I'm using stock ubu
Same problem here on a Dell Mini 9 after latest upgrades. I can switch
keyboard layout from preferences and set it to Italian, it works but
after reboot I get again US mapped keys.
Also note that with latest upgrades Super key is not binded to F11
anymore so magic fullscreen doesn't work.
** Also
On Mon, Feb 2, 2009 at 11:08 PM, Chris Gregan wrote:
> Not a bug concerning the Shipping Dell mini OS
Why not? It uses Ubuntu Hardy and this bug affects Ubuntu Hardy. You
ship custom packages for Dell Mini which also include this bug.
Either disable the upgrades or fix it in your custom packages.
On Thu, Jan 8, 2009 at 10:00 PM, Tormod Volden wrote:
> Tested the version 2.24.2-0ubuntu0+intrepid1 (with my Genius Eye) and
> everything worked fine, no regressions AFAICS. I can not comment on any
> bug fixes though. Where is that debug information supposed to show up?
It should come up runnin
On Thu, Jan 8, 2009 at 11:32 PM, Tormod Volden wrote:
> I tried -v and --verbose with no luck. These options are not mentioned
> in the man page, but that would be another bug.
As far as I remember we don't ship any man page, probably it comes
from a debian or ubuntu patch.
Anyway, do you mean ch
On Tue, Dec 23, 2008 at 10:35 PM, WillSmith wrote:
> I did not run the commands found in that ubuntuforums post. I don't have
> interest to inject potentially unstable modules into my kernel.
> >From what I have seen the update should just be of the kernel and v4l2
> packages.
> Do we know when t
@everybody:
Please also note that libv4l 0.5.6 has got a nasty bug that prevents uvcvideo
webcams to correctly work.
So the kernel alone is not enough to make Cheese work again.
The new libv4l 0.5.7, with the fix, already went through a SRU and should enter
intrepid-proposed soon (if it didn't y
Currently the upgrade fails with:
Preparing to replace nvidia-glx-180-dev 180.35-0ubuntu1 (using
.../nvidia-glx-180-dev_180.37-0ubuntu1_i386.deb) ...
dpkg-divert: rename involves overwriting `/usr/lib/libGL.so' with
different file `/usr/lib/nvidia/libGL.so.xlibmesa', not allowed
dpkg: error pro
Thanks Alberto, you're right, I don't know dpkg enought to distinguish
the two errors :)
--
dpkg-divert mismatch when upgrading or reinstalling nvidia-glx-180
https://bugs.launchpad.net/bugs/333550
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, new cheese package with the fix is out, could you guys confirm that
this bug is fixed?
--
on photo capture cheese blanks the screen until logout
https://bugs.launchpad.net/bugs/297890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Public bug reported:
Binary package hint: cheese
>From the debdiff:
+ifeq ($(DEB_BUILD_ARCH),lpia)
+ DEB_CONFIGURE_EXTRA_FLAGS += --enable-hildon
+endif
As far as I can tell I'm not supposed to run lpia packages on a
hildonized desktop, that's the reason there is a separate cheese-hildon
p
Subscribing Michael who worked on splitting hildon stuff in a separate
package.
--
lpia package built with hildon support while there is a separate hildon package
https://bugs.launchpad.net/bugs/345772
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm currently discussing with gnome accessibility experts to try to nail down
this issue. It is definetely confirmed that it only happens if a11y is enabled.
There is probably some locking issue with gdk threads.
Anyway, why the upstream tracker is set to Incomplete? the bug is marked as NEW
in
Ok, I think it's fixed with my last commit in SVN trunk. Could any of
you who experienced the issue test it and confirm it? Anyway now
bugzilla status is RESOLVED FIXED, and here it's still marked as
Incomplete, you really need to fix your upstream bug tracker.
--
on photo capture cheese blanks t
** Changed in: gconf
Status: New => Invalid
--
on photo capture cheese blanks the screen until logout
https://bugs.launchpad.net/bugs/297890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Hey is there something wrong with my debdiff? why no more reply?
Thanks again,
Filippo
--
GNOME Mastermind grid is shifted to the right with new cairo releases
https://bugs.launchpad.net/bugs/222580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Seems ok to me looking at the code.
--
Add apport hook for cheese
https://bugs.launchpad.net/bugs/542091
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
https://lists.ubuntu.com/m
On Sat, May 1, 2010 at 6:48 PM, schaze wrote:
> Now the system using the uvcvideo driver and now I am getting up to
> 640x480. Which is better, but still not the 800x600.
Still cheese has nothing to do about it.
> Unfortunately cheese -v in Lucid does not print any output any more
> (bug?).
GST
Could you run the following command line and attach here the cheese-
debug.log file produced?
GST_DEBUG=cheese*:3 src/cheese -v > cheese-debug.log 2>&1
--
Cheese doesn't detect webcam on MSI Wind U100
https://bugs.launchpad.net/bugs/508196
You received this bug notification because you are a mem
Did cheese detect you camera in previous versions?
--
Cheese doesn't detect webcam on MSI Wind U100
https://bugs.launchpad.net/bugs/508196
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.ubu
Confirmed and reported upstream
https://bugzilla.gnome.org/show_bug.cgi?id=610823
Please, for the future: I stumbled here by chance and I don't usually check
launchpad bugs (and usually ubuntu guys are not so fast upstreaming them), so,
if you want Cheese issues to be fixed, please use gnome bug
@Vish, sure I doesn't break any freeze, it will be in the 2.29.2
rellease planned for March 9 (and, of course, in 2.30)
--
Cheese does not _use_ preferred settings on next start
https://bugs.launchpad.net/bugs/524854
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I'm not sure about what difference do you see between simply probing for valid
resolutions and retrieving a list from the driver.
Cheese simply asks for supported pixel formats and the v4l-info output you
posted just proves it's right. The strange 464x464 resolution comes directly
from you drive
For what it's worth, the upstream but is still open, if any of you who
could reproduce the issue before could test the current version and
report if it's still going out of sync it would be great.
--
Audio track becomes choppy & de-synchronized after 30 or so seconds of
recording.
https://bugs.l
Nigel, if Vish forwarded you my mail, you should be working on fixing the
cheese log.txt creation by now.
So, could you please open a bug for the cheese related part of this hook (i.e.
the cheese.c print handler) in gnome bugzilla and attach your patch there? it
would greatly speed up my review.
Ok, don't worry. Now that I think about it I'm not sure it makes so much
sense to create a debug log file as we did. Enabling GST_DEBUG can
really slow down the whole execution, writing all that stuff to a file
would be even worse. I think I'll completely get rid of that log file.
The nice thing w
Also CheeseDebug (with no dash) seems to fit better the naming style
used for the other logs.
--
Add apport hook for cheese
https://bugs.launchpad.net/bugs/542091
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Hi, in cheese we have a similar issue with pa_tls_set crashes with no apparent
reason. I believe there could be a bug in LP too but don't have a link at hand
now.
You say it is fixed in Lucid. Has it been fixed in abiword? or in pulseaudio?
could you please point me to the fixing commit or to a
It seems gnome-mastermind suffers the same problem (in the upstream bug
the reporter says he has an intel card).
--
Cairo/Gdk shapes not visible on Intel gpu since Karmic
https://bugs.launchpad.net/bugs/458545
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
@3v1n0
With your ppa fractional scaling works again (I'm almost sure it worked fine in
19.10)
Text rendering is pretty bad at 125%, slightly better at 150%
Geforce GTX 1080, latest nvidia driver (440.100), Philips 328P 4k
display.
Thanks for looking into this, let me know if I can do more.
Affected too, i915 after the upgrade from 9.10, no plymouth in the initrd, no
splash at bootup nor at shutdown.
Reinstalling plymouth doesn't work, update-alternatives --auto default.plymouth
says there is no default.plymouth.
Before trying the FRAMEBUFFER=y thing, is that workaround supposed to
Just for the sake of completeness, I have this very same dongle and
networkmanager doesn't seem to see it neither in 9.10 nor 10.04 but the same
dongle works flawlessly on Fedora 13.
So the issue is not in the firmware, it's either in some ubuntu specific patch
or some (mis)configuration (well f
Same here E220 works flawlessly in Fedora 13 and doesn't even show up in
Lucid's NetworkManager.
--
Huawei E220 and E169 3G dongle do not work on karmic (major regression)
https://bugs.launchpad.net/bugs/430011
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Any news about this? it seems all watchdog modules are blacklisted
unless the watchdog daemon is installed and one module is enabled in
/etc/default/watchdog. With basic watchdog functionality already enabled
in systemd shouldn't this be changed to support it?
--
You received this bug notificatio
83 matches
Mail list logo
