[Desktop-packages] [Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)

[ceg]

No updates, manually setting iso_layout=0 fixed the swapped keys for me,
so someone still needs to fix that module.

-- 
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/1043336

Title:
  Swiss keyboard layout with Apple keyboard (period instead of comma)

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

Bug description:
  It is a known bug that two keys on an Apple keyboard are swapped. There is 
another bug which occurs on Swiss keyboards with an Apple model.
  In Switzerland people have a period instead of a comma on their numpad. Also 
there is something weird with the default mapping of the upper left key below 
"ESC".
  To correct this there is a workaround with xmodmap:

  keycode 91 = period period
  keycode 94 = section degree

  I think this is not the best solution so I report this as a new bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+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 39717] Re: When guest (nobody) account exists, smbpasswd should default to none

[ceg]

seems fixed after the switch to usershares and "usershare allow guests =
yes" + " map to guest = bad user"

** Changed in: gnome-system-tools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  When guest (nobody) account exists, smbpasswd should default to none

Status in “gnome-system-tools” package in Ubuntu:
  Fix Released

Bug description:
  After installing Samba, I expected to be able to simply browse my
  Ubuntu computer from a WinXP machine.  Usually in such a situation the
  remote machine defaults to the "nobody" guest user, for which a
  password is not expected.

  However, after some time of not being able to get this to work, the
  following commands resolved the situation:

  # set nobody to no password
  sudo smbpasswd -n nobody

  # enable nobody user
  sudo smbpasswd -e nobody

  
  It seems to me that this should be the default situation, perhaps with no 
default file shares that have "guest ok" enabled for security reasons.  
However, once the user creates a file share, it should be expected to work 
without having to manually run the smbpasswd command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/39717/+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 268663] Re: files incoming through nautilus-share should be created with user ownership, instead of "nobody"

[ceg]

** Bug watch added: Debian Bug tracker #678834
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834

** Also affects: nautilus-share via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678834
   Importance: Unknown
   Status: Unknown

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

Title:
  files incoming through nautilus-share should be created with user
  ownership, instead of "nobody"

Status in Nautilus Share:
  Unknown
Status in Samba:
  Won't Fix
Status in “nautilus-share” package in Ubuntu:
  New
Status in “samba” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: nautilus-share

  Steps to reproduce
  1- Create a usershare with nautilus (say, ~/Public)
  2- From another computer, send a file to this share

  The file will have ownership to user "nobody" and group "nogroup",
  instead of the userś ownership and starting group. This makes it
  inconvenient to modify these files, especially since there's no easy
  way to change ownership of files and folders (one has to know about
  the nautilus-gksu package, which is not installed by default).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus-share/+bug/268663/+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 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)

[ceg]

The hid_apple module will have set iso_layout=0 for some locales (all
non-US?).

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => Confirmed

-- 
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/1043336

Title:
  Swiss keyboard layout with Apple keyboard (period instead of comma)

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

Bug description:
  It is a known bug that two keys on an Apple keyboard are swapped. There is 
another bug which occurs on Swiss keyboards with an Apple model.
  In Switzerland people have a period instead of a comma on their numpad. Also 
there is something weird with the default mapping of the upper left key below 
"ESC".
  To correct this there is a workaround with xmodmap:

  keycode 91 = period period
  keycode 94 = section degree

  I think this is not the best solution so I report this as a new bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+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 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)

[ceg]

set it _automatically_ of course

-- 
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/1043336

Title:
  Swiss keyboard layout with Apple keyboard (period instead of comma)

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

Bug description:
  It is a known bug that two keys on an Apple keyboard are swapped. There is 
another bug which occurs on Swiss keyboards with an Apple model.
  In Switzerland people have a period instead of a comma on their numpad. Also 
there is something weird with the default mapping of the upper left key below 
"ESC".
  To correct this there is a workaround with xmodmap:

  keycode 91 = period period
  keycode 94 = section degree

  I think this is not the best solution so I report this as a new bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+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 984449] Re: Palimpsest doesn't allow precisely-sized partitions

[ceg]

Forgot to mention: conifirmed the failure to create lage enough raid
partition when trying to extend a raid 1 with another 333MiB sized
parttion (gui shows 349 MB). Nevertheless, it worked with a 18.62GiB
(20GB) raid.

Seems like messing up with with MB and MiB (MiB being the only sane unit
as this is the default alignment anyway.)

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

