Unfortunately, we're unable to reproduce this here, even when using the
setup conditions suggested in comments twelve and fifteen (along with
things like deliberately omitting the trailing slash, using '~' instead
of typing out the full path to my home directory, etc.).
For those of you still
Hi, and thank you for taking time to report this. Do you still see this
behaviour if you upgrade to 0.13?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074645
Title:
Shotwell crashes on image
Hi,
What you're proposing sounds very similar to an upstream ticket we'd
like to fix at some point; please see
http://redmine.yorba.org/issues/3173 .
Although it hasn't been yet been timetabled, we will definitely take
your interest in having this into consideration as we think about
possible
Apologies for bothering those watching this bug, but I'd like to let
everyone know this has been fixed upstream and will be available in the
next point release; please see
http://redmine.yorba.org/projects/shotwell/repository/revisions/8be51587fb776e5c398dedd67138e105e93011e2
for details.
--
You
Hi Aaron,
My name is Clint, and I'm the developer tasked with looking into this.
Unfortunately, I didn't seem to be able to reproduce it; is there
anything else unusual (besides the above-noted problem with Nautilus)
you've encountered that you think might be germane to us reproducing and
fixing
I just gave this a go with the paths
/home/clinton/test-images-11/Lynne's Pix/vlcsnap-2012-09-13-12h53m54s124.png
-and-
/home/clinton/test-images-11/Lynne's Pix/it's some kind of hockey image.png
...and external applications seemed to be able to open both (again,
using master), so this may
Unfortunately, we're not seeing this happen with the repository version,
either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048639
Title:
Cannot launch external editor for photos in directories
Hi again,
This is on Quantal i386 (Linux 3.5.0-13-generic #14-Ubuntu SMP Wed Aug
29 16:47:23 UTC 2012 i686 GNU/Linux).
I'm guessing the problem still occurs for you, even after installing the
most recent batch of updates?
--
You received this bug notification because you are a member of Ubuntu
Hi, and thank you for reporting this.
When you're seeing this, are you building Shotwell from trunk yourself,
or are you installing it from the repositories? The reason I ask is
because the repository version in 12.10 has been vendor-patched to
handle authentication in a different manner than
Ah, I retract the question; I see that this is specifically due to a
UOA-specific patch. My mistake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047588
Title:
Shotwell spawning oauth2callback
Hi Giovanni,
Apologies for the late response on this, but, might it be possible that
you have your images filtered somehow by date? I ask because we're
unable to reproduce this locally at all, and I'm at a loss as to why
importing would work, but the images would otherwise be hidden.
Do you see
Hi all,
Thank you for bringing this to our attention; I've created an upstream
bug report for this - please see http://redmine.yorba.org/issues/5638.
Thank you again,
-c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good morning, one and all,
We've committed a fix for this upstream (please see
http://redmine.yorba.org/projects/shotwell/repository/revisions/51336040742ad51936c1d2d92fa1d092cad73a54
for details); those of you who've been affected by this and are
comfortable building applications from source,
Good afternoon,
Apologies for bothering this list, but we've committed what we believe
to be a fix for this (please see
http://redmine.yorba.org/projects/shotwell/repository/revisions/7c2e51d3bbf9457d4dd37c60e3f59055c3923cbf);
those of you who have been affected and are comfortable with building
Fraser:
The fix is planned as part of 0.13, which, at this point, is still
timetabled for a few months from now, so you might have better luck
building from source, unfortunately.
The good news is that this is actually quite easy, and if you run into
difficulty doing so, either us here at Yorba
Hi all,
Apologies for bothering this list, but, for those of you who are
affected by this, do the images in question have nested tags attached to
them? The glitch you're encountering sounds very similar to upstream
bug http://redmine.yorba.org/issues/4297...
--
You received this bug
Hi Roland,
My name is Clinton, and I'm one of the developers currently assigned to
Shotwell.
I took a quick stab at trying to get the TombstoneTable into that same
state (two rows with the same fully qualified path- and file-name, but
with different IDs) wiht various combinations of importing
This is known to severely break at least one upstream package; please
see http://redmine.yorba.org/issues/4591.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903302
Title:
Dialog windows are not
As an aside, I believe I know what happened when it initially didn't
work; I've identified a repro case for it, although 90% of users
shouldn't have this problem.
When we start enumerating media files on a storage device, we
explicitly check several well-known paths, such as /DCIM, /AVCHD and
so
Hi Sebastien,
We do traverse all subdirectories inside a 'well-known' directory, so
anything saved inside /PRIVATE/AVCHD should have been found. As for
filtering, we don't, to my knowledge, leave out any video formats.
Is this happening when you connect the camera directly? Do you see the
same
Hi Sebastien,
Where do the videos normally get written to on a Lumix?
Due to a workaround to some problems between GPhoto and many Android
devices (http://redmine.yorba.org/issues/1903), we've had to explicitly
whitelist directories we want it to tell us about.
(I admit this is a suboptimal way
Hi again,
This question is unrelated to the bug report, so it, along with future
questions of a similar type might be better directed to our mailing list
(shotw...@lists.yorba.org). That said, here's how to enable the Unity
sidebar icon:
1) From the command line, navigate to the directory where
melenzb: You'll be pleased to know that we've just checked a small fix
into trunk that should help, and it's slated for inclusion into 0.12.3.
Along with checking for the presence of (and enumerating image and video
files in) /DCIM, we'll now also try /PRIVATE/AVCHD and /AVCHD as well,
which
Hi and thank you for taking time to report this. Does this happen evry
time you try to launch Shotwell, or is it intermitent?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944144
Title:
Hi,
I've marked the upstream ticket as 'blocked' for now; once the GPhoto
team have had a chance to address this, we'll reopen our ticket and get
their fix into Shotwell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, and thank you for reporting this.
When you attempt to use the send-to feature, what, exactly, happens?
If you get a dialogue box from Shotwell, but the images never make it as
far as your mail client, please check whether the package 'nautilus-
sendto' is installed (you can do this by typing
Hi,
Thank you for this; this should prove to be quite useful. I'll pass
this on to the rest of the team and we'll begin working on this as soon
as we can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, and thank you for taking time to report this.
I'll inform the rest of the team here, and we'll investigate this as
soon as we can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910595
Title:
For those watching this bug, please also see
http://redmine.yorba.org/issues/4544 - this is the upstream bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910044
Title:
shotwell crashed
Hi, and thank you for reporting this.
Unfortunately, it looks as if you may have uncovered a new bug, rather
than a previously-known one, and I'll ticket it on our side shortly.
If you feel comfortable doing so, can you try building Shotwell from
source, running with logging enabled and
Hi, and thank you for reporting this.
I just tried this in the current trunk, and it's 100% reproducible.
I've ticketed it on our side; please see
http://redmine.yorba.org/issues/4523.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, and thank you for reporting this.
Can you run the following command:
nautilus-sendto
...and tell me what the output is?
What Shotwell does is, rather than remember what email client you use
and try to launch it directly, it calls out to Nautilus for this, which,
in turn, keeps a list of
Hi, and thank you for taking time to report this.
When you're launching Shotwell, how are you doing so? If you usually
use a graphical launcher or lens, can you try launching it from the
command line and seeing if it works?
If it works normally from the command line, but not when launched from
Hi, and thank you for reporting this.
Here are some things you might try that could help:
1. Upgrade your Shotwell package to the latest one available in the repository
for Natty Narwhal (which should be 0.10).
2. Try rerunning the scenario with debugging enabled and with a smaller import;
if
The offending assertion has been ticketed at
http://redmine.yorba.org/issues/4461.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898028
Title:
assertion failed in hash_timed_queue_removed while
Hi, and thank you for reporting this.
I've been following the original thread on the mailing list as well,
and, unfortunately, short of adding time/date data via an EXIF-writing
tool, which you've already tried, there isn't a workaround that I'm
aware of.
When you say you're having images get
Hi again,
When the app freezes in the debugger, it has, in fact, crashed; GDB just
preserves the window.
When you do get the freeze in the debugger, if you type
bt
...what do you see?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
Thank you for reporting this. Can you try the following?
1) If you feel comfortable doing so, please try upgrading to 0.11.4,
available from
https://launchpad.net/ubuntu/+source/shotwell/0.11.4-0ubuntu1/+build/2861946
and see if the problem persists.
2) If you still encounter this, please
Hi,
Thank you for reporting this and attaching the backtrace. I've just
tried it here, and can reproduce it readily. We'll begin working on a
fix right away, and you can track our progress at
http://redmine.yorba.org/issues/4305 .
--
You received this bug notification because you are a member
Hi, and thank you for taking time to report this. I've added a ticket
for on our side at http://redmine.yorba.org/issues/4306 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882283
Title:
shotwell
Hallo,
Vergeef mijn arme Nederlandse taal, ik ben met behulp van een
automatische vertaler.
Als je zegt ontbrekende foto's niet bewegen, wat bedoel je? Is dit
gebeurt wanneer je foto's opgeslagen op een verwisselbare schijf die was
losgekoppeld en zijn ze het niet terug gevonden wanneer de
Hi, and thanks for taking time to report this.
It may be relevant that many of my photos are on a removable
disk that is not connected now.
Possibly, although the expected behaviour is that the application will
mark the offline photographs as 'missing' and continue to run normally.
With this
Hi again,
Because Shotwell is a non-destructive editor, the edited version of an
image is never actually stored on disk, unless the user manually exports
it; instead, some information about the original, along with the various
cropping, red eye and colour modifications, are stored in a database
Hi,
I'm sorry you've encountered something like this. When this happened,
were you running Shotwell directly with a specific image, or running it
with the entire library? Also, have you seen this happen a second time?
--
You received this bug notification because you are a member of Ubuntu
Hi, and thanks for responding.
So far, I haven't been able to reproduce this, so it isn't yet clear
what it is or how to fix it yet, but there are a few more things you can
try.
If you feel comfortable doing so, can you try upgrading to 0.11.5 to see
if the problem still occurs (available from
Unfortunately, the fix in question didn't make it into 0.11.5, so with
certain PNGs, this may still happen, albeit rarely, but it is available
in our git repository today, if you feel comfortable building things
from source and running bleeding edge software.
If you're interested, please see
Hi,
We'll begin looking into how to reproduce the problem with the
information you've already provided, so thanks for reporting this. If
you do experience further problems, you might try updating to Shotwell
0.11.5, currently available for Oneiric from
https://launchpad.net/~yorba/+archive/ppa .
Hi, and thank you for taking time to report this.
Can you try running Shotwell again from a command shell and see if any
error messages appear? Please copy and paste any error output into this
bug, as this will help us pinpoint the source of the problem.
If you feel comfortable doing so, you
Hi all,
As I stated before, this sounds like it might be an alternate symptom of
http://redmine.yorba.org/issues/4172 (please bear in mind that this is
just a guess; without seeing the console output, it's difficult to
tell). If so, then it has been fixed already and a fixed version,
0.11.5,
Hi,
Although we never reproduced this on our side, even with some
deliberately unusual PNG images (please see
http://redmine.yorba.org/issues/4195 for details), I can see where the
offending assertion would trigger if we somehow got an out-of-range
pixel (colour value less than 0 or greater than
Hi,
As Sebastien said, thank you for taking time to report this. If you
upgrade to the most recent version from the repository, currently
0.11.2, does this still occur?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Thanks to everyone who has reported this. I have opened a bug report
for it on our side; please see
http://http://redmine.yorba.org/issues/4268 .
We have the stacktrace and an approximate location in the code to begin
digging, but if any other users out there hit this and would like to
Hi,
Thank you for taking time to contact us. This does seem like a sensible
request, so I've added a ticket on our side; please see
http://redmine.yorba.org/issues/4269.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
This is most likely going to be made available at a slightly later time
as an update by the distro's packaging staff.
In the meantime, it is possible to install 0.11.4 from our PPA; please
see https://launchpad.net/~yorba/+archive/ppa/+sourcepub/2000217
/+listing-archive-extra for details.
Hi,
Thank you for reporting this. If you haven't already done so, can you try
running Shotwell from the command line with the debugger and logging enabled
and try to trigger the bug there? You can do this by typing
SHOTWELL_LOG=1 gdb shotwell
in a command shell window, then typing
Hi,
Thanks for reporting this, even if it seems to have gone away on its own
since then. If you ever get this again, can you try running Shotwell
from the command line and seeing if an error gets printed there?
I'd guess you may have encountered some variant of
Hi David,
Thank you for reporting this to us. This sounds very similar to
http://redmine.yorba.org/issues/4172, which, it would seem, can also
happen occasionally when importing images as well.
If you feel comfortable doing so, can you send a few sample images from
the failed import to
Hi, and thank you for taking time to report this to us. I've filed a
bug on our side; please see http://redmine.yorba.org/issues/4199.
Does this happen every time you open Shotwell now, or did it only happen
once? Also, if you feel comfortable doing so, can you send us a copy of
your photo
If the crash is no longer occurring, this might not be needed.
Between the deletion and the assertion I spotted in Stacktrace.txt, I
believe we have enough clues to investigate further at this point.
In the meantime, if you do happen to perform roughly the same sequence
of actions (delete images
Hi,
Thank you for taking time to report this. I've opened a matching ticket
on our side; please have a look at http://redmine.yorba.org/issues/4195
.
If you feel comfortable sending this, may we have a copy of repulse.png?
It may help to reproduce this crash and aid us in fixing it.
--
You
Hi, and thank you for taking time to report this problem to us.
I'd like to get more details about how to reproduce this; may I know
what email client you're using when this happens?
On the topic of renaming the button for better clarity, I'll bring that
up with the rest of the team ASAP.
--
Public bug reported:
Steps to reproduce:
1) With a small GTK application that creates one window, full-screens
it, then presents it, then creates and presents a second window, notice
which window is brought to the front and gets focus.
Notice that, roughly 60% of the time, the first window will
This may be related to
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/829863
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832293
Title:
Occasionally, after calling gtk_window_fullscreen() on
This can be observed in the wild with Shotwell 0.10.x:
1) On Oneric, launch the application.
2) Press F11.
3) Move the pointer to the bottom of the display and observe the results.
Occasionally, the toolbar doesn't appear; compare and contrast with the
behaviour on Maverick or Natty (the toolbar
Hi,
Thank you for reporting this. We will try to reproduce it in-house as
soon as possible. Is there anything else you can think of that might
have made the session unusual? It seemed like Facebook publishing was
working as recently as four days ago on our side.
--
You received this bug
Hi,
It looks like you may be running an older version of Shotwell; can you
try importing and cropping the same image with the most recent version
and let us know if that helps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
If you're still encountering this, but the debugger changes the
behaviour enough to the point where you can't trigger the crash while
running through it, here are a few things you might try:
1) If you haven't already done so, please try upgrading to the latest
version of Shotwell; I believe
Hi, and thank you for taking time to report this. We will try to
reproduce and triage this as soon as possible, and most likely ticket it
on our side. This sounds like it could be either an alternate case of,
or related to, a known problem; please see
http://trac.yorba.org/ticket/1502 for
Hi Mustava,
Thank you for taking time to report this. We'll look into it as soon as
we can, but in the meantime, can you:
* try this in 0.10.1 and let us know if it still happens?
* if it does, can you run Shotwell with gdb and obtain a backtrace at the
moment you see the error?
* let us know
Hi,
The custom crop dialog is actually the aspect ratio, rather than
absolute pixels, and as such, doesn't seem like it should have units. I
can confirm, though, that 'y' does seem to come before 'x' when running
the latest from trunk, which isn't right.
I will ticket this on our side
Hi,
We've been able to reproduce this in-house; I've opened a ticket
upstream for this at http://trac.yorba.org/ticket/3579 .
Thank you for taking time to report this.
** Bug watch added: trac.yorba.org/ #3579
http://trac.yorba.org/ticket/3579
--
You received this bug notification because
Hi,
It looks like the title is indeed getting copied to two fields
inappropriately, and we've been able to reproduce this in-house. I've
opened a ticket upstream; please see http://trac.yorba.org/ticket/3580.
Thank you for taking time to report this.
** Bug watch added: trac.yorba.org/ #3580
Hi David,
We'd like to address this for you, if possible. May I know:
- If you've been able to reproduce this?
- Approximately how many images are in your library?
- What type of image you performed the crop against (raw, JPEG, PNG, etc.)?
- The original resolution of the image you cropped?
-
Hi Duy,
We'd like to help you with this; can you provide us with more
information on how to reproduce it?
- What part of the application is this occurring in? Are you seeing poor
performance when zooming in on a single image, or is this when zooming
in on thumbnails in your library?
- If this
Hi,
Unfortunately, I'm unable to reproduce this in the most current version;
can you try the same operation in 0.9.3 and let us know if it still
happens?
If it does, can you try running it with GDB and post the stack dump
here?
--
You received this bug notification because you are a member of
Hi,
It sounds as if you may have encountered the problem discussed in this
thread: http://ubuntuforums.org/showthread.php?t=1520831.
If you try the solution in post #3, does it solve the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Shaswat,
I've set up Macbuntu with Compiz on my machine here in order to try to
reproduce this. Can you tell us what you were doing or what happened
right before the crash? I ran Shotwell in Macbuntu quite a bit last
week, but I didn't see anything unusual occur.
--
You received this bug
Hi,
Is this the problem in question? http://trac.yorba.org/ticket/3470
** Bug watch added: trac.yorba.org/ #3470
http://trac.yorba.org/ticket/3470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi again,
You'll be happy to know that we're already looking at how to address
this; please have a look at http://trac.yorba.org/ticket/2779.
** Bug watch added: trac.yorba.org/ #2779
http://trac.yorba.org/ticket/2779
--
You received this bug notification because you are a member of Ubuntu
Hi again,
That seems like it might be a very useful feature. I've added a ticket
in our database for this; please have a look at
http://trac.yorba.org/ticket/3449 .
** Bug watch added: trac.yorba.org/ #3449
http://trac.yorba.org/ticket/3449
--
You received this bug notification because you
Hi again,
Can you post a screenshot of what you see right before you publish?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745267
Title:
No option for publishing a selectiive picture from an
Hi,
This is a sound request; I've added it to our internal bug database at
http://trac.yorba.org/ticket/3451.
** Bug watch added: trac.yorba.org/ #3451
http://trac.yorba.org/ticket/3451
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I forgot to add that there is a workaround available in the current
version:
1. Choose the image you'd like to obtain the path to.
2. Choose 'View-Extended Information'.
3. In the extended information dialog, highlight the path to the file.
4. Secondary-click and choose 'Copy'.
The next time
Hi again,
One thing to note is that, because it is possible to alter an image via
Shotwell, the image you see in the application may be different than
what you end up copying. If we do implement this, we'll need to think
about what path should be given to the user, so that what they end up
Hi,
First off, thank you for taking time to use Shotwell and to report a bug
to us.
I'm not quite sure if I understand the problem, though - Shotwell
doesn't currently have an 'Album' feature, and it currently requires the
user to manually choose which pictures will be published. There isn't a
Hi,
It sounds like what you're requesting may already be implemented - when
you import new images, Shotwell remembers this, and navigating to 'Last
Import' will display the most recent ones.
Is this what you're looking for?
--
You received this bug notification because you are a member of
86 matches
Mail list logo
