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,
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:
** 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 :
** 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 :
** 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:
** 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
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
~/.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
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
** 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
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
@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
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
** 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:
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:
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
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
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
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
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
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:
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
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
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
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
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
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.
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
--
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,
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)
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
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
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,
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
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
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
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
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
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
** 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
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
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
** 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
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
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
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
** 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
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
** 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
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,
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
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
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
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
** 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
** 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).
+
+
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)
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
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
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
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
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.
** 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
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
** 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
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
** 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
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
** 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
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)
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
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
** 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
...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
** 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
** 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
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
** 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
** 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
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
** 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,
** 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
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
** 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
*** 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
** 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
** 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
** 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
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.
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
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
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
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
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
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.
95 matches
Mail list logo
