Thanks for the report, but the stack trace is missing many information
and is completely unusable. If you see the problem again, please reopen
the bug, and we'll find a way to debug this by hand.
For what it's worth, OpenOffice is not related at all to this crash.
** Changed in:
Let's assume it's been fixed, since I've not seen the crash since then.
But I should have reported it upstream sooner, to be sure it's gone.
** Changed in: empathy (Ubuntu)
Status: Incomplete = Invalid
--
empathy crashed with SIGSEGV
https://bugs.launchpad.net/bugs/554708
You received
*** This bug is a duplicate of bug 533870 ***
https://bugs.launchpad.net/bugs/533870
** This bug has been marked a duplicate of bug 533870
Crash in SelfConfig on amd64
--
Unable to change name in Users Settings
https://bugs.launchpad.net/bugs/623361
You received this bug notification
You're right, but that doesn't change much of the problem: the fix is
here, waiting for somebody to upload a new version to Lucid. But Ubuntu
devs are quite busy, and a GUI to set up system level shares are not
considered as the highest priority.
--
shares-admin doesn't see NFS and SMB installed
Sorry to all, but this report has become a terrible mix of different issues, so
I can only close it. Please individually file new reports if you are still
able to experience you issues with recent versions of Ubuntu. A few
explanations, though:
- Anton: 8.10 is no longer supported, so I won't
That's not the solution, we'd need to find the underlying bug that
reinstalling the package fixes. But now that you don't experience the
bug, it's impossible to discover what was going wrong before.
Sorry for the lack of answer on my part last month, but now I can only
close the bug - if somebody
*** This bug is a duplicate of bug 542183 ***
https://bugs.launchpad.net/bugs/542183
In Lucid, you can't give a UID when creating a user: you can change the
UID afterwards, though. But there's bug 542183, so I'm marking this as a
duplicate.
** This bug has been marked a duplicate of bug
2.10.0 has been uploaded to Maverick, waiting for a backport to Lucid.
** Changed in: system-tools-backends (Ubuntu)
Status: Triaged = Fix Released
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a
Package is gnome-control-center.
Why do you say transitive in the title? To me, proxy settings simply
don't work on your system, it's as simple as that.
** Package changed: gnome-system-tools (Ubuntu) = gnome-control-center
(Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Importance:
Fixed with 2.10.0 in Maverick (delays are much shorter). Waiting for a
Lucid backport.
** Changed in: system-tools-backends (Ubuntu)
Status: Triaged = Fix Released
** Changed in: system-tools-backends
Status: Fix Committed = Fix Released
--
users-admin has significantly delayed
Public bug reported:
Binary package hint: system-tools-backends
Lucid ships with system-tools-backends 2.9.4-0ubuntu1, which is an
upstream development version considered as unstable, and which suffers
form several serious bugs. Maverick now has 2.10.0 synced from Debian,
with very limited
** Attachment added: system-tools-backends_2.9.4-0ubuntu1_2.10.0-2.diff.gz
https://bugs.launchpad.net/bugs/616682/+attachment/1485650/+files/system-tools-backends_2.9.4-0ubuntu1_2.10.0-2.diff.gz
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided = High
** Description
*** This bug is a duplicate of bug 433654 ***
https://bugs.launchpad.net/bugs/433654
Thanks for the report, this is indeed a very confusing behavior caused
by inconsistencies between packages. But that's known as bug 433654 for
a while. The suggested simple and dirty fix would even be to
Adding a task for Epiphany, as on my box (bug 617030) the crash doesn't
occur in Firefox.
** Also affects: epiphany-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: epiphany-browser (Ubuntu)
Importance: Undecided = High
** Changed in: epiphany-browser (Ubuntu)
I've applied the changes in explained in my comment #19, I hope that
will be enough. Commit is 85e1a92, which will be available in GNOME 2.32
for Maverick. See attached screenshot for a preview (sorry for the ugly
theme, GTK+3.0 without engines that is).
** Attachment added: Capture.png
** Changed in: gnome-system-tools (Ubuntu)
Status: Fix Released = Triaged
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = Fix Released
--
the word 加入 in group managment should be 新增
https://bugs.launchpad.net/bugs/603746
You
I understand this concern, but I don't think that's the problem here:
- Add/Delete means Add/Delete and item of the list, and the ambiguous point
here is: what's in the list? (users or groups). The general idea of having
short labels is pretty intuitive and is used in many other places (file
...a global configuration window, and not something affecting only the
current user.
** Changed in: gnome-system-tools (Ubuntu)
Status: Invalid = Triaged
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Low
--
the word 加入 in group managment should be 新增
Only users with a UID = 1000 are shown in GUIs, since other users are
system ones. What UID did you use?
--
Users vanish from User Settings after changes made to /etc/passwd
https://bugs.launchpad.net/bugs/362421
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I don't believe that would improve things. The confusion is not around
the fact that the list represents groups: it's quite obvious, since the
list in the main window represented users, and you clicked on Manage
Groups. The problem can be that we don't know whether the groups are
those present on
I don't think there can be a real confusion, simply clicking on the
button will be enough to find out what the button means if needed. I'll
add a tooltip if you think that's worth it, though.
--
the word 加入 in group managment should be 新增
https://bugs.launchpad.net/bugs/603746
You received this
The fix has been released upstream with 2.30.2, which could be
backported to Lucid at some point.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Fix Released
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Low
--
Full user names not correctly displayed in
My point was that it should be obvious what the button does for most
people, and that /in addition/ there's no risk of being misled since in
the end, clicking the button will explain it all. But I agree GUIs have
to be intuitive.
The fact that the string is not obvious in Chinese is not my
Le samedi 07 août 2010 à 14:04 +, Cheng-Chia Tseng a écrit :
In my opinion, the window title here says group settings doesn't
convey that this is a list of groups, so users don't know whether
he/she is going to add a new group to the list or he/she is going to add
a existing group for the
*** This bug is a duplicate of bug 542183 ***
https://bugs.launchpad.net/bugs/542183
** This bug has been marked a duplicate of bug 542183
[users-admin] Changing UID doesn't work
--
Unable to change UID from users-admin gui
https://bugs.launchpad.net/bugs/613618
You received this bug
In English, we use Add/Delete as in many other places of the desktop. I
don't think this needs to be changed, as it's perfectly clear. If
Chinese suffers from ambiguity here, feel free to use another word
that's better suited to group creation - and if you say the word is
correct, changing English
You don't really need to create a user with a specific UID as long as
changing it's UID right after creation does the right thing. So what we
need is to chown the home directory when changing UID for a user. I
won't allow choosing UID on user creation since that would bring back
the bloat for most
Closing then.
Thanks for your observations, but these are completely separate problem
that apparently come from adduser/deluser, and should be reported to its
authors. adduser/deluser are developed by Debian, you may want to report
a bug there - hoping somebody is still working on them.
**
No need for this workaround - you'd better edit /etc/passwd and
/etc/group directly. For the proper fix, we just need to package system-
tools-backends 2.10 to Lucid.
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you
Let's be clear: the fix is known upstream for ages, see my comment #2
above. So no need to discuss it again, you just have to find somebody
willing to upload the version to Lucid.
The question of whether we should chown the home directory is another
problem, which could be easily solved using the
Hm, that didn't work , probably because you didn't provide a PID. I was
silly, since you're on Lubuntu, gnome-settings-daemon isn't running. So
start users-admin, get its PID using 'pidof users-admin', and replce
$PID with this value in the command.
BTW, you can paste command outputs directly
Is the user member of the 'admin' group? Are you logged in remotely
(VNC...)? What's the output of 'ck-list-sessions'?
--
Polkit authentication fails in Lubuntu
https://bugs.launchpad.net/bugs/599050
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
OK, I see the problem. Actually, it's completely the contrary of what
you said. ;-)
The button doesn't seem to check for PolicyKit authorizations when
activated by keyboard, while it does when clicked using the mouse. So in
your case this *appears* to work when you press Space, but it actually
You can check easily what groups you are in by running the 'groups'
command.
Could you run the two pkcheck commands again, but after having run
sudo killall polkitd
sudo /usr/lib/policykit-1/polkitd
and post the three outputs here? (Don't stop the last command while
running the two pkcheck
Please don't mix bugs. You refused to mark this one as a duplicate, and
know you act as if it was!
So in the other report, we should find what's the exact lxde package
that should disable gdm when installed, or at least find a solution. I
don't know lxde at all, so you'll need to find it yourself
What does these commands say?
pkcheck --action-id org.freedesktop.systemtoolsbackends.set --process $PID -u
pkcheck --action-id org.freedesktop.systemtoolsbackends.self.set --process $PID
-u
(replacing $PID with the output of the command 'pidof gnome-settings-daemon'
for example).
--
Polkit
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Ah, sorry for missing the strace! I've looked at it, and comparing with other
bug, the same permission issues appear. So, please continue the steps described
by Martin from comment #12, and go on while
Looks like a gnome-panel bug, since it's the program using CPU. But if
you're not able to reproduce it, we cannot do anything but close the
bug! What happens if you retry the same operation, e.g. from a separate
user accout?
For the record, when trying to debug, you should move configuration
So could you post the output of 'ps x | grep polkit' here? Also, please
run 'users-admin' from a terminal, and paste the messages here too.
--
users-admin Click to make changes button does nothing
https://bugs.launchpad.net/bugs/599441
You received this bug notification because you are a member
Weird. polkit-gnome-authentication-agent-1 should definitely be running,
and though starting it doesn't solve your problem.
What does users-admin and /usr/lib/policykit-1-gnome/polkit-gnome-
authentication-agent-1 output if you start them in a terminal (the
second first), and reproduce the bug?
** Changed in: gnome-panel (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-panel (Ubuntu)
Status: New = Incomplete
--
gnome-panel did not start properly after I moved it
https://bugs.launchpad.net/bugs/599462
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
So we're on a completely different bug now. The dbus issue was likely
related to permissions on a file included in the package. It would be
interesting to reproduce in a virtual machine a fresh install of
Could be interesting then! ;-)
The problem is, you're using GNOME 2.28 and it's not impossible that the
bug is already fixed in 2.30. So debugging could be a waste of time.
Since Lucid is a LTS release, do you plan to upgrade to it at some
point? It would be much better to check that 2.30 has the
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
And what about the other questions? The error message you see can be
related to several know bugs and may not be related. The output of
polkitd might be much more interesting.
--
Failed to execute program
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
users-admin worked but it didn't provide interesting information. The
polkitd output would still be required to understand why PolicyKit
thinks you cannot authenticate. See the end of my comment #17, after
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
** (process:32132): DEBUG: not authorized
So that's polkitd that thinks you don't have the required privileges.
Does that user have a password? I not, please try with a user with a
password.
What does
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Maybe PolicyKit is unable to authenticate a user with its key. Could you
try with a test account that has a password?
ConsoleKit seems to work fine, so it's very likely that password is the
problem.
--
Thanks for the infos. So that's really a problem with PolicyKit or it's
configuration files. Pretty hard to guess where the problem may come
from.
Please check that your /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
file contains,
[Configuration]
AdminIdentities=unix-group:admin
and
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
Ah, I hadn't noticed this comment before posting on the other bug, where
you didn't mention the fix didn't work.
Could you try the solution described at:
Could you run
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
and retry?
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided = Medium
** Changed in: system-tools-backends (Ubuntu)
Status: New = Incomplete
--
users-admin Click to make changes button
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
If the solutions of the duplicate didn't work, it may be something
different in the end. Have you tried the suggestion above too?
Do you get the same problem when try to run other programs, e.g. jockey-
gtk
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
OK, so that's not a bug specific to users-admin. Didn't reinstalling the
package solve the problem?
As I said above, /even if it's not the same issue/, please follow the
instructions given by Martin Pitt
I meant 108 of course.
When I referred to the other report, I thought about things like:
ls -l /lib/dbus-1.0/dbus-daemon-launch-helper
Or the one explained at:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/295405/comments/10
The idea is that I'm going to have to reproduce the same steps
*** This bug is a duplicate of bug 599050 ***
https://bugs.launchpad.net/bugs/599050
** This bug has been marked a duplicate of bug 599050
Cant change username
--
Cant make auto login to Lubuntu
https://bugs.launchpad.net/bugs/599044
You received this bug notification because you are a
*** This bug is a duplicate of bug 599050 ***
https://bugs.launchpad.net/bugs/599050
** This bug has been marked a duplicate of bug 599050
Polkit authentication fails in Lubuntu
--
Cant open advanced settings
https://bugs.launchpad.net/bugs/599052
You received this bug notification
*** This bug is a duplicate of bug 599050 ***
https://bugs.launchpad.net/bugs/599050
** This bug has been marked a duplicate of bug 599050
Polkit authentication fails in Lubuntu
--
Cant change account type
https://bugs.launchpad.net/bugs/599051
You received this bug notification because
Thanks for your report. Usually, reporting two very close issues is not
a good idea because they are likely to be related. In your case,
authentication failure is probably the cause of both.
Please run 'users-admin' from a console and post the output here.
Also, please run
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
OK, the problem is obvious and exactly the same as for the other report.
/lib/dbus-1.0/dbus-daemon-launch-helper shouldn't be owned by the
'avahi' group, but by 'messagebus'.
See my comment at
What problem still exists? ;-) There were three of them, and I got no
answer to confirm. So I'm closing it, please open a new report with
detailed explanations.
David: feel free to reopen when you can answer my question.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete =
Please don't reopen a fixed bug at random. Why on earth do you believe
this is the same problem?! None of the symtoms you describe is similar.
It's not because it has high priority that people will fix your bug more
quickly. As you said yourself, I checked and /etc/groups did not appear
to be
As I suggested on the other report (bug 295405), could you try setting
UID for user messagebus to 102 (if that's not used by another one)? More
generally, please follow the procedures I described there to check that
it's not the same problem (very likely).
(BTW, when I said liboobs, I thought
True, but you have to find a better place for it! ;-) The only other
area I could think of was behind the users list, but that wasn't really
nice either.
Anyway, users-admin is going to be replaced by accounts-dialog, so this
will probably never be fixed. Thanks for reporting, though.
** Changed
** Bug watch added: GNOME Bug Tracker #619588
https://bugzilla.gnome.org/show_bug.cgi?id=619588
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=619588
Importance: Unknown
Status: Unknown
--
ampersand in user real name freezes login screen
Thanks for your report. Could you run the command:
'sudo apt-get install --reinstall gnome-system-tools'
and see if that fixes your problem?
The file triggerring the error is a file present in 2.28 but not in
2.30. But I don't know why it makes the upgrade fail. Nobody has
reported this problem
*** This bug is a duplicate of bug 570828 ***
https://bugs.launchpad.net/bugs/570828
If you're not using Ubuntu Studio, you have NetworkManager, else you can
install it, or wait for the tab to come back (hopefully). The decision
was made by developers that didn't know Studio wasn't installing
'sudo update-rc.d cups defaults'
And for the tool, a new one is being developed ATM. See
http://jacob.peddicord.net/blog.html
--
System Administration Services (services-admin) missing
https://bugs.launchpad.net/bugs/437905
You received this bug notification because you are a member of Ubuntu
no!chance: See bug 160862 rather. This is a know problem that is fixed
in Lucid and should be fixed at some point in Hardy too. Though the
original issue is that you had weird characters in your /etc/group file,
nowadays users-admin shouldn't get crazy when it encounters this kind of
thing.
I'm
*** This bug is a duplicate of bug 433654 ***
https://bugs.launchpad.net/bugs/433654
** This bug has been marked a duplicate of bug 433654
[Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
--
[Users and Groups] Advanced Settings: User Privileges on using
No, that's really the same bug. users-admin shouldn't show that group at
all since it's plainly broken. This behavior doesn't make sense. That's
why I said we should remove the audio group, which would fix the bug for
all people that were added to it without noticing.
If that doesn't seem right,
Przemysław: edit /etc/network/interfaces (e.g. with 'sudo pico
/etc/network/interfaces'), and remove everything BUT the first lines:
auto lo
iface lo inet loopback
Then you can add the interface using System-Preferences-Network
Connections
--
gnome-network-admin on UbuntuStudio doesnt allow to
Chauncellor: at least, if you were able to play with permissions, you
should be able to find this bug report. With the new users-admin, it's
harder to tweak fine-grained permissions, so hopefully nobody will do
this anymore.
--
[Karmic][Lucid] Only one user has sound; no hw shows in Sound
Fix released and uploaded for a long time.
** Changed in: liboobs
Status: Fix Committed = Fix Released
** Changed in: liboobs (Ubuntu)
Status: Triaged = Fix Released
--
shares-admin crashes on start when udev has been restarted without reboot
Thanks for the report. Do you mean you were removing two accounts by
selecting them both at the same time, and clicking Delete once? Did the
crash happen before or after the confirmation dialog asking whether to
remove user files?
** Changed in: gnome-system-tools (Ubuntu)
Status: New =
HP: and what does 'ps x | grep keyring' returns on your box after
booting without your script?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
Seems to be the same issue then. Are you using autologin or password-
less login?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
Yes, but that doesn't change the problem. Bug 583428 is about g-k-d
hanging when started without a password, whether it actually needs one
or not. ;-) BTW, let's comment this on that report rather than here,
which may not be the same issue.
--
gnome-keyring-daemon fails to start
use_md5 parameters has been removed in 2.10, we now use chpasswd to set
the password, and don't play with encryption methods.
** Changed in: system-tools-backends (Ubuntu)
Status: New = Fix Released
--
including a file leads to confusion about whether md5 is being used
That would be a different bug then. Could you paste here the line from
/etc/passwd which was the problem? National characters shouldn't be an
issue as long as they are in UTF-8; if they aren't, then some strange
tool must have gone wrong when writing to it.
Closing the bug since in Lucid we no
** Changed in: gdm (Ubuntu)
Status: Confirmed = Triaged
--
Unable to change options on passwordless login
https://bugs.launchpad.net/bugs/508552
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
** Package changed: gnome-system-tools (Ubuntu) = gnome-control-center
(Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided = Low
--
Proxy auto-config (PAC) not usable by some applications
https://bugs.launchpad.net/bugs/587097
You received this bug notification
g-k-d should be started by it's PAM module. If it's not started on login
before any app tries to use it, then it's the problem. What does
/etc/pam.d/gdm contains?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a
Yeah, the problem is that the menu is shared with the groups, so fixing
this would require splitting it from there. It may be easier to remove
completely this menu, since it's mainly redundant. But definitely not a
very serious issue...
Don't bother reporting this upstream, I manage the bugs here
Upstream has committed a fix which should be made available with gnome-
keyring 2.30.2.
--
if ( users-admin - password: Not asked on login) gnome-keyring-daemon hangs
https://bugs.launchpad.net/bugs/583428
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Maybe you should remove the .service file you added manually. Bug 525642
is fixed now, and manual tweaks like that can lead to problems. It's
possible that gnome-keyring is started via D-Bus before the PAM module
loads it, so it lacks the --login option that automatically unlocks the
keyring. But
That's because Samba and NFS no longer use SysV boot script, but Upstart
jobs. Thus, they are not detected even if they are installed. We need a
temporary fix in Lucid for that, possibly a ugly hack.
In the long term, though, that's going to be a problem: we need minimal
support for Upstart jobs,
** Branch linked: lp:~nalimilan/ubuntu/lucid/gnome-system-tools/shares-
services
--
shares-admin doesn't see NFS and SMB installed (no support for Upstart jobs)
https://bugs.launchpad.net/bugs/574046
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Yeah, I know, normally the --login option should be present in your case, but
for some reason it's not. I don't really see why it should work differently on
your system than on mine (say). Do you have a personal config starting g-k?
e.g. check with:
ls ~/.config/autostart/*keyring*
Else, you
ntpdate is not supposed to be run all the time AFAIK, it's mainly here
to allow synchronizing the clock manually (what the Sync Now button is
time-admin does), and creating scripts to do that. On my box, syslog
doesn't contain anything related to ntpdate... Can't you think of any
package you may
Is that without autologin and without password-less enabled?! That seems
very similar to what we get when it's on.
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
But that's not a problem with time-admin, which is not supposed to
control ntpdate at all. It's just that ntpdate shouldn't run by ifup
when interfaces are enabled. Else, there's no point in optionally
installing the ntp daemon.
I suspect ntpdate is not run when your connections are managed using
Is this still buggy in Lucid?
Anyway, I think fixing bug 583994 by replacing ntpdate with ntpd would
solve this the right way.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member
*** This bug is a duplicate of bug 573387 ***
https://bugs.launchpad.net/bugs/573387
OK, this is actually a duplicate. We're debugging this upstream ATM.
** This bug has been marked a duplicate of bug 573387
gnome-keyring-daemon fails to start
--
if ( users-admin - password: Not asked
** Summary changed:
- gnome-keyring-daemon fails to start
+ gnome-keyring-daemon fails to start when password-less login is enabled
** Changed in: gnome-keyring (Ubuntu)
Status: New = Triaged
** Changed in: gnome-keyring (Ubuntu)
Importance: Low = Medium
--
gnome-keyring-daemon
** This bug is no longer a duplicate of bug 573387
gnome-keyring-daemon fails to start
--
if ( users-admin - password: Not asked on login) gnome-keyring-daemon hangs
https://bugs.launchpad.net/bugs/583428
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Ah, that was what I feared: your bug is different from the password-less
issue. So let's say the latter is bug 525642, and deal with your problem
here. What does 'ps x|grep keyring' return, with and without autologin
enabled? What errors do you get in /var/log/auth.log in both cases?
(The logs
*** This bug is a duplicate of bug 542183 ***
https://bugs.launchpad.net/bugs/542183
** This bug has been marked a duplicate of bug 542183
[users-admin] Changing UID doesn't work
--
chainging user or group ID does nothing
https://bugs.launchpad.net/bugs/583951
You received this bug
Fix committed upstream, to be released with gnome-system-tools 2.30.2.
** Changed in: gst
Status: Confirmed = Fix Committed
** Bug watch added: GNOME Bug Tracker #619354
https://bugzilla.gnome.org/show_bug.cgi?id=619354
** Also affects: gnome-control-center via
Thanks for your report. This would be a bug in gnome-keyring-daemon,
which should start and ask for the password if there's any.
Is the keyring daemon running or not? You can check this using 'ps x |
grep gnome-keyring-daemon'. If it's not running at all, could you run
'gnome-keyring-daemon -sf'
I'm able to reproduce the problem. Actually, gnome-keyring-daemon is
hanging on login because with the --login option, it's waiting for the
password to be passed by PAM via stdin, which never happens. While it's
in this state, it won't anwser D-Bus messages, and will also prevent
D-Bus from
I think the upstream report is not related, see bug 525642 instead.
You're not using users-admin's password-less login option (Password:
Not asked on login), are you?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are
301 - 400 of 1345 matches
Mail list logo
