Unfortunately this bug report is being closed because we received no
response to the last inquiry for information. However, the Intrepid
Ibex 8.10 Beta release was most recently announced -
http://www.ubuntu.com/testing/intrepid/beta . If you are able to
confirm this is still an issue with this
** Tags added: regression-release
--
Clobbered X screen state during installation
https://bugs.launchpad.net/bugs/73955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Kernel Team
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have a machine that reproduces this bug now. According to strace, X
isn't even waking up when the corruption occurs, so I doubt it's an X
bug. It looks to me as if the kernel is overwriting video memory by
mistake. The fbcon and vesafb modules are loaded, and X is using the
vesa driver.
** Also
OK, I've worked around this in console-setup; I have an idea as to how
to implement setup-console-under-usplash while still avoiding this
problem. I do think it's a kernel bug that you can't reliably set the
font on another virtual console, though - and it's particularly
irritating that vgacon
Colin Watson wrote: OK, I've worked around this in console-setup
I just installed 1.13ubuntu5 in Feisty and confirm that it installed
without incident, thanks! :-)
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
Thanks, but there is no need for further confirmations of this bug at
this point. Help from another developer to fix it would be wonderful,
though.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It still happens on feisty herd 2...
I'm using ati radeon xpress 200
on a compaq presario m2000
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Also happening on Knot 1 Feisty Fawn. I'm not able to install it.
Using nVidia GeForce 2 MX200.
I can't install Feisty on my computer. I get part of the brown
background repeated over my screen after clicking through Ubiquity
keyboard selector.
--
Clobbered X screen state during installation
Feisty is very experimental but if you still want to install it when
it goes crazy the following;
Press Ctrl+Alt+F2 then press Ctrl+Alt+F7
It will straighten the display so you can continue.
At 07:12 AM 1/8/2007, you wrote:
Also happening on Knot 1 Feisty Fawn. I'm not able to install it.
I've just saw this interesting effect during dist-upgrade in feisty. And I can
have it again using
$ /etc/init.d/console-setup restart
My video card is S3 SuperSavage on IBM T23. Sometimes it show me
something strange after suspend and/or hibernate, but I don't remember
using those since last
I wasn't using framebuffer or (boot)splash. Now I added vga= to kernel
boot options and console-setup restart does nothing interesting.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just installed the latest batch of updates in Feisty and I got bit by
this bug :) To confirm the package that was causing the problems, I
copied all the DEBs that had just installed in the latest round from
/var/cache/apt/archives and manually reinstalled them until I got to the
one that broke
Reproduce confirmed on nc8230
(https://wiki.ubuntu.com/LaptopTestingTeam/HPNC8230)
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
OK, so that suggests it's the KDFONTOP ioctl.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I did a quick survey on #ubuntu-devel, and had one failure report
(reproducing this bug) from fglrx and one success report from i810.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Could you please try the following to see if it exhibits the same
problem? You may want to run 'sudo setupcon' afterwards to ensure that
the console is in a sane state again.
zcat /etc/console-setup/Lat15-VGA16.psf.gz Lat15-VGA16.psf
psfstriptable Lat15-VGA16.psf Lat15-VGA16-stripped.psf
Colin, that triggers the bug as well.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm using the proprietary nvidia driver :-(.
Attached a strace of the consolechars command.
** Attachment added: strace consolechars
http://librarian.launchpad.net/5231942/strace.consolechars
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs
On Fri, Dec 01, 2006 at 06:42:36AM -, Colin Watson wrote:
consolechars doesn't cause this breakage for me (ati X driver, on a
Radeon 9600). Matt, Johan, what X drivers are you using?
nv
--
- mdz
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
console-setup.postinst contains setupcon --force --save;
--force do not check whether we are on the console
That seems to be the culprit.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Scratch that, also the edgy version uses --force.
The breakage seems to happen when setupcon runs 'consolechars -v
--tty=/dev/tty1 -f /etc/console-setup/Lat15-VGA16.psf.gz'.
I built and installed the edgy version of console-tools; the bug was
triggered by it, too.
--
Clobbered X screen state
** Tags added: feisty-regression
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Not checking whether we're on the console is deliberate; this is needed
for setup-console-under-usplash. Evidently console-tools isn't quite as
ready for it as I'd hoped, though.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
consolechars doesn't cause this breakage for me (ati X driver, on a
Radeon 9600). Matt, Johan, what X drivers are you using?
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
An strace of that consolechars command, or failing that all of setupcon,
on a failing system would be appreciated.
--
Clobbered X screen state during installation
https://launchpad.net/bugs/73955
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
27 matches
Mail list logo
