From andreas.wallberg at gmail.com Tue Feb 1 00:34:22 2011 From: andreas.wallberg at gmail.com (Andreas Wallberg) Date: Tue, 1 Feb 2011 01:34:22 +0100 Subject: [Shotwell] Auto-import stops prematurely - how to trace problem? Message-ID: Hi all! I am trying to import a large photo collection into Shotwell by having it crawling my Pictures directory structured by YYYY/MM. The collection contains 27000+ jpgs, photos in some other formats (including raw and nef) and some video. I am quite impressed with the performance of this program, which handles such a large collection really well. However, the auto import makes it to 25794 photos and then stops. Restarting the program to import the last pictures does not help. It claims to do 32% of the remaining files, but stops and does not update the "25794" number. My guess is that I have some bad file in there, but without knowing what actually happens during the import, the problem is difficult to locate. My question is, how do I move forward and find out what is going on? Can Shotwell do logging or print debug info somehow? Best regards, Andreas shotwell 0.8.1 Arch Linux 64-bit From pocmatos at gmail.com Tue Feb 1 08:13:52 2011 From: pocmatos at gmail.com (Paulo J. Matos) Date: Tue, 01 Feb 2011 08:13:52 +0000 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: <4D4290BE.2020103@googlemail.com> References: <4D428FD3.6030806@a-little-bit.de> <4D4290BE.2020103@googlemail.com> Message-ID: On 28/01/11 09:47, Martin Wei?haupt wrote: > Hi, > > try starting shotwell with this commandline argument: > shotwell -d /path/to/filestore > That's great to know. What's the best way to move an existing database and photo archive into a new directory? I want to move ~pmatos/.shotwell and ~pmatos/Pictures into ~photos/.shotwell and ~photos/Pictures respectively. Any tips? > This should give you a new shotwell "profile" in the given location. > I believe that you have to change the import directory in the settings > of shotwell too. > > Regards, > Martin > From steinixx at gmail.com Tue Feb 1 09:16:10 2011 From: steinixx at gmail.com (stone keeper) Date: Tue, 1 Feb 2011 10:16:10 +0100 Subject: [Shotwell] Auto-import stops prematurely - how to trace problem? In-Reply-To: References: Message-ID: hello, i have the same probleme here (same configuration). Could you please try to import only jpg files (all jpg's at once, without videos)? For me this works and it seems to be a problem with videos? regards On Tue, Feb 1, 2011 at 1:34 AM, Andreas Wallberg wrote: > Hi all! > > I am trying to import a large photo collection into Shotwell by having > it crawling my Pictures directory structured by YYYY/MM. The > collection contains 27000+ jpgs, photos in some other formats > (including raw and nef) and some video. I am quite impressed with the > performance of this program, which handles such a large collection > really well. > > However, the auto import makes it to 25794 photos and then stops. > Restarting the program to import the last pictures does not help. It > claims to do 32% of the remaining files, but stops and does not update > the "25794" number. My guess is that I have some bad file in there, > but without knowing what actually happens during the import, the > problem is difficult to locate. > > My question is, how do I move forward and find out what is going on? > Can Shotwell do logging or print debug info somehow? > > Best regards, > Andreas > > shotwell 0.8.1 > Arch Linux 64-bit > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From egidijus.kamarauskas at gmail.com Tue Feb 1 09:34:04 2011 From: egidijus.kamarauskas at gmail.com (Egidijus Kamarauskas) Date: Tue, 01 Feb 2011 11:34:04 +0200 Subject: [Shotwell] Shotwell can not start Message-ID: <4D47D38C.70800@gmail.com> Hallo. Where I can find a debug version of Shotwell? Until now I can not run Shotwell. I can not self resolve this problem - not enough Information about running process.. Best Regards Egis. From vera at yorba.org Tue Feb 1 19:52:57 2011 From: vera at yorba.org (Vera Yin) Date: Tue, 1 Feb 2011 11:52:57 -0800 Subject: [Shotwell] shotwell does not start In-Reply-To: <1296393055.8366.7.camel@Bacila> References: <1296393055.8366.7.camel@Bacila> Message-ID: Hi Egidijus, If you could follow these instructions and send back the two files, it would help us diagnose the problem: http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit Thanks, Vera On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas wrote: > Hello > I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. > I can not start shotwell. When i send ?shotwell? to a terminal, i see > this error > "Unique-DBus-WARNING **: Error while sending message: Did not receive a > reply. Possible causes include: the remote application did not send a > reply, the message bus security policy blocked the reply, the reply > timeout expired, or the network connection was broken." > And I see, that shotwell is using about a 600 MB of RAM, and between > 70-80 percent of CPU. > This error occures after 10 - 20 minutes after sending a command to a > terminal. > I have only security updates enabled. > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From jim at yorba.org Tue Feb 1 19:59:01 2011 From: jim at yorba.org (Jim Nelson) Date: Tue, 1 Feb 2011 11:59:01 -0800 Subject: [Shotwell] Assertion failure on Ubuntu 10.10 with 0.8.1 PPA In-Reply-To: <4D4710BE.9010005@thorslund.org> References: <4D4710BE.9010005@thorslund.org> Message-ID: Are you running Shotwell with any command-line parameters? -- Jim On Mon, Jan 31, 2011 at 11:42 AM, Gustaf Thorslund wrote: > Hi, > > When trying to start shotwell I'm now getting: > --> > ** > ERROR:DatabaseTables.vala:567:version_table_construct: assertion failed: > (res == SQLITE_OK) > --> > > I'm using the 0.8.1 PPA on Ubuntu 10.10. > > Any hints on this? Any more debugging/traces interesting? > > /Gustaf > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From jim at yorba.org Tue Feb 1 20:02:12 2011 From: jim at yorba.org (Jim Nelson) Date: Tue, 1 Feb 2011 12:02:12 -0800 Subject: [Shotwell] Auto-import stops prematurely - how to trace problem? In-Reply-To: References: Message-ID: If you run Shotwell like this: $ SHOTWELL_LOG=1 shotwell When you exit Shotwell, send this file: ~/.cache/shotwell/shotwell.log That might give us a hint which file is causing the problem. -- Jim On Mon, Jan 31, 2011 at 4:34 PM, Andreas Wallberg < andreas.wallberg at gmail.com> wrote: > Hi all! > > I am trying to import a large photo collection into Shotwell by having > it crawling my Pictures directory structured by YYYY/MM. The > collection contains 27000+ jpgs, photos in some other formats > (including raw and nef) and some video. I am quite impressed with the > performance of this program, which handles such a large collection > really well. > > However, the auto import makes it to 25794 photos and then stops. > Restarting the program to import the last pictures does not help. It > claims to do 32% of the remaining files, but stops and does not update > the "25794" number. My guess is that I have some bad file in there, > but without knowing what actually happens during the import, the > problem is difficult to locate. > > My question is, how do I move forward and find out what is going on? > Can Shotwell do logging or print debug info somehow? > > Best regards, > Andreas > > shotwell 0.8.1 > Arch Linux 64-bit > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From gustaf at thorslund.org Tue Feb 1 20:13:45 2011 From: gustaf at thorslund.org (Gustaf Thorslund) Date: Tue, 01 Feb 2011 21:13:45 +0100 Subject: [Shotwell] Assertion failure on Ubuntu 10.10 with 0.8.1 PPA In-Reply-To: References: <4D4710BE.9010005@thorslund.org> Message-ID: <4D486979.9050801@thorslund.org> Jim Nelson wrote at 2011-02-01 11:59:01 -0800 > Are you running Shotwell with any command-line parameters? No, and after restoring an old copy of my .shotwell directory it works again. I have the non working copy of my .shotwell directory too if I should try something out, else it's working fine again. /Gustaf From jim at yorba.org Tue Feb 1 20:28:25 2011 From: jim at yorba.org (Jim Nelson) Date: Tue, 1 Feb 2011 12:28:25 -0800 Subject: [Shotwell] Assertion failure on Ubuntu 10.10 with 0.8.1 PPA In-Reply-To: <4D486979.9050801@thorslund.org> References: <4D4710BE.9010005@thorslund.org> <4D486979.9050801@thorslund.org> Message-ID: Two immediate possibilities I see: 1. You didn't have proper writer permissions set on the old .shotwell directory. 2. The database was corrupted for some reason. Could you archive the entire old .shotwell directory and send it to me? That might give me a clue what happened here. -- Jim On Tue, Feb 1, 2011 at 12:13 PM, Gustaf Thorslund wrote: > Jim Nelson wrote at 2011-02-01 11:59:01 -0800 > > Are you running Shotwell with any command-line parameters? > > No, and after restoring an old copy of my .shotwell directory it works > again. I have the non working copy of my .shotwell directory too if I > should try something out, else it's working fine again. > > /Gustaf > > From guiyou65 at gmail.com Tue Feb 1 21:33:42 2011 From: guiyou65 at gmail.com (Thierry Le Guillou) Date: Tue, 01 Feb 2011 22:33:42 +0100 Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: <1296516625049-32909.post@talk.nabble.com> References: <1296516625049-32909.post@talk.nabble.com> Message-ID: <4D487C36.10002@gmail.com> I globaly agree with Harald. Needs to be examined closer. Thierry Le 01/02/2011 00:30, Harald Franzen a ?crit : > First off, a big round of applause to the people behind Shotwell! I for one > -but I won't be alone- was amazed at the light-weightedness and the speed of > Shotwell! Oh what a bliss :-) > > Well, I'll not beat around the bush: > > My two cents: > The systems of "events" and "tags" in my not so humble opinion are two sides > of the same medal; I might be way off, but by my reckoning I can divvy up > any photo collection by applying "what", "where" and "when" to every > picture; I think I'd pretty much be sorted. > > In Shotwell, the "what" (event) mimicks the "when" (date) -and I've read > more than one comment here that this is in effect experienced as such by > people using Shotwell. Events -as currently implemented- don't add much; > more often than not for me, several "events" have been photographed on any > day where Shotwell treats them as one single event. But Shotwell is more > than capable of dealing with the "when"; it's what you get out of the EXIF > information in each file... > > 1) So my feature request would be to be able to separate the tags into > "headers" (and I personally would set it up as described above; what, where > and when). I'd be the first to admit this is a nice-to-have :-) > 2) My second feature request would be for the tags to be able to be > drag-and-dropped onto a (selection of) photos, so I don't have to retype > them all the time (so if I am looking for "Christmas" I know I am not > looking for "X-Mas" or "XMAS" at the same time too). > 3) If I could tag any photo in the "what", "where", "when" way, I'd be able > to retrieve any photo by it too, so I *know* I am looking for this great > picture taken in 2006 -or maybe 2005?, where Phil was in it, but Mary wasn't > and I am quite sure it was at *their* house too and wasn't this at their > wedding anniversary? It's not the archiving, it's the retrieving which is > the magical part :-) > > Having said that: I moved from 0.7.x (Ubuntu Maverick Meerkat) to 0.8.1. > (via your repos) today and was amazed at the amount of progress having been > made! Keep up the good work and thank you! From egidijus.kamarauskas at gmail.com Tue Feb 1 22:20:37 2011 From: egidijus.kamarauskas at gmail.com (Egidijus Kamarauskas) Date: Wed, 02 Feb 2011 00:20:37 +0200 Subject: [Shotwell] shotwell does not start In-Reply-To: References: <1296393055.8366.7.camel@Bacila> Message-ID: <4D488735.2010004@gmail.com> Hallo. I have attached required files of logs and one screen-shot from a Gnome system monitor, to illustrate my problem. On my machine is Ubuntu 10.10 running, 64 bit. Shotwell version is 0.8.1, from PPA. A little bit of explanation - when I haved a Shotwell version, that comes with Ubuntu 10.10, Shotwell stops working without any reason with this error : " Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken " Then I have tried to update Shotwell to 0.8.1 version from PPA. Now Shotwell simply does not start without any errors. Best Regards. 2011.02.01 21:52, Vera Yin ra??: > Hi Egidijus, > > If you could follow these instructions and send back the two files, it > would help us diagnose the problem: > > http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit > > Thanks, > Vera > > On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas > wrote: >> Hello >> I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. >> I can not start shotwell. When i send ?shotwell? to a terminal, i see >> this error >> "Unique-DBus-WARNING **: Error while sending message: Did not receive a >> reply. Possible causes include: the remote application did not send a >> reply, the message bus security policy blocked the reply, the reply >> timeout expired, or the network connection was broken." >> And I see, that shotwell is using about a 600 MB of RAM, and between >> 70-80 percent of CPU. >> This error occures after 10 - 20 minutes after sending a command to a >> terminal. >> I have only security updates enabled. >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> From vera at yorba.org Tue Feb 1 22:44:20 2011 From: vera at yorba.org (Vera Yin) Date: Tue, 1 Feb 2011 14:44:20 -0800 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: <4D428FD3.6030806@a-little-bit.de> References: <4D428FD3.6030806@a-little-bit.de> Message-ID: Hi Valeri, Actually, accessing a Shotwell library across a network (and/or by multiple machines) is discouraged. Here is the FAQ entry on that: http://trac.yorba.org/wiki/Shotwell/FAQ#CanIaccessaShotwelllibraryacrossanetworkpossiblyfrommultiplemachines We have a ticket for it: http://trac.yorba.org/ticket/1292. Regards, Vera On Fri, Jan 28, 2011 at 1:43 AM, Valeri Geiser wrote: > Hi, > > I am looking for a picture management software and like the look and feel of > shotwell a lot. One of my requirements though is to store the database on a > central place (fileserver) since there are multiple PCs that need access to > the same database. I did not find any command line parameters or settings so > far to do that. > I am trying Shotwell 0.5.0 on Ubuntu. > > Best regards, > ?Valeri > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From vera at yorba.org Wed Feb 2 01:14:42 2011 From: vera at yorba.org (Vera Yin) Date: Tue, 1 Feb 2011 17:14:42 -0800 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> <4D4290BE.2020103@googlemail.com> Message-ID: Hi Paulo, Which version of Shotwell are you using? I believe in 0.8.1 you can do the following: 1) move the .shotwell and Pictures directories to the new locations 2) launch Shotwell specifying the .shotwell location with -d (or as user 'photos'). At this point your entire library (if previously all located in ~pmatos/Pictures) will be on the Missing Photos page. 3) go to Edit->Preferences and change the Library Location to the new Pictures directory 4) under the Library Location enable 'Watch library directory for new files'. Now Shotwell should find and restore everything from Missing Photos to the Photo library. Regards, Vera On Tue, Feb 1, 2011 at 12:13 AM, Paulo J. Matos wrote: > > That's great to know. What's the best way to move an existing database and > photo archive into a new directory? > > I want to move ~pmatos/.shotwell and ~pmatos/Pictures into ~photos/.shotwell > and ~photos/Pictures respectively. > > Any tips? > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From valeri at a-little-bit.de Wed Feb 2 06:58:57 2011 From: valeri at a-little-bit.de (Valeri Geiser) Date: Wed, 2 Feb 2011 07:58:57 +0100 (CET) Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> Message-ID: Hi Vera, I assume inconsistencies will only occur when you access the database at the same time, correct? My goal is to have it available from multiple PCs, but not to "edit" at the same time. Would that be risky? Best regards, Valeri > Actually, accessing a Shotwell library across a network (and/or by > multiple machines) is discouraged. Here is the FAQ entry on that: > > http://trac.yorba.org/wiki/Shotwell/FAQ#CanIaccessaShotwelllibraryacrossanetworkpossiblyfrommultiplemachines > > We have a ticket for it: http://trac.yorba.org/ticket/1292. > > Regards, > Vera > > On Fri, Jan 28, 2011 at 1:43 AM, Valeri Geiser > wrote: >> Hi, >> >> I am looking for a picture management software and like the look and >> feel of >> shotwell a lot. One of my requirements though is to store the database >> on a >> central place (fileserver) since there are multiple PCs that need access >> to >> the same database. I did not find any command line parameters or >> settings so >> far to do that. >> I am trying Shotwell 0.5.0 on Ubuntu. >> >> Best regards, >> ?Valeri >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> > From jim at yorba.org Wed Feb 2 18:18:27 2011 From: jim at yorba.org (Jim Nelson) Date: Wed, 2 Feb 2011 10:18:27 -0800 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> Message-ID: The problem of database inconsistency can occur for any number of reasons, not just editing photos. We do have a ticket for opening the database in a read-only mode: http://trac.yorba.org/ticket/3048 -- Jim On Tue, Feb 1, 2011 at 10:58 PM, Valeri Geiser wrote: > Hi Vera, > > I assume inconsistencies will only occur when you access the database at > the same time, correct? My goal is to have it available from multiple PCs, > but not to "edit" at the same time. Would that be risky? > > Best regards, > Valeri > > > Actually, accessing a Shotwell library across a network (and/or by > > multiple machines) is discouraged. Here is the FAQ entry on that: > > > > > http://trac.yorba.org/wiki/Shotwell/FAQ#CanIaccessaShotwelllibraryacrossanetworkpossiblyfrommultiplemachines > > > > We have a ticket for it: http://trac.yorba.org/ticket/1292. > > > > Regards, > > Vera > > > > On Fri, Jan 28, 2011 at 1:43 AM, Valeri Geiser > > wrote: > >> Hi, > >> > >> I am looking for a picture management software and like the look and > >> feel of > >> shotwell a lot. One of my requirements though is to store the database > >> on a > >> central place (fileserver) since there are multiple PCs that need access > >> to > >> the same database. I did not find any command line parameters or > >> settings so > >> far to do that. > >> I am trying Shotwell 0.5.0 on Ubuntu. > >> > >> Best regards, > >> Valeri > >> _______________________________________________ > >> 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 jim at yorba.org Wed Feb 2 18:19:37 2011 From: jim at yorba.org (Jim Nelson) Date: Wed, 2 Feb 2011 10:19:37 -0800 Subject: [Shotwell] shotwell does not start In-Reply-To: <4D488735.2010004@gmail.com> References: <1296393055.8366.7.camel@Bacila> <4D488735.2010004@gmail.com> Message-ID: Hello, I'm not sure I understand your last email. Are you saying that now Shotwell runs fine? -- Jim On Tue, Feb 1, 2011 at 2:20 PM, Egidijus Kamarauskas < egidijus.kamarauskas at gmail.com> wrote: > Hallo. > I have attached required files of logs and one screen-shot from a Gnome > system monitor, to illustrate my problem. > On my machine is Ubuntu 10.10 running, 64 bit. > Shotwell version is 0.8.1, from PPA. > A little bit of explanation - when I haved a Shotwell version, that comes > with Ubuntu 10.10, Shotwell stops working without any reason with this error > : " > > > Unique-DBus-WARNING **: Error while sending message: Did not receive a > reply. Possible causes include: the remote application did not send a > reply, the message bus security policy blocked the reply, the reply > timeout expired, or the network connection was broken > > " > Then I have tried to update Shotwell to 0.8.1 version from PPA. Now > Shotwell simply does not start without any errors. > Best Regards. > > > > 2011.02.01 21:52, Vera Yin ra??: > > Hi Egidijus, >> >> If you could follow these instructions and send back the two files, it >> would help us diagnose the problem: >> >> >> http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit >> >> Thanks, >> Vera >> >> On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas >> wrote: >> >>> Hello >>> I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. >>> I can not start shotwell. When i send ?shotwell? to a terminal, i see >>> this error >>> "Unique-DBus-WARNING **: Error while sending message: Did not receive a >>> reply. Possible causes include: the remote application did not send a >>> reply, the message bus security policy blocked the reply, the reply >>> timeout expired, or the network connection was broken." >>> And I see, that shotwell is using about a 600 MB of RAM, and between >>> 70-80 percent of CPU. >>> This error occures after 10 - 20 minutes after sending a command to a >>> terminal. >>> I have only security updates enabled. >>> >>> _______________________________________________ >>> 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 egidijus.kamarauskas at gmail.com Wed Feb 2 18:35:25 2011 From: egidijus.kamarauskas at gmail.com (Egidijus Kamarauskas) Date: Wed, 02 Feb 2011 20:35:25 +0200 Subject: [Shotwell] shotwell does not start In-Reply-To: References: <1296393055.8366.7.camel@Bacila> <4D488735.2010004@gmail.com> Message-ID: <4D49A3ED.6090200@gmail.com> Hello Excuse me for a very unclear explanation of my situation. 1) I installed Ubuntu 10.10. Shotwell was operate very well. 2) After regular updates from official repos, Shotwell does not started. In a terminal a error was displayed, related to a unique-DBus-WARNING**: .... 3) I have tried to update Shotwell to version 0.8.1 from PPA. Now Shotwell does not start, does not run. In a terminal NO errors is displayed. I send logs, that is generated in a situation 3, after updating Shotwell. 2011.02.02 20:19, Jim Nelson ra??: > Hello, > > I'm not sure I understand your last email. Are you saying that now > Shotwell runs fine? > > -- Jim > > On Tue, Feb 1, 2011 at 2:20 PM, Egidijus Kamarauskas > > wrote: > > Hallo. > I have attached required files of logs and one screen-shot from a > Gnome system monitor, to illustrate my problem. > On my machine is Ubuntu 10.10 running, 64 bit. > Shotwell version is 0.8.1, from PPA. > A little bit of explanation - when I haved a Shotwell version, > that comes with Ubuntu 10.10, Shotwell stops working without any > reason with this error : " > > > Unique-DBus-WARNING **: Error while sending message: Did not receive a > reply. Possible causes include: the remote application did not send a > reply, the message bus security policy blocked the reply, the reply > timeout expired, or the network connection was broken > > " > Then I have tried to update Shotwell to 0.8.1 version from PPA. > Now Shotwell simply does not start without any errors. > Best Regards. > > > > 2011.02.01 21:52, Vera Yin ra??: > > Hi Egidijus, > > If you could follow these instructions and send back the two > files, it > would help us diagnose the problem: > > http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit > > Thanks, > Vera > > On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas > > wrote: > > Hello > I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. > I can not start shotwell. When i send ?shotwell? to a > terminal, i see > this error > "Unique-DBus-WARNING **: Error while sending message: Did > not receive a > reply. Possible causes include: the remote application did > not send a > reply, the message bus security policy blocked the reply, > the reply > timeout expired, or the network connection was broken." > And I see, that shotwell is using about a 600 MB of RAM, > and between > 70-80 percent of CPU. > This error occures after 10 - 20 minutes after sending a > command to a > terminal. > I have only security updates enabled. > > _______________________________________________ > 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 adam at yorba.org Wed Feb 2 18:55:37 2011 From: adam at yorba.org (Adam Dingle) Date: Wed, 02 Feb 2011 10:55:37 -0800 Subject: [Shotwell] shotwell does not start In-Reply-To: <4D49A3ED.6090200@gmail.com> References: <1296393055.8366.7.camel@Bacila> <4D488735.2010004@gmail.com> <4D49A3ED.6090200@gmail.com> Message-ID: <4D49A8A9.6060203@yorba.org> Egidijus, given everything you've said, I suspect that something is wrong with the DBus configuration on your system. When Shotwell starts up, it uses a library called libunique to determine if another instance is already running. libunique in turn uses DBus. Something is going wrong with this mechanism on your system, so when you run Shotwell it thinks another instance is running and immediately exits. First, most obviously, I assume you've tried rebooting your system - yes? If a reboot doesn't work, I'd recommend backing up your files and reinstalling Ubuntu 10.10. That will take a couple of hours, but it will almost certainly solve your problem. Otherwise you could try searching the Web for [Unique-DBus-WARNING] to see if you can find a fix from others who've seen this problem. I strongly suspect that the trouble you're seeing is unrelated to Shotwell itself. adam On 02/02/2011 10:35 AM, Egidijus Kamarauskas wrote: > Hello > Excuse me for a very unclear explanation of my situation. > 1) I installed Ubuntu 10.10. Shotwell was operate very well. > 2) After regular updates from official repos, Shotwell does not > started. In a terminal a error was displayed, related to a > unique-DBus-WARNING**: .... > 3) I have tried to update Shotwell to version 0.8.1 from PPA. Now > Shotwell does not start, does not run. In a terminal NO errors is > displayed. > I send logs, that is generated in a situation 3, after updating Shotwell. > > > > > 2011.02.02 20:19, Jim Nelson ra??: >> Hello, >> >> I'm not sure I understand your last email. Are you saying that now >> Shotwell runs fine? >> >> -- Jim >> >> On Tue, Feb 1, 2011 at 2:20 PM, Egidijus Kamarauskas >> > > wrote: >> >> Hallo. >> I have attached required files of logs and one screen-shot from a >> Gnome system monitor, to illustrate my problem. >> On my machine is Ubuntu 10.10 running, 64 bit. >> Shotwell version is 0.8.1, from PPA. >> A little bit of explanation - when I haved a Shotwell version, >> that comes with Ubuntu 10.10, Shotwell stops working without any >> reason with this error : " >> >> >> Unique-DBus-WARNING **: Error while sending message: Did not >> receive a >> reply. Possible causes include: the remote application did not >> send a >> reply, the message bus security policy blocked the reply, the reply >> timeout expired, or the network connection was broken >> >> " >> Then I have tried to update Shotwell to 0.8.1 version from PPA. >> Now Shotwell simply does not start without any errors. >> Best Regards. >> >> >> >> 2011.02.01 21:52, Vera Yin ra??: >> >> Hi Egidijus, >> >> If you could follow these instructions and send back the two >> files, it >> would help us diagnose the problem: >> >> >> http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit >> >> Thanks, >> Vera >> >> On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas >> > > wrote: >> >> Hello >> I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. >> I can not start shotwell. When i send ?shotwell? to a >> terminal, i see >> this error >> "Unique-DBus-WARNING **: Error while sending message: Did >> not receive a >> reply. Possible causes include: the remote application did >> not send a >> reply, the message bus security policy blocked the reply, >> the reply >> timeout expired, or the network connection was broken." >> And I see, that shotwell is using about a 600 MB of RAM, >> and between >> 70-80 percent of CPU. >> This error occures after 10 - 20 minutes after sending a >> command to a >> terminal. >> I have only security updates enabled. >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From egidijus.kamarauskas at gmail.com Wed Feb 2 19:02:47 2011 From: egidijus.kamarauskas at gmail.com (Egidijus Kamarauskas) Date: Wed, 02 Feb 2011 21:02:47 +0200 Subject: [Shotwell] shotwell does not start In-Reply-To: <4D49A8A9.6060203@yorba.org> References: <1296393055.8366.7.camel@Bacila> <4D488735.2010004@gmail.com> <4D49A3ED.6090200@gmail.com> <4D49A8A9.6060203@yorba.org> Message-ID: <4D49AA57.4050503@gmail.com> Emm, it were be a big trouble to re-install my all system... Rebooting does not help. Now, I'll self search a solution. 2011.02.02 20:55, Adam Dingle ra??: > Egidijus, > > given everything you've said, I suspect that something is wrong with > the DBus configuration on your system. When Shotwell starts up, it > uses a library called libunique to determine if another instance is > already running. libunique in turn uses DBus. Something is going > wrong with this mechanism on your system, so when you run Shotwell it > thinks another instance is running and immediately exits. > > First, most obviously, I assume you've tried rebooting your system - yes? > > If a reboot doesn't work, I'd recommend backing up your files and > reinstalling Ubuntu 10.10. That will take a couple of hours, but it > will almost certainly solve your problem. Otherwise you could try > searching the Web for [Unique-DBus-WARNING] to see if you can find a > fix from others who've seen this problem. I strongly suspect that the > trouble you're seeing is unrelated to Shotwell itself. > > adam > > On 02/02/2011 10:35 AM, Egidijus Kamarauskas wrote: >> Hello >> Excuse me for a very unclear explanation of my situation. >> 1) I installed Ubuntu 10.10. Shotwell was operate very well. >> 2) After regular updates from official repos, Shotwell does not >> started. In a terminal a error was displayed, related to a >> unique-DBus-WARNING**: .... >> 3) I have tried to update Shotwell to version 0.8.1 from PPA. Now >> Shotwell does not start, does not run. In a terminal NO errors is >> displayed. >> I send logs, that is generated in a situation 3, after updating >> Shotwell. >> >> >> >> >> 2011.02.02 20:19, Jim Nelson ra??: >>> Hello, >>> >>> I'm not sure I understand your last email. Are you saying that now >>> Shotwell runs fine? >>> >>> -- Jim >>> >>> On Tue, Feb 1, 2011 at 2:20 PM, Egidijus Kamarauskas >>> >> > wrote: >>> >>> Hallo. >>> I have attached required files of logs and one screen-shot from a >>> Gnome system monitor, to illustrate my problem. >>> On my machine is Ubuntu 10.10 running, 64 bit. >>> Shotwell version is 0.8.1, from PPA. >>> A little bit of explanation - when I haved a Shotwell version, >>> that comes with Ubuntu 10.10, Shotwell stops working without any >>> reason with this error : " >>> >>> >>> Unique-DBus-WARNING **: Error while sending message: Did not >>> receive a >>> reply. Possible causes include: the remote application did not >>> send a >>> reply, the message bus security policy blocked the reply, the reply >>> timeout expired, or the network connection was broken >>> >>> " >>> Then I have tried to update Shotwell to 0.8.1 version from PPA. >>> Now Shotwell simply does not start without any errors. >>> Best Regards. >>> >>> >>> >>> 2011.02.01 21:52, Vera Yin ra??: >>> >>> Hi Egidijus, >>> >>> If you could follow these instructions and send back the two >>> files, it >>> would help us diagnose the problem: >>> >>> >>> http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit >>> >>> Thanks, >>> Vera >>> >>> On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas >>> >> > wrote: >>> >>> Hello >>> I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. >>> I can not start shotwell. When i send ?shotwell? to a >>> terminal, i see >>> this error >>> "Unique-DBus-WARNING **: Error while sending message: Did >>> not receive a >>> reply. Possible causes include: the remote application did >>> not send a >>> reply, the message bus security policy blocked the reply, >>> the reply >>> timeout expired, or the network connection was broken." >>> And I see, that shotwell is using about a 600 MB of RAM, >>> and between >>> 70-80 percent of CPU. >>> This error occures after 10 - 20 minutes after sending a >>> command to a >>> terminal. >>> I have only security updates enabled. >>> >>> _______________________________________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> >>> >>> _______________________________________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From valeri at a-little-bit.de Wed Feb 2 19:39:42 2011 From: valeri at a-little-bit.de (Valeri Geiser) Date: Wed, 02 Feb 2011 20:39:42 +0100 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> Message-ID: <4D49B2FE.20502@a-little-bit.de> Jim, with "edit" I meant Tagging etc., not photo editing. So I am a little bit baffled, that I should not be able to open it - or do you write anything to the database like access times etc.? If not, then at least opening it one at a time should be ok - if not, please let me know. Best regards, Valeri > The problem of database inconsistency can occur for any number of > reasons, not just editing photos. We do have a ticket for opening the > database in a read-only mode: http://trac.yorba.org/ticket/3048 > > -- Jim > > On Tue, Feb 1, 2011 at 10:58 PM, Valeri Geiser > wrote: > > Hi Vera, > > I assume inconsistencies will only occur when you access the > database at > the same time, correct? My goal is to have it available from > multiple PCs, > but not to "edit" at the same time. Would that be risky? > > Best regards, > Valeri > > > Actually, accessing a Shotwell library across a network (and/or by > > multiple machines) is discouraged. Here is the FAQ entry on that: > > > > > http://trac.yorba.org/wiki/Shotwell/FAQ#CanIaccessaShotwelllibraryacrossanetworkpossiblyfrommultiplemachines > > > > We have a ticket for it: http://trac.yorba.org/ticket/1292. > > > > Regards, > > Vera > > > > On Fri, Jan 28, 2011 at 1:43 AM, Valeri Geiser > > > > wrote: > >> Hi, > >> > >> I am looking for a picture management software and like the > look and > >> feel of > >> shotwell a lot. One of my requirements though is to store the > database > >> on a > >> central place (fileserver) since there are multiple PCs that > need access > >> to > >> the same database. I did not find any command line parameters or > >> settings so > >> far to do that. > >> I am trying Shotwell 0.5.0 on Ubuntu. > >> > >> Best regards, > >> Valeri > >> _______________________________________________ > >> 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 jim at yorba.org Wed Feb 2 23:10:39 2011 From: jim at yorba.org (Jim Nelson) Date: Wed, 2 Feb 2011 15:10:39 -0800 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: <4D49B2FE.20502@a-little-bit.de> References: <4D428FD3.6030806@a-little-bit.de> <4D49B2FE.20502@a-little-bit.de> Message-ID: We don't write access times, but there are background processes in Shotwell, such as runtime monitoring. If the library detects a change on the filesystem it may update the database without you doing a thing. The larger issue here is we've done no work or testing to verify that what you're asking for is okay, and we never designed Shotwell for this kind of use case. In theory it sounds like it should be okay, but in practice there could be problems. -- Jim On Wed, Feb 2, 2011 at 11:39 AM, Valeri Geiser wrote: > Jim, > > with "edit" I meant Tagging etc., not photo editing. So I am a little bit > baffled, that I should not be able to open it - or do you write anything to > the database like access times etc.? If not, then at least opening it one at > a time should be ok - if not, please let me know. > > Best regards, > Valeri > > > The problem of database inconsistency can occur for any number of reasons, > not just editing photos. We do have a ticket for opening the database in a > read-only mode: http://trac.yorba.org/ticket/3048 > > -- Jim > > On Tue, Feb 1, 2011 at 10:58 PM, Valeri Geiser wrote: > >> Hi Vera, >> >> I assume inconsistencies will only occur when you access the database at >> the same time, correct? My goal is to have it available from multiple PCs, >> but not to "edit" at the same time. Would that be risky? >> >> Best regards, >> Valeri >> >> > Actually, accessing a Shotwell library across a network (and/or by >> > multiple machines) is discouraged. Here is the FAQ entry on that: >> > >> > >> http://trac.yorba.org/wiki/Shotwell/FAQ#CanIaccessaShotwelllibraryacrossanetworkpossiblyfrommultiplemachines >> > >> > We have a ticket for it: http://trac.yorba.org/ticket/1292. >> > >> > Regards, >> > Vera >> > >> > On Fri, Jan 28, 2011 at 1:43 AM, Valeri Geiser >> > wrote: >> >> Hi, >> >> >> >> I am looking for a picture management software and like the look and >> >> feel of >> >> shotwell a lot. One of my requirements though is to store the database >> >> on a >> >> central place (fileserver) since there are multiple PCs that need >> access >> >> to >> >> the same database. I did not find any command line parameters or >> >> settings so >> >> far to do that. >> >> I am trying Shotwell 0.5.0 on Ubuntu. >> >> >> >> Best regards, >> >> Valeri >> >> _______________________________________________ >> >> 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 joseph.bylund at gmail.com Wed Feb 2 18:36:04 2011 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Wed, 02 Feb 2011 13:36:04 -0500 Subject: [Shotwell] shotwell does not start In-Reply-To: <4D49A3ED.6090200@gmail.com> References: <1296393055.8366.7.camel@Bacila> <4D488735.2010004@gmail.com> <4D49A3ED.6090200@gmail.com> Message-ID: <4D49A414.8050101@gmail.com> Looks like that's a symptom of the same problem as this bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/379183 I've also seen a few reports of the same bug when using gedit. But in either case I think it's a bug with something other than shotwell. Perhaps you should add a comment on the bug there? Egidijus Kamarauskas wrote: > Hello > Excuse me for a very unclear explanation of my situation. > 1) I installed Ubuntu 10.10. Shotwell was operate very well. > 2) After regular updates from official repos, Shotwell does not > started. In a terminal a error was displayed, related to a > unique-DBus-WARNING**: .... > 3) I have tried to update Shotwell to version 0.8.1 from PPA. Now > Shotwell does not start, does not run. In a terminal NO errors is > displayed. > I send logs, that is generated in a situation 3, after updating Shotwell. > > > > > 2011.02.02 20:19, Jim Nelson ra??: >> Hello, >> >> I'm not sure I understand your last email. Are you saying that now >> Shotwell runs fine? >> >> -- Jim >> >> On Tue, Feb 1, 2011 at 2:20 PM, Egidijus Kamarauskas >> > > wrote: >> >> Hallo. >> I have attached required files of logs and one screen-shot from a >> Gnome system monitor, to illustrate my problem. >> On my machine is Ubuntu 10.10 running, 64 bit. >> Shotwell version is 0.8.1, from PPA. >> A little bit of explanation - when I haved a Shotwell version, >> that comes with Ubuntu 10.10, Shotwell stops working without any >> reason with this error : " >> >> >> Unique-DBus-WARNING **: Error while sending message: Did not >> receive a >> reply. Possible causes include: the remote application did not >> send a >> reply, the message bus security policy blocked the reply, the reply >> timeout expired, or the network connection was broken >> >> " >> Then I have tried to update Shotwell to 0.8.1 version from PPA. >> Now Shotwell simply does not start without any errors. >> Best Regards. >> >> >> >> 2011.02.01 21:52, Vera Yin ra??: >> >> Hi Egidijus, >> >> If you could follow these instructions and send back the two >> files, it >> would help us diagnose the problem: >> >> >> http://trac.yorba.org/wiki/Shotwell/FAQ#IfoundabuginShotwell.HowcanIreportit >> >> Thanks, >> Vera >> >> On Sun, Jan 30, 2011 at 5:10 AM, Egidijus Kamarauskas >> > > wrote: >> >> Hello >> I'm using Ubuntu 10.10 and shotwell 0.8.1 from ppa. >> I can not start shotwell. When i send ?shotwell? to a >> terminal, i see >> this error >> "Unique-DBus-WARNING **: Error while sending message: Did >> not receive a >> reply. Possible causes include: the remote application did >> not send a >> reply, the message bus security policy blocked the reply, >> the reply >> timeout expired, or the network connection was broken." >> And I see, that shotwell is using about a 600 MB of RAM, >> and between >> 70-80 percent of CPU. >> This error occures after 10 - 20 minutes after sending a >> command to a >> terminal. >> I have only security updates enabled. >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From vera at yorba.org Fri Feb 4 00:20:51 2011 From: vera at yorba.org (Vera Yin) Date: Thu, 3 Feb 2011 16:20:51 -0800 Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: <1296516625049-32909.post@talk.nabble.com> References: <1296516625049-32909.post@talk.nabble.com> Message-ID: Hi Harald, > First off, a big round of applause to the people behind Shotwell! I for one > -but I won't be alone- was amazed at the light-weightedness and the speed of > Shotwell! Oh what a bliss :-) Thanks - we're very happy you like Shotwell! > Well, I'll not beat around the bush: > > My two cents: > The systems of "events" and "tags" in my not so humble opinion are two sides > of the same medal; I might be way off, but by my reckoning I can divvy up > any photo collection by applying "what", "where" and "when" to every > picture; I think I'd pretty much be sorted. > > In Shotwell, the "what" (event) mimicks the "when" (date) -and I've read > more than one comment here that this is in effect experienced as such by > people using Shotwell. ?Events -as currently implemented- don't add much; > more often than not for me, several "events" have been photographed on any > day where Shotwell treats them as one single event. But Shotwell is more > than capable of dealing with the "when"; it's what you get out of the EXIF > information in each file... Events are a bit more flexible than that - you can create your own events by highlighting a group of photos and selecting Events->New Event or pressing Ctrl-N. You can also combine events by highlighting a group of events on the Events page and selecting Events->Merge Events. > 1) So my feature request would be to be able to separate the tags into > "headers" (and I personally would set it up as described above; what, where > and when). I'd be the first to admit this is a nice-to-have :-) We've had many requests for hierarchical tags and we're hoping to implement that for 0.9: http://trac.yorba.org/ticket/1401. > 2) My second feature request would be for the tags to be able to be > drag-and-dropped onto a (selection of) photos, so I don't have to retype > them all the time (so if I am looking for "Christmas" I know I am not > looking for "X-Mas" or "XMAS" at the same time too). You can drag photos onto a tag to associate that tag with those photos. There is also auto-completion in the Add Tags and Modify Tags dialog boxes. > 3) If I could tag any photo in the "what", "where", "when" way, I'd be able > to retrieve any photo by it too, so I *know* I am looking for this great > picture taken in 2006 -or maybe 2005?, where Phil was in it, but Mary wasn't > and I am quite sure it was at *their* house too and wasn't this at their > wedding anniversary? It's not the archiving, it's the retrieving which is > the magical part :-) We also have a search filter toolbar in the works: http://trac.yorba.org/ticket/3100 and http://trac.yorba.org/ticket/1587. > Having said that: I moved from 0.7.x (Ubuntu Maverick Meerkat) to 0.8.1. > (via your repos) today and was amazed at the amount of progress having been > made! Keep up the good work and thank you! Thanks again! Regards, Vera From kahing at gmail.com Fri Feb 4 04:13:34 2011 From: kahing at gmail.com (Ka-Hing Cheung) Date: Thu, 3 Feb 2011 20:13:34 -0800 Subject: [Shotwell] rawtherapee as raw editor Message-ID: Is there a way to set rawtherapee as the raw editor? It's not available in the dropdown list in preference however it's installed. shotwell version is 0.8.1 from ubuntu ppa and rawtherapee is 3.0 alpha 1. Distribution is ubuntu maverick. thanks, ps I am not subscribed. From harald.franzen at lotcavediving.eu Fri Feb 4 09:19:08 2011 From: harald.franzen at lotcavediving.eu (Harald Franzen) Date: Fri, 4 Feb 2011 01:19:08 -0800 (PST) Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: References: <1296516625049-32909.post@talk.nabble.com> Message-ID: <1296811148709-32992.post@talk.nabble.com> Thank you Vera for taking the time to write such a comprehensive reply! Cheers, Harald -- View this message in context: http://shotwell.3510.www.nabble.com/Three-feature-requests-tp32909p32992.html Sent from the Shotwell mailing list archive at Nabble.com. From menulio.svytuokle at gmail.com Fri Feb 4 17:06:58 2011 From: menulio.svytuokle at gmail.com (=?UTF-8?B?TcSXbnVsaW8gxaB2eXR1b2tsxJc=?=) Date: Fri, 04 Feb 2011 19:06:58 +0200 Subject: [Shotwell] Shotwell 0.8.1 from PPA uses 3 GB RAM and does not start. Message-ID: <4D4C3232.4050106@gmail.com> Hallo. I'm using Ubuntu 10.10 64 bit on my machine. I have tried to install Shotwell from PPA, version 0.8.1. Shotwell starts but immediately window goes blank (see screen-shot) and Shotwell uses a 3 GB amount of RAM. I have tried to debug. I have attached shotwell.log and shotwell.gdb. How I can solve this problem? Best Regards. From vera at yorba.org Fri Feb 4 19:28:36 2011 From: vera at yorba.org (Vera Yin) Date: Fri, 4 Feb 2011 11:28:36 -0800 Subject: [Shotwell] Shotwell 0.8.1 from PPA uses 3 GB RAM and does not start. In-Reply-To: <4D4C3232.4050106@gmail.com> References: <4D4C3232.4050106@gmail.com> Message-ID: Hi M?nulio, This mailing list doesn't allow attachments so your shotwell.log and shotwell.gdb didn't go through. Could you instead send those files to us at ? Thanks, Vera 2011/2/4 M?nulio ?vytuokl? : > Hallo. > I'm using Ubuntu 10.10 64 bit on my machine. > I have tried to install Shotwell from PPA, version 0.8.1. Shotwell starts > but immediately window goes blank (see screen-shot) and Shotwell uses a 3 GB > amount of RAM. I have tried to debug. I have attached shotwell.log and > shotwell.gdb. > How I can solve this problem? > Best Regards. > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > From vera at yorba.org Fri Feb 4 19:41:29 2011 From: vera at yorba.org (Vera Yin) Date: Fri, 4 Feb 2011 11:41:29 -0800 Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: References: <1296516625049-32909.post@talk.nabble.com> Message-ID: On Thu, Feb 3, 2011 at 4:20 PM, Vera Yin wrote: >> 1) So my feature request would be to be able to separate the tags into >> "headers" (and I personally would set it up as described above; what, where >> and when). I'd be the first to admit this is a nice-to-have :-) > > We've had many requests for hierarchical tags and we're hoping to > implement that for 0.9: http://trac.yorba.org/ticket/1401. Actually, I wasn't aware but hierarchical tags won't make it into 0.9. We're hoping to implement it for 0.10! Regards, Vera From vera at yorba.org Fri Feb 4 20:46:42 2011 From: vera at yorba.org (Vera Yin) Date: Fri, 4 Feb 2011 12:46:42 -0800 Subject: [Shotwell] rawtherapee as raw editor In-Reply-To: References: Message-ID: Hi Ka-hing, The editors in the dropdown box are from the list of programs associated with the image type. If you go into Nautilus, select a RAW image, click File -> Properties, and add RAWTherapee, it will appear in the Shotwell list. Regards, Vera On Thu, Feb 3, 2011 at 8:13 PM, Ka-Hing Cheung wrote: > Is there a way to set rawtherapee as the raw editor? It's not available in > the dropdown list in preference however it's installed. shotwell version is > 0.8.1 from ubuntu ppa and rawtherapee is 3.0 alpha 1. Distribution is ubuntu > maverick. > > thanks, > > ps I am not subscribed. > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From monnier at iro.umontreal.ca Fri Feb 4 15:40:31 2011 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Fri, 04 Feb 2011 10:40:31 -0500 Subject: [Shotwell] Three (!) feature requests ;-) References: <1296516625049-32909.post@talk.nabble.com> Message-ID: > Events are a bit more flexible than that - you can create your own > events by highlighting a group of photos and selecting Events->New > Event or pressing Ctrl-N. You can also combine events by highlighting > a group of events on the Events page and selecting Events->Merge > Events. Indeed. And that's very good. I do wish it were easier to move photos from one event to another after the fact, tho. Currently, I end up having to: - select photos in event-source. - create a new event-temp for them. - merge that event-temp into the event-destination. which is not completely clunky, but seems a bit roundabout, when what I'd like to do, really is to just drag-and-drop the photos into the event folder on the left. Stefan From vera at yorba.org Fri Feb 4 20:59:01 2011 From: vera at yorba.org (Vera Yin) Date: Fri, 4 Feb 2011 12:59:01 -0800 Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: References: <1296516625049-32909.post@talk.nabble.com> Message-ID: Hi Stefan, Thanks for bringing up what I forgot to mention - you *can* drag-and-drop photos into an Event in the sidebar. This and more are explained in our user guide: http://yorba.org/shotwell/help/event.html. Cheers, Vera On Fri, Feb 4, 2011 at 7:40 AM, Stefan Monnier wrote: >> Events are a bit more flexible than that - you can create your own >> events by highlighting a group of photos and selecting Events->New >> Event or pressing Ctrl-N. You can also combine events by highlighting >> a group of events on the Events page and selecting Events->Merge >> Events. > > Indeed. ?And that's very good. ?I do wish it were easier to move photos > from one event to another after the fact, tho. ?Currently, I end up > having to: > - select photos in event-source. > - create a new event-temp for them. > - merge that event-temp into the event-destination. > which is not completely clunky, but seems a bit roundabout, when what > I'd like to do, really is to just drag-and-drop the photos into the > event folder on the left. > > > ? ? ? ?Stefan > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From gorkypl at gmail.com Fri Feb 4 21:20:16 2011 From: gorkypl at gmail.com (=?UTF-8?Q?Pawe=C5=82_Rumian?=) Date: Fri, 4 Feb 2011 22:20:16 +0100 Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: References: <1296516625049-32909.post@talk.nabble.com> Message-ID: Hi all. First of all - I'm really impressed by the speed of development and quality of shotwell. Said that, I must admit that I wholeheartedly agree with the author of this thread - particularly I don't understand the idea behind 'Events'. Wouldn't a kind of timeline be more flexible? In my daily work I often have three or four events during one day, but also events that last as long as one week or month. I know I can merge events and create new ones, but it makes the automatic daily events totally unnecessary, because I'd always have to customize them. Furthermore, the lack of any kind of timeline, which would enable me to restrict displayed photos tho specific range of dates is even more painful. I'm really excited with what you are doing, so don't treat this as a complainment - I just believe that such discussions could make shotwell better. greetings, Pawe? From andreas.wallberg at gmail.com Fri Feb 4 22:37:04 2011 From: andreas.wallberg at gmail.com (Andreas Wallberg) Date: Fri, 4 Feb 2011 23:37:04 +0100 Subject: [Shotwell] Auto-import stops prematurely - how to trace problem? In-Reply-To: References: Message-ID: Hi again! I had a look at the logs but apart from some reports of duplicates that shotwell ignored there was nothing of particular interest. I followed stone keeper's suggestion to move out all video (about 9 gigs from both cell phones and cameras) from the directory tree. Voil?!! Shotwell now imported all photos. I have not tracked down the bad video yet though. Best regards, Andreas On Tue, Feb 1, 2011 at 9:02 PM, Jim Nelson wrote: > If you run Shotwell like this: > > $ SHOTWELL_LOG=1 shotwell > > When you exit Shotwell, send this file: > > ~/.cache/shotwell/shotwell.log > > That might give us a hint which file is causing the problem. > > -- Jim > > On Mon, Jan 31, 2011 at 4:34 PM, Andreas Wallberg > wrote: >> >> Hi all! >> >> I am trying to import a large photo collection into Shotwell by having >> it crawling my Pictures directory structured by YYYY/MM. The >> collection contains 27000+ jpgs, photos in some other formats >> (including raw and nef) and some video. I am quite impressed with the >> performance of this program, which handles such a large collection >> really well. >> >> However, the auto import makes it to 25794 photos and then stops. >> Restarting the program to import the last pictures does not help. It >> claims to do 32% of the remaining files, but stops and does not update >> the "25794" number. My guess is that I have some bad file in there, >> but without knowing what actually happens during the import, the >> problem is difficult to locate. >> >> My question is, how do I move forward and find out what is going on? >> Can Shotwell do logging or print debug info somehow? >> >> Best regards, >> Andreas >> >> shotwell 0.8.1 >> Arch Linux 64-bit >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > From kahing at gmail.com Fri Feb 4 22:48:48 2011 From: kahing at gmail.com (Ka-Hing Cheung) Date: Fri, 4 Feb 2011 14:48:48 -0800 Subject: [Shotwell] rawtherapee as raw editor In-Reply-To: References: Message-ID: On Fri, Feb 4, 2011 at 12:46, Vera Yin wrote: > > Hi Ka-hing, > > The editors in the dropdown box are from the list of programs > associated with the image type. If you go into Nautilus, select a RAW > image, click File -> Properties, and add RAWTherapee, it will appear > in the Shotwell list. Thanks, that worked. From pocmatos at gmail.com Sat Feb 5 09:55:18 2011 From: pocmatos at gmail.com (Paulo J. Matos) Date: Sat, 05 Feb 2011 09:55:18 +0000 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> <4D4290BE.2020103@googlemail.com> Message-ID: Hello Vera, Thanks for the help. I only managed to give it a try now. I am in 0.8.1. Unfortunately it doesn't work. After I change the Library Location to the new Pictures directory and mark the Watch Library option... it shows up on the bottom "Updating Library" and then it stops. Nothing happens. Restarting doesn't work. The paths for the photos in the database are still /home/pmatos/... (previous path) since now should be /home/photos/... I can't really remember the correct sql... but I am sure it is possible to mass change the paths from /home/pmatos/... to /home/photos/... directly on the database. Any tips? On 02/02/11 01:14, Vera Yin wrote: > Hi Paulo, > > Which version of Shotwell are you using? I believe in 0.8.1 you can do > the following: > > 1) move the .shotwell and Pictures directories to the new locations > 2) launch Shotwell specifying the .shotwell location with -d (or as > user 'photos'). At this point your entire library (if previously all > located in ~pmatos/Pictures) will be on the Missing Photos page. > 3) go to Edit->Preferences and change the Library Location to the new > Pictures directory > 4) under the Library Location enable 'Watch library directory for new > files'. Now Shotwell should find and restore everything from Missing > Photos to the Photo library. > > Regards, > Vera > > On Tue, Feb 1, 2011 at 12:13 AM, Paulo J. Matos wrote: >> >> That's great to know. What's the best way to move an existing database and >> photo archive into a new directory? >> >> I want to move ~pmatos/.shotwell and ~pmatos/Pictures into ~photos/.shotwell >> and ~photos/Pictures respectively. >> >> Any tips? >> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> From pocmatos at gmail.com Sat Feb 5 10:08:20 2011 From: pocmatos at gmail.com (Paulo J. Matos) Date: Sat, 05 Feb 2011 10:08:20 +0000 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> <4D4290BE.2020103@googlemail.com> Message-ID: On 02/02/11 01:14, Vera Yin wrote: > Hi Paulo, > > Which version of Shotwell are you using? I believe in 0.8.1 you can do > the following: > > 1) move the .shotwell and Pictures directories to the new locations > 2) launch Shotwell specifying the .shotwell location with -d (or as > user 'photos'). At this point your entire library (if previously all > located in ~pmatos/Pictures) will be on the Missing Photos page. > 3) go to Edit->Preferences and change the Library Location to the new > Pictures directory > 4) under the Library Location enable 'Watch library directory for new > files'. Now Shotwell should find and restore everything from Missing > Photos to the Photo library. > Where are the Preferences kept? I just noticed that they are kept nowhere in the .shotwell directory? Is it a gnome registry thing or something? From gandal71 at gmail.com Sat Feb 5 15:33:06 2011 From: gandal71 at gmail.com (gandal) Date: Sat, 5 Feb 2011 07:33:06 -0800 (PST) Subject: [Shotwell] Writing IPTC tags Message-ID: <1296919986469-33024.post@talk.nabble.com> Hi, I installed Shotwell 0.8.1 (on Xubuntu 10.10) and I'm experiencing some problems with IPTC tags. In Preferences I checked "Write tags, titles, and other metadata to photo files". I noticed that Shotwell doesn't write IPTC keywords in the jpg photos taken with my Canon camera. Only if I write an IPTC keyword in the file using the command: iptc -a Keywords -v "value" "filename.jpg" then Shotwell become able to modify the Keyword into the jpg file. I tested IPTC tags with this command: iptc "filename.jpg" and with XNview under Windows. It seems that Shotwell doesn't write IPTC tags if no IPTC data exists in the file. I'm a bit confused, because in http://trac.yorba.org/ticket/3044 this ticket is said: "Shotwell has a list of metadata tags for each type of metadata (titles, keywords/tags, ratings, etc.) If none of the metadata domains is present for that particular type, it uses the first one in the list regardless if the domain is present or not" -- View this message in context: http://shotwell.3510.www.nabble.com/Writing-IPTC-tags-tp33024p33024.html Sent from the Shotwell mailing list archive at Nabble.com. From baldakkl at gmail.com Sun Feb 6 18:33:00 2011 From: baldakkl at gmail.com (Lorenzo Baldacchini) Date: Sun, 6 Feb 2011 19:33:00 +0100 Subject: [Shotwell] Strange date error Message-ID: Hello everybody, I am trying to compile shotwell from source, obtained via SVN. I have such a strange error with the last version Compiling Vala code... src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' could not be found private GLib.DateTime example_date = new GLib.DateTime.local(2009, 3, 10, 18, 16, 11); ^^^^^^^^^^^^^ src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not be found DateTime date = new DateTime.from_unix_utc(tm); ^^^^^^^^ Compilation failed: 2 error(s), 0 warning(s) make: *** [src/.stamp] Errore 1 What does this mean? I have installed glib2.26 from source to be able to install shotwell. Thanks a lot best regards Lorenzo From adam at yorba.org Mon Feb 7 18:48:12 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 07 Feb 2011 10:48:12 -0800 Subject: [Shotwell] Strange date error In-Reply-To: References: Message-ID: <4D503E6C.1070004@yorba.org> Lorenzo, thanks for your message. I suspect you're using Vala 0.9.8. The Shotwell trunk will no longer build with that version of Vala. I've just updated the Shotwell makefile to check for a minimum of Vala 0.10.0. So if you upgrade to Vala 0.10, you should be able to build. Cheers - adam On 02/06/2011 10:33 AM, Lorenzo Baldacchini wrote: > Hello everybody, > > I am trying to compile shotwell from source, obtained via SVN. > > I have such a strange error with the last version > > Compiling Vala code... > src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' could > not be found > private GLib.DateTime example_date = new GLib.DateTime.local(2009, 3, > 10, 18, 16, 11); > ^^^^^^^^^^^^^ > src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not be > found > DateTime date = new DateTime.from_unix_utc(tm); > ^^^^^^^^ > Compilation failed: 2 error(s), 0 warning(s) > make: *** [src/.stamp] Errore 1 > > > What does this mean? > I have installed glib2.26 from source to be able to install shotwell. > > Thanks a lot > best regards > Lorenzo > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Mon Feb 7 20:53:08 2011 From: jim at yorba.org (Jim Nelson) Date: Mon, 7 Feb 2011 12:53:08 -0800 Subject: [Shotwell] Auto-import stops prematurely - how to trace problem? In-Reply-To: References: Message-ID: We've received a number of bug reports on this: http://trac.yorba.org/ticket/3125 We're looking into some possible fixes for this. We hope to have this fixed in 0.9. -- Jim On Fri, Feb 4, 2011 at 2:37 PM, Andreas Wallberg wrote: > Hi again! > > I had a look at the logs but apart from some reports of duplicates > that shotwell ignored there was nothing of particular interest. > > I followed stone keeper's suggestion to move out all video (about 9 > gigs from both cell phones and cameras) from the directory tree. > Voil?!! Shotwell now imported all photos. I have not tracked down the > bad video yet though. > > Best regards, > Andreas > > On Tue, Feb 1, 2011 at 9:02 PM, Jim Nelson wrote: > > If you run Shotwell like this: > > > > $ SHOTWELL_LOG=1 shotwell > > > > When you exit Shotwell, send this file: > > > > ~/.cache/shotwell/shotwell.log > > > > That might give us a hint which file is causing the problem. > > > > -- Jim > > > > On Mon, Jan 31, 2011 at 4:34 PM, Andreas Wallberg > > wrote: > >> > >> Hi all! > >> > >> I am trying to import a large photo collection into Shotwell by having > >> it crawling my Pictures directory structured by YYYY/MM. The > >> collection contains 27000+ jpgs, photos in some other formats > >> (including raw and nef) and some video. I am quite impressed with the > >> performance of this program, which handles such a large collection > >> really well. > >> > >> However, the auto import makes it to 25794 photos and then stops. > >> Restarting the program to import the last pictures does not help. It > >> claims to do 32% of the remaining files, but stops and does not update > >> the "25794" number. My guess is that I have some bad file in there, > >> but without knowing what actually happens during the import, the > >> problem is difficult to locate. > >> > >> My question is, how do I move forward and find out what is going on? > >> Can Shotwell do logging or print debug info somehow? > >> > >> Best regards, > >> Andreas > >> > >> shotwell 0.8.1 > >> Arch Linux 64-bit > >> _______________________________________________ > >> Shotwell mailing list > >> Shotwell at lists.yorba.org > >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > > > > From baldakkl at gmail.com Mon Feb 7 21:29:50 2011 From: baldakkl at gmail.com (Lorenzo Baldacchini) Date: Mon, 7 Feb 2011 22:29:50 +0100 Subject: [Shotwell] Shotwell Digest, Vol 19, Issue 8 In-Reply-To: References: Message-ID: Hello, I am installing vala 0.10 from source. I suggest to put it in your ppa, since there are two version (or at least is what I have in the software list) 0.98 and 0.11.5, both not good for installing shotwell. Thanks again, anyway, for the perfect work you are doing with shotwell! Regards Lorenzo 2011/2/7 > Send Shotwell mailing list submissions to > shotwell at lists.yorba.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > or, via email, send a message with subject or body 'help' to > shotwell-request at lists.yorba.org > > You can reach the person managing the list at > shotwell-owner at lists.yorba.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Shotwell digest..." > > > Today's Topics: > > 1. Re: Strange date error (Adam Dingle) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 07 Feb 2011 10:48:12 -0800 > From: Adam Dingle > To: shotwell at lists.yorba.org > Subject: Re: [Shotwell] Strange date error > Message-ID: <4D503E6C.1070004 at yorba.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Lorenzo, > > thanks for your message. I suspect you're using Vala 0.9.8. The > Shotwell trunk will no longer build with that version of Vala. I've > just updated the Shotwell makefile to check for a minimum of Vala > 0.10.0. So if you upgrade to Vala 0.10, you should be able to build. > Cheers - > > adam > > On 02/06/2011 10:33 AM, Lorenzo Baldacchini wrote: > > Hello everybody, > > > > I am trying to compile shotwell from source, obtained via SVN. > > > > I have such a strange error with the last version > > > > Compiling Vala code... > > src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' > could > > not be found > > private GLib.DateTime example_date = new GLib.DateTime.local(2009, > 3, > > 10, 18, 16, 11); > > ^^^^^^^^^^^^^ > > src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not be > > found > > DateTime date = new DateTime.from_unix_utc(tm); > > ^^^^^^^^ > > Compilation failed: 2 error(s), 0 warning(s) > > make: *** [src/.stamp] Errore 1 > > > > > > What does this mean? > > I have installed glib2.26 from source to be able to install shotwell. > > > > Thanks a lot > > best regards > > Lorenzo > > _______________________________________________ > > 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 > > > End of Shotwell Digest, Vol 19, Issue 8 > *************************************** > From baldakkl at gmail.com Mon Feb 7 21:32:42 2011 From: baldakkl at gmail.com (Lorenzo Baldacchini) Date: Mon, 7 Feb 2011 22:32:42 +0100 Subject: [Shotwell] Shotwell Digest, Vol 19, Issue 8 In-Reply-To: References: Message-ID: Hello, it is again me with the compiling issue. I have correctly installed vala 0.10, but still shotwell does not compile. It doesn't even recognize that vala is installed. Do I have to give some fancy parameter to vala to be correctly installed? Thanks in advance Lorenzo 2011/2/7 > Send Shotwell mailing list submissions to > shotwell at lists.yorba.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > or, via email, send a message with subject or body 'help' to > shotwell-request at lists.yorba.org > > You can reach the person managing the list at > shotwell-owner at lists.yorba.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Shotwell digest..." > > > Today's Topics: > > 1. Re: Strange date error (Adam Dingle) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 07 Feb 2011 10:48:12 -0800 > From: Adam Dingle > To: shotwell at lists.yorba.org > Subject: Re: [Shotwell] Strange date error > Message-ID: <4D503E6C.1070004 at yorba.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Lorenzo, > > thanks for your message. I suspect you're using Vala 0.9.8. The > Shotwell trunk will no longer build with that version of Vala. I've > just updated the Shotwell makefile to check for a minimum of Vala > 0.10.0. So if you upgrade to Vala 0.10, you should be able to build. > Cheers - > > adam > > On 02/06/2011 10:33 AM, Lorenzo Baldacchini wrote: > > Hello everybody, > > > > I am trying to compile shotwell from source, obtained via SVN. > > > > I have such a strange error with the last version > > > > Compiling Vala code... > > src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' > could > > not be found > > private GLib.DateTime example_date = new GLib.DateTime.local(2009, > 3, > > 10, 18, 16, 11); > > ^^^^^^^^^^^^^ > > src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not be > > found > > DateTime date = new DateTime.from_unix_utc(tm); > > ^^^^^^^^ > > Compilation failed: 2 error(s), 0 warning(s) > > make: *** [src/.stamp] Errore 1 > > > > > > What does this mean? > > I have installed glib2.26 from source to be able to install shotwell. > > > > Thanks a lot > > best regards > > Lorenzo > > _______________________________________________ > > 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 > > > End of Shotwell Digest, Vol 19, Issue 8 > *************************************** > From adam at yorba.org Mon Feb 7 22:50:36 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 07 Feb 2011 14:50:36 -0800 Subject: [Shotwell] Shotwell Digest, Vol 19, Issue 8 In-Reply-To: References: Message-ID: <4D50773C.5050307@yorba.org> Lorenzo, what version of Ubuntu are you using? Both Ubuntu Maverick (10.10) and Natty (11.04) include Vala 0.10.0 in their repositories in the valac-0.10 package, so on those releases you shouldn't need to build Vala from source. It sounds like you're probably on Ubuntu Lucid, since you said you had to install libglib 2.26 from source. I don't know whether the Shotwell trunk will build on Lucid, since I'm not sure whether Shotwell has other dependencies that are not available there. Yorba's policy is that each Shotwell release supports the last two releases of the major distros. That is, Shotwell 0.8 builds on both Maverick and Lucid, and Shotwell 0.9 (including the current trunk) will build on both Natty and Maverick. I'd recommend that you update to Maverick if you want to work with the Shotwell trunk. By the way, we probably won't publish Vala in our PPA, since that's really up to the Vala team and is outside the scope of Yorba's activities. There is a Vala PPA (https://launchpad.net/~vala-team/+archive/ppa), though it only includes Vala 0.11.5. You could ask the Vala team to publish the last stable release (0.10) in their PPA of Lucid if you like - don't know what they'll say, though. I suspect that they, like we, are focused on newer operating system releases. adam On 02/07/2011 01:29 PM, Lorenzo Baldacchini wrote: > Hello, > > I am installing vala 0.10 from source. > I suggest to put it in your ppa, since there are two version (or at least is > what I have in the software list) 0.98 and 0.11.5, both not good for > installing shotwell. > > Thanks again, anyway, for the perfect work you are doing with shotwell! > > Regards > Lorenzo > > 2011/2/7 > >> Send Shotwell mailing list submissions to >> shotwell at lists.yorba.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> or, via email, send a message with subject or body 'help' to >> shotwell-request at lists.yorba.org >> >> You can reach the person managing the list at >> shotwell-owner at lists.yorba.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Shotwell digest..." >> >> >> Today's Topics: >> >> 1. Re: Strange date error (Adam Dingle) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 07 Feb 2011 10:48:12 -0800 >> From: Adam Dingle >> To: shotwell at lists.yorba.org >> Subject: Re: [Shotwell] Strange date error >> Message-ID:<4D503E6C.1070004 at yorba.org> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> Lorenzo, >> >> thanks for your message. I suspect you're using Vala 0.9.8. The >> Shotwell trunk will no longer build with that version of Vala. I've >> just updated the Shotwell makefile to check for a minimum of Vala >> 0.10.0. So if you upgrade to Vala 0.10, you should be able to build. >> Cheers - >> >> adam >> >> On 02/06/2011 10:33 AM, Lorenzo Baldacchini wrote: >>> Hello everybody, >>> >>> I am trying to compile shotwell from source, obtained via SVN. >>> >>> I have such a strange error with the last version >>> >>> Compiling Vala code... >>> src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' >> could >>> not be found >>> private GLib.DateTime example_date = new GLib.DateTime.local(2009, >> 3, >>> 10, 18, 16, 11); >>> ^^^^^^^^^^^^^ >>> src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not be >>> found >>> DateTime date = new DateTime.from_unix_utc(tm); >>> ^^^^^^^^ >>> Compilation failed: 2 error(s), 0 warning(s) >>> make: *** [src/.stamp] Errore 1 >>> >>> >>> What does this mean? >>> I have installed glib2.26 from source to be able to install shotwell. >>> >>> Thanks a lot >>> best regards >>> Lorenzo >>> _______________________________________________ >>> 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 >> >> >> End of Shotwell Digest, Vol 19, Issue 8 >> *************************************** >> > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From adam at yorba.org Mon Feb 7 22:52:17 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 07 Feb 2011 14:52:17 -0800 Subject: [Shotwell] Shotwell Digest, Vol 19, Issue 8 In-Reply-To: References: Message-ID: <4D5077A1.10102@yorba.org> Lorenzo, what do the following commands print? $ which valac $ valac --version You might to run 'sudo ldconfig' after installing Vala - that sometimes helps after installing shared libaries. adam On 02/07/2011 01:32 PM, Lorenzo Baldacchini wrote: > Hello, it is again me with the compiling issue. > > I have correctly installed vala 0.10, > but still shotwell does not compile. > It doesn't even recognize that vala is installed. > > Do I have to give some fancy parameter to vala to be correctly installed? > > Thanks in advance > Lorenzo > > 2011/2/7 > >> Send Shotwell mailing list submissions to >> shotwell at lists.yorba.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> or, via email, send a message with subject or body 'help' to >> shotwell-request at lists.yorba.org >> >> You can reach the person managing the list at >> shotwell-owner at lists.yorba.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Shotwell digest..." >> >> >> Today's Topics: >> >> 1. Re: Strange date error (Adam Dingle) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 07 Feb 2011 10:48:12 -0800 >> From: Adam Dingle >> To: shotwell at lists.yorba.org >> Subject: Re: [Shotwell] Strange date error >> Message-ID:<4D503E6C.1070004 at yorba.org> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> Lorenzo, >> >> thanks for your message. I suspect you're using Vala 0.9.8. The >> Shotwell trunk will no longer build with that version of Vala. I've >> just updated the Shotwell makefile to check for a minimum of Vala >> 0.10.0. So if you upgrade to Vala 0.10, you should be able to build. >> Cheers - >> >> adam >> >> On 02/06/2011 10:33 AM, Lorenzo Baldacchini wrote: >>> Hello everybody, >>> >>> I am trying to compile shotwell from source, obtained via SVN. >>> >>> I have such a strange error with the last version >>> >>> Compiling Vala code... >>> src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' >> could >>> not be found >>> private GLib.DateTime example_date = new GLib.DateTime.local(2009, >> 3, >>> 10, 18, 16, 11); >>> ^^^^^^^^^^^^^ >>> src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not be >>> found >>> DateTime date = new DateTime.from_unix_utc(tm); >>> ^^^^^^^^ >>> Compilation failed: 2 error(s), 0 warning(s) >>> make: *** [src/.stamp] Errore 1 >>> >>> >>> What does this mean? >>> I have installed glib2.26 from source to be able to install shotwell. >>> >>> Thanks a lot >>> best regards >>> Lorenzo >>> _______________________________________________ >>> 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 >> >> >> End of Shotwell Digest, Vol 19, Issue 8 >> *************************************** >> > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From spschiebel at gmail.com Tue Feb 8 03:47:13 2011 From: spschiebel at gmail.com (Steven Schiebel) Date: Tue, 8 Feb 2011 10:47:13 +0700 Subject: [Shotwell] Shotwell Digest, Vol 19, Issue 8 In-Reply-To: <4D50773C.5050307@yorba.org> References: <4D50773C.5050307@yorba.org> Message-ID: So will there be a PPA update for future versions of Shotwell for Lucid? It seems a bit short sighted not to support the current LTS release of Ubuntu. Also, if 0.8 builds on Lucid why is there no PPA for that version? On Tue, Feb 8, 2011 at 5:50 AM, Adam Dingle wrote: > Lorenzo, > > what version of Ubuntu are you using? Both Ubuntu Maverick (10.10) and > Natty (11.04) include Vala 0.10.0 in their repositories in the valac-0.10 > package, so on those releases you shouldn't need to build Vala from source. > It sounds like you're probably on Ubuntu Lucid, since you said you had to > install libglib 2.26 from source. I don't know whether the Shotwell trunk > will build on Lucid, since I'm not sure whether Shotwell has other > dependencies that are not available there. Yorba's policy is that each > Shotwell release supports the last two releases of the major distros. That > is, Shotwell 0.8 builds on both Maverick and Lucid, and Shotwell 0.9 > (including the current trunk) will build on both Natty and Maverick. I'd > recommend that you update to Maverick if you want to work with the Shotwell > trunk. > > By the way, we probably won't publish Vala in our PPA, since that's really > up to the Vala team and is outside the scope of Yorba's activities. There > is a Vala PPA (https://launchpad.net/~vala-team/+archive/ppa), though it > only includes Vala 0.11.5. You could ask the Vala team to publish the last > stable release (0.10) in their PPA of Lucid if you like - don't know what > they'll say, though. I suspect that they, like we, are focused on newer > operating system releases. > > adam > > > On 02/07/2011 01:29 PM, Lorenzo Baldacchini wrote: > >> Hello, >> >> I am installing vala 0.10 from source. >> I suggest to put it in your ppa, since there are two version (or at least >> is >> what I have in the software list) 0.98 and 0.11.5, both not good for >> installing shotwell. >> >> Thanks again, anyway, for the perfect work you are doing with shotwell! >> >> Regards >> Lorenzo >> >> 2011/2/7 >> >> Send Shotwell mailing list submissions to >>> shotwell at lists.yorba.org >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> or, via email, send a message with subject or body 'help' to >>> shotwell-request at lists.yorba.org >>> >>> You can reach the person managing the list at >>> shotwell-owner at lists.yorba.org >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of Shotwell digest..." >>> >>> >>> Today's Topics: >>> >>> 1. Re: Strange date error (Adam Dingle) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Mon, 07 Feb 2011 10:48:12 -0800 >>> From: Adam Dingle >>> To: shotwell at lists.yorba.org >>> Subject: Re: [Shotwell] Strange date error >>> Message-ID:<4D503E6C.1070004 at yorba.org> >>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >>> >>> Lorenzo, >>> >>> thanks for your message. I suspect you're using Vala 0.9.8. The >>> Shotwell trunk will no longer build with that version of Vala. I've >>> just updated the Shotwell makefile to check for a minimum of Vala >>> 0.10.0. So if you upgrade to Vala 0.10, you should be able to build. >>> Cheers - >>> >>> adam >>> >>> On 02/06/2011 10:33 AM, Lorenzo Baldacchini wrote: >>> >>>> Hello everybody, >>>> >>>> I am trying to compile shotwell from source, obtained via SVN. >>>> >>>> I have such a strange error with the last version >>>> >>>> Compiling Vala code... >>>> src/Dialogs.vala:1664.13-1664.25: error: The type name `GLib.DateTime' >>>> >>> could >>> >>>> not be found >>>> private GLib.DateTime example_date = new GLib.DateTime.local(2009, >>>> >>> 3, >>> >>>> 10, 18, 16, 11); >>>> ^^^^^^^^^^^^^ >>>> src/AppDirs.vala:93.9-93.16: error: The type name `DateTime' could not >>>> be >>>> found >>>> DateTime date = new DateTime.from_unix_utc(tm); >>>> ^^^^^^^^ >>>> Compilation failed: 2 error(s), 0 warning(s) >>>> make: *** [src/.stamp] Errore 1 >>>> >>>> >>>> What does this mean? >>>> I have installed glib2.26 from source to be able to install shotwell. >>>> >>>> Thanks a lot >>>> best regards >>>> Lorenzo >>>> _______________________________________________ >>>> 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 >>> >>> >>> End of Shotwell Digest, Vol 19, Issue 8 >>> *************************************** >>> >>> _______________________________________________ >> 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 adam at yorba.org Tue Feb 8 17:36:12 2011 From: adam at yorba.org (Adam Dingle) Date: Tue, 08 Feb 2011 09:36:12 -0800 Subject: [Shotwell] Shotwell Digest, Vol 19, Issue 8 In-Reply-To: References: <4D50773C.5050307@yorba.org> Message-ID: <4D517F0C.7080004@yorba.org> Steven, On 02/07/2011 07:47 PM, Steven Schiebel wrote: > So will there be a PPA update for future versions of Shotwell for Lucid? It > seems a bit short sighted not to support the current LTS release of Ubuntu. A few points: With most GNOME applications such as Nautilus, gedit or Totem, you must run the very latest GNOME release if you want to use the latest version of the application. So Shotwell is actually more backward compatible then most other GNOME applications: our policy is that the latest Shotwell supports both the latest and the previous version of GNOME. LTS releases of Ubuntu appear only once every two years. If Shotwell were to always support the latest LTS release, then we'd be unable to use any new GNOME libraries or features in Shotwell until two years after they appeared. That might be reasonable at a later stage in Shotwell's evolution, but Shotwell is a young program which is evolving rapidly and we want to be able to use the latest and greatest GNOME technologies at this point in its life cycle. When Shotwell's feature set matures we may extend the backward compatibility window further back in time. > Also, if 0.8 builds on Lucid why is there no PPA for that version? Unfortunately we realized late in the 0.8 development cycle that we couldn't easily support 0.8 for Lucid on our PPA for technical reasons involving Vala versions and build dependencies. See http://trac.yorba.org/ticket/3015 http://lists.yorba.org/pipermail/shotwell/2011-January/001583.html We won't make that mistake again: for 0.9 and future releases, we're committed to having our PPA support both the current and previous versions of Ubuntu. adam From rodney.dawes at canonical.com Tue Feb 8 15:23:47 2011 From: rodney.dawes at canonical.com (Rodney Dawes) Date: Tue, 08 Feb 2011 10:23:47 -0500 Subject: [Shotwell] Writing Plug-ins Message-ID: <1297178627.7526.16.camel@localhost> Hi, I've been looking over the Shotwell wiki, and source code over the past few days, in order to get a handle on how we may go about developing the Ubuntu One plug-in for Shotwell. Between this, and the lack of a -dev package, with no development contents in the normal shotwell package in Ubuntu; I'm a bit confused on how one actually writes a plug-in for Shotwell. I can't find any rules for building and installing a .gir file, a .vapi/.deps for Vala, or a .pc for getting CFLAGS/LDFLAGS to link against a library providing the plug-in API. Are there plans to provide these, or are plug-ins meant to be in the upstream tree and compiled into the shotwell binary directly? Because, as far as I can tell, that's how they seem to work. But you guys aren't using any standard build system either, and trying to navigate and decipher yours is a bit difficult; so perhaps I missed something? Thanks. PS: Please use that reply-to-all button, and not the reply-to-list one, as I am not subscribed. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From vera at yorba.org Tue Feb 8 19:38:55 2011 From: vera at yorba.org (Vera Yin) Date: Tue, 8 Feb 2011 11:38:55 -0800 Subject: [Shotwell] Writing IPTC tags In-Reply-To: <1296919986469-33024.post@talk.nabble.com> References: <1296919986469-33024.post@talk.nabble.com> Message-ID: Hi Gandal, There are three metadata domains: EXIF, IPTC, and XMP. You can see the contents of all of them by running 'exiv2 -pa' on a filename. It's likely that Shotwell wrote the tags to XMP when you didn't see them in IPTC. Currently Shotwell tries to write to domains where metadata already exists, but we agree that the behavior you saw is not ideal, and we're planning to fix it in 0.9 by having Shotwell write the metadata to all domains. Cheers, Vera On Sat, Feb 5, 2011 at 7:33 AM, gandal wrote: > > Hi, > I installed Shotwell 0.8.1 (on Xubuntu 10.10) and I'm experiencing some > problems with IPTC tags. > In Preferences I checked "Write tags, titles, and other metadata to photo > files". > I noticed that Shotwell doesn't write IPTC keywords in the jpg photos taken > with my Canon camera. > Only if I write an IPTC keyword in the file using the command: > iptc -a Keywords -v "value" "filename.jpg" > then Shotwell become able to modify the Keyword into the jpg file. I tested > IPTC tags with this command: > iptc "filename.jpg" > and with XNview under Windows. > It seems that Shotwell doesn't write IPTC tags if no IPTC data exists in the > file. > I'm a bit confused, because in ?http://trac.yorba.org/ticket/3044 this > ticket is said: > "Shotwell has a list of metadata tags for each type of metadata (titles, > keywords/tags, ratings, etc.) ?If none of the metadata domains is present > for that particular type, it uses the first one in the list regardless if > the domain is present or not" > -- > View this message in context: http://shotwell.3510.www.nabble.com/Writing-IPTC-tags-tp33024p33024.html > Sent from the Shotwell mailing list archive at Nabble.com. > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From adam at yorba.org Tue Feb 8 19:57:42 2011 From: adam at yorba.org (Adam Dingle) Date: Tue, 08 Feb 2011 11:57:42 -0800 Subject: [Shotwell] Three (!) feature requests ;-) In-Reply-To: References: <1296516625049-32909.post@talk.nabble.com> Message-ID: <4D51A036.5070502@yorba.org> On 02/04/2011 01:20 PM, Pawe? Rumian wrote: > Hi all. > > First of all - I'm really impressed by the speed of development and > quality of shotwell. > > Said that, I must admit that I wholeheartedly agree with the author of > this thread - particularly I don't understand the idea behind > 'Events'. > Wouldn't a kind of timeline be more flexible? > > In my daily work I often have three or four events during one day, but > also events that last as long as one week or month. > I know I can merge events and create new ones, but it makes the > automatic daily events totally unnecessary, because I'd always have to > customize them. > Furthermore, the lack of any kind of timeline, which would enable me > to restrict displayed photos tho specific range of dates is even more > painful. > > I'm really excited with what you are doing, so don't treat this as a > complainment - I just believe that such discussions could make > shotwell better. > > greetings, > Pawe? Pawe?, thanks for your comments. Of course there are various ways to organize photos by time. Lots of people find that events work well for them, but some people have expressed interest in a timeline view as well. So I think we'll probably add one sooner or later - see http://trac.yorba.org/ticket/2195 adam From adam at yorba.org Tue Feb 8 20:02:55 2011 From: adam at yorba.org (Adam Dingle) Date: Tue, 08 Feb 2011 12:02:55 -0800 Subject: [Shotwell] Change location of .shotwell directory (incl. database) In-Reply-To: References: <4D428FD3.6030806@a-little-bit.de> <4D4290BE.2020103@googlemail.com> Message-ID: <4D51A16F.9090409@yorba.org> On 02/05/2011 02:08 AM, Paulo J. Matos wrote: > On 02/02/11 01:14, Vera Yin wrote: >> Hi Paulo, >> >> Which version of Shotwell are you using? I believe in 0.8.1 you can do >> the following: >> >> 1) move the .shotwell and Pictures directories to the new locations >> 2) launch Shotwell specifying the .shotwell location with -d (or as >> user 'photos'). At this point your entire library (if previously all >> located in ~pmatos/Pictures) will be on the Missing Photos page. >> 3) go to Edit->Preferences and change the Library Location to the new >> Pictures directory >> 4) under the Library Location enable 'Watch library directory for new >> files'. Now Shotwell should find and restore everything from Missing >> Photos to the Photo library. >> > > Where are the Preferences kept? I just noticed that they are kept > nowhere in the .shotwell directory? Is it a gnome registry thing or > something? Paulo, Shotwell stores its preferences in GConf under /apps/shotwell. You can see them easily if you run 'gconf-editor' in GNOME. adam From lucas at yorba.org Tue Feb 8 20:29:46 2011 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 8 Feb 2011 12:29:46 -0800 Subject: [Shotwell] Writing Plug-ins In-Reply-To: <1297178627.7526.16.camel@localhost> References: <1297178627.7526.16.camel@localhost> Message-ID: Hi Rodney, As of last night's commit (svn revision 2612), the Facebook publishing plug-in is built and packaged as a separate, dynamically-loadable .so. The Facebook plug-in is our reference implementation for both the plug-in packaging scheme and the new API that publishing plug-ins use to connect to Shotwell. You can see the source and make files for the Facebook plug-in by browsing the files in ${SHOTWELL_ROOT}/plugins/shotwell-publishing/. When browsing these and other plug-in related files in the Shotwell source tree, there are a few things to keep in mind. One is that writing a publishing plug-in is actually a three-step process. First, you have to write the plug-in infrastructure. Regardless of whether you're writing a plug-in for web publishing or for slideshow transitions, the Shotwell Pluggable Interface Technology (SPIT) controls the mechanics of entry points, API version negotiation, and interface discovery. The SPIT architecture is documented on our wiki at http://trac.yorba.org/wiki/ShotwellArchWritingPlugins. Next, you have to write the core functionality of the plug-in itself. This is where the plug-in actually does what it does. In the case of publishing plug-ins, this where you actually write code to send network messages, parse XML responses, etc. There is a new publishing-specific API for publishing plugins, written on top of SPIT, that we are finalizing the details of right now. Some preliminary documentation for this API is available at http://trac.yorba.org/wiki/ShotwellPrelimPublishingAPIDoc. The code that actually defines the new publishing API lives in ${SHOTWELL_ROOT}/src/plugins/PublishingInterfaces.vala. The reference Facebook plug-in in trunk is written against this API. Last, you have to decide on a mechanism to build and package your publishing .so. In the case of the reference Facebook plug-in, it's built via a recursive make invoked from the main Shotwell Makefile. Essentially, the Facebook plug-in is built as part of Shotwell itself. This makes sense for a reference plug-in that -- even if packaged as a separate .so -- constitutes a core part of Shotwell. Of course, this makes less sense for a third-party publishing plug-in like Ubuntu One. That said, a good way to get started working is to check out Shotwell trunk and then, in your own sandbox, edit the Shotwell makefiles so that your plug-in is built alongside Shotwell itself. You can then decide on a build system and packaging mechanism later. Another thing to keep in mind is that the new, plug-in based Shotwell publishing API exists alongside the old legacy publishing API in which publishing connectors were actually baked into the Shotwell executable. For this reason, we have quite a lot of code dedicated to bridging the old and the new APIs. All of this code lives in ${SHOTWELL_ROOT}/src/publishing/APIGlue.vala. At least until we rip out all of the old publishing code, getting your publishing plug-in to tie into Shotwell probably involves modifying three or four lines of driver code this file. Lastly, keep in mind that the new publishing API is still in flux, and while it's pleasantly chilled, it hasn't exactly been frozen yet. As I said, some preliminary documentation is available at http://trac.yorba.org/wiki/ShotwellPrelimPublishingAPIDoc. As of right now, it describes the two core interfaces in the new publishing API: the Publisher interface, which your plug-in must implement to be discovered as a publishing service, and the PublishingInteractor interface, which your plug-in uses to communicate with Shotwell to query the list of items to publish, ask Shotwell to set up the publishing interface, etc. If you need any more information, or if you think it'd be helpful to talk by phone, just reply to this message and we'll set something up. We're here for you guys. Regards, Lucas From vera at yorba.org Tue Feb 8 20:49:56 2011 From: vera at yorba.org (Vera Yin) Date: Tue, 8 Feb 2011 12:49:56 -0800 Subject: [Shotwell] Shotwell 0.8.1 from PPA uses 3 GB RAM and does not start. In-Reply-To: <4D4C7FE9.8050001@gmail.com> References: <4D4C3232.4050106@gmail.com> <4D4C7FE9.8050001@gmail.com> Message-ID: Hi M?nulio, I looked through your shotwell.gdb and found the line: #4 0x00007fffe6a4a208 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libaurora.so The same behavior was reported with the Aurora theme by another user - http://trac.yorba.org/ticket/3021. Perhaps you can try switching to another theme and see if the problem persists. Cheers, Vera 2011/2/4 M?nulio ?vytuokl? : > Yes, of course. > > > 2011.02.04 21:28, Vera Yin ra??: >> >> Hi M?nulio, >> >> This mailing list doesn't allow attachments so your shotwell.log and >> shotwell.gdb didn't go through. Could you instead send those files to >> us at? >> >> Thanks, >> Vera >> >> 2011/2/4 M?nulio ?vytuokl?: >>> >>> Hallo. >>> I'm using Ubuntu 10.10 64 bit on my machine. >>> I have tried to install Shotwell from PPA, version 0.8.1. Shotwell starts >>> but immediately window goes blank (see screen-shot) and Shotwell uses a 3 >>> GB >>> amount of RAM. I have tried to debug. I have attached shotwell.log and >>> shotwell.gdb. >>> How I can solve this problem? >>> Best Regards. >>> >>> _______________________________________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> > > From rodney.dawes at canonical.com Wed Feb 9 00:24:00 2011 From: rodney.dawes at canonical.com (Rodney Dawes) Date: Tue, 08 Feb 2011 19:24:00 -0500 Subject: [Shotwell] Writing Plug-ins In-Reply-To: References: <1297178627.7526.16.camel@localhost> Message-ID: <1297211040.2413.3.camel@localhost> Hi Lucas, That was an interesting read, but it didn't quite answer my questions. 1) Is there a shared library that the plug-ins link to for the Spit.* API/Interfaces? - If so, is there also a .gir being generated for them? a) If so, is there a .vapi/.deps being built for those? - If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? I see in the facebook publisher plug-in's Makefile that it wants to use shotwell-spit-1.0 as a package, but I don't see that .vapi anywhere in the tree, nor a .deps that would accompany it; nor do I see any of them being generated in a Makefile. Where are they? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From lucas at yorba.org Wed Feb 9 01:53:00 2011 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 8 Feb 2011 17:53:00 -0800 Subject: [Shotwell] Writing Plug-ins In-Reply-To: <1297211040.2413.3.camel@localhost> References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> Message-ID: Hi Rodney, Sorry for not answering your questions! Admittedly, my previous email was probably more of an introduction to the state of the Shotwell plug-in system than it was a specific response to your points. Once again, I apologize. I'll hit your questions one-by-one this time: > Is there a shared library that the plug-ins link > to for the Spit.* API/Interfaces? No. The plug-ins link directly with the Shotwell executable. There's no stub library or developer package that needs to be installed or that appears in Synaptic or as a pkg-config module. All of the references to the word "package" in the Shotwell make files refer to Vala packages. As you noted, a Vala package isn't a "package" in the sense of Synaptic or pkg-config. It's just a .vapi file and a .deps file. > is there also a .gir being generated for them? No. Shotwell doesn't use GObject introspection to discover interfaces. Interface specification is all done directly through .vapi and .deps files. > If so, is there a .vapi/.deps being built for those? Yes. The .vapi and .deps files for the plug-in interfaces are generated automatically by the Shotwell build system. Simply running "./configure ; make" will cause the files shotwell-spit-1.0.vapi, shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and shotwell-publishing-1.0.deps to appear in the ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for interface specification, at least as far as the Vala compiler is concerned. If you're curious, the make rules that generate these files are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. > If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? No. The Vala compiler will specify the CFLAGS and LDFLAGS variables automatically when it invokes gcc as a child process. Right now, if you want to develop plug-ins in C instead of Vala, you'll need to set these up manually. Cheers, Lucas From jim at yorba.org Wed Feb 9 03:29:25 2011 From: jim at yorba.org (Jim Nelson) Date: Tue, 8 Feb 2011 19:29:25 -0800 Subject: [Shotwell] Writing Plug-ins In-Reply-To: References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> Message-ID: Hi Rodney, To jump in here, there's still some work to be done to support plug-in writers. We wanted to make sure our own plug-ins worked first so we weren't putting untested interfaces out into the world. One ticket you should be aware of: http://trac.yorba.org/ticket/3160 This is to have Shotwell install the .h and VAPI files in a "make install". This will only happen if a switch is enabled with the configure script. As part of this work we'll also produce and install a .pc file. Until then, you'll need to copy the generated .h, .vapi, and .dep files to your project and include them in your build (the valac --vapidir option is useful here). Because the .vapi files wants to look for the .h files in a plugins/ subdirectory, they should be placed there, i.e. my_project/plugins. Once Shotwell is capable of installing the header and VAPIs, you won't need to include them in your project directory. -- Jim On Tue, Feb 8, 2011 at 5:53 PM, Lucas Beeler wrote: > Hi Rodney, > > Sorry for not answering your questions! Admittedly, my previous email > was probably more of an introduction to the state of the Shotwell > plug-in system than it was a specific response to your points. Once > again, I apologize. I'll hit your questions one-by-one this time: > > > Is there a shared library that the plug-ins link > > to for the Spit.* API/Interfaces? > > No. The plug-ins link directly with the Shotwell executable. There's > no stub library or developer package that needs to be installed or > that appears in Synaptic or as a pkg-config module. All of the > references to the word "package" in the Shotwell make files refer to > Vala packages. As you noted, a Vala package isn't a "package" in the > sense of Synaptic or pkg-config. It's just a .vapi file and a .deps > file. > > > is there also a .gir being generated for them? > > No. Shotwell doesn't use GObject introspection to discover interfaces. > Interface specification is all done directly through .vapi and .deps > files. > > > If so, is there a .vapi/.deps being built for those? > > Yes. The .vapi and .deps files for the plug-in interfaces are > generated automatically by the Shotwell build system. Simply running > "./configure ; make" will cause the files shotwell-spit-1.0.vapi, > shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and > shotwell-publishing-1.0.deps to appear in the > ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for > interface specification, at least as far as the Vala compiler is > concerned. If you're curious, the make rules that generate these files > are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. > > > If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? > > No. The Vala compiler will specify the CFLAGS and LDFLAGS variables > automatically when it invokes gcc as a child process. Right now, if > you want to develop plug-ins in C instead of Vala, you'll need to set > these up manually. > > Cheers, > Lucas > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From adam at yorba.org Wed Feb 9 14:55:22 2011 From: adam at yorba.org (Adam Dingle) Date: Wed, 09 Feb 2011 06:55:22 -0800 Subject: [Shotwell] Shotwell 0.8.1 from PPA uses 3 GB RAM and does not start. In-Reply-To: <4D525188.70403@gmail.com> References: <4D4C3232.4050106@gmail.com> <4D4C7FE9.8050001@gmail.com> <4D525188.70403@gmail.com> Message-ID: <4D52AADA.9080103@yorba.org> M?nulio, as far as I can tell, the home page for Aurora is http://gnome-look.org/content/show.php/Aurora+Gtk+Engine?content=56438 I downloaded the aurora-1.5.1 sources from that site. The AUTHORS file in the engine source says that the Aurora author is Eric Matthews. His email address is echm2007 at gmail. Probably he's the best person to report this bug to. adam On 02/09/2011 12:34 AM, M?nulio ?vytuokl? wrote: > Hallo. > When I switch theme from Aurora to other like ClearlooksClassic or > IndustrialTango, Shotwell starts up very well. > When will this problem with Aurora engine fixed? > Aurora engine is my preferred engine and due only Shotwell I can not > use it... > Best regards. > > 2011.02.08 22:49, Vera Yin ra??: >> Hi M?nulio, >> >> I looked through your shotwell.gdb and found the line: >> >> #4 0x00007fffe6a4a208 in ?? () from >> /usr/lib/gtk-2.0/2.10.0/engines/libaurora.so >> >> The same behavior was reported with the Aurora theme by another user - >> http://trac.yorba.org/ticket/3021. Perhaps you can try switching to >> another theme and see if the problem persists. >> >> Cheers, >> Vera >> >> 2011/2/4 M?nulio ?vytuokl?: >>> Yes, of course. >>> >>> >>> 2011.02.04 21:28, Vera Yin ra??: >>>> Hi M?nulio, >>>> >>>> This mailing list doesn't allow attachments so your shotwell.log and >>>> shotwell.gdb didn't go through. Could you instead send those files to >>>> us at? >>>> >>>> Thanks, >>>> Vera >>>> >>>> 2011/2/4 M?nulio ?vytuokl?: >>>>> Hallo. >>>>> I'm using Ubuntu 10.10 64 bit on my machine. >>>>> I have tried to install Shotwell from PPA, version 0.8.1. Shotwell >>>>> starts >>>>> but immediately window goes blank (see screen-shot) and Shotwell >>>>> uses a 3 >>>>> GB >>>>> amount of RAM. I have tried to debug. I have attached shotwell.log >>>>> and >>>>> shotwell.gdb. >>>>> How I can solve this problem? >>>>> Best Regards. >>>>> >>>>> _______________________________________________ >>>>> Shotwell mailing list >>>>> Shotwell at lists.yorba.org >>>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>>>> >>>>> >>> > From menulio.svytuokle at gmail.com Wed Feb 9 08:34:16 2011 From: menulio.svytuokle at gmail.com (=?UTF-8?B?TcSXbnVsaW8gxaB2eXR1b2tsxJc=?=) Date: Wed, 09 Feb 2011 10:34:16 +0200 Subject: [Shotwell] Shotwell 0.8.1 from PPA uses 3 GB RAM and does not start. In-Reply-To: References: <4D4C3232.4050106@gmail.com> <4D4C7FE9.8050001@gmail.com> Message-ID: <4D525188.70403@gmail.com> Hallo. When I switch theme from Aurora to other like ClearlooksClassic or IndustrialTango, Shotwell starts up very well. When will this problem with Aurora engine fixed? Aurora engine is my preferred engine and due only Shotwell I can not use it... Best regards. 2011.02.08 22:49, Vera Yin ra??: > Hi M?nulio, > > I looked through your shotwell.gdb and found the line: > > #4 0x00007fffe6a4a208 in ?? () from > /usr/lib/gtk-2.0/2.10.0/engines/libaurora.so > > The same behavior was reported with the Aurora theme by another user - > http://trac.yorba.org/ticket/3021. Perhaps you can try switching to > another theme and see if the problem persists. > > Cheers, > Vera > > 2011/2/4 M?nulio ?vytuokl?: >> Yes, of course. >> >> >> 2011.02.04 21:28, Vera Yin ra??: >>> Hi M?nulio, >>> >>> This mailing list doesn't allow attachments so your shotwell.log and >>> shotwell.gdb didn't go through. Could you instead send those files to >>> us at? >>> >>> Thanks, >>> Vera >>> >>> 2011/2/4 M?nulio ?vytuokl?: >>>> Hallo. >>>> I'm using Ubuntu 10.10 64 bit on my machine. >>>> I have tried to install Shotwell from PPA, version 0.8.1. Shotwell starts >>>> but immediately window goes blank (see screen-shot) and Shotwell uses a 3 >>>> GB >>>> amount of RAM. I have tried to debug. I have attached shotwell.log and >>>> shotwell.gdb. >>>> How I can solve this problem? >>>> Best Regards. >>>> >>>> _______________________________________________ >>>> Shotwell mailing list >>>> Shotwell at lists.yorba.org >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>>> >>>> >> From gandal71 at gmail.com Wed Feb 9 19:58:02 2011 From: gandal71 at gmail.com (gandal) Date: Wed, 9 Feb 2011 11:58:02 -0800 (PST) Subject: [Shotwell] Writing IPTC tags In-Reply-To: References: <1296919986469-33024.post@talk.nabble.com> Message-ID: <1297281482165-33344.post@talk.nabble.com> I checked my files with the 'exiv2 -pa' command and I found the xmp tags. Xnview was hiding XMP tags, showing me only "real" IPTC tags. Thank you very much for your help. Now I can really say that this software is perfect for me. -- View this message in context: http://shotwell.3510.www.nabble.com/Writing-IPTC-tags-tp33024p33344.html Sent from the Shotwell mailing list archive at Nabble.com. From lucas at yorba.org Fri Feb 11 02:06:35 2011 From: lucas at yorba.org (Lucas Beeler) Date: Thu, 10 Feb 2011 18:06:35 -0800 Subject: [Shotwell] Writing Plug-ins In-Reply-To: References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> Message-ID: Hi Rodney, I'm just following up on my email message of two days ago. I wanted to let you know that we made some changes to the pluggable publishing API today. We've also substantially improved the API documentation, which remains available at http://trac.yorba.org/wiki/ShotwellPrelimPublishingAPIDoc. We haven't frozen the API yet, but it has stabilized to the point where the names and parameter signatures of things shouldn't change willy-nilly. That said, if you or Canonical have need of any services that we're not currently providing in the API, drop us a line. We'd likely be happy to add them. Finally, you might want to stay close to trunk over the next week or so, running "svn up" on your sandbox at least once a day. There are some changes to the plugin infrastructure coming down the pipe. Thankfully, these won't directly affect the publishing API. Regards, Lucas From baldakkl at gmail.com Fri Feb 11 23:58:40 2011 From: baldakkl at gmail.com (Lorenzo Baldacchini) Date: Sat, 12 Feb 2011 00:58:40 +0100 Subject: [Shotwell] Going back in time Message-ID: Hello everybody is there a way to obtain the svn version of shotwell of the last week? I can't compile the last version, but the 15 days ago version was perfect. Can you help me? Thanks a lot Lorenzo From insomniacpenguin at googlemail.com Sat Feb 12 00:39:11 2011 From: insomniacpenguin at googlemail.com (Andy Stevens) Date: Sat, 12 Feb 2011 00:39:11 +0000 Subject: [Shotwell] Going back in time In-Reply-To: References: Message-ID: On 11 February 2011 23:58, Lorenzo Baldacchini wrote: > Hello everybody > > ?is there a way to obtain the svn version of shotwell of the last week? >From http://svnbook.red-bean.com/en/1.5/svn.ref.svn.html "--revision (-r) REV Indicates that you're going to supply a revision (or range of revisions) for a particular operation. You can provide revision numbers, keywords, or dates (in curly braces) as arguments to the revision option." > ? I can't compile the last version, but the 15 days ago version was > perfect. > ? Can you help me? Something along the lines of svn update --revision {2010-01-27} in your local work directory sounds about right to me. Hope this helps, Andy -- http://pseudoq.sourceforge.net/ Open source java sudoku application From brunogirin at gmail.com Sat Feb 12 20:21:43 2011 From: brunogirin at gmail.com (Bruno Girin) Date: Sat, 12 Feb 2011 20:21:43 +0000 Subject: [Shotwell] Writing Plug-ins In-Reply-To: References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> Message-ID: <1297542104.1855.23.camel@nuuk> Hi Jim, Interesting! That brings a number of questions: * When it comes to distributing plug-ins, what is your preferred way of doing it? Developers distribute them on independent sites or contribute them to the Shotwell repo? Personally, I'd prefer the latter as I'm confortable writing code but I would struggle to work out sensible build and packaging code. * If the latter, would you rather offer a single package that includes Shotwell + plugins or several packages, one for Shotwell core and others for the various plugins? * And if plugins are distributed separately, what is the plan to make them discoverable? By the way, I get the following error when starting Shotwell with the current trunk: shotwell: symbol lookup error: /usr/local/lib/shotwell/plugins/builtin/spitter.so: undefined symbol: spit_wad_get_type Cheers, Bruno On Tue, 2011-02-08 at 19:29 -0800, Jim Nelson wrote: > Hi Rodney, > > To jump in here, there's still some work to be done to support plug-in > writers. We wanted to make sure our own plug-ins worked first so we weren't > putting untested interfaces out into the world. > > One ticket you should be aware of: http://trac.yorba.org/ticket/3160 This > is to have Shotwell install the .h and VAPI files in a "make install". This > will only happen if a switch is enabled with the configure script. > > As part of this work we'll also produce and install a .pc file. > > Until then, you'll need to copy the generated .h, .vapi, and .dep files to > your project and include them in your build (the valac --vapidir option is > useful here). Because the .vapi files wants to look for the .h files in a > plugins/ subdirectory, they should be placed there, i.e. my_project/plugins. > > Once Shotwell is capable of installing the header and VAPIs, you won't need > to include them in your project directory. > > -- Jim > > On Tue, Feb 8, 2011 at 5:53 PM, Lucas Beeler wrote: > > > Hi Rodney, > > > > Sorry for not answering your questions! Admittedly, my previous email > > was probably more of an introduction to the state of the Shotwell > > plug-in system than it was a specific response to your points. Once > > again, I apologize. I'll hit your questions one-by-one this time: > > > > > Is there a shared library that the plug-ins link > > > to for the Spit.* API/Interfaces? > > > > No. The plug-ins link directly with the Shotwell executable. There's > > no stub library or developer package that needs to be installed or > > that appears in Synaptic or as a pkg-config module. All of the > > references to the word "package" in the Shotwell make files refer to > > Vala packages. As you noted, a Vala package isn't a "package" in the > > sense of Synaptic or pkg-config. It's just a .vapi file and a .deps > > file. > > > > > is there also a .gir being generated for them? > > > > No. Shotwell doesn't use GObject introspection to discover interfaces. > > Interface specification is all done directly through .vapi and .deps > > files. > > > > > If so, is there a .vapi/.deps being built for those? > > > > Yes. The .vapi and .deps files for the plug-in interfaces are > > generated automatically by the Shotwell build system. Simply running > > "./configure ; make" will cause the files shotwell-spit-1.0.vapi, > > shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and > > shotwell-publishing-1.0.deps to appear in the > > ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for > > interface specification, at least as far as the Vala compiler is > > concerned. If you're curious, the make rules that generate these files > > are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. > > > > > If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? > > > > No. The Vala compiler will specify the CFLAGS and LDFLAGS variables > > automatically when it invokes gcc as a child process. Right now, if > > you want to develop plug-ins in C instead of Vala, you'll need to set > > these up manually. > > > > Cheers, > > Lucas > > _______________________________________________ > > 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 blklists at elementarea.net Sun Feb 13 22:37:20 2011 From: blklists at elementarea.net (Andreas Brauchli) Date: Sun, 13 Feb 2011 23:37:20 +0100 Subject: [Shotwell] GSoC 2011 Message-ID: <1297636640.12109.18.camel@thinky> Dear shotwell team are there any plans for yorba/shotwell to apply for the google summer of code 2011? I've seen last year's wiki page [1] and would totally love to work on shotwell this summer! What i have in mind is the idea of a multi-user/multi-computer shotwell or shotwell server instance (something like [2]) so that a photo collection can be simultaneously accessed and modified from multiple frontends but would also allow each shotwell instance - think on a laptop - to locally cache (parts of) the collection. Students, please voice yourselves to encourage yorba to apply for a gsoc spot and to provide some mentors - and the others to suggest or point out feature requests that would keep a student busy for a good summer of code. GSoC website: http://www.google-melange.com/ cheers andreas [1] http://trac.yorba.org/wiki/SummerCodeIdeas [2] http://trac.yorba.org/ticket/1572 From andreas.wallberg at gmail.com Sun Feb 13 23:49:55 2011 From: andreas.wallberg at gmail.com (Andreas Wallberg) Date: Mon, 14 Feb 2011 00:49:55 +0100 Subject: [Shotwell] GSoC 2011 In-Reply-To: <1297636640.12109.18.camel@thinky> References: <1297636640.12109.18.camel@thinky> Message-ID: That sounds like a wonderful project! /Andreas Sent from my Android. On Feb 13, 2011 11:37 PM, "Andreas Brauchli" wrote: > Dear shotwell team > > are there any plans for yorba/shotwell to apply for the google summer of > code 2011? I've seen last year's wiki page [1] and would totally love to > work on shotwell this summer! > > What i have in mind is the idea of a multi-user/multi-computer shotwell > or shotwell server instance (something like [2]) so that a photo > collection can be simultaneously accessed and modified from multiple > frontends but would also allow each shotwell instance - think on a > laptop - to locally cache (parts of) the collection. > > Students, please voice yourselves to encourage yorba to apply for a gsoc > spot and to provide some mentors - and the others to suggest or point > out feature requests that would keep a student busy for a good summer of > code. > > GSoC website: http://www.google-melange.com/ > > cheers > andreas > > [1] http://trac.yorba.org/wiki/SummerCodeIdeas > [2] http://trac.yorba.org/ticket/1572 > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Mon Feb 14 21:08:21 2011 From: jim at yorba.org (Jim Nelson) Date: Mon, 14 Feb 2011 13:08:21 -0800 Subject: [Shotwell] Writing Plug-ins In-Reply-To: <1297542104.1855.23.camel@nuuk> References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> <1297542104.1855.23.camel@nuuk> Message-ID: Hi Bruno, Regarding the error, two things happened: (a) we changed the API slightly and (b) we removed one of the built-in plugins (which was there just for testing; it's essentially been moved to the samples directory). Shotwell is attempting to load an old .so. If you remove that spitter.so file, Shotwell should start. To answer your questions: 1. At this point we envision developers distributing their own plug-ins. If a contributor offers us a plugin that we think belongs in the Shotwell core, then we would accept it and move it into our source tree. But Yorba does not want to become the central repository of all Shotwell plugins. 2. We plan on bundling our core plugins with Shotwell. Other plugins will (most likely) be packaged separately. Note that packagers and/or distros may bundle a number of those plugins together and offer them as a single separate download. That's beyond our purview. 3. Today Shotwell discovers plugins only when they've been installed in one of two locations: /usr/lib/shotwell/plugins ~/.gnome2/shotwell/plugins The first is for plugins available system-wide, the second for plugins only available to that user. (Shotwell will search their subdirectories as well.) Hope that answers your questions, -- Jim On Sat, Feb 12, 2011 at 12:21 PM, Bruno Girin wrote: > Hi Jim, > > Interesting! That brings a number of questions: > * When it comes to distributing plug-ins, what is your preferred > way of doing it? Developers distribute them on independent sites > or contribute them to the Shotwell repo? Personally, I'd prefer > the latter as I'm confortable writing code but I would struggle > to work out sensible build and packaging code. > * If the latter, would you rather offer a single package that > includes Shotwell + plugins or several packages, one for > Shotwell core and others for the various plugins? > * And if plugins are distributed separately, what is the plan to > make them discoverable? > > By the way, I get the following error when starting Shotwell with the > current trunk: > > shotwell: symbol lookup > error: /usr/local/lib/shotwell/plugins/builtin/spitter.so: undefined > symbol: spit_wad_get_type > > Cheers, > > Bruno > > > On Tue, 2011-02-08 at 19:29 -0800, Jim Nelson wrote: > > Hi Rodney, > > > > To jump in here, there's still some work to be done to support plug-in > > writers. We wanted to make sure our own plug-ins worked first so we > weren't > > putting untested interfaces out into the world. > > > > One ticket you should be aware of: http://trac.yorba.org/ticket/3160 This > > is to have Shotwell install the .h and VAPI files in a "make install". > This > > will only happen if a switch is enabled with the configure script. > > > > As part of this work we'll also produce and install a .pc file. > > > > Until then, you'll need to copy the generated .h, .vapi, and .dep files > to > > your project and include them in your build (the valac --vapidir option > is > > useful here). Because the .vapi files wants to look for the .h files in > a > > plugins/ subdirectory, they should be placed there, i.e. > my_project/plugins. > > > > Once Shotwell is capable of installing the header and VAPIs, you won't > need > > to include them in your project directory. > > > > -- Jim > > > > On Tue, Feb 8, 2011 at 5:53 PM, Lucas Beeler wrote: > > > > > Hi Rodney, > > > > > > Sorry for not answering your questions! Admittedly, my previous email > > > was probably more of an introduction to the state of the Shotwell > > > plug-in system than it was a specific response to your points. Once > > > again, I apologize. I'll hit your questions one-by-one this time: > > > > > > > Is there a shared library that the plug-ins link > > > > to for the Spit.* API/Interfaces? > > > > > > No. The plug-ins link directly with the Shotwell executable. There's > > > no stub library or developer package that needs to be installed or > > > that appears in Synaptic or as a pkg-config module. All of the > > > references to the word "package" in the Shotwell make files refer to > > > Vala packages. As you noted, a Vala package isn't a "package" in the > > > sense of Synaptic or pkg-config. It's just a .vapi file and a .deps > > > file. > > > > > > > is there also a .gir being generated for them? > > > > > > No. Shotwell doesn't use GObject introspection to discover interfaces. > > > Interface specification is all done directly through .vapi and .deps > > > files. > > > > > > > If so, is there a .vapi/.deps being built for those? > > > > > > Yes. The .vapi and .deps files for the plug-in interfaces are > > > generated automatically by the Shotwell build system. Simply running > > > "./configure ; make" will cause the files shotwell-spit-1.0.vapi, > > > shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and > > > shotwell-publishing-1.0.deps to appear in the > > > ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for > > > interface specification, at least as far as the Vala compiler is > > > concerned. If you're curious, the make rules that generate these files > > > are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. > > > > > > > If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? > > > > > > No. The Vala compiler will specify the CFLAGS and LDFLAGS variables > > > automatically when it invokes gcc as a child process. Right now, if > > > you want to develop plug-ins in C instead of Vala, you'll need to set > > > these up manually. > > > > > > Cheers, > > > Lucas > > > _______________________________________________ > > > Shotwell mailing list > > > Shotwell at lists.yorba.org > > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > > > > _______________________________________________ > > Shotwell mailing list > > Shotwell at lists.yorba.org > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From adam at yorba.org Mon Feb 14 21:29:11 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 14 Feb 2011 13:29:11 -0800 Subject: [Shotwell] Going back in time In-Reply-To: References: Message-ID: <4D599EA7.7040507@yorba.org> On 02/11/2011 03:58 PM, Lorenzo Baldacchini wrote: > Hello everybody > > is there a way to obtain the svn version of shotwell of the last week? > I can't compile the last version, but the 15 days ago version was > perfect. > Can you help me? > Thanks a lot Lorenzo, what error are you seeing compiling the latest version? We'd like to fix it so you can stay current. :) adam From antony at onlymee.co.uk Tue Feb 15 14:08:33 2011 From: antony at onlymee.co.uk (Antony Mee) Date: Tue, 15 Feb 2011 14:08:33 +0000 Subject: [Shotwell] GSoC 2011 In-Reply-To: <1297636640.12109.18.camel@thinky> References: <1297636640.12109.18.camel@thinky> Message-ID: I had a similar thought - my use case simply being a multi-user system when the whole family can use a common library and switch users 'safely'. (What to do about the photos you don't want the kids to see?!) It may be ambitious but please make this happen if you can! Antony On 13 Feb 2011 22:37, "Andreas Brauchli" wrote: > Dear shotwell team > > are there any plans for yorba/shotwell to apply for the google summer of > code 2011? I've seen last year's wiki page [1] and would totally love to > work on shotwell this summer! > > What i have in mind is the idea of a multi-user/multi-computer shotwell > or shotwell server instance (something like [2]) so that a photo > collection can be simultaneously accessed and modified from multiple > frontends but would also allow each shotwell instance - think on a > laptop - to locally cache (parts of) the collection. > > Students, please voice yourselves to encourage yorba to apply for a gsoc > spot and to provide some mentors - and the others to suggest or point > out feature requests that would keep a student busy for a good summer of > code. > > GSoC website: http://www.google-melange.com/ > > cheers > andreas > > [1] http://trac.yorba.org/wiki/SummerCodeIdeas > [2] http://trac.yorba.org/ticket/1572 > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From vivien.didelot at gmail.com Tue Feb 15 14:32:30 2011 From: vivien.didelot at gmail.com (Vivien Didelot) Date: Tue, 15 Feb 2011 09:32:30 -0500 Subject: [Shotwell] GSoC 2011 In-Reply-To: References: <1297636640.12109.18.camel@thinky> Message-ID: Hi, That are great ideas! For example I have a desktop and a laptop, I thought about pushing everything to a local server, but that's becoming a bit tricky... The family case is a good example again! So a *distributed* option for shotwell would be very useful. The antony's idea has a less important priority (for me) but is quite nice too. What about *sensible* photos you want to manage but you don't want anybody to browse them if they just open shotwell on your machine? (e.g. the family computer case). Two *easy-to-do* options (I guess) would be : - adding a special tag feature (let's say "sensible" with a beautiful locker or warning icon) that requires the sudo password (or whatever for Windows) each time you want to browse them (or even better, just one time for each instance of shotwell). - a "Show sensible photos" checkbox in the Edition menu (unchecked at startup) that requires the sudo password for each instance of shotwell if you check it. Regards, Vivien. On Tue, Feb 15, 2011 at 9:08 AM, Antony Mee wrote: > I had a similar thought - my use case simply being a multi-user system when > the whole family can use a common library and switch users 'safely'. (What > to do about the photos you don't want the kids to see?!) > > It may be ambitious but please make this happen if you can! > > Antony > On 13 Feb 2011 22:37, "Andreas Brauchli" wrote: > > Dear shotwell team > > > > are there any plans for yorba/shotwell to apply for the google summer of > > code 2011? I've seen last year's wiki page [1] and would totally love to > > work on shotwell this summer! > > > > What i have in mind is the idea of a multi-user/multi-computer shotwell > > or shotwell server instance (something like [2]) so that a photo > > collection can be simultaneously accessed and modified from multiple > > frontends but would also allow each shotwell instance - think on a > > laptop - to locally cache (parts of) the collection. > > > > Students, please voice yourselves to encourage yorba to apply for a gsoc > > spot and to provide some mentors - and the others to suggest or point > > out feature requests that would keep a student busy for a good summer of > > code. > > > > GSoC website: http://www.google-melange.com/ > > > > cheers > > andreas > > > > [1] http://trac.yorba.org/wiki/SummerCodeIdeas > > [2] http://trac.yorba.org/ticket/1572 > > > > > > _______________________________________________ > > 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 > -- Vivien Didelot, vivien.didelot.org From el.cameleon.1 at gmail.com Tue Feb 15 14:55:20 2011 From: el.cameleon.1 at gmail.com (Vincent) Date: Tue, 15 Feb 2011 15:55:20 +0100 Subject: [Shotwell] GSoC 2011 In-Reply-To: References: <1297636640.12109.18.camel@thinky> Message-ID: On Tue, Feb 15, 2011 at 3:32 PM, Vivien Didelot wrote: > Hi, > Two *easy-to-do* options (I guess) would be : > > - adding a special tag feature (let's say "sensible" with a beautiful > locker or warning icon) that requires the sudo password (or whatever for > Windows) each time you want to browse them (or even better, just one time > for each instance of shotwell). > - a "Show sensible photos" checkbox in the Edition menu (unchecked at > startup) that requires the sudo password for each instance of shotwell if > you check it. > > I think this would not be interesting because your private photo in Shotwell will be public on your hard disk, so it has no sens to forbid access only in Shotwell. But maybe Shotwell could change the status of some photos/folder in order to share them with other users or to restrict their access only to the current users. From brunogirin at gmail.com Tue Feb 15 19:45:15 2011 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 15 Feb 2011 19:45:15 +0000 Subject: [Shotwell] Writing Plug-ins In-Reply-To: References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> <1297542104.1855.23.camel@nuuk> Message-ID: Hi Jim, My question was from a user's point of view: how can a Shotwell user discover new plugins? E.g. how does a user know that if he goes to foo.com, I'll find a publishing plugin for barpics.net? This subject was actually discussed in the context of LibreOffice at FOSDEM a week ago: there are lots of extensions for OpenOffice/LibreOffice but users don't know about them so they believe that the software can't do what they want it to do. Same for Shotwell: you could have tons of plugins available, if there is no easy way for users to find them, they won't use them and this will potentially reflect on the software itself. One simple way to solve this could be to have a plugin directory in the Shotwell wiki. In terms of packaging, what could be of tremendous help is if there was some simple plugin packaging how-to on the wiki: for instance, I'd have no problem coding a plugin but I would not know where to start in order to package it in a .deb that actually works. The there's the aspect of getting the plugins in the distros. I agree that this is distro specific but having pointers along the packaging info would be of great help. For instance, do we know what it would take for a plugin to appear as an add-on to Shotwell in the Ubuntu Software Center (see GnuCash for an example)? Ideally, when you find Shotwell in the software centre, the plugins that are available in the distro should appear as add-ons (which would in turn make them more discoverable by the users). I'm conscious that none of the above has an easy answer and is probably not trivial to do but making sure that the whole plugin ecosystem works beyond the coding and API aspects can greatly enhance the feature. Cheers, Bruno On 14 February 2011 21:08, Jim Nelson wrote: > Hi Bruno, > > Regarding the error, two things happened: (a) we changed the API slightly > and (b) we removed one of the built-in plugins (which was there just for > testing; it's essentially been moved to the samples directory).? Shotwell is > attempting to load an old .so.? If you remove that spitter.so file, Shotwell > should start. > > To answer your questions: > > 1. At this point we envision developers distributing their own plug-ins.? If > a contributor offers us a plugin that we think belongs in the Shotwell core, > then we would accept it and move it into our source tree.? But Yorba does > not want to become the central repository of all Shotwell plugins. > > 2. We plan on bundling our core plugins with Shotwell.? Other plugins will > (most likely) be packaged separately.? Note that packagers and/or distros > may bundle a number of those plugins together and offer them as a single > separate download.? That's beyond our purview. > > 3. Today Shotwell discovers plugins only when they've been installed in one > of two locations: > > /usr/lib/shotwell/plugins > ~/.gnome2/shotwell/plugins > > The first is for plugins available system-wide, the second for plugins only > available to that user.? (Shotwell will search their subdirectories as > well.) > > Hope that answers your questions, > > -- Jim > > On Sat, Feb 12, 2011 at 12:21 PM, Bruno Girin wrote: >> >> Hi Jim, >> >> Interesting! That brings a number of questions: >> ? ? ?* When it comes to distributing plug-ins, what is your preferred >> ? ? ? ?way of doing it? Developers distribute them on independent sites >> ? ? ? ?or contribute them to the Shotwell repo? Personally, I'd prefer >> ? ? ? ?the latter as I'm confortable writing code but I would struggle >> ? ? ? ?to work out sensible build and packaging code. >> ? ? ?* If the latter, would you rather offer a single package that >> ? ? ? ?includes Shotwell + plugins or several packages, one for >> ? ? ? ?Shotwell core and others for the various plugins? >> ? ? ?* And if plugins are distributed separately, what is the plan to >> ? ? ? ?make them discoverable? >> >> By the way, I get the following error when starting Shotwell with the >> current trunk: >> >> shotwell: symbol lookup >> error: /usr/local/lib/shotwell/plugins/builtin/spitter.so: undefined >> symbol: spit_wad_get_type >> >> Cheers, >> >> Bruno >> >> >> On Tue, 2011-02-08 at 19:29 -0800, Jim Nelson wrote: >> > Hi Rodney, >> > >> > To jump in here, there's still some work to be done to support plug-in >> > writers. ?We wanted to make sure our own plug-ins worked first so we >> > weren't >> > putting untested interfaces out into the world. >> > >> > One ticket you should be aware of: http://trac.yorba.org/ticket/3160 >> > ?This >> > is to have Shotwell install the .h and VAPI files in a "make install". >> > ?This >> > will only happen if a switch is enabled with the configure script. >> > >> > As part of this work we'll also produce and install a .pc file. >> > >> > Until then, you'll need to copy the generated .h, .vapi, and .dep files >> > to >> > your project and include them in your build (the valac --vapidir option >> > is >> > useful here). ?Because the .vapi files wants to look for the .h files in >> > a >> > plugins/ subdirectory, they should be placed there, i.e. >> > my_project/plugins. >> > >> > Once Shotwell is capable of installing the header and VAPIs, you won't >> > need >> > to include them in your project directory. >> > >> > -- Jim >> > >> > On Tue, Feb 8, 2011 at 5:53 PM, Lucas Beeler wrote: >> > >> > > Hi Rodney, >> > > >> > > Sorry for not answering your questions! Admittedly, my previous email >> > > was probably more of an introduction to the state of the Shotwell >> > > plug-in system than it was a specific response to your points. Once >> > > again, I apologize. I'll hit your questions one-by-one this time: >> > > >> > > > Is there a shared library that the plug-ins link >> > > > to for the Spit.* API/Interfaces? >> > > >> > > No. The plug-ins link directly with the Shotwell executable. There's >> > > no stub library or developer package that needs to be installed or >> > > that appears in Synaptic or as a pkg-config module. All of the >> > > references to the word "package" in the Shotwell make files refer to >> > > Vala packages. As you noted, a Vala package isn't a "package" in the >> > > sense of Synaptic or pkg-config. It's just a .vapi file and a .deps >> > > file. >> > > >> > > > is there also a .gir being generated for them? >> > > >> > > No. Shotwell doesn't use GObject introspection to discover interfaces. >> > > Interface specification is all done directly through .vapi and .deps >> > > files. >> > > >> > > > If so, is there a .vapi/.deps being built for those? >> > > >> > > Yes. The .vapi and .deps files for the plug-in interfaces are >> > > generated automatically by the Shotwell build system. Simply running >> > > "./configure ; make" will cause the files shotwell-spit-1.0.vapi, >> > > shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and >> > > shotwell-publishing-1.0.deps to appear in the >> > > ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for >> > > interface specification, at least as far as the Vala compiler is >> > > concerned. If you're curious, the make rules that generate these files >> > > are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. >> > > >> > > > If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? >> > > >> > > No. The Vala compiler will specify the CFLAGS and LDFLAGS variables >> > > automatically when it invokes gcc as a child process. Right now, if >> > > you want to develop plug-ins in C instead of Vala, you'll need to set >> > > these up manually. >> > > >> > > Cheers, >> > > Lucas >> > > _______________________________________________ >> > > Shotwell mailing list >> > > Shotwell at lists.yorba.org >> > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> > > >> > _______________________________________________ >> > Shotwell mailing list >> > Shotwell at lists.yorba.org >> > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> >> >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > -- Bruno Visit my weblog: http://brunogirin.blogspot.com From adam at yorba.org Wed Feb 16 02:13:29 2011 From: adam at yorba.org (Adam Dingle) Date: Tue, 15 Feb 2011 18:13:29 -0800 Subject: [Shotwell] Writing Plug-ins In-Reply-To: References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> <1297542104.1855.23.camel@nuuk> Message-ID: <4D5B32C9.4000709@yorba.org> Bruno, today at Yorba we met to discuss plugin packaging/distribution more. Here's our tentative plan. The core Shotwell publishing plugins (Facebook, Flickr, Picasa Web, YouTube) will continue to live in the Shotwell trunk. Starting in Shotwell 0.9, they will build into a shared library separate from the main Shotwell executable. Other existing plugins (Yandex, Piwigo) will stay in the Shotwell trunk for 0.9, but will build into an extra shared library which is separate from the core plugin shared library. In the Shotwell 0.10 time frame, we plan to move these plugins to a separate shotwell-plugins source tarball which will be hosted in version control at Yorba. Other authors may contribute plugins to shotwell-plugins as long as they seem to be of good quality. The bar for getting into Shotwell core is very high (major services only, all code carefully reviewed at Yorba). For shotwell-plugins it will not be as high, but we will certainly reject plugins that contain crashing bugs, for example. It will be up to distributions to decide whether to install and/or enable the shotwell-plugins package by default. I think they will probably not, but users will be able to install this package easily if they want it. Finally, we'll have a Shotwell wiki page which lists all existing plugins (including core plugins, those in the extra shotwell-plugins tarball, and those hosted by third parties). Hopefully there will also be some helpful tutorials helping plugin authors get started. All of this echoes common practice in the GNOME world. For example, gedit includes some core plugins in its source package, but there is a gedit-plugins source package containing additional plugins and then a wiki page listing zillions of third-party plugins. adam On 02/15/2011 11:45 AM, Bruno Girin wrote: > Hi Jim, > > My question was from a user's point of view: how can a Shotwell user > discover new plugins? E.g. how does a user know that if he goes to > foo.com, I'll find a publishing plugin for barpics.net? This subject > was actually discussed in the context of LibreOffice at FOSDEM a week > ago: there are lots of extensions for OpenOffice/LibreOffice but users > don't know about them so they believe that the software can't do what > they want it to do. Same for Shotwell: you could have tons of plugins > available, if there is no easy way for users to find them, they won't > use them and this will potentially reflect on the software itself. One > simple way to solve this could be to have a plugin directory in the > Shotwell wiki. > > In terms of packaging, what could be of tremendous help is if there > was some simple plugin packaging how-to on the wiki: for instance, I'd > have no problem coding a plugin but I would not know where to start in > order to package it in a .deb that actually works. > > The there's the aspect of getting the plugins in the distros. I agree > that this is distro specific but having pointers along the packaging > info would be of great help. For instance, do we know what it would > take for a plugin to appear as an add-on to Shotwell in the Ubuntu > Software Center (see GnuCash for an example)? Ideally, when you find > Shotwell in the software centre, the plugins that are available in the > distro should appear as add-ons (which would in turn make them more > discoverable by the users). > > I'm conscious that none of the above has an easy answer and is > probably not trivial to do but making sure that the whole plugin > ecosystem works beyond the coding and API aspects can greatly enhance > the feature. > > Cheers, > > Bruno > > On 14 February 2011 21:08, Jim Nelson wrote: >> Hi Bruno, >> >> Regarding the error, two things happened: (a) we changed the API slightly >> and (b) we removed one of the built-in plugins (which was there just for >> testing; it's essentially been moved to the samples directory). Shotwell is >> attempting to load an old .so. If you remove that spitter.so file, Shotwell >> should start. >> >> To answer your questions: >> >> 1. At this point we envision developers distributing their own plug-ins. If >> a contributor offers us a plugin that we think belongs in the Shotwell core, >> then we would accept it and move it into our source tree. But Yorba does >> not want to become the central repository of all Shotwell plugins. >> >> 2. We plan on bundling our core plugins with Shotwell. Other plugins will >> (most likely) be packaged separately. Note that packagers and/or distros >> may bundle a number of those plugins together and offer them as a single >> separate download. That's beyond our purview. >> >> 3. Today Shotwell discovers plugins only when they've been installed in one >> of two locations: >> >> /usr/lib/shotwell/plugins >> ~/.gnome2/shotwell/plugins >> >> The first is for plugins available system-wide, the second for plugins only >> available to that user. (Shotwell will search their subdirectories as >> well.) >> >> Hope that answers your questions, >> >> -- Jim >> >> On Sat, Feb 12, 2011 at 12:21 PM, Bruno Girin wrote: >>> Hi Jim, >>> >>> Interesting! That brings a number of questions: >>> * When it comes to distributing plug-ins, what is your preferred >>> way of doing it? Developers distribute them on independent sites >>> or contribute them to the Shotwell repo? Personally, I'd prefer >>> the latter as I'm confortable writing code but I would struggle >>> to work out sensible build and packaging code. >>> * If the latter, would you rather offer a single package that >>> includes Shotwell + plugins or several packages, one for >>> Shotwell core and others for the various plugins? >>> * And if plugins are distributed separately, what is the plan to >>> make them discoverable? >>> >>> By the way, I get the following error when starting Shotwell with the >>> current trunk: >>> >>> shotwell: symbol lookup >>> error: /usr/local/lib/shotwell/plugins/builtin/spitter.so: undefined >>> symbol: spit_wad_get_type >>> >>> Cheers, >>> >>> Bruno >>> >>> >>> On Tue, 2011-02-08 at 19:29 -0800, Jim Nelson wrote: >>>> Hi Rodney, >>>> >>>> To jump in here, there's still some work to be done to support plug-in >>>> writers. We wanted to make sure our own plug-ins worked first so we >>>> weren't >>>> putting untested interfaces out into the world. >>>> >>>> One ticket you should be aware of: http://trac.yorba.org/ticket/3160 >>>> This >>>> is to have Shotwell install the .h and VAPI files in a "make install". >>>> This >>>> will only happen if a switch is enabled with the configure script. >>>> >>>> As part of this work we'll also produce and install a .pc file. >>>> >>>> Until then, you'll need to copy the generated .h, .vapi, and .dep files >>>> to >>>> your project and include them in your build (the valac --vapidir option >>>> is >>>> useful here). Because the .vapi files wants to look for the .h files in >>>> a >>>> plugins/ subdirectory, they should be placed there, i.e. >>>> my_project/plugins. >>>> >>>> Once Shotwell is capable of installing the header and VAPIs, you won't >>>> need >>>> to include them in your project directory. >>>> >>>> -- Jim >>>> >>>> On Tue, Feb 8, 2011 at 5:53 PM, Lucas Beeler wrote: >>>> >>>>> Hi Rodney, >>>>> >>>>> Sorry for not answering your questions! Admittedly, my previous email >>>>> was probably more of an introduction to the state of the Shotwell >>>>> plug-in system than it was a specific response to your points. Once >>>>> again, I apologize. I'll hit your questions one-by-one this time: >>>>> >>>>>> Is there a shared library that the plug-ins link >>>>>> to for the Spit.* API/Interfaces? >>>>> No. The plug-ins link directly with the Shotwell executable. There's >>>>> no stub library or developer package that needs to be installed or >>>>> that appears in Synaptic or as a pkg-config module. All of the >>>>> references to the word "package" in the Shotwell make files refer to >>>>> Vala packages. As you noted, a Vala package isn't a "package" in the >>>>> sense of Synaptic or pkg-config. It's just a .vapi file and a .deps >>>>> file. >>>>> >>>>>> is there also a .gir being generated for them? >>>>> No. Shotwell doesn't use GObject introspection to discover interfaces. >>>>> Interface specification is all done directly through .vapi and .deps >>>>> files. >>>>> >>>>>> If so, is there a .vapi/.deps being built for those? >>>>> Yes. The .vapi and .deps files for the plug-in interfaces are >>>>> generated automatically by the Shotwell build system. Simply running >>>>> "./configure ; make" will cause the files shotwell-spit-1.0.vapi, >>>>> shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and >>>>> shotwell-publishing-1.0.deps to appear in the >>>>> ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for >>>>> interface specification, at least as far as the Vala compiler is >>>>> concerned. If you're curious, the make rules that generate these files >>>>> are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. >>>>> >>>>>> If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? >>>>> No. The Vala compiler will specify the CFLAGS and LDFLAGS variables >>>>> automatically when it invokes gcc as a child process. Right now, if >>>>> you want to develop plug-ins in C instead of Vala, you'll need to set >>>>> these up manually. >>>>> >>>>> Cheers, >>>>> Lucas >>>>> _______________________________________________ >>>>> Shotwell mailing list >>>>> Shotwell at lists.yorba.org >>>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>>>> >>>> _______________________________________________ >>>> Shotwell mailing list >>>> Shotwell at lists.yorba.org >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> _______________________________________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> > > From ralf.butler at web.de Wed Feb 16 05:54:02 2011 From: ralf.butler at web.de (rbutler) Date: Tue, 15 Feb 2011 21:54:02 -0800 (PST) Subject: [Shotwell] Shotwell & Darktable Workflow Message-ID: <1297835642838-33549.post@talk.nabble.com> Hi there, I love playing with darktable. However, it is a terrible slow (even version 0.8) compared to other RAW programs and lacks of features like diashow. On the other hand I find shotwell wonderful for browsing and tagging images. But even though it can read RAW files it, of course, doesn't interpret a sidecar file that has been created with darktable. To work with both of them it is necessary to export all raw files to jpg e.g. and to than import them into shotwell. Does anyone have an alternative way? How does your workflow looks like if you're dealing with raw files at shotwell? Thank you, Ralf -- View this message in context: http://shotwell.3510.www.nabble.com/Shotwell-Darktable-Workflow-tp33549p33549.html Sent from the Shotwell mailing list archive at Nabble.com. From accounts at thesustainablestore.com.au Wed Feb 16 10:58:33 2011 From: accounts at thesustainablestore.com.au (Sustainable Store Accounts Dept) Date: Wed, 16 Feb 2011 21:58:33 +1100 Subject: [Shotwell] vala problem when compiling Message-ID: I get this: ====================== make valac: error while loading shared libraries: libvala-0.10.so.0: cannot open shared object file: No such file or directory usage: minver valac: error while loading shared libraries: libvala-0.10.so.0: cannot open shared object file: No such file or directory Shotwell requires Vala compiler 0.9.8 or greater. You are running. make: *** [src/.stamp] Error 1 ========= vala 0.10 is installed as are other libraries. Can someone help please Ubuntu 10.04 Danny Raymond From adam at yorba.org Wed Feb 16 14:58:59 2011 From: adam at yorba.org (Adam Dingle) Date: Wed, 16 Feb 2011 06:58:59 -0800 Subject: [Shotwell] vala problem when compiling In-Reply-To: References: Message-ID: <4D5BE633.9090306@yorba.org> Danny, it looks like something is not right with your installation of Vala. - Where did you get Vala 0.10? From a PPA? Or did you build and install it yourself? - Are you sure that Vala 0.8 (from the Lucid repository) is not installed? - What do the following commands print? $ which valac $ ls -l /usr/lib/libvala* $ ls -l /usr/local/lib/libvala* - Try running "sudo ldconfig", then try building Shotwell again. Does that help? adam On 02/16/2011 02:58 AM, Sustainable Store Accounts Dept wrote: > I get this: > ====================== > make > valac: error while loading shared libraries: libvala-0.10.so.0: cannot open > shared object file: No such file or directory > usage: minver > valac: error while loading shared libraries: libvala-0.10.so.0: cannot open > shared object file: No such file or directory > Shotwell requires Vala compiler 0.9.8 or greater. You are running. > make: *** [src/.stamp] Error 1 > ========= > vala 0.10 is installed as are other libraries. Can someone help please > > Ubuntu 10.04 > > Danny Raymond > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From accounts at thesustainablestore.com.au Wed Feb 16 21:36:43 2011 From: accounts at thesustainablestore.com.au (Sustainable Store Accounts Dept) Date: Thu, 17 Feb 2011 08:36:43 +1100 Subject: [Shotwell] vala compile issue Message-ID: Compiled myself from download on vala site === get this: dan at dan-desktop:~$ which valac /usr/local/bin/valac dan at dan-desktop:~$ ls -l /usr/lib/libvala* ls: cannot access /usr/lib/libvala*: No such file or directory dan at dan-desktop:~$ ls -l /usr/local/lib/libvala* -rwxr-xr-x 1 root root 1033 2011-02-16 21:21 /usr/local/lib/ libvala-0.10.la lrwxrwxrwx 1 root root 21 2011-02-16 21:21 /usr/local/lib/ libvala-0.10.so -> libvala-0.10.so.0.0.0 lrwxrwxrwx 1 root root 21 2011-02-16 21:21 /usr/local/lib/libvala-0.10.so.0 -> libvala-0.10.so.0.0.0 -rwxr-xr-x 1 root root 8777035 2011-02-16 21:21 /usr/local/lib/libvala-0.10.so.0.0.0 dan at dan-desktop:~$ -- The Sustainable Store Pty Ltd 320 Grey Street, Glen Innes, NSW Australia 2370 +612 6732 3288 From accounts at thesustainablestore.com.au Wed Feb 16 23:14:51 2011 From: accounts at thesustainablestore.com.au (Sustainable Store Accounts Dept) Date: Thu, 17 Feb 2011 10:14:51 +1100 Subject: [Shotwell] vala recompile error Message-ID: thanks sorted out with sudo ldconfig dan raymond -- The Sustainable Store Pty Ltd 320 Grey Street, Glen Innes, NSW Australia 2370 +612 6732 3288 From nsavch at gmail.com Thu Feb 17 14:40:00 2011 From: nsavch at gmail.com (Nickolay S. Savchenko) Date: Thu, 17 Feb 2011 16:40:00 +0200 Subject: [Shotwell] shotwell error - database disk image is malformed Message-ID: <1297953600.6228.5.camel@dynatos> Hi dear shotwell users and developers! I encountered the following problem with shotwell today. I was using default shotwell version from ubuntu 10.10, it worked quite good. But today shotwell crashed during photo import. I looked error in .xsession-errors, it was following: ** ERROR **: DatabaseTables.vala:55: add_photo: [11] database disk image is malformed I then run from gdb, here is the backtrace: Program received signal SIGABRT, Aborted. 0x00007ffff0b6fba5 in raise () from /lib/libc.so.6 (gdb) backtrace full #0 0x00007ffff0b6fba5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00007ffff0b736b0 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x00007ffff1425f0a in g_logv () from /lib/libglib-2.0.so.0 No symbol table info available. #3 0x00007ffff1425fa3 in g_log () from /lib/libglib-2.0.so.0 No symbol table info available. #4 0x000000000046b4df in database_table_fatal () No symbol table info available. #5 0x000000000046f782 in photo_table_add () No symbol table info available. #6 0x00000000004d7510 in library_photo_import_create () No symbol table info available. #7 0x00000000004e9606 in ?? () No symbol table info available. #8 0x000000000055aa82 in ?? () No symbol table info available. #9 0x00007ffff141b342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 No symbol table info available. #10 0x00007ffff141f2a8 in ?? () from /lib/libglib-2.0.so.0 No symbol table info available. #11 0x00007ffff141f7b5 in g_main_loop_run () from /lib/libglib-2.0.so.0 No symbol table info available. #12 0x00007ffff3ce33e7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #13 0x0000000000455ead in library_exec () No symbol table info available. #14 0x0000000000456572 in _vala_main () No symbol table info available. #15 0x00000000004565f9 in main () No symbol table info available. (gdb) Then I tried to install shotwell 0.8.1 from ppa, and now it doesn't even start. nss at dynatos:~/Music/lessons$ SHOTWELL_LOG=1 shotwell ** ERROR **: DatabaseTables.vala:57: VideoTable constructor: [11] database disk image is malformed aborting... Aborted I tried to navigate through database using console sqlite3 tool, database looks not damaged. I tried random select queries and they worked. So it's quite strange that shotwell thinks that the database is corrupt. I looked into faq and user guide and didn't find any information about database repairing. Any ideas? -- best regards, Nickolay Savchenko From brunogirin at gmail.com Thu Feb 17 22:42:32 2011 From: brunogirin at gmail.com (Bruno Girin) Date: Thu, 17 Feb 2011 22:42:32 +0000 Subject: [Shotwell] Writing Plug-ins In-Reply-To: <4D5B32C9.4000709@yorba.org> References: <1297178627.7526.16.camel@localhost> <1297211040.2413.3.camel@localhost> <1297542104.1855.23.camel@nuuk> <4D5B32C9.4000709@yorba.org> Message-ID: <1297982552.1749.13.camel@nuuk> Adam, That sounds like a great plan :-) Bruno On Tue, 2011-02-15 at 18:13 -0800, Adam Dingle wrote: > Bruno, > > today at Yorba we met to discuss plugin packaging/distribution more. > Here's our tentative plan. > > The core Shotwell publishing plugins (Facebook, Flickr, Picasa Web, > YouTube) will continue to live in the Shotwell trunk. Starting in > Shotwell 0.9, they will build into a shared library separate from the > main Shotwell executable. > > Other existing plugins (Yandex, Piwigo) will stay in the Shotwell trunk > for 0.9, but will build into an extra shared library which is separate > from the core plugin shared library. In the Shotwell 0.10 time frame, > we plan to move these plugins to a separate shotwell-plugins source > tarball which will be hosted in version control at Yorba. Other authors > may contribute plugins to shotwell-plugins as long as they seem to be of > good quality. The bar for getting into Shotwell core is very high > (major services only, all code carefully reviewed at Yorba). For > shotwell-plugins it will not be as high, but we will certainly reject > plugins that contain crashing bugs, for example. It will be up to > distributions to decide whether to install and/or enable the > shotwell-plugins package by default. I think they will probably not, but > users will be able to install this package easily if they want it. > > Finally, we'll have a Shotwell wiki page which lists all existing > plugins (including core plugins, those in the extra shotwell-plugins > tarball, and those hosted by third parties). Hopefully there will also > be some helpful tutorials helping plugin authors get started. > > All of this echoes common practice in the GNOME world. For example, > gedit includes some core plugins in its source package, but there is a > gedit-plugins source package containing additional plugins and then a > wiki page listing zillions of third-party plugins. > > adam > > On 02/15/2011 11:45 AM, Bruno Girin wrote: > > Hi Jim, > > > > My question was from a user's point of view: how can a Shotwell user > > discover new plugins? E.g. how does a user know that if he goes to > > foo.com, I'll find a publishing plugin for barpics.net? This subject > > was actually discussed in the context of LibreOffice at FOSDEM a week > > ago: there are lots of extensions for OpenOffice/LibreOffice but users > > don't know about them so they believe that the software can't do what > > they want it to do. Same for Shotwell: you could have tons of plugins > > available, if there is no easy way for users to find them, they won't > > use them and this will potentially reflect on the software itself. One > > simple way to solve this could be to have a plugin directory in the > > Shotwell wiki. > > > > In terms of packaging, what could be of tremendous help is if there > > was some simple plugin packaging how-to on the wiki: for instance, I'd > > have no problem coding a plugin but I would not know where to start in > > order to package it in a .deb that actually works. > > > > The there's the aspect of getting the plugins in the distros. I agree > > that this is distro specific but having pointers along the packaging > > info would be of great help. For instance, do we know what it would > > take for a plugin to appear as an add-on to Shotwell in the Ubuntu > > Software Center (see GnuCash for an example)? Ideally, when you find > > Shotwell in the software centre, the plugins that are available in the > > distro should appear as add-ons (which would in turn make them more > > discoverable by the users). > > > > I'm conscious that none of the above has an easy answer and is > > probably not trivial to do but making sure that the whole plugin > > ecosystem works beyond the coding and API aspects can greatly enhance > > the feature. > > > > Cheers, > > > > Bruno > > > > On 14 February 2011 21:08, Jim Nelson wrote: > >> Hi Bruno, > >> > >> Regarding the error, two things happened: (a) we changed the API slightly > >> and (b) we removed one of the built-in plugins (which was there just for > >> testing; it's essentially been moved to the samples directory). Shotwell is > >> attempting to load an old .so. If you remove that spitter.so file, Shotwell > >> should start. > >> > >> To answer your questions: > >> > >> 1. At this point we envision developers distributing their own plug-ins. If > >> a contributor offers us a plugin that we think belongs in the Shotwell core, > >> then we would accept it and move it into our source tree. But Yorba does > >> not want to become the central repository of all Shotwell plugins. > >> > >> 2. We plan on bundling our core plugins with Shotwell. Other plugins will > >> (most likely) be packaged separately. Note that packagers and/or distros > >> may bundle a number of those plugins together and offer them as a single > >> separate download. That's beyond our purview. > >> > >> 3. Today Shotwell discovers plugins only when they've been installed in one > >> of two locations: > >> > >> /usr/lib/shotwell/plugins > >> ~/.gnome2/shotwell/plugins > >> > >> The first is for plugins available system-wide, the second for plugins only > >> available to that user. (Shotwell will search their subdirectories as > >> well.) > >> > >> Hope that answers your questions, > >> > >> -- Jim > >> > >> On Sat, Feb 12, 2011 at 12:21 PM, Bruno Girin wrote: > >>> Hi Jim, > >>> > >>> Interesting! That brings a number of questions: > >>> * When it comes to distributing plug-ins, what is your preferred > >>> way of doing it? Developers distribute them on independent sites > >>> or contribute them to the Shotwell repo? Personally, I'd prefer > >>> the latter as I'm confortable writing code but I would struggle > >>> to work out sensible build and packaging code. > >>> * If the latter, would you rather offer a single package that > >>> includes Shotwell + plugins or several packages, one for > >>> Shotwell core and others for the various plugins? > >>> * And if plugins are distributed separately, what is the plan to > >>> make them discoverable? > >>> > >>> By the way, I get the following error when starting Shotwell with the > >>> current trunk: > >>> > >>> shotwell: symbol lookup > >>> error: /usr/local/lib/shotwell/plugins/builtin/spitter.so: undefined > >>> symbol: spit_wad_get_type > >>> > >>> Cheers, > >>> > >>> Bruno > >>> > >>> > >>> On Tue, 2011-02-08 at 19:29 -0800, Jim Nelson wrote: > >>>> Hi Rodney, > >>>> > >>>> To jump in here, there's still some work to be done to support plug-in > >>>> writers. We wanted to make sure our own plug-ins worked first so we > >>>> weren't > >>>> putting untested interfaces out into the world. > >>>> > >>>> One ticket you should be aware of: http://trac.yorba.org/ticket/3160 > >>>> This > >>>> is to have Shotwell install the .h and VAPI files in a "make install". > >>>> This > >>>> will only happen if a switch is enabled with the configure script. > >>>> > >>>> As part of this work we'll also produce and install a .pc file. > >>>> > >>>> Until then, you'll need to copy the generated .h, .vapi, and .dep files > >>>> to > >>>> your project and include them in your build (the valac --vapidir option > >>>> is > >>>> useful here). Because the .vapi files wants to look for the .h files in > >>>> a > >>>> plugins/ subdirectory, they should be placed there, i.e. > >>>> my_project/plugins. > >>>> > >>>> Once Shotwell is capable of installing the header and VAPIs, you won't > >>>> need > >>>> to include them in your project directory. > >>>> > >>>> -- Jim > >>>> > >>>> On Tue, Feb 8, 2011 at 5:53 PM, Lucas Beeler wrote: > >>>> > >>>>> Hi Rodney, > >>>>> > >>>>> Sorry for not answering your questions! Admittedly, my previous email > >>>>> was probably more of an introduction to the state of the Shotwell > >>>>> plug-in system than it was a specific response to your points. Once > >>>>> again, I apologize. I'll hit your questions one-by-one this time: > >>>>> > >>>>>> Is there a shared library that the plug-ins link > >>>>>> to for the Spit.* API/Interfaces? > >>>>> No. The plug-ins link directly with the Shotwell executable. There's > >>>>> no stub library or developer package that needs to be installed or > >>>>> that appears in Synaptic or as a pkg-config module. All of the > >>>>> references to the word "package" in the Shotwell make files refer to > >>>>> Vala packages. As you noted, a Vala package isn't a "package" in the > >>>>> sense of Synaptic or pkg-config. It's just a .vapi file and a .deps > >>>>> file. > >>>>> > >>>>>> is there also a .gir being generated for them? > >>>>> No. Shotwell doesn't use GObject introspection to discover interfaces. > >>>>> Interface specification is all done directly through .vapi and .deps > >>>>> files. > >>>>> > >>>>>> If so, is there a .vapi/.deps being built for those? > >>>>> Yes. The .vapi and .deps files for the plug-in interfaces are > >>>>> generated automatically by the Shotwell build system. Simply running > >>>>> "./configure ; make" will cause the files shotwell-spit-1.0.vapi, > >>>>> shotwell-spit-1.0.deps, shotwell-publishing-1.0.vapi, and > >>>>> shotwell-publishing-1.0.deps to appear in the > >>>>> ${SHOTWELL_ROOT}/plugins/ directory. These should be sufficient for > >>>>> interface specification, at least as far as the Vala compiler is > >>>>> concerned. If you're curious, the make rules that generate these files > >>>>> are located in the file ${SHOTWELL_ROOT}/src/plugins/mk/interfaces.mk. > >>>>> > >>>>>> If so, is there a .pc file to specify CFLAGS/LDFLAGS for linking? > >>>>> No. The Vala compiler will specify the CFLAGS and LDFLAGS variables > >>>>> automatically when it invokes gcc as a child process. Right now, if > >>>>> you want to develop plug-ins in C instead of Vala, you'll need to set > >>>>> these up manually. > >>>>> > >>>>> Cheers, > >>>>> Lucas > >>>>> _______________________________________________ > >>>>> Shotwell mailing list > >>>>> Shotwell at lists.yorba.org > >>>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > >>>>> > >>>> _______________________________________________ > >>>> Shotwell mailing list > >>>> Shotwell at lists.yorba.org > >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > >>> > >>> _______________________________________________ > >>> Shotwell mailing list > >>> Shotwell at lists.yorba.org > >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > >> > > > > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From mmassonnet at gmail.com Sat Feb 19 09:36:16 2011 From: mmassonnet at gmail.com (Mike Massonnet) Date: Sat, 19 Feb 2011 10:36:16 +0100 Subject: [Shotwell] Unable to start Shotwell 0.8.1 Message-ID: Hello, I have seen a few posts on this list about Shotwell 0.8.1 not starting, but I haven't found anything similar to what I'm facing. While Shotwell does start, it consumes more and more memory until it reaches a point where new memory can't be allocated. I have run strace on it, and in fact it shows the following result: mmap2(NULL, 262144, ...) = 0xae1a2000 mmap2(NULL, 520192, ...) = 0xae123000 mmap2(NULL, 1036288, ...) = 0xae026000 mmap2(NULL, 2068480, ...) = 0xade2d000 mmap2(NULL, 4132864, ...) = 0xada3c000 mmap2(NULL, 8261632, ...) = 0xad25b000 mmap2(NULL, 16519168, ...) = 0xac29a000 mmap2(NULL, 33034240, ...) = 0xaa319000 mmap2(NULL, 66064384, ...) = 0xa6418000 mmap2(NULL, 132124672, ...) = 0x9e617000 mmap2(NULL, 264245248, ...) = 0x8ea16000 mmap2(NULL, 528486400, ...) = 0x6f215000 mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) brk(0x494de000) = 0xa4de000 mmap2(NULL, 1057099776, ...) = -1 ENOMEM (Cannot allocate memory) mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) We can actually see that the allocated size is always doubled. Shotwell will keep running and consuming 100% CPU of one core (I'm glade to have two cores), and use almost all the RAM, but nothing seems to be progressing, no files seem to be read or written. I have tried to use an empty data directory, but it ends the same. The shotwell.log file contains only the following two lines: L 14195 2011-02-19 10:16:52 [MSG] main.vala:61: Verifying database ... L 14195 2011-02-19 10:16:53 [MSG] VideoSupport.vala:373: interpreter state cookie not found; assuming all video thumbnails are out of date Given this is the latest stable version, I'm reporting it here for now ;) Kind Regards -- Mike PS: my shotwell 0.6.1 won't start because it doesn't find libexiv2 anymore, and rebuilding it needs an older version of Vala, I have installed shotwell 0.8.1 from the ArchLinux package PPS: I'm the one who bugged you about this on twitter under @m8t From mmassonnet at gmail.com Sat Feb 19 09:41:15 2011 From: mmassonnet at gmail.com (Mike Massonnet) Date: Sat, 19 Feb 2011 10:41:15 +0100 Subject: [Shotwell] Unable to start Shotwell 0.8.1 In-Reply-To: References: Message-ID: Why I was sure I wasn't using an Aurora theme... switching to another theme fixed the issue. Kind Regards Mike 2011/2/19 Mike Massonnet : > Hello, > > I have seen a few posts on this list about Shotwell 0.8.1 not > starting, but I haven't found anything similar to what I'm facing. > > While Shotwell does start, it consumes more and more memory until it > reaches a point where new memory can't be allocated. I have run strace > on it, and in fact it shows the following result: > > mmap2(NULL, 262144, ...) = 0xae1a2000 > mmap2(NULL, 520192, ...) = 0xae123000 > mmap2(NULL, 1036288, ...) = 0xae026000 > mmap2(NULL, 2068480, ...) = 0xade2d000 > mmap2(NULL, 4132864, ...) = 0xada3c000 > mmap2(NULL, 8261632, ...) = 0xad25b000 > mmap2(NULL, 16519168, ...) = 0xac29a000 > mmap2(NULL, 33034240, ...) = 0xaa319000 > mmap2(NULL, 66064384, ...) = 0xa6418000 > mmap2(NULL, 132124672, ...) = 0x9e617000 > mmap2(NULL, 264245248, ...) = 0x8ea16000 > mmap2(NULL, 528486400, ...) = 0x6f215000 > mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) > brk(0x494de000) ? ? ? ? ? ? ? ? ? ? ? ? = 0xa4de000 > mmap2(NULL, 1057099776, ...) = -1 ENOMEM (Cannot allocate memory) > mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) > > We can actually see that the allocated size is always doubled. > > Shotwell will keep running and consuming 100% CPU of one core (I'm > glade to have two cores), and use almost all the RAM, but nothing > seems to be progressing, no files seem to be read or written. > > I have tried to use an empty data directory, but it ends the same. The > shotwell.log file contains only the following two lines: > > L 14195 2011-02-19 10:16:52 [MSG] main.vala:61: Verifying database ... > L 14195 2011-02-19 10:16:53 [MSG] VideoSupport.vala:373: interpreter > state cookie not found; assuming all video thumbnails are out of date > > Given this is the latest stable version, I'm reporting it here for now ;) > > Kind Regards > -- > Mike > PS: my shotwell 0.6.1 won't start because it doesn't find libexiv2 > anymore, and rebuilding it needs an older version of Vala, I have > installed shotwell 0.8.1 from the ArchLinux package > PPS: I'm the one who bugged you about this on twitter under @m8t > -- Mike From ralf.butler at web.de Mon Feb 21 08:25:55 2011 From: ralf.butler at web.de (Ralf Butler) Date: Mon, 21 Feb 2011 09:25:55 +0100 (CET) Subject: [Shotwell] Reading exif data out of MTS Message-ID: <235716284.3896123.1298276755211.JavaMail.fmail@mwmweb075> Hi there, are there any plans to support reading exif data out of an MTS file? So far I can import an MTS but it is not assigned to any event. Furthermore the Extended Information dialog list basically no data. Thanks, Ralf ___________________________________________________________ NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://produkte.web.de/go/webdefreephone From adam at yorba.org Mon Feb 21 15:37:07 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 21 Feb 2011 07:37:07 -0800 Subject: [Shotwell] Reading exif data out of MTS In-Reply-To: <235716284.3896123.1298276755211.JavaMail.fmail@mwmweb075> References: <235716284.3896123.1298276755211.JavaMail.fmail@mwmweb075> Message-ID: <4D6286A3.4030503@yorba.org> On 02/21/2011 12:25 AM, Ralf Butler wrote: > Hi there, are there any plans to support reading exif data out of an MTS file? So far I can import an MTS but it is not assigned to any event. Furthermore the Extended Information dialog list basically no data. > > Thanks, > Ralf Yes - we have a ticket for this: http://trac.yorba.org/ticket/3093 adam From pdo.smith at gmail.com Mon Feb 21 15:51:30 2011 From: pdo.smith at gmail.com (Peter DO Smith) Date: Mon, 21 Feb 2011 17:51:30 +0200 Subject: [Shotwell] Filter visibility Message-ID: I started up Shotwell (latest build from trunk) and was very disconcerted to find that very few of my photos were visible. Eventually I realised that a filter term from an earlier invocation of Shotwell was still active. I hit F8 to bring up the filter bar, cleared the term and all was well. But it was an alarming experience as I thought I has lost all my photos. As a result I would like to suggest that a) when a filter is active the filter bar is always visible b) the filter should not be carried over from one invocation of Shotwell to the next invocation. From adam at yorba.org Mon Feb 21 15:57:10 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 21 Feb 2011 07:57:10 -0800 Subject: [Shotwell] Filter visibility In-Reply-To: References: Message-ID: <4D628B56.6080201@yorba.org> Peter, On 02/21/2011 07:51 AM, Peter DO Smith wrote: > I started up Shotwell (latest build from trunk) and was very > disconcerted to find that very few of my photos were visible. > > Eventually I realised that a filter term from an earlier invocation of > Shotwell was still active. I hit F8 to bring up the filter bar, > cleared the term and all was well. But it was an alarming experience > as I thought I has lost all my photos. Thanks for being brave enough to run our trunk build! :) Glad you figured it out. > As a result I would like to suggest that > a) when a filter is active the filter bar is always visible Yes - we certainly agree. This is not implemented yet, but will be soon. > b) the filter should not be carried over from one invocation of > Shotwell to the next invocation. I'm not as sure about this one - if we implement (a), then it should be clear to the user when a filter is active and so it might be useful to persist the filter between invocations. Will think about this more. adam From pdo.smith at gmail.com Mon Feb 21 16:04:34 2011 From: pdo.smith at gmail.com (Peter DO Smith) Date: Mon, 21 Feb 2011 18:04:34 +0200 Subject: [Shotwell] Filter visibility In-Reply-To: <4D628B3E.3060106@yorba.org> References: <4D628B3E.3060106@yorba.org> Message-ID: Yes, agreed that if the filter is always visible then having the filter carry over to the next invocation can be quite useful. >From the usability point of view it is desirable that an action remains in place until the user chooses otherwise. So I agree with you. On Mon, Feb 21, 2011 at 5:56 PM, Adam Dingle wrote: > Peter, > > On 02/21/2011 07:51 AM, Peter DO Smith wrote: >> >> I started up Shotwell (latest build from trunk) and was very >> disconcerted to find that very few of my photos were visible. >> >> Eventually I realised that a filter term from an earlier invocation of >> Shotwell was still active. I hit F8 to bring up the filter bar, >> cleared the term and all was well. But it was an alarming experience >> as I thought I has lost all my photos. > > Thanks for being brave enough to run our trunk build! ?:) ?Glad you figured > it out. > >> As a result I would like to suggest that >> a) when a filter is active the filter bar is always visible > > Yes - we certainly agree. ?This is not implemented yet, but will be soon. > >> b) the filter should not be carried over from one invocation of >> Shotwell to the next invocation. > > I'm not as sure about this one - if we implement (a), then it should be > clear to the user when a filter is active and so it might be useful to > persist the filter between invocations. ?Will think about this more. > > adam > > From adam at yorba.org Mon Feb 21 17:10:03 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 21 Feb 2011 09:10:03 -0800 Subject: [Shotwell] Unable to start Shotwell 0.8.1 In-Reply-To: References: Message-ID: <4D629C6B.4080006@yorba.org> Mike, not completely sure I understand your last email - can you confirm the following? - When you start Shotwell when using the Aurora theme, Shotwell allocates all available memory and uses 100% CPU. - When you start Shotwell when using other themes, everything works fine. adam On 02/19/2011 01:41 AM, Mike Massonnet wrote: > Why I was sure I wasn't using an Aurora theme... switching to another > theme fixed the issue. > > Kind Regards > Mike > > 2011/2/19 Mike Massonnet: >> Hello, >> >> I have seen a few posts on this list about Shotwell 0.8.1 not >> starting, but I haven't found anything similar to what I'm facing. >> >> While Shotwell does start, it consumes more and more memory until it >> reaches a point where new memory can't be allocated. I have run strace >> on it, and in fact it shows the following result: >> >> mmap2(NULL, 262144, ...) = 0xae1a2000 >> mmap2(NULL, 520192, ...) = 0xae123000 >> mmap2(NULL, 1036288, ...) = 0xae026000 >> mmap2(NULL, 2068480, ...) = 0xade2d000 >> mmap2(NULL, 4132864, ...) = 0xada3c000 >> mmap2(NULL, 8261632, ...) = 0xad25b000 >> mmap2(NULL, 16519168, ...) = 0xac29a000 >> mmap2(NULL, 33034240, ...) = 0xaa319000 >> mmap2(NULL, 66064384, ...) = 0xa6418000 >> mmap2(NULL, 132124672, ...) = 0x9e617000 >> mmap2(NULL, 264245248, ...) = 0x8ea16000 >> mmap2(NULL, 528486400, ...) = 0x6f215000 >> mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) >> brk(0x494de000) = 0xa4de000 >> mmap2(NULL, 1057099776, ...) = -1 ENOMEM (Cannot allocate memory) >> mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) >> >> We can actually see that the allocated size is always doubled. >> >> Shotwell will keep running and consuming 100% CPU of one core (I'm >> glade to have two cores), and use almost all the RAM, but nothing >> seems to be progressing, no files seem to be read or written. >> >> I have tried to use an empty data directory, but it ends the same. The >> shotwell.log file contains only the following two lines: >> >> L 14195 2011-02-19 10:16:52 [MSG] main.vala:61: Verifying database ... >> L 14195 2011-02-19 10:16:53 [MSG] VideoSupport.vala:373: interpreter >> state cookie not found; assuming all video thumbnails are out of date >> >> Given this is the latest stable version, I'm reporting it here for now ;) >> >> Kind Regards >> -- >> Mike >> PS: my shotwell 0.6.1 won't start because it doesn't find libexiv2 >> anymore, and rebuilding it needs an older version of Vala, I have >> installed shotwell 0.8.1 from the ArchLinux package >> PPS: I'm the one who bugged you about this on twitter under @m8t >> > > From shimegi at gmail.com Sun Feb 20 10:55:45 2011 From: shimegi at gmail.com (Shimegi) Date: Sun, 20 Feb 2011 11:55:45 +0100 Subject: [Shotwell] tags improvments Message-ID: <4D60F331.9050608@gmail.com> Hi, First of all, thanks for shotwell and the work done. It rocks. I'm suggesting something probably already suggested : it's quite boring to tag a pictures "animal, bird, eagle", so it will be useful if we were able to organize tags, so when tagging "eagle", "animal" and "bird" would be automatically applied. Sorry for my bad english. Regards, Shimegi From sil at kryogenix.org Sun Feb 20 22:58:12 2011 From: sil at kryogenix.org (Stuart Langridge) Date: Sun, 20 Feb 2011 22:58:12 +0000 Subject: [Shotwell] Shotwell mounts camera and then asks to unmount it Message-ID: I'm having a weird shotwell + gvfs experience. When I plug in my camera, I trip over https://bugzilla.gnome.org/show_bug.cgi?id=642827 (gvfs mounts the camera twice and so conflicts with itself). If I carefully kill gvfs-gphoto2-volume-monitor first so that that doesn't happen, then shotwell shows the camera fine...but clicking on the camera in shotwell mounts it with gvfs (thus colliding again), and then shotwell tells me that it needs to unmount it to read the photos! So...shotwell mounts the camera, and then tells me to unmount it. This is...quite annoying. :) Is there anything I can do about it? Like...tell shotwell to not mount the camera in the first place? sil -- New Year's Day -- everything is in blossom! I feel about average. ?? -- Kobayashi Issa From adam at yorba.org Mon Feb 21 19:12:22 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 21 Feb 2011 11:12:22 -0800 Subject: [Shotwell] tags improvments In-Reply-To: <4D60F331.9050608@gmail.com> References: <4D60F331.9050608@gmail.com> Message-ID: <4D62B916.9010505@yorba.org> Shimegi, On 02/20/2011 02:55 AM, Shimegi wrote: > Hi, > > First of all, thanks for shotwell and the work done. It rocks. > > I'm suggesting something probably already suggested : it's quite > boring to tag a pictures "animal, bird, eagle", so it will be useful > if we were able to organize tags, so when tagging "eagle", "animal" > and "bird" would be automatically applied. > > Sorry for my bad english. I'm glad you like Shotwell. Your English is fine! :) We use the term "hierarchical tags" to describe the feature you're asking for. And yes, lots of users have asked for this: http://trac.yorba.org/ticket/1401 This won't make the upcoming 0.9 release, but is a high priority for 0.10 this summer. Cheers - adam From jim at yorba.org Mon Feb 21 19:13:43 2011 From: jim at yorba.org (Jim Nelson) Date: Mon, 21 Feb 2011 11:13:43 -0800 Subject: [Shotwell] shotwell error - database disk image is malformed In-Reply-To: <1297953600.6228.5.camel@dynatos> References: <1297953600.6228.5.camel@dynatos> Message-ID: I've looked into your problem and found one possible clue: http://www.mail-archive.com/sqlite-users at sqlite.org/msg58721.html The key here is that you're able to read from the database (SELECT, etc.) but when Shotwell goes to write it the problem occurs. It's difficult to tell without closer examination of the database. Could you send it to me? I could then take a closer look at the problem. -- Jim On Thu, Feb 17, 2011 at 6:40 AM, Nickolay S. Savchenko wrote: > Hi dear shotwell users and developers! > > I encountered the following problem with shotwell today. I was using > default shotwell version from ubuntu 10.10, it worked quite good. But > today shotwell crashed during photo import. I looked error > in .xsession-errors, it was following: > > ** ERROR **: DatabaseTables.vala:55: add_photo: [11] database disk image > is malformed > > I then run from gdb, here is the backtrace: > > Program received signal SIGABRT, Aborted. > 0x00007ffff0b6fba5 in raise () from /lib/libc.so.6 > (gdb) backtrace full > #0 0x00007ffff0b6fba5 in raise () from /lib/libc.so.6 > No symbol table info available. > #1 0x00007ffff0b736b0 in abort () from /lib/libc.so.6 > No symbol table info available. > #2 0x00007ffff1425f0a in g_logv () from /lib/libglib-2.0.so.0 > No symbol table info available. > #3 0x00007ffff1425fa3 in g_log () from /lib/libglib-2.0.so.0 > No symbol table info available. > #4 0x000000000046b4df in database_table_fatal () > No symbol table info available. > #5 0x000000000046f782 in photo_table_add () > No symbol table info available. > #6 0x00000000004d7510 in library_photo_import_create () > No symbol table info available. > #7 0x00000000004e9606 in ?? () > No symbol table info available. > #8 0x000000000055aa82 in ?? () > No symbol table info available. > #9 0x00007ffff141b342 in g_main_context_dispatch () > from /lib/libglib-2.0.so.0 > No symbol table info available. > #10 0x00007ffff141f2a8 in ?? () from /lib/libglib-2.0.so.0 > No symbol table info available. > #11 0x00007ffff141f7b5 in g_main_loop_run () from /lib/libglib-2.0.so.0 > No symbol table info available. > #12 0x00007ffff3ce33e7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 > No symbol table info available. > #13 0x0000000000455ead in library_exec () > No symbol table info available. > #14 0x0000000000456572 in _vala_main () > No symbol table info available. > #15 0x00000000004565f9 in main () > No symbol table info available. > (gdb) > > Then I tried to install shotwell 0.8.1 from ppa, and now it doesn't even > start. > > nss at dynatos:~/Music/lessons$ SHOTWELL_LOG=1 shotwell > > ** ERROR **: DatabaseTables.vala:57: VideoTable constructor: [11] > database disk image is malformed > aborting... > Aborted > > I tried to navigate through database using console sqlite3 tool, > database looks not damaged. I tried random select queries and they > worked. So it's quite strange that shotwell thinks that the database is > corrupt. I looked into faq and user guide and didn't find any > information about database repairing. > > Any ideas? > > > -- > best regards, > Nickolay Savchenko > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From mmassonnet at gmail.com Mon Feb 21 19:37:40 2011 From: mmassonnet at gmail.com (Mike Massonnet) Date: Mon, 21 Feb 2011 20:37:40 +0100 Subject: [Shotwell] Unable to start Shotwell 0.8.1 In-Reply-To: <4D629C6B.4080006@yorba.org> References: <4D629C6B.4080006@yorba.org> Message-ID: Hi Adam, Yes exactly, like reported in this previous post: http://lists.yorba.org/pipermail/shotwell/2011-February/001793.html http://trac.yorba.org/ticket/3021 Cheers Mike 2011/2/21 Adam Dingle : > Mike, > > not completely sure I understand your last email - can you confirm the > following? > > - When you start Shotwell when using the Aurora theme, Shotwell allocates > all available memory and uses 100% CPU. > - When you start Shotwell when using other themes, everything works fine. > > adam > > On 02/19/2011 01:41 AM, Mike Massonnet wrote: >> >> Why I was sure I wasn't using an Aurora theme... switching to another >> theme fixed the issue. >> >> Kind Regards >> Mike >> >> 2011/2/19 Mike Massonnet: >>> >>> Hello, >>> >>> I have seen a few posts on this list about Shotwell 0.8.1 not >>> starting, but I haven't found anything similar to what I'm facing. >>> >>> While Shotwell does start, it consumes more and more memory until it >>> reaches a point where new memory can't be allocated. I have run strace >>> on it, and in fact it shows the following result: >>> >>> mmap2(NULL, 262144, ...) = 0xae1a2000 >>> mmap2(NULL, 520192, ...) = 0xae123000 >>> mmap2(NULL, 1036288, ...) = 0xae026000 >>> mmap2(NULL, 2068480, ...) = 0xade2d000 >>> mmap2(NULL, 4132864, ...) = 0xada3c000 >>> mmap2(NULL, 8261632, ...) = 0xad25b000 >>> mmap2(NULL, 16519168, ...) = 0xac29a000 >>> mmap2(NULL, 33034240, ...) = 0xaa319000 >>> mmap2(NULL, 66064384, ...) = 0xa6418000 >>> mmap2(NULL, 132124672, ...) = 0x9e617000 >>> mmap2(NULL, 264245248, ...) = 0x8ea16000 >>> mmap2(NULL, 528486400, ...) = 0x6f215000 >>> mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) >>> brk(0x494de000) ? ? ? ? ? ? ? ? ? ? ? ? = 0xa4de000 >>> mmap2(NULL, 1057099776, ...) = -1 ENOMEM (Cannot allocate memory) >>> mmap2(NULL, 1056968704, ...) = -1 ENOMEM (Cannot allocate memory) >>> >>> We can actually see that the allocated size is always doubled. >>> >>> Shotwell will keep running and consuming 100% CPU of one core (I'm >>> glade to have two cores), and use almost all the RAM, but nothing >>> seems to be progressing, no files seem to be read or written. >>> >>> I have tried to use an empty data directory, but it ends the same. The >>> shotwell.log file contains only the following two lines: >>> >>> L 14195 2011-02-19 10:16:52 [MSG] main.vala:61: Verifying database ... >>> L 14195 2011-02-19 10:16:53 [MSG] VideoSupport.vala:373: interpreter >>> state cookie not found; assuming all video thumbnails are out of date >>> >>> Given this is the latest stable version, I'm reporting it here for now ;) >>> >>> Kind Regards >>> -- >>> Mike >>> PS: my shotwell 0.6.1 won't start because it doesn't find libexiv2 >>> anymore, and rebuilding it needs an older version of Vala, I have >>> installed shotwell 0.8.1 from the ArchLinux package >>> PPS: I'm the one who bugged you about this on twitter under @m8t >>> >> >> > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From adam at yorba.org Mon Feb 21 21:15:32 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 21 Feb 2011 13:15:32 -0800 Subject: [Shotwell] Reading exif data out of MTS In-Reply-To: References: <235716284.3896123.1298276755211.JavaMail.fmail@mwmweb075> <4D6286A3.4030503@yorba.org> Message-ID: <4D62D5F4.6060006@yorba.org> Vincent, On 02/21/2011 11:37 AM, Vincent wrote: > On Mon, Feb 21, 2011 at 4:37 PM, Adam Dingle > wrote: > > On 02/21/2011 12:25 AM, Ralf Butler wrote: > > Hi there, are there any plans to support reading exif data out > of an MTS file? So far I can import an MTS but it is not > assigned to any event. > > > Yes - we have a ticket for this: http://trac.yorba.org/ticket/3093 > > adam > > > I feel also vey concerned by this question as I planned to buy a new > camera and hesitated between Lumix LX5 (AVHCD/mts videos) and Canon > S95 (H264/mov videos). I wonder if I will be able to deals with > Shotwell the videos embeded by the Lumix camera... Do you have any > date (0.9 or 1.0) for AVHCD support in Shotwell??? Does it depends on > Shotwell or another library? Shotwell reads date/time metadata from video files by itself. We'd like to do that using GStreamer, but GStreamer can't handle all the necessary formats yet (including AVHCD/MTS). (See http://trac.yorba.org/ticket/2836 and the tickets it points to for more details.) Even once GStreamer is able to read the metadata we need, we still won't be able to use it until some time passes and new enough versions of GStreamer make it into the major distributions. So if we want to be able to read MTS date/times in the near future we need to implement that in Shotwell itself. I think it's too late to take this on for 0.9 since our feature freeze is this week. But I think we should implement this for 0.10 since a number of users have reported they are using this format. I've upped the priority on the associated ticket ( http://trac.yorba.org/ticket/3093 ) to high. adam From el.cameleon.1 at gmail.com Mon Feb 21 21:20:27 2011 From: el.cameleon.1 at gmail.com (Vincent) Date: Mon, 21 Feb 2011 22:20:27 +0100 Subject: [Shotwell] Reading exif data out of MTS In-Reply-To: <4D62D5F4.6060006@yorba.org> References: <235716284.3896123.1298276755211.JavaMail.fmail@mwmweb075> <4D6286A3.4030503@yorba.org> <4D62D5F4.6060006@yorba.org> Message-ID: Hi Adam, This is simply great, thanks. Wait impatiently for 0.10 as hierachical tag and (depending of my future camera choice) AVCHD support would be very important for me. From ralf.butler at web.de Mon Feb 21 21:53:20 2011 From: ralf.butler at web.de (Ralf Butler) Date: Mon, 21 Feb 2011 22:53:20 +0100 (CET) Subject: [Shotwell] Reading exif data out of MTS Message-ID: <618299505.4763195.1298325200555.JavaMail.fmail@mwmweb075> Hi Adam, Thank you very much for your quick reply. I'm not familiar with the status of GStreamer. So, currently it does not allow to read out exif data of an MTS file; even not the creation date? On the other hand, if it does I guess it would be a quick fix to read out the creation date at least (for 0.9) to assign imported MTS files to events. Thanks, Ralf > ?Vincent, > > On 02/21/2011 11:37 AM, Vincent wrote: > > On Mon, Feb 21, 2011 at 4:37 PM, Adam Dingle > > wrote: > > > > On 02/21/2011 12:25 AM, Ralf Butler wrote: > > > > Hi there, are there any plans to support reading exif data out > > of an MTS file? So far I can import an MTS but it is not > > assigned to any event. > > > > > > Yes - we have a ticket for this: http://trac.yorba.org/ticket/3093 > > > > adam > > > > > > I feel also vey concerned by this question as I planned to buy a new > > camera and hesitated between Lumix LX5 (AVHCD/mts videos) and Canon > > S95 (H264/mov videos). I wonder if I will be able to deals with > > Shotwell the videos embeded by the Lumix camera... Do you have any > > date (0.9 or 1.0) for AVHCD support in Shotwell??? Does it depends on > > Shotwell or another library? > > Shotwell reads date/time metadata from video files by itself. We'd like > to do that using GStreamer, but GStreamer can't handle all the necessary > formats yet (including AVHCD/MTS). (See > http://trac.yorba.org/ticket/2836 and the tickets it points to for more > details.) Even once GStreamer is able to read the metadata we need, we > still won't be able to use it until some time passes and new enough > versions of GStreamer make it into the major distributions. > > So if we want to be able to read MTS date/times in the near future we > need to implement that in Shotwell itself. I think it's too late to > take this on for 0.9 since our feature freeze is this week. But I think > we should implement this for 0.10 since a number of users have reported > they are using this format. I've upped the priority on the associated > ticket ( http://trac.yorba.org/ticket/3093 ) to high. > > adam > ___________________________________________________________ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.web.de From adam at yorba.org Mon Feb 21 22:32:15 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 21 Feb 2011 14:32:15 -0800 Subject: [Shotwell] Reading exif data out of MTS In-Reply-To: <618299505.4763195.1298325200555.JavaMail.fmail@mwmweb075> References: <618299505.4763195.1298325200555.JavaMail.fmail@mwmweb075> Message-ID: <4D62E7EF.2020806@yorba.org> On 02/21/2011 01:53 PM, Ralf Butler wrote: > Hi Adam, > > Thank you very much for your quick reply. I'm not familiar with the status of GStreamer. So, currently it does not allow to read out exif data of an MTS file; even not the creation date? That's right: GStreamer cannot read the creation date from a MTS file at this time. See https://bugzilla.gnome.org/show_bug.cgi?id=642911 adam > On the other hand, if it does I guess it would be a quick fix to read out the creation date at least (for 0.9) to assign imported MTS files to events. > > Thanks, > Ralf > > >> ?Vincent, >> >> On 02/21/2011 11:37 AM, Vincent wrote: >>> On Mon, Feb 21, 2011 at 4:37 PM, Adam Dingle>> > wrote: >>> >>> On 02/21/2011 12:25 AM, Ralf Butler wrote: >>> >>> Hi there, are there any plans to support reading exif data out >>> of an MTS file? So far I can import an MTS but it is not >>> assigned to any event. >>> >>> >>> Yes - we have a ticket for this: http://trac.yorba.org/ticket/3093 >>> >>> adam >>> >>> >>> I feel also vey concerned by this question as I planned to buy a new >>> camera and hesitated between Lumix LX5 (AVHCD/mts videos) and Canon >>> S95 (H264/mov videos). I wonder if I will be able to deals with >>> Shotwell the videos embeded by the Lumix camera... Do you have any >>> date (0.9 or 1.0) for AVHCD support in Shotwell??? Does it depends on >>> Shotwell or another library? >> Shotwell reads date/time metadata from video files by itself. We'd like >> to do that using GStreamer, but GStreamer can't handle all the necessary >> formats yet (including AVHCD/MTS). (See >> http://trac.yorba.org/ticket/2836 and the tickets it points to for more >> details.) Even once GStreamer is able to read the metadata we need, we >> still won't be able to use it until some time passes and new enough >> versions of GStreamer make it into the major distributions. >> >> So if we want to be able to read MTS date/times in the near future we >> need to implement that in Shotwell itself. I think it's too late to >> take this on for 0.9 since our feature freeze is this week. But I think >> we should implement this for 0.10 since a number of users have reported >> they are using this format. I've upped the priority on the associated >> ticket ( http://trac.yorba.org/ticket/3093 ) to high. >> >> adam > ___________________________________________________________ > Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.web.de > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Tue Feb 22 20:31:38 2011 From: jim at yorba.org (Jim Nelson) Date: Tue, 22 Feb 2011 12:31:38 -0800 Subject: [Shotwell] Shotwell mounts camera and then asks to unmount it In-Reply-To: References: Message-ID: This doesn't make any sense to me -- Shotwell never attempts to mount a camera, only unmount it. However, Shotwell does monitor for attached devices (via udev) to receive notifications of attached devices. Here's something to try: Reproduce the behavior as you've described. When you click on the camera in Shotwell and it's remounted, check to see if the gvfs-gphoto2-volume-monitor is running again. I'm wondering if it was re-launched when Shotwell probed the device chain. Great haiku by the way! Issa is my favorite: New Year's god-- once again I rely on your help -- Jim On Sun, Feb 20, 2011 at 2:58 PM, Stuart Langridge wrote: > I'm having a weird shotwell + gvfs experience. When I plug in my > camera, I trip over https://bugzilla.gnome.org/show_bug.cgi?id=642827 > (gvfs mounts the camera twice and so conflicts with itself). If I > carefully kill gvfs-gphoto2-volume-monitor first so that that doesn't > happen, then shotwell shows the camera fine...but clicking on the > camera in shotwell mounts it with gvfs (thus colliding again), and > then shotwell tells me that it needs to unmount it to read the photos! > > So...shotwell mounts the camera, and then tells me to unmount it. This > is...quite annoying. :) > > Is there anything I can do about it? Like...tell shotwell to not mount > the camera in the first place? > > sil > > -- > New Year's Day -- > everything is in blossom! > I feel about average. > -- Kobayashi Issa > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From foxy at on-the-hill.me.uk Sat Feb 26 22:47:58 2011 From: foxy at on-the-hill.me.uk (Foxy) Date: Sat, 26 Feb 2011 22:47:58 +0000 Subject: [Shotwell] Global tagging Message-ID: <4D69831E.6090103@on-the-hill.me.uk> Hi guys! I've got 2 accounts on my laptop: one is mine and another is my wife's. If I tag photos in Shotwell, the tags are not available on my wife's account. Is it possible to make the tags available on all accounts? Another thing. After importing photos, some of them ended up in No Event although they all have dates. Is it possible to move them in particular dates? From el.cameleon.1 at gmail.com Sun Feb 27 07:17:13 2011 From: el.cameleon.1 at gmail.com (Vincent) Date: Sun, 27 Feb 2011 08:17:13 +0100 Subject: [Shotwell] Global tagging In-Reply-To: <4D69831E.6090103@on-the-hill.me.uk> References: <4D69831E.6090103@on-the-hill.me.uk> Message-ID: On Sat, Feb 26, 2011 at 11:47 PM, Foxy wrote: > I've got 2 accounts on my laptop: one is mine and another is my wife's. If > I tag photos in Shotwell, the tags are not available on my wife's account. > Is it possible to make the tags available on all accounts? > For this point, I assume that you should simply store the tags into the photos (it is one of the new features of Shotwell 0.8) in order to make them available to all. This can be done by checking the right option in the menu "Edition", "Preferences". From foxy at on-the-hill.me.uk Sun Feb 27 19:02:02 2011 From: foxy at on-the-hill.me.uk (Foxy) Date: Sun, 27 Feb 2011 19:02:02 +0000 Subject: [Shotwell] Global tagging In-Reply-To: References: <4D69831E.6090103@on-the-hill.me.uk> Message-ID: <4D6A9FAA.1050708@on-the-hill.me.uk> On 27/02/11 07:17, Vincent wrote: > On Sat, Feb 26, 2011 at 11:47 PM, Foxy wrote: > >> I've got 2 accounts on my laptop: one is mine and another is my wife's. If >> I tag photos in Shotwell, the tags are not available on my wife's account. >> Is it possible to make the tags available on all accounts? >> > For this point, I assume that you should simply store the tags into the > photos (it is one of the new features of Shotwell 0.8) in order to make them > available to all. This can be done by checking the right option in the menu > "Edition", "Preferences". > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell Thanks a lot. I did not know about this function! From philsdutchie at gmail.com Sun Feb 27 13:45:18 2011 From: philsdutchie at gmail.com (philsdutchie) Date: Sun, 27 Feb 2011 05:45:18 -0800 (PST) Subject: [Shotwell] Event not shown Message-ID: <1298814317994-34259.post@talk.nabble.com> I tried to import my photo's from different directories in shotwell. I encountered a problem with photos in a subdirectory in a directory named 2007_03. Photo's under a subdirectory 2000309 are loaded, seen under photo's and there is an event made in Shotwell: - 2007 - March Fri Mar 9,2007 Photo's in the subdirectory 200303 however are loaded and seen under photo's but there is no event made. What is the problem here? I am using Shotwell 0.5.0 under Ubuntu (64) lucid. But the same problem appears in Shotwell 0.7.2. -- View this message in context: http://shotwell.3510.www.nabble.com/Event-not-shown-tp34259p34259.html Sent from the Shotwell mailing list archive at Nabble.com. From mharris312 at gmail.com Sun Feb 27 23:36:07 2011 From: mharris312 at gmail.com (Matthew S. Harris) Date: Sun, 27 Feb 2011 15:36:07 -0800 Subject: [Shotwell] How best to use with Bibble? Message-ID: Maybe I'm looking to better learn how to use the tools I have, or maybe I'm making a Shotwell feature request. I'm not sure. I'm trying to use Shotwell with Bibble. I love Shotwell's speed for navigating my photos. I can tell that a lot of work went into optimizing the checkerboard display. I'm willing to wait for hierarchical tags and other promising features. But Shotwell is not a sophisticated editor. I could be perfectly happy with it managing my photos if it interacted well with external editors. I don't know how other raw editors work, but to "edit" a file with Bibble, Bibble just writes an .xmp file that sits next to the raw file. There's no JPEG involved at all. I would love it if after editing a file externally, Shotwell could recognize the updated .xmp file and call Bibble to rerender the thumbnail and mimic. I don't know how other raw editors do it, so I hope I'm not asking for a lot of special case logic for Bibble. Maybe there's a way to do it with plugins. Since I have a paid copy of Bibble, I'm willing to do tests for you if necessary. Matthew From adam at yorba.org Mon Feb 28 22:18:25 2011 From: adam at yorba.org (Adam Dingle) Date: Mon, 28 Feb 2011 14:18:25 -0800 Subject: [Shotwell] How best to use with Bibble? In-Reply-To: References: Message-ID: <4D6C1F31.60701@yorba.org> Matthew, thanks for your comments. Sadly, interaction with external RAW editors is an area of weakness for Shotwell at this time, and I don't know of any way to improve your workflow with Shotwell and Bibble today. If you could convince Bibble to write out a JPEG every time you saved then you could import that into Shotwell (either manually or via auto-import), but it currently would appear as a separate image. We'd like to improve this interaction so that with popular RAW editors you'll be able to save and have your changes show up in Shotwell automatically, though I think we might need to special case various RAW editors because I'm not aware of any standard way to make this work for all such programs (though I'd like to investigate this more). We have a ticket tracking this here: http://trac.yorba.org/ticket/3061 In the longer term, we'd like to add more advanced RAW capabilities to Shotwell so you won't even need to use an external RAW editor at all. :) But that probably won't happen for a while. adam On 02/27/2011 03:36 PM, Matthew S. Harris wrote: > Maybe I'm looking to better learn how to use the tools I have, or > maybe I'm making a Shotwell feature request. I'm not sure. > > I'm trying to use Shotwell with Bibble. I love Shotwell's speed for > navigating my photos. I can tell that a lot of work went into > optimizing the checkerboard display. I'm willing to wait for > hierarchical tags and other promising features. But Shotwell is not a > sophisticated editor. I could be perfectly happy with it managing my > photos if it interacted well with external editors. > > I don't know how other raw editors work, but to "edit" a file with > Bibble, Bibble just writes an .xmp file that sits next to the raw > file. There's no JPEG involved at all. I would love it if after > editing a file externally, Shotwell could recognize the updated .xmp > file and call Bibble to rerender the thumbnail and mimic. > > I don't know how other raw editors do it, so I hope I'm not asking for > a lot of special case logic for Bibble. Maybe there's a way to do it > with plugins. > > Since I have a paid copy of Bibble, I'm willing to do tests for you if > necessary. > > > Matthew > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell