** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41454575/Dependencies.txt
** Attachment added: "InitctlList.txt"
http://launchpadlibrarian.net/41454576/InitctlList.txt
** Attachment added: "ProcAttrCurrent.gz"
http://launchpadlibrarian.net/41454577/ProcAttrCurrent.
Public bug reported:
Binary package hint: gnome-settings-daemon
This seems to be a meta-glitch relating to an update that I applied last
night.
Logging in after booting this morning showed the custom background
image, but none of the (autohide) taskbars appeared nor did alt+f2 work.
Switching t
Maybe it's like bug 418417 but from another angle?
--
sleep,hibernation fail
https://bugs.launchpad.net/bugs/535553
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
I think this bug effects me too; and is matched to the sometimes
detected kernel-error. However I only discovered it when I realized I
was selecting Sleep and wondered where Suspend and Hibernate options
were tossed; leading to a google search.
--
sleep,hibernation fail
https://bugs.launchpad.ne
The problem with a normal table is you get a result like this:
# | Really Long Description | Another big description | A third description
|
User 1 |
User 2 |
User 3 |
I won't bother adding the spaces since the display will strip them out,
but I think you can figure out how that grid wastes
Public bug reported:
Binary package hint: gnome-system-tools
This is a wishlist priority item, please change that as I don't have
that kind of access.
I think it would be much easier to understand and control current
account privileges if there were a tabular format.
Across the top slanted ( li
Also, I just noticed when going to file the other wishlist bug... Why
was my bug linked to GDM as a duplicate? I specifically chose the
proper package and hadn't looked; this isn't related to mine at all!
--
Update PAM policy to allow password-less logins set up via users-admin
https://bugs.lau
Sorry, I was trying to clarify potential use cases, both for passwords
with and passwords without sys-admin capabilities. Editing accounts is
probably some other bug... all the usability issues that I see as
related actually collections of different bugs. Each bug a small piece
of grit fouling th
If that is the case then the root user should be added to the admin
group by default.
** Changed in: gnome-system-tools (Ubuntu)
Status: Invalid => New
--
System administration task dialgues do not allow the account 'root' to
authenticate even with a password
https://bugs.launchpad.net/b
My use case is different. My parents are near retirement and just want
a super-easy-to-use computer; that means security via physical access
only. Accounts are merely a preference filing system to them.
Password-less accounts in the admin group are a questionable thing; but
if that's what the sy
Public bug reported:
Binary package hint: gnome-system-tools
Tested on 9.10 beta and 9.04 as well.
Steps to reproduce:
#Set a root password.
sudo passwd
# Verify you can login at a local console.
(ctrl+alt+f1) login...
Logout/switch back to your X session.
Attempt to launch a graphical system
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
While I agree that the correct policy would be to (after a clear
warning) allow password-less accounts...
'Documentation' in this case should be a CLEAR error message triggered
by this combination of events:
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
Having this behavior isn't in it's self a bug. Not /documenting/ the
behavior properly in dialogs related to system administration tools /is/
a bug. Additionally when root ==HAS A PASSWORD== it is a valid ac
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
I should clarify, this is an issue I encountered trying to unlock the
privileged mode of system administration tasks. As an example,
adding/modifying users/groups with the tool found in the system menu.
It sh
*** This bug is a duplicate of bug 393854 ***
https://bugs.launchpad.net/bugs/393854
The user logged in at the time was NOT root. As I described, I had
created a root password (I like su better than sudo -s, and local root
login is nicer for servicing a system than the potential alternative
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33849674/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/33849675/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/33849676/ProcStatus.txt
--
Unable
Public bug reported:
Binary package hint: gnome-system-tools
Unable to authenticate as user 'root' (I have added a password) OR as
current user (account has no password due to end user preference).
The end users in question want one click logins and to not remember
passwords. They might be conv
17 matches
Mail list logo
