[Desktop-packages] [Bug 709860] Re: banshee repeat the playing tracks even if repeat is turned off

2014-01-25 Thread Paddy Launch
Andres, yes, can confirm the bug only manifests for me with ogg files
(not mp3) when gapless playback is enabled.

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

Title:
  banshee repeat the playing tracks even if repeat is turned off

Status in “banshee” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: banshee

  I play an album on Banshee, but anormously, banshee keep repeating the
  track, but repeat option is turned off.

  I expected banshee to stop playing at the end of the last track.
  (Playing queue is empty)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: banshee 1.9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
  Uname: Linux 2.6.37-12-generic x86_64
  Architecture: amd64
  Date: Sat Jan 29 20:19:24 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202)
  ProcEnviron:
   LANGUAGE=fr_FR:fr:en_GB:en
   LANG=fr_FR.UTF-8
   LC_MESSAGES=fr_FR.utf8
   SHELL=/bin/bash
  SourcePackage: banshee

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/709860/+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 990831] Re: Repeat always on

2012-12-14 Thread Paddy Launch
*** This bug is a duplicate of bug 709860 ***
https://bugs.launchpad.net/bugs/709860

** This bug has been marked a duplicate of bug 709860
   banshee repeat the playing tracks even if repeat is turned off

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

Title:
  Repeat always on

Status in Banshee Music Player:
  New
Status in “banshee” package in Ubuntu:
  Triaged

Bug description:
  I use ubuntu 12.04 amd64 and banshee 2.4.0-2ubuntu1. I have repeat
  option off (the default setting, I haven't changed it), but when the
  last song of an album is finished then banshee automatic plays the
  first one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/banshee/+bug/990831/+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 830348] Re: desktop contents briefly visible on resume from suspend before lock dialog

2012-06-12 Thread Paddy Launch
This affects me on 12.04 using conventional 3d unity. I just returned to my 
laptop after a several hours, swished my mouse, and the screen came back on, 
unlocked... I thought odd... shouldn't this be locked? and just assumed that 
I must have absent-mindedly unlocked it earlier. I then went to start using the 
laptop, and as soon as I touched the keyboard, the lock screen came up. 
There was a delay of several seconds before the lock came up - it was certainly 
long enough to convince me that the screen was unlocked and ready to use.


** Also affects: unity
   Importance: Undecided
   Status: New

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

Title:
  desktop contents briefly visible on resume from suspend before lock
  dialog

Status in Unity:
  New
Status in Unity 2D:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Incomplete
Status in “unity-2d” package in Ubuntu:
  Confirmed

Bug description:
  This seems like a recent regression on Oneiric (or perhaps I haven't
  noticed it before):

  On resume from suspend, the contents of the desktop are often briefly
  visible before being hidden behind the lock screen.  This is a
  security problem if there happens to be sensitive information on the
  screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/830348/+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 1009527] [NEW] user-accounts panel does not give the option to encrypt a new user's home directory

2012-06-06 Thread Paddy Launch
Public bug reported:

The gnome-control-center user-accounts panel does not give the user the
option to encrypt a new user's home directory.

This omission is clearly a bug, because the user is given the option of
encrypting their own home directory when installing the operating
system, and therefore would certainly expect this functionality to be
available for creating new accounts via the GUI.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Wed Jun  6 15:06:16 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime  0.3.94-0ubuntu2

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

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

Title:
  user-accounts panel does not give the option to encrypt a new user's
  home directory

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  The gnome-control-center user-accounts panel does not give the user
  the option to encrypt a new user's home directory.

  This omission is clearly a bug, because the user is given the option
  of encrypting their own home directory when installing the operating
  system, and therefore would certainly expect this functionality to be
  available for creating new accounts via the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun  6 15:06:16 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1009527/+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 1009527] Re: user-accounts panel does not give the option to encrypt a new user's home directory

2012-06-06 Thread Paddy Launch
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1009527

Title:
  user-accounts panel does not give the option to encrypt a new user's
  home directory

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  The gnome-control-center user-accounts panel does not give the user
  the option to encrypt a new user's home directory.

  This omission is clearly a bug, because the user is given the option
  of encrypting their own home directory when installing the operating
  system, and therefore would certainly expect this functionality to be
  available for creating new accounts via the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun  6 15:06:16 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1009527/+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 1009703] [NEW] brasero intermittently fails to appear on desktop when activated via nautilus context menu

2012-06-06 Thread Paddy Launch
Public bug reported:

Steps to reproduce:

1. In nautilus right-click on an .iso file and select open with brasero disc 
burner
2. If the brasero dialog appears, then click cancel.
3. repeat step 1.

