From lfu.project at gmail.com Sun Jan 3 21:15:29 2010 From: lfu.project at gmail.com (LFU Project Team) Date: Sun, 3 Jan 2010 23:15:29 +0200 Subject: [Shotwell] Bulgarian translation of Shotwell Message-ID: <6992f8d71001031315j7f3d4dbfk96e250c08e3ce848@mail.gmail.com> Hello, I've made a Bulgarian translation of Shotwell. It's based on version 0.4.1, and it's completed at 99%. Both PO and MO files are in the attached TAR.GZ file. Regards, Svetoslav -- http://learnfree.eu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bg.tar.gz Type: application/x-gzip Size: 21295 bytes Desc: not available URL: From iluetkeb at techfak.uni-bielefeld.de Mon Jan 4 14:28:49 2010 From: iluetkeb at techfak.uni-bielefeld.de (=?ISO-8859-1?Q?Ingo_L=FCtkebohle?=) Date: Mon, 04 Jan 2010 15:28:49 +0100 Subject: [Shotwell] interesting approach? In-Reply-To: References: <20091228192905.0d32fcd0@noname> Message-ID: <4B41FB21.6090208@techfak.uni-bielefeld.de> >> http://git.savannah.gnu.org/cgit/solang.git/commit/?h=tracker&id=f93aca51902d555331ede95d92aac7f1c4353cd2 >> >> Sounds like an interesting approach to me. I'm usually totally in favor of re-use but Tracker has been one of the most annoying pieces of software for me. I regularly have to kill it, because it keeps hogging the CPU. That may be just me, or my system (Ubuntu Karmic) of course, but I wonder what solangs experience is with this approach. The change /is/ fairly recent. cheers, Ingo From jim at yorba.org Mon Jan 4 18:40:15 2010 From: jim at yorba.org (Jim Nelson) Date: Mon, 4 Jan 2010 10:40:15 -0800 Subject: [Shotwell] Shared photo library and database In-Reply-To: <9421dc6f0912311354j7228edd7v81e69abf0154504@mail.gmail.com> References: <9421dc6f0912311354j7228edd7v81e69abf0154504@mail.gmail.com> Message-ID: Hi Todd, What you're trying to do is not supported by Shotwell -- the current design relies on a single process accessing the data files in ~/.shotwell. Sharing this directory between multiple instances of Shotwell is not recommended (and, in fact, will result in data loss at some point). For now, I can't offer an easy solution to this problem. Note, however, that multiple users can have their own Shotwell libraries pointing to the same set of photos (because Shotwell's editing system is non-destructive). If you press Ctrl+Shift when dropping the photos onto the Shotwell window or deselect "Copy files to Pictures photo library" from File -> Import From Folder ..., the photos won't be copied but linked by the Shotwell library, saving disk space. I hope this helps, -- Jim On Thu, Dec 31, 2009 at 1:54 PM, Todd Slater wrote: > Hi, > > I just tried Shotwell for the first time today and I like it! I like to set > up one photo directory and database to share with my family. I'm trying to > figure out the best way to do this on a linux box. > > I noticed that Shotwell creates its own ~/.shotwell directory with relevant > files. I went to my wife's directory and just made a symlink to my > ~/.shotwell, which I added to a group we share. As far as I can tell, this > works. However, the first time I did it I was in the process of importing > pictures and I believe it caused Shotwell to crash as none of the pictures > had and "events" associated with them when I relaunched it. > > Anyway, is there a "preferred" or "safer" way to share a single library and > database? > > Thanks and happy New Year! > > Todd > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at yorba.org Tue Jan 5 00:42:43 2010 From: jim at yorba.org (Jim Nelson) Date: Mon, 4 Jan 2010 16:42:43 -0800 Subject: [Shotwell] Shotwell 0.4.2 - a digital photo organizer for the GNOME desktop Message-ID: Yorba has released Shotwell 0.4.2, an update to our digital photo organizer. This release adds new translations, corrects a crash when deleting photos from a camera, and fixes the Windows installer. It is highly recommended that all users upgrade. Download the source from the Shotwell home page at http://www.yorba.org/shotwell/ Ubuntu binaries for karmic and lucid are available at Yorba's PPA: https://launchpad.net/~yorba/+archive/ppa -- Jim Nelson Shotwell home page: http://www.yorba.org/shotwell/ Shotwell wiki: http://trac.yorba.org/wiki/Shotwell -------------- next part -------------- An HTML attachment was scrubbed... URL: From lfu.project at gmail.com Tue Jan 5 06:49:48 2010 From: lfu.project at gmail.com (LFU Project Team) Date: Tue, 5 Jan 2010 08:49:48 +0200 Subject: [Shotwell] Direct editing of PNG files? Message-ID: <6992f8d71001042249m61e01831rdc3503b5501882f0@mail.gmail.com> Is it possible to open and edit PNG files directly with Shotwell Photo Viewer, without import them into library? Currently Shotwell gives me an error message, saying that PNG is not supported format. Opening and editing of JPEG is working file. -- http://learnfree.eu -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidj at gmail.com Tue Jan 5 17:52:30 2010 From: davidj at gmail.com (David Jeske) Date: Tue, 5 Jan 2010 09:52:30 -0800 Subject: [Shotwell] Shotwell 0.4.2 windows very slow at importing Message-ID: <7a63d2e71001050952h3fafec8ei24f11d72c83c956d@mail.gmail.com> Does shotwell 0.4.2 windows build import very very slowly for others? Mine has been running for 30 minutes and if the box in the lower right is a progress bar, looks to be less than 5% done. The photos are flipping by in the importer at a glacial pace. Is this possibly a debug build? On Mon, Jan 4, 2010 at 4:42 PM, Jim Nelson wrote: > >> Yorba has released Shotwell 0.4.2, an update to our digital photo >> organizer. This release adds new translations, corrects a crash when >> deleting photos from a camera, and fixes the Windows installer. >> >> It is highly recommended that all users upgrade. >> >> Download the source from the Shotwell home page at >> http://www.yorba.org/shotwell/ >> >> Ubuntu binaries for karmic and lucid are available at Yorba's PPA: >> https://launchpad.net/~yorba/+archive/ppa >> >> -- Jim Nelson >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidj at gmail.com Tue Jan 5 18:02:31 2010 From: davidj at gmail.com (David Jeske) Date: Tue, 5 Jan 2010 10:02:31 -0800 Subject: [Shotwell] Shotwell 0.4.2 windows very slow at importing In-Reply-To: <7a63d2e71001050952h3fafec8ei24f11d72c83c956d@mail.gmail.com> References: <7a63d2e71001050952h3fafec8ei24f11d72c83c956d@mail.gmail.com> Message-ID: <7a63d2e71001051002v6811cafvd044a9ed97e40ff1@mail.gmail.com> On Tue, Jan 5, 2010 at 9:52 AM, David Jeske wrote: > Does shotwell 0.4.2 windows build import very very slowly for others? Mine > has been running for 30 minutes and if the box in the lower right is a > progress bar, looks to be less than 5% done. The photos are flipping by in > the importer at a glacial pace. Is this possibly a debug build? > Additionally.. rather than let it finish, I clicked "stop" at the bottom and received an error dialog... ** ERROR **: DatabaseTables.vala:33: execute_update_by_id: [14] unable to open database file; aborting... -------------- next part -------------- An HTML attachment was scrubbed... URL: From adam at yorba.org Tue Jan 5 18:29:40 2010 From: adam at yorba.org (Adam Dingle) Date: Tue, 05 Jan 2010 10:29:40 -0800 Subject: [Shotwell] Direct editing of PNG files? In-Reply-To: <6992f8d71001042249m61e01831rdc3503b5501882f0@mail.gmail.com> References: <6992f8d71001042249m61e01831rdc3503b5501882f0@mail.gmail.com> Message-ID: <4B438514.7090607@yorba.org> An HTML attachment was scrubbed... URL: From adam at yorba.org Wed Jan 6 18:09:03 2010 From: adam at yorba.org (Adam Dingle) Date: Wed, 06 Jan 2010 10:09:03 -0800 Subject: [Shotwell] Shotwell 0.4.2 windows very slow at importing In-Reply-To: <7a63d2e71001050952h3fafec8ei24f11d72c83c956d@mail.gmail.com> References: <7a63d2e71001050952h3fafec8ei24f11d72c83c956d@mail.gmail.com> Message-ID: <4B44D1BF.2000505@yorba.org> An HTML attachment was scrubbed... URL: From jim at yorba.org Thu Jan 7 22:31:11 2010 From: jim at yorba.org (Jim Nelson) Date: Thu, 7 Jan 2010 14:31:11 -0800 Subject: [Shotwell] Call for testing Message-ID: Hello, First, I want to thank everyone out there who put in the time last month to test Shotwell. All those reports *really* paid off in terms of working out corner cases and squashing some serious bugs. We can use your help again. We've noticed under Ubuntu 9.10 (Karmic) that Shotwell is having trouble unmounting cameras. It reports a failure to unmount although the camera was indeed unmounted. Shotwell then winds up in a bad state. The only recourse is to close Shotwell and restart it, and things work fine thereafter. I committed to the 0.4 branch a fix for this. However, it could use more testing, as it involves a problem that is hardware-dependent and timing-sensitive. We didn't see this in the past, and there's concern about different results under different versions of GTK. If you have a chance to test this and let us know how it goes, it would be greatly appreciated. To get the latest 0.4 use the following command: svn co svn://svn.yorba.org/shotwell/branches/shotwell-0.4 This requires Vala 0.7.9 to compile, which is available at http://live.gnome.org/Vala Thanks! -- Jim Nelson -------------- next part -------------- An HTML attachment was scrubbed... URL: From iluetkeb at techfak.uni-bielefeld.de Sat Jan 9 13:01:01 2010 From: iluetkeb at techfak.uni-bielefeld.de (=?ISO-8859-15?Q?Ingo_L=FCtkebohle?=) Date: Sat, 09 Jan 2010 14:01:01 +0100 Subject: [Shotwell] re-read metadata? Message-ID: <4B487E0D.8050508@techfak.uni-bielefeld.de> Hi, is there a way to make Shotwell re-read metadata from EXIF, without removing and re-adding the photos? The reason I'm asking is because I left my camera in summer-time mode and hence had to shift a number of photos timestamp by one hour. Shotwell, however, still displays the previous timestamp. btw, on a positive note: when I make changes to the photo, the /new/ metadata gets kept, as desired. Very nice attention to detail, I wouldn't have expected that. Best Regards, Ingo From iluetkeb at techfak.uni-bielefeld.de Sat Jan 9 13:34:05 2010 From: iluetkeb at techfak.uni-bielefeld.de (=?ISO-8859-1?Q?Ingo_L=FCtkebohle?=) Date: Sat, 09 Jan 2010 14:34:05 +0100 Subject: [Shotwell] Call for testing In-Reply-To: References: Message-ID: <4B4885CD.6080800@techfak.uni-bielefeld.de> Am 07.01.2010 23:31, schrieb Jim Nelson: > If you have a chance to test this and let us know how it goes, it would be > greatly appreciated. I just checked this out and have mostly good but still mixed results. I compiled the 0.4 branch and started shotwell from there. This is what happened: A Panasonic TZ7 was recognized and the import started, without an "unmount necessary" message. It spent a while in the "retrieving photo information" stage, but otherwise, the retrieval went well. The lag in that stage seems to be either a deficiency in the PTP implementation of the camera or in gphoto2 (which reports it as an FZ20, too). Nothing serious there. A Nikon D90, on first try (directly after the above try) gave an "unspecified error -1" when I switched the camera on. Switching the camera off, then on again, gave me an "unmount necessary" message, which I confirmed and afer that, import was fine. On the third try, it worked without the "unmount required" message, just the progress bar said "unmounting". I repeated this sequence (first the Panasonic, then the Nikon), and then the Nikon worked without issues, right the first time. So, apart from the strange "unspecified error", which only occured in one try, it seems that everything works fine! cheers, Ingo From iluetkeb at techfak.uni-bielefeld.de Sat Jan 9 17:38:06 2010 From: iluetkeb at techfak.uni-bielefeld.de (=?ISO-8859-15?Q?Ingo_L=FCtkebohle?=) Date: Sat, 09 Jan 2010 18:38:06 +0100 Subject: [Shotwell] photo sorter ideas Message-ID: <4B48BEFE.5040207@techfak.uni-bielefeld.de> Hi, I do not know whether you guys already have ideas for a photo sorter, but for me this is one the most important tasks when coming back from a shoot and I have a few ideas that I just wanted to throw out for some feedback. My basic view is that sorting photos when coming back from a shoot is a task that is distinctly different from everyday work with my library. Most importantly, import time is when I delete the photos that are obvious rejects. I do this both for space economy and to reduce the large number of photos that are not keepers. To do this, I usually first look at photo in high resolution, as many technical defects are often not visible otherwise -- for example, slight shake is usually not visibly from thumbnails. I do this first because (unwanted) technical defects are a fairly uncontroversial reason for throwing out an image, whereas choices based on other factors are often be harder to make. Also, I often compare several shots of the same object, to pick the best one(s). Last, but not least, I check for "pop-outs" and the reverse, i.e. which of the photos strike me as good and not. I can usually do this fairly quickly, but Shotwell's current way of asking for confirmation after every delete is really cumbersome and something else, which is still safe, would be great (see below for an idea). Sorting is an incremental task -- I go through photos one at a time, cull those that are immediate rejects, go back and forth between alternatives and mark those that could pass or not. Having explained this, my suggestions are two things: 1) Provide a "sort view" which displays a batch of photos (for example, one event) in full resolution. Provide keyboard shortcuts or icons that sort photos into three categories: a) obvious keepers, b) obvious rejects, c) maybes. For maximum efficiency, no questions should be asked and after a selection has been made, the sorter should advance to the next image, but provide an "undo" shortcut that goes back one image and undoes the selection for that one. After completion, the obvious rejects should be removed at once and the object keepers kept. The "maybes" may warrant a further iteration or could also be kept, at the user's discretion. 2) Provide a comparison view which displays a batch of photos of the same object. This could either be based on user-selection or based on image & time similarity (I don't know whether its possible here, but in video processing, often very simple things such as the euclidean distance can already provide usable frame differencing. This can often be done on vastly reduced scale images, for faster comparison, at almost no cost in discriminatory power). A general comparison view is difficult. Many things could be the object of comparison. One use case could be that several photos are ok but one of them has better exposure. A bunch of histograms, shown all together with their respective photos at thumbnail size, could help with the decision in this case. If high resolution is needed to compare, one could get multiple high resolution views by selecting a region of interest, with the same region being shown from each image, in high resolution. Well, I hope you can use some of those ideas, at least generally ;-) Let me know if you need more detail. I'm also interested what others think of this?! Best Regards, Ingo From adam at yorba.org Mon Jan 11 17:57:56 2010 From: adam at yorba.org (Adam Dingle) Date: Mon, 11 Jan 2010 09:57:56 -0800 Subject: [Shotwell] re-read metadata? In-Reply-To: <4B487E0D.8050508@techfak.uni-bielefeld.de> References: <4B487E0D.8050508@techfak.uni-bielefeld.de> Message-ID: <4B4B66A4.5080801@yorba.org> Ingo, > is there a way to make Shotwell re-read metadata from EXIF, without > removing and re-adding the photos? Not at this time. > The reason I'm asking is because I left my camera in summer-time mode > and hence had to shift a number of photos timestamp by one hour. > Shotwell, however, still displays the previous timestamp. For 0.5 we're adding a Shotwell feature that lets the user adjust photos' timestamps. We've already implemented this in trunk, though at the moment Shotwell only updates its internal database, not the EXIF data in the photos. Soon, we'll improve this so that the EXIF dates get updated as well. cheers adam Ingo L?tkebohle wrote: > Hi, > > is there a way to make Shotwell re-read metadata from EXIF, without > removing and re-adding the photos? > > The reason I'm asking is because I left my camera in summer-time mode > and hence had to shift a number of photos timestamp by one hour. > Shotwell, however, still displays the previous timestamp. > > btw, on a positive note: when I make changes to the photo, the /new/ > metadata gets kept, as desired. Very nice attention to detail, I > wouldn't have expected that. > > Best Regards, > Ingo > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > From jim at yorba.org Mon Jan 11 18:18:21 2010 From: jim at yorba.org (Jim Nelson) Date: Mon, 11 Jan 2010 10:18:21 -0800 Subject: [Shotwell] Call for testing In-Reply-To: <4B4885CD.6080800@techfak.uni-bielefeld.de> References: <4B4885CD.6080800@techfak.uni-bielefeld.de> Message-ID: Thanks, Ingo. Unfortunately gPhoto's -1 error is a generic code, which means anything could've happened (although it does originate from the port layer, i.e. USB). Much thanks for testing this out and letting us know what you found. Cheers, -- Jim Nelson On Sat, Jan 9, 2010 at 5:34 AM, Ingo L?tkebohle < iluetkeb at techfak.uni-bielefeld.de> wrote: > Am 07.01.2010 23:31, schrieb Jim Nelson: > > If you have a chance to test this and let us know how it goes, it would > be > > greatly appreciated. > > I just checked this out and have mostly good but still mixed results. I > compiled the 0.4 branch and started shotwell from there. This is what > happened: > > A Panasonic TZ7 was recognized and the import started, without an > "unmount necessary" message. It spent a while in the "retrieving photo > information" stage, but otherwise, the retrieval went well. The lag in > that stage seems to be either a deficiency in the PTP implementation of > the camera or in gphoto2 (which reports it as an FZ20, too). Nothing > serious there. > > A Nikon D90, on first try (directly after the above try) gave an > "unspecified error -1" when I switched the camera on. > > Switching the camera off, then on again, gave me an "unmount necessary" > message, which I confirmed and afer that, import was fine. On the third > try, it worked without the "unmount required" message, just the progress > bar said "unmounting". > > I repeated this sequence (first the Panasonic, then the Nikon), and then > the Nikon worked without issues, right the first time. > > So, apart from the strange "unspecified error", which only occured in > one try, it seems that everything works fine! > > cheers, > Ingo > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -------------- next part -------------- An HTML attachment was scrubbed... URL: From caccolangrifata at gmail.com Thu Jan 14 14:29:07 2010 From: caccolangrifata at gmail.com (caccolangrifata) Date: Thu, 14 Jan 2010 15:29:07 +0100 Subject: [Shotwell] it.po update Message-ID: <1263479347.3106.6.camel@mind> Hi everybody! in the attach you can find it.po.patch. Diff file for some string "fix". Cheers! -- caccolangrifata -------------- next part -------------- A non-text attachment was scrubbed... Name: it.po.patch Type: text/x-patch Size: 3224 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Questa ? una parte del messaggio firmata digitalmente URL: From matthias.clasen at gmail.com Thu Jan 14 21:59:36 2010 From: matthias.clasen at gmail.com (Matthias Clasen) Date: Thu, 14 Jan 2010 16:59:36 -0500 Subject: [Shotwell] shotwell 0.4.2 in F12 Message-ID: Hey, just a quick note: I've just built 0.4.2 as an update for Fedora 12. It should appear in the updates-testing repository today or tomorrow, and make it out to stable updates within a week or so. Matthias From jim at yorba.org Thu Jan 14 22:13:02 2010 From: jim at yorba.org (Jim Nelson) Date: Thu, 14 Jan 2010 14:13:02 -0800 Subject: [Shotwell] shotwell 0.4.2 in F12 In-Reply-To: References: Message-ID: Hi Matthias, That's great news! We really appreciate your continuing efforts to make Shotwell available to Fedora users. One thing: We're about to release 0.4.3 (as in tomorrow or Monday). The primary update in 0.4.3 is to fix an annoying problem when trying to unmount a camera (in order to import photos from it). I don't know if 0.4.2 is out-the-door or in the works, but if it's feasible, waiting for 0.4.3 (I think) would be worth it. If not, 0.4.2 is still a solid update to 0.3.2. Cheers, -- Jim On Thu, Jan 14, 2010 at 1:59 PM, Matthias Clasen wrote: > Hey, just a quick note: > > I've just built 0.4.2 as an update for Fedora 12. It should appear in > the updates-testing repository today or tomorrow, and make it out to > stable updates within a week or so. > > > Matthias > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthias.clasen at gmail.com Thu Jan 14 22:26:58 2010 From: matthias.clasen at gmail.com (Matthias Clasen) Date: Thu, 14 Jan 2010 17:26:58 -0500 Subject: [Shotwell] shotwell 0.4.2 in F12 In-Reply-To: References: Message-ID: On Thu, Jan 14, 2010 at 5:13 PM, Jim Nelson wrote: > Hi Matthias, > > That's great news!? We really appreciate your continuing efforts to make > Shotwell available to Fedora users. > > One thing: We're about to release 0.4.3 (as in tomorrow or Monday).? The > primary update in 0.4.3 is to fix an annoying problem when trying to unmount > a camera (in order to import photos from it).? I don't know if 0.4.2 is > out-the-door or in the works, but if it's feasible, waiting for 0.4.3 (I > think) would be worth it.? If not, 0.4.2 is still a solid update to 0.3.2. I'll just replace the update by 0.4.3 before pushing it out to stable in that case. Thanks for the headsup. From jim at yorba.org Mon Jan 18 23:35:39 2010 From: jim at yorba.org (Jim Nelson) Date: Mon, 18 Jan 2010 15:35:39 -0800 Subject: [Shotwell] Shotwell 0.4.3 - a digital photo organizer for the GNOME desktop Message-ID: We're pleased to announce the release of Shotwell 0.4.3, Yorba's digital photo organizer for the GNOME desktop. This release includes updated Italian and French translations, a fixed theming on Windows, and better handling of unmounting an attached camera prior to import. It's recommended that all users upgrade. Download the source from the Shotwell home page at http://www.yorba.org/shotwell/ Ubuntu binaries for karmic and lucid are available at Yorba's PPA: https://launchpad.net/~yorba/+archive/ppa -- Jim Nelson Shotwell home page: http://www.yorba.org/shotwell/ Shotwell wiki: http://trac.yorba.org/wiki/Shotwell -------------- next part -------------- An HTML attachment was scrubbed... URL: From kaj-ivar at vanderwijst.com Sun Jan 24 17:46:45 2010 From: kaj-ivar at vanderwijst.com (Kaj-Ivar van der Wijst) Date: Sun, 24 Jan 2010 18:46:45 +0100 Subject: [Shotwell] Dutch translation Message-ID: <4B5C8785.9080208@vanderwijst.com> Good evening everyone! This is just a quick email to say I submitted the dutch translation. I hope it is alright. Poedit said it was 100% completed, so it should do it. This is my very first translation, so if I forgot to do something, don't hesitate to say it. I also added the .po file in this email. Thanks for the development of this great application! I love it and recommend it to every Linux user I know. Best regards, Kaj-Ivar van der Wijst -------------- next part -------------- A non-text attachment was scrubbed... Name: nl.po Type: text/x-gettext-translation Size: 47323 bytes Desc: not available URL: From pnovak at alumni.caltech.edu Sun Jan 24 20:23:05 2010 From: pnovak at alumni.caltech.edu (Paul Novak) Date: Sun, 24 Jan 2010 12:23:05 -0800 Subject: [Shotwell] Build errors Message-ID: <4B5CAC29.7070506@alumni.caltech.edu> Hello, I am trying to build shotwell from SVN, and failing. I am running Fedora, so I first installed the following packages from the Fedora 12 repo: dbus-glib-devel GConf2-devel gtk2-devel libexif-devel libgphoto2-devel libsoup-devel libxml2-devel sqlite-devel unique-devel webkitgtk-devel I then installed libgudev1-devel from Fedora Rawhide, to get a sufficiently recent version. I downloaded the source of shotwell from SVN, vala from git at git://git.gnome.org/vala, and libgee from git://git.gnome.org/libgee. I built vala first, then libgee, then tried to build shotwell, but failed with the following errors: src/main.vala src/AppWindow.vala src/CollectionPage.vala src/Thumbnail.vala src/DatabaseTables.vala src/ThumbnailCache.vala src/image_util.vala src/CheckerboardLayout.vala src/PhotoPage.vala src/Exif.vala src/Page.vala src/ImportPage.vala src/GPhoto.vala src/SortedList.vala src/EventsDirectoryPage.vala src/Dimensions.vala src/Box.vala src/Photo.vala src/Orientation.vala src/util.vala src/BatchImport.vala src/Dialogs.vala src/Resources.vala src/Debug.vala src/Sidebar.vala src/ColorTransformation.vala src/EditingTools.vala src/DataObject.vala src/DataCollection.vala src/LibraryWindow.vala src/CameraTable.vala src/DirectWindow.vala src/Properties.vala src/CustomComponents.vala src/Config.vala src/Event.vala src/International.vala src/Workers.vala src/system.vala src/AppDirs.vala src/PixbufCache.vala src/WebConnectors.vala src/FacebookConnector.vala src/CommandManager.vala src/Commands.vala src/SlideshowPage.vala src/LibraryFiles.vala src/FlickrConnector.vala src/Printing.vala glib-2.0.vapi:1010.9-1010.21: error: Assignment: Cannot convert from `string*' to `char*' char* dest = result; ^^^^^^^^^^^^^ glib-2.0.vapi:1012.21-1012.24: error: The name `dest' does not exist in the context of `string.splice' GLib.Memory.copy (dest, this, (char*) start_string - (char*) this); ^^^^ glib-2.0.vapi:1013.3-1013.6: error: The name `dest' does not exist in the context of `string.splice' dest += (char*) start_string - (char*) this; ^^^^ glib-2.0.vapi:1015.21-1015.24: error: The name `dest' does not exist in the context of `string.splice' GLib.Memory.copy (dest, str, str_size); ^^^^ glib-2.0.vapi:1016.3-1016.6: error: The name `dest' does not exist in the context of `string.splice' dest += str_size; ^^^^ glib-2.0.vapi:1018.21-1018.24: error: The name `dest' does not exist in the context of `string.splice' GLib.Memory.copy (dest, end_string, end_string.size ()); ^^^^ Compilation failed: 6 error(s), 0 warning(s) Do you have any suggestions on how to fix this error so I can build shotwell? I also tried to use vala and libgee from Rawhide, but when I did so, shotwell failed with a runtime error of "Illegal instruction". And when I try the debug build (./configure --debug) it works. Go figure. Also, could the instructions on installing shotwell, at http://trac.yorba.org/wiki/ShotwellInstallation, be corrected to reflect that hal (0.5.11) is deprecated but that gudev is needed to build shotwell, and that vala and libgee from Rawhide are recent enough to build shotwell? Thanks, Paul From pablo.martin-gomez at laposte.net Mon Jan 25 16:02:03 2010 From: pablo.martin-gomez at laposte.net (Pablo Martin-Gomez) Date: Mon, 25 Jan 2010 17:02:03 +0100 Subject: [Shotwell] About translating Shotwell Message-ID: <20100125170203.33a66abe@laposte.net> Hi all, I'm currently updating the French translation of Shotwell and some strings are surprising. >#: src/FlickrConnector.vala:369 >msgid "Your free Flickr account limits how much data you can " Huh, does this string have been accidentaly cut down ? >#: src/Dialogs.vala:787 >#, c-format >msgid "" >"Exposure time will be shifted %s by\n" >"%d %s, %d %s, %d %s, and %d %s." Sorry, but I'm not a clairvoyant. How could I know what each of this macros stand for ? (By the way, I don't understand the mining of the first %s) >#: src/Dialogs.vala:788 >#, c-format >msgid "forward" Okay, but what about the context ? In french, we can translate in 3 different ways. So please, gettext provides a wonderful feature called "context", use it, the translators will be thankful. Best regards, Pablo From lucas at yorba.org Mon Jan 25 21:07:17 2010 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 25 Jan 2010 13:07:17 -0800 Subject: [Shotwell] Build errors In-Reply-To: <4B5CAC29.7070506@alumni.caltech.edu> References: <4B5CAC29.7070506@alumni.caltech.edu> Message-ID: <992b763d1001251307j6671640ayc3a0d6d9c77e3ab6@mail.gmail.com> Hi Paul, First of all, we appreciate your making us aware of a build issue on Fedora 12. The diagnostic information you provided was helpful. One further question though: when you used git to fetch the vala and libgee sources from gnome.org, did you pull the source from trunk or did you pull it from a stable release branch? In general, Gnome sources pulled from trunk are under active development and may be unstable. One thing you might want to try is rebuilding and reinstalling vala and libgee from stable release tarballs, accessible through the following links: Vala: http://live.gnome.org/Vala/Release Libgee: http://live.gnome.org/Libgee/Release Once again, thanks for giving us the heads up. Best regards, Lucas From roman.yepishev at yandex.ua Mon Jan 25 21:17:26 2010 From: roman.yepishev at yandex.ua (Roman Yepishev) Date: Mon, 25 Jan 2010 23:17:26 +0200 Subject: [Shotwell] Build errors In-Reply-To: <4B5CAC29.7070506@alumni.caltech.edu> References: <4B5CAC29.7070506@alumni.caltech.edu> Message-ID: <1264454246.3891.67.camel@buzz.west.homenet.org> On Sun, 2010-01-24 at 12:23 -0800, Paul Novak wrote: > > Also, could the instructions on installing shotwell, at > http://trac.yorba.org/wiki/ShotwellInstallation, be corrected to reflect > that hal (0.5.11) is deprecated but that gudev is needed to build > shotwell, and that vala and libgee from Rawhide are recent enough to > build shotwell? > Make sure that vala compiler reads the vapi directory supplied with shotwell. I was having some build issues as well, since it reads standard vapi directory by default only. I had to supply additional --vapidir to shotwell makefile. -- Roman Yepishev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From jim at yorba.org Tue Jan 26 02:34:47 2010 From: jim at yorba.org (Jim Nelson) Date: Mon, 25 Jan 2010 18:34:47 -0800 Subject: [Shotwell] Dutch translation In-Reply-To: <4B5C8785.9080208@vanderwijst.com> References: <4B5C8785.9080208@vanderwijst.com> Message-ID: Thanks, Kaj-Ivar! We sincerely appreciate all the support our translators are offering. Cheers, -- Jim Nelson 2010/1/24 Kaj-Ivar van der Wijst > Good evening everyone! > > This is just a quick email to say I submitted the dutch translation. I hope > it is alright. Poedit said it was 100% completed, so it should do it. > > This is my very first translation, so if I forgot to do something, don't > hesitate to say it. I also added the .po file in this email. > > Thanks for the development of this great application! I love it and > recommend it to every Linux user I know. > > Best regards, > > Kaj-Ivar van der Wijst > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at yorba.org Tue Jan 26 02:35:45 2010 From: jim at yorba.org (Jim Nelson) Date: Mon, 25 Jan 2010 18:35:45 -0800 Subject: [Shotwell] Build errors In-Reply-To: <1264454246.3891.67.camel@buzz.west.homenet.org> References: <4B5CAC29.7070506@alumni.caltech.edu> <1264454246.3891.67.camel@buzz.west.homenet.org> Message-ID: Roman, Are you sure you needed to add the --vapidir option? It is included in the Makefile. Can you send back what you changed to make this work? -- Jim On Mon, Jan 25, 2010 at 1:17 PM, Roman Yepishev wrote: > On Sun, 2010-01-24 at 12:23 -0800, Paul Novak wrote: > > > > Also, could the instructions on installing shotwell, at > > http://trac.yorba.org/wiki/ShotwellInstallation, be corrected to reflect > > that hal (0.5.11) is deprecated but that gudev is needed to build > > shotwell, and that vala and libgee from Rawhide are recent enough to > > build shotwell? > > > Make sure that vala compiler reads the vapi directory supplied with > shotwell. I was having some build issues as well, since it reads > standard vapi directory by default only. > > I had to supply additional --vapidir to shotwell makefile. > > -- > Roman Yepishev > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark at fastzweimeter.de Tue Jan 26 18:42:38 2010 From: Mark at fastzweimeter.de (Mark Schuppert) Date: Tue, 26 Jan 2010 19:42:38 +0100 Subject: [Shotwell] Wishlist: Database updates, lighttable, easier deletion, aspect ratio Message-ID: <1264531358.2294.25.camel@mk64> Hi there, its amazing to see shotwells progress! It has become very usable and fast, it?s already a very good means! Yet I found there are somethings that could be thought over - let me suggest: * When I delete an image in the filemanager or the terminal, it is still existing in shotwells database. Add a single-button refresh database function to get rid of these phantoms. * Add some kind of lighttable-area (maybe in the left panel?), to which images may easily be drag-and-dropped. A lighttabe could open like an event and could be used for ordering prints for example. Maybe it could make sense to save a collection in the database for later use? * deleting images is not simple in shotwell, because shotwell asks how to handle imagefiles every time. eog for example gives an option to keep the way it deletes for the session. Browsing and deleting images using the keyboard is not easy fun because ALT-L is way more complicated than single button removal. * add a single way to change the aspect ration - many digital cameras take pictures in a ratio 4/3 instead of traditional 3/2. An automatic funktion to switch the ratio whith the possibility to adjust the image would be great! (something like a frame of the full width of an photo that could be moved to the top or the bottom) How about that? Mark From pnovak at alumni.caltech.edu Wed Jan 27 05:09:36 2010 From: pnovak at alumni.caltech.edu (Paul Novak) Date: Tue, 26 Jan 2010 21:09:36 -0800 Subject: [Shotwell] Build errors In-Reply-To: <992b763d1001251307j6671640ayc3a0d6d9c77e3ab6@mail.gmail.com> References: <4B5CAC29.7070506@alumni.caltech.edu> <992b763d1001251307j6671640ayc3a0d6d9c77e3ab6@mail.gmail.com> Message-ID: <4B5FCA90.5030005@alumni.caltech.edu> On 01/25/2010 01:07 PM, Lucas Beeler wrote: > Hi Paul, > > First of all, we appreciate your making us aware of a build issue > on Fedora 12. The diagnostic information you provided was helpful. One > further question though: when you used git to fetch the vala and > libgee sources from gnome.org, did you pull the source from trunk or > did you pull it from a stable release branch? In general, Gnome > sources pulled from trunk are under active development and may be > unstable. One thing you might want to try is rebuilding and > reinstalling vala and libgee from stable release tarballs, accessible > through the following links: > > Vala: > http://live.gnome.org/Vala/Release > > Libgee: > http://live.gnome.org/Libgee/Release > > Once again, thanks for giving us the heads up. > > Best regards, > Lucas > Lucas, Thanks for the pointer about using the stable releases. Using the stable release tarballs of vala and libgee allows me to build shotwell. When I try to run it, it still fails at runtime with the error "Illegal instruction", while the debug build works. I would like to help troubleshoot. Do you have any suggestions on where to start? I have also updated the shotwell installation page, at http://trac.yorba.org/wiki/ShotwellInstallation, to reflect that the stable source releases (or Rawhide) should be used. Paul From pnovak at alumni.caltech.edu Thu Jan 28 05:07:29 2010 From: pnovak at alumni.caltech.edu (Paul Novak) Date: Wed, 27 Jan 2010 21:07:29 -0800 Subject: [Shotwell] Build errors In-Reply-To: References: <4B5CAC29.7070506@alumni.caltech.edu> <992b763d1001251307j6671640ayc3a0d6d9c77e3ab6@mail.gmail.com> <4B5FCA90.5030005@alumni.caltech.edu> Message-ID: <4B611B91.8090208@alumni.caltech.edu> On 01/27/2010 11:02 AM, Jim Nelson wrote: > Hi Paul, > > Thanks for the pointer about using the stable releases. Using the stable >> release tarballs of vala and libgee allows me to build shotwell. When I >> try to run it, it still fails at runtime with the error "Illegal >> instruction", while the debug build works. I would like to help >> troubleshoot. Do you have any suggestions on where to start? >> > > The following steps would be a big help. Can you run Shotwell from the > command-line like this: > > % SHOTWELL_LOG=1 gdb shotwell > > You'll see Shotwell dump logging information to the console. When the > illegal instruction occurs, gdb will resume control. At the gdb prompt > type: > > (gdb) where > > Can you send us everything that's been logged to the screen? Thanks! > > -- Jim > Hi Jim, I followed your instructions and the output is below. If you need additional information, let me know. Paul $ shotwell Illegal instruction $ SHOTWELL_LOG=1 $ echo $SHOTWELL_LOG 1 $ gdb shotwell GNU gdb (GDB) Fedora (7.0.1-29.fc12) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/local/bin/shotwell...done. (gdb) run Starting program: /usr/local/bin/shotwell warning: .dynamic section for "/usr/lib/libfreetype.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libltdl.so.7" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libz.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libexpat.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libudev.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libICE.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations [Thread debugging using libthread_db enabled] warning: .dynamic section for "/usr/lib/libcanberra-gtk.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcanberra.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libogg.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libtdb.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Missing separate debuginfo for /usr/lib/libtdb.so.1 Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/a9/d89f5a179340f6dc46499bbcdce21d2f85a644.debug [New Thread 0xb7d37b70 (LWP 2062)] Program received signal SIGILL, Illegal instruction. dimensions_get_scaled_by_height (self=0xbffff0f0, scale=24, result=0xbffff0b8) at Dimensions.vala:208 208 Dimensions.vala: No such file or directory. in Dimensions.vala Missing separate debuginfos, use: debuginfo-install GConf2-2.28.0-3.fc12.i686 ORBit2-2.14.17-3.fc12.i686 atk-1.28.0-1.fc12.i686 bzip2-libs-1.0.5-6.fc12.i686 cairo-1.8.8-3.fc12.i686 dbus-glib-0.82-2.fc12.i686 dbus-libs-1.2.16-9.fc12.i686 enchant-1.5.0-3.fc12.i686 expat-2.0.1-8.fc12.i686 fontconfig-2.8.0-1.fc12.i686 freetype-2.3.11-3.fc12.i686 gamin-0.1.10-5.fc12.i686 geoclue-0.11.1.1-0.10.20091026git73b6729.fc12.i686 glib2-2.22.3-2.fc12.i686 glibc-2.11.1-1.i686 gnutls-2.8.5-1.fc12.i686 gstreamer-0.10.25.1-3.fc12.i686 gstreamer-plugins-base-0.10.25.1-2.fc12.i686 gtk2-2.18.6-1.fc12.i686 gtk2-engines-2.18.4-4.fc12.i686 gvfs-1.4.3-3.fc12.i686 libICE-1.0.6-1.fc12.i686 libSM-1.1.0-7.fc12.i686 libX11-1.3-1.fc12.i686 libXau-1.0.5-1.fc12.i686 libXcomposite-0.4.1-2.fc12.i686 libXcursor-1.1.10-1.fc12.i686 libXdamage-1.1.2-1.fc12.i686 libXext-1.1-2.fc12.i686 libXfixes-4.0.4-1.fc12.i686 libXi-1.3-1.fc12.i686 libXinerama-1.1-1.fc12.i686 libXrandr-1.3.0-3.fc12.i686 libXrender-0.9.5-1.fc12.i686 libXt-1.0.7-1.fc12.i686 libcanberra-0.22-1.fc12.i686 libcanberra-gtk2-0.22-1.fc12.i686 libcap-ng-0.6.2-3.fc12.i686 libcroco-0.6.2-3.fc12.i686 libexif-0.6.16-4.fc12.i686 libgcc-4.4.2-20.fc12.i686 libgcrypt-1.4.4-8.fc12.i686 libgpg-error-1.6-4.i686 libgphoto2-2.4.7-2.fc12.i686 libgsf-1.14.15-4.fc12.i686 libgudev1-147-2.fc13.i686 libicu-4.2.1-7.fc12.i686 libjpeg-6b-46.fc12.i686 libogg-1.1.4-2.fc12.i686 libpng-1.2.39-1.fc12.i686 librsvg2-2.26.0-3.fc12.i686 libselinux-2.0.87-1.fc12.i686 libsoup-2.28.2-1.fc12.i686 libstdc++-4.4.2-20.fc12.i686 libtasn1-2.3-1.fc12.i686 libtool-ltdl-2.2.6-17.fc12.i686 libudev-147-2.fc13.i686 libuuid-2.16.2-5.fc12.i686 libvorbis-1.2.3-3.fc12.i686 libxcb-1.5-1.fc12.i686 libxml2-2.7.6-1.fc12.i686 libxslt-1.1.26-1.fc12.i686 pango-1.26.2-1.fc12.i686 pixman-0.16.4-2.fc12.i686 sqlite-3.6.20-1.fc12.i686 unique-1.1.6-1.fc12.i686 webkitgtk-1.1.15.4-1.fc12.i686 zlib-1.2.3-23.fc12.i686 (gdb) where #0 dimensions_get_scaled_by_height (self=0xbffff0f0, scale=24, result= 0xbffff0b8) at Dimensions.vala:208 #1 0x080a07fe in dimensions_get_scaled (self=, scale=, scale_up=, result=) at Dimensions.c:443 #2 0x080715f6 in scale_pixbuf (pixbuf=, scale=, interp=, scale_up=) at image_util.vala:92 #3 0x080bdf8e in resources_get_icon (name=, scale=) at Resources.vala:215 #4 0x08058af9 in app_window_construct (object_type=) at AppWindow.vala:352 #5 0x080f427c in library_window_construct (object_type=, monitor=, monitor_target=) at LibraryWindow.vala:254 #6 0x080f4f26 in library_window_new (monitor=, monitor_target=) at LibraryWindow.vala:254 #7 0x080567b2 in library_exec (mounts=, mounts_length1=) at main.vala:141 #8 0x08056d2a in _main (args=0xbffff3d4, args_length1=1) at main.vala:245 #9 0x08056e09 in main (argc=, argv=) at main.vala:198 From jim at yorba.org Thu Jan 28 20:04:19 2010 From: jim at yorba.org (Jim Nelson) Date: Thu, 28 Jan 2010 12:04:19 -0800 Subject: [Shotwell] Build errors In-Reply-To: <4B611B91.8090208@alumni.caltech.edu> References: <4B5CAC29.7070506@alumni.caltech.edu> <992b763d1001251307j6671640ayc3a0d6d9c77e3ab6@mail.gmail.com> <4B5FCA90.5030005@alumni.caltech.edu> <4B611B91.8090208@alumni.caltech.edu> Message-ID: Hi Paul, Just today I built Shotwell from trunk on Fedora 12, and I do not see this problem. I believe it has something to do with your build environment. I confirmed today that the version of gudev that comes with Fedora 12 (145) is sufficient for our needs, so I checked in an update Makefile that reflects this. That means you should be able to build Shotwell with only adding packages from the GUI Add/Remove Software utility (I'm seeing Vala 0.7.9 and libgee 0.5.0 there) and the yum command-line tool, as reflected on our wiki. I'd really recommend attempting to build this with a clean system. -- Jim On Wed, Jan 27, 2010 at 9:07 PM, Paul Novak wrote: > On 01/27/2010 11:02 AM, Jim Nelson wrote: > > Hi Paul, > > > > Thanks for the pointer about using the stable releases. Using the stable > >> release tarballs of vala and libgee allows me to build shotwell. When I > >> try to run it, it still fails at runtime with the error "Illegal > >> instruction", while the debug build works. I would like to help > >> troubleshoot. Do you have any suggestions on where to start? > >> > > > > The following steps would be a big help. Can you run Shotwell from the > > command-line like this: > > > > % SHOTWELL_LOG=1 gdb shotwell > > > > You'll see Shotwell dump logging information to the console. When the > > illegal instruction occurs, gdb will resume control. At the gdb prompt > > type: > > > > (gdb) where > > > > Can you send us everything that's been logged to the screen? Thanks! > > > > -- Jim > > > > Hi Jim, > > I followed your instructions and the output is below. If you need > additional information, let me know. > > Paul > > $ shotwell > Illegal instruction > $ SHOTWELL_LOG=1 > $ echo $SHOTWELL_LOG > 1 > $ gdb shotwell > GNU gdb (GDB) Fedora (7.0.1-29.fc12) > Copyright (C) 2009 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-redhat-linux-gnu". > For bug reporting instructions, please see: > ... > Reading symbols from /usr/local/bin/shotwell...done. > (gdb) run > Starting program: /usr/local/bin/shotwell > warning: .dynamic section for "/usr/lib/libfreetype.so.6" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/usr/lib/libltdl.so.7" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/lib/libz.so.1" is not at the expected > address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at > the expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/lib/libexpat.so.1" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/lib/libudev.so.0" is not at the expected > address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/usr/lib/libICE.so.6" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > [Thread debugging using libthread_db enabled] > warning: .dynamic section for "/usr/lib/libcanberra-gtk.so.0" is not at > the expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/usr/lib/libcanberra.so.0" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/usr/lib/libogg.so.0" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > warning: .dynamic section for "/usr/lib/libtdb.so.1" is not at the > expected address > warning: difference appears to be caused by prelink, adjusting expectations > Missing separate debuginfo for /usr/lib/libtdb.so.1 > Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install > /usr/lib/debug/.build-id/a9/d89f5a179340f6dc46499bbcdce21d2f85a644.debug > [New Thread 0xb7d37b70 (LWP 2062)] > > Program received signal SIGILL, Illegal instruction. > dimensions_get_scaled_by_height (self=0xbffff0f0, scale=24, > result=0xbffff0b8) > at Dimensions.vala:208 > 208 Dimensions.vala: No such file or directory. > in Dimensions.vala > Missing separate debuginfos, use: debuginfo-install > GConf2-2.28.0-3.fc12.i686 ORBit2-2.14.17-3.fc12.i686 > atk-1.28.0-1.fc12.i686 bzip2-libs-1.0.5-6.fc12.i686 > cairo-1.8.8-3.fc12.i686 dbus-glib-0.82-2.fc12.i686 > dbus-libs-1.2.16-9.fc12.i686 enchant-1.5.0-3.fc12.i686 > expat-2.0.1-8.fc12.i686 fontconfig-2.8.0-1.fc12.i686 > freetype-2.3.11-3.fc12.i686 gamin-0.1.10-5.fc12.i686 > geoclue-0.11.1.1-0.10.20091026git73b6729.fc12.i686 > glib2-2.22.3-2.fc12.i686 glibc-2.11.1-1.i686 gnutls-2.8.5-1.fc12.i686 > gstreamer-0.10.25.1-3.fc12.i686 > gstreamer-plugins-base-0.10.25.1-2.fc12.i686 gtk2-2.18.6-1.fc12.i686 > gtk2-engines-2.18.4-4.fc12.i686 gvfs-1.4.3-3.fc12.i686 > libICE-1.0.6-1.fc12.i686 libSM-1.1.0-7.fc12.i686 libX11-1.3-1.fc12.i686 > libXau-1.0.5-1.fc12.i686 libXcomposite-0.4.1-2.fc12.i686 > libXcursor-1.1.10-1.fc12.i686 libXdamage-1.1.2-1.fc12.i686 > libXext-1.1-2.fc12.i686 libXfixes-4.0.4-1.fc12.i686 > libXi-1.3-1.fc12.i686 libXinerama-1.1-1.fc12.i686 > libXrandr-1.3.0-3.fc12.i686 libXrender-0.9.5-1.fc12.i686 > libXt-1.0.7-1.fc12.i686 libcanberra-0.22-1.fc12.i686 > libcanberra-gtk2-0.22-1.fc12.i686 libcap-ng-0.6.2-3.fc12.i686 > libcroco-0.6.2-3.fc12.i686 libexif-0.6.16-4.fc12.i686 > libgcc-4.4.2-20.fc12.i686 libgcrypt-1.4.4-8.fc12.i686 > libgpg-error-1.6-4.i686 libgphoto2-2.4.7-2.fc12.i686 > libgsf-1.14.15-4.fc12.i686 libgudev1-147-2.fc13.i686 > libicu-4.2.1-7.fc12.i686 libjpeg-6b-46.fc12.i686 > libogg-1.1.4-2.fc12.i686 libpng-1.2.39-1.fc12.i686 > librsvg2-2.26.0-3.fc12.i686 libselinux-2.0.87-1.fc12.i686 > libsoup-2.28.2-1.fc12.i686 libstdc++-4.4.2-20.fc12.i686 > libtasn1-2.3-1.fc12.i686 libtool-ltdl-2.2.6-17.fc12.i686 > libudev-147-2.fc13.i686 libuuid-2.16.2-5.fc12.i686 > libvorbis-1.2.3-3.fc12.i686 libxcb-1.5-1.fc12.i686 > libxml2-2.7.6-1.fc12.i686 libxslt-1.1.26-1.fc12.i686 > pango-1.26.2-1.fc12.i686 pixman-0.16.4-2.fc12.i686 > sqlite-3.6.20-1.fc12.i686 unique-1.1.6-1.fc12.i686 > webkitgtk-1.1.15.4-1.fc12.i686 zlib-1.2.3-23.fc12.i686 > (gdb) where > #0 dimensions_get_scaled_by_height (self=0xbffff0f0, scale=24, result= > 0xbffff0b8) at Dimensions.vala:208 > #1 0x080a07fe in dimensions_get_scaled (self=, > scale=, scale_up=, > result=) at Dimensions.c:443 > #2 0x080715f6 in scale_pixbuf (pixbuf=, > scale=, interp=, > scale_up=) at image_util.vala:92 > #3 0x080bdf8e in resources_get_icon (name=, > scale=) at Resources.vala:215 > #4 0x08058af9 in app_window_construct (object_type=) > at AppWindow.vala:352 > #5 0x080f427c in library_window_construct (object_type= out>, > monitor=, monitor_target=) > at LibraryWindow.vala:254 > #6 0x080f4f26 in library_window_new (monitor=, > monitor_target=) at LibraryWindow.vala:254 > #7 0x080567b2 in library_exec (mounts=, > mounts_length1=) at main.vala:141 > #8 0x08056d2a in _main (args=0xbffff3d4, args_length1=1) at main.vala:245 > #9 0x08056e09 in main (argc=, argv= optimized out>) > at main.vala:198 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pnovak at alumni.caltech.edu Fri Jan 29 06:29:46 2010 From: pnovak at alumni.caltech.edu (Paul Novak) Date: Thu, 28 Jan 2010 22:29:46 -0800 Subject: [Shotwell] Build errors In-Reply-To: References: <4B5CAC29.7070506@alumni.caltech.edu> <992b763d1001251307j6671640ayc3a0d6d9c77e3ab6@mail.gmail.com> <4B5FCA90.5030005@alumni.caltech.edu> <4B611B91.8090208@alumni.caltech.edu> Message-ID: <4B62805A.7060700@alumni.caltech.edu> On 01/28/2010 12:04 PM, Jim Nelson wrote: > Hi Paul, > > Just today I built Shotwell from trunk on Fedora 12, and I do not see this > problem. I believe it has something to do with your build environment. I > confirmed today that the version of gudev that comes with Fedora 12 (145) is > sufficient for our needs, so I checked in an update Makefile that reflects > this. > > That means you should be able to build Shotwell with only adding packages > from the GUI Add/Remove Software utility (I'm seeing Vala 0.7.9 and libgee > 0.5.0 there) and the yum command-line tool, as reflected on our wiki. I'd > really recommend attempting to build this with a clean system. > > -- Jim > > On Wed, Jan 27, 2010 at 9:07 PM, Paul Novak wrote: > >> On 01/27/2010 11:02 AM, Jim Nelson wrote: >>> Hi Paul, >>> >>> Thanks for the pointer about using the stable releases. Using the stable >>>> release tarballs of vala and libgee allows me to build shotwell. When I >>>> try to run it, it still fails at runtime with the error "Illegal >>>> instruction", while the debug build works. I would like to help >>>> troubleshoot. Do you have any suggestions on where to start? >>>> >>> >>> The following steps would be a big help. Can you run Shotwell from the >>> command-line like this: >>> >>> % SHOTWELL_LOG=1 gdb shotwell >>> >>> You'll see Shotwell dump logging information to the console. When the >>> illegal instruction occurs, gdb will resume control. At the gdb prompt >>> type: >>> >>> (gdb) where >>> >>> Can you send us everything that's been logged to the screen? Thanks! >>> >>> -- Jim >>> >> >> Hi Jim, >> >> I followed your instructions and the output is below. If you need >> additional information, let me know. >> >> Paul >> >> $ shotwell >> Illegal instruction >> $ SHOTWELL_LOG=1 >> $ echo $SHOTWELL_LOG >> 1 >> $ gdb shotwell >> GNU gdb (GDB) Fedora (7.0.1-29.fc12) >> Copyright (C) 2009 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. Type "show copying" >> and "show warranty" for details. >> This GDB was configured as "i686-redhat-linux-gnu". >> For bug reporting instructions, please see: >> ... >> Reading symbols from /usr/local/bin/shotwell...done. >> (gdb) run >> Starting program: /usr/local/bin/shotwell >> warning: .dynamic section for "/usr/lib/libfreetype.so.6" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/usr/lib/libltdl.so.7" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/lib/libz.so.1" is not at the expected >> address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at >> the expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/lib/libexpat.so.1" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/lib/libudev.so.0" is not at the expected >> address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/usr/lib/libICE.so.6" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> [Thread debugging using libthread_db enabled] >> warning: .dynamic section for "/usr/lib/libcanberra-gtk.so.0" is not at >> the expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/usr/lib/libcanberra.so.0" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/usr/lib/libogg.so.0" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> warning: .dynamic section for "/usr/lib/libtdb.so.1" is not at the >> expected address >> warning: difference appears to be caused by prelink, adjusting expectations >> Missing separate debuginfo for /usr/lib/libtdb.so.1 >> Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install >> /usr/lib/debug/.build-id/a9/d89f5a179340f6dc46499bbcdce21d2f85a644.debug >> [New Thread 0xb7d37b70 (LWP 2062)] >> >> Program received signal SIGILL, Illegal instruction. >> dimensions_get_scaled_by_height (self=0xbffff0f0, scale=24, >> result=0xbffff0b8) >> at Dimensions.vala:208 >> 208 Dimensions.vala: No such file or directory. >> in Dimensions.vala >> Missing separate debuginfos, use: debuginfo-install >> GConf2-2.28.0-3.fc12.i686 ORBit2-2.14.17-3.fc12.i686 >> atk-1.28.0-1.fc12.i686 bzip2-libs-1.0.5-6.fc12.i686 >> cairo-1.8.8-3.fc12.i686 dbus-glib-0.82-2.fc12.i686 >> dbus-libs-1.2.16-9.fc12.i686 enchant-1.5.0-3.fc12.i686 >> expat-2.0.1-8.fc12.i686 fontconfig-2.8.0-1.fc12.i686 >> freetype-2.3.11-3.fc12.i686 gamin-0.1.10-5.fc12.i686 >> geoclue-0.11.1.1-0.10.20091026git73b6729.fc12.i686 >> glib2-2.22.3-2.fc12.i686 glibc-2.11.1-1.i686 gnutls-2.8.5-1.fc12.i686 >> gstreamer-0.10.25.1-3.fc12.i686 >> gstreamer-plugins-base-0.10.25.1-2.fc12.i686 gtk2-2.18.6-1.fc12.i686 >> gtk2-engines-2.18.4-4.fc12.i686 gvfs-1.4.3-3.fc12.i686 >> libICE-1.0.6-1.fc12.i686 libSM-1.1.0-7.fc12.i686 libX11-1.3-1.fc12.i686 >> libXau-1.0.5-1.fc12.i686 libXcomposite-0.4.1-2.fc12.i686 >> libXcursor-1.1.10-1.fc12.i686 libXdamage-1.1.2-1.fc12.i686 >> libXext-1.1-2.fc12.i686 libXfixes-4.0.4-1.fc12.i686 >> libXi-1.3-1.fc12.i686 libXinerama-1.1-1.fc12.i686 >> libXrandr-1.3.0-3.fc12.i686 libXrender-0.9.5-1.fc12.i686 >> libXt-1.0.7-1.fc12.i686 libcanberra-0.22-1.fc12.i686 >> libcanberra-gtk2-0.22-1.fc12.i686 libcap-ng-0.6.2-3.fc12.i686 >> libcroco-0.6.2-3.fc12.i686 libexif-0.6.16-4.fc12.i686 >> libgcc-4.4.2-20.fc12.i686 libgcrypt-1.4.4-8.fc12.i686 >> libgpg-error-1.6-4.i686 libgphoto2-2.4.7-2.fc12.i686 >> libgsf-1.14.15-4.fc12.i686 libgudev1-147-2.fc13.i686 >> libicu-4.2.1-7.fc12.i686 libjpeg-6b-46.fc12.i686 >> libogg-1.1.4-2.fc12.i686 libpng-1.2.39-1.fc12.i686 >> librsvg2-2.26.0-3.fc12.i686 libselinux-2.0.87-1.fc12.i686 >> libsoup-2.28.2-1.fc12.i686 libstdc++-4.4.2-20.fc12.i686 >> libtasn1-2.3-1.fc12.i686 libtool-ltdl-2.2.6-17.fc12.i686 >> libudev-147-2.fc13.i686 libuuid-2.16.2-5.fc12.i686 >> libvorbis-1.2.3-3.fc12.i686 libxcb-1.5-1.fc12.i686 >> libxml2-2.7.6-1.fc12.i686 libxslt-1.1.26-1.fc12.i686 >> pango-1.26.2-1.fc12.i686 pixman-0.16.4-2.fc12.i686 >> sqlite-3.6.20-1.fc12.i686 unique-1.1.6-1.fc12.i686 >> webkitgtk-1.1.15.4-1.fc12.i686 zlib-1.2.3-23.fc12.i686 >> (gdb) where >> #0 dimensions_get_scaled_by_height (self=0xbffff0f0, scale=24, result= >> 0xbffff0b8) at Dimensions.vala:208 >> #1 0x080a07fe in dimensions_get_scaled (self=, >> scale=, scale_up=, >> result=) at Dimensions.c:443 >> #2 0x080715f6 in scale_pixbuf (pixbuf=, >> scale=, interp=, >> scale_up=) at image_util.vala:92 >> #3 0x080bdf8e in resources_get_icon (name=, >> scale=) at Resources.vala:215 >> #4 0x08058af9 in app_window_construct (object_type=) >> at AppWindow.vala:352 >> #5 0x080f427c in library_window_construct (object_type=> out>, >> monitor=, monitor_target=) >> at LibraryWindow.vala:254 >> #6 0x080f4f26 in library_window_new (monitor=, >> monitor_target=) at LibraryWindow.vala:254 >> #7 0x080567b2 in library_exec (mounts=, >> mounts_length1=) at main.vala:141 >> #8 0x08056d2a in _main (args=0xbffff3d4, args_length1=1) at main.vala:245 >> #9 0x08056e09 in main (argc=, argv=> optimized out>) >> at main.vala:198 >> > Hi Jim, I built shotwell from SVN trunk this evening. I used libgudev1-devel from Fedora 12, and re-built vala and libgee from the stable source releases. When I ran shotwell, it failed at runtime with the "Illegal instruction" error. I changed the Makefile to build shotwell with the following compiler flags CFLAGS = -O2 -g -pipe -mfpmath=sse -march=athlon-xp because I am building and running on an AMD Athlon XP 2000+ cpu; the diff is below. Paul Index: Makefile =================================================================== --- Makefile (revision 1141) +++ Makefile (working copy) @@ -242,7 +242,7 @@ ifdef BUILD_DEBUG CFLAGS = -O0 -g -pipe else -CFLAGS = -O2 -g -pipe -mfpmath=sse -march=nocona +CFLAGS = -O2 -g -pipe -mfpmath=sse -march=athlon-xp endif endif From pnovak at alumni.caltech.edu Fri Jan 29 06:47:12 2010 From: pnovak at alumni.caltech.edu (Paul Novak) Date: Thu, 28 Jan 2010 22:47:12 -0800 Subject: [Shotwell] Rightward pointing mouse cursor Message-ID: <4B628470.6020205@alumni.caltech.edu> Hello, Occasionally, the mouse pointer points towards the right. This happens when I edit a photo by double-clicking on a photo, pressing the "Crop" button at the bottom of the screen, entering the cropped area and then upon leaving the cropped area the mouse points rightward. This can be fixed with the changes listed in the diff below so the mouse pointer is consistent and always points in one direction. The change is replacing every instance of GDK_ARROW with GDK_LEFT_PTR. The standard cursors are at http://library.gnome.org/devel/gdk/stable/gdk-Cursors.html, and I think GDK_LEFT_PTR is the appropriate cursor. Paul Index: src/AppWindow.vala =================================================================== --- src/AppWindow.vala (revision 1141) +++ src/AppWindow.vala (working copy) @@ -319,7 +319,7 @@ } public void set_normal_cursor() { - window.set_cursor(new Gdk.Cursor(Gdk.CursorType.ARROW)); + window.set_cursor(new Gdk.Cursor(Gdk.CursorType.LEFT_PTR)); spin_event_loop(); } } Index: src/FacebookConnector.vala =================================================================== --- src/FacebookConnector.vala (revision 1141) +++ src/FacebookConnector.vala (working copy) @@ -345,7 +345,7 @@ } private void on_page_load(WebKit.WebFrame origin_frame) { - webview.window.set_cursor(new Gdk.Cursor(Gdk.CursorType.ARROW)); + webview.window.set_cursor(new Gdk.Cursor(Gdk.CursorType.LEFT_PTR)); string loaded_url = origin_frame.get_uri().dup(); Index: src/FlickrConnector.vala =================================================================== --- src/FlickrConnector.vala (revision 1141) +++ src/FlickrConnector.vala (working copy) @@ -673,7 +673,7 @@ } private void on_page_load(WebKit.WebFrame origin_frame) { - white_pane.window.set_cursor(new Gdk.Cursor(Gdk.CursorType.ARROW)); + white_pane.window.set_cursor(new Gdk.Cursor(Gdk.CursorType.LEFT_PTR)); string token; string username; bool got_auth_info = false; Index: src/EditingTools.vala =================================================================== --- src/EditingTools.vala (revision 1141) +++ src/EditingTools.vala (working copy) @@ -524,7 +524,7 @@ private CropToolWindow crop_tool_window = null; private Gdk.Pixbuf color_shifted = null; - private Gdk.CursorType current_cursor_type = Gdk.CursorType.ARROW; + private Gdk.CursorType current_cursor_type = Gdk.CursorType.LEFT_PTR; private BoxLocation in_manipulation = BoxLocation.OUTSIDE; private Gdk.GC wide_black_gc = null; private Gdk.GC wide_white_gc = null; @@ -1024,7 +1024,7 @@ // make sure the cursor isn't set to a modify indicator if (canvas != null) - canvas.get_drawing_window().set_cursor(new Gdk.Cursor(Gdk.CursorType.ARROW)); + canvas.get_drawing_window().set_cursor(new Gdk.Cursor(Gdk.CursorType.LEFT_PTR)); base.deactivate(); } @@ -1168,7 +1168,7 @@ Gdk.Rectangle scaled_pos = canvas.get_scaled_pixbuf_position(); Box offset_scaled_crop = scaled_crop.get_offset(scaled_pos.x, scaled_pos.y); - Gdk.CursorType cursor_type = Gdk.CursorType.ARROW; + Gdk.CursorType cursor_type = Gdk.CursorType.LEFT_PTR; switch (offset_scaled_crop.approx_location(x, y)) { case BoxLocation.LEFT_SIDE: cursor_type = Gdk.CursorType.LEFT_SIDE; @@ -1207,7 +1207,7 @@ break; default: - // use Gdk.CursorType.ARROW + // use Gdk.CursorType.LEFT_PTR break; } @@ -1862,7 +1862,7 @@ bind_window_handlers(); - cached_arrow_cursor = new Gdk.Cursor(Gdk.CursorType.ARROW); + cached_arrow_cursor = new Gdk.Cursor(Gdk.CursorType.LEFT_PTR); cached_grab_cursor = new Gdk.Cursor(Gdk.CursorType.FLEUR); canvas.get_photo().altered += on_photo_altered;