I've just hit the same bug on Feisty Herd 5 with todays set of upgrades (6/3/2007). Is there any other information I can supply to help get this fixed?
I'm running Kubuntu Feisty Herd5. I tried running the updates by clicking on the adept notifier icon and through the main adept manager with identical results. I get the same debconf problem described here. A dialogue saying Incorrect nice value that won't accept any input from me.
I tried running sudo dpkg --configure -a and sudo dpkg-reconfigure debconf. I didn't change any settings in debconf because post 9 of the above forum thread said use 'dialog' but that didn't work. I didn't see the suggestion in this thread to set it as 'kde' until after I found an alternative work around.
Which was to run 'sudo apt-get upgrade' from the commandline. This worked perfectly. Can I supply anything else that would be useful? If some one can tell me where adept/dpkg keeps it's log files I can attach those if they're any use.
I have to say I don't really understand why running from commandline works while the GUI doesn't if the bug is in X rather than adept. But then that's just me.
I've just hit the same bug on Feisty Herd 5 with todays set of upgrades (6/3/2007). Is there any other information I can supply to help get this fixed?
I'm running Kubuntu Feisty Herd5. I tried running the updates by clicking on the adept notifier icon and through the main adept manager with identical results. I get the same debconf problem described here. A dialogue saying Incorrect nice value that won't accept any input from me.
If I hit show details in adept I have the same output as described in post 6 of this thread http:// ubuntuforums. org/showthread. php?p=1856049. even referring to the same Qt::VBoxLayout element
I tried running sudo dpkg --configure -a and sudo dpkg-reconfigure debconf. I didn't change any settings in debconf because post 9 of the above forum thread said use 'dialog' but that didn't work. I didn't see the suggestion in this thread to set it as 'kde' until after I found an alternative work around.
Which was to run 'sudo apt-get upgrade' from the commandline. This worked perfectly. Can I supply anything else that would be useful? If some one can tell me where adept/dpkg keeps it's log files I can attach those if they're any use.
I have to say I don't really understand why running from commandline works while the GUI doesn't if the bug is in X rather than adept. But then that's just me.