On 06/10/2012 01:21 PM, Mateusz Loskot wrote:
On 10 June 2012 20:35, Sébastien le Preste de Vauban
<ulpianosonsi@xxxxxxxxx> wrote:
El 10/06/12 14:11, Mateusz Loskot escribió:
On 10 June 2012 19:03, Javier Vasquez <j.e.vasquez.v@xxxxxxxxx> wrote:
On Sun, Jun 10, 2012 at 11:42 AM, Mateusz Loskot <mateusz@xxxxxxxxxx>
wrote:
I have been observing strange issues when I switch between X and TTY.
[...]
I started noticing this same thing since last year (though don't
remember when exactly). Never asked cause the work around is simple,
the TTY from which startx was run is considered "dead" to me, I just
don't use it once in X.
Yes, you are right it's not a very disturbing issue.
I was just curious if it is known problem and perhaps there is a solution.
I have a similar problem:
https://bugs.freedesktop.org/show_bug.cgi?id=47277
Nice one, I'm going to subscribe to this issue. Thanks!
Best regards,
I think I have a similar problem, I am on a 64bit laptop with OpenBox
and Slim. What happens for me is if I change TTYs or even try and
shutdown the screen turns red some times other times its just a black
screen, but during both the computer is locked up. No output in logs and
does cause a kernel panic. They way I have been able to work around it
after an update gets me back to seeing red again is running this little
script. Maybe it will help you figure a work around for yours, but
probably not though.
sudo pacman -S --noconfirm systemd-tools dbus acpid acpi xorg-server
xorg-server-common nvidia-lts slim nvidia xorg-xinit consolekit
nvidia-utils xorg-server-utils polkit lib32-nvidia-utils
sudo mkinitcpio -p linux-lts
sudo mkinitcpio -p linux
After this is run and I have rebooted. I can change TTYs and shutdown
and reboot without seeing red or black and the computer just freezing. I
honestly can not track it down, each time I think it is caused by one
certain thing something new in an update seems to trigger it. The
weirdest thing to me is it does not have to be an update of any of the
packages listed in my script to trigger the issue again. Also if I
remove any one of those, the issue persists.
Sorry if not fully related, just figured might help spring an idea or
something for you.
