Comment 16 for bug 533870

Revision history for this message
Asif Youssuff (yoasif) wrote : Re: Changing the long name in users-admin to the same name results in an error

Here is the updated debug log.

asif@asif-laptop:~$ sudo killall system-tools-backends
system-tools-backends: no process found
asif@asif-laptop:~$ sudo gdb /usr/sbin/system-tools-backends
GNU gdb (GDB) 7.0.1-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/system-tools-backends...Reading symbols from /usr/lib/debug/usr/sbin/system-tools-backends...done.
(no debugging symbols found)...done.
(gdb) break dispatcher.c:547
Breakpoint 1 at 0x40431f: file dispatcher.c, line 547.
(gdb) run
Starting program: /usr/sbin/system-tools-backends
[Thread debugging using libthread_db enabled]

Breakpoint 1, dispatch_self_config (connection=<value optimized out>,
    message=0x61c190, data=<value optimized out>) at dispatcher.c:547
547 dispatcher.c: No such file or directory.
 in dispatcher.c
(gdb) continue
Continuing.

Breakpoint 1, dispatch_self_config (connection=<value optimized out>,
    message=0x618250, data=<value optimized out>) at dispatcher.c:547
547 in dispatcher.c
(gdb) print (message_uid == uid)
$1 = 1
(gdb) print message_uid
$2 = <value optimized out>
(gdb) print uid
$3 = <value optimized out>
(gdb)

Now, without closing users-admin (this is what I mean by the second time -- doing the same steps during the same session is still reproducible, it is only if I try it again without closing users-admin that I don't see an error), I get a new dialog after I click on change:

You are not allowed to modify the system configuration.

An error occurred while checking for authorizations: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
You may report this as a bug.