From jaakko.luttinen at iki.fi Thu Nov 1 12:04:16 2012 From: jaakko.luttinen at iki.fi (Jaakko Luttinen) Date: Thu, 01 Nov 2012 14:04:16 +0200 Subject: [Shotwell] Destructive editing? Message-ID: <50926540.3030003@iki.fi> Hi! Shotwell performs non-destructive editing. Is there a way to actually perform all the edits I have done to my photos? I didn't know about non-destructiveness and I had edited a several photos and I would like the photo files to be really edited. It would be nice if there was something like "Save changes to the file" for a photo or "Save all modified photos" to save all the changes you have to in your whole library. Thanks! Jaakko From lucas at yorba.org Thu Nov 1 13:11:42 2012 From: lucas at yorba.org (Lucas Beeler) Date: Thu, 1 Nov 2012 14:11:42 +0100 Subject: [Shotwell] Destructive editing? In-Reply-To: <50926540.3030003@iki.fi> References: <50926540.3030003@iki.fi> Message-ID: Hi Jaakko, One day, we would like Shotwell to keep a fully-transformed version of every photo on disk, which is to say that all your edits would be "in the file." We even have an open feature request for this functionality in our bug tracking database here: http://redmine.yorba.org/issues/1798. Until we implement this feature, there is a work-around that most users find straightforward. If you want a file on disk containing all of the edits you've applied to a photo, just export the photo using the "File" > "Export..." menu option. Shotwell will write all the edits into a photo file of a type and size of your choosing. Cheers, Lucas On Thu, Nov 1, 2012 at 1:04 PM, Jaakko Luttinen wrote: > Hi! > > Shotwell performs non-destructive editing. Is there a way to actually > perform all the edits I have done to my photos? I didn't know about > non-destructiveness and I had edited a several photos and I would like the > photo files to be really edited. > > It would be nice if there was something like "Save changes to the file" for > a photo or "Save all modified photos" to save all the changes you have to in > your whole library. > > Thanks! > Jaakko > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jaakko.luttinen at iki.fi Thu Nov 1 13:38:49 2012 From: jaakko.luttinen at iki.fi (Jaakko Luttinen) Date: Thu, 01 Nov 2012 15:38:49 +0200 Subject: [Shotwell] Destructive editing? In-Reply-To: References: <50926540.3030003@iki.fi> Message-ID: <50927B69.7010207@iki.fi> Great, thanks! It'd be great if Export had an option such as "Overwrite original files". The user could either select custom location (like now) or choose to overwrite files (no need to browse and find the correct file locations, which is annoying and time consuming). Best, Jaakko On 2012-11-01 15:11, Lucas Beeler wrote: > Hi Jaakko, > > One day, we would like Shotwell to keep a fully-transformed version of > every photo on disk, which is to say that all your edits would be "in > the file." We even have an open feature request for this functionality > in our bug tracking database here: > http://redmine.yorba.org/issues/1798. > > Until we implement this feature, there is a work-around that most > users find straightforward. If you want a file on disk containing all > of the edits you've applied to a photo, just export the photo using > the "File" > "Export..." menu option. Shotwell will write all the > edits into a photo file of a type and size of your choosing. > > Cheers, > Lucas > > On Thu, Nov 1, 2012 at 1:04 PM, Jaakko Luttinen wrote: >> Hi! >> >> Shotwell performs non-destructive editing. Is there a way to actually >> perform all the edits I have done to my photos? I didn't know about >> non-destructiveness and I had edited a several photos and I would like the >> photo files to be really edited. >> >> It would be nice if there was something like "Save changes to the file" for >> a photo or "Save all modified photos" to save all the changes you have to in >> your whole library. >> >> Thanks! >> Jaakko >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From clanlaw at googlemail.com Sat Nov 3 13:49:42 2012 From: clanlaw at googlemail.com (Colin Law) Date: Sat, 3 Nov 2012 13:49:42 +0000 Subject: [Shotwell] Repeated date events when using exiftool to set the date Message-ID: I am scanning slides into png files then using exiftool to set the date on a number of slides then importing from folder to get them into Shotwell. The command I am using to set the date is, for example, exiftool -overwrite_original -DateTimeOriginal="1975:01:01 00:00:00" * and the photos appear in shotwell in an event Wed 1 Jan, 1975, which is correct. However, if I then scan some more slides and set the same date on them and import them then instead of going into the original event a new one, apparently identical, is created. So then I have two events for that date. Is this a known issue? I am using Shotwell 0.13.0 on Ubuntu 12.10. 0.13.1 has still not appeared in the repos :( From joseph.bylund at gmail.com Sat Nov 3 14:03:26 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Sat, 03 Nov 2012 10:03:26 -0400 Subject: [Shotwell] Repeated date events when using exiftool to set the date In-Reply-To: References: Message-ID: <5095242E.2080701@gmail.com> Colin, I believe this is the ticket related to the behavior you describe http://redmine.yorba.org/issues/3565 , there are also a few related tickets which are subsumed as duplicates. It's ticketed for 0.14, so hopefully you'll see this soon. In the meanwhile you can merge the newly created "duplicate" event into the existing one. hope that helps, -Joe On 11/03/2012 09:49 AM, Colin Law wrote: > I am scanning slides into png files then using exiftool to set the > date on a number of slides then importing from folder to get them into > Shotwell. > The command I am using to set the date is, for example, > > exiftool -overwrite_original -DateTimeOriginal="1975:01:01 00:00:00" * > > and the photos appear in shotwell in an event Wed 1 Jan, 1975, which is correct. > However, if I then scan some more slides and set the same date on them > and import them then instead of going into the original event a new > one, apparently identical, is created. So then I have two events for > that date. > > Is this a known issue? I am using Shotwell 0.13.0 on Ubuntu 12.10. > 0.13.1 has still not appeared in the repos :( > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From clanlaw at googlemail.com Sat Nov 3 15:21:21 2012 From: clanlaw at googlemail.com (Colin Law) Date: Sat, 3 Nov 2012 15:21:21 +0000 Subject: [Shotwell] Repeated date events when using exiftool to set the date In-Reply-To: <5095242E.2080701@gmail.com> References: <5095242E.2080701@gmail.com> Message-ID: On 3 November 2012 14:03, Joseph Bylund wrote: > Colin, > I believe this is the ticket related to the behavior you describe > http://redmine.yorba.org/issues/3565 , there are also a few related tickets > which are subsumed as duplicates. It's ticketed for 0.14, so hopefully > you'll see this soon. > In the meanwhile you can merge the newly created "duplicate" event into the > existing one. Yes, I see that is it, thanks. I had assumed it was something to do with the way I was setting the date. I had worked out how to merge the events. Thanks again Colin > hope that helps, > -Joe > > > On 11/03/2012 09:49 AM, Colin Law wrote: >> >> I am scanning slides into png files then using exiftool to set the >> date on a number of slides then importing from folder to get them into >> Shotwell. >> The command I am using to set the date is, for example, >> >> exiftool -overwrite_original -DateTimeOriginal="1975:01:01 00:00:00" * >> >> and the photos appear in shotwell in an event Wed 1 Jan, 1975, which is >> correct. >> However, if I then scan some more slides and set the same date on them >> and import them then instead of going into the original event a new >> one, apparently identical, is created. So then I have two events for >> that date. >> >> Is this a known issue? I am using Shotwell 0.13.0 on Ubuntu 12.10. >> 0.13.1 has still not appeared in the repos :( >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > From jaakko.luttinen at iki.fi Sat Nov 3 16:56:44 2012 From: jaakko.luttinen at iki.fi (Jaakko Luttinen) Date: Sat, 03 Nov 2012 18:56:44 +0200 Subject: [Shotwell] EXIF: Copyright, license and location? Message-ID: <50954CCC.5060509@iki.fi> Hi! Is it possible to modify the following metadata using Shotwell: Copyright, license and location? I couldn't find a way.. At least copyright would be very important metadata for photos. Anyway, Shotwell seems great, thanks! Regards, Jaakko From clinton at yorba.org Sat Nov 3 18:36:10 2012 From: clinton at yorba.org (Clinton Rogers) Date: Sat, 3 Nov 2012 11:36:10 -0700 Subject: [Shotwell] EXIF: Copyright, license and location? In-Reply-To: <50954CCC.5060509@iki.fi> References: <50954CCC.5060509@iki.fi> Message-ID: Hi Jaakko, Currently, there isn't a way to modify copyright, license or GPS data from within Shotwell itself, although they are read in. Exposing a way to change these is certainly possible; I'll add a ticket for this shortly. With regard to location, though, if you simply want a human-readable location attached to each photo, the tagging feature may be of use to you. Thank you for using Shotwell! Cheers, -c On 03/11/2012, Jaakko Luttinen wrote: > Hi! > > Is it possible to modify the following metadata using Shotwell: > Copyright, license and location? I couldn't find a way.. > > At least copyright would be very important metadata for photos. > > Anyway, Shotwell seems great, thanks! > > Regards, > Jaakko > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -- public struct Box { public static const int HAND_GRENADES = 12; -- from shotwell/src/Box.vala From jaakko.luttinen at iki.fi Sun Nov 4 15:17:47 2012 From: jaakko.luttinen at iki.fi (Jaakko Luttinen) Date: Sun, 04 Nov 2012 17:17:47 +0200 Subject: [Shotwell] Modifying tags of multiple photos Message-ID: <5096871B.6000808@iki.fi> Hi! It seems that Shotwell disables "Modify tags" if you select multiple photos. I understand the reason for this when the photos have different tags, but if they have the same tags, it would be efficient to be able to edit the tags. Is the only solution to modify the tags one photo at a time or find the photos from the tag collection and remove the tag in there? Just an idea: It would be easy to modify the tags of several photos (even if they have different set of tags), if the "tag modification" dialog had the tags as check boxes: Checked if they all have the tag and grey if only some have it.. Or something like that.. Anyway, if they have the same tags, the existing dialog would suffice, so it would be simple. What would be the correct place to make suggestions and feature requests? Regards, Jaakko From jim at yorba.org Mon Nov 5 20:54:44 2012 From: jim at yorba.org (Jim Nelson) Date: Mon, 05 Nov 2012 20:46:44 -0008 Subject: [Shotwell] EXIF: Copyright, license and location? In-Reply-To: References: <50954CCC.5060509@iki.fi> Message-ID: <50982797.2ad3440a.53cd.ffffda4f@mx.google.com> I'll jump in here and add that there is a ticket for this: http://redmine.yorba.org/issues/3103 -- Jim On Sat, Nov 3, 2012 at 11:36 AM, Clinton Rogers wrote: Hi Jaakko, Currently, there isn't a way to modify copyright, license or GPS data from within Shotwell itself, although they are read in. Exposing a way to change these is certainly possible; I'll add a ticket for this shortly. With regard to location, though, if you simply want a human-readable location attached to each photo, the tagging feature may be of use to you. Thank you for using Shotwell! Cheers, -c On 03/11/2012, Jaakko Luttinen wrote: > Hi! > > Is it possible to modify the following metadata using Shotwell: > Copyright, license and location? I couldn't find a way.. > > At least copyright would be very important metadata for photos. > > Anyway, Shotwell seems great, thanks! > > Regards, > Jaakko > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -- public struct Box { public static const int HAND_GRENADES = 12; -- from shotwell/src/Box.vala _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Mon Nov 5 21:09:00 2012 From: jim at yorba.org (Jim Nelson) Date: Mon, 05 Nov 2012 21:01:00 -0008 Subject: [Shotwell] Modifying tags of multiple photos In-Reply-To: <5096871B.6000808@iki.fi> References: <5096871B.6000808@iki.fi> Message-ID: <50982aef.47dd440a.05c1.ffffe7ad@mx.google.com> Jaakko, What you're describing is something we've long thought about. ?Tag management is a complex beast, and there's a lot of fine detail work getting it right. In general, if you want to propose a feature or report a bug for Shotwell, go to http://redmine.yorba.org/projects/shotwell. ?You'll need to register an account to add or modify tickets. We do have two tickets on this subject: http://redmine.yorba.org/issues/3715 http://redmine.yorba.org/issues/2382 Feel free to comment or watch these tickets for developments. ?I'm marking them both for 0.14, although I can't promise they'll be fixed in that cycle. -- Jim On Sun, Nov 4, 2012 at 7:17 AM, Jaakko Luttinen wrote: Hi! It seems that Shotwell disables "Modify tags" if you select multiple photos. I understand the reason for this when the photos have different tags, but if they have the same tags, it would be efficient to be able to edit the tags. Is the only solution to modify the tags one photo at a time or find the photos from the tag collection and remove the tag in there? Just an idea: It would be easy to modify the tags of several photos (even if they have different set of tags), if the "tag modification" dialog had the tags as check boxes: Checked if they all have the tag and grey if only some have it.. Or something like that.. Anyway, if they have the same tags, the existing dialog would suffice, so it would be simple. What would be the correct place to make suggestions and feature requests? Regards, Jaakko _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From guettli at thomas-guettler.de Mon Nov 5 21:29:53 2012 From: guettli at thomas-guettler.de (=?ISO-8859-15?Q?Thomas_G=FCttler?=) Date: Mon, 05 Nov 2012 22:29:53 +0100 Subject: [Shotwell] Tags per Event Message-ID: <50982FD1.2000706@thomas-guettler.de> Hi, I have a lot of pictures (40k) and up to now I sort them in a directory structure like this YYYY/MM/DD. If there are two events on one day there is second dir DD2... I want to tag events: I want to tag the persons which where at the event: Alice, Bob or Mum .... I don't want to tag each picture because the tag on the event means "Bob was around" while a tag on the picture means "here you can see Bob". Do you understand what I mean? Any chance to do this in shotwell? Regards, Thomas -- Thomas Guettler http://www.thomas-guettler.de/ From clinton at yorba.org Tue Nov 6 00:16:33 2012 From: clinton at yorba.org (Clinton Rogers) Date: Mon, 5 Nov 2012 16:16:33 -0800 Subject: [Shotwell] Tags per Event In-Reply-To: <50982FD1.2000706@thomas-guettler.de> References: <50982FD1.2000706@thomas-guettler.de> Message-ID: Hi Thomas, On 05/11/2012, Thomas G?ttler wrote: > I want to tag events: I want to tag the persons which where at the > event: Alice, Bob or Mum .... > > I don't want to tag each picture because the tag on the event means "Bob > was around" while a tag on the picture means "here you can see Bob". > > Do you understand what I mean? Are you looking for the ability to rename an event based on who was present? If so, Shotwell does have this capability already; simply right-click on the event you'd like to change in the sidebar, and choose 'rename'. If this isn't quite what you had in mind, please let us know - perhaps there's some usability need that's going unaddressed and deserves discussion. Thank you for your interest in Shotwell! Cheers, -c From guettli at thomas-guettler.de Tue Nov 6 06:49:46 2012 From: guettli at thomas-guettler.de (=?ISO-8859-1?Q?Thomas_G=FCttler?=) Date: Tue, 06 Nov 2012 07:49:46 +0100 Subject: [Shotwell] Tags per Event In-Reply-To: References: <50982FD1.2000706@thomas-guettler.de> Message-ID: <494cbfd4-df5d-4619-98a7-bed0a9bd8e08@email.android.com> I know that it is possible to rename events. I would like to tag them. I could rename the event. But if you have several friends called Bob .... There are two things I want to do: find all pictures that belong to someone and next: control access permissions after uploading it to a gallery Web app. Thomas Clinton Rogers schrieb: >Hi Thomas, > >On 05/11/2012, Thomas G?ttler wrote: >> I want to tag events: I want to tag the persons which where at the >> event: Alice, Bob or Mum .... >> >> I don't want to tag each picture because the tag on the event means >"Bob >> was around" while a tag on the picture means "here you can see Bob". >> >> Do you understand what I mean? > >Are you looking for the ability to rename an event based on who was >present? If so, Shotwell does have this capability already; simply >right-click on the event you'd like to change in the sidebar, and >choose 'rename'. > >If this isn't quite what you had in mind, please let us know - perhaps >there's some usability need that's going unaddressed and deserves >discussion. > >Thank you for your interest in Shotwell! > >Cheers, >-c -- http://www.thomas-guettler.de From rehmann at math.uni-bielefeld.de Thu Nov 8 10:57:39 2012 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Thu, 08 Nov 2012 11:57:39 +0100 Subject: [Shotwell] Problems with shotwell 0.13.0 and 0.13.1: Message-ID: <87mwysuzto.fsf@rhea.lan> I just upgraded from shotwell 0.12.90 to 0.13.0 and/or 0.13.1: Both 0.13.* versions have problems which did not occur in 0.12.90: (I am working under Ubuntu 12.10.) i) If in Preferences/Metadata I check "Write tags, titles, and other metadata to photo files", the program starts writing to the files, but seems to always end up in an endless loop, apparently caused by "modified" files, repeatedly saying (in shotwell.log) something like [WRN] No namespace info available for XMP prefix `lr' This is an old bug, as far as I recall, and was fixed in 0.12.90, but now does appear again in both 0.13.*. ii) The deskewing button does not seem to work anymore: I do get a popup window, however, I cannot modify the angle anymore: Clicking on the "Angle" field just skews by 15.0 degrees, which cannot further be modified except by reset to the original state. This also worked well in version 0.12.90 and earlier, as far as I recall. Apparently it is not easily possible to fall back to version 0.12.90, as the data structure of the library was automatically upgraded to schema 16 during my first use of 0.13.*. Any comments? Ulf From joseph.bylund at gmail.com Thu Nov 8 17:34:03 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Thu, 08 Nov 2012 12:34:03 -0500 Subject: [Shotwell] Problems with shotwell 0.13.0 and 0.13.1: In-Reply-To: <87mwysuzto.fsf@rhea.lan> References: <87mwysuzto.fsf@rhea.lan> Message-ID: <509BED0B.7050201@gmail.com> Ulf, On 11/08/2012 05:57 AM, Ulf Rehmann wrote: > I just upgraded from shotwell 0.12.90 to 0.13.0 and/or 0.13.1: > > Both 0.13.* versions have problems which did not occur in 0.12.90: > > (I am working under Ubuntu 12.10.) > > i) If in Preferences/Metadata I check "Write tags, titles, and other > metadata to photo files", the program starts writing to the files, > but seems to always end up in an endless loop, apparently caused by > "modified" files, repeatedly saying (in shotwell.log) something > like > > [WRN] No namespace info available for XMP prefix `lr' > > This is an old bug, as far as I recall, and was fixed in 0.12.90, > but now does appear again in both 0.13.*. This is a known bug and I believe it is being worked on (http://redmine.yorba.org/issues/4297). Some of the issue is that it had been difficult to reproduce. Don't know anything about any of the other issues, sorry. -Joe From jim at yorba.org Thu Nov 8 22:49:12 2012 From: jim at yorba.org (Jim Nelson) Date: Thu, 08 Nov 2012 22:41:12 -0008 Subject: [Shotwell] Problems with shotwell 0.13.0 and 0.13.1: In-Reply-To: <87mwysuzto.fsf@rhea.lan> References: <87mwysuzto.fsf@rhea.lan> Message-ID: <509c36ea.6148420a.4331.ffffcd47@mx.google.com> As Joseph mentioned, the metadata writing bug is one we're aware of and hope to have fixed in the next release. Regarding your other bug, is this a problem with all your photos or just one or two? ?Could you perhaps further explain your problem? ?It sounds like when you attempt to straighten a photo, the slider is stuck at 15 degrees and doesn't move. ?Is that correct? -- Jim On Thu, Nov 8, 2012 at 2:57 AM, Ulf Rehmann wrote: I just upgraded from shotwell 0.12.90 to 0.13.0 and/or 0.13.1: Both 0.13.* versions have problems which did not occur in 0.12.90: (I am working under Ubuntu 12.10.) i) If in Preferences/Metadata I check "Write tags, titles, and other metadata to photo files", the program starts writing to the files, but seems to always end up in an endless loop, apparently caused by "modified" files, repeatedly saying (in shotwell.log) something like [WRN] No namespace info available for XMP prefix `lr' This is an old bug, as far as I recall, and was fixed in 0.12.90, but now does appear again in both 0.13.*. ii) The deskewing button does not seem to work anymore: I do get a popup window, however, I cannot modify the angle anymore: Clicking on the "Angle" field just skews by 15.0 degrees, which cannot further be modified except by reset to the original state. This also worked well in version 0.12.90 and earlier, as far as I recall. Apparently it is not easily possible to fall back to version 0.12.90, as the data structure of the library was automatically upgraded to schema 16 during my first use of 0.13.*. Any comments? Ulf _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From rehmann at math.uni-bielefeld.de Thu Nov 8 23:40:42 2012 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Fri, 09 Nov 2012 00:40:42 +0100 Subject: [Shotwell] Problems with shotwell 0.13.0 and 0.13.1: In-Reply-To: <509c36ea.6148420a.4331.ffffcd47@mx.google.com> (message from Jim Nelson on Thu, 08 Nov 2012 22:41:12 -0008) Message-ID: <87obj7hddx.fsf@rhea.lan> | As Joseph mentioned, the metadata writing bug is one we're aware of and hope to have fixed in the next release. The funny thing here is that it >does work< for me under 0.12.90... | Regarding your other bug, is this a problem with all your photos or just one or two? ?Could you perhaps further explain your problem? ?It sounds like when you attempt to straighten a photo, the slider is stuck at 15 degrees and doesn't move. ?Is that correct? The slider does not occur at all. There is just a filled rectangle (the area where the slider was formerly shown, right to the displayed word 'Angle:'). If I click on that rectangle, the photo is skewed by 15 degrees (so the numerical display right to the rectangle says) and can only be moved further by Reset (i.e., back into its initial position). As far as I can tell, this happens for any picture. However, this may be a problem of some of the involved graphics libraries under 12.10 (gtk?), not of shotwell: As I just tested, the problem occurs on my ubuntu 12.10 system also for the program generated from the 0.12.90 sources (while the problem did not occur for that code under ubuntu 12.04 before my system upgrade). Anyway, thanks for any help! Ulf From rehmann at math.uni-bielefeld.de Sat Nov 10 17:36:45 2012 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Sat, 10 Nov 2012 18:36:45 +0100 Subject: [Shotwell] Problems with shotwell 0.13.0 and 0.13.1: In-Reply-To: <509c36ea.6148420a.4331.ffffcd47@mx.google.com> (message from Jim Nelson on Thu, 08 Nov 2012 22:41:12 -0008) Message-ID: <87bof5e4wi.fsf@rhea.lan> Hi Jim and Joseph, Thanks for your helpful comments. In contrast to what I reported before, Let me just report: The deskewing problem described below is >not> an issue of shotwell 0.13.0 or of 0.13.1: I did compile+install 0.13.1 on Ubuntu 12.04 (precise), where it did work as it should. The problem does occur under Ubuntu 12.10 (quantal) for both the Ubuntu precompiled package shotwell 0.13.0 and for version 0.13.1 which I did compile myself under Ubuntu 12.10. So I conclude there may be something wrong with the Ubuntu 12.10 gtk package. Ulf Jim Nelson writes: | [1:text/plain Hide] | As Joseph mentioned, the metadata writing bug is one we're aware of and hope to have fixed in the next release. | Regarding your other bug, is this a problem with all your photos or just one or two? ?Could you perhaps further explain your problem? ?It sounds like when you attempt to straighten a photo, the slider is stuck at 15 degrees and doesn't move. ?Is that correct? | -- Jim | On Thu, Nov 8, 2012 at 2:57 AM, Ulf Rehmann wrote: | I just upgraded from shotwell 0.12.90 to 0.13.0 and/or 0.13.1: | Both 0.13.* versions have problems which did not occur in 0.12.90: | (I am working under Ubuntu 12.10.) | i) If in Preferences/Metadata I check "Write tags, titles, and other | metadata to photo files", the program starts writing to the files, | but seems to always end up in an endless loop, apparently caused by | "modified" files, repeatedly saying (in shotwell.log) something | like | [WRN] No namespace info available for XMP prefix `lr' | This is an old bug, as far as I recall, and was fixed in 0.12.90, | but now does appear again in both 0.13.*. | ii) The deskewing button does not seem to work anymore: I do get a popup | window, however, I cannot modify the angle anymore: Clicking on the | "Angle" field just skews by 15.0 degrees, which cannot further be | modified except by reset to the original state. This also worked | well in version 0.12.90 and earlier, as far as I recall. | Apparently it is not easily possible to fall back to version 0.12.90, as | the data structure of the library was automatically upgraded to schema | 16 during my first use of 0.13.*. | Any comments? | Ulf | _______________________________________________ | Shotwell mailing list | Shotwell at lists.yorba.org | http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell | [2:text/html Show] From preining at logic.at Mon Nov 12 08:12:22 2012 From: preining at logic.at (Norbert Preining) Date: Mon, 12 Nov 2012 17:12:22 +0900 Subject: [Shotwell] working on comment support Message-ID: <20121112081222.GA24717@gamma.logic.tuwien.ac.at> Dear all, I am currently working on comment/note support for shotwell (see http://redmine.yorba.org/issues/1573) and by now comments for photos work well (including saving, displaying, etc). I would need a bit of help in getting this also done for events. Is there anyone that might be interested to work together on this project? I have a git branch on github at the moment, could also move it to gitorious, depending on preferences. Please let me know if anyone has interest in helping (in *coding*!) Thanks a lot and all the best Norbert ------------------------------------------------------------------------ Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ GLAZELEY (adj.) The state of a barrister's flat greasy hair after wearing a wig all day. --- Douglas Adams, The Meaning of Liff From moejoeblue at gmail.com Tue Nov 13 20:58:01 2012 From: moejoeblue at gmail.com (Moe Blue) Date: Tue, 13 Nov 2012 21:58:01 +0100 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) Message-ID: Hi there, I've moved my photos and shotwell to a new PC (fedora 17 to ubuntu 12.10) and the RAW+JPEG are not paired anymore. On fedora 17, I installed shotwell 0.13 from source. On ubuntu 12.10 I use the shotwell 0.13.1 from the official repositories. First, I moved my old shotwell database to /home/user/.local/share/shotwell/data/photos.db overwriting the (empty?) one. On my old machine, photos were stored at /media/daten/fotos/ now they are stored at /home/user/Bilder/ After moving files, I started shotwell, set default photo path to /home/user/Bilder/, enabled the rescan option and set default developer to shotwell. (I have set it to shotwell, because I've had problems in the past with priorities of shotwell using embedded JPEG instead of full resolution camera developed JPEG versions. usually I set it manually to camera afterwards.) However, shotwell rediscovers (took ages) my images, both JPEG and RAW, but separately. That is, I see the RAW version beside the JPEG. Ther does not seem to be a way to re-combine them. Setting back the developer for a particular RAW photo to camera makes it disapper first. After a relaunch of shotwell, it reappears beside the JPEG. For some files, opening the RAW in full view makes it disappear again. For other files, opening the RAW provides a black screen with the message that source file at /media/daten/fotos is missing. It then disappears again. Most of my tags seem to be lost. RAW and JPEG versions are not combined and reside in separate events. Is there a way to fix this? Or do I have to re-import everything manually. I find, that moving it to the DCIM folder on my camera's storage card while restoring the original name for the JPG makes it possible to perform a clean new import of the photos. By the way, there does not seem to be a problem for ordinary JPEG photos. However, RAW+JPEG support in shotwell seem to be broken. I'm looking foreward to some fixes in 0.14. Best Moe -- Moe Blue From clanlaw at googlemail.com Tue Nov 13 21:05:50 2012 From: clanlaw at googlemail.com (Colin Law) Date: Tue, 13 Nov 2012 21:05:50 +0000 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: References: Message-ID: On 13 November 2012 20:58, Moe Blue wrote: > Hi there, > > I've moved my photos and shotwell to a new PC (fedora 17 to ubuntu 12.10) > and the RAW+JPEG are not paired anymore. On fedora 17, I installed shotwell > 0.13 from source. On ubuntu 12.10 I use the shotwell 0.13.1 from the > official repositories. 0.13.1 is not in the Ubuntu 12.10 repository yet (sadly). It is still 0.13.0. For me anyway. Colin > > First, I moved my old shotwell database to > /home/user/.local/share/shotwell/data/photos.db > overwriting the (empty?) one. > > On my old machine, photos were stored at > /media/daten/fotos/ > now they are stored at > /home/user/Bilder/ > > After moving files, I started shotwell, set default photo path to > /home/user/Bilder/, enabled the rescan option and set default developer to > shotwell. (I have set it to shotwell, because I've had problems in the past > with priorities of shotwell using embedded JPEG instead of full resolution > camera developed JPEG versions. usually I set it manually to camera > afterwards.) > > However, shotwell rediscovers (took ages) my images, both JPEG and RAW, but > separately. That is, I see the RAW version beside the JPEG. Ther does not > seem to be a way to re-combine them. > > Setting back the developer for a particular RAW photo to camera makes it > disapper first. After a relaunch of shotwell, it reappears beside the JPEG. > For some files, opening the RAW in full view makes it disappear again. For > other files, opening the RAW provides a black screen with the message that > source file at /media/daten/fotos is missing. It then disappears again. > > Most of my tags seem to be lost. RAW and JPEG versions are not combined and > reside in separate events. > > Is there a way to fix this? Or do I have to re-import everything manually. > I find, that moving it to the DCIM folder on my camera's storage card while > restoring the original name for the JPG makes it possible to perform a > clean new import of the photos. > > By the way, there does not seem to be a problem for ordinary JPEG photos. > However, RAW+JPEG support in shotwell seem to be broken. I'm looking > foreward to some fixes in 0.14. > > Best > Moe > > > -- > Moe Blue > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From clanlaw at googlemail.com Tue Nov 13 21:19:35 2012 From: clanlaw at googlemail.com (Colin Law) Date: Tue, 13 Nov 2012 21:19:35 +0000 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: References: Message-ID: On 13 November 2012 21:15, Moe Blue wrote: > That's right. But does it make a difference for my RAW+JPEG issue? I don't know but I thought I had better correct the statement in case it is relevant. Colin > > > 2012/11/13 Colin Law >> >> On 13 November 2012 20:58, Moe Blue wrote: >> > Hi there, >> > >> > I've moved my photos and shotwell to a new PC (fedora 17 to ubuntu >> > 12.10) >> > and the RAW+JPEG are not paired anymore. On fedora 17, I installed >> > shotwell >> > 0.13 from source. On ubuntu 12.10 I use the shotwell 0.13.1 from the >> > official repositories. >> >> 0.13.1 is not in the Ubuntu 12.10 repository yet (sadly). It is still >> 0.13.0. For me anyway. >> >> Colin >> >> > >> > First, I moved my old shotwell database to >> > /home/user/.local/share/shotwell/data/photos.db >> > overwriting the (empty?) one. >> > >> > On my old machine, photos were stored at >> > /media/daten/fotos/ >> > now they are stored at >> > /home/user/Bilder/ >> > >> > After moving files, I started shotwell, set default photo path to >> > /home/user/Bilder/, enabled the rescan option and set default developer >> > to >> > shotwell. (I have set it to shotwell, because I've had problems in the >> > past >> > with priorities of shotwell using embedded JPEG instead of full >> > resolution >> > camera developed JPEG versions. usually I set it manually to camera >> > afterwards.) >> > >> > However, shotwell rediscovers (took ages) my images, both JPEG and RAW, >> > but >> > separately. That is, I see the RAW version beside the JPEG. Ther does >> > not >> > seem to be a way to re-combine them. >> > >> > Setting back the developer for a particular RAW photo to camera makes it >> > disapper first. After a relaunch of shotwell, it reappears beside the >> > JPEG. >> > For some files, opening the RAW in full view makes it disappear again. >> > For >> > other files, opening the RAW provides a black screen with the message >> > that >> > source file at /media/daten/fotos is missing. It then disappears again. >> > >> > Most of my tags seem to be lost. RAW and JPEG versions are not combined >> > and >> > reside in separate events. >> > >> > Is there a way to fix this? Or do I have to re-import everything >> > manually. >> > I find, that moving it to the DCIM folder on my camera's storage card >> > while >> > restoring the original name for the JPG makes it possible to perform a >> > clean new import of the photos. >> > >> > By the way, there does not seem to be a problem for ordinary JPEG >> > photos. >> > However, RAW+JPEG support in shotwell seem to be broken. I'm looking >> > foreward to some fixes in 0.14. >> > >> > Best >> > Moe >> > >> > >> > -- >> > Moe Blue >> > _______________________________________________ >> > Shotwell mailing list >> > Shotwell at lists.yorba.org >> > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > > > > -- > Moe Blue From blklists at elementarea.net Tue Nov 13 21:26:48 2012 From: blklists at elementarea.net (Andreas Brauchli) Date: Tue, 13 Nov 2012 22:26:48 +0100 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: References: Message-ID: <1352842008.24552.19.camel@thinky> Hi Moe On Die, 2012-11-13 at 21:58 +0100, Moe Blue wrote: > Hi there, > > I've moved my photos and shotwell to a new PC (fedora 17 to ubuntu 12.10) > and the RAW+JPEG are not paired anymore. On fedora 17, I installed shotwell > 0.13 from source. On ubuntu 12.10 I use the shotwell 0.13.1 from the > official repositories. > > First, I moved my old shotwell database to > /home/user/.local/share/shotwell/data/photos.db > overwriting the (empty?) one. it's photo.db but you probably meant that. > On my old machine, photos were stored at > /media/daten/fotos/ > now they are stored at > /home/user/Bilder/ > Most of my tags seem to be lost. You should write them back to the photo (there's an option for that), then they should survive such operations > Is there a way to fix this? Or do I have to re-import everything manually. > I find, that moving it to the DCIM folder on my camera's storage card while > restoring the original name for the JPG makes it possible to perform a > clean new import of the photos. Moving storage locations is not a supported feature, so you took quite some chances doing that. However you hopefully made a backup, so you can try again if you feel confident enough. What I would do is: - Back up the photo db to a different location (otherwise you get one single shot at it.. if you like adrenaline ;)) - Upgrade shotwell in place to the version you want to use after the move (just start the new version, let it do its work, maybe leave it open a few minutes more and close it again) - DO NOT START SHOTWELL ANYMORE NOW - Connect to the db and fix the paths to their new locations with an appropriate sqlite query. Nothing scary if you know some sql dialect - otherwise you're screwed. A pretty good graphical tool to do that is sqliteman (query is still text though) - Move the pictures to the new location - the you updated your db with - NOW START SHOTWELL and it won't even notice something's different I did that a few times some versions back and never had problems. If done right i'm sure it also works with the raw-pairing (never used that but there's usually no dark magic involved in open software) no guarantees.. $(cat dead_kitten_speech) > Best > Moe Cheers and good luck andreas From blklists at elementarea.net Tue Nov 13 22:00:08 2012 From: blklists at elementarea.net (Andreas Brauchli) Date: Tue, 13 Nov 2012 23:00:08 +0100 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: References: <1352842008.24552.19.camel@thinky> Message-ID: <1352844008.1392.11.camel@thinky> Hi please always CC the list, they might be interested. On Die, 2012-11-13 at 22:43 +0100, Moe Blue wrote: > Hi Andreas, > > thank you for your help. > > > it's photo.db but you probably meant that. > > > yep. sorry for the typos. > > >> Most of my tags seem to be lost. > > You should write them back to the photo (there's an option for > that), > > then they should survive such operations > > if I apply your SQL trick this is not necessary anymore. is it? Yes, you're right, that's not necessary. But then you could also, God forbid, move to a different picture manager ;) > Does the option to write metadata to photos also apply for > transformations, flags and events or only for tags? No just tags, and just on pictures that support tags (probably not on RAW and videos) > > some chances doing that. However you hopefully made a backup, so you > can > > try again if you feel confident enough. > > I have a untouched copy of database and photos on my old PC. > > Before I start with your workaround, two questions: > > > - Upgrade shotwell in place to the version you want to use after the > > move (just start the new version, let it do its work, maybe leave it > > open a few minutes more and close it again) > > First, on (old) fedora 17 I have 0.13.1, so I should upgrade 0.13.0 to > 0.13.1 on the new ubuntu 12.10 machine using the yorba ppa, right? Yes, versions must match - the DB is dependent on the shotwell version. I don't think the distro packagers would modify the DB layout, therefore matching the versions *should* be enough. > Second, the write metadata to files is not needed for this step, > right? Does it help, anyway? No, won't help a thing > Best > Moe cheers > > 2012/11/13 Andreas Brauchli > Hi Moe > > On Die, 2012-11-13 at 21:58 +0100, Moe Blue wrote: > > Hi there, > > > > I've moved my photos and shotwell to a new PC (fedora 17 to > ubuntu 12.10) > > and the RAW+JPEG are not paired anymore. On fedora 17, I > installed shotwell > > 0.13 from source. On ubuntu 12.10 I use the shotwell 0.13.1 > from the > > official repositories. > > > > First, I moved my old shotwell database to > > /home/user/.local/share/shotwell/data/photos.db > > overwriting the (empty?) one. > > it's photo.db but you probably meant that. > > > On my old machine, photos were stored at > > /media/daten/fotos/ > > now they are stored at > > /home/user/Bilder/ > > > > Most of my tags seem to be lost. > > You should write them back to the photo (there's an option for > that), > then they should survive such operations > > > Is there a way to fix this? Or do I have to re-import > everything manually. > > I find, that moving it to the DCIM folder on my camera's > storage card while > > restoring the original name for the JPG makes it possible to > perform a > > clean new import of the photos. > > Moving storage locations is not a supported feature, so you > took quite > some chances doing that. However you hopefully made a backup, > so you can > try again if you feel confident enough. > What I would do is: > - Back up the photo db to a different location (otherwise you > get one > single shot at it.. if you like adrenaline ;)) > - Upgrade shotwell in place to the version you want to use > after the > move (just start the new version, let it do its work, maybe > leave it > open a few minutes more and close it again) > - DO NOT START SHOTWELL ANYMORE NOW > - Connect to the db and fix the paths to their new locations > with an > appropriate sqlite query. Nothing scary if you know some sql > dialect - > otherwise you're screwed. A pretty good graphical tool to do > that is > sqliteman (query is still text though) > - Move the pictures to the new location - the you updated your > db with > - NOW START SHOTWELL and it won't even notice something's > different > I did that a few times some versions back and never had > problems. > If done right i'm sure it also works with the raw-pairing > (never used > that but there's usually no dark magic involved in open > software) > > no guarantees.. $(cat dead_kitten_speech) > > > Best > > Moe > Cheers and good luck > andreas > > > > > -- > Moe Blue > From clanlaw at googlemail.com Tue Nov 13 22:04:34 2012 From: clanlaw at googlemail.com (Colin Law) Date: Tue, 13 Nov 2012 22:04:34 +0000 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: <1352844008.1392.11.camel@thinky> References: <1352842008.24552.19.camel@thinky> <1352844008.1392.11.camel@thinky> Message-ID: On 13 November 2012 22:00, Andreas Brauchli wrote: > Hi > > please always CC the list, they might be interested. > > On Die, 2012-11-13 at 22:43 +0100, Moe Blue wrote: >> ... >> First, on (old) fedora 17 I have 0.13.1, so I should upgrade 0.13.0 to >> 0.13.1 on the new ubuntu 12.10 machine using the yorba ppa, right? > Yes, versions must match - the DB is dependent on the shotwell version. > I don't think the distro packagers would modify the DB layout, therefore > matching the versions *should* be enough. 0.13.1 is apparently not yet available for 12.10 in the ppa unfortunately. Colin From blklists at elementarea.net Tue Nov 13 22:29:06 2012 From: blklists at elementarea.net (Andreas Brauchli) Date: Tue, 13 Nov 2012 23:29:06 +0100 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: References: <1352842008.24552.19.camel@thinky> <1352844008.1392.11.camel@thinky> Message-ID: <1352845746.1392.20.camel@thinky> On Die, 2012-11-13 at 22:04 +0000, Colin Law wrote: > On 13 November 2012 22:00, Andreas Brauchli wrote: > > Hi > > > > please always CC the list, they might be interested. > > > > On Die, 2012-11-13 at 22:43 +0100, Moe Blue wrote: > >> ... > >> First, on (old) fedora 17 I have 0.13.1, so I should upgrade 0.13.0 to > >> 0.13.1 on the new ubuntu 12.10 machine using the yorba ppa, right? > > Yes, versions must match - the DB is dependent on the shotwell version. > > I don't think the distro packagers would modify the DB layout, therefore > > matching the versions *should* be enough. > > 0.13.1 is apparently not yet available for 12.10 in the ppa unfortunately. Fortunately, that still leaves the option to compile it. OTOH i quickly checked the repo and the schema didn't change between 0.13.0 and 0.13.1 so the db _layout_ (not content) is compatible between the versions (i expect it to be for for stable stuff like paths.. some transformations will probably only work 0.13.0 -> 0.13.1 but not the other way causing crashes and whatnot). I'd give it a try I know I keep saying it but: keep a backup when doing stuff like that! > Colin best, andreas From clanlaw at googlemail.com Wed Nov 14 17:29:10 2012 From: clanlaw at googlemail.com (Colin Law) Date: Wed, 14 Nov 2012 17:29:10 +0000 Subject: [Shotwell] Building shotwell from source on Ubuntu 12.10 Message-ID: I have succeeded in building 0.13.1 from the source tarball but it seems that the instructions in [1] could do with updating, at least for Ubuntu 12.10. The dependencies should include libgtk-3-dev, libunique-3.0-dev, libwebkitgtk-3.0-dev, libjson-glib-dev and valac-0.18 and possibly should not include libgtk2.0-dev, libunique-dev, libwebkit-dev and valac-0.16 though I cannot guarantee this as I installed them first, following the instructions, and don't want to uninstall them in case they were actually already installed and I need them for something else. However I now have a working 0.13.1 on Ubuntu 12.10 so I am happy. Thanks to the developers for a great application. Colin [1] http://yorba.org/shotwell/install.html From moejoeblue at gmail.com Wed Nov 14 21:19:27 2012 From: moejoeblue at gmail.com (Moe Blue) Date: Wed, 14 Nov 2012 22:19:27 +0100 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: <1352845746.1392.20.camel@thinky> References: <1352842008.24552.19.camel@thinky> <1352844008.1392.11.camel@thinky> <1352845746.1392.20.camel@thinky> Message-ID: <50A40ADF.3040005@gmail.com> Hi Andreas, it worked! Thanks a lot! Am 13.11.2012 23:29, schrieb Andreas Brauchli: > On Die, 2012-11-13 at 22:04 +0000, Colin Law wrote: >> On 13 November 2012 22:00, Andreas Brauchli wrote: >>> Hi >>> >>> please always CC the list, they might be interested. >>> >>> On Die, 2012-11-13 at 22:43 +0100, Moe Blue wrote: >>>> ... >>>> First, on (old) fedora 17 I have 0.13.1, so I should upgrade 0.13.0 to >>>> 0.13.1 on the new ubuntu 12.10 machine using the yorba ppa, right? >>> Yes, versions must match - the DB is dependent on the shotwell version. >>> I don't think the distro packagers would modify the DB layout, therefore >>> matching the versions *should* be enough. >> >> 0.13.1 is apparently not yet available for 12.10 in the ppa unfortunately. > Fortunately, that still leaves the option to compile it. > > OTOH i quickly checked the repo and the schema didn't change between > 0.13.0 and 0.13.1 so the db _layout_ (not content) is compatible between > the versions (i expect it to be for for stable stuff like paths.. some > transformations will probably only work 0.13.0 -> 0.13.1 but not the > other way causing crashes and whatnot). I'd give it a try > > I know I keep saying it but: keep a backup when doing stuff like that! > >> Colin > best, > andreas > From jim at yorba.org Wed Nov 14 22:26:13 2012 From: jim at yorba.org (Jim Nelson) Date: Wed, 14 Nov 2012 22:18:13 -0008 Subject: [Shotwell] Building shotwell from source on Ubuntu 12.10 In-Reply-To: References: Message-ID: <50a41a87.49eb440a.24ba.ffff8a89@mx.google.com> Thanks Colin, I've updated the web site. -- Jim On Wed, Nov 14, 2012 at 9:29 AM, Colin Law wrote: I have succeeded in building 0.13.1 from the source tarball but it seems that the instructions in [1] could do with updating, at least for Ubuntu 12.10. The dependencies should include libgtk-3-dev, libunique-3.0-dev, libwebkitgtk-3.0-dev, libjson-glib-dev and valac-0.18 and possibly should not include libgtk2.0-dev, libunique-dev, libwebkit-dev and valac-0.16 though I cannot guarantee this as I installed them first, following the instructions, and don't want to uninstall them in case they were actually already installed and I need them for something else. However I now have a working 0.13.1 on Ubuntu 12.10 so I am happy. Thanks to the developers for a great application. Colin [1] http://yorba.org/shotwell/install.html _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From blklists at elementarea.net Thu Nov 15 11:55:23 2012 From: blklists at elementarea.net (Andreas Brauchli) Date: Thu, 15 Nov 2012 12:55:23 +0100 Subject: [Shotwell] RAW+JPEG are not re-paired after move to new PC (new photo directory) In-Reply-To: <50A40ADF.3040005@gmail.com> References: <1352842008.24552.19.camel@thinky> <1352844008.1392.11.camel@thinky> <1352845746.1392.20.camel@thinky> <50A40ADF.3040005@gmail.com> Message-ID: <1352980523.3982.0.camel@thinky> On Mit, 2012-11-14 at 22:19 +0100, Moe Blue wrote: > Hi Andreas, > > it worked! Thanks a lot! Cool, thanks for letting us know have fun From hendrikusgodvliet at gmail.com Fri Nov 16 21:51:23 2012 From: hendrikusgodvliet at gmail.com (Hendrikus Godvliet) Date: Fri, 16 Nov 2012 23:51:23 +0200 Subject: [Shotwell] shotwell no crop function Message-ID: Hi all I am new to this list I am having problems with shotwell in Fedora 17 Mate desktop The crop function is not functioning well. What happend is that when I click on the crop button the pallet ore do i have to say window witch show the crop form is half way under in the graphic of the screen. I mean it is not visible only for a small say 10the part. It is a bit scrollable but when i crop the image then there is no button to apply button. Hope this info make it understandeble - better would be to show up with a screen shot. Cause the pallet/window is not under the main window from Shotwell - alt-tab. Hendrikus From depaola.andrea at gmail.com Sat Nov 17 14:10:35 2012 From: depaola.andrea at gmail.com (Andrea De Paola) Date: Sat, 17 Nov 2012 15:10:35 +0100 Subject: [Shotwell] Generate thumbnails Message-ID: <20121117151035.339257fa@debian> Hello everybody. I'm using shotwell 0.12.3 on debian wheezy. After importing my pictures in shotwell, I modified some of them using an external tool. After this operation, the thumbnail in shotwell changed and they get very bad, so I searched the modified thumbnails in ~/.shotwell/thumbs and I've deleted them, thinking that they'll generate again when shotwell will start. But then I think that this isn't happening, because the thumbnail of these pictures have now a very bad resolution, I think that they're aren't in the thumbnail folder. Is there a way to force shotwell to generate again all the thumbnails or the ones of some events? Thank you Andrea From moejoeblue at gmail.com Sat Nov 17 16:04:15 2012 From: moejoeblue at gmail.com (Moe Blue) Date: Sat, 17 Nov 2012 17:04:15 +0100 Subject: [Shotwell] RAW+JPEG pairing Message-ID: Hello, can someone explain how Shotwell matches RAW+JEPGs during normal import (does it match RAW+JPEG at watch directory import at all?). a. For some Photos I find the RAW it correctly paired with camera developed JPEG. b. For some Photos Shotwell ignores the camera JPEG and imports borth separately and developing the RAW as _shotwell afterwards. The Photo then apperas twice. c. Sometimes it uses the embedded JPEG as camera developed Version. I wanted to post a bug report on this but the importing behaviour seem to be somewhat arbitrary so I couldn't reporduce the error all the time. I have a set of photos at DCIM/100MSDCF which should be importet into shotwell. Filename (excempt ending .ARW/.JPG) and file timestamp are identical for the RAW and JPG version. But the pairing behaviour is different. Best Moe -- Moe Blue From moejoeblue at gmail.com Sat Nov 17 16:06:13 2012 From: moejoeblue at gmail.com (Moe Blue) Date: Sat, 17 Nov 2012 17:06:13 +0100 Subject: [Shotwell] RAW+JPEG pairing In-Reply-To: References: Message-ID: I forgot to mention: I'm using shotwell 0.13.0 on ubuntu 12.10. 2012/11/17 Moe Blue > Hello, > > can someone explain how Shotwell matches RAW+JEPGs during normal import > (does it match RAW+JPEG at watch directory import at all?). > > a. For some Photos I find the RAW it correctly paired with camera > developed JPEG. > b. For some Photos Shotwell ignores the camera JPEG and imports borth > separately and developing the RAW as _shotwell afterwards. The Photo then > apperas twice. > c. Sometimes it uses the embedded JPEG as camera developed Version. > > I wanted to post a bug report on this but the importing behaviour seem to > be somewhat arbitrary so I couldn't reporduce the error all the time. > > I have a set of photos at DCIM/100MSDCF which should be importet into > shotwell. Filename (excempt ending .ARW/.JPG) and file timestamp are > identical for the RAW and JPG version. But the pairing behaviour is > different. > > Best > Moe > > -- > Moe Blue > -- Moe Blue From gpopac at gmail.com Sat Nov 17 23:46:18 2012 From: gpopac at gmail.com (=?UTF-8?Q?=D0=9C=D0=B8=D0=BB=D0=BE=D1=88_?= =?UTF-8?Q?=D0=9F=D0=BE=D0=BF=D0=BE=D0=B2=D0=B8=D1=9B?=) Date: Sun, 18 Nov 2012 00:46:18 +0100 Subject: [Shotwell] RAW+JPEG pairing In-Reply-To: References: Message-ID: <1353195978.13611.2.camel@medjed> Are you considering to fix this for 0.14? It looks like a huge problem for many users. I have asked for some automatization to autopair unpaired RAW+JPEG and remove _embeded.jpg and _shotwel.jpg files a couple of months ago (on the mailing list). What do you think about this? From gpopac at gmail.com Sun Nov 18 01:19:06 2012 From: gpopac at gmail.com (=?UTF-8?Q?=D0=9C=D0=B8=D0=BB=D0=BE=D1=88_?= =?UTF-8?Q?=D0=9F=D0=BE=D0=BF=D0=BE=D0=B2=D0=B8=D1=9B?=) Date: Sun, 18 Nov 2012 02:19:06 +0100 Subject: [Shotwell] Generate thumbnails In-Reply-To: <20121117151035.339257fa@debian> References: <20121117151035.339257fa@debian> Message-ID: <1353201546.13611.3.camel@medjed> You just need to install the version 0.13.X. All the best, Milo? ? ???, 17. 11 2012. ? 15:10 +0100, Andrea De Paola ????: > Hello everybody. > I'm using shotwell 0.12.3 on debian wheezy. > > After importing my pictures in shotwell, I modified some of them using > an external tool. After this operation, the thumbnail in shotwell > changed and they get very bad, so I searched the modified thumbnails > in ~/.shotwell/thumbs and I've deleted them, thinking that they'll > generate again when shotwell will start. > > But then I think that this isn't happening, because the thumbnail of > these pictures have now a very bad resolution, I think that they're > aren't in the thumbnail folder. > > Is there a way to force shotwell to generate again all the thumbnails > or the ones of some events? > > Thank you > Andrea > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From depaola.andrea at gmail.com Mon Nov 19 13:43:44 2012 From: depaola.andrea at gmail.com (Andrea De Paola) Date: Mon, 19 Nov 2012 14:43:44 +0100 Subject: [Shotwell] Generate thumbnails In-Reply-To: <1353201546.13611.3.camel@medjed> References: <20121117151035.339257fa@debian> <1353201546.13611.3.camel@medjed> Message-ID: <20121119144344.7f1aabb5@debian> This works, thank you very much. Andrea On Sun, 18 Nov 2012 02:19:06 +0100 ????? ??????? wrote: > You just need to install the version 0.13.X. > > All the best, > Milo? > From lucas at yorba.org Mon Nov 19 19:22:28 2012 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 19 Nov 2012 11:22:28 -0800 Subject: [Shotwell] RAW+JPEG pairing In-Reply-To: <1353195978.13611.2.camel@medjed> References: <1353195978.13611.2.camel@medjed> Message-ID: Hi ?????, We're aware of the RAW pairing woes in Shotwell, especially when the default developer selected via the preferences panel is "Camera." See, for example, the following bug tickets in our issue tracking system: http://redmine.yorba.org/issues/4149 http://redmine.yorba.org/issues/4141 http://redmine.yorba.org/issues/4207 http://redmine.yorba.org/issues/4262 You'll be happy to know that most of these issues are milestoned for 0.14, the next release of Shotwell! Lucas On Sat, Nov 17, 2012 at 3:46 PM, ????? ??????? wrote: > Are you considering to fix this for 0.14? It looks like a huge problem > for many users. > > I have asked for some automatization to autopair unpaired RAW+JPEG and > remove _embeded.jpg and _shotwel.jpg files a couple of months ago (on > the mailing list). What do you think about this? > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From lucas at yorba.org Mon Nov 19 19:31:35 2012 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 19 Nov 2012 11:31:35 -0800 Subject: [Shotwell] shotwell no crop function In-Reply-To: References: Message-ID: Hi Hendrikus, Having a screenshot to demonstrate this behavior would really be helpful in debugging the problem. The Shotwell mailing list doesn't allow attachments, but it's easy to work around this restriction by uploading your image to a file sharing site (such as Dropbox) and then linking to it on the mailing list. Lucas On Fri, Nov 16, 2012 at 1:51 PM, Hendrikus Godvliet wrote: > Hi all I am new to this list > > I am having problems with shotwell in Fedora 17 Mate desktop > > The crop function is not functioning well. What happend is that when I > click on the crop button the pallet ore do i have to say window witch show > the crop form is half way under in the graphic of the screen. I mean it is > not visible only for a small say 10the part. It is a bit scrollable but > when i crop the image then there is no button to apply button. > > Hope this info make it understandeble - better would be to show up with a > screen shot. Cause the pallet/window is not under the main window from > Shotwell - alt-tab. > > > Hendrikus > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From gpopac at gmail.com Mon Nov 19 23:22:51 2012 From: gpopac at gmail.com (=?UTF-8?Q?=D0=9C=D0=B8=D0=BB=D0=BE=D1=88_?= =?UTF-8?Q?=D0=9F=D0=BE=D0=BF=D0=BE=D0=B2=D0=B8=D1=9B?=) Date: Tue, 20 Nov 2012 00:22:51 +0100 Subject: [Shotwell] RAW+JPEG pairing In-Reply-To: References: <1353195978.13611.2.camel@medjed> Message-ID: <1353367371.27776.26.camel@medjed> Hi Lucas, Thank you for your Reply. For me this is great news! ? ???, 19. 11 2012. ? 11:22 -0800, Lucas Beeler ????: > Hi ?????, > > We're aware of the RAW pairing woes in Shotwell, especially when the > default developer selected via the preferences panel is "Camera." See, > for example, the following bug tickets in our issue tracking system: > > http://redmine.yorba.org/issues/4149 > http://redmine.yorba.org/issues/4141 > http://redmine.yorba.org/issues/4207 > http://redmine.yorba.org/issues/4262 > > You'll be happy to know that most of these issues are milestoned for > 0.14, the next release of Shotwell! > > Lucas > > On Sat, Nov 17, 2012 at 3:46 PM, ????? ??????? wrote: > > Are you considering to fix this for 0.14? It looks like a huge problem > > for many users. > > > > I have asked for some automatization to autopair unpaired RAW+JPEG and > > remove _embeded.jpg and _shotwel.jpg files a couple of months ago (on > > the mailing list). What do you think about this? > > > > _______________________________________________ > > Shotwell mailing list > > Shotwell at lists.yorba.org > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From thomas at xyz.pp.se Tue Nov 20 19:54:28 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Tue, 20 Nov 2012 20:54:28 +0100 Subject: [Shotwell] Yorba PPA In-Reply-To: <508fd615.1893cc0a.35e4.5a57@mx.google.com> References: <508fd615.1893cc0a.35e4.5a57@mx.google.com> Message-ID: On Tue, Oct 30, 2012 at 2:28 PM, Jim Nelson wrote: > We're working with Ubuntu to get 0.13.1 packaged and distributed with > Quantal. Please hang on while we work out this issue. > > -- Jim > > Won't the PPA be updated? Because it's usually much faster to get the updates from the PPA than Ubuntu so I would prefer using that version. Rgds//TN From lucas at yorba.org Tue Nov 20 20:30:38 2012 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 20 Nov 2012 12:30:38 -0800 Subject: [Shotwell] Yorba PPA In-Reply-To: References: <508fd615.1893cc0a.35e4.5a57@mx.google.com> Message-ID: > Won't the PPA be updated? It's not as simple as just updating the PPA. The PPA version of Shotwell offered by Yorba and the Canonical-patched version of Shotwell distributed with Ubuntu Quantal differ substantially. Specifically, the Ubuntu-distributed version of Shotwell has been patched such that the Shotwell photo publishing system uses Ubuntu Online Accounts for web service sign-in and authentication. We're moving forward on a number of tracks. For example, we're working to get the UOA support changes integrated into our upstream repo. We're also considering offering a non-UOA version of Shotwell via the PPA but no definitive decision has been made on this yet. Stay tuned. Lucas From thomas at xyz.pp.se Wed Nov 21 13:17:31 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Wed, 21 Nov 2012 14:17:31 +0100 Subject: [Shotwell] Yorba PPA In-Reply-To: References: <508fd615.1893cc0a.35e4.5a57@mx.google.com> Message-ID: On Tue, Nov 20, 2012 at 9:30 PM, Lucas Beeler wrote: > > Won't the PPA be updated? > > It's not as simple as just updating the PPA. The PPA version of > Shotwell offered by Yorba and the Canonical-patched version of > Shotwell distributed with Ubuntu Quantal differ substantially. > Specifically, the Ubuntu-distributed version of Shotwell has been > patched such that the Shotwell photo publishing system uses Ubuntu > Online Accounts for web service sign-in and authentication. We're > moving forward on a number of tracks. For example, we're working to > get the UOA support changes integrated into our upstream repo. We're > also considering offering a non-UOA version of Shotwell via the PPA > but no definitive decision has been made on this yet. Stay tuned. Ok, for now, is it OK to run 0.13.0 and 0.13.1 towards the same DB? I share my Shotwell database so it's the same on three computers in our home. Rgds//Thomas From joseph.bylund at gmail.com Fri Nov 23 04:29:13 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Thu, 22 Nov 2012 23:29:13 -0500 Subject: [Shotwell] Trouble with Import "Hardware Error" Message-ID: <50AEFB99.6020001@gmail.com> I'm having some difficulty importing some pictures with shotwell reporting a "hardware error", the only possibly relevant note I see in the log is: L 5607 2012-11-22 23:25:14 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored. L 5607 2012-11-22 23:25:14 [WRN] Invalid JPEG preview image. but those don't look terribly serious. One of the images in question can be found here: http://www.columbia.edu/~jhb2147/img/P1010438.JPG Can someone check if you get the same behavior? In unrelated news, happy thanksgiving to all, and I apologize if any of you recently got some spam from my gmail account. -Joe From emailgrant at gmail.com Sun Nov 25 21:49:30 2012 From: emailgrant at gmail.com (Grant) Date: Sun, 25 Nov 2012 13:49:30 -0800 Subject: [Shotwell] Crashes when importing Message-ID: I can import in place, but if I choose to copy to library, shotwell crashes like this: (shotwell:9130): GConf-CRITICAL **: gconf_engine_pop_owner_usage: assertion `engine->owner_use_count > 0' failed ** ERROR:gconfsettingsbackend.c:205:gconf_settings_backend_remove_notifier: assertion failed: (notifier && g_str_equal (path, notifier->path)) Aborted I'm using 0.13.1 on Gentoo. Should I file a bug? - Grant From scott_shotwell at dewie.net.au Mon Nov 26 11:50:38 2012 From: scott_shotwell at dewie.net.au (Scott) Date: Mon, 26 Nov 2012 22:50:38 +1100 Subject: [Shotwell] Shotwell 0.13.1 hanging on import Message-ID: <50B3578E.2090606@dewie.net.au> Hi all, My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to hang on import of anything. What will happen is it will try to get the photo's off the SD Card, it will get some of the thumbnails, but will freeze half way through. The progress bar will stop moving and no more thumbnails will appear. Whats more, when i try to exit, the process will not actually quit, until i use either top or gnome-system-monitor to kill it manually. I have done a full backport, but as i have absolutely no idea what i am looking at, i cant tell if it is helpful or not. I also believe that this list doesnt allow attachments, is there somewhere i could e-mil them to? Is anyone else experiencing this? On a possibly unrelated note, the library is on an external USB, with the database in my home directory. The problem is that i accidentally opened shotwell the other day not knowing that the external hdd had not been mounted correctly, and as a result the entire library has now been shown to be missing, and no matter how long I wait, the library will not update itself. Is there a way to force shotwell to attempt to locate these? Or could there be in a future release? Normally, a workaround i find is to re-import (this does happen occasionally if i accidentally insert the SD card before the hdd), but with all imports hanging i cannot get my photos to refresh themselves... Thanks, Scott. From joseph.bylund at gmail.com Mon Nov 26 12:49:33 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Mon, 26 Nov 2012 07:49:33 -0500 Subject: [Shotwell] Shotwell 0.13.1 hanging on import In-Reply-To: <50B3578E.2090606@dewie.net.au> References: <50B3578E.2090606@dewie.net.au> Message-ID: <50B3655D.8020106@gmail.com> Scott, It's likely it's importing and the progress bar is hung (that's what I saw). Can you do "export SHOTWELL_LOG=1" and watch ~/.cache/shotwell/shotwell.log during import? If you're continually seeing it talk about new photos then it's probably not hung (but the bar may be). To share your backtrace you can upload to dropbox and get a link or email shotwell at yorba. -Joe On 11/26/2012 06:50 AM, Scott wrote: > Hi all, > > My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to > hang on import of anything. What will happen is it will try to get > the photo's off the SD Card, it will get some of the thumbnails, but > will freeze half way through. The progress bar will stop moving and > no more thumbnails will appear. Whats more, when i try to exit, the > process will not actually quit, until i use either top or > gnome-system-monitor to kill it manually. I have done a full > backport, but as i have absolutely no idea what i am looking at, i > cant tell if it is helpful or not. I also believe that this list > doesnt allow attachments, is there somewhere i could e-mil them to? Is > anyone else experiencing this? > > On a possibly unrelated note, the library is on an external USB, with > the database in my home directory. The problem is that i accidentally > opened shotwell the other day not knowing that the external hdd had > not been mounted correctly, and as a result the entire library has now > been shown to be missing, and no matter how long I wait, the library > will not update itself. Is there a way to force shotwell to attempt > to locate these? Or could there be in a future release? Normally, a > workaround i find is to re-import (this does happen occasionally if i > accidentally insert the SD card before the hdd), but with all imports > hanging i cannot get my photos to refresh themselves... > > Thanks, > Scott. > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From scott_shotwell at dewie.net.au Mon Nov 26 13:19:24 2012 From: scott_shotwell at dewie.net.au (Scott) Date: Tue, 27 Nov 2012 00:19:24 +1100 Subject: [Shotwell] Shotwell 0.13.1 hanging on import In-Reply-To: <50B3655D.8020106@gmail.com> References: <50B3578E.2090606@dewie.net.au> <50B3655D.8020106@gmail.com> Message-ID: <50B36C5C.6050209@dewie.net.au> Joe, Thanks for the reply, i had a look at the log. The last things i get before it starts chewing through CPU (jumps to about 60-90% of a Core2 2.0Ghz from an avg of around 10%) are these lines: L 22473 2012-11-26 23:52:32 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-10/.rawstudio L 22473 2012-11-26 23:52:40 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio L 22473 2012-11-26 23:52:42 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio L 22473 2012-11-26 23:52:47 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio Reproducable every time, and the same four directories cause the problems... This also causes the process to need to be killed. These directories have been moved, and i am still getting the same results: L 22949 2012-11-27 00:12:52 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio L 22949 2012-11-27 00:12:53 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio L 22949 2012-11-27 00:12:57 [WRN] DirectoryMonitor.vala:912: Skipping hidden file/directory /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio The CPU spikes, disk read stalls and process needs to be killed. I can watch this happening in real time with the log open and system load indicator showing CPU usage, disk write and memory at 500ms intervals. Scott. On Mon 26 Nov 2012 23:49:33 EST, Joseph Bylund wrote: > Scott, > > It's likely it's importing and the progress bar is hung (that's what I > saw). Can you do "export SHOTWELL_LOG=1" and watch > ~/.cache/shotwell/shotwell.log during import? If you're continually > seeing it talk about new photos then it's probably not hung (but the > bar may be). > > To share your backtrace you can upload to dropbox and get a link or > email shotwell at yorba. > > -Joe > > On 11/26/2012 06:50 AM, Scott wrote: >> Hi all, >> >> My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to >> hang on import of anything. What will happen is it will try to get >> the photo's off the SD Card, it will get some of the thumbnails, but >> will freeze half way through. The progress bar will stop moving and >> no more thumbnails will appear. Whats more, when i try to exit, the >> process will not actually quit, until i use either top or >> gnome-system-monitor to kill it manually. I have done a full >> backport, but as i have absolutely no idea what i am looking at, i >> cant tell if it is helpful or not. I also believe that this list >> doesnt allow attachments, is there somewhere i could e-mil them to? >> Is anyone else experiencing this? >> >> On a possibly unrelated note, the library is on an external USB, with >> the database in my home directory. The problem is that i >> accidentally opened shotwell the other day not knowing that the >> external hdd had not been mounted correctly, and as a result the >> entire library has now been shown to be missing, and no matter how >> long I wait, the library will not update itself. Is there a way to >> force shotwell to attempt to locate these? Or could there be in a >> future release? Normally, a workaround i find is to re-import (this >> does happen occasionally if i accidentally insert the SD card before >> the hdd), but with all imports hanging i cannot get my photos to >> refresh themselves... >> >> Thanks, >> Scott. >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From scott_shotwell at dewie.net.au Mon Nov 26 14:01:43 2012 From: scott_shotwell at dewie.net.au (Scott) Date: Tue, 27 Nov 2012 01:01:43 +1100 Subject: [Shotwell] Shotwell 0.13.1 hanging on import In-Reply-To: <50B36C5C.6050209@dewie.net.au> References: <50B3578E.2090606@dewie.net.au> <50B3655D.8020106@gmail.com> <50B36C5C.6050209@dewie.net.au> Message-ID: <50B37647.4010002@dewie.net.au> Sorry, Rookie error. moved contents, but not directories themselves. However the problem still stands. The log has been silent, as has CPU usage and disk stall for a full 20 minutes, plus progress bar has stalled, and absolutely no thumbnails are showing up now. As it is now 1am here i am going to go to bed, and leave this running overnight (again) to test the theory. I will post results in the morning (my time). Scott. On Tue 27 Nov 2012 00:19:24 EST, Scott wrote: > > Joe, > > Thanks for the reply, i had a look at the log. The last things i get > before it starts chewing through CPU (jumps to about 60-90% of a Core2 > 2.0Ghz from an avg of around 10%) are these lines: > > L 22473 2012-11-26 23:52:32 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-10/.rawstudio > L 22473 2012-11-26 23:52:40 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio > L 22473 2012-11-26 23:52:42 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio > L 22473 2012-11-26 23:52:47 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio > > Reproducable every time, and the same four directories cause the > problems... This also causes the process to need to be killed. These > directories have been moved, and i am still getting the same results: > > L 22949 2012-11-27 00:12:52 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio > L 22949 2012-11-27 00:12:53 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio > L 22949 2012-11-27 00:12:57 [WRN] DirectoryMonitor.vala:912: Skipping > hidden file/directory > /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio > > The CPU spikes, disk read stalls and process needs to be killed. I > can watch this happening in real time with the log open and system > load indicator showing CPU usage, disk write and memory at 500ms > intervals. > > > Scott. > > On Mon 26 Nov 2012 23:49:33 EST, Joseph Bylund wrote: >> >> Scott, >> >> It's likely it's importing and the progress bar is hung (that's what I >> saw). Can you do "export SHOTWELL_LOG=1" and watch >> ~/.cache/shotwell/shotwell.log during import? If you're continually >> seeing it talk about new photos then it's probably not hung (but the >> bar may be). >> >> To share your backtrace you can upload to dropbox and get a link or >> email shotwell at yorba. >> >> -Joe >> >> On 11/26/2012 06:50 AM, Scott wrote: >>> >>> Hi all, >>> >>> My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to >>> hang on import of anything. What will happen is it will try to get >>> the photo's off the SD Card, it will get some of the thumbnails, but >>> will freeze half way through. The progress bar will stop moving and >>> no more thumbnails will appear. Whats more, when i try to exit, the >>> process will not actually quit, until i use either top or >>> gnome-system-monitor to kill it manually. I have done a full >>> backport, but as i have absolutely no idea what i am looking at, i >>> cant tell if it is helpful or not. I also believe that this list >>> doesnt allow attachments, is there somewhere i could e-mil them to? >>> Is anyone else experiencing this? >>> >>> On a possibly unrelated note, the library is on an external USB, with >>> the database in my home directory. The problem is that i >>> accidentally opened shotwell the other day not knowing that the >>> external hdd had not been mounted correctly, and as a result the >>> entire library has now been shown to be missing, and no matter how >>> long I wait, the library will not update itself. Is there a way to >>> force shotwell to attempt to locate these? Or could there be in a >>> future release? Normally, a workaround i find is to re-import (this >>> does happen occasionally if i accidentally insert the SD card before >>> the hdd), but with all imports hanging i cannot get my photos to >>> refresh themselves... >>> >>> Thanks, >>> Scott. >>> >>> _______________________________________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From lucas at yorba.org Mon Nov 26 21:01:43 2012 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 26 Nov 2012 13:01:43 -0800 Subject: [Shotwell] Crashes when importing In-Reply-To: References: Message-ID: Hi Grant, Shotwell hasn't used GConf to store configuration data since version 0.11. Versions 0.12.x and later store all of their configuration information in GSettings. This is in-line with GNOME best practices. For what it's worth, the source file mentioned here (gconfsettingsbackend.c) is part of the GConf distribution, not part of Shotwell. So there may be a problem with the GConf setup on your machine. Since you're a Gentoo user, I'm sure you're comfortable using the command line. If you'd like to debug this problem further, I'd recommend running Shotwell from the command line with log output directed to the terminal. You can do this by running the following command: $ SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: shotwell With logging turned on, the Shotwell configuration system is very verbose about reporting changes to the configuration database. If you examine your log file, you should see several lines like this: L 6405 2012-11-26 12:51:59 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'LIBRARY_WINDOW_WIDTH' changed. I'm curious if you see any indication of configuration activity right before the system crashes. Take care, Lucas On Sun, Nov 25, 2012 at 1:49 PM, Grant wrote: > I can import in place, but if I choose to copy to library, shotwell crashes > like this: > > (shotwell:9130): GConf-CRITICAL **: gconf_engine_pop_owner_usage: assertion > `engine->owner_use_count > 0' failed > ** > ERROR:gconfsettingsbackend.c:205:gconf_settings_backend_remove_notifier: > assertion failed: (notifier && g_str_equal (path, notifier->path)) > Aborted > > I'm using 0.13.1 on Gentoo. Should I file a bug? > > - Grant > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From emailgrant at gmail.com Tue Nov 27 02:22:17 2012 From: emailgrant at gmail.com (Grant) Date: Mon, 26 Nov 2012 18:22:17 -0800 Subject: [Shotwell] Crashes when importing In-Reply-To: References: Message-ID: > Shotwell hasn't used GConf to store configuration data since version 0.11. Versions 0.12.x and later store all of their configuration information in GSettings. This is in-line with GNOME best practices. For what it's worth, the source file mentioned here (gconfsettingsbackend.c) is part of the GConf distribution, not part of Shotwell. So there may be a problem with the GConf setup on your machine. > > Since you're a Gentoo user, I'm sure you're comfortable using the command line. If you'd like to debug this problem further, I'd recommend running Shotwell from the command line with log output directed to the terminal. You can do this by running the following command: > > $ SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: shotwell > > With logging turned on, the Shotwell configuration system is very verbose about reporting changes to the configuration database. If you examine your log file, you should see several lines like this: > > L 6405 2012-11-26 12:51:59 [DBG] ConfigurationInterfaces.vala:303: > ConfigurationFacade: engine reports property > 'LIBRARY_WINDOW_WIDTH' changed. > > I'm curious if you see any indication of configuration activity right before the system crashes. Thanks Lucas. I logged to a file instead of the console and I've attached the log. Please let me know if there's anything else you'd like me to try. - Grant >> I can import in place, but if I choose to copy to library, shotwell crashes >> like this: >> >> (shotwell:9130): GConf-CRITICAL **: gconf_engine_pop_owner_usage: assertion >> `engine->owner_use_count > 0' failed >> ** >> ERROR:gconfsettingsbackend.c:205:gconf_settings_backend_remove_notifier: >> assertion failed: (notifier && g_str_equal (path, notifier->path)) >> Aborted >> >> I'm using 0.13.1 on Gentoo. Should I file a bug? >> >> - Grant From jim at yorba.org Tue Nov 27 19:42:00 2012 From: jim at yorba.org (Jim Nelson) Date: Tue, 27 Nov 2012 19:34:00 -0008 Subject: [Shotwell] Yorba PPA In-Reply-To: References: <508fd615.1893cc0a.35e4.5a57@mx.google.com> Message-ID: <50b5178a.e156420a.6b48.5a8b@mx.google.com> Hi Thomas, Yes, it's okay to run both versions on the same database. ?I don't believe any schema changes were made between the two. -- Jim On Wed, Nov 21, 2012 at 5:17 AM, Thomas Novin wrote: On Tue, Nov 20, 2012 at 9:30 PM, Lucas Beeler wrote: > Won't the PPA be updated? It's not as simple as just updating the PPA. The PPA version of Shotwell offered by Yorba and the Canonical-patched version of Shotwell distributed with Ubuntu Quantal differ substantially. Specifically, the Ubuntu-distributed version of Shotwell has been patched such that the Shotwell photo publishing system uses Ubuntu Online Accounts for web service sign-in and authentication. We're moving forward on a number of tracks. For example, we're working to get the UOA support changes integrated into our upstream repo. We're also considering offering a non-UOA version of Shotwell via the PPA but no definitive decision has been made on this yet. Stay tuned. Ok, for now, is it OK to run 0.13.0 and 0.13.1 towards the same DB? I share my Shotwell database so it's the same on three computers in our home. Rgds//Thomas From lucas at yorba.org Tue Nov 27 20:38:38 2012 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 27 Nov 2012 12:38:38 -0800 Subject: [Shotwell] shotwell no crop function In-Reply-To: References: Message-ID: Hi Hendrickus, > I am on Ubuntu 12.04 Mate desktop What if you try running with Unity or the GNOME shell? Does the problem still occur? Take care, Lucas On Tue, Nov 27, 2012 at 2:17 AM, Hendrikus Godvliet < hendrikusgodvliet at gmail.com> wrote: > Lucas > > Nvidea GeForce Go 7300 > Nvidea driver version 295.40 > > > proprietary driver or vice-versa? > I am not aware how to do that. > > I am on Ubuntu 12.04 Mate desktop > > > Hendrikus > From lucas at yorba.org Tue Nov 27 20:40:12 2012 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 27 Nov 2012 12:40:12 -0800 Subject: [Shotwell] Crashes when importing In-Reply-To: References: Message-ID: Hi Grant, Unfortunately the mailing list doesn't support attachments, but you can send the log file directly to the Shotwell engineering team by mailing it to shotwell at yorba.org (note that's just "@yorba.org," not "@lists.yorba.org "). Take care, Lucas On Mon, Nov 26, 2012 at 6:22 PM, Grant wrote: > > Shotwell hasn't used GConf to store configuration data since version > 0.11. Versions 0.12.x and later store all of their configuration > information in GSettings. This is in-line with GNOME best practices. For > what it's worth, the source file mentioned here (gconfsettingsbackend.c) is > part of the GConf distribution, not part of Shotwell. So there may be a > problem with the GConf setup on your machine. > > > > Since you're a Gentoo user, I'm sure you're comfortable using the command > line. If you'd like to debug this problem further, I'd recommend running > Shotwell from the command line with log output directed to the terminal. > You can do this by running the following command: > > > > $ SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: shotwell > > > > With logging turned on, the Shotwell configuration system is very verbose > about reporting changes to the configuration database. If you examine your > log file, you should see several lines like this: > > > > L 6405 2012-11-26 12:51:59 [DBG] ConfigurationInterfaces.vala:303: > > ConfigurationFacade: engine reports property > > 'LIBRARY_WINDOW_WIDTH' changed. > > > > I'm curious if you see any indication of configuration activity right > before the system crashes. > > Thanks Lucas. I logged to a file instead of the console and I've attached > the log. Please let me know if there's anything else you'd like me to try. > > - Grant > > > >> I can import in place, but if I choose to copy to library, shotwell > crashes > >> like this: > >> > >> (shotwell:9130): GConf-CRITICAL **: gconf_engine_pop_owner_usage: > assertion > >> `engine->owner_use_count > 0' failed > >> ** > >> ERROR:gconfsettingsbackend.c:205:gconf_settings_backend_remove_notifier: > >> assertion failed: (notifier && g_str_equal (path, notifier->path)) > >> Aborted > >> > >> I'm using 0.13.1 on Gentoo. Should I file a bug? > >> > >> - Grant > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > From emailgrant at gmail.com Tue Nov 27 22:15:19 2012 From: emailgrant at gmail.com (Grant) Date: Tue, 27 Nov 2012 14:15:19 -0800 Subject: [Shotwell] Crashes when importing In-Reply-To: References: Message-ID: > Hi Grant, > > Unfortunately the mailing list doesn't support attachments, but you can send the log file directly to the Shotwell engineering team by mailing it to shotwell at yorba.org (note that's just "@yorba.org," not "@lists.yorba.org "). No problem, here's the log: L 5280 2012-11-27 14:10:37 [MSG] main.vala:372: Shotwell Photo Manager 0.13.1 L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:316: Searching /home/grant/.gnome2/shotwell/plugins for plugins ... L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:135: Unable to search directory /home/grant/.gnome2/shotwell/plugins for plugins: No such file or directory L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins for plugins ... L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins/builtin for plugins ... L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:424: Loaded SPIT module "Core Slideshow Transitions 0.13.1" (org.yorba.shotwell.transitions) [/usr/lib64/shotwell/plugins/builtin/shotwell-transitions.so] L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:424: Loaded SPIT module "Core Publishing Services 0.13.1" (org.yorba.shotwell.publishing.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing.so] L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:424: Loaded SPIT module "Core Data Import Services 0.13.1" (org.yorba.shotwell.data_imports.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so] L 5280 2012-11-27 14:10:37 [WRN] Resources.vala:42: couldn't load icon set from /usr/lib64/shotwell/plugins/builtin/tumblr.png. L 5280 2012-11-27 14:10:37 [DBG] Plugins.vala:424: Loaded SPIT module "Shotwell Extra Publishing Services 0.13.1" (org.yorba.shotwell.publishing.extras) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so] L 5280 2012-11-27 14:10:37 [MSG] main.vala:43: Verifying database ... L 5280 2012-11-27 14:10:37 [DBG] Db.vala:40: Database schema version 16 created by app version 0.13.1 L 5280 2012-11-27 14:10:37 [DBG] Upgrades.vala:82: Could not delete mimics: /home/grant/.local/share/shotwell/mimics is not a directory L 5280 2012-11-27 14:10:37 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'DISPLAY_BASIC_PROPERTIES' changed. L 5280 2012-11-27 14:10:37 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'EVENTS_SORT_ASCENDING' changed. L 5280 2012-11-27 14:10:37 [DBG] LibraryWindow.vala:268: on_library_monitor_installed: /home/grant/Pictures L 5280 2012-11-27 14:10:38 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'SHOW_WELCOME_DIALOG' changed. L 5280 2012-11-27 14:10:38 [DBG] main.vala:187: 0.794128 seconds to Gtk.main() L 5280 2012-11-27 14:11:14 [DBG] BatchImport.vala:1827: Importing /home/grant/Pictures/2012/08/13/img_20120813_203337.jpg L 5280 2012-11-27 14:11:14 [DBG] BatchImport.vala:1827: Importing /home/grant/Pictures/2012/08/13/img_20120813_124713.jpg This last time it crashed, I got extra output in the terminal which doesn't usually appear even in debug mode: (shotwell:5280): GConf-CRITICAL **: gconf_client_remove_dir: assertion `found->add_count > 0' failed (shotwell:5280): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed ======= Backtrace: ========= /lib64/libc.so.6(+0x7b066)[0x7fe8ef05d066] /usr/lib64/libgconf-2.so.4(+0x199b8)[0x7fe8c9c419b8] /usr/lib64/libgconf-2.so.4(+0x19ae5)[0x7fe8c9c41ae5] /usr/lib64/libgconf-2.so.4(gconf_client_notify_remove+0x68)[0x7fe8c9c500b8] /usr/lib64/gio/modules/libgsettingsgconfbackend.so(+0x4433)[0x7fe8c9e94433] /usr/lib64/libgobject-2.0.so.0(g_object_newv+0x737)[0x7fe8efcf7187] /usr/lib64/libgobject-2.0.so.0(g_object_new_valist+0x1d1)[0x7fe8efcf74c1] /usr/lib64/libgobject-2.0.so.0(g_object_new+0xd9)[0x7fe8efcf77c9] shotwell[0x580245] shotwell[0x581088] shotwell[0x582c6f] shotwell[0x57d6e1] shotwell(app_dirs_get_baked_import_dir+0x48)[0x63dae8] shotwell(library_files_generate_unique_file+0xcc)[0x65c90c] shotwell(library_files_duplicate+0x1ac)[0x65ccbc] shotwell[0x60c197] shotwell[0x483268] /usr/lib64/libglib-2.0.so.0(+0x6ec58)[0x7fe8ef826c58] /usr/lib64/libglib-2.0.so.0(+0x6e385)[0x7fe8ef826385] /lib64/libpthread.so.0(+0x7da6)[0x7fe8ef394da6] /lib64/libc.so.6(clone+0x6d)[0x7fe8ef0cdabd] ======= Memory map: ======== 00400000-007db000 r-xp 00000000 08:02 7555193 /usr/bin/shotwell 009db000-009ee000 r--p 003db000 08:02 7555193 /usr/bin/shotwell 009ee000-009f1000 rw-p 003ee000 08:02 7555193 /usr/bin/shotwell 009f1000-009f4000 rw-p 00000000 00:00 0 02352000-0305b000 rw-p 00000000 00:00 0 [heap] 7fe8b0000000-7fe8b0043000 rw-p 00000000 00:00 0 7fe8b0043000-7fe8b4000000 ---p 00000000 00:00 0 7fe8b4000000-7fe8b4021000 rw-p 00000000 00:00 0 7fe8b4021000-7fe8b8000000 ---p 00000000 00:00 0 7fe8b8000000-7fe8b8043000 rw-p 00000000 00:00 0 7fe8b8043000-7fe8bc000000 ---p 00000000 00:00 0 7fe8bc000000-7fe8bc022000 rw-p 00000000 00:00 0 7fe8bc022000-7fe8c0000000 ---p 00000000 00:00 0 7fe8c0000000-7fe8c019a000 rw-p 00000000 00:00 0 7fe8c019a000-7fe8c4000000 ---p 00000000 00:00 0 7fe8c4e70000-7fe8c4e71000 ---p 00000000 00:00 0 7fe8c4e71000-7fe8c5671000 rw-p 00000000 00:00 0 [stack:5302] 7fe8c5671000-7fe8c5672000 ---p 00000000 00:00 0 7fe8c5672000-7fe8c5e72000 rw-p 00000000 00:00 0 [stack:5301] 7fe8c5e72000-7fe8c5e73000 ---p 00000000 00:00 0 7fe8c5e73000-7fe8c6673000 rw-p 00000000 00:00 0 [stack:5300] 7fe8c6673000-7fe8c6674000 ---p 00000000 00:00 0 7fe8c6674000-7fe8c6e74000 rw-p 00000000 00:00 0 [stack:5298] 7fe8c6e74000-7fe8c70ae000 rw-p 00000000 00:00 0 7fe8c74f0000-7fe8c74f5000 r-xp 00000000 08:02 7152717 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fe8c74f5000-7fe8c76f4000 ---p 00005000 08:02 7152717 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fe8c76f4000-7fe8c76f5000 r--p 00004000 08:02 7152717 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fe8c76f5000-7fe8c76f6000 rw-p 00005000 08:02 7152717 /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fe8c76f6000-7fe8c77a6000 r--p 00000000 08:02 7094801 /usr/share/fonts/dejavu/DejaVuSans.ttf 7fe8c77a6000-7fe8c77a8000 r-xp 00000000 08:02 2040143 /usr/lib64/pango/1.6.0/modules/pango-basic-fc.so 7fe8c77a8000-7fe8c79a7000 ---p 00002000 08:02 2040143 /usr/lib64/pango/1.6.0/modules/pango-basic-fc.so 7fe8c79a7000-7fe8c79a8000 r--p 00001000 08:02 2040143 /usr/lib64/pango/1.6.0/modules/pango-basic-fc.so 7fe8c79a8000-7fe8c79a9000 rw-p 00002000 08:02 2040143 /usr/lib64/pango/1.6.0/modules/pango-basic-fc.so 7fe8c79a9000-7fe8c79b2000 r--s 00000000 08:02 7692498 /var/cache/fontconfig/acc285bc1956c3c4bc7afb41d537a85a-le64.cache-3 7fe8c79b2000-7fe8c79b3000 ---p 00000000 00:00 0 7fe8c79b3000-7fe8c81b3000 rw-p 00000000 00:00 0 [stack:5287] 7fe8c81b3000-7fe8c81b4000 ---p 00000000 00:00 0 7fe8c81b4000-7fe8c89b4000 rw-p 00000000 00:00 0 [stack:5286] 7fe8c89b4000-7fe8c89b5000 ---p 00000000 00:00 0 7fe8c89b5000-7fe8c91b5000 rw-p 00000000 00:00 0 [stack:5285] 7fe8c91b5000-7fe8c91b6000 ---p 00000000 00:00 0 7fe8c91b6000-7fe8c99b6000 rw-p 00000000 00:00 0 [stack:5284] 7fe8c99b6000-7fe8c9a15000 r-xp 00000000 08:02 2540463 /usr/lib64/libORBit-2.so.0.1.0 7fe8c9a15000-7fe8c9c15000 ---p 0005f000 08:02 2540463 /usr/lib64/libORBit-2.so.0.1.0 7fe8c9c15000-7fe8c9c24000 r--p 0005f000 08:02 2540463 /usr/lib64/libORBit-2.so.0.1.0 7fe8c9c24000-7fe8c9c27000 rw-p 0006e000 08:02 2540463 /usr/lib64/libORBit-2.so.0.1.0 7fe8c9c27000-7fe8c9c28000 rw-p 00000000 00:00 0 7fe8c9c28000-7fe8c9c65000 r-xp 00000000 08:02 7530240 /usr/lib64/libgconf-2.so.4.1.5 7fe8c9c65000-7fe8c9e64000 ---p 0003d000 08:02 7530240 /usr/lib64/libgconf-2.so.4.1.5 7fe8c9e64000-7fe8c9e66000 r--p 0003c000 08:02 7530240 /usr/lib64/libgconf-2.so.4.1.5 7fe8c9e66000-7fe8c9e69000 rw-p 0003e000 08:02 7530240 /usr/lib64/libgconf-2.so.4.1.5 7fe8c9e6b000-7fe8c9e78000 r--s 00000000 08:02 7692496 /var/cache/fontconfig/8d4af663993b81a124ee82e610bb31f9-le64.cache-3 7fe8c9e78000-7fe8c9e83000 r--s 00000000 08:02 7692491 /var/cache/fontconfig/d722f191fc173fb8c13c8ea6f285de40-le64.cache-3 7fe8c9e83000-7fe8c9e87000 r--s 00000000 08:02 7692486 /var/cache/fontconfig/a595ca43be94766bbfe429f07fba82d0-le64.cache-3 7fe8c9e87000-7fe8c9e90000 r--s 00000000 08:02 7692465 /var/cache/fontconfig/12b26b760a24f8b4feb03ad48a333a72-le64.cache-3 7fe8c9e90000-7fe8c9e96000 r-xp 00000000 08:02 7530229 /usr/lib64/gio/modules/libgsettingsgconfbackend.so 7fe8c9e96000-7fe8ca095000 ---p 00006000 08:02 7530229 /usr/lib64/gio/modules/libgsettingsgconfbackend.so 7fe8ca095000-7fe8ca096000 r--p 00005000 08:02 7530229 /usr/lib64/gio/modules/libgsettingsgconfbackend.so 7fe8ca096000-7fe8ca097000 rw-p 00006000 08:02 7530229 /usr/lib64/gio/modules/libgsettingsgconfbackend.so 7fe8ca097000-7fe8ca0cd000 r-xp 00000000 08:02 7555586 /usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so 7fe8ca0cd000-7fe8ca2cd000 ---p 00036000 08:02 7555586 /usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so 7fe8ca2cd000-7fe8ca2cf000 r--p 00036000 08:02 7555586 /usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so 7fe8ca2cf000-7fe8ca2d0000 rw-p 00038000 08:02 7555586 /usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so 7fe8ca2d0000-7fe8ca2d1000 rw-p 00000000 00:00 0 7fe8ca2d1000-7fe8ca2f4000 r-xp 00000000 08:02 7555570 /usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so 7fe8ca2f4000-7fe8ca4f3000 ---p 00023000 08:02 7555570 /usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so 7fe8ca4f3000-7fe8ca4f5000 r--p 00022000 08:02 7555570 /usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so 7fe8ca4f5000-7fe8ca4f6000 rw-p 00024000 08:02 7555570 /usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so 7fe8ca4f6000-7fe8ca4fa000 r-xp 00000000 08:02 5089028 /lib64/libuuid.so.1.3.0 7fe8ca4fa000-7fe8ca6f9000 ---p 00004000 08:02 5089028 /lib64/libuuid.so.1.3.0 7fe8ca6f9000-7fe8ca6fa000 r--p 00003000 08:02 5089028 /lib64/libuuid.so.1.3.0 7fe8ca6fa000-7fe8ca6fb000 rw-p 00004000 08:02 5089028 /lib64/libuuid.so.1.3.0 7fe8ca6fb000-7fe8ca712000 r-xp 00000000 08:02 6893145 /usr/lib64/libICE.so.6.3.0 7fe8ca712000-7fe8ca911000 ---p 00017000 08:02 6893145 /usr/lib64/libICE.so.6.3.0 7fe8ca911000-7fe8ca912000 r--p 00016000 08:02 6893145 /usr/lib64/libICE.so.6.3.0 7fe8ca912000-7fe8ca913000 rw-p 00017000 08:02 6893145 /usr/lib64/libICE.so.6.3.0 7fe8ca913000-7fe8ca917000 rw-p 00000000 00:00 0 7fe8ca917000-7fe8ca91e000 r-xp 00000000 08:02 7513160 /usr/lib64/libSM.so.6.0.1 7fe8ca91e000-7fe8cab1e000 ---p 00007000 08:02 7513160 /usr/lib64/libSM.so.6.0.1 7fe8cab1e000-7fe8cab1f000 r--p 00007000 08:02 7513160 /usr/lib64/libSM.so.6.0.1 7fe8cab1f000-7fe8cab20000 rw-p 00008000 08:02 7513160 /usr/lib64/libSM.so.6.0.1 7fe8cab20000-7fe8cab48000 r-xp 00000000 08:02 1771051 /usr/lib64/libdbus-glib-1.so.2.2.2 7fe8cab48000-7fe8cad47000 ---p 00028000 08:02 1771051 /usr/lib64/libdbus-glib-1.so.2.2.2 7fe8cad47000-7fe8cad48000 r--p 00027000 08:02 1771051 /usr/lib64/libdbus-glib-1.so.2.2.2 7fe8cad48000-7fe8cad49000 rw-p 00028000 08:02 1771051 /usr/lib64/libdbus-glib-1.so.2.2.2 7fe8cad49000-7fe8cadaa000 r-xp 00000000 08:02 5120300 /usr/lib64/libXt.so.6.0.0 7fe8cadaa000-7fe8cafaa000 ---p 00061000 08:02 5120300 /usr/lib64/libXt.so.6.0.0 7fe8cafaa000-7fe8cafab000 r--p 00061000 08:02 5120300 /usr/lib64/libXt.so.6.0.0 7fe8cafab000-7fe8cafb0000 rw-p 00062000 08:02 5120300 /usr/lib64/libXt.so.6.0.0 7fe8cafb0000-7fe8cafb1000 rw-p 00000000 00:00 0 7fe8cafb1000-7fe8cb1ab000 r-xp 00000000 08:02 6840482 /usr/lib64/libicui18n.so.49.1.2 7fe8cb1ab000-7fe8cb3ab000 ---p 001fa000 08:02 6840482 /usr/lib64/libicui18n.so.49.1.2 7fe8cb3ab000-7fe8cb3b7000 r--p 001fa000 08:02 6840482 /usr/lib64/libicui18n.so.49.1.2 7fe8cb3b7000-7fe8cb3b9000 rw-p 00206000 08:02 6840482 /usr/lib64/libicui18n.so.49.1.2 7fe8cb3b9000-7fe8cb3f2000 r-xp 00000000 08:02 5940940 /usr/lib64/libxslt.so.1.1.27 7fe8cb3f2000-7fe8cb5f1000 ---p 00039000 08:02 5940940 /usr/lib64/libxslt.so.1.1.27 7fe8cb5f1000-7fe8cb5f2000 r--p 00038000 08:02 5940940 /usr/lib64/libxslt.so.1.1.27 7fe8cb5f2000-7fe8cb5f3000 rw-p 00039000 08:02 5940940 /usr/lib64/libxslt.so.1.1.27 7fe8cb5f3000-7fe8cb5f4000 rw-p 00000000 00:00 0 7fe8cb5f4000-7fe8cb634000 r-xp 00000000 08:02 2752872 /usr/lib64/libjpeg.so.8.0.2 7fe8cb634000-7fe8cb833000 ---p 00040000 08:02 2752872 /usr/lib64/libjpeg.so.8.0.2 7fe8cb833000-7fe8cb834000 r--p 0003f000 08:02 2752872 /usr/lib64/libjpeg.so.8.0.2 7fe8cb834000-7fe8cb835000 rw-p 00040000 08:02 2752872 /usr/lib64/libjpeg.so.8.0.2 7fe8cb835000-7fe8cb845000 rw-p 00000000 00:00 0 7fe8cb845000-7fe8cbc0e000 r-xp 00000000 08:02 6791177 /usr/lib64/libjavascriptcoregtk-3.0.so.0.13.4 7fe8cbc0e000-7fe8cbe0d000 ---p 003c9000 08:02 6791177 /usr/lib64/libjavascriptcoregtk-3.0.so.0.13.4 7fe8cbe0d000-7fe8cbe1a000 r--p 003c8000 08:02 6791177 /usr/lib64/libjavascriptcoregtk-3.0.so.0.13.4 7fe8cbe1a000-7fe8cbe22000 rw-p 003d5000 08:02 6791177 /usr/lib64/libjavascriptcoregtk-3.0.so.0.13.4 7fe8cbe22000-7fe8cbe46000 rw-p 00000000 00:00 0 7fe8cbe46000-7fe8cbe6c000 r-xp 00000000 08:02 393239 /usr/lib64/libjson-glib-1.0.so.0.1400.2 7fe8cbe6c000-7fe8cc06b000 ---p 00026000 08:02 393239 /usr/lib64/libjson-glib-1.0.so.0.1400.2 7fe8cc06b000-7fe8cc06c000 r--p 00025000 08:02 393239 /usr/lib64/libjson-glib-1.0.so.0.1400.2 7fe8cc06c000-7fe8cc06d000 rw-p 00026000 08:02 393239 /usr/lib64/libjson-glib-1.0.so.0.1400.2 7fe8cc06d000-7fe8cc0d6000 r-xp 00000000 08:02 6048996 /usr/lib64/libsoup-2.4.so.1.5.0 7fe8cc0d6000-7fe8cc2d6000 ---p 00069000 08:02 6048996 /usr/lib64/libsoup-2.4.so.1.5.0 7fe8cc2d6000-7fe8cc2d8000 r--p 00069000 08:02 6048996 /usr/lib64/libsoup-2.4.so.1.5.0 7fe8cc2d8000-7fe8cc2da000 rw-p 0006b000 08:02 6048996 /usr/lib64/libsoup-2.4.so.1.5.0 7fe8cc2da000-7fe8cc2ed000 r-xp 00000000 08:02 590757 /usr/lib64/librest-0.7.so.0.0.0 7fe8cc2ed000-7fe8cc4ec000 ---p 00013000 08:02 590757 /usr/lib64/librest-0.7.so.0.0.0 7fe8cc4ec000-7fe8cc4ed000 r--p 00012000 08:02 590757 /usr/lib64/librest-0.7.so.0.0.0 7fe8cc4ed000-7fe8cc4ee000 rw-p 00013000 08:02 590757 /usr/lib64/librest-0.7.so.0.0.0 7fe8cc4ee000-7fe8cdbdb000 r-xp 00000000 08:02 6791181 /usr/lib64/libwebkitgtk-3.0.so.0.13.4 7fe8cdbdb000-7fe8cddda000 ---p 016ed000 08:02 6791181 /usr/lib64/libwebkitgtk-3.0.so.0.13.4 7fe8cddda000-7fe8cdf42000 r--p 016ec000 08:02 6791181 /usr/lib64/libwebkitgtk-3.0.so.0.13.4 7fe8cdf42000-7fe8cdf54000 rw-p 01854000 08:02 6791181 /usr/lib64/libwebkitgtk-3.0.so.0.13.4 7fe8cdf54000-7fe8cdf5c000 rw-p 00000000 00:00 0 7fe8cdf5c000-7fe8cecc2000 r--p 00000000 08:02 5128218 /usr/share/icons/hicolor/icon-theme.cache 7fe8cecc2000-7fe8cfa28000 r--p 00000000 08:02 5128218 /usr/share/icons/hicolor/icon-theme.cache 7fe8cfa28000-7fe8d3b9e000 r--p 00000000 08:02 5128957 /usr/share/icons/gnome/icon-theme.cache 7fe8d3b9e000-7fe8d7d14000 r--p 00000000 08:02 5128957 /usr/share/icons/gnome/icon-theme.cache 7fe8d7d14000-7fe8dbe8a000 r--p 00000000 08:02 5128957 /usr/share/icons/gnome/icon-theme.cache 7fe8dbe8a000-7fe8e0000000 r--p 00000000 08:02 5128957 /usr/share/icons/gnome/icon-theme.cache 7fe8e0000000-7fe8e0021000 rw-p 00000000 00:00 0 7fe8e0021000-7fe8e4000000 ---p 00000000 00:00 0 7fe8e4020000-7fe8e40c5000 r--p 00000000 08:02 7095158 /usr/share/fonts/dejavu/DejaVuSans-Bold.ttf 7fe8e40c5000-7fe8e40d5000 r-xp 00000000 08:02 6357886 /usr/lib64/libgstinterfaces-0.10.so.0.24.0 7fe8e40d5000-7fe8e42d5000 ---p 00010000 08:02 6357886 /usr/lib64/libgstinterfaces-0.10.so.0.24.0 7fe8e42d5000-7fe8e42d6000 r--p 00010000 08:02 6357886 /usr/lib64/libgstinterfaces-0.10.so.0.24.0 7fe8e42d6000-7fe8e42d7000 rw-p 00011000 08:02 6357886 /usr/lib64/libgstinterfaces-0.10.so.0.24.0 7fe8e42d7000-7fe8e42e2000 r-xp 00000000 08:02 6357940 /usr/lib64/libgstapp-0.10.so.0.24.0 7fe8e42e2000-7fe8e44e2000 ---p 0000b000 08:02 6357940 /usr/lib64/libgstapp-0.10.so.0.24.0 7fe8e44e2000-7fe8e44e3000 r--p 0000b000 08:02 6357940 /usr/lib64/libgstapp-0.10.so.0.24.0Aborted - Grant >> > Shotwell hasn't used GConf to store configuration data since version >> 0.11. Versions 0.12.x and later store all of their configuration >> information in GSettings. This is in-line with GNOME best practices. For >> what it's worth, the source file mentioned here (gconfsettingsbackend.c) is >> part of the GConf distribution, not part of Shotwell. So there may be a >> problem with the GConf setup on your machine. >> > >> > Since you're a Gentoo user, I'm sure you're comfortable using the command >> line. If you'd like to debug this problem further, I'd recommend running >> Shotwell from the command line with log output directed to the terminal. >> You can do this by running the following command: >> > >> > $ SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: shotwell >> > >> > With logging turned on, the Shotwell configuration system is very verbose >> about reporting changes to the configuration database. If you examine your >> log file, you should see several lines like this: >> > >> > L 6405 2012-11-26 12:51:59 [DBG] ConfigurationInterfaces.vala:303: >> > ConfigurationFacade: engine reports property >> > 'LIBRARY_WINDOW_WIDTH' changed. >> > >> > I'm curious if you see any indication of configuration activity right >> before the system crashes. >> >> Thanks Lucas. I logged to a file instead of the console and I've attached >> the log. Please let me know if there's anything else you'd like me to try. >> >> - Grant >> >> >> >> I can import in place, but if I choose to copy to library, shotwell >> crashes >> >> like this: >> >> >> >> (shotwell:9130): GConf-CRITICAL **: gconf_engine_pop_owner_usage: >> assertion >> >> `engine->owner_use_count > 0' failed >> >> ** >> >> ERROR:gconfsettingsbackend.c:205:gconf_settings_backend_remove_notifier: >> >> assertion failed: (notifier && g_str_equal (path, notifier->path)) >> >> Aborted >> >> >> >> I'm using 0.13.1 on Gentoo. Should I file a bug? >> >> >> >> - Grant From jim at yorba.org Tue Nov 27 22:45:23 2012 From: jim at yorba.org (Jim Nelson) Date: Tue, 27 Nov 2012 22:37:23 -0008 Subject: [Shotwell] Trouble with Import "Hardware Error" In-Reply-To: <50AEFB99.6020001@gmail.com> References: <50AEFB99.6020001@gmail.com> Message-ID: <50b54285.6a56420a.37c7.7cef@mx.google.com> Hi Joseph, I don't see any error when importing this photo. ?The errors you listed are warnings from Exiv2 and not serious in any way. How are you importing this photo? ?Is it from a camera, a USB stick, or your hard drive? ?Are you copying or importing in-place? -- Jim On Thu, Nov 22, 2012 at 8:29 PM, Joseph Bylund wrote: I'm having some difficulty importing some pictures with shotwell reporting a "hardware error", the only possibly relevant note I see in the log is: L 5607 2012-11-22 23:25:14 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored. L 5607 2012-11-22 23:25:14 [WRN] Invalid JPEG preview image. but those don't look terribly serious. One of the images in question can be found here: http://www.columbia.edu/~jhb2147/img/P1010438.JPG Can someone check if you get the same behavior? In unrelated news, happy thanksgiving to all, and I apologize if any of you recently got some spam from my gmail account. -Joe _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From joseph.bylund at gmail.com Wed Nov 28 20:39:50 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Wed, 28 Nov 2012 15:39:50 -0500 Subject: [Shotwell] Trouble with Import "Hardware Error" In-Reply-To: <50b54285.6a56420a.37c7.7cef@mx.google.com> References: <50AEFB99.6020001@gmail.com> <50b54285.6a56420a.37c7.7cef@mx.google.com> Message-ID: <50B67696.2050007@gmail.com> On 11/27/2012 05:45 PM, Jim Nelson wrote: > Hi Joseph, > > I don't see any error when importing this photo. The errors you > listed are warnings from Exiv2 and not serious in any way. > > How are you importing this photo? Is it from a camera, a USB stick, > or your hard drive? Are you copying or importing in-place? > > -- Jim Jim, I was copying the photos from a local folder. In looking at my preferences I saw the "Import photos to" field was set to (none), after updating this I got the import to work successfully. So I guess there needs to be a check at import time for that directory being set, and if not set maybe pop-up (as much as I dislike popups) a window to allow the user to set it. I don't know how it came unset in the first place. -Joe From preining at logic.at Wed Nov 28 23:54:43 2012 From: preining at logic.at (Norbert Preining) Date: Thu, 29 Nov 2012 08:54:43 +0900 Subject: [Shotwell] Development stalled? Message-ID: <20121128235443.GK29401@gamma.logic.tuwien.ac.at> Hi everyone, is there anything that one can do to reactivate development? Practically no commits, no changes since long time. I have committed several patches to trac, which all somehow get more and more lost. I am running myself since long my own build with the piwigo improvements, the sidebar-can-be-hidden patches and the folder-show patches, all fine, no problems. The more invasive changes implementing the comments system also seem to not get any interest from shotwell devs, although this is one of the longest open requests. Anything else we can do??? I don't want to see my favorite photo manager stall that way away. Best wishes Norbert ------------------------------------------------------------------------ Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ HOFF (vb.) To deny indignantly something which is palpably true. --- Douglas Adams, The Meaning of Liff From jim at yorba.org Thu Nov 29 00:32:09 2012 From: jim at yorba.org (Jim Nelson) Date: Thu, 29 Nov 2012 00:24:09 -0008 Subject: [Shotwell] Trouble with Import "Hardware Error" In-Reply-To: <50B67696.2050007@gmail.com> References: <50AEFB99.6020001@gmail.com> <50b54285.6a56420a.37c7.7cef@mx.google.com> <50B67696.2050007@gmail.com> Message-ID: <50b6ad08.0383440a.5f07.0e1d@mx.google.com> I haven't tried reproducing it, but I ticketed this problem for us to look at soon: http://redmine.yorba.org/issues/6108 ?If you think of anything else that might be important about this problem, please add it to the ticket -- thanks! -- Jim On Wed, Nov 28, 2012 at 12:39 PM, Joseph Bylund wrote: On 11/27/2012 05:45 PM, Jim Nelson wrote: > Hi Joseph, > > I don't see any error when importing this photo. The errors you listed are warnings from Exiv2 and not serious in any way. > > How are you importing this photo? Is it from a camera, a USB stick, or your hard drive? Are you copying or importing in-place? > > -- Jim Jim, I was copying the photos from a local folder. In looking at my preferences I saw the "Import photos to" field was set to (none), after updating this I got the import to work successfully. So I guess there needs to be a check at import time for that directory being set, and if not set maybe pop-up (as much as I dislike popups) a window to allow the user to set it. I don't know how it came unset in the first place. -Joe From scott_shotwell at dewie.net.au Thu Nov 29 04:11:15 2012 From: scott_shotwell at dewie.net.au (Scott) Date: Thu, 29 Nov 2012 15:11:15 +1100 Subject: [Shotwell] Shotwell 0.13.1 hanging on import In-Reply-To: <50B37647.4010002@dewie.net.au> References: <50B3578E.2090606@dewie.net.au> <50B3655D.8020106@gmail.com> <50B36C5C.6050209@dewie.net.au> <50B37647.4010002@dewie.net.au> Message-ID: <50B6E063.9020800@dewie.net.au> Hi all - a progress update... I'm happy to say that it was importing while updating the library, but nothing was telling me what it was doing during this time. Apparently according to the logs it was skipping a directory with around 8k files in it which doesnt exist as far as i know. Does this line in the log mean anything to anyone? L 3327 2012-11-29 14:59:51 [CRT] Directory NikonPreview with 8224 entries considered invalid; not read. This particular one there is over 2000 log entries in 2 minutes. Could explain the high CPU usage... In the previous log file (while i was having the initial unresponsiveness of the first e-mail) it was this one: L 3433 2012-11-27 01:48:23 [CRT] Directory Panasonic with 14848 entries considered invalid; not read. I know my own library structure well and I certainly dont have any directories Panasonic or NikonPreview, although I have once owned a Panasonic and my current camera is a Nikon DSLR, so could this be to do with reading the EXIF or something? Either way, this tends to stall the import process for a long, long time. In the case of the auto-import it was well over an hour of inactivity, in the ase of this current import in progress now it is more like 5-10 minutes. Either way, it is a long time to wait for an unresponsive program to respond... Thanks for the initial help, Scott. On Tue 27 Nov 2012 01:01:43 EST, Scott wrote: > > Sorry, Rookie error. moved contents, but not directories themselves. > However the problem still stands. The log has been silent, as has CPU > usage and disk stall for a full 20 minutes, plus progress bar has > stalled, and absolutely no thumbnails are showing up now. As it is now > 1am here i am going to go to bed, and leave this running overnight > (again) to test the theory. I will post results in the morning (my time). > > Scott. > > On Tue 27 Nov 2012 00:19:24 EST, Scott wrote: >> >> >> Joe, >> >> Thanks for the reply, i had a look at the log. The last things i get >> before it starts chewing through CPU (jumps to about 60-90% of a Core2 >> 2.0Ghz from an avg of around 10%) are these lines: >> >> L 22473 2012-11-26 23:52:32 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-10/.rawstudio >> L 22473 2012-11-26 23:52:40 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio >> L 22473 2012-11-26 23:52:42 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio >> L 22473 2012-11-26 23:52:47 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio >> >> Reproducable every time, and the same four directories cause the >> problems... This also causes the process to need to be killed. These >> directories have been moved, and i am still getting the same results: >> >> L 22949 2012-11-27 00:12:52 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio >> L 22949 2012-11-27 00:12:53 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio >> L 22949 2012-11-27 00:12:57 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio >> >> The CPU spikes, disk read stalls and process needs to be killed. I >> can watch this happening in real time with the log open and system >> load indicator showing CPU usage, disk write and memory at 500ms >> intervals. >> >> >> Scott. >> >> On Mon 26 Nov 2012 23:49:33 EST, Joseph Bylund wrote: >>> >>> >>> Scott, >>> >>> It's likely it's importing and the progress bar is hung (that's what I >>> saw). Can you do "export SHOTWELL_LOG=1" and watch >>> ~/.cache/shotwell/shotwell.log during import? If you're continually >>> seeing it talk about new photos then it's probably not hung (but the >>> bar may be). >>> >>> To share your backtrace you can upload to dropbox and get a link or >>> email shotwell at yorba. >>> >>> -Joe >>> >>> On 11/26/2012 06:50 AM, Scott wrote: >>>> >>>> >>>> Hi all, >>>> >>>> My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to >>>> hang on import of anything. What will happen is it will try to get >>>> the photo's off the SD Card, it will get some of the thumbnails, but >>>> will freeze half way through. The progress bar will stop moving and >>>> no more thumbnails will appear. Whats more, when i try to exit, the >>>> process will not actually quit, until i use either top or >>>> gnome-system-monitor to kill it manually. I have done a full >>>> backport, but as i have absolutely no idea what i am looking at, i >>>> cant tell if it is helpful or not. I also believe that this list >>>> doesnt allow attachments, is there somewhere i could e-mil them to? >>>> Is anyone else experiencing this? >>>> >>>> On a possibly unrelated note, the library is on an external USB, with >>>> the database in my home directory. The problem is that i >>>> accidentally opened shotwell the other day not knowing that the >>>> external hdd had not been mounted correctly, and as a result the >>>> entire library has now been shown to be missing, and no matter how >>>> long I wait, the library will not update itself. Is there a way to >>>> force shotwell to attempt to locate these? Or could there be in a >>>> future release? Normally, a workaround i find is to re-import (this >>>> does happen occasionally if i accidentally insert the SD card before >>>> the hdd), but with all imports hanging i cannot get my photos to >>>> refresh themselves... >>>> >>>> Thanks, >>>> Scott. >>>> >>>> _______________________________________________ >>>> Shotwell mailing list >>>> Shotwell at lists.yorba.org >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> >>> >> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From scott_shotwell at dewie.net.au Thu Nov 29 04:26:24 2012 From: scott_shotwell at dewie.net.au (Scott) Date: Thu, 29 Nov 2012 15:26:24 +1100 Subject: [Shotwell] Trouble with Import "Hardware Error" In-Reply-To: <50b6ad08.0383440a.5f07.0e1d@mx.google.com> References: <50AEFB99.6020001@gmail.com> <50b54285.6a56420a.37c7.7cef@mx.google.com> <50B67696.2050007@gmail.com> <50b6ad08.0383440a.5f07.0e1d@mx.google.com> Message-ID: <50B6E3F0.90300@dewie.net.au> This may not nesseciarily be a shotwell problem, I had these errors right before my previous external hdd failed. It would start to import, then fail due to a 'hardware error'. I would try doing a disk check first and seeing what that comes up with, but i know mine had read errors, right where my library was which was causing hardware errors. If there was an I/O error, this would probably have caused the unsetting of the setting also. Just a thought, Scott. On 29/11/12 11:32, Jim Nelson wrote: > I haven't tried reproducing it, but I ticketed this problem for us to look at soon: http://redmine.yorba.org/issues/6108 If you think of anything else that might be important about this problem, please add it to the ticket -- thanks! > > -- Jim > > On Wed, Nov 28, 2012 at 12:39 PM, Joseph Bylund wrote: > On 11/27/2012 05:45 PM, Jim Nelson wrote: >> Hi Joseph, >> >> I don't see any error when importing this photo. The errors you listed are warnings from Exiv2 and not serious in any way. >> >> How are you importing this photo? Is it from a camera, a USB stick, or your hard drive? Are you copying or importing in-place? >> >> -- Jim > Jim, > > I was copying the photos from a local folder. In looking at my preferences I saw the "Import photos to" field was set to (none), after updating this I got the import to work successfully. So I guess there needs to be a check at import time for that directory being set, and if not set maybe pop-up (as much as I dislike popups) a window to allow the user to set it. I don't know how it came unset in the first place. > > -Joe > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From el.cameleon.1 at gmail.com Thu Nov 29 08:15:19 2012 From: el.cameleon.1 at gmail.com (Vincent) Date: Thu, 29 Nov 2012 09:15:19 +0100 Subject: [Shotwell] Development stalled? In-Reply-To: <20121128235443.GK29401@gamma.logic.tuwien.ac.at> References: <20121128235443.GK29401@gamma.logic.tuwien.ac.at> Message-ID: Hi, I should say that I share the same feeling... I really hope that Yorba is not going in the wrong direction by developing a new mail client (Geary) which seems completely useless as Thunderbird and Evolution are already there, and consequently neglect Shotwell development... Hope that next release will show us the arrival of real innovations in Shotwell (map widget, folder managment,...). At least, if Yorba don't want to invest much time in Shotwell, it would be great if it can improve community contributions with a better patch review system... 2012/11/29 Norbert Preining > Hi everyone, > > is there anything that one can do to reactivate development? Practically > no commits, no changes since long time. > > I have committed several patches to trac, which all somehow get more > and more lost. > > I am running myself since long my own build with the piwigo improvements, > the sidebar-can-be-hidden patches and the folder-show patches, all fine, > no problems. > > The more invasive changes implementing the comments system also seem > to not get any interest from shotwell devs, although this is one of the > longest open requests. > > Anything else we can do??? I don't want to see my favorite photo > manager stall that way away. > > Best wishes > > Norbert > ------------------------------------------------------------------------ > Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} > JAIST, Japan TeX Live & Debian Developer > DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 > ------------------------------------------------------------------------ > HOFF (vb.) > To deny indignantly something which is palpably true. > --- Douglas Adams, The Meaning of Liff > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -- Vincent (cam?l?on) From blklists at elementarea.net Thu Nov 29 09:20:25 2012 From: blklists at elementarea.net (Andreas Brauchli) Date: Thu, 29 Nov 2012 10:20:25 +0100 Subject: [Shotwell] Development stalled? In-Reply-To: References: <20121128235443.GK29401@gamma.logic.tuwien.ac.at> Message-ID: <1354180825.2017.18.camel@thinky> While I would love to see more shotwell development and don't have much use for geary either, the fundamental issue is probably that they have to keep funding. An interesting insight is given in this article: https://lwn.net/Articles/511260/ As for the map widget, it's been tagged just recently for 0.14 (though it also had been tagged for 0.10 but at that point the widget and dependent upstream distro packages were in rather rough shape) but it's certainly not forgotten. Some new features would be great, but I'd rather they keep it stable than adding functionality - our whole picture libraries (minus the backups) depend on it. Whatever it is we certainly all hope for ongoing, steady development of shotwell. Cheers, andreas On Don, 2012-11-29 at 09:15 +0100, Vincent wrote: > Hi, > > I should say that I share the same feeling... > > I really hope that Yorba is not going in the wrong direction by developing > a new mail client (Geary) which seems completely useless as Thunderbird and > Evolution are already there, and consequently neglect Shotwell > development... > > Hope that next release will show us the arrival of real innovations in > Shotwell (map widget, folder managment,...). At least, if Yorba don't want > to invest much time in Shotwell, it would be great if it can improve > community contributions with a better patch review system... > > > 2012/11/29 Norbert Preining > > > Hi everyone, > > > > is there anything that one can do to reactivate development? Practically > > no commits, no changes since long time. > > > > I have committed several patches to trac, which all somehow get more > > and more lost. > > > > I am running myself since long my own build with the piwigo improvements, > > the sidebar-can-be-hidden patches and the folder-show patches, all fine, > > no problems. > > > > The more invasive changes implementing the comments system also seem > > to not get any interest from shotwell devs, although this is one of the > > longest open requests. > > > > Anything else we can do??? I don't want to see my favorite photo > > manager stall that way away. > > > > Best wishes > > > > Norbert > > ------------------------------------------------------------------------ > > Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} > > JAIST, Japan TeX Live & Debian Developer > > DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 > > ------------------------------------------------------------------------ > > HOFF (vb.) > > To deny indignantly something which is palpably true. > > --- Douglas Adams, The Meaning of Liff > > _______________________________________________ > > Shotwell mailing list > > Shotwell at lists.yorba.org > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > > > > From nomnex at gmail.com Thu Nov 29 09:36:30 2012 From: nomnex at gmail.com (nomnex) Date: Thu, 29 Nov 2012 18:36:30 +0900 Subject: [Shotwell] Development stalled? In-Reply-To: <1354180825.2017.18.camel@thinky> References: <20121128235443.GK29401@gamma.logic.tuwien.ac.at> <1354180825.2017.18.camel@thinky> Message-ID: <20121129183630.5619779b.nomnex@gmail.com> > On Thu, 29 Nov 2012 10:20:25 +0100 > Andreas Brauchli wrote: > > > > I am running myself since long my own build with the piwigo > > > improvements, the sidebar-can-be-hidden patches and the > > > folder-show patches, all fine, no problems. Hello, it would really be great to have those in a stable release. Especially the sidebar-can-be-hidden for those with small display notebooks. Best, nomnex -- nomnex Freenode: nomnex Registered Linux user #505281. Be counted at: http://linuxcounter.net From el.cameleon.1 at gmail.com Thu Nov 29 10:04:49 2012 From: el.cameleon.1 at gmail.com (Vincent) Date: Thu, 29 Nov 2012 11:04:49 +0100 Subject: [Shotwell] Fwd: Development stalled? In-Reply-To: References: <20121128235443.GK29401@gamma.logic.tuwien.ac.at> <1354180825.2017.18.camel@thinky> Message-ID: 2012/11/29 Andreas Brauchli > While I would love to see more shotwell development and don't have much > use for geary either, the fundamental issue is probably that they have > to keep funding. An interesting insight is given in this article: > https://lwn.net/Articles/511260/ > Very very interesting reading! No later that yesterday I had set a 5?/month donation to a French website that I love after receiving a mail asking for donation. The important thing is that in 3 days (after the mail) they obtains around 600? of monthly donations, when in 11 months they only got 1500? of monthly donations!!! All raw donations are recorder at http://soutenir.framasoft.org/tous-les-dons Like Yorba, this website has a donate button that I have never click, but the fact to receive a mail with more explanations and all these things make me change my mind, and it seems that I am not the only one ;-) If money is really the problem, maybe Yorba should communicate more about this? -- Vincent (cam?l?on) -- Vincent (cam?l?on) From jim at yorba.org Thu Nov 29 22:05:35 2012 From: jim at yorba.org (Jim Nelson) Date: Thu, 29 Nov 2012 21:57:35 -0008 Subject: [Shotwell] Shotwell 0.13.1 hanging on import In-Reply-To: <50B6E063.9020800@dewie.net.au> References: <50B3578E.2090606@dewie.net.au> <50B3655D.8020106@gmail.com> <50B36C5C.6050209@dewie.net.au> <50B37647.4010002@dewie.net.au> <50B6E063.9020800@dewie.net.au> Message-ID: <50b7dc2e.a24b420a.594c.ffff8e75@mx.google.com> The log message you're seeing is coming from Exiv2, meaning that it encountered some piece of metadata in a photo file that it couldn't parse. ?This is harmless and doesn't affect Shotwell's operation in any way. Import can take a while with a large photo library. ?Shotwell shouldn't be completely unresponsive while it's importing. ?Can you tell me how many photos you're attempting to import? ?How many photos are in your library before you start the import? -- Jim On Wed, Nov 28, 2012 at 8:11 PM, Scott wrote: Hi all - a progress update... I'm happy to say that it was importing while updating the library, but nothing was telling me what it was doing during this time. Apparently according to the logs it was skipping a directory with around 8k files in it which doesnt exist as far as i know. Does this line in the log mean anything to anyone? L 3327 2012-11-29 14:59:51 [CRT] Directory NikonPreview with 8224 entries considered invalid; not read. This particular one there is over 2000 log entries in 2 minutes. Could explain the high CPU usage... In the previous log file (while i was having the initial unresponsiveness of the first e-mail) it was this one: L 3433 2012-11-27 01:48:23 [CRT] Directory Panasonic with 14848 entries considered invalid; not read. I know my own library structure well and I certainly dont have any directories Panasonic or NikonPreview, although I have once owned a Panasonic and my current camera is a Nikon DSLR, so could this be to do with reading the EXIF or something? Either way, this tends to stall the import process for a long, long time. In the case of the auto-import it was well over an hour of inactivity, in the ase of this current import in progress now it is more like 5-10 minutes. Either way, it is a long time to wait for an unresponsive program to respond... Thanks for the initial help, Scott. On Tue 27 Nov 2012 01:01:43 EST, Scott wrote: > > Sorry, Rookie error. moved contents, but not directories themselves. > However the problem still stands. The log has been silent, as has CPU > usage and disk stall for a full 20 minutes, plus progress bar has > stalled, and absolutely no thumbnails are showing up now. As it is now > 1am here i am going to go to bed, and leave this running overnight > (again) to test the theory. I will post results in the morning (my time). > > Scott. > > On Tue 27 Nov 2012 00:19:24 EST, Scott wrote: >> >> >> Joe, >> >> Thanks for the reply, i had a look at the log. The last things i get >> before it starts chewing through CPU (jumps to about 60-90% of a Core2 >> 2.0Ghz from an avg of around 10%) are these lines: >> >> L 22473 2012-11-26 23:52:32 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-10/.rawstudio >> L 22473 2012-11-26 23:52:40 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio >> L 22473 2012-11-26 23:52:42 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio >> L 22473 2012-11-26 23:52:47 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio >> >> Reproducable every time, and the same four directories cause the >> problems... This also causes the process to need to be killed. These >> directories have been moved, and i am still getting the same results: >> >> L 22949 2012-11-27 00:12:52 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio >> L 22949 2012-11-27 00:12:53 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio >> L 22949 2012-11-27 00:12:57 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio >> >> The CPU spikes, disk read stalls and process needs to be killed. I >> can watch this happening in real time with the log open and system >> load indicator showing CPU usage, disk write and memory at 500ms >> intervals. >> >> >> Scott. >> >> On Mon 26 Nov 2012 23:49:33 EST, Joseph Bylund wrote: >>> >>> >>> Scott, >>> >>> It's likely it's importing and the progress bar is hung (that's what I >>> saw). Can you do "export SHOTWELL_LOG=1" and watch >>> ~/.cache/shotwell/shotwell.log during import? If you're continually >>> seeing it talk about new photos then it's probably not hung (but the >>> bar may be). >>> >>> To share your backtrace you can upload to dropbox and get a link or >>> email shotwell at yorba. >>> >>> -Joe >>> >>> On 11/26/2012 06:50 AM, Scott wrote: >>>> >>>> >>>> Hi all, >>>> >>>> My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to >>>> hang on import of anything. What will happen is it will try to get >>>> the photo's off the SD Card, it will get some of the thumbnails, but >>>> will freeze half way through. The progress bar will stop moving and >>>> no more thumbnails will appear. Whats more, when i try to exit, the >>>> process will not actually quit, until i use either top or >>>> gnome-system-monitor to kill it manually. I have done a full >>>> backport, but as i have absolutely no idea what i am looking at, i >>>> cant tell if it is helpful or not. I also believe that this list >>>> doesnt allow attachments, is there somewhere i could e-mil them to? >>>> Is anyone else experiencing this? >>>> >>>> On a possibly unrelated note, the library is on an external USB, with >>>> the database in my home directory. The problem is that i >>>> accidentally opened shotwell the other day not knowing that the >>>> external hdd had not been mounted correctly, and as a result the >>>> entire library has now been shown to be missing, and no matter how >>>> long I wait, the library will not update itself. Is there a way to >>>> force shotwell to attempt to locate these? Or could there be in a >>>> future release? Normally, a workaround i find is to re-import (this >>>> does happen occasionally if i accidentally insert the SD card before >>>> the hdd), but with all imports hanging i cannot get my photos to >>>> refresh themselves... >>>> >>>> Thanks, >>>> Scott. >>>> >>>> _______________________________________________ >>>> Shotwell mailing list >>>> Shotwell at lists.yorba.org >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> >>> >> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From rehmann at math.uni-bielefeld.de Thu Nov 29 23:57:06 2012 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Fri, 30 Nov 2012 00:57:06 +0100 Subject: [Shotwell] Again: Bug #4300 Shotwell view state is incorrect at startup Message-ID: <87fw3s7yjx.fsf@rhea.lan> It seems that bug #4300 is still not fixed (or was revived). Pages rated "Rejected" are initially shown in version 13.0 as well as in 13.1. As far as I can tell, the code to fix this problem as mentioned on http://redmine.yorba.org/issues/4300 is (in slightly modified version) contained in my 13.1 sources, but does not seem to work. I am working on Ubuntu 12.10. Can anybody help? Best regards Ulf From jim at yorba.org Fri Nov 30 01:27:40 2012 From: jim at yorba.org (Jim Nelson) Date: Fri, 30 Nov 2012 01:19:40 -0008 Subject: [Shotwell] Again: Bug #4300 Shotwell view state is incorrect at startup In-Reply-To: <87fw3s7yjx.fsf@rhea.lan> References: <87fw3s7yjx.fsf@rhea.lan> Message-ID: <50b80b8a.29bf440a.595b.ffffafcb@mx.google.com> Hi Ulf, I can reproduce the problem you're seeing. ?I've re-opened the bug for 0.14. -- Jim On Thu, Nov 29, 2012 at 3:57 PM, Ulf Rehmann wrote: It seems that bug #4300 is still not fixed (or was revived). Pages rated "Rejected" are initially shown in version 13.0 as well as in 13.1. As far as I can tell, the code to fix this problem as mentioned on http://redmine.yorba.org/issues/4300 is (in slightly modified version) contained in my 13.1 sources, but does not seem to work. I am working on Ubuntu 12.10. Can anybody help? Best regards Ulf _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Fri Nov 30 02:18:58 2012 From: jim at yorba.org (Jim Nelson) Date: Fri, 30 Nov 2012 02:10:58 -0008 Subject: [Shotwell] The state of Shotwell and Geary Message-ID: <50b81790.e38a440a.75e9.ffffb9f7@mx.google.com> Hello all, Recent messages on the Shotwell mailing list have made inquiries about a slowing of the pace of development of the project. ?Looking at the Geary commit log, you would see a similar dimming of activity. ?We also have several outstanding unreviewed patches for both projects. ?We acknowledge this situation and want to let you know that we don't like it any more than you do. However, the situation isn't permanent. ?Yorba currently has a work commitment it must meet which has impacted development of our other projects. ?I can't go into the details of the commitment, but the good news is that it ultimately helps Yorba further development of Shotwell and Geary. We are already planning the next releases of both projects. ?For Shotwell 0.14, we want to focus on: * Improving the photo import experience * Fixing several outstanding RAW image bugs * Working better with the filesystem, including an option to store fully-transformed images on disk without destroying your originals * Adding a folder tree to the sidebar (indicating where photos are stored on your hard disk) For Geary, we plan on turning our attention to: * Multiple user accounts * Email search * Better support for non-Gmail/Yahoo servers (in particular, Dovecot) * Mail notifications even when Geary isn't running Other features, bug fixes, and stabilization work are planned as well. ?For more fine-grained information, see Yorba's Redmine server at http://redmine.yorba.org/ Unfortunately I can't promise when this work will begin. ?The commitment I mentioned must be satisfied and we're working diligently to complete it. ?All I can ask from our community is some patience and to know that we fully intend to return to both projects shortly. -- Jim Nelson Yorba Foundation From clanlaw at googlemail.com Fri Nov 30 09:05:03 2012 From: clanlaw at googlemail.com (Colin Law) Date: Fri, 30 Nov 2012 09:05:03 +0000 Subject: [Shotwell] The state of Shotwell and Geary In-Reply-To: <50b81790.e38a440a.75e9.ffffb9f7@mx.google.com> References: <50b81790.e38a440a.75e9.ffffb9f7@mx.google.com> Message-ID: On 30 November 2012 02:18, Jim Nelson wrote: > Hello all, > > Recent messages on the Shotwell mailing list have made inquiries about a slowing of the pace of development of the project. Looking at the Geary commit log, you would see a similar dimming of activity. We also have several outstanding unreviewed patches for both projects. We acknowledge this situation and want to let you know that we don't like it any more than you do. > > However, the situation isn't permanent. Yorba currently has a work commitment it must meet which has impacted development of our other projects. I can't go into the details of the commitment, but the good news is that it ultimately helps Yorba further development of Shotwell and Geary. > > We are already planning the next releases of both projects. For Shotwell 0.14, we want to focus on: That is great to hear. Thanks for letting us know. Colin From thomas at xyz.pp.se Fri Nov 30 21:12:09 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Fri, 30 Nov 2012 22:12:09 +0100 Subject: [Shotwell] Failure to create thumbnails after start Message-ID: Hello I was starting Shotwell and I knew that a few hundred thumbnails was missing. Because I've had problem with this before I did export SHOTWELL_LOG=1 before starting. Could see in the log that it was working (and on the CPU usage). Then all of a sudden the CPU was constant at 100% but the log stopped. Now, 10 minutes later, the CPU is still 100% but nothing in the log. Shotwell is greyed out (unresponsive) if I try to switch to that window in the DE. Here is the log: http://paste.ubuntu.com/1400573/ Next start I did the rest of the thumbnails got created OK. Rgds//Thomas