From estebancster at gmail.com Sat Sep 1 04:38:14 2012 From: estebancster at gmail.com (Esteban Cervetto) Date: Sat, 1 Sep 2012 01:38:14 -0300 Subject: [Shotwell] compiling face recogntion In-Reply-To: References: <50290224.8697320a.702f.fffff9f8@mx.google.com> Message-ID: I would like how can i install the FaceTool http://redmine.yorba.org/projects/shotwell/wiki/FacesTool implemented on August 27, 2012 I was installed the old valentin repository git clone git://github.com/Sanva/shotwell-gsoc.git but only shows a tool that you have to identify manually the faces by mean a rectangle tool and had compiled the ours I didn't fint it twice! 2012/8/14 Esteban Cervetto : > Hola Valent?n! > > Estoy siguiendo tu proyecto de detecci?n de rostros. > Como usuario final, me gustar?a ser uno de los primeros en probarlo ;-) > > Lo que no pude hacer fue lograr que Shotwell me reconozca > autom?ticamente las caras. Si logre que me permita identificarlas > manualmente > > Compil? lo siguiente: > > #git init > #clono codigo prestado Shotwell > #git clone git://github.com/Sanva/shotwell-gsoc.git > #le incorporo el desarrollo de facedetect que esta en esta revision > #git merge 6c805edfbf0ed0e2a42a38f8efda51003dd5f5f2 > > luego compilo > #./configure --define=ENABLE_FACES > #make > #./shotwell > > Hice algo mal? > > Saludos! > > > > > 2012/8/13 Adam Dingle : >> Esteban, >> >> there is no face recognition code in Shotwell's git repository, so I'm not >> surprised that you didn't see it. :) Valent?n Barros has been working on >> adding face recognition as a Google Summer of Code project, but none of his >> changes have been committed to trunk yet. You can read about his progress >> on his blog at http://sanva.net/ . If you get in touch with him, he can >> tell you more. We hope to commit some of his changes in time for the >> upcoming 0.13 release. Cheers - >> >> adam >> >> >> On Sun, Aug 12, 2012 at 9:28 PM, Esteban Cervetto >> wrote: >> >> hello: >> >> I was compiled the latest version of Shotwell from Git with >> >> git clone git://yorba.org/shotwell >> >> but I can't see the face-recognition feature >> >> I could not figure out the answer to get try face-recognition >> >> >> Regards >> >> Esteban >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> From shotwell at svenningsen.dk Sun Sep 2 16:20:42 2012 From: shotwell at svenningsen.dk (Rikard Svenningsen) Date: Sun, 2 Sep 2012 18:20:42 +0200 Subject: [Shotwell] Regarding Fujifilm RAF format, and conversion. Message-ID: Hi I have just start using this great tool, I am going to use it for my RAF files. I was looking for some way to make a batch conversion of my RAF files, there are tools to do it, but no one in the same quality as Shotwell. I used a tool like UFRaw or Rawstudio they all come up with a defektive image with grey bars. This is of couce not a problem for the developer of Shotwell, and I just say it to warn against using any of the same rutines used in those tools. What I would like is a way to put my RAF files in a conversion queue, and be able to convert to TIFF and/or JPG. This tool is the best! Best regards Rikard Svenningsen From scott_shotwell at dewie.net.au Mon Sep 3 01:06:54 2012 From: scott_shotwell at dewie.net.au (Scott) Date: Mon, 03 Sep 2012 11:06:54 +1000 Subject: [Shotwell] Regarding Fujifilm RAF format, and conversion. In-Reply-To: References: Message-ID: <504402AE.7080300@dewie.net.au> Hi Rikard, You should be able to select multiple items in library view, then hit File > Export (or the hotkey: Ctrl+Shift+E), select your format and follow the prompts. Note though, that at present, Shotwell doesnt export metadata to the JPG or TIFF due to bugs with RAW files, but this can be done if needed using exiftool. Most of my workflow is in NEF RAW format, so it may be different with Fuji RAF, but NEF's definately dont get metadata exported... Hope this helps, Scott. On 03/09/12 02:20, Rikard Svenningsen wrote: > Hi > I have just start using this great tool, I am going to use it for my RAF > files. > I was looking for some way to make a batch conversion of my RAF files, > there are tools to do it, but no one in the same quality as Shotwell. > > I used a tool like UFRaw or Rawstudio they all come up with a defektive > image with grey bars. > > This is of couce not a problem for the developer of Shotwell, and I just > say it to warn against using any of the same rutines used in those tools. > > What I would like is a way to put my RAF files in a conversion queue, and > be able to convert to TIFF and/or JPG. > > This tool is the best! > > Best regards > Rikard Svenningsen > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From maxxer at ufficyo.com Mon Sep 3 14:38:00 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Mon, 3 Sep 2012 16:38:00 +0200 (CEST) Subject: [Shotwell] Photo library location Message-ID: <756498110.91260.1346683080529.JavaMail.root@yetopen.it> While I wait to import my Fspot collection, I was trying to use a fresh shotwell installation for my summer pics. I keep my photos on a remotely mounted SMB share, and with fspot I used to create a link to .gvfs/whatever on wherever/Photos -> ~/Photos. If I try to select this location on shotwell it places the pictures in my home (~/2012 and so on). I tried forcing the dir with gconf-editor but didn't work, still placing them on the home. Isn't this supported? thanks -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From maxxer at ufficyo.com Mon Sep 3 14:28:54 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Mon, 3 Sep 2012 16:28:54 +0200 (CEST) Subject: [Shotwell] FSpot Import - resume? Message-ID: <1272784310.91234.1346682534433.JavaMail.root@yetopen.it> Hi. Is F-Spot import resumable? I have a very huge collection that won't import in just one step. If I run it once and cancel, can I start from where I aborted the operation? thanks -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From brunogirin at gmail.com Mon Sep 3 18:16:05 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Mon, 03 Sep 2012 19:16:05 +0100 Subject: [Shotwell] FSpot Import - resume? In-Reply-To: <1272784310.91234.1346682534433.JavaMail.root@yetopen.it> References: <1272784310.91234.1346682534433.JavaMail.root@yetopen.it> Message-ID: <5044F3E5.6080501@gmail.com> On 03/09/12 15:28, Lorenzo Milesi wrote: > Hi. > Is F-Spot import resumable? > I have a very huge collection that won't import in just one step. If I run it once and cancel, can I start from where I aborted the operation? > > thanks > Lorenzo, It should resume where you left it as it will check whether F-Spot photos have already been imported. Whether it actually enables you to import a large collection in several steps without issue is another question. I haven't had a large database at my disposal when writing the import so I haven't been able to check performance as much as I would have liked. If you want to try, I'd suggest you back up your Shotwell and F-Spot databases before starting. If it fails, report the problems here and we will try to fix them. Cheers, Bruno From maxxer at ufficyo.com Tue Sep 4 07:01:58 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Tue, 4 Sep 2012 09:01:58 +0200 (CEST) Subject: [Shotwell] FSpot Import - resume? In-Reply-To: <5044F3E5.6080501@gmail.com> Message-ID: <1156184750.94004.1346742118887.JavaMail.root@yetopen.it> > It should resume where you left it as it will check whether F-Spot > photos have already been imported. Whether it actually enables you to > import a large collection in several steps without issue is another > question. What's the difference between the ability to resume and import a large collection in steps? :) I already tried importing once, and 48h weren't enough :( My fspot db contains 60k photos... thanks -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From adam at yorba.org Tue Sep 4 18:29:41 2012 From: adam at yorba.org (Adam Dingle) Date: Tue, 04 Sep 2012 18:22:41 -0007 Subject: [Shotwell] Photo library location In-Reply-To: <756498110.91260.1346683080529.JavaMail.root@yetopen.it> References: <756498110.91260.1346683080529.JavaMail.root@yetopen.it> Message-ID: <50464897.28bd440a.2bc4.ffff9a4c@mx.google.com> Lorenzo, First, this sounds a bit like this bug: http://redmine.yorba.org/issues/4834 I just tried to reproduce your problem: I connected to an SMB share from Nautilus, and then in Shotwell I set my library directory to a directory under ~/.gvfs representing a directory on the SMB share. ?I then imported a few photos and at first it seemed to work: the photos were copied to the remote share. ?But then Shotwell hung and I had to kill it. ?So it looks like I saw a different form of failure than you did. ?:) In any case, I've opened a new ticket here: http://redmine.yorba.org/issues/5764 To be honest, I think investigating this won't be a high priority for us since we're not huge fans of SMB, but I hope we'll get a chance to look into this more at some point. ?Cheers - adam On Mon, Sep 3, 2012 at 7:38 AM, Lorenzo Milesi wrote: While I wait to import my Fspot collection, I was trying to use a fresh shotwell installation for my summer pics. I keep my photos on a remotely mounted SMB share, and with fspot I used to create a link to .gvfs/whatever on wherever/Photos -> ~/Photos. If I try to select this location on shotwell it places the pictures in my home (~/2012 and so on). I tried forcing the dir with gconf-editor but didn't work, still placing them on the home. Isn't this supported? thanks -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From maxxer at ufficyo.com Tue Sep 4 18:46:25 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Tue, 4 Sep 2012 20:46:25 +0200 (CEST) Subject: [Shotwell] Photo library location In-Reply-To: <50464897.28bd440a.2bc4.ffff9a4c@mx.google.com> Message-ID: <1264989734.96442.1346784385060.JavaMail.root@yetopen.it> > To be honest, I think investigating this won't be a high priority for > us since we're not huge fans of SMB, but I hope we'll get a ch ance > to look into this more at some point. Cheers - Thanks for the investigation. About your last statement, do you propose any suggestion to work around this? thanks again! maxxer -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From adam at yorba.org Tue Sep 4 18:53:30 2012 From: adam at yorba.org (Adam Dingle) Date: Tue, 04 Sep 2012 18:46:30 -0007 Subject: [Shotwell] Photo library location In-Reply-To: <1264989734.96442.1346784385060.JavaMail.root@yetopen.it> References: <1264989734.96442.1346784385060.JavaMail.root@yetopen.it> Message-ID: <50464e2c.a6e7440a.3388.ffffa474@mx.google.com> On Tue, Sep 4, 2012 at 11:46 AM, Lorenzo Milesi wrote: > To be honest, I think investigating this won't be a high priority for > us since we're not huge fans of SMB, but I hope we'll get a ch ance > to look into this more at some point. Cheers - Thanks for the investigation. About your last statement, do you propose any suggestion to work around this? thanks again! Well, Shotwell wasn't really designed to have library photos on a network drive, and we've done very little testing in that configuration. ?And there are other known issues with accessing photos over SMB or other protocols, e.g. http://redmine.yorba.org/issues/2787 http://redmine.yorba.org/issues/2878 So my strong recommendation is to keep your photos in a directory on a local drive, and to use some sort of file syncing mechanism (such as SparkleShare or Ubuntu One or Dropbox or rsync) to copy them to where you want them to be. ?At least, Shotwell will be much happier that way today. In the long run, we'd like Shotwell to know how to sync your photo library: http://redmine.yorba.org/issues/1292 But we're not there yet. ?Cheers - adam From thomas at xyz.pp.se Tue Sep 4 19:17:13 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Tue, 4 Sep 2012 21:17:13 +0200 Subject: [Shotwell] Photo library location In-Reply-To: <756498110.91260.1346683080529.JavaMail.root@yetopen.it> References: <756498110.91260.1346683080529.JavaMail.root@yetopen.it> Message-ID: On Mon, Sep 3, 2012 at 4:38 PM, Lorenzo Milesi wrote: > While I wait to import my Fspot collection, I was trying to use a fresh shotwell installation for my summer pics. > I keep my photos on a remotely mounted SMB share, and with fspot I used to create a link to .gvfs/whatever on wherever/Photos -> ~/Photos. > > If I try to select this location on shotwell it places the pictures in my home (~/2012 and so on). > I tried forcing the dir with gconf-editor but didn't work, still placing them on the home. > > Isn't this supported? I can guarantee you will have better results using NFS instead of SMB. Most fileservers support it. You can start Shotwell with a script to ensure that the library is available (I also use it because I have several Shotwell clients sharing the same DB). I'm pasting my own script which I'm sure could be a lot better done but it works for me.. -- #!/bin/bash #set -x NFSSHARE=10.0.0.100:/Shared MOUNTDIR=/media/nfs_shared if [ -f ${MOUNTDIR}/Photos/.shotwell/data/photo.db ]; then echo "${MOUNTDIR} mounted, ok" if [ -f ${MOUNTDIR}/Photos/.shotwell/data/photo.db.lock ]; then echo "lockfile already exists, exiting.." exit 99 fi touch ${MOUNTDIR}/Photos/.shotwell/data/photo.db.lock echo "created lockfile" /usr/bin/shotwell echo "shotwell closed, removing lockfile" rm -v ${MOUNTDIR}/Photos/.shotwell/data/photo.db.lock echo "umounting nfs" sudo umount ${NFSSHARE} else echo "${MOUNTDIR} not mounted, trying to mount" sudo mount -t nfs -o soft,retry=1,proto=tcp,timeo=10,retrans=2 ${NFSSHARE} ${MOUNTDIR} exec $0 fi From maxxer at ufficyo.com Tue Sep 4 20:30:01 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Tue, 4 Sep 2012 22:30:01 +0200 (CEST) Subject: [Shotwell] Photo library location In-Reply-To: <923695146.99231.1346790598110.JavaMail.root@yetopen.it> Message-ID: <1553254172.99243.1346790601322.JavaMail.root@yetopen.it> > So my strong recommendation is to keep your photos in a directory on > a local drive, and to use some sort of file syncing mechanism (such > as SparkleShare or Ubuntu One or Dropbox or rsync) to copy them to > where you want them to be. At least, Shotwell will be much happier > that way today. Unfortunately keeping pictures locally is not possible nowadays. With SD cards which can store up to 16G, a 320Gb hdd can be filled up pretty quickly. Luckily it seems that shotwell is happier when mounting the remote storage with mount command instead of gvfs. I'll try to remember not to open shotwell when the destination is unmounted. thanks -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From lucas at yorba.org Tue Sep 4 22:26:39 2012 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 4 Sep 2012 15:26:39 -0700 Subject: [Shotwell] compiling face recogntion In-Reply-To: References: <50290224.8697320a.702f.fffff9f8@mx.google.com> Message-ID: Hi Esteban, You can't install or use the Faces Tool yet. Valentin and I are still working to glue the two parts of his project together. The first part is the Faces Tool UI in Shotwell and the second part is a family of helper programs written in C++ that Shotwell spawns as external processes to do face detection and recognition. I'm hoping that we'll get these two parts integrated and then commit the integrated whole to a branch in the Yorba repo within the next few weeks. Once that happens, you should be able to pull from that branch to get Faces Tool support. Cheers, Lucas On Fri, Aug 31, 2012 at 9:38 PM, Esteban Cervetto wrote: > I would like how can i install the FaceTool > http://redmine.yorba.org/projects/shotwell/wiki/FacesTool implemented > on August 27, 2012 > I was installed the old valentin repository > git clone git://github.com/Sanva/shotwell-gsoc.git > but only shows a tool that you have to identify manually the faces by > mean a rectangle tool > > and had compiled the ours > > I didn't fint it twice! > > > > > 2012/8/14 Esteban Cervetto : >> Hola Valent?n! >> >> Estoy siguiendo tu proyecto de detecci?n de rostros. >> Como usuario final, me gustar?a ser uno de los primeros en probarlo ;-) >> >> Lo que no pude hacer fue lograr que Shotwell me reconozca >> autom?ticamente las caras. Si logre que me permita identificarlas >> manualmente >> >> Compil? lo siguiente: >> >> #git init >> #clono codigo prestado Shotwell >> #git clone git://github.com/Sanva/shotwell-gsoc.git >> #le incorporo el desarrollo de facedetect que esta en esta revision >> #git merge 6c805edfbf0ed0e2a42a38f8efda51003dd5f5f2 >> >> luego compilo >> #./configure --define=ENABLE_FACES >> #make >> #./shotwell >> >> Hice algo mal? >> >> Saludos! >> >> >> >> >> 2012/8/13 Adam Dingle : >>> Esteban, >>> >>> there is no face recognition code in Shotwell's git repository, so I'm not >>> surprised that you didn't see it. :) Valent?n Barros has been working on >>> adding face recognition as a Google Summer of Code project, but none of his >>> changes have been committed to trunk yet. You can read about his progress >>> on his blog at http://sanva.net/ . If you get in touch with him, he can >>> tell you more. We hope to commit some of his changes in time for the >>> upcoming 0.13 release. Cheers - >>> >>> adam >>> >>> >>> On Sun, Aug 12, 2012 at 9:28 PM, Esteban Cervetto >>> wrote: >>> >>> hello: >>> >>> I was compiled the latest version of Shotwell from Git with >>> >>> git clone git://yorba.org/shotwell >>> >>> but I can't see the face-recognition feature >>> >>> I could not figure out the answer to get try face-recognition >>> >>> >>> Regards >>> >>> Esteban >>> _______________________________________________ >>> 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 kawazu428 at gmail.com Wed Sep 5 08:55:04 2012 From: kawazu428 at gmail.com (Kristian Rink) Date: Wed, 5 Sep 2012 10:55:04 +0200 Subject: [Shotwell] multi-machine setup? Message-ID: Folks; I've been playing with shotwell for quite a while so far, yet one thing kept me from "fully" using it: Usually, in my "imaging" workflow there are more than one machines involved, between which I usually transfer images in this way or the other, and between which I also want to have shotwell information (starred / tagged images, ...) shared to make things meaningful and not do the same work over and over again. So to ask: Is there sort of a "best practise" setup how to deal with shotwell database and image files if using both on multiple computers? Would keeping both on an USB drive be a way to go? How do you do these things? TIA and all the best, Kristian From lbc at bnrlabs.com Wed Sep 5 14:53:39 2012 From: lbc at bnrlabs.com (Lucas B. Cohen) Date: Wed, 05 Sep 2012 16:53:39 +0200 Subject: [Shotwell] multi-machine setup? In-Reply-To: References: Message-ID: <50476773.5040402@bnrlabs.com> On 2012.09.05 10:55, Kristian Rink wrote: > Is there sort of a > "best practise" setup how to deal with shotwell database and image files if > using both on multiple computers? Would keeping both on an USB drive be a > way to go? How do you do these things? Hi Kristian. Your will be way better off if you avoid any setup where you use storage devices that are locally attached to your different computers, such as USB thumb drives or portables hard disk drives that you will have to plug and unplug, move around, and most importantly, will give your set of files different logical addresses across the different computer, which will make your workflow that much more loaded with overhead. Instead, by using a single, centralized source of storage, that is accessible via your local network (whether is uses physical cable connections, or a Wi-Fi network setup). All your computers, fairly independently of the different operating systems they may be running, can access them using the same network file sharing scheme, CIFS/SMB. You can choose any of your different workstations to act as that central storage point, or you could dedicate a whole computer to storing your files and making them accessible over your local network. If your picture collection starts to get too large, you can use a NAS devices made by companies like Synology, QNAP, or NetGear, which are computers designed to easily hook-up to your local network and let you put your files on it. Using a central storage point should also make it easier and faster to backup and restore your photo collection and "workshop" temporary files. Hope it helps, Lucas From kawazu428 at gmail.com Wed Sep 5 18:22:56 2012 From: kawazu428 at gmail.com (Kristian Rink) Date: Wed, 05 Sep 2012 20:22:56 +0200 Subject: [Shotwell] multi-machine setup? In-Reply-To: <50476773.5040402@bnrlabs.com> References: <50476773.5040402@bnrlabs.com> Message-ID: <50479880.8050301@gmail.com> Hi Lucas, all; and first off, thanks a bunch for your response and thoughts. Overally, well, though you didn't provide me with a real solution to my problem, at least you made me think more about what my actual use case is. This is good. :) A few thoughts, so: Am 05.09.2012 16:53, schrieb Lucas B. Cohen: > Instead, by using a single, centralized source of storage, that is > accessible via your local network (whether is uses physical cable > connections, or a Wi-Fi network setup). All your computers, fairly > independently of the different operating systems they may be running, > can access them using the same network file sharing scheme, CIFS/SMB. Well. Yes. And no. Overally, of course, a central network storage, most likely a NAS, would make handling files and eventually database easier. But, in the end, and talking Linux-only machines: Isn't that, same as an external large USB drive, just a matter of being mounted anywhere in the file system? Mount points, volume labels and symlinks to the rescue, and it should easily be doable to have files in the same logical location on all machines even while living on USB storage. But that's not actually my problem. On closer look: I see my use case not to be sharing files and data between local machines. My use case rather is syncing files and metadata between machines, and, in worst case, doing so incrementally, while some of these machines often to always operate offline. Given the netbook (vacation) or notebook+USB drive (business travel) use case: Most of these times, I try downloading and sorting images on a daily basis. In most of these situation, keeping a central storage is not an option as network connectivity either is too slow or too expensive or both. So, what I actually wanted to do is something like this: 1. Download and sort images, say, on the netbook. This would include things such as tagging, commenting and rating ("star") images. This is something I try doing day-by-day in order to somehow keep track of the vast load of images. The netbook and/or the USB drive by then would keep images of the current trip, sorted and tagged. 2. Back home, I would like to "somehow"(?) merge these images and its metadata into my existing image archive on my workstation machine. This mainly would include moving (not just copying) all the files off the netbook to the workstation into the image archive living there, plus importing the corresponding metadata to the workstations shotwell database. Assuming the current shotwell ability to monitor an image folder and automatically import new additions, this would seem fairly straightforward, but so far I fail to see a way how to transfer metadata. Is there a way of storing metadata along with the images rather than in the database? Can one shotwell instance store comments, star rating, tags, titles, comments and all these things in JPEG EXIF _and_ another shotwell installment restore these information out of the EXIF while importing these images? Ultimately, I think that this might be the most straightforward way, assuming my use case, even though I am open to any suggestions outlining better ways. ;) TIA and all the best, Kristian From fred.grollier at gmail.com Wed Sep 5 18:46:06 2012 From: fred.grollier at gmail.com (Fred Grollier) Date: Wed, 5 Sep 2012 20:46:06 +0200 Subject: [Shotwell] multi-machine setup? In-Reply-To: <50479880.8050301@gmail.com> References: <50476773.5040402@bnrlabs.com> <50479880.8050301@gmail.com> Message-ID: Hi, 2012/9/5 Kristian Rink : > Hi Lucas, all; > Assuming the current shotwell ability to monitor an image folder and > automatically import new additions, this would seem fairly straightforward, > but so far I fail to see a way how to transfer metadata. Is there a way of > storing metadata along with the images rather than in the database? Can one > shotwell instance store comments, star rating, tags, titles, comments and > all these things in JPEG EXIF _and_ another shotwell installment restore > these information out of the EXIF while importing these images? Well, yes, there's an option in the preferences dialog to "write metadata and others things to image file" (I can't open shotwell right now for the exact wording). And if your import image files tagged like this, shotwell will read this data and use it as expected. It surely works for title ratings and tags, I'm unsure for comments though. And most importantly, it won't work if you're shooting only raw files. Cheers, Fred. From durduran at yahoo.com Thu Sep 6 18:47:40 2012 From: durduran at yahoo.com (Turgut Durduran) Date: Thu, 6 Sep 2012 11:47:40 -0700 (PDT) Subject: [Shotwell] multi-machine setup? In-Reply-To: References: Message-ID: <1346957260.875.YahooMailNeo@web163004.mail.bf1.yahoo.com> ? ? ----- Original Message ----- > From: Kristian Rink > To: shotwell at lists.yorba.org > Cc: > Sent: Wednesday, September 5, 2012 4:55 AM > Subject: [Shotwell] multi-machine setup? > > Folks; > I've been playing with shotwell for quite a while so far, yet one thing > kept me from "fully" using it: Usually, in my "imaging" > workflow there are > more than one machines involved, between which I usually transfer images in > this way or the other, and between which I also want to have shotwell > information (starred / tagged images, ...) shared to make things meaningful > and not do the same work over and over again. So to ask: Is there sort of a > "best practise" setup how to deal with shotwell database and image > files if > using both on multiple computers? Would keeping both on an USB drive be a > way to go? How do you do these things? > TIA and all the best, > Kristian Hi Kristian, If the set of images will be identical/near-identical in both computers, I would just keep a copy of database file in both and an equivalent path. I have tested that method earlier this year and it works fine.? Then syncronize the set of images in both computers. In my case, I wanted something more specific (search messages from February 2012 with? "Dual Computer" in the subject line) where I keep a small subset of images in one computer ("current set that I am working on") which is let's call a "slave" and another "master" which has all the images. In that case, the problem was shotwell was spending a lot of time scanning for missing images upon starting. So Adam had sugggested that I put forward a feature request that did not see any activity :< http://redmine.yorba.org/issues/4754 Turgut From lbc at bnrlabs.com Thu Sep 6 23:00:53 2012 From: lbc at bnrlabs.com (Lucas B. Cohen) Date: Fri, 07 Sep 2012 01:00:53 +0200 Subject: [Shotwell] multi-machine setup? In-Reply-To: <50479880.8050301@gmail.com> References: <50476773.5040402@bnrlabs.com> <50479880.8050301@gmail.com> Message-ID: <50492B25.8060306@bnrlabs.com> Okay, I completely had missed the point by not understand that you wanted to use Shotwell on more than a single machine in your imaging worklow ! In that case Fred Grollier's solution looks ideal for you if it handles all the metadata you need it to do. From jnfo-c at grauman.com Sun Sep 9 05:48:46 2012 From: jnfo-c at grauman.com (Joshua Grauman) Date: Sat, 8 Sep 2012 22:48:46 -0700 (PDT) Subject: [Shotwell] Plugin Config data Message-ID: Hello all, I am wondering where the shotwell plugin config data is stored. After setting up the piwigo plugin, I changed my piwigo install on my server, and now I can't publish to piwigo from shotwell and can't find where to change the login info to piwigo in shotwell. Thanks! Josh From adam at yorba.org Mon Sep 10 17:24:05 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 10 Sep 2012 17:17:05 -0007 Subject: [Shotwell] Plugin Config data In-Reply-To: References: Message-ID: <504e2236.a3e5440a.5221.fffffd24@mx.google.com> Josh, to change the login information to Piwigo in Shotwell: 1. Select one or more photos to publish. 2. Press Publish. 3. In the publishing dialog, select Piwigo. 4. Press the Logout button. You'll now be prompted to reenter your login information. If you want to get to the configuration information directly, it's stored in GSettings in /apps/shotwell/sharing/org-yorba-shotwell-publishing-piwigo. adam On Sat, Sep 8, 2012 at 10:48 PM, Joshua Grauman wrote: Hello all, I am wondering where the shotwell plugin config data is stored. After setting up the piwigo plugin, I changed my piwigo install on my server, and now I can't publish to piwigo from shotwell and can't find where to change the login info to piwigo in shotwell. Thanks! Josh _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From lucas at yorba.org Thu Sep 13 23:25:43 2012 From: lucas at yorba.org (Lucas Beeler) Date: Thu, 13 Sep 2012 16:25:43 -0700 Subject: [Shotwell] Shotwell 0.13: Call for Translation Message-ID: Hi Shotwell Fans, The next major release of Shotwell, 0.13, is due out in the next few weeks. Shotwell 0.13 is mostly a bug-fix and stability release, but it does include several exciting new features: * The Shotwell Extras plugins now include support for publishing photos to Tumblr * Shotwell correctly handles dates before 1969 * Shotwell lets you remove sensitive information from photos before publishing them to social media sites * Shotwell regenerates thumbnails automatically, making migrating libraries between computers easier * The Picasa connector now uses OAuth authentication for enhanced security Of course, all of these new features have added new text strings to Shotwell. So if you'd like to use Shotwell 0.13 in your native language, we invite you to update the translation files for your language to take these new strings into account. We froze the addition of new strings today, and we're accepting translation submissions for the 0.13 release until Wednesday, September 19. You can submit an updated translation on our Transifex project page at http://www.transifex.net/projects/p/shotwell/. Thanks for your help. We hope you're as excited about the future of Shotwell as we are! Regards, Lucas ---------------------------------------- Lucas Beeler Shotwell Project Lead Developer Yorba Foundation From arzitek at yahoo.com Fri Sep 14 21:36:21 2012 From: arzitek at yahoo.com (Luc More) Date: Fri, 14 Sep 2012 21:36:21 +0000 (UTC) Subject: [Shotwell] how to get the UserComment of the Image Data into SW? References: <4E1F5806.6030500@gmx.de> <4E1F5FFC.2090308@yorba.org> Message-ID: Adam Dingle writes: > Today, Shotwell only supports the notion of a title for each image. As > you've correctly observed, that comes from Xmp.dc.title. We'd like to > extend Shotwell so that each image can have a description as well as a > title: > > http://trac.yorba.org/ticket/1573 Hi Adam & all. Thanks for your efforts on this great application. +1 for this request. I have used gThumb so far, and many photos in my archive have both a short title/caption and a longer notes/description. I'll admit it's a bit of a mess to check what each photo program or web service does with the EXIF and other fields but I had a nice working combination for these two fields using gThumb + Flickr Uploader. At this point I'm using Shotwell in parallel with gThumb but since SW only supports one field it tends to overwrite any note in the other fields that gThumb uses. I think this comes from SW writing the title into Caption-Abstract in addition to two other fields. My findings: 1. gThumb short title goes in both "Title" and "Headline" fields (as reported by exiftool, not sure which technical tags this exactly means). SW uses the same fields + Caption-Abstract as well. 2. gThumb long description goes in 3 fields: "User Comment", "Description" and "Caption-Abstract" 3. Flickr Uploader takes these values from at least two of the fields above and uses them to set the appropriate fields online. So I was a relatively happy camper with gThumb, but now I would really like to upgrade to SW in order to benefit from the more advanced features like fast searches, and some more advanced and non destructive global edit/retouching functions. I'm a bit stuck because of this. It would really have been nicer for me if SW did not touch the Caption-Abstract field. Is there any other field available that SW currently ignores? Luc From lucas at yorba.org Sat Sep 15 02:00:42 2012 From: lucas at yorba.org (Lucas Beeler) Date: Fri, 14 Sep 2012 19:00:42 -0700 Subject: [Shotwell] Shotwell 0.13: Call for Testing Message-ID: Hi Shotwell Fans, Shotwell needs your help! The next major release of Shotwell, 0.13, is due out in the next few weeks. Shotwell 0.13 is mostly a bug-fix and stability release, but it does include several exciting new features: * The Shotwell Extras plugins now include support for publishing photos to Tumblr * Shotwell correctly handles dates before 1969 * Shotwell lets you remove sensitive information from photos before publishing them to social media sites * Shotwell regenerates thumbnails automatically, making migrating libraries between computers easier * The Picasa connector now uses OAuth authentication for enhanced security With all these new features, we on the dev team could use your help testing Shotwell 0.13. To test the latest code, you'll need to either pull from Shotwell git master and build from source or, if you're on Ubuntu, install a Shotwell daily build from the Shotwell Daily Builds PPA. Pulling from Shotwell git master should be as easy as executing $ git clone git://yorba.org/shotwell on your system, and then building as usual with $ ./configure $ make # make install For Ubuntu users, the Shotwell daily builds PPA is located here: https://launchpad.net/~yorba/+archive/daily-builds As always, we thank you for your help! Cheers, Lucas Regards, Lucas ---------------------------------------- Lucas Beeler Shotwell Project Lead Developer Yorba Foundation From jamesmikedupont at googlemail.com Sat Sep 15 07:20:50 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Sat, 15 Sep 2012 09:20:50 +0200 Subject: [Shotwell] another bug report Message-ID: Hi there, i installed the latest version of shotwell uploading a file, i think the problem is the the shared lib being incompatible, Program received signal SIGSEGV, Segmentation fault. 0xb7e5922e in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::find(std::string const&) () from /usr/lib/libexiv2.so.10 (gdb) bt #0 0xb7e5922e in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::find(std::string const&) () from /usr/lib/libexiv2.so.10 #1 0xb7e7e7fc in ?? () from /usr/lib/libexiv2.so.10 #2 0xb7e5c3f6 in ?? () from /usr/lib/libexiv2.so.10 #3 0xb7e88584 in ?? () from /usr/lib/libexiv2.so.10 #4 0xb7e4b4ba in ?? () from /usr/lib/libexiv2.so.10 #5 0xb7e49109 in Exiv2::XmpParser::encode(std::string&, Exiv2::XmpData const&, unsigned short, unsigned int) () from /usr/lib/libexiv2.so.10 #6 0xb7dac668 in ?? () from /usr/lib/libexiv2.so.10 #7 0xb7dad3ea in Exiv2::JpegBase::writeMetadata() () from /usr/lib/libexiv2.so.10 #8 0xb7f36db8 in ?? () from /usr/lib/libgexiv2.so.1 #9 0xb7f37445 in gexiv2_metadata_save_file () from /usr/lib/libgexiv2.so.1 #10 0x081166eb in photo_metadata_write_to_file (self=0xa64b8440, file=0xa64a5dc0, error=0xbfffc76c) at /home/mdupont/experiments/photo/shotwell/src/photos/PhotoMetadata.vala:152 #11 0x0811c297 in jfif_metadata_writer_real_write_metadata (base=0x9cfedb0, metadata=0xa64b8440, error=0xbfffc818) at /home/mdupont/experiments/photo/shotwell/src/photos/JfifSupport.vala:139 #12 0x0810868e in photo_file_metadata_writer_write_metadata (self=0x9cfedb0, metadata=0xa64b8440, error=0xbfffc818) at /home/mdupont/experiments/photo/shotwell/src/photos/PhotoFileAdapter.vala:110 #13 0x082533d3 in photo_export (self=0x91401f0, dest_file=0x9d0a120, scaling=0xbfffc88c, quality=JPEG_QUALITY_HIGH, export_format=PHOTO_FILE_FORMAT_JFIF, direct_copy_unmodified=0, export_metadata=1, error=0xbfffc8b4) at /home/mdupont/experiments/photo/shotwell/src/Photo.vala:3427 #14 0x08129df5 in publishing_glue_media_source_publishable_wrapper_serialize_for_publishing ( self=0x9afd980, content_major_axis=720, strip_metadata=0, error=0xbfffc93c) at /home/mdupont/experiments/photo/shotwell/src/publishing/APIGlue.vala:54 #15 0x081288fd in spit_publishing_concrete_publishing_host_real_serialize_publishables ( base=0x9012418, content_major_axis=720, strip_metadata=0, result_target=0xbfffc9d4, result_target_destroy_notify=0xbfffc9d8) at /home/mdupont/experiments/photo/shotwell/src/publishing/PublishingPluginHost.vala:215 #16 0x080f5412 in spit_publishing_plugin_host_serialize_publishables (self=0x9012418, content_major_axis=720, strip_metadata=0, result_target=0xbfffc9d4, ---Type to continue, or q to quit---q result_target_destroy_notify=0xbQuit (gdb) info shared >From To Syms Read Shared Object Library 0xb7fde820 0xb7ff6b9f Yes (*) /lib/ld-linux.so.2 0xb7f57790 0xb7f8dfe8 Yes (*) /usr/lib/i386-linux-gnu/libgee.so.2 0xb7f369c0 0xb7f47468 Yes (*) /usr/lib/libgexiv2.so.1 0xb7d61010 0xb7e8f2c8 Yes (*) /usr/lib/libexiv2.so.10 0xb7d15f60 0xb7d26058 Yes (*) /usr/lib/i386-linux-gnu/libgstpbutils-0.10.so.0 0xb7c40fb0 0xb7cce1f8 Yes (*) /usr/lib/i386-linux-gnu/libgstreamer-0.10.so.0 0xb7c22c30 0xb7c23ce8 Yes (*) /usr/lib/i386-linux-gnu/libgmodule-2.0.so.0 0xb7c1ab00 0xb7c1d658 Yes (*) /usr/lib/i386-linux-gnu/libgudev-1.0.so.0 0xb7b9ecd0 0xb7bb1c48 Yes (*) /usr/lib/libgphoto2.so.2 0xb7b93670 0xb7b97878 Yes (*) /usr/lib/libgphoto2_port.so.0 0xb7b6a430 0xb7b84b08 Yes /lib/i386-linux-gnu/libm.so.6 0xb7b345a0 0xb7b48fac Yes (*) /usr/lib/libexif.so.12 0xb7aa9a50 0xb7ade168 Yes (*) /usr/lib/libraw.so.5 0xb79ffd30 0xb7a81c38 Yes /usr/lib/i386-linux-gnu/libsqlite3.so.0 0xb7594570 0xb787a648 Yes (*) /usr/lib/i386-linux-gnu/libgtk-3.so.0 0xb74d7100 0xb751ed08 Yes (*) /usr/lib/i386-linux-gnu/libgdk-3.so.0 0xb74bb510 0xb74c0998 Yes (*) /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 0xb749b0e0 0xb74af608 Yes (*) /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0 0xb7455600 0xb74775f8 Yes (*) /usr/lib/i386-linux-gnu/libpango-1.0.so.0 0xb738a3f0 0xb7421068 Yes (*) /usr/lib/i386-linux-gnu/libcairo.so.2 0xb724d5f0 0xb731f4c8 Yes (*) /usr/lib/i386-linux-gnu/libgio-2.0.so.0 0xb71e3300 0xb7213fc8 Yes (*) /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 0xb71d8450 0xb71d8608 Yes (*) /usr/lib/i386-linux-gnu/libgthread-2.0.so.0 0xb70f2b40 0xb71680d8 Yes (*) /lib/i386-linux-gnu/libglib-2.0.so.0 0xb70d0a60 0xb70d8c18 Yes (*) /usr/lib/i386-linux-gnu/libgomp.so.1 0xb70b7650 0xb70c3a78 Yes /lib/i386-linux-gnu/libpthread.so.0 0xb6f24f10 0xb705535c Yes /lib/i386-linux-gnu/libc.so.6 0xb6d2ab70 0xb6e6b898 Yes (*) /usr/lib/libexiv2.so.11 0xb6cdef50 0xb6cf5cf8 Yes (*) /lib/i386-linux-gnu/libgcc_s.so.1 0xb6cc8760 0xb6cd5668 Yes (*) /lib/i386-linux-gnu/libz.so.1 0xb6c9f020 0xb6cb8828 Yes (*) /lib/i386-linux-gnu/libexpat.so.1 ---Type to continue, or q to quit--- 0xb6bfdd00 0xb6c6c208 Yes (*) /usr/lib/i386-linux-gnu/libstdc++.so.6 0xb6a86960 0xb6b70f28 Yes (*) /usr/lib/i386-linux-gnu/libxml2.so.2 0xb6a628d0 0xb6a66618 Yes /lib/i386-linux-gnu/librt.so.1 0xb6a5ca60 0xb6a5da08 Yes /lib/i386-linux-gnu/libdl.so.2 0xb6a4e610 0xb6a55488 Yes (*) /lib/i386-linux-gnu/libudev.so.0 0xb6a43730 0xb6a48178 Yes (*) /usr/lib/i386-linux-gnu/libltdl.so.7 0xb69f3170 0xb6a29538 Yes (*) /usr/lib/i386-linux-gnu/libjasper.so.1 0xb69a5f10 0xb69d8128 Yes (*) /usr/lib/i386-linux-gnu/liblcms2.so.2 0xb687d1e0 0xb690b558 Yes (*) /usr/lib/i386-linux-gnu/libX11.so.6 0xb685d830 0xb6867a88 Yes (*) /usr/lib/i386-linux-gnu/libXi.so.6 0xb6856f60 0xb6859698 Yes (*) /usr/lib/i386-linux-gnu/libXfixes.so.3 0xb683c290 0xb68499d8 Yes (*) /usr/lib/i386-linux-gnu/libatk-1.0.so.0 0xb682f980 0xb6830b78 Yes (*) /usr/lib/i386-linux-gnu/libcairo-gobject.so.2 0xb6806e90 0xb6822e78 Yes (*) /usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0 0xb67d2070 0xb67ed298 Yes (*) /usr/lib/i386-linux-gnu/libfontconfig.so.1 0xb67be700 0xb67c8ca8 Yes (*) /usr/lib/i386-linux-gnu/libXext.so.6 0xb67b8770 0xb67b9158 Yes (*) /usr/lib/i386-linux-gnu/libXinerama.so.1 0xb67af100 0xb67b3c18 Yes (*) /usr/lib/i386-linux-gnu/libXrandr.so.2 0xb67a4ad0 0xb67a9e68 Yes (*) /usr/lib/i386-linux-gnu/libXcursor.so.1 0xb679f880 0xb67a02e8 Yes (*) /usr/lib/i386-linux-gnu/libXcomposite.so.1 0xb679b7c0 0xb679c148 Yes (*) /usr/lib/i386-linux-gnu/libXdamage.so.1 0xb67077d0 0xb6773388 Yes (*) /usr/lib/i386-linux-gnu/libfreetype.so.6 0xb666c070 0xb66ed168 Yes (*) /usr/lib/i386-linux-gnu/libpixman-1.so.0 0xb66417c0 0xb665e528 Yes (*) /lib/i386-linux-gnu/libpng12.so.0 0xb663a750 0xb663b148 Yes (*) /usr/lib/i386-linux-gnu/libxcb-shm.so.0 0xb66328d0 0xb66364d8 Yes (*) /usr/lib/i386-linux-gnu/libxcb-render.so.0 0xb6616ba0 0xb6626d98 Yes (*) /usr/lib/i386-linux-gnu/libxcb.so.1 0xb66052f0 0xb660b028 Yes (*) /usr/lib/i386-linux-gnu/libXrender.so.1 0xb65e9140 0xb65fa968 Yes (*) /lib/i386-linux-gnu/libselinux.so.1 0xb65cf6b0 0xb65dc578 Yes /lib/i386-linux-gnu/libresolv.so.2 0xb65c6ef0 0xb65ca538 Yes (*) /usr/lib/i386-linux-gnu/libffi.so.6 0xb658af60 0xb65b1138 Yes (*) /lib/i386-linux-gnu/libpcre.so.3 ---Type to continue, or q to quit--- 0xb6534a30 0xb656e5b8 Yes (*) /usr/lib/i386-linux-gnu/libjpeg.so.8 0xb652e9e0 0xb652f828 Yes (*) /usr/lib/i386-linux-gnu/libXau.so.6 0xb6527d00 0xb65299a8 Yes (*) /usr/lib/i386-linux-gnu/libXdmcp.so.6 0xb7fb43a0 0xb7fd0428 Yes (*) /usr/lib/gio/modules/libgvfsdbus.so 0xb6511620 0xb651c718 Yes (*) /usr/lib/gvfs/libgvfscommon.so 0xb6492d90 0xb64c2198 Yes (*) /lib/i386-linux-gnu/libdbus-1.so.3 0xb6485dc0 0xb648ac98 Yes /lib/i386-linux-gnu/libnss_compat.so.2 0xb646e160 0xb647afa8 Yes /lib/i386-linux-gnu/libnsl.so.1 0xb6460970 0xb6466f58 Yes /lib/i386-linux-gnu/libnss_nis.so.2 0xb6453a10 0xb645ab18 Yes /lib/i386-linux-gnu/libnss_files.so.2 0xb64fdf50 0xb6506ed8 Yes (*) /usr/lib/liboverlay-scrollbar3-0.2.so.0 0xb64f6650 0xb64f87f8 Yes (*) /usr/lib/gtk-3.0/modules/libcanberra-gtk-module.so 0xb64193a0 0xb641a948 Yes (*) /usr/lib/libcanberra-gtk3.so.0 0xb64e5f30 0xb64eff28 Yes (*) /usr/lib/libcanberra.so.0 0xb64db590 0xb64e0858 Yes (*) /usr/lib/i386-linux-gnu/libvorbisfile.so.3 0xb64068d0 0xb6411158 Yes (*) /usr/lib/i386-linux-gnu/libtdb.so.1 0xb63dbfb0 0xb63f1c18 Yes (*) /usr/lib/i386-linux-gnu/libvorbis.so.0 0xb63d3340 0xb63d5fe8 Yes (*) /usr/lib/i386-linux-gnu/libogg.so.0 0xb6443260 0xb644d768 Yes (*) /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so 0xb63ae400 0xb63b00d8 Yes (*) /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so 0xb641e770 0xb641ebc8 Yes (*) /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so 0xb5b44890 0xb5b6d648 Yes (*) /usr/lib/i386-linux-gnu/librsvg-2.so.2 0xb5b122c0 0xb5b33b58 Yes (*) /usr/lib/libcroco-0.6.so.3 0xb5b7b920 0xb5b7ea06 Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-transitions.so 0xb5988100 0xb59d532f Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-publishing.so 0xaa6bb080 0xab6d74b8 Yes (*) /usr/lib/libwebkitgtk-3.0.so.0 0xaa54f220 0xaa557608 Yes (*) /usr/lib/librest-0.7.so.0 0xaa4f4e50 0xaa531388 Yes (*) /usr/lib/i386-linux-gnu/libsoup-2.4.so.1 0xaa4c5600 0xaa4d9258 Yes (*) /usr/lib/i386-linux-gnu/libjson-glib-1.0.so.0 0xaa182720 0xaa432fb8 Yes (*) /usr/lib/libjavascriptcoregtk-3.0.so.0 ---Type to continue, or q to quit--- 0xb596b060 0xb5970888 Yes (*) /usr/lib/libenchant.so.1 0xb5b03f10 0xb5b08718 Yes (*) /usr/lib/i386-linux-gnu/libgailutil-3.so.0 0xaa0eb8a0 0xaa0f4018 Yes (*) /usr/lib/libgeoclue.so.0 0xaa0dc390 0xaa0e2578 Yes (*) /usr/lib/i386-linux-gnu/libgstapp-0.10.so.0 0xaa0cca80 0xaa0d3698 Yes (*) /usr/lib/i386-linux-gnu/libgstinterfaces-0.10.so.0 0xaa0aea40 0xaa0c0c38 Yes (*) /usr/lib/i386-linux-gnu/libgstvideo-0.10.so.0 0xaa053bb0 0xaa096a88 Yes (*) /usr/lib/i386-linux-gnu/libgstbase-0.10.so.0 0xaa015ef0 0xaa03cc2c Yes (*) /usr/lib/libxslt.so.1 0xa9e85680 0xa9fb8bb8 Yes (*) /usr/lib/libicui18n.so.48 0xa9d02d30 0xa9dcd848 Yes (*) /usr/lib/libicuuc.so.48 0xa9c829b0 0xa9cbf3e8 Yes (*) /usr/lib/i386-linux-gnu/libXt.so.6 0xb59643c0 0xb5965718 Yes (*) /usr/lib/i386-linux-gnu/libsoup-gnome-2.4.so.1 0xa9c580f0 0xa9c6c1a8 Yes (*) /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 0xa9bc8ab0 0xa9c2c708 Yes (*) /usr/lib/i386-linux-gnu/liborc-0.4.so.0 0xa8a50370 0xa8a50468 Yes (*) /usr/lib/libicudata.so.48 0xa8a48430 0xa8a4cb48 Yes (*) /usr/lib/i386-linux-gnu/libSM.so.6 0xa8a30010 0xa8a3ed38 Yes (*) /usr/lib/i386-linux-gnu/libICE.so.6 0xa8a0f6f0 0xa8a22288 Yes (*) /usr/lib/i386-linux-gnu/libgnome-keyring.so.0 0xa8a04fb0 0xa8a06c28 Yes (*) /lib/i386-linux-gnu/libuuid.so.1 0xa89837d0 0xa89dc558 Yes (*) /lib/i386-linux-gnu/libgcrypt.so.11 0xa897a630 0xa897abf8 Yes (*) /lib/i386-linux-gnu/libgpg-error.so.0 0xabae94d0 0xabafbe31 Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-data-imports.so 0xa894d550 0xa8968b3a Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-publishing-extras.so 0xa88f4dd0 0xa88f8368 Yes (*) /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so 0xa8082a90 0xa8082ff8 Yes (*) /usr/lib/i386-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so 0xa807d8b0 0xa807f458 Yes (*) /usr/lib/gtk-3.0/3.0.0/menuproxies/libappmenu.so 0xa8039930 0xa8042058 Yes (*) /usr/lib/libdbusmenu-gtk3.so.4 0xa801d320 0xa802c5a8 Yes (*) /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4 0xa8069b60 0xa8076578 Yes (*) /usr/lib/gio/modules/libgioremote-volume-monitor.so 0xa8061060 0xa8062e98 Yes (*) /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so ---Type to continue, or q to quit--- 0xa6312e00 0xa63200c8 Yes (*) /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so 0xa804fd30 0xa8059258 Yes (*) /usr/lib/i386-linux-gnu/libp11-kit.so.0 0xa4fef7e0 0xa507fbd8 Yes (*) /usr/lib/i386-linux-gnu/libgnutls.so.26 0xa80080e0 0xa8014038 Yes (*) /usr/lib/i386-linux-gnu/libtasn1.so.3 0xa6506a10 0xa6511468 Yes (*) /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so (*): Shared library is missing debugging information. -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From jamesmikedupont at googlemail.com Sat Sep 15 09:06:28 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Sat, 15 Sep 2012 11:06:28 +0200 Subject: [Shotwell] server working Message-ID: I have a facebook api server running that shotwell can talk to https://github.com/h4ck3rm1k3/photo-librarian-server next is picasa. mike -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From arzitek at yahoo.com Sun Sep 16 00:49:16 2012 From: arzitek at yahoo.com (Luc More) Date: Sat, 15 Sep 2012 17:49:16 -0700 (PDT) Subject: [Shotwell] Build error 0.13 Message-ID: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> Hi! I built it on Ubuntu 11.10 (had to add the vala team ppa to get valac-0.18, got the other dependencies from the distro).? Got a compile error as follows: Compiling Vala code... src/library/LibraryWindow.vala:502.30-502.32: error: Argument 1: Cannot convert from `Page?' to `CheckerboardPage' ??????????? init_view_filter(tmp); ???????????????????????????? ^^^ Compilation failed: 1 error(s), 0 warning(s) make: *** [src/.stamp] Erreur 1 Any advice? TIA Luc From thomas at xyz.pp.se Sun Sep 16 07:20:45 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 16 Sep 2012 09:20:45 +0200 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: References: Message-ID: On Sat, Sep 15, 2012 at 4:00 AM, Lucas Beeler wrote: > With all these new features, we on the dev team could use your help > testing Shotwell 0.13. To test the latest code, you'll need to either > pull from Shotwell git master and build from source or, if you're on > Ubuntu, install a Shotwell daily build from the Shotwell Daily Builds > PPA. > Tried to but could not. $ sudo aptitude dist-upgrade The following packages will be upgraded: shotwell 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/8 081 kB of archives. After unpacking 1 383 kB will be freed. Do you want to continue? [Y/n/?] y dpkg: dependency problems prevent configuration of shotwell: shotwell depends on libgexiv2-0; however: Package libgexiv2-0 is not installed. dpkg: error processing shotwell (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already Errors were encountered while processing: shotwell E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: dpkg: dependency problems prevent configuration of shotwell: shotwell depends on libgexiv2-0; however: Package libgexiv2-0 is not installed. dpkg: error processing shotwell (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: shotwell This is on Ubuntu 12.04. I have a package called libgexiv2-1 but 2-0 isn't available. Rgds//Thomas From adam at yorba.org Sun Sep 16 19:06:03 2012 From: adam at yorba.org (Adam Dingle) Date: Sun, 16 Sep 2012 12:06:03 -0700 Subject: [Shotwell] Build error 0.13 In-Reply-To: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> References: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> Message-ID: Luc, The build was broken - sorry about that. I've just committed a fix, so you might want to try again. adam On Sat, Sep 15, 2012 at 5:49 PM, Luc More wrote: > Hi! > > I built it on Ubuntu 11.10 (had to add the vala team ppa to get > valac-0.18, got the other dependencies from the distro). Got a compile > error as follows: > > Compiling Vala code... > src/library/LibraryWindow.vala:502.30-502.32: error: Argument 1: Cannot > convert from `Page?' to `CheckerboardPage' > init_view_filter(tmp); > ^^^ > Compilation failed: 1 error(s), 0 warning(s) > make: *** [src/.stamp] Erreur 1 > > Any advice? > > TIA > > Luc > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From arzitek at yahoo.com Sun Sep 16 23:03:22 2012 From: arzitek at yahoo.com (Luc More) Date: Sun, 16 Sep 2012 16:03:22 -0700 (PDT) Subject: [Shotwell] Build error 0.13 In-Reply-To: References: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> Message-ID: <1347836602.41295.YahooMailNeo@web122306.mail.ne1.yahoo.com> Hi Adam, The new build worked fine, thanks for the quick reaction. Then I patched the following because I would like shotwell to leave the Caption tag alone when setting the Picure Title (I use Caption with other programs for a long description on some photos).? Eventually I'd like shotwell to handle both fields but that would be a much heavier change.? Initial testing shows that it works well in my workflow (e.g. Flickr Uploader can set both fields on my uploads -- not if I use shotwell's plugin though). Thanks for this new shotwell.? With this patch I'll be able to test much more extensively by using shotwell as my main photo management application, now that I'm confident it won't overwrite this Caption field. So far I've only done limited testing but had no problems. --- shotwell/src/photos/PhotoMetadata.vala??? 2012-09-17 00:14:09.933142226 +0200 +++ shotwell-0.13-patched//src/photos/PhotoMetadata.vala??? 2012-09-15 22:25:22.126927218 +0200 @@ -800,7 +800,7 @@ ???? private const string IPHOTO_TITLE_TAG = "Iptc.Application2.ObjectName"; ???? ???? private static string[] STANDARD_TITLE_TAGS = { -??????? "Iptc.Application2.Caption", +//??????? "Iptc.Application2.Caption", ???????? "Xmp.dc.title", ???????? "Iptc.Application2.Headline", ???????? "Xmp.photoshop.Headline" ________________________________ De?: Adam Dingle ??: Luc More Cc?: "shotwell at lists.yorba.org" Envoy? le : Dimanche 16 septembre 2012 21h06 Objet?: Re: [Shotwell] Build error 0.13 Luc, The build was broken - sorry about that. ?I've just committed a fix, so you might want to try again. adam From jamesmikedupont at googlemail.com Mon Sep 17 09:06:30 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Mon, 17 Sep 2012 11:06:30 +0200 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response Message-ID: Package: shotwell Version: 0.12.3-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? testing the plugin with a invalid piwigo server api. * What exactly did you do (or not do) that was effective (or ineffective)? does not check the response of the server, segfaults. Entity: line 1: parser error : Start tag expected, '<' not found OK ^ Entity: line 1: parser error : Start tag expected, '<' not found OK ^ ^C [1]+ Segmentation fault (core dumped) shotwell (wd: ~) * What was the outcome of this action? segfault/hanging program. * What outcome did you expect instead? an error that the response from the server is invalid. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-17-generic-pae Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages shotwell depends on: ii dbus-x11 1.6.2-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-35 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libexif12 0.6.20-3 ii libexiv2-12 0.23-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-2 ii libgexiv2-1 0.4.1-3 ii libglib2.0-0 2.33.12+really2.32.3-1 ii libgomp1 4.7.1-9 ii libgphoto2-2 2.4.14-2 ii libgphoto2-port0 2.4.14-2 ii libgstreamer-plugins-base0.10-0 0.10.36-1 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-3 ii libgudev-1.0-0 175-7 ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 ii liblcms2-2 2.2+git20110628-2.2 ii libpango1.0-0 1.30.0-1 ii libraw5 0.14.6-2 ii librest-0.7-0 0.7.12-3 ii librsvg2-common 2.36.1-1 ii libsoup2.4-1 2.38.1-2 ii libsqlite3-0 3.7.13-1 ii libstdc++6 4.7.1-9 ii libunique-3.0-0 3.0.2-1 ii libwebkitgtk-3.0-0 1.8.1-3.3 ii libx11-6 2:1.5.0-1 ii libxml2 2.8.0+dfsg1-5 ii shotwell-common 0.12.3-2 shotwell recommends no packages. shotwell suggests no packages. -- no debconf information -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From brunogirin at gmail.com Mon Sep 17 09:56:24 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Mon, 17 Sep 2012 10:56:24 +0100 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response In-Reply-To: References: Message-ID: <5056F3C8.7050003@gmail.com> Hi Mike, I thought I had tested that particular scenario. Obviously not. Can you include the URL that you used so that I can debug? Thanks, Bruno On 17/09/12 10:06, Mike Dupont wrote: > Package: shotwell > Version: 0.12.3-2 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > > * What led up to the situation? > testing the plugin with a invalid piwigo server api. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > does not check the response of the server, segfaults. > > Entity: line 1: parser error : Start tag expected, '<' not found > OK > ^ > Entity: line 1: parser error : Start tag expected, '<' not found > OK > ^ > ^C > [1]+ Segmentation fault (core dumped) shotwell (wd: ~) > > > * What was the outcome of this action? > segfault/hanging program. > > * What outcome did you expect instead? > an error that the response from the server is invalid. > > *** End of the template - remove these lines *** > > > -- System Information: > Debian Release: wheezy/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > > Kernel: Linux 3.0.0-17-generic-pae > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) > Shell: /bin/sh linked to /bin/dash > > Versions of packages shotwell depends on: > ii dbus-x11 1.6.2-2 > ii libatk1.0-0 2.4.0-2 > ii libc6 2.13-35 > ii libcairo-gobject2 1.12.2-2 > ii libcairo2 1.12.2-2 > ii libexif12 0.6.20-3 > ii libexiv2-12 0.23-1 > ii libgdk-pixbuf2.0-0 2.26.1-1 > ii libgee2 0.6.4-2 > ii libgexiv2-1 0.4.1-3 > ii libglib2.0-0 2.33.12+really2.32.3-1 > ii libgomp1 4.7.1-9 > ii libgphoto2-2 2.4.14-2 > ii libgphoto2-port0 2.4.14-2 > ii libgstreamer-plugins-base0.10-0 0.10.36-1 > ii libgstreamer0.10-0 0.10.36-1 > ii libgtk-3-0 3.4.2-3 > ii libgudev-1.0-0 175-7 > ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 > ii liblcms2-2 2.2+git20110628-2.2 > ii libpango1.0-0 1.30.0-1 > ii libraw5 0.14.6-2 > ii librest-0.7-0 0.7.12-3 > ii librsvg2-common 2.36.1-1 > ii libsoup2.4-1 2.38.1-2 > ii libsqlite3-0 3.7.13-1 > ii libstdc++6 4.7.1-9 > ii libunique-3.0-0 3.0.2-1 > ii libwebkitgtk-3.0-0 1.8.1-3.3 > ii libx11-6 2:1.5.0-1 > ii libxml2 2.8.0+dfsg1-5 > ii shotwell-common 0.12.3-2 > > shotwell recommends no packages. > > shotwell suggests no packages. > > -- no debconf information > > From jamesmikedupont at googlemail.com Mon Sep 17 12:50:08 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Mon, 17 Sep 2012 14:50:08 +0200 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response In-Reply-To: <5056F3C8.7050003@gmail.com> References: <5056F3C8.7050003@gmail.com> Message-ID: HI, Shotwell works, it works great, just not with invalid data. normally this will never happen, but it happens with you are implementing a new server that looks like piwigo, that might happen once every x years, but shotwell should not crash like that. I returned "OK" from the server not any xml. there is no error checking, lots of shotwell plugins just crash on invalid input. here, I have setup a simple rule in dancer to reproduce the problem : post '/piwigocrash/ws.php' => sub { return "crash"; }; https://github.com/h4ck3rm1k3/photo-librarian-server/commit/fbc6e93ff4fa3d87c671e969b7b3fb6d04955a6b On Mon, Sep 17, 2012 at 11:56 AM, Bruno Girin wrote: > Hi Mike, > > I thought I had tested that particular scenario. Obviously not. Can you > include the URL that you used so that I can debug? > > Thanks, > > Bruno > > On 17/09/12 10:06, Mike Dupont wrote: >> Package: shotwell >> Version: 0.12.3-2 >> Severity: normal >> >> Dear Maintainer, >> *** Please consider answering these questions, where appropriate *** >> >> * What led up to the situation? >> testing the plugin with a invalid piwigo server api. >> >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> does not check the response of the server, segfaults. >> >> Entity: line 1: parser error : Start tag expected, '<' not found >> OK >> ^ >> Entity: line 1: parser error : Start tag expected, '<' not found >> OK >> ^ >> ^C >> [1]+ Segmentation fault (core dumped) shotwell (wd: ~) >> >> >> * What was the outcome of this action? >> segfault/hanging program. >> >> * What outcome did you expect instead? >> an error that the response from the server is invalid. >> >> *** End of the template - remove these lines *** >> >> >> -- System Information: >> Debian Release: wheezy/sid >> APT prefers unstable >> APT policy: (500, 'unstable') >> Architecture: i386 (i686) >> >> Kernel: Linux 3.0.0-17-generic-pae >> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) >> Shell: /bin/sh linked to /bin/dash >> >> Versions of packages shotwell depends on: >> ii dbus-x11 1.6.2-2 >> ii libatk1.0-0 2.4.0-2 >> ii libc6 2.13-35 >> ii libcairo-gobject2 1.12.2-2 >> ii libcairo2 1.12.2-2 >> ii libexif12 0.6.20-3 >> ii libexiv2-12 0.23-1 >> ii libgdk-pixbuf2.0-0 2.26.1-1 >> ii libgee2 0.6.4-2 >> ii libgexiv2-1 0.4.1-3 >> ii libglib2.0-0 2.33.12+really2.32.3-1 >> ii libgomp1 4.7.1-9 >> ii libgphoto2-2 2.4.14-2 >> ii libgphoto2-port0 2.4.14-2 >> ii libgstreamer-plugins-base0.10-0 0.10.36-1 >> ii libgstreamer0.10-0 0.10.36-1 >> ii libgtk-3-0 3.4.2-3 >> ii libgudev-1.0-0 175-7 >> ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 >> ii liblcms2-2 2.2+git20110628-2.2 >> ii libpango1.0-0 1.30.0-1 >> ii libraw5 0.14.6-2 >> ii librest-0.7-0 0.7.12-3 >> ii librsvg2-common 2.36.1-1 >> ii libsoup2.4-1 2.38.1-2 >> ii libsqlite3-0 3.7.13-1 >> ii libstdc++6 4.7.1-9 >> ii libunique-3.0-0 3.0.2-1 >> ii libwebkitgtk-3.0-0 1.8.1-3.3 >> ii libx11-6 2:1.5.0-1 >> ii libxml2 2.8.0+dfsg1-5 >> ii shotwell-common 0.12.3-2 >> >> shotwell recommends no packages. >> >> shotwell suggests no packages. >> >> -- no debconf information >> >> > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From brunogirin at gmail.com Mon Sep 17 13:42:14 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Mon, 17 Sep 2012 14:42:14 +0100 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response In-Reply-To: References: <5056F3C8.7050003@gmail.com> Message-ID: <505728B6.7050109@gmail.com> Mike, We all agree that Shotwell should not crash like that. Thanks for reporting the issues. I'll have a look when I can. Cheers, Bruno On 17/09/12 13:50, Mike Dupont wrote: > HI, > Shotwell works, it works great, > just not with invalid data. normally this will never happen, but it > happens with you are implementing a new server that looks like piwigo, > that might happen once every x years, but shotwell should not crash > like that. > > I returned "OK" from the server not any xml. > there is no error checking, > lots of shotwell plugins just crash on invalid input. > > here, I have setup a simple rule in dancer to reproduce the problem : > > post '/piwigocrash/ws.php' => sub { > return "crash"; > }; > > https://github.com/h4ck3rm1k3/photo-librarian-server/commit/fbc6e93ff4fa3d87c671e969b7b3fb6d04955a6b > > On Mon, Sep 17, 2012 at 11:56 AM, Bruno Girin wrote: >> Hi Mike, >> >> I thought I had tested that particular scenario. Obviously not. Can you >> include the URL that you used so that I can debug? >> >> Thanks, >> >> Bruno >> >> On 17/09/12 10:06, Mike Dupont wrote: >>> Package: shotwell >>> Version: 0.12.3-2 >>> Severity: normal >>> >>> Dear Maintainer, >>> *** Please consider answering these questions, where appropriate *** >>> >>> * What led up to the situation? >>> testing the plugin with a invalid piwigo server api. >>> >>> * What exactly did you do (or not do) that was effective (or >>> ineffective)? >>> does not check the response of the server, segfaults. >>> >>> Entity: line 1: parser error : Start tag expected, '<' not found >>> OK >>> ^ >>> Entity: line 1: parser error : Start tag expected, '<' not found >>> OK >>> ^ >>> ^C >>> [1]+ Segmentation fault (core dumped) shotwell (wd: ~) >>> >>> >>> * What was the outcome of this action? >>> segfault/hanging program. >>> >>> * What outcome did you expect instead? >>> an error that the response from the server is invalid. >>> >>> *** End of the template - remove these lines *** >>> >>> >>> -- System Information: >>> Debian Release: wheezy/sid >>> APT prefers unstable >>> APT policy: (500, 'unstable') >>> Architecture: i386 (i686) >>> >>> Kernel: Linux 3.0.0-17-generic-pae >>> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) >>> Shell: /bin/sh linked to /bin/dash >>> >>> Versions of packages shotwell depends on: >>> ii dbus-x11 1.6.2-2 >>> ii libatk1.0-0 2.4.0-2 >>> ii libc6 2.13-35 >>> ii libcairo-gobject2 1.12.2-2 >>> ii libcairo2 1.12.2-2 >>> ii libexif12 0.6.20-3 >>> ii libexiv2-12 0.23-1 >>> ii libgdk-pixbuf2.0-0 2.26.1-1 >>> ii libgee2 0.6.4-2 >>> ii libgexiv2-1 0.4.1-3 >>> ii libglib2.0-0 2.33.12+really2.32.3-1 >>> ii libgomp1 4.7.1-9 >>> ii libgphoto2-2 2.4.14-2 >>> ii libgphoto2-port0 2.4.14-2 >>> ii libgstreamer-plugins-base0.10-0 0.10.36-1 >>> ii libgstreamer0.10-0 0.10.36-1 >>> ii libgtk-3-0 3.4.2-3 >>> ii libgudev-1.0-0 175-7 >>> ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 >>> ii liblcms2-2 2.2+git20110628-2.2 >>> ii libpango1.0-0 1.30.0-1 >>> ii libraw5 0.14.6-2 >>> ii librest-0.7-0 0.7.12-3 >>> ii librsvg2-common 2.36.1-1 >>> ii libsoup2.4-1 2.38.1-2 >>> ii libsqlite3-0 3.7.13-1 >>> ii libstdc++6 4.7.1-9 >>> ii libunique-3.0-0 3.0.2-1 >>> ii libwebkitgtk-3.0-0 1.8.1-3.3 >>> ii libx11-6 2:1.5.0-1 >>> ii libxml2 2.8.0+dfsg1-5 >>> ii shotwell-common 0.12.3-2 >>> >>> shotwell recommends no packages. >>> >>> shotwell suggests no packages. >>> >>> -- no debconf information >>> >>> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > From jamesmikedupont at googlemail.com Mon Sep 17 13:50:23 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Mon, 17 Sep 2012 15:50:23 +0200 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response In-Reply-To: <505728B6.7050109@gmail.com> References: <5056F3C8.7050003@gmail.com> <505728B6.7050109@gmail.com> Message-ID: Ok, well then I have more crashes in the pipeline, please approve my redmine account and I will report them directly, I can also fix them when i have time, i have a branch here https://github.com/h4ck3rm1k3/shotwell On Mon, Sep 17, 2012 at 3:42 PM, Bruno Girin wrote: > Mike, > > We all agree that Shotwell should not crash like that. Thanks for > reporting the issues. I'll have a look when I can. > > Cheers, > > Bruno > > On 17/09/12 13:50, Mike Dupont wrote: >> HI, >> Shotwell works, it works great, >> just not with invalid data. normally this will never happen, but it >> happens with you are implementing a new server that looks like piwigo, >> that might happen once every x years, but shotwell should not crash >> like that. >> >> I returned "OK" from the server not any xml. >> there is no error checking, >> lots of shotwell plugins just crash on invalid input. >> >> here, I have setup a simple rule in dancer to reproduce the problem : >> >> post '/piwigocrash/ws.php' => sub { >> return "crash"; >> }; >> >> https://github.com/h4ck3rm1k3/photo-librarian-server/commit/fbc6e93ff4fa3d87c671e969b7b3fb6d04955a6b >> >> On Mon, Sep 17, 2012 at 11:56 AM, Bruno Girin wrote: >>> Hi Mike, >>> >>> I thought I had tested that particular scenario. Obviously not. Can you >>> include the URL that you used so that I can debug? >>> >>> Thanks, >>> >>> Bruno >>> >>> On 17/09/12 10:06, Mike Dupont wrote: >>>> Package: shotwell >>>> Version: 0.12.3-2 >>>> Severity: normal >>>> >>>> Dear Maintainer, >>>> *** Please consider answering these questions, where appropriate *** >>>> >>>> * What led up to the situation? >>>> testing the plugin with a invalid piwigo server api. >>>> >>>> * What exactly did you do (or not do) that was effective (or >>>> ineffective)? >>>> does not check the response of the server, segfaults. >>>> >>>> Entity: line 1: parser error : Start tag expected, '<' not found >>>> OK >>>> ^ >>>> Entity: line 1: parser error : Start tag expected, '<' not found >>>> OK >>>> ^ >>>> ^C >>>> [1]+ Segmentation fault (core dumped) shotwell (wd: ~) >>>> >>>> >>>> * What was the outcome of this action? >>>> segfault/hanging program. >>>> >>>> * What outcome did you expect instead? >>>> an error that the response from the server is invalid. >>>> >>>> *** End of the template - remove these lines *** >>>> >>>> >>>> -- System Information: >>>> Debian Release: wheezy/sid >>>> APT prefers unstable >>>> APT policy: (500, 'unstable') >>>> Architecture: i386 (i686) >>>> >>>> Kernel: Linux 3.0.0-17-generic-pae >>>> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) >>>> Shell: /bin/sh linked to /bin/dash >>>> >>>> Versions of packages shotwell depends on: >>>> ii dbus-x11 1.6.2-2 >>>> ii libatk1.0-0 2.4.0-2 >>>> ii libc6 2.13-35 >>>> ii libcairo-gobject2 1.12.2-2 >>>> ii libcairo2 1.12.2-2 >>>> ii libexif12 0.6.20-3 >>>> ii libexiv2-12 0.23-1 >>>> ii libgdk-pixbuf2.0-0 2.26.1-1 >>>> ii libgee2 0.6.4-2 >>>> ii libgexiv2-1 0.4.1-3 >>>> ii libglib2.0-0 2.33.12+really2.32.3-1 >>>> ii libgomp1 4.7.1-9 >>>> ii libgphoto2-2 2.4.14-2 >>>> ii libgphoto2-port0 2.4.14-2 >>>> ii libgstreamer-plugins-base0.10-0 0.10.36-1 >>>> ii libgstreamer0.10-0 0.10.36-1 >>>> ii libgtk-3-0 3.4.2-3 >>>> ii libgudev-1.0-0 175-7 >>>> ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 >>>> ii liblcms2-2 2.2+git20110628-2.2 >>>> ii libpango1.0-0 1.30.0-1 >>>> ii libraw5 0.14.6-2 >>>> ii librest-0.7-0 0.7.12-3 >>>> ii librsvg2-common 2.36.1-1 >>>> ii libsoup2.4-1 2.38.1-2 >>>> ii libsqlite3-0 3.7.13-1 >>>> ii libstdc++6 4.7.1-9 >>>> ii libunique-3.0-0 3.0.2-1 >>>> ii libwebkitgtk-3.0-0 1.8.1-3.3 >>>> ii libx11-6 2:1.5.0-1 >>>> ii libxml2 2.8.0+dfsg1-5 >>>> ii shotwell-common 0.12.3-2 >>>> >>>> shotwell recommends no packages. >>>> >>>> shotwell suggests no packages. >>>> >>>> -- no debconf information >>>> >>>> >>> _______________________________________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> > -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From joseph.bylund at gmail.com Mon Sep 17 14:02:04 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Mon, 17 Sep 2012 10:02:04 -0400 Subject: [Shotwell] enhance->revert hides exif info In-Reply-To: References: <5017E7D8.4080309@gmail.com> Message-ID: <50572D5C.5080702@gmail.com> I've just tested this with the current 12.90+trunk build and I'm still seeing the same behavior (viewing a nef file and then returning to library view causes the exif info to disappear). Is this related to there being no exif info on upload? Is there an issue open for this, I didn't find it searching, but I wasn't sure which terms to use. -Joe On 08/08/2012 05:58 PM, Lucas Beeler wrote: > Hi Joseph, > > The NEF file here is the problem. This is a known issue with RAW file > handling in Shotwell that we hope to fix in the next release. > > Cheers, > Lucas From brunogirin at gmail.com Mon Sep 17 14:28:35 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Mon, 17 Sep 2012 15:28:35 +0100 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response In-Reply-To: References: <5056F3C8.7050003@gmail.com> <505728B6.7050109@gmail.com> Message-ID: <50573393.8080109@gmail.com> Mike, I do not have the authority to approve your redmine account. However, if you do have the time to work on those defects and you are happy to do so, you can attach patches to the Ubuntu bugs you've opened in Launchpad. Create them using git format-patch. Someone from Yorba will then be able to pick them up and review them before committing them to trunk. Bruno On 17/09/12 14:50, Mike Dupont wrote: > Ok, well then I have more crashes in the pipeline, > please approve my redmine account and I will report them directly, I > can also fix them when i have time, i have a branch here > https://github.com/h4ck3rm1k3/shotwell > > On Mon, Sep 17, 2012 at 3:42 PM, Bruno Girin wrote: >> Mike, >> >> We all agree that Shotwell should not crash like that. Thanks for >> reporting the issues. I'll have a look when I can. >> >> Cheers, >> >> Bruno >> >> On 17/09/12 13:50, Mike Dupont wrote: >>> HI, >>> Shotwell works, it works great, >>> just not with invalid data. normally this will never happen, but it >>> happens with you are implementing a new server that looks like piwigo, >>> that might happen once every x years, but shotwell should not crash >>> like that. >>> >>> I returned "OK" from the server not any xml. >>> there is no error checking, >>> lots of shotwell plugins just crash on invalid input. >>> >>> here, I have setup a simple rule in dancer to reproduce the problem : >>> >>> post '/piwigocrash/ws.php' => sub { >>> return "crash"; >>> }; >>> >>> https://github.com/h4ck3rm1k3/photo-librarian-server/commit/fbc6e93ff4fa3d87c671e969b7b3fb6d04955a6b >>> >>> On Mon, Sep 17, 2012 at 11:56 AM, Bruno Girin wrote: >>>> Hi Mike, >>>> >>>> I thought I had tested that particular scenario. Obviously not. Can you >>>> include the URL that you used so that I can debug? >>>> >>>> Thanks, >>>> >>>> Bruno >>>> >>>> On 17/09/12 10:06, Mike Dupont wrote: >>>>> Package: shotwell >>>>> Version: 0.12.3-2 >>>>> Severity: normal >>>>> >>>>> Dear Maintainer, >>>>> *** Please consider answering these questions, where appropriate *** >>>>> >>>>> * What led up to the situation? >>>>> testing the plugin with a invalid piwigo server api. >>>>> >>>>> * What exactly did you do (or not do) that was effective (or >>>>> ineffective)? >>>>> does not check the response of the server, segfaults. >>>>> >>>>> Entity: line 1: parser error : Start tag expected, '<' not found >>>>> OK >>>>> ^ >>>>> Entity: line 1: parser error : Start tag expected, '<' not found >>>>> OK >>>>> ^ >>>>> ^C >>>>> [1]+ Segmentation fault (core dumped) shotwell (wd: ~) >>>>> >>>>> >>>>> * What was the outcome of this action? >>>>> segfault/hanging program. >>>>> >>>>> * What outcome did you expect instead? >>>>> an error that the response from the server is invalid. >>>>> >>>>> *** End of the template - remove these lines *** >>>>> >>>>> >>>>> -- System Information: >>>>> Debian Release: wheezy/sid >>>>> APT prefers unstable >>>>> APT policy: (500, 'unstable') >>>>> Architecture: i386 (i686) >>>>> >>>>> Kernel: Linux 3.0.0-17-generic-pae >>>>> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) >>>>> Shell: /bin/sh linked to /bin/dash >>>>> >>>>> Versions of packages shotwell depends on: >>>>> ii dbus-x11 1.6.2-2 >>>>> ii libatk1.0-0 2.4.0-2 >>>>> ii libc6 2.13-35 >>>>> ii libcairo-gobject2 1.12.2-2 >>>>> ii libcairo2 1.12.2-2 >>>>> ii libexif12 0.6.20-3 >>>>> ii libexiv2-12 0.23-1 >>>>> ii libgdk-pixbuf2.0-0 2.26.1-1 >>>>> ii libgee2 0.6.4-2 >>>>> ii libgexiv2-1 0.4.1-3 >>>>> ii libglib2.0-0 2.33.12+really2.32.3-1 >>>>> ii libgomp1 4.7.1-9 >>>>> ii libgphoto2-2 2.4.14-2 >>>>> ii libgphoto2-port0 2.4.14-2 >>>>> ii libgstreamer-plugins-base0.10-0 0.10.36-1 >>>>> ii libgstreamer0.10-0 0.10.36-1 >>>>> ii libgtk-3-0 3.4.2-3 >>>>> ii libgudev-1.0-0 175-7 >>>>> ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 >>>>> ii liblcms2-2 2.2+git20110628-2.2 >>>>> ii libpango1.0-0 1.30.0-1 >>>>> ii libraw5 0.14.6-2 >>>>> ii librest-0.7-0 0.7.12-3 >>>>> ii librsvg2-common 2.36.1-1 >>>>> ii libsoup2.4-1 2.38.1-2 >>>>> ii libsqlite3-0 3.7.13-1 >>>>> ii libstdc++6 4.7.1-9 >>>>> ii libunique-3.0-0 3.0.2-1 >>>>> ii libwebkitgtk-3.0-0 1.8.1-3.3 >>>>> ii libx11-6 2:1.5.0-1 >>>>> ii libxml2 2.8.0+dfsg1-5 >>>>> ii shotwell-common 0.12.3-2 >>>>> >>>>> shotwell recommends no packages. >>>>> >>>>> shotwell suggests no packages. >>>>> >>>>> -- no debconf information >>>>> >>>>> >>>> _______________________________________________ >>>> Shotwell mailing list >>>> Shotwell at lists.yorba.org >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> > > From jamesmikedupont at googlemail.com Mon Sep 17 14:41:20 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Mon, 17 Sep 2012 16:41:20 +0200 Subject: [Shotwell] shotwell: Segfault, on invalid piwigo response In-Reply-To: <50573393.8080109@gmail.com> References: <5056F3C8.7050003@gmail.com> <505728B6.7050109@gmail.com> <50573393.8080109@gmail.com> Message-ID: OK, well thats fine, I have other things to do right now, but I will put them on the todo list when i am bored thanks mike On Mon, Sep 17, 2012 at 4:28 PM, Bruno Girin wrote: > Mike, > > I do not have the authority to approve your redmine account. However, if > you do have the time to work on those defects and you are happy to do > so, you can attach patches to the Ubuntu bugs you've opened in > Launchpad. Create them using git format-patch. Someone from Yorba will > then be able to pick them up and review them before committing them to > trunk. > > Bruno > > On 17/09/12 14:50, Mike Dupont wrote: >> Ok, well then I have more crashes in the pipeline, >> please approve my redmine account and I will report them directly, I >> can also fix them when i have time, i have a branch here >> https://github.com/h4ck3rm1k3/shotwell >> >> On Mon, Sep 17, 2012 at 3:42 PM, Bruno Girin wrote: >>> Mike, >>> >>> We all agree that Shotwell should not crash like that. Thanks for >>> reporting the issues. I'll have a look when I can. >>> >>> Cheers, >>> >>> Bruno >>> >>> On 17/09/12 13:50, Mike Dupont wrote: >>>> HI, >>>> Shotwell works, it works great, >>>> just not with invalid data. normally this will never happen, but it >>>> happens with you are implementing a new server that looks like piwigo, >>>> that might happen once every x years, but shotwell should not crash >>>> like that. >>>> >>>> I returned "OK" from the server not any xml. >>>> there is no error checking, >>>> lots of shotwell plugins just crash on invalid input. >>>> >>>> here, I have setup a simple rule in dancer to reproduce the problem : >>>> >>>> post '/piwigocrash/ws.php' => sub { >>>> return "crash"; >>>> }; >>>> >>>> https://github.com/h4ck3rm1k3/photo-librarian-server/commit/fbc6e93ff4fa3d87c671e969b7b3fb6d04955a6b >>>> >>>> On Mon, Sep 17, 2012 at 11:56 AM, Bruno Girin wrote: >>>>> Hi Mike, >>>>> >>>>> I thought I had tested that particular scenario. Obviously not. Can you >>>>> include the URL that you used so that I can debug? >>>>> >>>>> Thanks, >>>>> >>>>> Bruno >>>>> >>>>> On 17/09/12 10:06, Mike Dupont wrote: >>>>>> Package: shotwell >>>>>> Version: 0.12.3-2 >>>>>> Severity: normal >>>>>> >>>>>> Dear Maintainer, >>>>>> *** Please consider answering these questions, where appropriate *** >>>>>> >>>>>> * What led up to the situation? >>>>>> testing the plugin with a invalid piwigo server api. >>>>>> >>>>>> * What exactly did you do (or not do) that was effective (or >>>>>> ineffective)? >>>>>> does not check the response of the server, segfaults. >>>>>> >>>>>> Entity: line 1: parser error : Start tag expected, '<' not found >>>>>> OK >>>>>> ^ >>>>>> Entity: line 1: parser error : Start tag expected, '<' not found >>>>>> OK >>>>>> ^ >>>>>> ^C >>>>>> [1]+ Segmentation fault (core dumped) shotwell (wd: ~) >>>>>> >>>>>> >>>>>> * What was the outcome of this action? >>>>>> segfault/hanging program. >>>>>> >>>>>> * What outcome did you expect instead? >>>>>> an error that the response from the server is invalid. >>>>>> >>>>>> *** End of the template - remove these lines *** >>>>>> >>>>>> >>>>>> -- System Information: >>>>>> Debian Release: wheezy/sid >>>>>> APT prefers unstable >>>>>> APT policy: (500, 'unstable') >>>>>> Architecture: i386 (i686) >>>>>> >>>>>> Kernel: Linux 3.0.0-17-generic-pae >>>>>> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) >>>>>> Shell: /bin/sh linked to /bin/dash >>>>>> >>>>>> Versions of packages shotwell depends on: >>>>>> ii dbus-x11 1.6.2-2 >>>>>> ii libatk1.0-0 2.4.0-2 >>>>>> ii libc6 2.13-35 >>>>>> ii libcairo-gobject2 1.12.2-2 >>>>>> ii libcairo2 1.12.2-2 >>>>>> ii libexif12 0.6.20-3 >>>>>> ii libexiv2-12 0.23-1 >>>>>> ii libgdk-pixbuf2.0-0 2.26.1-1 >>>>>> ii libgee2 0.6.4-2 >>>>>> ii libgexiv2-1 0.4.1-3 >>>>>> ii libglib2.0-0 2.33.12+really2.32.3-1 >>>>>> ii libgomp1 4.7.1-9 >>>>>> ii libgphoto2-2 2.4.14-2 >>>>>> ii libgphoto2-port0 2.4.14-2 >>>>>> ii libgstreamer-plugins-base0.10-0 0.10.36-1 >>>>>> ii libgstreamer0.10-0 0.10.36-1 >>>>>> ii libgtk-3-0 3.4.2-3 >>>>>> ii libgudev-1.0-0 175-7 >>>>>> ii libjavascriptcoregtk-3.0-0 1.8.1-3.3 >>>>>> ii liblcms2-2 2.2+git20110628-2.2 >>>>>> ii libpango1.0-0 1.30.0-1 >>>>>> ii libraw5 0.14.6-2 >>>>>> ii librest-0.7-0 0.7.12-3 >>>>>> ii librsvg2-common 2.36.1-1 >>>>>> ii libsoup2.4-1 2.38.1-2 >>>>>> ii libsqlite3-0 3.7.13-1 >>>>>> ii libstdc++6 4.7.1-9 >>>>>> ii libunique-3.0-0 3.0.2-1 >>>>>> ii libwebkitgtk-3.0-0 1.8.1-3.3 >>>>>> ii libx11-6 2:1.5.0-1 >>>>>> ii libxml2 2.8.0+dfsg1-5 >>>>>> ii shotwell-common 0.12.3-2 >>>>>> >>>>>> shotwell recommends no packages. >>>>>> >>>>>> shotwell suggests no packages. >>>>>> >>>>>> -- no debconf information >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Shotwell mailing list >>>>> Shotwell at lists.yorba.org >>>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>>> >> >> > -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From adam at yorba.org Mon Sep 17 16:37:41 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 17 Sep 2012 16:30:41 -0007 Subject: [Shotwell] another bug report In-Reply-To: References: Message-ID: <505751d8.661c3c0a.29ae.ffffd62e@mx.google.com> Mike, thanks for the bug report. ?What operating system version are you running? ?You said "the latest version of Shotwell" - do you mean 0.12.3, 0.12.90, or built from git master? ?It looks like you built Shotwell yourself - yes? Unfortunately there's no debug information for libexiv2 in the stack trace below, so it's hard to see what's going on. ?Could you install debug symbols for libexiv2 and generate another backtrace? ?(On Ubuntu, for example, you would install the libexiv2-dbg package.) adam On Sat, Sep 15, 2012 at 12:20 AM, Mike Dupont wrote: Hi there, i installed the latest version of shotwell uploading a file, i think the problem is the the shared lib being incompatible, Program received signal SIGSEGV, Segmentation fault. 0xb7e5922e in std::_Rb_treestd::string>, std::_Select1ststd::string> >, std::less, std::allocator > >::find(std::string const&) () from /usr/lib/libexiv2.so.10 (gdb) bt #0 0xb7e5922e in std::_Rb_treeconst, std::string>, std::_Select1ststd::string> >, std::less, std::allocator > >::find(std::string const&) () from /usr/lib/libexiv2.so.10 #1 0xb7e7e7fc in ?? () from /usr/lib/libexiv2.so.10 #2 0xb7e5c3f6 in ?? () from /usr/lib/libexiv2.so.10 #3 0xb7e88584 in ?? () from /usr/lib/libexiv2.so.10 #4 0xb7e4b4ba in ?? () from /usr/lib/libexiv2.so.10 #5 0xb7e49109 in Exiv2::XmpParser::encode(std::string&, Exiv2::XmpData const&, unsigned short, unsigned int) () from /usr/lib/libexiv2.so.10 #6 0xb7dac668 in ?? () from /usr/lib/libexiv2.so.10 #7 0xb7dad3ea in Exiv2::JpegBase::writeMetadata() () from /usr/lib/libexiv2.so.10 #8 0xb7f36db8 in ?? () from /usr/lib/libgexiv2.so.1 #9 0xb7f37445 in gexiv2_metadata_save_file () from /usr/lib/libgexiv2.so.1 #10 0x081166eb in photo_metadata_write_to_file (self=0xa64b8440, file=0xa64a5dc0, error=0xbfffc76c) at /home/mdupont/experiments/photo/shotwell/src/photos/PhotoMetadata.vala:152 #11 0x0811c297 in jfif_metadata_writer_real_write_metadata (base=0x9cfedb0, metadata=0xa64b8440, error=0xbfffc818) at /home/mdupont/experiments/photo/shotwell/src/photos/JfifSupport.vala:139 #12 0x0810868e in photo_file_metadata_writer_write_metadata (self=0x9cfedb0, metadata=0xa64b8440, error=0xbfffc818) at /home/mdupont/experiments/photo/shotwell/src/photos/PhotoFileAdapter.vala:110 #13 0x082533d3 in photo_export (self=0x91401f0, dest_file=0x9d0a120, scaling=0xbfffc88c, quality=JPEG_QUALITY_HIGH, export_format=PHOTO_FILE_FORMAT_JFIF, direct_copy_unmodified=0, export_metadata=1, error=0xbfffc8b4) at /home/mdupont/experiments/photo/shotwell/src/Photo.vala:3427 #14 0x08129df5 in publishing_glue_media_source_publishable_wrapper_serialize_for_publishing ( self=0x9afd980, content_major_axis=720, strip_metadata=0, error=0xbfffc93c) at /home/mdupont/experiments/photo/shotwell/src/publishing/APIGlue.vala:54 #15 0x081288fd in spit_publishing_concrete_publishing_host_real_serialize_publishables ( base=0x9012418, content_major_axis=720, strip_metadata=0, result_target=0xbfffc9d4, result_target_destroy_notify=0xbfffc9d8) at /home/mdupont/experiments/photo/shotwell/src/publishing/PublishingPluginHost.vala:215 #16 0x080f5412 in spit_publishing_plugin_host_serialize_publishables (self=0x9012418, content_major_axis=720, strip_metadata=0, result_target=0xbfffc9d4, ---Type to continue, or q to quit---q result_target_destroy_notify=0xbQuit (gdb) info shared >From To Syms Read Shared Object Library 0xb7fde820 0xb7ff6b9f Yes (*) /lib/ld-linux.so.2 0xb7f57790 0xb7f8dfe8 Yes (*) /usr/lib/i386-linux-gnu/libgee.so.2 0xb7f369c0 0xb7f47468 Yes (*) /usr/lib/libgexiv2.so.1 0xb7d61010 0xb7e8f2c8 Yes (*) /usr/lib/libexiv2.so.10 0xb7d15f60 0xb7d26058 Yes (*) /usr/lib/i386-linux-gnu/libgstpbutils-0.10.so.0 0xb7c40fb0 0xb7cce1f8 Yes (*) /usr/lib/i386-linux-gnu/libgstreamer-0.10.so.0 0xb7c22c30 0xb7c23ce8 Yes (*) /usr/lib/i386-linux-gnu/libgmodule-2.0.so.0 0xb7c1ab00 0xb7c1d658 Yes (*) /usr/lib/i386-linux-gnu/libgudev-1.0.so.0 0xb7b9ecd0 0xb7bb1c48 Yes (*) /usr/lib/libgphoto2.so.2 0xb7b93670 0xb7b97878 Yes (*) /usr/lib/libgphoto2_port.so.0 0xb7b6a430 0xb7b84b08 Yes /lib/i386-linux-gnu/libm.so.6 0xb7b345a0 0xb7b48fac Yes (*) /usr/lib/libexif.so.12 0xb7aa9a50 0xb7ade168 Yes (*) /usr/lib/libraw.so.5 0xb79ffd30 0xb7a81c38 Yes /usr/lib/i386-linux-gnu/libsqlite3.so.0 0xb7594570 0xb787a648 Yes (*) /usr/lib/i386-linux-gnu/libgtk-3.so.0 0xb74d7100 0xb751ed08 Yes (*) /usr/lib/i386-linux-gnu/libgdk-3.so.0 0xb74bb510 0xb74c0998 Yes (*) /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 0xb749b0e0 0xb74af608 Yes (*) /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0 0xb7455600 0xb74775f8 Yes (*) /usr/lib/i386-linux-gnu/libpango-1.0.so.0 0xb738a3f0 0xb7421068 Yes (*) /usr/lib/i386-linux-gnu/libcairo.so.2 0xb724d5f0 0xb731f4c8 Yes (*) /usr/lib/i386-linux-gnu/libgio-2.0.so.0 0xb71e3300 0xb7213fc8 Yes (*) /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 0xb71d8450 0xb71d8608 Yes (*) /usr/lib/i386-linux-gnu/libgthread-2.0.so.0 0xb70f2b40 0xb71680d8 Yes (*) /lib/i386-linux-gnu/libglib-2.0.so.0 0xb70d0a60 0xb70d8c18 Yes (*) /usr/lib/i386-linux-gnu/libgomp.so.1 0xb70b7650 0xb70c3a78 Yes /lib/i386-linux-gnu/libpthread.so.0 0xb6f24f10 0xb705535c Yes /lib/i386-linux-gnu/libc.so.6 0xb6d2ab70 0xb6e6b898 Yes (*) /usr/lib/libexiv2.so.11 0xb6cdef50 0xb6cf5cf8 Yes (*) /lib/i386-linux-gnu/libgcc_s.so.1 0xb6cc8760 0xb6cd5668 Yes (*) /lib/i386-linux-gnu/libz.so.1 0xb6c9f020 0xb6cb8828 Yes (*) /lib/i386-linux-gnu/libexpat.so.1 ---Type to continue, or q to quit--- 0xb6bfdd00 0xb6c6c208 Yes (*) /usr/lib/i386-linux-gnu/libstdc++.so.6 0xb6a86960 0xb6b70f28 Yes (*) /usr/lib/i386-linux-gnu/libxml2.so.2 0xb6a628d0 0xb6a66618 Yes /lib/i386-linux-gnu/librt.so.1 0xb6a5ca60 0xb6a5da08 Yes /lib/i386-linux-gnu/libdl.so.2 0xb6a4e610 0xb6a55488 Yes (*) /lib/i386-linux-gnu/libudev.so.0 0xb6a43730 0xb6a48178 Yes (*) /usr/lib/i386-linux-gnu/libltdl.so.7 0xb69f3170 0xb6a29538 Yes (*) /usr/lib/i386-linux-gnu/libjasper.so.1 0xb69a5f10 0xb69d8128 Yes (*) /usr/lib/i386-linux-gnu/liblcms2.so.2 0xb687d1e0 0xb690b558 Yes (*) /usr/lib/i386-linux-gnu/libX11.so.6 0xb685d830 0xb6867a88 Yes (*) /usr/lib/i386-linux-gnu/libXi.so.6 0xb6856f60 0xb6859698 Yes (*) /usr/lib/i386-linux-gnu/libXfixes.so.3 0xb683c290 0xb68499d8 Yes (*) /usr/lib/i386-linux-gnu/libatk-1.0.so.0 0xb682f980 0xb6830b78 Yes (*) /usr/lib/i386-linux-gnu/libcairo-gobject.so.2 0xb6806e90 0xb6822e78 Yes (*) /usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0 0xb67d2070 0xb67ed298 Yes (*) /usr/lib/i386-linux-gnu/libfontconfig.so.1 0xb67be700 0xb67c8ca8 Yes (*) /usr/lib/i386-linux-gnu/libXext.so.6 0xb67b8770 0xb67b9158 Yes (*) /usr/lib/i386-linux-gnu/libXinerama.so.1 0xb67af100 0xb67b3c18 Yes (*) /usr/lib/i386-linux-gnu/libXrandr.so.2 0xb67a4ad0 0xb67a9e68 Yes (*) /usr/lib/i386-linux-gnu/libXcursor.so.1 0xb679f880 0xb67a02e8 Yes (*) /usr/lib/i386-linux-gnu/libXcomposite.so.1 0xb679b7c0 0xb679c148 Yes (*) /usr/lib/i386-linux-gnu/libXdamage.so.1 0xb67077d0 0xb6773388 Yes (*) /usr/lib/i386-linux-gnu/libfreetype.so.6 0xb666c070 0xb66ed168 Yes (*) /usr/lib/i386-linux-gnu/libpixman-1.so.0 0xb66417c0 0xb665e528 Yes (*) /lib/i386-linux-gnu/libpng12.so.0 0xb663a750 0xb663b148 Yes (*) /usr/lib/i386-linux-gnu/libxcb-shm.so.0 0xb66328d0 0xb66364d8 Yes (*) /usr/lib/i386-linux-gnu/libxcb-render.so.0 0xb6616ba0 0xb6626d98 Yes (*) /usr/lib/i386-linux-gnu/libxcb.so.1 0xb66052f0 0xb660b028 Yes (*) /usr/lib/i386-linux-gnu/libXrender.so.1 0xb65e9140 0xb65fa968 Yes (*) /lib/i386-linux-gnu/libselinux.so.1 0xb65cf6b0 0xb65dc578 Yes /lib/i386-linux-gnu/libresolv.so.2 0xb65c6ef0 0xb65ca538 Yes (*) /usr/lib/i386-linux-gnu/libffi.so.6 0xb658af60 0xb65b1138 Yes (*) /lib/i386-linux-gnu/libpcre.so.3 ---Type to continue, or q to quit--- 0xb6534a30 0xb656e5b8 Yes (*) /usr/lib/i386-linux-gnu/libjpeg.so.8 0xb652e9e0 0xb652f828 Yes (*) /usr/lib/i386-linux-gnu/libXau.so.6 0xb6527d00 0xb65299a8 Yes (*) /usr/lib/i386-linux-gnu/libXdmcp.so.6 0xb7fb43a0 0xb7fd0428 Yes (*) /usr/lib/gio/modules/libgvfsdbus.so 0xb6511620 0xb651c718 Yes (*) /usr/lib/gvfs/libgvfscommon.so 0xb6492d90 0xb64c2198 Yes (*) /lib/i386-linux-gnu/libdbus-1.so.3 0xb6485dc0 0xb648ac98 Yes /lib/i386-linux-gnu/libnss_compat.so.2 0xb646e160 0xb647afa8 Yes /lib/i386-linux-gnu/libnsl.so.1 0xb6460970 0xb6466f58 Yes /lib/i386-linux-gnu/libnss_nis.so.2 0xb6453a10 0xb645ab18 Yes /lib/i386-linux-gnu/libnss_files.so.2 0xb64fdf50 0xb6506ed8 Yes (*) /usr/lib/liboverlay-scrollbar3-0.2.so.0 0xb64f6650 0xb64f87f8 Yes (*) /usr/lib/gtk-3.0/modules/libcanberra-gtk-module.so 0xb64193a0 0xb641a948 Yes (*) /usr/lib/libcanberra-gtk3.so.0 0xb64e5f30 0xb64eff28 Yes (*) /usr/lib/libcanberra.so.0 0xb64db590 0xb64e0858 Yes (*) /usr/lib/i386-linux-gnu/libvorbisfile.so.3 0xb64068d0 0xb6411158 Yes (*) /usr/lib/i386-linux-gnu/libtdb.so.1 0xb63dbfb0 0xb63f1c18 Yes (*) /usr/lib/i386-linux-gnu/libvorbis.so.0 0xb63d3340 0xb63d5fe8 Yes (*) /usr/lib/i386-linux-gnu/libogg.so.0 0xb6443260 0xb644d768 Yes (*) /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so 0xb63ae400 0xb63b00d8 Yes (*) /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so 0xb641e770 0xb641ebc8 Yes (*) /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so 0xb5b44890 0xb5b6d648 Yes (*) /usr/lib/i386-linux-gnu/librsvg-2.so.2 0xb5b122c0 0xb5b33b58 Yes (*) /usr/lib/libcroco-0.6.so.3 0xb5b7b920 0xb5b7ea06 Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-transitions.so 0xb5988100 0xb59d532f Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-publishing.so 0xaa6bb080 0xab6d74b8 Yes (*) /usr/lib/libwebkitgtk-3.0.so.0 0xaa54f220 0xaa557608 Yes (*) /usr/lib/librest-0.7.so.0 0xaa4f4e50 0xaa531388 Yes (*) /usr/lib/i386-linux-gnu/libsoup-2.4.so.1 0xaa4c5600 0xaa4d9258 Yes (*) /usr/lib/i386-linux-gnu/libjson-glib-1.0.so.0 0xaa182720 0xaa432fb8 Yes (*) /usr/lib/libjavascriptcoregtk-3.0.so.0 ---Type to continue, or q to quit--- 0xb596b060 0xb5970888 Yes (*) /usr/lib/libenchant.so.1 0xb5b03f10 0xb5b08718 Yes (*) /usr/lib/i386-linux-gnu/libgailutil-3.so.0 0xaa0eb8a0 0xaa0f4018 Yes (*) /usr/lib/libgeoclue.so.0 0xaa0dc390 0xaa0e2578 Yes (*) /usr/lib/i386-linux-gnu/libgstapp-0.10.so.0 0xaa0cca80 0xaa0d3698 Yes (*) /usr/lib/i386-linux-gnu/libgstinterfaces-0.10.so.0 0xaa0aea40 0xaa0c0c38 Yes (*) /usr/lib/i386-linux-gnu/libgstvideo-0.10.so.0 0xaa053bb0 0xaa096a88 Yes (*) /usr/lib/i386-linux-gnu/libgstbase-0.10.so.0 0xaa015ef0 0xaa03cc2c Yes (*) /usr/lib/libxslt.so.1 0xa9e85680 0xa9fb8bb8 Yes (*) /usr/lib/libicui18n.so.48 0xa9d02d30 0xa9dcd848 Yes (*) /usr/lib/libicuuc.so.48 0xa9c829b0 0xa9cbf3e8 Yes (*) /usr/lib/i386-linux-gnu/libXt.so.6 0xb59643c0 0xb5965718 Yes (*) /usr/lib/i386-linux-gnu/libsoup-gnome-2.4.so.1 0xa9c580f0 0xa9c6c1a8 Yes (*) /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 0xa9bc8ab0 0xa9c2c708 Yes (*) /usr/lib/i386-linux-gnu/liborc-0.4.so.0 0xa8a50370 0xa8a50468 Yes (*) /usr/lib/libicudata.so.48 0xa8a48430 0xa8a4cb48 Yes (*) /usr/lib/i386-linux-gnu/libSM.so.6 0xa8a30010 0xa8a3ed38 Yes (*) /usr/lib/i386-linux-gnu/libICE.so.6 0xa8a0f6f0 0xa8a22288 Yes (*) /usr/lib/i386-linux-gnu/libgnome-keyring.so.0 0xa8a04fb0 0xa8a06c28 Yes (*) /lib/i386-linux-gnu/libuuid.so.1 0xa89837d0 0xa89dc558 Yes (*) /lib/i386-linux-gnu/libgcrypt.so.11 0xa897a630 0xa897abf8 Yes (*) /lib/i386-linux-gnu/libgpg-error.so.0 0xabae94d0 0xabafbe31 Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-data-imports.so 0xa894d550 0xa8968b3a Yes /usr/local/lib/shotwell/plugins/builtin/shotwell-publishing-extras.so 0xa88f4dd0 0xa88f8368 Yes (*) /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so 0xa8082a90 0xa8082ff8 Yes (*) /usr/lib/i386-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so 0xa807d8b0 0xa807f458 Yes (*) /usr/lib/gtk-3.0/3.0.0/menuproxies/libappmenu.so 0xa8039930 0xa8042058 Yes (*) /usr/lib/libdbusmenu-gtk3.so.4 0xa801d320 0xa802c5a8 Yes (*) /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4 0xa8069b60 0xa8076578 Yes (*) /usr/lib/gio/modules/libgioremote-volume-monitor.so 0xa8061060 0xa8062e98 Yes (*) /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so ---Type to continue, or q to quit--- 0xa6312e00 0xa63200c8 Yes (*) /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so 0xa804fd30 0xa8059258 Yes (*) /usr/lib/i386-linux-gnu/libp11-kit.so.0 0xa4fef7e0 0xa507fbd8 Yes (*) /usr/lib/i386-linux-gnu/libgnutls.so.26 0xa80080e0 0xa8014038 Yes (*) /usr/lib/i386-linux-gnu/libtasn1.so.3 0xa6506a10 0xa6511468 Yes (*) /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so (*): Shared library is missing debugging information. -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From jamesmikedupont at googlemail.com Mon Sep 17 17:08:51 2012 From: jamesmikedupont at googlemail.com (Mike Dupont) Date: Mon, 17 Sep 2012 19:08:51 +0200 Subject: [Shotwell] another bug report In-Reply-To: <505751d8.661c3c0a.29ae.ffffd62e@mx.google.com> References: <505751d8.661c3c0a.29ae.ffffd62e@mx.google.com> Message-ID: I rebuilt libexiv2 from source and it worked, I think the problem is that the git master latest version of shotwell does not work with let me debug this I am using ubuntu precise with libexiv2-dbg i386 0.22-2 Here is an error just importing a file , looks like a problem with the xml Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xa6429b40 (LWP 10728)] 0xb7e5625f in lower_bound (__k=..., this=) at XMPMeta.cpp:1650 1650 XMPMeta.cpp: No such file or directory. (gdb) bt #0 0xb7e5625f in lower_bound (__k=..., this=) at XMPMeta.cpp:1650 #1 lower_bound (__x=..., this=) at /usr/include/c++/4.6/bits/stl_map.h:784 #2 operator[] (__k=..., this=) at /usr/include/c++/4.6/bits/stl_map.h:450 #3 XMPMeta::RegisterNamespace (namespaceURI=0x0, prefix=0xa5b15797 "") at XMPMeta.cpp:1049 #4 0xb7e75545 in StartNamespaceDeclHandler (userData=0xa5b1c4a0, prefix=0xa5b15796 "x", uri=) at ExpatAdapter.cpp:263 #5 0xb6bb176d in ?? () from /lib/i386-linux-gnu/libexpat.so.1 #6 0xb6bb3bb9 in ?? () from /lib/i386-linux-gnu/libexpat.so.1 #7 0xb6bb6a7d in ?? () from /lib/i386-linux-gnu/libexpat.so.1 #8 0xb6bb7a82 in ?? () from /lib/i386-linux-gnu/libexpat.so.1 #9 0xb6bb48f1 in ?? () from /lib/i386-linux-gnu/libexpat.so.1 #10 0xb6bb6332 in ?? () from /lib/i386-linux-gnu/libexpat.so.1 #11 0xb6bb974b in XML_ParseBuffer () from /lib/i386-linux-gnu/libexpat.so.1 #12 0xb6bb9b22 in XML_Parse () from /lib/i386-linux-gnu/libexpat.so.1 #13 0xb7e755aa in ExpatAdapter::ParseBuffer (this=0xa5b1c4a0, buffer=, length=, last=false) at ExpatAdapter.cpp:135 #14 0xb7e5d1de in ProcessUTF8Portion (xmlParser=0xa5b1c4a0, buffer=0xa5b1c2fc "\r\n\r\n\r\n::ParseFromBuffer (this=0xa6428508, buffer=0xa5b1c2fc "\r\n, std::allocator > >::TXMPMeta ( this=0xa6428508, buffer=0xa5b1c2fc "\r\n to continue, or q to quit--- at /home/mdupont/experiments/photo/shotwell/src/photos/GdkSupport.vala:14 #26 0x0813b3e4 in photo_file_reader_read_metadata (self=0x9b522d0, error=0xa6428b94) at /home/mdupont/experiments/photo/shotwell/src/photos/PhotoFileAdapter.vala:72 #27 0x0836c281 in prepare_files_job_prepare_file (self=0x99de540, job=0x9ad5880, file=0x99e9b00, associated_file=0x0, copy_to_library=0, prepared_file=0xa6428e0c) at /home/mdupont/experiments/photo/shotwell/src/BatchImport.vala:1692 #28 0x0836a8c8 in prepare_files_job_real_execute (base=0x99de540) at /home/mdupont/experiments/photo/shotwell/src/BatchImport.vala:1581 #29 0x080bc7b2 in background_job_execute (self=0x99de540) at /home/mdupont/experiments/photo/shotwell/src/threads/BackgroundJob.vala:123 #30 0x080badd3 in workers_thread_start (self=0x9b1a248, ignored=0x99de540) at /home/mdupont/experiments/photo/shotwell/src/threads/Workers.vala:94 #31 0x080b9fd8 in _workers_thread_start_gfunc (data=0x99de540, self=0x9b1a248) at /home/mdupont/experiments/photo/shotwell/src/threads/Workers.vala:31 #32 0xb7136047 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #33 0xb71356b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #34 0xb70a5d4c in start_thread (arg=0xa6429b40) at pthread_create.c:308 #35 0xb6fe4ace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 (gdb) On Mon, Sep 17, 2012 at 6:37 PM, Adam Dingle wrote: > Mike, > > thanks for the bug report. What operating system version are you running? > You said "the latest version of Shotwell" - do you mean 0.12.3, 0.12.90, or > built from git master? It looks like you built Shotwell yourself - yes? > > Unfortunately there's no debug information for libexiv2 in the stack trace > below, so it's hard to see what's going on. Could you install debug symbols > for libexiv2 and generate another backtrace? (On Ubuntu, for example, you > would install the libexiv2-dbg package.) > > adam > > On Sat, Sep 15, 2012 at 12:20 AM, Mike Dupont > wrote: > > Hi there, > i installed the latest version of shotwell > > uploading a file, i think the problem is the the shared lib being > incompatible, > > Program received signal SIGSEGV, Segmentation fault. > 0xb7e5922e in std::_Rb_treestd::string>, std::_Select1ststd::string> >, > std::less, > std::allocator > >>::find(std::string const&) () from /usr/lib/libexiv2.so.10 > (gdb) bt > #0 0xb7e5922e in std::_Rb_treeconst, std::string>, > std::_Select1ststd::string> >, std::less, > std::allocator > >>::find(std::string const&) () from /usr/lib/libexiv2.so.10 > #1 0xb7e7e7fc in ?? () from /usr/lib/libexiv2.so.10 > #2 0xb7e5c3f6 in ?? () from /usr/lib/libexiv2.so.10 > #3 0xb7e88584 in ?? () from /usr/lib/libexiv2.so.10 > #4 0xb7e4b4ba in ?? () from /usr/lib/libexiv2.so.10 > #5 0xb7e49109 in Exiv2::XmpParser::encode(std::string&, > Exiv2::XmpData const&, unsigned short, unsigned int) () from > /usr/lib/libexiv2.so.10 > #6 0xb7dac668 in ?? () from /usr/lib/libexiv2.so.10 > #7 0xb7dad3ea in Exiv2::JpegBase::writeMetadata() () from > /usr/lib/libexiv2.so.10 > #8 0xb7f36db8 in ?? () from /usr/lib/libgexiv2.so.1 > #9 0xb7f37445 in gexiv2_metadata_save_file () from /usr/lib/libgexiv2.so.1 > #10 0x081166eb in photo_metadata_write_to_file (self=0xa64b8440, > file=0xa64a5dc0, error=0xbfffc76c) > at > /home/mdupont/experiments/photo/shotwell/src/photos/PhotoMetadata.vala:152 > #11 0x0811c297 in jfif_metadata_writer_real_write_metadata > (base=0x9cfedb0, metadata=0xa64b8440, > error=0xbfffc818) at > /home/mdupont/experiments/photo/shotwell/src/photos/JfifSupport.vala:139 > #12 0x0810868e in photo_file_metadata_writer_write_metadata > (self=0x9cfedb0, metadata=0xa64b8440, > error=0xbfffc818) at > /home/mdupont/experiments/photo/shotwell/src/photos/PhotoFileAdapter.vala:110 > #13 0x082533d3 in photo_export (self=0x91401f0, dest_file=0x9d0a120, > scaling=0xbfffc88c, > quality=JPEG_QUALITY_HIGH, export_format=PHOTO_FILE_FORMAT_JFIF, > direct_copy_unmodified=0, > export_metadata=1, error=0xbfffc8b4) > at /home/mdupont/experiments/photo/shotwell/src/Photo.vala:3427 > #14 0x08129df5 in > publishing_glue_media_source_publishable_wrapper_serialize_for_publishing > ( > self=0x9afd980, content_major_axis=720, strip_metadata=0, error=0xbfffc93c) > at /home/mdupont/experiments/photo/shotwell/src/publishing/APIGlue.vala:54 > #15 0x081288fd in > spit_publishing_concrete_publishing_host_real_serialize_publishables ( > base=0x9012418, content_major_axis=720, strip_metadata=0, > result_target=0xbfffc9d4, > result_target_destroy_notify=0xbfffc9d8) > at > /home/mdupont/experiments/photo/shotwell/src/publishing/PublishingPluginHost.vala:215 > #16 0x080f5412 in spit_publishing_plugin_host_serialize_publishables > (self=0x9012418, > content_major_axis=720, strip_metadata=0, result_target=0xbfffc9d4, > ---Type to continue, or q to quit---q > result_target_destroy_notify=0xbQuit > > (gdb) info shared > From To Syms Read Shared Object Library > 0xb7fde820 0xb7ff6b9f Yes (*) /lib/ld-linux.so.2 > 0xb7f57790 0xb7f8dfe8 Yes (*) /usr/lib/i386-linux-gnu/libgee.so.2 > 0xb7f369c0 0xb7f47468 Yes (*) /usr/lib/libgexiv2.so.1 > 0xb7d61010 0xb7e8f2c8 Yes (*) /usr/lib/libexiv2.so.10 > 0xb7d15f60 0xb7d26058 Yes (*) > /usr/lib/i386-linux-gnu/libgstpbutils-0.10.so.0 > 0xb7c40fb0 0xb7cce1f8 Yes (*) > /usr/lib/i386-linux-gnu/libgstreamer-0.10.so.0 > 0xb7c22c30 0xb7c23ce8 Yes (*) /usr/lib/i386-linux-gnu/libgmodule-2.0.so.0 > 0xb7c1ab00 0xb7c1d658 Yes (*) /usr/lib/i386-linux-gnu/libgudev-1.0.so.0 > 0xb7b9ecd0 0xb7bb1c48 Yes (*) /usr/lib/libgphoto2.so.2 > 0xb7b93670 0xb7b97878 Yes (*) /usr/lib/libgphoto2_port.so.0 > 0xb7b6a430 0xb7b84b08 Yes /lib/i386-linux-gnu/libm.so.6 > 0xb7b345a0 0xb7b48fac Yes (*) /usr/lib/libexif.so.12 > 0xb7aa9a50 0xb7ade168 Yes (*) /usr/lib/libraw.so.5 > 0xb79ffd30 0xb7a81c38 Yes /usr/lib/i386-linux-gnu/libsqlite3.so.0 > 0xb7594570 0xb787a648 Yes (*) /usr/lib/i386-linux-gnu/libgtk-3.so.0 > 0xb74d7100 0xb751ed08 Yes (*) /usr/lib/i386-linux-gnu/libgdk-3.so.0 > 0xb74bb510 0xb74c0998 Yes (*) > /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 > 0xb749b0e0 0xb74af608 Yes (*) > /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0 > 0xb7455600 0xb74775f8 Yes (*) /usr/lib/i386-linux-gnu/libpango-1.0.so.0 > 0xb738a3f0 0xb7421068 Yes (*) /usr/lib/i386-linux-gnu/libcairo.so.2 > 0xb724d5f0 0xb731f4c8 Yes (*) /usr/lib/i386-linux-gnu/libgio-2.0.so.0 > 0xb71e3300 0xb7213fc8 Yes (*) /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 > 0xb71d8450 0xb71d8608 Yes (*) /usr/lib/i386-linux-gnu/libgthread-2.0.so.0 > 0xb70f2b40 0xb71680d8 Yes (*) /lib/i386-linux-gnu/libglib-2.0.so.0 > 0xb70d0a60 0xb70d8c18 Yes (*) /usr/lib/i386-linux-gnu/libgomp.so.1 > 0xb70b7650 0xb70c3a78 Yes /lib/i386-linux-gnu/libpthread.so.0 > 0xb6f24f10 0xb705535c Yes /lib/i386-linux-gnu/libc.so.6 > 0xb6d2ab70 0xb6e6b898 Yes (*) /usr/lib/libexiv2.so.11 > 0xb6cdef50 0xb6cf5cf8 Yes (*) /lib/i386-linux-gnu/libgcc_s.so.1 > 0xb6cc8760 0xb6cd5668 Yes (*) /lib/i386-linux-gnu/libz.so.1 > 0xb6c9f020 0xb6cb8828 Yes (*) /lib/i386-linux-gnu/libexpat.so.1 > ---Type to continue, or q to quit--- > 0xb6bfdd00 0xb6c6c208 Yes (*) /usr/lib/i386-linux-gnu/libstdc++.so.6 > 0xb6a86960 0xb6b70f28 Yes (*) /usr/lib/i386-linux-gnu/libxml2.so.2 > 0xb6a628d0 0xb6a66618 Yes /lib/i386-linux-gnu/librt.so.1 > 0xb6a5ca60 0xb6a5da08 Yes /lib/i386-linux-gnu/libdl.so.2 > 0xb6a4e610 0xb6a55488 Yes (*) /lib/i386-linux-gnu/libudev.so.0 > 0xb6a43730 0xb6a48178 Yes (*) /usr/lib/i386-linux-gnu/libltdl.so.7 > 0xb69f3170 0xb6a29538 Yes (*) /usr/lib/i386-linux-gnu/libjasper.so.1 > 0xb69a5f10 0xb69d8128 Yes (*) /usr/lib/i386-linux-gnu/liblcms2.so.2 > 0xb687d1e0 0xb690b558 Yes (*) /usr/lib/i386-linux-gnu/libX11.so.6 > 0xb685d830 0xb6867a88 Yes (*) /usr/lib/i386-linux-gnu/libXi.so.6 > 0xb6856f60 0xb6859698 Yes (*) /usr/lib/i386-linux-gnu/libXfixes.so.3 > 0xb683c290 0xb68499d8 Yes (*) /usr/lib/i386-linux-gnu/libatk-1.0.so.0 > 0xb682f980 0xb6830b78 Yes (*) > /usr/lib/i386-linux-gnu/libcairo-gobject.so.2 > 0xb6806e90 0xb6822e78 Yes (*) /usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0 > 0xb67d2070 0xb67ed298 Yes (*) /usr/lib/i386-linux-gnu/libfontconfig.so.1 > 0xb67be700 0xb67c8ca8 Yes (*) /usr/lib/i386-linux-gnu/libXext.so.6 > 0xb67b8770 0xb67b9158 Yes (*) /usr/lib/i386-linux-gnu/libXinerama.so.1 > 0xb67af100 0xb67b3c18 Yes (*) /usr/lib/i386-linux-gnu/libXrandr.so.2 > 0xb67a4ad0 0xb67a9e68 Yes (*) /usr/lib/i386-linux-gnu/libXcursor.so.1 > 0xb679f880 0xb67a02e8 Yes (*) /usr/lib/i386-linux-gnu/libXcomposite.so.1 > 0xb679b7c0 0xb679c148 Yes (*) /usr/lib/i386-linux-gnu/libXdamage.so.1 > 0xb67077d0 0xb6773388 Yes (*) /usr/lib/i386-linux-gnu/libfreetype.so.6 > 0xb666c070 0xb66ed168 Yes (*) /usr/lib/i386-linux-gnu/libpixman-1.so.0 > 0xb66417c0 0xb665e528 Yes (*) /lib/i386-linux-gnu/libpng12.so.0 > 0xb663a750 0xb663b148 Yes (*) /usr/lib/i386-linux-gnu/libxcb-shm.so.0 > 0xb66328d0 0xb66364d8 Yes (*) /usr/lib/i386-linux-gnu/libxcb-render.so.0 > 0xb6616ba0 0xb6626d98 Yes (*) /usr/lib/i386-linux-gnu/libxcb.so.1 > 0xb66052f0 0xb660b028 Yes (*) /usr/lib/i386-linux-gnu/libXrender.so.1 > 0xb65e9140 0xb65fa968 Yes (*) /lib/i386-linux-gnu/libselinux.so.1 > 0xb65cf6b0 0xb65dc578 Yes /lib/i386-linux-gnu/libresolv.so.2 > 0xb65c6ef0 0xb65ca538 Yes (*) /usr/lib/i386-linux-gnu/libffi.so.6 > 0xb658af60 0xb65b1138 Yes (*) /lib/i386-linux-gnu/libpcre.so.3 > ---Type to continue, or q to quit--- > 0xb6534a30 0xb656e5b8 Yes (*) /usr/lib/i386-linux-gnu/libjpeg.so.8 > 0xb652e9e0 0xb652f828 Yes (*) /usr/lib/i386-linux-gnu/libXau.so.6 > 0xb6527d00 0xb65299a8 Yes (*) /usr/lib/i386-linux-gnu/libXdmcp.so.6 > 0xb7fb43a0 0xb7fd0428 Yes (*) /usr/lib/gio/modules/libgvfsdbus.so > 0xb6511620 0xb651c718 Yes (*) /usr/lib/gvfs/libgvfscommon.so > 0xb6492d90 0xb64c2198 Yes (*) /lib/i386-linux-gnu/libdbus-1.so.3 > 0xb6485dc0 0xb648ac98 Yes /lib/i386-linux-gnu/libnss_compat.so.2 > 0xb646e160 0xb647afa8 Yes /lib/i386-linux-gnu/libnsl.so.1 > 0xb6460970 0xb6466f58 Yes /lib/i386-linux-gnu/libnss_nis.so.2 > 0xb6453a10 0xb645ab18 Yes /lib/i386-linux-gnu/libnss_files.so.2 > 0xb64fdf50 0xb6506ed8 Yes (*) /usr/lib/liboverlay-scrollbar3-0.2.so.0 > 0xb64f6650 0xb64f87f8 Yes (*) > /usr/lib/gtk-3.0/modules/libcanberra-gtk-module.so > 0xb64193a0 0xb641a948 Yes (*) /usr/lib/libcanberra-gtk3.so.0 > 0xb64e5f30 0xb64eff28 Yes (*) /usr/lib/libcanberra.so.0 > 0xb64db590 0xb64e0858 Yes (*) /usr/lib/i386-linux-gnu/libvorbisfile.so.3 > 0xb64068d0 0xb6411158 Yes (*) /usr/lib/i386-linux-gnu/libtdb.so.1 > 0xb63dbfb0 0xb63f1c18 Yes (*) /usr/lib/i386-linux-gnu/libvorbis.so.0 > 0xb63d3340 0xb63d5fe8 Yes (*) /usr/lib/i386-linux-gnu/libogg.so.0 > 0xb6443260 0xb644d768 Yes (*) > /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so > 0xb63ae400 0xb63b00d8 Yes (*) > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so > 0xb641e770 0xb641ebc8 Yes (*) > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so > 0xb5b44890 0xb5b6d648 Yes (*) /usr/lib/i386-linux-gnu/librsvg-2.so.2 > 0xb5b122c0 0xb5b33b58 Yes (*) /usr/lib/libcroco-0.6.so.3 > 0xb5b7b920 0xb5b7ea06 Yes > /usr/local/lib/shotwell/plugins/builtin/shotwell-transitions.so > 0xb5988100 0xb59d532f Yes > /usr/local/lib/shotwell/plugins/builtin/shotwell-publishing.so > 0xaa6bb080 0xab6d74b8 Yes (*) /usr/lib/libwebkitgtk-3.0.so.0 > 0xaa54f220 0xaa557608 Yes (*) /usr/lib/librest-0.7.so.0 > 0xaa4f4e50 0xaa531388 Yes (*) /usr/lib/i386-linux-gnu/libsoup-2.4.so.1 > 0xaa4c5600 0xaa4d9258 Yes (*) > /usr/lib/i386-linux-gnu/libjson-glib-1.0.so.0 > 0xaa182720 0xaa432fb8 Yes (*) /usr/lib/libjavascriptcoregtk-3.0.so.0 > ---Type to continue, or q to quit--- > 0xb596b060 0xb5970888 Yes (*) /usr/lib/libenchant.so.1 > 0xb5b03f10 0xb5b08718 Yes (*) /usr/lib/i386-linux-gnu/libgailutil-3.so.0 > 0xaa0eb8a0 0xaa0f4018 Yes (*) /usr/lib/libgeoclue.so.0 > 0xaa0dc390 0xaa0e2578 Yes (*) /usr/lib/i386-linux-gnu/libgstapp-0.10.so.0 > 0xaa0cca80 0xaa0d3698 Yes (*) > /usr/lib/i386-linux-gnu/libgstinterfaces-0.10.so.0 > 0xaa0aea40 0xaa0c0c38 Yes (*) > /usr/lib/i386-linux-gnu/libgstvideo-0.10.so.0 > 0xaa053bb0 0xaa096a88 Yes (*) /usr/lib/i386-linux-gnu/libgstbase-0.10.so.0 > 0xaa015ef0 0xaa03cc2c Yes (*) /usr/lib/libxslt.so.1 > 0xa9e85680 0xa9fb8bb8 Yes (*) /usr/lib/libicui18n.so.48 > 0xa9d02d30 0xa9dcd848 Yes (*) /usr/lib/libicuuc.so.48 > 0xa9c829b0 0xa9cbf3e8 Yes (*) /usr/lib/i386-linux-gnu/libXt.so.6 > 0xb59643c0 0xb5965718 Yes (*) > /usr/lib/i386-linux-gnu/libsoup-gnome-2.4.so.1 > 0xa9c580f0 0xa9c6c1a8 Yes (*) /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 > 0xa9bc8ab0 0xa9c2c708 Yes (*) /usr/lib/i386-linux-gnu/liborc-0.4.so.0 > 0xa8a50370 0xa8a50468 Yes (*) /usr/lib/libicudata.so.48 > 0xa8a48430 0xa8a4cb48 Yes (*) /usr/lib/i386-linux-gnu/libSM.so.6 > 0xa8a30010 0xa8a3ed38 Yes (*) /usr/lib/i386-linux-gnu/libICE.so.6 > 0xa8a0f6f0 0xa8a22288 Yes (*) > /usr/lib/i386-linux-gnu/libgnome-keyring.so.0 > 0xa8a04fb0 0xa8a06c28 Yes (*) /lib/i386-linux-gnu/libuuid.so.1 > 0xa89837d0 0xa89dc558 Yes (*) /lib/i386-linux-gnu/libgcrypt.so.11 > 0xa897a630 0xa897abf8 Yes (*) /lib/i386-linux-gnu/libgpg-error.so.0 > 0xabae94d0 0xabafbe31 Yes > /usr/local/lib/shotwell/plugins/builtin/shotwell-data-imports.so > 0xa894d550 0xa8968b3a Yes > /usr/local/lib/shotwell/plugins/builtin/shotwell-publishing-extras.so > 0xa88f4dd0 0xa88f8368 Yes (*) > /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so > 0xa8082a90 0xa8082ff8 Yes (*) > /usr/lib/i386-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so > 0xa807d8b0 0xa807f458 Yes (*) > /usr/lib/gtk-3.0/3.0.0/menuproxies/libappmenu.so > 0xa8039930 0xa8042058 Yes (*) /usr/lib/libdbusmenu-gtk3.so.4 > 0xa801d320 0xa802c5a8 Yes (*) > /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4 > 0xa8069b60 0xa8076578 Yes (*) > /usr/lib/gio/modules/libgioremote-volume-monitor.so > 0xa8061060 0xa8062e98 Yes (*) > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so > ---Type to continue, or q to quit--- > 0xa6312e00 0xa63200c8 Yes (*) > /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so > 0xa804fd30 0xa8059258 Yes (*) /usr/lib/i386-linux-gnu/libp11-kit.so.0 > 0xa4fef7e0 0xa507fbd8 Yes (*) /usr/lib/i386-linux-gnu/libgnutls.so.26 > 0xa80080e0 0xa8014038 Yes (*) /usr/lib/i386-linux-gnu/libtasn1.so.3 > 0xa6506a10 0xa6511468 Yes (*) > /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so > (*): Shared library is missing debugging information. > > > > -- > James Michael DuPont > Member of Free Libre Open Source Software Kosova http://flossk.org > Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com > Contributor FOSM, the CC-BY-SA map of the world http://fosm.org > Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 > > -- James Michael DuPont Member of Free Libre Open Source Software Kosova http://flossk.org Saving wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com Contributor FOSM, the CC-BY-SA map of the world http://fosm.org Mozilla Rep https://reps.mozilla.org/u/h4ck3rm1k3 From adam at yorba.org Mon Sep 17 17:49:20 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 17 Sep 2012 17:42:20 -0007 Subject: [Shotwell] Build error 0.13 In-Reply-To: <1347836602.41295.YahooMailNeo@web122306.mail.ne1.yahoo.com> References: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> <1347836602.41295.YahooMailNeo@web122306.mail.ne1.yahoo.com> Message-ID: <505762a3.2230b60a.0418.ffffe428@mx.google.com> Luc, thanks for the patch. ?We've spent a fair amount of time at Yorba thinking about which metadata fields to write titles to. ?Unfortunately different programs use these fields in different ways. ?See the tables at http://redmine.yorba.org/projects/shotwell/wiki/PhotoTags If we don't write to Iptc.Application2.Caption, then some programs (most notably Picasa) will not be able to read titles exported from Shotwell. ?On the other hand, some Apple programs (iPhoto and Picasa) use ?Iptc.Application2.Caption to store descriptions, so as you pointed out we could clobber those when writing. ?I don't see any ideal solution here at the moment. We generated the tables on the wiki page above by testing various programs a couple of years ago. ?It would be interesting to refresh those tables to see if programs' behavior has changed. ?I really hope that different programs can converge on a single metadata tag for storing captions and another for descriptions. ?Xmp.dc.title and Xmp.dc.description would be good candidates for this. adam On Sun, Sep 16, 2012 at 4:03 PM, Luc More wrote: Hi Adam, The new build worked fine, thanks for the quick reaction. Then I patched the following because I would like shotwell to leave the Caption tag alone when setting the Picure Title (I use Caption with other programs for a long description on some photos).? Eventually I'd like shotwell to handle both fields but that would be a much heavier change.? Initial testing shows that it works well in my workflow (e.g. Flickr Uploader can set both fields on my uploads -- not if I use shotwell's plugin though). Thanks for this new shotwell.? With this patch I'll be able to test much more extensively by using shotwell as my main photo management application, now that I'm confident it won't overwrite this Caption field. So far I've only done limited testing but had no problems. --- shotwell/src/photos/PhotoMetadata.vala??? 2012-09-17 00:14:09.933142226 +0200 +++ shotwell-0.13-patched//src/photos/PhotoMetadata.vala??? 2012-09-15 22:25:22.126927218 +0200 @@ -800,7 +800,7 @@ ???? private const string IPHOTO_TITLE_TAG = "Iptc.Application2.ObjectName"; ???? ???? private static string[] STANDARD_TITLE_TAGS = { -??????? "Iptc.Application2.Caption", +//??????? "Iptc.Application2.Caption", ???????? "Xmp.dc.title", ???????? "Iptc.Application2.Headline", ???????? "Xmp.photoshop.Headline" De?: Adam Dingle ??: Luc More Cc?: "shotwell at lists.yorba.org" Envoy? le : Dimanche 16 septembre 2012 21h06 Objet?: Re: [Shotwell] Build error 0.13 Luc, The build was broken - sorry about that. ?I've just committed a fix, so you might want to try again. adam From joseph.bylund at gmail.com Mon Sep 17 17:53:05 2012 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Mon, 17 Sep 2012 13:53:05 -0400 Subject: [Shotwell] Build error 0.13 In-Reply-To: <505762a3.2230b60a.0418.ffffe428@mx.google.com> References: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> <1347836602.41295.YahooMailNeo@web122306.mail.ne1.yahoo.com> <505762a3.2230b60a.0418.ffffe428@mx.google.com> Message-ID: <50576381.4020500@gmail.com> Adam, Would it be possible to just pick one of the two conventions for local images, and then possibly reverse the convention on the exported photo depending on the target of the export? -Joe On 09/17/2012 01:49 PM, Adam Dingle wrote: > Luc, > > thanks for the patch. We've spent a fair amount of time at Yorba thinking about which metadata fields to write titles to. Unfortunately different programs use these fields in different ways. See the tables at > > http://redmine.yorba.org/projects/shotwell/wiki/PhotoTags > > If we don't write to Iptc.Application2.Caption, then some programs (most notably Picasa) will not be able to read titles exported from Shotwell. On the other hand, some Apple programs (iPhoto and Picasa) use Iptc.Application2.Caption to store descriptions, so as you pointed out we could clobber those when writing. I don't see any ideal solution here at the moment. > > We generated the tables on the wiki page above by testing various programs a couple of years ago. It would be interesting to refresh those tables to see if programs' behavior has changed. I really hope that different programs can converge on a single metadata tag for storing captions and another for descriptions. Xmp.dc.title and Xmp.dc.description would be good candidates for this. > > adam > > On Sun, Sep 16, 2012 at 4:03 PM, Luc More wrote: > Hi Adam, > > The new build worked fine, thanks for the quick reaction. > > Then I patched the following because I would like shotwell to leave the Caption tag alone when setting the Picure Title (I use Caption with other programs for a long description on some photos). Eventually I'd like shotwell to handle both fields but that would be a much heavier change. Initial testing shows that it works well in my workflow (e.g. Flickr Uploader can set both fields on my uploads -- not if I use shotwell's plugin though). > > Thanks for this new shotwell. With this patch I'll be able to test much more extensively by using shotwell as my main photo management application, now that I'm confident it won't overwrite this Caption field. > > So far I've only done limited testing but had no problems. > > > --- shotwell/src/photos/PhotoMetadata.vala 2012-09-17 00:14:09.933142226 +0200 > +++ shotwell-0.13-patched//src/photos/PhotoMetadata.vala 2012-09-15 22:25:22.126927218 +0200 > @@ -800,7 +800,7 @@ > private const string IPHOTO_TITLE_TAG = "Iptc.Application2.ObjectName"; > > private static string[] STANDARD_TITLE_TAGS = { > - "Iptc.Application2.Caption", > +// "Iptc.Application2.Caption", > "Xmp.dc.title", > "Iptc.Application2.Headline", > "Xmp.photoshop.Headline" > > De : Adam Dingle > ? : Luc More > Cc : "shotwell at lists.yorba.org" > Envoy? le : Dimanche 16 septembre 2012 21h06 > Objet : Re: [Shotwell] Build error 0.13 > > Luc, > > The build was broken - sorry about that. I've just committed a fix, so you might want to try again. > > adam > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From adam at yorba.org Mon Sep 17 17:59:39 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 17 Sep 2012 17:52:39 -0007 Subject: [Shotwell] Build error 0.13 In-Reply-To: <50576381.4020500@gmail.com> References: <1347756556.72614.YahooMailNeo@web122301.mail.ne1.yahoo.com> <1347836602.41295.YahooMailNeo@web122306.mail.ne1.yahoo.com> <505762a3.2230b60a.0418.ffffe428@mx.google.com> <50576381.4020500@gmail.com> Message-ID: <5057650e.ea0a3c0a.5d53.ffffdd3c@mx.google.com> Shotwell doesn't currently have a notion of an export target, i.e. exporting for a specific program such as Digikam or Picasa. ?We could conceivably add that, but it would be really nice if we could converge on a single convention that would work across all cooperating programs so that users wouldn't have to worry about that. adam On Mon, Sep 17, 2012 at 10:53 AM, Joseph Bylund wrote: Adam, Would it be possible to just pick one of the two conventions for local images, and then possibly reverse the convention on the exported photo depending on the target of the export? -Joe On 09/17/2012 01:49 PM, Adam Dingle wrote: > Luc, > > thanks for the patch. We've spent a fair amount of time at Yorba thinking about which metadata fields to write titles to. Unfortunately different programs use these fields in different ways. See the tables at > > http://redmine.yorba.org/projects/shotwell/wiki/PhotoTags > > If we don't write to Iptc.Application2.Caption, then some programs (most notably Picasa) will not be able to read titles exported from Shotwell. On the other hand, some Apple programs (iPhoto and Picasa) use Iptc.Application2.Caption to store descriptions, so as you pointed out we could clobber those when writing. I don't see any ideal solution here at the moment. > > We generated the tables on the wiki page above by testing various programs a couple of years ago. It would be interesting to refresh those tables to see if programs' behavior has changed. I really hope that different programs can converge on a single metadata tag for storing captions and another for descriptions. Xmp.dc.title and Xmp.dc.description would be good candidates for this. > > adam > > On Sun, Sep 16, 2012 at 4:03 PM, Luc More wrote: > Hi Adam, > > The new build worked fine, thanks for the quick reaction. > > Then I patched the following because I would like shotwell to leave the Caption tag alone when setting the Picure Title (I use Caption with other programs for a long description on some photos). Eventually I'd like shotwell to handle both fields but that would be a much heavier change. Initial testing shows that it works well in my workflow (e.g. Flickr Uploader can set both fields on my uploads -- not if I use shotwell's plugin though). > > Thanks for this new shotwell. With this patch I'll be able to test much more extensively by using shotwell as my main photo management application, now that I'm confident it won't overwrite this Caption field. > > So far I've only done limited testing but had no problems. > > > --- shotwell/src/photos/PhotoMetadata.vala 2012-09-17 00:14:09.933142226 +0200 > +++ shotwell-0.13-patched//src/photos/PhotoMetadata.vala 2012-09-15 22:25:22.126927218 +0200 > @@ -800,7 +800,7 @@ > private const string IPHOTO_TITLE_TAG = "Iptc.Application2.ObjectName"; > private static string[] STANDARD_TITLE_TAGS = { > - "Iptc.Application2.Caption", > +// "Iptc.Application2.Caption", > "Xmp.dc.title", > "Iptc.Application2.Headline", > "Xmp.photoshop.Headline" > > De : Adam Dingle > ? : Luc More > Cc : "shotwell at lists.yorba.org" > Envoy? le : Dimanche 16 septembre 2012 21h06 > Objet : Re: [Shotwell] Build error 0.13 > > Luc, > > The build was broken - sorry about that. I've just committed a fix, so you might want to try again. > > adam > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From rehmann at math.uni-bielefeld.de Mon Sep 17 18:07:54 2012 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Mon, 17 Sep 2012 20:07:54 +0200 Subject: [Shotwell] shotwell says: Failed to execute default File Manager Message-ID: <87wqzsikud.fsf@rhea.lan> I have some problem with shotwell which may or may not be a bug -- maybe somebody can immediately give some helpful hint: Everytime I click on the thumbnail for a video file (like *.avi or so) inside shotwell, I get a popup window saying "Failed to execute default File Manager. Failed to execute child process "Shotwell" (No such file or directory)." What can I do? I think a couple of months earlier this did not happen, instead, some video player would pop up playing the video. I have shotwell_0.12.90.orig installed and running on ubuntu 12.04. Thanks for any advice! From adam at yorba.org Mon Sep 17 18:09:44 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 17 Sep 2012 18:02:44 -0007 Subject: [Shotwell] shotwell says: Failed to execute default File Manager In-Reply-To: <87wqzsikud.fsf@rhea.lan> References: <87wqzsikud.fsf@rhea.lan> Message-ID: <5057676b.c4173c0a.3157.ffffea4a@mx.google.com> Ulf, what is your default video player set to? ?In other words, what happens if you double click on an *.avi file in Nautilus? adam On Mon, Sep 17, 2012 at 11:07 AM, Ulf Rehmann wrote: I have some problem with shotwell which may or may not be a bug -- maybe somebody can immediately give some helpful hint: Everytime I click on the thumbnail for a video file (like *.avi or so) inside shotwell, I get a popup window saying "Failed to execute default File Manager. Failed to execute child process "Shotwell" (No such file or directory)." What can I do? I think a couple of months earlier this did not happen, instead, some video player would pop up playing the video. I have shotwell_0.12.90.orig installed and running on ubuntu 12.04. Thanks for any advice! _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From adam at yorba.org Mon Sep 17 18:18:13 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 17 Sep 2012 18:11:13 -0007 Subject: [Shotwell] enhance->revert hides exif info In-Reply-To: <50572D5C.5080702@gmail.com> References: <5017E7D8.4080309@gmail.com> <50572D5C.5080702@gmail.com> Message-ID: <50576968.23bd440a.523b.78fc@mx.google.com> Joseph, for the upcoming 0.13 release we were hoping to make significant changes to Shotwell's RAW handling to clean up various bugs involving RAW and RAW+JPEG handling, but unfortunately we've run out of time and so that cleanup will have to wait for 0.14. ?See the tickets listed for 0.14 at http://redmine.yorba.org/projects/shotwell/issues?query_id=1 Regarding the problem you're seeing, I think that's probably a symptom of this bug: http://redmine.yorba.org/issues/4372 adam On Mon, Sep 17, 2012 at 7:02 AM, Joseph Bylund wrote: I've just tested this with the current 12.90+trunk build and I'm still seeing the same behavior (viewing a nef file and then returning to library view causes the exif info to disappear). Is this related to there being no exif info on upload? Is there an issue open for this, I didn't find it searching, but I wasn't sure which terms to use. -Joe On 08/08/2012 05:58 PM, Lucas Beeler wrote: > Hi Joseph, > > The NEF file here is the problem. This is a known issue with RAW file > handling in Shotwell that we hope to fix in the next release. > > Cheers, > Lucas _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From rehmann at math.uni-bielefeld.de Mon Sep 17 19:07:23 2012 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Mon, 17 Sep 2012 21:07:23 +0200 Subject: [Shotwell] shotwell says: Failed to execute default File Manager In-Reply-To: <5057676b.c4173c0a.3157.ffffea4a@mx.google.com> (message from Adam Dingle on Mon, 17 Sep 2012 18:02:44 -0007) Message-ID: <87sjagii38.fsf@rhea.lan> | what is your default video player set to? ?In other words, what | happens if you double click on an *.avi file in Nautilus? The file is played by Totem Movie Player 3.0.1. From adam at yorba.org Tue Sep 18 19:10:16 2012 From: adam at yorba.org (Adam Dingle) Date: Tue, 18 Sep 2012 19:03:16 -0007 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: References: Message-ID: <5058c718.2781440a.7ae8.230e@mx.google.com> On Sun, Sep 16, 2012 at 12:20 AM, Thomas Novin wrote: On Sat, Sep 15, 2012 at 4:00 AM, Lucas Beeler wrote: > With all these new features, we on the dev team could use your help > testing Shotwell 0.13. To test the latest code, you'll need to either > pull from Shotwell git master and build from source or, if you're on > Ubuntu, install a Shotwell daily build from the Shotwell Daily Builds > PPA. > Tried to but could not. $ sudo aptitude dist-upgrade The following packages will be upgraded: shotwell 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/8 081 kB of archives. After unpacking 1 383 kB will be freed. Do you want to continue? [Y/n/?] y dpkg: dependency problems prevent configuration of shotwell: shotwell depends on libgexiv2-0; however: Package libgexiv2-0 is not installed. dpkg: error processing shotwell (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already Errors were encountered while processing: shotwell E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: dpkg: dependency problems prevent configuration of shotwell: shotwell depends on libgexiv2-0; however: Package libgexiv2-0 is not installed. dpkg: error processing shotwell (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: shotwell This is on Ubuntu 12.04. I have a package called libgexiv2-1 but 2-0 isn't available.? This behavior is surprising, since currently Shotwell depends on libgexiv2-1, not 2-0. ?Which PPA(s) are you using as software sources? ?Are you sure that your package information is up to date? ?(If not, run 'sudo apt-get update' to update it.) ?What does 'apt-cache show shotwell' print? ? adam From gpopac at gmail.com Tue Sep 18 19:51:36 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, 18 Sep 2012 21:51:36 +0200 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <5058c718.2781440a.7ae8.230e@mx.google.com> References: <5058c718.2781440a.7ae8.230e@mx.google.com> Message-ID: <1347997896.773.19.camel@MeDjeD> When do you expect to fix all the iritating RAW+JPEG stuff? Is it possible to came with SW 0.14? Currently I have stop using Shotwell because my photo library looks like this after a while: img_3148.cr2 img_3148.jpg img_3148_cr2_embedded.jpg img_3148_cr2_embedded_1.jpg img_3148_cr2_shotwell.jpg If there is full resolution JPG file, why does the software creates embedd and shotwell files? By the way, I have tried 0.13. It works fine on Gentoo! Thumbnail creation is a great option :) Best regards, Milo? From adam at yorba.org Tue Sep 18 20:03:24 2012 From: adam at yorba.org (Adam Dingle) Date: Tue, 18 Sep 2012 19:56:24 -0007 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <1347997896.773.19.camel@MeDjeD> References: <5058c718.2781440a.7ae8.230e@mx.google.com> <1347997896.773.19.camel@MeDjeD> Message-ID: <5058d38e.63cb440a.75c7.2793@mx.google.com> On Tue, Sep 18, 2012 at 12:51 PM, ????? ??????? wrote: When do you expect to fix all the iritating RAW+JPEG stuff? Is it possible to came with SW 0.14? Yes, we would really like to fix Shotwell's RAW+JPEG handling for 0.14. ?We wanted to fix it for 0.13, but simply ran out of time. ?We've been very busy at Yorba getting Geary off the ground, plus doing contract work that keeps the company alive. ?:) Currently I have stop using Shotwell because my photo library looks like this after a while: img_3148.cr2 img_3148.jpg img_3148_cr2_embedded.jpg img_3148_cr2_embedded_1.jpg img_3148_cr2_shotwell.jpg If there is full resolution JPG file, why does the software creates embedd and shotwell files? You're right that in this situation those extra files should be unnecessary. adam From gpopac at gmail.com Tue Sep 18 21:25:16 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, 18 Sep 2012 23:25:16 +0200 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <5058d38e.63cb440a.75c7.2793@mx.google.com> References: <5058c718.2781440a.7ae8.230e@mx.google.com> <1347997896.773.19.camel@MeDjeD> <5058d38e.63cb440a.75c7.2793@mx.google.com> Message-ID: <1348003516.773.24.camel@MeDjeD> Adam, thank you for quick answers! > > If there is full resolution JPG file, why does the software creates > > embedd and shotwell files? > > You're right that in this situation those extra files should be > unnecessary. Strange, I did a bit more testing on an empty database file. Sometimes Shotwell creates xxx_cr2_shotwell.jpg and imports xxx.jpg as separate file, and other time it just couples xxx.cr2 with xxx.jpg. The files I was importing were inside the Shotwell?s photo directory. Best, Milo? From guerda at freenet.de Wed Sep 19 07:51:30 2012 From: guerda at freenet.de (=?UTF-8?B?UGhpbGlwIEdpbGxpw59lbg==?=) Date: Wed, 19 Sep 2012 09:51:30 +0200 Subject: [Shotwell] Shotwell Compile Dependencies Message-ID: Hi Shotwell list! I recently tried to compile shotwell from the source code bit it was quite tedious. As I could not find a complete list of all compile dependencies, I had to install every missing dependency one by one after trying to `make`. Is there such a list of compile dependencies available? Where can I find it? Thanks in advance! Kind regards, Philip --- E-Mail ist da wo du bist! Jetzt mit freenetMail ganz bequem auch unterwegs E-Mails verschicken. Am besten gleich informieren unter http://mail.freenet.de/mobile-email/index.html From mateusz at loskot.net Wed Sep 19 09:44:12 2012 From: mateusz at loskot.net (Mateusz Loskot) Date: Wed, 19 Sep 2012 10:44:12 +0100 Subject: [Shotwell] Shotwell Compile Dependencies In-Reply-To: References: Message-ID: On 19 September 2012 08:51, Philip Gilli?en wrote: > Hi Shotwell list! > > I recently tried to compile shotwell from the source code bit it was quite tedious. As I could not find a complete list of all compile dependencies, I had to install every missing dependency one by one after trying to `make`. > > Is there such a list of compile dependencies available? > Where can I find it? I build from Git using shotwell-git package for Arch Linux [1] Even if you don't use Arch, you can still find the list of depends helpful, just take a look at the PKGBUILD file [2] (depends property): [1] http://aur.archlinux.org/packages.php?ID=48503 [2] http://aur.archlinux.org/packages/sh/shotwell-git/PKGBUILD Best regards, -- Mateusz Loskot, http://mateusz.loskot.net From adam at yorba.org Wed Sep 19 12:38:35 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 12:31:35 -0007 Subject: [Shotwell] Shotwell Compile Dependencies In-Reply-To: References: Message-ID: <5059bccc.28bd440a.6f29.ffffaaf2@mx.google.com> On Wed, Sep 19, 2012 at 12:51 AM, Philip Gilli?en wrote: Hi Shotwell list! I recently tried to compile shotwell from the source code bit it was quite tedious. As I could not find a complete list of all compile dependencies, I had to install every missing dependency one by one after trying to `make`. Is there such a list of compile dependencies available? Where can I find it? Yes: http://yorba.org/shotwell/install.html Also, on most distros you can automatically install build dependencies since the package manager knows about them. ?For example, on Fedora: $ sudo yum-builddep shotwell On Ubuntu: $ sudo apt-get build-dep shotwell adam From farrukh.najm at gmail.com Wed Sep 19 12:56:31 2012 From: farrukh.najm at gmail.com (Farrukh Najmi) Date: Wed, 19 Sep 2012 08:56:31 -0400 Subject: [Shotwell] Building latest shotwell on Ubuntu 11.04 Message-ID: <5059C0FF.6050705@gmail.com> Hi Guys, I had upgraded to Shotwell 0.12.3 as a part of upgrade to Ubuntu 12.04. Later I ran into network drop problems in Ubuntu 12.04 and 11.10 that drove my productivity to near zero. So I reverted back to Ubuntu 11.04 and Shotwell 0.11.6. Now when I run shotwell I get: "Your photo library is not compatible with this version of Shotwell. It appears it was created by Shotwell 0.12.3 (schema 15). This version is 0.11.6 (schema 14). Please use the latest version of Shotwell." Is there a way to build latest shotwell on Ubuntu 11.04? Thanks for a great application and for a very helpful community. -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com From adam at yorba.org Wed Sep 19 13:21:32 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 13:14:32 -0007 Subject: [Shotwell] Building latest shotwell on Ubuntu 11.04 In-Reply-To: <5059C0FF.6050705@gmail.com> References: <5059C0FF.6050705@gmail.com> Message-ID: <5059c6de.e8ed440a.515a.ffffb8a9@mx.google.com> On Wed, Sep 19, 2012 at 5:56 AM, Farrukh Najmi wrote: Hi Guys, I had upgraded to Shotwell 0.12.3 as a part of upgrade to Ubuntu 12.04. Later I ran into network drop problems in Ubuntu 12.04 and 11.10 that drove my productivity to near zero. So I reverted back to Ubuntu 11.04 and Shotwell 0.11.6. Now when I run shotwell I get: "Your photo library is not compatible with this version of Shotwell. It appears it was created by Shotwell 0.12.3 (schema 15). This version is 0.11.6 (schema 14). Please use the latest version of Shotwell." Is there a way to build latest shotwell on Ubuntu 11.04? Not easily. ?Shotwell 0.12 depends on libraries found only in Ubuntu 11.10 and higher. ?Similarly, the upcoming Shotwell 0.13 (or the pre-release 0.12.90) depends on libraries found only in Ubuntu 12.04 and higher. By reverting back to an older Ubuntu you may not be able to run the latest versions of lots of useful programs. ?Instead, you could try upgrading to the development version of Ubuntu 12.10 (Quantal Quetzal). ?I've been running it every day for months now with few problems. ?If the network drop problems are still occurring there, you could file a bug report with Ubuntu. adam From scott_shotwell at dewie.net.au Wed Sep 19 14:02:22 2012 From: scott_shotwell at dewie.net.au (Scott Cove) Date: Thu, 20 Sep 2012 00:02:22 +1000 Subject: [Shotwell] Building latest shotwell on Ubuntu 11.04 In-Reply-To: <5059c6de.e8ed440a.515a.ffffb8a9@mx.google.com> References: <5059C0FF.6050705@gmail.com> <5059c6de.e8ed440a.515a.ffffb8a9@mx.google.com> Message-ID: <05915B95-E65C-487F-B51F-77BD5E8406C3@dewie.net.au> On a side note: Actually the network drop is a known issue with intel wireless N cards. I'm on mobile at the moment so unable to find bug but there is a known workaround to this, so long as you can put up with wireless G speeds only. Find the driver, or module, by using iwconfig - in my case I know I have the module iwlwifi. To disable wireless N to see if it fixes problem, type these into a terminal window: sudo rmmod iwlwifi (or whatever module is confit spits out) sudo modprobe iwlwifi 11n_disable=1 What I have done is made myself a simple bash script with those two lines so that when I connect to an N network I can disable it and run at G speeds without failure. Hope this helps, Scott Sent from my iPhone On 19/09/2012, at 11:21 PM, Adam Dingle wrote: > > > On Wed, Sep 19, 2012 at 5:56 AM, Farrukh Najmi wrote: > > Hi Guys, > > I had upgraded to Shotwell 0.12.3 as a part of upgrade to Ubuntu 12.04. Later I ran into network drop problems in Ubuntu 12.04 and 11.10 that drove my productivity to near zero. So I reverted back to Ubuntu 11.04 and Shotwell 0.11.6. > > Now when I run shotwell I get: > > "Your photo library is not compatible with this version of Shotwell. It appears it was created by Shotwell 0.12.3 (schema 15). This version is 0.11.6 (schema 14). Please use the latest version of Shotwell." > > Is there a way to build latest shotwell on Ubuntu 11.04? > > Not easily. Shotwell 0.12 depends on libraries found only in Ubuntu 11.10 and higher. Similarly, the upcoming Shotwell 0.13 (or the pre-release 0.12.90) depends on libraries found only in Ubuntu 12.04 and higher. > > By reverting back to an older Ubuntu you may not be able to run the latest versions of lots of useful programs. Instead, you could try upgrading to the development version of Ubuntu 12.10 (Quantal Quetzal). I've been running it every day for months now with few problems. If the network drop problems are still occurring there, you could file a bug report with Ubuntu. > > adam > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From adam at yorba.org Wed Sep 19 14:08:21 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 14:01:21 -0007 Subject: [Shotwell] Building latest shotwell on Ubuntu 11.04 In-Reply-To: <05915B95-E65C-487F-B51F-77BD5E8406C3@dewie.net.au> References: <5059C0FF.6050705@gmail.com> <5059c6de.e8ed440a.515a.ffffb8a9@mx.google.com> <05915B95-E65C-487F-B51F-77BD5E8406C3@dewie.net.au> Message-ID: <5059d1d7.844d420a.1761.4af9@mx.google.com> Looks like the wireless drop bug is here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/911059 That bug report claims this was fixed late in the 12.04 release cycle. ?I'd suggest trying either 12.04 with all software updates applied, or the development version of 12.10. adam On Wed, Sep 19, 2012 at 7:02 AM, Scott Cove wrote: On a side note: Actually the network drop is a known issue with intel wireless N cards. I'm on mobile at the moment so unable to find bug but there is a known workaround to this, so long as you can put up with wireless G speeds only. Find the driver, or module, by using iwconfig - in my case I know I have the module iwlwifi. To disable wireless N to see if it fixes problem, type these into a terminal window: sudo rmmod iwlwifi (or whatever module is confit spits out) sudo modprobe iwlwifi 11n_disable=1 What I have done is made myself a simple bash script with those two lines so that when I connect to an N network I can disable it and run at G speeds without failure. Hope this helps, Scott Sent from my iPhone On 19/09/2012, at 11:21 PM, Adam Dingle wrote: > > > On Wed, Sep 19, 2012 at 5:56 AM, Farrukh Najmi wrote: > > Hi Guys, > > I had upgraded to Shotwell 0.12.3 as a part of upgrade to Ubuntu 12.04. Later I ran into network drop problems in Ubuntu 12.04 and 11.10 that drove my productivity to near zero. So I reverted back to Ubuntu 11.04 and Shotwell 0.11.6. > > Now when I run shotwell I get: > > "Your photo library is not compatible with this version of Shotwell. It appears it was created by Shotwell 0.12.3 (schema 15). This version is 0.11.6 (schema 14). Please use the latest version of Shotwell." > > Is there a way to build latest shotwell on Ubuntu 11.04? > > Not easily. Shotwell 0.12 depends on libraries found only in Ubuntu 11.10 and higher. Similarly, the upcoming Shotwell 0.13 (or the pre-release 0.12.90) depends on libraries found only in Ubuntu 12.04 and higher. > > By reverting back to an older Ubuntu you may not be able to run the latest versions of lots of useful programs. Instead, you could try upgrading to the development version of Ubuntu 12.10 (Quantal Quetzal). I've been running it every day for months now with few problems. If the network drop problems are still occurring there, you could file a bug report with Ubuntu. > > adam > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From scott_shotwell at dewie.net.au Wed Sep 19 14:13:09 2012 From: scott_shotwell at dewie.net.au (Scott Cove) Date: Thu, 20 Sep 2012 00:13:09 +1000 Subject: [Shotwell] Building latest shotwell on Ubuntu 11.04 In-Reply-To: <5059d1d7.844d420a.1761.4af9@mx.google.com> References: <5059C0FF.6050705@gmail.com> <5059c6de.e8ed440a.515a.ffffb8a9@mx.google.com> <05915B95-E65C-487F-B51F-77BD5E8406C3@dewie.net.au> <5059d1d7.844d420a.1761.4af9@mx.google.com> Message-ID: Definitely not fixed in 12.04 - even with all updates. Given all the crash reports I have been getting from 12.04 I might even try the dev version of quantal myself. Thanks for finding bug report though :) Scott. Sent from my iPhone On 20/09/2012, at 12:08 AM, Adam Dingle wrote: > Looks like the wireless drop bug is here: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/911059 > > That bug report claims this was fixed late in the 12.04 release cycle. I'd suggest trying either 12.04 with all software updates applied, or the development version of 12.10. > > adam > > On Wed, Sep 19, 2012 at 7:02 AM, Scott Cove wrote: >> On a side note: >> >> Actually the network drop is a known issue with intel wireless N cards. I'm on mobile at the moment so unable to find bug but there is a known workaround to this, so long as you can put up with wireless G speeds only. >> >> Find the driver, or module, by using iwconfig - in my case I know I have the module iwlwifi. >> >> To disable wireless N to see if it fixes problem, type these into a terminal window: >> >> sudo rmmod iwlwifi (or whatever module is confit spits out) >> sudo modprobe iwlwifi 11n_disable=1 >> >> What I have done is made myself a simple bash script with those two lines so that when I connect to an N network I can disable it and run at G speeds without failure. >> >> Hope this helps, >> >> Scott >> >> Sent from my iPhone >> >> On 19/09/2012, at 11:21 PM, Adam Dingle wrote: >> >> > >> > >> > On Wed, Sep 19, 2012 at 5:56 AM, Farrukh Najmi wrote: >> > >> > Hi Guys, >> > >> > I had upgraded to Shotwell 0.12.3 as a part of upgrade to Ubuntu 12.04. Later I ran into network drop problems in Ubuntu 12.04 and 11.10 that drove my productivity to near zero. So I reverted back to Ubuntu 11.04 and Shotwell 0.11.6. >> > >> > Now when I run shotwell I get: >> > >> > "Your photo library is not compatible with this version of Shotwell. It appears it was created by Shotwell 0.12.3 (schema 15). This version is 0.11.6 (schema 14). Please use the latest version of Shotwell." >> > >> > Is there a way to build latest shotwell on Ubuntu 11.04? >> > >> > Not easily. Shotwell 0.12 depends on libraries found only in Ubuntu 11.10 and higher. Similarly, the upcoming Shotwell 0.13 (or the pre-release 0.12.90) depends on libraries found only in Ubuntu 12.04 and higher. >> > >> > By reverting back to an older Ubuntu you may not be able to run the latest versions of lots of useful programs. Instead, you could try upgrading to the development version of Ubuntu 12.10 (Quantal Quetzal). I've been running it every day for months now with few problems. If the network drop problems are still occurring there, you could file a bug report with Ubuntu. >> > >> > adam >> > _______________________________________________ >> > Shotwell mailing list >> > Shotwell at lists.yorba.org >> > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From spacemen12 at yahoo.com Wed Sep 19 15:24:21 2012 From: spacemen12 at yahoo.com (Xavier Thibert) Date: Wed, 19 Sep 2012 08:24:21 -0700 (PDT) Subject: [Shotwell] Delete only Raw, keep tag on JPEG of Raw + JPEG pair Message-ID: <1348068261.3428.YahooMailNeo@web31809.mail.mud.yahoo.com> Hi, ? ? I want to delete the RAW of a RAW + JPEG pair and keep the tag that I put in. I have multiple pairs of file on which I want to do this operation.? The problem is linked to several known issue: Adding a tag to a RAW+JPEG image with metadata writing enabled has no effect. (http://redmine.yorba.org/issues/4156) How to remove only RAW or only JPEG from database and disk? (http://lists.yorba.org/pipermail/shotwell/2012-May/003922.html) RAW files in RAW+JPEG pairs aren't properly deleted (http://redmine.yorba.org/issues/4207) ? ?Does anyone found a work around this issue? If I remove from library -> manually delete the raw files -> re-import the left over JPEG, I will loose the tag Any help would be appreciated. Best regards, From gpopac at gmail.com Wed Sep 19 15:56:08 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: Wed, 19 Sep 2012 17:56:08 +0200 Subject: [Shotwell] Idea for RAW+JPG Message-ID: <1348070168.13084.5.camel@MeDjeD> Here is the proposal: 1. Shotwell could scan library for xxx.raw photos containing xxx_raw_shotwell.jpg (or _embedded.jpg). 2. If there is xxx.jpg delete xxx_raw_shotwell.jpg and assign JPG to RAW. 3. Remove xxx.jpg from library. Transfer metadata from xxx.jpg to xxx.raw. It could be a quick solution for all of my problems at least :) Best regards, Milo? From farrukh.najm at gmail.com Wed Sep 19 16:13:21 2012 From: farrukh.najm at gmail.com (Farrukh Najmi) Date: Wed, 19 Sep 2012 12:13:21 -0400 Subject: [Shotwell] Building latest shotwell on Ubuntu 11.04 In-Reply-To: References: <5059C0FF.6050705@gmail.com> <5059c6de.e8ed440a.515a.ffffb8a9@mx.google.com> <05915B95-E65C-487F-B51F-77BD5E8406C3@dewie.net.au> <5059d1d7.844d420a.1761.4af9@mx.google.com> Message-ID: <5059EF21.7080905@gmail.com> Adam, Scott, you guys are the most thoughtful and helpful even when my issue was not directly Shotwell related. I have upgraded to 11.10 (as first step) and so far my wired connection is working. My original network drop issue was with both wired and wireless. So the immediate Shotwell issue is solved and I have my precious image library back. Thanks again. I really love and evangelize Shotwell already but now I will do the same for the Shotwell community :-) On 09/19/2012 10:13 AM, Scott Cove wrote: > Definitely not fixed in 12.04 - even with all updates. > > Given all the crash reports I have been getting from 12.04 I might > even try the dev version of quantal myself. > > Thanks for finding bug report though :) > > Scott. > > Sent from my iPhone > > On 20/09/2012, at 12:08 AM, Adam Dingle > wrote: > >> Looks like the wireless drop bug is here: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/911059 >> >> That bug report claims this was fixed late in the 12.04 release >> cycle. I'd suggest trying either 12.04 with all software updates >> applied, or the development version of 12.10. >> >> adam >> >> On Wed, Sep 19, 2012 at 7:02 AM, Scott Cove >> > wrote: >>> On a side note: >>> >>> Actually the network drop is a known issue with intel wireless N >>> cards. I'm on mobile at the moment so unable to find bug but there >>> is a known workaround to this, so long as you can put up with >>> wireless G speeds only. >>> >>> Find the driver, or module, by using iwconfig - in my case I know I >>> have the module iwlwifi. >>> >>> To disable wireless N to see if it fixes problem, type these into a >>> terminal window: >>> >>> sudo rmmod iwlwifi (or whatever module is confit spits out) >>> sudo modprobe iwlwifi 11n_disable=1 >>> >>> What I have done is made myself a simple bash script with those two >>> lines so that when I connect to an N network I can disable it and >>> run at G speeds without failure. >>> >>> Hope this helps, >>> >>> Scott >>> >>> Sent from my iPhone >>> >>> On 19/09/2012, at 11:21 PM, Adam Dingle wrote: >>> >>> > >>> > >>> > On Wed, Sep 19, 2012 at 5:56 AM, Farrukh Najmi wrote: >>> > >>> > Hi Guys, >>> > >>> > I had upgraded to Shotwell 0.12.3 as a part of upgrade to Ubuntu >>> 12.04. Later I ran into network drop problems in Ubuntu 12.04 and >>> 11.10 that drove my productivity to near zero. So I reverted back to >>> Ubuntu 11.04 and Shotwell 0.11.6. >>> > >>> > Now when I run shotwell I get: >>> > >>> > "Your photo library is not compatible with this version of >>> Shotwell. It appears it was created by Shotwell 0.12.3 (schema 15). >>> This version is 0.11.6 (schema 14). Please use the latest version of >>> Shotwell." >>> > >>> > Is there a way to build latest shotwell on Ubuntu 11.04? >>> > >>> > Not easily. Shotwell 0.12 depends on libraries found only in >>> Ubuntu 11.10 and higher. Similarly, the upcoming Shotwell 0.13 (or >>> the pre-release 0.12.90) depends on libraries found only in Ubuntu >>> 12.04 and higher. >>> > >>> > By reverting back to an older Ubuntu you may not be able to run >>> the latest versions of lots of useful programs. Instead, you could >>> try upgrading to the development version of Ubuntu 12.10 (Quantal >>> Quetzal). I've been running it every day for months now with few >>> problems. If the network drop problems are still occurring there, >>> you could file a bug report with Ubuntu. >>> > >>> > adam >>> > _______________________________________________ >>> > Shotwell mailing list >>> > Shotwell at lists.yorba.org >>> > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> From thomas at xyz.pp.se Wed Sep 19 16:49:40 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Wed, 19 Sep 2012 18:49:40 +0200 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <5058c718.2781440a.7ae8.230e@mx.google.com> References: <5058c718.2781440a.7ae8.230e@mx.google.com> Message-ID: On Tue, Sep 18, 2012 at 9:10 PM, Adam Dingle wrote: > This is on Ubuntu 12.04. I have a package called libgexiv2-1 but 2-0 > isn't available. > > > This behavior is surprising, since currently Shotwell depends on > libgexiv2-1, not 2-0. Which PPA(s) are you using as software sources? Are > you sure that your package information is up to date? (If not, run 'sudo > apt-get update' to update it.) What does 'apt-cache show shotwell' print? > It was like this; first I wanted to install it without adding the ppa, so I just downloaded the deb-file. I took the wrong version, I got oneiric. Then after failing the install I added the ppa and the correct version (precise) was tried to be installed but I still got the same error. Now did apt-get remove shotwell & then again apt-get install shotwell and then it all worked. Rgds From thomas at xyz.pp.se Wed Sep 19 19:18:22 2012 From: thomas at xyz.pp.se (Thomas Novin) Date: Wed, 19 Sep 2012 21:18:22 +0200 Subject: [Shotwell] Two issues with 0.12.90+2225~precise1 Message-ID: 1. Got this when starting: /usr/bin/shotwell-settings-migrator: 24: /usr/bin/shotwell-settings-migrator: dconf: not found /usr/bin/shotwell-settings-migrator: 27: /usr/bin/shotwell-settings-migrator: dconf: not found 2. Got this when exiting ** ERROR:/build/buildd/shotwell-0.12.90+2225~precise1/src/db/DatabaseTable.vala:190:database_table_prepare_update_by_id: assertion failed: (res == Sqlite.OK) bin/shotwell: line 22: 3271 Aborted (core dumped) /usr/bin/shotwell The core dump is here: https://dl.dropbox.com/u/2387311/_usr_bin_shotwell.1000.crash Rgds From maxxer at ufficyo.com Wed Sep 19 19:32:32 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Wed, 19 Sep 2012 21:32:32 +0200 (CEST) Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: Message-ID: <1042004068.17421.1348083151837.JavaMail.root@yetopen.it> > For Ubuntu users, the Shotwell daily builds PPA is located here: > https://launchpad.net/~yorba/+archive/daily-builds Tried to install now on ubuntu 12.04 but complains about unresolved dep with libunity (>= 5.10.0). But that package doesn't seem to exist: http://packages.ubuntu.com/search?keywords=libunity -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From maxxer at ufficyo.com Wed Sep 19 19:34:07 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Wed, 19 Sep 2012 21:34:07 +0200 (CEST) Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <1042004068.17421.1348083151837.JavaMail.root@yetopen.it> Message-ID: <1584948918.17470.1348083247722.JavaMail.root@yetopen.it> > Tried to install now on ubuntu 12.04 but complains about unresolved > dep with libunity (>= 5.10.0). For the record I'm using XFCE, I hope that shotwell won't forcely need unity :-) -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From adam at yorba.org Wed Sep 19 19:45:20 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 19:38:20 -0007 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <1042004068.17421.1348083151837.JavaMail.root@yetopen.it> References: <1042004068.17421.1348083151837.JavaMail.root@yetopen.it> Message-ID: <505a20d1.0487440a.3309.ffffd9c1@mx.google.com> On Wed, Sep 19, 2012 at 12:32 PM, Lorenzo Milesi wrote: > For Ubuntu users, the Shotwell daily builds PPA is located here: > https://launchpad.net/~yorba/+archive/daily-builds Tried to install now on ubuntu 12.04 but complains about unresolved dep with libunity (>= 5.10.0). But that package doesn't seem to exist: http://packages.ubuntu.com/search?keywords=libunity Thanks for bringing this to our attention. ?We'll fix this before the 0.13 release: http://redmine.yorba.org/issues/5851 adam From maxxer at ufficyo.com Wed Sep 19 19:50:24 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Wed, 19 Sep 2012 21:50:24 +0200 (CEST) Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <505a20d1.0487440a.3309.ffffd9c1@mx.google.com> Message-ID: <880947449.17622.1348084224017.JavaMail.root@yetopen.it> > Thanks for bringing this to our attention. We'll fix this before the > 0.13 release: Can I wait (shortly) or should I build from source for testing? ;) -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From adam at yorba.org Wed Sep 19 19:52:14 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 19:45:14 -0007 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <1584948918.17470.1348083247722.JavaMail.root@yetopen.it> References: <1584948918.17470.1348083247722.JavaMail.root@yetopen.it> Message-ID: <505a2270.488a440a.1fae.ffffddd2@mx.google.com> On Wed, Sep 19, 2012 at 12:34 PM, Lorenzo Milesi wrote: > Tried to install now on ubuntu 12.04 but complains about unresolved > dep with libunity (>= 5.10.0). For the record I'm using XFCE, I hope that shotwell won't forcely need unity :-) For this release, we've decided to build Shotwell in the Yorba PPA with Unity support enabled (just like the prebuilt Shotwell package from Ubuntu). ?This allows Shotwell to display a progress bar in the Unity launcher. ?This means that Shotwell will depend on libunity (the actual package name is something like libunity9). ?I think it won't do any harm to install that library even if you're running XFCE. ?If you really want Shotwell without this dependency, you can always build it yourself without the --unity-support flag. adam From adam at yorba.org Wed Sep 19 19:53:16 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 19:46:16 -0007 Subject: [Shotwell] Shotwell 0.13: Call for Testing In-Reply-To: <880947449.17622.1348084224017.JavaMail.root@yetopen.it> References: <880947449.17622.1348084224017.JavaMail.root@yetopen.it> Message-ID: <505a22ad.a4dd440a.5106.ffffd9ad@mx.google.com> On Wed, Sep 19, 2012 at 12:50 PM, Lorenzo Milesi wrote: > Thanks for bringing this to our attention. We'll fix this before the > 0.13 release: Can I wait (shortly) or should I build from source for testing? ;) We should have this fixed in the Yorba daily PPA within a day or so. If you want it sooner, you can build from source. :) adam From adam at yorba.org Wed Sep 19 20:02:41 2012 From: adam at yorba.org (Adam Dingle) Date: Wed, 19 Sep 2012 19:55:41 -0007 Subject: [Shotwell] Two issues with 0.12.90+2225~precise1 In-Reply-To: References: Message-ID: <505a24e3.c6d9440a.47fa.ffffdfcd@mx.google.com> On Wed, Sep 19, 2012 at 12:18 PM, Thomas Novin wrote: 1. Got this when starting: /usr/bin/shotwell-settings-migrator: 24: /usr/bin/shotwell-settings-migrator: dconf: not found /usr/bin/shotwell-settings-migrator: 27: /usr/bin/shotwell-settings-migrator: dconf: not found You need to install the dconf-tools package to get the dconf binary. ?Evidently we need to add a dependency to that package: http://redmine.yorba.org/issues/5853 2. Got this when exiting ** ERROR:/build/buildd/shotwell-0.12.90+2225~precise1/src/db/DatabaseTable.vala:190:database_table_prepare_update_by_id: assertion failed: (res == Sqlite.OK) bin/shotwell: line 22: 3271 Aborted (core dumped) /usr/bin/shotwell The core dump is here: https://dl.dropbox.com/u/2387311/_usr_bin_shotwell.1000.crash Sigh. ?That's a bug which people have reported from time to time, but we're as yet unable to reproduce at Yorba: http://redmine.yorba.org/issues/5071 adam From clinton at yorba.org Thu Sep 20 01:14:01 2012 From: clinton at yorba.org (Clinton Rogers) Date: Wed, 19 Sep 2012 18:14:01 -0700 Subject: [Shotwell] Shotwell 0.13.0 Released Message-ID: Good evening, one and all, We're pleased to announce the release of Shotwell version 0.13, available at the following URL: http://www.yorba.org/download/shotwell/0.13/shotwell-0.13.0.tar.xz Among the many enhancements and fixes since 0.12: * Shotwell now has the ability to publish to Tumblr * Shotwell correctly handles dates before 1969 * Shotwell lets you remove sensitive information from photos before publishing them to social media sites * Shotwell now uses GtkApplication * Shotwell regenerates thumbnails automatically, making migrating libraries between computers easier * The Picasa connector now uses OAuth authentication for enhanced security If you have any questions regarding this release, please feel free to respond to this message, and either I or another member of the Shotwell team will respond as soon as we can, and - as always - thank you for using Shotwell! Cheers, -c From maxxer at ufficyo.com Fri Sep 21 05:09:11 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Fri, 21 Sep 2012 07:09:11 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <1104737490.34913.1348203818244.JavaMail.root@yetopen.it> Message-ID: <120002449.34982.1348204151569.JavaMail.root@yetopen.it> I'm still trying to import my large_fspot_collection :) now I've a dedicated PC running it, with ubuntu 12 and shotwell 0.13 The import run for several hours, then hangs. I tried running thru gdb but there's no crash, it just running. top says shotwell is still at 100%, but there's no message in log since 3h. I'm attaching full shotwell.log and shotwell.gdb. I ran this procedure twice, and both times hung on: L 10484 2012-09-21 04:57:22 [DBG] DataImportsUI.vala:411: DataImportsDialog: install_pane( ): invoked. L 10484 2012-09-21 04:57:22 [DBG] DataImportsUI.vala:414: DataImportsDialog: install_pane( ): a pane is already installed; removing it. help appreciated, thanks! -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From maxxer at ufficyo.com Fri Sep 21 05:16:32 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Fri, 21 Sep 2012 07:16:32 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <120002449.34982.1348204151569.JavaMail.root@yetopen.it> Message-ID: <890684218.34998.1348204592717.JavaMail.root@yetopen.it> > I'm attaching full shotwell.log and shotwell.gdb. I ran this > procedure twice, and both times hung on: Since the ml stripped the attachments, here they are: http://dl.dropbox.com/u/706934/shotwell.log.gz http://dl.dropbox.com/u/706934/shotwell.gdb.gz -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From maxxer at ufficyo.com Fri Sep 21 19:22:55 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Fri, 21 Sep 2012 21:22:55 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <120002449.34982.1348204151569.JavaMail.root@yetopen.it> Message-ID: <80157550.43915.1348255375127.JavaMail.root@yetopen.it> > L 10484 2012-09-21 04:57:22 [DBG] DataImportsUI.vala:411: > DataImportsDialog: install_pane( ): invoked. > L 10484 2012-09-21 04:57:22 [DBG] DataImportsUI.vala:414: > DataImportsDialog: install_pane( ): a pane is already installed; > removing it. if it can be useful I did a CTRL+C (since it's stuck in the same point since at last 12h) and what I got from gdb is this: [New Thread 0xac105b40 (LWP 11604)] [Thread 0xaf129b40 (LWP 11602) exited] [New Thread 0xaf129b40 (LWP 11605)] [Thread 0xac105b40 (LWP 11604) exited] [New Thread 0xac105b40 (LWP 11606)] [Thread 0xaf129b40 (LWP 11605) exited] [New Thread 0xaf129b40 (LWP 11607)] [Thread 0xaf129b40 (LWP 11607) exited] [New Thread 0xaf129b40 (LWP 11608)] [Thread 0xac105b40 (LWP 11606) exited] [New Thread 0xac105b40 (LWP 11609)] [Thread 0xac105b40 (LWP 11609) exited] [Thread 0xaf129b40 (LWP 11608) exited] [New Thread 0xaf129b40 (LWP 11625)] [New Thread 0xac105b40 (LWP 11626)] [Thread 0xaf129b40 (LWP 11625) exited] [New Thread 0xaf129b40 (LWP 11627)] [Thread 0xaf129b40 (LWP 11627) exited] [Thread 0xac105b40 (LWP 11626) exited] [New Thread 0xac105b40 (LWP 11641)] [New Thread 0xaf129b40 (LWP 11642)] [Thread 0xaf129b40 (LWP 11642) exited] [New Thread 0xaf129b40 (LWP 11643)] [Thread 0xac105b40 (LWP 11641) exited] [New Thread 0xac105b40 (LWP 11644)] [Thread 0xac105b40 (LWP 11644) exited] [Thread 0xaf129b40 (LWP 11643) exited] [New Thread 0xaf129b40 (LWP 11648)] [New Thread 0xac105b40 (LWP 11649)] [Thread 0xac105b40 (LWP 11649) exited] [New Thread 0xac105b40 (LWP 11650)] [Thread 0xaf129b40 (LWP 11648) exited] [New Thread 0xaf129b40 (LWP 11651)] [Thread 0xaf129b40 (LWP 11651) exited] [New Thread 0xaf129b40 (LWP 11652)] [Thread 0xaf129b40 (LWP 11652) exited] [Thread 0xac105b40 (LWP 11650) exited] [New Thread 0xac105b40 (LWP 11695)] [New Thread 0xaf129b40 (LWP 11696)] [Thread 0xaf129b40 (LWP 11696) exited] [New Thread 0xaf129b40 (LWP 11697)] [Thread 0xaf129b40 (LWP 11697) exited] [New Thread 0xaf129b40 (LWP 11698)] [Thread 0xaf129b40 (LWP 11698) exited] [Thread 0xac105b40 (LWP 11695) exited] [New Thread 0xac105b40 (LWP 11699)] [New Thread 0xaf129b40 (LWP 11700)] [Thread 0xaf129b40 (LWP 11700) exited] [New Thread 0xaf129b40 (LWP 11701)] [Thread 0xac105b40 (LWP 11699) exited] [New Thread 0xac105b40 (LWP 11702)] [Thread 0xac105b40 (LWP 11702) exited] [New Thread 0xac105b40 (LWP 11703)] [Thread 0xac105b40 (LWP 11703) exited] [Thread 0xaf129b40 (LWP 11701) exited] [New Thread 0xaf129b40 (LWP 11704)] [New Thread 0xac105b40 (LWP 11705)] [Thread 0xac105b40 (LWP 11705) exited] [New Thread 0xac105b40 (LWP 11706)] [Thread 0xac105b40 (LWP 11706) exited] [New Thread 0xac105b40 (LWP 11707)] [Thread 0xac105b40 (LWP 11707) exited] [New Thread 0xac105b40 (LWP 11708)] [Thread 0xac105b40 (LWP 11708) exited] [New Thread 0xac105b40 (LWP 11709)] [Thread 0xaf129b40 (LWP 11704) exited] [Thread 0xac105b40 (LWP 11709) exited] [New Thread 0xac105b40 (LWP 11712)] [New Thread 0xaf129b40 (LWP 11713)] [Thread 0xaf129b40 (LWP 11713) exited] [New Thread 0xaf129b40 (LWP 11714)] [Thread 0xaf129b40 (LWP 11714) exited] [New Thread 0xaf129b40 (LWP 11715)] [Thread 0xaf129b40 (LWP 11715) exited] [New Thread 0xaf129b40 (LWP 11716)] [Thread 0xaf129b40 (LWP 11716) exited] [New Thread 0xaf129b40 (LWP 11717)] [Thread 0xaf129b40 (LWP 11717) exited] [Thread 0xac105b40 (LWP 11712) exited] [New Thread 0xac105b40 (LWP 11728)] [New Thread 0xaf129b40 (LWP 11729)] [Thread 0xaf129b40 (LWP 11729) exited] [Thread 0xac105b40 (LWP 11728) exited] [New Thread 0xac105b40 (LWP 11730)] [New Thread 0xaf129b40 (LWP 11731)] [Thread 0xaf129b40 (LWP 11731) exited] [Thread 0xac105b40 (LWP 11730) exited] Program received signal SIGINT, Interrupt. 0xb75542e0 in ?? () from /usr/lib/i386-linux-gnu/libgee.so.2 now after a "continue" shotwell still runs 100% cpu -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From brunogirin at gmail.com Fri Sep 21 20:36:52 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Fri, 21 Sep 2012 21:36:52 +0100 Subject: [Shotwell] f-spot import hangs In-Reply-To: <890684218.34998.1348204592717.JavaMail.root@yetopen.it> References: <890684218.34998.1348204592717.JavaMail.root@yetopen.it> Message-ID: <505CCFE4.7010808@gmail.com> On 21/09/12 06:16, Lorenzo Milesi wrote: >> I'm attaching full shotwell.log and shotwell.gdb. I ran this >> procedure twice, and both times hung on: > Since the ml stripped the attachments, here they are: > http://dl.dropbox.com/u/706934/shotwell.log.gz > http://dl.dropbox.com/u/706934/shotwell.gdb.gz Lorenzo, Looking at your logs, it looks like the import had been processing a large number of photos and was about to update the progress dialog (hence the messages about installing and removing panes) when it hung. The gdb output shows that it had been regularly creating and exiting pools of threads, which seems to indicate that it was happily creating and processing jobs in the import queue. So I suspect it's probably run out of some resource or other. To find out why, the import would need to be tested through valgrind. Unfortunately I won't have time to do that at the moment. If you fancy giving it a go, have a look at the quick start guide: http://valgrind.org/docs/manual/QuickStart.html For further reference, I did that a couple of years ago with the initial F-Spot import, using the "massif" tool in valgrind: http://redmine.yorba.org/issues/2334 Full valgrind docs can be found here: http://valgrind.org/docs/manual/manual.html Cheers, Bruno From maxxer at ufficyo.com Sat Sep 22 22:09:42 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Sun, 23 Sep 2012 00:09:42 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <505CCFE4.7010808@gmail.com> Message-ID: <695888143.58030.1348351782197.JavaMail.root@yetopen.it> > For further reference, I did that a couple of years ago with the > initial > F-Spot import, using the "massif" tool in valgrind: > http://redmine.yorba.org/issues/2334 I tried running valgrind --tool=massif shotwell, it's running for 24h at least, but massif output is very short: http://dl.dropbox.com/u/706934/massif.out.13520.gz now looks hung -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From brunogirin at gmail.com Sun Sep 23 16:37:31 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Sun, 23 Sep 2012 17:37:31 +0100 Subject: [Shotwell] f-spot import hangs In-Reply-To: <695888143.58030.1348351782197.JavaMail.root@yetopen.it> References: <695888143.58030.1348351782197.JavaMail.root@yetopen.it> Message-ID: <505F3ACB.7000701@gmail.com> On 22/09/12 23:09, Lorenzo Milesi wrote: >> For further reference, I did that a couple of years ago with the >> initial >> F-Spot import, using the "massif" tool in valgrind: >> http://redmine.yorba.org/issues/2334 > I tried running valgrind --tool=massif shotwell, it's running for 24h at least, but massif output is very short: > http://dl.dropbox.com/u/706934/massif.out.13520.gz > now looks hung Lorenzo, Are you sure you uploaded the file correctly? It claims it's 0 bytes when I download it. The massif output doesn't have to be huge but it should be more than 0 bytes :-) Bruno From maxxer at ufficyo.com Mon Sep 24 17:22:09 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Mon, 24 Sep 2012 19:22:09 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <505F3ACB.7000701@gmail.com> Message-ID: <504163250.72646.1348507329003.JavaMail.root@yetopen.it> > Are you sure you uploaded the file correctly? It claims it's 0 bytes > when I download it. The massif output doesn't have to be huge but it > should be more than 0 bytes :-) ups, something went wrong during the upload. this should work! http://dl.dropbox.com/u/706934/massif.out.13520.gz -- Lorenzo Milesi - lorenzo.milesi at yetopen.it YetOpen S.r.l. - http://www.yetopen.it/ Via Carlo Torri Tarelli 19 - 23900 Lecco - ITALY - Tel 0341 220 205 - Fax 178 6070 222 GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it -------- D.Lgs. 196/2003 -------- Si avverte che tutte le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Nel caso in cui questo messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena possibile. Grazie. -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From dave at dawoodfall.net Mon Sep 24 22:22:23 2012 From: dave at dawoodfall.net (David Woodfall) Date: Mon, 24 Sep 2012 23:22:23 +0100 Subject: [Shotwell] Idea maybe Feature Req for more external editors or at least external printer Message-ID: <20120924222223.GA15393@Junius> I would like to be able to use Photo Print to print, which I can do if I create a .desktop file for it and select it in external editors. Problem is that I'm having to swap back and forth between GIMP and Photo Print, which slows down the workflow. So may I put in a feature request for some more external editors or maybe an external printer command? I can only see it as an advantage. Cheers David From adam at yorba.org Mon Sep 24 23:18:52 2012 From: adam at yorba.org (Adam Dingle) Date: Mon, 24 Sep 2012 23:11:52 -0007 Subject: [Shotwell] Idea maybe Feature Req for more external editors or at least external printer In-Reply-To: <20120924222223.GA15393@Junius> References: <20120924222223.GA15393@Junius> Message-ID: <5060ea5d.c44a420a.2448.18d8@mx.google.com> On Mon, Sep 24, 2012 at 3:22 PM, David Woodfall wrote: I would like to be able to use Photo Print to print, which I can do if I create a .desktop file for it and select it in external editors. Problem is that I'm having to swap back and forth between GIMP and Photo Print, which slows down the workflow. So may I put in a feature request for some more external editors or maybe an external printer command? Sure - I've created a feature request at http://redmine.yorba.org/issues/5879 adam From dave at dawoodfall.net Tue Sep 25 00:07:05 2012 From: dave at dawoodfall.net (David Woodfall) Date: Tue, 25 Sep 2012 01:07:05 +0100 Subject: [Shotwell] Idea maybe Feature Req for more external editors or at least external printer In-Reply-To: <5060ea5d.c44a420a.2448.18d8@mx.google.com> References: <20120924222223.GA15393@Junius> <5060ea5d.c44a420a.2448.18d8@mx.google.com> Message-ID: <20120925000704.GB9822@Junius> On (23:11 24/09/12), Adam Dingle put forth the proposition: >On Mon, Sep 24, 2012 at 3:22 PM, David Woodfall wrote: >I would like to be able to use Photo Print to print, which I can do if >I create a .desktop file for it and select it in external editors. >Problem is that I'm having to swap back and forth between GIMP and >Photo Print, which slows down the workflow. > >So may I put in a feature request for some more external editors >or maybe an external printer command? > >Sure - I've created a feature request at > >http://redmine.yorba.org/issues/5879 > >adam Thanks Adam From saivasanth8 at gmail.com Tue Sep 25 11:58:30 2012 From: saivasanth8 at gmail.com (sai vasanth) Date: Tue, 25 Sep 2012 17:28:30 +0530 Subject: [Shotwell] REG: Shotwell(0.12.3) new saved search not working In-Reply-To: References: Message-ID: Dear all i am using Shotwell(0.12.3) ,in this version, Edit -> Saved search is not working. need the help to solve this bug. and Right clicking on a photo and giving move to trash fails sometimes.thanks in advance -- __________________________ Saivasanth S From adam at yorba.org Tue Sep 25 14:29:39 2012 From: adam at yorba.org (Adam Dingle) Date: Tue, 25 Sep 2012 14:22:39 -0007 Subject: [Shotwell] REG: Shotwell(0.12.3) new saved search not working In-Reply-To: References: Message-ID: <5061bfd0.6457420a.1fa8.162a@mx.google.com> On Tue, Sep 25, 2012 at 4:58 AM, sai vasanth wrote: Dear all i am using Shotwell(0.12.3) Good to know. ?What operating system version are you running? in this version, Edit -> Saved search is not working. need the help to solve this bug. What happens when you choose Edit->New Saved Search? ?How is Shotwell behaving differently that you would expect, exactly? and Right clicking on a photo and giving move to trash fails sometimes. How does it fail? ?Do you see an error message, or does nothing happen at all? adam From brunogirin at gmail.com Tue Sep 25 15:29:15 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 25 Sep 2012 16:29:15 +0100 Subject: [Shotwell] f-spot import hangs In-Reply-To: <504163250.72646.1348507329003.JavaMail.root@yetopen.it> References: <504163250.72646.1348507329003.JavaMail.root@yetopen.it> Message-ID: <5061CDCB.9090305@gmail.com> On 24/09/12 18:22, Lorenzo Milesi wrote: >> Are you sure you uploaded the file correctly? It claims it's 0 bytes >> when I download it. The massif output doesn't have to be huge but it >> should be more than 0 bytes :-) > ups, something went wrong during the upload. > this should work! > http://dl.dropbox.com/u/706934/massif.out.13520.gz Lorenzo, If you run ms_print on this file, you get a nice graph and some detailed memory snapshot. What we get out of this is that Shotwell was using 386MB of memory by the time the software finished running, which in itself is not a massive concern. What is more concerning is that the memory usage seems to only go up and rarely down. Most of the memory (~94% by the end of the run) seems to be allocated to pixbuf structures (i.e. images), which is sort of understandable for a photo management application. 80% in gdk_pixbuf_new and the remainder in gdk_pixbuf_copy. However, the fact that it happens during an import probably means they're all thumbnails as Shotwell creates them at that time. Having said this, I'm not convinced memory usage is the root cause of your problem. The output you got would still warrant opening a defect in redmine though as it would be good to understand why all those pixbufs are not released. One thing I didn't ask you, which I should have: when it hangs, what is the CPU usage? Is Shotwell using 100% CPU or not that much? If it uses 100% CPU, it's probably stuck in an infinite loop somewhere. If not, it may be a threading issue. The next thing to do would be to run it through valgrind again but this time using the helgrind or DRD tools to confirm what is happening in terms of thread management and see if it locks itself out. Using the callgrind tool could produce interesting output too. I haven't used any of those so can't really help on how to use them or interpret the results but if you have data, we can always try to have a look see if it tells us something. Cheers, Bruno From maxxer at ufficyo.com Tue Sep 25 15:52:47 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Tue, 25 Sep 2012 17:52:47 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <88291205.81987.1348588112806.JavaMail.root@yetopen.it> Message-ID: <582078275.82040.1348588367288.JavaMail.root@yetopen.it> > Most of the memory (~94% by the end of the run) seems to be allocated > to > pixbuf structures (i.e. images), which is sort of understandable for > a > photo management application. 80% in gdk_pixbuf_new and the remainder > in > gdk_pixbuf_copy. However, the fact that it happens during an import > probably means they're all thumbnails as Shotwell creates them at > that time. > > Having said this, I'm not convinced memory usage is the root cause of > your problem. Yeah, can agree, in fact it's not filling up system ram, even if this system has only 1Gb. > One thing I didn't ask you, which I should have: when it hangs, what > is > the CPU usage? Is Shotwell using 100% CPU or not that much? If it > uses > 100% CPU, it's probably stuck in an infinite loop somewhere. If not, > it > may be a threading issue. I wrote in my first post that it's hanging at 100%. when I captured the massif file shotwell was running at 100% cpu (on a single core, if matters). > The next thing to do would be to run it through valgrind again but > this > time using the helgrind or DRD tools to confirm what is happening in > terms of thread management and see if it locks itself out. Using the > callgrind tool could produce interesting output too. I haven't used > any > of those so can't really help on how to use them or interpret the > results but if you have data, we can always try to have a look see if > it > tells us something. I'm not familiar with valgrind too, but it's ok to run anything if can sort this out. Said that, if anyone has a more precise target to hunt (that is: tool) I'll be happy to report back. I'll open a ticket, in the meantime. -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From brunogirin at gmail.com Tue Sep 25 16:59:54 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 25 Sep 2012 17:59:54 +0100 Subject: [Shotwell] f-spot import hangs In-Reply-To: <582078275.82040.1348588367288.JavaMail.root@yetopen.it> References: <582078275.82040.1348588367288.JavaMail.root@yetopen.it> Message-ID: <5061E30A.3010800@gmail.com> On 25/09/12 16:52, Lorenzo Milesi wrote: >> Most of the memory (~94% by the end of the run) seems to be allocated >> to >> pixbuf structures (i.e. images), which is sort of understandable for >> a >> photo management application. 80% in gdk_pixbuf_new and the remainder >> in >> gdk_pixbuf_copy. However, the fact that it happens during an import >> probably means they're all thumbnails as Shotwell creates them at >> that time. >> >> Having said this, I'm not convinced memory usage is the root cause of >> your problem. > Yeah, can agree, in fact it's not filling up system ram, even if this system has only 1Gb. > >> One thing I didn't ask you, which I should have: when it hangs, what >> is >> the CPU usage? Is Shotwell using 100% CPU or not that much? If it >> uses >> 100% CPU, it's probably stuck in an infinite loop somewhere. If not, >> it >> may be a threading issue. > I wrote in my first post that it's hanging at 100%. > when I captured the massif file shotwell was running at 100% cpu (on a single core, if matters). Sorry, I had forgotten that. Which means it's probably trying to do something repeatedly that it just doesn't finish. Sounds like an infinite loop. There's a good example of how to debug this sort of problem with gdb here: http://www.unknownroad.com/rtfm/gdbtut/gdbinfloop.html > >> The next thing to do would be to run it through valgrind again but >> this >> time using the helgrind or DRD tools to confirm what is happening in >> terms of thread management and see if it locks itself out. Using the >> callgrind tool could produce interesting output too. I haven't used >> any >> of those so can't really help on how to use them or interpret the >> results but if you have data, we can always try to have a look see if >> it >> tells us something. > I'm not familiar with valgrind too, but it's ok to run anything if can sort this out. > Said that, if anyone has a more precise target to hunt (that is: tool) I'll be happy to report back. > > > I'll open a ticket, in the meantime. Thanks! Tell me when you've done so and I'll have a look to see if I can add anything. Bruno From jim at yorba.org Tue Sep 25 18:25:30 2012 From: jim at yorba.org (Jim Nelson) Date: Tue, 25 Sep 2012 18:18:30 -0007 Subject: [Shotwell] f-spot import hangs In-Reply-To: <5061CDCB.9090305@gmail.com> References: <504163250.72646.1348507329003.JavaMail.root@yetopen.it> <5061CDCB.9090305@gmail.com> Message-ID: <5061f71c.c654420a.796f.34ba@mx.google.com> Just to jump in here, I'll add that what Bruno's seeing is completely in line with the design of the BatchImport class. ?The whole import process is a kind of bucket brigade, moving files from one stage to the next. ?The last stage (creating the thumbnails) is a bottleneck because encoding and writing JPEGs takes a bit of time. ?So in import memory usage will spike due to the number of Pixbufs sitting in memory waiting to be committed to disk. -- Jim On Tue, Sep 25, 2012 at 8:29 AM, Bruno Girin wrote: On 24/09/12 18:22, Lorenzo Milesi wrote: >> Are you sure you uploaded the file correctly? It claims it's 0 bytes >> when I download it. The massif output doesn't have to be huge but it >> should be more than 0 bytes :-) > ups, something went wrong during the upload. > this should work! > http://dl.dropbox.com/u/706934/massif.out.13520.gz Lorenzo, If you run ms_print on this file, you get a nice graph and some detailed memory snapshot. What we get out of this is that Shotwell was using 386MB of memory by the time the software finished running, which in itself is not a massive concern. What is more concerning is that the memory usage seems to only go up and rarely down. Most of the memory (~94% by the end of the run) seems to be allocated to pixbuf structures (i.e. images), which is sort of understandable for a photo management application. 80% in gdk_pixbuf_new and the remainder in gdk_pixbuf_copy. However, the fact that it happens during an import probably means they're all thumbnails as Shotwell creates them at that time. Having said this, I'm not convinced memory usage is the root cause of your problem. The output you got would still warrant opening a defect in redmine though as it would be good to understand why all those pixbufs are not released. One thing I didn't ask you, which I should have: when it hangs, what is the CPU usage? Is Shotwell using 100% CPU or not that much? If it uses 100% CPU, it's probably stuck in an infinite loop somewhere. If not, it may be a threading issue. The next thing to do would be to run it through valgrind again but this time using the helgrind or DRD tools to confirm what is happening in terms of thread management and see if it locks itself out. Using the callgrind tool could produce interesting output too. I haven't used any of those so can't really help on how to use them or interpret the results but if you have data, we can always try to have a look see if it tells us something. Cheers, Bruno _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From brunogirin at gmail.com Tue Sep 25 18:49:46 2012 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 25 Sep 2012 19:49:46 +0100 Subject: [Shotwell] f-spot import hangs In-Reply-To: <5061f71c.c654420a.796f.34ba@mx.google.com> References: <504163250.72646.1348507329003.JavaMail.root@yetopen.it> <5061CDCB.9090305@gmail.com> <5061f71c.c654420a.796f.34ba@mx.google.com> Message-ID: <5061FCCA.1090403@gmail.com> True but then shouldn't it release memory allocated to thumbnails for a given BatchImportJob once that job is finished? By the looks of it, it doesn't always do that as the memory usage only goes up. The way the F-Spot import was (re-)designed it creates a series of small BatchImportJob's rather than a single massive one to enable the core BatchImport class to clean up after each job. The idea was that even with a massive database to import, it should never really spike but should rather plateau with processed jobs being removed from the head of queue while new ones are added to the tail. Note that this is not necessarily the most efficient design in terms of processor performance because it results in quite a few threads but the size of each individual jobs could be quite easily adjusted. Bruno On 25/09/12 19:25, Jim Nelson wrote: > Just to jump in here, I'll add that what Bruno's seeing is completely > in line with the design of the BatchImport class. The whole import > process is a kind of bucket brigade, moving files from one stage to > the next. The last stage (creating the thumbnails) is a bottleneck > because encoding and writing JPEGs takes a bit of time. So in import > memory usage will spike due to the number of Pixbufs sitting in memory > waiting to be committed to disk. > > -- Jim > > On Tue, Sep 25, 2012 at 8:29 AM, Bruno Girin wrote: >> On 24/09/12 18:22, Lorenzo Milesi wrote: >> >> Are you sure you uploaded the file correctly? It claims it's 0 bytes >> >> when I download it. The massif output doesn't have to be huge but it >> >> should be more than 0 bytes :-) >> > ups, something went wrong during the upload. >> > this should work! >> > http://dl.dropbox.com/u/706934/massif.out.13520.gz >> >> Lorenzo, >> >> If you run ms_print on this file, you get a nice graph and some detailed >> memory snapshot. What we get out of this is that Shotwell was using >> 386MB of memory by the time the software finished running, which in >> itself is not a massive concern. What is more concerning is that the >> memory usage seems to only go up and rarely down. >> >> Most of the memory (~94% by the end of the run) seems to be allocated to >> pixbuf structures (i.e. images), which is sort of understandable for a >> photo management application. 80% in gdk_pixbuf_new and the remainder in >> gdk_pixbuf_copy. However, the fact that it happens during an import >> probably means they're all thumbnails as Shotwell creates them at >> that time. >> >> Having said this, I'm not convinced memory usage is the root cause of >> your problem. The output you got would still warrant opening a defect in >> redmine though as it would be good to understand why all those pixbufs >> are not released. >> >> One thing I didn't ask you, which I should have: when it hangs, what is >> the CPU usage? Is Shotwell using 100% CPU or not that much? If it uses >> 100% CPU, it's probably stuck in an infinite loop somewhere. If not, it >> may be a threading issue. >> >> The next thing to do would be to run it through valgrind again but this >> time using the helgrind or DRD tools to confirm what is happening in >> terms of thread management and see if it locks itself out. Using the >> callgrind tool could produce interesting output too. I haven't used any >> of those so can't really help on how to use them or interpret the >> results but if you have data, we can always try to have a look see if it >> tells us something. >> >> Cheers, >> >> Bruno >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From jim at yorba.org Tue Sep 25 19:17:03 2012 From: jim at yorba.org (Jim Nelson) Date: Tue, 25 Sep 2012 19:10:03 -0007 Subject: [Shotwell] f-spot import hangs In-Reply-To: <5061FCCA.1090403@gmail.com> References: <504163250.72646.1348507329003.JavaMail.root@yetopen.it> <5061CDCB.9090305@gmail.com> <5061f71c.c654420a.796f.34ba@mx.google.com> <5061FCCA.1090403@gmail.com> Message-ID: <50620330.4955420a.7913.38cd@mx.google.com> On Tue, Sep 25, 2012 at 11:49 AM, Bruno Girin wrote: True but then shouldn't it release memory allocated to thumbnails for a given BatchImportJob once that job is finished? By the looks of it, it doesn't always do that as the memory usage only goes up. Yes, but the bottleneck at the end of the process causes the Pixbufs to queue up, leading to constant growth in the footprint. ?When the import does complete the memory is released. ?At least, it's *supposed* to, if not, that's a memory leak, but I don't think that's what we're seeing here. It's unfortunate that the thumbnail generation has to happen at the tail of the process. ?It's a result of an early design decision that the thumbnails are named by their corresponding photo's rowid in the SQLite database. ?Obviously you don't know the rowid until the row has been inserted, hence the thumbnails are the last step in the process. Also remember that GLib uses a slice allocator that will grow a pool of available memory so speed up malloc's. ?It's a kind of garbage collection, and means that the total memory Shotwell is using (as seen by the system) is not necessarily a reflection of how much *active* memory Shotwell as allocated at any moment. The way the F-Spot import was (re-)designed it creates a series of small BatchImportJob's rather than a single massive one to enable the core BatchImport class to clean up after each job. The idea was that even with a massive database to import, it should never really spike but should rather plateau with processed jobs being removed from the head of queue while new ones are added to the tail. Note that this is not necessarily the most efficient design in terms of processor performance because it results in quite a few threads but the size of each individual jobs could be quite easily adjusted. Yes, this is a solid improvement, because it allows for BatchImport to smooth out the tasks between the various stages. Import has proven to be of the trickiest beasts in Shotwell. ?It takes too long, so you increase parallelization, then it takes too much CPU/RAM/disk activity, so you back off the parallelization. ?Each system is different, so finding that sweet spot is difficult. All this said, it does sound like there's an infinite loop here, and it sounds like it's at the end of the import. ?If it's in the main loop, that would block completion of background import tasks, which also leads to what looks like a memory leak. -- Jim From shaun at cantab.net Thu Sep 27 04:23:28 2012 From: shaun at cantab.net (Shaun Crampton) Date: Wed, 26 Sep 2012 21:23:28 -0700 Subject: [Shotwell] Support for external editor Message-ID: Hi, I'm trying to import a library from iPhoto with lots of adjusted/cropped/rotated photos. I'd like to keep the originals safe but also import my edited copies for display. Does shotwell support anything like that (managing an original and externally-edited file) at present or is all its editing done by reapplying edits at display time? If the support is there I can probably write a script to import the database (iPhoto seems to maintain an XML doc listing the library and shotwell uses sqlite) but I don't really want to have to re-edit 20,000 photos! Thanks, -Shaun From maxxer at ufficyo.com Thu Sep 27 04:54:48 2012 From: maxxer at ufficyo.com (Lorenzo Milesi) Date: Thu, 27 Sep 2012 06:54:48 +0200 (CEST) Subject: [Shotwell] f-spot import hangs In-Reply-To: <5061E30A.3010800@gmail.com> Message-ID: <2108123525.10789.1348721688769.JavaMail.root@yetopen.it> > Sorry, I had forgotten that. Which means it's probably trying to do > something repeatedly that it just doesn't finish. Sounds like an > infinite loop. There's a good example of how to debug this sort of > problem with gdb here: > http://www.unknownroad.com/rtfm/gdbtut/gdbinfloop.html Following this guide I produced the gdb backtrace attached here: http://redmine.yorba.org/issues/5882#note-2 #47 0xb72dd201 in g_main_context_iteration (context=0x8477880, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #48 0xb7479824 in g_application_run (application=0x84ac840, argc=0, argv=0x0) at /build/buildd/glib2.0-2.32.3/./gio/gapplication.c:1507 #49 0x0830a31d in application_start (self=0x8482f18, argv=0x0, argv_length1=0) at /build/buildd/shotwell-0.13.0/src/Application.vala:157 #50 0x081ded94 in library_exec (mounts=0x847a9c0, mounts_length1=0) at /build/buildd/shotwell-0.13.0/src/main.vala:189 #51 0x081e04af in _vala_main (args=0xbffff474, args_length1=1) at /build/buildd/shotwell-0.13.0/src/main.vala:407 #52 0x080a9538 in main (argc=1, argv=0xbffff474) at /build/buildd/shotwell-0.13.0/src/main.vala:309 thanks for the help! -- Lorenzo Milesi - lorenzo.milesi at yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it From farrukh.najm at gmail.com Fri Sep 28 14:57:58 2012 From: farrukh.najm at gmail.com (Farrukh Najmi) Date: Fri, 28 Sep 2012 10:57:58 -0400 Subject: [Shotwell] Setting date metadata in photo Message-ID: <5065BAF6.9000305@gmail.com> Dear Colleagues, I have some photos that were either scanned or were taken froma camera that did not have date set correctly. I would like to be able to edit the date embedded in the image file itself. Does shotwell allow that? Also, are there any plans for setting IPTC metadata from Shotwell. If so what is the ETA for that feature? Thanks for a great application. -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com From el.cameleon.1 at gmail.com Fri Sep 28 15:05:26 2012 From: el.cameleon.1 at gmail.com (Vincent) Date: Fri, 28 Sep 2012 17:05:26 +0200 Subject: [Shotwell] Setting date metadata in photo In-Reply-To: <5065BAF6.9000305@gmail.com> References: <5065BAF6.9000305@gmail.com> Message-ID: 2012/9/28 Farrukh Najmi > I have some photos that were either scanned or were taken froma camera > that did not have date set correctly. > I would like to be able to edit the date embedded in the image file > itself. Does shotwell allow that? > Yes it does, and this support page explains it in details: http://yorba.org/shotwell/help/edit-time-date.html -- Vincent (cam?l?on) From farrukh.najm at gmail.com Fri Sep 28 15:22:45 2012 From: farrukh.najm at gmail.com (Farrukh Najmi) Date: Fri, 28 Sep 2012 11:22:45 -0400 Subject: [Shotwell] Setting date metadata in photo In-Reply-To: References: <5065BAF6.9000305@gmail.com> Message-ID: <5065C0C5.2040603@gmail.com> Worked perfectly! Sorry I should have discovered that. Thanks Vincent. On plans for setting any IPTC tag on one or more photos I see the following issue: http://redmine.yorba.org/issues/3103 Any updates on the plans for this issue? Thanks. On 09/28/2012 11:05 AM, Vincent wrote: > 2012/9/28 Farrukh Najmi > >> I have some photos that were either scanned or were taken froma camera >> that did not have date set correctly. >> I would like to be able to edit the date embedded in the image file >> itself. Does shotwell allow that? >> > Yes it does, and this support page explains it in details: > http://yorba.org/shotwell/help/edit-time-date.html > From adam at yorba.org Fri Sep 28 17:10:24 2012 From: adam at yorba.org (Adam Dingle) Date: Fri, 28 Sep 2012 17:03:24 -0007 Subject: [Shotwell] Support for external editor In-Reply-To: References: Message-ID: <5065da02.84c9440a.3b69.4b3a@mx.google.com> On Wed, Sep 26, 2012 at 9:23 PM, Shaun Crampton wrote: Hi, I'm trying to import a library from iPhoto with lots of adjusted/cropped/rotated photos. I'd like to keep the originals safe but also import my edited copies for display. Does shotwell support anything like that (managing an original and externally-edited file) at present or is all its editing done by reapplying edits at display time? Both are true. ?:) ?If you make edits within Shotwell, Shotwell doesn't write those out to the external file - instead, the edits are reapplied at display time. ?But if you use Shotwell's Open With External Editor command to edit a photo with a program such as GIMP, then Shotwell manages both the original and the externally edited file. ?Typically the original will have a name like IMG_0729.JPG and the externally edited file will be named like IMG_0729_modified.JPG. Unfortunately Shotwell isn't smart enough to be able to import both the original and modified versions of a photo and associate them with each other. ?If you import from a directory containing IMG_0729.JPG and IMG_0729_modified.JPG, these will be imported as two separate photos. If the support is there I can probably write a script to import the database (iPhoto seems to maintain an XML doc listing the library and shotwell uses sqlite) but I don't really want to have to re-edit 20,000 photos! It would certainly be nice if Shotwell could import from an iPhoto database while preserving both the original and modified versions of each photo. ?You could consider implementing this as a Shotwell plugin, since Shotwell allows plugins to provide new import sources (importing from F-Spot is implemented via such a plugin). ?Cheers - adam From shaun at cantab.net Sat Sep 29 04:02:11 2012 From: shaun at cantab.net (Shaun Crampton) Date: Fri, 28 Sep 2012 21:02:11 -0700 Subject: [Shotwell] Support for external editor In-Reply-To: <5065da02.84c9440a.3b69.4b3a@mx.google.com> References: <5065da02.84c9440a.3b69.4b3a@mx.google.com> Message-ID: Just what I wanted to know, thanks. I'm not sure if I'll have time to grok the Shotwell code vs just hacking together a script but the docs look quite good so I might give it a go. Either way, I'll put the work on github. -Shaun On 28 September 2012 10:10, Adam Dingle wrote: > > > On Wed, Sep 26, 2012 at 9:23 PM, Shaun Crampton wrote: > > Hi, > > I'm trying to import a library from iPhoto with lots of > adjusted/cropped/rotated photos. I'd like to keep the originals safe but > also import my edited copies for display. Does shotwell support anything > like that (managing an original and externally-edited file) at present or > is all its editing done by reapplying edits at display time? > > > Both are true. :) If you make edits within Shotwell, Shotwell doesn't > write those out to the external file - instead, the edits are reapplied at > display time. But if you use Shotwell's Open With External Editor command > to edit a photo with a program such as GIMP, then Shotwell manages both the > original and the externally edited file. Typically the original will have > a name like IMG_0729.JPG and the externally edited file will be named like > IMG_0729_modified.JPG. > > Unfortunately Shotwell isn't smart enough to be able to import both the > original and modified versions of a photo and associate them with each > other. If you import from a directory containing IMG_0729.JPG and > IMG_0729_modified.JPG, these will be imported as two separate photos. > > > > If the support is there I can probably write a script to import the > database (iPhoto seems to maintain an XML doc listing the library and > shotwell uses sqlite) but I don't really want to have to re-edit 20,000 > photos! > > > It would certainly be nice if Shotwell could import from an iPhoto > database while preserving both the original and modified versions of each > photo. You could consider implementing this as a Shotwell plugin, since > Shotwell allows plugins to provide new import sources (importing from > F-Spot is implemented via such a plugin). Cheers - > > adam > From martin at minimum.se Sat Sep 29 14:57:54 2012 From: martin at minimum.se (Martin Olsson) Date: Sat, 29 Sep 2012 16:57:54 +0200 Subject: [Shotwell] [PATCH] Fix spelling errors (some user facing, most in source code comments) Message-ID: <1348930674-22368-1-git-send-email-martin@minimum.se> --- help/C/view-sidebar.page | 2 +- plugins/Makefile.plugin.mk | 2 +- plugins/shotwell-publishing/PicasaPublishing.vala | 2 +- plugins/shotwell-publishing/PiwigoPublishing.vala | 2 +- plugins/shotwell-publishing/YouTubePublishing.vala | 2 +- po/shotwell-core/shotwell.pot | 2 +- src/AppDirs.vala | 2 +- src/Commands.vala | 2 +- src/CustomComponents.vala | 2 +- src/DirectoryMonitor.vala | 2 +- src/Photo.vala | 2 +- src/PhotoPage.vala | 2 +- src/Tombstone.vala | 4 ++-- src/camera/ImportPage.vala | 2 +- src/core/DataSource.vala | 4 ++-- src/core/DatabaseSourceCollection.vala | 2 +- src/plugins/DataImportsInterfaces.vala | 4 ++-- src/plugins/PublishingInterfaces.vala | 2 +- src/searches/SearchBoolean.vala | 2 +- src/util/file.vala | 2 +- src/util/misc.vala | 2 +- thumbnailer/shotwell-video-thumbnailer.vala | 2 +- 22 files changed, 25 insertions(+), 25 deletions(-) diff --git a/help/C/view-sidebar.page b/help/C/view-sidebar.page index de26c40..2da4674 100644 --- a/help/C/view-sidebar.page +++ b/help/C/view-sidebar.page @@ -26,7 +26,7 @@