Expected behaviour: Brasero dialog appears

Actual behaviour: nothing appears

pgrep -l brasero shows that a brasero process is running. If you kill
that process, you are then able to get to the brasero dialog by
selecting the option from the context menu.

Note: I first noticed this the very first time I right-click selected
brasero - nothing appeared and there was no feedback. Also, when this
happens, attempting to start brasero from the Dash also results in
nothing happening, no feedback.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: brasero 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Wed Jun  6 20:53:26 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: brasero (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

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

Title:
  brasero intermittently fails to appear on desktop when activated via
  nautilus context menu

Status in “brasero” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. In nautilus right-click on an .iso file and select open with brasero disc 
burner
  2. If the brasero dialog appears, then click cancel.
  3. repeat step 1.

  Expected behaviour: Brasero dialog appears

  Actual behaviour: nothing appears

  pgrep -l brasero shows that a brasero process is running. If you kill
  that process, you are then able to get to the brasero dialog by
  selecting the option from the context menu.

  Note: I first noticed this the very first time I right-click selected
  brasero - nothing appeared and there was no feedback. Also, when this
  happens, attempting to start brasero from the Dash also results in
  nothing happening, no feedback.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: brasero 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun  6 20:53:26 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1009703/+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 1009703] Re: brasero intermittently fails to appear on desktop when activated via nautilus context menu

2012-06-06 Thread Paddy Launch
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/1009703

Title:
  brasero intermittently fails to appear on desktop when activated via
  nautilus context menu

Status in “brasero” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. In nautilus right-click on an .iso file and select open with brasero disc 
burner
  2. If the brasero dialog appears, then click cancel.
  3. repeat step 1.

  Expected behaviour: Brasero dialog appears

  Actual behaviour: nothing appears

  pgrep -l brasero shows that a brasero process is running. If you kill
  that process, you are then able to get to the brasero dialog by
  selecting the option from the context menu.

  Note: I first noticed this the very first time I right-click selected
  brasero - nothing appeared and there was no feedback. Also, when this
  happens, attempting to start brasero from the Dash also results in
  nothing happening, no feedback.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: brasero 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun  6 20:53:26 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1009703/+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 1002075] [NEW] nautilus context menu options incorrectly greyed out

2012-05-20 Thread Paddy Launch
Public bug reported:

** PART I **

Steps to reproduce:

1. Right-click on any file or folder in nautilus that you have
permission to rename.

Expected behaviour:

A Rename option should be available in the context menu for the
selected file or folder.

Actual behaviour:

The Rename option is ALWAYS greyed out. However, clicking on the
greyed out option still allows you to rename the selected file or
folder.

** PART II **

Steps to reproduce:

1. Right-click on any file or folder in nautilus that you have permission to 
read and select Copy from the context menu.
2. Right-click into a blank space in any folder in nautilus for which you have 
write permission.

Expected behaviour:

A Paste option should be available in the context menu.

Actual behaviour:

The Paste option is ALWAYS greyed out. However, clicking on the greyed
out option still allows you to paste the file that you just copied.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sun May 20 22:26:38 2012
EcryptfsInUse: Yes
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '800x550+263+173'
 org.gnome.nautilus.window-state maximized true
 org.gnome.nautilus.window-state side-pane-view 'tree'
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

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

Title:
  nautilus context menu options incorrectly greyed out

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  ** PART I **

  Steps to reproduce:

  1. Right-click on any file or folder in nautilus that you have
  permission to rename.

  Expected behaviour:

  A Rename option should be available in the context menu for the
  selected file or folder.

  Actual behaviour:

  The Rename option is ALWAYS greyed out. However, clicking on the
  greyed out option still allows you to rename the selected file or
  folder.

  ** PART II **

  Steps to reproduce:

  1. Right-click on any file or folder in nautilus that you have permission to 
read and select Copy from the context menu.
  2. Right-click into a blank space in any folder in nautilus for which you 
have write permission.

  Expected behaviour:

  A Paste option should be available in the context menu.

  Actual behaviour:

  The Paste option is ALWAYS greyed out. However, clicking on the
  greyed out option still allows you to paste the file that you just
  copied.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May 20 22:26:38 2012
  EcryptfsInUse: Yes
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+263+173'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state side-pane-view 'tree'
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1002075/+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 1002075] Re: nautilus context menu options incorrectly greyed out

2012-05-20 Thread Paddy Launch
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1002075

