there should be no screensaver on the liveCD

So espresso should signal gnome-screensaver, sounds more like an espresso bug/feature request to me.

Yes, please change the package if need be, I forgot to mention I put gnome-screensaver just because I was not sure if it had to be filed on expresso.

Off topic question: after having tried expresso, I noticed that the keyboard layout choice is VERY limited. For example, it does not have Canadian French (XkbLayout "ca", XKbVariant "fr"). I'd like to know if this is going to stay like this, if I need to file a bug, or if it's just "under work"?

On zo, 2006-03-12 at 01:43 +0000, Jeff Fortin wrote:
> Yes, please change the package if need be, I forgot to mention I put
> gnome-screensaver just because I was not sure if it had to be filed on
> expresso.

I would if launchpad wasn't too broken atm.
--
Dennis K.
 - Linux for human beings - http://www.ubuntu.com
 - Linux voor normale mensen - http://www.ubuntu-nl.org

cross assigned to espresso-frontend-gtk, please add a 30 sec gtk timeout with code similar to the following:

if (access("/usr/bin/gnome-screensaver-command", X_OK) == 0)
  {
          g_spawn_command_line_async( "gnome-screensaver-command --poke >&- 2>&- &", NULL);
  }

that will prevent screensavers to be started.

Doing this in a timeout is pretty horrible. Isn't there a way to temporarily disable it entirely and turn it back on when we're finished?

the problem with deactivating is that it stays deactivated if your app crashes i prefer to simulate activity (which poke does) but indeed you can run gnome-screensaver-command --exit on start of your app and start gnome-screensaver on exit

Espresso should call:

  /usr/bin/gnome-screensaver-command --poke

semi-frequently. An equivalent is probably needed for the KDE version too.

Jeff, regarding your comment above:

  "For example, it does not have Canadian French (XkbLayout "ca", XKbVariant "fr")"

Please file a separate bug for this (although I believe the number of currently available keyboards in Espresso is low).

espresso (0.99.32) dapper; urgency=low

  [ Tollef Fog Heen ]
  * Change dependency on espresso-keyboard-setup to espresso-kbd-chooser,
    since that component moved to another package with a lower version
    number and we don't like epochs.
  * Make the keyboard selector work somewhat sanely -- call back to
    kbd-chooser when the selection is changed.
  * Fix choices_display_map to work correctly and map to the other value
    instead of being an identity map.

  [ Colin Watson ]
  * Update Portuguese translation from Rosetta.
  * GTK frontend:
    - Prevent gnome-screensaver from kicking in while Espresso is running
      (closes: Malone #34510 espresso-frontend-gtk task).
    - Translate window title immediately when changing language.
    - Make title of install progress bar translatable.
    - Make sure that cancelling the installation at the summary page cancels
      partman too.
    - Make "Installation complete" translatable.
  * Make sure that debconffilter never tries to call the same widget more
    than once for a single command.
  * Move more frontend-independent translation logic from the GTK frontend
    to espresso.misc so that other frontends can use it.

 -- Colin Watson <email address hidden> Wed, 22 Mar 2006 10:48:13 +0000

This is assigned to Kubuntu Team. It looks like the GTK front end to espresso was patched to keep the screensaver from popping up during installation, and the same needs to be done in KDE.

Has this been done already, or are there plans to implement this feature?

Wait, this is all wrong. Why is there any screensavers active at all on the liveCD? I think it's not a matter of patching the installer; it's a matter of simply configuring GNOME/KDE/XFCE on the liveCD to not run screensavers at all (just blank the screen if you really want to save screens).

Because even if you are not installing, you *DON'T* want a screensaver starting on the livecd. Especially with hardware that does not have open drivers (thinking of the nvidia people here as an example).

  * GTK frontend:
    - Prevent gnome-screensaver from kicking in while Espresso is running
      (closes: Malone #34510 espresso-frontend-gtk task).

I'm not exactly sure how Colin did this, but if it was like how Oliver suggested in comments 4 and 6, then it just simulated activity while espresso (the live CD installer) was running. The kde frontend for espresso would have to do the same thing to keep the screensaver from running.

If he did it by removing the screensaver entirely, then of course my question of whether or not the KDE frontend had been patched to include that change would be relevant.

Colin: Did you end up poking gnome-screensaver semi-often, or disabling it completely from the live CD? Do you know if the kde frontend had this change added to it?

Thanks

Has this problem been fixed in Feisty's installer?

I have never witnessed this issue during a Kubuntu install at all. Anyone else? Has this been fixed?

I am closing this report for 2 reasons, I don't/haven't experienced this issue and the lack of response. If you feel this is still an issue, I urge you to reopen this report. Thank you.

Not sure, reopening. Yesterday I tested the gnome ubuntu 7.04 liveCD and it was fine (I think), but today I booted the gnome gutsy livecd for tribe 1, and this reappeared.

After a while (10 minutes I would guess) the screensaver kicks in on the liveCD. Did not try the installer, I was just having the computer iddling on the desktop. Maybe there is no screensaver starting during the install, but there should be none starting on the livecd either (because more often than not the user has no working 3D acceleration)

[Expired for gnome-screensaver (Ubuntu) because there has been no activity for 60 days.]