The Flagged lists all photos you had previous flagged.

-

The Saved Search allows you to sort your libary by many criterias.

+

The Saved Search allows you to sort your library by many criteria.

The Events folder lists all events in your library. An event is a group of photos that were taken at approximately the same time.

diff --git a/plugins/Makefile.plugin.mk b/plugins/Makefile.plugin.mk index d76433b..2b83b5f 100644 --- a/plugins/Makefile.plugin.mk +++ b/plugins/Makefile.plugin.mk @@ -4,7 +4,7 @@ # Requires PLUGIN and SRC_FILES be set to the name of the plugin binary (minus extension) and that # the directory is registered in plugins.mk. # -# To use, include this file in each plug-in directory's Makefile after setting apropriate variables. +# To use, include this file in each plug-in directory's Makefile after setting appropriate variables. # Also be sure that each plug-in has a dummy_main() function to satisfy valac's linkage. # # NOTE: This file is called from the cwd of each directory, hence the relative paths should be diff --git a/plugins/shotwell-publishing/PicasaPublishing.vala b/plugins/shotwell-publishing/PicasaPublishing.vala index 397503d..a9676bb 100644 --- a/plugins/shotwell-publishing/PicasaPublishing.vala +++ b/plugins/shotwell-publishing/PicasaPublishing.vala @@ -318,7 +318,7 @@ public class PicasaPublisher : Spit.Publishing.Publisher, GLib.Object { // user's album feed doesn't exist -- this occurs when the user has a valid Google // account but it hasn't yet been set up for use with Picasa. In this case, we // display an informational pane with an "account not set up" message. In addition, we - // deauthenticate the session. Deauth is neccessary because must've previously auth'd + // deauthenticate the session. Deauth is necessary because we must've previously auth'd // the user's account to even be able to query the album feed. session.deauthenticate(); do_show_not_set_up_pane(); diff --git a/plugins/shotwell-publishing/PiwigoPublishing.vala b/plugins/shotwell-publishing/PiwigoPublishing.vala index d75b922..47b648b 100644 --- a/plugins/shotwell-publishing/PiwigoPublishing.vala +++ b/plugins/shotwell-publishing/PiwigoPublishing.vala @@ -859,7 +859,7 @@ public class PiwigoPublisher : Spit.Publishing.Publisher, GLib.Object { } debug("Unhandled error: type=%s; message='%s'".printf(error_type, e.message)); - do_show_error_message(_("An error message occured when publishing to Piwigo. Please try again.")); + do_show_error_message(_("An error message occurred when publishing to Piwigo. Please try again.")); } /** diff --git a/plugins/shotwell-publishing/YouTubePublishing.vala b/plugins/shotwell-publishing/YouTubePublishing.vala index 9319eb9..6ab6713 100644 --- a/plugins/shotwell-publishing/YouTubePublishing.vala +++ b/plugins/shotwell-publishing/YouTubePublishing.vala @@ -290,7 +290,7 @@ public class YouTubePublisher : Spit.Publishing.Publisher, GLib.Object { // account. This occurs when the user has a valid Google account but it hasn't // yet been set up for use with YouTube. In this case, we re-display the credentials // capture pane with an "account not set up" message. In addition, we deauthenticate - // the session. Deauth is neccessary because we did previously auth the user's + // the session. Deauth is necessary because we did previously auth the user's // account. session.deauthenticate(); do_show_credentials_pane(CredentialsPane.Mode.NOT_SET_UP); diff --git a/po/shotwell-core/shotwell.pot b/po/shotwell-core/shotwell.pot index df41958..a5dec74 100644 --- a/po/shotwell-core/shotwell.pot +++ b/po/shotwell-core/shotwell.pot @@ -3685,7 +3685,7 @@ msgid "Creating album %s..." msgstr "" #: plugins/shotwell-publishing/PiwigoPublishing.vala:862 -msgid "An error message occured when publishing to Piwigo. Please try again." +msgid "An error message occurred when publishing to Piwigo. Please try again." msgstr "" #: plugins/shotwell-publishing/PiwigoPublishing.vala:943 diff --git a/src/AppDirs.vala b/src/AppDirs.vala index 0a0c0f1..2b217f4 100644 --- a/src/AppDirs.vala +++ b/src/AppDirs.vala @@ -150,7 +150,7 @@ class AppDirs { return get_home_dir().get_child(_("Pictures")); } - // Library folder + photo folder, based on user's prefered directory pattern. + // Library folder + photo folder, based on user's preferred directory pattern. public static File get_baked_import_dir(time_t tm) { string? pattern = Config.Facade.get_instance().get_directory_pattern(); if (is_string_empty(pattern)) diff --git a/src/Commands.vala b/src/Commands.vala index b233599..02f0a4b 100644 --- a/src/Commands.vala +++ b/src/Commands.vala @@ -791,7 +791,7 @@ public class RedeyeCommand : GenericPhotoTransformationCommand { public abstract class MovePhotosCommand : Command { // Piggyback on a private command so that processing to determine new_event can occur before - // contruction, if needed + // construction, if needed protected class RealMovePhotosCommand : MultipleDataSourceCommand { private SourceProxy new_event_proxy = null; private Gee.HashMap old_events = new Gee.HashMap< diff --git a/src/CustomComponents.vala b/src/CustomComponents.vala index 13a0149..6f8e302 100644 --- a/src/CustomComponents.vala +++ b/src/CustomComponents.vala @@ -128,7 +128,7 @@ public class ThemeLoader { /* If the image data loaded from disk didn't contain NUM_SUPPORTED_INTENSITIES colors, then we can't unambiguously map the colors in the loaded image data - to theme colors on the user's system, so propogate an error */ + to theme colors on the user's system, so propagate an error */ if (colors.size != NUM_SUPPORTED_INTENSITIES) error("ThemeLoader: load_icon: pixbuf does not contain the correct number " + "of unique colors"); diff --git a/src/DirectoryMonitor.vala b/src/DirectoryMonitor.vala index 4647b2d..0ee2717 100644 --- a/src/DirectoryMonitor.vala +++ b/src/DirectoryMonitor.vala @@ -1100,7 +1100,7 @@ public class DirectoryMonitor : Object { break; default: - // artifically complete it + // artificially complete it query_info.completed = true; process_query_queue(query_info); break; diff --git a/src/Photo.vala b/src/Photo.vala index dd7b5ba..81ad24a 100644 --- a/src/Photo.vala +++ b/src/Photo.vala @@ -156,7 +156,7 @@ public enum Rating { // Photo is an abstract class that allows for applying transformations on-the-fly to a // particular photo without modifying the backing image file. The interface allows for -// transformations to be stored persistently elsewhere or in memory until they're commited en +// transformations to be stored persistently elsewhere or in memory until they're committed en // masse to an image file. public abstract class Photo : PhotoSource, Dateable { // Need to use "thumb" rather than "photo" for historical reasons -- this name is used diff --git a/src/PhotoPage.vala b/src/PhotoPage.vala index 8676364..9c55327 100644 --- a/src/PhotoPage.vala +++ b/src/PhotoPage.vala @@ -1459,7 +1459,7 @@ public abstract class EditingHostPage : SinglePhotoPage { current_tool = tool; current_tool.activate(photo_canvas); - // if the tool has an auxilliary window, move it properly on the screen + // if the tool has an auxiliary window, move it properly on the screen place_tool_window(); // repaint entire view, with the tool now hooked in diff --git a/src/Tombstone.vala b/src/Tombstone.vala index c71948b..4e2fed6 100644 --- a/src/Tombstone.vala +++ b/src/Tombstone.vala @@ -102,7 +102,7 @@ public class TombstoneSourceCollection : DatabaseSourceCollection { // This initiates a scan of the tombstoned files, resurrecting them if the file is no longer // present on disk. If a DirectoryMonitor is supplied, the scan will use that object's FileInfo // if available. If not available or not supplied, the scan will query for the file's - // existance. + // existence. // // Note that this call is non-blocking. public void launch_scan(DirectoryMonitor? monitor, Cancellable? cancellable) { @@ -132,7 +132,7 @@ public class TombstoneSourceCollection : DatabaseSourceCollection { break; if (!(err is IOError.NOT_FOUND)) { - warning("Unable to check for existance of tombstoned file %s: %s", + warning("Unable to check for existence of tombstoned file %s: %s", file.get_path(), err.message); } } diff --git a/src/camera/ImportPage.vala b/src/camera/ImportPage.vala index 5859b80..3d19e77 100644 --- a/src/camera/ImportPage.vala +++ b/src/camera/ImportPage.vala @@ -1626,7 +1626,7 @@ public class ImportPage : CheckerboardPage { CameraImportJob import_job = new CameraImportJob(null_context, import_file); - // Maintain RAW+JPEG assocation. + // Maintain RAW+JPEG association. if (import_file is PhotoImportSource && ((PhotoImportSource) import_file).get_associated() != null) { import_job.set_associated(new CameraImportJob(null_context, diff --git a/src/core/DataSource.vala b/src/core/DataSource.vala index f0c219e..11a5f90 100644 --- a/src/core/DataSource.vala +++ b/src/core/DataSource.vala @@ -361,7 +361,7 @@ public abstract class DataSource : DataObject { // or has been unlinked from one. It should not be used otherwise. (In particular, don't // automate destroys by removing and then calling this method -- that will happen automatically.) // To destroy a DataSource already integrated into a SourceCollection, call - // SourceCollection.destroy_marked(). Returns true if the operation completed succesfully, + // SourceCollection.destroy_marked(). Returns true if the operation completed successfully, // otherwise it will return false. public bool destroy_orphan(bool delete_backing) { bool ret = true; @@ -386,7 +386,7 @@ public abstract class DataSource : DataObject { return ret; } - // DataViews subscribe to the DataSource to inform it of their existance. Not only does this + // DataViews subscribe to the DataSource to inform it of their existence. Not only does this // allow for signal reflection (i.e. DataSource.altered -> DataView.altered) it also makes // them first-in-line for notification of destruction, so they can remove themselves from // their ViewCollections automatically. diff --git a/src/core/DatabaseSourceCollection.vala b/src/core/DatabaseSourceCollection.vala index 44b080f..044a8bf 100644 --- a/src/core/DatabaseSourceCollection.vala +++ b/src/core/DatabaseSourceCollection.vala @@ -8,7 +8,7 @@ public delegate int64 GetSourceDatabaseKey(DataSource source); // A DatabaseSourceCollection is a SourceCollection that understands database keys (IDs) and the // nature that a row in a database can only be instantiated once in the system, and so it tracks -// their existance in a map so they can be fetched by their key. +// their existence in a map so they can be fetched by their key. // // TODO: This would be better implemented as an observer class, possibly with an interface to // force subclasses to provide a fetch_by_key() method. diff --git a/src/plugins/DataImportsInterfaces.vala b/src/plugins/DataImportsInterfaces.vala index bd97b8a..5edfcfb 100644 --- a/src/plugins/DataImportsInterfaces.vala +++ b/src/plugins/DataImportsInterfaces.vala @@ -94,7 +94,7 @@ public interface DataImporter : GLib.Object { } /** - * Represents a libary of importable media items. + * Represents a library of importable media items. * * Developers of data import plugins provide a class that implements this interface. */ @@ -190,7 +190,7 @@ public interface DialogPane : GLib.Object { /** * If this bit is set, when the associated pane is installed, the on-screen publishing - * dialog box will grow to accomodate a full-width 1024 pixel web page. If both + * dialog box will grow to accommodate a full-width 1024 pixel web page. If both * EXTENDED_SIZE and COLOSSAL_SIZE are set, EXTENDED_SIZE takes precedence. */ COLOSSAL_SIZE = 1 << 2; diff --git a/src/plugins/PublishingInterfaces.vala b/src/plugins/PublishingInterfaces.vala index 339cc9d..0c9eabe 100644 --- a/src/plugins/PublishingInterfaces.vala +++ b/src/plugins/PublishingInterfaces.vala @@ -178,7 +178,7 @@ public interface DialogPane : GLib.Object { /** * If this bit is set, when the associated pane is installed, the on-screen publishing - * dialog box will grow to accomodate a full-width 1024 pixel web page. If both + * dialog box will grow to accommodate a full-width 1024 pixel web page. If both * EXTENDED_SIZE and COLOSSAL_SIZE are set, EXTENDED_SIZE takes precedence. */ COLOSSAL_SIZE = 1 << 2; diff --git a/src/searches/SearchBoolean.vala b/src/searches/SearchBoolean.vala index 40a13c8..3ee72b2 100644 --- a/src/searches/SearchBoolean.vala +++ b/src/searches/SearchBoolean.vala @@ -735,7 +735,7 @@ public class SavedSearch : DataSource { } } -// This table contains every saved search. It's the prefered way to add and destroy a saved +// This table contains every saved search. It's the preferred way to add and destroy a saved // search as well, since this table's create/destroy methods are tied to the database. public class SavedSearchTable { private static SavedSearchTable? instance = null; diff --git a/src/util/file.vala b/src/util/file.vala index 15b9569..eaba254 100644 --- a/src/util/file.vala +++ b/src/util/file.vala @@ -6,7 +6,7 @@ // Returns true if the file is claimed, false if it exists, and throws an Error otherwise. The file // will be created when the function exits and should be overwritten. Note that the file is not -// held open; claiming a file is merely based on its existance. +// held open; claiming a file is merely based on its existence. // // This function is thread-safe. public bool claim_file(File file) throws Error { diff --git a/src/util/misc.vala b/src/util/misc.vala index c842840..54a7a93 100644 --- a/src/util/misc.vala +++ b/src/util/misc.vala @@ -355,7 +355,7 @@ public class OpTimer { } // Dummy function for suppressing 'could not stat file' errors -// generated when saving into a previously non-existant file - +// generated when saving into a previously non-existent file - // please see https://bugzilla.gnome.org/show_bug.cgi?id=662814 // and to work around a spurious warning given by GDK when a // key press event is passed from a child class' event handler diff --git a/thumbnailer/shotwell-video-thumbnailer.vala b/thumbnailer/shotwell-video-thumbnailer.vala index a4d7dc2..79a2d7e 100644 --- a/thumbnailer/shotwell-video-thumbnailer.vala +++ b/thumbnailer/shotwell-video-thumbnailer.vala @@ -84,7 +84,7 @@ class ShotwellThumbnailer { // Get the snapshot buffer format now. We set the caps on the appsink so // that it can only be an rgb buffer. The only thing we have not specified - // on the caps is the height, which is dependant on the pixel-aspect-ratio + // on the caps is the height, which is dependent on the pixel-aspect-ratio // of the source material. caps = buffer.get_caps(); if (caps == null) { -- 1.7.9.5 From nigelyngc at gmail.com Sat Sep 29 15:41:41 2012 From: nigelyngc at gmail.com (Nigel Fitt) Date: Sat, 29 Sep 2012 17:41:41 +0200 Subject: [Shotwell] I do not want to receive e-mails from Shotwell. Message-ID: to whom it may concern, I do not want to receive e-mails from Shotwell. Thanking you. Regards, Nigel Fitt From pt at traversin.org Sat Sep 29 15:58:22 2012 From: pt at traversin.org (pt) Date: Sat, 29 Sep 2012 17:58:22 +0200 Subject: [Shotwell] I do not want to receive e-mails from Shotwell. In-Reply-To: References: Message-ID: On 29 September 2012 17:41, Nigel Fitt wrote: > to whom it may concern, > > I do not want to receive e-mails from Shotwell. At this link (at the very end of every e-mail) you can unsubscribe yourself from the list. > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell -- Web: http://traversin.org GNU/Linux user 190604 From schuetz.marc at gmx.de Sun Sep 30 06:59:14 2012 From: schuetz.marc at gmx.de (Marc) Date: Sun, 30 Sep 2012 08:59:14 +0200 Subject: [Shotwell] Since 0.13 Filter won work anymore - Ubuntu x86_64 Message-ID: <5067EDC2.7070604@gmx.de> Hi, Before upgrading to 0.13 I had this problem: Shotwell starts and the default filter is set to "All photos" (STRG+0) But shotwell shows "All photos + Rejected" and so I had to change after every start of shotwell to another filter and back. I thought with 0.13 this would be better, But now the change of ANY filter doesn show an effect and it displays only "All photos + Rejected" Can someone confirm this? Thanks and Kind Regards Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From schuetz.marc at gmx.de Sun Sep 30 09:04:50 2012 From: schuetz.marc at gmx.de (Marc) Date: Sun, 30 Sep 2012 11:04:50 +0200 Subject: [Shotwell] Since 0.13 Filter won work anymore - Ubuntu x86_64 In-Reply-To: <5067EDC2.7070604@gmx.de> References: <5067EDC2.7070604@gmx.de> Message-ID: <50680B32.9090502@gmx.de> Hi all again, tested a little bit more around. All Filter seems to work !!ONLY!! if you are on the Library. If I'm on a event , no Filter will work as discribed before. They will be ignored. Even if there are pictures with *,**,** or anything else or not. Cheers Marc Am 30.09.2012 08:59, schrieb Marc: > Hi, > > Before upgrading to 0.13 I had this problem: > > Shotwell starts and the default filter is set to "All photos" (STRG+0) > But shotwell shows "All photos + Rejected" and so I had to change after > every start of shotwell to another filter and back. > > I thought with 0.13 this would be better, But now the change of ANY > filter doesn show an effect and it displays only > "All photos + Rejected" > > Can someone confirm this? > > Thanks and Kind Regards > Marc > > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From onefiftyfour at hotmail.com Sun Sep 30 12:32:40 2012 From: onefiftyfour at hotmail.com (Eric L) Date: Sun, 30 Sep 2012 07:32:40 -0500 Subject: [Shotwell] Since 0.13 Filter won work anymore - Ubuntu x86_64 In-Reply-To: <50680B32.9090502@gmx.de> References: <5067EDC2.7070604@gmx.de>,<50680B32.9090502@gmx.de> Message-ID: I also have this problem. But discovered that if you can fix the problem if you View - Search Bar (or F8). -Ericusing 0.13.0+trunk Date: Sun, 30 Sep 2012 11:04:50 +0200 From: schuetz.marc at gmx.de To: shotwell at lists.yorba.org Subject: Re: [Shotwell] Since 0.13 Filter won work anymore - Ubuntu x86_64 Hi all again, tested a little bit more around. All Filter seems to work !!ONLY!! if you are on the Library. If I'm on a event , no Filter will work as discribed before. They will be ignored. Even if there are pictures with *,**,** or anything else or not. Cheers Marc Am 30.09.2012 08:59, schrieb Marc: > Hi, > > Before upgrading to 0.13 I had this problem: > > Shotwell starts and the default filter is set to "All photos" (STRG+0) > But shotwell shows "All photos + Rejected" and so I had to change after > every start of shotwell to another filter and back. > > I thought with 0.13 this would be better, But now the change of ANY > filter doesn show an effect and it displays only > "All photos + Rejected" > > Can someone confirm this? > > Thanks and Kind Regards > Marc > > > > _______________________________________________ > 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 farrukh.najm at gmail.com Sun Sep 30 21:14:20 2012 From: farrukh.najm at gmail.com (Farrukh Najmi) Date: Sun, 30 Sep 2012 17:14:20 -0400 Subject: [Shotwell] How to generate date-based events from No Event photos Message-ID: <5068B62C.4020306@gmail.com> Hi Guys, Something I did along the way marked many of my photos under "No Event" even though they have date metadata showing in lower left of screen when I click on a picture in the browse view. I also note that I have some years with large gaps in my photo library. I am assuming that somehow the date-based events for some years got messed up. Is there some way that I can automatically generate date based events for such pictures? Thanks for your help.