Title:
  Palimpsest doesn't allow precisely-sized partitions

Status in “gnome-disk-utility” package in Ubuntu:
  Confirmed

Bug description:
  Palimpsest doesn't allow precisely-sized partitions. I need to be able
  to specify the size of a new partition at creation time in Bytes (not
  MiB, GiB, or TiB).

  Not that it matters, but the reason I need to do so is because I have
  an existing RAID5, and I wanted to make a new partition on a new drive
  to add to the RAID, and doing so automatically (by selecting the RAID
  in palimpsest and trying to add the unformatted drive) doesn't work
  (the partition size it creates is too small), and I cannot do it
  manually, because the slider input field is too coarse. I need to be
  able to enter the partition size manually, using my choice of units.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/984449/+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 984449] Re: Palimpsest doesn't allow precisely-sized partitions

[ceg]

PS launchpad is a waste of time, get in contact with upstrem directly.

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

Title:
  Palimpsest doesn't allow precisely-sized partitions

Status in “gnome-disk-utility” package in Ubuntu:
  Confirmed

Bug description:
  Palimpsest doesn't allow precisely-sized partitions. I need to be able
  to specify the size of a new partition at creation time in Bytes (not
  MiB, GiB, or TiB).

  Not that it matters, but the reason I need to do so is because I have
  an existing RAID5, and I wanted to make a new partition on a new drive
  to add to the RAID, and doing so automatically (by selecting the RAID
  in palimpsest and trying to add the unformatted drive) doesn't work
  (the partition size it creates is too small), and I cannot do it
  manually, because the slider input field is too coarse. I need to be
  able to enter the partition size manually, using my choice of units.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/984449/+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 984449] Re: Palimpsest doesn't allow precisely-sized partitions

[ceg]

I'd suggest to report the failure to create raid partition with the
correct (equal, large enough) size as a separate bug.

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

Title:
  Palimpsest doesn't allow precisely-sized partitions

Status in “gnome-disk-utility” package in Ubuntu:
  Confirmed

Bug description:
  Palimpsest doesn't allow precisely-sized partitions. I need to be able
  to specify the size of a new partition at creation time in Bytes (not
  MiB, GiB, or TiB).

  Not that it matters, but the reason I need to do so is because I have
  an existing RAID5, and I wanted to make a new partition on a new drive
  to add to the RAID, and doing so automatically (by selecting the RAID
  in palimpsest and trying to add the unformatted drive) doesn't work
  (the partition size it creates is too small), and I cannot do it
  manually, because the slider input field is too coarse. I need to be
  able to enter the partition size manually, using my choice of units.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/984449/+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 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

[ceg]

** Description changed:

  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543
  
  Release: 11.10
  
- Cause: The password is cleared (which prevents authentification for
- security reasons). However, the user only needs to be added to the
- nopasswordlogin group, to enable passwordless login with gdm (and other
- DMs that ship with a corresponding pam configuration).
+ Cause: The password is cleared to be empty, and this prevents
+ authentification for many admin tasks for security reasons. However, the
+ user only needs to be added to the "nopasswdlogin" group, to enable
+ passwordless login with gdm (and any other DM that ships with a
+ corresponding "auth sufficient pam_succeed_if.so user ingroup
+ nopasswdlogin" configuration).
+ 
+ Fix:
+  * lightdm to add pam rule
+  * account managing tools not clearing password but only adding user to
+"nopasswdlogin" group
+ 
  
  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.
  
  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.
  
  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).
  
  Further notes:
  After disabling the password request at login, the /etc/shadow file related 
to the test user account I created looked like this:
  test::15283:0:9:7:::
  This shows that the password hash is made completely empty; that conflicts 
with the policies listed in /etc/sudoers, which require a password to be given 
in order to perform
  administrative actions.
  
  Workaround:
  -If you can not perform administrative actions but can still login without a 
password, open a terminal and type "passwd". This command should prompt you for 
a new password and change it without any problems.
  -If you can not login, you can reset your password by booting into recovery 
mode and changing it there. Follow the instructions at 
.
  
  You may also choose to use a password for your account and to enable
  autologin at the same time. This choice will enable you to benefit the
  advantage of not entering a password at boot time with the security of
  Ubuntu requiring your password when attempting to perform privileged
  actions. Of course, this helps when you are the only desktop user or the
  primary one.

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

