I filed a ticket upstream at http://trac.yorba.org/ticket/3588 .
** Bug watch added: trac.yorba.org/ #3588
http://trac.yorba.org/ticket/3588
** Also affects: shotwell via
http://trac.yorba.org/ticket/3588
Importance: Unknown
Status: Unknown
--
You received this bug
Thanks for the log file and debug output. The stack trace reveals that
this is related to the global menu. Unfortunately I can't reproduce
this on Ubuntu Natty either in 0.9.2 or in trunk.
Do you see this crash every time you remove any tag from any picture?
Could you try the following? First
Thanks for the picture. I just tried to reproduce this again on Ubuntu
Natty, but was unsuccessful. Here's what I did:
1. Start Shotwell with an empty library: SHOTWELL_LOG=1 shotwell -d ~/foo.
2. In Nautilus, find the photo indicator_mockup.jpg that Jan attached above and
drag it into
I think the reporter is saying that zooming into images in general is
slower in 0.9 than in 0.8. Someone already filed a ticket upstream
saying he thought JPEG loading had slowed down, so let's consider this
another symptom of that:
http://trac.yorba.org/ticket/3536
** Bug watch added:
We at Yorba have tested the GNOME 3 background fix to make sure that
works on Natty as well as on GNOME 3 systems such as Fedora 15. But,
still, it's up to you whether to take Shotwell 0.9.3 in its entirety.
By the way, we are considering another bug fix release (0.9.4) in the
next week or two,
Thanks to all for their attention to this. I'll now close the upstream
bug. We're still undecided about whether to release a version 0.9.4,
but if we do we'll merge this fix in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yikes: this still occurs in 0.9.3 and in trunk. I'm surprised that
noone pointed this out before.
I've filed a bug upstream at http://trac.yorba.org/ticket/3540 . We'll
fix this for 0.10.
** Bug watch added: trac.yorba.org/ #3540
http://trac.yorba.org/ticket/3540
** Also affects: shotwell
Sebastien,
At Yorba, if try to reproduce a bug and are unsuccessful, we generally
close it, especially if only one user has reported it. If we kept such
bugs open, our bug database would grow larger and larger with lots of
bugs which we can do nothing about.
I do think, however, that we should
Sebastien,
We recently released Shotwell 0.9.3 including a fix for this bug. I
don't understand your question about blocking this fix - was it intended
for Shotwell developers, or for Shotwell packagers at Ubuntu? Can you
clarify?
--
You received this bug notification because you are a member
Thanks for the bug report. I've ticketed this upstream at
http://trac.yorba.org/ticket/3547
** Bug watch added: trac.yorba.org/ #3547
http://trac.yorba.org/ticket/3547
** Also affects: shotwell via
http://trac.yorba.org/ticket/3547
Importance: Unknown
Status: Unknown
--
You
Turns out the GConf mechanism *does* work on Natty/Unity; this was our
error. We'll fix this upstream right away.
** Changed in: shotwell (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is not reproducible, the original reporter found a solution and
it's not clear that it ever occurs with current versions of Shotwell
(the reporter was using 0.7). Marking as invalid.
** Changed in: shotwell (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Storing in XDG directories is ticketed upstream at
http://trac.yorba.org/ticket/421 .
As noted there, Shotwell isn't yet smart enough to automatically
regenerate missing thumbnails (that's
http://trac.yorba.org/ticket/2889), and we can't store thumbnails in a
cache directory until that
** Changed in: shotwell (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745831
Title:
shotwell crashed with SIGABRT in raise()
--
ubuntu-bugs mailing list
I'm seeing this too (on Fedora 15, actually). I've filed a bug upstream
here:
https://bugzilla.gnome.org/show_bug.cgi?id=648224
** Bug watch added: GNOME Bug Tracker #648224
https://bugzilla.gnome.org/show_bug.cgi?id=648224
--
You received this bug notification because you are a member of
lucas@yorba, can you investigate and comment on this? Is this a
Shotwell bug or an Ubuntu packaging bug, in your opinion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760978
Title:
Shotwell's
Thanks for the bug report. The filter options in the menu are supposed
to show the search bar automatically. Unfortunately, it seems that this
is broken if the search bar has never been visible in the current
Shotwell session.
I've ticketed this upstream at http://trac.yorba.org/ticket/3490 .
@Daniel: Yes. We (the Shotwell developers) are in touch with people at
Ubuntu and we believe there will be time to include Shotwell 0.9.2 in
Ubuntu 11.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've marked the upstream ticket as worksforme since Michael has said he
can't reproduce this in Shotwell 0.9 and since we have enough to do
trying to fix the bugs we *can* reproduce. :) If this rears its head
again then we can certainly reopen.
--
You received this bug notification because you
** Changed in: shotwell (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756592
Title:
shotwell crashed with SIGSEGV in
Here's a patch that fixes the build errors, assuming that you want to
stay with GNOME_COMPILE_WARNINGS(maximum) and fix all these errors in
place.
** Patch added: patch
https://bugs.launchpad.net/bamf/+bug/706703/+attachment/1978027/+files/fix_unused_variable_errors.patch
--
You received
I can't reproduce this. I tried upgrading from Shotwell 0.8.1 to
Shotwell 0.9. After the upgrade, filtering worked just fine.
- You're using the filter menu on the new Find toolbar, right?
- You said that the filter actions do nothing at all. So this means that
Shotwell always shows all
OK. Not a bug.
** Changed in: shotwell (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749893
Title:
Filter actions from menu or keyboard shortcuts do nothing
Public bug reported:
Binary package hint: compiz
On Natty, if any application in fullscreen mode opens a new window, then
the Unity panel and launcher will come to the foreground on top of the
fullscreen view. To see this, open gedit, choose View-Fullscreen, then
press Ctrl+F for Find. As the
I don't see this: on my Natty machine, the Shotwell menu appears in the
global menu. I installed a daily build recently.
Shotwell used to be blacklisted (i.e. excluded) from the global menu due
to some compability problems, but is no longer on the blacklist. It
looks like you upgraded from
We have a ticket for this upstream:
http://trac.yorba.org/ticket/2719
** Bug watch added: trac.yorba.org/ #2719
http://trac.yorba.org/ticket/2719
** Also affects: shotwell via
http://trac.yorba.org/ticket/2719
Importance: Unknown
Status: Unknown
--
You received this bug
Can you reproduce this crash? Does it occur every time you start
Shotwell, or did it only happen once?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741465
Title:
shotwell crashed with SIGABRT in
Ticketed upstream at http://trac.yorba.org/ticket/3413 .
** Bug watch added: trac.yorba.org/ #3413
http://trac.yorba.org/ticket/3413
** Also affects: shotwell via
http://trac.yorba.org/ticket/3413
Importance: Unknown
Status: Unknown
--
You received this bug notification
Ticketed upstream at http://trac.yorba.org/ticket/3413 .
** Bug watch added: trac.yorba.org/ #3413
http://trac.yorba.org/ticket/3413
** Also affects: shotwell via
http://trac.yorba.org/ticket/3413
Importance: Unknown
Status: Unknown
--
You received this bug notification
We have a ticket for this upstream:
http://trac.yorba.org/ticket/2748
** Bug watch added: trac.yorba.org/ #2748
http://trac.yorba.org/ticket/2748
** Also affects: shotwell via
http://trac.yorba.org/ticket/2748
Importance: Unknown
Status: Unknown
--
You received this bug
When you open the red eye tool, it displays a small circle which you can
move around the image to choose the spot where you want to fix red eye.
Unfortunately, when the photo is dark, the red eye circle can be hard to
see or practically invisible, which is confusing. I've ticketed this
upstream
You've reported two problems:
1. The adjust dialog [can't] be moved if you don't know about alt-
left_click-dnd.
You can simply click anywhere in the adjust dialog and drag the mouse to
move it. Does this not work for you?
2. The adjust dialog appears partially off the screen.
This is a
Ticketed upstream at http://trac.yorba.org/ticket/3438 .
** Bug watch added: trac.yorba.org/ #3438
http://trac.yorba.org/ticket/3438
** Also affects: shotwell via
http://trac.yorba.org/ticket/3438
Importance: Unknown
Status: Unknown
--
You received this bug notification
We didn't give the adjust window a title bar because we want it to feel
like a lightweight tool window that floats on top of the main window
while minimizing visual distraction. At some point we may move the
adjustments into a sidebar on the right like in some other photo apps,
though.
--
You
Oh, yes, I now see in this classic Ubuntu as well if I enable Compiz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744946
Title:
the adjust dialog should be a real dialog
--
ubuntu-bugs mailing
When you say the small icon in the right side view, I assume that you
mean the Videos icon in the Find toolbar at the top of the photos view -
yes?
I believe that we do show videos by default. If you run Shotwell on a
clean machine (e.g. after running 'gconftool --recursive-unset
Ticketed upstream at http://trac.yorba.org/ticket/3426 .
** Bug watch added: trac.yorba.org/ #3426
http://trac.yorba.org/ticket/3426
** Also affects: shotwell via
http://trac.yorba.org/ticket/3426
Importance: Unknown
Status: Unknown
--
You received this bug notification
I'm not quite sure I understand. Do you mean that when you click Events
to see one image for each event, the images don't have quite the same
resolution as the original image? That's this Shotwell bug:
http://trac.yorba.org/ticket/2613
Or do you mean something else?
** Bug watch added:
Public bug reported:
Binary package hint: shotwell
On Natty, windows contain a resize grip in the lower right-hand corner.
(This is actually a GTK 3 element which has been backported to GTK 2 in
Natty). Because Shotwell has no status bar, this resize grip overlaps
some visual elements. In
Yes. The fix was already present in Shotwell 0.8.90.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723465
Title:
auto import of photo's hangs infinately
--
ubuntu-bugs mailing list
Normal Ubuntu software updates provide only critical bug fixes and minor
improvements. If you want the latest versions of Shotwell or other
applications on the Ubuntu desktop, you'll need to upgrade to a newer
version of Ubuntu. You can do this through
System-Administration-Update Manager.
--
Yes - that version is pretty old now. We're made 3 releases since then
and are about to release 0.9. I'd recommend that you upgrade!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734714
Title:
Booxter,
just curious: Yorba's PPA already contains Shotwell 0.8 which includes
this fix, so why did you package 0.7.2 plus this fix for your own PPA?
I'd encourage anyone on Maverick who needs this fix to simply upgrade to
0.8 using Yorba's PPA.
https://launchpad.net/~yorba/+archive/ppa
--
The attached picture works fine in Shotwell on Natty with libexiv2
0.21.1 and libgexiv2 0.3.0. There were some crashing bugs in earlier
versions of libexiv2 that affected Shotwell users - see
http://dev.exiv2.org/issues/show/739
http://dev.exiv2.org/issues/show/752
I believe if you
- Are you sure that you have read permission on the images in question?
- What happens if you find the images in Nautilus and drag them into Shotwell?
- If you double click on them in Nautilus, what happens?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't understand this bug report. Did you export an image from
Shotwell by dragging it to the desktop? What happened differently from
what you expected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK. If you're having trouble upgrading libexiv2 and libgexiv2 feel free
to ask for help on the Shotwell mailing list (http://lists.yorba.org
/cgi-bin/mailman/listinfo/shotwell).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Michael, I've updated the Wikipedia page you mentioned to include
Shotwell as you suggested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/579804
Title:
Store/read tags inside photos
--
Omer,
we thought the newly expanded Shotwell preferences dialog would be OK
because it's not as tall as the Nautilus preferences dialog. Does that
dialog not fit on your screen either?
** Bug watch added: GNOME Bug Tracker #536187
https://bugzilla.gnome.org/show_bug.cgi?id=536187
--
You
Aha - I see that's considered a Nautilus bug:
https://bugzilla.gnome.org/show_bug.cgi?id=536187
** Bug watch added: trac.yorba.org/ #3320
http://trac.yorba.org/ticket/3320
** Also affects: shotwell via
http://trac.yorba.org/ticket/3320
Importance: Unknown
Status: Unknown
--
I've ticketed this at
http://trac.yorba.org/ticket/3320
Possibly too late to fix this for 0.9, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/732710
Title:
shotwell preference window is a
Changes from Shotwell 0.8.1 to 0.8.90 include the following:
- a search box that finds photos by name
- buttons that filter photos by type (photo, video, RAW) or flag state
- support for photos in TIFF format
- support for plugins, which can add publishing destinations or new slideshow
Robin,
thanks for the bug report. Are you able to reproduce this - in other
words, can you make it happen again? If not, then unfortunately there
may not be much we can do since the crash report you attached doesn't
give us enough information to proceed with.
If you can reproduce this, could
Note log file attached to the upstream ticket and continued discussion
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723465
Title:
auto import of photo's hangs infinately
--
ubuntu-bugs
Thanks for the backtrace and log file. It looks like some RAW file is
causing libraw to crash, but unfortunately the files you attached don't
reveal which RAW file that is.
As a next debugging step, let's try the following. You'll need to be
able to reproduce the crash again. If necessary, you
There is no Shotwell screensaver. This is a documentation bug. The
page with the wrong information is here:
https://help.ubuntu.com/10.10/musicvideophotos/C/photos-slideshow.html
I suspect that an older version of this page used to describe F-Spot,
and someone simply replaced the word F-Spot
I've ticketed this upstream here:
http://trac.yorba.org/ticket/3224
** Bug watch added: trac.yorba.org/ #3224
http://trac.yorba.org/ticket/3224
** Also affects: shotwell via
http://trac.yorba.org/ticket/3224
Importance: Unknown
Status: Unknown
--
You received this bug
I'm also sorely missing a system monitor applet for Unity. An indicator
applet might be OK. As another approach, perhaps System Monitor could
show a graph indicating CPU activity inside its icon in the Unity
Launcher. (That's how it works on a Mac, by the way.)
--
You received this bug
Thanks for the bug report. Are you able to reproduce this crash? If
so, could you possibly follow the instructions in the Shotwell FAQ
(http://trac.yorba.org/wiki/Shotwell/FAQ) to generate a backtrace and
log file and attach them to this bug?
--
You received this bug notification because you
Louis, you said that this bug is very low on anyone's priority list
but it affects me too and is a major nuisance. At home, I always boot
up my laptop with the lid closed and an external monitor on. GDM fails
to set the correct resolution, and the resolution is still wrong after I
log in: I have
Jan,
thanks for the bug report. Could you follow the instructions in the
Shotwell FAQ (http://trac.yorba.org/wiki/Shotwell/FAQ) to generate a
stack trace and log file and attach them to this bug? That will help us
track down what's wrong. Thanks!
** Changed in: shotwell (Ubuntu)
Dmitry,
Shotwell is known to not work with dates before 1969 - see
http://trac.yorba.org/ticket/3040 . I think that's probably the cause
of the sorting problems you're seeing.
** Bug watch added: trac.yorba.org/ #3040
http://trac.yorba.org/ticket/3040
--
You received this bug notification
Jan,
ah, yes - I see the log file now. Thanks.
1) there's a known metadata writing crash which was fixed in the very
latest release of libexiv2 - see http://trac.yorba.org/ticket/3104 . If
possible, could you build and install libexiv2 0.21.1 and also gexiv2
0.3.0, and then see if the crash
gokhanakat,
what did you do to make the crash happen? Does it happen every time you
run Shotwell? Can you reproduce the crash at will?
** Changed in: shotwell (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jan,
this fix will be included in Shotwell 0.9, which we're planning to
release some time in March. You'll be able to install Shotwell 0.9 from
the Yorba PPA at that time. Glad you're excited to have this fix! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Matt,
thanks for this latest information. Actually, I think what we need to
be able to reproduce this bug is to see the *exact* dimensions of the
Shotwell window in its maximized state on your machine. So could you
possibly do the following?
1. Start Shotwell and maximize the window.
2. Check
I can confirm this behavior. To make the above steps a bit more
precise:
1. Double-click a JPEG file on your desktop (or in any other Nautilus window).
Eye of GNOME will appear and display the image.
2. In Eye of GNOME, click Edit Image. The Shotwell image viewer will appear.
3. Crop the
Yesterday I asked Robert Ancell from Canonical to update libraw to 0.13
in natty and he went ahead and did that. (I'm not sure whether the
Debian update you mentioned is related to that.) Because libraw is
statically linked into Shotwell, Ubuntu will also need to rebuild
Shotwell for Natty now
This is a reasonable request. I've filed a ticket upstream here:
http://trac.yorba.org/ticket/3159
Glad you like Shotwell! :)
** Bug watch added: trac.yorba.org/ #3159
http://trac.yorba.org/ticket/3159
** Also affects: shotwell via
http://trac.yorba.org/ticket/3159
Importance:
Matt,
thanks for the additional information. One more question: what is your
display resolution in pixels? (You might be able to see it in
System-Preferences-Monitors, or by running 'xrandr' on the command
line.)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can't reproduce this problem in the current Shotwell trunk with the
test database posted in #7. Dmitri, can you update to Shotwell 0.8.1
(or even the current trunk) and confirm that you still see this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been reported upstream at http://trac.yorba.org/ticket/2246 for
different cameras. It would help us if you could attach a RAF photo
either to this ticket or the upstream ticket - that will help us make
sure that when we fix this bug we'll correctly support your camera as
well. The
Timo,
thanks for this latest ARW file. With this file, I can reproduce your
crash when Shotwell is built with libraw 0.9 (the version currently in
Ubuntu 11.04). When I build Shotwell with libraw 0.13 (the latest
release), however, your photo imports without a problem. So I believe
this bug
Phyrenze,
I'm not sure why you wrote thanks - to be clear:
1) we still aren't able to open your latest screenshot. As Omer pointed
out, it has an unusual name which might be the problem.
2) as I pointed out in #8, we still don't really understand what you're
experiencing. Perhaps the
Matt,
1. does the flicker happen only while the progress bar is advancing, or
even after the progress bar is complete?
2. If the flicker does stop once the progress bar is complete, are you
then able to select images and import them, or must you click another
entry in the sidebar as you
*** This bug is a duplicate of bug 675068 ***
https://bugs.launchpad.net/bugs/675068
OK, so this bug is definitely a duplicate of bug 675068. I'll mark it
as such.
Sorry to hear you've had trouble installing Shotwell 0.8. It sounds
like you may have a permissions problem with /etc/sudoers.
I can't reproduce this with Natty Alpha 2 and the current Shotwell
trunk. I built Shotwell in Natty Alpha 2 and the crop tool seems to
work normally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Eden7c,
ok - you were confused by the command in the Shotwell FAQ. It looked
like this:
% SHOTWELL_LOG=1 gdb ./shotwell 21 | tee shotwell.gdb
You weren't supposed to type the % character! That was merely an
indication of a shell prompt. Some older UNIX shells used a '%' instead
of a '$'.
Great to hear about this progress!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/649340
Title:
in Unity, top-level Shotwell menu does not change when user switches
views
--
ubuntu-bugs mailing
It's OK - we've all been there. :) Here's what's going on. The
command line in the FAQ looked like this:
$ SHOTWELL_LOG=1 gdb ./shotwell 21 | tee shotwell.gdb
. means the current directory, so ./shotwell means the shotwell
program in the current directory. Evidently when you ran that command
OK, great - we finally have a stack trace (i.e. shotwell.gdb), which
lets us see what's going on. This now looks like a duplicate of bug
675068, which occurred in Shotwell 0.7 whenever the Shotwell library
contained files remotely accessed via ssh. That bug was fixed in
Shotwell 0.8. So:
1.
Omar: We are not planning an 0.7.3 release at this time. (Our
development efforts are currently focused on 0.9, which we plan to
release in time for Ubuntu 11.04 this spring.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Omer: oops - I spelled your name wrong in my previous comment. Sorry
for the typo! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669263
Title:
backgroundcolor left pane does not match GTK
Thanks for the bug report. Could you generate a GDB backtrace and log
file following the instructions in the Shotwell FAQ
(http://trac.yorba.org/wiki/Shotwell/FAQ) and post them here? That will
help us investigate the problem. Thanks!
** Changed in: shotwell (Ubuntu)
Status: New =
I've looked through the log file and I don't really see any signs of
trouble. It looks like Shotwell was importing photos from 8:14 until
8:48. Then there are 10 minutes of silence in the log file and after
that, at 8:58, Shotwell reported that a camera was detected.
Did Shotwell hang during
*** This bug is a duplicate of bug 623029 ***
https://bugs.launchpad.net/bugs/623029
This is a duplicate of bug 623029. The crash is a bug in the GNOME
global menu plugin you're using. See bug 623029 for more details. You
might have better luck using the new Ubuntu global menu.
** This
The fix was in this commit
http://trac.yorba.org/changeset/2370
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669263
Title:
backgroundcolor left pane does not match GTK Theme color
--
Hm - this looks like some sort of library versioning problem. What does
this command print?
$ dpkg -l 'libgexiv2*'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709892
Title:
shotwell crashes on
It looks like you have libgexiv2 0.2.0 installed, but the library is
missing a symbol for some reason. Odd.
- Have you built Shotwell and/or gexiv2 yourself, or only installed
binary packages?
- Have you used the Yorba PPA, or have you gotten packages only from the
Ubuntu repositories?
- Could
Jan,
the entries considered invalid errors are harmless - see
http://trac.yorba.org/ticket/1872 . They should go away once you update
to a newer version of the libexiv2 library.
The hang you're experiencing is a bigger problem. Could you try
importing again while generating a log file as
Actually I misspoke: the entries considered invalid errors won't go
away merely as a result of updating libexiv2. They are harmless,
though. We're working on making them go away in a future Shotwell
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Jan,
you asked if that was correct - that depends on what you did, exactly.
This is incorrect:
$ SHOTWELL_LOG=1
$ shotwell
If you want a UNIX shell to pass a variable to a command, you need to do
either of these:
$ SHOTWELL_LOG=1 shotwell
or
$ export SHOTWELL_LOG=1
$ shotwell
--
You
OK - our engineers have looked at the patch and it looks OK. I'll
emphasize that we haven't built or tested it, however - we do lots of
testing on our official releases but if you guys want to cherry pick
individual bug fixes then you should do some testing yourselves. I
doubt this is a
Rogério,
Thanks for your suggestions. I've added your comments to the upstream
ticket as well.
By the way, for some information about how to back up your Shotwell
library, see the Shotwell FAQ at http://trac.yorba.org/wiki/Shotwell/FAQ
.
--
You received this bug notification because you are a
I agree that Shotwell should do this. In fact, I thought we had already
implemented this, but I was wrong. I've ticketed this upstream here:
http://trac.yorba.org/ticket/3132
** Bug watch added: trac.yorba.org/ #3132
http://trac.yorba.org/ticket/3132
** Also affects: shotwell via
Thanks for the suggestion. There's already a ticket for this upstream:
http://trac.yorba.org/ticket/3090
** Bug watch added: trac.yorba.org/ #3090
http://trac.yorba.org/ticket/3090
** Also affects: shotwell via
http://trac.yorba.org/ticket/3090
Importance: Unknown
Status:
Which model of Nokia phone is it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705667
Title:
problem with open fotos : no encuentra el archivo de origen
--
ubuntu-bugs mailing list
Brett,
I doubt that your bug is the same as this one, since this one only
occurred with memory cards, not when attaching a camera.
I still don't see what trouble you're having with Shotwell. When you
attach a camera, Shotwell says that it needs to unmount the camera in
order to access it;
I'm not sure I completely understand. You have several different
cellphones, and you're not able to import photos into Shotwell from any
of them?
Also, unfortunately I can't open the screenshot you attached to this
ticket - when I click it, I see a message There’s no page with this
address in
Michael,
Shotwell 0.8.1 will run on Lucid, but neither the Ubuntu repositories
nor the Yorba PPA contain Shotwell 0.8.1 for Lucid - you need to build
it yourself. See the instructions on the Yorba web site, and feel free
to ask on the Shotwell mailing list if you're having trouble building.
--
601 - 700 of 838 matches
Mail list logo
