Kevin, i'm glad you managed to resolve things. I will close this bug report.
In the end, it's still unclear to me: what were the starting conditions that
caused this problem? Was something wrong with your configuration, or is there
actually a bug in the upgrade process?
** Changed in:
Starting conditions:
1) Bad syntax in /etc/default/locale was en_US needed to be LANG=en_US
2) Bad file in /var/lib/locales/supported.d, which is scanned for shell
scripts and filtered only lightly. My bad file was treated as a script and
failed miserably. It was actually an artifact of
I think the error message to look at is:
dpkg: error processing locales (--configure):
subprocess post-installation script returned error exit status 1
The post-installation script is:
/var/lib/dpkg/info/locales.postinst
Try renaming it to something else, so that dpkg doesn't find it, and try
I found it. It's a tiny script that just calls locale-gen. I commented that
out and did the
aptitude reinstall locales
which now looked clean. Of course it left behind a bunch of unconfigured
packages.
Moreover, when I manually ran locale-gen, it failed again in the same way. I
even
The immediate problem turned out to be a stray file in
/var/lib/locales/supported.d, namely a typescript file that got there from
one of my attempts to debug something else. It also turns
out that locale-gen looks at all files in that directory, and its filters don't
catch that a typescript is
Some more poking around revealed that I needed /etc/default/locale to contain
LANG=en_US, not just the locale name, because it's sourced as a shell script.
With this change, X now starts on bootup (bad syntax in /etc/default/locale was
crashing /etc/init.d/gdm, among other things).
Feel free to
Kevin, please try running the 'sudo dpkg-reconfigure xserver-xorg' I
mentioned earlier, it might fix your X.
As for your other problems, it seems the root of them is the 'locales'
package not being configured...
Maybe you could try running 'sudo aptitude reinstall locales'?
--
dapper - hardy
'sudo dpkg-reconfigure xserver-xorg' ran fine, but accomplished only
reducing my resolution to 800x600. The xorg.conf file was nice and
clean however, and I just put the modelines in that one. I still have
to start Xorg manually with 'gdm'.
Looking at the reboot more carefully, however, I have
** Attachment added: Results of lsb_release
http://launchpadlibrarian.net/15562748/lsb_release
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please add the log files from '/var/log/dist-upgrade/'
to this bug report as attachments? Thanks in advance.
** Changed in: update-manager (Ubuntu)
Sourcepackagename: None = update-manager
** Tags added:
I assume you have already tried 'sudo dpkg --configure -a' and 'sudo
dpkg-reconfigure xserver-xorg'?
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: update-manager (Ubuntu)
Status: New = Incomplete
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: term.log
http://launchpadlibrarian.net/15564636/term.log
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: main_pre_req.log
http://launchpadlibrarian.net/15564630/main_pre_req.log
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: main.log
http://launchpadlibrarian.net/15564626/main.log
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: apt-term.log
http://launchpadlibrarian.net/15564601/apt-term.log
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: apt.log
http://launchpadlibrarian.net/15564570/apt.log
--
dapper - hardy upgrade breaks system
https://bugs.launchpad.net/bugs/242703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Okay, after reading localedef --help and localedef --usage, I'm still
pretty much flying blind.
I could, of course, just make a stab at it: for instance localedef en_US
seems plausible.
But no more than plausible, and I'm worried about making matters worse.
++ kevin
--
dapper - hardy upgrade
I did not even know about those things. I will try them.
In the meantime, I have solved the X part of this. Bumbling around
comparing with the Gentoo system that shares this monitor via KVM
switch, I narrowed the hsync and vsync ranges until something worked. I
now have X, so it was unrelated
I wrote too quickly about Xorg being repaired. It is not quite. When I
reboot, it fails, and I have to log in a root console and start X with
gdm(1). Then it comes up okay, modulo an unexpected dialog or two. I
can't quite imagine what's different between the normal bootup and gdm
run by root.
20 matches
Mail list logo