Status in “accountsservice” package in Ubuntu:
  New
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-system-tools” package in Ubuntu:
  New
Status in “lightdm” package in Ubuntu:
  New

Bug description:
  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543

  Release: 11.10

  Cause: The password is cleared to be empty, and this prevents
  authentification for many admin tasks for security reasons. However,
  the user only needs to be added to the "nopasswdlogin" group, to
  enable passwordless login with gdm (and any other DM that ships with a
  corresponding "auth sufficient pam_succeed_if.so user ingroup
  nopasswdlogin" configuration).

  Fix:
   * lightdm to add pam rule
   * account managing tools not clearing password but only adding user to
 "nopasswdlogin" group

  
  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of t

[Desktop-packages] [Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

[ceg]

** Description changed:

  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543
  
  Release: 11.10
+ 
+ Cause: The password is cleared (which prevents authentification for
+ security reasons). However, the user only needs to be added to the
+ nopasswordlogin group, to enable passwordless login with gdm (and other
+ DMs that ship with a corresponding pam configuration).
  
  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.
  
  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.
  
  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).
  
  Further notes:
  After disabling the password request at login, the /etc/shadow file related 
to the test user account I created looked like this:
  test::15283:0:9:7:::
  This shows that the password hash is made completely empty; that conflicts 
with the policies listed in /etc/sudoers, which require a password to be given 
in order to perform
  administrative actions.
  
  Workaround:
  -If you can not perform administrative actions but can still login without a 
password, open a terminal and type "passwd". This command should prompt you for 
a new password and change it without any problems.
  -If you can not login, you can reset your password by booting into recovery 
mode and changing it there. Follow the instructions at 
.
  
  You may also choose to use a password for your account and to enable
  autologin at the same time. This choice will enable you to benefit the
  advantage of not entering a password at boot time with the security of
  Ubuntu requiring your password when attempting to perform privileged
  actions. Of course, this helps when you are the only desktop user or the
  primary one.

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

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

Status in “accountsservice” package in Ubuntu:
  New
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-system-tools” package in Ubuntu:
  New

Bug description:
  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543

  Release: 11.10

  Cause: The password is cleared to be empty, and this prevents
  authentification for many admin tasks for security reasons. However,
  the user only needs to be added to the "nopasswdlogin" group, to
  enable passwordless login with gdm (and any other DM that ships with a
  corresponding "auth sufficient pam_succeed_if.so user ingroup
  nopasswdlogin" configuration).

  Fix:
   * lightdm to add pam rule
   * account managing tools not clearing password but only adding user to
 "nopasswdlogin" group

  
  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.

  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.

  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).

  Further notes:
  Afte

[Desktop-packages] [Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

[ceg]

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-system-tools (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/882255

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

Status in “accountsservice” package in Ubuntu:
  New
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-system-tools” package in Ubuntu:
  New

Bug description:
  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543

  Release: 11.10

  Cause: The password is cleared (which prevents authentification for
  security reasons). However, the user only needs to be added to the
  nopasswordlogin group, to enable passwordless login with gdm (and
  other DMs that ship with a corresponding pam configuration).

  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.

  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.

  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).

  Further notes:
  After disabling the password request at login, the /etc/shadow file related 
to the test user account I created looked like this:
  test::15283:0:9:7:::
  This shows that the password hash is made completely empty; that conflicts 
with the policies listed in /etc/sudoers, which require a password to be given 
in order to perform
  administrative actions.

  Workaround:
  -If you can not perform administrative actions but can still login without a 
password, open a terminal and type "passwd". This command should prompt you for 
a new password and change it without any problems.
  -If you can not login, you can reset your password by booting into recovery 
mode and changing it there. Follow the instructions at 
.

  You may also choose to use a password for your account and to enable
  autologin at the same time. This choice will enable you to benefit the
  advantage of not entering a password at boot time with the security of
  Ubuntu requiring your password when attempting to perform privileged
  actions. Of course, this helps when you are the only desktop user or
  the primary one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/882255/+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 878997] Re: setting nopasswdlogin removes user password

[ceg]

*** This bug is a duplicate of bug 882255 ***
https://bugs.launchpad.net/bugs/882255

** Also affects: gnome-system-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  setting nopasswdlogin removes user password

Status in “accountsservice” package in Ubuntu:
  New
Status in “gnome-system-tools” package in Ubuntu:
  New
Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  When user wants to setup login without password, user adds to
  nopasswdlogin group (it is fine), but actual password is removed as
  well. This makes impossible using the sudo or gksudo command if user
  was in adm group.

  Workaround is booting in recovery mode and manual setting password to
  the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 1.0.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Oct 20 22:03:52 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/878997/+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 987420] Re: allow to set restart/resume time on shutdown/suspend

