Ubuntu
f-spot package

f-spot-screensaver and gnome-screensaver don't mix

Bug #36531 reported by Matthew Vermeulen
12
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Fix Released
Medium
Andrew Mitchell

Bug Description

I'm running f-spot 0.1.10 and gnome-screensaver 2.4.10 on dapper with the latest updates applied. When f-spot-screensaver turns on, it can take up to a minute to exit on the moving of the mouse, or over a minute for the unlock screen dialogue to be displayed. Additionally, f-spot-screensaver will often start flickering rapidly between a few photos.

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

I haven't been able to test this yet, but does it still occur with f-spot 0.1.11 & the latest gnome-screensaver in dapper now?

Changed in f-spot:
assignee: nobody → ajmitch
Revision history for this message
Matthew Vermeulen (mattvermeulen) wrote :

Doesn't seem as bad, now with f-spot 0.1.11 and latest gnome-screensaver. Just a quite noticable delay when you try to get out of a locked screen, much more than with other screensavers.

Revision history for this message
Matthew Vermeulen (mattvermeulen) wrote :

Another thing I should have mentioned (sorry) is that often after exiting the screensaver, the f-spot screensaver continues in its own window, and has to be quit separately.

Revision history for this message
Adam Zimmerman (adam-zimmerman) wrote :

I can confirm this in dapper final, f-spot 0.1.11-1ubuntu1 and gnome-screensaver 2.14.1-0ubuntu5.

I get all three problems described:
- takes a while for the unlock screen to show up
- flickers back and forth between pictures sometimes
- screensaver continues in its own window sometimes

Changed in f-spot:
status: Unconfirmed → Confirmed
Revision history for this message
Hezekiah Carty (hez) wrote :

Also, if the f-spot screensaver is selected in the gnome-screensaver window and then another screensaver is selected, both will be running in the gnome-screensaver preview pane.

Revision history for this message
Johan Kiviniemi (ion) wrote :

This patch should fix the problem.

The f-spot wrapper is missing an "exec" when running mono. When gnome-screensaver SIGTERMs the f-spot pid, only an instance of /bin/sh is killed, but not the instance of mono that is running f-spot.exe.

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Fixed in 0.1.11-3

Changed in f-spot:
status: Confirmed → Fix Released
Revision history for this message
Johan Kiviniemi (ion) wrote :

Would it be possible to get the fix to dapper-updates as well?

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

I can try - there are a few fixes that should go in there

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.