Title:
  nautilus context menu options incorrectly greyed out

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  ** PART I **

  Steps to reproduce:

  1. Right-click on any file or folder in nautilus that you have
  permission to rename.

  Expected behaviour:

  A Rename option should be available in the context menu for the
  selected file or folder.

  Actual behaviour:

  The Rename option is ALWAYS greyed out. However, clicking on the
  greyed out option still allows you to rename the selected file or
  folder.

  ** PART II **

  Steps to reproduce:

  1. Right-click on any file or folder in nautilus that you have permission to 
read and select Copy from the context menu.
  2. Right-click into a blank space in any folder in nautilus for which you 
have write permission.

  Expected behaviour:

  A Paste option should be available in the context menu.

  Actual behaviour:

  The Paste option is ALWAYS greyed out. However, clicking on the
  greyed out option still allows you to paste the file that you just
  copied.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May 20 22:26:38 2012
  EcryptfsInUse: Yes
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+263+173'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state side-pane-view 'tree'
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1002075/+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 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2012-05-16 Thread Paddy Launch
I think I'm suffering from this in 12.04. That is to say, I get no sound
when I backspace an empty line in a terminal, and I have set alert
sound to Glass and the Alert volume to maximum. I can hear the sound
when selecting it, but I never hear it in use.

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

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in “gnome-media” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the
  Natty beta 2.  By default, no sound is produced, and several
  misconfigurations make it difficult to produce sound either from the
  PC speaker or Pulse Audio's module-x11-bell.  Not knowing what the
  desired behavior is, I can't say exactly what needs to be fixed.  But
  the combination of the following issues makes the system quite
  obviously broken.

  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.

  2) The X bell volume is set to 0.
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.

  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.

  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)

  5) gnome-volume-control doesn't.
  The Sound Effects tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.

  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.

  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions
  of Ubuntu running on various hardware.

  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.

  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

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

[Desktop-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2012-05-16 Thread Paddy Launch
Also, FWIW, when I log in using Gnome Shell instead of Unity *then* I
can hear the (Glass) alert sound from the terminal.

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

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in “gnome-media” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  This bug is about problems using the system bell in Unity or another
  Compiz-based environment.  For problems using the system bell in
  Ubuntu Classic/Metacity or another Metacity-based environment, please
  see bug #486154.

  The system bell (that beep when you backspace on an empty line on a
  terminal, i.e.) is badly broken using the Unity environment in the
  Natty beta 2.  By default, no sound is produced, and several
  misconfigurations make it difficult to produce sound either from the
  PC speaker or Pulse Audio's module-x11-bell.  Not knowing what the
  desired behavior is, I can't say exactly what needs to be fixed.  But
  the combination of the following issues makes the system quite
  obviously broken.

  1) pcskpr is blacklisted.
  The pcspkr module is necessary for the PC speaker to produce sound.  It is 
blacklisted, so regular users cannot turn the bell on.  It would be nice for 
this to be fixed, but the attitudes displayed in #77010 suggest that it won't 
be.  Nonetheless, I note it here because it interacts with some of the 
following.

  2) The X bell volume is set to 0.
  As reported by `xset q`, the bell volume is 0 when Unity is started.  Both 
the PC speaker and module-x11-bell respect this setting, so the volume must be 
turned up (with `xset b on` or `xset b 100`) for either to work.  Since both 
the PC speaker and module-x11-bell are disabled by default, this setting only 
serves to frustrate attempts to turn them on; it never prevents unwanted sound.

  3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
  This is a system file, not a user file, so users cannot decide whether they 
want this module loaded or not.  They could write a script to unload the module 
at login (and hope the module number doesn't vary between boots), but it would 
be much cleaner to have the modules loaded from a user file, possibly with 
defaults if the user file doesn't exist.

  4) Sample bell.ogg is not loaded.
  When module-x11-bell is loaded, it is told to use the sample bell.ogg.  But 
