You are not logged in.
- Topics: Active | Unanswered
#1 2015-07-09 11:23:22
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
[Solved] Oh No! something has gone wrong. Gnome 3.
Hi, this is my first time trying Arch Linux and for the past day I have been trying to resolve this issue when starting GNOME.
I have an intel core 17- 4790 and a nVidia GTX 780. I have installed all the drivers for the nVidia card from the their website and I have run the script. Xorg works perfectly and I don't know why this isn't working
Here is log file from /var/log/Xorg.0.log
[ 866.258]
X.Org X Server 1.17.2
Release Date: 2015-06-16
[ 866.261] X Protocol Version 11, Revision 0
[ 866.261] Build Operating System: Linux 4.0.4-2-ARCH x86_64
[ 866.262] Current Operating System: Linux localhost 4.0.7-2-ARCH #1 SMP PREEMPT Tue Jun 30 07:50:21 UTC 2015 x86_64
[ 866.262] Kernel command line: \vmlinuz-linux ro root=UUID=b6d5cec2-d1fc-4a50-9997-b63476be8613 initrd=\initramfs-linux.img
[ 866.264] Build Date: 30 June 2015 09:00:12PM
[ 866.265]
[ 866.266] Current version of pixman: 0.32.6
[ 866.268] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 866.268] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 866.271] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 10 07:15:44 2015
[ 866.273] (==) Using config file: "/etc/X11/xorg.conf"
[ 866.273] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 866.274] (==) ServerLayout "Layout0"
[ 866.274] (**) |-->Screen "Screen0" (0)
[ 866.274] (**) | |-->Monitor "Monitor0"
[ 866.274] (**) | |-->Device "Device0"
[ 866.274] (**) |-->Input Device "Keyboard0"
[ 866.274] (**) |-->Input Device "Mouse0"
[ 866.274] (==) Automatically adding devices
[ 866.274] (==) Automatically enabling devices
[ 866.274] (==) Automatically adding GPU devices
[ 866.274] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 866.274] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 866.274] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 866.274] (WW) Disabling Keyboard0
[ 866.274] (WW) Disabling Mouse0
[ 866.274] (II) Loader magic: 0x816d60
[ 866.274] (II) Module ABI versions:
[ 866.274] X.Org ANSI C Emulation: 0.4
[ 866.274] X.Org Video Driver: 19.0
[ 866.274] X.Org XInput driver : 21.1
[ 866.274] X.Org Server Extension : 9.0
[ 866.275] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 866.275] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 866.276] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 866.277] (--) PCI:*(0:2:0:0) 10de:1004:10de:104b rev 161, Mem @ 0xde000000/16777216, 0xd0000000/134217728, 0xd8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 866.277] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 866.277] (II) LoadModule: "glx"
[ 866.277] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 866.283] (II) Module glx: vendor="NVIDIA Corporation"
[ 866.283] compiled for 4.0.2, module version = 1.0.0
[ 866.283] Module class: X.Org Server Extension
[ 866.283] (II) NVIDIA GLX Module 352.21 Tue Jun 9 21:22:54 PDT 2015
[ 866.283] (II) LoadModule: "nvidia"
[ 866.283] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 866.284] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 866.284] compiled for 4.0.2, module version = 1.0.0
[ 866.284] Module class: X.Org Video Driver
[ 866.284] (II) NVIDIA dlloader X Driver 352.21 Tue Jun 9 20:58:55 PDT 2015
[ 866.284] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 866.284] (++) using VT number 1
[ 866.284] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 866.284] (II) Loading sub module "fb"
[ 866.284] (II) LoadModule: "fb"
[ 866.284] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 866.284] (II) Module fb: vendor="X.Org Foundation"
[ 866.284] compiled for 1.17.2, module version = 1.0.0
[ 866.284] ABI class: X.Org ANSI C Emulation, version 0.4
[ 866.284] (II) Loading sub module "wfb"
[ 866.284] (II) LoadModule: "wfb"
[ 866.284] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 866.284] (II) Module wfb: vendor="X.Org Foundation"
[ 866.284] compiled for 1.17.2, module version = 1.0.0
[ 866.284] ABI class: X.Org ANSI C Emulation, version 0.4
[ 866.284] (II) Loading sub module "ramdac"
[ 866.284] (II) LoadModule: "ramdac"
[ 866.284] (II) Module "ramdac" already built-in
[ 866.284] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 866.284] (==) NVIDIA(0): RGB weight 888
[ 866.284] (==) NVIDIA(0): Default visual is TrueColor
[ 866.284] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 866.285] (**) NVIDIA(0): Enabling 2D acceleration
[ 866.760] (II) NVIDIA: Allocated GPU:0 (GPU-5010982b-3d92-2550-8a82-c7a306457075) @
[ 866.760] (II) NVIDIA: PCI:0000:02:00.0
[ 866.771] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:2:0:0
[ 866.771] (--) NVIDIA(0): CRT-0
[ 866.771] (--) NVIDIA(0): DFP-0 (boot)
[ 866.771] (--) NVIDIA(0): DFP-1
[ 866.771] (--) NVIDIA(0): DFP-2
[ 866.771] (--) NVIDIA(0): DFP-3
[ 866.771] (--) NVIDIA(0): DFP-4
[ 866.781] (--) NVIDIA(0): CRT-0: disconnected
[ 866.781] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 866.781] (--) NVIDIA(0):
[ 866.801] (--) NVIDIA: GPU:0: Display (Ancor Communications Inc VG248 (DVI-I-1)) supports NVIDIA 3D Vision stereo.
[ 866.801] (--) NVIDIA(0): Ancor Communications Inc VG248 (DFP-0): connected
[ 866.801] (--) NVIDIA(0): Ancor Communications Inc VG248 (DFP-0): Internal TMDS
[ 866.801] (--) NVIDIA(0): Ancor Communications Inc VG248 (DFP-0): 330.0 MHz maximum pixel clock
[ 866.801] (--) NVIDIA(0):
[ 866.801] (--) NVIDIA(0): DFP-1: disconnected
[ 866.801] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 866.801] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 866.801] (--) NVIDIA(0):
[ 866.802] (--) NVIDIA(0): DFP-2: disconnected
[ 866.802] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 866.802] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[ 866.802] (--) NVIDIA(0):
[ 866.802] (--) NVIDIA(0): DFP-3: disconnected
[ 866.802] (--) NVIDIA(0): DFP-3: Internal TMDS
[ 866.802] (--) NVIDIA(0): DFP-3: 330.0 MHz maximum pixel clock
[ 866.802] (--) NVIDIA(0):
[ 866.802] (--) NVIDIA(0): DFP-4: disconnected
[ 866.802] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 866.802] (--) NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
[ 866.802] (--) NVIDIA(0):
[ 866.802] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 866.802] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 780 (GK110) at PCI:2:0:0 (GPU-0)
[ 866.802] (--) NVIDIA(0): Memory: 3145728 kBytes
[ 866.802] (--) NVIDIA(0): VideoBIOS: 80.10.36.00.01
[ 866.802] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 866.819] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 866.819] (**) NVIDIA(0): device Ancor Communications Inc VG248 (DFP-0) (Using EDID
[ 866.819] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 866.820] (==) NVIDIA(0):
[ 866.820] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 866.820] (==) NVIDIA(0): will be used as the requested mode.
[ 866.820] (==) NVIDIA(0):
[ 866.820] (II) NVIDIA(0): Validated MetaModes:
[ 866.820] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
[ 866.820] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 866.825] (--) NVIDIA(0): DPI set to (92, 91); computed from "UseEdidDpi" X config
[ 866.825] (--) NVIDIA(0): option
[ 866.825] (--) Depth 24 pixmap format is 32 bpp
[ 866.826] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 866.826] (II) NVIDIA: access.
[ 866.828] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 866.828] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 866.828] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 866.828] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 866.828] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 866.828] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 866.828] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 866.828] (II) NVIDIA(0): Config Options in the README.
[ 866.845] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[ 866.899] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 866.899] (==) NVIDIA(0): Backing store enabled
[ 866.899] (==) NVIDIA(0): Silken mouse enabled
[ 866.899] (**) NVIDIA(0): DPMS enabled
[ 866.899] (II) Loading sub module "dri2"
[ 866.899] (II) LoadModule: "dri2"
[ 866.899] (II) Module "dri2" already built-in
[ 866.899] (II) NVIDIA(0): [DRI2] Setup complete
[ 866.899] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 866.899] (--) RandR disabled
[ 866.902] (II) Initializing extension GLX
[ 866.902] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 866.944] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 866.944] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 866.944] (II) LoadModule: "libinput"
[ 866.944] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 866.944] (II) Module libinput: vendor="X.Org Foundation"
[ 866.944] compiled for 1.17.1, module version = 0.11.0
[ 866.944] Module class: X.Org XInput Driver
[ 866.944] ABI class: X.Org XInput driver, version 21.1
[ 866.945] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 30 paused 0
[ 866.945] (II) Using input driver 'libinput' for 'Power Button'
[ 866.945] (**) Power Button: always reports core events
[ 866.945] (**) Option "Device" "/dev/input/event2"
[ 866.945] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 866.945] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[ 866.945] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event2"
[ 866.945] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 866.945] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 866.945] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[ 866.945] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 866.945] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 866.945] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 866.945] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 33 paused 0
[ 866.945] (II) Using input driver 'libinput' for 'Power Button'
[ 866.945] (**) Power Button: always reports core events
[ 866.945] (**) Option "Device" "/dev/input/event1"
[ 866.946] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[ 866.946] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[ 866.946] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event1"
[ 866.946] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 866.946] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[ 866.946] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[ 866.946] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 866.946] (II) No input driver specified, ignoring this device.
[ 866.946] (II) This device may have been added with another device file.
[ 866.946] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[ 866.946] (II) No input driver specified, ignoring this device.
[ 866.946] (II) This device may have been added with another device file.
[ 866.946] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
[ 866.946] (II) No input driver specified, ignoring this device.
[ 866.946] (II) This device may have been added with another device file.
[ 866.946] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event19)
[ 866.946] (II) No input driver specified, ignoring this device.
[ 866.946] (II) This device may have been added with another device file.
[ 866.946] (II) config/udev: Adding input device USB Keyboard (/dev/input/event14)
[ 866.947] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 866.947] (**) USB Keyboard: Applying InputClass "libinput keyboard catchall"
[ 866.947] (II) systemd-logind: got fd for /dev/input/event14 13:78 fd 34 paused 0
[ 866.947] (II) Using input driver 'libinput' for 'USB Keyboard'
[ 866.947] (**) USB Keyboard: always reports core events
[ 866.947] (**) Option "Device" "/dev/input/event14"
[ 866.947] (II) input device 'USB Keyboard', /dev/input/event14 is tagged by udev as: Keyboard
[ 866.947] (II) input device 'USB Keyboard', /dev/input/event14 is a keyboard
[ 866.947] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.0/0003:04D9:0169.0002/input/input17/event14"
[ 866.947] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 8)
[ 866.947] (II) input device 'USB Keyboard', /dev/input/event14 is tagged by udev as: Keyboard
[ 866.947] (II) input device 'USB Keyboard', /dev/input/event14 is a keyboard
[ 866.947] (II) config/udev: Adding input device USB Keyboard (/dev/input/event15)
[ 866.947] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 866.947] (**) USB Keyboard: Applying InputClass "libinput keyboard catchall"
[ 866.948] (II) systemd-logind: got fd for /dev/input/event15 13:79 fd 35 paused 0
[ 866.948] (II) Using input driver 'libinput' for 'USB Keyboard'
[ 866.948] (**) USB Keyboard: always reports core events
[ 866.948] (**) Option "Device" "/dev/input/event15"
[ 866.948] (II) input device 'USB Keyboard', /dev/input/event15 is tagged by udev as: Keyboard
[ 866.948] (II) input device 'USB Keyboard', /dev/input/event15 is a keyboard
[ 866.948] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.1/0003:04D9:0169.0003/input/input18/event15"
[ 866.948] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 9)
[ 866.948] (II) input device 'USB Keyboard', /dev/input/event15 is tagged by udev as: Keyboard
[ 866.948] (II) input device 'USB Keyboard', /dev/input/event15 is a keyboard
[ 866.948] (II) config/udev: Adding input device Mad Catz Mad Catz R.A.T.9 Wireless Mouse (/dev/input/event0)
[ 866.948] (**) Mad Catz Mad Catz R.A.T.9 Wireless Mouse: Applying InputClass "evdev pointer catchall"
[ 866.948] (**) Mad Catz Mad Catz R.A.T.9 Wireless Mouse: Applying InputClass "libinput pointer catchall"
[ 867.000] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 36 paused 0
[ 867.000] (II) Using input driver 'libinput' for 'Mad Catz Mad Catz R.A.T.9 Wireless Mouse'
[ 867.000] (**) Mad Catz Mad Catz R.A.T.9 Wireless Mouse: always reports core events
[ 867.000] (**) Option "Device" "/dev/input/event0"
[ 867.000] (II) input device 'Mad Catz Mad Catz R.A.T.9 Wireless Mouse', /dev/input/event0 is tagged by udev as: Mouse
[ 867.000] (II) input device 'Mad Catz Mad Catz R.A.T.9 Wireless Mouse', /dev/input/event0 is a pointer caps
[ 867.000] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/0003:0738:1709.0001/input/input2/event0"
[ 867.000] (II) XINPUT: Adding extended input device "Mad Catz Mad Catz R.A.T.9 Wireless Mouse" (type: MOUSE, id 10)
[ 867.000] (**) Option "AccelerationScheme" "none"
[ 867.000] (**) Mad Catz Mad Catz R.A.T.9 Wireless Mouse: (accel) selected scheme none/0
[ 867.000] (**) Mad Catz Mad Catz R.A.T.9 Wireless Mouse: (accel) acceleration factor: 2.000
[ 867.000] (**) Mad Catz Mad Catz R.A.T.9 Wireless Mouse: (accel) acceleration threshold: 4
[ 867.000] (II) input device 'Mad Catz Mad Catz R.A.T.9 Wireless Mouse', /dev/input/event0 is tagged by udev as: Mouse
[ 867.000] (II) input device 'Mad Catz Mad Catz R.A.T.9 Wireless Mouse', /dev/input/event0 is a pointer caps
[ 867.000] (II) config/udev: Adding input device Mad Catz Mad Catz R.A.T.9 Wireless Mouse (/dev/input/mouse0)
[ 867.000] (II) No input driver specified, ignoring this device.
[ 867.000] (II) This device may have been added with another device file.
[ 867.000] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event3)
[ 867.000] (II) No input driver specified, ignoring this device.
[ 867.000] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event8)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event9)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event4)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event5)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.001] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event7)
[ 867.001] (II) No input driver specified, ignoring this device.
[ 867.001] (II) This device may have been added with another device file.
[ 867.002] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event13)
[ 867.002] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 867.002] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[ 867.002] (II) systemd-logind: got fd for /dev/input/event13 13:77 fd 37 paused 0
[ 867.002] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[ 867.002] (**) Eee PC WMI hotkeys: always reports core events
[ 867.002] (**) Option "Device" "/dev/input/event13"
[ 867.002] (II) input device 'Eee PC WMI hotkeys', /dev/input/event13 is tagged by udev as: Keyboard
[ 867.002] (II) input device 'Eee PC WMI hotkeys', /dev/input/event13 is a keyboard
[ 867.002] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input16/event13"
[ 867.002] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 11)
[ 867.002] (II) input device 'Eee PC WMI hotkeys', /dev/input/event13 is tagged by udev as: Keyboard
[ 867.002] (II) input device 'Eee PC WMI hotkeys', /dev/input/event13 is a keyboard
[ 867.002] (II) config/udev: Adding input device PC Speaker (/dev/input/event12)
[ 867.002] (II) No input driver specified, ignoring this device.
[ 867.002] (II) This device may have been added with another device file.
[ 870.286] (**) Option "fd" "30"
[ 870.286] (**) Option "fd" "33"
[ 870.286] (**) Option "fd" "34"
[ 870.286] (**) Option "fd" "35"
[ 870.286] (**) Option "fd" "36"
[ 870.286] (**) Option "fd" "37"
[ 870.287] (II) UnloadModule: "libinput"
[ 870.287] (II) systemd-logind: releasing fd for 13:77
[ 870.341] (II) UnloadModule: "libinput"
[ 870.341] (II) systemd-logind: releasing fd for 13:64
[ 870.409] (II) UnloadModule: "libinput"
[ 870.409] (II) systemd-logind: releasing fd for 13:79
[ 870.463] (II) UnloadModule: "libinput"
[ 870.463] (II) systemd-logind: releasing fd for 13:78
[ 870.516] (II) UnloadModule: "libinput"
[ 870.516] (II) systemd-logind: releasing fd for 13:65
[ 870.543] (II) UnloadModule: "libinput"
[ 870.543] (II) systemd-logind: releasing fd for 13:66
[ 870.846] (II) NVIDIA: Freed GPU:0 (GPU-5010982b-3d92-2550-8a82-c7a306457075) @
[ 870.847] (II) NVIDIA: PCI:0000:02:00.0
[ 870.924] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 870.927] (II) Server terminated successfully (0). Closing log file.Thanks! Any help is appreciated!
Last edited by mgrande465 (2015-07-10 01:53:47)
Offline
#2 2015-07-09 11:59:01
- forumache
- Member
- From: Netherlands
- Registered: 2011-09-02
- Posts: 57
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
Hi, this is my first time trying Arch Linux and for the past day I have been trying to resolve this issue when starting GNOME.
I have an intel core 17- 4790 and a nVidia GTX 780. I have installed all the drivers for the nVidia card from the their website and I have run the script.!
Why? The drivers are in the repository, it is recoomended to install it through pacman, no need to go to nVidia website and run scripts.
Offline
#3 2015-07-09 12:17:42
- Chazza
- Wiki Maintainer
- Registered: 2013-06-02
- Posts: 506
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
I second forumache's point. You shouldn't install anything directly from source. First check the official repositories, then the AUR. Only if both of those fail to provide what you need would you then start hunting down sources from websites. But even then, you would package the source, not install it directly from a script. If you don't know what packages you are looking for then don't forget to consult the wiki.
Anyway. I quickly skimmed through the log and spotted this:
[ 866.828] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 866.828] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 866.828] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 866.828] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 866.828] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 866.828] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 866.828] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 866.828] (II) NVIDIA(0): Config Options in the README.You can fix that with https://wiki.archlinux.org/index.php/NV … wer_source
I have no idea whether that is what is causing your problem, I'm not an NVIDIA user myself, but it's a start.
Last edited by Chazza (2015-07-09 12:18:59)
Offline
#4 2015-07-09 13:00:01
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
mgrande465 wrote:Hi, this is my first time trying Arch Linux and for the past day I have been trying to resolve this issue when starting GNOME.
I have an intel core 17- 4790 and a nVidia GTX 780. I have installed all the drivers for the nVidia card from the their website and I have run the script.!Why? The drivers are in the repository, it is recoomended to install it through pacman, no need to go to nVidia website and run scripts.
I reinstalled arch and everything and downloaded the drivers from pacman. the issues still persist.
Offline
#5 2015-07-09 13:00:45
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
I second forumache's point. You shouldn't install anything directly from source. First check the official repositories, then the AUR. Only if both of those fail to provide what you need would you then start hunting down sources from websites. But even then, you would package the source, not install it directly from a script. If you don't know what packages you are looking for then don't forget to consult the wiki.
Anyway. I quickly skimmed through the log and spotted this:
[ 866.828] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon [ 866.828] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X [ 866.828] (II) NVIDIA(0): configuration option may not be set correctly. When the [ 866.828] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will [ 866.828] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For [ 866.828] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and [ 866.828] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X [ 866.828] (II) NVIDIA(0): Config Options in the README.You can fix that with https://wiki.archlinux.org/index.php/NV … wer_source
I have no idea whether that is what is causing your problem, I'm not an NVIDIA user myself, but it's a start.
I installed acpid from pacman and started it but it didn't change a thing.
Offline
#6 2015-07-09 13:30:09
- Chazza
- Wiki Maintainer
- Registered: 2013-06-02
- Posts: 506
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
Ok. Another thing occurred to me. Are you using GDM to start GNOME? I ask because I just remembered that as of v3.16, GDM forwards the logs to the journal. Therefore, if GDM is in play, you would actually need to run something like
# journalctl -b /usr/bin/Xorg
to get up to date Xorg logs.
Offline
#7 2015-07-09 13:34:23
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
Ok. Another thing occurred to me. Are you using GDM to start GNOME? I ask because I just remembered that as of v3.16, GDM forwards the logs to the journal. Therefore, if GDM is in play, you would actually need to run something like
# journalctl -b /usr/bin/Xorg
to get up to date Xorg logs.
I am planning to use GDM but I am just going through the ~/.xinitrc file and the command startx. I tried loading chromium through that too and it came out with the same error in the logs.
Offline
#8 2015-07-09 13:40:50
- Chazza
- Wiki Maintainer
- Registered: 2013-06-02
- Posts: 506
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
Fair enough. One last thing and then I think I'm out of ideas. I saw a similar thread here: https://bbs.archlinux.org/viewtopic.php?id=195880
One suggestion in there was that a peripheral device was causing GNOME Settings Daemon to crash and hence leading to session failure. How about removing all peripheral devices and then trying to start GNOME?
Edit: I re-read your post and saw the Chromium point. That would suggest it's not a GNOME issue.
Last edited by Chazza (2015-07-09 13:44:38)
Offline
#9 2015-07-09 14:04:27
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
Fair enough. One last thing and then I think I'm out of ideas. I saw a similar thread here: https://bbs.archlinux.org/viewtopic.php?id=195880
One suggestion in there was that a peripheral device was causing GNOME Settings Daemon to crash and hence leading to session failure. How about removing all peripheral devices and then trying to start GNOME?
Edit: I re-read your post and saw the Chromium point. That would suggest it's not a GNOME issue.
I just pulled everything out except keyboard and it still errors. Thanks though for helping!
Offline
#10 2015-07-09 14:07:06
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 13,729
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
I have an intel core 17- 4790 ...
That's a Haswell processor. Is your microcode up to date?
Offline
#11 2015-07-09 14:10:07
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
mgrande465 wrote:I have an intel core 17- 4790 ...
That's a Haswell processor. Is your microcode up to date?
How would I do that, I'm new to arch...
EDIT: Silly me, need to look in the wiki more often...
Last edited by mgrande465 (2015-07-09 14:15:45)
Offline
#12 2015-07-09 14:20:13
- mgrande465
- Member
- From: Melbourne, Australia
- Registered: 2015-07-09
- Posts: 8
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
mgrande465 wrote:I have an intel core 17- 4790 ...
That's a Haswell processor. Is your microcode up to date?
YOU SIR HAVE SAVED ME. That worked perfectly. Thank you so much!
Offline
#13 2015-07-14 00:50:44
- jonnsl
- Member
- Registered: 2015-01-11
- Posts: 22
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
mgrande465 wrote:I have an intel core 17- 4790 ...
That's a Haswell processor. Is your microcode up to date?
I was having the same problem and this solved it. Thanks.
Here is the link to the wiki which has the instructions on how to update the microcode in case anyone else is having the same problem.
Just one question, the wiki doesn't make this clear, is this update a one time thing, or I have to leave the intel-ucode.img in the bootloader forever?
Offline
#14 2015-07-14 03:35:42
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 13,729
Re: [Solved] Oh No! something has gone wrong. Gnome 3.
Scimmia wrote:mgrande465 wrote:I have an intel core 17- 4790 ...
That's a Haswell processor. Is your microcode up to date?
I was having the same problem and this solved it. Thanks.
Here is the link to the wiki which has the instructions on how to update the microcode in case anyone else is having the same problem.Just one question, the wiki doesn't make this clear, is this update a one time thing, or I have to leave the intel-ucode.img in the bootloader forever?
You have to leave it there unless you can flash your UEFI firmware with a new enough one that it has the newer microcode. Even then, it doesn't hurt to keep it since you'll probably get other fixes before they become available in a firmware update.
Offline