[ceg]

I don't know if daily wake events can be programmed in the hardware real
time clock.

Yes, a small "+wakup again" checkbox or similar collapsible UI to enter
a date would be sufficient I guess. But if it the UI could remember the
last setting used this might already also allow daily (next day)
wakeups.

For facility wide power saving schedules I think debian has a "shutdown-
at-night" package.

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

Title:
  allow to set restart/resume time on shutdown/suspend

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  Linux provides a simple way to schedule an restart event, for example:

  rtcwake -m on -s 

  This command avoids that rtcwake does any switching into another power
  state (mode -m stays on).
  The power state is thus handled by the regular installed powermanagment
  tools, which is more stable especially on resume.

  Just schedule the wake event, then do the regular shutdown/suspend.
  Later, the real time clock will trigger the scheduled power event
  and the machine comes back up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/987420/+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 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon

[ceg]

** Bug watch added: GNOME Bug Tracker #675064
   https://bugzilla.gnome.org/show_bug.cgi?id=675064

** Changed in: zenity
   Importance: Undecided => Unknown

** Changed in: zenity
   Status: New => Unknown

** Changed in: zenity
 Remote watch: None => GNOME Bug Tracker #675064

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

Title:
  regression: lost ability to show continuous status with
  tray/appindicator icon

Status in Zenity:
  Unknown
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
  from zenity.

  For clarity, the tray icon functionality should be made available with
  a proper "zenity --trayicon" feature.

  For backwards compatibility, the --notification option would have to
  continue to show an icon. It may do so only together with the the
  --listen option (this then implies status updates should follow), and
  emit only a simple notification bubble and exit otherwise.

  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1

  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.

  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.

  What happens instead:
  A "zenity --warning" style dialog window pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/884011/+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 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon

[ceg]

In any case, it would be good if you could post the issue to the upstram
bugtracker.

** Description changed:

  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
  from zenity.
  
  For clarity, the tray icon functionality should be made available with a
  proper "zenity --trayicon" feature.
  
  For backwards compatibility, the --notification option would have to
- continue to show an icon, but may be switched to just bring up a
- notification bubble for clarity, once a separate --trayicon feature is
- available.
- 
+ continue to show an icon. It may do so only together with the the
+ --listen option (this then implies status updates should follow), and
+ emit only a simple notification bubble and exit otherwise.
  
  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1
  
  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.
  
  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.
  
  What happens instead:
  A "zenity --warning" style dialog window pops up.

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

Title:
  regression: lost ability to show continuous status with
  tray/appindicator icon

Status in Zenity:
  New
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
  from zenity.

  For clarity, the tray icon functionality should be made available with
  a proper "zenity --trayicon" feature.

  For backwards compatibility, the --notification option would have to
  continue to show an icon. It may do so only together with the the
  --listen option (this then implies status updates should follow), and
  emit only a simple notification bubble and exit otherwise.

  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1

  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.

  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.

  What happens instead:
  A "zenity --warning" style dialog window pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/884011/+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 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon

[ceg]

** Description changed:

  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
- from zenity. Instead, that functionality should have been moved into a
+ from zenity.
+ 
+ For clarity, the tray icon functionality should be made available with a
  proper "zenity --trayicon" feature.
+ 
+ For backwards compatibility, the --notification option would have to
+ continue to show an icon, but may be switched to just bring up a
+ notification bubble for clarity, once a separate --trayicon feature is
+ available.
+ 
  
  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1
  
  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.
  
  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.
  
  What happens instead:
  A "zenity --warning" style dialog window pops up.

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

Title:
  regression: lost ability to show continuous status with
  tray/appindicator icon

Status in Zenity:
  New
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
  from zenity.

  For clarity, the tray icon functionality should be made available with
  a proper "zenity --trayicon" feature.

  For backwards compatibility, the --notification option would have to
  continue to show an icon, but may be switched to just bring up a
  notification bubble for clarity, once a separate --trayicon feature is
  available.


  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1

  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.

  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.

  What happens instead:
  A "zenity --warning" style dialog window pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/884011/+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 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon

