[Desktop-packages] [Bug 224291] Re: f-spot hangs on exit.

2012-10-29 Thread Thomas Hotz
** Changed in: mono (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: mono (Ubuntu)
   Status: Invalid = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mono in Ubuntu.
https://bugs.launchpad.net/bugs/224291

Title:
  f-spot hangs on exit.

Status in “f-spot” package in Ubuntu:
  Invalid
Status in “mono” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: mono

  Description:  Ubuntu 8.04
  Release:  8.04
  Package: f-spot: /usr/bin/f-spot

  
  To reproduce. Upgraded installation. Start f-spot (either from the command 
line or a menu). Wait for the initial window to appear. Click on File - Exit. 
The application hangs. stracing it shows it stuck in a futex wait. Looks like a 
mono locking issue to me.

  100% reproducible. This is a blocker bug for me to upgrade all my
  desktop machines (f-spot is my primary photo manager).

  strace output when in hung state (endlessly loops):

  gettimeofday({1209483989, 221562}, NULL) = 0
  clock_gettime(CLOCK_REALTIME, {1209483989, 221663850}) = 0
  futex(0x8207aa4, 0x80 /* FUTEX_??? */, 51) = -1 ETIMEDOUT (Connection timed 
out)
  futex(0x8207a80, 0x81 /* FUTEX_??? */, 1) = 0
  semop(131074, 0xbf835a66, 1)= 0
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  semop(131074, 0xbf835a76, 1)= 0
  semop(131074, 0xbf835a66, 1)= 0
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  semop(131074, 0xbf835a76, 1)= 0
  gettimeofday({1209483989, 322863}, NULL) = 0
  clock_gettime(CLOCK_REALTIME, {1209483989, 322973699}) = 0
  futex(0x8207aa4, 0x80 /* FUTEX_??? */, 53 unfinished ...

  Let me know what more you need to track this down. Note this is *NOT*
  the same as the previously reported f-spot crashes on exit segv bugs
  reported, this is a hang.

  Jeremy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/224291/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 224291] Re: f-spot hangs on exit.

2012-10-29 Thread Thomas Hotz
Can you reproduce this error with a newer Ubuntu version?

** Changed in: mono (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mono in Ubuntu.
https://bugs.launchpad.net/bugs/224291

Title:
  f-spot hangs on exit.

Status in “f-spot” package in Ubuntu:
  Invalid
Status in “mono” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mono

  Description:  Ubuntu 8.04
  Release:  8.04
  Package: f-spot: /usr/bin/f-spot

  
  To reproduce. Upgraded installation. Start f-spot (either from the command 
line or a menu). Wait for the initial window to appear. Click on File - Exit. 
The application hangs. stracing it shows it stuck in a futex wait. Looks like a 
mono locking issue to me.

  100% reproducible. This is a blocker bug for me to upgrade all my
  desktop machines (f-spot is my primary photo manager).

  strace output when in hung state (endlessly loops):

  gettimeofday({1209483989, 221562}, NULL) = 0
  clock_gettime(CLOCK_REALTIME, {1209483989, 221663850}) = 0
  futex(0x8207aa4, 0x80 /* FUTEX_??? */, 51) = -1 ETIMEDOUT (Connection timed 
out)
  futex(0x8207a80, 0x81 /* FUTEX_??? */, 1) = 0
  semop(131074, 0xbf835a66, 1)= 0
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  semop(131074, 0xbf835a76, 1)= 0
  semop(131074, 0xbf835a66, 1)= 0
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  semop(131074, 0xbf835a76, 1)= 0
  gettimeofday({1209483989, 322863}, NULL) = 0
  clock_gettime(CLOCK_REALTIME, {1209483989, 322973699}) = 0
  futex(0x8207aa4, 0x80 /* FUTEX_??? */, 53 unfinished ...

  Let me know what more you need to track this down. Note this is *NOT*
  the same as the previously reported f-spot crashes on exit segv bugs
  reported, this is a hang.

  Jeremy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/224291/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Desktop-packages] [Bug 224291] Re: f-spot hangs on exit.

2012-10-29 Thread Dennis Heitmann
No, sorry. I do not use it anymore.

Best regards,

Dennis


Am 2012-10-29 10:00, schrieb Thomas Hotz:
 Can you reproduce this error with a newer Ubuntu version?

 ** Changed in: mono (Ubuntu)
Status: Confirmed = Incomplete

 --
 You received this bug notification because you are subscribed to the 
 bug
 report.
 https://bugs.launchpad.net/bugs/224291

 Title:
   f-spot hangs on exit.

 Status in “f-spot” package in Ubuntu:
   Invalid
 Status in “mono” package in Ubuntu:
   Incomplete

 Bug description:
   Binary package hint: mono

   Description:Ubuntu 8.04
   Release:8.04
   Package: f-spot: /usr/bin/f-spot


   To reproduce. Upgraded installation. Start f-spot (either from the
 command line or a menu). Wait for the initial window to appear. Click
 on File - Exit. The application hangs. stracing it shows it stuck in
 a futex wait. Looks like a mono locking issue to me.

   100% reproducible. This is a blocker bug for me to upgrade all my
   desktop machines (f-spot is my primary photo manager).

   strace output when in hung state (endlessly loops):

   gettimeofday({1209483989, 221562}, NULL) = 0
   clock_gettime(CLOCK_REALTIME, {1209483989, 221663850}) = 0
   futex(0x8207aa4, 0x80 /* FUTEX_??? */, 51) = -1 ETIMEDOUT
 (Connection timed out)
   futex(0x8207a80, 0x81 /* FUTEX_??? */, 1) = 0
   semop(131074, 0xbf835a66, 1)= 0
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   semop(131074, 0xbf835a76, 1)= 0
   semop(131074, 0xbf835a66, 1)= 0
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   time(NULL)  = 1209483989
   semop(131074, 0xbf835a76, 1)= 0
   gettimeofday({1209483989, 322863}, NULL) = 0
   clock_gettime(CLOCK_REALTIME, {1209483989, 322973699}) = 0
   futex(0x8207aa4, 0x80 /* FUTEX_??? */, 53 unfinished ...

   Let me know what more you need to track this down. Note this is 
 *NOT*
   the same as the previously reported f-spot crashes on exit segv 
 bugs
   reported, this is a hang.

   Jeremy.

 To manage notifications about this bug go to:
 
 https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/224291/+subscriptions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mono in Ubuntu.
https://bugs.launchpad.net/bugs/224291

Title:
  f-spot hangs on exit.

Status in “f-spot” package in Ubuntu:
  Invalid
Status in “mono” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mono

  Description:  Ubuntu 8.04
  Release:  8.04
  Package: f-spot: /usr/bin/f-spot

  
  To reproduce. Upgraded installation. Start f-spot (either from the command 
line or a menu). Wait for the initial window to appear. Click on File - Exit. 
The application hangs. stracing it shows it stuck in a futex wait. Looks like a 
mono locking issue to me.

  100% reproducible. This is a blocker bug for me to upgrade all my
  desktop machines (f-spot is my primary photo manager).

  strace output when in hung state (endlessly loops):

  gettimeofday({1209483989, 221562}, NULL) = 0
  clock_gettime(CLOCK_REALTIME, {1209483989, 221663850}) = 0
  futex(0x8207aa4, 0x80 /* FUTEX_??? */, 51) = -1 ETIMEDOUT (Connection timed 
out)
  futex(0x8207a80, 0x81 /* FUTEX_??? */, 1) = 0
  semop(131074, 0xbf835a66, 1)= 0
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  semop(131074, 0xbf835a76, 1)= 0
  semop(131074, 0xbf835a66, 1)= 0
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  time(NULL)  = 1209483989
  semop(131074, 0xbf835a76, 1)= 0
  gettimeofday({1209483989, 322863}, NULL) = 0
  clock_gettime(CLOCK_REALTIME, {1209483989, 322973699}) = 0
  futex(0x8207aa4, 0x80 /* FUTEX_??? */, 53 unfinished ...

  Let me know what more you need to track this down. Note this is *NOT*
  the same as the previously reported f-spot crashes on exit segv bugs
  reported, this is a hang.

  Jeremy.

To