well, you gave the details but the bug doesn't happen there so you will
need to provide a backtrace, note that you are the first one to report
it and that it could be hardware specific
current serie has nothing to do with the state of anything, it's where
the work happen, from day 1 on an unstable
Did you read mine? I gave all the details necessary to reproduce the bug
in eog on Oneiric. I cannot run apport, and I do not think that is
necessary to reproduce the bug .
Precise is not yet out of beta testing. Why is it considered the current
series in that state? The beta doesn't even boot on
did you read the comment? you need to report a bug with the details
needed to track the issue
> If the bug exists only in the earlier versions, it would still be
valid. Oneiric and Natty are still supported; Precise is not yet out of
beta testing.
that's not how launchpad work, the status concern
If the bug exists only in the earlier versions, it would still be valid.
Oneiric and Natty are still supported; Precise is not yet out of beta
testing.
** Changed in: eog (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
running that command on precise opens eog with a red banner saying "no
image found in file..." but no errors similar to what is described there
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/b
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
