I can't reproduce this in the trunk build of Shotwell on Natty. I'm not
running Unity, however. Are you running Shotwell in Unity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697436
Title:
[Natt
The ticket for using a RAW file's embedded JPEG is actually
http://trac.yorba.org/ticket/1771 , not #3041 as listed in the comment
above.
** Bug watch added: trac.yorba.org/ #1771
http://trac.yorba.org/ticket/1771
--
You received this bug notification because you are a member of Ubuntu
Bugs,
To be clear, it sounds like you're asking for an option which would
cause Shotwell to ignore RAW files completely. If you select this
option then Shotwell would never import RAW files, and if you select
this option with an existing library then Shotwell would discard all
existing RAW files in the
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 upstre
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 has
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 screens
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 described
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: Unkno
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
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 image
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 th
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 subs
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, w
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 t
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
--
ubuntu-bugs
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 s
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 desc
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 receive
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 particula
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.
https://bu
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 Theme
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 => Inco
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 thi
*** 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 bu
Eden7c,
ok - you were confused by the command in the Shotwell FAQ. It looked
like this:
% SHOTWELL_LOG=1 gdb ./shotwell 2>&1 | 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 '$'. I
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 l
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 2>&1 | tee shotwell.gdb
"." means the current directory, so "./shotwell" means the shotwell
program in the current directory. Evidently when you ran that co
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. Are
Gustaf,
ha - that's a useful hack. I work on the Shotwell team and I never
thought of that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652158
Title:
cant do red eye removal while zoomed
--
ub
It turns out that this issue is specific to the Russian translation,
which hasn't provided a translation for Shotwell's time format. I've
ticketed this here:
http://trac.yorba.org/ticket/2958
** Bug watch added: trac.yorba.org/ #2958
http://trac.yorba.org/ticket/2958
--
You received this b
Alejandro,
the trunk build of Shotwell now lets you specify permissions settings
when you create a Facebook album, so I think this solves the problem.
This was http://trac.yorba.org/ticket/1988 . This feature will be in
the upcoming 0.8 release.
** Bug watch added: trac.yorba.org/ #1988
http
We've now fixed this in the Russian translation upstream. The fix will
be present in the 0.8 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689055
Title:
Shotwell doesn't respect system loc
Agreed: we should display a better error message in this situation.
I've ticketed this upstream here:
http://trac.yorba.org/ticket/2979
** Bug watch added: trac.yorba.org/ #2979
http://trac.yorba.org/ticket/2979
** Also affects: shotwell via
http://trac.yorba.org/ticket/2979
Importance
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)
Status:
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 goe
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 notific
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 ar
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 hav
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 notifica
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 wi
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 Shotwe
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: trac.yor
Avi,
I'm not sure I understand, In what sense does the second crop operation
undo the first? When I follow your steps to reproduce, then when I
click 'crop' for the second time, Shotwell displays the crop rectangle I
chose when I first cropped the image. In other words, after I press
'crop' the
Thanks for the screencast. The behavior in the screencast is expected
and is how cropping is intended to work: when you press Crop the second
time, Shotwell once again displays the entire image and displays the
crop rectangle you chose the first time so that you can adjust it as you
like. It's st
Endomancer,
we fixed this bug in Shotwell 0.10, which was released just yesterday.
I suggest you upgrade to 0.10. The Shotwell web site will tell you how
to do that:
http://yorba.org/shotwell/install/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
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 notification
** Bug watch added: trac.yorba.org/ #3140
http://trac.yorba.org/ticket/3140
** Also affects: shotwell via
http://trac.yorba.org/ticket/3140
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
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, s
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 desk
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
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 functionali
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.
https://
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 b
** 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
publishing_rest_support_session_const
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 .
We
@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.
https://bugs.launchpad.net/bugs
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.
--
Timo,
to be clear, if you start Shotwell with an empty library (e.g. 'shotwell
-d ~/foo') and then import the single ARW file you attached to this
ticket, does the SIGSEGV still occur?
adam
** Changed in: shotwell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Phyrenze,
what kind of cell phone are you using?
--
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 lis
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 mai
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
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 s
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 re
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.
https:/
*** 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.
https://bugs.launchpad.net/bugs/6974
This sounds like a temporary network problem. Now that a couple of days
have passed, can you try again and let us know whether you still see
this error?
--
Cant logint to facebook auth
https://bugs.launchpad.net/bugs/671904
You received this bug notification because you are a member of Ubuntu
Bu
@Peter-Alexander: This feature has been implemented in trunk, is
optional, and is off by default. It can currently be enabled via a
command-line option, and in the next few days we'll be adding a
preferences checkbox you can use to enable the feature if you want.
By the way, in Shotwell 0.9 we're
Do the photos remain in the Missing view even after you restart
Shotwell?
--
files on a shared (smb) device remain in "missing files" even when device
becomes available again
https://bugs.launchpad.net/bugs/673049
You received this bug notification because you are a member of Ubuntu
Bugs, which
Dmitry,
thanks for your latest post. I just tried creating a few photos with
older dates (using exiv2 to set their timestamps) and I couldn't see any
problem sorting them in Shotwell, so I'm not sure that the old dates are
the problem.
I also tried running Shotwell with your database archive, bu
I suspect you've hit this bug:
http://trac.yorba.org/ticket/2776
Can you try uninstalling the flashplugin-installer package, and let us
know whether that fixes the crash?
** Bug watch added: trac.yorba.org/ #2776
http://trac.yorba.org/ticket/2776
--
Shotwell Photomanager crashes when you s
I've ticketed this upstream here:
http://trac.yorba.org/ticket/2807
** Bug watch added: trac.yorba.org/ #2807
http://trac.yorba.org/ticket/2807
** Also affects: shotwell via
http://trac.yorba.org/ticket/2807
Importance: Unknown
Status: Unknown
--
crop cancels zoom
https://bugs
Worth reading:
http://www.ubuntu.com/community/conduct
--
Multiple-tag research is not available
https://bugs.launchpad.net/bugs/625331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
This bug is known upstream:
http://trac.yorba.org/ticket/2221
** Bug watch added: trac.yorba.org/ #2221
http://trac.yorba.org/ticket/2221
** Also affects: shotwell via
http://trac.yorba.org/ticket/2221
Importance: Unknown
Status: Unknown
--
Exporting an adjusted Raw DNG file t
Thanks for the bug report. I've filed a ticket upstream here:
http://trac.yorba.org/ticket/2817
** Bug watch added: trac.yorba.org/ #2817
http://trac.yorba.org/ticket/2817
** Also affects: shotwell via
http://trac.yorba.org/ticket/2817
Importance: Unknown
Status: Unknown
--
S
To be clear, when you return to the browser view Shotwell does select
the last viewed photo (at least in my testing). It does not, however,
scroll to make that photo visible, and it should.
I've ticketed this upstream at http://trac.yorba.org/ticket/2644 .
** Bug watch added: trac.yorba.org/ #2
Yes, this is potentially confusing.
One possible solution would be to unify the Shotwell and GNOME trashes;
see http://trac.yorba.org/ticket/2645 .
** Bug watch added: trac.yorba.org/ #2645
http://trac.yorba.org/ticket/2645
** Also affects: shotwell via
http://trac.yorba.org/ticket/2645
Good point. I've ticketed this upstream at
http://trac.yorba.org/ticket/2647
** Bug watch added: trac.yorba.org/ #2647
http://trac.yorba.org/ticket/2647
** Also affects: shotwell via
http://trac.yorba.org/ticket/2647
Importance: Unknown
Status: Unknown
--
After moving image t
** Also affects: shotwell via
http://trac.yorba.org/ticket/2269
Importance: Unknown
Status: Unknown
--
Shotwell makes USB mouse flaky
https://bugs.launchpad.net/bugs/555408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
bmhm,
Glad you're willing to help out. Could you do the following?
1. Can you disconnect the active USB hub and plug the mouse into your
computer directly? In that case, does the problem still occur?
2. Run this command:
$ sudo lsusb -v > usb.txt
Then attach the usb.txt file to this ticket (
Actually, please either attach to this ticket or send to
shotw...@yorba.org so that other Shotwell developers can take a look
too. Thanks!
--
Incorrect sorting of photos
https://bugs.launchpad.net/bugs/665602
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Michael,
in the situation you described, you can do the following today:
1. In Nautilus, open the folder containing the 1501 pictures.
2. Select the 1 picture which you've just added and drag it into Shotwell to
import it.
Is that not good enough?
--
subfolder import
https://bugs.launchpad.ne
Thanks for the bug report. This is a known bug:
http://trac.yorba.org/ticket/2647
We hope to fix this bug for the Shotwell 0.8 release.
** Bug watch added: trac.yorba.org/ #2647
http://trac.yorba.org/ticket/2647
** Also affects: shotwell via
http://trac.yorba.org/ticket/2647
Importan
Thanks for the bug report. I can reproduce this too. I thought we had
fixed this (see http://trac.yorba.org/ticket/2483), but that fix seems
to be incomplete. I've reopened that ticket and we'll readdress this
for Shotwell 0.8.
** Bug watch added: trac.yorba.org/ #2483
http://trac.yorba.org/
Actually Shotwell does have this feature. When you export a photo using
File->Export, Shotwell lets you specify a new width or height for the
photo. Similarly, when you use Shotwell to open a single photo
directly, the File->Save As command lets you specify a width or height
for scaling.
--
Sho
We (Yorba) are considering issuing a Shotwell 0.7.3 release soon with this
and a small number of other fixes. If/when that happens, we hope that
Ubuntu will push it to all 10.10 users.
2010/10/24 Joshua Lückers <631...@bugs.launchpad.net>
> It seems that they have fixed the bug upstream. Any ETA
@Ketil: This bug is known, and is fixed in trunk. See the (new and
incomplete) Shotwell FAQ at http://trac.yorba.org/wiki/Shotwell/FAQ .
@A.K.Karthikeyan: You could alternatively follow the backtrace
instructions in the Shotwell FAQ at
http://trac.yorba.org/wiki/Shotwell/FAQ . You may find these
I've ticketed this upstream at http://trac.yorba.org/ticket/2700 .
** Bug watch added: trac.yorba.org/ #2700
http://trac.yorba.org/ticket/2700
** Also affects: shotwell via
http://trac.yorba.org/ticket/2700
Importance: Unknown
Status: Unknown
--
Rotate keys are bad for many kin
Hadmut: Good point. I don't know how commonly cameras embed a full-size
JPEG, but for such cameras it would indeed be nice to bypass RAW
conversion in Shotwell. See the Shotwell ticket
http://trac.yorba.org/ticket/1771 , which is related.
** Bug watch added: trac.yorba.org/ #1771
http://trac
Sam,
there was a typo in the command line Jim suggested. It should be
$ SHOTWELL_LOG=1 gdb shotwell 2>&1 | tee shotwell.gdb
Could you try again, and then attach shotwell.gdb and
~/.cache/shotwell/shotwell.log to this ticket?
--
Shotwell crashes if disk with images is not mounted
https://bugs.
Right. This is known upstream here:
http://trac.yorba.org/ticket/2307
** Bug watch added: trac.yorba.org/ #2307
http://trac.yorba.org/ticket/2307
** Also affects: shotwell via
http://trac.yorba.org/ticket/2307
Importance: Unknown
Status: Unknown
--
can't import from a sub dir
This is not a bug. The menu items you're looking out are disabled since
you haven't selected any photos. If you import photos and select them,
these menu items will appear normal.
--
menus have black fonts and are difficult to see
https://bugs.launchpad.net/bugs/659260
You received this bug not
Daniel: Yes, we've implemented this capability in the trunk and it will
be present in Shotwell 0.8, which we're planning to release in November.
If you want to try this in the trunk build, you'll need to run Shotwell
with the --autocommit-metadata command-line option, which tells Shotwell
to save t
701 - 800 of 838 matches
Mail list logo