no sample is loaded into Pulse Audio.  Thus, module-x11-bell traps system bell 
events (keeping them from going to the PC speaker) without producing any sound. 
 If module-x11-bell is loaded, the sample it calls on should be loaded as well. 
 (To fix this, run `pactl upload-sample 
/usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)

  5) gnome-volume-control doesn't.
  The Sound Effects tab of gnome-volume-control offers to set the volume and 
sound for system bell events, but these have no effect.  This is because 
gnome-volume-control is trying to control system bells through metacity.  
Ideally, it should be rewritten to control module-x11-bell instead, but a 
temporary fix could be to simply disable this tab.

  6) System bell settings don't transfer to the Ubuntu Classic environment.
  Because that is using metacity, which has it's own set of problems.  See bug 
#486154.

  This has been from testing in a VM (virtualbox), but all of these
  behaviors have also been seen in Compiz in various previous versions
  of Ubuntu running on various hardware.

  I have reported this bug against several components, as it is really an 
integration issue.  The eventual fix may not involve your component, but please 
do not mark this bug as invalid until we have at least a roadmap for fixing it. 
 Otherwise, I fear responsibility will be passed from component to component 
without anything being fixed.  Rationales:
  Unity - As the overarching environment, Unity should be responsible for 
getting everything integrated.  Additionally, some of the problems relate to 
session startup settings.
  Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
  Gnome Media - Own gnome-volume-control.

  Versions (but note the same behavior has been seen in many earlier versions):
  unity: 3.8.10-0ubuntu2
  pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
  gnome-media: 2.32.0-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+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 832034] Re: Firefox always says Well, this is embarrassing if it was open at logout

2012-05-02 Thread Paddy Launch
Yes, I'm getting this all the time in Pangolin
(12.0+build1-0ubuntu0.12.04.1) too.

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

Title:
  Firefox always says Well, this is embarrassing if it was open at
  logout

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  firefox 7.0~b1+build1+nobinonly-0ubuntu1, Ubuntu Ocelot

  1. Launch Firefox.
  2. Log out.
  3. Log in.
  4. Launch Firefox.

  What happens: Firefox says Well, this is embarrassing, and offers to
  restore your session.

  What should happen: Firefox should just restore your session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/832034/+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 872163] Re: power management unable to put display to sleep

2011-10-17 Thread Paddy Launch
It now seems to work.

** Changed in: gnome-power-manager (Ubuntu)
   Status: New = Invalid

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

Title:
  power management unable to put display to sleep

Status in “gnome-power-manager” package in Ubuntu:
  Invalid

Bug description:
  A recent update appears to have broken gnome-power-preferences. It is no 
longer capable of putting the display to sleep after a specified period of 
inactivity.
  To reproduce:
  1. start gnome-power-preferences
  2. in tab On AC Power set Put display to sleep when inactive for:  to 1 
minute
  3. wait 1 minute (10 minutes, 1 hour, or several hours)

  What I expect to happen: display to switch off after 1 minute.
  What happens: display remains active indefinitely.

  This was working up until the last 7 days or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-power-manager 2.30.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  Architecture: i386
  Date: Tue Oct 11 09:12:59 2011
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 
(20100429.4)
  MachineType: Dell Inc. Inspiron 1018
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=38d38be9-8acd-44f4-8519-f72dd828f186 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/29/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GHG2G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A01
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd07/29/2010:svnDellInc.:pnInspiron1018:pvrA01:rvnDellInc.:rn0GHG2G:rvrA01:cvnDellInc.:ct8:cvrA01:
  dmi.product.name: Inspiron 1018
  dmi.product.version: A01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/872163/+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 872163] Re: power management unable to put display to sleep

2011-10-11 Thread Paddy Launch
** Description changed:

  A recent update appears to have broken gnome-power-preferences. It is no 
longer capable of putting the display to sleep after a specified period of 
inactivity.
  To reproduce:
  1. start gnome-power-preferences
  2. in tab On AC Power set Put display to sleep when inactive for:  to 1 
minute
  3. wait 1 minute (10 minutes, 1 hour, or several hours)
  
  What I expect to happen: display to switch off after 1 minute.
- What happens: display remains inactive indefinitely.
+ What happens: display remains active indefinitely.
  
  This was working up until the last 7 days or so.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-power-manager 2.30.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  Architecture: i386
  Date: Tue Oct 11 09:12:59 2011
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 
(20100429.4)
  MachineType: Dell Inc. Inspiron 1018
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=38d38be9-8acd-44f4-8519-f72dd828f186 ro quiet splash
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/29/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GHG2G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A01
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd07/29/2010:svnDellInc.:pnInspiron1018:pvrA01:rvnDellInc.:rn0GHG2G:rvrA01:cvnDellInc.:ct8:cvrA01:
  dmi.product.name: Inspiron 1018
  dmi.product.version: A01
  dmi.sys.vendor: Dell Inc.

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

Title:
  power management unable to put display to sleep

Status in “gnome-power-manager” package in Ubuntu:
  New

Bug description:
  A recent update appears to have broken gnome-power-preferences. It is no 
longer capable of putting the display to sleep after a specified period of 
inactivity.
  To reproduce:
  1. start gnome-power-preferences
  2. in tab On AC Power set Put display to sleep when inactive for:  to 1 
minute
  3. wait 1 minute (10 minutes, 1 hour, or several hours)

  What I expect to happen: display to switch off after 1 minute.
  What happens: display remains active indefinitely.

  This was working up until the last 7 days or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-power-manager 2.30.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  Architecture: i386
  Date: Tue Oct 11 09:12:59 2011
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 
(20100429.4)
  MachineType: Dell Inc. Inspiron 1018
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=38d38be9-8acd-44f4-8519-f72dd828f186 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/29/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GHG2G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A01
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd07/29/2010:svnDellInc.:pnInspiron1018:pvrA01:rvnDellInc.:rn0GHG2G:rvrA01:cvnDellInc.:ct8:cvrA01:
  dmi.product.name: Inspiron 1018
  dmi.product.version: A01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/872163/+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 872163] [NEW] power management unable to put display to sleep

2011-10-11 Thread Paddy Launch
Public bug reported:

A recent update appears to have broken gnome-power-preferences. It is no longer 
capable of putting the display to sleep after a specified period of inactivity.
To reproduce:
1. start gnome-power-preferences
2. in tab On AC Power set Put display to sleep when inactive for:  to 1 
minute
3. wait 1 minute (10 minutes, 1 hour, or several hours)

What I expect to happen: display to switch off after 1 minute.
What happens: display remains active indefinitely.

This was working up until the last 7 days or so.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic i686
Architecture: i386
Date: Tue Oct 11 09:12:59 2011
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4)
MachineType: Dell Inc. Inspiron 1018
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=38d38be9-8acd-44f4-8519-f72dd828f186 ro quiet splash
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
dmi.bios.date: 07/29/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0GHG2G
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A01
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd07/29/2010:svnDellInc.:pnInspiron1018:pvrA01:rvnDellInc.:rn0GHG2G:rvrA01:cvnDellInc.:ct8:cvrA01:
dmi.product.name: Inspiron 1018
dmi.product.version: A01
dmi.sys.vendor: Dell Inc.

** Affects: gnome-power-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 lucid ubuntu-une

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

Title:
  power management unable to put display to sleep

Status in “gnome-power-manager” package in Ubuntu:
  New

Bug description:
  A recent update appears to have broken gnome-power-preferences. It is no 
longer capable of putting the display to sleep after a specified period of 
inactivity.
  To reproduce:
  1. start gnome-power-preferences
  2. in tab On AC Power set Put display to sleep when inactive for:  to 1 
minute
  3. wait 1 minute (10 minutes, 1 hour, or several hours)

  What I expect to happen: display to switch off after 1 minute.
  What happens: display remains active indefinitely.

  This was working up until the last 7 days or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-power-manager 2.30.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  Architecture: i386
  Date: Tue Oct 11 09:12:59 2011
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 
(20100429.4)
  MachineType: Dell Inc. Inspiron 1018
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=38d38be9-8acd-44f4-8519-f72dd828f186 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/29/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GHG2G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A01
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd07/29/2010:svnDellInc.:pnInspiron1018:pvrA01:rvnDellInc.:rn0GHG2G:rvrA01:cvnDellInc.:ct8:cvrA01:
  dmi.product.name: Inspiron 1018
  dmi.product.version: A01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/872163/+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 872163] Re: power management unable to put display to sleep

2011-10-11 Thread Paddy Launch
I have tested this with a second laptop and found that display
correctly turns off. The problem apparently only manifests on my
netbook.

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

Title:
  power management unable to put display to sleep

Status in “gnome-power-manager” package in Ubuntu:
  New

Bug description:
  A recent update appears to have broken gnome-power-preferences. It is no 
longer capable of putting the display to sleep after a specified period of 
inactivity.
  To reproduce:
  1. start gnome-power-preferences
  2. in tab On AC Power set Put display to sleep when inactive for:  to 1 
minute
  3. wait 1 minute (10 minutes, 1 hour, or several hours)

  What I expect to happen: display to switch off after 1 minute.
  What happens: display remains active indefinitely.

  This was working up until the last 7 days or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-power-manager 2.30.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic i686
  Architecture: i386
  Date: Tue Oct 11 09:12:59 2011
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 
(20100429.4)
  MachineType: Dell Inc. Inspiron 1018
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic 
root=UUID=38d38be9-8acd-44f4-8519-f72dd828f186 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  dmi.bios.date: 07/29/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GHG2G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A01
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd07/29/2010:svnDellInc.:pnInspiron1018:pvrA01:rvnDellInc.:rn0GHG2G:rvrA01:cvnDellInc.:ct8:cvrA01:
  dmi.product.name: Inspiron 1018
  dmi.product.version: A01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/872163/+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