[ceg]

Hi Peter-Alexander,
you're right, and I agree it still is a regression looking at the 
--notification function alone. As far as I understand the reason for the change 
was the decision for an updated semantic. Notification now only means a bubble 
message, and is different from a status icon or window. Going with this might 
be more precise. But changing this without giving apps the chance to adopt and 
use a --trayicon option if they actually do need a continuous status indication 
one is really bad.

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

Title:
  regression: lost ability to show continuous status with
  tray/appindicator icon

Status in Zenity:
  New
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
  from zenity.

  For clarity, the tray icon functionality should be made available with
  a proper "zenity --trayicon" feature.

  For backwards compatibility, the --notification option would have to
  continue to show an icon, but may be switched to just bring up a
  notification bubble for clarity, once a separate --trayicon feature is
  available.


  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1

  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.

  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.

  What happens instead:
  A "zenity --warning" style dialog window pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/884011/+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 387984] Re: Notifications using --listen should allow clicking to remove the icon

[ceg]

** Description changed:

  Binary package hint: zenity
+ 
+ 
+ Zenity --notify (or better --trayicon Bug #884011) may just always listen on 
stdin, and provide an --exit-on-click option enable user feedback.
+ 
+ This would remove the asumption that --listen always means to endlessly
+ listen to commands on stdin. It would provide the calling script with
+ feedback upon user action (zenity exits), while being able to modify the
+ status.
+ 
+ Ideally, zenity could also accept an "exit" or "quit" command on stdin,
+ in addition to Ctrl-C or closing the file descriptor.
+ 
+ 
+ ---
+ The follwing issues that got mixed into this report seem fixed, or are 
intended behavior:
  
  "zenity --notification --listen" can't show multi lines tooltip.
  But as cmd line parameter is works fine: zenity --notification --text 
$'line1\nline2'
  
  "zenity --notification" does not have command line parameter for "message"
  This does not work: zenity --notification --title hi
  Also this does not work: echo 'message:hi' | zenity --notification
  But this works: echo 'message:hi' | zenity --notification --listen
  
  "zenity --notification --listen" does not exit (does nothing) on click on 
notification icon
  But without "--listen", when notification icon is clicked, zenity does exit.
  
  "zenity --notification" man page does not tell about icon and message, does 
not explain about tooltip.
  Man page say only: "--text" set the notification text (message or tooltip?)

** Description changed:

  Binary package hint: zenity
  
- 
- Zenity --notify (or better --trayicon Bug #884011) may just always listen on 
stdin, and provide an --exit-on-click option enable user feedback.
+ Zenity --notification (or better --trayicon Bug #884011) may just always
+ listen on stdin, and provide an --exit-on-click option enable user
+ feedback.
  
  This would remove the asumption that --listen always means to endlessly
  listen to commands on stdin. It would provide the calling script with
  feedback upon user action (zenity exits), while being able to modify the
  status.
  
  Ideally, zenity could also accept an "exit" or "quit" command on stdin,
  in addition to Ctrl-C or closing the file descriptor.
- 
  
  ---
  The follwing issues that got mixed into this report seem fixed, or are 
intended behavior:
  
  "zenity --notification --listen" can't show multi lines tooltip.
  But as cmd line parameter is works fine: zenity --notification --text 
$'line1\nline2'
  
  "zenity --notification" does not have command line parameter for "message"
  This does not work: zenity --notification --title hi
  Also this does not work: echo 'message:hi' | zenity --notification
  But this works: echo 'message:hi' | zenity --notification --listen
  
  "zenity --notification --listen" does not exit (does nothing) on click on 
notification icon
  But without "--listen", when notification icon is clicked, zenity does exit.
  
  "zenity --notification" man page does not tell about icon and message, does 
not explain about tooltip.
  Man page say only: "--text" set the notification text (message or tooltip?)

** Description changed:

  Binary package hint: zenity
  
  Zenity --notification (or better --trayicon Bug #884011) may just always
- listen on stdin, and provide an --exit-on-click option enable user
+ listen on stdin, and provide an --exit-on-click option to enable user
  feedback.
  
  This would remove the asumption that --listen always means to endlessly
  listen to commands on stdin. It would provide the calling script with
  feedback upon user action (zenity exits), while being able to modify the
  status.
  
  Ideally, zenity could also accept an "exit" or "quit" command on stdin,
  in addition to Ctrl-C or closing the file descriptor.
  
  ---
  The follwing issues that got mixed into this report seem fixed, or are 
intended behavior:
  
  "zenity --notification --listen" can't show multi lines tooltip.
  But as cmd line parameter is works fine: zenity --notification --text 
$'line1\nline2'
  
  "zenity --notification" does not have command line parameter for "message"
  This does not work: zenity --notification --title hi
  Also this does not work: echo 'message:hi' | zenity --notification
  But this works: echo 'message:hi' | zenity --notification --listen
  
  "zenity --notification --listen" does not exit (does nothing) on click on 
notification icon
  But without "--listen", when notification icon is clicked, zenity does exit.
  
  "zenity --notification" man page does not tell about icon and message, does 
not explain about tooltip.
  Man page say only: "--text" set the notification text (message or tooltip?)

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

Title:
  Notifications using --listen should allow clicking to remove the icon

Status in Zenity:
  Expired
Status in “zenity” package in Ubuntu:
  Triaged

Bug descriptio

[Desktop-packages] [Bug 387984] Re: Notifications using --listen should allow clicking to remove the icon

[ceg]

Zenity --notify (or better --trayicon Bug #884011) may just always
listen on stdin, and provide an --exit-on-click option enable user
feedback.

This would remove the asumption that --listen means to continusly
listening to commands on stdin. It would provide the calling script with
a feedback upon user action (zenity exits), while being able to modify
the status.


Ideally, zenity could also accept an "exit" or "quit" command on stdin, in 
addition to Ctrl-C or closing the file descriptor.

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

Title:
  Notifications using --listen should allow clicking to remove the icon

Status in Zenity:
  Expired
Status in “zenity” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: zenity

  Zenity --notification (or better --trayicon Bug #884011) may just
  always listen on stdin, and provide an --exit-on-click option to
  enable user feedback.

  This would remove the asumption that --listen always means to
  endlessly listen to commands on stdin. It would provide the calling
  script with  feedback upon user action (zenity exits), while being
  able to modify the status.

  Ideally, zenity could also accept an "exit" or "quit" command on
  stdin, in addition to Ctrl-C or closing the file descriptor.

  ---
  The follwing issues that got mixed into this report seem fixed, or are 
intended behavior:

  "zenity --notification --listen" can't show multi lines tooltip.
  But as cmd line parameter is works fine: zenity --notification --text 
$'line1\nline2'

  "zenity --notification" does not have command line parameter for "message"
  This does not work: zenity --notification --title hi
  Also this does not work: echo 'message:hi' | zenity --notification
  But this works: echo 'message:hi' | zenity --notification --listen

  "zenity --notification --listen" does not exit (does nothing) on click on 
notification icon
  But without "--listen", when notification icon is clicked, zenity does exit.

  "zenity --notification" man page does not tell about icon and message, does 
not explain about tooltip.
  Man page say only: "--text" set the notification text (message or tooltip?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/387984/+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 884011] Re: zenity doesn't show tray/appindicator icon

[ceg]

** Description changed:

+ 
+ The functionality to display a tray icon with "zenity --notification" 
completely removed that functionality from zenity, instead of moving it into a 
proper "zenity --trayicon" feature.
+ 
+ ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1
  
  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.
  
  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.
  
  What happens instead:
  A "zenity --warning" style dialog window pops up.

** Summary changed:

- zenity doesn't show tray/appindicator icon
+ regression: lost ability to show continuous status with tray/appindicator icon

** Description changed:

- 
- The functionality to display a tray icon with "zenity --notification" 
completely removed that functionality from zenity, instead of moving it into a 
proper "zenity --trayicon" feature.
+ The change in the "zenity --notification" behavior completely removed
+ the functionality to display a tray icon from zenity, instead of moving
+ the functionality into a proper "zenity --trayicon" feature.
  
  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1
  
  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.
  
  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.
  
  What happens instead:
  A "zenity --warning" style dialog window pops up.

** Description changed:

  The change in the "zenity --notification" behavior completely removed
- the functionality to display a tray icon from zenity, instead of moving
- the functionality into a proper "zenity --trayicon" feature.
+ the functionality to display an unobtrusive, always visible tray icon
+ from zenity. Instead, that functionality should have been moved into a
+ proper "zenity --trayicon" feature.
  
  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1
  
  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.
  
  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.
  
  What happens instead:
  A "zenity --warning" style dialog window pops up.

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

Title:
  regression: lost ability to show continuous status with
  tray/appindicator icon

Status in Zenity:
  New
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  The change in the "zenity --notification" behavior completely removed
  the functionality to display an unobtrusive, always visible tray icon
  from zenity. Instead, that functionality should have been moved into a
  proper "zenity --trayicon" feature.

  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1

  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.

  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.

  What happens instead:
  A "zenity --warning" style dialog window pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/884011/+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 884011] Re: zenity doesn't show tray/appindicator icon

[ceg]

The functionality to display a status icon continuously still remains a 
requirement, and this is a zenity regression.

Reducing "zenity --notification" to implement just notifications (same
as "notify-send") may be OK, but then a separate "zenity --trayicon" is
required to maintain the functionality.

The replacement "zenity --trayicon --listen" should allow to change
trayicon, tooltip, menus, etc., and also to close/quit the trayicon
without user interaction.

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

Title:
  zenity doesn't show tray/appindicator icon

Status in Zenity:
  New
Status in “zenity” package in Ubuntu:
  Confirmed

Bug description:
  
  The functionality to display a tray icon with "zenity --notification" 
completely removed that functionality from zenity, instead of moving it into a 
proper "zenity --trayicon" feature.

  ---
  Ubuntu 11.10
  zenity 3.2.0-0ubuntu1

  In a script I use following line:
  exec 3> >(zenity --notification --window-icon="icon.svg" --listen 
--text="some text")
  so I can change the tray icon based on what the script does.

  What I expect to happen:
  "zenity --notification" should show an icon in the tray or appindicator.

  What happens instead:
  A "zenity --warning" style dialog window pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zenity/+bug/884011/+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 987420] Re: allow to set restart/resume time on shutdown/suspend

[ceg]

** Description changed:

  Linux provides a simple way to schedule an restart event, for example:
  
  rtcwake -m on -s 
  
- This command avoids that rtcwake does the switching into another power state 
(mode -m stays on).
- The power state are thus handled by the regular pm-tools, which is more 
stable especially on resume. The real time clock will simply trigger a 
scheduled power event.
+ This command avoids that rtcwake does any switching into another power
+ state (mode -m stays on).
+ The power state is thus handled by the regular installed powermanagment
+ tools, which is more stable especially on resume.
+ 
+ Just schedule the wake event, then do the regular shutdown/suspend.
+ Later, the real time clock will trigger the scheduled power event
+ and the machine comes back up.

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

Title:
  allow to set restart/resume time on shutdown/suspend

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  Linux provides a simple way to schedule an restart event, for example:

  rtcwake -m on -s 

  This command avoids that rtcwake does any switching into another power
  state (mode -m stays on).
  The power state is thus handled by the regular installed powermanagment
  tools, which is more stable especially on resume.

  Just schedule the wake event, then do the regular shutdown/suspend.
  Later, the real time clock will trigger the scheduled power event
  and the machine comes back up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/987420/+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 987420] [NEW] allow to set restart/resume time on shutdown/suspend

[ceg]

Public bug reported:

Linux provides a simple way to schedule an restart event, for example:

rtcwake -m on -s 

This command avoids that rtcwake does the switching into another power state 
(mode -m stays on).
The power state are thus handled by the regular pm-tools, which is more stable 
especially on resume. The real time clock will simply trigger a scheduled power 
event.

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

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

Title:
  allow to set restart/resume time on shutdown/suspend

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  Linux provides a simple way to schedule an restart event, for example:

  rtcwake -m on -s 

  This command avoids that rtcwake does the switching into another power state 
(mode -m stays on).
  The power state are thus handled by the regular pm-tools, which is more 
stable especially on resume. The real time clock will simply trigger a 
scheduled power event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/987420/+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 985876] [NEW] units shown are not equal to the units asked for creation

[ceg]

Public bug reported:

Try to recreate or clone the OS partition on another harddrive of a
different size as the original.

GParted shows only an impresize size of the existing partition such as
"32.63GB", whereas to create the new partition the exact size in MiB is
required.

Hidden in the Properties, gparted does tell the number of sectors in the
old partition, but that can't be directly used to create the new
partition either. (V 2.30.1)

** Affects: gnome-disk-utility
 Importance: Undecided
 Status: New

** Description changed:

  Try to recreate or clone the OS partition on another harddrive of a
  different size as the original.
  
- Bug GParted shows only an impresize size of the partition such as
- "32.63GB", whereas to create the new partitionthe exact size is
+ GParted shows only an impresize size of the existing partition such as
+ "32.63GB", whereas to create the new partition the exact size in MiB is
  required.
  
  Hidden in the Properties, gparted does tell the number of sectors in the
  old partition, but that can't be directly used to create the new
  partition eiher.

** Description changed:

  Try to recreate or clone the OS partition on another harddrive of a
  different size as the original.
  
  GParted shows only an impresize size of the existing partition such as
  "32.63GB", whereas to create the new partition the exact size in MiB is
  required.
  
  Hidden in the Properties, gparted does tell the number of sectors in the
  old partition, but that can't be directly used to create the new
- partition eiher.
+ partition either. (V 2.30.1)

** Package changed: gnome-disk-utility (Ubuntu) => gnome-disk-utility

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

Title:
  units shown are not equal to the units asked for creation

Status in gnome-disk-utility:
  New

Bug description:
  Try to recreate or clone the OS partition on another harddrive of a
  different size as the original.

  GParted shows only an impresize size of the existing partition such as
  "32.63GB", whereas to create the new partition the exact size in MiB
  is required.

  Hidden in the Properties, gparted does tell the number of sectors in
  the old partition, but that can't be directly used to create the new
  partition either. (V 2.30.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/985876/+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 393854] Re: Update PAM policy to allow password-less logins set up via users-admin

[ceg]

** Bug watch added: Debian Bug tracker #609417
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609417

** Also affects: gdm (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609417
   Importance: Unknown
   Status: Unknown

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

Title:
  Update PAM policy to allow password-less logins set up via users-admin

Status in GDM: The Gnome Display Manager:
  Fix Released
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “gdm” package in Debian:
  Unknown

Bug description:
  Binary package hint: gdm

  Upstream gnome-system-tools will have in 2.28 an option to allow specified 
users to log in graphically and locally without entering their password. This 
is intended for home users that can't use GDM's autologin because they are 
several on the same computer. A rationale is at:
  
http://markmail.org/message/2h5isyf3kip6updb#query:gdm%20passwordless+page:1+mid:pa6lrzmwdtbol5it+state:results
  and the bug upstream was http://bugzilla.gnome.org/show_bug.cgi?id=414862

  For this to work in Ubuntu, we need to add a rule to the PAM configuration 
file:
  auth   sufficient  pam_succeed_if.so user ingroup nopasswdlogin

  And to create the group 'nopasswdlogin' in the postinstall script.

  Attached is a debdiff that does that. I guess somebody familiar with
  Ubuntu's PAM rules should check it since that's a critical part of the
  system's security, but that way of achieving this has been accepted by
  Brian Cameron (GDM) and Carlos Garnacho (gnome-system-tools) as safe,
  and many users has been using this as a hack for some time.

  This change should also affect gnome-screensaver so that the screen is
  not locked after suspend. I'll post a diff for that too, and for the
  gdm-new package.

  Please ask if you need more explanations about how this works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/393854/+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 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

[ceg]

Istn't the feature part of the “gnome-system-tools” package?

-- 
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/882255

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

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

Bug description:
  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543

  Release: 11.10

  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.

  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.

  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).

  Further notes:
  After disabling the password request at login, the /etc/shadow file related 
to the test user account I created looked like this:
  test::15283:0:9:7:::
  This shows that the password hash is made completely empty; that conflicts 
with the policies listed in /etc/sudoers, which require a password to be given 
in order to 

  Workaround:
  -If you can not perform administrative actions but can still login without a 
password, open a terminal and type "passwd". This command should prompt you for 
a new password and change it without any problems.
  -If you can not login, you can reset your password by booting into recovery 
mode and changing it there. Follow the instructions at 
.

  You may also choose to use a password for your account and to enable
  autologin at the same time. This choice will enable you to benefit the
  advantage of not entering a password at boot time with the security of
  Ubuntu requiring your password when attempting to perform privileged
  actions.

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