gnome-keybinding-properties & theme-manager fail to run after a dist-upgrade from hoary to breezy

Could you try to login with a new user and see if that works?

Do they crash? Could you get a backtrace using gdb?

Daniel: yes, works fine with a new user account....

 Sebastien: I'm not a big user of gdb, but after the program hangs afer doing a
"run -X" I control-c and the bt is :

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGINT, Interrupt.
[Switching to Thread 46912580174496 (LWP 21955)]
0x00002aaaaabcd0d2 in __write_nocancel () from /lib/libpthread.so.0
(gdb) bt
#0 0x00002aaaaabcd0d2 in __write_nocancel () from /lib/libpthread.so.0
#1 0x00002aaab0267f00 in ?? () from /usr/lib/libfam.so.0
#2 0x00002aaab0268084 in ?? () from /usr/lib/libfam.so.0
#3 0x00002aaab0268bc5 in FAMMonitorDirectory () from /usr/lib/libfam.so.0
#4 0x00002aaab01624c3 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#5 0x00002aaaaba2cdff in _gnome_vfs_monitor_do_add () from
/usr/lib/libgnomevfs-2.so.0
#6 0x00002aaaaba2e5b0 in gnome_vfs_monitor_add () from /usr/lib/libgnomevfs-2.so.0
#7 0x000000000040b342 in gnome_theme_info_new ()
#8 0x000000000040ba30 in gnome_theme_info_new ()
#9 0x000000000040bf63 in gnome_theme_init ()
#10 0x0000000000407b2d in main ()

The backtrace is weird. Is your issue a hang or a crash (your description lacks
details). Do you have some custom theme installed ot ~/.themes or ~/.icons?

Sebastien: Definetely a hang. I don't have any special/custom theme stuff.
I've tried removing the ~/.theme & ~/.icons directories just in case. Same
problem persists.

After doing a bit of digging and reading :

http://lists.debian.org/debian-gtk-gnome/2003/01/msg00597.html

I've tried stopping inetd. Still doesn't come up, but a strace of
gnome-keybinding-preferences now hangs on :

setresgid(-1, 1000, -1) = 0
lstat("/usr/share/themes", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
rt_sigaction(SIGUSR2, {0x2aaab026ab50, [USR2], SA_RESTORER|SA_RESTART,
0x2aaaac432190}, {SIG_DFL}, 8) = 0
getuid() = 1000
open("/etc/passwd", O_RDONLY) = 13
fcntl(13, F_GETFD) = 0
fcntl(13, F_SETFD, FD_CLOEXEC) = 0
lseek(13, 0, SEEK_CUR) = 0
fstat(13, {st_mode=S_IFREG|0644, st_size=1463, ...}) = 0
mmap(NULL, 1463, PROT_READ, MAP_SHARED, 13, 0) = 0x2aaab036d000
lseek(13, 1463, SEEK_SET) = 1463
munmap(0x2aaab036d000, 1463) = 0
close(13) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 13
connect(13, {sa_family=AF_FILE, path=@/tmp/fam-billy-}, 110

Which makes me think that fam is involved as suggested by the debian posting.
Why the keybindings tool should be talking to fam I'm not sure... :-/

Having posted that - I restarted inetd and now the keybindings process is still
hanging on the fam socket... :-/

Great :-/

Resolved! I killed the /usr/lib/gamin/gam_server process and let it restart...
now all seems well.

if gam server hangs again, could you post a backtrace of it?

Will do :-) It's been fine since so looks like it was a one-off post
dist-upgrade issue.

Do you still have that issue?

No - it's cleared up. I'd put it down to a quirk of the dist-upgrade...

I'm closing the bug as WORKSFORME so, feel free to reopen if you can reproduce
it again