This is also bug #87641 (with 37 duplicates) for which Debian have fixed
debconf, see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413509
Not sure how to handle this (two different bug numbers for same problem
with many duplicates and different fix).
--
x11-common loop asking 'Please enter
fixed in the latest upload, thanks for all the help!
xorg (1:7.2-0ubuntu9) feisty; urgency=low
[ Colin Watson ]
* debian/xserver-xorg.config.in: Improve expr return code handling in
validate_nice_value (the right way this time); don't use run function
when we need to check db_input's
On Fri, March 23, 2007 06:56, Colin Watson wrote:
> Could somebody get a log of this failure with DEBCONF_DEBUG=developer
> set in the environment? It would help to see what's actually happening.
I will try to run adept_updater in the following manner:
sudo script -c ~/tmp/DebugAdept.sh
where "~
Colin, on some duplicates, some get segfaults after getting:
DESTROY created new reference to dead object ' Qt::VBoxLayout', <> line 2176
during global destruction
... followed by some /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104,
line 9.
Now, that's the third times I rewrite this commen
** Attachment added: "updated patch"
http://librarian.launchpad.net/6902452/xorg-68267.diff
--
x11-common loop asking 'Please enter an integer between -20 and 19.' at debconf
medium or higher
https://launchpad.net/bugs/68267
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I think that the -eq 1 change that Timo made to the expr call was in
fact correct. As far as I can tell from the subsequent bug reports, it
wasn't that it broke it completely, it merely had no obvious effect due
to the more serious bug in db_input return code handling.
--
x11-common loop asking '
Ah, Timo, the reason why it broke is that you used '-ne 1' rather than
'-eq 1' by mistake! The patch I'll attach in a moment incorporates my
previous fix and does this properly.
--
x11-common loop asking 'Please enter an integer between -20 and 19.' at debconf
medium or higher
https://launchpad.
** Attachment added: "remove pointless run call"
http://librarian.launchpad.net/6901818/xorg-68267.diff
--
x11-common loop asking 'Please enter an integer between -20 and 19.' at debconf
medium or higher
https://launchpad.net/bugs/68267
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I don't see an obvious need to fiddle with the expr calls here. They may
be ugly, but I don't think they're what's failing.
Paul Dufresne's idea in
https://launchpad.net/ubuntu/+source/xorg/+bug/68267/comments/27 looks
correct, but I think his suggested fix is wrong; $_retval is an internal
variab
Could somebody get a log of this failure with DEBCONF_DEBUG=developer
set in the environment? It would help to see what's actually happening.
--
x11-common loop asking 'Please enter an integer between -20 and 19.' at debconf
medium or higher
https://launchpad.net/bugs/68267
--
ubuntu-bugs mail
:Kubuntu herd 5
I have this problem, the 'debconf nice' error occurred for other
packages, but it was x11-common loop that halted adept update.
I installed via cli (sudo apt-get upgrade) as per
http://ubuntuforums.org/showthread.php?t=285853&page=2 and it seemed to
work.
--
x11-common loop aski
Paul Dufresne wrote:
> So as I understand: "set +e" make sure that it will NOT exit
> script because of the non-zero expr results. Which seems ok.
Aha - you're right. I didn't notice that it was ,
not the reverse order. Thanks for pointing that out.
--
x11-common loop asking 'Please enter an i
was said earlier:
1) That "set +e ... set -e" seems -really- bogus.
That forces exit on non-zero exit status from
simple commands, and this script intentionally
invokes some simple commands that might exit
non-zero, such as the expr line on the very next
line aft
My earlier patch (in this thread), replaces the contents of
validate_nice_value() function with a single line:
test "$1" -ge -20 -a "$1" -le 19 2> /dev/null
The patch I submitted was against the broken version (7.2.0ubuntu4 with
"$? -ne 1"), but the same idea works with the not-so-broken one.
BT
I would really appreciate if someone could test a real package with some
of the proposals here, and upgrade it with adept/apt/.. Yes, it's not
easy, but we've been bitten by this once and I don't feel like testing
with main again :)
--
x11-common loop asking 'Please enter an integer between -20 a
A couple of things in the x11-common.config
script validate_nice_value() don't look right to me:
1) That "set +e ... set -e" seems -really- bogus.
That forces exit on non-zero exit status from
simple commands, and this script intentionally
invokes some simple commands that might
making previous comment in a patch
Just this seems enough to make both dpkg-reconfigure -plow and -pmedium to work
(validate correctly nice value, don't have tested if nice value is really
applied to the server).
still some warning at medium level:
Use of uninitialized value in join or string
ah, run is define in the config file.
so, we can keep:
run db_input low x11-common/xwrapper/nice_value
but change:
if [ $? -eq 30 ]; then
for:
if [ $_retval -eq 30 ]; then
--
x11-common loop asking 'Please enter an integer between -20 and 19.' at debconf
medium or higher
https://launchpad.net/bu
the bug seems to be cause by:
---
while :; do
run db_input low x11-common/xwrapper/nice_value
# is the question going to be asked?
if [ $? -eq 30 ]; then
break # no; bail out of validation loop
fi
---
$? is 0, the result of run rather than the result of db_input
removing run seems to gi
** Summary changed:
- x11-common have an important debconf bug
+ x11-common loop asking 'Please enter an integer between -20 and 19.' at
debconf medium or higher
** Description changed:
Binary package hint: x11-common
- When dpkg is installing x11-common, on Edgy, when debconf is using kde
20 matches
Mail list logo