Gutsy synaptic fail with error on remove residual conf

Thanks for reporting. Does the history in synatpic (File->History) say anything of note? Try to run 'sudo dpkg -r linux-ubuntu-modules-2.6.22-7-generic' in a terminal and paste the output.

Sorry, if you're purging, I suppose that should be 'sudo dpkg --purge linux-ubuntu-modules-2.6.22-7-generic'

The Synaptic --> File-> History
Tell me that are removed as you can look below:
---------------------------------------------------------------------------
Commit Log for Sun Jul 15 09:08:54 2007

I seguenti pacchetti sono stati completamente rimossi: (<--- italian for fully removed)
linux-image-2.6.22-7-generic

I seguenti pacchetti sono stati rimossi: (<--- italian for fully removed)
linux-restricted-modules-2.6.22-7-generic
linux-ubuntu-modules-2.6.22-7-generic
------------------------------------------------------------------------------
But i still have:
ubuntu-modules-2.6.22-7-generic
packages available to remove into synaptic.

--- Now i do as you tell me.

sudo dpkg --purge linux-ubuntu-modules-2.6.22-7-generic
[sudo] password for ubuntu:

(Lettura del database ... 117665 file e directory attualmente installati.)
Rimuovo linux-ubuntu-modules-2.6.22-7-generic ...
Elimino i file di configurazione di linux-ubuntu-modules-2.6.22-7-generic ...
FATAL: Could not open '/boot/System.map-2.6.22-7-generic': No such file or directory
update-initramfs: Generating /boot/initrd.img-2.6.22-7-generic
Cannot find /lib/modules/2.6.22-7-generic
update-initramfs: failed for /boot/initrd.img-2.6.22-7-generic
dpkg: errore processando linux-ubuntu-modules-2.6.22-7-generic (--purge):
 il sottoprocesso post-removal script ha restituito un codice di errore 1
Sono occorsi degli errori processando:
 linux-ubuntu-modules-2.6.22-7-generic

HTH

When cleaning up my Gutsy installation I encountered the same issue:
NOTE: All commands are given as root!

dpkg --purge linux-ubuntu-modules-2.6.22-7-generic
(Reading database ... 102011 files and directories currently installed.)
Removing linux-ubuntu-modules-2.6.22-7-generic ...
Purging configuration files for linux-ubuntu-modules-2.6.22-7-generic ...
FATAL: Could not open '/boot/System.map-2.6.22-7-generic': No such file or directory
update-initramfs: Generating /boot/initrd.img-2.6.22-7-generic
Cannot find /lib/modules/2.6.22-7-generic
update-initramfs: failed for /boot/initrd.img-2.6.22-7-generic
dpkg: error processing linux-ubuntu-modules-2.6.22-7-generic (--purge):
 subprocess post-removal script returned error exit status 1
Errors were encountered while processing:
 linux-ubuntu-modules-2.6.22-7-generic

Although not entirely sure of the consequences I thought I give the following a try and issued the following commands:
cp /boot/System.map-2.6.22-8-generic /boot/System.map-2.6.22-7-generic
mkdir /lib/modules/2.6.22-7-generic
cp -R /lib/modules/2.6.22-8-generic/* /lib/modules/2.6.22-7-generic/

Next I tried again with the following result:
dpkg --purge linux-ubuntu-modules-2.6.22-7-generic
(Reading database ... 102011 files and directories currently installed.)
Removing linux-ubuntu-modules-2.6.22-7-generic ...
Purging configuration files for linux-ubuntu-modules-2.6.22-7-generic ...
update-initramfs: Generating /boot/initrd.img-2.6.22-7-generic
find: /lib/firmware/2.6.22-7-generic: No such file or directory
find: /lib/firmware/2.6.22-7-generic: No such file or directory
find: /lib/firmware/2.6.22-7-generic: No such file or directory
find: /lib/firmware/2.6.22-7-generic: No such file or directory
find: /lib/firmware/2.6.22-7-generic: No such file or directory
find: /lib/firmware/2.6.22-7-generic: No such file or directory

However the end result was that linux-ubuntu-modules-2.6.22-7-generic no longer appeared as residual in Synaptic.
I am not sure if it is an official workaround, but it resolved the issue for me.

Yes your workaround resolve working for me,
thank you.

Yes your workaround resolve working for me,
thank you.

Thanks for your report. We appreciate the difficulties you are facing, but this bug has already been reported. Please review the information and solution in bug 124373. We are marking this bug as a duplicate.