OK, thanks! Could you get more debugging information by following instructions
for users-admin at:
https://wiki.ubuntu.com/DebuggingGnomeSystemTools
No issue with the delays, I'm not in a hurry... ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So your system isn't broken, it's just that adduser doesn't interact
well with automount. I'm not sure why this doesn't work (i.e. why /home
isn't mounted when adduser tries to access it), nor if it should work.
But that's not a bug in users-admin. You could report a bug against
adduser in Debian
Thanks! The interesting part is:
file_run_full_failed::Command [/usr/sbin/adduser --gecos --disabled-password
bugta] failed.
Since the user wasn't created, everything else fails.
What do you get when you run:
sudo /usr/sbin/adduser --gecos --disabled-password bugta
in a terminal? You'll get
The problem isn't that I fear people won't do the work, as I know
packaging will happen anyway. It's just that the way Ubuntu devs
consider patching is plain wrong: there's generally no hurry pushing a
fix to the development release, so downstream patching only generates
useless work. I wish
Thanks for the debugging and for the patch, but I don't think it fixes
the root cause. tzmap-point_hover should already contain the point that
was retrieved using e_map_get_closest_point() when the pointer moved. So
if tzmap-point_hover isn't valid, we have to find out why. The
questions I asked
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/699664
Title:
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 683972 ***
https://bugs.launchpad.net/bugs/683972
** This bug is no longer a duplicate of bug 699664
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
** This bug has been marked a duplicate of bug 683972
nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 683972 ***
https://bugs.launchpad.net/bugs/683972
** This bug is no longer a duplicate of bug 699664
nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
** This bug has been marked a duplicate of bug 683972
nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 683972 ***
https://bugs.launchpad.net/bugs/683972
** This bug has been marked a duplicate of bug 683972
nautilus crashed with SIGSEGV in g_closure_invoke() ejecting drives
* You can subscribe to bug 683972 by following this link:
Thanks Romano, it allowed us to discover those forgotten reports! I've
made the other bug public.
These traces are very confusing, since they are all very similar to the
original bug 630884. I'm going to report this upstream, and see what
they say...
--
You received this bug notification
Thanks for your report. I see you're using the system-tools-backends
2.9.4-0ubuntu1, while the most recent version is 2.9.4-0ubuntu1.1, which
fixes many issues. Could you enable the lucid-proposed repository, run
the updates manager, and retry? See
https://wiki.ubuntu.com/Testing/EnableProposed
Upstream said we should also backport patch from
http://git.gnome.org/browse/nautilus/commit/?h=gnome-2-32id=c3b54e662b52ca15d1dcbe68386b8fa82b12adc5
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Triaged
** Bug watch added: GNOME Bug Tracker #627901
If this is reported to work, it might be wise to directly upload
nautilus 2.32.2.1 to maverick-updates, because it includes this fix
among others.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683972
The version I'm suggesting you to use is actually much more stable than the one
you're currently using... ;-) You can install it without updating any other
packages by getting it from
https://launchpad.net/ubuntu/+archive/primary/+files/system-tools-backends_2.9.4-0ubuntu1.1_i386.deb
(for
These groups are obsolete (or mostly), so I'm not sure what would be
best here. Since they still exist, I think it makes sense to add admins
to them, but we could also stop doing this in users-admin. How do
Ubiquity devs fell about that?
--
You received this bug notification because you are a
Romano: see https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport
about how to get a trace.
The log is interesting, it may indicate that Nautilus tries to get some
information from ConsoleKit, which fails. Then, maybe it follows a code
path that hasn't been really tested because it doesn't
And only when clicking on that point? Here I'm not able to reproduce the
crash...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697974
Title:
time-admin crashed with SIGSEGV in
This bug is weird because we seem to be passing NULL as location point.
This can only happen if no point was highlighted when you clicked; the
pointer must get out of the map for the point to be set to NULL. Do
different effects happen if e.g. you hover a different point before
clicking on
Thanks for the report, but I/O errors generally come from failing hard
disk drives, and not from a bug in a package. Thus, I'm closing this
report. I advise you to make a backup of your files in case you disk is
dying... ;-)
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Invalid
*** This bug is a duplicate of bug 685215 ***
https://bugs.launchpad.net/bugs/685215
** This bug has been marked a duplicate of bug 685215
users-admin hangs immediately when run as root
* You can subscribe to bug 685215 by following this link:
*** This bug is a duplicate of bug 685215 ***
https://bugs.launchpad.net/bugs/685215
The warning comes from a minor bug where we try to unreference the user
face icon even if there is none. It has no real incidence and is fixed
upstream.
--
You received this bug notification because you are
ubby: so same questions as in my comment #5...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/647371
Title:
time-admin crashed with SIGSEGV in e_map_point_get_location()
--
ubuntu-bugs mailing
Le mercredi 05 janvier 2011 à 07:49 +, gpk a écrit :
Essentially, the trade-off is a minor convenience 99.999% of the time,
versus a modest (or major) disaster 0.001% of the time.
That's also exactly how I'd describe the idea of allowing all users to set
timezone without authentication on
This button is going to be reworked soon anyway. This problem is known
upstream, I think there's a bug open about that.
** Package changed: gnome-system-tools (Ubuntu) = policykit-1-gnome
(Ubuntu)
** Changed in: policykit-1-gnome (Ubuntu)
Importance: Undecided = Low
** Changed in:
Paul: they aren't at all. In the former, the auth dialog doesn't appear;
in the latter, everything works, it's just that the button is
unintuitive. Here, it's the dialog that hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Le mercredi 05 janvier 2011 à 20:28 +, gpk a écrit :
No thanks. People love to add features. You can't stop someone who
has a pet idea that they haven't
thought through very carefully.They just produce self-justifying
reasons and don't listen.
That's an idea that came from
Le mardi 04 janvier 2011 à 15:51 +, gpk a écrit :
Actually, on consideration, I don't think that automatic detection of
the timezone
is a viable solution.It suffers from all kinds of potential problems
like
What does it do if it's connected to a VPN?. If I connect via VPN
to
Le dimanche 02 janvier 2011 à 22:58 +, RnSC a écrit :
Following up, new system. Gave up on getting 10.04 video to work on my
system (another story), switched to 10.10.
Created a user named bugta, user 1001, group 1001.
Tried to use System / Administration / Users and Groups to change
*** This bug is a duplicate of bug 574046 ***
https://bugs.launchpad.net/bugs/574046
Don't bother providing this information, this bug is already known and
has a fix in the lucid-proposed repository, which should be soon
uploaded to lucid-updates.
** This bug has been marked a duplicate of
Everybody shouldn't be allowed to set the system timezone by default, as
it affects all users on the system. If you don't have administrator
rights on your laptop, you can ask the administrator to grant you the
rights for the org.gnome.clock.mechanism.settimezone PolicyKit action,
but this
We can't change PolicyKit permissions depending on whether the system is
a laptop or not. So we'd have to make the change for all systems, which
is not necessarily what people expect. And even laptops can be used e.g.
in kiosks or schools, where you don't want people to play with system
settings.
Users will surely know what UTC is, but they'll have to be pretty smart
to guess without further information all the implications using UTC on
the hardware clock has. As I said, the installer should just disable UTC
in hardware clock if Windows is already installed. If we provide an
option for
Why do you think it is not a tzdata bug? time-admin merely shows
timezones as reported by /usr/share/zoneinfo/zone.tab, which is shipped
by tzdata, so the real bug must be there.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Triaged
** Changed in: tzdata (Ubuntu)
Kamus: are you sure you checked in time-admin, and not in gnome-panel? I
still don't see Brasilia in time-admin...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458331
Title:
time-admin doesn't
** Bug watch added: GNOME Bug Tracker #638375
https://bugzilla.gnome.org/show_bug.cgi?id=638375
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=638375
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/543042
Title:
pressing CANCEL in policykit super user mount dialog shows silly
That's because unsound's package doesn't use a version name that is
superior to Maverick's. It should be 2.26.0-0ubuntu1+bigendian, or
something like that. As a general rule, using the very same version as
an existing package is not a good idea.
--
You received this bug notification because you
Instead of fixing your test package, your time would be better spent in
generating a debdiff from it, so that developers can just upload the fix
to Maverick. See https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ah, sorry. It was the HP backend: I experienced this behavior with a
Laserjet 1100 and a Photosmart A612, which presumably didn't fail
because of the same kind of problem. But of course the error was more
severe than lack of paper: with the latter device, a page wasn't printed
correctly.
**
Thanks for the report. Can you tell me exactly what settings you
changed? I suspect you changed the home directory and something went
wrong in that process. Are you able to reproduce the problem? Else,
there's no much I can do, sadly...
** Changed in: gnome-system-tools (Ubuntu)
Importance:
SRU request: makes several apps unusable for PPC users, among which
Evince, Empathy and users-admin. Patches are not intrusive, are
available from upstream GLib 2.26.1, and can also be applied to
Maverick's 2.26.0. Users have tested these patches and they work.
--
You received this bug
*** This bug is a duplicate of bug 433851 ***
https://bugs.launchpad.net/bugs/433851
** This bug has been marked a duplicate of bug 433851
Authentication dialog doesn't get focus
* You can subscribe to bug 433851 by following this link:
*** This bug is a duplicate of bug 685655 ***
https://bugs.launchpad.net/bugs/685655
** This bug is no longer a duplicate of bug 433851
Authentication dialog doesn't get focus
** This bug has been marked a duplicate of bug 685655
PolicyKit authentication error: Only trusted callers
Public bug reported:
Binary package hint: cups
When printing fails for some reason (backend failed message), printer
is paused, and won't resume automatically, even after a reboot. This is
silly because there's no notice about that in the print dialog nor in
the print queue: you have to go to
This bug is *not* about the backend failure I'm getting. It's merely
about the fact that a backend failure makes the printer go to pause
instead of just aborting the current task. So the precise error that
happens in my case doesn't matter, and it actually happened while I was
away (users hadn't
This was tricky, but I've committed a fix upstream in liboobs and gnome-
system-tools. It will be available with 2.91.1 soon, for Natty.
** Also affects: gst
Importance: Undecided
Status: New
** Changed in: gst
Status: New = Fix Released
--
You received this bug notification
*** This bug is a duplicate of bug 685655 ***
https://bugs.launchpad.net/bugs/685655
** This bug has been marked a duplicate of bug 685655
PolicyKit authentication error: Only trusted callers (e.g. uid 0) can use
CheckAuthorization() and pass details
* You can subscribe to bug 685655 by
** Changed in: policykit-gnome (Ubuntu)
Importance: Medium = High
** Package changed: policykit-gnome (Ubuntu) = policykit-1-gnome
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685655
Could you run
G_DBUS_DEBUG=message time-admin
then try to unlock the dialog, and post the output here? Thanks in advance!
Upstream author says polkit-gtk doesn't pass details to polkitd, so this
bug is weird. Anyway, details are not supposed to be passed.
--
You received this bug notification
Thanks for the quick reply. It seems it's an Ubuntu patch that adds
details to match the authentication dialog with its parent window. This
is no longer allowed by polkitd. I can't find this patch in the
repositories, but it really seems it's applied, and we need to get rid
of it.
** Bug watch
usermod always fails when trying to change the home for an active user.
This is very reasonable since many files are likely to be open, so
moving/removing them will fail.
I've changed users-admin upstream to disable the home dir field and show
and explanation notice in that case. This will be
KeithG: What version exactly? Both are 2.32.0, what we need is the
-ubuntu part. It works here on Maverick. (Note you need to click the
unlock button after installing packages, which can be confusing - even
for me...)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
xlash911: are you seeing the same messages as the ones from the
description of this bug in /var/log/auth.log?
Andreas: does your problem still happen in 10.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 685655 ***
https://bugs.launchpad.net/bugs/685655
Thanks for the report. Why do you see in the title it occurs in Natty if
distro information says you're using Maverick (10.10)? This is important
to debug the problem.
Anyway, that's a duplicate of bug
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
If the patch doesn't apply, that just means it's not meant for Maverick, it
can't be linked with the kind of bug you have. Trust me, it's the right fix. If
you want to try it by yourself, you can edit
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
Hm, I hadn't read your two latter replies... Yes, the real question (see
duplicate report) is why remote sessions are considered as inactive. I
don't really understand whether they should be reported as
Don't worry for the delays... some bugs are opened for years, often with
a higher priority! As regards the active/inactive issue, that would
likely be a bug in ConsoleKit.
users-admin is not going away today nor in the next year, else I
wouldn't even reply to bug reports. It's just that I don't
*** This bug is a duplicate of bug 542183 ***
https://bugs.launchpad.net/bugs/542183
Yeah, that's a known bug that's going to be fixed soon in Lucid.
** This bug has been marked a duplicate of bug 542183
[users-admin] Changing UID doesn't work
* You can subscribe to bug 542183 by
Thanks. So everything works but the lock buttton, which means it's a bug
in polkit-gnome. The good news is, I'm going to stop using it in the
gnome-system-tools before the next release since it's not compatible
with GTK+ 3. We still need to find out what's going wrong, though - I'll
try to get
The button was moved in 2.32, which is present in Maverick.
** Changed in: gnome-system-tools (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598912
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
This is a mix of bug 685596, which is that users-admin doesn't report
authentication errors, and bug 187585, which is about
PolicyKit/ConsoleKit not detecting that remove sessions are active
users.
To
*** This bug is a duplicate of bug 221363 ***
https://bugs.launchpad.net/bugs/221363
Ah, and what I said is actually exactly bug 221363, which I'm going to
fix now, so marking as duplicate.
** This bug has been marked a duplicate of bug 221363
Policy Kit Unlock Buttons Greyed Out when
** Also affects: system-tools-backends
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/221363
Title:
Policy Kit Unlock Buttons Greyed Out when using NX /
I've eventually pushed the allow_any fix to the system-tools-backends
upstream, it should be available in 2.10.2 for Natty.
Somebody should really go over all actions from
/usr/share/polkit-1/actions/ and file a new bug task for all actions
that don't consider allow_any as a valid case without a
Thanks for the report. Please run
sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
And reproduce the problem. Then, copy/paste the output of the above command
here.
Also, what's the output of
apt-cache policy libpolkit-gobject-1-0 libpolkit-gtk-1-0
** Changed in: gnome-system-tools
Oh, and are you able for example to install software upgrades using
updates-manager? Are you able to authenticate from from
System-Administration-Network connections?
** Summary changed:
- Polickit authentication error: Only trusted callers (e.g. uid 0) can use
CheckAuthorization() and pass
I think it's been fixed some time ago indeed.
** Changed in: openoffice.org (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/66933
Title:
[upstream]
You mean there's nothing else printed than:
** (polkitd:1752): DEBUG: system-bus-name::1.56 is inquiring whether
unix-process:2283:1752924 is authorized for
org.freedesktop.systemtoolsbackends.set
** (polkitd:1752): DEBUG: user of caller is unix-user:connor
** (polkitd:1752): DEBUG: user of
Ah, sorry, I didn't know you weren't using GNOME. The gnome-settings-
daemon part is not essential at all: the idea was only to use the PID of
a process that is known to be running - you can use any program name
here.
The polkitd log contains the explanation to your problem:
** (polkitd:1592):
Thanks for the diff!
Looks good to me, except that the change log line:
- Identify users and groups by login instead of UID (LP: #533870, LP: #542183)
is wrong: Bug 533870 is a crash on amd64 too, not a login vs. UID issue.
--
You received this bug notification because you are a member of
No, I don't think it is. ;-) As long as the right number is listed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616682
Title:
Backport system-tools-backends 2.10.0 to Lucid
--
ubuntu-bugs
The gksu issue is not related at all, since users-admin doesn't use it
(else, that would mean it's running as root).
I suspect no user is shown in the list, or the current user isn't. Is it
the case? Can you test that by creating a test user using 'adduser' in a
console and check if it's enough?
Of course, it would be slightly better to fix users-admin not working as
root, rather than showing an error message, just in case some very
special distributions or users need this. But I'd accept a patch showing
a dialog too if it's well written... I don't think translators will mind
- if you
So it sounds like a PolicyKit issue. Please run
sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
start users-admin, and click on a button that doesn't work. Then please attach
the output here.
What happens if you run
export PID=`pidof gnome-settings-daemon`
pkcheck --action-id
There's an error in the log file you provided, though. Could you check
when it exactly happens (e.g. when pressing OK for the password
dialog...)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684587
But this is not a bug. You shouldn't run users-admin as root, as you
don't need to, and it potentially creates security issues.
** Changed in: gnome-system-tools (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You could, but I can sear you nobody will ever work on this because 1)
nobody usually works on users-admin except myself, and 2) users-admin is
going to be replaced, so we're not really fixing this kind of detail.
Feel free to provide a patch though, but filing a bug would really waste
your
You can just open the file after each time you validate a dialog by
clicking a button, and for example note somewhere what line was the last
at that point, and then mark this in the file by introducing comments.
You may also run the commands in a terminal without the stb-
users.log part, so that
Thanks for the report. Could you follow the procedure For users [users-
admin] at https://wiki.ubuntu.com/DebuggingGnomeSystemTools and attach
the resulting files here? Also, I'd need you to run 'sudo killall
polkitd; sudo /usr/lib/policykit-1/polkitd' before you carry out the
other actions, and
OK, let's say bug 683972 is the place where we track the crash that
still occurs with nautilus 1:2.32.0-0ubuntu1.1. What feels weird is that
the trace is very very similar, but let's see...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
What you should have said in the description is that this crash is very
close to bug 630884, which is reported to be fixed with nautilus
1:2.32.0-0ubuntu1.1.
** This bug has been marked a duplicate of bug 630884
nautilus crashed with SIGSEGV in g_closure_invoke()
* You can subscribe to bug
Public bug reported:
Binary package hint: xserver-xorg-video-intel
[Sorry for the silly title. ;-)]
The Intel driver in Maverick (2.12.0) is almost unusable for i915
because of redraw issues. Damaged areas don't seem to get repainted as
needed, which mostly happens with scrolling areas (web
Thanks Chris! But we really don't need to backport 2.10.1, 2.10.0 will
be enough. 2.10.1 only brings in a few improvements that are used by the
gnome-system-tools 2.32, which are not in Lucid. This removes most of
the changes (in terms of lines of code), which makes the SRU even safer.
--
Seriously, I've moved on to other things since Lucid has been released -
glad to know SRUs are considered even when they are that old, though!
;-)
The only translation change between Lucid and Maverick package is in one
file and for two strings, so definitely not something to care about. If
Richard: It's fixed in Maverick, but still present in Lucid. See
https://wiki.ubuntu.com/Bugs, and especially
https://wiki.ubuntu.com/Bugs/Status.
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 533870 ***
https://bugs.launchpad.net/bugs/533870
Yeah, that's known but we need to backport fixes to Lucid.
** This bug has been marked a duplicate of bug 533870
Crash in SelfConfig on amd64
* You can subscribe to bug 533870 by following this link:
Thanks for the report. This is indeed a synchronisation issue between
users-admin and adduser, the tool which is responsible for actually
creating users. I've filed a bug in Debian so they make adduser allow
dots in usernames.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided =
I've committed both changes (stratum 1 and unreachable servers)
upstream. Thanks for the help! Of course, the proper fix would be
creating a pool, but better fix this in the short term.
Commits are 0fef206 and 8e01e05.
** Also affects: gst
Importance: Undecided
Status: New
** Changed
*** This bug is a duplicate of bug 677929 ***
https://bugs.launchpad.net/bugs/677929
** This bug has been marked a duplicate of bug 677929
users-admin: create new user with dot/period fails
* You can subscribe to bug 677929 by following this link:
What's the exact behavior of the installer? It doesn't use the same code
at all, so that's purely a coincidence it it suffers from the same
problem.
Don't worry about the importance, though: I'm currently discussing with
an adduser developer, and the fact that I set it to Low doesn't mean it
Of course, we can pass --force-badname, but if we consider dots as
acceptable, adduser should accept them by default.
About chown, there's absolutely no need to change the tool, as long as
people that add dots to their usernames and use chown from the
commandline know what they are doing. Anyway,
I can't believe it. Can you remove these packages and reproduce the
problem? I've just done it here, and it's prompting an authentication
dialog.
Is that a new install of Maverick, or an upgraded system? Are you sure
you never played with system settings regarding authentication? Is
'sudo' asking
users-admin knows nothing about this authentication dialog, it's run by
PolicyKit-gnome. So the bug must affect all dialogs.
You should report this to upstream if you really want it to be fixed.
** Package changed: gnome-system-tools (Ubuntu) = policykit-gnome
(Ubuntu)
** Changed in:
None of the examples you cite are using PolicyKit actually. Try setting
a system connection using NetworkManager config tool for example, or
installing packages using updates-manager.
--
Authentication dialogs use plain text spoken password with screen-reader
Weird. Both use PolicyKit. What if you run
export PID=`pidof gnome-settings-daemon`
pkcheck --action-id org.debian.apt.upgrade-packages --allow-user-interaction
--process $PID
pkcheck --action-id org.freedesktop.systemtoolsbackends.set
--allow-user-interaction --process $PID
Is there a
Yeah, the latter result is more what I expected. There's a bug and a fix
for that, but nobody committed it for such a long time... Basically, you
can't use shares-admin since 10.04...
Be sure to remove /etc/init/nfs*, /etc/init.d/nfs*, /etc/init/samba and
/etc/init.d/samba if these files exist.
I can hardly imagine how the fact that you're running in VMWare should
change anything WRT authentication. More likely a config file was
edited... Or you weren't asked for authentication because you had just
provided your password for the same action a few seconds before.
Anyway, let's close this
And you can swear me the dialog from users-admin is not behaving the
same as others?! The only thing users-admin does is asking the backends
(so it doesn't even do it by itself) to ask PolicyKit1 to authenticate
by whatever means are adequate. So this amounts to pkcheck --action-id
Explain what exactly? xprop is easy, just run 'xprop' and click on the
offending dialog to get the results on the console.
--
Authentication dialogs use plain text spoken password with screen-reader
https://bugs.launchpad.net/bugs/672285
You received this bug notification because you are a
So these dialogs are indeed the same, from the same process, which is
what I expected. I really can't tell why Orca would treat them
differently... One would need to know how this works, and what may
happen in polkit-gnome-authentication-agent-1 that would change Orca's
behavior. But I can't help
201 - 300 of 1774 matches
Mail list logo
