[Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39717] Re: When guest (nobody) account exists, smbpasswd should default to none
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/39717/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
set it _automatically_ of course -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984449] Re: Palimpsest doesn't allow precisely-sized partitions
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 Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/984449 Title: Palimpsest doesn't allow precisely-sized partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/984449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984449] Re: Palimpsest doesn't allow precisely-sized partitions
PS launchpad is a waste of time, get in contact with upstrem directly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/984449 Title: Palimpsest doesn't allow precisely-sized partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/984449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984449] Re: Palimpsest doesn't allow precisely-sized partitions
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 Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/984449 Title: Palimpsest doesn't allow precisely-sized partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/984449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878997] Re: setting nopasswdlogin removes user password
*** 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 Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/878997 Title: setting nopasswdlogin removes user password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/878997/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login
** 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/882255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login
** 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 http://psychocats.net/ubuntu/resetpassword. 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 Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/882255 Title: No administrative actions possible (password refused) after enabling passwordless login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/882255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login
** 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 http://psychocats.net/ubuntu/resetpassword. 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 Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/882255 Title: No administrative actions possible (password refused) after enabling passwordless login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/882255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 987420] Re: allow to set restart/resume time on shutdown/suspend
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 Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987420 Title: allow to set restart/resume time on shutdown/suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/987420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/884011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon
** 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/884011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/884011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884011] Re: regression: lost ability to show continuous status with tray/appindicator icon
** 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/884011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884011] Re: zenity doesn't show tray/appindicator icon
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 Ubuntu Desktop Bugs, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/884011 Title: zenity doesn't show tray/appindicator icon To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/884011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 884011] Re: zenity doesn't show 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. + + --- 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/884011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 387984] Re: Notifications using --listen should allow clicking to remove the icon
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 Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/387984 Title: Notifications using --listen should allow clicking to remove the icon To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/387984/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 387984] Re: Notifications using --listen should allow clicking to remove the icon
** 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 Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/387984 Title: Notifications using --listen should allow clicking to remove the icon To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/387984/+subscriptions -- desktop-bugs mailing list
[Bug 987420] [NEW] allow to set restart/resume time on shutdown/suspend
Public bug reported: Linux provides a simple way to schedule an restart event, for example: rtcwake -m on -s seconds-to-sleep 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 Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987420 Title: allow to set restart/resume time on shutdown/suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/987420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 987420] Re: allow to set restart/resume time on shutdown/suspend
** Description changed: Linux provides a simple way to schedule an restart event, for example: rtcwake -m on -s seconds-to-sleep - 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 Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987420 Title: allow to set restart/resume time on shutdown/suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/987420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985876] [NEW] units shown are not equal to the units asked for creation
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/985876/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login
Istn't the feature part of the “gnome-system-tools” package? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/882255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 393854] Re: Update PAM policy to allow password-less logins set up via users-admin
** 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/393854/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 532200] Re: Enable Automatic Logon should not ask for password to WiFi logon
Though, it's an annoying behavior that no keyrings are not opened with autologin. A wishlist item, for a checkbox to clear the password from the login keyring for autologin, seems adequate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/532200 Title: automatic logon: option to clear login.keyring password -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 532200] Re: Enable Automatic Logon should not ask for password to WiFi logon
@wallydallas With the keyring tool under System-Preferences you can change the password for the login keyring to an empty string. Be aware though that the keys in this keyring will then be on your harddrive in plain text, readable for anybody who has access to it. ** Summary changed: - Enable Automatic Logon should not ask for password to WiFi logon + automatic logon: option to clear login.keyring password -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/532200 Title: automatic logon: option to clear login.keyring password -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 532200] Re: automatic logon: option to clear login.keyring password
Can you make this wishlist? The importance option is not accessible for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/532200 Title: automatic logon: option to clear login.keyring password -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 532200] Re: automatic logon: option to clear login.keyring password
** Changed in: gdm (Ubuntu) Status: Invalid = New ** Changed in: gdm Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/532200 Title: automatic logon: option to clear login.keyring password -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762983] Re: asks to open keyring default, but its pw was saved to login
~/.gnome2/keyrings/default actually contains the name of the keyring that is marked as default (login). As gksu uses a separate keyring (named default), which is alright, it has to open the keyring used. However, it should be able to ask for (open) a lower level keyring in case of daisy chained keyrings. ** Also affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/762983 Title: asks to open keyring default, but its pw was saved to login -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762983] Re: asks to open keyring default, but its pw was saved to login
Is it central functionality to handle keyring dependencies? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/762983 Title: asks to open keyring default, but its pw was saved to login -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762983] Re: asks to open keyring default, but its pw was saved to login
** Also affects: seahorse Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/762983 Title: asks to open keyring default, but its pw was saved to login -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762630] [NEW] battery state not discharging with unpluged AC
Public bug reported: Binary package hint: gnome-power-manager Laptop Model: Medion MD 96360 The battery symbol does not appear if ac is unpluged after booting. While # cat /proc/acpi/ac_adapter/ADP1/state changes between: state: off-line and : state: on-line # cat /proc/acpi/battery/BAT1/state keeps showing: present: yes capacity state: ok charging state: charged present rate:unknown remaining capacity: unknown present voltage: 1 mV ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Sat Apr 16 12:09:01 2011 GConfNonDefault: /apps/gnome-power-manager/backlight/battery_reduce=false /apps/gnome-power-manager/lock/blank_screen=false /apps/gnome-power-manager/lock/use_screensaver_settings=false /apps/gnome-power-manager/notify/sleep_failed_uri= /apps/gnome-power-manager/ui/icon_policy=charge GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: Notebook SAM2010 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=/dev/mapper/vg_w-lv_root ro splash quiet vga=773 quiet splash pcie_aspm=off ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 04/25/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1058AM7 V7.27 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SAM2010 dmi.board.vendor: MEDION dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1058AM7V7.27:bd04/25/2008:svnNotebook:pnSAM2010:pvr1058:rvnMEDION:rnSAM2010:rvr:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2010 dmi.product.version: 1058 dmi.sys.vendor: Notebook ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/762630 Title: battery state not discharging with unpluged AC -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762630] Re: battery state not discharging with unpluged AC
** Description changed: Binary package hint: gnome-power-manager - + Laptop Model: Medion MD 96360 The battery symbol does not appear if ac is unpluged after booting. While # cat /proc/acpi/ac_adapter/ADP1/state changes between: state: off-line and : state: on-line # cat /proc/acpi/battery/BAT1/state - keeps showing: + keeps showing: present: yes capacity state: ok charging state: charged present rate:unknown remaining capacity: unknown present voltage: 1 mV ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Sat Apr 16 12:09:01 2011 GConfNonDefault: - /apps/gnome-power-manager/backlight/battery_reduce=false - /apps/gnome-power-manager/lock/blank_screen=false - /apps/gnome-power-manager/lock/use_screensaver_settings=false - /apps/gnome-power-manager/notify/sleep_failed_uri= - /apps/gnome-power-manager/ui/icon_policy=charge + /apps/gnome-power-manager/backlight/battery_reduce=false + /apps/gnome-power-manager/lock/blank_screen=false + /apps/gnome-power-manager/lock/use_screensaver_settings=false + /apps/gnome-power-manager/notify/sleep_failed_uri= + /apps/gnome-power-manager/ui/icon_policy=charge GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: Notebook SAM2010 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=/dev/mapper/vg_w-lv_root ro splash quiet vga=773 quiet splash pcie_aspm=off ProcEnviron: - PATH=(custom, user) - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 04/25/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1058AM7 V7.27 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SAM2010 dmi.board.vendor: MEDION dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1058AM7V7.27:bd04/25/2008:svnNotebook:pnSAM2010:pvr1058:rvnMEDION:rnSAM2010:rvr:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2010 dmi.product.version: 1058 dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/762630 Title: battery state not discharging with unpluged AC -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762630] Re: battery state not discharging with unpluged AC
** Description changed: Binary package hint: gnome-power-manager - Laptop Model: Medion MD 96360 The battery symbol does not appear if ac is unpluged after booting. While # cat /proc/acpi/ac_adapter/ADP1/state changes between: state: off-line and : state: on-line # cat /proc/acpi/battery/BAT1/state keeps showing: present: yes capacity state: ok charging state: charged present rate:unknown remaining capacity: unknown present voltage: 1 mV + + + Also incorrect a line from: + # upower --dump + lid-is-closed: yes + + + The lid is open. + ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Sat Apr 16 12:09:01 2011 GConfNonDefault: /apps/gnome-power-manager/backlight/battery_reduce=false /apps/gnome-power-manager/lock/blank_screen=false /apps/gnome-power-manager/lock/use_screensaver_settings=false /apps/gnome-power-manager/notify/sleep_failed_uri= /apps/gnome-power-manager/ui/icon_policy=charge GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: Notebook SAM2010 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=/dev/mapper/vg_w-lv_root ro splash quiet vga=773 quiet splash pcie_aspm=off ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 04/25/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1058AM7 V7.27 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SAM2010 dmi.board.vendor: MEDION dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1058AM7V7.27:bd04/25/2008:svnNotebook:pnSAM2010:pvr1058:rvnMEDION:rnSAM2010:rvr:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2010 dmi.product.version: 1058 dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/762630 Title: battery state not discharging with unpluged AC -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762630] Re: battery state not discharging with unpluged AC
** Description changed: Binary package hint: gnome-power-manager - The battery symbol does not appear if ac is unpluged after booting. + The battery symbol does not appear if AC is unpluged after booting. While # cat /proc/acpi/ac_adapter/ADP1/state changes between: state: off-line and : state: on-line # cat /proc/acpi/battery/BAT1/state keeps showing: present: yes capacity state: ok charging state: charged present rate:unknown remaining capacity: unknown present voltage: 1 mV - Also incorrect a line from: + Also incorrect lines from: # upower --dump - lid-is-closed: yes + daemon-version: 0.9.5 + can-suspend: no + can-hibernateno + on-battery: no + on-low-battery: no + lid-is-closed: yes + lid-is-present: yes + + The lid is open! + + --- + + The battery symbol does appear/change correctly after booting from battery. + And upower --dump shows: + + daemon-version: 0.9.5 + can-suspend: yes + can-hibernateyes + on-battery: no + on-low-battery: no + lid-is-closed: no + lid-is-present: yes - The lid is open. - + -- ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Sat Apr 16 12:09:01 2011 GConfNonDefault: /apps/gnome-power-manager/backlight/battery_reduce=false /apps/gnome-power-manager/lock/blank_screen=false /apps/gnome-power-manager/lock/use_screensaver_settings=false /apps/gnome-power-manager/notify/sleep_failed_uri= /apps/gnome-power-manager/ui/icon_policy=charge GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: Notebook SAM2010 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=/dev/mapper/vg_w-lv_root ro splash quiet vga=773 quiet splash pcie_aspm=off ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 04/25/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1058AM7 V7.27 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SAM2010 dmi.board.vendor: MEDION dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1058AM7V7.27:bd04/25/2008:svnNotebook:pnSAM2010:pvr1058:rvnMEDION:rnSAM2010:rvr:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2010 dmi.product.version: 1058 dmi.sys.vendor: Notebook ** Summary changed: - battery state not discharging with unpluged AC + battery state not discharging if AC unpluged after boot -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/762630 Title: battery state not discharging if AC unpluged after boot -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762630] Re: battery state not discharging if AC unpluged after boot
** Description changed: Binary package hint: gnome-power-manager - The battery symbol does not appear if AC is unpluged after booting. + Unfortunately, I can not reproduce it reliably, but when it happens this + is the behavior: + + The battery symbol does not appear and the on-battery settings are not + applied, if AC is unpluged after booting with AC. While # cat /proc/acpi/ac_adapter/ADP1/state changes between: state: off-line and : state: on-line # cat /proc/acpi/battery/BAT1/state keeps showing: present: yes capacity state: ok charging state: charged present rate:unknown remaining capacity: unknown present voltage: 1 mV - Also incorrect lines from: # upower --dump - daemon-version: 0.9.5 - can-suspend: no - can-hibernateno - on-battery: no - on-low-battery: no - lid-is-closed: yes - lid-is-present: yes + daemon-version: 0.9.5 + can-suspend: no + can-hibernateno + on-battery: no + on-low-battery: no + lid-is-closed: yes + lid-is-present: yes The lid is open! --- The battery symbol does appear/change correctly after booting from battery. And upower --dump shows: - daemon-version: 0.9.5 - can-suspend: yes - can-hibernateyes - on-battery: no - on-low-battery: no - lid-is-closed: no - lid-is-present: yes + daemon-version: 0.9.5 + can-suspend: yes + can-hibernateyes + on-battery: no + on-low-battery: no + lid-is-closed: no + lid-is-present: yes + + -- + + With the wrong lid-state the laptop first was unable to resume fully (Bug #762576), then crashed hard during resume from suspend (caps+num lock blinking). + After a reboot, AC state and suspend is currently working correctly again. -- ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Sat Apr 16 12:09:01 2011 GConfNonDefault: /apps/gnome-power-manager/backlight/battery_reduce=false /apps/gnome-power-manager/lock/blank_screen=false /apps/gnome-power-manager/lock/use_screensaver_settings=false /apps/gnome-power-manager/notify/sleep_failed_uri= /apps/gnome-power-manager/ui/icon_policy=charge GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: Notebook SAM2010 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=/dev/mapper/vg_w-lv_root ro splash quiet vga=773 quiet splash pcie_aspm=off ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 04/25/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1058AM7 V7.27 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SAM2010 dmi.board.vendor: MEDION dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1058AM7V7.27:bd04/25/2008:svnNotebook:pnSAM2010:pvr1058:rvnMEDION:rnSAM2010:rvr:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SAM2010 dmi.product.version: 1058 dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/762630 Title: battery state not discharging if AC unpluged after boot -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 532200] Re: Enable Automatic Logon should not ask for password to WiFi logon
The option should of course have a fat warning that all your passwords will be saved on disk in plain text, if you don't have an encrypted filesystem. ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New ** Changed in: gksu (Ubuntu) Status: New = Invalid ** Also affects: gdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/532200 Title: Enable Automatic Logon should not ask for password to WiFi logon -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 420564] Re: importing snippets does not work unless .gnome2/gedit/snippets is already existing
Use gedit with the snippet plug-in installed, tools-snippets and import the file from http://mga.tiny.googlepages.com/openerp.tar.gz (or bzr branch lp:openobject-gedit) to the python snippets. See screencast at: http://openerp.tv/display.php?rnd=NzA= ** Changed in: gedit (Ubuntu) Status: New = Confirmed -- importing snippets does not work unless .gnome2/gedit/snippets is already existing https://bugs.launchpad.net/bugs/420564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574334] Re: [users-admin] no option to specify new U/GUID etc.
Specifying the UID on creation is not the only advanced option missing. Generally see it quite troublesome when gnome apps are cutting functionality away, not uncluttering or easing or explaining advanced options in the UI but actually delivering regressions. GDM just did the same, it used to have options to hide users or list only selected users, not any more. :( -- [users-admin] no option to specify new U/GUID etc. https://bugs.launchpad.net/bugs/574334 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574379] Re: [users-admin] No option to show system users
OK, hopefully system users can be shown for anybody to see in a next version. -- [users-admin] No option to show system users https://bugs.launchpad.net/bugs/574379 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574379] Re: [users-admin] No option to show system users
Just meant the option to show system users. -- [users-admin] No option to show system users https://bugs.launchpad.net/bugs/574379 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574334] Re: [users-admin] no option to specify new U/GUID etc.
I guess it's what I expect from a GUI. I expect it to be of help for new users not yet familiar with things and it to suggest appropriate actions the user may not be aware of but might likely be interested in. I.e. now, you have to be aware that users are made members to a couple of groups and then remember to change them afterwards. Whereas a GUI that is usefull for new users just as for experienced users, does not only silently apply some defaults in the background, but allows users to see them, discover them, and go through them and learn (get explanations) about them (under an advaced tab or button if they are so advanced). -- [users-admin] no option to specify new U/GUID etc. https://bugs.launchpad.net/bugs/574334 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 549451] Re: gksu uses keyring default but only login is auto opened
On a fresh install of 10.04 there was now an option to save the default.keyring password to the login.keyring. And it works (as long as autologin is disabled). So I'd consider my issue solved. Thanks! ** Changed in: seahorse (Ubuntu) Status: New = Fix Released ** Changed in: gksu (Ubuntu) Status: New = Fix Released -- gksu uses keyring default but only login is auto opened https://bugs.launchpad.net/bugs/549451 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574334] [NEW] [users-admin] no option to specify new U/GUID etc.
Public bug reported: Binary package hint: gnome-system-tools When creating a new user, there is no (advanced tab/button) option to specify those options for the new user. Since gdm does not support to display only selected or unselected users in the user list, you need to create users that should not show up in the user list with a UID 1000. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- [users-admin] no option to specify new U/GUID etc. https://bugs.launchpad.net/bugs/574334 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574334] Re: [users-admin] no option to specify new U/GUID etc.
** Description changed: Binary package hint: gnome-system-tools - When creating a new user, there is no (advanced tab/button) option to - specify those options for the new user. + When creating a new user in 10.04, there is no (advanced tab/button) + option to specify those options for the new user. Since gdm does not support to display only selected or unselected users in the user list, you need to create users that should not show up in the user list with a UID 1000. -- [users-admin] no option to specify new U/GUID etc. https://bugs.launchpad.net/bugs/574334 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 542183] Re: [users-admin] Changing UID doesn't work
Will g-s-t also adjust the ownership of files in the filesystem upon changing a user's ID, or would that be a different issue? -- [users-admin] Changing UID doesn't work https://bugs.launchpad.net/bugs/542183 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to system-tools-backends in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 542183] Re: [users-admin] Changing UID doesn't work
Is gst using usermod? Its manpage says: -u The ownership of files outside of the users home directory must be fixed manually. -- [users-admin] Changing UID doesn't work https://bugs.launchpad.net/bugs/542183 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to system-tools-backends in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 433654] Re: [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
Mind you that I'd consider any device-kit privilege escalation implementation that isn't configured to support/use (be itself easily configurable by) standard unix user group memberships as a regression. -- [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences https://bugs.launchpad.net/bugs/433654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 433654] Re: [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
Instead pulling users from the audio group etc. to make user switching work, device-kit configuration needs to take user groups into account. -- [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences https://bugs.launchpad.net/bugs/433654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574379] [NEW] [users-admin] advanced option can not show system IDs
Public bug reported: Binary package hint: gnome-system-tools The advanced option rightly allows to set G/UIDs below the standard rage (i.e. within the range of dynamically allocated system users, in debian: 100-999 created by adduser --system) But since the option to show those dynamically manageable users (100-999 in debian/ubuntu case) is missing the users dissappear once the ID is changed into that range. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- [users-admin] advanced option can not show system IDs https://bugs.launchpad.net/bugs/574379 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 433654] Re: [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
** Also affects: consolekit (Ubuntu) Importance: Undecided Status: New -- [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences https://bugs.launchpad.net/bugs/433654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 433654] Re: [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
** Description changed: + Sound does not work for different users if they belong to the audio + group. + + A workaround is to remove the users from the audio group. With this + however simply managing individual device access based on standard group + memberships stops working (regression). + + Consolekit (like any kit handling device permissions/privilege + escalation) needs to enable audio only for users belonging to audio + group (when they are at the console), and leave it disabled for users + not in the audio group. + + + Steps to reproduce the bugs: + 1. Create 2 new users, user1 and user2 (to be sure you use Karmic default settings). 2. Restart. Login as one user, then double click on /usr/share/example-content/Aesop'\''s_Fables,_Volume_1_(Fable_1)_-_The_Fox_and_The_Grapes.spx 3. Switch to second user. The sound from the first user is still playing uninterrupted, even at gdm stage. 2. As the second user, double click on /usr/share/example-content/Ubuntu_Free_Culture_Showcase/SpiritOfUbuntu.ogv while the first user audio is still not finished. Result: First user prevent any sound to be played as second user (with Totem, the video even doesn't start, but with other applications you can sometimes get the video but no audio). When the first user audio finishes to play, audio can be played as user2, but that would block audio for user1 if you switch back to its session. Expected behavior: like in Jaunty and previous releases, sound from one user should stop playing when another session is active. In Jaunty and earlier, even VT had sound from one user when logged as this user, and from the other when logged as him. Some audio applications on one session also prevent any sound to be played for the other user session even when they have nothing to play. (Note: this is not a multi-seat setup, but a single seat computer with multiple user accounts. See attached screenshots for details). - Other example: a first user has a session open, playing sound with Amarok (paused) on a Gnome desktop. The second user chose Switch user in FUSA, then login. The new session doesn't have any sound, and the Sound Preferences window only lists Dummy Output - Stereo in the Output tab (Screenshot 1). In the hardware tab, nothing appears (Screenshot 2). When the first user closes Amarok, the second user now has the hardware showing in the Hardware tab (Screenshot 3) but no sound, since the Profile is Analog Stereo Duplex (should be Analog Stereo Output). When the user changes it to the right Profile, sounds works (see also Screenshot 4, compared to Screenshot 1 when no sound was played). The second user can now play sound, for example a flash video. Now though, the first user doesn't have any sound when coming back to its session (or more exactly, the only sound he can hear is the flash video being played in the second user's session, even though the users have switched. Any audio application the first user opens shows in Sound preferencesApplications, but doesn't output any sound, and moving the application individual sound sliders only affect the sound being played in session 2. All that was handled properly in Jaunty and previous Ubuntu releases. ProblemType: Bug Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: paphro 9493 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: paphro 9493 F pulseaudio Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xea30 irq 22' -Mixer name : 'Realtek ALC889A' -Components : 'HDA:10ec0885,1458a002,00100101' -Controls : 38 -Simple ctrls : 21 + Card hw:0 'Intel'/'HDA Intel at 0xea30 irq 22' + Mixer name : 'Realtek ALC889A' + Components : 'HDA:10ec0885,1458a002,00100101' + Controls : 38 + Simple ctrls : 21 Date: Sun Sep 20 22:09:30 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: alsa-base 1.0.20+dfsg-1ubuntu4 PackageArchitecture: all ProcEnviron: - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: alsa-driver Uname: Linux 2.6.31-10-generic i686 -- [Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences https://bugs.launchpad.net/bugs/433654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288470] Re: digikam cannot download pictures due to gvfsd-gphoto2
** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New -- digikam cannot download pictures due to gvfsd-gphoto2 https://bugs.launchpad.net/bugs/288470 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288470] Re: digikam cannot download pictures due to gvfsd-gphoto2
The volume should not be mounted. Especially if do nothing is selected. ** Also affects: gnome-volume-manager (Ubuntu) Importance: Undecided Status: New -- digikam cannot download pictures due to gvfsd-gphoto2 https://bugs.launchpad.net/bugs/288470 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 549451] Re: gksu uses keyring default but only login is auto opened
I checked, and login keyring is set as default. On another machine I saw the login keyring containing the password for unlocking the default keyring. So the functionality seems to be there. Is it an option that could just be disabled somewhere? -- gksu uses keyring default but only login is auto opened https://bugs.launchpad.net/bugs/549451 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: listview: inaccessible dir has same emblem as read-only dir [emblem inconsistency]
Could you please reopen/update the upstram bug with the current description? -- listview: inaccessible dir has same emblem as read-only dir [emblem inconsistency] https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 549451] [NEW] gksu uses keyring default but only login is auto opened
Public bug reported: Binary package hint: gksu During login seahorse/gdm/pam? seems to open login.keyring, but gksu always saves passwords to default.keyring. Either gksu needs to ask which keyring to use, or seahorse/gdm/pam? needs to be able to open secondary keyrings on login. (possibly saving the password to the secondary keyring in the login.keyring.) ** Affects: gksu (Ubuntu) Importance: Undecided Status: New ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Also affects: seahorse (Ubuntu) Importance: Undecided Status: New -- gksu uses keyring default but only login is auto opened https://bugs.launchpad.net/bugs/549451 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 549092] [NEW] users-admin: users are not added to users group
Public bug reported: Binary package hint: gnome-system-tools Current behaviour is: The users group exists but is not populated (empty). When setting up a (set group ID) group directory (i.e. /home/group/users) users can not collaborate on files in that directory. As long as g-s-t is overriding the groups for new users its profiles should default to add new users to the users group. Changed (repaired) behaviour would be: * Users are added to the users group on creation, so that group directories for users are functional again. * To fix extisting users users-admin could offer to add all existing users (according to adduser.conf: FIRST_UID / LAST_UID) manually/scripted to the users group if it finds some that don't belong to the users group. There should be no security risk involved, because no files belonging to the users group are created by default and at the same time users is applied as the primary group to users when (private) USERGROUPS are disabled in /etc/adduser.conf. The users group is generally used as a group refering to all users, and is important to make the user private group scheme work as designed. (this issue is filed in the context of https://wiki.ubuntu.com/MultiUserManagement ) ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- users-admin: users are not added to users group https://bugs.launchpad.net/bugs/549092 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: in list view: inaccessible directory has same emblem as read-only directory
For me (on 9.10) the issue with group dirs resolved to be an issue with the list view not showing all emblems. I have no idea why you are not seeing the correct emblems for non writeable dirs. (even though a lock may suggest you can not even enter the dir) But I can confirm that dirs owned by another user and group (which I am not a member of, i.e. like foreign home dirs) are missing/don't have the lock emblem. -- in list view: inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: in list view: inaccessible directory has same emblem as read-only directory
** Description changed: Binary package hint: nautilus 9.10: Nautilus 2.28.1 In the list view the difference in permissions does not result in appropriate icon differences. (only one emblem is shown) - A lock is shown (suggesting heavy access restriction but meaning read- - only, maybe better put a pen behind the lock if item is not writeable) - but the X for inaccessible is not shown in the list view. + i.e. in the case below a lock emblem is shown but the X emblem for + inaccessible is not shown in the list view. - I checked back, and can more precisely add that I see this after: + (The lock is suggesting heavy access restriction but meaning read- + only. Maybe better put a pen behind the lock or X if item is not + writeable) + + Case: I added a second user user2 to the machine and added user1 to the user2 group. After newly logging in as user1 and browsing to /home/user2 drwxrwxr-x 23 user2 user2 - I see both these examples with the lock emblem although I can not - enter the 2nd dir: + In listview I see both these examples only with the lock emblem + although I can not enter the 2nd dir: Desktop drwxr-xr-x 2 user2 user2 private drwx-- 6 user2 user2 - /root and /lost+found directories do display correctly with the x - emblem. + - /root and /lost+found directories do display with only the x emblem + in listview. + + - The lock emblem seems to be suppressed (in all views) for dirs other + then subdirs of homedirs? ** Summary changed: - in list view: inaccessible directory has same emblem as read-only directory + listview: inaccessible dir has same emblem as read-only dir [emblem inconsistency] -- listview: inaccessible dir has same emblem as read-only dir [emblem inconsistency] https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: listview: inaccessible dir has same emblem as read-only dir [emblem inconsistency]
** Description changed: Binary package hint: nautilus 9.10: Nautilus 2.28.1 In the list view the difference in permissions does not result in appropriate icon differences. (only one emblem is shown) i.e. in the case below a lock emblem is shown but the X emblem for inaccessible is not shown in the list view. (The lock is suggesting heavy access restriction but meaning read- only. Maybe better put a pen behind the lock or X if item is not writeable) Case: I added a second user user2 to the machine and added user1 to the user2 group. After newly logging in as user1 and browsing to /home/user2 drwxrwxr-x 23 user2 user2 In listview I see both these examples only with the lock emblem although I can not enter the 2nd dir: - Desktop drwxr-xr-x 2 user2 user2 - private drwx-- 6 user2 user2 + /home/user2/Desktop drwxr-xr-x 2 user2 user2 + /home/user2/private drwx-- 6 user2 user2 - /root and /lost+found directories do display with only the x emblem in listview. - - The lock emblem seems to be suppressed (in all views) for dirs other - then subdirs of homedirs? + - The lock emblem (read-only) seems to be suppressed (in all views) for + dirs other then subdirs of homedirs? + + Possible solution: + -Provide more intuitve read-only emblem and don't suppress it for system folders. + -Show inaccessible dirs greyed-out instead of with an X emblem. ** Description changed: Binary package hint: nautilus 9.10: Nautilus 2.28.1 In the list view the difference in permissions does not result in - appropriate icon differences. (only one emblem is shown) + appropriate icon differences. (can not show multiple emblems, only one + emblem is shown) i.e. in the case below a lock emblem is shown but the X emblem for inaccessible is not shown in the list view. (The lock is suggesting heavy access restriction but meaning read- only. Maybe better put a pen behind the lock or X if item is not writeable) Case: I added a second user user2 to the machine and added user1 to the user2 group. After newly logging in as user1 and browsing to /home/user2 drwxrwxr-x 23 user2 user2 In listview I see both these examples only with the lock emblem although I can not enter the 2nd dir: /home/user2/Desktop drwxr-xr-x 2 user2 user2 /home/user2/private drwx-- 6 user2 user2 - /root and /lost+found directories do display with only the x emblem in listview. - The lock emblem (read-only) seems to be suppressed (in all views) for dirs other then subdirs of homedirs? Possible solution: -Provide more intuitve read-only emblem and don't suppress it for system folders. -Show inaccessible dirs greyed-out instead of with an X emblem. -- listview: inaccessible dir has same emblem as read-only dir [emblem inconsistency] https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326135] Re: policykit introduction broke unix user/group privileges
** Also affects: policykit (Ubuntu) Importance: Undecided Status: New -- policykit introduction broke unix user/group privileges https://bugs.launchpad.net/bugs/326135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326135] Re: policykit introduction broke unix user groups
** Summary changed: - policykit introduction broke unix user/group privileges + policykit introduction broke unix user groups -- policykit introduction broke unix user groups https://bugs.launchpad.net/bugs/326135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 295795] Re: ISO burn on Intrepid with Brasero will not mount
are you using brasero? https://bugzilla.redhat.com/show_bug.cgi?id=571074 ** Bug watch added: Red Hat Bugzilla #571074 https://bugzilla.redhat.com/show_bug.cgi?id=571074 -- ISO burn on Intrepid with Brasero will not mount https://bugs.launchpad.net/bugs/295795 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326135] Re: user:group privileges ignored
** Summary changed: - User Privileges ignored + user:group privileges ignored ** Summary changed: - user:group privileges ignored + policykit breaking unix user/group privileges -- policykit introduction broke unix user/group privileges https://bugs.launchpad.net/bugs/326135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326135] Re: policykit breaking unix user/group privileges
** Description changed: I have set up a number of user accounts. On one of these accounts I adjusted the user privileges (System-Administration-Users and Groups-Properties-User Privileges). For one particular user I de- selected the two options: - * Connect to Internet using a modem - * Connect to wireless and ethernet networks + * Connect to Internet using a modem + * Connect to wireless and ethernet networks However, despite disabling access to the internet, the user is still able to connect to the internet through a wireless connection. I am assuming that this is a security vulnerability, because the intention is to deny access and this doesn't occur. I am using Ubuntu 8.10 + + + + Policykit has been introduced without supporting the unix groups. (used + by admins and set up by the installer) + + i.e. It is possible to create a policy that just said yes rather than auth_* where the default was no, for anyone in the netdev group + so theiy could do it without a password. + + - we should ship PolicyKit config files that make use of these groups. ** Tags added: regression ** Summary changed: - policykit breaking unix user/group privileges + policykit introduction broke unix user/group privileges ** Changed in: policykit-1 (Ubuntu) Status: Invalid = Confirmed -- policykit introduction broke unix user/group privileges https://bugs.launchpad.net/bugs/326135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326135] Re: User Privileges ignored
...we should also ship PolicyKit config files that make use of these groups. You're tres right, Milan. But you showed already twice a desktop guy that actually learned/understands the *nix systems before not breaking them but hooking in to them :) Kudos! -- User Privileges ignored https://bugs.launchpad.net/bugs/326135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: Inaccessible directory has same emblem as read-only directory
The directories of user2 aren't group writeable. Well then they really should show with a lock symbol (read-only). Looks like this may be a (different) bug that you are experiencing. (and since you are only shown one emblem per icon don't see any difference to the list view icons either) For my part (and this bug) it turned out that the issue is just with the list view not showing all emblems (or overlaying them) and thus making the icons indistinguishable. In icon or compact view the difference is visible. (I noticed that the lock emblem shown for private/ seems to be OK (contrary to what thought and wrote before) because user1 is in the user2 group but not itself user2.) ** Summary changed: - Inaccessible directory has same emblem as read-only directory + in list view: inaccessible directory has same emblem as read-only directory -- in list view: inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: in list view: inaccessible directory has same emblem as read-only directory
** Description changed: Binary package hint: nautilus 9.10: Nautilus 2.28.1 - A file/directory without write permissions shows a lock emblem even - though you can access it. + In the list view the difference in permissions does not result in + appropriate icon differences. (only one emblem is shown) - And this icon/emblem just looks the same as a file/directory that can - not even be read. - - The difference in permissions should result in appropriate icon differences. - (maybe put a pen behind the lock if item is not writeable) + A lock is shown (suggesting heavy access restriction but meaning read- + only, maybe better put a pen behind the lock if item is not writeable) + but the X for inaccessible is not shown in the list view. I checked back, and can more precisely add that I see this after: I added a second user user2 to the machine and added user1 to the user2 group. After newly logging in as user1 and browsing to /home/user2 drwxrwxr-x 23 user2 user2 I see both these examples with the lock emblem although I can not enter the 2nd dir: Desktop drwxr-xr-x 2 user2 user2 private drwx-- 6 user2 user2 /root and /lost+found directories do display correctly with the x emblem. -- in list view: inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: in list view: inaccessible directory has same emblem as read-only directory
Actually the lock emblem (read-only) you are not seeing is bogus when one does not have any read permissions. Maybe you are using a newer version that recognizes this? (and avoids showing multiple emblems) Are there any other emblem combinations used that may get messed up in list view? -- in list view: inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: Inaccessible directory has same emblem as read-only directory
** Changed in: ubuntu Status: Incomplete = Confirmed ** Changed in: ubuntu Status: Confirmed = Incomplete -- Inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: Inaccessible directory has same emblem as read-only directory
Hm, do your user2's directories have the same permissions as mine? Or are your directories of user2 group writeable? It would be OK for them not to have a lock emblem then, if you are browsing as user1 and member in the user2 group. Further details on the issue I observe: * The theme used in ubuntu is just called Human not humanity. * In the *symbol view*, I see the Desktop/ with lock emblem in the upper right corner (correct with the above mentioned perms) *and* private/ with the lock-emblem (not correct). The private/ directory has a X emblem in the lower right corner (correct). * In the *list view*, the X-emblem for private/ is not shown (but wrongly a lock emblem). Maybe the wrongly set lock symbol is overlaying the x emblem in the list view? -- Inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] Re: Inaccessible directory has same emblem as read-only directory
Thank you for helping out here. I am using the humanity theme though, and seeing this. I checked back, and can more precisely add that I see this after: I added a second user user2 to the machine and added user1 to the user2 group. After newly logging in as user1 and browsing to /home/user2 drwxrwxr-x 23 user2 user2 I see both these examples with the lock emblem although I can not enter the 2nd dir: Desktop drwxr-xr-x 2 user2 user2 private drwx-- 6 user2 user2 /root and /lost+found directories do display correctly with the x emblem. -- Inaccessible directory has same emblem as read-only directory https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
Good choice I think. Cutting down the settings forced with g-s-t GUI profiles is probably also a good measure for supporting the adduser profiles (or any other system wide profiles). -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326135] Re: User Privileges ignored
If policykit broke the desktop and unprivileged profiles this is a bug with policykit not being set up to honor those unix groups. It seems to merely match all users in admin group to root. ** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- User Privileges ignored https://bugs.launchpad.net/bugs/326135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
Hmm, seems like adduser wants to ensure UID == UPG-GID? Maybe g-s-t could offer to choose the next possible ID available, or optionally override the GID and possibly mess up the system? -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 490354] [NEW] should identify processes associated with network traffic
Public bug reported: Binary package hint: gnome-system-monitor The monitor shows network activity over time (last x seconds) It should also show the list of processes that had network traffic (in the last x seconds). Possibly clicking on a traffic peak in the network graph could identify the corresponding process. (information should be available from netstat / procfs / hethog) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- should identify processes associated with network traffic https://bugs.launchpad.net/bugs/490354 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488913] Re: users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser
I have had a look into /usr/share/system-tools- backends-2.0/scripts/Users/Users.pm. Unfortunatly I am not at all familliar with perl. If it is currently reading in settings from /etc/adduser.conf it should work with a linked profile as well, what you mean is probably reading in other installed profiles as well, and providing those to the frontend to choose from. I have to regret, I do no see how to do that. -- users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser https://bugs.launchpad.net/bugs/488913 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 489977] [NEW] write restricted icons equal read restricted icons
Public bug reported: Binary package hint: nautilus 9.10: Nautilus 2.28.1 A file/directory without write permissions shows a lock emblem even though you can access it. And this icon/emblem just looks the same as a file/directory that can not even be read. The difference in permissions should result in appropriate icon differences. (maybe put a pen behind the lock if item is not writeable) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- write restricted icons equal read restricted icons https://bugs.launchpad.net/bugs/489977 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
Just came across this answer. http://lists.alioth.debian.org/pipermail/adduser-devel/2008-February/003161.html -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253103] Re: users not belonging to users group
Changing package because the profiles with default groups in ubuntu are currently maintained in g-s-t (not adduser). ** Package changed: pam (Ubuntu) = gnome-system-tools (Ubuntu) ** Changed in: gnome-system-tools (Ubuntu) Status: Invalid = New ** Description changed: - Current behaviour is: The users group exists but when setting up a (set group ID) groupdirectory (i.e. /home/group/users) it does not work as expected, because the users group is not populated (empty). Changed behaviour would be: Users are added to the users group also when the (private) USERGROUP scheme is used, and a created users groupdir is functional. - In order for the users to belong to the users group by default two - solutions exist. + In order for all (regular/login) users to belong to the users group by + default two solutions exist. 1) centrally add one line to /etc/security/group.conf (for dynamic addition to the group during login): *; *; *; Al-2400; users 2) change group membership off all existing users manually/scripted and modifying adduser defaults for new users to have them added to the users group. There should be no security risk involved, because no files belonging to users group are created by default and at the same time users is applied as the primary group to users when disableing (private) USERGROUPS in /etc/adduser.conf. The users group is generally used as a group refering to all users and makes the user private group scheme work as designed. (Context of this issue is https://wiki.ubuntu.com/MultiUserManagement) -- users not belonging to users group https://bugs.launchpad.net/bugs/253103 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488913] Re: users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser
I have actually produced a patch to adduser now, as far as I could. Since it is my first one I'd appreciate any feedback. Its in LP: #489136 -- users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser https://bugs.launchpad.net/bugs/488913 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin not following Debian policy
Concerning the UPG group membership: As it is not necessary (and redundant) and gives problems I believe users should not be made members of their main groups. As a result of adding the user to its main group deluser thinks the primary group is not one adduser has created automatically as a user private group (UPG) but a manually added group. So the empty group will not be deleted automatically. However if it truly is a UPG (created off record by users-admin) but is not being deleted together with the user, this in turn may very quickly lead to UPG accounts with primary GID != UID (when a user has been deleted before). Only if, of course, the adduser UID allocation algrithm is implemented in such a way that it does not skip UIDs with taken GIDs, or the calling program makes that decision. (May this be an issue for users-admin or adduser? May need fixing then, the same thing might happen as soon as a group is created manually.) (Let me stress that my feedback here is merely from a admin/users point of view, not of any knowledge from adduser or useradd which it in turn I believe depends on.) FYI: I was editing the (UPG) related wiki page https://wiki.ubuntu.com/MultiUserManagement when I got to users-admin. You may like to have a look at. Those kind of informations might be interesting for any users-admin user, and good for its help or wizard texts? -- users-admin not following Debian policy https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
Hi, what a nice coincidence. :) Thank you for your feedback. I have now updated the wiki to match the adduser behaviour as well. I've seen now, that only useradd/groupadd is part of the debian passwd package, but adduser uses it. (But still, adduser could be smarter and remove the group if the user was the only member of it.) Imagine the group of santaclauses. Around the end off the year different people get to be members therin. If the manually created group would get deleted with the last santa claus resigning in january, next year a newly created group would probably not get the same GID . Files provided in the /home/group/santaclauses would not be usable by the new group. I don't know the problems GID != UID UPGs could make other then not being easily recognizable by humans, when seeing the numerical IDs in .tar files or mounts on other machines. users-admin has its own algorithm to find a good UID/GID ... If that really matters, I could remove this behavior so that we ask adduser to choose [the UID/GIDs]. This is generally a good idea, but may not be very high priority for me if it does not hurt. Oh, well, that kind of behaviour however can actually hurt heavily, yes. (another tool has hit me with that) Especially in networked evironments you assign special UID/GID ranges to use (and configure the useradd/adduser hooks to take care of it). Now if me or some other admin of the institution switches the GUI tool and it starts choosing IDs of its own liking the tool can cause quite adverse effects. So if you can, please do not default to override the numerical IDs assigned by the system. In all I am happy to hear users-admin is generally using the adduser tool, and it's only some avoidable overrides that are troublesome. BTW: (for forwarding to the debian bug you linked) the default from /etc/login.defs: # This enables userdel to remove user groups if no members exist. # # Other former uses of this variable such as setting the umask when # user==primary group are not used in PAM environments, thus in Debian # USERGROUPS_ENAB yes In this case userdel should probaly also alter the Warning: group X is now empty. message to According to USERGROUPS_ENAB yes, the empty private user group has been deleted as well. or somthing. -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
All right, has been a pleasure. -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488913] [NEW] users-admin defaults to override system wide defaults from /etc/login.defs, /adduser.conf
Public bug reported: Binary package hint: gnome-system-tools splitting this from #488158 we implement user profiles in users-admin. Those allow the distribution/admin to present users with typical account types, which set sensible default values for home dir, shell, groups membership (esp. admin) Nothing wrong with those, because adduser is used and say EXTRA_GROUPS defined in /etc/adduser.conf will be honored, right. and UID. With this however I believe that any tool should *default to* leave the assignment of numerical IDs to be the responsibility of the system (it's part of the stuff that gets tweaked centrally in /etc/login.defs and /etc/adduser.conf) It's kind of silly we implement [user profiles] on the GUI side, but as we can't be sure the distribution supports this kind of feature (and none does ATM) Its probably ok if profiles are not supported otherwise and its easier then submitting a patch. All I can do for now is have a look at the profiles handling code so that when no profiles are set, we don't specify any UID, and the backends leave adduser decide for us. Not very hard, but our protocol does not support it ATM. Great. And its propably all that would be needed. Together with removing the settings that overide system defauls from the shipped profiles. (i.e. have empty uid-min=, uid-max=, home-prefix= and shell= lines ; since those should have sensible system defaults) (OT: Of course a patch to useradd -D or adduser to support different profiles would still be great, too. Single profile definition and configuration code is available in adduser.local. The doc is on any debian/ubuntu system file:///usr/share/doc/adduser/examples/README ) ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- users-admin defaults to override system wide defaults from /etc/login.defs, /adduser.conf https://bugs.launchpad.net/bugs/488913 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488913] Re: users-admin's profiles feature forces [GU]ID, home dir, shell and groups to adduser
Even better then. :) (yes adduser.conf and adduser.local.conf together provide only one profile ) ** Summary changed: - users-admin's profiles feature forces [GU]ID, home dir, shell and groups to adduser + users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser -- users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser https://bugs.launchpad.net/bugs/488913 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488913] Re: users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser
Oh, I just realized that adduser supports user profiles, maybe even since its first version. System wide profiles can be provided as adduser.conf.profile and the profile is selected with: # adduser --conf adduser.conf.profile username -- users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser https://bugs.launchpad.net/bugs/488913 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
From viewing users I created with adduser I just noticed that in the g-s-t edit group window the users name is of course not checked when viewing any UPG created with adduser. It may be nice to remove that user from the list and have some sort of indicator that a group is a (possibly private) primary group of user x instead, just as an affirmation that everything is ok. Another UI thing is that when changing the primary group of user, the g-s-t user may want the (edited) user to stay a member of the prior group. (you probably already had that in mind) -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin should leave adduser handle main group creation
s / remove that user from the list / remove that checkbox from the list -- users-admin should leave adduser handle main group creation https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488913] Re: users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser
Alternativly adduser.conf can be shipped as a symlink to a adduser.conf.dist (distribution) profile. This allows to switch the symlink to an admin provided profile, so that it will be used as a adduser default, without having to touch the .dist profile. -- users-admin profiles default to force [GU]ID, home dir, shell and groups to adduser https://bugs.launchpad.net/bugs/488913 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] [NEW] user/group: management not following policy
Public bug reported: Binary package hint: gnome-system-tools I have noticed differences with the adduser command. Are system-tools user and groups following policy and using debians useradd/adduser facility with its administration hooks? Debian policy states: Packages other than base-passwd must not modify /etc/passwd, /etc/shadow, /etc/group or /etc/gshadow. (http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2) ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- user/group: management not following policy https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488158] Re: users-admin not following Debian policy
Uh, oh, I got that feeling you know ;-) Seriously, exactly as you write I was seeing the user being added to his primary private group. adduser tester produces this group entry: tester:x:1006: where users-admin produced: test:x:1005:test I had experienced much trouble before because of another tool not using adduser (with its hooks). (probably why I got suspicious so quickly) Thank you for your response and feedback. (Strange you're right, maybe adduser once belonged to base-passwd and the doc didn't get updated?) -- users-admin not following Debian policy https://bugs.launchpad.net/bugs/488158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 42052] Re: Screen not locked on resume from hibernate/suspend
Same in hardy maybe putting a script in a pm-tools directory to lock the screens (and open consoles Alt-Ctrl-F1, ...) -- Screen not locked on resume from hibernate/suspend https://bugs.launchpad.net/bugs/42052 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
