natty has seen the end of its life and is no longer receiving any
updates. Marking the natty task for this ticket as "Won't Fix".
** Changed in: ubiquity (Ubuntu Natty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as "Won't Fix".
** Changed in: ubiquity (Ubuntu Maverick)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bug
** Tags added: bugpattern-written
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
status 128 - Use of uninitialized
** Branch linked: lp:ubuntu/ubiquity
** Branch linked: lp:ubuntu/natty-proposed/ubiquity
** Branch linked: lp:ubuntu/maverick-proposed/ubiquity
** Branch linked: lp:ubuntu/lucid-proposed/ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
N/A
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
status 128 - Use of uninitialized value $reply in scalar chomp a
I've written a bug pattern, which can be modified to point people to a
wiki page instead of this bug, to prevent further duplicates of this bug
report from coming in unnecessarily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
This bug was fixed in the package ubiquity - 2.2.26
---
ubiquity (2.2.26) lucid-proposed; urgency=low
* Stop ubiquity and oem-config when stopping display managers. This
should guarantee that X has exited by the time we try to start plymouth
on shutdown (LP: #628630).
* A
Adding back v-needed for maverick/natty
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2:
SRU verification for Lucid:
I have verified that the version of ubiquity 2.2.26 in -proposed fixes the
issue. I have verified that the permissions are set correctly, that a software
can be installed with software-center.
Marking as verification-done
** Tags added: verification-done-lucid
** Tag
Hello rohart, or anyone else affected,
Accepted ubiquity into maverick-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advanc
SRU team ack for the maverick-proposed upload. It has the unrelated
change of adding maverick-updates to the sources, but that seems
harmless.
For the natty-proposed upload you've got an equivalent change to the
sources, but also an update to the partman-auto version. Was that
intentional? Give
Hello rohart, or anyone else affected,
Accepted ubiquity into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Branch linked: lp:~ubuntu-installer/ubiquity/natty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
statu
@cc: indeed, the problem should solve itself after the first upgrade
that does anything with debconf - so reinstalling tzdata is one
reasonable workaround, although the problem isn't actually in tzdata
itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Branch linked: lp:~ubuntu-installer/ubiquity/maverick-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
st
This bug was fixed in the package ubiquity - 2.7.11
---
ubiquity (2.7.11) oneiric; urgency=low
[ Luke Yelavich ]
* Use at-spi2 dbus launcher to start the at-spi2 daemon
* Determine accessibility state from gsettings using the gsettings command,
to make sure privileges are dr
** Description changed:
+ Stable update justification:
+
+ Impact: Due to incorrect permissions on /var/cache/debconf/config.dat, the
first upgrade using update-manager may fail. Other package management
frontends that use aptdaemon may also fail on the first attempt.
+ Development branch: I'v
** Branch linked: lp:~ubuntu-installer/ubiquity/lucid-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
statu
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
status 128 - Use of uninitialized valu
Aha! What appears to be happening is that the installer erroneously
sets up /var/cache/debconf/config.dat with mode 0600, so it's unreadable
to the user-mode debconf frontend, which falls over and leaves the root
debconf proxy without anything to talk to; it then crashes shortly
afterwards and we'
I've finally found a reliable method that I can use to reproduce this
bug in isolation (so I might at long last be able to do something about
it!):
1) Install a Natty desktop system (and checkpoint the virtual machine at this
point)
2) Start update-manager
3) Uncheck everything except libpam0g
My report of this bug came from when I was using 11.04 Beta. This has
not occurred to me in the full release but, if it helps, the full
release is a dual-boot installation and upgraded from 10.10 whereas the
beta release was an upgrade of a WUBI install.
--
You received this bug notification beca
239 duplicate reports of this issue (not counting those not yet hunted
down and duped), and it causes package upgrade failures when it strikes;
we should really try to get a handle on this.
Colin, do you have any idea what's going on here with the passthrough
frontend?
** Changed in: debconf (Ubu
My bug having to do with the tzdata package just got redirected here, so
I thought I would throw in my two cents. The bug can be worked around
on a fresh install by entering the following into a terminal:
sudo apt-get update && sudo apt-get upgrade
Copy pasta that and you are good to go.
On a s
I just installed Ubuntu 11.04 on a blank Linux-Ubuntu virtual machine in
Oracle VirtualBox (4.0.6), and when attempting to run Software Update, I
get the following error messages:
Package operation failed
installArchives() failed: Setting up tzdata (2011g-0ubuntu0.11.04) ...
Use of uninitialized
Got the same problem (bug 605583) with a fresh install of Ubuntu 10.04 while
trying to install Eclipse IDE.
I then managed to update my system without a problem (with apt-get update &&
apt-get upgrade), and also installed Eclipse IDE without a problem on this
updated system.
Seems like this is
This happened to me too (on a clean instalation).
--
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128
- Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66
https://bugs.launchpad.net/bugs/442941
You received
just in case somebody else ends up in my same boat, running "sudo apt-
get install b43-fwcutter" from the command line works and avoids this
problem.
--
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128
- Use of uninitialized value $reply in scalar chomp at
/usr/sha
i just installed 10.04 on PowerBook G4 and the wireless driver doesn't
work out of the box (b43legacy-phy0 ERROR: Firmware file
"b43legacy/ucode4.fw" not found or load failed.).
a quick google led me to believe that installing the b43-fwcutter package might
get me up and running. trying to insta
Failed to report to debconf during first upgrade after installation of
0.04. Upgrade failed.
--
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128
- Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66
https://
** Changed in: tzdata (Ubuntu)
Importance: Undecided => Medium
** Changed in: debconf (Ubuntu)
Importance: Undecided => Medium
--
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128
- Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf
I'm adding a task for tzdata because it seems to be the most affected
package by this error.
** Also affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Changed in: tzdata (Ubuntu)
Status: New => Confirmed
--
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubunt
confirmed from duplicates.
** Changed in: debconf (Ubuntu)
Status: New => Confirmed
--
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128
- Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66
https://b
33 matches
Mail list logo
