Software Center fails on every package on 11.04 until tzdata is updated
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tzdata (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: tzdata
Cannot install/upgrade anything on a fresh install of 11.04 made from the install .iso last night using Software Center. I get errors similar to the log shown at the end of this message trying to install or update any package. Tried sudo apt-get update from the shell with no change. Then I tried to update tzdata:
$ sudo apt-get install tzdata
Reading package lists... Done
Building dependency tree
Reading state information... Done
tzdata is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 60 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up tzdata (2011g-
Current default time zone: 'America/
Local time is now: Thu May 5 09:52:08 PDT 2011.
Universal Time is now: Thu May 5 16:52:08 UTC 2011.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
Since apt-get says tzdata was not updated, it is rather strange that after this, other packages would install!
Perhaps there is a bug setting the local time zone in the install gui and this is merely a configuration issue.
- Eric
installArchives() failed:
Extracting templates from packages: 40%
Extracting templates from packages: 80%
Extracting templates from packages: 100%
Extracting templates from packages: 40%
Extracting templates from packages: 80%
Extracting templates from packages: 100%
Extracting templates from packages: 40%
Extracting templates from packages: 80%
Extracting templates from packages: 100%
Setting up tzdata (2011g-
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $ret in string eq at /usr/share/
dpkg: error processing tzdata (--configure):
subprocess installed post-installation script returned error exit status 128
Errors were encountered while processing:
tzdata
Setting up tzdata (2011g-
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $ret in string eq at /usr/share/
dpkg: error processing tzdata (--configure):
subprocess installed post-installation script returned error exit status 128
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: tzdata 2011g-0ubuntu0.
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Thu May 5 09:59:07 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitec
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: tzdata
UpgradeStatus: No upgrade log present (probably fresh install)
| Eric Weitzman (eweitzman) wrote | #1 |
| Robert Roth (evfool) wrote | #2 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #442941, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.