Closing the bug again as there has been no update about the bug.
I would like to remind again that such bugs are better handled upstream, Kindly
file a bug in:
https://bugzilla.gnome.org/enter_bug.cgi?product=cheese
We dont make major changes in Ubuntu for Cheese , so such issues are better
Alex Wauck , Thanks for digging deeper into the problem.
Marking bug as incomplete , for now , awaiting your reply on what is the cause
of the bug
** Changed in: cheese (Ubuntu)
Importance: Medium = Undecided
** Changed in: cheese (Ubuntu)
Status: New = Incomplete
--
cheese crashes
I was able to start cheese with sudo cheese on the command line. is
the upgrade package from Karmic to Lucid changing file permissions
somewhere?
--
cheese crashes on startup
https://bugs.launchpad.net/bugs/585137
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Kat Amsterdam: Your bug doesnt seem related to this one. Kindly file a
separate bug, using the command:
ubuntu-bug cheese
Remember to select the first option when prompted with a dialogue.
--
cheese crashes on startup
https://bugs.launchpad.net/bugs/585137
You received this bug notification
I have the exact same problem on a recently upgraded from Karmic to
Lucid (Cheese worked perfectly in Karmic). I resintalled cheese but this
did not help. I did a ubuntu-bug cheese but am not sure if the data got
properly attached.
--
cheese crashes on startup
When I start cheese with sudo cheese I get a different error, no
picture, but the application stays open.
error:
libv4l2: error converting / decoding frame data: v4l-convert: error parsing
JPEG header: Not a JPG file ?
--
cheese crashes on startup
https://bugs.launchpad.net/bugs/585137
You
I am reopening this bug because the problem has reappeared. I am
currently running the mainline 2.6.35-rc2 kernel, so that may have
something to do with it, but Kamoso works just fine. Also, my initial
investigation suggests that part of the problem is that Cheese is not
dealing with an error
I figured out how to get the build I wanted (it turned out to be
obvious: set a CFLAGS environment variable before running the configure
script), but when I switched back to the open-source radeon driver, the
bug was still gone! I would love to know why it didn't work initially,
but whatever. It
Thanks for following up.Closing bug report. I'm not sure I know the
answer to the how to convince the cheese build system to build binaries
without optimization
You can try contacting the upstream devs regarding this :
https://bugzilla.gnome.org/browse.cgi?product=cheese
or you can file a bug
Kindly follow all the steps as mentioned in: https://wiki.ubuntu.com/Backtrace
We need a full backtrace.
** Changed in: cheese (Ubuntu)
Status: New = Incomplete
--
cheese crashes on startup
https://bugs.launchpad.net/bugs/585137
You received this bug notification because you are a member
The problem seems to have gone away after I switched to fglrx for the
video driver. I think I can figure out the root cause of this crash if
someone tells me how to convince the cheese build system to build
binaries without optimization so that I don't get that annoying value
optimized out stuff
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
I have attached the requested backtrace.
** Attachment added: cheese_backtrace.txt
http://launchpadlibrarian.net/49089179/cheese_backtrace.txt
** Changed in: cheese (Ubuntu)
Status: Incomplete = New
--
cheese crashes on startup
https://bugs.launchpad.net/bugs/585137
You received this
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49040083/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/49040084/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49040085/Dependencies.txt
**
14 matches
Mail list logo
