You are not logged in.
I encountered a weird problem after fresh installation and could not solved by searching in the forums.
My screen become like shown at below when I run firefox or chrome. If I work only on gnome-terminal, I do not have any issue.



Those photos are take at three different times, each time screen gets weird and system halts.
[lamer@arch ~]$ uname -a
Linux arch 3.14.1-1-ARCH #1 SMP PREEMPT Mon Apr 14 20:40:47 CEST 2014 x86_64 GNU/LinuxI have nvidia as graphic card.
[root@arch lamer]# lspci | grep VGA
02:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400] (rev b1)nvidia driver 337.12 is installed on my system.
[root@arch lamer]# pacman -Qi nvidia
Name : nvidia
Version : 337.12-1I just found this post regarding the nvidia and added the mentioned parameters (rw rcutree.rcu_idle_gp_delay=1 CONFIG_HZ=1000) to the kernel line in GRUB, however it did not solve my problem.
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=be230c31-473d-4e92-9644-7e6671fd7a81 rw quiet rw rcutree.rcu_idle_gp_delay=1 CONFIG_HZ=1000At below you may find part of the dmesg output:
[ 5.814989] nvidia: module license 'NVIDIA' taints kernel.
[ 5.815002] Disabling lock debugging due to kernel taint
[ 5.845576] ACPI: PCI Interrupt Link [APMU] enabled at IRQ 20
[ 5.845861] ACPI: PCI Interrupt Link [AIGP] enabled at IRQ 23
[ 5.845875] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 5.846136] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:02:00.0 on minor 0
[ 5.846637] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 337.12 Fri Apr 4 14:51:15 PDT 2014Regarding the below error, I tried vga=normal kernel parameter.
Apr 17 22:14:25 arch kernel: NVRM: Your system is not currently configured to drive a VGA console
Apr 17 22:14:25 arch kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Apr 17 22:14:25 arch kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
Apr 17 22:14:25 arch kernel: NVRM: drivers including, but not limited to, vesafb, may result in
Apr 17 22:14:25 arch kernel: NVRM: corruption and stability problems, and is not supported.And some other errors that I do not know if they are related or not:
Apr 18 19:07:20 arch gnome-session[600]: Window manager warning: Log level 16: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.0 was not provided by any .service files
Apr 18 19:07:23 arch gnome-session[600]: Window manager warning: Log level 16: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.6 was not provided by any .service files
Apr 18 19:08:24 arch gnome-session[600]: Window manager warning: last_focus_time (296515) is greater than comparison timestamp (296513). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Apr 18 19:08:24 arch gnome-session[600]: Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x14001e2 not in stack
Apr 18 19:11:48 arch gnome-session[600]: Gjs-Message: JS LOG: pushModal: invocation of begin_modal failedAny suggestion?
Offline
I made a new installation, but nothing has changed.
My screen gets weird when I launch firefox, it also occured while trying to run gnome-control-center.
Last edited by OzanGuven (2014-04-21 18:16:42)
Offline
I made a new installation, but nothing has changed.
My screen gets weird when I launch firefox, it also occured while trying to run gnome-control-center.
You don't need to reinstall Arch when something doesnt work. Its never a good idea because it either still doesnt work, or worse it does and now you have no idea what the problem was. Just some friendly advice...
As for your problem, I have seen reports of this elsewhere with Gnome 3, though it doesnt usually cause the system to halt. My suggestion is to first install a simple window manager (e.g. Openbox, Fluxbox, etc), compton, and test for system stability. Depending on the results, I would try grabbing a different version of the Nvidia drivers from the AUR and see if that (temporarily) fixes your problem.
I could be wrong, but I dont see any issue with the output youve shown- back when I used Nvidia I always had that output and my system ran fine.
This seems like either a Gnome 3 or Nvidia driver problem, or perhaps the combination of both. Some others far more capable than me will be along shortly...
Offline