When I launched cheese on the Acer Aspire One I saw what looked like the startup screen, but then it immediately crashed. I'm wondering whether it is a problem of missing driver or something else. Anyone have any hints? Thanks
Anne
Cheese is a gnome app as far as I know.
However try to open cheese in terminal to see if it will show any error messages: Open the terminal and type in the promt "cheese" and press enter. What does it say, if it says anything?
2009/6/3 Anne Wilson cannewilson@googlemail.com:
When I launched cheese on the Acer Aspire One I saw what looked like the startup screen, but then it immediately crashed. I'm wondering whether it is a problem of missing driver or something else. Anyone have any hints? Thanks
Anne
New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
On Wednesday 03 June 2009 11:24:42 Torstein Adolf Winterseth wrote:
Cheese is a gnome app as far as I know.
Someone had asked about an application to work with webcams, and I was pretty sure that I had used cheese to check the Acer Aspire One webcam, when I first installed F10. For myself, I rarely need this, and would be happy to try anything else.
However try to open cheese in terminal to see if it will show any error messages: Open the terminal and type in the promt "cheese" and press enter. What does it say, if it says anything?
Yes, I'd already done that. Although the symptoms are the same as reported in the bug link Mary Ellen gave, the error messages aren't, and this is a kde- fedora-updated F10, not F11.
cheese
(cheese:6176): GLib-GObject-WARNING **: cannot register existing type `FluTsPatInfo'
(cheese:6176): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(cheese:6176): GLib-GObject-CRITICAL **: g_param_spec_object: assertion `g_type_is_a (object_type, G_TYPE_OBJECT)' failed
(cheese:6176): GLib-GObject-WARNING **: cannot register existing type `FluTsPmtInfo'
(cheese:6176): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(cheese:6176): GLib-GObject-CRITICAL **: g_param_spec_object: assertion `g_type_is_a (object_type, G_TYPE_OBJECT)' failed
(cheese:6176): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed Segmentation fault
I thought it was looking for glibc, but
Package glibc-2.9-3.i686 already installed and latest version
Anne
2009/6/3 Anne Wilson cannewilson@googlemail.com:
Yes, I'd already done that. Although the symptoms are the same as reported in the bug link Mary Ellen gave, the error messages aren't, and this is a kde- fedora-updated F10, not F11.
(cheese:6176): GLib-GObject-WARNING **: cannot register existing type `FluTsPatInfo'
[ ... ]
(cheese:6176): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed Segmentation fault
I think those are all warnings from glib, and possibly not relevant; I'd still be tempted to blame the segfault on the same root cause as the F11 case. What's your version of libv4l?
I thought it was looking for glibc, but
Package glibc-2.9-3.i686 already installed and latest version
glibc: standard core C libraries glib2: low-level library for GTK and GNOME
I think the warnings above are about glib2 issues, not glibc issues, and glib2 is a dependency (direct or indirect) of all GNOME apps so it can't be missing.
MEF
On Wednesday 03 June 2009 11:55:24 Mary Ellen Foster wrote:
2009/6/3 Anne Wilson cannewilson@googlemail.com:
Yes, I'd already done that. Although the symptoms are the same as reported in the bug link Mary Ellen gave, the error messages aren't, and this is a kde- fedora-updated F10, not F11.
(cheese:6176): GLib-GObject-WARNING **: cannot register existing type `FluTsPatInfo'
[ ... ]
(cheese:6176): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed Segmentation fault
I think those are all warnings from glib, and possibly not relevant; I'd still be tempted to blame the segfault on the same root cause as the F11 case. What's your version of libv4l?
libv4l-0.5.98-1.fc10.i386
I thought it was looking for glibc, but
Package glibc-2.9-3.i686 already installed and latest version
glibc: standard core C libraries glib2: low-level library for GTK and GNOME
I think the warnings above are about glib2 issues, not glibc issues, and glib2 is a dependency (direct or indirect) of all GNOME apps so it can't be missing.
Thanks
Anne
2009/6/3 Anne Wilson cannewilson@googlemail.com:
What's your version of libv4l?
libv4l-0.5.98-1.fc10.i386
According to the bug report, the crashing is an issue with libv4l-0.5.98 and is fixed in 0.5.99. I assume the maintainer will push the fix to all affected platforms ...
MEF
On Wednesday 03 June 2009 13:30:17 Mary Ellen Foster wrote:
2009/6/3 Anne Wilson cannewilson@googlemail.com:
What's your version of libv4l?
libv4l-0.5.98-1.fc10.i386
According to the bug report, the crashing is an issue with libv4l-0.5.98 and is fixed in 0.5.99. I assume the maintainer will push the fix to all affected platforms ...
MEF
Ah - I didn't spot that. Thanks.
Anne
2009/6/3 Anne Wilson cannewilson@googlemail.com:
When I launched cheese on the Acer Aspire One I saw what looked like the startup screen, but then it immediately crashed. I'm wondering whether it is a problem of missing driver or something else. Anyone have any hints? Thanks
Known bug, fix on the way: https://bugzilla.redhat.com/show_bug.cgi?id=503345
MEF
Hi Anne,
Quoting Anne Wilson cannewilson@googlemail.com:
When I launched cheese on the Acer Aspire One I saw what looked like the startup screen, but then it immediately crashed. I'm wondering whether it is a problem of missing driver or something else. Anyone have any hints?
I've never used cheese before and I don't own a AA1, so my feedback may not be too useful.
First, I didn't have my webcam plugged in and cheese started up just fine and after a couple of seconds it told me that I didn't have a camera. Then I tried a camera, for which I don't have a driver installed, with the same result as before. When I plugged in a working cam, cheese displayed a picture, but I seemed to be unable to take snapshots.
Judging from my rather limited experience, I don't think a missing driver should crash cheese. A broken driver will be another story, though.
Have you tried to use the cam with any other program, for instance kopete? I've been using luvcview with good results in the past
http://www.quickcamteam.net/software/linux/v4l2-software/luvcview
Cheers,
Andreas
On Wednesday 03 June 2009 11:41:16 Andreas Petzold wrote:
Hi Anne,
Quoting Anne Wilson cannewilson@googlemail.com:
When I launched cheese on the Acer Aspire One I saw what looked like the startup screen, but then it immediately crashed. I'm wondering whether it
is
a problem of missing driver or something else. Anyone have any hints?
I've never used cheese before and I don't own a AA1, so my feedback may not be too useful.
First, I didn't have my webcam plugged in and cheese started up just fine and after a couple of seconds it told me that I didn't have a camera. Then I tried a camera, for which I don't have a driver installed, with the same result as before. When I plugged in a working cam, cheese displayed a picture, but I seemed to be unable to take snapshots.
Judging from my rather limited experience, I don't think a missing driver should crash cheese. A broken driver will be another story, though.
Have you tried to use the cam with any other program, for instance kopete? I've been using luvcview with good results in the past
http://www.quickcamteam.net/software/linux/v4l2-software/luvcview
I hadn't actually tried it with anything else, but I fired up kopete, which instantly told me that I have an Acer Crystal Eye webcam, and produced a picture better than I expected considering the lighting condition.
Anne
-
Andreas Petzold -
Anne Wilson -
Mary Ellen Foster -
Torstein Adolf Winterseth