I did an strace and after the startup has finished there is tons of this
stuff

  recvmsg(8, 0x7fffce265f10, 0)           = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}, 
{fd=12, events=POLLIN}], 4, 0) = 0 (Timeout)

Occasionally there are also things like this:

  recvmsg(8, 0x7fffce262430, 0)           = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=8, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=8, 
revents=POLLOUT}])
  writev(8, 
[{"5\30\4\0\356\6\200\4\25\2\200\4\342\0\30\0\213\4\6\0\357\6\200\4\356\6\200\4*\0\0\0"...,
 4472}, {NULL, 0}, {"", 0}], 3) = 4472
  recvmsg(8, 0x7fffce265f10, 0)           = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=6, events=POLLIN}, 
{fd=12, events=POLLIN}], 4, 0) = 1 ([{fd=8, revents=POLLIN}])
  recvmsg(8, {msg_name(0)=NULL, 
msg_iov(1)=[{"\301\0\331\34\t\0\200\4\3\0\202\0\36\0r\5\0 
\20\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(8, {msg_name(0)=NULL, 
msg_iov(1)=[{"\301\0\343\34\t\0\200\4\3\0\202\0\36\0r\5\0 
\20\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(8, 0x7fffce265f30, 0)           = -1 EAGAIN (Resource temporarily 
unavailable)

Does that help?

  Titus

On 2014-09-19 Fri 12:25, Jim Nelson wrote:
> How many "Skipping hidden files" messages are you seeing?  More to the 
> point, do they keep appearing or do they eventually stop?
>
> It's possible this is a database issue, but I have a suspicion this is 
> the startup process that checks to verify your photo files are in the 
> places the database last saw them.  What I don't know is why this is 
> continuing without stopping.  Do you have metadata writing turned on?  
> Where are your photos located?  Are they on your local disk, or are 
> they on a USB drive, network storage, etc.?
>
> There is no more verbose logging.  Everything should be written to the 
> log file.
>
> -- Jim
>
> On Fri, Sep 19, 2014 at 12:04 PM, Titus von der Malsburg 
> <[email protected]> wrote:
>> 
>> 
>> This is what I see in the log file:
>> 
>> L 16444 2014-09-19 12:03:19 [MSG] main.vala:385: Shotwell Photo 
>> Manager 0.18.0
>> L 16444 2014-09-19 12:03:19 [MSG] main.vala:43: Verifying database ...
>> L 16444 2014-09-19 12:03:22 [WRN] DirectoryMonitor.vala:916: Skipping 
>> hidden file/directory /home/malsburg/Pictures/.DS_Store
>> 
>> And then many more of the "Skipping hidden file" warnings.  But I 
>> guess
>> these should be ok.
>> 
>> Is is possible that the database is messed up?  Can I just delete it 
>> and
>> have it rebuilt?  If yes, where do I find it.
>> 
>> Is there another way to extract information from the shotwell
>> process.  "shotwell --help" doesn't show a verbose flag.
>> 
>> Thank you!
>> 
>>   Titus
>> 
>> 
>> On 2014-09-19 Fri 11:48, Jim Nelson wrote:
>>>  I don't recall any reported bug similar to this.  It would probably
>>>  help to look in the Shotwell log file 
>>> (~/.cache/shotwell/shotwell.log)
>>>  and see if there's anything suspicious there.
>>> 
>>>  -- Jim
>>> 
>>>  On Sat, Sep 13, 2014 at 1:41 PM, Titus von der Malsburg
>>>  <[email protected]> wrote:
>>>> 
>>>>  Hi list,
>>>> 
>>>>  I'm a happy Shotwell user with a photo library containing around 
>>>> 3000
>>>>  photos that I took over the last two years.  I really like 
>>>> Shotwell's
>>>>  simplicity and straightforwardness.  However, now I encounter a
>>>>  problem
>>>>  that renders Shotwell pretty much unusable.  When I start the 
>>>> program
>>>>  (on Ubuntu 14.04) the GUI comes up and Shotwell consumes 100% of 
>>>> one
>>>>  CPU
>>>>  core.  Shotwell continues to keep this core busy even if I wait a 
>>>> long
>>>>  time and the GUI is only partly responsive: I can look at pictures 
>>>> and
>>>>  change folders but when I empty the trash, the GUI hangs.  
>>>> Likewise,
>>>>  it's not possible to import images from my camera (used to work).  
>>>> I
>>>>  see
>>>>  the message "Starting import" but nothing happens.
>>>> 
>>>>  Is this a known problem?  If yes, how can I fix it?
>>>> 
>>>>  Please let me know if you need further information.
>>>> 
>>>>  Thank you!
>>>> 
>>>>    Titus
>>>>  _______________________________________________
>>>>  shotwell-list mailing list
>>>>  [email protected]
>>>>  https://mail.gnome.org/mailman/listinfo/shotwell-list
>> 

Attachment: signature.asc
Description: PGP signature

_______________________________________________
shotwell-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/shotwell-list

Reply via email to