From golinuxgo at gmail.com Fri Feb 1 00:13:03 2013 From: golinuxgo at gmail.com (go linux) Date: Thu, 31 Jan 2013 18:13:03 -0600 Subject: [Shotwell] Shotwell no longer working on squeeze In-Reply-To: References: <20130124061234.GD6008@gamma.logic.tuwien.ac.at> <20130125035658.GA32110@gamma.logic.tuwien.ac.at> <5106de70.e958420a.1021.ffffdd15@mx.google.com> <5107055b.cade440a.4fb6.ffffe339@mx.google.com> Message-ID: On 1/31/13, Colin Law wrote: > On 31 January 2013 20:23, go linux wrote: >> >> On 1/31/13, Colin Law wrote: >>> >>> Is there a Debian users list you could ask that on? It must be some >>> configuration that you have accidentally changed (or purposefully >>> without realising the side effect) rather than something that has been >>> installed, or it would affect all users. >>> >> >> Well, I did post to the pkg-gnome-maintainers mailing list which was >> the contact listed on the rhythmbox package. Guess I'll put something >> together for the Debian users list in a bit. > > On the Debian list the issue to ask about is not the problem with the > camera, it is just with help to work out why rhythmbox is running > without you asking it. > OK. Will do. Actually, I may have already asked that question. > > I think someone already suggested that you check the autostart setup > for the user (don't know where that is in Debian). > rhythmbox is not in the start-up list but the gnome-keyring and gnome-settings-daemon are. > >> >>> >>> ps -ejH might just tell you something (though I am not very hopeful) , >>> it will show the processes as a tree so you can see which process >>> started rhythmbox. >>> >> >> Um . . . Happy to do that but it's going to need a little translation. >> ;) The list related to rhythmbox in memory maps (in the system >> monitor) is REALLY LONG! But I can't find a way to print it out. > > Not sure what you mean about rhythmbox and memory maps, but if you > need to copy stuff out of the terminal then you can use Ctrl+Shift+C > (or probably Edit Copy in the menu, dependant on which terminal you > are using). Are you talking about syslog? If so then the very first > entries for rhythmbox (and a few before it) might be interesting in > case they give an idea as to why it is starting up. > The 'memory maps' are an option to view for individual processes in the gnome-system-monitor gui not in a terminal. I don't know what command that would translate to. Early on I went through all the logs and only found one useful reference in .xsession-errors that I posted possibly in my original email. > ps -ejH produces a very simple output, though it can be a few screens > long. Just look for rhythmbox down the right hand side and you will > see it nested under its parent. As I said it is a bit of a long shot > but it might be informative. > Apologies for being so dense. The only only mention of rhythmbox is under the gdm3 tree: 1799 1798 1798 ? 00:00:00 gdm3 2732 1798 1798 ? 00:00:00 gdm-simple-slave 2733 2733 2733 tty8 00:00:38 Xorg 2785 1798 1798 ? 00:00:00 gdm-session-worker 2820 2820 2820 ? 00:00:00 x-session-manager 2858 2858 2858 ? 00:00:00 ssh-agent 2872 2872 2872 ? 00:00:00 seahorse-agent 2882 2820 2820 ? 00:00:00 gnome-power-manager 2897 2820 2820 ? 00:00:04 gnome-panel 2901 2820 2820 ? 00:00:01 nautilus 2907 2820 2820 ? 00:00:00 nm-applet 2908 2820 2820 ? 00:00:00 gdu-notificatio 2910 2820 2820 ? 00:00:00 polkit-gnome-au 2911 2820 2820 ? 00:00:07 compiz 2914 2820 2820 ? 00:01:02 firefox-bin 3210 2820 2820 ? 00:00:00 plugin-container 2916 2820 2820 ? 00:00:00 rhythmbox 2921 2820 2820 ? 00:00:00 kerneloops-applet 2922 2820 2820 ? 00:00:00 python > >> >>> >>> I have lost track slightly, is it actually rhythmbox that is running >>> or a rhythmbox related process? >>> >> >> Is that a trick question? The process is listed as rhythmbox. > > No, I just had a recollection that rhythmbox plugins were mentioned at > one point so was just checking that the process is actually RB, rather > than check back through the 30 odd messages in the thread. > Both rhythmbox and the rhythmbox-plugins are in the 'memory maps' for 'rhythmbox' (PID 2916). I guesstimate there are several hundred other entries in that list - all sorts of stuff from media to python. I originally ran across rhythmbox-plugins when I searched in synaptic for 'MTP'. That was the first clue that rhythmbox might be involved in preventing shotwell from accessing the camera. I really appreciate the followup. I love a good mystery! From golinuxgo at gmail.com Fri Feb 1 00:17:48 2013 From: golinuxgo at gmail.com (go linux) Date: Thu, 31 Jan 2013 18:17:48 -0600 Subject: [Shotwell] Shotwell no longer working on squeeze In-Reply-To: <510af2f2.c6ea440a.66ca.fffffedf@mx.google.com> References: <20130124061234.GD6008@gamma.logic.tuwien.ac.at> <20130125035658.GA32110@gamma.logic.tuwien.ac.at> <5106de70.e958420a.1021.ffffdd15@mx.google.com> <5107055b.cade440a.4fb6.ffffe339@mx.google.com> <510af2f2.c6ea440a.66ca.fffffedf@mx.google.com> Message-ID: On 1/31/13, Jim Nelson wrote: > I don't know if this is relevant, but if your camera(s) are being recognized > as MTP devices, it's possible Rhythmbox is being launched because it's > associated with those devices (and not at startup). The easy way to check > is System Settings -> Details -> Default Applications -> Music. > > -- Jim > I have checked every media association that I can find in 'preferred applications' and nautilus and none of them are pointing to rhythmbox. From hendry.michael at gmail.com Fri Feb 1 04:34:03 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Fri, 1 Feb 2013 04:34:03 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: <510af76f.e5e2440a.01e3.fffff162@mx.google.com> References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> Message-ID: On 31 Jan 2013, at 23:00, Jim Nelson wrote: > We've had an outstanding bug that resulted in some thumbnails not being regenerated, as well as a bug where video thumbnails were not being regenerated. These are fixed in master and will be available in 0.14. > > If you'd like to try the absolute latest of Shotwell, you can install it from our Daily Build PPA: https://launchpad.net/~yorba/+archive/daily-builds/ > > One other trick for forcing Shotwell to generate all your photo thumbnails (but not the videos): in the Library page (the first one when you run Shotwell), press F8 and press the far-left button on the Search bar; this will display only photos. Then press Ctrl+A and Ctrl+R. This will rotate all the photos, generating new thumbnails along the way. When it's finished, press Ctrl+Z. This will revert the rotation and generate thumbnails again. > > Convoluted, but a simple trick until 0.14 is released. Or, as I mentioned, please consider running our Daily Build version and see if that fixes it. I'll give the Ctrl-A Ctrl-R Ctrl-Z sequence a try first - only problem is, I'm not entirely sure which key is being interpreted as Ctrl in this Virtual Machine Ubuntu 12.04 running in Parallels on a Mac! I'll leave it running overnight (23:10 hrs here), and see what's happened in the morning. Thanks, Michael > > -- Jim > > On Thu, Jan 31, 2013 at 9:02 AM, Michael Hendry wrote: >> >> On 30 Jan 2013, at 20:02, Jim Nelson wrote: >> >> > A long, long time ago Yorba ported Shotwell to OSX and Windows. The Windows version was crippled but functional. The OSX version was in worse shape; I wouldn't even call it usable. We felt there was little demand for Shotwell outside of the GNOME desktop and abandoned the ports. My current estimate is that it would be quite an undertaking to port Shotwell today (which is a much larger program now). >> > >> > Shotwell doesn't write metadata to any RAW files today. Exiv2, the photo metadata it relies on, does support writing to NEF (as well as a handful of other RAW formats), and it's something we hope to offer in the future: http://redmine.yorba.org/issues/2622 >> > >> > As far as migrating Shotwell into your new machine, yes, you can copy the database and thumbnails as you've mentioned. You'll need to copy the photo files into their exact location. If they're stored in your home directory, that means your home directory name must be exactly the same. >> >> Thanks, Jim. >> >> I really need to have access to my photos in the Mac's file system, and before you sent this email I'd already copied them all across into my Mac in the same subdirectories as before - in /Users/michaelhendry/Pictures/Shotwell Library. >> >> I had already copied the database across, but not the thumbnails (I know, I should have waited for your advice!!), and I opened Shotwell in the Ubuntu virtual machine and asked it to "Import from Folder" - pointing it to the folder above. This proceeded as expected, and eventually all my images were available on my Mac, through Shotwell, with tags and Events intact. >> >> At this stage I noticed that not all of the thumbnails were present, but there appeared to be a background process going on, which was gradually re-creating them. >> >> Unfortunately, this appears to have ceased, with 5423 entries in each of thumbs128 and thumbs360. >> >> Is there some way of getting the thumbnail creation to start up again, or should I empty the shotwell library, copy the thumbnails across from my Ubuntu machine, and start the process of Importation again? >> >> Michael >> >> >> > >> > -- Jim >> > >> > On Wed, Jan 30, 2013 at 7:50 AM, Joseph Bylund wrote: >> > So I understand from the list that shotwell has at times in the past worked on OSX, how much of an undertaking would it be to get it working on OSX again (with possibly a restricted set of abilities)? >> > -Joe >> > _______________________________________________ >> > 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 javajens at gmail.com Fri Feb 1 07:44:15 2013 From: javajens at gmail.com (Jens B.) Date: Fri, 1 Feb 2013 08:44:15 +0100 Subject: [Shotwell] Development tools Message-ID: Hi there, I am really new to vala so I'd ask you guys about your development process. Right now I, like several people, printf alot to see whats going on, but this can't be right. So my questions: What IDE do you use? How do you debug? How do you test? Thanks! From clanlaw at googlemail.com Fri Feb 1 08:07:28 2013 From: clanlaw at googlemail.com (Colin Law) Date: Fri, 1 Feb 2013 08:07:28 +0000 Subject: [Shotwell] Shotwell no longer working on squeeze In-Reply-To: References: <20130124061234.GD6008@gamma.logic.tuwien.ac.at> <20130125035658.GA32110@gamma.logic.tuwien.ac.at> <5106de70.e958420a.1021.ffffdd15@mx.google.com> <5107055b.cade440a.4fb6.ffffe339@mx.google.com> Message-ID: On 1 February 2013 00:13, go linux wrote: > On 1/31/13, Colin Law wrote: >> ... > The 'memory maps' are an option to view for individual processes in > the gnome-system-monitor gui not in a terminal. I don't know what > command that would translate to. Early on I went through all the logs > and only found one useful reference in .xsession-errors that I posted > possibly in my original email. I think that did not appear till you plugged the camera in, so does not explain why rhythmbox is already running. I think you have previously said that rhythmbox is running immediately after a re-boot haven't you? > >> ps -ejH produces a very simple output, though it can be a few screens >> long. Just look for rhythmbox down the right hand side and you will >> see it nested under its parent. As I said it is a bit of a long shot >> but it might be informative. >> > > Apologies for being so dense. The only only mention of rhythmbox is > under the gdm3 tree: > > 1799 1798 1798 ? 00:00:00 gdm3 > 2732 1798 1798 ? 00:00:00 gdm-simple-slave > 2733 2733 2733 tty8 00:00:38 Xorg > 2785 1798 1798 ? 00:00:00 gdm-session-worker > 2820 2820 2820 ? 00:00:00 x-session-manager > 2858 2858 2858 ? 00:00:00 ssh-agent > 2872 2872 2872 ? 00:00:00 seahorse-agent > 2882 2820 2820 ? 00:00:00 gnome-power-manager > 2897 2820 2820 ? 00:00:04 gnome-panel > 2901 2820 2820 ? 00:00:01 nautilus > 2907 2820 2820 ? 00:00:00 nm-applet > 2908 2820 2820 ? 00:00:00 gdu-notificatio > 2910 2820 2820 ? 00:00:00 polkit-gnome-au > 2911 2820 2820 ? 00:00:07 compiz > 2914 2820 2820 ? 00:01:02 firefox-bin > 3210 2820 2820 ? 00:00:00 plugin-container > 2916 2820 2820 ? 00:00:00 rhythmbox > 2921 2820 2820 ? 00:00:00 kerneloops-applet > 2922 2820 2820 ? 00:00:00 python I don't know whether that would tell anyone anything useful. It says that rhythmbox is owned by x-session-manager but I don't know what that implies (if anything). I suspect your only hope now lies with the Debian list. Colin From hendry.michael at gmail.com Fri Feb 1 14:58:49 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Fri, 1 Feb 2013 14:58:49 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: <510af76f.e5e2440a.01e3.fffff162@mx.google.com> References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> Message-ID: On 31 Jan 2013, at 23:00, Jim Nelson wrote: > We've had an outstanding bug that resulted in some thumbnails not being regenerated, as well as a bug where video thumbnails were not being regenerated. These are fixed in master and will be available in 0.14. > > If you'd like to try the absolute latest of Shotwell, you can install it from our Daily Build PPA: https://launchpad.net/~yorba/+archive/daily-builds/ > > One other trick for forcing Shotwell to generate all your photo thumbnails (but not the videos): in the Library page (the first one when you run Shotwell), press F8 and press the far-left button on the Search bar; this will display only photos. Then press Ctrl+A and Ctrl+R. This will rotate all the photos, generating new thumbnails along the way. When it's finished, press Ctrl+Z. This will revert the rotation and generate thumbnails again. > > Convoluted, but a simple trick until 0.14 is released. Or, as I mentioned, please consider running our Daily Build version and see if that fixes it. Further to my last message, the select all, rotate and undo didn't work for me. I think I may have to cut my losses and try a different angle on this. What I'm proposing is: 1. Clear the library in my (Parallels) version of Shotwell altogether. 2. Copy across the database and thumbnails from the old computer. 3. Work out how to change the references in the database so that the full paths to the files match the new computers file structure, not the old. I've done a bit of work in MySQL, so I think I might be able to cope with this. Is this a feasible route? Michael > > > -- Jim > > On Thu, Jan 31, 2013 at 9:02 AM, Michael Hendry wrote: >> >> On 30 Jan 2013, at 20:02, Jim Nelson wrote: >> >> > A long, long time ago Yorba ported Shotwell to OSX and Windows. The Windows version was crippled but functional. The OSX version was in worse shape; I wouldn't even call it usable. We felt there was little demand for Shotwell outside of the GNOME desktop and abandoned the ports. My current estimate is that it would be quite an undertaking to port Shotwell today (which is a much larger program now). >> > >> > Shotwell doesn't write metadata to any RAW files today. Exiv2, the photo metadata it relies on, does support writing to NEF (as well as a handful of other RAW formats), and it's something we hope to offer in the future: http://redmine.yorba.org/issues/2622 >> > >> > As far as migrating Shotwell into your new machine, yes, you can copy the database and thumbnails as you've mentioned. You'll need to copy the photo files into their exact location. If they're stored in your home directory, that means your home directory name must be exactly the same. >> >> Thanks, Jim. >> >> I really need to have access to my photos in the Mac's file system, and before you sent this email I'd already copied them all across into my Mac in the same subdirectories as before - in /Users/michaelhendry/Pictures/Shotwell Library. >> >> I had already copied the database across, but not the thumbnails (I know, I should have waited for your advice!!), and I opened Shotwell in the Ubuntu virtual machine and asked it to "Import from Folder" - pointing it to the folder above. This proceeded as expected, and eventually all my images were available on my Mac, through Shotwell, with tags and Events intact. >> >> At this stage I noticed that not all of the thumbnails were present, but there appeared to be a background process going on, which was gradually re-creating them. >> >> Unfortunately, this appears to have ceased, with 5423 entries in each of thumbs128 and thumbs360. >> >> Is there some way of getting the thumbnail creation to start up again, or should I empty the shotwell library, copy the thumbnails across from my Ubuntu machine, and start the process of Importation again? >> >> Michael >> >> >> > >> > -- Jim >> > >> > On Wed, Jan 30, 2013 at 7:50 AM, Joseph Bylund wrote: >> > So I understand from the list that shotwell has at times in the past worked on OSX, how much of an undertaking would it be to get it working on OSX again (with possibly a restricted set of abilities)? >> > -Joe >> > _______________________________________________ >> > 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 avkaplmkt at gmail.com Fri Feb 1 21:41:36 2013 From: avkaplmkt at gmail.com (Advrk Aplmrkt) Date: Fri, 1 Feb 2013 16:41:36 -0500 Subject: [Shotwell] Shotwell hangs when upgrading library after 0.13.1 update Message-ID: Hello, I've recently updated Shotwell in my Fedora 18 (LXDE spin) to 0.13.1 from0.12, there are about 2000+ images in my Shotwell library. When opening Shotwell, I see a progress bar that says: "Updating library...", with a bar that moves back and forth within it. However, even after many hours (including overnight), the bar keeps moving with no end in sight, and eventually the Shotwell will just hang and I have to force quit it. This is a big problem as it prevents me from effectively accessing and using my entire photo library! How can I troubleshoot this issue? Thanks for your help. From michelinux at soccio.it Fri Feb 1 22:43:18 2013 From: michelinux at soccio.it (Michele) Date: Fri, 01 Feb 2013 23:43:18 +0100 Subject: [Shotwell] Shotwell not starting unless '--no-startup-progress' option is specified Message-ID: <510C4506.9010701@soccio.it> Hello everybody, I have facing the following problem: Shotwell is apparently not starting unless I start it from the terminal using 'shotwell --no-startup-progress'. If no option is specified, the 'Loading Shotwell' window stays stuck around 50% forever and eating 100% CPU (I tried leaving it there for a hour before killing it). Of course this didn't just suddenly started. I have installed a faster drive on my computer and reinstalled my system, and moved my home folder to the new drive. However I have left part of the photos on the old drive, making symbolic links to 'left behind' folders. My 'Pictures folder', the one that Shotwell point at, is now: 2011->/extra/michele/Pictures/Camera/2011 2012->/extra/michele/Pictures/Camera/2012 2013 where '/extra' is the mount point of my old home folder and '2013' is the only folder that I have moved on the new disk for the moment. I have perfectly replicated the folders structure in my new home. And when I start with 'shotwell --no-startup-progress' all the photos are there, all the albums are there and Shotwell works as magnificently as always. Shortly: $ shotwell -->> 'Loading window' stuck, CPU at 100%, Shotwell has apparently no intention to start $ shotwell --no-startup-progress -->> Shotwell starts in seconds and everything seems fine. I'm running Ubuntu 12.10 64bit, Shotwell is updated from the Yorba's PPA. Any idea, please? Any way to see what Shotwell is really doing during the load window? (is there any '--verbose' option?) Thank you, Michele From hendry.michael at gmail.com Fri Feb 1 23:03:18 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Fri, 1 Feb 2013 23:03:18 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> Message-ID: <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> On 1 Feb 2013, at 14:58, Michael Hendry wrote: > > On 31 Jan 2013, at 23:00, Jim Nelson wrote: > >> We've had an outstanding bug that resulted in some thumbnails not being regenerated, as well as a bug where video thumbnails were not being regenerated. These are fixed in master and will be available in 0.14. >> >> If you'd like to try the absolute latest of Shotwell, you can install it from our Daily Build PPA: https://launchpad.net/~yorba/+archive/daily-builds/ >> >> One other trick for forcing Shotwell to generate all your photo thumbnails (but not the videos): in the Library page (the first one when you run Shotwell), press F8 and press the far-left button on the Search bar; this will display only photos. Then press Ctrl+A and Ctrl+R. This will rotate all the photos, generating new thumbnails along the way. When it's finished, press Ctrl+Z. This will revert the rotation and generate thumbnails again. >> >> Convoluted, but a simple trick until 0.14 is released. Or, as I mentioned, please consider running our Daily Build version and see if that fixes it. > > Further to my last message, the select all, rotate and undo didn't work for me. > > I think I may have to cut my losses and try a different angle on this. > > What I'm proposing is: > > 1. Clear the library in my (Parallels) version of Shotwell altogether. > 2. Copy across the database and thumbnails from the old computer. > 3. Work out how to change the references in the database so that the full paths to the files match the new computers file structure, not the old. > > I've done a bit of work in MySQL, so I think I might be able to cope with this. > > Is this a feasible route? > > Michael And the answer is: Yes! 1. Is unnecessary. 2. Proceeded without trouble. I overwrote all the files in the .shotwell directory with their counterparts from the source computer. 3. Required me to install sqlite on the destination computer. Opening the database in sqlite, I found that the table "PhotoTable" has a column "filename" which contains the absolute path to the file which needs to be changed to suit the destination computer. Fortunately, there is a simple SQL statement which does this: update PhotoTable set filename = replace(filename, '/home/michael/Pictures/', '/home/parallels/Desktop/Parallels Shared Folders/Home/Pictures/Shotwell LIbrary/') I confess that I had my fingers crossed when I powered up Shotwell after doing this, but all appears to be working correctly. All I need to do now is find out how to set up the external editor links so that the Mac copies of GIMP and UFRAW are used. Oh, and keep an eye open for the aspects of the conversion I've been too ignorant to spot? Michael From clinton at yorba.org Fri Feb 1 23:35:31 2013 From: clinton at yorba.org (Clint Rogers) Date: Fri, 1 Feb 2013 15:35:31 -0800 Subject: [Shotwell] Shotwell hangs when upgrading library after 0.13.1 update In-Reply-To: References: Message-ID: Hi Advrk, My name is Clint, and I'm one of the developers working on Shotwell. On behalf of the team, I'm sorry you're running into this. Here are some things that might help determine what's happening here: 1) If you run Shotwell from the command line like so: shotwell --no-runtime-monitoring ...what happens? 2) In the directory ~/.cache/shotwell, there should be a file named shotwell.log, and in ~/.local/share/shotwell, there should be a file named shotwell.db; if you feel comfortable doing so, could you please mail them to the Yorba staff directly at shotwell at yorba.org? (They'll be treated as sensitive and confidential.) 3) Between the time you last ran 0.12, and the time you updated to 0.13.1, did you manually add any images to your library directory? I suspect that knowing the answers to these might shed some light on what's happening. Again, I apologize for the inconvenience; if you have any further questions or have further info on how to trigger this bug, please let us know. Cheers, -c On 01/02/2013, Advrk Aplmrkt wrote: > Hello, > > I've recently updated Shotwell in my Fedora 18 (LXDE spin) to 0.13.1 > from0.12, there are about 2000+ images in my Shotwell library. > > When opening Shotwell, I see a progress bar that says: "Updating > library...", with a bar that moves back and forth within it. However, > even after many hours (including overnight), the bar keeps moving with > no end in sight, and eventually the Shotwell will just hang and I have > to force quit it. > > This is a big problem as it prevents me from effectively accessing and > using my entire photo library! How can I troubleshoot this issue? > Thanks for your help. > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -- public struct Box { public static const int HAND_GRENADES = 12; -- from shotwell/src/Box.vala From valentin at sanva.net Sat Feb 2 00:56:22 2013 From: valentin at sanva.net (=?ISO-8859-1?Q?Valent=EDn?=) Date: Sat, 2 Feb 2013 01:56:22 +0100 Subject: [Shotwell] faces branch and merging/rebasing In-Reply-To: <20130124033511.GA3970@gamma.logic.tuwien.ac.at> References: <20130123233852.GD24310@gamma.logic.tuwien.ac.at> <20130124012935.GG24310@gamma.logic.tuwien.ac.at> <20130124033511.GA3970@gamma.logic.tuwien.ac.at> Message-ID: Hi all, Norbert, may be this [1] the thing that you was asking for? ?I've committed one correction in your name, I hope you are OK with that (you can see it as last commit). Cheers! [1] https://github.com/Sanva/shotwell-gsoc/tree/faces-tool-dirty 2013/1/24 Norbert Preining > Hi Lucas, > > hmmm ... > > On Mi, 23 Jan 2013, Lucas Beeler wrote: > > So I can merge all the changes from master into faces without incident. > > Indeed, > the first time I tried it wasn't working and tried to remerge > the whole changes as before. > Now I trashed my faces branch and made a re-checkout and did a test > commit to master and merged it, and it worked. > > Still the history is not nice because of the huge commit > that actually contains all the changes from master in one commit. > > Anyway, not my problem ;-) > > Ok, sorry for the noise ... > > Norbert > > ------------------------------------------------------------------------ > PREINING, Norbert http://www.preining.info > JAIST, Japan TeX Live & Debian Developer > DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 > ------------------------------------------------------------------------ > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From golinuxgo at gmail.com Sat Feb 2 04:59:27 2013 From: golinuxgo at gmail.com (go linux) Date: Fri, 1 Feb 2013 22:59:27 -0600 Subject: [Shotwell] Shotwell no longer working on squeeze In-Reply-To: References: <20130124061234.GD6008@gamma.logic.tuwien.ac.at> <20130125035658.GA32110@gamma.logic.tuwien.ac.at> <5106de70.e958420a.1021.ffffdd15@mx.google.com> <5107055b.cade440a.4fb6.ffffe339@mx.google.com> Message-ID: I previously described the "memory map" view of processes in the gnome-system-monitor. I did some research and now know that it is pmap that reports the memory map of a process by PID with the # pmap -d PID command. I have attached the output of that command (over 400 lines) for the rhythmbox PID (2916). There are MTP associations and possibly some others in there that are related to the issue I was having. It's more info than I can take in at the moment. Hopefully you can make some use of it. -------------- next part -------------- # pmap -d 2916 2916: rhythmbox --sm-client-id 1049d7261a503b771e135605773974937700000194310118 Address Kbytes Mode Offset Device Mapping 08048000 24 r-x-- 0000000000000000 008:00001 rhythmbox 0804e000 4 rw--- 0000000000006000 008:00001 rhythmbox 08234000 9156 rw--- 0000000000000000 000:00000 [ anon ] ac1ff000 4 ----- 0000000000000000 000:00000 [ anon ] ac200000 8192 rw--- 0000000000000000 000:00000 [ anon ] aca00000 248 rw--- 0000000000000000 000:00000 [ anon ] aca3e000 776 ----- 0000000000000000 000:00000 [ anon ] acb79000 384 rw-s- 0000000000000000 000:00004 [ shmid=0x14000b ] acbd9000 4 ----- 0000000000000000 000:00000 [ anon ] acbda000 8192 rw--- 0000000000000000 000:00000 [ anon ] ad3da000 4 ----- 0000000000000000 000:00000 [ anon ] ad3db000 8192 rw--- 0000000000000000 000:00000 [ anon ] adbdb000 6564 r---- 0000000000000000 008:00001 icon-theme.cache ae244000 48536 r---- 0000000000000000 008:00001 icon-theme.cache b11aa000 136 r-x-- 0000000000000000 008:00001 libbrasero-media.so.0.2.0 b11cc000 4 rw--- 0000000000021000 008:00001 libbrasero-media.so.0.2.0 b11e0000 16 r-x-- 0000000000000000 008:00001 libcd-recorder.so b11e4000 4 rw--- 0000000000003000 008:00001 libcd-recorder.so b11e5000 116 r-x-- 0000000000000000 008:00001 libdaap.so b1202000 8 rw--- 000000000001c000 008:00001 libdaap.so b1204000 32 rw--- 0000000000000000 000:00000 [ anon ] b120c000 24 r-x-- 0000000000000000 008:00001 libusb-0.1.so.4.4.4 b1212000 8 rw--- 0000000000005000 008:00001 libusb-0.1.so.4.4.4 b1214000 204 r-x-- 0000000000000000 008:00001 libmtp.so.8.3.3 b1247000 24 rw--- 0000000000032000 008:00001 libmtp.so.8.3.3 b124e000 68 r-x-- 0000000000000000 008:00001 libaudioscrobbler.so b125f000 4 rw--- 0000000000011000 008:00001 libaudioscrobbler.so b1260000 16 r-x-- 0000000000000000 008:00001 libusbmuxd.so.1.0.4 b1264000 4 rw--- 0000000000003000 008:00001 libusbmuxd.so.1.0.4 b1265000 80 r-x-- 0000000000000000 008:00001 libimobiledevice.so.1.0.2 b1279000 4 rw--- 0000000000013000 008:00001 libimobiledevice.so.1.0.2 b127a000 400 r-x-- 0000000000000000 008:00001 libgpod.so.4.2.0 b12de000 16 rw--- 0000000000063000 008:00001 libgpod.so.4.2.0 b12e2000 4 rw--- 0000000000000000 000:00000 [ anon ] b12e5000 64 r-x-- 0000000000000000 008:00001 libmtpdevice.so b12f5000 4 rw--- 000000000000f000 008:00001 libmtpdevice.so b12f6000 64 r-x-- 0000000000000000 008:00001 libipod.so b1306000 4 rw--- 000000000000f000 008:00001 libipod.so b1307000 64 r-x-- 0000000000000000 008:00001 libbz2.so.1.0.4 b1317000 4 rw--- 0000000000010000 008:00001 libbz2.so.1.0.4 b1318000 204 r-x-- 0000000000000000 008:00001 libcroco-0.6.so.3.0.1 b134b000 12 rw--- 0000000000032000 008:00001 libcroco-0.6.so.3.0.1 b134e000 212 r-x-- 0000000000000000 008:00001 libgsf-1.so.114.0.18 b1383000 12 rw--- 0000000000034000 008:00001 libgsf-1.so.114.0.18 b1386000 4 rw--- 0000000000000000 000:00000 [ anon ] b1387000 200 r-x-- 0000000000000000 008:00001 librsvg-2.so.2.26.3 b13b9000 4 rw--- 0000000000031000 008:00001 librsvg-2.so.2.26.3 b13bc000 28 r-x-- 0000000000000000 008:00001 libplist.so.1.1.3 b13c3000 4 rw--- 0000000000006000 008:00001 libplist.so.1.1.3 b13c4000 32 r-x-- 0000000000000000 008:00001 libstatus-icon.so b13cc000 4 rw--- 0000000000008000 008:00001 libstatus-icon.so b13cd000 44 r-x-- 0000000000000000 008:00001 libgeneric-player.so b13d8000 4 rw--- 000000000000b000 008:00001 libgeneric-player.so b13d9000 32 r-x-- 0000000000000000 008:00001 gnomekeyring.so b13e1000 4 rw--- 0000000000008000 008:00001 gnomekeyring.so b13e2000 116 r-x-- 0000000000000000 008:00001 libgcc_s.so.1 b13ff000 4 rw--- 000000000001c000 008:00001 libgcc_s.so.1 b1400000 932 r-x-- 0000000000000000 008:00001 libstdc++.so.6.0.13 b14e9000 16 r---- 00000000000e9000 008:00001 libstdc++.so.6.0.13 b14ed000 4 rw--- 00000000000ed000 008:00001 libstdc++.so.6.0.13 b14ee000 28 rw--- 0000000000000000 000:00000 [ anon ] b14f5000 160 r-x-- 0000000000000000 008:00001 libmusicbrainz.so.4.0.3 b151d000 4 rw--- 0000000000027000 008:00001 libmusicbrainz.so.4.0.3 b151e000 104 r-x-- 0000000000000000 008:00001 libgsttag-0.10.so.0.21.0 b1538000 4 rw--- 000000000001a000 008:00001 libgsttag-0.10.so.0.21.0 b153c000 4 r-x-- 0000000000000000 008:00001 svg_loader.so b153d000 4 rw--- 0000000000000000 008:00001 svg_loader.so b153e000 52 r-x-- 0000000000000000 008:00001 libvisualizer.so b154b000 4 rw--- 000000000000c000 008:00001 libvisualizer.so b154c000 60 r-x-- 0000000000000000 008:00001 libaudiocd.so b155b000 4 rw--- 000000000000f000 008:00001 libaudiocd.so b155c000 784 r-x-- 0000000000000000 008:00001 libasound.so.2.0.0 b1620000 16 rw--- 00000000000c4000 008:00001 libasound.so.2.0.0 b1624000 60 r-x-- 0000000000000000 008:00001 libavahi-client.so.3.2.7 b1633000 4 rw--- 000000000000e000 008:00001 libavahi-client.so.3.2.7 b1634000 44 r-x-- 0000000000000000 008:00001 libavahi-common.so.3.5.2 b163f000 4 rw--- 000000000000a000 008:00001 libavahi-common.so.3.5.2 b1640000 16 r-x-- 0000000000000000 008:00001 libORBitCosNaming-2.so.0.1.0 b1644000 4 rw--- 0000000000003000 008:00001 libORBitCosNaming-2.so.0.1.0 b1645000 128 r-x-- 0000000000000000 008:00001 libaudiofile.so.0.0.2 b1665000 12 rw--- 0000000000020000 008:00001 libaudiofile.so.0.0.2 b1668000 36 r-x-- 0000000000000000 008:00001 libesd.so.0.2.39 b1671000 4 rw--- 0000000000009000 008:00001 libesd.so.0.2.39 b1672000 356 r-x-- 0000000000000000 008:00001 libgnomevfs-2.so.0.2400.3 b16cb000 12 rw--- 0000000000058000 008:00001 libgnomevfs-2.so.0.2400.3 b16ce000 76 r-x-- 0000000000000000 008:00001 libbonobo-activation.so.4.0.0 b16e1000 8 rw--- 0000000000013000 008:00001 libbonobo-activation.so.4.0.0 b16e3000 344 r-x-- 0000000000000000 008:00001 libbonobo-2.so.0.0.0 b1739000 40 rw--- 0000000000055000 008:00001 libbonobo-2.so.0.0.0 b1743000 40 r-x-- 0000000000000000 008:00001 libpopt.so.0.0.0 b174d000 4 rw--- 0000000000009000 008:00001 libpopt.so.0.0.0 b174e000 80 r-x-- 0000000000000000 008:00001 libgnome-2.so.0.3000.0 b1762000 4 rw--- 0000000000014000 008:00001 libgnome-2.so.0.3000.0 b1763000 32 r-x-- 0000000000000000 008:00001 libgstcdda-0.10.so.0.21.0 b176b000 4 rw--- 0000000000008000 008:00001 libgstcdda-0.10.so.0.21.0 b176c000 36 r-x-- 0000000000000000 008:00001 libiradio.so b1775000 4 rw--- 0000000000008000 008:00001 libiradio.so b1776000 32 r-x-- 0000000000000000 008:00001 _gnome.so b177e000 4 rw--- 0000000000008000 008:00001 _gnome.so b177f000 52 r-x-- 0000000000000000 008:00001 gconf.so b178c000 8 rw--- 000000000000d000 008:00001 gconf.so b178e000 60 r-x-- 0000000000000000 008:00001 datetime.so b179d000 12 rw--- 000000000000e000 008:00001 datetime.so b17a0000 24 r-x-- 0000000000000000 008:00001 libgstnet-0.10.so.0.26.0 b17a6000 4 rw--- 0000000000005000 008:00001 libgstnet-0.10.so.0.26.0 b17a7000 12 r-x-- 0000000000000000 008:00001 libmmkeys.so b17aa000 4 rw--- 0000000000002000 008:00001 libmmkeys.so b17ab000 52 r-x-- 0000000000000000 008:00001 interfaces.so b17b8000 8 rw--- 000000000000d000 008:00001 interfaces.so b17ba000 432 r-x-- 0000000000000000 008:00001 _gst.so b1826000 40 rw--- 000000000006c000 008:00001 _gst.so b1830000 256 r-x-- 0000000000000000 008:00001 libxml2mod.so b1870000 20 rw--- 0000000000040000 008:00001 libxml2mod.so b1875000 204 r-x-- 0000000000000000 008:00001 atk.so b18a8000 16 rw--- 0000000000033000 008:00001 atk.so b18ac000 108 r-x-- 0000000000000000 008:00001 pango.so b18c7000 16 rw--- 000000000001b000 008:00001 pango.so b18cb000 388 rw--- 0000000000000000 000:00000 [ anon ] b192c000 264 r-x-- 0000000000000000 008:00001 _gio.so b196e000 32 rw--- 0000000000041000 008:00001 _gio.so b1976000 68 r-x-- 0000000000000000 008:00001 _cairo.so b1987000 12 rw--- 0000000000010000 008:00001 _cairo.so b198a000 1848 r-x-- 0000000000000000 008:00001 _gtk.so b1b58000 172 rw--- 00000000001cd000 008:00001 _gtk.so b1b83000 112 r-x-- 0000000000000000 008:00001 _gobject.so b1b9f000 8 rw--- 000000000001c000 008:00001 _gobject.so b1ba1000 260 rw--- 0000000000000000 000:00000 [ anon ] b1be2000 20 r-x-- 0000000000000000 008:00001 libffi.so.5.0.10 b1be7000 4 rw--- 0000000000005000 008:00001 libffi.so.5.0.10 b1be8000 12 r-x-- 0000000000000000 008:00001 libpyglib-2.0-python2.6.so.0.0.0 b1beb000 4 rw--- 0000000000002000 008:00001 libpyglib-2.0-python2.6.so.0.0.0 b1bed000 8 r-x-- 0000000000000000 008:00001 libavahi-glib.so.1.0.2 b1bef000 4 rw--- 0000000000001000 008:00001 libavahi-glib.so.1.0.2 b1bf0000 16 r-x-- 0000000000000000 008:00001 libgstdataprotocol-0.10.so.0.26.0 b1bf4000 4 rw--- 0000000000003000 008:00001 libgstdataprotocol-0.10.so.0.26.0 b1bf5000 12 r-x-- 0000000000000000 008:00001 pangocairo.so b1bf8000 4 rw--- 0000000000003000 008:00001 pangocairo.so b1bf9000 20 r-x-- 0000000000000000 008:00001 unix.so b1bfe000 4 rw--- 0000000000004000 008:00001 unix.so b1bff000 52 r-x-- 0000000000000000 008:00001 _glib.so b1c0c000 8 rw--- 000000000000c000 008:00001 _glib.so b1c0e000 520 rw--- 0000000000000000 000:00000 [ anon ] b1c90000 28 r--s- 0000000000000000 008:00001 gconv-modules.cache b1c97000 260 rw--- 0000000000000000 000:00000 [ anon ] b1cd8000 4 ----- 0000000000000000 000:00000 [ anon ] b1cd9000 8192 rw--- 0000000000000000 000:00000 [ anon ] b24d9000 516 r---- 0000000000000000 008:00001 DejaVuSans-Oblique.ttf b255a000 16 r-x-- 0000000000000000 008:00001 libpixbufloader-png.so b255e000 4 rw--- 0000000000003000 008:00001 libpixbufloader-png.so b255f000 100 r--s- 0000000000000000 008:00001 mime.cache b2578000 620 r---- 0000000000000000 008:00001 DejaVuSans.ttf b2613000 8 r-x-- 0000000000000000 008:00001 pango-basic-fc.so b2615000 4 rw--- 0000000000001000 008:00001 pango-basic-fc.so b2616000 4 r--s- 0000000000000000 008:00001 c05880de57d1f5e948fdfacc138775d9-le32d4.cache-3 b2617000 24 r--s- 0000000000000000 008:00001 945677eb7aeaf62f1d50efc3fb3ec7d8-le32d4.cache-3 b261d000 8 r--s- 0000000000000000 008:00001 ea47318ec9849e1a71e80a5d69d13859-le32d4.cache-3 b261f000 4 r--s- 0000000000000000 008:00001 e3fa16a14183b06aa45b3e009278fd14-le32d4.cache-3 b2620000 8 r--s- 0000000000000000 008:00001 b5ea634b0fb353b8ea17632d1f9ef766-le32d4.cache-3 b2622000 12 r--s- 0000000000000000 008:00001 6eb3985aa4124903f6ff08ba781cd364-le32d4.cache-3 b2625000 28 r--s- 0000000000000000 008:00001 6d41288fd70b0be22e8c3a91e032eec0-le32d4.cache-3 b262c000 4 r--s- 0000000000000000 008:00001 4794a0821666d79190d59a36cb4f44b5-le32d4.cache-3 b262d000 32 r--s- 0000000000000000 008:00001 d52a8644073d54c13679302ca1180695-le32d4.cache-3 b2635000 32 r--s- 0000000000000000 008:00001 e13b20fdb08344e0e664864cc2ede53d-le32d4.cache-3 b263d000 48 r--s- 0000000000000000 008:00002 2f0bc16259d5f2b9cff6e9239caef83f-le32d4.cache-3 b2649000 12 r--s- 0000000000000000 008:00002 0371e413d47d0dc1b2c9db6c577d1651-le32d4.cache-3 b264c000 232 r--s- 0000000000000000 008:00002 9a9b3fcca645efb2e47d0ad13e0f081a-le32d4.cache-3 b2686000 68 r-x-- 0000000000000000 008:00001 libgioremote-volume-monitor.so b2697000 4 rw--- 0000000000011000 008:00001 libgioremote-volume-monitor.so b2698000 84 r-x-- 0000000000000000 008:00001 libgvfscommon.so b26ad000 4 rw--- 0000000000014000 008:00001 libgvfscommon.so b26ae000 144 r-x-- 0000000000000000 008:00001 libgvfsdbus.so b26d2000 4 rw--- 0000000000024000 008:00001 libgvfsdbus.so b26d3000 6564 r---- 0000000000000000 008:00001 icon-theme.cache b2d3c000 48536 r---- 0000000000000000 008:00001 icon-theme.cache b5ca2000 124 r---- 0000000000000000 008:00001 icon-theme.cache b5cc1000 28 r-x-- 0000000000000000 008:00001 libltdl.so.7.2.1 b5cc8000 4 rw--- 0000000000007000 008:00001 libltdl.so.7.2.1 b5cc9000 52 r-x-- 0000000000000000 008:00001 libtdb.so.1.2.1 b5cd6000 4 rw--- 000000000000c000 008:00001 libtdb.so.1.2.1 b5cd7000 20 r-x-- 0000000000000000 008:00001 libogg.so.0.7.0 b5cdc000 4 rw--- 0000000000004000 008:00001 libogg.so.0.7.0 b5cdd000 156 r-x-- 0000000000000000 008:00001 libvorbis.so.0.4.4 b5d04000 4 rw--- 0000000000026000 008:00001 libvorbis.so.0.4.4 b5d05000 56 r-x-- 0000000000000000 008:00001 libcanberra.so.0.2.3 b5d13000 4 rw--- 000000000000e000 008:00001 libcanberra.so.0.2.3 b5d14000 4 r--s- 0000000000000000 008:00002 mime.cache b5d15000 68 r-x-- 0000000000000000 008:00001 libglide.so b5d26000 4 rw--- 0000000000010000 008:00001 libglide.so b5d27000 40 r-x-- 0000000000000000 008:00001 libnss_files-2.11.3.so b5d31000 4 r---- 0000000000009000 008:00001 libnss_files-2.11.3.so b5d32000 4 rw--- 000000000000a000 008:00001 libnss_files-2.11.3.so b5d33000 32 r-x-- 0000000000000000 008:00001 libnss_nis-2.11.3.so b5d3b000 4 r---- 0000000000008000 008:00001 libnss_nis-2.11.3.so b5d3c000 4 rw--- 0000000000009000 008:00001 libnss_nis-2.11.3.so b5d3d000 24 r-x-- 0000000000000000 008:00001 libnss_compat-2.11.3.so b5d43000 4 r---- 0000000000006000 008:00001 libnss_compat-2.11.3.so b5d44000 4 rw--- 0000000000007000 008:00001 libnss_compat-2.11.3.so b5d45000 1492 r---- 0000000000000000 008:00001 locale-archive b5eba000 16 rw--- 0000000000000000 000:00000 [ anon ] b5ebe000 12 r-x-- 0000000000000000 008:00001 libgpg-error.so.0.4.0 b5ec1000 4 rw--- 0000000000002000 008:00001 libgpg-error.so.0.4.0 b5ec2000 60 r-x-- 0000000000000000 008:00001 libtasn1.so.3.1.9 b5ed1000 4 rw--- 000000000000e000 008:00001 libtasn1.so.3.1.9 b5ed2000 16 r-x-- 0000000000000000 008:00001 libXdmcp.so.6.0.0 b5ed6000 4 rw--- 0000000000003000 008:00001 libXdmcp.so.6.0.0 b5ed7000 8 r-x-- 0000000000000000 008:00001 libXau.so.6.0.0 b5ed9000 4 rw--- 0000000000001000 008:00001 libXau.so.6.0.0 b5eda000 4 rw--- 0000000000000000 000:00000 [ anon ] b5edb000 76 r-x-- 0000000000000000 008:00001 libnsl-2.11.3.so b5eee000 4 r---- 0000000000012000 008:00001 libnsl-2.11.3.so b5eef000 4 rw--- 0000000000013000 008:00001 libnsl-2.11.3.so b5ef0000 8 rw--- 0000000000000000 000:00000 [ anon ] b5ef2000 48 r-x-- 0000000000000000 008:00001 libudev.so.0.9.3 b5efe000 4 r---- 000000000000c000 008:00001 libudev.so.0.9.3 b5eff000 4 rw--- 000000000000d000 008:00001 libudev.so.0.9.3 b5f00000 12 r-x-- 0000000000000000 008:00001 libuuid.so.1.3.0 b5f03000 4 rw--- 0000000000002000 008:00001 libuuid.so.1.3.0 b5f04000 1268 r-x-- 0000000000000000 008:00001 libcrypto.so.0.9.8 b6041000 96 rw--- 000000000013c000 008:00001 libcrypto.so.0.9.8 b6059000 12 rw--- 0000000000000000 000:00000 [ anon ] b605c000 280 r-x-- 0000000000000000 008:00001 libssl.so.0.9.8 b60a2000 16 rw--- 0000000000046000 008:00001 libssl.so.0.9.8 b60a6000 4 rw--- 0000000000000000 000:00000 [ anon ] b60a7000 100 r-x-- 0000000000000000 008:00001 libselinux.so.1 b60c0000 4 r---- 0000000000018000 008:00001 libselinux.so.1 b60c1000 4 rw--- 0000000000019000 008:00001 libselinux.so.1 b60c2000 64 r-x-- 0000000000000000 008:00001 libresolv-2.11.3.so b60d2000 4 r---- 0000000000010000 008:00001 libresolv-2.11.3.so b60d3000 4 rw--- 0000000000011000 008:00001 libresolv-2.11.3.so b60d4000 8 rw--- 0000000000000000 000:00000 [ anon ] b60d6000 200 r-x-- 0000000000000000 008:00001 libpcre.so.3.12.1 b6108000 4 rw--- 0000000000031000 008:00001 libpcre.so.3.12.1 b6109000 108 r-x-- 0000000000000000 008:00001 libgnome-keyring.so.0.1.1 b6124000 4 rw--- 000000000001a000 008:00001 libgnome-keyring.so.0.1.1 b6125000 4 rw--- 0000000000000000 000:00000 [ anon ] b6126000 620 r-x-- 0000000000000000 008:00001 libsqlite3.so.0.8.6 b61c1000 8 r---- 000000000009a000 008:00001 libsqlite3.so.0.8.6 b61c3000 4 rw--- 000000000009c000 008:00001 libsqlite3.so.0.8.6 b61c4000 4 rw--- 0000000000000000 000:00000 [ anon ] b61c5000 24 r-x-- 0000000000000000 008:00001 libproxy.so.0.0.0 b61cb000 4 rw--- 0000000000005000 008:00001 libproxy.so.0.0.0 b61cc000 452 r-x-- 0000000000000000 008:00001 libgcrypt.so.11.5.3 b623d000 12 rw--- 0000000000070000 008:00001 libgcrypt.so.11.5.3 b6240000 592 r-x-- 0000000000000000 008:00001 libgnutls.so.26.14.12 b62d4000 16 rw--- 0000000000093000 008:00001 libgnutls.so.26.14.12 b62d8000 144 r-x-- 0000000000000000 008:00001 libexpat.so.1.5.2 b62fc000 8 rw--- 0000000000024000 008:00001 libexpat.so.1.5.2 b62fe000 4 rw--- 0000000000000000 000:00000 [ anon ] b62ff000 96 r-x-- 0000000000000000 008:00001 libxcb.so.1.1.0 b6317000 4 rw--- 0000000000017000 008:00001 libxcb.so.1.1.0 b6318000 24 r-x-- 0000000000000000 008:00001 libxcb-render.so.0.0.0 b631e000 4 rw--- 0000000000005000 008:00001 libxcb-render.so.0.0.0 b631f000 8 r-x-- 0000000000000000 008:00001 libxcb-shm.so.0.0.0 b6321000 4 rw--- 0000000000001000 008:00001 libxcb-shm.so.0.0.0 b6322000 140 r-x-- 0000000000000000 008:00001 libpng12.so.0.44.0 b6345000 4 rw--- 0000000000022000 008:00001 libpng12.so.0.44.0 b6346000 524 r-x-- 0000000000000000 008:00001 libpixman-1.so.0.24.0 b63c9000 16 rw--- 0000000000082000 008:00001 libpixman-1.so.0.24.0 b63cd000 4 rw--- 0000000000000000 000:00000 [ anon ] b63ce000 32 r-x-- 0000000000000000 008:00001 libXcursor.so.1.0.2 b63d6000 4 rw--- 0000000000007000 008:00001 libXcursor.so.1.0.2 b63d7000 24 r-x-- 0000000000000000 008:00001 libXrandr.so.2.2.0 b63dd000 4 rw--- 0000000000005000 008:00001 libXrandr.so.2.2.0 b63de000 48 r-x-- 0000000000000000 008:00001 libXi.so.6.1.0 b63ea000 4 rw--- 000000000000c000 008:00001 libXi.so.6.1.0 b63eb000 8 r-x-- 0000000000000000 008:00001 libXinerama.so.1.0.0 b63ed000 4 rw--- 0000000000001000 008:00001 libXinerama.so.1.0.0 b63ee000 32 r-x-- 0000000000000000 008:00001 libXrender.so.1.3.0 b63f6000 4 rw--- 0000000000007000 008:00001 libXrender.so.1.3.0 b63f7000 4 rw--- 0000000000000000 000:00000 [ anon ] b63f8000 56 r-x-- 0000000000000000 008:00001 libXext.so.6.4.0 b6406000 4 rw--- 000000000000d000 008:00001 libXext.so.6.4.0 b6407000 16 r-x-- 0000000000000000 008:00001 libXfixes.so.3.1.0 b640b000 4 rw--- 0000000000003000 008:00001 libXfixes.so.3.1.0 b640c000 8 r-x-- 0000000000000000 008:00001 libXdamage.so.1.1.0 b640e000 4 rw--- 0000000000001000 008:00001 libXdamage.so.1.1.0 b640f000 8 r-x-- 0000000000000000 008:00001 libXcomposite.so.1.0.0 b6411000 4 rw--- 0000000000001000 008:00001 libXcomposite.so.1.0.0 b6412000 1124 r-x-- 0000000000000000 008:00001 libX11.so.6.3.0 b652b000 16 rw--- 0000000000118000 008:00001 libX11.so.6.3.0 b652f000 4 rw--- 0000000000000000 000:00000 [ anon ] b6530000 296 r-x-- 0000000000000000 008:00001 libORBit-2.so.0.1.0 b657a000 36 rw--- 000000000004a000 008:00001 libORBit-2.so.0.1.0 b6583000 4 rw--- 0000000000000000 000:00000 [ anon ] b6584000 272 r-x-- 0000000000000000 008:00001 libgmime-2.4.so.2.4.14 b65c8000 88 rw--- 0000000000044000 008:00001 libgmime-2.4.so.2.4.14 b65de000 8 r-x-- 0000000000000000 008:00001 libutil-2.11.3.so b65e0000 4 r---- 0000000000001000 008:00001 libutil-2.11.3.so b65e1000 4 rw--- 0000000000002000 008:00001 libutil-2.11.3.so b65e2000 8 r-x-- 0000000000000000 008:00001 libdl-2.11.3.so b65e4000 4 r---- 0000000000001000 008:00001 libdl-2.11.3.so b65e5000 4 rw--- 0000000000002000 008:00001 libdl-2.11.3.so b65e6000 156 r-x-- 0000000000000000 008:00001 libgstcontroller-0.10.so.0.26.0 b660d000 4 rw--- 0000000000026000 008:00001 libgstcontroller-0.10.so.0.26.0 b660e000 44 r-x-- 0000000000000000 008:00001 libgstpbutils-0.10.so.0.21.0 b6619000 4 rw--- 000000000000a000 008:00001 libgstpbutils-0.10.so.0.21.0 b661a000 4 rw--- 0000000000000000 000:00000 [ anon ] b661b000 24 r-x-- 0000000000000000 008:00001 libgudev-1.0.so.0.0.1 b6621000 4 r---- 0000000000006000 008:00001 libgudev-1.0.so.0.0.1 b6622000 4 rw--- 0000000000007000 008:00001 libgudev-1.0.so.0.0.1 b6623000 80 r-x-- 0000000000000000 008:00001 libICE.so.6.3.0 b6637000 8 rw--- 0000000000013000 008:00001 libICE.so.6.3.0 b6639000 4 rw--- 0000000000000000 000:00000 [ anon ] b663a000 28 r-x-- 0000000000000000 008:00001 libSM.so.6.0.1 b6641000 4 rw--- 0000000000006000 008:00001 libSM.so.6.0.1 b6642000 28 r-x-- 0000000000000000 008:00001 libnotify.so.1.2.3 b6649000 4 rw--- 0000000000006000 008:00001 libnotify.so.1.2.3 b664a000 1280 r-x-- 0000000000000000 008:00001 libc-2.11.3.so b678a000 4 ----- 0000000000140000 008:00001 libc-2.11.3.so b678b000 8 r---- 0000000000140000 008:00001 libc-2.11.3.so b678d000 4 rw--- 0000000000142000 008:00001 libc-2.11.3.so b678e000 16 rw--- 0000000000000000 000:00000 [ anon ] b6792000 76 r-x-- 0000000000000000 008:00001 libz.so.1.2.3.4 b67a5000 4 rw--- 0000000000013000 008:00001 libz.so.1.2.3.4 b67a6000 2020 r-x-- 0000000000000000 008:00001 libpython2.6.so.1.0 b699f000 320 rw--- 00000000001f9000 008:00001 libpython2.6.so.1.0 b69ef000 36 rw--- 0000000000000000 000:00000 [ anon ] b69f8000 800 r-x-- 0000000000000000 008:00001 libglib-2.0.so.0.2400.2 b6ac0000 4 rw--- 00000000000c8000 008:00001 libglib-2.0.so.0.2400.2 b6ac1000 28 r-x-- 0000000000000000 008:00001 librt-2.11.3.so b6ac8000 4 r---- 0000000000006000 008:00001 librt-2.11.3.so b6ac9000 4 rw--- 0000000000007000 008:00001 librt-2.11.3.so b6aca000 16 r-x-- 0000000000000000 008:00001 libgthread-2.0.so.0.2400.2 b6ace000 4 rw--- 0000000000003000 008:00001 libgthread-2.0.so.0.2400.2 b6acf000 4 rw--- 0000000000000000 000:00000 [ anon ] b6ad0000 244 r-x-- 0000000000000000 008:00001 libgobject-2.0.so.0.2400.2 b6b0d000 4 rw--- 000000000003d000 008:00001 libgobject-2.0.so.0.2400.2 b6b0e000 84 r-x-- 0000000000000000 008:00001 libpthread-2.11.3.so b6b23000 4 r---- 0000000000014000 008:00001 libpthread-2.11.3.so b6b24000 4 rw--- 0000000000015000 008:00001 libpthread-2.11.3.so b6b25000 8 rw--- 0000000000000000 000:00000 [ anon ] b6b27000 224 r-x-- 0000000000000000 008:00001 libdbus-1.so.3.4.0 b6b5f000 4 r---- 0000000000037000 008:00001 libdbus-1.so.3.4.0 b6b60000 4 rw--- 0000000000038000 008:00001 libdbus-1.so.3.4.0 b6b61000 120 r-x-- 0000000000000000 008:00001 libdbus-glib-1.so.2.1.0 b6b7f000 4 rw--- 000000000001d000 008:00001 libdbus-glib-1.so.2.1.0 b6b80000 56 r-x-- 0000000000000000 008:00001 libgstinterfaces-0.10.so.0.21.0 b6b8e000 4 rw--- 000000000000d000 008:00001 libgstinterfaces-0.10.so.0.21.0 b6b8f000 4 rw--- 0000000000000000 000:00000 [ anon ] b6b90000 1168 r-x-- 0000000000000000 008:00001 libxml2.so.2.7.8 b6cb4000 20 rw--- 0000000000124000 008:00001 libxml2.so.2.7.8 b6cb9000 4 rw--- 0000000000000000 000:00000 [ anon ] b6cba000 12 r-x-- 0000000000000000 008:00001 libgmodule-2.0.so.0.2400.2 b6cbd000 4 rw--- 0000000000002000 008:00001 libgmodule-2.0.so.0.2400.2 b6cbe000 780 r-x-- 0000000000000000 008:00001 libgstreamer-0.10.so.0.26.0 b6d81000 16 rw--- 00000000000c3000 008:00001 libgstreamer-0.10.so.0.26.0 b6d85000 4 rw--- 0000000000000000 000:00000 [ anon ] b6d86000 248 r-x-- 0000000000000000 008:00001 libgstbase-0.10.so.0.26.0 b6dc4000 4 rw--- 000000000003e000 008:00001 libgstbase-0.10.so.0.26.0 b6dc5000 616 r-x-- 0000000000000000 008:00001 libgio-2.0.so.0.2400.2 b6e5f000 8 rw--- 000000000009a000 008:00001 libgio-2.0.so.0.2400.2 b6e61000 4 rw--- 0000000000000000 000:00000 [ anon ] b6e62000 288 r-x-- 0000000000000000 008:00001 libsoup-2.4.so.1.3.0 b6eaa000 8 rw--- 0000000000047000 008:00001 libsoup-2.4.so.1.3.0 b6eac000 20 r-x-- 0000000000000000 008:00001 libsoup-gnome-2.4.so.1.3.0 b6eb1000 4 rw--- 0000000000004000 008:00001 libsoup-gnome-2.4.so.1.3.0 b6eb2000 180 r-x-- 0000000000000000 008:00001 libfontconfig.so.1.4.4 b6edf000 8 rw--- 000000000002c000 008:00001 libfontconfig.so.1.4.4 b6ee1000 464 r-x-- 0000000000000000 008:00001 libfreetype.so.6.6.0 b6f55000 16 rw--- 0000000000073000 008:00001 libfreetype.so.6.6.0 b6f59000 264 r-x-- 0000000000000000 008:00001 libpango-1.0.so.0.2800.3 b6f9b000 8 rw--- 0000000000041000 008:00001 libpango-1.0.so.0.2800.3 b6f9d000 4 rw--- 0000000000000000 000:00000 [ anon ] b6f9e000 704 r-x-- 0000000000000000 008:00001 libcairo.so.2.11000.2 b704e000 8 rw--- 00000000000b0000 008:00001 libcairo.so.2.11000.2 b7050000 8 rw--- 0000000000000000 000:00000 [ anon ] b7052000 40 r-x-- 0000000000000000 008:00001 libpangocairo-1.0.so.0.2800.3 b705c000 4 rw--- 000000000000a000 008:00001 libpangocairo-1.0.so.0.2800.3 b705d000 144 r-x-- 0000000000000000 008:00001 libm-2.11.3.so b7081000 4 r---- 0000000000023000 008:00001 libm-2.11.3.so b7082000 4 rw--- 0000000000024000 008:00001 libm-2.11.3.so b7083000 96 r-x-- 0000000000000000 008:00001 libgdk_pixbuf-2.0.so.0.2000.1 b709b000 4 rw--- 0000000000017000 008:00001 libgdk_pixbuf-2.0.so.0.2000.1 b709c000 148 r-x-- 0000000000000000 008:00001 libpangoft2-1.0.so.0.2800.3 b70c1000 4 rw--- 0000000000025000 008:00001 libpangoft2-1.0.so.0.2800.3 b70c2000 4 rw--- 0000000000000000 000:00000 [ anon ] b70c3000 104 r-x-- 0000000000000000 008:00001 libatk-1.0.so.0.3009.1 b70dd000 8 rw--- 0000000000019000 008:00001 libatk-1.0.so.0.3009.1 b70df000 588 r-x-- 0000000000000000 008:00001 libgdk-x11-2.0.so.0.2000.1 b7172000 12 rw--- 0000000000093000 008:00001 libgdk-x11-2.0.so.0.2000.1 b7175000 3900 r-x-- 0000000000000000 008:00001 libgtk-x11-2.0.so.0.2000.1 b7544000 24 rw--- 00000000003cf000 008:00001 libgtk-x11-2.0.so.0.2000.1 b754a000 4 rw--- 0000000000000000 000:00000 [ anon ] b754b000 192 r-x-- 0000000000000000 008:00001 libgconf-2.so.4.1.5 b757b000 12 rw--- 000000000002f000 008:00001 libgconf-2.so.4.1.5 b757e000 52 r-x-- 0000000000000000 008:00001 libgnome-media-profiles.so.0.0.0 b758b000 4 rw--- 000000000000c000 008:00001 libgnome-media-profiles.so.0.0.0 b758c000 4 rw--- 0000000000000000 000:00000 [ anon ] b758d000 96 r-x-- 0000000000000000 008:00001 libtotem-plparser.so.17.0.0 b75a5000 4 rw--- 0000000000018000 008:00001 libtotem-plparser.so.17.0.0 b75a6000 1152 r-x-- 0000000000000000 008:00001 librhythmbox-core.so.0.0.0 b76c6000 36 rw--- 0000000000120000 008:00001 librhythmbox-core.so.0.0.0 b76cf000 28 r-x-- 0000000000000000 008:00001 libvorbisfile.so.3.3.2 b76d6000 4 rw--- 0000000000006000 008:00001 libvorbisfile.so.3.3.2 b76d7000 16 r-x-- 0000000000000000 008:00001 libcanberra-gtk.so.0.1.6 b76db000 4 rw--- 0000000000003000 008:00001 libcanberra-gtk.so.0.1.6 b76dc000 20 r-x-- 0000000000000000 008:00001 libcanberra-gtk-module.so b76e1000 4 rw--- 0000000000004000 008:00001 libcanberra-gtk-module.so b76e2000 8 rw--- 0000000000000000 000:00000 [ anon ] b76e4000 4 r-x-- 0000000000000000 000:00000 [ anon ] b76e5000 108 r-x-- 0000000000000000 008:00001 ld-2.11.3.so b7700000 4 r---- 000000000001b000 008:00001 ld-2.11.3.so b7701000 4 rw--- 000000000001c000 008:00001 ld-2.11.3.so bfe81000 116 rw--- 0000000000000000 000:00000 [ stack ] mapped: 194060K writeable/private: 45752K shared: 964K From preining at logic.at Sat Feb 2 10:15:52 2013 From: preining at logic.at (Norbert Preining) Date: Sat, 2 Feb 2013 11:15:52 +0100 Subject: [Shotwell] Development tools In-Reply-To: References: Message-ID: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> I do vim and printf ;-) ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ On 2013/02/01, at 8:44, "Jens B." wrote: > Hi there, > > I am really new to vala so I'd ask you guys about your development process. > Right now I, like several people, printf alot to see whats going on, but > this can't be right. So my questions: > > What IDE do you use? How do you debug? How do you test? > > Thanks! > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From preining at logic.at Sat Feb 2 10:49:52 2013 From: preining at logic.at (Norbert Preining) Date: Sat, 2 Feb 2013 19:49:52 +0900 Subject: [Shotwell] FOSDEM Message-ID: <20130202104952.GA20148@gamma.logic.tuwien.ac.at> Hi Shotwell heros, anyone at FOSDEM? I am here till tomorrow afternoon? Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From preining at logic.at Sat Feb 2 10:50:34 2013 From: preining at logic.at (Norbert Preining) Date: Sat, 2 Feb 2013 19:50:34 +0900 Subject: [Shotwell] faces branch and merging/rebasing In-Reply-To: References: <20130123233852.GD24310@gamma.logic.tuwien.ac.at> <20130124012935.GG24310@gamma.logic.tuwien.ac.at> <20130124033511.GA3970@gamma.logic.tuwien.ac.at> Message-ID: <20130202105034.GB20148@gamma.logic.tuwien.ac.at> On Sa, 02 Feb 2013, Valent?n wrote: > Norbert, may be this [1] the thing that you was asking for? ?I've committed > one correction in your name, I hope you are OK with that (you can see it as > last commit). Thanks, that is fine ... I had no idea that this is possible ;-) Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From guerda at freenet.de Sat Feb 2 13:03:26 2013 From: guerda at freenet.de (=?UTF-8?B?UGhpbGlwIEdpbGxpw59lbg==?=) Date: Sat, 02 Feb 2013 14:03:26 +0100 Subject: [Shotwell] Shotwell on Nabble Message-ID: Hi folks! I'm frequently using Nabble for reading mailing list and as it seems, this list is also hosted on nabble.[1] Unfortunately, the nabble forum is not recent, since the last post is from four days ago. Does anybody have a clue, why is that and how this can be fixed? Kind regards, Philip [1] http://shotwell.996238.n3.nabble.com/ --- Alle Postf?cher an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/produkte/basic/index.html From martinyt at gmail.com Sat Feb 2 23:50:47 2013 From: martinyt at gmail.com (Martin Album Ytre-Eide) Date: Sun, 3 Feb 2013 00:50:47 +0100 Subject: [Shotwell] database malformed Message-ID: Hello all. My shotwell database is malformed and I can't find a solution for it. The problem is that a lot of pictures won't show up in shotwell (but videos do) no error message. I had a look at: http://askubuntu.com/questions/58295...ed-shotwell-db so I tried restoring the database (from photo.db.back) without any luck - it has the same issues. The pragma integrity_check gives: sqlite> pragma integrity_check; *** in database main *** Page 1090: btreeInitPage() returns error code 11 On tree page 996 cell 6: Child page depth differs On tree page 996 cell 7: Child page depth differs Page 29: btreeInitPage() returns error code 11 On tree page 27 cell 2: Child page depth differs On tree page 27 cell 3: Child page depth differs Error: database disk image is malformed I run ubuntu 12.10 and shotwell 0.13.1. I am missing about two year of photos in shotwell (I have the photos of course) Any ideas to fix this? I have also run a check on the disk's with sudo touch /forcefsck but I found no errors on the disk. I have had some problems with ffmpeg( did a apt-get remove and then install (I think)) and diskspace (I removed some old kernels), but I do not see how that could have anything to do with this..... Martin From schuetz.marc at gmx.de Sun Feb 3 12:51:32 2013 From: schuetz.marc at gmx.de (Marc) Date: Sun, 03 Feb 2013 13:51:32 +0100 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <5106cd87.8673440a.735f.ffffce82@mx.google.com> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> Message-ID: <510E5D54.8080802@gmx.de> Hi all, sorry for the late response. I've uploaded such an shotwell-thumbnail here http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ For me the workaround is now to create jpgs with imagemagick. I've tried to get information about the TIFFs via "Phatch Image Inspector" but it tells me "failure". GIMP and Eye of Gnome are displying the TIFF correct. Perhaps the problem is coming from Hugin, because the Source-Tiffs from Photoshop are displyaed correctly, only the Panoramas from Hugin not. If anyone has an tip for me how to get information about the Tiff would be very helpful. Cheers Marc Am 28.01.2013 20:12, schrieb Jim Nelson: > Hi Marc, > > Unfortunately our mailing list doesn't allow attachments. If they're > small enough, you can mail the photo(s) directly to shotwell at yorba.org. > If not, please make them available via a public download service. > > We don't have a ticket about the problem you're describing, so we'd be > interested in seeing this problem here. > > -- Jim > > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> HI, >> >> this is first time I have used my camera with AEB, then created HDRs >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> Panoramas with Hugin. >> The Problem after importing all into shotwell is that shotwell creates >> such thumbnail files with _shotwell.tif see attached. They are all black. >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. How >> could this fixed? >> >> Thanks >> Marc >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: From moejoeblue at gmail.com Sun Feb 3 18:52:00 2013 From: moejoeblue at gmail.com (Moe Blue) Date: Sun, 03 Feb 2013 19:52:00 +0100 Subject: [Shotwell] re-combine RAW+JPEG Message-ID: <510EB1D0.8040408@gmail.com> Hi, for the next version of shotwell, will there be any option to re-combine RAW+JPEG? I'm looking forward to shotwell 0.14 with the recent RAW fixes. I'm also trying the shotwell development ppa on a non production machine with a copy of my photo database. So far, things seem to improve, thanks a lot for taking up development again for this great photo management application! But my old photo database is a bit messed up. Often, RAW and JPEG are not properly paired. In some cases, the embedded JPEG has been extracted and been used instead of the Camera developed JPEG which was beside the RAW file. As for now, there does seem to be good handling for new imports from camera, while I cannot find a way to re-combine old RAW+JPEG pairs and get rid of the _embedded version. I really hope, there will be something to handle this old photos. I do not understand why shotwell uses the embedded version as development at all (except for the thumbnail). Best Moe From lucas at yorba.org Mon Feb 4 18:40:59 2013 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 4 Feb 2013 10:40:59 -0800 Subject: [Shotwell] re-combine RAW+JPEG In-Reply-To: <510EB1D0.8040408@gmail.com> References: <510EB1D0.8040408@gmail.com> Message-ID: Hi Moe, I can address two of your issues. First, The issue with the _embedded JPEG file being preferred to the sister JPEG in a RAW+JPEG pair has been addressed in several recent commits. Second, we do have an outstanding ticket to combine and separate RAW+JPEG pairs here: http://redmine.yorba.org/issues/4040. Would this give you most of the functionality you need? Cheers, Lucas On Sun, Feb 3, 2013 at 10:52 AM, Moe Blue wrote: > Hi, > > for the next version of shotwell, will there be any option to re-combine > RAW+JPEG? > > I'm looking forward to shotwell 0.14 with the recent RAW fixes. I'm also > trying the shotwell development ppa on a non production machine with a copy > of my photo database. So far, things seem to improve, thanks a lot for > taking up development again for this great photo management application! > > But my old photo database is a bit messed up. Often, RAW and JPEG are not > properly paired. In some cases, the embedded JPEG has been extracted and > been used instead of the Camera developed JPEG which was beside the RAW > file. As for now, there does seem to be good handling for new imports from > camera, while I cannot find a way to re-combine old RAW+JPEG pairs and get > rid of the _embedded version. > > I really hope, there will be something to handle this old photos. I do not > understand why shotwell uses the embedded version as development at all > (except for the thumbnail). > > Best > Moe > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Mon Feb 4 20:54:18 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 04 Feb 2013 20:46:18 -0008 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> Message-ID: <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> Great to hear! ?If it works, it works. We really would like to have a better export/import system for Shotwell to avoid this problem, but for now I'm glad you got this worked out. -- Jim On Fri, Feb 1, 2013 at 3:03 PM, Michael Hendry wrote: On 1 Feb 2013, at 14:58, Michael Hendry wrote: On 31 Jan 2013, at 23:00, Jim Nelson wrote: We've had an outstanding bug that resulted in some thumbnails not being regenerated, as well as a bug where video thumbnails were not being regenerated. ?These are fixed in master and will be available in 0.14. If you'd like to try the absolute latest of Shotwell, you can install it from our Daily Build PPA: https://launchpad.net/~yorba/+archive/daily-builds/ One other trick for forcing Shotwell to generate all your photo thumbnails (but not the videos): in the Library page (the first one when you run Shotwell), press F8 and press the far-left button on the Search bar; this will display only photos. ?Then press Ctrl+A and Ctrl+R. ?This will rotate all the photos, generating new thumbnails along the way. ?When it's finished, press Ctrl+Z. ?This will revert the rotation and generate thumbnails again. Convoluted, but a simple trick until 0.14 is released. ?Or, as I mentioned, please consider running our Daily Build version and see if that fixes it. Further to my last message, the select all, rotate and undo didn't work for me. I think I may have to cut my losses and try a different angle on this. What I'm proposing is: 1. Clear the library in my (Parallels) version of Shotwell altogether. 2. Copy across the database and thumbnails from the old computer. 3. Work out how to change the references in the database so that the full paths to the files match the new computers file structure, not the old. I've done a bit of work in MySQL, so I think I might be able to cope with this. Is this a feasible route? Michael And the answer is: Yes! 1. Is unnecessary. 2. Proceeded without trouble. I overwrote all the files in the .shotwell directory with their counterparts from the source computer. 3. Required me to install sqlite on the destination computer. Opening the database in sqlite, I found that the table "PhotoTable" has a column "filename" which contains the absolute path to the file which needs to be changed to suit the destination computer. Fortunately, there is a simple SQL statement which does this: update PhotoTable set filename = replace(filename, '/home/michael/Pictures/', '/home/parallels/Desktop/Parallels Shared Folders/Home/Pictures/Shotwell LIbrary/') I confess that I had my fingers crossed when I powered up Shotwell after doing this, but all appears to be working correctly. All I need to do now is find out how to set up the external editor links so that the Mac copies of GIMP and UFRAW are used. Oh, and keep an eye open for the aspects of the conversion I've been too ignorant to spot? Michael From jim at yorba.org Mon Feb 4 21:06:39 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 04 Feb 2013 20:58:39 -0008 Subject: [Shotwell] FOSDEM In-Reply-To: <20130202104952.GA20148@gamma.logic.tuwien.ac.at> References: <20130202104952.GA20148@gamma.logic.tuwien.ac.at> Message-ID: <511022e7.c5c5320a.738f.ffffbcb7@mx.google.com> Hi Norbert, Probably too late in any event, but no one from Yorba attended FOSDEM this year. ?We do plan on attending GUADEC later this year and we're often at UDS. ?If you plan on attending either of those, let us know! -- Jim On Sat, Feb 2, 2013 at 2:49 AM, Norbert Preining wrote: Hi Shotwell heros, anyone at FOSDEM? I am here till tomorrow afternoon? Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Mon Feb 4 22:59:25 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 04 Feb 2013 22:51:25 -0008 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <510E5D54.8080802@gmx.de> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> Message-ID: <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> Hi Marc, The link you sent us appears to display a JPEG, not TIFF. ?We would need to download the original TIFF in order to understand the problem. ?Is there any way you could make that available to us? -- Jim On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: Hi all, sorry for the late response. I've uploaded such an shotwell-thumbnail here http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ For me the workaround is now to create jpgs with imagemagick. I've tried to get information about the TIFFs via "Phatch Image Inspector" but it tells me "failure". GIMP and Eye of Gnome are displying the TIFF correct. Perhaps the problem is coming from Hugin, because the Source-Tiffs from Photoshop are displyaed correctly, only the Panoramas from Hugin not. If anyone has an tip for me how to get information about the Tiff would be very helpful. Cheers Marc Am 28.01.2013 20:12, schrieb Jim Nelson: > Hi Marc, > > Unfortunately our mailing list doesn't allow attachments. If they're > small enough, you can mail the photo(s) directly to shotwell at yorba.org. > If not, please make them available via a public download service. > > We don't have a ticket about the problem you're describing, so we'd be > interested in seeing this problem here. > > -- Jim > > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> HI, >> >> this is first time I have used my camera with AEB, then created HDRs >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> Panoramas with Hugin. >> The Problem after importing all into shotwell is that shotwell creates >> such thumbnail files with _shotwell.tif see attached. They are all black. >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. How >> could this fixed? >> >> Thanks >> Marc >> > From preining at logic.at Mon Feb 4 23:30:25 2013 From: preining at logic.at (Norbert Preining) Date: Tue, 5 Feb 2013 08:30:25 +0900 Subject: [Shotwell] FOSDEM In-Reply-To: <511022e7.c5c5320a.738f.ffffbcb7@mx.google.com> References: <20130202104952.GA20148@gamma.logic.tuwien.ac.at> <511022e7.c5c5320a.738f.ffffbcb7@mx.google.com> Message-ID: <20130204233025.GC28015@gamma.logic.tuwien.ac.at> Hi Jim, On Mo, 04 Feb 2013, Jim Nelson wrote: > Probably too late in any event, but no one from Yorba attended FOSDEM this year. ?We do plan on attending GUADEC later this year and we're often at UDS. ?If you plan on attending either of those, let us know! Thanks, I was there the two days, gave a talk about how to distribute TeX Live, and now I am in Wales for scientific work. Normally I cannot afford going from Japan over to Europe for these conferences, unless it is just on the way to a normal business trip. Bottomine, I will probably not attend any of those. See you around Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From jim at yorba.org Mon Feb 4 23:44:45 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 04 Feb 2013 23:36:45 -0008 Subject: [Shotwell] Development tools In-Reply-To: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> References: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> Message-ID: <511047f5.cb0d320a.75ad.05b2@mx.google.com> Let me point you to Valencia, a gedit plugin developed by Yorba specifically for Vala development: http://redmine.yorba.org/projects/valencia/wiki As fas as debugging, I recommend debug() over printf(), as it will display the filename and line number as well as your message. ?For more serious debug work I use gdb. -- Jim On Sat, Feb 2, 2013 at 2:15 AM, Norbert Preining wrote: I do vim and printf ;-) ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ On 2013/02/01, at 8:44, "Jens B." wrote: > Hi there, > > I am really new to vala so I'd ask you guys about your development process. > Right now I, like several people, printf alot to see whats going on, but > this can't be right. So my questions: > > What IDE do you use? How do you debug? How do you test? > > Thanks! > _______________________________________________ > 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 Tue Feb 5 00:01:11 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 04 Feb 2013 23:53:11 -0008 Subject: [Shotwell] Ubuntu automated testing meeting In-Reply-To: References: Message-ID: <51104bc9.28a4b60a.7298.ffff9291@mx.google.com> Hi Joseph, It looks like we're a little late in replying to this. Did you attend? ?Curious what decision were made, I don't see any summaries on the web site. -- Jim On Thu, Jan 31, 2013 at 3:54 PM, Joseph B wrote: Is this something shotwell would be interested in? http://fridge.ubuntu.com/2013/01/31/automated-testing-hackfest/ _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Tue Feb 5 00:10:14 2013 From: jim at yorba.org (Jim Nelson) Date: Tue, 05 Feb 2013 00:02:14 -0008 Subject: [Shotwell] database malformed In-Reply-To: References: Message-ID: <51104de8.44133c0a.6347.ffff98fa@mx.google.com> Unfortunately, no. ?If your photo.db and its backup are both malformed, I think you're out of luck. ?You might search for advanced SQLite recovery tools, but I don't know of any other than the command-line tools SQLite provides. Does Shotwell even start with this malformed database? ?You say you get error messages for your photos. ?What kinds of error messages? -- Jim On Sat, Feb 2, 2013 at 3:50 PM, Martin Album Ytre-Eide wrote: Hello all. My shotwell database is malformed and I can't find a solution for it. The problem is that a lot of pictures won't show up in shotwell (but videos do) no error message. I had a look at: http://askubuntu.com/questions/58295...ed-shotwell-db so I tried restoring the database (from photo.db.back) without any luck - it has the same issues. The pragma integrity_check gives: sqlite> pragma integrity_check; *** in database main *** Page 1090: btreeInitPage() returns error code 11 On tree page 996 cell 6: Child page depth differs On tree page 996 cell 7: Child page depth differs Page 29: btreeInitPage() returns error code 11 On tree page 27 cell 2: Child page depth differs On tree page 27 cell 3: Child page depth differs Error: database disk image is malformed I run ubuntu 12.10 and shotwell 0.13.1. I am missing about two year of photos in shotwell (I have the photos of course) Any ideas to fix this? I have also run a check on the disk's with sudo touch /forcefsck but I found no errors on the disk. I have had some problems with ffmpeg( did a apt-get remove and then install (I think)) and diskspace (I removed some old kernels), but I do not see how that could have anything to do with this..... Martin _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From joseph.bylund at gmail.com Tue Feb 5 01:02:05 2013 From: joseph.bylund at gmail.com (Joseph Bylund) Date: Mon, 04 Feb 2013 20:02:05 -0500 Subject: [Shotwell] Ubuntu automated testing meeting In-Reply-To: <51104bc9.28a4b60a.7298.ffff9291@mx.google.com> References: <51104bc9.28a4b60a.7298.ffff9291@mx.google.com> Message-ID: <51105A0D.5060803@gmail.com> Jim, I don't think much was decided at the chat, there's a log here: http://irclogs.ubuntu.com/2013/02/01/%23ubuntu-quality.html . You can find links to documentation on the various test packages here: https://wiki.ubuntu.com/QATeam/AutomatedTesting/Hackfest , I haven't looked at it in any depth. -Joe On 02/04/2013 07:01 PM, Jim Nelson wrote: > Hi Joseph, > > It looks like we're a little late in replying to this. > > Did you attend? Curious what decision were made, I don't see any > summaries on the web site. > > -- Jim > > On Thu, Jan 31, 2013 at 3:54 PM, Joseph B wrote: >> Is this something shotwell would be interested in? >> >> http://fridge.ubuntu.com/2013/01/31/automated-testing-hackfest/ >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From jim at yorba.org Tue Feb 5 02:46:21 2013 From: jim at yorba.org (Jim Nelson) Date: Tue, 05 Feb 2013 02:38:21 -0008 Subject: [Shotwell] Shotwell on Nabble In-Reply-To: References: Message-ID: <5110727f.2148420a.3bac.0c9d@mx.google.com> It looks like Nabble stopped processing Shotwell mailing list emails on 2 Aug, 2012. ?The only reason the Jan 29 post exists is that it's a spam message in reply to a much older message. I've looked into it on our end and don't see a problem. ?I've posted a query on their free support forum: http://support.nabble.com/Nabble-stopped-archiving-our-Mailman-list-td7582914.html -- Jim On Sat, Feb 2, 2013 at 5:03 AM, Philip Gilli?en wrote: Hi folks! I'm frequently using Nabble for reading mailing list and as it seems, this list is also hosted on nabble.[1] Unfortunately, the nabble forum is not recent, since the last post is from four days ago. Does anybody have a clue, why is that and how this can be fixed? Kind regards, Philip [1] http://shotwell.996238.n3.nabble.com/ --- Alle Postf?cher an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/produkte/basic/index.html _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From hendry.michael at gmail.com Tue Feb 5 08:33:09 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Tue, 5 Feb 2013 08:33:09 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> Message-ID: On 4 Feb 2013, at 20:54, Jim Nelson wrote: > Great to hear! If it works, it works. > > We really would like to have a better export/import system for Shotwell to avoid this problem, but for now I'm glad you got this worked out. > > -- Jim Unfortunately, I spoke too soon! I hadn't gone far enough back in my archive to detect "missing" files. Everything looked OK when I only viewed the thumbnails, but when I double-clicked on a thumbnail the thumbnail disappeared, and the image was consigned to the Missing folder. I had done some reorganisation of the location of files on my Ubuntu computer when I upgraded to 12.04 from 10.04 and incorporated a new hard disc, but didn't check that everything was working correctly in that environment. Back to the drawing board for me! Inevitably, as disc capacity becomes exhausted or failing discs are replaced, there will be a need for photo-archives to be moved around on the same computer, or shifted to new ones, and Shotwell needs to support this, My first thought on how this would look would be a Nautilus-like presentation of the filesystem, restricted to files "known to" Shotwell. Dragging-and-Dropping of folders or individual files could then be tracked by Shotwell, and the database adjusted accordingly. Michael From moejoeblue at gmail.com Tue Feb 5 11:03:44 2013 From: moejoeblue at gmail.com (Moe Blue) Date: Tue, 5 Feb 2013 12:03:44 +0100 Subject: [Shotwell] re-combine RAW+JPEG In-Reply-To: References: <510EB1D0.8040408@gmail.com> Message-ID: Hi Lucas, thanks for your answer. #4040 could be fine for that purpose. To be more precise, I don't need to combine/separate RAW+JPEGs day-to-day but rather want to fix my photo database as soon as the recent RAW+JPEG fixes are in the new stable version of shotwell. I face the situation, where I have already imported RAW+JPEGs, where the RAW is paired with the _embedded or the _shotwell development. On file system it looks something like: P0001.ORF P0001_ORF.jpg (which was originally P0001.JPG) P0001_embedded.jpg P0001_shotwell.jpg Sometimes the Camera sister JPG appears beside the RAW inside shotwell, sometimes not. I can investigate more on that later. But I think, a simple tool would be great where I can point for the RAW file to a certain JPEG. E.g. "Manuelly select developed JPG" or "Manually select Camera developed JPEG". On the one hand I could use this to fix my db, on the other hand I could use it to set a darktable or ufraw developed JPEG as the developed version. best Moe 2013/2/4 Lucas Beeler > Hi Moe, > > I can address two of your issues. First, The issue with the _embedded > JPEG file being preferred to the sister JPEG in a RAW+JPEG pair has > been addressed in several recent commits. Second, we do have an > outstanding ticket to combine and separate RAW+JPEG pairs here: > http://redmine.yorba.org/issues/4040. Would this give you most of the > functionality you need? > > Cheers, > Lucas > > On Sun, Feb 3, 2013 at 10:52 AM, Moe Blue wrote: > > Hi, > > > > for the next version of shotwell, will there be any option to re-combine > > RAW+JPEG? > > > > I'm looking forward to shotwell 0.14 with the recent RAW fixes. I'm also > > trying the shotwell development ppa on a non production machine with a > copy > > of my photo database. So far, things seem to improve, thanks a lot for > > taking up development again for this great photo management application! > > > > But my old photo database is a bit messed up. Often, RAW and JPEG are not > > properly paired. In some cases, the embedded JPEG has been extracted and > > been used instead of the Camera developed JPEG which was beside the RAW > > file. As for now, there does seem to be good handling for new imports > from > > camera, while I cannot find a way to re-combine old RAW+JPEG pairs and > get > > rid of the _embedded version. > > > > I really hope, there will be something to handle this old photos. I do > not > > understand why shotwell uses the embedded version as development at all > > (except for the thumbnail). > > > > Best > > Moe > > _______________________________________________ > > Shotwell mailing list > > Shotwell at lists.yorba.org > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -- Moe Blue From nilux17 at gmail.com Tue Feb 5 12:08:55 2013 From: nilux17 at gmail.com (Nicolas Gauvrit) Date: Tue, 05 Feb 2013 13:08:55 +0100 Subject: [Shotwell] rsync shotwell folders Message-ID: <5110F657.70004@gmail.com> Hi there, I use shotwell for few years now and i enjoyed it ! I run debian/sid on 3 computers. i rsync those computers with a home made script which synchronise my photos between them. my ~/.shotwell and my ~/Photos yesterday, i upgrade from 0.12.3 (sid/main amd64 Packages) to 0.13.1 (experimental/main amd64 Packages). I've seen than there is no more ~/.shotwell folder, but a ~/.cache/shotwell folder. so i 've change rsync command too... it works well but on the target computers , there isn't new photos tags thanks for reply, Nicolas From hendry.michael at gmail.com Tue Feb 5 16:32:18 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Tue, 5 Feb 2013 16:32:18 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> Message-ID: On 5 Feb 2013, at 08:33, Michael Hendry wrote: > > On 4 Feb 2013, at 20:54, Jim Nelson wrote: > >> Great to hear! If it works, it works. >> >> We really would like to have a better export/import system for Shotwell to avoid this problem, but for now I'm glad you got this worked out. >> >> -- Jim > > Unfortunately, I spoke too soon! > > I hadn't gone far enough back in my archive to detect "missing" files. Everything looked OK when I only viewed the thumbnails, but when I double-clicked on a thumbnail the thumbnail disappeared, and the image was consigned to the Missing folder. > > I had done some reorganisation of the location of files on my Ubuntu computer when I upgraded to 12.04 from 10.04 and incorporated a new hard disc, but didn't check that everything was working correctly in that environment. > > Back to the drawing board for me! > > Inevitably, as disc capacity becomes exhausted or failing discs are replaced, there will be a need for photo-archives to be moved around on the same computer, or shifted to new ones, and Shotwell needs to support this, > > My first thought on how this would look would be a Nautilus-like presentation of the filesystem, restricted to files "known to" Shotwell. Dragging-and-Dropping of folders or individual files could then be tracked by Shotwell, and the database adjusted accordingly. > > Michael PS The only other table I could find in the database which refers to file paths is BackingPhotoTable. I have made appropriate adjustments to these paths to fit the new environment on my iMac, and this seems to have sorted the Missing Files problem. I may still be speaking too soon.. Michael From schuetz.marc at gmx.de Tue Feb 5 18:43:30 2013 From: schuetz.marc at gmx.de (Marc) Date: Tue, 05 Feb 2013 19:43:30 +0100 Subject: [Shotwell] rsync shotwell folders In-Reply-To: <5110F657.70004@gmail.com> References: <5110F657.70004@gmail.com> Message-ID: <511152D2.4050009@gmx.de> Hi Nicolas, db and cache are now two directorys. There should be an .local/share/shotwell also or on another place. kind regards Marc Am 05.02.2013 13:08, schrieb Nicolas Gauvrit: > Hi there, > > I use shotwell for few years now and i enjoyed it ! > I run debian/sid on 3 computers. > > i rsync those computers with a home made script which synchronise my > photos between them. > my ~/.shotwell and my ~/Photos > > yesterday, i upgrade from 0.12.3 (sid/main amd64 Packages) to 0.13.1 > (experimental/main amd64 Packages). > I've seen than there is no more ~/.shotwell folder, but a > ~/.cache/shotwell folder. > so i 've change rsync command too... > > it works well but on the target computers , there isn't new photos tags > > thanks for reply, > > Nicolas > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: From schuetz.marc at gmx.de Tue Feb 5 18:45:22 2013 From: schuetz.marc at gmx.de (Marc) Date: Tue, 05 Feb 2013 19:45:22 +0100 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> Message-ID: <51115342.6040102@gmx.de> Hi Jim, I've uploaded a photo to ubuntu one. If you have an account or some other. I will share the link with you. PS: I have found a photo with only 277 mb ;-) not one of the >300mb... Kind Regards Marc Am 04.02.2013 23:59, schrieb Jim Nelson: > Hi Marc, > > The link you sent us appears to display a JPEG, not TIFF. We would need > to download the original TIFF in order to understand the problem. Is > there any way you could make that available to us? > > -- Jim > > On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: >> Hi all, >> >> sorry for the late response. >> I've uploaded such an shotwell-thumbnail here >> >> http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ >> >> For me the workaround is now to create jpgs with imagemagick. >> >> I've tried to get information about the TIFFs via "Phatch Image >> Inspector" but it tells me "failure". >> GIMP and Eye of Gnome are displying the TIFF correct. >> >> >> Perhaps the problem is coming from Hugin, because the Source-Tiffs from >> Photoshop are displyaed correctly, only the Panoramas from Hugin not. >> If anyone has an tip for me how to get information about the Tiff would >> be very helpful. >> >> Cheers >> Marc >> >> >> >> Am 28.01.2013 20:12, schrieb Jim Nelson: >> > Hi Marc, >> > >> > Unfortunately our mailing list doesn't allow attachments. If they're >> > small enough, you can mail the photo(s) directly to shotwell at yorba.org. >> > If not, please make them available via a public download service. >> > >> > We don't have a ticket about the problem you're describing, so we'd be >> > interested in seeing this problem here. >> > >> > -- Jim >> > >> > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> >> HI, >> >> >> >> this is first time I have used my camera with AEB, then created HDRs >> >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> >> Panoramas with Hugin. >> >> The Problem after importing all into shotwell is that shotwell creates >> >> such thumbnail files with _shotwell.tif see attached. They are all >> black. >> >> >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. How >> >> could this fixed? >> >> >> >> Thanks >> >> Marc >> >> >> > >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: From guerda at freenet.de Tue Feb 5 19:40:06 2013 From: guerda at freenet.de (=?UTF-8?B?UGhpbGlwIEdpbGxpw59lbg==?=) Date: Tue, 05 Feb 2013 20:40:06 +0100 Subject: [Shotwell] Shotwell on Nabble In-Reply-To: <5110727f.2148420a.3bac.0c9d@mx.google.com> References: <5110727f.2148420a.3bac.0c9d@mx.google.com> Message-ID: <51116016.4010202@freenet.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jim! On Tue 05 Feb 2013 03:46:21 AM CET, Jim Nelson wrote: > I've looked into it on our end and don't see a problem. I've posted a > query on their free support forum: > > http://support.nabble.com/Nabble-stopped-archiving-our-Mailman-list-td7582914.html Perfect! Thank you very much! Kind regards, Philip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlERYBYACgkQYNYFUFLXAD0MJACgjhwpn67toSaVv6v1JhG1jjjm pisAn2LrHayG6h3/GzWLwpv2Rx+egmmN =42x7 -----END PGP SIGNATURE----- From lucas at yorba.org Tue Feb 5 20:44:57 2013 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 5 Feb 2013 12:44:57 -0800 Subject: [Shotwell] Shotwell not starting unless '--no-startup-progress' option is specified Message-ID: Hi Michele, The Shotwell scanning and monitoring code is pretty good about logging what it's doing. So in this case it would be really helpful to have a log file. Or rather, two log files: one log file generated when Shotwell is run with the --no-startup-progress option specified and another log file generated when Shotwell is run without any additional options. Once you've generated these log files, mail 'em to shotwell at yorba.org and we on the Shotwell dev team will have a look at them. If you're unfamiliar with how to generate a log file, see the "I found a bug in Shotwell. How can I report it?" section of the Shotwell FAQ here: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#I-found-a-bug-in-Shotwell-How-can-I-report-it. Cheers, Lucas From jim at yorba.org Tue Feb 5 23:53:00 2013 From: jim at yorba.org (Jim Nelson) Date: Tue, 05 Feb 2013 23:45:00 -0008 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <51115342.6040102@gmx.de> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> <51115342.6040102@gmx.de> Message-ID: <51119b62.c258420a.6d66.45a8@mx.google.com> We can generate an Ubuntu One account, but I was under the impression you could make a file publicly available (assuming you're okay with that). Other than Ubuntu One, I know Dropbox offers such a feature, and I believe Mega does too. You can send the link to shotwell at yorba.org rather than this mailing list if you'd like to keep the photo private. -- Jim On Tue, Feb 5, 2013 at 10:45 AM, Marc wrote: Hi Jim, I've uploaded a photo to ubuntu one. If you have an account or some other. I will share the link with you. PS: I have found a photo with only 277 mb ;-) not one of the >300mb... Kind Regards Marc Am 04.02.2013 23:59, schrieb Jim Nelson: > Hi Marc, > > The link you sent us appears to display a JPEG, not TIFF. We would need > to download the original TIFF in order to understand the problem. Is > there any way you could make that available to us? > > -- Jim > > On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: >> Hi all, >> >> sorry for the late response. >> I've uploaded such an shotwell-thumbnail here >> >> http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ >> >> For me the workaround is now to create jpgs with imagemagick. >> >> I've tried to get information about the TIFFs via "Phatch Image >> Inspector" but it tells me "failure". >> GIMP and Eye of Gnome are displying the TIFF correct. >> >> >> Perhaps the problem is coming from Hugin, because the Source-Tiffs from >> Photoshop are displyaed correctly, only the Panoramas from Hugin not. >> If anyone has an tip for me how to get information about the Tiff would >> be very helpful. >> >> Cheers >> Marc >> >> >> >> Am 28.01.2013 20:12, schrieb Jim Nelson: >> > Hi Marc, >> > >> > Unfortunately our mailing list doesn't allow attachments. If they're >> > small enough, you can mail the photo(s) directly to shotwell at yorba.org. >> > If not, please make them available via a public download service. >> > >> > We don't have a ticket about the problem you're describing, so we'd be >> > interested in seeing this problem here. >> > >> > -- Jim >> > >> > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> >> HI, >> >> >> >> this is first time I have used my camera with AEB, then created HDRs >> >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> >> Panoramas with Hugin. >> >> The Problem after importing all into shotwell is that shotwell creates >> >> such thumbnail files with _shotwell.tif see attached. They are all >> black. >> >> >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. How >> >> could this fixed? >> >> >> >> Thanks >> >> Marc >> >> >> > >> > From lucas at yorba.org Wed Feb 6 01:04:39 2013 From: lucas at yorba.org (Lucas Beeler) Date: Tue, 5 Feb 2013 17:04:39 -0800 Subject: [Shotwell] rsync shotwell folders Message-ID: Hi Nicolas, The location of the Shotwell data and cache folders changed between Shotwell 0.12.x and Shotwell 0.13.x. This is documented in our FAQ under the "How can I copy my Shotwell library to a new computer?" entry here: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#How-can-I-copy-my-Shotwell-library-to-a-new-computer. Strictly speaking, you only need to copy the data directory. Shotwell is capable of regenerating everything in the cache directory automatically. Cheers, Lucas From nilux17 at gmail.com Wed Feb 6 08:21:11 2013 From: nilux17 at gmail.com (Nicolas Gauvrit) Date: Wed, 06 Feb 2013 09:21:11 +0100 Subject: [Shotwell] rsync shotwell folders In-Reply-To: <511152D2.4050009@gmx.de> References: <5110F657.70004@gmail.com> <511152D2.4050009@gmx.de> Message-ID: <51121277.4030200@gmail.com> Hi, Thanks for all your reply, works like a charm Nicolas On 05/02/2013 19:43, Marc wrote: > Hi Nicolas, > > db and cache are now two directorys. There should be an > .local/share/shotwell > > also or on another place. > > kind regards > Marc > > > Am 05.02.2013 13:08, schrieb Nicolas Gauvrit: >> Hi there, >> >> I use shotwell for few years now and i enjoyed it ! >> I run debian/sid on 3 computers. >> >> i rsync those computers with a home made script which synchronise my >> photos between them. >> my ~/.shotwell and my ~/Photos >> >> yesterday, i upgrade from 0.12.3 (sid/main amd64 Packages) to 0.13.1 >> (experimental/main amd64 Packages). >> I've seen than there is no more ~/.shotwell folder, but a >> ~/.cache/shotwell folder. >> so i 've change rsync command too... >> >> it works well but on the target computers , there isn't new photos tags >> >> thanks for reply, >> >> Nicolas >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >> From jim at yorba.org Wed Feb 6 19:16:52 2013 From: jim at yorba.org (Jim Nelson) Date: Wed, 06 Feb 2013 19:08:52 -0008 Subject: [Shotwell] Shotwell on Nabble In-Reply-To: <51116016.4010202@freenet.de> References: <5110727f.2148420a.3bac.0c9d@mx.google.com> <51116016.4010202@freenet.de> Message-ID: <5112ac23.c258420a.6d66.500d@mx.google.com> The Nabble list is now working again. ?They've also imported the entire archive going back to 2009, so good times are here again. -- Jim On Tue, Feb 5, 2013 at 11:40 AM, Philip Gilli?en wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jim! On Tue 05 Feb 2013 03:46:21 AM CET, Jim Nelson wrote: > I've looked into it on our end and don't see a problem. I've posted a > query on their free support forum: > > http://support.nabble.com/Nabble-stopped-archiving-our-Mailman-list-td7582914.html Perfect! Thank you very much! Kind regards, Philip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlERYBYACgkQYNYFUFLXAD0MJACgjhwpn67toSaVv6v1JhG1jjjm pisAn2LrHayG6h3/GzWLwpv2Rx+egmmN =42x7 -----END PGP SIGNATURE----- _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From schuetz.marc at gmx.de Wed Feb 6 20:01:39 2013 From: schuetz.marc at gmx.de (Marc) Date: Wed, 06 Feb 2013 21:01:39 +0100 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <51119b62.c258420a.6d66.45a8@mx.google.com> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> <51115342.6040102@gmx.de> <51119b62.c258420a.6d66.45a8@mx.google.com> Message-ID: <5112B6A3.1060503@gmx.de> Hi JIm, Hi all, here it is, hope it works https://www.dropbox.com/s/wlasybidzduc6w0/IMG_5438-IMG_5440_HDR1-IMG_5447-IMG_5449_HDR1_gradlinig.tif Cheers Marc Am 06.02.2013 00:53, schrieb Jim Nelson: > We can generate an Ubuntu One account, but I was under the impression > you could make a file publicly available (assuming you're okay with that). > > Other than Ubuntu One, I know Dropbox offers such a feature, and I > believe Mega does too. > > You can send the link to shotwell at yorba.org rather than this mailing > list if you'd like to keep the photo private. > > -- Jim > > On Tue, Feb 5, 2013 at 10:45 AM, Marc wrote: >> Hi Jim, >> >> I've uploaded a photo to ubuntu one. If you have an account or some >> other. I will share the link with you. >> >> PS: I have found a photo with only 277 mb ;-) not one of the >300mb... >> >> Kind Regards >> Marc >> >> >> >> Am 04.02.2013 23:59, schrieb Jim Nelson: >> > Hi Marc, >> > >> > The link you sent us appears to display a JPEG, not TIFF. We would need >> > to download the original TIFF in order to understand the problem. Is >> > there any way you could make that available to us? >> > >> > -- Jim >> > >> > On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: >> >> Hi all, >> >> >> >> sorry for the late response. >> >> I've uploaded such an shotwell-thumbnail here >> >> >> >> http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ >> >> >> >> For me the workaround is now to create jpgs with imagemagick. >> >> >> >> I've tried to get information about the TIFFs via "Phatch Image >> >> Inspector" but it tells me "failure". >> >> GIMP and Eye of Gnome are displying the TIFF correct. >> >> >> >> >> >> Perhaps the problem is coming from Hugin, because the Source-Tiffs >> from >> >> Photoshop are displyaed correctly, only the Panoramas from Hugin not. >> >> If anyone has an tip for me how to get information about the Tiff >> would >> >> be very helpful. >> >> >> >> Cheers >> >> Marc >> >> >> >> >> >> >> >> Am 28.01.2013 20:12, schrieb Jim Nelson: >> >> > Hi Marc, >> >> > >> >> > Unfortunately our mailing list doesn't allow attachments. If they're >> >> > small enough, you can mail the photo(s) directly to >> shotwell at yorba.org. >> >> > If not, please make them available via a public download service. >> >> > >> >> > We don't have a ticket about the problem you're describing, so >> we'd be >> >> > interested in seeing this problem here. >> >> > >> >> > -- Jim >> >> > >> >> > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> >> >> HI, >> >> >> >> >> >> this is first time I have used my camera with AEB, then created >> HDRs >> >> >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> >> >> Panoramas with Hugin. >> >> >> The Problem after importing all into shotwell is that shotwell >> creates >> >> >> such thumbnail files with _shotwell.tif see attached. They are all >> >> black. >> >> >> >> >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. >> How >> >> >> could this fixed? >> >> >> >> >> >> Thanks >> >> >> Marc >> >> >> >> >> > >> >> >> > >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: From jim at yorba.org Wed Feb 6 22:16:40 2013 From: jim at yorba.org (Jim Nelson) Date: Wed, 06 Feb 2013 22:08:40 -0008 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <5112B6A3.1060503@gmx.de> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> <51115342.6040102@gmx.de> <51119b62.c258420a.6d66.45a8@mx.google.com> <5112B6A3.1060503@gmx.de> Message-ID: <5112d647.264b420a.37cf.5fa6@mx.google.com> Marc, I got the image, thanks. ?I do see the problem here. ?Let me consult with the Shotwell team and get back to you. Thanks, -- Jim On Wed, Feb 6, 2013 at 12:01 PM, Marc wrote: Hi JIm, Hi all, here it is, hope it works https://www.dropbox.com/s/wlasybidzduc6w0/IMG_5438-IMG_5440_HDR1-IMG_5447-IMG_5449_HDR1_gradlinig.tif Cheers Marc Am 06.02.2013 00:53, schrieb Jim Nelson: > We can generate an Ubuntu One account, but I was under the impression > you could make a file publicly available (assuming you're okay with that). > > Other than Ubuntu One, I know Dropbox offers such a feature, and I > believe Mega does too. > > You can send the link to shotwell at yorba.org rather than this mailing > list if you'd like to keep the photo private. > > -- Jim > > On Tue, Feb 5, 2013 at 10:45 AM, Marc wrote: >> Hi Jim, >> >> I've uploaded a photo to ubuntu one. If you have an account or some >> other. I will share the link with you. >> >> PS: I have found a photo with only 277 mb ;-) not one of the >300mb... >> >> Kind Regards >> Marc >> >> >> >> Am 04.02.2013 23:59, schrieb Jim Nelson: >> > Hi Marc, >> > >> > The link you sent us appears to display a JPEG, not TIFF. We would need >> > to download the original TIFF in order to understand the problem. Is >> > there any way you could make that available to us? >> > >> > -- Jim >> > >> > On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: >> >> Hi all, >> >> >> >> sorry for the late response. >> >> I've uploaded such an shotwell-thumbnail here >> >> >> >> http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ >> >> >> >> For me the workaround is now to create jpgs with imagemagick. >> >> >> >> I've tried to get information about the TIFFs via "Phatch Image >> >> Inspector" but it tells me "failure". >> >> GIMP and Eye of Gnome are displying the TIFF correct. >> >> >> >> >> >> Perhaps the problem is coming from Hugin, because the Source-Tiffs >> from >> >> Photoshop are displyaed correctly, only the Panoramas from Hugin not. >> >> If anyone has an tip for me how to get information about the Tiff >> would >> >> be very helpful. >> >> >> >> Cheers >> >> Marc >> >> >> >> >> >> >> >> Am 28.01.2013 20:12, schrieb Jim Nelson: >> >> > Hi Marc, >> >> > >> >> > Unfortunately our mailing list doesn't allow attachments. If they're >> >> > small enough, you can mail the photo(s) directly to >> shotwell at yorba.org. >> >> > If not, please make them available via a public download service. >> >> > >> >> > We don't have a ticket about the problem you're describing, so >> we'd be >> >> > interested in seeing this problem here. >> >> > >> >> > -- Jim >> >> > >> >> > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> >> >> HI, >> >> >> >> >> >> this is first time I have used my camera with AEB, then created >> HDRs >> >> >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> >> >> Panoramas with Hugin. >> >> >> The Problem after importing all into shotwell is that shotwell >> creates >> >> >> such thumbnail files with _shotwell.tif see attached. They are all >> >> black. >> >> >> >> >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. >> How >> >> >> could this fixed? >> >> >> >> >> >> Thanks >> >> >> Marc >> >> >> >> >> > >> >> >> > >> > From javajens at gmail.com Thu Feb 7 09:28:24 2013 From: javajens at gmail.com (Jens B.) Date: Thu, 7 Feb 2013 10:28:24 +0100 Subject: [Shotwell] [Shotwell Slideshow] shotwell-transitions-extras Message-ID: Hi all, I've opened up a feature ticket: http://redmine.yorba.org/issues/6347 There I propose to include community built Slideshow transitions to ship with Shotwell. I've included 4 sample transitions: *Clock Transition *Circle *Circles *Vertical Blinds Maybe you can check it out and report what you think. Kind Regards Jens From jim at yorba.org Sat Feb 9 01:49:57 2013 From: jim at yorba.org (Jim Nelson) Date: Sat, 09 Feb 2013 01:41:57 -0008 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <5112B6A3.1060503@gmx.de> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> <51115342.6040102@gmx.de> <51119b62.c258420a.6d66.45a8@mx.google.com> <5112B6A3.1060503@gmx.de> Message-ID: <5115ab46.4955420a.3012.ffffe9e1@mx.google.com> We've looked into this here just a little bit and have a couple of theories about the problem. ?It's possible Shotwell is mistaking this file as a RAW file (they're similar in structure with TIFF) and trying to decode it with LibRaw instead of GDK (which decodes TIFFs). ?I've filed a ticket here: http://redmine.yorba.org/issues/6355 I don't know when we'll have this problem solved, but it's in the queue! -- Jim On Wed, Feb 6, 2013 at 12:01 PM, Marc wrote: Hi JIm, Hi all, here it is, hope it works https://www.dropbox.com/s/wlasybidzduc6w0/IMG_5438-IMG_5440_HDR1-IMG_5447-IMG_5449_HDR1_gradlinig.tif Cheers Marc Am 06.02.2013 00:53, schrieb Jim Nelson: > We can generate an Ubuntu One account, but I was under the impression > you could make a file publicly available (assuming you're okay with that). > > Other than Ubuntu One, I know Dropbox offers such a feature, and I > believe Mega does too. > > You can send the link to shotwell at yorba.org rather than this mailing > list if you'd like to keep the photo private. > > -- Jim > > On Tue, Feb 5, 2013 at 10:45 AM, Marc wrote: >> Hi Jim, >> >> I've uploaded a photo to ubuntu one. If you have an account or some >> other. I will share the link with you. >> >> PS: I have found a photo with only 277 mb ;-) not one of the >300mb... >> >> Kind Regards >> Marc >> >> >> >> Am 04.02.2013 23:59, schrieb Jim Nelson: >> > Hi Marc, >> > >> > The link you sent us appears to display a JPEG, not TIFF. We would need >> > to download the original TIFF in order to understand the problem. Is >> > there any way you could make that available to us? >> > >> > -- Jim >> > >> > On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: >> >> Hi all, >> >> >> >> sorry for the late response. >> >> I've uploaded such an shotwell-thumbnail here >> >> >> >> http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ >> >> >> >> For me the workaround is now to create jpgs with imagemagick. >> >> >> >> I've tried to get information about the TIFFs via "Phatch Image >> >> Inspector" but it tells me "failure". >> >> GIMP and Eye of Gnome are displying the TIFF correct. >> >> >> >> >> >> Perhaps the problem is coming from Hugin, because the Source-Tiffs >> from >> >> Photoshop are displyaed correctly, only the Panoramas from Hugin not. >> >> If anyone has an tip for me how to get information about the Tiff >> would >> >> be very helpful. >> >> >> >> Cheers >> >> Marc >> >> >> >> >> >> >> >> Am 28.01.2013 20:12, schrieb Jim Nelson: >> >> > Hi Marc, >> >> > >> >> > Unfortunately our mailing list doesn't allow attachments. If they're >> >> > small enough, you can mail the photo(s) directly to >> shotwell at yorba.org. >> >> > If not, please make them available via a public download service. >> >> > >> >> > We don't have a ticket about the problem you're describing, so >> we'd be >> >> > interested in seeing this problem here. >> >> > >> >> > -- Jim >> >> > >> >> > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> >> >> HI, >> >> >> >> >> >> this is first time I have used my camera with AEB, then created >> HDRs >> >> >> with Photoshop. Some of the 16-Bit-Tiff files I have used to create >> >> >> Panoramas with Hugin. >> >> >> The Problem after importing all into shotwell is that shotwell >> creates >> >> >> such thumbnail files with _shotwell.tif see attached. They are all >> >> black. >> >> >> >> >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. >> How >> >> >> could this fixed? >> >> >> >> >> >> Thanks >> >> >> Marc >> >> >> >> >> > >> >> >> > >> > From schuetz.marc at gmx.de Sat Feb 9 06:46:59 2013 From: schuetz.marc at gmx.de (Marc) Date: Sat, 09 Feb 2013 07:46:59 +0100 Subject: [Shotwell] Shotwell Daily/Trunk - Creates black Thumbnails from TIFF 16Bit - Panorama In-Reply-To: <5115ab46.4955420a.3012.ffffe9e1@mx.google.com> References: <51052C61.6040309@gmx.de> <5106cd87.8673440a.735f.ffffce82@mx.google.com> <510E5D54.8080802@gmx.de> <51103d50.0a143c0a.5b7c.ffff8a79@mx.google.com> <51115342.6040102@gmx.de> <51119b62.c258420a.6d66.45a8@mx.google.com> <5112B6A3.1060503@gmx.de> <5115ab46.4955420a.3012.ffffe9e1@mx.google.com> Message-ID: <5115F0E3.5040503@gmx.de> thank you Jim Looking forward :-) kind Regards Marc Am 09.02.2013 02:49, schrieb Jim Nelson: > We've looked into this here just a little bit and have a couple of > theories about the problem. It's possible Shotwell is mistaking this > file as a RAW file (they're similar in structure with TIFF) and trying > to decode it with LibRaw instead of GDK (which decodes TIFFs). I've > filed a ticket here: http://redmine.yorba.org/issues/6355 > > I don't know when we'll have this problem solved, but it's in the queue! > > -- Jim > > On Wed, Feb 6, 2013 at 12:01 PM, Marc wrote: >> Hi JIm, Hi all, >> >> here it is, hope it works >> >> https://www.dropbox.com/s/wlasybidzduc6w0/IMG_5438-IMG_5440_HDR1-IMG_5447-IMG_5449_HDR1_gradlinig.tif >> >> >> Cheers >> Marc >> >> Am 06.02.2013 00:53, schrieb Jim Nelson: >> > We can generate an Ubuntu One account, but I was under the impression >> > you could make a file publicly available (assuming you're okay with >> that). >> > >> > Other than Ubuntu One, I know Dropbox offers such a feature, and I >> > believe Mega does too. >> > >> > You can send the link to shotwell at yorba.org rather than this mailing >> > list if you'd like to keep the photo private. >> > >> > -- Jim >> > >> > On Tue, Feb 5, 2013 at 10:45 AM, Marc wrote: >> >> Hi Jim, >> >> >> >> I've uploaded a photo to ubuntu one. If you have an account or some >> >> other. I will share the link with you. >> >> >> >> PS: I have found a photo with only 277 mb ;-) not one of the >300mb... >> >> >> >> Kind Regards >> >> Marc >> >> >> >> >> >> >> >> Am 04.02.2013 23:59, schrieb Jim Nelson: >> >> > Hi Marc, >> >> > >> >> > The link you sent us appears to display a JPEG, not TIFF. We >> would need >> >> > to download the original TIFF in order to understand the problem. Is >> >> > there any way you could make that available to us? >> >> > >> >> > -- Jim >> >> > >> >> > On Sun, Feb 3, 2013 at 4:51 AM, Marc wrote: >> >> >> Hi all, >> >> >> >> >> >> sorry for the late response. >> >> >> I've uploaded such an shotwell-thumbnail here >> >> >> >> >> >> >> http://imageshack.us/photo/my-images/707/img5732img5733hdr1img57.jpg/ >> >> >> >> >> >> For me the workaround is now to create jpgs with imagemagick. >> >> >> >> >> >> I've tried to get information about the TIFFs via "Phatch Image >> >> >> Inspector" but it tells me "failure". >> >> >> GIMP and Eye of Gnome are displying the TIFF correct. >> >> >> >> >> >> >> >> >> Perhaps the problem is coming from Hugin, because the Source-Tiffs >> >> from >> >> >> Photoshop are displyaed correctly, only the Panoramas from Hugin >> not. >> >> >> If anyone has an tip for me how to get information about the Tiff >> >> would >> >> >> be very helpful. >> >> >> >> >> >> Cheers >> >> >> Marc >> >> >> >> >> >> >> >> >> >> >> >> Am 28.01.2013 20:12, schrieb Jim Nelson: >> >> >> > Hi Marc, >> >> >> > >> >> >> > Unfortunately our mailing list doesn't allow attachments. If >> they're >> >> >> > small enough, you can mail the photo(s) directly to >> >> shotwell at yorba.org. >> >> >> > If not, please make them available via a public download service. >> >> >> > >> >> >> > We don't have a ticket about the problem you're describing, so >> >> we'd be >> >> >> > interested in seeing this problem here. >> >> >> > >> >> >> > -- Jim >> >> >> > >> >> >> > On Sun, Jan 27, 2013 at 5:32 AM, Marc wrote: >> >> >> >> HI, >> >> >> >> >> >> >> >> this is first time I have used my camera with AEB, then created >> >> HDRs >> >> >> >> with Photoshop. Some of the 16-Bit-Tiff files I have used to >> create >> >> >> >> Panoramas with Hugin. >> >> >> >> The Problem after importing all into shotwell is that shotwell >> >> creates >> >> >> >> such thumbnail files with _shotwell.tif see attached. They >> are all >> >> >> black. >> >> >> >> >> >> >> >> The 16-Bit Tiff HDR files from Photoshop are imported correctly. >> >> How >> >> >> >> could this fixed? >> >> >> >> >> >> >> >> Thanks >> >> >> >> Marc >> >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> > >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: From preining at logic.at Sat Feb 9 09:32:32 2013 From: preining at logic.at (Norbert Preining) Date: Sat, 9 Feb 2013 18:32:32 +0900 Subject: [Shotwell] Development tools In-Reply-To: <511047f5.cb0d320a.75ad.05b2@mx.google.com> References: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> <511047f5.cb0d320a.75ad.05b2@mx.google.com> Message-ID: <20130209093232.GB30702@gamma.logic.tuwien.ac.at> Hi Jim, On Mo, 04 Feb 2013, Jim Nelson wrote: > As fas as debugging, I recommend debug() over printf(), as it will display the filename and line number as well as your message. ?For more serious debug work I use gdb. One question: how should this debug thingy work? I added some debug statements and compiled with --debug, but still nothing shows up ... buahhhhhh changing the debug statements to stdout.printf did give an output, so it is about debug, not the code path. Any suggestions? Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From javajens at gmail.com Sat Feb 9 09:51:55 2013 From: javajens at gmail.com (Jens B.) Date: Sat, 9 Feb 2013 10:51:55 +0100 Subject: [Shotwell] Development tools In-Reply-To: <20130209093232.GB30702@gamma.logic.tuwien.ac.at> References: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> <511047f5.cb0d320a.75ad.05b2@mx.google.com> <20130209093232.GB30702@gamma.logic.tuwien.ac.at> Message-ID: I believe you have to call shotwell using: SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: ./shotwell This way the output is redirected to the console, and not the log file. From preining at logic.at Sat Feb 9 11:06:02 2013 From: preining at logic.at (Norbert Preining) Date: Sat, 9 Feb 2013 20:06:02 +0900 Subject: [Shotwell] Development tools In-Reply-To: References: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> <511047f5.cb0d320a.75ad.05b2@mx.google.com> <20130209093232.GB30702@gamma.logic.tuwien.ac.at> Message-ID: <20130209110602.GD30702@gamma.logic.tuwien.ac.at> On Sa, 09 Feb 2013, Jens B. wrote: > SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: ./shotwell Umpf, thanks. Ok, I will remain with stdout.printf, that is easier and I don't need to remember the wonderful cmd line above ;-) Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From preining at logic.at Sat Feb 9 11:07:22 2013 From: preining at logic.at (Norbert Preining) Date: Sat, 9 Feb 2013 20:07:22 +0900 Subject: [Shotwell] Object Hierarchy explorer Message-ID: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> Hi everyone, is there some GUI tool to explore the object hierarchy of a project in vala. I am imagining a tool showing me the tree of objects, and I can get the functions implemented etc etc. ? Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From javajens at gmail.com Sat Feb 9 11:28:20 2013 From: javajens at gmail.com (Jens B.) Date: Sat, 9 Feb 2013 12:28:20 +0100 Subject: [Shotwell] Object Hierarchy explorer In-Reply-To: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> References: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> Message-ID: There is Vala Toys for gEdit: https://code.google.com/p/vtg/ This provides some structural tools, like quickly jumping to a class or function, but I find it a little laggy... Maybe thats just me though. I haven't used it really, but looks allright. I don't know if that is what you are looking for. From martinyt at gmail.com Mon Feb 11 00:02:04 2013 From: martinyt at gmail.com (Martin Album Ytre-Eide) Date: Mon, 11 Feb 2013 01:02:04 +0100 Subject: [Shotwell] database malformed In-Reply-To: <51104de8.44133c0a.6347.ffff98fa@mx.google.com> References: <51104de8.44133c0a.6347.ffff98fa@mx.google.com> Message-ID: Thanks for your ansver. Shotwell starts without any error message. It is only when I check the database for errors that I get the error messages (see first mail). I will se if I find some rescue tools or look at the database and try to see whats wrong. I am missisng about two years of photos. I can see all videos and photos older than about two years. Could this have something to do with the (new ) .cache dir? I am having multiple user access to the database - using symbolic link to the harddrive where the photos and the .shotwell dir is. Martin 2013/2/5 Jim Nelson > Unfortunately, no. If your photo.db and its backup are both malformed, I > think you're out of luck. You might search for advanced SQLite recovery > tools, but I don't know of any other than the command-line tools SQLite > provides. > > Does Shotwell even start with this malformed database? You say you get > error messages for your photos. What kinds of error messages? > > -- Jim > > > On Sat, Feb 2, 2013 at 3:50 PM, Martin Album Ytre-Eide > wrote: > > Hello all. > > My shotwell database is malformed and I can't find a solution for it. > > The problem is that a lot of pictures won't show up in shotwell (but > videos > do) no error message. > > I had a look at: > http://askubuntu.com/questions/58295...ed-shotwell-db** > > so I tried restoring the database (from photo.db.back) without any luck - > it has the same issues. > > The pragma integrity_check gives: > > sqlite> pragma integrity_check; > *** in database main *** > Page 1090: btreeInitPage() returns error code 11 > On tree page 996 cell 6: Child page depth differs > On tree page 996 cell 7: Child page depth differs > Page 29: btreeInitPage() returns error code 11 > On tree page 27 cell 2: Child page depth differs > On tree page 27 cell 3: Child page depth differs > Error: database disk image is malformed > > I run ubuntu 12.10 and shotwell 0.13.1. I am missing about two year of > photos in shotwell (I have the photos of course) > > Any ideas to fix this? > > I have also run a check on the disk's with > sudo touch /forcefsck > but I found no errors on the disk. > > I have had some problems with ffmpeg( did a apt-get remove and then > install > (I think)) and diskspace (I removed some old kernels), but I do not see > how > that could have anything to do with this..... > > Martin > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > ** > > > From lucas at yorba.org Mon Feb 11 19:10:52 2013 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 11 Feb 2013 11:10:52 -0800 Subject: [Shotwell] database malformed In-Reply-To: References: <51104de8.44133c0a.6347.ffff98fa@mx.google.com> Message-ID: > Could this have something to do > with the (new ) .cache dir? I am > having multiple user access to > the database - using symbolic link > to the harddrive where the photos > and the .shotwell dir is. In theory, the new .cache directory shouldn't have any effect on your Shotwell database. The only thing that gets stored in the ~/.cache directory are thumbnails, and Shotwell is capable of regenerating these if they go missing. Note that the switch to using the ~/.cache directory was motivated by the fact that ~/.cache is the preferred directory for storing temporary, replaceable information (like thumbnails) as per the XDG spec. One thing I will say, however, is that accessing a single Shotwell database by multiple users is unsupported and can lead to database corruption. We have an entry in the Shotwell FAQ that discusses this under the heading "Can I access a Shotwell library across a network, possibly from multiple machines?" that mentions the possibility of database corruption explicitly. While the FAQ entry speaks to the network share use case, the same would be true for multiple user accounts on the same physical machine. Cheers, Lucas On Sun, Feb 10, 2013 at 4:02 PM, Martin Album Ytre-Eide wrote: > Thanks for your ansver. > > Shotwell starts without any error message. It is only when I check the > database for errors that I get the error messages (see first mail). > > I will se if I find some rescue tools or look at the database and try to > see whats wrong. > > I am missisng about two years of photos. I can see all videos and photos > older than about two years. > > Could this have something to do with the (new ) .cache dir? I am having > multiple user access to the database - using symbolic link to the harddrive > where the photos and the .shotwell dir is. > > Martin > > 2013/2/5 Jim Nelson > >> Unfortunately, no. If your photo.db and its backup are both malformed, I >> think you're out of luck. You might search for advanced SQLite recovery >> tools, but I don't know of any other than the command-line tools SQLite >> provides. >> >> Does Shotwell even start with this malformed database? You say you get >> error messages for your photos. What kinds of error messages? >> >> -- Jim >> >> >> On Sat, Feb 2, 2013 at 3:50 PM, Martin Album Ytre-Eide >> wrote: >> >> Hello all. >> >> My shotwell database is malformed and I can't find a solution for it. >> >> The problem is that a lot of pictures won't show up in shotwell (but >> videos >> do) no error message. >> >> I had a look at: >> http://askubuntu.com/questions/58295...ed-shotwell-db** >> >> so I tried restoring the database (from photo.db.back) without any luck - >> it has the same issues. >> >> The pragma integrity_check gives: >> >> sqlite> pragma integrity_check; >> *** in database main *** >> Page 1090: btreeInitPage() returns error code 11 >> On tree page 996 cell 6: Child page depth differs >> On tree page 996 cell 7: Child page depth differs >> Page 29: btreeInitPage() returns error code 11 >> On tree page 27 cell 2: Child page depth differs >> On tree page 27 cell 3: Child page depth differs >> Error: database disk image is malformed >> >> I run ubuntu 12.10 and shotwell 0.13.1. I am missing about two year of >> photos in shotwell (I have the photos of course) >> >> Any ideas to fix this? >> >> I have also run a check on the disk's with >> sudo touch /forcefsck >> but I found no errors on the disk. >> >> I have had some problems with ffmpeg( did a apt-get remove and then >> install >> (I think)) and diskspace (I removed some old kernels), but I do not see >> how >> that could have anything to do with this..... >> >> Martin >> _______________________________________________ >> 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 Mon Feb 11 19:20:35 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 11 Feb 2013 19:12:35 -0008 Subject: [Shotwell] Object Hierarchy explorer In-Reply-To: References: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> Message-ID: <51194481.c54f420a.480a.48f4@mx.google.com> This doesn't show a class hierarchy, but it does allow you to browse the current class' symbols in an orderly fashion: http://blog.yorba.org/eric/2012/05/gedit-class-browser-for-vala.html -- Jim On Sat, Feb 9, 2013 at 3:28 AM, Jens B. wrote: There is Vala Toys for gEdit: https://code.google.com/p/vtg/ This provides some structural tools, like quickly jumping to a class or function, but I find it a little laggy... Maybe thats just me though. I haven't used it really, but looks allright. I don't know if that is what you are looking for. _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From jim at yorba.org Mon Feb 11 19:21:40 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 11 Feb 2013 19:13:40 -0008 Subject: [Shotwell] Development tools In-Reply-To: <20130209110602.GD30702@gamma.logic.tuwien.ac.at> References: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> <511047f5.cb0d320a.75ad.05b2@mx.google.com> <20130209093232.GB30702@gamma.logic.tuwien.ac.at> <20130209110602.GD30702@gamma.logic.tuwien.ac.at> Message-ID: <511944c1.ef98320a.3220.3f14@mx.google.com> One thing to note is that you can set those environment variables in your .bashrc and never have to worry about them again: export SHOTWELL_LOG=1 export SHOTWELL_LOG_FILE=:console: -- Jim On Sat, Feb 9, 2013 at 3:06 AM, Norbert Preining wrote: On Sa, 09 Feb 2013, Jens B. wrote: > SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: ./shotwell Umpf, thanks. Ok, I will remain with stdout.printf, that is easier and I don't need to remember the wonderful cmd line above ;-) Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From preining at logic.at Tue Feb 12 22:24:35 2013 From: preining at logic.at (Norbert Preining) Date: Wed, 13 Feb 2013 07:24:35 +0900 Subject: [Shotwell] Object Hierarchy explorer In-Reply-To: <51194481.c54f420a.480a.48f4@mx.google.com> References: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> <51194481.c54f420a.480a.48f4@mx.google.com> Message-ID: <20130212222435.GK6296@gamma.logic.tuwien.ac.at> On Mo, 11 Feb 2013, Jim Nelson wrote: > http://blog.yorba.org/eric/2012/05/gedit-class-browser-for-vala.html Thanks, that is a nice post. Already done. But still, I am not a gedit guy, I need vim ... ;-) > There is Vala Toys for gEdit: https://code.google.com/p/vtg/ Also not bad. Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From preining at logic.at Tue Feb 12 22:25:25 2013 From: preining at logic.at (Norbert Preining) Date: Wed, 13 Feb 2013 07:25:25 +0900 Subject: [Shotwell] Development tools In-Reply-To: <511944c1.ef98320a.3220.3f14@mx.google.com> References: <37C6CEA8-8B92-44EE-8129-54F4E0B9D8CF@logic.at> <511047f5.cb0d320a.75ad.05b2@mx.google.com> <20130209093232.GB30702@gamma.logic.tuwien.ac.at> <20130209110602.GD30702@gamma.logic.tuwien.ac.at> <511944c1.ef98320a.3220.3f14@mx.google.com> Message-ID: <20130212222525.GL6296@gamma.logic.tuwien.ac.at> On Mo, 11 Feb 2013, Jim Nelson wrote: > export SHOTWELL_LOG=1 > export SHOTWELL_LOG_FILE=:console: Thanks, yes of course, that might work. I will see what I do, but for now I can remain with stdout.printf ;-) Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From blklists at elementarea.net Tue Feb 12 22:29:42 2013 From: blklists at elementarea.net (Andreas Brauchli) Date: Tue, 12 Feb 2013 23:29:42 +0100 Subject: [Shotwell] Object Hierarchy explorer In-Reply-To: <20130212222435.GK6296@gamma.logic.tuwien.ac.at> References: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> <51194481.c54f420a.480a.48f4@mx.google.com> <20130212222435.GK6296@gamma.logic.tuwien.ac.at> Message-ID: <1360708182.1879.2.camel@thinky> Hi Norbert On Mit, 2013-02-13 at 07:24 +0900, Norbert Preining wrote: > On Mo, 11 Feb 2013, Jim Nelson wrote: > > http://blog.yorba.org/eric/2012/05/gedit-class-browser-for-vala.html > > Thanks, that is a nice post. Already done. > > But still, I am not a gedit guy, I need vim ... ;-) then that might be of interest http://sophiaongnome.wordpress.com/2012/01/31/how-do-i-set-up-my-vala-ide-in-vim/ i use just the tagbar but you may like the rest > > > There is Vala Toys for gEdit: https://code.google.com/p/vtg/ > > Also not bad. > > Norbert cheers From preining at logic.at Tue Feb 12 23:08:21 2013 From: preining at logic.at (Norbert Preining) Date: Wed, 13 Feb 2013 08:08:21 +0900 Subject: [Shotwell] Object Hierarchy explorer In-Reply-To: <1360708182.1879.2.camel@thinky> References: <20130209110722.GE30702@gamma.logic.tuwien.ac.at> <51194481.c54f420a.480a.48f4@mx.google.com> <20130212222435.GK6296@gamma.logic.tuwien.ac.at> <1360708182.1879.2.camel@thinky> Message-ID: <20130212230821.GM6296@gamma.logic.tuwien.ac.at> Hi Andreas, On Di, 12 Feb 2013, Andreas Brauchli wrote: > http://sophiaongnome.wordpress.com/2012/01/31/how-do-i-set-up-my-vala-ide-in-vim/ NICE, but I cannot get the tagbar to work out ... it opens up empty. Do you have any idea how to track that down? If I do anjuta-tags -f - some-file.vala I get the list of tags, fine. I have in my .vimrc: nmap :TagbarToggle let g:tagbar_ctags_bin = "anjuta-tags" let g:tagbar_type_vala = { \ 'ctagstype' : 'vala', .... (as copied from the author of tagbar's comment. Any idea what might be the problem? Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From clinton at yorba.org Wed Feb 13 03:00:55 2013 From: clinton at yorba.org (Clint Rogers) Date: Tue, 12 Feb 2013 19:00:55 -0800 Subject: [Shotwell] Bug #5681 Message-ID: Good evening, one and all, My name is Clint, and I'm the Yorban tasked with fixing bug #5681, where a camera-raw image will occasionally have multiple identical 'development' .JPEGs produced from it when repeatedly switching the raw image's developer. At the risk of bothering the list, I'd like to ask you all if any of you have encountered this, and if so, what you were doing when it occurred. I have seen it on occasion, but, unfortunately, I'm not able to reproduce it reliably enough to code up a patch for it, and I'm hoping that either one of you knows how to reproduce this reliably, or, barring that, we can get several reports of this together and back onto a repro case from the common bits between them. If you have seen this, please let us know right away; we'd like to fix it for you as soon as possible. Cheers, -c -- public struct Box { public static const int HAND_GRENADES = 12; -- from shotwell/src/Box.vala From valentin at sanva.net Wed Feb 20 17:14:39 2013 From: valentin at sanva.net (=?ISO-8859-1?Q?Valent=EDn?=) Date: Wed, 20 Feb 2013 18:14:39 +0100 Subject: [Shotwell] compiling face recogntion In-Reply-To: References: <50290224.8697320a.702f.fffff9f8@mx.google.com> Message-ID: Hi Esteban! First of all, sorry for the huge delay answering your question ?I'm too busy and your mail have got stuck in my *todo* list... If you're still interested in compiling Shotwell with faces tool and face detection ?there is not face recognition yet?, let me tell you that I've posted simple instructions to do so in Ubuntu 12.10 at [1]. Cheers! (: [1] http://sanva.net/blog/118/ 2012/9/5 Lucas Beeler > Hi Esteban, > > You can't install or use the Faces Tool yet. Valentin and I are still > working to glue the two parts of his project together. The first part > is the Faces Tool UI in Shotwell and the second part is a family of > helper programs written in C++ that Shotwell spawns as external > processes to do face detection and recognition. I'm hoping that we'll > get these two parts integrated and then commit the integrated whole to > a branch in the Yorba repo within the next few weeks. Once that > happens, you should be able to pull from that branch to get Faces Tool > support. > > Cheers, > Lucas > > On Fri, Aug 31, 2012 at 9:38 PM, Esteban Cervetto > wrote: > > I would like how can i install the FaceTool > > http://redmine.yorba.org/projects/shotwell/wiki/FacesTool implemented > > on August 27, 2012 > > I was installed the old valentin repository > > git clone git://github.com/Sanva/shotwell-gsoc.git > > but only shows a tool that you have to identify manually the faces by > > mean a rectangle tool > > > > and had compiled the ours > > > > I didn't fint it twice! > > > > > > > > > > 2012/8/14 Esteban Cervetto : > >> Hola Valent?n! > >> > >> Estoy siguiendo tu proyecto de detecci?n de rostros. > >> Como usuario final, me gustar?a ser uno de los primeros en probarlo ;-) > >> > >> Lo que no pude hacer fue lograr que Shotwell me reconozca > >> autom?ticamente las caras. Si logre que me permita identificarlas > >> manualmente > >> > >> Compil? lo siguiente: > >> > >> #git init > >> #clono codigo prestado Shotwell > >> #git clone git://github.com/Sanva/shotwell-gsoc.git > >> #le incorporo el desarrollo de facedetect que esta en esta revision > >> #git merge 6c805edfbf0ed0e2a42a38f8efda51003dd5f5f2 > >> > >> luego compilo > >> #./configure --define=ENABLE_FACES > >> #make > >> #./shotwell > >> > >> Hice algo mal? > >> > >> Saludos! > >> > >> > >> > >> > >> 2012/8/13 Adam Dingle : > >>> Esteban, > >>> > >>> there is no face recognition code in Shotwell's git repository, so I'm > not > >>> surprised that you didn't see it. :) Valent?n Barros has been > working on > >>> adding face recognition as a Google Summer of Code project, but none > of his > >>> changes have been committed to trunk yet. You can read about his > progress > >>> on his blog at http://sanva.net/ . If you get in touch with him, he > can > >>> tell you more. We hope to commit some of his changes in time for the > >>> upcoming 0.13 release. Cheers - > >>> > >>> adam > >>> > >>> > >>> On Sun, Aug 12, 2012 at 9:28 PM, Esteban Cervetto < > estebancster at gmail.com> > >>> wrote: > >>> > >>> hello: > >>> > >>> I was compiled the latest version of Shotwell from Git with > >>> > >>> git clone git://yorba.org/shotwell > >>> > >>> but I can't see the face-recognition feature > >>> > >>> I could not figure out the answer to get try face-recognition > >>> > >>> > >>> Regards > >>> > >>> Esteban > >>> _______________________________________________ > >>> Shotwell mailing list > >>> Shotwell at lists.yorba.org > >>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > >>> > >>> > > _______________________________________________ > > Shotwell mailing list > > Shotwell at lists.yorba.org > > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > From hendry.michael at gmail.com Wed Feb 20 22:13:00 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Wed, 20 Feb 2013 22:13:00 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> Message-ID: <56BC1D82-F44E-4AA5-8C4F-DDFB7C30F2E9@gmail.com> On 5 Feb 2013, at 16:32, Michael Hendry wrote: > > On 5 Feb 2013, at 08:33, Michael Hendry wrote: > >> >> On 4 Feb 2013, at 20:54, Jim Nelson wrote: >> >>> Great to hear! If it works, it works. >>> >>> We really would like to have a better export/import system for Shotwell to avoid this problem, but for now I'm glad you got this worked out. >>> >>> -- Jim >> >> Unfortunately, I spoke too soon! >> >> I hadn't gone far enough back in my archive to detect "missing" files. Everything looked OK when I only viewed the thumbnails, but when I double-clicked on a thumbnail the thumbnail disappeared, and the image was consigned to the Missing folder. >> >> I had done some reorganisation of the location of files on my Ubuntu computer when I upgraded to 12.04 from 10.04 and incorporated a new hard disc, but didn't check that everything was working correctly in that environment. >> >> Back to the drawing board for me! >> >> Inevitably, as disc capacity becomes exhausted or failing discs are replaced, there will be a need for photo-archives to be moved around on the same computer, or shifted to new ones, and Shotwell needs to support this, >> >> My first thought on how this would look would be a Nautilus-like presentation of the filesystem, restricted to files "known to" Shotwell. Dragging-and-Dropping of folders or individual files could then be tracked by Shotwell, and the database adjusted accordingly. >> >> Michael > > PS The only other table I could find in the database which refers to file paths is BackingPhotoTable. > > I have made appropriate adjustments to these paths to fit the new environment on my iMac, and this seems to have sorted the Missing Files problem. I may still be speaking too soon.. > > Michael All still appears to be well with my system following the database adjustments, but i've come up with a different kind of problem - changing the directory into which Shotwell imports images from a camera. Edit=>Preferences doesn't offer any means of changing the destination directory, and there's no reference to it in the various %gconf.xml files on my Parallels Virtual Machine. However, my old Ubuntu system has a reference to it... CAMERA /home/michael/Pictures %Y/%m/%d I don't want to go messing around with a text editor on an XML file if I can avoid it - there's surely an "official" way of changing import_dir. Michael From eric at yorba.org Thu Feb 21 00:11:17 2013 From: eric at yorba.org (Eric Gregory) Date: Wed, 20 Feb 2013 16:11:17 -0800 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: <56BC1D82-F44E-4AA5-8C4F-DDFB7C30F2E9@gmail.com> References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> <56BC1D82-F44E-4AA5-8C4F-DDFB7C30F2E9@gmail.com> Message-ID: On Wed, Feb 20, 2013 at 2:13 PM, Michael Hendry wrote: > > On 5 Feb 2013, at 16:32, Michael Hendry wrote: > > > > > On 5 Feb 2013, at 08:33, Michael Hendry > wrote: > > > >> > >> On 4 Feb 2013, at 20:54, Jim Nelson wrote: > >> > >>> Great to hear! If it works, it works. > >>> > >>> We really would like to have a better export/import system for > Shotwell to avoid this problem, but for now I'm glad you got this worked > out. > >>> > >>> -- Jim > >> > >> Unfortunately, I spoke too soon! > >> > >> I hadn't gone far enough back in my archive to detect "missing" files. > Everything looked OK when I only viewed the thumbnails, but when I > double-clicked on a thumbnail the thumbnail disappeared, and the image was > consigned to the Missing folder. > >> > >> I had done some reorganisation of the location of files on my Ubuntu > computer when I upgraded to 12.04 from 10.04 and incorporated a new hard > disc, but didn't check that everything was working correctly in that > environment. > >> > >> Back to the drawing board for me! > >> > >> Inevitably, as disc capacity becomes exhausted or failing discs are > replaced, there will be a need for photo-archives to be moved around on the > same computer, or shifted to new ones, and Shotwell needs to support this, > >> > >> My first thought on how this would look would be a Nautilus-like > presentation of the filesystem, restricted to files "known to" Shotwell. > Dragging-and-Dropping of folders or individual files could then be tracked > by Shotwell, and the database adjusted accordingly. > >> > >> Michael > > > > PS The only other table I could find in the database which refers to > file paths is BackingPhotoTable. > > > > I have made appropriate adjustments to these paths to fit the new > environment on my iMac, and this seems to have sorted the Missing Files > problem. I may still be speaking too soon.. > > > > Michael > > All still appears to be well with my system following the database > adjustments, but i've come up with a different kind of problem - changing > the directory into which Shotwell imports images from a camera. > > Edit=>Preferences doesn't offer any means of changing the destination > directory, and there's no reference to it in the various %gconf.xml files > on my Parallels Virtual Machine. > > However, my old Ubuntu system has a reference to it... > > > > type="bool" value="false"/> > type="string"> > CAMERA > > > /home/michael/Pictures > > type="string"> > > > > %Y/%m/%d > > value="true"/> > value="false"/> > > > I don't want to go messing around with a text editor on an XML file if I > can avoid it - there's surely an "official" way of changing import_dir. > > Michael > Hi Michael, What do you mean by "destination directory," exactly? Also, I should mention that Shotwell hasn't used GConf since version 0.10. If you're using a recent version, all the setting are in GSettings. - Eric From hendry.michael at gmail.com Thu Feb 21 18:40:29 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Thu, 21 Feb 2013 18:40:29 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> <56BC1D82-F44E-4AA5-8C4F-DDFB7C30F2E9@gmail.com> Message-ID: <049B4007-1FF3-4CC4-8F2F-F87C8508DC13@gmail.com> On 21 Feb 2013, at 00:11, Eric Gregory wrote: > On Wed, Feb 20, 2013 at 2:13 PM, Michael Hendry wrote: > > On 5 Feb 2013, at 16:32, Michael Hendry wrote: > > > > > On 5 Feb 2013, at 08:33, Michael Hendry wrote: > > > >> > >> On 4 Feb 2013, at 20:54, Jim Nelson wrote: > >> > >>> Great to hear! If it works, it works. > >>> > >>> We really would like to have a better export/import system for Shotwell to avoid this problem, but for now I'm glad you got this worked out. > >>> > >>> -- Jim > >> > >> Unfortunately, I spoke too soon! > >> > >> I hadn't gone far enough back in my archive to detect "missing" files. Everything looked OK when I only viewed the thumbnails, but when I double-clicked on a thumbnail the thumbnail disappeared, and the image was consigned to the Missing folder. > >> > >> I had done some reorganisation of the location of files on my Ubuntu computer when I upgraded to 12.04 from 10.04 and incorporated a new hard disc, but didn't check that everything was working correctly in that environment. > >> > >> Back to the drawing board for me! > >> > >> Inevitably, as disc capacity becomes exhausted or failing discs are replaced, there will be a need for photo-archives to be moved around on the same computer, or shifted to new ones, and Shotwell needs to support this, > >> > >> My first thought on how this would look would be a Nautilus-like presentation of the filesystem, restricted to files "known to" Shotwell. Dragging-and-Dropping of folders or individual files could then be tracked by Shotwell, and the database adjusted accordingly. > >> > >> Michael > > > > PS The only other table I could find in the database which refers to file paths is BackingPhotoTable. > > > > I have made appropriate adjustments to these paths to fit the new environment on my iMac, and this seems to have sorted the Missing Files problem. I may still be speaking too soon.. > > > > Michael > > All still appears to be well with my system following the database adjustments, but i've come up with a different kind of problem - changing the directory into which Shotwell imports images from a camera. > > Edit=>Preferences doesn't offer any means of changing the destination directory, and there's no reference to it in the various %gconf.xml files on my Parallels Virtual Machine. > > However, my old Ubuntu system has a reference to it... > > > > > > CAMERA > > > /home/michael/Pictures > > > > > > %Y/%m/%d > > > > > > I don't want to go messing around with a text editor on an XML file if I can avoid it - there's surely an "official" way of changing import_dir. > > Michael > > > Hi Michael, > > What do you mean by "destination directory," exactly? > > Also, I should mention that Shotwell hasn't used GConf since version 0.10. If you're using a recent version, all the setting are in GSettings. > > - Eric Thanks, Eric. When I plug my camera into my iMac on which a Virtual Machine is running Ubuntu 12.04, Shotwell opens, and lists a "Mass Storage Camera" in the sidebar. I can "Import All" of the images on the camera, or select the ones I want, but when I do so they go into the default directory, which is /home/parallels/Pictures. I don't want the images to end up within the VIrtual Machine, but in the standard directory structure on my Mac. Parallels provides this through a feature called "Parallels Shared Folders" on the Ubuntu VM's desktop. The destination I would like to send images from my camera to is... /home/parallels/Desktop/Parallels Shared Folders/Home/Pictures/Shotwell Library/ ?instead of? /home/parallels/Pictures There must surely be provision for this to be changed within Shotwell, I just can't find it! (hence my poking around in files that looked as though they might be configuration files). Michael From lucas at yorba.org Thu Feb 21 18:55:09 2013 From: lucas at yorba.org (Lucas Beeler) Date: Thu, 21 Feb 2013 10:55:09 -0800 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: <049B4007-1FF3-4CC4-8F2F-F87C8508DC13@gmail.com> References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> <56BC1D82-F44E-4AA5-8C4F-DDFB7C30F2E9@gmail.com> <049B4007-1FF3-4CC4-8F2F-F87C8508DC13@gmail.com> Message-ID: Hi Michael, In the Shotwell Preferences window, on the Library pane, there should be a combo box labelled "Import photos to:" Does this combo box not appear in your version of Shotwell? Lucas On Thu, Feb 21, 2013 at 10:40 AM, Michael Hendry wrote: > > On 21 Feb 2013, at 00:11, Eric Gregory wrote: > >> On Wed, Feb 20, 2013 at 2:13 PM, Michael Hendry wrote: >> >> On 5 Feb 2013, at 16:32, Michael Hendry wrote: >> >> > >> > On 5 Feb 2013, at 08:33, Michael Hendry wrote: >> > >> >> >> >> On 4 Feb 2013, at 20:54, Jim Nelson wrote: >> >> >> >>> Great to hear! If it works, it works. >> >>> >> >>> We really would like to have a better export/import system for Shotwell to avoid this problem, but for now I'm glad you got this worked out. >> >>> >> >>> -- Jim >> >> >> >> Unfortunately, I spoke too soon! >> >> >> >> I hadn't gone far enough back in my archive to detect "missing" files. Everything looked OK when I only viewed the thumbnails, but when I double-clicked on a thumbnail the thumbnail disappeared, and the image was consigned to the Missing folder. >> >> >> >> I had done some reorganisation of the location of files on my Ubuntu computer when I upgraded to 12.04 from 10.04 and incorporated a new hard disc, but didn't check that everything was working correctly in that environment. >> >> >> >> Back to the drawing board for me! >> >> >> >> Inevitably, as disc capacity becomes exhausted or failing discs are replaced, there will be a need for photo-archives to be moved around on the same computer, or shifted to new ones, and Shotwell needs to support this, >> >> >> >> My first thought on how this would look would be a Nautilus-like presentation of the filesystem, restricted to files "known to" Shotwell. Dragging-and-Dropping of folders or individual files could then be tracked by Shotwell, and the database adjusted accordingly. >> >> >> >> Michael >> > >> > PS The only other table I could find in the database which refers to file paths is BackingPhotoTable. >> > >> > I have made appropriate adjustments to these paths to fit the new environment on my iMac, and this seems to have sorted the Missing Files problem. I may still be speaking too soon.. >> > >> > Michael >> >> All still appears to be well with my system following the database adjustments, but i've come up with a different kind of problem - changing the directory into which Shotwell imports images from a camera. >> >> Edit=>Preferences doesn't offer any means of changing the destination directory, and there's no reference to it in the various %gconf.xml files on my Parallels Virtual Machine. >> >> However, my old Ubuntu system has a reference to it... >> >> >> >> >> >> CAMERA >> >> >> /home/michael/Pictures >> >> >> >> >> >> %Y/%m/%d >> >> >> >> >> >> I don't want to go messing around with a text editor on an XML file if I can avoid it - there's surely an "official" way of changing import_dir. >> >> Michael >> >> >> Hi Michael, >> >> What do you mean by "destination directory," exactly? >> >> Also, I should mention that Shotwell hasn't used GConf since version 0.10. If you're using a recent version, all the setting are in GSettings. >> >> - Eric > > > Thanks, Eric. > > When I plug my camera into my iMac on which a Virtual Machine is running Ubuntu 12.04, Shotwell opens, and lists a "Mass Storage Camera" in the sidebar. > > I can "Import All" of the images on the camera, or select the ones I want, but when I do so they go into the default directory, which is /home/parallels/Pictures. > > I don't want the images to end up within the VIrtual Machine, but in the standard directory structure on my Mac. > > Parallels provides this through a feature called "Parallels Shared Folders" on the Ubuntu VM's desktop. > > The destination I would like to send images from my camera to is... > > /home/parallels/Desktop/Parallels Shared Folders/Home/Pictures/Shotwell Library/ > > ?instead of? > > /home/parallels/Pictures > > There must surely be provision for this to be changed within Shotwell, I just can't find it! (hence my poking around in files that looked as though they might be configuration files). > > Michael > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From hendry.michael at gmail.com Thu Feb 21 19:08:45 2013 From: hendry.michael at gmail.com (Michael Hendry) Date: Thu, 21 Feb 2013 19:08:45 +0000 Subject: [Shotwell] Moving to Mac OS X - What is closest App to Shotwell In-Reply-To: References: <5109414C.7050401@gmail.com> <51097c58.c4c9440a.5b30.ffffd0ff@mx.google.com> <81F9BB85-B88F-4474-82D8-E0003FDC27C5@gmail.com> <510af76f.e5e2440a.01e3.fffff162@mx.google.com> <68040099-8A46-4E75-B0A3-ACC4214742F1@gmail.com> <51101ffd.c64b420a.2bfa.ffffbb74@mx.google.com> <56BC1D82-F44E-4AA5-8C4F-DDFB7C30F2E9@gmail.com> <049B4007-1FF3-4CC4-8F2F-F87C8508DC13@gmail.com> Message-ID: On 21 Feb 2013, at 18:55, Lucas Beeler wrote: > Hi Michael, > > In the Shotwell Preferences window, on the Library pane, there should > be a combo box labelled "Import photos to:" Does this combo box not > appear in your version of Shotwell? > > Lucas D'oh! Yes, there is. Sorry to have been so blind! Michael From emmanuel.fraisse at gmail.com Sat Feb 23 18:32:21 2013 From: emmanuel.fraisse at gmail.com (emmanuel FRAISSE) Date: Sat, 23 Feb 2013 19:32:21 +0100 Subject: [Shotwell] remarks on shotwell Message-ID: <51290B35.6090907@gmail.com> Hello, I am using shotwell since a few month. I find it very good, powerfull while simple. I think a few things are missing : - zoom on pictures is too small : it is difficult to quote a picture on a small view (go to full screen or quite full screen would be better) - Have a command line to be able to run batch operation on pictures - Be able to link different evolutions/versions of a picture. Best regards emmanuel fraisse From thomas at xyz.pp.se Sun Feb 24 09:28:31 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 24 Feb 2013 10:28:31 +0100 Subject: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) In-Reply-To: References: Message-ID: Hello I really wanted this so I upgraded to the daily ppa. Installed version 0.13.1+2321~quantal1. After this, no video thumbnails can be created. Tailing .cache/shotwell/shotwell.log during an import I get this: L 30370 2013-02-24 10:17:05 [WRN] VideoSupport.vala:235: Error creating pixbuf: Unrecognized image file format Something wrong with this version regarding thumbnails? Rgds//Thomas On Fri, Feb 22, 2013 at 2:49 AM, wrote: > > Issue #3314 has been updated by Lucas Beeler. > > Resolution set to fixed > > > ---------------------------------------- > Bug #3314: Wrong recognizing of Video recoring date (3gp) > http://redmine.yorba.org/issues/3314#change-22685 > > Author: Anonymous > Status: Closed > Priority: High > Assignee: Lucas Beeler > Category: video > Target version: 0.14.0 > Resolution: fixed > Keywords: > > > Hey there, > > Videos, recorded by my %(=caps)HTC% Desire, are always recognized as > recorded in the year 1945. > > This absolutely makes no sense, since pictures are recognized correctly. > > The format of thos videos is 3gp. > > If I can somehow help you, please comment. > > What also’d be nice, is the option to edit the recording date etc > manually, so the problem could be solved that way. > > Thank you :) > From thomas at xyz.pp.se Sun Feb 24 09:36:24 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 24 Feb 2013 10:36:24 +0100 Subject: [Shotwell] Importing .mp4-files to shotwell, how to get a date Message-ID: Hello I'm converting some old recordings from a DVR we had from .MTS to .MP4. After this, I will import them to shotwell. But I can't get shotwell to automatically detect the date. How can this be done? The old .MTS-filename includes the date. But I can't find any way to write it with avconv. Neither can shotwell use the file dates, right? Tried writing date as metadata with avconv but it doesn't help/doesn't work. for i in `find . -iname *.mts`; do FN=`echo $i | awk -F\. '{print $2}'` DATE=`echo $FN | awk -F'/' '{print $2}' | sed 's/\///'` /usr/bin/avconv -y -i "$i" -crf 25.0 -vcodec libx264 -acodec libvo_aacenc -ar 48000 -ab 160k -coder 1 -flags +loop -cmp +chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method hex -subq 6 -me_range 16 -g 250 -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -b_strategy 1 -qcomp 0.6 -qmin 0 -qmax 69 -qdiff 4 -bf 3 -refs 8 -directpred 3 -trellis 2 -flags2 +bpyramid+mixed_refs+wpred+dct8x8+fastpskip -wpredp 2 -rc_lookahead 60 -threads 0 -metadata date=2012-"$DATE" ."$FN".mp4 Suggestions are welcome.. Rgds//Thomas From schnouki at schnouki.net Sun Feb 24 09:45:44 2013 From: schnouki at schnouki.net (Thomas Jost) Date: Sun, 24 Feb 2013 10:45:44 +0100 Subject: [Shotwell] Importing .mp4-files to shotwell, how to get a date In-Reply-To: References: Message-ID: You can use exiftool, with something similar to this: exiftool -p -CreateDate="%Y:%m:%d %H:%M:%S" file.mp4 Here's a little Python3 script I wrote about a year ago to do it with all the relevant MP4 tags: http://pastebin.com/HTQZMqKX Cheers, Thomas Le 24/02/2013 10:36, Thomas Novin a ?crit?: > Hello > > I'm converting some old recordings from a DVR we had from .MTS to > .MP4. > After this, I will import them to shotwell. But I can't get shotwell > to > automatically detect the date. > > How can this be done? The old .MTS-filename includes the date. But I > can't > find any way to write it with avconv. Neither can shotwell use the > file > dates, right? > > Tried writing date as metadata with avconv but it doesn't > help/doesn't work. > > for i in `find . -iname *.mts`; do > > FN=`echo $i | awk -F\. '{print $2}'` > DATE=`echo $FN | awk -F'/' '{print $2}' | sed 's/\///'` > > /usr/bin/avconv -y -i "$i" -crf 25.0 -vcodec libx264 -acodec > libvo_aacenc > -ar 48000 -ab 160k -coder 1 -flags +loop -cmp +chroma -partitions > +parti4x4+partp8x8+partb8x8 -me_method hex -subq 6 -me_range 16 -g > 250 > -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -b_strategy 1 -qcomp > 0.6 > -qmin 0 -qmax 69 -qdiff 4 -bf 3 -refs 8 -directpred 3 -trellis 2 > -flags2 > +bpyramid+mixed_refs+wpred+dct8x8+fastpskip -wpredp 2 -rc_lookahead > 60 > -threads 0 -metadata date=2012-"$DATE" ."$FN".mp4 > > Suggestions are welcome.. > > Rgds//Thomas > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell -- Thomas/Schnouki From thomas at xyz.pp.se Sun Feb 24 13:14:32 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 24 Feb 2013 14:14:32 +0100 Subject: [Shotwell] Importing .mp4-files to shotwell, how to get a date In-Reply-To: References: Message-ID: That looks like exactly what I want, thanks! However, testing it, it doesn't seem to work? $ exifdate.py -s 2010-04-02_10:00:46 20100402100046.mp4 $ exiftool 20100402100046.mp4 | grep -i date File Modification Date/Time : 2013:02:24 14:10:13+01:00 Create Date : 1904:01:01 00:00:00 Modify Date : 1904:01:01 00:00:00 Track Create Date : 1904:01:01 00:00:00 Track Modify Date : 1904:01:01 00:00:00 Media Create Date : 1904:01:01 00:00:00 Media Modify Date : 1904:01:01 00:00:00 Rgds//Thomas On Sun, Feb 24, 2013 at 10:45 AM, Thomas Jost wrote: > You can use exiftool, with something similar to this: > > exiftool -p -CreateDate="%Y:%m:%d %H:%M:%S" file.mp4 > > Here's a little Python3 script I wrote about a year ago to do it with all > the relevant MP4 tags: http://pastebin.com/HTQZMqKX > > Cheers, > Thomas > > Le 24/02/2013 10:36, Thomas Novin a ?crit : > >> Hello >> >> I'm converting some old recordings from a DVR we had from .MTS to .MP4. >> After this, I will import them to shotwell. But I can't get shotwell to >> automatically detect the date. >> >> How can this be done? The old .MTS-filename includes the date. But I can't >> find any way to write it with avconv. Neither can shotwell use the file >> dates, right? >> >> Tried writing date as metadata with avconv but it doesn't help/doesn't >> work. >> >> for i in `find . -iname *.mts`; do >> >> FN=`echo $i | awk -F\. '{print $2}'` >> DATE=`echo $FN | awk -F'/' '{print $2}' | sed 's/\///'` >> >> /usr/bin/avconv -y -i "$i" -crf 25.0 -vcodec libx264 -acodec libvo_aacenc >> -ar 48000 -ab 160k -coder 1 -flags +loop -cmp +chroma -partitions >> +parti4x4+partp8x8+partb8x8 -me_method hex -subq 6 -me_range 16 -g 250 >> -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -b_strategy 1 -qcomp 0.6 >> -qmin 0 -qmax 69 -qdiff 4 -bf 3 -refs 8 -directpred 3 -trellis 2 -flags2 >> +bpyramid+mixed_refs+wpred+**dct8x8+fastpskip -wpredp 2 -rc_lookahead 60 >> -threads 0 -metadata date=2012-"$DATE" ."$FN".mp4 >> >> Suggestions are welcome.. >> >> Rgds//Thomas >> ______________________________**_________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-**bin/mailman/listinfo/shotwell >> > > -- > Thomas/Schnouki > ______________________________**_________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-**bin/mailman/listinfo/shotwell > From thomas at xyz.pp.se Sun Feb 24 13:27:00 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 24 Feb 2013 14:27:00 +0100 Subject: [Shotwell] Importing .mp4-files to shotwell, how to get a date In-Reply-To: References: Message-ID: http://www.sno.phy.queensu.ca/~phil/exiftool/#supported It say's MP4 isn't even supported writing to? On Sun, Feb 24, 2013 at 2:14 PM, Thomas Novin wrote: > That looks like exactly what I want, thanks! > > However, testing it, it doesn't seem to work? > > $ exifdate.py -s 2010-04-02_10:00:46 20100402100046.mp4 > $ exiftool 20100402100046.mp4 | grep -i date > File Modification Date/Time : 2013:02:24 14:10:13+01:00 > Create Date : 1904:01:01 00:00:00 > Modify Date : 1904:01:01 00:00:00 > Track Create Date : 1904:01:01 00:00:00 > Track Modify Date : 1904:01:01 00:00:00 > Media Create Date : 1904:01:01 00:00:00 > Media Modify Date : 1904:01:01 00:00:00 > > Rgds//Thomas > > On Sun, Feb 24, 2013 at 10:45 AM, Thomas Jost wrote: > >> You can use exiftool, with something similar to this: >> >> exiftool -p -CreateDate="%Y:%m:%d %H:%M:%S" file.mp4 >> >> Here's a little Python3 script I wrote about a year ago to do it with all >> the relevant MP4 tags: http://pastebin.com/HTQZMqKX >> >> Cheers, >> Thomas >> >> Le 24/02/2013 10:36, Thomas Novin a ?crit : >> >>> Hello >>> >>> I'm converting some old recordings from a DVR we had from .MTS to .MP4. >>> After this, I will import them to shotwell. But I can't get shotwell to >>> automatically detect the date. >>> >>> How can this be done? The old .MTS-filename includes the date. But I >>> can't >>> find any way to write it with avconv. Neither can shotwell use the file >>> dates, right? >>> >>> Tried writing date as metadata with avconv but it doesn't help/doesn't >>> work. >>> >>> for i in `find . -iname *.mts`; do >>> >>> FN=`echo $i | awk -F\. '{print $2}'` >>> DATE=`echo $FN | awk -F'/' '{print $2}' | sed 's/\///'` >>> >>> /usr/bin/avconv -y -i "$i" -crf 25.0 -vcodec libx264 -acodec libvo_aacenc >>> -ar 48000 -ab 160k -coder 1 -flags +loop -cmp +chroma -partitions >>> +parti4x4+partp8x8+partb8x8 -me_method hex -subq 6 -me_range 16 -g 250 >>> -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -b_strategy 1 -qcomp 0.6 >>> -qmin 0 -qmax 69 -qdiff 4 -bf 3 -refs 8 -directpred 3 -trellis 2 -flags2 >>> +bpyramid+mixed_refs+wpred+**dct8x8+fastpskip -wpredp 2 -rc_lookahead 60 >>> -threads 0 -metadata date=2012-"$DATE" ."$FN".mp4 >>> >>> Suggestions are welcome.. >>> >>> Rgds//Thomas >>> ______________________________**_________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-**bin/mailman/listinfo/shotwell >>> >> >> -- >> Thomas/Schnouki >> ______________________________**_________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-**bin/mailman/listinfo/shotwell >> > > From leonardof at gnome.org Sun Feb 24 14:27:54 2013 From: leonardof at gnome.org (Leonardo Ferreira Fontenelle) Date: Sun, 24 Feb 2013 11:27:54 -0300 Subject: [Shotwell] Move photos from the Photos folder to te Images folder Message-ID: <1361716074.24879.140661196106065.31A50A83@webmail.messagingengine.com> Like many other people, I used F-Spot for some years, but eventually I moved to Shotwell, and now I'm overall satisfied. There is something that annoys me, though. When I used F-Spot, the photos library was stored in the Photos folder. When I started using Shotwell, it offered to import the photos from F-Spot, and I said yes please. All the info was correctly imported, and the photos stayed in the Photos folder. When I started adding new photos to the library, I was surprised to see them in the Images folder! Now I have two folders for the same purpose: each holds part of the same photo library. I would like to move the photos from the Photos folder to the Images folder, but without breaking Shotwell's database, as it currently expects my older photos to be in the Photos folder. How do I accomplish that? Thanks in advance. -- Leonardo Ferreira Fontenelle http://lattes.cnpq.br/9234772336296638 From thomas at xyz.pp.se Sun Feb 24 17:34:57 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 24 Feb 2013 18:34:57 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? Message-ID: Hello I have been starting to convert some .mts-files to .mp4. The .mts-files didn't have any metadata so I'm now creating time/date so they will be properly added in my library. However, the time will always be wrong in Shotwell, even though it looks good to me? $ avconv -y -i 20101127100202.mts -crf 25.0 -vcodec libx264 -acodec libvo_aacenc -ar 48000 -ab 160k -coder 1 -flags +loop -cmp +chroma -partitions +parti4x4+partp8x8+partb8x8 -me_method hex -subq 6 -me_range 16 -g 250 -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -b_strategy 1 -qcomp 0.6 -qmin 0 -qmax 69 -qdiff 4 -bf 3 -refs 8 -directpred 3 -trellis 2 -flags2 +bpyramid+mixed_refs+wpred+dct8x8+fastpskip -wpredp 2 -rc_lookahead 60 -threads 0 -metadata creation_time="2001-02-03 13:14:15" hej.mp4 avconv version 0.8.5-6:0.8.5-0ubuntu0.12.10.1, Copyright (c) 2000-2012 the Libav developers built on Jan 24 2013 14:52:53 with gcc 4.7.2 Input #0, mpegts, from '20101127100202.mts': Duration: 00:00:03.36, start: 0.477344, bitrate: 16403 kb/s Program 1 Stream #0.0[0x1011]: Video: h264 (High), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc Stream #0.1[0x1100]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s [buffer @ 0x80d3f60] w:1920 h:1080 pixfmt:yuv420p [libx264 @ 0x80d34a0] using SAR=1/1 [libx264 @ 0x80d34a0] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64 [libx264 @ 0x80d34a0] profile High, level 5.0 [libx264 @ 0x80d34a0] 264 - core 123 r2189 35cf912 - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=8 deblock=1:0:0 analyse=0x3:0x111 me=hex subme=6 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=3 weightb=1 open_gop=1 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=60 rc=crf mbtree=1 crf=25.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.41 aq=1:1.00 Output #0, mp4, to 'hej.mp4': Metadata: creation_time : 2001-02-03 13:14:15 encoder : Lavf53.21.1 Stream #0.0: Video: libx264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], q=0-69, 50 tbn, 50 tbc Stream #0.1: Audio: libvo_aacenc, 48000 Hz, stereo, s16, 160 kb/s Stream mapping: Stream #0:0 -> #0:0 (h264 -> libx264) Stream #0:1 -> #0:1 (ac3 -> libvo_aacenc) Press ctrl-c to stop encoding frame= 168 fps= 6 q=-1.0 Lsize= 3767kB time=3.32 bitrate=9293.8kbits/s dup=84 drop=0 $ exiftool hej.mp4 ExifTool Version Number : 9.20 File Name : hej.mp4 Directory : . File Size : 3.7 MB File Modification Date/Time : 2013:02:24 18:31:13+01:00 File Access Date/Time : 2013:02:24 18:31:09+01:00 File Inode Change Date/Time : 2013:02:24 18:31:13+01:00 File Permissions : rw-rw-r-- File Type : MP4 MIME Type : video/mp4 Major Brand : MP4 Base Media v1 [IS0 14496-12:2003] Minor Version : 0.2.0 Compatible Brands : isom, iso2, avc1, mp41 Movie Data Size : 3853000 Movie Header Version : 0 Create Date : 2001:02:03 13:14:15 Modify Date : 2001:02:03 13:14:15 Time Scale : 1000 Duration : 3.37 s Preferred Rate : 1 Preferred Volume : 100.00% Preview Time : 0 s Preview Duration : 0 s Poster Time : 0 s Selection Time : 0 s Selection Duration : 0 s Current Time : 0 s Next Track ID : 3 Track Header Version : 0 Track Create Date : 2001:02:03 13:14:15 Track Modify Date : 2001:02:03 13:14:15 Track ID : 1 Track Duration : 3.36 s Track Layer : 0 Track Volume : 0.00% Image Width : 1920 Image Height : 1080 Graphics Mode : srcCopy Op Color : 0 0 0 Compressor ID : avc1 Source Image Width : 1920 Source Image Height : 1080 X Resolution : 72 Y Resolution : 72 Bit Depth : 24 Video Frame Rate : 50 Matrix Structure : 1 0 0 0 1 0 0 0 1 Media Header Version : 0 Media Create Date : 2001:02:03 13:14:15 Media Modify Date : 2001:02:03 13:14:15 Media Time Scale : 48000 Media Duration : 3.37 s Media Language Code : und Handler Description : SoundHandler Balance : 0 Audio Format : mp4a Audio Channels : 2 Audio Bits Per Sample : 16 Audio Sample Rate : 48000 Handler Type : Metadata Handler Vendor ID : Apple Encoder : Lavf53.21.1 Avg Bitrate : 9.14 Mbps Image Size : 1920x1080 Rotation : 0 When I import this file with Shotwell it reports Date: l?r 3 feb, 2001 Time: 2:14 So the date is right but the time is wrong. Why is this? Rgds//Thomas From thomas at xyz.pp.se Sun Feb 24 17:50:00 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Sun, 24 Feb 2013 18:50:00 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? In-Reply-To: References: Message-ID: On Sun, Feb 24, 2013 at 6:34 PM, Thomas Novin wrote: > > > However, the time will always be wrong in Shotwell, even though it looks good to me? > Btw, I have tested both these two formats YYYY-mm-dd HH:MM:SS ISO 8601 format YYYY-mm-ddTHH:MM:SS Neither works. From christophe.drevet at gmail.com Sun Feb 24 20:56:41 2013 From: christophe.drevet at gmail.com (Christophe Drevet) Date: Sun, 24 Feb 2013 21:56:41 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? In-Reply-To: References: Message-ID: 2013/2/24 Thomas Novin > > ISO 8601 format YYYY-mm-ddTHH:MM:SS > Could it be the timezone missing? Did you try to set the time to something like: 2001:02:03T13:14:15+01:00 or whatever your timezone is? -- Christophe. From thomas at xyz.pp.se Sun Feb 24 23:24:02 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Mon, 25 Feb 2013 00:24:02 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? In-Reply-To: References: Message-ID: On Sun, Feb 24, 2013 at 9:56 PM, Christophe Drevet wrote: > 2013/2/24 Thomas Novin >> >> >> ISO 8601 format YYYY-mm-ddTHH:MM:SS > > > > Could it be the timezone missing? > > Did you try to set the time to something like: 2001:02:03T13:14:15+01:00 or > whatever your timezone is? No, that didn't help. Also my files looks just like others from my new camera. Those files all have the wrong time in Shotwell aswell even though they look good in exiftool. Rgds//TN From schnouki at schnouki.net Mon Feb 25 08:24:26 2013 From: schnouki at schnouki.net (Thomas Jost) Date: Mon, 25 Feb 2013 09:24:26 +0100 Subject: [Shotwell] Importing .mp4-files to shotwell, how to get a date In-Reply-To: References: Message-ID: <87sj4kg5s5.fsf@schnouki.net> My bad, you're right. This was an old script which obviously didn't work on .mp4/.mov files because of exiftools limitations. After that I wrote another one that works fine. Here it is: https://gist.github.com/Schnouki/5028480 It's basically a .mov/.mp4 parser in pure Python that can change datetime fields. I never had any trouble with it, but please make sure to backup your files before using this tool :) Cheers, Thomas Le 24 f?vrier 2013 ? 14:27 CET, Thomas Novin a ?crit : > http://www.sno.phy.queensu.ca/~phil/exiftool/#supported > > It say's MP4 isn't even supported writing to? > > > > On Sun, Feb 24, 2013 at 2:14 PM, Thomas Novin wrote: > >> That looks like exactly what I want, thanks! >> >> However, testing it, it doesn't seem to work? >> >> $ exifdate.py -s 2010-04-02_10:00:46 20100402100046.mp4 >> $ exiftool 20100402100046.mp4 | grep -i date >> File Modification Date/Time : 2013:02:24 14:10:13+01:00 >> Create Date : 1904:01:01 00:00:00 >> Modify Date : 1904:01:01 00:00:00 >> Track Create Date : 1904:01:01 00:00:00 >> Track Modify Date : 1904:01:01 00:00:00 >> Media Create Date : 1904:01:01 00:00:00 >> Media Modify Date : 1904:01:01 00:00:00 >> >> Rgds//Thomas >> >> On Sun, Feb 24, 2013 at 10:45 AM, Thomas Jost wrote: >> >>> You can use exiftool, with something similar to this: >>> >>> exiftool -p -CreateDate="%Y:%m:%d %H:%M:%S" file.mp4 >>> >>> Here's a little Python3 script I wrote about a year ago to do it with all >>> the relevant MP4 tags: http://pastebin.com/HTQZMqKX >>> >>> Cheers, >>> Thomas >>> >>> Le 24/02/2013 10:36, Thomas Novin a ?crit : >>> >>>> Hello >>>> >>>> I'm converting some old recordings from a DVR we had from .MTS to .MP4. >>>> After this, I will import them to shotwell. But I can't get shotwell to >>>> automatically detect the date. >>>> >>>> How can this be done? The old .MTS-filename includes the date. But I >>>> can't >>>> find any way to write it with avconv. Neither can shotwell use the file >>>> dates, right? >>>> >>>> Tried writing date as metadata with avconv but it doesn't help/doesn't >>>> work. >>>> >>>> for i in `find . -iname *.mts`; do >>>> >>>> FN=`echo $i | awk -F\. '{print $2}'` >>>> DATE=`echo $FN | awk -F'/' '{print $2}' | sed 's/\///'` >>>> >>>> /usr/bin/avconv -y -i "$i" -crf 25.0 -vcodec libx264 -acodec libvo_aacenc >>>> -ar 48000 -ab 160k -coder 1 -flags +loop -cmp +chroma -partitions >>>> +parti4x4+partp8x8+partb8x8 -me_method hex -subq 6 -me_range 16 -g 250 >>>> -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -b_strategy 1 -qcomp 0.6 >>>> -qmin 0 -qmax 69 -qdiff 4 -bf 3 -refs 8 -directpred 3 -trellis 2 -flags2 >>>> +bpyramid+mixed_refs+wpred+**dct8x8+fastpskip -wpredp 2 -rc_lookahead 60 >>>> -threads 0 -metadata date=2012-"$DATE" ."$FN".mp4 >>>> >>>> Suggestions are welcome.. >>>> >>>> Rgds//Thomas >>>> ______________________________**_________________ >>>> Shotwell mailing list >>>> Shotwell at lists.yorba.org >>>> http://lists.yorba.org/cgi-**bin/mailman/listinfo/shotwell >>>> >>> >>> -- >>> Thomas/Schnouki >>> ______________________________**_________________ >>> Shotwell mailing list >>> Shotwell at lists.yorba.org >>> http://lists.yorba.org/cgi-**bin/mailman/listinfo/shotwell >>> >> >> -- Thomas/Schnouki From schnouki at schnouki.net Mon Feb 25 08:35:34 2013 From: schnouki at schnouki.net (Thomas Jost) Date: Mon, 25 Feb 2013 09:35:34 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? In-Reply-To: References: Message-ID: <87ppzog59l.fsf@schnouki.net> This is actually a timezone issue. The .mp4/.mov container spec states that "It is strongly recommended that [creation/modification times] should be specified using coordinated universal time (UTC)" (https://developer.apple.com/library/mac/#documentation/QuickTime/QTFF/QTFFChap2/qtff2.html). So your file has a date of 2001-02-03 13:14:15 UTC, which is 14:14:15 GMT+1. Cheers, Thomas Le 25 f?vrier 2013 ? 00:24 CET, Thomas Novin a ?crit : > On Sun, Feb 24, 2013 at 9:56 PM, Christophe Drevet > wrote: >> 2013/2/24 Thomas Novin >>> >>> >>> ISO 8601 format YYYY-mm-ddTHH:MM:SS >> >> >> >> Could it be the timezone missing? >> >> Did you try to set the time to something like: 2001:02:03T13:14:15+01:00 or >> whatever your timezone is? > > No, that didn't help. Also my files looks just like others from my new > camera. Those files all have the wrong time in Shotwell aswell even > though they look good in exiftool. > > Rgds//TN > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell -- Thomas/Schnouki From thomas at xyz.pp.se Mon Feb 25 09:48:09 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Mon, 25 Feb 2013 10:48:09 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? In-Reply-To: <87ppzog59l.fsf@schnouki.net> References: <87ppzog59l.fsf@schnouki.net> Message-ID: But this isn't the full issue, I think it's more that Shotwell does not use 24-hour time maybe.. If I have a file with: Media Create Date : 2013:01:01 13:14:15 This is added with time 2:14 in Shotwell. I have LC_TIME=sv_SE.UTF-8 Rgds//Thomas On Mon, Feb 25, 2013 at 9:35 AM, Thomas Jost wrote: > This is actually a timezone issue. The .mp4/.mov container spec states > that "It is strongly recommended that [creation/modification times] > should be specified using coordinated universal time (UTC)" > (https://developer.apple.com/library/mac/#documentation/QuickTime/QTFF/QTFFChap2/qtff2.html). > > So your file has a date of 2001-02-03 13:14:15 UTC, which is 14:14:15 > GMT+1. > > Cheers, > Thomas > > Le 25 f?vrier 2013 ? 00:24 CET, Thomas Novin a ?crit : >> On Sun, Feb 24, 2013 at 9:56 PM, Christophe Drevet >> wrote: >>> 2013/2/24 Thomas Novin >>>> >>>> >>>> ISO 8601 format YYYY-mm-ddTHH:MM:SS >>> >>> >>> >>> Could it be the timezone missing? >>> >>> Did you try to set the time to something like: 2001:02:03T13:14:15+01:00 or >>> whatever your timezone is? >> >> No, that didn't help. Also my files looks just like others from my new >> camera. Those files all have the wrong time in Shotwell aswell even >> though they look good in exiftool. >> >> Rgds//TN >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > -- > Thomas/Schnouki > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From preining at logic.at Mon Feb 25 13:26:42 2013 From: preining at logic.at (Norbert Preining) Date: Mon, 25 Feb 2013 22:26:42 +0900 Subject: [Shotwell] Move photos from the Photos folder to te Images folder In-Reply-To: <1361716074.24879.140661196106065.31A50A83@webmail.messagingengine.com> References: <1361716074.24879.140661196106065.31A50A83@webmail.messagingengine.com> Message-ID: <20130225132642.GD4424@gamma.logic.tuwien.ac.at> On So, 24 Feb 2013, Leonardo Ferreira Fontenelle wrote: > I would like to move the photos from the Photos folder to the Images > folder, but without breaking Shotwell's database, as it currently > expects my older photos to be in the Photos folder. How do I accomplish > that? I would do the following: - quit shotwell - make a backup copy of the database - physically move the photos - start shotwell - wait normally shotwell finds photos even if you move them around in the used folders. At least that is what happens with all the photos I often move around. If that does not work out, unwind: - quit shotwell - move the photos back - restore the photo db. Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From preining at logic.at Mon Feb 25 13:29:05 2013 From: preining at logic.at (Norbert Preining) Date: Mon, 25 Feb 2013 22:29:05 +0900 Subject: [Shotwell] remarks on shotwell In-Reply-To: <51290B35.6090907@gmail.com> References: <51290B35.6090907@gmail.com> Message-ID: <20130225132905.GE4424@gamma.logic.tuwien.ac.at> Hi Emmanuel, (note that I am in no way related to Yorba, just another user who sometimes program some things for shotwell) On Sa, 23 Feb 2013, emmanuel FRAISSE wrote: > - zoom on pictures is too small : it is difficult to quote a picture on > a small view (go to full screen or quite full screen would be better) I don't understand, do you mean the icon view? > - Have a command line to be able to run batch operation on pictures would be nice, but what kind of operations do you think of? The improvements? > - Be able to link different evolutions/versions of a picture. I think this concept is not in anyway implemented besides the link between raw and jpg. Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ From leonardof at gnome.org Mon Feb 25 15:21:25 2013 From: leonardof at gnome.org (Leonardo Ferreira Fontenelle) Date: Mon, 25 Feb 2013 12:21:25 -0300 Subject: [Shotwell] Move photos from the Photos folder to te Images folder In-Reply-To: <20130225132642.GD4424@gamma.logic.tuwien.ac.at> References: <1361716074.24879.140661196106065.31A50A83@webmail.messagingengine.com> <20130225132642.GD4424@gamma.logic.tuwien.ac.at> Message-ID: <1361805685.858.140661196588329.667C8E84@webmail.messagingengine.com> Wouldn't that make Shotwell lose metadata, e.g. tags? -- Leonardo Ferreira Fontenelle http://lattes.cnpq.br/9234772336296638 Em %:Date:, Norbert Preining escreveu: > On So, 24 Feb 2013, Leonardo Ferreira Fontenelle wrote: > > I would like to move the photos from the Photos folder to the Images > > folder, but without breaking Shotwell's database, as it currently > > expects my older photos to be in the Photos folder. How do I accomplish > > that? > > I would do the following: > - quit shotwell > - make a backup copy of the database > - physically move the photos > - start shotwell > - wait > normally shotwell finds photos even if you move them around in the > used folders. At least that is what happens with all the photos > I often move around. > > If that does not work out, unwind: > - quit shotwell > - move the photos back > - restore the photo db. > > Norbert > > ------------------------------------------------------------------------ > PREINING, Norbert http://www.preining.info > JAIST, Japan TeX Live & Debian Developer > DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 > ------------------------------------------------------------------------ From farrukh.najm at gmail.com Mon Feb 25 15:34:37 2013 From: farrukh.najm at gmail.com (Farrukh Najmi) Date: Mon, 25 Feb 2013 10:34:37 -0500 Subject: [Shotwell] Move photos from the Photos folder to te Images folder In-Reply-To: <1361805685.858.140661196588329.667C8E84@webmail.messagingengine.com> References: <1361716074.24879.140661196106065.31A50A83@webmail.messagingengine.com> <20130225132642.GD4424@gamma.logic.tuwien.ac.at> <1361805685.858.140661196588329.667C8E84@webmail.messagingengine.com> Message-ID: <512B848D.60605@gmail.com> I have moved all metadata to my photos themselves. This makes the metadata go wherever the photos go. I like this change a lot. Just check the checkbox: Edit / Preferences / Metadata / Write ... metadata to photo files On 02/25/2013 10:21 AM, Leonardo Ferreira Fontenelle wrote: > Wouldn't that make Shotwell lose metadata, e.g. tags? > From javajens at gmail.com Mon Feb 25 16:02:05 2013 From: javajens at gmail.com (Jens B.) Date: Mon, 25 Feb 2013 17:02:05 +0100 Subject: [Shotwell] remarks on shotwell In-Reply-To: <20130225132905.GE4424@gamma.logic.tuwien.ac.at> References: <51290B35.6090907@gmail.com> <20130225132905.GE4424@gamma.logic.tuwien.ac.at> Message-ID: For your request of several versions of one photo, I believe the following issue looks similar: http://redmine.yorba.org/issues/2474 I agree with you, I'd too would love to have this ability. Right now I do this with darktable which has a "Duplicate" function. However I don't know if those changes will come anytime soon, the last update to this ticket was 11 months ago. Jens From jim at yorba.org Mon Feb 25 19:55:50 2013 From: jim at yorba.org (Jim Nelson) Date: Mon, 25 Feb 2013 19:47:50 -0008 Subject: [Shotwell] Move photos from the Photos folder to te Images folder In-Reply-To: <512B848D.60605@gmail.com> References: <1361716074.24879.140661196106065.31A50A83@webmail.messagingengine.com> <20130225132642.GD4424@gamma.logic.tuwien.ac.at> <1361805685.858.140661196588329.667C8E84@webmail.messagingengine.com> <512B848D.60605@gmail.com> Message-ID: <512bc1c5.e755420a.02ee.ffffdee3@mx.google.com> To answer a few questions here: - Shotwell doesn't move photos during an F-Spot import since many people want to keep them where they were for sundry reasons. - You can enable metadata writing to store tags and other metadata in the files themselvers. - Norbert's suggestion will work, however. ?Shotwell uses duplication detection and library monitoring to detect when photos are moved. ?If you move them from Photos into Images, Shotwell will detect that during its startup scan and adjust its database accordingly. If you're worried about this, I suggest backing up your database before proceeding: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#How-can-I-back-up-my-Shotwell-library -- Jim On Mon, Feb 25, 2013 at 7:34 AM, Farrukh Najmi wrote: I have moved all metadata to my photos themselves. This makes the metadata go wherever the photos go. I like this change a lot. Just check the checkbox: Edit / Preferences / Metadata / Write ... metadata to photo files On 02/25/2013 10:21 AM, Leonardo Ferreira Fontenelle wrote: > Wouldn't that make Shotwell lose metadata, e.g. tags? > _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From leonardof at gnome.org Mon Feb 25 23:09:52 2013 From: leonardof at gnome.org (Leonardo Ferreira Fontenelle) Date: Mon, 25 Feb 2013 20:09:52 -0300 Subject: [Shotwell] Move photos from the Photos folder to te Images folder Message-ID: <1361833792.27012.140661196809737.3BBA0C07@webmail.messagingengine.com> Thank you all, it worked well as you expected. (BTW, I don't have F-Spot installed anymore.) (PS: sorry for the duplicate messages.) -- Leonardo Ferreira Fontenelle http://lattes.cnpq.br/9234772336296638 Em %:Date:, Jim Nelson escreveu: > To answer a few questions here: > > - Shotwell doesn't move photos during an F-Spot import since many people > want to keep them where they were for sundry reasons. > > - You can enable metadata writing to store tags and other metadata in the > files themselvers. > > - Norbert's suggestion will work, however. ?Shotwell uses duplication > detection and library monitoring to detect when photos are moved. ?If you > move them from Photos into Images, Shotwell will detect that during its > startup scan and adjust its database accordingly. > > If you're worried about this, I suggest backing up your database before > proceeding: > > http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#How-can-I-back-up-my-Shotwell-library > > -- Jim > > On Mon, Feb 25, 2013 at 7:34 AM, Farrukh Najmi > wrote: > > I have moved all metadata to my photos themselves. This makes the > metadata go wherever the photos go. I like this change a lot. > > Just check the checkbox: Edit / Preferences / Metadata / Write ... > metadata to photo files > > On 02/25/2013 10:21 AM, Leonardo Ferreira Fontenelle wrote: > > Wouldn't that make Shotwell lose metadata, e.g. tags? > > > > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From lucas at yorba.org Tue Feb 26 02:53:00 2013 From: lucas at yorba.org (Lucas Beeler) Date: Mon, 25 Feb 2013 18:53:00 -0800 Subject: [Shotwell] Call for Translations: Shotwell 0.14! Message-ID: Howdy Shotwell Fans, Shotwell 0.14 is almost here! This is a big release that includes a lot of new features and fixes, including: * A folder tree in the sidebar provides a directory-hierarchy view of your Shotwell library * Dramatically improved user experience for RAW photographers?long-standing bugs involving RAW developer switching have been fixed * Comprehensive logging of photo and video import, including the ability to save an import log file to disk. The log tracks which files were detected as duplicates as well as files that couldn't be imported due to disk or camera problems. * The Facebook Connector now uses the Facebook Graph API, resulting in a smoother, more stable experience uploading photos and videos to Facebook. As a bonus, Shotwell photo titles now appear as Facebook photo captions! * The Shotwell video subsystem now relies on GStreamer 1.0, making for easier, more stable video import, better video thumbnails, and better handling of video metadata * New slideshow effects, improved Piwigo support, the ability to show and hide the main Shotwell sidebar, and more... These features have introduced new, translatable text strings into Shotwell. Help others worldwide use this new version of Shotwell in their native languages by translating these strings. We invite you to submit updated translation files by Wednesday, March 6th. The latest Shotwell POT files are available here: https://www.transifex.com/projects/p/shotwell/resource/shotwell-core/ (for the Shotwell core program) https://www.transifex.com/projects/p/shotwell/resource/shotwell-extras/ (for the Shotwell Extras plugin pack) If you have any questions about the translation process, we're here to help. Thanks for supporting the Shotwell project. We hope you're as excited about this release as we are! Cheers, Lucas ---------- Lucas Beeler Shotwell Project Technical Lead http://www.yorba.org From rehmann at math.uni-bielefeld.de Tue Feb 26 10:16:42 2013 From: rehmann at math.uni-bielefeld.de (Ulf Rehmann) Date: Tue, 26 Feb 2013 11:16:42 +0100 Subject: [Shotwell] Call for Translations: Shotwell 0.14! How about bug #4300 ? In-Reply-To: (message from Lucas Beeler on Mon, 25 Feb 2013 18:53:00 -0800) Message-ID: <87y5eb2xdh.fsf@rhea.lan> Hi Lucas, Thanks for the good news concerning 0.14! Here is a question: Will the new release contain a fix of bug #4300? See below. Best regards, Ulf ------------------------- Date: Fri, 30 Nov 2012 01:19:40 -0008 From: Jim Nelson Subject: Re: [Shotwell] Again: Bug #4300 Shotwell view state is incorrect at startup To: Ulf Rehmann Cc: shotwell at lists.yorba.org In-Reply-To: <87fw3s7yjx.fsf at rhea.lan> Content-Type: multipart/alternative; boundary="=-gPSIVqCTMVddXW/af6Tv" [1:text/plain Hide] Hi Ulf, I can reproduce the problem you're seeing. ?I've re-opened the bug for 0.14. -- Jim On Thu, Nov 29, 2012 at 3:57 PM, Ulf Rehmann wrote: It seems that bug #4300 is still not fixed (or was revived). Pages rated "Rejected" are initially shown in version 13.0 as well as in 13.1. As far as I can tell, the code to fix this problem as mentioned on http://redmine.yorba.org/issues/4300 is (in slightly modified version) contained in my 13.1 sources, but does not seem to work. I am working on Ubuntu 12.10. Can anybody help? Best regards Ulf _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell [2:text/html Show] From thomas at xyz.pp.se Tue Feb 26 10:38:10 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Tue, 26 Feb 2013 11:38:10 +0100 Subject: [Shotwell] How does shotwell interpret time/date on mp4 video files? In-Reply-To: References: <87ppzog59l.fsf@schnouki.net> Message-ID: Added this ticket for this issue: http://redmine.yorba.org/issues/6431 On Mon, Feb 25, 2013 at 10:48 AM, Thomas Novin wrote: > But this isn't the full issue, I think it's more that Shotwell does > not use 24-hour time maybe.. > > If I have a file with: > > Media Create Date : 2013:01:01 13:14:15 > > This is added with time 2:14 in Shotwell. > > I have LC_TIME=sv_SE.UTF-8 > > Rgds//Thomas > From clinton at yorba.org Tue Feb 26 19:10:55 2013 From: clinton at yorba.org (Clint Rogers) Date: Tue, 26 Feb 2013 11:10:55 -0800 Subject: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) Message-ID: Hi Thomas, On behalf of the team here, I'm sorry you're encountering this. This is actually quite curious; it doesn't sound quite like anything we've ever had reported. Looking at the line in the error message, it looks like the video thumbnailer is producing invalid image data somehow, although why this might be the case is a mystery. Are you seeing it with all videos, or just videos of a certain format? Also, just for completeness' sake, what GStreamer plugins packages (if any) do you have installed? Cheers, -c > From: Thomas Novin > Subject:Re: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) > Date: Sun, 24 Feb 2013 10:28:31 +0100 > To: shotwell > > Hello > > I really wanted this so I upgraded to the daily ppa. Installed > version 0.13.1+2321~quantal1. > > After this, no video thumbnails can be created. Tailing > .cache/shotwell/shotwell.log during an import I get this: > > L 30370 2013-02-24 10:17:05 [WRN] VideoSupport.vala:235: Error creating > pixbuf: Unrecognized image file format > > Something wrong with this version regarding thumbnails? > > Rgds//Thomas From jim at yorba.org Tue Feb 26 19:51:14 2013 From: jim at yorba.org (Jim Nelson) Date: Tue, 26 Feb 2013 19:43:14 -0008 Subject: [Shotwell] Call for Translations: Shotwell 0.14! How about bug #4300 ? In-Reply-To: <87y5eb2xdh.fsf@rhea.lan> References: <87y5eb2xdh.fsf@rhea.lan> Message-ID: <512d1235.0a19440a.63e7.ffff9d99@mx.google.com> Hi Ulf, Yes, we're hoping to have that fixed for 0.14. -- Jim On Tue, Feb 26, 2013 at 2:16 AM, Ulf Rehmann wrote: Hi Lucas, Thanks for the good news concerning 0.14! Here is a question: Will the new release contain a fix of bug #4300? See below. Best regards, Ulf ------------------------- Date: Fri, 30 Nov 2012 01:19:40 -0008 From: Jim Nelson Subject: Re: [Shotwell] Again: Bug #4300 Shotwell view state is incorrect at startup To: Ulf Rehmann Cc: shotwell at lists.yorba.org In-Reply-To: <87fw3s7yjx.fsf at rhea.lan> Content-Type: multipart/alternative; boundary="=-gPSIVqCTMVddXW/af6Tv" [1:text/plain Hide] Hi Ulf, I can reproduce the problem you're seeing. ?I've re-opened the bug for 0.14. -- Jim On Thu, Nov 29, 2012 at 3:57 PM, Ulf Rehmann wrote: It seems that bug #4300 is still not fixed (or was revived). Pages rated "Rejected" are initially shown in version 13.0 as well as in 13.1. As far as I can tell, the code to fix this problem as mentioned on http://redmine.yorba.org/issues/4300 is (in slightly modified version) contained in my 13.1 sources, but does not seem to work. I am working on Ubuntu 12.10. Can anybody help? Best regards Ulf _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell [2:text/html Show] _______________________________________________ Shotwell mailing list Shotwell at lists.yorba.org http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From thomas at xyz.pp.se Wed Feb 27 00:03:42 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Wed, 27 Feb 2013 01:03:42 +0100 Subject: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) In-Reply-To: References: Message-ID: Hello Imported three other file types from three other cameras we have had. .wmv, .mov and .3gp-files. Neither got a thumbnail in Shotwell after import. I have *lots* of gstreamer packages. http://paste.ubuntu.com/5569204/ Rgds//Thomas On Tue, Feb 26, 2013 at 8:10 PM, Clint Rogers wrote: > Hi Thomas, > > On behalf of the team here, I'm sorry you're encountering this. This > is actually quite curious; it doesn't sound quite like anything we've > ever had reported. > > Looking at the line in the error message, it looks like the video > thumbnailer is producing invalid image data somehow, although why this > might be the case is a mystery. Are you seeing it with all videos, or > just videos of a certain format? Also, just for completeness' sake, > what GStreamer plugins packages (if any) do you have installed? > > Cheers, > -c > >> From: Thomas Novin >> Subject:Re: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) >> Date: Sun, 24 Feb 2013 10:28:31 +0100 >> To: shotwell >> >> Hello >> >> I really wanted this so I upgraded to the daily ppa. Installed >> version 0.13.1+2321~quantal1. >> >> After this, no video thumbnails can be created. Tailing >> .cache/shotwell/shotwell.log during an import I get this: >> >> L 30370 2013-02-24 10:17:05 [WRN] VideoSupport.vala:235: Error creating >> pixbuf: Unrecognized image file format >> >> Something wrong with this version regarding thumbnails? >> >> Rgds//Thomas From thomas at xyz.pp.se Thu Feb 28 16:26:32 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Thu, 28 Feb 2013 17:26:32 +0100 Subject: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) In-Reply-To: References: Message-ID: I'm just about to import 565 files/30GB video-files, if I do it now without getting any thumbnails, will these be created later when this is fixed or should I wait? Rgds//Thomas On Wed, Feb 27, 2013 at 1:03 AM, Thomas Novin wrote: > Hello > > Imported three other file types from three other cameras we have had. > > .wmv, .mov and .3gp-files. > > Neither got a thumbnail in Shotwell after import. > > I have *lots* of gstreamer packages. > > http://paste.ubuntu.com/5569204/ > > Rgds//Thomas > > On Tue, Feb 26, 2013 at 8:10 PM, Clint Rogers wrote: >> Hi Thomas, >> >> On behalf of the team here, I'm sorry you're encountering this. This >> is actually quite curious; it doesn't sound quite like anything we've >> ever had reported. >> >> Looking at the line in the error message, it looks like the video >> thumbnailer is producing invalid image data somehow, although why this >> might be the case is a mystery. Are you seeing it with all videos, or >> just videos of a certain format? Also, just for completeness' sake, >> what GStreamer plugins packages (if any) do you have installed? >> >> Cheers, >> -c >> >>> From: Thomas Novin >>> Subject:Re: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) >>> Date: Sun, 24 Feb 2013 10:28:31 +0100 >>> To: shotwell >>> >>> Hello >>> >>> I really wanted this so I upgraded to the daily ppa. Installed >>> version 0.13.1+2321~quantal1. >>> >>> After this, no video thumbnails can be created. Tailing >>> .cache/shotwell/shotwell.log during an import I get this: >>> >>> L 30370 2013-02-24 10:17:05 [WRN] VideoSupport.vala:235: Error creating >>> pixbuf: Unrecognized image file format >>> >>> Something wrong with this version regarding thumbnails? >>> >>> Rgds//Thomas From lucas at yorba.org Thu Feb 28 18:05:39 2013 From: lucas at yorba.org (Lucas Beeler) Date: Thu, 28 Feb 2013 10:05:39 -0800 Subject: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) In-Reply-To: References: Message-ID: Hi Thomas, The general rule is this: take one of your video files and open it in Totem. It Totem can play it, Shotwell should be able to thumbnail it (since they're both wrappers around the underlying GStreamer infrastructure). If Totem can't play the video, then that's a GStreamer issue. If Totem can play a video but Shotwell can't thumbnail it, then that's a Shotwell bug and you should definitely open a bug ticket for it! Lucas On Thu, Feb 28, 2013 at 8:26 AM, Thomas Novin wrote: > I'm just about to import 565 files/30GB video-files, if I do it now > without getting any thumbnails, will these be created later when this > is fixed or should I wait? > > Rgds//Thomas > > On Wed, Feb 27, 2013 at 1:03 AM, Thomas Novin wrote: >> Hello >> >> Imported three other file types from three other cameras we have had. >> >> .wmv, .mov and .3gp-files. >> >> Neither got a thumbnail in Shotwell after import. >> >> I have *lots* of gstreamer packages. >> >> http://paste.ubuntu.com/5569204/ >> >> Rgds//Thomas >> >> On Tue, Feb 26, 2013 at 8:10 PM, Clint Rogers wrote: >>> Hi Thomas, >>> >>> On behalf of the team here, I'm sorry you're encountering this. This >>> is actually quite curious; it doesn't sound quite like anything we've >>> ever had reported. >>> >>> Looking at the line in the error message, it looks like the video >>> thumbnailer is producing invalid image data somehow, although why this >>> might be the case is a mystery. Are you seeing it with all videos, or >>> just videos of a certain format? Also, just for completeness' sake, >>> what GStreamer plugins packages (if any) do you have installed? >>> >>> Cheers, >>> -c >>> >>>> From: Thomas Novin >>>> Subject:Re: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) >>>> Date: Sun, 24 Feb 2013 10:28:31 +0100 >>>> To: shotwell >>>> >>>> Hello >>>> >>>> I really wanted this so I upgraded to the daily ppa. Installed >>>> version 0.13.1+2321~quantal1. >>>> >>>> After this, no video thumbnails can be created. Tailing >>>> .cache/shotwell/shotwell.log during an import I get this: >>>> >>>> L 30370 2013-02-24 10:17:05 [WRN] VideoSupport.vala:235: Error creating >>>> pixbuf: Unrecognized image file format >>>> >>>> Something wrong with this version regarding thumbnails? >>>> >>>> Rgds//Thomas > _______________________________________________ > Shotwell mailing list > Shotwell at lists.yorba.org > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell From thomas at xyz.pp.se Thu Feb 28 20:35:17 2013 From: thomas at xyz.pp.se (Thomas Novin) Date: Thu, 28 Feb 2013 21:35:17 +0100 Subject: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) In-Reply-To: References: Message-ID: Hello Totem can both play them and Nautilus makes thumbnails. This worked in shotwell 13.1 from stable-ppa but stopped working when I upgraded to the daily-ppa. So OK, issue 6452 created. http://redmine.yorba.org/issues/6452 Rgds//Thomas On Thu, Feb 28, 2013 at 7:05 PM, Lucas Beeler wrote: > Hi Thomas, > > The general rule is this: take one of your video files and open it in > Totem. It Totem can play it, Shotwell should be able to thumbnail it > (since they're both wrappers around the underlying GStreamer > infrastructure). If Totem can't play the video, then that's a > GStreamer issue. If Totem can play a video but Shotwell can't > thumbnail it, then that's a Shotwell bug and you should definitely > open a bug ticket for it! > > Lucas > > On Thu, Feb 28, 2013 at 8:26 AM, Thomas Novin wrote: >> I'm just about to import 565 files/30GB video-files, if I do it now >> without getting any thumbnails, will these be created later when this >> is fixed or should I wait? >> >> Rgds//Thomas >> >> On Wed, Feb 27, 2013 at 1:03 AM, Thomas Novin wrote: >>> Hello >>> >>> Imported three other file types from three other cameras we have had. >>> >>> .wmv, .mov and .3gp-files. >>> >>> Neither got a thumbnail in Shotwell after import. >>> >>> I have *lots* of gstreamer packages. >>> >>> http://paste.ubuntu.com/5569204/ >>> >>> Rgds//Thomas >>> >>> On Tue, Feb 26, 2013 at 8:10 PM, Clint Rogers wrote: >>>> Hi Thomas, >>>> >>>> On behalf of the team here, I'm sorry you're encountering this. This >>>> is actually quite curious; it doesn't sound quite like anything we've >>>> ever had reported. >>>> >>>> Looking at the line in the error message, it looks like the video >>>> thumbnailer is producing invalid image data somehow, although why this >>>> might be the case is a mystery. Are you seeing it with all videos, or >>>> just videos of a certain format? Also, just for completeness' sake, >>>> what GStreamer plugins packages (if any) do you have installed? >>>> >>>> Cheers, >>>> -c >>>> >>>>> From: Thomas Novin >>>>> Subject:Re: [Shotwell] [shotwell - Bug #3314] Wrong recognizing of Video recoring date (3gp) >>>>> Date: Sun, 24 Feb 2013 10:28:31 +0100 >>>>> To: shotwell >>>>> >>>>> Hello >>>>> >>>>> I really wanted this so I upgraded to the daily ppa. Installed >>>>> version 0.13.1+2321~quantal1. >>>>> >>>>> After this, no video thumbnails can be created. Tailing >>>>> .cache/shotwell/shotwell.log during an import I get this: >>>>> >>>>> L 30370 2013-02-24 10:17:05 [WRN] VideoSupport.vala:235: Error creating >>>>> pixbuf: Unrecognized image file format >>>>> >>>>> Something wrong with this version regarding thumbnails? >>>>> >>>>> Rgds//Thomas >> _______________________________________________ >> Shotwell mailing list >> Shotwell at lists.yorba.org >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell